Hello all,
I have rooted my Moto G30 with Magisk and flashed both boot partitions. Now I have superuser rights and I am able to access everything on the phone.
After that I created a physical image of the phone with "dd if=/dev/block/mmcblk0 bs=512 conv=notrunc,noerror,sync | nc -l -p 8888". However, when I try to analyse this with Autopsy, I find no data. According to "cat proc/partitions", most of the data is on the partitions mmcblk0p75 and p77. Is it better to back up only these partitions or do I need other parts of the memory to be able to analyse the image?
Thank you very much for your help.
Can someone help me? i went to block the bootloader and soon after i tried to switch to the latest stock rom and if this error some help me please
Related
For some reason the I747M.DLL does not work correctly and Im pretty sure about this. If you use the I747M.DLL you will not have Download Mode. I know how to fix this but need SBL1.MBN specifically from Claro PR Unit and Im 100% Sure this one will work in any other USA/Canada Versions. Then for the others SBL2,SBL3,TZ,RPL & ABOOT they are on the stock I747MUMBLL1. Some one can try to make debrick.img from a working I747M rooted with this instructions and also make a backup of .PIT cuz are not the same.
This is the Most Important a Backup of a Good/Working Unit SBL1.MBN, Phone has to be rooted to extract it.
su
dd if=/dev/block/mmcblk0p2 of=/sdcard/sbl1 bs=4096
This is the Second Most Important a Backup of a Good/Working Unit OUT.PIT file, Phone has to be rooted to extract it.
su
dd if=/dev/block/mmcblk0 of=/sdcard/out.pit bs=8 count=481 skip=2176
This is for make a Recovery SDC Card:
su
dd if=/dev/block/mmcblk0 of=/sdcard/debrick.img bs=1M count=128
I already see a lot of Extremely Problems with the I747M Units that is why Im posting this to try between us and fix this situation. The I747M.DLL Is not working as expected. I already have 2 units that show the Qualcomm Hub and dont have Download nor Recovery Menu Available. Yes the units are completly full bricked so for me was useless to make a backup of first 128MBs I need a backup from an Actual Working I747M from Claro PR.
BRs,
Luis Daniel
anyone who can help?
i need the one of 4.4.2
Could someone run
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/unbrick.img bs=512 count=524288
and upload it? Flashing unbrick in a 'raw' fashion will allow you to hard brick most Qualcomm devices. Unfortunately I lost my backup and I can't boot my device. This file will allow me to recover. Thanks!
I can
Will it safe to run and guide me how to run it ??? Dont know where it goes............ I also have my stock recovery file saved by flashify https://drive.google.com/file/d/0B3i0YJU831QXTHctYWphX2Y0aE0/view?usp=sharing
vincowoo said:
Will it safe to run and guide me how to run it ??? Dont know where it goes............ I also have my stock recovery file saved by flashify https://drive.google.com/file/d/0B3i0YJU831QXTHctYWphX2Y0aE0/view?usp=sharing
Click to expand...
Click to collapse
I messed up, here's the correct command
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/unbrick.img bs=512 count=524288
Thank you very much!
Still not found .... run the command without error ... dont know where required file goes ... checked the root of both external and internal sd...
vincowoo said:
Still not found .... run the command without error ... dont know where required file goes ... checked the root of both external and internal sd...
Click to expand...
Click to collapse
Make sure you're running as root, from adb shell or terminal emulator. Try this one instead
Code:
dd if=/dev/block/mmcblk0 of=/storage/extSdCard/unbrick.img bs=512 count=31250
That command should have created 'unbrick.img' on your external SD card. I am extremely thankful for you doing this. My device is bricked and sitting in QHSUSB_BULK mode. You may want to save this file in case you ever need it! Thanks again, it is very much appreciated!
It is my pleasure. this forum helped me many times m trying to return something.That command completed successfully i am uploading it ?
https://docs.google.com/file/d/0B3i0YJU831QXUmViWGMyMGE1eHM/edit?usp=docslist_api
So I have been recently playing around with my S4 Mini Value Edition/Plus (I9195I) trying to port CyanogenMod to it. Then when it was really late I read about the `adb reboot nvbackup` (DO NOT EVER RUN THIS COMMAND ON THE S4 MINI VE), and now the phone is basically stuck in a bootloop. I think the problem is identical with http://forum.xda-developers.com/showthread.php?t=2657519 which points out that Samsung has simply messed up something there and now the FSG and BACKUP partitions are corrupt. According to the thread it is possible to recover if you get clean versions of the FSG and BACKUP partitions so I'm hoping someone with the S4 Mini Value Edition (i9195i) can help me by getting the clean versions from his device. It's not much to do and won't do anything to your device but will help me to continue (and actually have a working device again).
Can someone run these commands (either in a rooted shell (e.g. adb shell -> su -> change in the directory of your internal/external sdcard (not sure about the path), use TWRP way if in doubt), or from TWRP directly (Advanced -> Terminal Command -> then select e.g. your /external_sd or normal /sdcard) -> Select (bottom of the screen)), type the following 2 commands and send me the resulting files (e.g. by attaching it here to a post, or uploading it on AndroidFileHost or Dropbox, ... whatever):
Code:
dd if=/dev/block/mmcblk0p9 of=fsg.img
dd if=/dev/block/mmcblk0p19 of=backup.img
This will place the partition contents of FSG and BACKUP in the current dir (file names fsg.img and backup.img) and you can upload them from your PC e.g. by inserting your external SD card in your PC or simply booting into Android and connecting your phone to the PC. Unlike the names suggest they don't seem to contain a backup but actually files that are necessary for booting which is now corrupted after I run this stupid command... Thanks in advance, I hope someone can help me with getting my phone back working.
PS: I'm pretty sure there is no separate forum for the VE/Plus variant, so I guess this is correct here.
Solved with the help of @kariboo92 (thanks!), if someone ever makes the same mistake as me for this device, just PM me and I can help to fix it.
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 !!
Well, I have essentially done everything wrong that you can do wrong.
For security considerations, I wanted to disable my baseband modem on my LG G4 H815 (currently having /e/ installed) - see this beautiful post for the instructions.
As I don't have root, I had the genius idea to do it all via the TWRP recovery. Once booted into the recovery, I had to enter my encryption lock, but that didn't work. I had yet another genius idea, thinking that I probably wouldn't have to unlock the encryption, as I only wanted to disable the modem (and didn't care to backup my data). So I entered TWRP leaving the system read-only.
Then I entered the terminal and wanted to disable the relevant services, as described in the post. However, the pm command wasn't available in the TWRP shell, so I had the genius idea to just skip those steps.
I then wanted to override the radio with zeros (as described in the post). However, the exact file from the post didn't exist, so I had the genius idea to overwrite /dev/block/platform/soc.0/f9824900.sdhci/by-name/modem instead. However, I firstly wanted to back it up to my external SD (I assumed that wouldn't be affected by the encryption) and did so with dd. After also having the modem overwritten with 0s (and synced) I rebooted to system, where I got the error that "Settings," stopped working and my phone started rebooting to recovery.
I thought "oh well, I'll just restore the backup modem from the SD", however I had to realize that (probably because I hadn't mounted the SD properly) the file didn't exist on the SD (anymore).
That's the current state. As I don't really want to lose my data (that I didn't backup), I haven't tried re-flashing anything yet (especially as I don't know if this'd help).
Is there any way to recover the "modem" without losing my data? Or, even better, is there a way to continue disabling the modem, with my phone properly booting again?
I really appreciate your help - please let me know if you need further information.
EDIT: It would probably be super helpful (and enough) if someone out there with the H815 could dump the content of their modem dev and share it with me. I don't think (?) that's included in a system image - at least it isn't mounted in system.
EDIT: Let me provide some instructions on how to (presumably) safe my day, if you have an H815 with TWRP recovery and adb on your computer:
Reboot to recovery:
Bash:
adb reboot recovery
In TWRP, mount your Micro SD card or another partition you can read & write to (Mount -> Tick Micro SD card)
Restart adb:
Bash:
adb kill-server
Enter adb shell:
Code:
adb shell
In adb shell, validate that your SD (or other partition) is correctly mounted (you should get the contents of your external SD):
Bash:
ls /external_sd
In adb shell, dump data from modem and exit adb shell:
Bash:
dd if=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modem of=/external_sd/modem.img
sync
exit
Pull dump from device:
Bash:
adb pull /external_sd/modem.img
Upload modem.img from your computer (from the directory you executed above command from) to some cloud
Share a link to the file with me
I'd be very grateful if someone could do this. Please feel free to ask questions about the procedure or to help me in any other way.
Turns out, someone already did upload a modem - it's even linked in the install instructions for /e/. I used this file (flashed via TWRP) and it seems to have fixed my issues.
Of course, now the modem still isn't disabled - so if someone has an idea on how to achieve this without bricking my phone (preferrably also without having to root it), feel free to make me happy.
I now have tried killing the modem with rooting my phone, but it lead to the same error. Before deleting the modem, I ran the following commands in adb shell to mimick the disabled services from the original post as best as possible:
Bash:
su -c "pm disable com.android.cellbroadcastreceiver"
su -c "pm disable com.android.mms"
su -c "pm disable com.android.phone"
su -c "pm disable com.android.providers.telephony"
su -c "pm disable com.android.smspush"
su -c "pm disable com.android.mms.service"
su -c "pm disable foundation.e.message"
su -c "pm disable com.android.server.telecom"
su -c "pm disable com.qualcomm.qcrilmsgtunnel"
su -c "pm disable foundation.e.esmssync"
Do I have to put this in a startup script? And if so, how do I do this?
It does seem as if they stayed deactivated though:
Bash:
$ su -c "pm list packages" -d
package:com.android.providers.telephony
package:com.android.mms.service
package:com.android.terminal
package:foundation.e.message
package:com.qualcomm.qcrilmsgtunnel
package:com.android.cellbroadcastreceiver
package:com.android.server.telecom
package:com.android.smspush
package:foundation.e.esmssync
package:com.android.phone
I'd love to know how I can achieve this.
EDIT: Now my phone reboots as soon as it's disconnected from my computer (and doesn't boot anymore)...