Related
The partition layout of the SGS3 is the following:
/dev/block/mmcblk0p9 /system ext4
/dev/block/mmcblk0p12 /data ext4
/dev/block/mmcblk0p8 /cache ext4
/dev/block/mmcblk0p3 /efs ext4
So, backing up efs with adb is easy:
'adb shell'
'dd if=/dev/block/mmcblk0p3 of=/sdcard/efsbackup.img'
'exit'
'adb pull /sdcard/efsbackup.img'
And there you go.
Restoring it is nearly the same process, but *surprise* reversed.
Only restore your efs partition if it's absolutely necessary. Yes, there is only a 0.01% chance of corrupting your efs partition/backup while doing the backup or restore but I won't be able to help you if you corrupt your backup or partition. You've been warned.
The usual disclaimer applies here: I nor XDA-developers.com are responsible for any damage you do to your phone.
But if you must know:
'adb push efsbackup.img /sdcard/efsbackup.img'
'adb shell'
'dd if=/sdcard/efsbackup.img of=/dev/mmcblk0p3'
'exit'
And if you want to be absolutely sure there's no garbage left on your efs partition prior to restoring it:
'adb push efsbackup.img /sdcard/efsbackup.img'
'adb shell'
'dd if=/dev/zero of=/dev/block/mmcblk0p3'
'dd if=/sdcard/efsbackup.img of=/dev/mmcblk0p3'
'exit'
But, and yes this is a major problem. Adb shell isn't functioning properly on our SGS3. As I mentioned in this thread, you can only use one adb shell command per cmd window. If you want to do two things in adb shell, you'll have to open a new command prompt and enter the second command which isn't a huge disaster but it's quite annoying, especially if you've got some heavy duty shell work.
you can also use this for EFS Folder Backup
http://forum.xda-developers.com/showthread.php?t=1308546
Test:
http://translate.google.com/transla...sa=X&tbo=1&tbas=0&biw=1680&bih=925&prmd=imvns
I wonder if there are any information about other partitions? There are suppose to be 12 partitions. I only know the purpose of a couple of them.
Below is what I can find so far.
/dev/block/mmcblk0p1 - unknown
/dev/block/mmcblk0p2 - unknown
/dev/block/mmcblk0p3 - /efs
/dev/block/mmcblk0p4 - unknown
/dev/block/mmcblk0p5 - kernel
/dev/block/mmcblk0p6 - recovery
/dev/block/mmcblk0p7 - unknown
/dev/block/mmcblk0p8 - /cache
/dev/block/mmcblk0p9 - /system
/dev/block/mmcblk0p10 - unknown
/dev/block/mmcblk0p11 - unknown
/dev/block/mmcblk0p12 - /data
Supposing some of the unknown ones are bootloader related.
what partition is for modem?
Thx.
thanks to both of you guys for posting this! i was wondering what the partition layout looked like. now i'm ready to start tweaking even if we don't get root for US versions day1. this is unlikely, though.
Samsung Galaxy S3 I9300 Full Partition Layout
This should fill in the "blanks". From my system dump yesterday when I was searching for the modem (radio) partition. Check my guide in the sig
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
That's great information! The only remaining question is the mapping of sboot.bin and tz.img. I often see these two partitions in many ROMs. It seems likely that these are the first 2 partitions.
Thijs96 said:
.............But if you must know:
'adb push efsbackup.img /sdcard/efsbackup.img'
'adb shell'
'dd if=/sdcard/efsbackup.img of=/dev/mmcblk0p3'
'exit'
And if you want to be absolutely sure there's no garbage left on your efs partition prior to restoring it:
'adb push efsbackup.img /sdcard/efsbackup.img'
'adb shell'
'dd if=/dev/zero of=/dev/block/mmcblk0p3'
'dd if=/sdcard/efsbackup.img of=/dev/mmcblk0p3'
'exit'
.........
Click to expand...
Click to collapse
Hey, why are the /block/ parts missing in some lines of code? looks like an error, isn't it? It should always be /dev/block/mmcblk0p3 if I'm not wrong
Thanks.
WT Ho said:
That's great information! The only remaining question is the mapping of sboot.bin and tz.img. I often see these two partitions in many ROMs. It seems likely that these are the first 2 partitions.
Click to expand...
Click to collapse
The sboot.bin is stored in the mmcblk0p1 partition. No idea what the tz.img stands for though...
is this info still the exact same info for SPH-L710 (Sprint CDMA) S3 Device?
its running android 4.1.1 stock but im rooted and have CWM installed
en11gma said:
is this info still the exact same info for SPH-L710 (Sprint CDMA) S3 Device?
its running android 4.1.1 stock but im rooted and have CWM installed
Click to expand...
Click to collapse
Have a look here http://forum.xda-developers.com/showthread.php?t=1959445
Perka said:
Have a look here http://forum.xda-developers.com/showthread.php?t=1959445
Click to expand...
Click to collapse
i did a search there for sph-l710 (my model and nothing came up)
i dont think that thread was for this phone so i guess the question remains.
is the partition tables in the (1st page) not just the first post correct for SPH-L710?
WT Ho said:
I wonder if there are any information about other partitions? There are suppose to be 12 partitions. I only know the purpose of a couple of them.
Below is what I can find so far.
/dev/block/mmcblk0p1 - unknown
/dev/block/mmcblk0p2 - unknown
/dev/block/mmcblk0p3 - /efs
/dev/block/mmcblk0p4 - unknown
/dev/block/mmcblk0p5 - kernel
/dev/block/mmcblk0p6 - recovery
/dev/block/mmcblk0p7 - unknown
/dev/block/mmcblk0p8 - /cache
/dev/block/mmcblk0p9 - /system
/dev/block/mmcblk0p10 - unknown
/dev/block/mmcblk0p11 - unknown
/dev/block/mmcblk0p12 - /data
Supposing some of the unknown ones are bootloader related.
Click to expand...
Click to collapse
odia gives this to restore bootloaders
# dd if=/sdcard/sboot.bin of=/dev/block/mmcblk0p1
# dd if=/sdcard/tz.img of=/dev/block/mmcblk0p2
# dd if=/sdcard/param.bin of=/dev/block/mmcblk0p4
so 1 = bootloader
2= tz
3= param
en11gma said:
i did a search there for sph-l710 (my model and nothing came up)
i dont think that thread was for this phone so i guess the question remains.
is the partition tables in the (1st page) not just the first post correct for SPH-L710?
Click to expand...
Click to collapse
well maybe you can use the commands to find your table?
in adb type:
mount
Sorry for bumping this thread but nothing is working for me. I've tried the EFS pro backup tool and only get "connecting to device" for hours. So I saw this thread and thought manually doing it would work fine, and I get "permission denied".
I'm on a rooted, US variant, the SPH-L710. Even backing up the MSL has posed problems, so idk what is going on. Please help. I've been searching the site for 2 days and came up with tons of threads that just do not work.
Now if only we could resize these partitions!
Sent from my GT-I9300 using Tapatalk
AzzidReign said:
Sorry for bumping this thread but nothing is working for me. I've tried the EFS pro backup tool and only get "connecting to device" for hours. So I saw this thread and thought manually doing it would work fine, and I get "permission denied".
I'm on a rooted, US variant, the SPH-L710. Even backing up the MSL has posed problems, so idk what is going on. Please help. I've been searching the site for 2 days and came up with tons of threads that just do not work.
Click to expand...
Click to collapse
AS this is not your phones forum i suggest you ask in your phones forum as there are significant differences in the hardware .
The I9300 stickys have a network EFS IMEI thread if you want to read that but any I9300 firmware or fixes may brick a different phone .
OH1 partitions
Thought I should post the latest partition for OH1 firmware (Stagefright BUG FIX firmware)
[email protected]:/ # ls -al /dev/block/platform/msm_sdcc.1/by-name/
lrwxrwxrwx root root 2013-12-31 23:48 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2013-12-31 23:48 backup -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2013-12-31 23:48 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2013-12-31 23:48 cache -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2013-12-31 23:48 efs -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2013-12-31 23:48 fota -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2013-12-31 23:48 fsg -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2013-12-31 23:48 grow -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2013-12-31 23:48 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2013-12-31 23:48 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2013-12-31 23:48 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2013-12-31 23:48 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2013-12-31 23:48 param -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2013-12-31 23:48 persist -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2013-12-31 23:48 recovery -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2013-12-31 23:48 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2013-12-31 23:48 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2013-12-31 23:48 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2013-12-31 23:48 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2013-12-31 23:48 ssd -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2013-12-31 23:48 system -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2013-12-31 23:48 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2013-12-31 23:48 userdata -> /dev/block/mmcblk0p15
Droid Turbo Think Tank
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The main purpose of this thread is to discuss possible ideas for development and exploitation of the Motorola Droid Turbo. Topics can range from ideas on how to accomplish certain mods as we are trying to bake them into images to ways to flash different files to unlocking the BL. I am by no means an expert and I have some ideas I'd like to share with others on various topics. There is alot of hostility on this board, lets build some community!
__________________________________________________________________________________________________________
I do not however have total knowledge so I lack some skills to know if what I am saying is even possible. I am simply an android enthusiast, technologically inclined individual, and engineering student.
I will start us off: Since we have root permissions would it be possible to just dd a replacement recovery to the recovery partition, or even a modified bootloader. Or is that something R/W would prohibit/ not keep after a reboot? Would we be able to nandroid and restore/ install if we even could get a replacement recovery without the unlocked B/L?
Recovery Image DD:
Code:
dd if=/sdcard/recoveryfile.img of=/dev/block/mmcblk0p36
Here is a list of the partitions along with their name
Code:
[email protected]:/dev/block/platform/msm_sdcc.1 $ ls -al /dev/block/platform/msm_sdcc
.1/by-name
/platform/msm_sdcc.1/by-name <
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="Blue"]aboot[/COLOR] -> /dev/block/mmcbl
k0p6
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]abootBackup[/COLOR] -> /dev/block
/mmcblk0p13
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]boot [/COLOR]-> /dev/block/mmcblk
0p35
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]cache[/COLOR] -> /dev/block/mmcbl
k0p38
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]cid[/COLOR] -> /dev/block/mmcblk0
p25
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]clogo[/COLOR] -> /dev/block/mmcbl
k0p28
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]ddr[/COLOR] -> /dev/block/mmcblk0
p5
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]factorytune1 [/COLOR]-> /dev/bloc
k/mmcblk0p10
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]factorytune2 [/COLOR]-> /dev/bloc
k/mmcblk0p37
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]kpan [/COLOR]-> /dev/block/mmcblk
0p34
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]logo [/COLOR]-> /dev/block/mmcblk
0p27
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]logs [/COLOR]-> /dev/block/mmcblk
0p20
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]mdm1dhob [/COLOR]-> /dev/block/mm
cblk0p23
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]mdm1hob [/COLOR]-> /dev/block/mmc
blk0p22
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]mdm1m9kefs1 [/COLOR]-> /dev/block
/mmcblk0p17
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]mdm1m9kefs2 [/COLOR]-> /dev/block
/mmcblk0p18
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]mdm1m9kefs3 [/COLOR]-> /dev/block
/mmcblk0p31
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]mdm1m9kefsc [/COLOR]-> /dev/block
/mmcblk0p32
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]misc [/COLOR]-> /dev/block/mmcblk
0p29
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]modem [/COLOR]-> /dev/block/mmcbl
k0p1
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]padA [/COLOR]-> /dev/block/mmcblk
0p11
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]padB [/COLOR]-> /dev/block/mmcblk
0p19
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]padC [/COLOR]-> /dev/block/mmcblk
0p30
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]pds [/COLOR]-> /dev/block/mmcblk0
p26
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]persist [/COLOR]-> /dev/block/mmc
blk0p21
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]recovery [/COLOR]-> /dev/block/mm
cblk0p36
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]rpm [/COLOR]-> /dev/block/mmcblk0
p7
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]rpmBackup [/COLOR]-> /dev/block/m
mcblk0p14
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]sbl1 [/COLOR]-> /dev/block/mmcblk
0p2
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]sbl1bak [/COLOR]-> /dev/block/mmc
blk0p12
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]sdi [/COLOR]-> /dev/block/mmcblk0
p3
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]sec [/COLOR]-> /dev/block/mmcblk0
p4
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]sp [/COLOR]-> /dev/block/mmcblk0p
24
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]ssd [/COLOR]-> /dev/block/mmcblk0
p33
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]system [/COLOR]-> /dev/block/mmcb
lk0p39
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]tz [/COLOR]-> /dev/block/mmcblk0p
9
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]tzBackup [/COLOR]-> /dev/block/mm
cblk0p16
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]userdata [/COLOR]-> /dev/block/mm
cblk0p40
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]utags [/COLOR]-> /dev/block/mmcbl
k0p8
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]utagsBackup [/COLOR]-> /dev/block
/mmcblk0p15
[email protected]:/dev/block/platform/msm_sdcc.1 $
If a more knowledgeable user would comment on this I'd appreciate it!
Which are the imei blocks?
cascade128 said:
Which are the imei blocks?
Click to expand...
Click to collapse
The IMEI is in the utags partition.
Code:
su
dd if="/dev/block/platform/msm_sdcc.1/by-name/utags" of="/sdcard/utags.bin"
Then pull utags.bin off of the internal storage of the device and open it in a hex editor (you need root to copy it to the internal storage)
What about 2nd init? This seems to have been a good solution in the past. I believe this is how Safestrap worked. It used an exploit in a log file to launch 2nd init from the data partition. In this case the system would boot from data and we would presumably have full access. I don't know if the exploit would still work in 4.4.4. This would be the key, but the exploit could be added to a system image and flashed. Safestrap would be awesome, but even a simple 2nd init could work to start. I am just throwing this out there for discussion. This is way outside of my means, but someone else might be able to help.
Harry44 said:
Would we be able to nandroid and restore/ install if we even could get a replacement recovery without the unlocked B/L?
Click to expand...
Click to collapse
To answer your first question, no, dd'ing a new recovery in place wouldn't work. I think wp(write protect) would stop it and even if it doesn't, booting it would fail, as it verifies the signature of the partition it's booting from unless the device is unlocked or an engineering model. For your second question, yes, if you could miraculously perform the act of getting a recovery in there and it boots (emphasis on "and it boots") you *should* be able to backup/restore/install stuff.
r3pwn said:
The IMEI is in the utags partition.
Code:
su
dd if="/dev/block/platform/msm_sdcc.1/by-name/utags" of="/sdcard/utags.bin"
Then pull utags.bin off of the internal storage of the device and open it in a hex editor (you need root to copy it to the internal storage)
Click to expand...
Click to collapse
Thx.
What is utagsBackup.bin? Do i need to change it?
cascade128 said:
Thx.
What is utagsBackup.bin? Do i need to change it?
Click to expand...
Click to collapse
Not sure what your local laws are but check before modifying IMEI.
cascade128 said:
Thx.
What is utagsBackup.bin? Do i need to change it?
Click to expand...
Click to collapse
Erh, I wasn't aware that you wanted to CHANGE your IMEI. I am afraid that I am unable to assist you with that (well, I'm able, I just don't want to because it's illegal).
Harry44 said:
Not sure what your local laws are but check before modifying IMEI.
Click to expand...
Click to collapse
r3pwn said:
Erh, I wasn't aware that you wanted to CHANGE your IMEI. I am afraid that I am unable to assist you with that (well, I'm able, I just don't want to because it's illegal).
Click to expand...
Click to collapse
In our country, you have to register to use the mobile phone brought a passport outside the country due to a ridiculous law. Also you invest 50$ before the bank for this purpose.
That's not all. The passport to be registered abroad in the last 2 months need to be logged in our country. In addition, within the last 2 years it is supposed to be saved to another mobile phone passport...
This transaction is being processed on the IMEI number...
We were so old that we bring to mobile phones from abroad, used condition but in our country we are writing the IMEI number of the phone is registered. However we have to...
Any way we could boot back up an IRC for people who want to throw ideas off eachother a bit quicker, or just a general DT Discuss?
Sareniah said:
Any way we could boot back up an IRC for people who want to throw ideas off eachother a bit quicker, or just a general DT Discuss?
Click to expand...
Click to collapse
This would actually be a good idea. Anyone willing to set it up?
If someone have moto maxx and check files whats changes in unlocking bootloader and try change in droid turbo too.
I have some ideas for bootloader unlock. They're probably really stupid, but bear with me. Like OP, I'm no developer, just an Android enthusiast with basic knowledge of the inner workings.
So the Moto Maxx US (XT1250) and Droid Turbo (XT1254) are essentially the same device, right? They essentially have the same specs, same hardware, software, and they both work on CDMA carriers like Verizon. The only difference is that the Maxx's bootloader is not locked by Verizon. So here are a few ideas pertaining to that.
***NOTE: It has to be the XT1250 variant
Idea A:
1. XT1250 Maxx user uses "fastboot oem get_unlock_data" or goes through WinDroid to get the unlock key
2. Key is given to a Turbo user
3. Turbo user uses "fastboot oem unlock <maxx_key>
4. Profit
Idea B (risky):
1. Turbo user downloads XT1250 system .img
2. User flashes to Turbo using RSDlite or MOFO (not sure which would work better, if at all)
3. Use WinDroid to unlock BL, root, and install a custom recovery
4. Profit
Yes, yes, I know...they are probably bad ideas, but we must consider every possibility!
jake7405 said:
I have some ideas for bootloader unlock. They're probably really stupid, but bear with me. Like OP, I'm no developer, just an Android enthusiast with basic knowledge of the inner workings.
Click to expand...
Click to collapse
These wouldn't work. Good start on ideas, though.
Thanks!
Just a quick n00b question, why wouldnt flashing the xt1250 img work?
Sent from my XT1254
Thank you.
jake7405 said:
Thanks!
Just a quick n00b question, why wouldnt flashing the xt1250 img work?
Sent from my XT1254
Click to expand...
Click to collapse
The phone data itself (IMEI and stuff) is still the same, so the unlock data generated would still be the same, meaning Motorola would still reject it.
Was shown this as potential ways to head towards bl unlock. Leaving it here for greater minds to dissect.
http://manualwire.com/view/19580/
JakeDHS07 said:
Was shown this as potential ways to head towards bl unlock. Leaving it here for greater minds to dissect.
http://manualwire.com/view/19580/
Click to expand...
Click to collapse
Unless I'm mistaken, that would only help with a bootloader bypass. Trust me. Unlocks are better than bypasses.
r3pwn said:
The phone data itself (IMEI and stuff) is still the same, so the unlock data generated would still be the same, meaning Motorola would still reject it.
Click to expand...
Click to collapse
Any way to modify or change it? Also, would this probably end up hard bricking me if I tried?
So here we are
Its officialy confirmed
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Cant wait to create a rom / kernel for This Beast
Who has received it
Itsnot reciveable , just spam them tell them that htc dev didnt publish it yet
Just copy and paste this to them ,, they should know their ota system sucks
We need a download link for HTC desire 820s Dual Sim Software Version 1.14.709.1 Sense 7 , Lolipop 5.0.2 Build as itsn't recievable as OTA " we didn't and will never recive it as kk users " it only come out of the box by luck.
Please publish it . we are stuck at kitkat
There's no way they can send lollipop and Sense 7 OTA. That's about 4 GBs!!!!
---------- Post added at 04:07 PM ---------- Previous post was at 04:04 PM ----------
I've been spamming them the entire week. They are too reluctant to give the source code or OTA
I think going to get refund and reppace this device
Mohamed Yaser said:
I think going to get refund and reppace this device
Click to expand...
Click to collapse
Let me be patient until December
What about battery ,charging 6% / Hour ??
Too slow?
Wait a minute. Isn't a50mldtul desire 820s?
where u got that from
http://www.droidviews.com/list-of-android-device-codenames/
Yeah it is
i think also we are getting a recovery soon
[email protected]_a50ml_dtul:/ $ su
/platform/mtk-msdc.0"This is our chip"/by-name <
lrwxrwxrwx root root 2015-07-08 00:46 boot -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-07-08 00:46 cache -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2015-07-08 00:46 cota -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-07-08 00:46 dkb -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2015-07-08 00:46 expdb -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-07-08 00:46 flashinfo -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2015-07-08 00:46 kb -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-07-08 00:46 lk -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-07-08 00:46 logo -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2015-07-08 00:46 metadata -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2015-07-08 00:46 nvram -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-07-08 00:46 para -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-07-08 00:46 proinfo -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-07-08 00:46 protect1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-07-08 00:46 protect2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-07-08 00:46 recovery -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-07-08 00:46 seccfg -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-07-08 00:46 secro -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-07-08 00:46 system -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-07-08 00:46 tee1 -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-07-08 00:46 tee2 -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-07-08 00:46 userdata -> /dev/block/mmcblk0p21
[email protected]_a50ml_dtul:/ #
http://forum.xda-developers.com/desire-820/orig-development/desire-820-models-msm-chipset-twrp-2-8-t3147260/page4
http://forum.xda-developers.com/des...20-models-msm-chipset-twrp-2-8-t3147260/page4
The kernel source code for a50mldtul is at htcdev
There's this one I flashed. Seems to be working fine. It can backup. Haven't tried restoring or installing zip though.
CWM
Isn't this the greatest breakthrough for our phone
Oh , May be i will start work on a rom
PS ,, Give me a link to our source code and How u did unlock the bl
I'm not sure how I unlocked it. I remember trying to unlock it at htcdev.com and using kingo htc bootloader unlock but I wasn't successfull. I don't know maybe it's still locked.
At htcdev there are kernel source codes with a50mldtul name under Desire 820 dual sim. But again I'm not if sure they are for Desire 820s.
You can get the CWM I flashed here
http://www.4shared.com/rar/SM6wcBzyce/CWM_820s.html
It's fully working for me
Gibz97 said:
I'm not sure how I unlocked it. I remember trying to unlock it at htcdev.com and using kingo htc bootloader unlock but I wasn't successfull. I don't know maybe it's still locked.
At htcdev there are kernel source codes with a50mldtul name under Desire 820 dual sim. But again I'm not if sure they are for Desire 820s.
You can get the CWM I flashed here
http://www.4shared.com/rar/SM6wcBzyce/CWM_820s.html
It's fully working for me
Click to expand...
Click to collapse
who made this cwm
I found it here
http://forum.xda-developers.com/and...6732-64bit-t2998980/post61761125#post61761125
Pretty old thread
---------- Post added at 12:19 AM ---------- Previous post was at 12:18 AM ----------
Mohamed Yaser said:
who made this cwm
Click to expand...
Click to collapse
Have you tried it?
Gibz97 said:
I found it here
http://forum.xda-developers.com/and...6732-64bit-t2998980/post61761125#post61761125
Pretty old thread
---------- Post added at 12:19 AM ---------- Previous post was at 12:18 AM ----------
Have you tried it?
Click to expand...
Click to collapse
i didn't find the kernel source ??
no not yet
i remember a great developer ( odia ) who downgrade the I9300 xella
has someone try this way ?
http://forum.xda-developers.com/gal.../util-sboot-checker-simple-downgrade-t2081748
this method was used also for N7100
http://forum.xda-developers.com/showthread.php?t=2089353
I HAVE NOT TRY THIS WITH N910C I JUST ASK IF SOMEONE TRY THIS !!!
kondronaute said:
i remember a great developer ( odia ) who downgrade the I9300 xella
has someone try this way ?
http://forum.xda-developers.com/gal.../util-sboot-checker-simple-downgrade-t2081748
this method was used also for N7100
http://forum.xda-developers.com/showthread.php?t=2089353
I HAVE NOT TRY THIS WITH N910C I JUST ASK IF SOMEONE TRY THIS !!!
Click to expand...
Click to collapse
Very interesting....
Only thing to verify if partitions are the same. They should be. Since this is 2 years old wonder if Samsung has caught on.
dicksteele said:
Very interesting....
Only thing to verify if partitions are the same. They should be. Since this is 2 years old wonder if Samsung has caught on.
Click to expand...
Click to collapse
first look there are same, I am happy with the new rom and I haven't time to test .....
if someone want to test he must take last abd version .... (you can download the zip with batch...)
kondronaute said:
first look there are same, I am happy with the new rom and I haven't time to test .....
if someone want to test he must take last abd version .... (you can download the zip with batch...)
Click to expand...
Click to collapse
I just got my phone last month and did the OJ5 update not realizing it was locked. I was on ATT Note 2 for years and years and never got to try a Dr Ketan's ROM. Pissed with the new locked bootloader.
So I'm ODIN flashing to full COJ5.
Will back up efs, param, pit and whatever else I can think of and give it a shot.
Obviously it seems to simple to work.
I did a compare yesterday on the pre-locked 5.1.1 bootloaders and the locked one.
I saw a few things in there that were different and I modified them in the locked one.
My edited one flashed so I was surprised. But I tried to downgrade and it didn't work..... So what I changed didn't make a difference. Yet ! :laugh:
dicksteele said:
I just got my phone last month and did the OJ5 update not realizing it was locked. I was on ATT Note 2 for years and years and never got to try a Dr Ketan's ROM. Pissed with the new locked bootloader.
So I'm ODIN flashing to full COJ5.
Will back up efs, param, pit and whatever else I can think of and give it a shot.
Obviously it seems to simple to work.
I did a compare yesterday on the pre-locked 5.1.1 bootloaders and the locked one.
I saw a few things in there that were different and I modified them in the locked one.
My edited one flashed so I was surprised. But I tried to downgrade and it didn't work..... So what I changed didn't make a difference. Yet ! :laugh:
Click to expand...
Click to collapse
ok good luck
i think this is the better option in the past i do it for 3 or 4 I9300 without any pbm hope it's same again
kondronaute said:
ok good luck
i think this is the better option in the past i do it for 3 or 4 I9300 without any pbm hope it's same again
Click to expand...
Click to collapse
Double checking things Back on full stock
[email protected]:/dev/block/platform/15540000.dwmmc0/by-name $ ls -la
ls -la
lrwxrwxrwx root root 2015-11-28 11:15 BOOT -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-11-28 11:15 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-11-28 11:15 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-11-28 11:15 CACHE -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-11-28 11:15 CARRIER -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-11-28 11:15 CDMA-RADIO -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-11-28 11:15 DNT -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-11-28 11:15 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-11-28 11:15 HIDDEN -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2015-11-28 11:15 OTA -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-11-28 11:15 PARAM -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-11-28 11:15 PERSDATA -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-11-28 11:15 RADIO -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2015-11-28 11:15 RECOVERY -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-11-28 11:15 RESERVED2 -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-11-28 11:15 SYSTEM -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2015-11-28 11:15 TOMBSTONES -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-11-28 11:15 USERDATA -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2015-11-28 11:15 m9kefs1 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-11-28 11:15 m9kefs2 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-11-28 11:15 m9kefs3 -> /dev/block/mmcblk0p6
# dd if=/sdcard/sboot.bin of=/dev/block/mmcblk0p1 BOTA0 Restore Bootloader (I hope!)
# dd if=/sdcard/tz.img of=/dev/block/mmcblk0p2 BOTA1 Restore tz.img
# dd if=/sdcard/param.bin of=/dev/block/mmcblk0p4 PARAM Restore PARAM
# dd if=/dev/block/mmcblk0 of=/sdcard/N910C.pit bs=8 count=580 skip=2176 Backup PIT
PIT -> /dev/block/mmcblk0
BOOT -> /dev/block/mmcblk0p9 Kernel
RECOVERY-> /dev/block/mmcblk0p10 TWRP
RADIO -> /dev/block/mmcblk0p13 Modem
Starting partition backups and continuing internal debate of how confident I am I won't f**k something up
dicksteele said:
Double checking things Back on full stock
[email protected]:/dev/block/platform/15540000.dwmmc0/by-name $ ls -la
ls -la
lrwxrwxrwx root root 2015-11-28 11:15 BOOT -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-11-28 11:15 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-11-28 11:15 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-11-28 11:15 CACHE -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-11-28 11:15 CARRIER -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-11-28 11:15 CDMA-RADIO -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-11-28 11:15 DNT -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-11-28 11:15 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-11-28 11:15 HIDDEN -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2015-11-28 11:15 OTA -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-11-28 11:15 PARAM -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-11-28 11:15 PERSDATA -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-11-28 11:15 RADIO -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2015-11-28 11:15 RECOVERY -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-11-28 11:15 RESERVED2 -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-11-28 11:15 SYSTEM -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2015-11-28 11:15 TOMBSTONES -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-11-28 11:15 USERDATA -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2015-11-28 11:15 m9kefs1 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-11-28 11:15 m9kefs2 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-11-28 11:15 m9kefs3 -> /dev/block/mmcblk0p6
# dd if=/sdcard/sboot.bin of=/dev/block/mmcblk0p1 BOTA0 Restore Bootloader (I hope!)
# dd if=/sdcard/tz.img of=/dev/block/mmcblk0p2 BOTA1 Restore tz.img
# dd if=/sdcard/param.bin of=/dev/block/mmcblk0p4 PARAM Restore PARAM
# dd if=/dev/block/mmcblk0 of=/sdcard/N910C.pit bs=8 count=580 skip=2176 Backup PIT
PIT -> /dev/block/mmcblk0
BOOT -> /dev/block/mmcblk0p9 Kernel
RECOVERY-> /dev/block/mmcblk0p10 TWRP
RADIO -> /dev/block/mmcblk0p13 Modem
Starting partition backups and continuing internal debate of how confident I am I won't f**k something up
Click to expand...
Click to collapse
i think you can try without tz.img and param.bin
look at this rar (i put the last adb)
(when I do it with I9300 the phone was on ....)
kondronaute said:
i think you can try without tz.img and param.bin
look at this rar (i put the last adb)
(when I do it with I9300 the phone was on ....)
Click to expand...
Click to collapse
No dice with and without param.bin. Good news still boots.
Still shows bootloader of COJ5
Maybe it does need tz.img
dicksteele said:
No dice with and without param.bin. Good news still boots.
Still shows bootloader of COJ5
Maybe it does need tz.img
Click to expand...
Click to collapse
yes god news i boot but seem not do the job....
do you try w ith only this script
@files1\adb push sboot.bin /sdcard/sboot.bin
@files1\adb shell su -c "dd if=/sdcard/sboot.bin of=/dev/block/mmcblk0p1"
@files1\adb shell rm /sdcard/sboot.bin
@files1\adb reboot fota_bl
kondronaute said:
yes god news i boot but seem not do the job....
do you try w ith only this script
@files1\adb push sboot.bin /sdcard/sboot.bin
@files1\adb shell su -c "dd if=/sdcard/sboot.bin of=/dev/block/mmcblk0p1"
@files1\adb shell rm /sdcard/sboot.bin
@files1\adb reboot fota_bl
Click to expand...
Click to collapse
Yeah, I did that
Then I bumped it up a notch
@files1\adb shell su -c "dd if=/sdcard/sboot.bin of=/dev/block/platform/15540000.dwmmc0/by-name/BOTA0"
@files1\adb shell getprop ro.boot.bootloader
@pause
After the pause it comes back with the COJ5.
Rebooting, running same command, COJ5.
Assuming this will create a tz.img.... I haven't seen anything referring to it for 5.1.1
dd if=/dev/block/mmcblk0p2 of=/sdcard/cache.rfs bs=4096
dd if=/dev/block/platform/15540000.dwmmc0/by-name/BOTA1 of=/sdcard/tz.img bs=4096
Also just downloaded 11/27 firmware for Kenya going to try that. I've been using the sboot.bin from here
http://forum.xda-developers.com/note-4/development/rom-note-4-mod-t3244665
dicksteele said:
Yeah, I did that
Then I bumped it up a notch
@files1\adb shell su -c "dd if=/sdcard/sboot.bin of=/dev/block/platform/15540000.dwmmc0/by-name/BOTA0"
@files1\adb shell getprop ro.boot.bootloader
@pause
After the pause it comes back with the COJ5.
Rebooting, running same command, COJ5.
Assuming this will create a tz.img.... I haven't seen anything referring to it for 5.1.1
dd if=/dev/block/mmcblk0p2 of=/sdcard/cache.rfs bs=4096
dd if=/dev/block/platform/15540000.dwmmc0/by-name/BOTA1 of=/sdcard/tz.img bs=4096
Also just downloaded 11/27 firmware for Kenya going to try that. I've been using the sboot.bin from here
http://forum.xda-developers.com/note-4/development/rom-note-4-mod-t3244665
Click to expand...
Click to collapse
after the pause can you reboot directly in download mode and flash again the new bootloader with odin
try this bootloader
N910CXXU1COH4 Bootloader (5.1.1)(ONLY for N910C users)
http://forum.xda-developers.com/showpost.php?p=58867937&postcount=3
I am very pessimistic with this ...
kondronaute said:
after the pause can you reboot directly in download mode and flash again the new bootloader with odin
try this bootloader
N910CXXU1COH4 Bootloader (5.1.1)(ONLY for N910C users)
http://forum.xda-developers.com/showpost.php?p=58867937&postcount=3
I am very pessimistic with this ...
Click to expand...
Click to collapse
You should be .... No dice.
But again. I was able to pull battery go back into download mode and ODIN flash the COJ5 I had
Kenya firmware from 11/27 same thing...
dicksteele said:
You should be .... No dice.
But again. I was able to pull battery go back into download mode and ODIN flash the COJ5 I had
Kenya firmware from 11/27 same thing...
Click to expand...
Click to collapse
when you pull the battery after flashed a pre locked bootloader can you in the go reflash the same pre locked bl with odin ( it flash or it say error .....)
kondronaute said:
when you pull the battery after flashed a pre locked bootloader can you in the go reflash the same pre locked bl with odin ( it flash or it say error .....)
Click to expand...
Click to collapse
Same error NAND write fail
dicksteele said:
Same error NAND write fail
Click to expand...
Click to collapse
it was a pleasure to collaborate with u
i hope a developer look at this pbm; really i am happy with 5.1.1 coz i can use xposed and it's better than 5.0.1 but I love to have the choice, I love the idea to be free and I don't understand why samsung and other lock our phones; personally I have no care for guaranty.... i want just be free to play with my phone !
kondronaute said:
it was a pleasure to collaborate with u
i hope a developer look at this pbm; really i am happy with 5.1.1 coz i can use xposed and it's better than 5.0.1 but I love to have the choice, I love the idea to be free and I don't understand why samsung and other lock our phones; personally I have no care for guaranty.... i want just be free to play with my phone !
Click to expand...
Click to collapse
Agree.
I'm really having no issues with 5.1.1.
I'm with you, it was more of a challenge to see if it could be done. CM 13 seems to be moving along so that may take the desire to flash back to lessen. Take care. I'll be around
dicksteele said:
Agree.
I'm really having no issues with 5.1.1.
I'm with you, it was more of a challenge to see if it could be done. CM 13 seems to be moving along so that may take the desire to flash back to lessen. Take care. I'll be around
Click to expand...
Click to collapse
please guys for those who are on COH4 can you install partition backup (wanam) from store and give us the backup of
BOTA0
BOTA1
PARAM
please in raw partion image (img)
thank u by advance
please friends it will take you just a little of your time and if work it will help all
btw if you are in kitkat also you can give us
Step :
Install adb driver
Root devices
Open adb type :
adb shell
su
ls -al /dev/block/platform/mtk-msdc.0/by-name (see from update-script file stockrom)
lrwxrwxrwx root root 2015-12-14 15:21 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-12-14 15:21 cache -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2015-12-14 15:21 custom -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-12-14 15:21 expdb -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-12-14 15:21 flashinfo -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2015-12-14 15:21 frp -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2015-12-14 15:21 keystore -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-12-14 15:21 lk -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-12-14 15:21 logo -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-12-14 15:21 metadata -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2015-12-14 15:21 nvdata -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-12-14 15:21 nvram -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-12-14 15:21 oemkeystore -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-12-14 15:21 para -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2015-12-14 15:21 proinfo -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-12-14 15:21 protect1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-12-14 15:21 protect2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-12-14 15:21 recovery -> /dev/block/mmcblk0p8 <<=========<<<
lrwxrwxrwx root root 2015-12-14 15:21 seccfg -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-12-14 15:21 secro -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2015-12-14 15:21 system -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2015-12-14 15:21 tee1 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-12-14 15:21 tee2 -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-12-14 15:21 userdata -> /dev/block/mmcblk0p23
dd if=/dev/block/mmcblk0p8 of=/sdcard/recovery.img
(reference of @broadways on post http://forum.xda-developers.com/showpost.php?p=64312955&postcount=125 )
Take backup recovery.img from sdcard and save in folder ImgExtractor_32-64Bit
Open folder and click menu - Run as administrator
Select 3 - unpack process
Select 4 - repack process
Rename recovery-new.img to recovery.img
Flash recovery.img with Flashify-premium-1.8.3.apk / fastboot or etc,
Open Rebootmanager.apk - reboot to recovery
Finished
___
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
___
___
___
Files :
ImgExtractor_32-64Bit source from boycracked
Flashify-premium-1.8.3.apk
recovery-stock-M2-flyme-4.5.4iglobal
recovery-stock-M2-flyme-5.1.6.0global
recovery-stock-M2-flyme-5.1.8.0global
recovery-stock-M2-flyme-5.1.9.0global
recovery-stock-M2-flyme-5.1.10.0global
recovery-stock-M2-flyme-5.1.11.0global
recovery-stock-M2-flyme-5.1.12.0global
and the possibility of this method can be used for other android,
Great..it very useful