Here are some OTA firmware updates which were decrypted, they are fully working and can be installed using the original recovery
Huge thanks to Condi who actually made this possible.
You can check which region/product you have by looking at your build.prop:
Code:
ro.build.description=nbx03_010-user 3.2.1 THMAS0042 0042.004 release-keys
Please look at the next post to see what those numbers mean.
Full OTA:
signed_nbx03_007-ota-0042.017_decrypted.zip
Incremental OTA:
incremental_nbx03_001 0042.001
It would be very helpful, if you would describe the version exactly.
From which country, which version and with or without 3G.
Otherwise it is a risk to flash a "unknown" version.
We should also collect a "region code translation table"
I would like to start with:
Region Code:
001 = USA
007 = Germany
015 = Austria
016 = Poland
Version Code:
0042.017 = 3.2.1R2
11000.014 = 3.2
I have two different versions downloaded:
signed-nbx03_007-ota-0042.017.zip
signed-nbx03_007-ota-11000.014.zip
My device:
Sony Tablet S - 16GB - no 3G - Model: SGPT111DE/S
Could someone explain how we can decrypt a firmware version?
obicom, check PM
Yes, more details needed, we cannot do a blind update.
Sent from my U8800 using Tapatalk
Actually my post was intended to be used by developers, there are some interesting technical information in the update.
I'll try to upload more firmwares once i have time and try to put a list like obicom suggested
uploading full last ota from pl region, for developing purpose, will be ready in ~18min.
signed-nbx03_016-ota-0042.004_decrypted.zip
Great work! Is there anyway you can create an update.zip to replace the /system/sbin, /system/bin, and /system/xbin with the stock or prerooted files?
I ask this because, I tried creating one, but I still get the signature verification failed error.
I have tried signing it with a few different methods, but still failing.
I'm trying to root the device and when I do, I get permission denied with every buysbox command, ie chmod, insmod, etc...
In addittion, I tried running just the update, and that failed because it is the same as my current version. I would think you could just change the update version inbedded in this package...
Great work guys!
Can i ask how to decrypt the zip files?
I want to decrypt my OTA zip too.
Thanks!
Br
norberto
@Condi:
If I take a look into the posted fw .. I am a little bit astonished.
I found three different region.prop files:
one for Austria
one for Switzerland
one for Poland
Does it mean this is the fw file for this three countries?
Do you know what the last three digits of the file name mean?
for Poland 004 and in Germany 017?
Mabay a hint for the included kernel version? (Build)
condi said:
uploading full last ota from pl region, for developing purpose, will be ready in ~18min.
signed-nbx03_016-ota-0042.004_decrypted.zip
Click to expand...
Click to collapse
Is this for wifi or 3g version? Or maybe desn't matter. I ask because I have SGPT111PL/S and the last ota I got 3 days ago was:
signed-nbx03_015-ota-0042.002.zip
obicom said:
@Condi:
If I take a look into the posted fw .. I am a little bit astonished.
I found three different region.prop files:
one for Austria
one for Switzerland
one for Poland
Does it mean this is the fw file for this three countries?
Do you know what the last three digits of the file name mean?
for Poland 004 and in Germany 017?
Mabay a hint for the included kernel version? (Build)
Click to expand...
Click to collapse
The file on my austrian SGPT111AT/S is named "signed_nbx03_015-ota-0042.002.zip"
@Condi & skoperst
Do you know how I can extract the system.img and hidden.img file ?
Do you know what part of our OS is 'hidden' in the hidden.img file?
Is it the kernel image?
Where did you get the 'signed_nbx03_007-ota-0042.017_decrypted.zip' file?
From my point of view, it is exactly "my" firmware file from Germany.
Could you confirm that?
obicom said:
@Condi & skoperst
Do you know how I can extract the system.img and hidden.img file ?
Do you know what part of our OS is 'hidden' in the hidden.img file?
Is it the kernel image?
Where did you get the 'signed_nbx03_007-ota-0042.017_decrypted.zip' file?
From my point of view, it is exactly "my" firmware file from Germany.
Could you confirm that?
Click to expand...
Click to collapse
Yes its your firmware.
system.img is just ext4 partition while hidden.img is not yet fully understood.
My guess its some sort of encrypted package for kernel/recovery/bootloader, maybe more then just one.
But if system.img is a dd image of the system partition, I would guess that 'OTA RootKeeper' cannot work in this case. From my understanding the ota update would overwrite the /system/, system/xbin and /system/bin. Is this correct?
-- Edit --
I found the following string in the 'updater-script':
assert(package_extract_file("system.img", "/dev/block/mmcblk0p3"));
Click to expand...
Click to collapse
so I guess it is not a dd image .. any idea how I can extract such a file?
img's
The img files can be mounted with rw access this way :
cd /media
mkdir tablet_system
mkdir tablet_hidden
mount -o loop -t ext4 system.img /media/tablet_system
mount -o loop -t sysfs hidden.img /media/tablet_hidden
Maybe a way to build pre-rooted roms if the stock recovery accepts uncrypted zips or if we are able to re-encrypt a modified one ?
I'll be very pleased to try something but i need a decrypted french OTA update...
Nesquick95 said:
The img files can be mounted with rw access this way :
cd /media
mkdir tablet_system
mkdir tablet_hidden
mount -o loop -t ext4 system.img /media/tablet_system
mount -o loop -t sysfs hidden.img /media/tablet_hidden
Maybe a way to build pre-rooted roms if the stock recovery accepts uncrypted zips or if we are able to re-encrypt a modified one ?
I'll be very pleased to try something but i need a decrypted french OTA update...
Click to expand...
Click to collapse
Get one using this method:
http://forum.xda-developers.com/showthread.php?t=1511825
@sebarkh
I guess he need a decrypted one .. not only an encrypted ota update.
@Nesquick95
Thanks for the advice. Try to send Condi and/or skoperst your build.prop and region.zip. Maybe they can download an encrypted french version for you.
So, the question is HOW to decrypt.
img's
Some further informations :
My tablet isn't actually rootable because of an unlucky OTA update that leads me from kernel 8 to kernel 10.
I'm trying to find a way to gain root again but i'm not experienced in hacking...
The simple idea is to add the ro.kernel.qemu = 1 in the local.prop of a decrypted firmware and flash it with recovery to gain root with ADB, then push the busybox, su and superuser.apk in the right places.
I've mounted Condi's decrypted firmware with the mount commands given in my last post. Unfortunatly, i've not found the exact image of the tablet's file systems that I expected to.
I'll try to understand how it works anyway.
I join the "ls" of the two img file, if someone wants to take a look.
I also join my build.prop + region.zip if someone (Condi ?) can get a french OTA update and upload it somewhere for me.
Nesquick95 said:
Some further informations :
My tablet isn't actually rootable because of an unlucky OTA update that leads me from kernel 8 to kernel 10.
I'm trying to find a way to gain root again but i'm not experienced in hacking...
The simple idea is to add the ro.kernel.qemu = 1 in the local.prop of a decrypted firmware and flash it with recovery to gain root with ADB, then push the busybox, su and superuser.apk in the right places.
I've mounted Condi's decrypted firmware with the mount commands given in my last post. Unfortunatly, i've not found the exact image of the tablet's file systems that I expected to.
I'll try to understand how it works anyway.
I join the "ls" of the two img file, if someone wants to take a look.
I also join my build.prop + region.zip if someone (Condi ?) can get a french OTA update and upload it somewhere for me.
Click to expand...
Click to collapse
I will start from the end. About getting ota update - ask skoperst - he is an expert in this Second thing - it will not work.
Encryption of update zip is one thing, signature - signing is another thing. You will edit anything in zip - signature failed.
To understand how flash works you don't need your region decrypted ota zip.
Its very hard to get final decrypted update. Two of available - one incremental,
and one full - are fully sufficent to 'understand how it works'
br
condi
Related
So... a lot of us are stuck on a certain firmware and need to get off of it. A solution to us all (hopefully), is a program called "bspatch" (usually comes with bsdiff). We have a boot.img file (compiled android img) and a boot.img.p (from an OTA update, zip, which we know 100% works and people have updated with the OTA zip).
We need bspatch to stop checking for corruption like it does now and to just force the patch to go. This would help save a lot of users stuck on firmware and we would all appreciate a point in the right direction.
We tried compiling the source of bspatch from many sites, but none seem to compile correctly or even run. We get them to run from binary pre-compiled versions, but those won't help us since it sees the patch as corrupt.
If we can get boot.img from the 6.12.181 fastboot files to patch with the boot.img.p from an ICS like the most current (6.16.206 as of 5/20/2012) we can make a fastboot files that is flashable onto someone stuck on 6.14.84 so they can upgrade to 206 with Moto Recovery.
Also if this magically can be done by the help of the XDA community, we can create a boot.img from 6.12.181 patched with a 4.0.3 boot.img.p (like from 84 or 85, since 79 and below aren't flashable on newer ICS), we can also have a root method for 4.0.4 like the GSM users have.
Best of luck to those who try to help with this!
http://www.daemonology.net/bsdiff/
https://launchpad.net/ubuntu/+source/bsdiff/4.3-10ubuntu1/+build/2960721
Files(s): http://rombot.droidhive.com/ROMs/spyder/BspatchProject.zip
alt link: http://www.filefactory.com/file/1xj6eh1mocz7/n/BspatchProject_zip
Note: My friend tried this already and we got Pre-flash validation errors when trying to fastboot it. Just throwing this idea out there.... best of luck.
EDIT: Added as an attachment.
Thanks to dhacker29 for trying this idea out first
Err.. Doesn't the /system/bin/applypatch can do this already??
I've always used it to patch OTA manualy..
example usage:
Code:
applypatch boot.img boot_new.img [B]X Y Z[/B]:boot.img.p
where
Code:
[B]X[/B] is the target(boot_new.img) sha1sum
[B]Y[/B] is the target(boot_new.img) new size
[B]Z[/B] is the source(boot.img) sha1sum
Obviously it will failed the cert test,
if the patch(boot.img.p) is not intended for the base(boot.img)
Information can be extracted from OTA update-script
example
assert(apply_patch("MTD:boot:8388608:5fff8425560eb 1002b467062de2b355b45090ad7:8388608:2997ddb421e1d4 4b026410339e343f60b3bb65bd",
"-", 2997ddb421e1d44b026410339e343f60b3bb65bd, 8388608,
5fff8425560eb1002b467062de2b355b45090ad7, package_extract_file("patch/boot.img.p")));
Click to expand...
Click to collapse
X = 2997ddb421e1d44b026410339e343f60b3bb65bd
Y = 8388608
Z = 5fff8425560eb1002b467062de2b355b45090ad7
easily done via adb
Code:
adb.exe push boot.img /tmp/
adb.exe push boot.img.p /tmp/
adb.exe shell /system/bin/applypatch /tmp/boot.img /tmp/boot_new.img X Y Z:/tmp/boot.img.p
adb.exe pull /tmp/boot_new.img
whirleyes said:
Err.. Doesn't the /system/bin/applypatch can do this already??
I've always used it to patch OTA manualy..
example usage:
Code:
applypatch boot.img boot_new.img x y z:boot.img.p
where
Code:
x is the target(boot_new.img) sha1sum
y is the target(boot_new.img) new size
z is the source(boot.img) sha1sum
Obviously it will failed the cert test,
if the patch(boot.img.p) is not intended for the base(boot.img)
Click to expand...
Click to collapse
I can confirm that applypatch does have at least some success in patching a boot.img once you can figure out the information required from updater-script found in the OTA you are trying to make fastboot images for. I patched the file obtained by
Code:
dd if=/dev/block/mmcblk1p14 of=/sdcard-ext/b/boot.bin
on a 6.12.181 successfully using the code
Code:
applypatch ./boot.bin ./boot.bin.2 dd9310794842a4908aff55979a9fe97f825e8748 8388608 8e21cfa5d9be4dd08427b079fbff9a80d6e04560:boot.img.p
the code i ripped apart from 6.16.206 is
Code:
assert(apply_patch("MTD:boot:8388608:8e21cfa5d9be4dd08427b079fbff9a80d6e04560:8388608:dd9310794842a4908aff55979a9fe97f825e8748",
"-", dd9310794842a4908aff55979a9fe97f825e8748, 8388608,
8e21cfa5d9be4dd08427b079fbff9a80d6e04560, package_extract_file("patch/boot.img.p")));
to figure out the apply patch code i looked at the info above and compared it to this
[qoute]adb shell applypatch
usage: applypatch <src-file> <tgt-file> <tgt-sha1> <tgt-size> [<src-sha1>:<patch> ...]
or applypatch -c <file> [<sha1> ...]
or applypatch -s <bytes>
or applypatch -l
Filenames may be of the form
MTD:<partition>:<len_1>:<sha1_1>:<len_2>:<sha1_2>:...
to specify reading from or writing to an MTD partition.[/quote] and with a little trial and error got it to work
EDIT
Let me be clear the patched boot.bin.2 does flash perfectly fine. no preflash validation failure.
Anyone on 6.16.206 want to do me a favor and do?
Code:
dd if=/dev/block/mmcblk1p15 of=/sdcard-ext/b/recovery.bin
and email/upload it to me? I'll hit the thanks button </bribe>
SilentViper said:
EDIT
Let me be clear the patched boot.bin.2 does flash perfectly fine. no preflash validation failure.
Anyone on 6.16.206 want to do me a favor and do?
Code:
dd if=/dev/block/mmcblk1p15 of=/sdcard-ext/b/recovery.bin
and email/upload it to me? I'll hit the thanks button </bribe>
Click to expand...
Click to collapse
I asked on the DroidRZR thread for 6.16.206 if anyone could do it, let's see
Edit: By the way which version boot.img is patched and flashable, and could we get a copy?
This is what a user at DroidRzr got when he tryed:
dd if=/dev/block/mmcblk1p15 of=/sdcard-ext/b/recovery.bin
[quote name='Fixter' timestamp='1337690349' post='46825']
Doing it right now Matt.
PS: Cannot Open for Read: Permission Denied
Also, I have root. Let me check now. I forgot to restore root.
Update 2: Cannot Open for Write: No such file or Directory. I copy pasted it, so I know it's right.
[/quote]
dimitri407 said:
This is what a user at DroidRzr got when he tryed:
dd if=/dev/block/mmcblk1p15 of=/sdcard-ext/b/recovery.bin
[quote name='Fixter' timestamp='1337690349' post='46825']
Doing it right now Matt.
PS: Cannot Open for Read: Permission Denied
Also, I have root. Let me check now. I forgot to restore root.
Update 2: Cannot Open for Write: No such file or Directory. I copy pasted it, so I know it's right.
Click to expand...
Click to collapse
[/QUOTE]
He might need to do
Code:
mkdir /sdcard-ext/b
He might need to do
Code:
mkdir /sdcard-ext/b
[/QUOTE]
http://www.mediafire.com/?iihwd669mdxg740
Recovery.bin from DR user Fixter from 206.
Enjoy!
dimitri407 said:
This is what a user at DroidRzr got when he tryed:
dd if=/dev/block/mmcblk1p15 of=/sdcard-ext/b/recovery.bin
[quote name='Fixter' timestamp='1337690349' post='46825']
Doing it right now Matt.
PS: Cannot Open for Read: Permission Denied
Also, I have root. Let me check now. I forgot to restore root.
Update 2: Cannot Open for Write: No such file or Directory. I copy pasted it, so I know it's right.
Click to expand...
Click to collapse
[/QUOTE]
Finally, some headway,
But I have a question is in regards to the DD command (kinda off topic but not really). How do you know that p15 is associated with recovery.bin, well at least for Droid Razr XT912-Verizon. I have some tools that show symlinks in an android file browser, but I am looking for a Linux command as well.
Been trying to find access to the devtree partition as well as cdrom, recovery, cdt.bin (p18=true), and now in this case, boot. I found all but devtree. Any ideas,
X
Open the recovery.img in a hex editor and the partitions are listed at the top.
mattlgroff said:
He might need to do
Code:
mkdir /sdcard-ext/b
Click to expand...
Click to collapse
http://www.mediafire.com/?iihwd669mdxg740
Recovery.bin from DR user Fixter from 206.
Enjoy!
Click to expand...
Click to collapse
AWESOME. I successfully flashed that to my secondary razr that i am playing with these updates on. I used this plus my custom patched boot.bin.2 to successfully boot into recovery. but im currently stuck there because no OTAs will flash from that, and my /system partition isn't the right version, nor anything else for that matter. now I need the rest of the /dev/block files from 206 :/
i'm going to have to figure something out quick
Couldn't you just extract the files from the .206 zip file that you need? Unless if I am missing something of course... just one thought I had on this.
No, those are patch files. To make a fastboot package I need the block dumps
Sent from my DROID RAZR using XDA
SilentViper said:
No, those are patch files. To make a fastboot package I need the block dumps
Sent from my DROID RAZR using XDA
Click to expand...
Click to collapse
Makes sense. Hopefully someone running .206 could provide that to you. Sadly I'm unable to as I'm on .203 on my RAZR. Bummer.
Project Success.
http://www.droidrzr.com/index.php/t...m-icsbut-not-back-to-gb-6148485-616203204206/
Great job to everyone involved!
mattlgroff said:
Project Success.
http://www.droidrzr.com/index.php/t...m-icsbut-not-back-to-gb-6148485-616203204206/
Great job to everyone involved!
Click to expand...
Click to collapse
Awesome! mind posting just the fastboot commands? I tried interpreting the .bat but haven't had much experience with .BATs and am not entirely sure what you are doing
DemoManMLS said:
Makes sense. Hopefully someone running .206 could provide that to you. Sadly I'm unable to as I'm on .203 on my RAZR. Bummer.
Click to expand...
Click to collapse
Not anymore you're not!
Sent from the bottom of my fart
SEMI success. We wanna get us back on the path, not on a later ICS build. This might be okay if it works with the OTA, but...
[TSON] said:
SEMI success. We wanna get us back on the path, not on a later ICS build. This might be okay if it works with the OTA, but...
Click to expand...
Click to collapse
Why wouldn't they be able to use this strategy again and use img file from official ota?
Sent from my DROID SPYDER using Tapatalk 2
Knowing Moto...
[TSON] said:
Knowing Moto...
Click to expand...
Click to collapse
I feel like update is pretty close . I would be impressed if they patched it that quickly
Sent from my DROID SPYDER using Tapatalk 2
Hi,
some days ago i brought a new Prestigio Tablet. There was no Root Tool available for this tablet and i did a lot of searching to find a way to achieve root rights.
Today I found a way and want to share my results with you.
The solution is similar to the one described in this Post.
The main difference is the file system of the system image.
In the PMP5080B Rom the system.img is in cramfs and the wendal script unpacks this image onto disk.
The system.img in the PMP5097C is ext3 so you can mount the image directly on a Linux system and copy the Superuser binaries and set the rights with chmod.
copy /B su system\bin\
copy /B Superuser.apk system\app\
chmod -R 0777 system/*
chmod 6755 system/bin/su
chmod 6755 system/app/Superuser.apk
Click to expand...
Click to collapse
after you did this and copied the modified image back into the Temp/Image folder you can use the script to pack the ROM back together.
Now you can flash the new ROM on the usual way like described in the manual.
Hope this helps
Please can you upload the patched image file ..
THX a lot
Here you are:
https://www.dropbox.com/s/lwa1d0v6lotuhwi/rootrom.zip
teddybt said:
Here you are:
https://www.dropbox.com/s/lwa1d0v6lotuhwi/rootrom.zip
Click to expand...
Click to collapse
thx .. i have install the rom but i have no root .....
I checked the uploaded Rom.
The owner of the Superuser files was not root.
Hope this will fix the issue.
Link: https://www.dropbox.com/s/lwa1d0v6lotuhwi/rootrom.zip
Thx Thx Thx... Rooted pmp 5097 now... Your the Best... 1000 Thx
OMG thank you so much for this! I have been waiting a long time for this. You are awesome!
You don't happen to know how to install clockworkmod if its possible do u? Cheers.
Sent from CrazyD's Galaxy II via XDA Android App
Is there any link for this?
I have 1.06 on my tablet and I would like to root it.
I have 1.06 also.
Is there a way to root it?
I found 1.06 root version on a RU site.
This version has 512 MB for apps and later on 1GB for apps ver. should be available.
iJohnny said:
I found 1.06 root version[/URL] on a RU site.
This version has 512 MB for apps and later on 1GB for apps ver. should be available.
Click to expand...
Click to collapse
I installed this onto my 5097 and it hasn't seemed to give me root access at all have i missed something?
smithaz1212 said:
I installed this onto my 5097 and it hasn't seemed to give me root access at all have i missed something?
Click to expand...
Click to collapse
Same problem here
I dont suppose anyone has had any progress with the russian firmware which was posted earlier, still cant seem to gain root access through it for some reason. It might possibly be the same problem as was detailed before in that the owner of the superuser is not root? although i have noticed that there is no superuser app on this firmware, any ideas anyone?
Ok found a firmware that seems to be rooted and is working 100% on my device only small issue is that it is for another tablet (eFun M1005) which seems to be the exact same tablet just rebranded for sale in asia possibly. Anyway:
h t t p ://narod.ru/disk/48873776001.bacdb0ce2f72ba9a6bd089bf055f247a/M1005HN_20120419_V1.0.3_OS4.0_mod_v2.7z.html
As i said is working fine on my tablet and seems to have no problems but i have only tested it for ~1 hour
1.06 root
I found 1.06 root version on a RU site.
This version has 512 MB for apps and later on 1GB for apps ver. should be available.
Click to expand...
Click to collapse
Its no root
I made rooted version of latest v.1.0.6 firmware. But as a new user, I cannot post link
Thanks to daddycruel for posting my link in next post.
Here is the link for download, thank's to gregyk!
http://www.sendspace.com/file/ignk4l
mount
Hi,
I've just downloaded official and rooted 1.0.6 img and I wanted to look into it before flashing. For some reason
Code:
mount -t ext3 -o loop ASBSM1005HN_20120802_V1.0.6.img /mnt
on my box doesn't work (wrong superblock). Did they changed fs or I'm doing something wrong?
BTW thanks for sharing the rom.
Ficik said:
Hi,
I've just downloaded official and rooted 1.0.6 img and I wanted to look into it before flashing. For some reason
Code:
mount -t ext3 -o loop ASBSM1005HN_20120802_V1.0.6.img /mnt
on my box doesn't work (wrong superblock). Did they changed fs or I'm doing something wrong?
BTW thanks for sharing the rom.
Click to expand...
Click to collapse
You must extract firmware file with Wendal RK29xx Image Tools and then you get images (.img) that you can mount in linux (system.img, etc ..).
I rooted like this: extracted firmware with wendal, than mounted system.img in linux - copied "su" and "superuser.apk" and set right permissions to this files. Than packed firmware back together also with wendal tools.
Today I had to send my 5097 for repair ... it won't turn on no more normally. I had to press few times reset, then power and if that didn't work - sometimes it started when I connected it to PC. I tried several different firmwares, but same situation with all.
Anyone heard of or had similar problems?
I Backup-ed my Acer tab b1-A71 using android system recovery - Just like CWM.
The file name ends with .Backup, and i wanted to extract some files from it..
How to Extract data from .Backup file ? - Created with android system recovery
looking for the same
reena0307 said:
I Backup-ed my Acer tab b1-A71 using android system recovery - Just like CWM.
The file name ends with .Backup, and i wanted to extract some files from it..
How to Extract data from .Backup file ? - Created with android system recovery
Click to expand...
Click to collapse
me too looking for the same thing ..how to extract from or decompile .backup file which we get thru recovery.
hi loverboyritesh :: i and you are in same position.. but some advaaanced users are here that we are telling rumors and lies.. dont worry bro.. even i'm trying to get solution.. will tel you after geeing one.. Still no one can tell me hoe to extract .BACKUP file..
same
i am looking for how to reinstall .backup myself so i can have my original rom install.
but i have notice my .backup is 700+mb while custom rom is 200+mb
do you know how to?
reena0307 said:
I Backup-ed my Acer tab b1-A71 using android system recovery - Just like CWM.
The file name ends with .Backup, and i wanted to extract some files from it..
How to Extract data from .Backup file ? - Created with android system recovery
Click to expand...
Click to collapse
same here. dunno how to open and extract the files from a .backup file. hoping you know already
siiingkeeet said:
same here. dunno how to open and extract the files from a .backup file. hoping you know already
Click to expand...
Click to collapse
Nope.. Still i'm having that file but no one knew
reena0307 said:
Nope.. Still i'm having that file but no one knew
Click to expand...
Click to collapse
been searching for 5 days now :<
not a single answer found on google and forums
cant even post a new thread yet. just joined
hope someone will drop by this thread
still no solution?
got same problem here
Got a bootloop issue with an ASUS MeMo Pad 7 HD and I've booted in recovery <3e> to make a backup.
I've got a userdata_YYYYMMDD_HHMMSS.backup. I tried opening it with a bunch of tools like unyaffs, abe (Android backup extractor), going live on the file using linux tools (open as 7zip, zip, rar, tar, tar.gz, gz, bz2 , mount as iso, ext4 and so on....)
Still no luck :-/
Only clue is that the file seems compressed. During the backup under recovery, it told me 3600MB to backup and the file userdata_xxxxxxxx_xxxxxx.backup show only 2.61GB
I did this backup 3 time to ensure there were no corruption during the write process from the pad and did again the same "tests" to open the file...Not better.
If any dev' have any clue of the file format, I'd be glad to help
It doesn't seem to be a valid unix img file. Tried mounting it to no avail. When it's restored by the recovery it also extracts the individual files because i fails on one in my case and stops the entire restore... I tried unzipping it, changed extension to ,jar, .tar, .zip, etc., none of them are recognised...amazing for a standard android feature to find so little info about it
Any solution?
I called Alcatel's technical service today and they told me that you can use the backup file only from the phone. Mine gives me the following error when I try to restore it: Error Magic header
If anyone knows how to unpack the backup file I would be more than grateful.
It's a 512 byte header in front of a "tar.gz"
hexdump -C userdata_xxxxxxxx_yyyyyy.backup | lessshowed the magical zip header "1f8b0800 00000000" at offset 0x200
So, skipping 512 bytes, the rest can be gunzip | tar
dd if=userdata_xxxxxxxx_yyyyyy.backup bs=512 skip=1 | gunzip -c | tar xv
Sir ektoric what d u mean on ur post?
Sorry cant understand it..
Can u please d a step by step procedure? Please...pls...plss
Thanks in advance...
Steps?
@ektoric sir im a noob in this... Can u show a step by step procedure?
@killen00 sorry, I assume you have a linux machine (or have access to one). The command is actually all there is to it.
Code:
dd if=userdata_xxxxxxxx_yyyyyy.backup bs=512 skip=1 | gunzip -c | tar xv
If you don't have a linux machine available, might I suggest one of the many distros of your choice, most of which have LiveCDs which you can run without installing.
script for gunzip method
maybe on xda it is common sense, but for me it was necessary to know, that these stock android recovery extracted files can be restored with nandroid custom recovery, if you simply repack them into tar archive.
i put this two command lines in a dirty shell script (extract + repack as tar).
thanks to ektoric figuring out his gunzip method!
edit: notamamasboy's mount method added (but not tested yet). if script not works come back few days later, download again and check version, maybe it has changed meanwhile.
with this you're able to transfer data of non-rooted phone to (rooted) similar one.
this is useful in case touchscreen is broken, you haven't custom recovery installed, usb-debugging is disabled and connecting usb-otg-mouse doesn't work.
tested on my Archos 50 b Oxygen (Mediatek MT6582).
it works for me, feel free to improve, port to busybox and publish. no support. use at own risk.
edit: bckp2cwm.sh is deprecated it is FOR JELLY BEAN ONLY (no selinux support)
a newer (selinux) version bckp2win.sh for TWRP you can find here:
http://forum.xda-developers.com/showthread.php?t=3775129
How did you go about determining the magic number found at 0x200? My hexdump output does not have that magic number (1f 8b) in any instance. Leads me to believe my backup is not a tar file. Any suggestions then?
@notamamasboy, you are unfortunately correct.
Someone else also mentioned that their
Code:
userdata_xxxxxxxx_yyyyyy.backup
file was not of the same format I tried some "known magic headers", and could not find anything tell-tale. In which case, without some clues, you are back at square one.
ektoric said:
@notamamasboy, you are unfortunately correct.
Someone else also mentioned that their
Code:
userdata_xxxxxxxx_yyyyyy.backup
file was not of the same format I tried some "known magic headers", and could not find anything tell-tale. In which case, without some clues, you are back at square one.
Click to expand...
Click to collapse
Even more peculiarly, two backups were created a .backup and a .backup2, I wonder if combining with cat I can get somewhere...
Manual Updating: How-To Preserve Root Access and Bootloader Unlock!
update... as of Nov 10 2014:
Official Lollipop for D855 and F400 has come out... following my instructions here you can still get bump'd - http://forum.xda-developers.com/showpost.php?p=56650179&postcount=59
So far, no anti-rollback in sight but I would still be careful of future updates.. and all other G3 devices models should be careful before taking an OTA (AT&T/Verizon... maybe).
Follow the steps above and you will ALWAYS have access to root/bump and flash anything you want.
This thread assumes you are already rooted, have TWRP installed and can read English.
If you have those 3 covered the rest is EASY as long as you read.
If you are unsure of any terms used in this post please search XDA/Google instead of asking in here.
Background
I'll get this out of the way right now... if you do not care about having access to Bump or root you can ignore all of this and continue to take LG's OTA updates. One could argue that taking OTA updates is required to maintain any level of safety/security... but that goes out the window once you start rooting and installing recovery/roms anyway. Regardless, I am not telling anyone not to update. But if you do update... do it manually. As of Oct 18 2014, every single G3 variant has root and bootloader unlock.. either out of the box(D851) or thanks to Bump. There is no need to ever take an OTA from here on out. The latest D855 and F400 OTA updates have blocked TowelRoot, IORoot and even Stump.. pretty sure only PurpleDrake works on them for now... I would expect PurpleDrake to be patched soon enough. And with official Lollipop updates coming root will only get harder. But.. as long as we install everything through TWRP manually we can update while keeping root/unlock/Bump.
Yes, we can downgrade using LG FlashTool but that could be blocked at any time with an OTA update to prevent rollback(Samsung does this).
Yes, it's possible to complete an OTA upgrade and maintain root but there is no way to know for sure if root will stick. And the OTA is upgrading the bootloader. Why gamble? This post is just a suggestion on how to stay updated without locking yourself out of anything... but it's not a rule. Just one of many options you can take. But if you do lose root or bootloader unlock after an OTA... don't go asking any devs when then next root tool is coming out or if there's a magical way to downgrade the bootloader. Overview
With all that said... now that we're all rooted and unlocked I decided to make a thread on how to:
1. Block OTA updates and remove OTA packages and that annoying notification. Easy!
2. Download updates manually.. no OTA zip needed. Easy!
3. Manually flash updates without losing root or Bump. Easy!
Most of us have access to the same files found in the latest OTA.. either with a .KDZ or .TOT(Sprint and AT&T refuse to release KDZ files..it seems they would prefer you to not be ale to fix the phone yourself). We can extract the individual partition files from a KDZ/TOT and easily flash them through TWRP. ATT/Sprint users will need leaked TOT files... or something like a pre-patched System.img/Boot.img/Modem.img from a user who has run a modified OTA update... yet managed to keep/regain root. More on that possibly in the future.
The main things we want out of a new OTA update:
A. Radio/Modem.img - although newer isn't always better
B. Kernel/Boot.img - this is often where root is blocked in new updates. But update manually and it no longer matters since we can root system through TWRP.
C. Rom/System.img - this is where most of the "fixes" in updates happen.. and what most people want from an OTA.
D. *Optional: Bootloader stack/Aboot.img,SBL1.img, DBI.img, LAF.img, RPM.img, TZ.img - this is where downgrading and Bump could be blocked. Avoid updating for now unless you are 110% sure you know what you're doing.How-To Block and Remove OTA Updates
If you are flashing custom roms in TWRP.. I'd expect OTA updates to already be removed. If you get an OTA update while running a custom flashable rom be sure to ask the dev why he can't make a proper custom rom that keeps you safe from OTA updates.
Block
Open LG Hidden Menu (3845#*851#) --> WLAN Test --> OTA Setting --> Disable
*Replace "851" with your devices model number, 850, 852, 855 etc.
This seems to only work on D851, D851 and D855 versions (possibly D857/8/9 and F400). AT&T, Verizon and Sprint users have reported the Hidden Menu method does not work. If you have one of those devices you can use a RootExplorer-type app to find the OTA related APK and rename the file to ____.apk.bak or use Titanium Backup to freeze it. If using Titanium Backup look for com.lge.lgfota.permission, OTA or System Update and freeze it. If looking for apk and odex file to rename.. search for OTA or FOTA or LGDMSClient.. etc
If you see an "Apps update" that just might be the "LG Apps" and not a firmware update. Updating LG apps is safe.. firmware is not (if you want to be able to maintain root/mods).
Remove OTA Update(and notification)
If an OTA notification is on your device you most likely already have the OTA file on your phone. If rooted, you can remove the OTA files and get rid of that annoying notification.
Updates are found in the /cache/ folder on your phone. Using a RootExplorer-type app(or ES File Explorer) browse to the root of your phone(NOT the root of your internal storage, /sdcard/, but the actual phone). If using ES File Explorer you may have to use the "show hidden files" option and grant the app root. You will see the update .zip file in cache if you did everything correctly. If no one has already uploaded the OTA zip.. copy the update to your sdcard and then upload for everyone else. Now delete the zip file from /cache/.
Deleting the file in /cache/ will get rid of the OTA but will not get rid of the notification. To get rid of notification:
1. Pull the notification shade down on your phone
2. Long press on the OTA notification until you see the App Info option pop up.
3. Click App Info and uncheck the Show Notifications box.
How-To Download Updates and Extract KDZ/TOT Files
1. Easiest way to obtain updates would be to look in this around XDA in your proper subforum for an update already posted by someone else. With Bump, many flashable rom zips will be popping up. Roms usually contain "system" and "boot"... which are two of the three things we generally want from an update. The third being the modem.. which is never included in a flashable rom and often not required to be updated. If you want the updated modem you will have to look around for the file or use the steps below to get it yourself.
2. If there is a new OTA update, no one has already posted the updated flashable files and you can't wait any longer... it is time to take matters into your own hands. Instead of giving in and taking the official OTA or begging others for help.. download the updated KDZ for your device yourself. And NO, we will NOT be not flashing the full KDZ.. we are just taking some files from it.
You can get your devices KDZ by visiting THIS LINK and entering in your MEID or IMEI.. it will give you a link to the latest available KDZ from LG. Sometimes KDZ files take a few days to show up after the OTA.. give it a little time. Do not beg in thread for KDZ files. Help yourself or wait for someone to post the files you were looking for.
It is encouraged to share not only KDZ and TOT files... but the extracted System/Boot/Modem images you extract from them as well. Only one person needs to download a KDZ per DeviceVariant/SoftwareVersion... that person can then share and everyone else just downloads from their link. You no longer have to be a "rom dev" of even know how to make a flashable zip to help share updates with others.
Anyway... to extract these partitions after downloading the KDZ/tot you can check out the following posts for scripts/tools to make things easy:
a. CLICK HERE [Tool][python] LG Compressed KDZ Extractor - by thecubed Script to extract partitions from KDZ.
b. CLICK HERE SystemMerger.py - by cybojenix Script to merge split system files from extracted KDZ.
c. CLICK HERE [TOOL]LG Bin Firmware Extractor - by xonar_ Script to extract TOT files and merge system.img's into one.
d. CLICK HERE [TOOL] KDZ and TOT Extractor - by bullghost Windows tool, adds all features of the scripts above with an easy to use UI.
invisiblek has updated xonar_'s LGBinExtractor to work with some more G3 devices - https://github.com/invisiblek/LGBinExtractor
If you have a question about an extraction tool be sure to read everything in the 4 threads. Post in the above threads if your question is still unanswered. Between the 5 extraction links above you can extract any G3 KDZ/TOT on Linux, OSX or Windows.
And remember, the main partitions we want from the TOT or KDZ: modem, boot and system.
Alternatively you can extract the KDZ directly on your phone -- click HERE.
Since more than a few people are having issues manually extracting... I will show an example that came from this thread and how to correct it:
KDZFileTools.py -f D85510L_00.kdz -x
[!] Error: Unsupported KDZ file format.
[ ] Expected: 0x28 0x5 0x0 0x0 0x34 0x31 0x25 0x80 ,
but received 0x28 0x5 0x0 0x0 0x24 0x38 0x22 0x25
Two things wrong here... first, the command is incorrect. when using the KDZFileTools.py "-x" is not used.. you want "-s 0" to extract the DZ.
Example:
Code:
python KDZFileTools.py -f D85510L_00.kdz -s 0
The second error is the "Expected.. but received" message. To fix this just open the .py script up in a proper text editor(notepad++ on windows for example).. find "x28x05x00x00x34x31x25x80" in the script...
replace it with "x28x05x00x00x24x38x22x25" (or whatever string is given after the "but received" output.. use logic) then save script.
rerun script. DZ will now extract into the "kdzextracted" folder. Once that finishes extracting you can use the Windows GUI tool to extract the .DZ file into individual partitions (and merge system). Or you can continue using the manual script methods.
To manually extract the DZ you're going to now use the DZFileTools.py script to split the DZ file (that's in the kdzextracted folder) into individual partitions.
Example:
Code:
python DZFileTools.py -f kdzextracted/D85510l_00.dz -x
that command will extract all your partitions into the dzextracted folder. Now drop the SystemMerger.py - by cybojenix file linked above into the dzextracted folder.. cd into the dzextracted folder and run that script to merge all the split system partitions into one system file.
Code:
python SystemMerger.py
All done.. you now have the boot, modem and full system.img to flash on your phone (along with every other partitions that comes with a kdz). :good:
3. Other methods for obtaining updated files would be grabbing the OTA update zip from the /cache folder and trying to pull files out of that.. or having an "in" and getting some leaked files or TOT. Sprint and AT&T users would benefit most from a leaked updated TOT.
Where-To Download KDZ Files
In this section I want to start a collection of all the latest KDZ files for all G3 devices.
You can help me out by either posting your KDZ link with FULL info about the KDZ/DEVICE..
Example of a helpful post:
derp said:
Hi, here is my model info and kdz url below...
LGD855
A6NEWH
D85510L_00
16GB
http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW978806432109876543213/D85510L_00.kdz
Click to expand...
Click to collapse
OR you can PM/Private Message me your IMEI so I can look up all the models and latest KDZ's myself. This would help me the most but I understand the security concern. If security is an issue.. you could leave the last 3 digits off the end so I dont have your exact #. If you trust me.. please consider sending me your IMEI if you own one of the devices I need listed below...
KDZ Links Below
Team Codefire had to come through once again and supply TOT files to the USA carriers that provide no public KDZ (AT&T, Sprint, Verizon)
AS985 (USA Regional) - NEED IMEI
D850 (USA AT&T) - 10D TOT (AT&T has no public KDZ files. Feel free to complain to them.)
D850PR (Puerto Rico Claro) - NEED IMEI
D851 (USA T-Mobile) - 10M KDZ
D852 (Canada) - NEED IMEI for D852 Bell, D852 Rogers and D852G
D855 (Europe) - 10L Netherlands 16GB | 10L Germany 16GB NEED MORE IMEIS
D855AR (Argentina) - NEED IMEI
D855K (Australia) - NEED IMEI
D855P (Brazil / Mexico) - NEED IMEI
D855TR (Turkey) - NEED IMEI
D857 (China) - 10C KDZ NEED IMEI STILL
D858 (China / Hong Kong) - NEED IMEI D858 and D858HK
D859 (China) - NEED IMEI
F400 (Korea)- F400L 20E,
LS990 (USA Sprint) - ZV4 TOT (Sprint has no public KDZ files. Feel free to complain to them.)
US990 (USA US Cellular) - 10C KDZ
VS985 (USA Verizon) - 12B
Click to expand...
Click to collapse
How-To Manually Flash/Update Device w/ System.img, Boot.img and Modem.img
1. You downloaded a custom rom flashable zip a rom has made for the community. Roms contain "system" and "boot"
Flash these in TWRP and follow any instructions in the thread/post where you downloaded it. Rom questions belong in those specific rom threads.
You may have to wipe data/factory reset in TWRP, depending on rom.. or you may need to flash a gapps zip if using an aosp-type rom.. etc..
There's no need to worry about OTA's using this route. Proper custom roms will never include the bootloader stack or anything that could remove your bootloader unlock. And just about all custom roms come with a pre-rooted "system" so you don't have to worry about root either. Remember to make a backup in TWRP before flashing anything.
2. You obtained some boot.img,modem.img,system.img files... either extracting from TOT/KDZ yourself or downloaded files another XDA member has uploaded. This method is something you can do all by yourself... no help from a dev needed. To make this method just as easy as flashing a custom rom zip in method #1.. I have made 3 flashable zip files - [Flash2System.zip, Flash2Boot.zip and Flash2Modem.zip]
Download them to your phone using the link below then follow the directions that follow...
DOWNLOAD FLASH2 FILES FROM CODEFIRE HERE
A. Make a new folder on your internal sdcard called: flash2
B. Download and place Flash2System.zip, Flash2Boot.zip and Flash2Modem.zip on your phone. Internal/external sdcard.
C. Stick system.img, boot.img and modem.img into the /sdcard/flash2/ folder. Files must be named system.img, boot.img and modem.img
D. Create backup's in TWRP.
E. In TWRP, flash Flash2System.zip and/or Flash2Boot.zip and/or Flash2Modem.zip to install your updated images.
F. If you have flashed a stock system.img you will need root. After the flash completes press Reboot System and TWRP will ask if you want root. Go thru the process in TWRP then reboot. After booting you may have a notification to finalize root. Few more clicks and you're rooted... it's that easy. No more worrying if root is patched in the latest OTA update... or having to undo everything you changed in stock so that the OTA doesn't brick you.
Flash2*.zip didn't work? Make sure your system/boot/modem.img files are in the /sdcard/flash2/ folder. Internal sdcard!
How-To Properly Share KDZ/TOT and other Update Files
If you have a new KDZ or have already extracted the KDZ.. please share it with the rest of us in this thread! Please post the KDZ link along with the exact model, region software version and size. Example: D855 Germany 10L 16GB KDZ.
If you want to share your extracted system.img, boot.img and modem.img files please upload them somewhere and share the link. Please specify if you would like others to mirror your files or not (if hosting them on personal server).
Please label all shared files properly! Name them appropriately with boot, modem or system in the name.. as well as the FULL model and software version. Entering my IMEI into the KDZ generator from the last section I can see my device info such as: LGD851TN and D85110M_00. Exact models and software versions are important so other users know which files they need to flash and which to avoid. You should only flash files for your exact device variant. An example name based on my info above: LGD851TN_10M_00_Boot.img (this can be renamed later to boot.img once downloaded or placed on sdcard).
Click to expand...
Click to collapse
More G3 Flash2 Threads:
[FIX] Stuck in Custom Recovery [TWRP/CWM] (After trying OTA)
[EFS] LG G3 EFS Backup and Restore
XDA:DevDB Information
Flash2, Tool/Utility for the LG G3
Contributors
autoprime
Version Information
Status: Stable
Current Stable Version: 1.0
Created 2014-10-18
Last Updated 2014-12-11
Reserved
Nice. On the LS990 (Sprint), it appears that the APK responsible for OTA is titled "com.lge.lgfota.permission" version 4.4.2-LS990ZV41403169216
If I'm looking at the wrong app, someone please correct me, so that other users don't freeze this app and think they're covered, but I froze it and rebooted with no problems.
I also had to run the command line "am start com.lge.hiddenmenu ....[etcetera]" to get into the OTA enable/disable screen.
Block and remove instructions won't show, "spoiler" text reads "blocked"
Sent from my LG-D850
I have Verizon and after i enter : am start com.lge.hiddenmenu/.wlan_service.wifi_ota_buttons in to adb i get an error:
WARNING: linker: app_process has text relocations. This is wasting memory and is a security risk. Please Fix.
WARNING: linker: app_process has text relocations. This is wasting memory and is a security risk. Please Fix.
starting: intent {act=android.intent.acton.MAIN cat =[android.intent.category.LAUNCHER] cmp=com.lge.hiddenmenu/.wlan_service.wifi_ota_buttons} does not exist.
cali4nia831 said:
I have Verizon and after i enter : am start com.lge.hiddenmenu/.wlan_service.wifi_ota_buttons in to adb i get an error:
WARNING: linker: app_process has text relocations. This is wasting memory and is a security risk. Please Fix.
WARNING: linker: app_process has text relocations. This is wasting memory and is a security risk. Please Fix.
starting: intent {act=android.intent.acton.MAIN cat =[android.intent.category.LAUNCHER] cmp=com.lge.hiddenmenu/.wlan_service.wifi_ota_buttons} does not exist.
Click to expand...
Click to collapse
did you install the hiddenmenu.apk as the link instructed?
then entered the following commands like the URL says:
Code:
adb shell
su
am start -a android.intent.action.MAIN -n com.lge.hiddenmenu/com.lge.hiddenmenu.HiddenMenu
which should then give you the hidden menu where you can "WLAN Test --> OTA Setting --> OFF"
Yes I did install the apk as instructed. It does open up the hidden menu after i enter those commands and after that error message but there is no WLAN TEST in the hidden menu that i can see.
---------- Post added at 10:55 PM ---------- Previous post was at 10:42 PM ----------
autoprime said:
did you install the hiddenmenu.apk as the link instructed?
then entered the following commands like the URL says:
Code:
adb shell
su
am start -a android.intent.action.MAIN -n com.lge.hiddenmenu/com.lge.hiddenmenu.HiddenMenu
which should then give you the hidden menu where you can "WLAN Test --> OTA Setting --> OFF"
Click to expand...
Click to collapse
Okay so i got it to the hidden menu to pop up as well as OTA enable/disable page even though it still gives me the same error message. I tap ENABLE and it says ENABLE but then i go back to the hidden menu and it still isn't listed...
EDIT:
Ended up just renaming the LGFOTA.apk file listed in the first reply above. So I should be good to go...
cali4nia831 said:
Yes I did install the apk as instructed. It does open up the hidden menu after i enter those commands and after that error message but there is no WLAN TEST in the hidden menu that i can see.
---------- Post added at 10:55 PM ---------- Previous post was at 10:42 PM ----------
Okay so i got it to the hidden menu to pop up as well as OTA enable/disable page even though it still gives me the same error message. I tap ENABLE and it says ENABLE but then i go back to the hidden menu and it still isn't listed...
Click to expand...
Click to collapse
Don't tap Enable.. Tap Disable... and that's it. OTA disabled... off.. all done.
Someone can provide me with img files? I dont have a PC, just using my phone PM if you can help me.
autoprime said:
word
XDA:DevDB Information
Flash2, Tool/Utility for the LG G3
Contributors
autoprime
Version Information
Status: Stable
Current Stable Version: 1.0
Created 2014-10-18
Last Updated 2014-10-18
Click to expand...
Click to collapse
Don't stick threads.. stick the man
He knows too much
Thanks for all your work
Edit: Can someone sticks his threads ?
Sorry for my noobish post, but where can I find tool for extracting KDZ for LG G3? You just provide link for GitHub, not for .exe program. Thanks.
First of all, thanks for the guide! It will help a lot of users in preserving bump and root
I don't think that leaving boot/etc .img out will help. LG engineers aren't stupid. The can, for example, do it like this: after "m" update all our phones will reflash aboot/etc partitions to patched versions on 1 jan 2015. The partition's images will be hidden in some big system file, while the waiting daemon will be hidden in, for example, healthd. We will never discover it until it's too late. GG WP.
That said, I really doubt that they will do it that way, but this is still a possibility. I guess i'll flash AOSP/CM/OMNI/smthing rom ASAP.
pRo_lama said:
Sorry for my noobish post, but where can I find tool for extracting KDZ for LG G3? You just provide link for GitHub, not for .exe program. Thanks.
Click to expand...
Click to collapse
link a, b ,c , d in the O.P. mate.. He provided all you need.... =)
The Python scripts and Windows GUI App, don't work for my D855 kdz files.
Don't have linux currently setup to test the last one (needs to be compiled).
L10nH34Rt said:
The Python scripts and Windows GUI App, don't work for my D855 kdz files.
Don't have linux currently setup to test the last one (needs to be compiled).
Click to expand...
Click to collapse
I'm on windows 8 mate... use the phython first with the kdz, then you can use the one with GUI for the dz file....
The hidden menu setting ever resets? Not after reboot, factory reset etc?
teddy0209 said:
I'm on windows 8 mate... use the phython first with the kdz, then you can use the one with GUI for the dz file....
Click to expand...
Click to collapse
I get an unsupported KDZ format error, that's my problem.
L10nH34Rt said:
I get an unsupported KDZ format error, that's my problem.
Click to expand...
Click to collapse
Well, I just extracted mine.... d855, v10i..
Check the command...
teddy0209 said:
Well, I just extracted mine.... d855, v10i..
Check the command...
Click to expand...
Click to collapse
I tried to extract v10l and it failed.
i deleted system updates with tibu should i delete LGFOTA.apk? under system,etc security there are a file named otacerts.zip should i delete that one to.
I am stuck can't upgrade my phone through OTA as /system/build.prop and /system/bin debuggered have been modified by some root app.
So I managed to find the link to the OTA .zip and poking through it on the pc I removed the two lines in the update-script which verified the two files.
So the update installs itself without giving errors but when I reboot the phone info displays the same old firmware version.
I was thinking the build.prop is to be looked at but the one in the update is build.prop.p and I can't figure out how to open it.
Can someone point me in the right direction?
The endgame is to upgrade from 4.4.4 to 5.1.1 but I think I have to do one update after the other..
nobody? please helps..