Database Info

[GUIDE] WIPE multiple SD-EXT partitions with TWRP recovery

Welcome guys, with this short guide you'll be able to wipe any number of SD-EXT partitions with the help of a powerful feature inside TWRP recovery. Furthermore you'll get always fresh ext4 partitions without journal in just one shot.
TOOLS
1. MiniTool Partition Wizard (Google it if you don't have it already installed).
2. TWRP recovery 2.3.6.0 for Pico (click here).
INSTRUCTIONS
1. Get your ext4 partions done with MiniTool Partition Wizard. You can see here a very good guide.
2. Insert your SD card into Pico and boot into TWRP recovery.
3. Once inside TWRP, click MOUNT button. Check that SD-Ext is not selected (unmounted), otherwise you could damage your partition.
{
"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"
}
4. Go back to start screen and tap ADVANCED button then TERMINAL COMMAND button. Check that it is in Root folder (/). Tap SELECT button.
5. Write the folowing inside the command window and press enter.
Code:
mke2fs -t ext4 -O ^has_journal /dev/block/mmcblk0p2
6. Repeat the process if you have more sd-ext partitions, you just have to edit the last number in the command line and press enter (for 2 sd-ext partitions mmcblk0p2 is first partition and mmcblk0p3 is second partition).
7. Now you have fresh formated ext4 partitions and without journal for maximum speed. Now flash your favorite ROM that supports multiple sd-ext partitions and ENJOY!
8. Repeat this process (from number 3) whenever you'll flash a new ROM. I hope one day TWRP incorporates multiple SD-ext partitions handling.
SPECIAL THANKS
@#define for porting awesome TWRP recovery to Pico.
@Dees_Troy and TeamWin project members for making the best Recovery out there.
@cute_prince for his great idea of multiple sd-ext partitions and OC for Pico.

you could also try using the Aroma File Manager for shell access

http://forum.xda-developers.com/showpost.php?p=42928510&postcount=1 I have to follow the whole procedure or only PART 1 : Preparing The SDcard . I already have Single SD-EXT partition.

droidbot678 said:
http://forum.xda-developers.com/showpost.php?p=42928510&postcount=1 I have to follow the whole procedure or only PART 1 : Preparing The SDcard . I already have Single SD-EXT partition.
Click to expand...
Click to collapse
Just the part related to creating the partitions! One sd-ext can be created with any recovery. For more than one we need MiniTool.

thewisenerd said:
you could also try using the Aroma File Manager for shell access
Click to expand...
Click to collapse
But the good thing is TWRP has it all!

cornholio_rules said:
Just the part related to creating the partitions! One sd-ext can be created with any recovery. For more than one we need MiniTool.
Click to expand...
Click to collapse
Thanks, btw in that guide (http://s11.postimg.org/yjknyd51v/image.png) SD-DATA and SD-CACHE were done. And Amal said that partition should be SD-SYSTEM , SD- DATA. I'm confused here.. PFA of my sdcard partition!

droidbot678 said:
Thanks, btw in that guide (http://s11.postimg.org/yjknyd51v/image.png) SD-DATA and SD-CACHE were done. And Amal said that partition should be SD-SYSTEM , SD- DATA. I'm confused here.. PFA of my sdcard partition!
Click to expand...
Click to collapse
Don't worry, names doesn't matter, just the order. First ext4 partition from top to bottom (in MiniTool) will be mmcblk0p2 and so on.

But twrp doesn't mount sd-ext 4 from mini tool

ahmadmemon said:
But twrp doesn't mount sd-ext 4 from mini tool
Click to expand...
Click to collapse
That was like 10 years ago dude!

cornholio_rules said:
But the good thing is TWRP has it all!
Click to expand...
Click to collapse
IMO, I find it easier to type in Aroma's Terminal, even though I have TWRP

Is there any way to type the command conviently？
---------- Post added at 07:06 AM ---------- Previous post was at 06:56 AM ----------
icame to a key called kill.is it alright
?

wsdyleon said:
Is there any way to type the command conviently？
---------- Post added at 07:06 AM ---------- Previous post was at 06:56 AM ----------
icame to a key called kill.is it alright
?
Click to expand...
Click to collapse
The keyboard in TWRP is very good but tiny as everything in Pico, just tipe in carefully.
Don't touch that 'kill' button, leave the magic work. Kill is always bad!

no os found
after creating 3 ext as ext 2 ,3 n 4 ........i success fully installed rom but i found error as no os found ??? help

I have 3 ext4 partitions, created via MiniParition Tools
SD-SYSTEM ---> EXT4 ---> 500 mB is enough
SD-DTA ----> EXT4 ----> 1 GB
SD-CACHE ---> EXT4 ---> 150 MB
SD-EXT unmounted, and command "mke2fs -t ext4 -O ^has_journal /dev/block/mmcblk0p2" (last digit 3 and 4) doesn't work. But sometimes it works...
Can't understand why...?
and

Mount system as rw on Android 10 with Magisk 20.4

I am using Magisk 20.4 and trying to mount /system on a Google Pixel running Android 10.
I have tried using:
Code:
adb shell su -c mount -o rw,remount /system
that gives: me
mount: '/system' not in /proc/mounts
Click to expand...
Click to collapse
The following also do not work:
Code:
adb shell su -c mount -o rw,remount /
'/dev/root' is read-only
Click to expand...
Click to collapse
Code:
adb shell su -c mount -o rw,remount /sbin/.magisk/mirror/system_root
'/sbin/.magisk/block/system_root' is read-only
Click to expand...
Click to collapse
I was also curious whether stuff in /sbin/.magisk/rootdir/system/ can actually override stuff in /system/ but that doesn't seem to be the case..
Has anyone managed to mount /system on Android 10? Is this issue specific to Google Pixel?
Cheers,
Paschalis

Its due to EXT4 dedup filesystem (it's not writable).
This was pointed out by magisk developer john wu, more info: https://mobile.twitter.com/topjohnwu/status/1170404631865778177

So it's impossible? Even with TWRP?

Turns out I don't need to mount /system.
I wanted this so I could ship my modified version of libart.so, libart-compiler.so and dex2oat (which are in APEX), as well some other external compiler libraries and tools.
So I've written some magisk modules, and it works really well. Even for the runtime apex. I'm impressed!
The only reason someone might need to mount /system is if he/she uses an app/tool that needs it.

The only way to make changes to the /system partition is to make a Magisk module that mounts the files you modified instead of the original ones.

Paschalis said:
Turns out I don't need to mount /system.
I wanted this so I could ship my modified version of libart.so, libart-compiler.so and dex2oat (which are in APEX), as well some other external compiler libraries and tools.
So I've written some magisk modules, and it works really well. Even for the runtime apex. I'm impressed!
The only reason someone might need to mount /system is if he/she uses an app/tool that needs it.
Click to expand...
Click to collapse
Well I need to mount because of Link2sd. Is there any way to do it?

jcruzcruz35 said:
Well I need to mount because of Link2sd. Is there any way to do it?
Click to expand...
Click to collapse
No, on Android 10 the /system partition is locked at read only, the only way to make modifications to the /system partition is to make a Magisk module.

JJcoder said:
No, on Android 10 the /system partition is locked at read only, the only way to make modifications to the /system partition is to make a Magisk module.
Click to expand...
Click to collapse
Sht, it has to be especially make it for each smartphone? Or you think there gonna be eventually a Module for everyone?

jcruzcruz35 said:
Sht, it has to be especially make it for each smartphone? Or you think there gonna be eventually a Module for everyone?
Click to expand...
Click to collapse
I'm sure eventually there will either be a universal Module, Or a way to resize the partition and change the file system to make it writable.

JJcoder said:
...Or a way to resize the partition and change the file system to make it writable.
Click to expand...
Click to collapse
Resized works, but how to change the file system to make it writable?

vagyula said:
Resized works, but how to change the file system to make it writable?
Click to expand...
Click to collapse
How did you resize it?

Code:
$ su
# mount --remount / -w
ONLY makes effert to terminal, which means other apps like Solid Explorer, Root Explorer etc are still r/o. Some roms(Pixel Experience tested, including stock) are not working.

hardplastic said:
Code:
$ su
# mount --remount / -w
Only works in terminal
Click to expand...
Click to collapse
It doesn't work on Android 10, you will just get the error:
Code:
'/dev/root' is read only

JJcoder said:
It doesn't work on Android 10, you will just get the error:
Code:
mount: '/dev/root' not user user mountable in fstab
Click to expand...
Click to collapse
Reboot your device and try again, it works both two of my devices in Android 10

hardplastic said:
Reboot your device and try again, it works both two of my devices in Android 10
Click to expand...
Click to collapse
Nope, Same error bcuz it is locked at read only.

JJcoder said:
Nope, Same error bcuz it is locked at read only.
Click to expand...
Click to collapse
That's weird, have you checked your operation is in the terminal? It only makes /system rw to terminal, other apps still r/o .

hardplastic said:
That's weird, have you checked your operation is in the terminal? It only makes /system rw to terminal, other apps still r/o .
Click to expand...
Click to collapse
No, you can't just simply Type a command and have it mount as rw...
If you want to make modifications you have to make a Magisk Module which uses Magic Mount to mount the modified files over the original ones.
I have no idea how u got it to work, I would like to see proof..

JJcoder said:
No, you can't just simply Type a command and have it mount as rw...
If you want to make modifications you would have to make a Magisk Module which uses Magic Mount to mount the modified files over the original ones.
Click to expand...
Click to collapse
Then how do you explain that?
{
"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"
}

hardplastic said:
Then how do you explain that?
Click to expand...
Click to collapse
Let me see that u are on stock Android 10

JJcoder said:
Let me see that u are on stock Android 10
Click to expand...
Click to collapse

Failed to mount 'system_root' (Read-only file system)

Deleted

Flacito13 said:
I think I bricked my Poco F2 Pro (Redmi K30 Pro). I installed LuckyPatcher to disable disable signature verification. When I LuckyPatcher rebooted, I got stuck in a bootloop (the phone booted to Fastboot instead of System). I now want to format data in my TWRP to flash a new ROM and start from scratch. However, when I format data I get the following error in my TWRP: Failed to mount 'system_root' (Read-only file system).
I tried unsuccessfully tried fixing it by starting Terminal in TWRP and typing "mount -o rw,remount /system". I get "mount: can't find /system in /etc/fstab. with "mount -s system", I get a bunch of text but nothing that makes sense to me.
I hope somebody can help me out here...I just bought it :crying:
Click to expand...
Click to collapse
I have the same issue. Just install fresh rom with xiaomi tool and everything should be fine.

Koziol87 said:
I have the same issue. Just install fresh rom with xiaomi tool and everything should be fine.
Click to expand...
Click to collapse
I successfully flashed, but I still get "failed to mount /system_root (read-only file system)"...
{
"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"
}

When I reboot after flash, it simply boots to FastBoot again...someone please help me (

Flacito13 said:
When I reboot after flash, it simply boots to FastBoot again...someone please help me (
Click to expand...
Click to collapse
have you tried with XiaomiTools?

Flacito13 said:
When I reboot after flash, it simply boots to FastBoot again...someone please help me (
Click to expand...
Click to collapse
Did You flash 4 part file?

Koziol87 said:
Did You flash 4 part file?
Click to expand...
Click to collapse
What is 4 part file?

kevinmonja said:
have you tried with XiaomiTools?
Click to expand...
Click to collapse
I tried, but I get this error:

Flacito13 said:
I tried, but I get this error:
Click to expand...
Click to collapse
what rom are you trying to flash?

What TWRP version did you install? I recommend 3.4.2B from LR.Team.

batuken said:
What TWRP version did you install? I recommend 3.4.2B from LR.Team.
Click to expand...
Click to collapse
I have it...the problem is still that the system_root is "read-only"...:crying::crying::crying:
EDIT: after flashing with the xiaomitool, I now get error when formating data: failed to mount /odm invalid argument

kevinmonja said:
what rom are you trying to flash?
Click to expand...
Click to collapse
The one automatically downloaded by the flash tool. It is: lmi_eea_global_images_V12.0.2.0.QJKEUXM_20200730.0000.00_10.0_eea_7a4654b9f8
I tried formatting data again, but now I get another error: "failed to mount /odm invalid argument"

Flacito13 said:
The one automatically downloaded by the flash tool. It is: lmi_eea_global_images_V12.0.2.0.QJKEUXM_20200730.0000.00_10.0_eea_7a4654b9f8
I tried formatting data again, but now I get another error: "failed to mount /odm invalid argument"
Click to expand...
Click to collapse
Try to flash Xiaomi.eu ROM in TWRP.

batuken said:
Try to flash Xiaomi.eu ROM in TWRP.
Click to expand...
Click to collapse
failed to mount '/odm' (invalid argument)

Flacito13 said:
failed to mount '/odm' (invalid argument)
Click to expand...
Click to collapse
I had this problem a few days ago. To solve it, I had to reflash the rom (without formatting any partition) from twrp, ignoring the errors. (I'm on xiaomi.eu stable rom)
The important thing is to never modify the system partition (via lucky patcher or other tool) after installing Magisk, otherwise the phone won't reboot.

Lowxorx said:
I had this problem a few days ago. To solve it, I had to reflash the rom (without formatting any partition) from twrp, ignoring the errors. (I'm on xiaomi.eu stable rom)
The important thing is to never modify the system partition (via lucky patcher or other tool) after installing Magisk, otherwise the phone won't reboot.
Click to expand...
Click to collapse
Look the picture, I reflashed the rom with twrp. I still get the error cannot mount.
I see that some people have solved it by external rom installation, using adb sideload? How do I do that?

Deleted

Flacito13 said:
Look the picture, I reflashed the rom with twrp. I still get the error cannot mount.
I see that some people have solved it by external rom installation, using adb sideload? How do I do that?
Click to expand...
Click to collapse
I tried flashing via adb sideload in twrp, my devices wasnt recognized. Had to use my OTG USB Flashdrive.

ok i try side loading

I had same problem and go to twrp,format data type YES then reboot to twrp and clean cache,data,dalvik,interal,not wipe system...and reboot to twrp,put stable rom from xiaoimi.eu and flash it

How To Guide [GUIDE] How to make your System RW / Super R/W read/write-able

Welcome to the one and only, the original, universal
SystemRW / SuperRW feat. MakeRW / ro2rw by lebigmac​
This script removes the read-only lock of all partitions embedded in the super partition of your stock firmware.
This allows you to mount your device as R/W and fully debloat your device and customize your MIUI experience to make it run as smooth as silk!
MIUI 12 is great but it has a little bit too much bloatware.
Be very careful and make lots of backups before messing with your System ! One small error could cause irreversible bootloop!
Enjoy debloating and customizing your fully read/write-able Android device!
NOTE: Before launching this script make sure you've got full read/write (rw) access to the /data partition by first decrypting and then mounting /data partition as r/w !
Visit official project thread​
{
"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"
}

PS C:\adb> adb shell "ls -Alg /dev/block/by-name | grep 'super'"
lrwxrwxrwx 1 root 16 1970-02-02 16:40 super -> /dev/block/sda23
POCO X3 pro

/

so does this work on x3 pro?
edit, it didnt. threw some devblock warnings about not mounting

@gsser Yes it works! Try latest version! Good luck!

lebigmac said:
@gsser it can work depending on how much effort you decide to put into it.
Click to expand...
Click to collapse
well if it is like that, then why is there even a non complete script when it can be done by the owner...
And since you have already asked how it is on x3 pro im saying it doesnt work.
"I'm looking forward to hearing from the Poco X3 Pro users how the script performs on your device."

It is mostly because of current recoveries for x3 pro doesnt support /data yet, but the script can use sdcard rather than internal storage.

@gsser Thanks for the screenshot and feedback. Please download latest v1.32
Feel free to send me your log files if you get any errors and I'll take a look. Thanks.

lebigmac said:
@gsser Thanks for the screenshot and feedback. Please download latest v1.31 that I uploaded today. And feel free to edit the script with your favorite text editor and change the super image dump path in line #333 to this. Then save file.
Code:
sDumpTarget="/sdcard/super_original.bin"
Feel free to send me your log files if you get any errors so I can take a look. Thanks.
Click to expand...
Click to collapse
Only lines i could find about data were these and i edited the path to my sdcard, flashed it.
Edit just seen you edited your reply. Ill try

I'm not 100% sure if your changes will work properly. Feel free to give it a try.
Keep in mind if you change variables the script might not work as expected.
The reason why the script is installed to /data/local/tmp is because in /scard path you don't have execution permission. That's why it's better to launch script from /data/local/tmp
Poco x3 pro recovery don't have full r/w access to /data/local/tmp ?! That's crazy!
You can try launch script directly from android and it should work as expected.

lebigmac said:
I'm not 100% sure if your changes will work properly. Feel free to give it a try.
You can also use /sdcard path it should be the same thing as what you wrote. Good luck.
Please report back any errors thanks.
Keep in mind if you change LOC variable you must also copy the whole script folder to that new location.
The reason why the script is installed to /data/local/tmp is because in /scard path you don't have execution permission. Is better to launch script from /data/local/path
You don't have full access to /data/local/path in poco x3 pro?
Click to expand...
Click to collapse
This is how the folder looks rightnow. Do i need to do anything about it? Also what is LOC :c
Edit nvm, lol im blind

Not sure what you're trying to do but that path is totally messed up
Just run script in android operating system as described in the instructions if you don't have full read write access to /data/local/tmp from custom recovery
Have you tried manually mounting /data partition in orange fox? Maybe it's not mounted and that's why /data/local/tmp is unavailable.

lebigmac said:
Not sure what you're trying to do but that path is totally messed up
Click to expand...
Click to collapse
Yeah ill just change than only line

lebigmac said:
Not sure what you're trying to do but that path is totally messed up
Just run script in android operating system as described in the instructions if you don't have full read write access to /data/local/tmp from custom recovery
Have you tried manually mounting /data partition in orange fox? Maybe it's not mounted and that's why /data/local/tmp is unavailable.
Click to expand...
Click to collapse
All available recoveries have issue mounting data, some cant even mount mtp.
Ill try android one and see what happens.

If your /data partition is not mounted then you can try manually mounting /data partition before running script.
mount /data

lebigmac said:
LOC is a safety path check feature I had to implement because some folks were launching the script from God knows where and overwriting God knows what with dd lol.
Did you try manually mounting /data partition before running script?
mount -o remount,rw /data
Click to expand...
Click to collapse
Yeah, ill try android version then flash it with fastboot but im a bit confused. Do i execute this command or do i need to do other things? Sorry im a noob at these things
./makesysrw.sh in=./files/super/super_original.bin out=./custom/path/super_fixed.bin size=50
Actually ill stop here since i dont get the whole thing, i dont understand at all :/ once i tried to use linux and it was not fun for me... Im bad with command lines and scripts

After copying script folder into /data/local/tmp/
open command prompt and type this
Bash:
adb shell
su
cd /data/local/tmp/systemrw_1.32
chmod +x ./systemrw.sh
./systemrw.sh size=50

lebigmac said:
After installing script folder into /data/local/tmp/
open command prompt and type this
Bash:
adb shell
su
cd /data/local/tmp/makesysrw_1.31
chmod +x ./makesysrw.sh
./makesysrw.sh size=25
Click to expand...
Click to collapse
now this is what i like

are you sure your bootloader is unlocked?

now do i need to flash the super_fixed.bin in script folder's files folder in fastboot? original super is approx. 8gb and fixed one is nearly half of it

Question APN settings permanent fix?

So I was able to get my APN settings applied once using the methods on here, but since then, the APN stopped working and I am unable to repeat the process to get my Verizon SIM to have data.
Looking at another thread, the APNs are stored in /system/product/etc/apns-conf.xml
That file contains mostly Asian market APNs, but I did see a few for T-mobile, which explains why that service usually works.
I'm trying to use lsec6315update to replace the apns-conf.xml file but it's failing. Is this a root issue or something I'm missing?
Code:
#!/system/bin/sh
#
mv /system/product/etc/apns-conf.xml /system/product/etc/apns-conf.xml.bak
cp -rf /storage/sdcard1/apns-conf.xml /system/product/etc/apns-conf.xml
chmod 0644 /system/product/etc/apns-conf.xml
Thanks!

can't use lsec6315update to with in /system partition
You should use FYT Firmware Workbench (linux) and put the file manually inside, then recompile and flash only the kernel (with lsec6315update)
Cheers !

mariodantas said:
can't use lsec6315update to with in /system partition
You should use FYT Firmware Workbench (linux) and put the file manually inside, then recompile and flash only the kernel (with lsec6315update)
Cheers !
Click to expand...
Click to collapse
OK, so to use the workbench, I need ADB to the system or does the tool mount my FYT unit?
(I'm new to mods, but do have a Linux system to execute with, so that's a thing)

This tool wil decompile your firmware (file named 6315_1.zip) and recompile it (when decompiled and mounted, you can replace your files inside /system /vendor /product etc) !

mariodantas said:
This tool wil decompile your firmware (file named 6315_1.zip) and recompile it (when decompiled and mounted, you can replace your files inside /system /vendor /product etc) !
Click to expand...
Click to collapse
OK, so I need to extract the firmware using a different tool, then can run the scripts?
Got it, now I just need to choose which 6315_1.zip to use. 4PDA has some nice modded ones that add USB tethering, which is compelling.

FYT Factory (mine) and gfo to -> Kernels !

mariodantas said:
FYT Factory (mine) and gfo to -> Kernels !
Click to expand...
Click to collapse
yep, got that one from another thread.
now for troubleshooting.
I tried to mount it but got the following:
Code:
BROTLI -- Handling socko.new.dat.br...
Converting socko.new.dat file into socko.img file
Creating _mountpoint/socko folder...
Adding '128 Mb' extra size to _tmp/_firmware/socko.img ...
128+0 records in
128+0 records out
134217728 bytes (134 MB, 128 MiB) copied, 0.0375032 s, 3.6 GB/s
e2fsck 1.46.5 (30-Dec-2021)
ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open _tmp/_firmware/socko.img
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>
resize2fs 1.46.5 (30-Dec-2021)
resize2fs: Bad magic number in super-block while trying to open _tmp/_firmware/socko.img
Couldn't find valid filesystem superblock.

Easy solution: go to config.ini and remove socko from partitions to handle, later I'll try to handle 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"
}

mariodantas said:
Easy solution: go to config.ini and remove socko from partitions to handle, later I'll try to handle this
View attachment 5752349
Click to expand...
Click to collapse
Actually, it's giving the same error for all the images, not just socko.
Mount points and sub folders are created, but nothing is mounted and folders are empty.
Code:
Cleaning workbench...
Unmounting and deleting folder '_mountpoint'...
Unmounting product.img ...
umount: /home/john/Downloads/Radio/FYT-Firmware-Workbench/_tmp/_firmware/product.img: not mounted.
Unmounting system.img ...
umount: /home/john/Downloads/Radio/FYT-Firmware-Workbench/_tmp/_firmware/system.img: not mounted.
Unmounting vendor.img ...
umount: /home/john/Downloads/Radio/FYT-Firmware-Workbench/_tmp/_firmware/vendor.img: not mounted.
Unmounting elable.img ...
umount: /home/john/Downloads/Radio/FYT-Firmware-Workbench/_tmp/_firmware/elable.img: not mounted.
Deleting _mountpoint ...
Deleteing folder '_tmp'...
All done !
Workbench clean now !

Which linux distro are you using ?

mariodantas said:
Which linux distro are you using ?
Click to expand...
Click to collapse
DISTRIB_ID=Pop
DISTRIB_RELEASE=22.04
DISTRIB_CODENAME=jammy
DISTRIB_DESCRIPTION="Pop!_OS 22.04 LTS"
NAME="Pop!_OS"
VERSION="22.04 LTS"
ID=pop
ID_LIKE="ubuntu debian"
PRETTY_NAME="Pop!_OS 22.04 LTS"
VERSION_ID="22.04"
VERSION_CODENAME=jammy
UBUNTU_CODENAME=jammy
LOGO=distributor-logo-pop-os

update:
after some python3 tweaks, I was able to get my apns_conf.xml loaded into the unit, but it didn't help, I still get no data on Verizon. I may have to do the drastic and factory reset to see if that fixes anything since I think the unit is wonked but good.