Related
Sorry if this seems a bit stupid, I'm new to android and rooting phones. Anyhow, I'm desperatly in need of help!
I successfully followed the root guide for the desire and got the basic rom on from Modaco (Paul's guide). I then thought it would be fun to try out some of the other roms so gave Pays rom a go but couldn't get this to boot.
I did the changing of the partitions on the SD card tried doing this before and after, still no boot.
Done various other things since but now can't get my phone to be recognised by my PC when in recovery mode. When I go into the boot menu, the USB is picked up but when I go to recovery, it isn't.
I've tried running through the rooting process again to apply the stock rom but I can only do the first bit but when I try to run the windows step2 bit, it says error device not found.
I've been looking at the guide on modaco for unbricking your phone and I cant see how do to the following step:
"Enable the SD Card functionality. Boot your phone in FASTBOOT mode (back + power), and enter this command: 'fastboot oem enableqxdm 0' . This will re-enable your SD card."
I can go into fastboot, that's fine... but how do I enter the command in fastboot? There is no command prompt or text entry method?
Am I being very stupid? Please, can someone help me!!!!!!!
jaketurbo said:
Sorry if this seems a bit stupid, I'm new to android and rooting phones. Anyhow, I'm desperatly in need of help!
I successfully followed the root guide for the desire and got the basic rom on from Modaco (Paul's guide). I then thought it would be fun to try out some of the other roms so gave Pays rom a go but couldn't get this to boot.
I did the changing of the partitions on the SD card tried doing this before and after, still no boot.
Done various other things since but now can't get my phone to be recognised by my PC when in recovery mode. When I go into the boot menu, the USB is picked up but when I go to recovery, it isn't.
I've tried running through the rooting process again to apply the stock rom but I can only do the first bit but when I try to run the windows step2 bit, it says error device not found.
I've been looking at the guide on modaco for unbricking your phone and I cant see how do to the following step:
"Enable the SD Card functionality. Boot your phone in FASTBOOT mode (back + power), and enter this command: 'fastboot oem enableqxdm 0' . This will re-enable your SD card."
I can go into fastboot, that's fine... but how do I enter the command in fastboot? There is no command prompt or text entry method?
Am I being very stupid? Please, can someone help me!!!!!!!
Click to expand...
Click to collapse
You need ADB-SDK
Open a cmd [tools/commandline here] at the tools-dir you will find there and you will be able to execute de fastboot commands. Youre phone has to be connected to youre pc in the fastboot-modus.
Thanks for the quick reply. I'll give that a go now
I struggled with the guide on Modaco, as it's rather vague, so when I finally figured it out I wrote down ALL the steps you have to take, and this is what I ended up with:
To Un-USB Brick HTC Desire:
1. Hold down the back button, and then turn on your Desire
2. Make sure the screen shows FASTBOOT. If it doesn’t, choose it from the options available
3. In command prompt go to the folder on your computer where you downloaded and extracted the Android SDK to
4. At the command prompt type ‘fastboot oem boot’
5. If you know that you don’t have access to the SD card when your phone loads up, also type the command ‘ fastboot oem enable qxdm 0’
6. The bit you need from the information displayed in the CID. Look for something like ‘INFOCID is O2___001’. In this case, my CID is ‘O2___001’
7. On your phone go to Settings>About phone>Software Information and note your Software Number. Mine was 1.21.405.1
8. Now turn off the phone and take the SD card out and put it in your computer
9. Go to http://ks33673.kimsufi.com/misc/ and put in the details from steps 6 & 7.
10. Download the file it creates
11. Get the flash image from http://www.shadowchild.nl/flash_image
12. Put both of these on the SD card
13. Put the SD Card back in your Desire and turn it on
14. Go to the Market and download a terminal emulator. I used ConnectBot
15. Run Connectbot. In the bottom left corner where it says ‘ssh’ click on the triangle. Choose ‘locall and put in anything for your nickname.
16. Now enter the following commands EXACTLY as they are shown below, pressing enter after each one
17. su
18. cat /sdcard/flash_image > /data/flash_image
19. cat /sdcard/mtd0.img > /data/mtd0.img
20. chmod 755 /data/flash_image
21. /data/flash_image misc /data/mtd0.img
22. Reboot your Desire, and it should all work again!
AWESOME
Thanks guys,
sorted now... been a while since I did anything with unix/linux commands as well
Now I just need to figure out when I flash the custom roms, why they don't boot.
When you flash the roms are you doing a full wipe?
I suggest backing up your sd to your pc and then wiping your sd fully just as a precaution.
Then before you flash a rom, from recovery make sure you go down the full list of wipe options. Wipe data, cache, ext (if you have one but shouldn't after wiping sd) etc...
some de-odexed roms like pays take a long time for the first boot (up to 10mins) you just have to be patient
chippieuk said:
I struggled with the guide on Modaco, as it's rather vague, so when I finally figured it out I wrote down ALL the steps you have to take, and this is what I ended up with:
To Un-USB Brick HTC Desire:
1. Hold down the back button, and then turn on your Desire
2. Make sure the screen shows FASTBOOT. If it doesn’t, choose it from the options available
3. In command prompt go to the folder on your computer where you downloaded and extracted the Android SDK to
4. At the command prompt type ‘fastboot oem boot’
5. If you know that you don’t have access to the SD card when your phone loads up, also type the command ‘ fastboot oem enable qxdm 0’
6. The bit you need from the information displayed in the CID. Look for something like ‘INFOCID is O2___001’. In this case, my CID is ‘O2___001’
7. On your phone go to Settings>About phone>Software Information and note your Software Number. Mine was 1.21.405.1
8. Now turn off the phone and take the SD card out and put it in your computer
9. Go to and put in the details from steps 6 & 7.
10. Download the file it creates
11. Get the flash image from
12. Put both of these on the SD card
13. Put the SD Card back in your Desire and turn it on
14. Go to the Market and download a terminal emulator. I used ConnectBot
15. Run Connectbot. In the bottom left corner where it says ‘ssh’ click on the triangle. Choose ‘locall and put in anything for your nickname.
16. Now enter the following commands EXACTLY as they are shown below, pressing enter after each one
17. su
18. cat /sdcard/flash_image > /data/flash_image
19. cat /sdcard/mtd0.img > /data/mtd0.img
20. chmod 755 /data/flash_image
21. /data/flash_image misc /data/mtd0.img
22. Reboot your Desire, and it should all work again!
Click to expand...
Click to collapse
Ok, I've bricked my Desire so my pc no longer recognizes it and the phone can't see the SD card.
I know i have to do the ‘fastboot oem boot’ part but how??
My PC doesn't recognize the phone, at the moment i've got android 1.0 in the Android USB devices with the yellow problem sign against it as the driver/software never loaded when connecting the phone.
I've tried running the Fastboot file from SDK but the screen just flashes up then disappears, so basically I can't get the command prompt up to run step 4 in the above post.
Any suggestions?
Cheers
celticone said:
Ok, I've bricked my Desire so my pc no longer recognizes it and the phone can't see the SD card.
I know i have to do the ‘fastboot oem boot’ part but how??
My PC doesn't recognize the phone, at the moment i've got android 1.0 in the Android USB devices with the yellow problem sign against it as the driver/software never loaded when connecting the phone.
I've tried running the Fastboot file from SDK but the screen just flashes up then disappears, so basically I can't get the command prompt up to run step 4 in the above post.
Any suggestions?
Cheers
Click to expand...
Click to collapse
Further to my post above, I've used cmd in windows to run the flashboot command but it comes up with waiting for device and still waiting after 5 mins. I guess as the PC can't recognize it as a device commnd prompt won't ever work??
Fantastic tutorial!! because it really works!!
Dear All,
I had my HTC Desire Bricked....
I follow all steps of the tutorial and it unbrick my HTC Desire!
thank you so much!!
Greetzzz
AndroidJunk
celticone said:
Further to my post above, I've used cmd in windows to run the flashboot command but it comes up with waiting for device and still waiting after 5 mins. I guess as the PC can't recognize it as a device commnd prompt won't ever work??
Click to expand...
Click to collapse
Try fiddling with when you plug in your USB-cable... that did the trick for me...
Will this work for a Legend???
Does these steps work for HTC Legend aswell?
After installing a custom rom,
I cannot access USB, SD or SIM.
This Guide creates a big moment 22 for me.
I asume im bricked however i have seriously 0 idea how it hapened. After a reboot i could no longer access the SD card, the SIM did not read and the USB could not be connected to the PC. Ive tried with diffrent SD cards and SIM cards without anny progess.
So this guide asumes that this will help:
5. If you know that you don’t have access to the SD card when your phone loads up, also type the command ‘ fastboot oem enable qxdm 0’
But it doesnt. It only gives me the error message:
... INFOR[ERR] Command error !!!
in CMD.
So, i cant use my SD card(it works on the comp but not on phone) And thats that.. what the f*ck do i do?
Edit: Besides,
7. On your phone go to Settings>About phone>Software Information and note your Software Number. Mine was 1.21.405.1
This doesnt aply to me since im running a custom rom and not a stock rom. (And no i cant install a RUU due to the computor not even noticing the phone).
Edit2: Acording to:
http://android.modaco.com/content/h...com/309939/usb-brick-rickrolled-b0rked-fixed/
The command is
fastboot oem enableqxdm 0
not
fastboot oem enable qxdm 0
Wich resulted in a successfull Command but the SD card can still not be read.
The bit I don't get.. (not that I need to do this), but there is no file/executable named fastboot in the dir of the tools directory on the linux sdk. how does it work?
Sajhe said:
This Guide creates a big moment 22 for me.
I asume im bricked however i have seriously 0 idea how it hapened. After a reboot i could no longer access the SD card, the SIM did not read and the USB could not be connected to the PC. Ive tried with diffrent SD cards and SIM cards without anny progess.
So this guide asumes that this will help:
5. If you know that you don’t have access to the SD card when your phone loads up, also type the command ‘ fastboot oem enable qxdm 0’
But it doesnt. It only gives me the error message:
... INFOR[ERR] Command error !!!
in CMD.
So, i cant use my SD card(it works on the comp but not on phone) And thats that.. what the f*ck do i do?
Edit: Besides,
7. On your phone go to Settings>About phone>Software Information and note your Software Number. Mine was 1.21.405.1
This doesnt aply to me since im running a custom rom and not a stock rom. (And no i cant install a RUU due to the computor not even noticing the phone).
Edit2: Acording to:
http://android.modaco.com/content/h...com/309939/usb-brick-rickrolled-b0rked-fixed/
The command is
fastboot oem enableqxdm 0
not
fastboot oem enable qxdm 0
Wich resulted in a successfull Command but the SD card can still not be read.
Click to expand...
Click to collapse
I solved all of this by bypassing the SD card and downloading straight to /Data with Wget in shell.
However i still have the problem of runnin a non HTC rom (NO i cant flash a new one cus i still cant get the damn SD Card to work ).
So the whole software version .. if its wrong. will this still work? I changed the CID in the mtd0-img but since i dont know the software version i cant do annything about it ..
I follow all steps of the tutorial and it unbrick my HTC Desire!
Thanks!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
i love my phone!
Cant running a RUU in fastboot solve a usb brick, please?
chippieuk said:
I struggled with the guide on Modaco, as it's rather vague, so when I finally figured it out I wrote down ALL the steps you have to take, and this is what I ended up with:
To Un-USB Brick HTC Desire:
1. Hold down the back button, and then turn on your Desire
2. Make sure the screen shows FASTBOOT. If it doesn’t, choose it from the options available
3. In command prompt go to the folder on your computer where you downloaded and extracted the Android SDK to
4. At the command prompt type ‘fastboot oem boot’
5. If you know that you don’t have access to the SD card when your phone loads up, also type the command ‘ fastboot oem enable qxdm 0’
6. The bit you need from the information displayed in the CID. Look for something like ‘INFOCID is O2___001’. In this case, my CID is ‘O2___001’
7. On your phone go to Settings>About phone>Software Information and note your Software Number. Mine was 1.21.405.1
8. Now turn off the phone and take the SD card out and put it in your computer
9. Go to BROKEN LINK and put in the details from steps 6 & 7. <---------------------------------
10. Download the file it creates
11. Get the flash image from OTHER LINK
12. Put both of these on the SD card
13. Put the SD Card back in your Desire and turn it on
14. Go to the Market and download a terminal emulator. I used ConnectBot
15. Run Connectbot. In the bottom left corner where it says ‘ssh’ click on the triangle. Choose ‘locall and put in anything for your nickname.
16. Now enter the following commands EXACTLY as they are shown below, pressing enter after each one
17. su
18. cat /sdcard/flash_image > /data/flash_image
19. cat /sdcard/mtd0.img > /data/mtd0.img
20. chmod 755 /data/flash_image
21. /data/flash_image misc /data/mtd0.img
22. Reboot your Desire, and it should all work again!
Click to expand...
Click to collapse
I think the link at the 9 doesn't working anymore. It is connecting a French website which is asking an ID and Password. Can you please renew the link
Thanks
PS. I deleted the link because i don't have 8 posts and i can't add links to my messages.
Have a look for 'gold card helper' in the market.
It should help
Sent from my HTC Desire using Tapatalk
Ok so when i try to use rom manager, it says i need flash clockworkmod recovery. So i click on it n it says confirm model n i do, then it says "an error occurred while attempting to run privileged commands." Wat am i doing wrong?? Thanks.
Are you rooted? That's usually a good sign that you aren't.
Sent from my EVO from the Apple Store.
yea i went thro all the steps to root n in titanium backup it says root access is OK. so im confused now.
Make sure you have the latest version of Super User Permissions (2.2.2): http://forum.xda-developers.com/showthread.php?t=682828
When I got that error, it was because I hadn't told SUP to allow ROM Manager quick enough, and RM had timed out on the permission request.
ok so how do i get this onto my phone, i apologize, this is my first android phone.
tarheelsmj12001 said:
ok so how do i get this onto my phone, i apologize, this is my first android phone.
Click to expand...
Click to collapse
Just go ahead and download the zip file su-2.2.2-ef-signed.zip from that thread I linked to. Plug your USB cable into your phone and computer, and either go to Notifications, tap on Chareg Only, and then change it to Disk Drive and press done, then open My Computer (or if on Mac/Linux, double-click the drive on your desktop) and copy the ZIP file directly to SD card, or use ADB to push the file by first turning on USB debugging if it isn't already (Settings>Applications>Development>USB debugging) then open Command Prompt (Terminal on Mac/Linux), go to wherever you have ADB located (usually the Tools folder of the Android SDK) and use this command:
Code:
WINDOWS: adb push *path to ZIP*\su-2.2.2-ef-signed.zip /sdcard/
MAC/LINUX: ./adb puh *path to ZIP*/su-2.2.2-ef-signed.zip /sdcard/
If you used the ADB method: Go ahead and just use the command "adb reboot recovery" (or "./adb reboot recovery" if on Mac/Linux) to reboot into your Recovery. If you used USB Mass Storage, power off your phone, then hold down the Volume Down button, then continue holding Volume Down while holding the Power button. You will then see the bootloader screen (white screen with three skateboarding Androids at the bottom) and can let go of the buttons as soon as you do. Press Volume-Down to highlight "RECOVERY", and then the Power button to select it. Next you'll see the words "HTC EVO 4G" on a white screen (like a normal boot-up) followed shortly after your Recovery image.
Next, use Volume Up/Down to move your selection up/down and use the Power button to select "Install ZIP from SD Card" (or something along those lines). You should have one option for "install update.zip" and one for "Choose ZIP from SD card" (again, or something similar). Choose the latter of the two, and then use Volume Up/Down to select su-2.2.2-ef-signed.zip, and Power to select. Wait a few moments until you're told that the installation was successful, and then select to reboot the phone.
You should then be able to boot into Android, and have the Super User Permissions app installed! Whenever you try to run something which needs root, you'll get a pop-up asking for permission. Go ahead and launch ROM Manager, and you'll get the pop-up, make sure "Remember" is checked, and then press allow. If ROM Manager still complains that it didn't get permissions, re-launch it, and it should work fine.
drmacinyasha said:
Just go ahead and download the zip file su-2.2.2-ef-signed.zip from that thread I linked to. Plug your USB cable into your phone and computer, and either go to Notifications, tap on Chareg Only, and then change it to Disk Drive and press done, then open My Computer (or if on Mac/Linux, double-click the drive on your desktop) and copy the ZIP file directly to SD card, or use ADB to push the file by first turning on USB debugging if it isn't already (Settings>Applications>Development>USB debugging) then open Command Prompt (Terminal on Mac/Linux), go to wherever you have ADB located (usually the Tools folder of the Android SDK) and use this command:
Code:
WINDOWS: adb push *path to ZIP*\su-2.2.2-ef-signed.zip /sdcard/
MAC/LINUX: ./adb puh *path to ZIP*/su-2.2.2-ef-signed.zip /sdcard/
If you used the ADB method: Go ahead and just use the command "adb reboot recovery" (or "./adb reboot recovery" if on Mac/Linux) to reboot into your Recovery. If you used USB Mass Storage, power off your phone, then hold down the Volume Down button, then continue holding Volume Down while holding the Power button. You will then see the bootloader screen (white screen with three skateboarding Androids at the bottom) and can let go of the buttons as soon as you do. Press Volume-Down to highlight "RECOVERY", and then the Power button to select it. Next you'll see the words "HTC EVO 4G" on a white screen (like a normal boot-up) followed shortly after your Recovery image.
Next, use Volume Up/Down to move your selection up/down and use the Power button to select "Install ZIP from SD Card" (or something along those lines). You should have one option for "install update.zip" and one for "Choose ZIP from SD card" (again, or something similar). Choose the latter of the two, and then use Volume Up/Down to select su-2.2.2-ef-signed.zip, and Power to select. Wait a few moments until you're told that the installation was successful, and then select to reboot the phone.
You should then be able to boot into Android, and have the Super User Permissions app installed! Whenever you try to run something which needs root, you'll get a pop-up asking for permission. Go ahead and launch ROM Manager, and you'll get the pop-up, make sure "Remember" is checked, and then press allow. If ROM Manager still complains that it didn't get permissions, re-launch it, and it should work fine.
Click to expand...
Click to collapse
Damn i appreciate ur help n giving me the steps. Just one question, how do i get my command prompt to go to where my ADB is located, its stuck on C:\documents and settings. Thanks again for ur help n sorry for my stupidity.
When i go into my recovery n click on apply sdcard:update.zip, it says failed to open /sdcard/update.zip ( no such file or directory). Wat am i doin wrong??
tarheelsmj12001 said:
When i go into my recovery n click on apply sdcard:update.zip, it says failed to open /sdcard/update.zip ( no such file or directory). Wat am i doin wrong??
Click to expand...
Click to collapse
dont click that one, click the one that says install zip file or something, not update .zip
skittlesV1 said:
dont click that one, click the one that says install zip file or something, not update .zip
Click to expand...
Click to collapse
hmmm i dont have that option
skittlesV1 said:
dont click that one, click the one that says install zip file or something, not update .zip
Click to expand...
Click to collapse
Correct. There's usually two options, one of them being to choose to look for a ZIP file, and the other is sdcard:update.zip. You want to have it look for the ZIP file, and select it off of your card's root directory.
Oh, and to change what directory your command prompt is in, use "cd *path*" which is both for Windows, Mac, and Linux.
yea i dont have that option, only have the one to update.
What Recovery are you using? Perhaps your first step should be to get a better recovery image.
If u don't mind telling me how to do that then ill try n get a better one. N i have no idea which one i have.
Sent from my PC36100 using XDA App
Alright, at the top or bottom of your recovery mode's screen, it will usually tell you what recovery you have (ClockworkMod, Amon Ra, etc.).
To flash a new one, connect your computer and phone, and open up command prompt. Change to wherever you have ADB, and get ready for some fun.
First up, download recovery-RA-evo-v1.7.0.1.img (Amon_Ra's Recovery). Boot your phone into Fastboot by either using "adb reboot bootloader" or turn off you're phone, and turn it back on by holding Volume Down and Power. You'll get the white screen with the skating Androids again. Go ahead and select FASTBOOT. Now, in your command prompt/terminal, use this command:
Code:
fastboot devices
It should acknowledge that fastboot can see your phone. If not, try rebooting again. Once it sees your phone, use this command to flash the recovery:
Code:
fastboot flash recovery *path to file*\recovery-RA-evo-v1.7.0.1.img
Give it some time, and it should succeed. Then go on your phone, select bootloader, and then recovery. You should then boot into RA Recovery 1.7.0.1. Select "Flash zip from sdcard" and select the su-2.2.2-ef-signed.zip file. Give it a bit to do its thing, and then when it's all done, select "Reboot system now"
drmacinyasha said:
Alright, at the top or bottom of your recovery mode's screen, it will usually tell you what recovery you have (ClockworkMod, Amon Ra, etc.).
To flash a new one, connect your computer and phone, and open up command prompt. Change to wherever you have ADB, and get ready for some fun.
First up, download recovery-RA-evo-v1.7.0.1.img (Amon_Ra's Recovery). Boot your phone into Fastboot by either using "adb reboot bootloader" or turn off you're phone, and turn it back on by holding Volume Down and Power. You'll get the white screen with the skating Androids again. Go ahead and select FASTBOOT. Now, in your command prompt/terminal, use this command:
Code:
fastboot devices
It should acknowledge that fastboot can see your phone. If not, try rebooting again. Once it sees your phone, use this command to flash the recovery:
Code:
fastboot flash recovery *path to file*\recovery-RA-evo-v1.7.0.1.img
Give it some time, and it should succeed. Then go on your phone, select bootloader, and then recovery. You should then boot into RA Recovery 1.7.0.1. Select "Flash zip from sdcard" and select the su-2.2.2-ef-signed.zip file. Give it a bit to do its thing, and then when it's all done, select "Reboot system now"
Click to expand...
Click to collapse
Ok so i downloaded the recovery image. Where i get confused is when u say open the the command prompt and change to where i have ADB. So i go to start, run, n then type command?? N i dont understand when u said how to change what directory the command prompt is in, idk wat "cd *path*" means.
Where do you have ADB or the Android SDK?
To open command prompt, go to Start>Run and type cmd then hit enter. Then use the command cd (path to Android SDK)\tools\, so for example, I have my Android SDK in "C:\Program Files (x86)\Android SDK" so I would use cd C:\Program Files (x86)\Android SDK\tools\.
tarheelsmj12001 said:
Damn i appreciate ur help n giving me the steps. Just one question, how do i get my command prompt to go to where my ADB is located, its stuck on C:\documents and settings. Thanks again for ur help n sorry for my stupidity.
Click to expand...
Click to collapse
Dude it's not stupidity. This is the steepest part of the learning curve and there is actually not an easy answer. This drove me nuts when I first started to learn. But it's really fun once you figure it out.
First, follow the steps here: http://htcevohacks.com/htc-evo-hacks/how-to-install-android-sdk-and-adb-drivers-for-htc-evo-4g/
That will give you the SDK folder on your computer. I recommend that you extract the files directly onto the C: drive. That will give you the following path: C:\android-sdk-windows\tools (that will make more sense once you actually follow those steps.
Then, open a Command Prompt on your computer. If you use windows, it's under the Accessories folder on the Start menu. You obviously know this from your earlier post.
Then type the following:
Code:
cd C:\android-sdk-windows\tools
That should bring you to that folder. Everything you ever do that is "ADB" is done from this folder. That means that you actually need to put pertinent files into the "tools" folder there.
Once you are there type the following:
Code:
adb devices
If a long number shows up, then it sees your phone. There you go. If the above doesn't work, it might mean that you have to do another really annoying b.s. maneuver to your computer. Not worth mentioning if you don't have to do it. So just reply if this doesn't work and you can take it from there as far as troubleshooting.
Having said all that, the easiest way to install the new su zip file is to just put it on the your SD card, reboot into recovery, and choose install from SD card, and just choose it.
I would just like to thank u guys so much for ur help n def ur patience. I followed the steps u guys gave me n it worked flawlessly. Im so damn happy now lol, ive been trying to do this for sometime now. Now its time to get some ROMs on this bad boy. Once again, thank u very much guys for ur help, its nice to see ppl helping each other out on here so much.
tarheelsmj12001 said:
I would just like to thank u guys so much for ur help n def ur patience. I followed the steps u guys gave me n it worked flawlessly. Im so damn happy now lol, ive been trying to do this for sometime now. Now its time to get some ROMs on this bad boy. Once again, thank u very much guys for ur help, its nice to see ppl helping each other out on here so much.
Click to expand...
Click to collapse
You're more than welcome, just make sure to hang onto ADB and the Android SDK folders, and where they're are, as they'll be necessary for almost any ROM, upgrade, unlock, etc.!
I have no clue how this started. Last thing I did was flash Amon_RA 2.3 recovery on FEB 9th then the newest CM7 nightly, 32 I believe. Everything was fine with my phone up until an hour ago. I was on the phone with Sprint, they screwed up my sign-up date. But thats a whole other story. My phones battery was getting low during the call. Once I ended the call I set my phone down then noticed it started going into a boot cycle. Now all it will do is boot to the splash screen then reboot again, and again, and again. I tried to pull the battery and boot to recovery. It does the same thing. It will let me get to the bootloader and select recovery. Once I select recovery, it starts its damn boot loop. Any ideas? PLEASE HELP!
Well since you can't get into recovery, try pushing a recovery via adb or fastboot...
teh roxxorz said:
Well since you can't get into recovery, try pushing a recovery via adb or fastboot...
Click to expand...
Click to collapse
Its been soo long since I had to do any adb. Actually since launch using toasts root methods. Can you explain the commands please? On another note I do not have any recovery.img's saved to my pc. I dl'd them directly to my phone and flashed from a terminal app.
http://forum.xda-developers.com/showthread.php?t=705026
this thread can help you out especially the OP
download the amon-ra p36img.zip and place it onto your sdcard somehow, pull the battery, boot into bootloader, flash the pc36img and then reboot. they you'll have recovery and can load any rom you want again
t3project said:
download the amon-ra p36img.zip and place it onto your sdcard somehow, pull the battery, boot into bootloader, flash the pc36img and then reboot. they you'll have recovery and can load any rom you want again
Click to expand...
Click to collapse
^ Do exactly that [basically what I was saying/] But take out the battery and put the SD card in your computer via adapter to put the file on there.
Ok, the PC36IMG.ZIP is on the root of my sd and the bootloader is not seeing it? Now what?
if you're using windows make sure to not have the file as PC36IMG.zip.zip
mich11128 said:
if you're using windows make sure to not have the file as PC36IMG.zip.zip
Click to expand...
Click to collapse
Ok, I got it to see it. I ran the update, once it rebooted I selected recovery. It first asked me if I want to delete data? Or something on those terms. I chose no, and it will not let me boot to recovery still.....Back to the boot loops
Edit: First time I must have selected clear storage by mistake. Anyway I hit no at that point. I just re-dl'd the pc36img.zip file to make sure. It does run in the boot loader but will not reboot to recovery. Still endless loop????
splink7007 said:
Ok, I got it to see it. I ran the update, once it rebooted I selected recovery. It first asked me if I want to delete data? Or something on those terms. I chose no, and it will not let me boot to recovery still.....Back to the boot loops
Click to expand...
Click to collapse
Considering you can't get into recovery still, I would suggest reflashing the recovery and erasing the data when prompted.
Did you do a nandroid backup? I only ask cause once you get back into recovery you can just restore that.
so the bootloader read the file, then you ran the update and then it asked you to delete data? I don't remember that being a part of the process. Try it again and as soon as it's done updating try to get into the recovery again. If not then try to use adb.
sekigah84 said:
Considering you can't get into recovery still, I would suggest reflashing the recovery and erasing the data when prompted.
Did you do a nandroid backup? I only ask cause once you get back into recovery you can just restore that.
Click to expand...
Click to collapse
Ya I hit clear storage at first by mistake. I believe if I hit that it will wipe my entire sd card and will loose my nand backup?
mich11128 said:
so the bootloader read the file, then you ran the update and then it asked you to delete data? I don't remember that being a part of the process. Try it again and as soon as it's done updating try to get into the recovery again. If not then try to use adb.
Click to expand...
Click to collapse
Re-ran the update and still loops. The first time I ran it I hit clear storage instead recovery by mistake. Im sitting at the bootloader screen. I cant remember the adb commands. Can you refresh my memory? Thanks
Copy recovery-RA-supersonic-v2.3.img to the root of your sdcard
start the terminal app or launch adb shell
su(press enter)
flash_image recovery /sdcard/recovery-RA-supersonic-v2.3.img(press enter)
reboot recovery(press enter)
I find it strange that all this happened after getting off the phone with Sprint lol.
Does it still say S-OFF at the top of your bootloader?
I copied this from the amon ra recovery thread
Copy recovery-RA-supersonic-v2.3.img to the root of your sdcard
start the terminal app or launch adb
su(press enter)
flash_image recovery /sdcard/recovery-RA-supersonic-v2.3.img(press enter)
reboot recovery(press enter
now whenever I am about to start adb I use the command "./adb devices" without quotations of course, to make sure adb recognizes my evo oh and ignore the ./ that's just for mac users. When you enter that command you should see the serial number for your evo. after that I use
./adb shell
that should lead to
#
Then you type
su
and then you enter the rest of the commands. Sorry I didn't really organize it but that's pretty much it.
sekigah84 said:
Copy recovery-RA-supersonic-v2.3.img to the root of your sdcard
start the terminal app or launch adb shell
su(press enter)
flash_image recovery /sdcard/recovery-RA-supersonic-v2.3.img(press enter)
reboot recovery(press enter)
I find it strange that all this happened after getting off the phone with Sprint lol.
Does it still say S-OFF at the top of your bootloader?
Click to expand...
Click to collapse
lol you beat me to it and I was also about to ask if the phone was still rooted. READ MY MIND hahaha
sekigah84 said:
Copy recovery-RA-supersonic-v2.3.img to the root of your sdcard
start the terminal app or launch adb shell
su(press enter)
flash_image recovery /sdcard/recovery-RA-supersonic-v2.3.img(press enter)
reboot recovery(press enter)
I find it strange that all this happened after getting off the phone with Sprint lol.
Does it still say S-OFF at the top of your bootloader?
Click to expand...
Click to collapse
I totally agree!! Crazy....Yes it still says S-OFF. How do I launch adb shell from the bootloader? Im sorry, I havent used adb or fastboot since launch rooting using toasts method.
Wish I could help you there but I haven't ran adb on a windows since my G1 lol I'll see if I find a thread with some help for adb and windows.
EDIT: Maybe this will help. http://forum.xda-developers.com/showthread.php?t=694250
Ok, if I run fastboot devices, it sees my device. But if I run adb devices, it doesnt see my device anymore. Im soo lost now.
sorry I forgot adb runs through recovery, what you have to use I believe is fastboot flash to flash the recovery image
here try this page better...I used this when I had to root my nexus one the hard way (before that crappy 1-click method was devised) this is the best guide I'd ever used as far as adb/fastboot commands.
http://forum.xda-developers.com/showthread.php?t=694250
warnning: any damage you do to your phone following these directions is your responsibility. Assume you warranty is void if your are rooted.
I used the information koush provided here and info birdman provided here and adopted it in Ubutnu Linux 11.10. I hit some bumps along the way using my Linux box so I decided to write this for those of us not using OS's made by the darkside This should also work with Ubuntu 12.04 LTS just fine.
All this should work with Linux Mint 12 also.
1- Set up Android SDK, adb, and fastboot in Ubuntu Linux using the links in my signature. I can't stress how useful and easy it is to set adb and fastboot in your "path" so you can easily use it from any prompt. The links explain it. Take your time with that and it will payoff for all your devices. Here is the guide I wrote http://forum.xda-developers.com/showpost.php?p=19446284&postcount=62
STOP NOW! EVERYTHING INCLUDING YOUR PERSONAL FILES, PICTURES, AND VIDEOS WILL BE ERASED WHEN YOU UNLOCK/ROOT THIS DEVICE. It does not have a physical SD card. Very annoying. Use Dropbox or Google+ to backup everything.
2- on your phone, go to settings/Developer Options and check the box for USB Debugging
3-connect your phone, fire up a terminal, and type:
Code:
adb devices
You should get the serial number of your device appear. If not, unplug, reboot phone, re-attach the phone to your computer and try again. If you still do not get your device's serial number, go back to step 1 and make sure everything is setup correctly.
4- Now download Clockwork Recovery from here
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.5.0.4-toro.img
(make sure it's the CDMA one (toro). The GSM one is called maguro and steps should be the same)
and su.zip from here
http://download.clockworkmod.com/test/su.zip
5-Turn the phone off, hold both Volume up and Volume Down and press the power button. You should come to a screen that has a big arrow and some writings at the bottom (fastboot). Last line should say Locked state.
6- Connect your phone to your computer, fire up a terminal and type:
Code:
fastboot devices
your phone and its serial number should appear just as it did using adb above. adb will not work here of course. If you don't see your device, go to step one. I guess you can download the fastboot for linux and cd to that directory and do it but I like to have it setup on my computer.
STOP NOW! EVERYTHING INCLUDING YOUR PERSONAL FILES, PICTURES, AND VIDEOS WILL BE ERASED WHEN YOU UNLOCK/ROOT THIS DEVICE. It does not have a physical SD card. Very annoying. Use Dropbox or Google+ to backup everything.
7- Now for the stuff that voids your warranty: Type
Code:
fastboot oem unlock
and enter. Look at your phone now, use the Volume up to choose YES and press the power button to accept. It should say that you are unlocked and fastboot is in good state.
9-use the volume up to change the value appearing in the arrow to recovery and press the power button to accept. You are taken to laying down android with a red triangle. This is the stock recovery. Now carefully press the volume up, volume down, and the power button to get to a menu. Choose wipe data and factory reset. 2 things: I had a hard time getting to the menu. Do it a few times and try pressing the power button JUST a fraction of a second earlier than the 2 volume buttons. Also wiping and resetting takes a few minutes, be patient.
10-you are now unlocked. Turn the phone off ( I pulled battery), go to fastboot screen by holding volume up, down and power button. Connect your phone to your computer and make sure it is recognized by typing:
Code:
fastboot devices
If it is, change directory to where you downloaded clockwork recovery. If you didn't change it, it should be the Download directory (remember it's case sensitive):
Code:
cd Downloads
11- Time to re-write your recovery:
Code:
fastboot flash recovery recovery-clockwork-5.5.0.4-toro.img
Please make sure you use common sense here when it comes to file names. If the file you downloaded has a different name or version, change it in the code above. I guess you can put the fastboot file in that location also to be used if you do not have it setup as in step 1. I'm not positive how and if that would work. Downloading and installing the wrong file is a mistake that may cause harm to your phone.
12- Use the vol up/down to point the big arrow toward recovery, push the power button to get to Cloclwork Recovery. Once you confirm you have CWR, reboot the phone normally and let Android OS create all the folders it needs. Once at start up screen, pull the battery to turn phone off, and then get to bootloader by holding vol up/down and power button in. Use the vol up/down to point the big arrow on sceen toward recovery. While in recovery, make sure your terminal prompt still shows the Downloads directory (or where the su and recovery files were downloaded to). Now type: (note the space between zip and /data)
Code:
adb push su.zip /data/media
this will put the su.zip file in the root of your virtual sd card.
You are still in recovery, reboot into recovery to refresh the file list by typing this
Code:
adb reboot recovery
Now go ahead and install su.zip through clockwork recovery's menus. Pretty self explanatory (choose zip from sd card). The su.zip should be now in the root of your virtual sd card.
That's all. You are now unlocked and rooted. Reboot. Make sure you install the paid versions of rom manager, titanium backup, and update superuser app.
13- Download Rom Manager and flash the recovery again (top choice). This will erase the install-recovery.sh file and keeps your CWR at each boot. You do not have to do step 14 if you do this. I will leave step 14 here just in case someone needs it.
14-When you are back in the fastboot screen. DO NOT reboot the phone here. There maybe a file that re-writes the recovery to stock if the phone is rebooted. Your phone may or may not have this file. of the two GN I have, one did and one did not at this step(may have been erased). The file is reovery.sh and is located in /system/etc/ . You need to either rename it or delete it.
While in fastboot and after you flashed CWR, use the Volume up and Down to change the arrow's value to recovery and press the power button. You should now see the familiar Clockwork recovery. In recovery, you can use adb (you can't in fastboot of course). You need to rename that file, use these steps in terminal: (If you see no file/folder found message, you know you do not have this file)
Code:
adb shell
Code:
mount -o rw,remount /system
Code:
mv /system/etc/install-recovery.sh /system/etc/install-recovery.bak
step 1 fires up adb, step 2 allows you to change permissions and read and write, and step 3 renames it. You can now unplug the phone.
Again, you can also get rid of this file by flashing the clcokwork recovery in Rom Manager or using the paid app root explorer to rename the file.
Once again referrence links:
http://rootzwiki.com/topic/12013-welcome-to-rootzwiki-editionstep-by-step-oem-unlock-and-root/
https://plus.google.com/103583939320326217147/posts/1Jsh9xPwnQP
thank you so much this is exactly what i was looking for. cant believe im the only one to comment on this. it is very detailed even some one new to Ubuntu could figure this out.
I've been using it too for a while but never posted so THANK YOU! Very easy to follow. Great work.
you're welcome. I find it ironic that a Linux based OS such as Android has so many HOWTOs for Windows but not enough for Linux. #powerofmonoply
I find I need to run fastboot commands with sudo or su into root before it will work. Same for you, or misconfig on my side?
Sent from my Galaxy Nexus using XDA
ual4720 said:
I find I need to run fastboot commands with sudo or su into root before it will work. Same for you, or misconfig on my side?
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
I'm not sure. How did you setup your adb and fastboot? I did not have to sudo for fastboot commands. What OS are you running?
Hey loveubuntu, I have a question.
I'm at Step 12, and I'm in recovery and when I run adb push su.zip /data/media, it isn't finding any devices. When I run adb devices, the device isn't listed.
Any advice?
AndroidSparty said:
Hey loveubuntu, I have a question.
I'm at Step 12, and I'm in recovery and when I run adb push su.zip /data/media, it isn't finding any devices. When I run adb devices, the device isn't listed.
Any advice?
Click to expand...
Click to collapse
were you able to see the device in the previous steps 3, 6 and 10 and now you don't?
Things that come to mind is:
1- Do you have the usb debugging checked?
2- unplug and replug the device and see if it works.
3- don't forget the samsung recovery file install-recovery.sh. If the phone is rebooted you may have re-written your recovery and have to start over. Then reboot the phone and go to rom manager and reflash the recovery (first option). This will take care of the install-recovery.sh file.
loveubuntu said:
were you able to see the device in the previous steps 3, 6 and 10 and now you don't?
Things that come to mind is:
1- Do you have the usb debugging checked?
2- unplug and replug the device and see if it works.
3- don't forget the samsung recovery file install-recovery.sh. If the phone is rebooted you may have re-written your recovery and have to start over. Then reboot the phone and go to rom manager and reflash the recovery (first option). This will take care of the install-recovery.sh file.
Click to expand...
Click to collapse
3, 6, & 9...check.
I rebooted my phone by pulling the battery and I still can't get adb to see the device. The install-recovery.sh? I don't remember reading anything about that.
In step 12 it says to let the phone reboot into the Android OS, but it's now back at factory reset, as that's what we did earlier in the instructions. As soon as it boots into the Android OS, adb lists the device.
At that point, since I'm in the AOS, I downloaded Astro File Manager and tried to put su.zip in the /cache folder, I think that's the folder that the clockwork recovery mod folder sees, and I don't have permission. I was hoping I could cheat and just drag & drop instead of pushing it. BUT...I did try the command adb push su.zip /media/play and I get permission denied. I'm guessing I don't have permission, even as sudo, to move the file to /data/media.
Okay I finally got it!
I didn't wait long enough for the Android OS to boot up. I finally was able to move the .zip file, but I couldn't find where /data/media was. So I let the OS boot up, removed the battery, went back into recovery, moved the zip file, and it was finally listed.
Ordered a Galaxy Nexus too, will definitely be using this guide. Windows guides are confusing.
Forceflow said:
Ordered a Galaxy Nexus too, will definitely be using this guide. Windows guides are confusing.
Click to expand...
Click to collapse
>Windows guides are confusing
>Windows guides
>Windows
Root of the issue
But agreed, this was a good supplement to follow for Ubuntu.
Sent from my Galaxy Nexus using xda app-developers app
Thank you for this guide. Some how I like the Linux method better than the Windows ones.
12- Use the vol up/down to point the big arrow toward recovery, push the power button to get to Cloclwork Recovery. Once you confirm you have CWR, reboot the phone normally and let Android OS create all the folders it needs. Once at start up screen, pull the battery to turn phone off, and then get to bootloader by holding vol up/down and power button in. Use the vol up/down to point the big arrow on sceen toward recovery. While in recovery, make sure your terminal prompt still shows the Downloads directory (or where the su and recovery files were downloaded to). Now type: (note the space between zip and /data)
Click to expand...
Click to collapse
This step is confusing. While in recovery should be replaced by "Hit Power button to enter ClockworkMod Recovery"
Otherwise people may mis-interpret by "Stay in fastboot and position the big arrow on top to Recovery Mode"
In my case (GNex GSM stock JB 4.11):
adb push su.zip /data/media
or
adb push su.zip /sdcard
did copy su.zip successfully but could not be listed by ClockworkMod Recovery menu when selecting "choose zip from sd card". I had to do this:
Code:
adb push su.zip /sdcard/Alarms
And, within the ClockWorkMod Recevery menu, select "choose zip from sd card"
Land on another screen where I could navigate to Alarms folder and see the su.zip there.
Now go ahead and install su.zip through clockwork recovery's menus. Pretty self explanatory (choose zip from sd card). The su.zip should be now in the root of your virtual sd card.
Click to expand...
Click to collapse
Sorry for being picky but personally, it is NOT self explanatory for me. I was expecting a menu item in CWM Recovery menu to say "Install su.zip". Actually you must navigate in the file system and select the su.zip yourself. Ok, may be that seems obvious now that I know what to do. But on the moment, I was worried I screwed up something because I needed to do some extra manipulations while you said that should be "self explanatory".
4- Now download Clockwork Recovery from here
Click to expand...
Click to collapse
You may want to up date the link, ClockWorkMod now has a Recovery program which is touch sensitive:
GSM: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.1.0-maguro.img
Sprint: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.1.0-toroplus.img
VRZ: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.1.0-toro.img
Step 12 finishes with
That's all. You are now unlocked and rooted. Reboot. Make sure you install the paid versions of rom manager, titanium backup, and update superuser app.
Click to expand...
Click to collapse
Therefore what is the need of doing #13 and 14?
Furthermore, Step 13 starts by
13- Download Rom Manager and flash the recovery again (top choice)
Click to expand...
Click to collapse
What is that top choice? Do you mean restart from the top at step #1? If you need to reflash again CWN, would it be simpler to restart from Step 10 instead of going back to the top?
And BTW, what is the reason to reflash the CWM Recovery again just after you have successfully flashed it at Step 12? Could that be #13 and #14 are some steps of an older guide which no longer apply now but you forgot to remove?
Sorry for the silly question but I am rather lost. After all that hardwork, when I attempt to Update SuperUser, it failed on the line "Gaining root access ..." What is the reason and how to fix that? FOUND ANSWER: the su.zip given in the post is Superuser 3.07 which is outdated, It is probably buggy. Replaced it by SuperSU 0.94 and it works perfect: http://download.chainfire.eu/204/SuperSU/
Thanks
worked like a charm.. if you have problem using fastboot, just cd to the folder with fastboot and run it like this:
Code:
sudo ./fastboot "command"
it will require your password and then work normally, seems like it need super user permissions.
Also for new user: to avoid writing a command or a folder name manually just push the TAB button, it will autocomplete the word if it's unique in that folder
Alright, I have been searching around for my problem and I have found no such luck. I am running Evervolv ICS ROM Preview 8 and I noticed they released Preview 9. So I decided to upgrade of course but I came across a snag. My phone just boot's into the stock recovery and not into Clockwork. I have found a similar problem in another forum but I am unable to post the link do the rules of this forum.
The problem being that I cannot turn off FASTBOOT, I have no selection to do so in my phones settings.
Any help at all would be wonderful.
Hadonka402 said:
Alright, I have been searching around for my problem and I have found no such luck. I am running Evervolv ICS ROM Preview 8 and I noticed they released Preview 9. So I decided to upgrade of course but I came across a snag. My phone just boot's into the stock recovery and not into Clockwork. I have found a similar problem in another forum but I am unable to post the link do the rules of this forum.
The problem being that I cannot turn off FASTBOOT, I have no selection to do so in my phones settings.
Any help at all would be wonderful.
Click to expand...
Click to collapse
Are you s-off? If so flash cwm recovery thru hboot as a PB31IMG.zip http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip
If you can boot into the stock recovery then fastboot is not the issue. If fast boot is enabled holding vol down and power just boots the phone, you will not enter any recovery. The only way to enter recovery with fastboot enabled is to pull the battery truly powering off the phone, fastboot does not power of but hibernates for faster boot.
cmlusco said:
Are you s-off? If so flash cwm recovery thru hboot as a PB31IMG.zip
If you can boot into the stock recovery then fastboot is not the issue. If fast boot is enabled holding vol down and power just boots the phone, you will not enter any recovery. The only way to enter recovery with fastboot enabled is to pull the battery truly powering off the phone, fastboot does not power of but hibernates for faster boot.
Click to expand...
Click to collapse
Yes I am S-OFF, how do I flash through hboot? This does not fully answer my question of why I am unable to boot into Clockwork and how to fix this issue.
Hadonka402 said:
Yes I am S-OFF, how do I flash through hboot? This does not fully answer my question of why I am unable to boot into Clockwork and how to fix this issue.
Click to expand...
Click to collapse
Well if you are getting the stock recovery then i assume cwm recovery is not installed. Flashing the file above will install it.
To do so download the file and place it on your sdcard in no folders.
Power off the phone and pull the battery, then reinsert.
Hold vol down and power buttond till a white screen pops up (hboot). Wait a couple secs and hboot will find the file, parse it, and then prompt to press vol up to update. When its donr it will prompt to press vol up to reboot or vol down not to. Press vol down and then scroll to and select recovery. You should now be where you want to be.
cmlusco said:
Well if you are getting the stock recovery then i assume cwm recovery is not installed. Flashing the file above will install it.
To do so download the file and place it on your sdcard in no folders.
Power off the phone and pull the battery, then reinsert.
Hold vol down and power buttond till a white screen pops up (hboot). Wait a couple secs and hboot will find the file, parse it, and then prompt to press vol up to update. When its donr it will prompt to press vol up to reboot or vol down not to. Press vol down and then scroll to and select recovery. You should now be where you want to be.
Click to expand...
Click to collapse
I'm sorry I was not clear before, forgive me. Yes Clockwork is installed, I have reflashed it with the current version and older versions to attempt to fix the problem. I tried another recovery as well (One that I cannot recall at the moment) and I still boot into the stock recovery. My main problem is that I cannot boot into Clockwork. I'm sorry again for not being specific before.
Hadonka402 said:
I'm sorry I was not clear before, forgive me. Yes Clockwork is installed, I have reflashed it with the current version and older versions to attempt to fix the problem. I tried another recovery as well (One that I cannot recall at the moment) and I still boot into the stock recovery. My main problem is that I cannot boot into Clockwork. I'm sorry again for not being specific before.
Click to expand...
Click to collapse
Have you tried using rom manager to install cwm, and using the erase recovery before flashing option in its preferences?
What hboot version are you on?
cmlusco said:
Have you tried using rom manager to install cwm, and using the erase recovery before flashing option in its preferences?
What hboot version are you on?
Click to expand...
Click to collapse
Yes I have done that and still no luck. I am using, HBOOT-0.92.0000
Hadonka402 said:
Yes I have done that and still no luck. I am using, HBOOT-0.92.0000
Click to expand...
Click to collapse
Hmmm very strange. Do you have a pc with adb and fastboot setup on it?
cmlusco said:
Hmmm very strange. Do you have a pc with adb and fastboot setup on it?
Click to expand...
Click to collapse
No I do not, should I go ahead and get that setup? Before I forget thank you for being patient and helpful this far, I appreciate your help so far.
Download this http://dinc.does-it.net/ADB/ADB-Fastboot-USB-Drivers_v4_(x86)(x64).zip, and extract it to C:\. You should now have an ADB folder on the C:\ drive (C:\ADB), which contains adb.exe and fastboot.exe. Then follow this guide to setup the drivers http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
Once that is setup and working download this zip file ( http://dinc.does-it.net/Guide_Root_New_Hboot/flash_mtd_recovery.zip ), unzip it, and place the 2 files on your sdcard in no folders.
Make sure usb debuging is checked on in menu - settings - applications - development
Power off the phone pull the battery and reinsert. Plug the phone in to the pc and hold vol down and power till hboot comes up. Select fastboot, it should say in red near the top fastboot usb. Then type the folowing in a cmd prompt:
fastboot erase recovery
Once complete reboot the phone.
Set the phone to charge only.
Open a command prompt on your PC and navigate to the same folder as your fastboot.exe file, (example type: cd C:\ADB ).
Type the following into the command prompt pressing the enter key at the end of each line:
adb shell
(You should now get a pound sign #)
cat /sdcard/flash_image > /data/flash_image
chmod 755 /data/flash_image
/data/flash_image recovery /sdcard/recovery.img
Then try to see if you can access cwm recovery.
cmlusco said:
Hmmm very strange. Do you have a pc with adb and fastboot setup on it?
Click to expand...
Click to collapse
cmlusco said:
Download this http://dinc.does-it.net/ADB/ADB-Fastboot-USB-Drivers_v4_(x86)(x64).zip, and extract it to C:\. You should now have an ADB folder on the C:\ drive (C:\ADB), which contains adb.exe and fastboot.exe. Then follow this guide to setup the drivers http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
Once that is setup and working download this zip file ( http://dinc.does-it.net/Guide_Root_New_Hboot/flash_mtd_recovery.zip ), unzip it, and place the 2 files on your sdcard in no folders.
Power off the phone pull the battery and reinsert. Plug the phone in to the pc and hold vol down and power till hboot comes up. Select fastboot if not already selectef for you. It should say in red near the top fastboot usb plug. Then type the folowing in a cmd prompt:
fastboot erase recovery
Once complete reboot the phone.
Set the phone to charge only, and make sure usb debuging is checked on in menu - settings - applications - development.
Open a command prompt on your PC and navigate to the same folder as your fastboot.exe file, (example type: cd C:\ADB ).
Type the following into the command prompt pressing the enter key at the end of each line:
adb shell
(You should now get a pound sign #)
cat /sdcard/flash_image > /data/flash_image
chmod 755 /data/flash_image
/data/flash_image recovery /sdcard/recovery.img
Then try to see if you can access cwm recovery.
Click to expand...
Click to collapse
I got an error called Segmentation Fault.
Hadonka402 said:
I got an error called Segmentation Fault.
Click to expand...
Click to collapse
Sounds like the recovery partition may be corrupt, nothing will write to it. Well if i were you i would do an ruu and see if that fixes it. Not much else you can do i dont think. Hopefully the ruu will fix it and allow you to flash cwm.
How do I go about doing ruu?
Hadonka402 said:
How do I go about doing ruu?
Click to expand...
Click to collapse
Download this ruu http://dinc.does-it.net/Stock_Images/4.06.605.3/PB31IMG.zip, and here is a good write up on how to flash it. http://pvillecomp.com/?page_id=79. Its the same way you flashed the cwm file earlier in post 2, thru hboot as a PB31IMG.zip
cmlusco said:
Download this ruu http://dinc.does-it.net/Stock_Images/4.06.605.3/PB31IMG.zip, and here is a good write up on how to flash it. http://pvillecomp.com/?page_id=79. Its the same way you flashed the cwm file earlier in post 2, thru hboot as a PB31IMG.zip
Click to expand...
Click to collapse
Note that doing an ruu will wipe yout phone and you will ne back to stock. If after doing so you still cant get a recovery to flash, you will be stuck on stock.