[Q] I have a problem. - One (M8) Q&A, Help & Troubleshooting

So I have a problem. I rooted and unlocked my bootloader just fine on my T-Mobile HTC One M8. While installing insert coin to prep for s-off, I was wiping my data and accidentally deleted my operating system (oops). So I followed a tutorial and tried using firewater and I got the "whelp, no amount of retrying will make this work on your device" message. I want to use Sunshine now, but I can't because sunshine only works with stock sense, which I accidentally deleted. I have looked and looked online and the only presumable way of getting the operating system back is through an RUU which I can't do because I'm not S-Off. I can't get S-Off because I don't have sense, and I can't get sense because I'm not S-Off. Is there just a regular ROM I could use to flash sense just temporarily while I get sunshine? My whole goal of this was to make my regular M8 a google play edition, as I prefer stock android.

TrentCowden said:
So I have a problem. I rooted and unlocked my bootloader just fine on my T-Mobile HTC One M8. While installing insert coin to prep for s-off, I was wiping my data and accidentally deleted my operating system (oops). So I followed a tutorial and tried using firewater and I got the "whelp, no amount of retrying will make this work on your device" message. I want to use Sunshine now, but I can't because sunshine only works with stock sense, which I accidentally deleted. I have looked and looked online and the only presumable way of getting the operating system back is through an RUU which I can't do because I'm not S-Off. I can't get S-Off because I don't have sense, and I can't get sense because I'm not S-Off. Is there just a regular ROM I could use to flash sense just temporarily while I get sunshine? My whole goal of this was to make my regular M8 a google play edition, as I prefer stock android.
Click to expand...
Click to collapse
Who says you need to be S-OFF to run a RUU If there is an RUU available for your device then run it. Just make sure you lock the bootloader before you do.
You could also just flash a ROM(any rom) onto your device or restore a backup from the collection of stock backups thread(In general section).

BerndM14 said:
Who says you need to be S-OFF to run a RUU If there is an RUU available for your device then run it. Just make sure you lock the bootloader before you do.
Click to expand...
Click to collapse
How do I relock the bootloader and why do I have to do that? (just curious)
You could also just flash a ROM(any rom) onto your device or restore a backup from the collection of stock backups thread(In general section).
Click to expand...
Click to collapse
Also I tried downloading a stock sense rom and when I flashed it, my phone turned on and the message "unfortunately, phone has stopped" just kept coming up over and over. Do I need to find a Rom specific to T-mobile and/or my device version?
Thank you so much for your quick response and help!

TrentCowden said:
How do I relock the bootloader and why do I have to do that? (just curious)
Also I tried downloading a stock sense rom and when I flashed it, my phone turned on and the message "unfortunately, phone has stopped" just kept coming up over and over. Do I need to find a Rom specific to T-mobile and/or my device version?
Thank you so much for your quick response and help!
Click to expand...
Click to collapse
To lock bootloader, shut down device. Hold Power button + Volume down to boot into bootloader. Connect Phone to PC. Open command prompt in adb folder. Type
Code:
fastboot devices
To check if the device gets picked up, Next type:
Code:
fastboot oem lock
This will lock bootloader. Then you can run the RUU.exe as administrator on your PC and begin restoring your device back to stock.
Why do you need to lock it? I'm not entirely sure Perhaps it's just part of the verification the RUU needs in order to make changes to the device, kinda like you need to be stock to do OTA. Maybe it just has something to do with the oem method of recovering/restoring the device, I don't know mate, sorry.
Perhaps someone with a bit more expertise can answer that one for you, I only know that it needs to be locked if you're S-ON.

BerndM14 said:
To lock bootloader, shut down device. Hold Power button + Volume down to boot into bootloader. Connect Phone to PC. Open command prompt in adb folder. Type
Code:
fastboot devices
To check if the device gets picked up, Next type:
Code:
fastboot oem lock
This will lock bootloader. Then you can run the RUU.exe as administrator on your PC and begin restoring your device back to stock.
Why do you need to lock it? I'm not entirely sure Perhaps it's just part of the verification the RUU needs in order to make changes to the device, kinda like you need to be stock to do OTA. Maybe it just has something to do with the oem method of recovering/restoring the device, I don't know mate, sorry.
Perhaps someone with a bit more expertise can answer that one for you, I only know that it needs to be locked if you're S-ON.
Click to expand...
Click to collapse
Sweet! Could I just skip going back to stock sense and just go straight to the google play edition ruu?

TrentCowden said:
Sweet! Could I just skip going back to stock sense and just go straight to the google play edition ruu?
Click to expand...
Click to collapse
You'll need to be S-OFF in order to convert to the GPE as it makes changes to the partition sizes on the device. If I recall correctly it was Graffixnyc that made a thread about that and I'm almost sure he mentioned in that very thread that you need to be S-OFF.
First restore your phone to working condition, then get S-OFF then you can follow the guide to convert your device to GPE.
---------- Post added at 11:43 PM ---------- Previous post was at 11:39 PM ----------
[RUU] M8 Google Edition Conversion. 4.4.4 - RUU Zip Non-Rooted & Pre-Rooted
Yep there's the thread I was talking about. You can see he clearly states there:
Prerequisites
S-Off,
ADB knowledge
Fastboot knowledge

