Develop Bugs

[Q] Problem installing custom kernel on stock ROM

Hi all. I just got a Verizon Htc One M7. I bought it used and it was already updated to 4.4.2 Kit kat and sense 5.5. I am new to rooting and unlocking and I am running into issues I am hoping someone can help me with. I successfully unlocked, rooted, and got S-off. A am trying to get a custom kernel on the phone so I can have tap to wake and swipe to wake. I installed TWRP recovery 2.7.0.0. Everything appears to be working I boot into bootloader mode and it say unlocked and s-off on top of the screen. I started recovery and it appears to be working fine. I created a backup and that works. So I tried 2 different kernels elementalx and elite lunar. Both appear to install fine but when I reboot the phone gets stuck in a boot loop on the HTC screen. I then have to go back into recovery and revert back to my saved backup. The phone will then boot up fine. Not sure if I'm doing something wrong or what. I am running the stock ROM. Any help will be greatly appreciated.

Forgive and help a noop!!!!
No one knows? I also just noticed that on the bootloader screen there is no numbers after OS. Which would appear to mean i have no OS. But the phone boots and operates just fine. Any suggestions? Thinking I should get it back to factory and start over and flash the NuSenseSIX rom. If anyone could please help me out here it would be greatly appreciated!!!! I attached a picture of what my bootloader screen looks like.

Reubster24 said:
No one knows? I also just noticed that on the bootloader screen there is no numbers after OS. Which would appear to mean i have no OS. But the phone boots and operates just fine. Any suggestions? Thinking I should get it back to factory and start over and flash the NuSenseSIX rom. If anyone could please help me out here it would be greatly appreciated!!!! I attached a picture of what my bootloader screen looks like.
Click to expand...
Click to collapse
it's the rom you are on, if you go back to stock build you will see the OS-build number correctly displayed. if you are on a custom rom, and its not built correctly, it will not display properly.
you dont need to worry about it. all the info in hboot is for diagnostic purpose and wont effect you in any way.

synisterwolf said:
it's the rom you are on, if you go back to stock build you will see the OS-build number correctly displayed. if you are on a custom rom, and its not built correctly, it will not display properly.
you dont need to worry about it. all the info in hboot is for diagnostic purpose and wont effect you in any way.
Click to expand...
Click to collapse
Ok I appreciate the response. I am still on the stock ROM. Just have it rooted, unlocked and s-off with twrp custom recovery installed. Any ideas as to why I'm not able to get it to boot after installing a custom kernel? Can I just try to flash the NuSenseSIX ROM in the phones current state or should I start over?

Reubster24 said:
Ok I appreciate the response. I am still on the stock ROM. Just have it rooted, unlocked and s-off with twrp custom recovery installed. Any ideas as to why I'm not able to get it to boot after installing a custom kernel? Can I just try to flash the NuSenseSIX ROM in the phones current state or should I start over?
Click to expand...
Click to collapse
if you would like to try NuSense i would make sure you have a good backup or do one before. you'll need to wipe system - data - cache - dalvik in twrp and then install the rom.
---------- Post added at 01:36 PM ---------- Previous post was at 01:29 PM ----------
After some discussion with fellow dev's, i think you havent flash the insecure boot.img that allows you to write to /system. this should stop the kernel bootlooping you.
ok, here we go.
Flash the attached zip in recovery.
wipe dalvik and cache (2x for good measure)
reboot the phone.
then try to flash a custom kernel and see if you boot loop. Let me know what happens. please have a working backup before trying any of this.
(credit to @buckmarble and @brymaster5000)
kernel source

