Database Users

Flashed CM7, Unable to Restore Backup

I flashed CM7 but there's problems with it, I think it's broken. I can't restore. I go to ROM Manager and click restore but then nothing happens. Tried going to recovery but there's not restore option. How do I Restore?
I have clockworkmod recovery, I can go to bootloader screen. I'm just not sure how to Recover a backup...
These are my only options in CWM
Reboot System Now
Apply update from SD Card
Wipe data/factory reset
Wipe cache partition
There's an error at the bottom, what do I do???

Bump for thread...

have you ever done a backup before? if you don't have the backup, you can't restore from it. recovery doesn't do automatic backup.

txdeathray said:
have you ever done a backup before? if you don't have the backup, you can't restore from it. recovery doesn't do automatic backup.
Click to expand...
Click to collapse
I have done a backup, I have 2 backup files on here. The error I get is
e: can't open/cache/recovery/command

oh, that! ok, just to verify, after that screen do you get a green text menu or blue text menu

txdeathray said:
oh, that! ok, just to verify, after that screen do you get a green text menu or blue text menu
Click to expand...
Click to collapse
It actually doesn't say clockwork recovery it says Android system recovery. No it's a black screen
Basically like this only the Red triangle in the background and it says the same error
http://cdn.androidcommunity.com/wp-content/uploads/2010/07/Droid-X-Recovery-540x450.png

ok, since you can get have clockworkmod recovery, don't use RomManager. when you see those four options as you described, select "Apply Update from SD card", then select "Backup and restore", choose your restore file and you're good to go.
also, i hope you're not using the Droid X, because this is MyTouch 3G Slide forum.

txdeathray said:
ok, since you can get have clockworkmod recovery, don't use RomManager. when you see those four options as you described, select "Apply Update from SD card", then select "Backup and restore", choose your restore file and you're good to go.
also, i hope you're not using the Droid X, because this is MyTouch 3G Slide forum.
Click to expand...
Click to collapse
OMG THANKS SO MUCH! I was able to restore!!! I love you sir.
No, I do have a MyTouch 3G Slide

However since my Touchscreen refuses to work I suspect I'll have to unroot my phone now to turn it in. I'm following the unroot guide
http://forum.xda-developers.com/showthread.php?t=946435
The fella says I need to "If you are sending back your phone to Tmobile for replacement, make sure you flash the newest radio out as of now."
Flash a radio out? How do I do this?

BriK94 said:
Flash a radio out? How do I do this?
Click to expand...
Click to collapse
You can do so through CWM the same way. Select "Apply update from SD" and just use the zip for the latest radio (7.15) which you can grab from this thread --> [RADIO] Newest Radio from Froyo OTA 1/21/2011. Once applied just reboot and you will have the latest radio.

Help with flashing custom ROM please

Here is what I have done so far:
Unlocked bootloader from HTC DEV
Flashed custom recovery
I can get into the recovery fine, and have flashed a custom ROM but I am getting stuck at the white HTC boot screen
Can anyone offer some guidance please?

How long does it stick at the white HTC logo? did it write "quietly brilliant" or not? It can take a long time to boot up a new ROM, but if it's longer than 10 minutes then pull the battery and try flashing the ROM again.
check the MD5 sum of the ROM on the SDcard, and the MD5 the dev published. If they're different, re-download the ROM.
Not unheard of for a ROM with a good MD5 to flash badly, happened to me when I flashed recovery to a Sensation last week. Simply re-flashing it sorted it out OK.

chrisund123 said:
How long does it stick at the white HTC logo? did it write "quietly brilliant" or not? It can take a long time to boot up a new ROM, but if it's longer than 10 minutes then pull the battery and try flashing the ROM again.
check the MD5 sum of the ROM on the SDcard, and the MD5 the dev published. If they're different, re-download the ROM.
Not unheard of for a ROM with a good MD5 to flash badly, happened to me when I flashed recovery to a Sensation last week. Simply re-flashing it sorted it out OK.
Click to expand...
Click to collapse
thanks for the reply buddy
no it does not say quietly brilliant, i've flashed a few ROMS all exhibiting the same behaviour.
Can you confirm that the steps I have taken are correct? One obvious thing that I think I am missing is actually rooting the phone? Yes I have unlocked the bootloader and installed a custom recovery, but how do I root? Sorry to sound like a noob, I am a Samsung man, just temporarily using this phone.

winwiz said:
thanks for the reply buddy
no it does not say quietly brilliant, i've flashed a few ROMS all exhibiting the same behaviour.
Can you confirm that the steps I have taken are correct? One obvious thing that I think I am missing is actually rooting the phone? Yes I have unlocked the bootloader and installed a custom recovery, but how do I root? Sorry to sound like a noob, I am a Samsung man, just temporarily using this phone.
Click to expand...
Click to collapse
It sounds like you're doing it right, what version of recovery are you using? clockwork?
Basically, the steps are:
1.Boot into recovery
2.choose "Wipe data/factory reset", confirm, and go back to main menu
3.Select "Install zip from SDcard", select "choose zip from SDcard", and then select the ROM. Confirm, and then let it do it's thing. Then go back and choose to reset the phone, and you should be away (after a few minutes for it to boot up).

