Hey,
I'm trying to flash a ROM on my phone and I'm currently running "Flashback 2.1" or whatever it is. When I try to reboot into recovery using the Volume +, I get a picture of the Eris with a red triangle/exclamation point.
So, my lovely Eris users, does anyone know what this means and how I can fix it, before I call Verizon and demand a new phone?
Thanks!
That is normal behavior for a stock phone - it is the "stock" recovery boot.
When that image is on the screen, press Vol-up+End (once more), and you will see the stock recovery menu.
You said you installed the "FlashBack21" ROM - which returns your phone to stock, including the recovery boot. (As it states in bold red print in that ROM's thread).
What you are seeing is stock behavior.
Time for you to root again - if that's what you are trying to do.
bftb0
PS: Here's what the different Eris Recovery "splash screens" have looked like over time
http://i756.photobucket.com/albums/xx209/erisuser1/recovery_boot/RecoverySplashComparison-small.jpg
I've tried what you said and I can't get it into recovery. I got it once, but I can't seem to get it again... Help?? Please.
queenybee8289 said:
I've tried what you said and I can't get it into recovery. I got it once, but I can't seem to get it again... Help?? Please.
Click to expand...
Click to collapse
Well, I only suggested that so you would see that there is nothing wrong with your phone. The "stock" recovery is of almost no use to you at all - you want a custom recovery (Amon_RA)
You need to re-root your phone, let's say using Jcase's "One Click" app. After doing that there will be a usable recovery available to you, from which you can flash other ROMs. (Again, the "FlashBack21" ROM UNROOTS a phone - returns it to factory software).
Thank you! I apologize for the blond moment I'm not a noob, I swear.
queenybee8289 said:
Hey,
I'm trying to flash a ROM on my phone and I'm currently running "Flashback 2.1" or whatever it is. When I try to reboot into recovery using the Volume +, I get a picture of the Eris with a red triangle/exclamation point.
So, my lovely Eris users, does anyone know what this means and how I can fix it, before I call Verizon and demand a new phone?
Thanks!
Click to expand...
Click to collapse
/facepalm
Flashback 2.1 is not a rom, it's a zip that when you flash it, it unroots you and sends you back to stock. Reroot with the one click root apk and flash a rom. You'll be fine.
Related
Tuesday night I loaded CM7, and then the Market wouldn't update my apps so I decided I would restore BAMF 1.5. After doing so, the Market just gave me "Fails" trying to update, and I could not access recovery, as I was going to do a complete wipe and reflash. Most of Wednesday, an extremely helpful & knowledgable member, Mattgyver83, tried diligently to help me rectify the situation, but to no avail. We tried to Fastboot, tried flash_image, tried fix permissions...shoot, I practically wore out adb..anyway, I ended up reverting back to stock and unrooted. I used jcase's method to revert back to stock, and that was painless, and successful. I decided last night to try rooting again, thinking a fresh root would solve my issue of not being able to access recovery. Root was successful, but I still cannot access recovery, through rom manager, or through bootloader. When I attempt it my Tbolt goes to white HTC screen, and stays there. All functions of my phone now work, and all aspects of root work, except I cannot flash anything. Rom manager shows I have clockwork recovery, but I just can't get to it.
Sorry for the long ramble. If anyone has had this issue, or if anyone knows a fix, I would appreciate it. Otherwise, I wait for Gingerbread.
Thanks
Happened to me with CM7 builds. For some reason they were erasing the recovery. Just have to reflash the recovery in Rom Manager and you'll be all set in the future.
do what i do pull batt leave out for a min, then put the batt back in and connect usb right away.
travishamockery said:
Happened to me with CM7 builds. For some reason they were erasing the recovery. Just have to reflash the recovery in Rom Manager and you'll be all set in the future.
Click to expand...
Click to collapse
Tried that, but thanks. Still just goes to white HTC screen, and stays there until I do battery pull.
jr4000watts said:
do what i do pull batt leave out for a min, then put the batt back in and connect usb right away.
Click to expand...
Click to collapse
I can get to bootloader, just not able to get into recovery.
I'm stabbing in the dark at this, but this did work for me with my Droid...
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Ie. Flash recovery and wait until the confirmation pop-up/message only takes a few seconds to pop up. If the message takes longer than 5 seconds or so, re-flash recovery and repeat until the confirmation comes up quickly.
This sounded retarded to me, but I was at the end of my rope so I tried it. It worked like a charm.
M.
monolithic said:
I'm stabbing in the dark at this, but this did work for me with my Droid...
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Ie. Flash recovery and wait until the confirmation pop-up/message only takes a few seconds to pop up. If the message takes longer than 5 seconds or so, re-flash recovery and repeat until the confirmation comes up quickly.
This sounded retarded to me, but I was at the end of my rope so I tried it. It worked like a charm.
M.
Click to expand...
Click to collapse
Thanks, but that didn't work. I think something in my os got lost when I restored BAMF from CM7.
Yea I spent a good few hours yesterday trying to help Orio out and we attempted a ton of things to try and fix the recovery issue, this post should offer a bit more insight to the methods used, this is running off memory;
adb reboot recovery failed
Reinstall latest Rom Manager apk and Flash CWM
flash latest rom manager via fastboot (CWM only)
(fastboot flash recovery /sdcard/recovery-clockwork-3.0.2.5.img)
**did not do fastboot erase recovery first**
"return to stock safely and properly" XDAthread by jcase
return to stock image [RUU], reroot, try again
try to boot into recovery via hboot
manually installed fix_permissions.sh script and busybox on rooted stock, ran.. didnt fix
tried to see if flash_image method would work, didn't
All of the above have failed and we basically tried almost all combinations. Not once would this phone get back into recovery, even after flashing the appropriate RUUs which include either stock android or CWM recovery. The only thing we have not currently attempted which might be the last thing left is to do is manually install the nandroid.sh script and do an advanced restore of the recovery image only from a nandroid backup on SD. I would rather not go down this method as it could have an undesired result, I have done it to restore a G1 back in the day but not 100% if its gonna work on a tbolt. Thankfully his phone boots, and we can get into hboot, but yea.. pretend recovery just doesnt exist at all...
Curious if anyone has any knowledge above what we have already tried.
monolithic said:
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Click to expand...
Click to collapse
I recall the same thing and its a good thought however that was mostly a generic error due to a CWM update and CM6 (I think) but either way flashing an RUU should override this shortcoming and im pretty sure that issue was worked out in CWM as well.
Not to be rude, but I don't think this question belongs in the development section.
Orio56 said:
I can get to bootloader, just not able to get into recovery.
Click to expand...
Click to collapse
do you still have the P zip file for the radio (baseband) on your SD card? if you do....try to delete it...then hold power and volume down button down....then see if you can get into recovery....
probably not going to work...but it is worth a try......
hogowner said:
do you still have the P zip file for the radio (baseband) on your SD card? if you do....try to delete it...then hold power and volume down button down....then see if you can get into recovery....
probably not going to work...but it is worth a try......
Click to expand...
Click to collapse
Thanks, but no, I deleted that after loading it. I actually reverted back to stock/unrooted last night and rerooted and the problem still remains. It's quite strange.
maybe i missed it if someone suggested this but what about flashing an older version of CWM?
shelooga said:
maybe i missed it if someone suggested this but what about flashing an older version of CWM?
Click to expand...
Click to collapse
That is what I was going to suggest. In ROM Manager at the very bottom try and flash an older version.
Sent from my ADR6400L using XDA Premium App
SUCCESS !!!
I fixed it !
Apparently, when I loaded up cm7, files showed up about the same time on my sdcard in clockworkmod download file. I deleted those files, and reflashed clockworkmod in rom manager, (which this time took like 3 - 4 minutes), and rebooted into recovery and it worked...did it again, just in case it was a fluke and it worked.
All is well now...the planets are realigned !!!
Thanks everyone for your ideas and especially thanks to mattgyver83 who helped me for something like 4 hours yesterday. Exceptional kindness !!
mods...you can close this thread.
GREAT NEWS!!!! CONGRATULATIONS!!
THANKS FOR REPORTING BACK!
This may help out other members with the same problem!!
now go ahead and start playing with your T-BOLT again!
That's a very odd solution. My first two things to try would have been:
1) fastboot:
fastboot erase recovery
fastboot flash recovery C:\some\local\path\recovery.img
You can't, well, probably shouldn't, flash a recovery from the /sdcard. When in fastboot mode I don't think the sdcard is even mounted. Either way, I think fastboot needs the img file on the local file system.
2) Create a PG05IMG.zip file with the recovery.img file in it, and flash that through HBOOT. Although this should have been done in some form or fashion when you downgraded or re-rooted, so YMMV.
i have a atrix and cannot for the life of me get the following rom to load. [ROM] CM7 Mod ICS FINAL I have followed several different installation instructions but after loading the main file, the google updates, and fixes, have i been able to reboot. It just hangs at the screen that says unlocked.
I have used rsd lite to reload the latest stock file and the phone returns to its normal unrooted self.
What could i be doing incorrectly.
If anyone knows or has a FOOLproof method for installing this rom any help would be appreciated.
I never used to have any trouble changing roms on my TILT phone.
I have tried for several days to get this to work. any expertise would be most appreciated.
So you unlocked your bootloader and you are using the latest cwm recovery?
questions
first off, thanks for replying.
I beleive i am using the current of both.
just in case i am not could you tell me the most current boot unlocker and where what and how on the cdm recovery. i must be doing something a little wrong in these 2 areas, everything else seems very straight forward.
mgoforth said:
first off, thanks for replying.
I beleive i am using the current of both.
just in case i am not could you tell me the most current boot unlocker and where what and how on the cdm recovery. i must be doing something a little wrong in these 2 areas, everything else seems very straight forward.
Click to expand...
Click to collapse
Well if you have "unlocked" when you start up your phone your bootloader is unlocked. If that's the case then go ahead and download "Rom manager" from the market and flash it from there.
Hello all,
I have a question that has not been answered after many hours of searching. Hopefully I'm just dumb, and my buddy's stock firmware and data isn't hosed. I'm trying to get his stock firmware running again so I can back it up safely.
What I've done:
Tried to flash CWM's update.zip via stock recovery (signature verification failed on the three different zip's I could find in the forums and various links)
Used Heimdall to push "cmenard-T959-CWM" zImage (this worked, and I get a different screen at boot)
The phone boots to the point of the T-Mobile splash screen with the annoying shriek sound, but goes to a black screen after. If i touch any of the soft buttons, they light up and remain lit. It'll stay like that for at least 20 minutes.
Is it possible to re-flash the system partition and not the data partitions using ODIN? Is that even feasible? Like I mentioned above, I'd like to get the stock firmware running such that I can make a good backup of it with all the user data intact. I haven't been able to because the CWM+root wouldn't flash.
Any suggestions or insight would be greatly appreciated.
thanks in advance!
Well as long as you don't format the internal SD, any pictures and videos and things should remain intact.
Here is a similar thread. See if it resembles your issue.
http://forum.xda-developers.com/archive/index.php/t-794869.html
Toast6977 said:
Well as long as you don't format the internal SD, any pictures and videos and things should remain intact.
Here is a similar thread. See if it resembles your issue.
http://forum.xda-developers.com/archive/index.php/t-794869.html
Click to expand...
Click to collapse
Thanks for the suggestion, Toast. I don't believe the internal SD has been messed with, and I don't plan to mess with it either. The thread you linked is not quite related to my issue, as far as I can tell.
I am able to get into Download Mode, and the Stock Recovery mode as well. However every time I try to flash an 'update.zip' with the Stock Recovery, I get an error about Signature Verification Failure.
After stepping back from it for a day, I think I've gained some clarity. Since all I've done is flash a different Kernel with Heimdall, I'm going to try to flash a stock kernel then see what happens.
Is this phone on stock Froyo or have you got it back to JFD (eclair)?
If Froyo, that's the problem. Using Odin back to Eclair and run update.zip. It won't work from stock Froyo.
*-*- I made some assumptions in my previous post. The shrieking sound. Black screen. Lights stay lit. Sounded like a poltergeist.
Glad you can get in download mode and recovery.
The old 2E vs 3E problem. Nice catch Toast
Give this a whirl: recovery 3e modified to work like recovery 2e
Might have to ABD push it to your internal SD card though.
Toast6977 said:
Is this phone on stock Froyo or have you got it back to JFD (eclair)?
If Froyo, that's the problem. Using Odin back to Eclair and run update.zip. It won't work from stock Froyo.
*-*- I made some assumptions in my previous post. The shrieking sound. Black screen. Lights stay lit. Sounded like a poltergeist.
Glad you can get in download mode and recovery.
Click to expand...
Click to collapse
Woodrube said:
The old 2E vs 3E problem. Nice catch Toast
Give this a whirl: recovery 3e modified to work like recovery 2e
Might have to ABD push it to your internal SD card though.
Click to expand...
Click to collapse
hahaha poltergeist!
Wow, so I'm glad I asked. I wouldn't have known about this issue, as I do not have any history with this device.
I know that the ROM is currently 2.2, and the Android System Recovery is showing "3e".
If I understand correctly, once I'm ready to flash up to ICS, I'll need to ODIN back to 2.1 to get Android System Recovery "2e", which will let me flash 'update.zip' packages freely. Then I flash an 'update.zip' to get CWM, then flash CM7, then CM9 (and CM9 is my intended destination).
The things mentioned in the thread you linked do appear to apply to my situation.
However I still want to get the stock OS booted and working, then do a Nandroid backup of it. (it's the computer tech/security pro in me. Since I'm new to this device, I -tried- to read up on everything first, and didn't want to make a change without being sure it would work.)
Does anyone happen to know if flashing a stock kernel over the 'cmenard' kernel will harm anything, and hopefully get a successful boot? Again, I'm trying to get the stock ROM booting again in order to verify I have everything I need off of it, then do a nandroid backup. Flashing to CM9 will come afterwards.
Ok, here are some things for you.
Here is a kernel pack that you can use. Read the OP because there are Froyo AND Gingerbread kernels in there.
[KERNELS] Moped_Ryder SGS Kernel Pack v2 [20+ Froyo/GB Kernels]
I really suggest using something like BaliX 1.2 or BaliUV kernels to make your back up. They are smooth, fast and OC/UV-able. To flash just Wipe /cache, /dalvik -> flash kernel -> Wipe /cache, /dalvik (I also fix permissions too bc that is the way that I learned and I just do it that way all the time). Reboot and Bam!! you should be able to get to the point that you can make a backup.
Look in my signature, there are downloads and flashables that are direct download linked. There is also an ICS install guide that can help your journey. Once you have your backup, then use Odin from the Toolbox in my signature and flash back to stock JFD. From there you will be able to follow my guide.
If you need any files, just let me know and I will upload them when I get home (won't be until late though, i have plans right after work).
Using HB, can I choose any theme? I am not so acquainted with the Theme chooser and boot animation of my phone. I flashed a boot animation zip yesterday and it was stuck in "ANDROID" screen. So I have to flash again. I never used any boot animation and themes in my phone yet. I want to know about them.
Sent from my SGH-T959 using xda app-developers app
Wrong thread. Put that question in the Jelly Bean Banter thread. No need to hijack this thread until we get OP up and running.
Ugh, so I've been on vacation for a while, and since being back I've been super freaking busy =(
Finally spent some time with the phone tonight. Took some fiddling to get the right drivers working for the phone on my Win7x64 laptop.
In any case, I checked out that Kernel thread, and extracted the Bali kernel. Since I had flashed successfully(?) with Heimdall at first, and I'm becoming more familiar with it, I used it to flash the Bali_1.8.8-zImage. That appeared to work, as I get a new boot screen/animation with the Bali logo.
However, after the Bali logo disappears, the T-Mobile animation+sound plays, and then gives me a black screen. The screen is on (backlight is on) but all black. Also, if I touch a soft-button, they'll light up and the phone will remain in that state for as long as I can stand to wait. (one episode of Archer)
So, it's doing the same thing as before, but with a new boot logo/animation.
I wonder if something else in the ROM has been messed up? Should I forget trying to save it, and just use ODIN to flash a whole new rom/kernel package? I'll talk to the owner tomorrow and see if he's now willing to do that.
I also wonder if I was wrong to use Heimdall again, instead of using the CWM method. Please correct me if I'm wrong, but I think those two methods end up doing the exact same thing. Is one method more reliable than the other?
Bah, this sucks; I have more questions than answers at this point =( Any ideas, Woodrube, Toast?
maxpeet said:
Ugh, so I've been on vacation for a while, and since being back I've been super freaking busy =(
Finally spent some time with the phone tonight. Took some fiddling to get the right drivers working for the phone on my Win7x64 laptop.
In any case, I checked out that Kernel thread, and extracted the Bali kernel. Since I had flashed successfully(?) with Heimdall at first, and I'm becoming more familiar with it, I used it to flash the Bali_1.8.8-zImage. That appeared to work, as I get a new boot screen/animation with the Bali logo.
However, after the Bali logo disappears, the T-Mobile animation+sound plays, and then gives me a black screen. The screen is on (backlight is on) but all black. Also, if I touch a soft-button, they'll light up and the phone will remain in that state for as long as I can stand to wait. (one episode of Archer)
So, it's doing the same thing as before, but with a new boot logo/animation.
I wonder if something else in the ROM has been messed up? Should I forget trying to save it, and just use ODIN to flash a whole new rom/kernel package? I'll talk to the owner tomorrow and see if he's now willing to do that.
I also wonder if I was wrong to use Heimdall again, instead of using the CWM method. Please correct me if I'm wrong, but I think those two methods end up doing the exact same thing. Is one method more reliable than the other?
Bah, this sucks; I have more questions than answers at this point =( Any ideas, Woodrube, Toast?
Click to expand...
Click to collapse
Wrong they are not the same. cwm can do the work without a PC beside you can erase, back up , restore and flash, which make our life easier, heimdall or Odin ," I prefer odin "are the last option when you can't fix it with cwm
To fix your phone use Odin or heimdall and go back to stock don't worry all your files, photo, music, will be safe. Then
1 get root on you , if you don't how ask
2 get cWm
3 do a nandroid back up
4 have fun flashing all roms you want lol
Sent from my SGH-T989 using xda app-developers app
Yeah, I would just Odin back to stock JFD w/ repartition checked...
Then I'd flash something real stable for him. There are lots of stable ROMs to choose from. I used Bionix V for a long time before moving onto Jelly Bean.
Since the phone belongs to someone else, I'd stick with something lower than JB though. 911 can have/has issues.
Toast6977 said:
Yeah, I would just Odin back to stock JFD w/ repartition checked...
Then I'd flash something real stable for him. There are lots of stable ROMs to choose from. I used Bionix V for a long time before moving onto Jelly Bean.
Since the phone belongs to someone else, I'd stick with something lower than JB though. 911 can have/has issues.
Click to expand...
Click to collapse
do no check de re-partition button and use a .pit file follow this tutorial and you will be fine
http://forum.xda-developers.com/showthread.php?t=848737
I have the HTC One X Plus International and recently recovered from it only being able to go into Bootloader Mode because of the System being erased without a backup. I finally was able to learn how to find the correct RUU for my make and model to bring it back to life. Before accomplishing this, this current problem still existed.
Each time now when I boot-up, it starts perfectly well, no problem. But when I try going into Bootloader Mode and choose Recovery, it shuts itself down. So, since I am unable to Root it, or at least I don't know how to do so under these circumstances, how do I get around this obstacle? Thanks.
Jussi31 said:
I have the HTC One X Plus International and recently recovered from it only being able to go into Bootloader Mode because of the System being erased without a backup. I finally was able to learn how to find the correct RUU for my make and model to bring it back to life. Before accomplishing this, this current problem still existed.
Each time now when I boot-up, it starts perfectly well, no problem. But when I try going into Bootloader Mode and choose Recovery, it shuts itself down. So, since I am unable to Root it, or at least I don't know how to do so under these circumstances, how do I get around this obstacle? Thanks.
Click to expand...
Click to collapse
I don't know if this is too obvious.. but have you flashed the recovery again??
When you run the RUU, it is overwritten. You need to download a recovery and flash it through fastboot:
fastboot flash recovery recovery.img
Actually, around six or seven times now, with no luck. Now when attempting to get into Recovery, it hangs on the white screen. The thing is, I successfully had TWRP 2.5.0.0 on it. (Long story.) I am now trying to figure out how to root it through Fastboot, if that's even possible. Otherwise, I am out of ideas.
Through trial-and-error, I finally was able to get it rooted. However, no matter how many times I try flashing TWRP-Touch (various versions), it maintains its inability to boot into Recovery Mode. Go figure.
I use twrp venom without any issues, maybe try that one?
http://forum.xda-developers.com/showthread.php?p=37300312
Sent from my Viper One X+
Oh wow, it actually worked! God love you. Thanks much.
No problem
Sent from my Viper One X+
When you were hanging on the white screen, did it say anything on the screen?
I can't recite it exactly, HTC, something. But know that it is the first screen you would see upon rebooting.
Update
00mpollard said:
No problem
Sent from my Viper One X+
Click to expand...
Click to collapse
Hey 00mpollard, I just wanted to thank you for both recommending a working Recovery IMG (that works great) for my HTC One+, and as well as introducing me to the corresponding Viper One X+ ROM, that I also decided to install, and I couldn't be happier. Thanks again.
No problem, glad i could help!
I love Viper rom, very stable & lots of customizations Can't go wrong!
Jussi31 said:
I can't recite it exactly, HTC, something. But know that it is the first screen you would see upon rebooting.
Click to expand...
Click to collapse
I was just curious because if it said something about waiting on SD card or SDdata, something along those lines, I get that issue when the phone is plugged in. Unplugging the cable allowed me to enter hboot with no issues.
Hi guys I need some urgent help. I'm wanting to go back to stock recovery so I can install OTA updates when they are available. I made the mistake of rooting my phone without thinking about updates. I just want it back to stock so it's all nice and easy to use and I don't need to worry. I've found this thread which contains the stock recoverys but when I try and flash the STOCK RECOVERY 1.54.206.5 file I can't even into recovery and just got a error symbol up.
My phone is on the o2 network (I'm in the UK) and my phone is 4.4.2 Software number 1.54.206.5. Am I right in thinking it is that file I need?
If someone could take 5 minutes of their time to help me out it would be ever so much appreciated
EDIT - When Ive sent the stock recovery and I go to boot into it the symbol is a phone with a warning sign. Is that just what it is suppose to do or is it because it's wrong? I read on the thread "You can test originals by flashing them. If you see a phone with warning sign it's the HTC original one."
PLEASE HELP!
Nah, that's how it looks stock. You have to play around with some of the buttons to get the reset and reboot options to pop up. I can never remember what to do exactly. Try hitting the the Volume Up + Power on that screen. But I don't think they change the recovery much if at all between updates.
es0tericcha0s said:
Nah, that's how it looks stock. You have to play around with some of the buttons to get the reset and reboot options to pop up. I can never remember what to do exactly. Try hitting the the Volume Up + Power on that screen. But I don't think they change the recovery much if at all between updates.
Click to expand...
Click to collapse
Ohh yes brilliant! . I panicked and thought it meant it couldn't find a suitable recovery to boot into. It's all sorted now and hopefully I will have no problem installing OTA updates when they become available. Thank you
No problem. Glad all is well.