synisterwolf said:
if you would like to try NuSense i would make sure you have a good backup or do one before. you'll need to wipe system - data - cache - dalvik in twrp and then install the rom.
---------- Post added at 01:36 PM ---------- Previous post was at 01:29 PM ----------
After some discussion with fellow dev's, i think you havent flash the insecure boot.img that allows you to write to /system. this should stop the kernel bootlooping you.
Click to expand...
Click to collapse
I have everything backed up google drive with titanium backup as well as backed up in TWRP. When I wipe it doesn't remove the TWRP backup right? I have not flashed any boot.img. I am new to this and don't really know what that is. How would I find the boot.img I need. I think I'll just move forward with the NuSense Rom. Can I just download the zip for the NuSense ROM then wipe and flash it using TWRP and I'm good to go or is there other stuff I need to do?

Reubster24 said:
I have everything backed up google drive with titanium backup as well as backed up in TWRP. When I wipe it doesn't remove the TWRP backup right? I have not flashed any boot.img. I am new to this and don't really know what that is. How would I find the boot.img I need. I think I'll just move forward with the NuSense Rom. Can I just download the zip for the NuSense ROM then wipe and flash it using TWRP and I'm good to go or is there other stuff I need to do?
Click to expand...
Click to collapse
the boot.img zip above will allow you to write to the /system part of the phone.
TWRP will not wipe your backup. that is stored in a location its not allowed to wipe unless you do a "factory reset"
flash the zip above first. let it boot then flash NuSense. I'm not to familiar with that rom so i cant for sure say it will have said insecure boot.img.

Ok I flashed that file and the phone boots up fine. But it has a weird N flashing at the top of the screen now. I'll try a kernel this evening and see what happens. Any idea what the N is? Attached a zipped video of what its doing.

Reubster24 said:
Ok I flashed that file and the phone boots up fine. But it has a weird N flashing at the top of the screen now. I'll try a kernel this evening and see what happens. Any idea what the N is? Attached a zipped video of what its doing.
Click to expand...
Click to collapse
That icon is for NFC. idk why its flashing but make sure its off if you dont use it.
its under settings.

synisterwolf said:
That icon is for NFC. idk why its flashing but make sure its off if you dont use it.
its under settings.
Click to expand...
Click to collapse
Ok. It is off in settings. Tried to turn it on and it won't let me. I'll flash a kernel later and see what happens and if it stops doing it. Is there another insecure boot.img I can try?

Reubster24 said:
Ok. It is off in settings. Tried to turn it on and it won't let me. I'll flash a kernel later and see what happens and if it stops doing it. Is there another insecure boot.img I can try?
Click to expand...
Click to collapse
only need to do it once. flash any kernel that is meant for your rom or switch roms. you should be good to go.

synisterwolf said:
only need to do it once. flash any kernel that is meant for your rom or switch roms. you should be good to go.
Click to expand...
Click to collapse
Awesome thanks for all your help. I think I'm gonna flash a Rom. Any suggestions? I would like something close to the stock Rom.

Thank you for all your help!! I successfully installed the NuSense Rom.

Reubster24 said:
Thank you for all your help!! I successfully installed the NuSense Rom.
Click to expand...
Click to collapse
congrats man, you can PM me if you have anymore questions or post in the Q/A thread and i will try to help
:highfive:

[Q] TWRP asking for encryption password after factory reset?

Thought I'd try out the encryption in AOKP on my Nexus 7 (2013) and decided I didn't like it. I read that a "factory reset" in TWRP was supposed to remove it, although it would nuke all my files, sdcard, apps, etc. No problem, the thing is brand new so nothing really on it. After wiping however, when I boot into recovery now, TWRP is still asking for the encryption PIN. I thought I would just get into the shell over ADB and see what's going on but not able to do that either. I just get "?????????" when trying to view the device with "adb devices". I read something about erasing userdata, system and cache from fastboot and also another piece of info about flashing the stock recovery back to it, but not sure that's the best route. Any thoughts? Thanks.

