Soft Bricked HTC One M7_WLS (Sprint) PLEASE HELP - General Questions and Answers

So I got my HTC one and rooted it immediately and Installed Cyanogenmod 11. I love Cyanogenmod but my SMS and MMS messages were all screwed up. I booted back up from my backup and noticed that It was running Android 4.3, 4.4 is available so I tried to install the update, It failed so I realized this must be because I was rooted so I went about going back to stock HTC Sense. I relocked the bootloader and ran RUU but the program crashed. After that I was only able to get to the fastboot page, recovery would crash. I ran a few different verisons of RUU but each one failed (error 155 being most prevalent). I unlocked my bootloader again and cyanogenmod started to boot up but never got through. I wipe data and cache. CM still won't boot. I reflashed the CWM recovery and tried to load the back up that I had. I get multiple errors about not being able to mount /system, /cache everything. I installed TWRP and tried to do sideload, not working. I have a USB OTG cable and I tried to load files that way, no good. I don't have S-Off and I can't boot into a rom so I can't get S-Off. I've exhausted google, not sure what to do now. Here is a breakdown.
*** Tampered ***
*** Unlocked ***
M7_WLS PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-1.00.20.1108
OpenDSP-v32.120.274.0909
OS-3.05.651.6
eMMC-boot 2048MB
Jan 3 2014,13:35:00.0
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 1.00.20.1108
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.05.651.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA3CHS903191
(bootloader) meid: 99000428862892
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4082mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-35824024
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I've tried flashing a different firmware but I get the error
C:\Users\Administrator\Downloads\fastboot>fastboot flash zip firmware.zip
sending 'zip' (20935 KB)...
OKAY [ 2.090s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 99 unknown fail)
finished. total time: 2.340s
I've tried to run my exact version of RUU, found here.
http://forum.xda-developers.com/showthread.php?t=2576995
The Ruu window won't even open, I've run as administrator, in all sorts of compatibility modes. I've run it on my windows 8 pc, windows 7 pc and from mini-windowsXP. None of them could start.
Like I've said I've exhausted my resources. I appreciate any and all of the help I can get. Thank you!
-Brycery91

I need this to get more attention. Does anyone have any ideas?

Brycery91 said:
I need this to get more attention. Does anyone have any ideas?
Click to expand...
Click to collapse
u can get more attention if u open thread in m7 forums

Remove Thread
Asking a Mod to delete this thread, I have another thread posted elsewhere.
Thanks

Related

[Q] unlock bootloader