BerndM14 said:
You'll need to be S-OFF in order to convert to the GPE as it makes changes to the partition sizes on the device. If I recall correctly it was Graffixnyc that made a thread about that and I'm almost sure he mentioned in that very thread that you need to be S-OFF.
First restore your phone to working condition, then get S-OFF then you can follow the guide to convert your device to GPE.
---------- Post added at 11:43 PM ---------- Previous post was at 11:39 PM ----------
[RUU] M8 Google Edition Conversion. 4.4.4 - RUU Zip Non-Rooted & Pre-Rooted
Yep there's the thread I was talking about. You can see he clearly states there:
Prerequisites
S-Off,
ADB knowledge
Fastboot knowledge
Click to expand...
Click to collapse
OK. So I re-locked my phone. I'm downloading the RUU now from the official HTC website. Once it's done, then what?

TrentCowden said:
OK. So I re-locked my phone. I'm downloading the RUU now from the official HTC website. Once it's done, then what?
Click to expand...
Click to collapse
Just make sure you download the correct version that corresponds to the version your device is.
If you need earlier or other version it's in here: [Recovery] [RUU 2.22.531.5] [TWRP Nandroid Backups] [Radio IMGs][ OTA 2.22.531.6]
Once that is done you can just right click on the exe file, select run as administrator and follow the onscreen wizard to restore the device back to stock.
---------- Post added 17th September 2014 at 12:00 AM ---------- Previous post was 16th September 2014 at 11:55 PM ----------
TrentCowden said:
OK. So I re-locked my phone. I'm downloading the RUU now from the official HTC website. Once it's done, then what?
Click to expand...
Click to collapse
A quick Google search dropped this guide on restoring, might be worth a look if you're interested.
How to Restore T-Mobile HTC One M8 to Stock with RUU

