Database Users

[request] to korean users

As all you know, Motorola had released oficial 2.3.4 Gingerbread update in your country as 16 this month (august). You Korean fellow who had upgraded your Atrix to Gingerbread, your cooperation is needed. If you got your update thru MSU Tool (Motorola Software Update) or OTA (Over the air), please, share your SBF file or zip file. This will allow International Atrix users gain access to an official update to Gingerbread and provide developers an more stable base to build their custom ROMS.
Your effort will be VERY appreciated.
Cheers.

I'm sure this request will take a long time, as most users with korean atrix on xda forum will try get rid of the original firmware and flashed 2.3.4, like I did. There's no sbf leak for korean firmware so theres no going back.
Sent from my MB860 using XDA Premium App

There are 2 different model numbers in Korea, KT & SKT, and we have OTA update file(KT) and full nand CWM backup(also KT) which was backed up from an unlocked stock rom(there's only 1 unlocked pure stock GB Atrix exist , customer service guy SBFed unlocked one). Somebody already has found a method to go back to the stock rom which is using CWM restore, BL&Radio flashing. the only problem we have is removing "unlocked" message to get services. I'll upload the files later(cuz i'm working right now ) if those are what you wanted

Mb860 .4.5.2a-skt-75
Thanks my friend.
I guess the correct model number is (MB860_SKT) MB860 .4.5.2A-SKT-75.
KT model is also refered as MOTOROLA ATRIX™ (MB861_KT) MB861 .4.5.2A-KT-75 at Korea Motorola website.
Anyway, we would appreciate if you upload your files and share with us.
Cheers.

Here are the files.
OTA update file(KT MB861)
Blur_Version.4.1.210.MB861.KT.en.KR.zip(thanks to Circle)
files.ucloud.com/pf/D992523_245924_35579
CWM backup stock GB(KT MB861)
4.5.2A-KT-75.zip(thanks to Zove)
files.ucloud.com/pf/D992523_245924_35562
The way to go back to the stock GB(unlocked) Zove found is removing all update scripts except for boot related imgs from the OTA update file and flashing it with CWM.
Anyway, do you think these are enough to make gobstopper, which hides "unlocked" message without SBF? or do we need an SBF to make it?
ps. I'm a kinda newbie here, so i'm not allowed to post outside links just put https in front of addresses, and there is limit number of downloading files, so download them carefully

Hi brother,
Thanks for your time and interest.
I can't make myself a Gobstopper, but I will forward that files for the one who can if possible.
Thank you.

Hi,
I had a look at the OTA file, it's a regular patch job for folks already running a Korean firmware. Not really sure what the second file is for.
Code:
assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "MOTO/KT_KR/olympus/olympus:2.2.2/OLYKT_U4_1.21.0/1307051364:user/ota-rel-keys,release-keys" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "MOTO/KT_KR/olympus:2.3.4/4.5.2A-KT-75/110802:user/release-keys");
So, to create a Gobstopper you need to do a dump of the partitions after the OTA has been applied. I can't apply the OTA since I don't have OLYKT_U4_1.21.0 on my phone. This is required since the existing files are checksum checked and a patch is applied to them. Unless the files are the same, the patch fails.
To do a dump of the partitions:
dd if=/dev/block/mmcblk0p1 of=/sdcard/mmcblk0p1
dd if=/dev/block/mmcblk0p2 of=/sdcard/mmcblk0p2
dd if=/dev/block/mmcblk0p4 of=/sdcard/mmcblk0p4
dd if=/dev/block/mmcblk0p5 of=/sdcard/mmcblk0p5
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6
dd if=/dev/block/mmcblk0p7 of=/sdcard/mmcblk0p7
dd if=/dev/block/mmcblk0p8 of=/sdcard/mmcblk0p8
dd if=/dev/block/mmcblk0p9 of=/sdcard/mmcblk0p9
dd if=/dev/block/mmcblk0p10 of=/sdcard/mmcblk0p10
dd if=/dev/block/mmcblk0p11 of=/sdcard/mmcblk0p11
dd if=/dev/block/mmcblk0p12 of=/sdcard/mmcblk0p12
dd if=/dev/block/mmcblk0p13 of=/sdcard/mmcblk0p13
dd if=/dev/block/mmcblk0p14 of=/sdcard/mmcblk0p14
dd if=/dev/block/mmcblk0p17 of=/sdcard/mmcblk0p17
I did notice that there is a bootloader in there, an ap20bl.img file, if you flash that you will either brick or be with a locked bootloader. That would be how to not have an unlocked message showing. I did notice there is unlocked text in that bootloader, am checking that out now to see if it *is* unlocked, and if it has memory issues.
EDIT: It seems the ap20bl.img in there is unlocked, but it is the same as the IHOP_Bell with the memory issues. So, if you need the "unlocked" message gone, you can try the Bell ap20bl.img file. Which may or may not cause issues on your phone. The radio is 1.35.03P if anyone is interested in that.
Cheers!

Aha. The dump of the partitions isn't the same as the nandroid that is about is it? How is it different? I have just been messing about with the system.img to no avail =[
Interesting about the bootloader etc. =] Would love to get a build of this rom on my phone at some point.

xangma said:
Aha. The dump of the partitions isn't the same as the nandroid that is about is it? How is it different? I have just been messing about with the system.img to no avail =[
Interesting about the bootloader etc. =] Would love to get a build of this rom on my phone at some point.
Click to expand...
Click to collapse
Hi,
I don't use Nandroid, so no idea. If you want to create a CWM like I did, you dump all the partitions, except pds, userdata, and cache. The point is to be hash check compatible with OTA updates.
Cheers!

