Database Develop

Need help with Me176c, fastboot.... 123# screen

My Asus memo pad 7 is stuck on fastboot.... 123# screen. I've tried temporary recovery and had success installation with lineage-14.1 but nothing changed. Please help. Thanks.

Did you have Lollipop installed before?
Also, do I understand it correctly that you're able to get into the temp recovery session?

Yes lollipop was installed and rooted long time ago, after the issue I decided to put it away. I did loads after that though, so I don't think lollipop is still there.
It was first at boot screen, got this fastboot... 123# after I flashed a fastboot image. Flashed loads of recoveries, systems and boot images before and after the fastboot issue.
Hope this helps you understand the state it's in. Thanks for replying.

MJMJ7 said:
Yes lollipop was installed and rooted long time ago, after the issue I decided to put it away. I did loads after that though, so I don't think lollipop is still there.
It was first at boot screen, got this fastboot... 123# after I flashed a fastboot image. Flashed loads of recoveries, systems and boot images before and after the fastboot issue.
Hope this helps you understand the state it's in. Thanks for replying.
Click to expand...
Click to collapse
If the tablet boots into the screen with the 3 fastboot lines you are in DNX mode, which means you've likely messed up your bootloader. To restore the bootloader, follow the steps outlined in https://forum.xda-developers.com/showpost.php?p=73672837&postcount=5
If everything works, you should get to a second Fastboot screen with NORMAL BOOT etc. From there you can either start the temporary TWRP recovery session (see https://forum.xda-developers.com/showpost.php?p=73673438&postcount=7) to flash the Lollipop package you've downloaded earlier (UL-K013-WW-12.10.1.36-user.zip) or flash LineageOS.
If you want to flash LineageOS you need to unlock your bootloader. Download https://www.androidfilehost.com/?fid=312978532265362065, take the ESP.img from the ZIP and download https://github.com/me176c-dev/devic...recovery-3.1.1-20171119-UNOFFICIAL-me176c.img. Then run:
Code:
fastboot flash ESP ESP.img
fastboot flash recovery twrp-recovery-3.1.1-20171119-UNOFFICIAL-me176c.img
Power off your device, then press Volume Down + Power. Intel logo should show up, and ask if you want to go into recovery or fastboot. Go into recovery using Volume Down. Do a Factory reset again (it's under Wipe), then flash https://github.com/me176c-dev/devic...ge-14.1-20171119-UNOFFICIAL-me176c-signed.zip (e.g. put it on your external SD).

I will try these steps and update you. Thank you very much.

O yes! It worked. Tablet is now back in operation on lineageos. Going and get Gapps now. Thanks a lot lambdadroid

I believe my work on this tablet is not complete as I can't install Gapps. Installation failing every time. So I tried to reinstall lineage as this was installed before when I was trying all sorts to fix it.
Then when I followed the procedures you sent me, it booted into lineage after I unlocked the bootloader and installed twrp. So the system still had lineage from my fastboot installation attempts. What I can install now is the original version (ul k013 ww-12.10.1.36-user) and that works but I don't want this.
Any help on getting lineage to complete the installation? as it gets to the end with a little to go hut just never finishes (left this overnight)
Thanks.

lambdadroid said:
If the tablet boots into the screen with the 3 fastboot lines you are in DNX mode, which means you've likely messed up your bootloader. To restore the bootloader, follow the steps outlined in https://forum.xda-developers.com/showpost.php?p=73672837&postcount=5
If everything works, you should get to a second Fastboot screen with NORMAL BOOT etc. From there you can either start the temporary TWRP recovery session (see https://forum.xda-developers.com/showpost.php?p=73673438&postcount=7) to flash the Lollipop package you've downloaded earlier (UL-K013-WW-12.10.1.36-user.zip) or flash LineageOS.
If you want to flash LineageOS you need to unlock your bootloader. Download https://www.androidfilehost.com/?fid=312978532265362065, take the ESP.img from the ZIP and download https://github.com/me176c-dev/devic...recovery-3.1.1-20171119-UNOFFICIAL-me176c.img. Then run:
Code:
fastboot flash ESP ESP.img
fastboot flash recovery twrp-recovery-3.1.1-20171119-UNOFFICIAL-me176c.img
Power off your device, then press Volume Down + Power. Intel logo should show up, and ask if you want to go into recovery or fastboot. Go into recovery using Volume Down. Do a Factory reset again (it's under Wipe), then flash https://github.com/me176c-dev/devic...ge-14.1-20171119-UNOFFICIAL-me176c-signed.zip (e.g. put it on your external SD).
Click to expand...
Click to collapse
I believe my work on this tablet is not complete as I can't install Gapps. Installation failing every time. So I tried to reinstall lineage as this was installed before when I was trying all sorts to fix it.
Then when I followed the procedures you sent me, it booted into lineage after I unlocked the bootloader and installed twrp. So the system still had lineage from my fastboot installation attempts. What I can install now is the original version (ul k013 ww-12.10.1.36-user) and that works but I don't want this.
Any help on getting lineage to complete the installation? as it gets to the end with a little to go hut just never finishes (left this overnight)
Thanks.

MJMJ7 said:
I believe my work on this tablet is not complete as I can't install Gapps. Installation failing every time. So I tried to reinstall lineage as this was installed before when I was trying all sorts to fix it.
Then when I followed the procedures you sent me, it booted into lineage after I unlocked the bootloader and installed twrp. So the system still had lineage from my fastboot installation attempts. What I can install now is the original version (ul k013 ww-12.10.1.36-user) and that works but I don't want this.
Any help on getting lineage to complete the installation? as it gets to the end with a little to go hut just never finishes (left this overnight)
Thanks.
Click to expand...
Click to collapse
No need to reply twice.
Please clarify: What exactly is failing? The LineageOS ZIP or the OpenGApps ZIP? Do you get an error during installation or does it never finish the boot after installation?
Things you can try: Check TWRP log for errors (usually marked red if you click the bottom right button in TWRP). Try a factory reset in TWRP.

lambdadroid said:
No need to reply twice.
Please clarify: What exactly is failing? The LineageOS ZIP or the OpenGApps ZIP? Do you get an error during installation or does it never finish the boot after installation?
Things you can try: Check TWRP log for errors (usually marked red if you click the bottom right button in TWRP). Try a factory reset in TWRP.
Click to expand...
Click to collapse
Just thought you wouldn't be notified if I don't quote.
The gapps file is giving an error and failing, the lineageOS just stalls and never complete the installation.
I will try again now.....

patching system image unconditionally....
This is going on and on, about 10% left to complete but it never does. LineageOS installation.
Updater process ended with ERROR: 1
Error installing zip file '/external_sd/0-System zips/
Asus Memo pad 7 K013/gapps 7.1.zip'
And that's what I'm getting from the gapps installation.
Installation failed.

Got the Gapps to install, had to choose x86 version. Still no improvement from lineage.

MJMJ7 said:
patching system image unconditionally....
This is going on and on, about 10% left to complete but it never does. LineageOS installation.
Updater process ended with ERROR: 1
Error installing zip file '/external_sd/0-System zips/
Asus Memo pad 7 K013/gapps 7.1.zip'
And that's what I'm getting from the gapps installation.
Installation failed.
Click to expand...
Click to collapse
Maybe the file wasn't downloaded/copied properly. Enable ZIP file signature verification in the TWRP settings and flash the LineageOS package again. Does it print "Zip signature verified successfully"?

lambdadroid said:
Maybe the file wasn't downloaded/copied properly. Enable ZIP file signature verification in the TWRP settings and flash the LineageOS package again. Does it print "Zip signature verified successfully"?
Click to expand...
Click to collapse
Did it again with another copy and enabled the verification and all came out successfully. Thanks for your help.:good:

TWRP asking for password for Decrypt Data on (8.1) international global rom

Hello guys,
just wanna asking again,.. I was going to flash magisk on red magic. I already succeed in flashing the TWRP. But, unfortunately, the TWRP was asking for a password to Decrypt Data...
Does anyone know the solution for this?
I already try to put pin on android and use it on TWRP still no luck here. Is there is a way to decrypt the phone from the system itself??
any suggestions will be great :fingers-crossed:

ianseer said:
Hello guys,
just wanna asking again,.. I was going to flash magisk on red magic. I already succeed in flashing the TWRP. But, unfortunately, the TWRP was asking for a password to Decrypt Data...
Does anyone know the solution for this?
I already try to put pin on android and use it on TWRP still no luck here. Is there is a way to decrypt the phone from the system itself??
any suggestions will be great :fingers-crossed:
Click to expand...
Click to collapse
Flash official recovery from twrp website. If I remember right it will work. But change language to English

If you haven't already find solution you must do factory reset through twrp option to unlock it ,of course this action will wipe all your data.

strakell said:
If you haven't already find solution you must do factory reset through twrp option to unlock it ,of course this action will wipe all your data.
Click to expand...
Click to collapse
Data partition he needs to wipe.

ianseer said:
Hello guys,
just wanna asking again,.. I was going to flash magisk on red magic. I already succeed in flashing the TWRP. But, unfortunately, the TWRP was asking for a password to decrypt Data...
Does anyone know the solution for this?
I already try to put pin on android and use it on TWRP still no luck here. Is there is a way to decrypt the phone from the system itself??
any suggestions will be great :fingers-crossed:
Click to expand...
Click to collapse
1. You need to go in boot-loader mode: VOL DOWN and POWER - preferable from power off state and when logo appear release buttons.
2. unlock boot-loader (every time is needed if you want to modify recovery or anything else)
3. install original international recovery: http://www.mediafire.com/file/s3dyqlhsytsflpd/recovery-114.img/file
4. restart in RECOVERY...now you see original recovery : choose English and go and wipe USER DATA (!!!!!!IT WILL ERASE EVERYTHING, ANY IMG< MP# < EVERYTHING FROM INTERNAL MEMORY and DECRYPT IT !!!!!),
erase also cache!!!!!
5. Power OFF
6. Unlock boot-loader (yes, again!)
7. install TWRP 3.3.1 : http://www.mediafire.com/file/nsu9nr0pdknruxw/recovery-331.img/file
8. Boot into TWRP Recovery
9. now install "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip" : http://www.mediafire.com/file/hquo5qjoi45hy9c/Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip/file
In this way you will decrypt your phone and prevent to encrypt it again on reboot. If you don't Disable verity and force encrypt phone will re-encrypt itself on reboot because Vendor partition contain settings to encrypt data. There is a chance that after step 8 you will need to reinstall original international ROM ver. 114 and immediately after that the "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip"
After reboot successfully (and no encrypting data) go back to TWRP and flash the last magisk.
....If you want to try something else: Download the Resurrection Remix 8. 1, version 64 bit A only gapps from here: https://forum.xda-developers.com/project-treble/trebleenabled-device-development/resurrection-remix-phh-treble-t3767688
This one I found that is working also gapss.
You can find also other ROM (as system image!) here:
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-%28GSI%29-list ,
or here:
https://forum.xda-developers.com/project-treble/trebleenabled-device-development
About treble experimentation here: https://github.com/phhusson/treble_experimentations/wiki/Frequently-asked-questions-%28FAQ%29
For example I like the DESCENDANT 3.1.1 : https://forum.xda-developers.com/project-treble/trebleenabled-device-development/descendant-android-pie-custom-rom-ver-t3840578 but I can not make working gapps on it....till now at least
So, I think i have opened your appetite!
have fun!

ABM30 said:
1. You need to go in boot-loader mode: VOL DOWN and POWER - preferable from power off state and when logo appear release buttons.
2. unlock boot-loader (every time is needed if you want to modify recovery or anything else)
3. install original international recovery: http://www.mediafire.com/file/s3dyqlhsytsflpd/recovery-114.img/file
4. restart in RECOVERY...now you see original recovery : choose English and go and wipe USER DATA (!!!!!!IT WILL ERASE EVERYTHING, ANY IMG< MP# < EVERYTHING FROM INTERNAL MEMORY and DECRYPT IT !!!!!),
erase also cache!!!!!
5. Power OFF
6. Unlock boot-loader (yes, again!)
7. install TWRP 3.3.1 : http://www.mediafire.com/file/nsu9nr0pdknruxw/recovery-331.img/file
8. Boot into TWRP Recovery
9. now install "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip" : http://www.mediafire.com/file/hquo5qjoi45hy9c/Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip/file
In this way you will decrypt your phone and prevent to encrypt it again on reboot. If you don't Disable verity and force encrypt phone will re-encrypt itself on reboot because Vendor partition contain settings to encrypt data. There is a chance that after step 8 you will need to reinstall original international ROM ver. 114 and immediately after that the "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip"
After reboot successfully (and no encrypting data) go back to TWRP and flash the last magisk.
....If you want to try something else: Download the Resurrection Remix 8. 1, version 64 bit A only gapps from here: https://forum.xda-developers.com/pr...opment/resurrection-remix-phh-treble-t3767688
This one I found that is working also gapss.
You can find also other ROM (as system image!) here:
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list ,
or here:
https://forum.xda-developers.com/project-treble/trebleenabled-device-development
About treble experimentation here: https://github.com/phhusson/treble_experimentations/wiki/Frequently-asked-questions-(FAQ)
For example I like the DESCENDANT 3.1.1 : https://forum.xda-developers.com/pr...escendant-android-pie-custom-rom-ver-t3840578 but I can not make working gapps on it....till now at least
So, I think i have opened you appetite!
have fun!
Click to expand...
Click to collapse
Does the songs are getting played into the gsi? Treble GSI have issues like overheating and no sound while playing music. Means no ringtones either. I had put logs for phh but he didn't worked as he is busy. As all gsi uses phh base and fixes, the issues are same across the gsi.
Plus- in pie Chinese vendor the treble support is gone. So no more treble in pie update. Only we have legacy support on 8.1.
I had tried to work onto updating Omni but my motherboard went down. It got burnt. You know how to cook ROMs right ! Why don't you try?
Plus the latest gsi no longer boot idk the reasons with the July updates. Reply to me I am trying to donate a device to anyone who can work on this phone

ABM30 said:
1. You need to go in boot-loader mode: VOL DOWN and POWER - preferable from power off state and when logo appear release buttons.
2. unlock boot-loader (every time is needed if you want to modify recovery or anything else)
3. install original international recovery: http://www.mediafire.com/file/s3dyqlhsytsflpd/recovery-114.img/file
4. restart in RECOVERY...now you see original recovery : choose English and go and wipe USER DATA (!!!!!!IT WILL ERASE EVERYTHING, ANY IMG< MP# < EVERYTHING FROM INTERNAL MEMORY and DECRYPT IT !!!!!),
erase also cache!!!!!
5. Power OFF
6. Unlock boot-loader (yes, again!)
7. install TWRP 3.3.1 : http://www.mediafire.com/file/nsu9nr0pdknruxw/recovery-331.img/file
8. Boot into TWRP Recovery
9. now install "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip" : http://www.mediafire.com/file/hquo5qjoi45hy9c/Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip/file
In this way you will decrypt your phone and prevent to encrypt it again on reboot. If you don't Disable verity and force encrypt phone will re-encrypt itself on reboot because Vendor partition contain settings to encrypt data. There is a chance that after step 8 you will need to reinstall original international ROM ver. 114 and immediately after that the "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip"
After reboot successfully (and no encrypting data) go back to TWRP and flash the last magisk.
....If you want to try something else: Download the Resurrection Remix 8. 1, version 64 bit A only gapps from here: https://forum.xda-developers.com/pr...opment/resurrection-remix-phh-treble-t3767688
This one I found that is working also gapss.
You can find also other ROM (as system image!) here:
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list ,
or here:
https://forum.xda-developers.com/project-treble/trebleenabled-device-development
About treble experimentation here: https://github.com/phhusson/treble_experimentations/wiki/Frequently-asked-questions-(FAQ)
For example I like the DESCENDANT 3.1.1 : https://forum.xda-developers.com/pr...escendant-android-pie-custom-rom-ver-t3840578 but I can not make working gapps on it....till now at least
So, I think i have opened you appetite!
have fun!
Click to expand...
Click to collapse
You answering all of my question very nice and clear... Yes i will having fun next week, i hope... (Still in other city now, i need my phone)... But, when the time comes, i will try it and post the update here... big thanks, Appriciate it... Yes i'm hungry now

methuselah said:
Does the songs are getting played into the gsi? Treble GSI have issues like overheating and no sound while playing music. Means no ringtones either. I had put logs for phh but he didn't worked as he is busy. As all gsi uses phh base and fixes, the issues are same across the gsi.
Plus- in pie Chinese vendor the treble support is gone. So no more treble in pie update. Only we have legacy support on 8.1.
I had tried to work onto updating Omni but my motherboard went down. It got burnt. You know how to cook ROMs right ! Why don't you try?
Plus the latest gsi no longer boot idk the reasons with the July updates. Reply to me I am trying to donate a device to anyone who can work on this phone
Click to expand...
Click to collapse
If only i can help you guys out cooking the rom... I'm only animator and designer... Not chef programmer or coder

methuselah said:
Does the songs are getting played into the gsi? Treble GSI have issues like overheating and no sound while playing music. Means no ringtones either. I had put logs for phh but he didn't worked as he is busy. As all gsi uses phh base and fixes, the issues are same across the gsi.
Plus- in pie Chinese vendor the treble support is gone. So no more treble in pie update. Only we have legacy support on 8.1.
I had tried to work onto updating Omni but my motherboard went down. It got burnt. You know how to cook ROMs right ! Why don't you try?
Plus the latest gsi no longer boot idk the reasons with the July updates. Reply to me I am trying to donate a device to anyone who can work on this phone
Click to expand...
Click to collapse
YES, at this moment sound is a problem in GSI ROMs. In call you have sound but not in media.
I am still looking for solutions.

ABM30 said:
YES, at this moment sound is a problem in GSI ROMs. In call you have sound but not in media.
I am still looking for solutions.
Click to expand...
Click to collapse
There are logs on phh thread about sound and other issues on gsi. Take a look if you have any knowledge. You don't need to take logs again I guess. But new GSI don't even boot last time this month when I checked. Maybe I was wrong.
It's just my point of view. You should try to bring up lineageOs with Omni sources coz lot of developers are there to help you if you have knowledge. The device tress are there from Omni. Well 8.1 is still there as lineageOs is still updating and giving security fixes. And most of commits are there for ok our phones in Omni GitHub.

ABM30 said:
1. You need to go in boot-loader mode: VOL DOWN and POWER - preferable from power off state and when logo appear release buttons.
2. unlock boot-loader (every time is needed if you want to modify recovery or anything else)
3. install original international recovery: http://www.mediafire.com/file/s3dyqlhsytsflpd/recovery-114.img/file
4. restart in RECOVERY...now you see original recovery : choose English and go and wipe USER DATA (!!!!!!IT WILL ERASE EVERYTHING, ANY IMG< MP# < EVERYTHING FROM INTERNAL MEMORY and DECRYPT IT !!!!!),
erase also cache!!!!!
5. Power OFF
6. Unlock boot-loader (yes, again!)
7. install TWRP 3.3.1 : http://www.mediafire.com/file/nsu9nr0pdknruxw/recovery-331.img/file
8. Boot into TWRP Recovery
9. now install "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip" : http://www.mediafire.com/file/hquo5qjoi45hy9c/Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip/file
In this way you will decrypt your phone and prevent to encrypt it again on reboot. If you don't Disable verity and force encrypt phone will re-encrypt itself on reboot because Vendor partition contain settings to encrypt data. There is a chance that after step 8 you will need to reinstall original international ROM ver. 114 and immediately after that the "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip"
After reboot successfully (and no encrypting data) go back to TWRP and flash the last magisk.
....If you want to try something else: Download the Resurrection Remix 8. 1, version 64 bit A only gapps from here: https://forum.xda-developers.com/project-treble/trebleenabled-device-development/resurrection-remix-phh-treble-t3767688
This one I found that is working also gapss.
You can find also other ROM (as system image!) here:
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-%28GSI%29-list ,
or here:
https://forum.xda-developers.com/project-treble/trebleenabled-device-development
About treble experimentation here: https://github.com/phhusson/treble_experimentations/wiki/Frequently-asked-questions-%28FAQ%29
For example I like the DESCENDANT 3.1.1 : https://forum.xda-developers.com/project-treble/trebleenabled-device-development/descendant-android-pie-custom-rom-ver-t3840578 but I can not make working gapps on it....till now at least
So, I think i have opened your appetite!
have fun!
Click to expand...
Click to collapse
Hello, me again...
I'm trying to do the method that you've explained...
there's a new problem... right now, already try to connect my phone to USB on pc, it always says "USB supplying power on attached device" even for fastboot mode it doesn't work the computer still not recognize anything.. already tried different computer, already tried different cables too... no luck...
Now, I can go to emergency recovery with stock nicely but cannot go to the usual recovery cuz i already installed twrp but the phone itself is encrypted device so nothing to do there, I'm thinking about wiping userdata from emergency recovery,... is it okay to do this? cuz maybe I'm thinking after I wiping the userdata and everything I can get my USB connection again (cuz before i've had similar issue but after install new rom it's working nicely almost with every cable),... what do u guys think? thanks in advance

ianseer said:
Hello, me again...
I'm trying to do the method that you've explained...
there's a new problem... right now, already try to connect my phone to USB on pc, it always says "USB supplying power on attached device" even for fastboot mode it doesn't work the computer still not recognize anything.. already tried different computer, already tried different cables too... no luck...
Now, I can go to emergency recovery with stock nicely but cannot go to the usual recovery cuz i already installed twrp but the phone itself is encrypted device so nothing to do there, I'm thinking about wiping userdata from emergency recovery,... is it okay to do this? cuz maybe I'm thinking after I wiping the userdata and everything I can get my USB connection again (cuz before i've had similar issue but after install new rom it's working nicely almost with every cable),... what do u guys think? thanks in advance
Click to expand...
Click to collapse
Well, if you are encrypted you will need to uncrypt your phone.
!!!!!!!But you will lose everithing saved in internal memory!!!!!!!!
Just follow steps 1 to 8 from my previous guide. Then you can reinstall the ROM. If you will install International ROM you will get encrypted again if you don't run Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip right after installing ROM in TWRP!!!!!!!
Wiping everything with original recovery is the best way to clear your phone!!! sometimes is mandatory this, even with advanced wipe in TWRP you wont achieve what you can with original recovery wipe!

Back to report...
Already finished all the things need to be done... and ABM30 method is working nicely.... now, I can enjoy all the root goodness in my red magic with original global rom.
really this is what I'm looking for... Thanks a lot.
Ps: just wanna share for the USB to pc connectivity problems: what I did was connect it on fastboot mode, and do fastboot command for unlocking your red magic.... wait around 5 min, unplug it if nothing happens, plug it again and wait again (until many times), after that you will see your fastboot command from wait mode into something successful... (i dunno why).
and then do reflash the recovery...
for the resurrection remix, I will try it and post it on new thread.... seems interesting

ianseer said:
Back to report...
Already finished all the things need to be done... and ABM30 method is working nicely.... now, I can enjoy all the root goodness in my red magic with original global rom.
really this is what I'm looking for... Thanks a lot.
Ps: just wanna share for the USB to pc connectivity problems: what I did was connect it on fastboot mode, and do fastboot command for unlocking your red magic.... wait around 5 min, unplug it if nothing happens, plug it again and wait again (until many times), after that you will see your fastboot command from wait mode into something successful... (i dunno why).
and then do reflash the recovery...
for the resurrection remix, I will try it and post it on new thread.... seems interesting
Click to expand...
Click to collapse
Why are flashing without any output. Flash phh treble and help in sorting out bugs.

methuselah said:
Why are flashing without any output. Flash phh treble and help in sorting out bugs.
Click to expand...
Click to collapse
I will... btw, do u know if we in treble. what happened with led strip on the back? is it only for notification? or turned off completely?

ianseer said:
I will... btw, do u know if we in treble. what happened with led strip on the back? is it only for notification? or turned off completely?
Click to expand...
Click to collapse
well it doesn't work. It's a part of kernel I guess. There are no sounds from loudspeaker. and there are huge issues with pie in phh treble. He needs logs for that. You can't even login into the google account. There are logs with on treble Phh thread. August images are there. Start taking logs after reading the thread. You will be happy to help him.

ianseer said:
I will... btw, do u know if we in treble. what happened with led strip on the back? is it only for notification? or turned off completely?
Click to expand...
Click to collapse
Did you posted any log?

ABM30 said:
1. You need to go in boot-loader mode: VOL DOWN and POWER - preferable from power off state and when logo appear release buttons.
2. unlock boot-loader (every time is needed if you want to modify recovery or anything else)
3. install original international recovery: [url]http://www.mediafire.com/file/s3dyqlhsytsflpd/recovery-114.img/file[/URL]
4. restart in RECOVERY...now you see original recovery : choose English and go and wipe USER DATA (!!!!!!IT WILL ERASE EVERYTHING, ANY IMG< MP# < EVERYTHING FROM INTERNAL MEMORY and DECRYPT IT !!!!!),
erase also cache!!!!!
5. Power OFF
6. Unlock boot-loader (yes, again!)
7. install TWRP 3.3.1 : [url]http://www.mediafire.com/file/nsu9nr0pdknruxw/recovery-331.img/file[/URL]
8. Boot into TWRP Recovery
9. now install "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip" : [url]http://www.mediafire.com/file/hquo5qjoi45hy9c/Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip/file[/URL]
In this way you will decrypt your phone and prevent to encrypt it again on reboot. If you don't Disable verity and force encrypt phone will re-encrypt itself on reboot because Vendor partition contain settings to encrypt data. There is a chance that after step 8 you will need to reinstall original international ROM ver. 114 and immediately after that the "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip"
After reboot successfully (and no encrypting data) go back to TWRP and flash the last magisk.
....If you want to try something else: Download the Resurrection Remix 8. 1, version 64 bit A only gapps from here: [url]https://forum.xda-developers.com/project-treble/trebleenabled-device-development/resurrection-remix-phh-treble-t3767688[/URL]
This one I found that is working also gapss.
You can find also other ROM (as system image!) here:
[url]https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-%28GSI%29-list[/URL] ,
or here:
[url]https://forum.xda-developers.com/project-treble/trebleenabled-device-development[/URL]
About treble experimentation here: [url]https://github.com/phhusson/treble_experimentations/wiki/Frequently-asked-questions-%28FAQ%29[/URL]
For example I like the DESCENDANT 3.1.1 : [url]https://forum.xda-developers.com/project-treble/trebleenabled-device-development/descendant-android-pie-custom-rom-ver-t3840578[/URL] but I can not make working gapps on it....till now at least
So, I think i have opened your appetite!
have fun!
Click to expand...
Click to collapse
Hello sir, I followed each and every step, but device ended up in bootloop. Mostly a soft brick. Every time I power on the device, the logo comes and phone turns off.
I even tried to patch the fstab in /vendor/etc. Same results.
By the way, I could not get the V114 stock global rom which you have mentioned but was able to get V109 stock global rom. If you have the link of the stock rom you mentioned, please provide a link for it. I will just revert back to stock and use it that way. Seems like the device doesn't wants to have an unlocked bootloader and a uncrypted data state ?

ianseer said:
Back to report...
Already finished all the things need to be done... and ABM30 method is working nicely.... now, I can enjoy all the root goodness in my red magic with original global rom.
really this is what I'm looking for... Thanks a lot.
Ps: just wanna share for the USB to pc connectivity problems: what I did was connect it on fastboot mode, and do fastboot command for unlocking your red magic.... wait around 5 min, unplug it if nothing happens, plug it again and wait again (until many times), after that you will see your fastboot command from wait mode into something successful... (i dunno why).
and then do reflash the recovery...
for the resurrection remix, I will try it and post it on new thread.... seems interesting
Click to expand...
Click to collapse
I'm facing issues with this. I followed every step as mentioned by ABM30. But the device in now on bootloop. Infact, I do have the twrp as recovery but device state is locked and the system isnt booting up. Help please

Zenith9082 said:
I'm facing issues with this. I followed every step as mentioned by ABM30. But the device in now on bootloop. Infact, I do have the twrp as recovery but device state is locked and the system isnt booting up. Help please
Click to expand...
Click to collapse
you mean twrp mentioned that your device is locked?

Help! Got bootloop after flashing permissiver_v5 in Evo X Rom (A2)

Hello! Hoping someone can help and guide me in fixing my A2's bootloop. I already searched many forums online, but still no luck.
I flashed a permissiver_v5.zip in Evolution X Rom hoping that it will solve the random reboots, and I got bootloop. I successfully flashed the July stock rom through Miflash, hoping to boot into system, but still bootloop. I flashed the stock firmware and persist zip too in TWRP, but I also got mount persist error. I also need to use fastboot boot twrp.img to get into Twrp since it will disappear after clicking reboot recovery. I tried EDL, but then I got not enough storage error in Miflash.
Hopefully somebody can help me with steps!
LATEST UPDATE:
With the help of KevMetal, I can now use my phone after a week of being hardbricked. At first, my device can't boot to the bootloader or recovery, so what I did was to press the volume down and power button for some time and my phone was detected by the PC. So my device booted to EDL by itself, no need to open the phone. Then I used the 2018 version of MiFlash Tool and flashed the V.10.0.17 of stock Pie ROM from here: https://forum.xda-developers.com/mi-...-t3824849/amp/
After that, I flashed the persist.zip provided by KevMetal (browse in this thread) in recovery since I can't sideload the zip, and it worked fine. I then booted to system and finally there was no bootloop.
I then noticed that the IMEI was gone, so I tried to fix through some guides online but this one worked for me. https://medium.com/@shekhawatkoki/fi...1-2ed533548d32

Ronaldendoma said:
Hello! Hoping someone can help and guide me in fixing my A2's bootloop. I already searched many forums online, but still no luck.
I flashed a permissiver_v5.zip in Evolution X Rom hoping that it will solve the random reboots, and I got bootloop. I successfully flashed the July stock rom through Miflash, hoping to boot into system, but still bootloop. I flashed the stock firmware and persist zip too in TWRP, but I also got mount persist error. I also need to use fastboot boot twrp.img to get into Twrp since it will disappear after clicking reboot recovery. I tried EDL, but then I got not enough storage error in Miflash.
Hopefully somebody can help me with steps!
Click to expand...
Click to collapse
you are messing up ..stop ..
1.boot into fastboot
2. flash stock rom with miflash
3. boot back to fastboot
4. download orange fox or pitch black recovery that actually supports persist flashing
5. join global mi a2 telegram group download relevant persist like if mi a2 or mi x6 and on android 9 or 10
6. put it in adb folder
7. boot recovery ( don't flash)
8. in recovery activate sideload adb option
9. in command window run :adb sideload persist.zip ( persist must have this name in adb folder )
10. now reboot your phone
*in the beginning it will bootloop four or five times ..just leave it
***suddenly your phone will be back to new
***stop flashing permissver and other crap
Sent from my wayne using XDA Labs

KevMetal said:
you are messing up ..stop ..
1.boot into fastboot
2. flash stock rom with miflash
3. boot back to fastboot
4. download orange fox or pitch black recovery that actually supports persist flashing
5. join global mi a2 telegram group download relevant persist like if mi a2 or mi x6 and on android 9 or 10
6. put it in adb folder
7. boot recovery ( don't flash)
8. in recovery activate sideload adb option
9. in command window run :adb sideload persist.zip ( persist must have this name in adb folder )
10. now reboot your phone
*in the beginning it will bootloop four or five times ..just leave it
***suddenly your phone will be back to new
***stop flashing permissver and other crap
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
Thank you so much for your reply. I really appreciate it. I admit that I am really wrong in flashing that permissiver zip. I just hoped that it will solve my random reboot issue, from this tutorial: https://www.google.com/url?sa=t&sou...BMAB6BAgCEAE&usg=AOvVaw2suOu9rYeTps71AvKuZbrA
So now, I already downloaded OrangeFox-R10.1_1-Stable-jasmine_sprout.zip for recovery and persist_restorer_6x.zip from the Telegram group, which is universal persist according to them.
But I just have some questions:
1. Do I need to wipe both a and b in recovery or use command fastboot -w before flashing the stock ROM?
2. After flashing stocK ROM in Miflash tool, it will start to boot to system, but in this case, bootloop, so am I right to press buttons to forcibly go to bootloader?
3. For #7 (boot to recovery), this means fastboot boot recovery.img?
4. For #9, if adb sideload doesn't work, can I flash persist in recovery instead?

Ronaldendoma said:
Thank you so much for your reply. I really appreciate it. I admit that I am really wrong in flashing that permissiver zip. I just hoped that it will solve my random reboot issue, from this tutorial: https://www.google.com/url?sa=t&sou...BMAB6BAgCEAE&usg=AOvVaw2suOu9rYeTps71AvKuZbrA
So now, I already downloaded OrangeFox-R10.1_1-Stable-jasmine_sprout.zip for recovery and persist_restorer_6x.zip from the Telegram group, which is universal persist according to them.
But I just have some questions:
1. Do I need to wipe both a and b in recovery or use command fastboot -w before flashing the stock ROM?
2. After flashing stocK ROM in Miflash tool, it will start to boot to system, but in this case, bootloop, so am I right to press buttons to forcibly go to bootloader?
3. For #7 (boot to recovery), this means fastboot boot recovery.img?
4. For #9, if adb sideload doesn't work, can I flash persist in recovery instead?
Click to expand...
Click to collapse
no install stock using miflash but don't wipe anything ..for this to work well don't install the recovery ..just boot
fastboot boot recovery.img
then using the adb sideload option you can flash the zip from your computer without decryting the internal storage
you can flash magisk the same way ..then you will have stock rooted with persist restored but without custom recovery and your device will remain encrypted ..
if you want custom recovery and install custom rom you can wipe and install but for stock don't do it ..flash persist and magisk from adb sideload without decrypting
2.yeah enter bootloader / fastboot with power button and volume button
4. it will work if done correctly ...if you want to flash from internal storage you will have to wipe and format data to decrypt internal syorage
Sent from my wayne using XDA Labs

KevMetal said:
you are messing up ..stop ..
1.boot into fastboot
2. flash stock rom with miflash
3. boot back to fastboot
4. download orange fox or pitch black recovery that actually supports persist flashing
5. join global mi a2 telegram group download relevant persist like if mi a2 or mi x6 and on android 9 or 10
6. put it in adb folder
7. boot recovery ( don't flash)
8. in recovery activate sideload adb option
9. in command window run :adb sideload persist.zip ( persist must have this name in adb folder )
10. now reboot your phone
*in the beginning it will bootloop four or five times ..just leave it
***suddenly your phone will be back to new
***stop flashing permissver and other crap
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
KevMetal said:
no install stock using miflash but don't wipe anything ..for this to work well don't install the recovery ..just boot
fastboot boot recovery.img
then using the adb sideload option you can flash the zip from your computer without decryting the internal storage
you can flash magisk the same way ..then you will have stock rooted with persist restored but without custom recovery and your device will remain encrypted ..
if you want custom recovery and install custom rom you can wipe and install but for stock don't do it ..flash persist and magisk from adb sideload without decrypting
2.yeah enter bootloader / fastboot with power button and volume button
4. it will work if done correctly ...if you want to flash from internal storage you will have to wipe and format data to decrypt internal syorage
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
Thank you again.
I tried adb sideload before but was stuck at 0%, I missed something. I'll update here for the result once I can be back to PC.

KevMetal said:
you are messing up ..stop ..
1.boot into fastboot
2. flash stock rom with miflash
3. boot back to fastboot
4. download orange fox or pitch black recovery that actually supports persist flashing
5. join global mi a2 telegram group download relevant persist like if mi a2 or mi x6 and on android 9 or 10
6. put it in adb folder
7. boot recovery ( don't flash)
8. in recovery activate sideload adb option
9. in command window run :adb sideload persist.zip ( persist must have this name in adb folder )
10. now reboot your phone
*in the beginning it will bootloop four or five times ..just leave it
***suddenly your phone will be back to new
***stop flashing permissver and other crap
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
KevMetal said:
no install stock using miflash but don't wipe anything ..for this to work well don't install the recovery ..just boot
fastboot boot recovery.img
then using the adb sideload option you can flash the zip from your computer without decryting the internal storage
you can flash magisk the same way ..then you will have stock rooted with persist restored but without custom recovery and your device will remain encrypted ..
if you want custom recovery and install custom rom you can wipe and install but for stock don't do it ..flash persist and magisk from adb sideload without decrypting
2.yeah enter bootloader / fastboot with power button and volume button
4. it will work if done correctly ...if you want to flash from internal storage you will have to wipe and format data to decrypt internal syorage
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
Thank you again.
I tried adb sideload before but was stuck at 0%, I maybe missed something. I'll update here for the result once I can be back to PC.

Ronaldendoma said:
Thank you again.
I tried adb sideload before but was stuck at 0%, I maybe missed something. I'll update here for the result once I can be back to PC.
Click to expand...
Click to collapse
ok yeah must be a mistake ..
do you understand that first you enter fastboot and boot the orange fox recovery ..only then you start the adb ..
BUT REMember first you need to toggle or activate adb from orange fox recovery (maybe you forgot this ? )
another thing it is very slow so wait very long
another thing the zip you want to flash must be in the adb folder and have the name you use
so
rename persist to persist.zip and put it in adb folder ..then put magisk zip and rename to magisk.zip :
adb sideload persist.zip
adb sideload magisk.zip
Sent from my wayne using XDA Labs

here is a photo where you need to activate adb
Sent from my wayne using XDA Labs

KevMetal said:
ok yeah must be a mistake ..
do you understand that first you enter fastboot and boot the orange fox recovery ..only then you start the adb ..
BUT REMember first you need to toggle or activate adb from orange fox recovery (maybe you forgot this ? )
another thing it is very slow so wait very long
another thing the zip you want to flash must be in the adb folder and have the name you use
so
rename persist to persist.zip and put it in adb folder ..then put magisk zip and rename to magisk.zip :
adb sideload persist.zip
adb sideload magisk.zip
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
I need to wait more, I think. Before this thread, I tried to adb sideload in TWRP but it took somewhat long and still 0%, so I just cancelled since I ran out of time.

KevMetal said:
here is a photo where you need to activate adb
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
Regarding persist.zip, I am now confused because I asked in the group if the file persist_restorer_6x.zip is universal (either pie or 10, wayne or jasmine), they said yes, and another one said no. I searched in the group and found persist_restorer_a2.zip. I checked both files and they have the same filesize and contents.
So is there a thing like a universal persist for a2/6x, either for pie or 10? Or like what you said, only relevant persist depending on the os and device?

techieboy2020 said:
Regarding persist.zip, I am now confused because I asked in the group if the file persist_restorer_6x.zip is universal (either pie or 10, wayne or jasmine), they said yes, and another one said no. I searched in the group and found persist_restorer_a2.zip. I checked both files and they have the same filesize and contents.
So is there a thing like a universal persist for a2/6x, either for pie or 10? Or like what you said, only relevant persist depending on the os and device?
Click to expand...
Click to collapse
it is the same device.. so it is cross compatible ..it might just give an error if it checks the build prop ..obviously flash the A2..pie or q will just maybe be updated version or not but bettrr to flash corresponding if it exists
Sent from my wayne using XDA Labs

KevMetal said:
it is the same device.. so it is cross compatible ..it might just give an error if it checks the build prop ..obviously flash the A2..pie or q will just maybe be updated version or not but bettrr to flash corresponding if it exists
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
I see. I can't access my PC yet, but what if I still got bootloop after trying those steps, what must I do next? I'm worried for step #10.
Regarding the persist.zip, can you please check the zips below? The two have the same filesize and files inside, so maybe the two are just the same.

techieboy2020 said:
I see. I can't access my PC yet, but what if I still got bootloop after trying those steps, what must I do next? I'm worried for step #10.
Regarding the persist.zip, can you please check the zips below? The two have the same filesize and files inside, so maybe the two are just the same.
Click to expand...
Click to collapse
those are empty and won't work ..use this
https://www.dropbox.com/s/mimt4go8fert44c/persist good.zip?dl=0
Sent from my wayne using XDA Labs

KevMetal said:
those are empty and won't work ..use this
https://www.dropbox.com/s/mimt4go8fert44c/persist good.zip?dl=0
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
Ok thank you so much. Will try this tomorrow.
Regarding the state of my device, I can't boot to system because of bootloop. If I press power and volume +, I got no command. If I press power and volume -, fastboot mode. My device's bootloader is already unlocked, and can be detected through fastboot.

techieboy2020 said:
Ok thank you so much. Will try this tomorrow.
Regarding the state of my device, I can't boot to system because of bootloop. If I press power and volume +, I got no command. If I press power and volume -, fastboot mode. My device's bootloader is already unlocked, and can be detected through fastboot.
Click to expand...
Click to collapse
you don't need to boot to system ...just boot the revovery and flash the zip ..
Sent from my wayne using XDA Labs

KevMetal said:
you don't need to boot to system ...just boot the revovery and flash the zip ..
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
Got it. So the zip is compatible for either Pie or Android 10?
What's the best version for Miflash tool? I tried the newer version but it can't detect my device, and only the older version can detect. But it seems that the older version can't be trusted also since I still got persist error before.
For #10, my device will bootloop 4 to 5 times. So will it automatically turn off and on again until it will successfully boot? How long does it normally boot?

UPDATE:
KevMetal said:
you don't need to boot to system ...just boot the revovery and flash the zip ..
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
UPDATE:
So I flashed the Pie Rom (V.10.0.17.0) in the MiFlash Tool (v. 2016.04.01.0) and the flashing was successful. The device turned on and only remained at the Android One logo and turned off again. This repeated for another time and I then forced my device to fastboot mode through the buttons. I then flashed the latest Orange Fox Recovery and it was successful. Now, I checked the recovery and persist can't be mounted (can't put a check on the box), but I still continued to adb sideload mode. The sideloading for persist.zip started, but was stuck at 10%. I waited more and decided to disconnect and try to flash the zip on the device instead. I checked the active slot and it was b, so I thought changing to a will be able to mount persist. I thought that if I remain at b, I will still get mount persist error. I clicked "boot to recovery" and the screen turned off. After a while, the screen remained off and I tried to use the button combinations, and the screen was totally black (no fastboot, logo, animation, or even some light, etc). It's completely black, but I noticed that the device was still hot after a few minutes. I connected my device to the PC again and the MiFlash tool detected my device as Com10. I flashed the rom again but the flashing was not successful. I tried to uninstall the drivers and still, there is no hope for reflashing the rom (it's now detected as com4). If I try to use power combinations, the PC will make sounds like when you connect/ disconnect a device, meaning, my phone can still be detected by my PC. So is there still a hope for my phone?

techieboy2020 said:
UPDATE:
So I flashed the Pie Rom (V.10.0.17.0) in the MiFlash Tool (v. 2016.04.01.0) and the flashing was successful. The device turned on and only remained at the Android One logo and turned off again. This repeated for another time and I then forced my device to fastboot mode through the buttons. I then flashed the latest Orange Fox Recovery and it was successful. Now, I checked the recovery and persist can't be mounted (can't put a check on the box), but I still continued to adb sideload mode. The sideloading for persist.zip started, but was stuck at 10%. I waited more and decided to disconnect and try to flash the zip on the device instead. I checked the active slot and it was b, so I thought changing to a will be able to mount persist. I thought that if I remain at b, I will still get mount persist error. I clicked "boot to recovery" and the screen turned off. After a while, the screen remained off and I tried to use the button combinations, and the screen was totally black (no fastboot, logo, animation, or even some light, etc). It's completely black, but I noticed that the device was still hot after a few minutes. I connected my device to the PC again and the MiFlash tool detected my device as Com10. I flashed the rom again but the flashing was not successful. I tried to uninstall the drivers and still, there is no hope for reflashing the rom (it's now detected as com4). If I try to use power combinations, the PC will make sounds like when you connect/ disconnect a device, meaning, my phone can still be detected by my PC. So is there still a hope for my phone?
Click to expand...
Click to collapse
all of this couldn't happen if you only flashed permissiver ..what rom did you previously flash in slot b
anyway doesn't matter ..boot to fastboot with buttons ..boot ..NOT FLASH orange fox recovery
do all wipes
format data
install custom rom
install magisk
install persist
reboot to other standby slot ..
do all wipes
format data
install custom rom
install magisk
install persist
then reboot and phone will boot
use a latest custom rom Q with gapps included ....
follow all the instructions ..not only some ..don change them ..if it fails message me with screenshot
but the 10% problem over usb is a hardware , computer or most likely cable problem ..get a new cable ..or maybe you changed or damaged your screen improperly ..
anyway try the above
also download the most newest copy of miflash and use that to install drivers and flash if you want to flash stock and flash the latest stock amdroid ..
if your phone doesn't go into fastboot it is cos it is bricked in edl mode ..so flash latest stock with latest miflash ..
THEN FLASH PERSIST BY ONLY BOOTINGBrecovery
did you try to convert this A2 to Wayne amd triggered arb ? that could be why flashing stock pie goes to edl mode
Sent from my wayne using XDA Labs

Just FYI:
Since 10.0.2.0 till now I thought that persist.img is version-insensitive, as I flashed persist.img taken from 8.1 ROM into couple of versions of 9.0 without any problems (via my method published in "Guides...").
Last week I noticed that compass is "showing south", and tried to flash various versions of persist.img into active 11.0.12.0 - and was surprised to encounter "white screen of eternal booting" with non-native version of persist.img. So finally had to flash persist.img taken from 11.0.12.0 fastboot ROM image.
(Btw, my problem with compass seems to have 2 sides -1st is somewhat very big deviation at homeplace, and 2nd is that only 1st magnetic sensor is being calibrated while second magnetic sensor is not being calibrated by means I used).

KevMetal said:
all of this couldn't happen if you only flashed permissiver ..what rom did you previously flash in slot b
anyway doesn't matter ..boot to fastboot with buttons ..boot ..NOT FLASH orange fox recovery
do all wipes
format data
install custom rom
install magisk
install persist
reboot to other standby slot ..
do all wipes
format data
install custom rom
install magisk
install persist
then reboot and phone will boot
use a latest custom rom Q with gapps included ....
follow all the instructions ..not only some ..don change them ..if it fails message me with screenshot
but the 10% problem over usb is a hardware , computer or most likely cable problem ..get a new cable ..or maybe you changed or damaged your screen improperly ..
anyway try the above
also download the most newest copy of miflash and use that to install drivers and flash if you want to flash stock and flash the latest stock amdroid ..
if your phone doesn't go into fastboot it is cos it is bricked in edl mode ..so flash latest stock with latest miflash ..
THEN FLASH PERSIST BY ONLY BOOTINGBrecovery
did you try to convert this A2 to Wayne amd triggered arb ? that could be why flashing stock pie goes to edl mode
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
So I was able to use another laptop, and I managed to install adb, drivers, and MiFlash Tool. The 2018 version can now detect my phone, and I can now at least boot into fastboot. But my flashing is still not successful because I got stuck at system.img. The laptop freezes and I already tried to free up space in C: drive.

[Recovery] TWRP (Unofficial/Experimental) for Samsung M40

We got our first recovery for Samsung M40 (SM-M405F). This one is ported using Samsung Auto TWRP recovery porter by Team Hovatek
Please try and let everyone know if it works for you or not.
(If you want to do it yourself for any other Android OS version, you can refer to the original Hovatek post.)
You must disable dm_verity before flashing TWRP.
TWRP based on version: 3.5.*
Details of base recovery used for porting:
Source: Extracted from downloaded firmware
Version: Android 11
Build Date: Mon, 12 Apr 2021 07:54:43 +0000
Security Patch Level: 2021-04-01
Product code: INS
PDA: M405FDDU2CUD2
CSC: M405FODM2CUD2
If this works for you, please post here so everyone will know.
If something goes wrong you need and any stock img/file let me know, I will share that too.
Update 1 =>
NOTE: Unfortunately, I can not test this recovery for few more days as this M40 is the only device that I have and it is also source of internet access for me and my laptop. If this mobile is turned off for any reason I wont have internet access so looking for fixes would be difficult.
But I have rooted some devices before and know how things work so I will help in every possible way if someone stuck at any place while trying this recovery.
Also, if someone confirms this recovery does not work, I am planning to port TWRP from scratch.
Update 2 =>
Instructions for NON-Rooted and Bootloader locked device-
Unlocking Bootloader:
Allow bootloader unlocking in Developer options → OEM unlocking
Reboot to download mode: power off your device and press Volume Up + Volume Down and plug in your device to a PC to boot into download mode.
Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.
Go through the initial setup. Skip through all the steps since data will be wiped again in later steps. Connect the device to Internet during the setup.
Enable developer options, and confirm that the OEM unlocking option exists and is grayed out. This means the VaultKeeper service has unleashed the bootloader.
Your bootloader now accepts unofficial images in download mode
Disable DM_Verity (Android Verified Boot):
Copy the vbmeta.img (download from attachments) into your adb and fastboot folder
You can now flash the vbmeta.img using fastboot to remove dm_verity from your device
// Enable USB Debugging and enter following commands in CMD/Terminal after connecting device to computer.
adb devices
// You should see your device listed
adb reboot-bootloader
// Device should reboot to bootloader
fastboot devices
// You should see your device listed
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
// OR if the command above doesn't work, try below
fastboot flash vbmeta vbmeta.img
// DONE
////////////////////////////////++++++++++++++++++++++++++////////////////////////////////
Note: For Magisk Rooted devices above steps are not required, as Magisk already patches vbmeta.img and disabled dm_verity (Android Verified Boot)
Flash TWRP with/without Root using Odin
1. Download and install Odin on your PC
2. Download the attached recovery.img, convert it into .tar
3. Reboot to download mode: power off your device and press Volume Up + Volume Down and plug in your device to a PC to boot into download mode.
4. Select recovery.tar under AP_ and Uncheck “Auto Reboot” in Options!
5. Flash the device
6. Now do not power on to System, enter into Recovery/TWRP mode using key combination.
Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
*DONE*
Enjoy TWRP!

Can you tell step by step procedure for flashing twrp in m40.
How to disable dm-verity?

I guess this didn't work in my device.
"reason recovery: error verifying vbmeta image: invalid vbmata header" error is coming.

Shashvatsawar said:
I guess this didn't work in my device.
"reason recovery: error verifying vbmeta image: invalid vbmata header" error is coming.
Click to expand...
Click to collapse
You must disable dm_verity before flashing TWRP.
Is your device rooted?
How did you flash this TWRP?
Please share your device info.

did you already tested it on your device??

rohitrss said:
You must disable dm_verity before flashing TWRP.
Is your device rooted?
How did you flash this TWRP?
Please share your device info.
Click to expand...
Click to collapse
My Product code : SM-M405FZBDINS
My device is rooted using magisk patch.
I flashed twrp before root using odin.
I didn't disable dm_verity.
How can I disable dm_verity?

deadinside322 said:
did you already tested it on your device??
Click to expand...
Click to collapse
Unfortunately no, I can not do any testing for few more days as this M40 is the only device that I have and it is also source of internet access for me and my laptop. If this mobile is turned off for any reason I wont have internet access so looking for fixes would be difficult.
But I have rooted some devices before and know how things work so I will help in every possible way if someone stuck at any place while trying this recovery.
Also, if someone confirms this recovery does not work, I am planning to port TWRP from scratch.

Thread title and note updated.

Shashvatsawar said:
My Product code : SM-M405FZBDINS
My device is rooted using magisk patch.
I flashed twrp before root using odin.
I didn't disable dm_verity.
How can I disable dm_verity?
Click to expand...
Click to collapse
As you have flashed TWRP before root, it failed at verification stage. You need to disable dm_verity, please follow https://forum.hovatek.com/thread-32719.html based on your OS version.
Otherwise, you can flash TWRP after rooting as Magics already disables dm_verity.

rohitrss said:
As you have flashed TWRP before root, it failed at verification stage. You need to disable dm_verity, please follow https://forum.hovatek.com/thread-32719.html based on your OS version.
Otherwise, you can flash TWRP after rooting as Magics already disables dm_verity.
Click to expand...
Click to collapse
I tried it But I am not able to boot into recovery then.
It just reboots.

Shashvatsawar said:
I tried it But I am not able to boot into recovery then.
It just reboots.
Click to expand...
Click to collapse
Did you try key combination or adb command?
Also, could you please share what all have you tried/done so far so I will have better idea?

I unlocked the bootloader, then booted my device to download mode.. change .img file extension to .tar then tried to flashing it using oden and selected recovery.tar in AP slot.. but it's stuck on file analysis.
Any help? Any step I did wrong? Let me know

Akhil137 said:
I unlocked the bootloader, then booted my device to download mode.. change .img file extension to .tar then tried to flashing it using oden and selected recovery.tar in AP slot.. but it's stuck on file analysis.
Any help? Any step I did wrong? Let me know
Click to expand...
Click to collapse
As you have flashed TWRP before root, it failed at verification stage. You need to disable dm_verity, please follow https://forum.hovatek.com/thread-32719.html based on your OS version.
Otherwise, you can flash TWRP after rooting as Magics already disables dm_verity.

rohitrss said:
Did you try key combination or adb command?
Also, could you please share what all have you tried/done so far so I will have better idea?
Click to expand...
Click to collapse
I followed this thread to root my device
https://forum.xda-developers.com/t/root-sm-m405f-galaxy-m40.3951491/
There was no option of dm verity while patching stock rom using magisk.
Though My phone was successfully rooted.
I can't use fastboot as it's not showing my device in devices list ( tried a lot).
Finally I flashed your recovery using odin but after going to recovery mode it rebooted only. For recovery mode I tried key combination first and then a root app after device booted.

Updated post with detailed flashing instructions.

rohitrss said:
Updated post with detailed flashing instructions.
Click to expand...
Click to collapse
did the recovery work for you?

Is there any update?

When i try to go to bootloader, my device always go to download mode. how can i fix this???

rohitrss said:
Unfortunately no, I can not do any testing for few more days as this M40 is the only device that I have and it is also source of internet access for me and my laptop. If this mobile is turned off for any reason I wont have internet access so looking for fixes would be difficult.
But I have rooted some devices before and know how things work so I will help in every possible way if someone stuck at any place while trying this recovery.
Also, if someone confirms this recovery does not work, I am planning to port TWRP from scratch.
Click to expand...
Click to collapse
Bro, I am going to use twrp in my main phone M40.
And I don't care if it gets bricked :>

Question stuck at bootlogo after installing gsi

Hello everyone. i just want to install Gsi on an new unlocked tab a8, after flashing twrp, I use the fastbootd mode to flash the gsi and installed the multi-disable zip. when I want to reboot to os, it stucked at bootlogo. I don't know where I am wrong, so please help me, in appreciation

WolfHRB said:
Hello everyone. i just want to install Gsi on an new unlocked tab a8, after flashing twrp, I use the fastbootd mode to flash the gsi and installed the multi-disable zip. when I want to reboot to os, it stucked at bootlogo. I don't know where I am wrong, so please help me, in appreciation
Click to expand...
Click to collapse
We don't know where you went wrong either because you didn't list the steps you took or what GSI you flashed or what stock ROM you started from. Or where you are looping.

starting firmware: X200ZCU2CWD3
Steps: 1. Unlock BL
2. flash TWRP via Odin V3.14
3. Format data partition
4. flash dm-verity disabler (File name: Disable_Dm-Verity_ForceEncrypt)
5. reboot to fastbootd mode (using TWRP reboot menu)
6. fastboot erase system
7. fastboot flash system "img path"
8. fastboot -w
9. fastboot reboot

lewmur said:
We don't know where you went wrong either because you didn't list the steps you took or what GSI you flashed or what stock ROM you started from. Or where you are looping.
Click to expand...
Click to collapse
starting firmware: X200ZCU2CWD3
Steps: 1. Unlock BL
2. flash TWRP via Odin V3.14
3. Format data partition
4. flash dm-verity disabler (File name: Disable_Dm-Verity_ForceEncrypt)
5. reboot to fastbootd mode (using TWRP reboot menu)
6. fastboot erase system
7. fastboot flash system "img path"
8. fastboot -w
9. fastboot reboot

WolfHRB said:
starting firmware: X200ZCU2CWD3
Steps: 1. Unlock BL
2. flash TWRP via Odin V3.14
3. Format data partition
4. flash dm-verity disabler (File name: Disable_Dm-Verity_ForceEncrypt)
5. reboot to fastbootd mode (using TWRP reboot menu)
6. fastboot erase system
7. fastboot flash system "img path"
8. fastboot -w
9. fastboot reboot
Click to expand...
Click to collapse
Don't flash dm-verity disabler for this device and the GSI should boot as long as it's compatible

kevinco1 said:
Don't flash dm-verity disabler for this device and the GSI should boot as long as it's compatible
Click to expand...
Click to collapse
Without this alway bootloop logo too.
1. Extract the IMG to the adb folder and rename it system.img
2. Flash TWRP with ODIN
3. When booting into TWRP using the Volume up and Power key, select reboot and then fast boot.
4. When you get there, go on your PC and open cmd with the adb folder.
5. Now type fastboot devices just make sure you have the device connect properly. Type fastboot -w after.
6. Type "fastboot flash system system.img" press enter and wait for it to finish. The last line should be be where you can type other commands.
7. When its finished, type fastboot reboot fastboot.

stradfred said:
Without this alway bootloop logo too.
1. Extract the IMG to the adb folder and rename it system.img
2. Flash TWRP with ODIN
3. When booting into TWRP using the Volume up and Power key, select reboot and then fast boot.
4. When you get there, go on your PC and open cmd with the adb folder.
5. Now type fastboot devices just make sure you have the device connect properly. Type fastboot -w after.
6. Type "fastboot flash system system.img" press enter and wait for it to finish. The last line should be be where you can type other commands.
7. When its finished, type fastboot reboot fastboot.
Click to expand...
Click to collapse
What exact GSI and build are you trying to install? There are only a few that are compatible, otherwise you're not gonna have any other luck flashing

I tryed with on my X200XXU2CWC1 firmware:
lineage-19.1-20230418-UNOFFICIAL-arm64_bgN.img
lineage-20.0-20230324-UNOFFICIAL-arm64_bgN.img
lineage-20.0-20230325-UNOFFICIAL-a64_bgN.img
Old version too but the same result...
Which version we are sure that works?

stradfred said:
I tryed with on my X200XXU2CWC1 firmware:
lineage-19.1-20230418-UNOFFICIAL-arm64_bgN.img
lineage-20.0-20230324-UNOFFICIAL-arm64_bgN.img
lineage-20.0-20230325-UNOFFICIAL-a64_bgN.img
Old version too but the same result...
Which version we are sure that works?
Click to expand...
Click to collapse
Make sure you are only trying to flash arm64 builds for this device
Both 19.1-20230418 and 20.0-20230324 do install properly but there's certain bugs that make them unfit to be used as a daily driver.
If you're looking for the latest build where everything works (including bluetooth) flash 20.0-20230218

stradfred said:
Without this alway bootloop logo too.
1. Extract the IMG to the adb folder and rename it system.img
2. Flash TWRP with ODIN
3. When booting into TWRP using the Volume up and Power key, select reboot and then fast boot.
4. When you get there, go on your PC and open cmd with the adb folder.
5. Now type fastboot devices just make sure you have the device connect properly. Type fastboot -w after.
6. Type "fastboot flash system system.img" press enter and wait for it to finish. The last line should be be where you can type other commands.
7. When its finished, type fastboot reboot fastboot.
Click to expand...
Click to collapse
You left out the step to format data and factory wipe.

lewmur said:
You left out the step to format data and factory wipe.
Click to expand...
Click to collapse
That's right!
How is it normal to do this command after having flashed a ROM ???
Once done, I boot of course on lineage after a few moments on the Samsung logo.
Which version of lineage is the most stable, 19 (Android 12) or 20 (Android 13)?
Thank you both for your help.

kevinco1 said:
If you're looking for the latest build where everything works (including bluetooth) flash 20.0-20230218
Click to expand...
Click to collapse
https://sourceforge.net/projects/andyyan-gsi/files/lineage-20-td/History/lineage-20.0-20230218-UNOFFICIAL-arm64_bgN.img.xz/download
I tried this.

stradfred said:
That's right!
How is it normal to do this command after having flashed a ROM ???
Once done, I boot of course on lineage after a few moments on the Samsung logo.
Which version of lineage is the most stable, 19 (Android 12) or 20 (Android 13)?
Thank you both for your help.
Click to expand...
Click to collapse
TWRP and fastboot can't handle the encrypted data partition. So you need to format it. Current versions of LOS re-encrypt it as soon as you boot to system. And you can't use dm-verity on this model, so you can't disable it.

stradfred said:
https://sourceforge.net/projects/andyyan-gsi/files/lineage-20-td/History/lineage-20.0-20230218-UNOFFICIAL-arm64_bgN.img.xz/download
I tried this.
Click to expand...
Click to collapse
Did you try this build before or after the realization you had left out the steps to wipe and factory reset?

Has anyone managed to install a GSI on the SM-X200 with X200XXU2CWC1 firmware? I tried different LOS 20 and LOS 19 GSIs, with and without GAPPS, including the ones mentioned earlier from March and April, but did not succeed a single time. The tablet gets always stuck in a boot loop. I flashed via TWRP and wiped and formatted data every time.
Is it possibly the vendor firmware (SW rev. 2) that prevents the GSI from running? All guides from this forum seems to relate to a SW rev. 1 firmware like X200XXS1CWA3.

mrspeccy said:
Has anyone managed to install a GSI on the SM-X200 with X200XXU2CWC1 firmware? I tried different LOS 20 and LOS 19 GSIs, with and without GAPPS, including the ones mentioned earlier from March and April, but did not succeed a single time. The tablet gets always stuck in a boot loop. I flashed via TWRP and wiped and formatted data every time.
Is it possibly the vendor firmware (SW rev. 2) that prevents the GSI from running? All guides from this forum seems to relate to a SW rev. 1 firmware like X200XXS1CWA3.
Click to expand...
Click to collapse
If you mean you used the "Install" button in TWRP to flash, then that is your mistake. The "Install" button only has the option to flash the "Super" partition and not the "System". You need to use "Fastboot" to flash the system image. I flashed from CWD2 which is even later than CWC1, so that shouldn't be a problem. If it was, then TWRP wouldn't have worked. I'm running LOS 20 20300507 bgN.

No, I used TWRP to get into fastboot mode and said fastboot flash system ...img. I have no idea what I did wrong. Previously I flashed Lineage on a couple of Samsung Tablets (SM-T510, SM-T505).

mrspeccy said:
No, I used TWRP to get into fastboot mode and said fastboot flash system ...img. I have no idea what I did wrong. Previously I flashed Lineage on a couple of Samsung Tablets (SM-T510, SM-T505).
Click to expand...
Click to collapse
There are only certain LOS builds that work with this device, you're wasting your time if you are blindly flashing random ones.
Refer to earlier posts to confirm which ones do work. And like @lewmur just reported the newest build 20300507 bgN does flash successfully

The 20230507 bgN was actually the first build I tried before I went to older variants, including the 20220814 bgN that is mentioned in a different thread.
@lewmur : Did you do a clean flash and format data before you installed the 20230507 build on the CWD2 firmware? There might be some issues with format data and the TWRP 3.7.0-12.2 from this forum (https://forum.xda-developers.com/t/...-for-2021-galaxy-tab-a8-10-5-sm-x200.4488691/) on the latest kernel. After I format data in TWRP, the tablet is recognized as writable media in Windows, but I get reading and writing errors when I try to access the about 22 GB large partition.
I know that it is impossible to roll back the bootloader to revision 1, but may it be possible that I extract and flash a kernel from the X200XXS1CWA3 to further investigate this issue?

mrspeccy said:
The 20230507 bgN was actually the first build I tried before I went to older variants, including the 20220814 bgN that is mentioned in a different thread.
@lewmur : Did you do a clean flash and format data before you installed the 20230507 build on the CWD2 firmware? There might be some issues with format data and the TWRP 3.7.0-12.2 from this forum (https://forum.xda-developers.com/t/...-for-2021-galaxy-tab-a8-10-5-sm-x200.4488691/) on the latest kernel. After I format data in TWRP, the tablet is recognized as writable media in Windows, but I get reading and writing errors when I try to access the about 22 GB large partition.
I know that it is impossible to roll back the bootloader to revision 1, but may it be possible that I extract and flash a kernel from the X200XXS1CWA3 to further investigate this issue?
Click to expand...
Click to collapse
You must do a clean flash. The purpose of formatting the data partition is to get rid of the encryption. TWRP can't handle the encryption. And LOS will re-encrypt it the first time you boot to system. As to extracting the kernel from CWA3, I don't advise doing that. It could hard brick the tablet.