I've downloaded the latest Android Pie stock image, however it seems that once I manual boot to TWRP 3.2.3, it causes the Android system UI to keep crashing. Any guesses on what's going on or what I'm doing wrong? I am flashing with the W removed.
Sent from my Pixel 2 XL using Tapatalk
brackett5 said:
I've downloaded the latest Android Pie stock image, however it seems that once I manual boot to TWRP 3.2.3, it causes the Android system UI to keep crashing. Any guesses on what's going on or what I'm doing wrong? I am flashing with the W removed.
Click to expand...
Click to collapse
So after you fastboot the factory image, and then fastboot into twrp you get a crash???
Reflash factory image but don't install TWRP. Do you still get crashes?
sublimaze said:
Reflash factory image but don't install TWRP. Do you still get crashes?
Click to expand...
Click to collapse
I fastboot into TWRP, backup my phone, rebooted back into system ( on accident) and all the sudden my system UI was broke.
Sent from my Pixel 2 XL using Tapatalk
brackett5 said:
I fastboot into TWRP, backup my phone, rebooted back into system ( on accident) and all the sudden my system UI was broke.
Click to expand...
Click to collapse
Go back to bone stock and don't install/fastboot TWRP, and see if you still get FCs.
sublimaze said:
Go back to bone stock and don't install/fastboot TWRP, and see if you still get FCs.
Click to expand...
Click to collapse
I already have and it works fine. Sorry, I should have mentioned that. I was wondering if it was the backing up process. It's happened twice now since backing up.
Sent from my Pixel 2 XL using Tapatalk
brackett5 said:
I already have and it works fine. Sorry, I should have mentioned that. I was wondering if it was the backing up process. It's happened twice now since backing up.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
You're backing up a fresh stock install? Is that correct?
Try flashing JUST the factory image, let it boot, boot into bootloader, fastboot into TWRP 3.2.2-0.IMG (previous version of TWRP), and see if you're still crashing.
Az Biker said:
You're backing up a fresh stock install? Is that correct?
Try flashing JUST the factory image, let it boot, boot into bootloader, fastboot into TWRP 3.2.2-0.IMG (previous version of TWRP), and see if you're still crashing.
Click to expand...
Click to collapse
That's what I mean by stock, I'm sorry. I've been installing the factory image (flash-all). I'll try the 3.2.2 when I get home
Sent from my Pixel 2 XL using Tapatalk
brackett5 said:
I already have and it works fine. Sorry, I should have mentioned that. I was wondering if it was the backing up process. It's happened twice now since backing up.
Click to expand...
Click to collapse
Are you using Titanium Backup or a similar 3rd party app to restore data? If you are restoring system data, especially across different versions of Android, that is likely the culprit.
TWRP does not modify any system data except the recovery files, so it should not affect system UI. I updated from Oreo to Pie by flashing the Pie factory image, then installed TWRP & Magisk in the same recovery session, and I have yet to experience any system UI errors. I know that doesn't really help your situation, but your it appears to be limited to your phone/setup.
sublimaze said:
Are you using Titanium Backup or a similar 3rd party app to restore data? If you are restoring system data, especially across different versions of Android, that is likely the culprit.
TWRP does not modify any system data except the recovery files, so it should not affect system UI. I updated from Oreo to Pie by flashing the Pie factory image, then installed TWRP & Magisk in the same recovery session, and I have yet to experience any system UI errors. I know that doesn't really help your situation, but your it appears to be limited to your phone/setup.
Click to expand...
Click to collapse
I honestly have not idea what was going on, but I installed twrp 3.2.2, Flash Kernel3.0.3, and the Magisk posted in your post all in the same session and it worked. Im lost, but im good now.
Thank you all.
Related
So my Nexus 7 still has not received the OTA update, and like a bunch of other, I decided to try to put it on myself. I tried both ways too - sideloading the zip and flashing the full factory image from google. Now I'm no newbie in this.. but for some odd reason, my Nexus 7 just wont boot past the Google logo in start up... any ideas? Ive been at it for the past couple days and still can't find anything on it
If you are not afraid to loose your data. Enter the recovery and do a factory reset.
BraddahBoi808 said:
So my Nexus 7 still has not received the OTA update, and like a bunch of other, I decided to try to put it on myself. I tried both ways too - sideloading the zip and flashing the full factory image from google. Now I'm no newbie in this.. but for some odd reason, my Nexus 7 just wont boot past the Google logo in start up... any ideas? Ive been at it for the past couple days and still can't find anything on it
Click to expand...
Click to collapse
There are always a small percentage of installations that won't work with a dirty flash (keeping your user data).
This could be because of the specific apps they have installed, flash memory corruption, etc.
That is why you should always backup before doing a system update.
The solution normally is to just wipe data/factory reset from recovery.
vbaros said:
If you are not afraid to loose your data. Enter the recovery and do a factory reset.
Click to expand...
Click to collapse
sfhub said:
There are always a small percentage of installations that won't work with a dirty flash (keeping your user data).
This could be because of the specific apps they have installed, flash memory corruption, etc.
That is why you should always backup before doing a system update.
The solution normally is to just wipe data/factory reset from recovery.
Click to expand...
Click to collapse
So wipe the data before flashing the factory image? Because I have tried booting into recovery AFTER doing the update to wipe data and it kept bootlooping still.
Sent from my Nexus 7 using xda app-developers app
BraddahBoi808 said:
So wipe the data before flashing the factory image? Because I have tried booting into recovery AFTER doing the update to wipe data and it kept bootlooping still.
Click to expand...
Click to collapse
Sorry, I didn't read your original post closely enough, if you are bootlooping at google, then it is a problem with /system and wiping won't help. If you were looping at the bouncing balls or X, then that is user data related so wiping usually fixes it.
If you are stuck at Google, something went wrong with your flash or your flash memory got corrupted.
I would try reflashing the factory image, making sure to do the -w wipe option (by default that is what flash-all.bat does)
Make sure to pay attention to any errors that might show up.
I had the same issue. You need to clear your data and cache after flashing the factory image. See my post here: http://forum.xda-developers.com/showpost.php?p=47472320&postcount=35
msk said:
I had the same issue. You need to clear your data and cache after flashing the factory image. See my post here: http://forum.xda-developers.com/showpost.php?p=47472320&postcount=35
Click to expand...
Click to collapse
It worked all fine until i wiped data and cache at the end of your process... After rebooting it still bootloops and is now hanging at the Google sign... At this point I have no idea what I'm doing wrong...
Bump.. Can someone help me?
Sent from my Nexus 7 using xda app-developers app
BraddahBoi808 said:
Bump.. Can someone help me?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
What method did you use to flash the factory images?
Sent from my Nexus 7
RMarkwald said:
What method did you use to flash the factory images?
Sent from my Nexus 7
Click to expand...
Click to collapse
Command prompt through android sdk. Didn't boot, stayed at Google screen. Then tried wugs toolkit and same thing, hung at Google boot screen...
Sent from my Nexus 7 using xda app-developers app
BraddahBoi808 said:
Command prompt through android sdk. Didn't boot, stayed at Google screen. Then tried wugs toolkit and same thing, hung at Google boot screen...
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
So you did all of the steps listed here? http://forum.xda-developers.com/showthread.php?t=2469508
Yes..
Sent from my Nexus 7 using xda app-developers app
Now sure if this means anything, but when i send the ota update zip through aideload, at the end it gives me
script succeeded: result was [/system]
Does that mean it worked or the system had something wrong??
Not sure on that one.
- Sent from my Galaxy S3
K this stupid thing must hate kit Kat or something cause no matter what ROM I try to flash that's kit kat it still don't boot. I'm tired of this already. Idk what else to do. I thought nexus devices were suppose to be the easiest ones to get updates... /end rant
Sent from my SCH-I545 using xda app-developers app
BraddahBoi808 said:
So my Nexus 7 still has not received the OTA update, and like a bunch of other, I decided to try to put it on myself. I tried both ways too - sideloading the zip and flashing the full factory image from google. Now I'm no newbie in this.. but for some odd reason, my Nexus 7 just wont boot past the Google logo in start up... any ideas? Ive been at it for the past couple days and still can't find anything on it
Click to expand...
Click to collapse
I would try this, if you can use TWRP to back up your data partition, then use Wugfresh's Rom toolkit to flash to stock KRT160, and then root, and install your recovery again.. Then.. restore just the data partiton.. That should bring your nexus to working order..
This will only work if you can move the TWRP folder off your device, use the TWRP folder via OTG to a Sdcard or thumb drive and then copy it back when your back at stock.. Sounds complicated, but its very simple.. That may work for you
Or if your brave enough, just flash Bootloader.img first, then System.img from Stock image.. That should be the simpler method..
Zaphodspeaks said:
I would try this, if you can use TWRP to back up your data partition, then use Wugfresh's Rom toolkit to flash to stock KRT160, and then root, and install your recovery again.. Then.. restore just the data partiton.. That should bring your nexus to working order..
This will only work if you can move the TWRP folder off your device, use the TWRP folder via OTG to a Sdcard or thumb drive and then copy it back when your back at stock.. Sounds complicated, but its very simple.. That may work for you
Or if your brave enough, just flash Bootloader.img first, then System.img from Stock image.. That should be the simpler method..
Click to expand...
Click to collapse
At the moment I dont really care about my data cause I dont have much on it. All i have are a couple songs and a movie, which is easily transferable because they are from my laptop. I just want this thing updated to kit kat. So, one more time, the methods I've tried using are:
Wug's toolkit to restore to KRT16O
ADB sideload to update manually using the OTA zip obtained from here
factory images obatined from google and flashed using the .bat in their zip
the link Mr. @RMarkwald posted
and through flashing stock KRT16O update from Scrosler's rom
So far, ALL methods will not allow my device to boot past the Google logo...
BraddahBoi808 said:
At the moment I dont really care about my data cause I dont have much on it. All i have are a couple songs and a movie, which is easily transferable because they are from my laptop. I just want this thing updated to kit kat. So, one more time, the methods I've tried using are:
Wug's toolkit to restore to KRT16O
ADB sideload to update manually using the OTA zip obtained from here
factory images obatined from google and flashed using the .bat in their zip
the link Mr. @RMarkwald posted
and through flashing stock KRT16O update from Scrosler's rom
So far, ALL methods will not allow my device to boot past the Google logo...
Click to expand...
Click to collapse
Then i would suggest possibly restoring your Nexus to 4.3 and see if you can atleast get it working again..
Im thinking your device maybe corrupted, but dont quote me on that.. Can you atleast boot into recovery?
I made a recovery of a Stock 4.4 from TWRP incase I needed it..
If you cant boot into recovery on the device, you can try booting into TWRP via Wugfresh's tookit.. and try and restore your Nexus that way
https://www.dropbox.com/s/mqczh3q59lydga9/2013-11-13--06-14-08 KRT16O.TWRP.zip Good luck..
Zaphodspeaks said:
Then i would suggest possibly restoring your Nexus to 4.3 and see if you can atleast get it working again..
Im thinking your device maybe corrupted, but dont quote me on that.. Can you atleast boot into recovery?
I made a recovery of a Stock 4.4 from TWRP incase I needed it..
If you cant boot into recovery on the device, you can try booting into TWRP via Wugfresh's tookit.. and try and restore your Nexus that way
https://www.dropbox.com/s/mqczh3q59lydga9/2013-11-13--06-14-08 KRT16O.TWRP.zip Good luck..
Click to expand...
Click to collapse
I can restore back to JSS15R 4.3 fine and the device works fine, no issues. It's just for some reason it doesnt like anything 4.4, which I find very odd. It still hasn't gotten to OTA update either. After updating to 4.4 and it hanging on the Google screen, it can boot into stock recovery fine. I have wiped data and cache in there too to see if that works but nothing. Thanks for all your quick help by the way. So the method your saying now.. Do I flash that from my stuck 4.4 or from rooted 4.3?
I would try that from 4.3....Dont use the stock recovery.. Flash it from TWRP..
Does anyone know of a successful method of full backup and restore of the Google pixel xl?
If so, how?
I've heard twrp isn't ready and I can't find a way to full nandroid backup either. Some clarification would be most appreciated!
prot- said:
Does anyone know of a successful method of full backup and restore of the Google pixel xl?
If so, how?
I've heard twrp isn't ready and I can't find a way to full nandroid backup either. Some clarification would be most appreciated!
Click to expand...
Click to collapse
You cant do a back up through twrp now ? I can on mine and have for months. What happens when you try ?
M9guy said:
You cant do a back up through twrp now ? I can on mine and have for months. What happens when you try ?
Click to expand...
Click to collapse
I heard the restore doesn't actually won't. Have you tried?
prot- said:
I heard the restore doesn't actually won't. Have you tried?
Click to expand...
Click to collapse
I have months ago and worked fine. Are you on the rc1 twrp or the beta ?
M9guy said:
I have months ago and worked fine. Are you on the rc1 twrp or the beta ?
Click to expand...
Click to collapse
Alpha2 still. I heard that rc1 has bootlooped people too. Hmm
[/COLOR]
prot- said:
Alpha2 still. I heard that rc1 has bootlooped people too. Hmm
Click to expand...
Click to collapse
I would flash to rc1 as the beta versions the back ups were not working correctly.
I've restored backups several times and it seemed to go well but the restored rom was killing the battery, not sure why. The phone stayed warm even when off. I didn't spend enough time to see what was going on. Wiping data or a clean reinstall fixed it.
RC 1 been working for me. It's perfect, you don't even need to install TWRP, you can just boot to it via fastboot, backup, reboot and still completely stock. If people are into that.
Sent from my Pixel XL
I'm running rc1 and I have not been able to preform a backup. It tells me that it cannot create the folder to backup... I tried switching boot slots and still can't back up. Is there something I missed?
In TWRP I can't make a back up it says it can't do it, an error message comes up. Will a back up and restore work in flash fire? I know that's from within the ROM I'm just wondering will that work.
Rydah805 said:
RC 1 been working for me. It's perfect, you don't even need to install TWRP, you can just boot to it via fastboot, backup, reboot and still completely stock. If people are into that.
Sent from my Pixel XL
Click to expand...
Click to collapse
How to boot to TWRP via fastboot? do you have a guide?
Ro_man said:
How to boot to TWRP via fastboot? do you have a guide?
Click to expand...
Click to collapse
Literally the first step of its installation.
fastboot boot TWRP.img
Sent from my Pixel XL
Rydah805 said:
Literally the first step of its installation.
fastboot boot TWRP.img
Sent from my Pixel XL
Click to expand...
Click to collapse
Thanks.
dmb219 said:
I've restored backups several times and it seemed to go well but the restored rom was killing the battery, not sure why. The phone stayed warm even when off. I didn't spend enough time to see what was going on. Wiping data or a clean reinstall fixed it.
Click to expand...
Click to collapse
I'm guessing it's because you backed up system and vendor instead of system image and vendor image. Use system image and vendor image instead. I've had the same problem if I used system and vendor. Never any problem if I used the other two instead.
robocuff said:
I'm guessing it's because you backed up system and vendor instead of system image and vendor image. Use system image and vendor image instead. I've had the same problem if I used system and vendor. Never any problem if I used the other two instead.
Click to expand...
Click to collapse
Thanks, I'll try that next time.
robocuff said:
I'm guessing it's because you backed up system and vendor instead of system image and vendor image. Use system image and vendor image instead. I've had the same problem if I used system and vendor. Never any problem if I used the other two instead.
Click to expand...
Click to collapse
I made and restored a backup today using system and vendor images as you suggested and it worked just fine. Thanks again for the help.
I have full backup of stock rooted and Pure Nexus. Works perfectly fine with RC1.
I keep getting a zram dump pop up that can never got before after flashing in twrp. Does anyone else have this issue? It turns into a boot loop when flashing arise sound mod and sometimes after flashing ROMs. It boot loops between the Google splash and the zram dump screen. Man this is annoying Any help would be highly appreciated!
I did a complete clean flash with a factory image wiping everything, and reinstalled twrp. That stopped it for me.
What process did you use when doing the complete factory flash?
chapelfreak said:
I did a complete clean flash with a factory image wiping everything, and reinstalled twrp. That stopped it for me.
Click to expand...
Click to collapse
And did you flash the 7.1.2 factory image or 7.1.1?
chapelfreak said:
I did a complete clean flash with a factory image wiping everything, and reinstalled twrp. That stopped it for me.
Click to expand...
Click to collapse
Guessphx said:
And did you flash the 7.1.2 factory image or 7.1.1?
Click to expand...
Click to collapse
If you bought your pixel from google and NOT from verizon, flash the 7.1.2 factory image, then boot twrp RC1 and flash RC2
Guessphx said:
And did you flash the 7.1.2 factory image or 7.1.1?
Click to expand...
Click to collapse
I used a computer and used flash all to flash 7.1.2, before I did that I backed up all the stuff I on my phone I didn't want to lose like pics.
Thank you I appreciate it going to do this when I get home
chapelfreak said:
I used a computer and used flash all to flash 7.1.2, before I did that I backed up all the stuff I on my phone I didn't want to lose like pics.
Click to expand...
Click to collapse
chapelfreak said:
I used a computer and used flash all to flash 7.1.2, before I did that I backed up all the stuff I on my phone I didn't want to lose like pics.
Click to expand...
Click to collapse
Do you have a 32gb or 128gb? I heard if you do this on a 128 gigabyte it messes up the storage
Guessphx said:
Do you have a 32gb or 128gb? I heard if you do this on a 128 gigabyte it messes up the storage
Click to expand...
Click to collapse
I have the 128GB and never once had an issue. I know with the N6 it happened to it, but I'm not if that happens to our pixels .
Hi Guys, I am sorry if I sound ignorant, I am honestly stuck in limbo here and need some assistance...
I was on Freedom OS 2.1 prior to moving to OB3. Before the move, I backed up fully my Freedom OS 2.1. When I flashed OB3, I didn't realize that I didn't have to do full wipe and could just dirty flash OB3. I now want to restore my nandroid backup, but I am running into a problem where it boot loops and when I boot into recovery I don't get to see the pin code unlock to decrypt the phone, therefore can't see my data partition. I was able to get back my partition and reinstall OB3... Please can someone guide me, how to properly restore my nandroid backup, so my data partition doesn't disappear and Freedom OS 2.1 boots up?
Thank you!
M5devil said:
Hi Guys, I am sorry if I sound ignorant, I am honestly stuck in limbo here and need some assistance...
I was on Freedom OS 2.1 prior to moving to OB3. Before the move, I backed up fully my Freedom OS 2.1. When I flashed OB3, I didn't realize that I didn't have to do full wipe and could just dirty flash OB3. I now want to restore my nandroid backup, but I am running into a problem where it boot loops and when I boot into recovery I don't get to see the pin code unlock to decrypt the phone, therefore can't see my data partition. I was able to get back my partition and reinstall OB3... Please can someone guide me, how to properly restore my nandroid backup, so my data partition doesn't disappear and Freedom OS 2.1 boots up?
Thank you!
Click to expand...
Click to collapse
Youll have to wipe the phone completely from stock recovery, flash the full 4.7.4 zip and finally flash twrp Image from fastboot then you'll be able to restore your backup.
https://forum.xda-developers.com/showpost.php?p=75096633&postcount=1
Forgot to mention, be sure to backup your internal storage first because you will he wiping everything.
Dazed No More said:
Youll have to wipe the phone completely from stock recovery, flash the full 4.7.4 zip and finally flash twrp Image from fastboot then you'll be able to restore your backup.
https://forum.xda-developers.com/showpost.php?p=75096633&postcount=1
Forgot to mention, be sure to backup your internal storage first because you will he wiping everything.
Click to expand...
Click to collapse
Dazed No More said:
Youll have to wipe the phone completely from stock recovery, flash the full 4.7.4 zip and finally flash twrp Image from fastboot then you'll be able to restore your backup.
https://forum.xda-developers.com/showpost.php?p=75096633&postcount=1
Forgot to mention, be sure to backup your internal storage first because you will he wiping everything.
Click to expand...
Click to collapse
Thanks for your assistance! I think I missed something somewhere...
I rebooted to stock recovery (on OB3) and wiped the internal storage. Next I tried flash the 4.7.4 zip via adb sideload and after about 10 min recovery screen returned, but I'm still on OB3 after reboot. Please tell me what am I missing. I am not sure how to flash 4.7.4 zip. I will try now to wipe again internal storage, boot into OB3 and copy the 4.7.4 in windows and try to flash it from stock recovery. I read the link you posted and read from post 19 in OP that's downgrading from OB1/2 and I assume OB3 too -- back to OOS 4.7.x is troublesome and WIFI gets lost. I'm hoping that won't be the case where I am simply trying to do a nadroid restore.
Had no idea this is going to be so difficult...
M5devil said:
Thanks for your assistance! I think I missed something somewhere...
I rebooted to stock recovery (on OB3) and wiped the internal storage. Next I tried flash the 4.7.4 zip via adb sideload and after about 10 min recovery screen returned, but I'm still on OB3 after reboot. Please tell me what am I missing. I am not sure how to flash 4.7.4 zip. I will try now to wipe again internal storage, boot into OB3 and copy the 4.7.4 in windows and try to flash it from stock recovery. I read the link you posted and read from post 19 in OP that's downgrading from OB1/2 and I assume OB3 too -- back to OOS 4.7.x is troublesome and WIFI gets lost. I'm hoping that won't be the case where I am simply trying to do a nadroid restore.
Had no idea this is going to be so difficult...
Click to expand...
Click to collapse
- Wipe everything from stock recovery
- Reboot to fastboot from stock recovery
- Run command fastboot boot twrp.img, then transfer the 4.7.4 over mtp
- Flash 4.7.4 zip
- Reboot
Then let it boot and you can re root after that. Have faith that you are one of the luxjy ones whose WiFi is unaffected and works .
Dazed No More said:
- Wipe everything from stock recovery
- Reboot to fastboot from stock recovery
- Run command fastboot boot twrp.img, then transfer the 4.7.4 over mtp
- Flash 4.7.4 zip
- Reboot
Then let it boot and you can re root after that. Have faith that you are one of the luxjy ones whose WiFi is unaffected and works .
Click to expand...
Click to collapse
Thanks, man! I appreciate it. I was able to successfully get back to my Freedom OS via nandroid restore. Everything is back to normal aside from few hiccups, like no can't view and download images on telegram app for some reason. Uninstalled reinstalled, just see spinning logo but no images.
Other than that. Thank you!
M5devil said:
Thanks, man! I appreciate it. I was able to successfully get back to my Freedom OS via nandroid restore. Everything is back to normal aside from few hiccups, like no can't view and download images on telegram app for some reason. Uninstalled reinstalled, just see spinning logo but no images.
Other than that. Thank you!
Click to expand...
Click to collapse
Wifi works?
Dazed No More said:
Wifi works?
Click to expand...
Click to collapse
Yes, Wi-Fi works!
M5devil said:
Yes, Wi-Fi works!
Click to expand...
Click to collapse
I wish I was that lucky. I dont know what it is with my device but wifi just will not work when reverting back to Nougat...Ive spent so much time flashing official zips trying to get it back before finding the right combination.
Dazed No More said:
I wish I was that lucky. I dont know what it is with my device but wifi just will not work when reverting back to Nougat...Ive spent so much time flashing official zips trying to get it back before finding the right combination.
Click to expand...
Click to collapse
I ended up going back to OB3. I suggest you do the same. Battery life is much much better and phone feels much snappier. Have you tried any 8.1 ROMs? I always preferred the pure vanilla look, so was wondering which 8.1 ROM is good. Thanks!
M5devil said:
I ended up going back to OB3. I suggest you do the same. Battery life is much much better and phone feels much snappier. Have you tried any 8.1 ROMs? I always preferred the pure vanilla look, so was wondering which 8.1 ROM is good. Thanks!
Click to expand...
Click to collapse
I won't go back to an Oreo OOS until audio controls for wired and wireless headphones work. I've tried codename phoenix, liquid remix, AICP and validus. I personally liked validus the most and aicp second.
Hi! I was playing around with my phone and I might have wrecked it somehow. My twrp is password protected, which I have no clue what it is, and therefore can't install roms or restore backups. The phone is not booting into the rom no matter what I do either. Twrp boots everytime I power on my device.
Please help!
Flash stock image and stock recovery (and wipe cache). Then after if it will boot into OOS recovery just click "reboot now".
Were you able to get into twrp? The password is usually the one you set up for your login to andriod system.
If you can get in, then no need worry. i had exact experience last week. Just remember to clear both cache, system, and data. Just keep internal storage intact. Then try to flash stock rom without rooting.
See if you can get it.
The cause of having this issue may due to flashing rom without uninstallng magisk first.
Good luck.
stellarroar said:
Hi! I was playing around with my phone and I might have wrecked it somehow. My twrp is password protected, which I have no clue what it is, and therefore can't install roms or restore backups. The phone is not booting into the rom no matter what I do either. Twrp boots everytime I power on my device.
Please help!
Click to expand...
Click to collapse
Siljorfag said:
Flash stock image and stock recovery (and wipe cache). Then after if it will boot into OOS recovery just click "reboot now".
Click to expand...
Click to collapse
Stock image is the stock OOS rom right?
lyrebird said:
Were you able to get into twrp? The password is usually the one you set up for your login to andriod system.
If you can get in, then no need worry. i had exact experience last week. Just remember to clear both cache, system, and data. Just keep internal storage intact. Then try to flash stock rom without rooting.
See if you can get it.
The cause of having this issue may due to flashing rom without uninstallng magisk first.
Good luck.
Click to expand...
Click to collapse
The twrp password is known only to god because I've tried every pin/password I have ever used on all roms I've tried so far but none of them work. Which is why I can't flash any rom as my storage is encrypted. Most of the times I have a pattern lock set but that can't be mapped to a password can it?
I decided to start from scratch and installed stock recovery and then adb sideloaded first the stock Nougat OOS and then later 5.1.1 stock OOS, but both times in vain. Both times the phone gets stuck on the startup setup saying "just a sec", endlessly. On the very first activity it shows a message, that disappears in a few seconds, saying "Disabled or missing download manager. Can't download voice pack". How can I fix this? Help please.
stellarroar said:
I decided to start from scratch and installed stock recovery and then adb sideloaded first the stock Nougat OOS and then later 5.1.1 stock OOS, but both times in vain. Both times the phone gets stuck on the startup setup saying "just a sec", endlessly. On the very first activity it shows a message, that disappears in a few seconds, saying "Disabled or missing download manager. Can't download voice pack". How can I fix this? Help please.
Click to expand...
Click to collapse
I would fully wipe, then format, but make sure you have the contents from your storage backed up externally. This is the only way to insure there's nothing left over from previous flashes. And then sideload 5.1.1-full update, you should be good from there. I had the same issue after flashing a OOS custom build.
Sent from my ONEPLUS A5010 using XDA Labs
blas4me said:
I would fully wipe, then format, but make sure you have the contents from your storage backed up externally. This is the only way to insure there's nothing left over from previous flashes. And then sideload 5.1.1-full update, you should be good from there. I had the same issue after flashing a OOS custom build.
Sent from my ONEPLUS A5010 using XDA Labs
Click to expand...
Click to collapse
Formatting everything did the trick. I thought sideloading OOS would implicitly do that but I was wrong. Thanks a lot man! Now is there any way I can keep my device unencrypted going ahead? I don't want Twrp to ask me for a password when I'm booting it.