yashsingh1/xdaforums huggingface dataset:
[T-Mobile Samsung Galaxy Note 3] Mcheverez:
sure there is... i suggest you to root your device... its very easy and means no harm unless you start playing with system stuff but basically it just unleash your phone full power.... and once you rooted you just install titanium backup which is the best back up ever (in my opinion) and u do a full system data/user data back up which it will save ALL phone and apps settings and data and you just save the titanium back up folder to your pc and then put it back once you done flashing... also be careful once u flash and you are reverting the back up since the error might be a misconfiguration somewhere... but u can choose manually which stuff u wanna restore like accounts messages phone call history and more... also remember to root back again and installing a custom recovery like TWRP or CWM so i can flash stuff and back up and get a better recovery experience and also u could flash the SD card write fix since on newer versions phone wont let you write data directly to a SD card.... hope it helps at all and good luck
[Moto G Q&A, Help & Troubleshooting] SH1M4BD3:
Hii am new on moto g things..let's said that am not happy with my ow xt1033 specifically on its dual sim abilities, well some and even much custom ROM that I really want to try most of them only support single sim variants and am sick with that. Some research that you can convert your device to another variants eg. Xt1033 to GPE, xt1033 to xt1032.. Both of them I already done, Yea its work my second sim disappear from setting at least it works on stock ROM or some custom ROM eg. Newly releases The AOSP 5.1 even to make it works correctly it needs some command pushed to build.prop well , some like SlimLP,DU, , Vanir even I've converted the devices they don't even works facing some FC's right after flashing. The point is did I missed some tutor on how to completely converting the devices, or this convert thing was actually useless and fail to manipulate some ROMs to make them works on converted x1033???
[P3300, MDA Compact III  upgrading etc.] IRREAL:
It is possible to change the first image what it appears on the start??
[P3300, MDA Compact III  upgrading etc.] rvbcrs:
Hopefully I have the answer for you tomorrow! I'm almost there!
[P3300, MDA Compact III  upgrading etc.] arvind09:
Any luck?Waiting for your results.
[P3300, MDA Compact III  upgrading etc.] biranouran:
here it is, pls check.
[P3300, MDA Compact III  upgrading etc.] mikealder:
The attached file refuses to open? - any chance you can re-upload it after checking if something is wrong? - Mike
[P3300, MDA Compact III  upgrading etc.] zippyioa:
Same problem for me - I cant open the zip as Winzip says it "cannot open the file, it does not appear to be a valid archive"

I am keen to change my boot screen because I want to try something I read in another forum. The idea is to add your contact details at that point.

It will be more difficult for a theif to change than the "display identification information when device is turned on" option and a hard reset shouldn't remove it!!

I hope someone finds a way soon.
[P3300, MDA Compact III  upgrading etc.] Nooky:
I used WinRAR to unzip it and that works fine.
[P3300, MDA Compact III  upgrading etc.] biranouran:
just change the .zip in .rar, it will work.
[P3300, MDA Compact III  upgrading etc.] IRREAL:
Ok..perfect!

I must now unlock the CID..someone has the necessary tools??
[P3300, MDA Compact III  upgrading etc.] Samson711:
so far i guess you can only unlock the CID by paying imei check... Sorry
[P3300, MDA Compact III  upgrading etc.] pythons:
hm.

im try this utility with 2 example images and no result, my boot screen dont change :(

htc p3300, unlocked, 2 files copyed to windows folder, cab file installed, soft reset... no result, what can i do?
[P3300, MDA Compact III  upgrading etc.] j0kkk3r:
Nothing changed ... Anyone get this "thing" to work?

Cheers 8)
[P3300, MDA Compact III  upgrading etc.] poltep:
My M700 don't change as well
[Galaxy S6 Q&A, Help & Troubleshooting] tailgunner9:
Will T-Mobile S6 have locked bootloader??? Will a T-Mobile work on AT&T LTE networks if sim unlocked???
[Galaxy S6 Q&A, Help & Troubleshooting] phobia09:
Chainfire already confirmed root for the T-Mobile S6 and S6 Edge, which confirms unlocked BL. Time will only tell whether or not it works well with AT&T, though it likely will.
[Galaxy S6 Q&A, Help & Troubleshooting] garwynn:
Correct. Tmo already confirmed unlocked, which means Sprint likely as well.

The big question is AT&T and Verizon... has a way been found to accomplish this now on Exynos?
[Moto X General] JulesJam:
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.
[Moto X General] Javajohn:
thats not a boot unlock and not a write protection disable ... its just ability to install rooted custom system img ....... i think
[Moto X General] JulesJam:
Yes I know what it is.

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.
[Moto X General] Ctrl-Freak:
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...
[Moto X General] JulesJam:
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.

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.

What is this?

Guess I need to learn what a symlink is first, lol!
[Moto X General] Ctrl-Freak:
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://xdaforums.com/droid-turbo/orig-development/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.
[Moto X General] JulesJam:
OK thanks, I am doing this for the Moto X 2013, not DT.

