Database Develop

[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

[SOLVED] Upgrade HTC One from 4.1.2 to 4.4.3 and gain S-OFF+Doubletap2wake

Kind XDA users,
Ever since I got my HTC One I unlocked bootloader and rooted it to be able to use my Moga Controller.
All went and still is fine, I would not upgrade my software I get great battery life and performance.
However there are 2 reasons that make me want to upgrade my firmware:
1) It seems Google will drop support for this Android version some time.
2) Google glasses and other gear seem to uselow energy bluetooth that was introduced in Android 4.3+
My HTC One is now on firmware version v 4.1.2.
Now if Iam going to upgrade my firmware I want to S-off aswell.
Recovery info:
ClockworkMod Recovery v6.0.3.1
Boot loader info:
*** Tampered ***
*** Unlocked ***
M7_UL PVT SHIP S-ON RH
HBOOT11.44.0000
RADIO-4A14.3250.13
OpenDSP-v26.120.274.0202
Could anyone direct me to the files needed \ steps I need to take in order to:
1) S-off.
2) Upgrade.
3) Regain root?
If you need more info about my phone let me know.
Kind regards, Stefan.

Thaevil0ne said:
Kind XDA users,
Ever since I got my HTC One I unlocked bootloader and rooted it to be able to use my Moga Controller.
All went and still is fine, I would not upgrade my software I get great battery life and performance.
However there are 2 reasons that make me want to upgrade my firmware:
1) It seems Google will drop support for this Android version some time.
2) Google glasses and other gear seem to uselow energy bluetooth that was introduced in Android 4.3+
My HTC One is now on firmware version v 4.1.2.
Now if Iam going to upgrade my firmware I want to S-off aswell.
Recovery info:
ClockworkMod Recovery v6.0.3.1
Boot loader info:
*** Tampered ***
*** Unlocked ***
M7_UL PVT SHIP S-ON RH
HBOOT11.44.0000
RADIO-4A14.3250.13
OpenDSP-v26.120.274.0202
Could anyone direct me to the files needed \ steps I need to take in order to:
1) S-off.
2) Upgrade.
3) Regain root?
If you need more info about my phone let me know.
Kind regards, Stefan.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2314582
post the ouput of fastboot getvar all except imei/sn

alray said:
http://forum.xda-developers.com/showthread.php?t=2314582
post the ouput of fastboot getvar all except imei/sn
Click to expand...
Click to collapse
Iam at work atm, the USB ports here could be USB 3.0 I get a error at the end of the listing.
Kinda sure I could make a proper listing once home, however I think this contains all info needed?
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.16
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXXXXX
(bootloader) imei: 35XXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 4282mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.062s
Also: Is it possible to use rumrunner to S-OFF?
That seems a whole lot easier \ faster than revone...
Kind regards, Stefan.

Before you do anything with firmware make sure you s off. Revone is the tool you want to use with that hboot version
Sent from my HTC One using XDA Premium 4 mobile app

Thaevil0ne said:
Iam at work atm, the USB ports here could be USB 3.0 I get a error at the end the listing.
Kinda sure I could make a proper listing once home, however I think this contains all info needed?
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.16
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXXXXX
(bootloader) imei: 35XXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 4282mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.062s
Also: Is it possible to use rumrunner to S-OFF?
That seems a whole lot easier \ faster than revone...
Kind regards, Stefan.
Click to expand...
Click to collapse
1)s-off with revone
2)flash 4.19.401.9 ruu (android 4.4)
3)flash twrp 2.6.3.3 recovery, boot in recovery then exit, twrp will prompt you to root the phone when you exit.
stay s-off and bootloader unlocked.
Ask here if you need detailed instructions of above steps.

alray said:
1)s-off with revone
2)flash 4.19.401.9 ruu (android 4.4)
3)flash twrp 2.6.3.3 recovery, boot in recovery then exit, twrp will prompt you to root the phone when you exit.
stay s-off and bootloader unlocked.
Ask here if you need detailed instructions of above steps.
Click to expand...
Click to collapse
Thank you both very kindly, Iam S-OFF now.
I will read up instructions before going any further.
Kind regards, Stefan.

