Related
For anyone having issues with running this in linux.
I used zikronix guide and modified it for use in a linux support thread. The original thread can be found here:
http://forum.xda-developers.com/showthread.php?t=829045
This is my setup:
-I made sure to show my .bashrc profile and path to my tools folder if you needed help getting that setup as well... If not please ignore.
Code:
[email protected]:~$ cat .bashrc | grep adb
alias start-adb='sudo /usr/local/android-sdk/tools/./adb start-server'
alias kill-adb='sudo /usr/local/android-sdk/tools/./adb kill-server'
[email protected]:~$ cat .bashrc | grep android-sdk
export PATH="/usr/local/android-sdk/tools/:${PATH}"
[email protected]:~$ $PATH
bash: /usr/local/android-sdk/tools/:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:
Download: http://www.wackynoodle.com/hboot202-s_off-V6.2.zip
Download (Mirror): http://sdx-downloads.com/EVO/devs/jerdog/fixes/hboot202-s_off-V6.2.zip
Now This might make things easier.
-I have this so that you are in the same enviroment that i was in so that the paths will be the same.
Code:
wget http://www.wackynoodle.com/hboot202-s_off-V6.2.zip
mkdir Evo-root
mv hboot202-s_off-V6.2.zip
cd Evo-root
unzip hboot202-s_off-V6.2.zip
- This step I just made sure that adb devices showed my device. If not get it working.
- Once adb devices showed my device properly, I simply ran the following commands.
Code:
adb push root/unrevoked-forever.zip /sdcard/
adb push root/mtd-eng.img /sdcard/
adb push pc36img/PC36IMG-ENG.zip /sdcard/PC36IMG.zip
adb push root/flash_image /data/local/
adb push root/rageagainstthecage /data/local/tmp
adb push root/amon_ra.img /sdcard/
- Then this is just changing permissions. Pretty straight forward.
Code:
adb shell
chmod 0755 /data/local/tmp/rageagainstthecage
chmod 0755 /data/local/flash_image
- Running the script. Should kick you out of adb... If not after 5 min kill the adb server and restart.
Code:
adb shell
./data/local/tmp/rageagainstthecage
- Now you should see a "#", if you do proceed. If not then run the script above again till it works.
Code:
adb shell
- If you saw that "#" run this. This can only be ran as root "#" means root.
Code:
./data/local/flash_image misc /sdcard/mtd-eng.img
Now you are going to want to reboot into the bootloader. Make sure once you do that you selet bootloader and let the PC36IMG.zip load.
Code:
reboot bootloader
After that is done reboot into the new rooted rom. Then make sure adb works again. Then run the following commands. Make sure you terminal is in the same directory this entire time there is no reason to leave the direcory we went into earlier "cd Evo-root" You directory should always be Evo-root. Thanks. The part that I found out was the second command where the entire recovery/ needed the permissions changed to be executable. As you saw in my post on that forum board.
- This will remove the PC36IMG.zip to a different name so that the bootloader won't get confused again. Then the second commands makes the directory executable recursivly. Then the third will reboot you into recovery.
Code:
adb shell mv /sdcard/PC36IMG.zip /sdcard/PC36IMG-ENG.zip
chmod -R +x recovery/
adb reboot recovery
- Now this is going to be done at the recovery screen. As long as you followed the steps above it will work fine. Should only take you about 20 mins to root this phone. Though it took me about 2 hours since no one else has been rooting using linux. I am thinking about writing a script that will root everything and alls you have to do is follow a terminal guide.... But ill see.
- Just run these commands that will allow you to flash the unrevoked-forever.zip. Once you follow the onscreen instructions of the unrevoked-forever.zip you will be able to reboot into the recovery and see the S-Off. Once that is done reboot into the rom, now we need to flash a custom recovery!
Code:
adb push recovery /
adb shell busybox --install /sbin
adb shell nohup /sbin/recovery &
- Again make sure your terminal was never closed and in the same folder. Then simply run these commands to flash the Amon_ra recovery. Since it has wimax capabilities I prefer it.
Code:
adb push root/flash_image /data/local/
adb shell
chmod 0755 /data/local/flash_image
./data/local/flash_image recovery /sdcard/amon_ra.img
reboot recovery
Now you should see the custom recovery and you should be able to flash any rom you desire!
reserved for later use
i see that they are same commands as the pc.., so would this also work with PC?
nickespi said:
i see that they are same commands as the pc.., so would this also work with PC?
Click to expand...
Click to collapse
I am guessing your talking about windows? Sure make sure adb is in your path. Though there are steps in here that are only for linux.
95% success
Well I want to thank you for this thread
It has worked for me I have root I have NAND unlocked
I can flash ROMs
The only issue I have is my radio/baseband and PRI version have been lowered
I have not been able to get thise back where they whould with either update or by using teh wimax.ADDRESS.tree.xml fix (there is no file with that)
If you have any ideas how to fix this would be much appreciated
I am unable to get higher tahn baseband 1.36.00.04.02 in ant rom
when I got teh phone it was 2.15.00.xx.xx
any help would be appreciated
100% Success
THANK YOU
My Evo
Hardware 004
Build 3.30
Hboot 2.02
Baseband 2.15.xx.xx
is now sucessfully rooted.
I did have some problems after being able to flash ROMs of not haveing PRI and Baseband updated.
On thread #787756 there are downloads that can be flashed to fix this problem if anyone else is in that boat.
zikronix sent me there for the fix...I believe he is adding it to the main thread but if it isn't there yet I wanted to add it now for anyone in my boat.
Again this method works and there is success.
Happy rooting
Hey thanx for this Linux guide. Does this steps work with the update 12.25.10 on the windows thread?
Will you update this guide?
My Xoom is rooted and running tiamat 1.41.
I'm trying to push a file onto the xoom and having trouble with it.
I have the Android SDK installed.
When I type ADB DEVICES, it shows my xoom listed as a long string of letters and numbers.
I figured out I could get into the shell by using ADB -s ###### shell (where #### is the numbers/letters shown as the device).
If I type remount, i get permission denied.
If I try to push a file onto the Xoom, I get permission denied.
What am I missing here and how do I mount the Xoom so that I can push files onto the it?
Anyone know where the libflashplayer.so goes? I have the official flash installed and don't see it in /system/lib
you have to cd into the directory where adb is. most people put it right on the root of there C drive so in terminal type "cd c:\android-sdk-windows\platform-tools" without quotes then type "adb remount" and you should be mounted
if you need more help with adb check out this guide http://androidsamurai.com/forum/viewtopic.php?f=12&t=4&sid=b8c229b771793d03bb84efbcf562e55b
I have tools and platform-tools directories in my PATH so I can run them from any directory. Even running it from the directory containing the executable fails with 'remount failed - operation not permitted'
you could try uninstalling and reinstalling android sdk
shobirama said:
If I type remount, i get permission denied.
If I try to push a file onto the Xoom, I get permission denied.
Click to expand...
Click to collapse
What does running "getprop ro.secure" say? (in adb shell/terminal on the tablet)
ydaraishy said:
What does running "getprop ro.secure" say? (in adb shell/terminal on the tablet)
Click to expand...
Click to collapse
Running getprop ro.secure in both adb shell and in terminal emulator on the tablet returns 1
shobirama said:
Running getprop ro.secure in both adb shell and in terminal emulator on the tablet returns 1
Click to expand...
Click to collapse
You're not in insecure mode. I thought flashing that kernel would put you into insecure mode? Maybe you need to reflash?
If you still actually have a working su binary, copy the file somewhere writeable, then su to root, then copy it from there again to the location.
I successfully received the OTA update, and was wondering if anyone wanted/needed a rooted nandroid.
I tried to do the requisite search before posting, (did not find a clear answer) - I'd love to make a CWM zip, but don't know how, but am in the midst of looking for the answer. Might try kitchen...
If I missed someone else's effort to do the same, kindly disregard.
Let me know, I'll get it up tonight. This is 2.3.6 and DOES NOT have CIQ.
hey can u dump the modem for me
I've got adb and kitchen setup on PC, but really have not tried to dabble until now. Got a reference for the modem dump that I can follow? If not I'll look how to do just the modem. Flashed radios via adb but never saved one from a device.
yes....turn on usb debugging in development. connect to your pc.....open cmd prompt.....navigate to the directory that has adb in it
---------- Post added at 10:17 PM ---------- Previous post was at 10:14 PM ----------
run these commands
adb shell dd if=/dev/block/mmcblk0p13 of=/sdcard/amss.bin
adb shell dd if=/dev/block/mmcblk0p17 of=/sdcard/mdm.bin
Thanks guys for doing this. Will there be two zip files: one for the UCLA3 baseband (radio) and one for GINGERBREAD.UCLA3 build? Or can they be combined into one flashable zip?
Sent from my SAMSUNG-SGH-I727 using XDA App
silver03wrx said:
yes....turn on usb debugging in development. connect to your pc.....open cmd prompt.....navigate to the directory that has adb in it
---------- Post added at 10:17 PM ---------- Previous post was at 10:14 PM ----------
run these commands
adb shell dd if=/dev/block/mmcblk0p13 of=/sdcard/amss.bin
adb shell dd if=/dev/block/mmcblk0p17 of=/sdcard/mdm.bin
Click to expand...
Click to collapse
I got a permission denied error, please see attached screenshot
opss lol sorry start over
type adb shell hit enter
type su hit enter
then run those commands
silver03wrx said:
opss lol sorry start over
type adb shell hit enter
type su hit enter
then run those commands
Click to expand...
Click to collapse
hmm, denied again, sreenshot attached
sob.. lol ok.
adb shell hit enter
su hit enter
then
mount -o remount,rw /dev/block/stl9 /system
then those commands
silver03wrx said:
sob.. lol ok.
adb shell hit enter
su hit enter
then
mount -o remount,rw /dev/block/stl9 /system
then those commands
Click to expand...
Click to collapse
Grrr, I'll keep trying. after entering "su" it seems to be thinking for about a min.
attached
superfire71 said:
Grrr, I'll keep trying. after entering "su" it seems to be thinking for about a min.
attached
Click to expand...
Click to collapse
if your phone is rooted, then make sure that on screen you allow SU permissions after typing su in the cmd prompt
unplug phone
plug back in
close the terminal..
reopen it
get to adb directory
adb start service
adb shell
su
Pirateghost said:
if your phone is rooted, then make sure that on screen you allow SU permissions after typing su in the cmd prompt
Click to expand...
Click to collapse
k, trying again, brb
lol dificult with out phone in hand
much closer, see attached. Now says "not found" when entering original commands. never mind the nonsense entered at the bottom
I did have to allow on phone screen when entering su, missed that originally
ok close the terminal
re open it
unplug phone
plug back in
adb start service
adb shell
su
dd if=/dev/block/mmcblk0p13 of=/sdcard/amss.bin
dd if=/dev/block/mmcblk0p17 of=/sdcard/mdm.bin
adb pull /sdcard/amss.bin
adb pull /sdcard/mdm.bin
superfire71 said:
much closer, see attached. Now says "not found" when entering original commands. never mind the nonsense entered at the bottom
I did have to allow on phone screen when entering su, missed that originally
Click to expand...
Click to collapse
once you are already IN adb shell, you dont enter the command adb shell...lol
adb shell
su
dd command
silver03wrx said:
ok close the terminal
re open it
unplug phone
plug back in
adb start service
adb shell
su
adb shell dd if=/dev/block/mmcblk0p13 of=/sdcard/amss.bin
adb shell dd if=/dev/block/mmcblk0p17 of=/sdcard/mdm.bin
adb pull /sdcard/amss.bin
adb pull /sdcard/mdm.bin
Click to expand...
Click to collapse
silver,
when IN adb shell, adb shell is bad command. just start it at dd
Pirateghost said:
once you are already IN adb shell, you dont enter the command adb shell...lol
adb shell
su
dd command
Click to expand...
Click to collapse
thank you sir
Ok guys, really close. see attached, setting up to do it again.
check your sd card
---------- Post added at 11:07 PM ---------- Previous post was at 11:07 PM ----------
i dont think you need to do adb pull for them after the first 2 commands
is that right pg?
So I wanted to install APK-Multi Tool to my PC. But in order to set it up it is required to have a"framework-res.apk" and a "SystemUI.apk", am I right?(Ι am not sure if I forget anything) But where to find them? Do they mean that I have to use these that I got in my phone? OK lets say yes... I have found the framework-res.apk which is located in my system/framework. But I really dont know what is going on... I cant find the systemUI.apk in system/app !
Any help is appreciated! Thanks!
Additional Device Info:
Phone Model:LG-E986 G Optimus Pro
Android Version: 4.1.2
Kernel Version: 3.4.0
Root: Yes
ROM: Stock
Recovery: Yes
The Proof: Here
You can install titanium backup and search for SystemUI.apk and make a backup of it !!!
Sent from my GT-S5360 Using tapatalk 2
PreSS ThanKs If i HelPeD YoU ?!?
D-J Mutant said:
So I wanted to install APK-Multi Tool to my PC. But in order to set it up it is requered to have a"framework-res.apk" and a "SystemUI.apk", am I right?(Ι am not sure if I forget anything) But where to find them? Do they mean that I have to use these that I got in my phone? OK lets say yes... I have found the framework-res.apk which is located in my system/framework. But I really dont know what is going on... I cant find the systemUI.apk in system/app !
Any help is appreciated! Thanks!
Click to expand...
Click to collapse
What version of android do you have?
androidrocks23 said:
You can install titanium backup and search for SystemUI.apk and make a backup of it !!!
Sent from my GT-S5360 Using tapatalk 2
PreSS ThanKs If i HelPeD YoU ?!?
Click to expand...
Click to collapse
No results?? --> http://imgur.com/jZ87lHA,KRlB4QY#0
Lgrootnoob said:
What version of android do you have?
Click to expand...
Click to collapse
I wrote some additional info for the device.
D-J Mutant said:
I wrote some additional info for the device.
Click to expand...
Click to collapse
Anomaly.
Ive had some hidden apks too but i've always been able to back them up.
huh? confused4life.
All i can say is try this:
Code:
ls -l -R /system > /sdcard/syslist.txt
ls -l -R /data > /sdcard/datalist.txt
post the datalist.txt and syslist.txt files here as attachments.
Lgrootnoob said:
Anomaly.
Ive had some hidden apks too but i've always been able to back them up.
huh? confused4life.
All i can say is try this:
Code:
ls -l -R /system > /sdcard/syslist.txt
ls -l -R /data > /sdcard/datalist.txt
post the datalist.txt and syslist.txt files here as attachments.
Click to expand...
Click to collapse
Confused? Lol! What do you have to say about this?
D-J Mutant said:
Confused? Lol! What do you have to say about this?
Click to expand...
Click to collapse
lol
You need to have a root shell first.
Try this in the terminal:
Code:
su
ls -l -R /system > /sdcard/syslist.txt
ls -l -R /data > /sdcard/datalist.txt
Lgrootnoob said:
lol
You need to have a root shell first.
Try this in the terminal:
Code:
su
ls -l -R /system > /sdcard/syslist.txt
ls -l -R /data > /sdcard/datalist.txt
Click to expand...
Click to collapse
Oh... Where can I find one? For the above commands I used Terminal Emulator which has Superuser permissions.
D-J Mutant said:
Oh... Where can I find one? For the above commands I used Terminal Emulator which has Superuser permissions.
Click to expand...
Click to collapse
You have type su then the console will go from $ to # meaning you have root perms.
In the picture you provided you definitely have a user shell as denoted by the $ prompt.
If you are unsure you can always type whoami and if that returns "uid 0" then you have root permissions on the current shell.
Just because the terminal emulator has the ability to become the superuser doesn't mean you are always the superuser when you run the app.
The app has to request su permissions so you have to use the su command.
I had updated the code I wanted you to type into the emulator that you were using.
Please use the new code:
Code:
su
ls -l -R /system > /sdcard/syslist.txt
ls -l -R /data > /sdcard/datalist.txt
Please run this code then upload the datalist.txt and syslist.txt files from the sdcard here as attachments.
Ohh yes you are right..I forgot it.I have so much time to use the terminal
Here you go :
~~~The attached files have been deleted.~~~
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?