I have an asus zenfone 2 laser running android lollipop. I have turned the USB debugging on for my laptop.
I used to install kingoroot for rooting my phone, and it works fine.
For no particular reasons, i switched over to magisk and uninstalled the kingoroot apps.
The installation was successful, then the app asked me to update it via the app. I updated it, and then it asked me to do reboot.
I rebooted............and i got stuck in bootloop.
I got into the recovery mode and factory resetted the phone but i am still stuck with the bootloop.
I tried to install magisk uninstaller zip from sd card but the installation was unsuccessful
I tried to install the latest firmware from ASUS's official website from SD card and was unsuccessful
I tried to flash the latest TWRP to my device via flashboot. Since many tutorials out there have a TWRP Recovery mode to fix the problem which i don't hace at the time. i used "fastboot flash recovery TWRP.img" command and it said finish.
But it lead me to a new problem. I cannot use "power button+vol.down" key combination to access stock recovery mode. And the TWRP recovery mode doesn't come out as well.
One thing that i can use is the "power button+vol.up" key to access fastboot mode..
I stopped messing around with my devices for now so that i don't make the problems worse. I hope someone can help me out with this problem
BIG THANKS
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.
So, I did brick my D802 in some way.
After a long history from cloudy g2-g3, rr, cm12, cm13, lineage 14.1, I clicked by mistake on the OTA of the lineage.
I thought I could stop the update once in the recovery, but I got stucked in the recovery bootloop. I got rid of it via recovery terminal, but system didn't boot. I tried reflashing lineage, nothing happened, I tried restoring a cm13 full backup, nothing happened, so I got back in download mode to restock with lollipop kdz (the one I used every time I restocked to change rom). It did not work, and I had to download a different KDZ to get to stock again.
Now, all the methods always used to root + recovery didn't work, so I manually rooted, installed the proper AUTOREC, but it didn't work (as I understand after hours of searching because supersu had updated himself in the meantime).
So I tried to install the TWRP image using flashify, it didn't work and corrupted something in my recovery. So i tried to unroot everything and reinstall the original root + supersu without letting him autoupdate. Not working.
Well, now I can boot and I can get in original lollipop rom, but I have no recovery and download mode appears but doesn't work anymore (once I had 3 COM ports when connected in download mode, now I can see only one; kdz flash does not sense the phone connected). When I try to open recovery I got the error "boot certification verify, secureboot error" in the top left corner of the screen, then a white page opens with the message "critical error" "demigod crash handler", volume up to download mode (that opens but does not work), volume down to reboot.
Now, I am stucked, I cannot find any suggestion of what to do to get the recovery working or to get the download mode working again.
Any help will be highly appreciated.
Thank you very much guys.
Not sure will it help but you may give it a try:
https://forum.xda-developers.com/lg-g2/development/tools-srk-tool-useful-toos-lg-root-twrp-t3079076
Hi,
maybe anyone can help me getting out of the bootloop(LG G6 H870)? reason, why I'm stuck in bootloop: I installed magisk v13.0 (beta) and magisk manager 5.0.3 after unlocking my bootloader to gain root access. A new version came out and I decided to installed it because it switched magisk 13 from beta to stable. I opened magisk manager, updated the manager, downloaded magisk v13.2 and flashed it through recovery (twrp). But i wasn't able to get root access (rebooted a few times, but no difference). So my next plan was to uninstall magisk using the magisk-uninstaller.zip and flashed it using twrp. After this step, my phone rebooted over and over again. The only thing i can do is to get into the factory data reset screen. While booting , i connected my phone to my laptop, but obviously its not recognized so I can't execute any adb commands.
Any suggestions how to access recovery mode or how i can leave the bootloop?
Thanks
edit:
I managed to solve my issue in following way:
1. booted into download mode like Killua96 suggested while connected to my computer
2. opened lgup on and flashed the factory image
3. rebooted into bootloader and flashed twrp image
4. copied my backup (which i made with twrp) into the BACKUP folder
5. restored my backup with twrp
6. after reboot I wasn't able to unlock my phone, because my correct unlock pattern wasn't accepted
7. booted again into twrp, navigated into /data/system and deleted locksettings.db-wall, locksettings.db-shm and locksettings.db
8. rebooted one more time and everything was fine again!
iLikeContainers said:
Hi,
maybe anyone can help me getting out of the bootloop(LG G6 H870)? reason, why I'm stuck in bootloop: I installed magisk v13.0 (beta) and magisk manager 5.0.3 after unlocking my bootloader to gain root access. A new version came out and I decided to installed it because it switched magisk 13 from beta to stable. I opened magisk manager, updated the manager, downloaded magisk v13.2 and flashed it through recovery (twrp). But i wasn't able to get root access (rebooted a few times, but no difference). So my next plan was to uninstall magisk using the magisk-uninstaller.zip and flashed it using twrp. After this step, my phone rebooted over and over again. The only thing i can do is to get into the factory data reset screen. While booting , i connected my phone to my laptop, but obviously its not recognized so I can't execute any adb commands.
Any suggestions how to access recovery mode or how i can leave the bootloop?
Thanks
Click to expand...
Click to collapse
Try to connect it to the pc while bootlooping, then turn it off by keeping pressed power and vol- when the display turns off quickly keep pressed vol+ and it should boot in download mode... Good luck
Killua96 said:
Try to connect it to the pc while bootlooping, then turn it off by keeping pressed power and vol- when the display turns off quickly keep pressed vol+ and it should boot in download mode... Good luck
Click to expand...
Click to collapse
Ok, I'm able to access the download mode now. I only have access to a laptop running Linux right now, when I'm back home, I try to flash the stock ROM using the official LG Tools! Thanks for your help!
A little while ago I downgraded my phone. Today I tried to install magisk with a custom rom and TWRP. It didn't work now when I boot my phone it gets into fastboot I have tried formatting it with TWRP and reinstalling the rom but it doesn't fix it. Are there any solutions (downloading to stock via erecovery doesn't work but I can easily open the erecovery menu.
Fastboot says
Android reboot reason:
bootloader 1
no
NA
reboot_enter_fastboot_common_func
I think there is something wrong with the vendor
Solution:I used the dload trick to download stock firmware
Problem 2:I reinstalled TWRP with a custom rom now my phone keeps restarting and not opening the custom rom.
try this rom
https://forum.xda-developers.com/ma...havoc-os-huawei-honor-hi6250-devices-t3813738
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