Develop Bugs

[q] omfg help!

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?

[Q] Please Help Soft Brinck, No RUU will take

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

[Q] STUCK with HTC logo and 4 triangles in corners

Need some help daorderdillon...I have an HTC One M8
I wanted to flash to the UNROOTED Google Play Edition...so I rooted, TWRP'ed and did the S-OFF
and then tried to flash the ROM while in RUU mode...it gave me back a "41 error"...
so I tried to change the ModelID in the android.txt file...flashed, and then my HTC One M8 kept going into the HTC logo screen with 4 triangle error screen
When I do fastboot oem reboot, it gets me back into the device - but any normal restart after, and I'm back in the HTC logo error screen
I can't go into recovery mode either - using the POWER and UP / DOWN buttons or through the software...
Stuck, and I really don't know what to do
Thanks in advance!

wikwikwik said:
I've looked everyone and really need some help now
I've done the following steps to try and convert my Asia HTC One M8 to the Google Play Edition
Rooted the phone
Did the S-Off
The final flash using the ROM didn't work - so I tried changing the MODELID, and then the 4 warning triangles started to show up
I don't know what to do...so if you can help me with detailed steps to fix and get back to the stock ROM - that would be greatly appreciated
Thanks in advance
Click to expand...
Click to collapse
Do volume up and power when starts to reboot hold power volume down to get back to recovery

jaythenut said:
Do volume up and power when starts to reboot hold power volume down to get back to recovery
Click to expand...
Click to collapse
I tried that multiple times...but still gives me the HTC logo with the 4 triangles...
Don't know what else to do...
Thanks for your help...

Which network was the phone on?
The phone has a corrupt boot loader. You need to flash the correct firmware and then you will be able to boot into the boot loader.
Sent from my HTC One_M8 using Tapatalk

While you were trying to flash GPE Rom on RUU mode or you were flashing the RUU?

x017in said:
Which network was the phone on?
The phone has a corrupt boot loader. You need to flash the correct firmware and then you will be able to boot into the boot loader.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
I'm on the 3 network in Hong Kong...the phone came unlocked when I bought it
Since I'm new to all this, can you help walk me through the steps on where to find the correct firmware and the process to get into the bootloader?
Thanks!

maxrdlf95 said:
While you were trying to flash GPE Rom on RUU mode or you were flashing the RUU?
Click to expand...
Click to collapse
I was trying to flash the GPE Rom while in RUU mode
Then I got the 41 modelid error...so I tried to change the modelid and flash the android-file.txt
That's when the phone became stuck
Thanks!

you can restart to bootloader mode?

maxrdlf95 said:
you can restart to bootloader mode?
Click to expand...
Click to collapse
No, that seems to be the problem...I can't get into bootloader
The only thing that seems to work temporarily is that I can do the fastboot oem boot...but I reboot, and back at the error screen

Need to Reflash firmware
What is your fastboot getvar all output?

SaHiLzZ said:
Need to Reflash firmware
What is your fastboot getvar all output?
Click to expand...
Click to collapse
Hi, this is what I get with getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331831.A11G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B63000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!

wikwikwik said:
Hi, this is what I get with getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331831.A11G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B63000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
Your CID/MID matches what is required in conversion. I will suggest to redownload the file, and restart the process
fastboot oem rebootRUU
fastboot flash zip RUU-HTC_One_M8_GE-1.16.1700.16.zip
fastboot flash zip RUU-HTC_One_M8_GE-1.16.1700.16.zip

