Android TV Launcher Pushed to Google Play

Over the past decade, the tech universe has seen two drastic and widely contrasting changes with … more

Cyngn, OnePlus, Micromax – The Legal Battle

Recently, a battle has been waging in India over the rights to distribute the commercial … more

Lean Mean Battery Power Saving App Review

We talk a lot about battery topics here at XDA TV. We talk about everything from Power Banks to USB … more

Android 5.1 Possibly Coming February 2015

Google released Android 5.0 just over a month ago, and since then Lollipop has been trying to … more

Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

[Q] HTC One Soft-Brick with a twist

OP Druuix

29th May 2014, 03:32 AM   |  #1  
OP Junior Member
Thanks Meter: 0
 
3 posts
Join Date:Joined: May 2014
Hey Guys,

A few nights ago I was tinkering around with my M7, testing out the custom Vyper Rom that is oh so popular. I unlocked my bootloader, gained SU rights on the phone, and was flashing the rim.zip file in recovery using TWRP. It was rolling around 2:30 AM, and I was pretty exhausted but I kept going. The installation failed, and I had a malfunctioning copy of the ROM. The home page didn't display, no apps, etc. Frustrated, I powered down the phone, entered fastboot, and then entered recovery. Any attempt to reinstall the ROM was failing, so in my irritation, I managed to re-lock my bootloader, delete the system cache, and left S-ON active. For all intents and purposes, I take it this is a soft brick.

Now, after about 17~ hours of research, testing, and frustration, I come to you guys for help. The furthest I've gotten so far is to use Process Monitor to take the rom.zip out of the RUU for (what I thought) is my HTC One. It works up until the Model ID check, which is apparantly incorrect.

My fastboot getvar all is this:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.502.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3826mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

Any ideas?

NOTE: I am unable to access recovery as well right now, and at the top of the screen, ***TAMPERED*** ***RELOCKED*** ***SECURITY WARNING*** is displaying. Any attempt to leave the bootloader results in the reloading OF the boot loader. The only other function I have had work is Fastboot oem rebootRUU. If it would help, when I attempt a flash of the .RUU.zip, my CLI appears as such:

C:\mini-sdk>fastboot oem rebootRUU
... (bootloader) Start Verify: 3
OKAY

C:\mini-sdk>fastboot flash zip rom4.zip
sending 'zip'... (41217 KB) [isLargeZip: 1 fileCount: 1 / 5]
Sending... 10240 KB / 41217 KB
Sending... 20480 KB / 41217 KB
Sending... 30720 KB / 41217 KB
Sending... 40960 KB / 41217 KB
Sending... 41217 KB / 41217 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...
FAIL41 model id check fail
FAILED (remote: 41 model id check fail)

C:\mini-sdk>

Any ideas? My next step is to try and find my model ID RUU, but I can't seem to find it. The RUU I used is RUU_M7_UL_K44_SENSE55_MR_Bouygues_FR_4.20.1020.12_ Radio_4A.23.3263.28_10.38r.1157.04L_release_351533 _signed_2
Last edited by Druuix; 29th May 2014 at 06:04 AM.
29th May 2014, 04:24 AM   |  #2  
n1234d's Avatar
Senior Member
Flag Mumbai
Thanks Meter: 221
 
743 posts
Join Date:Joined: Aug 2013
More
Quote:
Originally Posted by Druuix

Hey Guys,

A few nights ago I was tinkering around with my M7, testing out the custom Vyper Rom that is oh so popular. I unlocked my bootloader, gained SU rights on the phone, and was flashing the rim.zip file in recovery using TWRP. It was rolling around 2:30 AM, and I was pretty exhausted but I kept going. The installation failed, and I had a malfunctioning copy of the ROM. The home page didn't display, no apps, etc. Frustrated, I powered down the phone, entered fastboot, and then entered recovery. Any attempt to reinstall the ROM was failing, so in my irritation, I managed to re-lock my bootloader, delete the system cache, and left S-ON active. For all intents and purposes, I take it this is a soft brick.

