i have lg p765 with unlocked bootloader (just yesterday). After rooting the phone I installed cwm recovery 6.0.1.9 by artas using recovery installer.
Now as kk roms work only on 6.0.4.x I tried to flash new recovery many times but after flashing new recovery phone directly boots into recovery after 2-3 seconds of LG logo. So I have to restore using my previous backup.
So even after unlocking the bootloader I am unable install roms.
Please help ... How to fix it?
Can anybody give me working recovery and how to use it ?(for my older recovery I had to press vol down button after blinking of lights)
Tablet is rooted. Tablet has unlocked bootoader.
ROM Manager reports that I have recovery installed - both TWRP and ClockwordMod Recovery 5.8.3.4.
I want to update to 4.4.2 but when I go to try to boot into recovery, via ROM Manager or just manual hold volume down and power, I get the dead Android on his back with a red exclamation. No matter what recovery I try I get this.
Any thoughts on how to get out of it?
Ok.. I used this process to successfully flash the FlatLine CWM Recovery! Which I can now boot into that recovery via RCK selection and recovery bootup (power + vol down key)!
Not sure why the other recoveries were borked... but the key is the FlatLine recovery allows me to boot into recovery.
So this allows one to at least boot into a recovery and make a backup.
BUT this will not, I found out, allow me to install 4.4.2 (CM11) since you must use a TWRP or CWM recovery to install 4.4.2 (CM11) as FlatLine will not allow it
So then I use the same above Fastboot method to push a CWM recovery for the TF201 - fresh download of 5.8.3.4 - since I need a CWM recovery to intall the 4.4.2 (CM11) and... no joy. I push it by fastboot, boot into recovery, select RCK and it says it is going to "booting recovery kernal image" and then just hangs.
so still stuck. Any thoughts? I need to get to a kit kat and tf201 compatible CWM or TWRP recovery to flash the new ROM but I am stuck. I can only boor into the FlatLine recovery, but that does no good now.
So.... I opted to install TWRP 2.7.0.0 and that installed. I was able to boot into it, backup, and then tried it all again and.... FAIL!!
I get the same failed error... ugh!
So a ROM Manager install of 5.8.3.4 CWM fails to even boot
So a Fastboot install of 5.8.3.4 CWM fails to even boot
So a Fastboot install of TWRP 2.7.0.0 boots but fails to allow the 4.4.2 (CM11) install
So a Fastboot install of FlatLine boots but fails to allow the 4.4.2 (CM11) install
http://wiki.cyanogenmod.org/w/Tf201_Info
" Note: Support Status
This device does not support the newest version of CyanogenMod. This may be due to hardware limitations or simply because development is not yet complete. The last version officially supported was based on the jellybean branch of CyanogenMod. "
I believe you cannot run kitkat cyanogenMod as far as I know because you need cwm 6.0.+ version that isn't there . However there is a method to install kitkat on tf201 . I say so because I am running latest version of cyanogenmod snapshot m8 android 4.4.4 on my tf201 . There is just a simple matter of flashing recovery for tf300t ( well when I say simple ... ) on your tf201 .
http://forum.xda-developers.com/showthread.php?t=2773812
take a look at the link above . To install crombi-kk you flash twrp recovery version 2.7.0.1 (I think check the version I don't remember) . however there is no such version for tf201 . I never installed the actual rom but I played around and notice after doing step 2,3,then 2 again (in crombi-kk upgrade instruction) my device won't run cwm for tf201 but works fine with tf300t version of cwm .
I am talking from experience and there is always a chance of bricking as this is not an official guide but I think its what I did .
I was on twrp latest version of tf 300t and I installed cm snapshot m8 android 4.4.4 for tf300t device successfully . after using the rom for a while I noticed hangs when your device was on sleep and you wanted to wake the device , it just wouldn't turn on which forced me to hold power for like 5-10 sec to force a reboot.
I solved this by flashing cwm 6.0.4.7 for tf300t via fastboot . Again seems like development for tf201 and also tf300t is going to hell . so you won't find this version of recovery for tf300t on cwm site .However if you google latest kitkat recovery for tf300t or smthing like that I'm sure you will find it . These I think are ports from other people than acutal cwm team ...
One thing is for sure ... Cyanogenmod cm11 require cwm 6.0.+ or twrp 2.7.0.1 ...
Edit : as always do a backup ... and MOVE IT OUT of internal SD since for some reason it formatted all my data on internal plus my backups ... I messed around with more stuff though . but just in case be prepared for a formatted internalSD ...
I think I bricked it for good this time
I now can no longer fastboot in, so I cannot change recovery apps. I can boot into recovery - TWRP.
I boot up and I no longer have the USB plugin icon and fastboot will just no longer allows me to push a new recovery - says no device present despite having done it 20 times earlier. WHich sucks as I had a TWRP and Flatline recovery saved, an now I am stuck on an older version of TWRP and it does not see the TWRP recovery I made from a newer TWRP version.
This happened when I updated the bootloader to Hairybean.
So I am stuck in a circle where I can boot into an old TWRP, cannot push a new recovery, bastfoot seems borked and the tablet won't boot into Android.
I am sorry to hear that . I can't see where you wen't wrong to the point that broke fastboot . The post no.4 in link above has step to step instruction .
There is always APX mode (if you have backups) . I personally haven't worked with it but you should be able to do a recovery ...
http://forum.xda-developers.com/wiki/APX_mode .
Edit : take a look at the other Thread you posted . you might be on the right track after all .
Hi everybody.
I just flashed PureNexus 6.0 rom from 5.1.1 version, and after flashing and rebooting, the device gets stucked at the boot logo (an animation with 4 dots). This was the updating process (I'm rooted and with unlocked bootloader).
1) wiped all partitions (including system, data, etc...)
2) flashed bootloader from latest factory image via fastboot.
3) rebooted to bootloader
4) flashed vendor image via fastboot
5) flashed latest PureNexus 6.0 rom from recovery (latest twrp)
6) flashed dynamic-gapps from banks from recovery
7) rebooted
Did I do something wrong? Bootloader seems unlocked and I'm able to reboot to recovery but I don't know what else I can do.
ialana said:
Hi everybody.
I just flashed PureNexus 6.0 rom from 5.1.1 version, and after flashing and rebooting, the device gets stucked at the boot logo (an animation with 4 dots). This was the updating process (I'm rooted and with unlocked bootloader).
1) wiped all partitions (including system, data, etc...)
2) flashed bootloader from latest factory image via fastboot.
3) rebooted to bootloader
4) flashed vendor image via fastboot
5) flashed latest PureNexus 6.0 rom from recovery (latest twrp)
6) flashed dynamic-gapps from banks from recovery
7) rebooted
Did I do something wrong? Bootloader seems unlocked and I'm able to reboot to recovery but I don't know what else I can do.
Click to expand...
Click to collapse
Sounds like you did everything correct.
" Bootloader seems unlocked"
--- reboot into bootloader and it will tell you if you are unlocked.
Personally I would flash the volantis-mra58n factory image to get on the latest Marshmallow - boot up make sure all is running well.
Flash TWRP, make a nandroid, then flash the ROM.
No need to flash anything else, or at least that's what I did, here where my steps upon recieving the tablet last week.
unlocked bootloader.
flashed volantis-mra58n factory image, booted up played around for a bit (as Pure Nexus 6.0 wasn't out yet)
flashed TWRP, make a nandroid
flashed Pure Nexus 6.0 + banks gaaps
reboot, profit
sounds like something is going wrong, you should have the Marshmallow boot animation not the LP dots.
you don't need to flash the bootloader or vendor images doing my process as you are already on the latest ones from flashing the volantis-mra58n factory image.
Best of luck.
andybones said:
Sounds like you did everything correct.
" Bootloader seems unlocked"
--- reboot into bootloader and it will tell you if you are unlocked.
Personally I would flash the volantis-mra58n factory image to get on the latest Marshmallow - boot up make sure all is running well.
Flash TWRP, make a nandroid, then flash the ROM.
No need to flash anything else, or at least that's what I did, here where my steps upon recieving the tablet last week.
unlocked bootloader.
flashed volantis-mra58n factory image, booted up played around for a bit (as Pure Nexus 6.0 wasn't out yet)
flashed TWRP, make a nandroid
flashed Pure Nexus 6.0 + banks gaaps
reboot, profit
sounds like something is going wrong, you should have the Marshmallow boot animation not the LP dots.
you don't need to flash the bootloader or vendor images doing my process as you are already on the latest ones from flashing the volantis-mra58n factory image.
Best of luck.
Click to expand...
Click to collapse
Thanks for your answer. The bootloader is unlocked, or that's what it says when I boot on it. I'll try flash to the factory image and see what happens. Thanks!
Problem solved after flashing recovery, boot.img and system.img from factory image, thanks! I'll try flashing a custom rom now.
i've read that there needs to be gapps for 6.0, 5.1 gapps supposedly won't work on 6.0
I have a Z5C(E5803) that was originally able to unlock the bootloader and let me flash ROMs, specifically the Cyanogen ROM that CTXz has been working on. I ran out of power and got stuck in some kind of nasty bootloop yesterday that prompted me to re-flash boot.img and TWRP.
After I did these things I left it charging for a few hours and it was able to boot into TWRP where I then restored it to a backup of the basic Xperia pre-loaded ROM.
This all worked fine, thought I could boot into TWRP and just flash the Cyanogen zip again. I can get into TWRP just fine but I attempt to flash Cyanogen I get an "ERROR 7"
I have since done several wipes, gotten into the bootloader settings by entering that code in the dialer and have seen that bootloader unlock = no. I distinctly remember bootloder unlocking being allowed the first time I installed CM on my device, what could have caused this?
I was able to use it with fastboot anyway and install CM13 again, maybe this was a bug?
When I tried using oem unlock command with fastboot it said my device was already rooted even though I had just restored from a backup, and then I just proceeded normally from there.
use CM13 official Recovery to FLASH CM13.
also i don't think so twrp3.0.2 is out there for z5c. are you using any other variants Twrp? (YUGA ? )
This is my version of TWRP built for the 2017 Moto G5S. It should work fine, but using it is a try at your own risk procedure. Your bootloader must be unlocked to use this recovery. Fastboot mode is used to flash or boot this recovery. To enter fastboot mode, turn off your device, hold PWR and VolDn for 3 seconds, then let go.
Differences between upstream TWRP and my fork:
My original green theme
No SuperSU
No TWRP app
No HTC Dumlock cruft
Updated pigz compressor (slightly faster and more tolerant of corruption)
To temporarily boot this recovery:
Code:
fastboot boot twrp.img
To permanently flash it:
Code:
fastboot flash recovery twrp.img
The download is available on the downloads tab.
XDA:DevDB Information
TWRP for Moto G5S, Tool/Utility for the Moto G5S
Contributors
squid2
Source Code: https://github.com/moto8937-twrp
Version Information
Status: Stable
Current Stable Version: 3.2.3-r1
Stable Release Date: 2018-08-17
Created 2017-11-05
Last Updated 2018-08-17
Squid TWRP 3.1.1-r3
Initial build for montana is up. I expect it to be fully functional, including encryption support. Special thanks to @lohanbarth for testing.
thank you for your work :good:
Hi,
i just flashed your TWRP. The flash was successful, after booting to recovery twrp came up just fine. I wiped /data to decrypt, then rebooted the phone... Now it seems either bootlooping or bricked.
(Of course i unlocked the bootloader before flashing)
The phone just shows the bootloader-screen (blue background, red M-Logo, white letters "powered by android") with a small text in the middle "bad key).
Nothing happens. I cant even shut it down. Holding the power button for 10 seconds seems to start a reboot (screen goes black) but the bootloader-screen immediately shows back up and stays. Theres nothing i can do, no adb/fastboot access either...
Any suggestions?
Edit1:
AH! Pressing VolDown + Power gets me to fastboot/recovery... Phew. Guess i flash the stock rom first before proceeding any further.
Edit2:
Succeeded, nice!
Hi,
I flashed this TWRP. After flashing I went to recovery mode. Format Data failed as /data unknown. Flashed stock ROM. Again flashed TWRP. This time it just bootloops into TWRP recovery. When I power off and ON again, it bootloops and goes into TWRP recovery again and again. Any idea what could be wrong? My guess is I screwed up partition table. But not sure.
Thanks
KS
I went through flashing stock ROM, TWRP once again. After flashing TWRP, I went to recovery repeatedly and did 'Format Data' every time. I flashed Magisk. System booted fine. I verified by power off/on several times. Seems to be working fine.
Thanks
KS
Thanks for your hard work at bringing TWRP to the MOTO G5s.
It took me a while to install it on my XT1797, as there was some strange message during boot which said
ID: Bad key
But after many many times bricking and unbricking, I am now finally rooted using Magisk.
Hope that we can see some custom Roms for this great device soon.
I tried it with XT1797, but I can not boot and flash twrp.
Is this twrp compatible with XT1797?
hello, your bootloader and unlock it?
did you enable USB debugging?
that you put the fastboot cmd?
Hi . Thx for You job . My phone stil a live But I have a question .
how about this one ? At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) . To avoid this you have to flash either SuperSU or flash any of the verity disabler zips there in xda
FAFAŁ said:
Hi . Thx for You job . My phone stil a live But I have a question .
how about this one ? At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) . To avoid this you have to flash either SuperSU or flash any of the verity disabler zips there in xda
Click to expand...
Click to collapse
What is the question? For me it worked without such vertiy disable stuff. Simply unlock the bootloader, boot and/or flash TWRP, root your phone or do anything else. When TWRP asks to change /system, answer yes.
Root and TWRP. And a great phone.
Just need some Roms, pray that they will come!
Thank you!
janhieber said:
What is the question? For me it worked without such vertiy disable stuff. Simply unlock the bootloader, boot and/or flash TWRP, root your phone or do anything else. When TWRP asks to change /system, answer yes.
Click to expand...
Click to collapse
Ok .that's all super go to recovery end fire .Thanks
Hello, I compiled the twrp3.2 with the sources of squid2.
thank @squid2 for sources
twrp-montana-3.2.0-r1 > http://www.mediafire.com/file/4443oy6kwiyvm5g/twrp-montana-3.2.0-r1.img
Squid TWRP 3.2.0-r1
I've posted a new build of my TWRP with the latest changes from upstream. It brings better support for Oreo zips while still supporting older ones. It also has improvements to the reliability of backups.
squid2 said:
I've posted a new build of my TWRP with the latest changes from upstream. It brings better support for Oreo zips while still supporting older ones. It also has improvements to the reliability of backups.
Click to expand...
Click to collapse
Dear @squid2 please give some ROMs also
... please i know you are busy with work but it is just a request
Unable to Flash twrp recovery
After flashing oficial firmware, i am no longer able to flash twrp recovery, after each system reboot, i am back on stock recovery.
Does anyone know how to fix?
Flashed using: fastboot flash recovery twrp.img
Get a notification: bootloader file not signed or corrupt
dau999 said:
After flashing oficial firmware, i am no longer able to flash twrp recovery, after each system reboot, i am back on stock recovery.
Does anyone know how to fix?
Flashed using: fastboot flash recovery twrp.img
Get a notification: bootloader file not signed or corrupt
Click to expand...
Click to collapse
after the flash of the twrp you select good recovery in the bootloader?
lohanbarth said:
after the flash of the twrp you select good recovery in the bootloader?
Click to expand...
Click to collapse
Select good recovery in the bootloader??!!
Bootloader gives me a notification that the img is not signed or corrupt (squids one)
you tried to download it again and then try again
lohanbarth said:
you tried to download it again and then try again
Click to expand...
Click to collapse
I did, same error.