Database Develop

Phone keeps downloading OTA updates -- using lots of Bandwidth

I got message from tmobile saying I had used over 10GB this month, which seemed not right to me.
Looking at my bandwidth usage on tmobile's site I saw lots of 40 MB downloads. So I ran tcpdump on the phone for a while and it looks like maybe my phone keeps downloading an update several times a day from google?
There is a GET /updates/signed-kila-ota-150275.53dde3 to IP of 74.125.47.101 .
I am using a JF build: 1.5 CRB 21 147201 test-keys.
Anyone know why this is happening if what I think is happening is in fact happening Or how I might stop it?
Also, I didn't delete the oacerts or cacerts files:
# ./bash
bash-4.0# cd /system/etc/security/
bash-4.0# ls -l
-rw-r--r-- 1 0 0 47159 Aug 1 2008 cacerts.bks
-rw-r--r-- 1 0 0 1107 Aug 1 2008 otacerts.zip

You could try 1 of 3 of JF's solutions:
1. delete the otacerts.zip file manually. The file is at /system/etc/security/otacerts.zip But keep in mind if you use this method your phone will continuously re-down the OTA and try to verify it, which is bad on your bandwidth usage and your battery life
2. Replace /system/build.prop on your phone with the one from the ADP1 version of JFv1.51
3. chmod 000 the OTA file in /cache (unconfirmed solution, but is likely to work)
Click to expand...
Click to collapse
EDIT: actually not the first one since thats what you're trying to avoid

[R&D] Unlock Verizon Galaxy Note 10.1 - SCH-i925 bootloader

Update: the VZW Ignore 10.1 is now boot loader unlocked and jail broken using the technique and software I outlined in this thread:
http://forum.xda-developers.com/showthread.php?p=41016954
I'm locking this because its done. Use the report button to report this thread to have it unlocked if you need to.
Hey guys,
I just received this device last night, gave it the obligatory teardown, and I'm in the process of collecting resources. From what I can see about the hardware overview, the device is quite similar to the Verizon Galaxy Note 2. However, the process will not be exactly the same as Galaxy Note 2 for several reasons.
1. Exynos Abuse cannot be triggered without a signed kernel of the proper variant. So there will be no Exynos Abuse. However, This http://forum.xda-developers.com/showthread.php?t=2186177 may function similarly.
2. We need an SBoot.bin so @Ralekdev can get started on code-smithing a new bootloader for the device.
3. The partitions may not be mapped the same.
4. A recovery is required which is functional and I have yet to figure out if there is a hardware difference between the i925 and the other variants of this device.
So, my team just needs an Sboot.bin and a Partition Information Table in order to get started. I have high confidence that we can make this a one-click.
Here's some partition info I've gathered so far.
Code:
lrwxrwxrwx 1 0 0 20 Apr 27 03:20 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 0 0 20 Apr 27 03:20 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 0 0 21 Apr 27 03:20 CACHE -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 0 0 20 Apr 27 03:20 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 0 0 21 Apr 27 03:20 HIDDEN -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 0 0 21 Apr 27 03:20 OTA -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 0 0 20 Apr 27 03:20 PARAM -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 0 0 21 Apr 27 03:20 RADIO -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 0 0 20 Apr 27 03:20 RECOVERY -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 0 0 21 Apr 27 03:20 SYSTEM -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 0 0 21 Apr 27 03:20 TOMBSTONES -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 0 0 21 Apr 27 03:20 USERDATA -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 0 0 20 Apr 27 03:20 m9kefs1 -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 0 0 20 Apr 27 03:20 m9kefs2 -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 0 0 20 Apr 27 03:20 m9kefs3 -> /dev/block/mmcblk0p6
Looks like UART is enabled by default so there should be a pin which can be monitored on the dock connector during startup.
Code:
console=ttySAC2,115200 loglevel=4 androidboot.baseband=mdm
and here's a zip containing the partitions themselves. I removed my own EFS from there though.
Code:
http://d-h.st/SPx

