ADB Partition Backup Restore Tool is a Partition Management app for all rooted Phones. with the help of this tool you can backup any partition from your device to your PC, also there is a flash option which you can use to write any partition..
Feature:
Read Partition directly to PC
Write Partition from PC
support almost all rooted phones
Requirement:
rooted phone, windows pc/laptop
Why:
read & flash critical partition like modem or EFS without custom recovery
Download;
file attached below
Disclaimer:
flashing wrong file to wrong block cause immediate bootloop
How to use:
Install adb driver
enable debugging
connect device
Run tool, click Start Partition Manager, once partition table readed, Select Read button to Read a partition and flash button to write a partition..
Here is My another similar tool for Xiaomi which use Sideload & work without root (only for xiaomi)
Your browser is not able to display this video.
Can you add window size scaling. Currently it is set to a fixed 1709x822.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ze7zez said:
Can you add window size scaling. Currently it is set to a fixed 1709x822.
View attachment 5747165
Click to expand...
Click to collapse
added in new attachment
After connecting to a PC and making a copy of any partition, an error is displayed:
"Reading" boot_b ".img: Pulling" boot_b ".img: ADB: Error: Failed to Stat Remote Object '/Sdcard/boot_B.img': No Such File or Directory"
There is no "boot_b.img" file on the card on the smartphone card (OnePlus8pro), no pop-up has erected in Magiska to give any root permissions.
What am I doing wrong?
regards
qriozum said:
After connecting to a PC and making a copy of any partition, an error is displayed:
"Reading" boot_b ".img: Pulling" boot_b ".img: ADB: Error: Failed to Stat Remote Object '/Sdcard/boot_B.img': No Such File or Directory"
There is no "boot_b.img" file on the card on the smartphone card (OnePlus8pro), no pop-up has erected in Magiska to give any root permissions.
What am I doing wrong?
regards
View attachment 5833457
Click to expand...
Click to collapse
inside magisk superuser allow SharedUID
Related
Hi!
I picked up a Mate 8 from a local service provider and would love to flash a new ROM to get rid of the ugly stock one, but I am stuck when trying to flash anything from TWRP.
The phone boots fine, I unlocked the bootloader, and has TWRP Mate 8 version...I can't locate any files from the internal storage though. I understand this is due to the system being encrypted. I cant seem to get around that though. I tried the format data option, hit yes, then go back but that obviously has deleted what I had stored (the SU zip). I can't mount the SD either afterwards, to load it in recovery.
I tried using the Italian knife tool, and used the Root option, and option 3, but get an error: error: cannot load '.\rec\boot.img
I am not a pro on this so it might be something farely stupid. I would love if anyone could help me with this...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
--------------------------------
Edit:
I was able to solve myself. It was a rookie mistake. Perhaps the internal storage is encrypted, however I was able to flash SU using TWRP by inserting an external SD, which I had not done before. I was able to view contents from that location and did not need to use the Italian knife tool.
Hi there I am using iBall KitKat mobile is rooted but i am unable delete system apps and can't use link2sd showing error mount structure needs cleaning can anyone help
aceslivelong said:
Hi there I am using iBall KitKat mobile is rooted but i am unable delete system apps and can't use link2sd showing error mount structure needs cleaning can anyone help
Click to expand...
Click to collapse
Are you using SuperSU ??
To delete system apps, download system app uninstaller from play store and grand it superuser permission.
My phone battery went off I plugged the charger and it boots me to twrp even though I didn't wish to open it when I press to boot me to system I still end up in twrp window... I also get this noffication
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Au123456 said:
My phone battery went off I plugged the charger and it boots me to twrp even though I didn't wish to open it when I press to boot me to system I still end up in twrp window... I also get this noffication View attachment 5479285
Click to expand...
Click to collapse
Do you want to be able to modify your system partition(including rooting the device) at some point in the future? If so, check the box beside the "never show this screen during boot again" then just swipe the slider at the bottom to allow modifications in the future.
Or
If you do not plan to modify your system partition in any kind of way, tap the "keep read only" button.
This happened to me multiple times, for me it was an error with flashing Treble GSI from google, tho i fixed it by going in fastboot mode/bootloader and on my PC to flash boot, lk, lk2, recovery (official one) and then reboot my phone, but you will delete the TWRP Recovery just so you know.
_________________________________________________________________________________________________________________________
NOTE: I don't know if this will work for you and might brick your device if you don't use correct ROM files...
_________________________________________________________________________________________________________________________
Also if it then boots into Fastboot mode than you can try flashing all files (It will factory reset your phone)
You have to install adb and fastboot on your PC
Commands:
cd *the path to adb and fastboot*
fastboot devices
fastboot flash *what you wanna flash* *filename of the file that you wanna flash*
For Example if you wanna flash boot it will be like ( fastboot flash boot boot.img ) if the filename is with .bin wich most new devices use it will be fastboot flash boot boot.bin
Hope that this helps
Hello!
How to unmount an old android 4.4.2 data partition?
Update: phone model if that makes any difference is Sony Xperia E1 dual
Not sure where to put this question, so I guess a general??
I have no knowledge of linux, android. But I got a programming background on windows systems and web.
I want to unmount an old android 4.4.2 data partition to run file system check because after deleting some files in data directory I am unable to write anything.
Could anyone please help me to get an idea how to do this? I searched the threads but they are more about flashing, TWRP and so on. Would not a simple file system check be enough in this case? As I noticed possibly it might be some sort of inode error? So checkdisk or something should fix it, shouldn't it?
I tried clearing the cache, it helped, but after few hours could not write anything again.
Now even the cache cleaning does not help.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It's always a good idea to set filepointer to begin of filesystem if you mount / unmount a partition: doing so you'll never run into error "Device or resource busy"
xXx yYy said:
It's always a good idea to set filepointer to begin of filesystem if you mount / unmount a partition: doing so you'll never run into error "Device or resource busy"
Click to expand...
Click to collapse
thanks for the tip!
However, I am a noob in linux/android, and the mount was done by android or KINGO rooter. So should I something like restart in recovery mode? Update:
Code:
adb reboot recovery
-> just rebooted to the regular interface
Update: phone is Sony Xperia E1 dual
I thought fixing a disk would be something like very basic task, like one liner or one parameter I did not add...
The mounting is just a way how I think I might solve the problem. That might be absolutely wrong way, not sure, now trying to move in the darkness by intuition only ...
Main problem: can not write anything with free space avaliable. Appeared since I deleted some files from /data using adb and rm command.
I also tried all the devices, but none of them was checked with two types of error:
Hi what is secret to using file manager on phone Android 10+ with su access to read and write in system - remove bloat apps? I have su access, but I read in 10+ file system not allow from file manager, only need use adb. How to use file manager with su to remove manually on Android 10+? I get error when deleting app from any file manager with su access "cannot delete". Danke.
Well, i guess that i can reply your question. It seems that we can't mount R/W due to Google's use of dynamic partitions for new version android devices.
However, we still have a way to fix it. Use su permissions and dd command to export those partitions which you want to modify (for example: system, product, vendor, and oem, but oem special), unpack and then repack, at last reboot you devices into fastbootd mode and flash back those partitions into you devices. reboot, now, you can R/W those partitions .
if you need to edit oem partition. You need edit a file in vendor partition firstly. Export and unpacking vendor partition. Finding a file which called "fstab.qcom". Open it and delect（,avb_keys=/product/etc/security/avb/oem.avbpubkey）code inside. Repacking and flash into you devices again. After this, the repackaged oem partition can be mounted correctly by flashing it again otherwise the oem partition can not be mounted (no files inside).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
SirisRui said:
Well, i guess that i can reply your question. It seems that we can't mount R/W due to Google's use of dynamic partitions for new version android devices.
However, we still have a way to fix it. Use su permissions and dd command to export those partitions which you want to modify (for example: system, product, vendor, and oem, but oem special), unpack and then repack, at last reboot you devices into fastbootd mode and flash back those partitions into you devices. reboot, now, you can R/W those partitions .
if you need to edit oem partition. You need edit a file in vendor partition firstly. Export and unpacking vendor partition. Finding a file which called "fstab.qcom". Open it and delect（,avb_keys=/product/etc/security/avb/oem.avbpubkey）code inside. Repacking and flash into you devices again. After this, the repackaged oem partition can be mounted correctly by flashing it again otherwise the oem partition can not be mounted (no files inside).
View attachment 5577955
Click to expand...
Click to collapse
Wow very complex but thank you for explain!
When attemping to flash the india A9 rom, "FAILED (remote: 'No such file or directory')" is encountered, the device is half bricked
I'm using this guide:
How to flash India version rom on rmx3560 (80W)
This is a simple tutorial English is not my native, so if anyone can add more explanation or answer question i will very appreciate Before flash, you must have adb and fastboot. Now follow the step Enable devloper option and enable oem unlock...
forum.xda-developers.com
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
According to this Google, "system" , "vendor" and "product" belongs to a dynamic partition inside super partition
Implementing Dynamic Partitions | Android Open Source Project
source.android.com
Fastboot Enhance shows I have a super partition 11.5GB in size:
I then tried to create / delete the logical partition and encounter "Could not open super partition" error:
Does this mean I have a corrupted super partition?
I tried the following command, it didn't solve the issue:
fastboot erase super
fastboot flash super super_empty.img (file is from A9 zip)
Will flashing a "super.img" solve the issue here? Can anyone upload the dump file?
Any ideas?
Hello. I have an idea as follows. if you need to do that, look for a rom specifically for flashing super.img, not a rom that contains a lot of images like this
bubugugu said:
When attemping to flash the india A9 rom, "FAILED (remote: 'No such file or directory')" is encountered, the device is half bricked
I'm using this guide:
How to flash India version rom on rmx3560 (80W)
This is a simple tutorial English is not my native, so if anyone can add more explanation or answer question i will very appreciate Before flash, you must have adb and fastboot. Now follow the step Enable devloper option and enable oem unlock...
forum.xda-developers.com
View attachment 5769945
According to this Google, "system" , "vendor" and "product" belongs to a dynamic partition inside super partition
Implementing Dynamic Partitions | Android Open Source Project
source.android.com
View attachment 5769943
Fastboot Enhance shows I have a super partition 11.5GB in size:
View attachment 5769965
I then tried to create / delete the logical partition and encounter "Could not open super partition" error:
View attachment 5769959
Does this mean I have a corrupted super partition?
I tried the following command, it didn't solve the issue:
fastboot erase super
fastboot flash super super_empty.img (file is from A9 zip)
Will flashing a "super.img" solve the issue here? Can anyone upload the dump file?
Any ideas?
Click to expand...
Click to collapse
Did you every solve this? I'm having the same problem.