Database Develop

Flashing Issues/Permission Issues

A few days ago I got my Atrix HD and immediately rooted and subsequently unlocked the bootloader. Later I successfully flashed EcHoFiiVe's paranoidAndroid port... I didn't really like it because of the aspect ratio (too tiny) so I tried to flash back to a stock ROM. I lost and later accidentally deleted the backup I had made of the stock ROM that came on the device so that is now out of the question but for some reason, no matter what I do, I can't make changes to /system from the recovery or from the bootloader using fastboot commands. I've tried inputing
Code:
fastboot erase system -w
and it told me that I didn't have sufficient permissions and that the command failed. Therein lies my problem. Fortunately, I have a runnable backup (PA) I just really wish to try something different and the device is adamantly against the idea. According to the bootloader the device is unlocked with status code 3. Any help will be greatly appreciated!

read this
http://forum.xda-developers.com/showthread.php?t=2226527

frog1982 said:
read this
http://forum.xda-developers.com/showthread.php?t=2226527
Click to expand...
Click to collapse
I've read through that and I can now see a line that I missed that said that it was a common issue for that particular command to not work but I still don't know what to do about my inability to flash a different ROM. I have tried to mount /system before flashing and I've tried wiping /system using the recovery before flashing, all without avail. Do you have any advice on how to wipe the system partition?

you do not have to wipe it just fastboot flash Mex retail to overwrite it and you will be starting over.

frog1982 said:
you do not have to wipe it just fastboot flash Mex retail to overwrite it and you will be starting over.
Click to expand...
Click to collapse
to be clear, are you saying I can just do this:
Extract the zip
Open a terminal to the extracted zips directory
Reboot into fastboot
Type the following commands in this order
Code:
fastboot flash boot boot.img
fastboot flash devtree device_tree.bin
fastboot flash system system.img
fastboot -w
fastboot reboot

sparkplugDev said:
to be clear, are you saying I can just do this:
Extract the zip
Open a terminal to the extracted zips directory
Reboot into fastboot
Type the following commands in this order
Code:
fastboot flash boot boot.img
fastboot flash devtree device_tree.bin
fastboot flash system system.img
fastboot -w
fastboot reboot
Click to expand...
Click to collapse
yes but make sure you also have the snap-fastboot files in the folder you are working in or in your path

[GUIDE] Update to Lollipop without losing apps/settings

