I have the HD10, 5.1.1 and rooted with kingroot. I already had gplay working. Stopped OTA, removed kingroot and installed supersu.
I rebooted into stock recovery and cleared cache. The process hung and I had to force reboot. when I went back into the stock recovery it gives failed to mount /cache.
When I try to boot into android it hangs on the fire screen.
I am going to try to rebuild the partition table. Can someone please post the output of their HD10 table?
If not I will have to sideload the firmware and reroot.
Thanks,
Turned out to be simple repair.
I did factory reset from the stock recovery and I still had root after.
Immediately stopped ota, reinstalled supersu, and the rest of my apps.
Working good now.
Related
hi,
so I've updated to 0E3 using Kies. The phone booted fine. Then I flashed CF Auto Root using Odin, phone booted fine, root was working. Then I wanted to flash TWRP, but accidently flashed CF Auto Root again. This time phone didn't boot, upoen booting it says unfortunately ... has closed, and so for all the apps, clock, touchwiz ui etc etc etc How can I get back into the phone? I've tried clearing dalvik and cache, it boots, says optimizing apps, but then same happens, unfortunately closed for all the apps
Reflash the rom you are on.
Otherwise factory reset.
So I completely wiped my Nexus 4 yesterday (everything but internal storage) and clean-installed the 12/29 CM13 nightly + nano Gapps. Everything was working great, installed a bunch of apps from Google Play, etc.
Then this morning I booted to recovery and installed SuperSU 2.46 via recovery zip flash (not via the app), which appeared to flash successfully/with no errors (plus I now see a supersu directory at the root level of my device).
I then rebooted and got stuck at the boot animation. Went back to recovery, wiped dalvik cache and regular cache, rebooted, and I'm still stuck at the boot animation. Reflashed the zip and then wipes dalvik/cache, still stuck.
Any ideas on (a) how to fix without rewiping-reflashing, and (b) how to get root on CM13? Thanks!
EDIT: Forgot to mention my bootloader is unlocked and I have TWRP recovery.
EDIT2: Appears to be solved. I simply deleted the "/supersu" directory in the TWRP file manager and it now boots fine. Unsure if it screwed up hidden stuff, but I didn't have to wipe my system partition, which is a win in my book.
You don't need SuperSU on CM since it has root acces integrated, you just need to enable it under developer options. Format system, cache/dalvik and reflash cm13 and gapps.
Well ****. Looks like I needed to use the newer beta versions of "systemless" SuperSU, like 2.56 or 2.61 for Android 6/CM13.
I wasn't aware that installing 2.46 would cause me to get stuck at bootup, though! That sucks. Still looking for a solution.
Ah I wasn't aware of that. Thanks!
I deleted the /supersu directory, reflashed the 12/29 nightly, wiped caches, and the phone got past the boot animation and booted normally. I'll reboot a few times and see if things are OK.
Saved me from having to format system yet again and redo everything.
Install 2.56b Beta thats working coz it uses systemless ROOT
Do not install 2.56b , because you won't be able to install 2.60+ supersu after that without reflashing system. Install 2.65 beta. It's stable and tested on cm13. I use it myself.
Thank you so much for this - I flashed 2.46 on cm13 on my motog3. I thought I'd lose all my data since I have device encryption and an external sd formatted as internal storage (which is unsupported in twrp for the moto3g, so it isn't accessible for backing up).
I just reflashed the rom and cleared cache and it's back to normal, encryption was fine, all my data is here, and the external sd card functions as well. Saved my ass.
I tried this and it didn't work. I installed supersu while on CM13 and it got stuck at the boot animation of CM. I deleted the /supersu directory reflashed the newest nighlty rom and wiped caches but still stuck at boot animation. I'm on TWRP btw
Doesn't cm13 have an option to enable root under developer settings?
I've got a rooted Moto X Pure and this morning I got a System Update request. I said "sure." (First mistake) It downloaded the update then rebooted into recovery. Unfortunately, it's TWRP not the original System recovery. The update can't automatically run in TWRP and I don't know where it was downloaded to. Also, If I tell TWRP to just reboot, after the system comes up, it automatically downloads the update and reboots into recovery again. So that's where I'm stuck, a loop of download, recovery, download, recovery...
HELP!
frasej said:
I've got a rooted Moto X Pure and this morning I got a System Update request. I said "sure." (First mistake) It downloaded the update then rebooted into recovery. Unfortunately, it's TWRP not the original System recovery. The update can't automatically run in TWRP and I don't know where it was downloaded to. Also, If I tell TWRP to just reboot, after the system comes up, it automatically downloads the update and reboots into recovery again. So that's where I'm stuck, a loop of download, recovery, download, recovery...
HELP!
Click to expand...
Click to collapse
Usually if you get the Blur*.zip file out of cache it is enough to break the bootloop.
In TWRP
Wipe -> Advanced Wipe -> Cache
Or in bootloader:
Code:
fastboot erase cache
Enter TWRP, do a cache wipe, then you should be OK.
I made the same mistake (careless phone pick-up after days of dodging the update). A cache clear worked just fine for me.
TWRP 3.1.0-0 Touch
Lineage 14.1 Nightly
Mistakenly tried to do an OTA update and am now stuck with it booting only to TWRP
I have tried
Code:
Fastboot Continue
. I also then tried to do a complete restore from a previous TWRP backup.
Help?
user_null said:
TWRP 3.1.0-0 Touch
Lineage 14.1 Nightly
Mistakenly tried to do an OTA update and am now stuck with it booting only to TWRP
I have tried . I also then tried to do a complete restore from a previous TWRP backup.
Help?
Click to expand...
Click to collapse
If you can get into twrp, see if system is mounted. If it isn't, it probably won't keep the option when you try and check it. So do a restore on the system only, then woke cache, go to Mount system and it should stick. Reboot and it should get you back up and running.
I also took the update.. this method of mounting system, etc. isn't working. *edit* Battery pull, volume down/power button/ factory reset fixed the bootloop.
Hey,
I didn't updated my phone for quite some time and today I had some free time and I decided to update it to the latest version. I performed the first OTA update, and the process wen't really smooth. The phone booted after a few minutes, however it told me there's another system updated so I installed it as well.
However, after installing the second OTA update, my phone never booted again. it stucks in bootloop for a few minutes and then just boots to recovery.
I don't really know what to do, and although most of my data is backed up I really want to avoid wiping all the data.
The phone was never rooted and has stock recovery. How can I make it boot without wiping all the data? I did try to wipe cache already and it didn't help.
I see that there is a method called 'adb sideload' but I want to be sure it doesn't wipe data and to know which zip I should give it... Thanks!