eris170 said:
Thought I'd try out the encryption in AOKP on my Nexus 7 (2013) and decided I didn't like it. I read that a "factory reset" in TWRP was supposed to remove it, although it would nuke all my files, sdcard, apps, etc. No problem, the thing is brand new so nothing really on it. After wiping however, when I boot into recovery now, TWRP is still asking for the encryption PIN. I thought I would just get into the shell over ADB and see what's going on but not able to do that either. I just get "?????????" when trying to view the device with "adb devices". I read something about erasing userdata, system and cache from fastboot and also another piece of info about flashing the stock recovery back to it, but not sure that's the best route. Any thoughts? Thanks.
Click to expand...
Click to collapse
A factory reset from inside TWRP does NOT wipe internal storage/sdcard. If you want to wipe everything you can either do it from inside TWRP with "advanced wipe" or just do a normal factory reset from Settings/Backup and reset. If you fastboot flash the userdata and cache images that would also be like a factory reset. If you wipe/erase the system you will need to fastboot flash the system image or flash a rom BEFORE you try and reboot.

wantabe said:
A factory reset from inside TWRP does NOT wipe internal storage/sdcard.
Click to expand...
Click to collapse
Sorry, I meant to say I did the advanced wipe and smoked the data partition. I was going to go back and edit my post but it wouldn't let me do it for another five minutes and I went off and did something else. When you say "fastboot flash" the system image, do you mean re-install TWRP with "fastboot flash recovery twrp.img" ?
I tried a different comp and was able to get to the device over ADB so I pushed aokp_flo_jb-mr2_milestone-1.zip over ADB to /sdcard and did the same with gapps-jb-20130813-signed.zip. TWRP installed them OK, but after reboot, the zygote process now keeps trying to restart com.google.android.setupwizard which errors out with a dialog box which says "Unfortunately, Setup Wizard has stopped". I touch "Ok" but the dialog just comes back. Looks like I've made a real mess of things.
Should I just go find the stock OS image and recovery image and flash them over?

eris170 said:
Sorry, I meant to say I did the advanced wipe and smoked the data partition. I was going to go back and edit my post but it wouldn't let me do it for another five minutes and I went off and did something else.
Click to expand...
Click to collapse
I'm pretty sure that wiping data from inside advanced wipe will have wiped everything, that should have been enough to get rid of your encryption.
eris170 said:
When you say "fastboot flash" the system image, do you mean re-install TWRP with "fastboot flash recovery twrp.img" ?
Click to expand...
Click to collapse
No. The system image I was talking about is from the factory image. You have to extract/unzip the factory image a couple times before you can see the zip folder with all the images ( boot (kernel), cache, recovery, system and userdata). You had mentioned in your first post "erasing userdata, system and cache." If you erase system you will need to replace it otherwise your device does not have an os (operating system) anymore. One of many ways to replace it would be to fastboot flash the system image (fastboot flash system system.img) that is extracted from the factory image.
eris170 said:
I tried a different comp and was able to get to the device over ADB so I pushed aokp_flo_jb-mr2_milestone-1.zip over ADB to /sdcard and did the same with gapps-jb-20130813-signed.zip. TWRP installed them OK, but after reboot, the zygote process now keeps trying to restart com.google.android.setupwizard which errors out with a dialog box which says "Unfortunately, Setup Wizard has stopped". I touch "Ok" but the dialog just comes back. Looks like I've made a real mess of things
Click to expand...
Click to collapse
. I've always used the stock rom on my Nexus devices so I'm not much help with anything else. But... just from looking at the names on the zips you installed I'm guessing the "jb" means Jelly Bean and the gapps you installed are almost a year old. So... WTH? ; )
eris170 said:
Should I just go find the stock OS image and recovery image and flash them over?
Click to expand...
Click to collapse
I think in your case the easiest thing to do would be to flash the factory image and start over. You will then need to reinstall TWRP and then use TWRP to install/flash the supersu zip. My advice would be to do lots of research before flashing custom roms and custom kernels. After you get back to the factory rom you really need to use TWRP to do a backup (nandroid) BEFORE you flash any custom roms and kernels, with that done it will be easy as hell to get back to stock after experimenting with whatever! Don't rely on toolkits, install the android sdk and learn adb fastboot commands, it's not hard, hell even I can do it!
[TUTORIAL]Download Factory Images Nexus 7 FLO - Restore back STOCK - With latest version KitKat 4.4.4
I've never used this but looks interesting. [TOOL] 06/22/14 One Click Factory Restore 4.4.4 KTU84P (dead or alive)

