{26/JAN/2012}SD ROM+DualModeRecovery -MultibootCWM+XRecovery[Stock Kernel&Alfs Kernel - XPERIA X8 Original Android Development

{26/JAN/2012}SD ROM+DualModeRecovery -MultibootCWM+XRecovery[Stock Kernel&Alfs Kernel
Multiboot+DualRecovery (CWM with multiboot & XRecovery together at last!)
What is multiboot CWM by nobodyAtall?
It is a recovery that allows us to boot ROMs (with certain changes made) from our sd-cards!
Have one ROM on your NAND(internal memory) and as many ROMs as you can fit(400mb each) on your sd-card.
What is DualRecovery?
It is the option to: (in this case)
Boot into XRecovery by tapping the back button while your phone is turning on.
&
Boot into CWM multiboot by repeatedly tapping the screen while your phone is turning on.
Install Instructions:
Have approx. ~900mb free on your sd-card.
1:Simply download the "Multiboot+DualRecInstaller+FPv24SD.zip" & flash in ClockWorkMod.
2:Reboot phone + while rebooting tap the touchscreen like crazy!
3:In CWM multiboot, go to multiboot settings, choose "Select default boot option"
4:Select "FroyoProv24SD.StockKernel" then reboot.
Read Post#3!
DOWNLOAD:
Download "Multiboot+DualRecInstaller+FPv24SD.zip" Here~100mb.
This is for STOCK KERNEL, everyone else read post #2!
No Mirrors! I will make a mirror soon!!!
If you are on stock kernel this should work on ALL Roms...however I have only tested a few.
Credits:
Multiboot CWM= nobodyAtall.
XRecovery= zdzihu.
Dual Mode XRec+MultiCWM= [email protected] (me)
AutoInstaller+Extras= [email protected] (me)
This is not a new idea, I have just made the necessary changes, packaged dual mode recovery with multiboot CWM, made an AutoSDROMInstaller package, as well as offering your first ROM(FPv24SD).
Users were asking for this, so I made it.

Alfs Kernel Users:
What is DualRecovery?
It is the option to: (in this case)
Boot into CWM by tapping the back button while your phone is turning on.
&
Boot into CWM multiboot by repeatedly tapping the screen while your phone is turning on.
Install Instructions:
Have approx. ~900mb free on your sd-card.
1:Simply download the "AlfsMultiboot+DualRecInstaller+FPv24SD.zip" & flash in Alfs ClockWorkMod.
2:Reboot phone + while rebooting tap the touchscreen like crazy!
3:In CWM multiboot, go to multiboot settings, choose "Select default boot option"
4:Select "FroyoProv24SD.AlfsKernel" then reboot.
Read Post#3!
Download:
Download "AlfsMultiboot+DualRecInstaller+FPv24SD.zip" here~100mb.
No mirrors! I will add a mirror later! Please be patient!
Please note:
You can flash this at any time but if installing a new NAND(internal memory) ROM...
This is the last thing that should be flashed, if you flash Alfs kernel fix after this, you will break DualRecovery functionality.

Important Information:
1. Not all sd-card are supported!!! If you set a default boot option but your phone phone boots into your normal rom then your sd-card is NOT supported. (Try a different sd-card.)
2. Each boot option(ROM) takes up around 400mb of space on your sd-card.
3. However you need 800mb(+100mb for the installer) free on your sd-card to install this as I have included a 512mb data.img with this package so you can go crazy installing apps.
4. First boot will be SLOW. We are booting from the sd-card remember?
5. Slow sd-cards will mean a really sluggish multiboot.
6. Performance is very different compared with ROMs on your NAND(internal memory), you shouldn't compare them.
Explanation of multiboot functions:
-Select default boot option: Set the external(SD) ROM in which you want the phone to boot from now on.
-Unset default boot option: Unset booting of external(SD) ROM so that the phone will boot from NAND (internal memory).
-Create boot option from zip: Select and install an SD ROM in sdcard (requires 400mb free).
-Delete existing boot option: Delete an already installed ROM from your sdcard.
-Flash zip to boot option: Flash updates to an already installed (SD) ROM.

Bugs:
Stock Kernel:
--Some sd-cards are not supported -If you set default boot option but your NAND(internal memory) ROM loads, then your sd-card is not supported.
Alfs Kernel:(This may just be for the sd-card I have here, please try yourself.)
--SD-Card can not be accessed, not from USB or from file explorer
You can still download and install all your favourite games with the large data.img provided. (Alfs vold is already included, it doesn't magically fix this lol.)
--Cannot 'Create boot option from zip'+'Flash zip to boot option'=Same bug as above really.
This will either need ramdisk changes in Alfs kernel (probably wont happen) or ramdisk changes in ROM, or recompile of nAa's CWM multiboot 4 Alfs (probably wont happen).

To ROM devs:
Just give me a thanks & nobodyAtall a thanks before using this stuff, that's all I ask.
Devs using Alfs:
Due to the sd-card bug at the moment you will have to provide your rom in either:
1. A package like this one. -Use mine as a base, so users can auto install easily through CWM.
2. A system.img that users can put in a folder in the 'multiboot' folder of their sdcard with a cache.img & data.img (they can just copy the ones I have provided from one folder to another folder of there sd-cards).
3. Fix the sd-card bug, I haven't even looked at this yet, I have spent too much time on this already.
A lot more information can be found here & (for x10mini)here.
These links are old though so many of the stuff may not work anymore or cause weird bugs with current ROMS!
Not really advised to do it yourself, wait for your ROM developer to release a multiboot patch!

This seems really crazy, will try it out asap there are a bit more infos!
Will it be possible to eventually have boot images of 4 different Android versions?

will be the rom faster if it boots from sd class 10 card? Or nand is faster? Sorry, i have no time to test. I will be thanksful if you give me answer

Hefko said:
will be the rom faster if it boots from sd class 10 card? Or nand is faster? Sorry, i have no time to test. I will be thanksful if you give me answer
Click to expand...
Click to collapse
NAND ofcourse, there's still the bridge to the SD card.
You can compare it with your PC, the speed of your HDD is still faster than any USB pen you plug in.

Well in some ways & doing some things, SD ROMS will be faster.
But overall probably NAND is slightly faster.
For benchmarking scores SD ROMS will definitely mark higher.
This is so easy, on stock kernel or Alfs Kernel, you just install it in ClockWorkMod & hey presto dual mode recovery with XRecovery, Multiboot-ClockWorkMod and a flashy new SD ROM.
It works great for me...I play all my games on my SD ROM then I don't lose my save games when flashing new test updates of my NAND ROM.
It seems this was just a big waste of time for me though. No one interested in this??

i know it sounds stopid,but what is ETA? i really dont know

shadik555 said:
i know it sounds stopid,but what is ETA? i really dont know
Click to expand...
Click to collapse
http://en.wikipedia.org/wiki/Estimated_time_of_arrival
Google is your friend.

thnx

this could be handy if i ever manage to download the link, makes me wait then goes wrong then tells me to try again in a hour, plz could you make another link thanks

suppose i wanna mutiboot ics and gb what should i do

ankitxperia said:
suppose i wanna mutiboot ics and gb what should i do
Click to expand...
Click to collapse
stop daydreaming XD
ics needs nAa 11 or nAa ics,and multiboot only worksbon alfs and stock kernel.not nAa!!
Sent from my X8 using xda premium

Related

Solution to problems of performance, stability and performance, running Minicm7.

IMPORTANT GUIDE FOR THE SOLUTION TO PERFORMANCE, STABILITY AND PERFORMANCE, RUNNING MINICM7.
using MiniCM7 by nobodyAtall
before commenting or asking about, lags, slowness or anything else, try theses steps, they could really solve all that
1 - Latest 2.1.1.A.0.6/2.1.1.C.0.0 SE firmware / Baseband: 53,404,015 M76XX-TSNCJOLYM-
(you should know that since you read miniCM7 thread's first post )
[*]2-Having the unlocked bootloader
3 - download the all in one package (ROM+kernel) by nobodyatall
4 - Backup all files of your micro sd on the PC, because it will be formatted to perform the installation.
[*]5- format your microSD (using the phone option OR sd card formatter which is better than windows's formatter)
6 - Enter flash mode, and proceed to flash the last nAa kernel (nAa06 for miniCM7-2.1.5).
7 - Disconnect the PC mobile phones and switch it on. As nAa logo appears, repeatedly press the Back button to enter recovery mode.
- Then we enter the recovery mode, connect your phone to your pc, and CWM options, we look in advanced options, mounting usb.
- Pc, we detect the micro sd in our mobile, we proceed to format it, then copy the zip file renamed to update, and google apps.
--> theses two steps are in case you couldn't format before
8 - Disconnect the PC mobile phones, we enter the initial menu of CWM,
- Select 'Backup and Restore -> Backup'
- Select 'wipe data / factory reset' (Suggested)
- Select 'apply update from sdcard'
- Flash GAPPS​
Reboot (The first boot will take approximately 3 minutes)
9 - After installing the rom, no clean junk files, previous rom conflict with minicm7 performance, and we have no real work of our mobile,
10 - Proceed to copy all the files used by the user, just music, videos, apps, but no rom folder or file above (android_secure ...) , after performing this step, restart the phone, and go.
11 - We now have our minicm7 running, fast, stable and with impressive performances.
ronaldvalles said:
IMPORTANT GUIDE FOR USERS WITH PROBLEMS OF PERFORMANCE.
Well I will describe the steps to be useful:
1 - Latest 2.1.1.A.0.6/2.1.1.C.0.0 SE firmware / Baseband: 53,404,015 M76XX-TSNCJOLYM-
2-Having the unlocked bootloader
3 - download all in one package nobodyatall
4 - All files, your micro sd stored on the PC, because it will be formatted to perform the installation.
5 - Enter flash mode, and proceed to flash the kernel naa 5b.
6 - Disconnect the PC mobile phones, as naa logo appears repeatedly press the Back button to enter recovery mode.
7 - Then we enter the recovery mode, connect your phone to your pc, and CWM options, we look in advanced options, mounting usb.
8 - Pc, we detect the micro sd in our mobile, we proceed to format it, then copy the zip file renamed to update, and google apps.
9 - Disconnect the PC mobile phones, we enter the initial menu of CWM,
- Select 'Backup and Restore -> Backup'
- Select 'wipe data / factory reset' (Suggested)
- Select 'apply update from sdcard'
- Flash GAPPS
• Reboot (The first boot will take approximately 3 minutes)
10 - After installing the rom, no clean junk files, previous rom conflict with minicm7 performance, and we have no real work of our mobile,
11 - Proceed to copy all the files used by the user, just music, videos, apps, but no rom folder or file above, after performing this step, restart the phone, and go.
12 - We have our minicm7 running, fast, stable and impressive performance.
It is suggested, try the steps in this guide created by me, before placing COMMENTS, THAT IF THE ROM IS lagging unstable.
Because the wonderful work and FreeXperia Nobodyatall is phenomenal in every update, it is great.
Greetings Matmut if you want to add this guide to the FAQ, I'd appreciate it, be of good help.
I hope it was of good help these instructions, if you believe it was a great help to press the THANKS button.
This is a contribution to the advancement of our Minis.
Sorry for my bad English.
Click to expand...
Click to collapse
i appreciate your work but we allready have instalation guide
ChavitoArg said:
i appreciate your work but we allready have instalation guide
Click to expand...
Click to collapse
yes we do
but this one is better for people that have lag after upgrading
thank you man !
I will add some comments about the guide itself later
this should be in Q&A maybe and stickyed there
(i'll put a link in my faq so that you'll keep thx for you too )
ronaldvalles said:
"11 - Proceed to copy all the files used by the user, just music, videos, apps, but no rom folder or file above, after performing this step, restart the phone, and go."
Click to expand...
Click to collapse
This doesn't really make sense...what exactly do you mean?
Copy the music, videos, and apk files to another folder, format the SD card, and put them back in, and then reboot??...aren't there files in the SD card that the Operating system uses?
Kostas1601 said:
This doesn't really make sense...what exactly do you mean?
Copy the music, videos, and apk files to another folder, format the SD card, and put them back in, and then reboot??...aren't there files in the SD card that the Operating system uses?
Click to expand...
Click to collapse
friend trying to say in this step is that the above files we had in the micro sd, we'll go back to SD after installing the rom, but we will not overwrite the folders you create the system in the first start micro sd, Greetings
hopefully they will clarify the question,
for example. androidsecure, and other system folders, because the old files with the current mix and produce slow down the system therefore does not work 100%.
and the files are cached, images, lists, and others, I invite you to try this guide, and you will have good results.
configuration
I use the following configuration, and the truth that goes very well on my phone,
compcahe off
governor interactivex
not undervolt
overclok not
jit enabled
turned home in memory
sms in memory activated
stack size of 32 m
128k cache sd card
ronaldvalles said:
I use the following configuration, and the truth that goes very well on my phone,
compcahe off
governor interactivex
not undervolt
overclok not
jit enabled
turned home in memory
sms in memory activated
stack size of 32 m
128k cache sd card
Click to expand...
Click to collapse
for a better battery life (but maybe instability? it depend on your phone...) you can activate undervolt
---------- Post added at 05:06 PM ---------- Previous post was at 04:48 PM ----------
here is my little suggestion about your guide :
(i surely add a link to my FAQ when there will be a definitive version )
IMPORTANT GUIDE FOR USERS WITH PERFORMANCE PROBLEMS.
using MiniCM7 by nobodyAtall
1 - Latest 2.1.1.A.0.6/2.1.1.C.0.0 SE firmware / Baseband: 53,404,015 M76XX-TSNCJOLYM- (you should know that since you read miniCM7 thread's first post )
2-Having the unlocked bootloader
3 - download the all in one package (ROM+kernel) by nobodyatall
4 - Backup all files of your micro sd on the PC, because it will be formatted to perform the installation.
4b- format your microSD (using the phone option OR sd card formatter which is better than windows's formatter)
5 - Enter flash mode, and proceed to flash the last nAa kernel (nAa05 for miniCM7-2.1.3).
6 - Disconnect the PC mobile phones and switch it on. As nAa logo appears, repeatedly press the Back button to enter recovery mode.
7 - Then we enter the recovery mode, connect your phone to your pc, and CWM options, we look in advanced options, mounting usb.
8 - Pc, we detect the micro sd in our mobile, we proceed to format it, then copy the zip file renamed to update, and google apps.
--> that's too complicated see step 4b
9 - Disconnect the PC mobile phones, we enter the initial menu of CWM,
- Select 'Backup and Restore -> Backup'
- Select 'wipe data / factory reset' (Suggested)
- Select 'apply update from sdcard'
- Flash GAPPS
• Reboot (The first boot will take approximately 3 minutes)
10 - After installing the rom, no clean junk files, previous rom conflict with minicm7 performance, and we have no real work of our mobile,
11 - Proceed to copy all the files used by the user, just music, videos, apps, but no rom folder or file above (android_secure ...) , after performing this step, restart the phone, and go.
12 - We have our minicm7 running, fast, stable and impressive performance.
in attachment, there is the version with ready to modify BBcode
matmutant said:
for a better battery life (but maybe instability? it depend on your phone...) you can activate undervolt
---------- Post added at 05:06 PM ---------- Previous post was at 04:48 PM ----------
here is my little suggestion about your guide :
(i surely add a link to my FAQ when there will be a definitive version )
IMPORTANT GUIDE FOR USERS WITH PERFORMANCE PROBLEMS.
using MiniCM7 by nobodyAtall
1 - Latest 2.1.1.A.0.6/2.1.1.C.0.0 SE firmware / Baseband: 53,404,015 M76XX-TSNCJOLYM- (you should know that since you read miniCM7 thread's first post )
2-Having the unlocked bootloader
3 - download the all in one package (ROM+kernel) by nobodyatall
4 - Backup all files of your micro sd on the PC, because it will be formatted to perform the installation.
4b- format your microSD (using the phone option OR sd card formatter which is better than windows's formatter)
5 - Enter flash mode, and proceed to flash the last nAa kernel (nAa05 for miniCM7-2.1.3).
6 - Disconnect the PC mobile phones and switch it on. As nAa logo appears, repeatedly press the Back button to enter recovery mode.
7 - Then we enter the recovery mode, connect your phone to your pc, and CWM options, we look in advanced options, mounting usb.
8 - Pc, we detect the micro sd in our mobile, we proceed to format it, then copy the zip file renamed to update, and google apps.
--> that's too complicated see step 4b
9 - Disconnect the PC mobile phones, we enter the initial menu of CWM,
- Select 'Backup and Restore -> Backup'
- Select 'wipe data / factory reset' (Suggested)
- Select 'apply update from sdcard'
- Flash GAPPS
• Reboot (The first boot will take approximately 3 minutes)
10 - After installing the rom, no clean junk files, previous rom conflict with minicm7 performance, and we have no real work of our mobile,
11 - Proceed to copy all the files used by the user, just music, videos, apps, but no rom folder or file above (android_secure ...) , after performing this step, restart the phone, and go.
12 - We have our minicm7 running, fast, stable and impressive performance.
in attachment, there is the version with ready to modify BBcode
Click to expand...
Click to collapse
very good friend, is very good correction and a little easier to understand, I hope greetings for users to be of great help,
is better to perform these steps before commenting, whatever that if the slow, performance, and others.
ok
so :
a few correction added to the previous version
__________________________
IMPORTANT GUIDE FOR USERS WITH PERFORMANCE PROBLEMS.
using MiniCM7 by nobodyAtall
before commenting or asking about, lags, slowness or anything else, try theses steps, they could really solve all that
1 - Latest 2.1.1.A.0.6/2.1.1.C.0.0 SE firmware / Baseband: 53,404,015 M76XX-TSNCJOLYM-
(you should know that since you read miniCM7 thread's first post )
[*]2-Having the unlocked bootloader
3 - download the all in one package (ROM+kernel) by nobodyatall
4 - Backup all files of your micro sd on the PC, because it will be formatted to perform the installation.
[*]5- format your microSD (using the phone option OR sd card formatter which is better than windows's formatter)
6 - Enter flash mode, and proceed to flash the last nAa kernel (nAa05 for miniCM7-2.1.3).
7 - Disconnect the PC mobile phones and switch it on. As nAa logo appears, repeatedly press the Back button to enter recovery mode.
- Then we enter the recovery mode, connect your phone to your pc, and CWM options, we look in advanced options, mounting usb.
- Pc, we detect the micro sd in our mobile, we proceed to format it, then copy the zip file renamed to update, and google apps.
--> theses two steps are in case you couldn't format before
8 - Disconnect the PC mobile phones, we enter the initial menu of CWM,
- Select 'Backup and Restore -> Backup'
- Select 'wipe data / factory reset' (Suggested)
- Select 'apply update from sdcard'
- Flash GAPPS​
Reboot (The first boot will take approximately 3 minutes)
9 - After installing the rom, no clean junk files, previous rom conflict with minicm7 performance, and we have no real work of our mobile,
10 - Proceed to copy all the files used by the user, just music, videos, apps, but no rom folder or file above (android_secure ...) , after performing this step, restart the phone, and go.
11 - We now have our minicm7 running, fast, stable and with impressive performances.
__________________
now you can edit your first post, with this or a modified version of this guide using the following attachment
and then i'll link it in the FAQ 3d post (because all credits go to you since you had the idea and made it )
solution
Fixed several issues with respect to performance thanks to this guide, I thought it would not be achieved, solutions.
ronaldvalles said:
Fixed several issues with respect to performance thanks to this guide, I thought it would not be achieved, solutions.
Click to expand...
Click to collapse
Minicm7 what the 2.1.3 update to 2.1.4, but I had problems with Lagui, solved,
Thanks
It works very well!! miniCM7.1.5 is very laggy in my phone, but I follow the instructions in this post and now the permormance is AMAZING!! Thanks bróder!!
DarkestPriest said:
It works very well!! miniCM7.1.5 is very laggy in my phone, but I follow the instructions in this post and now the permormance is AMAZING!! Thanks bróder!!
Click to expand...
Click to collapse
greetings remember that we are to improve our minis do not worsen, greetings,
how do i know if i have performance issues, launcher was a little bit laggy, but i just installed v6 supercharger which solved this too
im only updating without factory restet/full wipe since something like mini cm 7.0 rc (edit: to be more specific i think it was miniCM7-2.0/CM7.1 port) , im not sure, maybe there is some benchmark so i can check if its too slow, or could be faster than now at least. In my opionion its pretty fast already, but maybe i only think it is fast
edit. im using nAa-06 kernel with minicm7-2.1.4
Abudinka said:
how do i know if i have performance issues, launcher was a little bit laggy, but i just installed v6 supercharger which solved this too
im only updating without factory restet/full wipe since something like mini cm 7.0 rc (edit: to be more specific i think it was miniCM7-2.0/CM7.1 port) , im not sure, maybe there is some benchmark so i can check if its too slow, or could be faster than now at least. In my opionion its pretty fast already, but maybe i only think it is fast
edit. im using nAa-06 kernel with minicm7-2.1.4
Click to expand...
Click to collapse
greetings friend this is for those who have problems with slow, but if you think your rom is stable so good but stability will mean superchanger unused v6 or other tricks, the perfect rom does not use performance tricks
ronaldvalles said:
greetings friend this is for those who have problems with slow, but if you think your rom is stable so good but stability will mean superchanger unused v6 or other tricks, the perfect rom does not use performance tricks
Click to expand...
Click to collapse
as im from germany i don't think i really got your point. As i said im using minicm7 for quite some time, usually overclocked at 710 MHz, which includes undervolting as far as i know. I had stabilty issuses using 729 MHz so i reduced it again and have may 1 crash since than, but i think it was caused by the usb conenction to a friends pc. You mean i should run very fast without v6 supercharger? even when pushing the home button to return to home screen? that was the moment it was a bit laggy.
So all in all i have no stability issues in every day life, im just not sure if my phone runs as fast as it should with this rom. as i said i would like to compare my perfomance in some way (like a video from one of u guys or a benchmark)
i also dont know, if i need a factory wipe when im going to upgrade to 2.1.5 or if i only need it when i get stability issues

[DEV][BETA][PREVIEW] TWRP 2.2 Recovery for NT

Team Win Recovery Project 2.2, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG (for 2.2.0):
- On-screen keyboard in recovery! -- supports long press, backspace repeat, and swipe left deletes everything left of the cursor
- Name new backups and rename existing backups
- Rename files and folders in the file manager
- Pseudo-terminal emulator
- Support decrypting an encrypted data partition on Galaxy Nexus (enter password using keyboard)
- Backup archive splitting -- allows backup and restore of data partitions larger than 2GB
- Simplified XML layout support between resolutions
- Added dual storage selection radio buttons to zip install, backup, and restore pages
- Improved zip install compatibility
- Updated update-binary source code
- Numerous small bug fixes and improvements
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
You can find more information and download links on our website!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 30 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
ORIGINAL POST (from May):
This is a work in progress.
TWRP (Team Win Recovery Project) 2.1 by TeamWin is an alternative recovery (instead of ClockworkMod) that is a good companion for Goo Manager. See this video for more info.
This is an experimental, mostly untested build of TWRP2 for entertainment purposes only. USE OR ATTEMPT TO USE ENTIRELY AT YOUR OWN RISK. It is intended for those who are willing to risk any and all damage, loss, and STD infection to their hardware, data, person, and associates resulting from this software. Do not attempt to use unless you understand and accept these risks.
Please note this is using the still-being-developed 3.x kernel.
I am including the raw .imgs which can be fastbooted or used on an SD (rename recovery.img.sdcard to recovery.img and put on SD in place of the existing version). Which I don't recommend doing of course, given the disclaimer above. Remember I don't have an NT so I haven't run this... ever.
Finally, this has not at all been put through any kind of paces. That's for you, assuming all the risks, to do. And report it back here for everyone's benefit.
Thanks to dees_troy, eyeballer and demetris_I & frustro for testing this. I'm busy the next few days, so I'm volunteering demetris_I, who has it running, to answer anyone's questions per his availability
twrp-2.1-nt-2012-05-17E-fullofbugs.tar.gz
History
6/12/12 - updated first post.. No binaries yet.. Can someone make one?
5/17 -
Updated 3.0 kernel to support new 512GB NTs (untested)
Updated twrp codebase to latest
Newer cm9 stuff as well
5/17B&C
Use cmdline from u-boot.bin to determine max ram size.
fix device showing up as "B" to "NookTablet"
5/17D&E
I can't remember. But it's betterer.
Has anyone successfully flashed this yet? And can anyone offer up the steps in a more-in-depth way?
Sent from my Team A CM9 Alpha 0.03 Nook Tablet
Well... there's always update.zip
I haven't tried it, but I'm guessing if you've installed fastboot to your computer, this should work:
1. boot into cyanoboot and choose Fastboot from the menu.
2. On your computer, navigate to where recovery.img is and enter into the terminal
fastboot flash recovery recovery.img
Or... maybe someone could whip up a quick update-twrp2-nt-2012-5-14.zip maybe?
I guess that someone might as well be me. This is intended for use with an existing cwm recovery. This will flash to emmc...maybe.
update-twrp-2.1-nt-2012-05-14-fullofbugs-emmc.zip
MD5: 337269fa77017150325d398216a6dd3c
Thoroughly and completely untested. I really don't know if it will even install, and if it does, if it will work. See all disclaimers above, plus make up some additional ones yourself.
Edit: See below about a possible issue with possible difficulties accessing the external SD card. Internal /emmc seems to work consistently. Looking into it, but if you want to help debug this, that would be much appreciated. Just knowing what works or doesn't work and log samples (dmesg via adb) would be great.
Will this completely replace CWM as the recovery? Or will it run alongside. Anything else I should be aware if before I try to flash (do it on a fresh rom install, will I be able to restore from a backup if something goes wrong etc etc...)
Sent from my Team A CM9 Alpha 0.03 Nook Tablet
It will replace cwm.
Rom doesnt matter , they reside in different partitions.
Cyanoboot is all you want if anything goes wrong or/and CWM/TWRP from sd card so you can dd the recovery.
SilentStormer said:
Will this completely replace CWM as the recovery? Or will it run alongside. Anything else I should be aware if before I try to flash (do it on a fresh rom install, will I be able to restore from a backup if something goes wrong etc etc...)
Sent from my Team A CM9 Alpha 0.03 Nook Tablet
Click to expand...
Click to collapse
Should replace it completely. I say should because if you do this with the update.zip, you will be the first one to try it.
Oh, Mister_Argent is trying it on IRC...
The Zip seems to work! Android boots fine, and it's entirely possible to get into TWRP via Cyanoboot. This might just be me, but the terminal seems to lock up...
Oh hey argent, so the zip works? And is it worth my time to change from CWM to TWRP?
Sent from my Team A CM9 Alpha 0.03 Nook Tablet
SilentStormer said:
Oh hey argent, so the zip works? And is it worth my time to change from CWM to TWRP?
Sent from my Team A CM9 Alpha 0.03 Nook Tablet
Click to expand...
Click to collapse
There may be issues with selecting the external SD card... not sure what the deal is. I believe demetris_I checked this out previously, but you can use the internal (/emmc) one though until this is worked out/confirmed one way or the other.
Note: if anyone is good at verifying/debugging, post any relavent dmesg stuff + what your theory is on the issue
So we can still flash stuff through emmc?
Sent from my Team A CM9 Alpha 0.03 Nook Tablet
Indirect gave me this command to flash recovery via terminal emulator and it worked out nicely
dd if=/recovery.img of=/dev/block/mmcblk0p3
Click to expand...
Click to collapse
where "/recovery.img" is the file path/file name of the recovery image
Recovery looks nice. I'll do some more playing with it later when I have time.
fattire said:
There may be issues with selecting the external SD card... not sure what the deal is. I believe demetris_I checked this out previously, but you can use the internal (/emmc) one though until this is worked out/confirmed one way or the other.
Note: if anyone is good at verifying/debugging, post any relavent dmesg stuff + what your theory is on the issue
Click to expand...
Click to collapse
No issues with external sd it just take some seconds to mount, is not instant but it will mount.
8gb NT. Successfully flashed internally; will test, log and provide feedback on any issues.
The zip file name is overly long and CWM doesn't like it. Renaming to something shorter solves the issue.
In my experience with other android devices, it is normally recommended you wipe 'dalvik cache' whenever changing / updating kernel. Perhaps this step will avoid some issues for people.
Edit: Flashing gapps update via Goo Manager results in failure of rom to load after Cyanoboot screen. I did not choose to wipe dalvik / cache in Goo Manager. Also unable to access Cyanoboot via N. Screen appears but does not seem to respond and automatically boots emmc (blank screen).
Re-download Gapps and press the buttons combo to access twrp/cwm and reflash (power+N)
What rom and what gapps you are using?
Make sure they are downloaded ok before flashing.
demetris_I said:
Re-download Gapps and press the buttons combo to access twrp/cwm and reflash (power+N)
What rom and what gapps you are using?
Make sure they are downloaded ok before flashing.
Click to expand...
Click to collapse
I could not access twrp as already stated, because Cyanoboot did not respond to button press. I've managed to get access to CWM via sdcard and reflashed another gapps. CM9 still will not load.
Next, I plan to wipe everything and flash CM9 anew.
Edit: Still won't boot. Looks like I have a brick to fix.
Edit2: Flashing CWM internally got everything working again. Cyanoboot would previously go automatically to loading from emmc; there was no delay / opportunity to press N to access the menu. Now the delay occurs and I have access. CM9 also loads.
Edit3: Reflashed TWRP internally again. It's not working on 8gb NT. It doesn't break Cyanoboot or prevent CM9 from loading, but any attempt to load TWRP results in a black screen.
How do you flash twrp?
If you flash the zip can you please try the fastboot way?
fastboot flash recovery twrp.img, thanks
demetris_I said:
How do you flash twrp?
If you flash the zip can you please try the fastboot way?
fastboot flash recovery twrp.img, thanks
Click to expand...
Click to collapse
I flashed the above emmc zip via cwm internal
I have adb working, however fastboot seems to require a separate driver to work in windows. I've searched the forum and have not found a clear answer.
I'm guessing the 3.0 kernel doesn't have support added for the 8gb nts yet. I guess maybe I could look into that...
Sent from my HTC Vision using XDA
So to run this I have to be running the new 3.x kernel? Or can I just flash the zip if I'm on the 2.x Cm9
(16gb Tablet)
Sent from my Team A CM9 Alpha 0.03 Nook Tablet
SilentStormer said:
So to run this I have to be running the new 3.x kernel? Or can I just flash the zip if I'm on the 2.x Cm9
(16gb Tablet)
Sent from my Team A CM9 Alpha 0.03 Nook Tablet
Click to expand...
Click to collapse
Recovery is separate from the rom. You'll be fine. I have it running on my 16GB.

Want to move to CM11 .. Help

I am currently on 4.1.2 10-20121209-UNOFFICAL-acclaim ROM
I want to move to CM 11.
My current recovery is CWM - Recovery v6.0.1.9
ON all CM 11 page , it says to update my recovery to new one through fastboot.
I am not sure how to do this on nook tablet. Can anyone help me ?
Also does repartitioning of 16Gb needs to done with each rom install or once done , it stays the same through out ?
naveen_reloaded said:
I am currently on 4.1.2 10-20121209-UNOFFICAL-acclaim ROM
I want to move to CM 11.
My current recovery is CWM - Recovery v6.0.1.9
ON all CM 11 page , it says to update my recovery to new one through fastboot.
I am not sure how to do this on nook tablet. Can anyone help me ?
Also does repartitioning of 16Gb needs to done with each rom install or once done , it stays the same through out ?
Click to expand...
Click to collapse
Hi, repartitioning doesnt need to be done with a new rom install.
IF THIS IS A CLEAN INSTALL
you dont HAVE to install it through flashing a new recovery using fastboot
you just need a working newer CWM , or a working TWRP that you can boot
if you can boot to an older Clockwordmod recovery in any form, you can flash a newer version of CWM to the internal by using a zip file , this user has a couple of the newest ones hosted here:
newbtrigger69 said:
https://www.mediafire.com/folder/3j4kxa3bwkrs1/CLOCKWORKMODS <--------------------------------------------- my compilation of a few important CWM versions in case u dont like twrp (like me).
Click to expand...
Click to collapse
after you flash the new recovery, remove the SDcard, power completely down,
press and hold the "N" NOOK button, and hold the power button for just a second or 2 after you see the tablet boot, and you should be prompted for the new recovery that you just flashed.
---
the newer recoveries have an option on the boot menu to start fastboot. So, if you really wanted to follow the instructions to the letter, get or make a working sd card of a newer CWM recovery, boot to it, then as long as your adb/utilities folder on your PC has fastboot in it, you can fastboot the recovery-0.2.img as is in the cm11 thread.
I found I never had to use fastboot before this cm11 install , so I didnt even have the fastboot on my pc side and had to hunt it down.
my first several installs of CM11 were done using an older boot sdcard that had TWRP recovery on it and it works fine.
----
it will probably be a lot easier it you have a working tablet, to have the copied the zips for cm11 and the gapps you want to install to the tablets
internal memory first, before flashing the new recovery internally
---------- (I completely forgot this other possibility, I'm always just doing clean installs)
IF YOU WANT CM to automatically upgrade though the CM updater process on a running CM10
then , yes you need the newer recovery, and it probably is best if it is the recovery-0.2.img the developer posted in the CM11 thread.
I've never tried it so I dont know how well it migrates your "stuff" from CM10 to CM11
theres a lot of changes to the way storage is mounted in CM11 , and the CM updating process is an important thing they are trying to make as seamless as possible.
If theres stuff on the tablet you really need, I'd save it first before doing any kind of major upgrade like this.
Thanks. I might do a clean install itself. I dont have much stuff.
Actually i am moving to CM 11 in hope that it would be faster. Currently i cant rad the PDF on thios tablet. The scrolling is very stuttery.. gives me headache. If that too doesnt solve that issue , i might simply sell this one and get some nexus tablet.
I just need a tablet to read my study books.
naveen_reloaded said:
Thanks. I might do a clean install itself. I dont have much stuff.
Actually i am moving to CM 11 in hope that it would be faster. Currently i cant rad the PDF on thios tablet. The scrolling is very stuttery.. gives me headache. If that too doesnt solve that issue , i might simply sell this one and get some nexus tablet.
I just need a tablet to read my study books.
Click to expand...
Click to collapse
the latest nightlies of CM11 on a 16GB tablet (has 1GB RAM) are fantastic. best thing ever, especially if you replace the kernel with one that user:demetris has supplied.
I havent run the CM11 on an 8GB (512MB RAM) tablet yet, but it really is a good package.
Its kinda like when Windows 7 came out, its what should have been released instead of XP or Windows 98, its really, really good.
Just tell me .. is flashing recovery via fastboot is same for all devices or for nook tablet its different. Also i need a SD card to do this ?
Can you help me how to flash recovery via fastboot for our nook tablet ?
naveen_reloaded said:
Just tell me .. is flashing recovery via fastboot is same for all devices or for nook tablet its different. Also i need a SD card to do this ?
Can you help me how to flash recovery via fastboot for our nook tablet ?
Click to expand...
Click to collapse
hmmm...
Ive seen fastboot on other devices, Kindle Fires, which I think have a motherboard thats a close match to the NOOK tablet.
on the Kindle, you can force fastboot by using a special cable.
if you need fastboot on the NOOK, the recovery program that you execute at boot has to have the option to start fastboot.
you can boot a recovery that has that option from an internal recovery (CWM newer versions have it, I dont remember about older versions)
or you can boot from an SD card you make that boots a CWM recovery
in any scenario, for fastboot to work, you need a working ADB setup and the fastboot program on your PC
------
you can completely install CM11 without replacing the internal recovery partition of your NOOK which is what that fastboot instruction is trying to get you to do.
the special internal recovery, as I understand it, is only for compatability with the automated CM updating process.
you can boot from an SD card that has CWM 6.0.4.x , or TWRP , and as long as the CM 11 nightly is on the SDcard too, or in the NOOK internal memory, you can flash it.
I am more confused
can you take me step by step or link me to a relevant thread ?
I am sorry if i am taking your time ..
naveen_reloaded said:
I am more confused
can you take me step by step or link me to a relevant thread ?
I am sorry if i am taking your time ..
Click to expand...
Click to collapse
--------- assuming you want to update your NOOK's INTERNAL software, and not run CM11 from an SDcard
I apologize had wrong file linked first post
this zip file should be flashable through your current CWM (6MB)
http://www.mediafire.com/download/0f5fjkjvxp1hga0/flashable_CWM_6.0.4.5(2).zip
http://forum.xda-developers.com/showpost.php?p=48855275&postcount=2
it should update your internal recovery to cwm 6.0.4.5
then you should be able to flash the CM11 nightly and gapps without error
--------------------------
a different (I think slightly more dangerous) way to load the newer recovey to your internal was posted here:
http://forum.xda-developers.com/showpost.php?p=48317620&postcount=15
get the newest recovery image file -
File: http://goo.im/devs/chrmhoffmann/cm-11.0/acclaim/recovery-0.2.img
md5sum: e2a87c433171b3d97d852d27aea1ff49
-------
You can install it from a terminal emulator, if you want to.
1. Download the cwm-recovery.img file referenced in the first post of the thread.
2. Copy this file to the internal memory of your Nook Tablet. Rename this file to cwm.img.
3. On your Nook Tablet, launch Android Terminal Emulator (ATE).
4. In ATE, type in 'su' [ENTER]. Grant it access when prompted.
5. In ATE, type in 'cd /emmc' [ENTER]. This will change your file system current directory to /emmc, which corresponds to the internal storage drive.
6. In ATE, type in 'ls' [ENTER]. This will list the contents of the /emmc directory. You should see the cwm.img file you copied over and renamed earlier (step 2).
7. In ATE, type in 'dd if=/emmc/cwm.img of=/dev/block/mmcblk0p3' [ENTER]. This will write the contents of the cwm.img file to partition 3 of device mmcblk0 (internal memory).
You should now be able to reboot and use cwm. CAREFUL, as you could brick your device if you get step 7 wrong.
nvm
@mikeataol
It worked perfectly. Just flashed it and it udpated to lastest CWM.
Installed CM 11 and got GApps and installed them too. Now downloading some PDF apps to see if they work smoothly and no stuttering is there.
In CM 11 , there is no option for "reboot to recovery" , why so ? I had to use cnyaboot option to enter into recovery.
naveen_reloaded said:
@mikeataol
It worked perfectly. Just flashed it and it udpated to lastest CWM.
Installed CM 11 and got GApps and installed them too. Now downloading some PDF apps to see if they work smoothly and no stuttering is there.
In CM 11 , there is no option for "reboot to recovery" , why so ? I had to use cnyaboot option to enter into recovery.
Click to expand...
Click to collapse
Great!
re: reboot recovery
you have to unlock developer options first by going into
Settings/ About Tablet / Build Number
and tapping the "build number" field 7 times.
then you see a new settings group "developer options",
and in there is advanced reboot and other things.
---------- Post added at 04:24 AM ---------- Previous post was at 04:21 AM ----------
are you on an 8GB / 512 MB ram, or a 16GB 1GB RAM Nook tablet?
Lol , just found that reboot to recovery , came here to say i found , you already replied.
Installing bexus kernel.
Thanks a lot for your help.
One thing though. The scroll stuttering issue is there . Its as if the screen refresh rate or frames per second is not upto the mark , scrolling is very stuttering.
Is there any way to increase or solve this issue ? Please
this is killing the whole tablet and the purpose i want to use this tablet .. ie to read books.
I use 16Gb/1GB tablet
ok ran into issue
After flashing gapps and installing kernel , i am stuck with andoid.phone stopped working error as soon as the tablet boots.
What is the gapps to be used for CM 11 on tablet and is bexus interfering with the gapps ?
how to enable multi touch ?
Also i think there is a serious problem with the screen/display. There is considerable lag and its not smooth scrolling. Its very stuttery...
naveen_reloaded said:
how to enable multi touch ?
Also i think there is a serious problem with the screen/display. There is considerable lag and its not smooth scrolling. Its very stuttery...
Click to expand...
Click to collapse
I would not enable the multi touch, thats just asking for even more trouble.
I think you should consider a total re wipe , and start over
on a 16GB Nook Tablet, the nightly just by itself should run fine
i just downloaded and opened a 71mb pdf file with no issues whatsoever
opens in Adobe reader just fine, scrolling and zooming and searching is perfectly acceptable, nothing I would describe as a stutter
----
if you HAD enabled the multi touch while you were on CM10, I'd consider reflashing the stock LCD firmware before you put CM11 back on it
yeah flashed thrice and i have witheld flashing bexus kernel for time being.
Stutter in the way , the refresh rate is not upto the mark
To best see this issue , dont swipe a text/pdf fast , do it slowly then you will see the jerkiness and also a lag between your swiping and actual screen change.
LCD firmware ? where to get it ?
naveen_reloaded said:
yeah flashed thrice and i have witheld flashing bexus kernel for time being.
Stutter in the way , the refresh rate is not upto the mark
To best see this issue , dont swipe a text/pdf fast , do it slowly then you will see the jerkiness and also a lag between your swiping and actual screen change.
LCD firmware ? where to get it ?
Click to expand...
Click to collapse
to me, seeing a white page while adobe pdf loads the next buffer of pages several pagesahead is normal
I dont see anything abnormal while swiping slowly
re: LCD firmware
if you were on CM10, and fashed the 10 point LCD firmware, then I think you would need to rebuild the unit back to CM10, and reflash the stock LCD firmware.
I dont know how to explain , but look carefully when scrolling (slowly) , you will see tests stuttering as its been scrolled .
I am on CM 11 , do you want me to go to CM 10 ? and flash that firmware?
https://play.google.com/store/apps/details?id=com.aatt.fpsm&hl=en
Used this app and saw that fps varies and it varies like from 7 - 50 during reading pdf.
On slow scrolling of pdf , it only shows 11 or so fps , which is why i think shows the stuttering effect
Used the same app on my GS3 to see the difference and it holds its FPS at 60+ and not dropping below 50.
I think if i can make this tablet to render everything at 30+ fps i might not feel this stuttering effect.
Which PDF reader are you using?
I don't have any stuttering issue on the Mantano Reader.

[FBOOT][MULTIROM] FOTA -Noob edition

I worked a bit on FOTA bootloader, and i'd like to share some of my work.
Few words about Fota in general
I think lot of people here don't understand fully how Fota work, and this may prevent a lot of questions, please read it.
We use Fota in Badadroid project as a bootloader, it's the piece of code loading modem and android kernel in RAM, and starting android kernel.
Fota decide what key combination does, which system is to be launched if no key are pressed, and where kernel file is searched.
Fota doesn't care if a kernel is Nand or SD or Loop. It just search for a file with a certain name, load it and launch the execution of its code.
This Fota is compatible with ALL roms and ALL versions (nand, SD, loop).
About keys : power key isn't important for Fota, the only function power key have is to power on the device. Once device is powered on (you can use power key but also plug charger or use reboot function), fota will check for other keys. So if i write "Recovery mode : home key", you'll have to press home key and then manage to power on the device, it won't boot if you just press home key.
About this Fota
This Fota is able to load two different kernel. It can be used to load two rom (one Nand and one SD, one Loop and one SD) or if you have a "test" kernel.
If you have only one rom or one kernel, no problem, it will work the same, all the stuff related to second kernel won't work, that's all.
This Fota doesn't allow two Nand rom or two SD rom.
This Fota provide a default "Silent boot" displaying default Bada bootscreen (no more ugly ASCII), however boot is slow so it will be displayed for maybe 15 seconds. If there is an error with kernel, ugly ASCII will appear and tell you there is something wrong.
This Fota also provide an "interactive" mode (or Noob mode). If you press any keys during boot (home, call or volume), it will boot in interactive mode. It's simple and you'll understand fast how it work. Control are vol + and vol - and home key to select.
It also support usual key combination, if you press keys to boot recovery, and when white screen appear you stop pressing, it will boot "interactive mode" and after few seconds boot recovery IF no keys are pressed. If you press sth at this moment, interactive mode will be active.
Test it, you'll understand.
This Fota also boot faster in recovery (no Modem init, who need modem in recovery ?)
However, battery reading won't work anymore in recovery because of that, so don't spend hours in recovery mode.
README
First kernel : boot.img on SDcard
Second kernel : boot_2.img on SDcard
Boot 1st kernel : default
Boot recovery 1st kernel : vol up
Boot 2nd kernel : home
Boot recovery 2nd kernel : vol up + home
Boot bada : call
Yeah, you read well, kernel must be named boot.img and not zImage.
If your rom came with a file named zImage, just rename it boot.img it will work the same. I could have chosen to load a file named MyLittleKernel. Name doesn't matter, only file content is important.
And all the same, rename the second kernel (for your secondary rom, test kernel...) boot_2.img.
All the kernels must be placed on SDCARD
REQUIREMENTS
Bada 2.0
Android Bootfiles (if you have an android rom on your phone, you have it, else, see in badadroid thread to download it.
Bugs
Bada boot doesn't work in interactive mode, it's stuck after Bada bootanimation, maybe someone know why.
Just boot with call key pressed to boot bada.
Please report if there is any other bugs.
Thanks
Big thanks to all Fota contributors, Rebellos, Mijoma, Tigrouzen, ihavenick, Volk204 and all the others i forgot
Sources
My github here, see branch sd.
Downloads
Fixed dual boot broken by little mistake (20/07/2014) :
Mega (s8500 & s8530)
Alternative links :Google Drive
Just flash it with Multiloader
WoW.. Awesome BenzoX.. Congrats for ur work.. Thank u so much..
Regards,
Abhijeet....
Any other links other than mega..??
abhijeet1331 said:
Any other links other than mega..??
Click to expand...
Click to collapse
Updated (Google Drive)
BenzoX said:
Updated (Google Drive)
Click to expand...
Click to collapse
Oh thanks man..
Duude.
Bada+ Android LOOP + Android on SD - It work
Thaaankss
bada is not booting ..
is it possible to boot only bada by using this fota in s8530 ??
when i try to boot bada using press call button ...it won't boot
if it's work then i will boot also android ....but i need bada.
any suggestion...plz
thanks in advanced..
mishail said:
is it possible to boot only bada by using this fota in s8530 ??
when i try to boot bada using press call button ...it won't boot
if it's work then i will boot also android ....but i need bada.
any suggestion...plz
thanks in advanced..
Click to expand...
Click to collapse
For me bada boot work well if i press call key. Not from menu (i have s8530 too).
bada not boot proper
BenzoX said:
For me bada boot work well if i press call key. Not from menu (i have s8530 too).
Click to expand...
Click to collapse
Hi , Benzox
when i boot bada , screen display horrible line with different color (like my bada is crashed).
is it booting normal ??. what should i do. I am using CFW 10.1 Turko
thanks for giving answer ..
mishail said:
Hi , Benzox
when i boot bada , screen display horrible line with different color (like my bada is crashed).
it's booting normal. what should i do.
thanks for giving answer ..
Click to expand...
Click to collapse
I think that's because you have/had a Nand rom installed. Just flash bada (not Fota file) and it will work (you'll loose your nand rom thought)
bada is not booting.
BenzoX said:
I think that's because you have/had a Nand rom installed. Just flash bada (not Fota file) and it will work (you'll loose your nand rom thought)
Click to expand...
Click to collapse
Hi Benzox ,
When u write about this fota like " It can be used to load two rom (one Nand and one SD, one Loop and one SD)" .
So i thought i boot two OS ( bada & nand ) while flash my bada 2.0 with this new fota file.
is it not possible to load Nand & Bada alternative ?
Thanks in advanced.
mishail said:
Hi Benzox ,
When u write about this fota like " It can be used to load two rom (one Nand and one SD, one Loop and one SD)" .
So i thought i boot two OS ( bada & nand ) while flash my bada 2.0 with this new fota file.
is it not possible to load Nand & Bada alternative ?
Thanks in advanced.
Click to expand...
Click to collapse
Nand format and install on nand memory, bada is installed on nand memory...
You need Loop rom (such as badadroid) if you want both to be on internal. memory.
I can allow two kernel but i don't know how to make partitions and storage space appear from nowhere
Questions ...
I want to install two android roms NAND and SD
What do I install first nand ram or rom SD?
The reason for my question is that when a rom on the SD card installed to do partition SD and lost all the contents of the SD.
If installation nand rom first
And after install the second rom in sd
Does the second rom could not delete the first installation nand?
I want to install nand rom and sd rom but not in what order I have to do
I do not want a rom overwrite the other rom because the two are installed in the SD
tofifo said:
Questions ...
I want to install two android roms NAND and SD
What do I install first nand ram or rom SD?
The reason for my question is that when a rom on the SD card installed to do partition SD and lost all the contents of the SD.
If installation nand rom first
And after install the second rom in sd
Does the second rom could not delete the first installation nand?
I want to install nand rom and sd rom but not in what order I have to do
I do not want a rom overwrite the other rom because the two are installed in the SD
Click to expand...
Click to collapse
Nand rom partition Nand (and delete it's content)
SD rom partition SDcard (and delete its content)
A nand rom will never overwrite a SD rom and vice versa, whatever fota you use.
Order doesn't matter.
Of course if you do Nand rom first you'll have to put its kernel on SD again.
You can't install two rom on SD, nand rom is installed on nand (internal memory) and sd rom is installed on SD.
Only kernel is on SD for both rom.
@BenzoX i forgot your codes but if you want to boot from interactive mode to bada mode i remember you must turn on mmu and disable modem (its opens again )
ihavenick said:
@BenzoX i forgot your codes but if you want to boot from interactive mode to bada mode i remember you must turn on mmu and disable modem (its opens again )
Click to expand...
Click to collapse
But in my code Modem init and mmu is called only after the "return rm_BL3 (which is the signal to start bada if i understood well)
Only thing made from the start of Fota.c are
Code:
int mmuctrl = MemMMUCacheEnable(gMMUL1PageTable, 1);
disp_FOTA_Init();
__PfsNandInit();
__PfsMassInit();
MemoryCardMount();
Rest is only displaying and setting some variable used only in Fota.c
I must be doing something wrong
If I knew cuel is my error.... not would have error haha
I installed a rom sd using the SD kernel.
I installed a rom nand using the nand kernel.
But the fota of menu always starts the same rom both when select kernel 1 o when select kernel 2
I have noticed one thing, we make a sd installation or nand installation the folder Android always appears on the sd card.
I see it almost impossible to install two android roms even if one is nand and the other sd because the folder Android always overwrite rom to another rom
tofifo said:
I must be doing something wrong
If I knew cuel is my error.... not would have error haha
I installed a rom sd using the SD kernel.
I installed a rom nand using the nand kernel.
But the fota of menu always starts the same rom both when select kernel 1 o when select kernel 2
I have noticed one thing, we make a sd installation or nand installation the folder Android always appears on the sd card.
I see it almost impossible to install two android roms even if one is nand and the other sd because the folder Android always overwrite rom to another rom
Click to expand...
Click to collapse
If it start the same rom, it's a kernel for same type (SD/Nand)
Take your kernel for SD and name it boot.img, take your kernel for Nand and name it boot_2.img (or vice versa). Put both on sdcard.
I'll test again my Fota but i'm almost sure it work (i did small modification and haven't tested both boot, but it should work)
This folder is not "essential" and distinctive to both rom.
Only issue may be if you have different version of the same apps on both rom, or if you use same apps on both rom. In this case (and only IF apps data are stored on SD, which is a minority), thing may be a bit confused.
nice.. good job.. this is what im waiting for.. something that will replace ugly ASCII on boot.. got some questions though,.
i have bada installed with sd rom and sd kernel installed on a partitioned sd card.. so my questions are..
1) can i install 3 OS?.. 1 bada(call) on nand, 1 android sd (end) and 1 android nand/loop (middle) on nand again?..
2) so if i put ALL kernels in sdcard by just renaming it.. what about the 2 roms, both in sd card as well?.. how will it know which rom the kernel will boot if same on sd card?
3) how long does the new boot take?.. can u show some screenshot or video?
4) what rom and kernel are u currently using?
again.. thank u for this fota!
BenzoX said:
If it start the same rom, it's a kernel for same type (SD/Nand)
Take your kernel for SD and name it boot.img, take your kernel for Nand and name it boot_2.img (or vice versa). Put both on sdcard.
I'll test again my Fota but i'm almost sure it work (i did small modification and haven't tested both boot, but it should work)
This folder is not "essential" and distinctive to both rom.
Only issue may be if you have different version of the same apps on both rom, or if you use same apps on both rom. In this case (and only IF apps data are stored on SD, which is a minority), thing may be a bit confused.
Click to expand...
Click to collapse
I've the 2 kernels renamed boot.img and boot_2.img
But I noticed that only detects one of the kernels
When you start the menu fota options
KERNEL 1
KERNEL 2
No matter which you select because it always opens the same kernel
Do not know if that will be a mistake, it's a question is not affirmation

[Q] Archos 10.1 (gen8) update to android 4.4?

Hello guys,
Is there a possibility to update the "archos 10.1 (gen8)"
from android froyo 2.2 to android 4.4??
And if it is possible would it be worth it to do that ?
Will speed and so increase the tablet?
Greetings Avanox
Absolutely not.
Mavasilisk said:
Absolutely not.
Click to expand...
Click to collapse
Hello again, thank you for your reply.
And not possible to install another version that's higher than 2.2 on that tablet?
Greetings Avanox
Avanox said:
Hello again, thank you for your reply.
And not possible to install another version that's higher than 2.2 on that tablet?
Greetings Avanox
Click to expand...
Click to collapse
2.3 or 4.0 but that's the highest u can go, did u even have a look in the gen8 android development section?
Ranomez said:
2.3 or 4.0 but that's the highest u can go, did u even have a look in the gen8 android development section?
Click to expand...
Click to collapse
Waw great. Thanks for the information.
Yes I did check this section but probably not good enough.
Avanox said:
Waw great. Thanks for the information.
Yes I did check this section but probably not good enough.
Click to expand...
Click to collapse
Here is the link to ICS (4.0.x): http://forum.xda-developers.com/showthread.php?t=1941377
And here is the link to GB (2.3.x): http://dev.openaos.org/wiki/AndroidInstall_CM7_Gingerbread (there is also a thread on this forum)
Unfortunately the openaos site seems to be down right now (was up in the morning and last night when I answered you) but anyway I did find cm9 (ics) to be more stable and "usable" (less bugs than actually affect usability) than cm7 (gb) although no doubt quite a bit slower than cm7, but again that's me that has at least 300 apps installed on each android device and that goes back to since I had a HTC Touch Pro 2 and turned it from an windows mobile device to an android one and the specs on that were way lower than the ones on the gen8.
Also feel free to ask any questions you may have related to our gen8 tablets, I am one of the "lost souls" still using this tablet and I can say that judging by the fact that I bought this quite soon after it was released (at least in my country) I can say it has served me well since then and I still think it is a decent device (although I do now have a much better and much more powerful tablet device too, my 101it is still a fun thing to play around with).
Hello again I will give it a try now.
Any idea where I can download the kernel ?
Because the download link doesn't work on the link you gave me for android 4.
I just posted for it.
Would you still have it or could you reupload this for me?
Would be awesome.
Greetings Avanox
Ranomez said:
Here is the link to ICS (4.0.x): http://forum.xda-developers.com/showthread.php?t=1941377
And here is the link to GB (2.3.x): http://dev.openaos.org/wiki/AndroidInstall_CM7_Gingerbread (there is also a thread on this forum)
Unfortunately the openaos site seems to be down right now (was up in the morning and last night when I answered you) but anyway I did find cm9 (ics) to be more stable and "usable" (less bugs than actually affect usability) than cm7 (gb) although no doubt quite a bit slower than cm7, but again that's me that has at least 300 apps installed on each android device and that goes back to since I had a HTC Touch Pro 2 and turned it from an windows mobile device to an android one and the specs on that were way lower than the ones on the gen8.
Also feel free to ask any questions you may have related to our gen8 tablets, I am one of the "lost souls" still using this tablet and I can say that judging by the fact that I bought this quite soon after it was released (at least in my country) I can say it has served me well since then and I still think it is a decent device (although I do now have a much better and much more powerful tablet device too, my 101it is still a fun thing to play around with).
Click to expand...
Click to collapse
Avanox said:
Hello again I will give it a try now.
Any idea where I can download the kernel ?
Because the download link doesn't work on the link you gave me for android 4.
I just posted for it.
Would you still have it or could you reupload this for me?
Would be awesome.
Greetings Avanox
Click to expand...
Click to collapse
The link that you are talking about that isn't working is the kernel source link (which is actually very unfortunate) and not the kernel itself, the kernel can be downloaded from the attachments of the first post in the thread (a zimage and the initramfs.cpio.gs files)
Hello again ,
I will set it on a row:
1. Cm9 image download (ok)
2. Initramfs.cpio.gz download (ok)
3. Kernel download
(which files are the kernel to download zimage and the initramfs.cpio.gs??)
I can't see a link to the zimage ?? Can you give me the correct link?
4. Data.img.tar.gz download (ok)
Install kernel by SDE menu
(ok I know how to get in the SDE menu but what steps I have to do there?)
Where to configure menu.Ist (is that the one I downloaded in the attachements downstairs?
What about the terminal ? How to enter the terminal to activate Bluetooth?
What is the swap configuration??
Ok and one last question, at the moment my Archos 10.1 gen8 is running on Urukdroid must I remove the sd card for this procedure and reinstall the SDE firmware or not?
Or is this method for cm9 (android4) not like urukdroid method??
Sorry for all my questions but I don’t want to make mistakes.
Greetings Avanox
Ranomez said:
The link that you are talking about that isn't working is the kernel source link (which is actually very unfortunate) and not the kernel itself, the kernel can be downloaded from the attachments of the first post in the thread (a zimage and the initramfs.cpio.gs files)
Click to expand...
Click to collapse
Avanox said:
Hello again ,
I will set it on a row:
1. Cm9 image download (ok)
2. Initramfs.cpio.gz download (ok)
3. Kernel download
(which files are the kernel to download zimage and the initramfs.cpio.gs??)
I can't see a link to the zimage ?? Can you give me the correct link?
4. Data.img.tar.gz download (ok)
Install kernel by SDE menu
(ok I know how to get in the SDE menu but what steps I have to do there?)
Where to configure menu.Ist (is that the one I downloaded in the attachements downstairs?
What about the terminal ? How to enter the terminal to activate Bluetooth?
What is the swap configuration??
Ok and one last question, at the moment my Archos 10.1 gen8 is running on Urukdroid must I remove the sd card for this procedure and reinstall the SDE firmware or not?
Or is this method for cm9 (android4) not like urukdroid method??
Sorry for all my questions but I don’t want to make mistakes.
Greetings Avanox
Click to expand...
Click to collapse
There are a few files starting with zImage, chose one of the 3 of them and rename it to just zImage (no extension and don't extract it although when youu will download it it is an archive, just rename it to zImage and I can't really tell you which one to choose cause I do not know which of the 3 will work best for you, I personally use the 35% one.
To flash it you will use the same procedure as for urukdorid but you will loose access to urukdroid, though you don't need to remove your card and also AFAIR the OpenAOS multi-boot menu does not have the ability to boot at tablet boot (or I am wrong, not sure) so you might have to reboot in recovery and run developer version each time you want to boot it.
You could also use kboot for even more multi-boot and being able to still use urukdroid, I think I posted a mirror for the files on it's thread, or at least I wanted to, if I didn't I will. BUT if you do want this first backup the urukdroid kenrel and initramfs, I can tell you how to do it if you intend to do this, if loosing access to urukdroid is ok for you then I'd say don't bother, uruk isn't that great, you can get the same things on stock after getting root on it, though I could still recommend using it as that's the only way to have rooted stock using the kernels here on the forums or being able to boot also GB and/or debian/bodhi/whatever other linux distro you fancy.
For the OpenAOS boot menu you indeed need to download that menu.lst and put it on the storage, it is already setup for booting CM9 so you don't really need to do much more here.
Swap is already configured so you don't really need to do anything about that or worry about it, it's just info and for the bluetooth I think terminal emulator comes preinstalled so you do the commands in there but I would recommend creating a bash script and downloading SManager from play store and using that to create a homescreen shortcut to your script (I could also share you my script if you would like later after I charge my archos.
Also there is no initramfs.cpio.gs that was a typo, it's actually .gz so you have the right file and the kernel is the zImage.
In the SDE menu just do the steps you did when you flashed urukdroid but only place the initramfs.cpio.gz and zImage without a 3rd file (if I remember correctly the steps for flashing urukdroid), I can't really tell you what steps to do in there as I don't really remember, it's something like go in the repair menu and click flash developer firmware or something along those lines I think.
EDIT: Also if you intend to edit the menu.lst file for whatever reason (if you want to use kboot to add the CM7 kernel and use that to boot CM7 and/or debian for example) don't use windows notepad, instead install notepad++.
Ok this makes some things clear to me
Yeah is also a long time ago urukdroid installing.
I found the guide from it but it seems idd similar to your explanation.
https://code.google.com/archive/p/urukdroid/wikis/Installation.wiki
ok I Installed Kernel and initramfs.cpio.gz
But what about installing cm9 image?
1. I did extract "CYANOBIZ_BETA2.6_A101.img" and copyd it to the root.
2. I did uncompressed data.img.tar.gz, I choosed one of the 3 images and renamed it to data_ICS.img
3. I did copy the 2 files to the root.
But what now how to install it? That's not specificly said how you must do it.
Can you help me ?
Greetings
Avanox said:
ok I Installed Kernel and initramfs.cpio.gz
But what about installing cm9 image?
1. I did extract "CYANOBIZ_BETA2.6_A101.img" and copyd it to the root.
2. I did uncompressed data.img.tar.gz, I choosed one of the 3 images and renamed it to data_ICS.img
3. I did copy the 2 files to the root.
But what now how to install it? That's not specificly said how you must do it.
Can you help me ?
Greetings
Click to expand...
Click to collapse
You need to also drop the menu.lst file on the internal memory and have the cm9 image named as CYANOBIZ_BETA2.6.img then just got to recovery and boot the developer edition firmware and you will be greeted by a boot menu with just one item, click power and it will boot and that's it.
You don't really install anything, the tablet will boot from the img file and use the data.img file as the data partition, that's all (and if you decide to move any apps to the sd card aka internal memory don't boot in an other android os like stock because the android_secure folder will be wiped, though I am not sure CM9 allows you to, I know CM7 does).
Also I have uploaded kboot and it is on the thread in the development section if you want to use that for more flexible multi-boot (or at least to have the multi-boot menu loaded at every normal boot without needing to enter recovery to boot ics), although now it will be a bit hard to obtain the uruk kernel in case you still want to boot that, it is possible, you just need a linux computer or the ext2fsd driver in windows, I can't really give you the kernel from my installation of it since I understood yours is on the sd card and mine is on the internal memory.
And if you would like I can give you kboot already set up with the stock root kernel and all the 3 ics kernels to make it easier for you.
Ow ok will try tomorrow.
Euhm yeah urukdroid is no more on tablet I think I installed last sde firmware.
The kboot is that for switching between then Linux similar system and android 2.2 and android 4 and maybe urukdroid if I reinstall it (not necessary for the Moment?)
Yeah I will try out that kboot you may send it to me if you want. Maybe it's cool feature
Thanks in advance
Greetings
Ranomez said:
You need to also drop the menu.lst file on the internal memory and have the cm9 image named as CYANOBIZ_BETA2.6.img then just got to recovery and boot the developer edition firmware and you will be greeted by a boot menu with just one item, click power and it will boot and that's it.
You don't really install anything, the tablet will boot from the img file and use the data.img file as the data partition, that's all (and if you decide to move any apps to the sd card aka internal memory don't boot in an other android os like stock because the android_secure folder will be wiped, though I am not sure CM9 allows you to, I know CM7 does).
Also I have uploaded kboot and it is on the thread in the development section if you want to use that for more flexible multi-boot (or at least to have the multi-boot menu loaded at every normal boot without needing to enter recovery to boot ics), although now it will be a bit hard to obtain the uruk kernel in case you still want to boot that, it is possible, you just need a linux computer or the ext2fsd driver in windows, I can't really give you the kernel from my installation of it since I understood yours is on the sd card and mine is on the internal memory.
And if you would like I can give you kboot already set up with the stock root kernel and all the 3 ics kernels to make it easier for you.
Click to expand...
Click to collapse
Avanox said:
Ow ok will try tomorrow.
Euhm yeah urukdroid is no more on tablet I think I installed last sde firmware.
The kboot is that for switching between then Linux similar system and android 2.2 and android 4 and maybe urukdroid if I reinstall it (not necessary for the Moment?)
Yeah I will try out that kboot you may send it to me if you want. Maybe it's cool feature
Thanks in advance
Greetings
Click to expand...
Click to collapse
If urukdroid was on the internal memory and you just installed the sde firmware it was not removed and I can send you my uruk kernel, if you first went to recovery and did a full format and then installed the full firmware and then the sde then it is no more on the tablet.
If it was on the sd card then nothing affected it unless you put the card in the pc and used something like minitool partition wizard to delete all partitions and I can not give you the kernel.
Yes, kboot is a chroot based multi-boot menu (think GRUB but unable to boot non-linux kernels, I think) and it allows booting android 2.2, 2.3, 4.0 and linux distributions as ubuntu (although the ubuntu for archos files are gone but you can still use it to boot the kernel from OpenAOS and boot debian from that bootmenu, which will be the same boot menu you will get from android 4.0 though you can not boot stock or debian from that as the kernel is different, well you might be able to boot it but most things won't work, like wi-fi and the likes).
Ok, I will send you my already set up kboot but first tell me if your urukdroid instalation was on the sd card or internal memory and what you exactly did to the tablet cause then I might be able to throw in my uruk krenel and thus you will also once again have access to that as well.
Hello first of all I wanted to say I just got into android 4.4.
But when I start it up I get a lot of messages that are saying.
This application doesn't work anymore.
Any idea what this could be?
Hmm after looking I restarted it and now it works better the android 4.4
But how do you put something on the internal memory if I connect them with usb to laptop I can't acces the root with all my files.
Greetings
R
anomez;65030979 said:
If urukdroid was on the internal memory and you just installed the sde firmware it was not removed and I can send you my uruk kernel, if you first went to recovery and did a full format and then installed the full firmware and then the sde then it is no more on the tablet.
If it was on the sd card then nothing affected it unless you put the card in the pc and used something like minitool partition wizard to delete all partitions and I can not give you the kernel.
Yes, kboot is a chroot based multi-boot menu (think GRUB but unable to boot non-linux kernels, I think) and it allows booting android 2.2, 2.3, 4.0 and linux distributions as ubuntu (although the ubuntu for archos files are gone but you can still use it to boot the kernel from OpenAOS and boot debian from that bootmenu, which will be the same boot menu you will get from android 4.0 though you can not boot stock or debian from that as the kernel is different, well you might be able to boot it but most things won't work, like wi-fi and the likes).
Ok, I will send you my already set up kboot but first tell me if your urukdroid instalation was on the sd card or internal memory and what you exactly did to the tablet cause then I might be able to throw in my uruk krenel and thus you will also once again have access to that as well.
Click to expand...
Click to collapse
Avanox said:
Hmm after looking I restarted it and now it works better the android 4.4
But how do you put something on the internal memory if I connect them with usb to laptop I can't acces the root with all my files.
Greetings
Click to expand...
Click to collapse
It is clearly stated that you can't access the internal memory via msc on the ics thread, only the sd card, and that is also true for any firmware that boots from an img file since the img is on the internal memory and that would mean cutting the system's access to itself=crash.
Ranomez said:
If urukdroid was on the internal memory and you just installed the sde firmware it was not removed and I can send you my uruk kernel, if you first went to recovery and did a full format and then installed the full firmware and then the sde then it is no more on the tablet.
If it was on the sd card then nothing affected it unless you put the card in the pc and used something like minitool partition wizard to delete all partitions and I can not give you the kernel.
Yes, kboot is a chroot based multi-boot menu (think GRUB but unable to boot non-linux kernels, I think) and it allows booting android 2.2, 2.3, 4.0 and linux distributions as ubuntu (although the ubuntu for archos files are gone but you can still use it to boot the kernel from OpenAOS and boot debian from that bootmenu, which will be the same boot menu you will get from android 4.0 though you can not boot stock or debian from that as the kernel is different, well you might be able to boot it but most things won't work, like wi-fi and the likes).
Ok, I will send you my already set up kboot but first tell me if your urukdroid instalation was on the sd card or internal memory and what you exactly did to the tablet cause then I might be able to throw in my uruk krenel and thus you will also once again have access to that as well.
Click to expand...
Click to collapse
Hello again,
Owkey now if I start up my tablet android 2.2.1 startsup
(firmware version: 2.4.83)
I did set the iso file from cyanobiz_BETA2.6.img on my internal memory.
So cm9 boots nice on the tablet but I must go first to the SDE (by pushing volume + ) then a see a white menu -> developer edition -> and chose cyonade and it start good
Urukdroid was installed on my sdcard but that doesn't start anymore as standard at moment. don't know why?
Before I started with cm9 I installed the latest SDE firmware for archos 10.1 gen8. (and the procedure to runb cm9)
Would it work with your kboot file so I can choose between:
android 2.2 (Archos),
Android 4 (CYANOBIZ)
Angstrom (openAOS)
urukdroid 1.6 (not in the menu)
Greeetings Avanox
Avanox said:
Hello again,
Owkey now if I start up my tablet android 2.2.1 startsup
(firmware version: 2.4.83)
I did set the iso file from cyanobiz_BETA2.6.img on my internal memory.
So cm9 boots nice on the tablet but I must go first to the SDE (by pushing volume + ) then a see a white menu -> developer edition -> and chose cyonade and it start good
Urukdroid was installed on my sdcard but that doesn't start anymore as standard at moment. don't know why?
Before I started with cm9 I installed the latest SDE firmware for archos 10.1 gen8. (and the procedure to runb cm9)
Would it work with your kboot file so I can choose between:
android 2.2 (Archos),
Android 4 (CYANOBIZ)
Angstrom (openAOS)
urukdroid 1.6 (not in the menu)
Greeetings Avanox
Click to expand...
Click to collapse
Kboot will make it load at boot so it will go to the boot menu instead of stock 2.2 from where u can choose what to boot or (after a period of time) it will just boot your last selection.
Yes from Kboot you can choose to boot any of those though I really wouldn't recommend Angstrom (I don't even think you can still find a rootfs.img for it, if you still have it on your internal memory please upload) cause it is really limited and also I don't think OpenAOS made a kernel for Angstrom and it'll be quite hard to get the kernel from the SDL aos package (though I do have a kernel that can boot it directly, compiled from the stock 2.2 sources, NOT by me). In theory you can edit the menu.lst to launch Angstrom for it but remember you must edit it with Notepad++ and not any other windows text editor (notepad, word, etc) and you will need to know the format for booting a linux image file (I can tell you what that is) and just add the OpenAOS CM7 (gingerbread) kernel also and use that to boot Angstrom, never boot ANYTHING ELSE when loading the boot menu with the ICS kernel, you will have the same options but you must always remember you CAN'T launch anything else than ICS when launching the OpenAOS boot menu with the ICS kernel. But if you are actually interested in running linux I'd say just go the debianlxde way (download from OpenAOS site) as it is so way much better than Angstrom.
To boot UrukDroid you will need to either have linux installed on your PC/laptop or boot a live cd, put the MicroSD Card in a card reader and connect it and then search the uruk partitions to find the zImage and initramfs.cpio.gz (they might have some slightly different names) and put those in a new folder in the kboot os folder, of if you want I could probably unpack the UrukDroid install and update packages to find the right kernel for you but as I can't really remember what tools I need for doing that you will have to wait about 2-3 weeks (I have exams and also bought myself a Nintendo New 3DS XL that I plan to hard mod after I finish with the exams and do a nand dump and try to edit the firmware and flash it back to see what I can obtain so that's gonna take me about 1-5 days as I am not the best with soldering things on motherboards). You will also have to wait that exact same amount of time if you want me to tell you from where on the UD partitions to find the kernel files as I do not know myself and will have to search for them.

Categories

Resources