I have been having call issues with my phone and need to send it back to VZW.
This phone was Rooted, with S-Off and Unlocked in the Bootloader, I started researching today how to put it back to stock and in the process I have simply soft bricked my phone and have tried and exhausted everything I could find.
When I reboot into RUU and try to flash the Decrypted file for my 1.10.65.10 it fails:
C:\fastboot>fastboot flash zip M7RUU.zip
sending 'zip' (1178304 KB)...
OKAY [ 60.146s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 196.594s
I am not able to go into or load any recovery files either, I am only able to do fastboot commands and no adb commands.
I really have searched all over xda forums and have not found the answer
My HTC currently will not boot and is able to fastboot only.
It is Displaying:
TAMPERED
RELOCKED
Security Warning
M7_WLV PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-1.12.42.1104
OpenDSP-v31.120.274.0617
OS-1.10.605.10
eMMC-boot 2048MB
Sep 9 2013, 11:53:38.0
FASTBOOT USB
ETC..
Here are the notes from fastboot get var
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 1.12.42.1104
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.10.605.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA37YS901096
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4011mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-57eb7f637d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Please if you have any advice or assistance, I woudl love to hear it I am on Win 7 32bit machine and is the same machine and cable I have used to do all the previous rooting and set it to s-off in the first place.
Thank you
Another error I receive:
C:\fastboot>fastboot oem unlock
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.001s]
finished. total time: 0.001s
You must run an encrypted version of the RUU since you are back to S-ON. If you stayed at S-OFF you can run the decrypted RUU. Try to S-OFF again and then PM me and I will send you a link to help you out. If you can't. Run the following RUU. Link below.
http://bit.ly/vzwone-15
Flyhalf205 said:
You must run an encrypted version of the RUU since you are back to S-ON. If you stayed at S-OFF you can run the decrypted RUU. Try to S-OFF again and then PM me and I will send you a link to help you out. If you can't. Run the following RUU. Link below.
http://bit.ly/vzwone-15
Click to expand...
Click to collapse
Not to mention he's not even in ruu mode.
Sent from my HTC6600LVW using Tapatalk
dottat said:
Not to mention he's not even in ruu mode.
Sent from my HTC6600LVW using Tapatalk
Click to expand...
Click to collapse
Very tru dottat..
@tomwatez make sure when you hook to usb. In the command
fastboot oem rebootRUU
fastboot flash zip ruu.zip <---- You'll most likely have to do this command twice with the signed encrypted RUU
Flyhalf205 said:
Very tru dottat..
@tomwatez make sure when you hook to usb. In the command
fastboot oem rebootRUU
fastboot flash zip ruu.zip <---- You'll most likely have to do this command twice
Click to expand...
Click to collapse
And yes....if s-on make sure the ruu isn't older than software running on the phone.
Sent from my HTC6600LVW using Tapatalk
Flyhalf205 said:
You must run an encrypted version of the RUU since you are back to S-ON. If you stayed at S-OFF you can run the decrypted RUU. Try to S-OFF again and then PM me and I will send you a link to help you out. If you can't. Run the following RUU. Link below.
http://bit.ly/vzwone-15
Click to expand...
Click to collapse
Thank you I'll give it a shot!
Flyhalf205 said:
You must run an encrypted version of the RUU since you are back to S-ON. If you stayed at S-OFF you can run the decrypted RUU. Try to S-OFF again and then PM me and I will send you a link to help you out. If you can't. Run the following RUU. Link below.
http://bit.ly/vzwone-15
Click to expand...
Click to collapse
Flyhalf205 said:
Very tru dottat..
@tomwatez make sure when you hook to usb. In the command
fastboot oem rebootRUU
fastboot flash zip ruu.zip <---- You'll most likely have to do this command twice with the signed encrypted RUU
Click to expand...
Click to collapse
I actually have been using those commands and have been running it in RUU mode all day, been at it for about 8 hrs trying all sorts of different things.
The thing different now is that I have a link to a signed ru instead... trying it now, its been running for about 10 mins and is at this point:
C:\fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.043s]
finished. total time: 0.043s
C:\fastboot>fastboot flash zip RUU.zip
sending 'zip' (1178525 KB)...
OKAY [ 57.957s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
tomwatez said:
i actually have been using those commands and have been running it in ruu mode all day, been at it for about 8 hrs trying all sorts of different things.
The thing different now is that i have a link to a signed ru instead... Trying it now, its been running for about 10 mins and is at this point:
C:\fastboot>fastboot oem rebootruu
...
(bootloader) start verify: 3
okay [ 0.043s]
finished. Total time: 0.043s
c:\fastboot>fastboot flash zip ruu.zip
sending 'zip' (1178525 kb)...
Okay [ 57.957s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
Click to expand...
Click to collapse
blah blah blah>> nothing to read here
Flyhalf205 said:
Very tru dottat..
@tomwatez make sure when you hook to usb. In the command
fastboot oem rebootRUU
fastboot flash zip ruu.zip <---- You'll most likely have to do this command twice with the signed encrypted RUU
Click to expand...
Click to collapse
Is thsi why you said to run twice?
C:\fastboot>fastboot flash zip RUU.zip
sending 'zip' (1178525 KB)...
OKAY [ 57.957s]
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) 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[hboot] flushing...
(bootloader) signature checking...
(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: 1031.357s
tomwatez said:
Is thsi why you said to run twice?
C:\fastboot>fastboot flash zip RUU.zip
sending 'zip' (1178525 KB)...
OKAY [ 57.957s]
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) 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[hboot] flushing...
(bootloader) signature checking...
(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: 1031.357s
Click to expand...
Click to collapse
Yes. Run it again. and It should run fine.
looks successful.. Now before I do anything else.. end goal is stock but want to wait after I get my replacement tomorrow to see what is on it.
what is the next step from here:
(bootloader) [RUU]UZ,radio,94
(bootloader) [RUU]UZ,radio,99
(bootloader) [RUU]UZ,radio,100
(bootloader) [RUU]WP,radio,0
(bootloader) [RUU]WP,radio,34
(bootloader) [RUU]WP,radio,68
(bootloader) [RUU]WP,radio,100
(bootloader) ...... Successful
(bootloader) start image[rcdata] unzipping & flushing...
(bootloader) [RUU]UZ,rcdata,0
(bootloader) [RUU]UZ,rcdata,100
(bootloader) [RUU]WP,rcdata,0
(bootloader) [RUU]WP,rcdata,100
(bootloader) ...... Successful
OKAY [410.428s]
finished. total time: 468.138s
tomwatez said:
looks successful.. Now before I do anything else.. end goal is stock but want to wait after I get my replacement tomorrow to see what is on it.
what is the next step from here:
(bootloader) [RUU]UZ,radio,94
(bootloader) [RUU]UZ,radio,99
(bootloader) [RUU]UZ,radio,100
(bootloader) [RUU]WP,radio,0
(bootloader) [RUU]WP,radio,34
(bootloader) [RUU]WP,radio,68
(bootloader) [RUU]WP,radio,100
(bootloader) ...... Successful
(bootloader) start image[rcdata] unzipping & flushing...
(bootloader) [RUU]UZ,rcdata,0
(bootloader) [RUU]UZ,rcdata,100
(bootloader) [RUU]WP,rcdata,0
(bootloader) [RUU]WP,rcdata,100
(bootloader) ...... Successful
OKAY [410.428s]
finished. total time: 468.138s
Click to expand...
Click to collapse
Your all good. So why are you getting it replaced after we just got it to stock?
Been having lots of issues with breaking up and dropped calls, not to mention the speaker is crackling..Verizon exhausted the troubleshooting and said we will send you a replacement. I wanted to try putting it back to stock to see if those things were still happening... So now that it is stock and I had s-off previously should I be good to go to redo s-off and rom, root it if I chose to keep it and it works better
tomwatez said:
Been having lots of issues with breaking up and dropped calls, not to mention the speaker is crackling..Verizon exhausted the troubleshooting and said we will send you a replacement. I wanted to try putting it back to stock to see if those things were still happening... So now that it is stock and I had s-off previously should I be good to go to redo s-off and rom, root it if I chose to keep it and it works better
Click to expand...
Click to collapse
Hope it all works out...I fear the supply of pre-4.3 phones is dwindling
Sent from my Nexus 7 using Tapatalk
dottat said:
Hope it all works out...I fear the supply of pre-4.3 phones is dwindling
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
The directions and link that was listed worked perfectly and I'm back up and running.
Thank you All! Lets see if the one I get is pre 4.3 or not.. I may just send it back if mine is working better.
tomwatez said:
The directions and link that was listed worked perfectly and I'm back up and running.
Thank you All! Lets see if the one I get is pre 4.3 or not.. I may just send it back if mine is working better.
Click to expand...
Click to collapse
Got the replacement today, sounds and looks great.. Best of all it was on 4.2.2 and 1.10.605.10, s-on, however the hboot is on 1.54.
I'm trying s-off right now and it seems to be going good so far, will report if it doesn't unlock...
Thanks again for your great support!
Sorry the pros are helping
Sent from my HTC6500LVW using XDA Premium HD app
C:\adb>fastboot flash zip RUU.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1178525 KB)...
OKAY [ 53.441s]
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: 186.403s
I'm using the instructions from this thread: http://forum.xda-developers.com/showthread.php?p=51514093
what should I do? please help me
You can S-off an m7vzw on 4.4.2 now. Use WeakSauce.apk for temp root, then firewater to s-off.
http://forum.xda-developers.com/showthread.php?t=2699089
Related
Long story short, my friend said he would throw Viperone on my phone. He couldnt. Returned phone to me in the following condition.
*** RELOCKED ***
M7_WLV PVT SHIP S-OFF RH
CID-VZW__001
HBOOT-1.54.0000
OpenDSP-v31.120.274.0617
OS-1.10.605.10
eMMC-boot 2048
Sep 9 2013,11:53:38.174
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 1.12.42.0906
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.10.605.10
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA39DS901760
(bootloader) imei: 990004282284201
(bootloader) meid: 99000428228420
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4292mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-57eb7f637d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
When trying to use Fastboot to do anything it says "FAILED (remote: not allowed)
When trying to boot into the recovery it just goes to the HTC screen and says some crap about HTC Property and shouldnt be distruibuted. And resets over and over.
I can get into the bootloader and thats about it. But anything I do with Fastboot to try to push anything it says not allowed.
Should I burn my friends house down , beat his ass ? Or is this fixable.
morpheusxeno said:
Long story short, my friend said he would throw Viperone on my phone. He couldnt. Returned phone to me in the following condition.
When trying to use Fastboot to do anything it says "FAILED (remote: not allowed)
When trying to boot into the recovery it just goes to the HTC screen and says some crap about HTC Property and shouldnt be distruibuted. And resets over and over.
I can get into the bootloader and thats about it. But anything I do with Fastboot to try to push anything it says not allowed.
Should I burn my friends house down , beat his ass ? Or is this fixable.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=46183050
Chilidog said:
http://forum.xda-developers.com/showthread.php?p=46183050
Click to expand...
Click to collapse
ADB doesnt work while the phone is in fastboot. The phone has to have a kernel running.
>.>
I need a way to bypass the failed (remote: not allowed) so that I can fix my device. Is there any possible way?
Unlock the bootloader so you can flash a custom recovery. Its locked so it won't allow you to flash one
Sent from my Nexus 7 using Tapatalk 4
dottat said:
Unlock the bootloader so you can flash a custom recovery. Its locked so it won't allow you to flash one
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
How can I unlock the bootloader if anything I try to send is rejected?...
If you could be more descriptive I would appreciate it..
Tried to use fastboot oem rebootRUU
C:\Users\Taz\Desktop\rco>fastboot flash zip rom.zip
sending 'zip' (882369 KB)...
OKAY [ 33.598s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 48.833s
morpheusxeno said:
How can I unlock the bootloader if anything I try to send is rejected?...
If you could be more descriptive I would appreciate it..
Tried to use fastboot oem rebootRUU
C:\Users\Taz\Desktop\rco>fastboot flash zip rom.zip
sending 'zip' (882369 KB)...
OKAY [ 33.598s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 48.833s
Click to expand...
Click to collapse
Read the ruu fourm someone had that problem I think
morpheusxeno said:
How can I unlock the bootloader if anything I try to send is rejected?...
If you could be more descriptive I would appreciate it..
Tried to use fastboot oem rebootRUU
C:\Users\Taz\Desktop\rco>fastboot flash zip rom.zip
sending 'zip' (882369 KB)...
OKAY [ 33.598s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 48.833s
Click to expand...
Click to collapse
What zip did you try using?
If its the RUU, change the Android Info version in the text file to .10 and try again.
It may still fail, worth a shot.
morpheusxeno said:
How can I unlock the bootloader if anything I try to send is rejected?...
If you could be more descriptive I would appreciate it..
Tried to use fastboot oem rebootRUU
C:\Users\Taz\Desktop\rco>fastboot flash zip rom.zip
sending 'zip' (882369 KB)...
OKAY [ 33.598s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 48.833s
Click to expand...
Click to collapse
in RUU thread, it says to make sure the zip's file name is Rom.zip, not RoM.zip, rom.zip, Rom.zip.zip, or something like that.
don't know if that'll solve your issue but hey it's a quick try.
wiredout46 said:
in RUU thread, it says to make sure the zip's file name is Rom.zip, not RoM.zip, rom.zip, Rom.zip.zip, or something like that.
don't know if that'll solve your issue but hey it's a quick try.
Click to expand...
Click to collapse
Zip was named Rom.zip not rom.zip
Forgot case sensitive unix/linux /facepalm
I would delete ur imei on here
Sent from my HTC One VZW using Tapatalk 4
morpheusxeno said:
Zip was named Rom.zip not rom.zip
Forgot case sensitive unix/linux /facepalm
Click to expand...
Click to collapse
so... did you solve your issue yet?
I used firewater to unlock and s-off my HTC One with 4.3. Everything went well and I installrd TWRP. I did a back up and when I restarted the phone it said No OS. After trying so many things I ended up, only able to boot into bootloader with no recovery or os and anything I try to send to the phone fails.
C:\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: XA SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN073****
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4256mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-3c88cdd7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.110s
This is what I get when I try to flash a new recovery.
C:\platform-tools>fastboot flash recovery openrecovery-twrp-2.6.3.3-m7vzw.img
target reported max download size of 1526722560 bytes
sending 'recovery' (9744 KB)...
OKAY [ 1.166s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.326s
Thanks for any in put guys.
Make sure you open command prompt in administrator mode. Try renaming your recovery to recovery.img. And make sure you can see file extensions on your computer. If file extensions are hidden and you add that img at the end,it could really be recovery.img.img.
joeymagnus1 said:
Make sure you open command prompt in administrator mode. Try renaming your recovery to recovery.img. And make sure you can see file extensions on your computer. If file extensions are hidden and you add that img at the end,it could really be recovery.img.img.
Click to expand...
Click to collapse
I tried this and it failed....
C:\platform-tools>fastboot oem rebootRUU
...
(bootloader) [ERR] Cmd18 polling status timed out, MCI_STATUS: 0x4C2000
(bootloader) [ERR] sdcc_command: sdcc_poll_status error, rc: 2
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) CMD18: cmd failed
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(876): error 2
(bootloader) Start Verify: 0
(bootloader) [ERR] Cmd25 polling status timed out, MCI_STATUS: 0x4C0000
(bootloader) [ERR] sdcc_command: sdcc_poll_status error, rc: 2
OKAY [ 0.057s]
finished. total time: 0.057s
C:\platform-tools>fastboot flash zip Twrp_2.6.3.4_RUU_Mode.zip
target reported max download size of 1526722560 bytes
sending 'zip' (9278 KB)...
OKAY [ 1.150s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 1.185s
C:\platform-tools>
I got the same errors running as adm... Should I try this? Someone had a similar problem but he was S-On.
Here you guys go. Santod added it to his thread. http://goo.gl/JEkyCk 2.10.605.1 RUU Signed
joeyz400 said:
I used firewater to unlock and s-off my HTC One with 4.3. Everything went well and I installrd TWRP. I did a back up and when I restarted the phone it said No OS. After trying so many things I ended up, only able to boot into bootloader with no recovery or os and anything I try to send to the phone fails.
C:\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: XA SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN073****
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4256mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-3c88cdd7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.110s
This is what I get when I try to flash a new recovery.
C:\platform-tools>fastboot flash recovery openrecovery-twrp-2.6.3.3-m7vzw.img
target reported max download size of 1526722560 bytes
sending 'recovery' (9744 KB)...
OKAY [ 1.166s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.326s
Thanks for any in put guys.
Click to expand...
Click to collapse
This line: (bootloader) product: m7_wlv indicates that you flashed a Sprint bootloader to the phone. It should say m7_vzw. The Sprint model has different mount points, so that could explain the error.
NotATreoFan said:
This line: (bootloader) product: m7_wlv indicates that you flashed a Sprint bootloader to the phone. It should say m7_vzw. The Sprint model has different mount points, so that could explain the error.
Click to expand...
Click to collapse
I must have messed something up when I was still able to get into recovery, I wasn't able to flash anything. I kept getting E: drive errors so I flashed a stock recovery.... that is when I lost Twrp and only bootloops into boot loader with no OS.
I just tried flashing openrecovery-twrp-2.6.3.3-m7.img and got the same errors....
C:\platform-tools>fastboot flash zip Twrp_2.6.3.4_RUU_Mode.zip
target reported max download size of 1526722560 bytes
sending 'zip' (9278 KB)...
OKAY [ 1.152s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 1.190s
C:\platform-tools>fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
target reported max download size of 1526722560 bytes
sending 'recovery' (9184 KB)...
OKAY [ 4.911s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 5.090s
C:\platform-tools>
joeyz400 said:
I must have messed something up when I was still able to get into recovery, I wasn't able to flash anything. I kept getting E: drive errors so I flashed a stock recovery.... that is when I lost Twrp and only bootloops into boot loader with no OS.
I just tried flashing openrecovery-twrp-2.6.3.3-m7.img and got the same errors....
C:\platform-tools>fastboot flash zip Twrp_2.6.3.4_RUU_Mode.zip
target reported max download size of 1526722560 bytes
sending 'zip' (9278 KB)...
OKAY [ 1.152s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 1.190s
C:\platform-tools>fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
target reported max download size of 1526722560 bytes
sending 'recovery' (9184 KB)...
OKAY [ 4.911s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 5.090s
C:\platform-tools>
Click to expand...
Click to collapse
If you have stock recovery on the phone now, try using ADB Sideload to push the stock, rooted 4.4.2 ROM from here: http://forum.xda-developers.com/showthread.php?t=2485319
If that works for you, then try pushing TWRP 2.6.3.4.
Will that relock my bootloader and make it S-On? I was on stock 4.3 before I started everything.
NotATreoFan said:
If you have stock recovery on the phone now, try using ADB Sideload to push the stock, rooted 4.4.2 ROM from here: http://forum.xda-developers.com/showthread.php?t=2485319
If that works for you, then try pushing TWRP 2.6.3.4.
Click to expand...
Click to collapse
joeyz400 said:
Will that relock my bootloader and make it S-On? I was on stock 4.3 before I started everything.
Click to expand...
Click to collapse
No. But you will also need to flash the latest firmware package from that thread. It also does not affect S-Off, so don't worry.
Seems my bootloader is corrupt... Is there anyway to wipe it clean to start over?
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>cd C:\platform-tools
C:\platform-tools>fastboot oem rebootRUU
...
(bootloader) [ERR] Cmd18 polling status timed out, MCI_STATUS: 0x4C2000
(bootloader) [ERR] sdcc_command: sdcc_poll_status error, rc: 2
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) CMD18: cmd failed
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(876): error 2
(bootloader) Start Verify: 0
(bootloader) [ERR] Cmd25 polling status timed out, MCI_STATUS: 0x4C0000
(bootloader) [ERR] sdcc_command: sdcc_poll_status error, rc: 2
OKAY [ 0.059s]
finished. total time: 0.059s
C:\platform-tools>
I tried flashing the stock recovery and got this error:
C:\platform-tools>fastboot flash recovery 1.10.605.10_recovery.img
target reported max download size of 1526722560 bytes
sending 'recovery' (16383 KB)...
OKAY [ 1.793s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.953s
C:\platform-tools>
I just tried this...... FAIL
C:\platform-tools>fastboot flash RUU RUU_M7_WL_JB43_SENSE50_VZW_MR_VERIZON_WWE_2
.10.605.1_Radio_1.12.41.1112_2_NV_VZW_3.71_002_release_341019_signed_2.zip
target reported max download size of 1526722560 bytes
sending 'RUU' (1232586 KB)...
OKAY [ 41.968s]
writing 'RUU'...
FAILED (remote: not allowed)
finished. total time: 42.006s
C:\platform-tools>
joeyz400 said:
I just tried this...... FAIL
C:\platform-tools>fastboot flash RUU RUU_M7_WL_JB43_SENSE50_VZW_MR_VERIZON_WWE_2
.10.605.1_Radio_1.12.41.1112_2_NV_VZW_3.71_002_release_341019_signed_2.zip
target reported max download size of 1526722560 bytes
sending 'RUU' (1232586 KB)...
OKAY [ 41.968s]
writing 'RUU'...
FAILED (remote: not allowed)
finished. total time: 42.006s
C:\platform-tools>
Click to expand...
Click to collapse
Is this the encrypted RUU? If so, you may need the decrypted one. Or vice versa.
Sent from my HTC6500LVW using Tapatalk
This is my latest attempt... FAIL***** Am I doing something wrong?
C:\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: XA SHIP S-OFF
(bootloader) serialno: 12345678****
(bootloader) imei: 99000428262****
(bootloader) meid: 9900042826****
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN073****
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4074mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-3c88cdd7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.113s
C:\platform-tools>fastboot flash recovery PN07IMG_M7_WL_JB_50_VZW_1.10.605.10_DE
CRYPT.zip
target reported max download size of 1526722560 bytes
sending 'recovery' (1178304 KB)...
OKAY [ 40.982s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 41.018s
C:\platform-tools>fastboot flash RUU PN07IMG_M7_WL_JB_50_VZW_1.10.605.10_DECRYPT
.zip
target reported max download size of 1526722560 bytes
sending 'RUU' (1178304 KB)...
OKAY [107.432s]
writing 'RUU'...
FAILED (remote: not allowed)
finished. total time: 107.468s
C:\platform-tools>
you are doing more than I can do right now. how did you get the sdk bundle to work?
I had it working before things went wrong. If you are on windows 8 people have problems so search that if that is your OS. I'm running Windows 7 on my PC. I had Unlocked S-Off and rooted with TWRP 2.6.3.3 installed. Everything was working till I did my first back up. When I restarted my phone it said there was no OS installed and the bootloops started but I still had recovery. But I couldn't restore my backup. Now I can only boot into bootloader with no OS or Recovery. Search how to set up SDK and ADB for your OS and take it from there. I am stumped because I cant run any RUU's, all I get are errors. Good luck.
I don't have my SIM card installed. Does that matter?
joeyz400 said:
I don't have my SIM card installed. Does that matter?[/QUOTE
]that shouldn't matter
Click to expand...
Click to collapse
If I fried something can the part be bought and replaced?
Jamesdbritt said:
joeyz400 said:
I don't have my SIM card installed. Does that matter?[/QUOTE
]that shouldn't matter
Click to expand...
Click to collapse
Click to expand...
Click to collapse
I gave up... I'm sending the phone to MobileTechVideos.COM they say they can repair it for $60. Thanks for all your help. Has anyone heard of their service to repair bricked phones using Riff Jtag tools?
Hello,
at first, here is my HTC info:
cidnum: HTC__044
mainver: 4.19.707.3
I was flashing firmware and follow instruction from mike1986 thread
i download 4.19.707.3 firmware, but failed.
here's the log.
sending 'zip' (12866 KB)...
OKAY [ 1.524s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(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) Format partition LNX done
(bootloader) [RUU]WP,boot,100
(bootloader) start image[hboot] unzipping & flushing...
(bootloader) [RUU]WP,hboot,50
(bootloader) signature checking...
(bootloader) start image[recovery] unzipping & flushing...
(bootloader) Format partition SOS done
(bootloader) [RUU]WP,recovery,100
(bootloader) start image[tp] unzipping & flushing...
(bootloader) ERROR enable flash mode attn time out
(bootloader) ERROR enable flash mode attn time out
(bootloader) ERROR enable flash mode attn time out
(bootloader) ERROR enable flash mode attn time out
(bootloader) ERROR enable flash mode attn time out
(bootloader) unzip and update fail, error code : 6
FAILED (remote: 51 partition update fail)
finished. total time: 68.545s
Click to expand...
Click to collapse
and now, my phone stuck in silver HTC screen, cant get into bootloader
i've tried:
fastboot reload
fastboot reload-bootloader
fastboot oem rebootRUU
try to flash firmware again so many time but still stuck.
and i've tried to download same firmware from another sourse. still stuck
Please anybody help me.
Thanks..
-sorry for my bad english
SOLVED!!
After 3 hour, i tried flash firmware million times, finally it works again :good:
Hello, I have a verizon htc one m7. I am rooted and s-off.
1: getvar info
c:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.13.41.0702
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.28.605.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3910mV
(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!
finished. total time: 0.066s
2: In the the bootloader screen if I choose recovery the phone tries to load twrp screen goes to entering recovery goes black then the entering recovery screen comes back up and stays until I power down:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3: I have tried fastboot, flashify, rom toolbox pro and linux to flash twrp images. every one of them does so without error, yet I can not get into twrp. The md5 on every file I have tried to flash checked out ok.
4: I installed the ruu from dottat kitkat 4.4.2 and 4.4.3 and installed the ruu version of twrp 2.7.0.8 and 2.7.1.12 and still recovery does not load. This is after installing an ruu and wipes the phone completely.
5:I have tried everything that has been suggested including running the commands from a linux terminal.
If anybody knows how to fix this please help!
vaping redhead said:
Hello, I have a verizon htc one m7. I am rooted and s-off.
1: getvar info
c:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.13.41.0702
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.28.605.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3910mV
(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!
finished. total time: 0.066s
2: In the the bootloader screen if I choose recovery the phone tries to load twrp screen goes to entering recovery goes black then the entering recovery screen comes back up and stays until I power down:
3: I have tried fastboot, flashify, rom toolbox pro and linux to flash twrp images. every one of them does so without error, yet I can not get into twrp. The md5 on every file I have tried to flash checked out ok.
4: I installed the ruu from dottat kitkat 4.4.2 and 4.4.3 and installed the ruu version of twrp 2.7.0.8 and 2.7.1.12 and still recovery does not load. This is after installing an ruu and wipes the phone completely.
5:I have tried everything that has been suggested including running the commands from a linux terminal.
If anybody knows how to fix this please help!
Click to expand...
Click to collapse
Educate me: what's an RUU version of TWRP, as opposed to any other kind?
Which precise filename(s) of TWRP are you trying, where are you getting them?
jpradley said:
Educate me: what's an RUU version of TWRP, as opposed to any other kind?
Which precise filename(s) of TWRP are you trying, where are you getting them?
Click to expand...
Click to collapse
they are in zip format and can be downloaded from dottat thread in the developer section. you use the command fasboot flash zip "filename"
http://forum.xda-developers.com/verizon-htc-one/development/ruu-vzw-kitkat4-4-3-sense-6-s-off-t2867643
http://forum.xda-developers.com/showthread.php?t=2765784
vaping redhead said:
they are in zip format and can be downloaded from dottat thread in the developer section. you use the command fasboot flash zip "filename"]
Click to expand...
Click to collapse
OK, thanks.
But what's wrong with the file format that most everyone uses for a recovery installation, which isn't a *zip file, but a *img file?
jpradley said:
OK, thanks.
But what's wrong with the file format that most everyone uses for a recovery installation, which isn't a *zip file, but a *img file?
Click to expand...
Click to collapse
It is my understanding that img files can be flashed directly from fastboot or flashify etc. the zip file contains the image file and also a txt file and can only be flashed while your phone is in ruu mode "fastboot oem rebootRUU"
since there is 2 files that it why it is zipped. the txt file contained in there is the istructions that tell the rom update utility how to flash the enclosed recovery image file.
jpradley said:
Educate me: what's an RUU version of TWRP, as opposed to any other kind?
Which precise filename(s) of TWRP are you trying, where are you getting them?
Click to expand...
Click to collapse
Fastboot erase cache
Then flash your recovery again and see what you have.
dottat said:
Fastboot erase cache
Then flash your recovery again and see what you have.
Click to expand...
Click to collapse
I have tried that command, it does not solve recovery not loading. Trust me I have tried every suggestion I can find on the internet and nothing solves this. I am hoping someone out there has knowledge of exaclty how the recovery partition works because at this point it would appear that the recovery partition on my phone is either not being written to or is corrupted.
vaping redhead said:
I have tried that command, it does not solve recovery not loading. Trust me I have tried every suggestion I can find on the internet and nothing solves this. I am hoping someone out there has knowledge of exaclty how the recovery partition works because at this point it would appear that the recovery partition on my phone is either not being written to or is corrupted.
Click to expand...
Click to collapse
When you flash the ruu mode twrp put a -w on the end of the command.
dottat said:
When you flash the ruu mode twrp put a -w on the end of the command.
Click to expand...
Click to collapse
I will try. Here are the results
c:\adb>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.049s]
finished. total time: 0.050s
c:\adb>fastboot flash zip M7_RUU_TWRP.zip -w
target reported max download size of 1514139648 bytes
sending 'zip' (9360 KB)...
OKAY [ 1.059s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[recovery] unzipping & flushing...
(bootloader) [RUU]UZ,recovery,0
(bootloader) [RUU]UZ,recovery,10
(bootloader) [RUU]UZ,recovery,20
(bootloader) [RUU]UZ,recovery,30
(bootloader) [RUU]UZ,recovery,41
(bootloader) [RUU]UZ,recovery,51
(bootloader) [RUU]UZ,recovery,61
(bootloader) [RUU]UZ,recovery,73
(bootloader) [RUU]UZ,recovery,87
(bootloader) [RUU]UZ,recovery,98
(bootloader) [RUU]UZ,recovery,100
(bootloader) [RUU]WP,recovery,0
(bootloader) [RUU]WP,recovery,100
(bootloader) ...... Successful
OKAY [ 3.179s]
erasing 'userdata'...
FAILED (remote: not allowed)
finished. total time: 4.250s
Revovery still does not load.
vaping redhead said:
I will try. Here are the results
c:\adb>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.049s]
finished. total time: 0.050s
c:\adb>fastboot flash zip M7_RUU_TWRP.zip -w
target reported max download size of 1514139648 bytes
sending 'zip' (9360 KB)...
OKAY [ 1.059s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[recovery] unzipping & flushing...
(bootloader) [RUU]UZ,recovery,0
(bootloader) [RUU]UZ,recovery,10
(bootloader) [RUU]UZ,recovery,20
(bootloader) [RUU]UZ,recovery,30
(bootloader) [RUU]UZ,recovery,41
(bootloader) [RUU]UZ,recovery,51
(bootloader) [RUU]UZ,recovery,61
(bootloader) [RUU]UZ,recovery,73
(bootloader) [RUU]UZ,recovery,87
(bootloader) [RUU]UZ,recovery,98
(bootloader) [RUU]UZ,recovery,100
(bootloader) [RUU]WP,recovery,0
(bootloader) [RUU]WP,recovery,100
(bootloader) ...... Successful
OKAY [ 3.179s]
erasing 'userdata'...
FAILED (remote: not allowed)
finished. total time: 4.250s
Revovery still does not load.
Click to expand...
Click to collapse
Failed (remote not allowed)
Is a sure sign that something isn't set up right for flashing to the device.
It will never work if that is the result in terminal.
Are you using Usb 2.0 and the original data cable that is meant for the device?
I think you probably never successfully flashed any recovery.
I would advise trying a cable meant for this device.
santod040 said:
Failed (remote not allowed)
Is a sure sign that something isn't set up right for flashing to the device.
It will never work if that is the result in terminal.
Are you using Usb 2.0 and the original data cable that is meant for the device?
I think you probably never successfully flashed any recovery.
I would advise trying a cable meant for this device.
Click to expand...
Click to collapse
I am using the htc cable that came with the phone. I will double check that I am using USB 2.0 and try a different cable.
I also noticed wihen flashing with rom toolbox pro is says successful yet also says #error: cannot locate recovery partition
Is it possible my recovery partitiion is not there?
I just tried several cables including the the one from htc. I also made sure I was using a usb 2.0 port. I still get the failed(remote not allowed)
Thank you for the help btw.
Hi, I think I have figured this one out. I changed my phone from blue to red. Verizon only offers silver or blue. Anyway I thought I might have damaged my motherboard, So I bought a silver verizon htc one off ebay with a cracked screen. (easy fix). So I swapped the hardware from the silver to my red and with a new board in the red shell twrp does not load. However my old board wich twrp would not load on is now in the silver shell and twrp now loads. Bottom line the red shell is the problem.
vaping redhead said:
Hi, I think I have figured this one out. I changed my phone from blue to red. Verizon only offers silver or blue. Anyway I thought I might have damaged my motherboard, So I bought a silver verizon htc one off ebay with a cracked screen. (easy fix). So I swapped the hardware from the silver to my red and with a new board in the red shell twrp does not load. However my old board wich twrp would not load on is now in the silver shell and twrp now loads. Bottom line the red shell is the problem.
Click to expand...
Click to collapse
Update. The red shell is 100% to blame for recovery software not loading. I did some more tinkering with two m7 motherboards and in a stock verizon silver shell twrp loads. Both board when in the red shell, twrp does not load.
If anyone out there was thinking of converting their blue or silver verizon m7 to a different color. Be warned that your recovery software will probably not load once you transfer the hardware over to the new shell.
I guess if I want a red htc one that twrp works on, I have to get a m8
vaping redhead said:
Update. The red shell is 100% to blame for recovery software not loading. I did some more tinkering with two m7 motherboards and in a stock verizon silver shell twrp loads. Both board when in the red shell, twrp does not load.
If anyone out there was thinking of converting their blue or silver verizon m7 to a different color. Be warned that your recovery software will probably not load once you transfer the hardware over to the new shell.
I guess if I want a red htc one that twrp works on, I have to get a m8
Click to expand...
Click to collapse
Or just.... Paint it with a good quality modeling paint (like you buy for model cars, boats, etc). It is durable and lasts if you know how to coat it correctly.
Sent from my HTC6500LVWBLU using XDA Free mobile app
Doesn't seem to me that you solved the initial problem, just found a work around for it. I have the same problem with my phone not accepting the stock recovery for what ever reason. It will, however, accept the TWRP recovery, but this doesn't do me any good wrt warranty returns. before I S-On and Lock it, I need to have the stock recovery installed.
gryghst72 said:
Doesn't seem to me that you solved the initial problem, just found a work around for it. I have the same problem with my phone not accepting the stock recovery for what ever reason. It will, however, accept the TWRP recovery, but this doesn't do me any good wrt warranty returns. before I S-On and Lock it, I need to have the stock recovery installed.
Click to expand...
Click to collapse
Have you tried ruu? That should flash the stock recovery and everything else stock. Need to ruu when you s-on to ensure everything is okay before turning secure flag on.
Sent from my HTC6500LVWBLU using XDA Free mobile app
Uzephi said:
Have you tried ruu? That should flash the stock recovery and everything else stock. Need to ruu when you s-on to ensure everything is okay before turning secure flag on.
Sent from my HTC6500LVWBLU using XDA Free mobile app
Click to expand...
Click to collapse
I have RUU'd the following and in different orders:
5.28.605.2_NoBoot-IMG_firmware.zip
VZW.M7.5.28.605.2.PN0731IMG.zip
as well as "fastboot flash recovery 5.28.605.2_Stock_recovery.img"
all with a scattering of "fastboot erase cache".
The flash says it is successful, but when I boot to recovery, the screen graphics are garbage and when not garbage, it's the ! droid after the usual 15-20 sec blank screen. When I flash TWRP either via flash recovery or RUU that takes and works just fine. But this obviously isn't a "back to stock" set up.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.13.41.0702
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.28.605.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: xxxxxxxxxxxxxx
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3899mV
(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!
finished. total time: 0.164s
Thoughts?
gryghst72 said:
I have RUU'd the following and in different orders:
5.28.605.2_NoBoot-IMG_firmware.zip
VZW.M7.5.28.605.2.PN0731IMG.zip
as well as "fastboot flash recovery 5.28.605.2_Stock_recovery.img"
all with a scattering of "fastboot erase cache".
The flash says it is successful, but when I boot to recovery, the screen graphics are garbage and when not garbage, it's the ! droid after the usual 15-20 sec blank screen. When I flash TWRP either via flash recovery or RUU that takes and works just fine. But this obviously isn't a "back to stock" set up.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.13.41.0702
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.28.605.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: xxxxxxxxxxxxxx
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3899mV
(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!
finished. total time: 0.164s
Thoughts?
Click to expand...
Click to collapse
Have you tried the 2.x.y.z signed ruu in santod's stock Rom/firmware thread? Unsigned ruus are good, but sometimes a signed, official ruu gets the job done that unofficial ones can't.
Sent from my HTC6500LVWBLU using XDA Free mobile app
Uzephi said:
Have you tried the 2.x.y.z signed ruu in santod's stock Rom/firmware thread? Unsigned ruus are good, but sometimes a signed, official ruu gets the job done that unofficial ones can't.
Sent from my HTC6500LVWBLU using XDA Free mobile app
Click to expand...
Click to collapse
Is the signed one located here? I have not only because I have not read that one can go backwards, especially that far back. Can this be done successfully? What are the risks? Does the signed RUU contain all he necessary files to restart after the flash, are there any supporting flashes necessary (HBOOT, Recovery, Radios, etc.) Is this a viable solution or a shot in the dark which could brick the device?
Thanks for the on-going troubleshooting. I'm not trying to be a pain, just being careful since I am unfamiliar with the bootload/security features build into the system.
---------- Post added at 03:33 PM ---------- Previous post was at 02:58 PM ----------
I tried to RUU flash the 1.10.605.10 version .. here was my result:
C:\Android>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.047s]
finished. total time: 0.047s
C:\Android>fastboot flash zip PN07IMG_M7_WL_JB_50_VZW_422_VERIZON_WWE_1.10.605.10_Radio_1.12.42.0906_NV_VZW_3.71_002_release_334098_signed_2.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1178274 KB)...
OKAY [ 44.569s]
writing 'zip'...
(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: 51.044s
C:\Android>fastboot flash zip PN07IMG_M7_WL_JB_50_VZW_422_VERIZON_WWE_1.10.605.10_Radio_1.12.42.0906_NV_VZW_3.71_002_release_334098_signed_2.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1178274 KB)...
OKAY [ 44.632s]
writing 'zip'...
(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: 51.075s
C:\Android>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.031s]
finished. total time: 0.031s
C:\Android>fastboot reboot
rebooting...
finished. total time: 0.031s
Well, that didn't do anything, good or bad. Just didn't take and phone operates just fine as a phone, but still no recovery image, stock or otherwise.
Downloading 2.x.y.z signed version now. Will report the results after flash attempt.
Same results:
C:\Android>adb reboot-bootloader
C:\Android>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.062s]
finished. total time: 0.062s
C:\Android>fastboot flash zip RUU_2_10_605_1.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1232586 KB)...
OKAY [ 41.931s]
writing 'zip'...
(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: 48.420s
Hi all, first time in this forum and i hope someone would save me!
I have an HTC One M8
i'm **TAMPERED** **LOCKED** **SECURITY WARNING** and S-ON
so from hboot and fastboot i can't do anything (also enter in recovery mode)
via usb in hboot i can use fastboot command but not adb command (for that i have to turn on my device which restart in 30 secs so it's very hard)
i have to get it back to stock state but for doing that i need a RUU (fastboot flash is useless and as i sayed i can't do anything with adb in fastboot mode)
in order to do that i have downloaded from htc the mem_ul source to compile with AOSP but on the phone there aren't the proc/
config.gz file and i'm stucked here.
these are the fastboot getvar all instruction.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.101.1102.19.1017
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.18.401.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ***********
(bootloader) imei: *********
(bootloader) imei2: *******
(bootloader) meid: 00000000000000
(bootloader) product: mem_ul
(bootloader) platform: hTCBmsm8226
(bootloader) modelid: 0P8B20000
(bootloader) cidnum: HTC__001
(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: be7179e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.121s
Please help me you would be my hero!
ADB doesn't work in fastboot, only when booted into Android. You need to use the 4.16.401.10 RUU in General and flag it when connected in fastboot mode
EddyOS said:
ADB doesn't work in fastboot, only when booted into Android. You need to use the 4.16.401.10 RUU in General and flag it when connected in fastboot mode
Click to expand...
Click to collapse
His device is not M8 but HTC One mini 2.
ulisse2010 said:
Hi all, first time in this forum and i hope someone would save me!
Click to expand...
Click to collapse
Check this thread for your device type : http://forum.xda-developers.com/one-mini-2
and this for your RUU : http://forum.xda-developers.com/one-mini-2/general/htc-one-mini-2-european-signed-ruu-t3003069
Good spot!
thanks to all of you for the help in advance.
but i tried the ruu you suggested and it doesn't work. he said that i have to choice the correct one.
what it can be?
ulisse2010 said:
thanks to all of you for the help in advance.
but i tried the ruu you suggested and it doesn't work. he said that i have to choice the correct one.
what it can be?
Click to expand...
Click to collapse
That RUU says it requires s-off
Oh... i see
ok so it won't work if i modify like this? http://forum.xda-developers.com/showthread.php?t=2364349
it is about to inject another rom in a preexistent ruu...
have done it but and it starts but the progress bar stops on the first step and it reboot
ulisse2010 said:
thanks to all of you for the help in advance.
but i tried the ruu you suggested and it doesn't work. he said that i have to choice the correct one.
what it can be?
Click to expand...
Click to collapse
You have to use the one linked to by @ckpv5 as you have an M8 Mini - this is the 'proper' M8 forum...
i think it doesn't work because the file it's corrupted, another link maybe? i think also i'm getting trought this s****
Thx a lot all of you
How did you get this **TAMPERED** **LOCKED** **SECURITY WARNING**
Is it you unlocked it before then suddenly when it has reboot problem, it turns to **LOCKED** ?
How do you know the RUU zip is corrupted ? How actually you flash it, what commands ?
The OP will need the htc_fastboot version unless they do it via SD card...
i'm sorry it is **RELOCKED**
i'm pushing it by modifing another RUU (i put it inside by replacing the rom.zip and renaming it to rom.zip) and this RUU have the htc_fastboot.exe inside it so i'm trying now to push it via "cmd".
I think this op it's broken because i can't unzip it whitout error.
ulisse2010 said:
I think this op it's broken because i can't unzip it whitout error.
Click to expand...
Click to collapse
I have no idea what you are trying to do .... by pushing & modifying another RUU
But a signed RUU zip is encrypted, you can't unzip it, it's not that it's corrupted.
You flash it by connecting the phone in fastboot and then boot into RUU mode (fastboot oem rebootRUU) and then flash the RUU (htc_fastboot flash zip ruu.zip)
when i try to do fastboot oem rebootRUU the phone reboots but in normal mode not entering in bootloader or in RUU
it's possible to enter RUU mode with adb command?
ulisse2010 said:
when i try to do fastboot oem rebootRUU the phone reboots but in normal mode not entering in bootloader or in RUU
it's possible to enter RUU mode with adb command?
Click to expand...
Click to collapse
This is a symptom of a corrupted partition (more of a hardware problem) ...
I run out of idea to help you, further more your device is not M8.
Maybe someone else can help you ... good luck
please don't give up now i'm almost here:
i tried to flash it in ruu mode via htc_fastboot and the message is that:
sending 'zip'... (43267 KB) OKAY
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) total_image_number=7
(bootloader) start image[hboot] flushing...
(bootloader) signature checking...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
(bootloader) current_image_number=0
(bootloader) current_image_number=1
(bootloader) current_image_number=2
(bootloader) current_image_number=3
(bootloader) current_image_number=4
(bootloader) current_image_number=5
(bootloader) current_image_number=6
FAIL90 hboot pre-update! please flush image again immediately
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
Restart the same procedure with "hboot-preupdate" response for (SH4AAWR02353)...
< waiting for device >
sending 'zip'... (43267 KB) OKAY
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
FAILnot allowed
FAILED (remote: not allowed)
Execution time is 74(s)
how i fix it?
i can't give the command two time because the device restart after this message.
I've moved this thread from the One M8 forum to the One Mini 2 forum. Hopefully you will get help here from people who have the same phone. Good luck!