I have installed Unofficial CM 13 successfully, but I forgot to root the device, so I go back and flash supersu file and reboot - I think I flashed wrong version for marshmallow. now phone stuck at cm boot animation, I have no recovery, only has access to download mode. I also have no access to phone through adb or fastboot.
I was in the similar situation before, where I was stuck at lg logo, and fix it by flashing stock rom (now I cannot find that thread), but now it tries to boot the rom, seems like a different situation.
What should I do?
lg g2 stuck on lg logo
Behzadsh said:
I have installed Unofficial CM 13 successfully, but I forgot to root the device, so I go back and flash supersu file and reboot - I think I flashed wrong version for marshmallow. now phone stuck at cm boot animation, I have no recovery, only has access to download mode. I also have no access to phone through adb or fastboot.
I was in the similar situation before, where I was stuck at lg logo, and fix it by flashing stock rom (now I cannot find that thread), but now it tries to boot the rom, seems like a different situation.
What should I do?
Click to expand...
Click to collapse
just short connectors and flash all partations again.
Related
Hi,
I was on a rooted android 4.4.2 official, when i tried to install custom recovery using Flashify.
https://play.google.com/store/apps/details?id=com.cgollner.flashify
There was the Secure booting error and booted normaly.I found out that this was not possible so i quit.
Today a got an update from LG so i installed it. The phone rebooted giving the Secure booting error, and it stayed black screen.
Googling i found this tread
http://forum.xda-developers.com/showthread.php?t=2582142
I folowed it but i thought since my phone had problem with it's recovery, just flashing the recovery.img would be ok.
I restarted the phone bat it would not start. It desplays the lg logo restarts, lg logo restarts.
I can boot the recovery but it does not work. When i press recover it just restarts.
I cant boot download mode or anything else, i have been googling the hole day.
I would apricciate your help. It is a one month old phone.....
Thanks
Skroutz said:
Hi,
I was on a rooted android 4.4.2 official, when i tried to install custom recovery using Flashify.
https://play.google.com/store/apps/details?id=com.cgollner.flashify
There was the Secure booting error and booted normaly.I found out that this was not possible so i quit.
Today a got an update from LG so i installed it. The phone rebooted giving the Secure booting error, and it stayed black screen.
Googling i found this tread
http://forum.xda-developers.com/showthread.php?t=2582142
I folowed it but i thought since my phone had problem with it's recovery, just flashing the recovery.img would be ok.
I restarted the phone bat it would not start. It desplays the lg logo restarts, lg logo restarts.
I can boot the recovery but it does not work. When i press recover it just restarts.
I cant boot download mode or anything else, i have been googling the hole day.
I would apricciate your help. It is a one month old phone.....
Thanks
Click to expand...
Click to collapse
are u stuck in cmw recovery??
Stock recovery.... :/
Sent from my GT-I9100 using XDA Free mobile app
Same Problem here! Exact Same
Also having this issue, stuck in the secure boot loop, can't get to download mode.
Im exactly the same - im stuck in TWRP and cant boot into Download mode at all - just get the LG Bootscreen then straight into TWRP Recovery no matter what i do
Did we all except some kind of update from LG........ i wonder if this the link here and is now a common problem?
Mine was this and i thought it was just an app update for the stock apps and now im stuck big time
Any luck guys or solutions then please post here so we can keep it together and help each other!
Yeah I got an OTA update for my D803-Bell model, upon restart entered the secure boot error loop.
Sounds like, via this thread that it's commonly happening to people who had TWRP or CWM (or even aborted / possibly never completed installs like me) got nailed.
As per that thread, and everything else, I've tried every option possible -- no download mode. Recovery mode doesn't restore anything, just resterts to lg logo -> secure boot error -> black screen. Shows as QSHSUSB_BULK in windows/linux, and I can see those 25 partitions in linux (but reflashing openrecoverytwrp__.img over the recovery partition didn't help. I'm waiting to find out how I can make my own copies of those various partitions listed, from another D803-Bell model I have access to. All the D803 .img files on those links in that thread, appear to not contain D803 Bell stuff, just Telus, Rogers, etc... so I'll likely have to source my own.
I just took a shot in the dark recommended by a friend -- and fixed my phone.
I zeroed out the 'fota' partition on the phone. As seen in this thread ; http://forum.xda-developers.com/showthread.php?t=2451696
Just did a dd if=/dev/zero overtop of the fota partition, which was 25 for me from my linux box. One quick power cycle later, and I'm fully functional again, and the OTA update that killed me is still showing as available again.
So I was relatively ok playing with my lg g2, rooted and have twrp 2.8.6.1 installed. It has been couple of months since I can't connect to freedompop/sprint network -- I can't change the cdma setting from nv to ruim/sim, I am thinking that it was the cause. Then I decided to upgrade twrp to 3.0.2, I boot into twrp, flash img, recovery, then I can't boot back to recovery. Something with fastboot. Surprisingly, I still can boot to system. Check root access, still have it. Then I used flashify to flash twrp back to 2.8.7 but to no avail, still the same thing, no recovery but boot into the system. Then I use autorec for ls980 on androidfilehost by bender_07, that's when things went down. Screen just black, not even lg flash screen, nor download mode, nor recovery. When I plugged the phone to computer, it asks to format multiple drives (15 or so), I am not sure where to go now. Anyone have any ideas?
-Found a solution, managed to get download mode working and tot-ing back
I got my Mi A1 today and it came with Android 7 installed, so I decided to install LOS. I unlocked the bootloader and then I booted into TWRP using fastboot (I didn't flash it), it gave that "system is read-only" warning. I tried to reboot to system without doing anything and it was stuck in a boot loop. Then I booted into TWRP again and flashed LOS sucessfully. When I tried to flash gapps, however, it failed claiming I was still running Android 7. I rebooted and it booted sucessfully into LOS, but that was the last time the phone ever booted. Now it shows the unlocked bootloader message and then gets stuck in a blinking black screen. I can't even boot into recovery or fastboot anymore.
iamleobn said:
I got my Mi A1 today and it came with Android 7 installed, so I decided to install LOS. I unlocked the bootloader and then I booted into TWRP using fastboot (I didn't flash it), it gave that "system is read-only" warning. I tried to reboot to system without doing anything and it was stuck in a boot loop. Then I booted into TWRP again and flashed LOS sucessfully. When I tried to flash gapps, however, it failed claiming I was still running Android 7. I rebooted and it booted sucessfully into LOS, but that was the last time the phone ever booted. Now it shows the unlocked bootloader message and then gets stuck in a blinking black screen. I can't even boot into recovery or fastboot anymore.
Click to expand...
Click to collapse
It seems you will have to flash stock ROM using Mi Flash (no idea how to use it so search it) and, once is done, flash LOS again.
EDG_ said:
It seems you will have to flash stock ROM using Mi Flash (no idea how to use it so search it) and, once is done, flash LOS again.
Click to expand...
Click to collapse
I somehow managed to get to fastboot and then I used MiFlash to flash the stock rom. I'm back to the bootloop, which is an improvement, because at least I can consistently get into recovery and fastboot.
The phone got stuck in that black screen after I tried to flash LOS, should I actually do it again?
EDIT: I flashed the stock rom a second time and it's working again. I don't know why, but I'll take it.
iamleobn said:
I somehow managed to get to fastboot and then I used MiFlash to flash the stock rom. I'm back to the bootloop, which is an improvement, because at least I can consistently get into recovery and fastboot.
The phone got stuck in that black screen after I tried to flash LOS, should I actually do it again?
EDIT: I flashed the stock rom a second time and it's working again. I don't know why, but I'll take it.
Click to expand...
Click to collapse
Update to stock Pie before trying to reinstall LOS again. Hope this time works.
AA
You should install 1.0.8.0firmware first before install 9 ROM!?
Hello,
First to get this out of the way i have searched the topic and there were several "solutions" none worked for me.
How it started, I downloaded the latest LieneageOS update as always, set the phone to do it's thing, came back and the phone was stucked on OP log, tried a little reboot, nothing.
No access to recovery or fastboot.
computer wouldn't recognize device even after installing drivers, this guide helped me a little https://forums.oneplus.com/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
found tools got fastboot back and original recovery.
via fastboot attempted to installed TWRP
fastboot flash recovery twrp****.img
and then tried to boot into recovery
fastboot boot twrp****.img
Not able to boot into twrp
after all that my phone still stucked on the boot OP logo
any help would be greatly appreciated.
Anyone has any idea, sorry I have been scouring and reading everywhere, but I can't find a solution.
Thank you
So i have been trying many things and finally getting somewhere. I apologize for the long post, but i have been trying so many things to get this device back to speed.
So flashing TWRP newer version for some reason is not letting me boot into recovery.
I have flashed twrp-2.8.7.0 and i am able to boot into recovery, however when trying to install the ROM (LineageOS 16) i get error E3004.
Searching the web i find that the correction is to that error is to update TWRP, thus i have tried flashing
twrp-3.2.1-0 and twrp-3.1.1-0 and once installed i am not able to boot into recovery again.
I flashed 2.8.7.0 and i was able to get in, thus from inside TWRP i did an image install of twrp-3.1.1-0 and rebooted, recovery won't load. I proceeded to repeat this until i get a result.
I flashed twrp-3.0.2-0 and be able to boot. However still not able to install LOS.
Once i tried flashing twrp-3.0.2-1, recovery won't load.
For sake of argument i flashed twrp-3.0.2-0 and attempted a image install for twrp-3.0.2-1, but the system still won't boot to recovery.
I have completely formatted the phone.
I hope someone could give me a little advice . Thank you.
Hello
Sorry for my bad english
a few months ago, i decided to flash my first custom rom (One UI rom) and it worked fine
then i was testing a lot of other roms too until i tried lineage os 20
when i flashed lineage os 20, i decided to try another rom but i was stuck on the twrp logo screen. i tried methods of fixing it but none of them worked.
after trying a method of flashing twrp once again, it failed and i got stuck in a reboot loop and could only boot into download mode. so i booted into download mode and flashed a stock rom.
everything was working fine again until i wanted to try another custom rom. At first whenever i would flash twrp, they would always fail. but later i found the cause of that and fixed it. then, flashing twrp would always pass but my device would get stuck on a reboot loop once again and i had to flash stock rom again.
i tried rooting using auto root but it would show me a verification failed error and i had to reset my device. so now im stuck on a device which cannot flash twrp, nor can it be rooted. its been 1 month and i could not find a viable solution so any help would be extremely appreciated.
You have to just reflash your fastboot rom with fastboot mode unzip it and double click on flash_all.bat file or something like that
it is a samsung, there is no fastboot mode