So, my Nexus 7 is stock rooted, running TWRP, M-Kernel and data-f2fs. I flashed CM12 with MultiROM and tried to boot it, however it didn't boot, just stayed at the Google screen. I tried to boot both regular TWRP & MultiROM TWRP, & It didn't boot either. I fastboot flashed stock recovery, cwm, and stock kernel. All of them booted fine, except the stock kernel, which didnt boot cause data was f2fs. Eventually, I just tried flashed M-Kernel again in cwm with adb sideload & It didn't work. So, I manually edited the M-Kernel boot.img on my PC for data-f2fs, since the one in the zip is all-f2fs, and flashed it & TWRP with fastboot. Both Android & TWRP finally booted! However, my data partition is corrupted. Android wants a password to decrypt, and TWRP detects it as ext4. How do I fix my data partition without formatting it?
Nvm, I'll just fastboot format data.
Related
Hi guys! I need a bit of help. I was using PA 4.42 with FK r209 on my N4 with all F2FS (/system, /data, /cache). Yesterday I flashed Nexus_5_Experience_cm11_Nexus4_Release8.5 which claimed in its features that it has F2FS support. so I made a Nandroid backup with TWRP, wiped system, data, cache, dalvik cache and flashed the ROM. Installer did the job apparently fine and showed installation as successful. I then rebooted but ROM could not make it. It was stuck on decryption password screen and did not go past even by giving the password. Then I got back to TWRP Recovery mode and tried to restore my Nandroid backup but it was also stuck at PA boot animation prior to decryption password screen. Then I again went back to Recovey, wiped system, cache, data and dalvik cache again and then restored the Nandroid backup again but it stuck at PA boot animation again.
Is there any way I can restore my backup or would I need to fastboot flash a factory image to make the phone alive again? If so, would it be ok to flash factory image while having all partitions converted to F2FS? Will it do the job or add up in the issue?
Any suggestions would be appreciated please.
EDIT:
ISSUE SOLVED BY FASTBOOT FLASHING 4.4.4 FACTORY IMAGE WHICH HAD NO CLASH WITH F2FS PARTITIONS AND RE-WROTE ALL PARTITIONS TO EXT4 FORMAT.
Hi,
I was using Slimkat 4.2 with TWRP recovery. Wanted to update to the latest stable build. Did so. Now I'm stuck in a bootloop.
1) I restarted in bootloader, went to advanced wipe and wiped system, dalivik cache and cache.
2) Then I flashed the file (Slim-grouper-4.4.4.build.7.0-OFFICIAL). Sha1 check out. My device is a nexus 7 2012 (non 3g).
3) on top of that, I flashed the latest gapps normal.
Bootlooped.
1) I'm able to enter into bootloader.
2) I do not have a backup of my previous instal
3) I am unable to mount usb through the twrp mount interface.
Could somebody help me here? I seem to be making a lot of mistakes with this after successfully flashing my phones for years (just recently I got a "enter password to decrypt device" on the same nexus 7 that I got through by formating through twrp.
Should I try wiping and flashing the rom again, without the gapps? (By wiping system, dalivik cach and cache)?
Are there other methods I could use?
Help would be greatly appreciated!
Please note that I can easily get into fastboot mode. When I'm at fastbook, should I just try to return to stock? I'm not exactly sure how that would work given that I have a custom recovery and rom installed.
Should I try to use sideload adb to instal the rom/original rom for the device again?
So i downloaded TWRP 2.8.2.0 on my Nexus 7 4.3.3, i was rooted and everything. Then wiped my system in recovery.
After that i went to Advanced wipe and changed all the partitions to f2sf except internal storage, i was then going to flash my Slimkat rom, but then i couldnt access any folder! Tried a reboot but now it wont start... Can acces fastboot and so, but what do i do??
EDIT: So now i wiped them back to ext4, but when i pressed reboot twrp sais i had no OS installed? What to do?
Thanks for any help
You can still go back to the bootloader I assume so when you're on it connect your Nexus to your computer and run the Nexus Toolkit to flash Google Factory Image. Then you'll have to do the same steps as before, reflash a recovery, root and then flash the rom you want to use.
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?
Hi,
I have a rooted OP5 with 4.5.13.
I tried to install the flashable zip (from here) via TWRP without wipe, but ended up in a bootloop.
I've restored to the nandroid backup, wiped data, and tried again. This time the OP5 managed to boot only to recovery.
I've verified the md5 of the file I've used.
Do you know why this is happening? Do you know how I can upgrade to 4.5.14?
Thanks.
Did you download the full ROM or just the update?
I tried both. I didn't succeeded to install the update (as it is not intended for rooted devices).
The full rom is what caused the bootloop.
If you are doing a dirty flash you wipe cache and system. If you are doing a clean flash you wipe cache, system and data. It doesn't sound like you wiped the correct partitions when doing your flash. You also need to flash Magisk or SU after the ROM flash and before booting up or you will lose TWRP and root. If your phone is decrypted for some reason you also need to flash a no verify zip or your phone will boot loop because OOS is made for encrypted phones.