Related
I have followed all of the instructions to a T like 5 times to no avail. Can someone please tell me what I may be doing wrong?
Here is a copy of my command prompt:
C:\Users\Jerry>cd c:\.android
c:\.android>fastboot oem get_identifier_token
...
(bootloader)
(bootloader) < Please cut following message >
(bootloader) <<<< Identifier Token Start >>>>
(bootloader) 48888EEB9889D124D6C72F309EB940E2
(bootloader) 4CF40D0980840AF3DBB8CE4A486C056F
(bootloader) B42CE3D1056CAA6E3BE6884B5A28F120
(bootloader) C3B4E7E9173E3A55070B1A910E2497CD
(bootloader) A10C7FCE2ECE00C595C9DEE4B4D2A0C9
(bootloader) 219FF2E5D0C5019BDD3CA2EE7E28D44B
(bootloader) 875A72786356791FD909F85FE585D75C
(bootloader) 066E93AB9754291B9EC07CF026967276
(bootloader) EFA05F5E63FD78921D794C18CB1FBE22
(bootloader) AA76C231B26418110079C337E1CBA85C
(bootloader) 32549FCB5270D515775DF1DB9EB7C42D
(bootloader) A835495897A09826555C5147F5A7DC51
(bootloader) 059061DBC08128A32501EA28C1C0736F
(bootloader) 1F55865A90703A538D44517E85259D43
(bootloader) D17D85912695F9E8A3F24E3AF917B299
(bootloader) 4DEF2BBCBAB92B36D0D778673321E5CB
(bootloader) <<<<< Identifier Token End >>>>>
OKAY [ 0.070s]
finished. total time: 0.070s
c:\.android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.151s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.007s]
finished. total time: 0.159s
c:\.android>
Downgrade ruu... See the hboot 1.5 sticky
Sent from my freshevo 3d on the now network
Hello all,
I've read many forum posts and have had no luck with my current situation, so I made an account and am reaching out to the community for assistance. I had bought a phone off ebay that I used for many months that was S-ON but unlocked--I ran many ROMS that worked on S-ON just fine. However, I've recently decided I'd like to work on an S-off ROM. I went all the way back to stock RUU using the main guide here on XDA (though, my bootloader still said it was "tampered" and "relocked" FWIW). I went back to stock, and took both OTAs to get to 2.06. I tried both the revone.dna (-1 and -2 errors) and moonshine (don't drink and shine after 10 "moonshining" attempts). Does anyone have any advice as to what I need to do to get unlocked again, become S-off, and then allow me to go forward with my own recovery and ROM of choice? I appreciate any help.
Thanks,
Andy
albernhagen said:
Hello all,
I've read many forum posts and have had no luck with my current situation, so I made an account and am reaching out to the community for assistance. I had bought a phone off ebay that I used for many months that was S-ON but unlocked--I ran many ROMS that worked on S-ON just fine. However, I've recently decided I'd like to work on an S-off ROM. I went all the way back to stock RUU using the main guide here on XDA (though, my bootloader still said it was "tampered" and "relocked" FWIW). I went back to stock, and took both OTAs to get to 2.06. I tried both the revone.dna (-1 and -2 errors) and moonshine (don't drink and shine after 10 "moonshining" attempts). Does anyone have any advice as to what I need to do to get unlocked again, become S-off, and then allow me to go forward with my own recovery and ROM of choice? I appreciate any help.
Thanks,
Andy
Click to expand...
Click to collapse
I just got through doing this myself, and had the exact same problem. I successfully got S-Off even when using DigitalDream 2.2 ROM. Here's what I did.
Step 1: Go to this link (http://forum.xda-developers.com/showthread.php?t=2314771) and use the stuff at the very bottom of the first post where it says to download 2.06 firmware and to flash that first. If you can an error when flashing the firmware, don't worry about it. Just do the fastboot reboot-bootloader command then power off the phone completely and turn it back on (as the instructions say.
Step 2: I used the FacePalm method (http://forum.xda-developers.com/showthread.php?t=2155069). I only downloaded the boot.img and firmware. Follow the steps for the FacePalm method. That successfully got me S-Off.
Thanks
Thanks for your response, BoogaBooga. I tried this out, but it seems that I'm out of luck because I'm relocked as opposed to unlocked. Here's what I saw when attempting FacePalm:
C:\Users\andyb_000\Downloads\adt-bundle-windows-x86_64-20130219\sdk\backup of pl
atform-tools\platform-tools>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Users\andyb_000\Downloads\adt-bundle-windows-x86_64-20130219\sdk\backup of pl
atform-tools\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.043s]
finished. total time: 0.044s
C:\Users\andyb_000\Downloads\adt-bundle-windows-x86_64-20130219\sdk\backup of pl
atform-tools\platform-tools>fastboot flash zip dna2.06firmware.zip
< waiting for device >
sending 'zip' (33119 KB)...
OKAY [ 2.411s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[boot] unzipping & flushing...
(bootloader) [RUU]UZ,boot,0
(bootloader) [RUU]UZ,boot,11
(bootloader) [RUU]UZ,boot,25
(bootloader) [RUU]UZ,boot,38
(bootloader) [RUU]UZ,boot,52
(bootloader) [RUU]UZ,boot,66
(bootloader) [RUU]UZ,boot,79
(bootloader) [RUU]UZ,boot,90
(bootloader) [RUU]UZ,boot,100
(bootloader) [RUU]WP,boot,0
(bootloader) [RUU]WP,boot,99
(bootloader) [RUU]WP,boot,100
(bootloader) ...... Successful
(bootloader) start image[hboot] unzipping & flushing...
(bootloader) [RUU]UZ,hboot,0
(bootloader) [RUU]UZ,hboot,51
(bootloader) [RUU]UZ,hboot,100
(bootloader) signature checking...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
(bootloader) start image[recovery] unzipping & flushing...
(bootloader) [RUU]UZ,recovery,0
(bootloader) [RUU]UZ,recovery,11
(bootloader) [RUU]UZ,recovery,22
(bootloader) [RUU]UZ,recovery,36
(bootloader) [RUU]UZ,recovery,48
(bootloader) [RUU]UZ,recovery,74
(bootloader) [RUU]UZ,recovery,86
(bootloader) [RUU]UZ,recovery,97
(bootloader) [RUU]UZ,recovery,100
(bootloader) [RUU]WP,recovery,0
(bootloader) [RUU]WP,recovery,99
(bootloader) [RUU]WP,recovery,100
(bootloader) ...... Successful
(bootloader) start image[radio] unzipping & flushing...
(bootloader) [RUU]UZ,radio,0
(bootloader) [RUU]UZ,radio,9
(bootloader) [RUU]UZ,radio,18
(bootloader) [RUU]UZ,radio,27
(bootloader) [RUU]UZ,radio,36
(bootloader) [RUU]UZ,radio,41
(bootloader) [RUU]UZ,radio,50
(bootloader) [RUU]UZ,radio,59
(bootloader) [RUU]UZ,radio,68
(bootloader) [RUU]UZ,radio,73
(bootloader) [RUU]UZ,radio,82
(bootloader) [RUU]UZ,radio,87
(bootloader) [RUU]UZ,radio,99
(bootloader) [RUU]UZ,radio,100
(bootloader) [RUU]WP,radio,0
(bootloader) [RUU]WP,radio,36
(bootloader) [RUU]WP,radio,73
(bootloader) [RUU]WP,radio,100
(bootloader) ...... Successful
OKAY [ 17.400s]
finished. total time: 19.810s
C:\Users\andyb_000\Downloads\adt-bundle-windows-x86_64-20130219\sdk\backup of pl
atform-tools\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.036s]
finished. total time: 0.037s
C:\Users\andyb_000\Downloads\adt-bundle-windows-x86_64-20130219\sdk\backup of pl
atform-tools\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.039s]
finished. total time: 0.040s
C:\Users\andyb_000\Downloads\adt-bundle-windows-x86_64-20130219\sdk\backup of pl
atform-tools\platform-tools>fasboot flash zip PL8320000-DNA.zip
'fasboot' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\andyb_000\Downloads\adt-bundle-windows-x86_64-20130219\sdk\backup of pl
atform-tools\platform-tools>fastboot flash zip PL8320000-DNA.zip
sending 'zip' (36905 KB)...
OKAY [ 2.680s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
FAILED (remote: 43 main version check fail)
finished. total time: 8.814s
C:\Users\andyb_000\Downloads\adt-bundle-windows-x86_64-20130219\sdk\backup of pl
atform-tools\platform-tools>fastboot flash zip PL8320000-DNA.zip
sending 'zip' (36905 KB)...
OKAY [ 2.680s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
FAILED (remote: 43 main version check fail)
finished. total time: 8.815s
C:\Users\andyb_000\Downloads\adt-bundle-windows-x86_64-20130219\sdk\backup of pl
atform-tools\platform-tools>fastboot boot DNA-rescue.img
downloading 'boot.img'...
OKAY [ 0.813s]
booting...
FAILED (remote: not allowed)
finished. total time: 0.815s
C:\Users\andyb_000\Downloads\adt-bundle-windows-x86_64-20130219\sdk\backup of pl
atform-tools\platform-tools>^A
BoogaBooga said:
I just got through doing this myself, and had the exact same problem. I successfully got S-Off even when using DigitalDream 2.2 ROM. Here's what I did.
Step 1: Go to this link (http://forum.xda-developers.com/showthread.php?t=2314771) and use the stuff at the very bottom of the first post where it says to download 2.06 firmware and to flash that first. If you can an error when flashing the firmware, don't worry about it. Just do the fastboot reboot-bootloader command then power off the phone completely and turn it back on (as the instructions say.
Step 2: I used the FacePalm method (http://forum.xda-developers.com/showthread.php?t=2155069). I only downloaded the boot.img and firmware. Follow the steps for the FacePalm method. That successfully got me S-Off.
Click to expand...
Click to collapse
After I updated to 2.06 (the stock way), I ended up reunlocking using the original unlock key I got from the HTCDEV site. Not exactly sure how you unlocked yours the first time, so I'm not sure if that will help you or not.
BoogaBooga said:
After I updated to 2.06 (the stock way), I ended up reunlocking using the original unlock key I got from the HTCDEV site. Not exactly sure how you unlocked yours the first time, so I'm not sure if that will help you or not.
Click to expand...
Click to collapse
Since I bought the phone already unlocked, I never had the old unlock key. I suppose I can contact the guy I bought it from and see if he still has it. Any other ideas in the meantime?
I'm really not sure. Have you tried this?
http://forum.xda-developers.com/showthread.php?t=2109862
BoogaBooga said:
I'm really not sure. Have you tried this?
http://forum.xda-developers.com/showthread.php?t=2109862
Click to expand...
Click to collapse
I received help from Beaups and got things working. It was a problem with my supercid. We did basically what happens in post #5 here:
http://forum.xda-developers.com/showthread.php?t=2407640
Thanks!
Here's the life story of my phone as far as tampering with the system files.
HTC Dev Unlock to get an unlocked bootloader
Flashed TWRP to my recovery partition
Made a backup, but I think I just included the default partitions and no more no less.
Flashed SuperSU
Used Rumrunner S-Off for AT&T 3.17.502.3 successfully
In preparation for AR31, I attempted to flash the 3.63.X.X firmware.zip, and failed miserably. One person later pointed out that it was because I was using the wrong model. Here's the log:
Code:
C:\adb>adb reboot bootloader
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: REMOVED
(bootloader) imei: REMOVED
(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: 4230mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.075s
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.042s]
finished. total time: 0.042s
C:\adb>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.048s]
finished. total time: 0.050s
C:\adb>fastboot flash zip C:\adb\firmware.zip
sending 'zip' (28043 KB)...
OKAY [ 2.497s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 2.915s
C:\adb>fastboot flash zip C:\adb\firmware.zip
sending 'zip' (28043 KB)...
OKAY [ 2.520s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 2.941s
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.040s]
finished. total time: 0.040s
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: REMOVED
(bootloader) imei: REMOVED
(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: 4234mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.090s
C:\adb>fastboot oem writecid 11111111
...
(bootloader) Start Verify: 0
(bootloader) Input CID is super CID
(bootloader) Start Verify: 0
OKAY [ 0.082s]
finished. total time: 0.082s
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.040s]
finished. total time: 0.041s
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: REMOVED
(bootloader) imei: REMOVED
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4242mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.084s
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.041s]
finished. total time: 0.042s
C:\adb>fastboot flash zip C:\adb\firmware.zip
sending 'zip' (28043 KB)...
OKAY [ 2.505s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 2.540s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.040s
After that failed, I decided I was just going to forget about it (as it was optional and I didn't want to risk anything worse than an error message), and instead, install Android Revolution by itself instead. As I entered my bootloader, I was greeted by *TAMPERED* / *LOCKED*. The bootloader was still S-OFF, so I assumed I could install AR31 regardless. It worked, but as I'm preparing to flash the proper firmware.zip from http://forum.xda-developers.com/showthread.php?t=2485651, it is a bit worrying to me. I already tried fastboot flash Unlock_code.bin so that I could just unlock the bootloader again and restore from the previous backup, but it refused to do so and gave me an error.
Anyways, with the information out there, should I even be worried about this considering I have S-Off? In either case, how do I solve the situation? It's a little worrying to me.
FreeK200 said:
Here's the life story of my phone as far as tampering with the system files.
HTC Dev Unlock to get an unlocked bootloader
Flashed TWRP to my recovery partition
Made a backup, but I think I just included the default partitions and no more no less.
Flashed SuperSU
Used Rumrunner S-Off for AT&T 3.17.502.3 successfully
In preparation for AR31, I attempted to flash the 3.63.X.X firmware.zip, and failed miserably. One person later pointed out that it was because I was using the wrong model. Here's the log:
Code:
C:\adb>adb reboot bootloader
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: REMOVED
(bootloader) imei: REMOVED
(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: 4230mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.075s
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.042s]
finished. total time: 0.042s
C:\adb>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.048s]
finished. total time: 0.050s
C:\adb>fastboot flash zip C:\adb\firmware.zip
sending 'zip' (28043 KB)...
OKAY [ 2.497s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 2.915s
C:\adb>fastboot flash zip C:\adb\firmware.zip
sending 'zip' (28043 KB)...
OKAY [ 2.520s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 2.941s
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.040s]
finished. total time: 0.040s
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: REMOVED
(bootloader) imei: REMOVED
(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: 4234mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.090s
C:\adb>fastboot oem writecid 11111111
...
(bootloader) Start Verify: 0
(bootloader) Input CID is super CID
(bootloader) Start Verify: 0
OKAY [ 0.082s]
finished. total time: 0.082s
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.040s]
finished. total time: 0.041s
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: REMOVED
(bootloader) imei: REMOVED
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4242mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.084s
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.041s]
finished. total time: 0.042s
C:\adb>fastboot flash zip C:\adb\firmware.zip
sending 'zip' (28043 KB)...
OKAY [ 2.505s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 2.540s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.040s
After that failed, I decided I was just going to forget about it (as it was optional and I didn't want to risk anything worse than an error message), and instead, install Android Revolution by itself instead. As I entered my bootloader, I was greeted by *TAMPERED* / *LOCKED*. The bootloader was still S-OFF, so I assumed I could install AR31 regardless. It worked, but as I'm preparing to flash the proper firmware.zip from http://forum.xda-developers.com/showthread.php?t=2485651, it is a bit worrying to me. I already tried fastboot flash Unlock_code.bin so that I could just unlock the bootloader again and restore from the previous backup, but it refused to do so and gave me an error.
Anyways, with the information out there, should I even be worried about this considering I have S-Off? In either case, how do I solve the situation? It's a little worrying to me.
Click to expand...
Click to collapse
it failed because you where not in ruu mode here is a great guide for firmware flashing
http://forum.xda-developers.com/showthread.php?t=2316726
jerrycoffman45 said:
it failed because you where not in ruu mode here is a great guide for firmware flashing
http://forum.xda-developers.com/showthread.php?t=2316726
Click to expand...
Click to collapse
I believe I was in RUU mode. If you look in the log, I used "fastboot oem rebootRUU" prior to trying to flash the firmware, and I had the black background with a silver htc logo when I attempted this as well. In either case, unless I'm missing something entirely, I already realize that I did that incorrectly (trying to flash firmware with the wrong model ID), and I already have the correct firmware with the correct model id waiting. What I'm looking for though is for a solution to unlock my bootloader again. Somewhere along this process, my bootloader went from Unlocked to locked, and I didn't have anything to do with it aside from the failed flashes on the firmware. In no way, shape or form, did I even attempt to lock my bootloader again, so when I was preparing to flash the AR31 rom, it came as a surprise that it was locked.
FreeK200 said:
I believe I was in RUU mode. If you look in the log, I used "fastboot oem rebootRUU" prior to trying to flash the firmware, and I had the black background with a silver htc logo when I attempted this as well. In either case, unless I'm missing something entirely, I already realize that I did that incorrectly (trying to flash firmware with the wrong model ID), and I already have the correct firmware with the correct model id waiting. What I'm looking for though is for a solution to unlock my bootloader again. Somewhere along this process, my bootloader went from Unlocked to locked, and I didn't have anything to do with it aside from the failed flashes on the firmware. In no way, shape or form, did I even attempt to lock my bootloader again, so when I was preparing to flash the AR31 rom, it came as a surprise that it was locked.
Click to expand...
Click to collapse
Since you're s-off, you should be able to unlock using the process outlined here (http://forum.xda-developers.com/showthread.php?t=2475914)
M7 was badly misbehaving. Couldn't install apps from the drawer (to the home page) or from the home page directly. I get the vibration feedback and that's it.
There have been other issues as well.
I'd been on the OTA 4.4.3, but some app must have poisoned the phone.
In any case formatted data and wiped caches.
Have TWRP 2.8.02 installed. Unlocked and rooted.
I can get to TWRP or Fastboot with no issues.
But Sideload, push nor fastboot will take my OTArom.zip.
Tried dropping back to TWRP 2.7.11 after reading about some issues. No difference.
FAILED (remote: 24 parsing android-info fail) was the error from Fastboot flash zip rom.zip
sideload seemed to pass the rom but got "error updating executer binary" a couple secs after the sideload is done.
I'd rather install OEM instead of a TWRP back-up that is loaded with apps that might have caused the issues. But so far ......
When I try to copy a TWRP back up (via MTP), TWRP replies "can't copy - data.ext4.win000"
I'm on a Mac so I can't run .exe.
HELP!!
thanks.
fastboot getvar all
(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:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA##########
(bootloader) imei: #############
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4305mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
metropical said:
M7 was badly misbehaving. Couldn't install apps from the drawer (to the home page) or from the home page directly. I get the vibration feedback and that's it.
There have been other issues as well.
I'd been on the OTA 4.4.3, but some app must have poisoned the phone.
In any case formatted data and wiped caches.
Have TWRP 2.8.02 installed. Unlocked and rooted.
I can get to TWRP or Fastboot with no issues.
But Sideload, push nor fastboot will take my OTArom.zip.
FAILED (remote: 24 parsing android-info fail) was the error from Fastboot flash zip rom.zip
sideload seemed to pass the rom but got "error updating executer binary" a couple secs after the sideload is done.
I'd rather install OEM instead of a TWRP back-up that is loaded with apps that might have caused the issues. But so far ......
When I try to copy a TWRP back up (via MTP), TWRP replies "can't copy - data.ext4.win000"
I'm on a Mac so I can't run .exe.
thanks.
fastboot getvar all
(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:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA##########
(bootloader) imei: #############
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4305mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Since you are S-OFF try this RUU_M7UL_TMOUS_5.14.531.1_With_Partial-decrypted.zip
majmoz said:
Since you are S-OFF try this RUU_M7UL_TMOUS_5.14.531.1_With_Partial-decrypted.zip
Click to expand...
Click to collapse
thanks. from adb I assume?
metropical said:
thanks. from adb I assume?
Click to expand...
Click to collapse
No, you will flash it like firmware in fastboot. Rename your file to RUU.zip or substitute RUU.zip with your file name.
Put the phone in bootloader/FASTBOOT USB
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 RUU.zip[/I][/B]
Repeat the same command: IMPORTANT
Code:
[B][I]fastboot flash zip RUU.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:
No, you will flash it like firmware in fastboot. Rename your file to RUU.zip or substitute RUU.zip with your file name.
Click to expand...
Click to collapse
Martin:android fritz$ fastboot flash zip RUU.zip
sending 'zip' (1567273 KB)...
FAILED (remote: 02 data length is too large)
metropical said:
Martin:android fritz$ fastboot flash zip RUU.zip
sending 'zip' (1567273 KB)...
FAILED (remote: 02 data length is too large)
Click to expand...
Click to collapse
Have you tried the method nkk71 discussed in FAQ #3?
I don't use a Mac so I can not help you there.
majmoz said:
Have you tried the method nkk71 discussed in FAQ #3?
I don't use a Mac so I can not help you there.
Click to expand...
Click to collapse
yup. no difference
metropical said:
yup. no difference
Click to expand...
Click to collapse
Here is another zip 6.10.531.9 you can try. It might be closer to your system setup since it is for the version just prior to the latest from TMOUS. I looked for a firmware only package but I could not find one.
Make sure you check the MD5 of the files!!!
majmoz said:
Here is another zip 6.10.531.9 you can try. It might be closer to your system setup since it is for the version just prior to the latest from TMOUS. I looked for a firmware only package but I could not find one.
Make sure you check the MD5 of the files!!!
Click to expand...
Click to collapse
same issue - FAILED (remote: 02 data length is too large)
did check the md5.
Darn the Luck ! ! !
There must be another issue, coz that is pretty much the ROM I had. And I can't copy recent TWRP backups.
Something odd.
metropical said:
same issue - FAILED (remote: 02 data length is too large)
did check the md5.
Darn the Luck ! ! !
There must be another issue, coz that is pretty much the ROM I had. And I can't copy recent TWRP backups.
Something odd.
Click to expand...
Click to collapse
Try each of the following steps until successful:
If possible, copy your personal files and data off of the phone.
You can pull the recovery.img from the zip and flash it. It is the stock image.
In bootloader, select factory reset
You might be able to build your own firmware by removing the system.img from the zip. You can rename it firmware and flash like the RUU.
metropical said:
same issue - FAILED (remote: 02 data length is too large)
did check the md5.
Darn the Luck ! ! !
There must be another issue, coz that is pretty much the ROM I had. And I can't copy recent TWRP backups.
Something odd.
Click to expand...
Click to collapse
Use this and update your fastboot / adb
http://forum.xda-developers.com/showthread.php?t=2588979
clsA said:
Use this and update your fastboot / adb
http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
appreciate the input, but that's windows. I'm on a Mac. My adb is 1.0.31
metropical said:
appreciate the input, but that's windows. I'm on a Mac. My adb is 1.0.31
Click to expand...
Click to collapse
their old, find new download the SDK
majmoz said:
Try each of the following steps until successful:
If possible, copy your personal files and data off of the phone.
You can pull the recovery.img from the zip and flash it. It is the stock image.
In bootloader, select factory reset
You might be able to build your own firmware by removing the system.img from the zip. You can rename it firmware and flash like the RUU.
Click to expand...
Click to collapse
I have all my files.
when I unzip, I don't see recovery.img or system.zip.
might be the Mac vs Windows.
The phone has no OS right now.
metropical said:
I have all my files.
when I unzip, I don't see recovery.img or system.zip.
might be the Mac vs Windows.
The phone has no OS right now.
Click to expand...
Click to collapse
https://github.com/corbindavenport/nexus-tools
bin updated adb binary to 1.0.32, Dec 16, 2014
README.md Dec 16, 2014
install.sh Dec 16, 2014
license.txt Dec 10, 2013
Click to expand...
Click to collapse
clsA said:
https://github.com/corbindavenport/nexus-tools
Click to expand...
Click to collapse
cool.! nice tool. thanks. hope this fixes my issues.
metropical said:
cool.! nice tool. thanks. hope this fixes my issues.
Click to expand...
Click to collapse
Yeah I have only seen the FAILED (remote: 02 data length is too large) when fastboot was too old
good luck
clsA said:
Yeah I have only seen the FAILED (remote: 02 data length is too large) when fastboot was too old
good luck
Click to expand...
Click to collapse
Darn the Luck ! ! !
No green progress bar.
I tried the RUU linked on the previous page as well as this OTA of the same vintage.
after the following failure, I formatted data and attempted to wipe Dalvik and cache. I get "unable to mount cache".
Martin:~ fritz$ fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.052s]
finished. total time: 0.052s
Martin:~ fritz$ fastboot flash zip OTA_M7.zip
error: cannot load 'OTA_M7.zip'
Martin:~ fritz$ cd downloads/android
Martin:android fritz$ fastboot flash zip OTA_M7.zip
target reported max download size of 1514139648 bytes
sending 'zip' (564982 KB)...
OKAY [ 21.195s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 24.222s
Martin:android fritz$ fastboot flash zip OTA_M7.zip
target reported max download size of 1515827200 bytes
sending 'zip' (564982 KB)...
OKAY [ 21.187s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 24.219s
Martin:android fritz$ fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.559s]
finished. total time: 0.559s
Martin:android fritz$ fastboot reboot
rebooting...
finished. total time: 0.037s
Martin:android fritz$ adb devices
List of devices attached
FA35########### device
Martin:android fritz$ adb reboot recovery
Martin:android fritz$ fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.052s]
finished. total time: 0.052s
Martin:android fritz$ fastboot flash zip OTA_M7.zip
target reported max download size of 1514139648 bytes
sending 'zip' (564982 KB)...
OKAY [ 21.216s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 24.226s
Martin:android fritz$ fastboot flash zip OTA_M7.zip
target reported max download size of 1515827200 bytes
sending 'zip' (564982 KB)...
OKAY [ 21.212s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 24.244s
Martin:android fritz$ fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.522s]
finished. total time: 0.522s
Martin:android fritz$ fastboot reboot
rebooting...
finished. total time: 0.037s
metropical said:
Darn the Luck ! ! !
No green progress bar.
I tried the RUU linked on the previous page as well as this OTA of the same vintage.
after the following failure, I formatted data and attempted to wipe Dalvik and cache. I get "unable to mount cache".
Martin:~ fritz$ fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.052s]
finished. total time: 0.052s
Martin:~ fritz$ fastboot flash zip OTA_M7.zip
error: cannot load 'OTA_M7.zip'
Martin:~ fritz$ cd downloads/android
Martin:android fritz$ fastboot flash zip OTA_M7.zip
target reported max download size of 1514139648 bytes
sending 'zip' (564982 KB)...
OKAY [ 21.195s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 24.222s
Martin:android fritz$ fastboot flash zip OTA_M7.zip
target reported max download size of 1515827200 bytes
sending 'zip' (564982 KB)...
OKAY [ 21.187s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 24.219s
Martin:android fritz$ fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.559s]
finished. total time: 0.559s
Martin:android fritz$ fastboot reboot
rebooting...
finished. total time: 0.037s
Martin:android fritz$ adb devices
List of devices attached
FA35########### device
Martin:android fritz$ adb reboot recovery
Martin:android fritz$ fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.052s]
finished. total time: 0.052s
Martin:android fritz$ fastboot flash zip OTA_M7.zip
target reported max download size of 1514139648 bytes
sending 'zip' (564982 KB)...
OKAY [ 21.216s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 24.226s
Martin:android fritz$ fastboot flash zip OTA_M7.zip
target reported max download size of 1515827200 bytes
sending 'zip' (564982 KB)...
OKAY [ 21.212s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 24.244s
Martin:android fritz$ fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.522s]
finished. total time: 0.522s
Martin:android fritz$ fastboot reboot
rebooting...
finished. total time: 0.037s
Click to expand...
Click to collapse
That OTA.zip can only be flashed with stock recovery .. it's not a RUU or Rom.zip
you get unable to mount cache because you formatted it
fastboot erase cache causes this error
clsA said:
That OTA.zip can only be flashed with stock recovery .. it's not a RUU or Rom.zip
you get unable to mount cache because you formatted it
fastboot erase cache causes this error
Click to expand...
Click to collapse
how can I get back to stock recovery? I assume with the soft brick and other tries that haven't worked that is the only choice at this point?
do I need to OEM lock or ..........?
and getvar seems to indicate that there is no firmware version now.
fastboot getvar all
(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:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA##YW######
(bootloader) imei: ############
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4326mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Update: Fixed. Please delete thread.
Hi guys,
I have an HTC One M8 which was rooted, with TWRP and running CM 12, S-ON. I just wanted to put the stock ROM back on it, I don't care about the flags that says that the software is modified or anything like that.
For that I followed this thread.
Step 1: lock the bootloader. -> this worked. The status is now RELOCKED. ***Software modified***
Trying to flash TWRP doesn't work though, neither is the device listed through adb, bellow what I get in the command prompt.
C:\miniadb_m8> fastboot flash recovery openrecovery-twrp-2.8.4.0-m8.img
target reported max download size of 1826414592 bytes
sending 'recovery' (16092 KB)...
OKAY [ 1.740s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.321s
C:\miniadb_m8>adb devices
List of devices attached
C:\miniadb_m8>fastboot devices
xxxx fastboot
I looked up the RUU for my devices based on the information I got back by using fastboot getvar all and came across another post on this forum for my device (HTC__038) and tried flashing that RUU.zip file, bellow the output.
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.011s]
finished. total time: 0.011s
C:\adb>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.013s]
finished. total time: 0.013s
C:\adb>htc_fastboot flash zip RUU.zip
sending 'zip'... (53966 KB) OKAY
sending time = 2.648 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (status read failed (Too many links))
Execution time is 8(s).
I can't get around this, was wondering if someone can point me in the right direction, based on my device info:
C:\miniadb_m8>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxx
(bootloader) imei: xxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Any help is appreciated, thanks a lot.
Cheers,
Adrian