Related
The other day I was just on my phone and restarted it. When I tried to power up the phone again it said "Warning Unlocked Bootloader" just like it does every time, but now it won't go past that screen. I have tried everything I can think of and this is still happening. Is there anything I can do to fix this?!?!
What is everything you can think of? Did you try wiping both cache's
Sent from my PACMAN MATRIX HD MAXX
deeje00 said:
What is everything you can think of? Did you try wiping both cache's
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
Well the only thing I can even to on it is go into fastboot mode. I've tried all the commands in the boot menu and nothing. I tried to use RSD Lite to go back to stock 4.1.1 but that wouldn't work either. I can't think of anything other than that.
MetalKiderific said:
Well the only thing I can even to on it is go into fastboot mode. I've tried all the commands in the boot menu and nothing. I tried to use RSD Lite to go back to stock 4.1.1 but that wouldn't work either. I can't think of anything other than that.
Click to expand...
Click to collapse
Do a full format of /data. You'll lose all internal sd data, but you'll be booting.
Boot into fastboot
Use the fastboot executable linked in the guide stickied in general
fastboot format cache
fastboot format userdata
My guess is you changed from 4.3/4.2 rom to a 4.1 rom or vice a versa.
skeevydude said:
Do a full format of /data. You'll lose all internal sd data, but you'll be booting.
Boot into fastboot
Use the fastboot executable linked in the guide stickied in general
fastboot format cache
fastboot format userdata
My guess is you changed from 4.3/4.2 rom to a 4.1 rom or vice a versa.
Click to expand...
Click to collapse
thats not what i did, but I tried your method. When i typed in any fastboot commands it comes back at me saying
"(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
error: cannot load 'boot.img' : No error"
MetalKiderific said:
thats not what i did, but I tried your method. When i typed in any fastboot commands it comes back at me saying
"(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
error: cannot load 'boot.img' : No error"
Click to expand...
Click to collapse
Download a stock fastboot and extract it
Copy the guides linked fastboot executable into the extracted location and rename it moto-fastboot
Open a command prompt/terminal in the extracted location
Do all of these commands in order exactly as written.
Use ./moto-fastboot on linux
The first line in bold can't be overwritten with an older version, so if you've flashed Mex Retail with fastboot or RSD you'll only be able to use gpt_main0.bin from Mex Retail.
Code:
[B]fastboot flash partition gpt_main0.bin[/B]
moto-fastboot flash sbl1 sbl1.mbn
moto-fastboot flash sbl2 sbl2.mbn
moto-fastboot flash sbl3 sbl3.mbn
moto-fastboot flash rpm rpm.mbn
moto-fastboot flash tz tz.mbn
moto-fastboot flash aboot emmc_appsboot.mbn
moto-fastboot flash modem NON-HLOS.bin
moto-fastboot flash fsg fsg.mbn
moto-fastboot erase modemst1
moto-fastboot erase modemst2
moto-fastboot flash logo logo.bin
moto-fastboot flash boot boot.img
moto-fastboot flash devtree device_tree.bin
moto-fastboot flash cdrom cdrom
moto-fastboot erase tombstones
moto-fastboot erase cache
moto-fastboot erase userdata
This is exactly what I do whenever I brick myself.
If you actually like the unlocked bootloader warning, skip flashing logo.bin
You could possibly use the Myth tool if you're using Windows. You should also read skeevydude's post in the Atrix HD General section, the Unlocked bootloader, what now... and the Beginner's guide. That should have a lot of the resources you'll need to fix the issue. If you can boot into fastboot, you shouldn't panic.
Thanks, I will try that
Did that work for you? I'm having the same issue.
Hi guys, I think I really messed up my new Moto X: and when I say new I mean I bought it yesterday even if used and bricked today.
I had a 4.4 Sprint firmware and I followed the guide to unlock the device (which it seemed to work), since I need it in Europe with a Vodafone sim. After that I decided to get a UK firmware, so I flashed the phone with RSD Lite, but the flash failed and now in boot mode I have the following message: Partition (boot) Security Version Downgraded - Fasboot reason: boot failure. If you have the solution can you explain it step by step, I'm not actually good with this kind of things. Do you think I have to toss the device in the trash bin? Thank you
Jack881 said:
Hi guys, I think I really messed up my new Moto X: and when I say new I mean I bought it yesterday even if used and bricked today.
I had a 4.4 Sprint firmware and I followed the guide to unlock the device (which it seemed to work), since I need it in Europe with a Vodafone sim. After that I decided to get a UK firmware, so I flashed the phone with RSD Lite, but the flash failed and now in boot mode I have the following message: Partition (boot) Security Version Downgraded - Fasboot reason: boot failure. If you have the solution can you explain it step by step, I'm not actually good with this kind of things. Do you think I have to toss the device in the trash bin? Thank you
Click to expand...
Click to collapse
I just want to add that I've altready tried to flash back to the original version, but how you can imagine...nothing to do...
Jack881 said:
I just want to add that I've altready tried to flash back to the original version, but how you can imagine...nothing to do...
Click to expand...
Click to collapse
You shouldn't have attempted to downgrade and/or flash another carriers rom. It's documented many places not to do this. Now you are in a pickle.
This will probably fix you up:
Download the FULL SBF of the ROM you want to flash. It must be the SAME VERSION, or HIGHER than the newest version you have flashed.
Boot into bootloader.
Type:
fastboot flash bootloader motoboot.img
fastboot flash partition gpt.bin
fastboot reboot-bootloader
Now you SHOULD be able to flash the ENTIRE SBF with RSD Lite or Manual method.
Explaination: By doing this, we are JUST flashing the bootloader and partition table (gpt.bin), THEN we reboot back to the bootloader in order to allow the bootloader to LOAD the new partition table before we flash the rest of the partitions.
It fixes people up most of the time, but not all. Good luck, hope it does the trick for you. Next time, heed the warning -- specifically not to downgrade. :good:
samwathegreat said:
You shouldn't have attempted to downgrade and/or flash another carriers rom. It's documented many places not to do this. Now you are in a pickle.
This will probably fix you up:
Download the FULL SBF of the ROM you want to flash. It must be the SAME VERSION, or HIGHER than the newest version you have flashed.
Boot into bootloader.
Type:
fastboot flash bootloader motoboot.img
fastboot flash partition gpt.bin
fastboot reboot-bootloader
Now you SHOULD be able to flash the ENTIRE SBF with RSD Lite or Manual method.
Explaination: By doing this, we are JUST flashing the bootloader and partition table (gpt.bin), THEN we reboot back to the bootloader in order to allow the bootloader to LOAD the new partition table before we flash the rest of the partitions.
It fixes people up most of the time, but not all. Good luck, hope it does the trick for you. Next time, heed the warning -- specifically not to downgrade. :good:
Click to expand...
Click to collapse
You are very kind, but I don't know if I can do it. I downloaded the firmware. But wheere I have to type the command? Sorry I'm really ignorant...
Jack881 said:
You are very kind, but I don't know if I can do it. I downloaded the firmware. But wheere I have to type the command? Sorry I'm really ignorant...
Click to expand...
Click to collapse
Get the latest android SDK from here: http://developer.android.com/sdk/index.html
Install it. It should have a folder called "Platform-tools" inside. Put gpt.bin and motoboot.img from the firmware inside this folder. Then open a command prompt, go to that folder, then run the commands as I outlined in the previous post.
After you "fastboot reboot-bootloader", try to flash the entire firmware zip file using RSD Lite.
I tried, but when I type the device still write Fastboot reason:flash failure. Any idea? Maybe I did something wrong. Thank you.
samwathegreat said:
You shouldn't have attempted to downgrade and/or flash another carriers rom. It's documented many places not to do this. Now you are in a pickle.
This will probably fix you up:
Download the FULL SBF of the ROM you want to flash. It must be the SAME VERSION, or HIGHER than the newest version you have flashed.
Boot into bootloader.
Type:
fastboot flash bootloader motoboot.img
fastboot flash partition gpt.bin
fastboot reboot-bootloader
Now you SHOULD be able to flash the ENTIRE SBF with RSD Lite or Manual method.
Explaination: By doing this, we are JUST flashing the bootloader and partition table (gpt.bin), THEN we reboot back to the bootloader in order to allow the bootloader to LOAD the new partition table before we flash the rest of the partitions.
It fixes people up most of the time, but not all. Good luck, hope it does the trick for you. Next time, heed the warning -- specifically not to downgrade. :good:
Click to expand...
Click to collapse
This is what it writes when I type the commands:
target reported max download size of 805306368 bytes
sending 'bootloader' (1604 KB)...
OKAY [ 0.346s]
writing 'bootloader'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.454s
C:\Users\Giacomo\Desktop\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>f
astboot flash partition gpt.bin
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'partition' (32 KB)...
OKAY [ 0.261s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.146s
C:\Users\Giacomo\Desktop\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>f
astboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.010s
C:\Users\Giacomo\Desktop\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>
Can you help me? thank you.
Jack881 said:
This is what it writes when I type the commands:
target reported max download size of 805306368 bytes
sending 'bootloader' (1604 KB)...
OKAY [ 0.346s]
writing 'bootloader'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.454s
C:\Users\Giacomo\Desktop\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>f
astboot flash partition gpt.bin
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'partition' (32 KB)...
OKAY [ 0.261s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.146s
C:\Users\Giacomo\Desktop\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>f
astboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.010s
C:\Users\Giacomo\Desktop\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>
Can you help me? thank you.
Click to expand...
Click to collapse
You noted that you flashed multiple ROMS. What is the LATEST VERSION of all the roms you tried to flash. You can never go lower, so please advise. Did you flash --any-- 4.4.2 or 4.4.4 ROM? If so, you MUST flash a new rom of the same or higher version.
samwathegreat said:
You noted that you flashed multiple ROMS. What is the LATEST VERSION of all the roms you tried to flash. You can never go lower, so please advise. Did you flash --any-- 4.4.2 or 4.4.4 ROM? If so, you MUST flash a new rom of the same or higher version.
Click to expand...
Click to collapse
I flashed a UK retail 4.4.2 and after a France retail 4.4.2...what should I flash now? I was trying your system on the Sprint 4.4 which was the original firmware of the telephone...
Jack881 said:
I flashed a UK retail 4.4.2 and after a France retail 4.4.2...what should I flash now? I was trying your system on the Sprint 4.4 which was the original firmware of the telephone...
Click to expand...
Click to collapse
That will absolutely not work. You are attempting to downgrade!!! (4.4.2 > 4.4) I already mentioned that you must use the same version or higher than the highest version you flashed previously. You MUST flash the Sprint 4.4.2 ROM, and not 4.4
If you try again, with the 4.4.2 Sprint SBF, you should be able to successfully recover.
Jack881 said:
I flashed a UK retail 4.4.2 and after a France retail 4.4.2...what should I flash now? I was trying your system on the Sprint 4.4 which was the original firmware of the telephone...
Click to expand...
Click to collapse
I also tried the 4.4.2 Sprint now, but same results. Do I have to get the file from the same firmware I flash, right? and when I flash do I have to flash without the getvar string?
Jack881 said:
I also tried the 4.4.2 Sprint now, but same results. Do I have to get the file from the same firmware I flash, right? and when I flash do I have to flash without the getvar string?
Click to expand...
Click to collapse
Please just use the manual method.
Do this:
First extract all the files in the SBF zip file (the 4.4.2 Sprint one!!!!!) to the same folder that includes fastboot & mfastboot (you do have the "mfastboot" binary, right?)
Now do this exactly: (ignore the fact that some of these commands are being run twice - this is intentional. Also notice that we are using "mfastboot" to flash system.img. If you don't have it, get it here [and put it in the same folder as fastboot]: https://docs.google.com/file/d/0B9qC3vvamytkSVp0NXhlSEhZVFU/edit )
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot reboot-bootloader
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
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
If everything is successful to this point, now do:
fastboot reboot
If something fails, move on with the other commands. If you get stuck, let me know. Pictures of the errors will be helpful if you have any.
Taking timgree
samwathegreat said:
Please just use the manual method.
Do this:
First extract all the files in the SBF zip file (the 4.4.2 Sprint one!!!!!) to the same folder that includes fastboot & mfastboot (you do have the "mfastboot" binary, right?)
Now do this exactly: (ignore the fact that some of these commands are being run twice - this is intentional. Also notice that we are using "mfastboot" to flash system.img. If you don't have it, get it here [and put it in the same folder as fastboot]: https://docs.google.com/file/d/0B9qC3vvamytkSVp0NXhlSEhZVFU/edit )
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot reboot-bootloader
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
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
If everything is successful to this point, now do:
fastboot reboot
If something fails, move on with the other commands. If you get stuck, let me know. Pictures of the errors will be helpful if you have any.
Click to expand...
Click to collapse
First of all I want to thank you, because I've never med anyone so kind online. Unfortunately I didn't succeed. I explain you exactly what I did:
1) I got from here http://sbf.droid-developers.org/phone.php?device=0 the Sprint 4.4.2 firmware (I had 4.4 originally, so this should be fine according to what you said)
2) I unzipped every file inside sdk/platform-tools
3) I downloaded your mfastboot (since I didn't have it) and stick it inside the same folder sdk/platform tools
4) So now I have this folder with inside all the files I thought you were asking to have there
5) at this point I opened from there the command prompt and started to type the commands you suggested
6) I had this:
C:\Users\Giacomo\Desktop\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>f
astboot partition gpt.bin
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, and if found,
recovery, tos
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
C:\Users\Giacomo\Desktop\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>f
astboot flash motoboot motoboot.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'motoboot' (1604 KB)...
OKAY [ 0.344s]
writing 'motoboot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.027s
C:\Users\Giacomo\Desktop\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>
I got stuck at the second command. Any idea? thank you.
Jack881 said:
First of all I want to thank you, because I've never med anyone so kind online. Unfortunately I didn't succeed. I explain you exactly what I did:
1) I got from here http://sbf.droid-developers.org/phone.php?device=0 the Sprint 4.4.2 firmware (I had 4.4 originally, so this should be fine according to what you said)
2) I unzipped every file inside sdk/platform-tools
3) I downloaded your mfastboot (since I didn't have it) and stick it inside the same folder sdk/platform tools
4) So now I have this folder with inside all the files I thought you were asking to have there
5) at this point I opened from there the command prompt and started to type the commands you suggested
6) I had this:
C:\Users\Giacomo\Desktop\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>f
astboot partition gpt.bin
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, and if found,
recovery, tos
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
C:\Users\Giacomo\Desktop\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>f
astboot flash motoboot motoboot.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'motoboot' (1604 KB)...
OKAY [ 0.344s]
writing 'motoboot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.027s
C:\Users\Giacomo\Desktop\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>
I got stuck at the second command. Any idea? thank you.
Click to expand...
Click to collapse
You also didn't correctly issue the first command. You left out "flash"
You typed "fastboot partition gpt.bin"
Instead of "fastboot flash partition gpt.bin"
Please start over. If it fails at motoboot.img -- don't worry. Just continue with the rest of the commands. If we can get everything else to flash, you may well recover. Sometimes it DOES fail at flashing motoboot, but just continue with the commands.
Be sure to type them EXACTLY as I've listed -- you can't leave off "flash" anymore
Please try and update as to status. If you can get to the very end, with nothing but motoboot.img failing, we should be able to recover you.
samwathegreat said:
You also didn't correctly issue the first command. You left out "flash"
You typed "fastboot partition gpt.bin"
Instead of "fastboot flash partition gpt.bin"
Please start over. If it fails at motoboot.img -- don't worry. Just continue with the rest of the commands. If we can get everything else to flash, you may well recover. Sometimes it DOES fail at flashing motoboot, but just continue with the commands.
Be sure to type them EXACTLY as I've listed -- you can't leave off "flash" anymore
Please try and update as to status. If you can get to the very end, with nothing but motoboot.img failing, we should be able to recover you.
Click to expand...
Click to collapse
Something moving...I repeated every single command, now I have on the phone Fastboot reason: Sticky bit factory_fastboot
What should I do now?
Thank you
Jack881 said:
Something moving...I repeated every single command, now I have on the phone Fastboot reason: Sticky bit factory_fastboot
What should I do now?
Thank you
Click to expand...
Click to collapse
Do this:
fastboot oem fb_mode_clear
fastboot reboot-bootloader
then start over with all the commands I previously listed
I recommend using copy / paste for all the commands just so none get messed up
samwathegreat said:
Do this:
fastboot oem fb_mode_clear
fastboot reboot-bootloader
then start over with all the commands I previously listed
I recommend using copy / paste for all the commands just so none get messed up
Click to expand...
Click to collapse
I did it: fastboot oem fb_mode_clear and fastboot reboot-bootloader and repeated all the commands, but now I have Partition (boot) Security version Downgraded. Fastboot reason: boot failure. Thank you
Jack881 said:
I did it: fastboot oem fb_mode_clear and fastboot reboot-bootloader and repeated all the commands, but now I have Partition (boot) Security version Downgraded. Fastboot reason: boot failure. Thank you
Click to expand...
Click to collapse
OK!
It looks like when you were on one of the other roms, you accepted an OTA to 4.4.3 or 4.4.4.....did this happen?
anyways, do this:
fastboot reboot-bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
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
Does it boot?? Hopefully at this point, you boot into android. Fingers crossed.... :fingers-crossed:
samwathegreat said:
OK!
It looks like when you were on one of the other roms, you accepted an OTA to 4.4.3 or 4.4.4.....did this happen?
anyways, do this:
fastboot reboot-bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
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
Does it boot?? Hopefully at this point, you boot into android. Fingers crossed.... :fingers-crossed:
Click to expand...
Click to collapse
No, gosh! maybe I have to repeat everything? now I have Partition (boot) Security version Downgraded Fastboot reason: Boot failure
Jack881 said:
No, gosh! maybe I have to repeat everything? now I have Partition (boot) Security version Downgraded Fastboot reason: Boot failure
Click to expand...
Click to collapse
I will have to continue helping you later tonight. Have to leave for a bit. I'm still hoping we will be able to recover you but it will take some more work, and we have to run the commands perfect. I'll post back here when I return.
Hi friends,
The app recommended by BQ "MTK Tool Flash" (SP_Flash_Tool_exe_Linux_v5.1612.00.100.zip) just didn't work for me on my Debian PC. There were always some excuses. So I tried some black command-line magic with fastboot and now I'm with a bricked device.
See ubuntu-android-installation-process-for-bq-aquaris-e4-5-and-e5 link I cannot post...
The good news is, I have installed the TWRP (twrp-3.1.1-0-freezerfhd.img) before I shot myself in the toe. So power + volume up gives me the comforting bluish screen of TWRP.
Question is, how can I bring the lovely device back to life? I wanted to flash official Android on it (which failed - 2.3.0_20170405-1553_bq_aquaris_m10_FHD_-FW.zip) and I'd like to complete that, but if it's a no go, I can go back to Ubuntu.
I have tried installing the image zip from twrp, but it said the image has invalid zip file format!
Thanks a lot for your help
Rob
failures
I've been struggling with this one. So I can switch to the bootloader mode and run fastboot commands. However, when I try to flash the system image I get some funny error:
Code:
sudo fastboot flash system ./system.img
target reported max download size of 134217728 bytes
erasing 'system'...
FAILED (remote: unknown command)
finished. total time: 0.002s
With the flash tool (after fixing all it's complaints) I'm stuck with a timeout on detecting the USB port (while fastboot works just fine)
Code:
Connecting to BROM...
Scanning USB port...
Search usb, timeout set as 3600000 ms
And with TWRP as mentioned earlier:
Code:
Invalid zip file format
I read the stock rom can be adjusted somehow to allow TWRP to flash it but I'm quite like what...? Android kitchen doesn't list my device as supported.
progress
Aha! This got us further:
Code:
sudo fastboot flash system -u -S 1G ./system.img
Which means do not erase the partition upfront, and sparse the file at max 1 GB.
Code:
sudo fastboot flash userdata -u -S 1G ./userdata.img
sudo fastboot flash boot -u -S 1G ./boot.img
sudo fastboot reboot
Now device is "powered by ubuntu" and stuck there... not sure what's happening
S now I tried flashing some more exotic partitions and the device is completely dead. I hope BQ can help...
undead
Wow, so BQ contacted me right away with a hard reset procedure. The key bit of information I must have overlooked somewhere is that for the flash tool to detect the device, the device must be plugged in while it's off and while the tool is waiting. We're now "powered by android" and system is ready to use. Oh my... thanks BQ
hello
i need help reflashing my phone from a software error it's seem's the software is corrupt and not letting me flash it,
After flashing various firmware's including the original stock and this one (VZW_XT907_4.4.2-KDA20.62-15.1_1FF.xml) 4.4.2 Android Kitkat with RSD Lite im getting the following error,
Fastboot Reason:
fastboot: max download size: 100MB
USB connected
Getvar max-sparse-size
Fastboot command failed
Getvar max-download-size
Downloading . . .
not found partition partition
E:No partition partition exisiting
Fastboot command failed
Hello,
Test flash with fastboot, with the gpt.bin file that I attached.
Code:
fastboot flash gpt gpt.bin
successes
Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via stock recovery because is no more needed. The updates will be done on the slot not used for example if you are using slot a the update will be installed on slot b and the slot b will be set as default. If you brick and you are in bootloop how you can restore the rom? You can't with Stock ROM you have, because the zip can be only installed via Update Engine, so what can you do? Flash a stock rom via fastboot. I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlocked. This will erase all your data and will wipe your internal storage.
HOW TO FLASH
This version is only for not branded devices
Download the zip;
Unpack the zip in a folder;
Reboot the OnePlus 7 Pro in fastboot mode (Power and volume + and volume-);
Connect the OnePlus 7 Pro to PC;
Run flash-all.bat flasher you need;
Wait until the process end;
The phone will automatically reboot.
FLASHER ADVANCED GUIDE
flash-all-partitions-fastboot.bat : this .bat will flash all possible partitions through fastboot (Except persist) , there are some criticals partitions that can't be flashed through fastboot;
flash-only-persist.bat : this .bat will flash only persist partition in fastboot mode (This is good for people that have problems with sensor);
flash-all-partitions-recovery-criticals.bat : this .bat will boot the twrp and will flash criticals partitions, use this carefully;
flash-system-boot-vendor.bat : this .bat is the same of older flash-all.bat and so it will flash only vendor, system and boot;
flash-all-partitions.bat : this .bat will run flash-all-partitions-fastboot.bat , then flash-only-persist.bat and then flash-all-partitions-recovery-criticals.bat .
Now usually the one needed is only the first "flash-all-partitions-fastboot.bat" but if you are badly bricked i recommend to use flash-all-partitions.bat .
DOWNLOAD
All roms on AFH: https://www.androidfilehost.com/?w=files&flid=294300
All roms on Sourceforge: https://sourceforge.net/projects/fastbootroms/files/OnePlus 7 Pro
OnePlus 7 Pro Persist: https://androidfilehost.com/?fid=6006931924117929081
BRANDED PHONE
For now branded device are not supported
MANUAL FLASH: Windows - OSX - Linux
If you want to manual flash these roms these are the commands (you need to extract images.zip before proceed)
Fastboot Partitions:
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 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
fastboot flash LOGO_a LOGO.img
fastboot flash LOGO_b LOGO.img
If you need also persist partition, this is the command:
Code:
fastboot flash persist persist.img
Criticals Partitions, for these you need to boot the TWRP:
Code:
fastboot boot TWRP.img
When you are in TWRP you need to run these commands to push and flash all criticals partitions:
Code:
adb push abl.img /sdcard/abl.img
adb shell dd if=/sdcard/abl.img of=/dev/block/bootdevice/by-name/abl_a
adb shell dd if=/sdcard/abl.img of=/dev/block/bootdevice/by-name/abl_b
adb push cmnlib.img /sdcard/cmnlib.img
adb shell dd if=/sdcard/cmnlib.img of=/dev/block/bootdevice/by-name/cmnlib_a
adb shell dd if=/sdcard/cmnlib.img of=/dev/block/bootdevice/by-name/cmnlib_b
adb push cmnlib64.img /sdcard/cmnlib64.img
adb shell dd if=/sdcard/cmnlib64.img of=/dev/block/bootdevice/by-name/cmnlib64_a
adb shell dd if=/sdcard/cmnlib64.img of=/dev/block/bootdevice/by-name/cmnlib64_b
adb push devcfg.img /sdcard/devcfg.img
adb shell dd if=/sdcard/devcfg.img of=/dev/block/bootdevice/by-name/devcfg_a
adb shell dd if=/sdcard/devcfg.img of=/dev/block/bootdevice/by-name/devcfg_b
adb push hyp.img /sdcard/hyp.img
adb shell dd if=/sdcard/hyp.img of=/dev/block/bootdevice/by-name/hyp_a
adb shell dd if=/sdcard/hyp.img of=/dev/block/bootdevice/by-name/hyp_b
adb push keymaster.img /sdcard/keymaster.img
adb shell dd if=/sdcard/keymaster.img of=/dev/block/bootdevice/by-name/keymaster_a
adb shell dd if=/sdcard/keymaster.img of=/dev/block/bootdevice/by-name/keymaster_b
adb push xbl.img /sdcard/xbl.img
adb shell dd if=/sdcard/xbl.img of=/dev/block/bootdevice/by-name/xbl_a
adb shell dd if=/sdcard/xbl.img of=/dev/block/bootdevice/by-name/xbl_b
adb push xbl_config.img /sdcard/xbl_config.img
adb shell dd if=/sdcard/xbl_config.img of=/dev/block/bootdevice/by-name/xbl_config_a
adb shell dd if=/sdcard/xbl_config.img of=/dev/block/bootdevice/by-name/xbl_config_b
adb push odm.img /sdcard/odm.img
adb shell dd if=/sdcard/odm.img of=/dev/block/bootdevice/by-name/odm_a
adb shell dd if=/sdcard/odm_config.img of=/dev/block/bootdevice/by-name/odm_b
adb push tz.img /sdcard/tz.img
adb shell dd if=/sdcard/tz.img of=/dev/block/bootdevice/by-name/tz_a
adb shell dd if=/sdcard/tz.img of=/dev/block/bootdevice/by-name/tz_b
REMEMBER
"Invalid sparce file format at header magic" is not an error, you need to wait a bit when you see that string, just wait.
These ROMs can't be used to update or downgrade your phone but just to restore your phone, so don't use them to come back to oreo or to update from oreo to pie.
If the rom seems doesn't start go in recovery stock and follow this guideline: English -> Wipe data and cache -> Erase everything.
If you want to rebrand your phone from HydrogenOS to OxygenOS you can follow this guide: Rebrand Guide
If you want you can use also my tool to flash Factory Images, unlock bootloader, flash twrp or to understand if the device is recognized: https://toolaio.tk/
Thanks to @SaiBork for first time tested
If you got some problems like write error or no partition, check this: https://forum.xda-developers.com/showpost.php?p=76658555&postcount=34
DONATE LINK
If you want to support this and others my projects please consider making a donation, thanks.
I know you said not for branded devices, are the partitions different for these devices?
Just wondering if this could be what we need to convert the T-Mobile version and if so if you need tester.
criptix said:
I know you said not for branded devices, are the partitions different for these devices?
Click to expand...
Click to collapse
Yes, sometimes also the rom is different. Actually the branded devices can't use this rom also if they want, because to use this rom you need to have an unlocked bootloader
Yeah figured bootloader would need to be unlocked as well.
If you happen to need testers for the conversion ( if your working on it) let me know.
I just SIM unlocked my T-Mobile variant today, and also applied for my unlock .bin on the OnePlus site!
Thank you! You revived my phone!
zzs001 said:
Thank you! You revived my phone!
Click to expand...
Click to collapse
Perfect, like for others oneplus devices i will continue to support them, if you want to contribute and help me, please consider making a donation, thanks.
I've F-ed my international 7 Pro up, used your flash all, seemed to have work, but stuck in a loop now... Anyone got any suggestions, please?
I was so happy when I found this post, I thought my problems were over, but yeah... apparently not
posedatull said:
I've F-ed my international 7 Pro up, used your flash all, seemed to have work, but stuck in a loop now... Anyone got any suggestions, please?
I was so happy when I found this post, I thought my problems were over, but yeah... apparently not
Click to expand...
Click to collapse
which version you had before use fastboot rom? which fastboot rom did you used?
I was on stock, tried to install twrp, didnt go well (wouldn't mount), and i wanted to wipe data/cache, and mistakenly wiped system as well because i wasnt paying attention. Tried putting the stock recovery, still wouldnt boot due to obvious reasons.... then I found this
Basically I had the 9.5.4 with deleted system when I attempted to use the flash all bat.
GM21BA, european 12gb one, if it makes any difference...
posedatull said:
I was on stock, tried to install twrp, didnt go well (wouldn't mount), and i wanted to wipe data/cache, and mistakenly wiped system as well because i wasnt paying attention. Tried putting the stock recovery, still wouldnt boot due to obvious reasons.... then I found this
Basically I had the 9.5.4 with deleted system when I attempted to use the flash all bat.
GM21BA, european 12gb one, if it makes any difference...
Click to expand...
Click to collapse
So you should use the 9.5.4 fastboot rom, have you used it?
of course.
I am hoping maybe a failed download, so I just redownloaded it and trying again now
posedatull said:
of course.
I am hoping maybe a failed download, so I just redownloaded it and trying again now
Click to expand...
Click to collapse
The process can take a lot of time, just wait until you see something like "presse a key to proceed"
also:
"extracting android-info.txt (0 MB) to RAM...
extracting boot.img (96 MB) to disk... took 0.386s
target reported max download size of 805306368 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.030s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (3472 MB) to disk..."
tose missing files, is that normal?
downloaded your zip, extracted it, started flash-all.bat, no modifications done whatsoever
---------- Post added at 04:02 PM ---------- Previous post was at 03:59 PM ----------
the zip finishes, no problem,ends with
"writing 'userdata'...
OKAY [ 0.003s]
rebooting...
finished. total time: 153.005s
Press any key to exit..."
and then the phone tries to boot, i get to the spinning 1+ logo, and it stays there for even an hour if i let it...
posedatull said:
also:
"extracting android-info.txt (0 MB) to RAM...
extracting boot.img (96 MB) to disk... took 0.386s
target reported max download size of 805306368 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.030s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (3472 MB) to disk..."
tose missing files, is that normal?
downloaded your zip, extracted it, started flash-all.bat, no modifications done whatsoever
---------- Post added at 04:02 PM ---------- Previous post was at 03:59 PM ----------
the zip finishes, no problem,ends with
"writing 'userdata'...
OKAY [ 0.003s]
rebooting...
finished. total time: 153.005s
Press any key to exit..."
and then the phone tries to boot, i get to the spinning 1+ logo, and it stays there for even an hour if i let it...
Click to expand...
Click to collapse
so i don't know, try to use the other flashall, you should unpack image.zip and other flashall in the main folder and then you should run the flash-all-fastboot.bat.
If you want you can try to flash the twrp in the boot partition and then try to flash the stock rom through sideload
i've just tried all of them one by one... still bootloop every time
posedatull said:
i've just tried all of them one by one... still bootloop every time
Click to expand...
Click to collapse
do you want to contact me on telegram? Maybe i can help you better
i'm struggling this at work, but i'll be home in about 2hours.
if you could help then, i would seriously appreciate it
posedatull said:
i'm struggling this at work, but i'll be home in about 2hours.
if you could help then, i would seriously appreciate it
Click to expand...
Click to collapse
Yes yes, write me on telegram, the nick is always the same: mauronofrio
hello, how long should it take to first boot after flashing all? I'm waiting for so long...