Database Users

[MOD] Uncapped Data - Gingerbread 4.5.588 Deodexed - Now flashable via Clockwork

I edited services.jar that came with the newest Gingerbread 4.5.588 deodexed system to disable data throttling.
Tested and works, though you may want to make a backup of your services.jar file first. I take no responsibility if you screw up your phone
(Make sure you're running deodexed system)
Instructions:
1. Place zip file in root of sdcard.
2. Boot into clockwork.
3. Install zip from sdcard.
4. Choose the zip on your card.
5. Reboot.
Note: You MAY have to mount system first. I know in the past people have ran into that problem. I personally did not have to mount system.
Enjoy!

This does not work ....

It absolutely does work. Feel free to decompile the .dex file yourself to see if the throttling files are still intact and compare it against the .dex decompile of stock. Or maybe you could post WHY you think it doesnt work instead of just stating that it doesnt.
Sent from my DROIDX using XDA App

lithiasalesjs said:
This does not work ....
Click to expand...
Click to collapse
Were you trying to flash it in recovery? If so then it will not work. There are also two other ways to do this. You can extract the file and replace your services.jar file in root explorer or you could use the commands provided (without the adb) in the app terminal emulator.
To the developer, thank you for making this but if someone says it doesn't work, you do not need to get mad at them. That will keep others away from downloading your files

No I followed the directions step by step and i replaced it via Root Explorer restarted and all it does is do a large freezeup. I tried this twice and all you get is a freezeup on restart. In return all I got out of this is a SBF Flash twice back to 4.5 and deodoxed again -.-

Im not mad in the slightest. Im here to help. Unfortunately its very hard to help with so little details. "It doesnt work" doesnt help everyone else.
Now, Im not sure whats going on with his particular issues, but I can guarantee it does work. Im running it now on my own personal device and have tested it on 3 other Droid X's running 4.5.588 deodexed. The services.jar file came straight from P3Droid's deodexed update.zip. The throttling files were removed and I packaged up the file.
To the person having issues: are you absolutely sure youre deodexed? Are you using P3Droid's deodexed update? Did you attempt using the adb commands and if so did you receive any errors? I will say, I have not tried this with root explorer so I cant predict the outcome, though it shouldn't work any differently than adb.
Sent from my DROIDX using XDA App

Ive never made an update.zip file before, but maybe Ill look into packaging it that way and see if he can have any luck with that.
Edit: Just packaged it into flashable zip. See first post.
Sent from my DROIDX using XDA App

Yes I used p3droids new deodexed for 4.5.588 then applied the services.jar in the framework folder did a restart and got big freeze. I haven't got a chance to do the adb push ... I will try that when I get home tonight.

Thanks GC14 for this!!! I am still on the original GB deodex rooted leak. Do you have, or is there an uncapped data service.jar for that release? thanks

Im not sure, but I can just patch that one too and upload it if you want.
Sent from my DROIDX using XDA App

If you don't mind that would be awesome.
Sent from my DROIDX using XDA App

P3droid recently posted a fix for his deodexed leak that fixed fc issues by making it slightly oxdexed and slightly deodexed, will this work with it?

Depends if services.jar is odexed or deodexed. Open up his new build and check to see if services.odex and services.jar are both inside /system/framework. That would mean it's odexed.

does the OS need to be deodexed for uncapped mod to work?

Did you use Clockwork for DX or D2? I have Clockwork for DX installed but can never boot into it.

Disable USB Debugging and then try DX Clockwork.

Is there a way to get this on the oxed .591 GB leak? PLEEEASE

http://db.tt/lchqb3k Nothrottle.zip for .591
Sent from my DROIDX using XDA App

dang, and now 595 is out!

Yeah...can't keep up these days lol...

Root Exploit

Hey guys,
I was looking at the newly patched (for 4.4.3) exploit.
It is patched in our .402 firmware but is exploitable in .69.
Update: Exploit is released, see primary thread: http://forum.xda-developers.com/showthread.php?t=2781109
-----------------------------------------------------------------------------------------
With it me and a friend have managed to take out SELinux:
Code:
[email protected]:/data/local/tmp $ getenforce
Permissive
Edit: And now, my device is rooted! Sweet Time to backup TA.
Edit#2
I/sh (12494): I am running as..
I/sh (12494): uid=0(root) gid=0(root) context=u:r:vold:s0
I/sh (12494): Backing up TA..
I/sh (12494): lrwxrwxrwx root root 1970-03-20 09:35 TA -> /dev/block/mmcblk0p1
I/sh (12494): 4096+0 records in
I/sh (12494): 4096+0 records out
I/sh (12494): 2097152 bytes transferred in 0.065 secs (32263876 bytes/sec)
I/sh (12494): Created /data/local/tmp/TA.img -- Checking MD5..
I/sh (12494): 215c7526bb9abea4ae6363c25987bbd0 /dev/block/platform/msm_sdcc.1/by-name/TA
I/SemcPhoneInterfaceManager(12500): QcSemcService is connected.
I/sh (12494): 215c7526bb9abea4ae6363c25987bbd0 /data/local/tmp/TA.img
Click to expand...
Click to collapse

WOW! this is the most exciting news on this forum yet! Do you have a link to a guide for this exploit?
Sent from my MI 2S using Tapatalk

I would really like to make it a simple process. Right now it is *VERY* ugly!
You have to take out selinux and then replace some files (specific to .69) that let you run root commands from a bash file.
Right now it's just a collection of scripts, an apk and a tar.gz. No checks at all to make sure they are being run correctly.
From what I can tell, this method I am using will work for ALL phones using Android 4.4.2 (unpatched) or earlier.
Although it is using Sony files for the exploit for no other reason than I only cared about rooting my device.

Nice. Hope you can get it polished enough to share soon! Maybe ask for donations too. I'm ordering one soon and I would love root without killing my warranty.
Sent from my MI 2S using Tapatalk

SANGER_A2 said:
Nice. Hope you can get it polished enough to share soon! Maybe ask for donations too. I'm ordering one soon and I would love root without killing my warranty.
Click to expand...
Click to collapse
Is this good enough?
https://mega.co.nz/#!zBZVnDTZ!tajRYy0F3_lgYDITHlqj3UTPv3bDiEQBUW-bj6JqMKQ

xsacha said:
Is this good enough?
https://mega.co.nz/#!zBZVnDTZ!tajRYy0F3_lgYDITHlqj3UTPv3bDiEQBUW-bj6JqMKQ
Click to expand...
Click to collapse
Cool. Can't wait to try it out. Will be a while as I'm not ordering the tablet for about a week. I'm fine with linux, but ADB looks like a complete PITA to install on it, plus having to mess around configuring the USB to talk to the tablet. I've used ADB lots on Windows with no issues and will probably run the commands from there instead. I don't quite understand the "&& \" at the end of each adb command. Is that needed if using ADB in windows?
I'm trying to figure out how it all works and I can understand most of what you have done. I assume the exploit.apk gives su. Is this temporary until a reboot or permanent? And does it mean we have to have the app installed permanently or can it be uninstalled afterwards? Then, you copy and make the scripts & binaries executable. But you don't seem to run the scripts? Do the scripts need to be run on the device in a terminal emulator to backup the TA partition and mount the new volume with vold?

Damn, already updated to .402. Is there anyway to go back to .69?
Greato work btw.

star85 said:
Damn, already updated to .402. Is there anyway to go back to .69?
Greato work btw.
Click to expand...
Click to collapse
Yes, just flash .69. I was on .402 as well and found the exploit patched.
SANGER_A2 said:
Cool. Can't wait to try it out. Will be a while as I'm not ordering the tablet for about a week. I'm fine with linux, but ADB looks like a complete PITA to install on it, plus having to mess around configuring the USB to talk to the tablet. I've used ADB lots on Windows with no issues and will probably run the commands from there instead. I don't quite understand the "&& \" at the end of each adb command. Is that needed if using ADB in windows?
I'm trying to figure out how it all works and I can understand most of what you have done. I assume the exploit.apk gives su. Is this temporary until a reboot or permanent? And does it mean we have to have the app installed permanently or can it be uninstalled afterwards? Then, you copy and make the scripts & binaries executable. But you don't seem to run the scripts? Do the scripts need to be run on the device in a terminal emulator to backup the TA partition and mount the new volume with vold?
Click to expand...
Click to collapse
There was absolutely zero configuration on my Linux distro. In Ubuntu, adb comes in the repos. You don't need drivers on Linux because they are detected as usbnet by default. It literally just works out of the box.
The "&& \" is actually for bash. The && only continues if the previous command succeeds. The \ breaks to next line.
On Windows, you'd use a caret (^) instead of a backslash.
The exploit.apk is used to deploy a shared library owned by system because when a system app tries to load its library, it needs to be owned by system and this is the only way I know how to achieve that.
The exploit is all in vdc (a shell command), which allows us to overwrite files anywhere on the system. So in this instance, ServiceMenu is used. Its library is overwritten with one from exploit.apk. The library simply turns off selinux and then runs whatever is in 'log.command' prop which is in this instance, a shell script. In the script it continues on to the root.
Basically: All apps have system libraries but they can't execute system code unless a system app runs it. System user can turn off selinux. Turning off selinux is required to run as root.
Yes, the scripts get run indirectly. You don't run them yourself because you are only a mere shell user. Vold is not used for anything. It's simply the vehicle for running as root.

Sonny, you win the internets. If I had donation money it would go straight to you.

Thanks for the explanation Sacha. Can't wait to try it. So this let's us backup TA. Does it also provide permanent root or do we still need to unlock the bootloader and break the warranty to get that?
I'll have a play putting adb on Linux tonight. All the guides I found were pretty old!
Sent from my MI 2S using Tapatalk

SANGER_A2 said:
Thanks for the explanation Sacha. Can't wait to try it. So this let's us backup TA. Does it also provide permanent root or do we still need to unlock the bootloader and break the warranty to get that?
I'll have a play putting adb on Linux tonight. All the guides I found were pretty old!
Sent from my MI 2S using Tapatalk
Click to expand...
Click to collapse
Definitely not permanent. Resets on reboot.
I couldn't find anywhere to stick the su binary. /system can't be remounted rw by root. All the other partitions don't let me setuid. If anyone knows where to stick, that would be appreciated.
Afaik unlocking bootloader shouldn't void warranty? Isn't that one of the reasons for TA. When we flash it back, warranty is valid again?

SANGER_A2 said:
Thanks for the explanation Sacha. Can't wait to try it. So this let's us backup TA. Does it also provide permanent root or do we still need to unlock the bootloader and break the warranty to get that?
I'll have a play putting adb on Linux tonight. All the guides I found were pretty old!
Click to expand...
Click to collapse
If your distro doesn't have it in the repos just download and install the official Android SDK. There you only install the "platform-tools".

Thank you very much for this, that's really great news!! As soon as I have time and found out how to flash back to .69 I will try it out. Is there a way to donate to you for your work?
Nevertheless if I understood it right, this persists only until a reboot so if I root it and then update back to .402 it will be gone, so there is no way to have root on .402 with locked bootloader?
Or is it possible to root and backup ta, flash .402 restore ta and lock bootloader AND keep root? That would be awesome!
Thanks
Fleckdalm

fleckdalm said:
Thank you very much for this, that's really great news!! As soon as I have time and found out how to flash back to .69 I will try it out. Is there a way to donate to you for your work?
Nevertheless if I understood it right, this persists only until a reboot so if I root it and then update back to .402 it will be gone, so there is no way to have root on .402 with locked bootloader?
Click to expand...
Click to collapse
I guess you can donate if you want I didn't put much time in to this and I didn't discover the Android exploit. Most my projects (like Dingleberry for rooting) have a full UI and everything. I have a donate link on my blog: http://www.qtness.com/blog/
That's correct. if you upgrade to 402, you will not be able to do it. It's a tethered root but being able to backup TA means you can unlock bootloader and lock it again with everything preserved.

xsacha said:
I guess you can donate if you want I didn't put much time in to this and I didn't discover the Android exploit. Most my projects (like Dingleberry for rooting) have a full UI and everything. I have a donate link on my blog: http://www.qtness.com/blog/
That's correct. if you upgrade to 402, you will not be able to do it. It's a tethered root but being able to backup TA means you can unlock bootloader and lock it again with everything preserved.
Click to expand...
Click to collapse
Yeah I will support your good work!
So that means I can flash 69 using flash tool and backup ta using your script, then i can flash 402, unlock bootloader, flash cwm and root? But how should I continue then? How can I relock bootloader and restore ta? And are you sure that root and cwm isn't lost during this process? Is there really no way to find out if bootloader was unlocked after doing this (for warranty reasons)? Has somebody successfully tried out this procedure?
Oh and an other problem, I can't find a 69 ftf anywhere for the Wifi only model sgp511?
BTW I have just donated to you

fleckdalm said:
Yeah I will support your good work!
So that means I can flash 69 using flash tool and backup ta using your script, then i can flash 402, unlock bootloader, flash cwm and root? But how should I continue then? How can I relock bootloader and restore ta? And are you sure that root and cwm isn't lost during this process? Is there really no way to find out if bootloader was unlocked after doing this (for warranty reasons)? Has somebody successfully tried out this procedure?
Oh and an other problem, I can't find a 69 ftf anywhere for the Wifi only model sgp511?
BTW I have just donated to you
Click to expand...
Click to collapse
For the bootloader locking questions, I'm not the best to ask. I am asking about warranty myself on another thread. This is my first sony device so not sure how they operate.
Don't know. I use sgp521.
Technically anything before firmware .402 should work.

Success!
xsacha, GREAT work!
Successfuly unlocked my bootloader and restored DRM keys! Thanks a lot! really appreciate your work:good:
And about the warranty: if you lock the bootloader before bringing the device to the service center the won't be able to find any traces of bootloader unlock! So with your help we don't need to void our warranty.

nos1609 said:
xsacha, GREAT work!
Successfuly unlocked my bootloader and restored DRM keys! Thanks a lot! really appreciate your work:good:
Click to expand...
Click to collapse
So you have done it like this?
flash 69 using flash tool and backup ta using the script, then flash 402, unlock bootloader, flash cwm and root.
But how should I continue then? How can I relock bootloader and restore ta?

fleckdalm said:
But how should I continue then? How can I relock bootloader and restore ta?
Click to expand...
Click to collapse
Just put the backup on your INTERNAL sdcard and then from adb under su type: "dd if=/sdcard/TA.img of=/dev/block/platform/msm_sdcc.1/by-name/TA"

nos1609 said:
Just put the backup on your INTERNAL sdcard and then from adb under su type: "dd if=/sdcard/TA.img of=/dev/block/platform/msm_sdcc.1/by-name/TA"
Click to expand...
Click to collapse
Thanks! I will try it out as soon as I get a 69 ftf for my model...

MoFo Root for Moto X 2013 4.4.4 is Coming - Need Help Making Rooted system.img file

So the DT 4.4.4 has root now, but it does not turn off write protection. It is a different kind of root in that what it lets you do is flash a pre-rooted system image (system.img). So you have to make any mods to the image BEFORE you flash, which is not something your average joe or joette knows how to do.
But for me at least, the Moto X didn't need much modding, just Xposed with Gravity Box, Root Cloaker and Moto Tether.
I have a Dev Ed so I don't need this exploit but I did pull all of the system images from my rooted Dev Ed. The only thing I don't know how to do is to put those into a flashable image file. Does anyone here know how to do that?
I also have the TWRP ext4 system file if that helps.

JulesJam said:
So the DT 4.4.4 has root now, but it does not turn off write protection. It is a different kind of root in that what it lets you do is flash a pre-rooted system image. So you have to make any mods to the image BEFORE you flash, which is not something your average joe or joette knows how to do.
But for me at least, the Moto X didn't need much modding, just Xposed with Gravity Box, Root Cloaker and Moto Tether.
I have a Dev Ed so I don't need this exploit but I did pull all of the system images from my rooted Dev Ed. The only thing I don't know how to do is to put those into a flashable image file. Does anyone here know how to do that?
I also have the TWRP ext4 system file if that helps.
Click to expand...
Click to collapse
thats not a boot unlock and not a write protection disable ... its just ability to install rooted custom system img ....... i think

Javajohn said:
thats not a boot unlock and not a write protection disable
Click to expand...
Click to collapse
Yes I know what it is.
Javajohn said:
... its just ability to install rooted custom system img ....... i think
Click to expand...
Click to collapse
Yes that is what I said it is.
Do you know how I can use the files I have from the system dump and TWRP nandroid ext4 file to create a flashable rooted system.img? That is what I am asking.

JulesJam said:
...
Do you know how I can use the files I have from the system dump and TWRP nandroid ext4 file to create a flashable rooted system.img? That is what I am asking.
Click to expand...
Click to collapse
edit: I misunderstood the question. Of course a CWM/TWRP flashable .zip is not a fastboot flashable system.img...
I'll 'take a stab at this'. I've done it a few times... (I'm sure there is a better guide, but I didn't attempt to find it...) You asked - please don't blame (or hate) me if I help you brick your phone... If you only modify /system, you should be able to restore using CWM/TWRP.
First, find a CWM/TWPR flashable .zip to use it's /META-INFO/ directory as a template. It's best to use a .zip made for your model (so the system mount and format work), and if you can find one for your android version even better. (Do not use an OTA .zip for this template.)
This template will likely [at least] do the following in the "/META-INFO/com/google/android/updater-script" script:
1) mount /system
2) format /system
3) copy /system directory from .zip (need to replace this directory)
4) create symlinks (might need work)
5) set permissions (probably needs work)
If you are only working on /system, then you should remove all superfluous sections (like flashing boot or the modem.)
So, first you need to prepare your new /system: In linux, take your dumped (or backup) /system and copy it to a new /system directory without symlinks. Now you have the new /system for your new flashable .zip
Then you need to modify the "updater-script" script and handle the creation of the symlinks. The easiest way to find this part of the script is locate a flashable zip (or OTA) that patches to your current model/android version. This will handle the bulk of the symlinks.
Next you need to handle the permissions in the "updater-script" script. The aforementioned .zip will also have the permissions scripted, but the root files may not be handled properly. You can find those script commands in a modern flashable zip with root 'baked in.'
Finally take your new /system and new "updater-script" and dump them in your template.... BACKUP (copy off phone) and test.
Good luck...

