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.
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?
Hi!
I have a problem with my LG Optimus 3D (P920). Installed the JellycreamV3 and it went good, untill everything was complete and I restarted the phone as instructed. Now my phone stucks at startup logo. Its been like that for hours but nothing happends? I have tried to restarted it several times without any resaults. Please help me. Its my first attempt to install new android version.
Perhaps your install was bad, try reinstalling it, or maybe you didn't clear the cache, system, data?
Sent from my LG-LS980 using xda app-developers app
- Boot into Recovery again
- Wipe data/cache and go to "Advanced" and wipe Dalvik (yes, this will delete everthing, but you don't exactly have a choice)
Reboot. If it's still hanging
- Boot into Recovery again
- Re-flash ROM
And BTW, didn't you make a backup of your original ROM? If not, well.. you won't go any places fast. Another tip is to go to the thread where you downloaded the ROM and ask for help there. People there have flashed the ROM, and some may have had the same issue as you have now.
I try to go into recover-mode but it just starts up and get stuck on the logo:S I did a backup but no matter how i press the buttons to access the recover-mode the phone just starts up and the LG logo comes up. Then its stuck there
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 ?
I was using my phone and all had been working fine for ages. It was in my pocket for a while and when i took it out to use it I saw that it was on the boot animation of CM11. My phone was already on when I last used it so I had assumed it had crashed. I took the battery out and turned the phone on again but it got stuck on the CM boot animation. The last time I turned on my phone before that was when I flashed a supersu zip file to make my root work as I was having some problems. After flashing the supersu zip and told my CWM recovery to restart the system, it prompted me to "fix root" or something like that, and I clicked yes and it booted normally. That was the last time it booted normally before being stuck as it is now. First thing I did after it got stuck was go into recovery and reflash my current rom ( a CM11 snapshot) I then got faced with a status 7 error and so couldnt flash the rom. So then I flashed multiple other CM11 roms, none of which worked, so I flashed a CM10.2 stable rom which worked. I then got faced with the fix root before reboot thing and so I clicked yes. Still had the stuck booting thingy. I tried many things, flashing kernals roms gapps etc and nothing made a difference. I wiped cache, dalvik cache and no difference. I even wiped the system and tried to flash roms but only the 10.2 one would work, still got a status 7 with the CM11 ones. When I wiped my data however and flashed CM 10.2, it booted. I still couldn't flash the CM11 roms though even after a factory reset. So I have the reason to believe something in the data is wrong, not cache system or anything like that. What could it be? I don't want to have to lose all my data in order to be able to use my phone again, even then, something is still wrong as my phone won't flash CM11 roms anymore. So my questions are;
What things could have caused this?
Can this be a problem from flashing the supersu zip (a root issue)
Is it possible to somehow view or copy the internal data on a computer (since I cant get into the operating system), and this would allow me to get all my pictures contacts music etc anything so I can use my phone by wiping data?
Thanks, sorry this is quite long and probably hard to understand whats going on, but help is appriciated thanks
Don't fix root if you wish to use SuperSU instead builded-in cm superuser. Also try to flash via Odin latest recovery. TWRP should be fine. You can mount partitions from recovery level to download data to your computer. Of course if it still exists. If not, if they are corrupted you need to flash stock ROM and repeat whole cm11 adventure again. If Odin successfully flash the stock then it's a chance your partition layout and user data are untouched.
____________________________________________
P3110 / I9300 / I9100 / NEXUS 5 / iPAD2
A friend of mine soft-bricked his old galaxy s2.
The phone is running a custom android 5.1 or 6.0 (I don't remember) that i flashed for him a few months ago.
He said he just disabled the google app (not sure why he did that) and the phone crashed and is now stuck in a bootloop.
Anyway I'm trying to enable the app back and hopefully fix the phone without having to wipe everything and flash back the system.
Does anyone know how/if it's possible from an adb shell in recovery mode ?
I tried the pm command but it just crash in recovery, probably because android is not running.
Maybe i could make it work with a chroot or something. No idea how to do that on android though.
Thanks for the help.
Hi,
In this situation, it would be best to wipe your phone. Avoiding wipes is not what you want to do as this could cause more problems instead.
You could try wiping system partition and cache partition. Reflash the ROM and gapps and see if that helps. You should still keep all of your apps this way and no personal data is affected.
Otherwise full wipe is the only option left.
gsstudios
Thanks for your help, i tried to wipe only system partition and cache but unfortunately the phone was still stuck in a bootloop. Tried then to manually remove all google apps and their data before reinstalling them but it didn't work either. I gave up and formated the data partition which fixed it as expected.