Post Reply

[FIXED - Post #19] Soft-Bricked?

OP andreasf93

17th June 2014, 06:10 PM   |  #1  
andreasf93's Avatar
OP Senior Member
Thanks Meter: 18
 
223 posts
Join Date:Joined: Jan 2012
So today I received a HTC One from a friend and something is going really wrong with the device. He bought it as used and I found out that it was already S-OFF/Unlocked BL/Rooted but we wanted to change the ROM. I tried to flash SlimKat but I kept getting error 7 and after a google search I saw that the problem was caused by outdated recovery (had an older version of CWM). Then I proceeded to install the latest CWM from the official website and after the installation I kept getting this error:

http://i.imgur.com/M9trfGW.jpg

While trying to fix that error we realised that the device was HTC One J and not HTC One. TL;DR I fixed it and while trying to install a ROM I got this error:

http://i.imgur.com/rXRyRsW.jpg

Notice at the end: This package is a for "m7wlj" devices; this is a "dlx"

I searched on Google about dlx and I found that it is the Verizon version of HTC One (http://www.androidcentral.com/verizon-htc-dlx).
What the hell is going on with this device? What is the actual source of it? Verizon or Japan??

I forgot to mention.. after updating the CWM version I get bootloop on bootloader and can no longer boot on OS.
Last edited by andreasf93; 18th June 2014 at 01:00 AM.
17th June 2014, 06:22 PM   |  #2  
Seanie280672's Avatar
Senior Member
Flag Halesowen
Thanks Meter: 344
 
1,162 posts
Join Date:Joined: Feb 2012
Donate to Me
More
maybe this can answer it for you http://www.droid-life.com/tag/dlx/

also have you tried twrp recovery rather than cwm, if it is the Verizon then you will need the Verizon version of twrp, normal version wont work.
The Following User Says Thank You to Seanie280672 For This Useful Post: [ View ]
17th June 2014, 06:28 PM   |  #3  
andreasf93's Avatar
OP Senior Member
Thanks Meter: 18
 
223 posts
Join Date:Joined: Jan 2012
Update: We contacted the guy he bought the phone from and he said he bought it from Japan already unlocked.

I've download slimkat verizon version just to try it out and now I get a different error:

http://i.imgur.com/WC6sZEV.jpg

Any ideas?
17th June 2014, 06:29 PM   |  #4  
andreasf93's Avatar
OP Senior Member
Thanks Meter: 18
 
223 posts
Join Date:Joined: Jan 2012
Quote:
Originally Posted by Seanie280672

maybe this can answer it for you http://www.droid-life.com/tag/dlx/

also have you tried twrp recovery rather than cwm, if it is the Verizon then you will need the Verizon version of twrp, normal version wont work.

Downling the verizon version now to test: http://forum.xda-developers.com/show....php?t=2416431
17th June 2014, 06:33 PM   |  #5  
andreasf93's Avatar
OP Senior Member
Thanks Meter: 18
 
223 posts
Join Date:Joined: Jan 2012
Quote:
Originally Posted by andreasf93

Downling the verizon version now to test: http://forum.xda-developers.com/show....php?t=2416431

This is what I get with Verizon TWRP: http://i.imgur.com/cWyu5WB.jpg
17th June 2014, 06:40 PM   |  #6  
Seanie280672's Avatar
Senior Member
Flag Halesowen
Thanks Meter: 344
 
1,162 posts
Join Date:Joined: Feb 2012
Donate to Me
More
can you post fastboot getvar all please remove serial number and imei first though please before posting, it might tell us exactly what device you have.
The Following User Says Thank You to Seanie280672 For This Useful Post: [ View ]
17th June 2014, 06:51 PM   |  #7  
andreasf93's Avatar
OP Senior Member
Thanks Meter: 18
 
223 posts
Join Date:Joined: Jan 2012
Quote:
Originally Posted by Seanie280672

can you post fastboot getvar all please remove serial number and imei first though please before posting, it might tell us exactly what device you have.

Code:
version: 0.5
version-bootloader: 1.54.0000
version-baseband: 1.23.11.1209
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-OFF
serialno: xxx
imei: xxx
meid: 99000291297045
product: m7_wlj
platform: HBOOT-8064
modelid: PN0740000
cidnum: 11111111
battery-status: good
battery-voltage: 4177mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-59e2cf62
hbootpreupdate: 11
gencheckpt: 0
17th June 2014, 07:01 PM   |  #8  
Seanie280672's Avatar
Senior Member
Flag Halesowen
Thanks Meter: 344
 
1,162 posts
Join Date:Joined: Feb 2012
Donate to Me
More
Quote:
Originally Posted by andreasf93

Code:
version: 0.5
version-bootloader: 1.54.0000
version-baseband: 1.23.11.1209
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-OFF
serialno: xxx
imei: xxx
meid: 99000291297045
product: m7_wlj
platform: HBOOT-8064
modelid: PN0740000
cidnum: 11111111
battery-status: good
battery-voltage: 4177mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-59e2cf62
hbootpreupdate: 11
gencheckpt: 0

http://forum.xda-developers.com/show....php?t=2680107 already S-OFF and super CID helps a lot, that's a whole thread to things you can flash
Last edited by Seanie280672; 17th June 2014 at 07:03 PM.
The Following User Says Thank You to Seanie280672 For This Useful Post: [ View ]
17th June 2014, 07:22 PM   |  #9  
andreasf93's Avatar
OP Senior Member
Thanks Meter: 18
 
223 posts
Join Date:Joined: Jan 2012
Quote:
Originally Posted by Seanie280672

http://forum.xda-developers.com/show....php?t=2680107 already S-OFF and super CID helps a lot, that's a whole thread to things you can flash

Thank you, I've installed TWRP from there and I get this in the log:

E: Unable to mount '/cache'

And also I can't see the device in "adb devices" in order to sideload the ROM.
17th June 2014, 07:36 PM   |  #10  
Seanie280672's Avatar
Senior Member
Flag Halesowen
Thanks Meter: 344
 
1,162 posts
Join Date:Joined: Feb 2012
Donate to Me
More
Quote:
Originally Posted by andreasf93

Thank you, I've installed TWRP from there and I get this in the log:

E: Unable to mount '/cache'

And also I can't see the device in "adb devices" in order to sideload the ROM.

boot to bootloader "FastbootUSB" and then fastboot erase cache

you may need to update your adb and fastboot and possibly your drivers once done, enter recovery, main screen only and try adb devices again, if it see's it now then adb push romname.zip /sdcard/
Last edited by Seanie280672; 17th June 2014 at 07:38 PM.

The Following User Says Thank You to Seanie280672 For This Useful Post: [ View ]
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes