Jump to content

Recommended Posts

Guest iBodge
Posted

....another Android virgin so please be gentle..

On my Orange San Francisco & tried the following ROM's - Modaco custom Froyo R12 & FLB Froyo G2. Quite happy with them but wanted to try CyanogenMod for Blade 7.0.0 RC3 which I then installed OK.

First problem - couldn't figure out how I should add GoogleApps package? It is on my SD card but using File Manager to install it, opens ROM Manager to perform a ROM installation? If I "ok" this & the following 'Reboot & install into ClockworkMod Recovery', the OS reboots & hangs on the 'android' logo with the 'return/ back up' button on the phone constantly illuminated.

I tried a"Reboot into Recovery" using ROM Manager to revert back to FLB Froyo G2 but again on reboot the OS freezes on the android logo. My only option is to remove the battery & Cyanogen boots fine.

I have searched for some time for advice but stuck now as it almost appears my ROM manager does not function (though it's probably me). I tried installing Recovery Manager & Universal Android as per the previous ROM installs but these also now do not want to run??

Appreciate any suggestions as I am completely stuck now - as I cannot recover into prevous working ROM's with ROM Manager.

Guest Michealtbh
Posted

Gapps isn't an apk, it needs to be flashed in recovery. If rom manager won't let you boot into recovery try simply switching your phone off then switching back on while keeping volume down pressed until you enter recovery

Guest iBodge
Posted
Gapps isn't an apk, it needs to be flashed in recovery. If rom manager won't let you boot into recovery try simply switching your phone off then switching back on while keeping volume down pressed until you enter recovery

Thanks for the prompt reply!

I have tried that & again the phone hangs on the initial 'Android' logo screen with the 'back' button lit up constantly. This is the same when trying to use Rom Manager which is why it's rather worrying... I can access the SD card from USB so wonder if there is anyway to force it in to recovery that way?

Guest jayhix
Posted

sounds to me like you dont have clockwork recovery installed on your phone?

Guest hugobosslives
Posted (edited)
sounds to me like you dont have clockwork recovery installed on your phone?

Questions you must answer for us to help you:

1) have you ever flashed a clockwork recovery image?

2) if so, which one?

3) sounds like your pressing: power and volume up. you should be pressing: power + volume down did you do this?

4) sounds like you tried to install gapps by an installer? Dont do this, you have to 'install from sd' in clockwork.

Edited by hugobosslives
Guest iBodge
Posted
sounds to me like you dont have clockwork recovery installed on your phone?

According to the ROM Manager, I have Clockwork 3.0.1.4 installed. I just deleted it & installed it again. Using ROM Manager I flashed ClockworkMod Recovery - the phone then confirms model -"ZTE Blade" & says 'sucessfully flashed ClockworkMod Recovery!'. Yet if I try to boot to recovery from the manager, it still freezes... RAH!

Guest iBodge
Posted (edited)
Questions you must answer for us to help you:

1) have you ever flashed a clockwork recovery image?

2) if so, which one?

3) sounds like your pressing: power and volume up. you should be pressing: power + volume down did you do this?

4) sounds like you tried to install gapps by an installer? Dont do this, you have to 'install from sd' in clockwork.

Hi - I have used ClockworkMod Recovery 3.0.1.4 to install FLB Froyo G2 & Modaco custom Froyo R12 Rom. These all flashed fine. The ROM Manager says I have ClockworkMod REcovery 3.0.1.4 installed but if I select "Reboot into recovery", the phone freezes.

I tried the power + DOWN volume (even tried UP) - again nothing. Just an Android logo with a constantly lit back button on the phone (which usually lights up for a couple of seconds then goes off before booting - a bit like your HDD led on a laptop)

I did try to install gapps via ROM manager & that's where my problems started.

I also have recovery manager installed which cannot be executed - Should I have this & ROM manager or will they conflict? When trying to execute RecoveryManager v.034b, the phone displays a message - "Sorry! The application Recovery Manager (process com.podtwo.RecoveryManager) has stopped unexpectedly. Please try again. <force Close>"

PS - Superuser shows BOTH ROM Manager & Recovery Manager as 'allowed'. Again should I be running both of these or do they do the same thing?

Edited by iBodge
Guest hugobosslives
Posted

