My lg-v410 is stuck in a boot loop and I can't open the boot-loader (Someone here said that if the device turns on it's fixable, but this is looking pretty hopeless)
The Imei is 351633071518370
The reason the tablet is in a boot loop is because build.prop got deleted with a glitch with ES File Explorer
And now I can't restore it.
I have the original build.prop.
No custom recovery.
Boot-loader is locked.
The only thing it does do is open the "factory data reset" and The "msn/imei display" and of course the boot-loop
I would greatly appreciate if some one can help me fix it
The tablet has NO valuable information on it, so wiping doesn't hurt my feelings
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.
Bottom half of the screen is cracked which makes it very difficult to " swipe to" do anything in TWRP. I locked my device and was unable to unlock with backup pin because the keyboard does not function properly. So I rebooted into recovery and accidentally wiped Calvin Cache, System, Data, Internal Storage and Cache. Rebooted phone and it's stuck in a boot loop. I tried using adb but I could not get it to swipe into adb sideload. I found that connecting the phone to my PC does open up /SDCARD/TWRP but there are no other folders in /SDCARD. I moved a ROM from my PC to the TWRP folder and was able to flash it but got stuck in boot loop. Tried flashing a different ROM and it shows a new loading screen but still stuck in boot loop. No other folders are being created to SDCARD.. Haven't had this pphone for more than a week.... Was thinking I could maybe flash a non touch TWRP or CWM to avoid having to swipe to get things done and use the hardware keys.. but why is it being stuck in boot loop after it says it successfully flashed the ROM.
I did flash the 30b file it says to flash prior to flashing the 2 custom lollipop ROMs in the tmo dev forum. Any help, links, advise would be much appreciated. Thanks.
I have unlocked bootloader, flash modified boot.img and recovery but when I boot the device I get 'Your device is corrupt and may not work properly' I then get stuck on the google boot screen. When I go into TWRP recovery it cannot mount anything so I cannot even perform a factory reset.
Please help
did you make a back up?
I didn't unfortunately, I can get into recovery and as long as I leave it as 'Read-Only' it seems to mount everything. I think I need to get a stock image.
Resolved - used a Toolkit to go completely back to stock, kind of scared to try again now.
Follow directions and that won't happen again. Make sure you are on the correct version MDB08K BEFORE you start (you have the OTA), format not wipe in TWRP and you won't get caught in the boot loop.
Failing to do those two things will put you in a boot loop.
What toolkit did you use because i myself have this issue with my nexus 6p
Swatto86 said:
I have unlocked bootloader, flash modified boot.img and recovery but when I boot the device I get 'Your device is corrupt and may not work properly' I then get stuck on the google boot screen. When I go into TWRP recovery it cannot mount anything so I cannot even perform a factory reset.
Please help
Click to expand...
Click to collapse
That warning is normal, and should be ignored if you want unlocked bootloader, custom ROMs, etc.
Here TWRP couldn't mount because you forgot to decrypt after flashing the modified boot.img.
If you have further issues, let me know.
A quick advise - Avoid toolkits. They are handy and easy, but if something goes wrong, it will be hard to track down the cause. On the contrary, doing thing manually, will not only make it easy, but will also help you learn more about your Android, and how it works.
My Lenovo P1ma40 Vibe stuck in a boot loop
I have no Custom Recovery installed, everything is original. I have changed my Boot Animation and rebooted my phone, but unfortunately, it stuck in a Boot Loop(never-ending). And, I haven't made any Backups.
I have many important data stored on my phone, so can't go with Factory Reset. I also tried to replace the "bootanimation.zip" with ADB, but it shows :
List of devices attached
But, then shows nothing, I then reinstalled the driver from Device Management Window(on reading a few answers). But, all my efforts were useless.
Since I have no Custom Recovery installed, I couldn't clear my Dalvik Cache as well. Can I do something to save my Phone and Data as well? I guess if I could replace the custom boot animation with the original, my phone will be saved.
Thanks in advance!!!
PLEASE HELP ME OUT
I'll try to summarise it.
Unlocked my bootloader.
Tried rooting by flashing twrp and then installing supersu (i think i installed a corrupted version, as my phone did not go past the logo).
Deleted all system and cache to install lineageos, hoping it would fix it. It did, but i was unable to use my mobile data.
So i tried flashing the stock firmware for my phone ( H87020f_00_EEO_GB_OP_0817.kdz ) using uppercut, as LGUP did not recognise my phone.
Both twrp recovery and lineage were deleted.
It's back to the old boot sequence for LG phones but it gets stuck at the LG Logo "LG Lifes's Good".
The boot up sequence is, Bootloader unlocked message>LG G6 ThinQ>"Erasing">Bootloader unlocked message>LG G6 ThinQ>LG Logo. and it just stays there, tried waiting for 3 hours (i fell asleep), and it was still stuck.
I seriously need any help i can get for fixing this. I know that i'm an idiot for not backing anything up.
Fixed it
skxxxxxx said:
I'll try to summarise it.
Unlocked my bootloader.
Tried rooting by flashing twrp and then installing supersu (i think i installed a corrupted version, as my phone did not go past the logo).
Deleted all system and cache to install lineageos, hoping it would fix it. It did, but i was unable to use my mobile data.
So i tried flashing the stock firmware for my phone ( H87020f_00_EEO_GB_OP_0817.kdz ) using uppercut, as LGUP did not recognise my phone.
Both twrp recovery and lineage were deleted.
It's back to the old boot sequence for LG phones but it gets stuck at the LG Logo "LG Lifes's Good".
The boot up sequence is, Bootloader unlocked message>LG G6 ThinQ>"Erasing">Bootloader unlocked message>LG G6 ThinQ>LG Logo. and it just stays there, tried waiting for 3 hours (i fell asleep), and it was still stuck.
I seriously need any help i can get for fixing this. I know that i'm an idiot for not backing anything up.
Click to expand...
Click to collapse
I fixed it, i installed the oldest version of the stock firmware using uppercut and now its working again. That was easier than i thought.