Hello i need help please.
I was trying to flash twrp using adb and fastboot when i accidentally flash aboot.img into system and now it wont boot into the system and it stuck on lg logo and it wont let me boot into recovery mode. When i do the Vol. down + power it directs me to factory data reset and I tried resetting it and gave me an error "Your device is corrupt. It can't be trusted and may not work properly."
Does anybody know how to fix this issue please?.
Related
I have a big problem at the moment... I wanted to boot into recovery mode, then an android icon with a red exclamation mark appeared. After I tried to boot into the recovery again using Power + Volume Up, it appears again. Since then I can't reboot my Nexus 10 normally. Bootloader says:
Reboot Mode Flag: Recovery
I think my Nexus 10 is always trying to boot into recovery, but this is no longer working... what can I do to get it work again?
Hope someone can help me with this
Edit: I could finally solve my problem I used fastboot to flash a new recovery that is working, after this I rebooted into recovery and restarted the system. Because this wasn't working, I had to get back to factory settings, but it is working
I decided to unlock the bootloader so that i could flash TWRP recovery but after unlocking the bootloader on my device, it has been stuck on the logo screen with "powered by android" under it. I have tried using fastboot to clear userdata & cache but that just leads to my phone again being stuck on the logo screen. The device also can't boot into recovery. When I chose to power off in fastboot it causes me to be stuck on the logo screen. Any help is appreciated I am on android oreo btw
Did you try a back to stock zip? go to fastboot and run flash-all.bat, while your device is plugged in ofcourse.
supervandd said:
I decided to unlock the bootloader so that i could flash TWRP recovery but after unlocking the bootloader on my device, it has been stuck on the logo screen with "powered by android" under it. I have tried using fastboot to clear userdata & cache but that just leads to my phone again being stuck on the logo screen. The device also can't boot into recovery. When I chose to power off in fastboot it causes me to be stuck on the logo screen. Any help is appreciated I am on android oreo btw
Click to expand...
Click to collapse
Let me guess.
You unlocked the boot loader and flashed TWRP and now you are looping, right?
There is no compatible TWRP that is compatible with Oreo on this phone.
You cannot leave TWRP installed. You can only install it along enough to get the recovery to boot.
You then must flash the stock boot image.
I had this problem tonight also. In my case I suspect it had to do with the install of magisk in which I checked both boxes and patched the bootloader. on reboot I was stuck on boot. Just wanted to add my solution. I got the pie back to stock zip here https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681 then I put it into the adb folder and ran the flashall.bat script. I tried the no wipe one and it saved my information. very happy I didnt have to resetup my phone in the end.
did you remember to flash a stock boot.img before flashing magisk (to clear TWRP?)
Hello!
I just repaired the display of my OP2 and when turning it back on it went straight into bootloop. Only showed the OP Logo and android on the bottom. ADB obviously doesnt work and tried to all partitions via fastboot to get fresh start. After completely resetting I unlocked the bootloader again just to be sure. Then I tried to flash twrp 3.2.1-0. it say dtb not found error. I tried a twrp 3.0.0-0 and it said succesfully flashed but after automatically rebooting the screen just turns black. I can the into fastboot mode or into bootloop can't do anything else. I also tried the MSM8994DownloadTool.exe but it just returns into bootloop again or turns black.
Help pls
I used TWRP to flash official lineage os 16, it was working fine but a new update came and it booted directly into recovery to install firmware. It could not install it . I was stuck in recovery. when I flashed my backup of lineage os it indicated some error saying /system not found. I then searched over and run some command in unlocked bootloader fastboot to fix it. I found a thread on xda to fix system error in TWRP and run cmd "fastboot erase system "also erased boot and recovery then clean installed boot and recovery but my bootloader was gone.
Now it's stuck at powered by android only and with no asus logo. I used asus flash tool with raw image file
to get into stock rom but failed.
THE UNLOCKED BOOT LOADER IS LOST
when I press volume up and power key the system bootloader comes but the deafult bootloader and the unlocked screen message is not showing.
and when i press only the power button there is no asus logo the phone is stuck at screen saying "Powered by android"
please help !!
Hi,
I have been using my P Smart (FIG-LX1) for a while with LineageOS 16 and decided to move on to Android 10. Installed LineageOS 17.1 (found it on this forum) and pph-Magisk 20.3 for root - it did work, but the system was unstable so i decided to try AOSP 10.0 instead. I entered TWRP, wiped cache,dalvik,system and data, flashed the ROM, gapps etc. It was advised to now flash stock recovery and use it to do a factory reset - and now i'm stuck here.
After flashing the recovery_ramdisk img the phone stopped being able to enter any recovery at all. The system itself does not boot (stuck on the "Your device has been unlocked (...) Your device is booting now..." screen forever), the recovery never appears (previously in the start screen with 'unlocked device' warning it used to suggest pressing volume UP to enter recovery, now it only shows "Your device is booting now"). As i can still access fastboot, I tried flashing TWRP again - the TWRP splash screen does appear, but the phone gets stuck on it. Also tried flashing another system's img - nothing changed.
Is there anything I can do or did i just brick it completely?
Thanks for help!
SOLVED:
Apparently running fastboot erase on system and userdata partitions made me able to boot into recovery/erecovery again. I do have another problem now, but it's not connected with this one so I will create another thread for that.
Could you try help me? I can't even get ADB to work anymore