[Q] No Mainver code! unknown firmware version - One (M7) Q&A, Help & Troubleshooting

Hello everyone,
I have a HTC One M7_UL GSM and I am wanting to upgrade the firmware but I cannot see it when I type the command getvar all, Its just blank next to the Mainver: everything else is showing something there,
I have 1.54 Hboot and am S-OFF with latest twrp 2.8.0.0 and Cyanogenmod 11 (M9 Snapshot Build)
any help greatly appreciated I do not want to mess the phone up.

JamieBlues said:
Hello everyone,
I have a HTC One M7_UL GSM and I am wanting to upgrade the firmware but I cannot see it when I type the command getvar all, Its just blank next to the Mainver: everything else is showing something there,
I have 1.54 Hboot and am S-OFF with latest twrp 2.8.0.0 and Cyanogenmod 11 (M9 Snapshot Build)
any help greatly appreciated I do not want to mess the phone up.
Click to expand...
Click to collapse
Does the phone boot into OS? If so, then it was overwritten during either the flash of an earlier version of TWRP or Cyanogenmod. If you were to flash a new firmware then it would be restored.

majmoz said:
Does the phone boot into OS? If so, then it was overwritten during either the flash of an earlier version of TWRP or Cyanogenmod. If you were to flash a new firmware then it would be restored.
Click to expand...
Click to collapse
Thanks for your reply, It does boot up normally and the phone is perfectly fine so your saying it has been overwritten by either the recovery or custom rom and thats why it isnt showing?
based on this i could flash the latest firmware 6.09.401.5?
Again Thanks.

JamieBlues said:
Thanks for your reply, It does boot up normally and the phone is perfectly fine so your saying it has been overwritten by either the recovery or custom rom and thats why it isnt showing?
based on this i could flash the latest firmware 6.09.401.5?
Again Thanks.
Click to expand...
Click to collapse
As long as it is higher or equal to your version, and if you are s-on you will have to lock your bootloader.

majmoz said:
As long as it is higher or equal to your version, and if you are s-on you will have to lock your bootloader.
Click to expand...
Click to collapse
This is why ive posted this thread mate because i dont know if it is higher or equal as i have said there is no firmware version visable i think it should be fine i cant see me having an earlier version than 6.XXXXX