Update. Was able to pull the pit from the device.. http://d-h.st/dRR Its unclean but it will do for now.
Still need the Sboot

Finally, a developer for our variant.
Sent from my SCH-I925 using xda premium

This is outstanding, we are getting some love, thanks adam and the rest of the team. This model has some serious potential over some of the other model numbers that are out there being produced right now. I love this thing, never thought Id like a tablet, but this thing kills it. Thanks adam and Ill be sending a few beers at you.

Thanks Adam u guys kick a$$. Suckitverizon!!
TaPpEd from my TwEaKeD N2

I'm new to this Note 10.1 (just got it from vzw today). So Adam is working to get the VZW version of the Note10.1 unlocked?
Sent from my Galaxy Nexus using xda app-developers app

omfgbfs said:
I'm new to this Note 10.1 (just got it from vzw today). So Adam is working to get the VZW version of the Note10.1 unlocked?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Sure looks that way. Just like the n2. Verizon better get to work to keep up with those guys!!!
TaPpEd from my TwEaKeD N2

I built a recovery and pulled a pit (which it sounds like you did too) for this mid March for a user but obviously no way to boot and test it yet so ymmv and take caution with it. They're obscuring the partitions that contain the sboot and the storage driver is compiled directly into the kernel. I spoke with ralekdev a bit about this device last month but without the sboot there was nothing to do yet. If you guys get the BL working hit me up and I'll fix up any issues in recovery that might exist.
I sourced the sboot.bin from the korean LTE variant of the tab and offered that last month too as perhaps it could be used but never heard back from him. So that file might be of interest if it could be used on the i925, else probably need to wait for an OTA from big red. I'll defer to someone with far more knowledge in ida pro. If it is, should be easy to leverage similar ideas used before on exynos4 devices to get a working BL. If it's not, at least the recovery I made should help someone.
Attached are the files from the work I started:
good luck with it.

I noticed in your tear down of SCH-I925 The N8020 label on more than 2 locations of the mainboad. This suggests to me that we are dealing with a Verizonized GT-N8020? Are the sboot.bin and recovery.img from the published N8020 any benefit your efforts? Forgive my newbeness
Sent from my GT-N8020 using XDA Premium HD app

waston2013 said:
I noticed in your tear down of SCH-I925 The N8020 label on more than 2 locations of the mainboad. This suggests to me that we are dealing with a Verizonized GT-N8020? Are the sboot.bin and recovery.img from the published N8020 any benefit your efforts? Forgive my newbeness
Sent from my GT-N8020 using XDA Premium HD app
Click to expand...
Click to collapse
Yeah, im sure they are. The problem here is there is no clear path back to stock. We have the required tools to test an unlock right now. @Ralekdev could whip up a new bootloader for the Exynos that would function on this device fairly easily.
The problem is that the Verizon Modem does not play nicely with other bootloaders. So you'd end up with a device which continuously reboots or works as a wifi-only model. And we can do that. But theres still no way to get it back to stock.
Hell, maybe we should just release it like that, provide a tool which will brick the device, and let the RMAs handle it. But the proper way is to get a stock bootloader.

Ok. With that said, I have a sacrificial SCH-I925 sent to me by Verizon by accident (long stoy). Can we succesfully make it an N8020 without concern of returning to stock? I have tried to flash stock N8020 through odin, ofcourse unsuccessfully.
I have rooted and run Triangle Away on another SCH-I925 leaving me with a Note that said "unauthorized software detected, please return to nearest Verizon store" I did and they replaced with the Note I am using now.
With explicit instructions I can attempt to prove any and all of your THEORIES on this "extra SCH-I925" I have. As I am not a developer please be detailed.
Best regards [email protected]
Sent from my SCH-I925 using XDA Premium HD app

