Hi All,
Here is rooted 3.2.78 firmware for SDE enabled devices.
I did two versions:
- squashfs (like my previous build), in this one, system is read-only, you can't add/remove stock apps and edit system files. Files are compressed so it takes less storage space than ext4, it should be also slower than ext4.
- ext4, system is read/write and should be quicker. Be careful if you modify system files though.
Both have kernel/modules from 3.2.78.
To install it:
0) You must have SDE installed. If you didn't do it already, check there instructions on how to do it.
1) Extract zip file content
2) Copy android_3.2.78.squashfs (or android_3.2.78.ext4) to internal storage root. You can do it the usual way or with adb with this:
Code:
adb push android_3.2.78.squashfs /data/media
or
Code:
adb push android_3.2.78.ext4 /data/media
3) Reboot
4) On boot menu, select "Recovery 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"
}
5) Select "developer edition menu"
6) Select "flash kernel and initramfs"
6) A drive should appear on your PC, copy zImage and initramfs.cpio.gz to it.
7) Select OK, the kernel should flash.
8) Select OK to reboot and maintain vol+ pressed. Boot menu should appear after reboot.
9) Select SDE in boot menu, you should be rooted and SuperUser functional.
The only change from stock: I enabled vibrator control panel option, it has been reported to work on some, it doesn't on mine.
I checked 3.2.78 stock firmware, it has an updated bootloader, it may be worth flashing stock firmware too to have everything synched.
Download rooted 3.2.78 on squashfs here.
Download rooted 3.2.78 on ext4 here.
Cheers,
LeTama
great thank you
gonna flash it as soon as its downloaded
btw do i have to do any special things to flash the ext4 ?
Ok...good job....!!!
I understand now why I did not have options rw in root-explorer....because I managed the Rom with squashfs and not with ext4.....
Now everything is ok....thanks again @letama...
No, nothing special for ext4, same thing as squashfs...
letama said:
No, nothing special for ext4, same thing as squashfs...
Click to expand...
Click to collapse
Are you saying that installing with ext4 partition I'll can't be mount RW in root_explorer ?
-because with squashfs I can't ....
surdu_petru said:
Are you saying that installing with ext4 partition I'll can't be mount RW in root_explorer ?
-because with squashfs I can't ....
Click to expand...
Click to collapse
no i think he answered my question from above
surdu_petru said:
Are you saying that installing with ext4 partition I'll can't be mount RW in root_explorer ?
-because with squashfs I can't ....
Click to expand...
Click to collapse
No, sorry, our posts crossed, I was effectively replying to djnilse. I'm trying to refrain my "quote mania", it was not a good idea this time
Ext4 is R/W, and permanently, no need to remount it in root explorer.
I would have preferred ext4 mounted first as r/o and allow the option to remount as r/w when needed, but this is not possible with the way Archos designed their rootfs.
Hi Letama,
Thanks for your build but I cant use your kernel with 3.2.78 kernel modules and when I extract kernel from 3.2.78, init kernel does not boot :/.
Thanks in advance
Thaolia
ok i flashed it everything worked fine
i have now a dualboot recovery menu with Android(non-root) and developer(root)
on developer the root is ok, also the system is r/w
thx letama for the rooted newest update
As a question to get out of the way early in the thread, I'm on your earlier rooted one, do I need to wipe?
Sent from my HTC Desire HD using xda premium
Tha0lia said:
Hi Letama,
Thanks for your build but I cant use your kernel with 3.2.78 kernel modules and when I extract kernel from 3.2.78, init kernel does not boot :/.
Thanks in advance
Thaolia
Click to expand...
Click to collapse
Archos kernel is using a new compression scheme for initrd, check my howto, the "find . | cpio ..." command. You need to rebuild your initrd.
Quinny899 said:
As a question to get out of the way early in the thread, I'm on your earlier rooted one, do I need to wipe?
Click to expand...
Click to collapse
I don't think so, Archos firmware update doesn't, so it shouldn't be necessary.
I had to wipe mine for another reason so I can't be sure though.
letama said:
Archos kernel is using a new compression scheme for initrd, check my howto, the "find . | cpio ..." command. You need to rebuild your initrd.
Click to expand...
Click to collapse
My extract kernel is of 5Mb (I use your howto for extract the 3.2.78 kernel). Init and recovery extract kernel doesn't boot with a lzop initramfs.cpio. Wheras with your kernel and modules, all works fine.
Sry but I certainly forget somethings.
Thanks in advance
Thaolia
Tha0lia,
5 MB is wrong:
- aos-unpack gives you 9_MMCF (5145304)
- dd strips header and gives you init_kernel which contains zImage+initrd (5145040)
- aos-kernel-unpack of init_kernel gives you kernel and initrd separated (unpacked-kernel, unpacked-cpio.gz), that I renamed to init-zImage afterwards.
This is the one you want, size should be 3993572.
Cheers,
LeTama
Noticed an issue in the first post:
adb cp should read
adb push
Sent from my ARCHOS 80G9 using xda premium
Quinny899 said:
Noticed an issue in the first post:
adb cp should read
adb push
Click to expand...
Click to collapse
Thanks! I shouldn't post when I'm in a hurry . First post fixed.
letama said:
Tha0lia,
5 MB is wrong:
- aos-unpack gives you 9_MMCF (5145304)
- dd strips header and gives you init_kernel which contains zImage+initrd (5145040)
- aos-kernel-unpack of init_kernel gives you kernel and initrd separated (unpacked-kernel, unpacked-cpio.gz), that I renamed to init-zImage afterwards.
This is the one you want, size should be 3993572.
Cheers,
LeTama
Click to expand...
Click to collapse
Sorry, your kernel and my extract kernel have same md5sum.
It's my fault but thanks for your help.
Have a nice day !
Thaolia
For the Buzz in FRANCE
http://www.jbmm.fr/?p=25015
(ps : je recherche des rédacteurs "techniques" pour jbmm - envoyez un MP)
Is it possible to get swap working in the build modifications?
When I use swapper for root from the market, reboot and type free, I get this:
It shows it as empty and unused. Any idea why? There's a swapfile on /sdcard, in fat, which is being activated by the app on boot. Could this be fixed? I'm using the latest rooted ext4 version btw
Sent from my ARCHOS 80G9 using xda premium
I got swap working!
You use swapper 2 and direct it to /mnt/sdcard, and rather than /sdcard. Turns out internal is ext and it needs fat
Sent from my ARCHOS 80G9 using xda premium
Related
Is there a way to view the raw boot process in text mode instead of the boot animation?
Hoping there is a setting in a config file somewhere....
Edit: ([Solved/Workaround])
One easy solution is to install the paid app mentioned here. It shows you the logcat log as your phone boots.
A free kernel mod to accomplish this is still elusive.
For linux/grub this is accomplished by removing the 'quiet' and 'splash' options in /boot/grub/menu.lst
Also found a possible setting in /init.rc
export ANDROID_BOOTLOGO 1
Click to expand...
Click to collapse
However I cannot chmod this file to edit it even as root. / is mounted read-only
su
chmod u+w init.rc
chmod: init.rc: Read-only file system
Click to expand...
Click to collapse
Do I need to unpack + edit the file + repack boot.img and then flash(boot) it to achieve this?
britoso said:
For linux/grub this is accomplished by removing the 'quiet' and 'splash' options in /boot/grub/menu.lst
Also found a possible setting in /init.rc
However I cannot chmod this file to edit it even as root. / is mounted read-only
Do I need to unpack + edit the file + repack boot.img and then flash(boot) it to achieve this?
Click to expand...
Click to collapse
you need to mount /system as rw before you can chmod anything. SU file manager works well for this, and you can do it all on the phone, even the edits. Just don't forget to make a nandroid before you do any tweaks.
I know there is a way to disable the boot animation in the boot.img-kernel, i've seen it done before.
So you want a verbose boot mode?
uansari1 said:
So you want a verbose boot mode?
Click to expand...
Click to collapse
Yes.
SU file manager is not free.
followinginsanity said:
you need to mount /system as rw before you can chmod anything. SU file manager works well for this, and you can do it all on the phone, even the edits.
Click to expand...
Click to collapse
SU file manager can only mount /data and /system as RW, afaik / is a ramdisk image that is only modifiable if the change is made in a boot.img and flashed.
heh Just depends on where you need to make the changes Its what I used to do the build.prop mods to get navi working on the G1 back before they did the official update. Either way I do hope we can figure out how to disable the boot animation. Like I said I know its been done, and where the guy said he did the mod to do it. But thats only a start. Also I know the emulator has a command so that you can boot it without the animation but thats the emu, not the actual device.
Heres where I am now:
The first X comes from initlogo.rle in the root directory of the bootimage.
The next image is the boot logo. This is a set of two images in framework-res.apk/assets/images.
{
"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"
}
If a bootanimation.zip is found in /data/local or system/media, it is shown next. This is the nexus boot animation.
I tried renaming bootanimation.zip...the boot logo images were shown instead.
I removed the boot logo images from framework-res.apk...got a blank black screen until the lock screen appeared.
Also tried editing pushing a modified init.rc with these commands, didnt help the original init.rc was restored on reboot.
Code:
adb shell mount -o remount,rw rootfs /
adb pull init.rc .
#edit the file.
adb push init.rc /
adb shell sync
adb reboot
Found some instructions on how to edit the boot image:
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
Thinking of setting up ubuntu in a virtualbox to try this. (Goal is to turn set ANDROID_BOOTLOGO 0 in init.rc). Dont know if this will let us see the verbose boot log or not...
Update:
Tried this. the 2.5MB boot.img splits up into two pieces (ramdisk and kernel), totaling 2MB (?), flashing an updated 2MB boot.img gets the phone stuck on the initial x. ... Something is missing.
heh this is what I want (not the phone)
http://www.youtube.com/watch?v=5yO2KQHkt4A#t=1m44s
Re: Boot with no boot screen? (console)
I noticed there is a /system/bin/bootanimation. I ran it from terminal and the animation played. I couldn't exit it and had to take the battery out to reboot. It took over my screen and disabled all the buttons.
If you removed the images and still had a black screen, I wonder if this program was running but was black because the images were gone. Maybe renaming it would keep it from running and do what you want?
I tried to "cat" it but it's a binary. There was some garbled text toward the end which said "boot animation disabled" and gave some file locations etc. May be some clues there.
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
fubaya said:
I noticed there is a /system/bin/bootanimation. Maybe renaming it would keep it from running and do what you want?
Click to expand...
Click to collapse
Tried this.
adb -d shell mv /system/bin/bootanimation /system/bin/bootanimation1
It booted ok and I got a black screen in place of the boot animation, went straight to the lock screen.
Didnt get the console text though
sorry, cant contribute. but id love to have this as well.
Well where are all the Kernel hackers when you need em
Told by someone pretty intelligent that the Kernel will basically need to be compiled to enable the console framebuffer option and maybe remove references to the boot animations etc. I'd love something like this though, wish I knew more about implementing it.
I can contribute a little bit.
Go over to the Dev section, see the "update.zip creation" thread. There are instructions for creating a boot image:
http://forum.xda-developers.com/showthread.php?t=667923
In these instructions, you'll notice an interesting switch for kernel to execute with:
--cmdline 'no_console_suspend=1 console=null'
I believe that might lead you to where you're trying to get
Jack_R1 said:
I can contribute a little bit.
Go over to the Dev section, see the "update.zip creation" thread. There are instructions for creating a boot image:
http://forum.xda-developers.com/showthread.php?t=667923
In these instructions, you'll notice an interesting switch for kernel to execute with:
--cmdline 'no_console_suspend=1 console=null'
I believe that might lead you to where you're trying to get
Click to expand...
Click to collapse
I tried that, the new boot.img I create does not work, see post #8
what did you define as console?
Jack_R1 said:
what did you define as console?
Click to expand...
Click to collapse
What you posted, and also tried the command that was in my boot.img (cyanogenmod)
Re: Boot with no boot screen? (console)
i would love this!
unfortunately i did the same things eg move bootanimation.zip bootanimation script etc.
only got a black screen.
we could build a bootanimation.zip with text images... lol
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
leonnib4 said:
we could build a bootanimation.zip with text images... lol
Click to expand...
Click to collapse
There is one out there, but I prefer the real thing.
We need help from one of the kernel masters!
britoso said:
What you posted, and also tried the command that was in my boot.img (cyanogenmod)
Click to expand...
Click to collapse
But I posted the default command, and marked it in red to say - if you're making a boot image with default command line, you're actually redirecting the console to null, so what do you expect to see?!
First, try eliminating redirection, the default might work. Remove the "console=null" from the line and rebuild the boot image.
In case it still won't work - try to change it to "console=tty", "console=ttyS0" or something like that.
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
Hi XDA, i want to move my apps to SD (Im Root user)
I made 3 partitions:
FAT32, Ext3 and SWAP.
Here is the 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"
}
COPY THE LINK IMAGE AND RELOAD IF U HAVE PROBLEMS!.
When i go to Link2SD, i choose "ext3" and a error appears:
"mount script not be created. mount:Not such device. Ext4 may not be supported on your device, try fat 32 on the second partition"
I tried selecting ext2, ext3 and ext4 and NOTHING
I restart the phone, and NOTHING
I tried to install another version of the Link2SD and NOTHING
In the description of the Link2SD in Android Market, says:
Some phones lack the ext2, ext3 or ext4 file system support and you may get mount errors like "no such device", "invalid argument". These phones need ext2.ko or ext3.ko modules and even some additional modules to be able to mount. Using FAT32 on the second partition will eleminate such problems, because FAT32 is supported on all phones
Click to expand...
Click to collapse
The x8 don't have the modules?
Im talked with other users and they have Link2SD working on Xperia x8
I tried to make the 3 partitions 4 times ago and NOTHING!
The Notebook and the phone, recognize the SDCard.
What i can do!!?
Thanks!!
PD: Sorry for my bad English, im from Argentina
KbZonFS said:
The x8 don't have the modules?
Click to expand...
Click to collapse
Well, you put it somewhat wrong...
The Stock ROM does not contain the required kernel modules for supporting EXT2/3/4 filesystems.
Also - why did you create a SWAP partition? Stock Kernel does NOT support swap!
You may try to borrow the modules from the GingerDX ModulesStockKernel AddOn and see if they work with Eclair. This, however, requires that you know what you are doing as you need to copy the kernel modules from the ZIP into the correct location and maybe alter a script to load them at boot-up.
B.Jay said:
Well, you put it somewhat wrong...
The Stock ROM does not contain the required kernel modules for supporting EXT2/3/4 filesystems.
Also - why did you create a SWAP partition? Stock Kernel does NOT support swap!
You may try to borrow the modules from the GingerDX ModulesStockKernel AddOn and see if they work with Eclair. This, however, requires that you know what you are doing as you need to copy the kernel modules from the ZIP into the correct location and maybe alter a script to load them at boot-up.
Click to expand...
Click to collapse
A friend gives me the libs And the modules. But Eclair don't have the /system/lib/modules folder.
If i put the libs and create the MODULES folder and paste the ext3.ko file... I don't brick my Xperia x8? Eclair detects the new libs and the folder modules?
Thanks for replyng!
Sorry for my bad English!
Sent from my E15a using XDA App
First link doesn't work for me
But if I were You I would change ext3 into ext2 and delete swap partition. I hope You set all partitions as primary cause it is neccessary
KbZonFS said:
A friend gives me the libs And the modules. But Eclair don't have the /system/lib/modules folder.
If i put the libs and create the MODULES folder and paste the ext3.ko file... I don't brick my Xperia x8? Eclair detects the new libs and the folder modules?
Thanks for replyng!
Sorry for my bad English!
Sent from my E15a using XDA App
Click to expand...
Click to collapse
Chances are you need to put them into the hw_config.sh file to automatically load them during boot - there are tons of threads about this topic, use SEARCH.
did you create the both partitions as primary??
- first partition (FAT32/Primary/more than 1GB)
- second partition (FAT32/Primary/500MB)
- ignore if there is notification to format your SD Card.
- Reboot.
- Install link2SD, Open it.
- Choose your Partition (select the second partition)
- Reboot.
- To move the App to your external, click the Apps/Games.
- Select Create Link. Reboot
Note: You just can create 2 partitions if you use 2GB SD card.
|| Click Thanks if My POST Helped ||
No results in search
B.Jay said:
Chances are you need to put them into the hw_config.sh file to automatically load them during boot - there are tons of threads about this topic, use SEARCH.
Click to expand...
Click to collapse
Can you give me a Link?
KbZonFS said:
Can you give me a Link?
Click to expand...
Click to collapse
Sure, here you go
Yeah
Dawoods said:
did you create the both partitions as primary??
- first partition (FAT32/Primary/more than 1GB)
- second partition (FAT32/Primary/500MB)
- ignore if there is notification to format your SD Card.
- Reboot.
- Install link2SD, Open it.
- Choose your Partition (select the second partition)
- Reboot.
- To move the App to your external, click the Apps/Games.
- Select Create Link. Reboot
Note: You just can create 2 partitions if you use 2GB SD card.
|| Click Thanks if My POST Helped ||
Click to expand...
Click to collapse
If u look in the first image, are the 3 partitions:
FAT32: Primary
Ext3: Primary
SWAP: Logical
But Link2SD doesn't work!
Troll
B.Jay said:
Sure, here you go
Click to expand...
Click to collapse
Haha, ok... But i don't know what lines i have to edit.
Sorry for mi bad english
KbZonFS said:
Haha, ok... But i don't know what lines i have to edit.
Click to expand...
Click to collapse
Find and edit the hw_config.sh
Input a like like...
insmod /system/lib/modules/<module>.ko
As an example about the Overclock module, you would put the following line:
insmod /system/lib/modules/x8oc.ko
Savvy?
KbZonFS said:
If u look in the first image, are the 3 partitions:
FAT32: Primary
Ext3: Primary
SWAP: Logical
But Link2SD doesn't work!
Click to expand...
Click to collapse
you must create just 2 partition and both are FAT32 Primary. I've tried that way and link2sd work great. You dont need to create swap, because it doesnt work on stock kernel.
First time, I got the same problem as you are. But after following that steps, I get no problem.
Like this?
B.Jay said:
Find and edit the hw_config.sh
Input a like like...
insmod /system/lib/modules/<module>.ko
As an example about the Overclock module, you would put the following line:
insmod /system/lib/modules/x8oc.ko
Savvy?
Click to expand...
Click to collapse
Would be...
insmod /system/lib/modules/ext3.ko
Right? Is secure edit hw_config.sh ?
Sorry for my bad English
Dawoods said:
you must create just 2 partition and both are FAT32 Primary. I've tried that way and link2sd work great. You dont need to create swap, because it doesnt work on stock kernel.
First time, I got the same problem as you are. But after following that steps, I get no problem.
Click to expand...
Click to collapse
I will consider your info
Thanks man!
Sorry for my bad English
KbZonFS said:
Would be...
insmod /system/lib/modules/ext3.ko
Right? Is secure edit hw_config.sh ?
Click to expand...
Click to collapse
Yes...
insmod /system/lib/modules/ext3.ko
insmod /system/lib/modules/ext4.ko
(and maybe you even need to specify the jbd*.ko modules if the ext modules doesn't load them automatically).
Editing hw_config.sh is "secure", but chances are that you could end up in a boot loop if the ROM doesn't love your modifications.
In that case you need to re-flash Stock to undo your changes and try anew.
B.Jay said:
Yes...
insmod /system/lib/modules/ext3.ko
insmod /system/lib/modules/ext4.ko
(and maybe you even need to specify the jbd*.ko modules if the ext modules doesn't load them automatically).
Click to expand...
Click to collapse
I don't understand you... :/
B.Jay said:
Editing hw_config.sh is "secure", but chances are that you could end up in a boot loop if the ROM doesn't love your modifications.
In that case you need to re-flash Stock to undo your changes and try anew.
Click to expand...
Click to collapse
Im using Eclair 2.1-update1
Build: 2.1.1.A.0.6
KbZonFS said:
I don't understand you... :/
Click to expand...
Click to collapse
The ext3.ko and ext4.ko have a dependency on jbd.ko and jbd2.ko
This means you possibly also need to load the modules to make ext3|4.ko work.
* "jdb" is short for "Journalled Block Device" ... ext3 and ext4 are journalled file systems keeping a transaction log of the things that happened in the fs to quickly recover from filesystem corruption.
B.Jay said:
The ext3.ko and ext4.ko have a dependency on jbd.ko and jbd2.ko
This means you possibly also need to load the modules to make ext3|4.ko work.
* "jdb" is short for "Journalled Block Device" ... ext3 and ext4 are journalled file systems keeping a transaction log of the things that happened in the fs to quickly recover from filesystem corruption.
Click to expand...
Click to collapse
Daaaam, that is so complicated!
Thanks man... I have to go! :/
Sorry for my bad English D:
KbZonFS said:
Daaaam, that is so complicated!
Click to expand...
Click to collapse
Didn't I tell you that you just entered a topic where you should know what you're doing and what all these fancy things mean?
Hey Guys,
first off i had this issue once before, but in that case i could restore a cwm backup from sd card and after sometime the problem fixed itself,
this time, i switched to bacon and i wanted to prepare the p880 for my sister to use, i downloaded zaiben, formatted my external sd card and put the rom on it, i rebooted to recovery wiped( i used the clean to install new rom in philz recovery if i remember correctly) everything and flashed the rom and exactly as last time, the flash seems to go way too fast and ofc i cant boot into android. now as i formatted my sd i have no backup to restore to. kdz flashing seems hopeless as well, as none of the tools recognize the phone when i put it in s/w upgrade mode,
for proof: i checked /system with aromafm and found it being empty after flashing a rom, i even tried extracting the rom zip on sd and moving the content from the zip to /system manually but after a recovery reboot, /system was empty again( only empty "bin" folder)
is somebody able to explain me why i have this issue and maybe how to fix it, or upload a clean cwm backup of whatever rom for me to use?
thx
Thanks for the help until now, really.......
In Further investigation i could find out that Roms ARE actually flashing properly, but /system and probably other partitions are not being mounted
At Boot or in recovery(manually mounting works Here) which is why aromafm reports an empty /system, after a manual Mount in either recovery itself of Aroma console i can See /system being filled with Rom files, now i will change the thread title accordingly, and now ASK: can i force /system to be mounted at Boot somehow? Someone pls answer this time
Okay this is ridicoulous.... why am i getting no help AT ALL?, thank you srsly.....
i investigated even further and suspected that something with fstab might be wrong, but fstab file looks fine to me:
Code:
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 rw
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 rw
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 rw
if someone bothers to answer: what do you think?
pls help........
bump
please help
What recovery are you using? Are you sure your partitions aren't formatted to F2FS? (which would explain why the (F2FS-) recovery can mount the partitions but the system cannot as it expects an ext4 formatted partition rather than a F2FS formatted one)
i'm using an older version of philz touch (i dont think it has f2fs functionality), as i had weird flickering issues with latest philz,
using cat /proc/mounts shows ext4 for /system and other partitions
~MaX~ said:
i'm using an older version of philz touch (i dont think it has f2fs functionality), as i had weird flickering issues with latest philz,
using cat /proc/mounts shows ext4 for /system and other partitions
Click to expand...
Click to collapse
Did you try to boot another ROM (Slim, nameless, whatever) or using another kernel?
laufersteppenwolf said:
Did you try to boot another ROM (Slim, nameless, whatever) or using another kernel?
Click to expand...
Click to collapse
i tried latest aospa,zaiben, pa 3.99 and iodak kernel (stock or cm according to the kind of rom i tried to boot)
thank you for helping btw, i appreciate it
EDIT: I attached an image of output of cat /proc/mounts (sorry for the size)
{
"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"
}
~MaX~ said:
i tried latest aospa,zaiben, pa 3.99 and iodak kernel (stock or cm according to the kind of rom i tried to boot)
thank you for helping btw, i appreciate it
EDIT: I attached an image of output of cat /proc/mounts (sorry for the size)
Click to expand...
Click to collapse
hmm, can you please grab me a kmsg? (from when it is stuck)
laufersteppenwolf said:
hmm, can you please grab me a kmsg? (from when it is stuck)
Click to expand...
Click to collapse
could you give me a quick how to on using adb in recovery from pc? i put the phone in sideload mode and tried "adb shell dmesg" but the output just was "error close" and using the command in aromafm terminal gave me an endless stream of log
(Also currently need to charge the phone a bit)
EDIT: NVM kmesg incoming....
okay next question, how can i dump the output into a file and how do i know where it hangs? time in recovery is not correct anymore(i set it once but after reboot it was wrong again, also in kmesg the time again seems to be different)
does that part help? i think it has to do with boot
~MaX~ said:
does that part help? i think it has to do with boot
Click to expand...
Click to collapse
nah, I need the entire log
here's how you get it:
boot the system until it is stuck
hard reboot into recovery (don't enter sideload)
then run the following commands:
Code:
adb shell cat /proc/last_kmsg > /sdcard/last_kmsg
adb pull /sdcard/last_kmsg C:\whatever\path\you\like\last_kmsg
then post the file via pastie.com or any other online paste site
laufersteppenwolf said:
nah, I need the entire log
here's how you get it:
boot the system until it is stuck
hard reboot into recovery (don't enter sideload)
then run the following commands:
Code:
adb shell cat /proc/last_kmsg > /sdcard/last_kmsg
adb pull /sdcard/last_kmsg C:\whatever\path\you\like\last_kmsg
then post the file via pastie.com or any other online paste site
Click to expand...
Click to collapse
no such file or directory
by hard reboot you mean vol - and hold power without pulling battery after hang?
~MaX~ said:
no such file or directory
by hard reboot you mean vol - and hold power without pulling battery after hang?
Click to expand...
Click to collapse
Yes, I meant that. But no kernel log seems like your boot partition/kernel is messed up... I guess you'll have to find a way to restore your entire phone via LG tools, I can't see any other way around that..
laufersteppenwolf said:
Yes, I meant that. But no kernel log seems like your boot partition/kernel is messed up... I guess you'll have to find a way to restore your entire phone via LG tools, I can't see any other way around that..
Click to expand...
Click to collapse
two last things then: when i hold vol - and then hold power until i reboot, recovery does not start, it tries to boot android again (has always been like that)
and also: all roms except cm official show no bootanimation before hang, cm does
~MaX~ said:
two last things then: when i hold vol - and then hold power until i reboot, recovery does not start, it tries to boot android again (has always been like that)
and also: all roms except cm official show no bootanimation before hang, cm does
Click to expand...
Click to collapse
1) yeah, I know, easiest way to fix that is to simply pull the battery and then boot into recovery
2) if the bootanimation shows up, it means the kernel as well as the ramdisk have booted properly. So in this case, you should be able to grab a last_kmsg as well as a logcat
hi
today I installed that application " LG-Optimus-4XHD-Recovery-v1.0.apk "
I have selected ClockworkMod Custom Recovery.
It showed that Operation is successful.
than i clicked on "Boot Recovery" to restart my Phone in CloclworkMod Custom Recovery.
since then I am getting only Starting animation. (LG LOGO).
nothing happens.
My battery was full when i performed this procedure
any help please
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.