Question Device bricked, possibly damaged super partition? - Realme GT Neo 3

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.

Related

Android 10+ system file r/w access

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!

Apparently my phone has no system partition

I have a CUBOT Note 20 Pro (rooted) and today I tried to install the android 11 GSI when I got an error saying "FAILED (remote: 'This partition doesn't exist')" when trying to flash using the fastboot command line and this command specifically "fastboot flash system system.img". I looked around the scatter file and there seems to be no use of the system.img file whatsoever.
I have attached the scatter file and a screenshot of the error.
Any help would be highly appreciated.
{
"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"
}
[TOOL][WIN,LIN,AND,DARW] Super image tools | extract or make partitions RW in super partition
Disclaimer: Super image tools was made for testing and educational purposes, ME is not responsible for what you do on/with your device using our tools, you must agree that you using our tools on your own risk, I am not responsible for anything...
forum.xda-developers.com
aIecxs said:
[TOOL][WIN,LIN,AND,DARW] Super image tools | extract or make partitions RW in super partition
Disclaimer: Super image tools was made for testing and educational purposes, ME is not responsible for what you do on/with your device using our tools, you must agree that you using our tools on your own risk, I am not responsible for anything...
forum.xda-developers.com
Click to expand...
Click to collapse
How exactly do I use this tool?
read back super.img from SP Flash Tool, patch it, replace system.img, whatever, and flash new super.img back from fastboot
aIecxs said:
read back super.img from SP Flash Tool, patch it, replace system.img, whatever, and flash new super.img back from fastboot
Click to expand...
Click to collapse
Can you explain the steps a bit more? I'm really new and have no clue how to do this.
sorry apparently TWRP is required, but you can also use official tools on PC
https://forum.xda-developers.com/showthread.php?t=4041843
https://forum.xda-developers.com/showthread.php?t=4196625
aIecxs said:
sorry apparently TWRP is required, but you can also use official tools on PC
https://forum.xda-developers.com/showthread.php?t=4041843
https://forum.xda-developers.com/showthread.php?t=4196625
Click to expand...
Click to collapse
So, lets review the steps:
1. Unpack the super.img using the links you provided
2. Modify the system.img inside the super
3. flash
another approach is DSU Loader from Developer Options
DSU Sideloader lets you easily boot any custom GSI via Android DSU Loader
DSU Sideloader is an open source app that greatly simplifies the custom GSI installation process of the Android DSU Loader. Check it out!
www.xda-developers.com
https://forum.xda-developers.com/t/cubot-note-20-pro.4383027

Question Why can't we flash to vendor?

Trying to flash twrp adreno drivers gives this error despite having enough space in /vendor.
Anyone knows why?
RUI 3.0 LiteOS has custom drivers pre-installed. Looking on how to do this.
Thanks.
{
"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"
}
GT Neo 2 has dynamic partitions , i.e, A large partition named super that has virtual system , vendor and product partitions
RMX3370 said:
GT Neo 2 has dynamic partitions , i.e, A large partition named super that has virtual system , vendor and product partitions
Click to expand...
Click to collapse
is there a way to extract them so I can do it manually?
Spl1tz said:
is there a way to extract them so I can do it manually?
Click to expand...
Click to collapse
Yes , there is a way
But why you want to flash vendor ?
RMX3370 said:
Yes , there is a way
But why you want to flash vendor ?
Click to expand...
Click to collapse
Like i said on the original post... drivers.
So I don't need to use Magisk and Overlayfs.
Overlayfs is unstable for some apps.
Spl1tz said:
Like i said on the original post... drivers.
So I don't need to use Magisk and Overlayfs.
Overlayfs is unstable for some apps.
Click to expand...
Click to collapse
Method 1
Extract .ofp file use simg2img to make a single sparsed Super image and then use lpunpack to open Super.img and get all extracted partitions like my_heytap , my_stock , system , vendor and product , then edit the vendor .img file and then repack all partitions using lppack
​Method 2
Get vendor.img (Firmware.zip >firmware.ofp>super.img>vendor.img)
Modify it and repack it as newvendor.img
in fastboot mode do , fastboot erase vendor then fastboot flash vendor newvendor.img
Also before flashing this modified partition ensure that you have TWRP and have disabled vbmeta verification on all three vbmetas partitions​
RMX3370 said:
Method 1
Extract .ofp file use simg2img to make a single sparsed Super image and then use lpunpack to open Super.img and get all extracted partitions like my_heytap , my_stock , system , vendor and product , then edit the vendor .img file and then repack all partitions using lppack
​Method 2
Get vendor.img (Firmware.zip >firmware.ofp>super.img>vendor.img)
Modify it and repack it as newvendor.img
in fastboot mode do , fastboot erase vendor then fastboot flash vendor newvendor.img
Also before flashing this modified partition ensure that you have TWRP and have disabled vbmeta verification on all three vbmetas partitions​
Click to expand...
Click to collapse
Thank you for the detailed explanation!
Spl1tz said:
Thank you for the detailed explanation!
Click to expand...
Click to collapse
Did it work?

