Develop Bugs

Can't decrypt my phone after installing oos nougats beta 8

After installing oos beta 8 nougats I made encryption and I made pin code but after restarting the phone when I write the pin code it gives me wrong pin and also gives me wrong pin when trying to open twrp , any solution please??

eid_elageeb said:
After installing oos beta 8 nougats I made encryption and I made pin code but after restarting the phone when I write the pin code it gives me wrong pin and also gives me wrong pin when trying to open twrp , any solution please??
Click to expand...
Click to collapse
You need modified TWRP 3.0.2-28 to get TWRP working with Beta 8. I had the same issue witrh my installation.

Also you need to make sure to remove your lock screen, then you will be able to use TWRP

strumaticjoker2 said:
Also you need to make sure to remove your lock screen, then you will be able to use TWRP
Click to expand...
Click to collapse
even without protection, twrp asking pw, need to erase use data and system.

I solved the problem by using oneplus 3 toolkit " Force Decryption Device" option and it works well, Thank you for your help guys

eid_elageeb said:
I solved the problem by using oneplus 3 toolkit " Force Decryption Device" option and it works well, Thank you for your help guys
Click to expand...
Click to collapse
I got the same issue, cannot decrypt the internal storage.
I am using TWRP3.0.2.1-28
What is your action, just run "Force Decryption Device" by using Toolkit v.3.6
and what recovery are you using ?
Thx

yiphoming said:
I got the same issue, cannot decrypt the internal storage.
I am using TWRP3.0.2.1-28
What is your action, just run "Force Decryption Device" by using Toolkit v.3.6
and what recovery are you using ?
Thx
Click to expand...
Click to collapse
First I flash the stock recovery by toolkit and then make force decryption device and then I flash twrp 3.0.2.1-28 and It works, but you should to know that everything on your phone will be erased

eid_elageeb said:
First I flash the stock recovery by toolkit and then make force decryption device and then I flash twrp 3.0.2.1-28 and It works, but you should to know that everything on your phone will be erased
Click to expand...
Click to collapse
No luck, can erase the storage, but it is still in encrypted.

yiphoming said:
No luck, can erase the storage, but it is still in encrypted.
Click to expand...
Click to collapse
I'm using latest modified TWRP 3.0.2-28 + OOS Beta 8. I have a protected lockscreen (fingerprint / pin) and pin is needed to start the device.
I flashed TWRP, wiped everything and changed "DATA" filesystem to "F2FS" and flashed the rom (clean installation)
I have full acces when using TWRP.
No need to force decryption or anything...

LS.xD said:
I'm using latest modified TWRP 3.0.2-28 + OOS Beta 8. I have a protected lockscreen (fingerprint / pin) and pin is needed to start the device.
I flashed TWRP, wiped everything and changed "DATA" filesystem to "F2FS" and flashed the rom (clean installation)
I have full acces when using TWRP.
No need to force decryption or anything...
Click to expand...
Click to collapse
It doesn't work though, if you installed dirty and just upgraded from MM. TWRP keeps asking for password and doesn't accept it, even if I change to password (else using PIN) in the system.

rarog said:
It doesn't work though, if you installed dirty and just upgraded from MM. TWRP keeps asking for password and doesn't accept it, even if I change to password (else using PIN) in the system.
Click to expand...
Click to collapse
I came from OOS 3.2.8 running already with F2FS and did a dirty flash to the Nougat Beta.
All with the -1.28 TWRP and have no issues going into TWRP and it accepts my pin.

AcmE85 said:
I came from OOS 3.2.8 running already with F2FS and did a dirty flash to the Nougat Beta.
All with the -1.28 TWRP and have no issues going into TWRP and it accepts my pin.
Click to expand...
Click to collapse
This is the way I went, just yet being on ext4. Could it be a difference, if you flash or if you just boot TWRP? I'm only booting instead of flashing, so I retain my recovery, as I didn't see the new Oxygen recovery for OOS4 in the wild yet.

rarog said:
This is the way I went, just yet being on ext4. Could it be a difference, if you flash or if you just boot TWRP? I'm only booting instead of flashing, so I retain my recovery, as I didn't see the new Oxygen recovery for OOS4 in the wild yet.
Click to expand...
Click to collapse
You probably need an older version for ext4. The last one working on ext4 when I did the switch to f2fs was -1.25 if I remember correctly.
After the switch to f2fs I had to flash 1.28 or the recovery wouldn't accept my pin anymore.
LS.xD said:
I'm using latest modified TWRP 3.0.2-28 + OOS Beta 8. I have a protected lockscreen (fingerprint / pin) and pin is needed to start the device.
I flashed TWRP, wiped everything and changed "DATA" filesystem to "F2FS" and flashed the rom (clean installation)
I have full acces when using TWRP.
No need to force decryption or anything...
Click to expand...
Click to collapse
Do you also get the dm-verity bootscreen?

AcmE85 said:
You probably need an older version for ext4. The last one working on ext4 when I did the switch to f2fs was -1.25 if I remember correctly.
After the switch to f2fs I had to flash 1.28 or the recovery wouldn't accept my pin anymore.
Click to expand...
Click to collapse
Hm... Interesting, do you have a link? And perhaps a link to a thread with all the available versions? I searched, but found only several tutorial threads with just one or another version linked, no thread for specific modified version.

AcmE85 said:
Do you also get the dm-verity bootscreen?
Click to expand...
Click to collapse
As far as I know - no.
When would this error message pop up?

LS.xD said:
As far as I know - no.
When would this error message pop up?
Click to expand...
Click to collapse
Right at boot before or after the screen which shows that the bootloader is unlocked.

AcmE85 said:
Right at boot before or after the screen which shows that the bootloader is unlocked.
Click to expand...
Click to collapse
No such error message for me

LS.xD said:
No such error message for me
Click to expand...
Click to collapse
Did you flash SuperSU?

AcmE85 said:
Did you flash SuperSU?
Click to expand...
Click to collapse
Yes, 2.78 SR5

I have done format userdata in fastboot but my phone still shows up as encrypted. Flashed 3.0.2-1.28 and I still get a password screen when booting to recovery. Not really sure what else I can do.

OnePlus3 Stuck on Logo When Booting

My problems started when I was on version 3.2.4 and could not update to 3.2.6 or 3.2.8, the update downloaded (OTA) and got stuck on the installation page after my phone rebooted. I previously has TWRP installed but uninstalled it before trying the OTA update and have again managed to install it. When I click "Install" in TWRP and look at /sdcard the folder is empty with the exception of a TWRP folder. I have tried to use adb sideload toOnePlus3Oxygen_16_OTA_008_all_1606122244_e0cfc5ffc8bf411a (cant link since this is my first post, sorry) but got an error 7. Any ideas on how I can fix this?

ng150716 said:
My problems started when I was on version 3.2.4 and could not update to 3.2.6 or 3.2.8, the update downloaded (OTA) and got stuck on the installation page after my phone rebooted. I previously has TWRP installed but uninstalled it before trying the OTA update and have again managed to install it. When I click "Install" in TWRP and look at /sdcard the folder is empty with the exception of a TWRP folder. I have tried to use adb sideload toOnePlus3Oxygen_16_OTA_008_all_1606122244_e0cfc5ffc8bf411a (cant link since this is my first post, sorry) but got an error 7. Any ideas on how I can fix this?
Click to expand...
Click to collapse
Sounds like your encrypted? Not sure what version of twrp you are on but this is the one that most have found luck with.

Ducter said:
Sounds like your encrypted? Not sure what version of twrp you are on but this is the one that most have found luck with.
Click to expand...
Click to collapse
If thats the case running the command fastboot oem lock
And then fastboot oem unlock will help to wipe everything and remove encryption

v.konvict said:
If thats the case running the command fastboot oem lock
And then fastboot oem unlock will help to wipe everything and remove encryption
Click to expand...
Click to collapse
Are you trying to get him into more trouble that he's already in?
Locking the bootloader while having custom recovery will result in a brick!
And there's no reason whatsoever to lock the bootloader on OP3 once it has been unlocked. Everything works with unlocked bootloader (including official OTA) so just keep it at that.
To remove encryption you have to format data partition - command: fastboot format userdata.
Sent from my OnePlus 3 using Tapatalk

Explorer23 said:
Are you trying to get him into more trouble that he's already in?
Locking the bootloader while having custom recovery will result in a brick!
And there's no reason whatsoever to lock the bootloader on OP3 once it has been unlocked. Everything works with unlocked bootloader (including official OTA) so just keep it at that.
To remove encryption you have to format data partition - command: fastboot format userdata.
Click to expand...
Click to collapse
Wierd coz it happened to me the other day. After i flashed unofficial recovery . so i did that and it wiped everything

v.konvict said:
Wierd coz it happened to me the other day. After i flashed unofficial recovery . so i did that and it wiped everything
Click to expand...
Click to collapse
Lucky guy then
But still, many people bricked their devices when they tried locking bootloader without stock recovery and ROM. Better not to push your luck, especially when there exist better ways of doing stuff (wiping internal storage in this case).
Sent from my OnePlus 3 using Tapatalk

[Official] [Recovery] TWRP for daisy

Hi all,
We've worked with TeamWin to get an official release of TWRP for daisy released, and here it is! We're sponsoring continued development of TWRP for daisy and other devices, so reach out to me if you have any questions.
I have to thank Dees_Troy & TeamWin for putting in the effort to make this available for us - donate here to support them directly.
So, without further ado, here's the download link. Here's a link to the source.
Please make sure you're on the factory image. If you aren't, the instructions to do that are here. You will lose your data and you'll have to set up your phone again.
1. Enable developer options (your bootloader should still be unlocked)
2. adb reboot bootloader
3. fastboot boot twrp-daisy-3.2.3-0.img
4. Hit "Cancel" if you're prompted for a decrypt password
5. adb push ./twrp-installer-daisy-3.2.3-0.zip /sdcard
6. Run the install in TWRP to permanently install TWRP across both slots
7. Reboot (you can reboot afterwards to TWRP to verify it is there)
Thanks all - and feel free to post your experiences, questions, comments, and concerns.
, Guava.

