Related
Hi
I am trying to backup my current rom from my rooted Tmo G2(just for trying because i could get the original rom from the xda wiki.
When i click on the backup rom, my phone reboots and tries to go onto recovery mode, but then i get that black phone and the red exclamation point. after that i cannot do anything.
I have to remove the battery to reboot the phone.
What am i doing wrong here?
thanks
The red exclamation means your still in stock recovery. Reboot the phone, go into ROM Manager and flash the recovery TWICE. I had this same problem and flashing it a second time solved it
Sent from my T-Mobile G2 using XDA App
you are a genius.
I did update the recovery before trying, but this time, i did it twice in a row and that did the trick
thanks again
Same problem but flashing it twice still doesn't fix it?
pretty much what i said above... I have the same exact problem so when i =read this i flashed it twice and still get the red ! arrow when i backup it restarts? any other ideas?
If you get this image, just hit Vol (+) and Power. This will continue you to recovery and you can see whether you are still stock or CW Recovery. I am CW, but I will sometimes get the triangle image.
I think you have to flash twice because of root permissions.
My G2 did not ask me for superuser permission until after it had already downloaded the recovery and was in the process of installing it.
The second time you flash it, ROM manager will already have the superuser permission it needs to successfully install it.
I think that the initial (unsuccessful) installation of recovery is what gets ROM manager to ask for superuser access.
So if you have a way to grant ROM manager su permission before installing, it SHOULD work the first time. I don't really know how to test this theory yet though.
I temp rooted + flashed the recovery part 4 times now, "successful" each time, but on "ROM Backup", the red exclamation mark is the only thing that works..
DesireHD
AlCapone said:
I temp rooted + flashed the recovery part 4 times now, "successful" each time, but on "ROM Backup", the red exclamation mark is the only thing that works..
DesireHD
Click to expand...
Click to collapse
Do you have Desire HD ? If so, you are in the wrong forum, this is the Vision forum (G2/Desire Z).
If you do have a Vision, then I suspect the problem is that you don't have S-OFF. Temp root is enough to run ROM Manager, but not enough to flash a custom recovery.
ok, thanks that might be it - still ..strange that it detects the recovery software as installed after boot - maybe it's just saving the information and fakes it. ?
yes, I am in wrong forum - just searched for this issue, and it seems like it is just the same.
Thanks.
AlCapone said:
ok, thanks that might be it - still ..strange that it detects the recovery software as installed after boot - maybe it's just saving the information and fakes it. ?
yes, I am in wrong forum - just searched for this issue, and it seems like it is just the same.
Click to expand...
Click to collapse
If you don't have S-OFF, then your recovery partition (plus others) is write-protected in hardware. So the software thinks it's writing to it, but the data is just being held in cache. When you reboot the cache is lost so you see the old image (i.e. stock recovery) again.
Remember to have "USB Debugging" enabled, i've just spend over 2hrs tbefore i've figured it out...
I just perm rooted my G2 using the Visonary + gfree (No ADB) method, and it worked on the 1st try. I am also trying to backup my stock rom, and was wondering about the steps. I have ROM Manager, and I know that I need to flas ClockWorkMod Recovery, But do I do it before I attempt to backup my current ROM, or after? Do I need to erase recovery before flashing ClockWork?
omarsalmin said:
The red exclamation means your still in stock recovery. Reboot the phone, go into ROM Manager and flash the recovery TWICE. I had this same problem and flashing it a second time solved it
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
This worked perfectly for me. Thank you!
Hi!
I bought a Desire HD a week ago and today I decided to try one of the custom roms. I rooted it with Visionary+, turned s-off with the one-click tool found in another thread, installed Rom Manager and Clockwork mod and then flashed it with a custom rom from the recovery/boot screen without wiping anything.
The problem is, when I later tried to install another rom, it wouldn't boot, it's stuck on the HTC boot screen. I've tried reflashing it, wiping everything there is to wipe and I even tried RUU but it won't recognize the phone. Can anyone help me how to restore to the normal stock rom?! I can bring up the Clockworkmod recovery menu if I take out the battery and put it back in.
I would be very grateful if someone could help me with this! Consider that I'm a noob though so try to write the instructions as simply as possible
Hi, I'm basically in the same boat (I take it you tried one of the stable CM6 builds?).
Digged through an awful lot of stuff, found something about downgrading clockwork.
Maybe this'll help you, I'm still having trouble.
I've found an older clockwork recovery image, gathered all the SDK bits and pieces, got my USB drivers set up after even more digging - now this:
D:\android-sdk-windows\tools>fastboot boot recovery.img
downloading 'boot.img'... OKAY
booting... FAILED (remote: not allowed)
It's rooted, S-OFF, all that good jazz. Halp. :<
enectrixx said:
Hi!
I bought a Desire HD a week ago and today I decided to try one of the custom roms. I rooted it with Visionary+, turned s-off with the one-click tool found in another thread, installed Rom Manager and Clockwork mod and then flashed it with a custom rom from the recovery/boot screen without wiping anything.
The problem is, when I later tried to install another rom, it wouldn't boot, it's stuck on the HTC boot screen. I've tried reflashing it, wiping everything there is to wipe and I even tried RUU but it won't recognize the phone. Can anyone help me how to restore to the normal stock rom?! I can bring up the Clockworkmod recovery menu if I take out the battery and put it back in.
I would be very grateful if someone could help me with this! Consider that I'm a noob though so try to write the instructions as simply as possible
Click to expand...
Click to collapse
Which version clockwork mod are you using? And what is the ROM you tried to flash?
Sometimes custom ROMs can take 5 minutes to boot...so give it some more time and see if that helps.
Headwoünd said:
Hi, I'm basically in the same boat.
Digged through an awful lot of stuff, found something about downgrading clockwork.
Maybe this'll help you, I'm still having trouble.
I've found an older clockwork recovery image, gathered all the SDK bits and pieces, got my USB drivers set up after even more digging - now this:
D:\android-sdk-windows\tools>fastboot boot recovery.img
downloading 'boot.img'... OKAY
booting--- FAILED (remote: not allowed)
It's rooted, S-OFF, all that good jazz. Halp. :<
Click to expand...
Click to collapse
seems like your pc is not recognizing your phone. And should not you flash the recovery first and then boot?
I did flash the recovery via Rom Manager, which gave me Clockwork Recovery version 3.0.0.5.
Then I had Rom Manager download CM6, it rebooted the phone, phone gets stuck in HTC splash screen.
According to the thread I linked above, I needed to downgrade Clockwork Recovery, hence flashing 2.5.x.x via command prompt.
The drivers are installed correctly, I'm at least sure of that.
Recovering my previously backed up stock ROM won't get me further than the splash screen either, same with wiping everything that can be wiped before that.
Headwoünd said:
I did flash the recovery via Rom Manager, which gave me Clockwork Recovery version 3.0.0.5.
Then I had Rom Manager download CM6, it rebooted the phone, phone gets stuck in HTC splash screen.
According to the thread I linked above, I needed to downgrade Clockwork Recovery, hence flashing 2.5.x.x via command prompt.
The drivers are installed correctly, I'm at least sure of that.
Recovering my previously backed up stock ROM won't get me further than the splash screen either, same with wiping everything that can be wiped before that.
Click to expand...
Click to collapse
Then use ROM manager to downgrade the CWM to 2.x. You can do it under the option "All recoveries" in ROM manager. People are reporting problems with the latest version of CWM. Check if you get the same if you wipe everything and install another custom ROM.
Can't find a way to even get past the first splash screen - only thing I can properly access is the Bootloader.
Same here. When I boot I just see the initial "HTC" logo, nothing else.
I had Mike's Revolution HD ROM installed and working just fine, and then I tried to install another mod, which got me to this situation.
I have CWM 3.0.0.5 and I have a nandroid backup of the working system from before installing the last mod.
I tried recovering the nandroid, which goes smoothly (including the MD5 validation of the backup) but it still doesn't boot afterwards. I wiped the boot, system and data partitions and tried restoring again - same result.
I assume my next step is to flash a new ROM but unfortunately I don't have any ROMs on my SDCARD, so I need a way to push it there. I tried with fastboot but it doesn't recognize a partition called "sdcard". I believe adb should work while I'm in CWM but it just says "error: device not found".
Any suggestions?
sphuyal said:
Which version clockwork mod are you using? And what is the ROM you tried to flash?
Sometimes custom ROMs can take 5 minutes to boot...so give it some more time and see if that helps.
Click to expand...
Click to collapse
Sorry, no idea which version, but it's the default that comes with Rom Manager. I downloaded Rom Manager yesterday so I guess it's the most recent Clockwork mod.
Left it for 15 minutes, still nothing. I used Android Revolution HD 2.0.11 for the first flash which worked and then when I tried to install Pays-ROM HD Sparta 1.0 I got stuck on the boot screen. I've tried recovering from the previous backup I made on the recovery screen with no result.
Just got mine back alive
Flashed CWM 2.5.1.3 and restored the nandroid with it.
Spending the last few hours searching the forums my best advice is to avoid 3.0.0.5
Went a different approach - finally figured out that you could mount the sdcard via Clockwork Recovery, threw newest CM7 nightly on there and installed it with Clockwork as well.
CHRIST that was a pain in the ass... and I thought downgrading the stock ROM was annoying.
as a rule i have found out cwm3 is for flashing gingerbread and cwm2 is for froyo
Headwoünd said:
Went a different approach - finally figured out that you could mount the sdcard via Clockwork Recovery, threw newest CM7 nightly on there and installed it with Clockwork as well.
CHRIST that was a pain in the ass... and I thought downgrading the stock ROM was annoying.
Click to expand...
Click to collapse
Thanks for the advice! It worked for my DHD too Except that I, after flashing ut with CM7, restored it to stock with RUU! Thanks to everyone here who tried to help
erank said:
Just got mine back alive
Flashed CWM 2.5.1.3 and restored the nandroid with it.
Spending the last few hours searching the forums my best advice is to avoid 3.0.0.5
Click to expand...
Click to collapse
how do I get 2.5.1.3 onto the device when I can't even get the darn thing to load?
encrypshun said:
how do I get 2.5.1.3 onto the device when I can't even get the darn thing to load?
Click to expand...
Click to collapse
Read here: http://forum.xda-developers.com/showthread.php?t=855490&page=132 (jump to page 132 #1312)...
Take your battery off, then put it back in. Hold power button and volume down button at the same time. You come to recovery...or alternately you can use adb.
sphuyal said:
Read here: http://forum.xda-developers.com/showthread.php?t=855490&page=132 (jump to page 132 #1312)...
Take your battery off, then put it back in. Hold power button and volume down button at the same time. You come to recovery...or alternately you can use adb.
Click to expand...
Click to collapse
mate you're a STAR. I actually downloaded a recovery image (from post 1315) in the same thread but it kept saying "connecting to device". When I downloaded the recovery image from 1312 and ran "fastboot flash recovery recovery.img" it say's
sending recovery ... OK
writing recover ... OKAY
What do I do next? Just reboot the device?
oh mother looks like I got somewhere. I did a format device and it went into the CWM 2.3.XX screen as below, reloaded Cyanogen 6.1.3 and boom I'm in. Man I though the device was a goner....I'm almost feeling brave enough to install Cyanogen 7.X
encrypshun said:
oh mother looks like I got somewhere. I did a format device and it went into the CWM 2.3.XX screen as below, reloaded Cyanogen 6.1 and boom I'm in. Man I though the device was a goner....
Click to expand...
Click to collapse
So you are happy with your device now?
Well not really, I went back to HTC Sense because Internet Pass Through wasn't available on Cyanogen and now I cannot get the phone to login and create my google account no matter what
Headwoünd said:
Can't find a way to even get past the first splash screen - only thing I can properly access is the Bootloader.
Click to expand...
Click to collapse
the REMOTE NOT ALLOWED error means you only have radio s-off, so you cannot issue fastboot commands to your device.
I noticed when I first got the phone that there was surprisingly no recovery mode. I'd get into bootloader and try to enter recovery and I get the dead android guy with a red triangle. Well I recently rooted and installed touchwiz recovery and was able to boot into it exactly once. After that though it does the same thing of giving me the dead android with the red triangle. Phones is barely a month old so do I just need to take it back to stock and return it or whats going on?
revwolf said:
I noticed when I first got the phone that there was surprisingly no recovery mode. I'd get into bootloader and try to enter recovery and I get the dead android guy with a red triangle. Well I recently rooted and installed touchwiz recovery and was able to boot into it exactly once. After that though it does the same thing of giving me the dead android with the red triangle. Phones is barely a month old so do I just need to take it back to stock and return it or whats going on?
Click to expand...
Click to collapse
Sounds like you didn't remove/rename /system/recovery-from-boot.p
This file flashes the stock recovery every time the phone boots. The recovery you describe is the stock recovery.
http://forum.xda-developers.com/showthread.php?t=1357642
Delete boot-from-recobery.p
If you have rooted your device,detele boot-from-recobery.p in "/system"
Yup. that fixed that. Wonder why that step wasn't in any of the how-to's I read. LOL.
It's in mine =]
revwolf said:
Yup. that fixed that. Wonder why that step wasn't in any of the how-to's I read. LOL.
Click to expand...
Click to collapse
Just some background for learning purposes:
There are TWO files added to your system when you apply an OTA update: a script (/system/etc/install-recovery.sh) that applies a patch (/system/recovery-from-boot.p) to the recovery partition, effectively re-flashing the stock recovery every time you boot your device. These files do NOT exist in Google's factory images -- they are only placed on your device if you apply an OTA update. They serve no purpose other than what I just mentioned, and are not part of the stock ROM (in other words, deleting them is perfectly safe, and will not affect your ability to apply any future updates using CWM).
I'm having the same problem. I can't get into the recovery mode. I just see a red triangle with an exclamation point.
Here's what I have done so far with my G-Nex. I had mine originally at 4.0.4 Yakjuxw. I received an OTA update to 4.1.1 JRCO03C and started to have some wifi issues. I did plan to flash it back to 4.0.4.
I used Mark Skippen's toolkit (the DOS-like GUI) to unlock the bootloader, to root, and to flash it to 4.0.4 IMM76I Google factory, and finally to root it again.
After reading more about manual ADB commands of doing the steps I've done above for further learning, I found out I can't get into the recovery mode.
I checked on the /system/recovery-from-boot.p and the file do not exist.
Will trying to flash a custom or stock recovery fix it?
TIA
The red triangle screen IS the stock recovery, but flashing CWM should sort it out
EddyOS said:
The red triangle screen IS the stock recovery, but flashing CWM should sort it out
Click to expand...
Click to collapse
Yes. Except that I don't have any options to choose from. I only got a picture of a lying android with the red triangle screen and an exclamation point.
Yeah, that's normal for the Nexus...
EddyOS said:
Yeah, that's normal for the Nexus...
Click to expand...
Click to collapse
I see. I hope you could bear with me more as I'm new with this. Will flashing custom recovery require me to do a cleanup of my files, I mean like wiping dalvik-cache and everything?
Shouldn't do, just flash it when in the bootloader
z_extend_99 said:
Yes. Except that I don't have any options to choose from. I only got a picture of a lying android with the red triangle screen and an exclamation point.
Click to expand...
Click to collapse
To get the options when you are on that screen, just hold power and press volume up. More details can be found in the "basics" link in my signature.
Thanks guys for this. I came across this thread as I was flashing my GNexus back to stock as I'm selling it tomorrow. I've run custom recovery ever since I got this phone and I forgot how a stock recovery looked like.
I was going crazy reflashing the recovery.img via fastboot only to see the red triangle and the android lying on its back which is normal. I was expecting a similar recovery with less selection on the menu for the stock recovery.
Hi. i tried to install maximus new 3.2 rom and after i installed from zip and rebooted my phone, my phone is stuck on the htc logo white screen and keeps rebooting!
i tried to go back to recovery and it doesnt work now! the phone goes into a black screen then reboots again!
try in fastboot mode fastboot erase cache .
you posted in wrong section
Don't forget to reflash kernel modules incase you are using a custom kernel and if you need to reflash the recovery in fastboot make sure your battery isn't below 10% else fastboot won't allow you to flash it.
Sent from my HTC One X using Tapatalk 2
jonneymendoza said:
Hi. i tried to install maximus new 3.2 rom and after i installed from zip and rebooted my phone, my phone is stuck on the htc logo white screen and keeps rebooting!
i tried to go back to recovery and it doesnt work now! the phone goes into a black screen then reboots again!
Click to expand...
Click to collapse
I have the same problem. The solution is simple: Flash the default recovery then re-flash the clockworkmod recovery again and then try.
You mention which rom you installed and that you flashed the zip file but don't mention that you did a wipe before this (depending on which rom you were previously on) or that you flashed the boot.img file via fastboot first.
PS! There's a section specifically for Q&A and these types of posts should go there are not to be posted in the dev section. Hopefully some kind mod will move it, but I guess you have a few answers by now.
jonneymendoza said:
Hi. i tried to install maximus new 3.2 rom and after i installed from zip and rebooted my phone, my phone is stuck on the htc logo white screen and keeps rebooting!
i tried to go back to recovery and it doesnt work now! the phone goes into a black screen then reboots again!
Click to expand...
Click to collapse
You haven't flashed the boot.img if your phone keeps rebooting.
Also - you've posted this in the wrong section, this is a development section only.
Sent from my HTC One X using Tapatalk 2
theintelligent said:
I have the same problem. The solution is simple: Flash the default recovery then re-flash the clockworkmod recovery again and then try.
Click to expand...
Click to collapse
Soz for the delay but this is what i done and it worked. reflashed the recovery from fastboot mode and it worked.
i dont know why some rom and karnals dont boot up properly. a pain really. nearly got worried when maximus lates stable rom messed up my recovery clockworkmod!
Hi! All my problems became today, when I decided to root that samsung ROM. I used evervolv (old version) I red the instructions and I flashed kernel and boot.img with the htc one V all-in-one toolkit. It said that: "boot.img flashed" I was like: nice, and continued, did full wipe, and wiped cache then I flashed ROM and update. I tried to boot, but it did not boot. After waiting for about an hour I decided to do something. I was able to get to fastboot, and I flashed boot.img manually trough adb and fastboot, did everything like before, and still no boot.
I decided to try some else rom, because I have SD- card reader in my laptop. I putted sphongle to SD- card and I was able to get to fastboot, flashed boot.img, and flashed ROM. Phone was not able to boot, and it just got stuck in a boot loop. I tried samsung again, and now I can only get to recovery or to the white HTC- screen, that has text about build being for developement purposes only. Does anyone have any ideas how-to get my phone back to life, or is it totaly dead? Answes appreciated =)
Enpo said:
Hi! All my problems became today, when I decided to root that samsung ROM. I used evervolv (old version) I red the instructions and I flashed kernel and boot.img with the htc one V all-in-one toolkit. It said that: "boot.img flashed" I was like: nice, and continued, did full wipe, and wiped cache then I flashed ROM and update. I tried to boot, but it did not boot. After waiting for about an hour I decided to do something. I was able to get to fastboot, and I flashed boot.img manually trough adb and fastboot, did everything like before, and still no boot.
I decided to try some else rom, because I have SD- card reader in my laptop. I putted sphongle to SD- card and I was able to get to fastboot, flashed boot.img, and flashed ROM. Phone was not able to boot, and it just got stuck in a boot loop. I tried samsung again, and now I can only get to recovery or to the white HTC- screen, that has text about build being for developement purposes only. Does anyone have any ideas how-to get my phone back to life, or is it totaly dead? Answes appreciated =)
Click to expand...
Click to collapse
Are you flashing correct kernel check that first.
sent from HOV
powered by sphongle 4.2.2
Hmm... I'm pretty sure that I flashed right kernel, but now I can't get to fasboot screen. Only to ClockWork mod recovery. When I boot device, and press vol. down, and power, it always goes to recovery, or if I start to press those buttons a bit later, it only goes to that white HTC screen with red text. =(
E: After a while phone turns screen off, vibrates, and makes the screen again, so some kind of boot loop i guess?
Use the computer, turn it on normally and type in adb reboot bootloader
Sent from my HTC One V using xda app-developers app
mr_nooby said:
Use the computer, turn it on normally and type in adb reboot bootloader
Sent from my HTC One V using xda app-developers app
Click to expand...
Click to collapse
Thanks!
Was able to get it into fastboot. I flashed kernel and boot.img, those that came with shpongle. Then I did all the wipes and flashed the ROM. Still nothing. Goes into that same screen, and loops there.
Enpo said:
Thanks!
Was able to get it into fastboot. I flashed kernel and boot.img, those that came with shpongle. Then I did all the wipes and flashed the ROM. Still nothing. Goes into that same screen, and loops there.
Click to expand...
Click to collapse
flash this boot img as the one which comes with sphongle rom doesnt boot
http://www.mediafire.com/download/vj8vv8hjyhzg3xv/boot-HELLBOY-42-201305202359.img :good: :highfive:
I love you so much <3 :victory: :highfive: :good: No homo. Got it working. Thaks everyone *spams that "thanks" button*
Enpo said:
I love you so much <3 :victory: :highfive: :good: No homo. Got it working. Thaks everyone *spams that "thanks" button*
Click to expand...
Click to collapse
haha no problem!
I wish 1ce would post the correct kernel for his ROM
wud save a lot of questions