Database Develop

Need help ASAP!

So i was flashing unleashed rom which I've done a bunch of times already but this time i formatted system and realized i forgot to put the zip file on my card to flash and i accidentally rebooted device...now it just stays at motorola screen...i went into fast boot and tried the one click fast boot but it isn't working....it says this....which I'm not sure why cuz i have it hooked up right...
I'm on a mac and I'm not sure if thats why
***************************************************************************
* *
* dhacker29 Presents: One-Click Fastboot Restore and ROOT for the BIONIC *
* An easier way to recover after bricking or bootlooping your BIONIC *
* This script will restore your phone to stock unrooted, *
* and then give you the option to reroot your phone *
* *
* A special thanks for the info and files to: *
* http://BriefMobile.com/droid-bionic-recieves-fastboot-recovery-files *
* Visit us at TH3ORYROM.com *
* *
***************************************************************************
*
* Please make sure you do the following:
*
* (a) Hold down the Volume down button and push power to enter AP Fastboot mode
* (b) plug in your phone by USB
*
_EOF
read -n1 -s -p "* Press enter to continue..."
$adb kill-server > /dev/null 2>&1
echo "* Flashing boot.img"
echo "* Enter your root password to continue or ctrl-c if you do no wish to continue"
`sudo $fastboot flash boot boot.img`
echo "* Flashing system.img"
`sudo $fastboot flash system system.img`
echo "* Wiping data"
`sudo $fastboot -w`
echo "* Rebooting your phone now, factory restore complete"
`sudo $fastboot reboot`
echo "*"
echo "* Do you want to root your phone now?"
echo "*"
echo "* If so press 1 after your phone has rebooted and you have turned on"
echo "* USB debugging under Settings/Applications/Development and switched"
echo "* USB to PC mode or press 2 to exit"
select yn in "Yes" "No"; do
case $yn in
Yes ) echo "* Rooting your phone now..."; break;;
No ) exit;;
esac
done
cat <<_EOF

You have to follow the instructions for a fastboot FXZ:
edit: There are multiple places you can find the FXZ, xda bionic dev forums has it I do believe, but I can't post links yet... if you google search All Things Root for Android Forums that thread has links for the small file and the complete file.
Here is a list of files you are going to need:
RSD Lite 5.5 - MD5 EAE167B9F9ABE207579F29285E9BBF84
Motorola USB Drivers (Windows only)
32-bit - MD5 417375F263AE83C973CF8F2F317F88FE or
64-bit - MD5 FACAE88CA21B0C37E99D027F1F63628D
The fastboot binary (LINUX AND OSX ONLY) - MD5: 2DC253F848307C4A33DE7E8A2580772B
The FXZ file (MINIMAL - 213MB) - MD5: 08C76A533D74060A842EF5DDEEA95A47
You also need to:
Have a Windows PC (For Linux or Mac OS X users, refer to this XDA thread)
Charge your Bionic all the way
Back up your data (SD card or Titanium for rooted users) as /data will be erased
Now that the prerequisites are over with...
How to restore (Linux and OS X)
Put the fastboot binary into its own folder
Extract all of the files from the FXZ to that folder
Enable USB Debugging and Charge Only mode or if you don't have access to the OS (soft-brick, bootloops, etc), put your Bionic into Fastboot mode by holding the volume-down button and pressing the power button. Then use the volume down button to select AP Fastboot, then the volume up to select. Continue on.
Open up a terminal, change directories to the folder you made in step 1, then run these commands:
Code:
./fastboot flash system system.img
./fastboot flash boot boot.img
./fastboot flash recovery recovery.img
./fastboot -w
Shut off the phone using the power button
Turn it back on
Click to expand...
Click to collapse
---------- Post added at 04:04 PM ---------- Previous post was at 03:59 PM ----------
I've done this to my phone multiple times with the unleashed on Bionic just days ago, I know the screen you're talking about... the FXZ fastboot brought me back, but i'm on Windows 7 -- wouldn't know how to navigate on Mac's

There's a sticky in the dev forum labeled Bionic FAQ.
It contains many links including this one.
http://forum.xda-developers.com/showthread.php?t=1263009

HELP!!! My phone won't boot past the unlocked bootloader screen!!

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.

Problem installing not incremental ROM

