Hi,
Asked a bit everywhere but get answer ...
Got Apollopro unlocked, magsk and TWRP (whyle beta 1) and when download the update and rebooting, I'm stuck in the TWRP booting image ... nothing happened, Have to force reboot i no update installed.
Try just to reboot into twrp, same thing, stuck at the the twrp boot page.
WHy shall I do whitout loosing data ?
Thanks
No one ?
Related
Hello guys,
Just got my m9 a few hours ago, decided to root,s-off etc
Anyway, I did something stupid and Im stuck on the android logo.
Here is what I did.
-I updated the device through the stock recovery, there was another update but I didnt install i.
- unlocked the bootloader, phone rebooted and was working fine
-installed costume recovery(TWRP), I didnt boot into it because there wasnt and option like in the m8 to boot in recovery from bootloader.
-I reset the device and installed the update(stupid move I knew the stock recovery is not there)
- I got into TWRP and the updated failed so I had the SUbinary.zip so I plashed it and decided to reboot
-Here I got a note that theres no OS installed so I installed android Revolution, I placed it in the sdcard prior
- after flashing it I pressed on reboot yet I get no OS installed and now im stuck on the HTC logo.
BTW I can boot into boot loader but it says sd card not mounted (64GB)
Edit:
I entered into recovery, flashed AR again,its installs everything normally but I realized on the installation log last line : set_metadata_recursive: some changes failed
still I get no OS installed
I got it working now. Anyone whos having this problem just use the beta recovery because the official one is broken
here's a like https://basketbuild.com/devs/Captain_Throwback/One (M9)/Recovery
just flash it normally and install the rom again.
now i will have to go back to stock recovery and download the OTA the flash TWRP again -.-
will the OTA work on the ARHD and stock recovery or thats not possible?
mr.dj26 said:
Hello guys,
I got it working now. Anyone whos having this problem just use the beta recovery because the official one is broken
here's a like https://basketbuild.com/devs/Captain_Throwback/One (M9)/Recovery
just flash it normally and install the rom again.
now i will have to go back to stock recovery and download the OTA the flash TWRP again -.-
will the OTA work on the ARHD and stock recovery or thats not possible?
Click to expand...
Click to collapse
I dont think the OTA will work.
either find the latest full RUU and flash it, or an older RUU, flash it, then do all the available OTAs.
Then redo TWRP and ARHD.
x51 said:
I dont think the OTA will work.
either find the latest full RUU and flash it, or an older RUU, flash it, then do all the available OTAs.
Then redo TWRP and ARHD.
Click to expand...
Click to collapse
hey there, thanks for the reply.
I think ill do the s-off first then ill download the RUU like this guy http://forum.xda-developers.com/one-m9/help/tut-ota-successfully-1-32-401-15-to-1-t3091911
i wish i updated before
I did the same thing twrp no OS installed and restarted now I am stuck at the htc logo and I can't get it to restart. Please help?
I tried power and volume down and it's not responding.
edit:
pressed all the buttons and got into recovery. went into download mode and updated twrp and reflashed android hd. working now.
thunderwolf333 said:
I did the same thing twrp no OS installed and restarted now I am stuck at the htc logo and I can't get it to restart. Please help?
I tried power and volume down and it's not responding.
edit:
pressed all the buttons and got into recovery. went into download mode and updated twrp and reflashed android hd. working now.
Click to expand...
Click to collapse
Thats good to hear, sometimes TWRP will say that there isn't any OS installed but actually there is just reboot the device.
After updating through the OTA I installed ARHD and I got the same error again with the latest recovery. I think its because when I did wipe the data there root directory is changing make the phone unable to boot or there is a problem with the rom although it flashed before the update.
Here is a fix http://forum.xda-developers.com/one...h-recovery-t3066720/post59934542#post59934542
If it didn't work try to format data in the recovery and reboot. Make sure you have a ROM or back up on an SD card.
Since your phone is running I would suggest you to S-off because from what I understand is RUU (for Europe) will only work with S-off
http://forum.xda-developers.com/one-m9/general/htc-one-m9-dump-t3060545
hope this helps others
Edit:
I installed some LG Drivers from a root article and now the phone is recognized. I can update to V20G and test it again, hope it works!
Hello!
I was running CM14.1 on my LG G4 and a few days ago I decided to install a new update but from within the phone itself. Sadly, it just rebooted to the recovery and didn't install anything. And from there, it always rebooted into the recovery no matter what I did. I also did a full wipe and installed CM14.1 clean but it still rebooted to the recovery and didn't want to go past that. I made a Reddid thread - https://www.reddit.com/r/cyanogenmod/comments/5gcap3/g4_h815_cm_141_help_i_cant_boot_outside_of/.
So I got help with that - I got into Download Mode and flashed the stock software via LGUP. Sadly, after I did this, I can no longer install a custom recovery. The phone is not rooted and LGUP and LG Bridge don't recognize the device anymore and the phone says there isn't a new update available but it's on the 5.1 stock ROM.
Whenever I flash the TWRP image via fastboot and I reboot into recovery, it doesn't boot into TWRP but it boots into some kind of other fastboot mode. And I've tried to issue `fastboot boot twrp-x-x-x.img` but it fails to do so and shows `FAILED (remote: dtb not found)`.
Is there a way to fix this so I can flash CM again?
Thanks in advance!
Peshyy said:
Hello!
I was running CM14.1 on my LG G4 and a few days ago I decided to install a new update but from within the phone itself. Sadly, it just rebooted to the recovery and didn't install anything. And from there, it always rebooted into the recovery no matter what I did. I also did a full wipe and installed CM14.1 clean but it still rebooted to the recovery and didn't want to go past that. I made a Reddid thread - https://www.reddit.com/r/cyanogenmod/comments/5gcap3/g4_h815_cm_141_help_i_cant_boot_outside_of/.
So I got help with that - I got into Download Mode and flashed the stock software via LGUP. Sadly, after I did this, I can no longer install a custom recovery. The phone is not rooted and LGUP and LG Bridge don't recognize the device anymore and the phone says there isn't a new update available but it's on the 5.1 stock ROM.
Whenever I flash the TWRP image via fastboot and I reboot into recovery, it doesn't boot into TWRP but it boots into some kind of other fastboot mode. And I've tried to issue `fastboot boot twrp-x-x-x.img` but it fails to do so and shows `FAILED (remote: dtb not found)`.
Is there a way to fix this so I can flash CM again?
Thanks in advance!
Click to expand...
Click to collapse
The bootloop to recovery is a known issue of one the December nightlies of CM 14. Head over to the CM thread and search for bootloop and twrp. They provided a solution to solve this too.
Besides that: which twrp version do you tried to fastboot? H811 or h815? Taken from the official download site?
.
steadfasterX said:
The bootloop to recovery is a known issue of one the December nightlies of CM 14. Head over to the CM thread and search for bootloop and twrp. They provided a solution to solve this too.
Besides that: which twrp version do you tried to fastboot? H811 or h815? Taken from the official download site?
.
Click to expand...
Click to collapse
twrp-3.0.2-1-h815.img, H815 as the title says and from the official website as I've always done. As for the thread - I don't have TWRP and I can't even flash it as I've written in my post. That's what I'm struggling with.
Edit:
I installed some LG Drivers from a root article and now the phone is recognized. I can update to V20G and test it again, hope it works!
I was running an unlocked one plus 3 on OxygenOS 4.0.2 (Android Nougat) and have TWRP installed. As 4.0.3 got released yesterday, i tried installing it today but i accidentally hit install on the OTA update setting which caused my phone to reboot. Now my phone won't boot into the os, i get a black screen after 'powered by Android'. I tried getting into Recovery however i get the same response, a black screen. I do not think it is hardbricked as the Fastboot still works and when i go into fashtboot it states that the OEM is 'unlocked'. I have personal data on this device pls can someone help. I do not know what i should do> How do i boot into recovery without crashing?
Is it possible to install twrp again with the PC? I had once also the same problem, install it again and after that it booted again into recovery.
Just install TWRP from fastboot, then you'll have access to internal storage by TWRP
It's happening because it's trying to send you to recovery which is twrp 3. 0.4-1which is bugged so just go to fastboot and flash twrp 2.0.4-1 and then try booting in.. You can even update the phone by flashing the update zip by oneplus from recovery
Hello Everyone I am hoping there is a solution to this however I have been unable to find anything.
I flashed the latest OTA image via sideload and everything was fine until I tried to install TWRP. When trying to install the latest TWRP I could find ( 3.1.0-0RC2 ) my phone would then boot loop. I tried this process several times and each time after installing my phone would boot loop for 10 minutes until I forced it into fastboot, fast booted the TWRP image, and finally sideload the OTA once again.
I have seen a couple threads which I believe indicate that May update changed/broke something with the bootloader but I will be honest I
haven't read into it much.
This is on a Google version of the device with the bootloader unlocked. (failed to mention that).
Thanks in advance.
Bijiont said:
Hello Everyone I am hoping there is a solution to this however I have been unable to find anything.
I flashed the latest OTA image via sideload and everything was fine until I tried to install TWRP. When trying to install the latest TWRP I could find ( 3.1.0-0RC2 ) my phone would then boot loop. I tried this process several times and each time after installing my phone would boot loop for 10 minutes until I forced it into fastboot, fast booted the TWRP image, and finally sideload the OTA once again.
I have seen a couple threads which I believe indicate that May update changed/broke something with the bootloader but I will be honest I
haven't read into it much.
This is on a Google version of the device with the bootloader unlocked. (failed to mention that).
Thanks in advance.
Click to expand...
Click to collapse
Please read the other Posts about this
Flash the bootloader from april.
****************************
Download last months 7.1.2 factory image.
Extract it and find "bootloader-marlin-xxxxblahblah.img".
Rename it to "bootloader.img" for simplicity's sake, then move it to the side.
:Flash-all" the latest factory image, after its done stay in fastboot.
Run "fastboot flash bootloader_a bootloader.img" from wherever you moved the file to
Disregard if "partition_a" isnt your primary, once the command is ran it will auto flash to the primary partition.
Boot and setup, reboot back to bootloader.
Boot and install twrp, then reboot to recovery.
Delete fstab.marlin in main directory, then flash preferred supersu (i use 2.79 sr3).
Reboot to system and your done. from here reboot to recovery or bootloader to flash your preferred kernel and mods.
Was able to get this all sorted out.
If anyone else happens to see this thread with the same issues and missed the April bootloader deal you can find a good overview Here
To get the April bootloader image which is something I have never loaded myself you need to download the Factory Image from April then extract it. Inside there you will see the bootloader image.
Hope this helps anyone else who didn't read far enough into this issue.
My devices was rooted before I update it to v10.3.2. After I updated the phone the root was removed. When I tried to boot to twrp to root my device again, it stuck on mi logo after the fastboot logo disappear.
Please help me. I want to root my phone again but I cant ??
Same. I can't downgrade either because it would trigger ARB and break my phone. Very annoying.
No problem to in booting twrp . I was on 10.3.2 and flashed twrp recovery.. Make sure to download proper twrp (I used twrp recovery from mycats)
Yeah. I'm facing same issue also tried above twrp and Redwolf as well but no luck.. somebody pls help
same as @SunilSuni:
On my side @MyCats TWRP 3.1.1-3 works flawless for me with encrypted Data partition:
https://forum.xda-developers.com/re...t/recovery-team-win-recovery-project-t3940703