I was testing messi2050's arm64 TWRP and LOS. i was using it a while, then decided to restore a old backup with arm64 twrp. restored fine, but i locked myself out when my pattern was unrecognized. I pulled battery and attempted to boot into twrp using hard key method. I was unable to do so, each time it would boot back to system. It seems that the white screen prompting to factory reset has dissapeared entirely. The volume keys work fine, so I don't think that's it. I've flashed stock with LG Bridge and LGUP. I've locked and unlocked bootloader. Interestingly, when i flashed stock with LGUP, it didn't factory reset or remove my apps.
Related
So I took the OTA for MM and everything seemed fine. I noticed that if I tried to go into recovery my device would just restart. I flashed the recovery image but the same thing happened. After I tried to flash the recovery file, ADB did not recoginize my device anymore. I flashed TWRP to see if that would work. From the bootloader ADB did not recognize my device but if I went into TWRP my device showed up. I did not install SuperSU from TWRP but when I rebooted I was in a bootloop. So I used the restore to stock tool to reset everything. It flashed fine but failed on the radio file. Now I can't set it up because it hangs at the WiFi screen, ADB does not recognize the device for me to flash again, and I can't figure out how to fix this.
Steeleio said:
So I took the OTA for MM and everything seemed fine. I noticed that if I tried to go into recovery my device would just restart. I flashed the recovery image but the same thing happened. After I tried to flash the recovery file, ADB did not recoginize my device anymore. I flashed TWRP to see if that would work. From the bootloader ADB did not recognize my device but if I went into TWRP my device showed up. I did not install SuperSU from TWRP but when I rebooted I was in a bootloop. So I used the restore to stock tool to reset everything. It flashed fine but failed on the radio file. Now I can't set it up because it hangs at the WiFi screen, ADB does not recognize the device for me to flash again, and I can't figure out how to fix this.
Click to expand...
Click to collapse
Just restore the last stable nandroid you made.
What about fastboot
Steeleio said:
So I took the OTA for MM and everything seemed fine. I noticed that if I tried to go into recovery my device would just restart. I flashed the recovery image but the same thing happened. After I tried to flash the recovery file, ADB did not recoginize my device anymore. I flashed TWRP to see if that would work. From the bootloader ADB did not recognize my device but if I went into TWRP my device showed up. I did not install SuperSU from TWRP but when I rebooted I was in a bootloop. So I used the restore to stock tool to reset everything. It flashed fine but failed on the radio file. Now I can't set it up because it hangs at the WiFi screen, ADB does not recognize the device for me to flash again, and I can't figure out how to fix this.
Click to expand...
Click to collapse
Are you using the new SuperSU beta? The play store / alpha version of supersu is not compatible with MM. I suggest more reading, specifically this thread: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/page425
Also, because you did not fastboot flash the LP modem after returning to stock, your radio/wifi will not work. It's not an issue with the phone, but rather user-error. Fortunatally, it is a simple matter of getting you working again.
My advice is: Flash the stock unrooted MM TWRP backup (you should already be on the MM modem) and you should be able to start over. Just be sure to use the appropriate supersu beta, and DO NOT modify the boot image.
I had been using my phone with no issues for some time (on Nitrogen 7.1) and at dinner I took a picture and then tried to upload it to Facebook. It froze when I tried to do that and ever since, it has bootlooped.
It shows the unlocked bootloader warning and then Google splash screen and that's as far as it gets. I can't get it to boot into TWRP via the volume buttons, but I can get it into the bootloader. It also wont boot into TWRP via the bootloader menu option. I re-flashed TWRP from fastboot but it didn't change anything.
I realize I should be able to factory wipe it with fastboot, but is there any way I can recover my data or better yet get recovery going again?
Seanmiz said:
I had been using my phone with no issues for some time (on Nitrogen 7.1) and at dinner I took a picture and then tried to upload it to Facebook. It froze when I tried to do that and ever since, it has bootlooped.
It shows the unlocked bootloader warning and then Google splash screen and that's as far as it gets. I can't get it to boot into TWRP via the volume buttons, but I can get it into the bootloader. It also wont boot into TWRP via the bootloader menu option. I re-flashed TWRP from fastboot but it didn't change anything.
I realize I should be able to factory wipe it with fastboot, but is there any way I can recover my data or better yet get recovery going again?
Click to expand...
Click to collapse
Don't know if this is going to help out not but worth a shot
http://forum.xda-developers.com/android/help/guide-revive-angler-bootloop-t3454938/page1
Hello
I had my phone on the VNS-L31C113B132 firmware, unlocked, rooted.
Then I got a message about a new update (VNS-L31C113B141), so naturally, I downloaded the update.app and tried to flash it through twrp with no success, so I used the up+down+power method, it worked, and all was well, except i lost root, lost twrp, and the bootloader seemed to be locked again. No data or apps were deleted though. Then I updated to B150 same method.
any idea why root and recovery are gone? and how can I check if my bootloader indeed is relocked?
That is a completely regular behavior. You can check by booting to bootloader (holding up and power button when the phone is turned off), it will show you a white screen with the Android robot and info on bootloader and FRP status. To get everything back, just unlock the BL again, flash TWRP again and root again, no harm will be done, and your root software (e.g. Xposed) will start working again (although for xposed, you'll have only the client, the framework has to be flashed via TWRP once again).
Klorec said:
That is a completely regular behavior. You can check by booting to bootloader (holding up and power button when the phone is turned off), it will show you a white screen with the Android robot and info on bootloader and FRP status. To get everything back, just unlock the BL again, flash TWRP again and root again, no harm will be done, and your root software (e.g. Xposed) will start working again (although for xposed, you'll have only the client, the framework has to be flashed via TWRP once again).
Click to expand...
Click to collapse
unlocking again may result in factory reset.... or is there another method that keeps everything?
Moemen Shahawy said:
unlocking again may result in factory reset.... or is there another method that keeps everything?
Click to expand...
Click to collapse
Unfrtunately yes, the phone will be reset. All you can do is to back it up and then restore it. Next time you update firmware, update it with "update.zip" from TWRP, this way, only recovery and root will be removed, but not the BL unlock.
look around, it is a workaround for skip factory reset in unlock/relock procedure.
So a while ago I had dirty flashed the Oreo update from this link: OREO open to give it a try and see if I could actually get away with a dirty installation. Phone was working ok but battery drain has been enormous, around 30-50% worse than with Android 7.1 especially on idle so I thought ok time to do a proper factory reset by wiping everything (Dalvik, cache, system).
Now, I selected Factory Reset from within the OS (not TWRP) but during the first reboot it booted into TWRP asking me for decryption password, I did a wipe so it forgot all about it but now it only boots into TWRP no matter if I do an Advanced Factory Reset wiping everything via TWRP's menu, phone starts, shows the LG logo for a couple of sec and then TWRP screen shows up.
I am thinking I should flash a stock Oreo recovery in order for the boot to the OS but not 100% sure if this will cause more trouble.
mclisme said:
So a while ago I had dirty flashed the Oreo update from this link: OREO open to give it a try and see if I could actually get away with a dirty installation. Phone was working ok but battery drain has been enormous, around 30-50% worse than with Android 7.1 especially on idle so I thought ok time to do a proper factory reset by wiping everything (Dalvik, cache, system).
Now, I selected Factory Reset from within the OS (not TWRP) but during the first reboot it booted into TWRP asking me for decryption password, I did a wipe so it forgot all about it but now it only boots into TWRP no matter if I do an Advanced Factory Reset wiping everything via TWRP's menu, phone starts, shows the LG logo for a couple of sec and then TWRP screen shows up.
I am thinking I should flash a stock Oreo recovery in order for the boot to the OS but not 100% sure if this will cause more trouble.
Click to expand...
Click to collapse
Flash the oreo update zip from westwood or zefie. You can find it in the rom and development section. Search for v20a
mprovi_15 said:
Flash the oreo update zip from westwood or zefie. You can find it in the rom and development section. Search for v20a
Click to expand...
Click to collapse
Thanks but being impatient, I tried flashing the stock recovery. This seemed to free the booting and reset process, phone showed the LG logo, then for 2 seconds "Deleting" then LG Logo again and I thought the factory reset was in progress. After like half an hour still stuck in LG logo I realized I've probably soft bricked it. Phone only starts and gets stuck in LG Logo. So I entered bootloader and re-flashed TWRP but unfortunately now I can't find a way to boot into recovery (the irony). Phone just starts and gets stuck in LG logo forever, only thing i can do is use Power+Vol down to reboot into bootloader but no way to boot into recovery or even shut it off. Any way to enter recovery at this state and flash the OREO zip?
I realize I should have just waited for instructions but coming from consecutive unlocked Nexus devices i thought the steps and processes would be similar...
Try to discharge the phone completely (to shut it off) and enter download mode (I don't know any other method to do it). With LG UP flash stock kdz from your model, if you search a bit you will find it. This should work. If it don't work I've seen a couple of posts with the same problem as yours, search for the solution there, but if you can enter download mode it should work LG UP.
mprovi_15 said:
Try to discharge the phone completely (to shut it off) and enter download mode (I don't know any other method to do it). With LG UP flash stock kdz from your model, if you search a bit you will find it. This should work. If it don't work I've seen a couple of posts with the same problem as yours, search for the solution there, but if you can enter download mode it should work LG UP.
Click to expand...
Click to collapse
Thanks for the quick reply. With a bit of Googling I found that you can use volume down to enter stock recovery. This confused me as when I did it I expected to see the TWRP welcome screen. Instead I saw the stock recovery screen which only gives you the option to do factory reset. I did it and then rebooted again into recovery and all of a sudden I saw the TWRP screen! I remember there is something weird with how TWRP sticks to the system or not, again very confusing compared to Nexus devices. Anyway, since I managed to enter Recovery I copied the OREO flashable zip to internal memory and flashed and phone booted fine, now I am waiting to set up a fresh 8.0 installation :good:
mclisme said:
Thanks for the quick reply. With a bit of Googling I found that you can use volume down to enter stock recovery. This confused me as when I did it I expected to see the TWRP welcome screen. Instead I saw the stock recovery screen which only gives you the option to do factory reset. I did it and then rebooted again into recovery and all of a sudden I saw the TWRP screen! I remember there is something weird with how TWRP sticks to the system or not, again very confusing compared to Nexus devices. Anyway, since I managed to enter Recovery I copied the OREO flashable zip to internal memory and flashed and phone booted fine, now I am waiting to set up a fresh 8.0 installation :good:
Click to expand...
Click to collapse
OREO flashable zip? I am searching it for a long time, where did you find it?
Using the miflash tool I flashed stock firmware (some version of android 8) after previously having a custom ROM installed. Everything worked fine until I rebooted after updating to the latest version using OTA.
My phone never got past the android one screen where it would freeze part way through, and after removing my sim card I could get to the pin unlock screen before the lock screen but after inputting the correct pin it would reboot and ask me for it again and again. I can get into fastboot fine but since usb debugging wasn't enabled and my bootloader is locked I can't reflash.
Booting into recovery also only brings me to a screen where the android mascot has a red triangle with an exclamation mark and a message saying "No command", so I can't factory reset.
Is there anything I can do to unlock the bootloader in this state or factory reset? (all flash tools and fastbooting into TWRP require the bootloader to be unlocked which in turn requires usb debugging to be activated)
Thanks for your time.
Update: I messed around with stuff on the cli based tissot tool and used option 2 to boot me into TWRP. It didn't do that but brought me into android where a system process kept repeatedly closing until a random factory reset happened.
I then got into normal android for a bit before I had to reboot (did remember to unlock the bootloader this time). I can now install twrp fine but every time I install the stock rom using miflash or try to install resurrection remix through twrp I get the same bootloop issue.
For some reason also my internal storage is completely empty no matter what i do so i need to sideload roms via sd card. And sometimes twrp gives me the error "failed to mount /system"
Trying the latest version of LineageOS next.
Update 2: if you have the same issue I had, the only working fix I've found is this restore point for twrp. Have not tried to update yet in case it breaks again but will make a final update with how that goes.
[SOLVED] Mi A1 BOOTLOOP
THIS PROBLEM IS VERY ANNOYING!! (The reason is because i didn't backup EFS before i flash Custom ROM) And I would like to share how to RESOLVE it. **your phone must be Unlocked Bootloader. Search Google how to do it. (Quick tip: in Fastboot...
forum.xda-developers.com