Well I have tried to install MIUI ROM 6.5.26 after not processing updates for months (since november).
So I downloaded latest ROM and put it to the top of the partitions and then I wiped everything and that's where i might have done a mistake: I wiped internal storage (inside TWRP 2.8.7 i found there http://forum.xda-developers.com/mi-...timizing-leo-miui-advanced-tweaks-to-t3286972) then I might have might done a second mistake: I have done the command fastboot 'flash boot boot.img' as I read on an old HTC forum.
Then I pushed the latest ROM to the phone (as it was not there after the wipes) and when I tried installing it, it gave E: unable to mount 'cache' .
Now it seems i cannot enter TWRP, only Fastboot or I am stuck with MI logo.
I just want to install latest ROM, as I have done Titanium Backup before all the mess.
I don't know where i should start.

I am on mac so cannot use Mi Flash

EMJI79 said:
Well I have tried to install MIUI ROM 6.5.26 after not processing updates for months (since november).
So I downloaded latest ROM and put it to the top of the partitions and then I wiped everything and that's where i might have done a mistake: I wiped internal storage (inside TWRP 2.8.7 i found there http://forum.xda-developers.com/mi-...timizing-leo-miui-advanced-tweaks-to-t3286972) then I might have might done a second mistake: I have done the command fastboot 'flash boot boot.img' as I read on an old HTC forum.
Then I pushed the latest ROM to the phone (as it was not there after the wipes) and when I tried installing it, it gave E: unable to mount 'cache' .
Now it seems i cannot enter TWRP, only Fastboot or I am stuck with MI logo.
I just want to install latest ROM, as I have done Titanium Backup before all the mess.
I don't know where i should start.
Click to expand...
Click to collapse
you wiped internal sd so you have nothing the only way to solve is
Download the fastboot ROM https://www.dropbox.com/s/dg198q49dctzfgr/leo_images_5.11.26_20151104.0000.4_5.1_cn.tar.gz?dl=0 (recomend this others from this year locked bootloader)
Extract it to the same directory you extracted ADB/Fastboot
Press "Windows key + X" -> "Command Prompt (administrator)
In command prompt, go to your folder where your ADB/Fastboot are, assuming they are in C:\Fastboot, you type
> cd C:\Fastboot
> C:
10. Once in the "C:\Fastboot" folder, you will need to issue a chain of commands to flash critical images, so type:
C:\Fastboot>fastboot devices
C:\Fastboot>fastboot flash tz tz.mbn
C:\Fastboot>fastboot flash dbi sdi.mbn
C:\Fastboot>fastboot flash sbl1 sbl1.mbn
C:\Fastboot>fastboot flash rpm rpm.mbn
C:\Fastboot>fastboot flash aboot emmc_appsboot.mbn
C:\Fastboot>fastboot erase boot
C:\Fastboot>fastboot flash misc misc.img
C:\Fastboot>fastboot flash modem NON-HLOS.bin
C:\Fastboot>fastboot flash system system.img
C:\Fastboot>fastboot flash cache cache.img
C:\Fastboot>fastboot flash userdata userdata.img
C:\Fastboot>fastboot flash recovery recovery.img
C:\Fastboot>fastboot flash boot boot.img
C:\Fastboot>fastboot reboot
Now you're all set and should be able to boot normally.
after you can install recovery
to install recoverytwrp https://www.dropbox.com/s/hkuwc6d881im2hy/TWRP_leo.zip?dl=0
Extract it to the same directory you extracted ADB/Fastboot
Press "Windows key + X" -> "Command Prompt (administrator)
In command prompt, go to your folder where your ADB/Fastboot are, assuming they are in C:\Fastboot, you type
> cd C:\Fastboot
> C:
Once in the "C:\Fastboot" folder, you will need to issue a chain of commands to flash critical images, so type:
C:\Fastboot>fastboot devices
C:\Fastboot>fastboot flash recovery TWRP.img
C:\Fastboot>fastboot reboot
done now you can install latest rom from xiaomi.eu Does not locked bootloader