wantabe said:
. I've always used the stock rom on my Nexus devices so I'm not much help with anything else. But... just from looking at the names on the zips you installed I'm guessing the "jb" means Jelly Bean and the gapps you installed are almost a year old. So... WTH? ; )
Click to expand...
Click to collapse
Meh.. I like running the older stuff because it's usually faster... I mean as long as there isn't some gaping vulnerability in it.
wantabe said:
I think in your case the easiest thing to do would be to flash the factory image and start over.
Click to expand...
Click to collapse
Thanks for the link that saved me some time! Downloaded an flashed and encryption is finally gone. \o/ . Should be all good now.

eris170 said:
Meh.. I like running the older stuff because it's usually faster... I mean as long as there isn't some gaping vulnerability in it.
Thanks for the link that saved me some time! Downloaded an flashed and encryption is finally gone. \o/ . Should be all good now.
Click to expand...
Click to collapse
One of the great things about android is having the ability to change what you don't like and for the most part it isn't hard to do. I did notice with the update to 4.4 better performance and fluidity on both my N5 and N7 so it might be worth checking out at some point. I didn't care for some of the changes like the ui sounds with the 4.4.1 update but it's all easy to modify. Anyway.. glad you got it sorted out.

[Q] restored a nandroid backup and now stuck on boot screen

help! lol
my dilemma, i updated to 4.4.3, rooted, created a nandroid backup.
then i installed viperone 2.5
all going well till phone stopped sending texts (ee update fault, common fault)
after checking solutions all say factory reset, did that, phone booted, but i couldnt log into google, kept saying could not connect to servers
thought ive had enough, restore my nand, and now its stuck on load screen, been left for 15 mins and no joy, i can still get into twrp but im at a loss at what i can do.
twrp wont let me mount internal storage so i can send another backup, only mounts sd card
s-on so limited options

houston33 said:
help! lol
my dilemma, i updated to 4.4.3, rooted, created a nandroid backup.
then i installed viperone 2.5
all going well till phone stopped sending texts (ee update fault, common fault)
after checking solutions all say factory reset, did that, phone booted, but i couldnt log into google, kept saying could not connect to servers
thought ive had enough, restore my nand, and now its stuck on load screen, been left for 15 mins and no joy, i can still get into twrp but im at a loss at what i can do.
twrp wont let me mount internal storage so i can send another backup, only mounts sd card
s-on so limited options
Click to expand...
Click to collapse
If you can get into recovery, you can get into your bootloader. Flash a new ROM using ADB.
Also, only factory reset as a last resort. There's usually a way to fix stuff without resorting to that.

xunholyx said:
If you can get into recovery, you can get into your bootloader. Flash a new ROM using ADB.
Also, only factory reset as a last resort. There's usually a way to fix stuff without resorting to that.
Click to expand...
Click to collapse
i thought flashing a new rom on the m8 required the firmware setup?
so i can just reinstall viperone 2.5 again?

408
so from where i am now i can just go to twrp and install android rev 21? or do i have to use adb sideload?
is 21 even compatible?
i swore i wasnt gonna mess on with this phone.........

