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
I just followed this article to run ubuntu on my nexus s with CM7 running on it.
but each time I typing "bootubuntu"
I got this error:
mount: mounting /dev/loop1 on /data/local/ubuntu failed: Invalid argument
This error should happen when executing this line in bootubuntu:
mount -t ext2 /dev/block/loop1 /data/local/ubuntu
Any ideas ?
Are you sure that the kernel you are using supports the ext2 filesystem and loopback device?
Last lines of "dmesg" command might be helpful (if it exists).
how-to-install-ubuntu-on-your-android
This is the article I followed.
I'm not sure whether CM7 support ext2 and loop device, but I see somewhere people said they run ubuntu on CM7 successfully, that's why I post this thread and hope someone can confirm it and show me the steps.
Or let me know your experience on how to run Ubuntu on nexus s.
I like the busybox way to run ubuntu, means if I run a native ubuntu, I can't use my phone feature anymore.
If you read this: http://androlinux.com/android-ubuntu-development/how-to-install-ubuntu-on-android/
Just a few lines into the text there is this paragraph:
For example, G2 Phone and Nexus One both come with loop device support so there’s no need for us to compile a new kernel for it but for others, you may have to.
Click to expand...
Click to collapse
I don't know whether the cm7 kernel kernel supports loop either, but there are many kernels floating around this forum. Maybe one of them does.
Thanks man.
Finally I figure this out. When I got this phone, the seller had already pre-installed a rooted CM7 and busybox. That may cause the problem.
After I re-install the busybox with the latest version, it works.
So CM7 and Nexus S are good to run Ubuntu.
Thanks for taking your time once again.
Hi there, onto my third Android device (Rooted Zte Blade and Rooted Hanspree Hansspad) and I know find myself stuck sorting my new Defy out. I've rooted it with superoneclick and have hit a wall with 2nd Init Recovery, mainly because it seems to have vanished! It's not on market or Appsbrain. Can anyone help?
I plan on using CM7.1 (I use it on my Blade and love its stability) and was also thinking of duel booting with the latest nightly of CM9. I knew one of these days I was going to struggle with rooting one of these, the first two were stupidly easy!
If anyone could help it would be massively appreciated! Oh, and it's my first post because I'm switching from MoDaCo, don't get me wrong, they are cool, but they have barely anything on the Defy and everyone knows you guys rock!
/endsuckup
http://forum.xda-developers.com/showthread.php?t=1028427
Use this first. Then install Rom Manager and from it install CM7.1 It will aslo install latest 2nd init boot and latest CWM
Have Fun with Defy
BTW:
I have it today also xD
Thanks a lot! Especially for the speedy reply! Now I have to really turn my brain on, ADB Shell is not my favourite thing!
developer.android.com^sdk/index.html
(change ^ to /)
install ADB from here then use this tutorial :
wiki.cyanogenmod.com^wiki/Howto:_Install_the_Android_SDK
(change ^ to /)
Then other rest is easy as hell
I've got ADB and Java already installed. thing is, when in CMD i type adb shell and it comes out with
'adb' is not recognized as an internal or external command,operable program or batch file.
Man I hate cmd stuff!
My Android SDK folder is in my root C drive so I am currently in
c:\AndroidSDK>
Any help?
"In the "Variable values" section, add at the very end the location of the tools & package-tools folder, with a semicolon separating these two paths from the rest, e.g. %SystemRoot%;C:\android-sdk-windows\platform-tools;C:\android-sdk-windows\tools."
This should help
EDIT :
But watch your path to SDK's. My path is C:\Program Files (x86)\Android\android-sdk\platform-tools;C:\Program Files (x86)\Android\android-sdk\tools
Your's should be same. DON'T DELETE ANY PATH !! Only ADD this two to the rest.
More easy, try this... http://forum.xda-developers.com/showthread.php?t=1032212&highlight=2nd+init ;-)
2nd init on defy+
Hey, guys! Im a newbie here, soon celebrating one month with my first android phone, an mb256 running 2.3.6. I've just rooted and I'm planning to flash MIUI on it, but I'm not sure if 2nd init is compatible with my device. Just don't want to get locked out or something if anything goes wrong.
Also, does anyone about a good guide for flashing MIUI on my device?
Hi,
I have also a MB526 running 2.3.6 and the SndInitDefy_2.0.apk works perfectly on my device. Enjoy! ;-)
Thanks! Works great!
Any tips on how to install MIUI (Galnet ICS stable)?^^
Hi guys, I can't find any recent posts to help me so sorry if this is redundant. I want to install Ubuntu Desktop (not touch) on my nexus 7. I downloaded a mirror for the image but i cant find the one click installer and have no idea how to push the files myself. I installed the Touch version to my nexus just to try and get an understanding of how it does it but it was way over my head. Thanks for any and all help!
If you have no idea how to push the files yourself, are you sure you are ready to attempt even a one click installer? What will you do if it fails?
Sent from my Nexus 5
Figured it out
Pirateghost said:
If you have no idea how to push the files yourself, are you sure you are ready to attempt even a one click installer? What will you do if it fails?
Sent from my Nexus 5
Click to expand...
Click to collapse
Well to be honest, I figured out how to push using (sudo fastboot devices) all that junk got it stuck in a loop but then found out! If I download the bootimg and the IMG file I can pish both the first as sudo fastboot flash boot /path/.booting and the other sudo flashboot flash user data /path/.img suggestions are still welcome though. I took off the Ubuntu 13.04 and am currently installing LXDE might make a thread for people like me that want it yet.
multirom
I suggest you install twrp and multirom, then search for multiboot ubuntu, there's a thread round here wIth a handful of precompiled linux distros. This allows you yo keep android while enjoyong running linux.
Oh and I reccomend not using unity in ubuntu iy is terrinle and keeps crashing.
I have ubuntu permanently installed but very rarely use it. Lacks hardware accelleration, which is a shame as I think nvidia o[en sourced the tegra drivers. I dod have a little go at getting them running but failed miserably!
joesnose said:
I suggest you install twrp and multirom, then search for multiboot ubuntu, there's a thread round here wIth a handful of precompiled linux distros. This allows you yo keep android while enjoyong running linux.
Oh and I reccomend not using unity in ubuntu iy is terrinle and keeps crashing.
I have ubuntu permanently installed but very rarely use it. Lacks hardware accelleration, which is a shame as I think nvidia o[en sourced the tegra drivers. I dod have a little go at getting them running but failed miserably!
Click to expand...
Click to collapse
I found that installing just Ubuntu 13.04 desktop image and installing gnome or lxde and changing the swappiness to 5 or 0 works great. It runs great. No lag, i have been able to use it without any problems. Did you try that? As for the hardware acceleration I looked into that but seeing as I'm just learning linux and its programming I don't wanna try it. If anybody wants me to post how i installed everything to my tablet I could post the images and give a little tutorial if needed just to help
Ubuntu is a useless OS at this point.
Also....are Mexus devices really cheap? Like Sorny TV's?
Sent from my Moto X cellular telephone...
Hi
I want to use linux deploy app on my s7 edge. When I click on on install in my linux deploy app after configuring a container, phone powers off about 10 seconds after that and then I have to manually reboot it. Any fix for that? And before it powers off it totally freeses. Not just the app but whole phone. It does not even react to physical buttons anymore.
Anyone?
unfortunately, I have same problem. I doubt meefik reads this thread though
Same issue here, post on his github page. Which Linux packages are you trying to run?
I suggest if debian has the repo for it to run gnuroot debian. It works the same but no root required. Since you are rooted you change selinux to permissive which allows more functions
EternalSeekerX said:
Same issue here, post on his github page. Which Linux packages are you trying to run?
I suggest if debian has the repo for it to run gnuroot debian. It works the same but no root required. Since you are rooted you change selinux to permissive which allows more functions
Click to expand...
Click to collapse
The solution was to install TGP kernel where SELinux enforceing was disabled.
https://forum.xda-developers.com/s7-edge/development/kernel-tgpkernel-t3501571
--
I know it's already old and dead topic but I am posting this so that of anyone googles that issue, he might find this answer.