Database Info

App2sd error

After moving the folders (app, app-private, data, dalvik-cache) to the sd, it seems I cannot write to it, only read.
for the symlinks, the permissions are: root.root lrwxrwxrwx (777)
for the folders on sd, the permissions are: system.system drwxrwx--x (771)
Are these the permissions you guys have on your g1?
Symptoms:
- cant download apps
- receive mms but cant download pics

Mine are:
drwxrwx--x 2 1000 1000 4096 Apr 15 13:43 app
drwxrwx--x 2 1000 1000 4096 Apr 8 21:39 app-private
drwxrwx--x 2 1000 1000 8192 Apr 15 13:43 dalvik-cache
drwx------ 2 0 0 16384 Apr 7 17:28 lost+found
What method did you use to copy over the files? It would appear that the permissions did not get transferred.

daveid said:
Mine are:
drwxrwx--x 2 1000 1000 4096 Apr 15 13:43 app
drwxrwx--x 2 1000 1000 4096 Apr 8 21:39 app-private
drwxrwx--x 2 1000 1000 8192 Apr 15 13:43 dalvik-cache
drwx------ 2 0 0 16384 Apr 7 17:28 lost+found
What method did you use to copy over the files? It would appear that the permissions did not get transferred.
Click to expand...
Click to collapse
I believe the permissions were transfered right. just in case though, I chown the directories to system.system .
what does your symlinks show in /data/?
*edit* I did it through the recovery console with instructions from this post
*edit 2* I got mms to work by the chmod'ing the dirs. Looks like a lot more people are having issues with the market place so this may not be causing the issue.

lchanmanl said:
After moving the folders (app, app-private, data, dalvik-cache) to the sd, it seems I cannot write to it, only read.
for the symlinks, the permissions are: root.root lrwxrwxrwx (777)
for the folders on sd, the permissions are: system.system drwxrwx--x (771)
Are these the permissions you guys have on your g1?
Symptoms:
- cant download apps
- receive mms but cant download pics
Click to expand...
Click to collapse
Only superuser and the owner(the app itself) should be able to write anything to those. So it looks like permissions are o.k. to me. For the not downloading problem, it seems google is upgrading the market and downloads are going crazy slow(11 hours for an app) for people with the cupcake builds. You might be experiencing this. Not sure about the MMS stuff, haven't ever sent or received an mms.
EDIT: nm, didn't read the post right above mine...

Google Blocks Cupcake From Market
[email protected] said:
Only superuser and the owner(the app itself) should be able to write anything to those. So it looks like permissions are o.k. to me. For the not downloading problem, it seems google is upgrading the market and downloads are going crazy slow(11 hours for an app) for people with the cupcake builds. You might be experiencing this. Not sure about the MMS stuff, haven't ever sent or received an mms.
EDIT: nm, didn't read the post right above mine...
Click to expand...
Click to collapse
http://www.boygeniusreport.com/2009...gle-blocks-cupcake-users-from-android-market/

[Q] Building Harmony/GTablet CyanogenMod from source?

I'm getting pretty far along building CyanogenMod for the GTablet on Mandriva Linux x86_64, I pulled the latest source and did the following from a bash shell:
Code:
cd device/nvidia/harmony
./extract-files.sh
cd ../../..
cp ./vendor/cyanogen/products/cyanogen_harmony.mk ./buildspec.mk
. build/envsetup.sh
lunch cyanogen_harmony-eng
cd vendor/cyanogen
./get-rommanager
./get-google-files -v hdpi
cd ../..
make -j6 CYANOGEN_WITH_GOOGLE=true bacon
I'm wondering if I should have gotten the mdpi-tegra google apps instead? get-google-files requires the following change if so:
Code:
FILENAME=["gapps-hdpi-20101114-signed.zip","gapps-mdpi-20101020-signed.zip","gapps-mdpi-tiny-20101020-signed.zip","gapps-mdpi-tegra-20101020-signed.zip"]
VERSIONS=["hdpi","mdpi","mdpi-tiny","mdpi-tegra"]
then do:
Code:
./get-google-files -v mdpi-tegra
Has anyone gotten this working?

I'm almost 100% positive that you cannot use HDPI gapps. MDPI gapps are the ones that you need to use for CM6.1 for this device.