Now, after about 17~ hours of research, testing, and frustration, I come to you guys for help. The furthest I've gotten so far is to use Process Monitor to take the rom.zip out of the RUU for (what I thought) is my HTC One. It works up until the Model ID check, which is apparantly incorrect.

My fastboot getvar all is this:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.502.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3826mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

Any ideas?

NOTE: I am unable to access recovery as well right now, and at the top of the screen, ***TAMPERED*** ***RELOCKED*** ***SECURITY WARNING*** is displaying. Any attempt to leave the bootloader results in the reloading OF the boot loader. The only other function I have had work is Fastboot oem rebootRUU. If it would help, when I attempt a flash of the .RUU.zip, my CLI appears as such:

C:\mini-sdk>fastboot oem rebootRUU
... (bootloader) Start Verify: 3
OKAY

C:\mini-sdk>fastboot flash zip rom4.zip
sending 'zip'... (41217 KB) [isLargeZip: 1 fileCount: 1 / 5]
Sending... 10240 KB / 41217 KB
Sending... 20480 KB / 41217 KB
Sending... 30720 KB / 41217 KB
Sending... 40960 KB / 41217 KB
Sending... 41217 KB / 41217 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...
FAIL41 model id check fail
FAILED (remote: 41 model id check fail)

C:\mini-sdk>

Any ideas? My next step is to try and find my model ID RUU, but I can't seem to find it. The RUU I used is RUU_M7_UL_K44_SENSE55_MR_Bouygues_FR_4.20.1020.12_ Radio_4A.23.3263.28_10.38r.1157.04L_release_351533 _signed_2

Please remove your IMEI/SN. The RUU that you're trying to flash is the wrong one. Just try re-unlocking the bootloader, and flashing a recovery, rom. I'd say, flash ARHD 31.6 and use firewater to gain s-off. Then flash whatever rom you want to.
29th May 2014, 07:02 AM   |  #3  
OP Junior Member
Thanks Meter: 0
 
3 posts
Join Date:Joined: May 2014
eauChot and
Quote:
Originally Posted by n1234d

Please remove your IMEI/SN. The RUU that you're trying to flash is the wrong one. Just try re-unlocking the bootloader, and flashing a recovery, rom. I'd say, flash ARHD 31.6 and use firewater to gain s-off. Then flash whatever rom you want to.

That was a process I had already attempted, at least the bootloader unlocking.

C:\mini-sdk>fastboot flash unlocktoken unlock_code,bin
error: cannot load 'unlock_code,bin'


C:\mini-sdk>

The bootloader refuses to load anything else other than the fastboot. Even if the device is powered off, it will automatically boot to fastboot just by plugging in the phone to the PC
29th May 2014, 07:11 AM   |  #4  
ckpv5's Avatar
Recognized Contributor
Flag Kuala Lumpur
Thanks Meter: 9,517
 
7,357 posts
Join Date:Joined: Feb 2008
Donate to Me
More
Quote:
Originally Posted by Druuix

That was a process I had already attempted, at least the bootloader unlocking.

C:\mini-sdk>fastboot flash unlocktoken unlock_code,bin
error: cannot load 'unlock_code,bin'


C:\mini-sdk>

The bootloader refuses to load anything else other than the fastboot. Even if the device is powered off, it will automatically boot to fastboot just by plugging in the phone to the PC

Your .......unlock_code,bin is wrong
it should be unlock_code.bin

(a dot not a comma)
29th May 2014, 07:49 AM   |  #5  
OP Junior Member
Thanks Meter: 0
 
3 posts
Join Date:Joined: May 2014
Quote:
Originally Posted by ckpv5

Your .......unlock_code,bin is wrong
it should be unlock_code.bin

(a dot not a comma)

