How to prepare your i9001 stockROM for modding
First of all I want to say that I know that there already are tutorials about this, but this is just my sites "well explained aio tutorial" that everyone should be able to follow successfully, just as my other tutorials. I added loads of screenshots to make everything a lot easier. So please no complaining about duplicates
Short description:
In this tutorial I will explain you how to prepare a stock rom for modding, the files in this tutorial (cwm and root) are for the Samsung Galaxy S Plus (GT-i9001) only!
The deodex part will work for every device, So if you have an other device then the i9001 you can only follow the deodex part if you would like to.
General notes
- I know I already made a tutorial about how to root the i9001, but this method is faster and easier, so forget the old method and use this one!
- In this tutorial I assume that you have installed your new stock ROM (or still have the original one) and made no modifications to it yet (this excludes apps & settings)
Chapters:
1. ClockWorkMod Recovery (CWM)
2. Getting full access to your system files (Root)
3. How to make system apks available for modding (Deodex)
Chapter 1. ClockWorkMod Recovery
The first step of this guide is to get rid of the stock recovery, the stock recovery is very useless if you compare it to CWM.
CWM is a custom recovery that it known worldwide, it has a great number of options and actually should be installed by default on any smartphone!
The method of flashing the recovery will be Odin (Mutli Downloader 4.43), this method doesn’t require root access and is very trusted.
What you have to do on your pc:
1. Download and unpack Odin and AriesVE.ops
2. Download and unpack CWM v5.5.0.4 (ICS Compatible)
3. Download and install Samsung USB Drivers
4. Now go to the folder where you extracted odin and AriesVE.ops, and open odin (Multi_Downloader_v4.43_with_smd0425.exe)
{
"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"
}
5. Click on the “OPS” button, now choose the AriesVE.ops file you downloaded earlier, after this check the “One package” checkbox
6. Now click the “One Package” button and choose the “recovery-clockwork-5.5.0.4-ariesve.tar.md5″ file you downloaded earlier, now it will perform an md5 check
7. Now turn off your i9001 if it’s on at the moment.
8. Turn it on by holding: Volume Down + Home + Power (hold it for about 6 seconds) until the Download Mode comes
9. Now put the USB cable in your phone and computer, your computer will now install all needed drivers
10. Once the driver installation is complete you will see a yellow block in your upper left odin window
This means it’s detected and ready to flash
11. Now click the “Start” button and the flashing will start
(as you see this process only takes a few seconds)
12. Now your phone will reboot and CWM is installed correctly. (You can also press the “Volume up + Power” buttons when you see the Samsung logo (when odin reboots your phone), It will force your device to go to cwm.
What I strongly advice is to make a backup of your current rom (backup & restore > backup)
Now see the next chapter for quick rooting!
Chapter 2. Getting full access to your system files (Root)
Once CWM is installed it’s very easy to root your phone very fast.
1. Download Root-i9001-Signed.zip or scan this barcode on your phone:
2. Put the zip on your sdcards root, and turn off your phone.
3. Now turn your phone on by holding: Volume Up + Power, when you see the Samsung logo wait another 2/3 sec and then release both buttons.
4. Now CWM Recovery will show, use the volume buttons to scroll up and down, use the home button to choose something
5. Scroll to “install zip from sdcard” and press the home button
(using the volume down button to go down in the menu)
(after pressing home in main menu)
6. Now Press home again to go to “choose zip from sdcard, this will let you browse your internal sdcard, now search for the root-i9001-signed.zip file
(my sdcard is a bit messy ^^)
7. When you found the zip press Home to choose it
8. Now scroll up (it’s faster then down) until you reach Yes, then press the home button again. This will install the root zip on your phone
9. Now press the back button once to return to the main menu, with “reboot system now” selected, press the home button once to reboot your phone
10 . When your phone is rebooted you should look for the SuperUser app and open it, now press the menu button and choose “Preferences”
11. Now scroll all the way down to Superuser information, then press the second button “Su Binary v3.0-beta2″, this will open the updater
(dutch language)
12. As you see it’s outdated and needs to be updated, press the Update button to do this
13. Now the updating will start, and soon SuperUser will ask for SuperUser permissions, click Grant
(dutch language)
14. After clicking grant the update process will continue and will be done in a few seconds
15. Now your Su Binaries are updated you need to update the app itself, just go to the market and search for “Super User”
16. Choose the one contributed by: ChainsDD, now click the “Update” button to update it. You are now done with the rooting.
Chapter 3. How to make system apks available for modding (Deodex)
Requirements for deodexing:
- Android SDK (x86)
- Java Development Kit (x86)
- Busybox Installed on your phone (the download from the market is the installer, so you will need to run the app to install it)
1. Download xUltimate Script v2.3.3, unpack it in some folder and if you have an anti-virus, scan the jar folder and add “auto_app.exe” and “auto_frame.exe” to exclusions/trusted files. (at least my anti-virus thinks it’s dangerous, but it’s not..)
2. Run “Main Skip.bat”, now the main menu of xUltimate will open
3. Now connect your phone in debugging mode to your pc (but not in mass storage mode!), and choose “1″ then press enter, this will pull all system apps from your device
4. When the pulling is complete choose “2″ and press enter, this will pull all system framework files.
5. Now that you’ve collected all apks/odex files, you will probably need to remove these apks from the “origi_app” folder, since they will probably fail to deodex.
- GoogleQuickSearch.apk / GoogleQuickSearch.odex
- Maps.apk / Maps.odex
- Phonesky.apk / Phonesky.odex
- PlusOne.apk / PlusOne.odex
- Voicesearch.apk / Voicesearch.odex
These apps can be redownloaded at the market later! (Phonesky is just the market installer, not the actual market installation)
6. Now choose “3″ and press enter, now the deodexing of the system apps will start.
This may take a while, but at least it will deodex until the end, since the trouble makers are already removed.
7. When the deodexing of the system apps is done you will return to the main menu, now choose “4″ and press enter to deodex the framework files
Luckily deodexing the framework goes a lot faster then the apps. When this process is also done you will have 2 output folders, called “done_app” and “done_frame”
8. What you will need to do is copy both folders to your internal sdcard’s root (since you’re still in debugging mode, drag down the status bar and click on the usb notification, then click on “Mount Storage” to mount your internal sdcard on your computer (Mass Storage Mode)
9. After you copied both folders, you need to press “Unmount Storage” on your phone, now it will be back in normal debugging mode, keep the usb cable in because we are not done yet.
10. Download ADB (Android Debug Bridge) and unpack it in some folder, Now in that folder “Shift+Right Click” at some empty spot > Open command window here (This is only for Windows 7). XP users will have to open cmd manually and “cd” to the adb directory
11. Once your in cmd, enter the following commands to successfully deodex your phone (an explanation of the commands can be found below them, make sure you don’t enter the symbols as well, I added those so you can see if you’re in the right mode)
> adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
$ su
# stop
# mount -o remount rw /system
# rm /system/app/*.odex
# rm /system/framework/*.odex
# busybox cp /sdcard/done_app/* /system/app/
# busybox cp /sdcard/done_frame/* /system/framework/
# busybox chmod 644 -R /system/app/*
# busybox chmod 644 -R /system/framework/*
# reboot
What did those commands actually do?:
“adb shell” – opens a shell interface for your phone, this is the same as a unix shell
“su” – asks for superuser permissions (and gets it right away)
“stop” – this command freezes your phone completely, except the adb traffic, that means you can replace system files without crashing your device
“mount -o remount rw /system” - this remounts the system partition but writable
“rm /system/app/*.odex” / “rm /system/framework/*.odex” – This deletes the old .odex files which are not needed anymore after deodexing
“busybox cp /sdcard/done_app/* /system/app/” / “busybox cp /sdcard/done_frame/* /system/framework/” – This copies the apks from the folders in your sdcard to the right destination.
“busybox chmod 644 -R /system/app/*” / “busybox chmod 644 -R /system/framework/*” – This command sets the permissions to RW-R-R, some users say it’s not needed but just remember to do it always, it’s a good thing! (and bad permissions may even crash your device)
“reboot” – well, I think you know what this does.
Ok so If you entered all commands correctly your phone will now reboot and succeed to boot. be ware that it takes a lot longer then a normal boot since the dalvik-cache has to rebuilt, this takes about 1 minute and 30 seconds at the i9001. (also depending on the amount of apps you have)
12. Now that your phone is successfully deodexed it’s ready to be customized! This means you can install Theme’s and Mod’s, but you can also do all other kinds of customization, since your phone is also rooted, such as installing Thunderbolt. But don’t forget to redownload the apps that you removed before deodexing
I hope you’ve learned something in this tutorial, I’ve already written a tutorial about rooting, but this way of rooting is just way better then the traditional method.
As always, good tutorial :good: I'll probably never need it, but good to know i could if i want.
regards
busprofi said:
As always, good tutorial :good: I'll probably never need it, but good to know i could if i want.
regards
Click to expand...
Click to collapse
Thanks . The tutorial is really focussed on beginners, so they have a well explained tutorial to follow, that they will probably understand the first time they read it. (atleast I hope they do ^^)
broodplank1337 said:
Thanks . The tutorial is really focussed on beginners, so they have a well explained tutorial to follow, that they will probably understand the first time they read it. (atleast I hope they do ^^)
Click to expand...
Click to collapse
:thumbup: Always the Best!!!
Sent from my GT-I9001 using xda app-developers app
raptor92 said:
:thumbup: Always the Best!!!
Sent from my GT-I9001 using xda app-developers app
Click to expand...
Click to collapse
Thanks And the good thing is, I keep getting new idea's for apps and tutorials. my idea source will never go dry! (I guess, since sometimes I suddenly have 3 new apps in my mind, that I can make) In a few years I will have loads of stuff lol (If I keep this tempo of developing/writing tutorials)
Wow another awesome noob-friendly guide. Love your work. Keep it up.
Sent from my GT-I9001 using xda premium
iCloud said:
Wow another awesome noob-friendly guide. Love your work. Keep it up.
Sent from my GT-I9001 using xda premium
Click to expand...
Click to collapse
Thanks will do, btw I just noticed that I forgot to post all links! (I just copied it from my blog without thinking about all links). my mistake
I respect your work.thanks for the tutorial,exactly what I need.
john9 said:
I respect your work.thanks for the tutorial,exactly what I need.
Click to expand...
Click to collapse
Thank you, you're welcome Nice that it's exactly what you need haha
broodplank1337 said:
Thank you, you're welcome Nice that it's exactly what you need haha
Click to expand...
Click to collapse
Brood, i have a question on this. After deodexed the app and jar files can these file considered as zipaligned? Because i found that it take a lot of memory compared to the odexed ROM. However, in the xUltimate there is a optimization command available to optimize all the apk files but it also bring many FC after push all the files to the phone.
DreamerTKM said:
Brood, i have a question on this. After deodexed the app and jar files can these file considered as zipaligned? Because i found that it take a lot of memory compared to the odexed ROM. However, in the xUltimate there is a optimization command available to optimize all the apk files but it also bring many FC after push all the files to the phone.
Click to expand...
Click to collapse
The deodex process calls it aligning, and I'm not sure if that's really a zipalign, but it's very easy to zipalign, just run the attached "03zipalign" in script manager, (with su icon checked), But the fc's are are not normal, you must have made a mistake somewhere, do you still have the odex files inside /system/app and system/framework for example?
broodplank1337 said:
The deodex process calls it aligning, and I'm not sure if that's really a zipalign, but it's very easy to zipalign, just run the attached "03zipalign" in script manager, (with su icon checked), But the fc's are are not normal, you must have made a mistake somewhere, do you still have the odex files inside /system/app and system/framework for example?
Click to expand...
Click to collapse
Nope. During the push process i already write the remove command in adb to delete them all. For the FC case this won't happen if i didn't run the command in xUltimate>Advanced>Optimize all apk>Extreme.
After the optimization i found out that the apk files become smaller in size but sometimes some of the apk will get FC in phone. What i have experienced are camera.apk, AxT9IME.apk, Phone.apk and so on.
DreamerTKM said:
Nope. During the push process i already write the remove command in adb to delete them all. For the FC case this won't happen if i didn't run the command in xUltimate>Advanced>Optimize all apk>Extreme.
After the optimization i found out that the apk files become smaller in size but sometimes some of the apk will get FC in phone. What i have experienced are camera.apk, AxT9IME.apk, Phone.apk and so on.
Click to expand...
Click to collapse
Well, I assume you pushed the files while in mass storage mode?, (or did you use adb push?). When you're in mass storage mode you cannot access your sdcard in adb, so what you actually do when using the remove command: nothing.
Then If you place the done_app and done_frame folder in /system/app & /system/framework you will still have the .odex files , Right?
Please follow all steps correctly, I also screwed up at my first deodexes, but when I red the whole tutorial (I believe that was the i9003 one) again it worked
But you can also use deodex packages (KQE for example) which is posted at the KQE rom topic.
broodplank1337 said:
Well, I assume you pushed the files while in mass storage mode?, (or did you use adb push?). When you're in mass storage mode you cannot access your sdcard in adb, so what you actually do when using the remove command: nothing.
Then If you place the done_app and done_frame folder in /system/app & /system/framework you will still have the .odex files , Right?
Please follow all steps correctly, I also screwed up at my first deodexes, but when I red the whole tutorial (I believe that was the i9003 one) again it worked
But you can also use deodex packages (KQE for example) which is posted at the KQE rom topic.
Click to expand...
Click to collapse
Brood, i redownload the xUltimate using the link that you provided in this forum and now the deodex process run smoothly and successfully. Finally i can manage my phone freely. Thanks again~
DreamerTKM said:
Brood, i redownload the xUltimate using the link that you provided in this forum and now the deodex process run smoothly and successfully. Finally i can manage my phone freely. Thanks again~
Click to expand...
Click to collapse
Good! You know I've only managed to deodex roms successfully using the 2.3.3 version, I just think that 2.3.3 is the magical version . Enjoy the deodex
broodplank1337 said:
Good! You know I've only managed to deodex roms successfully using the 2.3.3 version, I just think that 2.3.3 is the magical version . Enjoy the deodex
Click to expand...
Click to collapse
Really? maybe also caused by last time im using the ver 2.4 so this might be the main cause for such problem
Thanks for this guide, but (there's always a but)....
... my I9001 keeps rebooting into CWM now. Whenever I boot it, or reboot it, it will always go back into CWM. I reflashed CWM using this guide, step by step, 4 times with the same result. It's great to have CWM on the phone, but it would be nice to also use the phone as a,... well "phone".
I tried flashing Broodrom (business) and it flashes alright. No way to test it however since all I see after a reboot is,... CWM. I tried 3 different ROMs, but all I see is CWM.
Do I have a seriously strange i9001, or is there something I am missing in this guide? I've flashed quite a few phones so maybe I can't be considered to be a beginner anymore, and maybe that's why this guide won't work for me
Anyways, back to odin and stock ROM for me.
FrepA said:
Thanks for this guide, but (there's always a but)....
... my I9001 keeps rebooting into CWM now. Whenever I boot it, or reboot it, it will always go back into CWM. I reflashed CWM using this guide, step by step, 4 times with the same result. It's great to have CWM on the phone, but it would be nice to also use the phone as a,... well "phone".
I tried flashing Broodrom (business) and it flashes alright. No way to test it however since all I see after a reboot is,... CWM. I tried 3 different ROMs, but all I see is CWM.
Do I have a seriously strange i9001, or is there something I am missing in this guide? I've flashed quite a few phones so maybe I can't be considered to be a beginner anymore, and maybe that's why this guide won't work for me
Anyways, back to odin and stock ROM for me.
Click to expand...
Click to collapse
The problem you're facing is the bootloop bug in cwm, some people experience this bug, you can find the fix in this post: http://forum.xda-developers.com/showpost.php?p=24831012&postcount=1330
broodplank1337 said:
The problem you're facing is the bootloop bug in cwm, some people experience this bug, you can find the fix in this post: http://forum.xda-developers.com/showpost.php?p=24831012&postcount=1330
Click to expand...
Click to collapse
Thanks for your reply. I did try that solution before I posted (I should have mentioned it, sorry). It didn't solve my problem however. I could boot without going into recovery, but nothing would happen, so the ROM would not be loaded. I should mention however that I had no problems with a different i9001, so I might have a phone with some special issues.
# stop
# mount -o remount rw /system
# rm /system/app/*.odex
# rm /system/framework/*.odex
# busybox cp /sdcard/done_app/* /system/app/
# busybox cp /sdcard/done_frame/* /system/framework/
# busybox chmod 644 -R /system/app/*
# busybox chmod 644 -R /system/framework/*
# reboot
Click to expand...
Click to collapse
I could not do the above. when i type stop, there is no #.
Edited: I have done it. It is deodex now but when I flash the mod such as the extended toggle bar, when the the phone restart the status bar missing. How can I fix it???
Related
The following is a guide for how to obtain root access within an ADB shell, then locally on the device.
UPDATED TO SIMPLE VERSION WITHOUT ADB
--------------------------------------------------------------------------
Credit:
- embeem for bringing the Eclair signature check hole to attention.
- For creating the exploited update package: Zinx Verituse (initially posted here)
- mjxg for writing a complete guide which I have modified and reposted here (original thread here
- Cyanogen for providing Superuser.
--------------------------------------------------------------------------
THIS WILL NOT UPDATE YOU TO 2.0.1. If you would like to end up with a rooted 2.0.1 and haven't been pushed the update OTA yet, then please follow this (http://alldroid.org/viewtopic.php?f=210&t=568) guide THEN follow the directions below.
--------------------------------------------------------------------------
1 - Download the droid-super_user.zip file from: http://alldroid.org/download/file.php?id=659 (md5sum cf653352967253e99d967498ffd9ce69).
Do not extract.
2 - Rename the file to "update.zip".
3 - Plug your Droid into your computer via USB. On the Droid go to the Notifications bar and select "USB Connected" then press "Mount".
4 - Once the device is mounted, the SD card will show as a removable device on your computer
5 - Put the "update.zip" file you just renamed into the Root (top) directory of your SD Card.
6 - Unmount the device from your computer, and turn the Droid off.
7 - Hold down the "X" key on the physical keyboard and while doing so press the power button. Hold both of them down until you see a Triangle with an !.
8 - Press the Vol+ and the Camera button together until you get a menu.
9 - Using the D-pad on the physical keyboard, select the option to update with the update.zip file.
10 - This should take a little bit. Once it's done select the option to reboot the phone.
Now you can download a root application, or terminal emulator and try out your new found root access.
This works with 2.0.1
Please do not start removing any applications just yet. You will run into problems trying to flash anything. Wait until we have a recovery image made.
can some one dump the phone?
Looking at the change in Gerritt:
https://review.source.android.com/#change,12807
It has not been approved yet, although that doesn't prevent Mot from cherry picking it.
I just tried the droid-root.zip update on my Droid, worked great. The only thing I might add is to rename the otakeys.zip from /system/etc/security/otakeys.zip to prevent future OTA updates.
Don't want to lose root now that we have it.
-Howard
http://www.magicandroidapps.com. - Home of Better Terminal Emulator Pro, the best terminal emulator for Droid.
With root, you can dump out the MTD partitions to /data/local, ie:
adb shell
$ su
# cd /data/local
# cat /proc/mtd
Use this output to figure out which partitions are what, and then dump them out, ie:
# cat /dev/block/mtdblock0 > pds.bin
Then 'adb pull' the /data/local/*.bin files to your PC.
-Howard
http://www.magicandroidapps.com - Home of Better Terminal Emulator Pro, the best terminal emulator for Droid.
There is now a more streamlined way of going about this. I need to update the guide.
NEWEST METHOD that DOES NOT require adb
New exploit zip, including Superuser from CyanogenMod
First you have to update your phone to 2.0.1. If you have already done this manually, or if your phone has already received the OTA update, move on to the next section.
First, download this attachment ( http://alldroid.org/download/file.php?id=646 ) and rename it to "update.zip".
Copy update.zip to the SDcard in your phone.
Reboot your phone to recovery mode by holding down x while the phone turns on. once you see the /!\ emblem, press the Volume Up and Camera buttons at the same time.
Select Install update.zip from the menu.
Reboot once it is done.
Now your phone is updated to 2.0.1
Now, to root the phone.
download this attachment ( http://alldroid.org/download/file.php?id=659 ) and rename it "update.zip"
Copy update.zip to the phones sdcard
reboot phone to recovery mode (hold x while turning phone on, press volume up + camera button)
install update.zip
reboot
and you are done.
all credit to Zinx Verituse over on Alldroid.org
su works but apps still say I don't have root?
I'm an IT Professional not a newb, but not super great on Linux either.
I've followed the rooting steps, after updating manually to 2.0.1
The issue is, I can go: su using a term emulator on my phone and it says "access granted courtesy of magicandroidapps" (something like that).
I can do things through the term emulator, but for some reason when I download apps that require root and try to use them it still says I don't have root access? What gives? I couldn't even rename a file in /etc/bluez using ROOT EXPLORER (a file manager).
It's like root works on term emulator but not through GUI apps? Am I missing something?
Disregard, problem solved
Disregard.
Updated to new, simple, one flash instructions.
i cant get this to work for nothing. when i download the files i extract them to the desktop then put them into one folder named update.zip is this wrong?
dabo318 said:
i cant get this to work for nothing. when i download the files i extract them to the desktop then put them into one folder named update.zip is this wrong?
Click to expand...
Click to collapse
It never said to extract. Rename the .zip to update.zip (make sure it's not update.zip.zip) then carry on.
I've got a question. This is a hole found in android, so this should work for any android device, as long as you append the original exploit.zip to that devices update.zip, correct?
ok i finally got the zip on the phone and trying to setup metamorph now. its been setting up file: zip for about five min is this normal?
Here is a link to a tutorial on how to create your own update.zip in order to deliver whatever you may need to (with a size limitation).
http://alldroid.org/viewtopic.php?f=210&t=626
Please note this is exclusive to the current Android 2.0
cellulararrest said:
Here is a link to a tutorial on how to create your own update.zip in order to deliver whatever you may need to (with a size limitation).
http://alldroid.org/viewtopic.php?f=210&t=626
Please note this is exclusive to the current Android 2.0
Click to expand...
Click to collapse
And 2.0.1 ... thanks though, that pretty much answered my question. So any device that gets pushed 2.0/2.0.1 ota update and on before this hole is patched up this should work on. Let's hope they don't patch it before we get a hold of a milestoine update.
Btw- someone should check out the 2.1 sense dump and see if this hole is still present.
Oh and sorry about getting slightly off topic, just seemed the most revelent place to ask.
Yeah that would be good to check 2.1. But I don't think anyone is actually using that recovery image. If it's even available. Everyone has fancy dancy custom recovery images.
COMPREHENSIVE HOWTO "ROOT YOUR DROID" (my best attempt anyhow)
*deleted* per a noobs request (cuz I've heard from others as well that my directions were outdated even though they use super-root from Cyanogen).
Rainabba, Please delete that post. it's out-of-date and incorrect.
i just installed a terminal app from the market, type su and hit enter, it asked to allow or deny, so i believe just a terminal app will give you SU also, correct?
im an idiot when it comes to adb. also just a reminder to the root nobbs, if your using vista, just name the update, update dont add the .zip to it, or it wont work.
Correct. Please don't start removing apps from your system. A few people have been doing that just because they can and are causing themselves real problems. Hold off until someone succeeds in their endeavors for a custom recovery image.
All the info and links needed, none of the fluff. If you have questions, simply ask.
This guide aims to be platform independent. However, some cheats may require user contribution. Thanks in advance!
UPDATED 5-4-2010: New, Faster Factory Reset. Thanks rt1oo and johnsongrantr
Root CDMA Hero, Load Custom Recovery & ROM
Forum Post: Step By Step Way to root Using Flashrec(Updated 4/5)
Thanks goku14238
1) Download: flashrec-1.1.3-20091107.apk
1.1) Download: recovery-RA-heroc-v1.6.2.img
1.2) Download ROM ZIP of Choice: XDA Wiki - ROMs
1.3) Market Download: Any File Manager. RootExplorer, ES File Manager, Astro, etc.
2) Rename "recovery-RA-heroc-v1.6.2.img" to "recovery_backup.img"
3) Copy downloads to SD card root (/sdcard/)
4) Fill in check box for: Settings>Applications>Unknown sources
5) Install "flashrec-1.1.3-20091107.apk" via Any File Manager (RootExplorer, ES File Manager, Astro, etc.) or ADB
*Unmount SD Card if mounted through USB*
6) Open "Recovery Flasher" App and select "Restore Backup Image"
7) Power OFF
8) Power ON to Recovery: Press and hold the "Home" button, Continue holding "Home" while pressing and releasing the "Power" button
9) Flash zip from sdcard>select ROM ZIP
10) Reboot
Reset Phone With Loaded ROM (1.5 "Cupcake" ROMs)
Code:
Menu > Settings > Security > Factory data reset > Reset phone > Erase everything
Reset Phone With Loaded ROM (2.1 ROMs)
Code:
Menu > Settings > Privacy > Factory data reset > Reset phone > Erase everything
Factory Reset
Thanks rt1oo: Forum Post
This will return the phone to its out-of-box, factory condition (including radio!).
Search "RUU" if you want it the official Windows way.
NOTE: If you used the 2.1 RUU, this will not work. HBoot version must be 1.41. Read Forum Post for another method.
1) Download: HERCIMG.ZIP
2) Copy to root of SD card (/sdcard/)
3) Turn phone OFF
3) Hold Volume Down while pressing the power button (turn back on)
4) Press trackball when prompted
5) Reboot
Boot to Recovery from Power OFF
Press and hold the "Home" button, Continue holding "Home" while pressing and releasing the "Power" button
Nandroid Backup
-Reboot into recovery mode>Backup/Restore>Nand backup
TIP: If you choose "Nand backup + ext" it will backup your apps2sd apps along with your imaged system.
*CAUTION: you must restore this kind of backup to an SD Card that is similarly formatted (i.e. SWAP/EXT/FAT backup)
COPY THE CONTENTS OF THE "nandroid" FOLDER TO OTHER MEDIA ON REGULAR BASIS IN CASE OF SD CARD FAILURE!
Nandroid Restore
-Reboot into recovery mode>Backup/Restore>Nand restore>Select desired backup
*TIP* If no backups are found, you need to copy the "nandroid" folder back onto your SD Card from your Computer backup (You did make a copy of nandroid to your Computer didn't you!?)
Partition SDCard for apps2sd (A2SD)
-WARNING: This will erase EVERYTHING from the SDCard. Nandroid does NOT backup SD Card data, except for apps2sd apps, and ONLY if you selected "Nand backup + ext"
1) Reboot into recovery mode>Partition sdcard>Follow on-screen instructions (Default values suggested are OK)
Load Custom ROMs
Download ROM ZIP of Choice: XDA Wiki - ROMs
1) Copy ROM ZIP to SDCard Root (/sdcard/)
2) Reboot into recovery mode>Flash zip from sdcard>select ROM ZIP
Load Android SDK [Mac]
1) Download Latest Android SDK: http://developer.android.com/sdk/index.html
2) Unpack and rename the extracted folder to "AndroidSDK", Move it to "Applications"
3) Copy and Paste into TextEdit:
Code:
export PATH=${PATH}:/Applications/AndroidSDK/tools
4) Save as: "~/.bash_profile"
5) Fill check box on Phone: Settings>Applications>Development>USB debugging
How to modify system files from Recovery
Code:
adb shell
mount <MOUNT_POINT>
Replace <MOUNT_POINT> with area you want to modify (ex: /system /data)
Install Apps through ADB
Code:
adb install <PATH_TO_APK>
Replace <PATH_TO_APK> with the location of your apk (ex: ~/Installers/Android/apk/wireless_tether_1_60_htc.apk)
How to tell if apps2sd (A2SD) is working
1) Connect Phone via USB
Code:
adb remount
adb shell
ls /system/sd/app/
If you get a list of applications, or no errors, then apps2sd is *should be* working properly.
Remove Extra Useless Preloaded Apps
Link: Root Explorer
Yes, you CAN do this through adb, but this is MUCH easier. Simply open, hit "mount r/w" button, delete anything in /system/app and /data/app you don't want! I'm well aware of the cost of the app. If you don't want to pay and help the developer, then search the forums and figure it out yourself !
Good stuff. Thanks for the contribution. Would you mind if I put it on GeekFor.Me / would you like to put it on there?
http://geekfor.me/news/wanted-writers-for-faq-tutorial-help/
Let me know.
Please do! Thanks for the read! Also, thank you very much for all of your hard work, the ROMs you make are crucial to all of this stuff advancing forward!
Thanks for putting this together - great post!
Thanks a lot for this Gallias. Definitely helped me out. I wish I had found this a couple weeks ago heh.
When I tried to enable compcache with your instructions I was getting a read-only error. Doing 'adb remount' first seems to have solved it.
AH yes thank you my apologies. Updated.
Hey, I swear i've tried for two hours to get Modacos custom ROM installed. I successfully installed the recovery-RA-heroc-v1.5.2.img and when I power off and reboot into recovery mode, I only get one option -- to CLEARSTORAGE "Delete all user data? <action>yes <send> no, I select YES and it reboots the phone and it looks like the same interface. I've tried flash_image recovery /sdcard/update.zip by renaming the ZIP file modaco 2.2 to (update) and moving it to the SDCARD home directory. I then use Lindas file manager to load the custom recovery image and select SDCARD/update.zip This doesn't work (I'm probably doing something wrong) But I don't understand why I can't boot into recovery mode. I am using the CDMA (sprint) version.
Any tips? I need a bit of some help here.
When you reboot into recovery mode you should see this:
{
"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"
}
If you don't see that, then you haven't actually pushed the new recovery image into the phone. The screen you describe is the default recovery loader that comes with the phone.
Try my "Load Custom Recovery" step over again, or if on a different platform, follow the root guide for your specific platform:
CDMA Hero Guides
I got up to the point of
adb push asroot2 /data/local
it says 836 KB/s <74512 bytes in 0.087s>
C:\hero\tools> aadb shell
$chmod 0755 /data/local/asroot2
chmod 0755 /data/local/asroot2
$ /data/ocal/asroot2 /system/bin/sh
/data/local/asroot2 /system/bin/sh
now get this.... this is what it gives back to me
[+] Using newer pipe_inode_info layout
Opening: /proc/758/fd/3
YES it says 758 NOT 857.
It then says
SUCCESS: Enjoy the shell
Is that right or is it supposed to be 857? I saw the guide and it told me that it should say 857 so it's not giving me the right message I assume.
I'll try again and see if this is right, i'll post an edit later to let you know if I get it workin, if not I guess 758 is incorect
Well, based on the C:\ I'm going to say your using Windows. I don't think that number will be critical, but you do need to perform this after you get the "SUCCESS: Enjoy the shell"
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/bin
cat sh > su
chmod 4775 su
exit
exit
THEN, you also need to push the recovery image. If you are following the link I placed at the top of this guide on how to root with Windows, it should have you go through everything I'm explaining. Don't get worried or hung up on steps that don't exactly match up with what other people are seeing; at the end of the day you may see some differences, but if you are getting "SUCCESS" from asroot2 it means that the technical "rooting" part is working, you just need to finish up and follow through on the rest of the steps. Keep working at it you are really close, don't let inconsistent numbers discourage you!
Just letting you know, you've got a typo in the rooting area. It should be asroot2 not asroot 2
ffolkes said:
Just letting you know, you've got a typo in the rooting area. It should be asroot2 not asroot 2
Click to expand...
Click to collapse
Ah yes very true thanks! Fixed.
I followed the instructions for rooting with a MAC, I did the boot into recovery mode, there is no option for "NANDROID" backup. It just says "Clear User Data" <ACTION> Yes <SEND> No. Wound up clearing everything off my phone.
rlundeen said:
I followed the instructions for rooting with a MAC, I did the boot into recovery mode, there is no option for "NANDROID" backup. It just says "Clear User Data" <ACTION> Yes <SEND> No. Wound up clearing everything off my phone.
Click to expand...
Click to collapse
Ouch! Sorry man, it means something went wrong during "Load Custom Recovery [MAC]". Try that step over again.
theraginasian said:
Ouch! Sorry man, it means something went wrong during "Load Custom Recovery [MAC]". Try that step over again.
Click to expand...
Click to collapse
Did it 3 times, get the same thing over and over. Actually, if you hold the Volume Down key and then power the phone on, I can do the nandroid backup, flash rom, etc.
theraginasian said:
Remove Extra Useless Preloaded Apps
Forum Post 1: How to remove Stocks, Nascar, and other useless apps...
Forum Post 2: APPS that are SAFE to remove
Thanks chuckhriczko and VoXHTC!
Beyond what most custom ROMs remove, I remove:
-Sprint Navigation (Sprint_Navigator.apk/odex)
-Sprint Visual Voicemail (Sprint_Core.apk/odex)
-Device Self-Service (SDSA.apk/odex)
Code:
adb remount
adb shell
cd /system/app
rm <NAME_OF_APP>.apk
rm <NAME_OF_APP>.odex
Replace <NAME_OF_APP> with the name of the app you want removed.
Make sure to check /system/sd/app for duplicate/other unwanted applications if you have apps2sd running.
Click to expand...
Click to collapse
Thanks the cheat sheet. Is this list of apps that can be safely removed still valid for 2.1 ROMs? I am running DC v2.07.2 ROM.
prateekandroid said:
Thanks the cheat sheet. Is this list of apps that can be safely removed still valid for 2.1 ROMs? I am running DC v2.07.2 ROM.
Click to expand...
Click to collapse
Make a NANDROID before removing any of them, so if you remove something you want back or that messes your phone up. You can go back to original.
They arent usually the main choices. But you can if you want to.
Heres some you can remove.
Type this
adb remount
adb shell
cd /system/app
ls
* "ls" this will show you all the apps on your phone.*
These are commonly removed-
Sprint_Navigation.apk
Sprint_TV.apk
Sprint_TVWidget.apk
Sprint_Nscar.apk
Sprint_NFL.apk
Stock.apk
com.htc.StockWidget.apk
HtcRingtoneTrimmer.apk
Youtube.apk
Facebook.apk
There are more, but these are usually the common ones. Pick and choose what you want and what you dont want.
Jus10o said:
Make a NANDROID before removing any of them, so if you remove something you want back or that messes your phone up. You can go back to original.
They arent usually the main choices. But you can if you want to.
Heres some you can remove.
Type this
adb remount
adb shell
cd /system/app
ls
* "ls" this will show you all the apps on your phone.*
These are commonly removed-
Sprint_Navigation.apk
Sprint_TV.apk
Sprint_TVWidget.apk
Sprint_Nscar.apk
Sprint_NFL.apk
Stock.apk
com.htc.StockWidget.apk
HtcRingtoneTrimmer.apk
Youtube.apk
Facebook.apk
There are more, but these are usually the common ones. Pick and choose what you want and what you dont want.
Click to expand...
Click to collapse
Thanks for a prompt response.
Just curious, wat do people prefer instead of Youtube.apk to watch Youtube? Because as far as I know there is no Adobe Flash support yet. So Youtube videos will not work on its website. I use Dolphin browser.
i personally believe the flashrec method is much more practical. i was able to root and flash a custom rom without ever plugging my phone into my computer, i did it all from my phone.
is there a downside to flashrec im not aware of?
1: ok step one download universal and root to sd card.
2: then download a file manager such as linda file manager.
3: download chainsdd SuperUser
4: go to settings then applications put a check next to unknown sources.Then go to Development and check usb debugging and stay awake.
5: use linda file manager and browse to sd card and install universal root "DO NOT INSTALL SUPERUSERBUILT INTO IT"
6: Install chainsdd Superuser, After install open it goto settings then scroll too bottom and click su binary it may fail the first time but click it again it will say Su binaries updated.
7: I am using root explorer i bought it from market.
8: after this is installed open it and be sure to click the rw option when you open it at top of directory. Now copy /system/xbin/su to your sd card for safe keeping along with rootshell file from sqlite_stmt_journals folder.
after you back them up too sd then copy Su file too /bin let it over write theres.
Now fire off adb and type adb shell then at the $ type su and walla full root.
Anyone have ideas on how to make it read only so system cant delete those files on reboot or automated way of putting the files in right place at reboot let me know.
Good work on the first steps, next we need to flash a new recovery.img, I've been hearing that there is no easy way into the recovery at startup, what does "adb reboot recovery" result in, long story short if we can get a new recovery then we can flash unsigned roms including your su/root pre installed. Sorry I'm not more help on the legwork portion of this, I really need to get a garmin to work more on this, but p.m. me if I can help more as I don't pay enough attention to these forms
tsukisan said:
Good work on the first steps, next we need to flash a new recovery.img, I've been hearing that there is no easy way into the recovery at startup, what does "adb reboot recovery" result in, long story short if we can get a new recovery then we can flash unsigned roms including your su/root pre installed. Sorry I'm not more help on the legwork portion of this, I really need to get a garmin to work more on this, but p.m. me if I can help more as I don't pay enough attention to these forms
Click to expand...
Click to collapse
Have you tried grabbing ROM Manager from the market? It allows you to install Clockwork recovery.
LiquidSolstice said:
Have you tried grabbing ROM Manager from the market? It allows you to install Clockwork recovery.
Click to expand...
Click to collapse
Do you know if there is a compatible recovery for the garminfone? You can't flash a sholes recovery on a garminfone.
ROM Manager is useless for the Garminfone. There are no backups for it and its not a supported phone.
"adb reboot recovery" I'll have to give it a try as well, now that I am also rooted.
I did a similar process... used androot (temporary root) to get rootshell with superuser app from the market.
I downloaded su binaries separately, fired up adb shell,ran rootshell.
I manually copied su to /system/xbin then used gscript lite to script the following:
/system/xbin/su -c 'mount -o remount,rw /'
/system/xbin/su -c 'mount -o remount,rw /system'
/system/xbin/su -c 'cp /system/xbin/su /bin'
After that I added the script to my home screen and I have one click root.
The changes won't persist until the boot image is changed to and repacked.
Note that the rootshell app is useless after a cold boot or if moved. It just crashes.
The most interesting thing is looking through the startup scripts that run.
There are parts from 3 or 4 developers commented out that,!among other things, show what to set to root it permanently,and what looks like loading parts of. the os from the emmc or sdcard.
And the automated test scripts built in come complete with a Garmin test phone number that can be called as well as a full suite of functional and regression test scripts that can be used to validate all functions including the Garmin apps automatically. The daemon even loads itself on boot by default.
It looks like the build they used was a virtually unmodified developer build. Hell,the boot scripts even show what to change to make it run in the emulator. That is my next project (getting it up in emulation so I can test different modifications)... well,that and see what it will take to get the Garmin app running in the latest android. I see no point in upgrading to the latest os if I lose Garmin functionality.
Being that the devs left nice comments for damn near every line and wrote very clean and elegant scripts, i would be shocked if it took very long to get Garmin up, at least in emulation.
Fyi, since piracy is illegal, I want to make it clear that the Garmin portions of my rant refer only to regaining functionality in the latest os.
Ok... to permanently root your phone...
Use the method in the first post. Then, in Root Explorer go to /system/bin and click r/w (if it isn't already). Scroll down to governor.sh, long press and choose open in text editor. Add the following to the end:
mount -o remount,rw /
mount -o remount,rw /system
cp /system/xbin/su /bin
Save it. Now at every boot you will have rw filesystems and the su file will copy over. I am working on making a modified recovery.img to flash.
I don't know why people say the Garminfone is more locked down or unflashable than any other phone. It comes with a flash_image program on the phone that lets you specify a destination partition and an image file, it will flash /system/recovery.img on boot and all the boot scripts are commented for how to do things like boot off the emmc. The developers left a bunch of services in the boot scripts but disabled to do various functions.
Tim2246 said:
1: ok step one download universal and root to sd card.
2: then download a file manager such as linda file manager.
3: download chainsdd SuperUser
4: go to settings then applications put a check next to unknown sources.Then go to Development and check usb debugging and stay awake.
5: use linda file manager and browse to sd card and install universal root "DO NOT INSTALL SUPERUSERBUILT INTO IT"
6: Install chainsdd Superuser, After install open it goto settings then scroll too bottom and click su binary it may fail the first time but click it again it will say Su binaries updated.
7: I am using root explorer i bought it from market.
8: after this is installed open it and be sure to click the rw option when you open it at top of directory. Now copy /system/xbin/su to your sd card for safe keeping along with rootshell file from sqlite_stmt_journals folder.
after you back them up too sd then copy Su file too /bin let it over write theres.
Now fire off adb and type adb shell then at the $ type su and walla full root.
Anyone have ideas on how to make it read only so system cant delete those files on reboot or automated way of putting the files in right place at reboot let me know.
Click to expand...
Click to collapse
So I ran into a little speed bump here, I'll post what I've done thus far and maybe someone has some feedback...
1) Open the applications settings menu for Android OS and Check off the option "Uknown Sources" and then click on "Development" and make sure options "USB debugging" and "Stay Awake" are checked.
2) Download and install the "Universal Androot" apk. application installer using the web browser on your android phone.
3) Launch "Universal Androot" and use the drop down menu on the main screen and select the option that states, "Do not install Superuser" and then click the "Root " button, the application will run a few scripts and then confirm success.
4) Go the Android Market, and download and install the following application, "SuperUser" written by android software developer, chainsdd.
5) Once "SuperUser" is installed on your phone, launch the application and click, "Settings" on the top right hand corner of the application, it will bring you to a list of options, scroll to the bottom, and click on, "Su binary v original", this will download a zip file containing any updates. (You may have to click this several times if it fails, it will eventually download)
6) Go to the Android Market, and download, "Root Explorer (File Manager)" and install it, you may also download this package elsewhere...
7) Open "Root Explorer" and make sure you are in the / "root directory" of the unit and then click the "Mount R/W" button at the top.
8) Browse to /system/xbin/ and copy file "su" to /sdcard
This is where I have a problem, I can not locate /system/xbin/su
Here is some additional information that may be relevant
Garmin
Hardware R1.7
Software 4.0.12
Android
Firmware 1.6
Kernel version 2.6.29
hey all!
I've tried following the directions like 10 times and i keep coming up short..i can't seem to get root.. It's odd. Would anyone be kind enough to post a video, or clarify the directions needed in a step-by-step fashion?
Thanks in advance!
Does anyone in the know have a timeframe for when we might know how to get rid of the t-mobile animation that plays when the phone boots up? I'd like to replace all the bootscreens with some wicked cool custom stuff, but gotta knock that pink crap outta the way first.
merwin said:
Ok... to permanently root your phone...
Use the method in the first post. Then, in Root Explorer go to /system/bin and click r/w (if it isn't already). Scroll down to governor.sh, long press and choose open in text editor. Add the following to the end:
mount -o remount,rw /
mount -o remount,rw /system
cp /system/xbin/su /bin
Save it. Now at every boot you will have rw filesystems and the su file will copy over. I am working on making a modified recovery.img to flash.
Click to expand...
Click to collapse
Sorry, but it didn't work for me. Rooting mine by manually pasting SU into the /bin folder works fine.
I copied/pasted your code over to the end of the file as described above.
Spazmogen said:
Sorry, but it didn't work for me. Rooting mine by manually pasting SU into the /bin folder works fine.
I copied/pasted your code over to the end of the file as described above.
Click to expand...
Click to collapse
Are you sure the version of su in /system/xbin is the one that comes with superuser? You can check by using either a terminal app or adb,going into the xbin folder, and type ./su
You should get a superuser request. If not, then something was not done correctly.
Thanks for the reply.
but since 2.1 Eclair was installed today, it's a moot 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"
}
There is no SU in either /bin or in /system/xbin.
SuperUser by ChainsDD won't install the SU file, it keeps failing. Tried it 30x today.
Root Explorer only allows folders to be r/o now. So I am waiting on an update for that one.
How exactly did you get 2.1 on a Garminfone?
I have a Garminfone with 2.1 and all i did was download z4root from the market place and ran it and it seems to have given me a perminant root and i have no problems hopefully this helps you guys out it is a simple one click root unroot app.
Root is persistant. It survived a few battery pulls.
I have been able to get it into ADB REBOOT RECOVERY. A green droid guy with a yellow warning triangle appears.
One of the fellows in the Tmo forums claims to have gotten it into FASTBOOT menu options. If that is true, it would appear the boot loader is unlocked...
Garminfone 2.1 easily rooted...
I easily rooted my Garminfone 2.1 Eclair with z4root. It was one click and done with the options to temp or permanently root the phone it is also reversible.
Problem I am having is that I created an ext2 partition on my sd card but the phone doesn't recognize it. It was partitioned with "ubuntu livecd" with "gparted" partition manager. It also shows up in windows with "Mini Tool Partition Wizard 5" when the sd card is in a card reader attached to the pc.
Whats the next step? I want to move apps to the sd card. I have link2sd installed for this but can't figure out how to enable ext2 mount.
Also another good pc app to have if you trashed your sd card partitions is "Active Partition Recovery for Windows" works for all drives.
Issues - Rooting with Z4Root
Hello,
I have a Garminfone that came with 2.1 version. I have downloaded Z4Root and tried both options Temp and permanent. But no Joy.
I made sure, USB Debugging is off. Can someone let me know what step am I missing ??
Much appreciate your time.
z4root
Perseus71 said:
Hello,
I have a Garminfone that came with 2.1 version. I have downloaded Z4Root and tried both options Temp and permanent. But no Joy.
I made sure, USB Debugging is off. Can someone let me know what step am I missing ??
Much appreciate your time.
Click to expand...
Click to collapse
What exactly are you trying to do by rooting? Did you install SuperUser by ChainsDD? What app/file manager are you using? If you dont have this you won't be able to do anything. The apps you use for app/file management need to have root permissions or they will do nothing.
Mine rooted with z4root no problem and was able to remove all the fluff apps it shipped with that I didn't want. But this was only half of what I wanted to achieve. I haven't been able to move apps to sd, but I can't get ext2 to mount, not a problem because of the root I don't think.
What I have on my Garminfone 2.1
z4root
busybox (installed with z4root)
superuser
my backup root
uninstaller for root
super manager
Hope this helps.
Ok First off. Thank you very much for your time. It is greatly appreciated.
Well, Here's what I have done so far.
1. Downloaded and installed Z4Root from the Market.
2. Download and Install SuperUser by ChainsDD from the Market.
3. Ran Z4Root and first tried Temporary Root. That seemed to go fine until it was stuck after displaying the message ReBooting.
4. Next Tried Permanent Root Option after a Battery Pull. That asked me to turn on USB Debug. Did so and it seemed to go smoothly until that too was stuck with Rebooting message.
5. I tried the same Permanent Option after another Battery Pull. This time, it worked and the phone rebooted & came back. So I installed BusyBox from Market.
6. At this time I downloaded Titanium Backup. It complained not having root access. 7. So I started SuperUser and that showed an empty list under application tab. Went under Settings and hit the update. It failed but saved the Zip on my SD card.
8. I installed the Binary from Step 7 using Apps Manager. Tried SuperUser again. Still empty list for applications.
So there I am. I suspect I probably missed something somewhere. Possibly before doing Step 6 I should have done something. Can't seem to figure out.
Also earlier in this thread there was a mention that you will need to manually copy the binaris for SuperUser to certain specfic directory. Since it got installed successfully, do I still need to do it ?
Update on 9/11/11: Thanks to phburks there is now a flashable zip to root the G2X stock rom. He figured out that the update-binary we were using was not compatible with the G2X. He found the compatible binary that allows us to create flashable zip files. Hats off to phburks. This is an unsigned zip and you should not be required to toggle signature verification. Of course the files required to root the phone (su and Superuser.apk) were created by Chainsdd.
There are two flashable zip packages. The first one roots the G2X. You simply flash it with Clockworkmod Recovery. The second zip unroots the phone for those who wish to unroot their device for whatever reason.
After rooting go to the Android Market and get the Busybox installer referenced below. Use that to install and keep Busybox updated.
Root Zip for G2X: http://www.mediafire.com/?92qpr525ztblh8w
Unroot Zip: http://www.mediafire.com/?2vr7cmgg7qcdn14
HOW TO ROOT
1. Install latest Clockworkmod Recovery using NVFlash, if you haven’t already done so.
http://forum.xda-developers.com/showthread.php?t=1056847
2. Download the root zip package referenced above.
3. Put the zip package on your internal or external sd card on your G2X. Do not unzip the package.
4. Turn off phone and boot into Clockworkmod Recovery by pressing volume down and power and hold until the fancy LG (second one) appears.
5. Select install zip from sd card. Select and flash the root zip package. Note: You navigate in Clockwordmod Recovery by using the volume keys up and down and commit the action by pressing the power button.
6. Reboot your phone. You are now rooted.
NOTE: THE FOLLOWING BELOW IS OBSOLETE. IT IS LEFT FOR HISTORICAL PURPOSES ONLY.
Original post made on 9/9/11:
I wanted to run the stock Gingerbread ROM and wanted to root it without flashing a new ROM. I was able to succesfully do it and the instructions are below. I was attempting to make an update.zip to do this but it kept getting a "status 0" error. The original superuser zip by ChainDD also gets this error. So I decided to try and root it using ADB commands while running Clockworkmod Recovery. Here is how I did it. If someone can help me get an update.zip that will install without error in Clockworkmod Recovery to make this easier for people to install it would be much appreciated.
1. Download my G2X root package that includes necessary ADB files (Android SDK install not required) and unzip the contents. The package contains the latest versions of “su” and “Superuser.apk”.
http://www.mediafire.com/?6rdrdfxvdoq9nkv <download link for my root G2X package>
2. Install latest Clockworkmod Recovery using NVFlash, if you haven’t already done so.
http://forum.xda-developers.com/showthread.php?t=1056847
3. Boot into Clockworkmod Recovery by holding down volume down and power until fancy LG logo shows (about ten to fifteen seconds). This is not the first one displayed when the phone powers up. Wait for recovery to start. Just to be safe perform a backup of your device’s current state.
4. Using the recovery menu scroll down to “mounts and storage,” press the power button, scroll down to “mount system” and press the power button.
5. Now that your system is mounted plug your phone into your computer (let drivers install if you have not done before – requires LG USB driver package).
http://bit.ly/qyoAxY <shortened link for direct download from LG server>
6. Open a command prompt windows on your computer. In the command prompt window change to the directory to where you unzipped the G2X root package.
7. Issue the following ADB commands. Do not type the the text in the brackets <>. That is just information on what the command is doing.
adb kill-server
<make sure no conflict with another version of adb server running>
adb devices
<checks to see if phone is connected to adb>
adb push system /system
<make sure you type a space before “/system”>
adb shell chmod 6755 /system/bin/su
adb shell ln -s /system/bin/su /system/xbin/su
<make sure you type a space before “/system/xbin/su ”>
8. System is now rooted. You can unplug the USB cable now.
9. Now in Clockworkmod Recovery choose “unmount system.”
10. Go back to the main menu and choose “reboot system now.”
11. If you want busybox (some root programs such as Titanium Backup require it) on your system go to the Android Market after rebooting your phone and search on “Busybox.” Download and run the Busybox installer by Stephen (Stericson). When you are prompted allow it to have superuser permissions.
http://bit.ly/qIAoXZ <link to Android Market page for Busybox>
12. You are now rooted with a working busybox installation.
13. It is a good idea to go back into recovery and make a backup of your newly rooted system before you start installing and running programs that obtain superuser permissions.
14. Enjoy the power!
Please click the Thanks button if this helped you out.
Reserved for future use.
Much appreciated for the help, but I don't think I will be using it.
Why not just load a rooted GB or xboards GB, same thing isn't it? lol.
Paul Nur said:
Much appreciated for the help, but I don't think I will be using it.
Why not just load a rooted GB or xboards GB, same thing isn't it? lol.
Click to expand...
Click to collapse
This is for people who have been using the phone after applying the update and don't want to start from scratch again. This lets you just root the phone without needing to flash a rom and format the system.
Wow, I've been waiting fire this thanks jboxer.
Sent from my LG-P999 using XDA App
jboxer said:
This is for people who have been using the phone after applying the update and don't want to start from scratch again. This lets you just root the phone without needing to flash a rom and format the system.
Click to expand...
Click to collapse
Ohhhhhhhhhhhhhhh, I got it lol thanks for showing me it from a different angle
still realy no point xboarders is more stable and much faster then stock and all u need to do is flash his rom then go to advanced restore and only restore data ive gotten away with that doesnt always work though
Always good to have more options.
phburks said:
Always good to have more options.
Click to expand...
Click to collapse
Damn straight. Keep it up, jboxer.
Sent from my LG-P999 using xda premium
Very nice! Thanks man, much appreciated.
Sent from my LG-P999 using XDA App
awesome i tried it on another g2x phone running 2.3.3 root the phone so fast plus with no lost data
thread rated 5 stars ^-^
Change Directory
jboxer said:
I wanted to run the stock Gingerbread ROM and wanted to root it without flashing a new ROM. I was able to succesfully do it and the instructions are below. I was attempting to make an update.zip to do this but it kept getting a "status 0" error. The original superuser zip by ChainDD also gets this error. So I decided to try and root it using ADB commands while running Clockworkmod Recovery. Here is how I did it. If someone can help me get an update.zip that will install without error in Clockworkmod Recovery to make this easier for people to install it would be much appreciated.
1. Download my G2X root package that includes necessary ADB files (Android SDK install not required) and unzip the contents. The package contains the latest versions of “su” and “Superuser.apk”.
http://www.mediafire.com/?6rdrdfxvdoq9nkv <download link for my root G2X package>
2. Install latest Clockworkmod Recovery using NVFlash, if you haven’t already done so.
http://forum.xda-developers.com/showthread.php?t=1056847
3. Boot into Clockworkmod Recovery by holding down volume down and power until fancy LG logo shows (about ten to fifteen seconds). This is not the first one displayed when the phone powers up. Wait for recovery to start. Just to be safe perform a backup of your device’s current state.
4. Using the recovery menu scroll down to “mounts and storage,” press the power button, scroll down to “mount system” and press the power button.
5. Now that your system is mounted plug your phone into your computer (let drivers install if you have not done before – requires LG USB driver package).
http://bit.ly/qyoAxY <shortened link for direct download from LG server>
6. Open a command prompt windows on your computer. In the command prompt window change to the directory to where you unzipped the G2X root package.
7. Issue the following ADB commands. Do not type the the text in the brackets <>. That is just information on what the command is doing.
adb kill-server
<make sure no conflict with another version of adb server running>
adb devices
<checks to see if phone is connected to adb>
adb push system /system
<make sure you type a space before “/system”>
adb shell chmod 6755 /system/bin/su
adb shell ln -s /system/bin/su /system/xbin/su
<make sure you type a space before “/system/xbin/su ”>
8. System is now rooted. You can unplug the USB cable now.
9. Now in Clockworkmod Recovery choose “unmount system.”
10. Go back to the main menu and choose “reboot system now.”
11. If you want busybox (some root programs such as Titanium Backup require it) on your system go to the Android Market after rebooting your phone and search on “Busybox.” Download and run the Busybox installer by Stephen (Stericson). When you are prompted allow it to have superuser permissions.
http://bit.ly/qIAoXZ <link to Android Market page for Busybox>
12. You are now rooted with a working busybox installation.
13. It is a good idea to go back into recovery and make a backup of your newly rooted system before you start installing and running programs that obtain superuser permissions.
14. Enjoy the power!
Please click the Thanks button if this helped you out.
Click to expand...
Click to collapse
Hi,
Sorry i'm new on rooting android phone.
on step 6. how i change the directory in the command prompt to go to the g2x root file i saved?
thanks
yogieajuz said:
Hi,
Sorry i'm new on rooting android phone.
on step 6. how i change the directory in the command prompt to go to the g2x root file i saved?
thanks
Click to expand...
Click to collapse
That's a Command Prompt windows on your computer. The easiest way is to open the desired folder in Windows Explorer and then click on the address bar. Highlight the entire location and copy it. Then in your command prompt windows type "cd" a space, right click and paste the copied location and hit return. You will now be in the correct folder in your command prompt windows.
Thank you for quick reply
jboxer said:
That's a Command Prompt windows on your computer. The easiest way is to open the desired folder in Windows Explorer and then click on the address bar. Highlight the entire location and copy it. Then in your command prompt windows type "cd" a space, right click and paste the copied location and hit return. You will now be in the correct folder in your command prompt windows.
Click to expand...
Click to collapse
Thanks jboxer, work like charm....
but when i did back up they said error can not back up image data ???
whats wrong???
never mind, i found out i run out of space on my sd card
@jboxer, I figured out the flashable zip. Just tested it on an unrooted 2.3.3 installation and it worked perfectly. I PM'd you a link to the zip. Please add it to your OP if you'd like. There's no need for me to create a separate thread.
phburks said:
@jboxer, I figured out the flashable zip. Just tested it on an unrooted 2.3.3 installation and it worked perfectly. I PM'd you a link to the zip. Please add it to your OP if you'd like. There's no need for me to create a separate thread.
Click to expand...
Click to collapse
Thanks to phburks for the good work in figuring out why our update zip packages were being rejected by Clockworkmod Recovery. We now have flashable zips to root the G2X (works on stock GB rom) and to unroot it. They are listed in the first post that I have edited.
http://forum.xda-developers.com/showthread.php?p=17398464
what is deodexing :
SilverZero said:
Deodexed ROMs have their .apk's (which are basically the application packages) repackaged in a certain way. An "odex" can be thought of as a collection of parts of applications that have been pulled out and optimized before booting. This speeds up the boot process - in a way, it preloads part of the applications - but it also makes hacking those apps difficult because part of the original code is already extracted somewhere else.
Deodexing is just a process of putting those pieces back into the original applications. It takes a while to extract those parts and build the .dex cache (aka Dalvik cache), but only because the relevant parts aren't in an easy-to-access place for the system. The advantage of this is that an app can be modified effectively and the developer doesn't have to worry about conflicts from the separate odex part of the code.
So, short version: "Deodexed" ROMs have all their apps put back together. If an app can be themed, for example, a deodexed version of that app will not get messed up when the modified .apk tries to mesh with the odex of the original un-modified .apk. Because it's not there.
If you want an aftermarket theme, you need a deodexed ROM. I'm not sure if deodexing can be done to individual apps within a non-deodexed ROM.
I think that's the general idea, anyway.
Click to expand...
Click to collapse
STEPS :
*Go HERE root tour device .
*Download Busybox installer and install the latest version of busybox compatible with your device.
*Install ADB :
In your android device, go to settings --> applications --> development -->
Check USB Debugging
Make sure your device driver is already installed otherwise install kies software which will install drivers too.. Get kies from This LINK
You need to download this ADB.zip file i made to your system.. Download link
Extract the ADB.zip file from any applications like IZarc/7Zip/winzip/winrar.
credits : DEADLY
*Download Xultimate.
*Connect your phone to computer.(Make sure you have select USB debugging in Settings>Applications>Development)
*Extract xUltimate v2.3.3.zip and Launch Main.exe
*If everything goes well xUltimate should recognize the phone and make a connection.You now should see a list of options.
*Select option (1) pull /system/app. Wait until it complete.
*Select option (2)pull /system/framework. Wait until it complete.
*Then select option (3) Deodex /system/app. Wait until it complete.
[If encounter any error. Find out which .odex file is it. Then remove .odex file from folder origi_app in xUltimate folder]
*Then select option (4)Deodex /system/framework. Wait until it complete.
*Now Exit from xUltimate.
*Put the phone in USB mass storage.
*Go to xUltimate folder and copy "done_frame", and "done_app", and move them to the root of the sdcard.
*Now get out from USB storage mode.
*Open Command prompt.
( Goto folder where android sdk installed. Then goto platform-tools folder in it. Right click on free space in folder while pressing shift key.Select open command prompt here.
Now enter commands. )
*Enter following codes.
(if you are using adb shell in su for the first time, keep phone screen on. After entering "su" code, super user request prompt in phone. Press allow )
Code:
adb shell
su
stop
mount -o rw,remount /system/ /system/
cp /sdcard/done_app/* /system/app/
rm /system/app/*.odex
cp /sdcard/done_frame/* /system/framework/
rm /system/framework/*.odex
mount -o ro,remount /system/ /system/
reboot
*Enjoy your DEODEXED rom ! also thank : chamatht (for i learnt this from him ).
Troubleshooting :
srt99 said:
for those who are having troubles with option (3),
exit Xultimate, go to task manager and find process adb.exe, select it and click on end process!
that's it, now run xultimate and run option (3) [no need to run option 1 and 2 again]
Click to expand...
Click to collapse
____________________________________
thoughtfully scribbled by nikufellow
Hi! Thanks for the Guide!
I don't know if I am doing something wrong, but I can't make it work. Every .odex file give me a error, so delete every odex will not help, I guess. Have you or anyone tested this guide with our firmware? (original 2.3.6, Only root).
I was trying to deodex, so I could make some little changes (like battery icon) without flash another rom.
battery icon is working for me but the rest not.... I'm using Rom toolbox
Sent from my GT-I9070 using xda app-developers app
johnnybr said:
Hi! Thanks for the Guide!
I don't know if I am doing something wrong, but I can't make it work. Every .odex file give me a error, so delete every odex will not help, I guess. Have you or anyone tested this guide with our firmware? (original 2.3.6, Only root).
I was trying to deodex, so I could make some little changes (like battery icon) without flash another rom.
Click to expand...
Click to collapse
You need xUltimate v2.3.3 only
I do not respond to tech support via PM
Battery icon works on odexed stock rom. I try this method tonight
GT-I9070P®land
Just done deodexing a stock jb rom for i747 through kitchen, then I read this post. Awesome job, man. :good:
At first this method works,
later after i reflash rom, rooted and do this again,
i get bootloop, any idea?
I tried 5 times and everytime bootloop
But why use the stop command ? Doesn't that stop Android itself entirely ?
I give up writing anymore signatures.
hey bro why this method shows error of insufficient space...
can you help me in dis...
i m having samsung galaxy fit running on 2.3.6 ddkt3
Why i cant!? Heeeelp please!!
for those who are having troubles with option (3),
exit Xultimate, go to task manager and find process adb.exe, select it and click on end process!
that's it, now run xultimate and run option (3) [no need to run option 1 and 2 again]
srt99 said:
for those who are having troubles with option (3),
exit Xultimate, go to task manager and find process adb.exe, select it and click on end process!
that's it, now run xultimate and run option (3) [no need to run option 1 and 2 again]
Click to expand...
Click to collapse
Thanks for the info added to first post
____________________________________
thoughtfully scribbled by nikufellow
I am able to pull app and framework but i'm not able to deodex them I get errors for each file...
adb.exe is not running so that's not the problem
edit: I own a Samsung Galaxy R (i9103)
ROKronoS said:
I am able to pull app and framework but i'm not able to deodex them I get errors for each file...
adb.exe is not running so that's not the problem
edit: I own a Samsung Galaxy R (i9103)
Click to expand...
Click to collapse
This is for I9070, you only can get bootloop if you use this.
Somebody gave me this link in the R section
Thanks anyway
Me too
ROKronoS said:
I am able to pull app and framework but i'm not able to deodex them I get errors for each file...
adb.exe is not running so that's not the problem
Click to expand...
Click to collapse
And now?
S Advance I9070
Do this has chances to brick my device if i do it wrong?
Sent from my GT-I9070 using xda app-developers app
Одг: [GUIDE]DEODEX stock ROM !!!!
AnMotass said:
Do this has chances to brick my device if i do it wrong?
Sent from my GT-I9070 using xda app-developers app
Click to expand...
Click to collapse
If there is any possibility to brick, it would be soft brick, that you can repair by flashing firmware with Odin.
Sent from Galaxy S Advance
ive got the error message for every app too. deleted many odex files. but it wouldn´t getting better. adb not running in taskmanager.
Starting BluetoothAvrcp.odex
*****************************************
* Deodexing... *
UNEXPECTED TOP-LEVEL EXCEPTION:
org.jf.dexlib.Util.ExceptionWithContext: Unknown opcode: f1
at org.jf.dexlib.Util.ExceptionWithContext.withContext(Exception
ext.java:54)
at org.jf.dexlib.Code.InstructionIterator.IterateInstructions(In
nIterator.java:87)
at org.jf.dexlib.CodeItem.readItem(CodeItem.java:157)
at org.jf.dexlib.Item.readFrom(Item.java:76)
at org.jf.dexlib.OffsettedSection.readItems(OffsettedSection.jav
at org.jf.dexlib.Section.readFrom(Section.java:143)
at org.jf.dexlib.DexFile.<init>(DexFile.java:431)
at org.jf.baksmali.main.main(main.java:254)
Caused by: java.lang.RuntimeException: Unknown opcode: f1
at org.jf.dexlib.Code.InstructionIterator.IterateInstructions(In
nIterator.java:51)
... 6 more
Error occured at code address 36
code_item @0x13dc
Drücken Sie eine beliebige Taste . . .
*****************************************
MAJOR ERROR!! WITH DEODEXING! BluetoothAvrcp.odex
*****************************************
********DELETING INCORRECT FILES*********
please exit out of window "***Deodexing ADB Window, DO NOT EXIT!***"
any ideas?
shut_down said:
This is for I9070, you only can get bootloop if you use this.
Click to expand...
Click to collapse
I disagree , this is a generic method for deodexing most phones , it's just that the stupid Sammy made un-deodexable .apks for us to suffer in
"Viper kills.....again!"