Related
Hello Moto
I've just downloaded Verizon Jelly Bean 4.1.1 by "Firmware Team".
Just to play with it a little, extract apks and test them on Galaxy SII Skyrocket.
The thing is i'm having a hard time opening system.img.
Now i've tried LinuxReader, Unyaffs and ext2explore/read but none of these can open it, they all say that it's an unrecognized image.
Do you guys know how to properly open a stock moto System.img?
lingowistico said:
Hello Moto
I've just downloaded Verizon Jelly Bean 4.1.1 by "Firmware Team".
Just to play with it a little, extract apks and test them on Galaxy SII Skyrocket.
The thing is i'm having a hard time opening system.img.
Now i've tried LinuxReader, Unyaffs and ext2explore/read but none of these can open it, they all say that it's an unrecognized image.
Do you guys know how to properly open a stock moto System.img?
Click to expand...
Click to collapse
Google for a tool called simg2img (I used the python script that appears in get first few results, there should be other versions as well). That will unpack the image into a plain ext4 image that you can mount with any Linux pc (I recommend using a virtual machine if you have windows or mac).
Happy hacking!
Sent from my XT907
aslomagic, did you try this with the firmware lingowistico is talking about? I also tried before to unpack system.img from this package, and system.img.ext4 from ICS package, and another ICS soft for XT897, and all of them give "Bad magic" error in simg2img. All of those softs are published by the same "Firmware Team" - maybe that's the case? I also tried dsixda kitchen (which also uses simg2img, but anyway...) and it also didn't work. Might be also some custom Motorola's approach to system.img....
Could you possibly help? Thanks.
micx_pl said:
aslomagic, did you try this with the firmware lingowistico is talking about? I also tried before to unpack system.img from this package, and system.img.ext4 from ICS package, and another ICS soft for XT897, and all of them give "Bad magic" error in simg2img. All of those softs are published by the same "Firmware Team" - maybe that's the case? I also tried dsixda kitchen (which also uses simg2img, but anyway...) and it also didn't work. Might be also some custom Motorola's approach to system.img....
Could you possibly help? Thanks.
Click to expand...
Click to collapse
Well, I know for a fact that those images are packed ext4, but I haven't tried specifically with that one.
Now that you mention, I think I remember signed images (like those ones) have some additional header, maybe that needs to be removed with an hex editor, or with dd of you like
If I get a chance, I'll try and report back...
Sent from my XT907
aslomagic said:
Well, I know for a fact that those images are packed ext4, but I haven't tried specifically with that one.
Now that you mention, I think I remember signed images (like those ones) have some additional header, maybe that needs to be removed with an hex editor, or with dd of you like
If I get a chance, I'll try and report back...
Click to expand...
Click to collapse
Ok, I tried, and yes, it complains it cannot find the magic (again, I'm using the python script). I modified the script to look for the magic value in the first 50Mb of the file, and if it finds it, it starts unpacking from there. Python scripts are very easy to play with
It seems to work for me, but I don't have a linux vm handy to see if it mounts correctly (I'm currently on a mac). micx_pl, can you give it a try and let me know?
I had to zip the file even though it's very small because the forum won't let me upload a .py file... who knows, just unzip it.
Holy cow! It works! You're the master I was looking for such solution everywhere, and was stunned to see barely few topics with similar problem, and no solution at all. Thanks!
micx_pl said:
Holy cow! It works! You're the master I was looking for such solution everywhere, and was stunned to see barely few topics with similar problem, and no solution at all. Thanks!
Click to expand...
Click to collapse
You're welcome, glad I could help!
Sent from my XT907
aslomagic said:
Ok, I tried, and yes, it complains it cannot find the magic (again, I'm using the python script). I modified the script to look for the magic value in the first 50Mb of the file, and if it finds it, it starts unpacking from there. Python scripts are very easy to play with
It seems to work for me, but I don't have a linux vm handy to see if it mounts correctly (I'm currently on a mac). micx_pl, can you give it a try and let me know?
I had to zip the file even though it's very small because the forum won't let me upload a .py file... who knows, just unzip it.
Click to expand...
Click to collapse
HOLY $#!+ THANKS!!! I've been trying to decompress the moto images for awhile and have never been able to do it until now
Would it be possible to modify make_ext4fs to re-sparse the image and copy the original signature?
Q9Nap said:
Would it be possible to modify make_ext4fs to re-sparse the image and copy the original signature?
Click to expand...
Click to collapse
You're welcome to try ... my guess is that it could be made to work if the image was an official, originally signed image that was unpacked by the script above or equivalent, but if you want to modify it, re-pack it and re-attach the signature, most likely the signature won't match the content. But I may be wrong, so if somebody is willing to try, best of luck to you
If your goal is just to create a packed image, but not necessarily signed (needs bootloader unlock), then I'd say it's definitely possible, search around here.
aslomagic said:
You're welcome to try ... my guess is that it could be made to work if the image was an official, originally signed image that was unpacked by the script above or equivalent, but if you want to modify it, re-pack it and re-attach the signature, most likely the signature won't match the content. But I may be wrong, so if somebody is willing to try, best of luck to you
If your goal is just to create a packed image, but not necessarily signed (needs bootloader unlock), then I'd say it's definitely possible, search around here.
Click to expand...
Click to collapse
i'm sure you're right about the signature not working on a modified image; it was just wishful thinking. the idea of course would be to inject superuser.apk and su, which wouldn't be necessary on a bootloader unlocked device.
for bootloader unlocked devices though, the ability to repack a modified image does give you another way to build custom roms. here's the code to unpack and repack images with simg2img.py and make_ext4fs:
Code:
mkdir system
./simg2img.py system.img.ext4 system.raw
sudo mount -t ext4 -o loop system.raw system/
#make changes, then:
wc -c system.raw #lists size in bytes of system.raw
sudo make_ext4fs -s -l 1234567890 -a system system.img system/ #where 1234567890 is output from wc -c
sudo umount system
rm -rf system
i've used this proecess with samsung system images, should work for moto images now too (bootloader unlocked, of course)
Yep, it's a good cheat sheet reference
Besides, on razr m and hd at least, you can also use this with safestrap without unlocking the bootloader.
aslomagic said:
Besides, on razr m and hd at least, you can also use this with safestrap without unlocking the bootloader.
Click to expand...
Click to collapse
Not sure what you mean by this; do you mean you could mount a modified system.img with safestrap? I guess it's possible since safestrap uses a system.img on the emmc, interesting idea
Q9Nap said:
Not sure what you mean by this; do you mean you could mount a modified system.img with safestrap? I guess it's possible since safestrap uses a system.img on the emmc, interesting idea
Click to expand...
Click to collapse
Yes, that's what I mean, more or less. You don't need safestrap to just mount it (use the terminal and "mount"), but you can use it to boot from it and try it.
I did this to try the Telstra image that pjcons dumped, which is pre-rooted and not signed (there it's no official signed image to date), and with a few tricks it worked without me having to unlock the bootloader.
Sent from my XT907
aslomagic said:
Google for a tool called simg2img (I used the python script that appears in get first few results, there should be other versions as well). That will unpack the image into a plain ext4 image that you can mount with any Linux pc (I recommend using a virtual machine if you have windows or mac).
Happy hacking!
Sent from my XT907
Click to expand...
Click to collapse
hello, i cant find anything on the basics of how this works, could you point me somewhere that explains it step by step or do one here. sorry of the noob question
TheWhiteChallenger said:
hello, i cant find anything on the basics of how this works, could you point me somewhere that explains it step by step or do one here. sorry of the noob question
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1588461
CNexus said:
http://forum.xda-developers.com/showthread.php?t=1588461
Click to expand...
Click to collapse
Thanks for the link I need to go learn Linux now. Lol I dontbgt the virtual machine thing at all. Its basically a Linux emulator right?
Sent from my XT1080 using XDA Premium 4 mobile app
TheWhiteChallenger said:
Thanks for the link I need to go learn Linux now. Lol I dontbgt the virtual machine thing at all. Its basically a Linux emulator right?
Sent from my XT1080 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No need to
http://sourceforge.net/projects/androidicsjbext/
CNexus said:
No need to
http://sourceforge.net/projects/androidicsjbext/
Click to expand...
Click to collapse
oh damn it. ok first i do appreciate the help. but that sucked. that was the frist program i tryed and it gives me "unknown file format" have i just been screwing up from the begining?
Ok since there is a new house of moto and some of the instructions have changed I am deleting the old instructions go here http://www.droidrzr.com/index.php/topic/28162-house-of-moto-20/ and follow Samuri's instructions if you get stuck I will still attempt to help you out I am not going to re write all the instructions again. Trying to piece it together will cause more confusion then help. Please read then re-read his instructions they are all you need after all he created the house of moto. If you cant figure it out pm me or post here and I will try to help the best I can. Here are his instructions for quick reference but you have to got to the above link to download everything.
ALL CREDIT GOES TO SAMURI HL FOR CREATING THIS AWESOME TOOL.
Please do yourself a favor and read, read again, and read one more time before installing and using this tool. If it's set up correctly, it's very easy to use. But if you don't follow directions, it'll either not work or not do what you expect. Failure to read and follow the directions is NOT a defect of the tool!
Mission statement for tool:
This will allow users to have a user friendly framework automation tool for new Motorola devices. Easily customized for any device that allows RSD or fastboot flashing of custom scripts that perform various functions. Most notably is when a user screws something up and the phone no longer boots (so called soft bricking). The KEEP DATA and/or FULL scripts can restore the partitions of the phone to minty factory fresh in the event that your phone doesn't boot.
WARNING: Upgrades from 1.4 are NOT supported. Install CLEAN. You have been warned.
SETUP:
Required Steps
o) You MUST have the latest Motorola USB driver installed: http://lmgtfy.com/?q...rola USB driver
o) Download: HouseOfMoto_2.0.zip
o) Extract the HouseOfMoto folder in the zip to your hard drive. IMPORTANT: Make sure no spaces are in the path. (Windows users should extract it to C:\)
o) Download the support file for your device and extract into your HouseOfMoto directory. (see device support below)
o) Download your FXZ from here: http://sbf.droid-developers.org/ [Site is back, BUT, very limited. It'll take time to repopulate it]
o) Add the FXZ files to your HouseOfMoto\FXZ_xtYYY directory. (see Adding the FXZ below)
Optional Steps
o) If root exists for your device, add the files to the root folder. Make sure run.bat and/or run.sh exists.
CLARIFICATION: When I say "if root exists for your phone" I'm referring to a root exploit that has a run.bat script in order to install root. If that doesn't exist for your phone, or your root exploit does not have a run.bat, this does not apply to you. This is ONLY for adding an option to root your phone to the House of Moto menu as a convenience option. It is NOT a required step.
Linux/Mac Notes:
o) You may need to chmod +x HouseOfMoto.sh
o) You may need to run HouseOfMoto.sh as sudo
Usage:
o) Your phone MUST be in AP Fastboot mode. Try holding volume down and pressing the power button when the phone is off.
o) Run the HouseOfMoto.bat or HouseOfMoto.sh in your HouseOfMoto directory
o) On first run:
Enter your device model (xt926, xt875, etc)
For Windows: Select flash mode: rsd or fastboot
o) Flash mode on Windows can be changed from the main menu
o) Phone model can be changed from the main menu
o) Select the script you wish to flash
o) Follow directions!
Adding the FXZ:
This part confuses a LOT of people so I'm going to use the FXZ for the xt926 as an example of how this should work. Obviously you'll need to use the proper FXZ for your device, but, the concept is generally the same.
This is a point that many get wrong so please follow this carefully...
When you open your VRZ_XT926_9.8.1Q-79-1_CFC.xml.zip file, you will see a directory inside it. You must go INTO the directory inside the zip. There you will see a whole bunch of files. Select them all, and extract them into the FXZ_xt926 folder. All the files must be at the root of the FXZ_xt926 folder, NOT in a sub folder within it. If you have this:
HouseOfMoto\FXZ_xt926\VRZ_XT926_9.8.1Q-79-1_CFC.xml\boot.img
It's wrong. If instead you have this:
HouseOfMoto\FXZ_xt926\boot.img
It's correct.
DEVICE SUPPORT:
o) xt875
o) xt907
o) xt912
o) xt926
o) xt1030
o) xt1080
NOTES:
o) xtYYY is the device model...i.e. xt1058, xt895, etc
DA FAQ:
Q: What flash mode should I pick?
A: Whether you use RSD or fastboot is a personal choice and completely up to you. If you have problems flashing in one mode, you can switch to the other and try again to see if you get better results.
SUPPORT:
If I tell you to create a log and post it, you are to run the CreateLOG.bat file to your c:\HouseOfMoto directory and post the results in this thread.
OP Plz update on Houseofmoto v1.4 when creating the FXZ version only the phone model, (i.e. FXZ_xt1080) Is needed. Also the Thread name needs to be [GUIDE] Return to stock and stickty IMO
You are a Godsend. The House of Moto website was pretty confusing.
Just want to make sure I'm understanding this right. I rooted my Maxx with PwnMyMoto. I also made some modification to allow for wifi tethering. I'm pretty sure I want to return to 100% stock, so that I can receive OTA updates. I can use House of Moto to accomplish this, and my Maxx will be like it was, fresh outta the box?
Ansky11 said:
Just want to make sure I'm understanding this right. I rooted my Maxx with PwnMyMoto. I also made some modification to allow for wifi tethering. I'm pretty sure I want to return to 100% stock, so that I can receive OTA updates. I can use House of Moto to accomplish this, and my Maxx will be like it was, fresh outta the box?
Click to expand...
Click to collapse
Yes what is better is you can choose the save data fxz and it will return you to stock but leave all your apps and data alone.
Which flash mode do we use? Fastboot [snapdragon]?
bigv5150 said:
** Moderators if this is in the wrong forum please move it also be advised I have contacted Samuri and he is fine with me posting this information.
ALL CREDIT GOES TO SamuriHL
Ok guys we have root this is great but I keep seeing guys having problems with installing it jcase has been great in evolving the root apk to accommodate us. I just thought I would try to lend some assistance because I know he is busy and a lot of us aren't as computer savvy as these guys. If you didn't have a bionic then you may not know who Samuri is but he made a tool for bionic owners it was great and very useful. He has since moved on from the bionic but after I contacted him about a tool for the Maxx he as usual came through. He created a Moto tool for several of the new devices and old. It is located here---> http://www.droidrzr.com/index.php/topic/28162-house-of-moto/ This tool will let you fxz full or fxz save data. If you don't know the difference fxz full will wipe the phone to out of the box fresh. Save data will install just the system but not touch your user data ie apps, wallpaper etc. Now to the good news any one that is having an issue still with root download use the above tool and use the fxz save data option it will wipe out root and you can start fresh. It will give you back your stock recovery as well. I had no problem with root but I tested this to make sure it would work. I just re-rooted the whole process took less than 15 minutes.
Below I will give instructions for the laymen if you find the instructions a little confusing in the House of Moto. If you get stuck PM me and I will try to help I am no genius when it comes to this but I have made most of the mistakes and learned from them. If I can't figure it out then you will have to contact the creator Samuri. But be forewarned he has little patience for stupidity. This is the reason I am taking the time to do this to assist him with the less knowledgeable. Remember he no longer owns a moto phone he did this out of the goodness of his heart.
Set up and installation:
1) install the House of Moto 1.2
2) Run it and let it extract to c:\HouseOfMoto it does this automatically
3) Create an FXZ_xxx_xtYYY directory where xxx is the FXZ version (MR4, 98.72.22, etc) and xtYYY is your device (xt926, xt875, etc) it should look like this FXZ_12.7.7_xt1080. You can go here---> http://sbf.droid-developers.org/ and download the FXZ for your device
4) Add the FXZ files to your new FXZ_xxx_xtYYY directory
5) Add the scripts for your device to your rsd_scripts and/or fastboot_scripts directories. See Adding support for an xtYY device. The scripts are at the bottom of the first post under support just find your phone download and execute, it will put them in the proper file in the house of moto.
6) the next step talks about root but we don't need that since we have an apk to re-root so I disregarded this step.
Using the House Of Moto:
1) Run the HouseOfMoto.bat in your c:\HouseOfMoto directory be advised if you make a desktop short cut of the run bat. file it will throw an error stating you need to install rsd which is already installed in the tool. You have to run the House of moto bat. file from within the house of moto folder.
2) On first run: Enter your device model (xt926, xt875, etc) Select flash mode: rsd, fastboot [snapdragon], or fastboot [omap]
3) flash mode can be changed from the main menu
4) device model can be changed from the main menu
5) Select the script you wish to execute ie. Full FXZ Save Data FXZ
6) Follow directions!
There are further instructions in the above thread for creating the FXZ file. I will say this simply when you create the FXZ file it should not have a file folder inside it. Meaning the FXZ file you placed in the House of Moto will say if you have a maxx FXZ_12.7.7_xt1080. When you open this file it shoud contain the whole FXZ not another file you have to open. So extract the FXZ then cut and paste it in the FXZ folder if you don't you will get an error.
This is what your house of moto should look like when you open it:
fastboot_scripts---> will contain Full_xt1080(or whatever phone you use) and Keep-data_xt1080 (or whatever phone you use)
FXZ_12.7.7_xt1080--->again when you open this file you should see the FXZ files not a folder that you have to access.
root
rsd
rsd_scripts---> will contain Full_xt1080(or whatever phone you use) and Keep-data_xt1080 (or whatever phone you use)
utils
flashmode
House of Moto
phone--->you will not see this until you type in what phone you want to use in step 2 above under using the house of moto
Just to sum things up the above tool will put everything where it needs to be except the FXZ that you have to do yourself. Good luck this is truly a useful tool.
One more thing I sent Samuri the xml files for the moto x (verizon and at&t models) also the mini and ultra he said the xml files are so close it was ridiculous. This is a quote from Samuri for being able to use this tool with an ultra mini or moto x
An anonymous donor sent me the xt1030, xt1058, and xt1060 FXZ xml's. They all use the same files as the xt1080 in their respective FXZ's. It's just a matter of me renaming the xt1080 scripts a bunch of times for the different models and packaging them up. Or if people need it before I get them posted, take the xt1080 package and rename the 4 scripts to xt10xx depending on your model and it'll work just fine. Moto's making my life a lot easier that's for sure! In fact I'll write a batch file so that if I ever have to change them for any reason it'll just create them all. LOL.
Click to expand...
Click to collapse
Dammit. I knew I'd be the one idiot.
Followed to the letter and when I run the .BAT, I get :
"Warning: Please check input file. Either XML format is wrong or image files associated with it are missing."
Any ideas that an idiot may be able to follow along with?
FIGURED IT OUT:
Didn't save to C drive. saved it to desktop.
Trying to do this but it seems to fail to install recovery even though it says successful. Tried to download fxz file a couple times and it always gives errors on unpacking, which may be issue.
It was successful at destroying my sim card though.... I have no service now.
One thing to keep in mind that stumped me for a few was the model number. When you go to download the FXZ file the droid maxx is xt1080m. You don't use that as your model number you type into house of moto. Just use xt1080.
Difficulties with howto...
Sorry guys,
I'm having a hell of a time but I have a problem related to this. At current my phone took the OTA while I was rooted and its now boot-looped. I'm trying to revert to the stock firmware, and someone suggested this option. I'm having problems with the step here:
5) Add the scripts for your device to your rsd_scripts and/or fastboot_scripts directories. See Adding support for an xtYY device. The scripts are at the bottom of the first post under support just find your phone download and execute, it will put them in the proper file in the house of moto.
This step is odd, what scripts are you supposed to add to the RSD/Fastboot scripts? Where do I get the scripts? From the FXZ passage?
Qb411 said:
Sorry guys,
I'm having a hell of a time but I have a problem related to this. At current my phone took the OTA while I was rooted and its now boot-looped. I'm trying to revert to the stock firmware, and someone suggested this option. I'm having problems with the step here:
5) Add the scripts for your device to your rsd_scripts and/or fastboot_scripts directories. See Adding support for an xtYY device. The scripts are at the bottom of the first post under support just find your phone download and execute, it will put them in the proper file in the house of moto.
This step is odd, what scripts are you supposed to add to the RSD/Fastboot scripts? Where do I get the scripts? From the FXZ passage?
Click to expand...
Click to collapse
the scripts are near the bottom of the post where you download houseofmoto, scroll down til you see Support in bold. theres a link for xt1080 scripts, just download them and place them in the correct folder.
hmmmm
beelow319 said:
the scripts are near the bottom of the post where you download houseofmoto, scroll down til you see Support in bold. theres a link for xt1080 scripts, just download them and place them in the correct folder.
Click to expand...
Click to collapse
I had trouble with this when I chose fastboot omap and did the "keep data" option. It went through said it flashed stuffs, but I still had root. I changed it to fastboot snapdragon and did it again and then it worked. I have a Droid Maxx and used Pwnmymoto a month ago, which flashed my recovery, thus the need to fixor that.
---------- Post added at 07:07 PM ---------- Previous post was at 06:46 PM ----------
the3dolla said:
I had trouble with this when I chose fastboot omap and did the "keep data" option. It went through said it flashed stuffs, but I still had root. I changed it to fastboot snapdragon and did it again and then it worked. I have a Droid Maxx and used Pwnmymoto a month ago, which flashed my recovery, thus the need to fixor that.
Click to expand...
Click to collapse
Also, just FYI, update went fine and hotspot still works, guess I won't worry about adaway working until an easy root method is found, so I can unroot easier for kitkat.
Just chiming in to say if you all need anything let me know. I've helped a lot of people today get their MAXX back to stock so they can take the ota. Seems to be working once people get it setup properly.
Sent from my Xoom using Tapatalk 4
Post for easy access later.
Sent from my DROID MAXX via Tapatalk 4.
BMWPower06 said:
Which flash mode do we use? Fastboot [snapdragon]?
Click to expand...
Click to collapse
I have the same question.
Kinda stuck. Tried using the flash with data for my XT1080 and the screen says waiting on device. I know i did something wrong but not sure what. Any help would be appreciated.
Device is plugged in via USB. I think I have everything in the right folders. Can I just close the command prompt window without hurting the phone?
Ok I updated the instructions I wrote these instructions with the first house of moto and the naming of the fxz changed. Your FXZ file in house of moto should look like this FXZ_xt1080 or what ever phone you are using not FXZ_12.7.7_xt1080. Sorry for the confusion if you were having a problem with house of moto finding the FXZ this is why.
If this was an issue for anyone I am sorry to be honest I stopped checking this thread a while ago. I created this thread on Sept. 19 and kept trying to tell people to download the tool even if they did not need it, better to safe then sorry. I kept checking but no posts or ?'s so after a month or so seeing no one posting here I figured no one cared or wanted this tool and I forgot about it until I received a pm a few days ago. If you have a question I will try to help but please give me as much info as possible.
bigv5150 said:
Ok I updated the instructions I wrote these instructions with the first house of moto and the naming of the fxz changed. Your FXZ file in house of moto should look like this FXZ_xt1080 or what ever phone you are using not FXZ_12.7.7_xt1080. Sorry for the confusion if you were having a problem with house of moto finding the FXZ this is why.
Click to expand...
Click to collapse
That got me passed my issue. Phone rebooted and now its updating. We'll see what happens from here. Thanks for the update.
In regards to what flash mode to use its rsd for the fxz keep data or full fxz. If you want to run fast boot commands then you would chose fastboot snapdragon.
daca1001 said:
That got me passed my issue. Phone rebooted and now its updating. We'll see what happens from here. Thanks for the update.
Click to expand...
Click to collapse
You should be good now this tool is awesome you will use it again and again trust me. You will do something stupid to your phone and have a DOH!!! moment and this will fix it.
1.Download Motorola G Drivers https://motorola-global-portal.custh.../p/30,6720,905
2.Have an unlocked Boot-loader. Go to https://motorola-global-portal.custh...-your-device-a
3.Download Self Extracting Zip https://drive.google.com/file/d/0Bx3...it?usp=sharing
4.Open Self Extracting Exe
5.Extract to new Folder or Folder of your Choice
6.Antivirus Might Say its Malware (Since Its a Self Extracting Exe)
7.If it does, simply disable it, till the file extracts.
8.After files extract you should see a file called StockFirmwareFlash.bat
9.Put your device in Boot-loader mode
10.The Adb drivers are in the extracted zip so no sdk is required.
11.Now Run the file.
12.Watch the Magic Happen.
13.Phone Should Boot up With stock image.
14.If you brick or break your device im not accountable for any damage. Do at your own risk.
15.This works on moto g Boost version.
16.Pleaze Reply and give me feedback.
m.yuro said:
1.Download Motorola G Drivers https://motorola-global-portal.custh.../p/30,6720,905
2.Have an unlocked Boot-loader. Go to https://motorola-global-portal.custh...-your-device-a
3.Download Self Extracting Zip https://drive.google.com/file/d/0Bx3...it?usp=sharing
4.Open Self Extracting Exe
5.Extract to new Folder or Folder of your Choice
6.Antivirus Might Say its Malware (Since Its a Self Extracting Exe)
7.If it does, simply disable it, till the file extracts.
8.After files extract you should see a file called StockFirmwareFlash.bat
9.Put your device in Boot-loader mode
10.The Adb drivers are in the extracted zip so no sdk is required.
11.Now Run the file.
12.Watch the Magic Happen.
13.Phone Should Boot up With stock image.
14.If you brick or break your device im not accountable for any damage. Do at your own risk.
15.This works on moto g Boost version.
16.Pleaze Reply and give me feedback.
Click to expand...
Click to collapse
Drive link not working bro!
deej_roamer said:
Drive link not working bro!
Click to expand...
Click to collapse
https://drive.google.com/file/d/0Bx3fLPcfAf3BcmRmdENLWHhPaDQ/edit?usp=sharing
deej_roamer said:
Drive link not working bro!
Click to expand...
Click to collapse
Does the link work??
m.yuro said:
Does the link work??
Click to expand...
Click to collapse
Yes it does!
Boost version means version of firmware? (Boost Mobile?)
For what version can this be used?
Will it restore a German XT1032 to stock?
Yes the .imgrs was the Boost Version
Dizzyrul3z said:
Boost version means version of firmware? (Boost Mobile?)
Click to expand...
Click to collapse
You could change the official zip. With what ever you want
This will also work on the Xt1032
Yes it would
what version of stock ? 4.4.2?
It stay on unlocked bootloader screen.
"Invalid Signed Image"
So the DT 4.4.4 has root now, but it does not turn off write protection. It is a different kind of root in that what it lets you do is flash a pre-rooted system image (system.img). So you have to make any mods to the image BEFORE you flash, which is not something your average joe or joette knows how to do.
But for me at least, the Moto X didn't need much modding, just Xposed with Gravity Box, Root Cloaker and Moto Tether.
I have a Dev Ed so I don't need this exploit but I did pull all of the system images from my rooted Dev Ed. The only thing I don't know how to do is to put those into a flashable image file. Does anyone here know how to do that?
I also have the TWRP ext4 system file if that helps.
JulesJam said:
So the DT 4.4.4 has root now, but it does not turn off write protection. It is a different kind of root in that what it lets you do is flash a pre-rooted system image. So you have to make any mods to the image BEFORE you flash, which is not something your average joe or joette knows how to do.
But for me at least, the Moto X didn't need much modding, just Xposed with Gravity Box, Root Cloaker and Moto Tether.
I have a Dev Ed so I don't need this exploit but I did pull all of the system images from my rooted Dev Ed. The only thing I don't know how to do is to put those into a flashable image file. Does anyone here know how to do that?
I also have the TWRP ext4 system file if that helps.
Click to expand...
Click to collapse
thats not a boot unlock and not a write protection disable ... its just ability to install rooted custom system img ....... i think
Javajohn said:
thats not a boot unlock and not a write protection disable
Click to expand...
Click to collapse
Yes I know what it is.
Javajohn said:
... its just ability to install rooted custom system img ....... i think
Click to expand...
Click to collapse
Yes that is what I said it is.
Do you know how I can use the files I have from the system dump and TWRP nandroid ext4 file to create a flashable rooted system.img? That is what I am asking.
JulesJam said:
...
Do you know how I can use the files I have from the system dump and TWRP nandroid ext4 file to create a flashable rooted system.img? That is what I am asking.
Click to expand...
Click to collapse
edit: I misunderstood the question. Of course a CWM/TWRP flashable .zip is not a fastboot flashable system.img...
I'll 'take a stab at this'. I've done it a few times... (I'm sure there is a better guide, but I didn't attempt to find it...) You asked - please don't blame (or hate) me if I help you brick your phone... If you only modify /system, you should be able to restore using CWM/TWRP.
First, find a CWM/TWPR flashable .zip to use it's /META-INFO/ directory as a template. It's best to use a .zip made for your model (so the system mount and format work), and if you can find one for your android version even better. (Do not use an OTA .zip for this template.)
This template will likely [at least] do the following in the "/META-INFO/com/google/android/updater-script" script:
1) mount /system
2) format /system
3) copy /system directory from .zip (need to replace this directory)
4) create symlinks (might need work)
5) set permissions (probably needs work)
If you are only working on /system, then you should remove all superfluous sections (like flashing boot or the modem.)
So, first you need to prepare your new /system: In linux, take your dumped (or backup) /system and copy it to a new /system directory without symlinks. Now you have the new /system for your new flashable .zip
Then you need to modify the "updater-script" script and handle the creation of the symlinks. The easiest way to find this part of the script is locate a flashable zip (or OTA) that patches to your current model/android version. This will handle the bulk of the symlinks.
Next you need to handle the permissions in the "updater-script" script. The aforementioned .zip will also have the permissions scripted, but the root files may not be handled properly. You can find those script commands in a modern flashable zip with root 'baked in.'
Finally take your new /system and new "updater-script" and dump them in your template.... BACKUP (copy off phone) and test.
Good luck...
Ctrl-Freak said:
I'll 'take a stab at this'. I've done it a few times... (I'm sure there is a better guide, but I didn't attempt to find it...) You asked - please don't blame (or hate) me if I help you brick your phone... If you only modify /system, you should be able to restore using CWM/TWRP.
Click to expand...
Click to collapse
Yeah, I am not worrying about a brick as I can wipe my OS entirely and still get into bootloader and recovery so all is good.
Ctrl-Freak said:
First, find a CWM/TWPR flashable .zip to use it's /META-INFO/ directory as a template.
Click to expand...
Click to collapse
My TWRP nandroid of the rooted 4.4.4 system has a meta-info folder with 3 files in it - manifest.mf, cert.sf and cert.rsa.
Ctrl-Freak said:
/META-INFO/com/google/android/updater-script
Click to expand...
Click to collapse
What is this?
Ctrl-Freak said:
So, first you need to prepare your new /system: In linux, take your dumped (or backup) /system and copy it to a new /system directory without symlinks. Now you have the new /system for your new flashable .zip
Click to expand...
Click to collapse
Guess I need to learn what a symlink is first, lol!
JulesJam said:
My TWRP nandroid of the rooted 4.4.4 system has a meta-info folder with 3 files in it - manifest.mf, cert.sf and cert.rsa. !
Click to expand...
Click to collapse
I did not mean your nandroid. Find a flashable zip (made for your device/version) by someone to flash a [custom] ROM. If it flashes a ROM for your device/version, it should be a good starting point.
I looked under xda -> droid turbo and this was the only ROM I found: http://forum.xda-developers.com/dro.../moto-maxx-xt1225-cm12-0-pre-release-t3060089 It says it is for a Moto Maxx xt1225, but again it is only a template, and it might be close.
/META-INFO/com/google/android/updater-script is a text based script that controls what/how CWM / TWRP flashes. AFAIK it is within all flashable zips.
Ctrl-Freak said:
I did not mean your nandroid. Find a flashable zip (made for your device/version) by someone to flash a [custom] ROM. If it flashes a ROM for your device/version, it should be a good starting point.
Click to expand...
Click to collapse
OK thanks, I am doing this for the Moto X 2013, not DT.
Ctrl-Freak said:
/META-INFO/com/google/android/updater-script is a text based script that controls what/how CWM / TWRP flashes. AFAIK it is within all flashable zips.
Click to expand...
Click to collapse
got it.
If this is successful, would there be a way to do it on the AT&T Moto 2013 running 4.4.4?
Sent from my XT1058 using XDA Free mobile app
hexbox117 said:
If this is successful, would there be a way to do it on the AT&T Moto 2013 running 4.4.4?
Click to expand...
Click to collapse
yes, if someone has a GSM Moto X Dev Ed. I don't.
JulesJam said:
yes, if someone has a GSM Moto X Dev Ed. I don't.
Click to expand...
Click to collapse
And would we be able to use Xposed?
Sent from my XT1058 using XDA Free mobile app
hexbox117 said:
And would we be able to use Xposed?
Click to expand...
Click to collapse
Someone has to create a pre-rooted system image with Xposed installed. I think you can then add modules as long as you only do soft reboots. If you do hard reboots, you lose the modules as write protection is still on.
But someone could make a pre-rooted system image with Xposed and the modules you want installed, then it would survive hard reboots AFAIK.
I am still working on how to make a pre-rooted flashable system image, lol!
JulesJam said:
Someone has to create a pre-rooted system image with Xposed installed. I think you can then add modules as long as you only do soft reboots. If you do hard reboots, you lose the modules as write protection is still on.
But someone could make a pre-rooted system image with Xposed and the modules you want installed, then it would survive hard reboots AFAIK.
I am still working on how to make a pre-rooted flashable system image, lol!
Click to expand...
Click to collapse
Interesting. I think you should take a look at this, it sounds like it could be better than what you're trying to accomplish.
http://forum.xda-developers.com/showthread.php?p=59702152
Sent from my XT1058 using XDA Free mobile app
hexbox117 said:
Interesting. I think you should take a look at this, it sounds like it could be better than what you're trying to accomplish.
http://forum.xda-developers.com/showthread.php?p=59702152
Sent from my XT1058 using XDA Free mobile app
Click to expand...
Click to collapse
That was discussed on the DT forums, there is a problem with that on 4.4.4.
For now, the only hope is maiko1's exploit on 4.4.4.
JulesJam said:
That was discussed on the DT forums, there is a problem with that on 4.4.4.
For now, the only hope is maiko1's exploit on 4.4.4.
Click to expand...
Click to collapse
I'm not familiar with what the exploit is. Do you think you could explain it or link me to his post?
Sent from my XT1058 using XDA Free mobile app
hexbox117 said:
I'm not familiar with what the exploit is. Do you think you could explain it or link me to his post?
Click to expand...
Click to collapse
http://forum.xda-developers.com/general/paid-software/mofo-root-turbo-t3064404
So far, it is for the DT only. I want to test it on the Moto X 2013 and then the Moto X 2014. But first, a pre-rooted flashable system.img needs to be created for the Moto X 2013.
JulesJam said:
OK thanks, I am doing this for the Moto X 2013, not DT.
Click to expand...
Click to collapse
If you modify the updater-script to remove the flashing of the kernel (below), then this .zip should be perfect for your testing pleasure:
http://forum.xda-developers.com/moto-x/development/rom-krypton-v1-2-v1-3b1-6-9-2014-t2716657 (download 4.4.4 Krypton v1.4.1 )
Remove this line:
Code:
package_extract_file("boot.img", "/dev/block/platform/msm_sdcc.1/by-name/boot");
Good testing...
Ctrl-Freak said:
If you modify the updater-script to remove the flashing of the kernel (below), then this .zip should be perfect for your testing pleasure:
http://forum.xda-developers.com/moto-x/development/rom-krypton-v1-2-v1-3b1-6-9-2014-t2716657 (download 4.4.4 Krypton v1.4.1 )
Remove this line:
Code:
package_extract_file("boot.img", "/dev/block/platform/msm_sdcc.1/by-name/boot");
Good testing...
Click to expand...
Click to collapse
Thanks, I took a look at the Eclipse Moto X, which is 4.4.4 kitkat based.
http://forum.xda-developers.com/moto-x/development/rom-eclipse-moto-x-v3-2-2-4-4-2-blur-t2521509
But now that I am thinking about it, do these custom ROMs need specific kernels or can you just flash the system w/o flashing the kernel? I guess I will try it and see what happens.
If someone will give me a detailed instruction how to flash a pre-rooted firmware with xposed installed I will try to do so on my AT&T XT1053
RabbitRu said:
If someone will give me a detailed instruction how to flash a pre-rooted firmware with xposed installed I will try to do so on my AT&T XT1053
Click to expand...
Click to collapse
You have to pay $20 to get set up with the exploit, but for now, the guy is only doing Droid Turbos. It is on the paid software forum.
I am trying to see if the exploit works on the Moto X. The dev needs to get back to me but first, I need to try to create a pre-rooted system image.
JulesJam said:
You have to pay $20 to get set up with the exploit, but for now, the guy is only doing Droid Turbos. It is on the paid software forum.
I am trying to see if the exploit works on the Moto X. The dev needs to get back to me but first, I need to try to create a pre-rooted system image.
Click to expand...
Click to collapse
I don't think it will work on the 2013 X... see -> http://forum.xda-developers.com/mot...e-protection-motowpnomo-t2551113/post59731261
And remember, Beaups had an hand in the root exploit and tool for the Droid Turbo along with Jcase... So if Beaups says no, it wont help the 2013 X with 4.4.4, its a pretty sure bet that it wont.
Okay, I am attempting to #unlockthedroid, but first I will need dumps from "/dev/block". What I'm trying to do is pull off @CrashXXL methods of rooting with Write Protect=1 but allowing the potential of unlocking bootloader with Sunshine. And I don't want it to be done randomly, so this is what we'll need to do in order to get that dump:
Requirements:
Rooted
Bootloader Unlocked
Firmware to be at 4-21. It's easier for me. Or if you have anything below, it'll probably work too.
Willing to spend time; this'll take a VERY long time. So you'll need to leave your phone overnight or whatever it takes for it to finish copying.
Instructions:
Turn on ADB in settings. (If done already, next step)
Get ADB and Fastboot on your computer. (If done already, next step)
Go to ADB directory
adb shell
Click to expand...
Click to collapse
dd if=/dev/block/mmcblk0p38 of=/(any directory)/(name your file anything - just remember the location combination)
Click to expand...
Click to collapse
When done, exit ADB
adb pull /(directory)/(file name)
Click to expand...
Click to collapse
Submit the file from the ADB folder to your own Google Drive, Mega, or Dropbox. Wherever you wish.
Files we currently need:
Droid Mini mmcblk0p5, 0p13, 0p33
Droid Ultra mmcblk0p5, 0p13, 0p33
Droid Maxx mmcblk0p5, 0p13, 0p33
There is also a certain block I don't know the mmc block number to, so when someone knows where partitions.mbn is then we'll be one step closer to getting my phone flashed and tested.
Thanks in advanced!
P.S.: Staff, please move this somewhere correct if where it is right now it's not.
mr_verystock said:
Okay, I am attempting to #unlockthedroid, but first I will need dumps from "/dev/block". What I'm trying to do is pull off @CrashXXL methods of rooting with Write Protect=1 but allowing the potential of unlocking bootloader with Sunshine. And I don't want it to be done randomly, so this is what we'll need to do in order to get that dump:
Requirements:
Rooted
Bootloader Unlocked
Firmware to be at 4-21. It's easier for me. Or if you have anything below, it'll probably work too.
Willing to spend time; this'll take a VERY long time. So you'll need to leave your phone overnight or whatever it takes for it to finish copying.
Instructions:
Turn on ADB in settings. (If done already, next step)
Get ADB and Fastboot on your computer. (If done already, next step)
Go to ADB directory
When done, exit ADB
Submit the file from the ADB folder to your own Google Drive, Mega, or Dropbox. Wherever you wish.
Files we currently need:
Droid Mini mmcblk0p5, 0p13, 0p33
Droid Ultra mmcblk0p5, 0p13, 0p33
Droid Maxx mmcblk0p5, 0p13, 0p33
There is also a certain block I don't know the mmc block number to, so when someone knows where partitions.mbn is then we'll be one step closer to getting my phone flashed and tested.
Thanks in advanced!
P.S.: Staff, please move this somewhere correct if where it is right now it's not.
Click to expand...
Click to collapse
various dumps https://yadi.sk/d/UnLW2G54f5Gbx
Thanks for the SU6-7 and 5-24 dumps! But just a question: can you dump for earlier versions? I can probably get it to run Sunshine and onto the bootloader unlock. Thanks though!
mr_verystock said:
Thanks for the SU6-7 and 5-24 dumps! But just a question: can you dump for earlier versions? I can probably get it to run Sunshine and onto the bootloader unlock. Thanks though!
Click to expand...
Click to collapse
I do not think that this would work, yes You can flash the 4-21 (all bootloader partitions + kernel + system) in the QLOAD mode, as You have access to the whole flash memory.
But the trusted boot chain will not let you boot earlier bootloader and system when a newer one was already there. Phone needs to be bootloader unlocked, to boot into any version.
It's worth trying. And plus, you never know what you can find if you try...
question is it possible to get a system dump from the following version -4.2.2-SU1-15-3 trying to unbrick my device and i need certain files from that version thanks been trying to do this for a while and no one seems to wanna help out
mr_verystock said:
It's worth trying. And plus, you never know what you can find if you try...
Click to expand...
Click to collapse
I think You can get all you need from the original FXZ file.
You can get all the bootloader partitions from the motoboot.img, see my post here.
Additionally You can extract the system partition with the simg2img tool from here, but this would be the original, not the rootet image,so You would need to insert the su binary by yourself.
pizmak said:
I think You can get all you need from the original FXZ file.
You can get all the bootloader partitions from the motoboot.img, see my post here.
Additionally You can extract the system partition with the simg2img tool from here, but this would be the original, not the rootet image,so You would need to insert the su binary by yourself.
Click to expand...
Click to collapse
If this is the method it would've been done already... But no, motoboot.img cannot be extracted for all it's worth. It has aboot, gpt, and many other parts we need to create a complete set of unbricking and/or bootloader-necessary files.
happysteve11c said:
question is it possible to get a system dump from the following version -4.2.2-SU1-15-3 trying to unbrick my device and i need certain files from that version thanks been trying to do this for a while and no one seems to wanna help out
Click to expand...
Click to collapse
Sigh... I wish, my friend. I know what you want, but nobody's willing to provide it because of. @CrashXXL is nice enough to provide the unbricking files but nobody is willing to dump for SU1.
mr_verystock said:
If this is the method it would've been done already... But no, motoboot.img cannot be extracted for all it's worth. It has aboot, gpt, and many other parts we need to create a complete set of unbricking and/or bootloader-necessary files.
Click to expand...
Click to collapse
it actually is as easy as this, the motoboot.img file is just the bootloader partition images put into one file plus a 1024 bytes header. I have extracted these image and compared them with the dumps from my own phone and they are identical, so this motoboot is not compressed or encrypted.
If You still do not believe me just check for yourself, dump for example the aboot partition from your phone and compare it with the motoboot image from the FXZ file for your firmware version, I think you will find the aboot image inside the motoboot image at some 512bytes aligned offset (you can get the offset from the header, see the description in my post linked above)
Edit: I have added my code I wrote to extract the motoboot image to this thread
happysteve11c said:
question is it possible to get a system dump from the following version -4.2.2-SU1-15-3 trying to unbrick my device and i need certain files from that version thanks been trying to do this for a while and no one seems to wanna help out
Click to expand...
Click to collapse
Not sure if you or anyone can do anything with it but I have a twrp backup of the boot and system from su1-15. Let me know if anyone wants it.
Sent from my XT1080 using XDA Free mobile app
@mr_verystock are you still working on this?
Yes, I'm working on it. But I'm dealing with school, along with patching up a broken computer which I am planning to use for my daily driver. So currently I'm installing Linux, to do a mbn split.
Oh, and I kinda messed up my Droid Maxx while doing this... Don't worry, it's a backup, I have a Droid Mini as main.
WOHOO!!!!!!!!!
Is it rooted?
What version of Android are you on?
Ya still working on this?
Hey man. I have a (probably useless) Droid Mini "dev" edition (on su6-7). Today, I will be receiving a droid maxx on 4.4 (idk if its 19.5.3 or 19.6.3 yet) and i will be unlocking it with sunshine. if you still need files/help, i can help. (when you do start work on this again). my sincere hope, aside from a bootloader unlock for the folks on 4.4.4) is that somehow this will help the Turbo folks. (mofo root is good, but bl unlock is better). let me know if and when i can help man.
Hey, yeah, please let me know if you need anything once you get started again. I have a droid ultra that I just bought off groupon for $80.
YYUSSSSSSSSSS!!!!!!!!!!!!!!!!!!!!! Thank you VERY MUCH!!!!
Great thing I have a Droid Mini. Can you dump cid.mbn for 4.4? That's the file I want to mess with currently after you unlocked.
me or him, broheim?
edit: duh, me. ill have it pulled and uploaded tomorrow around noon
Is it uploaded to a hosting site or not?
i never saw any reply dude. i can upload what i have...but my mini is on 4.4.4. i have a maxx on 4.4, but no dice on that build. i thought for a moment i was crazy. if it helps you to have either or both, i will pull them right now and throw up a link to my drive.
Hm... I can't do anything with the 4.4.4 one, I'll take the Maxx on 4.4 cid.mbn. Sorry if there were any confusion!!!