Database Develop

[DEV] ClockworkMod Recovery

A little preview:
{
"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"
}
sdcard doesn't get recognized yet but i'm working on that issue
The source is published at GitHub: https://github.com/SeraphimSerapis/Samsung-P7100-Recovery
UPDATE: Pershoot made the final fixes and published his working recovery here: http://droidbasement.com/db-blog

Nice work! That was damn quick!
EDIT: How hard is it to get a decent photo of these things? Impossible, I tell you!

bcmobile said:
EDIT: How hard is it to get a decent photo of these things? Impossible, I tell you!
Click to expand...
Click to collapse
That's part of the spirit
Sent from my Optimus 2X using Tapatalk

hi.
nvm..
seen your github link (i assume the stock kernel).
thx!
good work/progress

pershoot said:
hi.
nvm..
seen your github link (i assume the stock kernel).
thx!
good work/progress
Click to expand...
Click to collapse
thanks a lot yeah - it's the stock boot image i extracted.
only thing i'm not getting to work is the sdcard mounting. data/media gets mounted from the 10.1 recovery as far as i can tell, but i don't get that to work

seraphimserapis said:
thanks a lot yeah - it's the stock boot image i extracted.
only thing i'm not getting to work is the sdcard mounting. data/media gets mounted from the 10.1 recovery as far as i can tell, but i don't get that to work
Click to expand...
Click to collapse
your attempting to mount via EMMC, ext4, on mmcblk0p8?

pershoot said:
hi.
nvm..
seen your github link (i assume the stock kernel).
thx!
good work/progress
Click to expand...
Click to collapse
pershoot said:
your attempting to mount via EMMC, ext4, on mmcblk0p8?
Click to expand...
Click to collapse
Currently I'm trying this via fstab:
/data ext4 /dev/block/mmcblk0p8 length=-16384
/sdcard vfat /data/media
But that doesn't work. Perhaps it's something regarding the length.
As far as I could see the Samsung original recovery from the I/O device doesn't even mount /sdcard/ via fstab.
Perhaps we need to include a skript that does this work on recovery start.
EDIT: Tried fdisk -l to get the right partition to extract the original recovery.img but doesn't seem to be possible for me.
EDIT2: Found a skript that must be called on recovery boot. Need a way to include it..
EDIT3: Made another change to the recovery source - see https://github.com/SeraphimSerapis/Samsung-P7100-Recovery

I continued digging in the 10.1 system dump and found this in the vold file:
#dev_mount sdcard /mnt/sdcard auto /dev/fuse
dev_media_group * /mnt/sdcard/usbStorage/ auto /devices/platform/tegra-ehci.0
Perhaps there is a way to do some kind of this in the recovery.fstab as there is no vold file?
Mounting the sdcard fails currently saying this:
mount: mounting /dev/fuse on /sdcard failed: Block device required
Error mounting /sdcard

i have it mounting in CWM 3.1.01, without issue.
~ # mount /data; mount | grep "/data"; cd /data && cd /data/media && ls
mount /data; mount | grep "/data"; cd /data && cd /data/media && ls
/dev/block/mmcblk0p8 on /data type ext4 (rw,relatime,barrier=1,data=ordered)
Alarms Pictures
Android Playlists
DCIM Podcasts
Download Ringtones
Movies pulse
Music su_busybox_misc-sam_tab_10.1.zip
Notifications sys-backup

some more to do. will upload to git once done.

pershoot said:
i have it mounting in CWM 3.1.01, without issue.
~ # mount /data; mount | grep "/data"; cd /data && cd /data/media && ls
mount /data; mount | grep "/data"; cd /data && cd /data/media && ls
/dev/block/mmcblk0p8 on /data type ext4 (rw,relatime,barrier=1,data=ordered)
Alarms Pictures
Android Playlists
DCIM Podcasts
Download Ringtones
Movies pulse
Music su_busybox_misc-sam_tab_10.1.zip
Notifications sys-backup
Click to expand...
Click to collapse
Great work! We'll have a working recovery soon then
Very nice

Where are you guys at with CM Recovery? What's left to be done?

