Related
Hi all
I use HTC One X, but bought some time ago HTC One S, it worked fine for some time, but yesterday restarted and from that point I could not get it back neither to recovery nor ROM anymore. Phone bootloops and I can only get to fastboot.
I've unlocked the bootloader (*** UNLOCKED *** shows on top when in fastboot) and fastboot getvar all returns:
(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: 3.16.666.9
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT24AW408183
(bootloader) imei: 352103050022322
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3695mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
When I flash recovery (fastboot flash recovery recovery.img and recovery.img is from here (http://forum.xda-developers.com/showthread.php?t=2528113 under Recovery HBOOT 2.15 Users Only ClockworkMod 6.0.4.5), it does flash ok
sending 'recovery' (8106 KB)..
OKAY [ 1.079s]
writing 'recovery'...
OKAY [ 1.856s]
finished. total time: 2.943s
but I still cannot get into recovery (phone restarts to screen with red text (for dev only...) and then restarts and bootloops.
Can anybody please help me with this?
Thanks
I suggest reflashing kernel.
Wysłane z mojego HTC One S przy użyciu Tapatalka
jaco_lbn said:
I suggest reflashing kernel.
Wysłane z mojego HTC One S przy użyciu Tapatalka
Click to expand...
Click to collapse
Thanks, but I even cannot get into recovery
velvel said:
Thanks, but I even cannot get into recovery
Click to expand...
Click to collapse
Hm, really strange behavior, had couple of HTC phones but never seen something like this happening.
I did run RUU (first changed cid and relocked), everything went fine (no errors), but still cannot boot. My experience so far was that if RUU runs fine, you should boot without problem. Thinking more and more that there is some hardware problem, that is causing phone to bootloop.
If anyone has any idea, I would appreciate it a lot.
Thanks
Build me a scenario
velvel said:
Hm, really strange behavior, had couple of HTC phones but never seen something like this happening.
I did run RUU (first changed cid and relocked), everything went fine (no errors), but still cannot boot. My experience so far was that if RUU runs fine, you should boot without problem. Thinking more and more that there is some hardware problem, that is causing phone to bootloop.
If anyone has any idea, I would appreciate it a lot.
Thanks
Click to expand...
Click to collapse
According to your first post, everything seems to be okay. Your drivers are seeing the phone, and the phone is recognizing its hardware.
Which recoveries did you try to flash? (TWRP, CWM)
And which version?
Have you tried to reroot the device and flash a recovery again since running the RUU?
From my experience with running an RUU, you should be able to boot right away. What were the steps you took (in order) before you ran the RUU?
Sorry for all the questions, trying to establish a scenario.
[EDIT] Also, I see that you got the initial recovery from the CM11 ROM page. You didn't happen to flash a ROM that is meant for HBOOT 2.16 did you? I sure hope not. That could be a possibility as to why you can not boot anything.
42freelancer said:
Which recoveries did you try to flash? (TWRP, CWM)
Click to expand...
Click to collapse
I've tried both. fastboot flash recovery imgname would work fine, but I would again finish in bootloop after restart.
And which version?
Click to expand...
Click to collapse
TWRP_2.6.1.0_ville_4.2.2 and latest CWM
Have you tried to reroot the device and flash a recovery again since running the RUU?
Click to expand...
Click to collapse
You mean reunlock, not reroot, right? I've done reunlock so I could flash recovery.
From my experience with running an RUU, you should be able to boot right away. What were the steps you took (in order) before you ran the RUU?
Click to expand...
Click to collapse
I would run:
fastboot erase cache
fastboot reboot-bootloader
and then start RUU.
Sorry for all the questions, trying to establish a scenario.
Click to expand...
Click to collapse
You are welcome and thanks for the help.
[EDIT] Also, I see that you got the initial recovery from the CM11 ROM page. You didn't happen to flash a ROM that is meant for HBOOT 2.16 did you? I sure hope not. That could be a possibility as to why you can not boot anything.
Click to expand...
Click to collapse
No, 2.15 all the time...
velvel said:
I've tried both. fastboot flash recovery imgname would work fine, but I would again finish in bootloop after restart.
TWRP_2.6.1.0_ville_4.2.2 and latest CWM
You mean reunlock, not reroot, right? I've done reunlock so I could flash recovery.
I would run:
fastboot erase cache
fastboot reboot-bootloader
and then start RUU.
You are welcome and thanks for the help.
No, 2.15 all the time...
Click to expand...
Click to collapse
Try getting into bootloader and pushing the kernel this way: fastboot flash boot boot.img
you don't have to be in recovery for this. The phone is s-on right?
[edit] actually your security says it's off.
42freelancer said:
Try getting into bootloader and pushing the kernel this way: fastboot flash boot boot.img
you don't have to be in recovery for this.
Click to expand...
Click to collapse
No, it didn't work, this is something more serious
I've basically tried all I could think of, from doing RUUs (3 of them), flashing boot and recovery images, going 2.15, 2.16, locking/unlocking (obviously) and finally going S-On (ok, might be stupid, but I run out of ideas).
Bottom line is that all of the flashing worked for me, I get no error, but even simple fastboot boot recovery.img brings back the bootloop.
For example:
>fastboot flash recovery openrecovery-twrp-2.6.3.0-ville-selinux.img
sending 'recovery' (8668 KB)...
OKAY [ 1.108s]
writing 'recovery'...
OKAY [ 2.059s]
finished. total time: 3.173s
>fastboot reboot
and if I hold Vol- and select recovery in bootloader I am back to bootloop.
Same thing if I try:
>fastboot boot openrecovery-twrp-2.6.3.0-ville-selinux.img
I just do not understand why I am not getting any error message when flushing and is it possible that there is something wrong with the hardware that causes this behavior...
velvel said:
No, it didn't work, this is something more serious
I've basically tried all I could think of, from doing RUUs (3 of them), flashing boot and recovery images, going 2.15, 2.16, locking/unlocking (obviously) and finally going S-On (ok, might be stupid, but I run out of ideas).
Bottom line is that all of the flashing worked for me, I get no error, but even simple fastboot boot recovery.img brings back the bootloop.
For example:
>fastboot flash recovery openrecovery-twrp-2.6.3.0-ville-selinux.img
sending 'recovery' (8668 KB)...
OKAY [ 1.108s]
writing 'recovery'...
OKAY [ 2.059s]
finished. total time: 3.173s
>fastboot reboot
and if I hold Vol- and select recovery in bootloader I am back to bootloop.
Same thing if I try:
>fastboot boot openrecovery-twrp-2.6.3.0-ville-selinux.img
I just do not understand why I am not getting any error message when flushing and is it possible that there is something wrong with the hardware that causes this behavior...
Click to expand...
Click to collapse
Sounds like you have a soft brick on your hands.
Can you boot the device at all, stock or custom ROM?
Maybe reverting to COMPLETE STOCK and starting over fresh will help?
What was the last thing you did right before you got stuck?
42freelancer said:
Sounds like you have a soft brick on your hands.
Can you boot the device at all, stock or custom ROM?
Maybe reverting to COMPLETE STOCK and starting over fresh will help?
What was the last thing you did right before you got stuck?
Click to expand...
Click to collapse
No, I cannot boot, after RUU that runs fine, phone still bootloops and only thing I can do is go into bootloader.
When you say COMPLETE STOCK, you mean RUU, right?
I was talking on the phone and phone restarted. After that I was able to boot after many tries, after restart, could not boot and than tried RUU etc...
velvel said:
No, I cannot boot, after RUU that runs fine, phone still bootloops and only thing I can do is go into bootloader.
When you say COMPLETE STOCK, you mean RUU, right?
I was talking on the phone and phone restarted. After that I was able to boot after many tries, after restart, could not boot and than tried RUU etc...
Click to expand...
Click to collapse
And here we are. Do you happen to have the old All In One Kit that became obsolete, by hasoon2000? It has the function to flash your recovery back to stock. I found two mirrors on the internet, but because of the rules, I can't post them. But they are accessible through the internets if you use the right keywords.
42freelancer said:
And here we are. Do you happen to have the old All In One Kit that became obsolete? It has the function to flash your recovery back to stock. It's probably floating around the internet somewhere. If you don't I can try to find it.
Click to expand...
Click to collapse
Tried that too, no luck. Looks like I am getting a new paperweight
velvel said:
Tried that too, no luck. Looks like I am getting a new paperweight
Click to expand...
Click to collapse
If you haven't lost all hope, try reading through this and (Return to Stock - http://forum.xda-developers.com/showthread.php?t=2164783) see if you missed anything?
You seem pretty savvy in your HTC ONE S know-how. But it's always good to follow someone else's tutorial just for guidance.
Seems issue with Recovery, bootloop is normal
velvel said:
Hi all
I use HTC One X, but bought some time ago HTC One S, it worked fine for some time, but yesterday restarted and from that point I could not get it back neither to recovery nor ROM anymore. Phone bootloops and I can only get to fastboot.
I've unlocked the bootloader (*** UNLOCKED *** shows on top when in fastboot) and fastboot getvar all returns:
(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: 3.16.666.9
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT24AW408183
(bootloader) imei: 352103050022322
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3695mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
When I flash recovery (fastboot flash recovery recovery.img and recovery.img is from here (http://forum.xda-developers.com/showthread.php?t=2528113 under Recovery HBOOT 2.15 Users Only ClockworkMod 6.0.4.5), it does flash ok
sending 'recovery' (8106 KB)..
OKAY [ 1.079s]
writing 'recovery'...
OKAY [ 1.856s]
finished. total time: 2.943s
but I still cannot get into recovery (phone restarts to screen with red text (for dev only...) and then restarts and bootloops.
Can anybody please help me with this?
Thanks
Click to expand...
Click to collapse
Hi,
Bootloop is normal for ROM geeks.
In your case, it seems your phone has issue with version of Recovery. I had this issue too and found correct Recovery @ http://techerrata.com/browse/twrp2/ville ....
You can give a try..:fingers-crossed::fingers-crossed::fingers-crossed:
velvel said:
Hi all
I use HTC One X, but bought some time ago HTC One S, it worked fine for some time, but yesterday restarted and from that point I could not get it back neither to recovery nor ROM anymore. Phone bootloops and I can only get to fastboot.
I've unlocked the bootloader (*** UNLOCKED *** shows on top when in fastboot) and fastboot getvar all returns:
(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: 3.16.666.9
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT24AW408183
(bootloader) imei: 352103050022322
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3695mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
When I flash recovery (fastboot flash recovery recovery.img and recovery.img is from here (http://forum.xda-developers.com/showthread.php?t=2528113 under Recovery HBOOT 2.15 Users Only ClockworkMod 6.0.4.5), it does flash ok
sending 'recovery' (8106 KB)..
OKAY [ 1.079s]
writing 'recovery'...
OKAY [ 1.856s]
finished. total time: 2.943s
but I still cannot get into recovery (phone restarts to screen with red text (for dev only...) and then restarts and bootloops.
Can anybody please help me with this?
Thanks
Click to expand...
Click to collapse
Did you check the fast boot option in the powermenue under settings? If its check it will happen like ur problem.
velvel said:
No, I cannot boot, after RUU that runs fine, phone still bootloops and only thing I can do is go into bootloader.
When you say COMPLETE STOCK, you mean RUU, right?
I was talking on the phone and phone restarted. After that I was able to boot after many tries, after restart, could not boot and than tried RUU etc...
Click to expand...
Click to collapse
Have you tried this? :
--> flash STOCK recovery via fastboot or toolkit
--> Boot to bootloader --> Factory Reset(Userdata) / Clear Stotage (SD-card) (these commands only work with STOCK recovery)
Before I got the same problem, so in Bootloader I did Factory Reset and then flash the Recovery TWRP 2.6.3.0. Now it works
Hello! Before you guys flame me with messages of how much dumb I am or anything similar - don't bother, i already know it and i regret it...
So... I have AT&T HTC One X, with Hboot 2.14, CID CWS__01 which i just destroyed as much as i could >.> Let me reproduce things i've tried..
First of i changed my CID to 11111111 and unlocked the bootloader - took me an hour, but i did it and it was working...
I've installed recovery, even rooted the ROM... But that wasn't enough - i wanted to install ParanoidAndroid ( and i didn't read that it needs S-OFF, realized that just after i installed it and rebooted the phone )..
So after a reboot, the white HTC logo it just went black screen and nothing else... So i've began to look up on forums if someone else had this kind of a problem...
Then i tried another 2 ROM's, which worked as well as PA - just black screen...
So i thought - maybe i'll do everything from scratch ? Why not, I changed CID back to stock, wiped everything etc. and locked the bootloader....
But now I've got a weird problem - i can't change CID with "fastboot oem writecid" - it returned me error
(bootloader) elite_init_sd, SD card already power on
(bootloader) sdhw_7xxx_open: id=0
(bootloader) [SD_HW_ERR] SD: No device attached
(bootloader) 902910 902E20
FAILED (status read failed (No such file or directory))
finished. total time: 1.282s
Click to expand...
Click to collapse
So now i have no access to recovery, so i can't even do anything to the storage, the phone doesn't boot up, tried RUU for ATT version ( RUU_Evita_UL_ATT_US_1.44.502.1_Radio_0.15.3201.09_release_249105 - i guess its for HBoot 1.44, not 2.14 >.> ) it just showed me an error that it couldn't send data to the phone and i should check my connection to the phone ( drivers are installed and working fine )
I've also tried fastbooting the OTA zip to the phone - well, the phone is on S-ON and it just declines any zip that i try to flash
Also i lost connection to ADB - its impossible to connect to it while phone is in bootloader, right? : /
So i'm left with empty phone without any rom, recovery - anything...
Is there any way of fixing it ? Its 5th hour where i just sit and try to look up for any information, but I just can't find anything...
I guess i just hard bricked the phone and i can try to play some volleyball with it >.>
Your mistake was thinking that you needed s-off to flash the ROM(s), you don't, all you needed to do was flash the boot.img via fastboot after flashing the ROM with your recovery. There's an Evita FAQ thread which contains this information stickied at the top of the q&a section you've posted this thread in . This is in no way intended to flame you, just show you the catalyst point for this mayhem.
Anyway, what is your current CID? Check it with this command:
Code:
fastboot oem readcid
You must be connected in fastboot mode (bootloader) in order for fastboot commands to work (and in answer to your question, no, adb does not work in fastboot mode, only in Android and in recovery).
Transmitted via Bacon
thanks for Your reply : )
My current CID is CWS__001. Im posting the whole information from fastboot
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.14.0000
(bootloader) version-baseband: 0.24p.32.09.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT28GW304238
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: low
(bootloader) battery-voltage: 3403mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-97c9a06e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.094s
Click to expand...
Click to collapse
I should mention that the battery was at ~95% at the time i was trying to flash/do anything.
So, is there any way to make at least recovery working? As for now i flash recovery using fastboot flash, but that does nothing - it says that its done, but when i get into bootloader and check recovery then enter it, it goes to white htc logo and goes back to bootloader >.>
EDIT!!!!!
I managed to get it working! I downloaded RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial which worked flawlessly and stock ROM just booted up! Jesus christ, thank You internet for providing exact links to the RUU's etc >.> I guess i'll try to not brick the phone again ^^ Thanks for the reply again : )
Topic can be closed now : )
prechcik said:
thanks for Your reply : )
My current CID is CWS__001. Im posting the whole information from fastboot
I should mention that the battery was at ~95% at the time i was trying to flash/do anything.
So, is there any way to make at least recovery working? As for now i flash recovery using fastboot flash, but that does nothing - it says that its done, but when i get into bootloader and check recovery then enter it, it goes to white htc logo and goes back to bootloader >.>
EDIT!!!!!
I managed to get it working! I downloaded RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial which worked flawlessly and stock ROM just booted up! Jesus christ, thank You internet for providing exact links to the RUU's etc >.> I guess i'll try to not brick the phone again ^^ Thanks for the reply again : )
Topic can be closed now : )
Click to expand...
Click to collapse
Glad to see you're all working now. But you need to edit your IMEI out of your post asap, never post your IMEI publicly.
Transmitted via Bacon
My power button quit working, I'm within the 1 year warranty period, and I need to go back to stock after I get my replacement.
Before I call VZW, since I'm rooted and using nV ROM, and I know they ask about the Software, does anyone have a screen shot of the Stock Software screen, Kit Kat unless LP has been pushed?
Thanks!
Sent from my HTC6525LVW using XDA Premium 4 mobile app
EvoNotion said:
My power button quit working, I'm within the 1 year warranty period, and I need to go back to stock after I get my replacement.
Before I call VZW, since I'm rooted and using nV ROM, and I know they ask about the Software, does anyone have a screen shot of the Stock Software screen, Kit Kat unless LP has been pushed?
Thanks!
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
They can see more information than you can tell them. Best bet is to be stock during that call.
Thanks for that input.
So, since the new phone arrived, I've been trying to restore my old phone to stock, S-OF, Unroot and Locked boot loader, etc.
I'm able to ADB into fastboot, however for whatever reason I cannot load the 06BIMG.zip(not at my computer)
Fastboot simply reboots immediately when I adb reboot boatloader.
Is there another way to get a stock image on the phone, remove the red text at boot up, s-off, lock boot loader with stock recovery and unroot?
Everything I've tried seems to be hinged on that fastboot rebooting issue.
Thanks
Sent from my HTC6525LVW using XDA Premium 4 mobile app
EvoNotion said:
Thanks for that input.
So, since the new phone arrived, I've been trying to restore my old phone to stock, S-OF, Unroot and Locked boot loader, etc.
I'm able to ADB into fastboot, however for whatever reason I cannot load the 06BIMG.zip(not at my computer)
Fastboot simply reboots immediately when I adb reboot boatloader.
Is there another way to get a stock image on the phone, remove the red text at boot up, s-off, lock boot loader with stock recovery and unroot?
Everything I've tried seems to be hinged on that fastboot rebooting issue.
Thanks
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
0P6BIMG.zip ?
I typed it from my phone whilst I was enjoying the evening outside. Just the only numbers in my head.
I'm downloading your RUU exe right now Dottat. Didn't realize you're local by an hour to me.
thanks!
dottat said:
0P6BIMG.zip ?
Click to expand...
Click to collapse
So I downloaded your EXE, and I get a failure in regard that it reboots to the HTC logo and the phone reboots immediately, causing the program to fail.
Error 155: unknown error
This is the same problem i was having when trying to do the fastboot push of the RUU I had downloaded previously.
Image version is 1.54.401.10
What ever can i do?
EvoNotion said:
So I downloaded your EXE, and I get a failure in regard that it reboots to the HTC logo and the phone reboots immediately, causing the program to fail.
This is the same problem i was having when trying to do the fastboot push of the RUU I had downloaded previously.
Image version is 1.54.401.10
What ever can i do?
Click to expand...
Click to collapse
Try flashing official stock vzw firmware via SD card. Are your mid and cid stock?
401 isn't vzw firmware BTW
dottat said:
0P6BIMG.zip ?
Click to expand...
Click to collapse
dottat said:
Try flashing official stock vzw firmware via SD card. Are your mid and cid stock?
401 isn't vzw firmware BTW
Click to expand...
Click to collapse
I just remember last year downloading and installing the nV Rom which was 4.4.2. and updating the radios.
I've tried the 0p6bimg.zip method in fastboot, but it fails as well. Maybe I'm doing it wrong, but it's in the root of the SD card.
EvoNotion said:
I just remember last year downloading and installing the nV Rom which was 4.4.2. and updating the radios.
I've tried the 0p6bimg.zip method in fastboot, but it fails as well. Maybe I'm doing it wrong, but it's in the root of the SD card.
Click to expand...
Click to collapse
I can do a team viewer session with you this weekend to take a look with you if you want
dottat said:
I can do a team viewer session with you this weekend to take a look with you if you want
Click to expand...
Click to collapse
That would be tits man. I'll be in Dover tomorrow night if you want to check it out live....LMK
EvoNotion said:
That would be tits man. I'll be in Dover tomorrow night if you want to check it out live....LMK
Click to expand...
Click to collapse
Depends on what time...lol. I work in Lancaster during the week a lot.
dottat said:
Depends on what time...lol. I work in Lancaster during the week a lot.
Click to expand...
Click to collapse
You tell me, I'll probably get out of work around 3pm and head down to York. I have to pick up tools from a friend that's borrowing them for work around 5/530, so whenever.
Since the PWR buttons not working, I'm not able to select HBOOT at the bootloader screen, and the commands I was using to get the HTC black screen fail to push. However, I just renamed your ZIP file and will try again and report back
EvoNotion said:
You tell me, I'll probably get out of work around 3pm and head down to York. I have to pick up tools from a friend that's borrowing them for work around 5/530, so whenever.
Since the PWR buttons not working, I'm not able to select HBOOT at the bootloader screen, and the commands I was using to get the HTC black screen fail to push. However, I just renamed your ZIP file and will try again and report back
Click to expand...
Click to collapse
BTW...from a booted ROM the command adb reboot oem-78
Will land you in ruu mode.
dottat said:
BTW...from a booted ROM the command adb reboot oem-78
Will land you in ruu mode.
Click to expand...
Click to collapse
well now, learn something new everyday. Got me to the HTC screen, and then it rebooted though.
EvoNotion said:
well now, learn something new everyday. Got me to the HTC screen, and then it rebooted though.
Click to expand...
Click to collapse
Can you adb reboot-bootloader and get a fastboot getvar all.
X out your imei and sn
dottat said:
Can you adb reboot-bootloader and get a fastboot getvar all.
X out your imei and sn
Click to expand...
Click to collapse
C:\Users\Abraham\Documents>adb kill-server
C:\Users\Abraham\Documents>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Users\Abraham\Documents>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.027s]
finished. total time: 0.037s
C:\Users\Abraham\Documents>fastboot flash zip 0P6BIMG.zip
target reported max download size of 1826418688 bytes
sending 'zip' (1726320 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 8.723s
C:\Users\Abraham\Documents>adb reboot bootloader
C:\Users\Abraham\Documents>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.0926
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.1700.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXX
(bootloader) imei: XXXXX
(bootloader) imei2: Not Support
(bootloader) meid: 99000429333087
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.141s
C:\Users\Abraham\Documents>
EvoNotion said:
C:\Users\Abraham\Documents>adb kill-server
C:\Users\Abraham\Documents>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Users\Abraham\Documents>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.027s]
finished. total time: 0.037s
C:\Users\Abraham\Documents>fastboot flash zip 0P6BIMG.zip
target reported max download size of 1826418688 bytes
sending 'zip' (1726320 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 8.723s
C:\Users\Abraham\Documents>adb reboot bootloader
C:\Users\Abraham\Documents>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.0926
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.1700.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXX
(bootloader) imei: XXXXX
(bootloader) imei2: Not Support
(bootloader) meid: 99000429333087
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.141s
C:\Users\Abraham\Documents>
Click to expand...
Click to collapse
Try flashing this zip the same exact way...
https://www.androidfilehost.com/?fid=95916177934537898
dottat said:
Try flashing this zip the same exact way...
https://www.androidfilehost.com/?fid=95916177934537898
Click to expand...
Click to collapse
Should I rename it to something?
EvoNotion said:
Should I rename it to something?
Click to expand...
Click to collapse
Should not need to
dottat said:
Try flashing this zip the same exact way...
https://www.androidfilehost.com/?fid=95916177934537898
Click to expand...
Click to collapse
Got half way through and now I'm at the four exclamation marks on the corners
Trying to restore my wife's U11 to stock in preparation for Pie. It the US Unlocked version. Every RUU I have tried from here https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit#gid=0 gives me an error. The bootloader is relocked and I have tried both vanilla fastboot and fastboot RUU.. I have also tried the SDCard method (renaming to 2PZCIMG). Any ideas?
Errors I get are:
22 RU Header Error or 9 RU Security Fail
Details of phone:
(bootloader) kernel: lk
(bootloader) product: htc_ocnwhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1560800000
(bootloader) serialno: <SNIPPED>
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: <SNIPPED>
(bootloader) version-main: 2.42.617.1
(bootloader) boot-mode: download
(bootloader) version-baseband: 8998-002772-1712011153
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PZC50000
(bootloader) cid: BS_US001
tamudude said:
Trying to restore my wife's U11 to stock in preparation for Pie. It the US Unlocked version. Every RUU I have tried from here https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit#gid=0 gives me an error. The bootloader is relocked and I have tried both vanilla fastboot and fastboot RUU.. I have also tried the SDCard method (renaming to 2PZCIMG). Any ideas?
Errors I get are:
22 RU Header Error or 9 RU Security Fail
Details of phone:
(bootloader) kernel: lk
(bootloader) product: htc_ocnwhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1560800000
(bootloader) serialno: <SNIPPED>
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: <SNIPPED>
(bootloader) version-main: 2.42.617.1
(bootloader) boot-mode: download
(bootloader) version-baseband: 8998-002772-1712011153
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PZC50000
(bootloader) cid: BS_US001
Click to expand...
Click to collapse
I have the same variant and had a similar error with the SD card method. I ended up running the 2.42.617.7 exe from my computer and that worked. As soon as I got the stock ROM setup, I was able to take the OTA from the phone. Now running fully stock Pie, rooted with Magisk and TWRP installed, but that doesn't yet work for us, so not able to backup your ROM, so flash mods carefully. Good luck!
lucienengr said:
I have the same variant and had a similar error with the SD card method. I ended up running the 2.42.617.7 exe from my computer and that worked. As soon as I got the stock ROM setup, I was able to take the OTA from the phone. Now running fully stock Pie, rooted with Magisk and TWRP installed, but that doesn't yet work for us, so not able to backup your ROM, so flash mods carefully. Good luck!
Click to expand...
Click to collapse
Thanks for the reply. What mode does the phone have to be in? I have tried in Download Mode, Recovery Mode and rebootRUU mode but running the exe does nothing once I go past the "Agree" to terms and conditions stage from the exe. I have installed HTC Sync Manager installed. What am I doing wrong?
In recovery mode I get a red exclamation and an error on the phone saying "Your phone is corrupted and cannot boot". Is that the problem?
tamudude said:
Thanks for the reply. What mode does the phone have to be in? I have tried in Download Mode, Recovery Mode and rebootRUU mode but running the exe does nothing once I go past the "Agree" to terms and conditions stage from the exe. I have installed HTC Sync Manager installed. What am I doing wrong?
In recovery mode I get a red exclamation and an error on the phone saying "Your phone is corrupted and cannot boot". Is that the problem?
Click to expand...
Click to collapse
Fully booted, unlocked and USB plugged into your computer. The exe should recognize your phone and boot it into the right mode for the install. Be patient and let it do its thing. It will take ~10 mins I think.
lucienengr said:
Fully booted, unlocked and USB plugged into your computer. The exe should recognize your phone and boot it into the right mode for the install. Be patient and let it do its thing. It will take ~10 mins I think.
Click to expand...
Click to collapse
Finally got it figured out. The reason the exe would not progress was because it needed Visual C++ 2008 x86. I came across this post https://forum.xda-developers.com/htc-10/help/htc-ruu-windows-10-x64-x86-issues-t3690998 installed all the programs listed there and the RUU then proceeded. Eventually it threw error 170 at me. I then booted the phone into Download Mode and was able to get the ROM installed. BTW, this was with the 2.42.617.7 exe. Immediately thereafter I got the update to Pie so all is well.
tamudude said:
Finally got it figured out. The reason the exe would not progress was because it needed Visual C++ 2008 x86. I came across this post https://forum.xda-developers.com/htc-10/help/htc-ruu-windows-10-x64-x86-issues-t3690998 installed all the programs listed there and the RUU then proceeded. Eventually it threw error 170 at me. I then booted the phone into Download Mode and then I was able to get the ROM installed. BTW, this was with the 2.42.617.7 exe. Immediately thereafter I got the update to Pie so all is well.
Click to expand...
Click to collapse
That's great, congrats on sticking with it and figuring it out! I like the Pie update, especially the notifications, but they are somewhat of a challenge to get fully set up across the apps you want. Please let me know if you're able to set your SD card as your camera storage. This worked on Oreo, but cannot get this to work on Pie. I tried formatting it from the phone to no avail. The phone does recognize the SD card overall, but there does seem to be issues. I really hope devs are able make ROMs with these U11 updates. I've always used Viper ROMs and love the mods and extra features over stock. Without TWRP fully functional, this might not happen anytime soon.
Hello,
Hope someone can help me, I've read through alot of posts before asking, I have a strange issue. When my EU HTC U11 Unlocked S-ON is turned off and plugged in the battery charge icon always show as empty with the red light, fastboot see's it as empty, so I can't flash anything that way, I get RU_BATTERY_LOW error.
(bootloader) kernel: lk
(bootloader) product: htc_ocnuhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1562400000
(bootloader) serialno: FA76N1800376
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei:
(bootloader) version-main: 2.33.401.10
(bootloader) boot-mode: download
(bootloader) version-baseband: 8998-002772-1711161638
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PZC10000
(bootloader) cid: HTC__034
Appreciate any guidance on this issue.
Thank you.
If possible could someone provide me with links so I can try another DSP, RADIO, Bluetooth TWRP backup.
DSP is showing as UNKNOWN on the Fastboot download screen.
Oreo_WWE_Single_and_Dual_SIM_Radio_BT_and_DSP
Oreo_Radio_BT_DSP_TWRP_Flashable_v2_Euro
I tired these via TWRP with no luck.
Any help would be appreciated.
Try to flash the same DSP from my post - https://forum.xda-developers.com/showpost.php?p=80620553&postcount=1267
Golv said:
Try to flash the same DSP from my post - https://forum.xda-developers.com/showpost.php?p=80620553&postcount=1267
Click to expand...
Click to collapse
Thanks for the response, I'm stuck at the moment because I flashed a stock image from TWRP, which wiped out TWRP and root. So now I can't fastboot images at all due to the incorrect battery level.
Any ideas are welcome.
Glad this is a old phone
littledaga said:
Thanks for the response, I'm stuck at the moment because I flashed a stock image from TWRP, which wiped out TWRP and root. So now I can't fastboot images at all due to the incorrect battery level.
Any ideas are welcome.
Glad this is a old phone
Click to expand...
Click to collapse
Try to flash RUU for your cid (2.33.401.10 for SINGLE SIM)
You will lose all data on internal card and all user applications along with the settings, so make backup before!
Go to https://forum.xda-developers.com/u11/how-to/collection-htcu-u11-ruu-firmware-t3612048
This is your RUU - https://androidfilehost.com/?fid=746010030569951433
Golv said:
Try to flash RUU for your cid (2.33.401.10 for SINGLE SIM)
You will lose all data on internal card and all user applications along with the settings, so make backup before!
Go to https://forum.xda-developers.com/u11/how-to/collection-htcu-u11-ruu-firmware-t3612048
This is your RUU - https://androidfilehost.com/?fid=746010030569951433
Click to expand...
Click to collapse
When I try to flash RUU from sdcard I get RU_BATTERY_LOW please connect charger (0% < 30%) even though the battery shows 70% charge in the OS.
littledaga said:
When I try to flash RUU from sdcard I get RU_BATTERY_LOW please connect charger (0% < 30%) even though the battery shows 70% charge in the OS.
Click to expand...
Click to collapse
Try to flash hosd_signed.img from this firmware (2.33.401.10 for SINGLE SIM) before ruu flash.
- In bootloader mode run in command line:
Code:
fastboot flash hosd hosd_signed.img
Then reboot in Download mode and flash ruu again.
Golv said:
Try to flash hosd_signed.img from this firmware (2.33.401.10 for SINGLE SIM) before ruu flash.
- In bootloader mode run in command line:
Code:
fastboot flash hosd hosd_signed.img
Then reboot in Download mode and flash ruu again.
Click to expand...
Click to collapse
Thanks alot, flashing the hosd fixed the incorrect battery level.
And RUU and TWRP flash now without issues.