got it.
[Moto X General] hexbox117:
If this is successful, would there be a way to do it on the AT&T Moto 2013 running 4.4.4?
[Moto X General] JulesJam:
yes, if someone has a GSM Moto X Dev Ed. I don't.
[Moto X General] hexbox117:
And would we be able to use Xposed?
[Moto X General] JulesJam:
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!
[Moto X General] hexbox117:
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://xdaforums.com/showthread.php?p=59702152
[Moto X General] JulesJam:
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.
[Moto X General] hexbox117:
I'm not familiar with what the exploit is. Do you think you could explain it or link me to his post?
[Moto X General] JulesJam:
http://xdaforums.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.
[Moto X General] Ctrl-Freak:
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://xdaforums.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:

package_extract_file("boot.img", "/dev/block/platform/msm_sdcc.1/by-name/boot");

Good testing...
[Moto X General] JulesJam:
Thanks, I took a look at the Eclipse Moto X, which is 4.4.4 kitkat based.

http://xdaforums.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.
[Moto X General] RabbitRu:
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
[Moto X General] JulesJam:
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.
[Moto X General] KidJoe:
I don't think it will work on the 2013 X... see -> http://xdaforums.com/moto-x/orig-development/kill-write-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.
[Moto X General] JulesJam:
Thanks.

I am pretty sure that jcase did not. Idk about beaups.

edited- beaups just said he had no idea.

FYI - maiko1 said he would get back to me about it when it wasn't so busy for him so I think there is hope.
[Moto X General] JulesJam:
The final form of the file must be a ".img" file not a ".zip" file. It has to be flashable by fastboot.

From all I am reading, I need to do this in linux, which idk anything about and would have to install in a virtual machine.

If anyone knows how to repackage the raw system files into a ".img" file using linux, please let me know.
[Moto X General] JulesJam:
jcase says root is coming for the moto x 2014 on 4.4.4 using MoFo so that means it will work for the moto x 2013. I have the pre-rooted system files for a Verizon Moto X 2013 4.4.4 in "raw" form but they need to be packaged into a system.img file that can be flashed by fastboot (not a custom recovery zip file).

https://twitter.com/jcase/status/581105182492135424

Can anyone help me repackage them? This needs to be done in linux.
[Moto X General] jwort93:
Not true, at least for the modules I've been using on my Droid Turbo with Moforoot. I have xposed installed along with gravity box, flat style bar indicators and flat style colored bars, and all survive a hard reboot. The only thing the system image needs is xposed itself installed before hand and you can install modules just fine normally.
[Moto X General] JulesJam:
Even better!!!!! Do you know how to repackage the raw system dump files into a system.img?
[Moto X General] jwort93:
Not really, I used a prebuilt image from someone that had already added the backed for xposed. Have you taken a look at this? http://xdaforums.com/droid-turbo/general/tutorial-how-to-modify-turbo-images-t3064595
[Moto X General] JulesJam:
Yeah, but it shows you how to undo a system.img and then mod it. I asked on that thread and maybe someone will answer me.
[Moto X General] Fadelight:
I wonder if sunshine will become available with this root method. Fingers crossed.
[Moto X General] KidJoe:
I may have misspoken.. But I thought JCASE did review the exploit for the Turbo, and does know quite a bit about the 2013 X. So when he said NO, I did put some faith in that.

If SOMEONE can come up with something, that would be great for those who need it.

---------- Post added at 09:02 AM ---------- Previous post was at 08:58 AM ----------

Wait, What did I miss here? your statement reads as if your are saying... since its coming for the 2014 X, that it must also be coming for the 2013 X.

I didn't think the 2014 and 2013 X's were that similar.
[Moto X General] JulesJam:
Idk if he reviewed it or not. But what happened on the DT forum is maiko1 (a new member) posted he had rooted a DT and as would be expected, people questioned that - even jcase. Then when jcase found out maiko1 was someone he personally knows, he let everyone know that maiko1 was legit.

Then when maiko1 posted the link to his paid exploit, jcase asked that it be moved to the paid software forum.

That is all I know based on what was posted on the DT forums, but also, that was all that was posted. So unless you have other information from elsewhere, that is all that we know happened.

I think you are getting bootloader unlock via Sunshine confused with root via MoFo. AFAIK, jcase said No to him working on a bootloader unlock for the Moto X. He did not address root via MoFo for the Moto X 2013 b/c he is not the one working on root for the Moto X - maiko1 is. But jcase did say that root via MoFo for the Moto X 2014 is coming. AFAIK, jcase is not working on root via MoFo though - that is maiko1, it is just that jcase and maiko1 are friends so he knows what is up with MoFo.

AFAIK - and I got this from reading what others are posting on the DT forum - maiko1's exploit is dependent on the version of Android and will likely work for any Motorola device running kit kat 4.4.4.

From what I have read, and this may or may not be correct, I am just telling you what people are posting, the exploit allows fastboot to flash unsigned system images. It is not specific to the DT, rather it is specific to Motorola devices running 4.4.4. So that is why it will work for the Moto X. It may even work once lollipop is rolled out.

