Upgrading to stock from custom 4.4.3 ROM via RUU - One (M7) Q&A, Help & Troubleshooting

Hello,
I have a number of questions before I jump in and update my phone, so I'm hoping to get some advice on the best way to upgrade from a 4.4.3 custom rom (ARHD 83.1) to the latest stock (rooted) rom - it looks like the custom 6.0 roms aren't so stable at the moment, so best to avoid them for now?
I'm also looking to update my radio with the hope of getting a better signal, or is the radio not really affected by the rom version? Hoping to get better battery life and general stability too.
I understand that I can't just install a custom 5.0.2 rom (e.g. ARHD 93.0) or custom 6.0 rom via recovery (as I normally would do) because of firmware/radio miss-matches? I need to update this first (must be S_OFF) before I can flash.
Some details:
M7_UL
HTC_039
Unlocked
S-ON
HBOOT-1.44.0000
Current: 6.09.401.11 / 4A.14.3250.13
Carrier: Telstra (AU)
From what I can tell, my two main options are either using ruu.zip/ruu.exe or Guru Reset.
I'm S-ON, so I can use Guru Reset, but I can't seem to find the latest firmware with this.
I understand I can flash ruu.zip/ruu.exe with S-ON if the firmware is newer?
Am I better off going S-OFF now (it's easier while on 1.44?)? Do I need to be S-OFF?
How do I know which firmware version to choose? Can I jump straight to 7.19.401.2?
Will OTA work after this?
Does it matter if I use x.xx.401.x (WWE?) or x.xx.908.x (Optus?) or x.xx.841.x (Telstra??) ... I don't want any carrier software, but I would like the best radio for my carrier (Telechoice/Telstra).
I understand that HTC_039 is Optus, but my current firmware is using WWE - these don't have to match?
So, if I need to do S-OFF, should I just use revone using this method https://www.youtube.com/watch?v=J4BWxtjaamM and this file http://forum.xda-developers.com/showpost.php?p=63834144&postcount=6943 .. or using the toolkit http://forum.xda-developers.com/showthread.php?t=2364445 ?
Then, which is the preference for ruu.zip vs ruu.exe? e.g. https://www.youtube.com/watch?v=ybu7fZa41so
Once all is installed, I can re-root and install xposed for stock rom tweaks? I may or may not need to reinstall TWRP...?
I'd just like to be sure of what I'm doing before I start as there's so much information out there and I don't want to brick my phone!
Any help and advice is much appreciated - thank you!

Finner42 said:
Hello,
I have a number of questions before I jump in and update my phone, so I'm hoping to get some advice on the best way to upgrade from a 4.4.3 custom rom (ARHD 83.1) to the latest stock (rooted) rom - it looks like the custom 6.0 roms aren't so stable at the moment, so best to avoid them for now?
I'm also looking to update my radio with the hope of getting a better signal, or is the radio not really affected by the rom version? Hoping to get better battery life and general stability too.
I understand that I can't just install a custom 5.0.2 rom (e.g. ARHD 93.0) or custom 6.0 rom via recovery (as I normally would do) because of firmware/radio miss-matches? I need to update this first (must be S_OFF) before I can flash.
Some details:
M7_UL
HTC_039
Unlocked
S-ON
HBOOT-1.44.0000
Current: 6.09.401.11 / 4A.14.3250.13
Carrier: Telstra (AU)
From what I can tell, my two main options are either using ruu.zip/ruu.exe or Guru Reset.
I'm S-ON, so I can use Guru Reset, but I can't seem to find the latest firmware with this.
I understand I can flash ruu.zip/ruu.exe with S-ON if the firmware is newer?
Am I better off going S-OFF now (it's easier while on 1.44?)? Do I need to be S-OFF?
How do I know which firmware version to choose? Can I jump straight to 7.19.401.2?
Will OTA work after this?
Does it matter if I use x.xx.401.x (WWE?) or x.xx.908.x (Optus?) or x.xx.841.x (Telstra??) ... I don't want any carrier software, but I would like the best radio for my carrier (Telechoice/Telstra).
I understand that HTC_039 is Optus, but my current firmware is using WWE - these don't have to match?
So, if I need to do S-OFF, should I just use revone using this method https://www.youtube.com/watch?v=J4BWxtjaamM and this file http://forum.xda-developers.com/showpost.php?p=63834144&postcount=6943 .. or using the toolkit http://forum.xda-developers.com/showthread.php?t=2364445 ?
Then, which is the preference for ruu.zip vs ruu.exe? e.g. https://www.youtube.com/watch?v=ybu7fZa41so
Once all is installed, I can re-root and install xposed for stock rom tweaks? I may or may not need to reinstall TWRP...?
I'd just like to be sure of what I'm doing before I start as there's so much information out there and I don't want to brick my phone!
Any help and advice is much appreciated - thank you!
Click to expand...
Click to collapse
Please post the output of "fastboot getvar all" (remove your imei/sn before posting)

alray said:
Please post the output of "fastboot getvar all" (remove your imei/sn before posting)
Click to expand...
Click to collapse
I've just spent the last hour trying to get fastboot working on Windows 10 with no luck (adb was working, but not any more). Is there any other way of getting that information?
I'll keep trying anyway, I'll need it. . .
Edit:
Just got it working thanks to this Win 10 reg edit - http://forum.xda-developers.com/showpost.php?p=63454708&postcount=59
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.980.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ****
(bootloader) imei: ****
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__039
(bootloader) battery-status: good
(bootloader) battery-voltage: 4282mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT

You could use the 1.29.980.2 CWM backup to restore your phone back to stock and from there you could either attempt to s-off your phone using Revone and do whater you want (like converting your phone to another version) or simply update your phone until you are on the latest version for your phone.
http://www.htc1guru.com/dld/m7-cwm-nandroid-backup-cid-htc__039-1-29-980-2-2013-05-11-zip/

alray said:
You could use the 1.29.980.2 CWM backup to restore your phone back to stock and from there you could either attempt to s-off your phone using Revone and do whater you want (like converting your phone to another version) or simply update your phone until you are on the latest version for your phone.
http://www.htc1guru.com/dld/m7-cwm-nandroid-backup-cid-htc__039-1-29-980-2-2013-05-11-zip/
Click to expand...
Click to collapse
Thanks for this. I'm currently running TWRP, but it looks like there's only a CWM version for this.
So, do I need to S-OFF? If I do this, and don't S-OFF, do I just get all the OTA updates, or is there something else that needs to be done for that to work?
To confirm, I can't just install the latest 5.0.2 ARHD over the top (with full wipe), because of firmware differences?

Finner42 said:
Thanks for this. I'm currently running TWRP, but it looks like there's only a CWM version for this.
So, do I need to S-OFF? If I do this, and don't S-OFF, do I just get all the OTA updates, or is there something else that needs to be done for that to work?
To confirm, I can't just install the latest 5.0.2 ARHD over the top (with full wipe), because of firmware differences?
Click to expand...
Click to collapse
You need to use CWM recovery to restore CWM backup so you'll need to flash that recovery. You don't need S-OFF to flash the recovery, restore the backup and update your phone but if you want it, better to do it before updating. After restoring the backup, you'll need to flash back the stock recovery over CWM so you can install ota update. The stock recovery can be extracted from the ota update, download it and select "install later". Once downloaded, go to your Downloads folder and copy the zip file starting with "ota" to your computer. Open the zip file and you'll see another zip named "firmware.zip", extract that one to your desktop and finally open the firmware.zip file and extract the recovery.img file from it. This file is the stock recovery to be flashed before trying to install the previously downloaded ota update.
You can't install latest ROM (sense + lollipop) because your firmware is to old. Doesn't matters if its a x.xx.401.x or x.xx.780.x base but it must be 7.xx.xxx.x

Awesome, thanks for the guidance
Again, to clarify - is S-OFF something I need, or do the risks outweigh the benefits, once everything is up to date? Once S-OFF, this will remain S-OFF? Best to do this first while still on a rooted ROM, before loading stock nandroid?
Sorry for all the questions, but your help has been great, thanks!
Sent from my HTC One using Tapatalk

Related

[Q] Custom Rom/Recovery w/o tampered message?

Hello.
I just got my One, upgraded from the One X
I am very skilled regarding rooting, flashing custom roms, recoveries, etc. I just have a quick question.
Is it possible to install custom rom, custom recovery and turn the phone S-OFF - WITHOUT getting the tampered message?
- If no, tell me that
- If yes, read on
Second case: Does this RRU match my M7?
First of all, what have i done myself:
- Unlocked bootloader
- Installed TWRP
- Made a nandroid backup
- Relocked bootloader because i want to flash [ROM] Android Revolution HD 3.2 Google Edition | High Quality & Performance | Android 4.3 Jelly Bean | 2.14.1700.15
- Flashed latest firmware for my phone - 2.24.401.1 (the thread above states that its not needed but recommended)
- Got the TAMPERED message and wants to get rid of that (and return from HBOOT 1.54 to original HBOOT 1.44)
In order to get rid of that message, this guide state i must use "method 2", and as part of that method 2, i must find the correct RRU.
The following is the output of getvar all before firmware update:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.16
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: REMOVED
(bootloader) imei: REMOVED
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 3980mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.043s
Click to expand...
Click to collapse
And this is getvar all after firmware update:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: REMOVED
(bootloader) imei: REMOVED
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4010mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.043s
Click to expand...
Click to collapse
Will this RRU be for my phone: RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe
- I found it here: http://www.androidruu.com/index.php?developer=M7
I chose it as its the RRU for the M7 Europe model that gets closest to my original main version (1.29.401.16 vs 1.28.401.7), also the radio in that RRU is just a tad older than my own original radio.
Also, is it possible to downgrade like that (im quite certain it is, just want to be sure).
Kind Regards
TwinAdk
Wait, you was in 1.44 hboot and now you're on 1.54?
If yes, you can't get the s-off.
The tools for the S-OFF are working only in 1.44 hboot, and, i if read right, now you have the 1.54 and you can do nothing...
****, you are kidding me, right? And RUU downgrade is not an option? That will downgrade my RUU too.
Aside from S-OFF being down the toilet, are there any other downsides to Hboot 1.54?
TwinAdk said:
****, you are kidding me, right? And RUU downgrade is not an option? That will downgrade my RUU too.
Aside from S-OFF being down the toilet, are there any other downsides to Hboot 1.54?
Click to expand...
Click to collapse
You can't downgrade with any ruu if you don't have the S-OFF...
Nope, but now you can't remove the ****Tampered**** line and you can't get the S-OFF...
Guich said:
You can't downgrade with any ruu if you don't have the S-OFF...
Nope, but now you can't remove the ****Tampered**** line and you can't get the S-OFF...
Click to expand...
Click to collapse
God dammit.. Well, are there any downsides regarding custom roms, to having the 1.54 hboot? Also, is it likely S-OFF will ever be avail. with 1.54?
TwinAdk said:
God dammit.. Well, are there any downsides regarding custom roms, to having the 1.54 hboot? Also, is it likely S-OFF will ever be avail. with 1.54?
Click to expand...
Click to collapse
No, you can flash all rom, kernel, mod, theme that you want.
For the S-OFF, no, devs said that they will work on the tool for the S-OFF when the new update form htc will come with the 1.55 hboot
Guich said:
No, you can flash all rom, kernel, mod, theme that you want.
For the S-OFF, no, devs said that they will work on the tool for the S-OFF when the new update form htc will come with the 1.55 hboot
Click to expand...
Click to collapse
So when 1.55 hboot arrives, work will start for S-OFF for that HBOOT? Any ETA on 1.55?
TwinAdk said:
So when 1.55 hboot arrives, work will start for S-OFF for that HBOOT? Any ETA on 1.55?
Click to expand...
Click to collapse
Atm there are some leaks of android 4.3 and new hboot 1.55, but this isn't the update that we will get.
For the question, yes
Guich said:
Atm there are some leaks of android 4.3 and new hboot 1.55, but this isn't the update that we will get.
For the question, yes
Click to expand...
Click to collapse
Okay, thanks
Now that i booted the phone, my storage is not available and wifi does not turn on (it says enabling, but thats all) - great start! Any idea why?
Ill look into it tomorrow my self, im off to bed now... Guess the One X will be in service for a few more days...
EDIT: Im on a firmware thats NOT for the android version i have, i think thats the problem. I guess ill have to sideload the custom rom running 4.3, and get it running that way.
Freaking hell, no S-OFF!
You relocked your bootloader after the flash of the rom?
If yes, you have to unlock this, reflash the rom and the kernel, and do a wipe of cache and dalvik-cache...
Guich said:
You relocked your bootloader after the flash of the rom?
If yes, you have to unlock this, reflash the rom and the kernel, and do a wipe of cache and dalvik-cache...
Click to expand...
Click to collapse
I cannot flash the rom as my SD is unavail... Is it an option to sideload the ROM?
TwinAdk said:
I cannot flash the rom as my SD is unavail... Is it an option to sideload the ROM?
Click to expand...
Click to collapse
Flash the stock recovery and then do a factory reset in bootloader, this will fix your sd.
After flash a custom recovery and try to use the sideload
Guich said:
Flash the stock recovery and then do a factory reset in bootloader, this will fix your sd.
After flash a custom recovery and try to use the sideload
Click to expand...
Click to collapse
Hello.
I flashed the stock recovery, and factory reset the phone. It rebooted during factory reset (of course), and booted normally afterwards. Wifi and storage did however still not work.. From within android im told that the storage is "Unavailable" (ill post screenshots later) - and from TWRP, i am told that i have "Internal storage" of 28xxx mb available (not sure about the excact size, around 28 gb) - but i cannot mount it and make it available from windows.
I can see the phone in windows, as a HTC media unit, and browse the content (storage -> legacy -> more folders -> root of SD card with folders like "downloaded" etc - default folders). But when i get there i cannot create folders or files, i can only view the content.....?
1. I cannot downgrade with RRU, since im S-ON
2. My Wifi and storage SEEMS broke (i suspect its because i flashed the firmware mentioned earlier, and my android version is not happy with that firmware - someone with more insight are welcome to comment on my guessing here)
3. Sideloading the rom i want to use (based on android 4.3) seems to be the only option - but can i sideload when my SD is not available in recovery?
Starting to worry a bit here
And thank you for all your help so far :good: I didnt get to say that last evening.. Appriciate!
Kind Regards
Hello sir,
first of all, let me say you screwed up already when not researching XDA before doing an update. Since i have done so myself numerous times, let me advise you to make it a habit, when buying a new phone to specifically research downsides of updates before accepting any.
Particularly in the HTC world, it has become a common thing to only gain S-OFF while the phone is in early software states and loose this ability towards later releases. Until now, many HTC phones i have had to deal with, had issues with disabling security on later firmwares.
Then, the storage problem you describe could possibly be related to something i have seen a fair few times. What Guich told you to do is usually the ultimate trick to get it back working. But let me ask this first: were you able to access storage from windows normally before the update? Or could you also face a driver issue?
OK. Guich's comment did not help. You flashed the stock recovery from the firmware you run. Then you ran Factory Reset from within Bootloader? Or from within android? If the latter, try the first...
I will be putting up stock recoveries from different RUU's soon on my thread here: http://forum.xda-developers.com/showthread.php?t=2316726 but you also find them on the forum already by searching. Try different stock recoveries and factory reset from Bootloader.
Then, if that doesn't help, try to run the OTA 2.24 (which already runs on your phone!) again by booting into bootloader, then picking "Fastboot" there (use volume down and up to navigate and power to confirm) and then going to your adb/fastboot with a command window. Oh, connect phone to PC of course
Lets say you have adb and fastboot plus the dll files in C:\Android. Open a CMD window and do "CD C:\Android" to go there.
there, run "fastboot oem rebootRUU" (type exactly as i do here, omit the quotes though).
then, copy and paste the OTA file (obtain HERE) to the same folder (C:\Android).
For easier typing in CMD, rename the OTA to something short and simple like test.zip or whatever.
then go back to your CMD Window and type in "fastboot flash zip test.zip"
Since its the same hboot and firmware in the OTA like you have on phone and since this package is official and signed, your phone ---should--- accept the flash. If not (maybe because you got the wrong model ID or wrong CID) i wouldn't really know how to proceed. But you DID accept that OTA before so it MUST be for your phone or else it wouldn't have flashed in the first place.
If it flashes fine, boot your phone up and check if it fixed everything.
If not, run the check for software update in Settings/Info/ and see if there is already an official OTA for your phone available that brings you past the 2.24. If not, download one of the inofficial OTA's and --- hope --- that you can flash it. Like 3.18 or 3.22. The first is for Asia/Taiwan though and will almost certainly NOT flash on your phone and the second is BrightstarUS and for the DEV edition and will also almost certainly not flash. But its worth a try.
beyond that, i have no more valuable tips. Only thing I would try is to flash CWM and do a clear storage, wipe data, wipe everything there. But be sure to have your nandroid ready if you do that. CWM uses a slightly different formatting method so it could possibly correct issues. In the past, i have read about screwed up SDcards related to CWM formatting more often than those that got screwed up by TWRP though. So its not exactly ideal to play with CWM on a phone that has already issues with its partition. But if i was desperate, i would do it anyway.
If that doesnt help or make it worse, do the very same thing on TWRP, pick the "wipe Data" option which prompts you to type "yes" into an input line. This will once again format your SD with a different method. It could possible correct this problem.
DO NOT attempt to screw around with the SD Partition using tools like MiniTool or EASUS if you can access the sd from them at all!
The SD Card is an EXT4 file system and cannot be formatted with FAT or NTFS from windows. If you do that, the phone wont work at all anymore. The exact parameters to format the partition externally are not known to me and i doubt you can address the partition from within windows at all. Maybe it works under linux...
Sorry. Cant be much help here. If that all doesnt work, just flash stock recovery back and restore your stock nandroid and send it in for repair. Them service dudes will have the right RUU and fix it for you.
[EDIT]
Oh and before i forget: if you can fix it with these tips, you owe me one
You have to flash Team Venom's ViperOne then instead of ARHD! :laugh:
Aroma installer is running now!! So excited to see the result! I sideloaded the zip, via adb sideload Nice short article on it here: http://teamw.in/ADBSideload
Will return with outcome :highfive::fingers-crossed::fingers-crossed::fingers-crossed:
EDIT: Its back! Running custom rom with sd card avail and wifi working! Pew, saved by adb sideload, increddible!

[Q] HTC One returning to stock questions

Hello everyone,
I'm pretty new to whole rooting and stuff so excuse me for my probably noob and dumb questions..
I own a HTC One for a year now I believe, and I wanted to give the rooting thing a try.
So I unlocked my One, and installed a custom recovery (TWRP).
I didn't do alot with it, had a stock version af android with sense, no custom roms or anything, only used root acces for the cerberus app.
The other day HTC released a new version af the stock software, I believe 4.19.401.11.
Since I'm not doing anything with the unlocked phone I want to get it back to stock again.
I am on android 4.4 with sense 5.5 now, android version 4.19.401.9, hboot 1.56
My fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:-
(bootloader) imei: -
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 4135mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
I found this guide to get back to stock: http://www.htc1guru.com/guides/return-stock-guide/
There it works with S-off, with rumrunner to get s-off but I read that rumrunner wont work with hboot 1.56, sadly I have 1.56..
In that guide you have to get s-off, downgrade to another hboot (1.44) and use a RUU with android version 1.28 or 1.29 to go to stock again.
But, in another topic I found this:
herwegan said:
@crushalot hey mate did you realize that there are now 4.19.xxx RUU's available on http://androidruu.com/?developer=M7# ?
for those who are interested: here's the link to the WWE 4.19.401.9 RUU
http://androidruu.com/getdownload.p...10.38r.1157.04L_release_353069_signed_2-1.exe
Click to expand...
Click to collapse
That is an RUU for exactly my phone I believe.
So now my question: Can I run that RUU, in the way that is written in the htc1guru return to stock guide (via fastboot) and go back to stock again? With a (re)locked bootloader, and receive OTA updates again?
I hope my question and all the information I have given is clear! If not feel free to ask me below!
Greetings.
N3Gruj1989 said:
Hello everyone,
I'm pretty new to whole rooting and stuff so excuse me for my probably noob and dumb questions..
I own a HTC One for a year now I believe, and I wanted to give the rooting thing a try.
So I unlocked my One, and installed a custom recovery (TWRP).
I didn't do alot with it, had a stock version af android with sense, no custom roms or anything, only used root acces for the cerberus app.
The other day HTC released a new version af the stock software, I believe 4.19.401.11.
Since I'm not doing anything with the unlocked phone I want to get it back to stock again.
I am on android 4.4 with sense 5.5 now, android version 4.19.401.9, hboot 1.56
My fastboot getvar all:
I found this guide to get back to stock: http://www.htc1guru.com/guides/return-stock-guide/
There it works with S-off, with rumrunner to get s-off but I read that rumrunner wont work with hboot 1.56, sadly I have 1.56..
In that guide you have to get s-off, downgrade to another hboot (1.44) and use a RUU with android version 1.28 or 1.29 to go to stock again.
But, in another topic I found this:
That is an RUU for exactly my phone I believe.
So now my question: Can I run that RUU, in the way that is written in the htc1guru return to stock guide (via fastboot) and go back to stock again? With a (re)locked bootloader, and receive OTA updates again?
I hope my question and all the information I have given is clear! If not feel free to ask me below!
Greetings.
Click to expand...
Click to collapse
You are still essentially stock, you will only need to flash the stock recovery from 4.19.401.9 , unfortunately I did a quick google and couldn't fine one. If you have the OTA or ruu you can extract the recovery.img to use. unlocked bootloader and root is fine. Then when the version .11 is released by your carrier you will be able to install.
mb_guy said:
You are still essentially stock, you will only need to flash the stock recovery from 4.19.401.9 , unfortunately I did a quick google and couldn't fine one. If you have the OTA or ruu you can extract the recovery.img to use. unlocked bootloader and root is fine. Then when the version .11 is released by your carrier you will be able to install.
Click to expand...
Click to collapse
Hi mb_guy, i have a twrp backup which i can restore, which could allow me to return to stock with superuser root access.
If i flash a stock recovery, will it remove my root access and receive future OTA? (if i am not mistaken, i tried flashing the stock recovery, and relocked the bootloader, but i just can't remove the superuser app :crying: )
Thanks.
below are my phone informations :
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.707.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 4123mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-59adc32b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
mb_guy said:
You are still essentially stock, you will only need to flash the stock recovery from 4.19.401.9 , unfortunately I did a quick google and couldn't fine one. If you have the OTA or ruu you can extract the recovery.img to use. unlocked bootloader and root is fine. Then when the version .11 is released by your carrier you will be able to install.
Click to expand...
Click to collapse
I have found the RUU of 4.19.401.9 (it is in the link i posted in my opening post, from androidruu).
(http://androidruu.com/getdownload.p...10.38r.1157.04L_release_353069_signed_2-1.exe)
I found a guide to extract the rom.zip from a RUU file, but it wont work for me. Can someone extract the rom.zip file for me and upload it here?
Only flashing the recovery file sounds like loads easyer than the entire guide i found by htc1guru.
And what if i want to re-lock the bootloader and get rid of root? Can i do that too?
N3Gruj1989 said:
I have found the RUU of 4.19.401.9 (it is in the link i posted in my opening post, from androidruu).
(http://androidruu.com/getdownload.p...10.38r.1157.04L_release_353069_signed_2-1.exe)
I found a guide to extract the rom.zip from a RUU file, but it wont work for me. Can someone extract the rom.zip file for me and upload it here?
Only flashing the recovery file sounds like loads easyer than the entire guide i found by htc1guru.
And what if i want to re-lock the bootloader and get rid of root? Can i do that too?
Click to expand...
Click to collapse
You don't want rom.zip you want recovery.img it's likely in the firmware folder. You should be able to unroot from twrp. You can re lock the boot loader, but it will say relocked, I would just leave it unlocked.
N3Gruj1989 said:
I have found the RUU of 4.19.401.9 (it is in the link i posted in my opening post, from androidruu).
(http://androidruu.com/getdownload.p...10.38r.1157.04L_release_353069_signed_2-1.exe)
I found a guide to extract the rom.zip from a RUU file, but it wont work for me. Can someone extract the rom.zip file for me and upload it here?
Only flashing the recovery file sounds like loads easyer than the entire guide i found by htc1guru.
And what if i want to re-lock the bootloader and get rid of root? Can i do that too?
Click to expand...
Click to collapse
Ok it's easy
Retry run that ruu exe file goto temp folder in c-Windows- user- app data - local - temp find in some folders you will get it but it's not worth it as it's encrypted so next time you will ask how to decrypt it
So better Google HTC One stock recovery download it flash it
2 if you want unroot mostly super user or rooting apps have methods in their settings try them
3 locking boot loader is last step after recovery flash
Unlocked bootloader not prevent future OTA
So no need for relock bootloader
OTA need stock recovery + unmodified system
HTC One 1.56 S-Off MaximusHD 33
mb_guy said:
You don't want rom.zip you want recovery.img it's likely in the firmware folder. You should be able to unroot from twrp. You can re lock the boot loader, but it will say relocked, I would just leave it unlocked.
Click to expand...
Click to collapse
But the recovery.img file is in the rom.zip file correct?
So i have to extract the rom.zip file out of the RUU first to get the recovery.img out of the rom.zip file.
Or can it be done a much easyer way?
yatin kumar said:
Ok it's easy
Retry run that ruu exe file goto temp folder in c-Windows- user- app data - local - temp find in some folders you will get it but it's not worth it as it's encrypted so next time you will ask how to decrypt it
So better Google HTC One stock recovery download it flash it
2 if you want unroot mostly super user or rooting apps have methods in their settings try them
3 locking boot loader is last step after recovery flash
Unlocked bootloader not prevent future OTA
So no need for relock bootloader
OTA need stock recovery + unmodified system
HTC One 1.56 S-Off MaximusHD 33
Click to expand...
Click to collapse
I googled HTC One stock recovery, but i didn't find a recovery for my HTC One build version, or are all the recovery.img the same?
Because I need a recovery.img for the 4.19.401.9 HTC_E11 (NL) version.
N3Gruj1989 said:
But the recovery.img file is in the rom.zip file correct?
So i have to extract the rom.zip file out of the RUU first to get the recovery.img out of the rom.zip file.
Or can it be done a much easyer way?
Click to expand...
Click to collapse
You can't get the recovery from the rom.zip as the zip is encrypted.
I downloaded the 4.19.401.9 firmware.zip and extracted the recovery from it.
Here is the recovery : http://sourceforge.net/projects/htcone/files/Recovery/4.19.401.9/recovery.img/download
Now you have two options:
With the RUU that you have
1. relocked the bootloader
2. run the RUU to go back to stock
3. do the OTA
With the recovery only
1. fastboot flash the recovery
2. not necessary to remove the SuperSU (but you will lose root after OTA)
3. or remove root (open the SuperSU app, - settings - scroll down - select Full unroot if you think it's better to remove it before OTA
4. do the OTA
Remove root by flashing stock firmware
Hi guys, i did some searching and found this thread http://forum.xda-developers.com/showthread.php?t=1773659
according to this thread if i flash in stock firmware it will remove the root?
So my question is, if i restore my phone to the rooted stock state > relock the bootloader > flash in the stock firmware, in theory it should return the phone to stock state right? just to confirm if the above thread works for the HTC One
Thanks.
ckpv5 said:
You can't get the recovery from the rom.zip as the zip is encrypted.
I downloaded the 4.19.401.9 firmware.zip and extracted the recovery from it.
Here is the recovery : http://sourceforge.net/projects/htcone/files/Recovery/4.19.401.9/recovery.img/download
Now you have two options:
With the RUU that you have
1. relocked the bootloader
2. run the RUU to go back to stock
3. do the OTA
With the recovery only
1. fastboot flash the recovery
2. not necessary to remove the SuperSU (but you will lose root after OTA)
3. or remove root (open the SuperSU app, - settings - scroll down - select Full unroot if you think it's better to remove it before OTA
4. do the OTA
Click to expand...
Click to collapse
Thank you very much!
When I unlocked, rooted and installed the TWRP recovery I lost the stock flashlight app and calculator app and some others.
With the RUU i will get them back i think, with the other option, flashing recovery it wont return right? And after the OTA?
Is there any risk in running that RUU?
N3Gruj1989 said:
Thank you very much!
When I unlocked, rooted and installed the TWRP recovery I lost the stock flashlight app and calculator app and some others.
With the RUU i will get them back i think, with the other option, flashing recovery it wont return right? And after the OTA?
Is there any risk in running that RUU?
Click to expand...
Click to collapse
You should have said this earlier. When you lost the some apps that reside in data/preload folder means you don't already have a proper stock, OTA most probably will be a fail attempt.
Flashing the recovery alone cannot guarantee a successful OTA update due to those missing apps.
The best option that you have is run the RUU unless you can find any nandroid backup for the current ROM.
For me, I will choose to run the RUU as that is always the best option when it is the right RUU for your device.
Make a backup to PC all your storage content in case you lose them by running the RUU (but unlikely you will lose them)
With the RUU ... the procedure is :
1- in fastboot mode - relock the bootloader : run command fastboot oem lock
2- in fastboot mode - flash/run/double click the RUU; follow the updater instruction - next,update,bla,bla,bla until it finish
---------- Post added at 07:16 PM ---------- Previous post was at 07:13 PM ----------
SiaoNang said:
Hi guys, i did some searching and found this thread http://forum.xda-developers.com/showthread.php?t=1773659
according to this thread if i flash in stock firmware it will remove the root?
So my question is, if i restore my phone to the rooted stock state > relock the bootloader > flash in the stock firmware, in theory it should return the phone to stock state right? just to confirm if the above thread works for the HTC One
Thanks.
Click to expand...
Click to collapse
If it is the firmware.zip alone, no .. it won't remove your root app.
When people say stock firmware it is always mean stock ROM.
To remove root, just simply select Full unroot in SuperSU settings. (asumming your rooting app is SuperSU as shown in that thread).
Thanks everyone for their help!
Everything worked fine, I'm back to stock now and just updated the OTA !

[Q] fastboot getvar all, version-main empty?

I tried to find my firmware version but when i type gatvar all in fastboot there is nothing in version-main field. How can I find my firmware version?
snebojsa said:
I tried to find my firmware version but when i type gatvar all in fastboot there is nothing in version-main field. How can I find my firmware version?
Click to expand...
Click to collapse
If you have a file manager with root access you can look at your /system/build.prop and look under ro.aa.romver will give you which version you have.
snebojsa said:
I tried to find my firmware version but when i type gatvar all in fastboot there is nothing in version-main field. How can I find my firmware version?
Click to expand...
Click to collapse
which HBOOT version do you have, its missing off your output ?
at the moment based on your modelid and your cidnum you have something along the lines of a 401 firmware, need the HBOOT version to determine which exact version though.
majmoz said:
If you have a file manager with root access you can look at your /system/build.prop and look under ro.aa.romver will give you which version you have.
Click to expand...
Click to collapse
Seanie280672 said:
which HBOOT version do you have, its missing off your output ?
at the moment based on your modelid and your cidnum you have something along the lines of a 401 firmware, need the HBOOT version to determine which exact version though.
Click to expand...
Click to collapse
At build.prop under ro.aa.romver is 1.54.401.5
My hboot is 1.57. Phone was officially updated to Sense6 and hboot 1.57, if it helps. Then I unlocked and s-offed it and install custom rom.
My question is this:
I looked this thread: http://forum.xda-developers.com/showthread.php?t=2485651 (Firmware with modified HBOOT, (No Red warning))
There is lot of files for specific firmware versions,
6.06.401.1
5.11.1540.9
4.19.401.11
4.19.401.9
4.19.401.8
4.19.1540.4
3.62.401.1 etc...
but there is nothing for my firmware. Am I missing something?
snebojsa said:
At build.prop under ro.aa.romver is 1.54.401.5
My hboot is 1.57. Phone was officially updated to Sense6 and hboot 1.57, if it helps. Then I unlocked and s-offed it and install custom rom.
My question is this:
I looked this thread: http://forum.xda-developers.com/showthread.php?t=2485651 (Firmware with modified HBOOT, (No Red warning))
There is lot of files for specific firmware versions,
6.06.401.1
5.11.1540.9
4.19.401.11
4.19.401.9
4.19.401.8
4.19.1540.4
3.62.401.1 etc...
but there is nothing for my firmware. Am I missing something?
Click to expand...
Click to collapse
Your firmware is 5.11.401.??, you can flash any of those firmwares above, but never go s-on, they will lead to an instant brick due to modified hboot
Or see here for original firmwares http://forum.xda-developers.com/showthread.php?t=2316726
Seanie280672 said:
Your firmware is 5.11.401.??, you can flash any of those firmwares above, but never go s-on, they will lead to an instant brick due to modified hboot
Or see here for original firmwares http://forum.xda-developers.com/showthread.php?t=2316726
Click to expand...
Click to collapse
How do you know my firmware version, I can't see it?
So, if I want someday to go back s-on (for warranty) I could flash back original hboot and then go to s-on? But I don't think I will flash this modified hboot, it is only for removing red warning text that is seen only when reboot phone, don't bother me that much to mess around with possibly risky staff.
snebojsa said:
How do you know my firmware version, I can't see it?
So, if I want someday to go back s-on (for warranty) I could flash back original hboot and then go to s-on? But I don't think I will flash this modified hboot, it is only for removing red warning text that is seen only when reboot phone, don't bother me that much to mess around with possibly risky staff.
Click to expand...
Click to collapse
I can tell by your cid, mid and hboot version
Seanie280672 said:
I can tell by your cid, mid and hboot version
Click to expand...
Click to collapse
Ok, but on that site with modified hboots there is no 5.11.401 firmware? Newest Firmware is 6.06.401.1 and previously was 5.11.1540.9. If I updated my phone with officially update, like I was, suppose i would have 6.06.401.1?
snebojsa said:
Ok, but on that site with modified hboots there is no 5.11.401 firmware? Newest Firmware is 6.06.401.1 and previously was 5.11.1540.9. If I updated my phone with officially update, like I was, suppose i would have 6.06.401.1?
Click to expand...
Click to collapse
Use the other site I linked if you want official firmware, your current one is on there, the next update that's not been released yet will have 6.06.401.1 in it.
Seanie280672 said:
Use the other site I linked if you want official firmware, your current one is on there, the next update that's not been released yet will have 6.06.401.1 in it.
Click to expand...
Click to collapse
Yes, I see it, thanks for informations :good:
Same issue and confused (more than usual)
My version main is empty as well and I can't figure it out.
build.prop/ro.aa.romver=1.54.401.5
Downloads\HTCOneRoot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.01.20.0515
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: 12312313123
(bootloader) imei: 12345613456123
(bootloader) meid: 123456123456
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4117mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.085s
UNLOCKED
M7_WLS PVT HIP S-OFF RH
CID-SPCS_001
HBOOT-1.57.0000
RADIO -1.01.20.0512
OpenDSP -v32-120.284.0909
OS-
Currently running ViperOne 6.2.1. Tried 7.0 last night but things were a bit funky and didn't have enough time to sort 'em all out. Thought firmware might be an issue, and it seems a bigger issue than I originally thought.
Any and all help appreciated
Version-main empty is TWRP issue, you have to re-flash firmware and flash fixed twrp version. I moved from M7 to M8 so I forgot where to find those files, you have to search it.
On M8 I had the same problem, flashing firmware and fixed twrp solved it. Also, when tried latest Viper rom I was on old firmware and had some odd issues, but since flashed new firmware everything is fine.
Hope I helped you.
OK, so if someone could please confirm or correct me... Being S-Off, I can flash latest M7 FW (6.0.xxx, I think?), then latest TWRP, then re-flash Viper, etc? All without having to unlock, etc, again? Think I'm also going to get custom H-boot (latest Firewater) to rid myself of the dreaded red text. Anyone know, or think, of any issues with that?
Many thanks for any and all assistance.
Sent from my HTCONE using XDA Free mobile app
toad6386 said:
OK, so if someone could please confirm or correct me... Being S-Off, I can flash latest M7 FW (6.0.xxx, I think?), then latest TWRP, then re-flash Viper, etc? All without having to unlock, etc, again? Think I'm also going to get custom H-boot (latest Firewater) to rid myself of the dreaded red text. Anyone know, or think, of any issues with that?
Many thanks for any and all assistance.
Sent from my HTCONE using XDA Free mobile app
Click to expand...
Click to collapse
use the instructions here it works Great
http://forum.xda-developers.com/showthread.php?t=2758956
you can use his files or your own
clsA said:
use the instructions here it works Great
http://forum.xda-developers.com/showthread.php?t=2758956
you can use his files or your own
Click to expand...
Click to collapse
Sorry, I may be noobing out a bit :silly: and venturing outside the Sprint specific forums (couldn't find same issue there), but first link sent me to AT&T ROM thread, which alsi pointed to another thread for firmware which listed several modelid's, none of which matched mine of PN0720000.
I guess I'll keep on looking for firmware for Sprint. I do see that I should be good to go after flashing new FW and recovery and do not have to unlock again, etc.
Thanks! :good:
toad6386 said:
Sorry, I may be noobing out a bit :silly: and venturing outside the Sprint specific forums (couldn't find same issue there), but first link sent me to AT&T ROM thread, which alsi pointed to another thread for firmware which listed several modelid's, none of which matched mine of PN0720000.
I guess I'll keep on looking for firmware for Sprint. I do see that I should be good to go after flashing new FW and recovery and do not have to unlock again, etc.
Thanks! :good:
Click to expand...
Click to collapse
yeah sorry that's my bad ..i totally missed the Sprint part of your thread
clsA said:
yeah sorry that's my bad ..i totally missed the Sprint part of your thread
Click to expand...
Click to collapse
Hey, no worries. You've helped. I didn't make it clear I Sprint. I'm more used to the 3VO forum where there wasn't hardly anything BUT Sprint. I suppose that's what confuses me about this one, with all the variants. Thanks again! :thumbup:
Sent from my HTCONE using XDA Free mobile app

Deleted OS with no backup (Solved)

Hello, guys. How you doing?
UPDATE: it's solved, i got back to stock rom after flashing this: https :// fl1.androidfilehost.com/dl/2k6GKx4IJOgIhD09zRzbzw/1441027324/95897840722641610/Reset_rom_6.07.1540.2.zip?
Now I'm going to do a BACKUP haha
I am with a HTC ONE M7 Internation/Unlocked Soft-Bricked, with no OS... Here are some information:
- Using TWRP 2.8.7.0 custom recovery for M7 (latest version)
- Unlocked bootloader
- Rooted (at least I did it before wipping my OS)
- S-ON!
- HBOOT v.1.57
- Already have ADB/Fastboot on my PC
- Modelid: PN0711000
- Cidnum: HTC__332
Here's my tale:
I tried to install RUU M7 Lollipop ROM, from HTC's website. But, at the very beggining of the instalation (4%), the RUU software said it lost my device. I did it while in fastboot mode, because it was the only way RUU recognized my phone. Then I could not install Lollipop ROM by RUU method, so I decided to flash a Lollipop ROM Unlocked Version for One M7.
I knew that for doing it I would need to install some custom recovery on my phone, unlock its bootloader mode and install on my PC ADB and Fastboot. I did all of this; the bootloader unlocked I did from HTC's website guide. So, I put on my phone a ROM in zip extension, boot it on recovery mode. I read that I should wipe data, cache, calvik cache and, maybe, system. And I did it... with NO BACKUP of original ROM --' I know I was stupid...
So I wipe this partitions, entered Install menu and tried to run instalation of the ROM zip file. It didn't work!!! Some error: "E: error executing updater binary in zip..." And I tried to flash different ROMs, all of them showed this error...
Then now I am with a Soft-Bricked HTC ONE M7 which has no OS. Some pics of my status: https: // w w w .dropbox.com/s/ruyen2ikn0u5i0u/Soft-Bricked%20M7.rar?dl=0
I hope you can help me
Please, help me :crying:
Atadie said:
Hello, guys. How you doing?
I am with a HTC ONE M7 Internation/Unlocked Soft-Bricked, with no OS... Here are some information:
- Using TWRP 2.8.7.0 custom recovery for M7 (latest version)
- Unlocked bootloader
- Rooted (at least I did it before wipping my OS)
- S-ON!
- HBOOT v.1.57
- Already have ADB/Fastboot on my PC
- Modelid: PN0711000
- Cidnum: HTC__332
There's my tale:
I tried to install RUU M7 Lollipop ROM, from HTC's website. But, at the very beggining of the instalation (4%), the RUU software said it lost my device. I did it while in fastboot mode, because it was the only way RUU recognized my phone. Then I could not install Lollipop ROM by RUU method, so I decided to flash a Lollipop ROM Unlocked Version for One M7.
I knew that for doing it I would need to install some custom recovery on my phone, unlock its bootloader mode and install on my PC ADB and Fastboot. I did all of this; the bootloader unlocked I did from HTC's website guide. So, I put on my phone a ROM in zip extension, boot it on recovery mode. I read that I should wipe data, cache, calvik cache and, maybe, system. And I did it... with NO BACKUP of original ROM --' I know I was stupid...
So I wipe this partitions, entered Install menu and tried to run instalation of the ROM zip file. It didn't work!!! Some error: "E: error executing updater binary in zip..." And I tried to flash different ROMs, all of them showed this error...
Then now I am with a Soft-Bricked HTC ONE M7 which has no OS. Some pics of my status: https: // w w w .dropbox.com/s/ruyen2ikn0u5i0u/Soft-Bricked%20M7.rar?dl=0
I hope you can help me
Click to expand...
Click to collapse
post the output of "fastboot getvar all" (remove your imei and serialno)
alray said:
post the output of "fastboot getvar all" (remove your imei and serialno)
Click to expand...
Click to collapse
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.28.3218.04
version-cpld: None
version-microp: None
version-main: 6.15.599.101
version-misc: PVT SHIP S-ON
serialno: ************
imei: ***************
meid: 00000000000000
product: m7_u
platform: HBOOT-8064
modelid: PN0711000
cidnum: HTC__332
battery-status: good
battery-voltage: 4322mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-6d8a0b9b
hbootpreupdate: 11
gencheckpt: 0
Could not get S-OFF
I tried getting S-OFF by Rumrunner method and didn't work :/
Hep me, guys! I really need my One back to life!!! I'm in pain :crying:
Atadie said:
I tried getting S-OFF by Rumrunner method and didn't work :/
Click to expand...
Click to collapse
You can't use rumrunner to achieve s-off on hboot 1.57, only method is Sunshine
Atadie said:
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.28.3218.04
version-cpld: None
version-microp: None
version-main: 6.15.599.101
version-misc: PVT SHIP S-ON
serialno: ************
imei: ***************
meid: 00000000000000
product: m7_u
platform: HBOOT-8064
modelid: PN0711000
cidnum: HTC__332
battery-status: good
battery-voltage: 4322mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-6d8a0b9b
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
There is not much available for 6.15.599.101 version, you'll probably need to use custom roms or convert to another version. There is a 6.15.599.101 ruu available at irfile.com but you will need an acount to download it (paid account) http://www.ir-file.com/portal/index.php?dir=Firmware/HTC/HTC_Android/M7_U/
Atadie said:
UPDATE: it's solved, i got back to stock rom after flashing this: https :// fl1.androidfilehost.com/dl/2k6GKx4IJOgIhD09zRzbzw/1441027324/95897840722641610/Reset_rom_6.07.1540.2.zip?
Now I'm going to do a BACKUP haha
Click to expand...
Click to collapse
This rom is for the Developer edition version CID BS_US001 and MID PN0712000, By flashing this on your phone, you're far from being stock, you will not get any ota updates and be stuck on this version.
alray said:
You can't use rumrunner to achieve s-off on hboot 1.57, only method is Sunshine
There is not much available for 6.15.599.101 version, you'll probably need to use custom roms or convert to another version. There is a 6.15.599.101 ruu available at irfile.com but you will need an acount to download it (paid account) http://www.ir-file.com/portal/index.php?dir=Firmware/HTC/HTC_Android/M7_U/
This rom is for the Developer edition version CID BS_US001 and MID PN0712000, By flashing this on your phone, you're far from being stock, you will not get any ota updates and be stuck on this version.
Click to expand...
Click to collapse
Oh, thanks :/
So, what is the best path to follow to get Lollipop? Should I pay 25 bucks for Sunshine, change my CID and try to flash correct Lollipop rom? Is there another way to get Lollipop rather that one?
Are there so many new and interesting features on Lollipop or should I stay on KitKat 4.4.3? I don't know so many custom good roms; can you recommend me some?
Sorry for asking so much questions. I know, probably I'm bothering you '-'
PS: Now my system asks for an OTA update to Lollipop, but it's not possible... Probably due to what you said about my flashed rom being Developer edition's one.
Atadie said:
Oh, thanks :/
So, what is the best path to follow to get Lollipop? Should I pay 25 bucks for Sunshine, change my CID and try to flash correct Lollipop rom? Is there another way to get Lollipop rather that one?
Click to expand...
Click to collapse
Either pay for sunshine so you can change your CID / MID to convert your phone to another version using a lollipop RUU or pay for an account at ir-file.com so you can download the .599 ruu and then take all ota updates.
Are there so many new and interesting features on Lollipop or should I stay on KitKat 4.4.3?
Click to expand...
Click to collapse
Many ppl likes lollipop and probably as many ppl doesn't like it. I think its better to try it yourself and see what you prefer. Some ppl likes the new features and other ones are complaining about battery drain and lags.
I don't know so many custom good roms; can you recommend me some?
Click to expand...
Click to collapse
All custom roms are good, it all depends what features you need. The best you can do is to read some rom threads and choose one that fit what you need, try it a few days and if not liking it, flash another one. If you want good battery life and no lag, I would recommend GPE roms, if you need what HTC Sense have to offer, then choose a Sense based rom like ARHD, Maximus, InsertCoin, NuSense ....
PS: Now my system asks for an OTA update to Lollipop, but it's not possible... Probably due to what you said about my flashed rom being Developer edition's one.
Click to expand...
Click to collapse
Because your CID and MID doesn't match the rom version you have flashed. Developer edition is for CID BS_US001 and MID PN0712000, yours is HTC__332 and PN0711000, In order to receive ota updates, you must be 100% stock either be flashing the .599 ruu for HTC__332 / PN0711000 or by achieving s-off, changing your CID / MID and flashing another version ruu e.g: changing your cid to BS_US001, your MID to PN0712000 and flashing a dev edition (.1540) RUU.
alray said:
All custom roms are good, it all depends what features you need. The best you can do is to read some rom threads and choose one that fit what you need, try it a few days and if not liking it, flash another one. If you want good battery life and no lag, I would recommend GPE roms, if you need what HTC Sense have to offer, then choose a Sense based rom like ARHD, Maximus, InsertCoin, NuSense ....
Click to expand...
Click to collapse
I was reading about Android Revolution HD, it seems good. I really like Blinkfeed (Highlights) so I guess I wouldn't flash a ROM which doesn't have it. I think ARHD got Blinkfeed, right?
Can I flash this ROM on my phone? As far as you know about my specs.

Please help me revive this sick m7

Hi Guys,
Bought an m7 cheap on ebay. I don't know anything about the history, except to say it's been fiddled with...
It powers up but it won't boot up; it hangs on the HTC logo.
Bootloader's unlocked, it's been rooted... S-ON
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ** edited out **
(bootloader) imei: ** edited out **
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4297mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I'm thinking I should try and take it back to stock, but I don't know where I should go from here and I'm worried I might screw it up.
Any help would be greatly appreciated
Thanks in advance!
Go to RUU mode and flash an RUU. There's a lot of threads explaining how to go to back to stock on this forum. If it still doesn't work, it might be an internal issue like the motherboard.
Can someone please recommend an RUU to go to... I'm just worried if I use the wrong one it will cause more issues. I thought RUUs were dependent on the CID num and as that's been changed to allow custom roms... I'd be happy taking it back to a plain old vanilla HTC / Google - just something to get it back alive.
Thanks
Should also add I can't get s-off... adb devices doesn't show anything... I'm guessing usb debugging wasn't set up
mdb said:
Can someone please recommend an RUU to go to... I'm just worried if I use the wrong one it will cause more issues. I thought RUUs were dependent on the CID num and as that's been changed to allow custom roms... I'd be happy taking it back to a plain old vanilla HTC / Google - just something to get it back alive.
Click to expand...
Click to collapse
There is no ruu we can recommend because your version-main is blank the fact that you also have superCID doesn't help identifying which ruu you'll need to use.
mdb said:
Should also add I can't get s-off... adb devices doesn't show anything... I'm guessing usb debugging wasn't set up
Click to expand...
Click to collapse
You'll have to unlock the bootloader, flash a custom recovery (twrp preferred), flash a rom and use your phone like that or, if you want, from there you will be able to achieve s-off again and convert your phone to wherever you want (Stock Sense or stock GPE) by flashing a RUU.
alray said:
There is no ruu we can recommend because your version-main is blank the fact that you also have superCID doesn't help identifying which ruu you'll need to use.
You'll have to unlock the bootloader, flash a custom recovery (twrp preferred), flash a rom and use your phone like that or, if you want, from there you will be able to achieve s-off again and convert your phone to wherever you want (Stock Sense or stock GPE) by flashing a RUU.
Click to expand...
Click to collapse
Thanks so much for this... I've been learning more all day (traditionally an iOS guy)...
Am I right in thinking I would need to sideload a custom rom through twrp and then install it? If so, I'm having an issue getting my laptop to talk to the phone - "adb devices" is pretty flakey to say the least, sometimes it works sometimes it doesn't... I've read various things about Windows 8 and that adb works best on Windows 7, can you please confirm I'm on the right track here. I'd like to put the Viper rom on it.
Thanks again
In order to flash custom recovery you need to be booted to bootloader menu, and use fastboot commands. If you flash TWRP 2.8.6.0 or later, there's no need to sideload a ROM because newer TWRP recoveries have MTP option, so you use that. Try to go to bootloader, connect your phone to your laptop or PC, and issue a command fastboot devices. If it shows your phone, you're good to go
Thanks donkeyking1...
I got it working eventually, I needed to install new drivers for Windows 8 then adb started behaving properly. I ended up pushing the Viper ROM to the phone... The phone's alive now but currently it has no IMEI, baseband or OS - they're all blank. I'm wondering if it's because I've installed Viper 9 without upgrading the firmware first? My next goals are to try and S-OFF the device so I can install a stock rom, at which point hopefully I'll get OTA updates and then go back to Viper 9 - it looks great, I just can't use it! - no phone signal!
Does that sound like the right approach? I'm trying to flash different custom roms to hopefully find one that works with rumrunner. I've read that some folks have managed to S-OFF on hboot 1.57 with rumrunner, but it's picky on the rom that's installed. It doesn't work on Viper 9...
If anyone can add any help it would be much appreciated!
Thanks in advance
mdb said:
Thanks donkeyking1...
I got it working eventually, I needed to install new drivers for Windows 8 then adb started behaving properly. I ended up pushing the Viper ROM to the phone... The phone's alive now but currently it has no IMEI, baseband or OS - they're all blank. I'm wondering if it's because I've installed Viper 9 without upgrading the firmware first? My next goals are to try and S-OFF the device so I can install a stock rom, at which point hopefully I'll get OTA updates and then go back to Viper 9 - it looks great, I just can't use it! - no phone signal!
Does that sound like the right approach? I'm trying to flash different custom roms to hopefully find one that works with rumrunner. I've read that some folks have managed to S-OFF on hboot 1.57 with rumrunner, but it's picky on the rom that's installed. It doesn't work on Viper 9...
If anyone can add any help it would be much appreciated!
Thanks in advance
Click to expand...
Click to collapse
flash the 7.19.401.2 firmware and then the 7.19.401.2 RUU. If you still have imei problem after that, its most likely an hardware defect.
relock your bootloader if not already locked or re-locked:
Code:
fastboot oem lock
Code:
fastboot orm rebootRUU
fastboot flash zip M7_UL_Firmware_7.19.401.2.zip
fastbppt flash zip M7_UL_Firmware_7.19.401.2.zip
fastboot reboot-bootloader
fastboot oem rebootRUU
htc_fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.2_Radio_4T.35.3218.16_10.33Q.1718.01L_release_421790_signed.zip
fastboot reboot
*** use htc_fastboot.exe for flashing the ruu (linked below). Save all files in the same folder where you already have fastboot.exe and adb.exe on your computer.
M7_UL_Firmware_7.19.401.2.zip
PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.2_Radio_4T.35.3218.16_10.33Q.1718.01L_release_421790_signed.zip
htc_fastboot.exe
Alray, just curious (still learning ), how do you know from the info I've given you that the firmware / RUU you've suggested is one to fix the issues - I've struggled to understand this the past few days - thanks!
mdb said:
Alray, just curious (still learning ), how do you know from the info I've given you that the firmware / RUU you've suggested is one to fix the issues - I've struggled to understand this the past few days - thanks!
Click to expand...
Click to collapse
To flash a ruu on a s-on phone there are many prerequisites:
The RUU must match your MID: 7.19.401.2 is for PN0710000
The RUU must match your CID: You have superCID so its not a problem.
The RUU must be the same version or an upgrade from your actual version, we don't know your actual version because of your blank versio-main but you have 1.57 hboot which suggest a 6.xx.xxx.x version. So 7.19.401.2 should be an upgrade.
The bootloader must be locked or re-locked.
There is no risk trying it, the worst that can happen is that the phone won't accept the ruu and nothing will be flashed.
mdb said:
Alray, just curious (still learning ), how do you know from the info I've given you that the firmware / RUU you've suggested is one to fix the issues - I've struggled to understand this the past few days - thanks!
Click to expand...
Click to collapse
Super CID + your MID. WWE firmware should work just fine. Right @alray?
donkeykong1 said:
Super CID + your MID. WWE firmware should work just fine. Right @alray?
Click to expand...
Click to collapse
:good:
Well, thanks so much for your help guys, but alas it seems the phone is k-put... Flashed the firmware and the rom no problem.... but it still shows no IMEI / IMEI SV / IMSI and it can't recognise the phone number - I'm guessing it can't read the sim. It does show the OS and IMEI in the bootloader, but once booted it's a no go.
mdb said:
Well, thanks so much for your help guys, but alas it seems the phone is k-put... Flashed the firmware and the rom no problem.... but it still shows no IMEI / IMEI SV / IMSI and it can't recognise the phone number - I'm guessing it can't read the sim. It does show the OS and IMEI in the bootloader, but once booted it's a no go.
Click to expand...
Click to collapse
Try to bend your sim tray just a little bit. Maybe your sim card is not reaching the contacts inside the phone. Or put a piece of paper under the sim and see what happens
Thanks donkeykong1, I've tried but it's not working... The fact the IMEI / IMEI SV and baseband are unknown though... they're not sim related...
It does show the baseband and IMEI in fastboot getvar all though?...
There were a lot of people with that same issue, and their phones worked fine, so I doubt it has anything to do with your sim. Your sim works in another phone?
Yeah, the sim's fine. @alray said it's likely a hardware issue if the firmware / rom didn't repair the IMEI issue, and the other threads I've looked at with the same issue are all saying the motherboard's faulty.
Although I am baffled as to why it is showing the IMEI / baseband in the bootloader, in fastboot etc. but not once the phone has booted up?...
I read on another thread (http://forum.xda-developers.com/showthread.php?t=2253514) that maybe flashing a kernal and/or radio might solve it?
Just wondering whether I should try flashing an official HTC rom? I've been in touch with the guy I got it off and he said it was originally on Orange, UK:
http://www.htcdev.com/devcenter/downloads > One M7 / v5.0.2 > Find Files : Page 6
One M7 / Orange / UK / CRC / 3.4.10 / v5.0.2 / 539.0 MB / 7.19.61.10
Was also thinking of...
http://www.htcdev.com/devcenter/downloads > One M7 / v5.0.2 > Find Files : Page 1
One M7 / HTC / EU / MR 3 / 3.4.10 / v5.0.2 / 486.0 MB / 7.19.401.22
If I did that would I need to update the firmware first like you advised originally @alray?
If I know I can revive the IMEI etc. I'll be happy to go ahead and pay to S-OFF
Thanks in advance
You need a kernel to match your firmware. If you're on 7.19.401.2, then you need 7.19.401.2 kernel. I can give you boot.img, but I don't have the whole zip, with modules. Then again, if your phone boots fine, maybe boot.img will help. I'd [email protected] to confirm my thoughts though. He's much more into this than I am

Categories

Resources