NFHimself said:
Hi,
I don't use Nandroid, so no idea. If you want to create a CWM like I did, you dump all the partitions, except pds, userdata, and cache. The point is to be hash check compatible with OTA updates.
Cheers!
Click to expand...
Click to collapse
There is some .img files in a zip in the link above. what will I have to do to make this bootable? Oh the ramdisk?

If anyone is still running a stock korean rom could they check out the atrix firmwares superthread and send the OP the files so they can try and find an sbf for the korean firmware? Otherwise perform the dump as posted above straight after the OTA to 2.3.4
Thanks
Sent from my MB860 using Tapatalk

xangma said:
There is some .img files in a zip in the link above. what will I have to do to make this bootable? Oh the ramdisk?
Click to expand...
Click to collapse
Hi,
The second link gives me some error in what I would guess is Chinese. If there are img files that might help. But really you can only apply an OTA to a stock firmware that hasn't been modified, is this case for a Korean phone. So what you want is a gobstopper for the stock korean firmware in order to apply the OTA on other phones. Either that or create a CWM zip from the OTA that takes out all references to boot, recovery, cdrom, cdt, bootloader, radio, etc and apply that to a boot and system partition image flash of the stock Korean firmware of the version that the OTA wants to be applied to.
Cheers!

ds2atc said:
Here are the files.
OTA update file(KT MB861)
Blur_Version.4.1.210.MB861.KT.en.KR.zip(thanks to Circle)
files.ucloud.com/pf/D992523_245924_35579
CWM backup stock GB(KT MB861)
4.5.2A-KT-75.zip(thanks to Zove)
files.ucloud.com/pf/D992523_245924_35562
The way to go back to the stock GB(unlocked) Zove found is removing all update scripts except for boot related imgs from the OTA update file and flashing it with CWM.
Anyway, do you think these are enough to make gobstopper, which hides "unlocked" message without SBF? or do we need an SBF to make it?
ps. I'm a kinda newbie here, so i'm not allowed to post outside links just put https in front of addresses, and there is limit number of downloading files, so download them carefully
Click to expand...
Click to collapse
thx for sharing man,but the website u provide said,the number of download times exceeded the limit .plz try another one.

NFHimself said:
Hi,
The second link gives me some error in what I would guess is Chinese. If there are img files that might help. But really you can only apply an OTA to a stock firmware that hasn't been modified, is this case for a Korean phone. So what you want is a gobstopper for the stock korean firmware in order to apply the OTA on other phones. Either that or create a CWM zip from the OTA that takes out all references to boot, recovery, cdrom, cdt, bootloader, radio, etc and apply that to a boot and system partition image flash of the stock Korean firmware of the version that the OTA wants to be applied to.
Cheers!
Click to expand...
Click to collapse
Ok. I kind of understand what you're saying. I'm re-uploading the cwm .img backup to multiupload now for others to tinker with it.
I know i'm just being silly here. But when I was devving for some other devices a few years back, You could just flash the system.img, grab the ramdisk from the boot.img, pack it up with the kernel zimage and flash that as the new boot.img. Usually wifi wouldn't work because of the wlan.ko file or whatever, but you grab that out of the previous rom etc.
I'm guessing i'm being silly here right? I would love to start work on this official version, but I just don't know where to start. Will post the multiupload link asap.

NFHimself said:
Hi,
The second link gives me some error in what I would guess is Chinese. If there are img files that might help. But really you can only apply an OTA to a stock firmware that hasn't been modified, is this case for a Korean phone. So what you want is a gobstopper for the stock korean firmware in order to apply the OTA on other phones. Either that or create a CWM zip from the OTA that takes out all references to boot, recovery, cdrom, cdt, bootloader, radio, etc and apply that to a boot and system partition image flash of the stock Korean firmware of the version that the OTA wants to be applied to.
Cheers!
Click to expand...
Click to collapse
It says download limit exceeded. I'm uploading the file again and i believe we can make a gobstopper without unlocked bootloader
btw, flashing all KT stock partitions and Bell BL&BP caused "failed to boot 1 error"

Hehe whoops. Turned my laptop off mid upload ...

xangma said:
Hehe whoops. Turned my laptop off mid upload ...
Click to expand...
Click to collapse
here's the permanant link for the OTA
www.multiupload.com/LSH83FTBMV

ds2atc said:
here's the permanant link for the OTA
www.multiupload.com/LSH83FTBMV
Click to expand...
Click to collapse
Aha, i'm 20% into uploading the cwm of it after installation that was posted earlier.

daywalker said,
Definitely could use the OTA udate towards finding the stock SBF. If it's 43MB then it probably contains the radio.img (CG5)- should be about 19MB alone - that's what I need start on the right path.
Click to expand...
Click to collapse
Do you guys think the bp.img file whice is about 19Mb will help him to find the stock SBF?

http://www.multiupload.com/02249JZ851
Re-upload of the CWM backup of the new Korean Gingerbread release =D

How to reload OTA update after clearing cache?

I described here my failed attempt to update to 4.4.4
I've restored the device back to stock 4.3 JRW66Y, not rooted, and the cache has been cleared.
But the system remembers that it had an OTA to 4.4.2. If I try to install it it hangs 'rebooting now'.
logcat says E/SystemUpdateService( 961): 'OTA package doesn't exist'
Can I, without rooting it, get the system to forget that it had this OTA so that it will download a new one?

