Hey guys, rooted my tablet and got teamwin recovery on 5.0.2, my problem that I have found is when I reboot, I will get boot loops until I wipe cache+dalvik cache, then after I will get android upgrading and my tablet is fine, I need to sort the bootloops out, but really don't know why I get them till I wipe my cache.
I am using the wifi only tab with stock rom, rooted with king root then used kingroot to SU if that helps
When you wipe dalvik, the system needs to recompile all apps that you have installed (and the system app if the rom is deodexed). Normally this is done only when you upgrade your system. That's why you get "Android is upgrading".
Personally I don't use Kingroot, I really dislike it. I almost feels like a virus. But that's my opinion. I use SuperSU om my systems.
Related
Hi guys! I've been trying for the last hours to install Cyanogenmod 11 on a friend's S3 international (i9300). After some driver problems CM now installs fine, but after the installation finishes and the phone reboots the phone reverts to Samsung's stock firmware. Even though I select yes at the question that should prevent stock recovery from occurring.
I have tested every solution I could find out there to prevent this:
1. After CM setup finishes, I pull the battery and start the phone in Clockworkmod by holding Vol-up+home+power. Then I have wiped the cache, data and dalvik cache and rebooted. Still reverting to stock.
2. I have tried rooting the phone and removing /system/etc/install-recovery.sh using Root explorer before starting the installation. There was however no file /system/recovery-from-boot.p which was also mentioned in som guides.
Nothing seems to work.
I can't understand that I'm the only one having this problem. Is there a solution out there? Thanks!
r243 said:
Hi guys! I've been trying for the last hours to install Cyanogenmod 11 on a friend's S3 international (i9300). After some driver problems CM now installs fine, but after the installation finishes and the phone reboots the phone reverts to Samsung's stock firmware. Even though I select yes at the question that should prevent stock recovery from occurring.
I have tested every solution I could find out there to prevent this:
1. After CM setup finishes, I pull the battery and start the phone in Clockworkmod by holding Vol-up+home+power. Then I have wiped the cache, data and dalvik cache and rebooted. Still reverting to stock.
2. I have tried rooting the phone and removing /system/etc/install-recovery.sh using Root explorer before starting the installation. There was however no file /system/recovery-from-boot.p which was also mentioned in som guides.
Nothing seems to work.
I can't understand that I'm the only one having this problem. Is there a solution out there? Thanks!
Click to expand...
Click to collapse
1.Root your phone.
2.Install latest CWM or TWRP.
3.Boot into recovery.
4.Wipe Data/Factory reset.
5.Wipe cache.
6.Wipe dalvik cache.
7.Install ZIP from sdcard.
8.Choose your downloaded CM.
Good luck
GeekyDroid said:
1.Root your phone.
2.Install latest CWM or TWRP.
3.Boot into recovery.
4.Wipe Data/Factory reset.
5.Wipe cache.
6.Wipe dalvik cache.
7.Install ZIP from sdcard.
8.Choose your downloaded CM.
Good luck
Click to expand...
Click to collapse
Thanks! The reason I did not do this before was that I am not really comfortable installing manually and was afraid to brick the phone (since it's not mine). But I followed your instructions and it worked perfectly
It's a shame that the automatic installer can't handle this though.
r243 said:
Thanks! The reason I did not do this before was that I am not really comfortable installing manually and was afraid to brick the phone (since it's not mine). But I followed your instructions and it worked perfectly
It's a shame that the automatic installer can't handle this though.
Click to expand...
Click to collapse
Haha! Actually you won't brick your device by installing a ROM for your device. You can only brick it by flashing a ROM from other device without porting it, and I think this will be then only soft-bricked. A hard-brick can be done by flashing basebands from different devices. But I hope you won't do that
Actually by installing a ROM only your system(apps, vendor files, tweaks, etc.) and boot partition(kernel, etc.) will be overwritten. And that won't hard-brick your device
But I can understand your fear. I was same as you when I was a beginner
I rooted my device a few days ago in order to stop the 4.1 ota update, I am currently on 4.0.4 and the device is an xt912.
Today I decided to install safestrap and after installing the recovery and booting into it, I backed up the stock rom.
After backing it up, I clicked on reboot to system.
The device then jumped into a bootloop.
So I cleared cache, dalvik cache, and even factory reset but it won't pass the DROID eye.
So I created a new slot and restored my early backup and to my suprise, it booted up.
I then rebooted back to recovery and cleared system, data,cache and dalvik cache of stock slot and restored the same back up there and rebooted, and it booted up nicely. But after that the recovery kind of disappeared. So I installed safestrap apk again and rebooted to recovery to make sure it flashed.
I was able to boot into the recovery but as I tried to boot back into the rom, I got stuck in a boot loop again.
My problem is if I reinstall the recovery, the device gets stuck in a bootloop, unless I wipe everything and restore my backup.
Also when turn off the phone and connect it to wall charger, the battery sign doesn't show up again.
Can u guys help me out??
Doesn't matter if I loose my stuff.
I just want a working 4.0.4 with root and to be able to charge the device when it's off.
(BTW my version of safestrap is 3.3.0 I think. Its 3 point something.)
I need help ASAP.
Sent from my DROID RAZR using XDA Free mobile app
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
Hi,
I'm using CM13 on my LG d620, recently I tried installing SuperSu, and then updating binary, but normal way did not worked so I tried to install it with TWRP recovery, so my phone rebooted into recovery, supersu script automatically stared and installation was successfull. I wiped cahce, even dalvik just to be sure, and rebooted system, but it is now stuck in bootloop.
So I'm just curious if anyone would know if I can somehow fix this problem, maybe through recovery, flashing some script, or in terminal in recovery, with adb... pretty much anything just to avoid flashing new rom again and losing all of data and setings....
Thanks in advance
(btw, i'm on cm13 6.0.1, latest update to this day, twrp 3.0.0, supersu latest version on google play store i think, and also have enabled root access)
Enigma. said:
Hi,
I'm using CM13 on my LG d620, recently I tried installing SuperSu, and then updating binary, but normal way did not worked so I tried to install it with TWRP recovery, so my phone rebooted into recovery, supersu script automatically stared and installation was successfull. I wiped cahce, even dalvik just to be sure, and rebooted system, but it is now stuck in bootloop.
So I'm just curious if anyone would know if I can somehow fix this problem, maybe through recovery, flashing some script, or in terminal in recovery, with adb... pretty much anything just to avoid flashing new rom again and losing all of data and setings....
Thanks in advance
(btw, i'm on cm13 6.0.1, latest update to this day, twrp 3.0.0, supersu latest version on google play store i think, and also have enabled root access)
Click to expand...
Click to collapse
I end up with same issue now. I could have read this before flashing SuperSu. Now my device is in boot loop. Please help how to fix this without wiping data?
Rasgola said:
I end up with same issue now. I could have read this before flashing SuperSu. Now my device is in boot loop. Please help how to fix this without wiping data?
Click to expand...
Click to collapse
Just flash rom from the recovery, thats it. Let me know if it worked for you
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.