Oh man, I'm dumb.. Alright well I got the bootlocker unlocked, and the security warning is gone now. I can access recovery now, but I seem to only be able to flash .img files. The rom.zip files will not flash through fastboot. I get this error:
C:\mini-sdk>fastboot flash zip rom5.zip
< waiting for device >
sending 'zip'... (1133440 KB) [isLargeZip: 0 fileCount: 1 / 1]
Sending... 10240 KB / 1133440 KB
Sending... 20480 KB / 1133440 KB
Sending... 30720 KB / 1133440 KB
Sending... 40960 KB / 1133440 KB
Sending... 51200 KB / 1133440 KB
Sending... 61440 KB / 1133440 KB
Sending... 71680 KB / 1133440 KB
Sending... 81920 KB / 1133440 KB
Sending... 92160 KB / 1133440 KB
Sending... 102400 KB / 1133440 KB
Sending... 112640 KB / 1133440 KB
Sending... 122880 KB / 1133440 KB
Sending... 133120 KB / 1133440 KB
Sending... 143360 KB / 1133440 KB
Sending... 153600 KB / 1133440 KB
Sending... 163840 KB / 1133440 KB
Sending... 174080 KB / 1133440 KB
Sending... 184320 KB / 1133440 KB
Sending... 194560 KB / 1133440 KB
Sending... 204800 KB / 1133440 KB
Sending... 215040 KB / 1133440 KB
Sending... 225280 KB / 1133440 KB
Sending... 235520 KB / 1133440 KB
Sending... 245760 KB / 1133440 KB
Sending... 256000 KB / 1133440 KB
Sending... 266240 KB / 1133440 KB
Sending... 276480 KB / 1133440 KB
Sending... 286720 KB / 1133440 KB
Sending... 296960 KB / 1133440 KB
Sending... 307200 KB / 1133440 KB
Sending... 317440 KB / 1133440 KB
Sending... 327680 KB / 1133440 KB
Sending... 337920 KB / 1133440 KB
Sending... 348160 KB / 1133440 KB
Sending... 358400 KB / 1133440 KB
Sending... 368640 KB / 1133440 KB
Sending... 378880 KB / 1133440 KB
Sending... 389120 KB / 1133440 KB
Sending... 399360 KB / 1133440 KB
Sending... 409600 KB / 1133440 KB
Sending... 419840 KB / 1133440 KB
Sending... 430080 KB / 1133440 KB
Sending... 440320 KB / 1133440 KB
Sending... 450560 KB / 1133440 KB
Sending... 460800 KB / 1133440 KB
Sending... 471040 KB / 1133440 KB
Sending... 481280 KB / 1133440 KB
Sending... 491520 KB / 1133440 KB
Sending... 501760 KB / 1133440 KB
Sending... 512000 KB / 1133440 KB
Sending... 522240 KB / 1133440 KB
Sending... 532480 KB / 1133440 KB
Sending... 542720 KB / 1133440 KB
Sending... 552960 KB / 1133440 KB
Sending... 563200 KB / 1133440 KB
Sending... 573440 KB / 1133440 KB
Sending... 583680 KB / 1133440 KB
Sending... 593920 KB / 1133440 KB
Sending... 604160 KB / 1133440 KB
Sending... 614400 KB / 1133440 KB
Sending... 624640 KB / 1133440 KB
Sending... 634880 KB / 1133440 KB
Sending... 645120 KB / 1133440 KB
Sending... 655360 KB / 1133440 KB
Sending... 665600 KB / 1133440 KB
Sending... 675840 KB / 1133440 KB
Sending... 686080 KB / 1133440 KB
Sending... 696320 KB / 1133440 KB
Sending... 706560 KB / 1133440 KB
Sending... 716800 KB / 1133440 KB
Sending... 727040 KB / 1133440 KB
Sending... 737280 KB / 1133440 KB
Sending... 747520 KB / 1133440 KB
Sending... 757760 KB / 1133440 KB
Sending... 768000 KB / 1133440 KB
Sending... 778240 KB / 1133440 KB
Sending... 788480 KB / 1133440 KB
Sending... 798720 KB / 1133440 KB
Sending... 808960 KB / 1133440 KB
Sending... 819200 KB / 1133440 KB
Sending... 829440 KB / 1133440 KB
Sending... 839680 KB / 1133440 KB
Sending... 849920 KB / 1133440 KB
Sending... 860160 KB / 1133440 KB
Sending... 870400 KB / 1133440 KB
Sending... 880640 KB / 1133440 KB
Sending... 890880 KB / 1133440 KB
Sending... 901120 KB / 1133440 KB
Sending... 911360 KB / 1133440 KB
Sending... 921600 KB / 1133440 KB
Sending... 931840 KB / 1133440 KB
Sending... 942080 KB / 1133440 KB
Sending... 952320 KB / 1133440 KB
Sending... 962560 KB / 1133440 KB
Sending... 972800 KB / 1133440 KB
Sending... 983040 KB / 1133440 KB
Sending... 993280 KB / 1133440 KB
Sending... 1003520 KB / 1133440 KB
Sending... 1013760 KB / 1133440 KB
Sending... 1024000 KB / 1133440 KB
Sending... 1034240 KB / 1133440 KB
Sending... 1044480 KB / 1133440 KB
Sending... 1054720 KB / 1133440 KB
Sending... 1064960 KB / 1133440 KB
Sending... 1075200 KB / 1133440 KB
Sending... 1085440 KB / 1133440 KB
Sending... 1095680 KB / 1133440 KB
Sending... 1105920 KB / 1133440 KB
Sending... 1116160 KB / 1133440 KB
Sending... 1126400 KB / 1133440 KB
Sending... 1133440 KB / 1133440 KB
OKAY
writing 'zip'... FAILnot allowed
FAILED (remote: not allowed)

