[Q] Doesn't matter what I flash, phone boots into Recovery.. - EVO 4G Q&A, Help & Troubleshooting

Trying to return a Evo 4G to stock for return to sprint/assurion.
Phone has non-functioning volume buttons which makes navigating hboot and fastboot impossible. Can only select first option in each (power button works).
I have Smelkus recovery so i have full navigation in recovery (capacitive buttons work).
Right now whenever I boot the phone it goes right to recovery (smelkus 4.2.1)
When it boots up everything looks normal but the very bottom of the screen shows:
RA Revamped
Build : RA-supersonic-4.2.1-smelkusMOD
E:Invalid command argument
Recovery seems to work normally though.
The phone is rooted with HTCdev website. I did not go any further with other unlocks as far as I remember.
This is what bootloader shows:
*** UNLOCKED ***
SUPERSONIC EVT2-3 SHIP S-ON
HBOOT-2.18.0001
MICROP-041f
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.12.19
Dec 21 2011, 12:50:32
I've tried so far:
Flashing various stock rooted and unrooted roms (usually latest or one prior to latest I could find).
Also tried flashing AOSP ROM (Deck's 1.3d)
Running an RUU linked from (I think) CaptainThrowback's sig. Was a 3.7xxx version - RUU failed claiming was wrong RUU. Phone version had shown 4.56. or 4. something before starting so maybe was too old?
Am downloading now an RUU 4.67.651.3 now but DL is very slow. Hope that works because I think that's my last ditch.
Besides the RUU failing, the other flashes all seemed successful yet when I reboot the phone it still drops me right back into Recovery (smelkus)
Any help? I gotta return this thing very soon and running out of ideas.
Thanks all.
** EDIT
Ran that last RUU and I get the same error: ERROR [155]: UNKNOWN ERROR.
Then it tells me to get the correct ROM Update Utility an try again.
This RUU version (4.67.xx) is/was the same as reported on my phone before I started it.
Any thoughts anyone?

jackfrost909 said:
Trying to return a Evo 4G to stock for return to sprint/assurion.
Phone has non-functioning volume buttons which makes navigating hboot and fastboot impossible. Can only select first option in each (power button works).
I have Smelkus recovery so i have full navigation in recovery (capacitive buttons work).
Right now whenever I boot the phone it goes right to recovery (smelkus 4.2.1)
When it boots up everything looks normal but the very bottom of the screen shows:
RA Revamped
Build : RA-supersonic-4.2.1-smelkusMOD
E:Invalid command argument
Recovery seems to work normally though.
The phone is rooted with HTCdev website. I did not go any further with other unlocks as far as I remember.
This is what bootloader shows:
*** UNLOCKED ***
SUPERSONIC EVT2-3 SHIP S-ON
HBOOT-2.18.0001
MICROP-041f
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.12.19
Dec 21 2011, 12:50:32
I've tried so far:
Flashing various stock rooted and unrooted roms (usually latest or one prior to latest I could find).
Also tried flashing AOSP ROM (Deck's 1.3d)
Running an RUU linked from (I think) CaptainThrowback's sig. Was a 3.7xxx version - RUU failed claiming was wrong RUU. Phone version had shown 4.56. or 4. something before starting so maybe was too old?
Am downloading now an RUU 4.67.651.3 now but DL is very slow. Hope that works because I think that's my last ditch.
Besides the RUU failing, the other flashes all seemed successful yet when I reboot the phone it still drops me right back into Recovery (smelkus)
Any help? I gotta return this thing very soon and running out of ideas.
Thanks all.
** EDIT
Ran that last RUU and I get the same error: ERROR [155]: UNKNOWN ERROR.
Then it tells me to get the correct ROM Update Utility an try again.
This RUU version (4.67.xx) is/was the same as reported on my phone before I started it.
Any thoughts anyone?
Click to expand...
Click to collapse
My first thought is that you volume button might be stuck on the volume down key that's why it keeps booting up into recovery or it can be the recovery as well. Try to get the volume keys to work first tho.

Asonicperson said:
My first thought is that you volume button might be stuck on the volume down key that's why it keeps booting up into recovery or it can be the recovery as well. Try to get the volume keys to work first tho.
Click to expand...
Click to collapse
I know the volume key not to be stuck. The phone booted fine into the previous ROM until some point in my restoring to stock when the previous rom got wiped, iirc the first time I flashed a stock rooted over it.
I'm wondering if I didn't bork something trying to fix this with fastboot.
I'm grasping here but I think I read something once... Is it possible I pushed recovery to the 'regular' rom (OS) partition? That's why it's booting to Recovery every time?
But would that explain why flashing a rom from the recovery doesn't overwrite nor throw an error either..
Not sure where to go next. Gonna try to find a rom image I can push through fastboot. Should probably do recovery img that way too...

You have to relock before you can flash an RUU or PC36IMG.
Since you can get into recovery, adb will work. Connect the device to the computer in recovery, and open a command prompt from the folder with adb in it. Issue the command "adb reboot bootloader", and it should reboot into fastboot mode. Once the device says "FASTBOOT USB", you can issue the command "fastboot oem lock", which will relock your HBOOT.
Then the RUU should work.

Thanks Captain,
I wish I'd have seen your post sooner but I did figure it out. I guess talking it out sometimes is important too...
For now I'm going with that I had somehow installed the recovery into the "main" OS partition (I'd been trying to flash things from fastboot so user error is very possible..)
I noticed in Smelkus there's a 'developer' menu with a 'reboot to recovery' option so I tried that on a whim and when recovery booted up I did not have the "E:Invalid command argument" at the bottom of my screen.
I tried flashing a stock rooted. Bam! Success. Assumedly rebooting from the above menu actually got me to the *real* recovery running from the recovery partition and flashing worked from there
Captain, since you know this stuff well, maybe you can expand on exactly what just happened here (why it flashes seemed to succeed and not throw errors from the recovery in the 'wrong' partition for example) but for now I'm calling this solved and note to self and maybe other's that the "E:Invalid command argument" is at least a possible indication that recovery may be running from the wrong partition.
hth someone else,
J.

Related

Most likely bricked EVO 4g

I have officialy given up on repairing my phone. Looks like it's not possible to fix this thing. Just spent the better part of 3 pays (4hours of sleep a night) trying to get my phone fixed. My sister bought this EVO through some work deal and gave me it on Christmas. I rooted it that night, and bricked it 30mins later, because of the newer partition scheme it is currently impossible to get this phone back working...
This is what I have now. A EVO 4G that boots normally to this screen. ftp://eto.homeip.net/shared/IMAG0003.jpg
A Vol Down + Power Boot boots to this screen. ftp://eto.homeip.net/shared/IMAG0004.jpg
I can also navigate to this screen. ftp://eto.homeip.net/shared/IMAG0005.jpg
Because of the S-OFF it is obvious to those in the know that I rooted my phone.
I'm just wondering if you guys think this scenaro will work.
_________________________________________________________________
Walk into a Sprint Repair Store, tell them my sister just bought the phone new (about a week ago) and gave it to me as a X-Mas gift. I chose to do the latest OTA-Update, and after it stopped booting and only went to this screen. ftp://eto.homeip.net/shared/IMAG0003.jpg
Where I'd have to pull the battery to turn it off.
They will probably try VolDown+Power and might comment on S-OFF (which I will say I don't know what that is).
Hope they give me a new/refurbished EVO for free or less then $50.
===============================
Questions
* Should I go to a Sprint Store I've never been to? (There are stores within 20miles of me) (Closest knows I root phones, then other I've been into a bunch of times and may have given up on me)
* Should I get the receipt from my sister, who I don't want to tell I rooted/bricked phone
* Also please give me suggestions of anything that will help
BTW
* Am well within 30days of buying phone, though I'm not sure if my sister bought it through Sprint or not (Think she did though)
* I have pin/name/number on account and can easily activate a different phone they give me.
* Would rather not tell my sister or even get the receipt from her room to keep her from suspecting anything, but can if need be
Thanks for your suggestions, wanted to get this done by the end of the week before I head back down to San Luis Obispo for college. (Where there are fewer Sprint Stores to spam)
The Good news: If you're screen is turning on (using ANY method) you're Evo isn't bricked.
The Bad news: I don't know what you did. I would suggest trying the unroot method and seeing if you can get yourself out of this pickle that way. My first rooitng experience everything went horribly array, and I ended up just accepting an OTA to get out of it.
http://forum.xda-developers.com/showthread.php?t=884060
Pick which ever one you like and put it on the root of the sdcard. I couldnt tell you because if you didnt record what software you started with niether could I.
LaloHigh said:
http://forum.xda-developers.com/showthread.php?t=884060
Pick which ever one you like and put it on the root of the sdcard. I couldnt tell you because if you didnt record what software you started with niether could I.
Click to expand...
Click to collapse
What do you mean record what software I started with? I had 2.02, now have 0.76 (But my screen says 2.10). I've tried both the exe and the PC36IMG.zip that you've linked.
Using .exe gives me a Error 170 (Not recognizing my phone is plugged in)
Putting PC36IMG.zip on sd and using hboot gives me Failed-PU, Partition Update Fail! for every category but Radio_V2. BTW I'm supposed to use the first two files from that link
SUPERSONIC EVT1 ENG S-OFF
HBOOT-2.10.0001 (PC36*****)
MICROP-041f
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.11.19
Mar 30 2010,11:24:04
Greenfieldan said:
The Good news: If you're screen is turning on (using ANY method) you're Evo isn't bricked.
The Bad news: I don't know what you did. I would suggest trying the unroot method and seeing if you can get yourself out of this pickle that way. My first rooitng experience everything went horribly array, and I ended up just accepting an OTA to get out of it.
Click to expand...
Click to collapse
Well what I did was messup the way it sees my partition. I have a nwer partition scheme i believe but the 0.76 software thinks I have the older partition settup.
If you mean unroot method from this post http://forum.xda-developers.com/showthread.php?t=829045 the one I rooted with then I can't do it cause I have no recovery. I can't get to it cause bad partition settup.
I know I can run fastboot erase commands, do you guys think I should run
Code:
fastboot erase boot
to create an unbootable system. One that doesn't even have the screen turn on?
*Which if any partition can I delete in order to never have the phone even turn the screen on?
Here's the choices (wimax, misc, recovery, boot, system, cache, userdata)
if your getting error 170, the RUU can't communicate with the phone.\
Can you get Hboot USb on? IF so, the RUU may run with it.
Drivers installed on computer?
Otherwise, you mave have blown out USB port, like I did.
Try putting the RUU, rom.zip (rename rom.zip to PC36IMG.zip) to your sd card, and see if that saves your a$$.
If that don't work, better run it over with a car or something and take it back.
The good news is you are still in your 30 day warranty. The solution I would suggest is try to flash the bootloader back to hboot 2.10. I would find a pc36 with 2.10 and flash away. Maybe even fastboot erase every partition except boot and hboot first. Don't do radio or wimax either or it will brick your radio and wimax. Then flash a full pc36. Other than that, manually brick. I would erase hboot and boot to brick.
Good luck
If you erase boot.img, it will still go to hboot. Erase the touchpanel image. That way they cant see it. By the time your phone gets to its repair destination, "they" wont be looking for that type of thing. They will just repartition. Also, it wont let you erase hboot
What error are you seeing when you select recovery from the bootloader menu?
The RUU that you tried, what version was it? You MUST use the 3.70.651.1 RUU because your phone thinks you are on hboot 2.10. Do not try an older RUU.
--------------------------------
Try the following
1) Download File PC36IMG_Recovery.zip and Rename to PC36IMG.zip.
copy to the root of your SDCard and power off phone
2) Power your phone back on into the boot loader by holding power and vol-down until your presented with a white screen. It will read the pc36img.zip and as you if you want to flash. Say yes. Then it will ask if you want to reboot, VOL+UP for yes.
3) If your rom gets tossed in the process. Reboot your phone into bootloader select recovery, and reflash your rom....DONE
4) Once in recovery, flash HBoot 2.10 zip
6) Now try RUU 3.70.651.1
-----------------------------------------------
If that does not work then try the following:
1) Download the img file for the modified Amon_Ra Recovery
2) Put evo-test.img on the root of your sdcard
3) Put the phone in fastboot mode
4) fastboot boot evo-test.img
5) Once in recovery, flash HBoot 2.10 zip
6) Now try RUU 3.70.651.1
Update
thanks to some help I have gotten farther on this issue. Can get past USB Erro 170. Now get to Error 171 when trying to flash image. When i run RUU.exe it tries flashes then reboots into stuck image of 3 androids skating. Which I alwasy need to battery pull to fix. Heres the log
ftp://eto.homeip.net/shared/RUU_101228T160722.log
__________________________________________
So how could I remove touchpanel img? thanks
josh4trunks said:
Update
thanks to some help I have gotten farther on this issue. Can get past USB Erro 170. Now get to Error 171 when trying to flash image. When i run RUU.exe it tries flashes then reboots into stuck image of 3 androids skating. Which I alwasy need to battery pull to fix. Heres the log
ftp://eto.homeip.net/shared/RUU_101228T160722.log
__________________________________________
So how could I remove touchpanel img? thanks
Click to expand...
Click to collapse
But if you can't flash a RUU.exe, then you can probably flash a zip file of a ROM.
This can or be or is not correct, I am just curious how this well happened to you.
nope tried flashing ROM through hboot, fastboot... Tried 'fastboot erase boot' didn't do anything. I'm gonna update the OP on the current situation, giving up...
Are you able to use the bootloader to flash only the custom recovery amon RA zip? If you can get into custom recovery you will be fine. Once in recovery you can flash hboot radio etc 1 at a time with a reboot in between each flash. After that you can flash a custom rom and be happy.
i think he said multiple times that he was totally screwed and his partitions were messed up so he either needs a total memory reflash or god's private java code
illogos said:
Are you able to use the bootloader to flash only the custom recovery amon RA zip? If you can get into custom recovery you will be fine. Once in recovery you can flash hboot radio etc 1 at a time with a reboot in between each flash. After that you can flash a custom rom and be happy.
Click to expand...
Click to collapse
Can't flash through bootloader. Get Fail-PU
Which is a Partition Update Error

