I downgraded my hboot to 0.97 in the hopes that I would be able to get S-OFF with revolutionary. I used tacoroot to gain root access, misctool to modify the misc_version so I can downgrade, and flashed the 2.3.3 Gingerbread RUU through hboot. Everything seemed fine so I went to use revolutionary to get S-OFF. After gaining root access my device was rebooted into fastboot where i got an error and revolutionary terminated. Now my phone gets stuck in boot loop. It gets to slide to unlock screen, but reboots seconds later. A factory reset temporarily solves the boot loop problem and the phone doesn't automatically reboot, but once I power down or reboot the phone the boot loop problem returns.
While looking through the forums I noticed that in several threads about boot loops members suggested updating the radio. So I tried flashing the .0312 radio. First I tried through hboot. It checks the zip like normal, but never provides me with the option to install or not. Next I tried through fastboot, but I get this: sending 'radio' <13225 KB>... FAILED <command write failed <Unknown error>>
I'm not sure if I'm doing something wrong or not. If it is indeed the radio that is the issue what am I doing wrong and if it's not does anyone have any ideas as to what wrong and how I can go about fixing it? Any and all help is greatly appreciated. Thanks.
kioji86 said:
I downgraded my hboot to 0.97 in the hopes that I would be able to get S-OFF with revolutionary. I used tacoroot to gain root access, misctool to modify the misc_version so I can downgrade, and flashed the 2.3.3 Gingerbread RUU through hboot. Everything seemed fine so I went to use revolutionary to get S-OFF. After gaining root access my device was rebooted into fastboot where i got an error and revolutionary terminated. Now my phone gets stuck in boot loop. It gets to slide to unlock screen, but reboots seconds later. A factory reset temporarily solves the boot loop problem and the phone doesn't automatically reboot, but once I power down or reboot the phone the boot loop problem returns.
While looking through the forums I noticed that in several threads about boot loops members suggested updating the radio. So I tried flashing the .0312 radio. First I tried through hboot. It checks the zip like normal, but never provides me with the option to install or not. Next I tried through fastboot, but I get this: sending 'radio' <13225 KB>... FAILED <command write failed <Unknown error>>
I'm not sure if I'm doing something wrong or not. If it is indeed the radio that is the issue what am I doing wrong and if it's not does anyone have any ideas as to what wrong and how I can go about fixing it? Any and all help is greatly appreciated. Thanks.
Click to expand...
Click to collapse
try typing this (in fastboot menu)
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip (name of zip)
kioji86 said:
I downgraded my hboot to 0.97 in the hopes that I would be able to get S-OFF with revolutionary. I used tacoroot to gain root access, misctool to modify the misc_version so I can downgrade, and flashed the 2.3.3 Gingerbread RUU through hboot. Everything seemed fine so I went to use revolutionary to get S-OFF. After gaining root access my device was rebooted into fastboot where i got an error and revolutionary terminated. Now my phone gets stuck in boot loop. It gets to slide to unlock screen, but reboots seconds later. A factory reset temporarily solves the boot loop problem and the phone doesn't automatically reboot, but once I power down or reboot the phone the boot loop problem returns.
While looking through the forums I noticed that in several threads about boot loops members suggested updating the radio. So I tried flashing the .0312 radio. First I tried through hboot. It checks the zip like normal, but never provides me with the option to install or not. Next I tried through fastboot, but I get this: sending 'radio' <13225 KB>... FAILED <command write failed <Unknown error>>
I'm not sure if I'm doing something wrong or not. If it is indeed the radio that is the issue what am I doing wrong and if it's not does anyone have any ideas as to what wrong and how I can go about fixing it? Any and all help is greatly appreciated. Thanks.
Click to expand...
Click to collapse
Did you check the md5 for the radio? Did you rename it to EXACTLY PG32IMG.ZIP? if using windows, make sure there's no extra .zip at the end. What did hboot say when it "checked" the file?
Give me some more info. We'll get you going.
Sent from my vivow using xda app-developers app
having the same issue
Ok so I'm a complete noob at this. I ran everything and it seemed fine up until i went to run revolutionary. Rev kept waiting for the device I let it sit for ten minutes. then I had the bright idea to program my phone with my number, thinking that might help. it then rebooted and started bootlooping. It's been constantly looping since. Please help.
*similar* issue
kioji86 said:
I downgraded my hboot to 0.97 in the hopes that I would be able to get S-OFF with revolutionary. I used tacoroot to gain root access, misctool to modify the misc_version so I can downgrade, and flashed the 2.3.3 Gingerbread RUU through hboot. Everything seemed fine so I went to use revolutionary to get S-OFF. After gaining root access my device was rebooted into fastboot where i got an error and revolutionary terminated. Now my phone gets stuck in boot loop. It gets to slide to unlock screen, but reboots seconds later. A factory reset temporarily solves the boot loop problem and the phone doesn't automatically reboot, but once I power down or reboot the phone the boot loop problem returns.
While looking through the forums I noticed that in several threads about boot loops members suggested updating the radio. So I tried flashing the .0312 radio. First I tried through hboot. It checks the zip like normal, but never provides me with the option to install or not. Next I tried through fastboot, but I get this: sending 'radio' <13225 KB>... FAILED <command write failed <Unknown error>>
I'm not sure if I'm doing something wrong or not. If it is indeed the radio that is the issue what am I doing wrong and if it's not does anyone have any ideas as to what wrong and how I can go about fixing it? Any and all help is greatly appreciated. Thanks.
Click to expand...
Click to collapse
I downgraded to 2.3.3 using the tacoroot method. Everything was acting fine after the reboot and I was about to run Revolutionary, but I got a bright idea to confirm I had gained a .97hboot so I shut the phone off and went into the bootloader screen. Yup I have .97hboot. Restarted phone. Boots normally but as others mention it restarts its self after a couple seconds on the lock screen. Hoping this isn't a permanent brick.
zombolt said:
Hoping this isn't a permanent brick.
Click to expand...
Click to collapse
Doubtful that it's bricked. Have you tried flashing a custom rom?
Sent from my Incredible 2 using xda app-developers app
Related
I'm trying to flash a splash screen but I'm getting the following error..
writing 'evosplash1'... FAILED <remote: not allowed>
Any ideas?
you dont normally flash a splash screen ussually you have a file named evosplash1.rgb565 (see if when you open the zip file you have this)
you then place that file in your android sdk/tools directory.
Boot into fastboot and in adb enter the command
fastboot flash splash1 evosplash1.rgb565
once done reboot the phone and you shoudl be set.
_Cooze_ said:
I'm trying to flash a splash screen but I'm getting the following error..
writing 'evosplash1'... FAILED <remote: not allowed>
Any ideas?
Click to expand...
Click to collapse
It's likely you have hboot 0.79, and you need to have hboot .76
when you boot into bootloader, look across the top couple lines, it says something like hboot or eng boot and then the number.
if you have .79 that's why you're getting that error.
Do a search for "splash" there's a lot of threads about this exact issue and how to go from eng boot .79 to .76
Or, click here: http://forum.xda-developers.com/showthread.php?t=752832&highlight=engineering+hboot
or here: http://forum.xda-developers.com/showthread.php?t=769841&highlight=splash
There was actually a good bit of people last night who were also running into this, though we all worked together to figure it out about the hboot version, and now i'm rocking a better then stock splash screen.
tomh1979 said:
There was actually a good bit of people last night who were also running into this, though we all worked together to figure it out about the hboot version, and now i'm rocking a better then stock splash screen.
Click to expand...
Click to collapse
Yeah, I can't even get my computer to recognize my phone while in bootloader.
ADB works fine while in the os, but when i boot into bootloader, no devices show up...it's driving me nuts.
glad to see it finally worked for you guys though.
I know at least 2 other people have had this happen so I wanted to make a central thread to troubleshoot and maybe fix it. Chime in with what you've tried and (hopefully) what worked.
After a failed attempt at downgrading my hboot, I'm stuck with no picture on the screen. I can only access my phone in fastboot and the official RUU .exe. When I try to run the exe, I can get as far as the phone rebooting into bootloader but then it just times out. In fastboot I have tried to flash a new hboot or boot image but get "failed image error" or somethng.
Any other ideas/solutions?
Did you try flashing a recovery through fastboot? There is a link to amon ra's thread in my sig that has directions on it
Sent from my PC36100 using XDA App
I had the same problem this weekend.
http://forum.xda-developers.com/showthread.php?t=839155
Apparently nobody knows what to do because I didn't get it fixed.
EDIT
That being said, today I gave up and took it to Sprint, said HTC told me to use a program to restore it to factory defaults (I was very vague about the RUU, tried to sound as unknowledgeable as possible), and it stopped midway (which is sort of the truth). The guy at Sprint tried to restore it using their program, but it wasn't working. He asked if it was rooted, I played dumb, and I'm getting a new one sent to me through the warranty for free.
If your NAND is locked again (S-ON) you will only be able to flash an update signed by HTC.
I'm assuming you had the 2.02 hBoot? If so place this on your SD card, rename it to PC36IMG.zip and then put it back in your phone. Hold vol down and boot into your bootloader like normal, and after a full minute push vol down. If all goes well it will flash everything the RUU would normally.
3.30.651.2_PC36IMG.zip
xHausx said:
If your NAND is locked again (S-ON) you will only be able to flash an update signed by HTC.
I'm assuming you had the 2.02 hBoot? If so place this on your SD card, rename it to PC36IMG.zip and then put it back in your phone. Hold vol down and boot into your bootloader like normal, and after a full minute push vol down. If all goes well it will flash everything the RUU would normally.
3.30.651.2_PC36IMG.zip
Click to expand...
Click to collapse
he wasnt getting into the bootloader...I had a phone that did this...I was able to recover using unrevokeds hboot drivers and the 3.30 ruu on a 32bit windoes 7box
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
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.
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.