Is there any way to update cm10.1 sdcard version to the nook on fire kernel without messing with the internal rom?
clong510 said:
Is there any way to update cm10.1 sdcard version to the nook on fire kernel without messing with the internal rom?
Click to expand...
Click to collapse
guess what,you cant have two kernels at a time :silly: NOF is just fine
rafiur said:
guess what,you cant have two kernels at a time :silly: NOF is just fine
Click to expand...
Click to collapse
What I meant was, how can I make the NOF kernel run on the rom I have on sdcard? If I flash it internally it messes up my original nook os.
clong510 said:
What I meant was, how can I make the NOF kernel run on the rom I have on sdcard? If I flash it internally it messes up my original nook os.
Click to expand...
Click to collapse
not sure if it will work, but you can give it a try, but dont blame me if anything goes wrong
1.back up your current bootable sd card in case anything goes wrong.
2.download and unzip the kernel, replace the "boot.img" file in your sd card with the one you found with the zip.
3.copy the module files you found in the zip in the exact directory, which is /system/lib/modules . you can do it in your pc, alternatively, you can do it with root explorer.
rafiur said:
...
2.download and unzip the kernel, replace the "boot.img" file in your sd card with the one you found with the zip.
...
Click to expand...
Click to collapse
These two boot.img files are not interchangeable: the boot.img for installation on emmc is a concatenation of Cyanoboot and CM boot -- see http://forum.xda-developers.com/showthread.php?t=1539112. On SDcard based ROM image Cyanoboot and CM boot are separate standalone files, flashing_boot.im and boot.img respectively.
digixmax said:
These two boot.img files are not interchangeable: the boot.img for installation on emmc is a concatenation of Cyanoboot and CM boot -- see http://forum.xda-developers.com/showthread.php?t=1539112. On SDcard based ROM image Cyanoboot and CM boot are separate the standalone files flashing_boot.im and boot.img respectively.
Click to expand...
Click to collapse
oh I get it now
digixmax said:
These two boot.img files are not interchangeable: the boot.img for installation on emmc is a concatenation of Cyanoboot and CM boot -- see http://forum.xda-developers.com/showthread.php?t=1539112. On SDcard based ROM image Cyanoboot and CM boot are separate standalone files, flashing_boot.im and boot.img respectively.
Click to expand...
Click to collapse
so there no other way unlesss you decompile and then recompile it differently, if I understand it right?
clong510 said:
so there no other way unlesss you decompile and then recompile it differently, if I understand it right?
Click to expand...
Click to collapse
Yup.
Why not request the NOF developer for a SD-based ROM version?
digixmax said:
Yup.
Why not request the NOF developer for a SD-based ROM version?
Click to expand...
Click to collapse
I don't have enough post to get into that thread, but I would love a sd version of it.
Related
UPDATE: Since some of you guys are still finding this useful, I updated the CWM version to 3.0.2.8. Please note that ROM Manager is the best way to install CWM 3.0.2.8. You should only need this .zip if you need to restore the B&N boot loader.
There are a number of CWM installable .zip files being distributed that break Clockworkmod in a way that Rom Manager will not fix. This .zip file will reinstall the B&N bootloader (to enable the recovery buttons) and install ClockworkMod on your internal memory. This .zip will only help if you have installed a "flashable" .zip and can no longer get into CWM by holding N + Power on boot.
This file can be installed with IOMonster's bootable CWM to re-enable the ability to use CWM without an SD card.
How to use:
1) Create a bootable CWM SD card from the link above.
2) Mount the SD card on your computer and copy the RecoveryFix.zip file to it.
3) Boot the Nook into CWM from the SD card.
4) Choose "install zip from sdcard"
5) Choose "choose zip from sdcard"
6) Browse to the RecoveryFix.zip and select it.
7) Choose "Yes - Install RecoveryFix.zip"
CWM should now work by booting and holding the N + Power buttons.
Technical details:
The bootloader (u-boot.bin) file included with the stock image has code to look for the recovery key sequence on boot. It also contains the "Touch the Future of Reading" splash screen. Some of the update .zip releases include a custom uboot.bin (to change the splash screen) that does not look for the recovery keys...so there's no way to boot into recovery without an SD.
Currently the only automated way to put the correct files back is by using one of the stock recovery .zips. These take the entire system back to stock though. All this .zip does is replace the stock u-boot.bin file, CWM uRecRam and CWM uRecImg files on the /boot partition. This can also be easily fixed by booting any image from an SD card and copying these files manually.
is this for use with any flashable rom or only certain ones? i'm on hcv4 and want to make sure this is safe to use before flashing it.
This worked fantastic! Thank you!
byproxy said:
is this for use with any flashable rom or only certain ones? i'm on hcv4 and want to make sure this is safe to use before flashing it.
Click to expand...
Click to collapse
This is a standalone fix - its only necessary if you've flashed a rom and could no longer boot into CWM recovery afterward.
thanks again xawen!
Thanks so much for this! Great work!
Signature verification failed
Will This work with the Froyo builds?
Thanks
huemedia said:
Will This work with the Froyo builds?
Thanks
Click to expand...
Click to collapse
It should work with any build. It does not replace any of the build specific files, just the boot loader and the recovery images.
Works on phiremod (CM7). I was stressing why I couldn't reach my internal recovery, but was too lazy to do any research on the matter. Just stumbled upon this and everything is fixed again
Just what I was looking for... thanks!
omarsalmin said:
Works on phiremod (CM7). I was stressing why I couldn't reach my internal recovery, but was too lazy to do any research on the matter. Just stumbled upon this and everything is fixed again
Click to expand...
Click to collapse
what do you mean by "everything is fixed again"?
I like phiremod and all, but no internal storage is irking me and I want to go back to rooted stock and try to make a CM7 bootable SD.
Flashed this, now I'm stuck on the "Touch the Future of Reading" splash screen. Running CM7 nightly latest, dalingrin's 1100MHz Overclock.
Edit: Trying to boot, won't get past that damn splash screen. Tried reflashing cm7-encore-full-5.zip, gapps, got nothing. Going to try flashing the overclock again and see if that helps.
Edit2: No dice. I don't have a backup, either. Guess I have to flash a whole new boot.img?
This should be stickied. There are a LOT of CWR files around here right now.
oshigeru said:
Flashed this, now I'm stuck on the "Touch the Future of Reading" splash screen. Running CM7 nightly latest, dalingrin's 1100MHz Overclock.
Edit: Trying to boot, won't get past that damn splash screen. Tried reflashing cm7-encore-full-5.zip, gapps, got nothing. Going to try flashing the overclock again and see if that helps.
Edit2: No dice. I don't have a backup, either. Guess I have to flash a whole new boot.img?
Click to expand...
Click to collapse
Same thing kept happening to me. I would hold down the power button or power+n button or power+volume up + n button to get the NC to shut down. Then, I'd press the power+volume up + n button for a few seconds; this would get it to boot into CWR. From CWR I'd select reboot system. After that it would have no problem fully booting (until the problem happeend again). I did notice that after a while the startup boot took longer. After pressing the power button to power on the NC it would take several seconds before the "touch the future of reading" screen to come up, and it would take several more seconds (30 or so) for it to get past that screen.
I'm not sure what the beneft is of doing this; as long as I have a CWR bootable microSD with me (always in the NC's case) I don't need this.
xawen said:
There are a number of CWM installable .zip files being distributed that break Clockworkmod in a way that Rom Manager will not fix. This .zip file will reinstall the B&N bootloader (to enable the recovery buttons) and install ClockworkMod on your internal memory. This .zip will only help if you have installed a "flashable" .zip and can no longer get into CWM by holding N + Power on boot.
This file can be installed with IOMonster's bootable CWM to re-enable the ability to use CWM without an SD card.
How to use:
1) Create a bootable CWM SD card from the link above.
2) Mount the SD card on your computer and copy the RecoveryFix.zip file to it.
3) Boot the Nook into CWM from the SD card.
4) Choose "install zip from sdcard"
5) Choose "choose zip from sdcard"
6) Browse to the RecoveryFix.zip and select it.
7) Choose "Yes - Install RecoveryFix.zip"
CWM should now work by booting and holding the N + Power buttons.
Technical details:
The bootloader (u-boot.bin) file included with the stock image has code to look for the recovery key sequence on boot. It also contains the "Touch the Future of Reading" splash screen. Some of the update .zip releases include a custom uboot.bin (to change the splash screen) that does not look for the recovery keys...so there's no way to boot into recovery without an SD.
Currently the only automated way to put the correct files back is by using one of the stock recovery .zips. These take the entire system back to stock though. All this .zip does is replace the stock u-boot.bin file, CWM uRecRam and CWM uRecImg files on the /boot partition. This can also be easily fixed by booting any image from an SD card and copying these files manually.
Click to expand...
Click to collapse
This fixed my nook. Thanks!!!!!
Works - after a few tries!
Really appreciate the work. Thanks!
While I keep my boot disk with me, I am very happy to have the ability to power+N into CWR.
Great work, thanks m8s!
xawen said:
All this .zip does is replace the stock u-boot.bin file, CWM uRecRam and CWM uRecImg files on the /boot partition.
Click to expand...
Click to collapse
Can you be more specific about exactly which u-boot.bin, uRecRam and uRecImg files are included - including source and version ?
ADude said:
Can you be more specific about exactly which u-boot.bin, uRecRam and uRecImg files are included - including source and version ?
Click to expand...
Click to collapse
This .zip has the stock (B&N) u-boot.bin and the uRecRam and uRecImg for CWM 3.0.0.5. It was built a while ago to fix an issue with specific CMW installable Froyo .zip files that were being distributed. I haven't seen any CM7 images with this problem, but if anyone still has a need for this I can update to a current CWM version and post tonight.
xawen said:
This .zip has the stock (B&N) u-boot.bin and the uRecRam and uRecImg for CWM 3.0.0.5. It was built a while ago to fix an issue with specific CMW installable Froyo .zip files that were being distributed. I haven't seen any CM7 images with this problem, but if anyone still has a need for this I can update to a current CWM version and post tonight.
Click to expand...
Click to collapse
Aha - I looked more closely and saw that it is an old thread that was brought to the surface by a "thanks" comment.
question
So I flash this fix and can get into CWM 3.0.0.5, then I flash the official CWM 3.0.1.0 and can no longer get into recovery. I also tried the manual procedure using adb. Still no dice.
What am I doing wrong?
Hi,
I'm kinda new to flashing and upgrading my phone.
Therefore I got some questions:
Currently running on my Neo: AOSP 4.0.3 ICS BETA with kernel provided there
Baseband says: 56 as last two digits
I would like to upgrade my baseband to 62. (latest)?
As far as I understood I will have to flash 4.0.2.A.0.62 Baseband using flashtool.
Do I have to flash the kernel again after upgrading baseband or should I flash the 4.0.2.A.0.62 Kernel first and change it afterwards?
fastboot flash boot boot.img
Click to expand...
Click to collapse
Will changing the baseband or kernel delete anything?
When would be the right time to apply the RAISE your NEO userdata space patch? Before or after baseband, kernel flash?
Sometimes they say that a reboot is required after flashing a new ROM before flashing an update.zip in CWM. Do I have to reboot at other times?
Is there a tool or a possibility I missed which can flash anything like baseband, kernel, ROM and updates to it in one step?
If I want to edit a ROM like directly changing bootanimation and ringtones.
How should the zip file be packed? No compression, etc?
Is it a good idea to include updates which I would have flashed in CWM directly into the ROMs zip file?
Do I have to flash the kernel again after upgrading baseband or should I flash the 4.0.2.A.0.62 Kernel first and change it afterwards?
Click to expand...
Click to collapse
Kernel is not related to baseband. Simply flash baseband, no need to flash kernel after or before.
Will changing the baseband or kernel delete anything?
Click to expand...
Click to collapse
Flashing baseband won't delete anything, but flashing kernel might. I see that kernel in that thread have CWM inside, so if you flash stock kernel you will lose that.
When would be the right time to apply the RAISE your NEO userdata space patch? Before or after baseband, kernel flash?
Click to expand...
Click to collapse
Whenever you want. It's not related to kernel or baseband.
Sometimes they say that a reboot is required after flashing a new ROM before flashing an update.zip in CWM. Do I have to reboot at other times?
Click to expand...
Click to collapse
Yes, they say that so that ROM "settles down in it's place" then you can install fixes and stuff.
What other times?
Is there a tool or a possibility I missed which can flash anything like baseband, kernel, ROM and updates to it in one step?
Click to expand...
Click to collapse
There is flashtool, but only for stock rom's. Custom roms are installed as a .zip file via CWM recovery.
If I want to edit a ROM like directly changing bootanimation and ringtones.
Click to expand...
Click to collapse
You can do that with root explorer app(or any app which can access to system), create that bootanimation.zip on pc and upload it to sdcard, then move it to where it needs to be. For bootanimation.zip, yes, it's with no compression. How it's created, check other bootanimation.zip's over the net.
For other zip's which are flashed trough CWM, it's a bit more complicated to explain how to create them.
Is it a good idea to include updates which I would have flashed in CWM directly into the ROMs zip file?
Click to expand...
Click to collapse
Well depends. Most likely yes, but I would still ask creator/porter of each rom if that is advisable
Madfysh said:
seXneo said:
If I want to edit a ROM like directly changing bootanimation and ringtones.
How should the zip file be packed? No compression, etc?
Click to expand...
Click to collapse
You can do that with root explorer app(or any app which can access to system), create that bootanimation.zip on pc and upload it to sdcard, then move it to where it needs to be. For bootanimation.zip, yes, it's with no compression. How it's created, check other bootanimation.zip's over the net.
For other zip's which are flashed trough CWM, it's a bit more complicated to explain how to create them.
Click to expand...
Click to collapse
Thank you very much.
But in this point there was a misunderstanding.
I just wanted to know how the update.zip or rom.zip has to be packed and if it's save to replace bootanimation.zip inside rom.zip. Are there any checksums for apk or other files inside an CWM update.zip I need to change?
Most of the ICS based ROMs use MT15i_Neo_ICS_Kernel_V1.img. Where does it come from and where is it's original thread?
if it's save to replace bootanimation.zip inside rom.zip. Are there any checksums for apk or other files inside an CWM update.zip I need to change?
its safe to change bootanimations.zip and any other apk or file in side the provided update.zip file
but if u extract it n do changes then u will lose the signature of the developer n wont b able to install the update.zip properly
chintu1234 said:
its safe to change bootanimations.zip and any other apk or file in side the provided update.zip file
but if u extract it n do changes then u will lose the signature of the developer n wont b able to install the update.zip properly
Click to expand...
Click to collapse
Yes of course. If original zip file flashed and runs nice it will be my fault if it won't after my edits.
So no checksums in the update.zip directly. Thanks.
Signing of an altered apk file is required. Got it.
And I figured that there is no signing of the bootanimation possible.
Will post my question regarding the kernel in an extra thread.
Hi
I just bought a second hand nook tablet and it was flashed the CM10.2, I'm preparing to flash CM11 on it, but it seems the recovery is a bit older.
I download the latest recovery.img from this post http://forum.xda-developers.com/showthread.php?t=2585175.
But I've no idea about how to update the recovery, could anyone give some help? Thanks in advance.
See http://forum.xda-developers.com/showpost.php?p=47680141&postcount=2.
Oops.
droople said:
Hi
I just bought a second hand nook tablet and it was flashed the CM10.2, I'm preparing to flash CM11 on it, but it seems the recovery is a bit older.
I download the latest recovery.img from this post http://forum.xda-developers.com/showthread.php?t=2585175.
But I've no idea about how to update the recovery, could anyone give some help? Thanks in advance.
Click to expand...
Click to collapse
download the zip file i provided in that same thread u showed. its the second post. not the recovery.img. do the img file only if u know wut ur doing. put the zip i gave into a sd card. reboot into cyanoboot. open internal recovery. choose zip from sd card. choose the zip file i gave u. which means flashing it......reboot into cyanoboot. open internal recovery and now u have the newest cwm....lmk if u are confused.
newbtrigger69 said:
download the zip file i provided in that same thread u showed. its the second post. not the recovery.img. do the img file only if u know wut ur doing. put the zip i gave into a sd card. reboot into cyanoboot. open internal recovery. choose zip from sd card. choose the zip file i gave u. which means flashing it......reboot into cyanoboot. open internal recovery and now u have the newest cwm....lmk if u are confused.
Click to expand...
Click to collapse
thank you newbtrigger69
droople said:
thank you newbtrigger69
Click to expand...
Click to collapse
anytime i can help a fellow xda member
and if u can. remember to thank me on the tab
dont want to fall behind on those
<-----------------------------------------------------
How do u update TWRP?
Sent from my SGH-T889 using XDA Premium 4 mobile app
jpelagio11 said:
How do u update TWRP?
Click to expand...
Click to collapse
Here's how:
Download any flashable internal recovery zip file (e.g., flashable_CWM_6.0.2.9.zip from Succulent's repo http://goo.im/devs/succulent/acclaim/recovery).
Use an archive file manager such as 7-zip to delete and replace the recovery.img inside the flashable zip file with your choice of TWRP (internal recovery) file from http://techerrata.com/browse/twrp2/acclaim (e.g., openrecovery-twrp-2.6.3.1-acclaim.img); remember to rename the downloaded TWRP .img file to recovery.img before inserting it into the zip file.
Flash the resulting flashable recovery zip file using current EMMC recovery or SD-based recovery.
I have an 8gb nook tablet that I rooted probably 2 and a half years ago and haven't changed anything on it since. I am wanting to undo and update to current root and flash a 4.4 rom like on my phone. What is the best way to go about this? I know how to unroot, I just need to know the best way to root currently. Thanks.
Custom ROMs like CM comes with built-in root capability, and moreover once installed replaces completely the existing ROM currently in place (be it stock ROM, rooted stock ROM, or another custom ROM). As such, there is no need to root (or re-root) prior to flashing a custom ROM. See http://forum.xda-developers.com/showthread.php?t=2575489 for more background info and pointers.
Cool, thanks for the reply and links. I have some reading to do.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Will your guide for Installing CM10.1 Internally on Nook Tablet work for the 8gb model also? Will it work for CM11 also?
ryknow27 said:
Will your guide for Installing CM10.1 Internally on Nook Tablet work for the 8gb model also?
Click to expand...
Click to collapse
Yes.
Will it work for CM11 also?
Click to expand...
Click to collapse
It should work (with the usual caveat YMMV). Flashing CM11 requires CWM version 6.0.4.5 or later, or TWRP version 2.6.3.0 or later (in step 2(b) of http://forum.xda-developers.com/showpost.php?p=43326042&postcount=123); you can find the SD version of TWRP 2.6.3.x at http://techerrata.com/browse/twrp2/acclaim. You also need a recent Gapps version corresponding to the CM11.
Alternatively, if your NT is already on CM10.x (as my NT was), you can:
download CM11 ROM and the corresponding Gapps zip files onto your NT (user content media partition).
use SD based recovery to flash a flashable emmc CWM zip (http://forum.xda-developers.com/showpost.php?p=48855275&postcount=2) or flashable emmc TWRP zip (http://forum.xda-developers.com/showpost.php?p=49111924&postcount=8) into emmc.
remove SD then boot onto emmc recovery (which is installed in step 2) and use it to install the ROM and Gapps zip files downloaded in step 1.
Remember to use SD based recovery to backup your current ROM before flashing CM.
I need help once again. In step 2a. of Installing CM10.1 Internally on Nook Tablet, I do not see the boot.zip with the 3 files needed and I am not sure how to extract them from the .img file from the pre-made SDcard images. I've only used linux like once and that was to root my Droid DNA. Thank you for your patience with me.
Nevermind...I found a Linux Reader program that let me extract them.
Thanks again.
ryknow27 said:
I need help once again. In step 2a. of Installing CM10.1 Internally on Nook Tablet, I do not see the boot.zip with the 3 files needed and I am not sure how to extract them from the .img file from the pre-made SDcard images. I've only used linux like once and that was to root my Droid DNA. Thank you for your patience with me.
Nevermind...I found a Linux Reader program that let me extract them.
Thanks again.
Click to expand...
Click to collapse
For future reference, you can use 7-zip (which is available for windows) to open .img files and extract its content.
digixmax said:
For future reference, you can use 7-zip (which is available for windows) to open .img files and extract its content.
Click to expand...
Click to collapse
I did try 7-zip first and it didn't work. I may have just done something wrong. I'll try it again. Thanks for all the help.
Hi there!
Today I finally found how to make our codinas' kernels universal, i.e. allow to install kernel on whatever ROM and finally separate recovery from kernel. It's well known, bootloader decides what will be loaded - kernel or recovery. That probably may explain why AnyKernel installer(or other similar) doesn't work on codina, because we can't move recovery partition anywhere.
But there is also a little trick that allow us load recovery and boot.cpio from different partition - https://github.com/ChronoMonochrome/Chrono_Kernel/commit/df9094f1f12618ad9599da266792d6b2f8106170 - just an another approach
Don't worry, we won't touch bootloader at all.
As can be seen, /dev/block/mmcblk0p17 (kernel2 partition) will be used for storing recovery.cpio and boot.cpio. On stock that may not work (I don't know for what exactly uses Kernel2 partition, besides of manually restoring of kernel1 partition. I only know that is almost useless on custom ROMs, and we can use it as we want )
First do some preparations:
Download this kernel and needed recovery/boot scripts(4.4.x.cpio.zip, 4.4.x_f2fs.cpio.zip, etc... 4.4.x.cpio means that it support only ext4) from my google drive (folder ramdisks), unzip recovery (twrp or cwm) and rename to recovery.cpio, then move it to external SD card. Then do it with boot scripts that you've downloaded (e.g. 4.4.x_f2fs.cpio.zip - unzip and rename to boot.cpio)
Well, that all that needs for installation. Read following instruction very carefully, otherwise that may cause brick Keep in mind, all that you do at your own risk! I'm not responsible if you brick your phone!
Installation method:
1) reboot into recovery, plug your phone to your PC, enable adb:
Code:
adb shell
2) Format kernel2 partition to ext4 file system:
Code:
mke2fs -T ext4 /dev/block/mmcblk0p17
Think twice before you hit 'enter' button - wrong command may cause hardbrick!
3) create /ramdisk folder and mount kernel2 partition
Code:
mkdir /ramdisk
mount -t ext4 /dev/block/mmcblk0p17 /ramdisk
move your recovery.cpio and boot.cpio to this folder, give 777 permissions:
Code:
chmod 777 /ramdisk/recovery.cpio
chmod 777 /ramdisk/boot.cpio
4) install downloaded kernel
Now you can change recovery via changing /ramdisk/recovery.cpio - just make a backup of this file, and then replace with one of another recoveries. If you want to install another ROM or change filesystem of partition then replace /ramdisk/boot.cpio with one of needed boot scripts. Don't forget to give 777 permission (probably 644 is enough, but I didn't test it) to both of these files.
This method tested and working on 4.4.x TC ROM + twrp recovery + kernel with full F2FS support.
Well, now it's time to create uncompressed kernel, that may slightly decrease the boot time
@ChronoMonochrome
Thanks. do you mean that kernel2 partition is useless in stock and cyanogenmod firmware?
Is it right that boot loader will read kernel1 partition then it will read system partition? and kernel2 is not necessary for booting?
I have installed new universal kernel (2.5) , so I flashed new ramdisk for 4.4.x , can I roll back to older versions or stock firmware with this ramdisk or I should restore Partition17 backup?
sorset said:
@ChronoMonochrome
Thanks. do you mean that kernel2 partition is useless in stock and cyanogenmod firmware?
Click to expand...
Click to collapse
As it turned out, it's unneeded even on stock. So if you won't restore kernel2 partition, nothing will happen.
Is it right that boot loader will read kernel1 partition then it will read system partition? and kernel2 is not necessary for booting?
I have installed new universal kernel (2.5) , so I flashed new ramdisk for 4.4.x , can I roll back to older versions or stock firmware with this ramdisk or I should restore Partition17 backup?
Click to expand...
Click to collapse
Yes, you can roll back to usual kernels. it doesn't matter what written on kernel2 partition - real kernel or anything else...
ChronoMonochrome said:
As it turned out, it's unneeded even on stock. So if you won't restore kernel2 partition, nothing will happen.
Click to expand...
Click to collapse
Ok, thanks , But why do you mount kernel2 partition inside of OS? As I understand boot.cpio is necessary before booting OS . And inside of OS is just an extra storage! (is that true?)
sorset said:
And inside of OS is just an extra storage! (is that true?)
Click to expand...
Click to collapse
Yes and no, is 16 Mb big enough to be called "storage"? I did it, just to be able replace ramdisks even without booting to recovery. But newest boot scripts doesn't have it.
Ace 2 has 15 - 20 Partitions my Friend
ace2nutzer said:
Ace 2 has 15 - 20 Partitions my Friend
Click to expand...
Click to collapse
And what ? We actually talking about kernel2 partition.
ChronoMonochrome said:
And what ? We actually talking about kernel2 partition.
Click to expand...
Click to collapse
sorry, i meant @sorset
ChronoMonochrome said:
Yes and no, is 16 Mb big enough to be called "storage"? I did it, just to be able replace ramdisks even without booting to recovery. But newest boot scripts doesn't have it.
Click to expand...
Click to collapse
You are right , but I remember days that 1.44MB floppy disk was a large STORAGE and 16MB was HUGE
sry , I have another question , So can I remove its line from fstab to prevent mounting?
I'm confused
boot.img in kernel archive is recovery image that will extract on partition15 (kernel) , but what recovery.cpio exactly is that yu copy on partition17 (kernel2) ?
ace2nutzer said:
Ace 2 has 15 - 20 Partitions my Friend
Click to expand...
Click to collapse
Yes,With counting internal storage , 17 exactly , but thats not the point , I'm afraid.
sorset said:
sry , I have another question , So can I remove its line from fstab to prevent mounting?
Click to expand...
Click to collapse
just redownload bootscripts(kernel/ramdisks), as I said, newest scripts doesn't mount kernel2 partition.
boot.img in kernel archive is recovery image that will extract on partition15 (kernel) , but what recovery.cpio exactly is that yu copy on partition17 (kernel2) ?
Click to expand...
Click to collapse
I don't get it rephrase please
ChronoMonochrome said:
just redownload bootscripts(kernel/ramdisks), as I said, newest scripts doesn't mount kernel2 partition.
I don't get it rephrase please
Click to expand...
Click to collapse
I didn't too
There is an Image named boot.img in kernel flashable zip archive that extracts into partition 15 (named kernel) as I understood is recovery (TWRP or CWM) image and you wont touch linux orginal image , and your modified custom kernel is new modules for linux image that loads while booting (sry, I cant explain fine), So what is recovery.cpio that is in recovery flashable zip image that extracts into partition 17 (named kernel2) ?
sorset said:
as I understood is recovery (TWRP or CWM) image and you wont touch linux orginal image
Click to expand...
Click to collapse
originally kernel + recovery
, and your modified custom kernel is new modules for linux image that loads while booting (sry, I cant explain fine), So what is recovery.cpio that is in recovery flashable zip image that extracts into partition 17 (named kernel2) ?
Click to expand...
Click to collapse
In my mod kernel(mmcblk0p15) and recovery (mmcblk0p17) are splitted.
Thank you. I see.
This is probably the best (and only?) way to rebuild the ramdisk without having to compile anything, which is an excellent base for my NoUMS patches
:good:
<remove>