Database Info

[10/14/2012][RELEASE][UNOFFICIAL]Stock 67.21.125 ICS FXZ[Minimal/Minimal-Standard]

Do you want the fastboot files for ics (official AT&T US)?
well its all (or almost all) here!!!
Note: This is the minimal standard that is just missing the system.img and the junk apps in the preinstall partition, we should get it with the %100 OEM official .
Also: I'm not responsible if this brick's your Atrix 2!!!
And finally, the download link:
Minimal
Minimal Standard
Cheers,
TCF38012
PS: Don't flash your own system.img this WILL SOFT BRICK YOUR DEVICE.
List of Images Needed(by priority):
1. System (DON'T USE THE SOUTH AFRICIAN ONE AND SOFT BRICK)

Reserved.

Good job man!
It's important to have an ICS FXZ.
Sent from my MB865 using xda app-developers app

sad_but_cool1 said:
Good job man!
It's important to have an ICS FXZ.
Sent from my MB865 using xda app-developers app
Click to expand...
Click to collapse
Thanks, but it is incomplete so don't totally rely on it.

So what happens if you bork your system image? Have you tested that yet?
I do see you are looking for a system image, but I am curious how this can save you from a boot loop without that.
Nice start though.

jimbridgman said:
So what happens if you bork your system image? Have you tested that yet?
I do see you are looking for a system image, but I am curious how this can save you from a boot loop without that.
Nice start though.
Click to expand...
Click to collapse
Thanks.
I have every image now except for radio.
I'll upload the final one for the second leak when I make the most hardest part(radio.img)

tcf38012 said:
Thanks.
I have every image now except for radio.
I'll upload the final one for the second leak when I make the most hardest part(radio.img)
Click to expand...
Click to collapse
You can grab it off the phone and use the ext4utils to package it up, there are few guides on how to do it for the og atrix, and you can figure the rest out from there.... that is similar to how I have done it.

Don't we have to worry about the certs on those missing img files? From my understanding, you can't just dd/cat those images and flash on anyone's phone.. and from some of our previous tests with mtnlion.. we've tried that.
Or, would everyone have to make their own images? Found this in a post by whirleyes (not sure how much weight it holds, but similar idea):
whirleyes said:
Next time you got it back from service, do
Code:
cat /dev/block/system > /mnt/sdcard/system.img
& put it somewhere safe.
It seems that you can restore own system partition backup from fastboot.
Condition :
bootloader won't check security certificate when restored from own backup
you must used moto-fastboot.exe & not fasboot.exe
Click to expand...
Click to collapse
I would really like to see this fxz come to life though... keep it up.

alteredlikeness said:
Don't we have to worry about the certs on those missing img files? From my understanding, you can't just dd/cat those images and flash on anyone's phone.. and from some of our previous tests with mtnlion.. we've tried that.
Or, would everyone have to make their own images? Found this in a post by whirleyes (not sure how much weight it holds, but similar idea):
I would really like to see this fxz come to life though... keep it up.
Click to expand...
Click to collapse
Yes that works with moto-fastboot since it does not check during flashing. Now booting those is another issue. The boot image is the one to really worry about. System image and others not so much, even the recovery image is not signed.

jimbridgman said:
Yes that works with moto-fastboot since it does not check during flashing. Now booting those is another issue. The boot image is the one to really worry about. System image and others not so much, even the recovery image is not signed.
Click to expand...
Click to collapse
Right, but whirleye's was saying the certs aren't checked only if you flash your own system.img on your own phone.. or that's what i took away from it. Plus, we flashed the ICS system and boot from your phone on mtnlion's, and he came out with new CG errors.. still stuck in fastboot.
I guess this is a good place to elaborate on all of this.. if it's not considered hijacking.
@tcf38012 - has this been tested?

alteredlikeness said:
Right, but whirleye's was saying the certs aren't checked only if you flash your own system.img on your own phone.. or that's what i took away from it. Plus, we flashed the ICS system and boot from your phone on mtnlion's, and he came out with new CG errors.. still stuck in fastboot.
I guess this is a good place to elaborate on all of this.. if it's not considered hijacking.
@tcf38012 - has this been tested?
Click to expand...
Click to collapse
Right, that is why I was saying that flashing is easy, but booting is much harder with the locked bootloader checking the signature before booting, hence the cg errors from MY image on someone else's phone.

Updated 10/14/2012!!!
Cheers!!!

tcf38012 said:
Updated 10/14/2012!!!
Cheers!!!
Click to expand...
Click to collapse
So what exactly is this and how do we use it?
Sent from my MB865 using xda premium

tmease1 said:
So what exactly is this and how do we use it?
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
It is the partial fastboot files for ATT US 4.0.4. Nothing like a bootloader unlock or jellybean. When you are softbricked, just use these in AP fastboot and you are back to normal
Cheers!!!

I do not understand exactly how this works, please be more explicit.
Well let me know if this would work for me, my problem was that upgrading from GB to ICS 2.3.6 Official OTA, everything worked well and use the computer all day, until it froze and reboot and get stuck in the Motorola logo and back and restarted.

Andr3s said:
I do not understand exactly how this works, please be more explicit.
Well let me know if this would work for me, my problem was that upgrading from GB to ICS 2.3.6 Official OTA, everything worked well and use the computer all day, until it froze and reboot and get stuck in the Motorola logo and back and restarted.
Click to expand...
Click to collapse
This may help you since it sounds like you are softbricked. At this point you have nothing to lose and the boot.img is already there on your phone. Give it a shot and if it doesn't work you may be able to take it to AT&T since it was the official OTA that bricked ya. Good luck!!!

Ok friend, another question, as I use the files that I download, Minimal, Minimal Standard? also you do with South Africa FXZ file?
regards

Andr3s said:
Ok friend, another question, as I use the files that I download, Minimal, Minimal Standard? also you do with South Africa FXZ file?
regards
Click to expand...
Click to collapse
Minimal Standard. All you need from the South Africa FXZ is the system.img and flash with "moto-fastboot flash system system.img". Don't flash anything else from the South Africa FXZ.
Cheers!!!

Ok to get this straight, first put the phone in Fastboot bike, then unzip the file 4.0.4_67.21.125_edison_fxz_minimal_standard, run the file and then run flash.bat "moto-fastboot flash system system.img" with the system.img? That is so true?
if this is so I could include the system.img file in the same folder and add the file. bat line "moto-fastboot flash system system.img"?

Hello, after doing all this, I have this problem
Invalid CG OTV (CG: systema): Invalid SP Data
Invalid CG HAB (CG: system, status: 0X0056)
Invalid CG OTV (CG: system)
sending 'mbm' (256 KB)... OKAY [ 0.024s]
writing 'mbm'... OKAY [ 0.466s]
rebooting into bootloader... OKAY [ 0.285s]
sending 'mbmloader' (41 KB)... FAILED (command write failed (No such file or
directory))
sending 'mbm' (256 KB)... FAILED (command write failed (No such file or
directory))
sending 'cdt.bin' (16 KB)... FAILED (command write failed (No such file or
directory))
sending 'lbl' (16 KB)... FAILED (command write failed (No such file or
directory))
sending 'logo.bin' (854 KB)... FAILED (command write failed (No such file or
directory))
< waiting for device >
sending 'ebr' (16 KB)... OKAY [ 0.007s]
writing 'ebr'... OKAY [ 0.502s]
sending 'mbr' (16 KB)... OKAY [ 0.249s]
writing 'mbr'... OKAY [ 0.471s]
sending 'devtree' (512 KB)... OKAY [ 0.286s]
writing 'devtree'... OKAY [ 0.519s]
sending 'boot' (8192 KB)... OKAY [ 1.401s]
writing 'boot'... OKAY [ 0.877s]
sending 'recovery' (9216 KB)... OKAY [ 1.609s]
writing 'recovery'... OKAY [ 1.433s]
sending 'radio' (12080 KB)... OKAY [ 1.109s]
writing 'radio'... OKAY [ 1.906s]
sending 'cdrom' (12032 KB)... OKAY [ 1.049s]
writing 'cdrom'... INFOPreflash validation failure
FAILED (remote: )
sending 'preinstall' (262144 KB)... OKAY [ 17.227s]
writing 'preinstall'... OKAY [ 28.739s]
sending 'preinstall' (20480 KB)... OKAY [ 1.433s]
writing 'preinstall'... OKAY [ 1.901s]
sending 'system' (262144 KB)... OKAY [ 19.473s]
writing 'system'... OKAY [ 29.494s]
sending 'system' (229120 KB)... OKAY [ 15.423s]
writing 'system'... OKAY [ 25.304s]
erasing 'userdata'... OKAY [ 0.045s]
erasing 'cache'... OKAY [ 0.666s]
rebooting...
Press any key to continue . . .
Click to expand...
Click to collapse

WiFi not working after flashing stock files.

Hi there!
Before I flashed these I had 5.1.1 Retail UK stock, rooted, xposed installed with gravitybox, disabled the softkeys with the build.prop command & turned the volume up with rx_mixerpaths
I downloaded XT1541_OSPREY_RETGB_5.1.1_LPI23.72-47_cid7_subsidy-DEFAULT_CFC.xml.zip from this thread & used this guide http://forum.xda-developers.com/2015...ctory-t3187750 to flash the phone to complete stock before I pass it down the family.
Upon booting it won't turn on the WiFi, I try to turn it on & it flicks off straight away. I had a quick search & came across this thread http://forum.xda-developers.com/moto...tooth-t2813308 I have checked the /persist folder & its empty unlike those guys in that thread.
I was wondering if someone could be generous enough to share these files with me? Unless there is another way to get the WiFi working again?
Many many thanks!
Below is a copy of the fastboot commands.
C:\adb>fastboot devices
ZY2223RTMH fastboot
C:\adb>fastboot flash partition gpt.bin
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.005s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.713s]
finished. total time: 0.720s
C:\adb>fastboot flash bootloader bootloader.img
target reported max download size of 268435456 bytes
sending 'bootloader' (2546 KB)...
OKAY [ 0.085s]
writing 'bootloader'...
(bootloader) flashing sbl1 ...
(bootloader) flashing aboot ...
(bootloader) flashing tz ...
(bootloader) flashing hyp ...
(bootloader) flashing rpm ...
OKAY [ 1.596s]
finished. total time: 1.683s
C:\adb>fastboot flash logo logo.bin
target reported max download size of 268435456 bytes
sending 'logo' (917 KB)...
OKAY [ 0.033s]
writing 'logo'...
OKAY [ 0.074s]
finished. total time: 0.108s
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.524s]
writing 'recovery'...
OKAY [ 0.446s]
finished. total time: 0.971s
C:\adb>fastboot flash system system.img_sparsechunk.0
target reported max download size of 268435456 bytes
sending 'system' (262140 KB)...
OKAY [ 8.236s]
writing 'system'...
OKAY [ 6.949s]
finished. total time: 15.187s
C:\adb>fastboot flash system system.img_sparsechunk.1
target reported max download size of 268435456 bytes
sending 'system' (262143 KB)...
OKAY [ 8.223s]
writing 'system'...
OKAY [ 6.777s]
finished. total time: 15.003s
C:\adb>fastboot flash system system.img_sparsechunk.2
target reported max download size of 268435456 bytes
sending 'system' (232608 KB)...
OKAY [ 7.297s]
writing 'system'...
OKAY [ 6.221s]
finished. total time: 13.519s
C:\adb>fastboot flash system system.img_sparsechunk.3
target reported max download size of 268435456 bytes
sending 'system' (233343 KB)...
OKAY [ 7.332s]
writing 'system'...
OKAY [ 6.012s]
finished. total time: 13.348s
C:\adb>fastboot flash system system.img_sparsechunk.4
target reported max download size of 268435456 bytes
sending 'system' (257130 KB)...
OKAY [ 8.067s]
writing 'system'...
OKAY [ 6.554s]
finished. total time: 14.623s
C:\adb>fastboot flash system system.img_sparsechunk.5
target reported max download size of 268435456 bytes
sending 'system' (228585 KB)...
OKAY [ 7.171s]
writing 'system'...
OKAY [ 5.850s]
finished. total time: 13.024s
C:\adb>fastboot flash modem NON-HLOS.bin
target reported max download size of 268435456 bytes
sending 'modem' (36940 KB)...
OKAY [ 1.165s]
writing 'modem'...
OKAY [ 1.006s]
finished. total time: 2.172s
C:\adb>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.016s]
finished. total time: 0.017s
C:\adb>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.014s]
finished. total time: 0.015s
C:\adb>fastboot flash fsg fsg.mbn
target reported max download size of 268435456 bytes
sending 'fsg' (2031 KB)...
OKAY [ 0.068s]
writing 'fsg'...
OKAY [ 0.081s]
finished. total time: 0.151s
C:\adb>fastboot erase cache
erasing 'cache'...
OKAY [ 0.019s]
finished. total time: 0.019s
C:\adb>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.795s]
finished. total time: 0.796s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.007s

