A couple years ago, I unlocked/TWRPed/rooted/ROMed my phone - but I haven't touched it since. As a result, I haven't updated my firmware in a LONG time. I've been reading all afternoon, but I could use a little bit of help. Here's what I'm thinking my steps will be:
nandroid backup - I can't seem to get the phone mounted as a drive on my Mac, and HTC Sync Manager keeps crashing, but I'll figure out some way to pull the backup off...
S-OFF my phone - would you recommend Rumrunner? Any particular guide?
Using fastboot and this guy's advice, flash a bunch of firmwares onto my phone. Question: which firmwares do I need, and did how you know? I have to match my CID and MID, but how do I find all the firmware downloads that I've skipped? I don't suppose everyone flashes new versions of firmware the moment they're released, but I'm not sure how people "catch up"...
Flash the most recent TWRP and version of my custom ROM
I'd love to get some answers to the above questions, and to hear any advice you might have! Thanks, community - you rock! Here's some relevant information:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.15
(bootloader) version-misc: PVT SHIP S-ON
...
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4201mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
mynnx said:
A couple years ago, I unlocked/TWRPed/rooted/ROMed my phone - but I haven't touched it since. As a result, I haven't updated my firmware in a LONG time. I've been reading all afternoon, but I could use a little bit of help. Here's what I'm thinking my steps will be:
nandroid backup - I can't seem to get the phone mounted as a drive on my Mac, and HTC Sync Manager keeps crashing, but I'll figure out some way to pull the backup off...
S-OFF my phone - would you recommend Rumrunner? Any particular guide?
Using fastboot and this guy's advice, flash a bunch of firmwares onto my phone. Question: which firmwares do I need, and did how you know? I have to match my CID and MID, but how do I find all the firmware downloads that I've skipped? I don't suppose everyone flashes new versions of firmware the moment they're released, but I'm not sure how people "catch up"...
Flash the most recent TWRP and version of my custom ROM
I'd love to get some answers to the above questions, and to hear any advice you might have! Thanks, community - you rock! Here's some relevant information:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.15
(bootloader) version-misc: PVT SHIP S-ON
...
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4201mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
Click to expand...
Click to collapse
OK well your on the right track rumrunner should work for you to gain s-off. And that should be your first priority. Although rumrunner was developed for hboot 1.54 and 1.55 so if you run into issues you may need to flash the first 2 updates and a stock rom for it to work.
Once you have s-off which firmware to use depends largely on your situation. Your device is currently running At&t firmware. Are you still using the device on the At&t network? If not then it would probably be better to convert to Dev Edition or HTC Unbranded firmware.
Also with s-off it can be much easier to update the device using RUUs rather than just flashing firmware.zips.
Sent from my SM-T230 using Tapatalk
I was told that I shouldn't skip firmware updates. Is that true?
I'm on hboot 1.44, so I don't anticipate any problems with S-OFFing, right?
mynnx said:
I was told that I shouldn't skip firmware updates. Is that true?
I'm on hboot 1.44, so I don't anticipate any problems with S-OFFing, right?
Click to expand...
Click to collapse
That's right skipping firmware updates can brick your phone. Unless your using an RUU. RUUs contain a full firmware package so these can be used to skip a version but usually you need to be close to the RUU version for them to flash. Firmware updates however only include the updated part of the firmware. Skipping firmware updates can leave you with firmware incompatibility forcing the device into QHSUB USB DLOAD mode.
Try rumrunner with your current setup and see what happens. If it fails then make sure you have your backups safe. And relock your bootloader and flash this ruu. http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/
This will update your device to hboot 1.55 with a Jellybean 4.3 stock rom perfect for rumrunner. It will wipe your internal storage though so make sure you've got everything you want to keep backup.
Instructions....
Boot device to the bootloader and connect fastboot usb. In the command window type
Code:
fastboot erase cache
fastboot oem lock
fastboot reboot-bootloader
The bootloader should now read ***RELOCKED***
Make sure that it is in fastbootusb mode. Then launch the ruu.exe on your pc. Follow the instructions to update the phone. Once that's done unlock the bootloader and try rumrunner again. :good:
Sent from my SM-T230 using Tapatalk
Danny - thanks!
I don't have access to a PC, so I need a .zip to flash - is that the most recent RUU?
Can you (or anyone else) hook me up with the list of .zip RUUs that I need to flash to get to the most current version of my firmware?
Also, I shouldn't need to re-lock with S-OFF, right?
mynnx said:
Danny - thanks!
I don't have access to a PC, so I need a .zip to flash - is that the most recent RUU?
Can you (or anyone else) hook me up with the list of .zip RUUs that I need to flash to get to the most current version of my firmware?
Click to expand...
Click to collapse
Are you still on at&t ?
Also, I shouldn't need to re-lock with S-OFF, right?
Click to expand...
Click to collapse
right
mynnx said:
Danny - thanks!
I don't have access to a PC, so I need a .zip to flash - is that the most recent RUU?
Can you (or anyone else) hook me up with the list of .zip RUUs that I need to flash to get to the most current version of my firmware?
Also, I shouldn't need to re-lock with S-OFF, right?
Click to expand...
Click to collapse
It's not the most recent ruu no, but if you flash anything newer you will then need to use sunshine to s-off and it will cost you $25.
Any firmware or RUU will require access to a pc with fastboot. You can't flash firmware from recovery like a Rom. It has to be flashed in RUU mode.
You don't need to relock if your s-off but I think you will need to first update the device to hboot 1.55 before rumrunner will work. You can do that with this RUU then gain s-off then the sky's the limit
Sent from my M7 Running ARHD 92.x
Danny201281 said:
It's not the most recent ruu no, but if you flash anything newer you will then need to use sunshine to s-off and it will cost you $25.
Any firmware or RUU will require access to a pc with fastboot. You can't flash firmware from recovery like a Rom. It has to be flashed in RUU mode.
You don't need to relock if your s-off but I think you will need to first update the device to hboot 1.55 before rumrunner will work. You can do that with this RUU then gain s-off then the sky's the limit
Sent from my M7 Running ARHD 92.x
Click to expand...
Click to collapse
I should have been more specific - I don't have access to a Windows PC, so I can't run the .exe RUUs, but I can totally fastboot them on as .zip's.
Can you explain the need to use Sunshine with newer RUUs? And why/how it's necessary to update hboot to use rumrunner?
mynnx said:
I should have been more specific - I don't have access to a Windows PC, so I can't run the .exe RUUs, but I can totally fastboot them on as .zip's.
Can you explain the need to use Sunshine with newer RUUs? And why/how it's necessary to update hboot to use rumrunner?
Click to expand...
Click to collapse
There are different methods for gaining s-off depending on your hboot version.
First we had Revone and Moonshine. Which was developed for hboot 1.44 then HTC released a patched firmware to prevent it from working. [You currently have the patched firmware. So these are not an option.]
Then there is Rumrunner. Which was developed for hboot 1.54 and updated for 1.55 and 1.56. Then again HTC released patched firmware to prevent Rumrunner from working with hboot 1.56. But it still should work with 1.54 and 1.55. [Since the suggested RUU should update your device to 1.55. So rumrunner should then work with the device.]
Then came Firewater. Which was developed for 1.56 and 1.57. But for reasons of his own the dev discontinued support of Firewater. [Subsequently it no longer works at all.]
Then came Sunshine App developed for hboot 1.57 and above. Very simple to use, but the devs decided to charge a license for for it so you have to pay $25 to use it. [While controversial the s-off devs have worked hard for us over the years. So why shouldn't they.]
So you see you basically have 2 choices to s-off. rumrunner (free to use only works with hboot 1.54 and 1.55).
Sunshine App ( in theory should work with any hboot version. But costs $25)
I'm not sure if that ruu is available in zip format I'll see what I can find and post the links here :good: you may need to manually update firmware and flash a stock Rom to use rumrunner. Or if you can spare the 25 bills just use sunshine for a one click solution :good:
Sent from my M7 Running ARHD 92.x
alray said:
Are you still on at&t ?
right
Click to expand...
Click to collapse
Yeah, I'm still on AT&T.
mynnx said:
Yeah, I'm still on AT&T.
Click to expand...
Click to collapse
OK try this one. http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb43_50_cingular_3-10-502-2-zip/ ATT RUU zip. I don't know if it's been modified in any way though. If it has it will fail to flash because it's not signed. And your s-on. If it's signed it should flash just fine if you relock the bootloader.
Sent from my SM-T230 using Tapatalk
Danny201281 said:
There are different methods for gaining s-off depending on your hboot version.
First we had Revone and Moonshine. Which was developed for hboot 1.44 then HTC released a patched firmware to prevent it from working. [You currently have the patched firmware. So these are not an option.]
Then there is Rumrunner. Which was developed for hboot 1.54 and updated for 1.55 and 1.56. Then again HTC released patched firmware to prevent Rumrunner from working with hboot 1.56. But it still should work with 1.54 and 1.55. [Since the suggested RUU should update your device to 1.55. So rumrunner should then work with the device.]
Then came Firewater. Which was developed for 1.56 and 1.57. But for reasons of his own the dev discontinued support of Firewater. [Subsequently it no longer works at all.]
Then came Sunshine App developed for hboot 1.57 and above. Very simple to use, but the devs decided to charge a license for for it so you have to pay $25 to use it. [While controversial the s-off devs have worked hard for us over the years. So why shouldn't they.]
So you see you basically have 2 choices to s-off. rumrunner (free to use only works with hboot 1.54 and 1.55).
Sunshine App ( in theory should work with any hboot version. But costs $25)
I'm not sure if that ruu is available in zip format I'll see what I can find and post the links here :good: you may need to manually update firmware and flash a stock Rom to use rumrunner. Or if you can spare the 25 bills just use sunshine for a one click solution :good:
Sent from my M7 Running ARHD 92.x
Click to expand...
Click to collapse
Correct me if I'm wrong; I want to make sure I'm understanding you correctly:
hboot 1.44 with my firmware version isn't possible to S-OFF
Flashing RUUs will update my version of hboot, and the RUU you suggested is S-OFFable by rumrunner
I can't normally flash RUUs without S-OFF, but the RUU you suggested matches my CID and MID so it will work
Once I'm at hboot 1.55 after flashing that RUU, and S-OFFed after rumrunner, I should be able to flash more recent RUUs without losing my S-OFF
Why / how might I need to flash firmware manually and flash a stock ROM to use rumrunner?
mynnx said:
Correct me if I'm wrong; I want to make sure I'm understanding you correctly:
hboot 1.44 with my firmware version isn't possible to S-OFF <----- Correct because you have the latest 1.44 firmware as indicated by .15 on the end of your OS Version
Flashing RUUs will update my version of hboot, and the RUU you suggested is S-OFFable by rumrunner <----- Correct the Ruu will update your firmware hboot and rom completely stock. Rumrunner should work with this combination.
I can't normally flash RUUs without S-OFF, but the RUU you suggested matches my CID and MID so it will work. You can flash ruu's with s-on but the ruu must match your CiD, MiD You must relock the bootloader and the ruu must be unmodified and carry a HTC signiture. .exe ruu's are all HTC signed, Ruu zips can be modified so are not all guaranteed to work with s-on
Once I'm at hboot 1.55 after flashing that RUU, and S-OFFed after rumrunner, I should be able to flash more recent RUUs without losing my S-OFF <----- Correct, although you can update your firmware and flash the latest ruu with s-on but you will then have to pay for sunshine to get s-off so it's better to do it for free with rumrunner on the way. And No flashing RUUS will not affect s-off. The only way to go back to s-on requires a specific fastboot command.
Click to expand...
Click to collapse
Answers in bold red in above quote
Why / how might I need to flash firmware manually and flash a stock ROM to use rumrunner?
Click to expand...
Click to collapse
As your still on the att network you do have another option. You could flash this rom http://www.htc1guru.com/dld/guru_reset_m7_1-26-502-15-zip/
This is a guru reset rom that matches your current firmware. You can return your software to stock by flashing it in a custom recovery like a normal rom. It comes with some option of which you should choose
Stock radio = Yes
Stock recovery = Yes
Root = No
Once it's installed you'll have full stock rom and recovery, because your on the att network you will be able to accept OTA updates. Take the first to updates to hboot 1.55 then use Rumrunner then you could either manually flash the rest of the updates or just continue to take OTA's until your on the latest firmware and rom. Once that's done you can flash TWRP and any lollipop custom roms you like :good:
Edit:- Also forgot to mention with this method there is no need to relock the bootloader :good:
Sent from my SM-T230 using Tapatalk
Related
Hi all, my HTC One is currently running on unlocked bootloader with s-on, and on hboot 1.44.
I believe my phone is stuck on unlocked bootloader. My phone runs perfectly with no hiccups when my bootloader is unlocked, but when I try to use adb to relock my bootloader, while it does relock my bootloader successfully, I'm unable to boot into the rom, the phone just switches on into the bootloader everytime i reboot, and a "Security Warning" pops up below the "TAMPERED" and "RELOCKED" text.
I'm relocking my bootloader so that the RUU will work as I'm constantly getting error code 155 in the RUU when I try to flash back to stock. I've also tried to S-OFF my device but it kept giving me error 6 despite the fact that I was able to get on S-OFF before.
Note: I think I've done something wrong previously that got me into this situation. When I was trying to get my phone back to stock through RUU at first, I had S-OFF initially, and I followed this guide (http://androidforums.com/internatio...-return-100-stock-revone-moonshine-s-off.html) but I forgot to flash the RUU first before I used the "writesecureflag 3" command to lock my bootloader and revert back to S-ON.
Is there a way I could revert back and get my bootloader relocked with no problems? I've done a backup before I messed up my RUU, but due to the fact that I was stuck on the bootloader screen after locking my bootloader, I had to unlock my bootloader again which wiped my whole SD card including my backup...
EDIT: added getvar
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.707.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT367xxxxxx
(bootloader) imei: 3558590xxxxxx
(bootloader) meid: 00000000000000 <- (looks fishy, could this be the source of the problem?)
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 4248mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links)) <- (this too)
finished. total time: 0.050s
my meid is also all 0s so that is fine.
your firmware is version 2.24.707.1, has this been upgraded since you tried revone the first time? That could be why you are getting an error code with revone now, did you have 1.29.707.16 originally?
if you unlock your bootloader again you flash a custom recovery then install the stock rom for your carrier from your recovery. This will put your phone on a stock rom then you can re-lock again after that with fastboot oem lock.
you can gain Locked instead of Relocked using revone if you can get it to work again, which may require downgraded firmware version.
or I would run a .ruu for your device, though these could be dangerous especially if you are s-on. Also attempting to downgrade with RUU would cause a brick pretty sure.
Your phone will always bootloop when you lock the boot loader with a custom recovery installed. This is normal.
Edit:
I suppose I should offer some help also. Going to S-on was a mistake. You need to unlock the boot loader and flash a stock rom, then try to regain S-off. If you can achieve it, relock the boot loader and run the RUU. Then use Revone to set the ****Tampered**** flag to off and lock the boot loader. And if you do achieve S-off again, do NOT S-on. It is not necessary.
Sent from my One using XDA Premium 4 mobile app
blu9987 said:
my meid is also all 0s so that is fine.
your firmware is version 2.24.707.1, has this been upgraded since you tried revone the first time? That could be why you are getting an error code with revone now, did you have 1.29.707.16 originally?
if you unlock your bootloader again you flash a custom recovery then install the stock rom for your carrier from your recovery. This will put your phone on a stock rom then you can re-lock again after that with fastboot oem lock.
you can gain Locked instead of Relocked using revone if you can get it to work again, which may require downgraded firmware version.
or I would run a .ruu for your device, though these could be dangerous especially if you are s-on. Also attempting to downgrade with RUU would cause a brick pretty sure.
Click to expand...
Click to collapse
Wow thanks! I managed to lock my bootloader finally after finding and flashing a 1.29.707.3 stock rom, but my touchscreen is not responding now, which I guess is most probably an issue with the firmware? And I presume it's safer to use RUU over S-OFF? I want to try revone and S-OFF again but i cant grant adb shell superuser since i cant get my touchscreen to respond.. Oh god, endless ordeals lol...
EDIT: I'm on 1.29.707.3 currently and I have the 1.29.707.3 RUU, is it possible to flash the RUU? I'm hoping to get the RUU to run so that I can solve the touchscreen issue and possibly achieve S-OFF afterwards.
EDIT2: I went ahead with running RUU after finally being able to relock my bootloader but now I'm faced with RUU error 140
jerronchua55 said:
Wow thanks! I managed to lock my bootloader finally after finding and flashing a 1.29.707.3 stock rom, but my touchscreen is not responding now, which I guess is most probably an issue with the firmware? And I presume it's safer to use RUU over S-OFF? I want to try revone and S-OFF again but i cant grant adb shell superuser since i cant get my touchscreen to respond.. Oh god, endless ordeals lol...
EDIT: I'm on 1.29.707.3 currently and I have the 1.29.707.3 RUU, is it possible to flash the RUU? I'm hoping to get the RUU to run so that I can solve the touchscreen issue and possibly achieve S-OFF afterwards.
EDIT2: I went ahead with running RUU after finally being able to relock my bootloader but now I'm faced with RUU error 140
Click to expand...
Click to collapse
You are right, the touchscreen won't work because the drivers were updated in the firmware, but you can use an OTG cable with a mouse instead.
Anyway, first thing I would try to do is achieve s-off again (make sure you have hboot 1.44 dated before June 2013), and as Corry said, do not go back to s-on. adb should still work fine from your computer even without touchscreen, so you should be able to do it. In case your ROM is not "allowing" you proper use of adb or revone, then you can try the one I posted here: http://forum.xda-developers.com/showthread.php?t=2471174
nkk71 said:
You are right, the touchscreen won't work because the drivers were updated in the firmware, but you can use an OTG cable with a mouse instead.
Anyway, first thing I would try to do is achieve s-off again (make sure you have hboot 1.44 dated before June 2013), and as Corry said, do not go back to s-on. adb should still work fine from your computer even without touchscreen, so you should be able to do it. In case your ROM is not "allowing" you proper use of adb or revone, then you can try the one I posted here: http://forum.xda-developers.com/showthread.php?t=2471174
Click to expand...
Click to collapse
Even with ARHD 9.4 the touchscreen is still not responding, I think I need to reflash my firmware, is it possible to flash a firmware without updating hboot on S-ON?
jerronchua55 said:
Even with ARHD 9.4 the touchscreen is still not responding, I think I need to reflash my firmware, is it possible to flash a firmware without updating hboot on S-ON?
Click to expand...
Click to collapse
Just use the ROM to get S-Off, without touchscreen, just boot up the rom, and use adb from your PC.
Not possible to change firmware with S-On.
nkk71 said:
Just use the ROM to get S-Off, without touchscreen, just boot up the rom, and use adb from your PC.
Not possible to change firmware with S-On.
Click to expand...
Click to collapse
I couldnt get past my lockscreen to grant su access to adb shell without the touchscreen, but I just picked an OTG cable so I'm fine now.
Problem is, even on ARHD 9.4 I'm still getting error code -6 on revone... Bummer, I shouldn't have returned my phone back to S-ON.
EDIT: My hboot is dated 4/5/13, so it shouldnt be the patched 1.44 hboot. I'm gonna try S-OFF on the stock 1.29.707.3 instead, will post my results asap
jerronchua55 said:
I couldnt get past my lockscreen to grant su access to adb shell without the touchscreen, but I just picked an OTG cable so I'm fine now.
Problem is, even on ARHD 9.4 I'm still getting error code -6 on revone... Bummer, I shouldn't have returned my phone back to S-ON.
Click to expand...
Click to collapse
What's the date of your bootloader? If it's before June 2013 (and is version 1.44), you should be able to get it to work.
nkk71 said:
What's the date of your bootloader? If it's before June 2013 (and is version 1.44), you should be able to get it to work.
Click to expand...
Click to collapse
Nope it still didn't work, but i guess i resolved my main issue with not being able to relock my bootloader.
I'm gonna redirect my issues on the revone thread instead so yea, gave you a thanks for your help nonetheless!
jerronchua55 said:
Nope it still didn't work, but i guess i resolved my main issue with not being able to relock my bootloader.
I'm gonna redirect my issues on the revone thread instead so yea, gave you a thanks for your help nonetheless!
Click to expand...
Click to collapse
And one for you
Let me know if I can help out anyway.
If bootloader is May 2013 it shouldnt be the patched version. But it seems that there revone, not only has issues with ROMs, but also firmware. One last thing to try though: I saw one person was able to achieve S-Off using a GPe 4.2.2 ROM, (s)he didn't specify which but it worked. Since you're on the updated firmware, try getting your hands on a 4.2.2 GPe ROM and try.
I know it's all time consuming, but you never know :fingers-crossed:
Good luck
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
Hey guys and girls. A little backstory:
New to android
Use Cyanogenmod Installer
Get Purple Camera. Need to go back to stock.
Stumble upon guide by nkk71 http://forum.xda-developers.com/showthread.php?t=2541082
Botch last step
So I found an ruu with my CID and MID, but it was the GPE ruu not the ATT RUU! The ATT RUU zips don't list CID and MID so I assumed I should not use them and all that matters is matching those.
I had locked and went back to s-On when following the guide.... big mistake.
I've since unlocked and tried to root so that I could go back to S-Off.
Flashed several different correct recoveries and none will work. I am erasing the cache, but nothing works. I've tried the most recent versions of CWM and TWRP and can't get anywhere.
What should I try next?
bradreputation said:
Hey guys and girls. A little backstory:
New to android
Use Cyanogenmod Installer
Get Purple Camera. Need to go back to stock.
Stumble upon guide by nkk71 http://forum.xda-developers.com/showthread.php?t=2541082
Botch last step
So I found an ruu with my CID and MID, but it was the GPE ruu not the ATT RUU! The ATT RUU zips don't list CID and MID so I assumed I should not use them and all that matters is matching those.
I had locked and went back to s-On when following the guide.... big mistake.
I've since unlocked and tried to root so that I could go back to S-Off.
Flashed several different correct recoveries and none will work. I am erasing the cache, but nothing works. I've tried the most recent versions of CWM and TWRP and can't get anywhere.
What should I try next?
Click to expand...
Click to collapse
Sorry to hear that, I thought my guide was pretty clear
please post
1- a fastboot getvar all (excluding IMEI and s/n)
2- a screenshot of your bootloader
3- more details of what you have flashed (with links to the threads)
nkk71 said:
Sorry to hear that, I thought my guide was pretty clear
please post
1- a fastboot getvar all (excluding IMEI and s/n)
2- a screenshot of your bootloader
3- more details of what you have flashed (with links to the threads)
Click to expand...
Click to collapse
Your guide is very good and I thank you for it. I just messed up. I think it would be good to clarify that a person should reboot after flashing RUU before going back to S-On. I had the impression that was my only chance to go back S-On.
version: 0.5
version-bootloader: 1.54.0000
version-baseband: 4T.21.3218.21
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: CWS__001
battery-status: good
battery-voltage: 4291mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-5d4c562c
hbootpreupdate: 11
gencheckpt: 0
http://imgur.com/yXDR6lr Shot of my Bootloader
This is what I flashed for RUU http://www.htc1guru.com/dld/ruu-zip-m7_google-edition_4-4_3-58-1700-5-zip/
I've flashed the latest TWRP and CWM. The problem really started when I installed CWM and Su from this guidehttp://forum.xda-developers.com/showthread.php?t=2292729.
bradreputation said:
Your guide is very good and I thank you for it. I just messed up. I think it would be good to clarify that a person should reboot after flashing RUU before going back to S-On. I had the impression that was my only chance to go back S-On.
Click to expand...
Click to collapse
Technically, you can, but shouldn't reboot the OS because of the OTA notification, which may make it tempting to take, but I'll try and rephrase the guide.
bradreputation said:
version-bootloader: 1.54.0000
version-main:
version-misc: PVT SHIP S-ON
product: m7_ul
modelid: PN0712000
cidnum: CWS__001
http://imgur.com/yXDR6lr Shot of my Bootloader
This is what I flashed for RUU http://www.htc1guru.com/dld/ruu-zip-m7_google-edition_4-4_3-58-1700-5-zip/
I've flashed the latest TWRP and CWM. The problem really started when I installed CWM and Su from this guidehttp://forum.xda-developers.com/showthread.php?t=2292729.
Click to expand...
Click to collapse
bootloader is unlocked, good... do NOT try and lock it!!
reflash TWRP and a custom ROM (you can try ARHD 31.6 or similar), and get S-OFF using rumrunner and/or firewater
i'm off for tonight, sorry about the mess
The stock att RUU's would almost certainly have the stock CWS_001 Cid. You just need one that is the same or postdated to your current hboot version since you are s-on now. Unfortunately, now that you are s-on, you will also need to relock the bootloader to flash an RUU. I would do that and then use firewater/rumrunner/latest s-off method to get s-off and unlock boot loader. Then you want to fix the "relocked" flag to "locked", and s-on again, and get it repaired.
I would try to get S-OFF where you are now.
I'll keep this here just in case
Otherwise, you can use the 3.xx RUU.EXE: http://androidruu.com/getdownload.p...13_10.38j.1157.04_release_334235_signed_2.exe
this will upgrade to hboot 1.55, and rumrunner and/or firewater should work on it.
(remember you need to relock bootloader for that to work with S-On, that's why i'm recommending to try where you are now, so you don't lock bootloader)
there is also a 4.xx RUU but do not use it, because it will upgrade your hboot to 1.56, making it even more difficult to S-OFF.
and once you're S-OFF, you should use this ruu.zip for my guide (which is for PN0712000 + CWS__001):
http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb_50_cingular-1-26-502-15-decrypted-zip/
AFH Mirror: http://www.androidfilehost.com/?fid=23501681358544977
nkk71 said:
I would try to get S-OFF where you are now.
I'll keep this here just in case
Otherwise, you can use the 3.xx RUU.EXE:
this will upgrade to hboot 1.55, and rumrunner and/or firewater should work on it.
(remember you need to relock bootloader for that to work with S-On, that's why i'm recommending to try where you are now, so you don't lock bootloader)
there is also a 4.xx RUU but do not use it, because it will upgrade your hboot to 1.56, making it even more difficult to S-OFF.
and once you're S-OFF, you should use this ruu.zip for my guide (which is for PN0712000 + CWS__001):
]
Click to expand...
Click to collapse
I was able to get TWRP (newest version) and ARHD (31.6) running. I then got S-OFF using Firewater. I'll use the RUU and follow the guide again.
I saw another one of your posts that suggested S-OFF may not effect warranty claims. Any further thought on that?
Thanks again for all your contributions.
bradreputation said:
I was able to get TWRP (newest version) and ARHD (31.6) running. I then got S-OFF using Firewater. I'll use the RUU and follow the guide again.
I saw another one of your posts that suggested S-OFF may not effect warranty claims. Any further thought on that?
Thanks again for all your contributions.
Click to expand...
Click to collapse
It's really very country/carrier/people specific, in theory, S-Off shouldn't matter as some phones accidentally ship S-Off (ok, it's very very very rare), but S-Off shouldn't void warranty https://twitter.com/htc/status/377422743626842112
Then again, in practice some carriers/technicians may try to use any excuse to refuse warranty.
I have an AT&T HTC One (m7). I would like to ultimately get this back to HTC's stock version with the ability to receive OTA updates and behave just like it would if it were never modified. Several guides, post, and pages say that the only way I can successfully use an AT&T RUU file is accomplishing S-OFF since they will all contain older firmware (HBOOTS) than my current 1.57 version (I've seen some who LOCK the bootloader after achieve S-OFF and others who don't). If anyone can definitively tell me if it matters rather bootloader is still locked after achieve S-OFF, that would be appreciated.
XDA and HTC Guru indicate to successfully run an RUU I need to downgrade my HBOOT from 1.57 to HBOOT 1.44. While downgrading, can I go from 1.57 and directly install a 1.44 firmware or do I have to step down one at a time 1.57-->1.54-->1.x -> 1.44? Also, if anyone has a collection of firmware I can use to do this, that would be awesome too.
The RUU i'm trying to ultimately put on my phone is RUU_M7_UL_JB_50_Cingular_US_1.26.502.15_Radio_4A.17.3250.20_10.40.1150.04_release_326691_signed_2 from AndroidRUU (new , so can't embed the link)
After all my fiddling, this is the output of my getvar all:
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4M.27.3218.14
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-OFF
serialno: XXXXXX
imei: XXXXX
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: CWS__001
battery-status: good
battery-voltage: 4333mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-1f512bb6
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
If anyone has a suggestion on how to accomplish stock ROM back on my HTC m7 with my setup, I'd greatly appreciate it. Thank you!
consequense said:
I have an AT&T HTC One (m7). I would like to ultimately get this back to HTC's stock version with the ability to receive OTA updates and behave just like it would if it were never modified. Several guides, post, and pages say that the only way I can successfully use an AT&T RUU file is accomplishing S-OFF since they will all contain older firmware (HBOOTS) than my current 1.57 version (I've seen some who LOCK the bootloader after achieve S-OFF and others who don't). If anyone can definitively tell me if it matters rather bootloader is still locked after achieve S-OFF, that would be appreciated.
XDA and HTC Guru indicate to successfully run an RUU I need to downgrade my HBOOT from 1.57 to HBOOT 1.44. While downgrading, can I go from 1.57 and directly install a 1.44 firmware or do I have to step down one at a time 1.57-->1.54-->1.x -> 1.44? Also, if anyone has a collection of firmware I can use to do this, that would be awesome too.
The RUU i'm trying to ultimately put on my phone is RUU_M7_UL_JB_50_Cingular_US_1.26.502.15_Radio_4A.17.3250.20_10.40.1150.04_release_326691_signed_2 from AndroidRUU (new , so can't embed the link)
After all my fiddling, this is the output of my getvar all:
If anyone has a suggestion on how to accomplish stock ROM back on my HTC m7 with my setup, I'd greatly appreciate it. Thank you!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2485651 here is a list of firmware
You can downgrade your hboot and then run the RUU. Make sure it's a stock hboot and NOT a modified one (it'll say either or). You can open the firmeware zips (not extract) and open and edit the android.info text file and add in your CID and model id as required if necessary
You can then flash the RUU as normal after. No need to step down hboots
consequense said:
I have an AT&T HTC One (m7). I would like to ultimately get this back to HTC's stock version with the ability to receive OTA updates and behave just like it would if it were never modified.
Several guides, post, and pages say that the only way I can successfully use an AT&T RUU file is accomplishing S-OFF since they will all contain older firmware (HBOOTS) than my current 1.57 version (I've seen some who LOCK the bootloader after achieve S-OFF and others who don't). If anyone can definitively tell me if it matters rather bootloader is still locked after achieve S-OFF, that would be appreciated.
XDA and HTC Guru indicate to successfully run an RUU I need to downgrade my HBOOT from 1.57 to HBOOT 1.44. While downgrading, can I go from 1.57 and directly install a 1.44 firmware or do I have to step down one at a time 1.57-->1.54-->1.x -> 1.44? Also, if anyone has a collection of firmware I can use to do this, that would be awesome too.
The RUU i'm trying to ultimately put on my phone is RUU_M7_UL_JB_50_Cingular_US_1.26.502.15_Radio_4A.17.3250.20_10.40.1150.04_release_326691_signed_2 from AndroidRUU (new , so can't embed the link)
After all my fiddling, this is the output of my getvar all:
If anyone has a suggestion on how to accomplish stock ROM back on my HTC m7 with my setup, I'd greatly appreciate it. Thank you!
Click to expand...
Click to collapse
Since you are S-OFF, you don't have to go all the way back to JB, you can flash this 4.18.502.7 decrypted ROM. and the instructions are from clsA:
Copy your downloaded file to your fastboot / adb folder
Rename the file Rom.zip
open a command prompt in the same folder (shift + right click - command prompt here )
adb reboot-bootloader
fastboot commands:
fastboot oem rebootRUU
wait for the Silver HTC logo
fastboot flash zip Rom.zip
the first time you issue a command to flash firmware/ruu in fastboot it only prepares the flash. You have to issue the exact command again:
fastboot flash zip Rom.zip
most times the green status bar does not reach the 100% mark. So when the output in the command window is complete, you can reboot:
fastboot reboot
Click to expand...
Click to collapse
This should put you back at stock. You do not need to lock your bootloader since you are S-OFF.
Decrypted ROM Failed
majmoz said:
Since you are S-OFF, you don't have to go all the way back to JB, you can flash this and the instructions are from clsA:
This should put you back at stock. You do not need to lock your bootloader since you are S-OFF.
Click to expand...
Click to collapse
@majmoz I tried to flash the ROM you pointed me to, but it failed. It just said error updating <ROM Name> Updating partition details...
I am still on HBOOT 1.57, if I understood your previous comment, running this ROM would not require me to update the firmware first. Did I mis-understand that?
consequense said:
@majmoz I tried to flash the ROM you pointed me to, but it failed. It just said error updating <ROM Name> Updating partition details...
I am still on HBOOT 1.57, if I understood your previous comment, running this ROM would not require me to update the firmware first. Did I mis-understand that?
Click to expand...
Click to collapse
you can try it again but flash this firmware first and it should work.
http://d-h.st/a1w
You could also use the full RUU after flashing the above firmware. http://www.androidruu.com/getdownlo...09_10.26.1718.01L_release_356565_signed_2.exe
Hi , I have a One (M7) and I'm planning to send it back to HTC in order to fix the purple tint problem.
I'm S-off and I want to Lock the bootloader and returning to Stock + S-on.
I'll follow these steps from http://forum.xda-developers.com/showthread.php?t=2541082 Post #4 but i have doubts marked in blue
Step 0: -not in the previous thread link- I have hboot 1.57. Do I have to move to 1.44 ?
Step 1: let's get rid of TAMPERED (if it's there) and set you back to LOCKED (not relocked)
and confirm no TAMPERED and LOCKED status. (I have UNLOCKED status, so I'm only have to set it to LOCKED, isn't it?)
Step 2: Flash your RUU.zip
Download your MID & CID compatible RUU.zip: http://www.htc1guru.com/downloads/ruu-zip-downloads/
Rename the downloaded file to ruu.zip (careful about ruu.zip.zip in Windows)
(My mid is PN0710000 and cid= HTC__304 so I'll flash
RUU+Zip+M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed)
Do I need first to flash a stock splash?. Currently, I have Maximus 53 HD rom installed (with its own splash bootloader).
Step 3: if YOU decide to go S-On (Note: this should only be done for warranty or selling the phone, it is not needed for OTAs)
fastboot oem writesecureflag 3
( with 1.44 hboot, doesn't exist the possibility of a TEMPERED boot loop, Is it right?)
Thx in advance.
Nasrudin78 said:
Hi , I have a One (M7) and I'm planning to send it back to HTC in order to fix the purple tint problem.
I'm S-off and I want to Lock the bootloader and returning to Stock + S-on.
I'll follow these steps from http://forum.xda-developers.com/showthread.php?t=2541082 Post #4 but i have doubts marked in blue
Step 0: -not in the previous thread link- I have hboot 1.57. Do I have to move to 1.44 ?
Step 1: let's get rid of TAMPERED (if it's there) and set you back to LOCKED (not relocked)
and confirm no TAMPERED and LOCKED status. (I have UNLOCKED status, so I'm only have to set it to LOCKED, isn't it?)
Step 2: Flash your RUU.zip
Download your MID & CID compatible RUU.zip: http://www.htc1guru.com/downloads/ruu-zip-downloads/
Rename the downloaded file to ruu.zip (careful about ruu.zip.zip in Windows)
(My mid is PN0710000 and cid= HTC__304 so I'll flash
RUU+Zip+M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed)
Do I need first to flash a stock splash?. Currently, I have Maximus 53 HD rom installed (with its own splash bootloader).
Step 3: if YOU decide to go S-On (Note: this should only be done for warranty or selling the phone, it is not needed for OTAs)
fastboot oem writesecureflag 3
( with 1.44 hboot, doesn't exist the possibility of a TEMPERED boot loop, Is it right?)
Thx in advance.
Click to expand...
Click to collapse
You need to downgrade hboot to 1.44 or you will get a fail when you use the ruu.
Also hboot 1.44 has the ability to boot a custom recovery without actually flashing it to the device and returning to s-on on hboots above 1.55 could lead to Tampered message returning after you've completed the process. Then you will need to go back to s-off and start again. So it is best to downgrade hboot to 1.44, lock bootloader remove tampered, run the ruu. Then take the first (and only the first) OTA update. If the update installs OK then it's safe to say you can go back to s-on. :good:
Sent from my HTC One using Tapatalk
But what happens if I decide not to take 1st OTA update? Can i omit this step and run "fastboot oem ...3" (taking into account that I flashed hboot 1.44) ?
Nasrudin78 said:
But what happens if I decide not to take 1st OTA update? Can i omit this step and run "fastboot oem ...3" (taking into account that I flashed hboot 1.44) ?
Click to expand...
Click to collapse
Everything must be stock 100% before you go back to s-on. That's why you must flash the RUU. You don't have to take the first OTA, bit it's a good way for ensuring it's safe to turn s-on. If the OTA installs OK then you have unmodified system and it's safe to lock it up. The RUU should do the Job it's just an extra precaution.
Sent from my HTC One using Tapatalk
Uppps, but now that I'm reading more in detail... If I decide to take the 1st OTA just for extra checking, Can this OTA change the hboot (I mean, hboot 1.44 to more actual one)
doing "fastboot oem ...3" impossible due to the Tampered message protection in hboot > 1.55?
Thx
Danny201281 said:
Everything must be stock 100% before you go back to s-on. That's why you must flash the RUU. You don't have to take the first OTA, bit it's a good way for ensuring it's safe to turn s-on. If the OTA installs OK then you have unmodified system and it's safe to lock it up. The RUU should do the Job it's just an extra precaution.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Hi again,
I downgraded hboot to 1.44, but I realized that exists this Lollipop RUU.zip --> PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.22_Radio_4T.35.3218.16_10.33Q.1718.01L_release_430964_signed.zip
(https://www.androidfilehost.com/?fid=24052804347763626)
Is it a good idea,having hboot 1.44, flashing this .zip, instead of Jellybean -RUU+Zip+M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A .13.3231.27_10.31.1131.05_release_310878_signed-? and therefore ,accept 1st OTA and apply fastboot oem ...3 afterwards?
I'm scared because i saw ((status read failed (Too many links))) when I only tested a "fastboot getvar all" command:
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: <DEL>
(bootloader) imei: <DEL>
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__304
(bootloader) battery-status: good
(bootloader) battery-voltage: 4165mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
Execution time is 1(s)
Click to expand...
Click to collapse
And finally, If it's not possible and I install JB_50 RUU.zip, can I accept ALL OTA's up to Lollipop and then apply "fastboot oem writesecureflag 3"?
Thx!
Nasrudin78 said:
Hi again,
I downgraded hboot to 1.44, but I realized that exists this Lollipop RUU.zip --> PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.22_Radio_4T.35.3218.16_10.33Q.1718.01L_release_430964_signed.zip
(https://www.androidfilehost.com/?fid=24052804347763626)
Is it a good idea,having hboot 1.44, flashing this .zip, instead of Jellybean -RUU+Zip+M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A .13.3231.27_10.31.1131.05_release_310878_signed-? and therefore ,accept 1st OTA and apply fastboot oem ...3 afterwards?
Click to expand...
Click to collapse
Even with these new RUU's you still need to downgrade to go back to s-on. You must go s-on with a hboot 1.55 or below
I'm scared because i saw ((status read failed (Too many links))) when I only tested a "fastboot getvar all" command:
Click to expand...
Click to collapse
This is normal with hboot 1.44 and nothing to worry about. All devices with hboot 1.44 give that error after getvar all.
And finally, If it's not possible and I install JB_50 RUU.zip, can I accept ALL OTA's up to Lollipop and then apply "fastboot oem writesecureflag 3"?
Thx!
Click to expand...
Click to collapse
No you must go s-on after the first OTA from JB_50 RUU.zip. Further OTA updates will upgrade you to hboot 1.56 then it's to late to go s-on without risking TAMPERED flag returning :good:
Sent from my HTC One using Tapatalk
Danny201281 said:
Even with these new RUU's you still need to downgrade to go back to s-on. You must go s-on with a hboot 1.55 or below
This is normal with hboot 1.44 and nothing to worry about. All devices with hboot 1.44 give that error after getvar all.
No you must go s-on after the first OTA from JB_50 RUU.zip. Further OTA updates will upgrade you to hboot 1.56 then it's to late to go s-on without risking TAMPERED flag returning :good:
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Ok.
So, what do you suggest me to install, supposing I have hboot 1.44 installed, Lollipop RUU or JB RUU?
I don't understand when you say this:
No you must go s-on after the first OTA from JB_50 RUU.zip. Further OTA updates will upgrade you to hboot 1.56 then it's to late to go s-on without risking TAMPERED flag returning
Click to expand...
Click to collapse
If I run JB_RUU, Doesn't it change hboot version even if I take only 1st OTA?
Otherwise, If I run Lollipop_RUU doesn't it change hboot version even if I take only 1st OTA?
Why do 2nd,3rd OTA and so on change hboot and not 1st (only for understanding the reason)?
I'm aware that hboot > 1.54 adds "TAMPERED" ...
Thx
Nasrudin78 said:
Ok.
So, what do you suggest me to install, supposing I have hboot 1.44 installed, Lollipop RUU or JB RUU?
I don't understand when you say this:
If I run JB_RUU, Doesn't it change hboot version even if I take only 1st OTA?
Otherwise, If I run Lollipop_RUU doesn't it change hboot version even if I take only 1st OTA?
I'm aware that hboot > 1.54 adds "TAMPERED" ...
Thx
Click to expand...
Click to collapse
You must flash the jb ruu. After that you will still be on hboot 1.44.
Then you can take OTA updates. The first OTA will update hboot to 1.54. It is still safe to go back to s-on because your below hboot 1.56
Technically you can also take the next OTA up to hboot 1.55. But I don't recommend it. You won't gain anything from it and it increases the risk of problems later on.
Sent from my HTC One using Tapatalk
Danny201281 said:
You must flash the jb ruu. After that you will still be on hboot 1.44.
Then you can take OTA updates. The first OTA will update hboot to 1.54. It is still safe to go back to s-on because your below hboot 1.56
Technically you can also take the next OTA up to hboot 1.55. But I don't recommend it. You won't gain anything from it and it increases the risk of problems later on.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
And what happens if technical support receives the terminal with JB?
I mean, They asked me if my terminal had the last firmware version, because although I explained them that it was a HW problem, they insist to go last version and check if it fixes .
Then if I send the terminal (let's supose up to hboot 1.55 and JB) they would discover that I'm hiding something to them...
That's the reason I want to let the terminal with the latest firmware and Android version...
Thx
Danny201281 said:
You must flash the jb ruu. After that you will still be on hboot 1.44.
Then you can take OTA updates. The first OTA will update hboot to 1.54. It is still safe to go back to s-on because your below hboot 1.56
Technically you can also take the next OTA up to hboot 1.55. But I don't recommend it. You won't gain anything from it and it increases the risk of problems later on.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Let me explain what I'm planning to do and tell me if it's a good idea or not.
(with hboot 1.44 also installed)
Option 1:
htc_fastboot flash zip LP.zip (x2)
Apply 1st OTA (risk of TAMPERING??)
SOFF -> SON
Click to expand...
Click to collapse
Option 2: (safer??)
fastboot flash zip JB.zip (x2)
Apply 1st OTA ( here I'd have hboot 1.54)
SOFF -> SON
Apply 2nd, 3rd, and so OTA's up to LP and last firmware (risk of TAMPERING??)
Click to expand...
Click to collapse
Thanks, that's my last question. Sorry
Nasrudin78 said:
Let me explain what I'm planning to do and tell me if it's a good idea or not.
(with hboot 1.44 also installed)
Thanks, that's my last question. Sorry
Click to expand...
Click to collapse
Definitely option 2 :good: Follow nkk71's guide here http://forum.xda-developers.com/showpost.php?p=47794203&postcount=4
Using the JB ruu you have. And it will be fine
Sent from my HTC One using Tapatalk
Danny201281 said:
Definitely option 2 :good: Follow nkk71's guide here http://forum.xda-developers.com/showpost.php?p=47794203&postcount=4
Using the JB ruu you have. And it will be fine
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Thanks Danny,
Option 2 worked like a charm! But i spent more than 3hours during the overall OTA update process. LOL!