i dirtyflashed oos 5.0.1 and it wouldnt decrypt so i wiped and now i cant install a rom...? ive tried bluspark twrp and stock recovery to no avail
You have to wipe everything music, photos etc
Related
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.
Hey, so I can't decrypt my device anymore. Not in Android itself, and not in the recovery. I've tried sideloading no_verity.zip and formatting the system via fastboot, so far nothing helped. When I try to flash the stock rom via sideload, it says it's not readable. I don't know if thats because I didn't decrypt the device before flashing or because the zip is faulty, but I've tried 3 diffrent roms, including one that has worked before.
Is there anything I can do to get my phone working again?
Device: Onepluss 5 6GB
Rom: Omnirom
Install latest codeworkx twrp or blue spark twrp, skip password menu, format data (not wipe), reboot recovery, now wipe everything, then flash what you want
more_than_hater said:
Install latest codeworkx twrp or blue spark twrp, skip password menu, format data (not wipe), reboot recovery, now wipe everything, then flash what you want
Click to expand...
Click to collapse
Thank you! That worked. I figuered formatting data and wiping data would work quite the same, but thanks for proofing me wrong ^^
Ok, so I am not new to flashing rom but for some reason I am having huge issues trying to install clean stock OOS 5.1.4 rom. Just want to double check I am not doing anything stupid since I mainly been flashing custom roms (xXx rom mainly).
So I simply wipe dalvik/ART cache, cache, system and data (want to start off completely clan) then flashed the OnePlus5Oxygen_23_OTA_037_all_1807181258_7b4b6.zip file in TWRP.
I am currently on the latest blue TWRP and after flashing, it will try to boot but reboots back into TWRP. I have tried the zip file from a number of sources and they all do the same. Am I missing something here?
UPDATE: I did do something stupid after all. I forgot that my Oneplus was decrypted. So all I had to do was go into TWRP and go to Wipe and format data to re-encrypt it.
Z-Blade said:
Ok, so I am not new to flashing rom but for some reason I am having huge issues trying to install clean stock OOS 5.1.4 rom. Just want to double check I am not doing anything stupid since I mainly been flashing custom roms (xXx rom mainly).
So I simply wipe dalvik/ART cache, cache, system and data (want to start off completely clan) then flashed the OnePlus5Oxygen_23_OTA_037_all_1807181258_7b4b6.zip file in TWRP.
I am currently on the latest blue TWRP and after flashing, it will try to boot but reboots back into TWRP. I have tried the zip file from a number of sources and they all do the same. Am I missing something here?
Click to expand...
Click to collapse
When starting fresh, wiping of internal storage should be considered. I recommended 2 guides here https://forum.xda-developers.com/on...nos-beta-1-android-oreo-t3710003/post77205633
Hello everybody
So this is weird asf..
So I got Mi 9T with MIUI 10.3.7 EEA stock rom. TWRP and Magisk flashed. I wanted to update MIUI to the latest 10.3.12 and I found a method online to update via TWRP by flashing the new MIUI stock rom then flashing a zip "Lazyflasher-no-verity-opt-encrypt.zip".
I backed up (system, data, boot) and then wiped (sys, data, catch, dal/art), then flashed the newer MIUI rom, then Lazyflasher zip. But I got an error installing Lazyflasher. So I wiped and restored my backup and the device booted into system. But then I discovered that the system is acting crazy. Fingerprint, wifi, all sensors aren't working.. etc.
I tried re-restoring my back ups, and tried wiping Dalvil/Art cache, Data and, Cache (TWRP factory rest) but nothing changed.
I'm considering flashing stock room but I don't want to lose bootloader unlocking and wait again.
Any suggestions?
Thanks in advance