I got this tablet as a gift yesterday. Booted up fine, I updated all apps. Also rooted the tab which went through smoothly. The problem started after I installed Titanium Backup and froze/uninstalled a lot of system apps. Now the tablet has gone into a boot loop. It starts up, boots fully into the OS, and then restarts after around 10 seconds!
I have tried going into Recovery to do a factory reset, but YouTube videos showing the procedure show a menu which I am just not able to get to.
I have also downloaded the latest official firmware file from ASUS directly. Tried putting that on a MicroSD card and then booting up the tablet, but it does not recognise even that!
Basically, I'm screwed for now! And since it is a gift from the US, I cannot even send it in to ASUS for warranty recovery/replacement etc.
Please HELP!! :crying::crying:
Never mind. I've sorted everything out.
Related
First of i'd like to thank the community! I've ran in to numerous issues and have been graciously saved several times.
I'll start of by providing some context in to the issue.
original configuration:
Unlocked - T-Mobile US SIM
AT&T LG E980 factory tot 4.1.2 - flashed using LG Flashing Tool
Root - E980 Universal Root
Unlocked Bootloader - Freegee [Android Marketplace]
Installed Recovery TWRP v2.6 - Freegee [Android Marketplace]
Removed bloatware - AT&T Applications
So from this point the phone was working as expected. I spent hours configuring to my liking and decided to call it a night. Before I called it quits I decided to make a backup using TWRP. Backup took a really long time but it said successful. I left handset plugged in to charger overnight, roughly 6 hours of continuous charging. When I woke up I noticed the phone was in recovery mode. Touchscreen was also unresponsive. I held the power button to allow it to reboot and it rebooted me back to recovery. At this point I knew something was wrong. I attempted to re-install backup files made from previous night, this failed. The phone booted back to recovery. I then installing some zip files I had pre-loaded on to the external SD card, this was CM10.1 and gapps files for E980. I tried this out a few days ago and it was working fine. I decided lets try installing this and see what happens. Install was successful and rebooted. The phone boots back in to recovery. At this point I'm really frustrated. I checked the memory card by running through the TWRP menu. I noticed the file sizes were unchanged but the files were not displayed on both in/ext memory. I decided to finally restore again by using LG Flashing Tool. This by the way has saved my a$$ numerous times. So the one thing I would note, at the 85% when the phone reboots I noticed there was an error, an error I've never seen before. It was a picture of sync icon (large) and android man on top of it and text that said "error 0x123456" I didn't note the exact string. I let it go and monitored the flashing tool, somewhere around 93-95% it rebooted again in to the normal boot sequence. Viola my phone is back to where I started.
So here's some of the questions I had:
How did I end up in the TWRP Recovery boot loop?
Why could I not see the files to install once in TWRP?
Why did TWRP continuously boot back in to recovery mode after successful install of restore?
Why did TWRP continuously boot back in to recovery mode after successful install of CM10.1/gapps zip?
Has anyone seen the LG Flashing Tool error I described above and does anyone have an explanation as to what happened?
Here's my theory on what happened...
My phone was on 4.1.2 as mentioned. I noticed a few times that there was a notification stating the phone had a OTA software update available. The first time I tried to update (already rooted and unlocked) the phone failed to update. The error cited that my phone was believed to be rooted. I paid no attention to this and decided to continue using. Later in the day I noticed the notification again, I opted to try again. The phone updated, or at least tried to. It kept booting in to TWRP Recovery. Nothing I could do could restore it, except flashing using the LG Tool. After experiencing this I knew to leave the OTA alone. I don't know if this is possible but somehow I think the OTA was pushed and forced through while I was sleeping allowing the phone to charge. This is the only time I've seen that behavior. Is that even possible???
Where am I now...?
Phone is restored, I opted to upgrade using the OTA before I start tinkering again. Maybe I won't mess with it at all and leave it alone at this point.
So everything was working well no issues. The other night I am playing a game and everything seemed a bit wonky the touch screen was erratic and the graphics were stuttering so I figured I hadn't rebooted in a long time may as well. Well now the tablet just boot loops and won't come up. I tried doing a factory reset in recovery that hasn't helped. I hadn't gotten the time to try out the custom recovery so I have no backup is there any way to reload this thing from a computer or do I have a brick?
Little back ground I was rooted but no new software was installed in over 2 weeks prior and even upgrades had been at least a couple of days and then just Google stuff. No issues up till this point it was working very well. I was on Lollipop but would be happy to boot either KitKat or Lollipop at this point.
Little bit ticked off the tablet was only 6 months old never abused/dropped at all. I kept it in a sleeve when I wasn't using it and have a case as well. I don't install suspect programs at all. I use the tablet everyday for both work and personal use so I really need to get it going again if possible.
So I found this program called B2CAppSetup.exe in a post for the lg tablet 8.3 I installed it and put my tablet in download mode. It said that my tablet was up to date and that nothing needed to be done but there was an option to "update recovery" which downloaded a 1gb plus file so I assume it was the whole OS and not just the recovery. Took a while to do the reinstall but it did work, first boot took a few minutes but my tablet is running again. I will have to reset everything up again the way I had it but that is OK I had made a backup of my apps and data about 4 or 5 days before this happened so anything lost will be minimal. Hope this is helpful if this happens to someone else.
jpisini said:
So I found this program called B2CAppSetup.exe in a post for the lg tablet 8.3 I installed it and put my tablet in download mode. It said that my tablet was up to date and that nothing needed to be done but there was an option to "update recovery" which downloaded a 1gb plus file so I assume it was the whole OS and not just the recovery. Took a while to do the reinstall but it did work, first boot took a few minutes but my tablet is running again. I will have to reset everything up again the way I had it but that is OK I had made a backup of my apps and data about 4 or 5 days before this happened so anything lost will be minimal. Hope this is helpful if this happens to someone else.
Click to expand...
Click to collapse
Well if I can just find out exactly what I need installed on the computer and how to enter the commands and where to enter them I'd be alright. Its been a long time since I use a computer and I'm stuck in a boot loop for no reason at all except for I rebooted and it is stuck. Can't go past fastboot or recovery or that screen with the big barcode. I did nothing that could affect the operating system and only had some very simple route adjustments made so I don't understand why it is so messed up. But hopefully someone can explain the computer part of this and I'll be straight
Sent from my VS986 using Tapatalk
Hello, I recently went to upgrade Cyanogenmod 12 to Marshmallow, everything went fine, but when I went to reboot the system I got stuck in a boot loop. Following this I wiped my system, data, and stupidly my internal storage so I lost my nandroid backup. Installed earlier firmware (Android 4.4.4), everything worked but my system didnt recognize the SIM card. Opened LG Flash tool and went back to bone stock LG, rebooted and get stuck in intermittent boot loops in varying places along the setup process and once I get to the homescreen with many versions of the Verizon LG software varying from 5.0 to 6.0. I suspect my system permissions are all f***ed but I dont know for sure as I can't get the phone far enough to enable USB debugging. Enabling it in the stock system recovery screen doesnt seem to work. I've gone through many of the threads here regarding boot loops for the G3, but havent seen any with the stock hardware.......Any thoughts on where to go from here?
Bump. Please, any help would be appreciated
I'm stuck and confused:
Had a Nexus 4 and 5 for years. Decided to upgrade this past November to the LG G4 (T-Mobile H811)
Got it to root without touching the boot loader.
In came MM and then I had issues of repeating the process.
I came across a solution, to unlock my bootloader. So I did it and managed to get my G4 rooted while running stock LG MM (H81120i).
Everything was running well for several months, but then I started to see erratic behavior. It would heat-up in my pocket for no reason. It would not save pictures. Connections via WiFi and LTE were breaking up. All in all, I wasn't happy and I missed the stock Google interface.
So I've decided to install CM13. Had many issues of getting it to work for several days, which included persistent closings of Google Play services (and many others) and not being able to make/receive calls (it would automatically reboot) After several different attempts, I managed to get it all working. Cleared/Wiped everything off my internal drive, installed the "LG-H81120i-Flashable.COMPLETE" and "cm-13.0-201605xx-NIGHTLY-h811" and "open_gapps-arm64-6.0-nano-201605xx", all back to back. And then installed manual everything as needed Gmail, Maps, etc.
Everything worked great for about 2-days, until then next morning my screen locked up. Then the phone rebooted. After the reboot, it lasted for about 10-15 seconds in CM13 and rebooted again manually. Continued to reboot over and over, till it then stopped booting with CM13. I thought that maybe I needed to install the latest CM13 zip file, but found I couldn't get into recovery. The first reboot screen, showing "Bootloader State: Bootloader unlocked? and the LG logo would be in a loop. During that time, I could feel the phone getting hotter and hotter.
Sometimes, the phone would boot up into CM fully and last for 5 to 10 minutes. Then reboot again and stay in the first reboot screen.
I managed to get into TWRP recovery and thought that putting back the stock MRA58K image would help. During the install in recovery, the phone rebooted! I never thought it could do that. Eventually I got the stock LG back-up up and running, but it didn’t help, and same rebooting occurred.
I'm stuck and out of options. I would like to get the phone BACK TO STOCK and then perform an RMA. I’m afraid that with the BOOTLOADER UNLOCKED that my RMA will be denied and I’m stuck with what I have.
So can the H811's bootloader be re-locked?
PiCASSiMO said:
I'm stuck and confused:
Had a Nexus 4 and 5 for years. Decided to upgrade this past November to the LG G4 (T-Mobile H811)
Got it to root without touching the boot loader.
In came MM and then I had issues of repeating the process.
I came across a solution, to unlock my bootloader. So I did it and managed to get my G4 rooted while running stock LG MM (H81120i).
Everything was running well for several months, but then I started to see erratic behavior. It would heat-up in my pocket for no reason. It would not save pictures. Connections via WiFi and LTE were breaking up. All in all, I wasn't happy and I missed the stock Google interface.
So I've decided to install CM13. Had many issues of getting it to work for several days, which included persistent closings of Google Play services (and many others) and not being able to make/receive calls (it would automatically reboot) After several different attempts, I managed to get it all working. Cleared/Wiped everything off my internal drive, installed the "LG-H81120i-Flashable.COMPLETE" and "cm-13.0-201605xx-NIGHTLY-h811" and "open_gapps-arm64-6.0-nano-201605xx", all back to back. And then installed manual everything as needed Gmail, Maps, etc.
Everything worked great for about 2-days, until then next morning my screen locked up. Then the phone rebooted. After the reboot, it lasted for about 10-15 seconds in CM13 and rebooted again manually. Continued to reboot over and over, till it then stopped booting with CM13. I thought that maybe I needed to install the latest CM13 zip file, but found I couldn't get into recovery. The first reboot screen, showing "Bootloader State: Bootloader unlocked? and the LG logo would be in a loop. During that time, I could feel the phone getting hotter and hotter.
Sometimes, the phone would boot up into CM fully and last for 5 to 10 minutes. Then reboot again and stay in the first reboot screen.
I managed to get into TWRP recovery and thought that putting back the stock MRA58K image would help. During the install in recovery, the phone rebooted! I never thought it could do that. Eventually I got the stock LG back-up up and running, but it didn’t help, and same rebooting occurred.
I'm stuck and out of options. I would like to get the phone BACK TO STOCK and then perform an RMA. I’m afraid that with the BOOTLOADER UNLOCKED that my RMA will be denied and I’m stuck with what I have.
So can the H811's bootloader be re-locked?
Click to expand...
Click to collapse
Since you live in the US your only option is to apply over voltage to the battery terminal and burn the mobo so that it wont even boot up. The exact method is somewhere around here in xda so you should look it up since you have no other choice
Edit: To answer your question: No
sirsomething said:
Since you live in the US your only option is to apply over voltage to the battery terminal and burn the mobo so that it wont even boot up. The exact method is somewhere around here in xda so you should look it up since you have no other choice
Edit: To answer your question: No
Click to expand...
Click to collapse
If I can't re-lock the bootloader, has anyone had the success of returning their phones under warranty? Through T-Mobile?
Hi guys, bit of a saga here so bear with me...and also it should be mentioned I have little experience/understanding of tech stuff, so that isn't helpful either lol
I've had a Nexus 5x running 7.1.2 for not quite a week; it came with an unlocked bootloader (strangely). Tried to do the usual install twrp & root as I've done with previous phones (all pre-nougat) but all attempts failed. Couldn't boot into stock recovery from the bootloader at all, it would just boot into the system. OK, next thought was that an OTA upgrade to Oreo might work to restore a recovery - but got the BLOD (naturally lol). I found a fix in a modded 4-core Twrp 3.2.1 -0 fbe img + workaround injector zip from osm0sis & XCnathan32 which by some miracle worked.
So far, so good. Ffwd a few days and google play store keeps crashing on opening; I had the feeling that some glitch happened while it was updating, so I tried all the usual fixes like app cache/data wipes and uninstall updates/renistall google play, delete google account etc which failed. Next I tried a cache & data device wipe through twrp - also unsuccessful. Finally, I thought the only thing left to try would be to restore a backup I made on twrp - this led to the current issue of not booting, stuck on the google logo screen. I even thought what the hell! and attempted a factory reset with twrp - same result, where I am now. Google logo screen, however I still have an unlocked bootloader.
Would anyone be able to suggest where I might go from here? I'm pretty sure the version is N2G48C, if that helps.
Any suggestions very much appreciated...wouldn't mind getting to the 1 week mark with a functioning phone lol
Saga #2
Still no idea what's going on. I realised that I'd backed up and recovered the system and vendor .img files, which according to this thread would be a cause of the issue https://forum.xda-developers.com/nexus-6p/help/stuck-google-logo-twrp-backup-restore-t3320840/page3
So I made another backup without those images, did a full wipe and restored it - still does not boot, still only sitting on the google logo. Tried next to open a cmd terminal to see if I could reflash a stock image, but adb could not connect (maybe because the phone would have been on charging and not file transfer mode?)
Last resort as I saw it was to try the NRT, and see if it would flash stock via the bootloop/softbrick option. Process seemed to be OK, judging by the log - but it did not reboot to the system. Now there is a looping bootloop between the google logo and the unlocked bootloader warning.
Following wugfresh's instructions to factory reset from the recovery (the phone won't turn off via the power button so I just booted straight into the bootloader) Looked for the recovery option, selected....and nothing!!
So there isn't a stock recovery??? How does that work?
And what hope is there for this phone now? (I can't think of anything else )
Anyone have an idea? I've never heard of this before tbh!
Well, my problem has been sorted. In the absence of knowing what the hell I should do lol I managed to get a refund for the phone even though it was a refurb to begin with (something to be said for an honest seller who provides a 3 month warranty!) and I picked up a brand new N5x, which was unboxed on Tuesday. Not even 6 hours into setting it up, the phone started to get progressively hotter and then went into bootloop. Got into the bootloader and tried a factory reset - all seemed OK but halfway through the setup process it bootlooped again. Fortunately it was still within the 2 year warranty, and LG didn't argue about authorising a repair for a phone which didn't get even half a day's use on it lol
Authorised Wednesday, walked into the service centre Thursday and a 1 hour wait later had phone in hand with the PCB/motherboard replaced. Has been working fine (and cool!) ever since. Definitely feel lucky to have hopefully dodged a bullet on this one.
Bonus that they upgraded from 6.0 to 7.2.1 while they were at it; apparently LG considers nougat the "latest" stable version for the 5x.