Hi there,
I'm been having recurring Screen of Death issues with my HTC Desire.
This is where the screen is off, but the phone still works, i.e. touch, vibration, sounds, incoming calls etc, but the screen remains off.
The phone is rooted and S-Off and using the latest stable CM7.
I have tried reinstalling the ROM after a full wipe (data, cache and Dalvik)
Tried latest CM7 nightly with the same problem.
I even tried the MIUI and Oxygen ROMs and the problem is still there.
Also, I tried installing the Load Monitor app (to prevent the device from sleeping) but that did not help. Others reported that this has helped them.
I now have a device which appears to be unusable so any help is much appreciated.
To be clear: the phone works fine but once the screen goes off it will not come back on.
Many thanks
No Expert said:
Hi there,
I'm been having recurring Screen of Death issues with my HTC Desire.
This is where the screen is off, but the phone still works, i.e. touch, vibration, sounds, incoming calls etc, but the screen remains off.
The phone is rooted and S-Off and using the latest stable CM7.
I have tried reinstalling the ROM after a full wipe (data, cache and Dalvik)
Tried latest CM7 nightly with the same problem.
I even tried the MIUI and Oxygen ROMs and the problem is still there.
Also, I tried installing the Load Monitor app (to prevent the device from sleeping) but that did not help. Others reported that this has helped them.
I now have a device which appears to be unusable so any help is much appreciated.
To be clear: the phone works fine but once the screen goes off it will not come back on.
Many thanks
Click to expand...
Click to collapse
You obviously haven't tried everything. Check my guide.
Hi and thanks for taking time to reply.
I've just tried Option 9 in your thread, i.e.:
Fixing Deep Sleep
[STEP1]- Enter dialpad
[STEP2]- type *#*#4636#*#*
[STEP3]- Go to "phone information
[STEP4]- Change "preferred network type" to GSM only, or CDMA only
But unfortunately the problem persists (I didn't try any of the other options because they are not relevant at least to this issue).
Is there anything else I can try, perhaps something more aggressive in terms of "wiping"?
Thanks again.
No Expert said:
Hi and thanks for taking time to reply.
I've just tried Option 9 in your thread, i.e.:
Fixing Deep Sleep
[STEP1]- Enter dialpad
[STEP2]- type *#*#4636#*#*
[STEP3]- Go to "phone information
[STEP4]- Change "preferred network type" to GSM only, or CDMA only
But unfortunately the problem persists (I didn't try any of the other options because they are not relevant at least to this issue).
Is there anything else I can try, perhaps something more aggressive in terms of "wiping"?
Thanks again.
Click to expand...
Click to collapse
Try different radio
Hi,
I tried to flash another radio through ClockworkMod but I get the error:
"Amend scripting (update-script) is no longer supported.
Amend scripting was deprecated by Google in Android 1.5.
It was necessary to remove it when upgrading to the ClockworkMod 3.0 Gingerbread
based recovery."
This is the same as described here:
http://forum.xda-developers.com/showpost.php?p=17311987&postcount=2163
So I then tried the fastboot method but once I issue the command adb reboot bootloader, the screen goes black and then there is no response.
I tried this twice and it's the same both times.
Any ideas appreciated as the phone is unusable at the moment.
Thanks
EDIT: I issued the command to flash the radio anyway (fastboot flash radio) even though the screen was completely dark and the radio did indeed flash sucesfully.
I checked in "about phone" and I can see the updated radio.
The radio is version 5.11.05.27 which was the last one sent with the last official HTC update.
So I rebooted the phone and...the same thing.
Once the phone sleeps I cannot turn the screen on, even though the phone itself is on.
PS: I even tried an early Ice Cream Sandwich alpha ROM and the problem persists....
Thanks.
No Expert said:
Hi,
I tried to flash another radio through ClockworkMod but I get the error:
"Amend scripting (update-script) is no longer supported.
Amend scripting was deprecated by Google in Android 1.5.
It was necessary to remove it when upgrading to the ClockworkMod 3.0 Gingerbread
based recovery."
This is the same as described here:
http://forum.xda-developers.com/showpost.php?p=17311987&postcount=2163
So I then tried the fastboot method but once I issue the command adb reboot bootloader, the screen goes black and then there is no response.
I tried this twice and it's the same both times.
Any ideas appreciated as the phone is unusable at the moment.
Thanks
EDIT: I issued the command to flash the radio anyway (fastboot flash radio) even though the screen was completely dark and the radio did indeed flash sucesfully.
I checked in "about phone" and I can see the updated radio.
The radio is version 5.11.05.27 which was the last one sent with the last official HTC update.
So I rebooted the phone and...the same thing.
Once the phone sleeps I cannot turn the screen on, even though the phone itself is on.
PS: I even tried an early Ice Cream Sandwich alpha ROM and the problem persists....
Thanks.
Click to expand...
Click to collapse
Try the latest one http://download.oxygen.im/radios/bravo.5.17.05.23.zip
Also if you can't boot fastboot with commands then just poweroff, then hold BACK and POWER
Hi Bortak,
that's the one (5.17.05.23) I already had before I downgraded.
Thanks
Bortak,
HTC have actually agreed to have a look at the handset as part of the warranty (I was unaware at the time I posted my question that the warranty is 24 months), so I will be sending it to them.
Do you know if I can use HTC's own RUU from their site on my rooted and S-off handset to return it to stock, or do I risk any damage?
(see question here: http://forum.xda-developers.com/showthread.php?p=20288444#post20288444)
[Moderators, I will close / delete one or the other thread once answered. Thanks]
No Expert said:
Bortak,
(I was unaware at the time I posted my question that the warranty is 24 months), so I will be sending it to them.
Click to expand...
Click to collapse
Really? Which country?
Do you know if I can use HTC's own RUU from their site on my rooted and S-off handset to return it to stock, or do I risk any damage?
Click to expand...
Click to collapse
If you have a goldcard/you have the RUU meant for your region, there is no risk if you follow instructions
Hi,
I'm in the UK (I believe under EU rules all electronic manufacturers need to provide 24 months though Apple I think only provide 12 I thikn).
In any case, they said OK.
If you have a goldcard/you have the RUU meant for your region, there is no risk if you follow instructions
Click to expand...
Click to collapse
I do not have a goldcard but it's definitely the RUU for my region (i.e. GB / UK).
Just one more question: can I just run the RUU directly or do I need to downgrade HBOOT etc first?
Thanks.
No Expert said:
Hi,
I'm in the UK (I believe under EU rules all electronic manufacturers need to provide 24 months though Apple I think only provide 12 I thikn).
In any case, they said OK.
I do not have a goldcard but it's definitely the RUU for my region (i.e. GB / UK).
Just one more question: can I just run the RUU directly or do I need to downgrade HBOOT etc first?
Thanks.
Click to expand...
Click to collapse
1. Is the phone on contract?
- if yes, you need to correct RUU for your network provider (NOT region - unless you bought the phone yourself), otherwise your warranty will be void
2. Since you are S-OFF, you need to flash the stock hboot first, then the downgrader, then the RUU
3. If you don't know which RUU is for you, use the 2.3.3 one
Hi and thanks,
1. Is the phone on contract?
Click to expand...
Click to collapse
No, it's an unbranded one.
2. Since you are S-OFF, you need to flash the stock hboot first, then the downgrader, then the RUU
Click to expand...
Click to collapse
Can I confirm these steps are right?
(i) Flash Stock Hboot
Verify the MD5SUM of the file
Flash HBOOT with phone in fastboot mode (Back+POWER) -> 'fastboot flash hboot bravo_alphaspl.img'
'fastboot reboot-bootloader'
'fastboot erase cache'
Do I need to reboot after this?
(ii) Downgrader
As above but using the bravo_downgrade.img file.
So I do (i), then immediately (ii), then the official RUU.
Correct?
Many thanks
EDIT: the reason I'm asking about the correct order is because this post:
http://forum.xda-developers.com/showpost.php?p=16686095&postcount=9
says that the Downgrader needs to be run first and then the stock flash, which is why I'm a bit confused.
No Expert said:
Hi and thanks,
No, it's an unbranded one.
Can I confirm these steps are right?
(i) Flash Stock Hboot
Verify the MD5SUM of the file
Flash HBOOT with phone in fastboot mode (Back+POWER) -> 'fastboot flash hboot bravo_alphaspl.img'
'fastboot reboot-bootloader'
'fastboot erase cache'
Do I need to reboot after this?
(ii) Downgrader
As above but using the bravo_downgrade.img file.
So I do (i), then immediately (ii), then the official RUU.
Correct?
Many thanks
EDIT: the reason I'm asking about the correct order is because this post:
http://forum.xda-developers.com/showpost.php?p=16686095&postcount=9
says that the Downgrader needs to be run first and then the stock flash, which is why I'm a bit confused.
Click to expand...
Click to collapse
Yup, that sounds correct.
bortak, worked perfectly and was able to return device to stock for repair by HTC under warranty.
It turns out the Sleep of Death was a faulty screen.
Thanks.
Related
hi
on friday I got a desire which belonged to a friend of mine and now through me becomes the phone of another friend. the phone was already rooted (I was the one who did it initially too) but that was a long time ago and there was no custom recovery (I think we used some kind of tethered-recovery) or anything like that on the phone. so I decided to correct that. my target was custom recovery, root, new rom, s-off preferably data++
unrevoked and revolutionary did of course not work for me so I decided to just flash the GB RUU basically like described here: http://forum.xda-developers.com/showthread.php?t=1626405
and that worked pretty good but now the phone is stuck in a bootloop which resets the phone right after starting the rom. I already tried reflashing the ruu (via goldcard just to be safe, though I am pretty sure I have the correct one (tmobile DE branded, t-mob101), that however did not change anything.
so now I don't really know what to do, please help me
thanks in advance
what's the hboot info?
thaaanks a lot. in the german forum so far noone has been repyling at all since yesterday.
fastboot and recovery (though stock) works btw.
fastboot / hboot info:
Bravo PVT1 Ship s-on
hboot-1.02.0001
Microp-031d
touch panel-synth101
radio-5.17.05.23
Jul 22 2011, 16:19:16
yeah recovery isn't gonna help..
Think you can only try the 2.3 RUU again.. otherwise you can't do much more.
------
If that doesn't work (after a couple of tries).. then the process is to:
- find an XTC Clip (they're expensive, not worth buying, look into whether some phone repair shops have them)
- S-OFF the phone with the xtc clip
- Download an alpharev stock bootloader pb99img (rename it to pb99img), put it on your sd-card and update it from hboot
- Do a full wipe in fastboot
- flash recovery
- flash a rom
then I have a serious problem. apart from trying over and over again I have no choice? because I as mentioned I already tried it twice.
could the radio be a problem because the point where the phone reboots should be the moment when it normally asks for the sim pin?
can you please point me to the absolut right RUU file? I just want to be cautious.
starting the ruu installer, getting the rom.zip file (which seems to contain nothing if I open it on the computer?), renaming it to PB99IMG.zip putting it onto the goldcard and starting into fastboot is the right way?
fleity said:
then I have a serious problem. apart from trying over and over again I have no choice? because I as mentioned I already tried it twice.
could the radio be a problem because the point where the phone reboots should be the moment when it normally asks for the sim pin?
can you please point me to the absolut right RUU file? I just want to be cautious.
starting the ruu installer, getting the rom.zip file (which seems to contain nothing if I open it on the computer?), renaming it to PB99IMG.zip putting it onto the goldcard and starting into fastboot is the right way?
Click to expand...
Click to collapse
Ohh so it boots? If it does, boot it without inserting the sim, enable USB debugging, run revolutionary to S-OFF, flash recovery, backup the ROM, do a full wipe and flash a custom ROM.. see what happens then.
sorry if it was that easy I would have done that a long time ago ^^°
the phone also reboots if there is no sim inserted.
can I maybe flash some other RUU? another GB version, WWE instead of tmob UK/DE or even Froyo?) even newer stuff? I read something about a 1.03 hboot somewhere? as long as I get this running again I am pretty much willing to do anything. however I still wonder why this is happening.
I am dieing a little bit here, I'm so stupid
is it possible that I really messed up badly here:
http://www.your-android.de/htc-desire-gingerbread-upgrade-steht-zum-download-bereit
"Hey guys, we’re happy to announce that Gingerbread for Desire is here! Please visit our Developer website to access the download. http://developer.htc.com
Please note that the following regional variants are not compatible with this upgrade: Germany (Telekom Deutschland), North America, South Korea and Japan."
so still.. why is exactly is not working and how can I fix it...
no there is only 1 GB RUU.. try installing it from the .exe (boot into fastboot, plug it in, run RUU.exe).. see what happens then
i didnt know you could install RUUs from fastboot.
update worked perfectly like before but still reboots after 1 second in the rom.
fleity said:
i didnt know you could install RUUs from fastboot.
update worked perfectly like before but still reboots after 1 second in the rom.
Click to expand...
Click to collapse
Does the phone get really hot by any chance?
öhm how exactly should I test that? keep it runing in fastboot or repeat the bootcycle?
fleity said:
öhm how exactly should I test that? keep it runing in fastboot or repeat the bootcycle?
Click to expand...
Click to collapse
Umm nah, just when it boots, is it really hot? i.e. hotter than you would expect it to be...
Try sticking it in the freezer for 15 minutes in a plastic bag, then try turning it on again..
what the f? oookay one quick question before however: if I can flash the ruu from fastboot can I use revolutionary from fastboot too? (cause if revolutionary works all problems are solved, I did not dare to try that since the new hboot came with the weird gb update)
I would not say it gets any hotter than usual however freezer it is
fleity said:
what the f? oookay one quick question before however: if I can flash the ruu from fastboot can I use revolutionary from fastboot too? (cause if revolutionary works all problems are solved, I did not dare to try that since the new hboot came with the weird gb update)
I would not say it gets any hotter than usual however freezer it is
Click to expand...
Click to collapse
no, can only use revolutionary when booted into the ROM unfortunately
If you got hold of an XTC clip as mentioned before however...
The freezer thing? some Deisre's have faced hardware faults before causing them to overheat, reboot all the time etc. if you tried to use a RUU it would always fail.. sticking it in the freezer helped.. for a few minutes.. so trying to see whether this is the problem.
you sir are my hero of the day
it booted! awesome, incredible, how could you even think of that. I am absolutly speechless and impressed.
I just rebooted it manually again and it sill works. thaaaaaaaaank you so much
can you pm your paypal adress I like to buy you a beer or sth similar?
so the next steps would be run revolutionary and flash a custom right?
fleity said:
you sir are my hero of the day
it booted! awesome, incredible, how could you even think of that. I am absolutly speechless and impressed.
I just rebooted it manually again and it sill works. thaaaaaaaaank you so much
can you pm your paypal adress I like to buy you a beer or sth similar?
so the next steps would be run revolutionary and flash a custom right?
Click to expand...
Click to collapse
Haha don't worry about it.. and don't get too happy.. once it heats up again you may just have the same problem...
But for now yes, S-OFF the phone with revolutionary and flash a custom recovery, then backup, do a full wipe (boot, system, data, cache, dalvik) and flash a custom ROM. Cyanogenmod is a good place to start (need to flash google apps after flashing CM though)
So I've been trying to root my dads old Desire for a while now, with no success - it is locked to o2 and I'm on Orange. I didn't really want to pay to unlock it, and rooting it would have been nice. I've done two phones before, so I figured it shouldn't be too bad. Eventually I discovered it was HBOOT 1.03, and this was the problem, so the solution was to backdate the software to an earlier version (the phone is still S-ON and I cannot get this thing to take ANYTHING)
I was trying to roll back from Froyo to 2.1.
The current problem is that now the phone will not boot. With a simple turn-on it just sits at the white HTC screen, or if you go into Hboot it tries (what I assume is) 'fastboot' and checks the PB99IMG.zip file on the SD card. If I say I don't want to update and go to 'recovery' it loads the screen with the exclamation mark in a triangle in it. The problem here is that pressing up+power does nothing. I've tried a quick press, and a long hold multiple times, and with no result except the first time. Unfortunately I didn't go through the proceedure the first time, assuming it'd work again. Damn!
If I start the update it says 'can not roll back the hboot version'. It also fails on the radio_v2.
Any help will be much appreciated, and if you need any details (I've probably missed something) please ask!
Thanks
papercutout said:
So I've been trying to root my dads old Desire for a while now, with no success - it is locked to o2 and I'm on Orange. I didn't really want to pay to unlock it, and rooting it would have been nice. I've done two phones before, so I figured it shouldn't be too bad. Eventually I discovered it was HBOOT 1.03, and this was the problem, so the solution was to backdate the software to an earlier version (the phone is still S-ON and I cannot get this thing to take ANYTHING)
I was trying to roll back from Froyo to 2.1.
The current problem is that now the phone will not boot. With a simple turn-on it just sits at the white HTC screen, or if you go into Hboot it tries (what I assume is) 'fastboot' and checks the PB99IMG.zip file on the SD card. If I say I don't want to update and go to 'recovery' it loads the screen with the exclamation mark in a triangle in it. The problem here is that pressing up+power does nothing. I've tried a quick press, and a long hold multiple times, and with no result except the first time. Unfortunately I didn't go through the proceedure the first time, assuming it'd work again. Damn!
If I start the update it says 'can not roll back the hboot version'. It also fails on the radio_v2.
Any help will be much appreciated, and if you need any details (I've probably missed something) please ask!
Thanks
Click to expand...
Click to collapse
If it fails with Radio_v2, then it's a radio brick, and that's the reason it won't boot. I'm afraid you can't do much, due to the hboot version.
abaaaabbbb63 said:
If it fails with Radio_v2, then it's a radio brick, and that's the reason it won't boot. I'm afraid you can't do much, due to the hboot version.
Click to expand...
Click to collapse
I'm not too worried about getting a different rom on it, or rooting it or anything any more, currently I'd like to just put it back into a working state, as it was, probably locked to o2, if you've any suggestions on how to do that?
papercutout said:
I'm not too worried about getting a different rom on it, or rooting it or anything any more, currently I'd like to just put it back into a working state, as it was, probably locked to o2, if you've any suggestions on how to do that?
Click to expand...
Click to collapse
First, try this:
http://forum.xda-developers.com/showthread.php?t=1564644
abaaaabbbb63 said:
First, try this:
http://forum.xda-developers.com/showthread.php?t=1564644
Click to expand...
Click to collapse
The one step here I'm halted by is producing a Goldcard - the link to the website on the tool doesn't work any more (I've scoured t'internet, and that's the general consensus). Any idea where else I can input the CID to get a Goldcard Image?
Also how do I run the RUU on my computer? What file is it in the HTC Desire Android Upgrade folder I need to run? Afterall, there's no file titled 'RUU.exe'
Thanks
papercutout said:
The one step here I'm halted by is producing a Goldcard - the link to the website on the tool doesn't work any more (I've scoured t'internet, and that's the general consensus). Any idea where else I can input the CID to get a Goldcard Image?
Also how do I run the RUU on my computer? What file is it in the HTC Desire Android Upgrade folder I need to run? Afterall, there's no file titled 'RUU.exe'
Thanks
Click to expand...
Click to collapse
Just realized that it wouldn't work, because you have to boot your phone for the downgrader tool.
You could try something else. Unlock your bootloader using the HTC Dev site :http://www.htcdev.com/bootloader, and then try installing a custom recovery.
abaaaabbbb63 said:
Just realized that it wouldn't work, because you have to boot your phone for the downgrader tool.
You could try something else. Unlock your bootloader using the HTC Dev site and then try installing a custom recovery.
Click to expand...
Click to collapse
I've unlocked the bootloader (although obviously I'm still S-ON and HBOOT 1.03), so how would I go about installing a custom recovery?
Everything I can find online implies I need to do it starting with the phone up and running...
Thanks
papercutout said:
I've unlocked the bootloader (although obviously I'm still S-ON and HBOOT 1.03), so how would I go about installing a custom recovery?
Everything I can find online implies I need to do it starting with the phone up and running...
Thanks
Click to expand...
Click to collapse
You download this:
http://forum.xda-developers.com/showthread.php?p=28277117
You extract the recovery.img from it.
You then use fastboot to flash it:
fastboot flash recovery recovery.img
abaaaabbbb63 said:
You download this:
http://forum.xda-developers.com/attachment.php?attachmentid=1631968&d=1357780284
You extract the recovery.img from it.
You then use fastboot to flash it:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
That worked spot on! Have you got anything you'd recommend I put on there now? (factory reset didn't do anything, didn't really expect it to)
I tried cyangenmod7 for the desire, but with no luck. File 'BAD' or somethign when tried to read it from the SD card.
papercutout said:
That worked spot on! Have you got anything you'd recommend I put on there now? (factory reset didn't do anything, didn't really expect it to)
I tried cyangenmod7 for the desire, but with no luck. File 'BAD' or somethign when tried to read it from the SD card.
Click to expand...
Click to collapse
Try a MildWild ROM. Maybe the CM7 download was somehow faulty.
Can ya post the link to the thread and not just post the PB99IMG file? Thanks
jmcclue said:
Can ya post the link to the thread and not just post the PB99IMG file? Thanks
Click to expand...
Click to collapse
Sorry jmc. Will do
abaaaabbbb63 said:
Try a MildWild ROM. Maybe the CM7 download was somehow faulty.
Click to expand...
Click to collapse
You're getting good at this
So, that's on and working, but it's still locked to the carrier, o2. I've just tried 'HTC Desire unlock v0.9.5' but that didn't work (despite the program telling me it went flawlessly).
Any more suggestions?
papercutout said:
You're getting good at this
So, that's on and working, but it's still locked to the carrier, o2. I've just tried 'HTC Desire unlock v0.9.5' but that didn't work (despite the program telling me it went flawlessly).
Any more suggestions?
Click to expand...
Click to collapse
Try using a different USB port.
abaaaabbbb63 said:
Try using a different USB port.
Click to expand...
Click to collapse
Nope, nada. I tried v0.94 too. Nothing again. I guess I'll need to get a key. Damn that hboot 1.03!
At least the phone is actually WORKING now though, thanks to you, appreciated.
Hello,
My adb devices is not showing my device.
I'm pretty sure I forgot to activate developer mode and turn on USB debugging. I can not flash any room and I'm stuck in a boot loop or just using TWRP. I'm completely lost in a way to get beyond this. I've been searching XDA for 4.5 hours straight and it seems some people have 80% of my problem but not 100%. I decided initially to follow a Youtube video that didn't mention anything about USB debugging so I'm wondering if that's the main issue in all of this. I've tried going back to stock RUU, through Hasoon2000's allinone but I keep getting failures. Just at a loss and would appreciate any help. I'm trying to go to the Skydragon Rom, but I'm willing to go back to stock to work my way back up. I've initially rooted this type of phone before, but I didn't follow the same method as last time(which was Hasoon's) as I thought it would work the same, I used this Youtube video, youtube/watch?v=_yo4eoCfxmE. (sorry link is weird cause I can't post links yet, add a .com after youtube!) I do not have S-Off. I just wanna know what I can do to get back to Skydragon or at least back to stock before my girlfriend beats my ass for messing up her phone
Valkalkas said:
Hello,
My adb devices is not showing my device.
I'm pretty sure I forgot to activate developer mode and turn on USB debugging. I can not flash any room and I'm stuck in a boot loop or just using TWRP. I'm completely lost in a way to get beyond this. I've been searching XDA for 4.5 hours straight and it seems some people have 80% of my problem but not 100%. I decided initially to follow a Youtube video that didn't mention anything about USB debugging so I'm wondering if that's the main issue in all of this. I've tried going back to stock RUU, through Hasoon2000's allinone but I keep getting failures. Just at a loss and would appreciate any help. I'm trying to go to the Skydragon Rom, but I'm willing to go back to stock to work my way back up. I've initially rooted this type of phone before, but I didn't follow the same method as last time(which was Hasoon's) as I thought it would work the same, I used this Youtube video, youtube/watch?v=_yo4eoCfxmE. (sorry link is weird cause I can't post links yet, add a .com after youtube!) I do not have S-Off. I just wanna know what I can do to get back to Skydragon or at least back to stock before my girlfriend beats my ass for messing up her phone
Click to expand...
Click to collapse
haha... Love :victory:
Now back to issue.
If you're in the bootloader you don't need USB Debugging enabled, you can still use the fastboot command regardless of USB debugging mode. Check
Code:
fastboot devices
not
Code:
adb devices
.
Make sure all the drivers are still fine on the PC, reinstall if you must.
On a side note, try not to use all-in-one toolkits as you really don't get to learn from using something like that. If you did it manually you'd already have a pretty good understanding on which command gets used in which instance i.e bootloader vs in-system.
I actually didn't use a all-in-one this time around but as soon as I unlocked boot loader and rooted I had issues installing the custom rom. I've used both phil z and twrp but it still gets stuck when I install the sky dragon, or viper for that matter to test and make sure it wasn't just a bad download. Earlier when I did fast boot devices it did show something but now it's just a blank space. I'm in bed now I would double check again to make sure but like I said it's been a few hours and now it's 4:38 am and I'm tired. I'll double check in the morning but I appreciate your response and I'll double check. Drivers should be good from last time but I will double check and make sure. Again thanks for responding!
Alright, now after some rest I've checked the fastboot devices and it does show up.
Tried flashing to latest SkyDragon again and it just sits on the HTC screen before boot looping.
The device is S-On, unlocked and says tampered. I've tried flashing the boot.img in bootloader after flashing the rom but still no dice.
Valkalkas said:
Alright, now after some rest I've checked the fastboot devices and it does show up.
Tried flashing to latest SkyDragon again and it just sits on the HTC screen before boot looping.
The device is S-On, unlocked and says tampered. I've tried flashing the boot.img in bootloader after flashing the rom but still no dice.
Click to expand...
Click to collapse
Latest skydragon, ARHD, InsertCoin and many more are meant for hboot 3.18 and above. If you boot to bootloader and see your hboot is 3.16, these ROMs won't work properly for you.
So check your hboot no.
Next ... check your CID and MID
If possible the OS version no. on bootloader too
You may need to revert to your stock ROM ... then check any OTA for your device
ckpv5 said:
Latest skydragon, ARHD, InsertCoin and many more are meant for hboot 3.18 and above. If you boot to bootloader and see your hboot is 3.16, these ROMs won't work properly for you.
So check your hboot no.
Next ... check your CID and MID
If possible the OS version no. on bootloader too
You may need to revert to your stock ROM ... then check any OTA for your device
Click to expand...
Click to collapse
Alright yeah, my hboot is 3.16. Tried looking up ways to update the fastboot but all I've seen is requiring S-Off.
CID is CWS____001
MID is 0P6B12000
The OS is blank, just says OS- (blank space)
Gonna try flashing stock recovery again.
Valkalkas said:
Alright yeah, my hboot is 3.16. Tried looking up ways to update the fastboot but all I've seen is requiring S-Off.
CID is CWS____001
MID is 0P6B12000
The OS is blank, just says OS- (blank space)
Gonna try flashing stock recovery again.
Click to expand...
Click to collapse
Yours is At&T (if I'm not wrong as I'm not familiar with this Sprint, Verizon and AT&T)
And there are RUU for both 4.4.2 and 4.4.3 (hboot 3.16 and 3.18) ... it's best for you to head over AT&T forum for better guidance.
http://forum.xda-developers.com/showthread.php?t=2757462
http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
ckpv5 said:
Yours is At&T (if I'm not wrong as I'm not familiar with this Sprint, Verizon and AT&T)
And there are RUU for both 4.4.2 and 4.4.3 (hboot 3.16 and 3.18) ... it's best for you to head over AT&T forum for better guidance.
http://forum.xda-developers.com/showthread.php?t=2757462
http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
Click to expand...
Click to collapse
Alright, thank you for your help. I relocked and I tried the second link you posted, but the ruu messes up after I accept the EULA and just keeps popping up boxes. Downloading the RUU from the first link now and gonna try that. I just run the RUU in fastboot usb right?
Again thanks, I had no idea to check for hboot versions when rooting/flashing in the time I've rooted some devices so guess I'm learning something the hard way.
Edit: Same thing with the first link. I feel like I'm in the wrong place trying to run the RUU in fastboot usb?
Alright, tried running the RUU's again on the black screen with the silver HTC letters as suggested by someone else and the program still acts up after the EULA.
Alright, I was able to find a nandroid backup and restore it through there, so now I'm back in business. Thanks for the help!
I'm currently running Android Revolution HD on my new M9, unlocked, s-off also.
Found out that I have the battery is faulty, so I need to return it to stock, and get it back the shop for a replacement.
However, I stupidly didn't make a back up of my stock rom.
The CID of my phone is O2___01
I've downloaded the stock rom from this site, and flashed it using the RUU command. However when it flashes, then tells me to reboot, it still has Android Revolution HD on it.
I've spent a few hours browsing the forum, and still I've come to no avail.
Any help would be well appreciated!
Webbage said:
I'm currently running Android Revolution HD on my new M9, unlocked, s-off also.
Found out that I have the battery is faulty, so I need to return it to stock, and get it back the shop for a replacement.
However, I stupidly didn't make a back up of my stock rom.
The CID of my phone is O2___01
I've downloaded the stock rom from this site, and flashed it using the RUU command. However when it flashes, then tells me to reboot, it still has Android Revolution HD on it.
I've spent a few hours browsing the forum, and still I've come to no avail.
Any help would be well appreciated!
Click to expand...
Click to collapse
You don't provide much information so it's hard to help. So let's start at the bginning: What firmare version are you using? (It's stated in Download Mode in the line with "OS" at the beginning.)
You tried to flash a RUU? Which one? Have there been any error outputs? If yes, which ones? Since you're S-OFF flashing a RUU should not be a problem at all so these outputs are very important if you want any help.
I tried to flash 1.40.206.8 -> 2.10.206.2 from this page
Code:
http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
Also I followed this,
Code:
http://forum.xda-developers.com/one-m9/development/firmware-t3068243
downloaded the correct RUU zip, tried to flash, got the error code telling me I need to immediately flash again which I did. Rebooted, and it just set up Android Revolution HD again.-
My firmware currently is 2.10.206.2
Im sure it's something stupid I missing out?
Webbage said:
I tried to flash 1.40.206.8 -> 2.10.206.2 from this page
Code:
http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
Also I followed this,
Code:
http://forum.xda-developers.com/one-m9/development/firmware-t3068243
downloaded the correct RUU zip, tried to flash, got the error code telling me I need to immediately flash again which I did. Rebooted, and it just set up Android Revolution HD again.-
My firmware currently is 2.10.206.2
Im sure it's something stupid I missing out?
Click to expand...
Click to collapse
As far as I know Sneakyghost doesn't provide any RUUs. Those are only firmware packages that do not contain a rom. So it's no miracle that you're still booting ARHD.
You can download O2 RUUs from here, here or here. Any of the X.XX.206.X files will work since you are S-OFF. Do you have a SD card that is not bigger than 32gb? If yes, format it to fat32, copy one O2 RUU to its root directory and rename that file to "0PJAIMG.zip". If you then boot to Download Mode you will be asked to push the Volume Up button and the RUU will start flashing. If it reboots to system instead of rebooting to Download Mode you will have to power off your phone and boot to Download Mode manually. The RUU will continue then. At the end you will be asked to push the power button so that your phone gets shut down. If you now start your phone you will be back on a stock system.
Be aware that there is no RUU for your current firmware. Since you're S-OFF that doesn't matter but your phone will be downgraded at the end.
Ahh no wonder! haha
Going to try this shortly, so will let you know how I get on!
After its flashed, I'll be good to lock again and go s-on? Then return to the shop?
Webbage said:
Ahh no wonder! haha
Going to try this shortly, so will let you know how I get on!
After its flashed, I'll be good to lock again and go s-on? Then return to the shop?
Click to expand...
Click to collapse
Relock only after you successfully tested that your device is booting normaly. After that you theoretically could re-S-ON. (But I would never do that because there is always a risk of hardbricking your phone if you re-S-ON and there is anything still modified that you didn't notice. For safety reasons S-OFF should always be considered as a oneway.)
Edit: I'm not completely sure but I actually doubt that they will check whether your phone was S-OFFed or not. If I think about the people who are working at the O2 or vodafone shops in my city I would say they do not even know what a bootloader is...
Agreed, use the s-off command to change back to "LOCKED" and leave it s-off. Too much of a risk otherwise.
If in the unlikely event they see it, you can play dumb, because a few rare people have gotten s-off phones from the factory and it doesn't prove you did anything.
Flippy498 said:
Relock only after you successfully tested that your device is booting normaly. After that you theoretically could re-S-ON. (But I would never do that because there is always a risk of hardbricking your phone if you re-S-ON and there is anything still modified that you didn't notice. For safety reasons S-OFF should always be considered as a oneway.)
Edit: I'm not completely sure but I actually doubt that they will check whether your phone was S-OFFed or not. If I think about the people who are working at the O2 or vodafone shops in my city I would say they do not even know what a bootloader is...
Click to expand...
Click to collapse
All sorted mate! Thanks a lot for your help!
What recovery am I best restoring on it?
Webbage said:
All sorted mate! Thanks a lot for your help!
What recovery am I best restoring on it?
Click to expand...
Click to collapse
Didn't the RUU flash the corresponding stock recovery?
Flippy498 said:
Didn't the RUU flash the corresponding stock recovery?
Click to expand...
Click to collapse
My bad, I didn't check.
All sorted now, thanks again bud!
I'm a very new android user, so please forgive my ignorance.
I'm using a sim unlocked AT&T M8 outside USA with a different carrier. Right now, the bootloader is Locked, CID is 11111111 and S-OFF. I've downloaded the official marshmallow AT&T RUU for m8 from htc website.
I follow the install instructions until the update actually starts. Then it stops after about 10-20 seconds and shows Error 155: unknown error and enters into the recovery steps (in the RUU). My current software number is 4.28.502.2 and im trying to update to RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5
Can someone please help me out with this? I've been trying for over a week now. I will never receive the OTA's since I'm not using an AT&T sim. So RUU is the only other option left. Thanks a lot in advance.
http://forum.xda-developers.com/showpost.php?p=66886759&postcount=23
ckpv5 said:
http://forum.xda-developers.com/showpost.php?p=66886759&postcount=23
Click to expand...
Click to collapse
Thanks for your reply man, but im extremely lost here. Could you please guide me step by step? I've downloaded the firmware. Where do I put it? I've tried the adb folder. But it show error: can not locate firmware.zip.
Edit: Another question. Is that firmware applicable for my device?
The firmware is applicable BUT since you're using your device outside USA and not on AT&T carrier, S-Off .. the best thing for you to do is fully convert your device to other region, maybe a EU region or Dev Edition .. more suitable for you.
I read somewhere, with the latest firmware you may have calls problem due to Voice HD implemented by AT&T
If you're interested in converting, I will guide you (when I am available)
ckpv5 said:
The firmware is applicable BUT since you're using your device outside USA and not on AT&T carrier, S-Off .. the best thing for you to do is fully convert your device to other region, maybe a EU region or Dev Edition .. more suitable for you.
I read somewhere, with the latest firmware you may have calls problem due to Voice HD implemented by AT&T
If you're interested in converting, I will guide you (when I am available)
Click to expand...
Click to collapse
That would be very kind of you, thanks. Though, i think I've already messed up my phone. I finally got to update with the firmware in the link. The RUU was going on smoothly as well, until it reached 38% when Error 155 showed up again. The phone then went on to the bootloader screen with no options for fastboot, restore or such. I restarted it and entered the bootloader. My firmware is being shown as 6.20.502.5 but when rebooting the phone it won't go past the screen with the HTC logo. I'd be extremely grateful if you could help me out of this mess.
Also, when i open htc sync man, OS number and HTC Sense number shows up as blank, while the firmware number is shown as 6.20.502.5
Big-Bonsai said:
Also, when i open htc sync man, OS number and HTC Sense number shows up as blank, while the firmware number is shown as 6.20.502.5
Click to expand...
Click to collapse
Aren't you supposed to uninstall Htc Sync Manager before you run the RUU ?
That was clearly stated in link that I gave you earlier, and you also need PC with USB 2.0
Uninstall HTC Sync Manager but leave HTC USB drivers then try again to run RUU after you put the device on bootloader/fastboot mode.
ckpv5 said:
Aren't you supposed to uninstall Htc Sync Manager before you run the RUU ?
That was clearly stated in link that I gave you earlier, and you also need PC with USB 2.0
Click to expand...
Click to collapse
Yeah I did. I re-installed it later to see if it would show any information.
Most important is RUU must complete 100%, no error 155
I never use Htc Sync Manager, so I don't know what is shown there.
ckpv5 said:
Most important is RUU must complete 100%, no error 155
I never use Htc Sync Manager, so I don't know what is shown there.
Click to expand...
Click to collapse
So I'm gonna try the RUU again. I'll keep you updated. You've been a big help. Thanks a lot!!
Big-Bonsai said:
I'm a very new android user, so please forgive my ignorance.
I'm using a sim unlocked AT&T M8 outside USA with a different carrier. Right now, the bootloader is Locked, CID is 11111111 and S-OFF. I've downloaded the official marshmallow AT&T RUU for m8 from htc website.
I follow the install instructions until the update actually starts. Then it stops after about 10-20 seconds and shows Error 155: unknown error and enters into the recovery steps (in the RUU). My current software number is 4.28.502.2 and im trying to update to RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5
Can someone please help me out with this? I've been trying for over a week now. I will never receive the OTA's since I'm not using an AT&T sim. So RUU is the only other option left. Thanks a lot in advance.
Click to expand...
Click to collapse
I don't know if it's the problem,but did you try the RUU after unlocking your bootloader as you are S-OFF?
I think it's supposed to be unlocked if you have S-OFF.
Edit:Just got to know that S-OFF devices have nothing to do with unlocked or locked bootloader.
Why don't you try a EU RUU?Mine was also a AT&T device,but I converted it.
Jongla said:
I don't know if it's the problem,but did you try the RUU after unlocking your bootloader as you are S-OFF?
I think it's supposed to be unlocked if you have S-OFF.
Edit:Just got to know that S-OFF devices have nothing to do with unlocked or locked bootloader.
Why don't you try a EU RUU?Mine was also a AT&T device,but I converted it.
Click to expand...
Click to collapse
Hey man, thanks for replying here. I sent you a pm. Could you please check?
ckpv5 said:
Most important is RUU must complete 100%, no error 155
I never use Htc Sync Manager, so I don't know what is shown there.
Click to expand...
Click to collapse
Hello there. I kind of made it work. What I did was take the rom.zip from the ruu file and flash it via htc fastboot special. And it worked well. The only problem I'm facing now is that the boot animations are EXTREMELY slow. But once it's past that, everything seems pretty normal. I wiped the cache from recovery but that didn't help. Do you have any suggestions for me?
Big-Bonsai said:
\The only problem I'm facing now is that the boot animations are EXTREMELY slow. But once it's past that, everything seems pretty normal. I wiped the cache from recovery but that didn't help.
Click to expand...
Click to collapse
Meaning the boot animations are slow every time you boot, or just the first time (its unclear from what you've posted)? First time booting after RUU will be slow, due to cache being setup, etc. And clearing cache will cause that process to repeat when you start up again.
---------- Post added at 09:32 AM ---------- Previous post was at 09:30 AM ----------
Jongla said:
I think it's supposed to be unlocked if you have S-OFF.
Edit:Just got to know that S-OFF devices have nothing to do with unlocked or locked bootloader.
Click to expand...
Click to collapse
Neither of those statements is entirely correct.
With s-off, you can run an RUU with bootloader locked or relocked. Essentially, the check for the bootloader unlocked condition is bypassed with s-off.
But having the bootloader locked still means its locked (even with s-off). Meaning you can't do things like flash custom recovery with bootloader locked (even with s-off).
redpoint73 said:
Meaning the boot animations are slow every time you boot, or just the first time (its unclear from what you've posted)? First time booting after RUU will be slow, due to cache being setup, etc. And clearing cache will cause that process to repeat when you start up again.
Hello there. Thanks for the reply. What I meant was, the boot animations are slow every time I reboot the device.
Things I have already done:
1. Flashed the rom.zip again.
2. Factory reset.
3. Wiped the cache from recovery multiple times.
4. Restarted in all possible ways. Normal restart. Power off, wait 10 minutes and power on again. Pressed the power and volume up button for restarting. Reboot via fastboot.
I'd really appreciate if you could help me out.
Click to expand...
Click to collapse
redpoint73 said:
Meaning the boot animations are slow every time you boot, or just the first time (its unclear from what you've posted)? First time booting after RUU will be slow, due to cache being setup, etc. And clearing cache will cause that process to repeat when you start up again.
---------- Post added at 09:32 AM ---------- Previous post was at 09:30 AM ----------
Neither of those statements is entirely correct.
With s-off, you can run an RUU with bootloader locked or relocked. Essentially, the check for the bootloader unlocked condition is bypassed with s-off.
But having the bootloader locked still means its locked (even with s-off). Meaning you can't do things like flash custom recovery with bootloader locked (even with s-off).
Click to expand...
Click to collapse
Hello there. Thanks for the reply. What I meant was, the boot animations are slow every time I reboot the device.
Things I have already done:
1. Flashed the rom.zip again.
2. Factory reset.
3. Wiped the cache from recovery multiple times.
4. Restarted in all possible ways. Normal restart. Power off, wait 10 minutes and power on again. Pressed the power and volume up button for restarting. Reboot via fastboot.
I'd really appreciate if you could help me out.
Since you've already flashed the RUU again, I don't think there is much else you can do. Maybe its a common issue with the new build?
redpoint73 said:
Since you've already flashed the RUU again, I don't think there is much else you can do. Maybe its a common issue with the new build?
Click to expand...
Click to collapse
Man I searched EVERYWHERE. People dont seem to have any problems like this. What I did find out was that this might happen if the firmware or kernel numbers dont match (or something?). Can you tell me if I did anything wrong?
Big-Bonsai said:
What I did find out was that this might happen if the firmware or kernel numbers dont match (or something?).
Click to expand...
Click to collapse
That only applies to flashing ROMs in custom recovery. WHich is completely different from RUU. RUU re-writes all partitions, including firmware, kernel, ROM, and a bunch of others. So there isn't a possibility of a mismatch; as long as the RUU ran properly. And since you ran the RUU twice, you pretty much eliminated the possibility it didn't install completely.
Some other options you may consider:
1) Unlock the bootloader, flash TWRP custom recovery, flash a different ROM and see if the slow boot issue persists.
2) Change CID and/or MID (which you are free to do since you are s-off) and try another RUU; such as Developer's Edition or Euro.
redpoint73 said:
That only applies to flashing ROMs in custom recovery. WHich is completely different from RUU. RUU re-writes all partitions, including firmware, kernel, ROM, and a bunch of others. So there isn't a possibility of a mismatch; as long as the RUU ran properly. And since you ran the RUU twice, you pretty much eliminated the possibility it didn't install completely.
Some other options you may consider:
1) Unlock the bootloader, flash TWRP custom recovery, flash a different ROM and see if the slow boot issue persists.
2) Change CID and/or MID (which you are free to do since you are s-off) and try another RUU; such as Developer's Edition or Euro.
Click to expand...
Click to collapse
Thank you so much for the reply. I'd like to take your second suggestion. Can you please point me to the right direction? Or guide me through the steps. I don't know if it's asking too much of you. Thanks anyways.
Big-Bonsai said:
Thank you so much for the reply. I'd like to take your second suggestion. Can you please point me to the right direction? Or guide me through the steps.
Click to expand...
Click to collapse
Which version do you want to "convert" to?
Dev Ed is easy, it shares the same model ID (MID) as AT&T, and you already have SuperCID. So all you would need to do is run the MM Dev Ed RUU: http://dl3.htc.com/application/RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4.exe
Euro is a bit more steps, you would need to change to the Euro MID: http://forum.xda-developers.com/showthread.php?t=2708581
Then run Euro MM RUU, noting that relocking bootloader is not needed for you (since you have s-off): http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6