Good to know, I just got it built but now clockwork doesn't see the update-cm-6.1.0-Beta4-Harmony-signed.zip on the sdcard?!? I can mount and verify the .zip from linux, the file should be in the root directory, correct?
Weird, I tried copying over the clockwork update.zip and recovery/ dirs, now I can see LOST.DIR but nothing else from the recovery install from sdcard option...

Dumb question....but did you mount the sdcard? I've seen that happen if the card is not mounted to /sdcard

Possible /sdcard and /sdcard2 mount confusion?

Nope, from adb shell I can see /mnt/sdcard with the files (which match md5 checksums):
Code:
# ls -lF /mnt/sdcard
d---rwxr-x 3 system sdcard_r 4096 Jan 25 06:51 Android/
d---rwxr-x 2 system sdcard_r 4096 Jan 25 06:51 LOST.DIR/
d---rwxr-x 2 system sdcard_r 4096 Oct 29 2010 recovery/
----rwxr-x 1 system sdcard_r 83928334 Dec 5 2010 update-cm-6.1.0-Beta4-Harmony-signed.zip*
----rwxr-x 1 system sdcard_r 4003082 Nov 9 2010 update.zip*
Is there anything special that needs to be done with permissions? I did have to repartition the sd card, somehow it got really messed up when I tried formatting it from the tablet's setup app.
edit: I found out that the .zip needs to be on /mnt/emmc (which I guess shows up as sdcard from clockwork recovery).

[Q] Fresh ROM for Evo Shift 4G: Keeps Resetting

I've installed Fresh ROM on my Evo Shift 4G. It worked for about a week, then the GPS stopped working (a known bug with this device and Gingerbread). I restarted the device as normal, and when it came back up all my downloaded apps and the Market were gone, and the device was in that strange indeterminate state where I'm both synced to a Gmail account and not at the same time (the Setup app appears in the Apps folder). Signing in doesn't help.
I rebooted into Clockwork Recovery (3.2.0.1), wiped data/factory reset, wiped the cache, wiped dalvik, and installed Fresh ROM again.
Once that was complete and booted, I signed in, attempted to install an app and the phone reset. There's no file manager installed nor terminal app so I can't delete things by bash. I connected over USB and tried to adb shell in, but that caused the phone to reset.
I'm stuck. Clearly something has not been properly wiped prior to installing Fresh ROM.
What do I need to do to get out of this loop?

SoopahMan said:
I've installed Fresh ROM on my Evo Shift 4G. It worked for about a week, then the GPS stopped working (a known bug with this device and Gingerbread). I restarted the device as normal, and when it came back up all my downloaded apps and the Market were gone, and the device was in that strange indeterminate state where I'm both synced to a Gmail account and not at the same time (the Setup app appears in the Apps folder). Signing in doesn't help.
I rebooted into Clockwork Recovery (3.2.0.1), wiped data/factory reset, wiped the cache, wiped dalvik, and installed Fresh ROM again.
Once that was complete and booted, I signed in, attempted to install an app and the phone reset. There's no file manager installed nor terminal app so I can't delete things by bash. I connected over USB and tried to adb shell in, but that caused the phone to reset.
I'm stuck. Clearly something has not been properly wiped prior to installing Fresh ROM.
What do I need to do to get out of this loop?
Click to expand...
Click to collapse
Sounds like you either had a bad Flash, a bad Download, or both. So redownload the Rom you choose, then Clear and Flash your device according to THESE INSTRUCTIONS .