I had the exact same problem when trying to flash the generic Canadian firmware. I flashed three times to no avail. Then I downloaded and flashed a carrier-specific version of the Canadian firmware and suddenly wifi worked.

Sevael said:
I had the exact same problem when trying to flash the generic Canadian firmware. I flashed three times to no avail. Then I downloaded and flashed a carrier-specific version of the Canadian firmware and suddenly wifi worked.
Click to expand...
Click to collapse
Any chance you'd be able to share your files in /persist folder if you are rooted?
I think this will sort it. The phone was a simfree one I don't really want to flash carrier-specific software if possible.

Powereh said:
I think this will sort it. The phone was a simfree one I don't really want to flash carrier-specific software if possible.
Click to expand...
Click to collapse
The carrier-specific one won't lock your phone or put any bloatware on it. It's simply one that was taken from a phone that somebody bought from that carrier. The one I used was from a different carrier than the one I bought the phone from originally.
Powereh said:
Any chance you'd be able to share your files in /persist folder if you are rooted?
Click to expand...
Click to collapse
I can't from where I am right now. Hopefully you can find someone who can upload it, otherwise I recommend giving a different firmware download a try.

Here ya go, keep in mind this is from XT1540 Canadian retail.
https://drive.google.com/file/d/0B4Gyz91x5k7gdUoxQUtldEZ3Wmc/view?usp=docslist_api
Sent from my MotoG3 using XDA Free mobile app