adb says "adb: usage: push requires an argument" after using first command.
thanks for the effort though!

tutankpusch said:
adb says "adb: usage: push requires an argument" after using first command.
thanks for the effort though!
Click to expand...
Click to collapse
Oops - ad "/sdcard" to the end of that command. Missed that. I'll update the OP.

I can't get past decryption, but I'll wait for a fixed version. Thanks for going to all this trouble!

KezraPlanes said:
I can't get past decryption, but I'll wait for a fixed version. Thanks for going to all this trouble!
Click to expand...
Click to collapse
Decryption is a Xiaomi issue...what do you mean by fixed version?

d1ngh said:
Decryption is a Xiaomi issue...what do you mean by fixed version?
Click to expand...
Click to collapse
So there's no fix? I can't have my phone secure at all? I thought this was a bug lol
TWRP encryption is how I ended up killing my Note 4X

d1ngh said:
Hi all,
We've worked with TeamWin to get an official release of TWRP for daisy released, and here it is! We're sponsoring continued development of TWRP for daisy and other devices, so reach out to me if you have any questions.
I have to thank Dees_Troy & TeamWin for putting in the effort to make this available for us - donate here to support them directly.
So, without further ado, here's the download link. Here's a link to the source.
Please make sure you're on the factory image. If you aren't, download the files here and run flash_all.sh, then go to recovery and factory reset. You will lose your data and you'll have to set yup your phone again.
1. Enable developer options (your bootloader should still be unlocked)
2. adb push ./twrp-installer-daisy-3.2.3-0.zip /sdcard
3. adb reboot bootloader
4. fastboot boot twrp-daisy-3.2.3-0.img
5. Run the install in TWRP to permanently install TWRP across both slots
6. Reboot (you can reboot afterwards to TWRP to verify it is there)
Thanks all - and feel free to post your experiences, questions, comments, and concerns.
Click to expand...
Click to collapse
How to install de TWRP inside TWRP.. im not finding the file.
And I used the command adb push...

KezraPlanes said:
So there's no fix? I can't have my phone secure at all? I thought this was a bug lol
TWRP encryption is how I ended up killing my Note 4X
Click to expand...
Click to collapse
Try adb push while TWRP is booted. It should get you past the pre-load issue.

actually there was an error when installing twrp.zip from twrp:
"E:recv error un uevent
Unable to find partition for path '/cache'"
but it seems everything is working fine

brunoliveh said:
How to install de TWRP inside TWRP.. im not finding the file.
And I used the command adb push...
Click to expand...
Click to collapse
When you're in the TWRP UI tap "Install" and select the twrp file you pushed (if you used the command above it should be in /sdcard)

tutankpusch said:
actually there was an error when installing twrp.zip from twrp:
"E:recv error un uevent
Unable to find partition for path '/cache'"
Click to expand...
Click to collapse
There isn't a cache partition on A/B devices, that error is fine.

d1ngh said:
Hi all,
We've worked with TeamWin to get an official release of TWRP for daisy released, and here it is! We're sponsoring continued development of TWRP for daisy and other devices, so reach out to me if you have any questions.
I have to thank Dees_Troy & TeamWin for putting in the effort to make this available for us - donate here to support them directly.
So, without further ado, here's the download link. Here's a link to the source.
Please make sure you're on the factory image. If you aren't, download the files here and run flash_all.sh, then go to recovery and factory reset. You will lose your data and you'll have to set yup your phone again.
1. Enable developer options (your bootloader should still be unlocked)
2. adb push ./twrp-installer-daisy-3.2.3-0.zip /sdcard
3. adb reboot bootloader
4. fastboot boot twrp-daisy-3.2.3-0.img
5. Run the install in TWRP to permanently install TWRP across both slots
6. Reboot (you can reboot afterwards to TWRP to verify it is there)
Thanks all - and feel free to post your experiences, questions, comments, and concerns.
Click to expand...
Click to collapse
using the updated command
failed to copy './twrp-installer-daisy-3.2.3-0.zip' to '/sdcard': couldn't create file: Is a directory

brunoliveh said:
using the updated command
failed to copy './twrp-installer-daisy-3.2.3-0.zip' to '/sdcard': couldn't create file: Is a directory
Click to expand...
Click to collapse
If there's already stuff there you'll need to specify the filename as well

Great news!
-Is full encryption working?
-I don't want to loose magisk... how can i preserve it?

d1ngh said:
Try adb push while TWRP is booted. It should get you past the pre-load issue.
Click to expand...
Click to collapse
Hey, that worked! And decryption works after a reboot. But now it's boot looping into TWRP? Did I lose all my data or is there a way to make it boot back into what was installed?
If I have to reinstall it's fine, but I'd like to know