JamieBlues said:
This is why ive posted this thread mate because i dont know if it is higher or equal as i have said there is no firmware version visable i think it should be fine i cant see me having an earlier version than 6.XXXXX
Click to expand...
Click to collapse
you can more or less infer your firmware version, from hboot version:
hboot 1.44 = 1.xx.xxx.x
hboot 1.54 = 2.xx.xxx.x
hboot 1.55 = 3.xx.xxx.x
hboot 1.56 = 4.xx.xxx.x (in some rare cases 5.xx)
hboot 1.57 = 5.xx.xxx.x and 6.xx.xxx.x
however, i would recommend you flash them incrementally, since firmwares are usually extracted from OTAs they expect the previous changes to already have been applied, so depending on the firmware package you intend on using (some of them have been repackaged to include previous changes), you could end up in trouble.
(for example, flashing a 5.xx ota firmware while on 3.xx or lower firmware will result in QHSUSB_DLOAD mode, and you'd have to try [UNBRICK][BETA] HTC Unbricking Project)
so i recommend you flash them incrementally.

nkk71 said:
you can more or less infer your firmware version, from hboot version:
hboot 1.44 = 1.xx.xxx.x
hboot 1.54 = 2.xx.xxx.x
hboot 1.55 = 3.xx.xxx.x
hboot 1.56 = 4.xx.xxx.x (in some rare cases 5.xx)
hboot 1.57 = 5.xx.xxx.x and 6.xx.xxx.x
however, i would recommend you flash them incrementally, since firmwares are usually extracted from OTAs they expect the previous changes to already have been applied, so depending on the firmware package you intend on using (some of them have been repackaged to include previous changes), you could end up in trouble.
(for example, flashing a 5.xx ota firmware while on 3.xx or lower firmware will result in QHSUSB_DLOAD mode, and you'd have to try [UNBRICK][BETA] HTC Unbricking Project)
so i recommend you flash them incrementally.
Click to expand...
Click to collapse
OK Thanks for the advice still i dont know what firmware it is even if it is 2.XXXXX because im on Hboot 1.54 but i geuss i could start with just one increment up from the lowest 2.XXXXX version only thing is im paranoid about attempting to flash an older firmware and it mess up the phone.
Again a big thanks to everyone who has replied.

JamieBlues said:
OK Thanks for the advice still i dont know what firmware it is even if it is 2.XXXXX because im on Hboot 1.54 but i geuss i could start with just one increment up from the lowest 2.XXXXX version only thing is im paranoid about attempting to flash an older firmware and it mess up the phone.
Again a big thanks to everyone who has replied.
Click to expand...
Click to collapse
are you s-off? then you can flash unsigned firmware, and you can go straight to 3.62.401.1
i personally use these: http://forum.xda-developers.com/showthread.php?t=2365506
(in that thread, even the 6.09.401.5 firmware has all the previous files included so it should be safe to go directly to 6.09, but i personally prefer incremental, just in case)
can you post a "fastboot getvar al"l (excluding IMEI and s/n)
PS: the real problem was for people with 3.xx firmware or lower going to 5.xx firmware (from OTA) which was missing SBL3 from 4.xx (another Secondary Bootloader), which would cause the device to go into QHSUSB_DLOAD

nkk71 said:
are you s-off? then you can flash unsigned firmware, and you can go straight to 3.62.401.1
i personally use these: http://forum.xda-developers.com/showthread.php?t=2365506
(in that thread, even the 6.09.401.5 firmware has all the previous files included so it should be safe to go directly to 6.09, but i personally prefer incremental, just in case)
can you post a "fastboot getvar al"l (excluding IMEI and s/n)
PS: the real problem was for people with 3.xx firmware or lower going to 5.xx firmware (from OTA) which was missing SBL3 from 4.xx (another Secondary Bootloader), which would cause the device to go into QHSUSB_DLOAD
Click to expand...
Click to collapse
Yes i am S-OFF and here is my 'getvar all'
D:\Jay's Data\Android\Fastboot>adb reboot bootloader
D:\Jay's Data\Android\Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.5555
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXXXXXXXX
(bootloader) imei: XXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3791mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(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.069s

JamieBlues said:
Yes i am S-OFF and here is my 'getvar all'
D:\Jay's Data\Android\Fastboot>adb reboot bootloader
D:\Jay's Data\Android\Fastboot>fastboot getvar all
(bootloader) version-bootloader: 1.54.5555
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
all: Done!
finished. total time: 0.069s
Click to expand...
Click to collapse
fyi, looks like you have a rumrunner/firewater ENG hboot in there, that will be gone once you update, you'll be back on normal hboot.
I would personally flash the following versions incrementally from vomers thread
- 3.62.401.1
- 4.19.401.8
- 4.19.401.11
- 5.11.401.10
- 6.09.401.5
(there is some redundancy doing this since the versions from 4.19.401.11 upwards, vomer has included all previous updates too, but better safe than sorry)

nkk71 said:
fyi, looks like you have a rumrunner/firewater ENG hboot in there, that will be gone once you update, you'll be back on normal hboot.
I would personally flash the following versions incrementally from vomers thread
- 3.62.401.1
- 4.19.401.8
- 4.19.401.11
- 5.11.401.10
- 6.09.401.5
(there is some redundancy doing this since the versions from 4.19.401.11 upwards, vomer has included all previous updates too, but better safe than sorry)
Click to expand...
Click to collapse
Thank you so much for all your help i successfully flashed all firmwares incrementally and the phone does feel alot more snappy :laugh:

Related

[Q] Unable to unlock, flash recovery or s-off or RUU

I have one hell of a problem.
Status of device:
-Google play edition kit kat htc one (converted from att version)
-No recovery, recovery is INACCESSABLE
-No root, and temp root does not work as well.
-Stock att RUU's not working (as of yet)
-I have tried firewatter, revone and rum runner to try and root so i can get s-off but unable.
-For whatever reason fastboot oem unlock does not as well as the unlock token.
Things i haven't tried because i cant find them:
-Google play edition RUU.exe file
-A standalone RUU for downgrading hboot 1.54 (which is my device currently)
-A modified RUU.exe that will allow me to restore to stock ANYTHING
-A RUU.zip that i can flash manually without s-off
Any suggestions?
j.sax.riley said:
I have one hell of a problem.
Status of device:
-Google play edition kit kat htc one (converted from att version)
-No recovery, recovery is INACCESSABLE
-No root, and temp root does not work as well.
-Stock att RUU's not working (as of yet)
-I have tried firewatter, revone and rum runner to try and root so i can get s-off but unable.
-For whatever reason fastboot oem unlock does not as well as the unlock token.
Things i haven't tried because i cant find them:
-Google play edition RUU.exe file
-A standalone RUU for downgrading hboot 1.54 (which is my device currently)
-A modified RUU.exe that will allow me to restore to stock ANYTHING
-A RUU.zip that i can flash manually without s-off
Any suggestions?
Click to expand...
Click to collapse
you probably have to redo the process at http://www.htcdev.com/bootloader/
redo the process and try to unlock your bootloader with the new unlock.bin
just follow the steps
OK.. Explain this. If you converted. You went SOFF. Then how do you end up with LOCKED Bootloader and SJON?
sent from my mobile device
I have had the same problem few weeks ago
First unlock your bootloader again with a new unlock.bin ...redo the hole process
http://www.htcdev.com/bootloader/
Second regain S-Off with rumrunner
Finaly you should be able to restore with a RUU
Dosent go
Boachti said:
I have had the same problem few weeks ago
First unlock your bootloader again with a new unlock.bin ...redo the hole process
Second regain S-Off with rumrunner
Finaly you should be able to restore with a RUU
Click to expand...
Click to collapse
It says on the prompt that it completed successfully with the unlock, however i do not receive a prompt on the device stating the developer options to accept or deny.
I will proceed as if i did and try my att ruu to try and update the device.
I tried with a google ruu and get signature verify fail, i think that i get the same issue with the att ruu.
IF you can suggest a RUU that will help me out of the situation i would really appreciate it.
Also if there is any reason why rum runner will not complete, i can swear adb is up everything should work but it just will not complete.
j.sax.riley said:
It says on the prompt that it completed successfully with the unlock, however i do not receive a prompt on the device stating the developer options to accept or deny.
I will proceed as if i did and try my att ruu to try and update the device.
I tried with a google ruu and get signature verify fail, i think that i get the same issue with the att ruu.
IF you can suggest a RUU that will help me out of the situation i would really appreciate it.
Also if there is any reason why rum runner will not complete, i can swear adb is up everything should work but it just will not complete.
Click to expand...
Click to collapse
Turning security back to ''on'' and relocking your bootloader on GPE was a bad decision, you probably bricked your device forever.
This is discussed in this thread: http://forum.xda-developers.com/showthread.php?t=2547894
With S-ON and Locked (Re-Locked) bootloader, your only hope is to flash a RUU of same or higher version than the version currently installed on your phone. You can't downgrade anything with s-on using a ruu.exe neither a ruu.zip. You are stuck until htc release a newer gpe ruu.
Post the output of ''fastboot getvar all'' minus your IMEI and SERIALNO
alray said:
Turning security back to ''on'' and relocking your bootloader on GPE was a bad decision, you probably bricked your device forever.
This is discussed in this thread:
With S-ON and Locked (Re-Locked) bootloader, your only hope is to flash a RUU of same or higher version than the version currently installed on your phone. You can't downgrade anything with s-on using a ruu.exe neither a ruu.zip. You are stuck until htc release a newer gpe ruu.
Post the output of ''fastboot getvar all'' minus your IMEI and SERIALNO
Click to expand...
Click to collapse
Is there any chance of spoofing the ruu.zip to make it look like a higher verison?
If not that can i just flash a recovery image even if its stock so i can have a recovery as i currently don't even have that which i think is the source of my problems.
j.sax.riley said:
Is there any chance of spoofing the ruu.zip to make it look like a higher verison?
If not that can i just flash a recovery image even if its stock so i can have a recovery as i currently don't even have that which i think is the source of my problems.
Click to expand...
Click to collapse
Unfortunately no. ''spoofing'' the ruu will require to decrypt it. With s-on you can't flash a decrypted ruu, you can only flash a ruu that is signed with HTC private key (decrypted ruu can't be signed back with HTC private key). S-OFF would have saved your phone in this case.
The only way to flash the stock recovery in your case is to flash a signed firmware.zip of the same of higher version.
Still waiting your ''fastboot getvar all'' output
alray said:
Unfortunately no. ''spoofing'' the ruu will require to decrypt it. With s-on you can't flash a decrypted ruu, you can only flash a ruu that is signed with HTC private key (decrypted ruu can't be signed back with HTC private key). S-OFF would have saved your phone in this case.
The only way to flash the stock recovery in your case is to flash a signed firmware.zip of the same of higher version.
Still waiting your ''fastboot getvar all'' output
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.1700.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4318mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e82187e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
j.sax.riley said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.1700.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4318mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e82187e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Afaik, there is no ruu you can flash. Your version is 3.62.1700.1 and the latest ruu I can find is 3.58.1700.5 which is a downgrade (require S-OFF) You'll need to find or wait for a ruu higher or equal to 3.62.1700.1
alray said:
Afaik, there is no ruu you can flash. Your version is 3.62.1700.1 and the latest ruu I can find is 3.58.1700.5 which is a downgrade (require S-OFF) You'll need to find or wait for a ruu higher or equal to 3.62.1700.1
Click to expand...
Click to collapse
That sux.
Are you sure there is no other way?
The htc regular version stock is version 4 something and so i was hopping that would override any bull**** i have going on.
i tired temp roots to see if i can s-off in os with firewater but i was unsuccesffully at gaining temp root.
Its funny to me because i swear reading somewhere that "andoid 4.4 is great" dont even have to root because of app ops or something but its obvious now thats a load of b.s and i should have just always run rooted as that has never done me wrong.
Do you know where i would find a ruu when one comes out? as one probably will with 4.4.3 coming out soon.
j.sax.riley said:
That sux.
Are you sure there is no other way?
Click to expand...
Click to collapse
If you can't s-off using rumrunner or firewater then no, idt there is other options.
j.sax.riley said:
The htc regular version stock is version 4 something and so i was hopping that would override any bull**** i have going on.
Click to expand...
Click to collapse
The international version ruu is a .401 base (not .1700) and require to change CID and probably MID. Changing those values require S-OFF!
j.sax.riley said:
Do you know where i would find a ruu when one comes out? as one probably will with 4.4.3 coming out soon.
Click to expand...
Click to collapse
htcdev.com under the ''kernel source code'' section, http://htc1guru.com and http://androidruu.com/?developer=M7
[*] Attempting to acquire root. This will take 5-10 minutes, be patient
error in setsockopt().
Failed to get prepare_kernel_cred address.
Failed to get commit_creds address.
Failed to get ptmx_fops address.
Failed to setup variables.
This is my output from trying temp root with firewater method.
I am not sure what the issue is that is happening but i assume with the first failure the whole system collapses.
Thank you for the help btw, and i will keep my eyes open for a new ruu.
What do i need to be looking for in the ruu to make sure it will work with my phone?
Specific cid and mid?
j.sax.riley said:
What do i need to be looking for in the ruu to make sure it will work with my phone?
Specific cid and mid?
Click to expand...
Click to collapse
must be signed and same or higher version than 3.62.1700.1.
any .1700 version will match your CID and MID (GOOGL01 and PN0712000)
Last question,
Flashing a newer hboot or the "modified gpe bootloader"
Is it possible since im s-off, and will it change anything?
And why wont this zip work?
RUU Zip M7 Google Edition 4.4 3.58.1700.5
Because its version 3.58 and i am 3.62?
I like Htc phones and especially their commitment to bring timely updates.
But.....i do miss being able to use odin and never have to worry if your device gets f-ed up you can always reformat it to stock without trying to get a warranty replacement (which i cant because i'm rocking my google play edition) which is great and totally beats cyanogen mod for stability.
Although....i miss blink feed lol
j.sax.riley said:
Last question,
Flashing a newer hboot or the "modified gpe bootloader"
Is it possible since im s-off, and will it change anything?
Click to expand...
Click to collapse
Fomr the output of your fastboot getvar all, you are S-ON not S-OFF so you won't be able to flash a modifed hboot. Btw, if you flash a modified hboot in the future with s-off, you will brick your device if you s-on again (with a modified hboot)
j.sax.riley said:
And why wont this zip work?
RUU Zip M7 Google Edition 4.4 3.58.1700.5
Because its version 3.58 and i am 3.62?
Click to expand...
Click to collapse
Yes, 3.58 is a downgrade of version from what you have currently on your phone. Downgrading require S-OFF

So confused - OTA Updates & Rooted/Modified M7 - please help!

Hi all,
My girlfriend has a HTC One M7, currentley Rooted with an Unlocked bootloader, Bulletproof Kernel, CWM Recovery, S-On (can't get S-OFF no matter what I try) and running the stock 4.4.2 Sense ROM that came with the phone.
She wants to install an OTA update, obviously this won't work with the phone in it's current state. I've got experience with all of this with my Note II, but the M7 is just a whole different can of worms.
What I've tried:
Getting S-OFF (no luck whatsoever with any tools)
Flashing stock recovery and kernel
Flashing stock recovery and kernel and applying the OTA manually via recovery
I've read everything on here and nothing seems to go in. She just wants to be able to install OTA updates, even if it means unrooting her phone permanently as this will happen each time there is an OTA update.
Someone, please guide me in the right direction! Step by step maybe?
Keep in mind there is no way I can't get S-OFF.
Huge thanks to anyone that can help. I'd be eternally in your debt!!
SmokinWaffle said:
My girlfriend has a HTC One M7, currentley Rooted with an Unlocked bootloader, Bulletproof Kernel, CWM Recovery, S-On (can't get S-OFF no matter what I try) and running the stock 4.4.2 Sense ROM that came with the phone.
She wants to install an OTA update, obviously this won't work with the phone in it's current state. I've got experience with all of this with my Note II, but the M7 is just a whole different can of worms.
Click to expand...
Click to collapse
I suppose the phone is trying to apply to ota update and then show a red triangle with an exclamation mark inside?
What I've tried:
Getting S-OFF (no luck whatsoever with any tools) Any error message when trying to S-OFF? You must use the correct tool for your hboot version (probably firewater) + combination of the correct rom + kernel
Flashing stock recovery and kernel --> You must have stock recovery for ota, ota will not install using a custom one.
Flashing stock recovery and kernel and applying the OTA manually via recovery --> appyling the ota manually from stock recovery require s-off
Click to expand...
Click to collapse
I've read everything on here and nothing seems to go in. She just wants to be able to install OTA updates, even if it means unrooting her phone permanently as this will happen each time there is an OTA update
Click to expand...
Click to collapse
.
http://forum.xda-developers.com/showpost.php?p=52894276&postcount=9
http://forum.xda-developers.com/showpost.php?p=53151895&postcount=23
Keep in mind there is no way I can't get S-OFF.
Click to expand...
Click to collapse
still not sure about this, unless you get the "whelp" message from firewater...
post the output of fastboot getvar all except the imei number and serialno
alray said:
I suppose the phone is trying to apply to ota update and then show a red triangle with an exclamation mark inside?
Click to expand...
Click to collapse
Yep!
alray said:
http://forum.xda-developers.com/showpost.php?p=52894276&postcount=9
http://forum.xda-developers.com/showpost.php?p=53151895&postcount=23
Click to expand...
Click to collapse
Interesting. I don't have the phone with me at the moment and it's late but I'll try to do the POWERUP + VOL tomorrow at some point, I'll get her to try stock recovery + kernel then do it and see what it's stopping at.
alray said:
still not sure about this, unless you get the "whelp" message from firewater...
Click to expand...
Click to collapse
Didn't get that message, just keeps going indefinetley or stops, and doesn't S-OFF. Tried Firewater, Revone, RumRunner, if there is another then I've almost certainly tried it, followed all the guides including the one that flashed Android Revolution...no idea..
alray said:
post the output of fastboot getvar all except the imei number and serialno
Click to expand...
Click to collapse
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.25.3263.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: [I]XXXXXXXXXXXX[/I]
(bootloader) imei: [I]XXXXXXXXXXXXXXX[/I]
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3798mV
(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
all: Done!
finished. total time: 0.047s
Thanks for the prompt reply, really appreciate it and any help you can give.
SmokinWaffle said:
Yep!
Interesting. I don't have the phone with me at the moment and it's late but I'll try to do the POWERUP + VOL tomorrow at some point, I'll get her to try stock recovery + kernel then do it and see what it's stopping at.
Didn't get that message, just keeps going indefinetley or stops, and doesn't S-OFF. Tried Firewater, Revone, RumRunner, if there is another then I've almost certainly tried it, followed all the guides including the one that flashed Android Revolution...no idea..
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.25.3263.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: [I]XXXXXXXXXXXX[/I]
(bootloader) imei: [I]XXXXXXXXXXXXXXX[/I]
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3798mV
(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
all: Done!
finished. total time: 0.047s
Thanks for the prompt reply, really appreciate it and any help you can give.
Click to expand...
Click to collapse
your version-main? (rom version) Go in settings --> About --> Software info --> Rom version
maybe there is a ruu you could use to restore the phone(4.19.401.9), if it match your version
---------- Post added at 04:40 PM ---------- Previous post was at 04:35 PM ----------
you can also flash the stock 5.11.401.10 rom, recovery and firmware available on ARHD website
http://android-revolution-hd.blogspot.ca/p/android-revolution-hd-mirror-site-var.html
http://forum.xda-developers.com/showthread.php?t=2224752
alray said:
your version-main? (rom version) Go in settings --> About --> Software info --> Rom version
maybe there is a ruu you could use to restore the phone(4.19.401.9), if it match your version
---------- Post added at 04:40 PM ---------- Previous post was at 04:35 PM ----------
you can also flash the stock 5.11.401.10 rom, recovery and firmware available on ARHD website
http://android-revolution-hd.blogspot.ca/p/android-revolution-hd-mirror-site-var.html
http://forum.xda-developers.com/showthread.php?t=2224752
Click to expand...
Click to collapse
4.19.401.11
What exactly is the function of the RUU? I can't seems to get my head around it..
I'm guessing the ARHD steps are to try to get S-OFF?
SmokinWaffle said:
4.19.401.11
What exactly is the function of the RUU? I can't seems to get my head around it..
Click to expand...
Click to collapse
forget the ruu, your phone version is higher than the ruu. flashing a ruu (4.11.401.10) with a lower version than on your phone(4.11.401.11) require s-off.
I'm guessing the ARHD steps are to try to get S-OFF?
Click to expand...
Click to collapse
No, this is the latest stock rom(5.11.401.10) for your phone model (MID: PN0710000 and CID:HTC__001) including android 4.4.2 and sense 6.0
You can flash this stock odexed rom(5.11.401.10) from custom recovery, then flash the stock recovery(5.11.401.10) over the custom one and your phone will be stock and ready to take future ota update. You may also want to update firmware to 5.11.401.10
So after flashing that rom and stock recovery, ota would be ready to roll? Would the kernel matter?
What's the purpose / Difference of firmware and how is it updated? On my note II it was just choose a rom choose a kernel and off you go. This is so much more involved
SmokinWaffle said:
So after flashing that rom and stock recovery, ota would be ready to roll? Would the kernel matter?
Click to expand...
Click to collapse
stock kernel in included in the rom (boot.img) so if you don't flash any other kernel it should be fine.
What's the purpose / Difference of firmware and how is it updated? On my note II it was just choose a rom choose a kernel and off you go. This is so much more involved
Click to expand...
Click to collapse
firmware is all the low level code required for your phone hardware to works with the software (OS)
when speaking about HTC phone, firmware.zip include HBOOT(bootloader), BOOT(kernel), Recovery, Radio and some other stuff. if you want your phone to be 100% stock you need both stock rom + stock firmware to match the same version i.e 5.11.501.10
normally, the firmware is updated at the same time the rom version is updated (from an ota update) If you flash a rom, the rom will be updated but not the firmware.
Updating the firmware manually can be dangerous is you don't know what you are doing and flashing the wrong file. You can update firmware using this command from bootloader (with the correct firmware.zip package in the same folder you have adb and fastboot):
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
also it looks like flashing a 5.x.xxx.x firmware over a 3.x.xxx.x firmware will brick your phone. from what i see, your phone should be on a 4.x.401.x version at the moment, so it theory it should be fine.
Fails on:
>>>setting permissions
set_metadata_recursive: some changes failed
E:Error in /data/media/0/one_5.11.401.10_odexed.zip
(status 7)
Tried 3 different versions of cwm. Bad rom download?
Thinking about it I just re read your above post, could it be because the firmware isn't matched? I read your 'it should be fine' as 'dont update the firmware' not 'its fine to update' which I think is what you meant...
Firmware is 4.19.401.11 however the rom is 5.11.401.10. Can't believe I overlooked this, guess firmware needs to be 5.11.401.10 for the rom to take?
SmokinWaffle said:
Tried 3 different versions of cwm. Bad rom download?
Click to expand...
Click to collapse
No you are using CWM thats the problem. always use TWRP 2.6.3.3
alray said:
No you are using CWM thats the problem. always use TWRP 2.6.3.3
Click to expand...
Click to collapse
Huh?
Is this a requirement of ARHD or....?
Just seems odd
Edit: success!! All seems to work. Thank you. She's overjoyed!!!

[Q] Return to stock again, Q hboot

Hi,
So returning to stock again and Im planning on doing the following
Install the following zip as per video instructions on website.
Select option to include root
Then install this version of SuperSU >
Follow this guide to set the bootloader to LOCKED
Removed root from within SuperSu settings
Enter the following command via fastboot to go S-ON
./fastboot oem writesecureflag 3
However, when I completed this last year I was on hboot 1.54, now after upgrading a few times my setup is:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.06.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3880mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-01dc707e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I will change the cidnum back to VODAP001 before I do any of the above, but how do I get back to hboot 1.54 ?
The following is the status I need to get the phone back to:
(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.161.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT36JW907644
(bootloader) imei: 357864050522398
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4149mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
will the version-main and baseband also be downgraded when I use the Guru_Reset_M7_2.24.161.1.zip file ?
No the version main won't be downgraded with the guru reset file, that file is pretty much rom only, you need the firmware.zip file to do that, you also need it to downgrade your hboot, or an ruu, I've had a look and there is no ruu for Vodafone, however, there is some earlier ota's. You could try downloading those and pull firmware.zip from them, then manually flash that, firmware zip contains things like stock recovery, radio, hboot, partition layouts etc, try and get one which matches the number on the guru reset file, ie search for 2.24.161.xx firmware, flash that first, you will then need to put a custom recovery back on to run the guru reset file, during the installation, select wipe data, install stock recovery and install stock radio, once it's all done and booted at least once, only then lock your bootloader and s-on, be careful when going back s-on though, it's been known for the tampered flag to return, personally I would send it back s-off, high chance they wouldn't even notice.
Just one question, why do you want to root ?, if your returning to stock for warranty then skip that part completely, you won't need root.
You may be able to pull firmware.zip from this ota http://www.htc1guru.com/2013/10/vodafone-ota-2-24-161-1-added/
Seanie280672 said:
No the version main won't be downgraded with the guru reset file, that file is pretty much rom only, you need the firmware.zip file to do that, you also need it to downgrade your hboot, or an ruu, I've had a look and there is no ruu for Vodafone, however, there is some earlier ota's. You could try downloading those and pull firmware.zip from them, then manually flash that, firmware zip contains things like stock recovery, radio, hboot, partition layouts etc, try and get one which matches the number on the guru reset file, ie search for 2.24.161.xx firmware, flash that first, you will then need to put a custom recovery back on to run the guru reset file, during the installation, select wipe data, install stock recovery and install stock radio, once it's all done and booted at least once, only then lock your bootloader and s-on, be careful when going back s-on though, it's been known for the tampered flag to return, personally I would send it back s-off, high chance they wouldn't even notice.
Just one question, why do you want to root ?, if your returning to stock for warranty then skip that part completely, you won't need root.
You may be able to pull firmware.zip from this ota http://www.htc1guru.com/2013/10/vodafone-ota-2-24-161-1-added/
Click to expand...
Click to collapse
need root to remove the TAMPERED flag.
akuma24 said:
need root to remove the TAMPERED flag.
Click to expand...
Click to collapse
Nah you don't, on the guru reset site, there is a bootloader reset tool which you just run from custom recovery.
It will allow you to lock, relock, unlock the bootloader whilst s-off and also remove the tampered flag
http://www.htc1guru.com/guides/guru-bootloader-reset/
Seanie280672 said:
Nah you don't, on the guru reset site, there is a bootloader reset tool which you just run from custom recovery.
It will allow you to lock, relock, unlock the bootloader whilst s-off and also remove the tampered flag
http://www.htc1guru.com/guides/guru-bootloader-reset/
Click to expand...
Click to collapse
Thanks again, can you extract the firmware from this file for me ? I try to extract on a mac and it just zip's the file back up
http://www.htc1guru.com/2013/10/vodafone-ota-2-24-161-1-added/
Then again, Im thinking, is it necessary to downgrade the firmware to version 2.24.161.1, maybe downgrade to 4.06.1540.2 instead
akuma24 said:
Thanks again, can you extract the firmware from this file for me ? I try to extract on a mac and it just zip's the file back up
http://www.htc1guru.com/2013/10/vodafone-ota-2-24-161-1-added/
Then again, Im thinking, is it necessary to downgrade the firmware to version 2.24.161.1, maybe downgrade to 4.06.1540.2 instead
Click to expand...
Click to collapse
I'm not near a computer at the moment so can't do that sorry, 161 is Vodafone, the other one you mentioned is 1540 developer edition, as you are s-off you can flash any ruu, but it might get questioned.
Seanie280672 said:
I'm not near a computer at the moment so can't do that sorry, 161 is Vodafone, the other one you mentioned is 1540 developer edition, as you are s-off you can flash any ruu, but it might get questioned.
Click to expand...
Click to collapse
what about 4.19.401.11, is that developer also ?
akuma24 said:
what about 4.19.401.11, is that developer also ?
Click to expand...
Click to collapse
That's WWE unbranded Europe, that's what I have on my phone, that would work, change your cid to HTC__001 first then get the ruu 4.19.401.9 and run it, you'll be full stock in no time.
4.19.401.11 is just an ota
Seanie280672 said:
That's WWE unbranded Europe, that's what I have on my phone, that would work, change your cid to HTC__001 first then get the ruu 4.19.401.9 and run it, you'll be full stock in no time.
4.19.401.11 is just an ota
Click to expand...
Click to collapse
what about this firmware:
http://d-h.st/WO9 (2.24.401.1)
akuma24 said:
what about this firmware:
http://d-h.st/WO9 (2.24.401.1)
Click to expand...
Click to collapse
You may as well just run the 401 ruu which will update the firmware too and hboot, it will do everything for you.
Seanie280672 said:
You may as well just run the 401 ruu which will update the firmware too and hboot, it will do everything for you.
Click to expand...
Click to collapse
Wouldnt the fact I have a WWE rom on my phone with a cid of VODA raise eyebrows over at htc ? True I can change the cid to HTC__xx but do they not have a record of which phone was given to which network etc
akuma24 said:
Wouldnt the fact I have a WWE rom on my phone with a cid of VODA raise eyebrows over at htc ? True I can change the cid to HTC__xx but do they not have a record of which phone was given to which network etc
Click to expand...
Click to collapse
I got mine from Vodafone UK, unbranded on HTC__001, you can't send it unbranded with a Vodafone cid, you will need to send it with the HTC cid
Seanie280672 said:
I got mine from Vodafone UK, unbranded on HTC__001, you can't send it unbranded with a Vodafone cid, you will need to send it with the HTC cid
Click to expand...
Click to collapse
Have downloaded the following and it contains the firmware for 4-19-161-11
http://www.htc1guru.com/dld/ota_m7_...-63-161-6_release_356881mwn487m942rk64ep-zip/
The download for 2.24.161.1 on the site times out after download 142MB so think it is corrupt.
The plan is to flash the firmware from 4-19-161-11, then run the guru reset for 2.24.161.1 and take the OTA's to bring it up to whatever it should currently be ?
These phones were so easy to reset back in the Hero days
akuma24 said:
Have downloaded the following and it contains the firmware for 4-19-161-11
http://www.htc1guru.com/dld/ota_m7_...-63-161-6_release_356881mwn487m942rk64ep-zip/
The download for 2.24.161.1 on the site times out after download 142MB so think it is corrupt.
The plan is to flash the firmware from 4-19-161-11, then run the guru reset for 2.24.161.1 and take the OTA's to bring it up to whatever it should currently be ?
These phones were so easy to reset back in the Hero days
Click to expand...
Click to collapse
Yu can't do that, the 4xxxxx firmware will contain too high a hboot for the otas to work, although the guru reset file will install, the otas will lead to a bootloop due to you already having a higher hboot
Seanie280672 said:
Yu can't do that, the 4xxxxx firmware will contain too high a hboot for the otas to work, although the guru reset file will install, the otas will lead to a bootloop due to you already having a higher hboot
Click to expand...
Click to collapse
Right, I need someone to fix that link then, have posted it in the collection thread, hopefully someone fixes it
Right so decided Im short on time so will run the following after changing the cid to HTC__001
http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
This will downgrade the firmware and also flash the stock rom for htc europe.
Ill then need to change the recovery in order to run the following:
http://www.htc1guru.com/guides/guru-bootloader-reset/
then reflash stock recovery and finally remove s-off
????
akuma24 said:
Right, I need someone to fix that link then, have posted it in the collection thread, hopefully someone fixes it
Click to expand...
Click to collapse
which link, maybe there is another ?
---------- Post added at 04:36 PM ---------- Previous post was at 04:32 PM ----------
im home now so im just downloading that ota, see if it contains a firmware.zip that I can extract, then i'll upload it for you if its there.
the download keeps getting reset, this site is starting to do my head in.
Seanie280672 said:
which link, maybe there is another ?
---------- Post added at 04:36 PM ---------- Previous post was at 04:32 PM ----------
im home now so im just downloading that ota, see if it contains a firmware.zip that I can extract, then i'll upload it for you if its there.
Click to expand...
Click to collapse
this link here http://www.htc1guru.com/2013/10/vodafone-ota-2-24-161-1-added/
think the one you are downloading
akuma24 said:
this link here http://www.htc1guru.com/2013/10/vodafone-ota-2-24-161-1-added/
think the one you are downloading
Click to expand...
Click to collapse
yeah, he has a problem with someone hacking that site and resetting the downloads every 5 mins or so, im just trying to source the file from somewhere else.
Seanie280672 said:
yeah, he has a problem with someone hacking that site and resetting the downloads every 5 mins or so, im just trying to source the file from somewhere else.
Click to expand...
Click to collapse
Thanks, would really appreciate it if you could an alternative download source\link

[Q&A] VomerGuides [M7]: S-OFF, SuperCID, Firmware Upgrade & Custom Recovery

[Q&A] VomerGuides [M7]: S-OFF, SuperCID, Firmware Upgrade & Custom Recovery
Q&A for VomerGuides [M7]: S-OFF, SuperCID, Firmware Upgrade & Custom Recovery
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Just a general question.
Does model ID of the phone has to do anything with this?
my HTC One is an international variant and MID: PN0711000
Thanks
upon firmware
i am very sorry to disturb by a possibly noob question , but when downloading from OP it says the firmware is for m7 dual sim version , i would just like to know if it is OK to flash it on a single sim variant.....) thanks in advance, and You are doing really useful job , ThankYou))!
6.09.401.11 Latest firmware
since my HTC ONE is modelid: PN0714000
can i flash the following link firmware
http://forum.xda-developers.com/htc-one/development/firmware-6-09-401-11-red-warning-wipe-t2963199
as i found the android-info.txt , i only see the modelid: PN0710000
so im wondering can i flash this firmware
njuneja said:
Does model ID of the phone has to do anything with this?
my HTC One is an international variant and MID: PN0711000
Thanks
Click to expand...
Click to collapse
I have same question, can we use any firmware we want or not?
CID: HTC_332
MID: PN0711000
I need a room please FOR HTC ONE-M7
I have a phone in Italy, and I needed a room for him.
relocked
M7_UL PVT SHIP S-OFF RH
CID-TIM_401
HBOOT-1.57.0000
RADIO-4A.23.3263.28
OPENDSP-V32.120.274.0909
OS-4.20.901.17
eMMC-boot 2048MB
FEB 14 2014,16:5100.12992
!!!!!!
Sure is some **** in those download files. DONT DOWNLOAD ! ! !
hello
hi guys. i have a question.
do i need to flash a new rom after update the firmware on my htc one?
or can i just update the firmware and do nothing on the rom.
hboot-1.57 in one m7ul s-on
Can I download hboot-1.57 in one m7ul s-on
In less than 1.56 ... 1.55 ? ?
Ī¤hanks .
which firmware do I start with
@vomer, I'm unlocked with custom recovery, rooted and have s-off, question, I'm on the firmware version my phone shipped with, 5.12.502.2......what do I flash here for latest firmware, do I do the 5.11.xxx (401 or 1540? - 1540 is the developer build no?, why is that the only developer one in that list, i don't do both the 401 and 1540 correct?) or do I skip 5.11 and go straight to the latest 6.0.xxx ? I ask because the 5.12 was released in August where as the 5.11 is listed as May or something.
Thanks and let me know, great guide!
latest firmwares
oh and @vomer, are you going to update this with the latest firmwares for m7_ul? I noticed there is now a 6.0.11 and 6.0.12 - i tried to flash them from android revolution but my device bricked / hung on boot, had to reset to stock with guru reset and flash original firmware...which ultimately means i wasted a bunch of time previously...later noticed that ARHD requires re-locked bootloader...maybe this is what bricked it?? Did you remove that requirement from the ones you posted and I just didn't know? or were those firmwares just not compatible with the stock rom based on 5.12 from att from before I changed my CID with your guide? I'm really not sure what happened but I had waited to flash a custom rom but couldn't once i tried to flash later than your 6.0.10 listed (and yes I had changed my CID via your guide and had used .401 builds - does that number even matter once you're super CID?
Thanks!
am i screwed?
Sup,
Been on the XDA forums for two days now (totally rad) trying to return my phone to stock and bootloader locked for warranty trying all sorts of methods and I think I am screwed but I would love anyone to clarify
status:
-nandroids, OTA and guru reset available but no RUU available (HTC one m7, Telstra, Australia)
-rom - guru reset android 4.2.2, hboot 1.57, latest twrp
-bootloader unlocked, phone rooted, s-on.
Problem:
Only way to s-off with hboot 1.57 is to use sunshine which won't work for me. I want to roll back to hboot 1.44 so I can achieve s-off by revone and lock the phone back up with flags removed. My understanding is that being there is no RUU using a nandroid to roll hboot back to 1.44 is my only choice and to do so I have to change the CID on my device to match the nandroid CID. Unfortunately you can't modify your phones CID if you don't have s-off so it's a bit of a catch 22.
Is this correct or am I screwed?
Hi I am trying to flash the firmware from my mac using the commands provided , but it just doesn't work . This is what it keeps saying.
Can you help me out.
fastboot flash zip /Users/abdullahhashmi/Desktop/firmware.zip
error: cannot load '/Users/abdullahhashmi/Desktop/firmware.zip'
hashmi1195 said:
Hi I am trying to flash the firmware from my mac using the commands provided , but it just doesn't work . This is what it keeps saying.
Can you help me out.
fastboot flash zip /Users/abdullahhashmi/Desktop/firmware.zip
error: cannot load '/Users/abdullahhashmi/Desktop/firmware.zip'
Click to expand...
Click to collapse
cannot load = can't find the file. Make sure your file is at the correct location (in this case on your desktop) or even simpler, move it to the same folder you have fastboot installed and run "fastboot flash zip firmware.zip"
htc one m7 firmware
hello !!! I am trying to flash the firmware from my pc using the commands provided , but it just doesn't work . This is what it keeps saying.
Can you help me out. this is my screnshot
C:\fastboot_adb\fastboot_adb>fastboot flash zip firmware.zip
target reported max download size of 1526722560 bytes
sending 'zip' (28294 KB)...
OKAY [ 2.576s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 5.727s
C:\fastboot_adb\fastboot_adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT35YW906470
(bootloader) imei: 354439055774477
(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: 4322mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-a85199f7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.587s
I haven't been able to connect to GPS satellites for quite sometime. Would flashing the latest radio fix this and do I need to be s-off to do so or can I just fire that baby up in twrp? I'm running the latest official dirty unicorns ROM. Also is the a link somewhere that I can find the latest radio that I could flash if it were this simple?? Thank you thank you.

[Q] Old hboot on Lollipop

Hi,
I have reinstall my m7 to old ROM with Android 4.1.1 and didn't do all stages OTA updates but recover backup with Lollipop. Everything is going fine but now I have hboot 1.5.4 instead 1.61. Could it cause any problem in the future? Should I install latest hboot? (where to find it?)
I have a stock rom htc one, wwe, s-off, rooted.
At this time i don't think so except if you try modding. But when htc rolls out the new sense update maybe you will have some troubles.
VoynichJimmy said:
At this time i don't think so except if you try modding. But when htc rolls out the new sense update maybe you will have some troubles.
Click to expand...
Click to collapse
I wanna stay with a stock rom. But considering to keep system up to date. What is the solution then? Should I go to rom version down and upgrade to current android 5.02 and then recover backup? Or is there a place on the network where I can find the original stock hboot 1.61 and install it via fastboot? (I've tried, didn't found)
badzi0r said:
I wanna stay with a stock rom. But considering to keep system up to date. What is the solution then? Should I go to rom version down and upgrade to current android 5.02 and then recover backup? Or is there a place on the network where I can find the original stock hboot 1.61 and install it via fastboot? (I've tried, didn't found)
Click to expand...
Click to collapse
There is no stock hboot 1.61 yet but if you want check this: http://forum.xda-developers.com/htc-one/development/hboot-modified-hboot-1-60-7-15-401-1-t3006222
But i am still confused about your case dude !! People are trying to upgrade and you are downgrading ? Hope you know what/where you are doing ?
VoynichJimmy said:
There is no stock hboot 1.61 yet
Click to expand...
Click to collapse
Yes there is.
https://www.androidfilehost.com/?fid=95916177934533541
stock 1.61 can also be extracted from these files:
https://www.androidfilehost.com/?fid=95916177934534374
https://www.androidfilehost.com/?fid=95916177934534383
https://www.androidfilehost.com/?fid=95916177934534503
@badzi0r post the output of "fastboot getvar all" before going any further. Remove imei and serialno before posting.
VoynichJimmy said:
But i am still confused about your case dude !! People are trying to upgrade and you are downgrading Hope you know what/where you are doing
Click to expand...
Click to collapse
I'm not downgrading. As I said in my first post. After crashing my HTC I have installed all from the beginning, hboot 1.44, rom with android 4.1.1, etc... then I have made OTA update to 1 version up, and then I have restored whole system (Lollipop) from backup made by TWRP. So now I have now Lollipop with hboot 1.54 but I would prefer have the updated to 1.61.
I hope it's clear now
BTW, can anyone look at my bootloader screen and confirm that not only hboot is outdated? How about the radio, etc...?
badzi0r said:
I'm not downgrading. As I said in my first post. After crashing my HTC I have installed all from the beginning, hboot 1.44, rom with android 4.1.1, etc... then I have made OTA update to 1 version up, and then I have restored whole system (Lollipop) from backup made by TWRP. So now I have now Lollipop with hboot 1.54 but I would prefer have the updated to 1.61.
I hope it's clear now
BTW, can anyone look at my bootloader screen and confirm that not only hboot is outdated? How about the radio, etc...?
Click to expand...
Click to collapse
HTC never updates hboot by itself.
If you don't have latest firmware, then you don't have latest hboot, radio, adsp, touch driver, WiFi driver, modem files, etc....
In other words, don't just update your hboot and expect to be fully up to date.
Update your full firmware.
badzi0r said:
I have installed all from the beginning, hboot 1.44, rom with android 4.1.1, etc... then I have made OTA update to 1 version up, and then I have restored whole system (Lollipop) from backup made by TWRP
Click to expand...
Click to collapse
And why not updating all the way up to lollipop? You will not be able to take ota updates with your phone in this state. Your firmware version and software version must match. Its not only the hboot version, like said above.
alray said:
And why not updating all the way up to lollipop? You will not be able to take ota updates with your phone in this state. Your firmware version and software version must match. Its not only the hboot version, like said above.
Click to expand...
Click to collapse
I didn't have stock rom with lollipop and been to lazy to do one by one all that OTA updates, so after two I've restored the twrp backup.
(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-OFF
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4099mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(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.062s
Click to expand...
Click to collapse
What you suggest now?

Categories

Resources