Hi there,
Yesterday I rooted my oneplus 5T and installed TWRP 3.2.1 & masgisk. Then, I´ve installed Pixel experience AOSP which seemed like fairly stable from the description. Everything went fine, the OS started I started configuring it then after setting the password I got the OS having always the setting app to crash. So, I thought well, I can just go to recovery and try once again factory reset. Otherwise, I can mount the recovery and install another ROM. I went to recovery and to my surprise it was asking for a password and mine didn´t work. I tried the factory reset and still the encryption stayed. I found that this version has a decryption problem and all my files were encrypted and not accessible, that was fine, since I had everything backed up. So, I have installed the new version of TWRP which seems to fix this issue after loosing all encrypted file. I have formated the data, system, dalvic and cache and installed once again pixel exerience but the OS keeps on bootloop. Have anybody seen something like this? How should I fix it? My best guess was to reinstall stock OS via adb, but in the past I've rooted a couple of devices and I've never seen something like this.
Thanks in advance
Related
Team Vanir Jellybean v2-7, Galaxy Nexus Verizon
Last week i was having issues with the phone not booting, or just locking up not responding etc. A wipe seemed to help, and wit work for a while. I'd get my phone setup to where I wanted it again, and then the issues would come back.
I found a post that said it was possible EXT4 formatting issues because of a bad poweroff. So I downloaded all the stock 4.04 images, fastboot erased system boot recovery. Flashed the latest radios, stock system boot userdata and clockwork recovery 5.5.0.4. Booted seemed to be fine.
Rebooted into Clockwork and installed Vanir v7, ran fine for a few days. I thought the issue was gone. Until this morning when I got a text message and went to unlock the phone and it was locked up. I pulled the battery and that is when everything got extremely bad
Would not boot past the boot animation. I tried the following
I reinstalled the ROM,
i treid to wipe data,
wiped data and reinstalled the ROM.
although I was able to make a nandroid backup before I tried all of this
Then as a last resort I went into the mounts and storage and FORMATTED /system /data and /cache in CWM. Reinstalled the ROM and it actually booted.
What greeted me there is the last thing I'd EVER expect to see. I don't know how, what or why but all my data was there... every app text missed call... all of it.. even tho I had wiped AND formatted several times and did NOT restore my backup. EDIT: Even more oddness... My user apps didn't get wiped, they are all still there, but they are all acting like I had cleared their data through the applications menu....
I still don't know if this is because of a NAND issue that formatting fixed both times (flashing stock and using format in CWM) or if it will ever come back. Has any1 else had any issues of this sort? I really don't think this is a ROM issue.
you're probably causing more damage by flashing this, wiping this and that. best option is to leave it stock for now by flashing the factory image again. if it is a NAND issue then it would have stopped booting when the issue occured. but if it is still causing problems then send it back for a replacement.
Hello,
I have recently flashed the Marshmallow update to my phone coming from WW-2.20.40.194. It was encrypted and used a PIN on both the boot and the lock screen. With Lollipop, I can decrypt my phone in TWRP by entering my lock screen PIN. However, neither TWRP 3.0.2.0 nor a TWRP repack (found at: https://drive.google.com/drive/folders/0Byp0425xydUaYzk1anRCak0zZXc) on Marshmallow are able to decrypt the phone, saying the password is invalid. I have tried the lock screen PIN, "default_password", as well as using an app called "SnooperStopper" to change my encryption password to something other than my lock screen PIN, with no luck. Is anyone else experiencing this or have a fix?
If i recall you must unencrypt before any flash. Your encryption key is now lost along with all your data. Sorry.
Sent from my ASUS_Z00AD using XDA Premium HD app
Maybe you'll need to downgrade to L, decrypt the phone, upgrade to M again and encrypt it a second time.
After uploading the M update, Asus also uploaded a rom to downgrade from M to L, so anyone can perform a downgrade just the same way they did the upgrade.
Thanks for the replies! I haven't lost any data, since I backed everything up manually beforehand. However, even if I didn't backup the data, I can still unlock the phone itself (get past the lock screen and to all my files), just not through TWRP's lock screen. I've tried encrypting before and after upgrading to Marshmallow, with the same results.
UPDATE:
Just tried again with TWRP (tethered and untethered) on a clean install, same results. Steps:
Used fastboot to completely erase phone (data, cache, dalvik, system, etc).
Flashed stock recovery for Lollipop (WW-2.20.40.194).
ADB sideloaded WW-2.20.40.194 in stock recovery.
Wiped data and cache again in stock recovery.
ADB sideloaded Marshmallow (WW-4.21.40.134).
Rebooted to system, logged into Google account, set up system, etc.
While setting up system, chose to lock device with PIN.
After setup, encrypted the phone.
Rebooted to bootloader.
Fastboot boot TWRP.
Tried to enter PIN, says invalid. Tried to enter "default_password", says invalid.
Fastboot flash TWRP, same results.
Hi yes, ive had the exact same problem running a nightly build of CM13 / Android 6.0.1. It just tells me the password is wrong. TWRP 3.0.2.0
Personally I think something changed in recent Android builds and TWRP just hasnt figured out that its broken yet. TWRP 3.0.2.0 is almost 6 months old now ...
I need to find a way to update my roms also so this is a problem.
I am glad to hear it is not just me having this issue. I believe this as well, though TWRP 3.0.2.0 worked just fine on an older version of XOSP (CM13-based, I think from a build around December 2015). Something must have changed since then.
I have discovered the problem. You can read all about it here.
http://forum.xda-developers.com/gal...wrp-mount-encrypted-partition-recent-t3468989
tl;dr
Snapdragon 800+ CPU phones (any maybe others) have HW_Crypro (hardware crypto chip) and Android 6 + enables this. Which requires recompiled TWRP with support for HW_Crypto
Doesn't the last TWRP 3.2.3 solve this issue
https://dl.twrp.me/Z00A/
Or have you find a working TWRP build that can decrypt?
So I installed the beta and decided to go back to 7.1.2.
I did a normal wipe in TWRP then reinstalled SAOSP.
The first problem I noticed was that the phone was slow to turn the screen on after pressing the power button or the fingerprint scanner.
The second problem was that the proximity sensor wasn't working in phone calls. I then checked a few others sensors and noticed that the rotation also want working.
I downloaded a sensor checking app and it showed that the proximity sensor had a value of 5 but it didn't change when covering the sensor.
First thought was a bad flash, so I re-wiped and installed a Nand backup that I knew was good. Same thing happened, so I tried PN. That didn't work.
Downloaded stock zip, backed up personal data, then did a complete wipe with the zip, internal data included. The problems stayed even on stock.
I have since read through whatever threads I could. This seems to be a random issue people have had in the past. Yet is particularly prevalent after the o beta.
Most people have suggested to just re-flash stock but that hasn't worked. The only suggestion I have read otherwise is to also lock and then unlock the bootloader in the process as well.
Who else has this problem and has anyone found a fix yet?
Ok, someone posted in another thread (PN) that the locking and unlocking the bootloader worked for them.
If you have the issue try it out.
Just remember to copy all your internal data to your PC or other storage to save it.
https://forum.xda-developers.com/showpost.php?p=72397601&postcount=10078
Link to solution
To fix this, I flashed O DP2 factory image again and then stock 7.1.2 factory image. Now everything's working and I'm rocking Dirty Unicorns 7.1.2
neth15 said:
To fix this, I flashed O DP2 factory image again and then stock 7.1.2 factory image. Now everything's working and I'm rocking Dirty Unicorns 7.1.2
Click to expand...
Click to collapse
I tried it this way but after flashing back to 7.1.2 stock, I now get a crash of com.android.phone immediately after booting, followed by a reboot.
Tried clearing cache but didn't help. Anyone know what to try to fix the crash?
UPDATE: Wiped data and now it's fine.
I tried to flash my Wileyfox Swift 1 to Lineage today, from its Android 7.0 rom.
I downloaded twrp-3.1.1-crackling.img and lineage-14.1-20170703-nightly-crackling-signed.zip.
I then followed the instructions on the Lineage OS site for a Wileyfox Swift to the letter to get the Lineage rom flashed (with the one exception being I also "wiped" Internal Storage, along with Cache, System and Data partitions). I didn't try to install, or want to install, the Google Apps.
Everything worked exactly as expected, right down to the absolute final step in the guide. When I chose to Reboot, then System, I just found myself back in the bootloader. No matter what I do, I just keep booting back up to this. I still have full access to recovery mode, but I just can't load an OS or get past the bootloader screen when I restart.
I have an old Cyanogen mod I have been able to revert to in the mean time, but I'm struggling to understand what I did wrong here. Can anyone provide any help/suggestions?
I tried again this afternoon and everything appears to have worked. I've loaded Lineage OS successfully and everything is working well. I'm still not sure what happened the first time, but all is good now.
I had the same issue. After installing an old CM13 release (with TWRP), turning everything off and then start from scratch with LOS 14.1, everything worked. It seems that CM13 does have a side effect that is needed for LOS 14.1.
Good afternoon everyone.
I have a huge problem. When I got my OP one back in 2014 I flashed it, installed CWM and CM and later switched to LineageOS. Everything worked fine until today. For some reason, after I installed lineage-18.1-20210415-nightly-bacon-signed.zip, my phone is now booting but after a while, while still booting it shuts itself down and restarts into recovery mode!? Does anyone know how to fix this? Your help is highly appreciated. Thank you and stay safe.
EDIT: So far I wiped user data and dalvik cache but nothing seems to work. Is there anyway to fix this without loosing all data/apps on my phone?
AnotherStupidUser said:
Good afternoon everyone.
I have a huge problem. When I got my OP one back in 2014 I flashed it, installed CWM and CM and later switched to LineageOS. Everything worked fine until today. For some reason, after I installed lineage-18.1-20210415-nightly-bacon-signed.zip, my phone is now booting but after a while, while still booting it shuts itself down and restarts into recovery mode!? Does anyone know how to fix this? Your help is highly appreciated. Thank you and stay safe.
EDIT: So far I wiped user data and dalvik cache but nothing seems to work. Is there anyway to fix this without loosing all data/apps on my phone?
Click to expand...
Click to collapse
You already lost apps by wiping data, but you still have your photos.
If you had GApps installed before android version upgrade, you now need to flash android 11 GApps. Wiki.lineageos.org tells you what and how.
Thank you for your help. Surprisingly for some reason I found a work around as the unofficial GApps didn't work as well. I wiped data again, so the apps were gone (it took me 3 hours to restore that), but all files were still there and I flashed back to 17.1 with GApps and it worked. Phone is working same way as before. Guess I will wait a LOOOOOOOONG time now until I will try 18.1 again. But again thank you