bcmobile said:
Where are you guys at with CM Recovery? What's left to be done?
Click to expand...
Click to collapse
Nandroid backups need to be fixed to not take up lots of gigs
Everything else is working fine thanks to pershoot

Cool! Nice work guys. Let me know if there is anything I can do

ill rls this today most likely for extended testing. it will be in the IO forums. it will work on the 'v' version as well.
UMS will not work, as of yet.

http://forum.xda-developers.com/showpost.php?p=14020091&postcount=1
please let me know of any issues.

pershoot said:
http://forum.xda-developers.com/showpost.php?p=14020091&postcount=1
please let me know of any issues.
Click to expand...
Click to collapse
I noticed when i try and do a nandroid it gets stuck in a loop. Thats cuz once it gets to backing up the data partition its also includes the recently created system .img, boot.img, recovery.img. and then gets stuck at data.img. This is cuz its backing up itself while it is creating itself.

xavierdylan said:
I noticed when i try and do a nandroid it gets stuck in a loop. Thats cuz once it gets to backing up the data partition its also includes the recently created system .img, boot.img, recovery.img. and then gets stuck at data.img. This is cuz its backing up itself while it is creating itself.
Click to expand...
Click to collapse
pls post logs.

pershoot said:
pls post logs.
Click to expand...
Click to collapse
could you please direct me how i go about that?

xavierdylan said:
could you please direct me how i go about that?
Click to expand...
Click to collapse
/tmp/recovery.log

[Q] [RESOLVED] Need instructions for installing CWM on ZV8 Rooted

I just need instructions on installing Clockwork on rooted zv8. The AIO does not work for me. It hangs at starting daemon.

Are you in internet connection mode with debugging enable? I know it sounds like a stupid question but I had a brain fart when doing it and forgot that part... doh!

