Develop Bugs

just flash twrp . lost fastboot

just got my pixel xl today. unlocked the bootloader fine.
next step flash twrp. i fastboot boot twrp img. temp twrp , installed the zip.. i reboot to recovery. that where everything F up.. now i can not get into fastboot.. is there a way for me to get fastboot mode back ??

never mind just had to reboot the phone 3 times..

Hello. I think I am near you. I was on the latest stock 7.1.2 of may. Unlocked bootloader ok. Then boot the TWRP and flash the TWRP zip. After that I have bootloop all time. I can put the phone in bootloader but now my phone is not recognised by the computer. The first time I connected the phone he asked me what to do and I said transfers data. But now I cannot do anything.
How did you get in fastboot mode???
Any idea how to help me???
I really appreciate help!!

sytayeth said:
Hello. I think I am near you. I was on the latest stock 7.1.2 of may. Unlocked bootloader ok. Then boot the TWRP and flash the TWRP zip. After that I have bootloop all time. I can put the phone in bootloader but now my phone is not recognised by the computer. The first time I connected the phone he asked me what to do and I said transfers data. But now I cannot do anything.
How did you get in fastboot mode???
Any idea how to help me???
I really appreciate help!!
Click to expand...
Click to collapse
Hello,
You need to read this post: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
The thread contains a zip (verified boot signer v2 zip) that you must install right after you install the TWRP zip on latest May version...
This is weird your phone is not recognized while in bootloader.
Boot the bootloader and issue:
fastboot devices
Does it output your serial number in the command prompt?
Good luck...

5.1 said:
Hello,
You need to read this post: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
The thread contains a zip (verified boot signer v2 zip) that you must install right after you install the TWRP zip on latest May version...
This is weird your phone is not recognized while in bootloader.
Boot the bootloader and issue:
fastboot devices
Does it output your serial number in the command prompt?
Good luck...
Click to expand...
Click to collapse
Thank for your answer. The real problem was that in fastboot the phone is not recognised. There were no serial number. And I write in past because I could made it work.
I am very happy you worried about me. You have a new friend in Spain.
Thanks.

sytayeth said:
Thank for your answer. The real problem was that in fastboot the phone is not recognised. There were no serial number. And I write in past because I could made it work.
I am very happy you worried about me. You have a new friend in Spain.
Thanks.
Click to expand...
Click to collapse
Hey,
No problem. Glad you solved it by yourself anyway. What was the issue? Maybe others with the same problem could benefit from your experience?
Why your computer didn't recognized your phone while in bootloader?
Cheers...

5.1 said:
Hey,
No problem. Glad you solved it by yourself anyway. What was the issue? Maybe others with the same problem could benefit from your experience?
Why your computer didn't recognized your phone while in bootloader?
Cheers...
Click to expand...
Click to collapse
I really don't know the problem. I was just about to cry when I saw a post about skipsoft toolkit. And I thought why not to try. I installed that software in other pc, follow the instructions and now I am here again.
Yesssss!!!!

sytayeth said:
I really don't know the problem. I was just about to cry when I saw a post about skipsoft toolkit. And I thought why not to try. I installed that software in other pc, follow the instructions and now I am here again.
Yesssss!!!!
Click to expand...
Click to collapse
You shouldn't be modding you're device if you have to rely on a toolkit to save you. What if there wasn't a toolkit. You'd be SOL.
I highly recommend you learn how to use fastboot and adb, and do this stuff the right way. I'm not trying to be mean or anything. I just would hate to see you brick you're device. These pixel phones cost way too much to be screwing around with if you don't know what you're doing.

toknitup420 said:
You shouldn't be modding you're device if you have to rely on a toolkit to save you. What if there wasn't a toolkit. You'd be SOL.
I highly recommend you learn how to use fastboot and adb, and do this stuff the right way. I'm not trying to be mean or anything. I just would hate to see you brick you're device. These pixel phones cost way too much to be screwing around with if you don't know what you're doing.
Click to expand...
Click to collapse
Thanks. I am trying to learn. Not only fastboot or adb. English too. But sometimes I am a bit risky or only stupid.
By the way, recommend me a post or a place to learn.

