[DEV][Kernel] P5210 | USB RT8187 | Aircrack-ng How to Included - Galaxy Tab 3 10.1 Android Development

Hi,
This kernel/rom lets you connect an RT8187 USB Wifi adapter to your GT-P5210 and run aircrack-ng/airmon-ng/airodump-ng through Linux on Android.
Mind the noobness, I just compiled my first kernel(ever) and stuck it in someones image and it worked.
{
"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"
}
(worked untill i enabled the builtin wifi, lol)
After i bought one of these tablets I can't say I'm not a bit dissapointed about the amount of dev work on the GT-5210, (words go unspoken for DutchDanny, Angel_666, trevd)
It's an x86 device, anything should be compileable and runable without any arm mods (i'm looking at you kali linux) this thing should be owning the Nexus 7.
Tested with TWRP 2.7 recovery
Its built using builduntu, and from the P5210UEUAMI8 source, with the toolchain recommended in the Kernel Readme.
I followed this tutorial to enable driver support
And this detailed guide to compile the kernel and create a proper boot.img
Replaced the boot.img in Mod57's rom with my modified one. (god fed up with fastboot and usb issues on Win 8.1 and just flashed it, it worked. Thats my testing)
Mod57 said:
This is built using the Samsung GT-P5210 P5210UEUAMI8 [4.2.2] Jelly Bean base.
ORIGINAL THREAD
This is not debloated it's fat and sassy like Samsung intended it.
If you would like to debloat I highly recommend using DutchDanny's debloater which can be found here:
http://forum.xda-developers.com/showthread.php?t=2482582
Jelly Bean P5210UEUAMI8
Fully Deodexed
Rooted
BusyBox
Zipaligned
Extended Power Menu (Wanam Xposed)
Will Not Delete Internal SD
Thanks to:
DutchDanny
Angel_666
Zidkijah
and everyone else who has contributed to this device.
Download:
http://www.androidfilehost.com/?fid=23189362627838229
MD5: 79f732fefbaf7882bc7c814d3ac1e998
Click to expand...
Click to collapse
Once you have downloaded and verified Mod57's rom, open up the zip and replace boot.img with this one:
https://www.dropbox.com/s/9gfucdzsadciy66/boot.zip
MD5: 4dd95a78c78550586cf3c2f7953978ab boot.img
You must have a rooted device (I used TWRP 2.7, http://nasirtech.blogspot.dk/2014/03/root-p5210xxuanb4-android-422-stock.html)
Code:
Put the modified rom onto the sdcard
Go to recovery
Wipe Cache and dalvik-cache
Install the ROM
Reboot and enjoy
Once you have installed the kernel and it boots up, you must follow these steps to chroot into an ubuntu image and compile / install aircrack.
Code:
Download this image: ubuntu-13.10.LARGE.x86.ext2.v1.zip
from [url]http://sourceforge.net/projects/linuxonandroid/files/Ubuntu/13.10/x86/[/url]
and copy it to your sdcard
Thanks to jorgen_gustavsson for his excellent work [url]http://forum.xda-developers.com/showthread.php?t=2573441[/url]
1. Install busybox [url]https://play.google.com/store/apps/details?id=stericson.busybox[/url]
2. Install a vnc viewer [url]https://play.google.com/store/apps/details?id=android.androidVNC[/url]
3. Install [url]https://play.google.com/store/apps/details?id=com.zpwebsites.linuxonandroid[/url]
(Not sure, but open and close it once to be safe)
4. Copy bootscript.sh [url=http://forum.xda-developers.com/showthread.php?t=2573441]link to bootscript thread[/url] to /data/data/com.zpwebsites.linuxonandroid/files/ overwrite the old file.
bootscript.sh
(Thanks to xdadev: jorgen_gustavsson)
5. Unpack and Copy the ubuntu-13.10.LARGE.x86.ext2.img and .md5 to a place of your choosing on either internal or external sdcard.
6. Make a Linux on Android widget and point it to the img file you copied to your sdcard (ubuntu-13.10.LARGE.x86.ext2.v1.img).
7. Now click on the LOA widget you made in 6 and let linux ”bootup”
8. Press 'y' to check MD5 checksum
9. Connect vnc to localhost:5900 password ubuntu
Now to install Aircrack
# Libraries
sudo updatedb
sudo apt-get install build-essential
sudo apt-get install gcc
sudo apt-get install zlibg-dev
sudo apt-get install libssl-dev (or libssl-dev depending on your distribution)
#airolib-ng optional sqlite=true
sudo apt-get install libsqlite3-devel
#libnl optional libnl=true
sudo apt-get install libnl-genl-3-dev libnl-3-dev
#Required Extras
sudo apt-get install wireless-tools
sudo apt-get install net-tools
sudo apt-get install wicd-curses (or wicd-cli)
sudo apt-get install usbutils
sudo apt-get install wpasupplicant
sudo apt-get install dbus
# Download & unpack (or replace link with latest trunk)
wget [url]http://download.aircrack-ng.org/aircrack-ng-1.2-beta3.tar.gz[/url]
tar -zxvf aircrack-ng-1.2-beta3.tar.gz
cd aircrack-ng-1.2-beta3
# Make
sudo make libnl=false sqlite=false
sudo make install libnl=false sqlite=false
# or
make libnl=true;make libnl=true install
make install libnl=true;make libnl=true install
# or Airolib-ng support
make sqlite=true;make sqlite=true install
make install sqlite=true;make sqlite=true install
# Add binaries to path
export PATH=$PATH:/usr/local/sbin
# add the above line to below file for include path on startup
vim /home/ubuntu/.bashrc
# Update MAC OUI
airodump-ng-oui-update
Reboot and disable your internal wifi, connect your dongle, and get cracking.
This is what I spent my easter (and then some) doing, I hope someone can make good use of it. I can
Maybe someone can come along and add bcmon for the bcm4334 chipset
(Just maybe https://code.google.com/p/bcmon/source/browse/trunk/bcm4330/driver/src/bcmdhd/Kconfig?r=4 )
Any feedback and questions are welcome:
why didn't you use the latest source? -couldn't find it
Will this kernel work with xx rom? -probably not
Why aren't more roms including this? -dno, its in the menuconfig, should be easy
I've tried to give thanks where ever possible, let me know if you feel left out.
Ill come back tomorrow and clean up my post.
Best Regards

You my dear friend are a LEGEND

I'm also yoing to build an own kernel... And I think I'll add this feature too...
Sent from my GT-P5210 using Tapatalk

Keep having error while compiling kernel :"(

Daniel-TAz00 said:
Once you have downloaded and verified Mod57's rom
Click to expand...
Click to collapse
Thank your for your work. This is what I've been looking a long time for.
Please, would you provide a flashable zip of the rom with your kernel? It looks like I'm doing something wrong.
After flashing the modified rom my P5210 just keeps showing the wird boot logo and wont boot up at all.
Thanks in regard!

@Max4000 Do you realize that what Daniel-TAz00 original article is about!
He is showing us a way to run Aircrack-ng in a Ubuntu VNC session with our TAB3 wifi turned off but with a external USB WIFI Dongle!!!!.
He also suggest it will be nice if somebody, created the modification on our own TAB3 10.1 driver sources and compiled it in a new kernel. It was just a suggestion. Then a few commented but no buddy gave the final answer.
I did not follow his steps. I do not even understood why he start with a new TAB3 rom! And a new boot.img. I guess he gave that as a reference as how he did it.
@Jacker31 What is what you are trying to compile, your sources and steps? And what is the exact error?
This is an interested topic to me. But I been sick for more than a week.

r2d23cpo said:
@Max4000 Do you realize that what Daniel-TAz00 original article is about!
He is showing us a way to run Aircrack-ng in a Ubuntu VNC session with our TAB3 wifi turned off but with a external USB WIFI Dongle!!!!.
He also suggest it will be nice if somebody, created the modification on our own TAB3 10.1 driver sources and compiled it in a new kernel. It was just a suggestion. Then a few commented but no buddy gave the final answer.
I did not follow his steps. I do not even understood why he start with a new TAB3 rom! And a new boot.img. I guess he gave that as a reference as how he did it.
@Jacker31 What is what you are trying to compile, your sources and steps? And what is the exact error?
This is an interested topic to me. But I been sick for more than a week.
Click to expand...
Click to collapse
Well it have been a long story, I posted a thread about my error, here : http://forum.xda-developers.com/general/help/question-error-2-error-compiling-x86-t3047439 but in the end i found out i used the wrong toolchain. So i redownloaded the correct version and try again. It works but another error popup, its about some Broadcom error. I can successfully compile it after i disabled it in menuconfig. But instead of getting a Zimage i got a Bzimage. So Idk what to do with it. I googled a tones of information but still have no idea what to do with that bzimage. I used Kali Linux to compile and those kernel files are from http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=p5220 GT-P5220_SEA_KK_Opensource. Now i am trying to install builduntu and try to compile it again. Any tips or helps? especially with that bzimage

Daniel-TAz00 said:
Hi,
This kernel/rom lets you connect an RT8187 USB Wifi adapter to your GT-P5210 and run aircrack-ng/airmon-ng/airodump-ng through Linux on Android.
[...]
Once you have downloaded and verified Mod57's rom, open up the zip and replace boot.img with this one:
https://www.dropbox.com/s/9gfucdzsadciy66/boot.zip
MD5: 4dd95a78c78550586cf3c2f7953978ab boot.img
Click to expand...
Click to collapse
r2d23cpo said:
@Max4000 Do you realize that what Daniel-TAz00 original article is about!
He is showing us a way to run Aircrack-ng in a Ubuntu VNC session with our TAB3 wifi turned off but with a external USB WIFI Dongle!!!!.
He also suggest it will be nice if somebody, created the modification on our own TAB3 10.1 driver sources and compiled it in a new kernel. It was just a suggestion. Then a few commented but no buddy gave the final answer.
I did not follow his steps. I do not even understood why he start with a new TAB3 rom! And a new boot.img. I guess he gave that as a reference as how he did it.
Click to expand...
Click to collapse
I get it. He offers a kernel and tells to place it in an flashable zip of an other firmware.
This is not a new firmware, it's just a kernel.
Maybe someone can create a flashable zip of the kernel he has linked to. So I would try to flash it separately.

Max4000 said:
Maybe someone can create a flashable zip of the kernel he has linked to. So I would try to flash it separately.
Click to expand...
Click to collapse
I'll upload a complete zip for you, it's just gonna take a little while ....

OHH BOY!
This is Daniel-TAz00 thread, so he know what he is finally offering you when he said.
Daniel-TAz00 said:
I'll upload a complete zip for you, it's just gonna take a little while ....
Click to expand...
Click to collapse
Now what will be this "complete zip" he is offering! I hope is your desired kernel.
Max4000 said:
I get it. He offers a kernel and tells to place it in an flashable zip of an other firmware.
This is not a new firmware, it's just a kernel...
Click to expand...
Click to collapse
Max4000 In your quote
This kernel/rom lets you connect an RT8187 USB Wifi adapter to your GT-P5210 and run aircrack-ng/airmon-ng/airodump-ng through Linux on Android.
Click to expand...
Click to collapse
You are just looking in "This kernel/rom" at the beginning. While I am trying to tell you to look at the end "through Linux on Android."
So yes that kernel may have the "external RT8187 USB Wifi adapter driver" but in order to run "aircrack-ng/airmon-ng/airodump-ng" you need to run it through Linux....
Clearly the best approach is to use our internal wifi and some how run "aircrack-ng/airmon-ng/airodump-ng" without the need of "Linux" chrooted on Android.
@ Jacker31 I answered in your thread
http://forum.xda-developers.com/showpost.php?p=59310924&postcount=2

Here: https://www.dropbox.com/s/q27inuf6jmnhvdm/P5210UEUAMI8-Custom.zip?dl=0 942MB
It's what has been running on my tablet since I made the topic. If your tablet turns into a magic mushroom, it wasnt my fault

@r2d23cpo Thanks it was helpful for that Android Kitchen part How do you create a flashable .zip out of boot.img? I am thinking of using philz to create a custom rom backup and replace the boot.img with the one i modded.
@ Jacker31 I answered in your thread
http://forum.xda-developers.com/show...24&postcount=2
Click to expand...
Click to collapse
@Daniel-TAz00 Do you just edit the zimage or you even edited ur ramdisk? Eg: copy .ko modules into lib/modules/?

Jacker31 said:
@r2d23cpo Thanks it was helpful for that Android Kitchen part How do you create a flashable .zip out of boot.img? I am thinking of using philz to create a custom rom backup and replace the boot.img with the one i modded.
Click to expand...
Click to collapse
I did it with 7zip, open zip, replace boot.img, save zip, flash zip
Jacker31 said:
[MENTION=5688554]r2d23cpo[/MENTION
@Daniel-TAz00 Do you just edit the zimage or you even edited ur ramdisk? Eg: copy .ko modules into lib/modules/?
Click to expand...
Click to collapse
I compiled my zimage, and that was pretty much it i think

@Daniel-TAz00 Didn't expect was that easy XD just 7zip haha, gotta try it out after my dinner XD hope it works. I will post it if it works with p5220 since your post is for p5210. I have to agree with you that there is really rare to see Galaxy tab 3 10.1 series (00, 10 or 20(LTE)) development going, guess maybe there is limited advanced users on tab 3 10.1 series.

Is it possible to make a update.zip? If so how?

Daniel-TAz00 said:
Here: https://www.dropbox.com/s/q27inuf6jmnhvdm/P5210UEUAMI8-Custom.zip?dl=0 942MB...
Click to expand...
Click to collapse
@Daniel-TAz00 First thanks. Nice work. But can you tell us if your "942MB" file is just the same
This kernel/rom lets you connect an RT8187 USB Wifi adapter to your GT-P5210 and run aircrack-ng/airmon-ng/airodump-ng through Linux on Android.
Click to expand...
Click to collapse
In particular it is VNC Linux on Android
Now I think @Jacker31 is here for the fun of learning kernel compile and finding a way to implement "aircrack-ng/airmon-ng/airodump-ng" with TAB3 10.1 own Wifi and without Linux VNC. That is what I guess from his post.
Jacker31 said:
... it was helpful for that Android Kitchen part...
Click to expand...
Click to collapse
Thanks goes to the Greatest creator @osm0sis. Last time he complains on me for saying it was another Kitchen. So NOOOO It is the best Kitchen in xda. I know all this nice applications get hidden on so many post. @moonbutt74 was the one to point me to use AIK.
Jacker31 said:
... How do you create a flashable .zip out of boot.img? I am thinking of using philz to create a custom rom backup and replace the boot.img with the one i modded. ...
Click to expand...
Click to collapse
I will answer down
Jacker31 said:
... Do you just edit the zimage or you even edited ur ramdisk? Eg: copy .ko modules into lib/modules/?
Click to expand...
Click to collapse
You see Jacker31 is trying to include the needed driver in a kernel. But that is only a step.
So, which modules Tab3 10.1 own wifi? If so you need to recall that first we need to modify our driver bcmdhd to allow promiscuous communication!
Jacker31 said:
@Daniel-TAz00 Didn't expect was that easy XD just 7zip haha, gotta try it out after my dinner XD hope it works. I will post it if it works with p5220 since your post is for p5210. I have to agree with you that there is really rare to see Galaxy tab 3 10.1 series (00, 10 or 20(LTE)) development going, guess maybe there is limited advanced users on tab 3 10.1 series.
Click to expand...
Click to collapse
So I guess once you read this is going to be late, I was going you suggest to backup your own boot.img first! I do still you are a bit confuse it is not just ZIP!! see below
Code:
dd if=/dev/block/mmcblk0p10 of=/sdcard/mmcblk0p10.img bs=4096
Jacker31 said:
Is it possible to make a update.zip? If so how?
Click to expand...
Click to collapse
Yes, you see it is not just zip. In fact you need to make your own update.zip.
@Jacker31
1) So here is what you need to read. In this forum just search for "Edify", "updater script" and see how the script is build.
2) Please keep in mind that every device is different, in particular the partitions are in different places and in our case we are nor ARM but x86 or more technical we belong to the i686 family.
So if you unpack recovery.img an look inside the ramdiskfs you can find "/etc/recovery.fstab". By doing "cat /etc/recovery.fstab"
you will see
Code:
# mount point fstype device [device2]
/config ext4 /dev/block/mmcblk0p3
/cache ext4 /dev/block/mmcblk0p6
/system ext4 /dev/block/mmcblk0p8
/data ext4 /dev/block/mmcblk0p9 length=-16384
/recovery emmc /dev/block/mmcblk0p11
/boot emmc /dev/block/mmcblk0p10
/external_sd vfat /dev/block/mmcblk1p1
This tells you that "boot" is at partition "/dev/block/mmcblk0p10" and "recovery" at "/dev/block/mmcblk0p11".
So a valid script to introduce your new boot.img may read
Code:
ui_print("+++++++++++++++++++++++");
ui_print(" Galaxy Tab 3 gt-p52xx ");
ui_print("+++++++++++++++++++++++");
#
ui_print("Flashing boot.img");
ui_print("+++++++++++++++++++++");
#
#
package_extract_file("[COLOR="Blue"]boot.img[/COLOR]", "[COLOR="Blue"]/dev/block/mmcblk0p10[/COLOR]");
#
ui_print("Done");
ui_print("+++++++++++++++++++++");
Now I am attaching a update.zip skeleton. The needed part is in "update.zip\META-INF\com\google\android". There you will find "update-binary" valid for our x86 device. Observe how it is about 521KB. The ARM one is just around 125KB! Easily to distinguish. This "update-binary" is the program that will interpret the Edify commands that are store in "updater-script". So the "updater-script" holds the instructions.
In it you will find also "update.zip\META-INF\com\android". With "metadata" holds signature information when signed. And "otacert" with in fact holds the signature for ota validation. This files are only required when the update.zip is signed!! But that another process meant for distribution that I am not going to explain. In general when we test we do not sign the updtate.zip instead we disable that in the recovery menu, so that recovery accepts update.zip packages that are not signed. So I had include those for you knowledge but you can delete them if you want.
So the last file is "update.zip\boot.img". This is the file you are going to substitute and that you want to program.
And yes making the package is as simple of zipping all. Here is the important detail. When you zip the file you need to be in the same directory as the boot.img file is. So that the update.zip created do not contain an extra folder. In other words, when you double click a good update.zip you find quickly boot.img and META-INF folder. No extra folders.
Now waitttttt. That is just for your general knowledge. If you do use this info it is at your own risk. It is easily to do something wrong and break the device.
Example, Make sure you have a FULL battery before doing any firmware programing. The Charging mechanism is in boot image. If you have a bad boot image programing, then your device will not charge and if you get out of juice then you end up with a nonchargeable devices. It will feel that the device is dead, since you only way to charge will be to open the device and charge the battery separately!!!

OHHHH BOYY.
Now I am confuse! I guess it is my fault in assuming and not waiting for answers!
I guess Master Jacker31 was in fact into the Linux, he just release How to run Kali Linux on Galaxy Tab 3 10.1 => http://forum.xda-developers.com/gal...-to-run-kali-linux-galaxy-tab-3-10-1-t3050203
In any case I hope that my last post in update.zip is useful to him and others.

r2d23cpo said:
OHHHH BOYY.
Now I am confuse! I guess it is my fault in assuming and not waiting for answers!
I guess Master Jacker31 was in fact into the Linux, he just release How to run Kali Linux on Galaxy Tab 3 10.1 => http://forum.xda-developers.com/gal...-to-run-kali-linux-galaxy-tab-3-10-1-t3050203
In any case I hope that my last post in update.zip is useful to him and others.
Click to expand...
Click to collapse
@r2d23cpo
thanks for that answer, i am akinda into the linux, but there is plentyof stuff to get confused because of this x86 device and limited support from google. You are right, thats what i am going to research next, implement aircrack into the device it self and trying to find out that i can use the usb wifi dongle without turn off the build in wifi. Maybe you can surf facebook while attacking your neighbor network *joking* *its illegal anyways*

Well, Everything work well (I meant the script, I made some minor changes), except got stuck on that samsung Galaxy Tab 3 logo screen... I am trying to figure out why... I am trying to get a stock Boot.img and compile it again, since I used boot.img from philz back up...ANNNNNNNNNNNNND great bricked my device... not the first time though.

Jacker31 said:
Well, Everything work well, except got stuck on that samsung Galaxy Tab 3 logo screen... I am trying to figure out why...
Click to expand...
Click to collapse
I've got still the same problem.

Related

[GUIDE] Make any rom OS2SD

OS2SD for any rom ​
As I see there is many P500 users interested to put their ROM to sd card, so I'm providing this tutorial how to make any rom bootable from sd.
Requirements:
Linux or cygwin for Windows
Boot.img tools
Modified updater-script
Modified fstab
Correctly partitioned sdcard (Guide)
TWRP-OS2SD or TWRP-MULTI
Steps:
Replace updater-script in your's ROM zip with provided. It will probably work with all kitkat based roms. If not the idea is mounting /system on sd card so change all "mount("yaffs2", "MTD", "system", "/system");" lines with "mount("ext4", "EMMC", "/dev/block/mmcblk0p2", "/system");" in original updater-script
Extract bootimg-tools.zip and paste boot.img from your rom in same foder
Open terminal or cygwin, locate folder with boot.img tools and type "./extractboot boot.img"
This will create out folder. Replace fstab.p500 and init.qcom.rc in out/ramdisk with provided (they might need rework on older roms)
In terminal type "./packboot"
Now rename boot_new.img to boot.img and pase it to rom zip
Flash rom zip with one of provided TWRP versions
should probably work back thru 4.0 but froyo/gingerbread init won't mount any sd partitions before boot is completed.
just curious, why this partition layout?
I used p2 for /data until wiping it by accident several times swapping my sd to a phone with pre-os2sd recovery.
of course, I've modded my own os2sd partition map several times now experimenting, and the order doesn't seem to matter.
and i was wondering, could you post your twrp modifications for internal/os2sd hybrid? i had one kinda working but it was glitchy.
I used this configuration to keep swap working if enabled, because default is p3. Also p4 for /data because it not used by anything else, so it's safe. I think you are right, order doesn't impact performance. Will send you config of twrp then be on pc.
Sent from my LG-P500 using xda premium
HardLight said:
I used this configuration to keep swap working if enabled, because default is p3. Also p4 for /data because it not used by anything else, so it's safe. I think you are right, order doesn't impact performance. Will send you config of twrp then be on pc.
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
I'm not seeing any other ROMs of this style floating around.
The only reason I didn't leave p3 for swap is that it wasn't being used yet when I started with the os2sd stuff. I tried sticking it on p2 (instead of the stubby sd-ext I had there to satisfy the odd this-or-that which demanded sd-ext,) and that worked ok, but I hadn't set sd-swap as a default in any builds.
since you're building similar stuff now, maybe I'll drift mine into your partition map in the interest of some sort of unification. and I'd like to match up the twrps, too.
especially if the sd-swap is working well on the p500.
everybody who's been dealing with my versions for any length of time now since it came out in February, is used to having to upgrade recovery and deal with incompatible backups from earlier releases anyway.
thanks for your contributions.
Thank You
HardLight said:
OS2SD for any rom ​
As I see there is many P500 users interested to put their ROM to sd card, so I'm providing this tutorial how to make any rom bootable from sd.
Requirements:
Linux or cygwin for Windows
Boot.img tools
Modified updater-script
Modified fstab
Correctly partitioned sdcard (Guide)
TWRP-OS2SD or TWRP-MULTI
Steps:
Replace updater-script in your's ROM zip with provided. It will probably work with all kitkat based roms. If not the idea is mounting /system on sd card so change all "mount("yaffs2", "MTD", "system", "/system");" lines with "mount("ext4", "EMMC", "/dev/block/mmcblk0p2", "/system");" in original updater-script
Extract bootimg-tools.zip and paste boot.img from your rom in same foder
Open terminal or cygwin, locate folder with boot.img tools and type "./extractboot boot.img"
This will create out folder. Replace fstab.p500 and init.qcom.rc in out/ramdisk with provided (they might need rework on older roms)
In terminal type "./packboot"
Now rename boot_new.img to boot.img and pase it to rom zip
Flash rom zip with one of provided TWRP versions
Click to expand...
Click to collapse
Thank You for posting the guide as requested. Awesome, now I will try to make some ROMs bootable in sdcard, and try them in my phone.
bigsupersquid said:
should probably work back thru 4.0 but froyo/gingerbread init won't mount any sd partitions before boot is completed.
Click to expand...
Click to collapse
i think that you are wrong
i have a gingerbread installed on SD (and kitkat CM11 by mukulsoni on internal)
i used Multirom manager 5.1 by arnab321 based on work by Tassadar
http://forum.xda-developers.com/showthread.php?t=1828151
HardLight: can you make this procedure work like the one in Multirom ?
it allows me to have GB and KitKat installed at the same time, both are bootebel using the same recovery and im only a boot away from moving from one to the oder
danielboro said:
i think that you are wrong
i have a gingerbread installed on SD (and kitkat CM11 by mukulsoni on internal)
i used Multirom manager 5.1 by arnab321 based on work by Tassadar
http://forum.xda-developers.com/showthread.php?t=1828151
HardLight: can you make this procedure work like the one in Multirom ?
it allows me to have GB and KitKat installed at the same time, both are bootebel using the same recovery and im only a boot away from moving from one to the oder
Click to expand...
Click to collapse
multirom has preinit of its own, runs before GB init, and uses busybox to mount sd folders. It also mods init.rc to not mount the MTD partitions.
it would have to be recoded because, among other things, init.rc doesn't mount the filesystems anymore, it's moved to init.qcom.rc or init.device.rc (init.p500.rc or init.thunderc.rc in the current OS2SD versions.)
to use OS2SD like multirom, it would have to bind-mount folders or filesystem images from the card instead of mounting partitions directly, unless android can 'see' more than 4 card partitions now. It used to be limited to 4 back in GB.
Plus unless kexec is working every OS installed has to work with the kernel in the boot.img for tasssadar's original code (the app you're using is reflashing a new boot.img every time you change OS's, which will eventually trash your boot NAND memory,)
bigsupersquid said:
multirom has preinit of its own, runs before GB init, and uses busybox to mount sd folders. It also mods init.rc to not mount the MTD partitions.
it would have to be recoded because, among other things, init.rc doesn't mount the filesystems anymore, it's moved to init.qcom.rc or init.device.rc (init.p500.rc or init.thunderc.rc in the current OS2SD versions.)
to use OS2SD like multirom, it would have to bind-mount folders or filesystem images from the card instead of mounting partitions directly, unless android can 'see' more than 4 card partitions now. It used to be limited to 4 back in GB.
Plus unless kexec is working every OS installed has to work with the kernel in the boot.img for tasssadar's original code (the app you're using is reflashing a new boot.img every time you change OS's, which will eventually trash your boot NAND memory,)
Click to expand...
Click to collapse
ill start at the end
flashing boot is no worse then flashing a new rom but its less work and less time
i like GB for the speed and batt use but from time to time i need to run ting that wont work on GB(at list not on the 1 i chose after trying ~12 rom`s)
having kitkat installed and using multirom to change is faster
so, any chance of implementing the bind-mount option?
prite please
:fingers-crossed:
danielboro said:
ill start at the end
flashing boot is no worse then flashing a new rom but its less work and less time
i like GB for the speed and batt use but from time to time i need to run ting that wont work on GB(at list not on the 1 i chose after trying ~12 rom`s)
having kitkat installed and using multirom to change is faster
so, any chance of implementing the bind-mount option?
prite please
:fingers-crossed:
Click to expand...
Click to collapse
Just install your GB rom to internal memory and cm11 OS2SD to sd card, then make two flashable zips (or backups) of both roms boot.img and flash them respectively to rom you want to boot. Just keep in mind that GB won't be able to use sd-ext, because it's os2sd system partition.
Sent from my LG-P500 using xda premium
HardLight said:
Just keep in mind that GB won't be able to use sd-ext,
Click to expand...
Click to collapse
this is way i was hoping for the mount-bind
at the moment GB is on P2, swap on P3 and kitkat uses P4 as /sd-ext
i have some limited knowledge, ill try to see if i can do something wen ill have the time
any pointer on how i can use mount-bind ?
all the work on developing the p500 helps extend it life
thanks
p.s.
what is the MULTI in TWRP-MULTI?
danielboro said:
this is way i was hoping for the mount-bind
at the moment GB is on P2, swap on P3 and kitkat uses P4 as /sd-ext
i have some limited knowledge, ill try to see if i can do something wen ill have the time
any pointer on how i can use mount-bind ?
all the work on developing the p500 helps extend it life
thanks
p.s.
what is the MULTI in TWRP-MULTI?
Click to expand...
Click to collapse
the multi can flash os2sd & normal rom, so you have not to change between recoveries
ThAnKs
Thanks alot for this guide.....
have anyone tried it on an ICS rom ?
getting this error using cygwin
{
"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"
}
maybe it doesnt work with cygwin , i am trying to make genetICS 9.1.6 OS2SD compatible ..
nomancoolboy said:
getting this error using cygwin
maybe it doesnt work with cygwin , i am trying to make genetICS 9.1.6 OS2SD compatible ..
Click to expand...
Click to collapse
For starters , you need Perl installed for that script.
Second, ics don't use fstab, you'll have to change init.rc
And maybe even recompile init with a delay inside, like on GB.
otherwise init may not mount the card partitions.
The easy way to run ICS from card is tasssadar's multirom. You can find the thread buried in this forum.
I'm using HardLight's GenetICS 9.1.7 with the OS2SD mod. It's the most stable and smoothest with long battery life and 1.5GB in the data partition for my apps. Also successfully made it with Hephappy's ICS Plus simply modifying the updater-script inside the zip and search the mounting points in the 'init.rc' and 'init.qcom.rc', then just have to modify the lines following the first post.
Greetings from Costa Rica!
Enviado desde mi LG-P500 usando Tapatalk
@HardLight
This is twrp-multi, renamed to boot.img. I have previously extracted recovery images this way using apktool.
[email protected]:~/bootimg-tools$ ./extractboot boot.img
Page size: 2048 (0x00000800)
Kernel size: 2803424 (0x002ac6e0)
Ramdisk size: 2294087 (0x00230147)
Second size: 0 (0x00000000)
Board name:
Command line: mem=471M console=ttyMSM2,115200n8 androidboot.hardware=p500 no_console_suspend
Writing boot.img-kernel ... complete.
Writing boot.img-ramdisk.gz ... complete.
gzip: ../../boot.img-ramdisk.gz: not in gzip format
cpio: premature end of archive
Any other tools needed to make this work? (ubuntu 14.04)
manu3193 said:
I'm using HardLight's GenetICS 9.1.7 with the OS2SD mod. It's the most stable and smoothest with long battery life and 1.5GB in the data partition for my apps. Also successfully made it with Hephappy's ICS Plus simply modifying the updater-script inside the zip and search the mounting points in the 'init.rc' and 'init.qcom.rc', then just have to modify the lines following the first post.
Greetings from Costa Rica!
Enviado desde mi LG-P500 usando Tapatalk
Click to expand...
Click to collapse
Can you share the modified files to be replaced in the rom.
hi all - thanks for these instructions. I tried to apply these to cm-9.1.5-GenetICS-Final-P500+gapps.zip and cm-9.1.7-GenetICS-HardLight-p500.zip.
In those roms I had to update the updater-script (I had to remove the format command otherwise the install would fail - but i figured that should be ok since the ext4 partition can be formatted externally - if i remember to do it).
I also updated the init.rc in the (mount mtd partitions section), but no updates to the init.qcom.rc
Each time I try to install a ROM, the device gets stuck at the LG boot logo.
I get the same problem with those zip's installing from TWRP MULTI's "Internal" mode. So I suspect something else is wrong...
interestingly, the only zip I can install successfully is the cm11.0.0-20160101-os2sd-ext4-p500.zip. Works like a charm, just dies in a matter of hours with Wifi on.
eldamobo said:
hi all - thanks for these instructions. I tried to apply these to cm-9.1.5-GenetICS-Final-P500+gapps.zip and cm-9.1.7-GenetICS-HardLight-p500.zip.
In those roms I had to update the updater-script (I had to remove the format command otherwise the install would fail - but i figured that should be ok since the ext4 partition can be formatted externally - if i remember to do it).
I also updated the init.rc in the (mount mtd partitions section), but no updates to the init.qcom.rc
Each time I try to install a ROM, the device gets stuck at the LG boot logo.
I get the same problem with those zip's installing from TWRP MULTI's "Internal" mode. So I suspect something else is wrong...
interestingly, the only zip I can install successfully is the cm11.0.0-20160101-os2sd-ext4-p500.zip. Works like a charm, just dies in a matter of hours with Wifi on.
Click to expand...
Click to collapse
roms not built for kernel swapped system/userdata (kitkat only built this way, and not older kitkat versions) will flash to the wrong partition and won't boot.
change your updater-script to switch system and userdata for older roms to flash correctly with the twrp-multi in internal mode.

Patching sepolicy in the ramdisk to achieve root without permissive kernel

UPDATE 2: Tutorial and Patched Boot.imgs available here.
UPDATE: Chainfire's suggestion to patch sepolicy in the ramdisk for Samsung LL ROMS works perfectly. For unknown reasons, ODIN flash would not work, but flashing the patched boot.img with TWRP allowed me to successfully achieve root with a fully stock kernel and SEAndroid Enforcing. All the information you need is in the sources I quote below. Once I am confident that everything is working fine, I will create another thread with a concise guide and my patched boot.img for those who don't want to get their hands dirty. In the meantime, anybody who sees this should know that the same process can be done with the P605 as well, with your native ROM instead of a ROM from a different region. Also, stock kernel means no wifi dropping problems either!
@garyd9
This thread is to discuss the possibility of rooting the Samsung Note 10.1 (2014 Edition) without resorting to a permissive kernel. The background information for this thread can be found from the following posts:
http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
Chainfire's method of patching the device's sepolicy with a reference device to give sudaemon the required permissions that open the doors for rooting and more.
http://forum.xda-developers.com/showpost.php?p=63250893&postcount=26
garyd9's application of Chainfire's idea to the Note 5, which appears to have worked successfully.
http://forum.xda-developers.com/showpost.php?p=63552454&postcount=2375
My attempt to replicate garyd9's method on the P607T, which failed.
http://forum.xda-developers.com/showpost.php?p=63555137&postcount=2376
garyd9's recommendation on how to troubleshoot.
And finally the results from following Gary's advice:
0 - Check
1 - Check
2 - Fail
Tools and Process: Listing all of them. The one I followed for this methodical approach is the first one. Including the others for context, in the hopes that it will indicate what the next step should be.
1) Carliv's Kitchen
Followed instructions, placed boot.img in the boot_resources folder, unpacked it with the tool, changed nothing, repacked with the same tool, made tar using "tar -cf boot_stock_repack.tar bootxxx.img" bootxxx.img is what Carliv generated, of course. To compare, made tar of the stock boot.img as well, naming it boot_stock.tar. Flashing boot_stock.tar works, device boots, no problems. Flashing the boot_stock_repack.tar fails with "Unsupport dev_type" on the device.
Additional Info:
------------------------------------------------
2) bootimg_tools
split_boot to extract the kernel and ramdisk and unpack the ramdisk. No warnings are issued, nothing suggests there is any problem.
repack_ramdisk to repack ramdisk, no problems here either.
mkbootimg to create new boot.img; no arguments are specified since apparently it would automatically create the right image.
tar -cf to create ODIN flashable tar.
Flashing this would succeed in ODIN, but the device would reboot in Download Mode with "Unable to boot normal mode" showing on the device. 3 suggests an explanation why.
3) To extract the kernel and ramdisk, used umkbootimg instead of split_boot from the same toolset. This time, it issued a warning about the original img being created with a non-standard mkbootimg, said I should edit mkbootimg.c before making the new image. Despite the warning, it also provided a mkbootimg command to use to ensure the new img is created correctly. Googling the warning suggested downloading android source code to get the mkbootimg.c file, but nothing beyond that on what needs to be done.
While not optimistic, I still tried the mkbootimg command it gave me, as well as with extra arguments to correct the addresses till boot_info in the toolkit matched for the stock and new images. SAME outcome as with 2.
4) Modding_My_Mind/SHM's toolset
This one claimed to automatically make the necessary corrections for a non-standard boot image and definitely did something different. Unlike the other generated images which were smaller in size than the original, this one was the same size. Making a tar and flashing it though failed with Unsupport dev_type showing on the device. I have contacted SHM to see if he can shed some light on this.
NOTE: In the thread where I got this from, when dealing with a non-standard image, his output seems to show this warning. BUT, I got no such warning when I did this on my image.
5) Carliv's as in the first item here. It generated a boot.img that matched in size and failed with the same error as the previous, suggesting it is definitely making SOME changes to the mkbootimg arguments to work with the 'non-standard stock image', BUT I have no idea what these changes are, nor where to look for them.
Next Step?
I never tried a full manual repacking of the ramdisk and generation of the image. Not sure if the error could be in the way the ramdisk is being repacked (which seems improbable, since its a gzip + cpio command that does this, not much to mess up there), or if its the way in which the new img is being created (seems probable, given that many arguments need to be passed here and Im using binaries that I do not know and understand at all).
I tried to look for other ways to create the img file, BUT pretty much everything keeps pointing to these same toolsets and binaries. With regards process, I have not been able to find anything on how to make 'manual adjustments' to the addresses/offsets.
Any advice on where to go/look next?
Click to expand...
Click to collapse
This thread is started to continue exploring this option specifically for the Note 10.1 (2014 Edition). The idea is to achieve root by modifying only the ramdisk and not touching the kernel, and definitely NOT going to the extreme step of using a permissive kernel.
Can you post a boot.img that's known good? I don't use kitchens, dining rooms, or even bathrooms. I use my own compiled tools... (Are you doing all this work in linux or using win-blows?)
I've attached "imgtools.zip." Within are the linux binaries I use for unpacking and repacking boot images. They should work under ubuntu 64-bit 14.04.
Here's some idea of how you might use them (again, linux..)
Code:
# assumes "boot.img" in the cwd is the original boot image.
mkdir stockboot
# unpack the boot image into a new directory called "stockboot"
unpackbootimg -i boot.img -o stockboot
That will dump a bunch of files into that new directory...
Now, to remake it:
Code:
cd stockboot
mkbootimg --kernel boot.img-zImage --ramdisk boot.img-ramdisk.gz --base `cat boot.img-base` --pagesize `cat boot.img-pagesize` --kernel_offset `cat boot.img-kerneloff` --ramdisk_offset `cat boot.img-ramdiskoff` --tags_offset `cat boot.img-tagsoff` --dt boot.img-dtb -o ../newboot.img
What that does is goes into the directory we unpacked the original image to, and then just puts it back together in the original directory under a new name (newboot.img.) For all the parameters, we just re-use the values and items extracted from the stock boot image. The new image won't be identical to the old one, but the sizes should be close.
garyd9 said:
Can you post a boot.img that's known good? I don't use kitchens, dining rooms, or even bathrooms. I use my own compiled tools... (Are you doing all this work in linux or using win-blows?)
Click to expand...
Click to collapse
tar of stock boot.img attached. Until Carliv's kitchen, all attempts were on Slackware 14.1. Only Carliv's was done on Win 10.
garyd9 said:
I've attached "imgtools.zip." Within are the linux binaries I use for unpacking and repacking boot images. They should work under ubuntu 64-bit 14.04.
Click to expand...
Click to collapse
Will take a shot at it tomorrow with your binaries and post results.
karthikrr said:
tar of stock boot.img attached. Until Carliv's kitchen, all attempts were on Slackware 14.1. Only Carliv's was done on Win 10.
Click to expand...
Click to collapse
I'm not going to talk about that. I have a semi-religious belief that anyone using windows to manipulate linux kernel images is BEGGING for trouble. (It's not that I'm anti-windows. I'm just against mixing the platforms.)
Anyway, followed my own directions to unpack and repack your boot.img. I took the resulting newboot.img and zip'd it up (and attached it here.) This is NOT a TWRP/CWM flashable zip. It's just archived to save space (and make XDA's file manager happy.)
I didn't see any strange messages about non-standard images or anything like that. In fact, the process was outright boring.
(FYI, I might not be capable of responding to messages again until late tomorrow night or Sunday...)
Code:
~/temp$ unpackbootimg -i boot.img -o stockboot
BOARD_KERNEL_CMDLINE console=null androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 ehci-hcd.park=3
BOARD_KERNEL_BASE 00000000
BOARD_PAGE_SIZE 2048
BOARD_KERNEL_OFFSET 00008000
BOARD_RAMDISK_OFFSET 02000000
BOARD_TAGS_OFFSET 01e00000
BOARD_DT_SIZE 1574912
oh, that might not boot for you. my repack cmdline doesn't pull in the cmdline from the kernel unpack. Add something like this to the mkbootimg cmdline:
Code:
--cmdline "`cat boot.img-cmdline`"
(You might have to actually type out the cmdline inside the quotes instead)
garyd9 said:
I didn't see any strange messages about non-standard images or anything like that. In fact, the process was outright boring.
Click to expand...
Click to collapse
Not surprised . Most tools available won't give this information. Its typically only available as a cosmetic feature. My work is derived from Xialou's as seen here but modified to work for Linux and ARM alike.
I have attached images showing me unpacking and repacking his stock boot.img from my device.
{
"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"
}
With that said, I have been researching this error, "unsupported dev_type", and most of what I have came across points to it being a specific issue with Odin itself. However, I can't really rule this out because his device does not have root so I presume he can't write the boot image to his boot partition using the dd command in a terminal to verify if it will boot up using this method. If it were to boot up then it would clearly point the problem towards the Odin program being used.
Sent from my Ascend Mate 2 using Tapatalk
---------- Post added at 02:21 PM ---------- Previous post was at 01:59 PM ----------
@karthikrr, when making an Odin compatible package you are using the command:
Code:
tar -cf
I don't own a Samsung device but I have helped build TWRP for some so given my experience shouldn't the command actually be:
Code:
tar -H ustar -c boot.img > Odin_boot.tar
Where Odin_boot.tar is the package used to install via Odin.
Please use that command i just shared with you and try again.
Sent from my Ascend Mate 2 using Tapatalk
garyd9 said:
oh, that might not boot for you. my repack cmdline doesn't pull in the cmdline from the kernel unpack. Add something like this to the mkbootimg cmdline:
Code:
--cmdline "`cat boot.img-cmdline`"
(You might have to actually type out the cmdline inside the quotes instead)
Click to expand...
Click to collapse
SHM said:
I don't own a Samsung device but I have helped build TWRP for some so given my experience shouldn't the command actually be:
Code:
tar -H ustar -c boot.img > Odin_boot.tar
Where Odin_boot.tar is the package used to install via Odin.
Please use that command i just shared with you and try again.
Click to expand...
Click to collapse
Short version: No luck!
Long version:
In all cases, just unpack stock boot.img and make new stock boot.img, no changes.
Gary, everything except for the ODIN flash was done on Linux for the following.
SHM, all tars created using your command.
1) Used Gary's tools following all instructions including cmdline to create garyboot.img and then .tar
2) Used SHM's tools to try again, this time with his tar cmd to create shmboot.tar
3) Found a mkbootimg binary in the P607T KK Source from Samsung's opensource portal. Used that to create P607Tboot.tar from the img unpacked by Gary's tools.
4) This might have been completely off-base, but ... Used xialou's mkboot-master source code; edited mkbootimg.c with the Non-Standard addresses from SHM's image above. Ran make to compile a new binary, used it to create recboot1.tar
5) umkbootimg from another toolset gave me a different set of addresses to change in the mkbootimg.c file, this time to change kernel offset, ramdisk offset and second offset. New binary again, after make clean and make, used it to create recboot2.tar
ODIN 3.10.6 failed with the same unsupport dev_type error with ALL of these images.
Tried the first two with ODIN 3.09, no difference, same error again.
Questions:
SHM, your image above, as well as the warning on umkbootimg both say Modify mkbootimg.c and try again ... Should I look into this more?
Is there ANY chance that the problem is not with mkbootimg, but with unpackbootimg?
SHM, you mentioned unsupport dev_type in context with ODIN problems. Where can I find more info on this? FWIW, I have never had ODIN problems before, flashing firmware updates and twrp on this tablet, as well as on my Note 2 phone. Can't think why only in this case, it should fail like this.
What are my alternatives to ODIN? Can I flash using twrp? I have never created a twrp flashable zip, so will go read up on that some now, but do you think it makes sense to try that? If not, are there any other methods of flashing to try before being absolutely sure the problem is with mkbootimg?
@karthikrr, if you have the latest twrp for your device than there is something you need to try to see if in fact this is a problem with Odin specifically. I want you to take your boot.img that has been unpacked and repacked but don't make it into a tar. Leave it as an image. Boot up TWRP then select Install. At the bottom right of your screen will be a button that says, zip. If you click on it you will see it change to, image. This allows you to install either a flashable zip or flash a boot/recovery.img. Select to install the boot.img. The next screen will ask you to select either the boot or recovery partition based upon the image you chosen. In this case, choose the boot partition. Swipe to proceed. When done, reboot your system. If your device boots up successfully then your problem lays with Odin. Let me know if these instructions are a bit confusing.
Sent from my Ascend Mate 2 using Tapatalk
SHM said:
@karthikrr, if you have the latest twrp for your device than there is something you need to try to see if in fact this is a problem with Odin specifically.
Click to expand...
Click to collapse
No confusion, I even have all the imgs loaded on the device to try this. Two reasons I did not try it yet, perhaps you can clarify whether these are legitimate concerns:
1) TWRP is formally not out for LL on my device yet. I, like everybody else out there, is using the latest KK img on this device and it SEEMS to be working properly. The only noticeable difference I have seen is that it seems to take a lot longer to get into twrp than usual. But I made some 5 backups of the device yesterday and all of them seemed to be fine. Given this is not official for LL, I wasn't sure if it was wise to try to flash an image from twrp.
2) I was also concerned that PERHAPS Odin is doing me a favour and aborting the flash because there was something wrong, and that if I went with twrp and it flashed it without any problems, I might find that it killed my device. I was discussing this with a friend (no experience with Android flashing, but a developer who knows these things) and he said it was highly unlikely that this would happen, as long as the img I was flashing was within the size limit for my device, which I believe is 11mb. All the images are 10.5mb. Thoughts?
karthikrr said:
No confusion, I even have all the imgs loaded on the device to try this. Two reasons I did not try it yet, perhaps you can clarify whether these are legitimate concerns:
1) TWRP is formally not out for LL on my device yet. I, like everybody else out there, is using the latest KK img on this device and it SEEMS to be working properly. The only noticeable difference I have seen is that it seems to take a lot longer to get into twrp than usual. But I made some 5 backups of the device yesterday and all of them seemed to be fine. Given this is not official for LL, I wasn't sure if it was wise to try to flash an image from twrp.
2) I was also concerned that PERHAPS Odin is doing me a favour and aborting the flash because there was something wrong, and that if I went with twrp and it flashed it without any problems, I might find that it killed my device. I was discussing this with a friend (no experience with Android flashing, but a developer who knows these things) and he said it was highly unlikely that this would happen, as long as the img I was flashing was within the size limit for my device, which I believe is 11mb. All the images are 10.5mb. Thoughts?
Click to expand...
Click to collapse
If the partition table between KK and LP does not vary on your device then it will be fine.
As for flashing a boot image to your boot partition via twrp, this will not brick your device. Worse case, device doesn't get past the bootloader or the boot animation. In this case, use twrp to install your stock boot.img to your boot partition.. If you have a backup of your boot image then restore that. Either way you will be OK.
Sent from my Ascend Mate 2 using Tapatalk
SHM said:
If the partition table between KK and LP does not vary on your device then it will be fine.
As for flashing a boot image to your boot partition via twrp, this will not brick your device. Worse case, device doesn't get past the bootloader or the boot animation. In this case, use twrp to install your stock boot.img to your boot partition.. If you have a backup of your boot image then restore that. Either way you will be OK.
Sent from my Ascend Mate 2 using Tapatalk
Click to expand...
Click to collapse
IT WORKS!!!
Flashed a stock boot.img using TWRP to be safe, was fine. Patched the ramdisk again, created a new patchedboot.img using the binary I pulled from the P607T sources, crossed my fingers and flashed it with TWRP, the device booted successfully. There was a SEAndroid Not Enforcing; Set Warranty Bit Kernel message while it booted, but I don't care about Knox. Once I confirmed that it booted and worked alright, back to recovery, flashed SuperSU Beta 2.52, rebooted, and I HAVE ROOT!!!
No idea why Odin would fail to flash, but confirmed working with TWRP. Do you know what the policy is on me creating a thread and uploading my patchedboot.img for others to use? I am no developer, and I have no idea if the rules prohibit me from putting this up. I do know though that not everybody is going to go through this whole manual process to get root, and too many are resorting to permissive kernels to get root. Ideally, I will also repeat this process is someone sent me a P605 boot.img, so they too can have root with stock kernel. Just not sure where this thread should go, and if I can even make one.
In anycase, THANK YOU SO MUCH BOTH OF YOU FOR TAKING THE TIME TO WALK ME THROUGH THIS! Much appreciated
Glad you got it working. If you want to post the image, I'd suggest posting in the dev section for the device. (If it's just a repack of the stock kernel, don't use the original dev...) Yes, it is allowed to do that. Being that you aren't recompiling anything, there's no need for you to post any source code (but it might be nice to link to the source from samsung's site. We all know that Samsung doesn't update that anyway.)
Take care
Gary
Thanks for the suggestions on how and where to post. I think I will take the time to write out a decent tutorial and then post it with this image in the dev forum. Im sure the P605 users will also want to do this with theirs, so they are not stuck with an unsecure kernel!
karthikrr said:
Thanks for the suggestions on how and where to post. I think I will take the time to write out a decent tutorial and then post it with this image in the dev forum. Im sure the P605 users will also want to do this with theirs, so they are not stuck with an unsecure kernel!
Click to expand...
Click to collapse
Good luck with your future endeavors. I'm currently fighting with sepolicy right now with my CM13 builds lol. Whole other battle right there haha.
Sent from my Ascend Mate 2 using Tapatalk