BerndM14 said:
Just make sure you download the correct version that corresponds to the version your device is.
If you need earlier or other version it's in here: [Recovery] [RUU 2.22.531.5] [TWRP Nandroid Backups] [Radio IMGs][ OTA 2.22.531.6]
Once that is done you can just right click on the exe file, select run as administrator and follow the onscreen wizard to restore the device back to stock.
---------- Post added 17th September 2014 at 12:00 AM ---------- Previous post was 16th September 2014 at 11:55 PM ----------
A quick Google search dropped this guide on restoring, might be worth a look if you're interested.
How to Restore T-Mobile HTC One M8 to Stock with RUU
Click to expand...
Click to collapse
Hey there!
So I restored my phone and it worked, so I s-offed my phone using Sunshine (because like I said before firewater didn't work for me), and I downloaded the GPE RUU but for some reason when I type adb reboot bootloader into cmd it says error:device not found. When I plug my phone in, it makes the noise that signals that a device has been plugged in, but it doesn't show it in the file explorer. Any ideas?

TrentCowden said:
Hey there!
So I restored my phone and it worked, so I s-offed my phone using Sunshine (because like I said before firewater didn't work for me), and I downloaded the GPE RUU but for some reason when I type adb reboot bootloader into cmd it says error:device not found. When I plug my phone in, it makes the noise that signals that a device has been plugged in, but it doesn't show it in the file explorer. Any ideas?
Click to expand...
Click to collapse
Nevermind, realized I didn't have USB Debugging on.

Related

Big problem about S-off

Hello
I have bootloader unlocked, rooted HTC one M8. I want to use android revolution hd and to do that I need to flash a new firmware. I need to do "s-off". However I tried I failed that with "runrummer". I get this fail : (I dont wanna pay 25$ for sunshine)
Pouring (1) ......................
Pouring (2)
WTF: what are you doing.
Press Enter to exit.
I want to do s-off so badly and I can give more info. about the phone.
Thanks a lot
Runrunner doesn't work with the M8. Sunshine is the only working method
EddyOS said:
Runrunner doesn't work with the M8. Sunshine is the only working method
Click to expand...
Click to collapse
So you say There is no other way execpt sunshine ?
tugratolunay said:
So you say There is no other way execpt sunshine ?
Click to expand...
Click to collapse
Yep man. I use s-on for its ok all good
leos0000 said:
Yep man. I use s-on for its ok all good
Click to expand...
Click to collapse
That's nice, but you need to be S-Off to do certain things, like manually flashing firmware without reverting to stock, or using firmware meant for carriers other than yours when they update before your carrier.
There are other advantages as well, but these are the ones that S-Off is most used for.
tugratolunay said:
So you say there is no other way except Sunshine ?
Click to expand...
Click to collapse
That's exactly what I'm saying
tugratolunay said:
WTF: what are you doing.
Click to expand...
Click to collapse
"WTF what are you doing" indeed. Rumrunner never worked for this phone. It was for the M7. Firewater (related, but different from rumrunner) was for earlier M8 versions. It was an online service, and will no longer work now that the dev has stopped supporting it (so don't even bother asking).
For many variants, s-off is not needed to update firmware (as long as Lollipop has been released for your variant). You can just return to stock ROM and stock recovery, and OTA to Lollipop in order to update your firmware.
redpoint73 said:
"WTF what are you doing" indeed. Rumrunner never worked for this phone. It was for the M7. Firewater (related, but different from rumrunner) was for earlier M8 versions. It was an online service, and will no longer work now that the dev has stopped supporting it (so don't even bother asking).
For many variants, s-off is not needed to update firmware (as long as Lollipop has been released for your variant). You can just return to stock ROM and stock recovery, and OTA to Lollipop in order to update your firmware.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2694994
I have used this rom (Stock ROM's (Android 4.4.4 + HTC Sense 6.0 | Latest: 3.28.401.9) and I still cant use wifi or I cant restart the phone it stucks at HTC logo. Could you please help me about finding correct stock rom ? or is there only 1 stock rom I really dont know what to do so far or how do I return back..
tugratolunay said:
http://forum.xda-developers.com/showthread.php?t=2694994
I have used this rom (Stock ROM's (Android 4.4.4 + HTC Sense 6.0 | Latest: 3.28.401.9) and I still cant use wifi or I cant restart the phone it stucks at HTC logo. Could you please help me about finding correct stock rom ? or is there only 1 stock rom I really dont know what to do so far or how do I return back..
Click to expand...
Click to collapse
There are different stock ROMs for different CIDs. Plus, if you have no WiFi, and extreme long boot times, its due to your firmware not being supported by the ROM. You need to find the stock ROM for your current firmware and CID. Then you also need to flash the corresponding stock recovery. After that, you can OTA to the latest firmware.
What is your CID, hboot number, and radio number?
redpoint73 said:
There are different stock ROMs for different CIDs. Plus, if you have no WiFi, and extreme long boot times, its due to your firmware not being supported by the ROM. You need to find the stock ROM for your current firmware and CID. Then you also need to flash the corresponding stock recovery. After that, you can OTA to the latest firmware.
What is your CID, hboot number, and radio number?
Click to expand...
Click to collapse
HBoot 3.16.0.0000
Radio-1.16.21331931.LA11G
Cid : CWS_001
by the way I bought this phone when I was in USA and I bought it from AT&T I dont know if it makes difference. I have a custom rom (4.4.2) its the only rom that I can use the phone and this rom is sux :'(
tugratolunay said:
HBoot 3.16.0.0000
Radio-1.16.21331931.LA11G
Cid : CWS_001
by the way I bought this phone when I was in USA and I bought it from AT&T I dont know if it makes difference.
Click to expand...
Click to collapse
Not only is that make a difference, it makes it easy to update your firmware. Just relock the bootloader and run the new Lollipop RUU: http://dl3.htc.com/application/RUU_M8[email protected]50319A_40.45.C33065.00_F_release_426617_signed_2.exe
Backup any important personal data before RUU, as RUU will wipe the phone.
redpoint73 said:
Not only is that make a difference, it makes it easy to update your firmware. Just relock the bootloader and run the new Lollipop RUU: http://dl3.htc.com/application/RUU_M8[email protected]50319A_40.45.C33065.00_F_release_426617_signed_2.exe
Backup any important personal data before RUU, as RUU will wipe the phone.
Click to expand...
Click to collapse
Would you mind I want you to explain the process how to do it or can you please give me link to follow the process?
tugratolunay said:
Would you mind I want you to explain the process how to do it or can you please give me link to follow the process?
Click to expand...
Click to collapse
1) To lock bootloader: Connect phone to PC (PC required for RUU). Boot phone into bootloader-fastboot mode. Open command prompt on computer, and type command: fastboot oem lock
2) Download RUU onto PC. With phone connected, run the RUU exectuble program on the PC and follow the instructions given.
3) Done, drink beer
A little more detail is given here under "Manual system update instructions": http://www.htc.com/us/support/htc-one-m8-att/news/
But seriously, the RUU is a self-explanatory program. It will tell you to confirm a couple dialogue boxes. But aside from that, the program will install a completely clean factory Lollipop software image.
Option Step) Unlock the bootloader again via HTCDev.com, then flash TWRP if you want to root or flash a custom ROM.
redpoint73 said:
1) To lock bootloader: Connect phone to PC (PC required for RUU). Boot phone into bootloader-fastboot mode. Open command prompt on computer, and type command: fastboot oem lock
2) Download RUU onto PC. With phone connected, run the RUU exectuble program on the PC and follow the instructions given.
3) Done, drink beer
A little more detail is given here under "Manual system update instructions": http://www.htc.com/us/support/htc-one-m8-att/news/
But seriously, the RUU is a self-explanatory program. It will tell you to confirm a couple dialogue boxes. But aside from that, the program will install a completely clean factory Lollipop software image.
Option Step) Unlock the bootloader again via HTCDev.com, then flash TWRP if you want to root or flash a custom ROM.
Click to expand...
Click to collapse
Cant I use the same unlock_code.bin ? and Will the at&t app be back? and will my SD card will be safe? Should I be in fastboot while doing RUU? or just homescreen?
Sorry for bothering you too much :/
***Tampered***
***relocked***
***security Warning**
M8_ul_ca
.
.
.
I cant open my phone, it always comes at this screen (bootloader). Is that normal?
tugratolunay said:
Cant I use the same unlock_code.bin ?
Click to expand...
Click to collapse
You can try it. It certainly doesn't hurts, as it only takes a single fastboot command, and would be faster than going through the whole HTCDev.com process (although that really doesn't take that much time, either).
I know using the same token has worked on past HTC devices. But I haven't seen much (if any) success on the M8. Most (or all?) folks have had to get a new token in order to unlock.
tugratolunay said:
Will the at&t app be back?
Click to expand...
Click to collapse
Yes, whatever AT&T apps are present on the stock Lollipop AT&T image will be on your phone. Simply root and delete/freeze, or install a custom ROM to be rid of the AT&T bloat.
tugratolunay said:
will my SD card will be safe?
Click to expand...
Click to collapse
You mean the removable SD? It should be safe. But you can always take it out before RUU to be sure it doesn't get touched by RUU.
Any other data on the phone (including the "virtual SD" AKA internal storage) should be backed up, if you want to keep it. Internal storage "might" be okay, but I'd back up anything you want to keep, just in case.
tugratolunay said:
Should I be in fastboot while doing RUU? or just homescreen?
Click to expand...
Click to collapse
Usually booted into OS works. But some folks have had to put the phone in fastboot mode.
---------- Post added at 04:39 PM ---------- Previous post was at 04:37 PM ----------
tugratolunay said:
Sorry for bothering you too much :/
Click to expand...
Click to collapse
Its no bother. I enjoy helping others.
I only ask in return you click the "Thanks" button for any posts you found helpful.
---------- Post added at 04:41 PM ---------- Previous post was at 04:39 PM ----------
tugratolunay said:
***Tampered***
***relocked***
***security Warning**
M8_ul_ca
.
.
.
I cant open my phone, it always comes at this screen (bootloader). Is that normal?
Click to expand...
Click to collapse
Yes, that is normal. Its expected that RUU will be run once you relock, so it makes the phone this way.
I always forget this, since I s-off my devices (no relocking necessary to RUU with s-off)
redpoint73 said:
I always forget this, since I s-off my devices (no relocking necessary to RUU with s-off)
Click to expand...
Click to collapse
After installing this RUU I will have original At&t rom and unroot, relocked bootloader phone. and it will be 5.0.1 lollipop. Am I right? and so firmware will be upgraded tho? That means I can Unlock it, root it and install that android revolution HD rom without having problems.
tugratolunay said:
After installing this RUU I will have original At&t rom and unroot, relocked bootloader phone. and it will be 5.0.1 lollipop. Am I right? and so firmware will be upgraded tho? That means I can Unlock it, root it and install that android revolution HD rom without having problems.
Click to expand...
Click to collapse
Yes, yes, and yes.
The only thing above that isn't completely correct, if that after you unlock the bootloader again, just install custom recovery and flash ARHD. No need to root before flashing a custom ROM. Installing a ROM wipes whatever you did with root anyway, and custom ROMs are always pre-rooted. So rooting manually is an unnecessary step. You only need to root "manually" if you are keeping the stock ROM.