sytayeth said:
Thanks. I am trying to learn. Not only fastboot or adb. English too. But sometimes I am a bit risky or only stupid.
By the way, recommend me a post or a place to learn.
Click to expand...
Click to collapse
Honestly the best way I found to learn adb and fastboot is YouTube. It's so much easier to watch how to do it. Thats how I learned. There's also @Heisenberg 6p guide. That can get you all setup for adb and fastboot too. It's very comprehensive.
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928

toknitup420 said:
Honestly the best way I found to learn adb and fastboot is YouTube. It's so much easier to watch how to do it. Thats how I learned. There's also @Heisenberg 6p guide. That can get you all setup for adb and fastboot too. It's very comprehensive.
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
Thanks. I'll try.

Moto z play stuck in fastboot

So i kinda ****ed up on trying to install a custom rom, dint make a backup and had wrong bootloader for the rom i had planned. After trying different things to fix it. it went from bad to worse ( i think) and now im stuck in the fastboot menu. TWRP cannot boot up, it has error messages but it go's away fast so i cant see them.
Can i still recover my phone?

Somebodyz said:
So i kinda ****ed up on trying to install a custom rom, dint make a backup and had wrong bootloader for the rom i had planned. After trying different things to fix it. it went from bad to worse ( i think) and now im stuck in the fastboot menu. TWRP cannot boot up, it has error messages but it go's away fast so i cant see them.
Can i still recover my phone?
Click to expand...
Click to collapse
So do you have a backup of stock or anything?
If not, RSD lite latest 7.1.1 stock
https://forum.xda-developers.com/mo...ock-images-t3736767/post75236696#post75236696

KrisM22 said:
So do you have a backup of stock or anything?
If not, RSD lite latest 7.1.1 stock
https://forum.xda-developers.com/mo...ock-images-t3736767/post75236696#post75236696
Click to expand...
Click to collapse
Did not make a backup no, RSD doesnt see my phone though. how would i go about fixing it? Windows does see my phone as fastboost addison s

Somebodyz said:
Did not make a backup no, RSD doesnt see my phone though. how would i go about fixing it? Windows does see my phone as fastboost addison s
Click to expand...
Click to collapse
What version of RSD do you have - it's on the top bar when you stat RSD.

KrisM22 said:
What version of RSD do you have - it's on the top bar when you stat RSD.
Click to expand...
Click to collapse
the version is : RSD Lite v6.2.4 multi-flash / multiflex tool. is that the correct one?

Somebodyz said:
the version is : RSD Lite v6.2.4 multi-flash / multiflex tool. is that the correct one?
Click to expand...
Click to collapse
yes, now try a number of different cables. Make sure your phone is in fastboot mode.

That work?

KrisM22 said:
That work?
Click to expand...
Click to collapse
Tried to find, and failed in, finding other cables since this is the only phone with usb-c. are there other possibilites or should i buy a new cable?

Somebodyz said:
Tried to find, and failed in, finding other cables since this is the only phone with usb-c. are there other possibilites or should i buy a new cable?
Click to expand...
Click to collapse
Only reason I suggested that was because of second post on this thread
https://forum.xda-developers.com/mo...ock-images-t3736767/post75236696#post75236696
I did one a couple days ago with an old A to micro cable and a cheap ($3 for 5) Micro female to C male adapter that I got on ebay. Worked fine. Other than that I have no ideas. Sorry. I understand there may be some need to have cables with 56K ohm resisters if used for charging, but I don't have any of those yet - still using old stuff.

KrisM22 said:
Only reason I suggested that was because of second post on this thread
https://forum.xda-developers.com/mo...ock-images-t3736767/post75236696#post75236696
I did one a couple days ago with an old A to micro cable and a cheap ($3 for 5) Micro female to C male adapter that I got on ebay. Worked fine. Other than that I have no ideas. Sorry. I understand there may be some need to have cables with 56K ohm resisters if used for charging, but I don't have any of those yet - still using old stuff.
Click to expand...
Click to collapse
So i managed to get it to connect with a different cable (yeay), but i was wondering how much the stock rom version affects stuff? since there seem to be of stock roms to choose from. after ****ing it up i dont want to do that again.
moto z play
product/variant: addison xt1635-02 32gb p7
bootloader: c0.14 (sha-9325e5f, 2016-07-11)
Would anyone be able to give any pointers to what specific one i need?

Try to reflash the latest TWRP

