Well i have done the rooting and now i have more ques
1-best rom = i tried like 2/3 roms but they always get force close soo i need fast/stable/2.1based rom and yes dont eat much battery .....plz plz plz i m not gud at finding right rom.also what do the ppls think about CaNNon202 rom??is it stable?
2nd-do i always need to dangerSPL and Radio while installing any rom??
3-App2SD.. i idk how can i create ext2 in windows i use paragon partition manger process but when i put sd card in mobile it say i need to format it and after i just create complete 1 fat32 partition do i need to 1st create partition and then install the rom or what do i need to do to install apps on my sd card and also i need the files which i downloaded from marketplace into my card...
Thanks
Jamb
jamb said:
Well i have done the rooting and now i have more ques
1-best rom = i tried like 2/3 roms but they always get force close soo i need fast/stable/2.1based rom and yes dont eat much battery .....plz plz plz i m not gud at finding right rom.also what do the ppls think about CaNNon202 rom??is it stable?
2nd-do i always need to dangerSPL and Radio while installing any rom??
3-App2SD.. i idk how can i create ext2 in windows i use paragon partition manger process but when i put sd card in mobile it say i need to format it and after i just create complete 1 fat32 partition do i need to 1st create partition and then install the rom or what do i need to do to install apps on my sd card and also i need the files which i downloaded from marketplace into my card...
Thanks
Jamb
Click to expand...
Click to collapse
1, no such thing IMHO, if you want stable, stick to stock ROM
2, no
3, there are tuts telling you how to get it done in console, and, I don't recommend app2sd, slow like hell
Jimmy_Z said:
3, there are tuts telling you how to get it done in console, and, I don't recommend app2sd, slow like hell
Click to expand...
Click to collapse
Why wouldn't you run apps2sd? I've got the csdi roms with apps2sd and this thing is blazing fast. Besides, if you're going for apps with larger sizes, you're going to want apps2sd.
I find I'm OK with the 1.6 roms with Eclair bits. Don't need live wallpapers, and the Eclair bits have all the necessary things anyway. Personally I think the 1.6 roms are very stable at this point. Very few fcs and they're speedy.
fellows plz mention me the rom name ..i don't need live wallpapers coz it just slow the os and saying force close and what about 3d gallery coz i m not able to see the pics there..
@nmw407...mate plzz mention the rom name or i just need to unroot it and use 1.6
right?
i really recommend cyanogen. i stopped using it at 4.0.4. flashed every version he's ever made and i never really had good speed. this latest one is NICE, though, and i've hopped back on. for now. but i hear these CSDI ROMs are fast. just try any of them.
http://forum.xda-developers.com/forumdisplay.php?f=448
just look for CSDI in the post title.
as for partitioning, i use amon_ra's recovery.
I've tried cyanogen, superD, and now I'm currently on sciencetest. All these have been very stable. For those starting out, cyanogen has the best step-by-step guide, however, it does require additional steps because he went legal. Some of the other 1.6 roms out there are one step roms.
Use amon-ra's recovery, partitioning sd cards have never been simpler. Much better than partition manager. I used to get read/write errors all the time with partition manager. With the latest amon-ra's recovery, you can pretty much do everything on the phone.
Just remember to nandroid/bart backup, and completely wipe before flashing a rom (again... super easy with amon-ra recovery.) Having a backup will save your life or at least some hair.
Right now using CaNNon202....but as as always its slow
CSDI is really fast and really reliable for me (not using apps2sd). I've had like 1 or 2 app crashes total, and I've been running it for the past month or so, so it's been a lot more stable than any other rom I've flashed previously.
Plus, you get a lot of options like customizing the number of columns in app drawer and number of home screens.
Go Cyanogen. v5 is on the way, which wont be a generic half-assed 2.1 port with reduced functionality.
Given the law about releasing the source for their OS implementation, I.e. kernel and hardware drivers, when do we expect to have the 2.1 source, giving us a feel for the 2.2 implementation? Should have released the 2.1 by now for the 70 and 101....
EDIT: Looks like Android 2.2.1 (Firmware 2.0.54) was released Nov 30, 2010 - so we should expect to see the source for it by the end of this year.
EDIT: Looks like the source has been released - http://www.archos.com/support/download/software/sources/gen8-gpl-froyo.tgz
Now we need someone with good Linux abilities to start helping us compile a custom kernel.....
Sent with my fingertips and voice on my Evo
no custom kernel till we get rooted for the phone...once we get rooted we can do watever to it..im gonna have me a ball with this once we do...lmao
txtmikhail said:
no custom kernel till we get rooted for the phone...once we get rooted we can do watever to it..im gonna have me a ball with this once we do...lmao
Click to expand...
Click to collapse
So does the SDE not look attractive? We have root that way and can do kernels and such....
But I would rather have FULL root (NAND unlocked like we do with HTC phones) enabling us to fully take over the device - instead of essentially a dual boot environment that leaves the stock build on the device and takes up space....
There seem to be some people who think we can't unlock NAND - and don't see why we would want to.
Sent with my fingertips and voice on my Evo
jerdog said:
So does the SDE not look attractive? We have root that way and can do kernels and such....
But I would rather have FULL root (NAND unlocked like we do with HTC phones) enabling us to fully take over the device - instead of essentially a dual boot environment that leaves the stock build on the device and takes up space....
There seem to be some people who think we can't unlock NAND - and don't see why we would want to.
Sent with my fingertips and voice on my Evo
Click to expand...
Click to collapse
i dont know much about the SDE but i know i dont want to install it. with a lil work and time i think we can get this thing fully rooted .. The kernel
is most important to me cuz this thing needs to be overclocked to atleast 1.2ghz..
you don't want to fully root and reformat everything and may brick your device. it's just not worth it.
use the SDE: install custom kernel and if your satisfied remove default kernel and it will boot only custom kernel (until you install any archos firmware again)
with SDE you can use full internal storage (kernel is stored in another very little flash chip: /dev/mmcblk0, mmcblk1 = internal storage, mmcblk2 = sdcard), reformat it and install and do whatever you want. if you're not satisfied, start in recovery mode reformat the device and start all over again or install the archos firmware again. no real chance to brick your device.
why would anyone try to brick his device if he has full device access for free?
@topic building custom kernel and cross compile some linux libraries is quite easy, I'll post an HowTo and some shell scripts today or tomorrow, ok?
I want full root to do wat I want..I have a epic 4g wit root and a custom rom..one ...I don't need to boot up wit dual boot for the same os...
Sent from my A101IT using the XDA mobile application powered by Tapatalk
chulri said:
you don't want to fully root and reformat everything and may brick your device. it's just not worth it.
use the SDE: install custom kernel and if your satisfied remove default kernel and it will boot only custom kernel (until you install any archos firmware again)
with SDE you can use full internal storage (kernel is stored in another very little flash chip: /dev/mmcblk0, mmcblk1 = internal storage, mmcblk2 = sdcard), reformat it and install and do whatever you want. if you're not satisfied, start in recovery mode reformat the device and start all over again or install the archos firmware again. no real chance to brick your device.
why would anyone try to brick his device if he has full device access for free?
@topic building custom kernel and cross compile some linux libraries is quite easy, I'll post an HowTo and some shell scripts today or tomorrow, ok?
Click to expand...
Click to collapse
Once we get root and a recovery image installed bricking the device is pretty hard to do. I seriously haven't heard of any people bricking their phones (other then people flashing different radios - gsm for cdma and vice versa). Rooting and making a 100% ASOP rom would kick ass. Not sure what archos was thinking for making it impossible to root. dumb decision. fail
how would you install a recovery image to a bricked Gen8 device??
there is no need for dual boot but an option in the recovery menu called something like "remove android kernel" which removes the default kernel so the device boots custom kernel only, no dual boot if you don't want it.
You have full root access with SDE, tell me what you can't do with SDE?
SDE = recovery bootloader --> nearly unbrickable device
chulri said:
you don't want to fully root and reformat everything and may brick your device. it's just not worth it.
use the SDE: install custom kernel and if your satisfied remove default kernel and it will boot only custom kernel (until you install any archos firmware again)
with SDE you can use full internal storage (kernel is stored in another very little flash chip: /dev/mmcblk0, mmcblk1 = internal storage, mmcblk2 = sdcard), reformat it and install and do whatever you want. if you're not satisfied, start in recovery mode reformat the device and start all over again or install the archos firmware again. no real chance to brick your device.
why would anyone try to brick his device if he has full device access for free?
@topic building custom kernel and cross compile some linux libraries is quite easy, I'll post an HowTo and some shell scripts today or tomorrow, ok?
Click to expand...
Click to collapse
A HowTo on this device would be great. Thanks!
As to custom ROMs, etc. - I echo other comments above. I have never had anyone truly brick their device doing custom ROMs - I work at a carrier and have not seen a truly bricked device that couldn't be undone with a custom recovery and/or reflash back to stock and locking NAND again and noone is the wiser. We can put together custom kernels all we want, but a lot of the holdup in devices is the bloatware that the manufacturers put in - and a lot of it is behind the scene in the frameworks. Just doing a custom kernel is great - but to unleash the real potential of the device is to remove all the unnecessary options and software and libraries that are not needed.
Not sure who all here has dealt with Android phones and the custom/AOSP/CM environment, but going to AOSP (or CM) without all the manufacturer bloat and only including the necessary drivers and such will show you how much of a performance boost and unending promise a device truly has. The possibilities are endless.
THAT is why we desire to have NAND unlocked and the ability to move this device to take full advantage of it's hardware.
HowTo is online: [HOWTO] Build custom kernel, libraries and applications on your own
jerdog said:
We can put together custom kernels all we want, but a lot of the holdup in devices is the bloatware that the manufacturers put in - and a lot of it is behind the scene in the frameworks. Just doing a custom kernel is great - but to unleash the real potential of the device is to remove all the unnecessary options and software and libraries that are not needed.
Click to expand...
Click to collapse
you can replace the whole operating system, archos ships per default some buggy angstrom linux with SDE. maybe someone is able to put ubuntu or windows phone 7 onto it if he is crazy enough
jerdog said:
THAT is why we desire to have NAND unlocked and the ability to move this device to take full advantage of it's hardware.
Click to expand...
Click to collapse
What do you mean with NAND? The Internal Storage (A101IT - 8 or 16 GB) or the flash chip where the kernels and the default android OS are stored?
eitherway, both are NOT locked. you can remove and replace the (signed by archos) squashfs from /dev/mmcblk0p2 and put your own android or any other operating system in it. or reformat /dev/mmcblk1 (internal storage -> 8 / 16 GB) and install your own operating system (e.g. some stripped ubuntu)
Gen8 devices aren't locked. Install SDE und you can do whatever you want with only little possibility of permanently brick it. you always can reinstall the archos firmware to restore default android OS
I'm looking forward to a clean/vanilla 2.2 rom with all bloat removed!
chulri said:
What do you mean with NAND? The Internal Storage (A101IT - 8 or 16 GB) or the flash chip where the kernels and the default android OS are stored?
eitherway, both are NOT locked. you can remove and replace the (signed by archos) squashfs from /dev/mmcblk0p2 and put your own android or any other operating system in it. or reformat /dev/mmcblk1 (internal storage -> 8 / 16 GB) and install your own operating system (e.g. some stripped ubuntu)
Gen8 devices aren't locked. Install SDE und you can do whatever you want with only little possibility of permanently brick it. you always can reinstall the archos firmware to restore default android OS
Click to expand...
Click to collapse
NAND refers to the flash chip where Archos (and all other manufacturers) put their system files.
When you delete something from the Archos OS (i.e. /system) and then reboot, does it show back up or is it permanently removed? Are you able to remove ALL traces of Archos' stock Android implementation?
jerdog said:
When you delete something from the Archos OS (i.e. /system) and then reboot, does it show back up or is it permanently removed? Are you able to remove ALL traces of Archos' stock Android implementation?
Click to expand...
Click to collapse
yes you are.
install SDE
boot up the shipped angstrom linux
mount /dev/mmcblk0p2 and remove the androidmerged.squasfs.secure file inside
reboot to recovery mode and "uninstall android kernel"
reboot
without the default archos android kernel it boots always to the custom kernel (default: angstrom linux, but can be replaced with any other OS)
now you have a gen8 device without any archos android os and can use for whatever you want it
if you want it back to normal: recovery mode -> reformat device & install archos android firmware
chulri said:
yes you are.
install SDE
boot up the shipped angstrom linux
mount /dev/mmcblk0p2 and remove the androidmerged.squasfs.secure file inside
reboot to recovery mode and "uninstall android kernel"
reboot
without the default archos android kernel it boots always to the custom kernel (default: angstrom linux, but can be replaced with any other OS)
now you have a gen8 device without any archos android os and can use for whatever you want it
if you want it back to normal: recovery mode -> reformat device & install archos android firmware
Click to expand...
Click to collapse
Aren't you just removing the kernel and putting your own in? The partition with the actual system still exists though, correct?
What it seems to me, is that Archos has given the ability to use your own kernel with their /system still in place - but this doesn't give the ability to install a completely vanilla system (ala AOSP and/or CM) or to strip out the bloatware and modify the existing frameworks....
I hate to repeat myself.. ( is my english really that bad? )
You DON'T replace the kernel, you install just another one (called custom kernel).
You CAN remove the archos' kernel (but you don't have to)
You CAN remove the archos' android filesystem (location: /dev/mmcblk0p2 -> androidmerged.squashfs.secure)
You have WRITE ACCESS to all flash devices (/dev/mmcblk[0-2])
When you install SDE it ships a vanilla angstrom linux, this has nothing to do with android and shows that you are ABLE TO INSTALL A COMPLETELY VANILLA SYSTEM (even side by side with archos' android if you want to)
chulri, I think you're missing the point. He wants the entire system opened up. Even though you can use SDE to write to any of the flash devices, can you use it to remove a single App from the existing android setup?
They (and I actually) are wanting a custom recoery (something ALA Clockworkmod would work fine for me), and have full access to the internal nand, so they can flash a completely custom ROM, or a pre-rooted factory rom, etc. They want this WITHOUT having to use SDE. With the squashfs secured like it is now, this makes it a bit more difficult to get what we're wanting... If we have a full system rom that's not secure like the existing one, then any app could be removed, upgraded, or themed however you want.
If you don't already own a rooted android phone, then I don't think you really understand the WHY of what they are asking for.
and again...
you can install whatever you want, and even if it is a customizied archos android
the squashfs is not encrypted, you can unpack, copy and replace it with an unsigned squashfs image or even another filesystem, install a custom kernel which ignores the signature (change one or two lines in initramfs.cpio.gz) and there you go...
why do you need another recovery image when you have SDE? it IS a recovery image..
chulri said:
and again...
you can install whatever you want, and even if it is a customizied archos android
the squashfs is not encrypted, you can unpack, copy and replace it with an unsigned squashfs image or even another filesystem, install a custom kernel which ignores the signature (change one or two lines in initramfs.cpio.gz) and there you go...
why do you need another recovery image when you have SDE? it IS a recovery image..
Click to expand...
Click to collapse
I had thought the squashfs image was secured, which it's good to know it's not.
As for the custom recovery, it's more of a personal preference. Most people would rather have some sort of AOSP rom installed on their system, with none of the custom Archos stuff on it, no dual-booting, etc. And while it may be your opinion that it's not necessary, people want it. Being condescending whenever people request it or even ask about it doesn't help at all (all the , or is my english that bad, etc).
I use clockworkmod on my Incredible, and it's never once told me i had to have my device plugged into power to flash something, but I'm stuck at work right now with my Archos telling me that to flash my system with their SDE I have to have it plugged into the power adapter (even though I have 100% battery). That alone to me (again, TO ME) is justification for a seperate custom recovery...
after you have installed the sde you don't have to plug in power to flash custom kernels
anyway: only because some people want some own recovery image, go ahead, hack the sh!t out of gen8 and may brick it but for god sake don't tell the world you couldn't do the same with SDE and claim about the bad bad fail fail company not letting some stupid users brick their devices the ones who know how still can do whatever they want, with or without SDE. the ones who doesn't.. um.. nevermind
Starting this thread again as my previous one was deleted during the board's transformation yesterday...but I think it's important to bring up the subject.
Coming from an older Android terminal (Htc Magic), I still don't understand how so few dev's out there are actually using ClockworkMod Recovery for their ROM. I know, a lot of you come from WM 6.5, where USB-Flash was the only way to go but now things have changed ! If you are fan enough of Android to be willing to flash it completely to the Nand, wiping WinMo6.5, then go with it and start flashing your ROMS the Android way. The CW way !
As a reminder, CW allows to :
- Flash your ROMS from the SD card. Imagine you want to flash a new ROM but have to leave for 2 days without a computer; it's not a problem ! Put it on the SD card and flash it later !
- Easily implement new kernels or updates. Doing so, dev's can propose completely clean build with the option to flash as many add-on's, updates, kernels or fixes you want. Look here : http://forum.xda-developers.com/showthread.php?t=810471. You can't make it easier.
- Partition your SD card with an ext partition the size you want without the need of a software or a linux-based iso. If you are a Windows user, that's a huge time saver !
- Back-up ans restore. That's a HUGE bonus. Want to flash a new ROM ? Back-up all your current ROM (5 minutes), then flash the new one. Don't like after all ? Restore your backup in 5 minutes...
- For me (and here, I'm not my saying it's always the case, just FOR ME), sd data transfer through CW is two times faster than through MAGLDR.
- Many more...
The same goes for EXT. Using data.img is outdated, it's another WinMo days leftover. Ext is actually mounted as an internal memory, allowing Sense Roms. And the apps installed there won't need to be reinstalled every updates...
It's tough for a Android user like myself to find a proper ROM/Zip with data2ext support these days. Pretty much MDJ, thank God for him. It seems that there a lot of ROMS to choose from but actually there isn't. Especially when the DAF to ZIP tool from the board doesn't work with all the DAF's releases (most of the time it's actually the releases that are not made right).
So please, be an Android user and make the step. It's like you found the door but are afraid to come in...
Just go and read the CW tutorial thread if you are unsure. I'll be willing to help also...
I feel like you could clean flash, boot and set the ROM up, then reboot to recovery and restore the data partition and be good to go. Could it really be that simple?
Not sure how I've been an Android user for so long and I don't know the answer to this question. Any flack I get is hella deserved with this one, lol.
They must be based on the same romlike aosp,cm,oxy and so on
And even when you're switching to another ROM with same base, risks are high that there's some incompatible data layout between the ROMs datastore which will create interesting bugs (different layouts in configuration files and folder structures and so on)
I tried that when started messing with my phone, It sometimes works but with errors and apps no starting in my case. There are some apps that create a zip flashable of your apps which is safer to do.