I have locked the bootloader by using
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796 command.
then I used
adb reboot bootloader comant to reboot.
When it's executes the HTC Desire601(zara ul) the screen got off but it will not getting turn on again and also will not be able to charge the mobile.
Related
I'm trying to extract boot, recovery, system from my Rogers Notes, and need some clarification. Do I need to be rooted first? When I try now, I cannot access /dev/block to extract any image.
It seems all the root methods available somehow modifies the kernel or recovery or system, which kinda makes it impossible to extract stock images?
Help please
I have used adb to shell into the Note and extracted the various images. I'm looking for stock Rogers images. The ones DAGr8 posted still has the Telus brand on them.
c:\> adb shell
$ su
# dd if=/dev/block/mmcblk0p24 of=/sdcard/system.img
# dd if=/dev/block/mmcblk0p22 of=/sdcard/recovery.img
# dd if=/dev/block/mmcblk0p8 of=/sdcard/boot.img
# exit
c:\> adb pull /sdcard/system.img
c:\> adb pull /sdcard/recovery.img
c:\> adb pull /sdcard/boot.img
ha! i'm on the boat, i'm trying to extract all the original stuff before going crazy on it
just a few min ago i PMed DAGr8 for details
seems like you beat him to it
i know the radio was already done
so i'll just do those 3 mentioned above
firefly9 said:
c:\> adb shell
$ su
# dd if=/dev/block/mmcblk0p24 of=/sdcard/system.img
# dd if=/dev/block/mmcblk0p22 of=/sdcard/recovery.img
# dd if=/dev/block/mmcblk0p8 of=/sdcard/boot.img
# exit
c:\> adb pull /sdcard/system.img
c:\> adb pull /sdcard/recovery.img
c:\> adb pull /sdcard/boot.img
Click to expand...
Click to collapse
firefly9 said:
I have used adb to shell into the Note and extracted the various images. I'm looking for stock Rogers images. The ones DAGr8 posted still has the Telus brand on them.
c:\> adb shell
$ su
# dd if=/dev/block/mmcblk0p24 of=/sdcard/system.img
# dd if=/dev/block/mmcblk0p22 of=/sdcard/recovery.img
# dd if=/dev/block/mmcblk0p8 of=/sdcard/boot.img
# exit
c:\> adb pull /sdcard/system.img
c:\> adb pull /sdcard/recovery.img
c:\> adb pull /sdcard/boot.img
Click to expand...
Click to collapse
Once I get adb running do I just input the above commands into the command prompt?
Does the "adb pull" command just copy the images from the device or does it remove them?
Sorry for the basic adb questions. I've always had Nexus phones so I'm not sure if things work differently on other phones.
Once in the shell on the device, denoted by the "$" prompt, enter the commands outlined. After the "dd" commands have been completed, enter "exit" (twice, actually) and then the "adb pull" commands to copy the images from the device to you local computer. The images are copied so they will remain on the device until you delete them.
i find this easier...
adb shell dd if=/dev/block/mmcblk0p13 of=/sdcard/amss.bin
adb shell dd if=/dev/block/mmcblk0p17 of=/sdcard/mdm.bin
adb shell dd if=/dev/block/mmcblk0p24 of=/sdcard/system.img
adb shell dd if=/dev/block/mmcblk0p22 of=/sdcard/recovery.img
adb shell dd if=/dev/block/mmcblk0p8 of=/sdcard/boot.img
adb pull /sdcard/amss.bin
adb pull /sdcard/mdm.bin
adb pull /sdcard/system.img
adb pull /sdcard/recovery.img
adb pull /sdcard/boot.img
My htc evo 4glte is on hboot 1.19 and its software says 2.13.651.1 710RD and Im currently trying to do the facepalm s-off method but im stuck with this. Im not sure what to do or what im doing wrong. :,(
C:\adb\sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT256S400039 device
C:\adb\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # echo -ne "22222222" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
ev/block/mmcblk0p5 bs=1 seek=20 <
8+0 records in
8+0 records out
8 bytes transferred in 0.003 secs (2666 bytes/sec)
[email protected]:/ # adb reboot bootloader
adb reboot bootloader
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
1|[email protected]:/ # adb reboot bootloader
adb reboot bootloader
error: device not found
1|[email protected]:/ #
After this part type
C:\adb\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # echo -ne "22222222" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
ev/block/mmcblk0p5 bs=1 seek=20 <
8+0 records in
8+0 records out
8 bytes transferred in 0.003 secs (2666 bytes/sec)
Code:
exit
Code:
exit
These 2 exit commands will bring you out of adb shell and back to the regular command prompt.
**Note** if the cmd window closes on the second exit command then only 1 exit command is needed. (it's been a while so don't really remember)
Then type reboot-bootloader
uh well it looks like i got to the black htc screen but it said unkown error data failure does that mean i need to redownload something and redo it? im going to do that i guess an try again it seems it didnt hurt anything to mess that up..
welp now its hanging at sending 'zip' step 3.. :did i screw it up? how long is it supposed to take? :,(
I hate life heres a copy of my dumb scribble and please save me from my stupidness. ^^
F:\4glte\Evo4GLTERoot2>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HT256S400039 device
F:\4glte\Evo4GLTERoot2>adb shell
[email protected]:/ $ su
su
[email protected]:/ # echo -ne "22222222" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
ev/block/mmcblk0p5 bs=1 seek=20 <
8+0 records in
8+0 records out
8 bytes transferred in 0.006 secs (1333 bytes/sec)
[email protected]:/ # exit
exit
[email protected]:/ $ exit
exit
F:\4glte\Evo4GLTERoot2>adb reboot bootloader
F:\4glte\Evo4GLTERoot2>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.080s]
finished. total time: 0.080s
F:\4glte\Evo4GLTERoot2>fastboot flash zip PJ7510000-EvoLTE.zip
sending 'zip' (35863 KB)...
woo thank you for your help! looks like after i switched usb ports (both are 2.0) it stopped with the data failure and it seems to be s-off. so how should i update the software on it now? can I just flash a rom? I really need to flash a new rom/update it because the person who owned it before me somehow delete alot of stuff and left a partition of trash that wasn't delete when the guy sold it to me and some things don't work right.(IE sound as in ringtone and music doesn't work) but it vibrates and it seems to work on the sprint network just fine and I can text and call and hear people just fine.
Kannz2 said:
woo thank you for your help! looks like after i switched usb ports (both are 2.0) it stopped with the data failure and it seems to be s-off. so how should i update the software on it now? can I just flash a rom? I really need to flash a new rom/update it because the person who owned it before me somehow delete alot of stuff and left a partition of trash that wasn't delete when the guy sold it to me and some things don't work right.(IE sound as in ringtone and music doesn't work) but it vibrates and it seems to work on the sprint network just fine and I can text and call and hear people just fine.
Click to expand...
Click to collapse
Honestly now that you're S-off I would consider running the RUU for the Android 4.3 update. Click the top link in my sig and read the RUU section, which includes instructions on how to install the RUU. The link to the 4.3 update can be found at the bottom of the first post.
the one that says 4.13.651.4 RUU or is it the second to the bottom on the androidruu link?
looks like it updated it to 4.3 thank you for the link and for having all that stuff in one spot! ^^ what should I do now? can I installed a rom now? I dont need to update it anymore right?
could I get some help finding a usable rom? none of the ones ive downloaded want to flash they keep saying updater failed.. :/ i keep getting error executing updater binary in zip when installing rom.
Try V20 of this ROM:
http://forum.xda-developers.com/showthread.php?t=2528953
would that rom work with this kernel? http://forum.xda-developers.com/showthread.php?t=2181243 or this one? http://forum.xda-developers.com/showthread.php?t=2075542
No & no. There are no custom kernels for 4.3 for the EVO LTE.
dang owells thanks a bunch for the working rom. ^^ looks like the sound somehow doesn't work at all even with the fresh rom install. I guess the person who sold it to me ripped me off.. at least the sound works through the headphones and everything else works okay..you know any really good roms I can try out or is it limited for roms aswell? also the airplane mode widget is kinda weird in v20 in that its not actually a widget its just a shortcut to the settings. :,(
EDIT:
um would you happen to know the version of rom that they changed the airplane mode an if I can go back to it without messing up the phone? is seems a minor annoyance to some but it is much less annoying to toggle a widget than constantly going in and out of the settings. thanks for all the help.
First , your device must be S-OFF
S-off available now with Sunshine 3 and it's cost 25 $
1. Remove "Tampered flag"
Type following
adb devices
adb shell
su
echo -ne '\x00' | dd of=/dev/block/mmcblk0p6 bs=1 seek=5314564
(i would very strongly recomend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
Device boot into bootloader
Tampered is gone
2. Reset Bootloader to LOCKED
to LOCK bootloader, Type following: (recommended with using copy and paste or CTRL+C )
adb devices
adb shell
su
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
(recommended with using copy and paste or CTRL+C and paste)
exit
(exit twice until back to normal > prompt)
adb reboot bootloader
Device boot into bootloader
verify bootloader are now locked
3.UNLOCK bootloader
Following wint
adb devices
adb shell
su
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
(recommended with using copy and paste or CTRL+C and paste)
exit
(exit twice until back to normal > prompt)
adb reboot bootloader
verify bootloader are now unlocked
Really appreciate you putting this together1
If I ever RMA my phone I'm gonna appreciate it haha.
FoxyDrew said:
Really appreciate you putting this together1
If I ever RMA my phone I'm gonna appreciate it haha.
Click to expand...
Click to collapse
Haha this is just simple method , modified from M7 and M8
but it's worked as well
in case of it need .
Just a heads up these methods will work in Android Terminal Emulators from market just got to grant them root ( suggestions to copy and past echo line OP provides ) ... Also on newest Lollipop firmware the tampered flag still works but changes it to say software is official even if a custom rom and recovery are installed.
Sunshine 3 could be the cure for my headache **
Hi mytohn, sorry if this is the wrong way to contact you, but...
where can I get the program you are talking about (Sunshine 3)???
I need it for trying out if it will remove "Relocked" which HTC was so kind to demand for allowing me to install a RUU, and NOW I'M REALLY LOCKED =|:→$
↓ ↓☼↓ ↓
< S-off available now with Sunshine 3 and it's cost 25 $ >
mytohn said:
First , your device must be S-OFF
*****************************************************************
1. Remove "Tampered flag"
Type following
adb devices
adb shell
su
echo -ne '\x00' | dd of=/dev/block/mmcblk0p6 bs=1 seek=5314564
(i would very strongly recomend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
Device boot into bootloader
Tampered is gone
2. Reset Bootloader to LOCKED
to LOCK bootloader, Type following: (recommended with using copy and paste or CTRL+C )
adb devices
adb shell
su
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
(recommended with using copy and paste or CTRL+C and paste)
exit
(exit twice until back to normal > prompt)
adb reboot bootloader
Device boot into bootloader
verify bootloader are now locked
3.UNLOCK bootloader
Following wint
adb devices
adb shell
su
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
(recommended with using copy and paste or CTRL+C and paste)
exit
(exit twice until back to normal > prompt)
adb reboot bootloader
verify bootloader are now unlocked
Click to expand...
Click to collapse
Sc0rpio said:
Hi mytohn, sorry if this is the wrong way to contact you, but...
where can I get the program you are talking about (Sunshine 3)???
I need it for trying out if it will remove "Relocked" which HTC was so kind to demand for allowing me to install a RUU, and NOW I'M REALLY LOCKED =|:→$
↓ ↓☼↓ ↓
< S-off available now with Sunshine 3 and it's cost 25 $ >
Click to expand...
Click to collapse
You can find it out here and it cost 25 bucks
Cheers
http://theroot.ninja/
Hi, can someone who owns a working lg l9 device dump a bootloader image?
I prefer a P760 device but even if there are other devices it does the same.
This is the command:
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/debrick.img bs=1M count=128
or
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/debrick.img bs=1M count=512
I can't script worth a sh|t, hence my desire to share with other Pixel 4a5g owners, haha. Provided there is already a folder named '/partbackups' on the microsd card, the script should make a dd image backup of ALL 73 partitions on the phone, including userdata (pics, etc.) in compressed .gz format to save space (and time, since the script pipes the output to gzip).
I want to make it so it creates a folder with unique $Date$Time appended if not already existing (mkdir -p) for each backup run. So if run again it makes a new folder under /partbackups,One of these days I'll finish it, unless someone else wants to. This is just a rough draft. Requires dd utility in recovery, tested with TWRP. Need fastboot to boot TWRP
Put the script where you will remember it. I put it on the root of the phone's user storage which is /sdcard (or /emulated/0) or something. Doesnt matter where you put it (Downloads,Documents, etc.)
From Bootloader screen and phone connected to USB: fastboot boot twrp.img (unplug usb cable from phone after OK from terminal/cmd window).
TWRP should load. Goto Mount screen. Insert USB2GO usb adapter/microsd reader with properly formatted filesystem (I used ext4, but I think exfat works too?). You should see your storage there and go ahead and mount it. Then back out to main menu, goto advanced, then terminal. FYI, when mounted, the path to the mount point/microsd reader (USB2GO) is '/auto0-1/' .
Make sure to mark the script as executable: chmod +x partbackupgz.sh
run the script: ./partbackupgz.sh
There will only be output after each partition compresses over to storage. userdata (sda19) takes the longest. Let it run. It's not frozen. Does seem to use battery.
When it's done it will dump and compress each partition over on the fly with gzip.
When it's done, unmount the storage, remove and reboot. Again. I don't code/script. This is a work in progress. I'm not responsible if you open up a portal.
Please improve this script. I'll write a recovery script when I need one..Lol. Or maybe you will.
Bash:
#!/system/bin/sh
dd if=/dev/block/sda1 bs=1M | gzip -c > /auto0-1/partbackups/ssd.img.gz
dd if=/dev/block/sda2 bs=1M | gzip -c > /auto0-1/partbackups/persist.img.gz
dd if=/dev/block/sda3 bs=1M | gzip -c > /auto0-1/partbackups/misc.img.gz
dd if=/dev/block/sda4 bs=1M | gzip -c > /auto0-1/partbackups/keystore.img.gz
dd if=/dev/block/sda5 bs=1M | gzip -c > /auto0-1/partbackups/frp.img.gz
dd if=/dev/block/sda6 bs=1M | gzip -c > /auto0-1/partbackups/boot_a.img.gz
dd if=/dev/block/sda7 bs=1M | gzip -c > /auto0-1/partbackups/boot_b.img.gz
dd if=/dev/block/sda8 bs=1M | gzip -c > /auto0-1/partbackups/vendor_boot_a.img.gz
dd if=/dev/block/sda9 bs=1M | gzip -c > /auto0-1/partbackups/vendor_boot_b.img.gz
dd if=/dev/block/sda10 bs=1M | gzip -c > /auto0-1/partbackups/dtbo_a.img.gz
dd if=/dev/block/sda11 bs=1M | gzip -c > /auto0-1/partbackups/dtbo_b.img.gz
dd if=/dev/block/sda12 bs=1M | gzip -c > /auto0-1/partbackups/modem_a.img.gz
dd if=/dev/block/sda13 bs=1M | gzip -c > /auto0-1/partbackups/modem_b.img.gz
dd if=/dev/block/sda14 bs=1M | gzip -c > /auto0-1/partbackups/klog.img.gz
dd if=/dev/block/sda15 bs=1M | gzip -c > /auto0-1/partbackups/metadata.img.gz
dd if=/dev/block/sda16 bs=1M | gzip -c > /auto0-1/partbackups/vbmeta_system_a.img.gz
dd if=/dev/block/sda17 bs=1M | gzip -c > /auto0-1/partbackups/vbmeta_system_b.img.gz
dd if=/dev/block/sda18 bs=1M | gzip -c > /auto0-1/partbackups/super.img.gz
dd if=/dev/block/sda19 bs=1M | gzip -c > /auto0-1/partbackups/userdata.img.gz
dd if=/dev/block/sdb1 bs=1M | gzip -c > /auto0-1/partbackups/xbl_a.img.gz
dd if=/dev/block/sdb2 bs=1M | gzip -c > /auto0-1/partbackups/xbl_config_a.img.gz
dd if=/dev/block/sdc1 bs=1M | gzip -c > /auto0-1/partbackups/xbl_b.img.gz
dd if=/dev/block/sdc2 bs=1M | gzip -c > /auto0-1/partbackups/xbl_config_b.img.gz
dd if=/dev/block/sdd1 bs=1M | gzip -c > /auto0-1/partbackups/ALIGN_TO_128K_1.img.gz
dd if=/dev/block/sdd2 bs=1M | gzip -c > /auto0-1/partbackups/cdt.img.gz
dd if=/dev/block/sdd3 bs=1M | gzip -c > /auto0-1/partbackups/ddr.img.gz
dd if=/dev/block/sde1 bs=1M | gzip -c > /auto0-1/partbackups/aop_a.img.gz
dd if=/dev/block/sde2 bs=1M | gzip -c > /auto0-1/partbackups/tz_a.img.gz
dd if=/dev/block/sde3 bs=1M | gzip -c > /auto0-1/partbackups/hyp_a.img.gz
dd if=/dev/block/sde4 bs=1M | gzip -c > /auto0-1/partbackups/abl_a.img.gz
dd if=/dev/block/sde5 bs=1M | gzip -c > /auto0-1/partbackups/keymaster_a.img.gz
dd if=/dev/block/sde6 bs=1M | gzip -c > /auto0-1/partbackups/cmnlib_a.img.gz
dd if=/dev/block/sde7 bs=1M | gzip -c > /auto0-1/partbackups/cmnlib64_a.img.gz
dd if=/dev/block/sde8 bs=1M | gzip -c > /auto0-1/partbackups/devcfg_a.img.gz
dd if=/dev/block/sde9 bs=1M | gzip -c > /auto0-1/partbackups/qupfw_a.img.gz
dd if=/dev/block/sde10 bs=1M | gzip -c > /auto0-1/partbackups/vbmeta_a.img.gz
dd if=/dev/block/sde11 bs=1M | gzip -c > /auto0-1/partbackups/reserve_1.img.gz
dd if=/dev/block/sde12 bs=1M | gzip -c > /auto0-1/partbackups/uefisecapp_a.img.gz
dd if=/dev/block/sde13 bs=1M | gzip -c > /auto0-1/partbackups/imagefv_a.img.gz
dd if=/dev/block/sde14 bs=1M | gzip -c > /auto0-1/partbackups/apdp_a.img.gz
dd if=/dev/block/sde15 bs=1M | gzip -c > /auto0-1/partbackups/multiimgoem_a.img.gz
dd if=/dev/block/sde16 bs=1M | gzip -c > /auto0-1/partbackups/featenabler_a.img.gz
dd if=/dev/block/sde17 bs=1M | gzip -c > /auto0-1/partbackups/aop_b.img.gz
dd if=/dev/block/sde18 bs=1M | gzip -c > /auto0-1/partbackups/tz_b.img.gz
dd if=/dev/block/sde19 bs=1M | gzip -c > /auto0-1/partbackups/hyp_b.img.gz
dd if=/dev/block/sde20 bs=1M | gzip -c > /auto0-1/partbackups/abl_b.img.gz
dd if=/dev/block/sde21 bs=1M | gzip -c > /auto0-1/partbackups/keymaster_b.img.gz
dd if=/dev/block/sde22 bs=1M | gzip -c > /auto0-1/partbackups/cmnlib_b.img.gz
dd if=/dev/block/sde23 bs=1M | gzip -c > /auto0-1/partbackups/cmnlib64_b.img.gz
dd if=/dev/block/sde24 bs=1M | gzip -c > /auto0-1/partbackups/devcfg_b.img.gz
dd if=/dev/block/sde25 bs=1M | gzip -c > /auto0-1/partbackups/qupfw_b.img.gz
dd if=/dev/block/sde26 bs=1M | gzip -c > /auto0-1/partbackups/vbmeta_b.img.gz
dd if=/dev/block/sde27 bs=1M | gzip -c > /auto0-1/partbackups/reserve_2.img.gz
dd if=/dev/block/sde28 bs=1M | gzip -c > /auto0-1/partbackups/uefisecapp_b.img.gz
dd if=/dev/block/sde29 bs=1M | gzip -c > /auto0-1/partbackups/imagefv_b.img.gz
dd if=/dev/block/sde30 bs=1M | gzip -c > /auto0-1/partbackups/apdp_b.img.gz
dd if=/dev/block/sde31 bs=1M | gzip -c > /auto0-1/partbackups/multiimgoem_b.img.gz
dd if=/dev/block/sde32 bs=1M | gzip -c > /auto0-1/partbackups/featenabler_b.img.gz
dd if=/dev/block/sde33 bs=1M | gzip -c > /auto0-1/partbackups/devinfo.img.gz
dd if=/dev/block/sde34 bs=1M | gzip -c > /auto0-1/partbackups/spunvm.img.gz
dd if=/dev/block/sde35 bs=1M | gzip -c > /auto0-1/partbackups/splash.img.gz
dd if=/dev/block/sde36 bs=1M | gzip -c > /auto0-1/partbackups/limits.img.gz
dd if=/dev/block/sde37 bs=1M | gzip -c > /auto0-1/partbackups/limits-cdsp.img.gz
dd if=/dev/block/sde38 bs=1M | gzip -c > /auto0-1/partbackups/toolsfv.img.gz
dd if=/dev/block/sde39 bs=1M | gzip -c > /auto0-1/partbackups/logfs.img.gz
dd if=/dev/block/sde40 bs=1M | gzip -c > /auto0-1/partbackups/storsec.img.gz
dd if=/dev/block/sde41 bs=1M | gzip -c > /auto0-1/partbackups/uefivarstore.img.gz
dd if=/dev/block/sde42 bs=1M | gzip -c > /auto0-1/partbackups/secdata.img.gz
dd if=/dev/block/sdf1 bs=1M | gzip -c > /auto0-1/partbackups/ALIGN_TO_128K_2.img.gz
dd if=/dev/block/sdf2 bs=1M | gzip -c > /auto0-1/partbackups/modemst1.img.gz
dd if=/dev/block/sdf3 bs=1M | gzip -c > /auto0-1/partbackups/modemst2.img.gz
dd if=/dev/block/sdf4 bs=1M | gzip -c > /auto0-1/partbackups/fsg.img.gz
dd if=/dev/block/sdf5 bs=1M | gzip -c > /auto0-1/partbackups/fsc.img.gz
what's the point of backup partitions? most can be downloaded from google, some are auto generated, some are just cache and userdata is encrypted therefore useless. not to mention will fail on fat32 storage.
mine aren't encrypted. i think when I put a custom rom on, one of the requirements was to wipe the device which removed the encryption (LineageOS). I can open the .gz files with any archive utility. Or flash them. Similar but different than an ADB pull since dd copies ALL bits including those shown as not in use which for recovery purposes might be good (deleted file).
Some of the partitions not included are EFS partitions that include things like IMEI and serial number. There is supposed to be a backup/auto restoration if one gets wiped and/or golden copy but it has been known on "some" roms (I'd never use MIUI) where EFS gets totally nuked and unless you have a backup of it, or QPST backup of NV, you're screwed.
I think, this will copy EVERYTHING. For encrypted phones, this could still work, abeit more work involved because one would have to extract their key beforehand and then they coud use it to access their encrypted archives. I guess? I dunno.
And this script would be run from the phone in recovery (TWRP), I thought TWRP (or LineageRecovery) works with no encryption only? So it would only benefit those people anyway.
wouldn't it be easier to add important partitions to twrp fstab with flag backup=1?
FBE + metadata encryption used to be supported in TWRP up to Android 12, seems maintainers still working on it.
Oh, if that's the case, great (encryption support). I guess there were issues with A11-A12 and twrp at least
on 4a5g.
Does modiying twrp /fstab give more access to partitions to backup? If so, that would be sweet because I would have it do ALL of them, or at least of course the option. The persist is not enough, in some.....weird...cases and not nessessary this model phone, people have hosed their EFS--how, who knows. But yea I love TWRP. If twrp could be tweaked to backup all partitions if listed in /fstab, that would be super spiffy.
seriously I have no clue how things work on this TWRP, but on older devices one could just add lines in twrp.fstab ourself.
please ask in TWRP support thread maintainer might add important partitions.
thx for info.