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!
Related
tried to flash kernel, then rebooted, then it wont start , its stuck on the HTC loading screen, wont open anymore, the only thing i can access is the bootloader, tried to revert it back, i locked the boot loader, it says relocked still not working, erased all the data even the rom accidentally wiped it, how can i install a stock rom, can't open the device anymore
http://forum.xda-developers.com/showthread.php?t=1609190
mikey0105 said:
tried to flash kernel, then rebooted, then it wont start , its stuck on the HTC loading screen, wont open anymore, the only thing i can access is the bootloader, tried to revert it back, i locked the boot loader, it says relocked still not working, erased all the data even the rom accidentally wiped it, how can i install a stock rom, can't open the device anymore
Click to expand...
Click to collapse
To go back to stock:
1. you need to flash stock recovery
2. re-lock bootloader
3. run the RUU that goes with your CID
Or if you made a backup straight after flashing CWM, you do the following:
1. restore your back up
2. flash stock recovery
3. re-lock bootloader.
And please if you're gonna follow the link that nobnut gave, read it carefully and follow it as per instructions.
thanks so much guys, sorry for the trouble. one last question i guess. how to determine the correct ruu, i can see on the box saying made i china though
mikey0105 said:
thanks so much guys, sorry for the trouble. one last question i guess. how to determine the correct ruu, i can see on the box saying made i china though
Click to expand...
Click to collapse
Is it an unbranded phone?
Go here http://hoxroms.serveftp.com/ or here
http://www.filefactory.com/f/7cc7b2fbdd03c031/
And you might have try the ones from Asia.
Seriously though you should be prepared to read before you dive into things. You should've known what CID/RUU you needed before flashing any ROM. Because you might brick your phone without reading and following instructions.
Do you know what was your original ROM version was before using the custom ROM?
hmmm ill try asia RRU, since im from phil, i can see a telstra logo below your name, im actually working for telstra based here in Philippines...
mikey0105 said:
hmmm ill try asia RRU, since im from phil, i can see a telstra logo below your name, im actually working for telstra based here in Philippines...
Click to expand...
Click to collapse
My friends here in Australia are from Phils. Anyway all you can do is try the Asian RUUs. I would start with this one http://www.filefactory.com/file/6d5...Radio_1.1204.103.14_release_257077_signed.exe
ill try that after this one
from ASIA_SEA version 1.28.728.9
thanks so much for your help, i'll actually go there before this year ends,
Hi guys,
Hoping someone can help, have bricked my Australian Optus stock One X. I have tried to follow all threads related to loading stock or custom roms from fastboot and am unable to. I still have CWM recovery 5.8.2.7 touch installed.
I had previously rooted it and installed Android Revolution HD 5.1.0 and seemed to be fine but was unstable and would crash and reboot in certain apps. In trying to revert back to stock I stupidly formatted the SD card, DUMB ASS!
I have downloaded stock rom 1.29.401.7-DUO, all-in-one rootkit, and the ARHD ROM and have tried to either:
1) flash ARHD with bootloader still unlocked, doesn't work
2) follow reflashing stock process ie flash stock recovery, relock bootloader, then flash stock ROM, and am getting stuck on just reflashing the stock recovery. When I try to open stock recovery it takes me to a black screen with a red ! in a triangle, this is with the bootloader relocked.
If anyone is able to help an enthusiast noob like me I'd be very appreciative and would also be more than willing to donate for the trouble.
MAKE SURE you have exactly the right RUU for your phone, whatever the rom was on you were using, ie, 1.26, 1.28, 1.29, you need the same version of RUU, i discovered the problem trying to flash RUUs and after 2 days finally got the correct one, thats when i realised, unlike on other phones, you cant downgrade the One X and when recovering it seems to prefer the one that matches what you were using.
Also make sure youre cid is supported in that RUU, ie, HTC 001, TMOB 054, etc etc, mine can only accept 401 roms, so they must match exactly, until we can get S-Off this problem will remain, dont worry about recovery, so the guide on in case of disaster, you cant go wrong with it, relock your bootloader and get your RUU installed, from their update it to your latest ics version and then if you must reflash your cwm and root it.
Thanks for the info, graemeg. After downloading an RUU that was .exe file, I felt I was getting closer, as it was an AU Optus RUU. But it turns out that my current version is 1.28.980.10 and the RUU version was 1.26.980.3 and so yes I met with the non-downgrading issue.
It seems that there is not currently a stock 1.28.980.10 RUU at the moment, so might be using this as an ornament for much longer than I would have hoped/thought. Bummer.
agentorange82 said:
Thanks for the info, graemeg. After downloading an RUU that was .exe file, I felt I was getting closer, as it was an AU Optus RUU. But it turns out that my current version is 1.28.980.10 and the RUU version was 1.26.980.3 and so yes I met with the non-downgrading issue.
It seems that there is not currently a stock 1.28.980.10 RUU at the moment, so might be using this as an ornament for much longer than I would have hoped/thought. Bummer.
Click to expand...
Click to collapse
You can get 1.28.980.10 from htcdev downloads. I would link but I'm a new user, just filter by One X, Optus, and it's there.
Thanks again for the help. I have seen those files on htcdev website, but don't know how to use them
I don't know how to load a RUU that is not a .exe file...if anyone is able to assist, again, I would really appreciate it and will donate once up and running again.
Edit: I just wanted to add that I have tried to follow the thread that explains how to load/flash recovery and boot images via fastboot in command prompt, and have not been able to. So I don't think I'm a complete dumb ass, but do need someone with the knowledge and patience to guide me through it. Please!
First thing first, do you have the right RUU with you ?
If not, maybe this is the one for you : http://hoxroms.serveftp.com/RUU_END...Radio_1.1204.103.14_release_258004_signed.exe
second: do you have fastboot directory set up on your pc ? and htc usb driver too ?
Just starting the download now, I think that could be the RUU I've been looking for. Yes I have the drivers and fastboot directory. Will give this RUU a go and let you know, thanks for the quick reply, ckpv5!
Most important before you run the RUU, you need to:
1) have a stock recovery flashed to you your device first (I believe you already have one)
2) relock the bootloader - fastboot oem lock
3) run RUU, it should work.
THANK YOU!
ckpv5, thank you for the link to the updated RUU. Phone is functioning again, stock. Donation coming your way. Thanks for all your help. agentorange82.
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!
Hi everyone,
It would appear that my phone is stuck in a permanent boot loop. I'm still on the latest official rom from my carrier, it's not rooted nor have I made any changes to the bootloader.
The only thing that I did was restart my phone from within the OS after I couldn't launch the official SMS app (some MMS process error).
Now I'm stuck in a boot loop where the phone doesn't get past the first "HTC" logo page. I also notice that there are two thin dark horizontal lines on the top and middle of the screen that weren't there before. They look like clusters of dead pixels and are across the whole screen.
I've tried using the official bootloader to do a factory reset and wipe cache but I'm still having the same issue.
What else can I try? Is it safe for me to unlock the bootloader and try flashing a custom ROM while the phone is in this state?
I'd try to look for an RUU that matches your firmware before trying anything else.
Sent from my HTC 10 using XDA Labs
squ89r97 said:
I'd try to look for an RUU that matches your firmware before trying anything else.
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
I've tried to find it but I'm not having luck.
Since I'm S-ON I can only flash the ROM with the same firmware and I've figured that I need:
version: 3.35.166.12 for CID: VODAP120 (A1 Telekom Austria).
Now in case I can't find it, I would need to unlock the bootloader and flash a custom recovery.
However, since there is no way to go S-OFF without actually booting into the phone is there a risk of bricking the phone when trying to flash a custom ROM?
P$YCH0 said:
I've tried to find it but I'm not having luck.
Since I'm S-ON I can only flash the ROM with the same firmware and I've figured that I need:
version: 3.35.166.12 for CID: VODAP120 (A1 Telekom Austria).
Now in case I can't find it, I would need to unlock the bootloader and flash a custom recovery.
However, since there is no way to go S-OFF without actually booting into the phone is there a risk of bricking the phone when trying to flash a custom ROM?
Click to expand...
Click to collapse
If everything is official, I'd send it back and get a replacement.
P$YCH0 said:
I've tried to find it but I'm not having luck.
Since I'm S-ON I can only flash the ROM with the same firmware and I've figured that I need:
version: 3.35.166.12 for CID: VODAP120 (A1 Telekom Austria).
Now in case I can't find it, I would need to unlock the bootloader and flash a custom recovery.
However, since there is no way to go S-OFF without actually booting into the phone is there a risk of bricking the phone when trying to flash a custom ROM?
Click to expand...
Click to collapse
If your phone has a warranty send it back. For it to bork the way it has it was probably faulty, unless you know something we don't..
You could revive the phone but it may still have a fault.
Beamed in by telepathy.
squ89r97 said:
If everything is official, I'd send it back and get a replacement.
Click to expand...
Click to collapse
shivadow said:
If your phone has a warranty send it back. For it to bork the way it has it was probably faulty, unless you know something we don't..
You could revive the phone but it may still have a fault.
Beamed in by telepathy.
Click to expand...
Click to collapse
Hi guys,
Thank you very much for the friendly help. I've found the RUU file and it revived it. Wasn't free though (ir-file.com).
When I get the time I'll re-upload it and make available in one of the RUU threads.
Anyway, the first thing I did was to unlock the bootloader, install TWRP, root and finally S-OFF. If I had TWRP to start with I could have avoided all this hassle and just restore the boot partition for example.
However it does worry me a bit that such a thing occurred out of the blue. Are there any ways of checking if there is storage corruption, bad sectors in memory ect?
P$YCH0 said:
I've tried to find it but I'm not having luck.
Since I'm S-ON I can only flash the ROM with the same firmware and I've figured that I need:
version: 3.35.166.12 for CID: VODAP120 (A1 Telekom Austria).
Now in case I can't find it, I would need to unlock the bootloader and flash a custom recovery.
However, since there is no way to go S-OFF without actually booting into the phone is there a risk of bricking the phone when trying to flash a custom ROM?
Click to expand...
Click to collapse
P$YCHO, How did you find the version number and CID code, I can't see those anywhere on the bootloader of recovery?
Thanks
templer59 said:
P$YCHO, How did you find the version number and CID code, I can't see those anywhere on the bootloader of recovery?
Thanks
Click to expand...
Click to collapse
Hold the power button and volume down while booting. The OS line will show you the ROM version that you have to look for when trying to find the RUU. You need to install ADB and Fastboot and run a special command to read the CID and other device data. Something like allvars, can't remember exactly, did it a year ago when I got the phone
Sent from my HTC One M9 using Tapatalk
P$YCH0 said:
Hold the power button and volume down while booting. The OS line will show you the ROM version that you have to look for when trying to find the RUU. You need to install ADB and Fastboot and run a special command to read the CID and other device data. Something like allvars, can't remember exactly, did it a year ago when I got the phone
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
You mean "connect it to a pc while in download mode, install a copy of fastboot.exe and type: fastboot getvar.
P$YCH0 said:
Hi guys,
Thank you very much for the friendly help. I've found the RUU file and it revived it. Wasn't free though (ir-file.com).
When I get the time I'll re-upload it and make available in one of the RUU threads.
Anyway, the first thing I did was to unlock the bootloader, install TWRP, root and finally S-OFF. If I had TWRP to start with I could have avoided all this hassle and just restore the boot partition for example.
However it does worry me a bit that such a thing occurred out of the blue. Are there any ways of checking if there is storage corruption, bad sectors in memory ect?
Click to expand...
Click to collapse
If you need permanent storage for the ruu you got let me know as i have plenty of gdrive space.
Beamed in by telepathy.
Hi guys, I am in the exact same situation and don't seem to be able to find the appropriate RUU file for my phone. Can you please give me some indication regarding how to find it.
So far I managed to unlock the bootloader, install TWRP and attempted flashing several RUU files without any success whatsoever.
Thanks a lot in advance!
Cheers!