Fastboot Segmentation fault - Nexus 9 Q&A, Help & Troubleshooting

Hi,
I wanted to flash the stock image via fastboot but I keep getting these error
Code:
florian-MS-7788 volantis-mob30p # sh flash-all.sh
target reported max download size of 518205818 bytes
sending 'bootloader' (2898 KB)...
OKAY [ 0.217s]
writing 'bootloader'...
(bootloader) Device State : Unlocked
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[bct] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[mts_preboot_prod] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[mts_prod] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[hboot] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[nvtboot] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[nvtbootwb0] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[tos] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[sp1] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[gp1] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[pt] unzipping & flashing...
(bootloader) ...... Successful
OKAY [ 5.466s]
finished. total time: 5.683s
rebooting into bootloader...
OKAY [ 0.032s]
finished. total time: 0.182s
target reported max download size of 518205818 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
Info: zone aligned segment0 blkaddr: 512
Segmentation fault
It is not the first time I flashed back to stock, so bootloader is unlocked.
If it is important I'm using Linux mint 18

Have you tried flashing the images separately, instead of using the script?
Un zip the archive to get all images.

Flashing the images seperately seems to work as a workaround, but does not solve the error. I also tryed formatting all partitions in twrp.
Thanks

Flo9818 said:
Flashing the images seperately seems to work as a workaround, but does not solve the error. I also tryed formatting all partitions in twrp.
Thanks
Click to expand...
Click to collapse
Are you using the latest fastboot and adb versions, this error was reportedly fixed in 2015?
http://www.androidpolice.com/2014/1...-0-factory-images-heres-how-to-get-around-it/

corkiejp said:
Are you using the latest fastboot and adb versions, this error was reportedly fixed in 2015?
http://www.androidpolice.com/2014/1...-0-factory-images-heres-how-to-get-around-it/
Click to expand...
Click to collapse
I installed fastboot and adb over apt-get fastboot adb from offical repositorys, which should be up to date. I also try installing using nexustools

Related

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!

Installed Cyanongen 11, Revert to stock and im stuck! AT&T HTC One M7 (Please Help!)