It is assumed that you are on Kitkat with unlocked bootloader and rooted. Here is what I did (this is on Linux, but for Windows the instructions remain the same):
0. Backup first.
a. Use TWRP to do a full back up of your current ROM. Use 2.8.2.0 from Luca here: http://forum.xda-developers.com/mot...recovery-twrp-2-8-2-0-touch-recovery-t2979149
b. Use titanium backup to back up all your apps and their data.
Just as a precaution. This guide will keep your data and apps intact...
1. Get the Lollipop OTA
a. After the OTA download was complete, I kept on postponing the install. The downloaded ZIP was in /cache folder, which I could read when rooted. So, the first step was to adb pull it onto my PC to save it for eternity.
OR
b. If you don't have the OTA in your cache folder, download it from forums here. Left as an exercise for the reader....
2. Go back to stock Kitkat as much as you can without destroying the data partition and losing apps and settings.
a. Get your current stock ROM and unzip it in a folder
b. adb reboot bootloader, and change directory to the folder where you unzipped the stock files.
c. restore to stock without losing the /data
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
3. Sideload the OTA ZIP.
a. adb reboot recovery - this will put you into stock recovery. Press Vol UP while Power is pressed. It will be give you a menu. Vol Down to "Install from ADB" and Power (or Vol Up, don't remember, I think this changed with Lollipop) to select.
b. Once the phone is in sideload mode ("Install from ADB" mode), do 'adb sideload <ZIP NAME>'
c. Wait....wait some more. It will take quite a bit.
4. Boot back. It should start upgrading your apps you had before the upgrade with "Android upgrading..." dialog.
5. Go on and try other OTA updates (which don't work right now). Or load your favorite root method and/or TWRP, and create another backup point for your Lollipop install with all your apps and settings.
For me, I am at 22.11.6 (5.0.0 with 2 OTAs missing), rooted and TWRP. Once new OTAs arrive, I will do the same thing again...

Wow, great !
It worked like a charm for me, I even stopped before 3) to reboot and do the ota automatically, succesfully and I didn't lose any data.
Fyi I hat a rooted/xposed xt1032 running 4.4.4 and I installed the 5.0.1 OTA this way (210.12.40 to 220.27.1).
Thanks a lot !

[Q] Creating Backup: motoboot.img & gpt.bin from another Firmware? Nextel Mex XT1064

[Q] Creating Backup: motoboot.img & gpt.bin from another Firmware? Nextel Mex XT1064
Hi everyone! I need your help! I'm dumping the Firmware of my XT1064 Nextel México to share it with everyone in the community. I dumped almost all the partitions of my device, excluding "motoboot" (In another firmwares Dumps is motoboot.img) which I can not find it, and the "system" partition, which I can not flash it in the device because the file (system.img) is too big and I don't know how to divide it. Finally, I want to know if I can use the motoboot.bin and the gpt.bin from another firmware like the XT1064 Retail from USA.
Sorry for my bad english! I hope someone can help me!
Here I put the files I've already uploaded! USE AT YOUR OWN RISK!
https://mega.co.nz/#F!VMQHFJxB!7aSAkqkYI1SX7GI_S5yItw
USE AT YOUR OWN RISK! YOU MUST HAVE UNLOCKED BOOTLOADER
How-to:
-Copy all the files from the IMG's And BIN folder and the TWRP Recovery "twrp-2.8.3.0-titan.img" to your "platform-tools" folder
-Copy the TWRP Backup to your SD Card Backup's folder
Enter to fastboot in your device and run this commands in order (I exclude "fastboot flash partition gpt.bin" and
"fastboot flash motoboot motoboot.img")
fastboot flash logo logo.bin <--- From Retail US Firmware
fastboot flash boot boot.img <--- From XT1064 Nextel México
fastboot flash recovery twrp-2.8.3.0-titan.img <--- Flash TWRP Recovery include in the Link
-Enter to TWRP Recovery using your device, Wipe System/Data/Cache and Restore the System Partition from the Backup.
-Power Off the Device and enter to Fastboot again.
fastboot flash recovery recovery.img <--- Original Recovery from Retail US Firmware
fastboot flash modem NON-HLOS.bin <--- Modem from XT1064 Nextel México
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn <--- From XT1064 Nextel México
fastboot erase cache
fastboot erase userdata

ejsmsupersoyelm said:
Hi everyone! I need your help! I'm dumping the Firmware of my XT1064 Nextel México to share it with everyone in the community. I dumped almost all the partitions of my device, excluding "motoboot" (In another firmwares Dumps is motoboot.img) which I can not find it, and the "system" partition, which I can not flash it in the device because the file (system.img) is too big and I don't know how to divide it. Finally, I want to know if I can use the motoboot.bin and the gpt.bin from another firmware like the XT1064 Retail from USA.
Click to expand...
Click to collapse
Ok Lets just say this clearly 'STOP NOW' CALM DOWN AND LEARN A BIT MORE...... flashing images can and will brick your phone.
'I've dumped all most all the partitions of my device' -- Not really you have made TWPR backup of your Android Partitions (there are many more hidden partitions) some common android partitions are /boot /cache /data /system /recovery. these are the ones normally backed up with TWRP etc. A basic TWRP flashable custom rom can be made of as little as (boot.img, system folder and a META-INFO folder ) zipped up
You are mixing and matching 2 separate Flashing Methods - yes it can be done, but it can Also go badly wrong.
motoboot.img is your bootloader IT IS NOT the same as boot.img
forget flashing anything with fastboot or mfastboot untill you learn more. stick to TWRP backups (full all partitions for you. and just boot and system to share)
you can only upgrade (at moment) your gpt.bin and motoboot.img - so just leave them as they are.

reefuge said:
Ok Lets just say this clearly 'STOP NOW' CALM DOWN AND LEARN A BIT MORE...... flashing images can and will brick your phone.
'I've dumped all most all the partitions of my device' -- Not really you have made TWPR backup of your Android Partitions (there are many more hidden partitions) some common android partitions are /boot /cache /data /system /recovery. these are the ones normally backed up with TWRP etc. A basic TWRP flashable custom rom can be made of as little as (boot.img, system folder and a META-INFO folder ) zipped up
You are mixing and matching 2 separate Flashing Methods - yes it can be done, but it can Also go badly wrong.
motoboot.img is your bootloader IT IS NOT the same as boot.img
forget flashing anything with fastboot or mfastboot untill you learn more. stick to TWRP backups (full all partitions for you. and just boot and system to share)
you can only upgrade (at moment) your gpt.bin and motoboot.img - so just leave them as they are.
Click to expand...
Click to collapse
Yes, I learned a lot in another devices, I'm just Asking if I can use motoboot.img (Bootloader) and the gpt.bin of another variant of my phone... I made a Backup of all the partitions included in the Factory Firmware Images of another Variants (In specific, the Xt1064 from USA and the one of Canada. and the Xt1063 Retail... I don't know if you have checked all the files that I upload, but all dumps that I did are from the ADB method, it's universal, works with every device... I tested all the dumps (fsg.mbn, boot.img, logo.bin, NON-HLOS.bin, recovery.img) in my device and it worked, except the system.img dump, because is too big, And I had the idea of adding the step of the Custom Recovery just to flash System... and then, continue with all the remaining partitions...

ejsmsupersoyelm said:
Yes, I learned a lot in another devices, I'm just Asking if I can use motoboot.img (Bootloader) and the gpt.bin of another variant of my phone... I made a Backup of all the partitions included in the Factory Firmware Images of another Variants (In specific, the Xt1064 from USA and the one of Canada. and the Xt1063 Retail... I don't know if you have checked all the files that I upload, but all dumps that I did are from the ADB method, it's universal, works with every device... I tested all the dumps (fsg.mbn, boot.img, logo.bin, NON-HLOS.bin, recovery.img) in my device and it worked, except the system.img dump, because is too big, And I had the idea of adding the step of the Custom Recovery just to flash System... and then, continue with all the remaining partitions...
Click to expand...
Click to collapse
It's hard to say but motoboot.img and gpt.bin it's normally a one way upgrade only, if you flash newest, it can be hard to go back. Yes the should flash but you wont gain much and may lose OTA updates in future.
So there is no need to flash these for restoring TWRP back ups, I strongly suggest you leave yours alone.
ADB flashing really is just for OTA upgrades and using to get a custom recovery on phone, once you have a custom recovery you can make custom roms to flash from that.
Adb flashes system from OTA as 4 parts that combine into /system folder - so thats why you cant flash 1 big img via adb
again you need to learn how to make a flashable custom rom to use via TWRP, look for a guide there are many.
but i will give you a idea how to do
using your xt1064 mexcio TWRP back up - ALL you need for now is Boot.emmc.win and system.ext4.win nothing else
rename boot.emmc.win to boot.img and change system.ext4.win to system.ext4.tar and find a guide on how to extract the tar to a system folder ( I use cygwin )
then take a meta-info folder from a custom xt1064 rom and adjust the updater-script to work with your rom - zip these 3 files up into your new custom rom.
this is a very simple idea, there are more steps so search for a guide on here

I just need the motoboot.img file, would provide for me?

Help Please !!!

Hello ,
i am new to this fastboot thing because i had galaxy grand and restoring to stock rom was so easy and now i have moto g2 running CM12.1 + TWRP +unlocked bootloader
and now i want to restore to stock 5.0.2 .and restoring to stock will install stock recovery or not?? please tell me step by step instructions .
thanks

Recently i downgraded from cm12.1 to stock. Here is what i did.
Downloaded stock rom from one the xda threads.
Placed in internal storage
Used philiz recovery. Chose 'Clean for a new rom' or something like that.
Installed zip.
Wipe cache partition.

rahul.pipaliya007 said:
Hello ,
i am new to this fastboot thing because i had galaxy grand and restoring to stock rom was so easy and now i have moto g2 running CM12.1 + TWRP +unlocked bootloader
and now i want to restore to stock 5.0.2 .and restoring to stock will install stock recovery or not?? please tell me step by step instructions .
thanks
Click to expand...
Click to collapse
yes if you install stock rom stock recovery will also be installed and this is the link for mfastboot that will be required to flash stock rom http://goo.gl/lTYq4F
YOU WILL NEED A PC OR LAPTOP TO PERFORM THESE OPERATIONS
instructions :
1. download stock rom and mfastboot
2. unzip mfastboot and place it some were in your pc
3. unzip the stock rom and copy all the stuff to mfastboot folder
4. make a backup your internal storage will also be wiped
5. reboot your phone to bootloader mode
6. connect your phone to pc and go to mfastboot folder which you have unzip rom in it and right click mouse button in that folder and hit open command window hear
7. copy the bellow commands in that window one by one you need to hit enter for every each and every command
6.
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe reboot
now your done :laugh: enjoy stock

dj krishna said:
yes if you install stock rom stock recovery will also be installed and this is the link for mfastboot that will be required to flash stock rom http://goo.gl/lTYq4F
YOU WILL NEED A PC OR LAPTOP TO PERFORM THESE OPERATIONS
instructions :
1. download stock rom and mfastboot
2. unzip mfastboot and place it some were in your pc
3. unzip the stock rom and copy all the stuff to mfastboot folder
4. make a backup your internal storage will also be wiped
5. reboot your phone to bootloader mode
6. connect your phone to pc and go to mfastboot folder which you have unzip rom in it and right click mouse button in that folder and hit open command window hear
7. copy the bellow commands in that window one by one you need to hit enter for every each and every command
6.
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe reboot
now your done :laugh: enjoy stock
Click to expand...
Click to collapse
Why do we need such a long process. I installed stock rom through recovery mode.
Will be there any difference?

kishorebvs said:
Why do we need such a long process. I installed stock rom through recovery mode.
Will be there any difference?
Click to expand...
Click to collapse
that is flashable zip right hmm !! i prefer this method this is the actual method but you can ever go for that i prefer this because factory images will also be flashed in this method and even bootloader will also be updated and stuff like that. not sure what will be the difference between both may be nothing
and the main thing is he wanted to restore stock recovery so this is only way to restore stock recovery

Downgrading from 6.0 to 5.02 using easy installer

I've have read that it is possible to downgrade from MM to LP without bricking the device using the easy installer.bat file. I have also read that the bat file must be edited removing 2 lines of code ie: "mfastboot.exe flash motoboot motoboot.img" (Which appears twice ) . Is there anything else that needs to be removed ? Also does the whole section need to be removed ie: "echo FLASHING BOOT LOADER..
mfastboot.exe flash motoboot motoboot.img
echo". or just the "mfastboot.exe flash motoboot motoboot.img" line. I would appreciate a clarification . Thank you !!

You're also gonna want to remove the line of code responsible for flashing the partition table (gpt.bin) which also appears twice.
I modified this script for that very purpose....see the attachment.
Just place it in the same folder and flash.

MobileHD said:
You're also gonna want to remove the line of code responsible for flashing the partition table (gpt.bin) which also appears twice.
I modified this script for that very purpose....see the attachment.
Just place it in the same folder and flash.
Click to expand...
Click to collapse
.. Wow thanks! So let me get this straight. I extract the attached zip file to the easy installer folder and use it to flash back to to 5.0.2. I assume all 4 lines of code have been removed?

garyben60 said:
.. Wow thanks! So let me get this straight. I extract the attached zip file to the easy installer folder and use it to flash back to to 5.0.2. I assume all 4 lines of code have been removed?
Click to expand...
Click to collapse
Just make sure the following files are in the folder where you extracted the flash script:
AdbWinApi.dll
AdbWinUsbApi.dll
boot.img
flashfile.xml
fsg.mbn
logo.bin
mfastboot.exe
NON-HLOS.bin
recovery.img
servicefile.xml
system.img_sparsechunk.0
system.img_sparsechunk.1
system.img_sparsechunk.2
system.img_sparsechunk.3
system.img_sparsechunk.4
TITAN_RETUGLB_5.0.2_LXB22.99-24.12_cid9_CFC.info.txt (NOTE: name will differ based on variant)
gpt.bin & motoboot.img aren't required for the downgrade and shouldn't be downgraded as if may brick your device.
As an additional precaution you can rename those two files to something like '_gpt.bin' & '_motoboot.img'
And yes all unnecessary lines have been removed.
Run the script and choose option '1' to downgrade.
Good Luck and safe downgrade!!

MobileHD said:
Just make sure the following files are in the folder while you extracted the flash script:
AdbWinApi.dll
AdbWinUsbApi.dll
boot.img
flashfile.xml
fsg.mbn
logo.bin
mfastboot.exe
NON-HLOS.bin
recovery.img
servicefile.xml
system.img_sparsechunk.0
system.img_sparsechunk.1
system.img_sparsechunk.2
system.img_sparsechunk.3
system.img_sparsechunk.4
TITAN_RETUGLB_5.0.2_LXB22.99-24.12_cid9_CFC.info.txt (NOTE: name will differ based on variant)
gpt.bin & motoboot.img aren't required for the downgrade and shouldn't be downgraded as if may brick your device.
As an additional precaution you can rename those two files to something like '_gpt.bin' & '_motoboot.img'
And yes all unnecessary lines have been removed.
Run the script and choose option '1' to downgrade.
Good Luck and safe downgrade!!
Click to expand...
Click to collapse
Thanks again!! really appreciate your help..

One last question. My specific device model is xt1068 (Titan). I see that the flash script say it's for the xt1063. Will it still work with my device?

garyben60 said:
I've have read that it is possible to downgrade from MM to LP without bricking the device using the easy installer.bat file. I have also read that the bat file must be edited removing 2 lines of code ie: "mfastboot.exe flash motoboot motoboot.img" (Which appears twice ) . Is there anything else that needs to be removed ? Also does the whole section need to be removed ie: "echo FLASHING BOOT LOADER..
mfastboot.exe flash motoboot motoboot.img
echo". or just the "mfastboot.exe flash motoboot motoboot.img" line. I would appreciate a clarification . Thank you !!
Click to expand...
Click to collapse
I Recently made a video on this. If you want you can follow this https://youtu.be/OP_AGnwJF4Q tutorial. Hope you like it.

Manav08 said:
I Recently made a video on this. If you want you can follow this https://youtu.be/OP_AGnwJF4Q tutorial. Hope you like it.
Click to expand...
Click to collapse
. Thank you. I saw your video. Well done! I do have a question.. Did you modify the easy installer bat file in any way? The reason I'm asking this because if you read the previous replies certain modifications to the code within the bat file have to be made so that the bootloader doesn't get downgraded thus hardbricking the device.

garyben60 said:
One last question. My specific device model is xt1068 (Titan). I see that the flash script say it's for the xt1063. Will it still work with my device?
Click to expand...
Click to collapse
This is important:
It will work, just make sure that all the system.img_sparsechunk files are accounted for. You may have to edit the script in accordance, for example:
The Lollipop stock ROM for my device XT1063 has 5 system.img_sparsechunk files from 0-4 as the file extension thus the lines of code in the script...
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash system system.img_sparsechunk.4
However if your stock ROM has more or less system.img_sparsechunk files, simple edit the script adding or removing the addition files so that the system partition is properly flashed to your device.
--Update--
I just watched the video that @Manav08 posted, and yes the flash script will work with your device (XT1068), you have nothing to worry about.

MobileHD said:
This is important:
It will work, just make sure that all the system.img_sparsechunk files are accounted for. You may have to edit the script in accordance, for example:
The Lollipop stock ROM for my device XT1063 has 5 system.img_sparsechunk files from 0-4 as the file extension thus the lines of code in the script...
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash system system.img_sparsechunk.4
However if your stock ROM has more or less system.img_sparsechunk files, simple edit the script adding or removing the addition files so that the system partition is properly flashed to your device.
--Update--
I just watched the video that @Manav08 posted, and yes the flash script will work with your device (XT1068), you have nothing to worry about.
Click to expand...
Click to collapse
. Thanks a million for your input.. What are your views about the video?

garyben60 said:
. Thanks a million for your input.. What are your views about the video?
Click to expand...
Click to collapse
I can see in the video that the easyinstaller script used, attempted to flash 'motoboot.img' which you sure avoid doing. What I suggest is to follow the instructions from the video but use my flash script instead.

My thoughts exactly. ..

If anyone uses this method to downgrade don't do what I did and after downgrade allow your device to take any official updates or your device will hard brick. It happened to me and my moto g is now a paperweight.
Sent from my XT1068 using XDA-Developers mobile app