Database Develop

HTC One (M7) Unroot

Hello people.
I need your help regarding my AT&T HTC One M7.
My phone is rooted, has unlocked bootloader, and stock recovery. I want to unroot it and lock the bootloader
I tried the method with locking the bootloader and flashing stock RUU compatible with my CID and MID, but when I locked the bootloader the device couldn't boot to Android. Instead, it booted to fastboot. Anyways I continouted with the process and I tried to install my RUU, but in the middle of installation it gave me [error 155]. It gave me the same error with any other RUU I tried to install, can you help me?
Here is what i get when i type "getvar all" command:
(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:xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(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: 4294mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

Torcidas1950 said:
Hello people.
I need your help regarding my AT&T HTC One M7.
My phone is rooted, has unlocked bootloader, and stock recovery. I want to unroot it and lock the bootloader
I tried the method with locking the bootloader and flashing stock RUU compatible with my CID and MID, but when I locked the bootloader the device couldn't boot to Android. Instead, it booted to fastboot. Anyways I continouted with the process and I tried to install my RUU, but in the middle of installation it gave me [error 155]. It gave me the same error with any other RUU I tried to install, can you help me?
Here is what i get when i type "getvar all" command:
(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:xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(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: 4294mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
I don't know which RUU did you try but here is 3.17.502.3 and 4.18.502.7. You might try these, make sure your bootloader is locked/relocked! Generally, the error 155 is the result of using the wrong RUU for your version. The two I provided are based on you hboot, try version 3 first then version 4.

majmoz said:
I don't know which RUU did you try but here is 3.17.502.3 and 4.18.502.7. You might try these, make sure your bootloader is locked/relocked! Generally, the error 155 is the result of using the wrong RUU for your version. The two I provided are based on you hboot, try version 3 first then version 4.
Click to expand...
Click to collapse
I am pretty much sure I tried both of them, I think it has something to do with the fact it doesn't write down any "version-main" number like the phone doesn't even have it. :/

I am pretty much sure I tried both of them, I think it has something to do with the fact it doesn't write down any "version-main" number like the phone doesn't even have it. :/
majmoz said:
I don't know which RUU did you try but here is 3.17.502.3 and 4.18.502.7. You might try these, make sure your bootloader is locked/relocked! Generally, the error 155 is the result of using the wrong RUU for your version. The two I provided are based on you hboot, try version 3 first then version 4.
Click to expand...
Click to collapse

Torcidas1950 said:
I am pretty much sure I tried both of them, I think it has something to do with the fact it doesn't write down any "version-main" number like the phone doesn't even have it. :/
Click to expand...
Click to collapse
Your missing version number is the result of being overwritten when you flashed a custom recovery. The newer custom recoveries have made changes to avoid that issue. Since, your phone isn't bootlooping then it is just cosmetic. You might try this 3.17.502.3 rom.zip. You would flash it in bootloader/FASTBOOT USB:
In a command window type:
Code:
[B][I]adb reboot bootloader[/I][/B]
After that, type:
Code:
[B][I]fastboot oem rebootRUU [/I][/B]
NOTE: You should see a silver HTC logo come up on your phone after executing this command.
NOTE: if this command freezes, just disconnect the USB cable and hold the power and volume down buttons until the device reboots. Then, repeat the steps above again.
Finally:
Code:
[B][I]fastboot flash zip 3.17.502.3.rom.zip[/I][/B]
Repeat the same command: IMPORTANT
Code:
[B][I]fastboot flash zip 3.17.502.3.rom.zip[/I][/B]
NOTE: The green bar on the phone may not go to 100% of the bar ... but If you see completed on your computer command window, wait for a few seconds and move on.
Last Step:
Code:
[B][I]fastboot reboot[/I][/B]
Click to expand...
Click to collapse

majmoz said:
Your missing version number is the result of being overwritten when you flashed a custom recovery. The newer custom recoveries have made changes to avoid that issue. Since, your phone isn't bootlooping then it is just cosmetic. You might try this 3.17.502.3 rom.zip. You would flash it in bootloader/FASTBOOT USB:
Click to expand...
Click to collapse
Thanks, I will try that. But can I brick my phone or something else like that?

majmoz said:
Your missing version number is the result of being overwritten when you flashed a custom recovery. The newer custom recoveries have made changes to avoid that issue. Since, your phone isn't bootlooping then it is just cosmetic. You might try this 3.17.502.3 rom.zip. You would flash it in bootloader/FASTBOOT USB:
Click to expand...
Click to collapse
Should I maybe try this older RUU.exe
http://www.htc1guru.com/dld/ruu_m7_...20_10-40-1150-04_release_326691_signed_2-exe/

Can you run getvar all so we can see what firmware version you are on? Be sure to remove your IMEI and serial numbers.

MarkBell said:
Can you run getvar all so we can see what firmware version you are on? Be sure to remove your IMEI and serial numbers.
Click to expand...
Click to collapse
(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:xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(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: 4294mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

the 3.17.502.3 ruu should work for you (with a relocked bootloader)
http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/
http://androidruu.com/getdownload.p...13_10.38j.1157.04_release_334235_signed_2.exe
what error did you get?

nkk71 said:
the 3.17.502.3 ruu should work for you (with a relocked bootloader)
http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/
http://androidruu.com/getdownload.p...13_10.38j.1157.04_release_334235_signed_2.exe
what error did you get?
Click to expand...
Click to collapse
Error 155, every time with any of these RUU's :/

Torcidas1950 said:
Error 155, every time with any of these RUU's :/
Click to expand...
Click to collapse
can you find the debug log, or use the ROM.ZIP in fastboot:
the usual procedure is:
fastboot oem rebootRUU
fastboot flash zip ROM.ZIP
fastboot flash zip ROM.ZIP <- yes twice!!
fastboot reboot-bootloader
but during the first flash it will throw an error, let's see what it is
to get the ROM.ZIP, run the RUU, once the first screen shows up there will be a new folder in %TEMP%, within it you will find a 1GB file called ROM.ZIP
if it's due to the missing version-main, you can fix that using the misctool http://forum.xda-developers.com/showthread.php?t=1526316

nkk71 said:
can you find the debug log, or use the ROM.ZIP in fastboot:
the usual procedure is:
fastboot oem rebootRUU
fastboot flash zip ROM.ZIP
fastboot flash zip ROM.ZIP <- yes twice!!
fastboot reboot-bootloader
but during the first flash it will throw an error, let's see what it is
to get the ROM.ZIP, run the RUU, once the first screen shows up there will be a new folder in %TEMP%, within it you will find a 1GB file called ROM.ZIP
if it's due to the missing version-main, you can fix that using the misctool http://forum.xda-developers.com/showthread.php?t=1526316
Click to expand...
Click to collapse
Can I do any damage to my phone if the ZIP RUU fails?

Torcidas1950 said:
Can I do any damage to my phone if the ZIP RUU fails?
Click to expand...
Click to collapse
nope, especially with S-ON and a signed/encrypted RUU.ZIP (the one contained in the RUU.EXE is signed/encrypted), so when you try to flash it using fastboot (which is the same thing the RUU.EXE does, but doesn't show textual progress - though there should be a log somewhere), the fastboot flash will start by various checks, if and only if all the checks pass (meaning the signature, MID, CID, etc are correct for your phone), the ruu will begin installation.
the first flash will do the hboot preupdate and say "failed flush again immediately", the second flash would continue flashing all other partitions

nkk71 said:
nope, especially with S-ON and a signed/encrypted RUU.ZIP (the one contained in the RUU.EXE is signed/encrypted), so when you try to flash it using fastboot (which is the same thing the RUU.EXE does, but doesn't show textual progress - though there should be a log somewhere), the fastboot flash will start by various checks, if and only if all the checks pass (meaning the signature, MID, CID, etc are correct for your phone), the ruu will begin installation.
the first flash will do the hboot preupdate and say "failed flush again immediately", the second flash would continue flashing all other partitions
Click to expand...
Click to collapse
So, does that mean it will fail like the RUU.exe did because I'ts the same way of installing, just its showing install wizard instead of CMD?

Torcidas1950 said:
So, does that mean it will fail like the RUU.exe did because I'ts the same way of installing, just its showing install wizard instead of CMD?
Click to expand...
Click to collapse
yes most probably it will fail, the RUU.EXE is basically just a "container" for the ruu.zip (called ROM.ZIP).... the exe will extract fastboot/adb/rom.zip/etc files into a temp directory and then basically do the commands i listed above.
(I do believe the "wizard" does some initial checks just for the sake of visual feedback, but the actual flashing is done using fastboot commands in the background)

nkk71 said:
yes most probably it will fail, the RUU.EXE is basically just a "container" for the ruu.zip (called ROM.ZIP).... the exe will extract fastboot/adb/rom.zip/etc files into a temp directory and then basically do the commands i listed above.
(I do believe the "wizard" does some initial checks just for the sake of visual feedback, but the actual flashing is done using fastboot commands in the background)
Click to expand...
Click to collapse
Then where can I find that debug log from previous attempts? Its too much things to do just to see where is the error

Torcidas1950 said:
Then where can I find that debug log from previous attempts? Its too much things to do just to see where is the error
Click to expand...
Click to collapse
probably in the temp folder i guess, not sure since i haven't used or checked and ruu.exe log in about forever

nkk71 said:
probably in the temp folder i guess, not sure since i haven't used or checked and ruu.exe log in about forever
Click to expand...
Click to collapse
Something like this? I have around 10 of these in my C:\Temp\HTC folder
Start time: 2014/6/22, 13:1:7
Main
readConfig ok
InitInstance
HSM OLD HTC driver 3.0 is not installed.
Check Driver Version = 4.11.0.001
HSM OLD HTC driver 4.0 is needed to be upgraded.
The USB driver is needed to be upgraded
HSM already installed
WMP version = 12.0.7601.18150
Copy Installer folder from H:\ to C:\TEMP\HTCDriver
HSM OLD HTC driver is not existed
Check Driver Version = 4.11.0.001
HSM OLD HTC driver is installed.
Start to uninstall HSM OLD htc driver.
Uninstall HSM OLD htc driver finished.
New Driver Version = 4.3.0.001
Start to execute HTCDriverInstaller.
HTCDriverInstaller is finished.
Delete Installer folder C:\TEMP\HTCDriver
Please replug USB cable before using the USB functions.
HTC Sync Manager autorun,finished
End time: 2014/6/22, 13:3:18

nkk71 said:
probably in the temp folder i guess, not sure since i haven't used or checked and ruu.exe log in about forever
Click to expand...
Click to collapse
Here is the file i found in C:\ruu_log\
I had to .zip it because it didn't want to upload in .log format

[Q] Stuck in Fastboot RUU mode

So to begin I failed miserably trying to reinstall a stockROM for my HTC. Using an RUU for a Rogers phone the RUU i could find apparently has a corrupted file and has left me stranded with a relocked device without S-OFF in the fastboot RUU menu. The problem is I cant manually flash a zip because fastboot says its too large and its impossible to unlock because a big HTC error screen is up whenever the phone is connected to my PC. I was wondering if anyone had any problems similar to this and could help me out. I have no warranty left and the only people who have had this happen seem to have access to the HBOOT menu which i do not. If anyone can provide some insight it would be appreciated.
GETVAR LOG:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.631.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4120mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU (Hboot PreUpdate)
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

DCaterer said:
So to begin I failed miserably trying to reinstall a stockROM for my HTC. Using an RUU for a Rogers phone the RUU i could find apparently has a corrupted file and has left me stranded with a relocked device without S-OFF in the fastboot RUU menu. The problem is I cant manually flash a zip because fastboot says its too large and its impossible to unlock because a big HTC error screen is up whenever the phone is connected to my PC. I was wondering if anyone had any problems similar to this and could help me out. I have no warranty left and the only people who have had this happen seem to have access to the HBOOT menu which i do not. If anyone can provide some insight it would be appreciated.
GETVAR LOG:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.631.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4120mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU (Hboot PreUpdate)
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Remove your IMEI and Serialno from your above post.
What makes you believe the file is corrupted?
What ruu version are you trying to flash exactly? 4.19.631.9? 7.17.631.7?

alray said:
Remove your IMEI and Serialno from your above post.
What makes you believe the file is corrupted?
What ruu version are you trying to flash exactly? 4.19.631.9? 7.17.631.7?
Click to expand...
Click to collapse
I'm trying to flash 4.19.631.9 because that is the only Rogers RUU i could find and the reason I think it is corrupted is because the ROM file from the RUU temp files was corrupted and empty. I re downloaded the RUU twice but the same things happened. The utility also gave me an Error 152 System image error and on the error screen on my phone when it is unplugged it shows the OS in red (assuming it is deleted) and the an area CIR says FAIL-PU.
If you knew where I could get an updated ROGERS001 CID RUU that would be awesome but I havent been able to :L.
Edit:Managed to unlock device but still stuck in Fastboot RUU mode.

DCaterer said:
I'm trying to flash 4.19.631.9 because that is the only Rogers RUU i could find and the reason I think it is corrupted is because the ROM file from the RUU temp files was corrupted and empty. I re downloaded the RUU twice but the same things happened.
Click to expand...
Click to collapse
Did you checked the MD5 value of the RUU before flashing? Don't forget that rom.zip from the ruu is encrypted and attempting to open this file will output some "file corrupted" error.
The utility also gave me an Error 152 System image error and on the error screen on my phone when it is unplugged it shows the OS in red (assuming it is deleted) and the an area CIR says FAIL-PU.
Click to expand...
Click to collapse
Your phone is stuck in RUU mode as you can see from your "fastboot getvar all" because it failed the pre-update (FAIL - PU). CIR is the partition for the Infrared port (Consumer Infra Red). So looks like this part of the flash failed.
Your OS version in red indicate that the ruu flash didn't complete and that the phone is still waiting to be flashed. The phone will keep rebooting to ruu mode until its flashed correctly.
Were you on 4.19.631.9 before attempting to flash the 4.19.631.9 RUU?
If you knew where I could get an updated ROGERS001 CID RUU that would be awesome but I havent been able to :L.
Click to expand...
Click to collapse
There is a lollipop RUU for Rogers but will not help at this time. Your phone must be at least on hboot 1.57 to flash a lollipop RUU.

alray said:
Did you checked the MD5 value of the RUU before flashing? Don't forget that rom.zip from the ruu is encrypted and attempting to open this file will output some "file corrupted" error.
Your phone is stuck in RUU mode as you can see from your "fastboot getvar all" because it failed the pre-update (FAIL - PU). CIR is the partition for the Infrared port (Consumer Infra Red). So looks like this part of the flash failed.
Your OS version in red indicate that the ruu flash didn't complete and that the phone is still waiting to be flashed. The phone will keep rebooting to ruu mode until its flashed correctly.
Click to expand...
Click to collapse
I'm not sure what I should be looking for in the MD5 : 6ec60cc5e59d4e342a946405471d1218
This RUU was from htcguru the only place i could find it its name is:
RUU M7 UL K44 SENSE55 MR Rogers WWE 4.19.631.9 Radio 4A.23.3263.28 10.38r.1157.04L Release 351317 Signed 2
alray said:
Were you on 4.19.631.9 before attempting to flash the 4.19.631.9 RUU?
Click to expand...
Click to collapse
Yes I was on the same version apparently., at least according to the RUU. I know it sounds silly to flash the same version but my phone is not stock and even TWRP or CWM cant boot as it is waiting to be flashed correctly (according to you). Overlooked that the rom was encrypted silly me :L.

Is their a way to get out of RUU mode or is it required to flash a new RUU. Tried again still no luck cant access phone with adb so its hard to do anything and fastboot oem is just for dev edition so that doesnt work. Do you know of a ROGERS001 RUU zip file or has noone managed to get it into zip format.

DCaterer said:
I'm not sure what I should be looking for in the MD5 : 6ec60cc5e59d4e342a946405471d1218
This RUU was from htcguru the only place i could find it its name is:
RUU M7 UL K44 SENSE55 MR Rogers WWE 4.19.631.9 Radio 4A.23.3263.28 10.38r.1157.04L Release 351317 Signed 2
Click to expand...
Click to collapse
You must check the md5 value on your ocmputer once the file is downloaded. Both value must match (on your computer and that one from htc1guru.com)
Use winmd5.exe to check your md5, use google search, you'll find it easily.

Alright so both md5 match but the same error comes up during RUU, CIR partition continues to fail.

DCaterer said:
Alright so both md5 match but the same error comes up during RUU, CIR partition continues to fail.
Click to expand...
Click to collapse
There might be an issue with your emmc chip (memory). That would explain why the CIR partition can't be flashed. Can you post the output of
Code:
fastboot oem dmesg
and
Code:
fastboot oem last_dmesg

alray said:
There might be an issue with your emmc chip (memory). That would explain why the CIR partition can't be flashed. Can you post the output of
Code:
fastboot oem dmesg
and
Code:
fastboot oem last_dmesg
Click to expand...
Click to collapse
Text lines are huge threw them up on dropbox on txt documents.
Alright here is dmesg:
https://www.dropbox.com/s/0hgxz5wglezex0e/Dmesg.txt?dl=0
and last_dmesg:
https://www.dropbox.com/s/h2z5ddx45vw2zie/last dmesg.txt?dl=0

Ok dont worry about it anymore decided to get an htc one m8 found one for 250$ brand new. But if you figure out the problem let me know so i can avoid my mistakes from the past

DCaterer said:
Ok dont worry about it anymore decided to get an htc one m8 found one for 250$ brand new. But if you figure out the problem let me know so i can avoid my mistakes from the past
Click to expand...
Click to collapse
I don't think you have made any mistakes here. The only thing I can think to get out of ruu mode on a s-on phone is to flash a ruu or a firmware. RUU doesn't work and can't find any firmware of this version. Maybe flashing the firmware.zip from the same version ota update could work, then from there I would try to s-off and try some other things...

Got soft-brick in RUU mode

Earlier i had 6.09.401.5 ROM on my phone. Bootloader showed that main os version is 6.13.708.1
CID was set to 11111111 with S-ON and LOCKED bootloader, HBOOT 1.57
I tried to install 7.17.1540 RUU but got a BRICK with 1.61 HBOOT.
Now main version os shows 6.13.708.1 (7.17.1540.4)
Have only access to fastboot. Screen shows HTC logo with 4 triangles. On USB disconnection shows recovery with only "RUU" text.
Tried to flash through fastboot 401 and 708 firmwares, but getting: SBL1 = Fail-PU or Signature verify failed etc.
By RUU having error 152 or 155 or 12.
Non RUU or ZIP won't flash.
Don't know, what to do, please help!

lyrgo23 said:
Earlier i had 6.09.401.5 ROM on my phone. Bootloader showed that main os version is 6.13.708.1
CID was set to 11111111 with S-ON and LOCKED bootloader, HBOOT 1.57
I tried to install 7.17.1540 RUU but got a BRICK with 1.61 HBOOT.
Now main version os shows 6.13.708.1 (7.17.1540.4)
Have only access to fastboot. Screen shows HTC logo with 4 triangles. On USB disconnection shows recovery with only "RUU" text.
Tried to flash through fastboot 401 and 708 firmwares, but getting: SBL1 = Fail-PU or Signature verify failed etc.
By RUU having error 152 or 155 or 12.
Non RUU or ZIP won't flash.
Don't know, what to do, please help!
Click to expand...
Click to collapse
You must complete the flash of the 7.17.1540 ruu to get out of ruu mode. What is your "fastboot getvar all"? Are you flashing a zip or exe ruu? If you are flashing a zip ruu are you using htc_fastboot.exe instead of fastboot.exe? Is the md5 good on your ruu?
Sent from my HTC One using XDA Labs

alray said:
You must complete the flash of the 7.17.1540 ruu to get out of ruu mode. What is your "fastboot getvar all"? Are you flashing a zip or exe ruu? If you are flashing a zip ruu are you using htc_fastboot.exe instead of fastboot.exe? Is the md5 good on your ruu?
Sent from my HTC One using XDA Labs
Click to expand...
Click to collapse
Im using simple fastboot.exe. Tried to install through RUU (getting errors 152 and 155) and ZIP (but it won't flash images bigger than 1.5 GB). don't know about md5.
can't get "getvar all". But it has superCID with system image of 6.13.708.1. But came from service with 6.17.401.5 with unability to update by OTA.

lyrgo23 said:
Im using simple fastboot.exe. Tried to install through RUU (getting errors 152 and 155) and ZIP (but it won't flash images bigger than 1.5 GB). don't know about md5.
can't get "getvar all". But it has superCID with system image of 6.13.708.1. But came from service with 6.17.401.5 with unability to update by OTA.
Click to expand...
Click to collapse
You must use htc_fastboot.exe to flash a 7.xx.xxx.x ruu and you must check the md5 value of your ruu to confirm it's integrity. Why can't you post the output of "fastboot getvar all"? Need to know your Cid, mid, version-main, hboot version...
You also need s-off to flash a ruu that doesn't have the same base version. Your phone looks pretty messed up, that's why a complete "fastboot getvar all" would help determine the best way to get everything back to normal
Sent from my HTC One using XDA Labs

alray said:
You must use htc_fastboot.exe to flash a 7.xx.xxx.x ruu and you must check the md5 value of your ruu to confirm it's integrity. Why can't you post the output of "fastboot getvar all"? Need to know your Cid, mid, version-main, hboot version...
You also need s-off to flash a ruu that doesn't have the same base version. Your phone looks pretty messed up, that's why a complete "fastboot getvar all" would help determine the best way to get everything back to normal
Sent from my HTC One using XDA Labs
Click to expand...
Click to collapse
C:\adb>fastboot getvar all
(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: 6.13.708.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA3C2W158269
(bootloader) imei: 355859056916623
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3855mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU (Hboot PreUpdate)
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Execution time is 52(ms)

Tried to install RUU EXE Brightstar. Having error 152.

Tried to install 7.17.708.21 ZIP RUU. having error 51 partition update fail. Picture attached.

lyrgo23 said:
C:\adb>fastboot getvar all
(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: 6.13.708.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3855mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU (Hboot PreUpdate)
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Execution time is 52(ms)
Click to expand...
Click to collapse
Hboot PreUpdate mean that the RUU wasn't flashed completely, it went trough the hboot pre-update (first flash) and is now waiting for the second flash to finish.
lyrgo23 said:
Tried to install RUU EXE Brightstar. Having error 152.
Click to expand...
Click to collapse
Your phone is S-ON, running a x.xx.708.x base, MID PN0710000.
Brightsar US (aka Dev Edititon) is a x.xx.1540.x bas for MID PN0712000
You can't use this ruu unless you achieve S-OFF and change your MID number.
lyrgo23 said:
Tried to install 7.17.708.21 ZIP RUU. having error 51 partition update fail. Picture attached.
Click to expand...
Click to collapse
So now your "fastboot getvar all" isn't the same....
version-main is now: 6.13.708.1 (7.18.708.21)
so you must complete the 7.18.708.21 flash to get out of RUU mode....
and I guess the boot-mode isn't "Hboot PreUpdate" anymore...?
Try to flash the RUU again using htc_fastboot.exe and copy/paste your command window in your next post so we can see everything.

but 7.18.708.21 RUU is for model PN0714000. Mine is PN0710000. shows image error

lyrgo23 said:
but 7.18.708.21 RUU is for model PN0714000. Mine is PN0710000. shows image error
Click to expand...
Click to collapse
Sorry I miss-read your getvar, this explain everything. You either don't have the right MID or the right version installed on your phone. This phone was clearly S-OFF at some point and someone either changed the MID or the firmware version (since they don't match together) and turned back S-ON. Supercid (11111111) also confirm that your phone was s-off. You already have supercid so CID doesn't matters, flash a RUU that match your MID like 7.19.401.xx. If this is still failing you'll need s-off again to fix it.

[HELP] Returning HTC One (M7) to Stock ROM

Hey guys, What's up?
First of all, I must mention what happened, I always had an iPhone, and I bought a HTC One (M7) like 2 years ago, and I never thought about rooting it..
One year ago, my friend suggested that he can upgrade it to Lollipop, and he seemed so confident lol, and I think he messed it up, I do have Lollipop on it, but it's SO BUGGY!, The phone gets so HOT easily! keeps crashing! and many many other problems..
So I decided to have the Stock ROM back, and I started reading how, but honestly, it's so difficult since I don't know what he has done to the phone..
The only thing I remember he did: He was coming to this forum and mentioned that this is the best forums for Android devs..
So.. Can anyone please help me get my phone back to Stock ROM?
Tell me what to do first? What I need to have?
And most important, help me find the right files for my phone?
Thanks alot,
Have a nice day

Stock like in GPE or Sense?
IF you have international M7 not verizon, sprint etc.
The most simple method would be just flashing nearly stock tweaked rom through recovery i.e. this one:
Sense: http://forum.xda-developers.com/showthread.php?t=2183023
GPE: http://forum.xda-developers.com/htc-one/development/rom-google-play-edition-lollipop-v1-00-t2963927
Full on back to stock would require using fastboot and RUU images, but you wouldn't gain anything from that.

MahmoudM10 said:
Hey guys, What's up?
First of all, I must mention what happened, I always had an iPhone, and I bought a HTC One (M7) like 2 years ago, and I never thought about rooting it..
One year ago, my friend suggested that he can upgrade it to Lollipop, and he seemed so confident lol, and I think he messed it up, I do have Lollipop on it, but it's SO BUGGY!, The phone gets so HOT easily! keeps crashing! and many many other problems..
So I decided to have the Stock ROM back, and I started reading how, but honestly, it's so difficult since I don't know what he has done to the phone..
The only thing I remember he did: He was coming to this forum and mentioned that this is the best forums for Android devs..
So.. Can anyone please help me get my phone back to Stock ROM?
Tell me what to do first? What I need to have?
And most important, help me find the right files for my phone?
Thanks alot,
Have a nice day
Click to expand...
Click to collapse
We will first need to know the exact info about your phone. You'll need to have adb and fastboot installed on your computer, if you don't have it yet, I would suggest you to download the simplified version (Minimal adb and fastboot). You'll also need to have HTC drivers installed on your computer. Once both are installed, reboot your phone in bootloader mode (hold power and volume down), make sure your phone is in "fastboot usb" (showing a red "fastboot usb" caption, if not select "fastboot" from the bootloader menu), then start a "minimal adb and fastboot" command prompt (start menu --> program --> Minimal adb and fastboot ---> Minimal adb and fastboot.exe). Type "fastboot getvar all" and hit enter. Copy/paste the output here (remove your IMEI, MEID and SerialNo before posting).
Should look like this:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.43.0000
(bootloader) version-baseband: 4A.13.3231.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.707.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FAxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: xxxxxxxxxxxx
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4011mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT

FeelThePoveR said:
Stock like in GPE or Sense?
IF you have international M7 not verizon, sprint etc.
The most simple method would be just flashing nearly stock tweaked rom through recovery i.e. this one:
Sense: http://forum.xda-developers.com/showthread.php?t=2183023
GPE: http://forum.xda-developers.com/htc-one/development/rom-google-play-edition-lollipop-v1-00-t2963927
Full on back to stock would require using fastboot and RUU images, but you wouldn't gain anything from that.
Click to expand...
Click to collapse
Hey FeelThePoveR,
Well, I don't really know what are verizon or sprint... and I don't know how to know..
but I live in Israel, and bought it from a private store, so I guess I have the international M7.. (makes sense? :/ )
Honestly, I want it back to stock so I can do whatever I want with my phone knowing what I'm doing..
I have some experience with adb and fastboot already.. I have ubuntu as well, it's not gonna be hard for me to follow instructions.. my WHOLE problem is.. that I don't know the condition of my phone.. what's wrong with it..
for example.. all the time I thought I have root, I tried to follow instructions few days ago to install something..
and I checked my root via Root Checker app, and it says that I don't have root installed proberly..
So yeah.. I want my phone back to stock.. :/
And yeah it's Sense not GPE..
Any suggestions?
(I'm gonna post in a reply the "getvar" info in few hours..)
Thanks alot for giving me some of your time
Have a nice day..

alray said:
We will first need to know the exact info about your phone. You'll need to have adb and fastboot installed on your computer, if you don't have it yet, I would suggest you to download the simplified version (Minimal adb and fastboot). You'll also need to have HTC drivers installed on your computer. Once both are installed, reboot your phone in bootloader mode (hold power and volume down), make sure your phone is in "fastboot usb" (showing a red "fastboot usb" caption, if not select "fastboot" from the bootloader menu), then start a "minimal adb and fastboot" command prompt (start menu --> program --> Minimal adb and fastboot ---> Minimal adb and fastboot.exe). Type "fastboot getvar all" and hit enter. Copy/paste the output here (remove your IMEI, MEID and SerialNo before posting).
Should look like this:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.43.0000
(bootloader) version-baseband: 4A.13.3231.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.707.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FAxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: xxxxxxxxxxxx
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4011mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
Click to expand...
Click to collapse
Hey alray,
I've been trying to get fastboot to work on my Windows for all day now..
and I tried following your instructions and files you mentioned above..
But I still get "< waiting for any device >", it doesn't recognize my phone..
tried downloading Android-SDK and installed google usb drivers as well..
It didn't work..
That's why I didn't post the getvar info yet :/
So I'm thinking about trying to do that on my Ubuntu..
but It's gonna take few hours until I'm on my laptop..
then I'll post the getvar info
For now, I don't know if that helps,
But I do know that my phone is TAMPERED + UNLOCKED + S-OFF
Thanks for your time..

Windows can be weird that way. You just have to manually install the driver.
I think I used that driver pack http://d-h.st/23V .
Unpack it, connect your phone in fastboot mode, go to device manager in the control panel and search for your device, than right click on it and select update drivers, browse my computer and select the folder with drivers.
Voila it should be working now.

Hey..
Here's my getvar info:
Code:
(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:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__K18
(bootloader) battery-status: good
(bootloader) battery-voltage: 3874mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
NOTE: I didn't hide the meid field.. it's all zeros (is that okay?)

MahmoudM10 said:
Hey..
Here's my getvar info:
Code:
(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:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__K18
(bootloader) battery-status: good
(bootloader) battery-voltage: 3874mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Since your phone is S-OFF you can simply flash the international version on it but before flashing the international RUU, you'll have to change your CID and then update your firmware.
Download these 2 files and save it in your adb/fastboot folder on your computer:
RUU: https://www.androidfilehost.com/?fid=24391638059058554
htc_fastboot.exe (this version is needed to flash the RUU, not the regular fastboot): https://www.androidfilehost.com/?fid=24341993505161791
Change your CID to SuperCID:
Code:
fastboot oem writecid 11111111
fastboot reboot-bootloader
and confirm your cid is now 11111111 (8 times 1) using "fastboot getvar all"
Download the attached firmware.zip file and save it in your adb/fastboot folder on your computer
Then with the phone in bootloader mode:
Code:
fastboot oem rebootRUU
phone will reboot to a black screen with silver HTC logo (RUU mode), you can now flash the firmware:
Code:
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
You'll have to do the "fastboot flash zip" command twice, fist time it will fail. Ignore the green progress bar on your phone, it will not reach 100% just confirm in the command window that everything is OK.
Now that you are back in bootloader make sure your hboot is now 1.57 and your version-main is 7.19.401.102. If yes go back in ruu mode and flash the RUU:
Code:
fastboot oem rebootRUU
htc_fastboot flash zip PN07IMG_M7_U_L50_SENSE60_MR_HTC_Europe_7.19.401.151_Radio_4T.35.3218.16_10.33Q.1718.01D_release_458806_signed.zip
fastboot reboot
Make sure to use htc_fastboot to flash the RUU and not the regular fastboot.
NOTE: I didn't hide the meid field.. it's all zeros (is that okay?)[/QUOTE]
Thats fine, only CDMA phones have both an IMEI and MEID numbers (yours is GSM and only have an IMEI number)

alray said:
Since your phone is S-OFF you can simply flash the international version on it but before flashing the international RUU, you'll have to change your CID and then update your firmware.
Download these 2 files and save it in your adb/fastboot folder on your computer:
RUU: https://www.androidfilehost.com/?fid=24391638059058554
htc_fastboot.exe (this version is needed to flash the RUU, not the regular fastboot): https://www.androidfilehost.com/?fid=24341993505161791
Change your CID to SuperCID:
Code:
fastboot oem writecid 11111111
fastboot reboot-bootloader
and confirm your cid is now 11111111 (8 times 1) using "fastboot getvar all"
Download the attached firmware.zip file and save it in your adb/fastboot folder on your computer
Then with the phone in bootloader mode:
Code:
fastboot oem rebootRUU
phone will reboot to a black screen with silver HTC logo (RUU mode), you can now flash the firmware:
Code:
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
You'll have to do the "fastboot flash zip" command twice, fist time it will fail. Ignore the green progress bar on your phone, it will not reach 100% just confirm in the command window that everything is OK.
Now that you are back in bootloader make sure your hboot is now 1.57 and your version-main is 7.19.401.102. If yes go back in ruu mode and flash the RUU:
Code:
fastboot oem rebootRUU
htc_fastboot flash zip PN07IMG_M7_U_L50_SENSE60_MR_HTC_Europe_7.19.401.151_Radio_4T.35.3218.16_10.33Q.1718.01D_release_458806_signed.zip
fastboot reboot
Make sure to use htc_fastboot to flash the RUU and not the regular fastboot.
NOTE: I didn't hide the meid field.. it's all zeros (is that okay?)
Click to expand...
Click to collapse
Thats fine, only CDMA phones have both an IMEI and MEID numbers (yours is GSM and only have an IMEI number)[/QUOTE]
Hey alray,
Thanks for the instructions, but I have a question..
The fastboot you mentioned, ends with '.exe', which means it's for Windows, and I couldn't get my Windows to recognize my phone, so I'm using Ubuntu..
How can I get this fastboot for linux?
Thanks alot

MahmoudM10 said:
Hey alray,
Thanks for the instructions, but I have a question..
The fastboot you mentioned, ends with '.exe', which means it's for Windows, and I couldn't get my Windows to recognize my phone, so I'm using Ubuntu..
How can I get this fastboot for linux?
Thanks alot
Click to expand...
Click to collapse
Idk if there is a Linux version but there is a Windows and a MacOS version on htcdev.com

thanks boyy
thanks friends

possible brickage

i attempted to unlock bootloader on my wife's old HTC M7 (Australian/Vodafone), i was able to unlock the bootloader, but had to do some serious trial and error to get a custom recovery installed, eventually got an older twrp loaded, but the phone just refused to boot into recovery.
i then relocked the bootloader (no S-OFF), and when i try and unlock he bootloader now, the phone attempts to boot into the recovery, and is failing...
i've been trying to find an RUU from somewhere, just to blat the phone back to an old state, and try again.
are there RUUs available anywhere? i dont' care if its not for the local carrier, i just want to get a basic android rom on the thing.
However, im curious if i need to s-off to do this (wasnt the case with my previous HTC)
help!
<<<I NOW KNOW WHAT THE ISSUE WAS, I WAS FLASHING RECOVERY FROM THE HTC M8, NOT M7>>>
any ideas?

gjw00 said:
i then relocked the bootloader (no S-OFF), and when i try and unlock he bootloader now, the phone attempts to boot into the recovery, and is failing...
Click to expand...
Click to collapse
Really bad idea to relock the bootloader with a custom recovery, well you shouldn't relock at all if there is anything "custom" installed on your phone.The process of unlocking bootloader requires the stock recovery. The only way to flash the recovery partition is when the bootloader is unlocked or by flashing a signed firmware.zip or ruu.zip. The firmware.zip or ruu.zip must match your version-main, CID and MID.
i've been trying to find an RUU from somewhere, just to blat the phone back to an old state, and try again.
are there RUUs available anywhere? i dont' care if its not for the local carrier, i just want to get a basic android rom on the thing.
Click to expand...
Click to collapse
Its not working like that. If your phone is S-ON the ruu must be made for your carrier (must match CID and MID, must be same or newer version-main)
post the output of "fastboot getvar all" (remove your imei and serialno)

alray said:
Really bad idea to relock the bootloader with a custom recovery, well you shouldn't relock at all if there is anything "custom" installed on your phone.The process of unlocking bootloader requires the stock recovery. The only way to flash the recovery partition is when the bootloader is unlocked or by flashing a signed firmware.zip or ruu.zip. The firmware.zip or ruu.zip must match your version-main, CID and MID.
Its not working like that. If your phone is S-ON the ruu must be made for your carrier (must match CID and MID, must be same or newer version-main)
post the output of "fastboot getvar all" (remove your imei and serialno)
Click to expand...
Click to collapse
ok, i've been trying with a bunch of RUUs i found on the web, and trying to flash inside RUU (wasnt 100% sure what rebooting to RUU was for actually)
the CID is VODAP021, i will need to check when i get back home to see what the MID is, its not the GPE of the m7, if that helps, you reckon if i find an OTA update, and extract out the ruu.zip, it might blat a stock recovery on? will i need to use htc_fastboot, or just the standard fastboot?
my nexus 5 has finally shat it (small child cracked screen, now screen has crapped itself), just want to get a basic android build onto the m7 in the final few weeks before the new pixel phones are out...

gjw00 said:
ok, i've been trying with a bunch of RUUs i found on the web, and trying to flash inside RUU (wasnt 100% sure what rebooting to RUU was for actually)
the CID is VODAP021, i will need to check when i get back home to see what the MID is, its not the GPE of the m7, if that helps, you reckon if i find an OTA update, and extract out the ruu.zip, it might blat a stock recovery on? will i need to use htc_fastboot, or just the standard fastboot?
my nexus 5 has finally shat it (small child cracked screen, now screen has crapped itself), just want to get a basic android build onto the m7 in the final few weeks before the new pixel phones are out...
Click to expand...
Click to collapse
You can extract a firmware.zip (not an ruu) from an ota update and flash it to restore the stock recovery. You must use the right version. Waiting for your fastboot getvar all.
Sent from my HTC One using XDA Labs

fastboot getvar all
(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.51
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: VODAP021
(bootloader) battery-status: good
(bootloader) battery-voltage: 4322mV
(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

gjw00 said:
fastboot getvar all
(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.51
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: VODAP021
(bootloader) battery-status: good
(bootloader) battery-voltage: 4322mV
(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
7.21.980.51 is the latest version for vodap021 and can't find a 7.21.980.51 firmware.zip or ota.zip.
At least there is a 7.21.980.51 ruu on ir-file.com, bad news is that you must register to this website to be able to download (20$ for 30 days)
http://ir-file.com/show.php?token=32375

i can load the phone into the OS btw, i've a feeling that OTA might on the device, you think its' accessible using a non-root browser? i could maybe get the ota zip off the device and try flashing that in RUU?

gjw00 said:
i can load the phone into the OS btw, i've a feeling that OTA might on the device, you think its' accessible using a non-root browser? i could maybe get the ota zip off the device and try flashing that in RUU?
Click to expand...
Click to collapse
Yes, if you can capture the ota this is the best option (because its free). Look in your /download folder, you're looking for a long file name starting with "OTA_M7_UL_L50_SENSE60" and ending with ".zip". Save it on your computer and extract the "firmware.zip" file from it. Then reboot in RUU mode and flash the firmware:
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
Then you should be able to unlock again.

it worked! thank you..