houston33 said:
i thought flashing a new rom on the m8 required the firmware setup?
so i can just reinstall viperone 2.5 again?
Click to expand...
Click to collapse
You sure can. The newer firmware is needed for 4.4.4 ROMs. If you had 2.5, reflash it. It will work with the newest firmware as well. Just not the old stuff.
Here's a pointer: A dirty flash of the ROM you are currently running will reset your tweaks, and often fix problems you are having. When I start having glitches, I first reboot. If that didn't work; and I can't find a solution on XDA easily, I reflash my ROM; the dirty way. It really does help to clear up stuff, especially if you are using themes and tweaks.

Sadly didn't work.
Will have to use one of the stock na droid backups from the collection on here once the thread is up and running again
How do I access phone memory to copy the backup over? I only have boot loader and twrp

houston33 said:
Sadly didn't work.
Will have to use one of the stock na droid backups from the collection on here once the thread is up and running again
How do I access phone memory to copy the backup over? I only have boot loader and twrp
Click to expand...
Click to collapse
In TWRP, you can manage files easily.
Click advanced > file manager
There you can copy files, move them and change permissions. Plus deleting and renaming them.

After updating from cm13 to cm14 cant access TWRP recovery mode

Hello, i tried to OTA update my op3 from oficial CM13 nighly to oficial CM14 nighly and it did update.
but when i tried to enter TWRP recovery mode (i want to restore the backup because the new cm version has too many bugs) it wont open twrp, it stays in the op logo for some seconds and then a black screen appears and i have to restart my phone
i tried to reinstall twrp, intall stock recovery but nothing works, please help

If you had searched for your problem, you would have come across this: http://forum.xda-developers.com/oneplus-3/how-to/oos-3-5-2-comunity-build-t3461648/post68691560#post68691560. Reflash it in fastboot and it will work.

luigymarani said:
Hello, i tried to OTA update my op3 from oficial CM13 nighly to oficial CM14 nighly and it did update.
but when i tried to enter TWRP recovery mode (i want to restore the backup because the new cm version has too many bugs) it wont open twrp, it stays in the op logo for some seconds and then a black screen appears and i have to restart my phone
i tried to reinstall twrp, intall stock recovery but nothing works, please help
Click to expand...
Click to collapse
Are you running official TWRP? CM14.1 requires modified TWRP and I believe most people are using version 23 (Credits to @eng.stk) for CM14.1.

nitros12 said:
If you had searched for your problem, you would have come across this: http://forum.xda-developers.com/oneplus-3/how-to/oos-3-5-2-comunity-build-t3461648/post68691560#post68691560. Reflash it in fastboot and it will work.
Click to expand...
Click to collapse
Thanks a lot! it worked
Hw4ng3r said:
Are you running official TWRP? CM14.1 requires modified TWRP and I believe most people are using version 23 (Credits to @eng.stk) for CM14.1.
Click to expand...
Click to collapse
Oh I didnt know that, thank you

Thank you for both asking the question and answering the question. If I had seen this topic earlier I wouldn't have wasted 5 f*cking hours. Thank you!
CM13 nightly to CM14 nightly ruined everything for me. Never doing dirty flash again.

DamianSewo said:
Thank you for both asking the question and answering the question. If I had seen this topic earlier I wouldn't have wasted 5 f*cking hours. Thank you!
CM13 nightly to CM14 nightly ruined everything for me. Never doing dirty flash again.
Click to expand...
Click to collapse
This is quite funny (obviously not to you and no offense) and sad, but people that have been used CM14.1 for a while have said the same thing for about 2 months now: "people coming to CM14.1 from 13 are in for a mess"