[SOLVED] T-Mobile M8 Stuck In Recovery With ReLocked Bootloader and No ROM!

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

HTC M8 from Three UK stuck

Hello everyone.
I have an M8 with a corrupted software.
Always stuck on HTC logo.
Sometimes when it boots, it shows "3" , which means it's from Three UK.
I looked everywhere but couldn't find the corresponding RUU, except on http://www.htcdev.com/devcenter/downloads , but it's only around 500 MB !
It's in zip format.
I can go to the bootloader, but it doesn't accept to FACTORY-RESET (gets stuck on HTC screen)
Software status: Official
RELOCKED
Any ideas?
Thanks in advance.
I unlocked the bootloader in order to try to install another RUU.
Now it shows "UNLOCKED" .
I installed twrp and superuser (I guess).
According to the thread here http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
I have to install the sunshine.apk which I can not because my phone doesn't boot except to the bootloader !
What to do here?
majdykhrais said:
I looked everywhere but couldn't find the corresponding RUU, except on http://www.htcdev.com/devcenter/downloads , but it's only around 500 MB !
It's in zip format.
Click to expand...
Click to collapse
That isn't an RUU, its kernel source, and not going to be of any help to you.
---------- Post added at 09:41 AM ---------- Previous post was at 09:39 AM ----------
majdykhrais said:
I unlocked the bootloader in order to try to install another RUU.
Now it shows "UNLOCKED" .
Click to expand...
Click to collapse
Unlocking the bootloader will not allow you to run another version's RUU. I don't know why you think that, but its not correct information.
---------- Post added at 09:45 AM ---------- Previous post was at 09:41 AM ----------
majdykhrais said:
I installed twrp and superuser (I guess).
According to the thread here http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
I have to install the sunshine.apk which I can not because my phone doesn't boot except to the bootloader !
What to do here?
Click to expand...
Click to collapse
S-off is not the correct path, to do what you want (nor should it be necessary - save yourself $25). As you've figured out, you need a working OS to s-off; but working OS is the reason you want to s-off. So you have a Catch-22 dead end.
If there is no RUU, unlocked bootloader and TWRP are good things to have done. Now restore the 6.13.771.4 stock nandroid backup, using the file and instruction here: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Thanks
redpoint73 said:
That isn't an RUU, its kernel source, and not going to be of any help to you.
---------- Post added at 09:41 AM ---------- Previous post was at 09:39 AM ----------
Unlocking the bootloader will not allow you to run another version's RUU. I don't know why you think that, but its not correct information.
---------- Post added at 09:45 AM ---------- Previous post was at 09:41 AM ----------
S-off is not the correct path, to do what you want (nor should it be necessary - save yourself $25). As you've figured out, you need a working OS to s-off; but working OS is the reason you want to s-off. So you have a Catch-22 dead end.
If there is no RUU, unlocked bootloader and TWRP are good things to have done. Now restore the 6.13.771.4 stock nandroid backup, using the file and instruction here: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Click to expand...
Click to collapse
Thanks for the info.
I know TWRP and S-OFF won't help me here, but I just wanted to show what I've done.
One question, why to restore 6.13.771.4?
How will I know it's the correct one for my phone, and not a part of the pre-installed corruption?
majdykhrais said:
One question, why to restore 6.13.771.4?
How will I know it's the correct one for my phone, and not a part of the pre-installed corruption?
Click to expand...
Click to collapse
This is the main version given in your screenshot in your top post. And you'll see from the stock nandroid collection, that its the correct version number for your CID (carrier version).
Simply put, this is the stock Marshmallow ROM for your M8 version.
Somebody likely made the backup with a working OS. Yours has become damaged or corrupt (most likely) just on your phone. Not every phone with this software number is going to be broken!
didn't work!
redpoint73 said:
This is the main version given in your screenshot in your top post. And you'll see from the stock nandroid collection, that its the correct version number for your CID (carrier version).
Simply put, this is the stock Marshmallow ROM for your M8 version.
Somebody likely made the backup with a working OS. Yours has become damaged or corrupt (most likely) just on your phone. Not every phone with this software number is going to be broken!
Click to expand...
Click to collapse
excellent turorial.
I followed the steps one by one,
didn't get any errors,
but it didn't work.
I got the HTC screen, then "3" screen, then stuck on HTC One screen!
Any ideas?
majdykhrais said:
excellent turorial.
I followed the steps one by one,
didn't get any errors,
but it didn't work.
I got the HTC screen, then "3" screen, then stuck on HTC One screen!
Any ideas?
Click to expand...
Click to collapse
a strange thing I noticed,,
on command prompt on my pc, I can't see the new folder containing the unzipped file, while I can see it through the windows-explorer!
majdykhrais said:
a strange thing I noticed,,
on command prompt on my pc, I can't see the new folder containing the unzipped file, while I can see it through the windows-explorer!
Click to expand...
Click to collapse
Any particular reason why you are looking in command prompt? Since the steps don't use command prompt (unless you adb push the files).
What version TWRP?
Can you post a screenshot of what the TWRP backup folder structure (on the phone) looks like in Windows Explorer? Not sure what we can be missing here. But its worth a look.
Also, you might try the a Lollipop backup. It should work fine with the MM firmware. Although it may cause an issue with OTA updates (mixing LP ROM with MM firmware), at least it (should) get the phone up and running.
twrp backup
redpoint73 said:
Any particular reason why you are looking in command prompt? Since the steps don't use command prompt (unless you adb push the files).
What version TWRP?
Can you post a screenshot of what the TWRP backup folder structure (on the phone) looks like in Windows Explorer? Not sure what we can be missing here. But its worth a look.
Also, you might try the a Lollipop backup. It should work fine with the MM firmware. Although it may cause an issue with OTA updates (mixing LP ROM with MM firmware), at least it (should) get the phone up and running.
Click to expand...
Click to collapse
no reason for command prompt, but I just was there and noticed this.
TWRP 2.8.7.0-m8 according to the turorial.
I want to try Lollipop since it was the o.s. when my phone was working properly before I upgrade to 6 and get the wifi problem.
any specific Lollipop version?
I just want a stable version.
thanks
twrp
majdykhrais said:
no reason for command prompt, but I just was there and noticed this.
TWRP 2.8.5.0-m8 according to the turorial.
I want to try Lollipop since it was the o.s. when my phone was working properly before I upgrade to 6 and get the wifi problem.
any specific Lollipop version?
I just want a stable version.
thanks
Click to expand...
Click to collapse
here's a screen shot
the path on my laptop was the same.
sorry,
I used twrp-2.8.7.0-m8
I'm confused about what you are talking about anymore. Did you sell the phone or not?
http://forum.xda-developers.com/showpost.php?p=66116673&postcount=1498
If this is a different phone, you need to give details.
Fastboot getvar all

