[Q] Failed to apply OTA update after re-locking bootloader

[Q] Failed to apply OTA update after re-locking bootloader - AT&T HTC One (M8)

Sorry, delete this please. Dunno what I did wrong before but it works now.

I doubt these mean anything but here are the errors from fastboot oem lock:
...
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = 536739196 (0x1FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
FAILED (status read failed (No such device))
finished. total time: 6.135s
Again, it did go back to RE-LOCKED after this anyway, and running it again just gives:
...
(bootloader) Device was already locked!
OKAY [ 0.001s]
finished. total time: 0.001s

FYI, relocking bootloader is not required to OTA. You do however need to have stock recovery, stock ROM, and any files altered by root need to be restored.
Relocking bootloader is however required for RUU (unless S-off).

Related

[Q] USB unbrick problem

Hi All,
I tried to usb-unbrick my rooted phone some solutions, but the phone still usb-bricked. The sd card access is working, but the usb works only fastboot. ADB is not working.
I tried this solution http://forum.xda-developers.com/showthread.php?t=751265 but nothing has changed. I flashed the mtd0.img again and again. I have not got error messages and the fatboot oem boot result seems ok.
After this I unrooted the phone to the original stock rom like this post: http://forum.xda-developers.com/showpost.php?p=9889284&postcount=60 , but I still haven't got usb.
I rooted it again with hard work (no adb and usb, only temproot with visionary and terminal command what I used), and I tried some radio image, some rom, but nothing has changed. I still havn't got usb connection.
The fastboot oem boot output:
(bootloader) setup_tag addr=0x60000100 cmdline add=0x9D07B198
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 0
(bootloader) TAG:hwid 0x0
(bootloader) TAG:skuid 0x22F00
(bootloader) TAG:hero panel = 0x0
(bootloader) TAG:engineerid = 0x0
(bootloader) MCP dual-die
(bootloader) MCP dual-die
(bootloader) TAG:mono-die = 0x0
(bootloader) Device CID is not super CID
(bootloader) CID is HTC__032
(bootloader) setting->cid::HTC__032
(bootloader) serial number: HT03ZNX01346
(bootloader) commandline from head: no_console_suspend=1 console=null
(bootloader) command line length =446
(bootloader) active commandline: board_legend.disable_uart3=0 board_legen
(bootloader) d.usb_h2w_sw=0 board_legend.disable_sdcard=0 diag.enabled=0
(bootloader) board_legend.debug_uart=0 smisize=0 userdata_sel=0 androidbo
(bootloader) ot.emmc=false androidboot.baseband=7.05.35.26L androidboot.
(bootloader) cid=HTC__032 androidboot.carrier=HTC-EastEurope androidboot.
(bootloader) mid=PB7610000 androidboot.keycaps=qwerty androidboot.mode=no
(bootloader) rmal androidboot.serialno=HT03ZNX01346 androidboot.bootloade
(bootloader) r=1.01.0000 no_console_suspend=1 console=null
(bootloader) aARM_Partion[0].name=misc
(bootloader) aARM_Partion[1].name=recovery
(bootloader) aARM_Partion[2].name=boot
(bootloader) aARM_Partion[3].name=system
(bootloader) aARM_Partion[4].name=cache
(bootloader) aARM_Partion[5].name=userdata
(bootloader) partition number=6
(bootloader) Valid partition num=6
FAILED (status read failed (Too many links))
finished. total time: 0.953s
The most important options seems ok:
board_legend.disable_uart3=0
board_legend.usb_h2w_sw=0
board_legend.disable_sdcard=0
diag.enabled=0
So I don't know what I have to do. What is the problem? I would be very happy, if somebody could help me.
Thanks!

Why am I not getting the final unlock bootloader screen?

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>

See the guide/flashing notes in my signature. It'll straighten you out. Stuck at step 13right?

Redownload the bin file, if you noticed it cought it being 0kb of size.
Also ensure that the phone is seen correctly under windows.
Sent from my PG86100 using Tapatalk

That happened to me the bootloader unlock option did not want to come .. i am sure your number software ends with 3 . Or higher what i did i ran the 2.17.651.2 ruu shotter and after that i had no problems . If you run the ruu.shotter you will lose all your data.
Sent from my HTC.EVO.3D.Xda Premium

Amy luck
Sent from my HTC.EVO.3D.Xda Premium

Any luck?
Sent from my HTC.EVO.3D.Xda Premium

darkstar765 said:
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>
Click to expand...
Click to collapse
Download and run The 2.08 RUU Then Use the htc Unlock I had the same problem today this works

Why am I not getting the final unlock bootloader screen?

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

Help with S-Off

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!

Lock bootloader problem

Hello,
today I unlock bootloader to install EX Kernel, after few test I back to stock boot img and try to lock bootloader but I have:
Code:
fastboot oem lock
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.051s]
finished. total time: 0.051s
fastboot oem lock
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Flash valid Android images now
(bootloader) Then re-run this command to lock
OKAY [ 0.052s]
finished. total time: 0.052s
My soft:

Better Mobile App

welcome