listen this is my last resort, i did everything I possibly could before coming here. & I searched people I freaking searched and ive tried every method I came across that related to my issue specifically, where the users found resolution. That being said, NONE of them worked for me. So i am not going to detail everything ive tried in the last 120+ hours dedicated to this issue in the last 10 days, so please understand that if your solution is one that is commonly/easily found online, chances are ive tried/applied but to no avail. Now to my issue, my specs are provided on the attached pic, but its hboot 1.58.0 radio is 1.09.00.0108 S-On & relocked bootloader, it was rooted with S-off but I am not sure if it is still rooted after the many attempts to get this device up & running. So now what happened, this is an inactive device of mine & i havent had it long, its mint condition tho and worked fine when i got it originally. I have an evo 4g as well and thats the whole reason i wanted the 3d. Ok, so I unlocked the bootloader thru htcdev & I rooted the 3d with s-on of course cause i am on 1.58. But then 2 critical things happened. When i got the 3d it wouldnt charge fully. it would charge til a green light but the battery would never show anything over 85% and either way i was flashing a rom and the battery just died when it supposedly had well over 50%. oh & btw, the rom was cynmod V? but the zip file is called "wild-for-the-night", which I have since learned wouldnt have worked anyway. & Then all of sudden the 3d wouldnt charge or turn on, but the orange light would act a specific way that I found others experiencing all over the web, but none of their solutions worked for me and i spent alotta f-ing time with the batt issue, that is until the new batt i ordered arrived, & solved the issue entirely. either way from that point on it will only boot into fastboot/bootloader. no recovery no rom, its not happening. In fact when I plug it in to a pc or to charge it wont stay powered down, it boots str8 into fastboot & simply wont stay off while plugged in live. but it does show its charging while plugged in. anyway I relocked bootloader so I could run the ruu and thats just not happening either. the 3d is updated to 2.89.651.5. At one point I followed methods to downgrade hboot to get s-off & I flashed hboot 1.4 or 1.5 in my attempts to downgrade but I lost that page with the exact instructions i was following and I havent been able to find it again, and ontop of that I lost the files I had downloaded to a usb that has been formatted since.. But regardless, it still shows 1.58, I just thought it might be relevant that I did attempt to flash an earlier version but things clearly havent worked out for this device. Adb doesnt seem to be recognizing the evo 3d & wont even show up as a connected device. fastboot is recognizing the evo tho, however when I try to unlock the bootloader thru htcdev, now it gives me an error talking about the unlock code isnt long enough or somwething like that. I can take a screenshot of it if needed. I really just wanna get this device back to an oem/stock condition, & then be able to follow methods that ive since come across to root with s-off. Please Help
Related
I've got a bad feeling that it's beyond help, but I'm hoping someone may be able to help.
I just tried to flash the engineering bootloader. It LOOKED like it completed successfully, however, when my phone restarted, I got nothing. Blank screen, no backlight.
I cannot boot into recovery, hboot, fastboot. Any attempt at booting my Eris into anything results in a black screen, almost like it is off.
I'd almost think it was completely fried, except for this. If I completely shut it off by removing the charger & battery, then replacing the battery and plugging it in, the orange LED comes on, like it's charging normally. It will even turn green if I leave it plugged in long enough, like it's fully charged. If I leave it plugged in and try to turn it on, the charging LED goes off. Still no screen or anything, but the LED will stay off until I remove & reinsert the battery.
I'm really drawing a blank here. I've searched this forum and google to no avail.
Will your computer recognize it? I have not tried to install a different boot loader but I believe I saw it can be done through sdk.
Sent from my KaosFroyo V39 Eris using XDA
I've got a bad feeling too.
Everything else on the phone gets launched by the bootloader, so if the bootloader goes, there goes the phone.
Would you mind saying how you were trying to replace the bootloader? (What the exact steps you attempted?) Did you take any special precautions about charging the battery beforehand, or performing any checksum verifications of any files you used? What instructions were you following?
When you pull the battery out, make sure that you also remove the charger cable so that no power is trickling into the phone that way. With the battery out, press all the buttons (one at a time or together, doesn't matter). Then reinsert the battery, and put the phone on the AC charger.
Then try seeing if anything will happen with any of the following key sequences (you might want to do the battery/charger disconnect between each attempt to be thorough):
Vol-Down+End (HBOOT)
Send+End (FASTBOOT)
End (Normal Boot)
If you get no response from any of those, the only other possibility (other than the phone being dead) is a problem with the battery. If you have a friend with an Eris you could try swapping batteries.
Given that the problem cropped up immediately after you were attempting to fool with the bootloader though suggests that you probably did brick your Eris.
sorry.
Computer won't recognize it.
bftb0 said:
I've got a bad feeling too.
Everything else on the phone gets launched by the bootloader, so if the bootloader goes, there goes the phone.
Would you mind saying how you were trying to replace the bootloader? (What the exact steps you attempted?) Did you take any special precautions about charging the battery beforehand, or performing any checksum verifications of any files you used? What instructions were you following?
When you pull the battery out, make sure that you also remove the charger cable so that no power is trickling into the phone that way. With the battery out, press all the buttons (one at a time or together, doesn't matter). Then reinsert the battery, and put the phone on the AC charger.
Then try seeing if anything will happen with any of the following key sequences (you might want to do the battery/charger disconnect between each attempt to be thorough):
Vol-Down+End (HBOOT)
Send+End (FASTBOOT)
End (Normal Boot)
If you get no response from any of those, the only other possibility (other than the phone being dead) is a problem with the battery. If you have a friend with an Eris you could try swapping batteries.
Given that the problem cropped up immediately after you were attempting to fool with the bootloader though suggests that you probably did brick your Eris.
sorry.
Click to expand...
Click to collapse
I was following instructions on a post in a thread here. I honestly can't remember which one. All I can remember is that the name of the file was erisengspl.zip I can't seem to find it by searching either.
Battery was at least 70% charged. I flashed the zip through amon_ra recovery.
I've tried booting into hboot, fastboot, and recovery already. I don't even think it's making it that far.
I've been removing the cable each time I removed the battery. There is a store that specializes in cell phone batteries nearby though. I think I'll see if they will let me test out a battery before I buy one.
Well, at least I've still got my previous phone lying around, and I'm due for an upgrade in a couple of months.
blindmanpb,
I forgot to ask: what was the version number of the pre-existing bootloader on the phone?
Was it a really old bootloader?
For testing purposes, I had rolled back my phone using the HTC MR1 and Leak-V1 PB00IMG.ZIP ROMs (1.47.0000 S-ON and 1.49.0000 S-ON, respectively), and then rooted each of them to install a custom recovery, and then attempted the "erisengspl.zip" flash on each.
It worked successfully when the 1.49.0000 S-ON bootloader was present; when the 1.47.0000 S-ON was present, the on-screen behavior of that flashing process seemed identical, but it failed silently - on rebooting the phone, 1.47.0000 S-ON was still there.
I would hate to see anybody else end up with a brick, so if you are aware of any other details that might be pertinent, please consider sharing them.
Sorry about your phone.
I believe I had 1.46.0000 S-ON.
blindmanpb said:
I believe I had 1.46.0000 S-ON.
Click to expand...
Click to collapse
Thank you very much - that is new information. Hopefully it will prevent others from having the same experience. (In general, people don't like to talk about bad experiences).
If you are very confident that that was the version number, you might consider putting a reply to this post to let people know what happened to you. Between your experience and mine, it is very evident that the "erisengspl.zip" flashable zip method should ONLY be used by people that have the 1.49.0000 S-ON bootloader.
bftb0
[ Edit ]
I went through and added the following warning to every post of mine I could find which mentions "erisengspl.zip":
[ Edit 2011-01-18 ]
[SIZE=+2] WARNING: "erisengspl.zip" EXTREME HAZARD[/SIZE]
[SIZE=+1]
XDA user blindmanpb reported bricking of his phone when "erisengspl.zip" was flashed on a phone with a 1.46.0000 S-ON bootloader present.[/SIZE]
Previously, my own personal testing showed that it does not work with the 1.47.0000 S-ON bootloader (but did not cause a bricking)
[SIZE=+2]DO NOT USE "erisengspl.zip" ON ANYTHING OTHER THAN THE 1.49.0000 S-ON BOOTLOADER[/SIZE]
bftb0 said:
Thank you very much - that is new information. Hopefully it will prevent others from having the same experience. (In general, people don't like to talk about bad experiences).
If you are very confident that that was the version number, you might consider putting a reply to this post to let people know what happened to you. Between your experience and mine, it is very evident that the "erisengspl.zip" flashable zip method should ONLY be used by people that have the 1.49.0000 S-ON bootloader.
bftb0
[ Edit ]
I went through and added the following warning to every post of mine I could find which mentions "erisengspl.zip":
[ Edit 2011-01-18 ]
[SIZE=+2] WARNING: "erisengspl.zip" EXTREME HAZARD[/SIZE]
[SIZE=+1]
XDA user blindmanpb reported bricking of his phone when "erisengspl.zip" was flashed on a phone with a 1.46.0000 S-ON bootloader present.[/SIZE]
Previously, my own personal testing showed that it does not work with the 1.47.0000 S-ON bootloader (but did not cause a bricking)
[SIZE=+2]DO NOT USE "erisengspl.zip" ON ANYTHING OTHER THAN THE 1.49.0000 S-ON BOOTLOADER[/SIZE]
Click to expand...
Click to collapse
That was the exact post I found the file on, actually. I'll reply to it like you suggested. Might save someone else from doing what I did.
Thanks for all your help!
I bought a used Sprint HTC EVO 3D in ebay, knowing it had a boot loop problem as described by the seller. Before buying, I researched to see if I can possibly fix the issue, and at that time I saw a few ways to do it. Unfortunately, now that I have the phone and tried those ways, my phone is still stuck in a boot loop.
This is what I've done so far:
1) Received the phone w/ HBOOT 1.5 (unlocked using HTC method).
2) I tried to flash TWRP 2.1.1, TWRP 1.0.3, ClockWork Mod 4.0.1.4, ClockWork Mod 5.8.0.1, and 4EXT RC3. The flashing seems to work as indicated by fastboot (it says OKAY after flashing).
3) I tried launching the recovery via fastboot command line and also tried launching recovery via power cycle while holding volume button down. Neither method allowed me to get to recovery. I would see the HTC logo, and then boot loop.
Other things I've tried:
1) Relock the phone.
2) Run the latest RUU (Sprint 2.17.651.5). I also tried the PG86IMG version. Flashing seems to succeed either way. But when I reboot, boot loop is still there. ROM doesn't boot.
Other things I've tried:
1) With the relocked phone, I did the HBOOT 1.4 downgrade and was successful downgrading.
2) I ran the RUU (Sprint 1.13.651.7) after the successful downgrade as described in the downgrade method so that I can try the Revolutionary S-OFF if my ROM boots.
3) The RUU succeeds, but the phone is still stuck in boot loop. ROM doesn't boot.
Again, the only thing that seems to work is fastboot commands. Adb commands don't work since the ROM doesn't even boot up.
I'm not sure if there's anything else I can do with the phone. I'm thinking now this may be a hardware issue. But before I send it in to HTC, I'd like to get opinions from the experts out there to see if there's anything else I can try.
Thanks!!!
none
Try to plug it into your computer, open a command prompt and type.
"adb reboot recovery"
Just like you see it, that should get you into recovery so you can flash a new rom onto it. And if you can swing it, by a new one next time lol
As stated above, adb commands won't work since you need a bootable ROM in the first place.. My EVO 3d reboots right after the first HTC logo pops up.. I've also tried launching recovery via fastboot command line and via power cycle and holding volume down button and selecting recovery. Both methods just reboots the phone and reboots over and over til I pull the battery out.
exact same problems, any help?
i have the exact same problems as Alpine Man.
tired everything, and i was hoping that if i downgraded to hboot 1.4, everything would be ok in terms of bootloops, but no =[
Can anyone shed light on this, software issue? hardware issue?
Anyone have a solution for this? or just send it to htc/
Have u tried installing new custom Rom?
I can't remember the creator's name but the file name is EVO 3d v2. I used the file to fix my bootloop. It's actual use is to relock ur bootloader back and it also install the ruu file. But it worked for me.
It might help u too. Maybe give a shot.
Sent from my AWESOME HTC EVO 3D. Click THANKS if u find my post is helpful.
I tried everything... And nothing fixed it. I finally sent it to HTC. They replaced the motherboard and all is well again.
i've read almost every guide availble regarding bootloop problems. my sister's evo 3d has no problems whatsoever. mine won't boot for anything!! have to go to work now but i will try it when i get home. if that doesn't work i'll probably have to send it in too.
alpineman - does the 1 year manufacturer warranty transfer over when you buy the phone used off ebay? i got my phone in great condition on ebay, with no mention of bootloop problems =[ . i'm not with sprint. i bought the phone hoping to flash it to metro. do i call htc instead of sprint? i'm not really sure how this warranty thing works.
any help is greatly appreciated thanks!
HTC did not ask for receipt, proof of ownership, or whether I had an active Sprint contract. They went by the serial number to determine warranty status. This is the 2nd HTC phone I had to do this with. Both times, no warranty problems whatsoever.
that's great! if all else fails, i'll give them a call on monday. thanks for the help!
good news! Come came back from HTC with new motherboard, boots up nicely now. I haven't done anything to it yet.
Bad new: the battery cover doesn't sit nice and flush anymore, its kinda crooked
It's sooo minor i almost don't wanna bother with HTC, but physically it was mint when I sent it in.
Need help
Hi can any one help, I am trying to gain S-Off on my Evo 3D, hboot 1.49.0018, I have Htc sync driver (Sync Un Installed)
adb devices command works fiine and gives me the serial number
but any other command with adb or fastboot it stucks on waiting for device.
Please Please Help me.
Regards,
So long story short I have this thunderbolt that is not working any longer. All of this happened over a year ago so I am vague on what I did to get the phone in its currently ruined state. It was rooted with the stock image and after trying to put a CM rom on it that didn't work I mistakenly booted into the phones recovery instead of clock work.
I now get a security warning and it is now s-on. If i do a recovery or factory reset it just boots back into the bootloader. Attached is an image of what is current on the screen when I power it on. I can't get ADB working on this pc but my spare rig has it working in OSX. ADB does not display the device. I have a way to get files onto the sd card but I am still kinda new to all of this stuff and just looking for some help. So where do I proceed from here?
I am going out of my mind.
So the phone just literally booted into my rooted rom. So now the question is, how do I get rid of the security warning and get s-off permanently?
At my end.
After a long day of trying to fix this thing and crawling all over the internet reading different posts I officially don't have a damn clue as to how to fix this. I am pretty sure the bootloader is corrupted and seeing as the phone is so old now it's really hard to find working links to downloads for this device.
Here is where I was at, ready to throw away the phone I ruined. I was rooted and S-ON and unlocked via HTC unlock bootloader web page. I was happily trying new things here when my phone went to all white background with green HTC letters. Wouldnt do anything. While trying to fix that I erased my backup and the software on the phone. I let the phone sit all day hoping the white backgound would go away but no. It wouldnt even power off. But I able to get into bootloader by doing this: Hold down power and volume up for 10 seconds, as soon as the screen goes blank slide finger down to volume down and hold. This got me into boot loader. I tried all the things outlined here to recover (using abd commands, fastboot *.img files nandroid backups, sideloading etc. My CID shows CWS_001 and next to the OS field is blank. Pulled the SIM and SD card to erase cache, no help. Wipe delvick, data, etc all failed with the E: unable to mount message. 2 Days gone by with not even a glimmer of recovering phone
So I went to HTC support download news (sorry cant post a link until 10 posts) and downloaded the RUU that contains the 4.4.3 update. This is an exe file that updates your phone. It failed on the first go. So I relocked the phone using wonders_never_cease M8 all in one kit, then double clicked on the RUU app again. It took off and ran. It is menu driven so I answered all the acknowledgements and got to the update screen. On that screen "current version field was blank and update to field reflected the new RUU version. The instructions tell you to put your phone into recovery mode and select fastboot. My Windows PC already had the HTC drivers loaded. I was shocked when the app began loading modules without failing. I didnt have to do anything except put attach usb cable to phone from PC and put the phone in fastboot. 10 mins later, the phone rebooted and my hated ATT logo and tune showed. Am up and running on 4.4.3 and new firmware.
Everything works fine on the phone (no modules missing). So it appears the "upgrade" will wipe partition and reload all the software on the phone without doing much of anything else. Thought I post this up for any other semi-noob that got into trouble and just wants a working phone. I am not sure a phone that is S-OFF would work but it doesnt hurt to try. I do understand HTC stopped the OTA update due to battery draining issues but the download is still available for fastboot. Am just happy to have a working phone. Now will make a backup in TWRP immediately. Over and out....Michael
sethandian said:
Here is where I was at, ready to throw away the phone I ruined. I was rooted and S-ON and unlocked via HTC unlock bootloader web page. I was happily trying new things here when my phone went to all white background with green HTC letters. Wouldnt do anything. While trying to fix that I erased my backup and the software on the phone. I let the phone sit all day hoping the white backgound would go away but no. It wouldnt even power off. But I able to get into bootloader by doing this: Hold down power and volume up for 10 seconds, as soon as the screen goes blank slide finger down to volume down and hold. This got me into boot loader. I tried all the things outlined here to recover (using abd commands, fastboot *.img files nandroid backups, sideloading etc. My CID shows CWS_001 and next to the OS field is blank. Pulled the SIM and SD card to erase cache, no help. Wipe delvick, data, etc all failed with the E: unable to mount message. 2 Days gone by with not even a glimmer of recovering phone
So I went to HTC support download news (sorry cant post a link until 10 posts) and downloaded the RUU that contains the 4.4.3 update. This is an exe file that updates your phone. It failed on the first go. So I relocked the phone using wonders_never_cease M8 all in one kit, then double clicked on the RUU app again. It took off and ran. It is menu driven so I answered all the acknowledgements and got to the update screen. On that screen "current version field was blank and update to field reflected the new RUU version. The instructions tell you to put your phone into recovery mode and select fastboot. My Windows PC already had the HTC drivers loaded. I was shocked when the app began loading modules without failing. I didnt have to do anything except put attach usb cable to phone from PC and put the phone in fastboot. 10 mins later, the phone rebooted and my hated ATT logo and tune showed. Am up and running on 4.4.3 and new firmware.
Everything works fine on the phone (no modules missing). So it appears the "upgrade" will wipe partition and reload all the software on the phone without doing much of anything else. Thought I post this up for any other semi-noob that got into trouble and just wants a working phone. I am not sure a phone that is S-OFF would work but it doesnt hurt to try. I do understand HTC stopped the OTA update due to battery draining issues but the download is still available for fastboot. Am just happy to have a working phone. Now will make a backup in TWRP immediately. Over and out....Michael
Click to expand...
Click to collapse
congratulations that you restore your device. the link for the RUU its already posted in the General Forum http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
also a bootable no pc version of it http://forum.xda-developers.com/att...-2-23-502-3-bootable-ruu-pc-required-t2860486
as well as the OTA http://forum.xda-developers.com/att-htc-one-m8/general/htc-m8-4-4-3-official-ota-t2860139
t5620 said:
congratulations that you restore your device. the link for the RUU its already posted in the General Forum http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
also a bootable no pc version of it http://forum.xda-developers.com/att...-2-23-502-3-bootable-ruu-pc-required-t2860486
as well as the OTA http://forum.xda-developers.com/att-htc-one-m8/general/htc-m8-4-4-3-official-ota-t2860139
Click to expand...
Click to collapse
Thanks for posting up the links.
sethandian said:
Here is where I was at, ready to throw away the phone I ruined.
Click to expand...
Click to collapse
As long as the screen comes on for this phone, its virtually always recoverable. There was never any reason to think you had to throw away the phone. Next time you are stuck, just ask for help here; as we are happy to help. You did the right thing in trying to find existing solutions. But it sounds like you did your due diligence searching and reading; and would have been justified starting a new thread and asking for help.
sethandian said:
Everything works fine on the phone (no modules missing). So it appears the "upgrade" will wipe partition and reload all the software on the phone without doing much of anything else.
Click to expand...
Click to collapse
That is precisely what the RUU does. Its a complete image, and handy for recovery purposes.
sethandian said:
I do understand HTC stopped the OTA update due to battery draining issues but the download is still available for fastboot. l
Click to expand...
Click to collapse
While the OTA has had some reports of causing battery issues, the RUU has not had any reports of such issue, and seems to be free of it.
sethandian said:
I am not sure a phone that is S-OFF would work but it doesnt hurt to try.
Click to expand...
Click to collapse
S-off does not affect whether or not the RUU will work, I don't know why folks keep saying or asking this. RUU will work whether S-on or S-off. The only difference, is that with S-on, you need to either have a LOCKED bootloader, or RELOCKED (relock it manually if you unlocked it).
Also, in general, S-off does not limit anything. It means "all security off" and enables more access, not the opposite. If anything, S-off enables more things than S-on.
Thanks for the all the info. The experience was a valuable teaching moment. Now back to playing around with the M8.
Hello all! I know this is an old issue and the phone that I have is as old as life it's self but I hope that I can find some help here! I know there are sever threads covering this issue but I have not found any that covers the ENITRE issue that I am having.
Okay, now for my problem....
Of course my phone died (battery). I put it on the charger and powered it up. The phone stuck on Sprint screen for several days. This is the second time this has happened. The first time I was unable to use recovery but I was able to do a factory reset. THIS TIME I am unable to do anything. On factory reset, the phone goes to green icon and then it turns into the red exclamation. Same thing with recovery. I have tried the wipe/factory reset...I get an error there "E:can't open /cache/recovery/command" and I get that on all options in Sys recovery menu. I have read several threads on using fastboot but I have learned that there is more to it that plugging in the USB and recovering the phone.
To help answer some of the questions here are the details on the HBoot menu:
****Locked****
Shooter XC Ship S-On RL
HBoot - 1.58.0000
Radio - 1.09.00.0108
OpenADSP - v02.6.0226.00.0217
eMMC-boot
The phone has never been rooted and everything is stock.
I have seen that it can be recovered through Hboot menu but I'm not deep into this side of things so I will need detailed instructions if possible. I have an HTC Evo 3d and my PC is Mac OSX.
Same problem
I was about to post about my problem, but yours is very similar and like any good forum go-er I checked to see if there were any recent problems like mine.
I am running
**locked** shooter s-on hboot v 1.58 eMMC -boot from may 17, 2012.
I have never rooted the device or tampered with it in any way. I thought about it, but got a newer phone.
I recently got into computer programming and wanted to see what can be done with this old tech with still relevant hardware.
after starting the device it got into the OS , took me to my homescreen like normal then failed horribly after 10 seconds, once i slid the ring up.
it then got stuck at HTC screen, so i tried the bootloader, which works, so i went for a factory recovery. get the red triangle, so i look into rooting.
turns out that if i hadnt checked usb debugging and unlocked already, i cant get in to do anything. is this a soft-brick hard-brick case?
i feel there is hope, but the lack of response to OP after this time leaves me disappointed. I've spent many hours trying to find a solution to this problem, but it is way beyond me.
i tried finding signed copies of PG86IMG.zip for hboot 1.58 to no avail, only option is RUU which won't find the phone on windows 10. drivers are out of date, perhaps.
Installing linux now to hopefully get access to that file system.
Would really appreciate the help, devs. this is a great device would be a shame that NOT tampering with it would leave me and OP with a brick.
thanks for reading and thanks in advance for consideration and advice.
dunno, maybe try this
http://forum.xda-developers.com/showthread.php?t=1653777
virgin evo 3d has no downloadable current ruu to flash, and you guys are s on which won't let you flash older ruu to reset your system. which makes it difficult to fix.