KezraPlanes said:
Hey, that worked! And decryption works after a reboot. But now it's boot looping into TWRP? Did I lose all my data or is there a way to make it boot back into what was installed?
If I have to reinstall it's fine, but I'd like to know
Click to expand...
Click to collapse
That doesn't sound good. Did you factory reset after installing twrp? If so you will have lost data but the ROM should still be there.

d1ngh said:
That doesn't sound good. Did you factory reset after installing twrp? If so you will have lost data but the ROM should still be there.
Click to expand...
Click to collapse
I didn't. I was checking the file system and all my files are there. The ROM is the one who's gone lol.
Can I flash a GSI and have it working again?
Edit: Hooking up USB and I can access storage. Copying stuff over just in case.

KezraPlanes said:
I didn't. I was checking the file system and all my files are there. The ROM is the one who's gone lol.
Can I flash a GSI and have it working again?
Click to expand...
Click to collapse
I've been able to install TWRP before a GSI with relative ease but I couldn't get it to boot properly (phh-treble). I've also been able to install TWRP after a GSI and it works just fine. What GSI are you using? I might be able to test it out pretty quickly.

d1ngh said:
I've been able to install TWRP before a GSI with relative ease but I couldn't get it to boot properly (phh-treble). I've also been able to install TWRP after a GSI and it works just fine. What GSI are you using? I might be able to test it out pretty quickly.
Click to expand...
Click to collapse
I was using stock Android, just with Magisk. Didn't factory reset because I wasn't using a GSI and thought it wouldn't be a problem.
I'm asking if now I can just flash a GSI and have the phone up and running again. It seems storage and everything is there and working fine.

KezraPlanes said:
I was using stock Android, just with Magisk. Didn't factory reset because I wasn't using a GSI and thought it wouldn't be a problem.
I'm asking if now I can just flash a GSI and have the phone up and running again. It seems storage and everything is there and working fine.
Click to expand...
Click to collapse
Switch active slot
---------- Post added at 09:23 PM ---------- Previous post was at 09:23 PM ----------
KezraPlanes said:
I was using stock Android, just with Magisk. Didn't factory reset because I wasn't using a GSI and thought it wouldn't be a problem.
I'm asking if now I can just flash a GSI and have the phone up and running again. It seems storage and everything is there and working fine.
Click to expand...
Click to collapse
Try to Switch active slot

Reboot to recovery: "the system has been destroyed"

Hi
I followed this guide to root my son's phone
(the bootloader was already unlocked or so I tought - see below)
Now when I tried to reboot to twrp to root the phone, following these instructions in the guide:
“How To Root Mi A2 / A2 Lite Using Magisk
…
Now, boot your Xiaomi device into the TWRP Recovery Mode by pressing and holding the Volume Up and Power buttons simultaneously for a couple of seconds until the device starts booting.
…”
Click to expand...
Click to collapse
it does not boot to TWRP but instead displays a red error triangle with the message“The system has been destroyed”; I get exactly the same message after using the adb command
Code:
adb reboot recovery
as an alternative reboot-to-recovery method.
Reboot to system is perfectly fine!
Help anyone? Could it be the bootloader was not properly unlocked... I dit it when I received the phone and wa spretty sure it was unlocked then
Thanks

BenG7 said:
Hi
I followed this guide to root my son's phone
(the bootloader was already unlocked or so I tought - see below)
Now when I tried to reboot to twrp to root the phone, following these instructions in the guide:
it does not boot to TWRP but instead displays a red error triangle with the message“The system has been destroyed”; I get exactly the same message after using the adb command
as an alternative reboot-to-recovery method.
Reboot to system is perfectly fine!
Help anyone? Could it be the bootloader was not properly unlocked... I dit it when I received the phone and wa spretty sure it was unlocked then
Thanks
Click to expand...
Click to collapse
It's not a bootloader issue ,it is problem with the recovery.Use twrp 3.3.3-1-offain or 3.3.3-1dees_troy.

nikoman1987 said:
It's not a bootloader issue ,it is problem with the recovery.Use twrp 3.3.3-1-offain or 3.3.3-1dees_troy.
Click to expand...
Click to collapse
@nikoman1987: Thanks, so I suppose i should go thru the guide again, from the start, right? what is the difference between the offain and dees_troy twrps please?

BenG7 said:
@nikoman1987: Thanks, so I suppose i should go thru the guide again, from the start, right? what is the difference between the offain and dees_troy twrps please?
Click to expand...
Click to collapse
different developers ,i don't have any problems with the offain version.Some of the roms have priblems with dess-troy

nikoman1987 said:
It's not a bootloader issue ,it is problem with the recovery.Use twrp 3.3.3-1-offain or 3.3.3-1dees_troy.
Click to expand...
Click to collapse
exactly the same deal with:
twrp-daisy-3.3.0-0-offain
twrp-3.3.0-dees_troy-daisy
--> red error triangle with the message“The system has been destroyed”...

