Hi all,
Maybe someone could push me in the right direction here. I unlocked my HTC U11 and went searching for a good CFW with MHL support. Sadly many don't have decent MHL support, thanks Google! I went into recovery steps, locked the bootloader and flashed official 3.34.401.1 rom. That went fine, but now the phone is stuck at the pattern screen.
Phone works fine, but the pattern is not set by me, almost as if the stock firmware has some secret pattern. It won't ask me to setup my google account and factory defaults doesn't fix the issue.
Current rom file: 2PZCIMG_OCEAN_UHL_P90_SENSE10GP_MR_HTC_Europe_3.34.401.1_Radio_8998-200321-1905141529_release_signed.zip
Device info:
(bootloader) kernel: lk
(bootloader) product: htc_ocnuhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1560000000
(bootloader) serialno: xxxx
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: xxxx
(bootloader) version-main: 3.34.401.1
(bootloader) boot-mode: download
(bootloader) version-baseband: 8998-200321-1905141529
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PZC10000
(bootloader) cid: HTC__034
Thanks in advance!
ristodesign said:
Device info:
(bootloader) kernel: lk
(bootloader) product: htc_ocnuhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1560000000
(bootloader) serialno: xxxx
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: xxxx
(bootloader) version-main: 3.34.401.1
(bootloader) boot-mode: download
(bootloader) version-baseband: 8998-200321-1905141529
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PZC10000
(bootloader) cid: HTC__034
Click to expand...
Click to collapse
To the one/those answering:
How can one have 0 slots?
That's odd, isn't it? I mean there are a/b partitioned devices and 'a' partioned devices out there.
So the slot-count is either 2 (a/b) or 1 (a).
To @ristodesign: Before flashing you had no pattern? And you did a factory data reset with your recovery?
Hi, yes. I tested LineageOS and Goole PixelExperience, but should have known there was no MHL support. Then I tried Viper and LeeDroid, but those didn't enable Wifi somehow.
Then decided to get back to the stock ROM provided by Ziand: https://androidfilehost.com/?fid=1899786940962575313
Locked the bootloader and renamed the rom file to 2PZCIMG.zip so I could restore from booting in download. File was accepted and everything went back to normal. Got a welcome screen, was forced to enable wifi, then suddenly some pattern lock, which does not give any option to escape. Perviously used patterns are certainly not working.
Factory reset does not clear the pattern lock. Which makes me quite unique I guess. ;-)
ristodesign said:
Hi, yes. I tested LineageOS and Goole PixelExperience, but should have known there was no MHL support. Then I tried Viper and LeeDroid, but those didn't enable Wifi somehow.
Then decided to get back to the stock ROM provided by Ziand: https://androidfilehost.com/?fid=1899786940962575313
Locked the bootloader and renamed the rom file to 2PZCIMG.zip so I could restore from booting in download. File was accepted and everything went back to normal. Got a welcome screen, was forced to enable wifi, then suddenly some pattern lock, which does not give any option to escape. Perviously used patterns are certainly not working.
Factory reset does not clear the pattern lock. Which makes me quite unique I guess. ;-)
Click to expand...
Click to collapse
Maybe you can try to boot twrp and see if it asks to decrypt?
The thing is: Passwords, pins, patterns etc. should be stored in the userdata partition. If you wipe this partition, the pattern should be gone.
However, if you manage to boot twrp and to have the userdata partition decrypted (go to /data and see if those entries aren't "randomized" letters), we should be able to delete this manually.
Else I'd like to know whether that pattern has been coded into the update zip you applied... Don't know how to accomplish that, however. But I'll see if I figure out something for the case twrp doesn't work.
You could also try another file like this one from here: https://htcstockrom.com/htc-u11
Will try to get trwp back on the device. It was removed and USB debugging probably disabled.
I did try the rom at https://htcstockrom.com/htc-u11 , after all those Visual C++ x86/x64 fixes it finally worked to start, but at the end it wouldn't accept to downgrade 3.34.401.1 to 2.42.617.7.
ristodesign said:
Will try to get trwp back on the device. It was removed and USB debugging probably disabled.
I did try the rom at https://htcstockrom.com/htc-u11 , after all those Visual C++ x86/x64 fixes it finally worked to start, but at the end it wouldn't accept to downgrade 3.34.401.1 to 2.42.617.7.
Click to expand...
Click to collapse
I see.
You only need to boot twrp temporarily, no need to flash it. Just do:
Code:
fastboot boot twrp.img
EDIT: What if you reflash LineageOS and then the older firmware mentioned above?
LineageOS should allow downgrades.
Good idea, i tried with this result:
downloading 'boot.img'...
OKAY [2.4sec]
booting...
(Then it stops)
Phone screen shows:
Flash image succes
Start downloading (1/1)
It stops there.
ristodesign said:
Good idea, i tried with this result:
downloading 'boot.img'...
OKAY [2.4sec]
booting...
(Then it stops)
Phone screen shows:
Flash image succes
Start downloading (1/1)
It stops there.
Click to expand...
Click to collapse
Oh, well...
That's strange... Then go for the method you already know.
What did you do earlier to flash twrp? Same command but "flash boot"?
EDIT:
I think you flashed it using
Code:
fastboot flash recovery twrp.img
right?
If so, maybe you can boot it somehow similar like this:
Code:
fastboot boot recovery twrp.img
.
Earlier I had to unlock the phone with the HTC Dev website. I created an Unlock_code.bin file. But if I try to flash now it will not accept.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 1.002s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
So USB debugging and the OEM lock seems to have set to default by flashing the stock rom.
ristodesign said:
Earlier I had to unlock the phone with the HTC Dev website. I created an Unlock_code.bin file. But if I try to flash now it will not accept.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 1.002s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
So USB debugging and the OEM lock seems to have set to default by flashing the stock rom.
Click to expand...
Click to collapse
If you do
Code:
fastboot getvar all
do you get something like this?:
(bootloader) unlocked:yes
Click to expand...
Click to collapse
Nope, it does not. When I try to flash it states that the bootloader is locked. The phone screen shows:
HTC download mode
*** RELOCKED ***
*** PRODUCTION ***
htc_ocnuhl PVT S-ON
yada yada yada... ;-)
ristodesign said:
Nope, it does not. When I try to flash it states that the bootloader is locked. The phone screen shows:
HTC download mode
*** RELOCKED ***
*** PRODUCTION ***
htc_ocnuhl PVT S-ON
yada yada yada... ;-)
Click to expand...
Click to collapse
Well, maybe you should research how to unlock an relocked bootloader.
I heard that some bootloader won't unlock again after relocking, which is why I never relocked my devices bootloader...
Hehe, yes it might be not too smart but it was the fastest solution as I could not find a working MHL CFW. I'll give my kids some money if they can find the pattern lol.
Related
hi every one
i was trying to match the RIL/basebande versions
i tried to flash some radio files and i dont know what it happend (i really forget what i did exactlly)
sudenlly i pressed the hard reset in the hboot (yes i remember i did this)
after that i tried to reflash a radio file via fastboot
i notices that in my hboot it's writen like this
*** LOCKED ***
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.29.0000
eMMC-boot
Mar 2 2012, 18:14:34
now when i try to flash PG58IMG (radio) it says fail-PU
i thaught that i'm still s-on because that pink LOCKED which written above (even it's written s-off under it !!!!!!!!)
okay i was able to change between hboot version by just flashing the hboot zip file and that's all so i tried to do that like i was
now when i try to flash the hboot (PG58IMG) it says alsi fail-PU
and now i'm stuck into this screen
here is my getvar resault if some one could help me
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.29.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 9.99.999.999
(bootloader) serialno: (removed by me because it's not important)
(bootloader) imei: (removed by me because it's not important)
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG58*****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3831mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 705f86f6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.509s
specter16 said:
hi every one
i was trying to match the RIL/basebande versions
i tried to flash some radio files and i dont know what it happend (i really forget what i did exactlly)
sudenlly i pressed the hard reset in the hboot (yes i remember i did this)
after that i tried to reflash a radio file via fastboot
i notices that in my hboot it's writen like this
*** LOCKED ***
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.29.0000
eMMC-boot
Mar 2 2012, 18:14:34
now when i try to flash PG58IMG (radio) it says fail-PU
i thaught that i'm still s-on because that pink LOCKED which written above (even it's written s-off under it !!!!!!!!)
okay i was able to change between hboot version by just flashing the hboot zip file and that's all so i tried to do that like i was
now when i try to flash the hboot (PG58IMG) it says alsi fail-PU
and now i'm stuck into this screen
here is my getvar resault if some one could help me
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.29.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 9.99.999.999
(bootloader) serialno: REMOVED
(bootloader) imei: REMOVED
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG58*****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3831mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 705f86f6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.509s
Click to expand...
Click to collapse
As long as you have access to the boot loader and/or fastboot, you're not bricked. You can technically flash Universal firmware and a recovery to get around this but you might want to flash an RUU as it'll boot you into a ROM and give you a working setup to play with.
Since you're S-OFF download and flash an RUU via fastboot, upgrade or downgrade; it makes very little difference as it will put you in a position to flash a recovery and or universal firmware.
A note on RIL/Basebands, 3.32 and 3.33 have no adverse effects of using a non matching RIL baseband so long as your WiFi and mobile network works, you should be good.
P.S: remove your SN & IMEI from your post
Sent from my HTC
DennisBold said:
As long as you have access to the boot loader and/or fastboot, you're not bricked. You can technically flash Universal firmware and a recovery to get around this but you might want to flash an RUU as it'll boot you into a ROM and give you a working setup to play with.
Since you're S-OFF download and flash an RUU via fastboot, upgrade or downgrade; it makes very little difference as it will put you in a position to flash a recovery and or universal firmware.
A note on RIL/Basebands, 3.32 and 3.33 have no adverse effects of using a non matching RIL baseband so long as your WiFi and mobile network works, you should be good.
P.S: remove your SN & IMEI from your post
Sent from my HTC
Click to expand...
Click to collapse
i tried an RUU and it says error 171 usb connection error !
i'm in fastboot and i can see my device connected using the fastboot devices commande
by the way this problem happed while i'm trying to get my wifi working
any way now i'm trying to get my device booting
specter16 said:
i tried an RUU and it says error 171 usb connection error !
i'm in fastboot and i can see my device connected using the fastboot devices commande
by the way this problem happed while i'm trying to get my wifi working
any way now i'm trying to get my device booting
Click to expand...
Click to collapse
I skimmed over your other thread, and you probably should have tried a kernel with BCM drivers if you haven't already.
Try with a different (and known to work) USB.
Also, make sure HTC Sync is closed and that you run the RUU as administrator.
Sent from my HTC
DennisBold said:
I skimmed over your other thread, and you probably should have tried a kernel with BCM drivers if you haven't already.
Try with a different (and known to work) USB.
Also, make sure HTC Sync is closed and that you run the RUU as administrator.
Sent from my HTC
Click to expand...
Click to collapse
i tried Sultan kernel with BCM driver and it didn't work (wifi turning on................................)
any way this is not my current prb now
one other thing
when i try this commande fastboot oem rebootRUU
here is what it says
Code:
...
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(732): error 2
(bootloader) Start Verify: 0
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(732): error 2
(bootloader) Start Verify: 0
(bootloader) erase sector 130560 ~ 131071 (512)
(bootloader) emmc_erase(1852): sd_write_sector failed!
OKAY [ 0.235s]
finished. total time: 0.257s
and RUU is still not working
specter16 said:
i tried Sultan kernel with BCM driver and it didn't work (wifi turning on................................)
any way this is not my current prb now
one other thing
when i try this commande fastboot oem rebootRUU
here is what it says
Code:
...
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(732): error 2
(bootloader) Start Verify: 0
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(732): error 2
(bootloader) Start Verify: 0
(bootloader) erase sector 130560 ~ 131071 (512)
(bootloader) emmc_erase(1852): sd_write_sector failed!
OKAY [ 0.235s]
finished. total time: 0.257s
and RUU is still not working
Click to expand...
Click to collapse
Format you SDCard, or make sure it's properly inserted.
Download this file and place it in your fastboot directory.
Edit: Link: http://db.tt/4UwSEM33
Then try this:
fastboot erase recovery
fastboot flash recovery recovery.img
Using your bootloader, boot into recovery
Sent from my HTC
DennisBold said:
Format you SDCard, or make sure it's properly inserted.
Download this file and place it in your fastboot directory.
Edit: Link: http://db.tt/4UwSEM33
Then try this:
fastboot erase recovery
fastboot flash recovery recovery.img
Using your bootloader, boot into recovery
Sent from my HTC
Click to expand...
Click to collapse
okay i'll try
please stay connected, i really need you
specter16 said:
okay i'll try
please stay connected, i really need you
Click to expand...
Click to collapse
Sure. If the fastboot commands work I've got something you can try.
Sent from my HTC
DennisBold said:
Format you SDCard, or make sure it's properly inserted.
Download this file and place it in your fastboot directory.
Edit: Link: http://db.tt/4UwSEM33
Then try this:
fastboot erase recovery
fastboot flash recovery recovery.img
Using your bootloader, boot into recovery
Sent from my HTC
Click to expand...
Click to collapse
not working !!!
fastboot erase recovery gives me this
Code:
erasing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.002s
specter16 said:
not working !!!
fastboot erase recovery gives me this
Code:
erasing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.002s
Click to expand...
Click to collapse
You are S-OFF?
Try:
fastboot oem unlock
Else move the universal firmware file into the folder with fastboot and type:
fastboot flash zip <zip name>.zip
Sent from my HTC
DennisBold said:
You are S-OFF?
Try:
fastboot oem unlock
Else move the universal firmware file into the folder with fastboot and type:
fastboot flash zip <zip name>.zip
Sent from my HTC
Click to expand...
Click to collapse
not working
Code:
(bootloader) [ERR] Command error !!!
OKAY [ 0.006s]
finished. total time: 0.006s
specter16 said:
not working
Code:
(bootloader) [ERR] Command error !!!
OKAY [ 0.006s]
finished. total time: 0.006s
Click to expand...
Click to collapse
Sorry, always getting commands mixed up.
Try:
fastboot update PG58IMG.zip
Sent from my HTC
DennisBold said:
Sorry, always getting commands mixed up.
Try:
fastboot update PG58IMG.zip
Sent from my HTC
Click to expand...
Click to collapse
archive does not contain 'boot.img'
error: update package missing boot.img
are you sure that i'm s-off my friend ??? because it's written in the hboot above with pink
*** LOCKED ***
but under this line it's written S-OFF with green
specter16 said:
archive does not contain 'boot.img'
error: update package missing boot.img
are you sure that i'm s-off my friend ??? because it's written in the hboot above with pink
*** LOCKED ***
but under this line it's written S-OFF with green
Click to expand...
Click to collapse
You're S-OFF, however your bootloader is locked. Meaning commands are locked, S-OFF disables security allowing you to flash things without being signed by HTC.
Could you try this:
fastboot erase cache
fastboot oem rebootRUU (if you get SDcard errors, take out your SDCard and try again)
fastboot flash zip PG58IMG.zip
fastboot reboot-bootloader
Sent from my HTC
DennisBold said:
You're S-OFF, however your bootloader is locked. Meaning commands are locked, S-OFF disables security allowing you to flash things without being signed by HTC.
Could you try this:
fastboot erase cache
fastboot oem rebootRUU (if you get SDcard errors, take out your SDCard and try again)
fastboot flash zip PG58IMG.zip
fastboot reboot-bootloader
Sent from my HTC
Click to expand...
Click to collapse
fastboot erase cache
Code:
erasing 'cache'...
FAILED (remote: erasing error!)
finished. total time: 0.024s
fastboot oem rebootRUU
SD card errors and the device reboot into hboot
specter16 said:
fastboot erase cache
Code:
erasing 'cache'...
FAILED (remote: erasing error!)
finished. total time: 0.024s
fastboot oem rebootRUU
SD card errors and the device reboot into hboot
Click to expand...
Click to collapse
Tried removing your SD-Card? And have you checked the SDCard still works?
Sent from my HTC
DennisBold said:
Tried removing your SD-Card? And have you checked the SDCard still works?
Sent from my HTC
Click to expand...
Click to collapse
nothing is inserted on my phone (SIM / SD)
and my sd card is working fine on my pc
omg what i did :s:s:s
specter16 said:
nothing is inserted on my phone (SIM / SD)
and my sd card is working fine on my pc
omg what i did :s:s:s
Click to expand...
Click to collapse
That's odd. Insert your SDCard after formatting it and placing the PG58IMG.zip on it. Then reboot into bootloader. See if it works, and let me know.
Sent from my HTC
Fail-PU errors generally correspond to firmware corruption
Which is pretty hard to solve
If Op can exactly tell flashing what caused this issue
Maybe we can have a chance
Btw can the phone go to recovery?
Also how did the patched hboot flash went?
Sent from my HTC Sensation 4G using xda premium
DennisBold said:
That's odd. Insert your SDCard after formatting it and placing the PG58IMG.zip on it. Then reboot into bootloader. See if it works, and let me know.
Sent from my HTC
Click to expand...
Click to collapse
- Fail-PU next to the bootloader line
i found this command
Code:
fastboot oem writesecureflag 3
i think this will return me back to s-on
but can i s-off my phone from hboot ??? if i want
or it's useless this command for me ?
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
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
First to admit I did something stupid. I am looking for anyone to help me.
Long story short I think I have locked my bootloader. I dont know if i have the stock bootloader or twrp.
C:\adb>fastboot getvar all
< waiting for device >
(bootloader) kernel: lk
(bootloader) product: htc_ocnwhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1560800000
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) version-main: 2.31.617.2
(bootloader) boot-mode: download
(bootloader) version-baseband: 8998-002772-1711021119
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PZC50000
all:
finished. total time: 0.005s
I cant get into the twrp bootloader menu and I tried to use the RRU from htc to reload my phone. I get a 155 error. I tried to unlock the bootloader again with the htc ulock_code.bin error message
sending 'unlocktoken' (0 KB)...
OKAY [ 1.001s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: UnlockToken Verify Fail!!)
finished. total time: 1.199s
I am at a loss on what to do. Am I screwed? I am within the htc 30 day window but dont think they will accept my phone.
skinny1439 said:
First to admit I did something stupid. I am looking for anyone to help me.
Long story short I think I have locked my bootloader. I dont know if i have the stock bootloader or twrp.
C:\adb>fastboot getvar all
< waiting for device >
(bootloader) kernel: lk
(bootloader) product: htc_ocnwhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1560800000
(bootloader) serialno: FA79G0500641
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: 358182081003810
(bootloader) version-main: 2.31.617.2
(bootloader) boot-mode: download
(bootloader) version-baseband: 8998-002772-1711021119
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PZC50000
(bootloader) cid: BS_US001
all:
finished. total time: 0.005s
I cant get into the twrp bootloader menu and I tried to use the RRU from htc to reload my phone. I get a 155 error. I tried to unlock the bootloader again with the htc ulock_code.bin error message
sending 'unlocktoken' (0 KB)...
OKAY [ 1.001s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: UnlockToken Verify Fail!!)
finished. total time: 1.199s
I am at a loss on what to do. Am I screwed? I am within the htc 30 day window but dont think they will accept my phone.
Click to expand...
Click to collapse
Delete your SN and Imei.
Wysłane z mojego HTC U11 przy użyciu Tapatalka
skinny1439 said:
First to admit I did something stupid. I am looking for anyone to help me.
Long story short I think I have locked my bootloader. I dont know if i have the stock bootloader or twrp.
C:\adb>fastboot getvar all
< waiting for device >
(bootloader) kernel: lk
(bootloader) product: htc_ocnwhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1560800000
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) version-main: 2.31.617.2
(bootloader) boot-mode: download
(bootloader) version-baseband: 8998-002772-1711021119
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PZC50000
all:
finished. total time: 0.005s
I cant get into the twrp bootloader menu and I tried to use the RRU from htc to reload my phone. I get a 155 error. I tried to unlock the bootloader again with the htc ulock_code.bin error message
sending 'unlocktoken' (0 KB)...
OKAY [ 1.001s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: UnlockToken Verify Fail!!)
finished. total time: 1.199s
I am at a loss on what to do. Am I screwed? I am within the htc 30 day window but dont think they will accept my phone.
Click to expand...
Click to collapse
Skip again the bootloader unlocking procedure via htcdev
HTC U11 & Tapatalk
linar10 said:
Skip again the bootloader unlocking procedure via htcdev
Delete imei and serialno
HTC U11 & Tapatalk
Click to expand...
Click to collapse
Thanks I was able to unlock the bootloader via the htc dev. I just had to redownload the unlock key.
HTC u11 fails to boot.
skinny1439 said:
Thanks I was able to unlock the bootloader via the htc dev. I just had to redownload the unlock key.
Click to expand...
Click to collapse
I have a new problem.
I will start at the beginning. I was running stock htc oreo. I really wanted to install viperu 1.7. I assumed that I needed to reinstall nougat. I attemped to use the htc ruu to roll back. This failed. I booted into twrp and performed a wipe and restore to a known good nougat backup. When I rebooted the device started to boot gets past the htc logo and the shuts off. Thinking that something failed I rebooted into twrp and attempted to reinstall a stock zip. This fails to install. I wiped again and installed viperu 1.7 everything installs properly per the viper install guide. When the phone reboots it starts to install the apps. It finishes but shuts off. I connected it to a charger and booted the phone and attempted to boot but shuts off.
Can someone please tell me what I have done wrong and how to fix it.
thanks in advance.
Without s-off, the older ruu will not work. Probably older rom on newer firmware may not work. Download stock backup 2.xx.xxx.x and restore in twrp and do not forget full wipe before restoring backup
HTC U11 & Tapatalk
linar10 said:
Without s-off, the older ruu will not work. Probably older rom on newer firmware may not work. Download stock backup 2.xx.xxx.x and restore in twrp and do not forget full wipe before restoring backup
HTC U11 & Tapatalk
Click to expand...
Click to collapse
Do you have a stock backup 2.xx.xxx.x or know where I can get one. I looked online but they dont have 2.x on the list.
My phone is 2PZC50000 BS_US001 WHL (Single SIM) US Unlocked.
RUU and backup
https://forum.xda-developers.com/showthread.php?p=74694695
HTC U11 & Tapatalk
IT works again!!
linar10 said:
RUU and backup
https://forum.xda-developers.com/showthread.php?p=74694695
HTC U11 & Tapatalk
Click to expand...
Click to collapse
You saved me. I am extremely grateful of your knowledge. I thought I flushed 700 buck down the drain.
Whats the best way to revert back to nougat so I can flash to viperu 1.7. Right now I am on 2.31.617.2 from the backup you sent me to in the link. I do need to root the phone but have not attempted yet. I was planning to root the phone at the same time as installing viperu. Much thanks again.
skinny1439 said:
You saved me. I am extremely grateful of your knowledge. I thought I flushed 700 buck down the drain.
Whats the best way to revert back to nougat so I can flash to viperu 1.7. Right now I am on 2.31.617.2 from the backup you sent me to in the link. I do need to root the phone but have not attempted yet. I was planning to root the phone at the same time as installing viperu. Much thanks again.
Click to expand...
Click to collapse
Can't roll back to 7.1.1 yet. You need to be S-Off and Sunshine isn't fully working on Oreo at this time.
But there is a ViperU Oreo Rom available now. If you want, to just flash it and sick with 8.0.
linar10 said:
RUU and backup
https://forum.xda-developers.com/showthread.php?p=74694695
HTC U11 & Tapatalk
Click to expand...
Click to collapse
You're the man.
henslo said:
Can't roll back to 7.1.1 yet. You need to be S-Off and Sunshine isn't fully working on Oreo at this time.
But there is a ViperU Oreo Rom available now. If you want, to just flash it and sick with 8.0.
Click to expand...
Click to collapse
Thanks for all your help. I really appreciate it!
skinny1439 said:
Thanks for all your help. I really appreciate it!
Click to expand...
Click to collapse
The viper rom for oreo doesn't really work right yet and they're working on it. I'm using stock with magisk beta 14.5. Substratum works a bit too.
My HTC U11 always stuck in bootloader saying I use an unauthorized software everytime I update to Android Oreo ( official OTA update).
Even if I use RUU to 8.0.
The only thing I can boot my phone is when I use Nougat Rom. Even Costum Rom not helping. It;s very weird that I cannot update to 8.0.
I try leedroid Rom, also same, got back to Bootloader. So I need to reflash the 7.1.1 Rom to enable to boot.
My phone is S-Off with Bootloader Unlocked.
When I try to relock bootloader it will say something like
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ -0.000s]
finished. total time: -0.000s
In the Menu is greyed out saying bootloader already unlock.
Thanks in advance for any help.
sing2x said:
My HTC U11 always stuck in bootloader saying I use an unauthorized software everytime I update to Android Oreo ( official OTA update).
Even if I use RUU to 8.0.
The only thing I can boot my phone is when I use Nougat Rom. Even Costum Rom not helping. It;s very weird that I cannot update to 8.0.
I try leedroid Rom, also same, got back to Bootloader. So I need to reflash the 7.1.1 Rom to enable to boot.
My phone is S-Off with Bootloader Unlocked.
When I try to relock bootloader it will say something like
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ -0.000s]
finished. total time: -0.000s
In the Menu is greyed out saying bootloader already unlock.
Thanks in advance for any help.
Click to expand...
Click to collapse
Am output of a
Code:
fastboot getvar all
might show us some more, to help you with that very problem. Don't forget to delete your IMEI and SN though.
Tell us which RUU you are using that causes this very problem as well.
Sent from my HTC U12+ using XDA Labs
(bootloader) kernel: lk
(bootloader) product: htc_ocnwhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1562400000
(bootloader) serialno: FA76T1802xxx
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: 990007230168xxx
(bootloader) version-main: 1.28.617.6
(bootloader) boot-mode: download
(bootloader) version-baseband: 8998-001791N-1709131257
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PZC50000
(bootloader) cid: BS_US001
all:
finished. total time: 0.016s
Any RUU, any costum Rom based on Android 8.0 give me error.
Other than that, all 7.1.1 Roms / RUU boots just fine.
It's Sprint Unit , S-Off , and change to BS-US001
return to sprint Rom also no use.
I can receive OTA no problem.
After OTA to 8.0 stuck in Bootloader again saying same error.
sing2x said:
Any RUU, any costum Rom based on Android 8.0 give me error.
Other than that, all 7.1.1 Roms / RUU boots just fine.
It's Sprint Unit , S-Off , and change to BS-US001
return to sprint Rom also no use.
I can receive OTA no problem.
After OTA to 8.0 stuck in Bootloader again saying same error.
Click to expand...
Click to collapse
Well that's it actually. The device only accepts CDMA sprint updates. So it would have to be rebranded and RUU'd back to Sprint to receive updates again. But are you really using an HTC U11? The fastboot command mentions a slot which in general only applies to Treble enabled devices.
Sent from my HTC U12+ using XDA Labs
Ruu back to sprint. Also cannot upgrade to 8.0. Even on OTA update. Yes its U11.
Any help ? it only works with 7.0 Rom. I try almost everything.