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"
Related
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
This is a GSI (generic system image) for AOKP for devices with treble support...
this requires fastboot to flash the system image, if you dont know how to use fastboot, you shouldnt be here...
Downloads
https://androidfilehost.com/?w=files&flid=261339
commands:
$: fastboot flash system_a system.img
(for pixel devices= $: fastboot flash vbmeta_a vbmeta.img)
then boot into twrp and wipe data and reboot.
tested on the Pixel 2 XL
credit goes to the AOKP gang and @phhusson who without i wouldnt have been able to compile this
screenshots:
https://ibb.co/dBnFPn
https://ibb.co/kvGEH7
https://ibb.co/hOLVqS
has GApps but no root, im working on that
First!
Sent from my Pixel 2 XL using Tapatalk
slothdabski said:
First!
Click to expand...
Click to collapse
Crap missed it..
sixohtew said:
This is a GSI (generic system image) for AOKP for devices with treble support...
this requires fastboot to flash the system image, if you dont know how to use fastboot, you shouldnt be here...
Downloads
https://androidfilehost.com/?w=files&flid=261339
commands:
$: fastboot flash system_a system.img
(for pixel devices= $: fastboot flash vbmeta_a vbmeta.img)
then boot into twrp and wipe data and reboot.
tested on the Pixel 2 XL
credit goes to the AOKP gang and @phhusson who without i wouldnt have been able to compile this
screenshots:
https://ibb.co/dBnFPn
https://ibb.co/kvGEH7
https://ibb.co/hOLVqS
has GApps but no root, im working on that
Click to expand...
Click to collapse
does google camera work with hdr+? do you get unlimited photo storage?
sixohtew said:
This is a GSI (generic system image) for AOKP for devices with treble support...
this requires fastboot to flash the system image, if you dont know how to use fastboot, you shouldnt be here...
Downloads
https://androidfilehost.com/?w=files&flid=261339
commands:
$: fastboot flash system_a system.img
(for pixel devices= $: fastboot flash vbmeta_a vbmeta.img)
then boot into twrp and wipe data and reboot.
tested on the Pixel 2 XL
credit goes to the AOKP gang and @phhusson who without i wouldnt have been able to compile this
screenshots:
https://ibb.co/dBnFPn
https://ibb.co/kvGEH7
https://ibb.co/hOLVqS
has GApps but no root, im working on that
Click to expand...
Click to collapse
We should all be here not everyone can do what you do..
I can't get twrp to load after flashing.....it just hangs at the start up screen. Any suggestions? I went back to stock and flashed over that.
cdnsnOw said:
We should all be here not everyone can do what you do..
Click to expand...
Click to collapse
What I meant was if you don't know how to use fastboot, you probably shouldn't be messing with your phone because you used the wrong code and bricked it..no offense
What is the difference flashing with TWRP and fastboot method?
So far no luck getting it to boot. This is what I did.
fastboot flash system_a system.img
fastboot flash vbmeta_a vbmeta.img
then boot into twrp and wipe data and reboot
Going to update to the leatest April image and try again.
gforceriders said:
So far no luck getting it to boot. This is what I did.
fastboot flash system_a system.img
fastboot flash vbmeta_a vbmeta.img
then boot into twrp and wipe data and reboot
Going to update to the leatest April image and try again.
Click to expand...
Click to collapse
Maybe after flashing vbmeta reboot bootloader then load up twrp
cdnsnOw said:
What is the difference flashing with TWRP and fastboot method?
Click to expand...
Click to collapse
This is a system.img and needs to be flashed to the system which requires fastboot..in twrp you MUST make sure you're flashing to the system_a partition
sixohtew said:
Maybe after flashing vbmeta reboot bootloader then load up twrp
Click to expand...
Click to collapse
Yeah did that still no luck getting it to boot. Can't even switch to slot A without getting an error after fastbooting the images.
abduleo77 said:
I can't get twrp to load after flashing.....it just hangs at the start up screen. Any suggestions? I went back to stock and flashed over that.
Click to expand...
Click to collapse
Try booting twrp right after the vbmeta.img
gforceriders said:
Yeah did that still no luck getting it to boot. Can't even switch to slot A without getting an error after fastbooting the images.
Click to expand...
Click to collapse
Which device? Pixel 2 xl?
sixohtew said:
Which device? Pixel 2 xl?
Click to expand...
Click to collapse
Yep, the pixel 2 XL.
gforceriders said:
Yep, the pixel 2 XL.
Click to expand...
Click to collapse
Did you come from another rom or were you stock? This boots just fine for me
sixohtew said:
Did you come from another rom or were you stock? This boots just fine for me
Click to expand...
Click to collapse
Yes, came from another rom and when that didn't work I went back to stock and still wouldn't boot.
gforceriders said:
Yes, came from another rom and when that didn't work I went back to stock and still wouldn't boot.
Click to expand...
Click to collapse
Does it bootloop? Or boot back to the bootloader? If it boot loops are you seeing the aokp boot animation? Could you possibly get a logcat?
sixohtew said:
Does it bootloop? Or boot back to the bootloader? If it boot loops are you seeing the aokp boot animation? Could you possibly get a logcat?
Click to expand...
Click to collapse
It bootloops. No aokp boot animation. I will try and use the bootloop fix script and flash full stock and test again here shortly.
gforceriders said:
It bootloops. No aokp boot animation. I will try and use the bootloop fix script and flash full stock and test again here shortly.
Click to expand...
Click to collapse
Yeah if you tried to flash it over another rom instead of stock, issues could arise..I'll put a script together that will flash stock with the new system.img and add the vbmeta.img to it so it flashes all the necessary files
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
So i was running Android 10 Nov update rooted WITHOUT TWRP
And i wanted to update to Dec update
So i DLed DEC update factory image took out the -w booted my phone into the bootloader flash-all
It does its thing phone boots up obvi now i dont have root.
I put the bootloader.img onto my phone go into Magisk manager and modify the bootloader then bring it back to the computer.
Boot the phone into bootloader
fastboot flash boot magisk_patched.img
fastboot reboot
phone gets stuck in the G logo with the loading bar
any hints????
after doing some researched i tried it again but this time flashing the patched boot.img to both a and b slots. Still same result
krolla03 said:
So i was running Android 10 Nov update rooted WITHOUT TWRP
And i wanted to update to Dec update
So i DLed DEC update factory image took out the -w booted my phone into the bootloader flash-all
It does its thing phone boots up obvi now i dont have root.
I put the bootloader.img onto my phone go into Magisk manager and modify the bootloader then bring it back to the computer.
Boot the phone into bootloader
fastboot flash boot magisk_patched.img
fastboot reboot
phone gets stuck in the G logo with the loading bar
any hints????
Click to expand...
Click to collapse
krolla03 said:
after doing some researched i tried it again but this time flashing the patched boot.img to both a and b slots. Still same result
Click to expand...
Click to collapse
You stated that you patched the bootloader.img, is that correct?? You need to patch the boot.img, or, was that just a typo on your part?
Did you disable all your magisk modules before you fastbooted the factory image?? If not, then it's very likely that one, or maybe more modules, isn't compatible with the December update. I'll wait for your reply before trying to help solve the problem.
I previously dealt with similar symptoms. You can read about it here -- https://forum.xda-developers.com/showpost.php?p=81102855&postcount=33
Badger50 said:
You stated that you patched the bootloader.img, is that correct?? You need to patch the boot.img, or, was that just a typo on your part?
Did you disable all your magisk modules before you fastbooted the factory image?? If not, then it's very likely that one, or maybe more modules, isn't compatible with the December update. I'll wait for your reply before trying to help solve the problem.
Click to expand...
Click to collapse
OK so stupid me yes i was patching and flashing the bootloader.img not the boot.img.
I just tried flashing the indeed patched boot.img and now im getting the same issue as rustnails. Where it gets stuck at the G logo for a few secs and reboots.
I did not uninstall or disable any of the magisk modulus
how do i do that now that i dont have root?
krolla03 said:
OK so stupid me yes i was patching and flashing the bootloader.img not the boot.img.
I just tried flashing the indeed patched boot.img and now im getting the same issue as rustnails. Where it gets stuck at the G logo for a few secs and reboots.
I did not uninstall or disable any of the magisk modulus
how do i do that now that i dont have root?
Click to expand...
Click to collapse
Fastboot into twrp. Go to advanced, select file manager, go to /data/adb/modules then delete each one of them. Reboot, then go back and fastboot your patched boot.img to regain root :good:
Badger50 said:
Fastboot into twrp. Go to advanced, select file manager, go to /data/adb/modules then delete each one of them. Reboot, then go back and fastboot your patched boot.img to regain root :good:
Click to expand...
Click to collapse
Ok. Before i try that let me just ask this.
Can i just temp boot TWRP to do that
I dont want to install TWRP permanently because ive had mostly trouble with TWRP in the last few android versions.
krolla03 said:
Ok. Before i try that let me just ask this.
Can i just temp boot TWRP to do that
I dont want to install TWRP permanently because ive had mostly trouble with TWRP in the last few android versions.
Click to expand...
Click to collapse
Yep. It'll just be temporary :good:
Badger50 said:
Yep. It'll just be temporary :good:
Click to expand...
Click to collapse
Thanks man. I got it all working again!!!
Hi badger, @Badger50 (Mod Edit: added mention tag)
i have an issue with rooting my device
when I write fastboot flash boot magisk_patched.img I get a message says < waiting for device >
can you please help me to find a solution to my problem?
dark_heroo said:
Hi badger, @Badger50 (Mod Edit: added mention tag)
i have an issue with rooting my device
when I write fastboot flash boot magisk_patched.img I get a message says < waiting for device >
can you please help me to find a solution to my problem?
Click to expand...
Click to collapse
Not sure what your starting point is but:
After installing you fastboot factory image
you can either temporarily or permanently install TWRP (temp TWRP= fastboot twrp.img, install magisk, reboot OR perm TWRP = fastboot twrp.img, install TWRP.zip from witin TWRP)
then you just flash/install magisk in TWRP
In my sig is a link to a detailed step by step guide for all this.
Good luck!
OnePlus 7T OxygenOS 11.0.1.1.HD65AA Global boot.img
Stock: https://mega.nz/file/GMtlFIwR#6-J_kxKul0N4KGcBUn0vilyMJqtiRpqdteEWZTWlAvo
Magisk v23.0 Patched: https://mega.nz/file/7QknRQaL#eWBYPAw4-x_DRdMiQRDOauSF_PNgQBOIVZXPu1kxrV0
thexile said:
OnePlus 7T OxygenOS 11.0.1.1.HD65AA Global boot.img
Stock: https://srv-store1.gofile.io/download/9sV6fm/e23f3ec51a5f37cb2b979cc77845fbf9/boot.img
Magisk v23.0 Patched: https://srv-store1.gofile.io/downlo...1f9a1476987252769df2/magisk_patched-23000.img
Click to expand...
Click to collapse
Thanks - just tried 11.0.1.1 - Works fine so far. https://forum.xda-developers.com/t/stable-oxygen-os-11-now-released.4250755/post-85078197 (screenies, etc)
thexile said:
OnePlus 7T OxygenOS 11.0.1.1.HD65AA Global boot.img
Stock: https://srv-store1.gofile.io/download/9sV6fm/e23f3ec51a5f37cb2b979cc77845fbf9/boot.img
Magisk v23.0 Patched: https://srv-store1.gofile.io/downlo...1f9a1476987252769df2/magisk_patched-23000.img
Click to expand...
Click to collapse
fastboot boot magisk.img gets me stuck in a boot loop. had the same issue with the last android 11 update
posiblyLopsided said:
fastboot boot magisk.img gets me stuck in a boot loop. had the same issue with the last android 11 update
Click to expand...
Click to collapse
Usually, "fastboot boot [image.img]" is done where you just wish to temporarily try/boot without flashing a self-sufficient image, like some version of TWRP. I'm not sure what your intent was. If it was to just do what we did ^^, and flash the patched image, the statement would be more like this:
First one is for example flashing magisk_patched.img to the B partition. I'd also flash it to the boot_a partition.
fastboot flash boot_b magisk_patched.img
fastboot flash boot_a magisk_patched.img
Or if a pre-dual-partitioning system, then fastboot flash boot {imagename}
hachamacha said:
Usually, "fastboot boot [image.img]" is done where you just wish to temporarily try/boot without flashing a self-sufficient image, like some version of TWRP. I'm not sure what your intent was. If it was to just do what we did ^^, and flash the patched image, the statement would be more like this:
First one is for example flashing magisk_patched.img to the B partition. I'd also flash it to the boot_a partition.
fastboot flash boot_b magisk_patched.img
fastboot flash boot_a magisk_patched.img
Or if a pre-dual-partitioning system, then fastboot flash boot {imagename}
Click to expand...
Click to collapse
i always boot before flashing in case smth like this happens like getting stuck in a boot loop then i dont risk losing data. is there a difference between flashing and booting that could cause it to boot loop?
Did dirty upgrade from 11.0.0.2 to 11.0.1.1. Took longer than usual to boot, but it booted up. Then did fastboot flast boot magisk_patched-23000.img (no _a or _b), rebooted, and got my root back. Went to store and paid with GPay.
Links are not working.
Can you please add any mirror
zaibansari20 said:
Links are not working.
Can you please add any mirror
Click to expand...
Click to collapse
Fixed
thexile said:
Fixed
Click to expand...
Click to collapse
Links are broken again, can you add a mirror
TurnrDev said:
Links are broken again, can you add a mirror
Click to expand...
Click to collapse
Here you go: https://gofile.io/d/L1u4hF
thexile said:
Here you go: https://gofile.io/d/L1u4hF
Click to expand...
Click to collapse
Link is dead, can you reupload please?
gmpetrov said:
Link is dead, can you reupload please?
Click to expand...
Click to collapse
96 MB file on MEGA
mega.nz
thexile said:
96 MB file on MEGA
mega.nz
Click to expand...
Click to collapse
Thx you. Can you share also the stock image please ?
gmpetrov said:
Thx you. Can you share also the stock image please ?
Click to expand...
Click to collapse
Check first post.
Meri flashl Kam nahin kar rahi sahi se