Related
Not able to root Defy Plus..
Build number: 4.5.1-134_dfp-231
tried all versions of super one click..
but no luck..
Hi.
Use this
http://forum.xda-developers.com/showthread.php?t=1595013
Thank you. . It worked...
Sent from my MB526 using XDA
Pls help me!!!
Hi,
I'm trying to root my Motorola Defy plus.
Android:2.3.6
System Version:45.0.2310.MB526.AsiaRetail.en.03
Baseband version:EPU93_U_00.60.03
Kernal version: 2.6.32.9
BUILD NO: 4.5.1-134_DFP-231
It seems I'm not having write access for System folder...
Can any one help me to get rid of it...
My log is below.....
---------------------------------------------------------------
Easy rooting toolkit (v4.0)
created by DooMLoRD
using exploit zergRush (Revolutionary Team)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using latest zergRush exploit (21 Nov)
(2) install Busybox (1.18.4)
(3) install SU files (binary: 3.0.3 and apk: 3.0.6)
(4) some checks for free space, tmp directory
(will remove Google Maps if required)
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
* daemon not running. starting it now *
* daemon started successfully *
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
--- pushing zergRush
256 KB/s (23060 bytes in 0.087s)
--- correcting permissions
--- executing zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00000118
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
--- pushing busybox
368 KB/s (1075144 bytes in 2.845s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
48 KB/s (439 bytes in 0.008s)
df: /mnt/secure/asec: Permission denied
--- Free space on /system : 94% bytes
test: 94%: bad number
--- NOT enough free space on /system!!!
--- making free space by removing Google Maps
rm: can't remove '/system/app/Maps.apk': Read-only file system
--- copying busybox to /system/xbin/
/system/xbin/busybox: cannot open for write: Read-only file system
--- correcting ownership
Unable to chmod /system/xbin/busybox: No such file or directory
--- correcting permissions
Unable to chmod /system/xbin/busybox: No such file or directory
--- installing busybox
/system/xbin/busybox: not found
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
--- rebooting
ALL DONE!!!
Press any key to continue . . .
Thanks in advance..
Try this method as only this method works on BL7.
http://forum.xda-developers.com/showthread.php?t=1542956
Bharath256 said:
Hi,
I'm trying to root my Motorola Defy plus.
Android:2.3.6
System Version:45.0.2310.MB526.AsiaRetail.en.03
Baseband version:EPU93_U_00.60.03
Kernal version: 2.6.32.9
BUILD NO: 4.5.1-134_DFP-231
It seems I'm not having write access for System folder...
Can any one help me to get rid of it...
Thanks in advance..
Click to expand...
Click to collapse
you seriously need to read the threads prior to posting.. Its been answered like a 100 times..
MY Defy+ got rooted
Thanks a lot.....my defy+ got rooted....:victory::good:
THIS ONLY WORKS ON ROOTED ROMS/DEVICES
As a owner of the original Galaxy s i have encounter the problem like no radio signal etc, after flashing certain roms,this was because the efs partition/folder somehow got wiped.
This could be fixed by flashing certain original roms, or restoring the EFS folder from a backup, of course allot of people never did such backup
Soo, after you flash a rooted rom into your device this is one of the first thing you must do, believe me soon or later you gonna need it!
Here is how to:
1-Put your device into USB debugging mode
2- download busybox from the market and installed it, launch busybox in the device and press install.
3- download EFS-PRO from here, don't forget to thank the developer
4- launch the application in you pc
5- in " Data Backup Method select" "create compressed tar " or "create partition image" (Personally i used the tar method)
Tick "Save to device storage" and "Save to pc storage,then click "Backup EFS" button.
now you shoud have a Backup of the efs in you device storage card and one in the EFS pro folder in your pc, save it to a safe place and never share it!
{
"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"
}
Many thanks to the developer of EFS PRO tools.
Thanks a lot for the tip mate
One more way to back the efs is to manually mount the filesystems and then copy the /efs folder and paste it somewhere safe
I have not personally tried it Can someone confirm whether this works ? I see no reason that it shouldn't but better be safe than sorry
P.S. This also needs root
Hi, Faria! I messed up the EFS and now I have a problem with the phone, wrote in other forum threads. You know how much, I could not make the file EFS for Odin3 that would fix and restore it.
Great post, and very useful advice. Other partitions can be backup up as well in the following way:
Code:
cd /storage/extSdCard
mkdir backup
cd backup
dd if=/dev/block/mmcblk0p1 of=mmcblk0p1
dd if=/dev/block/mmcblk0boot0 of=mmcblk0boot0
dd if=/dev/block/mmcblk0boot1 of=mmcblk0boot0
dd if=/dev/block/mmcblk0p2 of=mmcblk0p2
dd if=/dev/block/mmcblk0p3 of=mmcblk0p3
dd if=/dev/block/mmcblk0p4 of=mmcblk0p4
dd if=/dev/block/mmcblk0p5 of=mmcblk0p5
dd if=/dev/block/mmcblk0p6 of=mmcblk0p6
dd if=/dev/block/mmcblk0p7 of=mmcblk0p7
dd if=/dev/block/mmcblk0p8 of=mmcblk0p8
dd if=/dev/block/mmcblk0p9 of=mmcblk0p9
dd if=/dev/block/mmcblk0p10 of=mmcblk0p10
dd if=/dev/block/mmcblk0p11 of=mmcblk0p11
dd if=/dev/block/mmcblk0p12 of=mmcblk0p12
dd if=/dev/block/mmcblk0p13 of=mmcblk0p13
dd if=/dev/block/mmcblk0p14 of=mmcblk0p14
dd if=/dev/block/mmcblk0p15 of=mmcblk0p15
dd if=/dev/block/mmcblk0p16 of=mmcblk0p16
dd if=/dev/block/mmcblk0p17 of=mmcblk0p17
dd if=/dev/block/mmcblk0p18 of=mmcblk0p18
dd if=/dev/block/mmcblk0p19 of=mmcblk0p19
sync
This will backup everything excluding the boot, recovery, system, cache, hidden, and data partitions. For the record, here is the PIT partition table:
Code:
--- Entry #0 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 1
Partition Flags: 2 (R/W)
Unknown 1: 1
Partition Block Size: 0
Partition Block Count: 256
Unknown 2: 0
Unknown 3: 0
Partition Name: MBR,GPT
Filename:
--- Entry #1 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 2
Partition Flags: 2 (R/W)
Unknown 1: 1
Partition Block Size: 256
Partition Block Count: 768
Unknown 2: 0
Unknown 3: 0
Partition Name: MasterTOC
Filename: STE_boot.bin
--- Entry #2 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 70
Partition Flags: 5 (R)
Unknown 1: 1
Partition Block Size: 1024
Partition Block Count: 2048
Unknown 2: 0
Unknown 3: 0
Partition Name: PIT
Filename: goldenxx.pit
--- Entry #3 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 71
Partition Flags: 5 (R)
Unknown 1: 1
Partition Block Size: 6144
Partition Block Count: 2048
Unknown 2: 0
Unknown 3: 0
Partition Name: MD5HDR
Filename: md5.img
--- Entry #4 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 3
Partition Flags: 2 (R/W)
Unknown 1: 1
Partition Block Size: 8192
Partition Block Count: 1024
Unknown 2: 0
Unknown 3: 0
Partition Name: STEboot1
Filename: STE_boot1.img
--- Entry #5 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 4
Partition Flags: 2 (R/W)
Unknown 1: 1
Partition Block Size: 9216
Partition Block Count: 1024
Unknown 2: 0
Unknown 3: 0
Partition Name: STEboot2
Filename: STE_boot2.img
--- Entry #6 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 5
Partition Flags: 2 (R/W)
Unknown 1: 1
Partition Block Size: 10240
Partition Block Count: 1024
Unknown 2: 0
Unknown 3: 0
Partition Name: Dnt
Filename: dnt.ssw
--- Entry #7 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 6
Partition Flags: 2 (R/W)
Unknown 1: 1
Partition Block Size: 11264
Partition Block Count: 1024
Unknown 2: 0
Unknown 3: 0
Partition Name: reserved
Filename:
--- Entry #8 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 7
Partition Flags: 5 (R)
Unknown 1: 1
Partition Block Size: 16384
Partition Block Count: 2048
Unknown 2: 0
Unknown 3: 0
Partition Name: CSPSAFS
Filename: cspsa.img
--- Entry #9 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 8
Partition Flags: 5 (R)
Unknown 1: 1
Partition Block Size: 18432
Partition Block Count: 2048
Unknown 2: 0
Unknown 3: 0
Partition Name: CSPSAFS2
Filename: cspsa2.img
--- Entry #10 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 9
Partition Flags: 5 (R)
Unknown 1: 5
Partition Block Size: 20480
Partition Block Count: 32768
Unknown 2: 0
Unknown 3: 0
Partition Name: EFS
Filename: EFS.img
--- Entry #11 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 10
Partition Flags: 5 (R)
Unknown 1: 5
Partition Block Size: 53248
Partition Block Count: 32768
Unknown 2: 0
Unknown 3: 0
Partition Name: ModemFS
Filename: modemfs.img
--- Entry #12 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 11
Partition Flags: 5 (R)
Unknown 1: 5
Partition Block Size: 86016
Partition Block Count: 32768
Unknown 2: 0
Unknown 3: 0
Partition Name: ModemFS2
Filename: modemfs2.img
--- Entry #13 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 12
Partition Flags: 5 (R)
Unknown 1: 1
Partition Block Size: 118784
Partition Block Count: 102400
Unknown 2: 0
Unknown 3: 0
Partition Name: Fota
Filename: ssgtest.img
--- Entry #14 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 13
Partition Flags: 5 (R)
Unknown 1: 1
Partition Block Size: 380928
Partition Block Count: 128
Unknown 2: 0
Unknown 3: 0
Partition Name: IPL Modem
Filename: ipl.bin
--- Entry #15 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 14
Partition Flags: 5 (R)
Unknown 1: 1
Partition Block Size: 385024
Partition Block Count: 28672
Unknown 2: 0
Unknown 3: 0
Partition Name: Modem
Filename: modem.bin
--- Entry #16 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 15
Partition Flags: 2 (R/W)
Unknown 1: 1
Partition Block Size: 417792
Partition Block Count: 4096
Unknown 2: 0
Unknown 3: 0
Partition Name: Loke4
Filename: normal.bin
--- Entry #17 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 16
Partition Flags: 2 (R/W)
Unknown 1: 1
Partition Block Size: 421888
Partition Block Count: 4096
Unknown 2: 0
Unknown 3: 0
Partition Name: 2ndLoke4
Filename: normal2.bin
--- Entry #18 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 17
Partition Flags: 5 (R)
Unknown 1: 1
Partition Block Size: 425984
Partition Block Count: 32768
Unknown 2: 0
Unknown 3: 0
Partition Name: PARAM
Filename: param.lfs
--- Entry #19 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 18
Partition Flags: 5 (R)
Unknown 1: 1
Partition Block Size: 458752
Partition Block Count: 32768
Unknown 2: 0
Unknown 3: 0
Partition Name: Kernel
Filename: boot.img
--- Entry #20 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 19
Partition Flags: 5 (R)
Unknown 1: 1
Partition Block Size: 491520
Partition Block Count: 32768
Unknown 2: 0
Unknown 3: 0
Partition Name: Kernel2
Filename: recovery.img
--- Entry #21 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 20
Partition Flags: 5 (R)
Unknown 1: 5
Partition Block Size: 524288
Partition Block Count: 2457600
Unknown 2: 0
Unknown 3: 0
Partition Name: SYSTEM
Filename: system.img
--- Entry #22 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 21
Partition Flags: 5 (R)
Unknown 1: 5
Partition Block Size: 2981888
Partition Block Count: 1720320
Unknown 2: 0
Unknown 3: 0
Partition Name: CACHEFS
Filename: cache.img
--- Entry #23 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 22
Partition Flags: 5 (R)
Unknown 1: 5
Partition Block Size: 4702208
Partition Block Count: 655360
Unknown 2: 0
Unknown 3: 0
Partition Name: HIDDEN
Filename: hidden.img
--- Entry #24 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 23
Partition Flags: 5 (R)
Unknown 1: 5
Partition Block Size: 5357568
Partition Block Count: 9891840
Unknown 2: 0
Unknown 3: 0
Partition Name: DATAFS
Filename: userdata.img
PEV201078 said:
Hi, Faria! I messed up the EFS and now I have a problem with the phone, wrote in other forum threads. You know how much, I could not make the file EFS for Odin3 that would fix and restore it.
Click to expand...
Click to collapse
The tool itself will restore the efs, no need for odin.
But if you never back up the efs folder this tool is not gonna help you now.
Never can find my device... :S
MalekoUK said:
Never can find my device... :S
Click to expand...
Click to collapse
Connect it first then run the program. That helped me.
But I could never get it to work, finds device but no partitions appear. Also says Qualcomm device disabled.
I backed up my efs folder using root explorer but still wanted to do this...
MalekoUK said:
Never can find my device... :S
Click to expand...
Click to collapse
Usb debuging on?
You sure you got all the drivers installed on the pc?
Try another usb slot?
All drivers installed, tested with ADB works, dunno if that means anything.
Sent from my SIII Mini using Tapatalk
for me;
efs ok connect I8190.
ok info rom .
(no partion detect)
Do not use the latest version of EFS , you will not be able to backup anything , search for an older version 1.x.x , I do the same and successfully backup my efs on i8190 .
evilinside said:
Do not use the latest version of EFS , you will not be able to backup anything , search for an older version 1.x.x , I do the same and successfully backup my efs on i8190 .
Click to expand...
Click to collapse
Thanks very much. I couldn't get 2.x.x version working, got a 1.9.12 and worked perfectly.
swagmeister said:
Thanks very much. I couldn't get 2.x.x version working, got a 1.9.12 and worked perfectly.
Click to expand...
Click to collapse
Worked perfectly for me with 1.9.12
Backup success
With the version 1.9.12 it worked for me, too!
Backup, backup backup!
Worked great for me on my GT-I8190L with EFS Pro v1.9.12 :good:
Can someone upload their EFS backup and paste it here, cause I kinda messed mine up and I can't get it back.
Thanks.
Edit: I actually need /modemfs folder /efs is fine.
No will post their efs folder here and if they do it will be taken down.
Efs folder contains the imei, mac etc.
No one wants their phone cloned.
Yes I realized that that's why I edited my post.I need a /modemfs folder, what's in there?
Edit: My /modemfs folder.
I think something's missing in there, I formatted it cause I accidentally installed a boot loader in it (dumba$$ I know) and no matter how many times i flashed my phone via Odin the radio didn't work.
Benzonat0r said:
Yes I realized that that's why I edited my post.I need a /modemfs folder, what's in there?
Edit: My /modemfs folder.
I think something's missing in there, I formatted it cause I accidentally installed a boot loader in it (dumba$$ I know) and no matter how many times i flashed my phone via Odin the radio didn't work.
Click to expand...
Click to collapse
In that folder alone you missing GARDFIIL and trace_auto.conf
I can't find version 1.9.12
Any idea how to...
Tks!
Hi !
I'm porting the TA Backup script to Linux. It advanced pretty well so backup works, but not restore for today.
I wanted to write this post on the developpement forum, but it seems I can't with less than 10 posts…
You can get my work on Github : github.com/Salamandar/Backup-TA-Linux.
Salamandar aka Félix
Top stuff! I had a look through you scripts and they're looking pretty good! A lot easier to read through than the Windows BAT files.
Thanks
I'd like to say that it'd work for OSX too, but i'm not exactly sure. I'll test it when i can.
I just updated the script, it now checks for script files. (all but busybox)
I'll add some options as help.
If you mant some other features, don't hesitate to ask. If you want some other scripts (bash for android), just ask, I'll do it if i can.
I run OSX. I'm happy to look over your scripts and test them out as best I can.
I think that expecting 'adb' to be in a particular place is not the best idea.
I have 'adb' installed, but not in "/opt/android-sdk/platform-tools/". So I modified the ADB="..." line in the script to be
Code:
ADB=`which adb`
Although this requires adb to be installed somewhere in your $PATH. A possible enhancement might be to use `which adb` with a fall-back to asking the user where adb is installed.
---------- Post added at 09:35 PM ---------- Previous post was at 09:27 PM ----------
Hmmm....
I ran the script and got the following output:
Code:
viking$ ../Backup-TA.sh
[ ------------------------------------------------------------ ]
[ Backup TA vL1.0 for Sony Xperia MIT License ]
[ ------------------------------------------------------------ ]
[ Copyright (C) 2013 DevShaft ]
[ ]
[ Permission is hereby granted, free of charge, ]
[ to any person obtaining a copy of this software ]
[ and associated documentation files (the "Software"), ]
[ to deal in the Software without restriction, ]
[ including without limitation the rights to use, ]
[ copy, modify, merge, publish, distribute, sublicense, ]
[ and/or sell copies of the Software, and to permit ]
[ persons to whom the Software is furnished to do so, ]
[ subject to the following conditions: ]
[ ]
[ The above copyright notice and this permission notice ]
[ shall be included in all copies or substantial portions ]
[ of the Software. ]
[ ]
[ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY ]
[ KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE ]
[ WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR ]
[ PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS ]
[ OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR ]
[ OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR ]
[ OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE ]
[ SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. ]
[ ------------------------------------------------------------ ]
Press any key to continue…
[Lots of empty lines]
[ ------------------------------------------------------------ ]
[ Backup TA vL1.0 for Sony Xperia MIT License ]
[ ------------------------------------------------------------ ]
[ Initialization ]
[ ]
[ Make sure that you have USB Debugging enabled, you do ]
[ allow your computer ADB access by accepting its RSA key ]
[ (only needed for Android 4.2.2 or higher) and grant this ]
[ ADB process root permissions through superuser. ]
[ ------------------------------------------------------------ ]
Starting adb and waiting for phone in USB Debugging Mode…
OK
Pushing Backup TA Tools… OK !
Checking for SU binary… OK : Su found at /system/xbin/su
Requesting root permissions… OK : Got Root permissions.
[Lots of empty lines]
[ ------------------------------------------------------------ ]
[ Backup TA vL1.0 for Sony Xperia MIT License ]
[ ------------------------------------------------------------ ]
[ Choose an option : ]
[ 1) Backup ]
[ 2) Restore ]
[ 3) Restore dry-run - nothing will be written on partition ]
[ 4) Convert TA.img to backup ]
[ 5) Quit ]
[ ------------------------------------------------------------ ]
scripts/utils.sh: line 37: read: 0.1: invalid timeout specification
=======================================
BACKUP
=======================================
When you continue Backup TA will perform a backup of the TA partition.
First it will look for the TA partition by its name. When it can not
be found this way it will ask you to perform an extensive search.
The extensive search will inspect many of the partitions on your device,
in the hope to find it and continue with the backup process.
scripts/utils.sh: line 37: read: 0.1: invalid timeout specification
Are you sure? [y/N] y
=======================================
Searchin TA Partition…
Partition not found by name.
scripts/utils.sh: line 37: read: 0.1: invalid timeout specification
Do you want to perform an extensive search for the TA ? [y/N] y
=======================================
Inspecting Partitions…
--- mmcblk0p1 ---
\e[KThis is a compatible TA Partition !figuration…
--- mmcblk0p2 ---
\e[KThis is not a TA Partition.entifier…
--- mmcblk0p3 ---
\e[KThis is not a TA Partition.entifier…
--- mmcblk0p4 ---
\e[KThis is not a TA Partition.entifier…
--- mmcblk0p5 ---
\e[KThis is not a TA Partition.entifier…
--- mmcblk0p6 ---
\e[KThis is not a TA Partition.entifier…
--- mmcblk0p7 ---
\e[KThis is not a TA Partition.entifier…
--- mmcblk0p8 ---
\e[KThis is not a TA Partition.entifier…
--- mmcblk0p9 ---
\e[KThis is not a TA Partition.entifier…
--- mmcblk0p10 ---
\e[KThis is not a TA Partition.entifier…
--- mmcblk0p11 ---
\e[KThis is not a TA Partition.entifier…
--- mmcblk0p12 ---
\e[KThis is not a TA Partition.entifier…
--- mmcblk0p13 ---
\e[KThis is not a TA Partition.entifier…
--- mmcblk0p14 ---
\e[KThis is not a TA Partition.entifier…
--- mmcblk0p15 ---
\e[KThis is not a TA Partition.entifier…
--- mmcblk0p18 ---
\e[KThis is not a TA Partition.entifier…
--- mmcblk0p19 ---
\e[KThis is not a TA Partition.entifier…
--- mmcblk0p20 ---
\e[KThis is not a TA Partition.entifier…
--- mmcblk0p21 ---
\e[KThis is not a TA Partition.entifier…
--- mmcblk0p22 ---
\e[KThis is not a TA Partition.entifier…
Partition found : /dev/block/mmcblk0p1
An unknown error was caught : partition is not set. Aborting…
=======================================
Backup unsuccessful
Cleaning working directory…
Removing files from Android…
Killing ADB Daemon… OK, exiting now !
If you're using ANSI colour sequences, don't. Colour is all well and good, but (as in my case) may not be totally compatible across platforms.
Now, the backup may have failed because my poor phone has had a "rough life" (Stock Sony ROM -> CM10.2 -> FreeXperia -> Stock Sony ROM) and I may have "lost" my TA partition somewhere along the line. Let me restore the backup I made and see what happens.
This is getting very strange. I've restored the original TA backup, rebooted the phone and compared the md5sum output from the original TA backup, the /dev/block/mmcblk0p1 device and the TA backup I took an hour or so ago. They all have different MD5 values. I thought that they should all be the same - after all, they are supposed to be same data.
Code:
aec2542181f6d5c0a21c1563897c9a93 ./TA-backup-2014-05-21.img
347632d7f2761996798acd7f1acc38fc ./TA-backup-2014-09-26.img
63cabee22106f26d25a34d2664ee1695 /dev/block/mmcblk0p1
When I reboot my phone after restoring the TA image, it puts up a "NFC Firmware Update in progress" message. Which is strange - as I'm not doing anything crazy to the NFC, and I'm putting the TA image back to where I got it from.
Any ideas from anyone?
There's a logging area in the TA partition, so the contents and therefore the md5 can vary.
Sent from my C6603 using Tapatalk
I never knew that. It certainly explains why the MD5s were different. Thanks for clearing that up.
Thanks a lot for sharing this work! =)
Will give a shot with my next Xperia as i already lost my TA x)
if [[ "x" == "x$partition" ]]; then
Thank's alot for the scrips, well done.
I had to make a minor fix to get it to work on my setup. The script backup.sh checks for an empty string, but that check failes for some reason (D5803_23.0.A.2.93_Nordic_1288-5411, Linux Mint 17.1 Rebecca, adb version 1.0.31).
The trick was to change
Code:
if [[ ! -z $partition ]]; then
to
Code:
if [[ "x" == "x$partition" ]]; then
I'm not saying anyone should do the same, or that the fix is any good, but I got the script running without indicating any errors and producing some kind of file.
I'm writing this just in case anyone else would have the same problem, and this might provide a clue on how to proceed. And of course to say thank you.
Cheers!
Coming back soon
Hi !
I must admit I changed my phone (OnePlus One) so i didn't work a lot on this script lately (but I found some bugs :s )
I'll work on it next week probably to finish it properly
More infos to come
Salamandar
New structure
Hi everybody,
I rewrote a big part of my script tonight. In fact all the complexity/difficulty/errors i encoutered was due to the adb communication.
So now, I simply copy a big part of the script on the phone, then call it from the computer. That means simpler code and probably an executable script from your phone's terminal if you can't use adb.
I think i'll have finished all of that by friday
The problem here is that I don't have an XPeria anymore to test this so… if someone feels like a beta-tester, just tell me (promise i'll do a safe-beta )
Backup is OP, the rest will follow
Hi !
This took me some more time than hoped, thanks to the sh*t that is adb…
Backup is OP with the new script structure. And way more stable and readable than the old structure.
I let aside the "partition detection" stuff, I don't know if it's useful. Let me know if you get the message "Partition not found by name. Extensive search is not available yet." and we'll see to add some model-specific stuff.
Hiya everybody !
Salamandar
thanks!
Just got a Z3c so will try out soon. Always good to see linux tools (and not just windows!)
Salamandar3500 said:
Hi everybody,
I rewrote a big part of my script tonight. In fact all the complexity/difficulty/errors i encoutered was due to the adb communication.
So now, I simply copy a big part of the script on the phone, then call it from the computer. That means simpler code and probably an executable script from your phone's terminal if you can't use adb.
I think i'll have finished all of that by friday
The problem here is that I don't have an XPeria anymore to test this so… if someone feels like a beta-tester, just tell me (promise i'll do a safe-beta )
Click to expand...
Click to collapse
D*mnit...i just typed up this informative article to explain whats going on & then the ENTIRE thing got deleted
Please keep checking this post as i will gradually add back the info as i go...for now i will post the zips/files & steps I've taken up to this point along with any other knowledge that u need to know and thx to @sicarius128 for pointing out the release of the south american model
View attachment USALTE705_NG1_MODEM.zip
^T705M NG1 MODEM (Flashing this will enable the north american LTE frequencies...i have tested this myself & it DOES indeed work to change the bands)
View attachment STOCK705_NF7_MODEM.zip
^T705 NF7 MODEM (this will put u back on the stock radio if u need it...although it is labeled NF7 it is the same modem that is included with the newer NG2 as well)
IF ANYONE IS ACTUALLY ABLE TO CONNECT AFTER FLASHING THIS THEN PLEASE DONT JUST GET HAPPY AND RUN OFF BECAUSE I NEED ALL THE DETAILS I CAN GET...THX IN ADVANCE
if u enter the dial code *#2263# (if this doesnt work then try *#0011#...i will include a link below with navigation instructions to get to the band selection menu) then select "LTE BAND" both before & after then u will notice that those available have in fact changed from "1.3,5,7,8,20" which are the stock/rest of the world values to "1,2,4,5,7,17" which correspond to the correct USA frequencies...at this point the mod MAY very well be working for some users but unfortunately for me my device still wont connect to the lte network for whatever reason so i need testers to see if this is an exclusive issue to my tab/sim or are there other settings that need to be changed somewhere. Below i will list additional steps i have taken & document other pieces of the puzzle i have put together for those of u who are interested,,,i humblyrequest that any devs or other knowledgeable users PLEASE post with your wisdom so we can get this working
http://forum.xda-developers.com/galaxy-tab-s/help/unlock-aws-tab-s-8-4-lte-t2860001
^SERVICE MODE *#0011# NAVIGATION INSTRUCTIONS (please see post #2...there is an app called "advanced signal status" that makes this easier to access)
So...once i flashed the columbian modem & found that i still wasnt connecting to LTE even though the NA frequencies were in fact found in the aforementioned menu i tried a few more fixes. After doing some reading i ran across a file in the "system/etc" folder named "lteon_netlist.xml" which seems to contain an index of whitelisted lte networks from around the world & upon opening it i noticed that ALL of the north american companies were missing. i found the the file of the same name from the columbian rom & sure enough it included AT&T as well as t-mo & other domestic services. This almost SURELY seems to be an important part of the problem but even after replacing this file my problem persisted...i guess i should mention that i'm on straight talk with an ATT compatible sim & it may not be important but i tried my sim in a LG phone & it worked after i forced it to LTE . To further complicate things...it wouldnt work on an ATT branded note 3 & the sim card from the same note 3 wouldnt connect to lte on my device either even with proper apn settings
So with all of that said...a few more failed attempts i've made include the following
1. added various apn settings including KNOWN working values on other devices
2. deleted "persist.radio.lteon" from the location "data/property" or change its value from false to true
3. flashed the kernel from the colombian rom & even created an entire rom from the firmware in hope that some combination of the files it contained would cause it to connect...everything was fully functional after the fact but alas no LTE
4. did a REAL factory reset with the stock recovery which even erases the contents of the internal sd card
5. altered a note 2 zip which contains ATT csc files inside which interesting enough does change the device product code to T705NTSAATT according to the app "phone info" (links to zip & app below)
6. Used the band selection menu mentioned above to force lte bands only but not only does ths not work it desnt seem to survive a reboot either...i also used the app method to do the same (link below)
7. Last but not least...i have tried to flash the bootloader & YES i'm aware of how dangerous this is which is why i wont be uploading the zip here although i havent yet found a way to get it to overwrite which is one of the question i need answered below
View attachment lteon_netlist.zip
^LTEON_NETLIST.XML (this zip is NOT flashable because i was being lazy :silly:....unzip then replace the file in "system/etc" & dont forget to change permissions to 0644 or rw-r--r--)
View attachment CSC_705_ATT.zip
^ATT CSC (please be aware...this will show the csc version as N7100ATTDMB1 but doesnt seem to cause any issues)
https://play.google.com/store/apps/details?id=com.cc.signalinfo&hl=en\
^ADVANCED SIGNAL STATUS APP (used to determine your current network connection...can be used to force to a certain type or to enable/disable individual gsm/wcdma/lte bands
https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo&hl=en
^PHONE INFO (provides a ton of info about your device...including a list of all secret codes as well as a csc changer)
couple of quick questions for anyone who can provide answers or otherwise assist...thx in advance
1. @bentee20 @crzcraft does choosing the particular bands or lte only in fact force the mode on your devices...i'm aware when u use the app method that u will need to change the setting every boot. Just out of curiousity...could u guys post your location and device/rom details
2. @vovochka-s2 did u ever find a 705 pit file or can anyone else please provide one for us?
3. Directly related to issue 2...has anyone use hemidall to flash there tab & if so could u please list the steps as well as version u used
4. i dont expect any other users to attempt this at least until i can confirm it fixes things...CAN ANYONE PLEASE PROVIDE A PROVEN WAY OF FLASHING THE BOOTLOADER ON NEWER GALAXY DEVICES? It wont flash through odin do to security reasons (neither would the modem file file but it flashed fine using twrp)...i have tried installing it through recovery but after reboot nothing seems to have been changed according to the phone info app
the input of @UpInTheAir (particularly would like your opinion on #3 & #4 above...yeah i know bro but i'm so close & this is the level of desperation i have reached :laugh or @edan1979 would be welcome although i dont think either of u are actually in the states so im not sure how important this issue is to u if at all...to answer your question from the other thread a few weeks NO i 'm not aware of the exact location of the network selector list but i did notice that it disappears from settings after using the att csc zip so i might spend some time to track it down tonight even though i came across an easy way to change it back
@Hakams the above modem should fix your issue if u never figured it out...please report your results
Sorry, I'm not going to get involved with bootloaders, if you get that wrong, your device is in a permanent world of hurt. It is possible to flash with Odin and I remember CWM.zip from the SGS2 days. On some devices, once you upgrade, it is impossible to revert.
Kernel side:
There is option in kernel build .config file with various regions. I haven't yet looked at what it really does in any sort of depth. I think I remember some thresholds and such. Maybe also drivers specific to various regions. (incl. modem/mobile connectivity ??? )
Code:
CONFIG_TARGET_LOCALE_EUR=y
# CONFIG_TARGET_LOCALE_KOR is not set
# CONFIG_TARGET_LOCALE_USA is not set
# CONFIG_TARGET_LOCALE_DEMO is not set
I don't know if it will even compile, but will try later on if you wish ?
UpInTheAir said:
Sorry, I'm not going to get involved with bootloaders, if you get that wrong, your device is in a permanent world of hurt. It is possible to flash with Odin and I remember CWM.zip from the SGS2 days. On some devices, once you upgrade, it is impossible to revert.
Kernel side:
There is option in kernel build .config file with various regions. I haven't yet looked at what it really does in any sort of depth. I think I remember some thresholds and such. Maybe also drivers specific to various regions. (incl. modem/mobile connectivity ??? )
Code:
CONFIG_TARGET_LOCALE_EUR=y
# CONFIG_TARGET_LOCALE_KOR is not set
# CONFIG_TARGET_LOCALE_USA is not set
# CONFIG_TARGET_LOCALE_DEMO is not set
I don't know if it will even compile, but will try later on if you wish ?
Click to expand...
Click to collapse
I understand the risks & all i'm asking if u happen to know a sure-fire way then please pm me or something but i've already attempted odin, twrp & even dd with no results (of course this would be a last resort option...as more users present new info i'm sure i can find the patience to exhaust those possibilities before doing anything dumb)...as far as the kernel is concerned if its not too much trouble then PLEASE attempt to build one for us. I tried the one from the T705M but as i already stated above it flashed fine & was fully functional but didnt let me connect to LTE...one would assume those configurations would already be set since the frequencies are unlocked by default although i could see samsung using that as another way to keep those devices out of the american market so that they dont hurt domestic sales. I appreciate u chiming in & patiently await a test build of the USA enabled kernel...thx in advance
You won't know of a sure fire way until (if) it's successfully done. ...
If you want to proceed, I can't help with that as I haven't played with the BL for a long time and don't want to give wrong or outdated info. Different devices use different ways.
As I said, I won't get involved with the BL at all (publically or PM).
I will try and compile that kernel for you though.
PM sent:
kernel compiled
Code:
CONFIG_TARGET_LOCALE_USA=y
Fairly sure it won't do anytrhing, could only find threshold changes in source related to that config change.
Please be aware I haven't tested the kernel for boot. There is a CIFS patch I've implemented not in v1.5.
The "problem" could actually be on the hardware side. I've owned a I9100T and I9300T. I remember that modems on ther "T" models were optimised for 850 MHz 3G band. The only difference was (the software) modem, and some internal jumper (recalling fading memory here.....)
Ha, found a thread regarding the SGS3 jumper,......... http://forum.xda-developers.com/galaxy-s3/help/samsung-galaxy-s3-19300t-t1688836/page2
My point is, that there could be hardware changes needed as well
I cant do anything as well. its out of my league.
This would be very useful, maybe US users raise some funds to pay for a test device for a recognized developer to see if this could be implemented?
However if it's a one-shot and the phone/tablet is permanently useless, than it might not be worth it.
PIT
I created a PIT file for SM-T705 16GB through heimdall. Cannot for the life of me get firmware to flash with the PIT (re-partition enabled), checked the PIT with PIT Magic on Windows and seems OK, but then again, unfortunately I don't know a great deal about it. I tried with Odin 1.85, 3.07, 3.09. All setup is Ok because I can flash the firmware without.
There was a risk of hard brick,......... but I was "in the mood". That mood is changing again though .............
edan1979 said:
I cant do anything as well. its out of my league.
Click to expand...
Click to collapse
It's ok bro...thx for checking in
Satorikn said:
This would be very useful, maybe US users raise some funds to pay for a test device for a recognized developer to see if this could be implemented?
However if it's a one-shot and the phone/tablet is permanently useless, than it might not be worth it.
Click to expand...
Click to collapse
Although I would prefer not to I'm willing to risk a brick of my own personal device & just file an insurance claim if so...hopefully we will have a breakthrough before then
UpInTheAir said:
I created a PIT file for SM-T705 16GB through heimdall. Cannot for the life of me get firmware to flash with the PIT (re-partition enabled), checked the PIT with PIT Magic on Windows and seems OK, but then again, unfortunately I don't know a great deal about it. I tried with Odin 1.85, 3.07, 3.09. All setup is Ok because I can flash the firmware without.
There was a risk of hard brick,......... but I was "in the mood". That mood is changing again though .............
Click to expand...
Click to collapse
Could u PLEASE upload or pm me the pit file kind sir...don't know if u tried the custom kernel yourself but even though it was a no go I definitely appreciate the effort
@UpInTheAir
hate to waste a post so hopefully u will see this bat signal...which drivers/process did u use to get heimdall to even initiate the flashing process? I can get it too recognize the device fine but once I press start I have various errors depending upon which driver i choose in zdiag...starting to wonder if it's because I'm on x64 Windows 8 or what?
THEDEVIOUS1 said:
It's ok bro...thx for checking in
Although I would prefer not to I'm willing to risk a brick of my own original device & just file an insurance claim if so...hopefully we will have a breakthrough before then
Could u PLEASE upload or pm me the pit file kind sir...don't know if u tried the custom kernel yourself but of course it was a no go but I definitely appreciate the effort
Click to expand...
Click to collapse
This is the heimdall PIT printout:
Entry Count: 24
Unknown 1: 1598902083
Unknown 2: 844251476
Unknown 3: 21324
Unknown 4: 13641
Unknown 5: 12596
Unknown 6: 48
Unknown 7: 0
Unknown 8: 0
--- Entry #0 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 80
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 0
Partition Block Count: 2046
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOTLOADER
Flash Filename: sboot.bin
FOTA Filename:
--- Entry #1 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 70
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 34
Partition Block Count: 16
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PIT
Flash Filename: -
FOTA Filename:
--- Entry #2 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 71
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 50
Partition Block Count: 2048
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MD5HDR
Flash Filename: md5.img
FOTA Filename:
--- Entry #3 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 1
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 8192
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOTA0
Flash Filename: -
FOTA Filename:
--- Entry #4 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 2
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 16384
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOTA1
Flash Filename: -
FOTA Filename:
--- Entry #5 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 3
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 24576
Partition Block Count: 40960
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: EFS
Flash Filename: efs.img
FOTA Filename:
--- Entry #6 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 4
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 65536
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: m9kefs1
Flash Filename: m9kefs1.bin
FOTA Filename:
--- Entry #7 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 5
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 73728
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: m9kefs2
Flash Filename: m9kefs2.bin
FOTA Filename:
--- Entry #8 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 6
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 81920
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: m9kefs3
Flash Filename: m9kefs3.bin
FOTA Filename:
--- Entry #9 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 7
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 90112
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CARRIER
Flash Filename: carrier.img
FOTA Filename:
--- Entry #10 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 8
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 98304
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PARAM
Flash Filename: param.bin
FOTA Filename:
--- Entry #11 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 9
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 114688
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOT
Flash Filename: boot.img
FOTA Filename:
--- Entry #12 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 10
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 131072
Partition Block Count: 20480
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RECOVERY
Flash Filename: recovery.img
FOTA Filename:
--- Entry #13 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 11
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 151552
Partition Block Count: 20480
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: OTA
Flash Filename: -
FOTA Filename:
--- Entry #14 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 12
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 172032
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CDMA-RADIO
Flash Filename: modem_cdma.bin
FOTA Filename:
--- Entry #15 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 13
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 180224
Partition Block Count: 98304
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RADIO
Flash Filename: modem.bin
FOTA Filename:
--- Entry #16 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 14
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 278528
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: TOMBSTONES
Flash Filename: tombstones.img
FOTA Filename:
--- Entry #17 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 15
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 286720
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: TDATA
Flash Filename: tdata.img
FOTA Filename:
--- Entry #18 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 16
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 294912
Partition Block Count: 24576
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PERSDATA
Flash Filename: persdata.img
FOTA Filename:
--- Entry #19 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 17
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 319488
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RESERVED2
Flash Filename: -
FOTA Filename:
--- Entry #20 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 18
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 327680
Partition Block Count: 4894720
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SYSTEM
Flash Filename: system.img
FOTA Filename:
--- Entry #21 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 19
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 5222400
Partition Block Count: 409600
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CACHE
Flash Filename: cache.img
FOTA Filename:
--- Entry #22 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 20
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 5632000
Partition Block Count: 471040
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: HIDDEN
Flash Filename: hidden.img
FOTA Filename:
--- Entry #23 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 21
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 6103040
Partition Block Count: 0
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: USERDATA
Flash Filename: userdata.img
FOTA Filename: remained
I'm just going to give it one last shot..........
Edit: Failed again, stuck at "get PIT for mapping" using 3.07.
PM sent
@THEDEVIOUS1
Installed heimdall on Ubuntu 14.04 64bit ..... Just for your PIT
I didn't actually try flashing anything through heimdall though. Never have (yet).
Kept getting an error eventually download the PIT with device connected to the PC USB 3.0 port. ..
Edit2: Tried to flash PIT with heimdall, but no go. "ERROR: Failed to receive PIT file part response!" , obviuosly something wrong with the PIT. I tried via DD and managed to pull some sort of PIT (doesn't flash), because the count= & BS= no idea where to obtain this info. I'm sure it's device specific
Tester
I will test this tonight when I get home and report back.
Question: What are my chances I will have a successful flash? This may be an obvious question, but assume I will need to root my device first, right?
Device Model: SM-T705
Baseband version: T705ZHU1ANG2
Kernel version: 3.4.39-2290729 [email protected] #1
Build number: KOT49H T705ZHU1ANG2
jadid said:
I will test this tonight when I get home and report back.
Question: What are my chances I will have a successful flash? This may be an obvious question, but assume I will need to root my device first, right?
Device Model: SM-T705
Baseband version: T705ZHU1ANG2
Kernel version: 3.4.39-2290729 [email protected] #1
Build number: KOT49H T705ZHU1ANG2
Click to expand...
Click to collapse
I think the attachments do not exist (maybe taken off a while back)
mac231us said:
I think the attachments do not exist (maybe taken off a while back)
Click to expand...
Click to collapse
Oh man, that suxs! Is there anyway I can get it? I would really like to have my device work with US bands.
jadid said:
Oh man, that suxs! Is there anyway I can get it? I would really like to have my device work with US bands.
Click to expand...
Click to collapse
you might want to ask the OP..he maintains 2 roms one for tabpro and tab S..maybe more...so he is still active on these forums
mac231us said:
you might want to ask the OP..he maintains 2 roms one for tabpro and tab S..maybe more...so he is still active on these forums
Click to expand...
Click to collapse
Thanks, I will!
mac231us said:
I think the attachments do not exist (maybe taken off a while back)
Click to expand...
Click to collapse
not sure what happended...thx for making me ware they were missing
jadid said:
I will test this tonight when I get home and report back.
Question: What are my chances I will have a successful flash? This may be an obvious question, but assume I will need to root my device first, right?
Click to expand...
Click to collapse
the links have been fixed in the first post...thx for testing. i know its a lot but please be sure to read the ENTIRE op...long story short the file labeled USALTE705_NG1_MODEM.zip will in fact flash without problems and show the north american bands when u got to the network menu but still no LTE yet on my personal device (with any luck u will flash this and LTE will automagically work...proving that there is just something set up wrong on my device) The only other zip in the op that i believe to be significant is the lteon_netlist.zip which contains a whitelist of LTE carriers including the north american providers (if u check it against the stock file u will see that they are in fact missing)
while i'm posting i would like to make another plea for some help from other users/devs...can anyone PLEASE tell me a step by step definite method of geting heimdall to recogize this device read the pit/flash files on windows OR linux?!
@pinsb
i posted the band enabling info in thie op of this thread as well as another in the question section...just wanted to get your attention as we may be able to help each other out. So...i'm assuming u were able to achieve root and i was just wondering what chipset the T805W variant uses? (i'm assuming the exynos but i may be mistaken). Most people are not aware but the original samsung tab that tmobile sold could in fact be flashed with the european modem to enable voice calls ( @oldblue910 ...i was gonna bring this to your attention in the other thread but due to the locked bootloader on the ATT version the info was almost irrelevent)! So with all of that said heres what i'm thinking...u MAY be able to flash the brazillian modem which makes calls and also has the north american lte frequencies! Although it would be less impressive...the international modem MAY enable calls with the obvious caveat being that u wouldnt be getting LTE speeds
@jadid
i apologize but i assumed anyone doing this would already have done both...technically all u need to do is flash using cwm/twrp but i would go ahead and root as well
THEDEVIOUS1 said:
not sure what happended...thx for making me ware they were missing
the links have been fixed in the first post...thx for testing. i know its a lot but please be sure to read the ENTIRE op...long story short the file labeled USALTE705_NG1_MODEM.zip will in fact flash without problems and show the north american bands when u got to the network menu but still no LTE yet on my personal device (with any luck u will flash this and LTE will automagically work...proving that there is just something set up wrong on my device) The only other zip in the op that i believe to be significant is the lteon_netlist.zip which contains a whitelist of LTE carriers including the north american providers (if u check it against the stock file u will see that they are in fact missing)
while i'm posting i would like to make another plea for some help from other users/devs...can anyone PLEASE tell me a step by step definite methof of geting heimdall to recogize this device read the pit/flash files on windows OR linux?!
@pinsb
i posted the band enabling info in thie op of this thread as well as another in the question section...just wanted to get your attention as we may be able to help each other out. So...i'm assuming u were able to achieve root and i was just wondering what chipset the T805W variant uses? (i'm assuming the exynos but i may be mistaken). Most people are not aware ( @oldblue910 ...i was gonna bring this to your attention in the other thread but due to the locked bootloader on the ATT version the info was almost irrelevent) but the original samsung tab that tmobile sold could in fact be flashed with the european modem to enable voice calls! So with all of that aid heres what i'm thinking...u MAY be able to flash the brazillian modem which makes calls and also has the north american lte frequencies! Although it would be less impressive...the international modem MAY enable calls with the obvious caveat being that u wouldnt be getting LTE speeds
Click to expand...
Click to collapse
Thank you I appreciate you taking the time to fix the links I download the files. Question: I need to have my device rooted first, right? and do I flash this in odin or cw/twrp? I didn't see any of these details in op.
Thanks again!
THEDEVIOUS1 said:
@pinsb
i posted the band enabling info in thie op of this thread as well as another in the question section...just wanted to get your attention as we may be able to help each other out. So...i'm assuming u were able to achieve root and i was just wondering what chipset the T805W variant uses? (i'm assuming the exynos but i may be mistaken). Most people are not aware but the original samsung tab that tmobile sold could in fact be flashed with the european modem to enable voice calls ( @oldblue910 ...i was gonna bring this to your attention in the other thread but due to the locked bootloader on the ATT version the info was almost irrelevent)! So with all of that said heres what i'm thinking...u MAY be able to flash the brazillian modem which makes calls and also has the north american lte frequencies! Although it would be less impressive...the international modem MAY enable calls with the obvious caveat being that u wouldnt be getting LTE speeds
Click to expand...
Click to collapse
No such luck.
I was looking at buying one on E-Bay UK and was trying to gather info before deciding to purchase. However there's now crazy (IMHO) bidders who have bid it up to over £300 ($480) so not worth the effort now, although whether they'll pay and whether they understand what they're really buying is of course another issue. Auction closes tomorrow on E-Bay UK and isn't too hard to find.
Sorry I can't be more helpful.
--
THEDEVIOUS1 said:
not sure what happended...thx for making me ware they were missing
the links have been fixed in the first post...thx for testing. i know its a lot but please be sure to read the ENTIRE op...long story short the file labeled USALTE705_NG1_MODEM.zip will in fact flash without problems and show the north american bands when u got to the network menu but still no LTE yet on my personal device (with any luck u will flash this and LTE will automagically work...proving that there is just something set up wrong on my device) The only other zip in the op that i believe to be significant is the lteon_netlist.zip which contains a whitelist of LTE carriers including the north american providers (if u check it against the stock file u will see that they are in fact missing)
l
Click to expand...
Click to collapse
I rooted my device and installed TWRP 2.8.1.0 I then flash the USALTE705_NG1_MODEM.zip which installed successfully. I inserted my T-Mobile SIM.
No LTE
I then accessed the Band configuration via the *#0011# code followed the instructions and selected the T-Mobile bands B4 & B17 in the LTE section. and WCDMA: 1900
No LTE
Next attempt was to copy the lteon_netlist.zip file to the system/etc folder and set the permission to 0644 or rw-r--r (note: this file did not exist prior to copying)
No LTE
What else should I try and am I missing anything else?
I need help, I wanted to do my ZTE to 512 and I can not do it at all. Of all the programs that support the device I get the following:
--- = SRS One-Click-Root v5.1 =
16:30:09 - Starting ADB Server ..
16:30:16 - Manufacturer: ZTE
16:30:16 - Model: ZTE BLADE A512
16:30:17 - Android Version: 6.0.1
16:30:17 - Build ID: VDF-A512B01-PT_MR03b
16:30:17 - Board ID: MSM8917
16:30:17 - Chipset Platform: msm8937
16:30:17 - Getting OffSets ..: error: only position independent executables (PIE) are supported. (False)
16:30:18 - Query Server for Best Method .. Found Rootkit: 8
---- = Start Rooting Process .. Please Wait = ----
16:30:19 [+] Testing exploit: root8 (please wait ..)
16:30:21 [+] Remounting / system Filesystem as R / W ..
16:30:21 [+] Installing SU Binary ...
16:30:22 [+] Installing SuperUser APK ...
16:30:23 [+] Remounting / system Filesystem as R / O ..
16:30:28 [+] Rooting Complete!
It gives indication that it gets root but it does not stay.
Another program that supposedly works is this one spoken in this video:
Https://www.youtube.com/watch?v=w_U_pjwE_3Q
Program: http://kidapso.com/autorootdl I can not test because I can not download even responding to the proposed surveys.
If you know of any solutions, share. Thank you
Build ID: VDF-A512B01-PT_MR03b