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
I don't want to dual-boot, even, just have a nice "normal" Nookie Froyo install on eMMC. I've seen several allude to the fact that it worked for them but no reviews of how they did it. I've backed up my 2.1 install with Clockwork so I'm not really worried about that.
TIA.
It's quite simple actually. All you need is basic knowledge of adb.
All disclaimers apply, I'm not responsible for any damage. Just know that mine is running on internal partitions. And the SD does mount too!
Before doing anything, I would recommend applying a dd from your partitions to your pc.
With, for example on mmcblk0p1 (boot) adb: dd if=/dev/block/mmcblk0p1 of=boot.img
You should do that for each partition to be safe (0p1 to 0p8).
All the following commands can be execute one after one, the separations are only there to makes things a bit more clear.
Then,
Boot to a working Nookie (NF) with your uSD fresh from burning, without any google apps, and without any uSD damaged errors.
Empty your internal system and copy uSD system over, by doing:
- adb shell mount -o remount,rw /dev/block/mmcblk1 / (---there is a space after the 1---)
- adb shell
- mkdir tmpfolder
- mount /dev/block/mmcblk0p5 tmpfolder
- cd tmpfolder
- rm -r * (---note that there is space after the r---)
- cd ..
- cp -r system/* tmpfolder (---this will take a few minutes---)
- umount tmpfolder
Click to expand...
Click to collapse
Then, you need to boot push the attached files (bottom of post) except for the 2 vold files to your boot partition: mmcblk0p1. Unzip, copy content, not zip.
You could very well replace uImage with the new Quickie overclocked uImage for froyo (see dev thread).
To push attached files to boot, do:
- mount /dev/block/mmcblk0p1 tmpfolder
- exit
- adb push [folder-containing-4-attached-files-except-vold.fstab] tmpfolder
- adb shell
- umount tmpfolder
Click to expand...
Click to collapse
I would also recommend erasing all your data. But that's up to you, if you want to keep your data on it. In any case, you can revert back with the data.img you created above . So next part you could skip, haven't tried skipping personally:
Non mandatory, but you could do:
- mount /dev/block/mmcblk0p6 tmpfolder
- cd tmpfolder
- rm -r *
- cd ..
- umount tmpfolder
Click to expand...
Click to collapse
Then you need to push vold.fstab and vold.conf (unzip volds, copy content) to system/etc
Copy vold's to system/etc:
- mount /dev/block/mmcblk0p5 tmpfolder
- exit
- adb push [folder-with-vold's] tmpfolder/etc/
- adb shell
- umount tmpfolder
- rm -r tmpfolder
- exit
Click to expand...
Click to collapse
Then shut down, remove uSD, and boot.
Again, you can choose to push the Quickie uImage, I you prefer, but the accelerometer doesn't work with it at the moment. The 950 kernel does sometimes crash on boot, but once booted is quite stable.
I think that's all folks. I could have been a bit vague at some times, but this should work. And if you made your imgs as recommended, you're bullet proof.
To revert back to initial state with img files, you need to copy files to sdcard and then dd:
- adb shell mount -o remount,rw /dev/block/mmcblk1p1 sdcard
- adb push XXX.img sdcard (--could take a few minutes--)
- dd if=XXXX.img of=/dev/block/mmcblk0pX
Click to expand...
Click to collapse
Do that for each partition.
For those who don't feel up to the task, I could make a CWR flashable zip file of all this. The only thing is, CWR dosen't boot on Nookie just yet. So you couldn't restore with a zip after the change.
[Before doing anything, I would recommend applying a dd from your partitions to your pc.
With, for example on mmcblk0p1 (boot) adb: dd if=/dev/block/mmcblk0p1 of=boot.img
You should do that for each partition to be safe (0p1 to 0p8).
[/QUOTE]
I am a little confused here. What are the names of the 7 other partitions? Thanks, Great guide btw!
See here.
Do you see improved speed and touch response running nookie from emmc?
im getting a "No such file or directory" error after "adb push [folder-with-vold's] tmpfolder/etc"
I created the directory but now it looks like i am stuck at the landscape android splash screen on boot...
any ideas? I am attempting to redo the whole process again just incase i missed something.
Sorry, there's a slash after etc.
Make sure you've copied the systen files, with "ls" inside tmpfolder where you copied system. Should be a etc folder there.
Sam
to the op: I'm not knocking you here, but do you have a basic idea of generic linux file hierarchy or operations in general? Getting a basic grasp on working with files in a linux terminal will make all of these operations make a lot more sense, since most "adb shell" commands are basic linux commands.
FastCR said:
to the op: I'm not knocking you here, but do you have a basic idea of generic linux file hierarchy or operations in general? Getting a basic grasp on working with files in a linux terminal will make all of these operations make a lot more sense, since most "adb shell" commands are basic linux commands.
Click to expand...
Click to collapse
Thanks but I don't see how that comment adds anything here.
Looks like the issue is above commands copy the actual system folder (not the contents of the folder) To the root of the partition. ls shows the folder "system" not the contents including etc. They are inside the folder but if the partition is mounted as system then the folder is redundant. Will check copying the contents and see if that helps.
Once I get it working in will post back to let others know
**** in the first block of code replace
Code:
- cp -r system tmpfolder (---this will take a few minutes---)
with
Code:
- cp -r system[B]/*[/B] tmpfolder (---this will take a few minutes---)
many thanks!
FastCR said:
to the op: I'm not knocking you here, but do you have a basic idea of generic linux file hierarchy or operations in general? Getting a basic grasp on working with files in a linux terminal will make all of these operations make a lot more sense, since most "adb shell" commands are basic linux commands.
Click to expand...
Click to collapse
Why would you go out of your way to say that? It's not constructive. As a junior member with three posts and 0 thanks after a year and a half, sharpen your teeth here at XDA before you act like a big shot.
Right thanks. Changed it.
Has it worked for you?
Sent from my HTC Desire using XDA App
samuelhalff said:
You could very well replace uImage with the new Quickie overclocked uImage for froyo (see dev thread).
Click to expand...
Click to collapse
Are you certain on this part? Last I read in that thread, Froyo needs a different minimum kernel.
UPDATE: Nevermind, I missed this updated effort.
Homer
Well, last time I checked, my NC was running at 950 on froyo with setcpu.
Check the forum. There's a nookie version of quickie. Except accelerometer doesn't work..
First, huge thanks to the second poster - great guide! Can we sticky this?
Second, yes I know what dd does, etc, I've been working with Linux for about ten years . I just don't know the ins and outs of embedded devices yet.
samuelhalff said:
Right thanks. Changed it.
Has it worked for you?
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
yeah i was up till 4am last night but got it working. first i tried to use my existing nf sd card... bad idea. would boot from emmc to the touch android screen to begin, but could not get past. i assume it was the issue on nookdevs because wifi was not enabled. so i removed the setupwizard.apk but somehow bricked and was unable to boot from emmc. so i took the following steps to get things working properly:
1. reimage boot and system from the stock 1.0.1 images and reset the nook to stock, didnt even touch. at the intro screen i just powered it off.
2. next i took a fresh nf sdcard and run steps from your post(with the correction to copy system contents)
3. from there i had a working nf from sdcard! i did my tweaks (google apps, market fix and button remapping from nookdevs froyo tips)
i might to put together a post with a more verbose set of instructions for a one stop froyo shop but if i do i will be sure to give you credit for your contribution.
thanks again!
Hi,
Second, yes I know what dd does, etc, I've been working with Linux for about ten years . I just don't know the ins and outs of embedded devices yet.
Click to expand...
Click to collapse
Well, that's a nice contrast. I've been working on Linux/Android for about 2 months now
I should have mentioned that the NF uSD Card must be a newly burnt image, without all the nookie tips added to it. Of course, your Google framework will crash if you port it without your data.
By the way, there's a nice trick to get past the numb android interface, simply touch every corner of the screen, starting with top left and going clockwise. You'll then be sent the your home screen, and from there you'll log on to google account again.
I think the best way of doing it would to create a flashable .zip, which I'll make tonight if I find the time and if people are really interested. But don't forget CWR dosen't work on nookie for the time being. The only way back would be through adb.
So, does anyone wish to have a flashable zip of this? Or will it be a waist of time?
Sam
samuelhalff said:
Hi,
Well, that's a nice contrast. I've been working on Linux/Android for about 2 months now
I should have mentioned that the NF uSD Card must be a newly burnt image, without all the nookie tips added to it. Of course, your Google framework will crash if you port it without your data.
By the way, there's a nice trick to get past the numb android interface, simply touch every corner of the screen, starting with top left and going clockwise. You'll then be sent the your home screen, and from there you'll log on to google account again.
I think the best way of doing it would to create a flashable .zip, which I'll make tonight if I find the time and if people are really interested. But don't forget CWR dosen't work on nookie for the time being. The only way back would be through adb.
So, does anyone wish to have a flashable zip of this? Or will it be a waist of time?
Sam
Click to expand...
Click to collapse
I would love a flashable .zip. I think many others would as well.
starkruzr said:
I would love a flashable .zip. I think many others would as well.
Click to expand...
Click to collapse
Can't wait for a flashable zip. Maybe even some cm7 release candidates would make me real happy.
Sent from Nooted NookColor using XDA App
Hey guys
So I am currently running 2.3.3 on my N1. I manually flashed the update from Here. I used the "Modified GRI40".
So after update, I noticed that my adfree wasn't working. Running the app, it tells me my host file is up to date. However, no ads are being blocked. Same after uninstalling and re-installing the app. So then I decided to try to copy the host file over manually using adb.
I run adb and get root prompt. Then I mount /system as rw using
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
It appears to work. So then I try copying the host file to /system/etc using
Code:
cp hosts /system/etc
Then I get the following error.
"write error: No space left on device"
But i do, over 30mb of free space.
So I don't know what the issue is. Im thinking that maybe /system isn't being mounted as RW so it is giving the error??
Any help would be much appreciated.
Thanks!
Did you check the /system free space, or /data?
Try doing a df -h from the terminal to verify that you do, indeed, have free space on /system as well as /data, as Jack_R1 mentioned.
codesplice said:
Try doing a df -h from the terminal to verify that you do, indeed, have free space on /system as well as /data, as Jack_R1 mentioned.
Click to expand...
Click to collapse
Well looks like somehow I don't have any space left. I went to go download a terminal application from the market but it errored saying no space left.
So now I can't even install new apps.
However, under settings->storage it says I have 28MB of free space left.
Any ideas?
Sent from my Nexus One using XDA App
Reboot, wipe Dalvik cache.
Go to Manage Applications, clear browser cache.
If it restores you some space - great, proceed with what codesplice suggested above.
If it doesn't - backup, wipe and reflash.
If no backup installed - you're out of luck.
Since you seem to have adb functioning, you can run adb shell df -h to get a readout of your available space on your different file systems. This could help troubleshoot the issue.
Additionally, rather than doing a long manual "mount" command, you could simply do an adb remount to automagically remount all file systems in read/write mode.
The indication under Settings --> Storage indicates free space on /data, I believe, and gives no indication of /system (where you're trying to copy the hosts file).
Another thought (sorry this isn't really coherent at this point...): What if you were to remove your default hosts file and then push the new one?
Code:
> adb remount
Remount succeeded
> adb shell rm /system/etc/hosts
> adb push hosts /system/etc/hosts
> adb shell chmod 644 /system/etc/hosts
codesplice said:
Another thought (sorry this isn't really coherent at this point...): What if you were to remove your default hosts file and then push the new one?
Code:
> adb remount
Remount succeeded
> adb shell rm /system/etc/hosts
> adb push hosts /system/etc/hosts
> adb shell chmod 644 /system/etc/hosts
Click to expand...
Click to collapse
Well that's thing, that is why I started this thread because I was trying to use ADB to push a new hosts file but got the no space error. So I already tried that.
Sent from my Nexus One using XDA App
I was asking if you had specifically tried removing the old one and replacing it rather than just overwriting.
Oh I see what you mean. But no I have not, let me give it a shot.
**Nope didn't work. I still got the same error, no space left on device.
Have you had the opportunity to do adb shell df -h yet?
codesplice said:
Since you seem to have adb functioning, you can run adb shell df -h to get a readout of your available space on your different file systems. This could help troubleshoot the issue.
Additionally, rather than doing a long manual "mount" command, you could simply do an adb remount to automagically remount all file systems in read/write mode.
The indication under Settings --> Storage indicates free space on /data, I believe, and gives no indication of /system (where you're trying to copy the hosts file).
Another thought (sorry this isn't really coherent at this point...): What if you were to remove your default hosts file and then push the new one?
Code:
> adb remount
Remount succeeded
> adb shell rm /system/etc/hosts
> adb push hosts /system/etc/hosts
> adb shell chmod 644 /system/etc/hosts
Click to expand...
Click to collapse
No to hijack this thread, but I just wanted to ask, does "adb remount" require root?
Brownbay said:
No to hijack this thread, but I just wanted to ask, does "adb remount" require root?
Click to expand...
Click to collapse
yes, without root access to the filesystem, adb remount will fail.
So when I try adb shell df -h, I get:
"-h: No such filesystem or directory"
You don't have busybox. Try running "adb shell df", maybe it'll still give some info.
Ok when I ran adb shell df I got a listing of filesystems. /system says size 145M and used 145M. So apparently it is full.
How could that be though?
It could be that you have some bad blocks on your /system partition (you can generally only check by doing a wipe operation in recovery and then viewing the log). These bad blocks could take up space that would otherwise store your system data, and could push you over capacity.
Or you could just have some extra bloat related to that ROM. You could drive to remove some of the applications on /system that you don't have use for (the Amazon MP3 thing, for instance). I'd suggest using Titanium Backup to do this, but you can also do it by manually using the adb shell.
Alternatively, a full wipe and clean reinstall may help make sure you don't have anything left over taking up space.
I'm thinking about just flashing a new ROM altogether as I am also having issues with the battery. Under usage, Android OS now shows somewhere around 35% of the usage. This only started happening after updating to 2.3.3.
I've always ran stock ROMs, so I haven't played with any of the custom ROMs out there. Are there any ROMs you recommend for a first timer?
*Sidenote* So a nandroid backup is a complete backup of the system state correct?
So after flashing a ROM, I can just restore the nandroid backup and my phone will be exactly as it was with the old ROM and user data?
decoyjoe said:
I'm thinking about just flashing a new ROM altogether as I am also having issues with the battery. Under usage, Android OS now shows somewhere around 35% of the usage. This only started happening after updating to 2.3.3.
I've always ran stock ROMs, so I haven't played with any of the custom ROMs out there. Are there any ROMs you recommend for a first timer?
*Sidenote* So a nandroid backup is a complete backup of the system state correct?
So after flashing a ROM, I can just restore the nandroid backup and my phone will be exactly as it was with the old ROM and user data?
Click to expand...
Click to collapse
I've been really impressed with the Kang-o-rama ROMs. Basically prettied-up versions of Cyanogen. The latest release is a beta based on CM7, so still has a few issues. The prior release (KOR 1.1Final) is still quite solid.
And yes, a nandroid backup creates a copy of your current disk image, which can then be restored at any time to revert back to a previously-working configuration (great for when you break stuff!).
decoyjoe said:
I'm thinking about just flashing a new ROM altogether as I am also having issues with the battery. Under usage, Android OS now shows somewhere around 35% of the usage. This only started happening after updating to 2.3.3.
I've always ran stock ROMs, so I haven't played with any of the custom ROMs out there. Are there any ROMs you recommend for a first timer?
*Sidenote* So a nandroid backup is a complete backup of the system state correct?
So after flashing a ROM, I can just restore the nandroid backup and my phone will be exactly as it was with the old ROM and user data?
Click to expand...
Click to collapse
Exactly Remember to wipe before restoring
Oh and that brings up another thought.
So if before I flash a new ROM, I do a Titanium Backup and then flash the ROM...
Would I then be able to restore that Titanium Backup made on the previous stock ROM to restore all my apps and user data?
Anyone know if theres anyone trying to get ubuntu on the galaxy tab. i saw lilsteve was working on it and the last post i saw was that he had one more bug to iron out and he would relase itvsoon. that was monts ago. i also saw that he had moved to another site but he hasnt posted there in quite a while either.
just really wondering if anyone is working on this to make it a daily driver and if we could expect it to have similar functions to the hd2 with phone and txt messaging.
cheers
steven
I've been following the development for about half a year now. There is no phone-capability yet (need to hot-wire the modem to get that working) which means no 3G.
Sound is only working partially. No idea about bluetooth(don't use it so don't care...). Wifi is working. Unaccelerated 2D is working.
I've successfully installed Ubuntu on my tab, but the x-server keeps rebooting when I touch the screen because I don't have the correct drivers and cb22's(guy who hosted the touchscreen-drivers) is currently down.
lilstevie said that he fixed the kernel so we don't need an external driver, but I can't get it to compile correctly because I have no idea how to extract the correct initramfs...
Hope that clears up somethings for you
If you want to see the x-server crash every time you try to click on the screen I could give you a quick dirty tutorial on how too install it... but if you use your tab on a daily basis, don't...
PS. If anyone got a copy of cb22's touchscreen-files please PM me DS.
bkcsoft said:
I've been following the development for about half a year now. There is no phone-capability yet (need to hot-wire the modem to get that working) which means no 3G.
Sound is only working partially. No idea about bluetooth(don't use it so don't care...). Wifi is working. Unaccelerated 2D is working.
I've successfully installed Ubuntu on my tab, but the x-server keeps rebooting when I touch the screen because I don't have the correct drivers and cb22's(guy who hosted the touchscreen-drivers) is currently down.
lilstevie said that he fixed the kernel so we don't need an external driver, but I can't get it to compile correctly because I have no idea how to extract the correct initramfs...
Hope that clears up somethings for you
If you want to see the x-server crash every time you try to click on the screen I could give you a quick dirty tutorial on how too install it... but if you use your tab on a daily basis, don't...
PS. If anyone got a copy of cb22's touchscreen-files please PM me DS.
Click to expand...
Click to collapse
pls post your tutorial mate.
eongab said:
pls post your tutorial mate.
Click to expand...
Click to collapse
Okej. As I said, the xserver is just going to restart everytime you press the screen... aka a booting brick
Warning: THIS IS GOING TO ERASE EVERYTHING ON YOUR TAB! (Backup instructions: wiki.meego.com/ARM/Hummingbird#Backing_up_the_existing_Android_installation_with_dd )
Note: I have the International GSM model (GT-P1000) so these instructions might not work on your tab!
Note2: I have not made these intructions, just reformating them for better flow
C# == Computer Shell
A# == Android Shell (adb shell)
First build a rootstock:
C# sudo rootstock --fqdn GalaxyTab --login ubuntu --password ubuntu --imagesize 5G --seed netbook-launcher-efl,onboard,ubuntu-netbook-efl-default-settings,openssh-server,xorg,gdm,gnome-terminal,gok,network-manager-gnome,gnome-panel --copy-package-cache
Partition your Tab (Will erase everything!)
A# parted /dev/block/mmcblk0 rm 1
A# parted /dev/block/mmcblk0 rm 2
#A parted /dev/block/mmcblk0 rm 3
A# parted /dev/block/mmcblk0 mkpartfs primary fat32 0.0Gb 10.0Gb
A# parted /dev/block/mmcblk0 mkpartfs primary fat32 10.0Gb 12.0Gb
A# parted /dev/block/mmcblk0 mkpartfs primary ext2 12.0Gb 15.9Gb
A# tune2fs –O dir_index,uninit_bg,has_journal /dev/block/mmcblk0p3
A# e2fsck -pf /dev/block/mmcblk0p3 ( if this gives an error remove the p in -pf )
A# mount /dev/block/mmcblk0p3 /sdcard
Push and unpack the rootstock you made earlier (
C# adb push ./rootfs.tgz /sdcard/rootfs.tar.gz
A# cd /sdcard
A# gunzip rootfs.tar.gz && tar xvf rootfs.tar
Editing fstab (add root-partition)
C# adb pull /sdcard/etc/fstab ./fstab
C# nano ./fstab
add line: /dev/block/mmcblk0p3 / ext2 defaults 0 0
C# adb push ./fstab /sdcard/etc/fstab
Flashing Kernel (kernel is here: ubuntab.edzilla.info/zImage-iSD )
C# adb reboot download
Wait for Tab to reboot into download-mode
C# heimdall flash --kernel zImage-iSD
Now it should boot into linux and after the normal text-prompt you should be welcomed by gdm login-screen... but as I said from now on your tab will be a booting brick unless you know your way around linux
---------- Post added at 01:24 AM ---------- Previous post was at 12:58 AM ----------
However if you got a USB-host-cable with a usb-hub, keyboard and mouse you should be able to play around with it
Oooh... and I also forgot about the WiFi-drivers. I havn't fixed auto-connect for wifi and don't have the usb-host-thingy so it escaped my mind
I'm going to fix a USB-host-cable soon thou to see if I can make it auto-login and auto-connect to a bluetooth-keyboard, so I can have my ubuntu-netbook
---------- Post added at 01:43 AM ---------- Previous post was at 01:24 AM ----------
Just as a side note... All my info is taken from here: wiki.meego.com/ARM/Hummingbird (has an incomplete tutorial but to chaotic for most people) and here: forum.xda-developers.com/showthread.php?t=933667
Thanks for the great tutorial!!
Also, lilstevie is no longer working on the native Ubuntu port, since he has moved on to the greener, Honeycomb-laden pastures of the Asus Transformer.
EDIT: Anyone know where I can grab a cheap USB host cable for the Tab?
agc93 said:
Thanks for the great tutorial!!
Also, lilstevie is no longer working on the native Ubuntu port, since he has moved on to the greener, Honeycomb-laden pastures of the Asus Transformer.
Click to expand...
Click to collapse
We should really say Ubuntu-laden pastures as afaiu that's what he's running on it
Nope... He's running Ubuntu on it if I'm not mistaken...
Also... got touchscreen to work today thanks to lardman
Just that I forgot to include the onboard virtual keyboard to my rootstock -.-
Ooh well... new rootstock overnight
Will be back with more info tomorrow
// BKC
Hello All,
Here is a log of what I did to unpack and repack 3.2.78 firmware if any cooker is interested. The interesting part that differs in gen8 and gen9 compared to previous generation is the way you extract kernel and initrd.
For the record, Archos changed again initrd compression in this one, this is now lzo, not lzma anymore. Gen8 extract is the same except that they still use .gz instead of lzma/lzo.
I also attached the tools (linux) I use, aos-unpack has gen8 and gen9 keys, aos-kernel-unpack is a tool I wrote to split zImage and initrd.
Log is a bit rough, but all should be there:
Code:
aos-unpack firmware_archos_it4.aos
cd firmware_archos_it4/raw
dd if=9_MMCF of=init_kernel bs=264 skip=1
aos-kernel-unpack init_kernel
mv unpacked-cpio.gz init-cpio.cpio.lzo
mv unpacked-header init-header
mv unpacked-kernel init-zImage
rm unpack-unknown
dd if=10_MMCF of=recovery_kernel bs=264 skip=1
aos-kernel-unpack recovery_kernel
mv unpacked-cpio.gz recovery-cpio.cpio.lzo
mv unpacked-header recovery-header
mv unpacked-kernel recovery-zImage
rm unpack-unknown
mkdir init_cpio
cd init_cpio
cat ../init-cpio.cpio.lzo | lzop -d | sudo cpio -i --make-directories
cd ..
mkdir recovery_cpio
cd recovery_cpio
cat ../recovery-cpio.cpio.lzo | lzop -d | sudo cpio -i --make-directories
sudo emacs init (comment secure part and change squashfs location:
#if [ $SQUASHFS_CHECK -eq 1 ] ; then
# SQUASHFS_FULL_PATH=`get_mount_info p system`/$SECURE_SQUASHFS_FILENAME
# $CRAMFSCHECKER $SQUASHFS_FULL_PATH
# if [ $? -ne 0 ] ; then
# $FLASH_PARTITION_ERASE init
# log_and_reboot $FS_CHECK_ERROR "Secured fs check failed"
# fi
# $LOSETUP -o 256 `get_mount_info d rootfs` $SQUASHFS_FULL_PATH || log_and_die "Mounting system partition failed"
#else
mount_p data
$LOSETUP `get_mount_info d rootfs` /data/media/android_3.2.78.squashfs || log_and_die "Mounting system partition failed"
#fi
)
sudo su
rm init~
find . | cpio -o -H newc | lzop > ../new_initrd.lzo
cd ../../root/data/
dd if=androidmerged.squashfs.secure of=androidmerged.squashfs bs=256 skip=1
unsquashfs androidmerged.squashfs
cd squashfs-root
cp ../../../../3.2.69/root/data/squashfs-root/system/bin/su system/bin
chmod 6755 system/bin/su
cp ../../../../3.2.69/root/data/squashfs-root/system/app/Superuser.apk system/app
emacs default.prop
-> ro.secure=0
-> persist.service.adb.enable=1
emacs system/build.prop
-> ro.board.has_vibrator=yes
tar -cvzf ../rooted_stock_3.2.78.tgz *
cd ..
mksquashfs squashfs-root android_3.2.78.squashfs
Let me know if you need details or explanations. I didn't release 3.2.78 yet, my g9 battery is dead (or is it the whole tablet ? Crossing finger ) and I can't test right now. Hopefully it will go back to life and I will be able to test soon.
LeTama
i searched for some tool like this
but i cant execute the archos-tools(archos-unpack, archos-kernel-unpack)
im using ubuntu 10.10 and i get "cant execute binary file"
i writed "aos-unpack firmware_archos_it4.aos" in terminal in the directory i have the aos-unpack firmware_archos_it4.aos
any idea what i do wrong,
sorry if i m spaming this thread because i dont understand so much yet (i get my archos g9 on xmas)
Oups, yes, I believe I know... 64 bits Ubuntu here, I bet you are 32 ?
letama said:
Oups, yes, I believe I know... 64 bits Ubuntu here, I bet you are 32 ?
Click to expand...
Click to collapse
i m on virual box and yes i have 32 bit
djnilse said:
i m on virual box and yes i have 32 bit
Click to expand...
Click to collapse
Ok, that explains. I uploaded 32 bits version, can you try them and let me know if they work ?
Thanks!
letama said:
Ok, that explains. I uploaded 32 bits version, can you try them and let me know if they work ?
Click to expand...
Click to collapse
ok i ll try it, i ll report back in a hour or so
HI!
Thanks @letama for your linux tools .
I repacked firmware.squashfs.secure but now I don't know which are the correct zImage and initramfs.cpio.gz ( into .../raw -directory ) for flash into Recovery. ( I used your tools for unpack-repack - 3.2.78 firmware) .
---------- Post added at 08:00 PM ---------- Previous post was at 07:50 PM ----------
Following your tutorial for version 3.2.69 I managed to root my device , but I returned to the official version 3.2.78 without root, because was not stable and had no root privileges for all apk instaled ( root_explorer , setcpu and ather like that without root privileage ) - for this I gave up...
Thanks for your tools !
Now, I can update my rootfs to 3.2.78.
Have a nice day !
Thaolia
Thanks for this, might come in handy, might start cooking.... Never done it before. Does anyone know if anyone has started getting ClockworkMod running on this so we can get some CyanogenMod 9 love on this?
Sent from my Galaxy Nexus using XDA App
surdu_petru said:
Thanks @letama for your linux tools .
I repacked firmware.squashfs.secure but now I don't know which are the correct zImage and initramfs.cpio.gz ( into .../raw -directory ) for flash into Recovery. ( I used your tools for unpack-repack - 3.2.78 firmware) .
Click to expand...
Click to collapse
Kernel unpack is in the list of commands there, and you also have to modify the initrd...
surdu_petru said:
Following your tutorial for version 3.2.69 I managed to root my device , but I returned to the official version 3.2.78 without root, because was not stable and had no root privileges for all apk instaled ( root_explorer , setcpu and ather like that without root privileage ) - for this I gave up...
Click to expand...
Click to collapse
3.2.78 rooted is coming soon, I'm uploading it currently, it should be ready in few minutes.
letama said:
3.2.78 rooted is coming soon, I'm uploading it currently, it should be ready in few minutes.
Click to expand...
Click to collapse
coool, i gonna try it as soon as its up
for the 32-bit thing,
i unpacked the .78 firmware it worked well
Ok now I found the way....it's rooted v3.2.78 working very well but I still not root privilege for all apk ....I have to find a solution, because I do not like root half ...
surdu_petru said:
Ok now I found the way....it's rooted v3.2.78 working very well but I still not root privilege for all apk ....I have to find a solution, because I do not like root half ...
Click to expand...
Click to collapse
do you tried to reinstall the apps or even the whole firmware ?
i was on .69 rooted(squash) and root explorer, setcpu and titanium backup
worked rooted
djnilse said:
do you tried to reinstall the apps or even the whole firmware ?
i was on .69 rooted(squash) and root explorer, setcpu and titanium backup
worked rooted
Click to expand...
Click to collapse
For both rooted versions (3.2.69 and 3.2.78) I receive permission for root ( from su ) but for example in root-explorer I can't mount RW is just RO , than I can't modifie the sytem files .....if you understand what I meant
I think copy su in /system/bin and Superuser.apk in /system/app it's not enough....but I will see ....
surdu_petru said:
For both rooted versions (3.2.69 and 3.2.78) I receive permission for root ( from su ) but for example in root-explorer I can't mount RW is just RO , than I can't modifie the sytem files .....if you understand what I meant
I think copy su in /system/bin and Superuser.apk in /system/app it's not enough....but I will see ....
Click to expand...
Click to collapse
As you saw in the other thread, you want ext4, not squashfs. Squashfs is read-only by nature, it can't be modified.
OneAn9ryN00b said:
Thanks for this, might come in handy, might start cooking.... Never done it before. Does anyone know if anyone has started getting ClockworkMod running on this so we can get some CyanogenMod 9 love on this?
Click to expand...
Click to collapse
Well, ClockworkMod is not needed to run Cyanogen 9, it can be launched without cmw.
I compiled a clockworkmod recovery for gen8 few weeks ago, it was working fine. However, it's not really worth the effort with Archos as we can't use directly partitions the way it's done on phones. We have to resize partition first.
hey op can this tool unpack a plug-in from one device and reconpile it to work on a different device? the reason i ask after my RMA i cant use my plug-in from my original g9
I never purchased plugins, so I don't know, but I believe it contains an activation key that depends on your device ID.
Try it and look at what it produce ?
But I believe it won't do much, you would have to regenerate a proper key for your device.
I would contact Archos about this, no reason that they can't produce one for a rma situation.
letama said:
I never purchased plugins, so I don't know, but I believe it contains an activation key that depends on your device ID.
Try it and look at what it produce ?
But I believe it won't do much, you would have to regenerate a proper key for your device.
I would contact Archos about this, no reason that they can't produce one for a rma situation.
Click to expand...
Click to collapse
i tried talking to archos, the plugin i had was a free pack they offered right when the g9 was released, all i get from archos is a big nothing no reply to my emails and when i call them they play stupid "I'm sorry i don't know what you are talking about"
well anyway I'd love to try just not to computer savvy I'll probably just spring for the full plugin on the archos site but if anyone wants to try the free pak plugin i have is here this plugin seemed to help with netflix and movies over heating the CPU causing a reboot
robertlawson225 said:
i tried talking to archos, the plugin i had was a free pack they offered right when the g9 was released, all i get from archos is a big nothing no reply to my emails and when i call them they play stupid "I'm sorry i don't know what you are talking about"
well anyway I'd love to try just not to computer savvy I'll probably just spring for the full plugin on the archos site but if anyone wants to try the free pak plugin i have is here this plugin seemed to help with netflix and movies over heating the CPU causing a reboot
Click to expand...
Click to collapse
I took a look, aos-unpack is able to unpack it. It produces multiple n_PLUG and there is a digest that mentions your device id. They seem to be flashed to rawfs partition, but I can't tell much more than that.
I'm afraid that without major reverse engineering to interpret these _PLUGIN files, it won't do any good.