Hi all,
chronological steps to bootloop after rebooting, when no os warning sign appeared.
Successfully Unlocked boot loader.
Successfully install twrp custom recovery
installing root wasn't successful.
Then I tried to check features of TWRP which resulted in always booting to recovery.
I might have deleted some data accidentally
Then after many attempts to restore to stock rom I flashed RUU 1.26 from guru's website ...
Phone booted but had touch screen issues.
In an attempt to fix I realized that I could only do with s-off and then tried to flash the correct RUU for 3.17.502.3 firmware but wasn't successful.
I realized the present RUU(1.26.X) might be the reason for all(any .zip) failures from twrp.
I tried to format system and push RUU for 3.17.502.3. But I accidentally rebooted when there was no OS warning came up. It got stuck in Bootloop with HTC logo. My attempts to power it down didn't work and when I press power button + volume down or just power button the led back lights on the home and back buttons flash.
firmware version 3.17.502.3
hboot 1.55 s-on
Phone shows up as HTC MTP device because of which adb/fastboot doesn't recognize the phone.
I guess this is what a brick is called. Is there a way to recover from this ?
Few questions:
1. How can I power off the device? Its been in bootloop for 6 hrs now. I'm afraid the screen will go bad
2. How can I use adb/fastboot in mtp modes to get it to power off / reboot to boot loader?
Thanks in advance.
PS: I have tried all these stuff(rooting, flashing custom recovery / kernels) on 3 samsung phones with out any issue, the procedure was much easier than it is for htc devices. After a day long attempt to root my phone I might have bricked it
Sriram
clrsri2006 said:
Hi all,
chronological steps to bootloop after rebooting, when no os warning sign appeared.
Successfully Unlocked boot loader.
Successfully install twrp custom recovery
installing root wasn't successful.
Then I tried to check features of TWRP which resulted in always booting to recovery.
I might have deleted some data accidentally
Then after many attempts to restore to stock rom I flashed RUU 1.26 from guru's website ...
Phone booted but had touch screen issues.
In an attempt to fix I realized that I could only do with s-off and then tried to flash the correct RUU for 3.17.502.3 firmware but wasn't successful.
I realized the present RUU(1.26.X) might be the reason for all(any .zip) failures from twrp.
I tried to format system and push RUU for 3.17.502.3. But I accidentally rebooted when there was no OS warning came up. It got stuck in Bootloop with HTC logo. My attempts to power it down didn't work and when I press power button + volume down or just power button the led back lights on the home and back buttons flash.
firmware version 3.17.502.3
hboot 1.55 s-on
Phone shows up as HTC MTP device because of which adb/fastboot doesn't recognize the phone.
I guess this is what a brick is called. Is there a way to recover from this ?
Few questions:
1. How can I power off the device? Its been in bootloop for 6 hrs now. I'm afraid the screen will go bad
2. How can I use adb/fastboot in mtp modes to get it to power off / reboot to boot loader?
Thanks in advance.
PS: I have tried all these stuff(rooting, flashing custom recovery / kernels) on 3 samsung phones with out any issue, the procedure was much easier than it is for htc devices. After a day long attempt to root my phone I might have bricked it
Sriram
Click to expand...
Click to collapse
UPDATE : The reboot to boot loader via power button + volume down works but it took about 2 mins of holding those buttons, which is unusually long time. So its not a brick As experienced developers say DO NOT PANIC, staying calm and read the forums thoroughly has helped.
I'm trying to see how I can fix the .zip install failures now.
Search for adb sideload, adb push or usb-otg
Sent from my HTC One using XDA Premium 4 mobile app
TopoX84 said:
Search for adb sideload, adb push or usb-otg
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
adb sideload isn't working though adb / fastboot work fine.
did try adb push a dirty unicorn rom and tried to install, just to test, it didn't work either
The problem i'm facing now is:
I have installed 1.26 RUU on 3.17.502.3 because that is the only RUU with cid CWS_001 which started all the issues.
From then i'm not able to install any zip files. Now that i deleted the system thinking i can flash another RUU I keep getting error: unable to mount cache. when ever i try to install something.This is one problem the other is for flashing an RUU i need s-off and for getting s-off i need to have ROM that matches with my firmware version(which i'm not able to get) Its kind of deadlock situation i guess.
As I have 1.55 hboot revone doesn't work and tools based on rumrunner fail at second test because when they reboot its going to fastboot usb mode and fails at that point.
clrsri2006 said:
adb sideload isn't working though adb / fastboot work fine.
did try adb push a dirty unicorn rom and tried to install, just to test, it didn't work either
The problem i'm facing now is:
I have installed 1.26 RUU on 3.17.502.3 because that is the only RUU with cid CWS_001 which started all the issues.
From then i'm not able to install any zip files. Now that i deleted the system thinking i can flash another RUU I keep getting error: unable to mount cache. when ever i try to install something.This is one problem the other is for flashing an RUU i need s-off and for getting s-off i need to have ROM that matches with my firmware version(which i'm not able to get) Its kind of deadlock situation i guess.
As I have 1.55 hboot revone doesn't work and tools based on rumrunner fail at second test because when they reboot its going to fastboot usb mode and fails at that point.
Click to expand...
Click to collapse
UPDATE : After many attempts I could work it out by using guru reset .zip file (1.26.502.12). I did this before as well but was not able to get s-off previously. This time I asked to install superuser when resetting using guru reset file. I got the 1.26 one back with disabled touchscreen. Then I used rumrunners and got s-off and then used the ruu for 3.17.502.3 exe file to get the working on.
Now the bootloader just says unlocked but not tampered. I got the twrp recovery again as it was very handy for me.
I was able to get supercid. Now trying for ARHD 51.0.
After I got the RUU for 3.17.502.3 the only issue i noticed is that when phone boots up I just see HTC instead of "HTC quitely brilliant"
Related
hi all
Forgot to charge my EVO 3D (CDMA) and battery completely drained. Even after using another fully charged battery my phone goes to bootloop - just shows the HTC logo and reboots again and again. Here is what I have:
hboot : 1.5 (S-ON)
radio : 1.06.00.1216
ota : 2_17.651_5
(I am using this phone in India activated on Reliance)
As the phone doesn't boot I can't access it thru adb to give command 'adb reboot bootloader'
I can get bootloader by pressing vol_down+power
When I run the 2_17.651_5 RUU (exe) from my computer while phone is on fastboot, it completes successfully without errors. But still on reboot it just stays at the htc screen and reboots (guess it's becoz stock kernel not getting flashed as the phone is s-on)
kindly help to get back my phone boot again
thanks and regards
ananth
R.I.P
Sent from my HTC.EVO.3D.Xda Premium
Don't listen to the previous guy. Try using fastboot OEM lock and then ruuing. Or, try getting freezas stock kernel and extracting the boot.IMG and flashing it thru fastboot. Or, you could use fastboot flash recover recovery.IMG to get twrp or clockworkmod and do a superwipe and try flashing a new Rom. There are tons of options if you still have fastboot.
Sent from my HTC popout book.
jdeoxys said:
Don't listen to the previous guy. Try using fastboot OEM lock and then ruuing. Or, try getting freezas stock kernel and extracting the boot.IMG and flashing it thru fastboot. Or, you could use fastboot flash recover recovery.IMG to get twrp or clockworkmod and do a superwipe and try flashing a new Rom. There are tons of options if you still have fastboot.
Sent from my HTC popout book.
Click to expand...
Click to collapse
Thanx for responding. As I mentioned earlier,I have already relocked and RUU'd the exe file,but though it runs without errors doesn't solve problem. Again as it is s-on doesn't permit to flash boot.img. Though I am able to flash twrp recovery, not able to get into recovery from fastboot. Thanks again, really appreciate your help.
ananth001 said:
Thanx for responding. As I mentioned earlier,I have already relocked and RUU'd the exe file,but though it runs without errors doesn't solve problem. Again as it is s-on doesn't permit to flash boot.img. Though I am able to flash twrp recovery, not able to get into recovery from fastboot. Thanks again, really appreciate your help.
Click to expand...
Click to collapse
You don't need to relock once you unlock the HTC way. Just unlock the phone then flash via fastboot the boot.img and then ruu if you want.
Sent from my PG86100 using Tapatalk
megabiteg said:
You don't need to relock once you unlock the HTC way. Just unlock the phone then flash via fastboot the boot.img and then ruu if you want.
Click to expand...
Click to collapse
thanks. extracted boot.img from freeza's kernel and flashed from fastboot after unlocking. But still doesnt solve problem. Can you give me a link for boot.img
Pleassssssse HELP !!!!!!
I have the exactly the same problem, a full reboot result in boot loop, and can not fix it by now.
I guest the phone is rooted before OTA, so OTA can not flash kernel successfully because the wrong signature, and the phone will not boot because the wrong kernel.
I have tried ruu, fastboot boot recovery.img and etc, all failed.
The key point is that, the phone is rooted and you tried OTA. HTC OTA must have a stupid bug, it can not recovery from a partial update, or automatically roll back becasuse of the partial update, dem!
Please have a look at the guide/flashing notes in my signature. If u r unlocked u are likely not entering recovery correctly.
If u are trying to flash the Ruu u have to be locked or relocked. If u cant boot to android, run the xhausx's full Ruu zip from bootloader.
Sent from my PG86100 using Tapatalk
mpgrimm2 said:
Please have a look at the guide/flashing notes in my signature. If u r unlocked u are likely not entering recovery correctly.
If u are trying to flash the Ruu u have to be locked or relocked. If u cant boot to android, run the xhausx's full Ruu zip from bootloader.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
1) flashed RUU (exe) after relocking - flash completed without errors
2) ran xhausx's full RUU zip (PG86IMG_2.17.651.5.zip) from bootloader (could get into bootloader by pressing volum_up + power button. adb cannot connect to phone (as phone does not boot), to run 'adb rebooot bootloader')
But still doesn't solve problem and phone keeps rebooting, apparently kernel has not flashed properly.
Please help !!!1
ananth001 said:
1) flashed RUU (exe) after relocking - flash completed without errors
2) ran xhausx's full RUU zip (PG86IMG_2.17.651.5.zip) from bootloader (could get into bootloader by pressing volum_up + power button. adb cannot connect to phone (as phone does not boot), to run 'adb rebooot bootloader')
But still doesn't solve problem and phone keeps rebooting, apparently kernel has not flashed properly.
Please help !!!1
Click to expand...
Click to collapse
You need to use the RUU 2.17 exe after you relock your phone... Then flash a copy of CWM or TWRP on it..
Then adb
fastboot boot recovery.img
Wipe and flash whatever you want
Just noticed u said India & carrier is reliance. Why would u be using a Sprint USA CDMA Ruu? Shouldn't u be using a GSM RUU version?
Sent from my PG86100 using Tapatalk
mpgrimm2 said:
Just noticed u said India & carrier is reliance. Why would u be using a Sprint USA CDMA Ruu? Shouldn't u be using a GSM RUU version?
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
I wonder the same thing all I saw was 1.5
Sent from my PG86100 using xda premium
mpgrimm2 said:
Just noticed u said India & carrier is reliance. Why would u be using a Sprint USA CDMA Ruu? Shouldn't u be using a GSM RUU version?
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Reliance has both CDMA as well as GSM service in India. Mine is a Reliance CDMA MDN.
thanks and regards
reaper24 said:
You need to use the RUU 2.17 exe after you relock your phone... Then flash a copy of CWM or TWRP on it..
Then adb
fastboot boot recovery.img
Wipe and flash whatever you want
Click to expand...
Click to collapse
Yeah , as I mentioned earlier, I also tried using the RUU 2.17 exe after relocking (RUU completed successfully without errors) , and flashed twrp recovery from fastboot . But still it's a no go.
(Again would like to repeat that I can't boot into bootloader from adb - adb cannot connect as phone doesn't android boot. I get into fastboot by pressing vol_down + power)
thanks all for your responses and help, hope you all will continue guiding me till I get this done.
ananth001 said:
Yeah , as I mentioned earlier, I also tried using the RUU 2.17 exe after relocking (RUU completed successfully without errors) , and flashed twrp recovery from fastboot . But still it's a no go.
(Again would like to repeat that I can't boot into bootloader from adb - adb cannot connect as phone doesn't android boot. I get into fastboot by pressing vol_down + power)
thanks all for your responses and help, hope you all will continue guiding me till I get this done.
Click to expand...
Click to collapse
Have you tried to just run the RUU like you said boot turn debug on .... Then go to hboot flash your recovery...
Then fastboot boot recovery.img.
This should work I have unrooted my phone 3 times already in the past month Trial and Error on my part adb always found my phone...
I am tryin to figure out what is going wrong on the last part with TWRP...
Since you said after you do that it was a no go? What happend ? Adb should still be working since you just flashed the recovery...
Anyways I hope you get it solved man I am tryin to figure this problem out.
Do you have a rom already ready to be flashed on your SD card?
Problem is, since i’m not able to android boot I can't reboot bootloader from adb, as I can't connect adb without the phone normal booting. When I boot it just stays at the HTC white screen.
I have flashed twrp recovery from fastboot, but when I give command 'fastboot boot <twrpxxxxx>.img it just boots back to the HTC splash screen
You can go back to complete stock if you rename the RUU file PG86IMG.zip and load onto the root of sd card. Get into bootloader with [power+volume down] and it will automatically detect and load the zip file. This can only be done if you are relocked. I did this in order to get the latest update. After you get back to stock you can unlock and root again.
Android Cowboy said:
You can go back to complete stock if you rename the RUU file PG86IMG.zip and load onto the root of sd card. Get into bootloader with [power+volume down] and it will automatically detect and load the zip file. This can only be done if you are relocked. I did this in order to get the latest update. After you get back to stock you can unlock and root again.
Click to expand...
Click to collapse
As I mentioned in earlier post, have tried flashing PG86IMG.zip from bootloader, but still phone doesn't boot properly and is in a bootloop.
You've used the following file and done these exact steps and allowed the phone to boot to full stock OS? (assuming 2.17.651.5 is correct version)
OPTION 2 - RUU.zip info:
I prefer the .exe version but xHausx’s “FULL” PG86IMG_2.17.651.5.zip may work for you (must be renamed PG86IMG.zip). Make sure you have plenty of battery/charge left!
- (XDA) Xhausx full PG86IMG.zip RUU images (651.5 zips)
PG86IMG_2.17.651.5.zip http://forum.xda-developers.com/showpost.php?p=21593454&postcount=564
MD5: 8F82C2D8F98C077AF775266064BACB5D
From Scrosler's zip Directions : http://forums.androidcentral.com/htc-evo-3d-rooting-roms-hacks/107641-how-return-100-stock-all-versions.html
Scrosler; said:
USE ONLY FOR EMERGENCY PURPOSES. THIS OVERWRITES EVERYTHING!!!!
**THIS WILL RETURN YOU TO FRESH OUT OF THE BOX**
You will not need any special drivers loaded, etc...
1.Download the stock ROM ZIP image from here: and rename it "PG86IMG.zip"
2.Copy it to SD Card
3.Reboot phone into hboot mode by holding volume down and then press power.
Keep volume down held until you boot into hboot mode.
4.In hboot mode the phone will scan the SD card with the image. Once it finds it will ask you if you want to update. Press "Power" to update.
5.Wait.... For a while. When it gets to "system" it will loop a few times. Its quite nerve wracking actually but after about 5 or 6 times it will complete.
6.Once the entire flash is complete it will prompt you to "press power to reboot." Press power and your phone will reboot to 100% stock ROM.
Click to expand...
Click to collapse
Hey all,
so i had cleanrom ics installed on my 3vo. i installed it without freizas firmware.
anyways, due to pink camera issues, i needed to get the phone replaced, so i tried downgrading with the 1.13 pg86img (this was before i learned about the downgrade issues).
the system part of the update failed, which made my phone not able to boot past the initial HTC screen.
i then tried installing freizas pg86img to get my phone in working order again. the installation worked, but i still cant boot past the htc screen.
i can boot into the bootloader and access recovery (although its the stock htc recovery so i cant use it), and still have s-off.
any help would be greatly appreciated
alexjzim said:
Hey all,
so i had cleanrom ics installed on my 3vo. i installed it without freizas firmware.
anyways, due to pink camera issues, i needed to get the phone replaced, so i tried downgrading with the 1.13 pg86img (this was before i learned about the downgrade issues).
the system part of the update failed, which made my phone not able to boot past the initial HTC screen.
i then tried installing freizas pg86img to get my phone in working order again. the installation worked, but i still cant boot past the htc screen.
i can boot into the bootloader and access recovery (although its the stock htc recovery so i cant use it), and still have s-off.
any help would be greatly appreciated
Click to expand...
Click to collapse
Use adb to push a recovery.img to your phone then boot into it and flash a nandroid back up.
ehurt152 said:
Use adb to push a recovery.img to your phone then boot into it and flash a nandroid back up.
Click to expand...
Click to collapse
after trying to push the latest clockworkmod with fastboot, i got this:
sending 'recovery' (4726 KB)...
OKAY [ 1.118s]
writing 'recovery'
FAILED (remote:not allowed)
finished. total time: 1.151s
im stuck
If your s-off try running an ruu with the same hboot you have. If it boots up go check usb debugging. Then try to push the recovery via adb or fastboot flash one.
#Root-Hack_Mod*Always\
laie1472 said:
If your s-off try running an ruu with the same hboot you have. If it boots up go check usb debugging. Then try to push the recovery via adb or fastboot flash one.
#Root-Hack_Mod*Always\
Click to expand...
Click to collapse
will an ruu run if i cant boot into the system? if so what should i boot into to get it working
edit: after doing lots of flashing, i was able to boot into the system with the 2.08 ruu. it upgraded my hboot to 1.5 and locked my bootloader, but i still have s-off. i was unable to change the recovery image, it kept failing, so i tried flashing an older ruu to unlock my bootloader. again i got the hboot back to 1.4, but the system part of the update still failed.
any help would be greatly appreciated
You should just flash a recovery threw hboot. Here's the latest twrp hboot.zip
http://db.tt/Zw4KCyW2
Drop it on your sd. Then power the phone off. Then press and hold the volume up button. Then tap/press the power button. Continue to hold the volume up button untill you see a white screen. Then wait you phone should recognize the zip. Follow the on screen instructions from there.
#Root-Hack_Mod*Always\
I've been trying everything I could find to root my wife's HTC Rhyme and nothing works. I tried flashing a custom RUU and now it won't boot. It just hangs at the white HTC screen. Now, I can only get to the bootloader.
The only thing that I've been able to do successfully is unlock/relock the bootloader. This is my wife's phone and I really want to root it so that she can have the benefit of being able to completely backup everything. However, at this point, I just want to get the damn phone to work again.
PLEASE... Any help would be greatly appreciated.
Thanks!
I'm still working on this. I'm finding a few hits on Google for this kind of issue but nothing seems to be working.
Please... anyone with any input at all would be helpful.
Thanks.
Boot into fastboot and run your device's RUU from your PC.
Hi... I tried to run the RUU application from my PC several time but it always fails with an error message saying that the "WRONG BOOTLOADER VERSION".
Thanks for your reply anyway.
********** UPDATE **********
I got it to boot-up normally.
I used the method explained here to extract the boot.img file and flashed it in fastboot.
I still have no recovery though. I really want to root this phone or at least get a recovery on it that I can create nandroid back-ups with.
RuLEoF2 said:
Hi... I tried to run the RUU application from my PC several time but it always fails with an error message saying that the "WRONG BOOTLOADER VERSION".
Thanks for your reply anyway.
********** UPDATE **********
I got it to boot-up normally.
I used the method explained here to extract the boot.img file and flashed it in fastboot.
I still have no recovery though. I really want to root this phone or at least get a recovery on it that I can create nandroid back-ups with.
Click to expand...
Click to collapse
If you have S-OFF, you should be able to flash CWM and root your device.
Problem fixed.
I was able to extract the stock recovery and boot image from the RUU application and flash them from fastboot.
Recovery is back and it's booting normally again.
RuLEoF2 said:
Problem fixed.
I was able to extract the stock recovery and boot image from the RUU application and flash them from fastboot.
Recovery is back and it's booting normally again.
Click to expand...
Click to collapse
plx tell me step by step my htc rhyme is bricked and the phone cmpltly dead plx help me
i was previously running Meanrom 6.4 rooted S-ON and i decided to S-OFF my phone
i have RUU my phone and unlock the bootloader through dirtyracun s-off but when i was about to run the final step which is RabiesShot.exe(to S-OFF), my laptop have barely any battery left so i decided to not do that for the time being.
after that, I am still running the RUU 2.13.651.1 - HBOOT 1.19 without Root or any mods.
I decided to flash the "PJ75IMG - Stock Kernel". i renamed it to PJ75IMG and put it on my sdcard and it did successfully flash.
the problem is that my phone wont boot past Sprint Logo(it would suddenly black screen of death).
also, since i have no way of removing the PJ75IMG on the SD card, everytime i try to access recovery, it automatically tries to flash that file then it would exit and reboot automatically.
the only way for me to skip that part is to remove the sdcard.
my TWRP is also gone so i cannot flash any roms.
i have no card reader so i cannot place any stuff on my micro sd. :crying:
i though about downgrading the kernel to the previous working version through fastboot but when i looked for the files, they say downgrading would result in a brick.
is there any way i can maybe fastboot jellybean or ics or the kernel to make my phone work again?
edit:
if i did flash the Jellybean with my current kernel, is there a way to achieve S-OFF?
i also havent found stock jellybean rom that isnt rooted
Just...
raclimja said:
i was previously running Meanrom 6.4 rooted S-ON and i decided to S-OFF my phone
i have RUU my phone and unlock the bootloader through dirtyracun s-off but when i was about to run the final step which is RabiesShot.exe(to S-OFF), my laptop have barely any battery left so i decided to not do that for the time being.
after that, I am still running the RUU 2.13.651.1 - HBOOT 1.19 without Root or any mods.
I decided to flash the "PJ75IMG - Stock Kernel". i renamed it to PJ75IMG and put it on my sdcard and it did successfully flash.
the problem is that my phone wont boot past Sprint Logo(it would suddenly black screen of death).
also, since i have no way of removing the PJ75IMG on the SD card, everytime i try to access recovery, it automatically tries to flash that file then it would exit and reboot automatically.
the only way for me to skip that part is to remove the sdcard.
my TWRP is also gone so i cannot flash any roms.
i have no card reader so i cannot place any stuff on my micro sd. :crying:
i though about downgrading the kernel to the previous working version through fastboot but when i looked for the files, they say downgrading would result in a brick.
is there any way i can maybe fastboot jellybean or ics or the kernel to make my phone work again?
edit:
if i did flash the Jellybean with my current kernel, is there a way to achieve S-OFF?
i also havent found stock jellybean rom that isnt rooted
Click to expand...
Click to collapse
If i were you, i would go back through the s-off process if you can, that will get you back to stock and s-off, then install latest twrp, and then instal OMJ's custom release of the new JB update, it will give you root and the new update, Install the radios since you are s-off and you are good to go.
You need to finish that last step to gain s-off though lol. You should have waited.
Also, im not sure if that is just the kernel, but if it is, just the kernel and nothing else. Then you should be able to do s-off fine still.
Someone correct me if im wrong, i just learned this whole s-off process today so i could do the update.
igotlostintampa said:
If i were you, i would go back through the s-off process if you can, that will get you back to stock and s-off, then install latest twrp, and then instal OMJ's custom release of the new JB update, it will give you root and the new update, Install the radios since you are s-off and you are good to go.
You need to finish that last step to gain s-off though lol. You should have waited.
Also, im not sure if that is just the kernel, but if it is, just the kernel and nothing else. Then you should be able to do s-off fine still.
Someone correct me if im wrong, i just learned this whole s-off process today so i could do the update.
Click to expand...
Click to collapse
the thing is the phone wont even boot past the HTC Logo then it would display black screen of death
edit: i found through google saying the error is rekated to the kernel version and i should downgrade first.
is there any safe/reliable method of downgrading the latest kernel from ota (i did not flash the one with the latest hboot but i am still s-on)
i tried to Fastboot RUU but i got an error saying FAILED (remote: 43 main version check fail)
Fix boot loop after jellybean firmware update via bootloader
raclimja said:
the thing is the phone wont even boot past the HTC Logo then it would display black screen of death
edit: i found through google saying the error is rekated to the kernel version and i should downgrade first.
is there any safe/reliable method of downgrading the latest kernel from ota (i did not flash the one with the latest hboot but i am still s-on)
i tried to Fastboot RUU but i got an error saying FAILED (remote: 43 main version check fail)
Click to expand...
Click to collapse
I had the same problem.
1.remove the PJ75IMG file from exrtenal sd card.
2.reboot to fastboot pres factory reset
3. immidietly press and hold volume down, this should get you to recovery.
4. wipe
5. restore a backup rom
6.reboot
It worked for me after hours of trying other methods.
I just went through a bootloop mess. What i did to get my phone back was to use fastboot and use commands (on my pc) like
fastboot flash recovery recovery.img (for TWRP)
fastboot flash boot boot.img (for Kernel)
That got my phone back up and working.
Have you tried this?
raclimja said:
the thing is the phone wont even boot past the HTC Logo then it would display black screen of death
edit: i found through google saying the error is rekated to the kernel version and i should downgrade first.
is there any safe/reliable method of downgrading the latest kernel from ota (i did not flash the one with the latest hboot but i am still s-on)
i tried to Fastboot RUU but i got an error saying FAILED (remote: 43 main version check fail)
Click to expand...
Click to collapse
ok i believe, fastboot should get you twrp. As will it get you the boot flash.
Fastboot flash zip (latest twrp)
Fastboot flash boot (ICS sense rom's boot.img extracted from zip) (this will get you the kernel)
Reboot hold vol down and power to get to bootloader
select recovery
Twrp wipe and flash ICS rom you got the boot img from. (this will take a bit because it wont install kernel, but you already have it from step 2)
you should boot into the rom. then re-do Dirty Raccoon installation, go all the way through, and you should now be s-off
re-install twrp
Flash radios in bootloader (fastboot flash zip (.zip for radios) (link one from Original android development jelly bean flashables post) (optional)
Go to twrp, factory reset, wipe cache, wipe dalvic, wipe syste.
Twrp Flash OMJ's custom JB release of this update, or stock with goodies, or jewel-swag.
Wipe cache/Dalvic
reboot.
I think this should work but i would immagine you've tried it already. Im running the new kernel and am experiencing no problems with it.
If you're s-off just use fastboot to flash a new kernel, no need to do a factory reset or anything else.
The kernel and ROM must be installed as a pair, just upgrading one isn't going to work.
SOLVED
Hey, I have htc evo 3d gsm (shooteru). I unlocked the bootloader using htcdev.com and installed clockworkmod recovery. Then I changed cid to HTC__001 and tried to flash a gingerbread ROM in preparation for using the flashmaniac tool to downgrade my hboot (1.53.0007 -> 1.49.0007).
But when I tried to flash the gb rom the recovery said that installation finished but the phone did nothing after reboot. So I took out the battery and went into bootloader and everything looked the same as before the flash attempt. So I tried once again with same result. Then I powered off the phone and now when I turned it on again it only shows the HTC logo for a few seconds and then nothing (the buttons at the bottom have their lights turned on though).
Any ideas?
Yes, hboot version not compatible with gb rom, and or boot partition didn't get flashed. Unlocked but s-on doesn't let boot partition have write if booted into recovery in a normal way.
So yoy can get boot.img from install zip and flash with fastboot
fastboot flash boot boot.img
Or you can reinstall from recovery if booted from fastboot command.
fastboot boot recovery.img
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
jcfunk said:
Yes, hboot version not compatible with gb rom, and or boot partition didn't get flashed. Unlocked but s-on doesn't let boot partition have write if booted into recovery in a normal way.
So yoy can get boot.img from install zip and flash with fastboot
fastboot flash boot boot.img
Or you can reinstall from recovery if booted from fastboot command.
fastboot boot recovery.img
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
Click to expand...
Click to collapse
Somehow got it at least to bootloader, no idea how, just tried taking out battery a few times and charging it a bit and it worked.
Thanks for the advice, didn't realize there was a difference between these flashing methods.
randomguyhtc said:
Somehow got it at least to bootloader, no idea how, just tried taking out battery a few times and charging it a bit and it worked.
Thanks for the advice, didn't realize there was a difference between these flashing methods.
Click to expand...
Click to collapse
Power + volume down when turning on will get you into bootloader
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
jcfunk said:
Power + volume down when turning on will get you into bootloader
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
Click to expand...
Click to collapse
I know , it just didn't work for some reason before.
So I flashed the boot.img and now it's stuck in a boot loop. Tried going to cwm recovery and wiping various caches etc and flashing again, and flashing boot.img again but it still goes into boot loop.
I would just use the flashmaniac's tool anyway because I don't care about any data on the phone or anything, but it seems that it requires the phone to be booted before it can start the downgrade.
What should I do? Try to flash other roms maybe? The one that I have now is EU_Shooter_U-1.20.401.8_ROOTED.
So I extracted a rom.zip from a RUU but it won't flash from cwm "Can't open /sdcard/rom.zip (bad)", should I try to flash it with adb/fastboot? I'm worried that the zip may be broken (even though archive manager integrity check says its fine).
Would this work with shooteru/GSM?
[TOOL] Ultimate Recovery Tool 3.1 (Unbrick, Downgrade, VM Radio Fix/Reset)
I'm thinking it might be a way to sidestep the boot loop problem that I have now, just relock the bootloader and follow the instructions until I get HBoot 1.40.something like the guy in the video?
Do I need some special drivers when using the RUU executables on Windows?
So I've got it to work. The problem was what jcfunk said (both of the things he mentioned, actually), I was trying to flash a GB rom when I should have tried an ICS rom instead (lol). After going to ICS RUU, I did the wire trick (unlimited.io) and now everything works nicely and I can get the latest roms.
Glad to hear.