I rooted my phone last week, but I have only been able to access the recovery mode through the ADB script each time. I was able to install a custom ROM (he latest version of HaXpresso) and subsequently back it up, but now I cannot enter recovery mode at all. Even the ADB script method gives me an error message and will not progress beyond the triangle screen. I even tried superoneclick, which verifies the fact that my phone is rooted. I'm hoping to flash a different custom ROM but can't seem to figure out how.
Hi, long time lurker of the forums here, but not sure how much help I will be. If you're at the recovery triangle screen, try hitting the power button, maybe waiting a little bit before you do. Not sure why, but my Espresso sometimes gets stuck at the triangle screen ( the ClockwordMod one, not the red recovery one ), and pushing the power button gets the ClockwordMod menu to show.
Also, if you can still connect to the phone via adb, this ( Android Commander ) might help you in terms of flashing another ROM or something, but just make sure you know what you're doing, or probably wait until someone more knowledgable than me chimes in :
http://forum.xda-developers.com/showthread.php?t=1202893
Anyways, in case I didn't help, what method did you use to root your phone? If anyone can help, knowing that might help them... help.
Related
Hi,
I just got a Motorola Defy and rooted it, as well as removed some apps with titanium backup. I've been getting the message for the 3.6.360 update, and when I download and install it, it stops halfway and I get the screen with the white exclamation point in the yellow triangle. The phone then won't respond, but when I remove my battery I'm able to start it up again normally. I'm not really too familiar with the android os; I'm just starting to experiment with it. I tried unrooting and updating, but the same thing happens. I even tried following post #20 here: http://forum.xda-developers.com/showthread.php?t=931212&page=2 but the recovery app doesn't boot the phone into recovery mode. And powering on while holding the volume down (or up, I forget) doesn't take me to a recovery menu. Can someone please help me? Thank you
make sure usb debugging is off when you try to boot into recovery mode
That seems to have done something, but now it doesn't want to make a ROM backup. I don't think I have clockworksmod installed, but there's no version for the Defy. Is there one that still worksl? The only ones it says is Droid, Droid 2 and a third motorola phone
this version works with the defy used it my self http://forum.xda-developers.com/showthread.php?t=875233
I've tried it, but it gives me three options for the phone model. I clicked Milestone and it just got the exclamation mark again; Defy isn't there at all. How did you use it?
I think you are still trying to use the clockwork mod which is not what you want to use...if you are using the one that drops a menu down and shows milestone, droid x and droid 2 as options when you try to backup rom (I think those were the options), they you are using the wrong one. If you use tenfars system recovery app that the previous poster posted with link...you should be good as this app was custom made for the defy.
darule, will that app allow me to flash my firmware to install custom ROMs? I've been looking everywhere for answers but keep hitting dead ends
I s-offed, rooted & put cm7 stable on a friends Incredible. He got to messing with ROM Manager. I'm not sure what he tried to flash, but it screwed this phone up big time. He said something about a kernel & also about an update to recovery. I told him not to mess with it, but i guess he doesn't pay attention.
Here's what it doing. Boot loops on white HTC splash screen. Boot loader won't recognize any PB31IMG.img's. It scans to where it finds the .img, but does nothing. It boots to clockwork recovery, but if you select any of the options, it goes to a blank screen with just the clockwork background image. I get the remote:not allowed error when trying to flash recovery through fastboot even though it still says s-off.
What I've tried. Loading several PB31IMG's with no results, including the one with the same radio. I've also tried every recovery pb31img except stock. Nothing happens. Tried doing an ruu, but since the phone won't boot to the os, it never sees the phone as attached even in hboot. I have the hboot drivers installed. I've tried running the unrevoked reflash_package again, but it won't recognize it in hboot either. I think you have to start from the ROM for the software to work.
I'm guessing i am going to have to fix it with some adb or fastboot commands, but i would need some guidance here. I have it set up, but i have no idea on what commands to use. I have searched & read these forums & can't find anyone with a similar problem.
If anyone has any ideas or knows what to do, let me know. If you need bootloader info, let me know. I told him I would try to fix it, but no promises. I have never seen anything like this and have semi bricked many devices. The post about it not recognizing the ruu images baffles me. I owned an evo 4g, which is very similar to the incredible, so I'm not completely unfamiliar with the way it works. Any help would be appreciated. Thanks guys.
EDIT: NVMD! I figured out you have to use the trackpad to select anything in recovery instead of Power button. Sorry to waste your time. Have a great day!
CM powered EVO 3D, enough said.
I picked up the Galaxy Nexus from Verizon yesterday and attempted the unlocking and rooting procedure on droid-life.com. It looked like it was working, but now I can not get into recovery. When I try, I end up stuck on the screen with Andy and a red yield sign. I can get into the bootloader and run fastboot from my computer. The phone does still boot up completely.
I've seen posts about using Terminal Emulator and flash_image to restore the recovery, but Terminal Emulator says it can't find su. So something must have failed with the rooting.
Is there any information I can gather to help with this? Any help would be greatly appreciated. I'm out of ideas. My only other rooting experience was on my OG nearly two years ago and it went flawlessly.
Download the image in this thread and flash via fastboot. Make sure to delete /system/reboot-from-recovery.p afterwards.
Android screen with red exclamation point is the stock recovery image. Press power and either up or down volume to get into the recovery.
But yes, you'd want to flash clockwork mod like the guy above me said. Also rename or delete that file he wrote, otherwise on every boot, your recovery will go back to stock recovery.
Sent from my Galaxy Nexus
Oh. I hadn't found any documentation on the stock recovery so when I saw Andy open with a red yield and exclamation sign, I assumed it was bad. Thanks for the help!
EDIT: Got it thanks.
Hi, I'm having trouble booting after flashing the stock jelly bean rom 4.3 from tmobile. Right now it is just stuck on the Samsung logo. The problem may have been that I had installed the slimkat Kitkat rom and tried to go back to stock tmobile rom which was jelly bean. (stupid I know)
The second problem is that my volume up button is broken so I can't hold it long enough to boot into recovery. I am able to get into download mode and use odin if I get lucky and struggle with the up button but it only works in short bursts as it's damaged on the actual board and not the rocker.
Is there any other way I can get into recovery? I can't boot into the os so rebooting from there is out of the question. I'm running out of ideas now.
any suggestions would be greatly appreciated.
Flashing stock was fine. Your roms version doesnt matter, its your base firnware that does. Whenever you go between tw and non-tw roms you have to factory reset or itll hang at boot, which is what is happening to you.
Since you flashed stock, i dont know if itll work or not, but if ADB is set up on your computer, connect while in download mode, open command prompt and type
Adb devices
This will start the service and tell you if its detected.
Next type
Adb reboot recovery
If thats not going to work, youre going to need to find a way to make an odin flashable cm rom (not sure if you can), or get the the volume button fixed.
I dont know of any other way to boot recovery if you cant boot your rom as well.
DocHoliday77 said:
Flashing stock was fine. Your roms version doesnt matter, its your base firnware that does. Whenever you go between tw and non-tw roms you have to factory reset or itll hang at boot, which is what is happening to you.
Since you flashed stock, i dont know if itll work or not, but if ADB is set up on your computer, connect while in download mode, open command prompt and type
Adb devices
This will start the service and tell you if its detected.
Next type
Adb reboot recovery
If thats not going to work, youre going to need to find a way to make an odin flashable cm rom (not sure if you can), or get the the volume button fixed.
I dont know of any other way to boot recovery if you cant boot your rom as well.
Click to expand...
Click to collapse
Thanks for the reply, I do have ADB set up but unfortunately when running the command on adb it's not finding any devices. Odin finds it ok. I also have the android toolkit but it looks like it only works if the phone boots into the os..
Well I got it working now. Playing with a piece of tin foil around the volume up button finally let me hold it long enough to get into recovery. Wiping the cache got it all working properly again. thanks again.
Nice fix man!
As for adb, I figured it wouldn't work, but was worth a shot in case I was wrong. Pretty sure that it requires an insecure kernel since it didnt work though.
And just remember in the future, every time you switch between TWO and nonTW roms you have to factory reset. Glad you got it working!
Hi everyone,
I am currently trying to update my phone for the 5th time to Lollipop.
I have a rooted HTC One M8 with a custom flashed recovery (which I did ages ago, with the assist of a tutorial on youtube).
I think I need help trying to reflash the recovery back to stock, I tried to reflash the recovery myself but I still get the same red triangle w/ exclamation error. I am too much of a newbie with this stuff to fix it myself and I find myself in a place where I don't know how to update!! :crying:
Could anyone please link me to a guide on how to reflash the recovery to stock? I really have no idea what I am doing
Many thanks
You are rooted. The Lollipop OTAs check for any changes in /system, and root is definitely a change. Even if it wasn't, most of the stuff you would do as root will make a change. There are ways to get around that, but the easiest way is to unroot and see if that fixes it. If it doesn't, then RUU back to stock (or restore a backup that isn't rooted) and try it again.
I don't know what your skill level is, but the update will inform you which file it failed on if you really want to try to fix it. However, it can quickly become a massive PITA if you really use your root privileges.
gauzah said:
I think I need help trying to reflash the recovery back to stock, I tried to reflash the recovery myself but I still get the same red triangle w/ exclamation error.
Click to expand...
Click to collapse
That is stock recovery. You just need to press VOL UP button and POWER button to get into recovery when you see that screen.