Dave_Ro said:
I described here my failed attempt to update to 4.4.4
I've restored the device back to stock 4.3 JRW66Y, not rooted, and the cache has been cleared.
But the system remembers that it had an OTA to 4.4.2. If I try to install it it hangs 'rebooting now'.
logcat says E/SystemUpdateService( 961): 'OTA package doesn't exist'
Can I, without rooting it, get the system to forget that it had this OTA so that it will download a new one?
Click to expand...
Click to collapse
You could do a factory reset then it should be able to download the OTA but the factory reset will completely wipe your device and you need to have the correct bootloader for the OTA to work. What version bootloader do you have?

wantabe said:
You could do a factory reset then it should be able to download the OTA but the factory reset will completely wipe your device and you need to have the correct bootloader for the OTA to work. What version bootloader do you have?
Click to expand...
Click to collapse
I don't want to do a factory reset - I'd rather live with 4.3
The installed bootloader is 4.23. Although the installed system is JRW66Y the bootloader is from JRW66V (see this thread).
I wonder whether deleting Google Services Framework data will do the trick, but this may have undesirable consequences (see this thread).
Maybe I'll wait a bit and have another go at flashing 4.4.4 - see my OP; nobody has suggested yet why that didn't work.

Dave_Ro said:
I don't want to do a factory reset - I'd rather live with 4.3
The installed bootloader is 4.23. Although the installed system is JRW66Y the bootloader is from JRW66V (see this thread).
I wonder whether deleting Google Services Framework data will do the trick, but this may have undesirable consequences (see this thread).
Maybe I'll wait a bit and have another go at flashing 4.4.4 - see my OP; nobody has suggested yet why that didn't work.
Click to expand...
Click to collapse
Sorry! I should have received a notification email that you had responded. For whatever reason, lately, the notification works some of the time but not always. I had no idea the bootloaders had gotten so effing screwed up! I bought my daughter a 2012 N7 for Christmas and no wonder I had to let it do an OTA before it would let me flash a factory image. I vaguely remember getting a bootloader invalid state error. My brothers bone stock 2012 N7 is on 4.4.4 with no issues, he would have called me otherwise. ; )
If you don't want to do a factory reset you CAN flash the factory image without wiping your device, as long as your bootloader is already/still unlocked. If you modify the flash_all.bat, which is inside the factory image the userdata.img which wipes your device won't be flashed. If you open the flash_all.bat with whatever text editor you use (I use editpad lite or notepad) and remove the -w from the text it won't wipe your device. You will keep your settings, installed apps and storage. Extract the factory image into the same folder as your adb.exe and fastboot.exe, you should see these files if you have the 3G version;
bootloader-tilapia-4.23.img
flash-all.bat
flash-all.sh
flash-base.sh
image-nakasig-krt16s.zip
radio-tilapia-1231_0.18.0_0409.img
The 4.4 (krt16s) is the newest factory image that has the exact same bootloader as jwr66v. From there you can let it do some OTA's or flash the 4.4.4 factory image. If you need help getting the sdk installed or have any questions let me know, hopefully the notification will work.

wantabe said:
...I had no idea the bootloaders had gotten so effing screwed up!
Click to expand...
Click to collapse
I'm not sure whether these bootloaders are as screwed up and some posts suggests. A corrupt bootloader in one release - JRW66Y - I can understand, but I'd have thought it would get corrected. But no, and the next version is also suspect. There's something going on that I don't understand. Files with the same name but different MD5s - why is that? I don't understand the 'signatures' that people mention - is there are explanation of that? In the post above mine at the end of this thread (post #98) he refers to a signature mismatch. I got the same error (post #100) but no mention of signatures. And that bootloader failed to flash despite others presumably having been successful and it having the 'correct' MD5 (which the OP has changed in the original post!). All very odd.
]If you don't want to do a factory reset you CAN flash the factory image without wiping your device, as long as your bootloader is already/still unlocked. If you modify the flash_all.bat, which is inside the factory image the userdata.img which wipes your device won't be flashed. If you open the flash_all.bat with whatever text editor...
Click to expand...
Click to collapse
I use Linux and flash the partitions individually rather than using their script, but essentially It's what I did with 4.4.4 KTU84 - at least I'm pretty sure I did.
The 4.4 (krt16s) is the newest factory image that has the exact same bootloader as jwr66v. From there you can let it do some OTA's or flash the 4.4.4 factory image. If you need help getting the sdk installed or have any questions let me know, hopefully the notification will work.
Click to expand...
Click to collapse
I might try KRT16S instead of KTU84P - it's a smaller step. But it would be better to go straight to the latest.
But I'd like to understand what's happening before I try again - and nobody's suggesting anything on that other thread. I guess the world's move on from the Nexus 7 2012! But thanks for your full replies and suggestions.
Going back to the object of this thread, here must be some way to just tell GFS to forget that it once downloaded that OTA! Any suggestions on that?