Ctrl-Freak said:
I'll 'take a stab at this'. I've done it a few times... (I'm sure there is a better guide, but I didn't attempt to find it...) You asked - please don't blame (or hate) me if I help you brick your phone... If you only modify /system, you should be able to restore using CWM/TWRP.
Click to expand...
Click to collapse
Yeah, I am not worrying about a brick as I can wipe my OS entirely and still get into bootloader and recovery so all is good.
Ctrl-Freak said:
First, find a CWM/TWPR flashable .zip to use it's /META-INFO/ directory as a template.
Click to expand...
Click to collapse
My TWRP nandroid of the rooted 4.4.4 system has a meta-info folder with 3 files in it - manifest.mf, cert.sf and cert.rsa.
Ctrl-Freak said:
/META-INFO/com/google/android/updater-script
Click to expand...
Click to collapse
What is this?
Ctrl-Freak said:
So, first you need to prepare your new /system: In linux, take your dumped (or backup) /system and copy it to a new /system directory without symlinks. Now you have the new /system for your new flashable .zip
Click to expand...
Click to collapse
Guess I need to learn what a symlink is first, lol!

JulesJam said:
My TWRP nandroid of the rooted 4.4.4 system has a meta-info folder with 3 files in it - manifest.mf, cert.sf and cert.rsa. !
Click to expand...
Click to collapse
I did not mean your nandroid. Find a flashable zip (made for your device/version) by someone to flash a [custom] ROM. If it flashes a ROM for your device/version, it should be a good starting point.
I looked under xda -> droid turbo and this was the only ROM I found: http://forum.xda-developers.com/dro.../moto-maxx-xt1225-cm12-0-pre-release-t3060089 It says it is for a Moto Maxx xt1225, but again it is only a template, and it might be close.
/META-INFO/com/google/android/updater-script is a text based script that controls what/how CWM / TWRP flashes. AFAIK it is within all flashable zips.