(TOOL) (Root) ADB Partition Backup Restore Tool for Windows

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

How To Guide [TB-J716F] Flashing Pseudo_Global firmware (many languages inside)

If you not like ZUI firmware - you can flash Pseudo_Global to your tablet. I've tested this way and sharing it here.
Pseudo_global fw was built on ZUI, it has A11 inside and you never can to get some system updates - no one is doing them.
Your data will gone away.
YOU ARE WARNED !
And so:
I've tryed this on ZUI 14.0.127 with unlocked bootloader and active slot _a. Active slot can be checked with
Code:
adb shell /bin/getprop ro.boot.slot_suffix
and answer must be _a
If not, you need change boot slot with command in fastboot mode:
Code:
fastboot set_active other
And now you can reboot in EDL mode and start to flash all needed partitions from unpacked archive Pseudo_ROW_J716Fl.7z
You need unpacked ZUI 12.6.211 from lolinet https://mirrors.lolinet.com/firmware/lenovo/Tab_P11_Pro_2021/TB-J716F/ for working with QPST Partition Manager.
How it looks you can see in this video:
You must flash ALL partitions archive contains. Files in Add.rar not need, it for any case.
MANDATORY ! After flashing you need at first to boot in recovery and make reset to factory settings, it will format userdata. Without this action you can't boot.
Spoiler: IS
{
"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"
}
Good Luck !
f1tm0t said:
If you not like ZUI firmware - you can flash Pseudo_Global to your tablet. I've tested this way and sharing it here.
Pseudo_global fw was built on ZUI, it has A11 inside and you never can to get some system updates - no one is doing them.
Your data will gone away.
YOU ARE WARNED !
And so:
I've tryed this on ZUI 14.0.127 with unlocked bootloader and active slot _a. Active slot can be checked with
Code:
adb shell /bin/getprop ro.boot.slot_suffix
and answer must be _a
If not, you need change boot slot with command in fastboot mode:
Code:
fastboot set_active other
And now you can reboot in EDL mode and start to flash all needed partitions from unpacked archive Pseudo_ROW_J716Fl.7z
You need unpacked ZUI 12.6.211 from lolinet https://mirrors.lolinet.com/firmware/lenovo/Tab_P11_Pro_2021/TB-J716F/ for working with QPST Partition Manager.
How it looks you can see in this video:
You must flash ALL partitions archive contains. Files in Add.rar not need, it for any case.
MANDATORY ! After flashing you need at first to boot in recovery and make reset to factory settings, it will format userdata. Without this action you can't boot.
Spoiler: IS
View attachment 5783891View attachment 5783993View attachment 5783995
Good Luck !
Click to expand...
Click to collapse
It was exactly what I was looking for and trying for days, but following your tutorial I still couldn't, it didn't turn on, I had to upload the rom 12.6.211 again. I wanted to leave it with multiple languages.
augustobfe said:
still couldn't, it didn't turn on
Click to expand...
Click to collapse
OK, I will re-check it in 2-3 days. Although I think you did something wrong.
f1tm0t said:
will re-check it in 2-3 days
Click to expand...
Click to collapse
Dude, I have some bad news for you. Your hands are crooked. That needs to be fixed.
My method works without fail. It only takes half an hour.
Try it again.
Spoiler: Look this:

Categories

Resources