C:\mini-sdk>fastboot erase userdata
erasing 'userdata'... FAILnot allowed
FAILED (remote: not allowed)

C:\mini-sdk>

I'm looking into what the remote: not allowed is a sign of right now

UPDATE: Just an update for anyone who has a similar issue as mine. After I unlocked the bootloader, I flashed CWM recovery and installed android_usb_driver.zip so my phone would appear in the adb list. Once I got it to appear, I sideloaded my ROM onto the card.

More to come
Last edited by Druuix; 29th May 2014 at 08:26 AM.
29th May 2014, 08:03 AM   |  #6  
ckpv5's Avatar
Recognized Contributor
Flag Kuala Lumpur
Thanks Meter: 9,517
 
7,357 posts
Join Date:Joined: Feb 2008
Donate to Me
More
Quote:
Originally Posted by Druuix

Oh man, I'm dumb.. Alright well I got the bootlocker unlocked, and the security warning is gone now. I can access recovery now, but I seem to only be able to flash .img files. The rom.zip files will not flash through fastboot. I get this error:
C:\mini-sdk>fastboot flash zip rom5.zip
< waiting for device >
sending 'zip'... (1133440 KB) [isLargeZip: 0 fileCount: 1 / 1]
..
writing 'zip'... FAILnot allowed
FAILED (remote: not allowed)

C:\mini-sdk>fastboot erase userdata
erasing 'userdata'... FAILnot allowed
FAILED (remote: not allowed)

C:\mini-sdk>

I'm looking into what the remote: not allowed is a sign of right now

I don't know what you are trying to do ... but all those look totally wrong way (at least for me).

What the other guy suggest is put another custom ROM.zip as you don't have the right stock ROM for your device.

First ... make sure you have a TWRP 2.6.3.3 installed as all other TWRP seems buggy for most people (including me ... that is why I have TWRP 2.7.0.4 in my signature as I mod that one to be fully working that suit my needs)

Second ... find a custom Sense ROM.zip of your choice ...

Third ... look around how to do adb push ROM.zip to recovery/sdcard (I never do this, if I wipe clean everything, I will use OTG cable to load the ROM)

Once everything ok then only you look forward to the next step ... either back to stock or try any other ROM
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes