need help from andriod pro - General Questions and Answers

i know its not the right section to post but i have very less post count
anyway my question
with ROOTED phone ,
I use this commands in adb :
adb shell dd if=/dev/zero of=/dev/block/sda1
adb shell dd if=/dev/zero of=/dev/block/sda2
adb shell dd if=/dev/zero of=/dev/block/sdd4
and works perfect
but I want something for UnROOTED phone
or is ther anything called temporary root?

Related

[Q] UCLA3 NANDRoid to flashable zip

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?

[REQUEST] [Dumps] [Evita-Utl] Need (hboot,misc partition,radio,adsp,wcnss) imgs

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

[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?

"write error: No space left on device" error fix

when im about to remove the modem files like this from adb menu
dd if=/dev/zero of=/dev/block/bootdevice/by-name/mdm1m9kefs1
dd if=/dev/zero of=/dev/block/bootdevice/by-name/mdm1m9kefs2
dd if=/dev/zero of=/dev/block/bootdevice/by-name/mdm1m9kefs3
dd if=/dev/zero of=/dev/block/bootdevice/by-name/mdm1m9kefsc
im getting "write error: No space left on device" error.
how to fix this. or is there any other way to delete those files.
Those commands will overwrite the named block-devices with zeroes, they don't get deleted means it's not technically erasing.
jwoegerbauer said:
Those commands will overwrite the named block-devices with zeroes, they don't get deleted means it's not technically erasing.
Click to expand...
Click to collapse
ok, so is there a way to overwrite them? cos atm i cant with those commands
To overwrite you have to specify as infile an image ( .img ) and as outfile the block-device wanted
jwoegerbauer said:
Look inside here:
dd: No Space Left on Device | Beamtic
After running dd for a long time, it stops with an error saying no space is left on the device.
beamtic.com
Click to expand...
Click to collapse
would it also be fixed when i format the device and wipe all data?
Raw34 said:
would it also be fixed when i format the device and wipe all data?
Click to expand...
Click to collapse
Re-read my altered post above yours.
jwoegerbauer said:
To overwrite you have to specify as infile an image ( .img ) and as outfile the block-device wanted
Click to expand...
Click to collapse
can u give me an example for the command for adb menu?
i want to get rid of this file mi10orj.bin in the modem
What ADB are you using? AFAIK ADB hasn't a menu,
If device is rooted then you may run
Code:
adb devices
adb shell "stop"
adb shell "rm -f /vendor/mi10orj.bin"
adb shell "start"
if the .bin-file is located in vendor partition what IDK
jwoegerbauer said:
What ADB are you using? AFAIK ADB hasn't a menu,
If device is rooted then you may run
Code:
adb devices
adb shell "stop"
adb shell "rm -f /vendor/mi10orj.bin"
adb shell "start"
if the .bin-file is located in vendor partition what IDK
Click to expand...
Click to collapse
its called "minimal adb and fastboot tool".
yes the device is rooted. im gonna try this commands when im done with my working.
thx so much for your help and insight, so far.

Question how to reset efs in poco x3 pro

hi
how can i reset EFS poco x3 pro ?
device is rooted and twrp installed
this is my code i run that in twrp for reset efs but device not coming up after running this :
adb shell ls -l /dev/block/bootdevice/by-name/
adb shell dd if=/dev/zero of=/dev/block/mmcblk0p46
adb shell dd if=/dev/zero of=/dev/block/mmcblk0p47
adb shell dd if=/dev/zero of=/dev/block/mmcblk0p45
adb shell dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1
adb shell dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2
adb shell dd if=/dev/zero of=/dev/block/bootdevice/by-name/fsg
adb shell dd if=/dev/zero of=/dev/block/bootdevice/by-name/fsc
adb shell reboot
Click to expand...
Click to collapse
I am also having the same issue with my poco m3. Have you fixed? Lets discuss... my telegram [email protected]_TEK
Just Read My Thread and Your Problem Will Be fixed
Download TWRP + EFS RESET tool From my thread Reqirement
I have explained all progress of this phone there
Link XDA
uncle.milad said:
hi
how can i reset EFS poco x3 pro ?
device is rooted and twrp installed
this is my code i run that in twrp for reset efs but device not coming up after running this :
Click to expand...
Click to collapse
When You Reset EFS Your Phone NV Data Goes Corrupt and When Reboots Each time You Power it
It Can Caused By two Problem
Firmware Security
RSA Encryption of IMEI
-------------
Read my Thread CareFully

Categories

Resources