Cheers for the help guys, I will try those files out once i get home from work later.
I'll let you know the outcome in due course.

christopherrrg said:
Here ya go, keep in mind this is from XT1540 Canadian retail.
https://drive.google.com/file/d/0B4Gyz91x5k7gdUoxQUtldEZ3Wmc/view?usp=docslist_api
Sent from my MotoG3 using XDA Free mobile app
Click to expand...
Click to collapse
OK tried your files & it just keeps force closing every thing upon boot an endless amount.
I think I need XT1541 specific files.
Thank you so much for taking the time to upload those though! I really appreciate it.

Fixed it I had to flash this one instead Retail Great Britain (1GB) - XT1541_OSPREY_RETGB_5.1.1_LPI23.72-22_cid7
Cheers for the guys who tried to help

Powereh said:
Fixed it I had to flash this one instead Retail Great Britain (1GB) - XT1541_OSPREY_RETGB_5.1.1_LPI23.72-22_cid7
Cheers for the guys who tried to help
Click to expand...
Click to collapse
Glad you're back up! Change thread to solved in case passer bys need the information.
Sent from my MotoG3 using XDA Free mobile app

christopherrrg said:
Glad you're back up! Change thread to solved in case passer bys need the information.
Sent from my MotoG3 using XDA Free mobile app
Click to expand...
Click to collapse
I don't think the issue is solved, he just returned to the previous factory image, I'm having the same issue with the US model. I posted in the factory image thread on general and I'm not the only one
at least for some people if you try to upgrade via fastboot, wifi is broken

