Develop Bugs

SM-T320 Hard Brick Recovery

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

my nexus 5x Only the boot animation flicker in and repeated to the splash screen

Pliss help me my bullhead Only the boot animation flicker in and repeated to the splash screen I've tried all ways at XDA for flashing but still can not boot...

Up
Sent from my Nexus 5X using XDA Labs

backup
did you make a backup using TWRP 3.0.2-1 ?
and then restore it?

diegoshock said:
did you make a backup using TWRP 3.0.2-1 ?
and then restore it?
Click to expand...
Click to collapse
yes master, first I install ROM weta but I do not like the ROM is then I returned to my stock rom backup through TWRP 3.0.2.1 (Rom Stock android N) there was the beginning can not boot, I've been many times tried to flash back ranging from adb fastboot, adb sideload and also LGup
Sent from my Nexus 5X using XDA Labs

You restored EFS partition? It's broken on 3.0.2.1 TWRP.

muwlan said:
yes master, first I install ROM weta but I do not like the ROM is then I returned to my stock rom backup through TWRP 3.0.2.1 (Rom Stock android N) there was the beginning can not boot, I've been many times tried to flash back ranging from adb fastboot, adb sideload and also LGup
Click to expand...
Click to collapse
If you make the backup with TWRP 3.0.2-1 your EFS partition is now useless.
You have to use this 2 strings of code un adb
ADB shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384
and
ADB shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384
This two strings of code Will zeroed the EFS partition.
This partition store the imei Mac network etc...
If you zeroed, is Smart enough to put a fresh copy completely new
Its tested on my nexus 5x also approved on the nexus 6p
Thanks to the senior developers and contributers of xda
Good luck!

diegoshock said:
If you make the backup with TWRP 3.0.2-1 your EFS partition is now useless.
You have to use this 2 strings of code un adb
ADB shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384
and
ADB shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384
This two strings of code Will zeroed the EFS partition.
This partition store the imei Mac network etc...
If you zeroed, is Smart enough to put a fresh copy completely new
Its tested on my nexus 5x also approved on the nexus 6p
Thanks to the senior developers and contributers of xda
Good luck!
Click to expand...
Click to collapse
Thank you very much master...

How to backup persist partition?

I searched everywhere but I couldn't find nowhere how to backup efs or persist partition, I just read the thread for twrp flashable stock oreo for moto g5 cedric and it says it is useful to backup them to save the phone in case of IMEI or VoLTE or 4G problems after the zip install but TWRP doesn't seems to backup them and online I didn't found guides.
EDIT:
To help people with the same problem I'll write here.
Thanks to TheFixItMan I've found the most easy solution which is to flash the TWRP 3.2.3-2 arm64 that has backup option for EFS and Persist, I'll quote here the answer with the link.
Use terminal commands to back up the partition - dd copy partition name to location
Or
Try this unofficial twrp and look at backup options
https://drive.google.com/open?id=1ML...yBHyg81cHdW1cB
Click to expand...
Click to collapse

Use terminal commands to back up the partition - dd copy partition name to location
Or
Try this unofficial twrp and look at backup options
https://drive.google.com/open?id=1MLlljM7BzMj9Da57LeyBHyg81cHdW1cB

TheFixItMan said:
Use terminal commands to back up the partition - dd copy partition name to location
Or
Try this unofficial twrp and look at backup options
https://drive.google.com/open?id=1MLlljM7BzMj9Da57LeyBHyg81cHdW1cB
Click to expand...
Click to collapse
So the command I should use is:
Code:
dd copy persist to <location dir>
?
Should I use this on twrp Advanced > Terminal?
Are unofficial twrp safe?