You need 3.3.1, not 3.3.0
dl.twrp.me/daisy
---------- Post added at 11:37 PM ---------- Previous post was at 11:35 PM ----------
You don't need to redo everything unless you failed to backup your boot image...

a1291762 said:
You need 3.3.1, not 3.3.0
dl.twrp.me/daisy
---------- Post added at 11:37 PM ---------- Previous post was at 11:35 PM ----------
You don't need to redo everything unless you failed to backup your boot image...
Click to expand...
Click to collapse
Hi again @a1291762
I already downloaded and flashed the official daisy twrp but that didn't do it, 3.3.0 it was.
On the official twrp.me website there is only Dees_troy version (true I didn't try 3.3.1 - will do so tonight) - no offain version.
Just wondering, I think I saw some command in some posts to allow flashing on the Mi A2 lite - would that be required here (although not stated in the guide I referenced)?
[EDIT] found this:
I am seeing the ‘System has been destroyed’ message after installing TWRP on Mi A2 Lite (daisy)?
Then download the ‘aboot.img’ from V9.6.4.0 (Download Link), boot your Mi A2 to Fastboot Mode and flash it using the following command:
Code:
fastboot flash aboot_a aboot_9.6.4.img
fastboot flash aboot_b aboot_9.6.4.img
According to the explanation given by XDA Senior Member mac12m99, the newer bootloader (aboot.img) version checks for stock recovery, even when the bootloader is unlocked. To overcome this, you can flash an older bootloader version (Especifically from V9.6.4.0) to fix this issue.
Click to expand...
Click to collapse

BenG7 said:
Hi again @a1291762
I already downloaded and flashed the official daisy twrp but that didn't do it, 3.3.0 it was.
On the official twrp.me website there is only Dees_troy version (true I didn't try 3.3.1 - will do so tonight) - no offain version.
Just wondering, I think I saw some command in some posts to allow flashing on the Mi A2 lite - would that be required here (although not stated in the guide I referenced)?
Click to expand...
Click to collapse
10.0.9.0 broke all the old twrps. Only 3.3.1 works now.
The official TWRP maintainer for daisy is dees troy.
Offain does the lineage ROM for daisy. I don't know how people get links to his TWRP. Search?
That guide looks ancient. TWRP and Magisk install guides can be found in this forum... I wrote a combined one (since having both complicates OTA) but if you're doing a custom ROM... It will depend.
Many custom ROMs want an encryption Disabler fix because they can't handle the encryption (which is on even if you don't have a password).
I've seen lots of surprise by people at the processes required for this phone. It was certainly different to what I've done before, but my last phone was pre-magisk and pre-A/B partitioning so I figured that's just how things are on newer phones.

a1291762 said:
10.0.9.0 broke all the old twrps. Only 3.3.1 works now.
The official TWRP maintainer for daisy is dees troy.
Offain does the lineage ROM for daisy. I don't know how people get links to his TWRP. Search?
That guide looks ancient. TWRP and Magisk install guides can be found in this forum... I wrote a combined one (since having both complicates OTA) but if you're doing a custom ROM... It will depend.
Many custom ROMs want an encryption Disabler fix because they can't handle the encryption (which is on even if you don't have a password).
I've seen lots of surprise by people at the processes required for this phone. It was certainly different to what I've done before, but my last phone was pre-magisk and pre-A/B partitioning so I figured that's just how things are on newer phones.
Click to expand...
Click to collapse
My build is 10.0.13.0

BenG7 said:
My build is 10.0.13.0
Click to expand...
Click to collapse
Then use 3.3.3-1 dees_troy or :
https://drive.google.com/file/d/1-Enw0Kn2CAYyfN1Krv8t3CVNLyn0p0JX/view?usp=drivesdk
Here is the link for twrp 3.3.3-1 offain version ,but it is in .img format.Dont install it via fastboot or TWRP .You can boot it via this command:
fasboot boot twrp-daisy-3.3.1-0-offain.img ,install everything you want,and you'll be ok ,if you don't need permanent twrp recovery!
If you want permanent installation - I am using Android All in One tool from another XDA thread and that's what i do:
Reboot in Fastboot mode,then connect the device to PC open the all-in-one tool on your windows computer ,then click on the "Recovery Flasher and Device Rooter" button(after you see that the device is recognised in the program) ,you need to choose which version- set it to MANUAL. From there navigate to the recovery files(dees_troy and offain) in the first row navigate to the recovery image (offain) ,on the second row navigate to the recovery zip (dees_troy).Then hit the Flash button. The phone will boot in 3.3.3-1 offain twrp ,and automatically will install the dees_troy version and when everything is installed,the phone will reboot after the flash again in recovery.All the time i have 100% success with this all in one tool. When you are ready with the installation of twrp ,flash magisk and reboot to system.
Here is the thread for the tool:
https://forum.xda-developers.com/mi...ol-one-driversunlocktwrpfactory-t3866191/amp/
I guarantee it works every time with 100% chance for success