sgloki77 said:
I don't think the issue is solved, he just returned to the previous factory image, I'm having the same issue with the US model. I posted in the factory image thread on general and I'm not the only one
at least for some people if you try to upgrade via fastboot, wifi is broken
Click to expand...
Click to collapse
Agreed - I have this problem as well. I've searched through the threads, but haven't found a solution yet.

cdluck said:
Agreed - I have this problem as well. I've searched through the threads, but haven't found a solution yet.
Click to expand...
Click to collapse
you need to flash back to the original factory image and then take the OTA , do NOT try to upgrade directly with the latest factory image, or you will find yourself in brick city
Sent from my Nexus 6 using Tapatalk

sgloki77 said:
you need to flash back to the original factory image and then take the OTA , do NOT try to upgrade directly with the latest factory image, or you will find yourself in brick city
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I'll try that, thanks - is flashing back to the original factory image the same process, just with a different zip (e.g. XT1540_OSPREY_RETUS_2GB_5.1.1_LPI23.72-44_cid9_subsidy-DEFAULT_CFC)?
Also, this wifi thing is weird - I was able to connect to my home wifi without issue, but my work wifi causes the shutdown problem (if I try to fiddle with it and get it to connect, it just crashes and reboots the phone).

cdluck said:
I'll try that, thanks - is flashing back to the original factory image the same process, just with a different zip (e.g. XT1540_OSPREY_RETUS_2GB_5.1.1_LPI23.72-44_cid9_subsidy-DEFAULT_CFC)?
Also, this wifi thing is weird - I was able to connect to my home wifi without issue, but my work wifi causes the shutdown problem (if I try to fiddle with it and get it to connect, it just crashes and reboots the phone).
Click to expand...
Click to collapse
no man [emoji33] that one you quoted is the bad apple, when I said "original" I meant the one your phone shipped with(16.3)
Sent from my Nexus 6 using Tapatalk

