Hello. I wanted to flash a stock ROM on my Xiaomi Mi3 (Not Mi3W) and I downloaded an official stock ROM and flashed it using Fastboot.
Here's where I think I messed up. I used the "fastboot erase userdata" on the phone and when it booted up, The system storage is showing fine when I go to settings > storage but the internal storage is showing up as 0.00b and I cannot install any applications.
I've tried reflashing but nothing is working. Any ideas on how I can get it to work? Thanks.
Try to flash again with fastboot but with following comands:
Enter the following commands below by order:
fastboot erase cache
fastboot erase userdata
fastboot erase system
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot-bootloader
boot.img ,recovery.img and system.img it should be inside your stock firmware.
Teddy Lo said:
Try to flash again with fastboot but with following comands:
Enter the following commands below by order:
fastboot erase cache
fastboot erase userdata
fastboot erase system
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot-bootloader
boot.img ,recovery.img and system.img it should be inside your stock firmware.
Click to expand...
Click to collapse
After much Googling, I was finally able to 'reset' the whole android partition system by flashing a CWM recovery, booting into it, and using ADB to fix it all.
Thank you for bothering to reply my at all. You're amazing.
You Welcome
Related
Hello,
I have problem with flashing stock firmware on my atrix 4g.
RSD -lite return error:
Failed flashing process. Unable to retrieve interface handle. (0x7027).
Thats happens when I would go back to stock firmware from CM7.
Before running RSD flashing, I was execute following fastboot commands:
fastboot erase boot
fatsboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase osh
fastboot erase logo
fastboot erase radio
Before 2-3 times mentioned above method without erase radio commands not return any errors with RSD flashing. And have not any problem.
Can anybody advice and help me ?
Thanks for help and advice.
Solved
alcpis said:
Hello,
I have problem with flashing stock firmware on my atrix 4g.
RSD -lite return error:
Failed flashing process. Unable to retrieve interface handle. (0x7027).
Thats happens when I would go back to stock firmware from CM7.
Before running RSD flashing, I was execute following fastboot commands:
fastboot erase boot
fatsboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase osh
fastboot erase logo
fastboot erase radio
Before 2-3 times mentioned above method without erase radio commands not return any errors with RSD flashing. And have not any problem.
Can anybody advice and help me ?
Thanks for help and advice.
Click to expand...
Click to collapse
Solved !
1. Copy Radio image (baseband) to the folder where located fastboot.
2. Power on phone and select fastboot
3. execute: fastboot flash radio bp.img, Where bp.img baseband image files
4. execute: fastboot reboot
5. Phone automatically boot on the android recovery mode
6. Wipe userdata/cache
7. Reload in RSD mode
8. on the RSD lite browse appropriate .sbf file and puch Start
Thats all.
Thanks.
alcpis said:
Solved !
1. Copy Radio image (baseband) to the folder where located fastboot.
2. Power on phone and select fastboot
3. execute: fastboot flash radio bp.img, Where bp.img baseband image files
4. execute: fastboot reboot
5. Phone automatically boot on the android recovery mode
6. Wipe userdata/cache
7. Reload in RSD mode
8. on the RSD lite browse appropriate .sbf file and puch Start
Thats all.
Thanks.
Click to expand...
Click to collapse
Can you be a bit more specific on syntax used. I have the atrix baseband img in the fastboot folder and all is good but I get a "cannot load" error. The name of the baseband img file is baseband_OTA.img So with that in mind how would my commands look? I have typed fastboot flash radio baseband.img. I get the error saying it cannot load the file.
hi
so i was trying to install a custom rom on my phone because i couldnt root it with supersu.zip and twrp but i accidentaly wiped internal storage with twrp and when i try to install the custom rom although it says its successful it doesnt copy the files and says"unmount of system directory failed no such voulume",im really confused now, what can i do? any help is appreciated
also the internal storage is always empty and nothing gets copied in it
macszxc said:
hi
so i was trying to install a custom rom on my phone because i couldnt root it with supersu.zip and twrp but i accidentaly wiped internal storage with twrp and when i try to install the custom rom although it says its successful it doesnt copy the files and says"unmount of system directory failed no such voulume",im really confused now, what can i do? any help is appreciated
also the internal storage is always empty and nothing gets copied in it
Click to expand...
Click to collapse
Use a SD card to flash the ROM using TWRP. Also check on TWRP that the internal and external memory are mounted.
Sent from my XT1650 using XDA-Developers mobile app
Or ADB Sideload. Simple stuff
macszxc said:
hi
so i was trying to install a custom rom on my phone because i couldnt root it with supersu.zip and twrp but i accidentaly wiped internal storage with twrp and when i try to install the custom rom although it says its successful it doesnt copy the files and says"unmount of system directory failed no such voulume",im really confused now, what can i do? any help is appreciated
also the internal storage is always empty and nothing gets copied in it
Click to expand...
Click to collapse
Don't panic! As long as you can get to recovery or bootloader you aren't bricked
I would restore to stock and try everything again.
Here's the stock US ROM https://mega.nz/#!vtVmgAoI!J1cZtlRi0FjRHbxIJGA5U8CLx6RwUWQjwrCbjzf_Naw
There's a link around here for stock EU ROM if you need that instead.
Use these commands from an ADB prompt:
fastboot flash partition gpt.bin
fastboot flash motoboot boot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
thx guys it worked with flashing stock rom
macszxc said:
thx guys it worked with flashing stock rom
Click to expand...
Click to collapse
I went through the exact same thing, wipe the whole system out, couldn't reboot even after flashing another ROM, then I figured, the boot.img must have gone missing, so I just fastboot flash boot boot.img (the one from within the stock ROM), then the phone booted
beaubin said:
I went through the exact same thing, wipe the whole system out, couldn't reboot even after flashing another ROM, then I figured, the boot.img must have gone missing, so I just fastboot flash boot boot.img (the one from within the stock ROM), then the phone booted
Click to expand...
Click to collapse
I'm ever more of the opinion that our Z is a device very hard to seriously brick...
Prfndhatrdofman said:
Don't panic! As long as you can get to recovery or bootloader you aren't bricked
I would restore to stock and try everything again.
Here's the stock US ROM https://mega.nz/#!vtVmgAoI!J1cZtlRi0FjRHbxIJGA5U8CLx6RwUWQjwrCbjzf_Naw
There's a link around here for stock EU ROM if you need that instead.
Use these commands from an ADB prompt:
fastboot flash partition gpt.bin
fastboot flash motoboot boot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Click to expand...
Click to collapse
Hello, can you give me the EU stock rom, and please for god's sake don't give me this file factory link because this website is downloading slower to force me to buy their premium ****, thanks.
Ok, i have unlocked bootloader, installed this rom https://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-versions-t3506342, added twrp via fastboot, rooted and so on.
Everything worked like a charm.
Than yesterday I got this update notification (from nplp 25.86-15 to nplp 25.86 -17-3; something about fixing notification sound - about 500mb). I thought what the hell lets try it - ended up in boot loop to recovery(twrp).
After that I installed this rom (odexed version) https://forum.xda-developers.com/moto-z/development/twrp-ported-to-moto-z-eu-version-t3470920.
Again I tried the update since it restored stock recovery - it went into the process and than reported some error.
Now, no matter what rom I install(those 2 and I tried cm14) phone acts messed up, it freezes and reboots when using it randomly and always reboots when screen goes to sleep 4 about 10 seconds.
I have also tried to install mm rom via twrp but ended up in recovery loop.
Any help is highly appreciated..
You need to flash back full stock ROM for your device. Had same issue. But that's if you are downgradable to MM roms
tafarelli said:
Ok, i have unlocked bootloader, installed this rom https://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-versions-t3506342, added twrp via fastboot, rooted and so on.
Everything worked like a charm.
Than yesterday I got this update notification (from nplp 25.86-15 to nplp 25.86 -17-3; something about fixing notification sound - about 500mb). I thought what the hell lets try it - ended up in boot loop to recovery(twrp).
After that I installed this rom (odexed version) https://forum.xda-developers.com/moto-z/development/twrp-ported-to-moto-z-eu-version-t3470920.
Again I tried the update since it restored stock recovery - it went into the process and than reported some error.
Now, no matter what rom I install(those 2 and I tried cm14) phone acts messed up, it freezes and reboots when using it randomly and always reboots when screen goes to sleep 4 about 10 seconds.
I have also tried to install mm rom via twrp but ended up in recovery loop.
Any help is highly appreciated..
Click to expand...
Click to collapse
i have the exactly same situation with my phone please help... i flashed MM rom but it didn't help it keeps rebooting every 5-10 minutes for no reason... will cyanogenmod 14.1 from this forum help?
Ok I have tried.
I flashed http://www.filefactory.com/file/6ht...ubsidy-DEFAULT_regulatory-03_CFC_EMEA.xml.zip using following commands:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash system system.img_sparsechunk.14
fastboot flash system system.img_sparsechunk.15
fastboot flash system system.img_sparsechunk.16
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 oem config carrier T-2
fastboot oem fb_mode_clear
Phone booted to mm stock (build number MPL 24.246-17) but I already had one reboot few minutes after.
Any suggestions?
kaxuna1 said:
i have the exactly same situation with my phone please help... i flashed MM rom but it didn't help it keeps rebooting every 5-10 minutes for no reason... will cyanogenmod 14.1 from this forum help?
Click to expand...
Click to collapse
I tried with cm but it's not helping.
Phone is stable so far after that initial self-reboot; I'll wait 4 couple hours and if it stays stable returning to n version because mm is too big of a downgrade.
If it continues rebooting, well I guess I'll just bang my head on the wall few times) cause I am out of ideas..
tafarelli said:
Phone is stable so far after that initial self-reboot; I'll wait 4 couple hours and if it stays stable returning to n version because mm is too big of a downgrade.
If it continues rebooting, well I guess I'll just bang my head on the wall few times) cause I am out of ideas..
Click to expand...
Click to collapse
i dont know what to do anymore i tried CM and it keeps rebooting...
do you have any more suggestions?
kaxuna1 said:
i dont know what to do anymore i tried CM and it keeps rebooting...
do you have any more suggestions?
Click to expand...
Click to collapse
Did you try what I posted above?
I have flashed nougat again after that and had one random reboot since. Don't like the fact that reboot happened but otherwise it feels stable and smooth.
Incomparable from what it was before-phone was unusable..
Ok now I have fully functional and stable Moto Z with rooted nougat (EU version).
Here is the receipt:
Download:
-(1) https://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-versions-t3506342 (mm rom)
-(2) https://mega.nz/#!ktxzwQrZ!UVHWD2B_ngkk7SiD9bWfVUhIfXkkdjpb2mgQhTrZIR8 (twrp img)
-(3) https://drive.google.com/file/d/0B7t82wiSkgOSdE5pbkVoZmNnLWM/view?usp=sharing (nougat modem)
-(4) https://mega.nz/#!5k5nCJAT!PUYLbJDGGyq3eZJMe38cl4tXG2vaXLIIID-wCdDjcYg (nougat rom)
-(5) superuser-r259.zip from https://superuser.phh.me/ (root zip)
Than from(1) fastboot as follows:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash system system.img_sparsechunk.14
fastboot flash system system.img_sparsechunk.15
fastboot flash system system.img_sparsechunk.16
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 oem fb_mode_clear
Boot up and put (4) and (5) to internal storage (idealy to sd card or usb via otg cable).
Than fastboot twrp from (2): fastboot flash recovery TWRP-Moto-Z.img
Than fastboot modem from (3): fastboot flash modem NON-HLOS.bin
Enter twrp recovery, advanced wipe dalvik, data, cache, format data; install n rom from (4); install root zip from (5)
Reboot
I have also freezed Motorola Update Services via Root Freezer Pro so that I don't get bothered with that type of potential problems in future.
Also, if you want to get rid of that annoying warning message (unlocked bootloader) upon booting download:
https://forum.xda-developers.com/attachment.php?attachmentid=3927285&d=1478365739
https://forum.xda-developers.com/attachment.php?attachmentid=3484630&d=1443097711
Unzip both on your pc, drag logo.bin onto MotoLogo_Injectorv1.1.bat, connect your phone in fastboot mode and follow onscreen instructions.
Hello @tafarelli what versión bootloader have your ?? Very thanks
Downgrade the Nougat at Mm ?
Regards
I never upgraded to nougat through OTA but from fastbooting this:
https://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-versions-t3506342
so I believe I still have mm bootloader.
If you have n bootloader than I guess(don't know) you will have to wait 4 stock nougat zip equivalent to (1) mm posted above..
tafarelli said:
Did you try what I posted above?
I have flashed nougat again after that and had one random reboot since. Don't like the fact that reboot happened but otherwise it feels stable and smooth.
Incomparable from what it was before-phone was unusable..
Click to expand...
Click to collapse
Yes I tried and it's been a 12 hours without reboot so thanks friend you saved me... I will try that nougat method you posted bello ???
---------- Post added at 11:45 PM ---------- Previous post was at 11:40 PM ----------
tafarelli said:
Ok now I have fully functional and stable Moto Z with rooted nougat (EU version).
Here is the receipt:
Download:
-(1) https://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-versions-t3506342 (mm rom)
-(2) https://mega.nz/#!ktxzwQrZ!UVHWD2B_ngkk7SiD9bWfVUhIfXkkdjpb2mgQhTrZIR8 (twrp img)
-(3) https://drive.google.com/file/d/0B7t82wiSkgOSdE5pbkVoZmNnLWM/view?usp=sharing (nougat modem)
-(4) https://mega.nz/#!5k5nCJAT!PUYLbJDGGyq3eZJMe38cl4tXG2vaXLIIID-wCdDjcYg (nougat rom)
-(5) superuser-r259.zip from https://superuser.phh.me/ (root zip)
Than from(1) fastboot as follows:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash system system.img_sparsechunk.14
fastboot flash system system.img_sparsechunk.15
fastboot flash system system.img_sparsechunk.16
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 oem fb_mode_clear
Boot up and put (4) and (5) to internal storage (idealy to sd card or usb via otg cable).
Than fastboot twrp from (2): fastboot flash recovery TWRP-Moto-Z.img
Than fastboot modem from (3): fastboot flash modem NON-HLOS.bin
Enter twrp recovery, advanced wipe dalvik, data, cache, format data; install n rom from (4); install root zip from (5)
Reboot
I have also freezed Motorola Update Services via Root Freezer Pro so that I don't get bothered with that type of potential problems in future.
Also, if you want to get rid of that annoying warning message (unlocked bootloader) upon booting download:
https://forum.xda-developers.com/attachment.php?attachmentid=3927285&d=1478365739
https://forum.xda-developers.com/attachment.php?attachmentid=3484630&d=1443097711
Unzip both on your pc, drag logo.bin onto MotoLogo_Injectorv1.1.bat, connect your phone in fastboot mode and follow onscreen instructions.
Click to expand...
Click to collapse
??????
tafarelli said:
I never upgraded to nougat through OTA but from fastbooting this:
https://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-versions-t3506342
so I believe I still have mm bootloader.
If you have n bootloader than I guess(don't know) you will have to wait 4 stock nougat zip equivalent to (1) mm posted above..
Click to expand...
Click to collapse
Hello correct I have bootloader Nougat I do not understand what it means to expect 4 stcok nougat zip equivalent to 1 MM postado but back many thanks
regards
iron maiden said:
Hello correct I have bootloader Nougat I do not understand what it means to expect 4 stcok nougat zip equivalent to 1 MM postado but back many thanks
regards
Click to expand...
Click to collapse
It means when they put link for n factory image here
http://www.androidsage.com/2016/12/...ce-android-7-0-nougat-ota-and-factory-images/
(or elshewhere)
than you download it and fastboot stock n rom to repair your (I presume) damaged device.
tafarelli said:
It means when they put link for n factory image here
http://www.androidsage.com/2016/12/...ce-android-7-0-nougat-ota-and-factory-images/
(or elshewhere)
than you download it and fastboot stock n rom to repair your (I presume) damaged device.
Click to expand...
Click to collapse
Hello my Moto z is in nougat but I was wondering if you had bootloader Nougat and could return to forgive MM if I made you believe that it was in brick my phone sorry for my English there is no image factory of the last version? NPL25.86-17-3 " I installed this by adb sideload but I like to install the whole image thanks
regards
Hi guys, I've tried all the threads so far and have got no where. I unlocked my device and flashed a custom rom, that worked fine. I then noticed no way to go back to stock so I tried the odexed version with no luck. Now any rom I flash does not boot, just loops back to twrp. I would like to get as close to stock as possible even if it's another region. Has anyone had any luck on getting their phones booting after this?
I've tried flashing stock firmware from 6.0.1 then flashing ota through side load
Flashing other countries firmware (which always ends in fail messages)
I've tried multiple rom from the forum which just loop.
I've spent about 6 hours trying different combinations of recovery, boot and other images with no luck.
Any help is appreciated.
Sent from my iPhone using Tapatalk
criptix said:
Hi guys, I've tried all the threads so far and have got no where. I unlocked my device and flashed a custom rom, that worked fine. I then noticed no way to go back to stock so I tried the odexed version with no luck. Now any rom I flash does not boot, just loops back to twrp. I would like to get as close to stock as possible even if it's another region. Has anyone had any luck on getting their phones booting after this?
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
I have gotten stuck with bootloops a couple times now, for me re-flashing a backup or custom rom or custom kernel didn't fix it either. Keep in mind that you cannot go back to 6.0.1 once you have flashed 7.0, the bootloader won't allow it. I have had to flash back to a stock firmware from https:// firmware.center/firmware/Motorola/Moto%20Z/Stock/XT1650-03/ (remove the space after https:// ) and re-fastboot flash TWRP, re-root, and restore my Titanium Backups to get going again.
It's extremely helpful if you create a servicefile.bat to flash all the firmware parts in the right order. This is the one I made for flashing the RETMX 7.0 image (the main difference I noticed between different firmwares from that link is the number of sparsechunks, so add or delete lines as necessary. I'm sure all this info is available elsewhere, but I didn't manage to find it all in one shot. So I figured I would post it to help others out that are in the same boat. Also note that even though you are re-flashing the bootloader.img it does not re-lock your bootloader.
Code:
echo off
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash system system.img_sparsechunk.14
fastboot flash system system.img_sparsechunk.15
fastboot flash system system.img_sparsechunk.16
fastboot flash oem oem.img
fastboot erase carrier
fastboot oem fb_mode_clear
pause
fastboot reboot
exit
Copy the above text and paste it into a new text file and change the name to "servicefile.bat" without quotes (not servicefile.bat.txt), and drop it in with the extracted firmware files. Then either copy-paste your adb and fastboot files into that folder or drop all that folder's contents into your Users/*YOURNAME*/App Data/Local/Android/sdk/platform-tools/ folder. Or better yet, add "%USERPROFILE%\AppData\Local\Android\sdk\platform-tools" to your Path in your system's Environment Variables. The latter will make adb and fastboot work from any command prompt window, then you can just press shift+right-click in the folder that already has the firmware files and choose "Open command window here" and then just type servicefile.bat and press enter. Hope this helps! Good Luck and Happy Flashing!
HippieFlasher said:
I have gotten stuck with bootloops a couple times now, for me re-flashing a backup or custom rom or custom kernel didn't fix it either. Keep in mind that you cannot go back to 6.0.1 once you have flashed 7.0, the bootloader won't allow it. I have had to flash back to a stock firmware from https:// firmware.center/firmware/Motorola/Moto%20Z/Stock/XT1650-03/ (remove the space after https:// ) and re-fastboot flash TWRP, re-root, and restore my Titanium Backups to get going again.
It's extremely helpful if you create a servicefile.bat to flash all the firmware parts in the right order. This is the one I made for flashing the RETMX 7.0 image (the main difference I noticed between different firmwares from that link is the number of sparsechunks, so add or delete lines as necessary. I'm sure all this info is available elsewhere, but I didn't manage to find it all in one shot. So I figured I would post it to help others out that are in the same boat. Also note that even though you are re-flashing the bootloader.img it does not re-lock your bootloader.
Code:
echo off
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash system system.img_sparsechunk.14
fastboot flash system system.img_sparsechunk.15
fastboot flash system system.img_sparsechunk.16
fastboot flash oem oem.img
fastboot erase carrier
fastboot oem fb_mode_clear
pause
fastboot reboot
exit
Copy the above text and paste it into a new text file and change the name to "servicefile.bat" without quotes (not servicefile.bat.txt), and drop it in with the extracted firmware files. Then either copy-paste your adb and fastboot files into that folder or drop all that folder's contents into your Users/*YOURNAME*/App Data/Local/Android/sdk/platform-tools/ folder. Or better yet, add "%USERPROFILE%\AppData\Local\Android\sdk\platform-tools" to your Path in your system's Environment Variables. The latter will make adb and fastboot work from any command prompt window, then you can just press shift+right-click in the folder that already has the firmware files and choose "Open command window here" and then just type servicefile.bat and press enter. Hope this helps! Good Luck and Happy Flashing!
Click to expand...
Click to collapse
Dude, you are awesome. Worked like a charm. Was missing fastboot getvar max-sparse-size andbfastboot oem fb_mode_set plus I was flashing the modem after the chunks. Thanks again!
Sent from my iPhone using Tapatalk
Anytime! Glad I could help!
Hello there! I unlock my bootloader and install twrp in my redmi 6 pro(sakura). Then i install havoc os and it was running completely fine . Then i flash camera to api & dm verity by twrp. After flashing and rebooting, my phone stuck on havoc animation after redmi sign . Then i wipe everything and then i flash lineage os and it also stuck on lineage animation. Whichever os i flash, it stuck on that Animation. It's non root device. Still it stuck on os animation. How to solve? Please Help
connect to pc via usb
open cmd window in adb and fastboot folder
reboot your device to fastboot mode using hardware keys
type fastboot devices to test connection
then download your stock rom from the internet
extract it
enterthe firmware file
copy recovery.img system.img cache.img userdata.img and boot.img
paste them in the adb folder
now in cmd window type
fastboot erase boot
fastboot flash boot boot.img
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot erase userdata
fastboot flash userdata userdata.img
fastboot erase cache
fastboot flash cache cache.img
fastboot erase system
fastboot flash system system.img
and you're all done, your phone should be able to start now
brother i am very new . adb and fastboot folder means ? is it platform tools folder
brother i am very new .adb and fastboot folder means ? is it platform tools folder ?
narwhhal27 said:
connect to pc via usb
open cmd window in adb and fastboot folder
reboot your device to fastboot mode using hardware keys
type fastboot devices to test connection
then download your stock rom from the internet
extract it..
enterthe firmware file
copy recovery.img system.img cache.img userdata.img and boot.img
paste them in the adb folder
now in cmd window type
fastboot erase boot
fastboot flash boot boot.img
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot erase userdata
fastboot flash userdata userdata.img
fastboot erase cache
fastboot flash cache cache.img
fastboot erase system
fastboot flash system system.img
and you're all done, your phone should be able to start now
Click to expand...
Click to collapse