My USB connection is broken, so here is how I did it using terminal emulator.
1) Download the cwmrecovery.img to your SD. ( I downloaded MT's zip file and then extracted all with root explorer, but you only need the cwmrecovery.img file.)
2) Use root explorer to copy or move it to the /data/local/tmp directory (make sure permissions are set to r/w/exe).
3) Launch terminal emulator and type these commands:
su
mount -orw,remount /dev/block/system /system
mount -orw,remount /dev/block/data /data
dd if=/data/local/tmp/cwmrecovery.img of=/dev/block/mmcblk0p14 bs=4096
rm /data/local/tmp/* 2>/dev/null
4) exit terminal emulator and then reboot.
You can then try the vol down+power button combo upon boot to enter CWM.
Good luck.

Haxcid said:
I just need instructions on installing Clockwork on rooted zv8. The AIO does not work for me. It hangs at starting daemon.
Click to expand...
Click to collapse
Download the zv8recovery.zip in mt's "easiest" thread in Dev. Run the bat and you'll be set.

Cal8192 said:
Download the zv8recovery.zip in mt's "easiest" thread in Dev. Run the bat and you'll be set.
Click to expand...
Click to collapse
Ran it twice, each time it does 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"
}
Then it reboots to a black screen. Clock work never loads. I pull the battery and it reboots normally. It will not reboot to clockwork. It does the same in the screen shot every time I run that batch.

Haxcid said:
Ran it twice, each time it does this...
Then it reboots to a black screen. Clock work never loads. I pull the battery and it reboots normally. It will not reboot to clockwork. It does the same in the screen shot every time I run that batch.
Click to expand...
Click to collapse
It still needs the local.prop for the way I have the bat coded. Put it back in data and rerun, you should be good to go!
Sent from my VS920 4G using Tapatalk 2

mtmichaelson said:
It still needs the local.prop for the way I have the bat coded. Put it back in data and rerun, you should be good to go!
Sent from my VS920 4G using Tapatalk 2
Click to expand...
Click to collapse
Where do I grab the local.prop and how do I put it in? :x

Same issue here as the rest. Getting "Operation not permitted" and permission errors

As I kept my local.prop as local.prop.bak, I renamed it back and restarted the phone, everything appears to have gone through now.
Thanks MT.

brad6360 said:
My USB connection is broken, so here is how I did it using terminal emulator.
1) Download the cwmrecovery.img to your SD. ( I downloaded MT's zip file and then extracted all with root explorer, but you only need the cwmrecovery.img file.)
2) Use root explorer to copy or move it to the /data/local/tmp directory (make sure permissions are set to r/w/exe).
3) Launch terminal emulator and type these commands:
su
mount -orw,remount /dev/block/system /system
mount -orw,remount /dev/block/data /data
dd if=/data/local/tmp/cwmrecovery.img of=/dev/block/mmcblk0p14 bs=4096
rm /data/local/tmp/* 2>/dev/null
4) exit terminal emulator and then reboot.
You can then try the vol down+power button combo upon boot to enter CWM.
Good luck.
Click to expand...
Click to collapse
How do you change the permissions of the /data folder to r/w/exe as you mentioned?
I am having a problem because I don't currently have the Local.prop file and I need to add it to that folder but I am getting a permission denied message.

Plumbert said:
How do you change the permissions of the /data folder to r/w/exe as you mentioned?
I am having a problem because I don't currently have the Local.prop file and I need to add it to that folder but I am getting a permission denied message.
Click to expand...
Click to collapse
I used the paid version of root explorer

How to Clear/Wipe Dalvik-Cache via ADB?

I recently got my cache corrupted and whenever i turn on the phone the phone goes into recovery and says -
E : failed to mount cache.
E : failed to mount cache/recovery/last_log.
ETC ETC...
There is an endless argument about this error. i cannot boot into stock roms because of this. i just want to clear dalvik cache now.
Is there any way to do it?
I'm not able to wipe anything in recovery mode.
i can access download mode only.

Using adb
rm - r /data/dalvik-cache
rm - r /cache/dalvik-cache

nokiamodeln91 said:
Using adb
rm - r /data/dalvik-cache
rm - r /cache/dalvik-cache
Click to expand...
Click to collapse
Thanks for your reply.
How can i get into adb ?
In cmd, when i enter 'adb shell' it says ' exec '/system/bin/sh' failed : no such file or directory.
i can see the device connected in adb devices.
how can i proceed ? please help

can you paste a pic? Are you trying to do this in recovery mode? What recovery ?

nokiamodeln91 said:
can you paste a pic? Are you trying to do this in recovery mode? What recovery ?
Click to expand...
Click to collapse
Yeah i can.
My phone is in recovery mode Stock ICS.
here is the screenshot of cmd.
{
"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"
}
What do i do next?

Try installing a custom kernel with Cwm and then try this.

nokiamodeln91 said:
Try installing a custom kernel with Cwm and then try this.
Click to expand...
Click to collapse
Flash speedmod ics kernel and i can now access adb shell.. what should i do next?
when i enter this 'rm - r /data/dalvik-cache' command it says 'rm' is not recognized as an internal or external command. operable program or batch file.
I'm a noob at this. please direct me.

samsung_saad said:
Flash speedmod ics kernel and i can now access adb shell.. what should i do next?
when i enter this 'rm - r /data/dalvik-cache' command it says 'rm' is not recognized as an internal or external command. operable program or batch file.
I'm a noob at this. please direct me.
Click to expand...
Click to collapse
mistakenly entered a space in "-r" command.
if you get permission denied then run adb as root...
Code:
adb root
rm -r /data/dalvik-cache
rm -r /cache/dalvik-cache

nokiamodeln91 said:
mistakenly entered a space in "-r" command.
if you get permission denied then run adb as root...
Code:
adb root
rm -r /data/dalvik-cache
rm -r /cache/dalvik-cache
Click to expand...
Click to collapse
I get this error

is your data and cache partition mounted? Also first go to task manager and kill adb.exe.
then use the above commands.

nokiamodeln91 said:
is your data and cache partition mounted? Also first go to task manager and kill adb.exe.
then use the above commands.
Click to expand...
Click to collapse
I dont know if my data and cache partition is mounted. how can i test that?
I also killed adb.exe and entered above commands but i got same error.

IN the recovery mode under mounts and storage

nokiamodeln91 said:
IN the recovery mode under mounts and storage
Click to expand...
Click to collapse
On my phone when i go into mounts and storage and select mount /cache it says error mounting /cache.

are you able to format cache ?

nokiamodeln91 said:
are you able to format cache ?
Click to expand...
Click to collapse
No I'm not able to do wipe anything in recovery mode.
Here is the error.

try running this.
e2fsck -f -c –y /dev/block/mmcblk0p7

nokiamodeln91 said:
try running this.
e2fsck -f -c –y /dev/block/mmcblk0p7
Click to expand...
Click to collapse
I get this -

looks problem with the memory block.. my support ends here.. may be you will need re-partition..
- you may try to rerun this after installing a newer recovery like cm10.2 kernel.

nokiamodeln91 said:
looks problem with the memory block.. my support ends here.. may be you will need re-partition..
- you may try to rerun this after installing a newer recovery like cm10.2 kernel.
Click to expand...
Click to collapse
i can see cm10.1 kernel..where can i find 10.2 kernel?

I made it with adb shell. Thank you for the help

Unpacking, Editing, Packing ROMS [.IMG, .DAT] in Windows.

Unpacking, Editing, Packing ROMS GUIDE - Host Zero
First download the tools from the link below.
{
"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"
}
1. system.img
2. system.new.dat
1.Unpacking Repacking system.img
1. Paste your system.img in tools folder
2. Open cmd.exe
3. Type:
Code:
mkdir <your_folder_name>
ImgExtactor <raw_sparse.img> system -i
ex: ImgExtactor system.img system -i
4. Now open your folder you have created, you can find your <raw_image> has been extracted.
5. Now edit the files in system folder as your convenience.
6. Now open properties of folder you have created see the size of folder.
7. Now lets pack the image back, open the minimized command window.
Code:
make_ext4fs -s -l <size_of_your_folder+100>M -a system <name_of_packing_image>.img <your_folder_name>/
ex: make_ext4fs -s -l 512M -a system my_new_system.img system/
8. Done, enjoy!
2.Unpacking Repacking system.new.dat
1. Paste your system.new.dat, system.transfer.list and file_contexts in tools folder.
2. Open cmd.exe
3. Type:
Code:
sprs2ext system.transfer.list <name_of_system>.new.dat
ex: sprs2ext system.transfer.list system.new.dat
4. Now again type:
Code:
mkdir <your_folder_name>
ImgExtactor <raw_sparse.new.img> system -i
ex: ImgExtactor system.img system -i
5. Now open folder you have created and you will find the system.new.dat has been extracted.
6. Edit the extracted files.
7. Open properties of the extracted folder and check the size of folder
7. Now open minimized command window.
Code:
make_ext4fs -T 0 -S file_contexts -l <size_of_folder+100>M -a system <name_of_packing_image>.img <your_folder_name>/
ex: make_ext4fs -T 0 -S file_contexts -I 512M -a system my_new_system.img system/
8. Now again type:
Code:
rimg2sdat <your_raw_image>.img
ex: rimg2img my_new_system.img
9. Done! enjoy.
CLICK HERE TO DOWNLOAD TOOLS

Thank you very much.
You refresh the xda University.
I hope the University becomes more active.
We really need more guides to master android OS.
Sent from my SM-N910P using Tapatalk

I tried as rules mention on this thread. unpack was succeed. when I repack, here is the problem:
1. repack was succeed, but when I flash into my phone by spf tools, my phone was stuck at mi.com logo.
2. when I mount new system.img was created into DiskInternals Linux Reader, the file knowing as uknown file.
repack was succeed, but unable to use.
how to fix it?

A useful guide! Thanks!
Sent from my Sony Xperia Z3 Compact using XDA Labs

kevin mitnick said:
I tried as rules mention on this thread. unpack was succeed. when I repack, here is the problem:
1. repack was succeed, but when I flash into my phone by spf tools, my phone was stuck at mi.com logo.
2. when I mount new system.img was created into DiskInternals Linux Reader, the file knowing as uknown file.
repack was succeed, but unable to use.
how to fix it?
Click to expand...
Click to collapse
hey a bit late but i may help you.
Causes for this:
1. May be your rom is odex.
2. May be you are using OTA Update or Patch instead of full rom.
3. Applying more size while building .img
4. make_ext4fs dosent support all kind of roms. it only supports roms based on ICS, JB, KK... but i dont know how google builds factory images then.
Anyways a alternative.
Flash a full stock or custom rom into your device (with root access and adb support)
connect your device
type in cmd:
adb shell
su
(grant permissions on your device)
ls -al /dev/block/platform/*/by-name
now you will get your PMT table (Partition Management Table.)
ex: system ---> /dev/block/mmcblk07
and other partition information also.
now make system.img using adb.
dd if=/partitionnumber of=/sdcard/system.img
ex: dd if=/dev/block/mmcblk07
now you can find fastboot flashable system.img in your sdcard.
do rest with other partitions also. (boot partition manadatory).
enjoy.