Thanks for the response. I downloaded the ROM again and ran a check - identical to the file I downloaded previously. So, if the ROM is the culprit, then the latest version of Fresh ROM for Evo Shift does not work (4.1.1).
I followed the instructions linked, wiping the cache and dalvik-cache twice (why?), and wiping system etc prior to installing the ROM.
I'm running into the exact same issues as before - I can't install anything from the Market, and the phone resets if I connect it to a computer over USB. When it resets, it resets multiple times and when it comes back up the 4G no longer works.
If I rerun the above instructions, the 4G works again, but I'm stuck back in this loop - can't use the Market or connect it over USB or it will reset, so forth.
Could Fresh ROM 4.1.1 for Evo Shift be bad? I still suspect the real problem is something is not sufficiently wiped or setup prior to install.
In case it might help, here's an ls -al after installing Fresh Rom 4.1.1 on my phone (an HTC Evo Shift 4G after following the above install instructions).
/
drwxr-xr-x 2 root root 0 Jan 17 07:39 boot
drwxr-xr-x 4 root root 1024 Jan 17 07:41 cache
drwxrwx--x 2 root root 0 Jan 1 1970 data
drwxr-xr-x 2 root root 0 Jan 17 07:39 datadata
-rw-r--r-- 1 root root 3462 Jan 1 1970 default.prop
drwxr-xr-x 12 root root 3060 Jan 17 07:39 dev
drwxr-xr-x 2 root root 0 Jan 17 07:39 emmc
drwxr-xr-x 2 root root 0 Jan 17 07:39 etc
-rwxr-x--- 1 root root 94372 Jan 1 1970 init
-rwxr-x--- 1 root root 899 Jan 1 1970 init.rc
dr-xr-xr-x 79 root root 0 Jan 1 1970 proc
drwxr-xr-x 4 root root 0 Jan 1 1970 res
drwx------ 2 root root 0 May 15 2011 root
drwxr-x--- 2 root root 0 Jan 1 1970 sbin
drwxr-xr-x 2 root root 0 Jan 17 07:39 sd-ext
drwxrwxrwx 78 root root 32768 Jan 1 1970 sdcard
drwxr-xr-x 18 root root 0 Jan 17 07:39 sys
drwxr-xr-x 3 root root 0 Jan 1 1970 system
drwxr-xr-x 2 root root 0 Jan 17 07:45 tmp
-rw-r--r-- 1 root root 0 Jan 1 1970 ueventd.goldfish.rc
-rw-r--r-- 1 root root 4027 Jan 1 1970 ueventd.rc
-rw-r--r-- 1 root root 987 Jan 1 1970 ueventd.speedy.rc
/data
(empty)
/system
drwxr-xr-x 2 root root 0 Jan 1 1970 bin
/system/bin
(empty)
/sys
drwxr-xr-x 2 root root 0 Jan 17 07:53 android_camera
drwxr-xr-x 2 root root 0 Jan 17 07:53 android_camera_awb_cal
drwxr-xr-x 2 root root 0 Jan 17 07:53 android_touch
drwxr-xr-x 2 root root 0 Jan 17 07:53 block
drwxr-xr-x 2 root root 0 Jan 17 07:39 board_properties
drwxr-xr-x 9 root root 0 Jan 17 07:53 bus
drwxr-xr-x 2 root root 0 Jan 17 07:53 camera_led_status
drwxr-xr-x 47 root root 0 Jan 17 07:53 class
drwxr-xr-x 4 root root 0 Jan 17 07:53 dev
drwxr-xr-x 10 root root 0 Jan 17 07:39 devices
drwxr-xr-x 2 root root 0 Jan 17 07:53 firmware
drwxr-xr-x 3 root root 0 Jan 17 07:53 fs
drwxr-xr-x 6 root root 0 Jan 17 07:53 kernel
drwxr-xr-x 62 root root 0 Jan 17 07:53 module
drwxr-xr-x 2 root root 0 Jan 17 07:53 power
drwxr-xr-x 2 root root 0 Jan 17 07:53 systemlog
I can post more or other diagnostics if others have something to recommend. Really stuck here.

Is it odd that /sd-ext is at root and not located on the SD card, and a directory not a symlink?

Now that you have 10 posts you should try posting your questions in the thread for flipz's rom.So the dev can help and maybe anyone else that is running this rom. Also have you tried the a2sd remove command adb shell or from terminal emulator? See if that helps.
Sent from my PG06100 using Tapatalk

