Related
Without YOUR dump, there won't be any Gingerbread based mods or ROMs for your phone. SuperOneClick doesn't work on the Rogers Infuse, but we do have a method to root. If you have a shiny new Rogers Infuse in hand, please join the #Infuse4G irc channel so we can work with you to obtain the necessary dumps. You'll need to connect using an irc client like xchat.
How to set up adb
If you don't already have adb working on your computer, you'll need to set it up. First download and install the Java JDK. Then download and extract the Android SDK. In the unzipped folder, open "SDK Manager.exe". A prompt should come up with a list of items to install. I recommend rejecting everything except "Google USB driver package", "Android SDK Tools", and "Android SDK Platform-tools". Once those are installed, you're ready. Most people add adb to their path as well for easier access, but you can do that later.
Commands used to dump the required data
Code:
dd if=/dev/block/bml1 of=/sdcard/boot.bin bs=512
dd if=/dev/block/bml2 of=/sdcard/infuse_gb.pit bs=4096
dd if=/dev/block/bml4 of=/sdcard/Sbl.bin bs=512
[COLOR="Red"]dd if=/dev/block/bml5 of=/sdcard/recovery.bin bs=512 (we still need this one)[/COLOR]
dd if=/dev/block/stl6 of=/sdcard/param.lfs bs=4096
dd if=/dev/block/bml7 of=/sdcard/zImage bs=4096
dd if=/dev/block/stl9 of=/sdcard/factoryfs.rfs bs=4096
dd if=/dev/block/stl10 of=/sdcard/dbdata.rfs bs=4096
dd if=/dev/block/stl11 of=/sdcard/cache.rfs bs=4096
dd if=/dev/block/bml12 of=/sdcard/modem.bin bs=4096
hope someone gets this info to you soon, I want gingerbread!!!!
When is the canadians getting it
Sent from my SAMSUNG-SGH-I997 using XDA Premium App
Like GTG said, its really easy. Also if you have MAC or Linux , please just PM one of the Dev's and we can walk you through it. Its easy and you will be helping alot of people out.
Awesome!
10char
Our Canadian friends can do it!
Sent from my SAMSUNG-SGH-I997 using XDA App
Nopcodex90 said:
Like GTG said, its really easy. Also if you have MAC or Linux , please just PM one of the Dev's and we can walk you through it. Its easy and you will be helping alot of people out.
Click to expand...
Click to collapse
"So easy even a Canadian can do it!" - Best tagline ever.
Surely you could've come up with a better title for this post...
SolusCado said:
Surely you could've come up with a better title for this post...
Click to expand...
Click to collapse
Hmm... probably not. Suggestions?
gtg465x said:
Hmm... probably not. Suggestions?
Click to expand...
Click to collapse
I like the title
gtg465x said:
Hmm... probably not. Suggestions?
Click to expand...
Click to collapse
Take a dump and send it to me quickly?
at first i thought it was an actual tutorial on how to take a dump
I live in Minnesota. If I had enough spare time I'd just drive to Canada to try and get one
LOL. I thought you was supposed to leave them. I guess it only matters that "the dump" happens though.
gtg465x said:
Without YOUR dump, there won't be any Gingerbread based mods or ROMs for your phone. Alright, let's get started. It's not that hard.
1) First you will need to root your device. SuperOneClick should work.
2) If you don't already have adb working on your computer, you'll need to set it up. First download and install the Java JDK. Then download and extract the Android SDK. In the unzipped folder, open "SDK Manager.exe". A prompt should come up with a list of items to install. I recommend rejecting everything except "Google USB driver package", "Android SDK Tools", and "Android SDK Platform-tools". Once those are installed, you're ready. Most people add adb to their path as well for easier access, but you can do that later.
3) On your now rooted phone, go to Settings > Applications > Development and turn on USB debugging. After you do that, plug your phone in to your computer.
4) Now open a command prompt on your computer and cd to your "android-sdk-windows\platform-tools" directory. This will allow you to run adb without adding it to your path.
5) In the command prompt, type "adb devices" without quotes to make sure your phone is connected properly. If it is, it should be listed in the command prompt.
6) Now copy and paste the following commands into the command prompt and wait for each one to finish after pressing enter. Some of the commands will take a little while to run.
Code:
adb shell
su
A Superuser prompt should now pop up on your phone that you need to accept. You should see # instead of $ in the command prompt now. Continue on.
Code:
dd if=/dev/block/bml1 of=/sdcard/boot.bin bs=4096
dd if=/dev/block/bml2 of=/sdcard/infuse_gb.pit bs=4096
dd if=/dev/block/bml4 of=/sdcard/Sbl.bin bs=4096
dd if=/dev/block/stl6 of=/sdcard/param.lfs bs=4096
dd if=/dev/block/bml7 of=/sdcard/zImage bs=4096
dd if=/dev/block/stl9 of=/sdcard/factoryfs.rfs bs=4096
dd if=/dev/block/stl10 of=/sdcard/dbdata.rfs bs=4096
dd if=/dev/block/stl11 of=/sdcard/cache.rfs bs=4096
dd if=/dev/block/bml12 of=/sdcard/modem.bin bs=4096
exit
exit
7) Connect the phone to your computer as a mass storage device.
8) Copy all 9 files we just created from your internal SD card to your computer.
9) Zip those suckers up, post the zip to MultiUpload or something, and link us to it. You're done!
If you need further assistance, please join the #Infuse4G channel at http://webchat.freenode.net/
If anyone thinks of anything else I should add to the guide or if anything needs correcting, let me know.
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I997 using XDA App
I think the post needs more detail on how to flush the dump your way.
And Canadians - gtg will be perfectly happy to hold your hand through the process of taking your dump.
Entropy512 said:
I think the post needs more detail on how to flush the dump your way.
And Canadians - gtg will be perfectly happy to hold your hand through the process of taking your dump.
Click to expand...
Click to collapse
Lol what a nice guy lol come on Canadians dump already
Sent from my SAMSUNG-SGH-I997 using XDA Premium App
Entropy512 said:
I think the post needs more detail on how to flush the dump your way.
And Canadians - gtg will be perfectly happy to hold your hand through the process of taking your dump.
Click to expand...
Click to collapse
Hell I'd pull it out myself if I were there with you.
Is it "actually" officially for sale at Rogers now?
ookba said:
Is it "actually" officially for sale at Rogers now?
Click to expand...
Click to collapse
nope.. not yet
link to rogers' samsung devices running android. no infuse yet
http://www.rogers.com/web/link/wire...lan&productType=normal&N=52+11+277+4294966826
Hey
Please can anyone have 'Evita-Utl' (Middle eastern variant) help me by dumping (hboot,misc partition,radio,adsp,wcnss) imgs from his working device .. and here is how:
1)first you must get into recovery(cwm) because img token from booted device is useless for me
2)then while you are in cwm recovery connect to pc and adb
Code:
adb shell
dd if=/dev/block/mmcblk0p12 of=/sdcard/hboot.img
exit
adb pull /sdcard/hboot.img
adb shell
dd if=/dev/block/mmcblk0p23 of=/sdcard/misc.img
exit
adb pull /sdcard/misc.img
adb shell
dd if=/dev/block/mmcblk0p17 of=/sdcard/radio.img
exit
adb pull /sdcard/radio.img
adb shell
dd if=/dev/block/mmcblk0p18 of=/sdcard/adsp.img
exit
adb pull /sdcard/adsp.img
adb shell
dd if=/dev/block/mmcblk0p19 of=/sdcard/wcnss.img
exit
adb pull /sdcard/wcnss.img
and upload these 5 files from your sdcard .. I will be grateful
Thanks for help
Why?
tjhooker73 said:
Why?
Click to expand...
Click to collapse
Do you have the middle eastern variant?
Sent from my Evita
tjhooker73 said:
Why?
Click to expand...
Click to collapse
timmaaa said:
Do you have the middle eastern variant?
Sent from my Evita
Click to expand...
Click to collapse
Someone in other thread tell that middle east version(ul flashed) can be fixed by those 3 blocks and radio block ofcours .. but do you have any suggestions for recover my misc partition .. if I was lucky and someone upload it to me .. do you think that adb can restore it ??
dr.scofield said:
Someone in other thread tell that middle east version(ul flashed) can be fixed by those 3 blocks and radio block ofcours .. but do you have any suggestions for recover my misc partition .. if I was lucky and someone upload it to me .. do you think that adb can restore it ??
Click to expand...
Click to collapse
What's wrong with your phone?
Need the imgs because no firmwares or ruu fo this phone .. and my utl flashed ul and bricked .. then relifed with evita-ul dll because no dll for it .. so since there no firmwares for it and I replaced mine .. I need it from any working phone by dumping it .. if you can help
Anyone??
Sent from my HTC One XL using XDA Premium 4 mobile app
dr.scofield said:
Anyone??
Click to expand...
Click to collapse
I upload these 5 files on my google drive
But I can't post the link
Send me you contact at "sladefoto" a t gmail
Sladefoto said:
I upload these 5 files on my google drive
But I can't post the link
Send me you contact at "sladefoto" a t gmail
Click to expand...
Click to collapse
Thanks .. i've managed these files and fixed this phone
dr.scofield said:
Hey
Please can anyone have 'Evita-Utl' (Middle eastern variant) help me by dumping (hboot,misc partition,radio,adsp,wcnss) imgs from his working device .. and here is how:
1)first you must get into recovery(cwm) because img token from booted device is useless for me
2)then while you are in cwm recovery connect to pc and adb
Code:
adb shell
dd if=/dev/block/mmcblk0p12 of=/sdcard/hboot.img
exit
adb pull /sdcard/hboot.img
adb shell
dd if=/dev/block/mmcblk0p23 of=/sdcard/misc.img
exit
adb pull /sdcard/misc.img
adb shell
dd if=/dev/block/mmcblk0p17 of=/sdcard/radio.img
exit
adb pull /sdcard/radio.img
adb shell
dd if=/dev/block/mmcblk0p18 of=/sdcard/adsp.img
exit
adb pull /sdcard/adsp.img
adb shell
dd if=/dev/block/mmcblk0p19 of=/sdcard/wcnss.img
exit
adb pull /sdcard/wcnss.img
and upload these 5 files from your sdcard .. I will be grateful
Thanks for help
Click to expand...
Click to collapse
i have same problem and still my device (no service )not antenna after jtag with riff box
my device one xl (evita utl pj83500) s-off and super cid
i dumped this 5 files but i dont know how to solve my problem and flash misc.radio and hboot files ==> when i write fastboot flash radio radio.img say error : not allowed
how to eng-s-off this model to flash radio.img and hboot.img
pls help
How did you flash them?
I have the same problem but I don't know how to flash the partitions.
Thread Cleaned, there is no "trading", "selling" for device files or anything of that sort, of funds or gifts, as per Forum Rules.
dr.scofield said:
Hey
Please can anyone have 'Evita-Utl' (Middle eastern variant) help me by dumping (hboot,misc partition,radio,adsp,wcnss) imgs from his working device .. and here is how:
1)first you must get into recovery(cwm) because img token from booted device is useless for me
2)then while you are in cwm recovery connect to pc and adb
Code:
adb shell
dd if=/dev/block/mmcblk0p12 of=/sdcard/hboot.img
exit
adb pull /sdcard/hboot.img
adb shell
dd if=/dev/block/mmcblk0p23 of=/sdcard/misc.img
exit
adb pull /sdcard/misc.img
adb shell
dd if=/dev/block/mmcblk0p17 of=/sdcard/radio.img
exit
adb pull /sdcard/radio.img
adb shell
dd if=/dev/block/mmcblk0p18 of=/sdcard/adsp.img
exit
adb pull /sdcard/adsp.img
adb shell
dd if=/dev/block/mmcblk0p19 of=/sdcard/wcnss.img
exit
adb pull /sdcard/wcnss.img
and upload these 5 files from your sdcard .. I will be grateful
Thanks for help
Click to expand...
Click to collapse
thanks god, could you tell me how did you do with 5 files, please share? we have the same problems, hope you help us? pls!
vincent844 said:
thanks god, could you tell me how did you do with 5 files, please share? we have the same problems, hope you help us? pls!
Click to expand...
Click to collapse
Do you have these 5 files If yes please please send them to me [email protected]
u will send for evita UTL?
and u have all the 5 files?
Hboot.img
Misc.img
Radio.img
Adsp.img
Wcnss.img
Can you send me these files please
I will also help you to flash them but please send them to me
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?
They do not detect the device. If you have a working phone, you can make a debrick image for me. Please install busybox and a terminal emulator. Then issue this command from the terminal and you will get the debrick image in your sd card.
su
busybox dd if=/dev/block/mmcblk0 of=/sdcard/debrick.img bs=1M count=128
Make sure you have SCH-I925vzw and android version 4.1.2 or the image will not work for me.
Please upload
Thanks
Guys help me, make debrick image
Hello guys, so now my mi4c is unlocked bootloader i want to backup first imei/nvram/efs partition before start to flashing twrp, since on my device before my imei gone after flashing twrp already restore from twrp backup/qpst tool/fastboot rom flash but still nothing work.
From now my local store refund the money since they cant fix it too and then i bought new one.
So, how i can backup those files directly from phone with root permission like terminal emulator or something?
Anyone can give me command for it..
Thanks. :fingers-crossed:
I'm searching over google and miui forum and find this thread on russian forum but its for minote pro does it same?
Correct me if i'm wrong please..
Take look link below
http://4pda.ru/forum/index.php?s=&showtopic=668750&view=findpost&p=45923244
http://4pda.ru/forum/index.php?s=&showtopic=657190&view=findpost&p=39377526
Might be usefull for everyone too before facing problem with imei.
bump
@ketut.kumajaya I need your advice please :crying:
Which is partition block number used on mi4c?
Degrinder said:
bump
@ketut.kumajaya I need your advice please :crying:
Which is partition block number used on mi4c?
Click to expand...
Click to collapse
https://github.com/kumajaya/android...-13.0-twrp/recovery/root/etc/twrp.fstab#L7-L8
You can use busybox's dd command:
Code:
busybox dd if=/dev/block/bootdevice/by-name/modemst1 of=/sdcard/modemst1.img bs=4096
busybox dd if=/dev/block/bootdevice/by-name/modemst2 of=/sdcard/modemst2.img bs=4096
Be careful with above commands.
ketut.kumajaya said:
https://github.com/kumajaya/android...-13.0-twrp/recovery/root/etc/twrp.fstab#L7-L8
You can use busybox's dd command:
Code:
busybox dd if=/dev/block/bootdevice/by-name/modemst1 of=/sdcard/modemst1.img bs=4096
busybox dd if=/dev/block/bootdevice/by-name/modemst2 of=/sdcard/modemst2.img bs=4096
Be careful with above commands.
Click to expand...
Click to collapse
I'm sorry but for me its new things for linux command so i dont know much about it :laugh:
And i'm affraid if my device got bricked too
Need to instal busybox first or i can do it instantly with terminal emulator?
Degrinder said:
I'm sorry but for me its new things for linux command so i dont know much about it :laugh:
And i'm affraid if my device got bricked too
Need to instal busybox first or i can do it instantly with terminal emulator?
Click to expand...
Click to collapse
Maybe yes, I'm not sure if 4c have a proper busybox binary preinstalled.
ketut.kumajaya said:
Maybe yes, I'm not sure if 4c have a proper busybox binary preinstalled.
Click to expand...
Click to collapse
So, which do you think is better using backup from this command or using 3rd apps like Partitions Backup & Restore(select raw .img files) ?
i thought that was crap that only happened with cheap mediatek based phones,
I've never made any backup of EFS on any phone...
#xiaomiMi4c