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
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 !
These will receive OTA updates for the Gecko/Gaia parts of Firefox OS. For a full system update you will need to download the new set of system images and reflash manually.
To install:
Extract all system images
Flash each image via fastboot
Reboot!
Use fastboot to flash each image to the relevant partition such as:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img
If you are flashing a full system image on top of an existing Firefox OS install you can skip userdata to keep all of your downloaded files, installed apps, browser history and other settings.
Download https://github.com/fxpdev/b2g-updates/releases/tag/nightly
Im not autor
bugs?
I know this is old but anyone tried this with Sony Z3 Compact Tablet? I cannot seem to find any wifi network with it, otherwise it works fine, but without network connection it's not too great.
Firefox OS is discontinued since four years ago or so..
I have been away from Android for a little while - but I'm coming to sell my Nexus 6, and so I'm attempting to flash the latest OS from google.
I downloaded 6.0.1 from google, and then worked through these steps:
fastboot flash bootloader C:/image-shamu-XXXXXX/bootloader.img
fastboot reboot-bootloader
fastboot flash radio C:/image-shamu-XXXXXX/radio.img
fastboot reboot-bootloader
fastboot flash system C:/image-shamu-XXXXXX/system.img
Yes, there are more steps, but I just can't get to them! Once I flash system I get the following...
target reported max download size of 536870912 bytes
sending sparse 'system' (517178 KB)...
OKAY [ 25.080s]
writing 'system'...
OKAY [ 7.142s]
sending sparse 'system' (515137 KB)...
OKAY [ 25.155s]
writing 'system'...
OKAY [ 7.346s]
sending sparse 'system' (515644 KB)...
Thats it, thats as far as it ever goes, then I just sit there waiting, waiting, and nothing happens.
Any suggestions?
Updated Android SDK Tools to make sure you have the latest fastboot? If you haven't updated, update these.
Here's the commands I run, keep in mind this will completely wipe all data/apps/files from the device, so backup anything you want saved to a computer before doing this. Is it overkill? Sure, but I've never had an issues across multiple devices, so since, for me at least, if it isn't broke I'll keep doing this:
Erase:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
Flash bootloader:
Code:
fastboot flash bootloader "name of bootloader"
fastboot reboot-bootloader
Flash radio:
Code:
fastboot flash radio "name of radio"
fastboot reboot-bootloader
Flash img files:
NOTE: The system.img is large, so if your Android SDK tools isn't updated, you could get an error. This part does take a few minutes to do, so be patient and give it time to complete.
Code:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
Reboot device:
Code:
fastboot reboot
Just a thought, prompted by the commands in the original post referring to the C: drive. I didn't even know you could do this, though I suppose it makes sense. The easier method IMO is to copy or move all the image files to the ADB/Fastboot folder, rename them if necessary for simpler typing, then just "fastboot flash system system.img", etc., as RMarkwald says.
I doubt that it will make any difference, but since you appear to be stuck it might be worth trying - worst case, it fails again...
And just for curiosity, did you try flash-all.bat? I know that people have trouble with it and fall back on the separate flashing steps - just wondering if that's why you're doing it this way.
dahawthorne said:
Just a thought, prompted by the commands in the original post referring to the C: drive. I didn't even know you could do this, though I suppose it makes sense. The easier method IMO is to copy or move all the image files to the ADB/Fastboot folder, rename them if necessary for simpler typing, then just "fastboot flash system system.img", etc., as RMarkwald says.
I doubt that it will make any difference, but since you appear to be stuck it might be worth trying - worst case, it fails again...
And just for curiosity, did you try flash-all.bat? I know that people have trouble with it and fall back on the separate flashing steps - just wondering if that's why you're doing it this way.
Click to expand...
Click to collapse
Good call on the movement of files to the adb/fastboot folder, as that is what I do when flashing these files, and the flash-all.bat potentially causing his issues.
RMarkwald said:
Updated Android SDK Tools to make sure you have the latest fastboot? If you haven't updated, update these.
Here's the commands I run, keep in mind this will completely wipe all data/apps/files from the device, so backup anything you want saved to a computer before doing this. Is it overkill? Sure, but I've never had an issues across multiple devices, so since, for me at least, if it isn't broke I'll keep doing this:
Erase:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
Flash bootloader:
Code:
fastboot flash bootloader "name of bootloader"
fastboot reboot-bootloader
Flash radio:
Code:
fastboot flash radio "name of radio"
fastboot reboot-bootloader
Flash img files:
NOTE: The system.img is large, so if your Android SDK tools isn't updated, you could get an error. This part does take a few minutes to do, so be patient and give it time to complete.
Code:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
Reboot device:
Code:
fastboot reboot
Click to expand...
Click to collapse
Having all kinds of trouble rerooting my 6. Will this relock the bootloader? Wanted to keep user data but if a fresh start is what I need then OK. TIA
Mongo23ny said:
Having all kinds of trouble rerooting my 6. Will this relock the bootloader? Wanted to keep user data but if a fresh start is what I need then OK. TIA
Click to expand...
Click to collapse
No, you have to run "fastboot oem lock" to lock the bootloader, not recommended.
You perform above steps, boot device and go through setup, enable USB debugging, boot to bootloader and flash TWRP, boot to TWRP. You will need to clean up some space to flash SuperSU (you'll have to remove apps from /system/app or /system/priv-app), as there will not be any space on /system to install/flash anything that needs to live there, it either won't work or error out. Once you have removed system apps and create space on /system, you can flash your SuperSU zip, then reboot the phone.
RMarkwald said:
No, you have to run "fastboot oem lock" to lock the bootloader, not recommended.
You perform above steps, boot device and go through setup, enable USB debugging, boot to bootloader and flash TWRP, boot to TWRP. You will need to clean up some space to flash SuperSU (you'll have to remove apps from /system/app or /system/priv-app), as there will not be any space on /system to install/flash anything that needs to live there, it either won't work or error out. Once you have removed system apps and create space on /system, you can flash your SuperSU zip, then reboot the phone.
Click to expand...
Click to collapse
I don't wanna relock the bootloader. Not sure what to remove from system apps, etc. This was not this difficult the first time I rooted. Thanks for any and all help.
This is off-topic from the original question, but let's go with it...
Personally I've never had to remove anything from system. Clean install, flash TWRP (or just temporarily boot into it), flash SuperSU v2.67. Job done. Since it (probably) doesn't try to install into system, there shouldn't be any problem.
@dannstarr - you haven't answered my question.
dahawthorne said:
This is off-topic from the original question, but let's go with it...
Personally I've never had to remove anything from system. Clean install, flash TWRP (or just temporarily boot into it), flash SuperSU v2.67. Job done. Since it (probably) doesn't try to install into system, there shouldn't be any problem.
@dannstarr - you haven't answered my question.
Click to expand...
Click to collapse
Do I keep system read only in twrp 3.0.0.0?
Disregard, did everything suggested by rmarkwald and dahawthorne. Worked well, took some security update that happened to get rid of the corrupt phone boot message. Flashed twrp 3.0.0.0 and installed SuperSU 2.67 with no problems. Thanks all.
After a lot of trial and error and experiments with custom roms I decided to post my own guide to to restoring Moto G XT1039 to stock firmware. I take no responsibility if you brick or do whatever damage to your device using this guide. Use it at your own risk: It was tested on my xt1039 and worked for me.
What you will need;
A stock firmware (rom) for Moto G XT1039 or Peregrine, or Moto G 4G LTE as it is often called. Make sure you get the right one for your region and device as well.
The best place to get one is from here http://firmware.center/firmware/Motorola/Moto%20G%20%281st%20gen-2013%29/Stock/XT1039/
The website is called firmware center http://firmware.center/ and maybe you can get other useful firmware there too for your devices.
To get the right firmware, check your model number (e.g xt1039) check the one you want for your region, Brasil, Eu (Europe), US,, others.
Check your device's cid to ensure compatibility, Mine is cid7. To do that reboot your device to bootloader by pressing power and volume down when turning the device on. Connect the device to your computer, open a terminal or a cmd (if in windows) and type "fastboot getvar all". For fastboot to work properly you should use fastbooot commands as root in Linux based systems and probably open cmd as administrator in Windows. After pressing lines will appear with info about your device, among those lines there is the cid value as well, for example something like, cid: 0x0007. You can use the cid getter from google play if you can use google play in your device.
Now that we got the cid and the model, choose one firmware from the link above, make sure it is in xml.zip format, has your cid value, for example 7 is the 0x0007 and select one for the region that you live and want to use your device in.
Next is setting up your computer, obviously you need a usb cable, and you need to have configured fastboot and adb drivers in your device correctly. For myself I use Fedora so I just installed android-tools. You can installed them from the terminal as root or your can install from yumex or yumex-dnf. You can't find them in gnome-software. I have no experience for Windows, or Mac, so do your own search about those devices.
So after downloading your firmware, which should be in xml.zip format, extract it and note the folder where you extracted it. For example in downloads, or documents or other folder.
Create a directory - Point the terminal to the extracted xml.zip folder.
It should be something like this, cd ~/Downloads/nameoffolder.xml.zip or as root cd /home/yourusername/Downloads/folder.xml.zip
It could be downloads, it could documents, you should know where you saved your xml.zip firmware file.
And now type these commands
su
yourrootpassword
fastboot devices
If you see a number a space and a name, it means your device has been recognized by fastboot.
Note: For the Indian version, the initial command might be fastboot.exe oem lock begin but I am not sure if this applies to xt1039 or not.
fastboot oem lock begin
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
Now at the next step, you should look into the extracted xm.zip folder and see how the sparsechunks are named and how many are there. Some people including myself made mistakes here by simply copying commands from tutorials which said for instance
fastboot flash system system.img_sparsechunk1 while in fact it was fastboot flash system system.img_sparsechunk.0
So you should flash the names of the sparsechunks found in your extracted folder according to their names from the lower number to the highest. In my Eu firmware there were four sparsechunks names sparsechunk.0 .1 .2 and .3
So you should type
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
If it is the same in the folder your extracted, maybe they are named sparsechunk1 or there are not four of them, maybe there are three, you should look into that and make sure.
Ok once done with the sparsechunks
Continue with these commands
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Optional (Recommended to avoid any possible errors but make sure you don't delete any important data. However it is always a good idea to backup what you need to backup before you flash anything on your device)
fastboot erase cache
fastboot erase userdata
And finally
fastboot oem lock.
There was an error message, I forgot what it was, but my device actually got locked.
Note: In some places you will see the mfastboot command. In Fedora that command does not exist. So I figure that is for Windows. mfastboot and fastboot do the same thing.
Now even after locking the device the bootloader unlocked warning message will remain. I think that is because Motorola wants to tell others that there is a chance that critical components of the device could have been altered and the firmware might be not original because it's bootloader got unlocked.
If you get annoyed by this message, and your phone is working perfect and perhaps you would like to sell it, there is a solution for this.
The solution is shown here. All you need to do is to flash an alternative or modified version of logo.bin. You can do this even when the device is locked again.
fastboot flash logo logo.bin.
Many sites give you a zip to install, but unless you have twrp or a custom recovery, this method won't work when you are doing a full stock firmware recovery like in this guide.
First go to your extracted.xml.zip folder and copy the logo.bin and save it somewhere else.
I installed hexedit in my Fedora computer and edited the logo.bin file (the original one inside the extracted xm.zip) using hexedit. Simply to make the unlocked bootloader logo and motoboot logo the same.
The guide for this is here https://www.reddit.com/r/MotoG/comments/2jucwe/removing_the_unlock_warning_on_boot_miniguide/
To edit wit hexedit (which only works as a terminal command)
cd to the path where logo.bin is, the same as cd-iing when flashing the firmware above.
type hexedit
type logo.bin and edit the logo.bin file according to the instructions set above. No need to do the pulling of logo.bin from the device using the command "# dd if=/dev/block/platform/msm_sdcc.1/by-name/logo of=/sdcard/logo.bin count=1 bs=1085857" described above.
For your convenience I have also attached the logo.bin file, the modified one that I used to remove the bootloader locked warning in my own phone.
Download the logo.bin from here and flash it using fastboot flash logo logo.bin.
https://mega.nz/#!XFRGxYhR!YApyTk1oY-aSKCHt_1r3TJWkO4FmrJfOzLl08X-Pmc8