Related
Pretty sure I effed up... Before reading further please know I am a very novice Android user, but am great at following directions.
In an attempt to install a custom ROM on my phone I'm having some serious issues getting it to work. I was able to unlock the bootloader on my device quite easily but after attempting to install TWRP the device boots to a black screen when trying to load the recovery. I know the phone is on because I have to press and hold power for a while before I can get back into the actual system. I figured I'd try installing CWM but it does the same thing. I installed the ROM Manager app as suggested by another site but it really is of no help to me without my phone being rooted, which it is not... yet. The app does show that both TWRP and CWM are installed but gets an error flashing CWM and if i try to set it to use the outdated version of CWM or TWRP it says that it's configured to use the existing recovery installation and makes no difference trying to load the recovery.
Phone info: (Let me know if you need anything not listed.)
Android Version: 4.1.1
HTC Sense: 4+
Software#: 3.17.631.3
HTC SDK API leve: 4.63
Build#: 3.17.631.3
Kernel version: 3.4.0-g240d4d5
I'm at a loss for what to do to either get a working custom recovery or restore the factory one to working condition, which I can't seem to find online anywhere.
Edit: Grammar.
Edit2: Update - I was able to get TWRP to run and then attempted to install CyanogenMod, when it installs it says MD5 file not found but says successfully installed. After rebooting to system it just gets stuck in an endless reboot cycle. Ideas / Suggestions?
If it's Rogers it isn't a one x. It's a one xl so you are in the wrong forum which will be why it has all gone wrong
nogotaclue said:
If it's Rogers it isn't a one x. It's a one xl so you are in the wrong forum which will be why it has all gone wrong
Click to expand...
Click to collapse
I've ensured to use Evita for all the guides. I double triple and quadruple checked everything before performing any steps. Posting in the wrong thread doesn't change the situation. Is there a way to move this to the correct thread?
Edit: Also, according to HTC the Evita was a code name used for both the One XL and One X simultaneously. One XL applied specifically to releases in Hong Kong, Australia, Germany, Singapore, and United Kingdom. One X applied to Canada (where I am) and USA.
13rennon said:
I've ensured to use Evita for all the guides. I double triple and quadruple checked everything before performing any steps. Posting in the wrong thread doesn't change the situation. Is there a way to move this to the correct thread?
Edit: Also, according to HTC the Evita was a code name used for both the One XL and One X simultaneously. One XL applied specifically to releases in Hong Kong, Australia, Germany, Singapore, and United Kingdom. One X applied to Canada (where I am) and USA.
Click to expand...
Click to collapse
Reported and will be moved
Boot into fastboot and run the command getvar and post the results. Be sure to block out your imei and serial before posting. This may help XDA members diagnose the problem.
Are you full wiping cache, data, and Dalvik before and after flashing CM?
audit13 said:
Boot into fastboot and run the command getvar and post the results. Be sure to block out your imei and serial before posting. This may help XDA members diagnose the problem.
Are you full wiping cache, data, and Dalvik before and after flashing CM?
Click to expand...
Click to collapse
Yes I was doing a full wipe before flashing, but not after. Situation has changed a bit though... I was working with someone via reddit (Full thread here: reddit.com/r/root/comments/3a4cc2/htc_one_x_root_for_beginner/ ) Long story short: Finally got CyanogenMod installed but let it sit over an hour and just stuck on spinning CM logo. Forced shutdown, booted into TWRP and wouldn't recognize SD or mount (eMMC). Read this can be due to not doing a factory reset, tried to do the factory reset but same deal. Tried to ruin an RUU that matched my info but it failed and with a locked bootloader I cant even get into TWRP, I need to unlock the bootloader and reinstall TWRP after failing an RUU.
Phone details as requested:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.14.0000
(bootloader) version-baseband: 0.23a.32.09.29
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.631.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4017mV
(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.156s
When I try to RUU I start by relocking the bootloader with "fastboot oem lock" and then I run "fastboot erase cache" then "fastboot oem rebootRUU" then "fastboot flash zip RUU.zip" when it's on the black screen with silver HTC logo. I get this:
c:\Android>fastboot flash zip RUU.zip
sending 'zip' (650005 KB)...
OKAY [ 25.324s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 97.643s
The RUU file I'm using is OTA_EVITA_UL_JB_45_S_Rogers_WWE_3.17.631.2_0.23a.32.09.29_10.128.32.34a_release_299850qstr7rxdbfuofl6j.zip I've read they can sometimes give odd errors so I ran it a second time as suggested, same error running a second time. If I try to boot after this it boots to the white HTC quietly brilliant screen.
I see you have s-on and you do not have super CID.
With s-on, I think you have to flash the boot.img file for the phone to boot.
Easiest way to solve the problem may be to get s-off and supercid.
This is what my Rogers HTC One X says:
version: 0.5
version-bootloader: 2.14.0000
version-baseband: 0.23a.32.09.29
version-cpld: None
version-microp: None
version-main: 3.17.707.1
version-misc: PVT SHIP S-OFF
serialno: HT
imei: 3596
product: evita
platform: HBOOT-8960
modelid: PJ8310000
cidnum: 11111111
battery-status: good
battery-voltage: 4081mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-97c9a0
hbootpreupdate: 11
gencheckpt: 0
all: Done!
Hello,
I recently dropped my HTC One S into a glass of water. It kept on working so I thought I'd got away with it, but then a few hours later it rebooted and now won't boot beyond the white "HTC" screen before rebooting again. I've tried drying it out but it's still doing it.
The phone had not been modded or rooted before, I just used the stock HTC OS which came with it. I can get to the bootloader screen and have tried various things to get it working but nothing seems to have worked. I've anyone can point me in the right direction (or tell me I've no chance) I'd be very grateful. I've done the following:
Tried the stock recovery, gave the same reboot loop.
Tried the "clear storage" and "factory reset" options, same reboot loop.
Connected with USB Fastboot - seems fine and I can see the device from my laptop
Unlocked the bootloader - I now have *** UNLOCKED *** at the top of the screen
Flashed a custom recovery (I've tried CWM and TWRP, various versions) - seemed fine and Fastboot suggested that the flash had worked, but when I try to load it I get the same reboot loop. The only difference is that I now have some red text on the HTC screen when starting recovery: "This build is for development purpose only. Do not distribute outside of HTC without HTC's written permission. Failure to comply may lead to legal action."
I'm at a loss as to what to try or where to look now. I saw one post which suggested that the stock ROM may be detecting the invalid recovery and trying to overwrite it, and others that suggest using an RUU to get the phone back to original state, but I can't seem to see one which matches the info I get from "fastboot getvar all". My thinking is that if the recovery doesn't even work then something is wrong with the phone itself, but is there a way I can tell what the phone is doing or any logs I can see? As Fastboot doesn't have access to files in storage I can't tell if there's anything there.
The phone's info (from fastboot getvar all) is below, and if anyone can suggest anything I'd be very grateful.
Thanks,
James
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.13.0000
(bootloader) version-baseband: 1.11.50.05.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.16.771.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH24SW409116
(bootloader) imei: 359901047356445
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: H3G__001
(bootloader) battery-status: low
(bootloader) battery-voltage: 3446mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-26dff973
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
From what you describe, it surely sounds like a HW fault. Reflashing will not fix it. You can always try (in the unlikely case that the flash memory was somehow rewritten), but as you already have tried it, it means your phone is most probably bricked. Sorry.
Some expert may want to confirm my conclusion.
As a last resort, I would take the phone apart, and leave it like that for a day or two, to make sure any remaining moisture has a change to evaporate - and then re-assemble. It is possible that some of it could be shorting an address line or something? More likely something is corroded beyond repair.
EDIT: It may be possible that the hboot was damaged / rewritten but the flash memory is still intact. That may be fixable, but quite difficult. It means purposedly "bricking" the device further and manually registering device nodes in Linux and directly writing into them.... I think I saw a guide somewhere. This will not be easy for the average user, and there only a slim chance it will actually work.
Thanks. That's pretty much what I thought but thought I'd ask in case someone had any bright ideas. I've already ordered a new phone which should get here tomorrow, so I don't really want to spend hours trying to get it working when it's probably bricked anyway.
I'm wondering if anyone can help with this. The phone is an Unbranded UK LTE One SV that was previously running Stock Jellybean 4.22. (Manufacturer No: 99HSH008-00).
I had it from new and it was never flashed or rooted or had S off etc. It started to play up so I got another device. At one point I was able to reset it and it worked but then randomly when it booted it would only boot to a black screen with a clock at the top. Like it had not loaded all the OS. After a while it would then just power off. Now I can't get past the boot menu. I'm trying to determine if this is a hardware fault or if it just needs to be reflashed to stock if the ROM has been corrupted.
The menu says as per attached picture :
TAMPERED
LOCKED.
Security Warning
K2_UL PVT SHIP S-ON RL
HBOOT-2.00.0000
RADIO-1.18.40a.00.05
OpenDSP-v13.2.0268.0620
eMMc-boot
March 14 2013 22:10:43-1
It boots to the following menu.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I notice it gets very hot if left for a while in this menu and the battery drains quickly. Factory reset just takes me back to the same menu as does recovery. After the HTC screen it says in red that this version is for development purposes only under. I note that on other screen shots from other devices it say the memory size next to the eMMC Boot, whereas mine has none. When connected via USB the phone is recognised on the PC in Device manager. Is there any hope or anything I can try?
Any help appreciated.
Since posting I've done the following:
First I've Unlocked my phone at the htcdev site successfully.
So now it shows this in the Boot menu
Then following instructions from here: Root for HTC One SV UPDATED 23/02/13
http://forum.xda-developers.com/showthread.php?t=2113671
I then flashed recovery.img using the downloaded file on the thread labelled as the stock recovery.
I just realised though that this file is called k2u_recovery_signed.img (which i had re-named to recovery.img)
but my phone is a K2 UL. Is this the wrong recovery file to flash with? I'm unable to enter recovery mode the phone just get stuck on the HTC quietly brilliant screen with the red development version writing underneath or just reboots in a loop. It still doesn't boot properly.
I can't seem to find the correct recovery.img.
I looked on this thread here:
http://forum.xda-developers.com/showthread.php?t=2317379
where there are 2 files for K2 UL European.
Jelly Bean (uploaded OTA_K2_UL_JB_45_S_HTC_Europe_2.14.401.6-2.14.401.2)
and
Jelly Bean (uploaded OTA_K2_UL_JB_45_S_HTC_Europe_2.14.401.2-1.17.401.5_R)
I am able to download the 2nd file from google docs but the 1st from app.box.com can't seem to be downloaded by any of my browsers.
I reflashed the 2nd K2UL recovery.img from Jelly Bean (uploaded OTA_K2_UL_JB_45_S_HTC_Europe_2.14.401.2-1.17.401.5_R)
But it still doesn't go into recovery mode. I sometimes get the green download arrow then it goes black or just goes straight to black so i guess its not the right file either. Is there an alternate link for the other file anywhere, so I can try that?
recovery.img
Md5Sum: B219A04154A3ED29271B14F120FDE853
I was unable to enter recovery before this so think it was already corrupted.
having no luck finding that recovery assuming its the right one. leaving it for now.
I think, that you can't boot into recovery, is a problem of mismatching files. You are using older recovery files with latest firmware.
But at least i don't know what software/firmware you are running on your phone, so try to get some more info by using fastboot with the following cmd:
Code:
fastboot getvar all
Put the output here without serial and imei numbers.
For a recovery which works with latest software, look here.
At all, this thread is a good start, if you are looking for something this phone related.
Thank you for the prompt reply, here's the info. The boot menu is now frozen so will have to remove the battery to try again and flash with that recovery you recommended. The link for TWRP 2.8.4.0 touch recovery on that thread is now dead. Is the latest version from here on (https://twrp.me/devices/htconesvlte.html) ok? It appears that
twrp-2.8.5.0-k2_ul.img is the newest compatible. Will this replace the stock recovery (that presently is likely the wrong one as the file on the other thread was non downloadable for me from app.box.com. Another link would be great, assuming its the correct file.
My aim is to get this phone working again, initially as stock jellybean 4.22 so it can be used then maybe experiment. As of now its still S-ON and unrooted but with an unlocked bootloader, but wont work at all.
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2
(bootloader) version-baseband: 1.1
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.40
(bootloader) version-misc: PVT SHI
(bootloader) serialno: *************
(bootloader) imei: ***************
(bootloader) product: k2_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PL8010000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4233
(bootloader) partition-layout: Gen
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
twrp-2.8.5.0-k2_ul.img from here https://dl.twrp.me/k2_ul/twrp-2.8.5.0-k2_ul.img.html is now flashed and working. It's on here as the latest working version https://dl.twrp.me/k2_ul/.
lucids said:
Will this replace the stock recovery...
Click to expand...
Click to collapse
Yes, it will.
....(that presently is likely the wrong one as the file on the other thread was non downloadable for me from app.box.com. Another link would be great, assuming its the correct file.
Click to expand...
Click to collapse
You don't need stock recovery (anymore). As your system won't boot, you need another way to get your phone working and the key for this is a custom recovery.
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2
(bootloader) version-baseband: 1.1
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.40
(bootloader) version-misc: PVT SHI
(bootloader) serialno: *************
(bootloader) imei: ***************
(bootloader) product: k2_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PL8010000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4233
(bootloader) partition-layout: Gen
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
Click to expand...
Click to collapse
Your fastboot output seems to be some kind of "cutout". Should look like this:
D:\adb>Fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.21.0000
(bootloader) version-baseband: 1.21.40f.00.23
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.164.107
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ****
(bootloader) imei: ****
(bootloader) meid:
(bootloader) product: k2_u
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PL8013000
(bootloader) cidnum: VODAP304
(bootloader) battery-status: good
(bootloader) battery-voltage: 3747mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2bb255c2
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
finished. total time: 0.132s
twrp-2.8.5.0-k2_ul.img from here https://dl.twrp.me/k2_ul/twrp-2.8.5.0-k2_ul.img.html is now flashed and working.
Click to expand...
Click to collapse
This is good and the next step forward.
Now, from TWRP recovery, you have 2 options to get your system working:
- you can flash a stock or custom rom
- you can restore a stock backup
It's up to you now!
Ok thanks, not sure what you mean by it being a "cut out". Mine is a non SIM locked unbranded UK One SV. Prior to it going faulty it had never been flashed or rooted etc.
EDIT:
Ah I see some of the info never pasted correctly I just noticed. Here it is in full.
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0000
(bootloader) version-baseband: 1.18.40a.00.05
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ******
(bootloader) imei: *******
(bootloader) product: k2_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PL8010000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3985mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.089s
Bearing in mind that the bootloader is now unlocked , but its still is S-ON and unrooted what is the next step for me to recover the newest JB4.22 that I had earlier and have the phone rooted. Do I need to have S off before in order to flash a ROM back on?
I have already downloaded several files but not sure which is the correct one and the procedure.
I already have:
OTA_K2_UL_JB422_SENSE50_MR_HTC_Europe_3.11.401.1-2.14.401.6_release_338297mseg08soslxcubit.zip (431MB)
(MD5: 0d6c763962fdc8915096b11b84329dc1)
PL80IMG_K2_UL_JB422_SENSE50_MR_HTC_Europe_3.11.401.1_Radio__1.18.40a.00.05_10.81a.40.23L_release_338297.zip (674MB)
(MD5: 336f6d914ac4b7799dca4d35bfe536ed)
Thank you again for your help.
lucids said:
Bearing in mind that the bootloader is now unlocked , but its still is S-ON and unrooted what is the next step for me to recover the newest JB4.22 that I had earlier and have the phone rooted. Do I need to have S off before in order to flash a ROM back on?
Click to expand...
Click to collapse
No, S-off needed.
I think the easiest way is to restore a TWRP backup: you can use this twrp backup to restore a working OS on your phone.
This is not to flash, you must use restore.
The location on ext_sdcard for the backup is:
\TWRP\BACKUPS"Put here the serial number of your device"\Backup files you have downloaded
Or the location where the files have to be that TWRP can recognise them, explained by another guy:
Modding.MyMind said:
TWRP (folder) >> BACKUPS (folder)>> Serial Device (folder)>> Name of Backup (folder)>> backup files
If those folders do not exist as listed above then make them. Serial device will be the devices actual serial number, by typing and entering, fastboot devices, will display the serial number. Name that folder as such.
The folder which is referred to the name of the backup you can simply call it whatever. For example, help_me_422.
Place backup files inside the "help_me_422" folder.
Go to main menu of the TWRP, click on restore, you backup will be on the external sdcard so insure you select that storage so the backup will appear as an option. Now select the backup. A list for system, boot, etc, etc will appear with boxes and a check in those boxes. Now swipe to restore.
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
Thank you for the info.
So as you said there is no need for S-Off now.
On 1st attempt the Restore failed as I put the zip file itself into the last folder as opposed to all the individual files themselves and their MD5's [boot.emmc.win, data.ext4.win, recovery.log, system.ext4.win]. The restore then said it completed successfully.
Still the phone will not work and gets stuck on startup with the HTC screen with the red development only version writing underneath.
I notice that the external SD card which shows its size next to it but the internal SD card is showing as 0MB. And also when the 1st restore failed it reported that it was unable to mount the Internal SD memory. The same is true after the restore success, it says unable to mount int_sd. (See pics below). is there a way to test the internal memory to see if there is another problem or does it need re partitioning, if this isn't done via the restore process itself?
Hm, sounds not so good...
Well, i don't know this TWRP version exactly, as it is long time ago i used it.
But go to the wipe menu and look, if there (or under wipe - advanced) is an option something like "repair broken filesystem" or so (can't remember exactly what it is called).
If yes, go there and try if this option can help.
on the main menu there is WIPE - that says it does a factory reset, Wipes Cache and Dalvik
Or
There is an Advanced as you remembered well where you can choose the partitions
Dalvik cache
Cache
Data
Int SD
Android Secure
SD card
System
Either you can select to wipe the selected partitions or with another button at the bottom Repair or Change File System
I selected IN_SD and clicked to Repair and it showed as being 0MB then Failed as per attached pics. I was able to repair the cache and Dalvik cache but the Int SD still saying unmountable. Same result not working.
lucids said:
on the main menu there is WIPE - that says it does a factory reset, Wipes Cache and Dalvik
Or
There is an Advanced as you remembered well where you can choose the partitions
Dalvik cache
Cache
Data
Int SD
Android Secure
SD card
System
Either you can select to wipe the selected partitions or with another button at the bottom Repair or Change File System
I selected IN_SD and clicked to Repair and it showed as being 0MB then Failed as per attached pics. I was able to repair the cache and Dalvik cache but the Int SD still saying unmountable. Same result not working.
Click to expand...
Click to collapse
Ok, it seems that you only have one chance for your phone, a ruu.
Download this file: https://www.androidfilehost.com/?fid=24369303960683578
Rename the zip file to PL80IMG.zip (make sure it is not named PL80IMG.zip.zip) and copy it in the external sdcard.
As you are S-on, you need to lock your bootloader again, first. Do this with the fastboot cmd
Code:
fastboot oem lock
Then boot into the bootloader and let the phone recognize the PL80IMG.zip. Confirm to update with vol+ and let it run until its finished.
Ok now while having selected the Int SD partition instead of selecting Repair I selected Change File System and then in there selected FAT, it completed and has gone back to this menu but now shows as being 4239MB as opposed to 0MB.
I will have another look at it later but presently its still not booting to the system.
Now in the Restore menu the Internal is showing 4239MB also instead of 0Mb.
So I'm trying a restore again. Fingers crossed....
This time no errors regarding mounting the Int SD but on Rebooting it goes to HTC with red writing for 30 sec then goes off.
Give the Ruu a try. It should restore everything to stock, if possible.
Thanks i posted the last post before seeing your reply about the RUU. I will give that a go and report back. After i tried the restore again (after the int Sd came back) the int sd again went back to 0MB and being unmountable. i had to fix it and format again for it to reappear as 4gb.
I relocked the bootloader so it now says Tampered and Relocked.
Re booted into the bootloader with the Ext sd card in with the PL80IMG.zip. at its root. (MD5 all ok)
First it says loading... [PL80DIAG.zip]
No Image!
Then loading... [PL80DIAG.nbh]
No image or wrong image!
Then Loading... [PL80IMG.zip]
After finding it it then says
Checking....[PL80IMG.zip]
But then remains in the bootloader after a minute or two when finished. Nothing happens for me to confirm with Vol+. I have no option to update?
If I choose Recovery from the bootloader it immediately just reboots to the bootloader again.
in fact whatever i do now it just goes straight back to the bootloader.
Ok, in this case i think you are out of luck. Sorry to say, but something seems broken, which even a ruu can't fix.
Just a thought, correct me if I'm wrong. Does the RUU require a working Recovery? If you remember my Recovery was previously corrupted I believe and before putting on TWRP there was no working stock recovery. Now TWRP is no longer available (because the bootloader is re-locked?) there is no working stock recovery to revert to in order to flash the RUU. If this is so is there a way to unlock the bootloader then put back a correct stock Recovery then re-lock it and use the RUU?
lucids said:
Just a thought, correct me if I'm wrong. Does the RUU require a working Recovery?
Click to expand...
Click to collapse
No, usually not. The Ruu has the stock file itself inside.
But, of course, you can try it. In this case you need to unlock bootloader again, then you can flash it with fastboot cmd.
I can upload the recovery.img if you want.
For the unlock you can use the already existing unlock_code.bin, i think.
Well it's worth a go I guess. Thank you that Recovery image would be very useful as I was unable to locate it or download from the app box link. My friend still uses his One SV so could come in useful at some point anyway.
I've re-Unlocked the Bootloader again and TWRP is still present and working when I select Recovery.
I'll wait for your new upload of the correct stock Recovery image and try with that.
Thanks again
lucids said:
Well it's worth a go I guess. Thank you that Recovery image would be very useful as I was unable to locate it or download from the app box link. My friend still uses his One SV so could come in useful at some point anyway.
I've re-Unlocked the Bootloader again and TWRP is still present and working when I select Recovery.
I'll wait for your new upload of the correct stock Recovery image and try with that.
Thanks again
Click to expand...
Click to collapse
Stock recovery k2ul Android 4.2.2
https://www.androidfilehost.com/?fid=385035244224390400
i tried to install the newest 5.1.11 in full ( as i am magisk rooted, twrp installed, and bootloader unlocked). i kept getting system ui crashes over and over and eventually, after so many, the phone just powers down by itself. I had tried clearing cache after going back into twrp. Rebooted. Same ui issue. Then i decided to restore a backup in twrp i had made a few weeks ago stored on internal memory. This was a bad idea. It said it restored successfully but upon reboot, i only get fastboot now. i think it is communicating with fastboot but when i try to fastboot boot twrp-3.2.1-0 (or 3.2.2-0) i get, "remote: Failed to load/authenticate boot image: Load Error". I do not know what to do and am hoping you guys can figure out how to fix this. Any attempt to enter recovery via buttons results in fastboot booting. restart is also fastboot.
This is what my phone says:
FastBoot mode
Product_name- sdm845
variant- sdm ufs
basband version-
serial- it's there
secure boot- yes
device state- unlocked
Don't know if this helps fastboot getvar all reports this:
C:\Adb\OnePlus 6 Files>fastboot getvar all
(bootloader) unlocked:yes
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3837
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) variant:SDM UFS
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x1B800B7000
(bootloader) partition-type:system_a:ext4
(bootloader) partition-size:system_a: 0xB2C00000
(bootloader) has-slot:modem:yes
(bootloader) has-slot:system:yes
(bootloader) current-slot:a
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:6
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:no
(bootloader) slot-retry-count:a:0
(bootloader) slot-unbootable:a:yes
(bootloader) slot-successful:a:no
(bootloader) slot-count:2
(bootloader) secure:yes
(bootloader) serialno: omitted
(bootloader) product:sdm845
(bootloader) max-download-size:536870912
(bootloader) kernel:uefi
all:
finished. total time: 0.047s
Is there anyone that has had this set of circumstances and got out of it? Any help is appreciated. There are some things i've seen that i can do but don't want to do further damage. Thanks to all for any and all help.
thejase said:
i tried to install the newest 5.1.11 in full ( as i am magisk rooted, twrp installed, and bootloader unlocked). i kept getting system ui crashes over and over and eventually, after so many, the phone just powers down by itself. I had tried clearing cache after going back into twrp. Rebooted. Same ui issue. Then i decided to restore a backup in twrp i had made a few weeks ago stored on internal memory. This was a bad idea. It said it restored successfully but upon reboot, i only get fastboot now. i think it is communicating with fastboot but when i try to fastboot boot twrp-3.2.1-0 (or 3.2.2-0) i get, "remote: Failed to load/authenticate boot image: Load Error". I do not know what to do and am hoping you guys can figure out how to fix this. Any attempt to enter recovery via buttons results in fastboot booting. restart is also fastboot.
This is what my phone says:
FastBoot mode
Product_name- sdm845
variant- sdm ufs
basband version-
serial- it's there
secure boot- yes
device state- unlocked
Don't know if this helps fastboot getvar all reports this:
C:\Adb\OnePlus 6 Files>fastboot getvar all
(bootloader) unlocked:yes
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3837
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) variant:SDM UFS
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x1B800B7000
(bootloader) partition-type:system_a:ext4
(bootloader) partition-size:system_a: 0xB2C00000
(bootloader) has-slot:modem:yes
(bootloader) has-slot:system:yes
(bootloader) current-slot:a
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:6
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:no
(bootloader) slot-retry-count:a:0
(bootloader) slot-unbootable:a:yes
(bootloader) slot-successful:a:no
(bootloader) slot-count:2
(bootloader) secure:yes
(bootloader) serialno: omitted
(bootloader) product:sdm845
(bootloader) max-download-size:536870912
(bootloader) kernel:uefi
all:
finished. total time: 0.047s
Is there anyone that has had this set of circumstances and got out of it? Any help is appreciated. There are some things i've seen that i can do but don't want to do further damage. Thanks to all for any and all help.
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 your solution lies here
tabletalker7 said:
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 your solution lies here
Click to expand...
Click to collapse
I saw this. Will i keep my data with this method?
thejase said:
I saw this. Will i keep my data with this method?
Click to expand...
Click to collapse
no, but if you can't even boot to TWRP then you have nothing left to save at this point.
Try booting the latest twrp (3.2.3.0) before giving up and wiping. If you can get to fastboot, you're not bricked.
iElvis said:
Try booting the latest twrp (3.2.3.0) before giving up and wiping. If you can get to fastboot, you're not bricked.
Click to expand...
Click to collapse
thanks for the suggestions but no dice.
According to your first posting, the phone knows that the boot partition on both your slots are a mess and can't load - you need the fastboot rom to make the phone start over and try again. Sorry buddy - I would like to save your data but it doesn't seem feasible at this point.
tabletalker7 said:
According to your first posting, the phone knows that the boot partition on both your slots are a mess and can't load - you need the fastboot rom to make the phone start over and try again. Sorry buddy - I would like to save your data but it doesn't seem feasible at this point.
Click to expand...
Click to collapse
That's alright. I appreciate the point in the right direction. Doing that fastboot method bat file that you suggested now... Thanks for the help.
thejase said:
That's alright. I appreciate the point in the right direction. Doing that fastboot method bat file that you suggested now... Thanks for the help.
Click to expand...
Click to collapse
tabletalker7 said:
According to your first posting, the phone knows that the boot partition on both your slots are a mess and can't load - you need the fastboot ROM to make the phone start over and try again. Sorry buddy - I would like to save your data but it doesn't seem feasible at this point.
Click to expand...
Click to collapse
So as it turns out that method worked using the bat file flash all fastboot. Though, not at first. When it first rebooted after the bat file finished flashing. system UI was still crashing. When you initially run the bat file at the beginning, it asks if you want to delete your data. First time around i said no, just to see what it would do. Well it booted, but kept getting that system ui crash that I had in the beginning of all this mess. I rebooted and this time chose to erase data and then it re-flashed all again (same bat file). Turns out, when it booted, same deal, system UI crash. So this time i was looking things up while the crashes where happening and then it just rebooted on its own (as it does with a number of system UI crashes in succession). When it came up it was that Chinese menu (which i assume to be download mode or something). Anyway, i chose English and it's a menu to clear dalvik and cache, system settings reset, and one other i can't remember. i did system settings then dalvik and finally, when i rebooted, it was like it was booting for the first time with no crashes. Only thing i can figure is that setting in the bat file at first launch actually didn't erase user data since when it booted, all my icons where there in the background. doing it "on device" in download mode seems to have worked. I am only adding this information as an f.y.i.. Thanks again for all your help, guys.
thejase said:
When it came up it was that Chinese menu (which i assume to be download mode or something).
Click to expand...
Click to collapse
That's stock recovery.
maigre said:
That's stock recovery.
Click to expand...
Click to collapse
Oh, ok. Funny thing is, I had never seen what that looked like as I immediately installed twrp from the time I bought it. Makes sense, though I still wonder why it booted to stock recovery after systemui crashing. Unless it senses the crashes and does that by default to clear system settings and data for a successful boot?
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.