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
Related
So I've been having a lot of issues lately with my connectivity. My process of troubleshooting involved updating my radios (as suggested in the deckmod instructions), and also updating the PRL.
However, when I attempted to flash new radios, the update took. After the device initially rebooted after applying the update - it just sat at the HTC Evo 4G white boot screen. It won't go anywhere.
I tried booting into recovery, but again it just sits at that white "HTC EVO 4G" screen.
I used the file here: http://forum.xda-developers.com/showthread.php?t=715485
I've had it sit for about a half hour, and nothing. So, I'm guessing the file itself was corrupted.
Luckily I can still get into the bootloader - can I just try and redownload the file?
See if the info in your Hboot shows the new radio version, for one. If you're getting to the white screen, you're not bricked. Try reflashing recovery via the pc36img. And I'd suggest Amon Ra. if you can get into recovery after that, clear Dalvik & Cache, and try to boot.
If nothing, go back to recovery, wipe everything but the SD Card and reflash your ROM
HipKat said:
See if the info in your Hboot shows the new radio version, for one. If you're getting to the white screen, you're not bricked. Try reflashing recovery via the pc36img. And I'd suggest Amon Ra. if you can get into recovery after that, clear Dalvik & Cache, and try to boot.
If nothing, go back to recovery, wipe everything but the SD Card and reflash your ROM
Click to expand...
Click to collapse
Radio does not look like it is updated. Tried reflashing amon-ra and had no success at all. The phone still freezes at the white htcEVO 4G screen that appears immediately after pressing the power button or trying to load recovery.
Just cleared storage from the bootloader, will try reflashing the rom. I'm just concerned about the fact I can't get into recovery at all.
Ok, still can't get into recovery. I tried copying the ROM to the sd card as PC36IMG.zip and the bootloader does nothing with it... I'm kind of stuck. Anyone have any other ideas?
Which bootloader version do you have? I think in that same thread, there're links to reflash the bootloaders, too. You may want to see if you can do that, although it seems like flashing anything isn't working out.
Another thing, is to try the pc version of the RUU for your phone, if nothing will flash in bootloader
HipKat said:
Which bootloader version do you have? I think in that same thread, there're links to reflash the bootloaders, too. You may want to see if you can do that, although it seems like flashing anything isn't working out.
Another thing, is to try the pc version of the RUU for your phone, if nothing will flash in bootloader
Click to expand...
Click to collapse
Here is what the bootloader says:
SUPERSONIC EVT2-3 SHIP S-OFF
HBOOT-2.10.0001
MICROP-041f
TOUCH PANEL-ATMEL03_16ac
RADIO-2.15.00.0808
OCT 15 210, 12:07:00
How can I flash the bootloader without being able to access recovery? The PC version requires my phone to be on, so unless fastboot will work, I'm not sure how well it'll work but at this point I will try anything.
EDIT: Holy crap, the RUU is working. When i tried the first few times while at the bootloader screen that it couldn't find my phone. So I put the phone into fastboot, and voila, the RUU saw it. Its updating now. I'll look at re-rooting it later today. Thank you so much for your help HipKat.
msarro said:
Here is what the bootloader says:
SUPERSONIC EVT2-3 SHIP S-OFF
HBOOT-2.10.0001
MICROP-041f
TOUCH PANEL-ATMEL03_16ac
RADIO-2.15.00.0808
OCT 15 210, 12:07:00
How can I flash the bootloader without being able to access recovery? The PC version requires my phone to be on, so unless fastboot will work, I'm not sure how well it'll work but at this point I will try anything.
Click to expand...
Click to collapse
Just so you know, that is the latest radio, unless you typed it wrong.
Sent from my PC36100 using Tapatalk
msarro said:
EDIT: Holy crap, the RUU is working. When i tried the first few times while at the bootloader screen that it couldn't find my phone. So I put the phone into fastboot, and voila, the RUU saw it. Its updating now. I'll look at re-rooting it later today. Thank you so much for your help HipKat.
Click to expand...
Click to collapse
If you rooted with unrevoked3 or flashed unrevoked forever as part of your root process, you should remain s-off. You can just reflash your recovery and restore a backup or flash a rom.
Glad you got the phone working!
Sent from my PC36100 using Tapatalk
You beat me to it. With Hboot 2.10, he had to have used Unrevoked, so he'll still be S-Off.
Glad it worked. I was gonna say put 'er in fastboot to run RUU, but you figured it out.
My htc evo all of the sudden it doesnt want to start it just staying on the htc white screen and then vibrates and it restarts itself I tried installing a ruu rom and sitll the same, tried to install a recovery app and it wont take it I get a message saying that the image is invalid. Plz someone help me I havent slep and been looking and looking and I havent found something that can help me with my problem
Heres some info from the Hboot screen
Supersonic EVT2-3 Ship S-on
Hboot-2.16.0001
Microp-041f
Touch Panel-Atmelc03_16ac
Radio-2.15.00.0808
any ideas will help
Same prob
Have you had any luck? I'm in the same boat, I've tried just about everything... I sold my phone to someone and they tried installing muiu rom and it quit working for them and they sent it back to me... And now I just want to get it working so I can use it and sell my iPhone and get a new android!! I hate the iPhone.
What exactly were you trying to achieve switching RUU's?
did you make sure it was for phones that were not rooted?
I havent had any luck and well I tried the Ruu that it wasnt rooted and it went all the way but the same thing keeps on happening
I am having this issue as well, about 12 hours after switching roms to cm9 nightly (unofficial) from the roms section, everything was working just fine, all was well. I had spent some time getting the rom set back up the way i like it, and had finished, while waiting in line at a restaurant I opened a bookmark from ics browser plus app and the phone rebooted itself. it just loops through the white screen, goes black, and then back to the white screen. I can get to hboot, but not to recovery, selecting recovery just goes back to the loop. I tried clearing user data via hboot, I tried reinstalling recovery (both amon-ra and twrp). the recovery installs ok according to the screen, but then trying to go back to recovery causes the loop to return. I do not know what else to try. (in my case, the phone does still show s-off and always has throughout the problems)
Any ideas or help would be greatly appreciated.....
is there a way to try and flash a rom thru ABD since im not able to go into recovery and i have S ON??? but my bootloader is unlocked already
areskorn said:
is there a way to try and flash a rom thru ABD since im not able to go into recovery and i have S ON??? but my bootloader is unlocked already
Click to expand...
Click to collapse
You're gona ned to get to s-off sot hat adb and mount the system if needed. Since you have the 2.16 bootloader, head over to revolutionary.io to get to rooting tools.
UPDATE
After trying different things now my HBOOT says 2.18.0001
Radio 2.15.00.12.19 and at the top it says unlocked, how can I S-off if i cant go inside the phone?
Now you're S-Off, flash a recovery and see if you can into Recovery and flash a ROM.
BTW, what ROM were you using when this started?
areskorn said:
UPDATE
After trying different things now my HBOOT says 2.18.0001
Radio 2.15.00.12.19 and at the top it says unlocked, how can I S-off if i cant go inside the phone?
Click to expand...
Click to collapse
If the top of the screen says S-Off, stop right there. Go to the dev section > download and flash a recovrey via PC36IMG.zip > then flash a rom.
for S+G's try pulling battery and removing sd card before rebooting without it
sorry but I havent had time to get online but now it says
S-ON
HBOOT-2.18.0001
MICROP-041f
RADIO-2.15.00.12.19
Dec 21 2011,
I still cant get the s-off tried different times, the recovery still doesnt work i try to select recovery sometimes it stays on a black screen sometmes it just starts rebooting itself
I tried installing a recovery thru fastboot and it says that it was finished and everything but when I select recovery it stays on the htc evo 4g white screen and it doesnt do anything after that
try to get S-Off useing revolutionary, once you get it ,Get smelkus-mod-4.3 recovery. Flash it through H-Boot, If you can get it to flash then your good to go. Just a note, Twerp is a badass recovery but twerp anc CWM dont really play well with the Evo 4g,,,Later,,,
areskorn said:
I tried installing a recovery thru fastboot and it says that it was finished and everything but when I select recovery it stays on the htc evo 4g white screen and it doesnt do anything after that
Click to expand...
Click to collapse
Try flashing it through the bootloader using the file attached here.
I tried flashing the image and it did detect it, but it wont go into it after I select recovery it restarts once by itself then goes into a black screen and I cant see anything there
i appreciate all the help that has been provided to me, has anyone else been thru the same thing if so what is the fix to this nightmare
areskorn said:
I tried flashing the image and it did detect it, but it wont go into it after I select recovery it restarts once by itself then goes into a black screen and I cant see anything there
Click to expand...
Click to collapse
So it detected it, but did you actually tell it to flash?
This happened to me after a dead battery. I was worried but a Phillip charge and then it booted up
Sent from my PC36100 using xda premium
It did flash it and everything but when I select recovery it restarts itself over and over again
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.
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!
I know there are a million threads about this but I haven't found the right files to work with what I have.
My Evo4g has:
Supersonic EVT2-3 SHIP S-OFF
HBOOT 2.10.001
RADIO 2.15.00.11.19
Two nights ago after I plugged in my phone to charge for the night it randomly rebooted and has been stuck rebooting on the HTC splash screen. If I try to go into recovery it goes to the same splash screen, goes black, back to the splash screen, etc.
I've tried to flash a new recovery but when I try to fastboot I get a failed message and I think it's because the recovery file I have may be for a different radio/hboot combo.
Any help you can give would be appreciated.
Thanks everyone!
Update.... still no success
I tried to do a complete reset on the phone by taking out the SD Card, coping over the PC36IMG.zip file I used when I first rooted the pone and doing the update. The update completed successfully but the phone is still stuck in the reboot cycle, even in recovery mode. This is the thread I followed when I first rooted my phone earlier this year howtoroothtcevo235withbootloader218.blogspot.com/2012/05/this-is-my-guide-on-how-to-achieve-s.html
If anyone has any ideas I would appreciate it. Right now I'm stuck and don't know what else to try.
archca said:
I tried to do a complete reset on the phone by taking out the SD Card, coping over the PC36IMG.zip file I used when I first rooted the pone and doing the update. The update completed successfully but the phone is still stuck in the reboot cycle, even in recovery mode. This is the thread I followed when I first rooted my phone earlier this year howtoroothtcevo235withbootloader218.blogspot.com/2012/05/this-is-my-guide-on-how-to-achieve-s.html
If anyone has any ideas I would appreciate it. Right now I'm stuck and don't know what else to try.
Click to expand...
Click to collapse
Try a newer PC36IMG.zip, like the 4.54.651.1.
Captain_Throwback said:
Try a newer PC36IMG.zip, like the 4.54.651.1.
Click to expand...
Click to collapse
Thanks for the idea. I've tried "PC36IMG_SuperSonic_GB_Sprint_WWE_4.54.651.1_Radio_2.15.00.0808_NV_2.15_release_220182_signed" which changed my HBoot to 2.16.0001 but the phone is still stuck in the boot loop and I can't get into recovery.
My current system stats are:
HBoot 2.16.0001
Radio 2.15.00.0808
UPDATE:
So, I think I may be out of luck. From what I've been reading around the forums, if what I've tried doesn't work then the phone most likely has a hardware issue and is dead. I'm going to get a new phone but if someone has any ideas I'd love to resurrect this one.