Related
Hi,
this thread is meant as a starting point for every kind of questions. I will write everything I know into this thread and update it (hopefully) frequently
Here are the topics handled for now (if you have any other questions you want to have answered you can PM me, so I can try to handle it if I know the solution and add this to my to do list in point 5!!! ):
1. How can I root my phone
1.1 General information/Basic adb-commands
1.2 Do I have to create a goldcard?
1.3 Tools you need
1.4 The automated way
1.5 The manual way (recommended by the author)
1.6 Problems and (hopefully good) solutions
1.7 References
2. Flashing images/ROMs
2.1 What is a recovery image
2.2 What is a boot image
2.3 How to flash/tools needed
2.3.1 Creating a Goldcard
2.4 Where can I get an overview of the existing ROMs?
2.5 Problems during flashing and solutions
2.6 References
3. Information about the Tattoo/Useful stuff
3.1 How to install busybox?
3.2 Can it perform multitouch?
3.3 How to increase battery life?
3.4 Using own ringtones for calls/sms
3.5 How to disable data transfer with a custom ROM?
3.6 How to make the Tattoo ring louder?
3.7 How to replace the home screen?
3.8 Disabling xxx-synchronisation with Google-servers
3.9 Backing up apk's and data to your PC
3.10 How to enable more languages on my mobile?
3.11 How to manually delete system apks? Alternatively with GUI?
4. Dev-Goodies
4.1 Modifying update.zips and resigning them
4.2 Modifying resources in apk-files and resigning them
4.3 Installing apks via adb for getting exact error codes if installation fails
4.4 Everything related to ROM cooking
5. Things I will do better in this thread due to user request
Please note: I won't be giving tutorials about Android-apps usage beside the one mentioned in my tutorial!
Let's start now:
1. How can I root my phone?
1.1 General information/Basic adb-commands
Rooting a phone enables you to do things, which normally aren't possible for the average user like:
- Removing apps which were preinstalled by the provider (like Orange, Vodafone, etc.). My Tattoo had Vodafone apps for buying music and other sh*t, which was installed on the system partition (to which a "normal" user has no rights to write to, including deleting).
The Tattoo was successfully rooted by a bunch of guys here, namely -bm-, mainfram3 and Coburn64 (maybe, I don't remember quite correctly ). Also the Tattoo was the first phone having a security mechanism hindering a user to mount the filesystems as read/write, which had to be overridden by remapping the read only memory region to a read/write one. This is done by the module Tattoo-hack.ko, also made by mainfram3. He also created the first boot.img, which enabled su directly from adb and loading Tattoo-hack directly from boot on.
A few words about adb:
ADB is a tool for communicating from the PC with the mobile phone. For this a service is running on the phone enabling the communication via Terminal Emulator. Here are the most useful adb-commands:
Code:
adb push localFileFromPC /path/on/mobilephone
-> pushes a file "localFileFromPC" to a specified location on the phone
adb pull /path/to/file pathFromPC
-> receives a file from the phone and stores it to "pathFromPC"
adb remount
-> This is only possible in custom ROMs, remounts the file system to r/w automatically
adb shell "command"
-> executes "command" and returns to the computer shell
adb shell
-> opens a shell session on the phone (from here on you have to be very careful! Also you can execute now normal linux commands like rm, mv, ls, chmod and so on, but not cp (this can done through busybox)). You will have to use this more often, so get used to it ;)
1.2 Do I have to create a goldcard?
I read this question quite often. For rooting, you don't need it, but for SIM-locked phones you can't flash custom unbranded ROMs (I think).
A guide to create a goldcard follow this link: http://forum.xda-developers.com/showpost.php?p=5179788&postcount=1 (thanks to MiSSigNNo to this point)
1.3 Tools you need
A complete set of tools can be found here Feel free to mirror it:
http://rapidshare.com/files/403766494/Tattoo.rar.html
This package contains:
- adb binaries for Windows (sorry Linux users )
- su (Please note: use the su-binary attached in this post, not the one in the archive!!!!!)
- m7 exploit
- Amon_RA recovery.img
- mainfram3 boot.img
- flash_image binary
- tattoo-hack.ko
1.4 The automated way
This method was created by maverixx and can be found here. This basically consists of a package doing everything you need by itself. It roots the phone and flashes maverixx recovery.img, which (no offense) I don't like as much as I like Amon_RA's one!). Just click the batchfile and it does the rest (you have to connect your phone via USB to your PC though ).
If you want to use the automated way, but flashing Amon_RA's recovery, just replace the recovery.img from maverixx' package with the recovery.img provided in my archive file (see 1.3 for the link).
In my time here I noticed quite a few users experiencing problems either with a fully functional su or with the recovery image not flashing certain update.zip packages. It seems to be a matter of luck.
1.5 The manual way (recommended by the author)
I personally like what is done when and how, that's why I recommend the manual way. So let's get down to business Let's see if you know all the adb-commands I wrote here:
1. Let's say you have everything unpacked into C:\Tattoo
2. In your terminal (on your PC) type:
- adb shell "mkdir /data/local/bin" (if it returns an error it means that the directory already exists, just proceed)
- adb push m7 /data/local/bin/
- adb push su /data/local/bin/
- adb push flash_image /data/local/bin/
- adb push tattoo-hack.ko /data/local/bin/
- adb push recovery.img /sdcard
- adb push boot.img /sdcard
3. We have every needed file on the phone now. Type now (we are still in your terminal):
- adb shell
$ cd /data/local/bin
$ chmod 766 m7 (I don't retain this step as mandatory, so if this process fails, just proceed)
$ while ./m7 ; do : ; done
lots of text until you see something like "wrote shell code", press enter 2 or 3 times enter to see:
#
4. Then perform this:
- # export LD_LIBRARY_PATH=/system/lib
- # export PATH=/system/bin
- # insmod ./tattoo-hack.ko
- # mount -o rw,remount /dev/block/mtdblock5 /data
- # mount -o rw,remount /dev/block/mtdblock3 /system
- # cat ./su > /system/bin/su
- # chmod 4755 /system/bin/su
- # chmod 755 ./flash_image
Click to expand...
Click to collapse
Questions?
1.6 Problems and (hopefully good) solutions
Q: How do I execute my command line tool?
A: On your Windows host, go to Start->Run...->type "cmd"
Q: Where is my adb? When I type it in my shell it says that it was not found!
A: The adb binary is found in the archive I supplied above or in the Google SDK. As my archive-file is quite smaller than the Google SDK you should take mine. Let's suppose your adb binary is unpacked in C:\Tattoo, then type:
Code:
Your\Current\Location> cd C:\Tattoo
C:\Tattoo> adb <command>
Q: adb says "error: device not found" when I try to launch the shell on the phone!
A: Connect the phone with the usb cable and make sure the sd card is not mounted as drive on your PC!!!
Q: When I want to copy something the phone returns that "cp" is not found! Also when I try to move a file, it says "cross-link device".
A: Well, copying from one partition to another is only possible either via busybox or via
Code:
cat file > /location/filename
Example:
cp /data/su /system/bin
is realized by typing
cat /data/su > /system/bin/su
Also make sure that system is r/w!!!
Q: flash_image returns write errors when flashing recovery/boot image!
A:
For boot: Try to redo the flash procedure
For recovery: Note that you can't flash the same recovery.img as the one already installed, so install another recovery.img first (like maverixx) and then Amon_RA's again. If it still doesn't work reboot, remount the partitions r/w, insmod tattoo-hack.ko and retry flashing.
Q: How can I unroot my device?
A: Just delete su from /system/xbin and restore the old boot.img. Alternatively see here for retrieving a stock ROM to flash it on your phone.
PM me with more questions and I'll post them with the possible solution.
1.7 References
- Zecanilis EXCELLENT Root-Recovery-Flash images thread
- maverixx' One-click root method+recovery thread
- Coburn64's Newbie guide for manual rooting (recommended reading!)
2. Flashing images/ROMs
2.1 What is a recovery image
A recovery image is not only useful to flash custom ROMs on your device. It also enables you to backup your entire phone contents to restore it completely in case of a brick, if anything should happen...especially SIM-locked mobiles should be backed up as soon as possible. Also many recovery image modders add several non-standard features like mounting the SD card while in recovery mode or enabling adb support, etc.
2.2 What is a boot image
The boot image not only contains the kernel which brings up your Tattoos, it only can be modified to load up modules enabling ext2/3 support, loading camera, remapping read only code to an r/w area (tattoo-hack.ko), etc. Without a working boot.img, don't even bother trying to boot the phone (maybe if you do a logcat it returns something useful to solve this problem )
2.3 How to flash/tools needed
Execute steps 1 to 4 in topic 1.5 first!
5. Now comes the hard part:
- # ./flash_image boot /sdcard/boot.img
- # ./flash_image recovery /sdcard/recovery.img
it can be that flash_image reports errors in the last step (recovery.img step), but another user said it would be still working to boot to recovery...but to be sure (if you got the error!!!) flash maverixx recovery.img and then again the one I supplied in my archive (Amon_RA)
Reboot once and when you connect with adb to your phone you should see the difference
Click to expand...
Click to collapse
2.3.1 Creating a Goldcard
This is a post I took from MiSSigNNo, kudos to him:
Creating the Gold Card:
[...]
4. We need the android-sdk tools, we can find them here: http://developer.android.com/sdk/index.html download them, and unzip in a folder maybe in C:\androidtools
5. Go the the Command line (Start->Execute->write cmd and OK), and there you should find where you unzip the android-sdk tools, example cd c:\androidtools\tools
6. Run this command "adb shell cat /sys/class/mmc_host/mmc1/mmc1:*/cid" if you had the microSD in the drive you will find a long number like:
532600bd227d9c0347329407514d5402
7. Go to this page to reverse it: http://hexrev.soaa.me/ and copy the code reversed:
In our example it will be: 00544d5107943247039c7d22bd002653
8. Go to this page to generate your GoldCard image: http://revskills.de/pages/goldcard.html
And put your reversed number and you email. You will receive an email with a file called "goldcard.img"
9. Now you need an Hex editor like HXD. Download it from: http://download.cnet.com/HxD-Hex-Edi...html?tag=mncol
10. Exactly the same as the instructions I pasted above:
11. Install and launch HxD Hex Editor program. (make sure you use "Run as Administrator" under Vista and win 7)
12. Go to Extra tab > Open Disk. Under Physical disk, select Removable Disk (Must be your SD card), uncheck “Open as Readonly), click OK. (BEWARE, MUST BE UNDER PHYSICAL DISK NOT LOGICAL DISK, THIS MISTAKE MADE ME BIG PROBLEMS)
13. Go to Extra again, Open Disk Image, open up goldcard.img which you’ve saved/unzipped earlier.
Now, you should have two tabs, one is your removable disk, the other is goldcard.img. Press OK when prompted for “Sector Size” 512 (Hard disks/Floppy disks), click OK.
14. Click on goldcard.img tab. Go to Edit tab > Select All, edit tab again > copy.
15. Click on the “removable disk” tab. Select offset (line) 00000000 till offset (line) 00000170 (including the 00000170 line), click on Edit tab and then Paste Write.
16. Click on File > Save. now you can exit the program. You now have a gold card.
[...]
Click to expand...
Click to collapse
2.4 Where can I get an overview of the existing ROMs?
Look it up here (Excellent work liderzre)
2.5 Problems during flashing and solutions
Q: HEEEEELLLPPP! flash_image says that it couldn't write to some memory addresses! What can I do?
A: Don't panic. First make sure to have loaded tattoo-hack.ko, remounted system and data to r/w and then try again with another recovery.img (either maverixx or Amon_RA). Flashing the same recovery.img again WON'T WORK!!!! That's why you have to take a little detour by first flashing another recovery image.
Q: How do I boot to recovery??
A: Type in your command line while the phone is plugged in:
Code:
adb shell "reboot recovery"
. If this doesn't work, turn off your phone, hold down the home-button and press the power-button. Then when the Tattoo logo can be seen, release the home button and the recovery screen should be seen
2.6 References
- Zecanilis EXCELLENT Root-Recovery-Flash images thread
- maverixx' One-click root method+recovery thread
3. Information about the Tattoo/Useful stuff
3.1 How to install busybox?
Load the busybox binary here (select the one with arm6 at the end). Put this binary onto your data or system partition (I suggest /system/xbin) and now there are two ways to install/enable it. See below
Method 1 (will extract EVERY FEATURE, but consumes A LOT of your disk space so be careful or switch to method 2)
Do this in your command line:
Code:
adb remount (make it r/w if not done already)
adb shell "mkdir /system/xbin" (create dir if it doesn't exist)
adb push busybox /system/xbin (please make sure to have busybox in the same directory as adb ;) )
adb shell
cd /system/xbin
./busybox --install
Method 2 (saves your precious disk space )
Do this in your command line
Code:
/system/xbin/busybox --install -s /system/xbin
3.2 Can it perform multitouch?
Nope, the Tattoo has a resistive touch screen, which is known to be NON-multitouch...newer generation or high-end phones usually have capacitative screens. My suggestion is not taking the Nexus One anymore, since their touch screen type supports only 2 fingers at once, while phones like the Samsung Galaxy S have a SUPER responsiveness and sensibility (and of course 10 fingers support).
3.3 How to increase battery life?
Okay, here are little tips how to increase battery life - mine holds 7 to 8 days and I surf, call ppl and sms almost every day:
1. Flash either fyodor 0.6.4.2 or Abyzou 2.1.9 - my favourite is fyodor ones (if I still would have a Tattoo, of course )
2. Download APNd roid from the market or here and disable your 3G Internet connection (for activating it, just start the program again!)
3. If you see that you have NO RECEPTION AT ALL in one place (at work for instance), turn off your phone as this will DRASTICALLY decrease battery life because the phone tries constantly to search for a network it can log on to.
4. Try to keep your phone in normal temperature areas (between 20 and 27 degrees celsius = 68 - 80.6 degrees fahrenheit)
5. Kill unneeded apps automatically (there are quite a few apps doing this)
3.4 Using own ringtones for calls/sms
Create a folder called "media" on the root of your SD card and a sub-folder called "audio" there you have to create one folder called "notifications" for SMS and "ringtones" for call sounds. Place every desired track into these folders and reboot your phone. You should see the entries now when choosing ringtones. Alternatively just load "Ringo Pro", a really powerful tool also able to display SMS pop-ups and much more.
3.5 How to disable data transfer with a custom ROM?
As already explained above, load APN droid from the market or here.
3.6 How to make the Tattoo ring louder?
There is a little app called "Louder Volume Hack" enabling your phone to ring much louder than normally. You can load it on any popular w*rez-site Unfortunately I cannot enter the link to the app here or PM it. Any questions requesting a link to this app will be deleted instantly, so don't bother trying and use Google. There are several buttons displayed, but for better visibility I suggest enabling the Widget and hacking the system there. Also please note that ROOT access is required!! Refer to section 1 to root your phone.
3.7 How to replace the home screen?
There are two ways to do it. Method 1 is the easier one, but runs the Google Launcher and the replacement laucher in parrallel, which implies more CPU usage and battery drain. Method 2 is the more brutal one, but enables you to run just one launcher.
Method 1:
Install the replacement home app and press the home button. A dialog should appear asking you which Home Launcher should be used.
Method 2:
Put your home replacement apk onto the root of your SD and make sure you have busybox installed and /system mounted as writeable. Rename the Home replacement apk to Launcher.apk and fire up adb shell:
Code:
mv /system/app/Launcher.apk /system/app/Launcher.apk.old && mv /system/app/Launcher.odex /system/app/Launcher.odex.old && cp /sdcard/Launcher.apk /system/app && chmod 755 /system/app/Launcher.apk
Should be a pretty generic approach
3.8 Disabling xxx-synchronisation with Google-servers
Go to settings, data synchonisation and disable the entries you don't want to have synch'ed with Google. Since it's long time ago since I did this (remember that I don't own a Tattoo anymore) the procedure can be slightly different from ROM to ROM.
3.9 Backing up apk's and data to your PC
By popular request, here a topic about how to backup apk's and their corresponding data manually (can be done separately, too if you want just one of the two). Doing it with the tar command HOPEFULLY preserves also all permissions!!! Check it:
Hit up adb shell and make sure have busybox:
Code:
for the apks
# tar -cvf /sdcard/dataAppsBackup.tar /data/app
for the data
# tar -cvf /sdcard/dataDataBAckup.tar /data/data
If you want to decompress these files again do:
Code:
# tar -xvf /sdcard/dataAppsBackup.tar -C /data
# tar -xvf /sdcard/dataDataBackup.tar -C /data
Note that these files won't be compressed! If you want to save some disk space on your SD then add the parameter 'z' (without the quotes) in the tar arguments (e.g. tar -cvfz for compressing and tar -xvfz for decompressing)
3.10 How to enable more languages on my mobile?
There is an app called MoreLocale in the market enabling you to select more languages. Download it, it's free
3.11 How to manually delete system apks? Alternatively with GUI?
For deleting manually you only need root-access. With GUI you need RootExplorer (buy it or do what you need to do to get this app-but with these features I would suggest to buy the app ).
Note: I do not take any responsibility if you delete the wrong apk and you lose any functionality of the phone. Do this only if you know what you're doing!
The manual way:
Connect the phone via USB, fire up adb shell and type:
Code:
insmod /LOCATION TO [URL="http://TATTOOHACK.KO/tattoo-hack.ko"]TATTOOHACK.KO/tattoo-hack.ko[/URL]
mount -o rw,remount /dev/block/mtdblock3 /system
cd /system/app
rm NAMEOFAPK.apk
The GUI way:
Install RootExplorer, open it, navigate to /system/app and press the little "Mount R/W" button at the top of the screen and begin deleting
4. Dev-Goodies
4.1 Modifying update.zips and resigning them
See this thread and get enlightened
4.2 Modifying resources in apk-files and resigning them
Same procedure as above:
1. Extract the file with WinRAR/WinZIP, delete the contents of META-INF and start modifying what you have to modify
2. Pack everything again into a ZIP file and sign it with the signapk.jar file (can be found somewhere in the forum or here). The syntax of how to use this can be found in the last link (yes, it's only 10 KB ).
4.3 Installing apks via adb for getting exact error codes if installation fails
Prerequisites: Either know the exact path to the apk or put it into the same directory as your adb executable and hit up your command line:
Code:
adb install /path/to/apk/file.apk
OR
adb install file.apk (implies that apk is located in same dir as adb)
4.4 Everything related to ROM cooking
Check this link (thanks to Decad3nce) and this one (thanks to mxlaser).
5. Things I will do better in this thread due to user request
- Nothing
The end for now.
Note: If you think that my thread is good, then please rate it with 5 stars
Changelog:
Version 1.0
- Initial draft
Version 1.1
- Added complete topic 1 now
- Fixed layout and some typos
Version 2.0
- Added complete topic 2 and half of 3
Version 2.1
- First prototype with all topics finished (will rework parts which are not quite understandable)
Version 2.2
- Added new question to 1.6
Version 2.3
- Added section 4.4 -> Everything related to ROM Cooking DUDEEEESSSSS
Version 2.4
- Added 3.11 How to manually delete system apks? Alternatively with GUI?
Version 2.5
- attached working su file - thanks to lovenemesis for this
Version 2.6
- added some mirrors for the Tattoo.rar archive - thanks to emb0re for providing some space
Version 3
- added topic about creating gold cards (2.3.1)
hi
very good initiative stuck
Great work
Very intuitive guide for beginner.
Though as an experienced and new android application developer, it really took me a whole afternoon to understand every step of the whole process. I am sure this guide would save many others wonderful Saturday afternoon.
Nice Work
Great Work From You Sir. This Will Be Useful for Beginners I Think This Will Save Lot Of Our Time's. And Mods Too
Thanks for the feedback...I hope that I can fill many topics tomorrow
P.S.: Indeed this is meant for the many unexperienced users who desperately want to flash custom ROMs but don't know how to do it...this also spares a lot senseless thread-posts I hope...^^
Dude
SSj Man Can You Add Tutorial Abt How to get the Apk file which i download from market in my mobile. if that is possible
3. We have every needed file on the phone now. Type now (we are still in your terminal):
- adb shell
$ cd /data/local/bin
$ while ./m7 ; do : ; done
lots of text until you see something like "wrote shell code", press enter 2 or 3 times enter to see:
#
Click to expand...
Click to collapse
For me I need to add execute permission for m7 before expolit, with
Code:
chmod 766 m7
.
jagan_3400 said:
SSj Man Can You Add Tutorial Abt How to get the Apk file which i download from market in my mobile. if that is possible
Click to expand...
Click to collapse
You mean getting the apk from your mobile on your PC for example?
lovenemesis said:
For me I need to add execute permission for m7 before expolit, with
Code:
chmod 766 m7
.
Click to expand...
Click to collapse
Hm, normally when you push the file via adb it will have user permissions, which includes execution...but I will add it to exclude any possible error...thanks for the info.
It might be worth to mention this in 3.1 Busybox installation:
Code:
adb push busybox /system/xbin/
I accidentallly use "adb push busybox /system/xbin" without the ending "/". Well, you know the rest part of the story...
Hmm, probably this one first, at least for the stock HTC ROM
Code:
adb shell "mkdir /system/xbin"
PS: Kind of weird for its name xbin, not the usual sbin on desktop linux. ;-)
TheSSJ said:
You mean getting the apk from your mobile on your PC for example?
Hm, normally when you push the file via adb it will have user permissions, which includes execution...but I will add it to exclude any possible error...thanks for the info.
Click to expand...
Click to collapse
Maybe it's because I am using a Fedora box, which the default permission for files in $HOME does not include execution.
lovenemesis said:
Hmm, probably this one first, at least for the stock HTC ROM
Code:
adb shell "mkdir /system/xbin"
PS: Kind of weird for its name xbin, not the usual sbin on desktop linux. ;-)
Click to expand...
Click to collapse
You're right, I added it already in the guide, thanks for the feedback. Well, /system/xbin isn't a "normal" directory indeed, but it was created for extra executables which normally aren't shipped in stock ROMs (like busybox).
4. Then perform this:
- # export LD_LIBRARY_PATH=/system/lib
- # export PATH=/system/bin
- # insmod ./tattoo-hack.ko
- # mount -o rw,remount /dev/block/mtdblock5 /data
- # mount -o rw,remount /dev/block/mtdblock3 /system
- # cat ./su > /system/bin/su
- # chmod 4755 /system/bin/su
Click to expand...
Click to collapse
I suppose after this step the stock ROM is rooted. Right?
But in Android Terminal Emulator gives me $ still. "su" reports an link_image error, which basically said about missing libbinder.so library.
Is it normal or I need to push an libbinder.so to /system/lib as well?
BTW: "adb shell " gives me # straightly.
Regards,
Hmm, I pushed another "su" binary to overwrite the one in Tattoo.rar. And now it works fine in Android Terminal Emulator.
Here is the su binary I use:
View attachment su.zip
Oops, Titanium Backup still refuses to work despite of working "su" binary.
What else should I do?
market not working
hi
i dont know why but the Market does not work for me can u give any solutions for the same im just not able to log in it keeps saying error i also tried with google mail and gmail id but no luck any suggestion pls
few questons kindly answer
hi
i have afew questions can u kindly answer
1. is wipe a must before flashing a new rom
i have flashed the Modoco rom and it was mentioned that this was not needed but i have read in many threads asking to do the same before flashing
2.to bring back contacts after flashing new rom can i use
a. backup pro or titanium backup
b. can i just use the out look sync and get back my contacts from my PC
3. if i restore the stock rom and latter on want to try one of the cooked roms do i need to do the rooting again ie does flashing stock rom remove the rooting
Note : i have been a WM user new to AM is why im asking such questions in the WM i have one app pim backup which would get back all my contacts in 1 min and when flashing any WM it will automatically wipe all the data from the phone this does not seem to be the case with AM is why i have asked above Questions
thanks in advance
lovenemesis said:
Oops, Titanium Backup still refuses to work despite of working "su" binary.
What else should I do?
Click to expand...
Click to collapse
Titanium Backup needs Busybox and su to work. If Titanium Backup tells you that it found BusyBox, then try to copy "su" to the following to locations:
/system/bin and /system/xbin
I think with the first it should work then.
haree said:
hi
i dont know why but the Market does not work for me can u give any solutions for the same im just not able to log in it keeps saying error i also tried with google mail and gmail id but no luck any suggestion pls
Click to expand...
Click to collapse
Do you use MoDaCo ROM or did u switch now to another? Normally the phone asks for log-in credentials when going online. When you enter them correctly, the login window should disappear and you should be able to access market...I know this sounds stupid, but check if you entered you PW correctly!
haree said:
hi
i have afew questions can u kindly answer
1. is wipe a must before flashing a new rom
i have flashed the Modoco rom and it was mentioned that this was not needed but i have read in many threads asking to do the same before flashing
2.to bring back contacts after flashing new rom can i use
a. backup pro or titanium backup
b. can i just use the out look sync and get back my contacts from my PC
3. if i restore the stock rom and latter on want to try one of the cooked roms do i need to do the rooting again ie does flashing stock rom remove the rooting
Note : i have been a WM user new to AM is why im asking such questions in the WM i have one app pim backup which would get back all my contacts in 1 min and when flashing any WM it will automatically wipe all the data from the phone this does not seem to be the case with AM is why i have asked above Questions
thanks in advance
Click to expand...
Click to collapse
1. As I told you via PM already: If the ROM is based on the same source ROM (HTC stock in your case) then a wipe is NOT required, but if you switch android version (AOSP, Vanilla, FroYo, Eclair) then you HAVE TO wipe.
2.
a) I had only problems with Titanium backup concerning restoring contacts. I would suggest using MyBackup Pro
b) Well, if you can sync to outlook, then I suppose yes, but I really doubt that these features are implemented in custom ROMs...
3. Well, if you mean restoring the NAND-backup and then flashing another cooked ROM (which are all rooted by default ), then no - you don't need to re-root. Only if you would flash the original/official HTC ROM which comes shipped as exe-file, but I don't see the sense in flashing this one...use your NAND-backups
TheSSJ said:
Titanium Backup needs Busybox and su to work. If Titanium Backup tells you that it found BusyBox, then try to copy "su" to the following to locations:
/system/bin and /system/xbin
I think with the first it should work then.
hi
thanks buddy for patiently answering all my Q
i got it now but i dont know why this Bl***dy market does not work what every i try ie when the net is on and ur browsing u see the E on ur phone screen and then the 2 white arrows flash this it self does not happen when i try to log in to market
just dont know what is wrong
right now im using Modoco and happy with it seems to be real fast and everything is working on this ROM
Click to expand...
Click to collapse
Welcome to GingerSense!
Please read this entire post and the two following FIRST, ask questions you have after reading them.
ROM is based on Evolutionary Sense by RCMix Team, ported to Incredible
This is a BETA rom. This means that anyone who downloads and installs this to their phone is therefor considered a BETA TESTER.
See post 3 for rules of testing!
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What's inside?
Desire HD (Ace) 2.36.405.8 WWE Release
Stock kernel (2.6.35.10) from Incredible_C Gingerbread leak
HTC Sense UI version 2.1 (Android 2.3.3 Gingerbread)
Extended Power Menu (with 4 in 1 reboot)
Quick Settings tab in notifications menu (with added settings)
HTC Kingdom lockscreen with buttons (Phone, Mail, Camera, Messages)
Lockscreen widgets!
Sense 3.0 MMS/SMS application
Sense 3.0 USB Menu
Sense 3.0 Task Manager (included in Quick Settings)
Polaris Office (replaces QuickOffice)
Screen On/Off animations (like AOSP)
AOSP Gingerbread Keyboard
Click to expand...
Click to collapse
What works?
Camera and Camcorder (thanks snq-!)
Wifi
Bluetooth
Video Playback
MMS! *thanks newtoroot
Verizon apps in Market *thanks JoelZ9614
much more...
Click to expand...
Click to collapse
What doesn't work?
MMS *fixed in Beta2
EMMC mount to pc
Lockscreen buttons have no icons
Netflix won't stream (w/ stock & modded apks)
No full-screen weather animations on homescreen *fixed in Beta3
Data shows EvDo instead of 3G *fixed in Beta3
[Google Maps causes soft reboot *fixed in Beta4
still looking for more bugs...
Click to expand...
Click to collapse
Thanks/Credits
Robocik, Capychimp, and Seo from RCMix team for allowing me to use their rom. Thanks guys!
Virus for help (with apktool especially) and his updater-script I used as a template
snq- you're a beast, man.
rmk40 for his stock boot.img
911htc for the Incredible_C gingerbread leak, this wouldn't be possible without it!
HTC for a kick ass phone!
Google, for android. Duh.
TokedUp for hunting down bugs like they owed him money
newtoroot for the original MMS fix! (kudos for original lockscreen fix!)
Vernox701 for the MMS hint (build.prop edit)
JoelZ9614 for Verizon apps in market + theming help
if I missed anyone, please let me know!
Click to expand...
Click to collapse
Flashing procedure/requirements:
ClockWorkMod 3.0.0.7+ required!
1. Download ROM and VR_SUPERWIPE.zip (modded to work on CWM3)
2. Transfer ROM and VR_SUPERWIPE.zip to SD card
3. Reboot phone to recovery
4. Make a nandroid backup (not required, but helpful)
5. Flash the VR_SUPERWIPE.zip FIRST! This will wipe all partitions on your phone, including: boot, data, system, and cache.
6. Wipe data/factory reset.
7. Flash GingerSense ReMix. When the install completes, reboot phone.
8. Let the phone boot to the lockscreen. Don't unlock the phone yet!
9. This ROM needs to sit for a good 5 minutes before unlocking fr the first time. It might be tough, but just leave it on the counter and watch some XDA TV
That's it! enjoy the rom! If you have an issue, please follow the procedure for reporting a bug in the third post
NilsP said:
Navigation is working good but can be finicky so:
1) Put Maps, Navigation, and GPS settings shortcuts on the desktop
2) Toggle GPS on
3) Make sure the icon toggles on (No \) and off (\) on the notification bar
4) If GPS icon shows on then open maps
5) If maps works you are good to go with anything depending on GPS.
NOTE: If the slash does not go away on the GPS notification icon keep toggling until it goes on and off consistently
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Download:
Beta1:
GingerSense_ReMix-B1-INC.zip
Click to expand...
Click to collapse
Beta2 (full wipe recommended):
GingerSense_ReMix-B2-INC.zip
Click to expand...
Click to collapse
Beta3 (full wipe recommended):
GingerSense_ReMix-B3-INC.zip
MegaUpload link
Click to expand...
Click to collapse
Beta4 (full wipe recommended):
http://www.multiupload.com/TZO1IK6QHI
MD5: 175ade1a2e8312fbe45ac398b53a4099
MegaUpload link is still uploading
Click to expand...
Click to collapse
CHANGELOG
Beta4 (5/28)
New method for lockscreen icons/caller id (no EGL changes) (snq- is a BEAST)
No more gps bug
Higher-quality weather animations for Weather 3.0 (emin3sku)
New weather sounds (baadnwz)
Maps 5.5 modded for global navigation (Ownhere)
Added back Weather LWP and a new "secret" LWP
Updated htcreader (robocik)
Undead/Phantom Call fix as init script (thanks bftb0)
Beta3 (5/26)
Sense 3.0 weather! (snq-, robocik, Krzysiec)
Working animation videos in weather app (re-encoded by emin3sku)
Full screen weather animations with sound! (robocik)
Updated TaskManager (Krzysiec)
Stock MMS app with "bubbles" and backup/restore. Uses less ram. (seo)
Refreshed libs (robocik)
3G icon instead of EvDo (thanks for the help JoelZ9614)
Removed location icon in notification bar (JoelZ9614)
DSP Manager (Cyanogenmod)
might be more...
Beta2 (5/24)
MMS FIXED! (HUGE thanks to newtoroot, Virus, and Vernox701)
Correct time format (12 hour)
Correct date format (DD/MM/YYYY)
Fahrenheit instead of Celsius
English (US) by default in setupwizard
Removed A2SD-related init scripts
Optimized more (feels smoother)
Probably more I don't remember...
Beta1
initial release
Rules for Beta Testing:
1. Please only report a bug if you have done a full wipe before flashing.
2. If possible, factory reset and re-flash rom, then see if the issue(s) still exist
3. How to report a bug/issue (please use this format):
Steps needed to re-produce the issue?
What was running at the time? BE SPECIFIC (apps, GPS, wifi/3g, etc.)
List what version of the software you are using
Describe what happens after the error (ex: hot-reboot, hard reboot, bootloops, etc.)
List ANY mods/themes/tweaks used on top of a fresh install
A logcat of the issue is GREATLY appreciated. If you need help, PM me.
Screenshots are also very much appreciated.
Post any other useful information (setup info, ideas, etc.)
________________________________________________________________
How to set up the Android SDK and ADB:
If you're on windows, you'll do the following:
1. Download the installer here: http://dl.google.com/android/installer_r11-windows.exe
2. Run the installer, and follow the steps. If it asks to install java, go ahead and install it. Then, choose where you want the SDK to be installed (I use C:\asdk for ease of use).
3. When the installer finishes, go to you're install location and open the SDK Manager.exe
4. A dialog should pop up with a list of updates. Click the "Accept All" bubble and click OK.
5. After the download is finished, check the list of installed packages, and make sure the "Google USB Driver package" is in the list.
6. Plug your device into the computer's USB port. On the phone, make sure USB debugging is on (check the notification area). If it's not on, go to Settings->Applications->Development and check USB debugging.
7. Go to you're Device Manager in windows by right-clicking "My Computer" in windows explorer, then clicking "Manage". In the application that opens, click "Device Manager" on the left side.
8. You will see something like "Android phone" under Other Devices; there should be an exclamation point next to it.
9. Right click that, and select "Update driver software" or something similar.
10. In te window that pops up, choose to browse for the driver manually. In the next window, select "Let me pick from a list of drivers on my computer"
11. Select "All Devices", then click "Have Disk". In the dialog that appears, enter the location of your downloaded driver (in my case: C:\asdk\extras\google\usb_driver). Click OK
12. A list of Android drivers should show up. Select "Android ADB Interface", then Next. Click Yes if it asks.
13. Use the Windows key + R to bring up the run dialog box. Type "cmd" (without quotes). Command prompt should pop up.
14. Type the following, pressing enter at the end of each box below:
Code:
cd C:\asdk\platform-tools
*modify this line with the path to your sdk
Code:
adb devices
*should show "HTXXXXXXXXXX device". If it does, you have adb installed correctly!
Code:
adb logcat > logcat.txt
*this starts the logcat, and ">" outputs the logcat to a file
15. Once the phone reboots, press Ctrl + C to stop logcat, if it hasn't already. Take the logcat.txt file, and upload it to pastebin.com. PM me the link
If you need more help, feel free to ask. I wrote this from memory, so I may have made an error or two. It looks pretty right to me
Click to expand...
Click to collapse
How to add ADB and other SDK tools to your PATH variable:
Adding a folder to your PATH variable makes it so you can execute adb, aapt, ddms, zipalign (and other useful development tools in your SDK) from any folder on your computer, saving you from having to type the whole path to these binaries.
I will be teaching you to do this for the folders inside your SDK, but the same procedure can also apply to any other folder on your computer, just change the path to the folder as needed.
I assume in this guide that you already went through the steps of setting up the sdk posted above...
In Windows:
1. Open up an Explorer window
2. Right-click My Computer, then click Properties
3. In the window that pops up, click "Advanced System Properties"
4. At the bottom of the box that pops up, click on the "Environment Variables" button
5. Look at the top list, look for "PATH". If you don't see "PATH", click the "New..." button. (if not, skip to step 6)
a. In the "Variable name" text box, type "PATH" (uppercase, no quotes)
b. In the "Variable value" text box, enter the path to your android sdk, followed by \tools or \platform-tools. Separate paths with a semicolon ";" (ex.: "C:\asdk\tools;C:\asdk\platform-tools" without quotes)
6. If a PATH variable exists already, simply click the "Edit..." button and use the same instructions as in steps 5a and 5b
7. When finished entering paths, click OK.
8. Click OK again to save the settings.
9. To confirm it worked, press "WINDOWS BUTTON" + R to bring up the Run prompt, and type "cmd" (without quotes). In Command Prompt, type adb, and if you get any output either than "'adb' is not recognized as an internal or external command, operable program or batch file.", you're good to go!
Click to expand...
Click to collapse
Gotta love the 3.0 lockscreen
f5 f5 f5 f5
YESSS!! Could this possibly include the Sense 3 Mail.apk? I love the exchange features...
Yeah this weekends going to be a flash fest I can see it now.
Sent from my ADR6300 using Tapatalk
I can edit and save that in notepad and itll be fine right? New to the whole inner workings of these scripts and coding in general... complete noob actually
I would flash this right now if MMS worked.
Drewsipher said:
I can edit and save that in notepad and itll be fine right? New to the whole inner workings of these scripts and coding in general... complete noob actually
Click to expand...
Click to collapse
I would suggest using a program called Notepad++, as it wont destroy the UNIX "new-line" invisible character that windows hates.
I have also found a few more errors after the one posted, so I'm updating the op with something you guys can copy/paste to make it easier.
Again, sorry for the inconvenience. I feel like such a noob right now...lol
wdfowty said:
I would suggest using a program called Notepad++, as it wont destroy the UNIX "new-line" invisible character that windows hates.
I have also found a few more errors after the one posted, so I'm updating the op with something you guys can copy/paste to make it easier.
Again, sorry for the inconvenience. I feel like such a noob right now...lol
Click to expand...
Click to collapse
your also gonna re-upload it right? >.<
it won't install. I realized MMS was not texting lol. so i tried and it no work!
This looks like the perfect median to stability and sense 3.0. I actually run 3.0 w/ little problems; the only bug I found was graphical issues in the weather app but it was laggy and heavy. The only thing I really loved in 3.0 was the task manager and the lockscreen w/ widgets but since this has it and is stable I will flash this once it's ready. Do you know if the HTC Sense 3.0 Camera (XDA Thread) will work because it works on the Kingdom port. This isn't a deal breaker just would make the rom more awesome.
Just my opinion because I haven't downloaded most of the ports are based from Sprint phones and they sometimes leave in the sprint settings could that be the issue for mms not working?
Drewsipher said:
your also gonna re-upload it right? >.<
Click to expand...
Click to collapse
Of course
I'm uploading right now to multiupload, gonna take an hour and 45 min with my crappy connection.
Vernox701 said:
Just my opinion because I haven't downloaded most of the ports are based from Sprint phones and they sometimes leave in the sprint settings could that be the issue for mms not working?
Click to expand...
Click to collapse
Quite possibly. I ported this directly from the Desire rom. I'm looking into it
Does this have Darktremor's A2SD script? if not i'm flashing in a couple days
PGleo86 said:
Does this have Darktremor's A2SD script? if not i'm flashing in a couple days
Click to expand...
Click to collapse
Yes, A2SD is built-in
wdfowty said:
Yes, A2SD is built-in
Click to expand...
Click to collapse
Does it automatically move all the Apps to the sd card or can you choose not to do it?
Sent from my Droid Incredible Running CM7
Thank you for posting and ROM and not a DUE DATE looks clean
hightech316 said:
Thank you for posting and ROM and not a DUE DATE looks clean
Click to expand...
Click to collapse
Amen brother
Sent from my Incredible using XDA App
This is a 100% AOSP ICS build for the Lenovo Ideapad K1. It will wipe your entire system. You will lose all data except what is stored on the EXTERNAL sdcard.
Includes
Android ICS 4.0.4
ClockworkMod Recovery 6.0.1.0
Google Apps
Rooted version includes Superuser and busybox
Issues
Video Camera face effects
Rotation Lock Switch (Software switch works)
Downloads
As always flash at your own risk. I'm not responsible for your device.
Nvflash versions
K1_ICS_AOSP_Rooted_R2.zip
dfddf13bf51e357a4964a11a8adbfd53
Mirror
K1_ICS_AOSP_Stock_R2.zip
b359ec6a06289ccf8c6b83f07346be17
Mirror
CWM versions
CWM_K1_ICS_AOSP_Rooted_R2.zip
90341324a0927f3035e92dc81ffb9416
Mirror
CWM_K1_ICS_AOSP_Stock_R2.zip
c026beb4dc2a11defbc3c3bcbec041cc
Mirror
Instructions
Nvflash version
1. Download one of the packages above and extract it to a directory
2. Power off device
3. Press and hold both the Vol + and Vol - buttons
4. While holding both Volume buttons power the tablet on
5. The screen should go black and the two front LED's should remain lit. You are now in APX mode
6. Connect your device to USB
7a) Windows: Install the APX drivers from the 'drivers' folder
Double click the 'flash-windows.bat' file
7b) Linux: run 'chmod +x flash-linux.sh && sudo ./flash-linux.sh' from the extracted directory
CWM version
1. Download one of the CWM_K1_*.zip versions and move to external sdcard
2. Reboot into recovery
3. Install zip from sdcard
4. Choose zip from sdcard
5. Flash the update.
How to boot into recovery
Non-rooted version
1. Make sure you have the Android SDK installed. http://developer.android.com/sdk/index.html
2. Make sure USB Debugging is enabled on the tablet. Go to Settings > Developers options > and check "USB Debugging"
3. Connect the device to USB
4. Open a terminal or command prompt window and type
Code:
adb shell k1recovery
Rooted version
From a Terminal Application
Run the follow two commands
Code:
su
k1recovery
From adb
1. Make sure you have the Android SDK installed. http://developer.android.com/sdk/index.html
2. Make sure USB Debugging is enabled on the tablet. Go to Settings > Developers options > and check "USB Debugging"
3. Connect the device to USB
4. Open a terminal or command prompt window and type
Code:
adb shell k1recovery
Changelog
Code:
8/11/2012 R2
-Fixed external sdcard permissions
-Fixed keylayout
-Modifed build.prop to spoof Moto Xoom (App compatibility)
7/31/2012 R1
-Initial Release
Source Code
http://github.com/khanning
So from now on we will be able to flash future updates through recovery without wiping everything?
So from now on we will be able to flash future updates through recovery without wiping everything?
Click to expand...
Click to collapse
Exactly, future updates will be CWM flashable .zip's.
All, I just noticed that Google Chrome isn't showing in the market, but Maps is. I swear it was showing up when I was testing previously. Will have to investigate...
khanning88 said:
Exactly, future updates will be CWM flashable .zip's.
All, I just noticed that Google Chrome isn't showing in the market, but Maps is. I swear it was showing up when I was testing previously. Will have to investigate...
Click to expand...
Click to collapse
I dont know if it's me or because of the ROM. WIth the rooted ROM before AOSP, I was able to install Chrome with a APK downloaded from mobilism but sometimes the pages are fine then just rendered white , for all tabs.
Does anybody use SKYPE ? When I do video chat, my broadcast picture stretched vertically when I broadcast-only (no picture feed from the other side), the picture my friend saw is fine though.
Many thanks for your hard work.
That is the main thing that i hate about Lenovo's Factory ICS image, i still cant install Chrome or Evernote, or many of my NEEDED apps. I hope that you get this working soon. or at least a temp fix.
Just flashed the rooted aosp, the boot animation is a nice touch. The app compatibility issue seems fully resolved outside of Chrome, pointed out already, which is no biggie for me atleast. I still can sideload Chrome and runs perfectly. Also, so far the dictionary miss-spell issue doesnt seem to be a problem anymore. Maybe its just me but touch responsiveness seems a little better/quicker with this build. Just tried using the command 'k1recovery' to boot into recovery and it keeps giving me an error relating to permissions, saying it cant create /dev/block/mmcblk0p5. Seems like I just need to change the permissions of the /block folder but wasnt sure if I was just not doing something right.
Massive improvements from Lenovo's vanilla ICS still, thanx khanning!
Noticed some graphical glitches. Screen goes black if switching orientations on lockscreen and home screen.
@Khanning88 Can you provide a mirror please? Goo.im is down and shows "Internal server error".
Never mind. It's up again.
me_is_rushin said:
Noticed some graphical glitches. Screen goes black if switching orientations on lockscreen and home screen.
Click to expand...
Click to collapse
Yup the screen flashes when switching orientations, for a split second...
That's great. thanks for share.
Flashed this one and works wonderful.
Rebooting to recovery didn't work 1st, but then mounted filesystem as rw and tried the command and could get to recovery.
Got an error "Can't mount backup path" when trying to make a backup. Is it because I didn't have an external sd card.
If yes, is there a way to take a nandroid backup to internal memory?
BTW, thanks again for providing this ROM.
Thanks khanning88 for giving this fabulous AOSP ROM
Does this ROM support the Wifi+3G version?
I found some issues installing apps, including some games, Zinio magazine reader, google earth, etc, all saying incompatible with my device.
I experienced alot of freezes while restoring my backup with titanium backup.
I keep testing if it also occurs in normal use.
Installed AOSP-Rooted. So far, Chrome (already noted as issue in OP), and POGO Games showing up as Incompatible.
Other than that, and possible other apps being incompatible, looks great and installed as easy as can be.
Thanks Khanning!
-Cybie
we need an easy way to enter recovery. Rom Manager button doesn't work.
Reboot recovery from terminal emulator doesn't work either.
Could you implement the nice options when turning the unit off?
several more freezes. obviously not depending on any special app..
erickwan said:
Does this ROM support the Wifi+3G version?
Click to expand...
Click to collapse
I'm not sure if 3G works since I have a Wifi version, but if someone with a 3G version could meet me in freenode IRC room #ideapad-k1 I would be happy to work on it. If you aren't familiar with IRC just go to this link and join the chat.
http://webchat.freenode.net/?channels=ideapad-k1
we need an easy way to enter recovery. Rom Manager button doesn't work.
Reboot recovery from terminal emulator doesn't work either.
Could you implement the nice options when turning the unit off?
Click to expand...
Click to collapse
From a terminal app type:
Code:
su
k1recovery
Or from adb type:
Code:
adb shell k1recovery
Either method will reboot the device into recovery. I will work on adding the power menu options later.
several more freezes. obviously not depending on any special app..
Click to expand...
Click to collapse
I haven't experienced any "freezes" but when it happens to you could you please document what you were doing and take a logcat to help debug.
http://rootzwiki.com/topic/11930-learn-to-logcat-like-a-pro/
Here is a very simple way to reboot into khanning's CWM recovery.
1. Playstore --> Download/Install aShell app
2. Run App
3. Select Checkbox for "Root" (In Settings, you can set app to start Root as Default)
4. type "k1recovery" into textbox
5. press "start command" button.
Simple, no need to be in "true shell" mode. This app allows you to run shell commands without the terminal. Great for newbies, quicker for anyone.
Hope this helps!
-Cybie
Here is a quick fix for the hardware keys. Just flash the .zip file from recovery. Updated first post with more detailed booting into recovery instructions.
K1_keylayout_fix.zip
Hi, if anyone would like to run a 4.3.1 Google OS on a Archos G9 80S device (and currently only this), download and extract this file:
19_01_2014-13_32_32
Installation (tested only with linux) :
- reboot into SDE menu and under "Format System" perform a "Reset Android & Storage" to clear all data of previous installations (this is really important!).
- reboot into SDE menu and under Developer Edition Menu -> "Export Data Partition"
- mount this usb drive
Code:
sudo mkdir <Mount_Path>/local
sudo cp archos.ext4.update <Mount_Path>/local/archos.ext4
sudo sync
sudo umount <Mount_Path>
- wait until the unmount process is done
- 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
- Wait for reboot your devices : after reboot you can see Android prepares the system for a while .....be patient !
What's new ?
------------ since 19_01_2014-13_32_32 -------------
Last attempt to satisfy "H" model users. Wrong fstab definition file was used.
ArchosControlCenter: Alternate command for enabling disabling 3G service activation/deactivation.
------------ since 17_01_2014-20_17_32 -------------
KSM (Kernel samepage merging) support. (Enable it in CM performance options).
HDMI enable for 101 models too.
WLAN MAC address taken from device. Until now in my releases, the MAC address where the same for all devices. (gave some conflicts, when two devices are used in parallel).
------------ since 22_12_2013-13_29_20 -------------
Deactivated PCB temperature sensor. It is not part of the devices, and (my) default setting gives the cpufreq
module a wrong view of the situation. Now it should reduce the reboot which is caused by critical temp, by reducing core speed.
------------ since 19_12_2013-23_43_36 -------------
Using CPUFreq from 3.0.31 omapzoom reference kernel
Included app from @mordesku (modified by me) -> 3G should work!
Note that if you only pushed the image as update, please make sure to delete the /data/data/com.android.providers.telephony/databases/telephony.db
(adb shell rm /data/data/com.android.providers.telephony/databases/telephony.db) and reboot the device to rebuild.
I forgot to include the apns-conf.xml so there are no APN's available (as result no data connection can be established).
Removed my Widget to not affect the archos control center app
Some kernel changes.
Enabled zram and init.d
Initial support for H models (testing and patches are welcome).
Newest CM Updates: Changes since last release
------------ since 02_12_2013-22_56_07 -------------
Removed clicks when audio driver is closed
Reduced the volume a little bit to avoid scratches
Removed default dpi setting on build
Newest CM Updates: Changes since last release
------------ since 21_11_2013-21_45_53 -------------
Using new pvr library SGX-BIN: DDK binaries and KM source [email protected]
HWComposer 1.1 interface
No ICS audio blob anymore. Adapted omap upstream audio HAL.
Some internal audio extensions by TI (omap_enhancement)
Kernel audio sources updated to 3.0.31 omap upstream release.[/INDENT]
------------ since 08_11_2013-22_14_52 -------------
CM10.2
Upstream init.rc
TI Openlink WLAN driver R5.SP6.01
Temporary disabled ClockworkMod Recovery
A widget "Archos Control Center" where the user can activate the deep sleep behavior. Warning: If you use the archos as alarm clock you will oversleep! (It only will wake up, when pressing the power button).
Also the 3G port can be activated with this widget. I discovered some hangs, which can only solved by removing and re-adding the widget on the screen. If someone can help me with this widget, please have a look at: github It's my first app ever... so it is very ugly =)
Initial A101s support.
Something I've not tried...
3G USB Stick is working.
Issues:
- GPS not reliable (as usual for every release....) -> After complete new system ("Reset Android & Storage") the GPS is working very good. Subsequent boots later it gets worse at my device(s):
My Workaround: Go into Settings->Apps->All->Google Service Framework and delete data and cache. Then reboot and GPS should e working. Also I get sufficient results with the GPS Toolbox App.
21_11_2013-21_45_53:
Microphone as degraded sound quality compared to the stock rom.
Some sound clicks here and there when system sounds are turned on.
Audio sound is a little bit quiet compared to the stock rom. (Needs to be adjusted by myself).
Can't test HDMI (both audio/video). (It's also not an use case for me). If someone would like to help....
HDMI scaling issues
"H" models doesn't seem to work.
Rebuild: All used revisions for this release are stored in a separate folder in the archive.
Additions:
Archos Control Panel App from @mordesku: http://forum.xda-developers.com/showpost.php?p=47789812&postcount=88
Archive:
17_01_2014-20_17_32
22_12_2013-13_29_20
19_12_2013-23_43_36
02_12_2013-22_56_07
21_11_2013-21_45_53
08_11_2013-22_14_52
07_11_2013-22_53_33
Archos CM10.2 - 26_10_2013-23_26_11
Thanx for your work now i'm bakcig up my data and will test as soon as possible. Is this build run from disk images or it replace original archos system?
mordesku said:
Thanx for your work now i'm bakcig up my data and will test as soon as possible. Is this build run from disk images or it replace original archos system?
Click to expand...
Click to collapse
As usual for the custom Android releases for this archos device , they don't replace the original partitions. But it is not possible to run both in parallel. So practically yes, it replace the original system.
Quallenauge said:
- Wait for reboot your devices : after reboot you can see Android prepares the system for a while .....be patient !
Click to expand...
Click to collapse
Hi again. My tab is displaying archos logo for long time (about 10-15 minutes) now is this normal. I have question where exacty i should put the update file. In debian i put it to /media/data/data/local where /media/data is my mount point.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
mordesku said:
Hi again. My tab is displaying archos logo for long time (about 10-15 minutes) now is this normal. I have question where exacty i should put the update file. In debian i put it to /media/data/data/local where /media/data is my mount point.
Click to expand...
Click to collapse
Sorry, my fault.....
Can you please rename the file while you copy? (I have corrected my first post).
Code:
sudo mkdir <Mount_Path>/local
sudo cp archos.ext4.update <Mount_Path>/data/local/[B]archos.ext4[/B]
Quallenauge said:
Sorry, my fault.....
Can you please rename the file while you copy? (I have corrected my first post).
Code:
sudo mkdir <Mount_Path>/data/local
sudo cp archos.ext4.update <Mount_Path>/data/local/[B]archos.ext4[/B]
Click to expand...
Click to collapse
(Just for reference, when using the update mechanism the file has to placed here:
Code:
sudo cp archos.ext4.update <Mount_Path>/data/[B]media[/B]/archos.ext4.update
)
Quallenauge said:
Sorry, my fault.....
Can you please rename the file while you copy? (I have corrected my first post).
Code:
sudo mkdir <Mount_Path>/data/local
sudo cp archos.ext4.update <Mount_Path>/data/local/[B]archos.ext4[/B]
Click to expand...
Click to collapse
Renamed file as you said but still tab is stuck on archos logo.
--- edit
My bad . Got to many data directories. Rom boots form /media/data/local/archo.ext4 before was /media/data/data/local/archos.ext4
mordesku said:
Renamed file as you said but still tab is stuck on archos logo.
--- edit
My bad . Got to many data directories. Rom boots form /media/data/local/archo.ext4 before was /media/data/data/local/archos.ext4
Click to expand...
Click to collapse
Thanks for your reply. I corrected the paths in previous posts.
Is it stable for very day use???
Everithing working lie Cam and HW video?
Using it since yesterday. It's very smooth and fast. No freezes at all.
Sent from my ARCHOS 80G9 using Tapatalk 4
Installation on Mac OS X
For those of you who want to brave installation from a Mac, you can use FUSE to mount the data partition. You'll need to follow the directions here to be able to mount the partition with write access. Once the partition is mounted, follow @Quallenauge's fabulous instructions! I'm watching a spinning CyanogenMod logo right now!
Note: If you copy the file from the command line, you'll probably get a message saying "could not copy extended attributes to data/local/archos.ext4: Operation not permitted". Don't worry, the file copied just fine. If you're really paranoid, run md5sums on the file to verify.
- Dave
stealthdave said:
For those of you who want to brave installation from a Mac, you can use FUSE to mount the data partition. You'll need to follow the directions here to be able to mount the partition with write access. Once the partition is mounted, follow @Quallenauge's fabulous instructions! I'm watching a spinning CyanogenMod logo right now!
Note: If you copy the file from the command line, you'll probably get a message saying "could not copy extended attributes to data/local/archos.ext4: Operation not permitted". Don't worry, the file copied just fine. If you're really paranoid, run md5sums on the file to verify.
- Dave
Click to expand...
Click to collapse
Damn to install it yesterday i installed debian on virtualbox on my macbook
Sent from my ARCHOS 80G9 using Tapatalk 4
My tablet is still showing the snazzy CyanogenMod bootloader image after an hour and refuses to load the Android GUI. I tried starting the process over again with the same results. I am able to get to an adb shell and play around there, but Android never finishes loading. I'm running a G9 80S with 1GHz OMAP 4430 and 512MB of RAM. Logcat attached.
Hi,
thank you for building this and all your other ROMs.
Quallenauge said:
Code:
sudo mkdir <Mount_Path>/local
sudo cp archos.ext4.update <Mount_Path>/data/local/archos.ext4
Click to expand...
Click to collapse
This is inconsistent.
Is it local/ or data/local/?
I tried to install the ROM following your instructions.
I renamed "archos.ext4.update" to "archos.ext4".
I reset Android and Storage, exported the USB storage, on my machine it was mounted on /media/username/data.
I then used the following commands:
Code:
sudo mkdir /media/username/data/local
sudo cp archos.ext4 /media/username/data/local/
Then I selected "OK" in the tablet and "Flash Kernel and Initramfs" followed by:
Code:
sudo cp zImage /media/username/A80S_REC/
sudo cp initramfs.cpio.lzo /media/username/A80S_REC/
Then I rebooted the tablet.
Now the tablet was flashing the Archos logo for a second and then rebooting, in a loop.
So I guessed the local/ directory was wrong and I might have to use data/local/.
I repeated the steps above, replacing "local/" with "data/local".
This time the tablet didn't reboot in a loop, but I only got the static Archos logo, not the animated Archos logo or the CyanogenMod logo.
I probably missed a step or misread some instruction.
Any idea where I made the mistake?
@esque: Sorry for the confusion... Your first attempt was right:
Code:
sudo mkdir /media/moronoxyd/data/local
sudo cp archos.ext4 /media/moronoxyd/data/local/
@all: Please perform an unmount before pressing "OK" on the device. If not, the image is broken!
Just to be sure, reboot the tab and mount the drive and perform a
Code:
md5sum <Mount_Path>/local/archos.ext4
and verify that value with the image on your host.
If there are the same values, we have to find another solution for the problem.
@stealthdave: Your logcat file looks very close to the problem above (file image broken).
Quallenauge said:
@stealthdave: Your logcat file looks very close to the problem above (file image broken).
Click to expand...
Click to collapse
Yes, that was the issue. umount for everyone!!!
Thanks.
Great job, like buying a new tablet.
The only thing I would add is to sudo sync before unmounting.
Quallenauge said:
@all: Please perform an unmount before pressing "OK" on the device. If not, the image is broken!
Click to expand...
Click to collapse
D'oh! I knew I made a rookie mistake.
Yes, that did the trick.
Thanks Again!
Hi,
Great job.
Is there a possibility to have the same ROM for the 101 version ?
Regards
Sent from my Galaxy Nexus using xda premium
Hi,
After two days of using this rom I must say it is very fast and smooth. But on idle after 6 hours I got -40% battery drain. Also I can feel heat from it. Got installed only 2 apps and one game. Is there any chance to implement deep sleep in this rom, to minimize batery drain?
Hi, if anyone would like to run a 5.1.x Google OS on a Archos G9 80S device (and currently basically verified only with this), download and extract the file
16_12_2015-16_26_24
Installation (tested only with linux) :
- reboot into SDE menu and under "Format System" perform a "Reset Android & Storage" to clear all data of previous installations (this is really important for the first installation. Updating a existing installation (same major version) doesn't require this step !).
- reboot into SDE menu and under Developer Edition Menu -> "Export Data Partition"
- mount this usb drive
Code:
sudo mkdir <Mount_Path>/local
sudo cp archos.ext4.update <Mount_Path>/local/archos.ext4
sudo sync
sudo umount <Mount_Path>
- wait until the unmount process is done
- 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
- Wait for reboot your devices : after reboot you can see Android prepares the system for a while .....be patient at least ~20 minutes for the first run!
!!Update!!: If you have already installed CM12.0 then it may possible that you don't have to delete the data partition. You only have to copy the kernel/initramfs and ext4 file. I use the command for the last step:
Code:
adb push archos.ext4.update /data/media/ && adb reboot
What's new ?
------------ since 16_12_2015-16_26_24 -------------
Added usual CM updates. -> Also this release include the latest security fixes.
------------ since 05_08_2015-05_48_32 -------------
Added usual CM updates. (See included changelog for details) -> Also this release include the latest security fixes.
Added the 99Performance file from BlackGunZ Big thanks!
------------ since 31_05_2015-19_39_10 -------------
Added usual CM updates. (See included changelog for details)
Add *some* memory improvements, suggested by trevd (big thanks!)
*Maybe last release*
------------ since 23_04_2015-22_05_13 -------------
Initial release.
Re-Enabled Non-PIE Support to support the gps module.
Rebuild: All used revisions for this release are stored in a separate folder in the archive.
Additions:
Archos Control Panel App from @mordesku: http://forum.xda-developers.com/showpost.php?p=47789812&postcount=88
Thanks: @stargo @Hashcode @trevd
@CM community @all the cool omap4 hackers where I taken some code and inspirations !!!
Without these peoples, It would not so easy to make some (working) builds of the CM-12.1.
Archive:
31_05_2015-19_39_10
23_04_2015-22_05_13
XDA:DevDB Information
Archos G9 CyanogenMod 12.1, ROM for the Archos Gen9
Contributors
Quallenauge
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: Cyanogenmod
Version Information
Status: Alpha
Created 2015-04-24
Last Updated 2015-04-24
Thanks for keeping this old tablet going! I'll give it a try this weekend. :good:
jawiler said:
Thanks for keeping this old tablet going! I'll give it a try this weekend. :good:
Click to expand...
Click to collapse
Hi Quallenauge,
I've tried installing this version, but it just goes to a black screen for over 1/2-3/4 hour. I've tried downloading from both sites and checked the MD5SUMs and everything checks out. I went with a clean install.. I've installed your previous versions without any problems. Any ideas?
thanks
Nevermind, I tried a different computer and it worked this time
jawiler said:
Hi Quallenauge,
I've tried installing this version, but it just goes to a black screen for over 1/2-3/4 hour. I've tried downloading from both sites and checked the MD5SUMs and everything checks out. I went with a clean install.. I've installed your previous versions without any problems. Any ideas?
thanks
Nevermind, I tried a different computer and it worked this time
Click to expand...
Click to collapse
Mostly this error comes into play if the kernel&initramfs step or the update package is transferred and the mass storage drive is not cleanly unmounted.
@Quallenauge I knew I should have waited as I've just built cm-12.0 .... I even used your build environment script. Slightly unorthodox but it gets the Job done :good:
Anyway couple of notes from my side .. a bit of dex_preopting does wonders for the boot time
In the full_archos_g9.mk or similar
Code:
WITH_DEXPREOPT := true
WITH_DEXPREOPT_PIC := true
PRODUCT_DEX_PREOPT_BOOT_FLAGS := --compiler-filter=everything
PRODUCT_DEX_PREOPT_DEFAULT_FLAGS := --compiler-filter=everything
$(call add-product-dex-preopt-module-config,services,--compiler-filter=everything)
Not 100% sure that WITH_DEXPREOPT_PIC is required I threw it in anyway...
I also read up on low memory optimizations ( tricks/hacks ) , dropped all the wallpapers and a ton other other apps that I'm not using
It's pretty smooth ... That can be done at runtime by anyone who is feeling brave .
Hackon folks!
trevd
trevd said:
@Quallenauge I also read up on low memory optimizations ( tricks/hacks ) , dropped all the wallpapers and a ton other other apps that I'm not using. It's pretty smooth ... That can be done at runtime by anyone who is feeling brave .
Click to expand...
Click to collapse
Hi @trevd, I always follow your advice therefore I wonder what changes have you applied to optimize this rom? Could you give us any clue?
Thanks in advance
@Quallenauge First, thank you for your great port and efforts ! God bless you.
I found how to fix the root problem by doing some researches. For so, I edited the following line persist.sys.root_access which is present in build.prop file like this :
Code:
persist.sys.root_access=1
After a reboot, my tablet is correctly rooted and Archos Control Panel enables normally the deep sleep mode at boot.
Have a good day !
Hi! Any chance, to use working USB Stick?
BlackGunZ said:
I found how to fix the root problem by doing some researches. For so, I edited the following line persist.sys.root_access which is present in build.prop file like this
Click to expand...
Click to collapse
Hey, could you explain how you do that?
I have CM 12.1 installed on my Archos 80 G9, ADB is working and when I use 'adb shell' I'm supposedly root but can not write to /system.
I can pull the build.prop and change it, but I don't know how to put it back onto /system.
esque said:
Hey, could you explain how you do that?
I have CM 12.1 installed on my Archos 80 G9, ADB is working and when I use 'adb shell' I'm supposedly root but can not write to /system.
I can pull the build.prop and change it, but I don't know how to put it back onto /system.
Click to expand...
Click to collapse
Of course ! The most secure method is to edit the build.prop with CM File Manager.
Before, using ADB put this command after "adb shell" to mount your /system partition RW. After, do the steps I said below :
Code:
mount -o remount,rw /
First, open the file manager. Then, access to the app's options by taping on its icon at the left and choosing after that its settings icon, which is present at the left down side. Go to Advanced section and tap on Access mode next, choose Root access by this way the app will ask root permissions and a pop-up will appear to accept it. You will be redirected to the root (/ directory) of your Archos, scroll down again and go to /system directory. Screenshots :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Secondly, tap on your build.prop file and open it with the file manager's text editor. Choose the line persist.sys.root_access, delete the "3" value and put "1" instead. Screenshots :
Finally, save the file and reboot your phone. Voilà !
esque said:
I can pull the build.prop and change it, but I don't know how to put it back onto /system.
Click to expand...
Click to collapse
Do not forget to change file ownership and permission after pushing it back - or else you'll get a bootloop.
Since you do not know how to remount filesystem, I'd second @BlackGunZ and recommend using any root file editor on android to avoid bootloops and reflashing android (as opposed to adb pull/push).
Bor-ka said:
Do not forget to change file ownership and permission after pushing it back - or else you'll get a bootloop.
Since you do not know how to remount filesystem, I'd second @BlackGunZ and recommend using any root file editor on android to avoid bootloops and reflashing android (as opposed to adb pull/push).
Click to expand...
Click to collapse
That's why I suggested him to use CM File Manager, you're right sir.
@Quallenauge
JustArchi updated his ArchiDroid Optimizations for Lollipop (CyanogenMod). Can they be useful ?
I would really like to try this rom, can anyone help me with a step by step guild for installation, kinda new to installing in this fashion.
i ran the wubi installer to dual boot windows/linux
using ubuntu desktop.
need to know what i need to install prior and how to install it.
Pm me please, i don't want to mock-up the development page
thanks in advance
am i using terminal and going to the usb directory then using these commands?
- mount this usb drive
Code:
sudo mkdir <Mount_Path>/local
sudo cp archos.ext4.update <Mount_Path>/local/archos.ext4
sudo sync
sudo umount <Mount_Path>
@toolhas4degrees
For Windows, check the quote below and I can confirm that it works (I always use it), but for Linux I can't provide you a help as I don't have it.
taninos said:
Install this rom or other roms using Windows is pretty easy with Ext2Fsd Open Source Project ( it works over Win2k, Winxp, Vista, Win7, Win8, Server 2003, Server 2008/R2). Install Ext2Fsd on your PC and follow the next steps below to achieve this purpose. Neither this tablet drivers nor ADB nor a linux virtualized on Windows are needed.
Steps:
00 install Ext2Fsd
01 reboot into SDE menu and under "Format System" perform a "Reset Android & Storage" to clear all data of previous installations (this is really important!)
02 reboot into SDE menu and under Developer Edition Mernu -> "Export Data Partition"
03 connect your Tablet with your PC
04 start Ext2Fsd (ext2 volume manager interface). You should see your local drives and a extra one which is the Linux partition
05 mark that partition and press F7
06 start the service and be sure to check the "Enable writing support for ext3 volumes" and uncheck "Mount all volumes in read-only mode. Press apply
07 again mark your linux partition and press F3 and uncheck "Mount volume in read only mode"
08 now you should see the partition under "myComputer". Open it and if you reseted "Reset Android & Storage" you should see 2 Folders ("media" and "lost+found")
09 make a new folder called "local"
10 rename the archos.ext4.update to archos.ext4 and copy it into "local" folder
11 unmount the linux partition as you would do with any usb drive and then press ok on your tablet
12 go to "Developer Edition Menu" and choose "Flash Kernel and Initramfs"
13 a new drive will appear under "my computer". Copy zImage and initramfs.cpio.lzo to it and press ok
14 reboot your tablet and after a couple of seconds you should see the Archos logo and then Cyanogen logo
Click to expand...
Click to collapse
BlackGunZ said:
For Windows, check the quote below and I can confirm that it works...
Click to expand...
Click to collapse
It is a tad incomplete
11a. go to "Developer Edition Menu" and choose "Remove android kernel" (if not present - skip this step)
Last release? How about working USB stick?
BlackGunZ said:
Of course ! The most secure method is to edit the build.prop with CM File Manager.
Before, using ADB put this command after "adb shell" to mount your /system partition RW. After, do the steps I said below :
Code:
mount -o remount,rw /
First, open the file manager. Then, access to the app's options by taping on its icon at the left and choosing after that its settings icon, which is present at the left down side. Go to Advanced section and tap on Access mode next, choose Root access by this way the app will ask root permissions and a pop-up will appear to accept it. You will be redirected to the root (/ directory) of your Archos, scroll down again and go to /system directory. Screenshots :
Secondly, tap on your build.prop file and open it with the file manager's text editor. Choose the line persist.sys.root_access, delete the "3" value and put "1" instead. Screenshots :
Finally, save the file and reboot your phone. Voilà !
Click to expand...
Click to collapse
Hi
I've tried your method but I can't select root access in cm file manager. It does not work. How can I do ? Any idea ?
Thanks in advance
Ladalgigi
Envoyé de mon ARCHOS 101G9 en utilisant Tapatalk
sashokmc said:
Last release? How about working USB stick?
Click to expand...
Click to collapse
The last release is the one which is present in the OP, for an update we have to wait ! I didn't test the USB stick, sorry. ^^'
ladalgigi said:
Hi
I've tried your method but I can't select root access in cm file manager. It does not work. How can I do ? Any idea ?
Thanks in advance
Ladalgigi
Envoyé de mon ARCHOS 101G9 en utilisant Tapatalk
Click to expand...
Click to collapse
Exit CM File Manager, go to Settings, Developer Options and turn off the root permissions. Then, switch on again the root access to "ADB and applications" and try again
BlackGunZ said:
The last release is the one which is present in the OP, for an update we have to wait ! I didn't test the USB stick, sorry. ^^'
Exit CM File Manager, go to Settings, Developer Options and turn off the root permissions. Then, switch on again the root access to "ADB and applications" and try again
Click to expand...
Click to collapse
Thank you very much ! It works !
Very great ROM
Ladalgigi
Envoyé de mon ARCHOS 101G9 en utilisant Tapatalk