Related
Sorry, me again!
I needed to re-lock and ‘stockify’ my HTC M8 today for a few reasons. It ended up taking me 4 hours, and I still have no idea if it’s ‘back’ to the way it was before I rooted it. Before you carry on reading, please know I’m fully aware any lack of understanding is my fault, and perhaps I should have realised that compared to the N4s blissfully easy steps, the HTC was a massive can of worms. However, I’m going to ask the below anyway, so hopefully someone is friendly and helpful enough to aid me in my quest for enlightenment of android stuff without me having to spend more hours searching than actually reading useful stuff…
So coming from a Nexus 4, where the guide is super simple:
http://forums.androidcentral.com/ne...3923-guide-nexus-4-factory-image-restore.html
It turned out to be SERIOUSLY complicated. I’ve put down a ‘typical’ guide below, and put my questions about each step in bold. Sorry if it seems like I’m just complaining and being trite, but I’d like to know if A) I’ve missed a far easier way of doing this and if not B) is it just me that seems to have a massive amount of issues?
1. Made sure your device is S-Off. If not, download firewater and S-Off your device.
Assume this is just a thing that some phones have and some don’t?
2. Restore a nandroid of the stock Sense ROM, or find a stock ROM to flash. You'll have to dig around; I used a nandroid.
WHY? Is there no such thing as downloadable factory images for HTC One M8s? Also, where’s the step that says ‘run the commands fast boot erase user data, fast boot erase cache’ etc.?
3. Flash SuperSU.zip in recovery on top of the stock Sense ROM. You can find the SuperSU.zip here: http://download.chainfire.eu/396/SuperSU
Fair enough… still an another extra step compared to N4.
4. Use fast boot to flash the stock firmware zip to your device based on CID (this includes the stock recovery)
-This took SO MUCH EFFORT. Turns out I had to Super CID so that one of the recovery zips worked, because I was getting “FAILED (remote: 42 custom id check fail)” - and I’m now paranoid because I have no idea how important it is to get the correct CID-numbered ‘stock firmware’ etc. The ‘stock firmware’ zips seem to contain boot, radios, recovery .imgs, and with about 4 billion versions of the M8 apparently existing, could I have flashed a wrong boot or radio or something? ARE they even different per CID? Then I changed the CID back to O2___001 in case I need to take it in for warranty repairs, but is that trackable? Would someone know that I’ve messed around with the CID? Could someone going to look at my Nexus and be like “Oh this radio seems to be the one we’d expect on a HTC_001, NOT an O2___001 CID device, they must have tampered with it”.
—OH, and I had to boot into RUU mode as well, which apparently no one felt like explaining what the hell that’s for. So I’ve got and HBoot, a Fastboot, and RUU mode, which no clear way of knowing what to flash where…??
—-ALSO there was a HELL of a lot of faffing by people throwing around CID, MID, Verizon, Sprint, and comments like this doesn’t work on this AT&T model but will only work on non branded eu models with a flag attached to the speaker with an SSID of “600TZL” and a it MUST have a holographic projector otherwise your CID must equal the square root of the MID so that the factory image will know which ID your phone carrier provides through an inter web”.
5. Boot back up into sense, and follow this guide to remove the tampered banner in recovery. http://forum.xda-developers.com/show....php?t=2708565
-Is this just removing a banner? or is it ‘you’ve removed the banner from a visual point of view only, but if they actually look into it it will still appeared ‘tampered’.
6. Follow this guide to lock your boot loader and make it say **LOCKED** instead of **RELOCKED**. http://forum.xda-developers.com/show....php?t=2708571
-So ‘fast boot OEM lock’ doesn’t work on HTCs then- is that an N4 thing? Why all that complicated cmd line stuff? And on a side note, why is it that when referring to re-locking a N4 people call it just that- locking. But with an HTC people on XDA seem to say ‘to make the banner say locked’ as if its not actually locking it, just changing a bit of writing on the boot loader.
7. Boot your device back up, and open SuperSU. Go into settings and find the "full unroot" option and run that. Reboot your device like it suggests.
Does running the unroot zip (can’t find the thread) work? So I can make it appear like the HTC is brand new out of the box? Rather than having to go through the ‘first setup’ screen?
Other question: people seem to keep yammering on about modded RUUs, is there one? is there a couple? (i.e. should I view it a bit like TWRP and CWM- there’s others but there’s one everyone really uses). And if I ‘flash’ a modded RUU, again, is there an easily accessible stock one?
It's really not that complicated! I think the problem is comparing it to a Nexus 4 which is designed to be easily unlocked and locked, due to being a more developer orientated device.
An RUU is a stock image (like the Nexus images) and a modded one would just have the CID/MID requirement removed or something so it can be used on more phones. It would still be the stock, untampered image.
Also, the whole CID/MID thing is only applicable to American devices which vary between GSM and CDMA radios. ANY international modem will work in Europe and you will never find the wrong one.
S-Off is like unlocking the bootloader on a Nexus device except that in this case, its an extra step after unlocking the bootloader in order to be able to modify every partition and flash unsupported firmware in OEM mode. Every consumer phone is initially shipped S-On.
Thanks very much Veryone's v. helpful around here. Just a few more questions based on what you've said:
Matt said:
Also, the whole CID/MID thing is only applicable to American devices which vary between GSM and CDMA radios. ANY international modem will work in Europe and you will never find the wrong one.
Click to expand...
Click to collapse
Why did I have to Super-CID to install the stock recovery? And did I do the right thing by going back to my carrier CID afterwards?
Matt said:
S-Off is like unlocking the bootloader on a Nexus device except that in this case, its an extra step after unlocking the bootloader in order to be able to modify every partition and flash unsupported firmware in OEM mode. Every consumer phone is initially shipped S-On.
Click to expand...
Click to collapse
Although I've read in quite a few places I shouldn't have to S-On to take it in for a warranty repair, because some arrive to people S-off and they can't prove that you did it? Is that right?
Thank you for the step-by-step list. I am in the process of restoring my phone and all the guides say to look for "version-main", but that line is empty for me. What other information can I use to determine what recovery image to flash. Also the reason I want to go back to unrooted is so I can recieve OTA updates.
legolator said:
Thank you for the step-by-step list. I am in the process of restoring my phone and all the guides say to look for "version-main", but that line is empty for me. What other information can I use to determine what recovery image to flash. Also the reason I want to go back to unrooted is so I can recieve OTA updates.
Click to expand...
Click to collapse
this also happened to me- just another thing to confuse....
Can you not receive OTA updates if you're rooted? I thought it was just if you were running a different ROM?
tmorterlaing said:
this also happened to me- just another thing to confuse....
Can you not receive OTA updates if you're rooted? I thought it was just if you were running a different ROM?
Click to expand...
Click to collapse
I was under the impression that flashing a custom recovery removes the ability for the phone to install OTA updates. But I could of course be wrong about that.
I got the bootloader unlocked with HTC Dev and rooted, installed TWRP. I installed Revolution (?) rom but had the restarting issue I presume because of the firmware being incompatible. Searching ways to achieve S-Off leaves me a bit confused though. Could someone hold my hand through the process or direct me to where I can update my Firmware and apply the newer Roms please? Thanks.
xgonzox said:
I got the bootloader unlocked with HTC Dev and rooted, installed TWRP. I installed Revolution (?) rom but had the restarting issue I presume because of the firmware being incompatible. Searching ways to achieve S-Off leaves me a bit confused though. Could someone hold my hand through the process or direct me to where I can update my Firmware and apply the newer Roms please? Thanks.
Click to expand...
Click to collapse
OMG do I agree with that post! When you ask about how to do this, they point you to a thread with 300+ post and say its in there, go read... Ive been reading for 2 freaking days and Im more confused then ever!!! CID, SUPERCID, brick without them... NO explanation from there. REALLY!?
Now some people go OUT OF THEIR way to help you, where others seem to just say search the forums. With any of the searches, there is 4000+++ hits, it would be time to upgrade before I read them all. Ive read. Im still reading. Heck, I'm about to ADB back to stock to by pass s-off because of the lack of info, or its scattered across 5 or 6 threads. Sorry for the rant, but Im tired, sleepy, and cant find the info on the threads. Ive done my time reading, came out worse then I started...
Guys, I know your first few weeks at xda can be frustrating, but there are reasons why we do it this way and why requests for hand-holding don't go over well.
First, this is, as the name says, a developers' forum where a certain amount of technical knowledge is assumed. All of us were noobs once, but we got past that by reading and asking intelligent questions, not throwing up our hands and begging to be spoon-fed. If you get less-than-helpful responses, it's often because what seems baffling to you is a question that gets asked regularly to the point that people get tired of dealing with it. S-off and firmware updating are in that realm.
Second, and more importantly, once you go s-off and start mucking with firmware, there is a very real chance of bricking your phone if you're not careful. So having a solid understanding of what you're doing is critical. The people who brick are the ones who rush the process and miss or skip important steps because they don't realize why they exist.
Now, having said that, I can give you a little guidance.
S-off for the M9 is pretty idiot proof at the moment. It's only possible through a paid app, Sunshine. You download it, install it, and it will tell you if s-off is possible for your phone. If so, you buy a license for $25 and run it. Done.
Updating firmware is trickier, but this thread is the best place to start. Read the whole thing from the beginning (especially the first few posts), and if there's anything you don't understand, asking specific questions will usually get you helpful responses.
Good luck!
Good advice from iElvis to go slowly and try not to rush before gaining necessary knowledge .
Usually for example with firmware flashing thread all relevant info is contained in the first four posts written by original poster.
Basically if you are S on you may only flash firmware that matches your currently installed software.
When you have S off (as described above by iElvis) then you may flash any firmware, by changing cid if necessary.
Firmware flashing done in download mode via command
Fastboot flash zip nameofirmware.zip
Phone will flash part of firmware then reboot to download mode,
Then you enter same command again and remainder of file is flashed.
Then you're good to flash custom roms based on the firmware you flashed.
Sent from my HTC One M9 using XDA Free mobile app
paul_59 said:
Good advice from iElvis to go slowly and try not to rush before gaining necessary knowledge .
Usually for example with firmware flashing thread all relevant info is contained in the first four posts written by original poster.
Basically if you are S on you may only flash firmware that matches your currently installed software.
When you have S off (as described above by iElvis) then you may flash any firmware, by changing cid if necessary.
Firmware flashing done in download mode via command
Fastboot flash zip nameofirmware.zip
Phone will flash part of firmware then reboot to download mode,
Then you enter same command again and remainder of file is flashed.
Then you're good to flash custom roms based on the firmware you flashed.
Sent from my HTC One M9 using XDA Free mobile app
Click to expand...
Click to collapse
I am not new to xda or flashing roms , but definitely new to htc device. The problem is Alot of threads don't seem to explain "Why" .
your quote here has explained something so simple, that unfortunately was made to sound so complex in some other threads. Also many threads give slightly differing or slightly incomplete instructions. thats why I notice many people asking for a "FULL guide" and even some people offering to "donate if you can help me step-by-step update firmware" .
So , can i ask, just to clarify, after S-off, then SuperCID, we can flash any firmware update from any region? eg If i am from 1.32.710 i can flash 1.40.401 firmware? And ONLY then i can flash a custom rom that MUST be 1.40.401?
simonbigwave said:
So , can i ask, just to clarify, after S-off, then SuperCID, we can flash any firmware update from any region? eg If i am from 1.32.710 i can flash 1.40.401 firmware? And ONLY then i can flash a custom rom that MUST be 1.40.401?
Click to expand...
Click to collapse
Yes, you can flash any firmware for your model. You can't for example, flash cdma firmware on a gsm phone (nor should you try).
But you don't necessarily have to match rom to firmware. It's advisable for best performance, but not always necessary. in this case, however, there is a conflict between firmware and kernel across 1.32 and 1.40—they need to be the same. That means you can run a 1.40 rom over 1.32 firmware as long as you have a 1.32 kernel running (this is my current configuration). But if you have 1.40 firmware, you pretty much have to run a 1.40 rom.
I am missing somethihng some where.. Ive tried the steps above, although no "guide" said anything about supercid. However, Ive tried to flash the firmware, and i do get a cid mismatch error. So I'm stuck and lost. I dont know what to do... Cid is being reported differently depending on how I get it, Adb reports htc_001, the app and the scrip report CWE_001, and I cant seem to find anything to flash to it. Im literally pulling out my hair.
klloyd said:
I am missing somethihng some where.. Ive tried the steps above, although no "guide" said anything about supercid. However, Ive tried to flash the firmware, and i do get a cid mismatch error. So I'm stuck and lost. I dont know what to do... Cid is being reported differently depending on how I get it, Adb reports htc_001, the app and the scrip report CWE_001, and I cant seem to find anything to flash to it. Im literally pulling out my hair.
Click to expand...
Click to collapse
As far as I know, get S-off from Sunshine app. Easiest way. Then in adb set your sid to super cid..try here a full guide, after u have used sunshine app to get s-off http://forum.xda-developers.com/showthread.php?t=2317536 u need to get S-off first AFAIK....i agree its confusing.
Hi guys,
Verizon HTC One M8 rooted, S-off,with CWM, running the old digital high GPE 4.4.4.
HBOOT 3.16.0
RADIO 0.89.20.0321
10G storage
I did the firewater procedure when I first got the phone with no problems. Now I am trying to install the new LolliGPE on here and getting nothing but headaches. I have tried to install TWRP(different versions) via Flashify AND fastboot, but when it reboots, it stays on the white HTC One screen-"loading recovery". I have done this multiple times, and then adb reboot, install CWM via flashboot, and no problems. I don't know what else to do, and don't wanna mess my phone up especially as the next step is updating RUU, etc. I'm thinking I may have to update hboot, I just don't want to do anything un-neccesary to brick my phone. Any ideas? Thanks!!
Your older hboot requires an older version of TWRP. Plus, on older TWRP versions, depending on which TWRP version exactly, the CDMA M8 variants had a different TWRP recovery image (as recovery is stored on a different partition location for that version versus the "GSM" or non-CDMA M8). So you need to be really careful (I think a brick is even possible).
I'd suggest updating to the current Verizon Lollipop firmware before proceeding. Your hboot is ancient, and will cause all sorts of issues. After that, the current version TWRP 2.8.7 should install fine.
Thanks for the reply..
So update Hboot first, then install TWRP, then RUU, then ROM?
dl12458 said:
So update Hboot first, then install TWRP, then RUU, then ROM?
Click to expand...
Click to collapse
Shouldn't be a need to flash new hboot, RUU will do that.
Further, you don't want to install TWRP before the RUU; as RUU will wipe it out with stock recovery, anyway.
So in general, you want to:
1) Backup your personal data, RUU will wipe the phone including internal storage.
2) RUU
3) Install TWRP
4) Flash the custom ROM of your choice
Although it should be noted that some folks have had trouble installing TWRP after installing the OTA (the one with Stagefright fix in particular), at least on "GSM" versions of the M8. So you might research and see if VZN folks are having the same issue on the RUU with Stagefright fix that you linked in your PM to me. But at least in browsing the last few pages of the thread, I don't see any mention of TWRP issues (and some confirmations of TWRP working okay):
http://forum.xda-developers.com/verizon-htc-one-m8/development/exe-zip-ruu-m8vzw-5-0-1-s-off-onlynewest-t3047103
Great, the update worked!!
I have one final question regarding the LolliGPE ROM (if you have any experience with it). Since I am now on 5.0.1, I tried installing the LolliGPE ROM, and once it is through with its inital bootup, Google prompts me to download a 600mb update. I allow to it to, but then it just gets stuck. It doesn't download anything, and I cannot procede any further. Do I need to flash the Verizon firmware listed, even though the RUU updated? I used the following to try and flash the VZN firmware 1. "fastboot oem rebootRUU" (Phone goes into RUU mode) 2."fastboot flash zip firmware.zip", but I get a response "cannot load firmware.zip" Any ideas?? Thanks again!!
Forum
http://forum.xda-developers.com/showthread.php?t=2716306
redpoint73 said:
Shouldn't be a need to flash new hboot, RUU will do that.
Further, you don't want to install TWRP before the RUU; as RUU will wipe it out with stock recovery, anyway.
So in general, you want to:
1) Backup your personal data, RUU will wipe the phone including internal storage.
2) RUU
3) Install TWRP
4) Flash the custom ROM of your choice
Although it should be noted that some folks have had trouble installing TWRP after installing the OTA (the one with Stagefright fix in particular), at least on "GSM" versions of the M8. So you might research and see if VZN folks are having the same issue on the RUU with Stagefright fix that you linked in your PM to me. But at least in browsing the last few pages of the thread, I don't see any mention of TWRP issues (and some confirmations of TWRP working okay):
http://forum.xda-developers.com/verizon-htc-one-m8/development/exe-zip-ruu-m8vzw-5-0-1-s-off-onlynewest-t3047103
Click to expand...
Click to collapse
dl12458 said:
I tried installing the LolliGPE ROM, and once it is through with its inital bootup, Google prompts me to download a 600mb update. I allow to it to, but then it just gets stuck. It doesn't download anything, and I cannot procede any further. Do I need to flash the Verizon firmware listed, even though the RUU updated?
Click to expand...
Click to collapse
I don't use that ROM, or any GPE ROMs, for that matter. So I'll be of limited help on this one.
What I can say, I've seen another post or 2 reporting a similar issue: GPE or AOSP custom ROM installed, will prompt to download an update upon setup (with no option to do otherwise), then phone is stuck.
So you might check the ROM thread, to see if others reported this. Or other help threads, as I've mentioned, I know others have posted this same issue; and that thread(s) may have some insight on a fix.
This issue is pretty weird. You won't normally see a custom ROM accept any type of OTA update, and certainly not a "forced" one like this at startup. In general, custom ROMs won't play well with any type of official OTA update (and updates are often disabled for this reason). And it seems you had no choice to bypass it, which is also odd.
dl12458 said:
Great, the update worked!!
Do I need to flash the Verizon firmware listed, even though the RUU updated? I used the following to try and flash the VZN firmware 1. "fastboot oem rebootRUU" (Phone goes into RUU mode) 2."fastboot flash zip firmware.zip", but I get a response "cannot load firmware.zip" Any ideas?? Thanks again!!
Click to expand...
Click to collapse
Again, I'm not sure what is going on with the forced "update". But I doubt flashing firmware will fix anything.
The error "cannot load" when trying to fastboot flash a file, almost always means the file is not present (meaning not located where it should be, or named wrong). You need to have the desired firmware zip in the same folder where fastboot.exe is located (assuming you are using a PC). And for the command you listed, the firmware actually/literally has to be named "firmware.zip" (with no quotes). If the firmware file is named something else, you either need to rename the file to "firmware.zip" or use the actual exact file name in the fastboot command. Another common problem, is on Windows, folks often have the option enabled to hide file extensions (this is typically enabled by default, and I highly recommended you turn this off). So if you already renamed the file, it may actually be named "firmware.zip.zip" even though Windows will display it as "firmware.zip". If you see a lot of file types with not extensions at all, its very likely you have the option enabled to hide file extensions.
But again, I'm not sure that flashing the firmware is going to help.
If you can't find an easier fix for the "forced" update and stuck on boot screen; my thought would be to try flashing another ROM. Or at worst, RUU to stock again, and try another ROM.
Update- I was trying to install the 5.0.1 update, and when I tried the 5.1 it worked!! Thanks for your help.
redpoint73 said:
I don't use that ROM, or any GPE ROMs, for that matter. So I'll be of limited help on this one.
What I can say, I've seen another post or 2 reporting a similar issue: GPE or AOSP custom ROM installed, will prompt to download an update upon setup (with no option to do otherwise), then phone is stuck.
So you might check the ROM thread, to see if others reported this. Or other help threads, as I've mentioned, I know others have posted this same issue; and that thread(s) may have some insight on a fix.
This issue is pretty weird. You won't normally see a custom ROM accept any type of OTA update, and certainly not a "forced" one like this at startup. In general, custom ROMs won't play well with any type of official OTA update (and updates are often disabled for this reason). And it seems you had no choice to bypass it, which is also odd.
Again, I'm not sure what is going on with the forced "update". But I doubt flashing firmware will fix anything.
The error "cannot load" when trying to fastboot flash a file, almost always means the file is not present (meaning not located where it should be, or named wrong). You need to have the desired firmware zip in the same folder where fastboot.exe is located (assuming you are using a PC). And for the command you listed, the firmware actually/literally has to be named "firmware.zip" (with no quotes). If the firmware file is named something else, you either need to rename the file to "firmware.zip" or use the actual exact file name in the fastboot command. Another common problem, is on Windows, folks often have the option enabled to hide file extensions (this is typically enabled by default, and I highly recommended you turn this off). So if you already renamed the file, it may actually be named "firmware.zip.zip" even though Windows will display it as "firmware.zip". If you see a lot of file types with not extensions at all, its very likely you have the option enabled to hide file extensions.
But again, I'm not sure that flashing the firmware is going to help.
If you can't find an easier fix for the "forced" update and stuck on boot screen; my thought would be to try flashing another ROM. Or at worst, RUU to stock again, and try another ROM.
Click to expand...
Click to collapse
Hi,good afternoon,my friend brought me his HTC one m9,because i have experience with these things, i have flashed many devices of different brands but this is my first HTC device.
Well the problem is this:
He unlocked the botloader,installed TWRP ,super SU.zip (via twrp) and a custom rom with s-on,after that he lost signal,the phone does not have imei and baseband is uknown.
I've searched trough xda ,before posting this,so i came across with a thread that said that the phone can recover signal flashing a custom rom and a kernel,did that with no success. And also i've read that returning the bootloader to locked status,will allow me to flash a RUU file in order to get back to stock.
So, i relocked the bootloader,using CMD, but now the phone just boots into bootloader ,i can enter download mode aswell,but its stucked there.
Phone is recognized by windows,via fastboot.
So,the phone status is bootloader relocked,and s-on.
i´ve tried flashing the RUU via sdcard on download mode and gives me error,also i tried using fastboot commands and the result is the same,i can not flash the RUU file.
Any suggestions are very apreciated. Thanks fot your time.
kalel29 said:
Hi,good afternoon,my friend brought me his HTC one m9,because i have experience with these things, i have flashed many devices of different brands but this is my first HTC device.
Well the problem is this:
He unlocked the botloader,installed TWRP ,super SU.zip (via twrp) and a custom rom with s-on,after that he lost signal,the phone does not have imei and baseband is uknown.
I've searched trough xda ,before posting this,so i came across with a thread that said that the phone can recover signal flashing a custom rom and a kernel,did that with no success. And also i've read that returning the bootloader to locked status,will allow me to flash a RUU file in order to get back to stock.
So, i relocked the bootloader,using CMD, but now the phone just boots into bootloader ,i can enter download mode aswell,but its stucked there.
Phone is recognized by windows,via fastboot.
So,the phone status is bootloader relocked,and s-on.
i´ve tried flashing the RUU via sdcard on download mode and gives me error,also i tried using fastboot commands and the result is the same,i can not flash the RUU file.
Any suggestions are very apreciated. Thanks fot your time.
Click to expand...
Click to collapse
For download mode SD card method:
Make sure you're using an external SD card, not internal storage.
Make sure SD card is formatted properly.
Make sure file is named 100% correctly and is meant for that specific carrier /model.
No reason it shouldn't work.
Sent from my HTC6545LVW using Tapatalk
kalel29 said:
i´ve tried flashing the RUU via sdcard on download mode and gives me error,also i tried using fastboot commands and the result is the same,i can not flash the RUU file.
Click to expand...
Click to collapse
Are you sure you flashed the correct one? Some basic information about firmware versions, RUUs and instructions how to flash them can be found in my sticky thread in the general section.
Concerning the reception problem: It's important whether you tried to use a sense-based custom rom or a non-sense-based one. The mono-kernel only works with non-sense roms like CM or Candysix. Moreover the reception problem has been covered in this thread some days ago. If you want to use a sense-based rom the re-flash boot.img "trick" might be working for you, too.
Sidenote: There is absolutely no need for flashing SuperSU if you are going to erase the system and to flash a custom com. It doesn't harm the device but it's a waste of time.
Flippy498 said:
Are you sure you flashed the correct one? Some basic information about firmware versions, RUUs and instructions how to flash them can be found in my sticky thread in the general section.
Concerning the reception problem: It's important whether you tried to use a sense-based custom rom or a non-sense-based one. The mono-kernel only works with non-sense roms like CM or Candysix. Moreover the reception problem has been covered in this thread some days ago. If you want to use a sense-based rom the re-flash boot.img "trick" might be working for you, too.
Sidenote: There is absolutely no need for flashing SuperSU if you are going to erase the system and to flash a custom com. It doesn't harm the device but it's a waste of time.
Click to expand...
Click to collapse
Yes I flashed the one for my operator. Can I flash another RUU?
About your links, I'll check them when I get back from work. Thanks.
Is your phone branded by your carrier? (Can be checked by looking at the SKU of the currently installed firmware.) If not then it's the wrong RUU. Is the RUU made for the same firmware version as the one that is currently installed on the phone or does the RUU even have a newer version? If not then it's the wrong RUU.
Flippy498 said:
Is your phone branded by your carrier? (Can be checked by looking at the SKU of the currently installed firmware.) If not then it's the wrong RUU. Is the RUU made for the same firmware version as the one that is currently installed on the phone or does the RUU even have a newer version? If not then it's the wrong RUU.
Click to expand...
Click to collapse
Hi again, the phone is giving me this error :
im still lost ,hope this helps to point me in the right direction.
Code:
D:\Francisco\Desktop\HTC\fastboot_adb\fastboot_adb>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himaulatt
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 3.44.600.1
(bootloader) boot-mode: RUU
(bootloader) version-baseband: 01.01_U11440801_97.04.60111G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA11000
(bootloader) cid: HTC__332
all:
finished. total time: 0.033s
Thanks
You still didn't mention the name of the RUU you wanted to flash. However a quick search for your SKU (Telcel Mexico) showed me that there is no RUU available you could use. The only one I could find is linked in my thread and that one is too old for your phone since you can't downgrade the firmware with S-ON. You either need to re-unlock the bootloader, flash a sense-based custom rom and buy the sunshine app or try to find someone who has a java card. Both solutions would set the phone S-OFF so that you would be able to use that old RUU. Alternatively you could contact Llabtoofer (a link can be found in my thread and in my google sheet). He has a RUU service with RUUs that are not available publicly*. Neither the sunshine app, nor a java nor the RUU service are for free. Llabtoofer and the sunshine app cost nearly the same. I don't know how much you need to pay for java card services. Be aware that even if it's OK if the phone is running a custom right now** and you don't want to use any of these solutions that you still lack a way back to stock if a new OTA (like the one for Android N) gets distributed and therefore you won't be able to install it.
If you use the old RUU all OTAs that got installed on your phone will need to get re-installed.
However you choose you should read the tab "make your own backup" of my sheet after the phone got recovered and all available OTAs got installed but before anyone starts flashing anything, again. This way you will learn how to create a backup that will help you out if you face such a situation, again. Instructions how to restore such a backup correctly can be found in the tab "twrp backups".You'll always need to create a new backup when a new OTA got installed on your phone and you want to re-root it. Besides if you're willing you could upload the backup (and any upcoming ones) and share it(/them) with the xda community by posting the download link(s) in my thread.
* He wants to know the hboot version of your phone of you request his help. Since the One M9 has no hboot but an aboot and that one never got updated you can enter version 1.0.0.0000. That's the current aboot version.
** Possible solutions for recovering the reception can be found in my first post in this thread. There is no need to flash a RUU since your IMEI and your baseband are still intact but the boot.img of the rom you tried to use was/is incompatible.
Flippy498 said:
You still didn't mention the name of the RUU you wanted to flash. However a quick search for your SKU (Telcel Mexico) showed me that there is no RUU available you could use. The only one I could find is linked in my thread and that one is too old for your phone since you can't downgrade the firmware with S-ON. You either need to re-unlock the bootloader, flash a sense-based custom rom and buy the sunshine app or try to find someone who has a java card. Both solutions would set the phone S-OFF so that you would be able to use that old RUU. Alternatively you could contact Llabtoofer (a link can be found in my thread and in my google sheet). He has a RUU service with RUUs that are not available publicly*. Neither the sunshine app, nor a java nor the RUU service are for free. Llabtoofer and the sunshine app cost nearly the same. I don't know how much you need to pay for java card services. Be aware that even if it's OK if the phone is running a custom right now** and you don't want to use any of these solutions that you still lack a way back to stock if a new OTA (like the one for Android N) gets distributed and therefore you won't be able to install it.
If you use the old RUU all OTAs that got installed on your phone will need to get re-installed.
However you choose you should read the tab "make your own backup" of my sheet after the phone got recovered and all available OTAs got installed but before anyone starts flashing anything, again. This way you will learn how to create a backup that will help you out if you face such a situation, again. Instructions how to restore such a backup correctly can be found in the tab "twrp backups".You'll always need to create a new backup when a new OTA got installed on your phone and you want to re-root it. Besides if you're willing you could upload the backup (and any upcoming ones) and share it(/them) with the xda community by posting the download link(s) in my thread.
* He wants to know the hboot version of your phone of you request his help. Since the One M9 has no hboot but an aboot and that one never got updated you can enter version 1.0.0.0000. That's the current aboot version.
** Possible solutions for recovering the reception can be found in my first post in this thread. There is no need to flash a RUU since your IMEI and your baseband are still intact but the boot.img of the rom you tried to use was/is incompatible.
Click to expand...
Click to collapse
Ok,thanks, and yes,the RUU I was trying to flash I the telcel one.
I'm going to tell my fiend that he needs to pay in order to get his phone working.
Thanks again for everything. Have a nice day.
Update
I managed to unlock the bootloader again, the phone boots, but it has no signal.
Do I need sunshine and then flash any ruu?
Or what can I do? BTW my friend agreed to pay for sunshine.
kalel29 said:
Update
I managed to unlock the bootloader again, the phone boots, but it has no signal.
Do I need sunshine and then flash any ruu?
Or what can I do? BTW my friend agreed to pay for sunshine.
Click to expand...
Click to collapse
Is it a sense-based rom? If yes, did you reflash the stock boot.img? Or is it a non-sense-based rom? In that case the mono kernel which is linked above needs to be flashed for recovering the reception.
If you're currently using a sense-based rom (which is not an HTC 10 port - e.g. Viper one m9 4.3) then you can install the sunshine app and start it. The app will explain the rest of the procedure. Just google "sunshine s-off" and you'll find it. After your phone got S-OFF you simply need to try reflashing the RUU.
Flippy498 said:
Is it a sense-based rom? If yes, did you reflash the stock boot.img? Or is it a non-sense-based rom? In that case the mono kernel which is linked above needs to be flashed for recovering the reception.
If you're currently using a sense-based rom (which is not an HTC 10 port - e.g. Viper one m9 4.3) then you can install the sunshine app and start it. The app will explain the rest of the procedure. Just google "sunshine s-off" and you'll find it. After your phone got S-OFF you simply need to try reflashing the RUU.
Click to expand...
Click to collapse
The phone has the ICE rom,Twrp and superSU,I think it's a sense-based rom, sorry I can't give you more info, as I said I'm new in flashing HTC, but I'm learning thanks to you.
ICE is sense-based. It's using HTCs own launcher and framework which is called Sense. Examples for non-sense-based roms are CM, CandySix or other AOSP roms.
Depending on the version of ICE that got flashed on the phone you might need to revert back to an older version*. The newest ICE rom is based on an HTC 10 port and I've read several posts of users reporting that they couldn't use sunshine with an HTC 10 port.
* I don't know which version that would be. I've never used ICE so you would need to figure that out on your own.
Flippy498 said:
ICE is sense-based. It's using HTCs own launcher and framework which is called Sense. Examples for non-sense-based roms are CM, CandySix or other AOSP roms.
Depending on the version of ICE that got flashed on the phone you might need to revert back to an older version*. The newest ICE rom is based on an HTC 10 port and I've read several posts of users reporting that they couldn't use sunshine with an HTC 10 port.
* I don't know which version that would be. I've never used ICE so you would need to figure that out on your own.
Click to expand...
Click to collapse
So basically, no matter what rom I flash,sense or no sense based, I will need sunshine in order to have a working baseband?
No. Sunshine is needed for getting back to stock for installing upcoming OTAs. And in case you want to use a sense-based roms it's needed for being able to backup the stock boot.img. As explained before, you need to re-flash that one after you flashed the custom rom. The boot.img of 3.35.y (y is a placeholder for any possible number) custom roms isn't compatible with 3.x firmware if x is not equal to 35 (as in your case). At the moment your only option for not having to use sunshine would be flashing a non-sense-based rom and the kernel I linked in an earlier post. But as explained before you wouldn't be able to install upcoming updates like the one for Android N if you choose not to use sunshine.
Flippy498 said:
No. Sunshine is needed for getting back to stock for installing upcoming OTAs. And in case you want to use a sense-based roms it's needed for being able to backup the stock boot.img. As explained before, you need to re-flash that one after you flashed the custom rom. The boot.img of 3.35.y (y is a placeholder for any possible number) custom roms isn't compatible with 3.x firmware if x is not equal to 35 (as in your case). At the moment your only option for not having to use sunshine would be flashing a non-sense-based rom and the kernel I linked in an earlier post. But as explained before you wouldn't be able to install upcoming updates like the one for Android N if you choose not to use sunshine.
Click to expand...
Click to collapse
Finally i have signal again,flashed slim 6 and monokernel. Thank you so much,i've learned something new about HTC now im going to return the phone to my friend,also i explained what you told me in order to have a sense based rom.
I recently got my hands on a One M9 but I'm having trouble updating anything on it. I check for updates and it says there aren't any available. However, my software version is 1.14.531.1, which is older than anything I've seen in any threads anywhere.
Here's the readout from fastboot getvar all:
kernel: lk
product: htc_himaul
version: 1.0
vzwisLTE:
vzwmid: HTC
max-download-size: 800000000
imei:
battery-status: good
version-main: 1.14.531.1
boot-mode: download
version-bootloader: 1.0.0.0000
mid: 0PJA12000
cid: 11111111
It doesn't say it here, but the phone is s-off.
I started by following the instructions at Cyanogenmod: unlocked, installed TWRP, installed ROM. However, it wouldn't install the ROM. It failed at the point where it tries to verify the device. I changed the recovery to the Cyanogenmod recovery and tried again, but that didn't work either. After a bit of reading, I thought that perhaps I needed to update the bootloader and that a RUU update might do the trick. I got the most recent one from HTC and ran it. It stalled where it says "sending" at 0%. I put the ROM.zip on the SD card to try it that way. That also failed. I relocked the bootloader and tried the RUU again with the same result.
I've wondered if I need to update the firmware per this thread http://forum.xda-developers.com/one-m9/development/firmware-t3068243 but I'm still new to the HTC world and not sure if that's it or if I'm just guessing. The firmware files I found there are much smaller than I expected, so I'm not sure what exactly they will update or if they'll fix the problem or just make it worse.
Can anyone tell me where to go from here, or at least point me in the right direction?
You can't flash offical firmwares unless your phone is stock. I think you should be ok flashing unsigned zips though. I couldn't tell you if htc do incremental or if you can just flash the latest. Flippy's thread might shine a light on something.. Your Cid is supercid.
Beamed in by telepathy.
So, are you saying that if I go back to the stock recovery that I should be able to use the RUU to update everything? There are a bunch of stock recoveries here, but none of them match my phone. The oldest ones there are several versions newer than mine and none match my CID. Can I still use one of them or do I need to find one that matches my phone exactly?
When I got the phone there was an SD card in it with a 0PJAIMG.zip file and a text file with a very long name with the software version (1.14.531.1) in it. Fortunately I saved them. I put those files back on and tried flashing that 0PJAIMG file and this time it worked. It seems to have removed the recovery I put on it and now it looks completely stock, with a locked bootloader and everything. Updating with the latest RUU still doesn't seem to work, however. It's still stalled at "sending" and 0%.
I would like to try a different RUU that's a smaller jump, but I haven't had any luck finding one yet.
OTA updates are incremental. A RUU on the other hand contains the whole firmware that has been distributed for its SKU until the point that RUU got released. Besides it contains the whole system. That's why RUUs are so big.
Sneakyghost's files lack some parts of the official firmware packs since they're not meant to get flashed if you want to get back to stock. They're meant to get flashed if you want to update your phone's firmware without reverting it's system back to stock since this way is less time consuming if you want to flash a new custom rom afterwards. That's why they're so much smaller than a RUU. Besides, they're unsigned and you won't be able to use them without S-OFF.
I personally don't like the *.exe versions of RUUs since they use fastboot and many users aren't able to set up their adb/fastboot environment correctly. Therefore, I neither support flashing RUU.exe files nor fastboot flashing of RUU.zip files. However if you extract the RUU.zip from the latest x.xx.531.x RUU.exe you could flash it via a SD card. I don't have a direct link to a guide for the extraction at the moment but there should be several here on xda which you should be able to find via google. It doesn't matter if they're written for an older HTC phone since the steps you need to do are always the same. Instructions for flashing a RUU via SD card can be found in my google sheet (which is linked in my signature).
And one last thing: The SCID prevents the M9 from installing OTAs. Therefore, you should revert it back to its original CID if you want to install any OTA.
Personal opinion: Since you can't use RUUs with a different MID than the one of your phone although you use the SCID (that was possible on older HTC phones) and you aren't able to install OTAs if you use it (that was possible on older phones, too) I personally don't think that there is any benefit left in using it.
Edit: I forgot to mention that there is a dedicated forum for the T-Mobile US M9 here on xda which can be found with the xda search function. You might find the files you need over there. Due to that other forum the T-Mobile US variant of the M9 isn't that much supported here in the forum for the international variant.
Sent from my HTC One S using XDA Labs
Thanks for the info on the T mobile forum. I wasn't aware of that and thought this was the only forum for the M9 here. I'll look for it.
I've already tried using the SD card method and that also failed.
I haven't changed the CID. It was the superCID when I got it. I don't think the previous owner changed it either because the phone seems unused. It still has the barcode sticker on the back and it's clearly be barely handled at all. The phone was originally a test unit or something because it has a serial number engraved on the front and it runs some HTC reporting software. It's rooted out of the box. I'm trying to replace the ROM to get rid of that extra software. I just mention that to explain why it's already rooted, s-off and superCID.
drfarmkid said:
Thanks for the info on the T mobile forum. I wasn't aware of that and thought this was the only forum for the M9 here. I'll look for it.
I've already tried using the SD card method and that also failed.
I haven't changed the CID. It was the superCID when I got it. I don't think the previous owner changed it either because the phone seems unused. It still has the barcode sticker on the back and it's clearly be barely handled at all. The phone was originally a test unit or something because it has a serial number engraved on the front and it runs some HTC reporting software. It's rooted out of the box. I'm trying to replace the ROM to get rid of that extra software. I just mention that to explain why it's already rooted, s-off and superCID.
Click to expand...
Click to collapse
I would say the phone is modified. As far as I know, test units don't need S-OFF or the SCID since they simply use different firmware versions than normal units. You can change every version of the M9 into a test unit by applying for HTCs beta program.
What was the error that got shown when the SD card method failed? Did you try to flash the correct RUU.zip for your phone? As mentioned before your MID needs to match even if the phone has the SCID. Therefore, you can only use x.xx.531.x RUUs.
Edit: I forgot to mention that every S-OFFed device runs that reporting software you mentioned if that device is running the stock rom. That Software gets triggered by the S-OFF flag.
Sent from my HTC One S using XDA Labs
Well, I managed to find the 1.32.531.33 RUU in the forum for the T-mobile variant (thanks flippy498 for bringing it to my attention) and that ran just fine. Once that was done I tried running the RUU I downloaded earlier from HTC (3.39.531.31) and it worked fine. It seems the problem was indeed that I just needed something that was a smaller jump. I've seen no mention of any software version earlier than 1.32 anywhere in this forum, so I wonder if my phone was an early test unit or something that the version 1.14 mine had was an earlier pre-release version or something and that is why I had the problems I did.
Thanks for the info regarding the reporting software running on all s-off phones. I saw something about red text in other threads and wondered if that's what it referred to. Now I know.