Related
Hey everybody.
So I had my phone rooted for a week now, but I had plenty of problems with root (Magisk 16.4, TWRP 3.2.1.0). Running Android P beta p2.
I wanted to simply restore the phone to it's stock state. Main idea was to get OS reinstalled and stock recovery flashed over TWRP.
When ever I tried to flash the boot.img from the stock image in fastboot I got the error saying "FAILED (remote: Requested download size is more than max allowed".
So mid process I read somewhere I might have to unlock unlock_critical. I tried running that but no response from the phone. I didn't want to interrupt so I left it running for a few minutes, came back and nothing has changed. Except for the phone not being able to boot to Android. And so here I am stuck in a boot loop.
So I read here: https://forum.xda-developers.com/pixel-2-xl/help/hard-bricked-t3770769
And realized maybe I should try this skipsoft toolkit. Well no luck.
This is what I get when I try to use option 9. (Download/Extract/Flash Google Factory Stock Image [Flash Part or Whole Rom]). I choose to flash the whole ROM.
Here is what I got.
Starting Flash Process..
Flashing Bootloader Image..
target didn't report max-download-size
sending 'bootloader' (36344 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.003s
An error occured when flashing the image
Try rebooting the device manually back to fastboot mode:
1. Unplug the usb cable
2. Hold the Power and Volume Down buttons until it reboots to Fastboot Mode.
From the main menu in the Toolkit choose the Download/Extract/Flash menu, then
select Flash previously downloaded image.
Sometimes there is a glitch in the flash process and doing it again will fix it.
Press any key to return to the Main Menu..
I gave Deuces Bootloop tool script a try and this is what I got:
Deuces-flash-all-script-V4.5-Windows
for Taimen or Walleye - Google Pixel 2 / XL
USE AT YOUR OWN RISK
Press any key to continue . . .
Make Sure your Device is in Fastboot Mode
(Power off, hold Volume-Down, hold Power)
Once you are in fastboot,
Press any key to continue . . .
Unlock Bootloader[Y/N]?y
Running Unlock
Look at your device,
press up arrow and Power to confirm
FAILED (remote: Device already : unlocked!)
Finished. Total time: 0.002s
This will say "failed" if already unlocked - ignore
Running Unlock_critical
Look at your device,
press up arrow and Power to confirm
FAILED (remote: unknown command)
Finished. Total time: 0.002s
This will say "failed" if already unlocked - ignore
Locating Bootloader and Radio Filenames
Flashing...
it is safe to ignore errors about active partition - there are multiple entries to support multiple versions of platform tools
File Not Found
File Not Found
fastboot: error: Device does not support slots
fastboot: error: Device does not support slots
rebooting into bootloader OKAY [ 0.002s]
Finished. Total time: 0.003s
rebooting into bootloader OKAY [ 0.002s]
Finished. Total time: 0.003s
Slot _b does not exist. supported slots are:
a
b
fastboot: error: Device does not support slots
rebooting into bootloader OKAY [ 0.003s]
Finished. Total time: 0.003s
rebooting into bootloader OKAY [ 0.002s]
Finished. Total time: 0.003s
Slot _a does not exist. supported slots are:
a
b
fastboot: error: Device does not support slots
fastboot: error: cannot load 'abl.img': No such file or directory
fastboot: error: cannot load 'aes.img': No such file or directory
fastboot: error: cannot load 'apdp.img': No such file or directory
fastboot: error: cannot load 'boot.img': No such file or directory
fastboot: error: Failed to identify current slot
fastboot: error: cannot load 'cmnlib64.img': No such file or directory
fastboot: error: cannot load 'devcfg.img': No such file or directory
fastboot: error: cannot load 'dtbo.img': No such file or directory
fastboot: error: cannot load 'hyp.img': No such file or directory
fastboot: error: cannot load 'keymaster.img': No such file or directory
fastboot: error: cannot load 'laf.img': No such file or directory
fastboot: error: Failed to identify current slot
fastboot: error: cannot load 'msadp.img': No such file or directory
fastboot: error: cannot load 'pmic.img': No such file or directory
fastboot: error: cannot load 'rpm.img': No such file or directory
fastboot: error: cannot load 'tz.img': No such file or directory
fastboot: error: cannot load 'vbmeta.img': No such file or directory
fastboot: error: cannot load 'vendor.img': No such file or directory
fastboot: error: cannot load 'xbl.img': No such file or directory
Flashing System A
fastboot: error: cannot load 'system.img': No such file or directory
Flashing System B
fastboot: error: cannot load 'system_other.img': No such file or directory
fastboot: error: Device does not support slots
Setting current slot to 'b' FAILED (status read failed (Too many links))
Finished. Total time: 5.871s
< waiting for any device >
Any help would be greatly appreciated.
Thank you in advance.
jan_ruc said:
Hey everybody. So I had my phone rooted for a week now, but I had plenty of problems with root (Magisk 16.4, TWRP 3.2.1.0)...
Click to expand...
Click to collapse
I don't have this device but, your best bet is probably to post this question within the following thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3702418
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
hELLO..
I have had a moto g5 with oreo and magisk installed I tried to unistall magisk from magisk app after reboot it told me that startup failed then flashed an nougat rom and it worked perfectly but without imei numbers so i deleted cache from twrp recovery and tried to install the same software again but it gave me the error at the end ..what should I know now to fix the mobile knowing that when i try to select recoverymode it tells me ersing and then takes m back to fastboot
note the first time i just opened a bat file with the software that installed the software automatically..
the bat file told me that
<bootloader> slot-count not found
<bootloader> slot suffixes not found
<bootloader>has-slot:fsg not found
Flash this firmware https://drive.google.com/file/d/1cESQyuRpeUAmmEn67_to0sQ0KLhkMnWM/view (Oreo 8.1, February 2019 security patch) using fastboot and commands below. All the data in the internal storage of the phone will be erased.
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Hi. Mine G5 is bricked as well.
When I`m trying to do what u said Andrej I got that:
C:\platform-tools>fastboot oem fb_mode_set
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash partition gpt.bin
(bootloader) is-logicalartition: not found
Sending 'partition' (45 KB) OKAY [ 0.169s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
Any ideas?
pablito1984 said:
Hi. Mine G5 is bricked as well.
When I`m trying to do what u said Andrej I got that:
Any ideas?
Click to expand...
Click to collapse
The firmware you are trying to flash is too old hense the security downgrade error
You must use firmware that is equal to or newer than what was previously flashed on it
Firmware available at
https://mirrors.lolinet.com/firmware/moto/cedric/official/
TheFixItMan said:
The firmware you are trying to flash is too old hense the security downgrade error
You must use firmware that is equal to or newer than what was previously flashed on it
Firmware available at
Click to expand...
Click to collapse
Thank you for your reply.
I`ve downloaded XT1675_CEDRIC_RETGB_SS_8.1.0_OPPS28.85-13-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
as my phone model is XT1675.
I don`t know why, but when I`m trying to put fastboot oem fb_mode_set and it gives me that error
pablito1984 said:
Thank you for your reply.
I`ve downloaded XT1675_CEDRIC_RETGB_SS_8.1.0_OPPS28.85-13-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
as my phone model is XT1675.
I don`t know why, but when I`m trying to put fastboot oem fb_mode_set and it gives me that error
Click to expand...
Click to collapse
That command is just to tell the phone you are about to flash firmware and the clear command at the end exists this mode
You don't need to use these commands it's just a way of telling the phone what you are doing and to start the phone normally after the flashing
You should be able to start with gpt (presuming you have found a firmware that is the same or newer than what you have on the phone already)
TheFixItMan said:
That command is just to tell the phone you are about to flash firmware and the clear command at the end exists this mode
You don't need to use these commands it's just a way of telling the phone what you are doing and to start the phone normally after the flashing
You should be able to start with gpt (presuming you have found a firmware that is the same or newer than what you have on the phone already)
Click to expand...
Click to collapse
Thanks for explaining me that
I`ve downloaded now CEDRIC_RETAIL_8.1.0_OPPS28.85-16-6_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
And this time it`s not saying anything about downgrade, but I got this:
C:\platform-tools>fastboot flash partition gpt.bin
(bootloader) is-logical: partition: not found
Sending 'partition' (45 KB) OKAY [ 0.169s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
pablito1984 said:
Thanks for explaining me that
I`ve downloaded now CEDRIC_RETAIL_8.1.0_OPPS28.85-16-6_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
And this time it`s not saying anything about downgrade, but I got this:
Click to expand...
Click to collapse
I presume you can get into the bootloader without using a sdcard for a hard bricked device
If so skip gpt and bootloader parts of the firmware - these don't need to be flashed unless your phone was hard bricked (just get a red flashing led if mmcblk0 sdcard not inserted)
Also make sure you have the Motorola drivers installed and that you are using the latest fastboot drivers from the android sdk
TheFixItMan said:
I presume you can get into the bootloader without using a sdcard for a hard bricked device
If so skip gpt and bootloader parts of the firmware - these don't need to be flashed unless your phone was hard bricked (just get a red flashing led if mmcblk0 sdcard not inserted)
Also make sure you have the Motorola drivers installed and that you are using the latest fastboot drivers from the android sdk
Click to expand...
Click to collapse
Yes. I can get into bootloader, but I can`t do anything over there except restarting and checking logs.
After checking the logs I can see :
Start up failed:
Your device didn`t start up successfully.
Use the Software Repair Assistant on computer to repair your device.
Connect your device to your computer to get Software Repair Assistant.
AP Fastboot Flash Mode (Secure)
Fastboot Reason: Last time flashing failed
USB Connected
failed to validate recovery iumage
ERROR: Failed to pass validation, backup to fastboot
Boot up failed
Click to expand...
Click to collapse
Tried to use Lenovo Moto smart assistant to fix it, but it doesn`t see the device.
I`ve got all drivers, sdk, etc.
When tried to use fastboot I got this:
C:\platform-tools>fastboot oem fb_mode_set
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash partition gpt.bin
(bootloader) is-logicalartition: not found
Sending 'partition' (45 KB) OKAY [ 0.170s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash bootloader bootloader.img
(bootloader) is-logical:bootloader: not found
Sending 'bootloader' (5179 KB) OKAY [ 0.331s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition aboot
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash logo logo.bin
(bootloader) is-logical:logo: not found
Sending 'logo' (2242 KB) OKAY [ 0.240s]
Writing 'logo' (bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash boot boot.img
(bootloader) is-logical:boot: not found
Sending 'boot' (16384 KB) OKAY [ 0.689s]
Writing 'boot' (bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash recovery recovery.img
(bootloader) is-logical:recovery: not found
Sending 'recovery' (16484 KB) OKAY [ 0.694s]
Writing 'recovery' (bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash dsp adspso.bin
(bootloader) is-logical:dsp: not found
Sending 'dsp' (16384 KB) OKAY [ 0.688s]
Writing 'dsp' (bootloader) Failed to erase partition
(bootloader) Failed to flash partition dsp
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash oem oem.img
(bootloader) is-logicalem: not found
Sending 'oem' (148900 KB) OKAY [ 4.969s]
Writing 'oem' (bootloader) Image o failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.0
(bootloader) is-logical:system: not found
Sending 'system' (256537 KB) OKAY [ 8.462s]
Writing 'system' (bootloader) Image s failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.1
(bootloader) is-logical:system: not found
Sending 'system' (256653 KB) OKAY [ 8.529s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.2
(bootloader) is-logical:system: not found
Sending 'system' (257978 KB) OKAY [ 8.446s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.3
(bootloader) is-logical:system: not found
Sending 'system' (260705 KB) OKAY [ 8.488s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.4
(bootloader) is-logical:system: not found
Sending 'system' (257421 KB) OKAY [ 8.464s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.5
(bootloader) is-logical:system: not found
Sending 'system' (257865 KB) OKAY [ 8.506s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.6
(bootloader) is-logical:system: not found
Sending 'system' (252667 KB) OKAY [ 8.402s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.7
(bootloader) is-logical:system: not found
Sending 'system' (253700 KB) OKAY [ 8.409s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.8
(bootloader) is-logical:system: not found
Sending 'system' (250301 KB) OKAY [ 8.271s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash modem NON-HLOS.bin
(bootloader) is-logical:modem: not found
Sending 'modem' (66366 KB) OKAY [ 2.329s]
Writing 'modem' (bootloader) Failed to erase partition
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot erase modemst1
Erasing 'modemst1' (bootloader) Failed to erase partition
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot erase modemst2
Erasing 'modemst2' (bootloader) Failed to erase partition
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash fsg fsg.mbn
(bootloader) is-logical:fsg: not found
Sending 'fsg' (2956 KB) OKAY [ 0.258s]
Writing 'fsg' (bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot erase cache
Erasing 'cache' (bootloader) Failed to erase partition
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot erase userdata
Erasing 'userdata' (bootloader) Failed to erase partition
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot erase customize
Erasing 'customize' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot erase clogo
Erasing 'clogo' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot oem fb_mode_clear
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.004s
Click to expand...
Click to collapse
pablito1984 said:
Yes. I can get into bootloader, but I can`t do anything over there except restarting and checking logs.
After checking the logs I can see :
Tried to use Lenovo Moto smart assistant to fix it, but it doesn`t see the device.
I`ve got all drivers, sdk, etc.
When tried to use fastboot I got this:
Click to expand...
Click to collapse
Either your setup is wrong - try another pc USB cable etc or you have a motherboard fault & need to replace it
TheFixItMan said:
That command is just to tell the phone you are about to flash firmware and the clear command at the end exists this mode
You don't need to use these commands it's just a way of telling the phone what you are doing and to start the phone normally after the flashing
You should be able to start with gpt (presuming you have found a firmware that is the same or newer than what you have on the phone already)
Click to expand...
Click to collapse
im having the same issue with moto e5play xt1921-1 i dont know what the latest fw is
ghettozo said:
im having the same issue with moto e5play xt1921-1 i dont know what the latest fw is
Click to expand...
Click to collapse
Neither do i as I don't own your phone
Go to your own phone forum or Google for firmware for your device
To flash gpt and bootloader it must be the same or newer than version on device and an unlocked bootloader to avoid permissions errors especially if has been unlocked before
TheFixItMan said:
Neither do i as I don't own your phone
Go to your own phone forum or Google for firmware for your device
To flash gpt and bootloader it must be the same or newer than version on device and an unlocked bootloader to avoid permissions errors especially if has been unlocked before
Click to expand...
Click to collapse
thanks. yes im using the forum here and google but im having issues
thankyou\
Okay, I've seen similar problems to mine but none of the suggested solutions seem to work out the problem. This seems to be the recommended solution, but it's not getting me anywhere:
https://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478
My bootloader is unlocked. I unlocked it the second I got the phone to save pain down the road. I've now hit the fork. It's an unlocked phone, not Verizon, I'm not sure what the original carrier was, it was second-hand and under no warranty. I'm on Android 10 Marlin, I updated it to the latest about a month ago. I got up to do some laundry last night and came back to a spontaneously dead phone. For detail, I was transferring a movie to my phone via USB to internal storage so I could watch it later. No idea what happened while I was up, but the phone was in the exact same position as when I left. Developer options were on, USB debugging was on.
What I have now is this: It will enter fastboot. When I prompt it to boot to recovery, it shuts down, or it will go to the unlocked bootloader warning screen, allow me to pause/continue booting, at which point it will either go directly to black, or briefly show the Google bootloader and then shut off. When I leave it on a charge, either trickle or full, it will sometimes loop through the unlocked bootloader warning, flicking that screen on and off, but sometimes it's just off. I never see the charging battery screen. I've left it to charge for hours.
Sometimes windows acknowledges a USB device is connected and that it's android, but at no point can I access storage. When working through a command line prompt, acknowledges that the device is there, but trying to flash anything fails immediately. Here is a sample of some of my results.
When trying the flash-all solution:
PHP:
Sending 'bootloader_b' (32480 KB) OKAY [ 1.779s]
Writing 'bootloader_b' FAILED (remote: 'Verify bootloader image failed on production device.')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.040s]
Finished. Total time: 0.044s
The device goes black. I'll bring it back up to fastboot and the command line spits this out:
PHP:
< waiting for any device >
Sending 'radio_b' (57156 KB) OKAY [ 3.785s]
Writing 'radio_b' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.199s]
Finished. Total time: 0.207s
Using fastboot to try and boot factory bootloader, it says it's worked but then the phone again just goes to black and does nothing:
PHP:
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot boot bootloader-marlin-8996-012001-1908071822.img
< waiting for any device >
creating boot image...
creating boot image - 33261568 bytes
Sending 'boot.img' (32482 KB) OKAY [ 2.100s]
Booting OKAY [ 0.531s]
Finished. Total time: 2.944s
Flashing that factory bootloader, seems successful, again, back to black screen and nothing until going back to fastboot:
PHP:
>> PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot boot bootloader-marlin-8996-012001-1908071822.img
>> < waiting for any device >
>> creating boot image...
>> creating boot image - 33261568 bytes
>> Sending 'boot.img' (32482 KB) OKAY [ 2.100s]
>> Booting OKAY [ 0.531s]
>> Finished. Total time: 2.944s
And finally, trying to push an update image over fastboot:
PHP:
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot update image-marlin-qp1a.191005.007.a3.zip
--------------------------------------------
Bootloader Version...: N/A
Baseband Version.....: N/A
Serial Number........: HT6AD0202367
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.044s]
Checking 'version-bootloader' FAILED
Device version-bootloader is 'N/A'.
Update requires '8996-012001-1908071822'.
fastboot: error: requirements not met!
I am wondering if locking the bootloader would give this thing what it wants and let me boot into recovery, but I have a terrible feeling it would just further lock me out of saving this phone. Does anyone have any insight? Is this a shot motherboard? Sorry, I know my problem has a ton of commonalities with a lot of other people's but it seems for all my searching, reading and Googling that it's idiosyncratic to the point of every solution not working for me. Thank you so much.
Edit: For interest, I just saw the screen throw up an odd block of static, for lack of a better term. In the bottom right corner, it took up a little more than 1/4 of the screen. It looked lik there was cut off text at the top, too little showing to read. It disappeared before I could take a picture with a spare phone. It lasted maybe 5 seconds and then it was gone. It's on USB charge, not sitting on fastboot right now.
ekjean said:
Okay, I've seen similar problems to mine but none of the suggested solutions seem to work out the problem. This seems to be the recommended solution, but it's not getting me anywhere:
https://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478
My bootloader is unlocked. I unlocked it the second I got the phone to save pain down the road. I've now hit the fork. It's an unlocked phone, not Verizon, I'm not sure what the original carrier was, it was second-hand and under no warranty. I'm on Android 10 Marlin, I updated it to the latest about a month ago. I got up to do some laundry last night and came back to a spontaneously dead phone. For detail, I was transferring a movie to my phone via USB to internal storage so I could watch it later. No idea what happened while I was up, but the phone was in the exact same position as when I left. Developer options were on, USB debugging was on.
What I have now is this: It will enter fastboot. When I prompt it to boot to recovery, it shuts down, or it will go to the unlocked bootloader warning screen, allow me to pause/continue booting, at which point it will either go directly to black, or briefly show the Google bootloader and then shut off. When I leave it on a charge, either trickle or full, it will sometimes loop through the unlocked bootloader warning, flicking that screen on and off, but sometimes it's just off. I never see the charging battery screen. I've left it to charge for hours.
Sometimes windows acknowledges a USB device is connected and that it's android, but at no point can I access storage. When working through a command line prompt, acknowledges that the device is there, but trying to flash anything fails immediately. Here is a sample of some of my results.
When trying the flash-all solution:
PHP:
Sending 'bootloader_b' (32480 KB) OKAY [ 1.779s]
Writing 'bootloader_b' FAILED (remote: 'Verify bootloader image failed on production device.')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.040s]
Finished. Total time: 0.044s
The device goes black. I'll bring it back up to fastboot and the command line spits this out:
PHP:
< waiting for any device >
Sending 'radio_b' (57156 KB) OKAY [ 3.785s]
Writing 'radio_b' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.199s]
Finished. Total time: 0.207s
Using fastboot to try and boot factory bootloader, it says it's worked but then the phone again just goes to black and does nothing:
PHP:
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot boot bootloader-marlin-8996-012001-1908071822.img
< waiting for any device >
creating boot image...
creating boot image - 33261568 bytes
Sending 'boot.img' (32482 KB) OKAY [ 2.100s]
Booting OKAY [ 0.531s]
Finished. Total time: 2.944s
Flashing that factory bootloader, seems successful, again, back to black screen and nothing until going back to fastboot:
PHP:
>> PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot boot bootloader-marlin-8996-012001-1908071822.img
>> < waiting for any device >
>> creating boot image...
>> creating boot image - 33261568 bytes
>> Sending 'boot.img' (32482 KB) OKAY [ 2.100s]
>> Booting OKAY [ 0.531s]
>> Finished. Total time: 2.944s
And finally, trying to push an update image over fastboot:
PHP:
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot update image-marlin-qp1a.191005.007.a3.zip
--------------------------------------------
Bootloader Version...: N/A
Baseband Version.....: N/A
Serial Number........: HT6AD0202367
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.044s]
Checking 'version-bootloader' FAILED
Device version-bootloader is 'N/A'.
Update requires '8996-012001-1908071822'.
fastboot: error: requirements not met!
I am wondering if locking the bootloader would give this thing what it wants and let me boot into recovery, but I have a terrible feeling it would just further lock me out of saving this phone. Does anyone have any insight? Is this a shot motherboard? Sorry, I know my problem has a ton of commonalities with a lot of other people's but it seems for all my searching, reading and Googling that it's idiosyncratic to the point of every solution not working for me. Thank you so much.
Edit: For interest, I just saw the screen throw up an odd block of static, for lack of a better term. In the bottom right corner, it took up a little more than 1/4 of the screen. It looked lik there was cut off text at the top, too little showing to read. It disappeared before I could take a picture with a spare phone. It lasted maybe 5 seconds and then it was gone. It's on USB charge, not sitting on fastboot right now.
Click to expand...
Click to collapse
First, do not repeat do not lock your boot loader.
Second, try this:
- Make sure you have the latest SDK Platform-tools installed on your computer r29.0.5.
There is a link for it in the guide below (Prerequisites c.).
- Make sure you plug the USB into a non charging USB port.
- Extract the boot.img (#6 in the guide brlow) from the Factory image you are currently using and flash it:
fastboot flash boot --slot all boot.img
or
fastboot flash boot boot.img --slot all
Guide
Homeboy76 said:
First, do not repeat do not lock your boot loader.
Second, try this:
- Make sure you have the latest SDK Platform-tools installed on your computer r29.0.5.
There is a link for it in the guide below (Prerequisites c.).
- Make sure you plug the USB into a non charging USB port.
- Extract the boot.img (#6 in the guide brlow) from the Factory image you are currently using and flash it:
fastboot flash boot --slot all boot.img
or
fastboot flash boot boot.img --slot all
Guide
Click to expand...
Click to collapse
Thank you thank you thank you for lending a hand. And for confirming that my temptation to lock the bootloader is a bad idea.
I have three ports on my laptop, I'm not sure any are non-charging. I'm selecting one that it wasn't attached to when the file transfer apparently went wrong.
Here goes nothing. I updated SDK tools last night during all this to be sure everything was kosher.
Unfortunately this was my result from all USB ports, testing both formats of the command:
PHP:
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot boot.img --slot all
Sending 'boot_a' (30969 KB) OKAY [ 0.846s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot boot.img --slot all
Sending 'boot_a' (30969 KB) OKAY [ 0.873s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot --slot all boot.img
Sending 'boot_a' (30969 KB) OKAY [ 0.936s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot --slot all boot.img
Sending 'boot_a' (30969 KB) OKAY [ 0.864s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot boot.img --slot all
Sending 'boot_a' (30969 KB) OKAY [ 0.827s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot boot.img --slot all
Sending 'boot_a' (30969 KB) OKAY [ 0.821s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot --slot all boot.img
Sending 'boot_a' (30969 KB) FAILED (Write to device failed in SendBuffer() (Too many links))
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot boot.img --slot all
Sending 'boot_a' (30969 KB) OKAY [ 0.939s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3>
ekjean said:
Thank you thank you thank you for lending a hand. And for confirming that my temptation to lock the bootloader is a bad idea.
I have three ports on my laptop, I'm not sure any are non-charging. I'm selecting one that it wasn't attached to when the file transfer apparently went wrong.
Here goes nothing. I updated SDK tools last night during all this to be sure everything was kosher.
Unfortunately this was my result from all USB ports, testing both formats of the command:
PHP:
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot boot.img --slot all
Sending 'boot_a' (30969 KB) OKAY [ 0.846s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot boot.img --slot all
Sending 'boot_a' (30969 KB) OKAY [ 0.873s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot --slot all boot.img
Sending 'boot_a' (30969 KB) OKAY [ 0.936s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot --slot all boot.img
Sending 'boot_a' (30969 KB) OKAY [ 0.864s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot boot.img --slot all
Sending 'boot_a' (30969 KB) OKAY [ 0.827s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot boot.img --slot all
Sending 'boot_a' (30969 KB) OKAY [ 0.821s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot --slot all boot.img
Sending 'boot_a' (30969 KB) FAILED (Write to device failed in SendBuffer() (Too many links))
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot boot.img --slot all
Sending 'boot_a' (30969 KB) OKAY [ 0.939s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3>
Click to expand...
Click to collapse
Are you using SDK Platform-tools r29.0.5?
Why? When you extract it it creates a Platform-tools folder.
Put this folder in PS C:\ so you have a
PS C:\Platform-tools folder.
Not: PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3>
That folder set up may be causing the to many links
error.
Then put the boot.img in the Platform-tools folder and do #6 in the guide.
Homeboy76 said:
Are you using SDK Platform-tools r29.0.5?
Why? When you extract it it creates a Platform-tools folder.
Put this folder in PS C:\ so you have a
PS C:\Platform-tools folder.
Not: PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3>
That folder set up may be causing the to many links
error.
Then put the boot.img in the Platform-tools folder and do #6 in the guide.
Click to expand...
Click to collapse
I was still working from the soft-bricked guide, where I had a copy of fastboot/platform tools pasted to everthing else. Not a problem at all to move Platform tools to C:/ Thank you!
I have noticed that what I have is r29.0.6. Should I roll it back? Assuming I should have the newest, I get the same result...
PHP:
PS C:\platform-tools> fastboot flash boot --slot all boot.img
Sending 'boot_a' (30969 KB) OKAY [ 1.729s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\platform-tools> fastboot flash boot boot.img --slot all
Sending 'boot_a' (30969 KB) OKAY [ 0.788s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\platform-tools>
ekjean said:
I was still working from the soft-bricked guide, where I had a copy of fastboot/platform tools pasted to everthing else. Not a problem at all to move Platform tools to C:/ Thank you!
I have noticed that what I have is r29.0.6. Should I roll it back? Assuming I should have the newest, I get the same result...
PHP:
PS C:\platform-tools> fastboot flash boot --slot all boot.img
Sending 'boot_a' (30969 KB) OKAY [ 1.729s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\platform-tools> fastboot flash boot boot.img --slot all
Sending 'boot_a' (30969 KB) OKAY [ 0.788s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\platform-tools>
Click to expand...
Click to collapse
No, do not roll back you have the latest version.
At this point I really don't know what will fix the problem but here are three long shots that might help/work:
1. Try fastboot flash boot boot.img. If that works. Do fastboot flash boot boot.img --slot other.
2. Download the latest Pixel or Pixel XL OTA image (which ever phone you have) and sideload it.
3. Do a Factory Reset. Settings => System => Advanced => Reset options => Erase all data (factory reset)
Good luck.
If none of them work, it could be a hardwear problem. Pixel/Pixel XL are failing because of age or manufacturing. I don't know which.
Homeboy76 said:
No, do not roll back you have the latest version.
At this point I really don't know what will fix the problem but hear are three long shots that might help/work:
1. Try fastboot flash boot boot.img. If that works. Do fastboot flash boot boot.img --slot other.
2. Download the latest Pixel or Pixel XL OTA image (which ever phone you have) and sideload it.
3. Do a Factory Reset. Settings => System => Advanced => Reset options => Erase all data (factory reset)
Good luck.
If none of them work, it could be a hardwear problem. Pixel/Pixel XL are failing because of age or manufacturing. I don't know which.
Click to expand...
Click to collapse
Sadly, anything that requires ADB/recovery is cut off to me, and so is anything that requires the actual OS interface, so accessing settings and factory resetting is out, and so is sideloading. All I can work from is fastboot.
The final option you had gave me another write failure. Thank you for working with me on this - this is my favorite phone I've ever had, and it may be time to eulogize it. I appreciate all you ran me through. <3
ekjean said:
Sadly, anything that requires ADB/recovery is cut off to me, and so is anything that requires the actual OS interface, so accessing settings and factory resetting is out, and so is sideloading. All I can work from is fastboot.
The final option you had gave me another write failure. Thank you for working with me on this - this is my favorite phone I've ever had, and it may be time to eulogize it. I appreciate all you ran me through. <3
Click to expand...
Click to collapse
RIP Pixel/Pixel XL!
hey bruh, try to cooling it in the freezer, my pixel xl turned on that way, give it a shot
@mateodiaz802 said:
hey bruh, try to cooling it in the freezer, my pixel xl turned on that way, give it a shot
Click to expand...
Click to collapse
Maybe I will! Did it stay on?
it will stay on the enough time to recover your data
@mateodiaz802 said:
hey bruh, try to cooling it in the freezer, my pixel xl turned on that way, give it a shot
Click to expand...
Click to collapse
I'm afraid in my case this was the death blow. Let out a few buzzes when attempting to power into fastboot, flashed a red light at the top and then nothing. She was euthanized by freezer around 5PM, 3/2/20, went quietly into that good night surrounded by friends and family at home. RIP Pixel.
did you cover the phone holes like the charging port and aux jack? I forgot to mention because I thought it was obvious
@mateodiaz802 said:
did you cover the phone holes like the charging port and aux jack? I forgot to mention because I thought it was obvious
Click to expand...
Click to collapse
I wrapped 'er in plastic wrap before putting it in. So it would've been covered. Oh well, stuff happens. Funny thing, I tried it again just to see. It started vibrating and hasn't stopped. XD
i covered the holes with tape, it's more effective, also you should try booting it with "start" optino from the bootloader
SOLVED I will make a topic about it https://forum.xda-developers.com/g5/help/how-to-revert-moto-g5-xt1670-to-stock-t4183425
Hello, how are you all over there? I here in trouble with this XT1670. I have installed several roms but now i want to go back to the official one, but it dont lock the bootloader.
Tried the following command (twice) to lock the bootloader: fastboot oem lock
And i get the following result:
Code:
(bootloader) Flash valid Android images now
(bootloader) Then re-run this command to lock
OKAY [ 0.016s]
finished. total time: 0.016s
Now i use the following command: fastboot flash boot boot.img
And the following was obtained:
Code:
target reported max download size of 535822336 bytes
sending 'boot' (16384 KB) ...
OKAY [0.545s]
writing 'boot' ...
(bootloader) Security version downgrade
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.747s
I have already tried several. Boot, gpt, oem with official rom. All showing the error "Security version downgrade"
I also tried Lenovo's Rescue & Smart app, but it says the SKU is wrong and doesn't recognize the mobile phone.
I don't know how to continue. I could put an official rom, but when you restart the phone the bootloader appears. It only starts when press start.
Not only does that happen. Every so often, the phone turns itself off and remains in the bootloader. And then when you start up, bug reports pop up to share with who knows what.
I do not know what to do. You are the experts.
Ty in advance
Greetings,
I've appreciated @abhinavgupta371, @HELLBOY017 for initial version of this firmware and @penguinus for continuous support and testing.
PLEASE NOTE THAT FASTBOOT ROMS CAN ONLY BE USED IN DEVICES WITH AN UNLOCKED BOOTLOADER!!!
AND BE WARNED THAT UNLOCKING DEVICE WILL WIPE INTERNAL STORAGE COMPLETELY.
THIS ROM UNOFFICIAL AND BASED ON IMAGES MANUALLY EXTRACTED FROM MT2111 DEVICES AND OTA UPDATES
This ROM can be used on MT2110 devices (Chinese version initially delivered with ColorOS) for migration to OxygenOS
Device bootloader can be locked after flashing this ROM
Attention: this ROM only for the migration from COS Android 11 to OOS Android 11. Do not try to use it for switching to/from other version of Android. This can lead to the boot loop.
You can find ROMs maintained by @penguinus which are more universal than these and allow to switch between Android versions.
Everything related to SafetyNet checks is working on this ROM like on original MT2111 devices.
If device is not rooted it can receive OTA updates.
Known issues:
- Device name in settings displayed incorrectly "Lahaina for amd64" instead of expected "MT2111". Fixed in latest firmwares.
Migration instructions:
- On your PC, install bootloader drivers for OP9RT and check if device is recognized in Bootloader and Fastbootd modes.
- Ensure you're using the LATEST version of SDK platform tools (adb and fastboot)
- On your PC, download the Fastboot ROM zip from the download link below.
- On your PC, unzip downloaded file
- On your PC, navigate to its now-uncompressed folder
- Reboot your OnePlus 9 RT to bootloader mode.
- Connect the OP9RT to your PC
- On your PC open command line window in the uncompressed folder,
- type install.bat
- wait till device boot to "Setup wizard" screen (it will take 5-7 min)
- at this point device bootloader can be locked if you need this.
Upgrade instruction (for devices with OxygenOS where standard updater decline update):
- follow the installation procedure till
- instead of install.bat you need to run upgrade.bat in command line window
- user data will be preserved
Good luck!
Edit:
Some linux users reports issue with device wipe during installation. It is related to fastboot dependencies. It requires android platform tools installed.
As an alternative after final reboot (device should reboot automatically twice during installation) device will boot to recovery mode where you need to wipe it manually.
DOWNLOAD LINKS:
Fastboot ROM OxygenOS A.11 zip:
4.3 GB file on MEGA
mega.nz
boot.img OxygenOS A.11 https://mega.nz/file/RVAXCJya#SXukMoZbmWqScbSuE3iVtTEYYkYlOt8eajfV8xCIOdI
Fastboot ROM OxygenOS A.08 zip:
https://mega.nz/file/LYFElKaL#9-gO2xVEenHufecxaDSTRTUuCuJY-QlxIRRbSUtHfo8boot.img OxygenOS A.08 https://mega.nz/file/kJQyCCTS#VHy7tzjPEhDlrtZm1v1AB-lmEN4ckx5dUVlnX0YZ0gs
Fastboot ROM OxygenOS A.07 zip:
https://mega.nz/file/4JZ2XRiT#7fIk6nL0V9zkr02CcGL9tgxiVJPfJpYN1S8jA-DAxE8boot.img OxygenOS A.07 https://mega.nz/file/dZpHiAYI#eEuNHhz7nO0dCqFJrl3kK57s2PAnwr7zfa2UvBecgAE
Fastboot ROM OxygenOS A.06 zip:
https://mega.nz/file/QZQQUZqZ#3PntyL67g71AneyGKjPD5UH-gVyTxHk21MkLoTxojpA
Fastboot ROM OxygenOS A.05 zip:
https://mega.nz/file/MBgg2AjJ#98vdiFZPUCMm9gskDu5SQmic-D8jHZ3snO8pLbqrbFY
Fastboot ROM OxygenOS A.04 zip:
https://mega.nz/file/oFhjDKrI#jUajmG5fAeH1TvYS3b6EZB6Pwj5MzDpAt47fwr6gurMhttps://disk.yandex.ru/d/U8WxNFOFU4rDfA
Credits:
- @abhinavgupta371
- @HELLBOY017
- @penguinus
Updates:
[2022-02-22] fixed installation and upgrade for some specific device state (if you have installed previous version successfully, you doesn't need re-installation).
[2022-03-01] add A.05 version of firmware.
[2022-03-11] add A.06 version of firmware.
[2022-03-20] add A.07 version of firmware.
[2022-05-23] add A.08 version of firmware.
[2022-06-06] update A.08 version of firmware (fixed issue with telegram by @penguinus).
[2022-07-20] add A.11 version of firmware (prepared by @penguinus)
[2022-10-12] add attention message about downgrading.
Thank you for this. I'm running this on my MT2110 (albeit the A03 version).
Can this be dirty flashed over the top of the original install, or will it wipe all my settings/apps?
bonez56 said:
Thank you for this. I'm running this on my MT2110 (albeit the A03 version).
Can this be dirty flashed over the top of the original install, or will it wipe all my settings/apps?
Click to expand...
Click to collapse
It has an option to upgrade without wipe.
Please read instructions more carefully (last part of instruction about upgrade from previous version)
Thanks for posting this.
bonez56 said:
Cảm ơn vì điều này. Tôi đang chạy cái này trên MT2110 của mình (mặc dù là phiên bản A03).
Điều này có thể bị bẩn được hiển thị trên đầu cài đặt gốc hay nó sẽ xóa tất cả các cài đặt / ứng dụng của tôi?
Click to expand...
Click to collapse
Choose update.bat to update and all your data is kept intact
Thank you so much, really appreciate it
Valdem said:
Greetings,
I've appreciated @abhinavgupta371, @HELLBOY017 for initial version of this firmware and @penguinus for continuous support and testing.
PLEASE NOTE THAT FASTBOOT ROMS CAN ONLY BE USED IN DEVICES WITH AN UNLOCKED BOOTLOADER!!!
AND BE WARNED THAT UNLOCKING DEVICE WILL WIPE INTERNAL STORAGE COMPLETELY.
THIS ROM UNOFFICIAL AND BASED ON IMAGES MANUALLY EXTRACTED FROM MT2111 DEVICES AND OTA UPDATES
This ROM can be used on MT2110 devices (Chinese version initially delivered with ColorOS) for migration to OxygenOS
Device bootloader can be locked after flashing this ROM
Everything related to SafetyNet checks is working on this ROM like on original MT2111 devices.
If device is not rooted it can receive OTA updates.
Known issues:
- Device name in settings displayed incorrectly "Lahaina for amd64" instead of expected "MT2111".
Migration instructions:
- On your PC, install bootloader drivers for OP9RT and check if device is recognized in Bootloader and Fastbootd modes.
- Ensure you're using the LATEST version of SDK platform tools (adb and fastboot)
- On your PC, download the Fastboot ROM zip from the download link below.
- On your PC, unzip downloaded file
- On your PC, navigate to its now-uncompressed folder
- Reboot your OnePlus 9 RT to bootloader mode.
- Connect the OP9RT to your PC
- On your PC open command line window in the uncompressed folder,
- type install.bat
- wait till device boot to "Setup wizard" screen (it will take 5-7 min)
- at this point device bootloader can be locked if you need this.
Upgrade instruction (for devices with OxygenOS where standard updater decline update):
- follow the installation procedure till
- instead of install.bat you need to run upgrade.bat in command line window
- user data will be preserved
Good luck!
Edit:
Some linux users reports issue with device wipe during installation. It is related to fastboot dependencies. It requires android platform tools installed.
As an alternative after final reboot (device should reboot automatically twice during installation) device will boot to recovery mode where you need to wipe it manually.
DOWNLOAD LINKS:
Fastboot ROM OxygenOS A.04 zip:
File on MEGA
mega.nz
Яндекс
Найдётся всё
disk.yandex.ru
Credits:
- @abhinavgupta371
- @HELLBOY017
- @penguinus
Click to expand...
Click to collapse
Thank you for the good work ! I install it successfully using the upgrade.bat and able to relock the bootloader ! If OnePlus release its official rom in the future, would it be possible for me to upgrade to those rom ?
borg79 said:
Thank you for the good work ! I install it successfully using the upgrade.bat and able to relock the bootloader ! If OnePlus release its official rom in the future, would it be possible for me to upgrade to those rom ?
Click to expand...
Click to collapse
If you talk about next OTA - then answer is YES, because you lock bootloader.
The main requirement for OTA - unmodified data on device system's partitions.
If you talk about official MSMDownload Tools. Then nothing can stop you to flash it. It is low level firmware, which can restore almost everything.
I own the chinese version with 8/256 GB. Will this rom work? I know, its the only version, thats not coming to india, but i would like to install this rom for better use.. Thanks for answering
Solved
deleted
miky03 said:
I have the mt2110 model comming from colorOs v12
i can boot to fastmode what should I do please help
Click to expand...
Click to collapse
Try to flash again. By log it looks like your phone didn't rebooted to fastbootd correctly when install script tried to do that.
miky03 said:
hi i did like you write unfortunly i get the
QUALCOMM CrashDump Mode:
dm-verity device corrupted verity_ctr
I have the mt2110 model comming from colorOs v12
i can boot to fastmode what should I do please help
D:\op9rt-oos-A04-fastboot-rom>install.bat
###################
# Formatting data #
###################
F2FS-tools: mkfs.f2fs Ver: 1.14.0 (2020-08-24)
Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 470920600 (229941 MB)
Info: zone aligned segment0 blkaddr: 512
Info: add quota type = 0 => 4
Info: add quota type = 1 => 5
[f2fs_init_sit_area: 634] Filling sit area at offset 0x00600000
[f2fs_init_nat_area: 668] Filling nat area at offset 0x01a00000
[f2fs_write_root_inode:1281] Writing root inode (hot node), 2b800 0 200 at offset 0x00178176
[f2fs_write_default_quota:1357] Writing quota data, at offset 0002be01, 0002be02
[f2fs_write_qf_inode:1416] Writing quota inode (hot node), 2b800 0 200 at offset 0x00178177
[f2fs_write_default_quota:1357] Writing quota data, at offset 0002be03, 0002be04
[f2fs_write_qf_inode:1416] Writing quota inode (hot node), 2b800 0 200 at offset 0x00178178
[f2fs_update_nat_root:1470] Writing nat root, at offset 0x00001a00
[f2fs_add_default_dentry_root:1667] Writing default dentry root, at offset 0x0002be00
Info: Overprovision ratio = 0.420%
Info: Overprovision segments = 963 (GC reserved = 484)
[f2fs_write_check_point_pack: 827] Writing main segments, cp at offset 0x00000200
[f2fs_write_check_point_pack: 982] Writing Segment summary for HOT/WARM/COLD_DATA, at offset 0x00000201
[f2fs_write_check_point_pack:1009] Writing Segment summary for HOT_NODE, at offset 0x00000202
[f2fs_write_check_point_pack:1021] Writing Segment summary for WARM_NODE, at offset 0x00000203
[f2fs_write_check_point_pack:1032] Writing Segment summary for COLD_NODE, at offset 0x00000204
[f2fs_write_check_point_pack:1040] Writing cp page2, at offset 0x00000205
[f2fs_write_check_point_pack:1060] Writing NAT bits pages, at offset 0x000003fe
[f2fs_write_check_point_pack:1081] Writing cp page 1 of checkpoint pack 2, at offset 0x00000400
[f2fs_write_check_point_pack:1100] Writing cp page 2 of checkpoint pack 2, at offset 0x00000405
[f2fs_write_super_block:1133] Writing super block, at offset 0x00000000
Info: format successful
Sending 'userdata' (85 KB) OKAY [ 0.004s]
Writing 'userdata' OKAY [ 0.012s]
Finished. Total time: 1.630s
mke2fs 1.46.2 (28-Feb-2021)
Creating filesystem with 4096 4k blocks and 4096 inodes
Allocating group tables: done
Writing inode tables: done
Creating journal (1024 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'metadata' (44 KB) OKAY [ 2.541s]
Writing 'metadata' OKAY [ 0.886s]
Finished. Total time: 5.592s
#######################################################################
# Oxygen OS Flasher For OnePlus 9RT by abhinavgupta371 and HELLBOY017 #
# updated by Va1d3m #
#######################################################################
#################################
# Flashing firmware into slot A #
#################################
Setting current slot to 'a' OKAY [ 0.008s]
Finished. Total time: 0.013s
#################################
# Flashing bootloader img's #
#################################
Sending 'boot_a' (196608 KB) OKAY [ 5.309s]
Writing 'boot_a' OKAY [ 0.384s]
Sending 'boot_b' (196608 KB) OKAY [ 4.253s]
Writing 'boot_b' OKAY [ 0.381s]
Finished. Total time: 10.370s
Sending 'modem_a' (190060 KB) OKAY [ 5.191s]
Writing 'modem_a' OKAY [ 0.376s]
Sending 'modem_b' (190060 KB) OKAY [ 4.143s]
Writing 'modem_b' OKAY [ 0.435s]
Finished. Total time: 10.186s
Sending 'vendor_boot' (196608 KB) OKAY [ 5.316s]
Writing 'vendor_boot' OKAY [ 0.430s]
Finished. Total time: 5.767s
Sending 'vbmeta' (8 KB) OKAY [ 0.001s]
Writing 'vbmeta' OKAY [ 0.002s]
Finished. Total time: 0.018s
Sending 'vbmeta_system' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_system' OKAY [ 0.002s]
Finished. Total time: 0.018s
Sending 'vbmeta_vendor' (4 KB) OKAY [ 0.002s]
Writing 'vbmeta_vendor' OKAY [ 0.001s]
Finished. Total time: 0.018s
##########################
# Rebooting to fastbootd #
##########################
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
#################################
# Flashing fastbootd img's #
#################################
fastboot: error: Could not check if partition abl has slot all
fastboot: error: Could not check if partition aop has slot all
fastboot: error: Could not check if partition bluetooth has slot all
fastboot: error: Could not check if partition cpucp has slot all
fastboot: error: Could not check if partition devcfg has slot all
fastboot: error: Could not check if partition dsp has slot all
fastboot: error: Could not check if partition dtbo has slot all
fastboot: error: Could not check if partition engineering_cdt has slot all
fastboot: error: Could not check if partition featenabler has slot all
fastboot: error: Could not check if partition hyp has slot all
fastboot: error: Could not check if partition imagefv has slot all
fastboot: error: Could not check if partition keymaster has slot all
fastboot: error: Could not check if partition mdtp has slot all
fastboot: error: Could not check if partition mdtpsecapp has slot all
fastboot: error: Could not check if partition multiimgoem has slot all
fastboot: error: Could not check if partition oplus_sec has slot all
fastboot: error: Could not check if partition oplusstanvbk has slot all
fastboot: error: Could not check if partition qupfw has slot all
fastboot: error: Could not check if partition qweslicstore has slot all
fastboot: error: Could not check if partition shrm has slot all
fastboot: error: Could not check if partition splash has slot all
fastboot: error: Could not check if partition tz has slot all
fastboot: error: Could not check if partition uefisecapp has slot all
fastboot: error: Could not check if partition vm-bootsys has slot all
fastboot: error: Could not check if partition xbl has slot all
fastboot: error: Could not check if partition xbl_config has slot all
###############################
# Resizing logical partitions #
###############################
Deleting 'odm_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'odm_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'system_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'system_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'system_ext_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'system_ext_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'product_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'product_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'vendor_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'vendor_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'my_carrier_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'my_carrier_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'my_company_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'my_company_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'my_engineering_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'my_engineering_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'my_heytap_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'my_heytap_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'my_manifest_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'my_manifest_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'my_preload_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'my_preload_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'my_product_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'my_product_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'my_region_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'my_region_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'my_stock_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'my_stock_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'odm_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'odm_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'system_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'system_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'system_ext_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'system_ext_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'product_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'product_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'vendor_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'vendor_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'my_carrier_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'my_carrier_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'my_company_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'my_company_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'my_engineering_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'my_engineering_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'my_heytap_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'my_heytap_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'my_manifest_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'my_manifest_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'my_preload_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'my_preload_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'my_product_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'my_product_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'my_region_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'my_region_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'my_stock_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'my_stock_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
###############################
# Flashing logical partitions #
###############################
Sending 'vendor' (621044 KB) OKAY [ 18.220s]
Writing 'vendor' FAILED (remote: '(vendor_a) No such partition')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'odm' 1/2 (786428 KB) OKAY [ 17.645s]
Writing 'odm' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Sending 'system' (760184 KB) OKAY [ 23.335s]
Writing 'system' FAILED (remote: '(system_a) No such partition')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'system_ext' 1/2 (786428 KB) OKAY [ 18.302s]
Writing 'system_ext' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Sending 'product' (71056 KB) OKAY [ 1.946s]
Writing 'product' FAILED (remote: '(product_a) No such partition')
fastboot: error: Command failed
Sending 'my_carrier' (340 KB) OKAY [ 0.010s]
Writing 'my_carrier' FAILED (remote: '(my_carrier_a) No such partition')
fastboot: error: Command failed
Sending 'my_company' (340 KB) OKAY [ 0.009s]
Writing 'my_company' FAILED (remote: '(my_company_a) No such partition')
fastboot: error: Command failed
Sending 'my_engineering' (340 KB) OKAY [ 0.009s]
Writing 'my_engineering' FAILED (remote: '(my_engineering_a) No such partition')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'my_heytap' 1/2 (786368 KB) OKAY [ 17.396s]
Writing 'my_heytap' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Sending 'my_manifest' (720 KB) OKAY [ 0.019s]
Writing 'my_manifest' FAILED (remote: '(my_manifest_a) No such partition')
fastboot: error: Command failed
Sending 'my_preload' (3520 KB) OKAY [ 0.097s]
Writing 'my_preload' FAILED (remote: '(my_preload_a) No such partition')
fastboot: error: Command failed
Sending 'my_product' (267700 KB) OKAY [ 7.769s]
Writing 'my_product' FAILED (remote: '(my_product_a) No such partition')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'my_region' 1/2 (781680 KB) OKAY [ 17.330s]
Writing 'my_region' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'my_stock' 1/2 (750628 KB) OKAY [ 16.707s]
Writing 'my_stock' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
#######################
# Rebooting to system #
#######################
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.003s
Press any key to continue . . .View attachment 5543893View attachment 5543895
Click to expand...
Click to collapse
From the log it seems that device was reconnected at the middle of installation or device can't correctly boot into fastbootd mode (need more investigation why). You can restart install.bat one more time from the bootloader state (like on second attached picture).
Valdem said:
From the log it seems that device was reconnected at the middle of installation or device can't correctly boot into fastbootd mode (need more investigation why). You can restart install.bat one more time from the bootloader state (like on second attached picture).
Click to expand...
Click to collapse
Thanks for fast response,
I tried already 2 times all the same.
As you mentioned after automatic reboot in the script im ending up in recovery mode.
miky03 said:
Thanks for fast response,
I tried already 2 times all the same.
As you mentioned after automatic reboot in the script im ending up in recovery mode.
Click to expand...
Click to collapse
it is ok. fastbootd mode looks like recovery. but script should not fail with message 'fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.'
Where is bootloader drivers for OP9RT？
miky03 said:
Thanks for fast response,
I tried already 2 times all the same.
As you mentioned after automatic reboot in the script im ending up in recovery mode.
Click to expand...
Click to collapse
It's weird.
You can check manually if device reboots into fastbootd properly.
Just do next steps and report here about output.
1. Open command line in folder with firmware.
2. Boot device in bootloader mode
3. run next commands to boot into fastbootd mode
Code:
fastboot reboot fastboot
4. device should reboot into fastbootd mode it looks like recovery mode.
5. after reboot run
Code:
fastboot devices
5. it should print serial number of device
if no serial number is printed - there is issue with fastboot binary.
Update: It looks like you have some issue with drivers.
miky03 said:
Thanks for fast response,
I tried already 2 times all the same.
As you mentioned after automatic reboot in the script im ending up in recovery mode.
Click to expand...
Click to collapse
Have you put your Window OS into "testsigning" mode before executing the batch file ?
Valdem said:
It's weird.
You can check manually if device reboots into fastbootd properly.
Just do next steps and report here about output.
1. Open command line in folder with firmware.
2. Boot device in bootloader mode
3. run next commands to boot into fastbootd mode
Code:
fastboot reboot fastboot
4. device should reboot into fastbootd mode it looks like recovery mode.
5. after reboot run
Code:
fastboot devices
5. it should print serial number of device
if no serial number is printed - there is issue with fastboot binary.
Update: It looks like you have some issue with drivers.
Click to expand...
Click to collapse
Hi i did until 3. Then reboot to this menu in cmd waiting for any device
borg79 said:
Have you put your Window OS into "testsigning" mode before executing the batch file ?
Click to expand...
Click to collapse
Hi im running on win 7 64bit.what is testing mode?