Hi,
So as the title says, I'm totally new to HTC world, had EVERY other phone in hand during the past 3 years but never an HTC.
So I trade my Nexus 6 with an HTC One m8.
Phone history (That I know of):
S-off, Unlocked Bootloader
Bought as unbranded.
Flashed with GPE
Flashed to Stock (with root)
Flashed to Developer Edition (By Me).
Some issues I've noticed:
The folder /system/etc/sdk --- doesn't exist in the phone...
HTC SDK API level: UNKNOWN
Xposed (XSence) not recognizing phone with Sence UI (Settings->Info->Sence 6.0)...
When flashed to Developer Edition I didn't flashed a nandroid backup.. Just changed the CID and MID to US_(can't remember)001 and flashed ATT RUU (Current: 4.16.1540.8, It was higher before)
When I'm playing on any game or an app (full-screen or not), when I get a call, it doesn't look like lollipop and it shows on the entire screen! instead of a "Heads-Up"
What do I need to do? flash stock? (Really, how..?)
Or maybe flash a Developer Edition but with the nandroid backup before?
I followed this guide, but I can't figure out what a firmware of 1.xx.xxx has to do with the version I want 4.16.1540.8, and I can't find anything so I want my phone intact and not bricked..
Can anyone clarify part 4?
http://forum.xda-developers.com/htc-one-m8/general/change-wwe-m8-to-dev-edition-ota-t2826567
4 Flash the stock recovery or firmware zip (which includes the recovery) matching your desired software number NOTE - yet again the download links below are for DEV edition for example - the versions relevant to the variant you want are accessible through the search function. The firmware is HERE this shouldn't wipe sd contents but backup to be sure thanks @ckpv5
Follow THIS GREAT GUIDE for flashing via fastboot thanks @Sneakyghost
Or This quality tutorial to flash firmware from external sd card thanks @skulldreamz
if you are s off, sd contents should be untouched after flashing firmware but back them up just in case
To flash just the recovery, get the recovery.img from the zip above and put it in your fastboot folder on your PC. Then in CMD type "fastboot flash recovery recovery.img" then "fastboot erase cache"
Click to expand...
Click to collapse
** In general, what's the point of flashing a nandroid backup and then flash an RUU? it makes the nandroid useless, doesn't it?
Thank you all for trying and helping out!
A RUU makes a nandroid flash totally useless.
Your device should be easily fixed by running a proper Sense RUU.
The GPE RUU apparently changes the size of the system partition, so after that, the device will either not accept or break any (bigger) Sense based system. So, in order to return the device to normal partition layout, a Sense RUU is required as far as I know.
To be quite sure I'd recommend reading the GPE conversion thread to learn how to properly restore to sense. I'm no expert for that.
Any issue in the ROM which you described could be due to an improper restore after running a full GPE conversion. It could also be a simply messed up ROM.
Your description sounds like you've done many things in all sorts of orders, so it's near impossible to tell what's actually wrong. The best strategy imho is to start over fresh with a RUU.
Thank you! that was fast..
So how can I return to full stock with a proper RUU? google? or you know something a bit better?
Can I just download the RUU from HTC website and flash it? would it be OK?
EDIT: in some guides I've seen, it says that the guid is applies for CIDs: HTC_001, HTC_A48 and so on.
the question is, if I have a dev CID (*002) can I follow that guide?)
Thanks again!
Well..
I followed this guide here: http://forum.xda-developers.com/showthread.php?t=2735235
Skipped s-on, tampered flag.
The HTC SDK API still UNKNOWN...
What am I doing wrong?!
Thanks
nirh216 said:
The HTC SDK API still UNKNOWN...
What am I doing wrong?!
Click to expand...
Click to collapse
You're not doing anything wrong. Its a known bug that SDK API is not listed, and nothing to be worried about.
Returning to stock doesn't make a difference. I'm pretty sure the RUU installed Sense LP correctly. But HTC changed a lot of things that removed Material Design and a lot of other features from Lollipop. Sense LP in fact looks almost exactly like Sense KK, with the exception of a few minor things such as the LP notification style, and Recent Apps style (option LP style).
If you want "real" Material Design, flash a GPE ROM or fully convert to GPE.
Thanks for the help! I don't want a vanilla android.. it's sucks to my opinion. The only thing that bothers me is that the dialer stinks and when in a game and getting a call, it's not getting the LP notification bar, it's going full screen. And I lose the game.. LOL any fix for that one?
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.
Good day all, I just got this phone yesterday so I apologize in advance for any noob questions as I have not done much research into the M8
I got this phone used in great condition, and I'd really love to try the stock HTC experience. Unfortunately, I got it with Android Revolution HD installed, and I did not like it so I flashed CM12 on to it, which is great but I'd really like to try the stock because I like Sense.
Does anybody have a backup of their stock rom they can post for me to restore the system? I've got TWRP installed and my bootloader is unlocked.
No S-OFF yet, I will have the funds to do it on my card in the week.
No SuperCID yet
Any other necessary information could be provided.
Post your fastboot getvar all (minus serial no & imei no)
no info, how to help ?
ckpv5 said:
Post your fastboot getvar all (minus serial no & imei no)
no info, how to help ?
Click to expand...
Click to collapse
Here you go
Sorry, I didn't know how to get it. Its been a while since I used HTC
Yours is a Developer Edition device
The latest stock is Lollipop 4.16.1540.8
You can use a RUU to revert everything to stock including the internal storage as it wipes the storage
You can get it here : http://dl3.htc.com/application/RUU_...G_20.68.4196.01_F_release_411207_signed_2.exe
What you need to do is :
1. put your device in bootloader/fastboot mode and connect to PC
2. relock bootloader - fastboot oem lock (because your device is S-On)
3. Right click the RUU exe that you downloaded, select "run as administrator" .. wait for it to run, later there is a dialog box, accept, next, next, update, blablabla until it finish and your device rebooted... done.
Note : this will wipe everything on your internal storage. Make a backup of important files before you proceed.
Re step 2 .. you can try to skip it first (as I'm not sure whether Developer Edition device is an unlocked device by default)
If you have error 155 then you need to do step 2
And an alternative way of doing this :
Download the 3.28.1540.5 backup from this thread : http://forum.xda-developers.com/showthread.php?t=2701376
restore the backup with TWRP and install its matching stock recovery image
check for OTA and accept, download and install
This way you don't need to relock bootloader and it does not wipe your internal storage
ckpv5 said:
Yours is a Developer Edition device
The latest stock is Lollipop 4.16.1540.8
You can use a RUU to revert everything to stock including the internal storage as it wipes the storage
You can get it here : http://dl3.htc.com/application/RUU_...G_20.68.4196.01_F_release_411207_signed_2.exe
What you need to do is :
1. put your device in bootloader/fastboot mode and connect to PC
2. relock bootloader - fastboot oem lock (because your device is S-On)
3. Right click the RUU exe that you downloaded, select "run as administrator" .. wait for it to run, later there is a dialog box, accept, next, next, update, blablabla until it finish and your device rebooted... done.
Note : this will wipe everything on your internal storage. Make a backup of important files before you proceed.
Re step 2 .. you can try to skip it first (as I'm not sure whether Developer Edition device is an unlocked device by default)
If you have error 155 then you need to do step 2
And an alternative way of doing this :
Download the 3.28.1540.5 backup from this thread : http://forum.xda-developers.com/showthread.php?t=2701376
restore the backup with TWRP and install its matching stock recovery image
check for OTA and accept, download and install
This way you don't need to relock bootloader and it does not wipe your internal storage
Click to expand...
Click to collapse
WOW ARE YOU SERIOUS?!?!?
I own a Dev Ed M8??
How can I tell? What exactly makes it Dev Ed?
I'm extremely happy right now so sorry if I ask a tonne of questions.
BTW I just used snipping tool to black out my serial number and IMEI number if that somehow made you think it's a Dev Ed (which I hope it didn't)
I traded my Note 3 for this yesterday expecting to get a normal used M8
I would have never expected to have gotten a used Dev Ed.
Also, related to the backup (because I'd prefer to not relock the bootloader or lose my stuff)
There isn't a boot.img with the exact number of 3.28.1540.5
Will one of the 3.28.401.x work? (There's three, each ending with either 6, 7 or 9)
EDIT: I mistakenly thought you said boot.img instead of recovery.img, which I found the correct compatibility for the version of the backup you instructed to restore.
I also want to know if it's necessary to flash the stock recovery, seeing that I may inevitably go back to the GPE rom I'm running right now.
rdar_93 said:
WOW ARE YOU SERIOUS?!?!?
I own a Dev Ed M8??
How can I tell? What exactly makes it Dev Ed?
I'm extremely happy right now so sorry if I ask a tonne of questions.
BTW I just used snipping tool to black out my serial number and IMEI number if that somehow made you think it's a Dev Ed (which I hope it didn't)
I traded my Note 3 for this yesterday expecting to get a normal used M8
I would have never expected to have gotten a used Dev Ed.
Also, related to the backup (because I'd prefer to not relock the bootloader or lose my stuff)
There isn't a boot.img with the exact number of 3.28.1540.5
Will one of the 3.28.401.x work? (There's three, each ending with either 6, 7 or 9)
Click to expand...
Click to collapse
You can tell it's a Dev edition by the CID, yours is BS_US002 so it does indeed appear to be a Dev edition M8. As for your firmware question, use the link ckpv5 gave you, scroll down until you see "all other CID's" and tap the button below it. Scroll all the way to the bottom of that list to find what you are looking for. Good luck!
Sent from my A0001 using XDA Free mobile app
rdar_93 said:
WOW ARE YOU SERIOUS?!?!?
I own a Dev Ed M8??
I also want to know if it's necessary to flash the stock recovery, seeing that I may inevitably go back to the GPE rom I'm running right now.
Click to expand...
Click to collapse
Your CID and MID tell that you have a Dev Ed
You need the stock recovery only for OTA updates.
Yours currently is on 4.4.4 hboot.
You need to update to lollipop 5.0.1 before you can run a 5.0.1 GPE ROM for top performance. Anyway it's your choice.
ckpv5 said:
Your CID and MID tell that you have a Dev Ed
You need the stock recovery only for OTA updates.
Yours currently is on 4.4.4 hboot.
You need to update to lollipop 5.0.1 before you can run a 5.0.1 GPE ROM for top performance. Anyway it's your choice.
Click to expand...
Click to collapse
Wow thanks a lot! I really do appreciate your help.
I am successfully on the Stock 5.0.1 official update as of right now, with TWRP and root access.
I can't wait to see what Sense 6 has come to. The last one I used was 4.1 on my Amaze, and even then I think it was 3.6 based.
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.
Alright, I will start at the beginning. I plugged my phone into my PC. HTC Sync manager popped up and told me there was an update for my device. So I was excited knowing it was the Marshmallow update. Everything was going smooth until my cable disconnected while it was installing. It failed and my phone was doing nothing. So like an idiot, I rebooted it.. Now my phone will not go past the HTC logo on boot. I tried wiping the cache partition from Android Recovery but no luck. I'm not really sure what to do at this point. My phone was not rooted, and it is *Locked*. I just want my phone back.. Any help would be so much appreciated, because I'm pretty unsure of what to do.
By the way I am not worried about saving what is on the phone. It's the HTC One M8 (Verizon).
Hi,
I'm a beginner here myself but based on what I read lately it might be possible to go into fastboot mode and flash a Lollipop RUU file.
You'll need a couple of tools on your PC (adb and fastboot) and a step by step guide, both easy to find with a quick search. The harder part is to locate the appropriate file to flash, at least I have trouble with that piece...
Good luck !
Gnondpom said:
it might be possible to go into fastboot mode and flash a Lollipop RUU file.
Click to expand...
Click to collapse
Depends on how far it got in the update. If enough of the MM update installed, LP may constitute a "downgrade", which is not allowed unless you have s-off. In that case, OP may need to use the Marshmallow RUU. But I agree, that RUU is the best bet. RUU will wipe the phone, but I think we're past the point of trying to recovery data at this point, anyway.
TO the OP, what does it say for OS number on the bootloader screen?
Presumably, the phone is s-on, as it sounds like it was never modified?
The Verizon RUUs are here: http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
Another option to flashing the RUU using fastboot, is to put the RUU zip on an SD card (if you have one) and flash. Instructions are in the link (Option 2). This is probably easiest of the options (again, assuming you have an SD card), especially if you don't have fastboot setup, and aren't familiar with it).
redpoint73 said:
Depends on how far it got in the update. If enough of the MM update installed, LP may constitute a "downgrade", which is not allowed unless you have s-off. In that case, OP may need to use the Marshmallow RUU. But I agree, that RUU is the best bet. RUU will wipe the phone, but I think we're past the point of trying to recovery data at this point, anyway.
TO the OP, what does it say for OS number on the bootloader screen?
Presumably, the phone is s-on, as it sounds like it was never modified?
The Verizon RUUs are here: http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
Another option to flashing the RUU using fastboot, is to put the RUU zip on an SD card (if you have one) and flash. Instructions are in the link (Option 2). This is probably easiest of the options (again, assuming you have an SD card), especially if you don't have fastboot setup, and aren't familiar with it).
Click to expand...
Click to collapse
OS # is (6.21.605.3) The update was just about finished before it disconnected. So I believe you are correct. I don't mind data loss, would rather just get the device functional again.
It is S-ON, it was never modified in any way. I will check out the links and see what I can do. Thank you for all the info!:good:
Good Evening Helpful People,
I'm currently in a predicament with my M9 Dev Edition on trying to upgrade to the latest Android 7 firmware...
I forgot to make a stock backup using TWRP while S-Off to restore a factory state to use the RUU.exe from the HTC site, and I'm having troubles upgrading to 3.35.617.31 to have the "base" to take the 4.14.617.6 RUU.exe successfully.
**I'm currently on 3.35.617.21
*I understand how to change my CID and MID with S-OFF
*I can not find a stock 3.35.617.21 recovery.img to allow the RUU.exe to work
*I have no intentions to turn my S-OFF to S-ON
*I'm un-rooted "TWRP Backup Save" (No SuperSU) with TWRP as my custom recovery
*I can re-root whenever needed.
*ADB and Fastboot drivers are totally fine
I know that there is probably 3 or 4 different ways to go about my problem and I like to be resourceful on my own, but I would super appreciate it if someone here would lead me on the right track!
SeventiesPaintbox
I'm a little confused - what problem are you running into with the Android 7.0 RUU (4.19.617.1.) from the HTC website? A non-stock recovery shouldn't be an obstacle to using a RUU. Assuming you're not worried about your phone being reset to factory*, you can use the RUU executable or install it via the SD card method.
I'm still learning, so maybe I'm missing something obvious - please let me know.
* As you know, your internal memory is wiped and your phone returned to stock system & recovery - but I'm pretty sure you don't lose S-OFF from RUUs. I've used RUUs several times since getting S-OFF and still have it.