Installed Cyanongen 11, Revert to stock and im stuck! AT&T HTC One M7 (Please Help!)
Greetings,
I am in a predicament. I installed and used the cyanogenmod 11 beta installer because it looked very easy (and it was), all went well. But, I needed to revert back to stock to unlock my sim with a newly purchased sim unlock code, and I botched my phone in the process and I am stuck running in circles.
What I can do: Lock and Relock bootloader (with tampered and unlocked flags), flash a recovery.
What I can't do: everything else... ruu's fail, flashing fails, and it's a never ending circle.
I can't get S-OFF due to being stuck in the bootloader and while in recovery, I am unable to mount /cache, /system, etc. Nothing seems writeable and nothing seems to be able to flash or install. I have tried, fastboot oem rebootRUU, etc. I have tried sideloading... and everything else that I have read around the net.
Getvar:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.00.000.0
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ***
(bootloader) imei: ***
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4214mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
When locking bootloader to attempt to RUU I get this:
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (No such file or directory))
finished. total time: 1.110s
When launching RUU exe I get: ERROR [155]: UNKNOWN ERROR ( I Have tried several different RUU's)
Please help! I am without a phone and I am like a chicken with its head cut off right now...
Any help would be highly appreciated...
OCTechs said:
Greetings,
I am in a predicament. I installed and used the cyanogenmod 11 beta installer because it looked very easy (and it was), all went well. But, I needed to revert back to stock to unlock my sim with a newly purchased sim unlock code, and I botched my phone in the process and I am stuck running in circles.
What I can do: Lock and Relock bootloader (with tampered and unlocked flags), flash a recovery.
What I can't do: everything else... ruu's fail, flashing fails, and it's a never ending circle.
I can't get S-OFF due to being stuck in the bootloader and while in recovery, I am unable to mount /cache, /system, etc. Nothing seems writeable and nothing seems to be able to flash or install. I have tried, fastboot oem rebootRUU, etc. I have tried sideloading... and everything else that I have read around the net.
Getvar:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.00.000.0
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ***
(bootloader) imei: ***
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4214mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
When locking bootloader to attempt to RUU I get this:
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (No such file or directory))
finished. total time: 1.110s
When launching RUU exe I get: ERROR [155]: UNKNOWN ERROR ( I Have tried several different RUU's)
Please help! I am without a phone and I am like a chicken with its head cut off right now...
Any help would be highly appreciated...
Click to expand...
Click to collapse
Did you use this thread to downgrade your version main?
http://forum.xda-developers.com/showthread.php?t=2398717
I don't have experience with this but I wonder what recovery you should have before trying to relock bootloader. do you have custom recovery installed?
mb_guy said:
Did you use this thread to downgrade your version main?
http://forum.xda-developers.com/showthread.php?t=2398717
I don't have experience with this but I wonder what recovery you should have before trying to relock bootloader. do you have custom recovery installed?
Click to expand...
Click to collapse
Yes, I have tried. I will try again and post the results...
Results:
Code:
C:\Android\One_All-In-One_Kit_v3.1\One_All-In-One_Kit_v\Data>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
HT3********* recovery
C:\Android\One_All-In-One_Kit_v3.1\One_All-In-One_Kit_v\Data>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (No such file or directory))
finished. total time: 1.115s
C:\Android\One_All-In-One_Kit_v3.1\One_All-In-One_Kit_v\Data>fastboot oem reboot
RUU
...
(bootloader) Start Verify: 3
OKAY [ 0.051s]
finished. total time: 0.052s
C:\Android\One_All-In-One_Kit_v3.1\One_All-In-One_Kit_v\Data>fastboot flash rom.
zip
unknown partition 'rom.zip'
error: cannot determine image filename for 'rom.zip'
C:\Android\One_All-In-One_Kit_v3.1\One_All-In-One_Kit_v\Data>fastboot flash zip
rom.zip
sending 'zip' (1029872 KB)...
OKAY [ 45.155s]
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...
(bootloader) Read zipped android_info fail
FAILED (status read failed (Too many links))
finished. total time: 146.955s
C:\Android\One_All-In-One_Kit_v3.1\One_All-In-One_Kit_v\Data>fastboot flash zip
rom.zip
sending 'zip' (1029872 KB)...
At this point.. I let it sit for 15 minutes and nothing happened.
I managed to flash a firmware provided by Android Revolution 4.06.1540.2.zip, renamed it to "firmware.zip" and was able to pull that off successfully (I think "see code below") but even after that, I tried to manually flash the rom.zip and install it via the exe and still no profit. :/
Code:
< waiting for device >
sending 'zip' (43288 KB)...
OKAY [ 2.976s]
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[boot] unzipping & flushing...
(bootloader) [RUU]UZ,boot,0
(bootloader) [RUU]UZ,boot,11
(bootloader) [RUU]UZ,boot,24
(bootloader) [RUU]UZ,boot,35
(bootloader) [RUU]UZ,boot,47
(bootloader) [RUU]UZ,boot,59
(bootloader) [RUU]UZ,boot,72
(bootloader) [RUU]UZ,boot,82
(bootloader) [RUU]UZ,boot,93
(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[recovery] unzipping & flushing...
(bootloader) [RUU]UZ,recovery,0
(bootloader) [RUU]UZ,recovery,6
(bootloader) [RUU]UZ,recovery,12
(bootloader) [RUU]UZ,recovery,21
(bootloader) [RUU]UZ,recovery,29
(bootloader) [RUU]UZ,recovery,38
(bootloader) [RUU]UZ,recovery,45
(bootloader) [RUU]UZ,recovery,50
(bootloader) [RUU]UZ,recovery,67
(bootloader) [RUU]UZ,recovery,75
(bootloader) [RUU]UZ,recovery,83
(bootloader) [RUU]UZ,recovery,88
(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[rpm] unzipping & flushing...
(bootloader) [RUU]UZ,rpm,0
(bootloader) [RUU]UZ,rpm,100
(bootloader) signature checking...
(bootloader) ...... Successful
(bootloader) start image[sbl1-1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-1,0
(bootloader) [RUU]UZ,sbl1-1,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) start image[sbl1-2] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-2,0
(bootloader) [RUU]UZ,sbl1-2,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) start image[sbl1-3] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-3,0
(bootloader) [RUU]UZ,sbl1-3,100
(bootloader) signature checking...
(bootloader) ...... Successful
(bootloader) start image[sbl2] unzipping & flushing...
(bootloader) [RUU]UZ,sbl2,0
(bootloader) [RUU]UZ,sbl2,100
(bootloader) signature checking...
(bootloader) ...... Successful
(bootloader) start image[sbl3] unzipping & flushing...
(bootloader) [RUU]UZ,sbl3,0
(bootloader) [RUU]UZ,sbl3,100
(bootloader) signature checking...
(bootloader) ...... Successful
(bootloader) start image[tp] unzipping & flushing...
(bootloader) [RUU]UZ,tp,0
(bootloader) [RUU]UZ,tp,100
(bootloader) ..... Bypassed
(bootloader) start image[tz] unzipping & flushing...
(bootloader) [RUU]UZ,tz,0
(bootloader) [RUU]UZ,tz,100
(bootloader) signature checking...
(bootloader) ...... Successful
(bootloader) start image[radio] unzipping & flushing...
(bootloader) [RUU]UZ,radio,0
(bootloader) [RUU]UZ,radio,6
(bootloader) [RUU]UZ,radio,12
(bootloader) [RUU]UZ,radio,18
(bootloader) [RUU]UZ,radio,24
(bootloader) [RUU]UZ,radio,30
(bootloader) [RUU]UZ,radio,37
(bootloader) [RUU]UZ,radio,43
(bootloader) [RUU]UZ,radio,49
(bootloader) [RUU]UZ,radio,55
(bootloader) [RUU]UZ,radio,62
(bootloader) [RUU]UZ,radio,68
(bootloader) [RUU]UZ,radio,74
(bootloader) [RUU]UZ,radio,81
(bootloader) [RUU]UZ,radio,87
(bootloader) [RUU]UZ,radio,93
(bootloader) [RUU]UZ,radio,99
(bootloader) [RUU]UZ,radio,100
(bootloader) [RUU]WP,radio,0
(bootloader) [RUU]WP,radio,24
(bootloader) [RUU]WP,radio,49
(bootloader) [RUU]WP,radio,74
(bootloader) [RUU]WP,radio,99
(bootloader) [RUU]WP,radio,100
(bootloader) ...... Successful
(bootloader) start image[rcdata] unzipping & flushing...
(bootloader) [RUU]UZ,rcdata,0
(bootloader) [RUU]UZ,rcdata,42949671
(bootloader) [RUU]WP,rcdata,0
(bootloader) [RUU]WP,rcdata,42949671
(bootloader) ...... Successful
OKAY [ 27.115s]
finished. total time: 30.095s
It did however change my GetVar slightly (below):
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.1540.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4276mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.055s
OCTechs said:
I managed to flash a firmware provided by Android Revolution 4.06.1540.2.zip, renamed it to "firmware.zip" and was able to pull that off successfully (I think "see code below") but even after that, I tried to manually flash the rom.zip and install it via the exe and still no profit. :/
Code:
< waiting for device >
sending 'zip' (43288 KB)...
OKAY [ 2.976s]
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[boot] unzipping & flushing...
(bootloader) [RUU]UZ,boot,0
(bootloader) [RUU]UZ,boot,11
(bootloader) [RUU]UZ,boot,24
(bootloader) [RUU]UZ,boot,35
(bootloader) [RUU]UZ,boot,47
(bootloader) [RUU]UZ,boot,59
(bootloader) [RUU]UZ,boot,72
(bootloader) [RUU]UZ,boot,82
(bootloader) [RUU]UZ,boot,93
(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[recovery] unzipping & flushing...
(bootloader) [RUU]UZ,recovery,0
(bootloader) [RUU]UZ,recovery,6
(bootloader) [RUU]UZ,recovery,12
(bootloader) [RUU]UZ,recovery,21
(bootloader) [RUU]UZ,recovery,29
(bootloader) [RUU]UZ,recovery,38
(bootloader) [RUU]UZ,recovery,45
(bootloader) [RUU]UZ,recovery,50
(bootloader) [RUU]UZ,recovery,67
(bootloader) [RUU]UZ,recovery,75
(bootloader) [RUU]UZ,recovery,83
(bootloader) [RUU]UZ,recovery,88
(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[rpm] unzipping & flushing...
(bootloader) [RUU]UZ,rpm,0
(bootloader) [RUU]UZ,rpm,100
(bootloader) signature checking...
(bootloader) ...... Successful
(bootloader) start image[sbl1-1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-1,0
(bootloader) [RUU]UZ,sbl1-1,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) start image[sbl1-2] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-2,0
(bootloader) [RUU]UZ,sbl1-2,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) start image[sbl1-3] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-3,0
(bootloader) [RUU]UZ,sbl1-3,100
(bootloader) signature checking...
(bootloader) ...... Successful
(bootloader) start image[sbl2] unzipping & flushing...
(bootloader) [RUU]UZ,sbl2,0
(bootloader) [RUU]UZ,sbl2,100
(bootloader) signature checking...
(bootloader) ...... Successful
(bootloader) start image[sbl3] unzipping & flushing...
(bootloader) [RUU]UZ,sbl3,0
(bootloader) [RUU]UZ,sbl3,100
(bootloader) signature checking...
(bootloader) ...... Successful
(bootloader) start image[tp] unzipping & flushing...
(bootloader) [RUU]UZ,tp,0
(bootloader) [RUU]UZ,tp,100
(bootloader) ..... Bypassed
(bootloader) start image[tz] unzipping & flushing...
(bootloader) [RUU]UZ,tz,0
(bootloader) [RUU]UZ,tz,100
(bootloader) signature checking...
(bootloader) ...... Successful
(bootloader) start image[radio] unzipping & flushing...
(bootloader) [RUU]UZ,radio,0
(bootloader) [RUU]UZ,radio,6
(bootloader) [RUU]UZ,radio,12
(bootloader) [RUU]UZ,radio,18
(bootloader) [RUU]UZ,radio,24
(bootloader) [RUU]UZ,radio,30
(bootloader) [RUU]UZ,radio,37
(bootloader) [RUU]UZ,radio,43
(bootloader) [RUU]UZ,radio,49
(bootloader) [RUU]UZ,radio,55
(bootloader) [RUU]UZ,radio,62
(bootloader) [RUU]UZ,radio,68
(bootloader) [RUU]UZ,radio,74
(bootloader) [RUU]UZ,radio,81
(bootloader) [RUU]UZ,radio,87
(bootloader) [RUU]UZ,radio,93
(bootloader) [RUU]UZ,radio,99
(bootloader) [RUU]UZ,radio,100
(bootloader) [RUU]WP,radio,0
(bootloader) [RUU]WP,radio,24
(bootloader) [RUU]WP,radio,49
(bootloader) [RUU]WP,radio,74
(bootloader) [RUU]WP,radio,99
(bootloader) [RUU]WP,radio,100
(bootloader) ...... Successful
(bootloader) start image[rcdata] unzipping & flushing...
(bootloader) [RUU]UZ,rcdata,0
(bootloader) [RUU]UZ,rcdata,42949671
(bootloader) [RUU]WP,rcdata,0
(bootloader) [RUU]WP,rcdata,42949671
(bootloader) ...... Successful
OKAY [ 27.115s]
finished. total time: 30.095s
It did however change my GetVar slightly (below):
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.1540.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4276mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.055s
Click to expand...
Click to collapse
I'd suggest you post here and see if @clsA thinks his rom will help you
http://forum.xda-developers.com/showthread.php?t=2674222
not sure now that you changed your firmware version and hboot is 1.56
mb_guy said:
I'd suggest you post here and see if @clsA thinks his rom will help you
http://forum.xda-developers.com/showthread.php?t=2674222
not sure now that you changed your firmware version and hboot is 1.56
Click to expand...
Click to collapse
Yea, I'll look into it but as far as having S-ON and 1.56, life seems really bleak.
(last time i'm using cyanogenrom) I can say that much.
clsA's custom rom says it needs to be installed in recovery, which isn't much of an option for me as it would have to be sideloaded,
which thus far has gotten me no-where.
I'm at a loss...
OCTechs said:
Yea, I'll look into it but as far as having S-ON and 1.56, life seems really bleak.
(last time i'm using cyanogenrom) I can say that much.
clsA's custom rom says it needs to be installed in recovery, which isn't much of an option for me as it would have to be sideloaded,
which thus far has gotten me no-where.
I'm at a loss...
Click to expand...
Click to collapse
What is your current recovery?
Is Your device a developer edition or stock at&t us
mb_guy said:
What is your current recovery?
Click to expand...
Click to collapse
I have tried:
openrecovery-twrp-2.6.3.3-m7.img
openrecovery-twrp-2.6.3.4-m7.img
recovery-clockwork-6.0.4.3-m7att.img
recovery-clockwork-touch-6.0.4.6-m7.img
and a few stock recoveries. The last flashed recovery was twrp 2.6.3.3. I can get into recovery, but nothing seems to work... such as mounting /cache, /system, etc. I can get sideload to work (sometimes) and have tried sideloading ruu's and stock roms and tried to install for zip, but no luck, everything fails.
I went from stock to Cyanogenrom 11 beta installer and it worked fine... but it never red flagged as "developer edition" S was never turned off (which was stupid on my part for not doing that first) before trying to RUU, which got me in this mess in the first place. As for it being stock or developer edition, I am not sure... I can unlock the bootloaded with the HTCDEV provided Unlock_code.bin, just fine. When executing "fastboot oem lock" it flags as a *tampered, relocked, and security warning".
OCTechs said:
I have tried:
openrecovery-twrp-2.6.3.3-m7.img
openrecovery-twrp-2.6.3.4-m7.img
recovery-clockwork-6.0.4.3-m7att.img
recovery-clockwork-touch-6.0.4.6-m7.img
and a few stock recoveries. The last flashed recovery was twrp 2.6.3.3. I can get into recovery, but nothing seems to work... such as mounting /cache, /system, etc. I can get sideload to work (sometimes) and have tried sideloading ruu's and stock roms and tried to install for zip, but no luck, everything fails.
I went from stock to Cyanogenrom 11 beta installer and it worked fine... but it never red flagged as "developer edition" S was never turned off (which was stupid on my part for not doing that first) before trying to RUU, which got me in this mess in the first place. As for it being stock or developer edition, I am not sure... I can unlock the bootloaded with the HTCDEV provided Unlock_code.bin, just fine. When executing "fastboot oem lock" it flags as a *tampered, relocked, and security warning".
Click to expand...
Click to collapse
That is normal behavior for bootloader flags. Is your bootloader now unlocked? I noticed a couple of posts back it was relocked. twrp and other custom recoveries need it unlocked to work.
The firmware you flashed is developer edition.
mb_guy said:
That is normal behavior for bootloader flags. Is your bootloader now unlocked? I noticed a couple of posts back it was relocked. twrp and other custom recoveries need it unlocked to work.
Click to expand...
Click to collapse
Yes, I can unlock and relock the bootloader by executing commands:
#fastboot oem lock
and
#fastboot flash unlocktoken Unlock_code.bin
I can install the recoveries once it's unlocked ofcourse, but I relock it in-order to try to RUU or install any sort of stock rom.
OCTechs said:
Yes, I can unlock and relock the bootloader by executing commands:
#fastboot oem lock
and
#fastboot flash unlocktoken Unlock_code.bin
I can install the recoveries once it's unlocked ofcourse, but I relock it in-order to try to RUU or install any sort of stock rom.
Click to expand...
Click to collapse
Why not reinstall twrp and try and sideload @clsA's rom. Or otg cable if you have.
OCTechs said:
Yes, I can unlock and relock the bootloader by executing commands:
#fastboot oem lock
and
#fastboot flash unlocktoken Unlock_code.bin
I can install the recoveries once it's unlocked ofcourse, but I relock it in-order to try to RUU or install any sort of stock rom.
Click to expand...
Click to collapse
Your really in panic mode it seems and your heading for disaster if you don't stop and listen.
First you don't relock to flash anything but a RUU
if you getting error on RUU your using the wrong one
you cid and MID are both stock AT&T ... simply flash the stock AT&T RUU
From your Second post
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (status read failed (Too many links))
finished. total time: 146.955s
Click to expand...
Click to collapse
This just means you used the wrong rom.zip .. if it's a decrypted RUU/ Rom.zip you need S-off to flash it.
Why have you kept flashing different recovery's ?
are you doing all the steps to flash recovery ?
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
then you simple sideload the rom of your choice ...
Are you MD5 checking all your downloads ?
here's the last AT&T RUU it should flash on your current setup (lock the bootloader first) >> http://www.androidruu.com/getdownlo...09_10.26.1718.01L_release_356565_signed_2.exe
---------- Post added at 07:20 PM ---------- Previous post was at 07:17 PM ----------
mb_guy said:
Why not reinstall twrp and try and sideload @clsA's rom. Or otg cable if you have.
Click to expand...
Click to collapse
this would seem the simple choice .. but if he has never cleared the cache from fastboot everything will fail. He also mention trying to mount things in recovery ??? I have never once mounted anything in recovery except my usb-otg device.
clsA said:
Your really in panic mode it seems and your heading for disaster if you don't stop and listen.
First you don't relock to flash anything but a RUU
if you getting error on RUU your using the wrong one
you cid and MID are both stock AT&T ... simply flash the stock AT&T RUU
From your Second post
This just means you used the wrong rom.zip .. if it's a decrypted RUU/ Rom.zip you need S-off to flash it.
Why have you kept flashing different recovery's ?
are you doing all the steps to flash recovery ?
then you simple sideload the rom of your choice ...
Are you MD5 checking all your downloads ?
here's the last AT&T RUU it should flash on your current setup (lock the bootloader first) >> http://www.androidruu.com/getdownlo...09_10.26.1718.01L_release_356565_signed_2.exe
---------- Post added at 07:20 PM ---------- Previous post was at 07:17 PM ----------
this would seem the simple choice .. but if he has never cleared the cache from fastboot everything will fail. He also mention trying to mount things in recovery ??? I have never once mounted anything in recovery except my usb-otg device.
Click to expand...
Click to collapse
Yes, you are 100% right and can sense my tension via chat, lol. I'm freaking out, kinda. Because, I am certain that I screwed up...
Here is where I went wrong (I started fresh on my girlfriends phone which is identical to mine "she has 1.55 though"), I didn't realize Cyanogenrom's > settings > Superuser > settings > "Apps & ADB" (allow access), So when I tried to S-OFF with Rumrunner, it failed because of this... and I was unable to achieve S-OFF. I wasn't thinking and attempted to flash a RUU and everything botched. Now it seems like my phone is stuck in bootloader and a halfway working recovery menu due to the permissions and being unable to mount anything. I have been trying to use the (above RUU) file and it fails and errors out while running the exe. I have taken the "rom.zip" out of the file and attempted to flash that but since it's S-ON it fails.
You have given me hope though, on the fact that "i didn't md5 verify" the downloads and it could possibly be fixed. So that's good news, and I honestly thank you for being here for me man.
OCTechs said:
Yes, you are 100% right and can sense my tension via chat, lol. I'm freaking out, kinda. Because, I am certain that I screwed up...
Here is where I went wrong (I started fresh on my girlfriends phone which is identical to mine "she has 1.55 though"), I didn't realize Cyanogenrom's > settings > Superuser > settings > "Apps & ADB" (allow access), So when I tried to S-OFF with Rumrunner, it failed because of this... and I was unable to achieve S-OFF. I wasn't thinking and attempted to flash a RUU and everything botched. Now it seems like my phone is stuck in bootloader and a halfway working recovery menu due to the permissions and being unable to mount anything. I have been trying to use the (above RUU) file and it fails and errors out while running the exe. I have taken the "rom.zip" out of the file and attempted to flash that but since it's S-ON it fails.
You have given me hope though, on the fact that "i didn't md5 verify" the downloads and it could possibly be fixed. So that's good news, and I honestly thank you for being here for me man.
Click to expand...
Click to collapse
you can flash rom zip .. just not decrypted rom zip
what error did you get with the at&t ruu rom.zip ?
it helps if I can see you command screens for possible errors
the normal procedure to recover from CM 11 is to just flash stock recovery to your phone and do a factory reset with the stock recovery ... then flash TWRP / clear cache / factory reset in twrp and sideload a rom
clsA said:
what error did you get with the at&t ruu rom.zip ?
Click to expand...
Click to collapse
Primarily this error: FAILED (status read failed (Too many links)) when attempting to ruu the rom.zip
clsA said:
you can flash rom zip .. just not decrypted rom zip
the normal procedure to recover from CM 11 is to just flash stock recovery to your phone and do a factory reset with the stock recovery ... then flash TWRP / clear cache / factory reset in twrp and sideload a rom
Click to expand...
Click to collapse
What stock recovery we be best to flash?
And what are the commands in order to sideload the rom from TWRP?
# adb sideload rom.zip ?
Should this automatically begin the installation procedure for the rom?
Or, will I have to attempt to "install from zip" in twrp afterwards?
When I tried to clear cache in twrp, I would get a failed flag "unable to mount /cache" etc.
and it basically did nothing, and it would fail when trying to mount it in twrp.
Update:
When trying to "factory reset" in twrp 2.6.3.3 it Failed.
Code:
E: unable to mount '/cache'
OCTechs said:
What stock recovery we be best to flash?
And what are the commands in order to sideload the rom from TWRP?
# adb sideload rom.zip ?
Should this automatically begin the installation procedure for the rom?
Or, will I have to attempt to "install from zip" in twrp afterwards?
When I tried to clear cache in twrp, I would get a failed flag "unable to mount /cache" etc.
and it basically did nothing, and it would fail when trying to mount it in twrp.
Click to expand...
Click to collapse
the recovery from you current version number is the one you want
you can extract it from a decrypted rom.zip
being your on kitkat this one should work
http://d-h.st/71m
TWRP / Advanced / Sideload
From PC adb /fastboot folder
you use
adb sideload rom.zip
clsA said:
the recovery from you current version number is the one you want
you can extract it from a decrypted rom.zip
being your on kitkat this one should work
http://d-h.st/71m
TWRP / Advanced / Sideload
From PC adb /fastboot folder
you use
adb sideload rom.zip
Click to expand...
Click to collapse
After installing the stock recovery (and trying to access it) it gives me the recycling symbol for a moment, then it bootloops with the HTC logo... So I factory reset within the bootloader, cleared cache, reboot-bootloader, installed twrp 2.6.3.0, cleared cache, reboot-bootloader, and im going to attempt to install the ruu exe from the above post, if that fails, then i'll try to sideload.
Success! Im very happy now... Two days running in circles and 2am ers... I got it to work!
I thank you very much man and I owe you big time bro.
I will post my steps on what I did from start to finish so maybe down the line it will help someone else out.

Am i Hard bricked? failed boot after firmware flash.

Phone is not showing a charge LED when its plugged in to AC, when plugged into a computer it dosnt recognize as a HTC One it recognizes the usb comunication hardware but not the device specifically.
This is a copy of the command prompt:
Code:
E:\Android-SDK\sdk\platform-tools>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.059s]
finished. total time: 0.060s
E:\Android-SDK\sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.048s]
finished. total time: 0.049s
E:\Android-SDK\sdk\platform-tools>fastboot flash zip firmware.zip
target reported max download size of 1526722560 bytes
sending 'zip' (44102 KB)...
OKAY [ 2.815s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 4.390s
E:\Android-SDK\sdk\platform-tools>fastboot flash zip firmware.zip
target reported max download size of 1514139648 bytes
sending 'zip' (44102 KB)...
OKAY [ 2.821s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[boot] unzipping & flushing...
(bootloader) [RUU]UZ,boot,0
(bootloader) [RUU]UZ,boot,11
(bootloader) [RUU]UZ,boot,24
(bootloader) [RUU]UZ,boot,35
(bootloader) [RUU]UZ,boot,46
(bootloader) [RUU]UZ,boot,56
(bootloader) [RUU]UZ,boot,66
(bootloader) [RUU]UZ,boot,79
(bootloader) [RUU]UZ,boot,91
(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[recovery] unzipping & flushing...
(bootloader) [RUU]UZ,recovery,0
(bootloader) [RUU]UZ,recovery,6
(bootloader) [RUU]UZ,recovery,12
(bootloader) [RUU]UZ,recovery,21
(bootloader) [RUU]UZ,recovery,30
(bootloader) [RUU]UZ,recovery,38
(bootloader) [RUU]UZ,recovery,45
(bootloader) [RUU]UZ,recovery,68
(bootloader) [RUU]UZ,recovery,73
(bootloader) [RUU]UZ,recovery,78
(bootloader) [RUU]UZ,recovery,86
(bootloader) [RUU]UZ,recovery,95
(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[rpm] unzipping & flushing...
(bootloader) [RUU]UZ,rpm,0
(bootloader) [RUU]UZ,rpm,100
(bootloader) [RUU]WP,rpm,0
(bootloader) [RUU]WP,rpm,100
(bootloader) ...... Successful
(bootloader) start image[sbl1-1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-1,0
(bootloader) [RUU]UZ,sbl1-1,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) start image[sbl1-2] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-2,0
(bootloader) [RUU]UZ,sbl1-2,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) start image[sbl1-3] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-3,0
(bootloader) [RUU]UZ,sbl1-3,100
(bootloader) signature checking...
(bootloader) [RUU]WP,sbl1-3,0
(bootloader) [RUU]WP,sbl1-3,100
(bootloader) ...... Successful
(bootloader) start image[sp1] unzipping & flushing...
(bootloader) [RUU]UZ,sp1,0
(bootloader) [RUU]UZ,sp1,99
(bootloader) [RUU]UZ,sp1,100
(bootloader) [RUU]WP,sp1,0
(bootloader) [RUU]WP,sp1,100
(bootloader) ...... Successful
(bootloader) start image[radio] unzipping & flushing...
(bootloader) [RUU]UZ,radio,0
(bootloader) [RUU]UZ,radio,6
(bootloader) [RUU]UZ,radio,11
(bootloader) [RUU]UZ,radio,17
(bootloader) [RUU]UZ,radio,23
(bootloader) [RUU]UZ,radio,28
(bootloader) [RUU]UZ,radio,34
(bootloader) [RUU]UZ,radio,40
(bootloader) [RUU]UZ,radio,46
(bootloader) [RUU]UZ,radio,52
(bootloader) [RUU]UZ,radio,59
(bootloader) [RUU]UZ,radio,69
(bootloader) [RUU]UZ,radio,75
(bootloader) [RUU]UZ,radio,81
(bootloader) [RUU]UZ,radio,87
(bootloader) [RUU]UZ,radio,92
(bootloader) [RUU]UZ,radio,99
(bootloader) [RUU]UZ,radio,100
(bootloader) [RUU]WP,radio,0
(bootloader) [RUU]WP,radio,23
(bootloader) [RUU]WP,radio,46
(bootloader) [RUU]WP,radio,69
(bootloader) [RUU]WP,radio,92
(bootloader) [RUU]WP,radio,100
(bootloader) ...... Successful
(bootloader) start image[rcdata] unzipping & flushing...
(bootloader) [RUU]UZ,rcdata,0
(bootloader) [RUU]WP,rcdata,0
(bootloader) ...... Successful
OKAY [ 18.165s]
finished. total time: 20.990s
E:\Android-SDK\sdk\platform-tools>fastboot flash recovery Recovery.img
target reported max download size of 1514139648 bytes
sending 'recovery' (11864 KB)...
OKAY [ 1.696s]
writing 'recovery'...
OKAY [ 0.849s]
finished. total time: 2.547s
E:\Android-SDK\sdk\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.051s
Got the firmware zip from Here.
If anyone has any input or recommendations on what to try to get any response from the device. itd be much apriciated.
And yes i know this isnt a whole lot of information to go on. provided as much as i could. :<
Sieze said:
And yes i know this isnt a whole lot of information to go on. provided as much as i could. :<
Click to expand...
Click to collapse
Does the phone boot into the OS/Android?
Can you boot into recovery?
Why did you flash that firmware what were you hoping to accomplish?
Have you tried different cables, charger, ports or computer?
Could you post a fastboot getvar all except remove the imei and serialno you don't want those getting out to the Net?
---------- Post added at 11:31 AM ---------- Previous post was at 11:28 AM ----------
Sieze said:
Phone is not showing a charge LED when its plugged in to AC, when plugged into a computer it dosnt recognize as a HTC One it recognizes the usb comunication hardware but not the device specifically.
This is a copy of the command prompt:
Code:
E:\Android-SDK\sdk\platform-tools>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.059s]
finished. total time: 0.060s
E:\Android-SDK\sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.048s]
finished. total time: 0.049s
E:\Android-SDK\sdk\platform-tools>fastboot flash zip firmware.zip
target reported max download size of 1526722560 bytes
sending 'zip' (44102 KB)...
OKAY [ 2.815s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 4.390s
E:\Android-SDK\sdk\platform-tools>fastboot flash zip firmware.zip
target reported max download size of 1514139648 bytes
sending 'zip' (44102 KB)...
OKAY [ 2.821s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[boot] unzipping & flushing...
(bootloader) [RUU]UZ,boot,0
(bootloader) [RUU]UZ,boot,11
(bootloader) [RUU]UZ,boot,24
(bootloader) [RUU]UZ,boot,35
(bootloader) [RUU]UZ,boot,46
(bootloader) [RUU]UZ,boot,56
(bootloader) [RUU]UZ,boot,66
(bootloader) [RUU]UZ,boot,79
(bootloader) [RUU]UZ,boot,91
(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[recovery] unzipping & flushing...
(bootloader) [RUU]UZ,recovery,0
(bootloader) [RUU]UZ,recovery,6
(bootloader) [RUU]UZ,recovery,12
(bootloader) [RUU]UZ,recovery,21
(bootloader) [RUU]UZ,recovery,30
(bootloader) [RUU]UZ,recovery,38
(bootloader) [RUU]UZ,recovery,45
(bootloader) [RUU]UZ,recovery,68
(bootloader) [RUU]UZ,recovery,73
(bootloader) [RUU]UZ,recovery,78
(bootloader) [RUU]UZ,recovery,86
(bootloader) [RUU]UZ,recovery,95
(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[rpm] unzipping & flushing...
(bootloader) [RUU]UZ,rpm,0
(bootloader) [RUU]UZ,rpm,100
(bootloader) [RUU]WP,rpm,0
(bootloader) [RUU]WP,rpm,100
(bootloader) ...... Successful
(bootloader) start image[sbl1-1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-1,0
(bootloader) [RUU]UZ,sbl1-1,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) start image[sbl1-2] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-2,0
(bootloader) [RUU]UZ,sbl1-2,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) start image[sbl1-3] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-3,0
(bootloader) [RUU]UZ,sbl1-3,100
(bootloader) signature checking...
(bootloader) [RUU]WP,sbl1-3,0
(bootloader) [RUU]WP,sbl1-3,100
(bootloader) ...... Successful
(bootloader) start image[sp1] unzipping & flushing...
(bootloader) [RUU]UZ,sp1,0
(bootloader) [RUU]UZ,sp1,99
(bootloader) [RUU]UZ,sp1,100
(bootloader) [RUU]WP,sp1,0
(bootloader) [RUU]WP,sp1,100
(bootloader) ...... Successful
(bootloader) start image[radio] unzipping & flushing...
(bootloader) [RUU]UZ,radio,0
(bootloader) [RUU]UZ,radio,6
(bootloader) [RUU]UZ,radio,11
(bootloader) [RUU]UZ,radio,17
(bootloader) [RUU]UZ,radio,23
(bootloader) [RUU]UZ,radio,28
(bootloader) [RUU]UZ,radio,34
(bootloader) [RUU]UZ,radio,40
(bootloader) [RUU]UZ,radio,46
(bootloader) [RUU]UZ,radio,52
(bootloader) [RUU]UZ,radio,59
(bootloader) [RUU]UZ,radio,69
(bootloader) [RUU]UZ,radio,75
(bootloader) [RUU]UZ,radio,81
(bootloader) [RUU]UZ,radio,87
(bootloader) [RUU]UZ,radio,92
(bootloader) [RUU]UZ,radio,99
(bootloader) [RUU]UZ,radio,100
(bootloader) [RUU]WP,radio,0
(bootloader) [RUU]WP,radio,23
(bootloader) [RUU]WP,radio,46
(bootloader) [RUU]WP,radio,69
(bootloader) [RUU]WP,radio,92
(bootloader) [RUU]WP,radio,100
(bootloader) ...... Successful
(bootloader) start image[rcdata] unzipping & flushing...
(bootloader) [RUU]UZ,rcdata,0
(bootloader) [RUU]WP,rcdata,0
(bootloader) ...... Successful
OKAY [ 18.165s]
finished. total time: 20.990s
E:\Android-SDK\sdk\platform-tools>fastboot flash recovery Recovery.img
target reported max download size of 1514139648 bytes
sending 'recovery' (11864 KB)...
OKAY [ 1.696s]
writing 'recovery'...
OKAY [ 0.849s]
finished. total time: 2.547s
E:\Android-SDK\sdk\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.051s
Got the firmware zip from Here.
If anyone has any input or recommendations on what to try to get any response from the device. itd be much apriciated.
Click to expand...
Click to collapse
The firmware flash correctly but when you flashed the recovery you should have "fastboot erase cache" before you booted the phone.
Phone was entirely un responsive it didnt boot at all zero response or life signs. used this though http://forum.xda-developers.com/showthread.php?t=2770684 and it brought it back from the dead. il still pull a log of a few things and especially a getvar all beforei touch anything on it

[Q] Trying to flash stock R and Q images problem when flashing image

I'm having this problem with my nexus 9
target reported max download size of 518205818 bytes
sending 'bootloader' (2970 KB)...
OKAY [ 0.213s]
writing 'bootloader'...
(bootloader) Device State : Unlocked
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[bct] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[mts_preboot_prod] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[mts_prod] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[hboot] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[nvtboot] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[nvtbootwb0] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[tos] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[sp1] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[gp1] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[pt] unzipping & flashing...
(bootloader) ...... Successful
OKAY [ 5.277s]
finished. total time: 5.490s
rebooting into bootloader...
OKAY [ 0.021s]
finished. total time: 0.022s
< waiting for device >
target reported max download size of 518205818 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1813984020 bytes
error: update package missing system.img
Press any key to exit...
I've tried factory images from Q and R but both have the same behaviour.
Do you guys have any suggestions?
Thanks!
extracting all .img files from the zip google provider into the platform-tools and running the following command resolved the issue
adb reboot bootloader
fastboot flash systemsystem.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash vendor vendor.img
fastboot -w
fastboot reboot

Infinite Loop reboot Nexus 9

Hi everyone, I may just lost my nexus 9... :/
I was trying to install the M developer preview on my nexus 9, so I enabled oem unlock from developer settings, then 'adb reboot bootloader', then 'adb fastboot unlock' and after restart:
Code:
Danieles-MacBook-Pro-2:volantis-MPZ44Q myusername$ ./flash-all.sh
target reported max download size of 518205818 bytes
sending 'bootloader' (3085 KB)...
OKAY [ 0.265s]
writing 'bootloader'...
(bootloader) Device State : Unlocked
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[bct] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[mts_preboot_prod] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[mts_prod] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[hboot] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[nvtboot] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[nvtbootwb0] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[tos] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[sp1] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[gp1] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[pt] unzipping & flashing...
(bootloader) ...... Successful
OKAY [ 5.283s]
finished. total time: 5.548s
rebooting into bootloader...
OKAY [ 0.022s]
finished. total time: 0.022s
target reported max download size of 518205818 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
fastboot(68411,0xa0ad51d4) malloc: *** mach_vm_map(size=2132963328) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
failed to allocate 2130828644 bytes
error: update package missing system.img
I tried to reboot the device and now I can see Google logo, a bit of the startup animation and then it restarts itself again and again...
I cannot even go to the recovery anymore, I'm trying to press and hold Power plus vol up and down but nothing.
Is there a way to fix it? I'm not sure what's happened :/
Thanks,
Daniele
http://www.androidpolice.com/2014/1...-0-factory-images-heres-how-to-get-around-it/
This works for M
Yes thank you!
Sent from my D5803 using XDA Free mobile app

Categories

Resources