Make sure you do. S off is very handy but it also disables some security safeguards so you can brick your phone. Going s on again also can be dangerous. So the more you read the better. Always people to ask on here if you have questions
Sent from my HTC One using XDA Premium 4 mobile app

nateboi81 said:
Make sure you do. S off is very handy but it also disables some security safeguards so you can brick your phone. Going s on again also can be dangerous. So the more you read the better. Always people to ask on here if you have questions
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Some questions come to mind when reading the information on this link:
http://www.htc1guru.com/2014/03/android-ruu-europe/
"You should not need to downgrade your hboot version for this RUU to work.
This should work for S-On users that need to return to stock that haven’t received the latest minor OTA update for 4.19.401.11"
My hboot version is now 1.44.0000 if I flash this RUU would this upgrade my hboot version, if so to what version?
It does state it works for S-On users, there should be no problem flashing this S-OFF right?
If I flash this RUU will I be able to flash it again later?
As in: Incase some how the rom gets corrupt over time and I want to do a clean install using this RUU?
Kind regards, Stefan.

Thaevil0ne said:
Some questions come to mind when reading the information on this link:
http://www.htc1guru.com/2014/03/android-ruu-europe/
"You should not need to downgrade your hboot version for this RUU to work.
This should work for S-On users that need to return to stock that haven’t received the latest minor OTA update for 4.19.401.11"
My hboot version is now 1.44.0000 if I flash this RUU would this upgrade my hboot version, if so to what version?
It does state it works for S-On users, there should be no problem flashing this S-OFF right?
If I flash this RUU will I be able to flash it again later?
As in: Incase some how the rom gets corrupt over time and I want to do a clean install using this RUU?
Kind regards, Stefan.
Click to expand...
Click to collapse
Check here: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
under "Not so FAQ#2" what you can and cannot do with S-OFF

nkk71 said:
Check here: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
under "Not so FAQ#2" what you can and cannot do with S-OFF
Click to expand...
Click to collapse
Cheers Nkk71, that clears up a lot of questions.
Only one question still remains: if I flash this RUU will it also update hboot, if so to what version?
Kind regards Stefan.

Thaevil0ne said:
Cheers Nkk71, that clears up a lot of questions.
Only one question still remains: if I flash this RUU will it also update hboot, if so to what version?
Kind regards Stefan.
Click to expand...
Click to collapse
yes, flashing ruu will update hboot. If you flash the 4.19.401 ruu, this will update hboot to 1.56.
So better to s-off now on 1.44 (easier to achieve)

Definitely s off first. Revone works so well with 1.44
Sent from my HTC One using XDA Premium 4 mobile app

alray said:
yes, flashing ruu will update hboot. If you flash the 4.19.401 ruu, this will update hboot to 1.56.
So better to s-off now on 1.44 (easier to achieve)
Click to expand...
Click to collapse
More questions come to mind when checking information:
1) When one gains S-OFF will the CID automaticly be changed to 1111111?
1.1) If so, would there be any problem flashing this RUU with this CID?
2) Making Nandroid backup from my version 4.1 now would I be able to load this backup if I upgrade to 4.4?
2.1) When making an Nandroid backup does it also backup a partition like mmcblk0p19?
2.2) If not, how can I make a backup from this partition?
And are there any other partitions I can backup myself that a Nandroid backup does not make?
Kind regards, Stefan.

Anyone who could give an awnser to the questions asked above?
PS: Iam S-OFF already, but the mind can not relaxt having this many open questions.
I do not want to do something I can no longer undo later.
Kind regards, Stefan.