mijing said:
Try to reflash the latest TWRP
Click to expand...
Click to collapse
if it try to boot it from cmd or if i try to reflash it, it says: cannot mount /data and unable to find crypto footer. on the top line. RSD Lite sees my phone now though, so do i need to reflash twrp?

Somebodyz said:
if it try to boot it from cmd or if i try to reflash it, it says: cannot mount /data and unable to find crypto footer. on the top line. RSD Lite sees my phone now though, so do i need to reflash twrp?
Click to expand...
Click to collapse
Did you unlock your bootloader before flashing the TWRP?
Twrp reflash is will not be damage our phone you can try it ?

mijing said:
Did you unlock your bootloader before flashing the TWRP?
Twrp reflash is will not be damage our phone you can try it
Click to expand...
Click to collapse
as i said i did try to reflash it and it gave me that message. and yea i did unlock the bootloader first.

Somebodyz said:
So i managed to get it to connect with a different cable (yeay), but i was wondering how much the stock rom version affects stuff? since there seem to be of stock roms to choose from. after ****ing it up i dont want to do that again.
moto z play
product/variant: addison xt1635-02 32gb p7
bootloader: c0.14 (sha-9325e5f, 2016-07-11)
Would anyone be able to give any pointers to what specific one i need?
Click to expand...
Click to collapse
Yay!!! cable!!! Who would have guessed!! Thanks @okaban !!!
Which one you choose depends mostly on which country or area you are in because flashing one from another country will mess things up (wrong radio frequencies). Then choose the latest one - never one earlier than where you were at. So what country/area are you in? and I'll try to help you choose.

KrisM22 said:
Yay!!! cable!!! Who would have guessed!! Thanks @okaban !!!
Which one you choose depends mostly on which country or area you are in because flashing one from another country will mess things up (wrong radio frequencies). Then choose the latest one - never one earlier than where you were at. So what country/area are you in? and I'll try to help you choose.
Click to expand...
Click to collapse
yea had to wait till today for the cables to arive, hence the delay.
But im from the netherlands (europe). and im guessing the one i was at is from 2016-07-11, atleast thats the date at the BL: message

Somebodyz said:
yea had to wait till today for the cables to arive, hence the delay.
But im from the netherlands (europe). and im guessing the one i was at is from 2016-07-11, atleast thats the date at the BL: message
Click to expand...
Click to collapse
Lots of questions for you to answer in here so read till end before start!
Okay. We need an expert (someone in Netherlands who has done it!!!)
I was thinking you were reteu and this post would agree
https://forum.xda-developers.com/showpost.php?p=72013707&postcount=126
though not totally certain.
The only rom I see for reteu is 24-104-25 which if you d/l and expand it (which I did) is 6.0.1 .
- - - - -
I didn't ask - are you able to boot to stock now?
- - - - - - -
Back to first post, you say you got error messages from twrp when you tried to flash a custom ROM. This would be typical if you were still on 6.x bootloader. and trying to flash a custom 8.x ROM.
So:
1) Had you ever updated stock (ota) to nougat?
2) did you go to motorola and unlock bootloader?
if no to update and yes to unlock, let's take @mijing 's idea and reflash TWRP, though I am going to suggest you go back in time a bit and flash this one:
https://androidfilehost.com/?fid=745425885120744582
That one will work for flashing 7.x custom ROMs and is the one I am using at the moment. It will not deal with 8.x custom ROMs but we can easily deal with that later.
To flash TWRP:
boot to fastboot on phone
connect via (good ) cable
On PC in terminal
To temporarily boot this recovery: (substitute actual name of TWRP you downloaded)
Code:
fastboot boot twrp.img
Don't reboot:
use vol up/dn to step to recovery and press power and see if it in fact boots to TWRP.
If it does, then boot back to bootloader and
To permanently flash it: again substitute correct name of img
Code:
fastboot flash recovery twrp.img
If that works that should get you going for flashing 7.x custom ROMs,
though if you want stock you would have to take a CHANCE and RSD that one above. If that works you would still have to flash TWRP. It would NOT affect your bootloader-unlock status.