OnionMaster03 said:
So the command I should use is:
Code:
dd copy persist to <location dir>
?
Should I use this on twrp Advanced > Terminal?
Are unofficial twrp safe?
Click to expand...
Click to collapse
The command should look something like this - not tried it and don't own this device
Code:
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
Yes enter it in twrp terminal - once done it will output persist.img to sdcard
To copy back just reverse the if and of parts of the command
Unofficial twrps are perfectly safe - all official builds that aren't build by twrp start off as unofficial and are just submitted to their repo to become official
You can always flash what ever recovery you want after
The one I gave I think has the backup option for persist - if not just try the terminal command

OP, did you try the command? I'd like to backup mine as well

same question here! any updates?
EDIT: Managed to do it myself. I ended up pulling up the image through adb.
For all of you who are still wondering all I did is start adb and type the following:
adb pull /persist C:\platform-tools/persist.img
Click to expand...
Click to collapse
Substitute C:\platform-tools with your local folder.
You can also use the code provided in the thread, but If you wanna retrieve the file, you should copy it to /external_sd instead of microsd (also you can do it from the adb shell instead of the twrp terminal, which is more convenient).

persist backup and restore - 9008 mode
maybe this tool is useful too...
works in 9008 mode and has some firehose-loaders inside
moto g5 has qualcomm 8937 chipset, so should work...
https://mega.nz/#!dIcE0ApR!DEZIBxdxCqVEVRZRKevRr_Z_EXMF1I1PCJb-k7wvyGc
BR

1rdc said:
OP, did you try the command? I'd like to backup mine as well
Click to expand...
Click to collapse
I haven't tried this yet, I'm going to do in the next hours

Trouble Restoring Backed Up Stock ROM & WiFi Won't connect using LOS 15.1

Most of my the question/topic was explained here.
@steadfasterX
Re the WiFi pls share also the boot logs (see LOS faq).
Click to expand...
Click to collapse
I couldn't pull a boot log from TWRP, I'd get "Sbin/sh: adb: not found". That output seems to be haunting a lot of my adb attempts, it appears when I try "adb sync" as well.
Ok the choose "format" data in twrp and try to boot first without your userdata backup into stock. Lemme know if that works.
Click to expand...
Click to collapse
I tried, I unfortunately get a solid wall of bootloop. I still have everything from my SALT backup in case anything may or may not be needed. I just had a though, could the problem be that this backup was from before I USUed my phone (I can't remember if I said that in the first place)?

emperordogma said:
Most of my the question/topic was explained here.
@steadfasterX
I couldn't pull a boot log from TWRP, I'd get "Sbin/sh: adb: not found". That output seems to be haunting a lot of my adb attempts, it appears when I try "adb sync" as well.
I tried, I unfortunately get a solid wall of bootloop. I still have everything from my SALT backup in case anything may or may not be needed. I just had a though, could the problem be that this backup was from before I USUed my phone (I can't remember if I said that in the first place)?
Click to expand...
Click to collapse
The confusing part is we talk about 2 different things here:
1) WiFi. This is related to LOS and so when asking for logs l always assume you're on LOS. TWRP must match the LOS version.
2) booting stock. To make TWRP work it must be the matching TWRP installed of your stock release. Is that the case? If not do that first.
So re stock. Its strange that it does not boot with formatted data. Could you also flash magisk here and then try to boot?

steadfasterX said:
The confusing part is we talk about 2 different things here:
1) WiFi. This is related to LOS and so when asking for logs l always assume you're on LOS. TWRP must match the LOS version.
2) booting stock. To make TWRP work it must be the matching TWRP installed of your stock release. Is that the case? If not do that first.
So re stock. Its strange that it does not boot with formatted data. Could you also flash magisk here and then try to boot?
Click to expand...
Click to collapse
1) I'll worry about the WiFi if/when I can get stock up and running. But I was/am using LOS 15.1 (here's the version "lineage-15.1-20210608-UNOFFICIAL-h812_usu"), and my TWRP was "twrp-3.4.0-PREVIEW-230_g4_O".
2) I downgraded my TWRP to "twrp-3.3.1-PREVIEW-196_g4_MM", and same result, I get to the LG screen and the notification light stays on, then nothing. When inputting these dd commands:
Code:
adb shell
dd if=/external_sd/boot.img of=/dev/block/bootdevice/by-name/boot bs=512
dd if=/external_sd/system.img of=/dev/block/bootdevice/by-name/system bs=4096
dd if=/external_sd/userdata.img of=/dev/block/bootdevice/by-name/userdata bs=4096
adb shell sync
When I put "adb shell sync" in I get "/sbin/sh: adb: not found"
I tried clearing the cache after I put it in, then tried formatting, as well as tried installing Magisk. And when mounting the data partition, everything seem to be there (hard to tell exactly since it's not the way I'm used to seeing it).
Edit: I just tried getting a boot log using:
Code:
adb pull /cache/debug/boot_lc_crash.txt
adb pull /cache/debug/boot_lc_full.txt
adb pull /cache/debug/boot_lc_kernel.txt
And the first one comes back with /sbin/sh: adb: not found