sgloki77 said:
no man [emoji33] that one you quoted is the bad apple, when I said "original" I meant the one your phone shipped with(16.3)
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
My mistake, I copied the name from the wrong file - thanks for catching that for me!

sgloki77 said:
you need to flash back to the original factory image and then take the OTA , do NOT try to upgrade directly with the latest factory image, or you will find yourself in brick city
Click to expand...
Click to collapse
:crying: really!?, I was thinking about update directly with latest firmware to avoid OTA

El_Nuevo said:
:crying: really!?, I was thinking about update directly with latest firmware to avoid OTA
Click to expand...
Click to collapse
by my experience
-flashing 16.3 image was ok,
-flashing 44 image (I only flashed system and radio) resulted in broken wifi
by other users' experiences I read
-flashing 44 image(all partitions) resulted in a brick
-flashing 47 image was ok at least by one user
my device is XT1540 US 1GB RAM at this point I would suggest you research your particular model/factory images compatible with your model and decide for yourself what factory image to flash, there's been a few bricks already so beware of dragons...

Internal Storage show less size after upgrade to Android 6.0

Hi all
After upgrade my firmware the internal storage show 3.2 GB free space(total size = 3.2 GB !! ) and I have problems to upgrade o downgrade to 5.1.1 any help or idea for this problem ?
thanks friends

OberonMX said:
Hi all
After upgrade my firmware the internal storage show 3.2 GB free space(total size = 3.2 GB !! ) and I have problems to upgrade o downgrade to 5.1.1 any help or idea for this problem ?
thanks friends
Click to expand...
Click to collapse
You need to do a factory reset and choose Erase Internal Storage. Make sure you back it up if you have anything important on it. Then after you wipe it will show the correct storage.

