Database Users

Recovery Mode Issue (stuck on warning Icon... Picture included)

I am at my wits end. I have unlocked and placed the CM zip file on my SD card. when i attempt to go into recovery mode i get this image and have to pull the battery to restart the phone. What in the world am i doing wrong. FYI when unlocking i accidentally hit the SimLock option, is that bad? I can get the phone to turn on and it seems to work, i just cant get into recovery mode so that i can put Cyanogens mod on.

jimtc said:
I am at my wits end. I have unlocked and placed the CM zip file on my SD card. when i attempt to go into recovery mode i get this image and have to pull the battery to restart the phone. What in the world am i doing wrong. FYI when unlocking i accidentally hit the SimLock option, is that bad? I can get the phone to turn on and it seems to work, i just cant get into recovery mode so that i can put Cyanogens mod on.
Click to expand...
Click to collapse
maybe u miss out a few steps ... go to unlockr.com and find the video tutorial for rooting the nexus one and installing recovery and rom

wrong forum... this shud be in Q&A... mods please move...
but btw, ur on the stock recovery.... u need to flash amon ra's recovery...

You still have the stock recovery image. Download the AmonRa recovery file and flash it your phone through fastboot.
This is the wrong forum for this, btw. Use Q&A next time.

Yep, get amon recovery put it into the same folder you put fastboot. Make sure you switch on debugging and turn your phone off. Connect your phone to usb and boot your phone into fastboot mode (power on while holding the trackball). Open up a command window in the fastboot folder (shift+right click) and type "fastboot flash recovery recovery-RA-nexus-v1.7.0.img". It should go, doesnt take long to flash. You can rename it recovery.img and use that, makes it easier to remember.

[Q] Cannot get to recovery with flashed clockwork (Bell D-Z Canada)

Edit: "Rom Development" is only meant for very advanced technical discussion directly related to ROM development activity and the delivery of actual ROMs and ROM components ONLY. Nothing else goes in here. Moved thread to "General." Please refer to "[REF] STOP! Read before posting!" ~TheRomMistress
Not able to get ROM manager to flash Clockwork for recovery. It shows successful but then when I reboot to recovery, it shows this image of red triangle over a cellphone, probably meaning recovery does not function.
Any ideas? I already have S-OFF done...

BriEE said:
Not able to get ROM manager to flash Clockwork for recovery. It shows successful but then when I reboot to recovery, it shows this image of red triangle over a cellphone, probably meaning recovery does not function.
Any ideas? I already have S-OFF done...
Click to expand...
Click to collapse
This is how I got it to work:
Step 1 - run Visionary R12 to get perm root.
Step 2 - Push the files from page 1 to phone via adb
./adb push [path to file]/wpthis-Z.ko /data/local/wpthis-Z.ko
./adb push [path to file]/hboot_7230_0.84.2000_100908.nb0 /data/local/hboot-eng.img
(as you can see above, I renamed the HBOOT file on the phone just to be consistent)
note: I'm not sure if you HAVE to put them in /data/local of if you can just run this from /sdcard - but I didn't want to experiment
Run the commands below as root via adb shell or from a terminal on your phone.
Step 3 -
insmod /data/local/wpthis-Z.ko
Step 4 -
dd if=/data/local/hboot-eng.img of=/dev/block/mmcblk0p18
Step 5 -
sync
Step 6 - Wait two minutes and then run clockwork and try to install recovery - do not reboot your phone.
Worked for me. Good luck.

I already have S-OFF and perm root though, why do it again?
So you're saying the WP isn't perm and neither is S-OFF? Is our root perm even lol?

Just reflash clockwork from rom manager. Same thing happened to me.

foxfire235 said:
Just reflash clockwork from rom manager. Same thing happened to me.
Click to expand...
Click to collapse
Same here, just reflash clockwork a second time and it should work.
Sent from my HTC Vision using XDA App

I had to flash CW twice as well. It seems successful after the first try but booting into recovery would show a black screen with a small phone icon.

