Related
I flashed the wrong bootloader so fastboot does not work. I still have TWRP Working but anything I flash does not boot. I am looking for a full factory OTA that I can flash via TWRP so it will re-flash the proper bootloader and all the other factory images so I can un-brick it through fastboot. I have tried to flash many different update files but it gives an error 7 and says to be on 6.0.1 or 7.0 before installing it. Can someone please help me un-brick this or link a full OTA that I can flash via TWRP. I attached the bootloader.img so if anyone could make a flashable zip to flash the stock bootloader that would probably work.
vibraniumdroid said:
I flashed the wrong bootloader so fastboot does not work. I still have TWRP Working but anything I flash does not boot. I am looking for a full factory OTA that I can flash via TWRP so it will re-flash the proper bootloader and all the other factory images so I can un-brick it through fastboot. I have tried to flash many different update files but it gives an error 7 and says to be on 6.0.1 or 7.0 before installing it. Can someone please help me un-brick this or link a full OTA that I can flash via TWRP. I attached the bootloader.img so if anyone could make a flashable zip to flash the stock bootloader that would probably work.
Click to expand...
Click to collapse
Follow this discussion.
"https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492"
ROM_HUNTER said:
Follow this discussion.
"https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492"
Click to expand...
Click to collapse
does not work
vibraniumdroid said:
does not work
Click to expand...
Click to collapse
If fastboot works then you're not hard bricked, most likes soft brick. I would suggest flashing magisks 14 after you flash the rom as dm-verity will check if your system is modified , dm-verity needs to be disabled
flashallthetime said:
If fastboot works then you're not hard bricked, most likes soft brick. I would suggest flashing magisks 14 after you flash the rom as dm-verity will check if your system is modified , dm-verity needs to be disabled
Click to expand...
Click to collapse
I already tried flashing magisk. Also I can boot into the bootloader but the computer does not see it in fastboot anymore (probably because I flashed the bootloader.img for the moto z play droid accidentally)
vibraniumdroid said:
I already tried flashing magisk. Also I can boot into the bootloader but the computer does not see it in fastboot anymore (probably because I flashed the bootloader.img for the moto z play droid accidentally)
Click to expand...
Click to collapse
Hard bricked for sure
flashallthetime said:
Hard bricked for sure
Click to expand...
Click to collapse
not exactly because twrp works. If I could flash fastboot images through TWRP I could un-brick it. If somebody could modify the stock rom's updater-script and remove the requirement to be running a stock rom then I could flash that and I would probably be unbricked.
vibraniumdroid said:
not exactly because twrp works. If I could flash fastboot images through TWRP I could un-brick it. If somebody could modify the stock rom's updater-script and remove the requirement to be running a stock rom then I could flash that and I would probably be unbricked.
Click to expand...
Click to collapse
Bootloader can not be flashed through twrp so you'll need to flash the bootloader through fastboot. If your device is not recognized when you plug it in your computer then you're hard bricked, if fastboot is not accessable then you're hard bricked
flashallthetime said:
Bootloader can not be flashed through twrp so you'll need to flash the bootloader through fastboot. If your device is not recognized when you plug it in your computer then you're hard bricked, if fastboot is not accessable then you're hard bricked
Click to expand...
Click to collapse
so you are sure that it is impossible to make a flashable zip of bootloader. Maybe it is just my computer I'll try booting of linux on usb and then see if fastboot can see it.
flashallthetime said:
Bootloader can not be flashed through twrp so you'll need to flash the bootloader through fastboot. If your device is not recognized when you plug it in your computer then you're hard bricked, if fastboot is not accessable then you're hard bricked
Click to expand...
Click to collapse
how do you fix a hardbrick?
vibraniumdroid said:
how do you fix a hardbrick?
Click to expand...
Click to collapse
Here https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492
flashallthetime said:
Here https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492
Click to expand...
Click to collapse
I tried that does not work:crying: also I got windows to see the phone as addison fastboot s but when i do fastboot devices it does not show up
vibraniumdroid said:
I tried that does not work:crying: also I got windows to see the phone as addison fastboot s but when i do fastboot devices it does not show up
Click to expand...
Click to collapse
Do you have the correct driver,, if you use Linux there is no need for the driver just install minimal ADB and fastboot
vibraniumdroid said:
I tried that does not work:crying: also I got windows to see the phone as addison fastboot s but when i do fastboot devices it does not show up
Click to expand...
Click to collapse
Have you tried using these albus (Z2 Play) blank flashes as mentioned here to repair your bootloader? https://forum.xda-developers.com/showpost.php?p=73402033&postcount=181
https://forum.xda-developers.com/showpost.php?p=73411048&postcount=206
These may hopefully get your device to the point where it's recognised in fastboot and you can then flash the stock ROM via fastboot.
vibraniumdroid said:
how do you fix a hardbrick?
Click to expand...
Click to collapse
You don't. That's why it's called a hard brick.
flashallthetime said:
Do you have the correct driver,, if you use Linux there is no need for the driver just install minimal ADB and fastboot
Click to expand...
Click to collapse
booted of linux from a usb and that worked thanks
I am currently running stock 7.1.1 with august updates NPNS26.118-22-1
I am facing some serious issues with it and thinking about downgrading to NPNS25.137-24-1-9 ( nougat 7.0) via fastboot.
I have heard that downgrading can result in a bricked phone. Is it so?
kkube said:
I am currently running stock 7.1.1 with august updates NPNS26.118-22-1
I am facing some serious issues with it and thinking about downgrading to NPNS25.137-24-1-9 ( nougat 7.0) via fastboot.
I have heard that downgrading can result in a bricked phone. Is it so?
Click to expand...
Click to collapse
Yes you'll end up bricking your phone, the best thing you can do is reflashing stock 7.1.1 either by adb or a zip or try a custom ROM but don't downgrade for your phone's sake.
nosiobadx said:
Yes you'll end up bricking your phone, the best thing you can do is reflashing stock 7.1.1 either by adb or a zip or try a custom ROM but don't downgrade for your phone's sake.
Click to expand...
Click to collapse
I have doubt, when I had the original Moto G 2013 it was possible to downgrade via fastboot flashing boot, recovery and system, avoiding gpt and bootloader (it was even possible to flash the modem without ending with a brick) do you know if it's possible to do the same kind of downgrade with this phone?
ddiuit said:
I have doubt, when I had the original Moto G 2013 it was possible to downgrade via fastboot flashing boot, recovery and system, avoiding gpt and bootloader (it was even possible to flash the modem without ending with a brick) do you know if it's possible to do the same kind of downgrade with this phone?
Click to expand...
Click to collapse
What are the issues you're facing??
It can be done, but to be sure you can reflash 7.1.1 and if the issues persists then yes you can try the steps you wrote above.
so i tried flashing many oreo custom roms, and the fingerprint sensor just didn't work anymore, and i know is a common issue, is there any fix to this?
Frarione said:
so i tried flashing many oreo custom roms, and the fingerprint sensor just didn't work anymore, and i know is a common issue, is there any fix to this?
Click to expand...
Click to collapse
If you're still on the nougat bootloader it won't work
Flash the entire oero firmware via fastboot
TheFixItMan said:
If you're still on the nougat bootloader it won't work
Flash the entire oero firmware via fastboot
Click to expand...
Click to collapse
my bootloader is in the B8.31 version, isn't that the oreo bootloader?
Frarione said:
my bootloader is in the B8.31 version, isn't that the oreo bootloader?
Click to expand...
Click to collapse
I don't own this device
My advice would be to flash the entire oero firmware
TheFixItMan said:
If you're still on the nougat bootloader it won't work
Click to expand...
Click to collapse
I believe it doesn't matter in case he is running Oreo CustomROM.
my bootloader is in the B8.31 version, isn't that the oreo bootloader?
Click to expand...
Click to collapse
I would recommend you to downgrade to Nougat first - flash everything except gpt and bootloader to avoid hardbrick. Also don't run erase modem commands, they will erase your IMEI in this case. Then, make sure that fingerprint is working with Nougat StockROM. If it does, try to install CustomROM.
Andrej_SK said:
I believe it doesn't matter in case he is running Oreo CustomROM.
I would recommend you to downgrade to Nougat first - flash everything except gpt and bootloader to avoid hardbrick. Also don't run erase modem commands, they will erase your IMEI in this case. Then, make sure that fingerprint is working with Nougat StockROM. If it does, try to install CustomROM.
Click to expand...
Click to collapse
ok i will try this, wish me luck
Andrej_SK said:
I would recommend you to downgrade to Nougat first - flash everything except gpt and bootloader to avoid hardbrick. Also don't run erase modem commands, they will erase your IMEI in this case. Then, make sure that fingerprint is working with Nougat StockROM. If it does, try to install CustomROM.
Click to expand...
Click to collapse
Dude ily, all this time with that problem, and this was the simple solution, thx :good:
Frarione said:
Dude ily, all this time with that problem, and this was the simple solution, thx :good:
Click to expand...
Click to collapse
Glad to help you.
Just one more thing to mention: don't even try to install OTA updates (in case you stay on StockROM). Here's why. Your bootloader's version is B8.31 now, but phone is "still" running Android Nougat (I guess). Oreo OTA updates the bootloader from B8.25 to B8.31, but since yours bootloader is already updated to B8.31, OTA would try to make a changes, which were already made and break the whole "structure" of bootloader. This would end up most probably in hard brick.
If you'd like to revert back to official Oreo someday, install it using fastboot method. (https://forum.xda-developers.com/g5/how-to/official-oreo-8-1-0-opp28-85-16-t3849244). Even you will most probably loose all of the data, it seems to be the only one safe way to update back to Oreo after downgrading to Nougat.
Andrej_SK said:
Glad to help you.
Just one more thing to mention: don't even try to install OTA updates (in case you stay on StockROM). Here's why. Your bootloader's version is B8.31 now, but phone is "still" running Android Nougat (I guess). Oreo OTA updates the bootloader from B8.25 to B8.31, but since yours bootloader is already updated to B8.31, OTA would try to make a changes, which were already made and break the whole "structure" of bootloader. This would end up most probably in hard brick.
If you'd like to revert back to official Oreo someday, install it using fastboot method. (https://forum.xda-developers.com/g5/how-to/official-oreo-8-1-0-opp28-85-16-t3849244). Even you will most probably loose all of the data, it seems to be the only one safe way to update back to Oreo after downgrading to Nougat.
Click to expand...
Click to collapse
Roger that, thanks again
my build number is NPPS25.137-93-14
I want to update to oreo but read some posts says that i can not because of build number
HELP
ahmedAZ said:
my build number is NPPS25.137-93-14
I want to update to oreo but read some posts says that i can not because of build number
HELP
Click to expand...
Click to collapse
You must be running NPPS25.137-93-2-5 to be able to update through OTA. However, you can still update to Oreo using fastboot method (link here: https://forum.xda-developers.com/g5/how-to/official-oreo-8-1-0-opp28-85-16-t3849244), but most probably, you will loose all of the data stored in the phone.
Andrej_SK said:
You must be running NPPS25.137-93-2-5 to be able to update through OTA. However, you can still update to Oreo using fastboot method (link here: https://forum.xda-developers.com/g5/how-to/official-oreo-8-1-0-opp28-85-16-t3849244), but most probably, you will loose all of the data stored in the phone.
Click to expand...
Click to collapse
Is it safe to downgrade?
Some people say you may hard brick
Using adb don't need to downgrade?
ahmedAZ said:
Is it safe to downgrade?
Some people say you may hard brick
Click to expand...
Click to collapse
It's safe as long as you don't try to flash gpt and bootloader. Downgrading one (or both) of these partition results in hardbrick.
Andrej_SK said:
It's safe as long as you don't try to flash gpt and bootloader. Downgrading one (or both) of these partition results in hardbrick.
Click to expand...
Click to collapse
But if i install oreo custom rom fingerprint may not work because it needs updated bootloader
I have read something like that on forum
ahmedAZ said:
But if i install oreo custom rom fingerprint may not work because it needs updated bootloader
I have read something like that on forum
Click to expand...
Click to collapse
If you update to official Oreo but then decide, you want to install CustomROM, you have to downgrade to Nougat first. Otherwise, your fingerprint won't simply work with any CustomROM. I have already mentioned it in this thread https://forum.xda-developers.com/g5/help/finger-print-sensor-issue-oreo-roms-t3853491.
Btw, bootloader version is not related to fingerprint working or not with CustomROM. There's another partition that makes difference in it.
Andrej_SK said:
If you update to official Oreo and decide later, you want to install CustomROM, you have to downgrade to Nougat first. Otherwise, fingerprint won't work with any CustomROM. I have already mentioned it in this thread https://forum.xda-developers.com/g5/help/finger-print-sensor-issue-oreo-roms-t3853491.
Click to expand...
Click to collapse
So it is better to be on nougat if i want custom roms in future?
Treble project needs stock nougat or oreo?
ahmedAZ said:
So it is better to be on nougat if i want custom roms in future?
Click to expand...
Click to collapse
In my opininon yes, but your opininon might be different. Downgrading from official Oreo to official Nougat isn't difficult at all. You just have to remember, you can't flash gpt and bootloader. It's also recommended to avoid erase modem commands to prevent loss of IMEI.
ahmedAZ said:
Treble project needs stock nougat or oreo?
Click to expand...
Click to collapse
None of them. Treble project needs Treble TWRP and Treble LineageOS installed firstly for correct functionality of other Treble CustomROMs. More info in this thread https://forum.xda-developers.com/g5/development/treble-project-treble-cedric-t3820451.
ahmedAZ said:
my build number is NPPS25.137-93-14
I want to update to oreo but read some posts says that i can not because of build number
HELP
Click to expand...
Click to collapse
Hi everyone , I have not yet received update for Oreo ? Indian region, having same build no , my bootloader is unlocked as well
Same problem here. I have also the same build number on amzin software channel. Didn't receive the update till now. It says there is no update available.
akshayshirkar10 said:
Hi everyone , I have not yet received update for Oreo ? Indian region, having same build no , my bootloader is unlocked as well
Click to expand...
Click to collapse
achintyakv said:
Same problem here. I have also the same build number on amzin software channel. Didn't receive the update till now. It says there is no update available.
Click to expand...
Click to collapse
I was on 137-93-14 too. I flashed the fastboot firmware 137-93-2-5 to go back full stock and official. No need to re lock bootloader..then I downloaded the latest OTA update 28.85-16 and installed it via ADB sideload.
My phone is xt1670 on channel retca..though I can't say for sure what difference it makes if your on amzin. Wish I could help more.
No problem bro Yesterday I flashed the fastboot files and successfully updated to oreo which I found on this thread.
https://forum.xda-developers.com/g5/how-to/official-oreo-8-1-0-opp28-85-16-t3849244
Btw you have taken the long step bro. No need to get back to 137-93-2-5.
Cheers!
Chekm8Qc said:
I was on 137-93-14 too. I flashed the fastboot firmware 137-93-2-5 to go back full stock and official. No need to re lock bootloader..then I downloaded the latest OTA update 28.85-16 and installed it via ADB sideload.
My phone is xt1670 on channel retca..though I can't say for sure what difference it makes if your on amzin. Wish I could help more.
Click to expand...
Click to collapse
achintyakv said:
No problem bro Yesterday I flashed the fastboot files and successfully updated to oreo which I found on this thread.
https://forum.xda-developers.com/g5/how-to/official-oreo-8-1-0-opp28-85-16-t3849244
Btw you have taken the long step bro. No need to get back to 137-93-2-5.
Cheers!
Click to expand...
Click to collapse
i updated through twrp
@achintyakv
Yeah your right that was definitely the long way hehe. It's cause I wasn't sure that th oreo fastboot method would have worked for me. I had tried the TWRP version and it kept boot looping so I thought the other way would be safer
Premise: I have a xiaomi Mi 10T Pro model "M2007J3SG", never flashed firmware, never rooted and only updated from phone settings.
Wanting to revert to a firmware with android 10, original do I need to unlock the bootloader?
If I have to unlock it how should I do it, assuming I don't have to put any custom rom or run root.
ricru90 said:
Premise: I have a xiaomi Mi 10T Pro model "M2007J3SG", never flashed firmware, never rooted and only updated from phone settings.
Wanting to revert to a firmware with android 10, original do I need to unlock the bootloader?
If I have to unlock it how should I do it, assuming I don't have to put any custom rom or run root.
Click to expand...
Click to collapse
Wanting to revert to a firmware with android 10, original do I need to unlock the bootloader? Yes
https://c.mi.com/thread-1857937-1-1.html
https://en.miui.com/unlock/index.html
Downgrade:
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
Fastboot rom:
https://xiaomirom.com/en/rom/mi-10t-10t-pro-apollo-china-fastboot-recovery-rom/
NOSS8 said:
Wanting to revert to a firmware with android 10, original do I need to unlock the bootloader? Yes
https://c.mi.com/thread-1857937-1-1.html
https://en.miui.com/unlock/index.html
Downgrade:
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
Fastboot rom:
https://xiaomirom.com/en/rom/mi-10t-10t-pro-apollo-china-fastboot-recovery-rom/
Click to expand...
Click to collapse
my concern is roll back protection, because from what I have read since I want to downgrade two versions of android i.e. from 12 to 10, the roll back index is discordant between the two firmwares
ricru90 said:
my concern is roll back protection, because from what I have read since I want to downgrade two versions of android i.e. from 12 to 10, the roll back index is discordant between the two firmwares
Click to expand...
Click to collapse
Not important, use the script directly included in the fastboot rom.
NOSS8 said:
Not important, use the script directly included in the fastboot rom.
Click to expand...
Click to collapse
in the unfortunate event that something should happen and the procedure fails, is there any precaution to be taken before doing so, like a backup not of the files, but a backup of the firmware or something similar?
ricru90 said:
in the unfortunate event that something should happen and the procedure fails, is there any precaution to be taken before doing so, like a backup not of the files, but a backup of the firmware or something similar?
Click to expand...
Click to collapse
If the phone is a Chinese version does not lock the bootloader.
Miflash is used to flash firmware.
unlock bootloader erases your data, Miflash too.
If there is an error during the flash, the flash does not occur.
NOSS8 said:
If the phone is a Chinese version does not lock the bootloader.
Miflash is used to flash firmware.
unlock bootloader erases your data, Miflash too.
If there is an error during the flash, the flash does not occur.
Click to expand...
Click to collapse
so what I have to do is unlock the bootloader as stated in the first guide and then run your guide to downgrade to the correct firmware?
ricru90 said:
so what I have to do is unlock the bootloader as stated in the first guide and then run your guide to downgrade to the correct firmware?
Click to expand...
Click to collapse
yep,any firmware version matching your phone's codename.
NOSS8 said:
yep,any firmware version matching your phone's codename.
Click to expand...
Click to collapse
just for information, searching on the internet I saw that there are or are created cables, called “Deep Flash Cables”, do you happen to know what they are for?
ricru90 said:
just for information, searching on the internet I saw that there are or are created cables, called “Deep Flash Cables”, do you happen to know what they are for?
Click to expand...
Click to collapse
To flash in EDL mode in the event of a total brick. (no more fastboot, no recovery) phone must be open.
NOSS8 said:
To flash in EDL mode in the event of a total brick. (no more fastboot, no recovery) phone must be open.
Click to expand...
Click to collapse
Is EDL mode only for xiaomi or for any Android phone?
ricru90 said:
Is EDL mode only for xiaomi or for any Android phone?
Click to expand...
Click to collapse
Qualcomm device.
bro twrp recovery file available for "mi 10t 5g" android 12 miui 13.
is it available?