nikoman1987 said:
Then use 3.3.3-1 dees_troy or :
https://drive.google.com/file/d/1-Enw0Kn2CAYyfN1Krv8t3CVNLyn0p0JX/view?usp=drivesdk
Here is the link for twrp 3.3.3-1 offain version ,but it is in .img format.Dont install it via fastboot or TWRP .You can boot it via this command:
fasboot boot twrp-daisy-3.3.1-0-offain.img ,install everything you want,and you'll be ok ,if you don't need permanent twrp recovery!
...
Here is the thread for the tool:
https://forum.xda-developers.com/mi...ol-one-driversunlocktwrpfactory-t3866191/amp/
I guarantee it works every time with 100% chance for success
Click to expand...
Click to collapse
Thanks @a1291762 & @nikoman1987 but the tool won't do it for me at home
I do not think I need permanent TWRP (although I know how nice it is to know you can always fall back to twrp - I will have to use a PC instead); my intention is to flash https://forum.xda-developers.com/mi-a2-lite/development/lineageos-16-0-xiaomi-mi-a2-lite-t3919060LineageOS with temporary twrp 3.3.3-1 offain version

BenG7 said:
Thanks @a1291762 & @nikoman1987 but the tool won't do it for me at home
I do not think I need permanent TWRP (although I know how nice it is to know you can always fall back to twrp - I will have to use a PC instead); my intention is to flash LineageOS with temporary twrp 3.3.3-1 offain version
Click to expand...
Click to collapse
Your choice , but I always prefer to have permanent twrp with custom ROMs . You know what's best for you.

a1291762 said:
10.0.9.0 broke all the old twrps. Only 3.3.1 works now.
The official TWRP maintainer for daisy is dees troy.
Offain does the lineage ROM for daisy. I don't know how people get links to his TWRP. Search?
That guide looks ancient. TWRP and Magisk install guides can be found in this forum... I wrote a combined one (since having both complicates OTA) but if you're doing a custom ROM... It will depend.
Many custom ROMs want an encryption Disabler fix because they can't handle the encryption (which is on even if you don't have a password).
I've seen lots of surprise by people at the processes required for this phone. It was certainly different to what I've done before, but my last phone was pre-magisk and pre-A/B partitioning so I figured that's just how things are on newer phones.
Click to expand...
Click to collapse
@a1291762
I got this message after formatting the data and wiping system, trying to install LO:
Code:
"Device unable to boot. Error - mdtp image is corrupted"
I am now stuck on fastboot!
From the post https://forum.xda-developers.com/nov...7#post80993947
I understand I have to flash BOOT/RECOVERY/SYSTEM imgs to restore your device;
the commands are
Boot:
Code:
fastboot flash boot boot.img
Recovery:
Code:
fastboot flash recovery recovery.img
System:
Code:
fastboot flash system system.img
but the question is where can I get the
boot.img
recovery.img
system.img
for the xiaomi Mi A2 Lite (daisy); bearing in mind the phone is on a 2 partition system?
Thanks a lot in advance

BenG7 said:
@a1291762
I got this message after formatting the data and wiping system, trying to install LO:
Code:
"Device unable to boot. Error - mdtp image is corrupted"
I am now stuck on fastboot!
From the post https://forum.xda-developers.com/nov...7#post80993947
I understand I have to flash BOOT/RECOVERY/SYSTEM imgs to restore your device;
Click to expand...
Click to collapse
There is no recovery image because this is an A/B partitioned phone.
The mdtp issue seems to be a real issue for some people.
https://forum.xda-developers.com/mi-a2-lite/help/device-unable-to-boot-error-mdtp-image-t3926962
The advice I gave there is all I can give here. Try to fastboot/MiFlash a stock ROM.
If you don't have a stock image, they're listed here:
https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
Note that the newest image is 10.0.13.0 (14, 15, 16 did not get full releases, just OTAs).
These threads suggest it's possible to flash a stock ROM to fix a corrupt mdtp partition...
https://forum.xda-developers.com/mi-a2-lite/help/fastboot-loop-t3996081
https://forum.xda-developers.com/mi-a2-lite/help/mi-a2-lite-stuck-fastboot-recovery-help-t3938175

a1291762 said:
There is no recovery image because this is an A/B partitioned phone.
The mdtp issue seems to be a real issue for some people.
https://forum.xda-developers.com/mi-a2-lite/help/device-unable-to-boot-error-mdtp-image-t3926962
The advice I gave there is all I can give here. Try to fastboot/MiFlash a stock ROM.
If you don't have a stock image, they're listed here:
https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
Note that the newest image is 10.0.13.0 (14, 15, 16 did not get full releases, just OTAs).
These threads suggest it's possible to flash a stock ROM to fix a corrupt mdtp partition...
https://forum.xda-developers.com/mi-a2-lite/help/fastboot-loop-t3996081
https://forum.xda-developers.com/mi-a2-lite/help/mi-a2-lite-stuck-fastboot-recovery-help-t3938175
Click to expand...
Click to collapse
Thanks @a1291762.
I
Code:
fastboot flash mdtp_a mdtp.img
fastboot flash mdtp_b mdtp.img
as instructed by @SubwayChamp in the link you posted
but the phone boots straight back to fastboot after
Code:
fastboot reboot
so I believe I need to flash a stock rom
I'm on Debian; I am wondering wether I can use
Can XiaoMiTool V2 unbrick my device?
to unbrick my phone or just
fastboot flash the daisy_global_images_V10.0.13.0.PDLMIXM_20190813.0000.00_9.0_5d0d486f04.tgz rom?
Please confirm the commands are:
Code:
fastboot -w
fastboot update </path/to/your/Rom.zip>
and it will work with a .tgz format or do I need to extract it and then zip it?
Thanks for your help