codf4ther said:
I had to flash CW twice as well. It seems successful after the first try but booting into recovery would show a black screen with a small phone icon.
Click to expand...
Click to collapse
Did you just flash it twice, or did you follow the complete instructions twice?

[Q] fastboot - no boot or img file

hey guys i'm having some trouble. i just got the nexus (it's my first smartphone, ever) and i've tried to hit the ground running. here's what i've done to the phone so far.
i got all the drivers running on my win7 machine and also installed the android SDK folder onto C: as was described in this thread: http://forum.xda-developers.com/showthread.php?t=878786
i then unlocked the bootloader using the above guide as well. when I power on the phone using UP+POWER it says UNLOCKED.
I then proceeded to follow this guide: http://forum.xda-developers.com/showthread.php?t=875875
i used ADB to flash the clockwork crespo recovery. i then used fastboot to install Superuser.
at that point i had an unlocked bootloader, clockword recovery image and superuser permissions.
i then saw that the 2.3.1 update had been released. i wanted to learn how to tackle that so i started reading up. i noticed that people were using ROM Manager and Titanium. I got titanium and installed the BusyBox addon and it allowed me to do a full Batch Backup of all my programs, etc. i've got the 50MB or so backup folder on my PC now.
anyway, i then messed with Rom Manager. I installed the 3.0.0.0 ClockworkMod Recovery and everything went smoothly. now this is where my troubles begin.
when i go to Download ROM all i get is a Free Stuff area.
when i go to Check for ROM Updates it tells me my device isnt set up for OTA updates.
those are just minor issues.
this is the big and scary issue i have:
when i click on reboot to recovery, it takes me to the same screen that i go to when i power on with VOLUME UP+POWER. it doesnt take me to the recovery screen that i see in various youtube videos. instead, i'm at the main screen where it says UNLOCKED and i have 4 choices (reboot bootloader, recovery, reboot, power off). and on the very top in RED letters it says fastboot - no boot or img file. <-- this is the part that makes me nervous. If i manually power down the phone and boot to fastboot and click recovery, it just goes back to this same screen and says fastboot - no boot or img file. when i first rooted the phone, clicking recovery actually took me to a different screen where i was able to load up superuser.zip and install it.
did i accidetnally delete something that i wasnt supposed to? did installing ROM manager mess something up? i typically dont do anything until i confirm that i am supposed to. i think the problem is that i dont yet know how one thing i do on the phone affects another. i'm guessing when i used rom manager to update the CWmod it changed some folders/files? i dunno!
otherwise, the phone works fine and there are no glitches or hiccups or crashes. So if someone can please take a moment to just explain to me what i did wrong or what i failed to do i'd really, really appreciate it.

you don't have a recovery partition. Either flash one over manually using fastboot, or boot up and try to use ROM Manager to flash CWR.

when you say flash one over using fastboot, do you mean put my phone using VOLUME UP + POWER, connect usb cable, then use command line to do this:
fastboot flash recovery recovery-clockwork-crespo.img
?

kramer987 said:
when you say flash one over using fastboot, do you mean put my phone using VOLUME UP + POWER, connect usb cable, then use command line to do this:
fastboot flash recovery recovery-clockwork-crespo.img
?
Click to expand...
Click to collapse
yes, just follow the examples in http://forum.xda-developers.com/showthread.php?t=875875

kramer987 said:
when you say flash one over using fastboot, do you mean put my phone using VOLUME UP + POWER, connect usb cable, then use command line to do this:
fastboot flash recovery recovery-clockwork-crespo.img
?
Click to expand...
Click to collapse
Yes, 'cept it will be "fastboot flash recoveryrecovery-clockwork-3.0.0.0-crespo.img" without the quotes now.
But does it say that you're missing a boot.img or recovery.img?
Also, the "not set up for OTA" thing isn't for official OTAs. Some developers have made their custom ROMs capable of being updated that way.