KrisM22 said:
Lots of questions for you to answer in here so read till end before start!
Okay. We need an expert (someone in Netherlands who has done it!!!)
I was thinking you were reteu and this post would agree
https://forum.xda-developers.com/showpost.php?p=72013707&postcount=126
though not totally certain.
The only rom I see for reteu is 24-104-25 which if you d/l and expand it (which I did) is 6.0.1 .
- - - - -
I didn't ask - are you able to boot to stock now?
- - - - - - -
Back to first post, you say you got error messages from twrp when you tried to flash a custom ROM. This would be typical if you were still on 6.x bootloader. and trying to flash a custom 8.x ROM.
So:
1) Had you ever updated stock (ota) to nougat?
2) did you go to motorola and unlock bootloader?
if no to update and yes to unlock, let's take @mijing 's idea and reflash TWRP, though I am going to suggest you go back in time a bit and flash this one:
https://androidfilehost.com/?fid=745425885120744582
That one will work for flashing 7.x custom ROMs and is the one I am using at the moment. It will not deal with 8.x custom ROMs but we can easily deal with that later.
To flash TWRP:
boot to fastboot on phone
connect via (good ) cable
On PC in terminal
To temporarily boot this recovery: (substitute actual name of TWRP you downloaded)
Code:
fastboot boot twrp.img
Don't reboot:
use vol up/dn to step to recovery and press power and see if it in fact boots to TWRP.
If it does, then boot back to bootloader and
To permanently flash it: again substitute correct name of img
Code:
fastboot flash recovery twrp.img
If that works that should get you going for flashing 7.x custom ROMs,
though if you want stock you would have to take a CHANCE and RSD that one above. If that works you would still have to flash TWRP. It would NOT affect your bootloader-unlock status.
Click to expand...
Click to collapse
i dint make a backup at the start so i lost all OS. i dont think i updated the stock the nougat, and i dint know what it meant so i ignored it (basicly where this mess started)
and i did manage to flash the twrp you sent me.
and i dint really want stock i thought it would be better to go back to it.
i want this rom: https://forum.xda-developers.com/moto-z-play/development/rom-unofficial-cyanogenmod-14-1-t3495644
it says i need a nougat bootloader, do i have that now or do i still need to do stuff to get this rom?
(also a massive thanks for all of your help so far)

Somebodyz said:
i dint make a backup at the start so i lost all OS. i dont think i updated the stock the nougat, and i dint know what it meant so i ignored it (basicly where this mess started)
and i did manage to flash the twrp you sent me.
and i dint really want stock i thought it would be better to go back to it.
i want this rom: https://forum.xda-developers.com/moto-z-play/development/rom-unofficial-cyanogenmod-14-1-t3495644
it says i need a nougat bootloader, do i have that now or do i still need to do stuff to get this rom?
(also a massive thanks for all of your help so far)
Click to expand...
Click to collapse
This has all been re-written:
You're welcome! and thanks to @mijing !!!!!!
Wow - we got much further than I thought! Good work!!!
No, I believe you have a MM B/L,
The problem with the 7.x bootloader mod is that once you apply it I believe you can never RSD lite back to 6.0.1 or you will brick your phone and need to send it to Moto for blankflash. Course you may decide that's a moot point.
I don't know if LinOS 14 (7.x) needs a 7.x bootloader - I think I was wrong - I think it may indeed. LinOS 14 should be a good one for you to play with and should flash fine with that TWRP. I also highly recommend
https://forum.xda-developers.com/moto-z-play/development/rom-aospextended-rom-v4-6-amulyax-t3735010
which I flashed yesterday and love.
Both those should flash fine with the Deh TWRP you have on.
Keep us posted.
---------- Post added at 03:14 PM ---------- Previous post was at 03:05 PM ----------
@somebodyz I just redid the above post - a lot was wrong.