Thaevil0ne said:
1) When one gains S-OFF will the CID automaticly be changed to 1111111?
1.1) If so, would there be any problem flashing this RUU with this CID?
Click to expand...
Click to collapse
no it won't change by itself, you need to manually change using
fastboot oem writecid 11111111 <- or any CID you like, but it has to be exactly 8 characters, so for example HTC__001 has two underscores
fastboot reboot-bootloader
Thaevil0ne said:
2) Making Nandroid backup from my version 4.1 now would I be able to load this backup if I upgrade to 4.4?
Click to expand...
Click to collapse
Yes.
Thaevil0ne said:
2.1) When making an Nandroid backup does it also backup a partition like mmcblk0p19?
2.2) If not, how can I make a backup from this partition?
And are there any other partitions I can backup myself that a Nandroid backup does not make?
Click to expand...
Click to collapse
No it will not, nandroids typically only backup /system, /data (excluding sdcard), /cache, boot.img (kernel), and recovery.img.
On the M7_U and UL models, the partitions go from mmcblk0p1 all the way to mmcblk0p37, the last ones being
Code:
mmcblk0p33 boot
mmcblk0p34 recovery
mmcblk0p35 system
mmcblk0p36 cache
mmcblk0p37 userdata <- this includes /data and your virtual sdcard
if you wanted to back all the others up, you use
adb shell dd if=/dev/block/mmcblk0p<number> of=/sdcard/mmcblk0p<number>_bak.img
and then copy them over to your PC. you should exclude p35, 36 but especially 37, as you can't copy your entire internal storage to itself. (it just won't fit )
the above commands assume you have a rooted ROM (with adb already in root mode), or are running the command in custom recovery, otherwise you'd have to open a shell, and issue su first
adb shell
su
dd if=/dev/block/mmcblk0p<number> of=/sdcard/mmcblk0p<number>_bak.img
other than p19 [misc], p6 [mfg] could be important as it is has all the information about your phone (model, manufacture date, etc): http://forum.xda-developers.com/showpost.php?p=50712531&postcount=37

nkk71 said:
no it won't change by itself, you need to manually change using
fastboot oem writecid 11111111 <- or any CID you like, but it has to be exactly 8 characters, so for example HTC__001 has two underscores
fastboot reboot-bootloader
Yes.
No it will not, nandroids typically only backup /system, /data (excluding sdcard), /cache, boot.img (kernel), and recovery.img.
On the M7_U and UL models, the partitions go from mmcblk0p1 all the way to mmcblk0p37, the last ones being
Code:
mmcblk0p33 boot
mmcblk0p34 recovery
mmcblk0p35 system
mmcblk0p36 cache
mmcblk0p37 userdata <- this includes /data and your virtual sdcard
if you wanted to back all the others up, you use
adb shell dd if=/dev/block/mmcblk0p<number> of=/sdcard/mmcblk0p<number>_bak.img
and then copy them over to your PC. you should exclude p35, 36 but especially 37, as you can't copy your entire internal storage to itself. (it just won't fit )
the above commands assume you have a rooted ROM (with adb already in root mode), or are running the command in custom recovery, otherwise you'd have to open a shell, and issue su first
adb shell
su
dd if=/dev/block/mmcblk0p<number> of=/sdcard/mmcblk0p<number>_bak.img
other than p19 [misc], p6 [mfg] could be important as it is has all the information about your phone (model, manufacture date, etc): http://forum.xda-developers.com/showpost.php?p=50712531&postcount=37
Click to expand...
Click to collapse
Made a backup of all partitions from 1 to 33.
1) You say p6 [mfg] could be important aswell.
I can make a backup of this partition by the following command:
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6_bak.img ?
(The reason for asking is because you note that p19 is [misc] and p6 is [mfg])
2) You say I can restore my Nandroid backup if I ever want to go back to 4.1.2
The Nandroid backup is made with CWM, would it be possible to restore this with TWRP recovery?
3) When reading your other topic I see cschmitt made a recovery that ignores BCB check.
Would it not be wise to use this recovery at all time instead of the generic TWRP recovery?
I think whit these 3 question awnsered I can change the subject to [SLOVED].
Kind regards, Stefan.

