I have successfully decrypted my essential phone using the dm verity disabler by zackptg. Need to test it some more, but twrp boots after flashing it, instantly.it doesn't have that lag
jacksummers said:
I have successfully decrypted my essential phone using the dm verity disabler by zackptg. Need to test it some more, but twrp boots after flashing it, instantly.it doesn't have that lag
Click to expand...
Click to collapse
were u rooted before or not? did u have to format everything in twrp?
edit it actually works!!!!!! I'm unencrypted...i can go into twrp while a pin is set....i can flash magisk with first boot of a rom and it boots...!!!!!
This is a huge advancement. I didn't think it worked until I booted into twrp. And it was instantaneous.so before I flashed the dm verity decryption zip, I did indeed wipe everything on both slots, then mounted system in twrp and flashed the zip, then I flashed the ROM.i will be switching back to stock to test if it stays decrypted later today. I'm running a gsi,(benzo ROM+ all my own customizations)rooted,with all the trimmings) the same mentality will have to follow, but it will be interesting to see how it goes with flashing stock fresh. I imagine restoring my nandroid will be fine and stay decrypted, but probably will have to flash stock, then after setup, back to twrp, wipe factory reset and flash the dm verity decryption zip..I think, I gotta just do it to be sure. Anyone who does this should share notes and that will help the community.
Here is a good question, wtf can I do to have lte again. ever since pie official, I lost lte.phone drops to 3g during calls only. I discovered this while searching for a fix for my volte. Hence,, switching to gsi's because they don't have volte and neither does my stock, even with fresh installs.i have t mobile.all the betas it worked fine.
Here's the thread folks
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Thanks to Zackptg
jacksummers said:
This is a huge advancement. I didn't think it worked until I booted into twrp. And it was instantaneous.so before I flashed the dm verity decryption zip, I did indeed wipe everything on both slots, then mounted system in twrp and flashed the zip, then I flashed the ROM.i will be switching back to stock to test if it stays decrypted later today. I'm running a gsi,(benzo ROM+ all my own customizations)rooted,with all the trimmings) the same mentality will have to follow, but it will be interesting to see how it goes with flashing stock fresh. I imagine restoring my nandroid will be fine and stay decrypted, but probably will have to flash stock, then after setup, back to twrp, wipe factory reset and flash the dm verity decryption zip..I think, I gotta just do it to be sure. Anyone who does this should share notes and that will help the community.
Here is a good question, wtf can I do to have lte again. ever since pie official, I lost lte.phone drops to 3g during calls only. I discovered this while searching for a fix for my volte. Hence,, switching to gsi's because they don't have volte and neither does my stock, even with fresh installs.i have t mobile.all the betas it worked fine.
Click to expand...
Click to collapse
How did u get wifi to work on gsi..for me i can seem to get it working..and im using the last 8.1 vendor....for the lte go into dialer and *#*#4636#*#* and change the lte/utms/cdma setting around until u get it
Tech_Savvy said:
How did u get wifi to work on gsi..for me i can seem to get it working..and im using the last 8.1 vendor....for the lte go into dialer and *#*#4636#*#* and change the lte/utms/cdma setting around until u get it
Click to expand...
Click to collapse
I have found that after booting up a gsi, factory reset it. Then be sure not to root with magisk. Every time I tried it killed my data and wifi. Use phhhsuperuser ab zip. I think I may have had to flash my modem.img a time as well after the initial install.
And yeah I got it kinda, still no lte. I'm gonna try a modem img from the pie firmware..I think it is the problem
Has anyone had success in decrypting on stock? I cant get it and then i lose touch with the phone booted up. So in other words do not try to decrypt stock. U will wreck your phone and the only way to fix it is to flash stock via fastboot AND adb sideload. One or the other doesnt fix it for some reason. Has to be both.
jacksummers said:
Has anyone had success in decrypting on stock? I cant get it and then i lose touch with the phone booted up. So in other words do not try to decrypt stock. U will wreck your phone and the only way to fix it is to flash stock via fastboot AND adb sideload. One or the other doesnt fix it for some reason. Has to be both.
Click to expand...
Click to collapse
Were you trying on stock oreo or pie?
governmentissuejoe said:
Were you trying on stock oreo or pie?
Click to expand...
Click to collapse
Both
jacksummers said:
Both
Click to expand...
Click to collapse
I tried it on stock Oreo and it works.
governmentissuejoe said:
I tried it on stock Oreo and it works.
Click to expand...
Click to collapse
Ok cool, I was worried I did this as a fluke. What was the steps u did?
jacksummers said:
Ok cool, I was worried I did this as a fluke. What was the steps u did?
Click to expand...
Click to collapse
So these are all the steps I took to get it to work. All of these steps may or may not be necessary. I used aer0zer0's stock dump for the lastest release of oreo and flashed the wipe all bat. It did its thing and wiped and flashed on both slots. I booted into the rom and finished initial setup and enabled adb in developer settings. I rebooted to bootloader and flashed twrp to inactive slot. I booted into recovery and selected the format data option and typed yes. I rebooted to bootloader and reflashed twrp. When I booted into recovery I transferred the stockboot.img, magisk 17.1 zip, and disable encryption zip to the phone. I flashed the stockboot.img to the boot partition. I then flashed the disable encryption zip. I then mounted the system partition and flashed the magisk zip. Finally, I rebooted into the rom and set pin and fingerprint. I installed EX Kernel Manager and created a backup of the decrypted magisked boot.img just in case. I flashed twrp through ex kernel manager and rebooted to recovery. Everything stayed decrypted. I flashed my newly created boot.img backup and booted back to my rom. Thats it. I hope I remembered everything. I hope this helps. Again, I do not know if all the steps I took are required but it worked for me.
Related
New OP6 owner, quite bugged with how this thing works when flashing stuff..
it was a breeze on my 6p, anyways.
i decided to do a "Clean" flash and wiped data/system/dalvik etc.
then tried to flash the Full zip of 5.1.8 (it is a 1.2gb file) and i flashed via TWRP then flashed twrp zip and rebooted recovery/flashed magisk.
but there is no OS installed it says, boots me back into twrp.
my question now is how do i get it back to load up OOS, do i have to use fastboot now .. ?
i dont want it to wipe my whole SD
what do i do, and how do i stop this from happening for next time?
i thought flashing was normal that way, are we not supposed to wipe system with the op phones..?
i had a MOD installed (xXx) and wanted it removed so that i could install another mod ,thus i wiped system/data etc.
please let me know how to fix this, thx !
leondestiny said:
New OP6 owner, quite bugged with how this thing works when flashing stuff..
it was a breeze on my 6p, anyways.
i decided to do a "Clean" flash and wiped data/system/dalvik etc.
then tried to flash the Full zip of 5.1.8 (it is a 1.2gb file) and i flashed via TWRP then flashed twrp zip and rebooted recovery/flashed magisk.
but there is no OS installed it says, boots me back into twrp.
my question now is how do i get it back to load up OOS, do i have to use fastboot now .. ?
i dont want it to wipe my whole SD
what do i do, and how do i stop this from happening for next time?
i thought flashing was normal that way, are we not supposed to wipe system with the op phones..?
i had a MOD installed (xXx) and wanted it removed so that i could install another mod ,thus i wiped system/data etc.
please let me know how to fix this, thx !
Click to expand...
Click to collapse
You need to make sure you are booting the slot you flashed the rom on, A or B.
sting5566 said:
You need to make sure you are booting the slot you flashed the rom on, A or B.
Click to expand...
Click to collapse
how do i do this? i only flashed zip from the root of my SD , there was no option to select either A or B :C
i went into advanced or seomthing and saw SLot a and B i tapped a and reboot sytem now it is stuck on twrp logo.
f** this ab ****.
When u flashed the rom and rebooted it should let u know which one u r flashing on when u flash magisk, the xXx should have been a magisk module so should have been deleted when u wiped data, I would re-download 5.1.8
Wipe all again.
Flash OS
Flash twrp installer
Reboot to twrp
Flash magisk and reboot
---------- Post added at 01:23 PM ---------- Previous post was at 01:22 PM ----------
Did u have the magisk module version of xXx, if so all u had to do was uncheck it and reboot
OnePlus 6 has two partitions like the Pixel 2. For seamless OTA updates. In TWRP go to the Reboot menu and you'll see your currently active slot. It's either A or B. Switch to the other one and reboot. That should do it if you did flash the ROM.
Bradl79 said:
When u flashed the rom and rebooted it should let u know which one u r flashing on when u flash magisk, the xXx should have been a magisk module so should have been deleted when u wiped data, I would re-download 5.1.8
Wipe all again.
Flash OS
Flash twrp installer
Reboot to twrp
Flash magisk and reboot
---------- Post added at 01:23 PM ---------- Previous post was at 01:22 PM ----------
Did u have the magisk module version of xXx, if so all u had to do was uncheck it and reboot
Click to expand...
Click to collapse
man screw this ab partition shet, i will be forced to do a userdata reset..
can you please advise me what not to do to get into this mess again..?
its not fun recopying my data back and forth.
all i tried to do was clean flash and flash the latest rom via twrp..
why does this thing has to be so complex, please tell me if a clean wipe does this mess ?
cant we safely clean wipe this thing or what?
i love the phone, but the flashing stuff is a huge mess imo.
leondestiny said:
man screw this ab partition shet, i will be forced to do a userdata reset..
can you please advise me what not to do to get into this mess again..?
its not fun recopying my data back and forth.
all i tried to do was clean flash and flash the latest rom via twrp..
why does this thing has to be so complex, please tell me if a clean wipe does this mess ?
cant we safely clean wipe this thing or what?
i love the phone, but the flashing stuff is a huge mess imo.
Click to expand...
Click to collapse
You can always just keep a backup of userdata in TWRP but you don't have to wipe data. If you wipe system and flash the full zip, you will get the no os error but you can boot to system anyway. It just thinks there is no os. The bootloop to TWRP is probably related to magisk.
mikex8593 said:
You can always just keep a backup of userdata in TWRP but you don't have to wipe data. If you wipe system and flash the full zip, you will get the no os error but you can boot to system anyway. It just thinks there is no os. The bootloop to TWRP is probably related to magisk.
Click to expand...
Click to collapse
took me an hour or so to get this thing booting up again..
without the need to wipe SD , this is so strange.
i honestly have no idea how i did it, but i am afraid to use twrp now..
this thing is messed up
leondestiny said:
took me an hour or so to get this thing booting up again..
without the need to wipe SD , this is so strange.
i honestly have no idea how i did it, but i am afraid to use twrp now..
this thing is messed up
Click to expand...
Click to collapse
It's relatively easy. Just always remember to flash TWRP and magisk after flashing full ROM zip. It's always a safe bet to erase your lock screen before messing with TWRP as well so it can just decrypt with no password. If you use a magisk ROM, it's all systemless so the only changes that would stay are the ones that would debloat apps or remove system files. Everything would revert back to normal after you uncheck the ROM module in magisk manager.
mikex8593 said:
It's relatively easy. Just always remember to flash TWRP and magisk after flashing full ROM zip. It's always a safe bet to erase your lock screen before messing with TWRP as well so it can just decrypt with no password. If you use a magisk ROM, it's all systemless so the only changes that would stay are the ones that would debloat apps or remove system files. Everything would revert back to normal after you uncheck the ROM module in magisk manager.
Click to expand...
Click to collapse
hmm okay thx, someone suggested me omni rom, but i will need to erase data right?
but my issue is, if in case i wanted to go back to OOS, would i need to erase data again? :l
and also about flashing roms, must they be flashed on both slots..? a and b ?
i have no clue how i got OOS back booting to be honest.. :l
leondestiny said:
hmm okay thx, someone suggested me omni rom, but i will need to erase data right?
but my issue is, if in case i wanted to go back to OOS, would i need to erase data again? :l
and also about flashing roms, must they be flashed on both slots..? a and b ?
i have no clue how i got OOS back booting to be honest.. :l
Click to expand...
Click to collapse
Switching ROMs, it is best to erase data or keep separate data backups for each ROM and restore the associated ones. As far as flashing on both slots, it wouldn't hurt, but it's not necessary unless instructions dictate. The whole reason for the slots is to allow seamless updates while the os is still active. If you experience any issues with bugs that aren't stated to be in the ROM thread, a clean install is always recommended.
mikex8593 said:
Switching ROMs, it is best to erase data or keep separate data backups for each ROM and restore the associated ones. As far as flashing on both slots, it wouldn't hurt, but it's not necessary unless instructions dictate. The whole reason for the slots is to allow seamless updates while the os is still active. If you experience any issues with bugs that aren't stated to be in the ROM thread, a clean install is always recommended.
Click to expand...
Click to collapse
thx mate, so for next time if i were to flash some oos through twrp, i only need to wipe data/cache etc.
then flash the oos zip ? i dont think i had the option to select which Slot to flash it to, so i guess i just have to reboot to the slot that it has it flashed on..?
and also flashing procedure must be like Rom then twrp then reboot twrp then flash magisk yes?
leondestiny said:
took me an hour or so to get this thing booting up again..
without the need to wipe SD , this is so strange.
i honestly have no idea how i did it, but i am afraid to use twrp now..
this thing is messed up
Click to expand...
Click to collapse
No sheet
This is what happened to me LOL and I soft bricked phone. Never ever bricked a phone before.
I tried to flash havoc os, OOS was originally on both A and B.
This process wiped slot B clean (even tho was booting on slot A), and OOS stayed on slot A.
I went to the reboot screen to reboot recovery on slot B and BAM I was bricked locked into fastboot mode.
And people say its easy.
Now I am in msmdownloadtool, I have managed to get it connected, and I can start the recovery but it fails, so I think the phone may be proper bricked.
Anyone getting a oneplus6 I would say these phones seem to have a genuine risk of brick, all I did was try to boot of a slot which TWRP says had no OS and now I have this problem.
---------- Post added at 01:59 ---------- Previous post was at 01:25 ----------
mikex8593 said:
It's relatively easy. Just always remember to flash TWRP and magisk after flashing full ROM zip. It's always a safe bet to erase your lock screen before messing with TWRP as well so it can just decrypt with no password. If you use a magisk ROM, it's all systemless so the only changes that would stay are the ones that would debloat apps or remove system files. Everything would revert back to normal after you uncheck the ROM module in magisk manager.
Click to expand...
Click to collapse
Havoc OS requires Oxygen OOS in both slots.
So I need to somehow get this to work.
I can unbrick the phone now with msmdownloadtool.
After ubricked the bootloader is locked again so I have to start from scratch.
Unlock oem loader in OS
Unlock bootloader in fastboot
Copy zips to phone.
Boot into TWRP and install TWRP, it says it installs to both slots but B bricks phone.
At this point I have oxygen OOS installed via recovery tool on slot A, twrp installed.
If I try to boot in slot B, phone bricks, fastboot loop which doesnt allow you to boot back into twrp so cannot switch back to slot A without msmdownload tool.
So the question is after I have recovered the phone how do I get oxygen OOS onto slot B as well, given I Cannot boot from slot B?
The solution is probably easy to those who know how but seems it isnt documented.
chrcol said:
No sheet
This is what happened to me LOL and I soft bricked phone. Never ever bricked a phone before.
I tried to flash havoc os, OOS was originally on both A and B.
This process wiped slot B clean (even tho was booting on slot A), and OOS stayed on slot A.
I went to the reboot screen to reboot recovery on slot B and BAM I was bricked locked into fastboot mode.
And people say its easy.
Now I am in msmdownloadtool, I have managed to get it connected, and I can start the recovery but it fails, so I think the phone may be proper bricked.
Anyone getting a oneplus6 I would say these phones seem to have a genuine risk of brick, all I did was try to boot of a slot which TWRP says had no OS and now I have this problem.
---------- Post added at 01:59 ---------- Previous post was at 01:25 ----------
Havoc OS requires Oxygen OOS in both slots.
So I need to somehow get this to work.
I can unbrick the phone now with msmdownloadtool.
After ubricked the bootloader is locked again so I have to start from scratch.
Unlock oem loader in OS
Unlock bootloader in fastboot
Copy zips to phone.
Boot into TWRP and install TWRP, it says it installs to both slots but B bricks phone.
At this point I have oxygen OOS installed via recovery tool on slot A, twrp installed.
If I try to boot in slot B, phone bricks, fastboot loop which doesnt allow you to boot back into twrp so cannot switch back to slot A without msmdownload tool.
So the question is after I have recovered the phone how do I get oxygen OOS onto slot B as well, given I Cannot boot from slot B?
The solution is probably easy to those who know how but seems it isnt documented.
Click to expand...
Click to collapse
Fastboot boot recovery. Img
Flash oos full ROM zip
Flash recovery. Zip
Reboot recovery
Flash oos full ROM zip AGAIN
flash twrp. Zip AGAIN
Reboot recovery
Flash magisk if you want root.
Make sure your using the correct twrp aswell. I recommend bluespark v86
chrcol said:
And people say its easy.
Click to expand...
Click to collapse
it is not easy, i make backups of my whole phone every 2weeks because i am a flashaholic i see myself switching from aosp back to oos and vice versa (i love oos) i actually gave up on flashing roms some weeks ago tried to stick to oos only so that i wont be bothered with bricks for whatver reason (and not being forced to use msmtool) , it is frustrating.
you always have to make sure you are not flashing a rom that has an older security patch , e.g november build of oos if you flash aosp rom with october build you might brick, so the rom has to be either on november security patch or newer e.g december.
it is so confusing as you even have to use the latest twrp always or else you can mess it up again..
always make backups is my advice.
leondestiny said:
it is not easy, i make backups of my whole phone every 2weeks because i am a flashaholic i see myself switching from aosp back to oos and vice versa (i love oos) i actually gave up on flashing roms some weeks ago tried to stick to oos only so that i wont be bothered with bricks for whatver reason (and not being forced to use msmtool) , it is frustrating.
you always have to make sure you are not flashing a rom that has an older security patch , e.g november build of oos if you flash aosp rom with october build you might brick, so the rom has to be either on november security patch or newer e.g december.
it is so confusing as you even have to use the latest twrp always or else you can mess it up again..
always make backups is my advice.
Click to expand...
Click to collapse
If you're installing havoc os, make sure you're using latest bluespark TWRP first. Reboot recovery, flash oos, flash TWRP, reboot recovery, flash havoc gapps and magisk then reboot. The only difference in a/b partition is that there's a few extra steps in the flashing process. You don't have to flash to both slots to have havoc, but you also shouldn't be manually changing the slot in TWRP to try to boot a specific slot unless you know what you're doing.
Hello everyone,
I don't know much about partitions but I know something is not right with mine
So, A few days ago my phone got bricked because I flashed crDroid rom. (I did something wrong)
So, after a lot of research, I found an solution to unbrick my phone. So it worked, I booted into software again and I was free to use.
So later, I decided to install an custom rom again (Havoc OS). I installed the rom but after I clean flashed the rom, I got stuck on booting logo.
So, I thought lets see what partition B does. So I booted into partition B and I got stuck on the logo of TWRP. Not sure why.
I really wanna know why this happend and how to fix my device.
(Btw, now my phone is working again and I am on stock os with rooted using Magisk 16,7.)
But just wanna know what I did wrong
I used the instruction in this thread: https://forum.xda-developers.com/oneplus-6/development/enchilada-romcrdroid-t3827070. And after I did that it got bricked.
I hope anyone knows what happend and how to fix my partition!
Friendly regards,
Crewz
Hi, why you get stuck and what not is because you simply do not follow the instructions 100%
After rom install and twrp install did you reboot? When you reboot at that point it will change partition.
If you get stuck on boot again, try reflash rom (without wipes), flash twrp, reboot to recovery, flash gapps and start the device. Apply root after setup this time just to be sure. Another thing could also be magisk, some roms require a later magisk version. But like I said, root after setup just to be sure where the issue is . Happy flashing mate!
whizeguy said:
Hi, why you get stuck and what not is because you simply do not follow the instructions 100%
After rom install and twrp install did you reboot? When you reboot at that point it will change partition.
If you get stuck on boot again, try reflash rom (without wipes), flash twrp, reboot to recovery, flash gapps and start the device. Apply root after setup this time just to be sure. Another thing could also be magisk, some roms require a later magisk version. But like I said, root after setup just to be sure where the issue is . Happy flashing mate!
Click to expand...
Click to collapse
I did the exact steps as in the thread.
ItsCrewz said:
I did the exact steps as in the thread.
Click to expand...
Click to collapse
If you're booted up and stable there's nothing wrong with your partitions.
What version of twrp are you using?
iElvis said:
If you're booted up and stable there's nothing wrong with your partitions.
What version of twrp are you using?
Click to expand...
Click to collapse
The newest one.
Look when I boot into TWRP and switch to partition B. I am stuck at logo of twrp
ItsCrewz said:
The newest one.
Look when I boot into TWRP and switch to partition B. I am stuck at logo of twrp
Click to expand...
Click to collapse
Which version? There are multiple "newest" ones.
Just because you have two slots doesn't mean both are bootable. The intent of the A/B arrangement is to allow seamless updates, not create a dual-boot phone. The inactive slot is often not bootable or will boot up with things broken. It's inactive because it's not suppose to be booted.
Switching slots manually is rarely necessary anyway. Why do you need to do it?
iElvis said:
Which version? There are multiple "newest" ones.
Just because you have two slots doesn't mean both are bootable. The intent of the A/B arrangement is to allow seamless updates, not create a dual-boot phone. The inactive slot is often not bootable or will boot up with things broken. It's inactive because it's not suppose to be booted.
Switching slots manually is rarely necessary anyway. Why do you need to do it?
Click to expand...
Click to collapse
Yes I know what it means. But it isn't normal that it boots into twrp and get stuck on the logo
I break my system a lot (currently testing which of my favorite Xposed modules work with Pie) . I've had to set up from scratch like 6 times in the past week. Every TWRP restore results in a boot loop, both custom and stock. Has anyone made it work and, if so, how? It surprises me that our TWRP is official if it can't restore a backup.
Encrypted?
arkansawdave74 said:
I break my system a lot (currently testing which of my favorite Xposed modules work with Pie) . I've had to set up from scratch like 6 times in the past week. Every TWRP restore results in a boot loop, both custom and stock. Has anyone made it work and, if so, how? It surprises me that our TWRP is official if it can't restore a backup.
Click to expand...
Click to collapse
I'm having the same problem. This is my first a/b device and everything I thought I knew after flashing ROMs for years just doesn't seem to work on this architecture. Like you said twrp backup restore always results in a bootloop. Also any full custom ROMs I've tried appear to overwrite twrp and install its own recovery. Even gsi's don't boot and then twrp freezes and back to stock I go. This thing has me stumped.
Skippy12359 said:
I'm having the same problem. This is my first a/b device and everything I thought I knew after flashing ROMs for years just doesn't seem to work on this architecture. Like you said twrp backup restore always results in a bootloop. Also any full custom ROMs I've tried appear to overwrite twrp and install its own recovery. Even gsi's don't boot and then twrp freezes and back to stock I go. This thing has me stumped.
Click to expand...
Click to collapse
I noticed when installing RR that it actually needs that Lineage recovery to factory reset after the install. A TWRP factory reset wouldn't help it, and it wouldn"t boot after the install. Funny how they try so hard to stop us tinkerers, then steal all our cool ideas for their stock ROMs. I see Linux phones in my future.
I wonder if a factory reset with that Lineage recovery would help after a TWRP restore? Next time I may try that.
Damn! I just got it. I'm typing this on a restored crDroid Official. The boot.img is in ramdisk, so only backup system and data. Yay!
WoKoschekk said:
Encrypted?
Click to expand...
Click to collapse
Just saw this. No. I had flashed dm-verity. Good thinking.
arkansawdave74 said:
Damn! I just got it. I'm typing this on a restored crDroid Official. The boot.img is in ramdisk, so only backup system and data. Yay!
Click to expand...
Click to collapse
So your saying because recovery is in the boot image that we need only to backup system and data and then a restore of same will not go into a bootloop? That would mean the problem has been backing up and then restoring the boot image. System as root and no recovery partition is just hard to grasp at this point. For me restoring data in a backup of stock results in twrp error 255.
Skippy12359 said:
So your saying because recovery is in the boot image that we need only to backup system and data and then a restore of same will not go into a bootloop? That would mean the problem has been backing up and then restoring the boot image. System as root and no recovery partition is just hard to grasp at this point. For me restoring data in a backup of stock results in twrp error 255.
Click to expand...
Click to collapse
I spoke too soon. This was the 1st time I'd flashed dm-verity on the install. That's why it worked. It won't work if /data is encrypted. I just made a backup with boot as well and it restored fine.
arkansawdave74 said:
I spoke too soon. This was the 1st time I'd flashed dm-verity on the install. That's why it worked. It won't work if /data is encrypted. I just made a backup with boot as well and it restored fine.
Click to expand...
Click to collapse
Which version of dm- verify are you using and what steps did you take to get crdroid to boot?
Skippy12359 said:
Which version of dm- verify are you using and what steps did you take to get crdroid to boot?
Click to expand...
Click to collapse
I'm not sure where I got it Or else I would link you. But this is the one I'm using this one. I flashed it after formatting /data and also after installing the ROM. One of those is proper, but I couldn't remember. I think it's supposed to be after you install, but before 1st boot.
https://www.mediafire.com/download/uxldj5okanllfza
arkansawdave74 said:
I'm not sure where I got it Or else I would link you. But this is the one I'm using this one. I flashed it after formatting /data and also after installing the ROM. One of those is proper, but I couldn't remember. I think it's supposed to be after you install, but before 1st boot.
https://www.mediafire.com/download/uxldj5okanllfza
Click to expand...
Click to collapse
That's the same one I've been using. So crdroid actually booted for you after doing a normal wipe in TWRP?. Assuming you had stock pie installed.
Skippy12359 said:
That's the same one I've been using. So crdroid actually booted for you after doing a normal wipe in TWRP?. Assuming you had stock pie installed.
Click to expand...
Click to collapse
Yup. I've restored it twice and made another with boot included and it booted as well. I hope it works with RR too, but I've got a helluva headache. I may stop messing with it for now.
Oh, I had wiped dalvic (actually ART), system, and data. I don't think boot was an option during wipe.
You know, I've only had one device before thar force encrypted, and back then, TWRP couldn't decrypt /data except by formatting. Now it can. That's why I didn't suspect it was an encryption issue.
I was still using a Galaxy S5 with crDroid 7.1.2 built by me until last week. It died, may it rest in peace.
Skippy12359 said:
That's the same one I've been using. So crdroid actually booted for you after doing a normal wipe in TWRP?. Assuming you had stock pie installed.
Click to expand...
Click to collapse
If, when you boot TWRP, it asks you to decrypt, dm-verity didn't work, and it might not work with stock. I'm only figuring it out at the moment.
arkansawdave74 said:
If, when you boot TWRP, it asks you to decrypt, dm-verity didn't work, and it might not work with stock. I'm only figuring it out at the moment.
Click to expand...
Click to collapse
My goal was to have twrp backup of stock pie which is really great in my opinion and also be able to flash Q gsi's like I do on my Moto g6. So far any backup restore of stock just bootloops and any gsi just hangs at boot logo or boots back to recovery.
arkansawdave74 said:
If, when you boot TWRP, it asks you to decrypt, dm-verity didn't work, and it might not work with stock. I'm only figuring it out at the moment.
Click to expand...
Click to collapse
It does appear to be an encryption issue with a stock rom TWRP backup restore not booting. Formatting data in TWRP and rebooting always results in a bootloop. Until I can format data to remove encryption and get it to boot and the security setting says it's not encrypted, I don't think a backup will ever boot. Out of ideas at this point.
Skippy12359 said:
It does appear to be an encryption issue with a stock rom TWRP backup restore not booting. Formatting data in TWRP and rebooting always results in a bootloop. Until I can format data to remove encryption and get it to boot and the security setting says it's not encrypted, I don't think a backup will ever boot. Out of ideas at this point.
Click to expand...
Click to collapse
For stock, I wonder if you could boot TWRP after all those fastboot commands and flash dm-verity before booting stock. You may be able to keep stock from encrypting. I don't know for sure though.
Hi guys. Really need your help. Oneplus 7pro ,european version running 10.0.4 software, latest magisk 20.4 i think? and twrp. Everything was running fine until earlier when I installed a system ui overlay (one i've used before) and now my phone is in a boot loop. I can access TWRP, I've run the substratum overlay uninstaller zip and removed all magisk modules but still i'm in a bootloop. I've never had a proper bootloop before and i'm very frustrated. I've googled for the past few hours and removed everything I can think of that could be causing issues. Does anyone have some advice that doesn't end with me losing all my data? I have a backup but its from a month ago. I've never had this issue before so i'm a little stuck. Thanks
Edit. Phone is fully accessible through my laptop I can see all my files and connect to it. I just cannot get it to boot,surely its a simple fix?
Bxperiaz3 said:
Hi guys. Really need your help. Oneplus 7pro ,european version running 10.0.4 software, latest magisk 20.4 i think? and twrp. Everything was running fine until earlier when I installed a system ui overlay (one i've used before) and now my phone is in a boot loop. I can access TWRP, I've run the substratum overlay uninstaller zip and removed all magisk modules but still i'm in a bootloop. I've never had a proper bootloop before and i'm very frustrated. I've googled for the past few hours and removed everything I can think of that could be causing issues. Does anyone have some advice that doesn't end with me losing all my data? I have a backup but its from a month ago. I've never had this issue before so i'm a little stuck. Thanks
Edit. Phone is fully accessible through my laptop I can see all my files and connect to it. I just cannot get it to boot,surely its a simple fix?
Click to expand...
Click to collapse
Can you boot in TWRP? if can try changing slot and boot from it
Mervingio said:
Can you boot in TWRP? if can try changing slot and boot from it
Click to expand...
Click to collapse
Hi,yes I can. Its loading the logo now so i'll wait and see what happens. If that works then what should be the next thing I do?
Edit: Slot B seems to be bootlooping on the logo unless its meant to take a few minutes
Is there a way to recover without wiping my data?
So slot A sits on the caution device rooted screen then defaults to the fastboot rescue mode which allows me to select reboot to recovery which is twrp. From there I have full access to the phone but still not booting to system. Slot B passes the fastboot screen and hangs on the one plus logo just circling around. This is my first rooted phone and I haven't had any problems until now so I'm hoping its something simple because I didnt do anything big to cause it. Hopefully someone has some insight.
Can I just sideload the current version of OOS i'm running using TWRP and not lose my data?
Bxperiaz3 said:
Can I just sideload the current version of OOS i'm running using TWRP and not lose my data?
Click to expand...
Click to collapse
Yes
MrSteelX said:
Yes
Click to expand...
Click to collapse
Will I lost root or relock the bootloader? I'm trying to find the least destructive way to get back to what I had which was oos 10 with twrp and magisk.
Uninstalled magisk and was able to reboot. However reflashing it as i want to retain root makes it bootloop again. Any possible fix for this that isn't a factory reset and reroot?
I can't get substratum or substratum themes to work on any rom or stock, nothing happens after reboots.....or everything turns this weird orange theme. Then one time it corrupted the whole OS and I had to wipe.
try to Dirty flash the same Oxygen version
it will not Wipe your Data or internal storage
i6rb said:
try to Dirty flash the same Oxygen version
it will not Wipe your Data or internal storage
Click to expand...
Click to collapse
Thanks, i'll try this. Will I need to install TWRP again once I do this or is it unaffected?
Tried to dirty flash the same stock rom from TWRP but I don't think it did it properly. Can I dirty flash stock rom, flash magisk then try reboot to system?
Any help greatly appreciated.
I'm using a Custom Rom but when there-'s an update I download the new Rom, using OTA process. It enters in the recovery but I can't update it. What is wrong? If i Try making a dirty flash inside the recovery my Smartphone gets encripted. Can someone help me?
For many custom ROMs, the so-called OTA is just using recovery to dirty flash what OTA downloaded and everything should be Okay. I never found my data gets encrypted after the update. Maybe u could check the log if there's some update that needs a clean flash.
You had you rom flashed with DFE?
If yes you need to flash DFE zip after rom before booting.
Anyway it's supposed a rom encrypt data, but if recovery can't decrypt data you going for a bad time, last twrp has working decryption ...
Or you talking about something else?
Please provide more details....
As the first reply said, at least in the Roms I use, it just downloads the zip, reboots in twrp and flashes it. It worked pretty good in Havoc-Os
TioCareca said:
You had you rom flashed with DFE?
If yes you need to flash DFE zip after rom before booting.
Anyway it's supposed a rom encrypt data, but if recovery can't decrypt data you going for a bad time, last twrp has working decryption ...
Or you talking about something else?
Please provide more details....
Click to expand...
Click to collapse
I'l try to explain in details what my problem is.
I was on Havoc 4.8 and the 4.9 came out. I entered config, selected System and Update. It showed me the new Rom to download. That's what I did. It was downloaded perfectly and then asked me to continue. Só I pressed the button and it entered TWRP (35.2 Nebrasy) and there I was. Stopped in recovery and no other process was going on. Should I have chosen Install, the rom (probably in download folder)?
I was thinking it should have done the whole process autmaticaly, as it always did using Miui Rom.
So, that's my problem. Thanks for your help.
Fmeyen said:
I'l try to explain in details what my problem is.
I was on Havoc 4.8 and the 4.9 came out. I entered config, selected System and Update. It showed me the new Rom to download. That's what I did. It was downloaded perfectly and then asked me to continue. Só I pressed the button and it entered TWRP (35.2 Nebrasy) and there I was. Stopped in recovery and no other process was going on. Should I have chosen Install, the rom (probably in download folder)?
I was thinking it should have done the whole process autmaticaly, as it always did using Miui Rom.
So, that's my problem. Thanks for your help.
Click to expand...
Click to collapse
If your phone is not encrypted, then I don't think that the automatic OTA update (which uses an openrecovery script) will run. You will need to install the update manually, and your device will probably be encrypted when the ROM boots (unless you disable forced encryption).
DarthJabba9 said:
If your phone is not encrypted, then I don't think that the automatic OTA update (which uses an openrecovery script) will run. You will need to install the update manually, and your device will probably be encrypted when the ROM boots (unless you disable forced encryption).
Click to expand...
Click to collapse
When I install the new custom rom i usually flash DFE. So, by your words, it is not encrypted. If so, I'll run it manually as I prefer not to have an encrypted rom. Thanks for your support.
Could you please explain the correct steps to make a proper dirty flash in X3P? Asking this 'cause this smartphone needs a format data.