This is quite funny (obviously not to you and no offense) and sad, but people that have been used CM14.1 for a while have said the same thing for about 2 months now: "people coming to CM14.1 from 13 are in for a mess"
Click to expand...
Click to collapse
No offense taken. This is just what happens if you venture using MODs with limited knowledge
But the misery of updating hasn't ended yet. So now I have access to TWRP, and I had done a TWRP nand backup before going to CM14, but I found out this was from the Boot, System, EFS and System Image, but NOT from the 'data'. When I restore everything I have I do get back into CM13, but nothing is working and it's rebooting all the time. Completely useless. I just checked and both my data and sd-card are intact. So I don't understand why I am not just getting back to the state I was before starting the CM14 misery. Is this because files on the 'data' got changed when doing the OTA CM14 nightly?
I also tried first restoring the image and then putting the CM13 nightly that I came from on top of it. Same ****. Also tried other way around, first CM13 nightly from TWRP, and then the image restore ('data' excluded since I didn't have that) on top of it. Also no luck.
Anyone an idea how to get back to my CM13?
By now I have wasted a full working day. I regret ever installing CM14, I just want to get back to the situation yesterday with a working CM13... :crying:

DamianSewo said:
No offense taken. This is just what happens if you venture using MODs with limited knowledge
But the misery of updating hasn't ended yet. So now I have access to TWRP, and I had done a TWRP nand backup before going to CM14, but I found out this was from the Boot, System, EFS and System Image, but NOT from the 'data'. When I restore everything I have I do get back into CM13, but nothing is working and it's rebooting all the time. Completely useless. I just checked and both my data and sd-card are intact. So I don't understand why I am not just getting back to the state I was before starting the CM14 misery. Is this because files on the 'data' got changed when doing the OTA CM14 nightly?
I also tried first restoring the image and then putting the CM13 nightly that I came from on top of it. Same ****. Also tried other way around, first CM13 nightly from TWRP, and then the image restore ('data' excluded since I didn't have that) on top of it. Also no luck.
Anyone an idea how to get back to my CM13?
By now I have wasted a full working day. I regret ever installing CM14, I just want to get back to the situation yesterday with a working CM13... :crying:
Click to expand...
Click to collapse
Exactly, when I got my TWRP working again I tried to restore my backup (cm13) but it happened like you said, wouldn't work.
I had to clean flash a new cm13 rom :/

luigymarani said:
Exactly, when I got my TWRP working again I tried to restore my backup (cm13) but it happened like you said, wouldn't work.
I had to clean flash a new cm13 rom :/
Click to expand...
Click to collapse
Why were you unable to use your backup to restore CM13? In my case I didn't have a backup of the data-partition, which I think is the problem. But if you have a complete backup you should be able to get it back right? Isn't that the whole purpose of doing a backup before you update the ROM?

DamianSewo said:
Why were you unable to use your backup to restore CM13? In my case I didn't have a backup of the data-partition, which I think is the problem. But if you have a complete backup you should be able to get it back right? Isn't that the whole purpose of doing a backup before you update the ROM?
Click to expand...
Click to collapse
It should have worked, but it didn't. I have no idea why, it was a complete backup and everything in it was working perfectly so idk

luigymarani said:
It should have worked, but it didn't. I have no idea why, it was a complete backup and everything in it was working perfectly so idk
Click to expand...
Click to collapse
Okay so if you restored a complete backup and still wasn't able to get back to a working CM13 then we probably have exactly the same issue.
It could also be related to the TWRP version we have installed now, maybe the new TWRP is not able to handle CM13. Anyone here to comment on this?

DamianSewo said:
Okay so if you restored a complete backup and still wasn't able to get back to a working CM13 then we probably have exactly the same issue.
It could also be related to the TWRP version we have installed now, maybe the new TWRP is not able to handle CM13. Anyone here to comment on this?
Click to expand...
Click to collapse
Which TWRP version are you using? I flashed the 3.0.2.1-v23 and it supports cm13, because o already flashed a new cm13 rom and I'm using TWRP normally.

luigymarani said:
Which TWRP version are you using? I flashed the 3.0.2.1-v23 and it supports cm13, because o already flashed a new cm13 rom and I'm using TWRP normally.
Click to expand...
Click to collapse
I'm also using 3.0.2.1-v23. Trying to find any information that could help me have my CM13 TWRP image working again, but no luck so far

Stuck with Twrp booting

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.