Here is a bugless version of TWRP by @Zormax
Full tutorial to unlock bootloader and install TWRPDownload ADB/Fastboot tool and extract it. Make sure you have installed ADB/FASTBOOT drivers on your PC (Google it for this)
Press Shift button and right click in extracted ADB tool's folder
Open command window there
Enable Developer option by clicking 5-6 times on build no.
go to the Developer Option and enale USB debugging and OEM unlock
connect your device to PC
then type these commands:
Code:
adb reboot bootloader
fastboot oem unlock
fastboot reboot
Now your bootloder is unlocked
For flash TWRP:
Code:
adb reboot bootloader
fastboot flash recovery recoveryE4plus.img
fastboot flash boot boot_NMA26.42-97.img
fastboot reboot
Done
then flash phh's superuser to root your phone
TWRP: Click Here
Boot: Click Here
Source
Credits: Zormax
Continues with stock recovery here, XT1773.
I want to root my e4 plus to use Substratum themes but I'm tensed what if I get boot loop there is no stock rom to recover device, Can anybody upload back up of Stock rom from TWRP, So if there is anything wrong I can use back my device is XT1770.
So many Stock rom requests already still there is no availability
SHadYreBOrN said:
So many Stock rom requests already still there is no availability
Click to expand...
Click to collapse
http://www.mediafire.com/file/zbjpsoi6wlfyorm/MOTOROLA_EPLUS_NMA26.42-75_ROW.7z
here is a stock rom
you can flash through sp tool as well
akash_eric said:
http://www.mediafire.com/file/zbjpsoi6wlfyorm/MOTOROLA_EPLUS_NMA26.42-75_ROW.7z
here is a stock rom
you can flash through sp tool as well
Click to expand...
Click to collapse
Can I flash it on E4 plus XT1770 model ??
sandeep chauhan 2722 said:
Can I flash it on E4 plus XT1770 model ??
Click to expand...
Click to collapse
ye u can
its for moto e4 plus - mt6737
sandeep chauhan 2722 said:
Can I flash it on E4 plus XT1770 model ??
Click to expand...
Click to collapse
follow this ! https://forum.xda-developers.com/moto-e4/how-to/how-to-backup-stock-rom-moto-e4-variants-t3654976 applies to both moto e4 and plus.
the boot.img just bricked my phone.... be careful
---------- Post added at 07:28 PM ---------- Previous post was at 07:26 PM ----------
log says failed to load kernel also have no recovery twrp that is
neilc300 said:
the boot.img just bricked my phone.... be careful
---------- Post added at 07:28 PM ---------- Previous post was at 07:26 PM ----------
log says failed to load kernel also have no recovery twrp that is
Click to expand...
Click to collapse
it is because of dm-verity
Is this for the Snapdragon/Qualcomm version?
Specifically model xt1775
soaringowl2145 said:
Is this for the Snapdragon/Qualcomm version?
Specifically model xt1775
Click to expand...
Click to collapse
nope.
its for mediatek (menitioned in OP)
Francesco Franz said:
nope.
its for mediatek (menitioned in OP)
Click to expand...
Click to collapse
Do you know what it will take to get twrp on the device I mentioned then?
soaringowl2145 said:
Do you know what it will take to get twrp on the device I mentioned then?
Click to expand...
Click to collapse
upload your device recovery and boot image here. i will make twrp for your device.
Didnt work for me, my screen stays black when i try to boot on recovery. xt1773. Then i have to keep pressing power button for 10+ seconds to reboot.
Any help ?
downloadkct said:
Didnt work for me, my screen stays black when i try to boot on recovery. xt1773. Then i have to keep pressing power button for 10+ seconds to reboot.
Any help ?
Click to expand...
Click to collapse
Try this fastboot erase recovery (erase stock recovery)
than flash new recovery
fastboot flash recovery twrp.img
Francesco Franz said:
Try this fastboot erase recovery (erase stock recovery)
than flash new recovery
fastboot flash recovery twrp.img
Click to expand...
Click to collapse
Thanks for your answer but ill wait for a better method. This made my phone hardbrick, i was lucky to recovery it using SP
downloadkct said:
Didnt work for me, my screen stays black when i try to boot on recovery. xt1773. Then i have to keep pressing power button for 10+ seconds to reboot.
Any help ?
Click to expand...
Click to collapse
*black screen*
may be twrp recovery doesn't support your device.
Francesco Franz said:
may be twrp recovery doesn't support your device.
Click to expand...
Click to collapse
Most likely, im not the only one saying it didnt work on xt1773
@Francesco Franz mate, after flashing the TWRP on my XT1770 I get also just a black screen when I try to boot into the recovery mode. Could it be, that the .img file is just sligtly too big? I get an output:
Code:
# fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending 'recovery' (13426 KB)...
OKAY [ 0.559s]
writing 'recovery'...
OKAY [ 0.315s]
finished. total time: 0.874s
(my ubuntu PC)# fastboot reboot
rebooting...
finished. total time: 0.053s
I can normally reboot the phone into its Android OS
Related
hey to all im new here and i want to root my phone and put custom rom
i unlock my boot loader
now i want to put recovery but i didnt find where to download the recovery?
thers twrp from google play but when i start it it say i need root so how i do it?
i found phil recovery but it end with .img not zip so how do i flash it?
plz your help
Flash recovery in fastboot usb mode with command
flash recovery recovery.img
where recovery.img is name of your recovery file.
You have everything explained here
http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
snebojsa said:
Flash recovery in fastboot usb mode with command
flash recovery recovery.img
where recovery.img is name of your recovery file.
Click to expand...
Click to collapse
fastboot flash recovery recovery.img
Maybe the 'fastboot' was implied by your mention of fastboot, but just wanted the command to be correct and clearly understood.
---------- Post added at 10:45 AM ---------- Previous post was at 10:44 AM ----------
bubu23 said:
thers twrp from google play but when i start it it say i need root so how i do it?
Click to expand...
Click to collapse
Just find your desired recovery (TWRP, Philz) in the Development forum section.
redpoint73 said:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
You are absolutely right, forgot to add fastboot at the beginning, that is the right command :good:
So I just went back to 7.1.2 from O and I tried using the fasboot boot to install tarp but in hanging on the twrp loading screen. I've downgraded all the way to March 7.1.1 and the same issue occurs. Any hel?
Google edition pixel not Verizon
Yes bootloader is unlocked
bennyboy2120 said:
So I just went back to 7.1.2 from O and I tried using the fasboot boot to install tarp but in hanging on the twrp loading screen. I've downgraded all the way to March 7.1.1 and the same issue occurs. Any hel?
Google edition pixel not Verizon
Yes bootloader is unlocked
Click to expand...
Click to collapse
Which version are you trying?
Are you booting to TWRP from fastboot or installing twrp from fastboot?
Try booting to twrp from fastboot and then installing TWRP with the ZIP
Latest version only give me bootloops
twrp-pixel-installer-marlin-3.0.2-0-RC1.zip works for me though.
parakleet said:
Which version are you trying?
Are you booting to TWRP from fastboot or installing twrp from fastboot?
Try booting to twrp from fastboot and then installing TWRP with the ZIP
Latest version only give me bootloops
twrp-pixel-installer-marlin-3.0.2-0-RC1.zip works for me though.
Click to expand...
Click to collapse
I am using the boot command I can't get passed the twrp boot screen unless it takes more then 10 minutes to boot up first time
Sent from my Pixel XL using Tapatalk
bennyboy2120 said:
I am using the boot command I can't get passed the twrp boot screen unless it takes more then 10 minutes to boot up first time
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
I'm having the exact same problem as we speak... had it with skipsoft toolkit and doing it manual through adb..
I'm using "twrp-3.0.2-0-RC1-fastboot-marlin.img"
I'm just going to leave it on that start screen for 30ish mins see if anything happens.
btw I also reverted from Android O to N
RedBlueGreen said:
I'm having the exact same problem as we speak... had it with skipsoft toolkit and doing it manual through adb..
I'm using "twrp-3.0.2-0-RC1-fastboot-marlin.img"
Click to expand...
Click to collapse
Keep me posted if you get it, I'm trying some other methods
Sent from my Pixel XL using Tapatalk
RedBlueGreen said:
I'm having the exact same problem as we speak... had it with skipsoft toolkit and doing it manual through adb..
I'm using "twrp-3.0.2-0-RC1-fastboot-marlin.img"
I'm just going to leave it on that start screen for 30ish mins see if anything happens.
btw I also reverted from Android O to N
Click to expand...
Click to collapse
I also went from 7.1.2 back to 7.1.1 March update still had the issue
Sent from my Pixel XL using Tapatalk
bennyboy2120 said:
Keep me posted if you get it, I'm trying some other methods
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Yeap will do. Might try an older version of twrp.img if nothing happens in 30mins
---------- Post added at 04:52 PM ---------- Previous post was at 04:17 PM ----------
bennyboy2120 said:
I also went from 7.1.2 back to 7.1.1 March update still had the issue
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
nothing.. still on the loading screen
RedBlueGreen said:
Yeap will do. Might try an older version of twrp.img if nothing happens in 30mins
---------- Post added at 04:52 PM ---------- Previous post was at 04:17 PM ----------
nothing.. still on the loading screen
Click to expand...
Click to collapse
Weird. I don't know what could be causing it. I'll check partition chance maybe after going to o?
Sent from my Pixel XL using Tapatalk
bennyboy2120 said:
Weird. I don't know what could be causing it. I'll check partition chance maybe after going to o?
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
came across this..
https://forum.xda-developers.com/showpost.php?p=72452371&postcount=1769
and this is the thread on how to do it.. (dont understand it)
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
not sure if it has anything to do with it.
---------- Post added at 05:41 PM ---------- Previous post was at 05:22 PM ----------
im in a bootloop now..
dont think ill be able to get out of it
RedBlueGreen said:
came across this..
https://forum.xda-developers.com/showpost.php?p=72452371&postcount=1769
and this is the thread on how to do it.. (dont understand it)
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
not sure if it has anything to do with it.
---------- Post added at 05:41 PM ---------- Previous post was at 05:22 PM ----------
im in a bootloop now..
dont think ill be able to get out of it
Click to expand...
Click to collapse
I'm looking into the VBS now, also looking at partition differences because of the O beta
Sent from my Pixel XL using Tapatalk
bennyboy2120 said:
I'm looking into the VBS now, also looking at partition differences because of the O beta
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
fixed my bootloop... thought i messed up really bad.. Gonna leave it for now.. giving me a headache.
Let me know if you find a fix please <3
It is happening when you revert from O back to N. Now I'm sure most of this is overkill but not sure which part actually resolved it. Here's how I fixed it -
in recovery, format userdata via fastboot (i actually did erase data first, then format data)
switch to the other slot and do the same
Flash latest N factory image
reboot to welcome screen
reboot into recovery
switch to other slot and flashed latest N factory image again (overkill, I know)
reboot to welcome screen
reboot to bootloader
set twrp as boot image and it will boot successfully into temporary twrp
install twrp zip
install the image signer zip
restart to welcome screen
restart to recovery
do steps 1 and 2 again
restart
profit
If you need more specific instructions, let me know and I'll type it out and make it more clear. Good luck.
mattyb65 said:
It is happening when you revert from O back to N. Now I'm sure most of this is overkill but not sure which part actually resolved it. Here's how I fixed it -
in recovery, format userdata via fastboot (i actually did erase data first, then format data)
switch to the other slot and do the same
Flash latest N factory image
reboot to welcome screen
reboot into recovery
switch to other slot and flashed latest N factory image again (overkill, I know)
reboot to welcome screen
reboot to bootloader
set twrp as boot image and it will boot successfully into temporary twrp
install twrp zip
install the image signer zip
restart to welcome screen
restart to recovery
do steps 1 and 2 again
restart
profit
If you need more specific instructions, let me know and I'll type it out and make it more clear. Good luck.
Click to expand...
Click to collapse
What's the command to swap to the other partition? Thank you!!!
Sent from my Pixel XL using Tapatalk
mattyb65 said:
It is happening when you revert from O back to N. Now I'm sure most of this is overkill but not sure which part actually resolved it. Here's how I fixed it -
in recovery, format userdata via fastboot (i actually did erase data first, then format data)
switch to the other slot and do the same
Flash latest N factory image
reboot to welcome screen
reboot into recovery
switch to other slot and flashed latest N factory image again (overkill, I know)
reboot to welcome screen
reboot to bootloader
set twrp as boot image and it will boot successfully into temporary twrp
install twrp zip
install the image signer zip
restart to welcome screen
restart to recovery
do steps 1 and 2 again
restart
profit
If you need more specific instructions, let me know and I'll type it out and make it more clear. Good luck.
Click to expand...
Click to collapse
any chance you could list all the commands?
bennyboy2120 said:
What's the command to swap to the other partition? Thank you!!!
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
to set it to A: fastboot --set-active=_a
to set it to B: fastboot --set-active=_b
---------- Post added at 03:59 PM ---------- Previous post was at 03:57 PM ----------
RedBlueGreen said:
any chance you could list all the commands?
Click to expand...
Click to collapse
Yeah - give me a bit and ill type it out.
---------- Post added at 04:26 PM ---------- Previous post was at 03:59 PM ----------
Ok - here's the list. Let me know if you run into any issues
in recovery, format userdata via fastboot (i actually did erase data first, then format data)
fastboot erase userdata
fastboot format userdata
switch to the other slot and do the same
fastboot --set-active=_a
Flash latest N factory image downloaded from here: https://developers.google.com/android/images I used N2G47O
fastboot flash bootloader bootloader-marlin-8996-012001-1703151359.img
fastboot reboot-bootloader
fastboot flash radio radio-marlin-8996-012901-1702171013.img
fastboot reboot-bootloader
fastboot -w update image-marlin-n2g47o.zip
reboot to welcome screen
fastboot reboot
reboot into recovery
switch to other slot and flashed latest N factory image again (overkill, I know)
fastboot --set-active=_b
fastboot flash bootloader bootloader-marlin-8996-012001-1703151359.img
fastboot reboot-bootloader
fastboot flash radio radio-marlin-8996-012901-1702171013.img
fastboot reboot-bootloader
fastboot -w update image-marlin-n2g47o.zip
reboot to welcome screen
fastboot reboot
reboot to bootloader
download RC1 image from here https://dl.twrp.me/marlin/ and set twrp as boot image
fastboot boot twrp-3.0.2-0-RC1-fastboot-marlin.img
once it boots into temporary TWRP, click on install and navigate to RC2 twrp zip
install the verified boot signer zip in TWRP(attached)
restart to welcome screen
restart to recovery
do steps 1 and 2 again
restart
fastboot reboot
profit
mattyb65 said:
to set it to A: fastboot --set-active=_a
to set it to B: fastboot --set-active=_b
---------- Post added at 03:59 PM ---------- Previous post was at 03:57 PM ----------
Yeah - give me a bit and ill type it out.
---------- Post added at 04:26 PM ---------- Previous post was at 03:59 PM ----------
Ok - here's the list. Let me know if you run into any issues
in recovery, format userdata via fastboot (i actually did erase data first, then format data)
fastboot erase userdata
fastboot format userdata
switch to the other slot and do the same
fastboot --set-active=_a
Flash latest N factory image downloaded from here: https://developers.google.com/android/images I used N2G47O
fastboot flash bootloader bootloader-marlin-8996-012001-1703151359.img
fastboot reboot-bootloader
fastboot flash radio radio-marlin-8996-012901-1702171013.img
fastboot reboot-bootloader
fastboot -w update image-marlin-n2g47o.zip
reboot to welcome screen
fastboot reboot
reboot into recovery
switch to other slot and flashed latest N factory image again (overkill, I know)
fastboot --set-active=_b
fastboot flash bootloader bootloader-marlin-8996-012001-1703151359.img
fastboot reboot-bootloader
fastboot flash radio radio-marlin-8996-012901-1702171013.img
fastboot reboot-bootloader
fastboot -w update image-marlin-n2g47o.zip
reboot to welcome screen
fastboot reboot
reboot to bootloader
download RC1 image from here https://dl.twrp.me/marlin/ and set twrp as boot image
fastboot boot twrp-3.0.2-0-RC1-fastboot-marlin.img
once it boots into temporary TWRP, click on install and navigate to RC2 twrp zip
install the verified boot signer zip in TWRP(attached)
restart to welcome screen
restart to recovery
do steps 1 and 2 again
restart
fastboot reboot
profit
Click to expand...
Click to collapse
You the man!!!!
Sent from my Pixel XL using Tapatalk
mattyb65 said:
to set it to A: fastboot --set-active=_a
to set it to B: fastboot --set-active=_b
---------- Post added at 03:59 PM ---------- Previous post was at 03:57 PM ----------
Yeah - give me a bit and ill type it out.
---------- Post added at 04:26 PM ---------- Previous post was at 03:59 PM ----------
Ok - here's the list. Let me know if you run into any issues
in recovery, format userdata via fastboot (i actually did erase data first, then format data)
fastboot erase userdata
fastboot format userdata
switch to the other slot and do the same
fastboot --set-active=_a
Flash latest N factory image downloaded from here: https://developers.google.com/android/images I used N2G47O
fastboot flash bootloader bootloader-marlin-8996-012001-1703151359.img
fastboot reboot-bootloader
fastboot flash radio radio-marlin-8996-012901-1702171013.img
fastboot reboot-bootloader
fastboot -w update image-marlin-n2g47o.zip
reboot to welcome screen
fastboot reboot
reboot into recovery
switch to other slot and flashed latest N factory image again (overkill, I know)
fastboot --set-active=_b
fastboot flash bootloader bootloader-marlin-8996-012001-1703151359.img
fastboot reboot-bootloader
fastboot flash radio radio-marlin-8996-012901-1702171013.img
fastboot reboot-bootloader
fastboot -w update image-marlin-n2g47o.zip
reboot to welcome screen
fastboot reboot
reboot to bootloader
download RC1 image from here https://dl.twrp.me/marlin/ and set twrp as boot image
fastboot boot twrp-3.0.2-0-RC1-fastboot-marlin.img
once it boots into temporary TWRP, click on install and navigate to RC2 twrp zip
install the verified boot signer zip in TWRP(attached)
restart to welcome screen
restart to recovery
do steps 1 and 2 again
restart
fastboot reboot
profit
Click to expand...
Click to collapse
Where is the Verified Bootloader?
[/COLOR]
bennyboy2120 said:
Where is the Verified Bootloader?
Click to expand...
Click to collapse
last download link.. install it after you install RC2
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
cant get root to work.. always bootloops..
RedBlueGreen said:
[/COLOR]
last download link.. install it after you install RC2
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
cant get root to work.. always bootloops..
Click to expand...
Click to collapse
how are you trying to root?
RedBlueGreen said:
[/COLOR]
last download link.. install it after you install RC2
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
cant get root to work.. always bootloops..
Click to expand...
Click to collapse
You need to flash the boot signer zip. This has been covered in many threads.
https://forum.xda-developers.com/an...-boot-images-android-verified-t3600606/page16
Hi. Sorry for my bad english..
I'm trying to root and setup the TWRP...
When I have install and enter the TWRP I don't have any storage and I can't Backup... And I can't install Magisk... I'm stuck...
Pic.
Someone have a solution?
Regards
you can try different things?
format data partition using twrp.
If that didnt work try flash stock recovery and erase everyting.
Or ompletely reflash everything:
i dont know... but you can try to put this zip (http://oxygenos.oneplus.net.s3.amazonaws.com/O2N_OBT_17801_OXYGEN_SIGN_wipe.zip.zip) on your phone then flash stock recovery and then flash this downloaded zip... it will install OOS 4.7.5 from there reinstall to whatever you were on... But this method will erase everything on your phone!
Going cracy :\ What am I doing wrong?
0kk0 said:
you can try different things?
format data partition using twrp.
If that didnt work try flash stock recovery and erase everyting.
Or ompletely reflash everything:
i dont know... but you can try to put this zip (http://oxygenos.oneplus.net.s3.amazonaws.com/O2N_OBT_17801_OXYGEN_SIGN_wipe.zip.zip) on your phone then flash stock recovery and then flash this downloaded zip... it will install OOS 4.7.5 from there reinstall to whatever you were on... But this method will erase everything on your phone!
Click to expand...
Click to collapse
Thanks for awnser. I will try
Every time I want to get in to TWRP I need to install it again, every time... "fastboot flash recovery twrp.img" ...
BTW The first problem I got was to install the ADB setup and get the files to show up on my c: drive... I think I give up.
SweDunda said:
Every time I want to get in to TWRP I need to install it again, every time... "fastboot flash recovery twrp.img" ...
BTW The first problem I got was to install the ADB setup and get the files to show up on my c: drive... I think I give up.
Click to expand...
Click to collapse
yeah me 2... i also installed drivers then files showed up in windows explorer
And twrp will be replaced on boot/reboot unless you root after flashing twrp with something like magisk...
Can someone please give me a "IDIOT proof" "HOW TO GUIDE" to me ?
Once you're on TWRP, did you flash Magisk just after, before rebooting on system?
If not, you lose twrp at every reboot. You'll be on stock recovery systematically.
abel06 said:
Once you're on TWRP, did you flash Magisk just after, before rebooting on system?
If not, you lose twrp at every reboot. You'll be on stock recovery systematically.
Click to expand...
Click to collapse
The thing is I can't flash anything. My device have no free space. I can't even backup. look at the pics in the first post.
Ah ok, thanks.
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase boot
fastboot erase recovery
And flash this one via fastboot: https://forum.xda-developers.com/oneplus-5/development/twrp-oneplus-5-wip-t3626134
EugenStanis said:
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase boot
fastboot erase recovery
And flash this one via fastboot: https://forum.xda-developers.com/oneplus-5/development/twrp-oneplus-5-wip-t3626134
Click to expand...
Click to collapse
Thanks. But can you explain little more in detail how I´m doing that? It was over 5 years ago I done this things
https://youtu.be/X1D4PhdhAac
What is my problem? :/
**** ME!!!! It will not boot now.... Spinning boot logo... I hope I not bricked it now
what i would do is flash stock recovery... and then format everything
Then flash rom or restore twrp backup or whatever..
i also had this prblem btw
---------- Post added at 07:29 PM ---------- Previous post was at 07:28 PM ----------
i can if you want describe it more if you are noob? joking
0kk0 said:
what i would do is flash stock recovery... and then format everything
Then flash rom or restore twrp backup or whatever..
i also had this prblem btw
---------- Post added at 07:29 PM ---------- Previous post was at 07:28 PM ----------
i can if you want describe it more if you are noob? joking
Click to expand...
Click to collapse
Please tell me how I do that in the best way? A little stressed up now
SweDunda said:
Please tell me how I do that in the best way? A little stressed up now
Click to expand...
Click to collapse
Download:
1) MINIMAL ADB & FASTBOOT : https://goo.gl/UbFXdA
2) STOCK OOS FILE : http://oxygenos.oneplus.net.s3.amazonaws.com/O2N_OBT_17801_OXYGEN_SIGN_wipe.zip.zip
this is nougat 4.7.5 if i remember it correctly
3) Stock Recovery : https://goo.gl/2kmbB7
4) Flash stock recovery (fastboot flash recovery [recoveryfilename.img])
5) In recovery erase everyting incl personal data.
6) fastboot boot [twrpfilename.img]
This wil boot twrp once so you can place OOS rom in internal storage
7) reboot to recovery.. and install zip you just placed on phone.
8) reboot... if everything works, then reinstall twrp codeworkx or blu_spark
9) after flashing twrp...boot to twrp and flash magisk... this will root your phone and this way twrp will not be replaced after first boot with stock recovery.
10) let me know if you have questions or if it worked etc :good:
When I try to bootloader "Powerbutton + volumedown" it say "Your device is corrupt. It can't be trusted and will not boot" ..................... F.U.C.K meee!
try VOLUME UP + POWER
this should send you straight to fastboot
try unlocking your bootloader then is your first prioriy i think
---------- Post added at 07:57 PM ---------- Previous post was at 07:52 PM ----------
if that also doenst work check this thread: https://forum.xda-developers.com/oneplus-5t/help/device-corrupt-trusted-boot-t3718158
0kk0 said:
try VOLUME UP + POWER
this should send you straight to fastboot
try unlocking your bootloader then is your first prioriy i think
Click to expand...
Click to collapse
Thanks! yes I got in to Fastboot and trying to get it unlocked. The device trying to boot again but I do not think it can... Boot logo of death.
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
Has anyone tried to flash it? I remember there being an issue with the layout of our partitions and what not. Just thought I'd ask because it's pretty nice on my pixel 3.
https://developer.android.com/topic/generic-system-image/releases
can't download, when you put gmail ans password account there is the security code from usb? what is it? if you have other link ill be appreciated thanks
Oh that is weird, I've never seen that before.
Me too, I will try it but I can't find the file to download
I just tried flashing system and vbmeta and also did fastboot -w, but its showing android logo at boot screen, and animation is a bootloop. Luckily adb devices shows my phone, but unauthorized
Sparker0i said:
I just tried flashing system and vbmeta and also did fastboot -w, but its showing android logo at boot screen, and animation is a bootloop. Luckily adb devices shows my phone, but unauthorized
Click to expand...
Click to collapse
where you downloaded ? can you provide a functional link? thanks
iaio72 said:
where you downloaded ? can you provide a functional link? thanks
Click to expand...
Click to collapse
Official site where the Android 11 gsi is available
Sparker0i said:
Official site where the Android 11 gsi is available
Click to expand...
Click to collapse
Yes of course but download doesn't work...
iaio72 said:
Yes of course but download doesn't work...
Click to expand...
Click to collapse
Sure you can't download the arm64 + gms zip from here: https://developer.android.com/topic/generic-system-image/releases . I can download..
Sparker0i said:
Sure you can't download the arm64 + gms zip from here: https://developer.android.com/topic/generic-system-image/releases . I can download..
Click to expand...
Click to collapse
ok im flashed but at reboot the phone remain in "qualcomm crash dump test"
i think not is good for our op7t
iaio72 said:
ok im flashed but at reboot the phone remain in "qualcomm crash dump test"
i think not is good for our op7t
Click to expand...
Click to collapse
Not really in crashdump mode, but for me it was on bootloop at Android logo screen
i have the same issue i believe we need an updated version of vbmeta and a custom boot.img because i have been able to get it to boot but as previously stated before it just bootloops on the android screen
how did you flash the android 11 gsi and the vbmeta?
i flashed it via fastboot commands
I tried several times and still trying . with system.img and vbmeta.img from google stuck at boot screen (Android logo waiting on screen) . Other custom builds (like erfangsi) is giving qualcomm crash dump without google vbmeta . No lack to boot until now . BUt there are some successful boot videos on internet with especially xiaomi phones . I don't know it is real or not . As far as I know op7t %100 of treble compatible phone and it should work .
intana said:
I tried several times and still trying . with system.img and vbmeta.img from google stuck at boot screen (Android logo waiting on screen) . Other custom builds (like erfangsi) is giving qualcomm crash dump without google vbmeta . No lack to boot until now . BUt there are some successful boot videos on internet with especially xiaomi phones . I don't know it is real or not . As far as I know op7t %100 of treble compatible phone and it should work .
Click to expand...
Click to collapse
I don't mean to ask a obvious question that I'm sure you did after you flashed but did you try flashing then booting into recovery and wiping caches and reboot? Prob won't work but worth a try
SICKMADE said:
I don't mean to ask a obvious question that I'm sure you did after you flashed but did you try flashing then booting into recovery and wiping caches and reboot? Prob won't work but worth a try
Click to expand...
Click to collapse
Yes I did . But it didn't work . I am trying every new build and custom roms about op7t-hotdogb and op7tpro-hotdog also . As you know op7tpro's custom roms are running on op7t with some minor problems like fod . Thanks for the advice
SICKMADE said:
I don't mean to ask a obvious question that I'm sure you did after you flashed but did you try flashing then booting into recovery and wiping caches and reboot? Prob won't work but worth a try
Click to expand...
Click to collapse
lol long time no see dude remember you from way back in note 4 days
btw ive been trying to get this to work for a few days lol still trying hopeful it will work
with which fastboot commands did you flash the gsi and the vbmeta
---------- Post added at 08:47 AM ---------- Previous post was at 08:44 AM ----------
fastboot flash system_a GSI.img
fastboot flash system_b GSI.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
ChrisFeiveel84 said:
with which fastboot commands did you flash the gsi and the vbmeta
---------- Post added at 08:47 AM ---------- Previous post was at 08:44 AM ----------
fastboot flash system_a GSI.img
fastboot flash system_b GSI.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
after "fastboot reboot fastboot" and fastboot -w I used same commands and used system.img and vbmeta.img from the below link (it includes its own vbmeta.img and it says it is AVB verification disabled) then reboot recovery delete cache and data again .
"https://developer.android.com/preview/gsi-release-notes"