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
Related
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
Hi.
Recent I downloaded a custom rom running android revolution 71.0 hd, my phone is rooted and I am running twrp 2.7. I choose to go back to original rom and restore everything my phone is also relocked tampered. I somehow locked it and again relocked and wiped everything, I ran this http://forum.xda-developers.com/showthread.php?t=2626050 rom and installed it, a while later I restart my phone and get "system proccess error" wait or click ok to shut down so the rom was not working. Somehow I am now stuck on the fastboot and cannot do a ****. Tried so hard installing like over 11 different twrp versions and no one of them seems working, only 1 worked from t-mobile, it went in and then I could not move anything, just stuck freez. I really want to do RUU recovery but my phone is S-on and I don't know if you guys know if it works to do a RUU even if the phone is s-on, I can lock the bootloader or keep it like now unlocked that works so far but cannot do anything else like install custom rom or anything else. I will put down my phone specifications down below and also typed "fastboot getvar all" command so you will see all info I can put down and which ruu version do I need and how do I do to install or fix this pls help me guys!!!!
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH36TW902758
(bootloader) imei: 357864056203233
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4289mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
and when I look on my phone (fastboot I see)
M7_UL PVT SHIP S-ON RH
HBOOT 1.55.0000
RADIO 4A.21.3263.04
etc etc
pls help me guys!!!, mike:crying::crying::crying::crying:
Give it to a phone service , they will repair .
Hi,
I got a HTC ONE SV with the following issue.
- When it boots it got stuck into the White HTC screen.. Computer (Win 8.1) recognizes it as unknown device
- When I try the Volume down + Power - it boots in to Fastboot mode
- Computer recognizes via FastBoot.
This is the screen I got. I tried to click bootloader, it keeps going back to the same htc screen. ?
Any help?
*****Locked*****
K2_UL PVT SHIP S-ON RL
HBOOT-2.00.000
eMMC-boot
Mar 14 2013, 22:10:43:-1
--------------
When I issue fastboot getvar all, I got the following.
C:\Android\HTCOneSV>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: 3.11.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXXX
(bootloader) imei: xxxxxxxxxxxxxxxx
(bootloader) product: k2_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PL8010000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3752mV
(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.142s
And what happened before, that it does not boot anymore?
Your phone is still S-on and locked, you maybe might try warranty service first, before you'll do anything else.
old.splatterhand said:
And what happened before, that it does not boot anymore?
Your phone is still S-on and locked, you maybe might try warranty service first, before you'll do anything else.
Click to expand...
Click to collapse
It's out of warranty. The screen was broken and was replaced and this started happening
Ok, i understand. And i can remember we had this case with replaced screen before here in the forum.
At the end we tried all things which are usually working to get the phone back working, but all failed.
I personally think, this is because the replacement screen is not supported by the firmware/drivers.
I have no proof for that, but i really think this is the case, here for you too.
Looks like an expensive paperweight
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!
Hi all.
I have a completely stock never-been-modified HTC One S that has started freezing on boot.
No, I never tried to root it, unlock the bootloader, or any other stuff.
I would like to get my data off it, but because I never rooted it, I can't extract said data using ADB (unless you know a trick that I don't).
My options seem to have come down to flashing something to get it to boot... ROM, kernel, radio, what do you think?
- I can get into Fastboot, Bootloader, Recovery, etc.
- I can ADB to the phone while it is boot-stuck (so probably not the kernel?).
I want to get my info off of it and if I can make it boot all the way in, that's an added bonus.
To that end, have you ever seen a 3.14.531.19 ROM that wasn't wrapped up in an RUU? I was willing to try RUU_Ville_U_JB_45_S_TMOUS_3.14.531.11_Radio_1.13.50.05.31_10.30.50.08L_release_309489_signed_ICS_2 but it says that it'll wipe all my info.
Here's my fastboot getvar all:
(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.19
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT24DW404294
(bootloader) imei: 359902041072822
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3920mV
(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.067s
What say you?
If your phone is bootloader locked, S-ON with original recovery, you're out of luck... The complete boot sequence is secured and if you try to unlock, all data will be wiped off.
The only first step to get to your data would be to root without unlocking the phone, but I can't see how to do that if you can't start the OS.
One thing you can try is to get to the HTC recovery and wipe cache (I think this is possible).
Thanks for the reply.
I have already wiped the cache (forgot to mention that in the OP, sorry) and it didn't make a difference.
It sounds like what I was expecting to hear: My data are beyond recovery... Which is a bummer.
Anyone else have anything to add?
Some miracle cure, maybe?
I'm going to hold off on my attempt to unlock the bootloader another few days in case someone has a suggestion to offer.
A final bump in the hope that someone might have a solution.
Thanks!