config errors when flashing

{
"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"
}
attached is recovery log sir
Er. Aditya said:
attached is recovery log sir
Click to expand...
Click to collapse
The error you see in recovery is one we have seen already and I don't know how to fix it or why it's broken. I think it has something to do with Windows though. It seems the config directory in the rom is not getting extracted to /tmp. When it tries to run /tmp/configure.sh it does not exist. Then it tries to get info from /tmp/config which is also not there because configure.sh was never run to create it. The problem is that the zips appear to be the same with the same contents, same updater-script contents, etc. If built on Windows it does not work. If built on Linux it works. I am not a Windows guy (for these and many other reasons lol) so I have no idea what the difference is. If you have any ideas please let me know. Has anyone built a working flashable zip on Windows using this kitchen?
SuperR. said:
sepolicy-inject is not available for windows currently. I should have removed the option for Windows, and will in the next update. Is this a feature that still needs to stick around? I am not sure if I can get it working in Windows due to the pre-compiled Linux libs in the source. I am also not sure if you can compile libsepol on Windows. If you can get this source compiled for Windows, I can add the feature
The error you see in recovery is one we have seen already and I don't know how to fix it or why it's broken. I think it has something to do with Windows though. It seems the config directory in the rom is not getting extracted to /tmp. When it tries to run /tmp/configure.sh it does not exist. Then it tries to get info from /tmp/config which is also not there because configure.sh was never run to create it. The problem is that the zips appear to be the same with the same contents, same updater-script contents, etc. If built on Windows it does not work. If built on Linux it works. I am not a Windows guy (for these and many other reasons lol) so I have no idea what the difference is. If you have any ideas please let me know. Has anyone built a working flashable zip on Windows using this kitchen?
Click to expand...
Click to collapse
U can surely remove that feature if u like hardly used ....
I am gonna make a rom on linux too and see if that flashes...u need anything to compare or check sir ?
I remember last time too i had issue for mounting when rom created on linux..let me try one now and report back
edit :\ @SuperR. dev check this screenshot
it shows mounting error still rom flashed and booted good
Er. Aditya said:
U can surely remove that feature if u like hardly used ....
I am gonna make a rom on linux too and see if that flashes...u need anything to compare or check sir ?
I remember last time too i had issue for mounting when rom created on linux..let me try one now and report back
edit :\ @SuperR. dev check this screenshot
it shows mounting error still rom flashed and booted good
Click to expand...
Click to collapse
It may have already been mounted so it gave an error. We can deal with that later since it flashed and booted. Now we need to find out what the difference is between the Linux created ROM and the Windows created ROM. Were they both created using the same kitchen version, same firmware, same procedure? The ONLY difference is Windows vs. Linux, right? If so, can you send the updater-script from both so I can compare?
Using Windows for building android is kinda looking like someone taking square wheels to a skatepark and expecting fluid motion.. [emoji23] [emoji23]
Sent from my N9515 using Tapatalk
bcrichster said:
Using Windows for building android is kinda looking like someone taking square wheels to a skatepark and expecting fluid motion.. [emoji23] [emoji23]
Sent from my N9515 using Tapatalk
Click to expand...
Click to collapse
These wheels are rolling faster each day. We will ride
SuperR. said:
These wheels are rolling faster each day. We will ride
Click to expand...
Click to collapse
Lmao. Right on! If anyone can get this right, it's You and these guys helping here @SuperR. [emoji41] Catching some air!
Sent from my N9515 using Tapatalk
SuperR. said:
It may have already been mounted so it gave an error. We can deal with that later since it flashed and booted. Now we need to find out what the difference is between the Linux created ROM and the Windows created ROM. Were they both created using the same kitchen version, same firmware, same procedure? The ONLY difference is Windows vs. Linux, right? If so, can you send the updater-script from both so I can compare?
Click to expand...
Click to collapse
yes both were created using latest kitchen 3.0.1.4 , same firmware and procedure
here are the scripts sir
SuperR. said:
v3.0.1.8
Changes:
Windows: Use 7-zip (included) to extract img files instead of Imgextractor.
Windows: Fixed missing symlinks in updater-script.
Windows: Fixed many file contexts not being set correctly.
Windows/Linux: Fixed system/SYSTEM on devices that use SYSTEM.
Linux: Do not create metadata lines for symlinks.
I think this will fix most of the flashing problems. Let me know how it goes
WINDOWS NOTE: It is important that the tools get updated. The updater should take care of it, but if you get errors that 7z is not found, go to Misc tools > Reset tools.
IMPORTANT: Start your rom fresh and extract from system.img again. Make sure you delete 00_project_files directory if you are reusing an existing project.
Click to expand...
Click to collapse
i still got the error 7 even i clean cloned kitchen sir
Er. Aditya said:
i still got the error 7 even i clean cloned kitchen sir
Click to expand...
Click to collapse
Can you send the updater-script and recovery.log?
There is still one problem I need to solve for sure... file capabilities in Windows. Currently there is a file with capabilities listed and it is checked when creating an updater-script in Windows. In the case of your ROM, it is not accurate. The only non-standard capability in your firmware is /system/bin/run-as which is correct in your updater-script. However, the rest should all be 0x0 and there are a few that are not. You could try changing them to 0x0 and zip the ROM back up.
It has also crossed my mind that there may be something strange about the zip itself in Windows. I am not sure of this at all but in my tests of kitchen v3.0.1.8 and your firmware, the updater-script comes out nearly identical in Linux and Windows with only the above mentioned capability differences. Maybe the compression level of the zip is too high or low? You could try manually zipping the ROM to find out if the zip process is causing an issue.
It seems that not a single working flashable zip has come out of this kitchen running Windows so far and I am running out of ideas about what is causing it
edit: Attached below is a modified updater-script for your firmware with the capabilities corrected
SuperR. said:
Can you send the updater-script and recovery.log?
There is still one problem I need to solve for sure... file capabilities in Windows. Currently there is a file with capabilities listed and it is checked when creating an updater-script in Windows. In the case of your ROM, it is not accurate. The only non-standard capability in your firmware is /system/bin/run-as which is correct in your updater-script. However, the rest should all be 0x0 and there are a few that are not. You could try changing them to 0x0 and zip the ROM back up.
It has also crossed my mind that there may be something strange about the zip itself in Windows. I am not sure of this at all but in my tests of kitchen v3.0.1.8 and your firmware, the updater-script comes out nearly identical in Linux and Windows with only the above mentioned capability differences. Maybe the compression level of the zip is too high or low? You could try manually zipping the ROM to find out if the zip process is causing an issue.
It seems that not a single working flashable zip has come out of this kitchen running Windows so far and I am running out of ideas about what is causing it
edit: Attached below is a modified updater-script for your firmware with the capabilities corrected
Click to expand...
Click to collapse
u have been a rock and we are so glad ur trying to get this to work sir i am attaching a working script and supeR script with recovery log
edit : the modified one again gave that error
OMJ said:
Fyi, I was able to build & successfully flash a rom via Windows kitchen on the latest update
Click to expand...
Click to collapse
Woo hoooo!!!! That is great news...but also confusing lol. Now we need to figure out why @Er. Aditya is getting this:
Code:
Checking config ...
minzip: Extracted 1 file(s)
about to run program [/tmp/configure.sh] with 1 args
run_program: execv failed: No such file or directory
OMJ said:
Fyi, I was able to build & successfully flash a rom via Windows kitchen on the latest update
Click to expand...
Click to collapse
samsung device ?
SuperR. said:
v3.0.1.9
Changes:
Windows: Fixed b key press not being recognized.
Added a Back option to the root method options.
Only allow key presses that correspond to menu options.
Fixed project name adding an extra superr_ when creating new project from the project selection menu.
Set permissions of configure.sh to 777 instead of /tmp to 755.
@Er. Aditya - This includes the change I sent you in the PM. No clue if it will work for you, but worth a try. No need to extract the system.img again if you extracted using v3.0.1.8. Just change perm types to something else and then back to set_metadata and it will update the updater-script for you.
Click to expand...
Click to collapse
sadly it still dint worked :'(
i clean cloned again so no old kitchen leftovers
SuperR. said:
Woo hoooo!!!! That is great news...but also confusing lol. Now we need to figure out why @Er. Aditya is getting this:
Code:
Checking config ...
minzip: Extracted 1 file(s)
about to run program [/tmp/configure.sh] with 1 args
run_program: execv failed: No such file or directory
Click to expand...
Click to collapse
another fyi---I was getting the same but I usually rip out the config folder & code from updater-script, no need for it on my ROMs
Er. Aditya said:
samsung device ?
Click to expand...
Click to collapse
HTC
Er. Aditya said:
sadly it still dint worked :'(
i clean cloned again so no old kitchen leftovers
Click to expand...
Click to collapse
Do ROMs flash properly when created in kitchen v2.x ? If so, I am clueless about what is going on. If not, I clearly need to change how we mount/format.
OMJ said:
another fyi---I was getting the same but I usually rip out the config folder & code from updater-script, no need for it on my ROMs
Click to expand...
Click to collapse
At least that narrows the issue down to configure.sh, unless you manually zip your ROMs. If so, then it still could be the zip process which is handled by the Python zip() module currently. I could switch this over to 7-zip in Windows if needed now that it is included anyway.
SuperR. said:
Do ROMs flash properly when created in kitchen v2.x ? If so, I am clueless about what is going on. If not, I clearly need to change how we mount/format.
At least that narrows the issue down to configure.sh, unless you manually zip your ROMs. If so, then it still could be the zip process which is handled by the Python zip() module currently.
Click to expand...
Click to collapse
i have been having issues since this config.sh has been introduced sir
Er. Aditya said:
i have been having issues since this config.sh has been introduced sir
Click to expand...
Click to collapse
That is actually good news believe it or not It means that probably the kitchen is now producing working roms in Windows...just not in your device lol. We can work on getting it working for your device too I will need to figure out if we can get configure.sh to run on your device. I will put together some small flashable zips for testing if you don't mind. They won't change anything, just print on the screen so we can see if it works.
SuperR. said:
That is actually good news believe it or not It means that probably the kitchen is now producing working roms in Windows...just not in your device lol. We can work on getting it working for your device too I will need to figure out if we can get configure.sh to run on your device. I will put together some small flashable zips for testing if you don't mind. They won't change anything, just print on the screen so we can see if it works.
Click to expand...
Click to collapse
[emoji23] [emoji23] Nice!! [emoji41] [emoji41]
Sent from my N9515 using Tapatalk
Er. Aditya said:
I am ready!
Click to expand...
Click to collapse
Here are 3 to try. I may come up with some others if they don't work. When you flash it, we want to see the by-name path on the screen and not get errors. Let me know how it goes