A bit more to isolate the problem:
If the phone resets (due to attempting an install from the Market or plug in from USB), 4G fails - but if I restart the phone at that point, when it reboots 4G works again. So 4G appears to be fine, it's the resets that are at the core of the issue.
I shutdown, removed the SD card, booted, and attempted to install an app and got the same reset, so it's not the SD card - it's definitely a problem somewhere on internal storage.
What else do I need to clear to clear this up?
Fresh ROM's pages say to look in /data/app and /system/app for a place where an app already exists that would cause a conflict.
Here's /data after booting the ROM and setting up a Gmail account:
lrwxrwxrwx 1 root root 14 Jan 17 07:54 app -> /system/sd/app
lrwxrwxrwx 1 root root 22 Jan 17 07:54 app-private -> /system/sd/app-private
drwx------ 5 system system 1024 Jan 6 1980 backup
drwxrwx--x 2 system system 14336 Jan 17 16:25 dalvik-cache
drwxrwx--x 161 system system 9216 Jan 17 07:57 data
drwxr-x--- 2 root log 1024 Jan 17 07:54 dontpanic
lrwxrwxrwx 1 root root 11 Jan 17 07:54 drm -> /data/local
-rw-r--r-- 1 root root 6134 Jan 6 1980 dta2sd.lg1
-rw-r--r-- 1 root root 6266 Jan 6 1980 dta2sd.lg2
-rw-r--r-- 1 root root 6266 Jan 6 1980 dta2sd.log
drwxrwxrwx 2 root root 1024 Jan 17 07:54 htcfs
drwxr-xr-x 4 root root 1024 Jan 17 07:42 jit
drwxrwx--x 4 shell shell 1024 Jan 17 07:54 local
drwxrwx--- 2 root root 12288 Jan 17 07:41 lost+found
drwxrwx--t 10 system misc 1024 Jan 17 07:55 misc
drwx------ 2 root root 1024 Jan 6 1980 property
drwx------ 3 system system 1024 Jan 17 07:55 secure
drwxrwxr-x 9 system system 1024 Jan 17 17:48 system
drwxrwx--- 3 system system 1024 Jan 17 17:14 wimax
I'd like to know if app and app-private are as expected (they appear to be the result of the ROM install, since they were completely wiped prior to installing it). The app symlink is a strange one. It points to /system/sd/app, which I can't cd to. /system/sd I can cd to, and this is all it contains:
-rw-r--r-- 1 root root 17 Aug 1 2008 placeholder
A file named placeholder. What?
I'm starting to suspect apps2sd. None of the relevant partitioning steps are in those install instructions, and they appear to be specific to the apps2sd of CyanogenMod. Google's appears to support a DOS partition, while CyanogenMod's appears to only support an ext3 partition, which I do not have.
At the same time, removing the SD card didn't change things, so color me confused.

As suggested by FdxRider you should definately post up in the Rom thread. That way you can get help resolving the issue from others running the same Rom.

It was apps2sd.
To resolve this problem, I had to:
Reboot into ClockwordModRecovery
Connect the phone to a computer over USB
In Clockwork, choose Mount Storage and choose the last option, Mount USB.
Dump anything I wanted to keep off of the SD card (most importantly, the FreshRom zip file).
Then, back in Clockwork, Advanced>Partition SD
Choose a size (they recommend 1024M)
This wipes out everything on the SD card, creates a Linux partition for apps2sd to use, marks the rest as a Windows partition.
Wait till it's done, then, still from ClockworkModRecovery:
Wipe cache, dalvik cache, system, data
Factory reset
Now Mount USB again so you can copy the FreshRom zip back onto the Windows partition (the only part that will come up on a Windows machine).
Eject on the Windows machine to ensure the copy completes, Unmount in Clockwork.
Install the ROM again
Let it boot, restart
Setup my Google Account/Gmail user
And one final thing:
As it turns out ES File Explorer is pre-installed on this ROM. That means installing it from the Market will make the phone go crazy regardless of proper setup. But I am now able to install other apps just fine from the Market (at last).

reset loop NO clockwork until factory reset
I installed Fresh 4.1.1 on my shift 4g
I went to install ROM Manager got it downloaded and it reset the phone at install.
I even tried going to the website and installing it that way. Same results.
I can't get clockwork to work, when i hold the volume down and then press power nothing happens until i release the power button then it goes directly to the Fresh install.
PLEASE HELP!!!!
---------- Post added at 05:30 AM ---------- Previous post was at 05:09 AM ----------
I got the problem solved. I used the RRU and it walked me through a recovery, part of it was yanking the battery. DUH!

[F2FS / EXT4] LineageOs 14.1 For General Mobile 5+