helderfp said:
you wiped internal sd so you have nothing the only way to solve is
Download the fastboot ROM https://www.dropbox.com/s/dg198q49dctzfgr/leo_images_5.11.26_20151104.0000.4_5.1_cn.tar.gz?dl=0 (recomend this others from this year locked bootloader)
Extract it to the same directory you extracted ADB/Fastboot
Press "Windows key + X" -> "Command Prompt (administrator)
In command prompt, go to your folder where your ADB/Fastboot are, assuming they are in C:\Fastboot, you type
> cd C:\Fastboot
> C:
10. Once in the "C:\Fastboot" folder, you will need to issue a chain of commands to flash critical images, so type:
C:\Fastboot>fastboot devices
C:\Fastboot>fastboot flash tz tz.mbn
C:\Fastboot>fastboot flash dbi sdi.mbn
C:\Fastboot>fastboot flash sbl1 sbl1.mbn
C:\Fastboot>fastboot flash rpm rpm.mbn
C:\Fastboot>fastboot flash aboot emmc_appsboot.mbn
C:\Fastboot>fastboot erase boot
C:\Fastboot>fastboot flash misc misc.img
C:\Fastboot>fastboot flash modem NON-HLOS.bin
C:\Fastboot>fastboot flash system system.img
C:\Fastboot>fastboot flash cache cache.img
C:\Fastboot>fastboot flash userdata userdata.img
C:\Fastboot>fastboot flash recovery recovery.img
C:\Fastboot>fastboot flash boot boot.img
C:\Fastboot>fastboot reboot
Now you're all set and should be able to boot normally.
after you can install recovery
to install recoverytwrp https://www.dropbox.com/s/hkuwc6d881im2hy/TWRP_leo.zip?dl=0
Extract it to the same directory you extracted ADB/Fastboot
Press "Windows key + X" -> "Command Prompt (administrator)
In command prompt, go to your folder where your ADB/Fastboot are, assuming they are in C:\Fastboot, you type
> cd C:\Fastboot
> C:
Once in the "C:\Fastboot" folder, you will need to issue a chain of commands to flash critical images, so type:
C:\Fastboot>fastboot devices
C:\Fastboot>fastboot flash recovery TWRP.img
C:\Fastboot>fastboot reboot
done now you can install latest rom from xiaomi.eu Does not locked bootloader
Click to expand...
Click to collapse
OK thanks a lot. :good:
I will try that tonight or tomorrow (already downloading from your dropbox, thanks again).
I'll let you know.

Only i dont understand: (recomend this others from this year locked boot loader) ?

EMJI79 said:
Only i dont understand: (recomend this others from this year locked boot loader) ?
Click to expand...
Click to collapse
It broke halfway, so I am trying again. Thank you for your patience.

Well, I downloaded it entirely and tried "fastboot the tz", then I get -> "device is locked. Cannot flash images"...
So I guess I locked my bootloader already, somehow... :crying:

EMJI79 said:
Well, I downloaded it entirely and tried "fastboot the tz", then I get -> "device is locked. Cannot flash images"...
So I guess I locked my bootloader already, somehow... :crying:
Click to expand...
Click to collapse
ok
so you have to do this
Download Xiaomi MiFlash Tool and install it to your PC https://www.dropbox.com/s/1qntzckybxg3rr4/MiSetup3.2.1.3111_2717.zip?dl=0
Download Qualcomm Driver 32-bit https://www.dropbox.com/s/klnn6h9z7038u80/QDLoader HS-USB Driver_32bit_Setup.zip?dl=0 OR Qualcomm Driver 64-bit https://www.dropbox.com/s/gvizx1ja1vmihox/QDLoader HS-USB Driver_64bit_Setup.zip?dl=0 install it to your PC
Enter your phone in fastboot mode
in command promt wrtite:
cmd
cd C:\fastboot
fastboot devices
fastboot oem edl
After the last command Your Note pro detected as a new device
Launch MiFlash and flash Note pro not locked ROM if you get one error at the midle (not at the beginnig) of flashing dont worry, you have unlocked bootloader, and you can folow the previous steps you already tried
The latest roms from xiaomi (since January 2016) lockes bootloader that is why i recomend that on the link.

Thanks
But I am on Mac, no MiFlash, only ADB, fastboot...