chrisund123 said:
It sounds like you're doing it right, what version of recovery are you using? clockwork?
Basically, the steps are:
1.Boot into recovery
2.choose "Wipe data/factory reset", confirm, and go back to main menu
3.Select "Install zip from SDcard", select "choose zip from SDcard", and then select the ROM. Confirm, and then let it do it's thing. Then go back and choose to reset the phone, and you should be away (after a few minutes for it to boot up).
Click to expand...
Click to collapse
yeah clockwork
exactly the process I have followed
will try again

winwiz said:
yeah clockwork
exactly the process I have followed
will try again
Click to expand...
Click to collapse
Use EXT4 recovery. Alot of DHD/Inspire roms do not like or use Clockwork mod recovery due to it causing issues.

To add what zel recommended, the reason its failing to boot is because you unlocked via HTC dev. With this method the boot.img has to be flashed seperately, via fast boot with the command fastboot flash boot boot.img(done using sdk). 4ext recovery has implemented a nice feature of being able to flash the bootimg for son/HTC dev unlocked devices.
Sent from my Inspire 4G using XDA

You should try using AHK (Advanced Hack Kit). It is really easy to use tool, you just need to install the drivers provided with it.

Can't boot into custom recovery

Hey all, trying to flash CM10.2 on my G2 and I'm not able to boot into a custom recovery. Here's how I did everything.
Rooted - all was successful as far as I can tell. Was able to install Titanium backup and backup files and allow root.
I downloaded ROM Manager and installed CWM. When I went to boot into recovery, i get the error with the Android a red triangle exclamation point above him. So I tried to switch to TWRP through Rom manager, no luck. I tried to 'flash' TWRP through the command prompt and download of the recovery file, no luck.
I saw somewhere to download SuperSU, so I did that and tried again, and same issues. When I 'cleaned' SuperSU, uninstalled and reinstalled it but this time chose 'use custom recovery' - it tied to reboot into recovery, saw a standing up right android with a spinning icon, but then went to the same error.
Obviously I'm missing something somewhere. Can't figure out what.
Thanks for any help!

Don't use rom manager. Either use adb and push the recovery or use the app flashify to install the recovery. There are many threads ids the development sections on how to install recoveries
Sent from my LG-D800 using Tapatalk

tdevaughn said:
Don't use rom manager. Either use adb and push the recovery or use the app flashify to install the recovery. There are many threads ids the development sections on how to install recoveries
Sent from my LG-D800 using Tapatalk
Click to expand...
Click to collapse
Thanks, Is there a way to undo what I've done from rom manager? Because I used adb to push the recovery and still had the same issue, and using flashify to flash the image doesn't seem to work. Booting into recovery just gets me to stock recovery asking 'do you want to factory wipe your device'
Edit: When I boot to recovery from within flashify, it gives a 'boot certification error' upon booting

goldenmonkey1 said:
Thanks, Is there a way to undo what I've done from rom manager? Because I used adb to push the recovery and still had the same issue, and using flashify to flash the image doesn't seem to work. Booting into recovery just gets me to stock recovery asking 'do you want to factory wipe your device'
Edit: When I boot to recovery from within flashify, it gives a 'boot certification error' upon booting
Click to expand...
Click to collapse
Are you using a recovery that has been Loki'd. The G2 needs this to by pass the bootloader. By that error it does not seem you used the correct recovery file.

Jimi Mack said:
Are you using a recovery that has been Loki'd. The G2 needs this to by pass the bootloader. By that error it does not seem you used the correct recovery file.
Click to expand...
Click to collapse
I used the one from here - http://forum.xda-developers.com/showthread.php?t=2449670 - 2.6.3.3 and just flashed it with flashify most recently. But I was having the same issue when I installed it via adb and 'option 1' as shown there.
Yeah, when flashing that recovery image using option 1, I still get "secure booting error - boot certification verify" after I reboot into recovery

Huh, I got it.
Reading this post here - http://forum.xda-developers.com/showpost.php?p=48118278&postcount=567
Someone else was having the same issue as me. The newest recovery gave him that same error. Flashed 2.6.3.2 and it worked fine. (So far)

Glad to hear. Good Luck.

[Q] Rooted Note 3 only boots to System Recovery

I recently attempted to restore a previous rom through safestrap but when it was nearly finished the phone restarted and booted into system recovery. I have ]removed battery and waited for 10 minutes, wiped/restored through system recovery, wiped cache,and attempted to reflash Jellybeans rom. When attempting to flash the rom an E: signature error pops up and it reboots into recovery. I am no expert and have no idea how to fix this. Any help or advice would be greatly appreciated.