Dave_Ro said:
I'm not sure whether these bootloaders are as screwed up and some posts suggests. A corrupt bootloader in one release - JRW66Y - I can understand, but I'd have thought it would get corrected. But no, and the next version is also suspect. There's something going on that I don't understand. Files with the same name but different MD5s - why is that? I don't understand the 'signatures' that people mention - is there are explanation of that? In the post above mine at the end of this thread (post #98) he refers to a signature mismatch. I got the same error (post #100) but no mention of signatures. And that bootloader failed to flash despite others presumably having been successful and it having the 'correct' MD5 (which the OP has changed in the original post!). All very odd.
I use Linux and flash the partitions individually rather than using their script, but essentially It's what I did with 4.4.4 KTU84 - at least I'm pretty sure I did.
I might try KRT16S instead of KTU84P - it's a smaller step. But it would be better to go straight to the latest.
But I'd like to understand what's happening before I try again - and nobody's suggesting anything on that other thread. I guess the world's move on from the Nexus 7 2012! But thanks for your full replies and suggestions.
Going back to the object of this thread, here must be some way to just tell GFS to forget that it once downloaded that OTA! Any suggestions on that?
Click to expand...
Click to collapse
Out of curiosity I looked at the bootloaders and even though they say v4.23 a crap load of them are different sizes. Just as an example jwr66v is 2,150,992 bytes and ktu84p is 2,151,068 bytes. Don't have a clue what is going on. I can tell you that the bootloaders on the N5 and 2013 N7 are the exact same size across os versions that state the same bootloader version number.
---------- Post added at 02:19 AM ---------- Previous post was at 02:00 AM ----------
The vast majority of the time I also fastboot flash the images separately, I make a few too may changes in the system files to be able to use an OTA unless it's a very small one. I would flash the images for krt16s, bootloader, boot, system, recovery and radio. Then let it do a couple OTA's. 4.4.2 has a different size bootloader (4,005,632 bytes) and 4.3, 4.4.3 and 4.4.4 have the same size (2,151,068 bytes).
---------- Post added at 02:26 AM ---------- Previous post was at 02:19 AM ----------
Dave_Ro said:
Going back to the object of this thread, here must be some way to just tell GFS to forget that it once downloaded that OTA! Any suggestions on that?
Click to expand...
Click to collapse
I would think flashing the system image would clear it out but I guess not. If you were rooted you could run SDMaid and I think that would clear it. If you were rooted you could sideload the OTA and put it in /cache and see it that works. Sorry, I don't have a lot of experience running OTA updates, I usually have to fastboot flash images.

Well, in the end I successfully reflashed it to 4.4 (KRT16S), erasing user data. It then did 3 OTAs to 4.4.4 in quick succession.
Along the way it said:
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'tos.img'
tos? ISTR that was on the Atari ST
Thanks for the suggestion. I don't need half these apps anyway - it's good to have a clearout!
Dave

[HOW TO] Downgrade from 19.6.3 to 19.5.3 RSD Lite or Fastboot

Alright so to start off here's the usual, I'm not responsible if you brick your phone or if your computer starts spitting corrosive acid at you, you know the general anything and everything that can happen on this planet.
So basically I have two files I'm uploading right now. The flash.zip that you have to download and the RSD lite zip that is optional.
You need to download the flash.zip or both and extract them and install RSD. After doing so you'll have to put your phone into fastboot by powering it off and holding the power button and vol - key together until it pops up in AP flash. (YOU DON'T NEED TO DO THIS IF YOUR USING THE LAUNCH.bat)
After all of that you need to plug in your phone to your desktop and assuming you have all the drivers installed you need to either open RSD and select the xml in the folder you extracted from the flash.zip and select your phone and start the flashing process.
Now if your phone is not recognized by RSD you need to run the LAUNCH.bat and it will do the whole process in about 5-15 minutes (rough estimate)
After everything is done your phone will reboot and your on 19.5.3 and can root your phone permanently and gain system r/w permissions with my other thread HERE.
Credits:
Credit for the downgrade through fastboot go to myself and Google for fastboot of course.
Credits for the other stuff in the other thread are in the link up above.
Download Section:
FLASH.zip
RSD 5.7

Is this for unlocked bootloaders only? I just tried it and it keeps failing because I get this:
downgraded security version
update gpt_main version failed
preflash validation failed for GPT
RSD Lite says:
Failed flashing process. 2/17 flash partition "gpt.bin"
Really hope this isn't for unlocked users only cause I just wiped my phone for this to test it and root

Jay_P11 said:
Is this for unlocked bootloaders only? I just tried it and it keeps failing because I get this:
downgraded security version
update gpt_main version failed
preflash validation failed for GPT
RSD Lite says:
Failed flashing process. 2/17 flash partition "gpt.bin"
Really hope this isn't for unlocked users only cause I just wiped my phone for this to test it and root
Click to expand...
Click to collapse
Its for the non-dev Droid Maxx/Droid Ultra's with locked bootloaders. It sounds like your on a os lower than 4.4 or higher than 4.4. Can you give me your system specs? (Android version, System version, and phone model)

TheOriginalist said:
Its for the non-dev Droid Maxx/Droid Ultra's with locked bootloaders. It sounds like your on a os lower than 4.4 or higher than 4.4. Can you give me your system specs? (Android version, System version, and phone model)
Click to expand...
Click to collapse
Android 4.4.4
Build SU4.21
System Version 21.11.21.obake_verizon.Verizon.en.US
The update said it was 19.6.3 when I downloaded it so now I'm really confused

Jay_P11 said:
Android 4.4.4
Build SU4.21
System Version 21.11.21.obake_verizon.Verizon.en.US
The update said it was 19.6.3 when I downloaded it so now I'm really confused
Click to expand...
Click to collapse
Yeah it said that probably from a previous download or something whats important is that you didnt brick your device. Can you boot?

