I was attempting to install the stock radio for my htc evo 3D gsm on Rogers network. I had the right exe file and ran it on my computer and started the update. Everything worked until the last ~5% when it said image writing error and now my phone will only show the htc symbol with exclamation marks in all four corners. Please help me out here! I just got this phone
EDIT: this problem has been solved thanks to il dice and his possy. I shall now attempt to recall the steps to fix ruu error 110 on the evo 3D gsm
When your phone has the above problems (ruu failiure resulting in a black HTC screen with exclamations in all four corners) you need to:
1-make sure it is charged
2-plug it into a computer on which you have the android SDK or at least fastboot.
3-Hopefully you have a nandroid back up that you can pull off of your sd, put the recovery.IMG and boot.IMG from your back up in the same folder as fastboot.exe.
4-open up a command prompt and point it to the folder with all the goodies in it (cd *path to folder*)
5-type these commands into the computer:
fastboot flash recovery recovery.img
Fastboot boot recovery.img
6-If all goes as planned your phone will boot into recovery (clockworkmod, or whatever you had with your backup), from there you need to wipe. (LOLilduce)
7-select wipe data/factory reset, wipe cache and wipe dalvik
8-now you can flash a Rom from your sd card, so go ahead and do so
9-don't reboot from recovery, in my situation it just brings you back to the ruu error, erasing all your previous work. Instead type in the computer fastboot oem boot.
I do believe those are all the steps you need to take to get your phone back up and running.
Update: re running the ruu is how I fixed my phone, yet I had to use another computer. If this happens to you, download the ruu again and try it on a different machine.
CAUTION: Every time your phone turns off, you probably will have to do these steps again. I am working on a fix for this hopefully with the help of il duce again.
Update: re running the ruu is how I fixed my phone, yet I had to use another computer. If this happens to you, download the ruu again and try it on a different machine. My phone is now working completely fine.
Please leave comments if this helped you out. I know there isn't much info on this error because I couldn't find any.
Cheers!
jverm said:
I was attempting to install the stock radio for my htc evo 3D gsm on Rogers network. I had the right exe file and ran it on my computer and started the update. Everything worked until the last ~5% when it said image writing error and now my phone will only show the htc symbol with exclamation marks in all four corners. Please help me out here! I just got this phone
Click to expand...
Click to collapse
Have you tried to Boot into Recovery? If you Can't get into Recovery, see if you can get to Fastboot...
Nothing. Power and volume button only bring up the error screen.
Let the phone charge a few hours and try to run the .exe again.
Locked & Loaded
""shooter on Deck""
Most likely your briked if you where messing with the radios something ill never do
Sent from my PG86100 using xda premium
Chances are you are bricked, if you can't get into recovery or try the exe again. Errors when flashing radio's is very bad.
@OP - please check info from our discussion in my help thread. Was busy last night, but still want to help. I was curious about if you tried using wireless adb since you can't communicate via usb cord? Also, I was digging thru some links from a couple years ago becuz your issue sounded familiar. Good news is I found a thread WITH A POSSIBLE FIX just linked in help thread
@jverm when you get time, please post the various steps we took to unbrick you, with links to helpful threads and concise information. Put SOLVED in the thread title, and add some thread tags to the issues. This way hopefully someone in a similar situation can hopefully find this thread, and then also successfully revive their phone as you did. This is all I ask of you for my help and again really it was fun for me, so thanks.
The screen with four small triangles in the corners means you had an incomplete flash. Luckily you're not bricked but it will be stuck in RUU mode until you Redland it with a good RUU
edit: nm, just saw il Duce's post
Related
Evening all,
I have been advised to post here on XDA from Android Forums. This is a copy of my initial post on there to explain the background to my issue.....
Hi there,
I have HTC Desire from O2 and after 12 hours of online searching and tweaking I'm hoping someone may be able to help.
I received the OTA upgrade yesterday which I accepted because I thought O2 might have it sorted by now. Obviously not. Anyway update ran with no interruption but then rebooted to a frozen O2 screen.
I searched the net and eventually found the guide to update the phone using the RUU Rom. I followed this to the letter and the installer for the RUU wouldnt't open. I then realised that Google Chrome hadn't fully downloaded the file (113mb not 171mb). I then used a download manager to ensure I had the full file. It then ran and seemed to be working... until 80% in when I get ERROR 110 File Open.... please use a complete RUU. I downloaded it several more times in various ways but still same result. By this point my phone was pretty much bricked.
I had black screen with silver HTC logo in the middle and 4 exclamation marks in the corners.... this remained whilst the phone was plugged in and the buttons in any combination did nothing. When i removed the USB cable i got a white boot screen with RUU highlighted in orange and again.... buttons do nothing. Every time I ran the RUU file it brought up a green bar as if it was making progress but then errors at the same point every time. (Error 110 use complete RUU... file seems to be complete now at 171mb)
I tried it on two computers, one win7 and the other vista. The vista machine doesn't even see the phone, it gives a USB error before the update begins.
At 2am I used the SDK download and typed the following at command prompt.... "fastboot oem boot".... phone instantly boots into O2 Froyo and works fine. If i then unplug the phone, turn it off and on again.... i get the black HTC screen again, back to square one.
At the moment I have fastbooted it so its working and have used the goldcard tool to obtain the CID and created the .img file.
I don't know what to do from here!!.... the update obviously hasn't FULLY worked but it must have completed enough for the thing to fastboot and seems to have full functionality (calls, wireless, network etc)
I don't really want to void the warranty but O2's only option is to send it off for 14 days to have an engineer tell me its buggered and send a replacement.
Any advice is appreciated.
Rich.
A couple of helpful guys on there have tried to advise me but without success. They suggested rooting etc but here is my problem.....
At the moment the phone seems to be working fine with Froyo... but the only way I can get my phone to start up is by plugging in and running "fastboot oem boot" from command prompt. If my phone is powered off and I turn it on in the normal way, I get the black screen with silver 'HTC' and triangles in 4 corners and all buttons do nothing!
I have tried fastboot command whilst holding down the volume keys etc and it just boots normally. Obviously something isn't right and I can't let my battery run down otherwise its useless until I can fastboot it again.
So this is preventing me from accessing any of the menu's required in the flash/root tutorials.
Can anyone help or do I just need to ensure I don't run the battery down?!?
Thanks in advance
Rich
if you have a goldcard already, have you tried flashing a diffrent ruu from fastboot? maybe just a generic htc one rather than the o2 one?
Hi,
Thanks for your reply.
Could you advise me which RUU would be the best to use?
I have looked through the list on shipped-roms website but apart from the obvious O2 ones, I don't understand which ones are which!
Thanks
Rich
Hi Rich,
I have exactly the same problem. Have you got any feedback about whether you have solved this issue?
Thanks!
Kelk
Edit:
I think I may have got it sorted. Downgrade to 2.1 as per:
hxxp://forum.xda-developers.com/showthread.php?t=768256
(replace xx to tt in link above)
Hi there,
I haven't solved my issue yet. At the moment I am using my phone on 2.2 but trying not let the battery run flat (I have to use fastboot from command prompt to get my phone to boot up)
Did the tutorial above work for you?
My issue is getting a working goldcard. I'm not sure whether mine has worked succesfully because when i've tried running the RUU of either the unbranded froyo update or even the O2 original, i get and error message and it doesn't work.
I followed the goldcard creation tutorial but I still get the CID error when trying to run the various RUU files.
I hope I can sort this soon because i've been close to throwing my phone out of the window several times!!
Cheers
Rich
Hi Rich,
Yes, the above tutorial worked for me. I think this is because it downgrades to a former version of HBOOT.
rich0684 said:
Hi there,
I haven't solved my issue yet. At the moment I am using my phone on 2.2 but trying not let the battery run flat (I have to use fastboot from command prompt to get my phone to boot up)
Did the tutorial above work for you?
My issue is getting a working goldcard. I'm not sure whether mine has worked succesfully because when i've tried running the RUU of either the unbranded froyo update or even the O2 original, i get and error message and it doesn't work.
I followed the goldcard creation tutorial but I still get the CID error when trying to run the various RUU files.
I hope I can sort this soon because i've been close to throwing my phone out of the window several times!!
Cheers
Rich
Click to expand...
Click to collapse
Use Goldcard + your shipped o2 ROM (ROM that came originally with ur phone 1st time). you can get the rom from HTC official website. enter your Serial Number t download (i recommend using Mozilla built in download manager, coz Google Chrome always give me Corrupted Download when downloading Large files)
Think you've broken your phone? Read this to return it back to normal.
I've seen a lot of questions about people accidentally screwing up their phones or doing something similar around here and on the OG Evo forums. This thread is for those of you who want to return it back to normal. This is also useful to redirect people to if they have those questions.
If your phone won't start up at all and the LED won't light up at all when it is plugged in:
-Take out battery and put it back in
-If that doesn't work, swap out a battery with one you know works
-If that doesn't work, take out the SD card and try again
*If taking out the SD card fixed it, your SD card is bad and you need a new one.
-If that doesn't work or you know it isn't the battery or SD card, your phone is probably bricked.
If your phone doesn't start up but a red LED blinks when you plug it in:
*Download Android ADB Files if you don't already have them
-Plug your phone in to your computer. With a terminal/cmd, navigate to /android-sdk-(OS You're Using)/platform-tools and type "adb reboot"
-If that doesn't start up your phone, try the steps before except this charge your battery or replace with a working battery
*If your phone doesn't get get past the HTC splash screen, use "adb reboot bootloader" instead of "adb reboot" so you reboot into bootloader.
If your phone starts up but gets stuck at the HTC splash:
-Go into bootloader with vol-down+power and go to recovery. Wipe everything and then flash a ROM or backup from there that you know has worked before
-If that doesn't work, flash this from bootloader: http://forum.xda-developers.com/showthread.php?t=1193540
-If you can't access your SD card, replace it with a working one
If your phone won't go into recovery:
-Flash the TWRP PG86IMG through bootloader again:
http://forum.xda-developers.com/showthread.php?t=1192077
-If that doesn't work, try the S-OFF tool again and reflash the recovery
-If that doesn't work, try putting back S-on (download fastboot and type "fastboot oem writesecureflag 3" or "fastboot oem lock" into cmd/terminal) and then flashing PG86IMG. Then try S-offing again and flashing the recovery.
If your phone won't get past the boot animation:
-Go into bootloader with vol-down+power and go to recovery. Wipe everything and then flash a ROM or backup from there that you know has worked before
If your phone gets bootloops:
-Pull the phones battery and put it back in, then:
Go into bootloader with vol-down+power and go to recovery. Wipe everything and then flash a ROM or backup from there that you know has worked before
-If that doesn't work, flash this from bootloader: http://forum.xda-developers.com/showthread.php?t=1193540
If anything else strange is happening to your phone:
-Reboot phone
-If that doesn't work, wipe data and go back to a working ROM/Recovery
-If that doesn't work, flash the PG86IMG RUU:
http://forum.xda-developers.com/showthread.php?t=1193540
If you want more accurate instructions on how to fix a problem, ask in this thread.
It's nice that you're trying to help people out, but I'm sure that everyone does all this anyway when they have seemingly unfixable problems lol
freeza said:
It's nice that you're trying to help people out, but I'm sure that everyone does all this anyway when they have seemingly unfixable problems lol
Click to expand...
Click to collapse
Ure right, but this could help some noobs. Should be sticky imo.
- Coz i just saw it in 3D with the Shooter -
dashrink said:
Ure right, but this could help some noobs. Should be sticky imo.
- Coz i just saw it in 3D with the Shooter -
Click to expand...
Click to collapse
Yeah it should definitely be a sticky. Surprising even with all this information all the n00bs still ask the same damn questions about stuff that has been posted here time and time again
I have HBOOT 1.5 and suffering from stucking at splash screen. In fact, before stuck at splash screen, I did not tried to s-off, rooted, and flash any roms. Just a fully reboot result in stuck at splash screen. I have tried every method you mentioned above, just stuck at the splash screen:-(
I googled all the world, and someone said maybe eMMC chip damaged? It is happened on EVO 4G, but maybe also on EVO 3D? I hope it is not true, I always hope my situation is just a soft brick, anyone can tell me if it is possible brick the phone( stuck at the splash screen) due to eMMC chip damaged? Thanks in advance!
freeza said:
It's nice that you're trying to help people out, but I'm sure that everyone does all this anyway when they have seemingly unfixable problems lol
Click to expand...
Click to collapse
Heh, you'd be surprised with all the threads about people asking how to fix their phone after 'x' happened.
subaochen said:
I have HBOOT 1.5 and suffering from stucking at splash screen. In fact, before stuck at splash screen, I did not tried to s-off, rooted, and flash any roms. Just a fully reboot result in stuck at splash screen. I have tried every method you mentioned above, just stuck at the splash screen:-(
I googled all the world, and someone said maybe eMMC chip damaged? It is happened on EVO 4G, but maybe also on EVO 3D? I hope it is not true, I always hope my situation is just a soft brick, anyone can tell me if it is possible brick the phone( stuck at the splash screen) due to eMMC chip damaged? Thanks in advance!
Click to expand...
Click to collapse
I guess something hardware related could only be the case then. If you've tried everything you could, that is probably the case. Go to sprint and tell them something happened during an OTA. (IK it is hardware related, but that will still get you a better chance of them replacing it)
If you want to have S-On for when you take it back to sprint, open up a terminal and type "fastboot oem writesecureflag 3" and it will remove -revolutionary- and change s-off to s-on.
Although I have figured this out through other posts, etc.....
+1 for sticky
would of been great to be reassured there is a light at the end of tunnel if
I messed up before I jumped into rooting/flashing. And a good place to calm the nerves when you bootloop for the first time....
Sent from my clean sharp shooter
HBoot 1.50 Softbrick
My phone is bricked!
But yay for fixability, (and your optimism: I vote for stickying your post!)
It WON'T:
Go into Recovery (and it's HBoot 1.50)
Let me touch the screen, or buttons.
Bring up the start-up unlock screen.
It CAN:
Recognize when charging / when the battery is in;
Recognize the power button to turn the screen on/off.
Boot up to the main page where icons come up (But only the status bar is seen)
And Shake to take pictures! I accidentally took my first, being the screen I can get to.
Probable Causes:
I think I froze something I shouldn't have (Settings widget?), with Ti Backup.
Or that senseless Rom I put in... Now it doesn't sense me! All the thing wants to do is take pictures of its selfish self.
Solutions?
Thanks!
You're responses are much appreciated!
RUU
/10char
I vote for sticky, too.
I am no noob. I didn't do anything to my phone prior to bricking. I had my phone fully charged in the evening and woke up to a brick. The phone worked great from the time I bought it ... great the whole time it was rooted ... great with each iteration of SteelH's ROM. Then I woke up to a brick.
Even though I knew all of the steps to take (and did each one to no avail) I still felt helpless and started a thread in Q&A praying there was something to make it come back to life.
Now I'm just sad.
RemWhale said:
My phone is bricked!
But yay for fixability, (and your optimism: I vote for stickying your post!)
It WON'T:
Go into Recovery (and it's HBoot 1.50)
Let me touch the screen, or buttons.
Bring up the start-up unlock screen.
It CAN:
Recognize when charging / when the battery is in;
Recognize the power button to turn the screen on/off.
Boot up to the main page where icons come up (But only the status bar is seen)
And Shake to take pictures! I accidentally took my first, being the screen I can get to.
Probable Causes:
I think I froze something I shouldn't have (Settings widget?), with Ti Backup.
Or that senseless Rom I put in... Now it doesn't sense me! All the thing wants to do is take pictures of its selfish self.
Solutions?
Thanks!
You're responses are much appreciated!
Click to expand...
Click to collapse
Can you get into the boot loader at all? I've always heard that if it powers on it can be fixed. Also see if ADB works and look up a list of commands. A full data wipe should get you back up and running.
An RUU sounds like something I should put on my SD card; What is /10char?
Where do I find them?
@ Drewmungus:
I can get into boatloader, and fastboot, but the recovery is shot; it just restarts the phone. When I reboot the phone, should I try to adb/push something?
Many Thanks for you responses!
RemWhale,
Here is the fix (which was also above):
Download TWRP 1.0 and read the instructions on installing it on your phone. Once it is installed, recovery should work. If it doesn't,
Boot into bootloader with vol+power down. Then hit fastboot and connect your phone to your computer. Download the PG86IMG in the OP, and flash it how you would on hboot 1.5.
Problem from bad freezing or Recent ROM
yousefak said:
RemWhale,
Here is the fix (which was also above):
Download TWRP 1.0 and read the instructions on installing it on your phone. Once it is installed, recovery should work. If it doesn't,
Boot into bootloader with vol+power down. Then hit fastboot and connect your phone to your computer. Download the PG86IMG in the OP, and flash it how you would on hboot 1.5.
Click to expand...
Click to collapse
After all this, my battery shorted or something, but I did get a new one from Sprint today. I tried it out these solutions! My report:
Recovery through SD Card:
For newest versions: teamw.in/project/twrp/67
Successfully put PG86IMG.zip and recovery-twrp-shooter-1.1.1.img onto my SD card, and went to Bootloader; it said "Updated succesfully.";
when I restarted my phone, I still could ONLY see the background pic and status bar, but nothing else. It was the same.
RUU_Shooter_S_Sprint_WWE_2.08.651.2_Radio_0.97.10.0808_NV_SPCS_1.31_003_release_208230_signed
RUU failed - Error 155 - Unknown Image Error:
One of these error messages will appear when you'd use the incorrect RUU to update and the image file size is larger than the Flash ROM size. In this case, It means I need to download the correct RUU version and try again. But where?
Factory Reset
Nothing. I still get MY emails, which you can see in the attached picture of the screen I get to below.
Re-Unlock Bootloader...
Take out SD Card; Cmd: "fastboot oem lock" - Cmd: "fastboot flash unlocktoken Unlock_code.bin"
(No icons on home page at all? How strange...) Hey! I'm back in!
Made a Phone call! Installed some widgets! Restored contacts!!!!
The day is saved; All is well.
Not able to tell if I have any ROMs on it at the moment...
It appears I had the wrong RUU and/or PMG86.zip; I have HBoot 1.50; is there one for my newer version? Should I start a new post for my resolved situation? BTW, thanks for trying! Please add "Re-Unlock Bootloader" as a resolution.
Please, Thank me if his helps you too! Others will find be more hopeful.
meatgel said:
I vote for sticky, too.
I am no noob. I didn't do anything to my phone prior to bricking. I had my phone fully charged in the evening and woke up to a brick. The phone worked great from the time I bought it ... great the whole time it was rooted ... great with each iteration of SteelH's ROM. Then I woke up to a brick.
Even though I knew all of the steps to take (and did each one to no avail) I still felt helpless and started a thread in Q&A praying there was something to make it come back to life.
Now I'm just sad.
Click to expand...
Click to collapse
Try Re unlocking the Bootloader -That was the only thing that could solve my problem! It erased the problem, whatever it was - Let me know if it works!
RemWhale said:
Try Re unlocking the Bootloader -That was the only thing that could solve my problem! It erased the problem, whatever it was - Let me know if it works!
Click to expand...
Click to collapse
It was a brick. I couldn't power it on and the charge light wouldn't come on. I changed batteries, changed power cords ... the guys at the Sprint store did the same stuff and then took it apart to see if it was water damage (LOL). They said they'd never seen one that wouldn't even show the charge light for a second.
I got a replacement in the mail. Hboot 1.50.
RemWhale said:
After all this, my battery shorted or something, but I did get a new one from Sprint today. I tried it out these solutions! My report:
Recovery through SD Card:
For newest versions: teamw.in/project/twrp/67
Successfully put PG86IMG.zip and recovery-twrp-shooter-1.1.1.img onto my SD card, and went to Bootloader; it said "Updated succesfully.";
when I restarted my phone, I still could ONLY see the background pic and status bar, but nothing else. It was the same.
RUU_Shooter_S_Sprint_WWE_2.08.651.2_Radio_0.97.10.0808_NV_SPCS_1.31_003_release_208230_signed
RUU failed - Error 155 - Unknown Image Error:
One of these error messages will appear when you'd use the incorrect RUU to update and the image file size is larger than the Flash ROM size. In this case, It means I need to download the correct RUU version and try again. But where?
Factory Reset
Nothing. I still get MY emails, which you can see in the attached picture of the screen I get to below.
Re-Unlock Bootloader...
Take out SD Card; Cmd: "fastboot oem lock" - Cmd: "fastboot flash unlocktoken Unlock_code.bin"
(No icons on home page at all? How strange...) Hey! I'm back in!
Made a Phone call! Installed some widgets! Restored contacts!!!!
The day is saved; All is well.
Not able to tell if I have any ROMs on it at the moment...
It appears I had the wrong RUU and/or PMG86.zip; I have HBoot 1.50; is there one for my newer version? Should I start a new post for my resolved situation? BTW, thanks for trying! Please add "Re-Unlock Bootloader" as a resolution.
Please, Thank me if his helps you too! Others will find be more hopeful.
Click to expand...
Click to collapse
Well, did you try going into recovery at all? I should have included that you should have reflashed the ROM and the kernel to fix it. That probably would have gotten you fixed after the first step.
usb does not work
i flashed the miui rom and now my phone has no usb so i cant do any commands i cant use the rom i had to restore a back up of an old rom and still no usb no usb in fastboot nothing and im not sure what to do its not the cables
babybear293 said:
i flashed the miui rom and now my phone has no usb so i cant do any commands i cant use the rom i had to restore a back up of an old rom and still no usb no usb in fastboot nothing and im not sure what to do its not the cables
Click to expand...
Click to collapse
Did you try another cable? Are you sure its not the cable?
Plug in the USB while the phone is off and tell me if you can do 'adb restart'. If your phone starts, that means the USB works it should be fixable by flashing the PG86IMG.
If it doesn't work when the phone is off, there is something wrong with your USB port or the cable you are using. There could also be something wrong with your comp/usb power source.
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,
I have been through a day of torment with my VM Evo 3D since deciding to throw a new ROM on yesterday. Several months ago, I rooted the phone and installed a new kernel, but was still running the stock ROM.
On previous phones, I had never had to deal (that I can recall) with the s-on/s-off issue, so I just chose to be cavalier, grab a ROM and install it without reading some very necessary details which I have definitely studied since! Every ROM that I tried put me into boot loop, and after a few I realized there was no getting around s-off. Since I am on 64-bit Windows, I downloaded Ubuntu 12.10 and ran live disk to try the unlimited.io wire trick, however, the software failed and I was unable to even get to the point of doing the wire trick itself.
This morning, dejectedly I decided to just un-root my phone and start from scratch. I relocked it and installed a stock ROM with RUU. I decided that I am going to work through the steps again and be very careful at each step. I went to reboot into recovery and was unable to do so from power/volume-down. I went ahead and booted into regular mode and ran >adb reboot recovery. At this point it rebooted, but came up to a screen with a picture of a phone and a red triangle and exclamation mark. Some googling seems to indicate that my recovery image is jacked up, so I went to run >fastboot flash recovery recovery.img, but fastboot is not enabled. When I do >adb devices, I see my phone. When I do >fastboot devices, it returns nothing. The only way that I know how to turn on fastboot is to go into recovery, but since I can't get into recovery, I am unable to do that.
Does anyone have any advice on a good next step? Is it possible to turn on fastboot via adb? I am hoping that someone has a response other than 'you are screwed'. Thanks in advance if so.
[EDIT] Please disregard. For some reason, after powering it off for a while and trying again, I am now able to get into recovery. I have no idea why it wasn't working then and is now, as I haven't change anyway, but that is pretty much how my last 24 hours has gone anyway. :/
olllllo said:
I have been through a day of torment with my VM Evo 3D since deciding to throw a new ROM on yesterday. Several months ago, I rooted the phone and installed a new kernel, but was still running the stock ROM.
On previous phones, I had never had to deal (that I can recall) with the s-on/s-off issue, so I just chose to be cavalier, grab a ROM and install it without reading some very necessary details which I have definitely studied since! Every ROM that I tried put me into boot loop, and after a few I realized there was no getting around s-off. Since I am on 64-bit Windows, I downloaded Ubuntu 12.10 and ran live disk to try the unlimited.io wire trick, however, the software failed and I was unable to even get to the point of doing the wire trick itself.
This morning, dejectedly I decided to just un-root my phone and start from scratch. I relocked it and installed a stock ROM with RUU. I decided that I am going to work through the steps again and be very careful at each step. I went to reboot into recovery and was unable to do so from power/volume-down. I went ahead and booted into regular mode and ran >adb reboot recovery. At this point it rebooted, but came up to a screen with a picture of a phone and a red triangle and exclamation mark. Some googling seems to indicate that my recovery image is jacked up, so I went to run >fastboot flash recovery recovery.img, but fastboot is not enabled. When I do >adb devices, I see my phone. When I do >fastboot devices, it returns nothing. The only way that I know how to turn on fastboot is to go into recovery, but since I can't get into recovery, I am unable to do that.
Does anyone have any advice on a good next step? Is it possible to turn on fastboot via adb? I am hoping that someone has a response other than 'you are screwed'. Thanks in advance if so.
[EDIT] Please disregard. For some reason, after powering it off for a while and trying again, I am now able to get into recovery. I have no idea why it wasn't working then and is now, as I haven't change anyway, but that is pretty much how my last 24 hours has gone anyway. :/
Click to expand...
Click to collapse
Glad it decided to work. I would try the linux bootable cd with the pull the battery trick to get s off. It worked for me although it took quite a few tries to get the battery out at the perfect time. I was not cool with the wire trick or any kind of htc dev unlock. The cd also gives you options for the hboot downgrade as well. Good luck!!!
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.