Related
I download the safestrap on the hashcode's site:
Droid 3 :: v1.06 [ 2011-11-20 ]
md5sum: 72ac240d099ff2ab2a755ce8ff95060b
I had never used recovery neither enable safe system before.
so I installed the "Droid3Safestrap-1.0.apk" >> installed recovery >> boot the phone >> entered in recovery menu >> enable safe system >> install zip from SD card >> selected the INIT.D HACK file >> it was installed >> i puted to boot the phone and it freezed.
I turned of battery and turn it on, it pasted the recovery menu and then it didn't boot.
I turned of battery again and entered in recovery menu >> disable safe system and the it booted.
was the INIT.D HACK installed correctly?
I read this:
"Use Bootstrap. Its probably not booting because you need to install a ROM after you enable safe system for the first time." from ChaoticWeaponry
I don't know what to do now.
thanks
you need to either toggle safe system off, or flash a ROM to use for safe system, and then flash the init.d hack
and my suggestion is to flash CM7 or Monster, Mav, SD3, Liberty, Etc. Im on CM7, works very nice http://hash-of-codes.blogspot.com
thanks MrJudylicious,
but sorry don't know how to do it...
this is my first android phone i just follow the steps that Chaoticweaponry told on the other topic:
"1: Root your Droid 3 using the 1 click root method (search around XDA/Google)
2: Download Safestrap from Hashcode's website. - USE BOOTSTRAP IF YOU'RE ON STOCK/NON-SAFESTRAP ROMS
3: Install the .apk file using AppInstaller from the Android Market.
4: Start Safestrap (or similar) and allow superuser permissions - then install recovery.
5: Get Download All Files from Android Market.
6: Download the init.d hack.
7: Turn your phone off.
8: Press m + power, scroll down to BP Tools (volume down key) and select it (volume up key)
9: Scroll down to install zip from SD card (select using power button)
10: Go to internal sd card - downloads folder.
11: Find the init.d file, and install it.
12: Reboot the device (go to main menu on safestrap (or similar) recovery)
13: Done."
I don't know what is flash a ROM...
so the init.d hack is not working?
as I said, I put system safe on and installed complete.. then it won't boot I don't know why..
so I put system safe off and it booted.
can you tell me what to do step by step please?
i'm thankful
Pedro
ps: I got one app called "droid3bootstrap" but idk if it will serve.
if you can, tell me what I need to download and what I should do...
sorry for the inconvenience
thanks
I, personally, would leave safestrap on and download http://goo.gl/xkZ0S which is CM7 11-16build. Put that on the sd card and boot into recovery, toggle safe system, format /system under mounts, install .zip for CM7, clear data/cache, and boot into cm7, then once youre done i would go back into recovery and flash the files for the init.d
MrJudylicious said:
I, personally, would leave safestrap on and download http://goo.gl/xkZ0S which is CM7 11-16build. Put that on the sd card and boot into recovery, toggle safe system, format /system under mounts, install .zip for CM7, clear data/cache, and boot into cm7, then once youre done i would go back into recovery and flash the files for the init.d
Click to expand...
Click to collapse
Thanks a lot MrJudylicious,
but what is this 'CM7 11-16 build'? what will it do on the phone?
I just wanted to install INIT.D HACK because I read that saves battery.
cm7 is a stripped down very functional, very fast operating system. if you want stock, you can visit his hash-of-codes.blogspot.com and under android downloads you can download the stock 5.6.890 /root + superuser ( http://goo.gl/3bTpJ ). you cannot flash to teh main system with safestrap, but you can with bootstrap. you could have issues installing more than one *strap, which is why i suggested you keep safestrap.
it's so confused...
my system version is already 5.6.890...
android version 2.3.4
CM7 is a ROM.
this stock 5.6.890 is another ROM? the INIT.D HACK is a ROM too?
pedroramos said:
it's so confused...
my system version is already 5.6.890...
android version 2.3.4
CM7 is a ROM.
this stock 5.6.890 is another ROM? the INIT.D HACK is a ROM too?
Click to expand...
Click to collapse
INIT.D is a edit of the system settings to inprove speed, battery, etc. Not a ROM.
5.6.890 is a system version - although most refer to it as a ROM (Motoblur)
CM7 is a custom ROM.
ChaoticWeaponry said:
INIT.D is a edit of the system settings to inprove speed, battery, etc. Not a ROM.
5.6.890 is a system version - although most refer to it as a ROM (Motoblur)
CM7 is a custom ROM.
Click to expand...
Click to collapse
Ok... so let me know if I'm starting to understand:
I tried to flash init.d using the safestrap but I had the problem booting in safe system mode and the config changes of init.d wasn't applied.
you told me to flash(using safestrap) the CM7 ROM or the 5.6.890 Motoblur "ROM" and then flash the init.d to have the config changes.
buuuut, I unnistalled the safestrap, installed the bootstrap, flashed the init.d and it booted normal...
now the init.d configs are properly working?
Thanks for your patience
I'm very newbie yet but beginning to understand thank you.
and sorry for my english, I am from Brazil
pedroramos said:
Ok... so let me know if I'm starting to understand:
I tried to flash init.d using the safestrap but I had the problem booting in safe system mode and the config changes of init.d wasn't applied.
you told me to flash(using safestrap) the CM7 ROM or the 5.6.890 Motoblur "ROM" and then flash the init.d to have the config changes.
buuuut, I unnistalled the safestrap, installed the bootstrap, flashed the init.d and it booted normal...
now the init.d configs are properly working?
Thanks for your patience
I'm very newbie yet but beginning to understand thank you.
and sorry for my english, I am from Brazil
Click to expand...
Click to collapse
This is why this didn't work
You install safestrap, it allows you to install roms to your /preinstall directory (directory for windows users ^^). You don't install a rom but install the init.d files to /preinstall and then try to boot off /preinstall (because safestrap is enabled). Obviously that wont work because when your phone boots it looks for system files in /preinstall but all that's there is the init.d hack.
You uninstalled safestrap, installed koush' and then installed the init.d files to /system which your phone actually runs off. At that point the init.d is correctly installed.
Another option(the one that people are telling you here) is to install safestrap, enable safestrap, install your rom to the safestrapped system and then install your init.d hack on top of the rom you just installed which is also correct.
it's 2 different ways to do the same thing slightly differently(although with the second method you basically have 2 /systems). I hope this helps clear up your confusion.
I was confused about what is ROMS and for what it serves...
let me see if I understand...
my OS is the android 2.3.4 which version is 5.6.890
the init.d is like a .exe that changes some configs.
the CM7 is like a firmware.
can I make this analogy?
but two thing are dark yet:
to use safestrap I would have to flash a ROM(CM7, 5.6.890 'motoblur', or another one) before flash the init.d...
but in the case of choosing the 'motoblur' ROM, won't my system change anything for it be the same as my 5.6.890 version?
you said that based on what I did using bootstrap, my init.d is working properly? is there any way to see it?
my another doubt is:
when I flash a ROM or a config like the init.d, is there any way to undo this?
thanks men for the explanation.
I'm grateful.
pedroramos said:
I was confused about what is ROMS and for what it serves...
let me see if I understand...
my OS is the android 2.3.4 which version is 5.6.890
the init.d is like a .exe that changes some configs.
the CM7 is like a firmware.
can I make this analogy?
but two thing are dark yet:
to use safestrap I would have to flash a ROM(CM7, 5.6.890 'motoblur', or another one) before flash the init.d...
but in the case of choosing the 'motoblur' ROM, won't my system change anything for it be the same as my 5.6.890 version?
you said that based on what I did using bootstrap, my init.d is working properly? is there any way to see it?
my another doubt is:
when I flash a ROM or a config like the init.d, is there any way to undo this?
thanks men for the explanation.
I'm grateful.
Click to expand...
Click to collapse
Your OS (android/system software version) is all firmware. CM7 is another firmware. Firmware is just a fancy way of saying "ROM" in this case and it just creates confusion.
If you were to install the motoblur safestrap rom (or any other rom) with safestrap enabled your system wont change, it flashes it to a backup partition instead and you would be booting it off your backup partition, your main system will remain untouched regardless of what you do to the second rom(that's what safestrap is all about).
Init.d is a directory in *nix that holds a bunch of scripts that the user is able to run.
As far as checking if the init.d hack is working, I assume the hack your using is Overminds, he posted
You can test that this works on your roms by flashing and then checking for a ".ItWorks" file in /data partition. If you are using ES File Explorer or similar you will need to be sure to allow it to show hidden files, otherwise you won't see this file.
Click to expand...
Click to collapse
In his development thread. This might work for you.
Willis111 said:
Your OS (android/system software version) is all firmware. CM7 is another firmware. Firmware is just a fancy way of saying "ROM" in this case and it just creates confusion.
If you were to install the motoblur safestrap rom (or any other rom) with safestrap enabled your system wont change, it flashes it to a backup partition instead and you would be booting it off your backup partition, your main system will remain untouched regardless of what you do to the second rom(that's what safestrap is all about).
Init.d is a directory in *nix that holds a bunch of scripts that the user is able to run.
As far as checking if the init.d hack is working, I assume the hack your using is Overminds, he posted
In his development thread. This might work for you.
Click to expand...
Click to collapse
I opened root explorer and there was a ".itworks"(with a medal of sheriff) on /data partition
you said that safestrap won't change my system because it install the ROM in a different partition and the boot is made by there.
doesn't bootstrap happen the same? bootstrap overwrite the original system?
a case:
I used bootstrap and suppose that I want to unflash the init.d.. how can I do it?
thanks a lot
I entered in the bootstrap again to explore the functions...
I went to backup and it was doing a backup for minutes and I realized that I think I didn`t make the backup before flash the init.d... so i`m not able to restore my system before the init.d?
pedroramos said:
I entered in the bootstrap again to explore the functions...
I went to backup and it was doing a backup for minutes and I realized that I think I didn`t make the backup before flash the init.d... so i`m not able to restore my system before the init.d?
Click to expand...
Click to collapse
Well...It depends on what your current phone state is. Are you in Safe Mode or non-safe mode?
If I am reading this thread correctly I would guess you are in non-safe mode but flashed in safe-mode. This means the hack is likely not working (I don't believe you can use SafeStrap to flash in non-safe).
In that case you will not have a backup but you have not done much to the system outside of the installs so it should not matter.
Unfortunately you picked the more complex recovery to start your android adventures with, and your starting instructions were incomplete. I prefer SafeStrap myself but it is really not that useful if you are not going to be doing some heavy hacking or rom flashing.
calash said:
Well...It depends on what your current phone state is. Are you in Safe Mode or non-safe mode?
If I am reading this thread correctly I would guess you are in non-safe mode but flashed in safe-mode. This means the hack is likely not working (I don't believe you can use SafeStrap to flash in non-safe).
In that case you will not have a backup but you have not done much to the system outside of the installs so it should not matter.
Unfortunately you picked the more complex recovery to start your android adventures with, and your starting instructions were incomplete. I prefer SafeStrap myself but it is really not that useful if you are not going to be doing some heavy hacking or rom flashing.
Click to expand...
Click to collapse
calash, thanks for reply
I downloaded the safestrap on the hashcode's site:
Droid 3 :: v1.06 [ 2011-11-20 ]
md5sum: 72ac240d099ff2ab2a755ce8ff95060b
I had never used recovery neither enable safe system before.
so I installed the "Droid3Safestrap-1.0.apk" >> installed recovery >> boot the phone >> entered in recovery menu >> enable safe system >> install zip from SD card >> selected the INIT.D HACK file >> it was installed >> i puted to boot the phone and it freezed.
I turned of battery and turn it on, it pasted the recovery menu and then it didn't boot.
I turned of battery again and entered in recovery menu >> disable safe system and the it booted.
I read this:
"Use Bootstrap. Its probably not booting because you need to install a ROM after you enable safe system for the first time." from ChaoticWeaponry
so I unnistalled the safestrap and installed the bootstraped...
I put to do the boot by the bootstrap >> select the init.d file >> it installed >> boot the cell and it booted normal..
It works 4 me
pedroramos said:
calash, thanks for reply
I downloaded the safestrap on the hashcode's site:
Droid 3 :: v1.06 [ 2011-11-20 ]
md5sum: 72ac240d099ff2ab2a755ce8ff95060b
I had never used recovery neither enable safe system before.
so I installed the "Droid3Safestrap-1.0.apk" >> installed recovery >> boot the phone >> entered in recovery menu >> enable safe system >> install zip from SD card >> selected the INIT.D HACK file >> it was installed >> i puted to boot the phone and it freezed.
I turned of battery and turn it on, it pasted the recovery menu and then it didn't boot.
I turned of battery again and entered in recovery menu >> disable safe system and the it booted.
I read this:
"Use Bootstrap. Its probably not booting because you need to install a ROM after you enable safe system for the first time." from ChaoticWeaponry
so I unnistalled the safestrap and installed the bootstraped...
I put to do the boot by the bootstrap >> select the init.d file >> it installed >> boot the cell and it booted normal..
Click to expand...
Click to collapse
Ok, so right now it sounds like you are using the basic Clockwork Mod recovery, identified by the installed Droid 3 Bootstrap from the market/downloaded. In this case you do not have a backup from before the change you applied (Side note: Backups are also called nandroid backups. They are the same, just a different term).
If you wanted to remove the init.d hack it would be a bit more difficult at this point. Not impossible but you may end up losing all your data. It depends on if the changes the init.d hack made are well documented or not. It is a fairly safe hack so I would not worry too much about it at this point.
For your reference the bootstrap you installed, also called Clockwork Mod, and SafeStrap do nearly the same thing, providing you with the menu at the very beginning when you power on the device and allows you to flash (what you did to install the init.d have), backup, and some other neat features.
The big difference is that SafeStrap allows you to have two operating systems, also called Roms, on the phone. These are identified as Safe and non-Safe. non-safe is whatever OS (or Rom, the terms mean the same on our phones) you start with while the Safe is a new install that you do in the same way as you flashed the init.d have.
As you work with it more you will get the hang of the various terms and software packages. For now you should be in good shape, even without a stock backup. We have ways to get back to a pure stock image if that needs comes up, just check the threads in the development forum for more information.
Hi , greeting everyone !
Before appearing ICS, I made a small update custom, including small changes in the original firmware 3.2.79.
This release is permanently ROOT, busybox is installed proper and is unique , Su and Superuser is up to date ! At the bottom you have Update of this version (activated vibrator and fixed adb command).
Included : 24/01/12
- new boot animation;
- battery percentage, and other new Icon;
- several applications in addition ( office free, flashplayer 11,adobe air.....+++);
- windows animations;
- Sony Ericsson Xperia Arc sound and other stuff.....
Now we have latest update of Su binary v3.0.3.2 , Superuser v3.0.7(41), unique busybox v1.19.3 installed into system/xbin ;
There is no need to install busybox.apk or busybox installer.apk from market, busybox is already installed into /system/xbin/
Also included some tweaks : - increase sdcard speed, - managemant ram memory....and increase reaction speed !
These are the files you need for install this Custom Rom :
- archos.ext4 => http://www.4shared.com/archive/tOxGcPqa/archos.html , http://hotfile.com/dl/143897684/d5edc5d/archos.7z.html
- zImage => http://www.4shared.com/file/KXp8bLDa/zImage.html ; http://hotfile.com/dl/144036333/e7d0e75/zImage.html
- initramfs.cpio.gz => http://www.4shared.com/zip/HnEobpnG/initramfscpiogz.html
How install :
- because the file structure is changed , you need perform a clean installation : Recovery -> Format System -> Reformat Devices...-> I Understand -> ok -> copy firmware_archos_it4.aos into new driver -> ok. After reboot copy archos.ext4 into Internal Storage ( data/media/), reboot into recovery , Recovery System-> Developer Edition Menu -> Remove Kernel ( for boot only to SDE) -> I Understand -> Ok -> Developer Edition Menu -> Flash Kernel and Initramfs -> copy zImage and initramfs into new driver -> Ok ! that's all ....now you have clean install custom rom
Solved - md5sum into superuser when you try to update the su binary , now check md5sum OK!
I did not managed any version of .squashfs because android compiler can't install busybox into system/xbin ( .squashf is NOT RW ), this is why I presented only version of ext4 ...Good Luck !
****************************************************************
Update : 27/01/12
- now >adb shell - fixed and enabel vibrator
- archos.ext4 => http://www.4shared.com/zip/dOscQIvA/archos_up.html ; http://hotfile.com/dl/143982123/b452656/archos_up.zip.html
What did you use to increase ram?
Sent from my HTC Desire HD using xda premium
Quinny899 said:
What did you use to increase ram?
Sent from my HTC Desire HD using xda premium
Click to expand...
Click to collapse
Hi! ...I just increase free ram , lol !
surdu_petru said:
Hi! ...I just increase free ram , lol !
Click to expand...
Click to collapse
Ok
Sent from my ARCHOS 80G9 using xda premium
good job tomorrow i try it (multumesc )
Maryanos25 said:
good job tomorrow i try it (multumesc )
Click to expand...
Click to collapse
..cu placere ....incearca-l nu vei regreta !
with pleasure ...try it...you'll no regret !
Nu ama avut rabdare si l-am instalat. Merge ok. Merci mult.
Y dont have patience and y instaled. Its ok. Thanks.
Sent from my ARCHOS 80G9 using xda premium
Quick question, and I appologize if this is the wrong place for this, I'm currently running your 3.2.78 (ext4). Do I need to update the stock firmware directly from archos first or can I just flash this 3.2.79 rom over what I currently have. Also I "removed android kernel" earlier to always boot rooted if that matters. So what's the best way of going about this?
surdu_petru said:
I did not managed an version of .squashfs because I can't install busybox into system/xbin ( .squashf is R/O ), this is why I presented only version of ext4 ...Good Luck !
Click to expand...
Click to collapse
You can try this:
-get a copy of busybox and symlinks from a working rom (make a .tar or .tar.gz of G9's [email protected])
-copy busybox+symlinks in appropriate directories and chmod them (just to be sure)
-mksquashfs
This *should* work (I've messed around a bit with squashfs on another device)
First custom rom i've seen. Great ! Thank you very much. I will try it later
First thank you surdu_petru Every new rooted/modified rom, I need to start tablet with "original" rom to copy the ext rom into the tablet, and every time, restarting for the first time after the update from sde with the "new" rom, I have SuperUser with empty list (and I have to re-add all the programs in my list). Is there a way to copy the ext rom without booting with original rom? thank you and sorry for my poor english
hitman72 said:
Is there a way to copy the ext rom without booting with original rom? thank you and sorry for my poor english
Click to expand...
Click to collapse
Not yet, accessing /data/media requires a working system (adb is not present in SDE/recovery)
However you should be able to update using "previous" custom firmware- system filename is different
install directly over the version rooted 3.2.79.
Work good. =)
Boot animation - maybe simply text android install? =) Can i change it himself?
gen_scheisskopf said:
You can try this:
-get a copy of busybox and symlinks from a working rom (make a .tar or .tar.gz of G9's [email protected])
-copy busybox+symlinks in appropriate directories and chmod them (just to be sure)
-mksquashfs
This *should* work (I've messed around a bit with squashfs on another device)
Click to expand...
Click to collapse
OK thanks !....but do not want to complicate ... I let the compiler to perform, if he says he can not because I have not rw rights !...I left it ..... I know that there are solutions, but leave it in for users !
ro4sho said:
First custom rom i've seen. Great ! Thank you very much. I will try it later
Click to expand...
Click to collapse
Thanks , lol....
gegabit said:
install directly over the version rooted 3.2.79.
Work good. =)
Boot animation - maybe simply text android install? =) Can i change it himself?
Click to expand...
Click to collapse
Sure, you can change what you want, system is RW, but attention ! do it carefully !
gen_scheisskopf said:
Not yet, accessing /data/media requires a working system (adb is not present in SDE/recovery)
However you should be able to update using "previous" custom firmware- system filename is different
Click to expand...
Click to collapse
In my builds, I added a mechanism to do that, the idea was to add a ".update" to filename to have the initrd replace the old image with the ".update" image before mounting and booting.
Surdu_petru, I don't know if you did the same in your initrd. As gen_scheisskopf mentioned in the sde thread, wiping dalvik-cache is probably a good idea if build changes, it could be done silently there or asked with a menu ? And a common file naming convention between us would help, I saw that you use the archos.img, we could define this as a standard ?
letama said:
In my builds, I added a mechanism to do that, the idea was to add a ".update" to filename to have the initrd replace the old image with the ".update" image before mounting and booting.
Surdu_petru, I don't know if you did the same in your initrd. As gen_scheisskopf mentioned in the sde thread, wiping dalvik-cache is probably a good idea if build changes, it could be done silently there or asked with a menu ? And a common file naming convention between us would help, I saw that you use the archos.img, we could define this as a standard ?
Click to expand...
Click to collapse
Ok I know what you mean...and yes ! for Stock firmware_3.2.79 (files.ext4/squqsh).update exist into initramfs, but because I made some changes in directory structure into Custom Rom , now .update it's not perform .
Ok it's very good idea , for future I'll rename (archos.ext4/squashfs).update
Thanks for your advice !
surdu_petru
will there be a custom rom for the archos 80 g9 250hdd or a root method
it would be nice to have a custom rom on my hard drive tablet
root method only seems to work on sd card versions of this nice tablet
regards phil
philmein said:
surdu_petru
will there be a custom rom for the archos 80 g9 250hdd or a root method
it would be nice to have a custom rom on my hard drive tablet
root method only seems to work on sd card versions of this nice tablet
regards phil
Click to expand...
Click to collapse
Hi!
This custom rom it's work for G9 tablett 80/101 but I don't know if it is supported for HDD.....maybe @letama or or another endorsed person will answer.....for you !
Hi , greeting everyone !
If ICS has not yet occurred then it's time for a new Custom Rom ...
This Custom Rom is based on the original Archos Firmware 3.2.80 and is only for enable SDE.
This release is permanently ROOT, have one busybox installed proper, Su and Superuser is up to date.
Included : 05/02/12
- new boot animation;
- battery percentage, and other new Icon;
- several applications in addition ( office free, flashplayer 11,adobe_air.....+++);
- windows animations;
- increase sdcard speed;
- more free ram;
- zipaling for /data/app/*;
- increase internet security and speed up ;
- high quality camera ( Sony-Bravia patch...);
- and other stuff....
These are the files you need for install this Custom Rom :
- archos.ext4.update => http://www.4shared.com/zip/4RFkHY4x/archosext4update.html
- zImage and initramfs => http://www.4shared.com/zip/gd_SWiL7/drive.html ( are into drive archive ....drive.zip)
Installation :
Can be installed over previous versions , for this it is better to flash with initramfs posted of @gen_scheisskopf ( http://forum.xda-developers.com/showthread.php?t=1480906 )
If you want to do a clean installation (recommended), then you only need to download : archos.ext4.update and drive.zip .
Also included enable vibrator and adjust sound volume !
( Not need to install : Superuser.apk and BusyBox.apk from the Market - they are already installed and updated , latest : Superuser - v.3.0.7(41), busybox - v1.19.3, su - v3.0.3.2 )
Great Thanks @gen_scheisskopf ...
With respect,
surdu_petru
How did you get more ram? I don't like the battery icons, so I'll stay on stock rooted, but how did you get more?
Sent from my HTC Desire HD using xda premium
Quinny899 said:
How did you get more ram? I don't like the battery icons, so I'll stay on stock rooted, but how did you get more?
Sent from my HTC Desire HD using xda premium
Click to expand...
Click to collapse
Hi !
Everyone is free to choose what version of software like.... , that is why I tried to diversify the range of Archos firmware ....everyone is free to choose currently between four versions of software released ( Original Stock Rom firmware3.2.8, Root Rom firmware3.2.80 , Custom Rom firm. 3.2.80 and Plasma Active,Thanks @LeTama ).
Of course expected and welcomed other versions of Custom Rom including various stuff !!!
On the other side, I have answered the same question about ram in the previous version ( Honeycomb Custom Rom 3.2.79 => http://forum.xda-developers.com/showthread.php?t=1462726 )
Have a nice day and Good Luck !
hi, sorry for my noob questions. I have used gen_scheisskopf's initramfs. After the first "long" boot, with pleasure, I saw that the "wipe-dalvik.update" file was deleted automatically now is necessary reflash your initramfs surdu_petru? are there problem leaving gen_scheisskopf's initramfs and rebooting without "wipe-dalvik.update" file? thank you
p.s. new icons for me are always better on every new version
hitman72 said:
hi, sorry for my noob questions. I have used gen_scheisskopf's initramfs. After the first "long" boot, with pleasure, I saw that the "wipe-dalvik.update" file was deleted automatically now is necessary reflash your initramfs surdu_petru? are there problem leaving gen_scheisskopf's initramfs and rebooting without "wipe-dalvik.update" file? thank you
p.s. new icons for me are always better on every new version
Click to expand...
Click to collapse
Ok ! no need to use another initramfs !
And less beware :
- if you plan to do a clean installation ( go to Format System, Reformat Device...OK! and reinstall archos_firmware_it4.aos , than copy archos.ext4.update into Internal Storage data/media/archos.ext4.update, reboot and into recovery copy the two files that are in drive.zip zImage , initramfs - into new drive ) - for this you don't need gen_scheisskopf's initramfs ;
- if you plan to do just update over the original firmware or rooted firmware you need just copy archos.ext4.update on Internal Storage (data/media/archos.ext4.update) and into recovery choose gen_scheisskopf's initramfs and zImage ;
I think you're better now...
Thanks for all your work! Just so I know, which file can I get rid off after flashing? I had your .79 custom rom before. Can I delete the archos.ext4.update file ?
By the way is the wipe Dalvik-cache from Supercharger OK?
blogmaw said:
Thanks for all your work! Just so I know, which file can I get rid off after flashing? I had your .79 custom rom before. Can I delete the archos.ext4.update file ?
By the way is the wipe Dalvik-cache from Supercharger OK?
Click to expand...
Click to collapse
If you are still in Custom Rom 3.2.79 you need to push archos.ext4.update into data/media and in recovery copy gen_scheisskopf's initramfs and zImage into new drive ! whith this you'll not lose your work , and Yes after flash you can delete archos.ext4.update from data/media/...Good Luck!
blogmaw said:
Thanks for all your work! Just so I know, which file can I get rid off after flashing? I had your .79 custom rom before. Can I delete the archos.ext4.update file ?
By the way is the wipe Dalvik-cache from Supercharger OK?
Click to expand...
Click to collapse
There is no need to worry about .update files, they are removed automatically.
I'll check Supercharger dalvik-cache wipe later.
BTW there is no need to flash suduru_petru init if you did flash modified one, functionality is the same, modified init works stable on my G9.
tapatalked from Desire
i just flashed this and will observe for some bugs. i dont know if this happened only to me. i noticed that when i turn off the wifi, the 3G stick will automatically be turn On even if its Off. tried switching it Off,but still it wont turn off.. it is still prompts that 3G stick connected
Flash sites not working
Hi
with this version of root I am unable to get Flash 11 to work (previous root is O.K.). Sites prompt for Flash to be installed although the software is installed. I can't uninstall as it seems to be part of the kernal. Installing Flash 10.3 allows Flash sites to work until a reboot disables it again. Any ideas.
best regards
Bill
bothylad said:
Hi
with this version of root I am unable to get Flash 11 to work (previous root is O.K.). Sites prompt for Flash to be installed although the software is installed. I can't uninstall as it seems to be part of the kernal. Installing Flash 10.3 allows Flash sites to work until a reboot disables it again. Any ideas.
best regards
Bill
Click to expand...
Click to collapse
Flash is not a part of kernel or system, it is a separate application.
Wipe dalvik-cache and try again- here is info.
If this doesn't help- reinstall flash
bothylad said:
Hi
with this version of root I am unable to get Flash 11 to work (previous root is O.K.). Sites prompt for Flash to be installed although the software is installed. I can't uninstall as it seems to be part of the kernal. Installing Flash 10.3 allows Flash sites to work until a reboot disables it again. Any ideas.
best regards
Bill
Click to expand...
Click to collapse
Ok!
You can do that : navigate into /system/app/flashplayer.apk and try to reinstall it , it's work fine....you can do the same with...adobe_air.apk and BooksTablet.apk
flashplayer and adobe_air are just preinstalled in this custom rom .
Thanks , Good Luck!
surdu_petru said:
Ok!
You can do that : navigate into /system/app/flashplayer.apk and try to reinstall it , it's work fine....you can do the same with...adobe_air.apk and BooksTablet.apk
flashplayer and adobe_air are just preinstalled in this custom rom .
Thanks , Good Luck!
Click to expand...
Click to collapse
Hi
thanks for your quick reply
I'am unable to delete Flashplayer, if I tap on the .apk I am prompted to re-install Flashplayer this resolves the issue until I reboot. Is this a permissions problem, how can I check.
I downloaded root explorer changed permissions on flashplayer.apk deleted it and re-installed from market working O.K. now.
Regards
Bill
Greetings, surdu_petru,
I recently installed this custom rom, into my Archos 80G9, and I have a question:
is there anyway to disble/enable the power supplied to de usb connector, in where the 3g Usb Dongle is connected, I use this port to supply power to a small fan, in order to cool down the tablet, and i would like to have control over it, before i rooted, I could controlled it by, just toggling the 3g switch on/off.
thank you in advance, for any help you could give me,
OsiriS5180
osiris5180 said:
Greetings, surdu_petru,
I recently installed this custom rom, into my Archos 80G9, and I have a question:
is there anyway to disble/enable the power supplied to de usb connector, in where the 3g Usb Dongle is connected, I use this port to supply power to a small fan, in order to cool down the tablet, and i would like to have control over it, before i rooted, I could controlled it by, just toggling the 3g switch on/off.
thank you in advance, for any help you could give me,
OsiriS5180
Click to expand...
Click to collapse
Because no changes are made in this direction in the original software, I think you can control as before toggling 3G switch ON/OFF !
surdu_petru said:
Because no changes are made in this direction in the original software, I think you can control as before toggling 3G switch ON/OFF !
Click to expand...
Click to collapse
Thank you, for your fast response, right now I have the switch in the off position, and still have the fan on, it could be the rooting process? , I rooted first with your other post for this version of the firmware, any help would be appreciated.....
Thank you in advance. ..
Osiris5180
So you recommend a clean install? Does this mean removing the kernel or formatting the whole drive?
Sent from my ARCHOS 80G9 using Tapatalk
Shano56 said:
So you recommend a clean install? Does this mean removing the kernel or formatting the whole drive?
Sent from my ARCHOS 80G9 using Tapatalk
Click to expand...
Click to collapse
A clean installation is the best and safest method of installing an operating system....to performe clean instal go to Format System->Reformate Device...-> I understand OK!, after that you need install original .aos file, and than flash archos.ext4.update. ( and yes ..will be completely formatted !)
And if you have important data and you can not delete, than you can install over previous versions, but you need initframs with removal Dalvik-Cache mechanism ( see initramfs posted [email protected]_scheisskopf).
osiris5180 said:
Thank you, for your fast response, right now I have the switch in the off position, and still have the fan on, it could be the rooting process? , I rooted first with your other post for this version of the firmware, any help would be appreciated.....
Thank you in advance. ..
Osiris5180
Click to expand...
Click to collapse
OK !...you are right ....I'll take a look ..but not right now...I have no time ! Thanks !
Thanks.................great job
Hi !
I am pleased to present the latest Archos ICS Firmware 4.0.4 , now with Root, Busybox and Deodexed all files into /system/app/* & /system/framework/* !
In this rom original files have been modified, to be Deodexed and added : Su, Superuser, Busybox & ICS Blue bootanimation !
These are the files you need to install root version :
- archos.ext4.update in archive archos.ext4.update_4.0.4.zip => https://hotfile.com/dl/149767565/ddfdbd1/archos.ext4.update_4.0.4.zip.html
- zImage and initramfs.cpio.lzo in archive drive_4.0.4.zip => https://hotfile.com/dl/149766018/3229b8e/drive_4.0.4.zip.html
http://www.4shared.com/zip/2PK6zYOt/drive_404.html
Installation :
- copy archos.ext4.update into Internal Storage ( /data/media ; /mnt/storage )
- reboot into SDE menu and under Developer Edition Mernu , Flash Kernel and Initramfs : copy zImage and initramfs.cpio.lzo on the new driver that appears on desktop/laptop
- ok ! and wait for reboot your devices : after reboot you can see Android update system for a while .....be patient !
The first boot take longer ....and also for the first boot you will not see bootanimation !.
This Root version works on all tablets gen9, is stable and can be used as a daily ROM !
( For not to expect too much between the two download ....now you have the option to download drive_4.0.4.zip )
If you have problems installing this root version , then you can thank him ( @Shano56 ) and please visit => http://forum.xda-developers.com/showthread.php?t=1542058
A deodexed rom allows for developers to theme the rom and tweak certain apps as they wish !
regards,
surdu_petru
Can't wait for this to be uploaded :3 does this have letamas kernel for overclocking? or will u include that in your custom firmware?
Shano56 said:
Can't wait for this to be uploaded :3 does this have letamas kernel for overclocking? or will u include that in your custom firmware?
Click to expand...
Click to collapse
Hi !
Because it's not a realy Custom Rom , I have not included the kernel of @letama !
surdu_petru said:
Hi !
Because it's not a realy Custom Rom , I have not included the kernel of @letama !
Click to expand...
Click to collapse
Okay! thanks for letting me know.. thanks for the deodex
Can I just have the bootanim? :3 Don't wan't to screw my overclock and build.prop
my 101 is already rooted with your previous ics 404. can i install the deodex version over the older one? what about with archos.ext4.backup file? should i delete them?
letamas overclock kernel doesnt work with this rom...the touchscreen doesnt work
4carlos said:
my 101 is already rooted with your previous ics 404. can i install the deodex version over the older one? what about with archos.ext4.backup file? should i delete them?
Click to expand...
Click to collapse
Hi!
Yes you can do ...and ....
No...don't delete .backup....you will need for Reset Android ! ...otherwise it will not work ! Good Luck!
Will this work with the hdd model and does this version address the wifi issues?
philmein said:
Will this work with the hdd model and does this version address the wifi issues?
Click to expand...
Click to collapse
Hi !
It should be work ....and for moment I don't have any problem with wi-fi ! Good luck !
surdu_petru said:
Hi!
Yes you can do ...and ....
No...don't delete .backup....you will need for Reset Android ! ...otherwise it will not work ! Good Luck!
Click to expand...
Click to collapse
thanks for reply. it works.
Just curious does this rom have the ac3 codec installed so I don't have to use MX video player
do not "custom" this fmw
it is a test for resolved problems
robertlawson225 said:
Just curious does this rom have the ac3 codec installed so I don't have to use MX video player
Click to expand...
Click to collapse
Ac3 plugin is available HERE (you have to buy it). But yes, firmware supports it.
Hi Thank you for your firmware,
I'm kinda new to this..
and i think I've accidentally made a mistake with this update
in sde menu i followed what needs to be done
flashed then copied the 2 other files to the internal HDD of the archos
and after the reboot i never saw the update screen
it went black and keeps rebooting ,sounds like it stock in a loop
(i have the 250GB hdd model so i can hear the spin loopy sound )
i have ruined my device,haven't i ?
thanks for any help
a83 said:
Hi Thank you for your firmware,
I'm kinda new to this..
and i think I've accidentally made a mistake with this update
in sde menu i followed what needs to be done
flashed then copied the 2 other files to the internal HDD of the archos
and after the reboot i never saw the update screen
it went black and keeps rebooting ,sounds like it stock in a loop
(i have the 250GB hdd model so i can hear the spin loopy sound )
i have ruined my device,haven't i ?
thanks for any help
Click to expand...
Click to collapse
hi! your device is not ruined don't worry!
first download this http://update.archos.com/9/gen9/gen9_4.0.4-TEST/firmware_archos_it4.aos
then install using step 1 of my guide (don't format if you don't want to lose apps and media), and step 2 for root http://forum.xda-developers.com/showthread.php?t=1542058
cajl said:
do not "custom" this fmw
it is a test for resolved problems
Click to expand...
Click to collapse
HI!
OK!
Maybe I'll try a test version " Custom Rom Beta" - but I still have much work !
Hi There
Unfortunately the Update also didn't work for me.....
I already get the Android 4.04 Update from Archos, and i also downloaded the AOS File in case that i need it. After that i used the SDE to copy File 1 and 2 on to the Archos 80. Then i executed the Files. After Rebooting the Second Time my System is really Slow it is impossible to use it correct. Anyway i copied the the Update File (archos.ext4.update) onto the System Root. Then i boot into SDE Menu and choose Developer and copy the remaining two Files (zImage and initramfs.cpio.lzo)to the Ramdisk, My Archos updates them. At next reboot i didn't see the Logo of Archos and nothing happens for Hours. i can boot into SDE Menu and i am also able to reformat the Device with the AOS File ( With the original Rom System is really Fast ). So do i made any Mistakes..?
Jiggasonic
Jiggasonic said:
Hi There
Unfortunately the Update also didn't work for me.....
I already get the Android 4.04 Update from Archos, and i also downloaded the AOS File in case that i need it. After that i used the SDE to copy File 1 and 2 on to the Archos 80. Then i executed the Files. After Rebooting the Second Time my System is really Slow it is impossible to use it correct. Anyway i copied the the Update File (archos.ext4.update) onto the System Root. Then i boot into SDE Menu and choose Developer and copy the remaining two Files (zImage and initramfs.cpio.lzo)to the Ramdisk, My Archos updates them. At next reboot i didn't see the Logo of Archos and nothing happens for Hours. i can boot into SDE Menu and i am also able to reformat the Device with the AOS File ( With the original Rom System is really Fast ). So do i made any Mistakes..?
Jiggasonic
Click to expand...
Click to collapse
Hi !
Please do not use this root ! because is a test version ....please use this => http://forum.xda-developers.com/showthread.php?t=1537366
Thanks !
Hi All,
Last week I bought this HTC one, after using iphones for many years. First I loved the phone and I was so annoyed after realizing that it doesn't support my native language "Sinhalese".
So after some trouble, I rooted the phone and replaced the DroidSansFallback-htc.ttf with a Sinhala ttf file which I took from a Samsung phone. I was using Root Explorer App. Wallah!! it was rendering everything fine. :laugh:
The happiness did not last long, after I realized that every time I restart the phone DroidSansFallback-htc.ttf gets replaced with the original. So everytime I restart, I have to replace the file.
Would anyone be able to give a solution for this? Top of my head, would flashing the phone by clockworkmod with a .zip with my DroidSansFallback-htc.ttf fix my problem?
Also what's the reason for this? My friend's got a Samsung S4 with fresh Kit Kat installed in it. And it doesn't do this.
Thanks in advance for your opinion guys.
uadissa
(HTC One; Android 4.3; Rooted)
uadissa said:
Hi All,
Last week I bought this HTC one, after using iphones for many years. First I loved the phone and I was so annoyed after realizing that it doesn't support my native language "Sinhalese".
So after some trouble I rooted the phone and replaced the DroidSansFallback-htc.ttf with a Sinhala ttf file which I took from a Samsung phone. Wallah!! it was rendering everything fine. :laugh:
The happiness did not last long, after I realized that every time I restart the phone DroidSansFallback-htc.ttf gets replaced with the original. So everytime I restart, I have to replace the file.
Would anyone be able to give a solution for this? Top of my head, would flashing the phone by clockworkmod with a .zip with my DroidSansFallback-htc.ttf fix my problem?
Also what's the reason for this? My friend's got a Samsung S4 with fresh Kit Kat installed in it. And it doesn't do this.
Thanks in advance for your opinion guys.
uadissa
(HTC One; Android 4.3; Rooted)
Click to expand...
Click to collapse
how are you 'installing' the sinhala font?
Re
cr1960 said:
how are you 'installing' the sinhala font?
Click to expand...
Click to collapse
Used the Root explorer app to copy and replace the file.
uadissa said:
Used the Root explorer app to copy and replace the file.
Click to expand...
Click to collapse
in system>fonts?
Re
cr1960 said:
in system>fonts?
Click to expand...
Click to collapse
Correct.
uadissa said:
Correct.
Click to expand...
Click to collapse
which rom are you running?
I find easiest way for me is to change the font in the rom zip before flashing the rom. no problems with things not 'sticking'.
Flash the entire ROM?
cr1960 said:
which rom are you running?
I find easiest way for me is to change the font in the rom zip before flashing the rom. no problems with things not 'sticking'.
Click to expand...
Click to collapse
I'm still using the stock ROM with OS ver 4.3. You mean flash the entire rom after changing the DroidSansFallback-htc.ttf in the ROM zip file?
Can't I just flash the Fallback font without flashing the entire ROM?
uadissa said:
I'm still using the stock ROM with OS ver 4.3. You mean flash the entire rom after changing the DroidSansFallback-htc.ttf in the ROM zip file?
Can't I just flash the Fallback font without flashing the entire ROM?
Click to expand...
Click to collapse
did you unlock bootloader and flash a custom rom, or just unlock bootloader?
you need to have a rooted rom to change stuff like fonts etc. if you want the changes to stick.
Flash with a fresh new ROM
Since still I'm only one week after buying the phone, bit reluctant to flash it with a fresh new ROM
Phone is rooted
cr1960 said:
did you unlock bootloader and flash a custom rom, or just unlock bootloader?
you need to have a rooted rom to change stuff like fonts etc. if you want the changes to stick.
Click to expand...
Click to collapse
Yes I have unlocked the phone and rooted the phone after installing TeamWin Recovery. So now my rom is rooted. But it still has the stock ROM in it.
would you be able to explain me bit more on what you meant by
change the font in the rom zip
Click to expand...
Click to collapse
.
you meant download a customer ROM. edit it with my new font and flash entire ROM? or correct me if I'm wrong.
thanks
RESOLVED
I was able to resolve this issue easier than expected. This is what I did.
1. Boot the phone in to the Recovery mode( I have TWRP recovery installed)
2. Connected the phone to PC
3. From PC command prompt access a phone shell using I]adb shell[/I]
4. mount /system
5. Changed the properties like user, group and access permissions of my DroidSansFallback-htc.ttf to match the file in ROM's /system/fonts
6. Copy my DroidSansFallback-htc.ttf which has sinhala to /system/fonts( I made sure my original file was backed up)
7. umount /system
8. Exit from recovery and reboot
All works well :laugh::laugh:
uadissa said:
I was able to resolve this issue easier than expected. This is what I did.
1. Boot the phone in to the Recovery mode( I have TWRP recovery installed)
2. Connected the phone to PC
3. From PC command prompt access a phone shell using I]adb shell[/I]
4. mount /system
5. Changed the properties like user, group and access permissions of my DroidSansFallback-htc.ttf to match the file in ROM's /system/fonts
6. Copy my DroidSansFallback-htc.ttf which has sinhala to /system/fonts( I made sure my original file was backed up)
7. umount /system
8. Exit from recovery and reboot
All works well :laugh::laugh:
Click to expand...
Click to collapse
glad you got it sorted.
there is a difference between being unlocked and running a rooted rom. unlocked means you can install a custom recovery which then means you can flash roms. the rom contains 'files' which provide the ability to change things, which unlocking the bootloader and flashing a custom recovery do not. if you were running a custom rom, simply replacing the font using root explorer would have worked the way you wanted without having to use adb commands.
I believe the phone is rooted.
cr1960 said:
glad you got it sorted.
there is a difference between being unlocked and running a rooted rom. unlocked means you can install a custom recovery which then means you can flash roms. the rom contains 'files' which provide the ability to change things, which unlocking the bootloader and flashing a custom recovery do not. if you were running a custom rom, simply replacing the font using root explorer would have worked the way you wanted without having to use adb commands.
Click to expand...
Click to collapse
thanks for your comment. from all these I'm learning because i'm little new to android.
However I still believe my ROM OS is rooted. Because
1. After installing the TWRP custom recovery I installed SuperUser.zip by Koush to root the ROM
2. When I run root explorer it allows me to replace files into System folders with root access( Super User).
HTC has their own HTC Sense thing running on top of Android. Can that be replacing the system folders every-time it restarts? which is not happening in other phones.
if you were running a custom rom, simply replacing the font using root explorer would have worked
Click to expand...
Click to collapse
Yes I would have fixed but I was only running my stock OS rooted.
uadissa said:
thanks for your comment. from all these I'm learning because i'm little new to android.
However I still believe my ROM OS is rooted. Because
1. After installing the TWRP custom recovery I installed SuperUser.zip by Koush to root the ROM
2. When I run root explorer it allows me to replace files into System folders with root access( Super User).
HTC has their own HTC Sense thing running on top of Android. Can that be replacing the system folders every-time it restarts?
Click to expand...
Click to collapse
you need an insecure kernel .. thats why he's recommending you just flash a rom, it's much simpler
Thanks
clsA said:
you need an insecure kernel .. thats why he's recommending you just flash a rom, it's much simpler
Click to expand...
Click to collapse
But I had a insecure kernal. That's why I had root access when I was in adbd shell and it allowed me to replace files into /system.
uadissa said:
But I had a insecure kernal. That's why I had root access when I was in adbd shell and it allowed me to replace files into /system.
Click to expand...
Click to collapse
nope
this is from ARHD
ROM details:
Removed software (CPU) rendering - full Snapdragon 600 (GPU) rendering
Fully optimized and tweaked
Root access
Unsecured boot.img
Newest BusyBox
RAM optimizations
System signatures check enabled for system security and safety
Improved virtual memory management
Speed optimizations
Enabled GPU UI rendering
Data, cache and system partitions mounting tweaks
Bloatware applications removed
All /system applications updated to latest available
All /data applications updated to latest available
Improved CPU governors performance
Most optimal system scheduler
Disabled kernel debugging for better performance
Zipaligned (Improved RAM management)
Zipalign on boot (for user applications on data partition)
Fully de-odexed
init.d scripts (BusyBox run-parts) support
Auto init.d permissions set on boot
sysro/sysrw commands support
Excellent battery life!
Improved EXT4 performance
OpenVPN support
Most up-to-date system files permissions
Adobe Flash Player support
Support almost 24h a day
...and many more!
Click to expand...
Click to collapse
you don't get all those things just by being Root