TheOriginalist said:
Yeah it said that probably from a previous download or something whats important is that you didnt brick your device. Can you boot?
Click to expand...
Click to collapse
All is well. I backed up my pics and stuff as I always do before trying something like this, so nothing major was lost. Just gotta re-install all my apps cause google backup somehow chose to not help me in my time of need but I guess the version I came from was what it said was 19.6.3 and I never bothered to double check before trying anything. Man would it be great if this worked on 4.4.4 though. Have you or anyone else tried the root method on 4.4.4? If not (unless you're sure it won't work) I'm willing to try the root process.

Jay_P11 said:
All is well. I backed up my pics and stuff as I always do before trying something like this, so nothing major was lost. Just gotta re-install all my apps cause google backup somehow chose to not help me in my time of need but I guess the version I came from was what it said was 19.6.3 and I never bothered to double check before trying anything. Man would it be great if this worked on 4.4.4 though. Have you or anyone else tried the root method on 4.4.4? If not (unless you're sure it won't work) I'm willing to try the root process.
Click to expand...
Click to collapse
No but I've tried my own exploits on other Android versions like 4.4 and 4.2.2 on this phone. I just wont risk updating to 4.4.4.

Thread is not needed. The simple process would be to simply download the fxz from the reputable sbfdevelopers and flash. Nothing else is needed. Again repost.

Topsnake said:
Thread is not needed. The simple process would be to simply download the fxz from the reputable sbfdevelopers and flash. Nothing else is needed. Again repost.
Click to expand...
Click to collapse
Again I am just trying to simplify things for people. Especially if they have issues with RSD Lite.

UPDATE: MoFo Works on XT1096 Running 4.4.4 and 5.0!!!!!