oh fair plays then. so your saying clockwork just suddenly stopped working? (i.e was fine and then suddenly not and you didn't play around with it?)

erm i dunno. sounds like your clockwork image has been screwed up somehow. i guess i would try a TPT flash of everything (software related) onto the phone again, including clockwork and see if that fixes it.

cant imagine the two are conflicting with each other. so i very much doubt this is the issue. Though where you say recovery manager says: "Sorry! The application Recovery Manager (process com.podtwo.RecoveryManager) has stopped unexpectedly. Please try again. <force Close>" this sounds like either a root issue or buggy apk. even if you have superuser it doesn't always mean your phone has active root. some roms 'lose' root on reboot and such (tho cm7 doesnt do this)... also reinstall this apk and see if it has the same force close.

i never use apps to run clockwork as its an extra risk not worth taking. its piss easy to do it manually anyways...

Guest iBodge
Posted
oh fair plays then. so your saying clockwork just suddenly stopped working? (i.e was fine and then suddenly not and you didn't play around with it?)

erm i dunno. sounds like your clockwork image has been screwed up somehow. i guess i would try a TPT flash of everything (software related) onto the phone again, including clockwork and see if that fixes it.

cant imagine the two are conflicting with each other. so i very much doubt this is the issue. Though where you say recovery manager says: "Sorry! The application Recovery Manager (process com.podtwo.RecoveryManager) has stopped unexpectedly. Please try again. <force Close>" this sounds like either a root issue or buggy apk. even if you have superuser it doesn't always mean your phone has active root. some roms 'lose' root on reboot and such (tho cm7 doesnt do this)... also reinstall this apk and see if it has the same force close.

i never use apps to run clockwork as its an extra risk not worth taking. its piss easy to do it manually anyways...

Yup - Clockwork worked up until I installed Cyanogen & have no played around with it (don't know enough!)

Sorry - what exactly do I do with the total phone transfer flash?

Talking of not having active root - I ran UniversalAndroid & it replies with "Failed! No---- Fu goo----" - Do you know if Universal Android runs on this ROM? Am I right in saying Cyanogen is 2.3 (gingerbread) when Uni...Android only works up to 2.2?

Guest hugobosslives
Posted

haha thats what i thought

erm follow if you want to do a tpt follow this thread and scroll to where it talks about tpt in the first post. tho if your not confident it might not be the easist thing do to...

yer universal androot will not work in cm7 as it is 2.3. and trys to install a superuser that works only to 2.2. tho cm7 should not requrie univeral androot as is pre-rooted. try another app that requires root to see if it is a root related problem....

Guest iBodge
Posted
haha thats what i thought

erm follow if you want to do a tpt follow this thread and scroll to where it talks about tpt in the first post. tho if your not confident it might not be the easist thing do to...

yer universal androot will not work in cm7 as it is 2.3. and trys to install a superuser that works only to 2.2. tho cm7 should not requrie univeral androot as is pre-rooted. try another app that requires root to see if it is a root related problem....

Thanks for the link - I will give the TPT a go.

At the risk of sounding a complete plank, this whole problem started beacuse I did not have the AppMarket on the ROM hence trying to load the gapps. You suggest trying an app that requires root but how do I load an app directly to the phone when I thought they had to be loaded directly via the AppMarket?

I have already saved a previous build (I take it this is just the apps & settings & NOT the whole ROM) with TitaniumBackup as well as saved an image of the previous good FLB G2 using Clockwork.

Moochos appreciate your assitance & patience! Cheers!

Guest wookie16081965
Posted
Thanks for the link - I will give the TPT a go.

At the risk of sounding a complete plank, this whole problem started beacuse I did not have the AppMarket on the ROM hence trying to load the gapps. You suggest trying an app that requires root but how do I load an app directly to the phone when I thought they had to be loaded directly via the AppMarket?

I have already saved a previous build (I take it this is just the apps & settings & NOT the whole ROM) with TitaniumBackup as well as saved an image of the previous good FLB G2 using Clockwork.

Moochos appreciate your assitance & patience! Cheers!

hello if you type the name of app in google with apk after it you can download from anywhere then using usb copy from pc to sd card then install it after you have turned off the usb connection

Guest iBodge
Posted
hello if you type the name of app in google with apk after it you can download from anywhere then using usb copy from pc to sd card then install it after you have turned off the usb connection

DOH! So simple when you know. Just running Titanium & its rooted ok. I would love to know what the recovery is not working but there you go. Too knackered now so will have a fresh butchers at the TPT tomorrow.

Many thanks!

Posted
DOH! So simple when you know. Just running Titanium & its rooted ok. I would love to know what the recovery is not working but there you go. Too knackered now so will have a fresh butchers at the TPT tomorrow.

Many thanks!

Had the same problem after nightly 28 (I think it was)

Had to flash recovery by fast boot and alls well!

Guest hugobosslives
Posted (edited)

yer titanium would have just backed up the apps and data, not the whole rom. only nandroids in clockwork will do this for you. you should always have a nandroid you can restore.

yer try flashing clockwork the normal way (using fastboot from a command prompt) before trying tpt.

I found this guide which newbies find really helpful who don't understand how command prompts work. its outdated so change the files (to something like 3.0.1.4), but explains it well.

report back if it works as you have got me intriguied by this one.....

EDIT: sorry if i'm being patronising by assuming you don't know how to use a command prompt. but tbh most people on here don't know as they just use apps like rom manager to do everything for them. so if you do know. sorry, and good lad!

Edited by hugobosslives
Guest iBodge
Posted
yer titanium would have just backed up the apps and data, not the whole rom. only nandroids in clockwork will do this for you. you should always have a nandroid you can restore.

yer try flashing clockwork the normal way (using fastboot from a command prompt) before trying tpt.

I found this guide which newbies find really helpful who don't understand how command prompts work. its outdated so change the files (to something like 3.0.1.4), but explains it well.

report back if it works as you have got me intriguied by this one.....

EDIT: sorry if i'm being patronising by assuming you don't know how to use a command prompt. but tbh most people on here don't know as they just use apps like rom manager to do everything for them. so if you do know. sorry, and good lad!

sorry for the delay - been agonising over my options..

I downloaded all the necessary for trying a fastboot install via a cmd window (which I have used a little). Trouble is, the phone could not get into fastboot or any boot loader options. Powering up & holding volume keys (down, up or even both with the menu button) did nothing. Phone went straight to the lil green fella & then to the CM7 boot logo. So tpt or other options seemed a none starter.

I tried checking for ROM updates through ROM Manger & followed the process it advised. On reboot, the device got to the CM7 logo screen & I left it 15 mins with the animated arrow still going. Had to remove the battery & try again. Exactly the same. Problems went from bad to worse as the phone now would not fully boot. Bugger!! Would 'bricked' be the appropriate term now?!

Took the phone back & got it replaced. Very fortunate here (if a little cheeky).

Thanks to everyone for your help but I must have screwed up clockwork somehow. The good news is, I checked the bootloader option on the replacement phone & it worked. So I used Recovery to install CM7 + gapps (after backing up the Orange rom first!). Voila - all worked beautifully. Even managed to restore to the Orange ROM & back again to cm7 to check if I have learnt my lesson.

My only complaint is the battery life runs out pretty quick so trying to stop all the power hungry functions. Otherwise, loving how responsive cm7 is & messing with different themes. Kewl!

THANKS TO ALL!!

ps - as a newbie, do I have to close the thread now or what?

Guest hugobosslives
Posted
......Took the phone back & got it replaced. Very fortunate here (if a little cheeky).

.....THANKS TO ALL!!

ps - as a newbie, do I have to close the thread now or what?

haha, all that help and thinking for nothing, oh well, this thread should help others in the same situation.

and no, don't close the thread, the whole point is others can benefit from these help threads as your probs not the only one with the same problems/questions.

Guest iBodge
Posted
haha, all that help and thinking for nothing, oh well, this thread should help others in the same situation.

and no, don't close the thread, the whole point is others can benefit from these help threads as your probs not the only one with the same problems/questions.

I really appreciate the advice & certainly tried hard to use everyone's input. But I could not get any recovery or boot loader started despite lots of attempts & ended up with just the CM7 logo spinning endlessly. Any manual attempt via the power / volume button would not start recovery. If there are any other ways around using the power / volume buttons to enter recovery (especially since ROM manager could identify clockwork as the installed recovery), I would love to understand them in detail (bearing in mind that "boot into recovery" from recovery manager would freeze on boot up).

With a whacking piece of humble pie in my chops, I have learnt from my sad experience (& as you advised) to enter recovery manually rather than letting recovery manager automatically install a rom.

At least then you know you can access recovery using the phones buttons, which I could not when it mattered.

Again - many thanks for your guidance.

Guest hugobosslives
Posted

no probs mate, glad you now got it working, and you've benefited from this experience as you now know how to use clockwork. there's no point (i can see) making backups from rom manager. cos when you do actually screw up (or sumthing weird happens, like in your case) there won't be anything you can do. as you probs won't be able to boot normally to enter the app.

Guest Superfuzz
Posted (edited)
I tried the power + DOWN volume (even tried UP) - again nothing. Just an Android logo with a constantly lit back button on the phone (which usually lights up for a couple of seconds then goes off before booting - a bit like your HDD led on a laptop)

Powering up & holding volume keys (down, up or even both with the menu button) did nothing.

Uhm maybe this is a silly remark but if you actually were pressing those exact buttons you mentioned, it's normal you couldn't get into Clockwork. You need to press power+home+volume down in order to boot into clockworkmod recovery. What you describe on the 1st quote is normal as well: pressing power up+vol down gets you to stock recovery, in which state the phone stays on the green droid.

If that was actually what you were doing wrong, you just ditched a perfectly working phone :D

Edited by Superfuzz
Guest hugobosslives
Posted
Uhm maybe this is a silly remark but if you actually were pressing those exact buttons you mentioned, it's normal you couldn't get into Clockwork. You need to press power+home+volume down in order to boot into clockworkmod recovery. What you describe on the 1st quote is normal as well: pressing power up+vol down gets you to stock recovery, in which state the phone stays on the green droid.

If that was actually what you were doing wrong, you just ditched a perfectly working phone B)

woah, slow down.

this is not correct........

clockwork (at least on a GEN 1 zte blade) is reached by pressing only two buttons: power + volume down. not by pressing home aswell.

also.... power + volume up does not get you to a 'stock recovery' it boots the phone into 'fastboot mode' (dunno if this has a more technical name as well, but most people call it 'fastboot mode'. This does not mean you've "ditched a perfectly working phone" It is a harmless mode which allows users to flash images or move around files by a command prompt on a computor through a usb cable.

sorry for the harshness in puting down you reply 'Superfuzz' but newbies will read this thread and get very confused otherewise....

So, to clarify: clockwork (once installed) is entered by: holding down power + volume down [when the phone is off]

happy flashing people :D

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.