Database Users

Unpack stock System.img?

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?

[GUIDE] House of Moto

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.

SDCARD hard brick recovery WIP, need dumps

I am working on getting a proper MJE SDCARD debrick image. I will need memory dumps of the boot partitions.
From ADB shell or terminal emulator run the following command
dd if=/dev/block/mmcblk0 of=/sdcard/unbrick.img bs=512 count=524288
This will place a file called unbrick.img into /sdcard (not your actual memory card (extSdCard) but your internal device memory. All I need you to do is upload this file anywhere you see fit so I can download it. I greatly appreciate your time!
At this time, I am only looking for retail SM-N900V MJE dumps.

ryanbg said:
I am working on getting a proper MJE SDCARD debrick image. I will need memory dumps of the boot partitions.
No sensitive data will be dumped with this command, and you will be helping the community out greatly if you have the time.
From ADB shell or terminal emulator run the following command
dd if=/dev/block/mmcblk0 of=/sdcard/unbrick.img count=524288
This will place a file called unbrick.img into /sdcard (not your actual memory card (extSdCard) but your internal device memory. All I need you to do is upload this file anywhere you see fit so I can download it. I greatly appreciate your time!
At this time, I am only looking for retail SM-N900V MJE dumps.
Click to expand...
Click to collapse
Retail or DE? Or does it matter?

cam30era said:
Retail or DE? Or does it matter?
Click to expand...
Click to collapse
Preferably retail, but if you have DE, go ahead anyways. Maybe I'll be able to find something new. As long as it's MJE.

ryanbg said:
Preferably retail, but if you have DE, go ahead anyways. Maybe I'll be able to find something new. As long as it's MJE.
Click to expand...
Click to collapse
That may be a problem. While baseband is MJE, ROM is CM11. That surely won't work. Sorry about that.

cam30era said:
That may be a problem. While baseband is MJE, ROM is CM11. That surely won't work. Sorry about that.
Click to expand...
Click to collapse
It won't grab anything from CM11, don't worry. These are just the boot partitions which would remain unmodified after installing CM11.

Deleted

PM sent.
Retail N3, up to date firmware.
<Note3>

OP: did you find or get a copy of a debrick img file for the SM-N900V? my retail edition is definitely hard bricked.

trevorcobb said:
OP: did you find or get a copy of a debrick img file for the SM-N900V? my retail edition is definitely hard bricked.
Click to expand...
Click to collapse
Let us know your results from the thread over in the General forum:
http://forum.xda-developers.com/verizon-galaxy-note-3/general/howto-recover-hard-brick-t2834419

bftb0 said:
Let us know your results from the thread over in the General forum:
http://forum.xda-developers.com/verizon-galaxy-note-3/general/howto-recover-hard-brick-t2834419
Click to expand...
Click to collapse
Long time no see old friend.

ryanbg said:
Long time no see old friend.
Click to expand...
Click to collapse
@ryanbg
Sorry for not getting in touch - I know I disappeared as if I had died. Life - and work - intervened to the point of needing to drop something on the floor, and unfortunately that was my XDA involvement. (As it is, even this post is a little bit of hooky). But all is well; I see you are still fighting the good fight. Thanks for your efforts.

[FXZ] 5.0 22.21.11 Verizon Moto X 2014 *ONLY*

WARNING: You REALLY need to UNDERSTAND and read EVERYTHING or you MAY brick your phone!
Purpose of this thread:
To get you, the Verizon Moto X 2014 owner, from any version to 5.0 ( LXE22.46-11).
Things you will need:
FXZ LXE22.46-11
Thanks @stras1234
Instructions:
Use the RSD Flasher with KEEP DATA to flash this on your phone with RSD.
OR
Use the House of Moto with KEEP DATA to flash this to your phone with fastboot.
OR
RSD Lite 6.2.4

Has anyone done this? Mighty tempting... Didnt even know this was possible!

I'm not sure what you mean by "done this", exactly, but, if you mean flashing this FXZ to upgrade, then yes. It's the same update as the OTA that's pushing out now...this is just the full version rather than the update zip. Is that what you were asking?

Do you mind reuploading both of those tools to a new file hosting service? Because I can't see either of them because I'm not a member of DroidRZR.com and I don't intend to be.
Or just providing the direct link to a upload or mirror would be great.

Just use RSD 6.2.4 in that case. I keep the tools I wrote in one place only because there's a lot of instructions that go with it and it's easier to support if it's in one place. But the link to RSD is to a mediafire download so you should be able to grab that no problem.

Don't bother, just updated ota. Rocking lollipop now

I followed your root and boot loader unlock on the xt926 I had. You being on the moto x makes me very happy. I bow down to you

SamuriHL said:
Just use RSD 6.2.4 in that case. I keep the tools I wrote in one place only because there's a lot of instructions that go with it and it's easier to support if it's in one place. But the link to RSD is to a mediafire download so you should be able to grab that no problem.
Click to expand...
Click to collapse
Can you provide the direct links to both then? I'd like to be able to clean flash this at some point.

bmwh0r3 said:
I followed your root and boot loader unlock on the xt926 I had. You being on the moto x makes me very happy. I bow down to you
Click to expand...
Click to collapse
I don't own any of these devices. LOL

The fact you are so good with them is even more amazing.

SamuriHL said:
I don't own any of these devices. LOL
Click to expand...
Click to collapse
You're probably still rocking the Bionic

texassax said:
You're probably still rocking the Bionic
Click to expand...
Click to collapse
It's around. I'm rocking an NX6 right now. Love it.

SamuriHL said:
It's around. I'm rocking an NX6 right now. Love it.
Click to expand...
Click to collapse
Trying to extract the system.img - is there a catch with Moto devices? I can't seem to get anywhere with mounting it on Windows or OS X.

I have consulted the great and powerful(tm) search engine thingie and determined your fate on this endeavor as documented with the following scroll...
http://forum.xda-developers.com/showthread.php?t=2294909
Sent from my SM-P600 using Tapatalk

SamuriHL said:
I have consulted the great and powerful(tm) search engine thingie and determined your fate on this endeavor as documented with the following scroll...
http://forum.xda-developers.com/showthread.php?t=2294909
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse
LOL - If only it were that easy. Anyone else?

SamuriHL said:
I don't own any of these devices. LOL
Click to expand...
Click to collapse
me neither

joderme said:
Trying to extract the system.img - is there a catch with Moto devices? I can't seem to get anywhere with mounting it on Windows or OS X.
Click to expand...
Click to collapse
Extracting system.img on Windows is simple Just do the following:
1. You need two utilities: sparse2img.exe and ImgExtractor.exe
2. Download and extract both in one folder
3. Put system.img in the same folder
4. Run CMD from that folder
5. Run: sparse2img system.img system_new.img
File system_new.img will be created
6. Run: ImgExtractor system_new.img
Folder system_new_ will be created. You will find all extracted files and folders here

Al936 said:
Extracting system.img on Windows is simple Just do the following:
1. You need two utilities: sparse2img.exe and ImgExtractor.exe
2. Download and extract both in one folder
3. Put system.img in the same folder
4. Run CMD from that folder
5. Run: sparse2img system.img system_new.img
File system_new.img will be created
6. Run: ImgExtractor system_new.img
Folder system_new_ will be created. You will find all extracted files and folders here
Click to expand...
Click to collapse
Welp - I feel like an idiot. I saw this method elsewhere, however, it seemed like it would only work with system1.sparse files as other updates have had multiple files for system.img.
This worked - thanks!!!
Now to find the APKs for moto assist.

This is quite interesting as none of the APKs will work on a Nexus 6.
APKs from the pure edition seem to have little problem.
I would think that the Nexus 6 wouldn't have a problem running these.

Root ANY LG G4 Variant 100% Success Directives | Root Injection | Less Bricks

Hi everyone. As I found out there's root for the G4 but doing this isn't easy especially if your variant is hard to find or has less users. This may result in you waiting for longer than you should. This thread is for those who can take things into their own hands and do it themselves. The tools are available everywhere but I'll give you the best order and steps. I'm using the China LG G4 H818 Dual SIM variant but this method is UNIVERSAL FOR ALL LG G4s.
The process will involve extracting a system image, injecting root and reflashing this image. Most of the steps are effortless and need just copy and paste with keen eyes. Do it slowly. You need an Ubuntu installation for step 2 of this 3-step tutorial. I used universal USB installer and put in on my 8GB USB. Anywhere will do so far as it boots&works. Beware this thread is not dumb-proof but this will not wipe your data or void your warranty if done successfully.
Step 1 -> Getting the proper system image.
Check here and skip to step 3 if you have your rootedsystem.img
>Don't worry because this doesn't require searching. It is from your device. Every device has a system partition and this method will pull it out as an image without root required.
1--Make sure all drivers are installed properly. I'll not be talking about this. We're on XDA not kindergarten.
2--Download the LG_root file or send command file from here and extract it. US Carrier specific check here
3--Put your device in download mode and connect it to your PC.
4--Open(double-click duh) port.bat and make sure to write down the number after com. There maybe different com numbers but choose the com on the DIAG1 line and write down that number. This is important.
5--Hold shift and right-click in any empty space in the extracted folder. Choose open command windows here.
6-- In that copy and paste this
Code:
[FONT=Lucida Console][COLOR=#ff8c00]Send_Command.exe \\.\COM[/COLOR][COLOR=#00ff00][*insert your number here][/COLOR][/FONT]
7--Now you're in send command mode. Nothing looks different on your phone but that's ok. It should just remain in download mode.
8-- On the computer screen in the window you now see #.
9--Now in this post copy the Backup system to internal storage command specific to your device model number. Check in you settings >general >about if in doubt. This is the most important step. Copy the whole line of code. Highlight with your mouse, select everything on the line and copy.
10--You didn't come all this way to fail so do it. Remember it is device model specific.
11-- Paste it in the command window and hit enter. It should take a while so wait until you see#reappear.
12--Now typeLEAVEall in capital letters. Your device will reboot. Check using the file manager if you have a file called system.img in your internal storage. If yes step 2 is next and you did well. If no repeat it and follow the steps properly. Make sure drivers are installed especially windows 10/8/8.1 users. Check device manager
Step 2 -> Root injection.
1--Prepare your Ubuntu USB or virtual machine or computer.
2--Download inject_root zip from here and extract.
3--Copy the system.img from your phone to the extracted inject_root folder on your PC.
4-Reboot into Ubuntu.
5--Here open a terminal.
6--Gain root access on Ubuntu by typing or copy and paste sudo -i
7--You should either be asked for your password which you have to enter or if you used a USB drive like me you'll see the name change to[email protected]
8--Navigate to the inject_root folder by using cd commands. This can also be done by typing cd then [space] then dragging and dropping the folder into the terminal and hitting enter.
9--You'll now see the name in the terminal become longer with the name of the folder in it.
10--Now type chmod +x autoroot.sh
11--Hit enter then sudo ./autoroot.sh
12--If you get any thing like command not recognized or something of the sort use sudo sh autoroot.sh
-That worked for me.
13--If you're successful the name of the file should change from system.img torootedsystem.img
-Please note don't rename the files. Leave them as they are.
14--Now go back to Windows let's finish this.
Step 3 ->Root
1--Transfer the rootedsytem.img to your phones internal storage.
2--Put your phone in download mode and connect it to your PC.
3--Get into send command mode as in step one.
-Put your device in download mode and connect it to your PC.
-Open port.bat and make sure to write down the number after com. There maybe different com numbers but choose the one that has DIAG1 on the same line as it. Note it down this is important.
-Hold shift and right click in any empty space in the extracted folder. Choose open command windows here.
- In that copy and paste this
Send_Command.exe \\.\COM[*insert your number here]
-Now you're in send command mode. Nothing looks different on your phone but it's find. It should just remain in download mode.
4-Now grab your command to flash system.img line of code from this post. It isn't the same as step one. Copy that an paste in the command window. Make sure it is for your device. They are model specific.
5--This should take a while so wait until you see the # again.
6--After thatLEAVEand upon reboot you should have root.
To Un-root just flash a KDZ file compatible with your device here.
Testimonies
Spudnubs said:
Rooted H812 10g for my fellow Canadians. Enjoy!
https://www.androidfilehost.com/?fid=24052804347821979
Click to expand...
Click to collapse
Wildsheep said:
This root method works for my G4 purchased in Singapore (H815 SEA)
Click to expand...
Click to collapse
luongquang said:
Thanks to @hackarchive, H818p10f done with tut.
Click to expand...
Click to collapse
player911 said:
Fantastic. This method will also ease devs for future rooted firmwares. I really cannot see LG being able to patch this, since this is basically a 3rd party LG Flashing tool. If they block this method, then their own tool will ultimately die with it.
Click to expand...
Click to collapse
GavTheStoner said:
Fantastic! I had almost given up hope of root on my EE LG G4. Have just used this method and now rooted perfectly!
hackarchive You rock! Have a thanks!
Click to expand...
Click to collapse
articular said:
everything worked fine and i successfully got my g4 rooted
my variant is H815TR
all steps easy only the ubuntu part was a bit hard especially for a windows user ( finding an ubuntu version and usb install etc. not root injection part)
ty ty ty again )
Click to expand...
Click to collapse
rirozizo said:
if it were for me to decide if we should delete the low effort root method, i'd totally delete it.
"The more 'manual', the better"
Click to expand...
Click to collapse
Moe5508 said:
Only method that roots my device successfully...I updated to 10e of the H815P and using this method (and only this!0 I was able to root my phone...ah felt so good...
The other 1-click rooting methods I came across in other parts of this forum just fail on the G4...
Click to expand...
Click to collapse
Marshmallow and root situation read here
Hit thanks if you appreciate. Hope I helped.
Credits to them whom without this won't be possible :good:
Thecubed
Team Codefire
ManhIT

This is a good method, thanks for writing this up.
I would like to add a few points....
I recommend you do keep your original system.img on your phones regular internal storage. If you encounter any boot issues you can then re-enter download mode and write the original system.img over the top of the failed root attempt. Use the same command from "step 3: root" but replace rootedsystem.img with system.img. This should still be on your phone from step 1 and will recover your phone from a failed root injection attempt. Note that it will not recover your phone if you messed up the dd command and overwrote other partitons. Be sure to use the right dd command and cut n paste to prevent seek/offset typeos.
I also recommend that you keep a backup of your system.img on your pc. When you run autoroot.sh in step 2 the copy on your pc will be renamed and patched. I suggest copying system.img somewhere else first, or re-copy it off your phone.
Additional credits to blog.lvu.kr. This is the blog of the hobbyist who reverse engineered the download mode protocol, created send_command.exe and gave it to the world. Kudos to you.

How is this any easier than the original method....if anything this requires even more work

kyle1867 said:
How is this any easier than the original method....if anything this requires even more work
Click to expand...
Click to collapse
It's for those who have rare variants.

psycho_asylum said:
It's for those who have rare variants.
Click to expand...
Click to collapse
Then you should probably take out the claim that this method is easier from the OP

Can this be used to inject Xposed as well for those of us with locked BLs.

djkinetic said:
Can this be used to inject Xposed as well for those of us with locked BLs.
Click to expand...
Click to collapse
No, we need to wait for a custom recovery.

psycho_asylum said:
No, we need to wait for a custom recovery.
Click to expand...
Click to collapse
Just used flash fire it worked rocking xposed now on 810!

djkinetic said:
Just used flash fire it worked rocking xposed now on 810!
Click to expand...
Click to collapse
Oh nice! I wasn't adventurous enough to try it. I'll make a system backup and give it a whirl!

Very nice thread, thank you. The steps were short, few, and fairly concise.
I was waiting for something like this where I could modify my own image and I wouldn't have to wipe everything or replace it with a new image.
One thing you might want to mention is that if your phone is encrypted, you'll need to unencrypt it first.
Can anyone link me to some instructions on how to disable OTA updates for an unlocked/international H815T?

kyle1867 said:
How is this any easier than the original method....if anything this requires even more work
Click to expand...
Click to collapse
This is what XDA is all about. It tells you how to inject root into your OWN system image. it's the opposite of spoon feeding. it's about teaching members how to do things for themselves. Too many people come here expecting to be spoon fed and have thigns done for them. This thread teaches people how to do their own work, while learning something at the same time.
Good work OP! :good:

the_scotsman said:
This is what XDA is all about. It tells you how to inject root into your OWN system image. it's the opposite of spoon feeding. it's about teaching members how to do things for themselves. Too many people come here expecting to be spoon fed and have thigns done for them. This thread teaches people how to do their own work, while learning something at the same time.
Good work OP! :good:
Click to expand...
Click to collapse
Thanks. I guess people don't know what XDA is about. Seeing noobs and others trying to spit on hard work when I used my time and device as Guinea pig. Also people don't know this is almost brick-proof because the system image if from their devices. Unless they use wrong commands but all here is just copy and paste. They see lot's of text and get cold feet. Anyways will be updating the OP with system images. If yours is available please share. If you see your image available and you have drivers and LG_root downloaded proceed to step 3.

The only downside is that I have to drag out my windows laptop instead of doing everything on the ubuntu machine I use at work.
But if that's the biggest of my problems then I don't really have a problem

hi, thx for this tutorial, looks good
when flashing back the rooted img,does it wipe everything ? apps, data ... etc
thx
EDIT: just correct me if im wrong
using this method WILL NOT wipe everything on my device cause im rooting my system with everything on it
correct ???
must make sure before i go ahead
thx

How to calculator extractly bs/seek/count ?

Is there a possibility of any personal data being written to /system on a phone during normal use? I can provide 10c Optus AU (carrier 505-02) if I can be sure its not identifying, but ive been using the phone a couple of weeks.
Download link:
https://www.androidfilehost.com/?fid=24052804347799013

optiplex2012 said:
using this method WILL NOT wipe everything on my device cause im rooting my system with everything on it
correct ???
Click to expand...
Click to collapse
correct.
---------- Post added at 06:01 PM ---------- Previous post was at 05:29 PM ----------
djkinetic said:
Can this be used to inject Xposed as well for those of us with locked BLs.
Click to expand...
Click to collapse
HTCuser90 said:
How to calculator extractly bs/seek/count ?
Click to expand...
Click to collapse
I would also like to know this. You can resolve system by running the following. Note that this is for the H815T and is not the same on all variants.
# ls -lZ /dev/block/bootdevice/by-name/system
You'll get something like:
lrwxrwxrwx root root ubject_r:block_device:s0 system -> /dev/block/mmcblk0p47
Which tells you the actual block device (partition its on).
And you can see the size of that with:
# cat /proc/partitions
where you see:
major minor #blocks name
<snip>
259 15 4239360 mmcblk0p47
<snip>
However I dont know how to identify how large a block is or how to calculate the start offset in the main partition.

ok, it worked great
wasnt easy, since im not so familiar with using ubuntu, but all is ok
the explanation of the how to... was great and nothing lost
my H815L is now rooted
thx guys

djkinetic said:
Just used flash fire it worked rocking xposed now on 810!
Click to expand...
Click to collapse
I know it's kind of going off topic, but I figured I'd mention that Flash Fire doesn't work on VS986. It just goes to a black screen and sits there forever. I left it sit for almost an hour. I saw elsewhere it has something to do with automount, I'll have to mess with it further.

hackarchive said:
Hit thanks if you appreciate. I spent hours trying to root so hope I helped.
Click to expand...
Click to collapse
Appreciated but you should include a way to unroot (undo) as well, ie how do we get back to stock (if required) ?