WARNING my qe = 1/1 now!!! So this trips the root checker. And even though I am unrooted now, it still shows as a modified system.
All you need to know is here:
http://forum.xda-developers.com/moto-x-2014/general/noob-guide-rooting-verizon-moto-x-2014-t3097375
and here:
http://forum.xda-developers.com/general/paid-software/mofo-root-turbo-t3064404
Please see @btdownloads7, @mikeoswego and @ClydeDroid threads for the latest 5.0 images!!!!
http://forum.xda-developers.com/mot...-xt1096-victara-lollipop-images-mofo-t3100601
http://forum.xda-developers.com/moto-x-2014/development/img-xt1096-victara-mofo-image-root-t3100145
http://forum.xda-developers.com/mot...mg-totalx-root-tether-busybox-sqlite-t3101853
Below is for historical purposes only (or until I get around to editing it, lol!):
UPDATE - success on 5.0 flashing the images that @Slack3r made from the fxz that @slogar25 uploaded. Slack3r made a stock ext4 image and a modified ext4 image having a modified build.prop to allow for free WiFi tether on UDP lines. Attached is the screenshot of me using my FREE WiFi Hotspot on my XT1096 on my UDP line!!!!! Yipeeeeee!!!!!!! Thanks so much Slack3r and slogar25!!!
@maiko1 - will you open up MoFo for XT1096 running 5.0? We don't have a pre-rooted image yet but we have one that has a modified build.prop that allows for free wifi tether, which is what many of us want out of this anyhow.
I just tested MoFo for @maiko1 on my Moto X 2014 running 4.4.4 and it is a SUCCESS!!!!!!! Attached is the root checker screen shot. I was able to modify the build.prop but of course it doesn't survive a reboot. And I used Titanium B/U to uninstall MotorolaOTA 2.0 to stop the OTA from downloading. Of course, it comes back on reboot.
And my software status shows Modified so it trips the root checker on the phone. Same thing happens with the DT so it is to be expected.
Planning on testing the image for Lollipop next!!!! Wish me luck!!!!
Edited to add information:
picowoodworm said:
This was pretty simple. Got it to root and got Hotspot to work. Thanks!
Click to expand...
Click to collapse
The pre-rooted 4.4.4 does not bypass the subscription check to allow for free WiFi hotspot if you have a UDP line. I know I tried it.
picowoodworm said:
I am grandfathered Verizon unlimited. Hotspot never worked for me before. I used the Entitlement Bypass app and have hotspot now.
Click to expand...
Click to collapse
Thank you!!! I didn't know there was an Entitlement Bypass app. Can you link to it?
picowoodworm said:
No problem. I just thought I'd give it a shot and it worked. The app actually says "failed", but it works and it shows this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here's the link. http://forum.xda-developers.com/moto-x/themes-apps/app-hotspot-entitlement-bypass-v1-1-5-9-t2705152
Click to expand...
Click to collapse
Caketray said:
How safe is this root?
Click to expand...
Click to collapse
Keep in mind the big picture of what you get with MoFo - you get a version of fastboot that will let you flash unsigned files to the system partition of your phone. It doesn't flash any other partition - just system.
You are not getting a root method with MoFo - you are getting a piece of software that lets you flash unsigned ext4 images to the system partition and only to the system partition of your phone. It does not disable write protection. But if you know how to, you can mod an ext4 system image using linux to have any feature you want in it including the su binary, modified build.prop file or Xposed Installer. And THAT is how you get root and the other features you want on your phone.
For 4.4.4, the pre-rooted image gives you root access, but nothing else. Anything else would have to be added to it, including a modified build.prop that would bypass the subscription check and allow for free WiFi hotspot if you have UDP. UPDATE - You can use the Entitlement Bypass App to get free WiFi hotspot if you have UDP. See above.
As long as you can get your phone into bootloader mode, you can flash complete garbage to the system partition using MoFo - I know I did it - and then reflash the stock system image using fastboot and your phone will be fine. Or connect your phone to your PC and run Motorola Device Manager and MDM will flash your phone back to stock system.
I flashed both the 4.4.4 and 5.0 stock images after flashing the pre-rooted images so I know they are fine. The only image that doesn't work is the pre-rooted 5.0 image. But the stock 4.4.4 and 5.0 are fine as is the pre-rooted 4.4.4 image on Root Junky's site. Although the pre-rooted 4.4.4 image only works if you haven't upgraded to 5.0 yet. I know b/c I tried to downgrade the system and kernel back to 4.4.4 after I upgraded to 5.0. Doesn't work, but doesn't hard brick either.
Caketray said:
Is there a decent chance that I'll break something beyond repair?
Click to expand...
Click to collapse
If you are on 4.4.4 and flash the 4.4.4 pre-rooted image, you should immediately uninstall or freeze MotorolaOTA 2.0 to stop the 5.0 OTA. The first thing I did was install Titanium B/U on my phone and uninstall MotorolaOTA 2.0. You can freeze MotorolaOTA 2.0 too if you pay for the Ti B/U pro key.
Now having said that, if you are on 4.4.4 and used MoFo to flash the pre-rooted image and then take the 5.0 OTA will you brick? Idk but since you don't have write protection disabled and there is no working pre-rooted 5.0 ext4 image, I don't see what good it would do for you to take the 5.0 OTA while running the 4.4.4 pre-rooted image. So I would uninstall or freeze MotorolaOTA 2.0.
I started on 4.4.4, then flashed the pre-rooted 4.4.4 image and tested that it worked using the root checker and by downloading Ti B/U and uninstalling MotorolaOTA 2.0 and modifying the build.prop file. Then I rebooted and confirmed that my changes were lost on reboot. Then I flashed back to stock 4.4.4 using fastboot and the 4.4.4 stock image on RJ's site and took the 5.0 OTA. Everything worked fine, no problems. I didn't run into problems until I used MoFo after I took the 5.0 OTA to flash the pre-rooted 5.0 system image - that image won't boot. So I flashed back to 5.0 stock using fastboot and the 5.0 stock image on RJ's site and then tried again to flash the pre-rooted 5.0 image using MoFo and got the same result - it wouldn't boot.
Read my other posts to see what all I flashed with MoFo - Pure Edition system images, images that weren't ext4 files, 4.4.4 system images after upgrading to 5.0, etc. No matter what I flashed using MoFo - even when MoFo told me not to flash the PE system image - I could get into bootloader mode and reflash the proper stock image for my bootloader version. I could also connect my phone to my PC and MDM would repair my phone.
The only time MDM couldn't repair my phone was after I flashed the PE system image using MoFo and the PE kernel using fastboot - then MDM just said unknown or something like that. But since I could get into bootloader mode, I just reflashed stock system and kernel using fastboot and was GTG.
Caketray said:
How do you reflash the stock image?
Click to expand...
Click to collapse
First you get the most recent version of fastboot and adb on your PC and install the Moto X 2014 drivers. You can get fastboot and adb from the Android SDK. You can get the Moto X 2014 drivers from Root Junky's site here:
http://rootjunkysdl.com/?device=Android Drivers&folder=Motorola
You should do that before even trying to verify for MoFo.
After you have the Moto X 2014 drivers installed, have enabled USB debugging on your phone and have tested that the drivers indeed work by putting your device into bootloader mode, opening a command shell, changing the directory to where fastboot.exe is and typing:
fastboot devices
to see that indeed your device serial number is returned by fastboot, then you download the stock image from Root Junky's site here:
http://rootjunkysdl.com/?device=Moto X 2014&folder=Official Firmware
and unzip it. Then I place a copy of fastboot.exe, adb.exe, AdbWinApi.dll and AdbWinUsbApi.dll from the Android SDK in the same folder as the unzipped stock image. Open a command shell, change directory to where the stock image is and then type the commands:
fastboot flash system system.img_sparsechunk.0
and keep repeating that for each sparsechunk until they have all been flashed.
If you are on 5.0, to put your phone in bootloader mode, you turn it off, then press and hold the volume down + up buttons simultaneously with the power button for about 4 seconds and then release both and you get into bootloader mode.
All of what I typed above is very basic info. You should do some reading here to make sure you understand what you are doing.

Great news man thanks for sharing

