ATT LG Optimus G Pro Here
I used newest FreeGee , Installed TWRP & Now im stuck in recovery mode. I flashed gummy rom first time & It worked. Ran into problem after I installed the Google apps so I did a factory reset, wiped everything to try again to install gummy rom. Now I'm stuck in TWRP. I also used ADB sideload commands to push the rom to phone & It did push it, except now. When I try to install the rom, It keeps saying FAILED. Can someone tell me what im doing wrong?
newgeek- I don't know if the AT&T version of this is very different to my F240 version but I am familiar with that 3rd screen you posted with the "secure booting error" or something like that.
What about just pulling that battery out and doing factory reset and start over from the beginning ?
LL13-
newgeek35 said:
ATT LG Optimus G Pro Here
I used newest FreeGee , Installed TWRP & Now im stuck in recovery mode. I flashed gummy rom first time & It worked. Ran into problem after I installed the Google apps so I did a factory reset, wiped everything to try again to install gummy rom. Now I'm stuck in TWRP. I also used ADB sideload commands to push the rom to phone & It did push it, except now. When I try to install the rom, It keeps saying FAILED. Can someone tell me what im doing wrong?
Click to expand...
Click to collapse
Try to push another ROM via adb, I read in the general Section that there were some Gummy files that weren't the right size, just download CM11 and try to flash it, TWRP is saying that the flash failed, that's why you are stuck in recovery.
Erik
The phone currently has no OS , I also tried to mount my 64gb sd card to install off of that & It gives me a mounting error for SD CARD. I have tried several other roms & No luck , Keeps giving me FAILED. Is this because of the secure boot perhaps? I'm totally clueless why it's not taking it. I'm running my nexus 4 with the gummy rom without a hitch.
Why not try a different SD card ? If that SD card was in the phone when all this happened maybe something is on the card that's bad ?
LL13-
I borrowed a 2GB SD CARD & It mounts but same thing as before FAILED. Tried both gummy & CM 10.2
newgeek35 said:
I borrowed a 2GB SD CARD & It mounts but same thing as before FAILED. Tried both gummy & CM 10.2
Click to expand...
Click to collapse
It looks like an error with the updater script, maybe something twrp isnt reading or executing? try a different rom.
At worst try a different Recovery.
ADDED:2/4/2014: I would avoid twrp on freegee, i've heard others have issues and it may have something to do with your situation.
Also, I noticed your twrp says 2.6.1.0, am I mistaken or is the newest teamwin 2.6.3.1? That number don't look right.
If possible try to flash madmacks twrp or cwm 6.0.4.6.
1.Try to Flash a ROM via sideload
2. you can end the recovery boot loop by using adb commands, there are two methods try them
http://forum.xda-developers.com/showpost.php?p=49370751&postcount=70
and
http://forum.xda-developers.com/showpost.php?p=48136185&postcount=268
I had the same issue seems like the are some problems with TWRP on this particular phone I flashed the regular clockworkmod and it works perfect.I tried on another phone with same results.
Right now
Flash stock rom
root
use freegee to install regular cwm I tried rom manage but recovery did not installed
the flash another rom if thats what you really want but copy rom directly to sd card instead
Its not just twrp apparently the new update of freegee installs the wrong bootloader/image on our phone. It bootloops anyone that uses it.
Sent from my LG-E980 using XDA Premium 4 mobile app
Use Madmack's hacked TWRP located in his CM threads. Best recovery for our device from what I've seen/tested.
Sent from my AICP 4.4 LG-E980
Neroga said:
Use Madmack's hacked TWRP located in his CM threads. Best recovery for our device from what I've seen/tested.
Sent from my AICP 4.4 LG-E980
Click to expand...
Click to collapse
Madmack's TWRP is reliable when you want to have no bootloops into your recovery. But i have the problem, that i cannot flash any other roms and it shows, that my LG E986 isnt recognized as a suitable device for the rom and it aborts the procedure. Although on the other recoveries it worked fine...
Is there something what i have to do except switching recoveries to my phone's death?
I used ADB to push the stock rom back to device & It took it's sweet time but it worked. I sold the phone to a friend of mine LOL! They wont know the difference.
Related
I have done this before but I used what seems to be a different version of freegee (didn't have the option to backup efs or flash TWRP) so I unlocked my device and after it had completed I rebooted and then powered down. I put my phone in to CWM and flashed the stock debloated ROM. After flashing this ROM I was stuck in a bootloop. I ended up using LG Tool to get it back to stock. I thought it must have been a random once off issue so I tried again with Freegee, same thing happened, only this time no matter what I do I can not get LG Tool to fix the issue as it keeps giving me the error of low battery even though it is at full capacity. I then tried to use BC2 to flash a kdz file and I get the same error. I have since tried factory resetting, sideloading different recoveries, ROMs and basebands without boot. I have tried to use LG Tool about 50 times and it is not working. I have changed USB ports, reinstalled drivers etc, just keeps giving me that error. Yes I have set permission in the app and I am using Windows 7
uppon2 said:
I have done this before but I used what seems to be a different version of freegee (didn't have the option to backup efs or flash TWRP) so I unlocked my device and after it had completed I rebooted and then powered down. I put my phone in to CWM and flashed the stock debloated ROM. After flashing this ROM I was stuck in a bootloop. I ended up using LG Tool to get it back to stock. I thought it must have been a random once off issue so I tried again with Freegee, same thing happened, only this time no matter what I do I can not get LG Tool to fix the issue as it keeps giving me the error of low battery even though it is at full capacity. I then tried to use BC2 to flash a kdz file and I get the same error. I have since tried factory resetting, sideloading different recoveries, ROMs and basebands without boot. I have tried to use LG Tool about 50 times and it is not working. I have changed USB ports, reinstalled drivers etc, just keeps giving me that error. Yes I have set permission in the app and I am using Windows 7
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=48205695&postcount=13
atifsh said:
http://forum.xda-developers.com/showpost.php?p=48205695&postcount=13
Click to expand...
Click to collapse
Thank you, I will use that if I ever get LG Tool to stop throwing me the low battery warning. What a stupid program to not give you the option to bypass it. Surely there is a way I can do this. My battery is at 99%. I just flashing madmack hacked and lockified recovery and now I can't even get in to recovery to do sideloads. I am running out of options, my only way is to get LG Tool or B2C to work
EDIT* I have recovery back. GRR why is this stupid message about low battery keep popping up
uppon2 said:
Thank you, I will use that if I ever get LG Tool to stop throwing me the low battery warning. What a stupid program to not give you the option to bypass it. Surely there is a way I can do this. My battery is at 99%. I just flashing madmack hacked and lockified recovery and now I can't even get in to recovery to do sideloads. I am running out of options, my only way is to get LG Tool or B2C to work
EDIT* I have recovery back. GRR why is this stupid message about low battery keep popping up
Click to expand...
Click to collapse
have not tested this from cm rom but works from any stock. bytheway i have optimus G not pro
from recovery adb push rom.zip (your rom)
adb push rom.zip /sdcard/0
(0 required for cwm and cm10.2)
flash that rom
enable debugging
run lgflash tool one that supports large files or the online one it will pass the battery and auto restart in download mode there it will give error just unplug replug and retry and it will be flashed this time.
atifsh said:
have not tested this from cm rom but works from any stock. bytheway i have optimus G not pro
from recovery adb push rom.zip (your rom)
adb push rom.zip /sdcard/0
(0 required for cwm and cm10.2)
flash that rom
enable debugging
run lgflash tool one that supports large files or the online one it will pass the battery and auto restart in download mode there it will give error just unplug replug and retry and it will be flashed this time.
Click to expand...
Click to collapse
I am unsure what this is but I am interested? Thanks, I ended up doing what I was trying to do in the first place and IT WORKED
To anybody that faces the same issue:
in recovery sideload install madmacks TWRP file attached below
after that is installed flash CM11 using the same sideload
The command in adb is adb sideload (your file name in here without the brackets.zip) You must include .zip
It is strange because it didn't work the first 3 times I flashed the ROM and on the fourth it worked, so keep trying
i can fix bootloop to cwm or recovery just 2 minutes. but u have to backup your stock recovery fírst before install cwm or twrp.
so thiss step to solve after u have boot loop. that u need to restore back your stock recovery on mmcblk0p28 then reboot. you will stuck at factory software repair. keep ur fone connected with the computer and type adb reboot. then u can boot into android os. and final step. u reinstall your custom recovery again and Enjoy. this fixing not for newbie and im typing it on my fone. someone can make automation script to help People solve it im lazy
Sent from my Optimus G Pro using Tapatalk
thaiminhan said:
i can fix bootloop to cwm or recovery just 2 minutes. but u have to backup your stock recovery fírst before install cwm or twrp.
so thiss step to solve after u have boot loop. that u need to restore back your stock recovery on mmcblk0p28 then reboot. you will stuck at factory software repair. keep ur fone connected with the computer and type adb reboot. then u can boot into android os. and final step. u reinstall your custom recovery again and Enjoy. this fixing not for newbie and im typing it on my fone. someone can make automation script to help People solve it im lazy
Sent from my Optimus G Pro using Tapatalk
Click to expand...
Click to collapse
Thanks for trying to help. I am not running stock and can not get a stock ROM to work (with locked bootloader obviously)
LG Tool is requesting for a TOT file which the E988 doesn't have, I have tried using E98810D_00.kdz file in the software field but it is not recognising the cab file. The DLL file is recognised but I don't know what else to do from there.
LG Mobile Support Tool keeps failing on me due to low battery error which as you can see, I have been trying my hardest to get it to work. Battery is at 99% but it still won't flash! - I am stuch with a custom ROM and a dodgy unlocked bootloader due to the latest release FreeGee.
I tried the old file you attached but it fails to download the image file to unlock my bootloaders, I guess because it is already unlocked.
What I need now is to find a way to relock my bootloader that doesn't involve LG Tool/LG Mobile Tool and then try the old FreeGee app again. Or I find a way to get passed this stupid battery warning
uppon2 said:
I have done this before but I used what seems to be a different version of freegee (didn't have the option to backup efs or flash TWRP) so I unlocked my device and after it had completed I rebooted and then powered down. I put my phone in to CWM and flashed the stock debloated ROM. After flashing this ROM I was stuck in a bootloop. I ended up using LG Tool to get it back to stock. I thought it must have been a random once off issue so I tried again with Freegee, same thing happened, only this time no matter what I do I can not get LG Tool to fix the issue as it keeps giving me the error of low battery even though it is at full capacity. I then tried to use BC2 to flash a kdz file and I get the same error. I have since tried factory resetting, sideloading different recoveries, ROMs and basebands without boot. I have tried to use LG Tool about 50 times and it is not working. I have changed USB ports, reinstalled drivers etc, just keeps giving me that error. Yes I have set permission in the app and I am using Windows 7
Click to expand...
Click to collapse
i have same problem with you, anyone have solution??
kuwir said:
i have same problem with you, anyone have solution??
Click to expand...
Click to collapse
Check this
http://forum.xda-developers.com/showthread.php?p=48225776
Sent from my LG-E980 using XDA Premium HD app
kuwir said:
i have same problem with you, anyone have solution??
Click to expand...
Click to collapse
First try to use LG Mobile Tool. All files and instructions found here CLICK ME
If that doesn't work the follow the instructions I posted earlier and it will get your phone booting again. As for getting back to stock and unlocking the bootloaders without causing kernel issues, I am still waiting for a response from Seth. He has been making a lot of changing as this is a known problem. The latest version is supposed to work like it used to now.
uppon2 said:
I am unsure what this is but I am interested? Thanks, I ended up doing what I was trying to do in the first place and IT WORKED
To anybody that faces the same issue:
in recovery sideload install madmacks TWRP file attached below
after that is installed flash CM11 using the same sideload
The command in adb is adb sideload (your file name in here without the brackets.zip) You must include .zip
It is strange because it didn't work the first 3 times I flashed the ROM and on the fourth it worked, so keep trying
Click to expand...
Click to collapse
Thanks! This worked 100%. Something's really up with the freegee CWM, totally useless. Had 3 days of a headache till I saw this post. I used to be a CWM guy, now TWRP all the way...! The interface is touch based and much easier to handle than CWM. Best of all it doesn't go into a bootloop! Cheers! :good::good:
Okay, everything seemed fine on my s2 until the latest CM download. I install it though CWM and it seems fine but then it says
set_metadata_recursive: some changes failed
E:Error in /sdcard/firmware/cm-11-20140619-NIGHTLY-hercules.zip
(Status 7)
Installation aborted
Click to expand...
Click to collapse
Firmware is just the folder name for where i keep the files i may flash to it. I have tried other
I tried to install CM 10.2.0 and it seems to work. but then when i try and boot, it goes to the splash screen and just stays there. Did I do something wrong that is causing this?
Spud37 said:
Okay, everything seemed fine on my s2 until the latest CM download. I install it though CWM and it seems fine but then it says
Firmware is just the folder name for where i keep the files i may flash to it. I have tried other
I tried to install CM 10.2.0 and it seems to work. but then when i try and boot, it goes to the splash screen and just stays there. Did I do something wrong that is causing this?
Click to expand...
Click to collapse
"Set metadata recursive" probably means you are using a recovery that is too old.
@Spud37
Yes, it means your recovery is outdated. Here is a download link for the latest TWRP that you can flash in Odin as PDA. http://techerrata.com/file/twrp2/hercules/openrecovery-twrp-2.7.1.0-hercules.tar
This link came from teamwins website (teamw.in)
Sent from my SGH-T989
jrc2 said:
@Spud37
Yes, it means your recovery is outdated. Here is a download link for the latest TWRP that you can flash in Odin as PDA. http://techerrata.com/file/twrp2/hercules/openrecovery-twrp-2.7.1.0-hercules.tar
This link came from teamwins website (teamw.in)
Sent from my SGH-T989
Click to expand...
Click to collapse
Well there is another issue with my phone that I have actually worked around for awhile now. The MircoUSB on the phone is broken. I bought an extra battery and swap it, I also just use the SD card to copy anything to the phone. Is there a way for me to flash the phone with the new TWRP from the sd card. Why would the older TWRP not install CM 10.2.0 ROM? Do I have to go older perhaps? Thanks though. Knowing is half the battle
EDIT: Going to try and install 10.1.0 and see if it will let me boot. I figure once I can get it to boot, it will be easier to update the Recovery on the phone.
EDIT 2: No problems or errors occured when I installed CM 10.1.0.zip. However it still got stuck in a boot loop. I did however find a file called superwipe for the T mobile S2. I am wondering if that could help
EDIT 3: Okay so the superwipe worked and i am now running 10.1.0, Is it possible to install a Recovery from the phone without using odin?
What all did you wipe when you installed 10.1? There is a way to update the recovery if you can get the phone to boot. What is the latest thing you got to boot on your phone?
Sent from my HP Slate 7 using Tapatalk
jrc2 said:
What all did you wipe when you installed 10.1? There is a way to update the recovery if you can get the phone to boot. What is the latest thing you got to boot on your phone?
Sent from my HP Slate 7 using Tapatalk
Click to expand...
Click to collapse
I had wiped everything, formatted and fixed permissions, it didn't work. It wasn't until i found the Superwipe that installation worked and i was able to boot to 10.1.0. How can i update/change the recovery from the phone.
Thanks
Spud37 said:
I had wiped everything, formatted and fixed permissions, it didn't work. It wasn't until i found the Superwipe that installation worked and i was able to boot to 10.1.0. How can i update/change the recovery from the phone.
Thanks
Click to expand...
Click to collapse
It is a lot more risky if your usb port doesn't work, since you can't flash back to stock in Odin if something goes wrong. I would recommend that you get someone to fix that USB port before you make too many changes.
DISCLAIMER: I am not responsible for anything that happens to your phone. These changes could brick your phone if something goes wrong. Proceed at your own risk!
Okay, now for the tutorial. These instructions are assuming that you are already rooted. Download this file and make sure you check the md5sum. Rename it to TWRP.img and move it to /storage/sdcard. This will make the next steps easier. If you move the file somewhere else, make a note of the location of the file. If you have not already, install the terminal emulator app form the Play Store. Open it and type the following lines in it.
Code:
su
[CLICK ENTER]
Code:
dd if=/storage/sdcard/TWRP.img of=/dev/block/mmcblk0p22
(Change the path to wherever you moved the file to) [CLICK ENTER]
Reboot into recovery and wipe cache and dalvik. Reboot. If recovery says that system recovery will override it on reboot, click fix. This should update your recovery.
Have a good afternoon,
jrc2
I just received my Nexus 7 2013 16gb WiFi from amazon a few days ago, and it's been great. The recovery has had issues though, it tried to do an OTA update the first day I got it, and when it rebooted, it just stayed on a black screen instead of actually going to recovery, so I had to hard reboot it, to get back to the jellybean it came with. This wasn't a major issue at the time, since then I've just unlocked it and flashed kitkat via fastboot (I'll get lollipop once it has gravitybox or something similar). But since then, I've rooted it and installed TWRP, and TWRP runs fine, but has some weird issues. It seems to not actually see the OS at all, or even the storage filesystem. I have to do a hard reboot to even get out of TWRP, as trying to get out normally gives me the error "Warning blah blah no OS installed, are you sure?", to which I tell it I'm sure and it just reboots recovery. But doing a hard reboot boots into the OS just fine. Am I doing something wrong? TWRP was installed AFTER I installed KitKat and the updated bootloader with the official google factory images, is this a problem?
Some images of what I'm seeing:
1
2
Maybe it's because you're running TWRP 2.8.2.0 which is for Lollipop. If it doesn't work with 2.8.1.0, try with the lastest 2.8.2.2. Running Lollipop at least, everyone had the same problem with both 2.8.2.0 and 2.8.2.1.
where can I place the recovery image where twrp will see it?
Thanks for your suggestion LittleConfucy. I was wondering if you can tell me where to put recovery image that TWRP can see it?
Flashing is a problem without being able to access the image to flash in the stripped down rom file system that twrp boots into. No shared directory in /cache.
Nevermind I got it dialed in.
Sent from my Nexus 7 using xda app-developers app
What did you do to fix this? I just had the exact same thing happen. I had a 5.0 rom and tried to flash a different one but once in twrp no files and the no os line when I tried to reboot. I'm on 2.8.2.0
kingston73 said:
What did you do to fix this? I just had the exact same thing happen. I had a 5.0 rom and tried to flash a different one but once in twrp no files and the no os line when I tried to reboot. I'm on 2.8.2.0
Click to expand...
Click to collapse
I just flashed to 2.8.2.2 and twrp started seeing my internal storage again.
el80ne said:
I just flashed to 2.8.2.2 and twrp started seeing my internal storage again.
Click to expand...
Click to collapse
So if I hold power down and force it to reboot it should boot back into the OS? And once in the OS will I be able to use TWRP manager to flash the latest?
kingston73 said:
So if I hold power down and force it to reboot it should boot back into the OS? And once in the OS will I be able to use TWRP manager to flash the latest?
Click to expand...
Click to collapse
That's what I did.
Sent from my SM-G900V using XDA Free mobile app
Hey guys,so heres the problem...recently i had to use the LG Support Tool and prior to this i was v50020d. When the tool had finished restoring the stock ROM,it upgraded me to v50020f. So i went and successfully rooted it with KingoRoot surprisingly enough with no trouble at all. I then tried to install TWRP Recovery,through the TWRP app,Flashify,Rashr and i even tried Fastboot and ADB which im led to believe don't work with the v500 but i still tried it and had absolutely no success at all in installing TWRP. I have tried flashing every version of TWRP from 2.8.7.1 back to 2.6.3.0 i think using all those apps mentioned above. So i came on here to XDA to see could i find any solution to my problem but no luck either but i did find a post where a script was used,edited and apparently worked. I downloaded the zip file that was used in this process,edited the runme.bat file by changing the last letter of the build to f which would correspond to my build which is v50020f. I saved the edited file and then ran the script which when finished told me that recovery had been installed so i rebooted the G Pad,it started up,the blue teamwin screen came up and then it just hung there for hours! Thats was it nothing more. No recovery installed. So then i went and used Flashify & flashed `twrp-2.8.7.1-v500.img´ and when i rebooted i got 'secure booting error,cause:device unlock:so boot success!!' rebooted the G Pad again and the same thing happened blue teamwun screen loads and then nothing,no recovery. So i flashed the same recovery image with TWRP Recovery app and when it was finished i got the message 'Success!! Flashing recovery was successful,would you like to attempt rebooting into recovery? so i did and again the same thing happened. Teamwin blue screen and nothing more. When i check TWRP Recovery app afterwards it tells me that there is no recovery installed or it us not recognised. Can anybody please,please,please find a solution to my problem? Oh yeah,i even tried booting into recovey by using the power and volume up and down trick too and got the same result. Thank you so much guys...hope you can help.
I think I've seen that in order to install TWRP on the V500 is similar to how on my VK810 variant, at least the part that requires downgrading your bootloader. If it's like the VK810, it has to be the bootloader from 4.2.2. I'm sure there's TWRP threads in these sections, specifically for the V500 that give the details and files.
I'd love to know a way too. I just rooted which went great, but I have the V50020f and don't want to do another thing until I see what happens in this thread. After years of flashing and rooting I finally hard bricked my Lenovo Yoga 10 and this is my replacement tablet, so I don't want to chance it at all. Until I read a concrete solution for this build I'm staying where I am.
That wall of text is really hard to read @[email protected]!c, when I first saw it I was too tired to try and decipher it so ignored it. Now I've had another look.
Have you tried downgrading to an older firmware which people have had success with?
I had trouble when I first got this tablet but kept reading the forum and found a method to downgrade, it isn't pretty but eventually it worked. As I'm new to this device I'm not overly familiar with the different official firmware versions so I'm not exactly sure what you've got.
My tablet was more complicated as the LG tool put the Chinese, no Google apps, version on for me as that is where it was bought. So I had to downgrade so I could get apps from the Play Store to flash my recovery!
So patience and research will reward you.
[email protected]!c said:
Hey guys,so heres the problem...recently i had to use the LG Support Tool and prior to this i was v50020d. When the tool had finished restoring the stock ROM,it upgraded me to v50020f. So i went and successfully rooted it with KingoRoot surprisingly enough with no trouble at all. I then tried to install TWRP Recovery,through the TWRP app,Flashify,Rashr and i even tried Fastboot and ADB which im led to believe don't work with the v500 but i still tried it and had absolutely no success at all in installing TWRP. I have tried flashing every version of TWRP from 2.8.7.1 back to 2.6.3.0 i think using all those apps mentioned above. So i came on here to XDA to see could i find any solution to my problem but no luck either but i did find a post where a script was used,edited and apparently worked. I downloaded the zip file that was used in this process,edited the runme.bat file by changing the last letter of the build to f which would correspond to my build which is v50020f. I saved the edited file and then ran the script which when finished told me that recovery had been installed so i rebooted the G Pad,it started up,the blue teamwin screen came up and then it just hung there for hours! Thats was it nothing more. No recovery installed. So then i went and used Flashify & flashed `twrp-2.8.7.1-v500.img´ and when i rebooted i got 'secure booting error,cause:device unlock:so boot success!!' rebooted the G Pad again and the same thing happened blue teamwun screen loads and then nothing,no recovery. So i flashed the same recovery image with TWRP Recovery app and when it was finished i got the message 'Success!! Flashing recovery was successful,would you like to attempt rebooting into recovery? so i did and again the same thing happened. Teamwin blue screen and nothing more. When i check TWRP Recovery app afterwards it tells me that there is no recovery installed or it us not recognised. Can anybody please,please,please find a solution to my problem? Oh yeah,i even tried booting into recovey by using the power and volume up and down trick too and got the same result. Thank you so much guys...hope you can help.
Click to expand...
Click to collapse
Hi!! I'm in the same boat! Any chance you were able to work out a solution? Thanks so much for any help!!
I know it didn't work for the OP, but coming from bone stock v50020f, I successfully rooted using ioroot25r1, updated Supersu through playstore, then using flashify i installed TWRP 2.8.7.1 (newest I think). Once booted into TWRP recovery, I wiped cache, data, and system, and then installed AOSP Marshmallow. All went smooth as silk, no problems at all. Now I can finally stop being jealous of my wifes Nexus 7!! Hope this helps some.
vettejock99 said:
Hi!! I'm in the same boat! Any chance you were able to work out a solution? Thanks so much for any help!!
Click to expand...
Click to collapse
Thanks.!
i have just used twrp manager apk from playstore (similar to flashify) to get TWRP 2.8.7.1 on stock v50020f, rooted using ioroot25r1 on a mac, with updated Supersu through playstore. just had to run the apk twice as it failed first time, and have booted into twrp recovery.
Had the same problem with the recovery but worked by rooting and flashing recovery with flashify.
I had CWM Recovery and an older cyanogenmod rom installed and I wanted to upgrade to 7.1.2 from here: https://forum.xda-developers.com/lg.../rom-android-7-0-nougat-20161008-r16-t3476750
I copied the rom to internal memory, rebooted into recovery, selected the rom file to install. It showed some messages about patching, then in a couple of minuted erred with smth like "Erro loki-ifying because of incompatible aboot image".
I then rebooted and now it boots and shows "ANDROID" and is stuck on it - looks like it partially updated the ROM and failed somewhere.
I am not sure what to do now - I tried to boot into recovery (Power off -> Hold Power + Vol down till menu shows) but it doesnt work - it keeps booting onto this stuck boot.
Any ideas?
As I understand it, being an amateur ROM flasher, all those 3rd party ROMs need a TWRP recovery to work. Provided your bootloader is unlocked, I'd flash the stock on via RSDlite, flash TWRP 3.1.1.0 (my best experience), THEN install whatever ROM you like in TWRP. This'll start you from a clean slate and wipe ALL data from the phone. I'm guessing you forgot to wipe dalvik and cache before restarting, to. Someone of more experience may chime in, soon.
Sent from my XT1254 using Tapatalk
Crap. Sorry. Disregard. Thought this was a Droid Turbo thread.
Einsteindks said:
As I understand it, being an amateur ROM flasher, all those 3rd party ROMs need a TWRP recovery to work. Provided your bootloader is unlocked, I'd flash the stock on via RSDlite, flash TWRP 3.1.1.0 (my best experience), THEN install whatever ROM you like in TWRP. This'll start you from a clean slate and wipe ALL data from the phone. I'm guessing you forgot to wipe dalvik and cache before restarting, to. Someone of more experience may chime in, soon.
Click to expand...
Click to collapse
But how do I flash anything if I can't get into recovery?
andreyl79 said:
But how do I flash anything if I can't get into recovery?
Click to expand...
Click to collapse
You missed my edit update. I got confused as to which thread I was replying to.
Sent from my XT1254 using Tapatalk
Einsteindks said:
You missed my edit update. I got confused as to which thread I was replying to.
Click to expand...
Click to collapse
Nevertheless you gave me the idea to try looking for a similar LG recovery tool and I just found one. Flashing stock at the moment - fingers crossed
Ok, I installed LineageOS and it worked fine. Must be an issue with the latest AOSP ROM here
andreyl79 said:
Ok, I installed LineageOS and it worked fine. Must be an issue with the latest AOSP ROM here
Click to expand...
Click to collapse
The reason the flash failed is simply the fact you put the ROM on the internal storage, flashing from there wiped the ROM before it gets written. If you had stored the AOSP on an external SD, it would have worked.
As Lineage is based on AOSP, it should have failed also...