unremarked said:
Yes, 'cept it will be "fastboot flash recoveryrecovery-clockwork-3.0.0.0-crespo.img" without the quotes now.
But does it say that you're missing a boot.img or recovery.img?
Also, the "not set up for OTA" thing isn't for official OTAs. Some developers have made their custom ROMs capable of being updated that way.
Click to expand...
Click to collapse
thank you luxferro and unremarked. i did it and it works perfectly. i am now able to access clockworkmod recovery 3.0.0.0. next step is backup my existing ROM and also to figure out how to put the OTA 2.3.1 on and restore all my data
oh and unremarked: it basically said no boot or img file and thats it after i would click on recovery or reboot to recovery trhough rom manager. it was just in red at the top. but now it takes me to the ClockworkMod Recovery

Bricked - Nexus S :(

OK first of all:
1 - I am a total noob
2 - Because of #1, I shouldnt have been doing this!
I unlocked my bootloader and was in the process of rooting my phone and when it booted up, I am stuck at the google screen with the unlocked lock at the bottom...any help here?
i CAN take out battery and load into the mode where I press volume up and power at the same time...if that helps.
When I do take out the battery, put it back in, then press the power and volume up buttons, then select recovery, I get a triangle with the "!" in it...dont know if that means anything to anyone or not.

When u get to the triangle part, Hold Power then press volume up. This will get you into recovery.
BUT you need to flash ( or re-flash) clockwork recovery via fast-boot ( follow the root guides) because looks like you didn't flash it.

Since you were attempting to root anyway, may I suggest you head over to the rooting guide, flash clockworkmod recovery and get a pre-rooted stock nandroid?

It lets me reboot the phone from there, but freezes on the google logo with the unlocked lock screen.

I cant seem to get the recovery img...like the link is bad....where else can i get it?

I googled and got the file, but when I type the command "fastboot flash recovery recovery.img" it says it cannot load "recovery.img" any help here?

chuckenfoot said:
I googled and got the file, but when I type the command "fastboot flash recovery recovery.img" it says it cannot load "recovery.img" any help here?
Click to expand...
Click to collapse
have android 2.3.X sdk set up properly? recovery.img needs to be in /sdk/tools/

zephiK said:
have android 2.3.X sdk set up properly? recovery.img needs to be in /sdk/tools/
Click to expand...
Click to collapse
Im sure I have it in the correct folder...what else?

wrong place
10char

Are you on a mac or a PC?
If you're on a mac I would suggest Kenvan19's rooting guide. It works great!

http://android.modaco.com/content/g...-colour-revert-superboot-rooting-the-nexus-s/
Chuckenfoot, Go to Paul's site Android Modaco see link above. I could'nt get fast boot commands to work and I almost gave up. His superboot method is absolutely the easiest method to get root and then you can install CWM. Follow his instructions and you'll be golden. Good Luck.

GFam4 said:
Chuckenfoot, Go to Paul's site Android Modaco see link above. I could'nt get fast boot commands to work and I almost gave up. His superboot method is absolutely the easiest method to get root and then you can install CWM. Follow his instructions and you'll be golden. Good Luck.
Click to expand...
Click to collapse
Superboot does make kernel modifications FYI. If you want to be completely stock and rooted so you can still get OTA superboot will prevent that.

Can't downgrade MT4G?

Hi all, I am going to be as thorough as I can. I am rather new, and I'm stuck trying to downgrade my MT4G to froyo (PD15IMG). I have read the tutorials, and learned enough about adb to attempt this task, but I think by doing the HTC Bootloader unlocking update last week, it may be the reason I'm stuck. I follow the instructions on the tutorial, to gain temp root, until I get to the part where I should get a "#" in the command Window when I type "adb shell" but I keep getting "$" instead, although everything seems to be going ok until I get to that point.
*Also, I put the PD15IMG.zip on the root of my sd card, and start my phone in bootloader mode, and it finds the PD15IMG.zip, and a blue progress bar appears in the top right corner of my phone for about 90 seconds, it then displays "parsing PD15IMG.zip" then stops at the hboot screen and does nothing. I just select power down, then power on my phone and nothing will have been done to my phone. I guess what I need to know is, by doing the HTC bootloader unlock update (which I did before I read that it was a bad idea), can I still downgrade and root with normal methods, or will I have to do something different?
Sent from my HTC Glacier using Tapatalk

You can start differently. Since you've unlocked the bootloader, try to flash recovery directly, by downloading recovery image directly from Clockworkmod site, rebooting to FASTBOOT (adb reboot bootloader) and using the command "fastboot flash recovery your_just_downloaded_recovery.img".
If recovery flash doesn't work for you - download the 2.2.1 PD15IMG, unzip it, and flash the following 2 files from it:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase userdata
Then reboot. You should end up on 2.2.1, which is perm-rootable using the guide (Visionary for temp-root, gfree for S-OFF, and then perm-root if you want).
Then flash the recovery and the engineering bootloader.

Here is what I did, I am giving a link to pastebin as instructed, it seems to go perfectly until I try to flash the StockRom. In the meantime I will attempt what was just posted above^^^^^^^ http://pastebin.com/fYrC6tAZ

One last thing before i have to throw away my phone. I couldnt leave well enough alone. I did this "fastboot flash boot boot.img" as you stated in the post above. It was successful. I then entered this one "fastboot flash system system.img", and it failed (said the img was too big or something) so I did the "fastboot-windows reboot" command and it is now stuck on the white HTC MyTouch 4g splashscreen. Is my phone toast? My PC no longer recognizes that my phone is connected to the USB port, however I can hold the volume dwn & power button and it comes on in the hboot mode.Is there any hope?
Also, when I boot it up by vol/dwn & pwr, the Hboot screen comes up and finds the PD15IMG that is on my sd card, goes through a 1 minute or so process (a blue status bar loads in top right corner), then it just stays on the hboot. It did that before it stuck on the splash screen, but never actually wrote anything i dont beleive.
OK its letting me use FASTBOOT and here is exactly what I got when i tried to flash the 2nd file in your post above. It came from the PD15IMG.zip as you instructed:
C:\adb>fastboot flash system system.img
sending 'system' (571388 KB)... FAILED (remote: data length is too large)
finished. total time: 0.016s

Can someone please let me know if there is hope for my phone? I can communicate with it through Fastboot (on my PC) and it will boot up in hboot mode. But it WON'T go past the Tmobile/MyTouch splash screen. If I get it fixed, I promise to never touch it again until I study! I truly feel there is hope, but I think don't know enough to figure it out. I loaded the PD15IMG on my SD, and it attempts to flash it, (a blue status bar appears in top right corner and fills up in about 90 seconds), but afterwards, it still sticks on splashscreen. Is there anything I can do to fix it? Anything I can flash it with in Fastboot? Please anyone?

You mixed 2 ways, and did it completely wrong way. And you didn't attempt to flash the recovery at all.
The first part, that went well (till ./flashgc), already prepared your phone for downgrading, and you should have recognized and understood it. You don't need anything else, no flashes from bootloader or anything. All you needed was to continue - put PD15IMG.ZIP on the SD card, reboot into bootloader, and let it downgrade.
You can still do it, so please do.
---------- Post added at 06:16 PM ---------- Previous post was at 06:13 PM ----------
Once you end up on 2.2.1, please follow the "Ultimate rooting guide" from Development section, and flash Engineering bootloader.

Jack_R1 said:
You mixed 2 ways, and did it completely wrong way. And you didn't attempt to flash the recovery at all.
The first part, that went well (till ./flashgc), already prepared your phone for downgrading, and you should have recognized and understood it. You don't need anything else, no flashes from bootloader or anything. All you needed was to continue - put PD15IMG.ZIP on the SD card, reboot into bootloader, and let it downgrade.
You can still do it, so please do.
---------- Post added at 06:16 PM ---------- Previous post was at 06:13 PM ----------
Once you end up on 2.2.1, please follow the "Ultimate rooting guide" from Development section, and flash Engineering bootloader.
Click to expand...
Click to collapse
Thank for your response. I have tried doing the PD15IMG.zip by booting my phone in bootloader mode. It finds the PD15IMG.zip and then a blue progress bar appears in the top right corner of the phone, finishes in about 90 seconds, the a message appears that says "wrong zip file". I would be happy just to get my phone back on with the gingerbread 2.3.4 on it, and simply leave it alone until I know what Im doing. Is there a way to just flash the original s/w back on it? If so if you could tell me how I will not mess with it again until I study alot more. But flashing the PD15IMG doesnt appear to be working for me.

Download the file again, and check MD5SUM on it before you use it.
If it responds "wrong ZIP" - it's because the ZIP is corrupted. When you'll download a good ZIP, it'll work.

Jack_R1 said:
Download the file again, and check MD5SUM on it before you use it.
If it responds "wrong ZIP" - it's because the ZIP is corrupted. When you'll download a good ZIP, it'll work.
Click to expand...
Click to collapse
Ok you were right, the one I had the wrong MD5SUM, but i d/l the correct one, it had the correct MD5SUM, but it still gave me the "wrong zip file error". I feel like there is hope, but I cant figure this out!! Thank you for trying, is there anything else I can do? I also tried going into recovery and doing factory reset/ data wipe etc...but it continues to get stuck on the splash screen....

How did you copy the correct one to the phone's SD card, and where did you put it? You either didn't copy it to your SD card, or named it wrong, or put it in wrong location, not overwriting the older file.
In any case, if flashing PD15IMG fails for you:
Download CWM recovery from here:
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-glacier.img
Boot to bootloader.
Enter FASTBOOT.
Execute:
fastboot flash recovery recovery-clockwork-5.0.2.0-glacier.img
Boot to recovery. You should have Clockworkmod.
Download a stock rooted 2.2.1 ROM from Development section.
Flash it in Clockworkmod recovery.
Extract boot.img from this ROM.
Flash it in fastboot, using "fastboot flash boot boot.img".
Boot into the ROM.
Proceed with gfree.

OK!! I got it fixed and it all makes sense to me now! I flashed the 2.2.1 boot.img to my phone, when it still had the 2.3.4 on it. It was as simple as that. I hadnt flashed the downgrade on it when I flashed the boot.img and I guess it was a mismatch. I read your last post to extract the "boot.img" from the rom and then it clicked! Yesterday I wrote the 2.2.1 boot img. to a phone that had 2.3.4...so I found a stock 2.3.4 rom, extracted the boot.img from it a BAM! its rolling again....thank you so much....

Yes, indeed, you flashed a mismatched, older kernel to your ROM. I was suggesting that you install custom recovery and change the ROM to match your boot.img, but the other way around also works - as long as you don't need to root your phone, that is.

Jack_R1 said:
Yes, indeed, you flashed a mismatched, older kernel to your ROM. I was suggesting that you install custom recovery and change the ROM to match your boot.img, but the other way around also works - as long as you don't need to root your phone, that is.
Click to expand...
Click to collapse
Well I will soon attempt it again, however I think I need to read a little more so I can understand the concept of what I am doing. I learned a ton by making that mistake. But as soo as I got it fixed, I couldnt resist, I used revovery and flashed [ROM]:: ProjectMIUI 2.2.17 [R6]- UPDATED 2/21/12 - [Stable + Smooth from the DEV section and I have never been happier with my phones performance! I will soon try the cyanmod, but I want to chill with this rom for a week or so. Again, I appreciate your help, I learned alot.

As long as you don't mind flashing kernels separately using fastboot for each ROM you flash, you can go indefinitely and flash ROMs as much as you like with your current setup, not needing anything else. The only good reason for you to go for S-OFF would be to flash Engineering HBOOT, to be able to flash kernels from recovery directly, avoiding extra fastboot step.
Also, thanks for finally confirming that you can flash recovery using fastboot on HTC-Dev-unlocked device. There was one device that didn't allow it (I think Incredible S, but not sure), so it's good to know that on MT4G it works as it should.