I fried my one s a few days ago and just got the replacement. I went to htcdev.com and put in my new identifier token, got my bin, went to flash and got
sending 'unlocktoken' (0 KB)...
OKAY [ 0.142s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.148s
and i thought ok maybe i messed up and used the old. I deleted all the bins, cleared cache on browser, and re-ran fastboot oem get_identier_token
it gave me something different... i thought ok i ****ed up some how, put the new one in to htcdev, got a bin flash, same thing...
i just sat here and spammed get id and its different every single time and none of the bins are working.
it came with hboot 2.15; but i was running this on the last phone (although i was s-off..) i did a quick forum search for "oem get-identifier_token" and didnt really see anything useful..
am i ****ed? whats the way ahead? thanks!
here's some possibly relevant info; this is a straight up latest **** from tmous phone
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.13.50.05.31
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.14.531.17
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT24YW402012
(bootloader) imei: 359902042972202
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3979mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
scratch that, i was trying to do this at work on a windows box; i got home and did it on my linux laptop and it worked fine.. strange.. never tried doing anything in windows before :/
See if your bootloader is unlocked
Sent from my Nexus 7 using Tapatalk HD

[Q] Bricked K2_UL

Hello.
First of all, I am new to Android development. I like to play around with stuff and a friend of mine who is a total noob asked if I could take a look at his HTC One SV. He said that the phone switched off during software update and now the phone is stuck in bootloop.
I spent 2 whole days reading up on what can be done and trying to fix it but right now I am fed up and would appreciate if anyone could help me in any way, especially a walktrough via PMs.
I tried to flash TWRP recovery via fastboot. It flashes, it goes on to the red warning message and goes back to bootloop after a minute. I think I tried every possible TWRP version. I cleared the cache before and after flashing. I flashed multiple times, I ereased cache multiple times with each image.
I am unable to go into recovery. What can I do about it? What am I doing wrong? What can I try? The guy that gave me the phone already made peace with the idea that it will never work again so I am willing to try anything. I would like to start from scratch as I do not know if anyone played with it before me.
*** TAMPERED ***
*** UNLOCKED ***
K2_UL PVT SHIP S-ON RL
HBOTT-2.00.0000
RADIO-1.15.40a.00.07
OpenDSP-v9.2.0268.1214
eMMC-boot
Apr 12 2013, 01:55:41:-1
>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0000
(bootloader) version-baseband: 1.15.40a.00.07
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.15.118.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxx
(bootloader) imei: xxx
(bootloader) product: k2_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PL8010000
(bootloader) cidnum: T-MOB009
(bootloader) battery-status: low
(bootloader) battery-voltage: 3453mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.077s
You can't restore your boot.img through TWRP because you are S-On. Would require Dumlock to do this.
You need to rename boot.emmc.win to boot.img and flash it via fastboot after restoring your device using a twrp backup.
Same concept as flashing a Rom.
Sent from my C525c using Tapatalk

[Q] Can't flash stock ROM

So that's my story cut short:
I was and is S-On
I had HBoot v1.13, upgraded it by RUU flashing firmware.zip from OTA_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_1.11.50.05.28_10.27.50.08L_release_301852xf01hejl416oev96.zip
Now I have HBoot 2.15 and TeamWin Recovery 2.8 .
ZenROM flashes with no problem, but that's still no stock, as the signature of /system is broken.
But in order to get S-Off, which is necessary at least to gain hboot 2.16 for Liberty ROM, I need to get stock ROM.
This is necessary in order for phone to boot with bootloader locked(signature should validate), which is a prereq for Faceplam S-Off(as I understand)
But every RUU I flash says:
Code:
sending 'zip' (534178 KB)...
OKAY [ 21.050s]
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...
FAILED (remote: 44 hboot version check fail)
finished. total time: 73.893s
And every OTA I try to install in TWRP says I have a CID mismatch , no matter leave I my original (HTC_A07) or SuperCID
Help anyone?
That's my config. I deliberately downed main version, because otherwise during RUU flash I got "invalid main version" instead
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.11.50.05.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.00.000.0
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT23XW411592
(bootloader) imei: *****************
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: HTC__A07
(bootloader) battery-status: good
(bootloader) battery-voltage: 4203mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.065s
Actually you don't need a stock rom. As far as I know you only need a sense rom. I S-OFFed while I had this rom installed.
Flippy498 said:
Actually you don't need a stock rom. As far as I know you only need a sense rom. I S-OFFed while I had this rom installed.
Click to expand...
Click to collapse
Which S-Off did you use? Rumrunner and firewater didn't work for me
I used facepalm. I know a lot of people here say that it won't work on hboot 2.15 but for me it did work. Don't know why...
Flippy498 said:
I used facepalm. I know a lot of people here say that it won't work on hboot 2.15 but for me it did work. Don't know why...
Click to expand...
Click to collapse
But with facepalm you need to flash PJ4010000.zip (or whatsitsname) in RUU mode(mean you should relock) and when it says "Error: 92 supercid blablablah" you should boot immediately, right?
And you're still with locked bootloader.
And on custom ROM, which means on boot the signature will be checked AND will fail, so it won't boot at all - that's what happens to me...
Tell me I'm wrong, cause otherwise I can't s-off neither I can flash stock...
Well, I SOFFed more than one and a half year ago. But as far as I remember you don't need to relock since you don't want to run a RUU.
Just looked it up. The instructions in the facepalm thread do not mention that you need to relock. Try again to S-OFF without relocking.

[Completed] [Q] Phone system folder wiped after failed cyanogenmod install

Alright, this is yet another wiped OS for an HTC ONE M7. I have spent DAYS trying to figure out a solution to this, but nothing has worked... Probably because I don't even know what the next step is.
BOOTLOAD SCREEN **
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.28.3218.04
OpenDSP-v32.128.274.0909
OS-6.10.531.9
eMMC-boot 2048 MB
(todays date)
I have tried fastboot flashing the zip files for the OS and it shows this in command prompt.
C:\Users\JamesM\Desktop\adbfastboot\adbfastboot>fastboot flash zip OS.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1221704 KB)...
OKAY [ 44.790s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 44.853s
Basically, the phone was rooted and unlocked and I was installing cyanogenmod on it which failed and I deleted the system folder instead of doing a factory reset on it. It does not get past the HTC screen and I have attempted to flash zip files after attempting relocking and rebootRUU, which have all failed.. I have also tried the .exe RUU files. I am also feeling like there is a definite driver issue, since my computer used to show My HTC in the device manager and now it shows it in "other devices" as "One" and seems to be showing up as a disc drive. There honestly is not much that I can think of at the moment that I have not tried to get this going, youtube videos, hours of looking for similar issues, messing with things on my own to see if there is ANYTHING to do and nothing has worked. I am assuming that it has something to do with it being S-ON, but I have tried to change that with revone and it wouldn't flash through USB. Everything is wiped, but I have my bootloader and recovery... there has to be a way back from here..
This is my fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.10.531.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA39HW907463
(bootloader) imei: 355972057571995
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4328mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(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.069s
Seriously though, if anyone can help me with this that would be amazing. If there is any information needed, I will be around to update. I have installed CWM recovery v6.0.4.3 and also have TWRP v2.6.3.0.
SIDE NOTE*
I don't expect someone to spend a tremendous amount of time spelling things out for me, but if someone could give me a starting point... Like (Oh, it's probably drivers.. Or incorrect RUU)
Thanks again!
JamesM1027 said:
Alright, this is yet another wiped OS for an HTC ONE M7. I have spent DAYS trying to figure out a solution to this, but nothing has worked... Probably because I don't even know what the next step is.
BOOTLOAD SCREEN **
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.28.3218.04
OpenDSP-v32.128.274.0909
OS-6.10.531.9
eMMC-boot 2048 MB
(todays date)
I have tried fastboot flashing the zip files for the OS and it shows this in command prompt.
C:\Users\JamesM\Desktop\adbfastboot\adbfastboot>fastboot flash zip OS.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1221704 KB)...
OKAY [ 44.790s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 44.853s
Basically, the phone was rooted and unlocked and I was installing cyanogenmod on it which failed and I deleted the system folder instead of doing a factory reset on it. It does not get past the HTC screen and I have attempted to flash zip files after attempting relocking and rebootRUU, which have all failed.. I have also tried the .exe RUU files. I am also feeling like there is a definite driver issue, since my computer used to show My HTC in the device manager and now it shows it in "other devices" as "One" and seems to be showing up as a disc drive. There honestly is not much that I can think of at the moment that I have not tried to get this going, youtube videos, hours of looking for similar issues, messing with things on my own to see if there is ANYTHING to do and nothing has worked. I am assuming that it has something to do with it being S-ON, but I have tried to change that with revone and it wouldn't flash through USB. Everything is wiped, but I have my bootloader and recovery... there has to be a way back from here..
This is my fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.10.531.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA39HW907463
(bootloader) imei: 355972057571995
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4328mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(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.069s
Seriously though, if anyone can help me with this that would be amazing. If there is any information needed, I will be around to update. I have installed CWM recovery v6.0.4.3 and also have TWRP v2.6.3.0.
Click to expand...
Click to collapse
Hi,
Here a dedicated help thread in your device section that you can ask about your issue in,
http://forum.xda-developers.com/showthread.php?t=2180425
Good luck!

'(Remote: image update error)'

please help me anybody!
the run 'fastboot flash recovery recovery.img' after
"....writing 'recovery'...
FAILED (remote: image update error)"
is there any solution for this problem?
htc one sv, unlocked, k2_ul, HBOOT- 2.21.000 S-ON
Whats wrong, what are you going to do?
What recovery version, what software, phone working or dead?
Wrong download, the whole error message could help too?
Sure that file ending is not hidden in windows (recovery.img.img)
Not much information...
phone is dead, because the battery full empty , after turn-on the phone dont run the twrp, or android, just a white screen, and dont work it.
the screen is:
UNLOCKED
K2_UL XA SHIP S-ON RL
HBOOT-2.21.000
OS-
eMMC-boot 1024MB
Nov 7 2013, 15:32:31.0
FASTBOOT USB (red)
VOL UP
VOL DOWN
POWER
BOOTLOADER
REBBOT
REBOOT BOOTLOADER
POWER DOWN
i try to bootloader-recovery menu, but dont work it, and try to fastboot recovery.img from (http://forum.xda-developers.com/htc-one-sv/orig-development/recovery-twrp-touch-recovery-t3152555)
and fastboot this error message:
d:\1>fastboot flash recovery TWRP_2871_Recovery.img
< waiting for device >
sending 'recovery' (11516 KB)...
(bootloader) start check_usb: usb_ep0: type=128, request=6
OKAY [ 6.977s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 7.211s
d:\1>
any tips? any hope, data in storage is save?
what i can do?
K2_UL XA...? What region are you from? Whats your Cid?
Output from " fastboot getvar all "?
I don't think you will get your data back! You did unlock the bootloader, don't you? In this case data gets wiped.
old.splatterhand said:
K2_UL XA...? What region are you from? Whats your Cid?
Output from " fastboot getvar all "?
I don't think you will get your data back! You did unlock the bootloader, don't you? In this case data gets wiped.
Click to expand...
Click to collapse
thank you for you answer!
K2_UL XA SHIP S-ON RL
europe region
after 'fastboot oem readcid'
"d:\priv\---HTC---\adb>fastboot oem readcid
...
(bootloader) cid: ORANG001
OKAY [ 0.013s]
finished. total time: 0.013s"
after 'fastboot getvar all'
d:\priv\---HTC---\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.21.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: XA SHIP S-ON
(bootloader) serialno: 123456789012
(bootloader) imei: 352803050972026
(bootloader) meid:
(bootloader) product: k2_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PL8010***
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4290mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2bb255c2
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.120s
yes, bootloader is work (i hope we thing same thing) ('fastboot-recovery-factory reset-clear storage-simlock-show barcode' menu)
next step? :crying
I assume you need a RUU or firmware package matching to your device/CID/MID which i don't have (ORANG001/PL8010000).
Would be all not so difficult, if you made your device S-off after the last "brick".
You also can try to use a toolkit like this, with support for your device. Maybe this is able to flash the recovery.
old.splatterhand said:
I assume you need a RUU or firmware package matching to your device/CID/MID which i don't have (ORANG001/PL8010000).
Would be all not so difficult, if you made your device S-off after the last "brick".
You also can try to use a toolkit like this, with support for your device. Maybe this is able to flash the recovery.
Click to expand...
Click to collapse
thanks a lot... i try...
unfortunately the windroid universal not working...
unlock bootloader (step 1)---> ok (no error message)
flash recovery (step2) ---> ok (no error message)
flash supersu (step 3) --- > NO DEVICE FOUND (Please ensure tha that USB Debugging is enable (but the android dont run this device ) your device is plugged correctly, and you correctly installed the ADB Drivers. If this is a persistent issue, please reply in the XDA thread
the past succeeded the new RUU and flash recovery. (http://forum.xda-developers.com/htc-one-sv/help/htc-one-sv-help-t3034790 ), but now dont see the device in 'my computer'
and just s-on 'mode' at the present. is there a method, which is there is S-OFF?
any idea?
Hi,
i figured I should join this thread since I have the same phone, same region (even the same carrier) & same problem here. For a little context my One SV was rooted (unlocked bootloader, installed CWM recovery and superuser), nothing more, no custom rom or anything like that. I was running stock 4.1.2, worked fine for 6 months after getting root access, then out of the blue, I get stuck on Fastboot/Bootloader just like OP. Recovery and factory reset don't do anything, just loop back to fastboot. I have fastboot usb working, but no adb connection apparently (adb devices is empty).
***unlocked***
K2_UL XA SHIP S-ON RL
HBOOT - 2.00
eMMC-boot
jun 13 2013
Output from " fastboot getvar all "?
Click to expand...
Click to collapse
c:\>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: XA SHIP S-ON
(bootloader) serialno: 123456789012 <== see i'm gonna leave this here because i have the same as you sanka01, isnt that weird ?
(bootloader) imei:
(bootloader) product: k2_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PL8010***
(bootloader) cidnum: ORANG202
(bootloader) battery-status: good
(bootloader) battery-voltage: 3706mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.078s
c:\>fastboot getvar commitno-bootloader
commitno-bootloader: dirty-15afa7fc67c51747c2eaca17ce1ac7846d555b6a
c:\>fastboot getvar hbootpreupdate
hbootpreupdate: 11
c:\>fastboot getvar gencheckpt
gencheckpt: 0
i've tried windroid universal, it says "success" at flashing recovery but after that, recovery still can't be entered. as u can see i'm S-ON, can't change CID or anything.... can u get s-off on a bricked phone ? I have found a super old stock ICS ruu but I can't figure how to install it.... and even after that I would need someone to walk me through the steps of getting back to 4.1.2 cause I'm a huge noob
so, I'm very interested in the resolution of your problem. any help appreciated.
ononyn0us said:
Hi,
i figured I should join this thread since I have the same phone, same region (even the same carrier) & same problem here. For a little context my One SV was rooted (unlocked bootloader, installed CWM recovery and superuser), nothing more, no custom rom or anything like that. I was running stock 4.1.2, worked fine for 6 months after getting root access, then out of the blue, I get stuck on Fastboot/Bootloader just like OP. Recovery and factory reset don't do anything, just loop back to fastboot. I have fastboot usb working, but no adb connection apparently (adb devices is empty).
***unlocked***
K2_UL XA SHIP S-ON RL
HBOOT - 2.00
eMMC-boot
jun 13 2013
c:\>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: XA SHIP S-ON
(bootloader) serialno: 123456789012 <== see i'm gonna leave this here because i have the same as you sanka01, isnt that weird ?
(bootloader) imei:
(bootloader) product: k2_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PL8010***
(bootloader) cidnum: ORANG202
(bootloader) battery-status: good
(bootloader) battery-voltage: 3706mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.078s
c:\>fastboot getvar commitno-bootloader
commitno-bootloader: dirty-15afa7fc67c51747c2eaca17ce1ac7846d555b6a
c:\>fastboot getvar hbootpreupdate
hbootpreupdate: 11
c:\>fastboot getvar gencheckpt
gencheckpt: 0
i've tried windroid universal, it says "success" at flashing recovery but after that, recovery still can't be entered. as u can see i'm S-ON, can't change CID or anything.... can u get s-off on a bricked phone ? I have found a super old stock ICS ruu but I can't figure how to install it.... and even after that I would need someone to walk me through the steps of getting back to 4.1.2 cause I'm a huge noob
so, I'm very interested in the resolution of your problem. any help appreciated.
Click to expand...
Click to collapse
i have a same program buddy my phone is running few month, after the root, and after dead. the seral number, is so weird... but my phone cidnum was t-mobile first root...
and any recovery or boot. img not working, because the reply is: "image update error"
do you have an idea? or any solution? anybody? somewhere? or phone throw to the trash?

Categories

Resources