Also, I specifically asked maiko1 if it would work for the Moto X 2013 and offered to use my device to test it and he responded that he will get back to me when he is less busy. He did not say no and hopefully he would not lead me on if he didn't think it would work for the Moto X 2013. And now from what jcase has posted, maiko1 is working on getting it to work for the Moto X 2014.

I haven't bothered maiko1 again b/c I was trying to get a pre-rooted system.img file ready to go before I asked him again. But it doesn't look like anyone is able to help me with that :(

My Moto X 2013 is a dev ed so I was going to relock the bootloader to see if it would work since I can always unlock it again. Plus my device is still under warranty so if I brick it, no big deal. So if [MENTION=5697730]maiko1[/MENTION] would like to see if his exploit works on a Moto X 2013 running 4.4.4., I am willing to test it on my relocked dev ed Moto X 2013 running 4.4.4.

But we need a pre-rooted system.img of 4.4.4 to test it. That is why I was trying to get help with this. I have all of the system files of a rooted 4.4.4 for a Verizon Moto X 2013 from doing an adb pull - I just don't know how to package them into a system.img file that fastboot can flash.
[Moto X General] Orch4rd:
Try extracting all the files you have onto a new .zip compression folder. Then rename it entirely, including the extension name .zip, as system.img.

If zip compression folder doesn't work try it using the same method with winrar and 7zip.
[Moto X General] JulesJam:
That for sure doesn't work. You have to use linux to be able to get it packaged correctly. That much I am sure of.

An ".img" file is not a ".zip" file.
[Moto X General] Orch4rd:
Yeah sorry, not much of a linux user. But here's the thing, an .img file indeed isn't a .zip file, but you can convert these extensions to each other, or to other extensions.

Like a a .zip file can be converted to a .iso file, and vice-versa simply by changing the extension name, and it works when you try to access a .zip-converted file from an .iso on Win 7+. Here, an image file like .img is similar to an .iso file; If anything you should be able to change the file's name.

I'm not certain it would read the system.img file, but it shouldn't hurt to try.
[Moto X General] Ctrl-Freak:
Sorry for leading this thread in the wrong direction before. I am trying to redeem myself. Below is a start. I tested this through making the new image, but I do not have the time to continue as I am going out of town.

On phone, make an image of the ext4 /system partition. Make sure you have 1.5+ gigs of free space on your sdcard:

su
dd if=/dev/block/platform/msm_sdcc.1/by-name/system of=/sdcard/Download/system_orig.img

Next copy /sdcard/Download/system_orig.img from phone's sdcard to Ubuntu linux 64 bit

On Ubuntu:

Find "make_ext4fs" binary

for android

or compile it yourself: ( http://xdaforums.com/showthread.php?t=2600364 )

Mount the original ext4 image and create a new system image:

mkdir sys1
sudo mount -t ext4 -o loop system_orig.img sys1
sudo make_ext4fs -s -l 1610612736 -a system system_new.img sys1/

Notes:

Apparently you can make the new image smaller that the one I made (with the -l parameter), but this size should also work.

There may be an issue with selinux requiring the "-S <file>" parameter. I am not yet sure about that.

If selinux is not a factor, you are done and can fastboot flash system system_new.img

Having already soft bricked my phone this weekend, I didn't test flashing the new image...

Apparently motorola stock images have an unusual header and footer. (Probably why we need special mfastboot.) I've read this header/footer is optional if the phone is unlocked.

Happy testing...
[Moto X General] JulesJam:
This post explains what has to be done, but again, it has to be done using linux.

http://xdaforums.com/showthread.php?t=1588461

However, I am not sure how to do it if you don't unpack a system.img first. I am not sure if repacking the adb pull files would work or not.

After maiko1 opens up his tool to the Moto X 2014, I will PM him again and again offer to do this with my Dev Ed to test to see if it works for the Moto X 2013 and perhaps he would be able to create the fastboot flashable pre-rooted system.img file. I can modify the build.prop no problem to enable free WiFi tether and I can install Xposed so that is in the pre-rooted system.img file also.
[Moto X General] Ctrl-Freak:
After working for hours with make_ext4fs using the -S parameter to handle selinux, I gave up. Apparently you will have to use the ext2simg utility, and if you make any changes to /system outside of the phone, you will need to handle the selinux permissions manually. For our purposes, the following is the only thing you will need to do in linux, after you copy system_orig.img (created in my last post) from the phone:

On ubuntu, find the ext2simg binary or compile it yourself. ( http://xdaforums.com/show....php?t=2600364 ). Then:

ext2simg -v system_orig.img system_new.img

That should do it, but I will wait for it to be needed before I test it... I would, however, like to hear if it works for someone else...

To test, execute this with the phone connected to the PC: (be sure and have a backup, and do not blame me if there is a problem)

fastboot flash system system_new.img
[Moto X General] CrashXXL:
Now, I also work on getting root

Earlier I did root for Droid Mini,Maxx,Ultra

Phones are technically the same, the problems with porting method will not.

root will be free, everyone will be able otblagadarit and help me buy a new phone, maybe the last was killed while trying to get new frequencies LTE
[Moto X General] CrashXXL:
I wonder how you Calculate checksums HAB and certified firmware SIGN

because they are, or these tools are able to do?