i flashed using the unbrick tool so i could do a clean flash and have the official udates.
i ran program worked nice,all updates ran perfectly to the last released by lenovo,
here is my issue twrp recovery will flash through adb but wont stick,when i reboot to revcovery
it is always lenovo recovery no twrp.
please can anyone advise me
thank you
Related
I was on OOS community build 3.5.3 with modified twrp-3.0.2-19-oneplus3.
I wiped everything except internal storage after that I tried to flash official TWRP.
After installing official twrp via modified TWRP. Niether I can boot into my recovery nor able to install any recovery via fastboot.
it I use "fastboot flash recovery recovery.img"
after installing recovery with this command My bootloader get stuck then I have to again restart my bootloader.
please help
You're probably stil on 3.5.2 firmware which isnt compatible with official twrp. Try and get into fastboot and try flashing modified twrp again. Then reboot in recovery and flash 3.2.6 firmware (not the rom) from modified twrp. Then reboot and flash official twrp from recovery or in flashify app.
i had this problem the other day, fixed this by flashing the modified recovery from a post here turn it off the booted it up by holding vol down + power and somehow it worked i was able to go into twrp
innocentwoolf said:
I was on OOS community build 3.5.3 with modified twrp-3.0.2-19-oneplus3.
I wiped everything except internal storage after that I tried to flash official TWRP.
After installing official twrp via modified TWRP. Niether I can boot into my recovery nor able to install any recovery via fastboot.
it I use "fastboot flash recovery recovery.img"
after installing recovery with this command My bootloader get stuck then I have to again restart my bootloader.
please help
Click to expand...
Click to collapse
I have same issue it is called half-brick go to full brick post here (http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700)
read whole post and prefer method 2 it will work like charm and i got when i am installing freedom os CE version and if it work then thank me
are you stuck with a black screen when booting to recovery if yea then wits the same situation i was in.
http://forum.xda-developers.com/showpost.php?p=68691560&postcount=56 that recovery helped me
Seagorilla2 said:
You're probably stil on 3.5.2 firmware which isnt compatible with official twrp. Try and get into fastboot and try flashing modified twrp again. Then reboot in recovery and flash 3.2.6 firmware (not the rom) from modified twrp. Then reboot and flash official twrp from recovery or in flashify app.
Click to expand...
Click to collapse
yes.. tried that only and it worked...
thanks
danxtian said:
are you stuck with a black screen when booting to recovery if yea then wits the same situation i was in.
http://forum.xda-developers.com/showpost.php?p=68691560&postcount=56 that recovery helped me
Click to expand...
Click to collapse
that helped me to thanks
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!
Hi,
i have a Helium 128G and got some problems with the radio. Currently i was on 8.1.5 following the guide
http://forum.xda-developers.com/mi-max/how-to/guide-install-global-miui8-root-t3435594
and i also officially unlocked the bootloader after this.
So i thought - to flash a new radio - it would be fine to just flash the 8.1.9 over the updater method. Unfortunately the phone rebooted in TWRP and flashed something. After this the reboot took >10 Minutes so i rebooted into TWRP and found the internal storage is encrypted now. So all data lost. Great!
Nevertheless i tried to flash 8.1.9 via Mi Flash. This worked and the phone booted but after i flashed TWRP it won't boot anymore. What is this? Is it even possible to run 8.1.9 rooted with twrp?
Thanks for your suggestions, i'm really pissed at the moment
EDIT: My TWRP Backup with 8.1.5 worked and now i have the radio from 8.1.9 and the rom 8.1.5. Nevertheless i would like to have 8.1.9 rooted with twrp
Hi! I've also experience your problem, did your phone entered recovery mode after flashing TWRP? if not try flashing the 8.1.2 ROM through EDL (power+vol up+vol down) then after letting the first boot finish flash TWRP. Hope this help
I'm not sure but at one point i saw the xiaomi recovery picture!? Now it works with my 8.1.5 backup again but is it really that heavy to just install a current version when on twrp and root!? i'm officially unlocked for that.
installed twrp then tried to install a custom rom crdroid 5.3 I belive encountered error, then tried to install official firmware again got stuck in bootloop with horizontal beam.managed to install twrp again so now how do I install a custom rom or get back to official firmware. I have pcwith adb tools and have twrp installed on my device. think I wiped everything first time installing rom.
how to get my device with a working os and no bootloop?
xdadaizzz said:
installed twrp then tried to install a custom rom crdroid 5.3 I belive encountered error, then tried to install official firmware again got stuck in bootloop with horizontal beam.managed to install twrp again so now how do I install a custom rom or get back to official firmware. I have pcwith adb tools and have twrp installed on my device. think I wiped everything first time installing rom.
how to get my device with a working os and no bootloop?
Click to expand...
Click to collapse
You need stock recovery and bootloader unlock for original rom image flashing, for all other roms, you must follow the instructions without any hickups.
Hello,
i'm stuck in a particular situation: i can use fastboot and i can flash recoveries but none of them can succesfully flash a rom. i want to go back to the stock Realme UI, my device is RMX1993.
i tried to follow the guide (https://forum.xda-developers.com/realme-x2/how-to/to-stock-rom-howto-t4014773) but the last recovery (rmx1993-sde20-stock_recovery-c05) can't flash neither RMX1993EX_11_OTA_1040_all_tSZ3Sf5A77NS nor RMX1993EX_11_OTA_1050_all_loALrMDyMrbs.
tried to flash trough orangefox or the last twrp that support ozip decription but the result is a "succesful flash" but a phone that does not go over the boot screen and it reboot.
i succesfully installed color os trough the proper old stock recovery and it said the installation was succesfull, but the problem was the same.
someone know where could be the problem?
You need to successfully flash Android 10 (Realme UI 1.0) before you can flash custom Android 10 roms.
Have you tried this guide: https://forum.xda-developers.com/realme-x2/help/how-to-flash-q-firmware-based-roms-t4115987
As for why your colorOS back up is not working i'm not quite sure...have you wiped your cache before booting to the color os backup?