JulesJam said:
Planning on testing the image for Lollipop next!!!! Wish me luck!!!!
Click to expand...
Click to collapse
Unfortunately, the pre-rooted image for 5.0 didn't work. It just hangs at the M and never loads the boot animation.
The good news is that all you have to do is power down and get into fastboot, connect your phone to your PC and run Motorola Device Manager and it fixes your phone by flashing the stock 5.0 system image to it.
I also tried flashing back to the pre-rooted 4.4.4 and also the 4.4.4 kernel but that didn't work either. Again, the good news is that I didn't brick and as long as I was able to get into fastboot, I could get MDM to fix it or flash the stock 5.0 image on Root Junky's site. However, the stock image on Root Junky's site seems to have the wrong version number although my phone shows the correct system version when I flash it.
I can tell you this much, after I flashed the pre-rooted 4.4.4 image, my software status showed modified. Then I flashed 4.4.4 stock image and the software status went back to official. Then took the OTA to 5.0, still showed official. Then flashed the pre-rooted 5.0, which did not load. Then fixed it with MDM - still showed software status official. Then flashed back to 4.4.4 pre-rooted and then flashed back to the 5.0 stock image on RJ's site and software status now shows modified.
I will repeat it all again later today to make sure that I didn't do anything wrong last night but I think the issue is in the 5.0 image. MoFo appears to flash the unsigned files once you have upgraded to 5.0, which is good news.
And for those of you on 4.4.4, I would stay there as it works on 4.4.4. The only thing you would need is for someone to add a modified build.prop to the pre-rooted image that has a line that says net.tethering.noprovisioning=true and you would have free WiFi tether.

Nice!! Thanks for testing. It sounds like something with the IMG itself got borked along the way. Since mofo was able to push the IMG through.
Sent from my XT1096 using Tapatalk

slogar25 said:
Nice!! Thanks for testing. It sounds like something with the IMG itself got borked along the way. Since mofo was able to push the IMG through.
Click to expand...
Click to collapse
I hope the problem is in the image but the only thing that seems odd to me it is the boot animation wouldn't load.
Edited - nevermind, I see that the boot animation is stored on \system\media so it could be the image.

Could you please try Sunshine/S-Off on 4.4.4, just for the record!

Pizzuto said:
Could you please try Sunshine/S-Off on 4.4.4, just for the record!
Click to expand...
Click to collapse
I've already upgraded to 5.0 and jcase says it won't work on motorola bootloaders above 4.4.2 even if you can get root so I believe him.
If you are still on 4.4.4, ask maiko1 to open up MoFo for the XT1096 running 4.4.4.

FYI
@Slack3r said he will try to make a system image with a modified build.prop file that will allow for free WiFi tether. I will flash it and see if that works. If so, at least you could have free WiFi tether on 5.0, which for me and other UDPers is huge. WiFi tether costs $30/mo so in the first month MoFo would pay for itself if you use WiFi tether.
FYI also - to do that you simply add a line anywhere in the build.prop that reads:
net.tethering.noprovisioning=true
I also found this article on how to hide that you are tethering:
http://pocketnow.com/2015/01/01/nexus-6-tethering

UPDATE - so the stock 5.0 that is available on RJ's site is broken up into 9 chunks and Slack3r was not able to mount the chunks to mod it. He tried to unroot the pre-rooted 5.0 image and then edit the build.prop to allow free WiFi tether but it gave the same result as the pre-rooted 5.0 system image once flashed with MoFo - it won't load the boot animation and hangs on the M.
So we still don't know if MoFo works on 5.0 or not or if the problem is with the pre-rooted 5.0 system image.
Does anyone know of a stock 5.0 system image for the XT1096 that is not broken down into chunks but is a single file?

I have the full fxz file with the untouched system IMG. However I'm at work right now and can't get it to you until this afternoon
Sent from my XT1096 using Tapatalk

slogar25 said:
I have the full fxz file with the untouched system IMG. However I'm at work right now and can't get it to you until this afternoon
Sent from my XT1096 using Tapatalk
Click to expand...
Click to collapse
Past the sake of testing for root having a clean system.img would be great for anyone wishing to fastboot flash their phone, so please ensure you upload it, even just for reference when you get back from work

The only other thing I can think of at the moment is trying to flash the system.img from the Pure Edition running 5.0, the phones have different radio chips though so I'm not sure what would happen.
http://forum.xda-developers.com/mot...g-lxe22-39-6-pure-edition-stock-boot-t2940437

slogar25 said:
I have the full fxz file with the untouched system IMG. However I'm at work right now and can't get it to you until this afternoon
Click to expand...
Click to collapse
Awesome, thanks!!!

Slack3r said:
The only other thing I can think of at the moment is trying to flash the system.img from the Pure Edition running 5.0, the phones have different radio chips though so I'm not sure what would happen.
http://forum.xda-developers.com/mot...g-lxe22-39-6-pure-edition-stock-boot-t2940437
Click to expand...
Click to collapse
I already did that last night, lol! First, I couldn't flash it with fastboot b/c it said it couldn't load it presumably due to size. The file is 2.7GB. With mfastboot it said it could not allocate about 1.3GB so I guess it is too large for the version of mfastboot I have?
Then I flashed it using MoFo and it flashed and it didn't work. It gave me some error I can't remember exactly what it said. I also tried to flash the PE 5.0 kernel but that didn't work either.
Also I found a copy of what appeared to be the 5.0 system.img in the programdata\motorola\SUE folder, which is where MDM must store what it is downloading. The file was only 2.195GB instead of 2.8GB like the pre-rooted 4.4.4 and 5.0. It wouldn't flash with fastboot or mfastboot, presumably b/c of size but when I tried to flash it with mofo, it said it did not appear to be a valid ext4 image. I flashed it anyhow and it didn't work.
The good news is I could always get into bootloader mode no matter what I did and then either flash RJ's stock image in chunks or MDM would repair my phone.

mofo now supports Moto X 2014 on 4.4.4. Thank @JulesJam for testing. Visit the mofo thread for more info.
5.0 will remain blocked until a valid image appears.

maiko1 said:
5.0 will remain blocked until a valid image appears.
Click to expand...
Click to collapse
Any tips on how to create one? Or thoughts on what might be the problem with the one that is on Root Junky's site?