Ctrl-Freak said:
I did not mean your nandroid. Find a flashable zip (made for your device/version) by someone to flash a [custom] ROM. If it flashes a ROM for your device/version, it should be a good starting point.
Click to expand...
Click to collapse
OK thanks, I am doing this for the Moto X 2013, not DT.
Ctrl-Freak said:
/META-INFO/com/google/android/updater-script is a text based script that controls what/how CWM / TWRP flashes. AFAIK it is within all flashable zips.
Click to expand...
Click to collapse
got it.

If this is successful, would there be a way to do it on the AT&T Moto 2013 running 4.4.4?
Sent from my XT1058 using XDA Free mobile app

hexbox117 said:
If this is successful, would there be a way to do it on the AT&T Moto 2013 running 4.4.4?
Click to expand...
Click to collapse
yes, if someone has a GSM Moto X Dev Ed. I don't.

JulesJam said:
yes, if someone has a GSM Moto X Dev Ed. I don't.
Click to expand...
Click to collapse
And would we be able to use Xposed?
Sent from my XT1058 using XDA Free mobile app

hexbox117 said:
And would we be able to use Xposed?
Click to expand...
Click to collapse
Someone has to create a pre-rooted system image with Xposed installed. I think you can then add modules as long as you only do soft reboots. If you do hard reboots, you lose the modules as write protection is still on.
But someone could make a pre-rooted system image with Xposed and the modules you want installed, then it would survive hard reboots AFAIK.
I am still working on how to make a pre-rooted flashable system image, lol!