Ticklefish said:
A useful guide! Thanks!
Sent from my Sony Xperia Z3 Compact using XDA Labs
Click to expand...
Click to collapse
Thankyou sir for encouraging.

Ticklefish said:
A useful guide! Thanks!
Sent from my Sony Xperia Z3 Compact using XDA Labs
Click to expand...
Click to collapse
Your Welcome sir.

HostZero said:
hey a bit late but i may help you.
Causes for this:
1. May be your rom is odex.
2. May be you are using OTA Update or Patch instead of full rom.
3. Applying more size while building .img
4. make_ext4fs dosent support all kind of roms. it only supports roms based on ICS, JB, KK... but i dont know how google builds factory images then.
Anyways a alternative.
Flash a full stock or custom rom into your device (with root access and adb support)
connect your device
type in cmd:
adb shell
su
(grant permissions on your device)
ls -al /dev/block/platform/*/by-name
now you will get your PMT table (Partition Management Table.)
ex: system ---> /dev/block/mmcblk07
and other partition information also.
now make system.img using adb.
dd if=/partitionnumber of=/sdcard/system.img
ex: dd if=/dev/block/mmcblk07
now you can find fastboot flashable system.img in your sdcard.
do rest with other partitions also. (boot partition manadatory).
enjoy.
Click to expand...
Click to collapse
thanks for respon @HostZero so much lessons and knowledge about this.
I'll try..report asap

kevin mitnick said:
thanks for respon @HostZero so much lessons and knowledge about this.
I'll try..report asap
Click to expand...
Click to collapse
This method is know as dumping method thanks to dd and su in android devices.

Cmd.exe not work on windows 7 32bit
?
sent from Xperia™ SP | Android 6.0.1

It seems to me that the permissions would be lost when they are dumped from system.img via this method. Are you seeing the selinux contexts preserved?

hamed24 said:
Cmd.exe not work on windows 7 32bit
sent from Xperia™ SP | Android 6.0.1
Click to expand...
Click to collapse
No problem. Open your tools folder in full screen. now below empty white space click (Shift + RightClick) then select Open Command Window Here.
Done!

HostZero said:
No problem. Open your tools folder in full screen. now below empty white space click (Shift + RightClick) then select Open Command Window Here.
Done!
Click to expand...
Click to collapse
Thanks for your help,that's work
Can you take screenshot from your cmd and typed codes, I'm beginner and confused some codes ?
sent from Xperia™ SP | Android 6.0.1

hamed24 said:
Thanks for your help,that's work
Can you take screenshot from your cmd and typed codes, I'm beginner and confused some codes
sent from Xperia™ SP | Android 6.0.1
Click to expand...
Click to collapse
Sorry bro I have recently shifted to Ubuntu14.04 for learning building. Read guide properly you will understand more. I have even provided examples as well as commands. and commands depends in each system folder.

hamed24 said:
Cmd.exe not work on windows 7 32bit
?
sent from Xperia™ SP | Android 6.0.1
Click to expand...
Click to collapse
Hi hamed24
Start-->run--> cmd.exe didn´t work? but using the right Mousebutton is okay?
Seems that Windows has lost the C:\Windows\system32 entry in the PATH Variable... easy to fix...
1. Press "Windows-Sign" Key and Break at the same time (it´s the same as rightclick on the Computer-Icon on the Desktop), click on Advanced System Settings.
2. Inside the new Window, click on Environment Variables, a new window opens. Now the lower part is the important one... look for PATH and doubleclick it.
3. At the end of the line, check if there is a ";" (without quotes). That seperates the different entries.... if there´s one there ... ok, place cursor at the end and enter C:\WINDOWS\SYSTEM32;
4. Hit ENTER, close all Windows, log off and on again.... and try again, should work now. If not, go to Start-->Run--> and type C:\WINDOWS\SYSTEM32\CMD.EXE and there you are
regards...
daywalker386

Thanks :3 Many thanks!!!!!! Very helpful thread!!!!!!

On <size_of_your_folder+100>M
For ex,
The folder size is 924MB, + 100MB=1024MB.
Is it right?

Unexpected argument: system

Hi, is that thread still active?
the tool download link is not working.

Fail could not create Tustarfilesystem

[Kernel] [MAINLINE] [Linux-5.XX BASED] [GCC9] Mainline Linux For Xiaomi Mi6 [New Update 5.11.14]

Code:
* Your warranty is now void.
* I'm not responsible for anything that may happen to your phone by installing any custom kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
Code:
This is a mainline linux port with some out of tree patch for DRM/PANEL and GPU
not tested on Android yet . Only ARM Linux distributions are been tested
How to test :
Make a new folder on /data/.stowaways
Grab any Linux OS you want to test place the rootfs on /data/. stowaways/postmarketOS.img
mount your rootfs and copy kernel modules on /lib/modules/ and also copy firmware file to /lib/firmware/
Than flash the kernel bellow and reboot
Note:
Wifi currently dos not works out of the box but if anyone want to try it just flow below guide
Update 25/04/2021:
+ update linux to 5.11.14
+ battery status are working now (charging may or may not work)
+ wifi working with some additional step along with firmware attached below
+ Bluetooth working fine
+ DRM/PANEL working via JDI-FHD-R63452
+ GPU working with mesa gallium driver
+ Haptics
+ Touchscreen using mainline RMI4
+ Vol Up key
+ Power button
NB: for wifi you will need
Install the following packages: pd-mapper, tqftpserv, qrtr & rmtfs
using your package manager if they are available if not clone than from this repo <https://github.com/jhugo/linux/tree/5.5rc2_wifi> and build and install
than clone & build & install diag-router from <https://github.com/andersson/diag>
run:
/bin/diag-router &
systemctl start rmtfs tqftpserv pd-mapper
After that you will be able to connect to the wifi successful
See screenshot bellow of a running Manjaro plasma-mobile OS
{
"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"
}
Ubuntu 21.04
and this thered edited on Debian 11 with phosh gui
Source :
https://github.com/degdag/W.I.P_sagit_mainline

does it support anbox?

When starting, display "or press Control-D to Continue" and wait.Cannot continue BOOT.
IMG is the result of Manjaro-ARM-plasma-mobile-dev-pinephone-210126.img decompression.
https://kdebuild.manjaro.org/images/dev/Manjaro-ARM-plasma-mobile-dev-pinephone-210126.img.xz

artful said:
When starting, display "or press Control-D to Continue" and wait.Cannot continue BOOT.
IMG is the result of Manjaro-ARM-plasma-mobile-dev-pinephone-210126.img decompression.
https://kdebuild.manjaro.org/images/dev/Manjaro-ARM-plasma-mobile-dev-pinephone-210126.img.xz
View attachment 5287775
Click to expand...
Click to collapse
mount your rootfs image and edit /etc/fstab and remove everything there than it should boot fine to gui

hajking said:
does it support anbox?
Click to expand...
Click to collapse
Yes the kernel has been compiled with anbox support as well

Fstab is empty。
I think it is possible that the SDCard is not decrypted, so I will try it when I have spare time.

artful said:
Fstab is empty。
I think it is possible that the SDCard is not decrypted, so I will try it when I have spare time.
Click to expand...
Click to collapse
Ofc storage need to be decrypted to get it working

degdag new dev said:
Yes the kernel has been compiled with anbox support as well
Click to expand...
Click to collapse
so where is the complete installation guide? i mean step by step. i downloaded manjaro lomiri from here but no chance amd i tried kde beta4. it gives kernel panic. am i doing right?
1. copy postmarketOS.img
2. flash kernel.img
3. reboot
should i change file system to f2fs?

hajking said:
so where is the complete installation guide? i mean step by step. i downloaded manjaro lomiri from here but no chance amd i tried kde beta4. it gives kernel panic. am i doing right?
1. copy postmarketOS.img
2. flash kernel.img
3. reboot
should i change file system to f2fs?
Click to expand...
Click to collapse
For manjaro lomiri you will need to empty /etc/fstab from any partition mount point
Also can you provide pic or dmesg to see the error

degdag new dev said:
For manjaro lomiri you will need to empty /etc/fstab from any partition mount point
Also can you provide pic or dmesg to see the error
Click to expand...
Click to collapse
is there any created log file?
how can i empty fstab?
is the kernel verison of img file important?

hajking said:
is there any created log file?
how can i empty fstab?
is the kernel verison of img file important?
Click to expand...
Click to collapse
it's depending on what os your using . But most of than log file will be under /var/log.
just open it with a text editor and remove all line there.
I recommend you to use the last kernel version I uploaded Wich you will have to Copy the kernel modules to rootfs .

Hello , I got error saids "
Error: ../arch/arm64/boot/dts/qcom/msm8998-xiaomi-sagit.dtsi:516.1-17 syntax error
FATAL ERROR: Unable to parse input tree " while compling with pmboostrap or "envkernel.sh".
Would u please help check this?

pugna said:
Hello , I got error saids "
Error: ../arch/arm64/boot/dts/qcom/msm8998-xiaomi-sagit.dtsi:516.1-17 syntax error
FATAL ERROR: Unable to parse input tree " while compling with pmboostrap or "envkernel.sh".
Would u please help check this?
Click to expand...
Click to collapse
Look at line 516 on sagit dtsi file under /arch/arm64/boot/dts/qcom/msm8998-xiaomi-sagit.dtsi it has some error
You can link me the source if you want more help

能不能给个详细的教程，我不知道怎么做 能不能给个详细的教程，我不知道怎么做

Can you give a detailed tutorial, I don't know how to do it

Download a compatible image or create one using pmbootstrap (see 1, 2)(advanced).
Pmbootstrap: basically the same standard process, but using split:
Code:
pmbootstrap init -> Xiaomi -> Sagit
pmbootstrap install --split
pmbootstrap export
adb shell mkdir /data/.stowaways
adb push /tmp/postmarketOS-export/xiaomi-sagit-root.img /data/.stowaways/postmarketOS.img
Note: image should contain only the rootfs partition.
This should boot, but there will be errors because lack of this exact kernel moduels, to fix this, edit the .img.
You should be able to do this with other arm64 .img, containg only rootfs, also.
Inside the image:
You can do this on your Linux PC or directly on phone using TWRP.
Copy kernel modules from 5.11.14-xiaomi-msm8998.zip to /lib/modules/
Copy firmware files from firmware.zip to /lib/firmware/.
E.g. using TWRP:
Code:
adb push 5-11-14-xiaomi-msm8998.zip /sdcard
adb push firmware.zip /sdcard
adb shell
cd /sdcard
unzip 5-11-14-xiaomi-msm8998.zip
unzip firmware.zip
mkdir /mnt/rootfs
mount -o loop -t ext4 /data/.stowaways/postmarketOS.img /mnt/rootfs
cp -r 5.11.14-xiaomi-msm8998/ /mnt/rootfs/lib/modules
cp -r firmware/* /mnt/rootfs/lib/firmware/
umount /mnt/rootfs/
reboot

Seems all firmware files was included in postmarketos edge channel now, but wifi isn't working
Update: v6.1_rc3 fixs it.