Database Users

Android N Preview Build to Cyanogen Mod 13

Hey guys,
Today I tried to go from the Android N developer preview back to Cyanogen Mod 13 (which I had been running before). I tried installing through TWRP 3.0.0.0 but for some reason whenever I install CM I get stuck in a boot loop at the screen that just says Google but multiple times I've been able to flash back to the Android N Preview. I've flashed my phone many times before and I tried a bunch of different stuff (formatting the userdata partition before flashing to decrypt the phone, wiping and not wiping the davlik cache before and after flashing, multiple snapshots of cm13 etc.) but I can't seem to break that bootloop. I ended up going to Android N after I broke something on CM so I used the opportunity to try out Nougat before I flashed back to CM so I didn't have any back ups (I thought I did but i only backed up apps and app data, not a whole solid backup from TWRP or something). Right now I'm entirely stable on Android N but missing XPosed a little so any help would be appreciated.
Alex

touchmywillis said:
Hey guys,
Today I tried to go from the Android N developer preview back to Cyanogen Mod 13 (which I had been running before). I tried installing through TWRP 3.0.0.0 but for some reason whenever I install CM I get stuck in a boot loop at the screen that just says Google but multiple times I've been able to flash back to the Android N Preview. I've flashed my phone many times before and I tried a bunch of different stuff (formatting the userdata partition before flashing to decrypt the phone, wiping and not wiping the davlik cache before and after flashing, multiple snapshots of cm13 etc.) but I can't seem to break that bootloop. I ended up going to Android N after I broke something on CM so I used the opportunity to try out Nougat before I flashed back to CM so I didn't have any back ups (I thought I did but i only backed up apps and app data, not a whole solid backup from TWRP or something). Right now I'm entirely stable on Android N but missing XPosed a little so any help would be appreciated.
Alex
Click to expand...
Click to collapse
Are you flashing the corresponding vendor image? If you do not flash the correct vendor image you will boot loop. I have gone from N to Marshmallow and reverse without issue.

santque said:
Are you flashing the corresponding vendor image? If you do not flash the correct vendor image you will boot loop. I have gone from N to Marshmallow and reverse without issue.
Click to expand...
Click to collapse
No I wasn't, I couldn't very easily find much information on how to flash the vendor image so right now I'm reverting back to Marshmallow via the OTA opt out, that should do the trick right? If not, I know where to find the vendor image but how do I flash it? just fastboot flash vendor.img or what?
Thanks for your help!

touchmywillis said:
No I wasn't, I couldn't very easily find much information on how to flash the vendor image so right now I'm reverting back to Marshmallow via the OTA opt out, that should do the trick right? If not, I know where to find the vendor image but how do I flash it? just fastboot flash vendor.img or what?
Thanks for your help!
Click to expand...
Click to collapse
There are two ways you can flash a vendor image. Either through TWRP's 'Install' menu or using the 'fastboot flash vendor vendor.img' command.
You can grab hold of the vendor image corresponding to the build number from here: https://www.androidfilehost.com/?w=files&flid=49333
Thanks to BeansTown106 for the vendor uploads.

Encryption Unsuccessful - Can we get data back?