ajsmsg78 said:
You need to do a factory reset and choose Erase Internal Storage. Make sure you back it up if you have anything important on it. Then after you wipe it will show the correct storage.
Click to expand...
Click to collapse
thanks
thats fix the problem., but now start android show this SCREEN
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Enable ... settings failed

OberonMX said:
thanks
thats fix the problem., but now start android show this SCREEN
Enable ... settings failed
Click to expand...
Click to collapse
I've never seen that before. Were you on stock when you did the wipe? Try putting in 6666 or 5555, 1111, 0000 or possibly the last 4 digits of your phone number. Try going to Settings --> screen lock --> PIN --> secure start-up and seeing if there is anything you can disable in there.

ajsmsg78 said:
I've never seen that before. Were you on stock when you did the wipe? Try putting in 6666 or 5555, 1111, 0000 or possibly the last 4 digits of your phone number. Try going to Settings --> screen lock --> PIN --> secure start-up and seeing if there is anything you can disable in there.
Click to expand...
Click to collapse
I think that problem origin firmwares MODEM.IMG and MODEM_UPDATENV.IMG , i dont have stock when I did flash
(My Model DAV-703L Chinese 32 GB Titanium G)
you can post firmware folders of your devices ? ... storage on / ... root maybe:
/3rdmodem
/3rdmodem-nvm
/mnvm2:0
/cust
/oem
/modem_log
/vendor
thank you so much for all help

OberonMX said:
I think that problem origin firmwares MODEM.IMG and MODEM_UPDATENV.IMG , i dont have stock when I did flash
(My Model DAV-703L Chinese 32 GB Titanium G)
you can post firmware folders of your devices ? ... storage on / ... root maybe:
/3rdmodem
/3rdmodem-nvm
/mnvm2:0
/cust
/oem
/modem_log
/vendor
thank you so much for all help
Click to expand...
Click to collapse
OK give me a minute to extract those. Do you want the B209 ones or the B029 ones? I don't own a P8 Max so I can't extract them from my phone, only from the stock roms.

ajsmsg78 said:
OK give me a minute to extract those. Do you want the B209 ones or the B029 ones?
Click to expand...
Click to collapse
Hi friend ! mmm thats files stay in your / ... extract with ES Explorer or file manager with root privileges for I compare thats files with my firmwares
all files ok... ever B209 Android M / EMUI 4 but my system is running you ROM
thank you (sorry for my bad bad english )

OberonMX said:
Hi friend ! mmm thats files stay in your / ... extract with ES Explorer or file manager with root privileges for I compare thats files with my firmwares
all files ok... ever B209 Android M / EMUI 4 but my system is running you ROM
thank you (sorry for my bad bad english )
Click to expand...
Click to collapse
I don't own a P8 Max.

ajsmsg78 said:
I don't own a P8 Max.
Click to expand...
Click to collapse
OMG ... ...

OberonMX said:
OMG ... ...
Click to expand...
Click to collapse
You can flash back the stock rom by downloading the stock firmware for your model and flashing the boot, cache, cust, recovery and system in fastboot.