Thaevil0ne said:
1) You say p6 [mfg] could be important aswell.
I can make a backup of this partition by the following command:
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6_bak.img ?
(The reason for asking is because you note that p19 is [misc] and p6 is [mfg])
Click to expand...
Click to collapse
Yes, the above command is correct; p6 is important because it has all the manufacture information of your phone:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Though this should never get corrupted anyway, unless you really flash something bad!! as long as you stick to flashing things appropriate for your phone model, you should be fine.
Thaevil0ne said:
2) You say I can restore my Nandroid backup if I ever want to go back to 4.1.2
The Nandroid backup is made with CWM, would it be possible to restore this with TWRP recovery?
Click to expand...
Click to collapse
No, (as far as I know) at the moment CWM backups and TWRP are not interchangeable, but it's easy enough to change recovery at any time you like.
Thaevil0ne said:
3) When reading your other topic I see cschmitt made a recovery that ignores BCB check.
Would it not be wise to use this recovery at all time instead of the generic TWRP recovery?
Click to expand...
Click to collapse
No, stick to regular builds, the noBCB recovery is only to be used for emergency situations.

nkk71 said:
Yes, the above command is correct; p6 is important because it has all the manufacture information of your phone:
Though this should never get corrupted anyway, unless you really flash something bad!! as long as you stick to flashing things appropriate for your phone model, you should be fine.
No, (as far as I know) at the moment CWM backups and TWRP are not interchangeable, but it's easy enough to change recovery at any time you like.
No, stick to regular builds, the noBCB recovery is only to be used for emergency situations.
Click to expand...
Click to collapse
Hello again kind XDA users,
Ever since going S-OFF I wanted to upgrade my firmware yet never did so as I did not really find the time.
However now Sense 6 is out and it has some nice features I would like to upgrade.
Could any of you direct me to the step by step guide to get this HTC M7 to 4.4 with Sense 6?
Also regain root will be prefered as I need it to use my gamepad.
(Getvar is still the same, only Iam S-Off now.)
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.16
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXXXXX
(bootloader) imei: 35XXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 4282mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.062s
Recovery info:
ClockworkMod Recovery v6.0.3.1
Kind regards, Stefan.

Thaevil0ne said:
Hello again kind XDA users,
Ever since going S-OFF I wanted to upgrade my firmware yet never did so as I did not really find the time.
However now Sense 6 is out and it has some nice features I would like to upgrade.
Could any of you direct me to the step by step guide to get this HTC M7 to 4.4 with Sense 6?
Also regain root will be prefered as I need it to use my gamepad.
(Getvar is still the same, only Iam S-Off now.)
fastboot getvar all
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-main: 1.29.401.16
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__E11
Recovery info:
ClockworkMod Recovery v6.0.3.1
Kind regards, Stefan.
Click to expand...
Click to collapse
First off, change recovery, that one is way outdated, use TWRP 2.6.3.3 or 2.8.0.1
http://techerrata.com/browse/twrp2/m7
flashing recovery instructions can be found in the Frequently Asked Question sticky page 3 under Point C
Firmwares and instructions can be found here: http://forum.xda-developers.com/showthread.php?t=2365506
(other places too, it's just the ones i'm using)
I'd recommend you flash the x.xx.401.x versions incrementally (though it may not be necessary with those firmwares, because they have been repacked to include all previous updates, but updates usually expect the previous version to already be in place, otherwise could result in problems)
List of ROMs:
http://forum.xda-developers.com/htc-one/#romList
always read the OP of the ROM to make sure you meet the requirements (recovery version, etc)