emperordogma said:
1) I'll worry about the WiFi if/when I can get stock up and running. But I was/am using LOS 15.1 (here's the version "lineage-15.1-20210608-UNOFFICIAL-h812_usu"), and my TWRP was "twrp-3.4.0-PREVIEW-230_g4_O".
2) I downgraded my TWRP to "twrp-3.3.1-PREVIEW-196_g4_MM", and same result, I get to the LG screen and the notification light stays on, then nothing. When inputting these dd commands:
Code:
adb shell
dd if=/external_sd/boot.img of=/dev/block/bootdevice/by-name/boot bs=512
dd if=/external_sd/system.img of=/dev/block/bootdevice/by-name/system bs=4096
dd if=/external_sd/userdata.img of=/dev/block/bootdevice/by-name/userdata bs=4096
adb shell sync
When I put "adb shell sync" in I get "/sbin/sh: adb: not found"
I tried clearing the cache after I put it in, then tried formatting, as well as tried installing Magisk. And when mounting the data partition, everything seem to be there (hard to tell exactly since it's not the way I'm used to seeing it).
Edit: I just tried getting a boot log using:
Code:
adb pull /cache/debug/boot_lc_crash.txt
adb pull /cache/debug/boot_lc_full.txt
adb pull /cache/debug/boot_lc_kernel.txt
And the first one comes back with /sbin/sh: adb: not found
Click to expand...
Click to collapse
Ok so first of all: adb shell sync must be executed from without the shell you're in. That wasn clear described. So in other words after the dd command you just need to write "sync". That's it. It will not give any output when finished.
So here the next steps:
Try to mount system in TWRP and browse with the file manager if there are any files in /system/apps .
Use bs=512 for all dd commands.
Share your stock boot img here.
What data do you need exactly btw? App data like settings etc? Or just specific files?