Help with installing AT&T Ruu

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

HTC ONE M8 security warning in FASTBOOT mode

Hi every one I have htc one m8 now 2-3 years, I rooted and unlocked bootloader, on stock firmware which is : 4.18.708.12 and now I have system updates that I cant update cuz im rooted , so I relocked bootloader and tried to update , still when i try it goes to fastboot with this : system software modified, security warning and it doesnt update nor perform a factory reset, can some one help me out here? id be glad I need this help asap
You need stock ROM, and stock recovery to update by OTA.
Return to stock ROM and stock recovery using this thread (which will then allow you to update): http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Relocking the bootloader isn't necessary to OTA (only to RUU or flash signed firmware.zip) and didn't help you matters. You'll need to unlock it again in order to perform the process linked above.
Factory reset also won't help your condition, so there isn't a point in doing so. Factory reset is a bit of a misnomer, all it does is wipe user data. It won't restore a previous OS, nor remove root, etc.
redpoint73 said:
You need stock ROM, and stock recovery to update by OTA.
Return to stock ROM and stock recovery using this thread (which will then allow you to update): http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Relocking the bootloader isn't necessary to OTA (only to RUU or flash signed firmware.zip) and didn't help you matters. You'll need to unlock it again in order to perform the process linked above.
Factory reset also won't help your condition, so there isn't a point in doing so. Factory reset is a bit of a misnomer, all it does is wipe user data. It won't restore a previous OS, nor remove root, etc.
Click to expand...
Click to collapse
I want my phone to be back to stock like it came from the company, with the original ruu and firmware signatures, if i install stock rom and stock recovery that way im still rooted in which case I dont want it, I wanna get back to original LB and Unrooted with warrenty back
madshark2009 said:
I want my phone to be back to stock like it came from the company, with the original ruu and firmware signatures, if i install stock rom and stock recovery that way im still rooted in which case I dont want it, I wanna get back to original LB and Unrooted with warrenty back
Click to expand...
Click to collapse
If that is what you wanted, then no mention was made of that in your OP (which you should have done). You should be specific about what you want, and not make it harder for folks trying to help you.
You are incorrect (that after installing the stock ROM, you will still be rooted). Installing the stock ROM will remove root. That's the whole point of the thread I linked.
If there is an RUU for your version number, just use it to return to almost full stock. When I say "almost", its because the bootloader will only say RELOCKED instead of LOCKED. The only way to make it say LOCKED (after its been unlocked) is with s-off. And if you don't already have s-off, it will cost you $25 by sunshine. Probably not worth the cost, as you no longer have warranty, anyway. HTC warranty is only valid for 1 year.
redpoint73 said:
If that is what you wanted, then no mention was made of that in your OP (which you should have done). You should be specific about what you want, and not make it harder for folks trying to help you.
You are incorrect (that after installing the stock ROM, you will still be rooted). Installing the stock ROM will remove root. That's the whole point of the thread I linked.
If there is an RUU for your version number, just use it to return to almost full stock. When I say "almost", its because the bootloader will only say RELOCKED instead of LOCKED. The only way to make it say LOCKED (after its been unlocked) is with s-off. And if you don't already have s-off, it will cost you $25 by sunshine. Probably not worth the cost, as you most likely don't have a warranty, anyway. HTC warranty is only valid for 1 year.
Click to expand...
Click to collapse
and how do i decide which RUU is suitable for my device?
android 5.0.1
software number : 4.18.708.12
I must point out that I never installed a custom rom nor recovery I just unlocked bootloader and rooted and thats it so how do I find my ruu and what to do if i dont?
Its not actually clear what you are trying to do. Return to stock to update? Or something else? Your later post says return to stock for warranty, but no way you have warranty at this point. Is something wrong with the phone? Or just trying to return the phone to stock to sell or trade it?
Can't really provide proper guidance unless we know your intent.
---------- Post added at 12:13 PM ---------- Previous post was at 12:11 PM ----------
madshark2009 said:
and how do i decide which RUU is suitable for my device?
software number : 4.18.708.12
how do I find my ruu and what to do if i dont?
Click to expand...
Click to collapse
You look for an RUU for that version number you just posted.
If no RUU, the process I linked for you in the first place will return you to full stock, with the exception of bootloader will be UNLOCKED. Or you can make it RELOCKED. Not really much different from what an RUU would give you.
redpoint73 said:
Its not actually clear what you are trying to do. Return to stock to update? Or something else? Your later post says return to stock for warranty, but no way you have warranty at this point. Is something wrong with the phone? Or just trying to return the phone to stock to sell or trade it?
Can't really provide proper guidance unless we know your intent.
---------- Post added at 12:13 PM ---------- Previous post was at 12:11 PM ----------
You look for an RUU for that version number you just posted.
If no RUU, the process I linked for you in the first place will return you to full stock, with the exception of bootloader will be UNLOCKED. Or you can make it RELOCKED. Not really much different from what an RUU would give you.
Click to expand...
Click to collapse
I didnt mean to get my warrenty back, I meant to get back to stock just like when getting back to original phone status like it came from the company, so I understood that flashing stock rom and recovery will help me with geting back and stat updating normally, but the precess seems too complicated to understand I might need your further help perferably vie Direct message, but just to save all the efforts, Id perfer the RUU flashing, and since you said none original RUU that has the same number of my version , that means I can install any one I want? whats the difference between RUUs and how do I choose the perfect one
(sorry i am new thats why i ask a lot )
madshark2009 said:
I didnt mean to get my warrenty back
Click to expand...
Click to collapse
But its exactly what you posted:
madshark2009 said:
I wanna get back to original LB and Unrooted with warrenty back
Click to expand...
Click to collapse
I strongly suggest you take a bit more time thinking about what you post, and making sure its properly typed, (lack of proper capitalization, spelling and punctuation makes your posts a pain to read, to say the least) and conveys what you want it to. Otherwise, you're just making it harder for folks to understand and help you.
Any time you think you are saving by typing quickly, is being lost x10 by me having to ask you to clarify what you mean.
madshark2009 said:
so I understood that flashing stock rom and recovery will help me with geting back and stat updating normally, but the precess seems too complicated to understand
Click to expand...
Click to collapse
The process isn't complicated. If you managed to unlock the bootloader and root the phone, you can certainly accomplish restoring the stock ROM and stock recovery. On that same note, it can be fairly said that anyone that is unable restore the phone by that method; probably shouldn't have unlocked the bootloader and rooted to begin with. Or look at it a slightly different way: you should never root a device without knowing how to return it to stock.
The guide looks long, mostly because its written in a very highly detailed, step-by-step manner (some folks seem to like that). But it just boils down to downloading the proper file, unzipping the folders, putting them in the right location on the phone, and restoring in TWRP.
If you have issues on a particular step, feel free to post again here, or the TWRP stock backup thread we are discussing.
madshark2009 said:
Id perfer the RUU flashing, and since you said none original RUU that has the same number of my version , that means I can install any one I want? whats the difference between RUUs and how do I choose the perfect one
Click to expand...
Click to collapse
I never said there was no RUU for your version number; or did you determine that yourself (your wording isn't clear)? I don't definitely know if there is or not; I was leaving it up to you to search. But doing a quick search myseld, it looks like NO.
If you looked, and there is no RUU for your version, you certainly cannot run any RUU you like. In fact, you can't run any RUU at all, unless its intended for your version, CID, MID.
redpoint73 said:
You need stock ROM, and stock recovery to update by OTA.
Return to stock ROM and stock recovery using this thread (which will then allow you to update): http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Relocking the bootloader isn't necessary to OTA (only to RUU or flash signed firmware.zip) and didn't help you matters. You'll need to unlock it again in order to perform the process linked above.
Factory reset also won't help your condition, so there isn't a point in doing so. Factory reset is a bit of a misnomer, all it does is wipe user data. It won't restore a previous OS, nor remove root, etc.
Click to expand...
Click to collapse
I downloaded signed firmware that has the same CID and MID but marshmellow not lolipop (I had lolipop and flashed marshmallow firmware) and now phone is stuck at black screen
madshark2009 said:
I downloaded signed firmware that has the same CID and MID but marshmellow not lolipop (I had lolipop and flashed marshmallow firmware) and now phone is stuck at black screen
Click to expand...
Click to collapse
Why did you flash signed firmware? Its not a ROM, not an RUU. Nobody told you to do this.
Black screen, as in the screen doesn't come on? Not a good sign.
redpoint73 said:
Why did you flash signed firmware? Its not a ROM, not an RUU. Nobody told you to do this.
Black screen, as in the screen doesn't come on? Not a good sign.
Click to expand...
Click to collapse
yes thats what it means! what can i do now?
redpoint73 said:
Why did you flash signed firmware? Its not a ROM, not an RUU. Nobody told you to do this.
Black screen, as in the screen doesn't come on? Not a good sign.
Click to expand...
Click to collapse
i found my version number in TWRP backup 4.18.708.12_ckpv5 can i use this to flash through ADB? because I cant flash TWRP recovery after what i did it says error bootloader signatures veryfication.. what are my options man?
madshark2009 said:
yes thats what it means! what can i do now?
Click to expand...
Click to collapse
How did you flash the firmware? By fastboot, or SD card method?
What's the exact file name for what you flashed?
Any error messages?
Did it tell you to flash again (very common, but actually says "flush image immediately"), and if so, did you flash it again?
Try holding power button and vol up for a minute or more, and see if there is any change.
redpoint73 said:
How did you flash the firmware? By fastboot, or SD card method?
What's the exact file name for what you flashed?
Any error messages?
Did it tell you to flash again (very common, but actually says "flush image immediately"), and if so, did you flash it again?
Try holding power button and vol up for a minute or more, and see if there is any change.
Click to expand...
Click to collapse
flashed by fastboot the way its mentioned in the thread you sent me.. on how to flash marshmallow signed firmwares and now when I rebooted as instructed it gets stuck at black screen after HTC logo on white screen and so I thought I could fix this by flashing twrp but now it says bootloader signatures veryfication error, so I cant proceed to the installation ..
madshark2009 said:
i found my version number in TWRP backup 4.18.708.12_ckpv5 can i use this to flash through ADB? because I cant flash TWRP recovery after what i did it says error bootloader signatures veryfication.. what are my options man?
Click to expand...
Click to collapse
You have to get the phone back on, in one mode or another, before you can do anything.
No, you can't flash the stock TWRP backup with adb. Its a TWRP backup, and you have to restore it with TWRP.
You can't flash custom recovery with the bootloader locked. That is why you have signature verification error. You need to unlock the bootloader again, which I already told you. And you need to be in bootloader-fastboot mode to flash it, anyway. I thought you said the screen wasn't coming on?
redpoint73 said:
You have to get the phone back on, in one mode or another, before you can do anything.
No, you can't flash the stock TWRP backup with adb. Its a TWRP backup, and you have to restore it with TWRP.
You can't flash custom recovery with the bootloader locked. That is why you have signature verification error. You need to unlock the bootloader again, which I already told you. And you need to be in bootloader-fastboot mode to flash it, anyway. I thought you said the screen wasn't coming on?
Click to expand...
Click to collapse
yes it got a black screen.
to Unlock bootloader I need what exactly?
madshark2009 said:
flashed by fastboot the way its mentioned in the thread you sent me.. on how to flash marshmallow signed firmwares
Click to expand...
Click to collapse
I told you to restore a stock ROM and stock recovery from the thread (Post #1). I said nothing about flashing a signed firmware (Post #5) which is not part of returning to stock.
---------- Post added at 03:24 PM ---------- Previous post was at 03:23 PM ----------
madshark2009 said:
yes it got a black screen.
to Unlock bootloader I need what exactly?
Click to expand...
Click to collapse
You can't do anything with the phone off.
I asked you to try something in Post #13 above. Please read everything I post, and stop jumping around and trying random things. Read carefully, and proceed with caution and attention. Rushing around isn't going to help anything, and may do permanent damage to the phone (if you haven't already).
redpoint73 said:
I told you to restore a stock ROM and stock recovery from the thread (Post #1). I said nothing about flashing a signed firmware (Post #5) which is not part of returning to stock.
---------- Post added at 03:24 PM ---------- Previous post was at 03:23 PM ----------
You can't do anything with the phone off.
I asked you to try something in Post #13 above. Please read everything I post, and stop jumping around and trying random things. Read carefully, and proceed with caution and attention. Rushing around isn't going to help anything, and may do permanent damage to the phone (if you haven't already).
Click to expand...
Click to collapse
so what are my options now?
madshark2009 said:
so what are my options now?
Click to expand...
Click to collapse
Your options are to read more carefully.
I seriously do not like repeating myself; especially having to repeat myself when I say "read more carefully" and try what I already told you several posts ago.
redpoint73 said:
Your options are to read more carefully.
I seriously do not like repeating myself; especially having to repeat myself when I say "read more carefully" and try what I already told you several posts ago.
Click to expand...
Click to collapse
ok it worked now im back to stock..
but now there are no software updates available
PS: I did exactly what the post said! now i am back to stock rom with stock recovery and when i go to check updates it says my device is up to date (on lolipop 5.0.1) but before I had 6.0.1 marshmallow available now its not.

Categories

Resources