SaHiLzZ said:
Your CID/MID matches what is required in conversion. I will suggest to redownload the file, and restart the process
fastboot oem rebootRUU
fastboot flash zip RUU-HTC_One_M8_GE-1.16.1700.16.zip
fastboot flash zip RUU-HTC_One_M8_GE-1.16.1700.16.zip
Click to expand...
Click to collapse
Here's the error message I get when I try and reflash (after doing a new download):
target reported max download size of 1830711296 bytes
sending 'zip' (510598 KB)...
OKAY [ 16.173s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 16.672s
I always get the 41 model id check fail

wikwikwik said:
Here's the error message I get when I try and reflash (after doing a new download):
target reported max download size of 1830711296 bytes
sending 'zip' (510598 KB)...
OKAY [ 16.173s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 16.672s
I always get the 41 model id check fail
Click to expand...
Click to collapse
Try supercid.
I tried flashing a stock rom and i change my CID to match the rom but i got the same error. Change it to supercid and it worked
Sent from my HTC One_M8 using XDA Premium 4 mobile app

ring_GT said:
Try supercid.
I tried flashing a stock rom and i change my CID to match the rom but i got the same error. Change it to supercid and it worked
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi, did that...and got this error message:
FAILED (remote: 24 parsing android-info fail)

Post your file config from the Android-info.txt please.
And what did you use to edit the MID there?
wikwikwik said:
Hi, did that...and got this error message:
FAILED (remote: 24 parsing android-info fail)
Click to expand...
Click to collapse

ring_GT said:
Post your file config from the Android-info.txt please.
And what did you use to edit the MID there?
Click to expand...
Click to collapse
modelid: 0P6B63000
cidnum: 11111111
mainver: 1.54.708.5
btype:1
aareport:1
hbootpreupdate:12

wikwikwik said:
modelid: 0P6B63000
cidnum: 11111111
mainver: 1.54.708.5
btype:1
aareport:1
hbootpreupdate:12
Click to expand...
Click to collapse
How did you edit the file? Notepad++?
Sent from my HTC One_M8 using XDA Premium 4 mobile app

ring_GT said:
How did you edit the file? Notepad++?
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah, it was just TEXTEDIT on Mac

Do you have a windows pc there?
Look at this thread... http://forum.xda-developers.com/showthread.php?t=2322820&page=19
"""""""""""""
"Thnx for reply but I just get it working.
My problem was the way of unzipping on MacOSX.
I now did it with 7Zip and NotePad++ on windows8 and it worked.
(No unzip, just editing the file in the zip)
"""""""""""
it is for htc one but he got the same error as you, and it was an issue with MAC OSX unzipping.
This all I can do. If still no go you will need an expert to help you.
wikwikwik said:
Yeah, it was just TEXTEDIT on Mac
Click to expand...
Click to collapse

[Soft Bricked] need ruu for HTC M8

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!

[Q] Stuck in Tampered with BL Locked and S-On [SOLVED]

Hello Android geeks! I am a novice Android user and have got myself a big problem!
I had a rooted phone with a custom recovery and a custom rom. Trying to return it to stock conditions (to sell), I did the following:
- Flashed the stock rom using the following RUU: http://forum.xda-developers.com/ver...m-google-play-edition-lollipop-v1-00-t2963841
- Relocked the BL
- Used the revone tool to change "relock" to "lock" and then to S-On
Now I am stuck at the screen that says Tampered and Locked with S-on. I try rebooting the phone or going to recovery, and I end up here again! I have researching it from this morning and tried several things without any luck! Here are some more details:
HBOOT-1.61.0000
RADIO-1.13.41.1209
Your help is really really appreciated!

SalmanMa said:
Hello Android geeks! I am a novice Android user and have got myself a big problem!
I had a rooted phone with a custom recovery and a custom rom. Trying to return it to stock conditions (to sell), I did the following:
- Flashed the stock rom using the following RUU: http://forum.xda-developers.com/ver...m-google-play-edition-lollipop-v1-00-t2963841
- Relocked the BL
- Used the revone tool to change "relock" to "lock" and then to S-On
Now I am stuck at the screen that says Tampered and Locked with S-on. I try rebooting the phone or going to recovery, and I end up here again! I have researching it from this morning and tried several things without any luck! Here are some more details:
HBOOT-1.61.0000
RADIO-1.13.41.1209
Your help is really really appreciated!
Click to expand...
Click to collapse
That's not an ruu
Show me the output of fastboot getvar all
Edit out the serial number and imei

dottat said:
That's not an ruu
Show me the output of fastboot getvar all
Edit out the serial number and imei
Click to expand...
Click to collapse
Thanks a lot for responding! Here it is:
Code:
c:\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 1.13.41.1209
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.22.605.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXX
(bootloader) imei: XXXX
(bootloader) meid: XXXX
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3750mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.049s

SalmanMa said:
Thanks a lot for responding! Here it is:
Code:
c:\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 1.13.41.1209
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.22.605.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXX
(bootloader) imei: XXXX
(bootloader) meid: XXXX
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3750mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.049s
Click to expand...
Click to collapse
Install HTC sync. Boot phone to fastboot mode. Connect to PC. Wait for phone to be read and click repair in the sync app. This will repair ruu your phone. Tampered will be gone and phone will be 100% stock.

dottat said:
Install HTC sync. Boot phone to fastboot mode. Connect to PC. Wait for phone to be read and click repair in the sync app. This will repair ruu your phone. Tampered will be gone and phone will be 100% stock.
Click to expand...
Click to collapse
HTC Sync does not detect the phone!

SalmanMa said:
HTC Sync does not detect the phone!
Click to expand...
Click to collapse
Check device manager. Likely you need to force update the driver that's installed for your phone to the latest which should be in c:/program files / HTC/ drivers
Sent from my HTC6535LVW using Tapatalk

dottat said:
Check device manager. Likely you need to force update the driver that's installed for your phone to the latest which should be in c:/program files / HTC/ drivers
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
The drivers were the latest. I reinstalled the Sync Manager with the drivers, and still no luck. Please see the screen shots below. It shows "no phone connected" in the lower left, but shows a phone without any information on the right (it disappears when I disconnect the phone). When I go to repair, I see the screen on the bottom and cannot do anything.
{
"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"
}

SalmanMa said:
The drivers were the latest. I reinstalled the Sync Manager with the drivers, and still no luck. Please see the screen shots below. It shows "no phone connected" in the lower left, but shows a phone without any information on the right (it disappears when I disconnect the phone). When I go to repair, I see the screen on the bottom and cannot do anything.
Click to expand...
Click to collapse
Alright. So you will need to manually flash this ruu. Download and rename file to rom.zip
https://www.androidfilehost.com/?fid=24052804347761412
To be successful you will need to use the following version of fastboot. Your old sdk version will not work.
https://www.androidfilehost.com/?fid=95784891001612150
Unzip this folder and drag the ruu into the newly created folder. Hold shift and right click inside the newly created folder and hit "open cmd prompt here".
Run the following commands
HTC_fastboot oem rebootRUU
HTC_fastboot flash zip rom.zip
Allow cmd above to fully finish. Once complete issue the following cmd to reboot
HTC_fastboot reboot
Sent from my HTC6535LVW using Tapatalk

dottat said:
Alright. So you will need to manually flash this ruu. Download and rename file to rom.zip
To be successful you will need to use the following version of fastboot. Your old sdk version will not work.
Unzip this folder and drag the ruu into the newly created folder. Hold shift and right click inside the newly created folder and hit "open cmd prompt here".
Run the following commands
HTC_fastboot oem rebootRUU
HTC_fastboot flash zip rom.zip
Allow cmd above to fully finish. Once complete issue the following cmd to reboot
HTC_fastboot reboot
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
The good news is it is finally doing something. All I got with other RUUs was signature checking failed.
The bad news is after a quick restart (you can see it in the log), it has been stuck here for about 15 minutes now. I will leave it be to see if it gets anywhere. I will update the post then!
Code:
C:\HTC_fastboot_adb>HTC_fastboot flash zip rom.zip
sending 'zip'... (46522 KB) OKAY
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
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 (FA37TS921762)...
< waiting for device >
sending 'zip'... (46522 KB)

SalmanMa said:
The good news is it is finally doing something. All I got with other RUUs was signature checking failed.
The bad news is after a quick restart (you can see it in the log), it has been stuck here for about 15 minutes now. I will leave it be to see if it gets anywhere. I will update the post then!
Code:
C:\HTC_fastboot_adb>HTC_fastboot flash zip rom.zip
sending 'zip'... (46522 KB) OKAY
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
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 (FA37TS921762)...
< waiting for device >
sending 'zip'... (46522 KB)
Click to expand...
Click to collapse
Unplug phone and replug it.
Start that exact cmd over again.
Sent from my HTC6535LVW using Tapatalk

dottat said:
Unplug phone and replug it.
Start that exact cmd over again.
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
Thanks to you, my phone is back alive!! I think the problem was the HTC Sync intervening when the phone automatically rebooted. After I uninstalled the HTC Sync, it went through seamlessly, and after the final reboot, my phone was quickly up and running!
Now, out of curiosity, I want to know:
- What I did wrong in the first place that got me stuck there?
- Why all the RUUs I tried failed?
- And where you got this RUU from?
Thank you so much again!

SalmanMa said:
Thanks to you, my phone is back alive!! I think the problem was the HTC Sync intervening when the phone automatically rebooted. After I uninstalled the HTC Sync, it went through seamlessly, and after the final reboot, my phone was quickly up and running!
Now, out of curiosity, I want to know:
- What I did wrong in the first place that got me stuck there?
- Why all the RUUs I tried failed?
- And where you got this RUU from?
Thank you so much again!
Click to expand...
Click to collapse
Specifically to flash a signed ruu you just use HTC fastboot. Regular fastboot doesn't understand htc's [email protected] format that really has it split into about 7 different zip files. You probably noticed it sending system at least 5 times. That's because it's split up.
Sent from my HTC6535LVW using Tapatalk

SalmanMa said:
Thanks to you, my phone is back alive!! I think the problem was the HTC Sync intervening when the phone automatically rebooted. After I uninstalled the HTC Sync, it went through seamlessly, and after the final reboot, my phone was quickly up and running!
Now, out of curiosity, I want to know:
- What I did wrong in the first place that got me stuck there?
- Why all the RUUs I tried failed?
- And where you got this RUU from?
Thank you so much again!
Click to expand...
Click to collapse
Great to see you up and running .... :good:
Can you add 'SOLVED' to the thread title ....
Thx Josh

lj50036 said:
Great to see you up and running .... :good:
Can you add 'SOLVED' to the thread title ....
Thx Josh
Click to expand...
Click to collapse
Thank you for reminding me!