Hello, I am using an AT&T LG G2 (D800 of course) and after Rooting I'd like to install CM. I've installed custom ROMs before and usually have no trouble with them, but I can't seem to install TWRP on my phone.
I've installed AutoRec for my model from the playstore to install TWRP but it doesn't seem to work. According to the tutorial I just have to reboot after the process and then boot into recovery, however when I do so from an app I do not have a recovery installed, and when I try to do it via hardware booting it just goes to the factory reset screen. I understand that booting into recovery this way will always show this screen and that I'm supposed to just confirm everything, then it should boot into TWRP. However doing so simply resets my phone.
Anyone have this problem or some more specific steps in order to help me?
ItsGflow said:
Hello, I am using an AT&T LG G2 (D800 of course) and after Rooting I'd like to install CM. I've installed custom ROMs before and usually have no trouble with them, but I can't seem to install TWRP on my phone.
I've installed AutoRec for my model from the playstore to install TWRP but it doesn't seem to work. According to the tutorial I just have to reboot after the process and then boot into recovery, however when I do so from an app I do not have a recovery installed, and when I try to do it via hardware booting it just goes to the factory reset screen. I understand that booting into recovery this way will always show this screen and that I'm supposed to just confirm everything, then it should boot into TWRP. However doing so simply resets my phone.
Anyone have this problem or some more specific steps in order to help me?
Click to expand...
Click to collapse
Take my advise. Do not install CM12. The speaker volume is too low and the shipped camera is the worst camera ever. I went to CM12 nightlies and reverted back to Stock G2 firmware. Plus, paid app Cygic GPS didnt work and few other crashes here and there. But anyways, if you still want to root then use LG One Click Root http://www.andromods.com/news-root/lg-g3-g-flex-2-g2-lollipop-one-click.html
Related
I have a Moto G X1032 rooted with TWRP installed. I've been using the stock firmware for 4.4.2 without any issues for a while, but after June 6th's OTA update to 4.4.3, my phone has gotten stuck in a boot loop. It turns on and runs Android as usual, without any issues, for less than a minute and then shuts down. It then continues to boot back up and continue the process. The only way to stop the loop is to boot into the bootloader from TWRP and power off the phone from there. Luckily I have a backup to that reverts me back to 4.4.2, which successfully stops the loop. But after several attempts to update to 4.4.3, it has become quite clear that this boot loop is inevitable unless I stick with 4.4.2. I read an article that seems to address some conflict with rooted phones and 4.4.3, but I'm not quite sure what the conflict is. Can anyone explain to me why this boot loop is most likely happening, what I could do to fix it, or if it is even possible to have a rooted X1032 with 4.4.3 installed? Any help whatsoever would be greatly appreciated. Thank you.
Are you saying you tried to install the OTA with TWRP installed and not the stock recovery?
Just go into recovery clear all cache,kavik cache that should do
NerdNoob1210 said:
I have a Moto G X1032 rooted with TWRP installed. I've been using the stock firmware for 4.4.2 without any issues for a while, but after June 6th's OTA update to 4.4.3, my phone has gotten stuck in a boot loop. It turns on and runs Android as usual, without any issues, for less than a minute and then shuts down. It then continues to boot back up and continue the process. The only way to stop the loop is to boot into the bootloader from TWRP and power off the phone from there. Luckily I have a backup to that reverts me back to 4.4.2, which successfully stops the loop. But after several attempts to update to 4.4.3, it has become quite clear that this boot loop is inevitable unless I stick with 4.4.2. I read an article that seems to address some conflict with rooted phones and 4.4.3, but I'm not quite sure what the conflict is. Can anyone explain to me why this boot loop is most likely happening, what I could do to fix it, or if it is even possible to have a rooted X1032 with 4.4.3 installed? Any help whatsoever would be greatly appreciated. Thank you.
Click to expand...
Click to collapse
The bootloop is caused by the recovery. It can't update 4.4.3 and keeps trying. Start the update again and let the OTA file download, then copy it out of /cache and into the sdcard. If it's not in cache it won't bootloop. I suggest flashing PhilZ recovery and updating with that instead. Flash the file in the sdcard and post whatever errors are listed...
secretkloud said:
The bootloop is caused by the recovery. It can't update 4.4.3 and keeps trying. Start the update again and let the OTA file download, then copy it out of /cache and into the sdcard. If it's not in cache it won't bootloop. I suggest flashing PhilZ recovery and updating with that instead. Flash the file in the sdcard and post whatever errors are listed...
Click to expand...
Click to collapse
Thank you. I will try that. Before I do though, do you know of any places I could find 4.4.3 online, so I could just download it from my PC and flash it over via sideload? I usually prefer to flash things that way, rather than straight from the phone.
bozzykid said:
Are you saying you tried to install the OTA with TWRP installed and not the stock recovery?
Click to expand...
Click to collapse
Yes. This is my first time doing so, excuse my lack of knowledge on the subject. In retrospect, I suppose I should have known there must be a different method with which I install it. Secretkloud gave me a good suggestion though. Is there a reason in particular as to why I can't do OTA updates with custom recovery installed?
secretkloud said:
The bootloop is caused by the recovery. It can't update 4.4.3 and keeps trying. Start the update again and let the OTA file download, then copy it out of /cache and into the sdcard. If it's not in cache it won't bootloop. I suggest flashing PhilZ recovery and updating with that instead. Flash the file in the sdcard and post whatever errors are listed...
Click to expand...
Click to collapse
I just downloaded the zip from my phone and flashed it from Phillz recovery. It worked very well and the update was successful. Thanks for pointing me to Phillz recovery by the way. It's the only functional recovery image that allows me to mount the sdcard.
NerdNoob1210 said:
Thank you. I will try that. Before I do though, do you know of any places I could find 4.4.3 online, so I could just download it from my PC and flash it over via sideload? I usually prefer to flash things that way, rather than straight from the phone.
Click to expand...
Click to collapse
Copy the one you have in your phone onto your PC. Smallest chance of error if you do it that way...
it's not easy getting out of the loop.
I did a factory reload of a rooted phone with CWM.
Now for the CWM issue the Moto G loaded OK and then said there was an update for android to fix some bugs. This was 4.4.3. I loaded it and it gets half way and it then says
"Signature verification fail"
at the bottom of the screen and
" Install Untrusted Package"
The options are yes, no or go back
at the top....
whichever one I try it then tries to boot shows the Android / Motorola screen and starts up gets a txt message for 2-3 seconds... it then goes back to Android CWM recovery with the same options as above and repeats the process. again and again and again. No function keys will stop this cycle which just repeats again. This continues until the battery dies.
any ideas ? how can I override this action in CWM v6.0.4.6 and force it to do a factory reload ? any help or advice much appreciated.
If you can still power your phone, can you still access the boot loader? If so, I would suggest using adb from a computer to flash Phillz recovery. CWM always gave me a lot of random errors when flashing items. You could use PhillZ to flash the stock ROM for 4.4.2. After that, just follow the same process I did. Download the update zip via the OTA download when it prompts you. Once it's finished, DON'T boot back into Android. Boot into Phillz recovery from the boot loader, move the zip out of the cache and onto sdcard or your computer, and then flash it either straight from the phone or by sideloading it from your computer. Then you'll have a working version of vanilla 4.4.3, and you can flash over a custom ROM in the future if you so choose.
Sent from my XT1032 using XDA Premium 4 mobile app
NerdNoob1210 said:
If you can still power your phone, can you still access the boot loader? If so, I would suggest using adb from a computer to flash Phillz recovery. CWM always gave me a lot of random errors when flashing items. You could use PhillZ to flash the stock ROM for 4.4.2. After that, just follow the same process I did. Download the update zip via the OTA download when it prompts you. Once it's finished, DON'T boot back into Android. Boot into Phillz recovery from the boot loader, move the zip out of the cache and onto sdcard or your computer, and then flash it either straight from the phone or by sideloading it from your computer. Then you'll have a working version of vanilla 4.4.3, and you can flash over a custom ROM in the future if you so choose.
Sent from my XT1032 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
unfortunately I can't get into bootloader. I can connect usb and it makes no difference. therefore adb commands dont work. it just goes straight into screen described with those three options. I'm hoping that there is an override action in CWM which isn't power and volume down which do nothing.
thanks for the suggestion tho. it was a good idea.
Hm... Without access to the boot loader, I'm not sure there's much of anything you can do anymore... You've completely lost the ability to communicate any sort of commands to your phone save for the 3 options that menu provides. I assume that what CWM is trying to do is install the zip from your cache and is failing to do so. The only viable option would be to flash a new recovery image and install the zip manually, but that's impossible for you given your current circumstances. I would give up looking for an override command for CWM, your best hope is to find an alternative means with which you can access your boot loader. I suggest you start a thread dedicated to your issue and see if a more experienced user can provide you with the information you need. Sorry, I hope you get the help you need. :/
Sent from my XT1032 using XDA Premium 4 mobile app
Thanks for trying to help. I have followed your advice and opened a thread
NerdNoob1210 said:
Hm... Without access to the boot loader, I'm not sure there's much of anything you can do anymore... You've completely lost the ability to communicate any sort of commands to your phone save for the 3 options that menu provides. I assume that what CWM is trying to do is install the zip from your cache and is failing to do so. The only viable option would be to flash a new recovery image and install the zip manually, but that's impossible for you given your current circumstances. I would give up looking for an override command for CWM, your best hope is to find an alternative means with which you can access your boot loader. I suggest you start a thread dedicated to your issue and see if a more experienced user can provide you with the information you need. Sorry, I hope you get the help you need. :/
Sent from my XT1032 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
im trying to flash a recovery but i think i screwed my bootloader, up i used an app (flashify) to try to install twrp on my lg g2 d800 running android L 5.0.2 software version d80030f but now i cant even get to the stock recovery it automatically goes into fastboot mode and before that it was saying something about a critical error when i tried going into recovery. the phone still boots up normally and works so should i just give up on trying to install a custom recovery and count my losses now before i mess it up for good. i wont try anything else unless i get some logical advice from someone who knows about this problem.
Use AutoRec
I have tried that already it says i can now flash twrp but when i tried to reboot into recovery it was still stock android recovery
jesse640 said:
im trying to flash a recovery but i think i screwed my bootloader, up i used an app (flashify) to try to install twrp on my lg g2 d800 running android L 5.0.2 software version d80030f but now i cant even get to the stock recovery it automatically goes into fastboot mode and before that it was saying something about a critical error when i tried going into recovery. the phone still boots up normally and works so should i just give up on trying to install a custom recovery and count my losses now before i mess it up for good. i wont try anything else unless i get some logical advice from someone who knows about this problem.
Click to expand...
Click to collapse
Please do not post questions more than once see http://forum.xda-developers.com/general/xda-assist/lg-g2-d800-t3120582/post61015809#post61015809
This thread will be close.
Alright so I have a Moto G original version, currently running 4.4.4. I previously rooted it and stuck TWRP on it, but then when it became available to update to Lollipop on the Moto G I tried to get stock recovery on it. I used "MotoToolAIOV3" to put "Kitkat Stock Recovery" on it. This seemed to work fine, until it came to update, which then it errored every time I tried. I then realised the stock recovery that "MotoToolAIOV3" must be faulty or something, so I tried reputting TWRP on my Moto G by flashing it from an app called "Rashr". This seemed to be successful, HOWEVER I went to reboot my phone to check if it had worked, put it into bootloader, then went into recovery and it still came up with the stock recovery "MotoToolAIOV3" had given me. I was confused, so I tried "normal powerup", which THEN sent me into TWRP, however this time, when the bootloader unlocked warning came up, a weird blurry line went through my screen every so often, and then it went into TWRP, with the line going across the screen in TWRP as well. I've tried to boot into normal powerup through TWRP, Bootloader, normal powerup, holding down power button but every time I try, it goes into TWRP with a dodgy line going across my screen. I'm currently doing exams and I really need my phone as I have revision notes on apps that I can only access on that phone, and things such as exam timetable saved in the actual phone.
Please, somebody help ):
Again my phone is a Moto G Original Gen running 4.4.4 stock android, on a tesco thing (cant remember what its called might be kernel).
Thank you.
bump
bump
bump2
bump2
Arcenum said:
bump2
Click to expand...
Click to collapse
Seems like you have flashed TWRP into the kernel partition. Seem like the "Rashr" app or whatever flashed it there by mistake. I recommend that you install TWRP via a more standard procedure, such as using fastboot(if bootloader unlocked) or using the instructions given where ever you downloaded TWRP. Your situation is not serious as long as you are careful....
1. Install recovery to correct partition
2. Boot to that recovery and wipe/factory reset etc...
3. Install an new ROM.
Hello I hope someone could help me.
I have an lg g3 D855 international version, with kit kat 4.4.2 and its the 10e version.
I've root my device in order to install new custom rooms. At first I wanted to go to android marshmallow official and wanted to do the flashing with lg flash tool, but in every computer I have, it does not working, its either stuck in 2% and then it fails, or 4% and then it fails, and I tried to erase an install the new drivers and the old ones in the computer... But I couldn't get it to work. So I decided to root my device, and install twrp recovery, so I did. First I try to install the latest version of twrp, this I did it directly from the phone via TWRP manager. It was supose to work... But when I finish installing and went to recovery.. It went to a black screen saying "[700] fastboot mode started" or sometimes "[760] fastboot mode started" to my surprise the phone is not softbrick. I removed the battery and then reboot the phone and it works... But everytime I go to recovery or tried to install a new bump recovery... Because i thought that was the problem is still the same. I tried to install a new recovery with ADB but when I put the file path in order to install it... It said it couldn't find the recovery img in the path... But it was there... And I tried, but couldn't get it to work. I have some experience with custom roms on samsung galaxy s3, but change my phone, and this lg g3 is really making me crazy.
Thank you very much in advanced.
danyjjg said:
Hello I hope someone could help me.
I have an lg g3 D855 international version, with kit kat 4.4.2 and its the 10e version.
I've root my device in order to install new custom rooms. At first I wanted to go to android marshmallow official and wanted to do the flashing with lg flash tool, but in every computer I have, it does not working, its either stuck in 2% and then it fails, or 4% and then it fails, and I tried to erase an install the new drivers and the old ones in the computer... But I couldn't get it to work. So I decided to root my device, and install twrp recovery, so I did. First I try to install the latest version of twrp, this I did it directly from the phone via TWRP manager. It was supose to work... But when I finish installing and went to recovery.. It went to a black screen saying "[700] fastboot mode started" or sometimes "[760] fastboot mode started" to my surprise the phone is not softbrick. I removed the battery and then reboot the phone and it works... But everytime I go to recovery or tried to install a new bump recovery... Because i thought that was the problem is still the same. I tried to install a new recovery with ADB but when I put the file path in order to install it... It said it couldn't find the recovery img in the path... But it was there... And I tried, but couldn't get it to work. I have some experience with custom roms on samsung galaxy s3, but change my phone, and this lg g3 is really making me crazy.
Thank you very much in advanced.
Click to expand...
Click to collapse
hi
Thank you for using XDA Assist
You can go here and ask questions, a lot should be able to help you on this
G3 Q&A, Help & Troubleshooting
Just got my XT1644 G4 Plus 16GB here in America and brought it home for some testing.
Everything was a piece of cake, I did these things in order with no issues. There are other guides for these things all over XDA so I won't be giving detailed instructions.
Unlocked the bootloader here - https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Installed TWRP from here. - http://forum.xda-developers.com/mot...p-twrp-3-0-2-2-recovery-moto-g4-plus-t3386586
And flashed SuperSU from here - https://download.chainfire.eu/696/supersu/
When TWRP first boots it will ask if you want to run in systemless mode. Make sure you tell it YES!!!
Rebooted on the first try with no issues.
I have Xposed installed with a few modules and it works great.
Sent from my Moto G (4) using Tapatalk
Can anyone get me a stock boot.img i seemed to have messed up my adb protocol on the phone and my computer will no longer allow it to give me an RSA key prompt. The method worked for me though.
mystx2112 said:
Can anyone get me a stock boot.img i seemed to have messed up my adb protocol on the phone and my computer will no longer allow it to give me an RSA key prompt. The method worked for me though.
Click to expand...
Click to collapse
Can extract it from the stock ROM here: https://www.androidfilehost.com/?fid=24572369242687085
not sure if this is full proof i got bootloop
After flashing SuperSu 2.76 the phone is stuck forever at the "moto" logo. Is it because I'm using such a new version of SuperSu? Why do you use 2.46?
How long did it take to get the unlock code? I am waiting for a couple hours now...
LE: 4 hours... and finally I got the code.
Just got XT1644.
Unlocked bootloader with no problem.
Installed TWRP 3.0.2-0 with no problem
Installed SuperSu 2.46 in read only mode.
Stuck at moto screen.
Any help would be appreciated.
craigl14 said:
Just got XT1644.
Unlocked bootloader with no problem.
Installed TWRP 3.0.2-0 with no problem
Installed SuperSu 2.46 in read only mode.
Stuck at moto screen.
Any help would be appreciated.
Click to expand...
Click to collapse
Nevermind. Followed steps 5-8 of this post http://forum.xda-developers.com/moto-g4-plus/how-to/root-systemless-rooting-supersu-2-74-2-t3405772 and all is well.
I can't get twrp to install. I keep getting told that the image is not signed or corrupt
First unlock Bootloader.
You don't need to install TWRP, just boot into it so you can flash the Systemless SuperSU.
SoNic67 said:
First unlock Bootloader.
You don't need to install TWRP, just boot into it so you can flash the Systemless SuperSU.
Click to expand...
Click to collapse
that's just it... I can't boot to twrp. It's not there.
Where? You can't find it on the SD by browsing in the recovery?
because that's just it, there's nothing in recovery. This has gotten so convoluted that I don't even know what I'm supposed to have where....
@davidkoby
Stock ROM Recovery starts with a "Dead Android" and "no command" written under it, it is you see or something else?
Does supersu need to be in systemless mode?
craigl14 said:
Nevermind. Followed steps 5-8 of this post http://forum.xda-developers.com/moto-g4-plus/how-to/root-systemless-rooting-supersu-2-74-2-t3405772 and all is well.
Click to expand...
Click to collapse
Hi Bro,
I was also stuck at the moto logo screen and then I followed steps from 5-8, (where I see the superSu file is of different version), and now my phone is not booting at all, normally. I can boot in to bootloader but not normal boot is happening, I cannot even switch on my phone. I am a bit scared. Can you please assist.
sam9s said:
Hi Bro,
I was also stuck at the moto logo screen and then I followed steps from 5-8, (where I see the superSu file is of different version), and now my phone is not booting at all, normally. I can boot in to bootloader but not normal boot is happening, I cannot even switch on my phone. I am a bit scared. Can you please assist.
Click to expand...
Click to collapse
Assuming you have XT1644, stock marshmallow ROM and TWRP recovery installed, maybe boot into recovery and double check that the .supersu file you created is in the data directory (step 6) through file manager. If it's there maybe flash the supersu zip file in OP since that is the version that worked for me. If neither works maybe factory reset in recovery and flash the correct supersu zip and try again. Failing all that, you may have to completely start over and reflash the ROM. My guess is creating the .supersu file wasn't done correctly or the incorrect version of the supersu zip is causing the problem.
craigl14 said:
Assuming you have XT1644, stock marshmallow ROM and TWRP recovery installed, maybe boot into recovery and double check that the .supersu file you created is in the data directory (step 6) through file manager. If it's there maybe flash the supersu zip file in OP since that is the version that worked for me. If neither works maybe factory reset in recovery and flash the correct supersu zip and try again. Failing all that, you may have to completely start over and reflash the ROM. My guess is creating the .supersu file wasn't done correctly or the incorrect version of the supersu zip is causing the problem.
Click to expand...
Click to collapse
Ok yes I have XT1644 (any way to confirm BTW), I also have TWRP recovery installed (thats how I took the backup)m BUT, I was not on stock marshmallow, I was on nougat (Stock), The phone did an OTA update, months ago. Could that be the reason.
Also I checked .supersu file was there via file manager. What do you advice ..??? I also have tried now with SR3-SuperSU v2.79, but same result, it get stuck at Moto Boot screen.
Another thing I noticed at the screen where it says "Your phone is unlocked and cant be trusted" and it will boot in 5 seconds, in front of ID it says BAD KEY ... wonder what that means or if it has something to do with what wrong has happened.
Appreciate your assistance here.
Regards
Sammy
sam9s said:
Ok yes I have XT1644 (any way to confirm BTW), I also have TWRP recovery installed (thats how I took the backup)m BUT, I was not on stock marshmallow, I was on nougat (Stock), The phone did an OTA update, months ago. Could that be the reason.
Also I checked .supersu file was there via file manager. What do you advice ..??? I also have tried now with SR3-SuperSU v2.79, but same result, it get stuck at Moto Boot screen.
Another thing I noticed at the screen where it says "Your phone is unlocked and cant be trusted" and it will boot in 5 seconds, in front of ID it says BAD KEY ... wonder what that means or if it has something to do with what wrong has happened.
Appreciate your assistance here.
Regards
Sammy
Click to expand...
Click to collapse
Hmmmm...I don't know if you have XT1644. Most who have that version are still waiting on OTA I think and certainly didn't get it month's ago. It is the G4 Plus North American version. If you still have the box it will be on the UPC label. It will also be in your phone info in settings once your phone works again. Did your phone work fine before you tried to root it? Anyway, Nougat will not root with this method. If you can boot into recovery, try factory reset. If that doesn't work, you're going to have to reflash the Nougat ROM...make sure you get the right one for your phone. You will need to search around on this forum for instructions and which download to get, etc. Once you have Nougat up and running again, you will need to leave it unrooted or use one of the proven methods of root. Again, I don't think systemless supersu works for Nougat. I have no idea what bad key means. The only thing I've ever had is "N/A" come up in the unlock warning. Incidentally, you can get rid of the bootloader warning screen if you want to.