Guys i really wanna try this rom!
But which commands do i have to use to install it? I know that i have to do "fastboot flash boot boot.img" etc.
I tried to install once but it got stuck sending system (fastboot flash system system.img).
What do i do wrong?
Anyone with an input?
Do twrp backup first.
fastboot -S 256M flash boot boot.img
fastboot -S 256M flash system system.img
fastboot -S 256M flash userdata userdata.img
Related
Hi all,
I'm installing CM10.1 on a TF201. Extracting the rom.zip shows there's a boot.blob and a boot.img. I've fastboot'd the boot.img, and can boot into CM fine.
What does the boot.blob provide, do I need to flash it, and if so, does the command need a -i 0x0b05 argument? I've seen other threads which state that the command should be:
Code:
fastboot flash boot -i 0x0b05 boot.blob
rather than just
Code:
fastboot flash boot boot.blob
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.
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!
I made a not-so-smart-decision and tried to update the most recent OTA via Flashfire.
Probably I took a wrong path in Flashfire or missed an important option. However, this happened:
Code:
…
FileNotFoundException: /dev/block/platform/624000.ufshc/by-name/… (Read-only file system)
…
Rebooting...
Error have been detected. Delaying reboot for three minutes in the hope you'll notice. You could reboot manually, of course
And since then the mobile just reboots into Recovery / TWRP.
I tried to reset it completely now via
sudo fastboot flash boot boot.img
sudo fastboot flash oem oem.img
sudo fastboot flash system system.img_sparsechunk.0
sudo fastboot flash system system.img_sparsechunk.1
sudo fastboot flash system system.img_sparsechunk.2
sudo fastboot flash system system.img_sparsechunk.3
sudo fastboot flash system system.img_sparsechunk.4
sudo fastboot flash system system.img_sparsechunk.5
sudo fastboot flash system system.img_sparsechunk.6
sudo fastboot flash system system.img_sparsechunk.7
sudo fastboot flash system system.img_sparsechunk.8
sudo fastboot flash system system.img_sparsechunk.9
sudo fastboot flash system system.img_sparsechunk.10
sudo fastboot flash system system.img_sparsechunk.11
sudo fastboot flash system system.img_sparsechunk.12
Click to expand...
Click to collapse
and the image RETBR/XT1650-03_GRIFFIN_RETBR_NPL25.86-30_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip (I have the GER/EU model but the last time I had a problem with the device people recommended the BR image).
This doesn't help so far. And I don't know why. I also resetted cache, userdata etc.
I didn't flash recovery so far because I fear to brick the Moto Z totally.
Nothing helps so far. It still boots into TWRP.
Does anyone have any idea what I could to to rescue the mobile?
Thank you in advance and have a nice day
EDIT: Okay, flashing the stock recovery helped.
How can I mark this thread as solved?
EDIT 2: As I flashed the (old) stock ROM now, I thought OTAs should be possible but they result in an error. But I don't have TWRP or root installed yet. Do you have any idea why that could be?
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