waston2013 said:
Ok. With that said, I have a sacrificial SCH-I925 sent to me by Verizon by accident (long stoy). Can we succesfully make it an N8020 without concern of returning to stock? I have tried to flash stock N8020 through odin, ofcourse unsuccessfully.
I have rooted and run Triangle Away on another SCH-I925 leaving me with a Note that said "unauthorized software detected, please return to nearest Verizon store" I did and they replaced with the Note I am using now.
With explicit instructions I can attempt to prove any and all of your THEORIES on this "extra SCH-I925" I have. As I am not a developer please be detailed.
Best regards [email protected]
Sent from my SCH-I925 using XDA Premium HD app
Click to expand...
Click to collapse
@Ralekdev should have something tonight. I'll package it up and get it ready for distribution. If you'd like to beta, send me an email via my profile. It will be later tonight at earliest.

Its coming

Anyone who would like to pre-test can do so.
You must have java installed on your computer then run this: http://d-h.st/q2R
I'm preparing a post right now. The unlock was similar to the Galaxy Note 2 in most respects.

http://forum.xda-developers.com/showthread.php?p=41016954

AdamOutler said:
Anyone who would like to pre-test can do so.
You must have java installed on your computer then run this: http://d-h.st/q2R
I'm preparing a post right now. The unlock was similar to the Galaxy Note 2 in most respects.
Click to expand...
Click to collapse
This worked for me Adam. Thanks again to you and all how contributed to this

waston2013 said:
This worked for me Adam. Thanks again to you and all how contributed to this
Click to expand...
Click to collapse
Great! Would you be so kind as to post in here? http://forum.xda-developers.com/showthread.php?p=41016954
This thread is done now. I will update the first post.

[Q] 4.4

how to fix at&t 4.4 update on my note 3....it makes it to 27% and stops...

hitlab1 said:
how to fix at&t 4.4 update on my note 3....it makes it to 27% and stops...
Click to expand...
Click to collapse
I hate to say this since I'm not a moderator, questions need to go into the Question/Help thread.
Also, you need to read the post (located in this General thread) and do a little search and research to help you. I'm even nice enough to provide you a link (http://forum.xda-developers.com/showthread.php?t=2686652) which is the Official - the 4.4.2 update - discussion thread.
However,
To begin, you must be on NB4 (the small update that happened a few weeks ago. Also, if you have NOT installed the 4.4 leak, and didn't really do anything to your phone but only rooted.
or
You didn't even root your phone, just can't get passed the 27% of the OTA update, please follow these instructions:
USER BEWARE, THESE INSTRUCTIONS WILL ROOT YOUR PHONE. I'M NOT RESPONSIBLE FOR ANY DAMAGES YOU CAN CAUSE. THIS IS (please forgive me, my caps lock was on) to help you get the update.
1 ) On you Windows computer, go to http://www.kingoapp.com/
2) Download Kingo and install.
3 ) Make sure you have the required Samsung drivers installed also so your phone can communicate with your computer (use the USB 3.0 cable that came with you phone).
4 ) before you connect with the computer:
A ) go into setting (in your phone) and turn on USB debugging. If you don't know how to turn that on, there is instructions within the Kingo software itself.
B ) Set your screen timeout option for 10 minutes.
C ) Also remove your lock screen to none.
5 ) With your phone on, attach the USB cable. It should connect (you'll hear multiple sounds)
6 ) The Kingo software should recognize your phone and give you the option to Root. Please do so (this will not trip your KNOX flag).
7 ) Pay close attention to your phone's screen while going through the rooting process, popups will happen and you will be asked to click approve various functions that is required for root.
8 ) After root is successful, detach you phone. Go to the Google Play store and download Root Explorer. I have the premium version (it worth the few dollars, plus it helps out the programmers).
9 ) Open Root Explorer (or any file manager with root access) and go to /system/csc/
10 ) Look for feature.xml.bak. If this exists, delete feature.xml and rename feature.xml.bak to feature.xml
11 ) See if dexdump is in /system/xbin/ if not down Download dexdump from Jakman85 - http://forum.xda-developers.com/showpost.php?p=51440984&postcount=313
12 ) Copy dexdump to /system/xbin and set correct permissions. Root Explorer will request the directory to be made r/w temporarily while the file is inserted then put it back r/o, however you still need to set the correct permissions for that individual file. The best way is tap and hold another file already in that directory and select permissions and see how to properly set the dexdump permissions. Make sure the permissions match the other files.
13 ) Check for Update and let it do it's thing, or you can sideload the 2400258.zip file (you can download this from a link earlier in another thread) and install it from stock recovery from your sccard.
Note : on first startup after upgrade I did not have touch screen access but the S-PEN did work. However, you can simply restart the phone to get the screen working with touch.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app