maiko1 said:
mofo now supports Moto X 2014 on 4.4.4.
Click to expand...
Click to collapse
To those on 4.4.4 - the pre-rooted image that is available just gives you root access and since write protection is enabled, there isn't much you can do with it.
Edited - Check out my OP for the link to the Entitlement Bypass App to enable free WiFi hotspot.
IMO, the first priority for those on legacy UDP plans who want free WiFi is to modify the build.prop of the pre-rooted system image to have the line:
net.tethering.noprovisioning=true
This will allow for free WiFi tether on your UDP line.
In the OP of the MoFo thread is a link to a thread that teaches you how to mod an image. You need linux to do this. There also is a link in the OP of the MoFo thread on how to get Xposed Installer baked into the pre-rooted system image. Obviously the images that were modded in these tutorials were for the Droid Turbo. You would of course be modding the 4.4.4 image for the Verizon Moto X 2014.

Waiting for the fxz to upload now. It will take some time as you know it is very large. Will post the link when ready
Edit: Here is a link to the lollipop fxz. Just extract the system.img
https://www.androidfilehost.com/user/?w=settings-dev-files&flid=30246
Sent from my XT1096 using Tapatalk

slogar25 said:
Edit: Here is a link to the lollipop fxz. Just extract the system.img
https://www.androidfilehost.com/user/?w=settings-dev-files&flid=30246
Click to expand...
Click to collapse
Thanks. I registered for the site but when I try to down load it, I get this error:
access denied
looks like you don't have permission to access this folder. Make sure you are signed in to an account that has permission, or check with the developer to request access.
How do I get access to download it?

JulesJam said:
Thanks. I registered for the site but when I try to down load it, I get this error:
access denied
looks like you don't have permission to access this folder. Make sure you are signed in to an account that has permission, or check with the developer to request access.
How do I get access to download it?
Click to expand...
Click to collapse
My bad lol. Wrong link.
Try this a let me know
https://www.androidfilehost.com/?w=files&flid=30246
Sent from my XT1096 using Tapatalk

Modified XT1095 OTA

I took the OTA update zip from my phone and modified the updater-script to look for:
motorola/victara_tmo/victara:5.0/LXE22.46-11/11:user/release-keys
Click to expand...
Click to collapse
This should allow the OTA to be sideloaded if you used the Motorola 5.0 Lollipop factory image that they recently published.
DISCLAIMER:
This is untested by me. I have no idea if it will work. Be sure you can return to stock if you need to. DO NOT flash this if your bootloader is locked!
Still here? Then if you want to be a guinea pig, you must be on the factory image from lollipop and the fingerprint must be motorola/victara_tmo/victara:5.0/LXE22.46-11/11:user/release-keys.
Url removed. Motorola has fixed the 5.0 images. Download them again.

Honestly I'd rather not do this. The check is there for a reason.

alvareo said:
Honestly I'd rather not do this. The check is there for a reason.
Click to expand...
Click to collapse
True. But Motorola hasn't been too good with their checks already. The only part that concerns me would be the sbl update at the end of the script.

I think the official 5.0 image Motorola posted was put together in a rush or something. After I flashed it, the software status in the bootloader always showed: modified. When I didn't see the OTA popping up after checking for updates yesterday, I tried a logcat and it was spitting out errors about build fingerprint mismatch (that made sense), but also errors about root being present? I had not rooted after flashing the 5.0 image... The OTA was clearly available from Motorola's servers (I could see the download link and manually download it if I wanted). It was just determined to be incompatible, so the phone just kept saying software is up to date...
After flashing the previous 5.0 I had laying around, the software status showed as official in the bootloader as well.

Very good info. Sounds like they botched the build and now it's causing issues for everyone. I bet when they compiled the image they had something extra in the /system and that caused it to increment the build fingerprint and the status to show modified

Anyone get this to work? Comes up invalid file for me.

I don't think it will work. If I remember correctly otas need a signature, which only motorola has. Since it's a modified ota, the signature won't match.
Sent from my XT1095 using Tapatalk

Actually it will work. Chinese people had successfully modified ota of 5.0.2,he reduced BL's version and gpt's level. So if u flash that ,it would not update your BL version and also gpt level. because of this modified ota u can easily downgrade ~

colourfuldays said:
Actually it will work. Chinese people had successfully modified ota of 5.0.2,he reduced BL's version and gpt's level. So if u flash that ,it would not update your BL version and also gpt level. because of this modified ota u can easily downgrade ~
Click to expand...
Click to collapse
I just read up on it some more. We are both correct. Yes you can modify an ota file but if it is not signed by motorola it can only be used on an unlocked bootloader. Anyoneone that has a locked bootloader will not work.
Sent from my XT1095 using Tapatalk

colourfuldays said:
Actually it will work. Chinese people had successfully modified ota of 5.0.2,he reduced BL's version and gpt's level. So if u flash that ,it would not update your BL version and also gpt level. because of this modified ota u can easily downgrade ~
Click to expand...
Click to collapse
In the other 5.1 thread they posted IMG files for everything but bl and gpt. I fastbooted just the system and boot files and now am on 5.1 may try the modem files at some point but didnt see a need so far. One disclaimer in the same thread i gave explicit directions to another user who said it didnt work at all but he was not on a pure edition and had a different bl version.
So why post all this here.... to agree with the above that with the script correctly modified it should work perfectly.