To do this you will need an Hexadecimal editor and have root access to your phone.
FIRST MAKE A BACKUP OF EFS PARTITION!USE GOOGLE FOR HOW-TO
Steps:
1. Make a full backup of the /efs folder
2. Get the nv_data.bin file located in /efs
3. Open it with an hexa editor (like WinHex)
4. Go to line 181460 and modify from 01 00 00 00 00 to 00 00 00 00 00
5. Copy the modified nv_data.bin file into /efs
6. Set the appropiate owner user and group doing chown 1001.1001 nv_data.bin
7. Remove the nv_data.bin.md5 file
8. Reboot your phone
9. Enjoy!!
LOCKED
{
"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"
}
UNLOCKED
ADB commands:
# su
# cd /efs
# cp /sdcard/nv_data.bin /efs/nv_data.bin
# rm nv_data.bin.md5
# chown 1001.1001 nv_data.bin
# reboot
To check it you can do *#7465625# and verify that Network Lock is [OFF]
I hope it can be useful for you.
I AM NOT RESPONSIBLE IF U SCREW UP UR PHONE....IF U DONT DO THIS CORRECTLY,U WILL SCREW UP UR /EFS PARTITION AND YOU WOULD NOT BE ABLE TO USE NETWORK!!
Hi,
this method doesn't work.
The main problem is that this file doesn't exist in I9001.
This method is similar if it is not the same that the one used for I9000 (I'm not sure if is the same address in the file)
Regards
sugggus said:
Hi,
this method doesn't work.
The main problem is that this file doesn't exist in I9001.
This method is similar if it is not the same that the one used for I9000 (I'm not sure if is the same address in the file)
Regards
Click to expand...
Click to collapse
ok...can u attach your /efs folder and pm me?
i am pretty sure all android phones have these files
which files u dont have?
Yep... file nv_data.bin doesn't exist on 9001. Made search on whole phone.
sh!t happens..........................
ok,so any "similar file"?
Hi Sakindia,
this is what I see:
- .files
.dj550 (folder)
empty
.jck12 (folder)
empty
.ssh01 (folder)
empty
keystr (file)
- lost+found (folder)
empty
Ther are 2 folders, the first one has 3 empty folders and one file (keystr) and the second one is empty.
Any solution for us?
Regards
this is /efs partition,right?strange............
sakindia123 said:
this is /efs partition,right?strange............
Click to expand...
Click to collapse
Hi,
yes, this is the /efs folder.
regards
has anyone tried any app?since this doesnt work,thats the last resort
Hi,confirm that it does not work on my phone.
file nv_data.bin doesn't exist
sakindia123 said:
has anyone tried any app?since this doesnt work,thats the last resort
Click to expand...
Click to collapse
hi sakindia, wise forum people, any alternative?
i have root and i9001XXKP4, european Vodafone lock (Spain).
Have been searching and trying out all the free apps available in the market, incl. sgs2 apps. Nothing works.
SGS unlock complains about a busy box error, but i think it just cant find the i9000 file its looking for.
Having to pay for IMEI unlock feels like a defeat... i'm finding out too late that the i9001 is a bit of an unsupported niche thing, i guess.
Hope someone comes up with something!!! Cheers
sakindia123 said:
To do this you will need an Hexadecimal editor and have root access to your phone.
FIRST MAKE A BACKUP OF EFS PARTITION!USE GOOGLE FOR HOW-TO
Steps:
1. Make a full backup of the /efs folder
2. Get the nv_data.bin file located in /efs
3. Open it with an hexa editor (like WinHex)
4. Go to line 181460 and modify from 01 00 00 00 00 to 00 00 00 00 00
5. Copy the modified nv_data.bin file into /efs
6. Set the appropiate owner user and group doing chown 1001.1001 nv_data.bin
7. Remove the nv_data.bin.md5 file
8. Reboot your phone
9. Enjoy!!
LOCKED
UNLOCKED
ADB commands:
# su
# cd /efs
# cp /sdcard/nv_data.bin /efs/nv_data.bin
# rm nv_data.bin.md5
# chown 1001.1001 nv_data.bin
# reboot
[...]
Click to expand...
Click to collapse
# cp /sdcard/nv_data.bin /efs/nv_data.bin
Really ???
eBug said:
# cp /sdcard/nv_data.bin /efs/nv_data.bin
Really ???
Click to expand...
Click to collapse
oops...my bad
thanks
...could you be a bit more clear? what is the problem with the instructions? thanks in advance.
senor_coconut said:
...could you be a bit more clear? what is the problem with the instructions? thanks in advance.
Click to expand...
Click to collapse
it doesnt matter really since this method doesnt work.....i9001 doesnt have that file!
Hi,we are awaiting a new method..........
sakindia123 said:
it doesnt matter really since this method doesnt work.....i9001 doesnt have that file!
Click to expand...
Click to collapse
Or we don't see it.
promi said:
Or we don't see it.
Click to expand...
Click to collapse
As u say maybe it`s hidden
Try to root your phone and install ES File Explorer from Market.
Maybe u will find it
I know that root is needed to access /efs.
I just stated that maybe this file is hidden somewhere.
EFS doesn't exist in I9001
The problem is that despsite you are toot and you can navigate through this folder, it seems to be almost empty and the NV_DATA.bin is not found inside.
Regards
Related
Its a free Root Explorer without Ads and without network use.
When busybox and root modes are enabled, you can make dumps of your nand partitions and export Kernel and initramfs (Menu/Tools)
{
"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"
}
https://market.android.com/details?id=fr.wdscript.yaffsexplorer
You can report here bug and feature requests...
Example : Dump and Rename The /cdrom partition (p17)
change dump file ext from .raw to .iso and you get your Windows drivers (MotoHelper 2.0.44 Driver 4.9.0 - 27 Jan 2011)
Version 1.9.9.8 attached
Awesome thanks, will def check this out.
useful tool
How can i dump the roofs?
can i restore it after backup?
Thank you.
This tool execute this command :
dd if=/dev/block/<partition> of=/sdcard/<partition>.raw ibs=8192 obs=8192 conv=notrunc
So you can do the reverse command (not in the tool because dangerous)
Update v1.1 : You can create yaffs images now
Epsylon3 said:
This tool execute this command :
dd if=/dev/block/<partition> of=/sdcard/<partition>.raw ibs=8192 obs=8192 conv=notrunc
So you can do the reverse command (not in the tool because dangerous)
Click to expand...
Click to collapse
Do you know, how to dump and remount the rootfs?
Thank you.
in fact, i dont know... rootfs is mounted before android (initrd on some devices)
Epsylon3 said:
in fact, i dont know... rootfs is mounted before android (initrd on some devices)
Click to expand...
Click to collapse
Ok, thank you.
Ok, been using this for a while now; couple suggestions.
1. Copy feature needs to work more like Root Explorer.
---- So when you long-press and copy a file, two buttons popup, Paste and Cancel - Maybe you could even add a third to paste quickly to a favourites folder without leaving working directory ?
2. Be able to change text size of file browser. I have big fingers heh.
3. Have a Mount/Unmount button similar to the Mount R/W in Root Explorer.
--- I find I cant copy anything to anywhere, am I just missing something ?
4. Select multiple files, and copy, delete, zip, move . . . . . to favourites ?
5. Compress files or folders and save zip to a saved favourites without leaving working directory.
6. Load apk icons maybe; easier to find things sometimes.
7. Show favourites picker on program startup. I'm always working in the same directories.
A built in text editor with line numbers would be awesome. Maybe an sqlite editor addon too ?
I like what this looks like so far; I really like that you can see symlinks, the dropdown with recent paths, nandroid dumps of any partitions (nice), and the favorites are cool. Just hoping it can take over for root explorer.
Keep up the great work so far. Will be keeping on eye on this for sure.
Thanks for your report
First, i dont want to copy Root Explorer or all these slow and "3 lines" explorers... So no image/movies preview... This tool is focused on system files exploration
Apk icons maybe but not in my prority (filter by name is nice), line size : not for the moment (maybe a zoom or something later)
The multiselect on click is almost ready (for files), to keep folder navigation
the Mount/Unmount will be in tools menu later (in mounted devices menu) i need to make a new window for that... but that need work (and could make lot of reports from unknown devices, like chinese ones)
Compression.... yea hmm v2.0
Hm. I tried this, but it is a lot slower than Root Explorer. Perhaps this is because it shows a lot more objects, or due to it having a lot of features I do not directly associate with a program to manage files. Still, I can not say that having more competition is a bad thing, so keep up the good work
its because the tool use a terminal process to list folders, and a new one on each refresh... I think i can optimize that if i keep the shell process opened.
but Root enabled, its 5x slower (220ms instead of 40ms)... i think there could be a problem with superuser tool, will try to uninstall it to check...
johnw.xda said:
Do you know, how to dump and remount the rootfs?
Thank you.
Click to expand...
Click to collapse
to remount In fact like others :
Code:
mount -o rw,remount,relatime -t rootfs rootfs /
This feature will be available in some minutes (v1.3.0)
But to dump... you need to skip /proc /tmp and /sys
Hi.
I´m using your app in a Samsung galaxy S.
I lost one file and I want to recover it from a CWM backup.
Your app lets me read the backup, but I cant save the needed file ...
Is there a possibility to extract it from the backup?
Thanks in advance
Its the next step yaffs extraction...
sorry, not for the moment (but soon)
just made an update v1.3.2 which really enhance exploration speed...
I hope you release it soon
Thanks
I can't Dump Partition. A circular thing shows up then it disapear and no text saying records in+out and that it finished (like in the screenshot). And there is no file on my SD card and yes I have plenty of space.
Tried several of the small 512k partitions and the Boot and Recovery partitions.
I'm running rooted froyo 3.4.2-155, few bloat APK's removed.
this feature uses busybox "dd" applet, try to set another busybox in setting window
you can search for them in other apps, do a search in /data/data/
Namiga said:
Hi.
I´m using your app in a Samsung galaxy S.
I lost one file and I want to recover it from a CWM backup.
Your app lets me read the backup, but I cant save the needed file ...
Is there a possibility to extract it from the backup?
Thanks in advance
Click to expand...
Click to collapse
Done... in v1.5.0 Single file or Folder for the moment... (file/folder context menu)
full extraction will be possible in next version... not linked
I found an easy method to unlock the i9003.
To do this you will need an Hexadecimal editor and have root access to your phone.
Steps:
1. Make a full backup of the /efs folder
2. Get the nv_data.bin file located in /efs
3. Open it with an hexa editor (I used WinHex)
4. Go to line 181460 and modify from 01 00 00 00 00 to 00 00 00 00 00
5. Copy the modified nv_data.bin file into /efs
6. Set the appropiate owner user and group doing chown 1001.1001 nv_data.bin
7. Remove the nv_data.bin.md5 file
8. Reboot your phone
9. Enjoy!!
Locked
{
"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"
}
Unlocked
ADB commands:
# su
# cd /efs
# cp /sdcard/nv_data.bin /efs/nv_data.bin
# rm nv_data.bin.md5
# chown 1001.1001 nv_data.bin
# reboot
To check it you can do *#7465625# and verify that Network Lock is [OFF]
I hope it can be useful for you.
after installing a new ROM and unlocking like this could the phone read my SIM card normally ?? (i'm in north africa - Tunisia)
Depends if your phone is region locked. Normally it shouldn't be locked, but some carriers with plans lock the phone
Thanks!! It works fine on my phone.
nice job man.. it works fine
Thanks!
It worked perfectly!
It works. Fantastic solution
Nice Work Man!!
Sent from my GT-I9003 using Tapatalk 2
It works! You are a good man
Man my file has only got 2 lines written.... what can be the problem? Im copying the efs folder in my SDcard, then i choose the called file and it has 32 bytes. only 2 lines written.. Any helps?
i cant ...
the file nv_data.bin.md5 reappears after a reboot
aaaaand nothing happens, a password is required for unlock again
can you help?
Can you upload or give to me your file nv_data.bin??
I try to generate to you a pin unlock code.
This is an experiment, unlock code may be not working.
We try to do, it is only a number PIN to insert.
i made it, thanks
but in 68 stroke
Well! How did you do?
Worked like a charm!! Thanks tons!
Hey fyter, can u help me to unlock the region on i9003.
I bought an i9003 from Africa/Tanzania, but the problem is i cant use it in any other country.
I can use any network in Tanzania, but outside of Tanzania its not showing the network.
Also its not even asking any unlock code.
It seems that the region is locked.....
To begin with, you need a hex editor, HxD - Freeware Hex Editor is a great editor and it is very small(less than an MB). Then you need a baseband to edit, you need to locate the file named ' appsboot.mbn '.
{
"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"
}
That file contains the partition tables, remember this tutorial is about editing the partition tables not extending your physical memory.
So, lets get cracking. Open HxD from programs and open the appsboot.mbn file, now press F3 and search for ' cache ' and press F3 until you see something like this
.
As you can see the highlighted section of the picture
,
there are a few repetitions of ' F0 F0 F0 F0 xx ' multiple times, you are concerned with only the first two /system and /cache partitions respectively.
Remember, you don't need to specify the partition size for /data as it is done automatically when you flash the baseband.
Now back to the hex editing part, once you've decided how much space(in MBs only) you wanna allocate to /system and /cache use this link to Convert hex/dec and select the two digits after the F0 F0 F0 F0 like in this pic
and type the hex number for example in the screenshot B4 in hex equals 180 in decimal, which means /system is allocated 180 MB of space and do the same with Cache, I would recommend allocating 10 MB to it as you hardly ever use it. Then flash the baseband like you normally do through Fastboot.
If you have any doubts ask me and I will do my best to clear things to you. Click Thanks if I helped you, doesn't cost anything
Anil_Sharma said:
To begin with, you need a hex editor, HxD - Freeware Hex Editor is a great editor and it is very small(less than an MB). Then you need a baseband to edit, you need to locate the file named ' appsboot.mbn '.
That file contains the partition tables, remember this tutorial is about editing the partition tables not extending your physical memory.
So, lets get cracking. Open HxD from programs and open the appsboot.mbn file, now press F3 and search for ' cache ' and press F3 until you see something like this
.
As you can see the highlighted section of the picture
,
there are a few repetitions of ' F0 F0 F0 F0 xx ' multiple times, you are concerned with only the first two /system and /cache partitions respectively.
Remember, you don't need to specify the partition size for /data as it is done automatically when you flash the baseband.
Now back to the hex editing part, once you've decided how much space(in MBs only) you wanna allocate to /system and /cache use this link to Convert hex/dec and select the two digits after the F0 F0 F0 F0 like in this pic
and type the hex number for example in the screenshot B4 in hex equals 180 in decimal, which means /system is allocated 180 MB of space and do the same with Cache, I would recommend allocating 10 MB to it as you hardly ever use it. Then flash the baseband like you normally do through Fastboot.
If you have any doubts ask me and I will do my best to clear things to you. Click Thanks if I helped you, doesn't cost anything
Click to expand...
Click to collapse
Thanks ws waiting fr this frm a long tym
Great Guide keep going on...........
@everyone instead of quoting whole OP ..
you can just type @op
The Droid Master said:
Great Guide keep going on...........
Click to expand...
Click to collapse
Usb diagnostics port change next Too many people fall for that
AMAZING GUIDE.... BLOWN MY MIND OFF !!!! :laugh:
good
OK first thing first IM NOT RESPONSIBLE IF YOU BRICK YOUR DEVICE OR DECIDE TO BE CARELESS OR CREATE A CYCLONE... you know the drill.
Well i stumbled on this by mistake and hey it works!!!!
Some of us do get bored with seeing the same thing over and over again specailly if u keep switching on and off your phone for whatever reason...
we can change boot animations thats popular but now we can the splash screen and by splash screen i mean boot logo and by bootlogo i mean that image that show "Samsung Galaxy **** powered by android"
Samsung stores its boot files in Param Partition but extracting those images is a hustle well now you dont have to... Here's How and its easy...
I dont know if it will work for any other device with a param partition but i am using Samsungs
YOU WILL NEED:
- A rooted device (Samsung)
- Terminal emulator or ADB (I used ADB but still i was at adb shell)
- Being able to check your partition (But ill explain how anyway)
HOW TO
CHECKING PARTITION BLOCK
1.a First check which block is your Param partition
use and root browsing app and goto /dev/platform/****/by-name
where i used *** is where things differ... there are usually two folder and one will have a folder named "by-name"...
take note of the full path to by-name
E.g in my j7 its: /dev/block/platform/13540000.dwmmc0/by-name
1.b In ADB type "adb shell"
now in Terminal or Continue in ADB
- run "ls -l /dev/block/platform/****/by-name"
- It will output all your block partition with their names
- Take the name of your mmcblk*** and mine is mmcblk0p9
NOTE : BACKUP YOUR ORIGINAL PARAM PARTITION
In Terminal or adb shell:
$ su
# dd if=/dev/block/mmcblk*** of=/data/media/0/param.fls
or dd if=/dev/block/mmcblk*** of=/storage/extSdCard/param.fls
-------- on of="Location to your sdcard (ext or int)" Dont use linked storages
Getting another device's Param file (The Boot logo you want)
Backup its PARAM partition by doing The steps above (Get block partition name and extract)
CHANGING YOUR BOOTLOGO[/COLOR]
-Copy the param.fls file you backed up to your device and note the location you put it (Dont overwrite your original)
In Terminal or adb shell
$ su
# dd if=location_param_file_you_copied/param.fls of=your_dev_block_partition
e.g
# dd if=/data/media/0/copied/param.fls of=/dev/block/mmcblk***
to restore your original change your bootlogo by your original Param.fls
image
{
"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"
}
vide:
https://youtu.be/st-VIeW4u2M
CHECKOUT POST 2 BEFORE ....
Downloads on Post 3
NOTICE's
PRO's
- You can change bootscreen to any other samsung you wish
-it will also change recovery and download mode images ... i think
CON's
- Dont know what else the param partition is for.... e.g dont know the side effects
---------- have you had any on your phone????
******** NO, i havent
- PARAM is a partition, it has a size... your stock param size is your partition size...
E.G Param from j7 is 8MB and that from Tab3 is 2MB... meaning Tab 3 param can fit and work in j7 but j7 param cannot work in Tab3
- Screen Size matters... if a bootlogo is too big for your screen itll will be small etc in order to fit
What if i wanna modify the image???
i managed to do this...
1. Create an empty archieve and put in in your phone
In Terminal or adb shell:
$ su
# dd if=/data/media/0/param.fls of=/data/media/0/archieve.zip
after this, all the images will be on the zip... N.B not in... On the zip
you can view them in the zip and extract them but you cannot add files to the archieve thats the problem...
7z says ... There are files at end of archieve (Not quite sure but something like that):
so thats where you guys and devs come in... making that zip addable...
if you extract the zip and compress it again... its size drops and if you flash it... it removes the boot image.
reserved
Downloads: PARAM by Other people
PARAM upload and download thread here
If you have question and/or answers... feel free :good:
can't modify image on j5 2016. I create archieve.zip but it say corrupted archive on any archive manager. I want old boot logo.jpg, any other way? decrypt, extract, convert param.lfs...??
How to modify param file in tab S6 ??
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.