Hello Guys
So i was trying to update my rooted Decrypted Nexus 6P from 7.0 to Developer preview 7.1 .
I followed the instructions to flash the OTA zip and then root it with SuperSu (http://forum.xda-developers.com/nexus-6p/general/available-android-7-1-developer-preview-t3483739).
I then flashed Franco's latest kernel as I usually end up doing that. The phone booted fine, but of course the camera had some problems as reported here (http://forum.xda-developers.com/showpost.php?p=69226309&postcount=373) which meant that the Franco kernel was at 7.0 and I needed 7.1 kernel.
So stupidly enough I just extracted the boot.img from the 7.1. OTA zip and flashed it through flashify app to revert to stock kernel for 7.1 and just re-started my phone.
But since that boot img was not patched it forced encryption on the phone which I did not realize until I found the phone was sitting at the boot animation for a long time and I just force re-started it.
Wrong decision . Now I have a phone that boots up to a screen which says Encryption Unsuccessful and has a button which asks me to wipe all the data.
Booting into TWRP asks me password for decrypting the data partition which I assume would be my PIN and supply it, but it sits on message saying 'Decrypting data' and just sits there endlessly. I have tried this as well (http://forum.xda-developers.com/showpost.php?p=66163153&postcount=826) i.e. trying the 3.0.0.1 twrp but that one does not like the PIN that I supply.
I followed this (http://forum.xda-developers.com/verizon-htc-one-m8/help/decryption-unsuccessful-currently-t3074855) to extract the whole data partition from my phone and essentially I have this 58 GB file which i tried to mount in Linux but unfortunately there is nothing that i see in that partition.
Is there anyone who has encountered this and has successfully retrieved their data??? I know it was stupid of me that I didn't take a backup of my internal storage plus the nandroid backup I had is on the phone .
Any help is much appreciated.
Thanks

Oneplus2 Stuck on Animation

I have a US Oneplus2 that is stuck on the animation when it boots. I can get into TWRP and Fastboot, latest TWRP works and can also use an older version that I had.
I made a TWRP backup that I pulled off onto another computer. I then installed OOS 3.5.1 (I think) to do some testing. Once I was done testing, I decided I wanted the latest lineage as my backup was a 6 month old version of the latest at that time. I used TWRP to wipe the data, cache, and system to then install the latest Lineage 14.1 11/24/17 and gapps mini and micro (tested both). It gets to the lineage boot animation and the ball goes back and forth forever. I have left it over night and it's still going. I have rebooted the device, installed lineage several times, moved to 12/1/17 today with the same results.
After messing with it for hours and days, I decided to just put the TWRP backup back on the phone and then update from there. Well... my custom animation is load but the animation is also going forever.
Looking for some help on what might be wrong with the phone, thanks.

Make sure everything is formatted as ext4 and update firmware to 3.6.1 just to rule it out.
I would use the latest twrp.
I go to format tick all the boxes and clear everything then go to reboot > recovery. Once back in twrp copy the ROM and gapps across from pc install ROM and gapps together, wipe cache and dalvik reboot.

I'm in the process of doing that now.
The TWRP that I'm using is 3.1.1-0 which looks to be the latest. I am working with OOS 3.5.8 but will look at downloading 3.6.1. I am working to get Lineage 14.1 on there once everything is stable.
I ran into another weird is when using the qualcomm recovery tool:
My method is to enable ADB, enable OEM Unlock, enable Advanced Reboot.
Reboot into fastboot
Fastboot oem unlock: is successful
Fastboot reboot
I then go through renabling ADB and Advanced Reboot, OEM Unlock is still enabled.
I then reboot into fastboot
Fastboot flash recovery twrp-3.1.1-0-oneplus2.img
This completes successfully and then I fastboot reboot.
I have tried several times to get into TWRP but I keep getting the stock recovery.
I have tried to reflash recovery but nothing ever changes.
Is there possibly something wrong with the OEM unlock that says it was successful?
How do I go about troubleshooting this?

Ok, I fixed that and install OOS 3.6.1 and then was able to install TWRP 3.1.1-0.
I then wanted to install Lineage 14.1:
I then formatted Cache, System, Data, Dalvik... everything but internal. Should I wipe internal as well?
I copied over linage 14.1 and open_gapps for the same build micro.
I now am back to getting the Lineage Boot animation.
Thanks for helping since I'm trying to get Lineage to boot.

cyrus104 said:
Ok, I fixed that and install OOS 3.6.1 and then was able to install TWRP 3.1.1-0.
I then wanted to install Lineage 14.1:
I then formatted Cache, System, Data, Dalvik... everything but internal. Should I wipe internal as well?
I copied over linage 14.1 and open_gapps for the same build micro.
I now am back to getting the Lineage Boot animation.
Thanks for helping since I'm trying to get Lineage to boot.
Click to expand...
Click to collapse
Internal doesn't really matter to be honest, did you check they data and system are formatted as ext4.
It is in twrp advanced wipe options.
Did it ever boot ?

I did doubt check the data and system are formatted as ext4.
I let it sit for 3-4 hours and didn't see any progress.

Try a different rom. There are a lot of lineage based roms around.

I tried that and am getting the same results. Even if I flash a full TWRP backup from a time when I had it known to be working it happens.

I've tested this with 3 different roms now. My latest attempt has been to update TWRP to 3.2.1 and then install lineage 14.1 20171208. I also tested with Paranoid and Carbon because they were near the top of my list not because I know anything about them.
The phone just never gets past the boot animation. If I reboot to recovery is there a log I can pull to see what the issue is?
Thanks

Would like to see if anyone has any thoughts. If I run OOS I can use the phone but as of right now I can't use any other rom.
Is there any advanced fastboot or wipes that can be done to get it to boot. Is there any type of debugging that will show me what's happening when it tries to boot.

Just trying to bump this, I really need a way to debug this problem. Besides running OOS, I have a feeling this device is bricked and the mega unbrick guide doesn't work.
Also looks like if I try to put Kali on top of the base 3.5.8, the phone goes into the animation loop. So any change after OOS on the device puts it into an animation loop.
Is there a way the system or boot locked? Even thought I can TWRP anything onto the phone without errors.

Hey!
I've got the same issue it seems, phone just sticks to boot animation when flashing any other ROM than OOS 3.6.1.
Any update?
EDIT :
problem was with the persist.img
Flashed a different firm file and it was resolved

cyrus104 said:
I have a US Oneplus2 that is stuck on the animation when it boots. I can get into TWRP and Fastboot, latest TWRP works and can also use an older version that I had.
I made a TWRP backup that I pulled off onto another computer. I then installed OOS 3.5.1 (I think) to do some testing. Once I was done testing, I decided I wanted the latest lineage as my backup was a 6 month old version of the latest at that time. I used TWRP to wipe the data, cache, and system to then install the latest Lineage 14.1 11/24/17 and gapps mini and micro (tested both). It gets to the lineage boot animation and the ball goes back and forth forever. I have left it over night and it's still going. I have rebooted the device, installed lineage several times, moved to 12/1/17 today with the same results.
After messing with it for hours and days, I decided to just put the TWRP backup back on the phone and then update from there. Well... my custom animation is load but the animation is also going forever.
Looking for some help on what might be wrong with the phone, thanks.
Click to expand...
Click to collapse
OOS does not refuse to boot if a mountable partition is corrupt. This is not the case with lineage. If a mountable partition is corrupt and the corresponding fstab entry does not allow lineage to format and somehow mount it then init never proceeds
Try flashing this file: https://glassrom.botstack.host/firmware/oos-3.6.1-firmware-signed.zip and try again
Note that this file reboots the device after the flash is done so don't use twrp queue to flash this file. Flash this file last
---------- Post added at 17:45 ---------- Previous post was at 17:34 ----------
Alternatively this is a method I don't recommend to beginners because they accidentally give twrp logs to devs without realising it
You can get logs by making the forcing the device to "crash" through the power button
Here's how it's done: you boot the non-booting ROM and wait for about a minute. Then press power + volume down while it's on the bootanimation. You have to hold it until you see the oneplus logo and boot to twrp
TWRP's kernel will recover the last booted kernel's log from ram and place it in /sys/fs/pstore
First you have to open the log yourself to check if it's valid. The file is console-ramoops-0. All other log files in that location are invalid for your specific issue
Now for an ordinary user this is hard. They can't tell if the log is a recovery log or a ROM log. Since we're dealing with official lineageos we assume selinux would be enforcing
You want to search for this string "permissive=1". On Linux just do cat console-ramoops-0 | grep "audit" (quotes are part of the command)
If you're on windows then you can download Linux and get the logs. Stop bothering me
If you see the string "permissive=1" in the log you have accidentally fetched a recovery log
Go back and boot again and wait for about a minute if selinux is permissive
The string should read
"permissive=0"
That means selinux is enforcing and this is indeed a ROM log
Send this log here

Hello,
Was this problem ever solved? I am experiencing the very same thing with every single ROM i have tried so far. TWRP is installed, I can install all ROMS but when I try to boot the phone, it just won't get passed the booting animation.
Thank you

OP6T brick, how to recover without data loss?

Hey folks, I somehow bricked my OP6T and I hope for help to recover without data loss.
OP6T
OxygenOS (stable, not the latest though, I guess it's 10.3.2)
TWRP Recovery (twrp-3.3.1-31-fajita-installer-mauronofrio.zip)
Rooted with Magisk (not the newest version, the one before)
How this happened...
I wanted to update Magisk from within the app via the recommended way. But the first click on the button did not start the installation, so I clicked again, few seconds later the first installation dialog appeared, installation ended with a positive result. Then the second installation dialog appeared and ended with an error.
I rebooted and it ended up with the bootloader screen. No recovery, no system booting up. The TWRP 3.3.1-31 did not start using this command:
Code:
sudo ./fastboot boot twrp-3.3.1-31-fajita-Q-mauronofrio.img
But TWRP finally started using the newer twrp-3.3.1-32-fajita-installer-mauronofrio.zip. However, neither slot a nor slot b will boot into system.
Booting system from slot a leads to bootloader, booting system from slot b ends up in a boot loop. Also, using the file manager within TWRP shows me encrypted directories and files. Now I am lost.
Is there a way to recover / unbrick without losing all the data?

Try restoring the stock boot image of whatever ROM you're using.
or You can use magisk patched img, instructions in magisk thread.
I read somewhere that you should not manually change the boot slots. The system decides when it must change the slot.

devilrulz4ever said:
Try restoring the stock boot image of whatever ROM you're using.
or You can use magisk patched img, instructions in magisk thread.
I read somewhere that you should not manually change the boot slots. The system decides when it must change the slot.
Click to expand...
Click to collapse
Restoring means losing data. This is what I wanted to avoid. I use stock OxygenOS, as mentioned above.
Since my system does not boot up, the system won't decide. Actually I hoped that things are not that bad and if I change the slot I maybe could have been lucky and system is booting up from that slot, but obviously nothing worked out yet.

benkxda said:
Restoring means losing data. This is what I wanted to avoid. I use stock OxygenOS, as mentioned above.
Since my system does not boot up, the system won't decide. Actually I hoped that things are not that bad and if I change the slot I maybe could have been lucky and system is booting up from that slot, but obviously nothing worked out yet.
Click to expand...
Click to collapse
Since you'll only replace the boot image your data will be safe. Boot and data are stored in different partitions.
You can use fastboot to do that or TWRP.
You will have to extract the boot image of OxygenOS before you can flash it. You'll need payload dumper to do that.
I suggest you google how to use it and all; check the guides section as well. If you need any more assistance then ask here.
Since the boot partition was corrupted it couldn't change the boot slot.

I think he means flash the same stock image you are currently running. This can fix many system issues with no data loss

devilrulz4ever said:
Since you'll only replace the boot image your data will be safe. Boot and data are stored in different partitions.
You can use fastboot to do that or TWRP.
You will have to extract the boot image of OxygenOS before you can flash it. You'll need payload dumper to do that.
I suggest you google how to use it and all; check the guides section as well. If you need any more assistance then ask here.
Since the boot partition was corrupted it couldn't change the boot slot.
Click to expand...
Click to collapse
bladestonez said:
I think he means flash the same stock image you are currently running. This can fix many system issues with no data loss
Click to expand...
Click to collapse
Thanks guys. For some reasons (???) the last attempt with TWRP (twrp-3.3.1-32-fajita-Q-mauronofrio.img) lead to access to all files via TWRP. So atm I create a complete backup of /sdcard pulling everything via adb, which kind of takes a lot of time due to USB 2. After that I push latest OOS ROM, TWRP and Magisk and give it a try. At least I get even not clouded data back.
Will keep you updated... please stay tuned. :fingers-crossed:

benkxda said:
Thanks guys. For some reasons (???) the last attempt with TWRP (twrp-3.3.1-32-fajita-Q-mauronofrio.img) lead to access to all files via TWRP. So atm I create a complete backup of /sdcard pulling everything via adb, which kind of takes a lot of time due to USB 2. After that I push latest OOS ROM, TWRP and Magisk and give it a try. At least I get even not clouded data back.
Will keep you updated... please stay tuned. :fingers-crossed:
Click to expand...
Click to collapse
Backup completed
pushed OOS ROM
TWRP and Magisk
dirty flashed ROM
rebooted to recovery
flashed Magisk
rebooted to system
That's basically it and everything works again. The most important step was, that for some reason TWRP let me access the decrypted file system. And then ADB is very helpful, brought my device back to live.
Thread will be closed shortly.

Thread closed at OP request

TWRP Installation issue on MIUI 12

I'm on MIUI 12, I'm not able to install TWRP recovery properly.. internal storage is encrypted.. not able to flash anything. anyone has a solution ? thanks in advance !

Harshadd30 said:
I'm on MIUI 12, I'm not able to install TWRP recovery properly.. internal storage is encrypted.. not able to flash anything. anyone has a solution ? thanks in advance !
Click to expand...
Click to collapse
When, entering TWRP, it asks you for PIN/password.
You have to enter your pin/password you have defined in Android for unlocking the screen.
TWRP must then confirm that it successfully decrypted for user 0 (for user 999 it would fail, do not wory about)
This is really nothing new, but you must not use an outdated TWRP that does not ask or does not support it properly
If having problems, reboot to Android and reset your pin/password.
Some TWRP versions may not support properly if you use pattern in Android - hence better switch to pin.
However, if you cannot make it with pin, reboot again to Android, redefine to pattern and try

zgfg said:
When, entering TWRP, it asks you for PIN/password.
You have to enter your pin/password you have defined in Android for unlocking the screen.
TWRP must then confirm that it successfully decrypted for user 0 (for user 999 it would fail, do not wory about)
This is really nothing new, but you must not use an outdated TWRP that does not ask or does not support it properly
If having problems, reboot to Android and reset your pin/password.
Some TWRP versions may not support properly if you use pattern in Android - hence better switch to pin.
However, if you cannot make it with pin, reboot again to Android, redefine to pattern and try
Click to expand...
Click to collapse
i have tried, i swiped to allow modification but it does not asked for password, goes straight in recovery mode & i can not access my files from there, i also tried removing password completely to unlock phone but still got the same issue.. i have heard that files are encrypted on android 11, so i posted this question..
thank you

Harshadd30 said:
i have tried, i swiped to allow modification but it does not asked for password, goes straight in recovery mode & i can not access my files from there, i also tried removing password completely to unlock phone but still got the same issue.. i have heard that files are encrypted on android 11, so i posted this question..
thank you
Click to expand...
Click to collapse
Make sure you use the latest official TWRP for davinci
Which "notifications" - it's about Passwords and Security in Android. You can try by removing Android unlock pin/pass, reboot to Android and set it again and then try with TWRP.
Again, make sure you use up-to-date TWRP, best the official
twrp-3.5.2_9-0-davinci.img (if you were not familiar with and TWRP does not ask, maybe you are on an ancient and maybe some unofficial TWRP)

HI, I updated to V12.1.4.0.RFJMIXM and tried to install the latest TWRP but booting into recovery mode TWRP is in this like read only mode and dosnt bring up the usual thing to decrypt your files. It says unmodified system partition. Keep system read only? TWRP can leave your system partition unmodified to make it easier for you to take official updates. TWRP will be unable to prevent the stock ROM from replacing TWRP and will not offer to root your device. Then it says keep read only or swipe to allow modifications. Any suggestions? Tried removing and adding security pin but didnt work
I need it to install magisk. I tried patching a recovery image with magisk which worked. But trying to boot to magisk with recovery dosnt work. I hold the keys and then when it vibrates let go but it always goes to stock recovery. Not system with magisk as it talks about.

Harshadd30 said:
i have tried, i swiped to allow modification but it does not asked for password, goes straight in recovery mode & i can not access my files from there, i also tried removing password completely to unlock phone but still got the same issue.. i have heard that files are encrypted on android 11, so i posted this question..
thank you
Click to expand...
Click to collapse
This seems like a bootloop. Did you change any roms before this happened? You might have to format (not wipe) your data partition which unfortunately will also delete all your files from the phone's internal storage.