Related
Okay, so I tried my best to search the forums and read the Q+A first, but the suggestions I've found so far didn't help me solve my problem.
I started with Hasoon200's tool kit and successfully unlocked the boot loader. Then, however, I got stuck at installing CWRM (it just wouldn't boot into recovery after installing). So I gave it a try with the "One X one Click" tool kit. I downloaded the n3okernel v34 and -modules as well as the newest nightly build of Cyanogen Mod (cm-10.1-20130414-NIGHTLY-endeavoru).
Now my HOX is caught in a boot loop. No matter which option I choose (fastboot / hboot, recovery, factory reset), it'll always go to the white HTC screen and stay there. Since Q+A's Q11 mentions it: yes, the last time I could boot into the OS (then still the stock image) I disabled fast boot in power settings.
Currently I can only access my HOX via fastboot, I already got a stock image and extracted the boot + recovery images, which I then flashed with the fastboot utility, as suggested in the Q+A's Q9. I erased the cache and rebooted to no avail. I also tried the firmware executable (RUU_ENDEAVOR_U_ICS_40_O2_DE_1.26.207.2_Radio_1.1204.90.13_release_251288_signed) to no avail.
Q+A's Q15 suggests sideloading via adb, but adb won't recognize my device.
I've also relocked the bootloader, this was suggested in another online ressource after flashing the stock boot+recovery images.
The phones HBOOT Version is 1.36.0000. I've noticed a different radio version than the one mentioned in my downloaded RUU; phone says 5.1204.162.29, downloaded file says 1.1204.90.13. I've not yet found a working download link with the right version number.
Please help.
Unlock it, make a full wipe in the custom recovery, install cm10.1, install gapps, flash the boot.img from the cm10.1 Rom and reboot.
So
Unlock it, flash a custom recovery (if you havent got one). If you still have trouble entering it you do this command in the bootloader
Fastboot erase cache
Mr Hofs said:
Unlock it, make a full wipe in the custom recovery, install cm10.1, install gapps, flash the boot.img from the cm10.1 Rom and reboot.
So
Unlock it, flash a custom recovery (if you havent got one). If you still have trouble entering it you do this command in the bootloader
Fastboot erase cache
Click to expand...
Click to collapse
Unlocking the bootloader works, but I'm not able to enter the recovery mode. It only shows a black screen (see attached picture).
EDIT: ok, wait... after flashing the clockwork recovery, I'm now getting into recovery mode. Will now try the next steps you suggested and give feedback later. Thanks a lot so far!
Press the Power and Volume down buttons which will take you the the hboot screen. From there select fastboot and flash a custom recovery like CWM via fastboot.
Now select hboot again and then select recovery!
Okay, so I successfully flashed CWM. I'm now able to boot into recovery. I also succeeded in flashing a boot.img which i took from cm-10.1-20130414-NIGHTLY-endeavoru.zip
c:\One\One\Data>fastboot flash boot boot.img
sending 'boot' (4960 KB)...
OKAY [ 0.684s]
writing 'boot'...
(bootloader) Format partition LNX done
OKAY [ 0.498s]
finished. total time: 1.186s
Now - when selecting hboot - the phone gets to another screen, the one where it displays the "HTC One" logo; I tried flashing the CM-image using fastboot (adb still doesn't work), but got following error message:
c:\One\One\Data>fastboot flash /sdcard update.zip
sending '/sdcard' (200098 KB)...
OKAY [ 25.507s]
writing '/sdcard'...
FAILED (remote: not allowed)
finished. total time: 25.716s
So close, yet so far...
So you have a working CWM installed right?
After flashing the boot.img... do "fastboot erase cache"
now go to CWM(recovery) and mount your sd card... copy the CM10ROM.zip and the gapps.zip to your HOX...
after that select wipe data and then wipe dalvic and cache...
Now select install zip from SD and install the ROM and then the gapps... reboot!
The problem is that I can't - or could'nt - transfer files any other way than using fastboot. However, I've now flashed Team Win TWRP2, and finally I'm able to access my phone over adb or just mount it and access it via explorer. Phew.
FINALLY!
So, if another noob like me finds this thread in the future...
After installing the TWRP2 recovery with flashboot flash twrp2.img, then booting into recovery and mounting my device, I was able to copy the CM-ROM-zip file onto the HOX. Then I rebooted into fastboot again and flashed the boot.img from aforementioned zip-file using "fastboot flash boot boot.img".
Booted again, selected the recovery system, installed ROM from zip file.
I'm getting too old for this ****. Almost had a heart attack when I thought I had bricked my phone. Thanks everyone for holding my hand, I appreciate it.
Good mate !
CASE CLOSED !
my m9 randomly rebooted, and now its stuck in a bootloop, i'm able to get out of it and into download, and from there into twrp and the bootloader, but whenever i try to flash any of the Europe RUU's i get multiple errors
I am -
unlocked, but cant relock for some reason
s-on
have the latest 1.40.401.8 software
have twrp, but cant wipe data or do anything in it, just says failed to mount for data, cache etc
trying to reflash 1.40.401.8
i tried -
htc_fastboot flash zip (zip name).zip but results in the fail90 with please flush immediately text, it just repeats this oer an over with no other result even if i leave it for a while
fastboot oem lock just says failed, too many links and reboots
fastboot flash recovery recovery.img, stock recovery, says its succeeded but it still boots twrp
fastboot boot reocvery .img says booting but does nothing
tried to flash a different ruu but just says zip read error, cant open the zip
-
thanks in advance for you help, much appreciated
eggyfish said:
my m9 randomly rebooted, and now its stuck in a bootloop, i'm able to get out of it and into download, and from there into twrp and the bootloader, but whenever i try to flash any of the Europe RUU's i get multiple errors
I am -
unlocked, but cant relock for some reason
s-on
have the latest 1.40.401.8 software
have twrp, but cant wipe data or do anything in it, just says failed to mount for data, cache etc
trying to reflash 1.40.401.8
i tried -
htc_fastboot flash zip (zip name).zip but results in the fail90 with please flush immediately text, it just repeats this oer an over with no other result even if i leave it for a while
fastboot oem lock just says failed, too many links and reboots
fastboot flash recovery recovery.img, stock recovery, says its succeeded but it still boots twrp
fastboot boot reocvery .img says booting but does nothing
tried to flash a different ruu but just says zip read error, cant open the zip
-
thanks in advance for you help, much appreciated
Click to expand...
Click to collapse
Did you try the sd-card method? Rename the RUU to 0PJAIMG.zip, copy it into the root directory of a sd-card that is formatted to fat32 and not bigger than 32gb, put the card into your phone, boot into download mode and follow the instructions on the phone's screen. (Where did you actually get the 1.40.401.8 RUU? The sources I know provide the OTA update and not the RUU. So maybe you know a source I haven't heard of before.)
The output during relocking my old One S and/or my fathers One SV always stated the "too many links" error, too. Nevertheless the bootloader was always relocked after the reboot. (I've never relocked my M9 because there was no need to do so since I bought it.)
Fastboot boot recovery doesn't work on the M9. That's the reason why we need to grab the stock recovery from RUUs or OTAs instead of backing it up before we start flashing.
What TWRP version are you running? I think that error only existed in one of the older versions and is fixed in the newest one.
To replace TWRP with the stock recovery you can try this: Make a backup with only "recovery" checked. Rename the stock recovery to recovery.emmc.win. Replace the recovery.emmc.win in your TWRP backup with the renamed stock recovery and restore the backup. If you now reboot your phone TWRP will be replaced.
Flippy498 said:
Did you try the sd-card method? Rename the RUU to 0PJAIMG.zip, copy it into the root directory of a sd-card that is formatted to fat32 and not bigger than 32gb, put the card into your phone, boot into download mode and follow the instructions on the phone's screen. (Where did you actually get the 1.40.401.8 RUU? The sources I know provide the OTA update and not the RUU. So maybe you know a source I haven't heard of before.)
The output during relocking my old One S and/or my fathers One SV always stated the "too many links" error, too. Nevertheless the bootloader was always relocked after the reboot. (I've never relocked my M9 because there was no need to do so since I bought it.)
Fastboot boot recovery doesn't work on the M9. That's the reason why we need to grab the stock recovery from RUUs or OTAs instead of backing it up before we start flashing.
What TWRP version are you running? I think that error only existed in one of the older versions and is fixed in the newest one.
To replace TWRP with the stock recovery you can try this: Make a backup with only "recovery" checked. Rename the stock recovery to recovery.emmc.win. Replace the recovery.emmc.win in your TWRP backup with the renamed stock recovery and restore the backup. If you now reboot your phone TWRP will be replaced.
Click to expand...
Click to collapse
i'm running 2.8.7.0 twrp and neither the sd card method nor backup method worked for me, and bootloader is still unlocked with that output, twrp just says failed when i try and do a backup, and reboots when i try to flash a rom, do you think the phones memory is corrupted or something?, i just cant seem to do anything
eggyfish said:
i'm running 2.8.7.0 twrp and neither the sd card method nor backup method worked for me, and bootloader is still unlocked with that output, twrp just says failed when i try and do a backup, and reboots when i try to flash a rom, do you think the phones memory is corrupted or something?, i just cant seem to do anything
Click to expand...
Click to collapse
There is a newer version (2.8.7.1-CPTB-B1) which can be found in the beta version section here. Furthermore there is a stock backup provided in this thread that corresponds to your firmware version. Try to update TWRP and then to restore the backup.
Edit (Just to answer my own question from my previous post): The second Link provides a 1.40.401.8 RUU, too.
Flippy498 said:
Did you try the sd-card method? Rename the RUU to 0PJAIMG.zip, copy it into the root directory of a sd-card that is formatted to fat32 and not bigger than 32gb, put the card into your phone, boot into download mode and follow the instructions on the phone's screen. (Where did you actually get the 1.40.401.8 RUU? The sources I know provide the OTA update and not the RUU. So maybe you know a source I haven't heard of before.)
The output during relocking my old One S and/or my fathers One SV always stated the "too many links" error, too. Nevertheless the bootloader was always relocked after the reboot. (I've never relocked my M9 because there was no need to do so since I bought it.)
Fastboot boot recovery doesn't work on the M9. That's the reason why we need to grab the stock recovery from RUUs or OTAs instead of backing it up before we start flashing.
What TWRP version are you running? I think that error only existed in one of the older versions and is fixed in the newest one.
To replace TWRP with the stock recovery you can try this: Make a backup with only "recovery" checked. Rename the stock recovery to recovery.emmc.win. Replace the recovery.emmc.win in your TWRP backup with the renamed stock recovery and restore the backup. If you now reboot your phone TWRP will be replaced.
Click to expand...
Click to collapse
oh and my internal storage is reading as zero, i cant reformat it either, every action i preform in twrp just fails
and i still cant flash twrp
i get this -
writing 'recovery'...
(bootloader) HOSD CL#549783
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 2.078s]
finished. total time: 5.047s
eggyfish said:
oh and my internal storage is reading as zero, i cant reformat it either, every action i preform in twrp just fails
Click to expand...
Click to collapse
Well, that definitely sounds like your phone's memory is corrupted. I don't know whether there is another method to help you than sending it to HTC's repair service. Are you sure your storage isn't just full (since the flashing output seems to be ok [see below])?
Edit:
eggyfish said:
i get this -
writing 'recovery'...
(bootloader) HOSD CL#549783
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 2.078s]
finished. total time: 5.047s
Click to expand...
Click to collapse
I actually don't see any error in that output. Everthing is the way it should be.
Flippy498 said:
Well, that definitely sounds like your phone's memory is corrupted. I don't know whether there is another method to help you than sending it to HTC's repair service. Are you sure your storage isn't just full (since the flashing output seems to be ok [see below])?
Edit:
I actually don't see any error in that output. Everthing is the way it should be.
Click to expand...
Click to collapse
hmm, thats strange as it didnt update, i get the same readout when i flash stock, but it stsys on twrp. sureley it cant be full as a ruu flash wipes your data, i think i'll try get a repair from htc, thanks for your help
I want to install Supersu using TWRP on my 360 gen1 (LCA44B).
I've built a USB cable like RootJunky's Guide and unlocked the 360 (fastboot oem unlock). The bootloader shows UNLOCKED STATUS CODE 1.
However, I can neither flash TWRP (fastboot flash recovery twrp.img), the flash process says successful (sending recovery... OKAY, writing recovery... OKAY finished), but the boot into Recovery shows TWRP does not exist.
And when I load TWRP (fastboot boot twrp.img) this has no access to the system partition.
What is wrong, what can I do?
Hi All,
I am facing issues with flashing any custom recovery on my oneplus 3 device running on open beta 30.
Everytime I flash a recovery, it says finished without an error but throw me back to stock recovery, After searching some available option I can across several links and tried following suggestions so far:
1) used "Fastboot boot recovery.img": Error "FAILED (remote: bootimage header fields are invalid)"
Thought the downloaded recovery file is corrupted, downloaded it from official site and other locations, all with same hash value and same problem
2) Searched an option to disable "update cm recovery", unable to location this setting on my device
3) Tried to flash recovery then poweroff and then reboot to recovery using power button and volume down key, did not worked.
recoveries I have tried:
blu_spark TWRP and original TWRP
device-info:
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) Have console: false
(bootloader) Selinux type: <none>
(bootloader) Boot_mode: normal
(bootloader) Kmemleak_detect: false
(bootloader) force_training: false
Anyone faced similar issue or found a way to fix this ?
Note: Device not rooted, bootloader unlocked.
You could try "fastboot format userdata" in fastboot mode. Backup your data first. I think it was something with encryption. Same case with my friend.
oopstairs said:
You could try "fastboot format userdata" in fastboot mode. Backup your data first. I think it was something with encryption. Same case with my friend.
Click to expand...
Click to collapse
Encryption is for the data partition not the recovery one. Are you using correct adb drivers? Works all fine here.
Puddi_Puddin said:
Encryption is for the data partition not the recovery one. Are you using correct adb drivers? Works all fine here.
Click to expand...
Click to collapse
Yes, I have verified ADB and fastboot on another device, its working fine.
I did tried two different systems for OP3 device, Ubuntu and windows. Same result in both cases, no success.
anandpandey said:
Yes, I have verified ADB and fastboot on another device, its working fine.
I did tried two different systems for OP3 device, Ubuntu and windows. Same result in both cases, no success.
Click to expand...
Click to collapse
Which recovery are you trying to flash?
Puddi_Puddin said:
Which recovery are you trying to flash?
Click to expand...
Click to collapse
recoveries I have tried:
blu_spark TWRP and official TWRP
Try:
fastboot flash recovery recovery.img
cmnaka said:
Try:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Thanks, that was the first thing i tried.
anandpandey said:
Thanks, that was the first thing i tried.
Click to expand...
Click to collapse
Did you try flashing SuperSU immediately after flashing TWRP and before booting into system?
When I flashed TWRP alone, I could boot back into TWRP but after booting into system, the next boot to recovery will take me to the stock one. I solved it by flashing SuperSu immediately after flashing TWRP.
tnsmani said:
Did you try flashing SuperSU immediately after flashing TWRP and before booting into system?
When I flashed TWRP alone, I could boot back into TWRP but after booting into system, the next boot to recovery will take me to the stock one. I solved it by flashing SuperSu immediately after flashing TWRP.
Click to expand...
Click to collapse
The problem with this approach is that I cound never reach to TWRP so to flash SuperSu or Magisk.
Soon after I flash TWRP, the repory enters into a loop.
Still not able to flash a custom rom, any other suggested options ?
This is a nonsense answer but can try , Rename to twrp or anything else other than recovery.img ( may be stock confused with same name )
anandpandey said:
Still not able to flash a custom rom, any other suggested options ?
Click to expand...
Click to collapse
Told you already to flash SuperSu. Don't use TWRP to flash SuperSu. Use adb.
If I were you, I would wipe system, data, Dalvik and cache and flash the ROM first, all using adb. Then boot into the ROM. Then using adb, flash blu_spark's TWRP v 8.61 and immediately thereafter flash SuperSu v 2.79 SR5, again using adb. Then boot into TWRP and then into system.
I after getting the beta31 I ran out of dash charger and also could not get the recovery oos
so I went back to 5.0.1 and did not go back to giving the cherzer dash. I got now I put the beta 31 and firmware of beta 30
Hi,
I have a Nexus 5X that was on the latest 8.1 firmware, and I successfully downgraded to the latest 6.0.1 firmware by unlocking the device and flashing everything separately. Here's what I did
Enable OEM unlock in Developer settings
Reboot to boot loader
fastboot flashing unlock
fastboot flash boot boot.img
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flashing unlock (had to do this cos after rebooting, device is locked again)
fastboot flash radio radio.img
fastboot flash recover recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot reboot
After this, I get the "Your device is corrupt. It can't be trusted and may not work properly" boot up message, but continue anyway, after which the device boots up and I set up the new device as per normal.
Then, I tried to flash TWRP in order to install Magisk. It is during this step that the device is stuck in the bootup process with the 4 colorful circles. Here's what I did
Reboot to boot loader
fastboot flash recover twrp-recovery.img
Reboot to recovery to check TWRP has been installed (it has)
Reboot to system (stuck in bootup!)
How can I get it to boot up again?
I ended up waiting for the battery to drain and the device to shutdown.