I think you should start by clarifying what you mean by "system recovery". Do you mean "stock recovery", or "safestrap recovery"?
If you install Safestrap on a Note 3, it leaves untouched the stock recovery boot (which has a simple (red/blue/yellow) plain-text menu system that you navigate using the volume up/down rocker button & the power button), and also installs the "Safestrap Recovery". The latter appears on every boot and gives an option to either continue the normal boot, or proceed to Safestrap's touch-based UI.
Also you might want to mention whether you are doing these restores to the "Stock ROM" slot or one of the alternate (1-4) slots in Safestrap.
The signature error thing probably results from you accidentally turning on the signature check option in Safestrap (unfortunately the vast majority of ROM devs fail to sign their ROMs, so this option usually doesn't work.) This puts the onus on anyone flashing ROMS to compute a checksum (md5 or sha1) of the ROM zip file after they transfer it to the phone, and cross-check this checksum against the value published by the ROM developer.

bftb0 said:
I think you should start by clarifying what you mean by "system recovery". Do you mean "stock recovery", or "safestrap recovery"?
If you install Safestrap on a Note 3, it leaves untouched the stock recovery boot (which has a simple (red/blue/yellow) plain-text menu system that you navigate using the volume up/down rocker button & the power button), and also installs the "Safestrap Recovery". The latter appears on every boot and gives an option to either continue the normal boot, or proceed to Safestrap's touch-based UI.
Also you might want to mention whether you are doing these restores to the "Stock ROM" slot or one of the alternate (1-4) slots in Safestrap.
The signature error thing probably results from you accidentally turning on the signature check option in Safestrap (unfortunately the vast majority of ROM devs fail to sign their ROMs, so this option usually doesn't work.) This puts the onus on anyone flashing ROMS to compute a checksum (md5 or sha1) of the ROM zip file after they transfer it to the phone, and cross-check this checksum against the value published by the ROM developer.
Click to expand...
Click to collapse
It's system recovery, so stock. Blue text, dead android guy all that. Safestrap won't come up at all when it had previously. I haven't tried flashing a stock rom yet because I am unable to put anything on my phone since it only boots into recovery.

Sirrometan said:
It's system recovery, so stock. Blue text, dead android guy all that. Safestrap won't come up at all when it had previously. I haven't tried flashing a stock rom yet because I am unable to put anything on my phone since it only boots into recovery.
Click to expand...
Click to collapse
Sounds like you need to odin back to stock.

shiftr182 said:
Sounds like you need to odin back to stock.
Click to expand...
Click to collapse
^ Yep.
BTW there is no such thing as "system recovery" in Android. Even the term "factory reset" is highly misleading in the context of rooted phones, or even stock phones that have gone through an OTA update.
Everybody would have been far better off if they had called it what it really is: user data wipe. That is all it has ever done; it absolutely does not "restore the system software back to a factory state"

Odin'd back and had to reroot and flash. All is well. It must have been a bad backup or something.
And I was just calling it what it says at the top of the screen which is; "Android System Recovery.." Sorry if that caused any confusion.

Sirrometan said:
Odin'd back and had to reroot and flash. All is well. It must have been a bad backup or something.
And I was just calling it what it says at the top of the screen which is; "Android System Recovery.." Sorry if that caused any confusion.
Click to expand...
Click to collapse
Glad to see things going well.

Sirrometan said:
Odin'd back and had to reroot and flash. All is well. It must have been a bad backup or something.
Click to expand...
Click to collapse
Good news, Nate!
Your experience is why (for now, anyway) that I just leave a (rooted) stock ROM in the stock slot, and run a tweaked ROM in an alternate slot as my daily driver. Because there really is no independently-bootable custom recovery, if something goes wrong with the stock slot, you have to go all the way back to square 1 with Odin... which also means losing everything since the last backup.
The stock recovery isn't useful for anything except wiping and/or manually installing Samsung official OTAs. And it definitely will only accept Samsung-signed update.zip packages; that's why you got the E: error message (I wasn't sure which recovery you were talking about)

[Q] Can't boot into Clockwork ROM recovery mode

So after recovering from a botched flashing experience, i decided to go down the safe route and get an app do all the dirty work for me.
I rooted the phone with CF-AutoRoot. Then installed Clockwork ROM manager, which then suggested and installed (successfully, according to the app) ClockworkMOD recovery (6.0.4.8). It should be straightforward from there - Install ROM from SD Card -> Pick the ROM file -> Click 'Reboot and install'.
Issue here is that the phone boots into stock recovery mode. Same happens if I click 'Reboot into Recovery' in the main menu of CLW. So even though I supposedly have CLW recovery, I can't boot into it. Anyone came across an issue like that before? Really want CMMOD up and running but i am not sure where I am going wrong.

Don't use Rom Manager go flash recovery. It's not working with note 3. Get ahead here http://forum.xda-developers.com/showthread.php?t=2454079
Sent from my SM-N9005 using Tapatalk