JulesJam said:
Someone has to create a pre-rooted system image with Xposed installed. I think you can then add modules as long as you only do soft reboots. If you do hard reboots, you lose the modules as write protection is still on.
But someone could make a pre-rooted system image with Xposed and the modules you want installed, then it would survive hard reboots AFAIK.
I am still working on how to make a pre-rooted flashable system image, lol!
Click to expand...
Click to collapse
Interesting. I think you should take a look at this, it sounds like it could be better than what you're trying to accomplish.
http://forum.xda-developers.com/showthread.php?p=59702152
Sent from my XT1058 using XDA Free mobile app

hexbox117 said:
Interesting. I think you should take a look at this, it sounds like it could be better than what you're trying to accomplish.
http://forum.xda-developers.com/showthread.php?p=59702152
Sent from my XT1058 using XDA Free mobile app
Click to expand...
Click to collapse
That was discussed on the DT forums, there is a problem with that on 4.4.4.
For now, the only hope is maiko1's exploit on 4.4.4.

JulesJam said:
That was discussed on the DT forums, there is a problem with that on 4.4.4.
For now, the only hope is maiko1's exploit on 4.4.4.
Click to expand...
Click to collapse
I'm not familiar with what the exploit is. Do you think you could explain it or link me to his post?
Sent from my XT1058 using XDA Free mobile app