ajsmsg78 said:
You can flash back the stock rom by downloading the stock firmware for your model and flashing the boot, cache, cust, recovery and system in fastboot.
Click to expand...
Click to collapse
C:\cwm\F>fastboot.exe flash boot BOOT.img
target reported max download size of 471859200 bytes
sending 'boot' (23548 KB)...
OKAY [ 0.754s]
writing 'boot'...
OKAY [ 0.591s]
finished. total time: 1.350s
C:\cwm\F>fastboot.exe flash cache CACHE.img
target reported max download size of 471859200 bytes
sending 'cache' (6248 KB)...
OKAY [ 0.202s]
writing 'cache'...
OKAY [ 0.088s]
finished. total time: 0.295s
C:\cwm\F>fastboot.exe flash cust CUST.img
target reported max download size of 471859200 bytes
sending 'cust' (112482 KB)...
OKAY [ 3.574s]
writing 'cust'...
OKAY [ 1.494s]
finished. total time: 5.070s
C:\cwm\F>fastboot.exe flash recovery RECOVERY.img
target reported max download size of 471859200 bytes
sending 'recovery' (31836 KB)...
OKAY [ 1.013s]
writing 'recovery'...
OKAY [ 0.771s]
finished. total time: 1.792s
C:\cwm\F>fastboot.exe flash system SYSTEM.img
target reported max download size of 471859200 bytes
sending sparse 'system' (453656 KB)...
OKAY [ 15.271s]
writing 'system'...
OKAY [ 5.953s]
sending sparse 'system' (459935 KB)...
OKAY [ 15.798s]
writing 'system'...
OKAY [ 6.147s]
sending sparse 'system' (459104 KB)...
OKAY [ 15.640s]
writing 'system'...
OKAY [ 6.014s]
sending sparse 'system' (450826 KB)...
OKAY [ 15.448s]
writing 'system'...
OKAY [ 5.906s]
sending sparse 'system' (431159 KB)...
OKAY [ 14.581s]
writing 'system'...
OKAY [ 5.614s]
finished. total time: 851.566s
C:\cwm\F>
C:\cwm\F>fastboot reboot
rebooting...
finished. total time: 0.123s
not fix error... I flash B011 FIRM,
can't flash modem.img via fastboot something .. wrong in EFI scheme partition ? ... can't flash any .img from update.app

OberonMX said:
C:\cwm\F>fastboot.exe flash boot BOOT.img
target reported max download size of 471859200 bytes
sending 'boot' (23548 KB)...
OKAY [ 0.754s]
writing 'boot'...
OKAY [ 0.591s]
finished. total time: 1.350s
C:\cwm\F>fastboot.exe flash cache CACHE.img
target reported max download size of 471859200 bytes
sending 'cache' (6248 KB)...
OKAY [ 0.202s]
writing 'cache'...
OKAY [ 0.088s]
finished. total time: 0.295s
C:\cwm\F>fastboot.exe flash cust CUST.img
target reported max download size of 471859200 bytes
sending 'cust' (112482 KB)...
OKAY [ 3.574s]
writing 'cust'...
OKAY [ 1.494s]
finished. total time: 5.070s
C:\cwm\F>fastboot.exe flash recovery RECOVERY.img
target reported max download size of 471859200 bytes
sending 'recovery' (31836 KB)...
OKAY [ 1.013s]
writing 'recovery'...
OKAY [ 0.771s]
finished. total time: 1.792s
C:\cwm\F>fastboot.exe flash system SYSTEM.img
target reported max download size of 471859200 bytes
sending sparse 'system' (453656 KB)...
OKAY [ 15.271s]
writing 'system'...
OKAY [ 5.953s]
sending sparse 'system' (459935 KB)...
OKAY [ 15.798s]
writing 'system'...
OKAY [ 6.147s]
sending sparse 'system' (459104 KB)...
OKAY [ 15.640s]
writing 'system'...
OKAY [ 6.014s]
sending sparse 'system' (450826 KB)...
OKAY [ 15.448s]
writing 'system'...
OKAY [ 5.906s]
sending sparse 'system' (431159 KB)...
OKAY [ 14.581s]
writing 'system'...
OKAY [ 5.614s]
finished. total time: 851.566s
C:\cwm\F>
C:\cwm\F>fastboot reboot
rebooting...
finished. total time: 0.123s
not fix error... I flash B011 FIRM,
can't flash modem.img via fastboot something .. wrong in EFI scheme partition ? ... can't flash any .img from update.app
Click to expand...
Click to collapse
After you flash those img files and the phone boots, go into settings and do a factory reset. After the reset finishes and the phone boots, then you need to do a dload (put the update.app from the B011 in a dload folder on your internal storage) and go to settings, updater and do a local update. It should see the file and you can do the update. This will flash everything including the B011 radio, modem, etc. The key is to fastboot flash to B011 then do the dload method to B011 so all the things that you can't flash in fastboot get flashed through the dload method.