steadfasterX said:
Ok so first of all: adb shell sync must be executed from without the shell you're in. That wasn clear described. So in other words after the dd command you just need to write "sync". That's it. It will not give any output when finished.
So here the next steps:
Try to mount system in TWRP and browse with the file manager if there are any files in /system/apps .
Use bs=512 for all dd commands.
Share your stock boot img here.
What data do you need exactly btw? App data like settings etc? Or just specific files?
Click to expand...
Click to collapse
Ahhhh, I assumed everything I saw was in a "copy/paste" format so, I didn't think to even try to exclude the adb from it.
I was able to mount system, and browse apps, there was stuff in there.
I used the "bs=512" method, and it gave the same result. I'm starting to think I'm just boned honestly. I'll upload my boot.img here in a few (in case you see this before I do).
I was hoping I could back up my texts/call logs (I was able to salvage a few, but I'm missing about a months worth), properly backup WhatsApp, get my Nova settings, and make sure I'm not missing anything else (I had a list, but can't think of it now). And I was hoping by doing it, it would fix the annoying Wifi bug.
Edit 1: I don't think it's "bootlooping", because I read that you could boot into TWRP while it's doing it (if your timing is good), I tried and couldn't get into TWRP at all, it's "stone walling" at the LG screen.
Edit 2: My stock Boot.img

ok so .. the boot image you send is not from the STOCK ROM. That is from LOS it seems. Pls upload the stock one which you are trying to flash with dd

steadfasterX said:
ok so .. the boot image you send is not from the STOCK ROM. That is from LOS it seems. Pls upload the stock one which you are trying to flash with dd
Click to expand...
Click to collapse
Huh, I am not sure how that happened. I'm starting to wonder if after the first try with adb push if I was even using my Stock Boot.img, magisk must've messed with me (they said the recommend way to to patch a boot.img) and I got them mixed up? Or at least that's the only thing I can think of.
Anyways, this should be the right one. Boot.img

@steadfasterX
I was able to boot back to Stock using the correct boot.img, unfortunately I lost some very important WhatsApp texts because it had to "re-verify", but other than that, everything seems to be in order. My apologies for confusing us both with the wrong boot.img. When I was messing around with Magisk, I must've gotten the two confused. I won't know if the wifi is fixed in LOS until later (I have to wait a while before I can use WhatsApp again).

emperordogma said:
@steadfasterX
I was able to boot back to Stock using the correct boot.img, unfortunately I lost some very important WhatsApp texts because it had to "re-verify", but other than that, everything seems to be in order. My apologies for confusing us both with the wrong boot.img. When I was messing around with Magisk, I must've gotten the two confused. I won't know if the wifi is fixed in LOS until later (I have to wait a while before I can use WhatsApp again).
Click to expand...
Click to collapse
yea that was my assumption after seeing that wrong boot.img.. all users were able to boot STOCK this way so it was either a mistake or bad flash. glad you figured it out.
when your WiFi does not come back on LOS later attach the boot logs then.
cheers

steadfasterX said:
yea that was my assumption after seeing that wrong boot.img.. all users were able to boot STOCK this way so it was either a mistake or bad flash. glad you figured it out.
when your WiFi does not come back on LOS later attach the boot logs then.
cheers
Click to expand...
Click to collapse
Everything appears to be working fine now, including the WiFi (you were right about fixing it by going back to stock), which appears to be better than it was before! I decided to upgrade to Lineage 16, because you had just updated it recently so, best to stay where the active development is (or at least last update), in case anything goes wrong. Thank you so much for your assistance, sorry about mixing up the boot.imgs. And thank you continuing support for the G4 (in some capacity).
I also just found out my phone had "OEM Unlock" in the developer settings, so I don't think I needed to use USU (if I read about that tight), pretty annoyed with myself for not paying attention properly.

emperordogma said:
Everything appears to be working fine now, including the WiFi (you were right about fixing it by going back to stock), which appears to be better than it was before! I decided to upgrade to Lineage 16, because you had just updated it recently so, best to stay where the active development is (or at least last update), in case anything goes wrong. Thank you so much for your assistance, sorry about mixing up the boot.imgs. And thank you continuing support for the G4 (in some capacity).
I also just found out my phone had "OEM Unlock" in the developer settings, so I don't think I needed to use USU (if I read about that tight), pretty annoyed with myself for not paying attention properly.
Click to expand...
Click to collapse
If your device is not a h811 or h815 international(!) then this option in dev settings will just do.....nothing. If it would be THAT easy there were never the need for UsU so you did it all right

steadfasterX said:
If your device is not a h811 or h815 international(!) then this option in dev settings will just do.....nothing. If it would be THAT easy there were never the need for UsU so you did it all right
Click to expand...
Click to collapse
Then what the heck is the point of that button/switch??? I figured because mine was a frankenstien device that maybe almost all of them had it, or I just got "lucky".

emperordogma said:
Then what the heck is the point of that button/switch??? I figured because mine was a frankenstien device that maybe almost all of them had it, or I just got "lucky".
Click to expand...
Click to collapse
Its just there by mistake. Not by LG but the OEMs. The OEMs like verizon, etc are not doing a good job but that's not new..

Question little help

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 !!