Related
Hi
I have accidentaly wiped system and sd card in CWM and cant mount via usb. I cannot find a stock HTC One X RUU and I had downloaded o2 RUU (would prefer carrier branded as want to return!!! although doesn't matter) but that was corrupted and downloaded off a chiness site that has stopped hosting it!
Please help me!
Doesnt matter if all you can find is a recovery that you can mount USB!! That would be great!!
Thank you very much guys!!!!!!!!!!!!!!!!!!!!!!!!!!!
-----------------------------------------------------------------------------------------------------------------------------------------------------
Thank you very much for all of your help! I have solved my issue.
I needed to download the stock o2 uk RUU and relock the bootloader and run the program in fast boot. I have just made my nandroid backup and planning to upload it so anyone else can use it! (it wont have my details on, just as if the os has been installed from scratch)
Steven
Please read before posting/flashing/wiping.
What is the CID of your device. You can only flash a stock RUU with matching CID.
So you need to download the correct RUU for your device.
All stock RUUs available are here
.
Keep thread on topic please
How do I find my CID?
stevepork said:
Hi
I have accidentaly wiped system and sd card in CWM and cant mount via usb. I cannot find a stock HTC One X RUU and I had downloaded o2 RUU (would prefer carrier branded as want to return!!! although doesn't matter) but that was corrupted and downloaded off a chiness site that has stopped hosting it!
Please help me!
Doesnt matter if all you can find is a recovery that you can mount USB!! That would be great!!
Thank you very much guys!!!!!!!!!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
If you would have spent 10 seconds looking in the Dev thread you would have found a list of all the available RUU's to download.
(http://forum.xda-developers.com/showthread.php?t=1543604)
Download your required RUU, boot into Fastboot-USB and run.
Next time be more careful and fully understand what you are doing before doing it otherwise you will end up with a £600 paperweight.
dr9722 said:
If you would have spent 10 seconds looking in the Dev thread you would have found a list of all the available RUU's to download.
(http://forum.xda-developers.com/showthread.php?t=1543604)
Download your required RUU, boot into Fastboot-USB and run.
Next time be more careful and fully understand what you are doing before doing it otherwise you will end up with a £600 paperweight.
Click to expand...
Click to collapse
That is why I started this thread!!! I don't know which is the correct one!!! I started on o2 uk rom and then flashed android revolution!!!
You've just answered your own question - look for the RUU with o2 UK in the name...
stevepork said:
That is why I started this thread!!! I don't know which is the correct one!!! I started on o2 uk rom and then flashed android revolution!!!
Click to expand...
Click to collapse
Flash the one that says o2 UK then?
Though I also wonder. How do you match CID to the firmware package? When I try to get my CID in fastboot or w/e, it says no CID like i've read around here. Any thoughts?
EddyOS said:
You've just answered your own question - look for the RUU with o2 UK in the name...
Click to expand...
Click to collapse
i unlocked the bootloader so if the op did the same their CID will be "none" and therefore the RUU wont flash.
treebill said:
i unlocked the bootloader so if the op did the same their CID will be "none" and therefore the RUU wont flash.
Click to expand...
Click to collapse
Ahh, that is what I did. Does anyone know how to get around this or relock it. I understood that when you relock it, the CID doesnt change
stevepork said:
Ahh, that is what I did. Does anyone know how to get around this or relock it. I understood that when you relock it, the CID doesnt change
Click to expand...
Click to collapse
You can't get around it nor you can change the CID unless we get S-OFF.
shadowboy23 said:
You can't get around it nor you can change the CID unless we get S-OFF.
Click to expand...
Click to collapse
Okay, I guess i will have to wait until the clockwork recovery gets USB mount!
Sorry but if you just want to return to stock you can do
1. Restore you nandroid backup, flash stock recovery and then relock the bootloader.
OR
2. You can flash stock recovery, relock bootloader and then run the RUU that corresponds to your CID/region.
I am probably answering my own question my CID is H3G_001. There doesnt appear to a 3 mobile ruu at all. Any help here? Fortunately its not urgent but may be handy if/when they release the upgrade
oisindubh said:
I am probably answering my own question my CID is H3G_001. There doesnt appear to a 3 mobile ruu at all. Any help here? Fortunately its not urgent but may be handy if/when they release the upgrade
Click to expand...
Click to collapse
Is your ROM the O2 UK?
Ooops sorry about that.
shadowboy23 said:
Sorry but if you just want to return to stock you can do
1. Restore you nandroid backup, flash stock recovery and then relock the bootloader.
OR
2. You can flash stock recovery, relock bootloader and then run the RUU that corresponds to your CID/region.
Click to expand...
Click to collapse
Thank you, very much. That was all I needed. Why does everyone have to bee rude? Be kine to a newbie!! I have only had an iPhone and a Dell Streak before this device!
You have to relock the bootloader to flash the RUU
Sent from my HTC Sensation Z710e using xda premium
how are you guys checking CID?
Using terminal emulator? do you need root?
I tried ADB shell command since the fastboot command doesn't work, and I get error:device not detected
pewpewbangbang said:
how are you guys checking CID?
Using terminal emulator? do you need root?
I tried ADB shell command since the fastboot command doesn't work, and I get error:device not detected
Click to expand...
Click to collapse
CID getter from the market.
I dont know, sorry. I do know though that mine came originally with 02 uk rom and that CID will only work with the one rom that came originally with your phone. It may be different for unlocked devices.
Thank you very much for everyone's help
Steven
hi
i need to ruu ruu 2.17.771.3 htc one x .exe .Many search on the Internet, but to no avail
Hasn't leaked yet - 3 UK right?
I'd love to know when this appears. Are all RUU's generally leaked from inside HTC?
I've ota update on the 3 Sweden.
Has anyone got the 2.17.771.3 ROM yet?
I need this one too!
try using this
nabel_sweed said:
hi
i need to ruu ruu 2.17.771.3 htc one x .exe .Many search on the Internet, but to no avail
Click to expand...
Click to collapse
if you are in need of the latest factory stock for your HOX try this:
http://forum.xda-developers.com/showthread.php?t=1546970
Note: it's an unbranded odexed ROM (HTC Sense 4.1 UI build 2.17.401.2) so you will get OTA updates
big thanks to mike1986
nabel_sweed said:
hi
i need to ruu ruu 2.17.771.3 htc one x .exe .Many search on the Internet, but to no avail
Click to expand...
Click to collapse
If u need the 2.17.771.3 3uk ruu inbox me i know where to get it from.
Plzzz tell me from where I can download it...
josehtc_onex said:
If u need the 2.17.771.3 3uk ruu inbox me i know where to get it from.
Click to expand...
Click to collapse
mfdasti said:
Plzzz tell me from where I can download it...
Click to expand...
Click to collapse
Searching fot the same RUU myself.. Seems that nobody has a link...
goliath969 said:
Searching fot the same RUU myself.. Seems that nobody has a link...
Click to expand...
Click to collapse
I have it on my PC and just used it to get my phone out of a boot loop. I used an RUU and did an OTA update. Somehow messed up trying to re-root and got stuck in boot loop. Couldnt use the old RUU since I had updated.
Anyway, I have it, but not sure how to host a file that big...any suggestions
EDIT:
I am uploading it to my Dropbox account in the public folder. I guess it will create a download link. It still has 2hours left of upload. My upload speed is pretty crap where I live.
Dropbox
Mr Hofs said:
Dropbox
Click to expand...
Click to collapse
Hi can you please help me. I want to go back to stock, and I have lost all my back up and I cant install nandroid backup for my carrier version using cwm. Do I need to use RUU? The software version I need is 2.17.771.3. Thanks.
shaazzaarr said:
Hi can you please help me. I want to go back to stock, and I have lost all my back up and I cant install nandroid backup for my carrier version using cwm. Do I need to use RUU? The software version I need is 2.17.771.3. Thanks.
Click to expand...
Click to collapse
Here you can download a new nandroid backup. Check your cid too, but they are there thumbup:
Here is the link. Its worth a try.:good:
http://www.roomyshare.com/ruu-endea...dio-2-1204-135-20h-release-277220-signed.html
I forgot the link to the nandroid backups
http://forum.xda-developers.com/showthread.php?t=1975140
.
And the ruu's are back online grab yours here
http://androidfiles.org/ruu/securek...adio_2.1204.135.20H_release_277220_signed.exe
Mr Hofs said:
I forgot the link to the nandroid backups
http://forum.xda-developers.com/showthread.php?t=1975140
.
And the ruu's are back online grab yours here
http://androidfiles.org/ruu/securek...adio_2.1204.135.20H_release_277220_signed.exe
Click to expand...
Click to collapse
Ok guys ive not posted much as ive had no need to... im fairly competant when it comes to messing with my phone but im baffled now.... Ive rooted desire hd, sensation xl and a few other phones so im not a complete noob i wouldnt say... although you lot may haha
OK, so ive tried to go stock from all of the different nandroid back ups that correspond with my device (because my hard drive crashed and killed all my data,) on this site to no avail. Every single one no matter how i do it, or in what manner, give me the same issue, an md5 checksum mismatch error. Doesn't matter what its called or where its unzipped too, i get the exact same thing every time. Also since starting this process abd no longer works.... The laptop sees the phone and if i try to use fastboot or any of the fastboot commands they work fine. If i do adb devices it shows nothing in the list. I can fastboot boot boot.img and then clear the cash but i just cannot get it to restore the back up at all so i can then flash the recovery after and get it running again.
Im currently in the process of downloading what i believe is the RUU for this phone so we will see if this works.
I need to reset back to factory because i want to sell the phone as a stock unrooted phone to a family member who will want to be able to do ota updates etc. And if it ever breaks or needs sending back it needs to be stock. so........ i was wondering if anyone on here could help me in any way to get my current brick back to a working stock HOX.
CID is H3G_001
version is 2.17.771.3
currently on the lastest CWM
on my fastboot screen ive got
*** UNLOCKED ***
ENDEAVORU PVT SHIP S-ON RL
HBOOT-1.12.0000
CPLD-None
MI CROP-None
RADIO-2.1204.135.20H
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW Secure boot: enabled
MODEM PATH : OFF
Jun 28 2012,11:31:28
Now is it possible usb debugging may have been turned off thus stopping the adb commands? I cannot get past the boot loop so i am unable to check...
All im trying to do is get back to the stock phone. If anyone is able to help me do that i would gladly show my appreciation....
Kind Regards
Brett (Nibbzy)
You are getting serviced here
http://forum.xda-developers.com/showthread.php?t=2205196
:thumbup:
Mr Hofs said:
You are getting serviced here
http://forum.xda-developers.com/showthread.php?t=2205196
:thumbup:
Click to expand...
Click to collapse
ooooh yeah getting serviced... hahahah thanks mate... :good: i double posted it hoping the usefull eyes on here could help me and it appears that it worked a treat!!!
now to figure out rooting the one x + hahaha :laugh:
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.
The title basically says it all but I'll describe what I did so hopefully you guys can help.
Today I got tired of the ROM I was running and I figured I'd update my firmware before I flashed a new one just cause I hadn't done it in months. So I went and followed this guide: http://forum.xda-developers.com/showthread.php?t=2696282
I used this firmware: https://www.androidfilehost.com/?w=files&flid=32788
My CID is T-MOB010 just like the firmware's and I thought it would be a pretty simple thing, so I got to work.
First I rebooted to fastboot USB and did fastboot getvar all to make sure everything lined up, then I relocked the bootloader and did fastboot oem rebootRUU, all successfully.
Then I flashed the firmware and it all went great but I forgot to flash it a second time. I'm not sure if it's required, but anyway...
After it flashed successfully I did a fastboot reboot and my phone tried to reboot but it stalled on the white HTC splash screen, then went black, then the splash screen returned, then black, then it went into the stock recovery.
The stock recovery functions just fine and I attempted to just clear the cache and reboot but it did the exact same thing.
I don't currently have a stock Nandroid or RUU on my phone and I'm not even sure I have a way to get one on there besides using someone else's phone to put one on my SD.
Can anyone help me out? Is it even possible to get out of this? My bootloader is relocked and my phone can't get S-OFF (tried awhile ago multiple times). As of now I am all out of ideas/experience so I'm hoping you guys can help me. Thank you!!
UPDATE: I got myself into the HBOOT so I think I should be good now but I'll keep this around just in case.
Update: Once I got into hboot all was well, I just flashed TWRP again and got it going. Thanks everyone for the help!
Did you get it going again?
_jakeryan said:
I don't currently have a stock Nandroid or RUU on my phone
Click to expand...
Click to collapse
Just use the official RUU.exe which runs from a PC (with phone connected), not from the phone.
http://www.htc.com/us/support/htc-one-m8-t-mobile/news/
RUU will also update your firmware.
Also, the firmware you linked is not the latest. Its the Android 4.4.4 firmware. The 5.0 (Lollipop) firmware would be 4.20.531.4
hack14u said:
Did you get it going again?
Click to expand...
Click to collapse
I did! Thank you redpoint for the help anyway!
_jakeryan said:
I did! Thank you redpoint for the help anyway!
Click to expand...
Click to collapse
Maybe add 'solved' to the topic? If that's still a thing.
_jakeryan said:
I did! Thank you redpoint for the help anyway!
Click to expand...
Click to collapse
Its not what your top post says, so its not clear whether you were trying to put the RUU.exe on the phone (which is incorrect), unsuccessful in putting on the phone or running an RUU.zip, or did the latter in addition to trying to run the RUU.exe from the PC (which was not originally mentioned). If the last one didn't work, it would help to have more details on failure mode, error messages, etc.
---------- Post added at 09:25 AM ---------- Previous post was at 09:23 AM ----------
_jakeryan said:
UPDATE: I got myself into the HBOOT so I think I should be good now but I'll keep this around just in case.
Click to expand...
Click to collapse
So is your issue resolve or not? Able to get a ROM or nandroid on the phone and flash/restore it?
---------- Post added at 09:26 AM ---------- Previous post was at 09:25 AM ----------
voidzero said:
Maybe add 'solved' to the topic? If that's still a thing.
Click to expand...
Click to collapse
Not everyone does it, but its certainly good to do, and still done from time to time. Its helpful so folks don't click on a link, intending to help someone that doesn't need the help anymore.
Same kinda problem.
I'm stuck in bootloader.
Any key I just brings me back to this again.
Even in HBOOT selecting Recovery or Factory reset does nothing other than bring up this screen.
Powering down and then on again has the same result.
I was trying to get back to stock. Typed in fastboot oem lock and after that... the problem started!!
Any ideas??
morgansgrandad said:
I'm stuck in bootloader.
Any key I just brings me back to this again.
Even in HBOOT selecting Recovery or Factory reset does nothing other than bring up this screen.
Powering down and then on again has the same result.
I was trying to get back to stock. Typed in fastboot oem lock and after that... the problem started!!
Any ideas??
Click to expand...
Click to collapse
This is intentional. When you relock the bootloader, it renders the phone unbootable and expects the RUU to be run.
redpoint73 said:
This is intentional. When you relock the bootloader, it renders the phone unbootable and expects the RUU to be run.
Click to expand...
Click to collapse
Ok. I'd downloaded what I assume is the correct RUU.exe. Ran it from the computer and I get a 131 error. Not the correct RUU !!
Stuck for a solution now!!
morgansgrandad said:
Ok. I'd downloaded what I assume is the correct RUU.exe. Ran it from the computer and I get a 131 error. Not the correct RUU !!
Stuck for a solution now!!
Click to expand...
Click to collapse
You shouldn't be assuming what RUU to run. What is your CID and hboot number? What RUU did you try to run?
HBOOT is 3.19.0.0000 CID, can't find.
RUU is M8_4.16.401.10_Europe.exe
morgansgrandad said:
HBOOT is 3.19.0.0000 CID, can't find.
RUU is M8_4.16.401.10_Europe.exe
Click to expand...
Click to collapse
The OS number (3.32.206.9) shown on your hboot screen (pic in your top post) indicates that is not the right RUU. The number in the x.xx.206.x is carrier specific,and seems to indicate that your phone is the O2 UK version. Running an RUU with version x.xx.401.x won't work. The number in the "401" spot would need to "206" for it to be the right RUU.
Not sure, but I don't think your CID has RUUs. If that is the case, your best bet it to unlock the bootloader again, flash TWRP back to the phone, and restore a nandroid with your software number (3.32.206.9) if you can find it. Then flash stock recovery back to the phone. That is as close to "stock" as you will get, if there is no RUU for your CID version.
redpoint73 said:
The OS number (3.32.206.9) shown on your hboot screen (pic in your top post) indicates that is not the right RUU. The number in the x.xx.206.x is carrier specific,and seems to indicate that your phone is the O2 UK version. Running an RUU with version x.xx.401.x won't work. The number in the "401" spot would need to "206" for it to be the right RUU.
Not sure, but I don't think your CID has RUUs. If that is the case, your best bet it to unlock the bootloader again, flash TWRP back to the phone, and restore a nandroid with your software number (3.32.206.9) if you can find it. Then flash stock recovery back to the phone. That is as close to "stock" as you will get, if there is no RUU for your CID version.
Click to expand...
Click to collapse
Thanks redpoint73. Looks like that's the only way to go!!
By looking at the radio, you need the Euro Version RUU. Looks like we gotta be detectives sometimes, lol.
Ok, I've unlocked the bootloader and am back to where it was.
It's running 5.0.1, Sense 6.0 and Android Revolution HD 34.6 by mike1986
I would like to clear that off and get back to stock with OTT updates.
Revolution HD 34.6 seems to use an awful lot of data. My other M8 has stock on-board, has identical apps etc and doesn't use nearly as much data as this one!!
Any further ideas??
morgansgrandad said:
Ok, I've unlocked the bootloader and am back to where it was.
It's running 5.0.1, Sense 6.0 and Android Revolution HD 34.6 by mike1986
I would like to clear that off and get back to stock with OTT updates.
Revolution HD 34.6 seems to use an awful lot of data. My other M8 has stock on-board, has identical apps etc and doesn't use nearly as much data as this one!!
Any further ideas??
Click to expand...
Click to collapse
Why not just set it up for Dev / Unlocked Edition?
http://www.htc.com/us/support/htc-one-m8/news/
hack14u said:
Why not just set it up for Dev / Unlocked Edition?
http://www.htc.com/us/support/htc-one-m8/news/
Click to expand...
Click to collapse
I'm downloading that now. BUT...........
Because of all my faffing on!! there's NO OS on the phone.
I'm really struggling now:crying:
This is my position now. Totally unusable phone!!
I would appreciate ANY help on getting back to as near as normal as possible.
Thank you.
I should add, the RUU messages are from trying post #16.
And the saga continues!
I found a nandroid backup with the same s/w number as mine, downloaded it from MEGA (it seemed to d/l ok).
When I ran it through TWRP I got signature verification failed.
This phone could end up in the depths of the river Tyne
morgansgrandad said:
This is my position now. Totally unusable phone!!
I would appreciate ANY help on getting back to as near as normal as possible.
Thank you.
I should add, the RUU messages are from trying post #16.
Click to expand...
Click to collapse
What hack14u neglected to mention, is that to run another version's RUU, you need s-off ($25 by sunshine), and then you need to change your MID and CID.
Relocking the bootloader (to run RUU) renders the phone with no OS, this is by design.
---------- Post added at 09:41 AM ---------- Previous post was at 09:34 AM ----------
morgansgrandad said:
And the saga continues!
I found a nandroid backup with the same s/w number as mine, downloaded it from MEGA (it seemed to d/l ok).
When I ran it through TWRP I got signature verification failed.
This phone could end up in the depths of the river Tyne
Click to expand...
Click to collapse
Hang in there, modding phones can often be an exercise in frustration. But the phone is quite recoverable, as long as you perform the correct steps.
A nandroid is not a flashable zip (such as a ROM). It needs to be restored in a very different way, its described in Post 3 of the stock nandroid thread (assuming that is where you go it from) under Question & Answers.
To summarize, you need to:
1) Unpack the zipk, which is a number of folders
2) Move the folders to the proper location on the phone's internal storage (removable SD is also possible, if you setup TWRP to back and restore to that location)
The exact location if very important (its described in Post 3 of the stock nandroid thread), since when restoring a nandroid, TWRP will not see the file to restore if you have it wrong. This is in direct contrast to installing a ROM zip, in which TWRP allows you to browse anywhere on the storage to find the file to flash.
3) Choose the menu option to RESTORE, not INSTALL
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!