hexbox117 said:
I'm not familiar with what the exploit is. Do you think you could explain it or link me to his post?
Click to expand...
Click to collapse
http://forum.xda-developers.com/general/paid-software/mofo-root-turbo-t3064404
So far, it is for the DT only. I want to test it on the Moto X 2013 and then the Moto X 2014. But first, a pre-rooted flashable system.img needs to be created for the Moto X 2013.

JulesJam said:
OK thanks, I am doing this for the Moto X 2013, not DT.
Click to expand...
Click to collapse
If you modify the updater-script to remove the flashing of the kernel (below), then this .zip should be perfect for your testing pleasure:
http://forum.xda-developers.com/moto-x/development/rom-krypton-v1-2-v1-3b1-6-9-2014-t2716657 (download 4.4.4 Krypton v1.4.1 )
Remove this line:
Code:
package_extract_file("boot.img", "/dev/block/platform/msm_sdcc.1/by-name/boot");
Good testing...

Ctrl-Freak said:
If you modify the updater-script to remove the flashing of the kernel (below), then this .zip should be perfect for your testing pleasure:
http://forum.xda-developers.com/moto-x/development/rom-krypton-v1-2-v1-3b1-6-9-2014-t2716657 (download 4.4.4 Krypton v1.4.1 )
Remove this line:
Code:
package_extract_file("boot.img", "/dev/block/platform/msm_sdcc.1/by-name/boot");
Good testing...
Click to expand...
Click to collapse
Thanks, I took a look at the Eclipse Moto X, which is 4.4.4 kitkat based.
http://forum.xda-developers.com/moto-x/development/rom-eclipse-moto-x-v3-2-2-4-4-2-blur-t2521509
But now that I am thinking about it, do these custom ROMs need specific kernels or can you just flash the system w/o flashing the kernel? I guess I will try it and see what happens.

If someone will give me a detailed instruction how to flash a pre-rooted firmware with xposed installed I will try to do so on my AT&T XT1053

RabbitRu said:
If someone will give me a detailed instruction how to flash a pre-rooted firmware with xposed installed I will try to do so on my AT&T XT1053
Click to expand...
Click to collapse
You have to pay $20 to get set up with the exploit, but for now, the guy is only doing Droid Turbos. It is on the paid software forum.
I am trying to see if the exploit works on the Moto X. The dev needs to get back to me but first, I need to try to create a pre-rooted system image.

JulesJam said:
You have to pay $20 to get set up with the exploit, but for now, the guy is only doing Droid Turbos. It is on the paid software forum.
I am trying to see if the exploit works on the Moto X. The dev needs to get back to me but first, I need to try to create a pre-rooted system image.
Click to expand...
Click to collapse
I don't think it will work on the 2013 X... see -> http://forum.xda-developers.com/mot...e-protection-motowpnomo-t2551113/post59731261
And remember, Beaups had an hand in the root exploit and tool for the Droid Turbo along with Jcase... So if Beaups says no, it wont help the 2013 X with 4.4.4, its a pretty sure bet that it wont.

Unable to convert apps to system (GalaxyA8 Sm-a800i)