KrisM22 said:
This has all been re-written:
You're welcome! and thanks to @mijing !!!!!!
Wow - we got much further than I thought! Good work!!!
No, I believe you have a MM B/L,
The problem with the 7.x bootloader mod is that once you apply it I believe you can never RSD lite back to 6.0.1 or you will brick your phone and need to send it to Moto for blankflash. Course you may decide that's a moot point.
I don't know if LinOS 14 (7.x) needs a 7.x bootloader - I think I was wrong - I think it may indeed. LinOS 14 should be a good one for you to play with and should flash fine with that TWRP. I also highly recommend
https://forum.xda-developers.com/moto-z-play/development/rom-aospextended-rom-v4-6-amulyax-t3735010
which I flashed yesterday and love.
Both those should flash fine with the Deh TWRP you have on.
Keep us posted.
---------- Post added at 03:14 PM ---------- Previous post was at 03:05 PM ----------
@somebodyz I just redid the above post - a lot was wrong.
Click to expand...
Click to collapse
So adb devices doesnt let me see my device. but adb sideload works. only problem is, is: This package supports bootloaders: 0xc105, 0xC106, 0xC107, 0xC112, 0xC113 and this device has bootloader 0xc014. do i need an older version then or what should i do?
i just found this https://forum.xda-developers.com/showpost.php?p=74069195&postcount=91, is that a good thing for me to do?

Bricked device? Tried to downgrade to oreo help?

Hello, I tried downgrading today to oreo (from official version of pie) because I wanted to root and flash resuruction remix rom. I unlocked my bootloader and then I installed android oreo from the website for pixel 2 xl, copied the files into the adb directory and ran the "flash-all" batch file. But now my device is stuck at the google screen with the unlcoked lock image, before this screen it says that my device is corrupt. How can I solve this issue and go back to oreo?
Thanks

abdane said:
Hello, I tried downgrading today to oreo (from official version of pie) because I wanted to root and flash resuruction remix rom. I unlocked my bootloader and then I installed android oreo from the website for pixel 2 xl, copied the files into the adb directory and ran the "flash-all" batch file. But now my device is stuck at the google screen with the unlcoked lock image, before this screen it says that my device is corrupt. How can I solve this issue and go back to oreo?
Thanks
Click to expand...
Click to collapse
Please list your exact steps trying to flash back to Oreo.
Unless I am mistaken (it does happen) I was under the impression flashing the 8.1 factory image was all that's needed to return to stock Oreo.
List your steps/process (and files used) and let's see if someone can't help you out.

Initially, I unlocked my bootloader and data was wiped, then I installed android 8.1 (the recommended version from resuruction remix rom forum) and extracted the files into the directory of adb, then I ran "flash-all" and it was running, then at the end it showed a fail error and now my device is not booting up, I can only access fastboot mode

abdane said:
Hello, I tried downgrading today to oreo (from official version of pie) because I wanted to root and flash resuruction remix rom. I unlocked my bootloader and then I installed android oreo from the website for pixel 2 xl, copied the files into the adb directory and ran the "flash-all" batch file. But now my device is stuck at the google screen with the unlcoked lock image, before this screen it says that my device is corrupt. How can I solve this issue and go back to oreo?
Thanks
Click to expand...
Click to collapse
Could be your Android PlatformTools are out of date?

abdane said:
Initially, I unlocked my bootloader and data was wiped, then I installed android 8.1 (the recommended version from resuruction remix rom forum) and extracted the files into the directory of adb, then I ran "flash-all" and it was running, then at the end it showed a fail error and now my device is not booting up, I can only access fastboot mode
Click to expand...
Click to collapse
If I am reading your steps right...
My suggestion is flash vanilla Oreo.
I wouldnt be surprised of there is some parition structure change that the Modded ROM is screwing up.
get back to vanilla
Mod after being stabel

parakleet said:
If I am reading your steps right...
My suggestion is flash vanilla Oreo.
I wouldnt be surprised of there is some parition structure change that the Modded ROM is screwing up.
get back to vanilla
Mod after being stabel
Click to expand...
Click to collapse
Im sorry, what do you mean by vanilla oreo? You mean the very first oreo ROM?

parakleet said:
If I am reading your steps right...
My suggestion is flash vanilla Oreo.
I wouldnt be surprised of there is some parition structure change that the Modded ROM is screwing up.
get back to vanilla
Mod after being stabel
Click to expand...
Click to collapse
abdane said:
Im sorry, what do you mean by vanilla oreo? You mean the very first oreo ROM?
Click to expand...
Click to collapse
I think the suggestion is that you flash the stock factory 8.1 image found on the Google site (the link to it is in my 9x and 8x links in my sig).
I agree with this.
Fastboot the factory 8.1 image using the flash-all, leave the -w in so you wipe any fragments, and you should have a brand new, fresh start.

