Related
Hi,
I get TWRP running on phone , but when I boot into recovery , I always get the Standard Recovery, only option being a factory reset. Have opted for this factory reset and that is exactly what I get, no TWRP :crying:
Thanks
Also if you reboot to recovery through TWRP itself, it won't stick? If not: Is rooting an option for you? If yes: Try Flashify and flash it through this nifty little app .
MickyFoley said:
If not: Is rooting an option for you? If yes: Try Flashify and flash it through this nifty little app .
Click to expand...
Click to collapse
Thanks,
Yes rooting is where I want to go by means of TWRP and flashing these
Marshmallow custom kernel for root — Link | File: STOCK-20a-ROOTED.zip (16.5 MB)
Click to expand...
Click to collapse
I did have Twrp running on this phone but had to reinstall the full 6.00kdz to get out of a bootloop and since then TWRP won't sick.
thanks
More than one way to skin a cat. went HERE chainfire Systemless Root 2.61 using Running TWRP from PC
Update on getting TWRP to stick. ......... I had success using following
adb reboot bootloader
Click to expand...
Click to collapse
fastboot flash recovery twrp-2.8.7.0-h815.img
Click to expand...
Click to collapse
When done, execute “fastboot reboot”
Click to expand...
Click to collapse
This happened to me, too. Here is what i did:
Boot your device into fastboot mode via adb, straight up boot to recovery ("fastboot boot twrp-2.8.7.0-h815.img"), transfer the recovery image to your device, then flash it from within TWRP (there is an option for that within the normal install menu, its called "install image" or something like that). Hope this helps, it did for me.
Edit: Just realized you already found a solution. Never mind.
Ive the same problem. I unlocked the bootloader by the official procedure. Then i tried to flash twrp but it doesnt install truly. It always appear the stock recovery. I tried also clockrecovery but nothing. No recovery wants to get installed. Pls help me i want a custom rom on my g4
use twrp v2.8.7.0 on 20A mm....... adb reboot bootloader, fastboot boot twrp-2.8.7.0-h815.img, and to double check you have recovery,adb reboot recovery and then flash STOCK-20a-ROOTED
chester2011 said:
use twrp v2.8.7.0 on 20A mm....... adb reboot bootloader, fastboot boot twrp-2.8.7.0-h815.img, and to double check you have recovery,adb reboot recovery
Click to expand...
Click to collapse
Ok the one i tried is the newest. Ill gonna try the one u told me. But the line u wrote wont install twrp it will only boot it
setaf said:
Ok the one i tried is the newest. Ill gonna try the one u told me. But the line u wrote wont install twrp it will only boot it
Click to expand...
Click to collapse
sorry, fastboot flash recovery twrp-2.8.7.0-h815.img, instead of fastboot boot twrp-2.8.7.0-h815.img worked for me after hours and hours of boot loops and restoring
chester2011 said:
sorry, fastboot flash recovery twrp-2.8.7.0-h815.img, instead of fastboot boot twrp-2.8.7.0-h815.img worked for me after hours and hours of boot loops and restoring
Click to expand...
Click to collapse
Also u had problem with the 3.0 ? Ill update you later
setaf said:
Also u had problem with the 3.0 ? Ill update you later
Click to expand...
Click to collapse
yep.. but currently running with xposed and g4 tweaksbox (paid version) nicely
ok update:
finaly i got twrp 2.8.7.0 on my g4 (thanx chester) but i still cannot flash cyanogen.
when i try to do it by recovery i get the error message 7 then when i start the system im in damn bootloop
what i can do ?
flash twrp version 3.0.2.0
setaf said:
ok update:
finaly i got twrp 2.8.7.0 on my g4 (thanx chester) but i still cannot flash cyanogen.
when i try to do it by recovery i get the error message 7 then when i start the system im in damn bootloop
what i can do ?
Click to expand...
Click to collapse
you can upgrade twrp with the twrp manager from playstore (once youve got twrp and root of course)
I'm trying flash trwp so I can back up the stock mm that I'm on and I wanted to flash the cm13 with mm blobs.
After flashing twrp and I try to go into recovery it just shows the android guy with a ! Icon above him.
I tried using Asus unlock tool apk but it fails and closes.
The for reading.
Look for the modder tool by giovix in general section , easy as pie
timbernot said:
Look for the modder tool by giovix in general section , easy as pie
Click to expand...
Click to collapse
Thx, I'll take a looksie!
timbernot said:
Look for the modder tool by giovix in general section , easy as pie
Click to expand...
Click to collapse
I just tried it and it seemed everything worked ok and flashed twrp. when i get in to bootloader and try to load into recovery it restarts and shows this https://www.google.ca/search?q=reco...hWFWh4KHW0rDPAQ_AUIBygC#imgrc=P6Av23J5FPR39M:
Hmmm, boot back to bootloader and try again ?
Mine work first time.
You did put the unzipped folder straight in C/: drive like advised? And run as admin ?
timbernot said:
Hmmm, boot back to bootloader and try again ?
Mine work first time.
You did put the unzipped folder straight in C/: drive like advised? And run as admin ?
Click to expand...
Click to collapse
Everything flashed fine the first time. I'll give it another shot.
timbernot said:
Hmmm, boot back to bootloader and try again ?
Mine work first time.
You did put the unzipped folder straight in C/: drive like advised? And run as admin ?
Click to expand...
Click to collapse
I just tried that and I get the same error. The fastboot verify shows my phone is connected.
For some reason I don't think its fully unlocking my bootloader.
It will start to flash but at the end it says failed https://gyazo.com/2025260de02c9ffa6c3a5b9f1663c5a2
I then can proceed to install the splash screen to turn it back to black and exit. When I try to boot in bootloader and goto recovery I then get https://www.google.ca/search?q=reco...hWFWh4KHW0rDPAQ_AUIBygC#imgrc=P6Av23J5FPR39M:
Not too sure what's going on here , relating to your initial problem maybe ?
Drivers installed correctly etc..
This tool just works for me..
You got "minimal adb and fastboot" installed before this tool and working fine ???
Can u power off from bootloader ...Then use hard buttons to get to recovery ?
Just a thought.
Flash stock mm recovery back first if not got and try again.
timbernot said:
Not too sure what's going on here , relating to your initial problem maybe ?
Drivers installed correctly etc..
This tool just works for me..
You got "minimal adb and fastboot" installed before this tool and working fine ???
Can u power off from bootloader ...Then use hard buttons to get to recovery ?
Just a thought.
Flash stock mm recovery back first if not got and try again.
Click to expand...
Click to collapse
Yup I can do all that, I'm on stock mm atm also.
quarterbreed said:
Yup I can do all that, I'm on stock mm atm also.
Click to expand...
Click to collapse
Good news that
Be done with it then by flashing stock recovery then sideload another fresh copy of firmware.
Then , use the modder
timbernot said:
Good news that
Be done with it then by flashing stock recovery then sideload another fresh copy of firmware.
Then , use the modder
Click to expand...
Click to collapse
I'm not sure what you mean. How do I flash stock recovery. And why would I have to reflash stock mm?
To start from fresh
Just in case you damaged any sectors flashing earlier what caused the initial problem you posted.
You need to fastboot flash stock recovery from boot loader screen . Boot into stock recovery then select 'update over adb'
Then sideload from PC which sends firmware to phone.
Then you will be back to clean factory settings.
Fastboot commands is >
fastboot flash recovery recovery.img
Putting stock recovery in adb/fastboot folder first and renaming it to 'recovery'
adb commands in stock recovery is >
adb sideload MOFD_SDUPDATE.zip
Renaming , stock ASUS firmware .134 to MOFD_SDUPDATE
and putting it in adb/ fastboot folder first.
Refresh this page later I will add some more info as I am stuck for time at the min ...
Or someone might come along and help further ?
timbernot said:
To start from fresh
Just in case you damaged any sectors flashing earlier what caused the initial problem you posted.
You need to fastboot flash stock recovery from boot loader screen . Boot into stock recovery then select 'update over adb'
Then sideload from PC which sends firmware to phone.
Then you will be back to clean factory settings.
Fastboot commands is >
fastboot flash recovery recovery.img
Putting stock recovery in adb/fastboot folder first and renaming it to 'recovery'
adb commands in stock recovery is >
adb sideload MOFD_SDUPDATE.zip
Renaming , stock ASUS firmware .134 to MOFD_SDUPDATE
and putting it in adb/ fastboot folder first.
Refresh this page later I will add some more info as I am stuck for time at the min ...
Or someone might come along and help further ?
Click to expand...
Click to collapse
Thx Ill have to give it a try when i have some time. So I cant flash twrp with the current stock MM. I should probably wait for the cm14 release to go through all that then.
Adb and fastboot knowledge is usually required when unlocking bootloader and flashing recoveries
Enjoy
timbernot said:
Adb and fastboot knowledge is usually required when unlocking bootloader and flashing recoveries
Enjoy
Click to expand...
Click to collapse
when i do fastboot flash recovery (name of twrp.img) it flashes but when I try to get in to recovery i get that command android picture :[
And ?
What about what you have already been advised ?
Hi. Im stucked at fastboot... I have no OS and no TWRP.... on oneplus 2 it happen to me and I used a tool called FIRST AID, but for op3 it does not exist. I tried flash twrp by fastboot, it says success but when I boot to fastboot, I get a black screen.... Please help me
Im sorry to say this. But r.i.p oneplus 3
Sent from my ONEPLUS A3000 using XDA-Developers mobile app
please help me!
infamouzwt said:
Im sorry to say this. But r.i.p oneplus 3
Sent from my ONEPLUS A3000 using XDA-Developers mobile app
Click to expand...
Click to collapse
thats not true.....
Which TWRP are you flashing and what rom were you on before the speed bump
NZnewbie said:
Which TWRP are you flashing and what rom were you on before the speed bump
Click to expand...
Click to collapse
Hi. My rom before was freedom OS.... I tried twrp 3.0.2.0 and twrp 3.0.2.1 and stock recovery....
tuga49 said:
Hi. My rom before was freedom OS.... I tried twrp 3.0.2.0 and twrp 3.0.2.1 and stock recovery....
Click to expand...
Click to collapse
Try the modified 3.0.2-19 twrp. Search XDA for it. It's all over.
Don't panic, i had the same issue yesterday. but try to search for the 3.0.2.19 verison of TWRP and flash it with fastboot.
Flash His recovery From here Via CMD OR anytoolkit
Than Move a flashable 3.2.4 on Your Mobile Via Usb (Going Recoverymode first)
Than Install 3.2.4 reboot my be its work...
Nilshalok said:
Flash His recovery From here Via CMD OR anytoolkit
Than Move a flashable 3.2.4 on Your Mobile Via Usb (Going Recoverymode first)
Than Install 3.2.4 reboot my be its work...
Click to expand...
Click to collapse
hi. it says success flashed on cmd, but when I boot to recovery, it just show me a black screen!
abuddlah said:
Don't panic, i had the same issue yesterday. but try to search for the 3.0.2.19 verison of TWRP and flash it with fastboot.
Click to expand...
Click to collapse
Hi. I don't find any twrp with version 3.0.2.19... please help me.
Unbrick tool
Just look here it did help me in nearly the same situation:
http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
Hi! thank you all! I solved the problem flashing twrp with version 3.0.2.19! thank you all!
tuga49 said:
hi. it says success flashed on cmd, but when I boot to recovery, it just show me a black screen!
Click to expand...
Click to collapse
are you Trying 3.5.2???
Having a similar issue. I'm on 3.5.2 unlocked bootloader, no root, stock recovery. Everytime I try to flash TWRP, it appears to succeed, but will never boot to TWRP. Boots fastboot and OOS just fine, but no recovery available. I then tried to flash stock recovery, but same issue appears. I then was able to use skipsoft toolkit to get stock recovery, but only by relocking then unlocking the bootloader. Everytime I tried to simply flash a recovery it appears to succeed, but will not boot to recovery. So skipsoft was able to fix the no recovery problem, but I am still unable to flash TWRP
Mansquatch312 said:
Having a similar issue. I'm on 3.5.2 unlocked bootloader, no root, stock recovery. Everytime I try to flash TWRP, it appears to succeed, but will never boot to TWRP. Boots fastboot and OOS just fine, but no recovery available. I then tried to flash stock recovery, but same issue appears. I then was able to use skipsoft toolkit to get stock recovery, but only by relocking then unlocking the bootloader. Everytime I tried to simply flash a recovery it appears to succeed, but will not boot to recovery. So skipsoft was able to fix the no recovery problem, but I am still unable to flash TWRP
Click to expand...
Click to collapse
Here is the issue. 3.5.2 has a different firmware than previous OOS versions. You will need a specific 3.5.2 modified TWRP. The link is here:
http://forum.xda-developers.com/attachment.php?attachmentid=3875375&d=1473889816
You can see that this is discussed on the oneplus forums here: https://forums.oneplus.net/threads/...ity-update-with-working-twrp-recovery.465353/
I ran into this same problem myself, and realized that this was the issue. You should be very careful because it could cause you some grief. Whatever you do don't lock your bootloader if you end up with a nonfunctional and non functional recovery.
I have the same issue i can flash all the recovery images but non of them worked i tried 1000 different methods and nothing works.. Getting a bit desperate is someone please able to help me got my new phone already broke it kinda..
Saqrez said:
I have the same issue i can flash all the recovery images but non of them worked i tried 1000 different methods and nothing works.. Getting a bit desperate is someone please able to help me got my new phone already broke it kinda..
Click to expand...
Click to collapse
I suggest you to refer to the post of @gmarondel :
gmarondel said:
Just look here it did help me in nearly the same situation:
http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
Click to expand...
Click to collapse
Follow this guide and everything will be ok.
I know u fixed the problem but i think this is a general guide to fix your phone if you have this type of issue after flashing OOS 3.5.6 based roms!
i had the same issue yesterday with freedom os 1.7 (based on OOS 3.5.6) and OOS 3.5.6, here is how i fixed my phone:
- download http://forum.xda-developers.com/attachment.php?attachmentid=3875375&d=1473889816
-unzip it and put it on the desktop
-put your phone in fastboot (make sure you have unloked bootloader and installed all the drivers and adb on your pc)
-press shift and right mouse click on the desktop and hit open a new prompt window here
-write "fastboot boot twrp-3.0.2-19-oneplus3.img" and press enter, your phone should reboot in recovery (keep the prompt open)
-wipe dalvik/system/data/cache/internal storage go back and do format data
-reboot in bootloader(fastboot)
-write in the prompt "fastboot flash recovery twrp-3.0.2-19-oneplus3.img"
-unplug your phone and turn it off switching in fastboot with the volume buttons
-when it's powered off press power+volume down and chose recovery
-now you should boot and flash any rom in recovery (i suggest you to not try to flash any OOS 3.5.6 based roms)
i went back to OOS 3.2.6 but any other custom rom lshould be fine!
Vexo_ said:
I know u fixed the problem but i think this is a general guide to fix your phone if you have this type of issue after flashing OOS 3.5.6 based roms!
i had the same issue yesterday with freedom os 1.7 (based on OOS 3.5.6) and OOS 3.5.6, here is how i fixed my phone:
- download http://forum.xda-developers.com/attachment.php?attachmentid=3875375&d=1473889816
-unzip it and put it on the desktop
-put your phone in fastboot (make sure you have unloked bootloader and installed all the drivers and adb on your pc)
-press shift and right mouse click on the desktop and hit open a new prompt window here
-write "fastboot boot twrp-3.0.2-19-oneplus3.img" and press enter, your phone should reboot in recovery (keep the prompt open)
-wipe dalvik/system/data/cache/internal storage go back and do format data
-reboot in bootloader(fastboot)
-write in the prompt "fastboot flash recovery twrp-3.0.2-19-oneplus3.img"
-unplug your phone and turn it off switching in fastboot with the volume buttons
-when it's powered off press power+volume down and chose recovery
-now you should boot and flash any rom in recovery (i suggest you to not try to flash any OOS 3.5.6 based roms)
i went back to OOS 3.2.6 but any other custom rom lshould be fine!
Click to expand...
Click to collapse
I really appreciate your help but i think i fixed it. Today suddenly my phone went into recovery without doing anything except for 1000 methods. I am so happy that people like you are willing to help people.
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
Hello everyone,
after many hours of research I couldn't find anyone with the same problem or any solution for this.
Recently (yesterday) magisk brought out a new update 20.0 and I got a notification so I opened magisk manager and clicked on update magisk auto (recommended). After it updated successfuly, a reboot button appeared on right bottom corner and I clicked it. After it turned off and on it went directly to download mode and of top of the screen there was this error:
"partition vbmeta
Reason vbmeta: Error verifying vbmeta image:
0_0_INDIVLDVMT_EDRHS_IMTHSGAUEMSAC"
Screenshots:
https://prnt.sc/pigzsh
https://prnt.sc/pih0ax
And after like 3-5 times I hardreset (VOL DOWN + POWER) then immediately press VOL UP + POWER to come into magisk root mode again, the device boot but I have no root anymore. And there is no auto update choice anymore at magisk. I tried also patching the official firmware again and flash it but didn't work, I'm still not rooted and I get always many times to download mode with this error if I reboot the device.
Did anything go wrong during magisk auto update?
If yes, why it said "update success"?
Do I have to update magisk? I used the auto update method the first time and I am deep in trouble.
What should I do to fix this and getting rooted again?
If possible without losing my files/wipe data.
My device: Galaxy A70 (SM-A705FN/DS)
Android 9
Thanks in advance
HH
Hello !
Dont worry, same here. Just install the unofficial twrp from step 4 (flashing vbmeta)
https://forum.xda-developers.com/galaxy-a70/development/recovery-twrp-galaxy-a70-t3955984
Now your phone will be able to boot to twrp then to system
Follow step 5 for root.
I do that and my phone boot again and magisk updated.
You will lose nothing, easy and fast
Good luck !
PS : dont know Why we have this problem. But this solution work for me.
Vmbeta Image
Hello, could you please post the original stock vmbeta image, i can't get out of that screen in the screenshots without flashing it and i am very stressed.
Please help me?
xeedes said:
Hello, could you please post the original stock vmbeta image, i can't get out of that screen in the screenshots without flashing it and i am very stressed.
Please help me?
Click to expand...
Click to collapse
hello xeedes, what screen you have ?
the same as "partition vbmeta
Reason vbmeta: Error verifying vbmeta image:
0_0_INDIVLDVMT_EDRHS_IMTHSGAUEMSAC" ???
try twrp maybe ?
flash with odin.
what have you done to get screw to that screen ?
ps : i think this screen mean you have try to modify partition system with stock vbmeta. stock vbmeta does not allow modifications. maybe... i dont know exactly ^^
Ial69 said:
hello xeedes, what screen you have ?
the same as "partition vbmeta
Reason vbmeta: Error verifying vbmeta image:
0_0_INDIVLDVMT_EDRHS_IMTHSGAUEMSAC" ???
try twrp maybe ?
flash with odin.
what have you done to get screw to that screen ?
ps : i think this screen mean you have try to modify partition system with stock vbmeta. stock vbmeta does not allow modifications. maybe... i dont know exactly ^^
Click to expand...
Click to collapse
I tried to relock the bootloader when flashing a modified vbmeta, now its stuck and will only continue if i flash the stock vbmeta i assume. yes its the exact same screen and message and this phone won't let me flash anything :/ nor exit the screen with any key commands, just flashes a70 and immediately goes back to the said screen
xeedes said:
I tried to relock the bootloader when flashing a modified vbmeta, now its stuck and will only continue if i flash the stock vbmeta i assume. yes its the exact same screen and message and this phone won't let me flash anything :/ nor exit the screen with any key commands, just flashes a70 and immediately goes back to the said screen
Click to expand...
Click to collapse
I think you need custom recovery if you're stuck on this screen.
its a good news your phone boot in download mode and is detected by odin.
dont relock bootloader. (maybe... if you know what you do forget that ^^)
if you want stock vbmeta try to download all the stock rom from samfirm.
then flash all the stock rom ( if possible, verify the requirements)
hope this help.
ps : cant post link to samfirm because the forum lock me to post external link....(because im a new user)
and you need to have unlock your bootloader to flash, bad things can happens with a lock bootloader. like brick.
Ial69 said:
I think you need custom recovery if you're stuck on this screen.
its a good news your phone boot in download mode and is detected by odin.
dont relock bootloader. (maybe... if you know what you do forget that ^^)
if you want stock vbmeta try to download all the stock rom from samfirm.
then flash all the stock rom ( if possible, verify the requirements)
hope this help.
Click to expand...
Click to collapse
hey, thank you for the reply, i've tried flashing the stock rom but nothing happens. downloading it from samfirm though. im going to sleep. thank you for the help
its really that hard guys, no one can root this device without having vbmeta and magisk problems,
it has been 6 months since this phone released
emadhussein said:
its really that hard guys, no one can root this device without having vbmeta and magisk problems,
it has been 6 months since this phone released
Click to expand...
Click to collapse
never got problems like that , as long as you follow tutorial it's fine , a blank vbmeta image have to be flashed in order to bypass boot verifications like theses , it's not that hard...
I've attempted to flash the stock rom but when i do, i get this.
https://ibb.co/mqhCKfc
Any thoughts?
xeedes said:
I've attempted to flash the stock rom but when i do, i get this.
https://ibb.co/mqhCKfc
Any thoughts?
Click to expand...
Click to collapse
Reboot phone and pc. Then retry to flash TWRP. The phone will boot fine.
this work for me.
I root this phone with magisk at first time. no problem...
follow tuto.
for magisk :
https://forum.xda-developers.com/galaxy-a70/how-to/to-root-magisk-odin-t3930099
for TWRP :
https://forum.xda-developers.com/galaxy-a70/development/recovery-twrp-galaxy-a70-t3955984
i have vbmeta error too, bypass with TWRP. cant help you more than that, sorry....
BK said:
never got problems like that , as long as you follow tutorial it's fine , a blank vbmeta image have to be flashed in order to bypass boot verifications like theses , it's not that hard...
Click to expand...
Click to collapse
Everything was fine till magisk got update v20
I got vbmeta error in the download mood , even tho i flashed vbmeta file , any idea how to fix
emadhussein said:
Everything was fine till magisk got update v20
I got vbmeta error in the download mood , even tho i flashed vbmeta file , any idea how to fix
Click to expand...
Click to collapse
to update magisk you have to patch a recovery.img with magisk then install it with TWRP/odin.
just like the first time you get root with magsik ?
Ial69 said:
to update magisk you have to patch a recovery.img with magisk then install it with TWRP/odin.
just like the first time you get root with magsik ?
Click to expand...
Click to collapse
yes i did that, but i end up with vbmeta error , i flashed vbmeta but still
emadhussein said:
yes i did that, but i end up with vbmeta error , i flashed vbmeta but still
Click to expand...
Click to collapse
sorry, do you have try to install twrp ? he cause the vbmeta error ?
what odin says ?
Do you have reboot phone and pc before each try ?
need to uncheck autoreboot in odin too, like even.
Thanks for every answer, I didn't try flashing TWRP but I will try when I go home. Seems like it fix the problem for alot of people. Thanks guys I will tell you if it worked for me or not.
emadhussein said:
yes i did that, but i end up with vbmeta error , i flashed vbmeta but still
Click to expand...
Click to collapse
Better try flash twrp since it works for many.
Read all answers in this thread.
HornyHugo said:
Thanks for every answer, I didn't try flashing TWRP but I will try when I go home. Seems like it fix the problem for alot of people. Thanks guys I will tell you if it worked for me or not.
Better try flash twrp since it works for many.
Read all answers in this thread.
Click to expand...
Click to collapse
this is what i say from the beginning.
Ial69 said:
Hello !
Dont worry, same here. Just install the unofficial twrp from step 4 (flashing vbmeta)
https://forum.xda-developers.com/galaxy-a70/development/recovery-twrp-galaxy-a70-t3955984
Now your phone will be able to boot to twrp then to system
Follow step 5 for root.
I do that and my phone boot again and magisk updated.
You will lose nothing, easy and fast
Good luck !
PS : dont know Why we have this problem. But this solution work for me.
Click to expand...
Click to collapse
But step 4 says after flashing vbmeta.tar you need to go to recovery mode and wipe data. And this will make me lose all data. Do I need to flash vbmeta if I flash twrp?
HornyHugo said:
But step 4 says after flashing vbmeta.tar you need to go to recovery mode and wipe data. And this will make me lose all data. Do I need to flash vbmeta if I flash twrp?
Click to expand...
Click to collapse
If you already unlocked your bootloader, start with step 3.
If you are already rooted, start with step 4.
4 - Time to flash recovery. Download (link is at the end of this post) the latest version as zip and extract it. You should end up with one single file named recovery.img. Pack it as tar with 7zip or any other compression tool you prefer. This packed tar file should only contain recovery.img and nothing else, also make sure the name is still recovery.img, otherwise Odin will refuse to flash it. In Odin put the tar file in AP and simply hit start. Congrats you now have TWRP installed!
You begin from step 4. step 4 no need to wipe.
wipe is for step 3.
you are already unlock and rooted your phone if you have tried to update magisk and get stuck on vbmeta error.
ps : just do step 4. flashing recovery. then step 5 for root access ^^
good luck !
xeedes said:
I've attempted to flash the stock rom but when i do, i get this.
https://ibb.co/mqhCKfc
Any thoughts?
Click to expand...
Click to collapse
just connect your device to computer with cable and boot it with volume buttons