nkk71 said:
First off, change recovery, that one is way outdated, use TWRP 2.6.3.3 or 2.8.0.1
http://techerrata.com/browse/twrp2/m7
flashing recovery instructions can be found in the Frequently Asked Question sticky page 3 under Point C
Firmwares and instructions can be found here: http://forum.xda-developers.com/showthread.php?t=2365506
(other places too, it's just the ones i'm using)
I'd recommend you flash the x.xx.401.x versions incrementally (though it may not be necessary with those firmwares, because they have been repacked to include all previous updates, but updates usually expect the previous version to already be in place, otherwise could result in problems)
List of ROMs:
http://forum.xda-developers.com/htc-one/#romList
always read the OP of the ROM to make sure you meet the requirements (recovery version, etc)
Click to expand...
Click to collapse
Hello,
Thanks for the fast responce.
Do you mean I should flash all of these first after I upgrade my recovery:
- 2.17.401.1: http://d-h.st/PJv (Rename to firmware.zip after downloading)
- 2.24.401.1: http://d-h.st/WO9 (Rename to firmware.zip after downloading)
- 2.24.401.8: http://d-h.st/qPT (Rename to firmware.zip after downloading) *LATEST*
If so, will I flash all of these after?
4.3 Base Firmwares:
- 3.06.1700.10: http://d-h.st/maA (Rename to firmware.zip after downloading)
- 3.09.401.1: http://d-h.st/PSE (Rename to firmware.zip after downloading)
- 3.17.401.2: http://d-h.st/bgE (Rename to firmware.zip after downloading)
- 3.22.1540.1: http://d-h.st/LLO (Rename to firmware.zip after downloading)
- 3.57.401.500 : http://d-h.st/z6g (Rename to firmware.zip after downloading)
- 3.62.401.1 : http://d-h.st/in6 (Rename to firmware.zip after downloading) *LATEST*
4.4 Base
- 4.06.1540.2 (Rename to firmware.zip after downloading)
- 4.06.1540.3 (Rename to firmware.zip after downloading)
- 4.19.401.8 (Rename to firmware.zip after downloading)
- 4.19.401.9 (Rename to firmware.zip after downloading)
- 4.19.401.11 (Rename to firmware.zip after downloading)
- 5.11.1540.9 (Rename to firmware.zip after downloading)
- 5.11.401.10 (Rename to firmware.zip after downloading)
- 6.06.401.1 (Rename to firmware.zip after downloading)
- 6.09.401.5 (Rename to firmware.zip after downloading) *LATEST*
Or will just flashing the latest one do for each major update?
Also, will flashing these upgrade me to Sense 6?
Kind regards, Stefan.

