Related
I have unlocked bootloader. And flash the official recovery to get Naugat OTA but after updating. I am seeing "ID : bad key " instead of "ID : N/A" which is written in previous version of OS.
Any one know what it really meant.?
Try to boot in qcom or bp tools mode via menu fastboot, then restart the device. In my case, at the restart it shows "ID: N/A" Again. Another Theory is that you can get the "N/A" message after a hard reset o format data vía TWRP. I do both with the same results. Maybe a encryption mismatch.
GuzXT said:
Try to boot in qcom or bp tools mode via menu fastboot, then restart the device. In my case, at the restart it shows "ID: N/A" Again. Another Theory is that you can get the "N/A" message after a hard reset o format data vía TWRP. I do both with the same results. Maybe a encryption mismatch.
Click to expand...
Click to collapse
I tried but still it shows bad key.. but it's ok until my device boots in system succesfully
.
GuzXT said:
Try to boot in qcom or bp tools mode via menu fastboot, then restart the device. In my case, at the restart it shows "ID: N/A" Again. Another Theory is that you can get the "N/A" message after a hard reset o format data vía TWRP. I do both with the same results. Maybe a encryption mismatch.
Click to expand...
Click to collapse
Has the same ID: N / A
unlocked bootloader on Android 7
Any ideas ?
S3V3N said:
Has the same ID: N / A
unlocked bootloader on Android 7
Any ideas ?
Click to expand...
Click to collapse
Pretty sure everyone has this with an unlocked bootloader.
ok thx
xxBrun0xx said:
Pretty sure everyone has this with an unlocked bootloader.
Click to expand...
Click to collapse
definitely not.
Am facing same problem. Bad boot image.. Looking for stock boot image
kdagia said:
Am facing same problem. Bad boot image.. Looking for stock boot image
Click to expand...
Click to collapse
did you find the solution iused twrp and i had no problem after installing the Russian ROM im getting this message
kdagia said:
Am facing same problem. Bad boot image.. Looking for stock boot image
Click to expand...
Click to collapse
Do you mean bad boot image in the sense of it won't boot or just the warning screen every time you boot. If its the second one you can fix it (almost) completely by flashing a modified logo.bin. I got those in my signature second thread if you are searching for that. Would be strange if your boot image couldn't boot up.
G4liant said:
Do you mean bad boot image in the sense of it won't boot or just the warning screen every time you boot. If its the second one you can fix it (almost) completely by flashing a modified logo.bin. I got those in my signature second thread if you are searching for that. Would be strange if your boot image couldn't boot up.
Click to expand...
Click to collapse
I mean 'bad key' instead of showing "N/A"
kdagia said:
I mean 'bad key' instead of showing "N/A"
Click to expand...
Click to collapse
You need to flash modified logo.bin ...That's it
Same, and cant seem to flash at all
I'm having the same trouble here.
The main problem is that it seems to be related to the impossibility to flash again or install new rom on the device.
When i try to follow the typical procedures on cmd, i get messages like:
>> writing 'partition'...
>> (bootloader) Security version downgrade
>> (bootloader) Image primary_gpt failed validation
>> (bootloader) Preflash validation failed
>> FAILED (remote failure)
And then I can't seem to move on to another rom (and relocking the device, as I wish to do after all this).
(when i said typical procedures is that i found on many places, such as the motorola official website, https :// motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images#)
FLASH AND RELOCK YOUR DEVICE
After downloading the image for your device:
Make sure you have a Moto Pure Edition or a Developer Edition device.
Make sure you download the corresponding recovery image from the above portal.
To flash, put the phone in fastboot mode:
1. Power OFF your device
2. Then Power ON + Volume Down
Alternatively, you can reboot into fastboot mode if you have adb...adb reboot bootloader.
Next flash the images using fastboot:
$ fastboot flash partition gpt.bin
$ fastboot flash motoboot motoboot.img
$ fastboot reboot-bootloader
$ fastboot flash logo logo.bin
$ fastboot flash boot boot.img
$ fastboot flash recovery recovery.img
$ fastboot flash system system.img
$ fastboot flash modem NON-HLOS.bin
$ fastboot erase modemst1
$ fastboot erase modemst2
$ fastboot flash fsg fsg.mbn
$ fastboot reboot
You also have the option to erase all the data on your device with
$ fastboot erase userdata
$ fastboot erase cache
After performing this sequence, you can relock your device with
$ fastboot oem lock
[email protected] said:
I'm having the same trouble here.
The main problem is that it seems to be related to the impossibility to flash again or install new rom on the device.
When i try to follow the typical procedures on cmd, i get messages like:
>> writing 'partition'...
>> (bootloader) Security version downgrade
>> (bootloader) Image primary_gpt failed validation
>> (bootloader) Preflash validation failed
>> FAILED (remote failure)
And then I can't seem to move on to another rom (and relocking the device, as I wish to do after all this).
(when i said typical procedures is that i found on many places, such as the motorola official website, https :// motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images#)
FLASH AND RELOCK YOUR DEVICE
After downloading the image for your device:
Make sure you have a Moto Pure Edition or a Developer Edition device.
Make sure you download the corresponding recovery image from the above portal.
To flash, put the phone in fastboot mode:
1. Power OFF your device
2. Then Power ON + Volume Down
Alternatively, you can reboot into fastboot mode if you have adb...adb reboot bootloader.
Next flash the images using fastboot:
$ fastboot flash partition gpt.bin
$ fastboot flash motoboot motoboot.img
$ fastboot reboot-bootloader
$ fastboot flash logo logo.bin
$ fastboot flash boot boot.img
$ fastboot flash recovery recovery.img
$ fastboot flash system system.img
$ fastboot flash modem NON-HLOS.bin
$ fastboot erase modemst1
$ fastboot erase modemst2
$ fastboot flash fsg fsg.mbn
$ fastboot reboot
You also have the option to erase all the data on your device with
$ fastboot erase userdata
$ fastboot erase cache
After performing this sequence, you can relock your device with
$ fastboot oem lock
Click to expand...
Click to collapse
I have exactly the same problem, has it been able to solve it?
How to solve it?
Same problem here
Can do nothing, phone always boots to fastboot no matter what I do/flash. It also states ID: bad key.
thoros1179 said:
Same problem here
Can do nothing, phone always boots to fastboot no matter what I do/flash. It also states ID: bad key.
Click to expand...
Click to collapse
Try typing "fastboot oem fb_mode_clear" inside the bootloader.
Hi there,
I have a problem i was try to root my phone.
Now i dont have access to ADB but only fastboot works.
If i start my phone it goes on fastboot mode, and if i try "fast boot twrp-3.3.0-0-daisy.img" i get the error "device unable to boot Error - mdtp image is corrupted"
Can some one help me out, if tried to download the image again but without success..
You don't need twrp for root?!
I guess you need to get a fast boot ROM and flash it. Don't relock the bootloader. Don't flash data. Just all the other partitions.
Maybe even just flash that partition. My phone has a and b. Should just need to flash the current one.
a1291762 said:
You don't need twrp for root?!
I guess you need to get a fast boot ROM and flash it. Don't relock the bootloader. Don't flash data. Just all the other partitions.
Maybe even just flash that partition. My phone has a and b. Should just need to flash the current one.
Click to expand...
Click to collapse
Sorry im a little bit noob, but how it works:
flastboot flash a?
fastboot flash mdtp_a mdtp.img
That file is in the images folder after you extract the fastboot ROM.
Hi,
while having 15 years of Linux experience, I've just dropped into the same issue on my first hour of Android exploration. Currently no OS is installed and the phone boots into fastboot. Booting into twrp-3.3.1-dees_troy-daisy.img failes also with "Error - mdtp image is corrupted".
I've flashed mdtp.img from V10.0.12.0.PDLMIXM as described, but still I get the same error when booting into twrp-3.3.1-dees_troy-daisy.img . Is there somewere a documentation, how to proceed in such a case?
a1291762 said:
fastboot flash mdtp_a mdtp.img
That file is in the images folder after you extract the fastboot ROM.
Click to expand...
Click to collapse
mj2o said:
Hi,
while having 15 years of Linux experience, I've just dropped into the same issue on my first hour of Android exploration. Currently no OS is installed and the phone boots into fastboot. Booting into twrp-3.3.1-dees_troy-daisy.img failes also with "Error - mdtp image is corrupted".
I've flashed mdtp.img from V10.0.12.0.PDLMIXM as described, but still I get the same error when booting into twrp-3.3.1-dees_troy-daisy.img . Is there somewere a documentation, how to proceed in such a case?
Click to expand...
Click to collapse
No OS installed is maybe cause the last rom that you flashed was not flashed in the right slot or correctly flashed.
Also the fastboot command mentioned here is to flash mdtp in "a" slot but you have to see first which is your active slot and then install it on it.
SubwayChamp said:
Also the fastboot command mentioned here is to flash mdtp in "a" slot but you have to see first which is your active slot and then install it on it.
Click to expand...
Click to collapse
I've searched more for the reason and once got the response: FAILED (remote: partition table doesn't exist)
So it sounds I have to recreate the partition table. I haven't found any fastboot command to request the current partition status.
mj2o said:
I've searched more for the reason and once got the response: FAILED (remote: partition table doesn't exist)
So it sounds I have to recreate the partition table. I haven't found any fastboot command to request the current partition status.
Click to expand...
Click to collapse
I don´t think that exist a command to diagnose status of partitions but I´m sure that if you try to flash on an inactive slot then won´t work, ever an inactive slot will give you a fail.
Check your active slot by typing
Code:
fastboot getvar current-slot
and then flash it on the active slot using "mdtp_a" or "mdtp_b" but ONLY if the active slot is actually with all the system on it it´s mean that if you deleted all your system and any of both are actually with partitions running (no matter that with errors) then won´t work this way as you expect.
I have the same problem, what you have did to fix? please
Hi,
I've downloaded and flashed the factory image from miui.com. This way I have reset all my efforts and started all over. You find there the full rom and a flashing guide for the Xiaomi Mi A2 Lite.
mj2o said:
Hi,
I've downloaded and flashed the factory image from miui.com. This way I have reset all my efforts and started all over. You find there the full rom and a flashing guide for the Xiaomi Mi A2 Lite.
Click to expand...
Click to collapse
hi
same issue here @mj2o: Can you please provide a link to the site in English; it all in Chinese and I cannot read it
Thanks
mj2o said:
Hi,
I've downloaded and flashed the factory image from miui.com. This way I have reset all my efforts and started all over. You find there the full rom and a flashing guide for the Xiaomi Mi A2 Lite.
Click to expand...
Click to collapse
SubwayChamp said:
I don´t think that exist a command to diagnose status of partitions but I´m sure that if you try to flash on an inactive slot then won´t work, ever an inactive slot will give you a fail.
Check your active slot by typing
Code:
fastboot getvar current-slot
and then flash it on the active slot using "mdtp_a" or "mdtp_b" but ONLY if the active slot is actually with all the system on it it´s mean that if you deleted all your system and any of both are actually with partitions running (no matter that with errors) then won´t work this way as you expect.
Click to expand...
Click to collapse
@mj2o;80151263:
Code:
fastboot getvar current-slot
returns -->
Code:
current-slot: INVALID
finished. total time: 0.008s
and
Code:
fastboot flash aboot aboot.img
returns -->
Code:
target reported max download size of 534773760 bytes
sending 'aboot' (1024 KB)...
OKAY [ 0.055s]
writing 'aboot'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.075s
please advise.
BenG7 said:
@mj2o;80151263:
Code:
fastboot getvar current-slot
returns -->
Code:
current-slot: INVALID
finished. total time: 0.008s
and
Code:
fastboot flash aboot aboot.img
returns -->
Code:
target reported max download size of 534773760 bytes
sending 'aboot' (1024 KB)...
OKAY [ 0.055s]
writing 'aboot'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.075s
please advise.
Click to expand...
Click to collapse
Why do you want to flash the bootloader, what is the issue?
Hi @SubwayChamp
I wanted to flash LO16
Did a wpie data -yes format
Then a wipe system as instructed and now im stuck in fast boot.
Device unable to boot. Error - mdtp is corrupted
BenG7 said:
Hi @SubwayChamp
I wanted to flash LO16
Did a wpie data -yes format
Then a wipe system as instructed and now im stuck in fast boot.
Click to expand...
Click to collapse
If your issue is related with mdtp partition then you should to install again this image through fastboot in both slots in order to can boot device again to recovery; use
Code:
fastboot flash mdtp_a mdtp.img
and
Code:
fastboot flash mdtp_b mdtp.img
(you will get the images from any of the full fastboot roms)
From there try again the steps recommended by OP in that thread to get that your device boots on LOS but this is other question concerning only to that thread
Thanks SubwayChamp,
Will try as advised and keep you updated.
I m going to look for the fastboot rom for my daisy.
SubwayChamp said:
If your issue is related with mdtp partition then you should to install again this image through fastboot in both slots in order to can boot device again to recovery; use
Code:
fastboot flash mdtp_a mdtp.img
and
Code:
fastboot flash mdtp_b mdtp.img
(you will get the images from any of the full fastboot roms)
From there try again the steps recommended by OP in that thread to get that your device boots on LOS but this is other question concerning only to that thread
Click to expand...
Click to collapse
@SubwayChamp
dit it and when I
Code:
fastboot reboot
it boots straight back to fastboot.
What next? Mi a2 Lite stuck at Fastboot - No recovery, no nothing! Help ?
Thanks for your help!
[EDIT]
realised I can
Code:
fastboot boot twrp-daisy-3.3.1-0-offain.img
and I can flash the twrp-installer-daisy-3.3.1-0-offain.zip
but if I want to reboot; it says
Code:
No OS installed! Are you sure you wish to reboot?
so I went on with flashing lineageos 16
but at the end of the flash, I get
Code:
Failed to mount '/system' (permission denied)
please advise
BenG7 said:
If your issue is related with mdtp partition then you should to install again this image through fastboot in both slots in order to can boot device again to recovery; use and
@SubwayChamp
dit it and when I
it boots straight back to fastboot.
What next? Mi a2 Lite stuck at Fastboot - No recovery, no nothing! Help ?
Thanks for your help!
Click to expand...
Click to collapse
Your recovery is missed now cause when you flashed LOS was overwritten and device can't boot to system cause some step failed in the process.
If you flashed successfully mdtp images now follow the steps to boot to recovery and then follow those indicated to install LOS.
SubwayChamp said:
Your recovery is missed now cause when you flashed LOS was overwritten and device can't boot to system cause some step failed in the process.
If you flashed successfully mdtp images now follow the steps to boot to recovery and then follow those indicated to install LOS.
Click to expand...
Click to collapse
Thanks; this is what I did:
from TWRP I rebooted to recovery
it took me straight to fastboot again
so I
Code:
fastboot boot twrp-daisy-3.3.1-0-offain.img
again and mounted system partition then I flashed LOS
and the process went fine this time but when I rebooted to the system
it's back to fastboot again!
BenG7 said:
Thanks; this is what I did:
from TWRP I rebooted to recovery
it took me straight to fastboot again
so I
again and mounted system partition then I flashed LOS
and the process went fine this time but when I rebooted to the system
it's back to fastboot again!
Click to expand...
Click to collapse
This is exactly what I tried to tell you: your issue concerning to this thread was solved.
Now you have an issue regarding how to flash and boot to system attempting to install LOS. TWRP is perfectly capable to mount/remount or unmount partitions if needed, no need an action from the user, this is not the reason why you are not booting but the method and steps is discussed more properly in the same thread.
From here you can take one of hese three routes:
- To insist with trying to flash LOS.
- Flash other rom or a previous known working rom.
- Return completely to stock by flashing a full global rom.
Just I could recommend that for the future when you flash a stock rom take a backup of the most important partitions (without userdata) this could avoid that you need to use EDL anymore.
Disclaimer :
Code:
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Your warranty will be void if you tamper with any part of your device / software.
Download :
OnePlus7TOxygen_14.I.05_OTA_fastboot
Code:
ro.vendor.build.date=Wed Sep 25 21:54:29 CST 2019
ro.vendor.build.date.utc=1569419669
ro.vendor.build.fingerprint=OnePlus/OnePlus7T/OnePlus7T:10/QKQ1.190716.003/1909250940:user/release-keys
ro.vendor.build.id=QKQ1.190716.003
ro.vendor.build.tags=release-keys
ro.vendor.build.type=user
ro.vendor.build.version.incremental=1909250940
ro.vendor.build.version.release=10
ro.vendor.build.version.sdk=29
ro.product.vendor.brand=OnePlus
ro.product.vendor.device=OnePlus7T
ro.product.vendor.manufacturer=OnePlus
ro.product.vendor.name=OnePlus7T
Fastboot Commands :
Code:
fastboot flash aop_a aop.img
fastboot flash aop_b aop.img
fastboot flash bluetooth_a bluetooth.img
fastboot flash bluetooth_b bluetooth.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash dsp_a dsp.img
fastboot flash dsp_b dsp.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash logo_a logo.img
fastboot flash logo_b logo.img
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash oem_stanvbk oem_stanvbk.img
fastboot flash qupfw_a qupfw.img
fastboot flash qupfw_b qupfw.img
fastboot flash storsec_a storsec.img
fastboot flash storsec_b storsec.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
Credits :
jamflux
Regards,
acervenky
reserved
Thanks very much for this.
.
Is there any solution for root ?
I am not able to root using magisk patched boot.img
.
Magisk beta stucking at bootloader warning info at boot.
Magisk canary giving Qualcomm crash dump error on boot.
RohanAJoshi said:
Thanks very much for this.
.
Is there any solution for root ?
I am not able to root using magisk patched boot.img
.
Magisk beta stucking at bootloader warning info at boot.
Magisk canary giving Qualcomm crash dump error on boot.
Click to expand...
Click to collapse
Download the attachment, and flash it using this command :
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
This should help you with the image patched using beta.
Regards,
acervenky
acervenky said:
Download the attachment, and flash it using this command :
This should help you with the image patched using beta.
Regards,
acervenky
Click to expand...
Click to collapse
OK, I will try this and report you back soon.
acervenky said:
Download the attachment, and flash it using this command :
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
This should help you with the image patched using beta.
Regards,
acervenky
Click to expand...
Click to collapse
tried this, not working.
same as before, with magisk beta patched, phone stuck at bootloader unlock warning.
.
steps i did
flashed vbmeta as you said.
flashed patched boot.
reboot.
.
my doubt is :
in your fist post, for plashing vbmeta, you used _a & _b
but in this command, its only vbemeta, not a or b
RohanAJoshi said:
tried this, not working.
same as before, with magisk beta patched, phone stuck at bootloader unlock warning.
.
steps i did
flashed vbmeta as you said.
flashed patched boot.
reboot.
.
my doubt is :
in your fist post, for plashing vbmeta, you used _a & _b
but in this command, its only vbemeta, not a or b
Click to expand...
Click to collapse
Managed to compile a kernel with avb flag disabled and vbmeta removed, download it from this link, please note that they're unpatched and there may be bugs if oneplus messed up something in the source code.
Please patch it with beta and canary, report if it works!
Regards,
acervenky
acervenky said:
Managed to compile a kernel with avb flag disabled and vbmeta removed, download it from this link, please note that they're unpatched and there may be bugs if oneplus messed up something in the source code.
Please patch it with beta and canary, report if it works!
Regards,
acervenky
Click to expand...
Click to collapse
which file should i dowload ?
stock or mod ?
RohanAJoshi said:
which file should i dowload ?
stock or mod ?
Click to expand...
Click to collapse
Mod, I've uploaded the stock incase you face any problems and need to revert!
Regards,
acervenky
acervenky said:
Mod, I've uploaded the stock incase you face any problems and need to revert!
Regards,
acervenky
Click to expand...
Click to collapse
that mod.img is going through bootloader warning screen, its boot looping further on boot animation.
did not tried patched magisk of mod file.
I thought 1st try plain if it booting or not, if not booting clean file, magisk mod wont boot.
RohanAJoshi said:
that mod.img is going through bootloader warning screen, its boot looping further on boot animation.
did not tried patched magisk of mod file.
I thought 1st try plain if it booting or not, if not booting clean file, magisk mod wont boot.
Click to expand...
Click to collapse
Same issue here, the mod.img file bootloops after warning of bootloader. Please help! The stock image brings me back to the qualcomm crashdump mode.
Another issue, while flashing the fastboot images initially, for system and vendor files, the following was displayed.
“Invalid sparse file format at header magi
sending sparse system_a (775469 KB)...
OKAY [ 17.955s]
writing ‘system_a’...
FAILED (remote: Partition not found)
finished. total time: 17.971s”
The same displays for system_b, vendor_a and vendor_b. I’ve tried SYSTEM_a, System_a, System_A, SYSTEM_A but to no avail. Do you think this might be the cause of the Qualcomm crash dump mode?
How2Kritin said:
Same issue here, the mod.img file bootloops after warning of bootloader. Please help! The stock image brings me back to the qualcomm crashdump mode.
Another issue, while flashing the fastboot images initially, for system and vendor files, the following was displayed.
“Invalid sparse file format at header magi
sending sparse system_a (775469 KB)...
OKAY [ 17.955s]
writing ‘system_a’...
FAILED (remote: Partition not found)
finished. total time: 17.971s”
The same displays for system_b, vendor_a and vendor_b. I’ve tried SYSTEM_a, System_a, System_A, SYSTEM_A but to no avail. Do you think this might be the cause of the Qualcomm crash dump mode?
Click to expand...
Click to collapse
It's not possible to flash it properly
Read the following reply from @mauronofrio
"actually is not possible, the oneplus 7t is using the new /super partition and on op7t is not possible to flash a full stock rom from fastboot, but you can flash all partitions except system, vendor, product (The 3 partitions that contains the rom), he should boot in twrp to try to restore his device, maybe i can help a bit, but it's something really new and i think the oneplus 7t is the first one that is supporting this"
cultofluna said:
It's not possible to flash it properly
Read the following reply from @mauronofrio
"actually is not possible, the oneplus 7t is using the new /super partition and on op7t is not possible to flash a full stock rom from fastboot, but you can flash all partitions except system, vendor, product (The 3 partitions that contains the rom), he should boot in twrp to try to restore his device, maybe i can help a bit, but it's something really new and i think the oneplus 7t is the first one that is supporting this"
Click to expand...
Click to collapse
Interesting! So the backup and restore vendor, system won't work via twrp?
Anyone tried manually flashing Magisk via twrp?
Regards,
acervenky
acervenky said:
Interesting! So the backup and restore vendor, system won't work via twrp?
Anyone tried manually flashing Magisk via twrp?
Regards,
acervenky
Click to expand...
Click to collapse
I did, initially but it said that the /system, /vendor and /product partitions couldn’t be mounted. When I tried to restore I got stuck in the fastboot mode. After that, I’ve used your file and got stuck with the qualcomm crashdump mode.
FIXED
Final update: Mauronofrio has helped me out and fixed everything for me, a huge thanks to him. My device is in perfect condition now. Thanks a lot to everyone who tried to help too!
I wonder, if a T-Mobile 7T is unlocked can we use this method to install the international firmware on it?
Is this for EU Model?
Hot-Proton said:
Is this for EU Model?
Click to expand...
Click to collapse
No, Global!
Regards,
acervenky
Ok that is bad. Wait for EU Version.
for T-Mobile no, I messed up mine, it boots but no wifi and data. I did a remote session with oneplus but they can't fix it, they don't have the firmware for the tmobile version, unless if someone has already patched the MSM, but sadly nothing yet
---------- Post added at 07:50 AM ---------- Previous post was at 07:48 AM ----------
How2Kritin said:
Final update: Mauronofrio has helped me out and fixed everything for me, a huge thanks to him. My device is in perfect condition now. Thanks a lot to everyone who tried to help too!
Click to expand...
Click to collapse
how did you reach out to him, just wanna know if there's a fix for my wifi and data no connections, T-Mobile unlock bootloader, tried flashing the modem from here but no effect and when I tried deleting it, sim card cannot be detected
Hello, I've been trying to install TWRP on my 5z (ZS620KL).
Whenever I try to use the "fastboot flash recovery recovery.img", I get the output:
Sending 'recovery' (25244 KB) OKAY [ 0.596s]
Writing 'recovery' FAILED (remote: '(recovery_b) No such partition')
I tried switching to the other partition using:
"fastboot --set-active=a" and "fastboot --set-active=b"
But it lead to no change whatsoever.
I'll be very thankful for any suggestions
Can provide any additional info, if needed
fastboot flash boot boot.img is the command you are looking for
Obviously you need you download the boot image and twrp zip for the version you are looking to install
jmancorp said:
fastboot flash boot boot.img is the command you are looking for
Obviously you need you download the boot image and twrp zip for the version you are looking to install
Click to expand...
Click to collapse
Thanks This solved my issue
jmancorp said:
fastboot flash boot boot.img is the command you are looking for
Obviously you need you download the boot image and twrp zip for the version you are looking to install
Click to expand...
Click to collapse
I have the same problem.
But when I fastboot flash boot boot.img and reboot .
It can not into twrp
It still into fastboot mode
Thanks in advance.
Exactly a year ago I bought Poco F3, unlocked the bootloader and installed ArrowOS. Now I'm trying to figure out how to change my ROM and I can't really find any answers. I have the ArrowOS recovery and it's useless, I can't install another recovery with it. My fastboot also seems to be broken(?), it has a different logo and it's detected on my computer when I do (fastboot devices) but other than that it gives me a bunch of errors
I would like to at least know how to change the recovery. Is it possible that my bootloader got locked? One last thing, when I installed ArrowOS I used TWRP and updated it using OTA updates, now TWRP is gone.
Please help me
You need fastboot for TWRP.
It could not have gotten locked, no.
Arealhooman said:
It could not have gotten locked, no.
Click to expand...
Click to collapse
I just found a guide on Youtube for flashing twrp and I followed it to the (fastboot boot <TWRP>) part and I got this error
Sending 'boot.img' (196608 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
Does this mean it got locked..?
Uh….maybe… did you lock it… what does it say in dev Setting sunder oem unlock.
Arealhooman said:
Uh….maybe… did you lock it… what does it say in dev Setting sunder oem unlock.
Click to expand...
Click to collapse
I don't have any oem unlock option in ArrowOS and I never locked anything wtf, I just used it as a normal phone and only did OTA updates + sometimes FW updates when required
Is there anyway to fix it?
ADB & Fastboot Binaries: https://developer.android.com/studio/releases/platform-tools
OrangeFox Recovery (recommended): https://orangefox.download/device/alioth
Install the Recovery ZIP by either ADB Sideload in ArrowOS Recovery
or you can extract the "recovery.img" and fastboot boot it ("fastboot boot recovery.img") and select "Install current Recovery"
Then you simply flash the ROM.zip (select "Reflash Recovery after ROM Flash") -> Reboot Recovery -> Format Data
The OTA Update has replaced your TWRP with ArrowOS Recovery, because ROM Updates replace the boot-partition (along with other system related partitions). The boot-partition contains the recovery-environment.
Only install Custom Recoveries from inside the Recovery, because Fastboot can only replace partitions entirely (and boot-partitions contains both bootloader & recovery)
The bootloader of the Poco F3 cannot (or shouldn't) be locked on Custom Software.
gobertel said:
I just found a guide on Youtube for flashing twrp and I followed it to the (fastboot boot <TWRP>) part and I got this error
Sending 'boot.img' (196608 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
Does this mean it got locked..?
Click to expand...
Click to collapse
Download these:
https://sourceforge.net/projects/mipa-project/files/arrow-mipa/arrow-13.0/alioth/Additions/boot.img/download
https://sourceforge.net/projects/mipa-project/files/arrow-mipa/arrow-13.0/alioth/Additions/vendor_boot.img/download
First link, "fastboot flash boot boot.img"
Second link, "fastboot flash vendor_boot vendor_boot.img"
Then Fastboot booting into your Recovery-file should work.
Also, what's the problem with ArrowOS anyway? We've ArrowOS MiPa, it's a good and reliable ROM.
cyanGalaxy said:
Download these:
https://sourceforge.net/projects/mipa-project/files/arrow-mipa/arrow-13.0/alioth/Additions/boot.img/download
https://sourceforge.net/projects/mipa-project/files/arrow-mipa/arrow-13.0/alioth/Additions/vendor_boot.img/download
First link, "fastboot flash boot boot.img"
Second link, "fastboot flash vendor_boot vendor_boot.img"
Then Fastboot booting into your Recovery-file should work.
Click to expand...
Click to collapse
I noticed that these are for ArrowOS 13, I'm on 12.1 and they did not work
Do you also suggest I go into fastboot by which method because each one looks different
Recovery > Advanced > Enter fastboot
Or
Hold power button with volume down method
Also I'm just looking to update to Android 13 in general
Thank you for helping me out by the way
gobertel said:
I noticed that these are for ArrowOS 13, I'm on 12.1 and they did not work
Do you also suggest I go into fastboot by which method because each one looks different
Recovery > Advanced > Enter fastboot
Or
Hold power button with volume down method
Also I'm just looking to update to Android 13 in general
Click to expand...
Click to collapse
Both methods of booting into Fastboot is the same I would guess.
Yes we do have ArrowOS MiPa, you should only need to flash the ArrowOS 13 MiPa ROM ZIP in Recovery, but I rather recommend you using OrangeFox or TWRP for that.
What do you mean by "did not work". "Did not work" can mean anything.
Are you using the latest official ADB & Fastboot Binaries? The ones I've given you?
If yes, you can use this Payload Dumper Tool, to extract the "vendor_boot.img" and "boot.img" from ArrowOS 12. Maybe those from Arrow v12 can be flashed.
[Windows] Payload Dumper GUI - dump boot.img and other img files from payload.bin.
Hello there. Was bored and decided to make a gui that dumps Payload.bin file for easy flashing. Tested on Lineage OS 18 Payload.bin Result: Credits: Based on vm03 payload_dumper script. Github: Payload_dumper.py...
forum.xda-developers.com
cyanGalaxy said:
Both methods of booting into Fastboot is the same I would guess.
Yes we do have ArrowOS MiPa, you should only need to flash the ArrowOS 13 MiPa ROM ZIP in Recovery, but I rather recommend you using OrangeFox or TWRP for that.
What do you mean by "did not work". "Did not work" can mean anything.
Click to expand...
Click to collapse
fastboot flash boot boot.img
Sending 'boot_a' (196608 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
fastboot flash vendor_boot vendor_boot.img
Sending 'vendor_boot_a' (98304 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
fastboot boot recovery.img
Sending 'boot.img' (196608 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
Another thing to add is I still I get the unlock symbol when booting up the phone, I dont know if that makes a difference
cyanGalaxy said:
Are you using the latest official ADB & Fastboot Binaries? The ones I've given you?
If yes, you can use this Payload Dumper Tool, to extract the "vendor_boot.img" and "boot.img" from ArrowOS 12. Maybe those from Arrow v12 can be flashed.
[Windows] Payload Dumper GUI - dump boot.img and other img files from payload.bin.
Hello there. Was bored and decided to make a gui that dumps Payload.bin file for easy flashing. Tested on Lineage OS 18 Payload.bin Result: Credits: Based on vm03 payload_dumper script. Github: Payload_dumper.py...
forum.xda-developers.com
Click to expand...
Click to collapse
Yes I'm using the exact one you gave me and I will try it
gobertel said:
Yes I'm using the exact one you gave me and I will try it
Click to expand...
Click to collapse
Yup try it.
Else, here I have the vendor_boot.img & boot.img from the latest ArrowOS MiPa (February). More up-to-date than the SourceForge links.
Either the 2 files from ArrowOS v12, or the latest v13 ones that I've uploaded here, should definitely work.
Also try rebooting Fastboot Mode.
XDA doesn't let me upload the boot.img ඞ
cyanGalaxy said:
XDA doesn't let me upload the boot.img ඞ
Click to expand...
Click to collapse
Starting to think I should just give up, no matter what I do I get (Download is not allowed on locked devices)
The fastboot method you suggested does not work, it gets stuck on (waiting for any devices) but the recovery one works although like I said, I get the error no matter what I do
Is it locked or what?? I'm trying to figure that out and if it is how did it even get locked in the first place
I'm guessing there's no way to resolve it and that I'll be stuck on Android 12 for eternity
So sorry for wasting your time, I always end up with weird issues in everything
gobertel said:
Starting to think I should just give up, no matter what I do I get (Download is not allowed on locked devices)
The fastboot method you suggested does not work, it gets stuck on (waiting for any devices) but the recovery one works although like I said, I get the error no matter what I do
Is it locked or what?? I'm trying to figure that out and if it is how did it even get locked in the first place
I'm guessing there's no way to resolve it and that I'll be stuck on Android 12 for eternity
So sorry for wasting your time, I always end up with weird issues in everything
Click to expand...
Click to collapse
Waiting for any devices means your PC does not detect the phone.
Download this: https://cdn.alsgp0.fds.api.mi-img.com/micomm/MiFlash2020-3-14-0.rar
And install the USB driver.
And no it's not locked, the Unlocked symbol during Boot is normal. I think it was a bug with older ArrowOS Bootloader versions. Not quite sure.
cyanGalaxy said:
Waiting for any devices means your PC does not detect the phone.
Download this: https://cdn.alsgp0.fds.api.mi-img.com/micomm/MiFlash2020-3-14-0.rar
And install the USB driver.
And no it's not locked, the Unlocked symbol during Boot is normal. I think it was a bug with older ArrowOS Bootloader versions. Not quite sure.
Click to expand...
Click to collapse
IT WORKED. Thank you so much, it was a driver issue but the exact version you gave me didn't work, I had to find another one