{
"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"
}
Code:
/* Disclaimer
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app failed. Please do some research
* if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you blame me in any way for what happens to your device, I will laugh at you.
* BOOM! goes the dynamite
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 7 (nougat), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
What's working :
*Boots
*Touch
*RIL [Calls, Mobile Data, Dual SIM]
*Wifi
*Wifi Tethering
*Bluetooth
*Camera
*Camcorder
*Audio
*Sensors
*Flash
*GPS
*Notification LED
*OTG
*VoLTE (comming soon)
*FM Radio
Instructions :
Download the latest build and GApps
* Reboot to recovery
* Wipe data/factory reset
* Flash the latest build and GApps
* Reboot
* If you want to root LineageOS, take a look at this thread:
Requriment TWRP: https://mega.nz/#!qwdXjRYB!0Ka5rwLU8ev-5bRYA9M0sFx_3xnCFIGaZXNt03JjNrA
Download Link:
Mega.nz
XDA:DevDB Information
[F2FS / EXT4] LineageOs 14.1 For General Mobile 5+, ROM for the General Mobile GM 5 Plus
Contributors
kaankulahli, wzedlare
Source Code: https://github.com/OneDeveloperOrganization/
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: LineageOS
Version Information
Status: Stable
Current Stable Version: 1.0
Created 2016-09-25
Last Updated 2017-07-04

@ kaankulahli achievements

oyş As Byraklari As

Has been sources released or will be? Where I could access them?

berkantkz said:
Has been sources released or will be? Where I could access them?
Click to expand...
Click to collapse
not yet, maybe next days.

kaankulahli said:
not yet, maybe next days.
Click to expand...
Click to collapse
Can I see the sources? I might help you

send a private message.

Right now, All of the hardware problems are fixed.

Fixed minor bugs . (Microphone)

Download link is broken.

links renewed.

kaankulahli said:
links renewed.
Click to expand...
Click to collapse
sorry download link still broken

Oops, new links added .

in recovery "twrp-3.0.2-1-shamrock" i did a full wipe/factory reset,
and flashed cm_shamrock-ota-38062b8f0f.zip (14.0-20161004-unofficial-shamrock) + open_gapps-arm-7.0-mini-20161005.zip,
then did a wipe dalvik+cache, and boot system.
now i got these 2 errors:
- android system -there's an internal error with your device, contact your manufacturer for details. then i just entered through
- SIM card missing. a sim card has not been detected in our phone
system is running nicely with Wifi, but "no sim card detected".
in settings i noticed that there's a Unknown Baseband version.
i did a TWRP-restore of my previous twrp-backup: cm-13.0-20160912-UNOFFICIAL-shamrock-by-turkdevs ,
now everything works normal again.
how to solve the above errors?

7dwergen said:
i did a full wipe/factory reset, and flashed cm_shamrock-ota-38062b8f0f.zip + open_gapps-arm-7.0-mini-20161005.zip, wipe dalvik+cache, did boot system.
then i got these 2 errors:
- android system -there's an internal error with your device, contact your manufacturer for details. then i just entered through
- SIM card missing. a sim card has not been detected in our phone
system is running nicely with Wifi, but no sim card detected. in settings i noticed that there's a Unknown Baseband version.
i did a restore of the previous cm-13.0-20160912-UNOFFICIAL-shamrock-by-turkdevs.zip , this rom works normal.
how to solve the above errors?
Click to expand...
Click to collapse
Please install 7.0 stock and transfer to cm from stock rom.

7dwergen said:
in recovery "twrp-3.0.2-1-shamrock" i did a full wipe/factory reset,
and flashed cm_shamrock-ota-38062b8f0f.zip (14.0-20161004-unofficial-shamrock) + open_gapps-arm-7.0-mini-20161005.zip,
then did a wipe dalvik+cache, and boot system.
now i got these 2 errors:
- android system -there's an internal error with your device, contact your manufacturer for details. then i just entered through
- SIM card missing. a sim card has not been detected in our phone
system is running nicely with Wifi, but "no sim card detected".
in settings i noticed that there's a Unknown Baseband version.
i did a TWRP-restore of my previous twrp-backup: cm-13.0-20160912-UNOFFICIAL-shamrock-by-turkdevs ,
now everything works normal again.
how to solve the above errors?
Click to expand...
Click to collapse
Can you paste a screenshot from the partitions that you've backed up?

berkantkz said:
Can you paste a screenshot from the partitions that you've backed up?
Click to expand...
Click to collapse
there it is;
/external_sd/TWRP/BACKUPS/d9e7aab0 # ls -la 2016-10-05--17-10-15_cm_shamrock-use
rdebug_6.0.1_MOB31E_2e9510ad/
drwxrwxrwx 2 media_rw media_rw 4096 Oct 5 2016 .
drwxrwxrwx 5 media_rw media_rw 4096 Oct 5 2016 ..
-rw-rw-r-- 1 media_rw media_rw 67108864 Oct 5 2016 boot.emmc.win
-rw-rw-r-- 1 media_rw media_rw 48 Oct 5 2016 boot.emmc.win.md5
-rw-rw-r-- 1 media_rw media_rw 786587720 Oct 5 2016 data.ext4.win000
-rw-rw-r-- 1 media_rw media_rw 51 Oct 5 2016 data.ext4.win000.md5
-rw-rw-r-- 1 media_rw media_rw 185203104 Oct 5 2016 data.ext4.win001
-rw-rw-r-- 1 media_rw media_rw 51 Oct 5 2016 data.ext4.win001.md5
-rw-rw-r-- 1 media_rw media_rw 65 Oct 5 2016 data.info
-rw-rw-r-- 1 media_rw media_rw 88080384 Oct 5 2016 modem.emmc.win
-rw-rw-r-- 1 media_rw media_rw 49 Oct 5 2016 modem.emmc.win.md5
-rw-rw-r-- 1 media_rw media_rw 3182671 Oct 5 2016 oem.ext4.win
-rw-rw-r-- 1 media_rw media_rw 47 Oct 5 2016 oem.ext4.win.md5
-rw-rw-r-- 1 media_rw media_rw 59 Oct 5 2016 oem.info
-rw-rw-r-- 1 media_rw media_rw 1867443 Oct 5 2016 recovery.log
-rw-rw-r-- 1 media_rw media_rw 11534336 Oct 5 2016 splash.emmc.win
-rw-rw-r-- 1 media_rw media_rw 50 Oct 5 2016 splash.emmc.win.md5
-rw-rw-r-- 1 media_rw media_rw 649600246 Oct 5 2016 system.ext4.win
-rw-rw-r-- 1 media_rw media_rw 50 Oct 5 2016 system.ext4.win.md5
-rw-rw-r-- 1 media_rw media_rw 65 Oct 5 2016 system.info
/external_sd/TWRP/BACKUPS/d9e7aab0 #

kaankulahli said:
Please install 7.0 stock and transfer to cm from stock rom.
Click to expand...
Click to collapse
did you mean this 7.0 stock rom ?
https://www.androidfilehost.com/?w=files&flid=96107
GM_5_PLUS_DUAL_ANDROID_7.0_NOUGAT_OTA_BY_TURKDEVS.zip

7dwergen said:
there it is;
/external_sd/TWRP/BACKUPS/d9e7aab0 # ls -la 2016-10-05--17-10-15_cm_shamrock-use
rdebug_6.0.1_MOB31E_2e9510ad/
drwxrwxrwx 2 media_rw media_rw 4096 Oct 5 2016 .
drwxrwxrwx 5 media_rw media_rw 4096 Oct 5 2016 ..
-rw-rw-r-- 1 media_rw media_rw 67108864 Oct 5 2016 boot.emmc.win
-rw-rw-r-- 1 media_rw media_rw 48 Oct 5 2016 boot.emmc.win.md5
-rw-rw-r-- 1 media_rw media_rw 786587720 Oct 5 2016 data.ext4.win000
-rw-rw-r-- 1 media_rw media_rw 51 Oct 5 2016 data.ext4.win000.md5
-rw-rw-r-- 1 media_rw media_rw 185203104 Oct 5 2016 data.ext4.win001
-rw-rw-r-- 1 media_rw media_rw 51 Oct 5 2016 data.ext4.win001.md5
-rw-rw-r-- 1 media_rw media_rw 65 Oct 5 2016 data.info
-rw-rw-r-- 1 media_rw media_rw 88080384 Oct 5 2016 modem.emmc.win
-rw-rw-r-- 1 media_rw media_rw 49 Oct 5 2016 modem.emmc.win.md5
-rw-rw-r-- 1 media_rw media_rw 3182671 Oct 5 2016 oem.ext4.win
-rw-rw-r-- 1 media_rw media_rw 47 Oct 5 2016 oem.ext4.win.md5
-rw-rw-r-- 1 media_rw media_rw 59 Oct 5 2016 oem.info
-rw-rw-r-- 1 media_rw media_rw 1867443 Oct 5 2016 recovery.log
-rw-rw-r-- 1 media_rw media_rw 11534336 Oct 5 2016 splash.emmc.win
-rw-rw-r-- 1 media_rw media_rw 50 Oct 5 2016 splash.emmc.win.md5
-rw-rw-r-- 1 media_rw media_rw 649600246 Oct 5 2016 system.ext4.win
-rw-rw-r-- 1 media_rw media_rw 50 Oct 5 2016 system.ext4.win.md5
-rw-rw-r-- 1 media_rw media_rw 65 Oct 5 2016 system.info
/external_sd/TWRP/BACKUPS/d9e7aab0 #
Click to expand...
Click to collapse
That's good you've backed up modem. To have sim working CM-14, wipe everything, then install CM-14 (and gapps as optional), restore the modem partition. Reboot your device. Mustafa work. And if it Works, I suggest you to back your modem partition somewhere like ön your local or Google Drive or Mega or Mediafire...
Modem includes your IMEI number. ?f you lost it, that back-up will help you. This saves your life.
Good luck. You can pm me anytime. I'm glad to help.

berkantkz said:
That's good you've backed up modem. To have sim working CM-14, wipe everything, then install CM-14 (and gapps as optional), restore the modem partition. Reboot your device. Mustafa work. And if it Works, I suggest you to back your modem partition somewhere like ön your local or Google Drive or Mega or Mediafire...
Modem includes your IMEI number. ?f you lost it, that back-up will help you. This saves your life.
Good luck. You can pm me anytime. I'm glad to help.
Click to expand...
Click to collapse
thanks a lot for your suggestion so fast, berkantkz !
but unfortunately it did not solve my problem, still the same error situation.
'think i'am doing something stupid (or not?)
so i restored the last twrp-backup with cm13, system is up and running smoothly as before..
strange, it is exactly the same error situation i got some weeks ago, after flashing: cm-13.0-20160802-UNOFFICIAL-shamrock_by-TURKDEVS.zip
afterwards i could flash: cm-13.0-20160912-UNOFFICIAL-shamrock-by-turkdevs.zip , this rom solved that problem....

Question Extracting super.img

I tried using lpunpack as suggested in Extract super.img.lz4 but once it unpacked the partitions to the output directory i was not able to open the images as archives.
Could anyone explain why this is happening?

Hey please Try Crb v14.
Link:-https://forum.xda-developers.com/t/tool-windows-kitchen-crb-v3-0-0-beta14.3947779/

nilsha said:
Hey please Try Crb v14.
Link:-https://forum.xda-developers.com/t/tool-windows-kitchen-crb-v3-0-0-beta14.3947779/
Click to expand...
Click to collapse
Since it is based out of imjtool & lpunpack it is not working.

Bump

73sla said:
I tried using lpunpack as suggested in Extract super.img.lz4 but once it unpacked the partitions to the output directory i was not able to open the images as archives.
Could anyone explain why this is happening?
Click to expand...
Click to collapse
I think they are in sparse format and you need to convert them (I think the tool is called simg2img)

73sla said:
I tried using lpunpack as suggested in Extract super.img.lz4 but once it unpacked the partitions to the output directory i was not able to open the images as archives.
Could anyone explain why this is happening?
Click to expand...
Click to collapse
Now system.img vendor.img etc are f2fs and at present most common kitchen/Tools doesnt mount it. You may try Fedora linux to mount to extrcat it, someone reported it is working.

dr.ketan said:
Now system.img vendor.img etc are f2fs and at present most common kitchen/Tools doesnt mount it. You may try Fedora linux to mount to extrcat it, someone reported it is working.
Click to expand...
Click to collapse
I tried mounting in Ubuntu without success, not sure if it's different in fedora

Using partitions backup app to backup super.img, is this super.img useful?
{
"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"
}

donkeyman1234 said:
Using partitions backup app to backup super.img, is this super.img useful?
Click to expand...
Click to collapse
Nope, it will be same like one packed in stock firmware.

dr.ketan said:
Nope, it will be same like one packed in stock firmware.
Click to expand...
Click to collapse
I see.

Bump as I still need a Windows-based solution.

The 6 imgs obtained after decompressing the super.img of S22 cannot be decompressed
Extracting system.img with Python ...
Traceback (most recent call last):
ext4.MagicError: Invalid magic value in superblock: 0x0002 (expected 0xEF53)
unbutu can not mount system.img too

which tools extract contents of system.img

Bump

Hi guys, I successfully extracted super.img using SuperR's Kitchen on linux. Good luck!

I have now unpacked the boot.img. Took me some time to figure out what Sammy had done.
Haven't done this sine my S9 and a lot has changed. Unpacking the .lz4 file was no problem, giving me a boot.img, which could not be extracted using any of my current tools...
But since I work in Linux, everything is possible.
I have some special tools installed, making it possible to run Android executables in Ubuntu tetminal. So I used Sammys own Android unpack boot image command. This gave me an unpacked boot image and a ram disk.
Again things has changed, RAMDISK is no longer packed like I used to see it, I had to unpack it with a Linux cpio command.
After all this work, just to find out that RAMDISK is more or less empty, only containing the init file, a short txt file and some empty folders.
But this work was required for me before I can build a custom kernel. Because things need to packed same way again.
Regards DeHAWK
Edit: Seems like sammy is f*cking with us. Why is the SamMobile firmware 8GB...they have done something strage and I'm about to find out. Take an example; a lz4 file is 365Kb packed, but unpacked its 8MB, don't make sense. Look at the end of the lz4 packed file.
Regards DeHAWK

SkylinesHD said:
Hi guys, I successfully extracted super.img using SuperR's Kitchen on linux. Good luck!
Click to expand...
Click to collapse
have you been able to get bin files from a vendor.img that uses f2fs as file system?

1. unpack S22's super.img ，your will get 6 imgs
2.copy system.img to your s22 phone /sdcard
3.adb shell su
4.mount -o loop /sdcard/system.img /sdcard/tmp
then you can cd /sdcard/tmp ，ls -l find all files！

tomatolei said:
1. unpack S22's super.img ，your will get 6 imgs
2.copy system.img to your s22 phone /sdcard
3.adb shell su
4.mount -o loop /sdcard/system.img /sdcard/tmp
then you can cd /sdcard/tmp ，ls -l find all files！
Click to expand...
Click to collapse
mount: bad /etc/fstab: No such file or directory
when trying the mount command

E:\tar>adb shell
b0q:/ $ su
b0q:/ # mkdir /sdcard/tmp
b0q:/ # mount -o loop /sdcard/vendor.img /sdcard/tmp
'/dev/block/loop34' is read-only
b0q:/ # cd /sdcard/tmp
b0q:/sdcard/tmp # ls -l
total 28772
drwxr-xr-x 2 root shell 4096 2021-01-01 08:00 apex
drwxr-xr-x 7 root shell 4096 2021-01-01 08:00 app
drwxr-x--x 4 root shell 20480 2021-01-01 08:00 bin
drwxr-xr-x 2 root shell 4096 2021-01-01 08:00 bt_firmware
-rw------- 1 root root 14406 2021-01-01 08:00 build.prop
drwxr-xr-x 2 root shell 4096 2021-01-01 08:00 dsp
drwxr-xr-x 40 root shell 8192 2021-01-01 08:00 etc
drwxr-xr-x 6 root shell 8192 2021-01-01 08:00 firmware
drwxr-xr-x 2 root shell 4096 2021-01-01 08:00 firmware-modem
drwxr-xr-x 2 root shell 4096 2021-01-01 08:00 firmware_mnt
drwxr-xr-x 3 root shell 4096 2021-01-01 08:00 gpu
drwxr-xr-x 10 root shell 118784 2021-01-01 08:00 lib
drwxr-xr-x 8 root shell 118784 2021-01-01 08:00 lib64
lrw-r--r-- 1 root root 4 2021-01-01 08:00 odm -> /odm
drwxr-xr-x 3 root shell 4096 2021-01-01 08:00 odm_dlkm
drwxr-xr-x 8 root shell 4096 2021-01-01 08:00 overlay
-rw-r--r-- 1 root root 29118684 2021-01-01 08:00 recovery-from-boot.p
drwxr-xr-x 5 root shell 4096 2021-01-01 08:00 rfs
drwxr-xr-x 6 root shell 4096 2021-01-01 08:00 saiv
-rw-r--r-- 1 root root 39446 2021-01-01 08:00 ueventd.rc
drwxr-xr-x 3 root shell 4096 2021-01-01 08:00 usr
drwxr-xr-x 2 root shell 4096 2021-01-01 08:00 vm-system