BenG7 said:
Thanks @a1291762.
I
Code:
fastboot flash mdtp_a mdtp.img
fastboot flash mdtp_b mdtp.img
as instructed by @SubwayChamp in the link you posted
but the phone boots straight back to fastboot after
Code:
fastboot reboot
so I believe I need to flash a stock rom
I'm on Debian; I am wondering wether I can use
Can XiaoMiTool V2 unbrick my device?
to unbrick my phone or just
fastboot flash the daisy_global_images_V10.0.13.0.PDLMIXM_20190813.0000.00_9.0_5d0d486f04.tgz rom?
Please confirm the commands are:
Code:
fastboot -w
fastboot update </path/to/your/Rom.zip>
and it will work with a .tgz format or do I need to extract it and then zip it?
Thanks for your help
Click to expand...
Click to collapse
Mdtp flashes returned your device to an state where partitions are readable again otherwise you won´t enter not even to recovery.
You don´t have to try to flash recovery (nor stock or custom), only reboot to a custom recovery like TWRP, the process to do it is well explained there, I also faced an mdtp issue and I didn´t need to flash the whole rom, just booted to TWRP and from there I did what I wanted, but if you yet want to do it.......
First of all I´m not familiar with Debian coming to modding smartphones, just I use it within other distros for other purposes.
The tool that you linked is not useful for us, this tool works mainly to fool recovery to accept modded scripts as original/signed and our device although it has a recovery image doesn´t have a dedicated partition and it simply is not available for the normal user, it´s mean that this tool uses MiRecovery present on all the devices running Miui out of the box but not for the others running Android One.
If you can access to a Windows machine this is the tool that I frequently use: https://xiaomifirmware.com/downloads/miflashpro/ but if you only can access to a PC with Debian probably this tool works for you https://forum.xda-developers.com/android/software/tool-miflash-linux-t3708847

BenG7 said:
daisy_global_images_V10.0.13.0.PDLMIXM_20190813.0000.00_9.0_5d0d486f04.tgz rom?
Please confirm the commands are:
Click to expand...
Click to collapse
You can't throw a .tgz or .zip at fastboot?!
If you're going to flash a stock ROM, extract it and run a flash_XXX script. It will use your fastboot to flash every partition. Variants preserve data or relock bootloader.

if fastboot fails (data transfer failure (too many links))
-> use a different USB port which is not a charging port.
-> try a different USB cable

Delete me

TWRP Recovery, Android 9 Pie

Warning! Warning! Warning!
All yours Data and files from internal storage will be lost. So make backup all what you need before continuing​
First read Bootloader Unlock and Root Instruction
So your bootloader is unlocked and you want TWRP-recovery on yours V35.
1. Download the necessary kernel
Boot+TWRPv3.3.1_only-V35-Pie-ULM20F.img - boot.img from latest V350ULM20f firmware
Boot+TWRPv3.3.1-V35-Pie-ULM20E.img - boot.img from V350ULM20e firmware
2. Flashing
a) Via Root: if you already have unlocked bootloader and root just copy downloaded f-or-e.img on internal sdcard, run CMD on PC and type
adb shell
su
dd if=/sdcard/_downloaded_.img of=/dev/block/bootdevice/by-name/boot_a
or
dd if=/sdcard/_downloaded_.img.img of=/dev/block/bootdevice/by-name/boot_b
reboot recovery
b) Via Qfil: all you need to know is here Bootloader Unlock and Root Instruction
3. Go to recovery ( via buttons or adb reboot recovery )
In recovery you will see a message that the data is encrypted and you need a password, which you not have.
Click cancel, agree to change system files.
In main menu click Install and select attached file Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip
In Wipe menu swipe right, then go back, Format Data - type "yes"
Install latest Magisk.zip
Reboot - System
Done!

Edit:
New Instructions in English: https://github.com/kaneorotar/LG-V35-Tinkering-Instructions/blob/master/README_EN.MD
Original:
I see that you are using my TWRP build.
Here is my original instructions (mainly in Chinese but has enough English to make sense): https://github.com/kaneorotar/LG-V35-Tinkering-Instructions

Yes, you are right. I just patched boot.img

thanks, it worked perfectly for me.

