Related
Just made an update.zip for sc2k's itsmagic...
its just an caller if you forgotten to include it in your update.zip or something else was going wrong
You can find HERE on github
there you can find other stuff related...
So the zip contains the itsmagic script, and when you apply the zip it applies no changes but executes the script? Great work.
Thanks. Btw, I have also made a signed zip, that contain the original kernel only.
(for someone playing with kernel and cannot boot. Of coz, itmagic is called after restore)
http://www.mediafire.com/?cmoc97rf6qldp80
EDIT:
sorry dudes, last update was a big fail... it seems we must mount /system and /data before apply, i will fix it
I have been a fan of DJ Steve's ROMs and his dev skills. But right now I am running a deodexed 351 that is otherwise stock, in portrait mode. haha
I love his ability to compile ROMs and Kernels and such, but I really want just the kernel that supports overclocking.
I can get any of the kernels to work from 1.91
no vol, no ppt
no vol, ppt
vol and ppt
vol and no ppt
I even add the proper dhd.ko file for the modules folder and correct the permissions and even the reset.ko file too.
But no matter what I do, I can't get the kernel to work AND wifi to work. It seems like either or for a stock rom. Either you have a plain kernel with no overclocking, or you can use the kernel with no wifi working.
Does anyone know of:
1: If there are other files I should be bringing over from the rom to make the kernel and wifi work together
or
2: What specifically I can edit to allow the stock kernel to allow overclocking?
Sorry for the long post.
Thanks for the help in advance.
OK. I guess no one out there knows either.
What I have been doing so far to achieve overclocking is create a .txt file (according to the instructions on setcpu.com) and put that at the root of my sdcard and have setcpu do the rest.
I would prefer to use the kernel method so I can add the volboost and/or ppt tweaks in 1.91.
I will wait patiently for your guidence.
Maybe try this
http://forum.xda-developers.com/showpost.php?p=14679059&postcount=135
Ok I figured out which one will work.
http://forum.xda-developers.com/showthread.php?t=1113256
Ok go to Simple Streak's thread.
1. Download the .zip for version 1.2
2. copy the files in /system/lib/modules to your /system/lib/modules
3. fix permissions, they should be 644, which are rw-r--r--
4. boot into fastboot, and flash his boot.img
Thank you Spidla for a kernel I can use that supports overclocking, that I dont have to use the entire ROM and most importantly, my wifi works.
rsalib said:
Ok I figured out which one will work.
http://forum.xda-developers.com/showthread.php?t=1113256
Ok go to Simple Streak's thread.
1. Download the .zip for version 1.2
2. copy the files in /system/lib/modules to your /system/lib/modules
3. fix permissions, they should be 644, which are rw-r--r--
4. boot into fastboot, and flash his boot.img
Thank you Spidla for a kernel I can use that supports overclocking, that I dont have to use the entire ROM and most importantly, my wifi works.
Click to expand...
Click to collapse
I am interested in this, can you explan the procedure in more detail, copy files from what rom to what rom and how to fix permissions?
thanks
[Size=+2]A500 Public Recovery v0.2 based on Koush's CWM v5.5.0.4[/Size]
Here is a new Clock Work Mod for the ICS unlocked bootloaders only.
Features:
* cleanup tab option: shortcut to try to fix forcequits after updates, return to recovery and select on the main screen (Wipes Cache, dalvik, and fixes permissions)
* Standard options to backup and restore to either the SD card or internal storage
* Mount points match those of most running roms
* adb shell works as root (with or without system mounted)
* set boot mode menu to select the boot partition (hidden on know non-multiboot bootloaders)
* setbootmode and itsmagic command line tools for advanced users
* /data/linux directory is not deleted on erase userdata, nor backed up on nandroid backup (just like /data/media) to allow a space for linux files for dual boot and chroot linux installes.
While there may not be much fantastic yet about the recovery it appears funcitonal at this point. (Features such as touch ui may appear in the future)
Why is it called Public: its public in the sense that all the scripts and code required for anyone to build it have been made avalible. (note some linux knowledge may be needed to build it yourself)
[Size=+2]Installation[/Size]
There are to main ways to install
1) using fastboot or nvflash you can install the image
A500PubRecovery_v0.2.img MD5: 0e40a494cd066b1c8e1a8d01493f1452
2) using a any exiting recovery (as long as you have one of the unlocked bootloaders) you can install with an update.zip
A500PubRecovery_v0.2_update_S.zip MD5: 349d0d6284fc6d1e071827a37a8a55e5
** (FYI the fastboot command to run on your computer is 'fastboot flash recovery A500PubRecovery_v0.2.img')
[Size=+2]Developers Additional Information:[/Size]
Build instructions (including how to fetch the source code) is here:
https://github.com/ezterry/AcerRecovery/blob/recovery_manifest/README.mkdn
(Thanks yous/Credits are also included)
Kernel:
as of version 0.2 the kernel is built from source (see above for information on fetching the build tree including the linux kernel)
the kernel in v0.1 was a patched for system r/w acer ICS Stock kernel
additional information can be seen on the commit:
https://github.com/ezterry/AcerRecovery/commit/402da6f73e752e80312318e177035ee02e4fbf89
The biggest thanks is as manythings in the Android World to Koush, and the CyanogenMod team. (They did the hard part, I've just tweaked it for the A500 configuration)
[Size=+2]Version List[/Size]
v0.2:
A500PubRecovery_v0.2.img 0e40a494cd066b1c8e1a8d01493f1452
A500PubRecovery_v0.2_update_S.zip 349d0d6284fc6d1e071827a37a8a55e5
v0.1:
A500PubRecovery_v0.1.img 4414bdbdd3aa7b7d7d1166595e6ccb2a
A500PubRecovery_v0.1_update_S.zip f45e7e3b640b42a68ec9bb08bd4b88ce
for details on the source commits used in the builds please see:
https://github.com/ezterry/AcerRecovery/blob/recovery_manifest/VERSIONS.mkdn
I will put it in the guide ,so when you flash the unlocked boot loader you can chose to install this with it , the more options for the user the better.
Thanks for the hard work.
Awesome !!! im curious to look at source so thanks for this
Sent from my SCH-R760 using XDA
btw,
The a501 is a very similar device.. is some more advanced user wishes to test things out and let me know if and changes is needed or if its good as is (fastboot boot may be useful if you wish to boot it without actually saving it to the tab)
Other Acer devices probably need slight modifications, if you help I can look into adding it to the codebase/builds..but I can only test the a500 as it's the only tab I own.
Just try to make sure you have a link to the source code of any kernel..and failing that that it Lisa stock kernel from an official OTA image.
I have a A500 with the Build.Number "1.033.00_EMEA_DE".
I have Problems to get the CWM with that Tutorial:
http://www.brutzelstube.de/2012/acer-iconia-a500-mit-android-4-0-ics-rooten/
Its all running fine but when i want to boot into the CWM it seems to work but then the Android Guy with open Stomach and the Red ExclamationPoint is showing.
I wonder if i can use this Public Recovery v0.1??
Maybe someone can help me that.
Basian Mile said:
Its all running fine but when i want to boot into the CWM it seems to work but then the Android Guy with open Stomach and the Red ExclamationPoint is showing.
Click to expand...
Click to collapse
If you are running a stock ICS rom you need to make sure you don't have the recovery patch still installed, otherwise the stock recovery will be installed on reboot if any other recovery is installed.
If you have the script and patch.. this recovery as any other custom recovery will be overwritten.
Sent from my Galaxy Nexus using Tapatalk 2
The CWM (v5 from Thor2002ro) is running now. I was using the wrong CPUID. That was my falut. But now its ok.
So i can flash this new Recovery just in this right?
If you have one of the the unlocked ics bootloader you can flash this recovery.. either directly or with the update.zip from a working custom recovery.
Sent from my Galaxy Nexus using Tapatalk 2
Great Job!
If you want to build an A510 version, just change the data partition to point to /dev/block/mmcblk0p10. Everything else stays the same. If it doesn't boot, i may need to have the A510 recovery kernel.
BTW.. the recovery kernel doesn't really need to be patched for r/w, because /system never gets mounted as readonly, so it never does a remount to r/w. I've repacked recoveries with stock ICS kernels and they work fine. == Although, it doesn't hurt to patch them. ==
Euclid's Brother said:
BTW.. the recovery kernel doesn't really need to be patched for r/w, because /system never gets mounted as readonly, so it never does a remount to r/w. I've repacked recoveries with stock ICS kernels and they work fine. == Although, it doesn't hurt to patch them. ==
Click to expand...
Click to collapse
Part of it is I intend the kernel for my own ics rom. (Safer anyway in my opinion to not find any surprises as a user but not the biggest issue)
Tested it and installed fine , it's barebones recovery but I think A lot will love it , clean and simple. I used fastboot to install it .
Thanks Ez.
BTW I'm working on the next release
1) Some minor bug fixes (partitioning sdcard and full wipe are a bit strange at present.. in most cases we don't re-partition sdcards.. and wipe if you are installing a rom after will fix its self)
2) Now that acer has released their source, I've dropped the pre-built tweaked stock kernel, and added a source build, mostly still stock but I've changed to lZMA to allow some more space for the recovery ramdisk. (also system remount is allowed by default in this kernel so no postbuild acrobatics .. ie KPatch script)
3) add setbootmode/itsmagic binaries to the system. A500 (this is in github as is the kernel so building from synced source will give you a recovery with these pre-installed)
4) hopefully add an interface to call said binaries
Also I have an A510 test version I need someone (with the tab) to try.. PM me
Edit (Feature Idea):
whould anyone be interested in recovery when wiping not only skiping /data/media (internal /sdcard) but also skiping /data/linux ?
The idea is dual boot people bootling linux could use a ramdisk to run some bindmount/piviot root hackery to make /data/linux the root directory
also anyone using chroot to run a linux distro along side android could use the /data/linux directory as the chroot jail
let me know and I'll look into making APR here support such a feature
Is it posible to add app cwm for install.zip,backup,restore since rom ?
For exemple,the same app into sgs2 with siyha kernel or another kernel ??? Big thanks
Envoyé depuis mon A500 avec Tapatalk
ezterry said:
3) add setbootmode/itsmagic binaries to the system. A500 (this is in github as is the kernel so building from synced source will give you a recovery with these pre-installed)
Click to expand...
Click to collapse
Ehm, definitely don't put itsmagic next to setbootmode, it corrupts the kernel image in AKB.
ezterry said:
Edit (Feature Idea):
whould anyone be interested in recovery when wiping not only skiping /data/media (internal /sdcard) but also skiping /data/linux ?
The idea is dual boot people bootling linux could use a ramdisk to run some bindmount/piviot root hackery to make /data/linux the root directory
also anyone using chroot to run a linux distro along side android could use the /data/linux directory as the chroot jail
let me know and I'll look into making APR here support such a feature
Click to expand...
Click to collapse
Yeah I'm actually thinking to install linux to /data/linux and chroot there, too, exactly the same way.
micky387 said:
Is it posible to add app cwm for install.zip,backup,restore since rom ?
For exemple,the same app into sgs2 with siyha kernel or another kernel ??? Big thanks
Click to expand...
Click to collapse
I'm not exactly sure what you are talking about,
If you want to use this recovery with RomManager (as an unofficial 3.x+ recovery) you may. (In rom manager select flash recovery, select a500, select that you have manually installed a CWM recovery, select 3.x) To make it "official" koush needs to update his repo.. and I'm not going to poke that until I fix some minor outstanding bugs.
Actions will by default happen on the /data/media partition (as that is usually /sdcard) and no roms are yet in the system.. but I may work on fixing that after I make the next release. Currently running a backup myself.
If you want some other app to do this.. it needs to be compatible with the clockwork mod API.
Skrilax_CZ said:
Ehm, definitely don't put itsmagic next to setbootmode, it corrupts the kernel image in AKB.
Click to expand...
Click to collapse
next to as in both the "itsmagic" and "setbootmode" binaries are in /sbin? .. I hope you can live with that.
I don't intend to automatically run it *ever* in this recovery, just want it to exist for anyone cleaning the system to return to a HC bootloader.. probably won't even add it to the GUI as its not something you want to do by mistake (and really I don't want to promote anyone to do.. its just there for some advanced users doing advanced operations). Boot mode however will be in the gui.
ezterry said:
next to as in both the "itsmagic" and "setbootmode" binaries are in /sbin? .. I hope you can live with that.
I don't intend to automatically run it *ever* in this recovery, just want it to exist for anyone cleaning the system to return to a HC bootloader.. probably won't even add it to the GUI as its not something you want to do by mistake (and really I don't want to promote anyone to do.. its just there for some advanced users doing advanced operations). Boot mode however will be in the gui.
Click to expand...
Click to collapse
Very clever... i was worried myself at first when i saw you mention itsmagic... i'm so happy we have an open bootloader now with no tricks... oh, except the original hacking
Thanks so much for your work on this!
ezterry said:
I'm not exactly sure what you are talking about,
If you want to use this recovery with RomManager (as an unofficial 3.x+ recovery) you may. (In rom manager select flash recovery, select a500, select that you have manually installed a CWM recovery, select 3.x) To make it "official" koush needs to update his repo.. and I'm not going to poke that until I fix some minor outstanding bugs.
Actions will by default happen on the /data/media partition (as that is usually /sdcard) and no roms are yet in the system.. but I may work on fixing that after I make the next release. Currently running a backup myself.
If you want some other app to do this.. it needs to be compatible with the clockwork mod API.
next to as in both the "itsmagic" and "setbootmode" binaries are in /sbin? .. I hope you can live with that.
I don't intend to automatically run it *ever* in this recovery, just want it to exist for anyone cleaning the system to return to a HC bootloader.. probably won't even add it to the GUI as its not something you want to do by mistake (and really I don't want to promote anyone to do.. its just there for some advanced users doing advanced operations). Boot mode however will be in the gui.
Click to expand...
Click to collapse
OK.
I want to know if it's possible to add the same app (a part of recovery)
Thanks
ezterry said:
next to as in both the "itsmagic" and "setbootmode" binaries are in /sbin? .. I hope you can live with that.
I don't intend to automatically run it *ever* in this recovery, just want it to exist for anyone cleaning the system to return to a HC bootloader.. probably won't even add it to the GUI as its not something you want to do by mistake (and really I don't want to promote anyone to do.. its just there for some advanced users doing advanced operations). Boot mode however will be in the gui.
Click to expand...
Click to collapse
Yeah that's ok, I meant next to as in GUI, that would bring only problems.
v0.2 is out (see op)
Bugfixes:
~ wipe full data fix
~ fix on formating the external sdcard
~ cleaned up some warnings
Features:
~ added multiboot support (select boot partition)
~ added itsmagic binary (command line only)
~ switch to kernel source build rather than pre-built kernels
~ added /data/linux support (skip on wipe data, and nandroid backup)
kernel was built from:
https://github.com/ezterry/AcerTabKernel/commit/a6312764aa19ea7fe581b9931723c206a12b11ef
config file: apr_a500_defconfig
besides the configuration the kernel source is thus far unchanged from the acer a500 ICS drop
The kernel is built along with the recovery, see developer notes in OP for a link to the build instructions.
v0.2 doesn't boot for me.
Using Skrilax v6 bootloader I can't boot v0.2 while v0.1 works fine, both flashed from fastboot.
I also tried flashing v0.2 from v0.1 recovery, same results.
DISCLAIMER: I'm not a dev, nor do I play one on t.v. Use the information and links at your own risk. READ and UNDERSTAND what your doing before flashing is the best bet.
I take no responsibility or credit for the information.
This is primarily just quotes/links about JcSullins' Moboot for the Touchpad.
-------------------------------------------------------------------------------------------------------------------------------------------------
Above is my first attempt at a poll. It was added because I have seen little feedback about user experience with Moboot 0.3.8 and hope it will be helpful to JcSullins. Feel free to post your experiences here and hopefully someone can help. I will if I can, but keep my disclaimer in mind.
-------------------------------------------------------------------------------------------------------------------------------------------------
RootzWiki Version of this thread (more Polling options)
By now all Touchpad users should be using the latest JcSullins' CWM6 (12/15/12) or latest TWRP (2.3.3.0+) due to files system corruption issues. If you use Cwm6, I recommend Moboot 3.8 as well.
If I recall correctly, Nevertell's CWM/TWRP discussion thread or (AcmeInstaller 3 thread) at RootzWiki covers the possible issues with TWRP & moboot 3.8.
Twrp & Moboot 3.8 summary ...
Moboot 3.8 is still considered a "Testing" version but allows correct device S/n reporting to android OS needed for certain apps/games like Asphalt 7 etc. There are no issues reported (yet) when used with cwm6 because it has always used sdcard/clockworkmod/ for backups.
TWRP uses your device S/N (000000000 on Moboot 3.5) to create the folder where backups are stored, when you update to Moboot 3.8, TWRP will be looking at a new backup folder (ie 12345678) and won't see your previous TWRP backups. This is not an issue on all future backups (or if you started with Moboot 3.8). If needed you can use a file browser to move the old TWRP backup files to the new S/n folder and it has been reported to work.
(Note: I have not tried TWRP on the Touchpad, but I have used it on other devices).
JcSullins' Moboot 3.5 Goo.im Download (Last "Stable" version)
JcSullins' Moboot 3.8 Goo.im Download
(Testing version, may also be compatible with Moboot themes)
Moboot 3.8 has been setup to be flashed from either Acme3 or the installed recovery (ie CWM6).
Original RootzWiki Post
jcsullins; RootzWiki said:
FOR TESTING ONLY:
Moboot 0.3.8:
changes from 0.3.7:
Code:
commit fa7b8ea4d7d326df147c57e017df6deb36aabc0a
Author: James Sullins
Date: Sun Dec 23 12:36:22 2012 -0600
update version to 0.3.8
commit ca019c0bce04c9084bde497e7894289cb258edcd
Author: James Sullins
Date: Sun Dec 23 12:29:45 2012 -0600
adjust menu centering for compatibility w/ themes
use older menu placement unless 10 or more entries
to maintain compatibility with moboot themes
commit 0e5af62ea9924fd08dd6f340c5d5f72265038cba
Author: James Sullins
Date: Sun Dec 23 12:28:15 2012 -0600
do not put serialno as last cmdline arg
seems that placing serialno as last cmdline arg triggers a
parsing error on older TWRP version(s), so place it earlier
Click to expand...
Click to collapse
jcsullins; RootzWiki said:
Probably not unless you have moboot themes.
0.3.7 & 0.3.8 (both in testing) passes serial no to android, which makes some apps (like Asphalt 7) happier
Click to expand...
Click to collapse
drmarble; RootzWiki said:
Jcsullins has created a new moboot. It correctly reports a unique 32 char serial number. Previously, it reported a 40 char hex serial number which caused the wpa supplicant to fill the logcat with errors. It can be flashed using CWM (get the new one!) or TWRP.
Click to expand...
Click to collapse
Moboot Related Threads:
How to edit Moboot default boot from Android
Change boot order in moboot
Adjust MOBOOT from Android?
High End Games Compatibility Thread with Working Version #'s (ICS edition!)
# 3 for me
#4 for me.
Moboot 3.7 & 3.8 history with early TWRP Backups
trekrev; RootzWiki said:
NT -- I was surprised and dismayed as you last night when I started testing moboot_037-tenderloin.zip via TWIRP 2.3.2.3. All seemed to go well. I checked for the Serial number in Settings>About>Status and there it was. Yay! Then I went to TWIRP to make a backup for CM10 rom I was using 20121216 [I think] and discovered the version of the TWIRP had gone from 2.3.2.3 to 2.3.1.0 UGHughUGH So not knowing that Team Win had updated the uImage for TWIRP from 2.3.2.3 to 2.3.3.0 via GooManager(I did look in their update area first) I installed the uImage via GooManager Install Open Recovery Script found in the 3-dot menu. By Now I was truly frustrated but thought I would just do a backup and then restore my CM9 version and do the same. Needless to say I found no backups in the restore area while running restore through TWIRP because of the "new" folder naming convention(serial number not 000000000). So I quit for the night. Today during a slow day at work I followed Team Wins description of installing a earlier version of TWIRP uImage(specifically 2.3.2.3) which I have already on the TP in the goomanager folder. I hadn't yet realized the folder naming convention had changed. So when I discovered this I tried to manually move one of my backups from old folder to the new folder via TWIRP and it got lost in transit. Luckily I make about 3-4 backups per version so no great loss. I decided to try again but this time COPY a backup from the old 000000 folder to the new serial numbered folder and this time it worked Yay finally. I then restored my CM9 backup and proceeded to reapply new TWIRP for this, as well as new moboot, flash the latest nightly, update Apps and finally make a backup via TWRP 2.3.3.0. I will probably not copy any of my older backups to the new "serial folder" unless I need to. All is working well but this process is NOT RECOMMENDED FOR THE FAINT OF HEART. I will keep everyone posted on my experience with TWRP and moboot 0.3.7-tenderloin. Hope this story helps. My experience of TWRP is better with this new uImage. The touch sensitivity is so much better than before.
The moral of the story is that 'Nandroid backups' are ALWAYS your friends especially in 'the bleeding edge of developing software '
Click to expand...
Click to collapse
vzvxf; RootzWiki said:
I did a nandroid backup using twrp 2.3.1. Then did an ACMEuninstall. Then did an Acmeinstall3 for CM9. Booted into TWRP to do the restore for CM9 prior to rooting CM10. Only one problem ... when I select Restore, it lists no backups. They are out there as I can see them using the TWRP File Manager. Has anybody had this issue? and what did you do to correct?
Oh .. and I installed JCSullins MoBoot 3.8.
Click to expand...
Click to collapse
nuttaone;RootzWiki said:
Are your nandroid backups in twrp/backups/00000000000 ??
If so then there are two methods to resolve this... the issue your having is the new moboot sends an alphanumeric serial number to twrp/android, which twrp no longer uses the "00000000000" folder
Method 1. (Not for the faint hearted)
- Restore moboot 0.3.5
Method 2. (Recommended)
- Create a backup with whatever setup you currently have (you can discard it afterwards) and let twrp create the new folder structure twrp/backups/RBXXXXXXXX12345
- Using a file manager app move your existing twrp backups from 00000000000 to the newly created folder, reboot in recovery and should now see your nandroids in twrp....
Click to expand...
Click to collapse
HP TouchPad Index
I will add this to the Index, not sure where to put it yet
But I'm using Moboot 0.38 with TWRP 2.4.1.0
I'm TWRP 2.4.1.0 & moboot 3.5 still.
BIGSimon said:
I will add this to the Index, not sure where to put it yet
But I'm using Moboot 0.38 with TWRP 2.4.1.0
Click to expand...
Click to collapse
Thanks for the index add. You'd select Moboot 3.8 w/2.3.3.0+ (as in 2.3.3.0 & up)
nickster1 said:
I'm TWRP 2.4.1.0 & moboot 3.5 still.
Click to expand...
Click to collapse
I didn't include any other options for Moboot 3.5, because TWRP'S backup folder location won't change (no device s/n), so there won't be any issue when moving to a newer TWRP with the file system corruption fix.
Hopefully you're aware of the issue at least and are prepared to address it if u decide to update your moboot version (easy enough from what I've read).
Sent from my "Up all night, Sleep all day" EVO3D!
Yes I'm aware. As far as I can tell it benefits me not to update moboot, I don't play any games or anything. If there are other reasons please let me know.
So arrgg ... mind is going blank here.... how to update to 3.8 please??? Coming fro. 3.5. Thanks.
Sent from my ss_tenderloin using xda premium
From the op..
mpgrimm2 said:
Moboot 3.8 has been setup to be flashed from either Acme3 or the installed recovery (ie CWM6).
Original RootzWiki Post
Click to expand...
Click to collapse
slam11100 said:
So arrgg ... mind is going blank here.... how to update to 3.8 please??? Coming fro. 3.5. Thanks.
Sent from my ss_tenderloin using xda premium
Click to expand...
Click to collapse
Just flash it with your existing recovery .
BIGSimon said:
I will add this to the Index, not sure where to put it yet
But I'm using Moboot 0.38 with TWRP 2.4.1.0
Click to expand...
Click to collapse
I am also using 0.38 with TWRP 2.4.1.0,. [with Schitzoid 18/02 ROM] but seems i've an anomaly,.. Moboot now keeps selecting WebOS as default,.. even though Moboot.default file is set to CyanogenMod !!,. anyone any ideas ?,.
I'm stumped with this one
I'd guess that since you are not running CM now but Schizoid rom (i haven't tried it), the moboot file needs to match that uimage filename. This should have happened automatically when the Rom installed it (you should mention this in the rom's thread).
Use EsFileExplorer or similar and have a look at the filenames in /boot to see if u can I.D. the uimage Schizoid filename (screenshot maybe?)
Edit:
I downloaded and took a quick look at the install script for Schizoid. One of the last 5 lines of the script has ...
Code:
package_extract_file("boot.img", "/boot/uImage.CyanogenMod");
With my limited code reading skills, it looks to me like it replaces the CM image with Schizoid's and uses the same filename, so I would think having "CyanogenMod" in the moboot.default file should work. Perhaps someone else will have a better suggestion.
dougs99 said:
I am also using 0.38 with TWRP 2.4.1.0,. [with Schitzoid 18/02 ROM] but seems i've an anomaly,.. Moboot now keeps selecting WebOS as default,.. even though Moboot.default file is set to CyanogenMod !!,. anyone any ideas ?,.
I'm stumped with this one
Click to expand...
Click to collapse
I have the same problem, except I'm using CWM. Would love a solution. It did it with SickleRom too.
tbrummell said:
I have the same problem, except I'm using CWM. Would love a solution. It did it with SickleRom too.
Click to expand...
Click to collapse
OK , in webOS DL Cyboot from preware , run it , select Android as default boot ,save and close.
This worked for dougs99 when I helped him in the general section yesterday..
I hope it works for you as well.
dougs99 said:
I am also using 0.38 with TWRP 2.4.1.0,. [with Schitzoid 18/02 ROM] but seems i've an anomaly,.. Moboot now keeps selecting WebOS as default,.. even though Moboot.default file is set to CyanogenMod !!,. anyone any ideas ?,.
I'm stumped with this one
Click to expand...
Click to collapse
Jcsullins has posted a zip file on goo that should help you just flash it in recovery
http://goo.im/devs/jcsullins/cmtouchpad/misc/update-boot-cm-default.zip
Sent from my Nexus 4 using Tapatalk 2
BIGSimon said:
Jcsullins has posted a zip file on goo that should help you just flash it in recovery
http://goo.im/devs/jcsullins/cmtouchpad/misc/update-boot-cm-default.zip
Click to expand...
Click to collapse
Thanks for that link BigSimon. I had forgotten about that zip.
Looking at the zip file it extracts the moboot.default file (set for CyanogenMod) and sets the correct permissions.
For those on other roms like Schizoid and Sickle, if you still have problems (and Cyboot doesn't help either) you will likely need to contact the rom developer, especially if the problem was duplicated on moboot 3.5.
BIGSimon said:
Jcsullins has posted a zip file on goo that should help you just flash it in recovery
http://goo.im/devs/jcsullins/cmtouchpad/misc/update-boot-cm-default.zip
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Well, that got the default menu item selected, now the default timer doesn't work. LoL
tbrummell said:
Well, that got the default menu item selected, now the default timer doesn't work. LoL
Click to expand...
Click to collapse
In webOS install Cyboot from preware when you run it select Android as default then alter the time out to what ever you want save and close . You will also then be able to edit the timeout from android should you need to.
I hope this helps
Edit : Didn't realise I'd already given you this advice, might be worth trying this time.
I have been playing around with kernels (for nexus 5), to add some features to the stock kernel. But I have problem with Samsung. I am trying to build a flashable custom kernel for Samsung S7 edge (G935F). .Steps I followed to create the boot.img are:
Get the stock source code (Samsung openSource)
Modify the kernel (just add/remove some TCP features)
Build the kernel (as per the kernel READ.ME, with aarch64-linux-android-4.9 toolchain)
-->created Image, with no loadable modules (*.ko)
Unpack the boot.img from the stock kernel (abootimg -x )
Create new boot.img replacing the original zImage with the custom kernel Image (abootimg --create . . . )
Make tar.md5 file of the custom boot.img for Odin3
Pushed the custom kernel using Odin3, but it fails to boot ("kernel not enforcing seadnroid"). I have tried using TWRP (install from zip), but it just does bootloop. Can anyone see what I am doing wrong? Am I missing something? I have read most of the "Build kernel from source" dev-threads but have not found a solution for this, nor am I allowed to post my questions there as I am just a junior member.
I would highly appreciate any help, as I have already invested some days with no avail
mdh-labs said:
I have been playing around with kernels (for nexus 5), to add some features to the stock kernel. But I have problem with Samsung. I am trying to build a flashable custom kernel for Samsung S7 edge (G935F). .Steps I followed to create the boot.img are:
Get the stock source code (Samsung openSource)
Modify the kernel (just add/remove some TCP features)
Build the kernel (as per the kernel READ.ME, with aarch64-linux-android-4.9 toolchain)
-->created Image, with no loadable modules (*.ko)
Unpack the boot.img from the stock kernel (abootimg -x )
Create new boot.img replacing the original zImage with the custom kernel Image (abootimg --create . . . )
Make tar.md5 file of the custom boot.img for Odin3
Pushed the custom kernel using Odin3, but it fails to boot ("kernel not enforcing seadnroid"). I have tried using TWRP (install from zip), but it just does bootloop. Can anyone see what I am doing wrong? Am I missing something? I have read most of the "Build kernel from source" dev-threads but have not found a solution for this, nor am I allowed to post my questions there as I am just a junior member.
I would highly appreciate any help, as I have already invested some days with no avail
Click to expand...
Click to collapse
I dont want to tell you something you have already read, if you have been through the Dev forums, But on the off chance:
Have you removed the Fingerprint reader?
The Kernel will fail to boot with it enabled, Unless you know the workaround (EchoTeam)
dave7802 said:
I dont want to tell you something you have already read, if you have been through the Dev forums, But on the off chance:
Have you removed the Fingerprint reader?
The Kernel will fail to boot with it enabled, Unless you know the workaround (EchoTeam)
Click to expand...
Click to collapse
Hmm ... Fingerprint reader? No, I have not removed anything. I was thinking that since I am not adding anything that was not already in the stock kernel source, I do not need to do any modifications. How can I remove this reader?
Here are the temporary solutions.
Way A:
Remove /system/lib/libbauth* , /system/lib64/libbauth*
Way B: (If you want to completely disable (or bypass) TEE)
Remove /system/lib/libbauth* , /system/lib64/libbauth*
Replace /system/lib64/hw/gatekeeper.exynos8890.so,/system/lib64/hw/keystore.exynos8890.so with these i uploaded.
Both of them will make your FP Sensor not working.
(Lock Screen will work)
But,at least,you get a stable custom kernel.
Click to expand...
Click to collapse
http://forum.xda-developers.com/s7-...m-g935f-fd-t3361460/post66762787#post66762787
Thank @Jesse Chan He also fixed the fingerprint too.
dave7802 said:
http://forum.xda-developers.com/s7-...m-g935f-fd-t3361460/post66762787#post66762787
Thank @Jesse Chan He also fixed the fingerprint too.
Click to expand...
Click to collapse
Thanks a lot, I will try that. I have already seen his custom kernel (would love to ask something on his thread but . . . )
mdh-labs said:
Thanks a lot, I will try that. I have already seen his custom kernel (would love to ask something on his thread but . . . )
Click to expand...
Click to collapse
I saw someone mention me.
Well, you must disable all TIMA-related configs as well as KNOX_KAP to get kernel boot.
And then, if you want to get a stable kernel with FP, you must apply my FP fix.(could be found in my Kernel's flashable zip)
Jesse Chan said:
I saw someone mention me.
Well, you must disable all TIMA-related configs as well as KNOX_KAP to get kernel boot.
And then, if you want to get a stable kernel with FP, you must apply my FP fix.(could be found in my Kernel's flashable zip)
Click to expand...
Click to collapse
I appreciate that you have had the time to look at my question. I've tried the tricks you suggested but my kernel still cannot boot. Modified the .config file (with menuconfig):
disabled
# CONFIG_KNOX_KAP is not set
# CONFIG_TIMA is not set
# CONFIG_TIMA_LKMAUTH is not set
not in config anymore
-CONFIG_TIMA_LOG=y
-CONFIG_TIMA_RKP=y
Then built a custom boot.img as mentioned in my question and added the META and mcRegistry folders from your flashable zip file to create a zip file out of the three.
I have also tried by removing the libbauth* files from system/lib/ and system/lib64 directories?
One more thing, does it matter whether I get just an Image file or zImage from kernel build (I get only Image and .gz of it)?