Hey guys, i quite unfortunately own a galaxy a8 (a800i). It has almost no dev support. After rooting my phone, i tried converting an app to system(through limk2sd). It did but when i rebooted my phone the app disappeared! Had to manually locate the system files (yes they were there, including the apk) and delete them.
Again,tried it with titanium backup, didnt work out.
Also tried moving the folders manually and i took care to set the correct permissions, the app just wouldnt appear.
At last, after deleting all the system app data and files again, i finally placed the apk with correct permissions in the/system/app folder and rebooted my phone. The app was there but it was force closing.
I tried doing this with 4 different apps, to no avail.
I run stock firmware.
(please note- Although a800F and A800i have same hardware, a800i will not support the others custom recovery, root methods,kernels etc.)
Any devs who might be interested in this? Id be glad.

You need to create a folder with the same name as the apk and push the folder to system app.
Then put apk in the folder with same name
Sent from my SM-G903F using Tapatalk

LastStandingDroid said:
You need to create a folder with the same name as the apk and push the folder to system app.
Then put apk in the folder with same name
Sent from my SM-G903F using Tapatalk
Click to expand...
Click to collapse
Tried that too, been working on this since 2 days. Nothing seems to work. I have never encountered an error like this before on any other of my devices. All the pre installed system apps are odexed, and the one im trying is not, for obvious reasons. Do you think it has got something to do with the error?

abhinavparasher said:
Tried that too, been working on this since 2 days. Nothing seems to work. I have never encountered an error like this before on any other of my devices. All the pre installed system apps are odexed, and the one im trying is not, for obvious reasons. Do you think it has got something to do with the error?
Click to expand...
Click to collapse
Hmm missing Libs? Or the odex file itself?
Sent from my SM-G903F using Tapatalk

LastStandingDroid said:
Hmm missing Libs? Or the odex file itself?
Sent from my SM-G903F using Tapatalk
Click to expand...
Click to collapse
No, the lib and the .dex file of the user app im trying to move to system is intact, all im trying to ask is that do you think the system is not accepting the converted app because it has a .dex instead of the regular .odex file which is the case with all system apps?
This assumption might be wild, but considering that i have never faced such an issue before in 10-12 android devices that i have owned in the past, it might be of some use.

abhinavparasher said:
No, the lib and the .dex file of the user app im trying to move to system is intact, all im trying to ask is that do you think the system is not accepting the converted app because it has a .dex instead of the regular .odex file which is the case with all system apps?
This assumption might be wild, but considering that i have never faced such an issue before in 10-12 android devices that i have owned in the past, it might be of some use.
Click to expand...
Click to collapse
Has nothing do do with it, if it's a "user app" as long if the app has all needed files in correct folder it should run. it should be working if it doesn't it might be any issue that the app won't run while in system/app
Sent from my SM-G903F using Tapatalk

So for now, we havnt arrive to any conclusion. All apps break if they are converted to system apps. Tried to do it via TB/Link2sd/various other tools and manually. App components are present in /system/app including the apk and lib, but the app wont appear anywhere on the phone.