Az Biker said:
I think the suggestion is that you flash the stock factory 8.1 image found on the Google site (the link to it is in my 9x and 8x links in my sig).
I agree with this.
Fastboot the factory 8.1 image using the flash-all, leave the -w in so you wipe any fragments, and you should have a brand new, fresh start.
Click to expand...
Click to collapse
I think I confused you guys, sorry, what i did is that I flashed the STOCK version of 8.1 Oreo, I wanted to downgrade from pie. I installed the official one from google and ran the "flash-all" command and failed at vendor_b

michaelbsheldon said:
Could be your Android PlatformTools are out of date?
Click to expand...
Click to collapse
I just uninstalled it, installed the latest version and still not working :/

I am trying to fastboot the files separately: bootloader, boot, radio, system and vendor images. They all pass except for the vendor image, it always fails there (Data write failure unknown error). Any help?

abdane said:
I just uninstalled it, installed the latest version and still not working :/
Click to expand...
Click to collapse
If you are for sure unlocked and critical unlocked, next step is to unzip everything in the Google factory image (about 25 files), then
use this with instructions listed: https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
It's fixed things for me several times when I just could not get results with flash-all.bat.

Alright, wow finally I got it to work. THe issue was either the cable or the port, I was using the originisl type-c to type c cable, tried my old LG G5 typeA to type c and worked fine, wow. Thanks for the help everyone!!! Phone is back and alive

abdane said:
Alright, wow finally I got it to work. THe issue was either the cable or the port, I was using the originisl type-c to type c cable, tried my old LG G5 typeA to type c and worked fine, wow. Thanks for the help everyone!!! Phone is back and alive
Click to expand...
Click to collapse
I thought you already read over my 8x or 9x guides, or I would've mentioned that in the first place
8x Guide:
-have a 2.0 USB in case your 3.0 USB doesn't work properly
-Reboot PC, change between 2.0 and 3.0 cables, and change USB ports if having trouble using fastboot
9x Guide:
*Unlocked bootloader and Critical_unlock completed.
*Latest SDK Tools found here
*USB 2.0 & 3.0 cables available (trust me)

hi dude, I have the same problem with you , have you solved yet?
after flash the factory image android o , it shows device corrupt..

Az Biker said:
I thought you already read over my 8x or 9x guides, or I would've mentioned that in the first place
8x Guide:
-have a 2.0 USB in case your 3.0 USB doesn't work properly
-Reboot PC, change between 2.0 and 3.0 cables, and change USB ports if having trouble using fastboot
9x Guide:
*Unlocked bootloader and Critical_unlock completed.
*Latest SDK Tools found here
*USB 2.0 & 3.0 cables available (trust me)
Click to expand...
Click to collapse
This exact info should be a sticky on every single thread!!

CyberpodS2 said:
This exact info should be a sticky on every single thread!!
Click to expand...
Click to collapse
I just created a "troubleshooting thread" for this situation in the 2 XL guides section
Link in my sig.
Should be much easier to point people to these steps before we spend two pages trying to help out just to find out it was a USB cable, or old SDK tools

Ble_Ale said:
hi dude, I have the same problem with you , have you solved yet?
after flash the factory image android o , it shows device corrupt..
Click to expand...
Click to collapse
I've had this happened a couple of times no Rhyme or Reason the only way out of it is to flash The Flash all with the -w. I believe it has something to do with Googles security.
Edit. I take that back I've switched to the other slot before and restored a backup and gotten out of it if that other slot isn't corrupt

I thought Android Pie has a mandatory "Anti Roll back" feature that prevents going back to Android Oreo?
That is not true then?!

samteeee said:
I thought Android Pie has a mandatory "Anti Roll back" feature that prevents going back to Android Oreo?
That is not true then?!
Click to expand...
Click to collapse
unless you do fastboot flashing unlock and fastboot flashing unlock_critical it is not possible to roll back.
if you do both above you can over-write the critical partitions allowing the roll-back.
the general population would not be doing these, so in essence they do block rolling back to earlier versions, but in a disaster situation it can be done.

uicnren said:
unless you do fastboot flashing unlock and fastboot flashing unlock_critical it is not possible to roll back.
if you do both above you can over-write the critical partitions allowing the roll-back.
the general population would not be doing these, so in essence they do block rolling back to earlier versions, but in a disaster situation it can be done.
Click to expand...
Click to collapse
Got it. Thanks for the explanation.