EMJI79 said:
Thanks
But I am on Mac, no MiFlash, only ADB, fastboot...
Click to expand...
Click to collapse
to work on mac
Download the fastboot ROM for your Mi phone and place it on your desktop. Double-click on it and Archive Utility will extract the file on the desktop, so you'll get a folder,
now go to terminal an type
cd C:\fastboot
fastboot devices
fastboot oem edl
In order to use the fastboot scripts, you should go to the folder. For that purpose, execute the following command (the folder name may be different in your case, the example below is for cancro):
cd ~/Desktop/cancro_global_images_V7.0.5.0.KXDMICI_20151016.0000.3_4.4_global
Copy the Code
Quick tip: you don't need to write the whole folder name, just type cd ~/Desktop/cancro, then press the Tab key and Terminal will append the folder name automatically.
Once inside, you need to make the scripts (all the files with .sh extension) executable. Execute the following command:
chmod +x ./*.sh
Now, the scripts are ready to use. In order to start the process, issue one of the following commands:
./flash_all.sh
or
./flash_all_except_storage.sh
or
./flash_all_except_data_storage.sh
When you start any of the scripts, you'll see the fastboot messages, flowing through the Terminal window. Once the script has done its work, the phone will restart itself automatically.

When I change directory for the fastboot ROM directory, the fastboot screen on my phone disappears. I have done the steps after that but i see no message on the terminal or the phone screen. My phone screen is black.
Edit: In fact the fastboot screen on my phone disappears when I type fastboot oem edl in my terminal although i get the message OKAY in my terminal.

EMJI79 said:
When I change directory for the fastboot ROM directory, the fastboot screen on my phone disappears. I have done the steps after that but i see no message on the terminal or the phone screen. My phone screen is black.
Edit: In fact the fastboot screen on my phone disappears when I type fastboot oem edl in my terminal although i get the message OKAY in my terminal.
Click to expand...
Click to collapse
so don't change the directory put the rom in the fastboot folder and do the next step
if you are not able to flash in your mac try in another pc (windows)

Don't you think I just locked my bootloader and I need to do the apply stuff for getting my phone unlocked?

EMJI79 said:
Don't you think I just locked my bootloader and I need to do the apply stuff for getting my phone unlocked?
Click to expand...
Click to collapse
you dont need
just try
put rom in fastboot folder and
cd C:\fastboot
fastboot devices
fastboot oem edl
chmod +x ./*.sh
./flash_all.sh
to unlock bootloader the previous steps (not this) work fine on windows
http://en.miui.com/thread-237832-1-1.html
https://xiaomi.eu/community/threads/mi-note-pro-complete-beginners-guide.30817/

every time I type:
fastboot oem edl
the screen of the smartphone goes off

Maybe I will buy Windows to make it work in VM...
Only can you interpretate why fastboot oem edl makes the screen go off?

EMJI79 said:
Maybe I will buy Windows to make it work in VM...
Only can you interpretate why fastboot oem edl makes the screen go off?
Click to expand...
Click to collapse
do you have qualcom drivers instaled?

No
Will try tomorrow.
Thanks again.
The link to your dropbox for Qualcomm drivers is for Windows, i found that:https://developer.qualcomm.com/download/software
and Snapdragon SDK but I have to register.

Is Snapdragon SDK actually Qualcomm drivers?

helderfp said:
do you have qualcom drivers instaled?
Click to expand...
Click to collapse
Hello,
OK, no Qualcomm drivers for Mac it seems... I have searched thoroughly and haven't found. I have asked a en.miui dev and waiting for the response.. Don't have them?

[Untested][Linux/ Mac] Fastboot package for Oreo January update

Hi all,
this one is for the brave, as it is still untested.
Nevertheless, please find here some information what I did:
Got the latest full OTA package here from xda
Extracted payload.bin into the fastboot compatible .img files
Adapted the "flash_all_except_storage script" in order to automate the flashing and included it
As I have right now (just my luck) an issue with fastboot not detecting my phone, I cannot test right now. Will try again myself in the evening though, at least that is the plan.
In the meantime any brave (no guarantees, no warranties) are welcome to test it. Apart from the above mentioned changes, it is the update as it was distributed by Xiaomi/ Google including the January security patch:
Android 8.0.0 [OPR1.170623.026.8.1.10]
link removed as official version is now available here
I am looking forward to your feedback.
P.S.: For more information how to use it, please have a look here
UPDATE: system.img seems to be not flashable right now and I have no more ideas right now what I could do about it. So sorry guys, back to waiting for Xiaomi again.

downloading...
will report the result later.
EDIT: Sorry, I just saw that it only includes a "flash_all_except_storage.sh" for Linux/Mac.. Could I use the *.bat script from an official fastboot image on this one?

i dont have a Mac, windows 10. how do i flash it ?

soeschelz said:
downloading...
will report the result later.
EDIT: Sorry, I just saw that it only includes a "flash_all_except_storage.sh" for Linux/Mac.. Could I use the *.bat script from an official fastboot image on this one?
Click to expand...
Click to collapse
Rawwr said:
i dont have a Mac, windows 10. how do i flash it ?
Click to expand...
Click to collapse
@ all dear Windows users: The scripts from the official fastboot package require some slight changes, due to some different namings. So far I have done this only for Linux/ Mac and included the appropriate script, but you could still flash the *.img files via the following fastboot commands:
Code:
fastboot oem unlock
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash sbl1 sbl1.img
fastboot flash sbl1bak sbl1.img
fastboot flash rpm rpm.img
fastboot flash rpmbak rpm.img
fastboot flash tz tz.img
fastboot flash tzbak tz.img
fastboot flash devcfg devcfg.img
fastboot flash devcfgbak devcfg.img
fastboot flash dsp dsp.img
fastboot flash aboot aboot.img
fastboot flash abootbak aboot.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash lksecapp lksecapp.img
fastboot flash lksecappbak lksecapp.img
fastboot flash cmnlib cmnlib.img
fastboot flash cmnlibbak cmnlib.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash cmnlib64bak cmnlib64.img
fastboot flash keymaster keymaster.img
fastboot flash keymasterbak keymaster.img
fastboot set_active a
fastboot reboot

majamee said:
@ all dear Windows users: The scripts from the official fastboot package require some slight changes, due to some different namings. So far I have done this only for Linux/ Mac and included the appropriate script, but you could still either flash the *.img files via the following fastboot commands:
Code:
fastboot oem unlock
fastboot flash modem_a modem.img
Click to expand...
Click to collapse
cant you make a script ? it is hard to enter every code at once

@majamee
I tried to flash manually but no luck. It seem all OK until I flash system.img.
After I enter
Code:
fastboot flash system_a system.img
I got the following error:
Code:
invalid sparse file format at header magi
then it flashes system_a. Same with system_b. All other commands run without any error. After a reboot I'm stuck on bootsplash.
I used fastboot and adb linked in the thread mentioned in first post and had no problem with flashing the first Oreo.
I hope you understand me, I'm very tired and not a native speaker

soeschelz said:
@majamee
I tried to flash manually but no luck. It seem all OK until I flash system.img.
After I enter
I got the following error:
then it flashes system_a. Same with system_b. All other commands run without any error. After a reboot I'm stuck on bootsplash.
I used fastboot and adb linked in the thread mentioned in first post and had no problem with flashing the first Oreo.
I hope you understand me, I'm very tired and not a native speaker
Click to expand...
Click to collapse
Thank you for your helpful feedback. I will see if I can do something about it, except waiting for xiaomi to finally release the fastboot image themselves or I get my ota without reading play services data.

Can you explain me how you extracted payload.bin to .img files

ramesh1686 said:
Can you explain me how you extracted payload.bin to .img files
Click to expand...
Click to collapse
I can tell you the basic instructions, but for the details I have to ask you to please have a look yourself how to do it for your Operating System.
So,
You download both python scripts from here: https://gist.github.com/ius/42bd02a5df2226633a342ab7a9c60f15
You make sure you have installed python and google-protobuf binding for python
You open a terminal/ shell/ cmd and navigate via the "cd" command to the directory the payload.bin and the both .py scripts are
run the following command "payload_dumper.py payload.bin"
I personally did these parts on a Linux system as it was at least for me the easiest way to have python and protobuf set up in no time.
----
Btw. I had another look, if I can do something about the system.img not being flashable at the moment. Nevertheless no luck so far, I begin to wonder if the OTA package is really a full OTA, due to that or just a very big update as it is intended to update Android N to O...
Sorry, for the failed attempt, at least it was worth a try.

I had issue with "invalid sparse file format at header magi" before (also extracted image from OTA), but it flashed successfully. Flashing just took longer than usual. However I had issues with failed video recording and the only fix for me was to use full flash of stock fastboot ROM. There might be something missing in extracted images from OTA package.

I have unpacked the latest payload.bin file from Android 8.0.0 [OPR1.170623.026.8.1.10] and the size of the system.img is 3.2 GB . This is too much?
The system partition has a size of 3072 MB. It's some error of unpacking?

Fastboot ROM is available http://bigota.d.miui.com/8.1.10/tissot_images_8.1.10_20180110.0000.00_8.0_8ea503201b.tgz
Source: http://en.miui.com/thread-1596182-1-1.html

[ROM][STOCK][FASTBOOT][OP7P] Stock Fastboot ROMs for OnePlus 7 Pro/ 7 Pro 5G

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...