ajsmsg78 said:
After you flash those img files and the phone boots, go into settings and do a factory reset. After the reset finishes and the phone boots, then you need to do a dload (put the update.app from the B011 in a dload folder on your internal storage) and go to settings, updater and do a local update. It should see the file and you can do the update. This will flash everything including the B011 radio, modem, etc. The key is to fastboot flash to B011 then do the dload method to B011 so all the things that you can't flash in fastboot get flashed through the dload method.
Click to expand...
Click to collapse
I upgrade from B011 to B029 via update app all is ok but not fix my error
... I have BALONG ??? , that way I can write my IMEI on the device ?? Thank you

OberonMX said:
I upgrade from B011 to B029 via update app all is ok but not fix my error
... I have BALONG ??? , that way I can write my IMEI on the device ?? Thank you
Click to expand...
Click to collapse
I'm really not sure, I've never seen that error before.

hi
do you know somewhere huawei phones KIRIN saves contents of NVM and IMEI file in root / ?
I think what the upgrade erase these files and I need restore the imei, do it with Xposed IMEI changer but not fix the trouble
thank you

Help flashing TWRP

Hi guys!
I don't seem to be able to flash TWRP 3.3.1 onto my pie phone. From Linux, I get the following:
Code:
:$ fastboot flash recovery ./recovery-TWRP-3.3.1-0602-REDMI6-CN-wzsx150.img
target reported max download size of 134217728 bytes
sending 'recovery' (65536 KB)...
OKAY [ 3.554s]
writing 'recovery'...
OKAY [ 0.942s]
finished. total time: 4.496s
The phone doesn't even blink. If I manually reboot it, nothing has happened. If I get to the recovery menu, I get the MI-Recovery 3.0.
What am I doing wrong? How should I be doing it?
Thanks!

To reboot to recovery : vol+ and power twice

I am stuck with the same problem. Is there any way to resize recovery partition? Or could someone send me stock recovery? Thx
EDIT: I managed to fix. Russian TWRP from 4PDA works.

timonoj said:
Hi guys!
I don't seem to be able to flash TWRP 3.3.1 onto my pie phone. From Linux, I get the following:
Code:
:$ fastboot flash recovery ./recovery-TWRP-3.3.1-0602-REDMI6-CN-wzsx150.img
target reported max download size of 134217728 bytes
sending 'recovery' (65536 KB)...
OKAY [ 3.554s]
writing 'recovery'...
OKAY [ 0.942s]
finished. total time: 4.496s
The phone doesn't even blink. If I manually reboot it, nothing has happened. If I get to the recovery menu, I get the MI-Recovery 3.0.
What am I doing wrong? How should I be doing it?
Thanks!
Click to expand...
Click to collapse
Kindly ensure that you are using the correct device image. If you flash the wrong image/other device image then it will always boot in mi recovery 3.0.
Here is the link : Xiaomi Redmi 6 (twrp.me)

After unlocking, "The system has been destroyed"...but can access via fastboot

I was able to get the device unlocked successfully, but now I'm in a bootloop.
When I run fastboot, I can try to flash a recovery ROM, but it shows:
PS D:\temp\xiaomi\[email protected]_1> fastboot flash recovery .\recovery.img
target reported max download size of 805306368 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.545s]
writing 'recovery'...
OKAY [ 0.359s]
finished. total time: 1.907s
Click to expand...
Click to collapse
...and then it just keeps bootlooping.
Do I have to flash a specific recovery? Do I need to (somehow) get back to a stock, locked ROM? (I'm unable to download the ROMs from here, so if anyone has hints as to where to get the stock ROMs, I'd appreciate it!)