abhinavparasher said:
So for now, we havnt arrive to any conclusion. All apps break if they are converted to system apps. Tried to do it via TB/Link2sd/various other tools and manually. App components are present in /system/app including the apk and lib, but the app wont appear anywhere on the phone.
Click to expand...
Click to collapse
That's because it has to be placed inside a folder with the same name as the app
Like /system/app/viper/viper.apk
It can't be /system/app/viper/base.apk
Also libs should be in
System/app/viper/lib/arm/*****.so
Hope this issue helps
Sent from my SM-G903F using Tapatalk

i did try this before. tried it again. It doesnt work. I was extremely careful with directries, app names, libs and permissions.
Like ive said iv done this countless times before on other devices, and it has always worked.
Something else i would like to mention- Thought the app shortcut doesnt appear anywhere, whenever i open the apk file (on my sd card) it says "do you want to update the app" which means the app is actually already installed. I click yes and the app is installed, app icon returns.
I open application manager and open up this app's settings. I get the option of "Uninstall updates" instead of uninstall apps which proves the first time i moved to system, the app became a system app but it disappeared. If i click uninstall updates, the app disappears again. If i try to integrate update with link2sd the app disappears any ways.
There is just no reason for this to happen! So basically im stuck with a phone which barely got a root method, doesnt have a custom recovery, has a enforcing kernel, and doesnt allow me to move apps to /system.
Do you think it might be possible to "flash" the app zip file via a custom recovery? (if we get one for a800i lol)

abhinavparasher said:
i did try this before. tried it again. It doesnt work. I was extremely careful with directries, app names, libs and permissions.
Like ive said iv done this countless times before on other devices, and it has always worked.
Something else i would like to mention- Thought the app shortcut doesnt appear anywhere, whenever i open the apk file (on my sd card) it says "do you want to update the app" which means the app is actually already installed. I click yes and the app is installed, app icon returns.
I open application manager and open up this app's settings. I get the option of "Uninstall updates" instead of uninstall apps which proves the first time i moved to system, the app became a system app but it disappeared. If i click uninstall updates, the app disappears again. If i try to integrate update with link2sd the app disappears any ways.
There is just no reason for this to happen! So basically im stuck with a phone which barely got a root method, doesnt have a custom recovery, has a enforcing kernel, and doesnt allow me to move apps to /system.
Do you think it might be possible to "flash" the app zip file via a custom recovery? (if we get one for a800i lol)
Click to expand...
Click to collapse
Well to be honest I did face same issue with Samsung s health I'm not sure what causes it, can be system related or something.
Don't you have spacex kernel which is set to permissive?
Sent from my SM-G903F using Tapatalk

The only difference is that it happens with me for every app lol.
I did hear about it but im pretty sure its for a800F. Anything related to a800F causes a bootloop in a800i. Someone on the forum tried the spacex kernel. Do you think you can make it compatible somehow?
If nothing works i might just compile a kernel with always_enforce set to false. Then i should be able to change the policy to permissive with seteneforce 0 command.

abhinavparasher said:
The only difference is that it happens with me for every app lol.
I did hear about it but im pretty sure its for a800F. Anything related to a800F causes a bootloop in a800i. Someone on the forum tried the spacex kernel. Do you think you can make it compatible somehow?
If nothing works i might just compile a kernel with always_enforce set to false. Then i should be able to change the policy to permissive with seteneforce 0 command.
Click to expand...
Click to collapse
Are you the dude that's going to test twrp?
I have built a permissive kernel for this device also.
You are welcome to try it.

Sure il try that too. Permissive kernel is something that many of us need. Infact i was gonna make it. Thanks for the effort!
You can pass me the flashable tar file. In the meanwhile, il test the recovery and get back to you.

abhinavparasher said:
Sure il try that too. Permissive kernel is something that many of us need. Infact i was gonna make it. Thanks for the effort!
You can pass me the flashable tar file. In the meanwhile, il test the recovery and get back to you.
Click to expand...
Click to collapse
Here you go, flash with odin or extract the boot.img from the archive and flash with TWRP.
SM-A800I_A800IXXU2AOL2 _boot

ashyx said:
Here you go, flash with odin or extract the boot.img from the archive and flash with TWRP.
SM-A800I_A800IXXU2AOL2 _boot
Click to expand...
Click to collapse
The kernel works perfectly! Root+ selinux set to permissive. Flashed the boot.img with the twrp recovery provided by @ashyx . The recovery as well as the kernel work with no issue whatsoever. The problem with the wifi did not occur this time. Must be related to the old kernel i flashed, it somehow changed the build.prop everytime i flashed something (Including the recovery)
Anyways, now we know that the kernel as well as the recovery works as it should.
I think you should make the post official, recovery as well as root+selinux set to permissive.
Thanks!

abhinavparasher said:
The kernel works perfectly! Root+ selinux set to permissive. Flashed the boot.img with the twrp recovery provided by @ashyx . The recovery as well as the kernel work with no issue whatsoever. The problem with the wifi did not occur this time. Must be related to the old kernel i flashed, it somehow changed the build.prop everytime i flashed something (Including the recovery)
Anyways, now we know that the kernel as well as the recovery works as it should.
I think you should make the post official, recovery as well as root+selinux set to permissive.
Thanks!
Click to expand...
Click to collapse
Released on XDA in Development section: http://forum.xda-developers.com/sam.../kernel-permissive-ll-5-11-kernel-sm-t3312817
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU

:bump:

abhinavparasher said:
:bump:
Click to expand...
Click to collapse
Tried flashing your apps with twrp?
Sent from my SM-G903F using Tapatalk

LastStandingDroid said:
Tried flashing your apps with twrp?
Sent from my SM-G903F using Tapatalk
Click to expand...
Click to collapse
Yes, thats the only thing that works. This issue really garners my interest as i have never seen this happening before.

persistant changes to hosts file following reboot?

Hi everyone. I'm scratching my head here and struggling to find a solution that doesn't require root.
I've got a hosts file that I love as it blocks nearly all advert servers on my phone.
I know there are several adblocking apps but they all require root.
I have had to remove root as I have some critical apps that still don;t work, even after hiding magisk from the apps within the Magisk Manager.
I've got a magisk patched image that I can "fastboot boot" with and can edit the hosts file (after remounting /system as rw) but when I then reboot afterwards, the hosts file has been overwritten.
Can anyone help me please or give me a pointer of how to make the hosts edits remain following a reboot?
edit2add
I am using stock ROM with latest August patches on my Mi A1

You can't without root even if you do it your system partition will be modified and it will result in phone not booting or just safetynet won't pass.
Use a vpn or I'm pretty sure there's app that can fake a vpn with a ad ban list

Dead-neM said:
You can't without root even if you do it your system partition will be modified and it will result in phone not booting or just safetynet won't pass.
Use a vpn or I'm pretty sure there's app that can fake a vpn with a ad ban list
Click to expand...
Click to collapse
Interesting idea regarding spoof VPN.
Do you know how the hosts file is generated? If it's copied over from somewhere during boot then could I edit the source file it's copied from?
If it's generated procedurally, might I be able to script it to add my edits during creation?

wodgey said:
Interesting idea regarding spoof VPN.
Do you know how the hosts file is generated? If it's copied over from somewhere during boot then could I edit the source file it's copied from?
If it's generated procedurally, might I be able to script it to add my edits during creation?
Click to expand...
Click to collapse
System partition ? so that's a good idea but you'll have to compile a rom to change this file. On Linux distro the host file is a thing you can modify easily. On android it's just deprecated by google as it's use mostly used as an adfilter. And google is an ad company. That's my guess.
Anyway host file will always need root even on Linux.
Simply because it can be used against you.
The problem is more on apps that blocks you because you're rooted than being rooted for changing this file.
If any app could modify host then bang you go to YouTube and it redirect you to something else.
Maybe for you it's just an adblock file but it's a little more than that.
So sorry but it's root or vpn.

Dead-neM said:
System partition ? so that's a good idea but you'll have to compile a rom to change this file. On Linux distro the host file is a thing you can modify easily. On android it's just deprecated by google as it's use mostly used as an adfilter. And google is an ad company. That's my guess.
Anyway host file will always need root even on Linux.
Simply because it can be used against you.
The problem is more on apps that blocks you because you're rooted than being rooted for changing this file.
If any app could modify host then bang you go to YouTube and it redirect you to something else.
Maybe for you it's just an adblock file but it's a little more than that.
So sorry but it's root or vpn.
Click to expand...
Click to collapse
So? Could I possibly extract the system.img from the stock ROM, make the edits there and then recompile?
(I've got a copy of payload.bin that I extracted a few weeks ago, when trying to flash the August security patches (this was before I did a compete flash of stock ROM using fastboot)
That actually seems like it wouldn't take too much effort

wodgey said:
So? Could I possibly extract the system.img from the stock ROM, make the edits there and then recompile?
(I've got a copy of payload.bin that I extracted a few weeks ago, when trying to flash the August security patches (this was before I did a compete flash of stock ROM using fastboot)
That actually seems like it wouldn't take too much effort
Click to expand...
Click to collapse
This will lead to a corrupt system partition modified. As i said the worse thing is you could not boot and the good just won't pass safetynet.

Dead-neM said:
This will lead to a corrupt system partition modified. As i said the worse thing is you could not boot and the good just won't pass safetynet.
Click to expand...
Click to collapse
Ok I understand.
How does the device 'know' that the system partition is corrupt? Does it perform a hash check perhaps?
How would compiling my own custom ROM avoid this same problem?

wodgey said:
Ok I understand.
How does the device 'know' that the system partition is corrupt? Does it perform a hash check perhaps?
How would compiling my own custom ROM avoid this same problem?
Click to expand...
Click to collapse
It does many thing to know that its have been touched. You'll have to modify some stuff and it will work. You'll loose certification but you'll have you own rom.

Dead-neM said:
It does many thing to know that its have been touched. You'll have to modify some stuff and it will work. You'll loose certification but you'll have you own rom.
Click to expand...
Click to collapse
Any chance you can outline the other stuff I'd need to change?
If it's really in-depth then don't worry but if it's just a few bullet-points that I can Google more info on, I'd appreciate it.

wodgey said:
Any chance you can outline the other stuff I'd need to change?
If it's really in-depth then don't worry but if it's just a few bullet-points that I can Google more info on, I'd appreciate it.
Click to expand...
Click to collapse
Search "dm-verity" and "safetynet". The first one is what will look at any r/o partition like system and kernel. It's been a long time since i dig into this. I'm not into this anymore.
But You can disable it but you'll loose safetynet, encrypted partition etc... (i may be wrong but you got the idea). And safetynet look if partition have been modified and you are a certified device if it won't pass the banking app and apps like Pokemon go etc won't work.
Magisk hide the fact that the kernel img have been touch and most app that detect it detect just the app itself. That means magisk capability (su, hide and module)
So you could maybe compile stock rom with a custom host file. Never touch vendor partition! Make a backup before! By booting and not flashing twrp. Do not flash twrp just use the "fastboot boot command"
You'll need to make a custom kernel and system img to flash in order to do it.
I'll try to do a rom without anything modded except kernel without dm verity and system with your host and i guess it needs change too.
I dunno if it will pass safetynet after.
Just don't brick your phone ?
Keep in mind that you'll loose ota. There's a chance that the rom work with just some changes but i can be a mess to do.
Why not trying a custom rom like lineage os?
Using their supersu zip won't you be able to replace the host file then remove root?
Once you make a backup a move it to a pc as a savestate. You are free to try different solution

Dead-neM said:
Search "dm-verity" and "safetynet". The first one is what will look at any r/o partition like system and kernel. It's been a long time since i dig into this. I'm not into this anymore.
But You can disable it but you'll loose safetynet, encrypted partition etc... (i may be wrong but you got the idea). And safetynet look if partition have been modified and you are a certified device if it won't pass the banking app and apps like Pokemon go etc won't work.
Magisk hide the fact that the kernel img have been touch and most app that detect it detect just the app itself. That means magisk capability (su, hide and module)
So you could maybe compile stock rom with a custom host file. Never touch vendor partition! Make a backup before! By booting and not flashing twrp. Do not flash twrp just use the "fastboot boot command"
You'll need to make a custom kernel and system img to flash in order to do it.
I'll try to do a rom without anything modded except kernel without dm verity and system with your host and i guess it needs change too.
I dunno if it will pass safetynet after.
Just don't brick your phone ?
Keep in mind that you'll loose ota. There's a chance that the rom work with just some changes but i can be a mess to do.
Why not trying a custom rom like lineage os?
Using their supersu zip won't you be able to replace the host file then remove root?
Once you make a backup a move it to a pc as a savestate. You are free to try different solution
Click to expand...
Click to collapse
Thanks for info I'll investigate later in the week when I have more time. Monday has arrived too quickly!
Appreciated though