Hi!
First of all, to give you some infos: I am runing the latest nightly CM11 on my LG G Pad 8.3 V500 and have the latest TWRP installed.
I was experimenting with a stupid app called LCDDensity for root (I am a noob and should not have done that) and it caused my G Pad to be stuck in a bootloop. I was able to boot into TWRP and the first thing I did was to make a complete backup. I then tried to wipe cache and dalvik cache but the device was still stuck in the bootloop. This was the point were I did not know what elso to do and so I wiped everything and installed the latest nightly (I was running a previous version when the bootloop happend). Everything is working again and I am on the latest version now, but all my data is gone of course.
My Questions are:
If I restore the backup I made when the device was stuck in the bootloop, will this then cause a bootloop again, or can I savely restore the backup? I don't know if that makes any sense, but I am afraid to restore corrupt data somehow.
Second Qustion is a noob question out of couriosity: What else could I have done to get the device to boot up again?
Thanks for your help!
What I would do if I were you
Wipe all
Restore nandroid of bootlooping ROM
Wipe cache + dalvik
Flash the same ROM on top of this nandroid
Reboot
Should easily fix your density issue
May even be able to just flash kernel (as opposed to whole ROM)
If this were me, chances are this app just changes build.prop to change dpi
So I would boot to recovery
adb pull the build.prop and edit it back to normal then push it back and change permissions and then reboot
Future reference
Noob mistakes happen to all at some point, experimenting is good, just always make a nandroid first!
Sent from my Nexus 4 using XDA Premium 4 mobile app
Hello,
I kinda have the same issue. I downloaded SuperSU while on CM13. And when I installed it it went into TWRP and after the installation there was the bootloop. I made a backup (while in bootloop) and I don't want to make a factory reset.
It's been a long time since I've done a backup (except the one in bootloop) so I can't restore.
Can I fix this with the adb (which I don't know how to use it) or can I make a factory reset then restore the backup or will it go into bootloop again ?
Related
Hi,
I've been using cyanogen mod 9 without any issues. recently i upgraded to cyanogen mod 9.1 and have been noticing minor glitches. nothing to be worried about. Recently i used Bluetooth to share files ( have used it before). when i powered off the Bluetooth it rebooted and is now stuck at boot animation. Also cannot connect to my PC. any suggestions or workaround to the problem? would be appreciated.
Restore backup, reflash kernel and/or rom (boot into recovery, or factory reset (in that order). Or if none of those things are a goer, back to stock via Odin try those steps (try to restore backup first if you have one, if not reflash CM & if you get bootloop or whatever after a clean install of CM, factory reset).
MistahBungle said:
Restore backup, reflash kernel and/or rom (boot into recovery, or factory reset (in that order). Or if none of those things are a goer, back to stock via Odin try those steps (try to restore backup first if you have one, if not reflash CM & if you get bootloop or whatever after a clean install of CM, factory reset).
Click to expand...
Click to collapse
I'm sure there is a bug in Bluetooth implementation in mod 9.1. I did a cache wipe, after that it was stuck in another kind of loop. rebooted normally, immediately Bluetooth turns on and it reboots again.
how do i reboot into recovery? previously i was using adb for that. i restored backup ( it was of mod 9) now it wont even boot.
ok. so i finally managed to get it working. i had accidentally restored mod 9 backup onto mod 9.1 so i used odin to flash ClockworkMod-Recovery_5.5.0.4 booted and now i'm back to a month older backup. Oh well since i have to restore my settings anyway why not try mod 10.1?
Hello guys!
Today i installed ClockworkMod Touch recovery and installed SuperNexus 2.0 Build 4 Rom , the whole process took less than 5 minutes. But before i installed SuperNexus i did a "Nandroid?" backup which went fine and took lots of space xD Anyway i proceeded with SuperNexus and it installed fine and played with the rom for a few hours ... i decided to restore the backup so my whatsapp and all that stuff comes back .. i didnt know that it'll restore system too! Ofcourse the phone went on a bootloop so i went to CWM and wiped data/factory reset and the phone booted with Stock 4.1.2 and the phone is kinda slow at the first boot ... now i dont really know what to do :/ The nandroid backup is large and im afraid the SuperNexus rom wont fit and it'll cause errors n all xD Im really stuck at this point , should i repeat installing SuperNexus?
EDIT: I cleared 4.6GB of space , what to do next?
the backup restore shouldn't have caused a bootloop, that's weird.
it restores everything - system and data. so if you want to keep the data when switching ROMs, use Titanium backup or something if the sort. try restoring again. if it fails, try a custom restore of /data
Glebun said:
the backup restore shouldn't have caused a bootloop, that's weird.
it restores everything - system and data. so if you want to keep the data when switching ROMs, use Titanium backup or something if the sort. try restoring again. if it fails, try a custom restore of /data
Click to expand...
Click to collapse
Im not sure if its a bootloop , it keeps restarting boot animation after 1min , i fixed it anyway by wipe data/factory reset option thru recovery and its on stock now booting fine , Shall i flash SuperNexus again normally ? Other than wipe data/factory reset is there anything else to do ?
I mean, if you don't care about your data being lost - then sure
Yeah no probs , contacts on sim and pic's and movies on sd card , Ill just have to redownload my games and all Ill charge my phone then proceed , thanks One more question. Since I installed SuperNexus before does it have system files that I need to delete? Or wipe data/factory reset will cover it?
Sent from my GT-I9300 using xda app-developers app
no, a data wipe will do.
Success Thanks for the help xD I learned a lesson Ill use titanium backup from now on
Hello everyone, I hope you can help me on this one since I'm already panicking.:
I have a Galaxy S3 international version, with Android 4.2.2, rooted, Philz recovery.
Wanted to flash a custom ROM, backed up EFS folder and data. Only thing missing was doing a NANDROID backup. Did the NANDROID backup to sdcard and rebooted....and now device won't start; it's stuck on the "SAMSUNG" logo. , WHAT THE HELL DID I WRONG?
I haven't formated anything or handled any system folders or anything. Just went , like in previous android phones, to recovery, made backup and rebooted. Any ideas? many thanks!
rhrs1987 said:
Hello everyone, I hope you can help me on this one since I'm already panicking.:
I have a Galaxy S3 international version, with Android 4.2.2, rooted, Philz recovery.
Wanted to flash a custom ROM, backed up EFS folder and data. Only thing missing was doing a NANDROID backup. Did the NANDROID backup to sdcard and rebooted....and now device won't start; it's stuck on the "SAMSUNG" logo. , WHAT THE HELL DID I WRONG?
I haven't formated anything or handled any system folders or anything. Just went , like in previous android phones, to recovery, made backup and rebooted. Any ideas? many thanks!
Click to expand...
Click to collapse
If its stuck in a bootloop factory reset and wipe cache in recovery.If that does not work install your backup and lastly if that doesn't work flash stock with odin.
Always remember the first thing to try whenever you are stuck in a bootloop is to factory reset wipe cache in recovery.
tallman43 said:
If its stuck in a bootloop factory reset and wipe cache in recovery.If that does not work install your backup and lastly if that doesn't work flash stock with odin.
Always remember the first thing to try whenever you are stuck in a bootloop is to factory reset wipe cache in recovery.
Click to expand...
Click to collapse
I did a full wipe and cache wipe and everything back to normal. What puzzles me is what was it that put the phone in a bootloop?
rhrs1987 said:
I did a full wipe and cache wipe and everything back to normal. What puzzles me is what was it that put the phone in a bootloop?
Click to expand...
Click to collapse
Good question but unfortunately I've not got a definite answer for you.Some times it is files leftover from a flash but no matter how experienced you are at flashing, bootloops are just one of those things you have to get used to.[emoji1]
tallman43 said:
Good question but unfortunately I've not got a definite answer for you.Some times it is files leftover from a flash but no matter how experienced you are at flashing, bootloops are just one of those things you have to get used to.[emoji1]
Click to expand...
Click to collapse
Indeed have to get used to it... many thanks for response tallman43
Hello,
I have a samsung S3 and cyanogenmod 13. I installed supersu because lucky patcher told me that my phone wasn't rooted (even though the root check was ok) and when I tried to install it (from the app. Launching the app was successful) that didn't work so it recommended me to go into recovery and install it from there. I have TWRP so after it was installed my phone got into bootloop.
Now I can't get out of it. I made a backup (while in the bootloop) and I tried wiping cache and dalvik cache but still in loop.
I seriously can't go through factory reset again. I did it a lot of times before and now I installed so many things on my phone and had it changed to my taste in a perfect way so I don't way to lose anything. And unfortunately I didn't make a backup in ages (only the one while in bootloop) and I don't have Titanium backup.
So what to do now ? How can I get out of the bootloop without losing anything ?
Or can I do a factory reset then restore the data from the backup I made without getting into the bootloop again ?
Thanks a lot
Actually I'm stuck at boot animation where the logo of CM is loading (I don't know if it's the same thing as bootloop or not)
I thought that this may help more.
You are on your own. Lucky patcher is banned and you will find no help here with it.
Thread closed.
I'll try and keep this short and to the point, any other info you require to help me out i'll add.
My Z5c is running 32.4.A.1.54, unlocked bootloader and rooted using rootkernel which adds TWRP.
Straight after rooting and after initial setup of the phone I started TWRP and created a backup, all available partitions were selected and the back completed. I then copied it to my PC.
Anyway, no the problem. I was messing with the phone and then after every boot of the phone i kept getting some app crashes. No problem i thought i'll just restore my backup in TWRP. I selected to restore the system and data partion ONLY, then wiped cache & dalvik and rebooted.
It didn't reboot, just the sony logo then a loop back to the sony logo and then into TWRP again. What did I do wrong?
So i decided to restore all partitions except the TA one and that resulted in the same problem. So recover i just flashed stock with flashtool and all is well.
My question is regarding TWRP and restoring a backup. Which partitions do you have to restore? All of them? What is safe to omit when doing a restore?
andybog said:
I'll try and keep this short and to the point, any other info you require to help me out i'll add.
My Z5c is running 32.4.A.1.54, unlocked bootloader and rooted using rootkernel which adds TWRP.
Straight after rooting and after initial setup of the phone I started TWRP and created a backup, all available partitions were selected and the back completed. I then copied it to my PC.
Anyway, no the problem. I was messing with the phone and then after every boot of the phone i kept getting some app crashes. No problem i thought i'll just restore my backup in TWRP. I selected to restore the system and data partion ONLY, then wiped cache & dalvik and rebooted.
It didn't reboot, just the sony logo then a loop back to the sony logo and then into TWRP again. What did I do wrong?
So i decided to restore all partitions except the TA one and that resulted in the same problem. So recover i just flashed stock with flashtool and all is well.
My question is regarding TWRP and restoring a backup. Which partitions do you have to restore? All of them? What is safe to omit when doing a restore?
Click to expand...
Click to collapse
The old TWRP in rootkernel had a backup problem if i remember correctly. Use a newer TWRP.
Thanks, i'll use 'your' TWRP from here.