[SM-G9750] Random root reboot fix (Snapdragon S10 & S10e probably, too)

WARNING: This won't work currently for the SM-G9730. I need a recovery.img(.lz4) from the latest firmware.
Here's a not-so-widely-tested fix for the spontaneous reboot that occurs after rooting the SM-G9750 and other Snapdragon S10 models.
tulth located this patch. If you read the description of that patch, it mentions a NULL pointer getting dereferenced in find_get_entry (such a thing tends to cause crashes in your average program, so when this happens in the kernel, it's not surprising that a crash and reset is the response). If you look at tulth's last_kmsg, my last_kmsg and G-ThGraf's last_kmsg from a G9730, you'll notice they all have one thing in common: SHTF at smaps_pte_range+0x29c. What's at that location on those devices' kernel? Why it's only find_get_entry(vma->vm_file. So yeah, it's the same bug, already known to Google and it's been fixed in their kernel tree since January. The bug is triggered externally by reading /proc/<pid>/smaps_rollup under certain conditions. You might be able to workaround this by disabling programs to get more free RAM, but The Only Way To Fix the Underlying Kernel Bug Is To Fix the Kernel Itself™.
We're probably not going to see a new kernel update until (if?) we get an update for the next major version of Android. We Snapdragon S10* users already have an older kernel compared to Exynos S10 owners (our 4.14.78 vs. their 4.14.85) and it's probably because of that they don't see this bug. So I think the idea of Samsung fixing this is a non-starter. While I did manage to build an SM-G9750 kernel from source (their instructions leave a lot to be desired) with that patch applied, I could not get my phone to boot the result.
I am not a programmer, but I do know just slightly enough to get the ball rolling and provide the fix that that aforementioned patch does in the opcode form that can be applied onto the existing kernel on the phone.
While I've not half-arsed it in the sense I took the easy way out (always having mss->check_shmem_swap set to zero is an easy one-liner workaround; however, freeing of unneeded SHM pages wouldn't happen, eventually causing your phone to crawl to a halt), I am not familiar with assembly language for any platform at all and, as such, I could not find a way to free up enough space in the show_smap function. So I jump quite far out into a chunk of the .text section where it's full of zeroes. I don't know anything about the ELF format to be able to tell you why this section of zeroes exists - I make the probably-wrong assumption it's perhaps a requirement of the ELF format if a linker that's very good at producing optimised code still bothers to output that or it's optimisation by alignment - but it's there and it's a good place to add extra code to on account of, you know, being empty and marked executable.
As far as I can see, where I have placed the code isn't referenced by anything else at all in the kernel but I can't be 100% certain on that. Nevertheless, I've been testing this on and off (I've had to manually initiate reboots in between for various reasons) myself for the past seven days or so and I've not noticed any adverse effects.
EDIT: Saying that, I think I'll try and move the code into load_module() when I get time because this kernel can't actually load modules (see below) thus much of the code there is pointless.The risk is yours, should you choose to apply this fix.
I would've liked to wrote this as a kernel module, being far easier to maintain, and hooked the relevant smap functions (in a similar vein to flar2's wp_mod and AleksJ's ric_mod) but thanks to the geniuses at Samsung, load_module() will always return early and the compiler accordingly realises it can optimise the function by excising all the code needed to actually load a module - there's no point in keeping unreachable code. Why Samsung bothered turning on mandatory module signing is beyond me because modules will never load! You can see this for yourself: insmod /system/vendor/lib/modules/wil6210.ko will always fail with "Exec format error", and that's a signed module built and shipped by Samsung themselves for their kernel. Anyway.
As long as the kernel version remains the same, it's likely, but not guaranteed, the same patches will work for future software updates from Samsung and all I'll have to do is update the compatibility list. If you try this on any other kernel version, the chances of not being able to boot are very high. The task of maintaining this doesn't enthuse me, but I'll continue to do so out of necessity, for I like having a rooted phone but not one that restarts at the worst of times.
{
"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"
}
I know people have reported longer uptimes than that on their phone before having a forced restart, but in my case, my phone has AOD enabled, the latest stable Magisk version installed and is running EdXposed. Before this fix, I've never seen an uptime longer than about 16 hours (usually less), regardless of whether the phone was in use or not, as getting multiple restarts in a day tends to have that effect.
As long as you only write to the recovery partition (and that's the only block device that this guide tells you to write to ), you should always be able to use Odin to reflash it to reverse this, the process being somewhat similar to flashing Magisk in the first place but with the notable exception of not needing to factory reset anything. The following flashing routine was adapted from Magisk, so my thanks to topjohnwu.
If someone has the bright idea of sharing their already-patched recovery.img because typing copy and pasting commands is hard, I'll point out the following: anybody flashing such an image should really make sure they're running the same firmware and Magisk version the image was designed for. (And after reading ianmacd's posts, topjohnwu supposedly doesn't like pre-patched images with Magisk being shared. I'll respect that, and so should you.)
I won't take any responsibility if this damages your phone. Perform the following at your own risk. If you agree, then:
If you haven't already, root the phone with Magisk. Make sure to keep a copy of the magisk_patched.tar somewhere on your computer so you can reflash it with ODIN if something goes wrong here. Always make sure Magisk is installed before modifying the recovery partition yourself. If you have a pending software update, install that with Odin and root that first before doing the following.
Set up ADB on your phone and computer
From your computer, adb shell into the phone
Run
Code:
uname -r
Only attempt to apply these patches if you get 4.14.78-16509050 back. For an older version, the bottom of this post has previous patches that may or may not apply. Or just update your phone.
Run
Code:
su
and then
Code:
rm -rf /data/local/tmp/q12kpwrk ; mkdir /data/local/tmp/q12kpwrk && cd /data/local/tmp/q12kpwrk
Run
Code:
mkdir recovery && cd recovery
Find the recovery partition on your phone by running:
Code:
recovery_blk="`readlink -f /dev/block/by-name/recovery`" ; [ -b "$recovery_blk" ] || echo "Eh, something's off here. Don't continue"
Dump it to a file by running:
Code:
dd if="$recovery_blk" of=recovery.img
Extract the kernel by running:
Code:
/data/adb/magisk/magiskboot unpack recovery.img || echo "Stop! Do not continue!"
If you see the warning message again on a new line, then stop.
Otherwise, if all went well with the step above (the message "Kernel is uncompressed or not a supported compressed type!" can be safely disregarded), then note that for any of these patches, if you don't get any matches or get more than one, then do not continue any further. Don't selectively apply any of these patches; it's all or nothing.
Apply the first patch by running:
Code:
/data/adb/magisk/magiskboot hexpatch kernel F7030032895240F9F64F00F9 F7030032FD10F997F64F00F9
Run
Code:
/data/adb/magisk/magiskboot hexpatch kernel 02000014C02E00F9E1630191 02000014ED10F997E1630191
If you have an SM-G9750/Snapdragon S10+: run
Code:
/data/adb/magisk/magiskboot hexpatch kernel F30300AAA1010035F40313AA750640F9890E41F83F7500F103010054AA02098BC10501B0407100D121B83191 F30300AA0D000014895240F9DF420239C0035FD600000000D22E40F94E02008BCE2E00F9C0035FD621B83191
OR if you have an SM-G9730/Snapdragon S10: there is currently no patch. Feel free to send me a recovery.img from the latest firmware and I'll adapt it
OR if you have an SM-G9700/Snapdragon S10e (thanks to Laikar_ for the recovery.img and testing): run
Code:
/data/adb/magisk/magiskboot hexpatch kernel F30300AAA1010035F40313AA750640F9890E41F83F7500F103010054AA02098BA10501D0407100D121B81D91 F30300AA0D000014895240F9DF420239C0035FD600000000D22E40F94E02008BCE2E00F9C0035FD621B81D91
Have the patched kernel placed into a new recovery image, new-boot.img, by running:
Code:
/data/adb/magisk/magiskboot repack recovery.img || echo "Stop! Do not continue!"
Check to see if new-boot.img isn't somehow larger than the recovery partition itself by running
Code:
[ `stat -c '%s' "new-boot.img"` -gt `blockdev --getsize64 "$recovery_blk"` ] && echo "Do not continue!"
Flash the new recovery image by running
Code:
cat new-boot.img /dev/zero >"$recovery_blk" 2>/dev/null
Run
Code:
sync ; sync ; sync ; reboot recovery
If the phone boots again, great! If you're stuck at the Samsung-only logo that fades in and out for many minutes, just restart the phone again whilst holding the recovery button combo to boot into Android with Magisk activated like normal.
You can rm -rf the /data/local/tmp/q12kpwrk folder afterwards to get some space back.
If your phone keeps restarting, or you automatically get put into semi-bootloader flashing mode, hold the bootloader button combo to get to the blue-background downloading mode and reflash magisk_patched.tar (and HOME_CSC) with Odin. If you didn't keep said file or a Magisk-patched recovery.img you can tar up with 7-Zip and get Odin to flash as AP, you'll need to download the latest firmware for your SM-G9750 with Frija or similar, reflash that and then follow the instructions to root your phone again with Magisk.
If you do get a reboot after applying this, looking at /proc/last_kmsg will indicate if it's something to do with this patch or something else entirely.
Q&A:
Q: Will I have to reapply this if I update Magisk from Magisk Manager with a direct install?
A: No.
Q: Will I have to reapply this if I update the phone's firmware?
A: Yes, but check the new kernel's version first and see if it's listed in the compatibility section. If not, then you'll need to wait for an update to this fix. And remember to make sure that Magisk is installed first before modifying the recovery partition yourself.
Q: I don't want to wait hours to see if my phone will restart out of the blue. How can I test for this bug?
A: A variation on the steps to reproduce here, you can do this:
Code:
su
dd if=/data/media/0/AP_G9750ZHU1ASF1_CL16082828_QB24224470_REV00_user_low_ship_MULTI_CERT_meta_OS9.tar.md5 of=/dev/shm # or any very large file (3-4 GB, /dev/urandom might work). This fills up the allocated space for shared memory
cat /proc/*/smaps_rollup
If your kernel isn't patched, restart your phone certainly does. (Of course, you should probably run reboot recovery anyway if not because a full SHM isn't really conducive to a well-running Android session.)
Q: Do you have any other kernel patches?
A: Just the one, only tested on the SM-G9750, and it seems to not be needed at all - it has no bearing on this specific reboot issue anyway. This one disables one aspect of RKP. Again, I don't think this is actually needed on the S10+ , but Magisk still attempts to patch for this issue indiscriminately (probably for the benefit of older devices), although its patch will not apply to our kernel.
Code:
/data/adb/magisk/magiskboot hexpatch kernel 1FA50F7143010054491540B93FA50F71E30000544B0940B97FA50F71830000544A1940B95FA10F7168090054 1FA10F71810A0054491540B93FA10F71200A00544B0940B97FA10F71C00900544A1940B95FA10F7161090054
Q: Are you a dirty GPL violator, qwerty12?
A: No! What I am providing is the compiled form of the patch linked to in the beginning of this thread. If you want to understand what this does in lovely C, just look at that patch. Of course, I have to deal with this on the assembler level, so there is no source per se, just dump all the hex strings into an online disassembler. The first two magiskboot hexpatch invocations replace two existing instructions with jumps into the new code I add. The third hexpatch invocation adds the additional code implementing the patch - the original replaced instruction is executed, along with the code I added to set mss->check_shmem_swap to zero before vma->vm_file is checked for != NULL and for shmem_swapped to be added to mss->swap instead of replacing it.
Patches for older kernels:
4.14.78-16082828:
Use Magisk Manager to install the Busybox Magisk module. No, this is not optional. You can use a version of Busybox from another source, but note that this is the version I have personally tested all this with. Restart your phone anyway if you already have it installed; you want your phone's running state to be as fresh as possible to avoid the possibility of running into this bug while attempting to fix it.
Code:
/data/adb/magisk/magiskboot hexpatch kernel F7030032895240F9F64F00F9 F70300327ED15494F64F00F9
Code:
/data/adb/magisk/magiskboot hexpatch kernel 02000014C02E00F9E1630191 020000146ED15494E1630191
Code:
printf '\x89\x52\x40\xF9\xDF\x42\x02\x39\xC0\x03\x5F\xD6\x00\x00\x00\x00\xD2\x2E\x40\xF9\x4E\x02\x00\x8B\xCE\x2E\x00\xF9\xC0\x03\x5F\xD6' | busybox dd of=kernel bs=1 seek="$((0x017F9AAC + 20))" conv=notrunc
The magiskboot hexpatch equivalent of this was too large, so I settled for writing to a hard coded offset.
I have random reboot... will try this patch tomorrow.
Sent from my SM-G9750 using Tapatalk
Hi... already doing your patches... i thinks succesfully, because i dont have any error, and boot normally after last command.
So.... i have to wait if random reboot appear right ? *to test*
Thank you... will report in about 3 days
Hi,
Vuska said:
So.... i have to wait if random reboot appear right ? *to test*
Click to expand...
Click to collapse
You can run the commands under "Q: I don't want to wait hours to see if my phone will restart out of the blue. How can I test for this bug?" in the first post. If your phone restarts automatically when running cat, then your phone is still susceptible to restarting itself during use.
If it doesn't restart, then you need to run reboot recovery yourself immediately, but it means the fix was successfully applied.
PS D:\S10+\ADB platform-tools> ./adb devices
List of devices attached
R28M31K3DNZ device
PS D:\S10+\ADB platform-tools> ./adb shell
beyond2q:/ $ su
Permission denied
1|beyond2q:/ $
?????
N1ldo said:
PS D:\S10+\ADB platform-tools> ./adb devices
List of devices attached
R28M31K3DNZ device
PS D:\S10+\ADB platform-tools> ./adb shell
beyond2q:/ $ su
Permission denied
1|beyond2q:/ $
?????
Click to expand...
Click to collapse
do you already install busybox via magisk ? also there will be a pop up in your device to request access from computer. accept it
already enable usb debugging in developer menu ?
permission denied .... [emoji848] .. strange... already rooted right ?
Sent from my SM-G9750 using Tapatalk
Vuska said:
do you already install busybox via magisk ? also there will be a pop up in your device to request access from computer. accept it
already enable usb debugging in developer menu ?
permission denied .... [emoji848] .. strange... already rooted right ?
Sent from my SM-G9750 using Tapatalk
Click to expand...
Click to collapse
Yes.
As you can see in the prints below.
i try install another busybox to.
N1ldo said:
beyond2q:/ $ su
Permission denied
1|beyond2q:/ $
?????
Click to expand...
Click to collapse
Check your Magisk settings to see if you haven't turned off ADB superuser access and your apps list for a denied Shell entry.
qwerty12 said:
Check your Magisk settings to see if you haven't turned off ADB superuser access and your apps list for a denied Shell entry.
Click to expand...
Click to collapse
Thank you all ...:good::good:
Yes Shell was unauthorized root on Magisk application list :victory:
3 days now.... i can say it successfully fixed.... [emoji106][emoji106]
Thank you.
hope you will update too when new firmware arrives....
because i dont understand some code mean.... just follow and copy paste
Sent from my SM-G9750 using Tapatalk
*ASG7 firmware is out
I can provide a recovery.img from s10e (smg9700), also any way i can contact you for some help about building the kernel? I have been trying to do with s10e's one and i'm not having much success
FlatOutRU said:
*ASG7 firmware is out
Click to expand...
Click to collapse
Downloading...
is ASG7 can use this patches ?
Sent from my SM-G9750 using Tapatalk
FlatOutRU said:
*ASG7 firmware is out
Click to expand...
Click to collapse
Vuska said:
s ASG7 can use this patches ?
Click to expand...
Click to collapse
I'll download the update later and give it a once-over; however, I'll quote myself:
qwerty12 said:
As long as the kernel version remains the same, it's likely, but not guaranteed, the same patches will work for future software updates from Samsung and all I'll have to do is update the compatibility list.
Click to expand...
Click to collapse
Laikar_ said:
I can provide a recovery.img from s10e (smg9700), also any way i can contact you for some help about building the kernel? I have been trying to do with s10e's one and i'm not having much success
Click to expand...
Click to collapse
That would be appreciated, thanks. I can move the S10e into the "Patch not tested" section of the compatibility list.
I wish you'd have asked me this a few days ago, I deleted the kernel tree I had on my disk because I thought a new source ZIP from Samsung would be forthcoming for the new firmware. I'd've just attached a diff...
I did get the kernel to build but I could not get the result to boot. Some of the compiler warnings displayed during build didn't make it seem like I was going to get a working kernel image. I'll get back to you soon with some steps
qwerty12 said:
That would be appreciated, thanks. I can move the S10e into the "Patch not tested" section of the compatibility list.
I wish you'd have asked me this a few days ago, I deleted the kernel tree I had on my disk because I thought a new source ZIP from Samsung would be forthcoming for the new firmware. I'd've just attached a diff...
I did get the kernel to build but I could not get the result to boot. Some of the compiler warnings displayed during build didn't make it seem like I was going to get a working kernel image. I'll get back to you soon with some steps
Click to expand...
Click to collapse
I can't post links yet, tinyurl(dot)com/y537462u for the drive download link
Does EdXposed work for G9750?
qwerty12 said:
I'll download the update later and give it a once-over; however, I'll quote myself:
Click to expand...
Click to collapse
Its changed a bit
kakahoho said:
Does EdXposed work for G9750?
Click to expand...
Click to collapse
Yes.
FlatOutRU said:
Its changed a bit
Click to expand...
Click to collapse
Good call; there's now code at 0x017F9AAC + 20, probably not a good idea to overwrite that...
I was hoping the newer build date might have meant that Samsung applied the patch, meaning I could abandon this thread, but no such luck: I did the quick writing to /dev/shm test and my phone kernel panicked. Lovely.
I've updated the first thread with an updated patch. I followed through with my plan of moving my extra code into load_module() instead of the empty section of zeros as, thanks to Samsung's kernel developers' ineptness, that function will always fail - may as well make it early return and then use the extra space gained to store my code in.
Laikar_ said:
I can't post links yet, tinyurl(dot)com/y537462u for the drive download link
Click to expand...
Click to collapse
Thanks for the S10e recovery image, Laikar_. I've checked the recovery image's kernel and moved the S10e into the "Patch not tested" section. I'll write up some steps soon on building a kernel that won't boot
Anyway,
The S10 and S10e recovery images are not from ASG7, however, so I don't know if my newer patch applies to it but my old ones do. I think my newer one will do, too, but that's an educated guess.
Just like with the S10, anybody's welcome to try this on their S10e and let me know of the result.
qwerty12 said:
Yes.
Good call; there's now code at 0x017F9AAC + 20, probably not a good idea to overwrite that...
I was hoping the newer build date might have meant that Samsung applied the patch, meaning I could abandon this thread, but no such luck: I did the quick writing to /dev/shm test and my phone kernel panicked. Lovely.
I've updated the first thread with an updated patch. I followed through with my plan of moving my extra code into load_module() instead of the empty section of zeros as, thanks to Samsung's brainiac developers, that function will always fail - may as well make it early return and then use the extra space gained to store my code in.
Thanks for the S10e recovery image, Laikar_. I've checked the recovery image's kernel and moved the S10e into the "Patch not tested" section. I'll write up some steps soon on building a kernel that won't boot
Anyway,
The S10 and S10e recovery images are not from ASG7, however, so I don't know if my newer patch applies to it but my old ones do. I think my newer one will do, too, but that's an educated guess.
Just like with the S10, anybody's welcome to try this on their S10e and let me know of the result.
Click to expand...
Click to collapse
so the first post already update to 050 kernel right ?
mean after i updated my s10+ magisk etc.. i can do that all steps right ?
cool...
still not yet finished my download since yesterday... my internet down.. [emoji2357]
Sent from my SM-G9750 using Tapatalk
Vuska said:
so the first post already update to 050 kernel right ?
mean after i updated my s10+ magisk etc.. i can do that all steps right ?
Click to expand...
Click to collapse
Yep, the first post is updated for ASG7. Those steps are working on my SM-G9750 running it, anyway
Laikar_ said:
[...]any way i can contact you for some help about building the kernel? I have been trying to do with s10e's one and i'm not having much success
Click to expand...
Click to collapse
I'll mention again that I couldn't get the result to boot. If you work it out, please let me know. I hate loading kernel images into a disassembler
I did this on a Ubuntu 18.04.2 minimal installation. I figure that if you want to build a kernel then you, like me, have at least a working familiarity with GNU/Linux, so I won't go too in-depth.
First, install the packages needed to build:
Code:
sudo apt install git-core gnupg flex bison gperf build-essential zip zlib1g-dev libxml2-utils xsltproc unzip python bc libssl-dev
Download the toolchain mentioned in README_kernel.txt:
Code:
git clone --depth=1 https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9
Download Snapdragon LLVM Compiler for Android v6.0.9 - Linux64 from https://developer.qualcomm.com/software/snapdragon-llvm-compiler-android/tools and untar it somewhere on your system. (This isn't actually the exact compiler Samsung use - if you look at /proc/version on your phone, you'll see it says 6.0.10 - but this is the closest we mere mortals will get.)
Download the source code zip from Samsung and untar Kernel.tar.gz into a newly-created folder. Inside said folder, run chmod 644 Makefile ; chmod 755 build_kernel.sh.
Open build_kernel.sh in your favourite editor. Make the following changes:
Set BUILD_CROSS_COMPILE to the folder where aarch64-linux-android-gcc, aarch64-linux-android-ld etc. are after cloning from git. Make sure to leave the aarch64-linux-android- suffix at the end. For me, this line looks like this:
Code:
BUILD_CROSS_COMPILE=/home/fp/x/aarch64-linux-android-4.9/bin/aarch64-linux-android-
KERNEL_LLVM_BIN needs to be set to the location of the Clang binary downloaded from Qualcomm. For me, this line looks like this:
Code:
KERNEL_LLVM_BIN=/home/fp/x/93270/toolchains/llvm-Snapdragon_LLVM_for_Android_6.0/prebuilt/linux-x86_64/bin/clang
After both REAL_CC=$KERNEL_LLVM_BIN instances add
Code:
CFP_CC=$KERNEL_LLVM_BIN
(although I think this is the wrong way to do it, consider just disabling CONFIG_RKP_CFP)
Open the Makefile in your favourite editor. Find the following line
Code:
@echo Cannot use CONFIG_CC_STACKPROTECTOR_$(stackp-name): \
$(stackp-flag) not supported by compiler >&2 && exit 1
Remove the "&& exit 1". The proper way to fix this would be to set CONFIG_CC_STACKPROTECTOR_STRONG to n in the config file; however if you run clang --help, you'll see that -fstack-protector-strong is actually supported. Why turn off a useful security feature?
Run build_kernel.sh and the kernel should build (albeit with a metric crap-ton of warnings, which is just one reason why it's not surprising the resulting kernel won't boot)

Sebanc's Brunch Project

This is what I do, and it has been working awesome. I have done it several times experimenting.
Starting with a dual boot Windows and Linux Mint setup, each in their own partition, plus another partition which I refer to as "storage" (sda4).
From Linux Mint I have download Sebanc's Brunch package and Rammus Recovery image. I extract them both, and place the recovery image inside of the extracted Brunch folder.
I install the pv, tar and cgpt packages/binaries if they are not installed already:
Code:
sudo apt install pv:
sudo apt install cgpt;
sudo apt install tar;
I then run the following from inside the extracted Brunch directory (making my img file 20 gb):
Code:
mkdir -p ~/tmpmount;
sudo mount /dev/sda4 ~/tmpmount/;
sudo bash chromeos-install.sh -src chromeos*.bin -dst ~/tmpmount/chromeos.img -s 20;
sudo umount ~/tmpmount;
{
"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"
}
Still in Linux Mint, I will then add the menu item for launching the image from the Linux Mint grub2 menu.
There are different ways to do this, but I use grub-customizer:
Code:
sudo add-apt-repository ppa:danielrichter2007/grub-customizer;
sudo apt update;
sudo apt install grub-customizer;
I add a new menu item, selecting "other" as the type, pasting from what is displayed at the end of the chromeos.img creation):
Code:
img_part=/dev/sda4
img_path=/ChromeOS/chromeos.img
search --no-floppy --set=root --file $img_path
loopback loop $img_path
linux (loop,gpt7)/kernel boot=local noresume noswap quiet splash loglevel=7 disablevmx=off \
cros_secure cros_debug loop.max_part=16 img_part=$img_part img_path=$img_path
initrd (loop,gpt7)/initramfs.img
I then reboot, and I will see the Chrome OS option in the grub2 boot menu.
I hope this is helpful to someone.
From Project Croissant thread
https://forum.xda-developers.com/ha...ide-installing-official-chrome-os-pc-t3865697
I thougth this project might be better discussed in it's own thread...
corvek97 said:
Spent some days reading through this thread and trying everything I could find to get mine to install properly but it all ended in the same "Missing OS" error or something else.
Thankfully it all did lead me discover Sebanc's Brunch Framework which worked perfectly for me... aside from having some issues with the installation as some of the documentation wasn't as newbie-friendly regarding some stuff and their Telegram group is private but that aside, as a complete noob I imanaged to get it running in hours and every function related to the OS itself is working perfectly on my dual-boot PC and laptop.
Just sharing in case anyone else is going through the same thing here.
Click to expand...
Click to collapse
djuroganovic said:
+1 - I also have much better success with sebanc brunch on github than with chromefy script. Everything works great on r80, only downside is that it only works with UEFI bios, no legacy bios support.
Click to expand...
Click to collapse
ralphwiggum1 said:
Thanks for the information. The sebanc brunch tool worked great. It seems to have taken the best of various methods, but made it simpler without having the manage various partitions. Even better news is that I had issues with my Dell Venue 11 Pro not working with any method for a while. Arnold after R56 or something stopped showing video and other issues with all other builds, including Fyde, that I tried . Using brunch with just the recommended recovery (rammus), which is a more generic build, everything works. The grub/boot it comes with also seems to be a bit more generic and better than I had with Arnold.
Instructions and downloads are here: www.github.com/sebanc/brunch
Some clarification, particularly for dual-boot, is that it brunch documentation doesn't seem to mention that everything, once installed, resides inside of an image file (.img) on one partition (ntfs or ext4) on your drive. It also doesn't tell you to copy the boot files anywhere, but rather to boot from a USB/SD then it will boot up the img. I got around this by loading the boot files onto my main boot partition where I'm triple booting Windows 10, Ubuntu (I used ubuntu to do this), and Chrome OS. I don't think that matters too much since I'm using rEFInd (www.rodsbooks.com/refind/) as the main bootloader and I think it has modules to chainload from any partition, not just FAT like most BIOS need (I could be wrong, since all mines on the the main FAT boot partition). I'm using the minimal theme on the refind site with some custom icons. I modify these files in Ubuntu with a sudo bash shell.
Another note is you may be able to secure boot with brunch since they include a certificate you could theoretically load to your system's key for secure boot.
Click to expand...
Click to collapse
@ralphwiggum1: Can you share how you got reFind to work? I have updated manual.conf with the following, but it gives me an error:
Starting (null)
Using load options 'initrd=(loop'
Error: Not Found uhile loading (null)
* Hit any key to continue *
Here is what I have in my refind manual.conf file - which matches what I have in my Linux Mint grub2 (which boots up great):
Code:
menuentry "ChromeOS (boot from disk image)" {
img_part=/dev/sda4
img_path=/ChromeOS/chromeos.img
search --no-floppy --set=root --file $img_path
loopback loop $img_path
linux (loop,gpt7)/kernel boot=local noresume noswap loglevel=7 disablevmx=off \
cros_secure options=enable_updates cros_debug loop.max_part=16 img_part=$img_part img_path=$img_path
initrd (loop,gpt7)/initramfs.img
}
Any idea what I could be doing wrong?
TheMCNerd2021 said:
Tried using the script after I discovered it a few days ago, and it worked perfectly inside of an Ubuntu VM I created. Overall, everything built successfully when using the Croissant script to create a Chrome OS image (I used ATB R80 Special chromium image, Eve R80 recovery image, and swtpm.tar) and I was able to write it to an old USB drive and boot off of it on my old laptop. Most things worked fine except for the Play Store, which would give the generic "Something went wrong" error. I tried again, this time not enforcing SELinux when asked by the script, and the same exact error came up when using the new image. The chrome://flags page was also completely empty.
I eventually tried using Sebanc's Brunch Framework since other people on here have used it, and the resulting image file that I wrote to the USB drive worked great with my old laptop. Every function including the Play Store was working, albeit sluggish due to the flash drive I was using being slow.
Not sure why the Play Store wouldn't work when I used the image created with the Croissant script, yet worked when I used the image created with the Sebanc's Brunch Framework. I guess it's because my laptop (Acer Aspire E5-571-563B) is simply too old for the Eve recovery image. Either way, big thanks to the developers of both the projects for allowing us to run official Chrome OS on normal laptops.
Click to expand...
Click to collapse
ralphwiggum1: I get the error above when adding a different OS - so I must be using the manual.conf wrong. Is there anything special you did to get reFind to recognize this loopback device as a boot option? Thanks!
jhedfors said:
@ralphwiggum1: I get the error above when adding a different OS - so I must be using the manual.conf wrong. Is there anything special you did to get reFind to recognize this loopback device as a boot option? Thanks!
Click to expand...
Click to collapse
I'm using Refind, but using it to load Grub. Refind may not have all the capabilities of Grub to be able to boot Chrome OS, at least I don't think it can.
With sebanc/brunch, I was actually wrong before, they do say to copy the grub info to your existing grub config. I had missed that part.
Copy the GRUB configuration which appears in the terminal at the end of the process (between lines with stars) to either:
your hard disk GRUB install if you have one (refer to you distro's online resources).
the USB flash drive / SD card GRUB config file (then boot from USB flash drive / SD card and choose "boot from disk image" in the GRUB menu),
Click to expand...
Click to collapse
So if you're already using grub, you could add your Chrome OS menuentry to it, but it may not be possible to make it a separate item in your refind boot screen. In that case, just copy the sebanc/brunch boot files to another folder on your system's efi boot partition and make a folder called 'cros' or something. It's just the grub loader and the grub.conf. Then just make an option in refind to load that grub file. You can maybe play with that grub's config file to not show the grub menu and autoload the first menuentry.
Hope this helps.
ralphwiggum1 said:
I'm using Refind, but using it to load Grub. Refind may not have all the capabilities of Grub to be able to boot Chrome OS, at least I don't think it can.
With sebanc/brunch, I was actually wrong before, they do say to copy the grub info to your existing grub config. I had missed that part.
So if you're already using grub, you could add your Chrome OS menuentry to it, but it may not be possible to make it a separate item in your refind boot screen. In that case, just copy the sebanc/brunch boot files to another folder on your system's efi boot partition and make a folder called 'cros' or something. It's just the grub loader and the grub.conf. Then just make an option in refind to load that grub file. You can maybe play with that grub's config file to not show the grub menu and autoload the first menuentry.
Hope this helps.
Click to expand...
Click to collapse
Thank you for the suggestion - I will probably give it a try. Right now I have successfully added it to the Linux Mint grub menu. But I can't resist tinkering.
jhedfors said:
Where are you trying to install it? It looks like you are missing arguments that are required with the installation, for example:
https://github.com/sebanc/brunch/blob/master/README.md
Click to expand...
Click to collapse
Shawnashley said:
The hard drive of a windows laptop. Linux cmds aren't my strong suit. Sorry for the inconvenience.
Click to expand...
Click to collapse
We should probably have this discussion in this thread, as it is not about Project Croissant...
So are you following the dual boot instructions to create the ChromeOS IMG file? Make sure you follow all the steps.
jhedfors said:
We should probably have this discussion in this thread, as it is not about Project Croissant...
So are you following the dual boot instructions to create the ChromeOS IMG file? Make sure you follow all the steps.
Click to expand...
Click to collapse
Sorry about that. I followed the YouTube video on the link in the Croissant thread to create the USB Linux with the Chrome OS folder inside. But when I try to install it presents me with the errors in the screenshots. I've tried installing to the HDD and it always give the same errors. I'm not real versed in Linux and maybe that is my issue.
Forgot the screenshot.
Shawnashley said:
Sorry about that. I followed the YouTube video on the link in the Croissant thread to create the USB Linux with the Chrome OS folder inside. But when I try to install it presents me with the errors in the screenshots. I've tried installing to the HDD and it always give the same errors. I'm not real versed in Linux and maybe that is my issue.
Click to expand...
Click to collapse
You are making an incomplete entry, as I said previously.
https://github.com/sebanc/brunch
Look at the "Dual Boot ChromeOS from your HDD" section.
You should also be checking out the support links that are linked to on the YouTube post. ?
jhedfors said:
You are making an incomplete entry, as I said previously.
https://github.com/sebanc/brunch
Look at the "Dual Boot ChromeOS from your HDD" section.
You should also be checking out the support links that are linked to on the YouTube post. ?
Click to expand...
Click to collapse
Thanks, I've followed those already. The incomplete entry is the exact same way it is done in the YouTube video. I'll work it out. Thanks though.
I keep getting an error stating that the gpt partition is messed up. Wether writing to a .IMG file or a USB device.
keweminer said:
I keep getting an error stating that the gpt partition is messed up. Wether writing to a .IMG file or a USB device.
Click to expand...
Click to collapse
Mine errors and says path to Cheomeos can't be found. Strange since it's in the file I'm running in a terminal. It's quite screwy, Fyde OS is looking like the greener grass from over here. :laugh:
jhedfors said:
You are making an incomplete entry, as I said previously.
https://github.com/sebanc/brunch
Look at the "Dual Boot ChromeOS from your HDD" section.
You should also be checking out the support links that are linked to on the YouTube post. ?
Click to expand...
Click to collapse
When I create the Chrome OS image in cmd line it doesn't give me a recovery image and I cannot trace the path to a location. It stores as individual files. How do I load that as an installable image on a USB? Thanks.
Shawnashley said:
When I create the Chrome OS image in cmd line it doesn't give me a recovery image and I cannot trace the path to a location. It stores as individual files. How do I load that as an installable image on a USB? Thanks.
Click to expand...
Click to collapse
I've had great luck with Project Croissant and maknig bootable usb drives, I just haven't found any recoveries other than lulu 80 that are stable enough to use, however, it lacks the linux container. I'm currently running Eve76, with the linux container upgraded to Buster, with backports and flatpaks. That's working really well for me... but, its not 80 :laugh:
I'm determined to figure this out though, because I'm home and bored out of my skull.
---------- Post added at 06:39 AM ---------- Previous post was at 06:31 AM ----------
Shawnashley said:
When I create the Chrome OS image in cmd line it doesn't give me a recovery image and I cannot trace the path to a location. It stores as individual files. How do I load that as an installable image on a USB? Thanks.
Click to expand...
Click to collapse
I found my image file in the scripts folder.
Edit: I got it! Went with mint on USB method. Works amazingly!!!
keweminer said:
I've had great luck with Project Croissant and maknig bootable usb drives, I just haven't found any recoveries other than lulu 80 that are stable enough to use, however, it lacks the linux container. I'm currently running Eve76, with the linux container upgraded to Buster, with backports and flatpaks. That's working really well for me... but, its not 80 :laugh:
I'm determined to figure this out though, because I'm home and bored out of my skull.
---------- Post added at 06:39 AM ---------- Previous post was at 06:31 AM ----------
I found my image file in the scripts folder.
Edit: I got it! Went with mint on USB method. Works amazingly!!!
Click to expand...
Click to collapse
Thanks for the info. I'll check there. I used the Linux mint method and created the folder and the IMG file but I could ever get it to install to disk. I tried various methods from the brunch page and no luck. Thanks though.
Here's what i did to get Brunch to work for me.
I used R80 k4.19 testing v3 from this page: https://sites.google.com/view/brunch-project/downloads
and the Rammus 80 recovery.
Using two USB thumbdrives, I booted Linux Mint from one, running apt to install pv and cgpt.
On usb drive 2 I had my unpacked brunch and the chromeos recovery.
I then followed the instructions for installing it to /dev/sdX to install it directly to my harddrive, found here: https://sites.google.com/view/brunch-project/wiki/how-to-install-chrome-os-on-your-laptop
I shutdown the computer, rebooted and let it do its thing. 10 Minutes later, I'm running ChromeOS 80. This seems rock solid so far. Playstore started no problem, updated and installed the various apps that I had been running on Eve 76. Linux installed and I updated Buster, added backports. Installed flatpak and am so far very happy.
keweminer said:
Here's what i did to get Brunch to work for me.
I used R80 k4.19 testing v3 from this page: https://sites.google.com/view/brunch-project/downloads
and the Rammus 80 recovery.
Using two USB thumbdrives, I booted Linux Mint from one, running apt to install pv and cgpt.
On usb drive 2 I had my unpacked brunch and the chromeos recovery.
I then followed the instructions for installing it to /dev/sdX to install it directly to my harddrive, found here: https://sites.google.com/view/brunch-project/wiki/how-to-install-chrome-os-on-your-laptop
I shutdown the computer, rebooted and let it do its thing. 10 Minutes later, I'm running ChromeOS 80. This seems rock solid so far. Playstore started no problem, updated and installed the various apps that I had been running on Eve 76. Linux installed and I updated Buster, added backports. Installed flatpak and am so far very happy.
Click to expand...
Click to collapse
That's cool. I had Fyde working pretty well, but battery life was awful and there were some glitches and flickering. I tried using Ubuntu in Windows to create a Cheomeos img but it tells me recovery image can't be found and all I have is a folder of files. Gonna go back to Fyde while I try to figure it out. Thanks for the input it's much appreciated.
I have updated the OP with my steps -
I hope this is helpful to someone.
Tag: @Shawnashley
jhedfors said:
This is what I do, and it has been working awesome. I have done it several times experimenting.
Starting with a dual boot Windows and Linux Mint setup, each in their own partition, plus another partition which I refer to as "storage" (sda4).
From Linux Mint I have download the Brunch package and Rammus Recovery image. I extract them both, and place the recovery image inside of the extracted Brunch folder.
I install the pv, tar and cgpt packages/binaries if they are not installed already:
I then run the following (making my img file 20 gb):
Still in Linux Mint, I will then add the menu item for launching the image from the Linux Mint grub2 menu.
There are different ways to do this, but I use grub-customizer:
I add a new menu item, selecting "other" as the type, pasting from what is displayed at the end of the chromeos.img creation):
I then reboot, and I will see this option in the grub2 boot menu.
I hope this is helpful to someone.
Tag: @Shawnashley
Click to expand...
Click to collapse
All that for me?:laugh: Well I am going to give this a shot and report back. Many apologies for my seeming ineptitude.
Shawnashley said:
All that for me?:laugh: Well I am going to give this a shot and report back. Many apologies for my seeming ineptitude.
Click to expand...
Click to collapse
Haha... I had been meaning to do this since I started this thread... Just had been too busy. :laugh:
jhedfors said:
Haha... I had been meaning to do this since I started this thread... Just had been too busy. :laugh:
Click to expand...
Click to collapse
Do you edit the recovery name or copy as is? Just double checking. Thanks for the help by the way.

Categories

Resources