[Q] Stuck on cyanogenmod boot loop and no clockwork recovery...

Ok so here's the deal I have been working on this STUPID Incredible for a buddy of mine for like the last 4 hours trying to fix his boot loop issue. I have scoured the internet looking for a way to fix this problem and downloaded countless *.img and *.zip files and who knows what else...
[EDIT] Also if I reboot to bootloader (either through adb fastboot or through the phone (VOL (-) + POWER) adb can't find the phone I can only access the phone when it's actually trying to boot up
[THE ISSUE]​
The phone boots up shows the white htc incredible screen than proceeds to boot into cyanogenmod 7.blah.blah.blah (don't know the exact version it's from a couple months ago) and than just continuously shows the skateboard dude and doesn't proceed past that point.
When I reboot the phone and load up the bootloader it runs fine and than when I try to do the recovery option it will vibrate for a second show the htc incredible screen and than show the fastboot usb options (bootloader, reboot, reboot bootloader, power down) and if I select reboot it just reboots to the same problem.
If I choose Factory Reset it goes to the fastboot usb menu but I can't choose any of the options and it just sits there, I actually have to do a battery pull in order to do anything.
I know that clockword mod was installed on this phone but I can't access it by any means.
I hooked the phone up to my computer and loaded up adb (which is installed correctly as I've used it on my phone and the htc drivers are installed correctly) if I try to access my internal sd card through an adb shell it doesn't list anything and I have root in the shell (#) and if I try to cd to sd-ext it says "can't cd to sd-ext) so I can put something on the cards and load them up (as far as I know) to get the recovery working or anything...
adb does see the phone sees the files on the phone I can do a adb reboot it and that works fine.
Here's some info from the bootloader:
incrediblec xc ship s-off
hboot-0.92.0000
microp-0417
touch panel-atmel224_16ab
radio-2.15.00.07.28
Jul 23 2010, 18:06:51
Ok so that got longer than I thought it would be (whoops) I hope I explained this well enough for everyone and didn't make it to confusing. I don't care if I have to go back to stock or what I just need to get this phone up and running again...
Thanks for reading this horribly long thread and for any feedback you have!
Sounds like something is borked with your install, and your recovery has vamooshed. Yes, those are the technical terms for it. Try an RUU.
http://pvillecomp.com/?page_id=22
That will give you stock everything, including recovery, you just have to flash CWM, then in CWM wipe everything (wipe data/factory reset, wipe boot, wipe system), then flash a ROM.
Edit: try Pons' method first.
First, the phone isn't stupid...it's Incredible. I mean seriously /s
Can you reformat the sd card, download CWM to the root of your sd card, then install CWM through hboot that way?
CWM is available from pvillecomp.com, download the file under the heading "Recoveries" and rename it to: PB31IMG.zip
Couple questions:
What started the bootloop issue? What steps have you taken to try resolving this issue?
G33kman said:
Ok so here's the deal I have been working on this STUPID Incredible for a buddy of mine for like the last 4 hours trying to fix his boot loop issue. I have scoured the internet looking for a way to fix this problem and downloaded countless *.img and *.zip files and who knows what else...
[EDIT] Also if I reboot to bootloader (either through adb fastboot or through the phone (VOL (-) + POWER) adb can't find the phone I can only access the phone when it's actually trying to boot up
[THE ISSUE]​
The phone boots up shows the white htc incredible screen than proceeds to boot into cyanogenmod 7.blah.blah.blah (don't know the exact version it's from a couple months ago) and than just continuously shows the skateboard dude and doesn't proceed past that point.
When I reboot the phone and load up the bootloader it runs fine and than when I try to do the recovery option it will vibrate for a second show the htc incredible screen and than show the fastboot usb options (bootloader, reboot, reboot bootloader, power down) and if I select reboot it just reboots to the same problem.
If I choose Factory Reset it goes to the fastboot usb menu but I can't choose any of the options and it just sits there, I actually have to do a battery pull in order to do anything.
I know that clockword mod was installed on this phone but I can't access it by any means.
I hooked the phone up to my computer and loaded up adb (which is installed correctly as I've used it on my phone and the htc drivers are installed correctly) if I try to access my internal sd card through an adb shell it doesn't list anything and I have root in the shell (#) and if I try to cd to sd-ext it says "can't cd to sd-ext) so I can put something on the cards and load them up (as far as I know) to get the recovery working or anything...
adb does see the phone sees the files on the phone I can do a adb reboot it and that works fine.
Here's some info from the bootloader:
incrediblec xc ship s-off
hboot-0.92.0000
microp-0417
touch panel-atmel224_16ab
radio-2.15.00.07.28
Jul 23 2010, 18:06:51
Ok so that got longer than I thought it would be (whoops) I hope I explained this well enough for everyone and didn't make it to confusing. I don't care if I have to go back to stock or what I just need to get this phone up and running again...
Thanks for reading this horribly long thread and for any feedback you have!
Click to expand...
Click to collapse
Have you tried to reflash cwm recovery thru hboot? http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip Then ser if you can access it. If you can wipe everything and flash a rom of your choosing. If that dosent work try an ruu thru hboot. http://dinc.does-it.net/Stock_Images/3.26.605.1/PB31IMG.zip
WIN!
cmlusco said:
Have you tried to reflash cwm recovery thru hboot? Then ser if you can access it. If you can wipe everything and flash a rom of your choosing. If that dosent work try an ruu thru hboot.
Click to expand...
Click to collapse
Oh man thanks guys for the feedback I thought it would be something easy enough. I officially have cwm recovery working and am currently install cyanogenmod 9 as we speak! You guys are lifesavers seriously thank you!
CWM Boot Loop - Unable to access via Odin/ADB
I have the boot loader problem too... Last night, for no apparent reason, my phone turned off and didn't want to come back on again. I didn't change anything, plug it into anything, or do anything fancy, it just turned itself off and now it's stuck in a boot loop.
It boots into download mode okay, but I can't get it into recovery.
Win here too!
i bricked my phone running cm7 also and had the exact same problems right down to the T. ...SO!, that program that i installed on my computer took complete control of the phone and reset the rom. this is a wonderful piece of software. if you have an incredible download this program and dont worry about bricking your phone again.
how to obtain s-on now?
After I used the program from the website in the previous post, it brought me back to stock Rom and everything. Now it's still s-off, but I can't get into cwm, just hboot. My main goal is just to get this back to stock (unrooted and s-on). Can someone please explain how I go about doing this? I can get.any info needed ie. Radio etc.
Problem right now is in order to get into the phone I have to do the entire setup which includes activating it,which I cannot do.
Thank you guys much for this useful info.
brandonb0013 said:
After I used the program from the website in the previous post, it brought me back to stock Rom and everything. Now it's still s-off, but I can't get into cwm, just hboot. My main goal is just to get this back to stock (unrooted and s-on). Can someone please explain how I go about doing this? I can get.any info needed ie. Radio etc.
Problem right now is in order to get into the phone I have to do the entire setup which includes activating it,which I cannot do.
Thank you guys much for this useful info.
Click to expand...
Click to collapse
Why do you want it unrooted and s-on? All you need to do is flash cwm recovery http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip thru hboot. From there you can flash superuser http://dinc.does-it.net/Superuser/SuperUser_3.1.1.zip and be rooted if so desired. If you really want s-on and stock you need to flash cwm http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip thru hboot, flash the 2.15.00.07.28 radio http://dinc.does-it.net/Radios/2.15.00.07.28/PB31IMG.zip thru hboot, and then flash the unrevoked s-on patch http://dinc.does-it.net/Unrevoked/unrevoked-forever-son.zip thru recovery. Once s-on flash a official ruu http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip thru hboot and you will be stock s-on. Also if you want to bypass the activation just cancel it 3 or 4 times and it will let you skip it.
cmlusco said:
Also if you want to bypass the activation just cancel it 3 or 4 times and it will let you skip it.
Click to expand...
Click to collapse
Tapping each corner going clockwise, starting in the top left, is an easier way to skip the setup.
thanks
Thanks guys. I ended up calling customer service and they got me past the activate screen. From there I re rooted the phone so I could use cwm recovery again and flash s-on then unrooted it and all is good now. Thanks

[Q] Is it possible to Recover my DInc?

I hope someone in this community is able to help. I've already been scouring Google this morning for people with a similar issue and haven't been successful in getting my phone to come back so I suspect there may be a hardware issue.
Here's a summary of the problem:
My phone shutdown this morning while I was listening to a podcast. It got stuck in a boot loop at the splash screen, constantly rebooting itself. A battery pull would not solve the problem. I was able to get it into HBOOT (version 0.92) but when I tried going into recovery from there, It got stuck on the splash screen (no looping). Before all this I had been running Nils Business Gingersense for quite a while and things were working fine, in case anyone needs that detail.
After failing to boot to recovery, here are some of the things I have tried to fix this issue:
1. Factory reset in HBOOT
2. Flashed RUU 2.2 and then tried RUU 2.3.4 through HBOOT. Though neither of these would get the phone to come up, the splash screen reboots stopped and the phone just freezes in splash screen now (over 30 minutes with no change).
3. Tried to reflash CWM 5.0.2.0 through Fastboot. Although the phone is recognized by 'fastboot device', it says 'remote: not allowed' when try to flash the .IMG file.
4. Tried to flash an older CWM recovery from when I originally rooted my phone --same 'not allowed' error
5. Ran the official RUU for Froyo on my PC and it looked promising but I never got past the splash screen afterward a reboot.
6. I don't know a ton about ADB but ADB does not recognize my device even though Fastboot does.
At this point I'm not sure what else to try. It seems promising that I can get into HBOOT and that Fastboot will recognize my phone but what can I do with that now?
Thanks for any ideas you might have.
Have you tried flashing cwm thru hboot as a PB31IMG.zip? http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip. If that dosent work you could try to update hboot to 1.02 and htcdev unlock it. This will allow extended fastboot commands. You can do this on the htcdev website. Or you could downgrade hboot to the 0.77 engineering bootloader http://dinc.does-it.net/Hboots/ENG_Hboot_0.77/PB31IMG.zip which basicly does the same thing, and might be a better option than upgrading. You are s-off right?
Yes, I still have S-OFF. I did try flashing several recoveries through hboot and they all acted like they updated fine but I wasn't able to boot into any of them because I kept getting frozen at the white screen after choosing recovery from hboot. I will try another hboot and see if that makes any difference. Thanks.
Cmlusco, I tried the CWM version you posted with hboot .92 and .77 but had no luck. I also tried walking through the hboot upgrade steps on the htcdev site but I couldn't get the RUU exe to find my phone. This is odd because an older RUU found the phone just fine earlier today.

Bootloop of Death Without Recovery

Yes, it is another infinite boot loop thread. It was working fine this morning and I was reading a book with Aldiko, then I hit homescreen and locked. From that point it went into the loop.
Okay so I'm somewhat new to the modification scene i.e. I haven't worked with fastboot etc. but I have gathered from other threads some of the information you'll be needing.
Here is my info from the HBOOT screen
Code:
SUPERSONIC EVT2-3 SHIP S-OFF
HBOOT-2.10.001
MICROP-041f
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.11.19
Oct 15 2010, 12:07:00
So here are a couple of things I've tried already..
Using HBOOT to boot to recovery causes it to go back into the boot loop.
I originally had CWM Recovery, so I reflashed recovery (RA-supersonic-v4.3-smelkusMOD) successfully and attempted to then enter recovery mode with the same result - boot loop. I have not tried re-flashing CWM, but I would assume it would produce the same result.
I downloaded the RUU exe that corresponds to my radio, but when running the program it gives me a USB Connection Error code 170. It does mention that the phone has to be turned on, however in what capacity I can have it "turned on" I don't know.
Thank you in advance, please advise if there is any additional information needed.
Coldhands said:
Yes, it is another infinite boot loop thread. It was working fine this morning and I was reading a book with Aldiko, then I hit homescreen and locked. From that point it went into the loop.
Okay so I'm somewhat new to the modification scene i.e. I haven't worked with fastboot etc. but I have gathered from other threads some of the information you'll be needing.
Here is my info from the HBOOT screen
Code:
SUPERSONIC EVT2-3 SHIP S-OFF
HBOOT-2.10.001
MICROP-041f
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.11.19
Oct 15 2010, 12:07:00
So here are a couple of things I've tried already..
Using HBOOT to boot to recovery causes it to go back into the boot loop.
I originally had CWM Recovery, so I reflashed recovery (RA-supersonic-v4.3-smelkusMOD) successfully and attempted to then enter recovery mode with the same result - boot loop. I have not tried re-flashing CWM, but I would assume it would produce the same result.
I downloaded the RUU exe that corresponds to my radio, but when running the program it gives me a USB Connection Error code 170. It does mention that the phone has to be turned on, however in what capacity I can have it "turned on" I don't know.
Thank you in advance, please advise if there is any additional information needed.
Click to expand...
Click to collapse
It has to be booted up, being in bootloader won't allow ADB to connect to the device and thats why you're getting the error for the USB connection in the RUU
Try going into recovery (if you can) and clearing EVERYTHING
/data, /system, /cache, dalvik cache, /sd-ext (I would suggest multiple times, or superwipe it if you have that)
Sent from my PG06100 using xda premium
Thank you for the reply, CNexus.
I am unable to get into recovery, but I was able to obtain the rom.zip file that the RUU exe contained and flashed it by renaming it to PC36IMG.zip. The process of flashing was successful on all 6 parts, however, I still have the same issue unfortunately - infinite boot loop, and recovery still looping as well.
I think it may be time to throw in the towel with my Evo unfortunately, barring any information anyone else can provide.
I just am thankful that my upgrade is available on the 1st of the year - but due to extenuating circumstances I will make Sprint give it to me early :laugh:
Coldhands said:
Thank you for the reply, CNexus.
I am unable to get into recovery, but I was able to obtain the rom.zip file that the RUU exe contained and flashed it by renaming it to PC36IMG.zip. The process of flashing was successful on all 6 parts, however, I still have the same issue unfortunately - infinite boot loop, and recovery still looping as well.
I think it may be time to throw in the towel with my Evo unfortunately, barring any information anyone else can provide.
I just am thankful that my upgrade is available on the 1st of the year - but due to extenuating circumstances I will make Sprint give it to me early :laugh:
Click to expand...
Click to collapse
Ah that was a good idea, it sucks that it didn't work though
Good luck then, sorry about your phone
Sent from my PG06100 using xda premium

[SOLVED] Bootloop with no access to recovery (S-OFF)

SOLVED. THE PHONE IS BROKEN AKA HARDWARE FAILURE
Hi,
My old Desire had been sitting in my desk for about a year since i bought myself a Galaxy S2. Today, I decided to try it out. Charged the battery first and then tried to boot it. Well, I got stuck in the splash screen. The phone had been working normally the last time i used it (maybe 6 months ago?) so i thought it was weird. Then I tried to boot it into recovery, and got again stuck in the splash screen. HBOOT came up normally but after pressing the recovery button the phone just made the boot vibration multiple times and then was stuck in the splash screen.
What I have:
- Alpharev S-OFF HBOOT: bravo_alphaspl-oxygenr2.img
- Oxygen rom (don't remember the version but i have the zip on my computer): update-oxygen-2.1.6-signed.zip
- My current HBOOT screen shows the following:
--- AlphaRev ---
BRAVO PVT1 SHIP S-OFF
HBOOT-0.93.0001
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.27
Aug 10 2010, 17:52:18
- AFAIK the phone is the older AMOLED version (if that matters)
- I have a working ADB
- I dont have a goldcard
What I did after noticing the problem:
1. Read the sticky which told me to reflash my recovery.
2. Flashed the CWM 2.5.0.7 recovery via Android flasher. The program said it was successful but my phone was in a bootloop again without access to recovery.
3. Flashed the Amon Ra recovery via Android flasher. The program again said it was successful but the bootloop persisted.
4. Flashed both of the recoveries (one at time of course) via the adb fastboot command. Again, it was supposed to be successful, but the phone STILL was in the bootloop.
I thought the sticky explained my situation perfectly but apparently this is not the case
I have also a RUU lying around:
RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00. 32U_5.11.05.27_release
But I was hesitant to use it as I have the custom Alpharev HBOOT which might cause problems.
So what should I do now? I appreciate all advice.
Re: Bootloop with no access to recovery (S-OFF)
In my sig you'll find a thread with how to install 4ext recovery through pb99img. Check it out.
I DL'd the PB99IMG.zip file for the recovery and put it on my SD by moving the SD to my other phone and connecting it to my PC.
However, when the HBOOT searches for the PB99IMG.zip, it only says "No Image!".
Re: Bootloop with no access to recovery (S-OFF)
Are you sure you didn't put it in any folder?
Then, again in my sig, you'll find a partitioning guide. The first part of the guide will help you install a recovery. Try it.
Yes, I put it right in the root of the sd card.
The partitioning thread in your sig has a few methods of installing the recovery. But i have already tried them and for some reason they fail. I have now tried the Android flasher method, the ADB + Fastboot method and the PB99IMG.zip method. I have no clue why these should fail like i have described.
EDIT: Looks like I cannot run the RUU either. It says it failed to detect the device. What on earth could be going on when EVERY possible way of reinstalling the recovery fails? I was starting to think that maybe there was something wrong with my USB connection/drivers or ADB so I made a test and flashed another alpharev HBOOT (their bravo stock one: bravo_alphaspl.img) and the flashing procedure worked. So at least my ADB is working. Still no idea why the PB99IMG.zip just won't work... looks like my phone defies all these guides available here.
Update:
I downloaded the 2.3 GB RUU from the sticky topic. Suprisingly enough I could run it, it detected my device and went throught the whole RUU process without a single error. I booted the phone - and was again stuck in a bootloop. Went to HBOOT, chose recovery (the RUU should have flashed the stock recovery) but no, I could not get into the recovery. Instead the phone was again stuck in a bootloop. So I still cannot get into the recovery. The only thing that changed was the splash screen I was stuck on... (I had a custom splash, now it's the stock one)
I then formatted my SD, put the 4ext recovery PB99IMG.zip there and booted into HBOOT. This time It found the PB99IMG.zip. It asked if I wanted to update, I pressed yes and it went through it without any error. When it asked if i wanted to reboot, i pressed no, navigated into recovery and pressed the power button. This should have taken me to the 4ext recovery i just flashed successfully. And guess what? Bootloop again...
So after all this, I still do not have access to the recovery. I just get the bootloop every time. I've whacked around with android phones (mostly Galaxy S2 though) quite a lot but this far have never seen such a persistent problem which just evades all (for other people) working attempts to fix it. The procedures work exactly as described and give me no errors, but in the end the issue still persists: I cannot access the recovery because of the bootloop.
I was starting to wonder if it could be hardware failure causing this? Just a wild guess but the phone has been sitting in my desk for almost a year... I didn't change anything in the software. The only thing that comes to my mind is that the memory where the recovery and rom are stored is somehow corrupt. This would explain why I cannot get into the recovery even though i have reflashed it successfully multiple times. I also can change my HBOOT and splash screen.
Does anyone have any ideas left?
Re: Bootloop with no access to recovery (S-OFF)
Are you s-on now?
Yep,
At the moment i'm S-ON with the 2.3 RUU from your sig. Bootloader is 1.02.0001. I flashed the RUU from the PB99IMG. No errors. Still cannot get to recovery.
I then opened the phone and removed the mainboard but i could not see any damage at all. No burns, marks of water damage etc.
Re: Bootloop with no access to recovery (S-OFF)
As weird as it sounds, try putting the phone in the freezer without the battery for 10 minutes, then try to boot.
You are pretty good, man.
CASE CLOSED
Explanation: after putting the phone into the freezer for some time, I tried to boot. It booted normally to the ROM. Wifi worked, I could use internet, setup my settings etc. After 10 minutes the phone rebooted into a bootloop. This proves that the problem always was a hardware one, and this is why any software fixes couldn't solve the issue. Because i don't have a freezer in my pocket I can safely say the phone is broken and I can throw it away.
Thank you!

Categories

Resources