Hey Guys,
I have seen a few people asking, in passing, how to root the 250GB Archos 70 (and maybe the same method would apply to Gen8s without SD slot or broken SD slots) with full R/W access.
There are a few answers, but nothing definitive for us with the HDDs.
So, has the method been complete for using the internal flash storage or alternative rooting method?
You don't need an SD card to get root.
You need to download and install the SDE from Archos (at the bottom of the page)- http://www.archos.com/support/support_tech/updates.html?country=us&lang=en
Then you'll need a custom kernel that is compatible with your hardware that enables root and adds SU. I can't say that the 3 that are being worked on here will work with your hardware and I'm willing to bet that it would need to be tweaked to access the hard drive as compared to the 70/101's solid state.
As long as your don't remove the Android Kernel (that's what Archos calls their own) you can try to flash others in the SDE and if they don't boot, you can still fall back on Archos's to use the device as normal.
The 3 kernels
Uruk by $aur0n - http://forum.xda-developers.com/showthread.php?t=895599
Ardatdat's OC'd - http://forum.xda-developers.com/showthread.php?t=897877
Dogmaphobia's the 1st with root and SU - http://forum.xda-developers.com/showthread.php?t=880321
If I were you, I'd start with Dogma's. As far as I know, he did very little to the kernel in terms of customizations.
Use Dogmaphobia's for your first try (with the SDE also), it will work, i have a 250, i'm root and OC/UV kernel too. Uruk use the rootfs on sdcard but i think on 250 it's not really a good deal to use it on the HD. Best will be to transfert the rootfs on the internal 2GB nand mem.
Dogma's will get you root, but full system r/w won't be available, as the true rootfs is still a squash. I presume another loopback drive (with r/w) would have to be created and union'd with the existing at startup instead of a tmpfs
Related
This is one of those things that I've always assumed would work, but I don't think I've seen anyone actually confirm it or talk about it yet. Before doing any of this I did a clean wipe of everything, just to avoid confusion on my part.
Step 1) I DD'ed the entire filesystem to an 8GB microSD that I have.
Step 2) Mounted p1 from SD (which is a copy of P1 from internal)
Step 3a) Pulled ramdisk
Step 3b) Extracted ramdisk
Step 3c) Changed all mmcblk0 refs to mmcblk1 in init.rc
Step 3d) Recompiled ramdisk
Step 3e) Pushed ramdisk back to p1 on SD
Step 4) Shut down Nook, reboot, confirm via mount command that all mounted volumes are mmcblk1
As I said, this is nothing revolutionary, but I figured it could be good for testing, especially if anyone wants to take a shot at a potentially dangerous mod like recovery or installing a fresh /system. Also, if I ever seriously messed up my internal memory, I would hope to be able to somehow recover by booting via the SD and being able to DD to the internal memory that way.
Very interesting. Thanks for the effort. Might be worth saving the image in case someone actually DOES brick their nook.
I'm curious as to the specifics. Aren't there several filesystems on the device? What did you do to pull/extract/recompile the ramdisk?
APKs
Are you able to install apk files to the emulated rom/nand on SD card...
also are you able to mount an extra partion on the card....
Thanks
"I would hope to be able to somehow recover by booting via the SD and being able to DD to the internal memory that way"
That will be great if we can push those files back to NAND
FYI, Holding just power + Nook buttons for about 15-20 sec will bring up the factury reset screen.
nook'r said:
Are you able to install apk files to the emulated rom/nand on SD card...
Click to expand...
Click to collapse
I haven't yet, but I don't see why not. Nothing especially different about it as opposed to the internal filesystem.
nook'r said:
also are you able to mount an extra partion on the card....
Click to expand...
Click to collapse
Right now I left vold alone, so it rather stupidly mounts p1, which contains all the critical stuff. I don't see any reason why vold couldn't be made to point to another seperate partition. (which is what I did with some other trials when using the internal ramdisk to boot to /system on the SD - left p1 as a "sdcard" partition)
nook'r said:
"I would hope to be able to somehow recover by booting via the SD and being able to DD to the internal memory that way"
That will be great if we can push those files back to NAND
Click to expand...
Click to collapse
I've backed up my own partitions individually. I suppose if I zero'd empty space and gzipped I could probably find some way to write the entire partition table to somewhere.
Would this be useful to someone who would want to dual boot with Ubuntu or MeeGo?
Could this be used to "dual boot" the fully stock Nook in store and then from card when you want to be free?
Homer
Homer_S_xda said:
Could this be used to "dual boot" the fully stock Nook in store and then from card when you want to be free?
Homer
Click to expand...
Click to collapse
This can be used for whatever you want to use it for. I've been running this way for quite a while, and everything works just as it would if you're running from the internal. It's just like dual booting on your PC.
The first (that I saw) and best documentation for setting this up can be found at:
http://blog.fsck.com/
axe2 said:
This can be used for whatever you want to use it for. I've been running this way for quite a while, and everything works just as it would if you're running from the internal. It's just like dual booting on your PC.
The first (that I saw) and best documentation for setting this up can be found at:
http://blog.fsck.com/
Click to expand...
Click to collapse
This is intriguing.
I would love to run everything off a micro sd and then pop it out to put it back to stock.
Would a 1GB micro sd work ok for this?
Someone needs to come up with an automated way to do this. That would be awesome.
moovius said:
This is intriguing.
I would love to run everything off a micro sd and then pop it out to put it back to stock.
Would a 1GB micro sd work ok for this?
Someone needs to come up with an automated way to do this. That would be awesome.
Click to expand...
Click to collapse
1GB is going to be too small to hold the whole system, but 4GB should work.
It should be something that would be scriptable assuming that the required tools exist on the standard rom, but I don't know if the tools are on there.
You could probably get to 1 GB if you dumped all the recovery junk and made media and data tiny. I'm trying to think if there's anything earing up tons of space besides /system.
Of course, just because you can doesn't mean you should.
how about multiple partitions on a 16gb
clockworx said:
This is one of those things that I've always assumed would work, but I don't think I've seen anyone actually confirm it or talk about it yet. Before doing any of this I did a clean wipe of everything, just to avoid confusion on my part.
Step 1) I DD'ed the entire filesystem to an 8GB microSD that I have.
Step 2) Mounted p1 from SD (which is a copy of P1 from internal)
Step 3a) Pulled ramdisk
Step 3b) Extracted ramdisk
Step 3c) Changed all mmcblk0 refs to mmcblk1 in init.rc
Step 3d) Recompiled ramdisk
Step 3e) Pushed ramdisk back to p1 on SD
Step 4) Shut down Nook, reboot, confirm via mount command that all mounted volumes are mmcblk1
As I said, this is nothing revolutionary, but I figured it could be good for testing, especially if anyone wants to take a shot at a potentially dangerous mod like recovery or installing a fresh /system. Also, if I ever seriously messed up my internal memory, I would hope to be able to somehow recover by booting via the SD and being able to DD to the internal memory that way.
Click to expand...
Click to collapse
Think someone could put together a noob guide for this? I'd like to try running a rooted version of Nook Color from SDCARD (partitioned?) on my stock Nook Color.
If possible? Please & Thanks...
Hi.
1)
I installed Urukdroid using the Easy Installer in internal memory.
Everytime I restart the device, UD wants to install rootfs on the SDHC card, but it is too slow for using UD.
How can I prevent UD from altering the working system
2)
I read somewhere, ext4 is faster than ext3.
Which file system is installed by UD, when usind Easy Installation?
3)
code.google.com/p/urukdroid/wiki/Installation
There is an additional Kernel on this page.
What is this one for?
Is it the OC Kernel?
lordofazeroth said:
Hi.
1)
I installed Urukdroid using the Easy Installer in internal memory.
Everytime I restart the device, UD wants to install rootfs on the SDHC card, but it is too slow for using UD.
How can I prevent UD from altering the working system
2)
I read somewhere, ext4 is faster than ext3.
Which file system is installed by UD, when usind Easy Installation?
3)
code.google.com/p/urukdroid/wiki/Installation
There is an additional Kernel on this page.
What is this one for?
Is it the OC Kernel?
Click to expand...
Click to collapse
2)
Every installation of urukdroid install it to an ext4 partition
3)
I think this is the normal kernel of uruk, the oc kernel is somewhere hede on xda
You should try to re-flash the normal kernel to solve 1)
Welcome on XDA!
Thanks for your answer.
Do you mean reflashing with SDHC card inserted?
I did that in one installation attempt, but it took a veeeery long time for the installation to finish.
I took the card out, after that attempt.
lordofazeroth said:
Thanks for your answer.
Do you mean reflashing with SDHC card inserted?
I did that in one installation attempt, but it took a veeeery long time for the installation to finish.
I took the card out, after that attempt.
Click to expand...
Click to collapse
Do you want uruk on sd or not? you can decide...
just reinstall urukdroid
No, I don't want it on SD.
I want it in internal.
I got a suggestion in android-hilfe .de to buy a slower but bigger SDHC Card and install Urukdroid on internal.
I did that, but it is annoying when the device restarts.
I would rather leave the SD in the A70 permanently but to remove it everytime it restarts.
16Gb class 4 card
Another question:
Is it wise to use ext4 instead of fat32 for the biggest patition used for storing data and readable by Windows?
Is there any speed improvement?
Furthermore:
I installed firmware 2.1.08 and I want to stay there, as I heard it is the most problem-free version.
Can I use the kernel from here:
forum.xda-developers.com/showthread.php?t=897877
I don't think so, as it says it is for 2.3.20
lordofazeroth said:
Thanks for your answer.
Do you mean reflashing with SDHC card inserted?
I did that in one installation attempt, but it took a veeeery long time for the installation to finish.
I took the card out, after that attempt.
Click to expand...
Click to collapse
Another question:
what happenes, if the SD Card is full?
Is UD creating new Partitions while saving the data on the SD?
That could be an answer to the long waiting time.
lordofazeroth said:
Another question:
Is it wise to use ext4 instead of fat32 for the biggest patition used for storing data and readable by Windows?
Is there any speed improvement?
Click to expand...
Click to collapse
The system partition of uruk is always ext4, the normal storage partition is alwys fat32 so you dont gonna have problems with mounting under windows
Furthermore:
I installed firmware 2.1.08 and I want to stay there, as I heard it is the most problem-free version.
Can I use the kernel from here:
forum.xda-developers.com/showthread.php?t=897877
I don't think so, as it says it is for 2.3.20
Click to expand...
Click to collapse
You wanna use Stock or Urukdroid?
Urukdroid 1.0 is the modified version of 2.1.08
Well, I want to use Urukdroid.
I tried the OC Kernel from the thread posted above, but I got a bootloop.
Reinstallation of the original Kernel is in progress.
lordofazeroth said:
Well, I want to use Urukdroid.
I tried the OC Kernel from the thread posted above, but I got a bootloop.
Reinstallation of the original Kernel is in progress.
Click to expand...
Click to collapse
I don't think the OC kernal works with Uruk1.0. If you want to OC you need to run the 0.7. Not sure if it makes a difference but the few times I have reinstalled Uruk to internal memory I remove the SD card during the whole process so nothing gets put on the SD. I don't think it makes a difference but it makes me feel better . My new 16gb class 10 should be here monday so I can install Uruk on it and hopefully it will speed things up.
Guess I have to wait...
(System is running now, never touch a running system)
I reinstalled UD with SDHC Card inserted. Before that I deleted all Data on it.
Installation was way quicker than before.
Although I think the UD Installer created the rootfs and data partition on both internal and external memory.
How do I out, which memory is used?
Hi, i have been searching but have been unable to find some answers..
Completely new to this,before i start.
I installed urukdroid 1.5 using the easy install method on my archos 101.
1. When using urukdroid it is so slow and unresponsive, from what i have read this is probably because i have a slow cheap sd card, sound about right??
2. So if i want to uninstall ud from my card am i best using the recovery menu option (and would that just wipe all my stuff) or (as i saw in a different post) format the sd card on a pc and copy my stuff back on to it?? unsure of what is actually on the card and whats on the archos as far as uninstall goes. and what happens to the partitions
2.1. Secondly, why do people put ud on a sd card instead of the internal memory? (remember noob alert!!) it seems like you limit yourself to only using one sd card and the possibility of it running really slow.
3. So if i want to put it on my internal memory - should i do it? what are the pitfalls? will it wipe all my data like it did on the sd card? (lucky i took a backup eh!)
4. And, last question, i promise, is urukdroid really that much faster once you overclock and get it all running nicely?? for example i tried to run shadow gun on the stock 101 and it tried hard but didnt quite get there, would this run ok under ud? or am i completely missing the point of ud (very possible)
Thank you all for any help/answers.
Lee...
I also just installed Uruk 1.5 on my A70 last night and have updated to 1.6RC2 then 1.6RC4. I used advanced install and let it do its thing to install to internal memory. I can see maybe a slight improvement over the stock ROM but I now have a problem where I can't install any apps due to lack of space. This method did not wipe all my data and while still on 1.5 I was able to find my backed up apps and re-installed a few. You will still have your original ROM to fall back on. Unfortunately I have a feeling that anyone knowledgeable will not be reading these posts and newbies cant post in the developer's thread where the meat of the conversation is taking place. Maybe we'll get lucky.
Hi,
Yes i agree, anyone who would know the answers prob doesnt read these. Is it possible to bump it up a bit in anyway??
Lee...
1. If you don't have a verrrry fast sd card ii is alot slower then internal, esp. as the controller is also slower on sd then on the internal .
2. If you remove the sd card, and flash the Urukdroid initram and zimage you can install everything on internal.
The easyinstaller allwas to resize your internal memory so that the original Android and Data stays intact.
2.1. UrukDroid started on sd because it is easier to not do something wrong instead on the internal. Since 0.7 it is stable eough to allways go to internal.
3. Yes internal is the best way, and for erasing read 2.
4. No it is not much faster, how could it be?
Std archos runs with 1GHz and Uruk sometimes up to 1.2GHz ( most of us can't get over 1.1 ) so to be able to play really demanding games it is the wrong tablet.
And yes you are completely missing the point.
UD and every ROM for other devices are there to give you more freedom, like root or the way bigger appspace ( std archos has 300MB ), OS upgrade ( when CM7 or CM9 are done for ex) or other designes ( like MIUI).
My A70 runs much better since I changed to Urukdroid. Less laggy and generally faster. Very few crashes. The ext4 filesytem is much faster than Fat32 and I think that compcache and swap also help a lot.
Don.
Hi Fzelle,
Thanks for your help, cleared stuff up.
Like i said, i thought i might be missing the point of it, i did wonder how much difference overclocking it to 1.2Ghz and the UD system would make. but i can see the point of having a bigger app area, i had the warning of running out of space.
Just to check though, to uninstall it from my sd card you said see 2. but it wasnt clear what that meant. should i go to the recovery boot screen and delete it there or just format my sd card? and i have now got a rootfs.img on my internal storage, is this normal??
Thanks again.
Cheers Lee...
Rootfs.img comes from the SDE installation, as you have installed Angstrom Linux with that.
If you don't plan to use that, you can erase that or save it to your computer.
If you shut down the tab and remove the sd, install the zimage and initram of uruk you will be asked to install again.
Use advanced and install on internal.
Alright, before I begin, here's what I have for my device:
Custom bootloader with the ability to boot any kernel I might need
CWM
OmniROM source tree compatible with my platform
~64 GiB SDXC microSD
Now, the issue is that my device (Acer Picasso ([Iconia A500]) has finally lost its ability to properly read certain partitions of the internal flash memory. Despite several attempts at reformatting the partitions (usually ending up in "this operation doesn't work because I/O error") I am unable to revive those partitions of the flash space. However, I have been able to flash a kernel and get it to boot Lubuntu off an external sdcard.
Nothing against Lubuntu, but I can't exactly play Clash of Clans/MCPE. And OnBoard is a poor replacement for Android's keyboard. It would be really nice if I could do the exact same thing I did with Lubuntu with an Android root filesystem.
Is using an external SD as a root filesystem possible? If so, how practical?
As sidenote, how hard would it be to solder in new flash memory in case it comes to that?
Hi- I have a Chuwi Hi 10 dual OS (Win10/Android 5.1) tablet. It has 64 GB of memory, but only about 1/4 of that is allocated for the Android partition. I had hoped to find a way to change the partition size so that about half was available to each OS, but haven't found a way yet.
I am now running into the situation where I am getting low storage capacity messages. I have a 128GB micro SD card installed, but it seems unable to use it. Is there a way to allow the use of that space, as other versions of Android (and variations) allow? Preferably, I would like to do it such that I won't lose everything currently on the tablet, but I can back up data files if necessary (such as for rooting?)
Thank you for any assistance.
Bob
Kind of late to help but I just went through this process. Hopefully this will help someone else at the least save some time searching around various forums. I and am currently in final steps of moving existing apps to SD card via the process below:
Unlock bootloader
Install Custom recovery (I suggest TWRP)
Install SU (the device is now rooted)
Install Apps2SD and partition the SD card as you wish, making ext4(ext3) the file system for the partition you want to install apps on > reboot.
Link apps to SD card in Apps2SD (there is multiselect in the menu)
Backup data and download stock OS, firmware, etc > http://forum.chuwi.com/thread-2341-1-1.html (this link is for the Hi10pro. There are other threads with downloads for other models link Hi10 plus, etc in that same forum)
Tutorial for unlocking, installing custom recovery, rooting, etc > http://www.modaco.com/forums/topic/...10-plus-hi10-plus-hi10-pro-hibook-hibook-pro/
Tutorial to use Apps2SD to partition and link apps > https://www.youtube.com/watch?v=NJMpQNXTFew