Database Info

Unlock SIDEKICK 4G [ Read Code Network ]

[ important Root Required ]
Turn On Phone and turn on usb debugging [ setting -> development -> usb debugging ]
Open terminal emulator.
cd /dev/block [Press enter]
su [Press enter] (Your phone ask for superuser access,you allow this)
dd if=/dev/block/bml3 of=/sdcard/bml3.bak [Press enter]
Now find the file in SD and transfer it to your pc.
Open bml3.bak with WinHex
Press Key Ctrl+Alt+X ,now paste this address FFFFFFFFFF0100000000
now you can see the network code
Code:
adb shell su -c "dd if=/dev/block/bml3 of=/sdcard/bml3.bak"
adb pull /sdcard/bml3.bak
Now turn to insert sim card phone,enter the code found. Phone Unlocked
__________
XcachorroX

Help
I am trying to unlock my sidekick 4G but am having trouble. I cant seem to find the code using the binary method. Can someone please help?

Hahah worked brilliantly, love you man!

FFFFFFFFFF0100000000 not found

achaps81 said:
FFFFFFFFFF0100000000 not found
Click to expand...
Click to collapse
Hi buddy, i have a problem because i cant pass shell to root.
can you help me?

[Article]Workaround for grep and Logcat, dmesg, and last_kmsg on Windows

In this article, I will explain some of the confusions that may occur whilst using grep in logcat, dmesg, kmsg and last_kmsg on different platforms,mainly between Unix(Linux based such as ubuntu, linux mint, fedora, BSD based such as netbsd, freebsd, and even Mac) and Windows(Windows XP, Windows Vista, Windows 7, Windows 8 and etc).
Requirements:
Known about the existence of logcat, dmesg, kmsg, and last_kmsg and have tried logging it at least once
Know some basic knowledge of batch/bash(cmd/terminal)
Using Windows OS(The problem only lies on Windows, so if you're using Mac or Linux then you're fine)
Although this is a rather technical article, but I will make it as simple as possible for all of the users to understand
Sometimes, I will see some of the developers will issue similar to this:
Log Commands with Grep
Logcat:
adb logcat | grep 'htc'
Dmesg:
adb shell dmesg | grep 'mp_decision'
last_kmsg:
adb shell cat /proc/last_kmsg | grep 'mp_decision'
Click to expand...
Click to collapse
So, the problem is?
The problem is that if you're using a Windows OS, Windows OS doesn't have grep installed, so your command would not run and you will see an error message like this:
{
"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"
}
Linux or Mac users will not have this problem as they have grep installed, so they are fine.
Workaround:
1. Install a Linux shell on Windows
2. Use a terminal app within the Android phone
3. Connect to the linux shell inside the Android Phone by using your computer
4. Use the built-in filters(for logcat ONLY)
Workaround #1
You can simply click here and follow the simple steps to get a linux shell on your computer
Click to expand...
Click to collapse
Workaround #2
You just need to download a terminal app from your phone and every command will work fine. You would need to omit the adb and adb shell keyword(refer below) in order for the command to work. A nice terminal app suggestion would be https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en which you can simply download from Google Playstore
Click to expand...
Click to collapse
Workaround #3
You can just type "adb shell" and press enter, then type your commands(omit all adb and adb shell keyword) and it will work just as like in workaround #2.
Click to expand...
Click to collapse
Example
1. "adb shell" + enter
2. Choose the command that you wanted:
Logcat:
logcat | grep 'htc'
Dmesg:
dmesg | grep 'mp_decision'
last_kmsg:
cat /proc/last_kmsg | grep 'mp_decision'
Click to expand...
Click to collapse
Workaround #4
This workaround is a workaround which only exists for logcat, because logcat have a filtering system that is built into it(makes us wonder why it is not built into dmesg and last_kmsg as well eh?).
For example, the grep command for the logcat above can be replaced by:
adb logcat htc:V *:S
Click to expand...
Click to collapse
However, the downside is that you need to know the exact name of the app which is logged at the logcat in order to search for it while you can do a random keyword search with grep which helps a lot if you do not know what to look for.
For more information about the filtration, you can refer to http://developer.android.com/tools/debugging/debugging-log.html
Click to expand...
Click to collapse
Conclusion:
Hopefully, after reading this article, you will know how to deal with grep when you're on Windows OS
Do drop me a question or two if you have something that you don't understand and stay tuned for more articles! :highfive:

Actually most of these are already known but neverthless nice guide
Ps: Limited to 8 thanks per day so will thank later !

nikufellow said:
Actually most of these are already known but neverthless nice guide
Ps: Limited to 8 thanks per day so will thank later !
Click to expand...
Click to collapse
I do agree that the last 3 solutions are common but there's still people who doesn't know about it.
But I think that there'll be quite some people who doesn't know about the first workaround though, as it is not covered in most tutorials(unless you're looking at a rom building tutorial on windows), or do you?
Sure thing and thanks in advance

Found it when I needed the most, the 1st method.. Thanks, simple but a good article
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app

ravike14 said:
Found it when I needed the most, the 1st method.. Thanks, simple but a good article
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You're welcome Glad to be of help even though this thread is already at least one year old

wcypierre said:
You're welcome Glad to be of help even though this thread is already at least one year old
Click to expand...
Click to collapse
i found it useful after year hehe....hey for some weird reason the method 1 and 3 fails when it comes to '' dmesg | grep 'xxx' > dmesg.txt '' commad :/ the text comes empty even tho the grep related logs are there in the normal dmesg when i try method 1 using [Msysgit]..when i try the 3rd method it just say read only file system and stops if i choose the output as a .txt file..when i enter 'dmesg | grep 'xxx' without '.txt' it do nothing :/

ravike14 said:
i found it useful after year hehe....hey for some weird reason the method 1 and 3 fails when it comes to '' dmesg | grep 'xxx' > dmesg.txt '' commad :/ the text comes empty even tho the grep related logs are there in the normal dmesg when i try method 1 using [Msysgit]..when i try the 3rd method it just say read only file system and stops if i choose the output as a .txt file..when i enter 'dmesg | grep 'xxx' without '.txt' it do nothing :/
Click to expand...
Click to collapse
For the 1st method, there won't be any output as it is redirected to the file 'dmesg.txt'. Or you're indicating that the dmesg.txt file is empty?
For the 3rd one, are you running it on a rooted phone or stock bootloader?
Last but not least, can you give me an example of the command that you had tried for the 1st and 3rd method and a snippet of the dmesg.txt so that I can look into your problem?

wcypierre said:
For the 1st method, there won't be any output as it is redirected to the file 'dmesg.txt'. Or you're indicating that the dmesg.txt file is empty?
For the 3rd one, are you running it on a rooted phone or stock bootloader?
Last but not least, can you give me an example of the command that you had tried for the 1st and 3rd method and a snippet of the dmesg.txt so that I can look into your problem?
Click to expand...
Click to collapse
The dmesg.txt is empty, not even adb daemon text is there.. And yea I'm rooted and s-off.... I tried
For 1st method
adb shell dmesg | grep 'wl127xx' > dmesg.txt
For 3rd i tried
dmesg ¦ grep 'wl127xx'
And
dmesg ¦ grep 'wl127xx' > dmesg.txt
Tried the 3rd method even in Linux shell still a no go the txt is empty it just creates it and that's it.. When I execute the command without 'grep' I get the dmesg logs correctly.. But I really want the grep part lol..
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app

ravike14 said:
The dmesg.txt is empty, not even adb daemon text is there.. And yea I'm rooted and s-off.... I tried
For 1st method
adb shell dmesg | grep 'wl127xx' > dmesg.txt
For 3rd i tried
dmesg ¦ grep 'wl127xx'
And
dmesg ¦ grep 'wl127xx' > dmesg.txt
Tried the 3rd method even in Linux shell still a no go the txt is empty it just creates it and that's it.. When I execute the command without 'grep' I get the dmesg logs correctly.. But I really want the grep part lol..
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
can you copy the text snippet of the dmesg that contains the 'wl127xx' text then? A screenshot or the actual text would do

wcypierre said:
can you copy the text snippet of the dmesg that contains the 'wl127xx' text then? A screenshot or the actual text would do
Click to expand...
Click to collapse
if you mean the normal dmesg text,

ravike14 said:
if you mean the normal dmesg text,
Click to expand...
Click to collapse
From what I've saw, there's only 'wl12xx' instead of 'wl127xx' though(note the missing '7'). Hence, the command should be dmesg | grep 'wl12xx'

wcypierre said:
From what I've saw, there's only 'wl12xx' instead of 'wl127xx' though(note the missing '7'). Hence, the command should be dmesg | grep 'wl12xx'
Click to expand...
Click to collapse
lol this is embarrassing haha i dont know how i missed that detail, thanks it worked i used '' dmesg | grep 'wl12xx' > /sdcard/dmesg.txt '' for method 3 and with adb shell i got it to pc straightly .. haha thanks again

ravike14 said:
lol this is embarrassing haha i dont know how i missed that detail, thanks it worked i used '' dmesg | grep 'wl12xx' > /sdcard/dmesg.txt '' for method 3 and with adb shell i got it to pc straightly .. haha thanks again
Click to expand...
Click to collapse
You're welcome After ruling out a few possibilities, I do feel that its either your grepping is wrong or the dmesg doesn't contains that text, which turns out to be true later on

[Q] Internal Memory Recovery -- help please

Hi,
I have a Verizon Samsung Galaxy S3 SCH-I535.
I have rooted it using this guide. I realize there was probably an easier way to root it, but regardless it worked fine, I have root access.
The phone is returned to factory condition, pretty much, but I need to recover data from it. There is no microSD card.
I have tried to follow this guide for recovering the internal memory without being able to transfer the internal memory to my computer. I'm stuck at the data transfer point.
I've followed the guide to the letter, except I'm trying to recover memory block /dev/block/mmcblk0p23 (and I've also tried simply /dev/block/mmcblk0), so I've modified the commands to the following:
Code:
adb forward tcp:5555 tcp:5555
adb shell
/system/xbin/busybox nc -l -p 5555 -e /system/xbin/busybox dd if=/dev/block/mmcblk0p23
And in the other Cygwin terminal:
Code:
adb forward tcp:5555 tcp:5555
cd /nexus
nc 127.0.0.1 5555 | pv -i 0.5 > mmcblk0p23.raw
Screenshots attached. I'm not sure why, but the data stays at 0 B/s no matter how long I let it run.
Am I missing something? Am I doing something wrong? I've installed Busybox on the phone (it's in xbin, not bin, hence the modified syntax). Cygwin (with pv and util-linux), Netcat, and ADB on the computer. USB debugging mode is enabled on the phone (ADB connection works).
I really need to pull the internal data off of this phone soon... can anyone help me get this figured out please? Thanks.

mastercsmc said:
Hi,
I have a Verizon Samsung Galaxy S3 SCH-I535.
I have rooted it using this guide. I realize there was probably an easier way to root it, but regardless it worked fine, I have root access.
The phone is returned to factory condition, pretty much, but I need to recover data from it. There is no microSD card.
I have tried to follow this guide for recovering the internal memory without being able to transfer the internal memory to my computer. I'm stuck at the data transfer point.
I've followed the guide to the letter, except I'm trying to recover memory block /dev/block/mmcblk0p23 (and I've also tried simply /dev/block/mmcblk0), so I've modified the commands to the following:
Code:
adb forward tcp:5555 tcp:5555
adb shell
/system/xbin/busybox nc -l -p 5555 -e /system/xbin/busybox dd if=/dev/block/mmcblk0p23
And in the other Cygwin terminal:
Code:
adb forward tcp:5555 tcp:5555
cd /nexus
nc 127.0.0.1 5555 | pv -i 0.5 > mmcblk0p23.raw
Screenshots attached. I'm not sure why, but the data stays at 0 B/s no matter how long I let it run.
Am I missing something? Am I doing something wrong? I've installed Busybox on the phone (it's in xbin, not bin, hence the modified syntax). Cygwin (with pv and util-linux), Netcat, and ADB on the computer. USB debugging mode is enabled on the phone (ADB connection works).
I really need to pull the internal data off of this phone soon... can anyone help me get this figured out please? Thanks.
Click to expand...
Click to collapse
Are you running cygwin as an administrator? Are you requesting superuser access by typing su after adb shell?

billard412 said:
Are you running cygwin as an administrator? Are you requesting superuser access by typing su after adb shell?
Click to expand...
Click to collapse
Hi billard, thank you for the response.
I have tried using su (# prompt instead of $ appears, so yes it is working) after adb shell, with no change in results.
I hadn't tried running Cygwin as administrator, but just made that change as well to see if it would make a difference. Still no dice.
I've also ensured NTFS permissions in the /nexus folder (C:\Cygwin\nexus) are "full access", and there are no issues there, either. Screen shot attached of latest attempt (Cygwin is "run as administrator"/su command used).

mastercsmc said:
Hi billard, thank you for the response.
I have tried using su (# prompt instead of $ appears, so yes it is working) after adb shell, with no change in results.
I hadn't tried running Cygwin as administrator, but just made that change as well to see if it would make a difference. Still no dice.
I've also ensured NTFS permissions in the /nexus folder (C:\Cygwin\nexus) are "full access", and there are no issues there, either. Screen shot attached of latest attempt (Cygwin is "run as administrator"/su command used).
Click to expand...
Click to collapse
Don't know why I didn't catch this sooner. But what lead you to believe it was mmcblk0p23 you needed to use? I'm not sure exactly what that partition is(if it exists) but the data partition is mmcblk0p15 I believe on the US S3's. Try that

billard412 said:
Don't know why I didn't catch this sooner. But what lead you to believe it was mmcblk0p23 you needed to use? I'm not sure exactly what that partition is(if it exists) but the data partition is mmcblk0p15 I believe on the US S3's. Try that
Click to expand...
Click to collapse
I was guessing it was the highest numerical memory block, and /system/dev/block ls lists 23 as the highest number.
I just tried with mmcblk0p15 and have the same exact frustrating 0 B/s indefinite results. -_-

[UPDATE] Galaxy S5 Developer edition ROOT & RECOVERY

Guys I can confirm the twrp klte recovery .tar file available on twrp's website works for the Verizon GS5 development edition phone. I am rooted as well
**This thread is aimed at folks who have already acquired the developer phone and need a little guidance and/or concrete evidence that is easy to find regarding how they should proceed with recovery and root. The other threads were geared towards linking folks to a .com site for purchase and the pros and cons of the dev edition.
Follow me @Bash_array

das7982 said:
Guys I can confirm the twrp klte recovery .tar file available on twrp's website works for the Verizon GS5 development edition phone. I am rooted as well
Follow me @Bash_array
Click to expand...
Click to collapse
Did you flash TWRP then install the Superuser zip in order to gain root?

Skeetch79 said:
Did you flash TWRP then install the Superuser zip in order to gain root?
Click to expand...
Click to collapse
Download the superuser.zip file of your choice (I used SuperSu). Flash TWRP Klte recovery image using ODIN.... Bootloader is unlocked out of the box. Then flash superuser zip via TWRP :good:

das7982 said:
Download the superuser.zip file of your choice (I used SuperSu). Flash TWRP Klte recovery image using ODIN.... Bootloader is unlocked out of the box. Then flash superuser zip via TWRP :good:
Click to expand...
Click to collapse
I have the DevS4... so identical process. But DevS4 can also use saferoot and preserve stock recovery
Sent from my SCH-I545 using Tapatalk

Moderator Comment: There is a reason for the report button; please make your comments germane to the thread topic, avoid arguing with anyone in the open forum, and be respectful at all times. We have a threadbare thread due to not following the aforementioned basic standards of decency.

das7982 said:
Guys I can confirm the twrp klte recovery .tar file available on twrp's website works for the Verizon GS5 development edition phone. I am rooted as well
**This thread is aimed at folks who have already acquired the developer phone and need a little guidance and/or concrete evidence that is easy to find regarding how they should proceed with recovery and root. The other threads were geared towards linking folks to a .com site for purchase and the pros and cons of the dev edition.
Follow me @Bash_array
Click to expand...
Click to collapse
Awesome, my DE SG5 is waiting for me at home, will try soon and confirm. Thanks!

How did you guys activate the phone on your verizon account? Did you take it to them or do you just swap sim card?

razzrmaxx said:
How did you guys activate the phone on your verizon account? Did you take it to them or do you just swap sim card?
Click to expand...
Click to collapse
Swap sim cards.

razzrmaxx said:
How did you guys activate the phone on your verizon account? Did you take it to them or do you just swap sim card?
Click to expand...
Click to collapse
I activated online and typed in the IMEI and the serial# of the SIM card that was in the phone.
BTW: it's working fine, here are the files I used:
1. Drivers: http://forum.xda-developers.com/showthread.php?t=2038555
2. Odin: http://samsung-updates.com/Odin307.zip
3. TWRP: http://techerrata.com/browse/twrp2/klte
4. Root: http://download.chainfire.eu/396/SuperSU/

Hey I'm very happy that you posted this thread up. I got my s5 Developer Edition a couple of days ago and it been sitting until someone could confirm this. With that being said.
What should us owners of the S5 Developer Edition do next? How could we retain a factory img of our current firmware (without losing unlocked bootlaoder status) since there is no factory image available directly from Samsung or verizon. Also, could we flash roms from other devices such as 900f, 900t, etc.... ?

sinfulmatik said:
Hey I'm very happy that you posted this thread up. I got my s5 Developer Edition a couple of days ago and it been sitting until someone could confirm this. With that being said.
What should us owners of the S5 Developer Edition do next? How could we retain a factory img of our current firmware (without losing unlocked bootlaoder status) since there is no factory image available directly from Samsung or verizon. Also, could we flash roms from other devices such as 900f, 900t, etc.... ?
Click to expand...
Click to collapse
Once you accomplish root, the next step you should immediately take is dd all partitions!!! I mean all!! Make a back up of all partitions!!! There are no official ODIN images available for the DevS4 or DevS5 - all images have come from the community. We have rooted our devices and backed up the partitions in case something goes wrong and we need to recover. Again, back up system, cache, radio, modem, aboot, recovery, etc etc etc....all!
You can run the following command from either the Android Terminal Emulator app on your phone (as "su") or (assuming the Samsung drivers and ADB are set up properly on your computer) plug your phone into your PC, open up a command prompt as administrator, type, without quotes, "adb shell", then type "su", grant superuser access. Type "ls -l /dev/block/platform/msm_sdcc.1/by-name/" (those are lower case "L"'s BTW). This will print out a list of all your partitions, then proceed to back them up.
You can back them up from either your Terminal app on the phone as "su" or PC again in a command prompt and ADB Shell as "su".
For example, to back up your system partition, you can try: dd if=/dev/block/platform/msm_sdcc.1/by-name/system of=/mnt/extSdCard/system.img.ext4
This will back up the partition (which is 2+GB) to your external card on your phone. You can change the directory (destination path if you want). Then after you are complete with all the partition backups, adb pull them or transfer them to your PC.
Some of the partition files names should be saved as:
aboot.mbn (ABOOT partition)
boot.img (boot partition)
NON-HLOS.bin (radio partition)
recovery.img (recovery partition)
modem.bin (modem partition)
and so on and so forth
For my Galaxy S4 Dev here are all the commands which I ran after getting my partition list while on I545OYUEMK2:
adb shell "su -c mkdir /mnt/extSdCard/MK2dump"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/mnt/extSdCard/MK2dump/aboot.mbn'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/apnhlos of=/mnt/extSdCard/MK2dump/NON-HLOS.bin'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/backup of=/mnt/extSdCard/MK2dump/backup.img'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/mnt/extSdCard/MK2dump/boot.img'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/cache of=/mnt/extSdCard/MK2dump/cache.img.ext4'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/carrier of=/mnt/extSdCard/MK2dump/carrier.img.ext4'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/efs of=/mnt/extSdCard/MK2dump/efs.img.ext4'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/mnt/extSdCard/MK2dump/fota.img'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/fsg of=/mnt/extSdCard/MK2dump/fsg.img'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/hidden of=/mnt/extSdCard/MK2dump/hidden.img.ext4'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/m9kefs1 of=/mnt/extSdCard/MK2dump/m9kefs1.bin'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/m9kefs2 of=/mnt/extSdCard/MK2dump/m9kefs2.bin'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/m9kefs3 of=/mnt/extSdCard/MK2dump/m9kefs3.bin'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/mdm of=/mnt/extSdCard/MK2dump/modem.bin'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst1 of=/mnt/extSdCard/MK2dump/modemst1.bin'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst2 of=/mnt/extSdCard/MK2dump/modemst2.bin'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/pad of=/mnt/extSdCard/MK2dump/pad.img'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/param of=/mnt/extSdCard/MK2dump/param.lfs'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/persdata of=/mnt/extSdCard/MK2dump/persdata.img.ext4'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/persist of=/mnt/extSdCard/MK2dump/persist.img'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=/mnt/extSdCard/MK2dump/recovery.img'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/rpm of=/mnt/extSdCard/MK2dump/rpm.mbn'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/sbl1 of=/mnt/extSdCard/MK2dump/sbl1.mbn'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/sbl2 of=/mnt/extSdCard/MK2dump/sbl2.mbn'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/sbl3 of=/mnt/extSdCard/MK2dump/sbl3.mbn'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/ssd of=/mnt/extSdCard/MK2dump/ssd.img'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/system of=/mnt/extSdCard/MK2dump/system.img.ext4'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/tz of=/mnt/extSdCard/MK2dump/tz.mbn'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/userdata of=/mnt/extSdCard/MK2dump/userdata.img.ext4'"

So grateful you guys took the time to share this. I've been holding off on purchasing the DevEd. I have the S4 DeveloperEdition, because I had to get my consumer edition replaced after the MDk bootloader was no more. I love the freedom of an unlocked bootloader, but I've been a little afraid that if they never crack the consumer edition we will never see custom roms for this device.
Do you guys think that if they never unlock the consumer vzw s5 bootloader we will see CM, or other varients make their way to the Developer edition? I know it's just speculation at this point, but If I have to run touchwiz, I may just want to stick with my s4 and return the new one.

Skeetch79 said:
Once you accomplish root, the next step you should immediately take is dd all partitions!!! I mean all!! Make a back up of all partitions!!! (...)
Click to expand...
Click to collapse
Thanks, here is the bat file for the Verizon SG5: (You'll need around 8+GB on your external SD card and around 10 minutes to complete)
Code:
adb shell "su -c mkdir /mnt/extSdCard/ANCGdump"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/mnt/extSdCard/ANCGdump/aboot.mbn'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/apnhlos of=/mnt/extSdCard/ANCGdump/NON-HLOS.bin'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/backup of=/mnt/extSdCard/ANCGdump/backup.img'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/mnt/extSdCard/ANCGdump/boot.img'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/cache of=/mnt/extSdCard/ANCGdump/cache.img.ext4'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/carrier of=/mnt/extSdCard/ANCGdump/carrier.img.ext4'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/dbi of=/mnt/extSdCard/ANCGdump/dbi.img.ext4'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/ddr of=/mnt/extSdCard/ANCGdump/ddr.img.ext4'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/efs of=/mnt/extSdCard/ANCGdump/efs.img.ext4'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/mnt/extSdCard/ANCGdump/fota.img'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/fsc of=/mnt/extSdCard/ANCGdump/fsc.img'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/fsg of=/mnt/extSdCard/ANCGdump/fsg.img'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/modem of=/mnt/extSdCard/ANCGdump/modem.bin'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst1 of=/mnt/extSdCard/ANCGdump/modemst1.bin'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst2 of=/mnt/extSdCard/ANCGdump/modemst2.bin'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/pad of=/mnt/extSdCard/ANCGdump/pad.img'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/param of=/mnt/extSdCard/ANCGdump/param.lfs'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/persdata of=/mnt/extSdCard/ANCGdump/persdata.img.ext4'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/persist of=/mnt/extSdCard/ANCGdump/persist.img'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=/mnt/extSdCard/ANCGdump/recovery.img'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/rpm of=/mnt/extSdCard/ANCGdump/rpm.mbn'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/sbl1 of=/mnt/extSdCard/ANCGdump/sbl1.mbn'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/ssd of=/mnt/extSdCard/ANCGdump/ssd.img'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/system of=/mnt/extSdCard/ANCGdump/system.img.ext4'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/tz of=/mnt/extSdCard/ANCGdump/tz.mbn'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/userdata of=/mnt/extSdCard/ANCGdump/userdata.img.ext4'"

sinfulmatik said:
Hey I'm very happy that you posted this thread up. I got my s5 Developer Edition a couple of days ago and it been sitting until someone could confirm this. With that being said.
What should us owners of the S5 Developer Edition do next? How could we retain a factory img of our current firmware (without losing unlocked bootlaoder status) since there is no factory image available directly from Samsung or verizon. Also, could we flash roms from other devices such as 900f, 900t, etc.... ?
Click to expand...
Click to collapse
I'm going to provide a dd of all partitions. However, you'll need to dd your own aboot partition as these are individually unlocked and have unique bootloader keys.
Sent from my SM-G900V using XDA Premium 4 mobile app

razzrmaxx said:
How did you guys activate the phone on your verizon account? Did you take it to them or do you just swap sim card?
Click to expand...
Click to collapse
Just put your Sim in the new phone.
Sent from my SM-G900V using XDA Premium 4 mobile app

Hey thanks guys so much for your help. I will do a soon a I get home. dd all partitions using the bat file got it. Also what about flashing roms for other carrier versions? Other should I wait for a verizon specific rom created by a dev? IIf I were to root wouldn't trip the Knox counter ?

sinfulmatik said:
Hey thanks guys so much for your help. I will do a soon a I get home. dd all partitions using the bat file got it. Also what about flashing roms for other carrier versions? Other should I wait for a verizon specific rom created by a dev? IIf I were to root wouldn't trip the Knox counter ?
Click to expand...
Click to collapse
Not sure about ROMs for other carriers. Stick to either ROMs for Verizon or "universal" ROMs. Who cares about tripping Knox if it does. ... You have a Developer Edition!
Sent from my SCH-I545 using Tapatalk

Skeetch79 said:
Once you accomplish root, the next step you should immediately take is dd all partitions!!! I mean all!! Make a back up of all partitions!!!
Click to expand...
Click to collapse
is there any way to do this complete partition backup prior to voiding the warranty from altering the software?
i am coming from a gnex and rooting is huge deal for me to replace my aging phone. custom roms, not as much, but i need it to be high end, i need it to be rootable, and i need it to be on verizon. (and i KNOW that verizon wont be getting a nexus again after they botched the gnex, which is the vanilla android OS that I want EXACTLY). but this is as close as I can get considering the circumstances and factors at play.
once i saw it was successfully rooted, i went and bought the s5 developer edition an hour ago (and extra battery/battery charger at 50% off with coupon) as i need to stay with Verizon as i am grandfathered unlimited data and have to pay full price for a new phone to keep that. as much a sI dont want to to business with verizon, the unlimited data/coverage/vs speed makes it a no brainer (especially when merely tethering)
this unlocked and rootable s5 (great hardware) seems like the best choice considering all of my personal factors, what has come, and what looks to be on the horizon (replacable battery is a MAJOR issue for me, and an extra battery with build in charger was PERFECT as I now carry 2 spare batteries without a dedicated charger).
i can add a large sd and freeze the bloatware or just deal with it, and can be ok staying with no OTA updates, but I might explore other roms as well if and when they become available if they upgrade android versions successfully and the s5 retail gets rooted eventually
so, to sum up and form a question out of my rambling, is there a way to back up EVERYTHING prior to altering the software or is the only way to do this with root?
I am going to use the s5 developer without rooting for 2 to 3 weeks to make sure the hardware is solid and i wont get hosed by the 30 day hardware warranty (you better believe i am dunking that SOB in water and making sure that it is indeed as claimed, more or less short term, shallow depth, water proof), and i want to do this PRIOR to altering the software/firmware to make sure all the hardware works as claimed, and I would MUCH rather backup every partition immediately after activating, before testing for a couple weeks and dunking it and eventually rooting it
is this possible?
after I am sure the hardware has no issues with warranty, i will be happy to factory reset, then root, then backup.
but can i backup the pre root stock image without, i think it is called triggering the knox by altering the soft/firm ware?
i know i cant reset once i have triggered it, but can i back up all partitions PRIOR to triggering it?
thanks, and this is a general question, not just to you, skeetch. but you certainly bring up a good point

Have any of you tried running a unified build of any AOSP ROMs yet? If there are any out yet... I'm not sure I'm still on an MDK S4 but I'm watching here closely to see how you guys make out. I'd possibly grab a Dev S5 if we could run any unified builds since that opens up many options. Great work by the way!
Sent from my SCH-I545 using Tapatalk

mulch maker said:
is there any way to do this complete partition backup prior to voiding the warranty from altering the software?
Click to expand...
Click to collapse
mulch maker said:
so, to sum up and form a question out of my rambling, is there a way to back up EVERYTHING prior to altering the software or is the only way to do this with root?
Click to expand...
Click to collapse
Umm, ok, in order to back up the partitions you have to root the device. Therefore, you will need to alter the software in order to back up the partitions. But if you are worried about ever having to warranty your device what, about uninstalling root through the superuser app? Another thing, once rooted, you phone may show a boot screen with the word "custom" on it and an open padlock. Unrooting, may remedy this and reset it back to the "official" boot screen. Anyone know if triangleaway could work on the GS5? I know root really hasn't been worked out yet, though.
Can someone chime in?

"Not running as root. Try "adb root" first." despite trying "adb root" above

C:\Users\HieAnh>adb root
restarting adbd as root
C:\Users\HieAnh>adb remount
Not running as root. Try "adb root" first.
Click to expand...
Click to collapse
after i do :"adb root" to cmd,
then i get :"restarting adbd as root"
next i do :"adb remount"
but i get :"Not running as root. Try "adb root" first."
a big question for this problem
my phone is rooted, switch ro.secure=0, ro.debuggle=1
pls help me

What response do you get when you type su in shell?

ze7zez said:
What response do you get when you type su in shell?
Click to expand...
Click to collapse
i get :
C:\Users\HieAnh>adb shell
gracerlte:/ $ su
gracerlte:/ #
Click to expand...
Click to collapse

The ADB driver does not care at all whether phone's Android is rooted or not. As you correctly stated one have to run adb root for ADB to gain root access device's Android.
I don't want to examine why adb root in your case doesn't work.
Anyways the following should be a workaround:
Code:
adb devices
adb shell "su -c 'mount -o remount,rw /system'"
...
...

jwoegerbauer said:
The ADB driver does not care at all whether phone's Android is rooted or not. As you correctly stated one have to run adb root for ADB to gain root access device's Android.
I don't want to examine why adb root in your case doesn't work.
Anyways the following should be a workaround:
Code:
adb devices
adb shell "su -c 'mount -o remount,rw /system'"
...
...
Click to expand...
Click to collapse
hmm, i just run
adb pull /data/data
Click to expand...
Click to collapse
but i get
/data/data/: 0 files pulled, 0 skipped.
Click to expand...
Click to collapse
why ?

You have to mount /data partitton as RW.