Want a LBL Lollipop root method for the Xperia ZR? Keep reading.

Hi all!
I'm happy to say that, thanks to iovyroot, and with a lot of help from zxz0O0, we managed to create a new root tool for the Xperia M2, EagleRootTool, meaning we don't actually need to use Kingroot anymore to root LBL devices under latest Lollipop firmware :victory:
However, since this root binary is compatible with (probably) any kernel built before December 2015, I thought of making the tool compatible with some other devices, like your ZR, since it's actually very similar to my device.
Unfortunately, since this tool's based on some kernel-specific addresses, to make it compatible with other devices like the ZR, I need them from every single variant.
I'm going to take for reference all models and firmware build numbers from XperiFirm.
WHAT YOU NEED:
- An already rooted device in 10.7.A.0.228 (10.7.A.0.222 might be compatible too) (it doesn't matter if it was rooted by Kingroot, or via UBL methods).
- A little of Android general knowledge: Usage of ADB (mainly).
- Patience.
DEVICES:
- C5503 ✓
- C5502
HOW TO DO IT?:
Just open an ADB prompt and run a shell in it. Then, run the following commands, replacing the *location with storage/sdcard1 if you want to use your SD Card, or with data/media/0 if you want to use the internal memory.
Code:
su
cat /proc/version > /[COLOR="Purple"]*[/COLOR][COLOR="red"]location[/COLOR]/version.txt
echo 1 > /proc/sys/kernel/kptr_restrict
cat /proc/kallsyms > /[COLOR="Purple"]*[/COLOR][COLOR="red"]location[/COLOR]/kallsyms.txt
(remember to hit enter after each line of the above :silly
Now upload those two files (version.txt & kallsyms.txt) wherever you want, or attach them in your comment, saying which model they're from, and I'll add the required offsets to support your device manually!
________________________
DISCLAIMER: This is NOT a placeholder NOR Spam thread. I just want to help this device users to get them supported in a common Lollipop Xperia rooting toolkit, since this device won't get Marshmallow, and has a compatible kernel. If you, moderator or user, decide to close/report this thread, I may understand it, but think it twice before doing it.

Definitely interesting.
In case no one is quicker I'll give the commands a go and revert when I'm home during the week.
Another note, any possibility for getting this on another complete different device? (I am looking for my daily one, a vk6050s which has a kernel date of Nov 6)
Sent from my vk6050s using Tapatalk

rufy93 said:
Definitely interesting.
In case no one is quicker I'll give the commands a go and revert when I'm home during the week.
Another note, any possibility for getting this on another complete different device? (I am looking for my daily one, a vk6050s which has a kernel date of Nov 6)
Sent from my vk6050s using Tapatalk
Click to expand...
Click to collapse
I see no problem (apart from being 64bits, it might be harder to get the offsets) on adding compatibility for it, however the mentioned root tool is only prepared for XPERIA devices, since it disables RIC and does some other things that'd probably mess something up in a almost "AOSP" device. Once you run the binary, you get as a result an elevated shell, as root, so you can now mount the system as rw and add the supersu files in there (from lines 44 to 146, and from 169 to 181 in the install_tool.sh provided with EagleRootTool).

It's worth a try for the vk if you are up for it (anyways, we can move that discussion over to PM)
For the C5503 i have included the two requested files in the attached 7z. (XDA won't let me upload kallsyms.txt unless i zip it, tooo big)

rufy93 said:
It's worth a try for the vk if you are up for it (anyways, we can move that discussion over to PM)
For the C5503 i have included the two requested files in the attached 7z. (XDA won't let me upload kallsyms.txt unless i zip it, tooo big)
Click to expand...
Click to collapse
Added https://github.com/sergiocastell/iovyroot/blob/patch-1/jni/offsets.c#L285
C5502 is still remaining.
Check your PM.

Here I have c5502 (10.7.A.0.222)
Regards!

[WIP] 1 Click Partition Back-Up v0.1

YOU MUST HAVE ROOT ACCESS TO PROCEED
THIS WILL NOT WORK IF YOU DON'T HAVE ROOT
A MINIMUM TEMPORARY SPACE OF 400MB ON YOUR INTERNAL STORAGE IS REQUIRE FOR THIS BACKUP PROCEDURE
THIS PROGRAM IS FOR PARTITIONS BACKUP PURPOSES AND NOTHING ELSE ​
Hello everyone,
After trial and error and keep trying with lot of errors finally got this puppy working, backups 19 Partitions from your device, i don't know if the A2017 (chinese variant) have the same partition table but as far as i know and have seen the A2017U and A2017G does have the same partition table which is awesome for any Rom developers to work on things or any dev.
Steps:
1- Download the zip file from here 1CLick_Partition_Backup_v0.1
2- Decompress anywhere you want (i prefer in the root of drive C: )
3- Make sure you have enable USB-Debbuging
4- Plug your Device
4- Double Click 1click_PartitionBackup_by_DrakenFX.exe and watch the program run
5- When Done your Partition Back-up will be in you C:/a2017u_partitions_backup folder
6- DONE
This is just the beginning i may be adding more Options like Single backup or group backup.
NOTE 01 : I didn't add the system partition backup for the sole reason of been huge file 6gb at least and I can add system in future update as separate option.
NOTE 02 : I'm not a savvy when comes to dev. but if i can do something that can help other do things a little easier , i'll be around

Reserve 01

Reserve 02

Do we have any way to restore these backups after?

XblackdemonX said:
Do we have any way to restore these backups after?
Click to expand...
Click to collapse
There is a way using flashable zip via TWRP, but I'll look into for something else... I'm new to all this so still learning , fastboot is another way but I'll look into it

I had to disable windows defender in order to download this. It kept flagging it as malware. Just a heads up.

CandyFoxJ said:
I had to disable windows defender in order to download this. It kept flagging it as malware. Just a heads up.
Click to expand...
Click to collapse
really? i'm ensure you there's no malware or anything malicious in this file.... i have downloaded and my windows doesn't detect anything. (Win10 Latest Update)

I've seen it throw false positives before, I'm not worried about it. Probably the packer used in your app. This is what it picked up.

Since this is XDA after all, you should probably either post your source and/or release it as a script/command list. It's not really security friendly to release a .exe that runs root commands. It could probably be run all as a batch command.

CandyFoxJ said:
I've seen it throw false positives before, I'm not worried about it. Probably the packer used in your app. This is what it picked up.
Click to expand...
Click to collapse
Could be cuz the commands it runs?
the zip file contains the following...
-adb.exe
-adbWinApi.dll
-adbWinUsbApi.dll
-1click_PartitionBackup_by_DrakenFX.exe
adb files needed just in case the user doesn't have adb install and these 3 files will do the job, Why sees it as Malware i really don't know but for command it have to Pull the Partitions out of the device.

---------- Post added at 09:06 PM ---------- Previous post was at 09:04 PM ----------
[/COLOR]
DrakenFX said:
YOU MUST HAVE ROOT ACCESS TO PROCEED
THIS WILL NOT WORK IF YOU DON'T HAVE ROOT
A MINIMUM TEMPORARY SPACE OF 400MB ON YOUR INTERNAL STORAGE IS REQUIRE FOR THIS BACKUP PROCEDURE
THIS PROGRAM IS FOR PARTITIONS BACKUP PURPOSES AND NOTHING ELSE
Hello everyone,
After trial and error and keep trying with lot of errors finally got this puppy working, backups 19 Partitions from your device, i don't know if the A2017 (chinese variant) have the same partition table but as far as i know and have seen the A2017U and A2017G does have the same partition table which is awesome for any Rom developers to work on things or any dev.
Steps:
1- Download the zip file from here 1CLick_Partition_Backup_v0.1
2- Decompress anywhere you want (i prefer in the root of drive C: )
3- Make sure you have enable USB-Debbuging
4- Plug your Device
4- Double Click 1click_PartitionBackup_by_DrakenFX.exe and watch the program run
5- When Done your Partition Back-up will be in you C:/a2017u_partitions_backup folder
6- DONE
This is just the beginning i may be adding more Options like Single backup or group backup.
NOTE 01 : I didn't add the system partition backup for the sole reason of been huge file 6gb at least and I can add system in future update as separate option.
NOTE 02 : I'm not a savvy when comes to dev. but if i can do something that can help other do things a little easier , i'll be around
Click to expand...
Click to collapse
OMG!
This is nice!
But I'm running linux!
You make the script universal please.
Or I could write one myself...

manu7irl said:
OMG!
This is nice!
But I'm running linux!
You make the script universal please.
Or I could write one myself...
Click to expand...
Click to collapse
if i only knew how to this in java (Universal) i'll do it in a flash, but i have no clue....i'm creating a new file and may by i'll do it as .bat (you can look it up if i release it this way with some choices and adding probably more partition if i have miss any + separate choice for system dumb (is way to big of a file),
P.S. if you know java PM

DrakenFX said:
if i only knew how to this in java (Universal) i'll do it in a flash, but i have no clue....i'm creating a new file and may by i'll do it as .bat (you can look it up if i release it this way with some choices and adding probably more partition if i have miss any + separate choice for system dumb (is way to big of a file),
P.S. if you know java PM
Click to expand...
Click to collapse
Bat file is good for me...
You can check the partition list under
Code:
ls -al /dev/block/....

manu7irl said:
Bat file is good for me...
You can check the partition list under
Code:
ls -al /dev/block/....
Click to expand...
Click to collapse
Yeah I have the partition table by-name , just don't see the need of adding every single one but just the necessary ones (modem, Bluetooth, aboot, few more) and I'll add system in the next release.....

DrakenFX said:
There is a way using flashable zip via TWRP, but I'll look into for something else... I'm new to all this so still learning , fastboot is another way but I'll look into it
Click to expand...
Click to collapse
you could fire up twrp or any terminal app.
In twrp mode:
Just comnect your device to your PC with adb installed.
Push the partition image you want to flash in /sdcard/ folder.
Code:
adb push [IMAGE.IMG] /sdcard/
then do:
From your PC, run first:
Code:
adb shell
Then do,
Code:
su
dd if=/sdcard/[IMAGE.IMG] of=/dev/block/bootdevice/by-name/[NAME OF IMAGE]
Example:
Code:
dd if=/sdcard/modem.bin of=/dev/block/bootdevice/by-name/modem
This will overwrite the chosen partition as dd works at a very low command level.
Do not try to flash recovery or boot or aboot through this if you are on locked bootloader. this will brick your device.
Do not try this at home if you don't know what you are doing, you may kill your neighbor's dog or worse the cat.

I made a script to backup any partition in our A7:
YOU HAVE TO BE ROOT, TO USE IT.
To run it simply push to the sdcard fire up adb shell to launch the script.
from the computer while connected to the A7 with usb debugging turned on
Code:
adb push PATH_to_the_script/full-backup.sh /sdcard
and
Code:
adb shell
su
cd /sdcard/
sh full-backup.sh
you will see a menu to choose which partition to backup.
As in the attachment.
enjoy, and please hit the thanks button.