Related
I run the following commands
su
adb shell
daemon not running, starting it now on port 5038
daemon started successfully
error: device not found.
any suggestions?
Replug usb cable after adb daemon start on PC or try to get adb when phone in CWM...
scott0 said:
I run the following commands
su
adb shell
daemon not running, starting it now on port 5038
daemon started successfully
error: device not found.
any suggestions?
Click to expand...
Click to collapse
Er... you're running adb _inside_ the phone?
aremcee said:
Er... you're running adb _inside_ the phone?
Click to expand...
Click to collapse
i'm guessing that's the issue.
scott0 said:
i'm guessing that's the issue.
Click to expand...
Click to collapse
ADB is used to connect to android devices. So unless you have another android plugged to your P930, running adb on the phone is pointless
hey thanks.
i guess i am way off track, i want to restore the phone's original recovery image (at some point in the future) and am tired of dealing with adb/windows on my PCs.
i was under the impression this could be done via terminal emulator/adb.
scott0 said:
hey thanks.
i guess i am way off track, i want to restore the phone's original recovery image (at some point in the future) and am tired of dealing with adb/windows on my PCs.
i was under the impression this could be done via terminal emulator/adb.
Click to expand...
Click to collapse
Well... yes, you need adb to connect to the phone, but terminal emulator is already running on the phone.
i see, well, i was hoping to be able to temporarily go back to the stock recovery to do OTA updates and such, it appears it won't be as cut&dry as i was hoping. i assumed that since adb is installed and running on the device via terminal emulator that it could be used to push/pull the stock recovery image onto the phone.
scott0 said:
i see, well, i was hoping to be able to temporarily go back to the stock recovery to do OTA updates and such, it appears it won't be as cut&dry as i was hoping. i assumed that since adb is installed and running on the device via terminal emulator that it could be used to push/pull the stock recovery image onto the phone.
Click to expand...
Click to collapse
You're still not getting it: The only purpose of "adb shell" is to connect you to the phone; terminal emulator is a direct shell already on the phone.
i simply want to flash the original recovery image to the phone without using a PC.
it was my understanding that this is possible via terminal emulator, does anyone know if this is possible and if so, could you point me in the right direction to learn how to do that?
thanks!
scott0 said:
i simply want to flash the original recovery image to the phone without using a PC.
it was my understanding that this is possible via terminal emulator, does anyone know if this is possible and if so, could you point me in the right direction to learn how to do that?
thanks!
Click to expand...
Click to collapse
Just use Terminal emulator in your phone and add manually the following commands to flash original images (put them on sd-card before):
Code:
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p13
dd if=/sdcard/firmware.img of=/dev/block/mmcblk0p1
dd if=/sdcard/baseband.img of=/dev/block/mmcblk0p14
dd if=/sdcard/system.img of=/dev/block/mmcblk0p27
super, thank you Machzelet!
i will give that a whirl this weekend.
here's how i think it will go
images to sd card
restore backed up original rom va rom manager
open up terminal emulator, run the commands above
reboot
update with OTA update
easy breezy?
Why would you even bother updating? The changes in the OTA update will eventually appear in custom ROMs anyway.
do i rly need to provide a reason for wanting to fiddle around with my phone? on a dev board? lolz
I have seen several of threads asking about how to recover data from a phone that has a broken display.
Backing up a phone with broken display
Prerequisites
Rooted phone with broken display/digitizer/etc. Display is nonfunctional for whatever reason.
ADB for your platform. Downloads for Windows, Mac, and Linux can be found at my dev-host.
Drivers installed (Windows), rules file set up (Linux + Mac). Drivers for windows can be found here. Rules file for Linux can be found here.
Recovery file attached to this post. (twrp.img)
External sdcard with at least 2 GB free space inserted in your broken phone.
openrecoveryscript.txt file attached to this post.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Backing up your broken device
Extract the ADB zip somewhere convenient.
Move the twrp.img recovery file into the ADB extracted directory.
Move the openrecoveryscript.txt file into the ADB directory.
Open a command prompt / terminal window in the ADB directory.
Windows: Windows Key + R => Type in "cmd" then click "RUN".
Linux: Open a terminal window by selecting it from your applications.
ALL:
Code:
cd /path/to/ADB/directory
Pull the battery from your phone, place it back in and boot into recovery (VolUp + Home + Power).
Connect your phone to your computer
Make sure that the following command returns "XXXXXX recovery" before proceeding to the next step.
Code:
./adb devices
Expected output:
Code:
List of devices attached
XXXXXXX recovery
Now to install TWRP recovery to your device. Type the following commands ( after each line). Linux users: Make sure you prepend each command with "./", as in "./adb ...". ALL Make sure you type the commands in CAREFULLY.
Code:
adb push twrp.img /tmp/twrp.img
adb shell dd if=/tmp/twrp.img of=/dev/block/mmcblk0p18
Wait until the last command above returns an output similar to below before proceeding to the next step:
Code:
12916+0 records in
12916+0 records out
6612992 bytes (6.3MB) copied, 1.094278 seconds, 5.8MB/s
Now pull your phones battery and reboot into recovery once again.
Run the following command to make sure your phone has booted into recovery completely.
Code:
adb devices
Expected output
Code:
List of devices attached
XXXXXXX recovery
Type the following to set up a script that will backup your phone to your external sdcard.
Code:
adb push openrecoveryscript.txt /cache/recovery/openrecoveryscript
Reboot your phone once more. This time, TWRP will begin backing up your ROM.
Wait for the backup to finish. You will know it is finished when you feel your phone reboot once more.
Optionally, you can check the state of your backup by running the following command and reading the last couple lines of it's output.
Code:
adb shell cat /tmp/recovery.log
Click to expand...
Click to collapse
Click to expand...
Click to collapse
That's it! Your entire system (/system, /data, /cache, and boot) will be backed up to your external sdcard. Just pop the sdcard in your replacement phone and you're good to go.
Enjoy and donate to the TWRP devs! This would not be possible if TWRP did not use the OpenRecoveryScript scripting engine!
Or you can use skip's unified toolkit.
I literally just used it. Moving the backup to my new device right now.
loserskater said:
Or you can use skip's unified toolkit.
I literally just used it. Moving the backup to my new device right now.
Click to expand...
Click to collapse
Whatever floats your boat :good:
Sorry, had to
Sent from my SGH-I747 using Tapatalk 2
Actually, this process might directly meet my needs.
You mentioned that the recovery image and script were attached to the initial post, though I must be missing something in that I don't see where they might be. Perhaps you could offer a pointer, please?
- ooofest
Ah sorry, you can find the files here
http://forum.xda-developers.com/showthread.php?t=2353828
Don't use the twrp.img from there though...go to the twrp website and download the latest .img file for your phone (d2att)
Sent from my S3 on Sense 5 (you jelly?)
CNexus said:
Ah sorry, you can find the files here
http://forum.xda-developers.com/showthread.php?t=2353828
Don't use the twrp.img from there though...go to the twrp website and download the latest .img file for your phone (d2att)
Click to expand...
Click to collapse
Thanks - I downloaded the appropriate files, but wonder if this can be used on a stock phone.
That is, I was able to push twrp.img to /tmp/twrp.img, but cannot write in the next step:
Code:
adb shell dd if=/tmp/twrp.img of=/dev/block/mmcblk0p18
/dev/block/mmcblk0p18: cannot open for write: Permission denied
This is a stock AT&T phone, in recovery mode, never been rooted.
- ooofest
You need to be rooted for this to work.
CNexus said:
You need to be rooted for this to work.
Click to expand...
Click to collapse
Ya know . . . I need to read things more carefully. Was so excited to see something that might possibly help. Sorry about that.
It's been awhile since I looked into rooting the Galaxy S III and will look around, but don't recall that this can be rooted from recovery, unfortunately. And, it seems that USB Debugging is not turned on when it boots to the lockscreen.
Hm.
- ooofest
Afternoon all,
My G4 has hit the bootloop for the last few days. Periodically, it has powered up to the main screen, but not for long enough for me to recover data.
I just spoke to a data recovery place that told me that if I can put my phone into download mode, they can recover the data. Lo and behold, my phone is currently next to me in download mode!
I'm quite keen to avoid dropping that amount of money if possible, so does anyone know of a way to recover the internal memory of the phone via download mode?
Apologies if I'm duplicating a previous thread - I had a quick look, but couldn't see any with the same issue.
Probably when the phone is in download mode they can copy the partitions bit by bit then try to do data recovery from those partition images.
So if the phone doesn't boot, it doesn't mean the data partition is corrupted so in theory you could try to copy the data partition and mount it and see what files you can recover.
I do not know the exact commands to dump the data partition but I think that's the way it can be done.
Anyone else willing to give a hand here?
Thanks for the help so far. I believe the data is intact - when the phone starts up, the data is all there. It's just accessing it that is the issue.
Sent from my Nexus 5 using Tapatalk
something similar to
Code:
dd if=/dev/block/mmcblk0p55 bs=8192 skip=65536 count=548352 of=/mnt/media_rw/external_SD/data.img
OR
Code:
dd if=/dev/block/mmcblk0p55 bs=8192 skip=65536 count=548352 of=/dev/block/mmcblk1/data.img
don't quote me on that but in theory this should work...
make SURE you have a 32gb SDCard in the phone first
Where would that command be entered mate? Sorry, only ever used my phone stock before.
Sent from my Nexus 5 using Tapatalk
I thought the OP title said download mode?
Use the LG Root method as if you were going to root..
I'm mobile ATM but if I remember correctly...
Send_Command \\.\Com# [# meaning your com port number]
Then insert that command.
Tomorrow at work I can get a common list of partition names and the command to back it up with.
je2854 said:
I thought the OP title said download mode?
Use the LG Root method as if you were going to root..
I'm mobile ATM but if I remember correctly...
Send_Command \\.\Com# [# meaning your com port number]
Then insert that command.
Tomorrow at work I can get a common list of partition names and the command to back it up with.
Click to expand...
Click to collapse
You need to mount the partition first.
Also, you could mount data if it is not encrypted (is it?)
Do this:
Code:
mkdir /temp
mkdir /temp/sd /temp/data
mount /dev/block/mmcblk1p1 /temp/sd
mount /dev/block/bootdevice/by-name/userdata /temp/data
mkdir /temp/sd/recoverydata
cp -R /temp/data/media/ /temp/sd/recoverydata/
A little tip that should work :
Take the battery off your phone
Put both phone and battery in the fridge
Wait till the phone is cold and boot the device.
The bootloop trouble is due to an abnormal warm so this way you can have a one shot normal boot to backup your data before send for warranty.
terisse said:
A little tip that should work :
Take the battery off your phone
Put both phone and battery in the fridge
Wait till the phone is cold and boot the device.
The bootloop trouble is due to an abnormal warm so this way you can have a one shot normal boot to backup your data before send for warranty.
Click to expand...
Click to collapse
If you try this, please put the phone in a ziploc bag 1st and seal it so humidity won't get inside the phone while in the fridge.
nagalun said:
You need to mount the partition first.
Also, you could mount data if it is not encrypted (is it?)
Do this:
Code:
mkdir /temp/sd /temp/data
mount /dev/block/mmcblk1p1 /temp/sd
mount /dev/block/bootdevice/by-name/userdata /temp/data
mkdir /temp/sd/recoverydata
cp -R /temp/data/media/ /temp/sd/recoverydata/
Click to expand...
Click to collapse
just a question though... How can you use this command if it will not boot?
---------- Post added at 08:59 AM ---------- Previous post was at 08:50 AM ----------
to get into download mode do the following...
Pull Battery
Hold Volume Up
Plug in USB Cable (make sure it's plugged in the computer)
Release button after 5 seconds
follow the link to grab the files needed for "Send_Command"
Grab LG Root here
once you are in the mode and you followed directions you can copy the command I wrote
above to copy your data partition. The reason you must have a 32gb+ SDCard is you will
be making an exact copy of the /data partition where you can remove the SDCard and recover
whatever is needed.
je2854 said:
just a question though... How can you use this command if it will not boot?
Click to expand...
Click to collapse
Hmm... With the Send_Command.............? dd is a command too :silly:
nagalun said:
Hmm... With the Send_Command.............? dd is a command too :silly:
Click to expand...
Click to collapse
there is no need to mount the partition first..
the dd command will copy the partition as a RAW image.
you must then take it to a computer and mount it as an EXT4 or use it with ext2explore
je2854 said:
there is no need to mount the partition first..
the dd command will copy the partition as a RAW image.
you must then take it to a computer and mount it as an EXT4 or use it with ext2explore
Click to expand...
Click to collapse
in that case the command you have given him will copy 4492 mb only.
Here is why:
Code:
dd if=/dev/block/mmcblk0p55 bs=8192 skip=65536 count=548352 of=/dev/block/mmcblk1/data.img
input_file=(some partition) block_size=8192 skip_this_much_data=65536 how_many_data=548352 output_file=(somewhere)
actual data copied is 8192 * 548352 = 4492099584 bytes, and you are skipping some data from the beggining with 'skip'
you do still need to mount the sdcard, the "mmcblk1" is not treated as a directory, and it is very unlikely the sd card is mounted automatically in download mode.
nagalun said:
in that case the command you have given him will copy 4492 mb only.
Click to expand...
Click to collapse
remember me saying (if you read) above that I said "something similar to"
Hi all. Firstly, thanks for all your responses!
I've not got much of a clue what I'm doing unfortunately, I've never really messed with Android before - I'm typically fairly computer literate, but I've steered clear of messing with and rooting phones for the most part.
So to clarify, I've downloaded LG Root, Running either of the exes just leads to a cmd box that's open for about a second before closing, so I'm presuming I've missed a step. Is there a guide already in existence on how to use it?
But once in, ensure there's a sizeable Micro SD card in (it's a 64gb so I should be okay!) and use the send_command exe to send:
Code:
mkdir /temp/sd /temp/data
mount /dev/block/mmcblk1p1 /temp/sd
mount /dev/block/bootdevice/by-name/userdata /temp/data
mkdir /temp/sd/recoverydata
cp -R /temp/data/media/ /temp/sd/recoverydata/
And then the entire image should be on the Micro SD card.
How would I then mount the data image to be readable? I've only used .iso for mounting before.
Apologies for my ignorance - I'm probably making helping me quite difficult!
Sorry all, correction to my previous:- Do I basically follow http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772
And replace step 10 with the above command?
Shift+Right Click the folder you extracted "open command prompt here" for starters...
Run ports.bat first...
It'll tell you your DIAG and communication port...
The second com port is the one you are looking for.
Send_Command \\.\Com"#" (don't insert quotes, # being the number you found)
je2854 said:
Shift+Right Click the folder you extracted "open command prompt here" for starters...
Run ports.bat first...
It'll tell you your DIAG and communication port...
The second com port is the one you are looking for.
Send_Command \\.\Com"#" (don't insert quotes, # being the number you found)
Click to expand...
Click to collapse
I'm having the same issue and actually tried this earlier today. Ports.bat didn't show a DIAG communication port even when I had the phone stably sitting in Download Mode.
Going to try the freezer trick. I already bought a Nexus 6P, just want to unlock the locked content on my SD card. lol.
EDIT: Holy crap! It worked. I chilled it in a baggie, then stood in front of the freezer as I unlocked all of my locked gallery files (1,411 files totaling 900MB). As soon as I was done, 30 seconds after stepping away from the freezer, it started to bootloop again.
Got the only information I needed off my phone...nice! I might give it another go tomorrow and see if I can't run ROM Toolbox and backup all my apps so it'll be easier to push to my N6P.
Awesome suggestion!
IlyaKol said:
I'm having the same issue and actually tried this earlier today. Ports.bat didn't show a DIAG communication port even when I had the phone stably sitting in Download Mode.
Going to try the freezer trick. I already bought a Nexus 6P, just want to unlock the locked content on my SD card. lol.
EDIT: Holy crap! It worked. I chilled it in a baggie, then stood in front of the freezer as I unlocked all of my locked gallery files (1,411 files totaling 900MB). As soon as I was done, 30 seconds after stepping away from the freezer, it started to bootloop again.
Got the only information I needed off my phone...nice! I might give it another go tomorrow and see if I can't run ROM Toolbox and backup all my apps so it'll be easier to push to my N6P.
Awesome suggestion!
Click to expand...
Click to collapse
Mine will only get to optimising Apps, even if still in the freezer.
Sent from my Nexus 5 using Tapatalk
Hi all, sorry for the double posting, but just to make certain before I do something that will accidentally brick my phone. I'm intending to do the following:
Put phone in download mode and connect device.
Open LG_Root folder
Run a command window in LG_Root
Code:
Send_Command.exe \\.\Com4
Then, line by line, command:
Code:
mkdir /temp/sd /temp/data
mount /dev/block/mmcblk1p1 /temp/sd
mount /dev/block/bootdevice/by-name/userdata /temp/data
mkdir /temp/sd/recoverydata
cp -R /temp/data/media/ /temp/sd/recoverydata/
Once I've done all this, what happens next? Will I see responses on the screen etc?
Again, I apologise for the probably stupid questions. I don't want to brick my phone and lose all of the data, but I'm going away with work so would like to square it before I go if I can.
Many thanks to you all so far.
Can anybody give me 'mmcblk0.img' file for htc 10(2ps6500/2ps6500). if the phone is rooted and busybox installed it can be extracted using adb command.
To view partition tables :
adb shell su -c ls -al /dev/block/
After running this you can see this partition mmcblk0 in starting and make sure that the partition is available.
First you have to backup your file.
To backup into internal memory run this command:
adb shell su -c dd if=/dev/block/mmcblk0 of=storage/sdcard0/fulldump.img
or
To backup into external memory runthis command:
adb shell su -c dd if=/dev/block/mmcblk0 of=storage/sdcard1/fulldump.img
the file is supposed to be in GBs, so copy the file in pc, make a zip/winrar archive and upload it.
It would be a great help for me as I'm stuck with a bricked device. Thanks in advance
Capturing it now. I'm on the October 2017 unlocked firmware/ROM (RUU_PERFUME_WL_N70_SENSE80GP_VZW_MR_NA_Gen_Unlock_2.51.617.21). The command I needed to use was
Code:
adb shell su -c dd if=/dev/block/mmcblk0 of=storage/emulated/0/fulldump.img
Code:
adb shell su -c dd if=/dev/block/mmcblk0 of=sdcard/fulldump.img
might've worked, too. I'll let you know when it's uploaded.
Edit: Filled up the 19 GB free space on internal. Let me try to external SD.
Likewise, the command for external SD on this device is:
Code:
adb shell su -c dd if=/dev/block/mmcblk0 of=storage/ext_sd/fulldump.img
Yikes, 29GB but done. And hopefully it will compress a ton in order to upload somewhere. I'll 7-Zip it with maximum settings and see how well it compresses before I figure out where to upload it to. I don't know if I'd be able to upload something that large anywhere - I could ask AFH if it would be cool, even if it's just temporary. Guess we could always try a torrent if you're familiar with downloading torrents. I'll let you know how it compresses. It'll take at least a couple of hours to compress. Right now it's averaging 28% so it'll be less than 10 GB, I think, which is still huge.
roirraW "edor" ehT said:
Capturing it now. I'm on the October 2017 unlocked firmware/ROM (RUU_PERFUME_WL_N70_SENSE80GP_VZW_MR_NA_Gen_Unlock_2.51.617.21). The command I needed to use was
Code:
adb shell su -c dd if=/dev/block/mmcblk0 of=storage/emulated/0/fulldump.img
Code:
adb shell su -c dd if=/dev/block/mmcblk0 of=sdcard/fulldump.img
might've worked, too. I'll let you know when it's uploaded.
Edit: Filled up the 19 GB free space on internal. Let me try to external SD.
Likewise, the command for external SD on this device is:
Code:
adb shell su -c dd if=/dev/block/mmcblk0 of=storage/ext_sd/fulldump.img
Yikes, 29GB but done. And hopefully it will compress a ton in order to upload somewhere. I'll 7-Zip it with maximum settings and see how well it compresses before I figure out where to upload it to. I don't know if I'd be able to upload something that large anywhere - I could ask AFH if it would be cool, even if it's just temporary. Guess we could always try a torrent if you're familiar with downloading torrents. I'll let you know how it compresses. It'll take at least a couple of hours to compress. Right now it's averaging 28% so it'll be less than 10 GB, I think, which is still huge.
Click to expand...
Click to collapse
You do realize this will give ALL of the info from every partition on your phone, correct? Including IMEI, serial#, and any and all data you have on it?
xunholyx said:
You do realize this will give ALL of the info from every partition on your phone, correct? Including IMEI, serial#, and any and all data you have on it?
Click to expand...
Click to collapse
No, I sure didn't. Thank you! I wondered but in my searches I didn't find that information. Well, forget that, then. [emoji16]
I had even considered, if I was prepared to RUU my 10 (the Pixel is my primary) (but I'm not), to only then capture it after.
Thank you very much!
Thanks for responding, I didn't know that will give all that partition details. I am new to xda. Thanks again.
anam_1285 said:
Thanks for responding, I didn't know that will give all that partition details. I am new to xda. Thanks again.
Click to expand...
Click to collapse
I hope you find another way to recover your phone. Is it out of the uh oh protection/warranty period?
roirraW "edor" ehT said:
I hope you find another way to recover your phone. Is it out of the uh oh protection/warranty period?
Click to expand...
Click to collapse
No it's not, hopefully they will fix it. Thanks anyways.
roirraW "edor" ehT said:
No, I sure didn't. Thank you! I wondered but in my searches I didn't find that information. Well, forget that, then. [emoji16]
I had even considered, if I was prepared to RUU my 10 (the Pixel is my primary) (but I'm not), to only then capture it after.
Thank you very much!
Click to expand...
Click to collapse
Can you provide any possible upload link for MMCBLK0.img of HTC 10, I accidentally delete the dump
Hello, is ther a way to send the mmcblk0 to pc? with adb shell su -c dd if=/dev/block/mmcblk0
Hello fellas
i just unlocked my poco f3 and i have a habit with xiaomi devices to take backup of my EFS and persist partitions
i already done with persist partition but i cannot do for efs using this command >>
dd if=/dev/block/mmcblk0p10 of=/sdcard/modemst1.bin bs=512
dd if=/dev/block/mmcblk0p11 of=/sdcard/modemst2.bin bs=512
always end no such a directory
advice needed
thanks in advance
I haven't heard anyone talk of backing up the EFS partition. Are you sure it still exists?
Robert314 said:
I haven't heard anyone talk of backing up the EFS partition. Are you sure it still exists?
Click to expand...
Click to collapse
AS I Know EFS partition is important because it has the imei so good to back it up
i thought it can be back it up via termux but i cannot so i did via twrp and save the img in my PC in case something went wrong
be safe better than regretting
Antidote03 said:
AS I Know EFS partition is important because it has the imei so good to back it up
i thought it can be back it up via termux but i cannot so i did via twrp and save the img in my PC in case something went wrong
be safe better than regretting
Click to expand...
Click to collapse
Cheers dude, backing up EFS is something i always do too, you just reminded me on my poco!!
Antidote03 said:
Hello fellas
i just unlocked my poco f3 and i have a habit with xiaomi devices to take backup of my EFS and persist partitions
i already done with persist partition but i cannot do for efs using this command >>
dd if=/dev/block/mmcblk0p10 of=/sdcard/modemst1.bin bs=512
dd if=/dev/block/mmcblk0p11 of=/sdcard/modemst2.bin bs=512
always end no such a directory
advice needed
thanks in advance
Click to expand...
Click to collapse
Antidote03 said:
AS I Know EFS partition is important because it has the imei so good to back it up
i thought it can be back it up via termux but i cannot so i did via twrp and save the img in my PC in case something went wrong
be safe better than regretting
Click to expand...
Click to collapse
Hi,
I'm also used to backup EFS and persist partitions, via terminal emulator. I got my F3 and am waiting to unlock BL. But I don't know much about these A/B partitions...
You said you already backed up your persist partition, but may I ask how exactly ?
=> after grant su rights : dd if=/dev/block/[what-name ??]/persist of=/sdcard/persist.img
So could you please tell me what I dont know about this device ([what-name?]) ?
And about the EFS backup, what's the command prompt ? Usually, I did so :
=> dd if=/dev/block/[sdf1 ??] of=/sdcard/modemst1.bin bs=512
dd if=/dev/block/[sdf2 ??] of=/sdcard/modemst2.bin bs=512
But it seems it doesn't work... So you say you did it trough recovery, how please, only backup EFS partition ? Are the actual TWRP working to restore it, not sure someone already tried ??
Thanks very much !
néonaloj said:
Hi,
I'm also used to backup EFS and persist partitions, via terminal emulator. I got my F3 and am waiting to unlock BL. But I don't know much about these A/B partitions...
You said you already backed up your persist partition, but may I ask how exactly ?
=> after grant su rights : dd if=/dev/block/[what-name ??]/persist of=/sdcard/persist.img
So could you please tell me what I dont know about this device ([what-name?]) ?
And about the EFS backup, what's the command prompt ? Usually, I did so :
=> dd if=/dev/block/[sdf1 ??] of=/sdcard/modemst1.bin bs=512
dd if=/dev/block/[sdf2 ??] of=/sdcard/modemst2.bin bs=512
But it seems it doesn't work... So you say you did it trough recovery, how please, only backup EFS partition ? Are the actual TWRP working to restore it, not sure someone already tried ??
Thanks very much !
Click to expand...
Click to collapse
i used these
Backup E.F.S. and modem partitions for Android devices
How to backup, restore E.F.S. and modem? **This guide should work for any android device that manufactured in recent years.** E.F.S. is a crucial partition for Android devices as well as persist partition, which it stores all the important data for I.M.E.I. and I.M.S.I. numbers, W.I.F.I. and...
telegra.ph
https://www . youtube . com/watch?v=NQSAeZO7DaE&ab_channel=munchy
https://www . youtube . com/watch?v=rfAry7YpuCc&ab_channel=munchy
Do not forget remove the space in youtube links
Don't think youtube video's are banned from XDA, here's the links...
First one
And here for the second video from above (post 6)
Hi
Thanks to both of you @Antidote03 and @reg66 !!
I do know this guy's videos, wich are often great indeed.
But.. I like to know what I'm doing, so downloading his script is not my goal.. What I'd like to know is what are the exact command lines to get these backups on my side, using fastboot commands.
As I mentioned I do have what I think is some parts of the commands, but it lacks some info. To show them again :
- persist backup :
"dd if=/dev/block/[what-name ??]/persist of=/sdcard/persist.img"
but what should I replace as [what-name?] ??
- EFS backup :
"dd if=/dev/block/[sdf1 ??] of=/sdcard/modemst1.bin bs=512"
"dd if=/dev/block/[sdf2 ??] of=/sdcard/modemst2.bin bs=512"
In this case, the video shows more to be written that the part I'm wondering what I'd need for this device... (between .../block/..??../[sdf1-2 ??]/...)
Many thanks to all who could help me out !!