[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

Deleted OS with no backup (Solved)

Hello, guys. How you doing?
UPDATE: it's solved, i got back to stock rom after flashing this: https :// fl1.androidfilehost.com/dl/2k6GKx4IJOgIhD09zRzbzw/1441027324/95897840722641610/Reset_rom_6.07.1540.2.zip?
Now I'm going to do a BACKUP haha
I am with a HTC ONE M7 Internation/Unlocked Soft-Bricked, with no OS... Here are some information:
- Using TWRP 2.8.7.0 custom recovery for M7 (latest version)
- Unlocked bootloader
- Rooted (at least I did it before wipping my OS)
- S-ON!
- HBOOT v.1.57
- Already have ADB/Fastboot on my PC
- Modelid: PN0711000
- Cidnum: HTC__332
Here's my tale:
I tried to install RUU M7 Lollipop ROM, from HTC's website. But, at the very beggining of the instalation (4%), the RUU software said it lost my device. I did it while in fastboot mode, because it was the only way RUU recognized my phone. Then I could not install Lollipop ROM by RUU method, so I decided to flash a Lollipop ROM Unlocked Version for One M7.
I knew that for doing it I would need to install some custom recovery on my phone, unlock its bootloader mode and install on my PC ADB and Fastboot. I did all of this; the bootloader unlocked I did from HTC's website guide. So, I put on my phone a ROM in zip extension, boot it on recovery mode. I read that I should wipe data, cache, calvik cache and, maybe, system. And I did it... with NO BACKUP of original ROM --' I know I was stupid...
So I wipe this partitions, entered Install menu and tried to run instalation of the ROM zip file. It didn't work!!! Some error: "E: error executing updater binary in zip..." And I tried to flash different ROMs, all of them showed this error...
Then now I am with a Soft-Bricked HTC ONE M7 which has no OS. Some pics of my status: https: // w w w .dropbox.com/s/ruyen2ikn0u5i0u/Soft-Bricked%20M7.rar?dl=0
I hope you can help me

Please, help me :crying:

Atadie said:
Hello, guys. How you doing?
I am with a HTC ONE M7 Internation/Unlocked Soft-Bricked, with no OS... Here are some information:
- Using TWRP 2.8.7.0 custom recovery for M7 (latest version)
- Unlocked bootloader
- Rooted (at least I did it before wipping my OS)
- S-ON!
- HBOOT v.1.57
- Already have ADB/Fastboot on my PC
- Modelid: PN0711000
- Cidnum: HTC__332
There's my tale:
I tried to install RUU M7 Lollipop ROM, from HTC's website. But, at the very beggining of the instalation (4%), the RUU software said it lost my device. I did it while in fastboot mode, because it was the only way RUU recognized my phone. Then I could not install Lollipop ROM by RUU method, so I decided to flash a Lollipop ROM Unlocked Version for One M7.
I knew that for doing it I would need to install some custom recovery on my phone, unlock its bootloader mode and install on my PC ADB and Fastboot. I did all of this; the bootloader unlocked I did from HTC's website guide. So, I put on my phone a ROM in zip extension, boot it on recovery mode. I read that I should wipe data, cache, calvik cache and, maybe, system. And I did it... with NO BACKUP of original ROM --' I know I was stupid...
So I wipe this partitions, entered Install menu and tried to run instalation of the ROM zip file. It didn't work!!! Some error: "E: error executing updater binary in zip..." And I tried to flash different ROMs, all of them showed this error...
Then now I am with a Soft-Bricked HTC ONE M7 which has no OS. Some pics of my status: https: // w w w .dropbox.com/s/ruyen2ikn0u5i0u/Soft-Bricked%20M7.rar?dl=0
I hope you can help me
Click to expand...
Click to collapse
post the output of "fastboot getvar all" (remove your imei and serialno)

alray said:
post the output of "fastboot getvar all" (remove your imei and serialno)
Click to expand...
Click to collapse
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.28.3218.04
version-cpld: None
version-microp: None
version-main: 6.15.599.101
version-misc: PVT SHIP S-ON
serialno: ************
imei: ***************
meid: 00000000000000
product: m7_u
platform: HBOOT-8064
modelid: PN0711000
cidnum: HTC__332
battery-status: good
battery-voltage: 4322mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-6d8a0b9b
hbootpreupdate: 11
gencheckpt: 0

Could not get S-OFF
I tried getting S-OFF by Rumrunner method and didn't work :/
Hep me, guys! I really need my One back to life!!! I'm in pain :crying:

Atadie said:
I tried getting S-OFF by Rumrunner method and didn't work :/
Click to expand...
Click to collapse
You can't use rumrunner to achieve s-off on hboot 1.57, only method is Sunshine
Atadie said:
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.28.3218.04
version-cpld: None
version-microp: None
version-main: 6.15.599.101
version-misc: PVT SHIP S-ON
serialno: ************
imei: ***************
meid: 00000000000000
product: m7_u
platform: HBOOT-8064
modelid: PN0711000
cidnum: HTC__332
battery-status: good
battery-voltage: 4322mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-6d8a0b9b
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
There is not much available for 6.15.599.101 version, you'll probably need to use custom roms or convert to another version. There is a 6.15.599.101 ruu available at irfile.com but you will need an acount to download it (paid account) http://www.ir-file.com/portal/index.php?dir=Firmware/HTC/HTC_Android/M7_U/
Atadie said:
UPDATE: it's solved, i got back to stock rom after flashing this: https :// fl1.androidfilehost.com/dl/2k6GKx4IJOgIhD09zRzbzw/1441027324/95897840722641610/Reset_rom_6.07.1540.2.zip?
Now I'm going to do a BACKUP haha
Click to expand...
Click to collapse
This rom is for the Developer edition version CID BS_US001 and MID PN0712000, By flashing this on your phone, you're far from being stock, you will not get any ota updates and be stuck on this version.

alray said:
You can't use rumrunner to achieve s-off on hboot 1.57, only method is Sunshine
There is not much available for 6.15.599.101 version, you'll probably need to use custom roms or convert to another version. There is a 6.15.599.101 ruu available at irfile.com but you will need an acount to download it (paid account) http://www.ir-file.com/portal/index.php?dir=Firmware/HTC/HTC_Android/M7_U/
This rom is for the Developer edition version CID BS_US001 and MID PN0712000, By flashing this on your phone, you're far from being stock, you will not get any ota updates and be stuck on this version.
Click to expand...
Click to collapse
Oh, thanks :/
So, what is the best path to follow to get Lollipop? Should I pay 25 bucks for Sunshine, change my CID and try to flash correct Lollipop rom? Is there another way to get Lollipop rather that one?
Are there so many new and interesting features on Lollipop or should I stay on KitKat 4.4.3? I don't know so many custom good roms; can you recommend me some?
Sorry for asking so much questions. I know, probably I'm bothering you '-'
PS: Now my system asks for an OTA update to Lollipop, but it's not possible... Probably due to what you said about my flashed rom being Developer edition's one.

Atadie said:
Oh, thanks :/
So, what is the best path to follow to get Lollipop? Should I pay 25 bucks for Sunshine, change my CID and try to flash correct Lollipop rom? Is there another way to get Lollipop rather that one?
Click to expand...
Click to collapse
Either pay for sunshine so you can change your CID / MID to convert your phone to another version using a lollipop RUU or pay for an account at ir-file.com so you can download the .599 ruu and then take all ota updates.
Are there so many new and interesting features on Lollipop or should I stay on KitKat 4.4.3?
Click to expand...
Click to collapse
Many ppl likes lollipop and probably as many ppl doesn't like it. I think its better to try it yourself and see what you prefer. Some ppl likes the new features and other ones are complaining about battery drain and lags.
I don't know so many custom good roms; can you recommend me some?
Click to expand...
Click to collapse
All custom roms are good, it all depends what features you need. The best you can do is to read some rom threads and choose one that fit what you need, try it a few days and if not liking it, flash another one. If you want good battery life and no lag, I would recommend GPE roms, if you need what HTC Sense have to offer, then choose a Sense based rom like ARHD, Maximus, InsertCoin, NuSense ....
PS: Now my system asks for an OTA update to Lollipop, but it's not possible... Probably due to what you said about my flashed rom being Developer edition's one.
Click to expand...
Click to collapse
Because your CID and MID doesn't match the rom version you have flashed. Developer edition is for CID BS_US001 and MID PN0712000, yours is HTC__332 and PN0711000, In order to receive ota updates, you must be 100% stock either be flashing the .599 ruu for HTC__332 / PN0711000 or by achieving s-off, changing your CID / MID and flashing another version ruu e.g: changing your cid to BS_US001, your MID to PN0712000 and flashing a dev edition (.1540) RUU.

alray said:
All custom roms are good, it all depends what features you need. The best you can do is to read some rom threads and choose one that fit what you need, try it a few days and if not liking it, flash another one. If you want good battery life and no lag, I would recommend GPE roms, if you need what HTC Sense have to offer, then choose a Sense based rom like ARHD, Maximus, InsertCoin, NuSense ....
Click to expand...
Click to collapse
I was reading about Android Revolution HD, it seems good. I really like Blinkfeed (Highlights) so I guess I wouldn't flash a ROM which doesn't have it. I think ARHD got Blinkfeed, right?
Can I flash this ROM on my phone? As far as you know about my specs.

[Q] M7 - Rooted S-ON 7.21.980.22 - Options for updating or install different ROM

Hi guys,
I first started looking into updating my rooted stock ROM, due to an update coming through. After reading quite a lot of different posts I'm kind of stuck with what my options are.
From all the reading about how I could update, I "think" my only option is to spoof the version-main to a lower version (from this post) than I currently have and flash a different RUU. Even that seems hard, as RUU's for the VODAP021 cidnum seem sparse ... Also having S-ON and my HBOOT I think limit my options. Would sunshine be the best option? Seeing as I may then be able to get S-OFF, and basically do what I want?
I don't mind updating to another ROM other than stock, as I'm not completely attached to the HTC Sense and other apps, so any help with what my options are would be appreciated.
Here is what my bootscreen says:
TAMPERED
UNLOCKED
M7_UL PVT SHIP S-ON RH
HBOOT-1.61.0000
RADIO-4T.35.3218.16
OpenDSP-v35.120.274.0718
OS-7.21.980.22
eMMC-boot 2048MB
Click to expand...
Click to collapse
Here is the output for the other version info:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.21.980.22
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: VODAP021
(bootloader) battery-status: good
(bootloader) battery-voltage: 4109mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Any advice at all on how I can either update to the latest version of the stock ROM, I think is 7.21.980.35 or updating to another custom ROM would be much appreciated!

orwell_g said:
Hi guys,
I first started looking into updating my rooted stock ROM, due to an update coming through. After reading quite a lot of different posts I'm kind of stuck with what my options are.
From all the reading about how I could update, I "think" my only option is to spoof the version-main to a lower version (from this post) than I currently have and flash a different RUU. Even that seems hard, as RUU's for the VODAP021 cidnum seem sparse ... Also having S-ON and my HBOOT I think limit my options. Would sunshine be the best option? Seeing as I may then be able to get S-OFF, and basically do what I want?
I don't mind updating to another ROM other than stock, as I'm not completely attached to the HTC Sense and other apps, so any help with what my options are would be appreciated.
Here is what my bootscreen says:
Here is the output for the other version info:
Any advice at all on how I can either update to the latest version of the stock ROM, I think is 7.21.980.35 or updating to another custom ROM would be much appreciated!
Click to expand...
Click to collapse
Your bootloader is already unlocked so all you need to do to spoof your version main is to flash my tool using twrp 2.6.3.3, select the .980.5 version-main and reboot.
Once done relock your bootloader and flash the .980.5 RUU. Take all ota updates before modding anything. The latest version is .980.51 not .35
The other option is to flash a custom rom. Your phone should accept any recent custom rom (HTC Sense or not) since the firmware installed on it is recent enough for all roms to work properly.

Thanks for the response! I have twrp 2.8.7.0, are there any issues with using that? Once updated to the latest version, is it easy enough to root again? Ideally keeping root would be great.

I'm tempted to perhaps use the manual commands to change the version, as it mentions that it can hang in higher versions of twrp, but want to make sure they are correct, I'm planning on using the following commands to go from 7.21.980.22 to 7.21.980.5:
adb shell
echo -ne "7.21.980.5\x00\x00" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
exit
adb reboot bootloader
The only thing I wasn't sure of the is the number of nulls as there are two versions one with two nulls, one with one.

orwell_g said:
Thanks for the response! I have twrp 2.8.7.0, are there any issues with using that? Once updated to the latest version, is it easy enough to root again? Ideally keeping root would be great.
Click to expand...
Click to collapse
It's the same process to root your phone on the latest version (unlock bootloader, flash twrp, flash the latest supersu). You can't keep root when flashing a ruu. SU binaries are on the /system partition which will be restored to stock when flashing the ruu.
orwell_g said:
I'm tempted to perhaps use the manual commands to change the version, as it mentions that it can hang in higher versions of twrp, but want to make sure they are correct, I'm planning on using the following commands to go from 7.21.980.22 to 7.21.980.5:
adb shell
echo -ne "7.21.980.5\x00\x00" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
exit
adb reboot bootloader
The only thing I wasn't sure of the is the number of nulls as there are two versions one with two nulls, one with one.
Click to expand...
Click to collapse
7.21.980.5\x00 is fine (there are currently 10 characters in your version-main and the new one is going to be 9 characters, you need one x00 to remove the last "2").
Sent from my HTC One using XDA Labs

Managed to get some time do this over the weekend. Had to flash the RUU twice for some reason, as there were failures initially "FAILED (status read failed (Too many links))", second time round went through fine. Now I'm back to 7.21.980.63 without a gaping security hole! Thanks for your help!!

orwell_g said:
Managed to get some time do this over the weekend. Had to flash the RUU twice for some reason, as there were failures initially "FAILED (status read failed (Too many links))", second time round went through fine. Now I'm back to 7.21.980.63 without a gaping security hole! Thanks for your help!!
Click to expand...
Click to collapse
got link for the ruu you used?
thanks