Can you root Android 10 v11.0.5.0.? New to Xiaomi phones...

Hello. I bought my Mi A2 Lite today off ebay and it came with Android (One) 10, version 11.0.5.0. I need help rooting it.
I've used Samsung phones all my life, So I'm very used to Odin and all Samsung procedures. This is my first Xiaomi phone, and I can't find a real basic guide for rooting it. I don't really understand the ones I've seen, especially this fastboot thing.
I'd appreciate if I could have some step-by-step help on how to root this phone on the latest v11.0.5.0.
Many thanks!

Use this thread
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952

thamidu said:
Use this thread
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
Click to expand...
Click to collapse
Thanks, but I'm confused by two things.
The first one is step number 4:
4. Now connect the phone with your PC via USB cable, open an administrative command prompt, move to the directory where the Android platform tools are placed and unlock the bootloader with the following command:
Code:
fastboot oem unlock
The phone will reboot, erasing all the data.
Now you unlocked your phone's bootloader and can continue to the next section.
I already flicked the "OEM" unlock in Developer Options. What Android platform tools is he talking about? and where do I get them? This is exactly the help I need with. The guide is for someone who knows about fastboot, I have zero experience with it. I'd appreciate help?
Second thing that confuses me:
The patched boot images available for download are for older builds (the newest one for download is for 10.0.3.0 and I'm on the latest 11.0.5.0). Does that matter?
Thanks again.

93starletgt said:
What Android platform tools is he talking about? and where do I get them?
The patched boot images available for download are for older builds (the newest one for download is for 10.0.3.0 and I'm on the latest 11.0.5.0). Does that matter?
Click to expand...
Click to collapse
These android platform tools: https://developer.android.com/studio/releases/platform-tools
You must use matching versions for the boot image or your system won't boot. Newer patched boot images are generally posted to the guides section of the forum. Here's the one for 11.0.5.0.
https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-patched-boot-img-v11-0-5-0-t4105497
Since you're coming from a different phone, please be careful and read all the instructions. Double-check with people if you're not sure. This phone is different to other phones and people have been caught out by those differences.

Sony Xperia XA1 - Bootloop after twrp misuse

Hello, i'm writing this post because i'm a noob on mobiles and i need some assistence in this scenario.
I have a xa1 that was stopped at home because it had terrible calibration problems. This year i remembered to root and flash this mobile, maybe it was the build that was having some compatibility issues.
For now i have successfully unlocked the bootloader but when doing an instructon installing the twrp program on the device, i may have done something wrong.
From what i understand, twrp is a backup/recovery user gui to make some actions easier.
i think i ****ed up and now the phone is on bootloop and i cant even go into recovery mode.
i did not move the twrp.img to the folder i was working on and still pressed enter on the "fastboot boot twrp.img" step.
I understand that i may have told the phone "hey use this img that doesnt exist" and now its standarized to launch from that img i told him? is that it?
I have adb and fastboot installed. I had them both recognizing the device, no problem until i did that step earlier, and now adb doesnt recognize the device anymore. I thought i could maybe get the standart boot.img(if that even exists) from some forum but this is getting waaay hairier that i thought.

Don't worry, it normal that the phone has bootloop after unlocked. You should flash stock rom again via Flashtool, for the firmware you could still download it from xperiafirm I guess, after reflash the stock rom your device will work just fine and you could download my twrp here which I build for XA1 Plus but a friend of mine have it working on XA1 Ultra just fine, if you need any more help on TWRP just DM me or ask in my thread

Hari Nguyen said:
Don't worry, it normal that the phone has bootloop after unlocked. You should flash stock rom again via Flashtool, for the firmware you could still download it from xperiafirm I guess, after reflash the stock rom your device will work just fine and you could download my twrp here which I build for XA1 Plus but a friend of mine have it working on XA1 Ultra just fine, if you need any more help on TWRP just DM me or ask in my thread
Click to expand...
Click to collapse
which firmware do i select and download? i bought the phone via amazon, from the uk, should i use the firmware of the language i want or the original from the fabric? does that even make a difference? im sorry, im a noob at android systems xD

Learn it at Xperia Firm thread, my country might vary from your (like network operator or what not) for that you need to do your own research to know which one to download, in my country all I need it go and download firmware that made for vietnam and done, it already come with multiple languages