Thanks a lot, not a lot of development and love on this device, I just wanted to say some of us really appreciate this.

SaiLas said:
Warning! Warning! Warning!
All yours Data and files from internal storage will be lost. So make backup all what you need before continuing​
First read Bootloader Unlock and Root Instruction
So your bootloader is unlocked and you want TWRP-recovery on yours V35.
1. Download the necessary kernel
Boot+TWRPv3.3.1_only-V35-Pie-ULM20F.img - boot.img from latest V350ULM20f firmware
Boot+TWRPv3.3.1-V35-Pie-ULM20E.img - boot.img from V350ULM20e firmware
2. Flashing
a) Via Root: if you already have unlocked bootloader and root just copy downloaded f-or-e.img on internal sdcard, run CMD on PC and type
adb shell
su
dd if=/sdcard/_downloaded_.img of=/dev/block/bootdevice/by-name/boot_a
or
dd if=/sdcard/_downloaded_.img.img of=/dev/block/bootdevice/by-name/boot_b
reboot recovery
b) Via Qfil: all you need to know is here Bootloader Unlock and Root Instruction
3. Go to recovery ( via buttons or adb reboot recovery )
In recovery you will see a message that the data is encrypted and you need a password, which you not have.
Click cancel, agree to change system files.
In main menu click Install and select attached file Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip
In Wipe menu swipe right, then go back, Format Data - type "yes"
Install latest Magisk.zip
Reboot - System
Done!
Click to expand...
Click to collapse
Can bootloader be unlocked on ATT V35 V350AWM I can't find it anywhere? There seems to be some talk it cannot be done?

What's the benefit without ROM's for rooting your phone? Magisk modules?

notanymore said:
Can bootloader be unlocked on ATT V35 V350AWM I can't find it anywhere? There seems to be some talk it cannot be done?
Click to expand...
Click to collapse
https://forum.xda-developers.com/lg-v35/development/bootloader-unlock-root-instruction-t4052145

SaiLas said:
https://forum.xda-developers.com/lg-v35/development/bootloader-unlock-root-instruction-t4052145
Click to expand...
Click to collapse
Hey thanks!

X-Nemesis said:
What's the benefit without ROM's for rooting your phone? Magisk modules?
Click to expand...
Click to collapse
Yes. On my V30 I've never installed a custom ROM. Rooted stock firmware when the TWRP custom recovery (gift by itself for backups), Magisk mods, Xposed mods. You can tweak yourself without having to install a ROM.

During flashing, you may see error messages about 'unable to unmount vendor'. This is fine as long as the zip flashing doesn't fail halfway.
Click to expand...
Click to collapse
realllllllllllly important. I kept getting unable to mount xx (one of vendor system systemroot randomly) and didn't notice it meant the magisk sticked until I gave up and was ready to settle with no twrp.

YUP
notanymore said:
Can bootloader be unlocked on ATT V35 V350AWM I can't find it anywhere? There seems to be some talk it cannot be done?
Click to expand...
Click to collapse

SaiLas said:
Yes, you are right. I just patched boot.img
Click to expand...
Click to collapse
links dont work
Boot+TWRPv3.3.1_only-V35-Pie-ULM20F.img - boot.img from latest V350ULM20f firmware

SaiLas said:
https://forum.xda-developers.com/lg-v35/development/bootloader-unlock-root-instruction-t4052145
Click to expand...
Click to collapse
after flashing twrp on a/b, Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip (http://Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip), and Magisk, my v35 wont boot, it got stuck on LG logo, I can go back to TWRP.
Is there any kernel, boot img I have to flash it? Im on this V350ULM20f_00_NAO_US_OP_0218.kdz Pie build

zfk110 said:
after flashing twrp on a/b, Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip (http://Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip), and Magisk, my v35 wont boot, it got stuck on LG logo, I can go back to TWRP.
Is there any kernel, boot img I have to flash it? Im on this V350ULM20f_00_NAO_US_OP_0218.kdz Pie build
Click to expand...
Click to collapse

Did you wipe your data after flashing the files?
The same happened to me once, I solved that by flashing via upgrade the stock firmware, and then re-rooted.

Excelstar said:
Did you wipe your data after flashing the files?
The same happened to me once, I solved that by flashing via upgrade the stock firmware, and then re-rooted.
Click to expand...
Click to collapse
I just went back to TWRP and used his boot.img to flash within TWRP to boot's partition and then I was able to boot without any issues, I was thinking the same, but it looked more work to do.

kaneorotar said:
Edit:
New Instructions in English: https://github.com/kaneorotar/LG-V35-Tinkering-Instructions/blob/master/README_EN.MD
Original:
I see that you are using my TWRP build.
Here is my original instructions (mainly in Chinese but has enough English to make sense): https://github.com/kaneorotar/LG-V35-Tinkering-Instructions
Click to expand...
Click to collapse
Just wanted to say thanks for the updated instructions. Worked like a charm.

Hello, can you help me with the TWRP file for the LG V350AWM?