{
"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"
}
Hello everybody!
The long wait has finally come to an end, as I successfully compiled CWM Touch Recovery for Medion Lifetab P9514. It works great on IceCreamSandwitch 4.0.3 Release 2 and it should also work on previous ICS updates. However, it is not compatible with Honeycomb 3.2!
Before we begin a warning is in order: You are making changes to your tablet’s software at your own risk!
So let's start. I advise you to first backup your stock recovery, just in case something goes wrong. There are couple of methods to do this. I will describe in my opinion the easiest, with adb commands for Microsoft Windows or Linux OS. This way you are not required to boot your tablet in special modes (fastboot or APX).
GETTING STARTED
When you connect LIFETAB to your PC, drivers should be installed automatically in Windows Vista/7. If they are not or if you encounter any erros, try the guide for Windows XP (original guide by @Pummelchen - android-hilfe.de).
Download drivers for WinXP: http://www.medion.com/au/service/_lightbox/treiber_details.php?did=10725
Extract the drivers - double click on "usb_p9514wxp.exe"
"Medion" folder will be created on C:/ drive, in there you will see "android_winusb.inf".
Open Device Manager: either by following the path "Start/Control Panel/System/Advanced System Settings/Hardware/Device Manager" or by right-clicking on "Computer" - "Properties" in start menu.
Connect your LIFETAB with a microUSB/USB Cable to the PC an wait for a few seconds.
In Device Manager "Other devices" should appear, there you will see "MTP" with a yellow exclamation mark. Right-click on it and choose "Properties".
Under "Driver tab" choose "Update driver".
Browse to C:/Medion and start the installation.
ADB/Fastboot tool for windows (USB drivers included): http://www.mediafire.com/download/bklnjn2x0fbln4b/MD_LT_P9514_Drivers_ADB_Fastboot.zip
You can install adb tools in Linux by following this guide: http://forum.xda-developers.com/showthread.php?t=2431956
Make sure you have USB-debugging enabled on your tablet (Settings – Developer options – USB debugging)
Run Windows Command Prompt (Start Menu – Run… – write in “cmd” – press OK); point the cursor to the ADB folder by using “cd” command (a simpler way: press SHIFT and right-click on ADB folder, choose "Open this folder in command window")
Open Terminal in Linux
Write the following order of commands in cmd:
BACKUP STOCK RECOVERY
See if your device is recognized (a long number)
Code:
adb devices
Enter the adb session
Code:
adb shell
Get root privileges
Code:
su
Make /system partition readable-writable, so you can make changes
Code:
mount -o rw,remount /system
Backup 1st file
Code:
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.backup
Backup 2nd file
Code:
mv /system/recovery-from-boot.p recovery-from-boot.p.backup
Create and backup stock recovery image file
Code:
dd if=/dev/block/mmcblk0p1 of=/sdcard/download/original-recovery-p9514.img
RESTORE STOCK RECOVERY
Should you at any time encounter problems with cwm touch, or you simply don't like it, you can restore your stock recovery. The commands are therefore reversed:
Restore 1st file
Code:
mv /system/etc/install-recovery.sh.backup /system/etc/install-recovery.sh
Restore 2nd file
Code:
mv /system/recovery-from-boot.p.backup /system/recovery-from-boot.p
Restore stock recovery to mmcblk0p1 partition
Code:
dd if=/sdcard/download/original-recovery-p9514.img of=/dev/block/mmcblk0p1
Warning: Be carful to use the right number in mmcblk0p1. This is /recovery partition, if you use others you might brick your tablet!
An easier way to have stock recovery back is to simply re-flash ROM update zip file. But by doing this you will loose root privileges, configuration and possibly user data.
I suggest you save "original-recovery-p9514.img" also to your external sdcard and possibly to your PC. You can use your USB connection cable or a file explorer (like ES File Manager) to transfer the file to an external data storage. Another option is this adb command:
Code:
adb pull /sdcard/download/original-recovery-p9514.img
FLASH CWM TOUCH RECOVERY
Now that you’ve successfully backed-up our stock recovery, let’s flash the new cwm touch. Again there are a couple of ways to do this, I will describe in my opinion the easiest.
First download attached file, extract it and copy cwm-recovery-p9514.img to your internal sdcard. You can simply use a USB connection cable and transfer the file to the path “/sdcard/download” or use a file explorer (like ES File Manager) to copy the file.
Another method is with ADB commands. Put cwm-recovery-p9514.img in ADB folder on your PC. Open windows command window and check that your tablet is recognized (adb devices). The following line will transfer the .img file to “download” folder (you can use any other name, but the folder needs to exist on your sdcard):
Code:
adb push cwm-recovery-p9514.img /sdcard/download
To flash cwm recovery on the recovery partition, use the following commands:
Code:
adb shell
su
mount -o rw,remount /system
dd if=/sdcard/download/cwm-recovery-p9514.img of=/dev/block/mmcblk0p1
You can now reboot your tablet.
INSTALL CWM TOUCH RECOVERY USING TERMINAL EMULATOR
This is a simpler and faster way to flash my cwm touch recovery, without needing a PC/Laptop.
Install one of free terminal emulators from Google Play Store.
Here are a couple of options:
ConnectBot
Android Terminal Emulator
Providing you already copied "cwm-recovery-p9514.img" to your tablet, skip this step. If not, look at the previous steps.
Open the terminal emulator app and insert these lines:
Code:
su
mount -o rw,remount /system
dd if=/sdcard/download/cwm-recovery-p9514.img of=/dev/block/mmcblk0p1
To restore your original recovery:
Code:
su
mount -o rw,remount /system
dd if=/sdcard/download/original-recovery-p9514.img of=/dev/block/mmcblk0p1
USING CWM TOUCH RECOVERY
To enter cwm recovery mode press hard buttons in combination: power off your tablet, press and hold VOLUME UP (PLUS) and press POWER. Once you see "Ota…" in the top left corner of the display, quickly press:
1X VOLUME DOWN (MINUS),
2X VOLUME UP (PLUS),
1X VOLUME DOWN (MINUS).
You will see the counter go to 4 and cwm recovery will start.
For a more practical access to the recovery, use this app: Quick Reboot.
Make a backup of your rom as soon as possible, to save your data.
Please do not attempt to flash any zip files using this recovery. You may damage your tablet in doing so.
"Wipe cache partition", "wipe dalvik cache" and "fix permissions" are safe processes, but use "wipe data/factory reset" only when needed.
ADDITIONAL INFORMATION
NOTE: I will leave older versions of cwm touch recovery available, should you have any problems with newer ones.
This guide wouldn't be possible, without the help from guys on http://www.avi-plus.com, Yves & Micky.
XDA:DevDB Information
[RECOVERY]CWM Touch 6.0.2.8 for MEDION LIFETAB P9514 [25.2.2013], ROM for the Android General
Contributors
MMWolverine
ROM OS Version: 2.3.x Gingerbread
Version Information
Status: Testing
Created 2015-02-04
Last Updated 2015-11-01
Briliant! Just found out, that there is CWM for my "old" P9514 ... great work!
Hope there will be some Custom-ROMs soon; maybe on CM basis - the Stock ROM is not that what I would call "well".
d3rm1k said:
Briliant! Just found out, that there is CWM for my "old" P9514 ... great work!
Hope there will be some Custom-ROMs soon; maybe on CM basis - the Stock ROM is not that what I would call "well".
Click to expand...
Click to collapse
Thanks! Actually not to difficult making a cwm recovery, but when it comes to custom roms I'm still a bit of a noobie. I am learning fast though, so maybe in the near future.
Oh btw, here's the recovery guide in german language: http://www.handy-faq.de/forum/medio...on_lifetab_p9514_13_1_2013_a.html#post2385512
Yes, I know. Because of that German post I searched here, hoping that there already might be a Custom ROM.
But I only have a LogIn here and not the muse to sign up at handy-faq.de, yet
Many thanks for this cwm, the installation worked like a charm.
One small remark, to enter cwm you have to hold the Volume Up (Plus) and Power button. You could perhaps change this in your guide (it is correctly in the guide in german language)
I have translated your guide to Dutch on my blog, I'll hope it's no prob:
http://blog.johanvanbogaert.be/2013/02/clockworkmod-voor-de-medion-lifetab.html
Rgrds Johan
Jopeke said:
Many thanks for this cwm, the installation worked like a charm.
One small remark, to enter cwm you have to hold the Volume Up (Plus) and Power button. You could perhaps change this in your guide (it is correctly in the guide in german language)
I have translated your guide to Dutch on my blog, I'll hope it's no prob:
http://blog.johanvanbogaert.be/2013/02/clockworkmod-voor-de-medion-lifetab.html
Rgrds Johan
Click to expand...
Click to collapse
Thanks for notifying me about the mistake, I already corrected it.
I updated the cwm to newest 6.0.2.8 and will change the adb drivers part of the guide, as some users have difficulties understanding it.
I see no problem that you translated my guide, after all it's from different sources and made to be used for free.
MMWolverine said:
Thanks for notifying me about the mistake, I already corrected it.
I updated the cwm to newest 6.0.2.8 and will change the adb drivers part of the guide, as some users have difficulties understanding it.
I see no problem that you translated my guide, after all it's from different sources and made to be used for free.
Click to expand...
Click to collapse
Hi MMWolverine, already flashed v6.0.2.8, only took a minute.
I've updated my own blog as well.
Instead of using adb it is much easier to use a terminal emulator (like ConnectBot) on Android todo the update.
To install cwm someone only needs his tablet, ConnectBot and ES File Explorer. No PC, adb, usb connection necessary for flashing cwm.
If someone has rooted his lifetab, your guide is more then easy to understand to do this installation.
But if you don't wan't to use a PC for flashing the following is possible: From the lifetab download the zip, extract with ES File Explorer,Flash with ConnectBot (only the 3 last commands from your guide are necessary: su,mount..., dd....)
Actually, I did plan to do both guides. But I wasn't sure how many people would agree to install the terminal. Will probably do this, as you recommend.
I was also hoping, that the recovery would be uploaded to Rom manager app. Says on recovery maker website, that you need to be the device owner. Medion still isn't added to device list.
I have checked ROM Manager before doing the installation manually, its a pitty its not jet implemented in ROM Manager. But the installation is quit straight forward.
If someone is ever making a custom ROM for the LifeTab P9514, please implement USB OTG, because thats an option I'm waiting for.
Great that you added the instructions todo the installation through a terminal emulator on Android. Just one remark, the adb shell command can be removed while using a terminal on Android.
What happens if you try to flash a zip with CWM? Why doesn't it work and what would break?
You need a properly written updater-script. If a zip isn't compatible, you will only get an error, but nothing will be changed.
Do you know if the CM10 based ROM that works on the P9516 would work on the P9514 too?
Thanks
The answer is no. CM roms are hardware based and if you would flash p9516 rom on p9514 it wouldn't even boot.
lost p9514 Stock rom
Hi together!
I have a problem! I want to get back to unrooted original stock rom in lifetab p9514.
Somehow, dont ask me how, I lost the backed up version.
Is there a possibility to download such rom - I couldnt find anything!
Thanks in advance!
W
wfmagic said:
Hi together!
I have a problem! I want to get back to unrooted original stock rom in lifetab p9514.
Somehow, dont ask me how, I lost the backed up version.
Is there a possibility to download such rom - I couldnt find anything!
Thanks in advance!
W
Click to expand...
Click to collapse
Hello,
you can get official rom by typing in your MSN number (written on the back of your tablet): http://www.medion.com/de/service/download/software.php
And I have a mirror here: http://www.mediafire.com/download/xi5b93rj55bc0e7/Lifetab_p9514.20120719.2-ICS-signed-ota-update.zip
Hope that helps.
works like a charm!
I love this Forum - thank you very much!
Related
Why should you root your Dream/G1?
You can install a full Linux distribution, like Debian.
You can run applications that require root, like Screenshot and Auto Rotate your Browser and or any other application.
You can install the latest Android build directly from the Android source tree.
Customize your boot image.
Create full backups of the state of your phone.
Create custom ROMs.
Install Applications to your SD Card to save space.
Use your phone as a tether to connect your computer/laptop to the internet.
Turn your phone into a wireless router that provides internet access.
Well, hopefully one of those reasons convinced you to get root access on your phone!
Preparing to Get Root on your Phone
Getting root on your phone involves exploiting a security hole that existed in an early version of Android. The versions with the security holes are known as RC19, RC28, and RC29 (or RC7 or lower for UK phones). As of RC30 (RC8 on UK), Google patched the security hole so that your phone can not be rooted (don't worry, we can still root it!).
To check your version, go to the Home Screen, click your menu button, choose "Settings", and then click "About phone". You will then see the following screen:
{
"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 have US-RC30/UK-RC8 or higher, you will first need to downgrade your phone to a previous version. (Skip these steps otherwise)
Format your phone's SD card to FAT32 mode:
Hook your phone up to your computer using a USB cable and then wait for the notification to show up in your title bar of your phone.
Click the notification, and then click "Mount".
A new removable disk should show up on your computer. Right click it and select Format, and select FAT32 as the file system type.
Download and unzip the RC29 or RC7 image file. Copy the DREAIMG.nbh file to the SD card. (RC29 for US, RC7 is for UK)
Turn the device power off.
Hold Camera button, and press Power button to entry boot loader mode. You should see a gray/white screen with instructions to flash your phone with the update on your SD card. If you don't see that, make sure you followed the instructions properly.
As per the on-screen instructions, press the Power button to start upgrade procedure. DO NOT DO ANYTHING TO INTERRUPT THIS PROCESS.
After it is finished, perform the restart your phone.
Rooting your RC29 or lower phone:
On RC29 phones and lower, anything you type into your keyboard is also being run in a hidden console with root permissions. More information regarding that at the bottom of this post. But, to get root access, do the following:
Instructions:
Download recovery.img or the new version by Amon recovery-RA-dream-v1.5.2.img and copy it to your SD card (see the previous instructions on how to copy from your computer to your Phone's SD card).
Download the Hard SPL and copy the zip file to the SD card.
All files must be on the root of your SD card.
Restart your phone. Wait for your phone to start up fully and show the home screen.
After your phone starts up, hit the enter key twice, type "telnetd" and press enter. (Yes, it will start up a contact search, don't worry. Just type it.)
Download an Android "Telnet" application from the Market and connect to localhost.
If you connect successfully, you will have a root prompt "#".
Type the following into Telnet (these commands will give you root access easier in the future):
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd sdcard
flash_image recovery recovery.img
cat recovery.img > /system/recovery.img
Now you have root!
What To Do Now That You Have Root
Now that you have root, you will want to apply "Hard SPL" to your phone. HardSPL is what will allow you to apply flash images from other regions (like UK on US phones, and vice versa), create full backups of your phone, install the latest build from the Android source, and usually resurrect your phone if it is "bricked". You have already downloaded the file to your SD card, so now you can apply it.
Power off your phone.
Start up in recovery mode by holding home and pressing power.
You will now enter recovery mode. You should see an exclamation.
If you do not see a menu on screen, press Alt-L to show the menu.
Press Alt-S to apply the update from the SD card.
After the update is complete, hold Home and press Back to restart.
And now, the last step! You are still running an old version of Android, but you want to upgrade to the latest and greatest update! You can do this, and not lose root by downloading modified versions of the updates.
First, choose a modified image from the list below:
ADP1.1: (md5: bacc58302e0b239d66c7bcc8db6c434b)
http://jf.odiness.com/v1.41/JFv1.41_ADP1.1_BuildEnvironment.tar.gz
http://android-dls.com/forum/index.php?f=24&t=241&rb_v=viewtopic
http://andblogs.net/2009/01/jesusfrekes-14-images-are-out/
RC33: (md5: f24b6c237775147cb4bc42efc2393973)
http://jf.odiness.com/v1.41/JFv1.41_RC33_BuildEnvironment.tar.gz
http://android-dls.com/forum/index.php?f=24&t=241&rb_v=viewtopic
http://andblogs.net/2009/02/new-rc33-based-images-from-jesusfreke/
RC8: (md5: de2d0d34adbb4015ee3aa5e4e7ca3c07)
http://jf.odiness.com/v1.41/JFv1.41_RC8_BuildEnvironment.tar.gz
http://android-dls.com/forum/index.php?f=24&t=241&rb_v=viewtopic
http://andblogs.net/2009/01/jesusfrekes-14-images-are-out/
Download the image.
Rename it to update.zip.
Copy it to your phone's SD card.
Turn your phone off.
Start up in recovery mode by holding Home and pressing Power.
Press alt-W to wipe your device. (You need to do this, or the device may hang at the flashing Android screen)
Press alt-S to apply the update.
And that's it! Remember to check the links up top to learn how to use root to do the advanced things I mentioned.
Rooting, Hacking, and Flashing your G1/Dream
Reserved for future posting
Wow this is great news keep the community updated. thanks man
EDIT:i just tested it my self!! your right this seems like root to me
Koush said:
I verified this by remounting the /system partition as read write and changing files around.
Click to expand...
Click to collapse
How did you do that?
Wow, good job!
I classify this as a major "oops" on Google's part...
humble said:
How did you do that?
Click to expand...
Click to collapse
mount -oremount,rw /dev/block/mtdblock3 /system
You can't remount that directory that unless you have root.
Use the dd command to copy stuff around (the cp command is not available). I should mention I'm a Windows guy, and am pretty clueless with Linux: my coworker figured the rest of this out once I got to a root prompt.
Incidentally, in the /system/bin directory there is a flash_image executable that changes the recovery.img used when you hard reset the device. I've noticed that I can run this without root access from a standard adb shell. Maybe we never needed to root the device after all... I think we can flash it without root access... I'm too scared to mess with that at all though.
i just rebooted from telnet!!! i must say this is cool
thanks dude I'm going to give it a run(not flashing) I'm scared too 428 and some change down the draine nooo
Yes!!! Now we dont even have to worry about the update.zip file!
Well, it still will be usefull for package updates.
I'm goin for the bootloader and pretty soon we'll be able to port Android to other HTC devices aswell.
Maybe this can be usefull its kind of old buthttp://benno.id.au/blog/2007/11/13/android-under-the-hood
well
i don't konw how safe it is but you can just chmod 777 files and access them through the glance file manager. can't open but you can copy and past them on the sd card and open from there. i wish i could figure out how to see them
i keep getting "Error running telnet: permission denied" in LogCat. any ideas ? i have rc29
hrm
i'm now getting Unable to chmod *******: Read-only file system across the board /////////////////nm i'm retarded
Koush said:
mount -oremount,rw /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
If you want to edit anything, you have to remount it as read/write.
yeah i forgot i rebooted my phone, lol just trying to see if i can figure out how to change the view when you mount the sd card to show all files.
anyone with RC29 getting root access ?
yeah i am
not that i know what to do with it
can u describe the steps ? i keep getting Permission denied
anyone know where the boot code is so I can tell it to mount all folders as read write at boot?
quedijo said:
Yes!!! Now we dont even have to worry about the update.zip file!
Well, it still will be usefull for package updates.
I'm goin for the bootloader and pretty soon we'll be able to port Android to other HTC devices aswell.
Click to expand...
Click to collapse
Good news!
Hope someone can develop something for Universal!
Cheers to all,
neerhaj said:
can u describe the steps ? i keep getting Permission denied
Click to expand...
Click to collapse
http://android-dls.com/forum/index.php?f=15&t=151&rb_v=viewtopic
All the steps are laid out there. pterminal downloadable and all.
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?
I've tried using ROM manager and booting back into recovery mode but it stalls at the Google unlock screen. I've also tried installing the stock version of 2.3.2 version from Rom manager but got the same results.
I've also flashed the clockworkMod recovery to 3.0.0.5 then rebooted into Bootloader where i selected the "Recovery" option but again I only reach the Google unlock icon screen. It's been sitting at that screen for the past 20mins. Only way past it is to boot normally (after i reinsert the battery).
I have tried restoring from a previous backup but that too fails because it cant reach the recovery portion of the process after rebooting.
About Phone
Version: 2.3.2
Baseband Version: I9020XXJK8
Kernel Version: 2.6.35.7-g81433b [[email protected]#1]
CPU INFO: ARMv7 Processor Rev 2 (v7l)
Mod Version: CyanogenMod-7-02102011-NIGHTLY-NS
Build #: GRH78C
Click to expand...
Click to collapse
any help is greatly appreciated.
reflash recovery
thejron said:
reflash recovery
Click to expand...
Click to collapse
try reflashing the recovery from within the bootloader with "fastboot flash recovery recovery.img" or something like that. you should find something about this here on XDA i think.
floomat said:
try reflashing the recovery from within the bootloader with "fastboot flash recovery recovery.img" or something like that. you should find something about this here on XDA i think.
Click to expand...
Click to collapse
thx. i'll try that now.
thx for the reply, this page worked:
http://forum.xda-developers.com/sho...ighlight=fastboot+flash+recovery+recovery.img
i was able to update the ROM to 2.3.3, while in recovery mode. I rebooted the device but now when i go to Reboot>Recovery it still hangs at the google unlock screen. I think the only way for me to successfully access the recovery screen would be to connect my phone to the pc and run the fastboot boot-recovery-clockwork-3.0.0.5-crespo.img file.
headsh0tshurt said:
I think the only way for me to successfully access the recovery screen would be to connect my phone to the pc and run the fastboot boot-recovery-clockwork-3.0.0.5-crespo.img file.
Click to expand...
Click to collapse
What's happening is that Android is overwriting your custom recovery whenever it reboots.
To fix it, you first have to go back to the stock rom. Then, using either root explorer or adb, you have to rename /etc/install-recovery.sh
That way, when you flash your custom recovery, it doesn't rewrite the stock one when you reboot.
Check out this link:
http://forum.xda-developers.com/showthread.php?t=740748
edit: Also, in case someone else reads your post about using fastboot to get into recovery... the command is actually: "fastboot boot recovery-clockwork-3.0.0.5-crespo.img"
Note the space, not hyphen, between boot and the recovery image
Edit2: Ugh, the link I gave is pretty unclear (very shoddy google work). Anyway, the idea in the link is right, the command to remount your system in adb is:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
The full list of commands would be:
adb shell
su [you have to allow root access on your phone at this point - superuser will give you a popup]
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /
cd etc
mv ./install-recovery.sh ./install-recovery.sh.old
kaimyn said:
What's happening is that Android is overwriting your custom recovery whenever it reboots.
To fix it, you first have to go back to the stock rom. Then, using either root explorer or adb, you have to rename /etc/install-recovery.sh
That way, when you flash your custom recovery, it doesn't rewrite the stock one when you reboot.
Check out this link:
http://forum.xda-developers.com/showthread.php?t=740748
edit: Also, in case someone else reads your post about using fastboot to get into recovery... the command is actually: "fastboot boot recovery-clockwork-3.0.0.5-crespo.img"
Note the space, not hyphen, between boot and the recovery image
Edit2: Ugh, the link I gave is pretty unclear (very shoddy google work). Anyway, the idea in the link is right, the command to remount your system in adb is:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
The full list of commands would be:
adb shell
su [you have to allow root access on your phone at this point - superuser will give you a popup]
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /
cd etc
mv ./install-recovery.sh ./install-recovery.sh.old
Click to expand...
Click to collapse
i ran adb shell and entered the commands listed above. Below is a screenshot of what was entered.
{
"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"
}
Now after I entered the mv ./install-recovery.sh ./install-recovery.sh.old
command it says that i can't rename the .install-recovery.sh because it doesn't exist. do i have to manually create a folder on the root with this name?
Did you go back to stock first? I think the files get deleted on a new rom, but for some reason you still have to rename the files while in stock. I had the same issue the first time I went to a custom rom.
I'm about to head to bed (asia) but I'll double check the directory in the morning.
You should also be able to Google the answer... I may have told you the wrong directory for the file. Look for something along the lines of android mount install-recovery.sh
Sent from my Nexus S using XDA App
No i didn't go back to stock prior to running the earlier cmd lines.
while in USB Debug mode, i transferred over the GRI40-2.3.3-rooted.zip into the phones' clockworkmod/backup folder. i then rebooted it into the bootloader and:
ran fastboot boot recovery-clockwork-3.0.0.5-crespo.img
Click to expand...
Click to collapse
I then chose the Backup & Restore option and selected to Restore the GRI40-2.3.3-rooted.
Once it was done i then selected reboot, it powered back on with full stock image. i rebooted it once more to confirm it had the stock image of 2.3.3. then from the bootloader screen i selected the recovery option and it took me to the screen with the android icon and the exclamation mark above it.
headsh0tshurt said:
No i didn't go back to stock prior to running the earlier cmd lines.
while in USB Debug mode, i transferred over the GRI40-2.3.3-rooted.zip into the phones' clockworkmod/backup folder. i then rebooted it into the bootloader and:
I then chose the Backup & Restore option and selected to Restore the GRI40-2.3.3-rooted.
Once it was done i then selected reboot, it powered back on with full stock image. i rebooted it once more to confirm it had the stock image of 2.3.3. then from the bootloader screen i selected the recovery option and it took me to the screen with the android icon and the exclamation mark above it.
Click to expand...
Click to collapse
So now if you delete or rename install-recovery.sh you should be good. For future reference
Code:
fastboot boot
Doesn't flash anything so you're literally just booting into an image so no matter what you wouldn't boot back into that image without the command again. If you want to flash a new recovery without using ROM Manager you can use the following command:
Code:
fastboot flash recovery recovery-clockworkmod-crespo-3.0.0.5.img
kenvan19 said:
So now if you delete or rename install-recovery.sh you should be good. For future reference
Click to expand...
Click to collapse
Okay I was not able to locate the file "install-recovery.sh" file on the SD, so from bootloader, I ran the code:
Code:
fastboot flash recovery recovery-clockworkmod-crespo-3.0.0.5.img
and went into recovery mode where i ran the latest nightly (cm_crespo_full-12.zip) and rebooted it more than once and each time it gets stuck @ the cyanogen mod7 boot screen....progress :/
headsh0tshurt said:
Okay I was not able to locate the file "install-recovery.sh" file on the SD, so from bootloader, I ran the code:
Code:
fastboot flash recovery recovery-clockworkmod-crespo-3.0.0.5.img
and went into recovery mode where i ran the latest nightly (cm_crespo_full-12.zip) and rebooted it more than once and each time it gets stuck @ the cyanogen mod7 boot screen....progress :/
Click to expand...
Click to collapse
interesting...Firstly because I wasn't paying close enough attention and mistyped the command (it should be fastboot flash recovery recovery-clockwork-crespo-3.0.0.5 not fastboot flash recovery recovery-clockworkmod-crespo-3.0.0.5) and it worked nonetheless.
There is a reason, however, you most likely weren't able to find the file etc/install-recovery.sh and that is because it isn't on the SD card. Unless you're using Root Explorer (paid app on the market, link here: https://market.android.com/details?id=com.speedsoftware.rootexplorer&feature=search_result) you're not going to see it.
Suggest you try the instructions at the bottom of this page > http://jaxov.com/2011/02/how-to-root-android-2-3-3-gingerbread-on-nexus-s/
7-step process that will help you go to CMR instead of stock recovery. Worked perfectly for me.
kenvan19 said:
interesting...Firstly because I wasn't paying close enough attention and mistyped the command (it should be fastboot flash recovery recovery-clockwork-crespo-3.0.0.5 not fastboot flash recovery recovery-clockworkmod-crespo-3.0.0.5) and it worked nonetheless.
There is a reason, however, you most likely weren't able to find the file etc/install-recovery.sh and that is because it isn't on the SD card. Unless you're using Root Explorer (paid app on the market, link here: https://market.android.com/details?id=com.speedsoftware.rootexplorer&feature=search_result) you're not going to see it.
Click to expand...
Click to collapse
yeah i copy/pasted what you wrote in my response but in actuality i wrote the correct file name into the the CMD and it went through. IF/when i get past the CM7 boot screen i'll look into the root explorer app. thx for the assist
kenvan19 said:
interesting...Firstly because I wasn't paying close enough attention and mistyped the command (it should be fastboot flash recovery recovery-clockwork-crespo-3.0.0.5 not fastboot flash recovery recovery-clockworkmod-crespo-3.0.0.5) and it worked nonetheless.
There is a reason, however, you most likely weren't able to find the file etc/install-recovery.sh and that is because it isn't on the SD card. Unless you're using Root Explorer (paid app on the market, link here: https://market.android.com/details?id=com.speedsoftware.rootexplorer&feature=search_result) you're not going to see it.
Click to expand...
Click to collapse
.cruiser said:
Suggest you try the instructions at the bottom of this page > http://jaxov.com/2011/02/how-to-root-android-2-3-3-gingerbread-on-nexus-s/
7-step process that will help you go to CMR instead of stock recovery. Worked perfectly for me.
Click to expand...
Click to collapse
Thanks for the link. I went through the instructions and the results were the same. the end of the instructions mentions to get the Root explorer on the phone but that doesnt work b/c i cant bypass the CM7 boot screen. so i just restored it to GRI40-2.3.3-rooted.zip via the clockwork recovery
The install-recovery.sh file is missing in CM7 - you have to do this process from a stock rom.
Personally, this is exactly how I did it. You may try it this way if you like... you should have instructions for all the individual pieces.
1. Go back to stock 2.3.2
2. Get the OTA update to 2.3.3
3. Unlock your bootloader
4. Using the fastboot boot recovery method, install SU
5. Boot in to Android and then rename install-recovery.sh
6. Install rom manager
7. Flash CWM 3.0.0.5
Good luck! Who knows, maybe you have to have an unlocked bootloader to get CWM to stick.
kaimyn said:
The install-recovery.sh file is missing in CM7 - you have to do this process from a stock rom.
Personally, this is exactly how I did it. You may try it this way if you like... you should have instructions for all the individual pieces.
1. Go back to stock 2.3.2
2. Get the OTA update to 2.3.3
3. Unlock your bootloader
4. Using the fastboot boot recovery method, install SU
5. Boot in to Android and then rename install-recovery.sh
6. Install rom manager
7. Flash CWM 3.0.0.5
Good luck! Who knows, maybe you have to have an unlocked bootloader to get CWM to stick.
Click to expand...
Click to collapse
my impatience got the best of me. after restoring it to the stock 2.3.3. i just reinstalled all the applications. none of my downloaded files (music/wallpapers) were lost.
[sarcasm]just have to go through the joy of reorganizing each screen [/sarcasm]. Mostly i am pisssed that i'd have to start from scratch in Angry birds .
This happened to me with gingercollab. I did fastboot flash then booted straight to recovery and installed cm7. Everything was working fine until I restored my nandroid of gingercollab by mistake.
Sent from my Nexus S using XDA Premium App
the issue was never resolved. and i get the system update for 2.3.4 about twice a week and i cant install it b/c after it restarts it bombs out at the android icon w/ the excalamtion mark.
i've tried the factory wipe/reset thinking that would start me off clean but that didnt work.
Unless you RENAME the stock recovery it WILL NEVER STICK. Unlocked bootloader or not. I just reflash recovery from fastboot if/when I need it.
Sent from a bird cage, with a swing!
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???
My phone's LCD touchscreen is broken and the phone seems stuck in bootloop. I have access to a custom recovery (OrangeFox is installed, but I should be able to `fastboot boot` into any other).
I have read on this reddit post that it should be possible to flash a new ROM, push my computer's ADB public key to it, boot it and use `scrcpy` to control my phone.
However I'm stuck on the first step: how can I flash a new ROM to my phone via command line from OrangeFox or other recoveries?
You can't flash a Custom ROM via ADB, you've to do this via FASTBOOT or Custom Recovery.
xXx yYy said:
You can't flash a Custom ROM via ADB, you've to do this via FASTBOOT or Custom Recovery.
Click to expand...
Click to collapse
Yes, when I said "ADB", I meant the ADB of a Custom Recovery. I can boot into OrangeFox and then `adb shell` into it. I'm wondering how to install a ROM from there.
Installing the ROM from Fastboot would work too, if it's simpler.
TWRP uses dd to flash raw images and tar + gzip to backup/restore userdata partition. It's all done with shell scripting and adb shell is nearly the same.
@peoro The custom rom zip archive is build as OTA update.zip and either has a payload.bin (A/B slots) or *.dat.br compressed images for A-only devices. Both can be unpacked to get the raw images. Those images can be flashed via ADB or via fastboot.
peoro said:
Yes, when I said "ADB", I meant the ADB of a Custom Recovery. I can boot into OrangeFox and then `adb shell` into it. I'm wondering how to install a ROM from there.
Installing the ROM from Fastboot would work too, if it's simpler.
Click to expand...
Click to collapse
Don't confuse things:
Code:
adb shell
is used to run Android ( Linux ) system commands on Android devices.
WoKoschekk said:
@peoro The custom rom zip archive is build as OTA update.zip and either has a payload.bin (A/B slots) or *.dat.br compressed images for A-only devices. Both can be unpacked to get the raw images. Those images can be flashed via ADB or via fastboot.
Click to expand...
Click to collapse
Thank you for the replies. My phone is A-only (it's a Poco X3 Pro).
I just downloaded a new ROM (the latest crDroid 12 for my device) and I could find a number of `.dat.br` files in its zip:
Code:
$ unzip -Z1 crDroidAndroid-12.1-20230106-vayu-v8.12.zip | grep '.dat.br$'
odm.new.dat.br
product.new.dat.br
system.new.dat.br
system_ext.new.dat.br
vendor.new.dat.br
However I'm not sure where or how to flash these files and what other commands I need to use to e.g. format the various partitions or whatever is needed.
OrangeFox offers a `fox` command line tool (I believe it's a fork of TRWP's command). I believe it should help me with all of this, but I'm too much of a noob to know what to do and how.
Would you know where to find a good guide about installing a ROM via command line?
Otherwise could you tell me what commands I'm supposed to run and/or what operations I'm supposed to do?
I know my way around Linux pretty well, can write and read bash, but am a complete noob for anything related to android. Don't even know what the various partitions are, how they map to the contents of the drive and in general how the boot process works...
xXx yYy said:
Don't confuse things:
Code:
adb shell
is used to run Android ( Linux ) system commands on Android devices.
Click to expand...
Click to collapse
Yeah. ADB gives me access to a shell on the phone. I can have a shell while the phone is in the Custom Recovery (OrangeFox, currently) and I believe I should be able to flash a new ROM from there. That's what I'm trying to do.
Any way to install a new ROM would work for me: `dd`, the `fox` command line tool, or fastboot.
I'm good with bash, but don't know much at all about Android's internals. But I'd love to find a noob-friendly guide on how to flash to a ROM using whatever tool.
{
"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"
}
xXx yYy said:
Click to expand...
Click to collapse
Which part?
While my phone is running a custom recovery (OrangeFox, TWRP, whatever), that recovery is able to flash a new ROM. It offers a UI to do so. Right? I can't use the UI, but can run anything on the recovery, via the shell opened by ADB.
Am I saying anything wrong?
I have access both to `fastboot` and to the shell of a running custom recovery. But I don't know how to install the ROM (the content of crDroidAndroid-12.1-20230106-vayu-v8.12.zip ) with either tool, without using the custom recovery's UI.
peoro said:
I have read on this reddit post that it should be possible to flash a new ROM, push my computer's ADB public key to it, boot it and use `scrcpy` to control my phone.
Click to expand...
Click to collapse
The tool scrcpy installs *.odex compiled Java code on your device. This code isn't executable in any recovery.
Options for flashing your ROM:
– TWRP:
1. Put the raw images of your custom ROM into the ADB folder on your desktop and adb push them to the phone or use MTP to copy them.
2. Then you can use the openrecoveryscript.html (TWRP's commandline tool) to flash images.
TWRP Commandline Guide
</style>CLIENT SIDE/SCRIPTinstall FILENAME : install FILENAME zip file.
twrp.me
– ADB:
1. copy all raw images into ADB folder
2. use adb push to flash the images on your device.
– ABD (adb shell):
1. copy all images via adb push or via MTP to your device
2. enter the device's shell with adb shell
3. You said you are familiar with bash scripting. Do you know the dd command and its syntax?
CAUTION: The command dd overwrites EVERYTHING and without a warning!! Be careful and only use it if you know what you're doing.
Creating RAW images:
You need this tool to convert *.dat.br to raw image.
Flash custom ROM via fastboot:
1. convert the *.dat.br to RAW images.
*.dat.br filesRAW imagespartitionodm.new.dat.brodm.imgodmproduct.new.dat.brproduct.imgproductsystem.new.dat.brsystem.imgsystemsystem_ext.new.dat.brsystem_ext.imgsystem_extvendor.new.dat.brvendor.imgvendor
2. Use command
Code:
fastboot flash PARTITION RAW_IMAGE
to flash them all.
xXx yYy said:
Don't confuse things:
Code:
adb shell
is used to run Android ( Linux ) system commands on Android devices.
Click to expand...
Click to collapse
Using ADB commands or adb shell to run commands in the device's shell (#!/system/bin/sh) doesn't matter. Both passing commands through adb.exe to the adbd on the device. Killing the adbd will kill the connection anywhere.
You must NOT teach me what ADB is and/or how it works.
WoKoschekk said:
The tool scrcpy installs *.odex compiled Java code on your device. This code isn't executable in any recovery.
Options for flashing your ROM:
– TWRP:
1. Put the raw images of your custom ROM into the ADB folder on your desktop and adb push them to the phone or use MTP to copy them.
2. Then you can use the openrecoveryscript.html (TWRP's commandline tool) to flash images.
TWRP Commandline Guide
</style>CLIENT SIDE/SCRIPTinstall FILENAME : install FILENAME zip file.
twrp.me
– ADB:
1. copy all raw images into ADB folder
2. use adb push to flash the images on your device.
– ABD (adb shell):
1. copy all images via adb push or via MTP to your device
2. enter the device's shell with adb shell
3. You said you are familiar with bash scripting. Do you know the dd command and its syntax?
CAUTION: The command dd overwrites EVERYTHING and without a warning!! Be careful and only use it if you know what you're doing.
Click to expand...
Click to collapse
Thank you a lot for the detailed answer.
I used the TWRP approach as it seems the simpler.
I know `dd` and can read its man, but I'd rather not mess with the phone's partitions and block devices, unless it could result in a different outcome than using the `twrp` tool.
I tried to install two different ROMs (Lineage and crDroid), but neither manages to boot.
I can see that the few visible pixels on the broken LCD are in different colors for the two ROMs (so it did manage to install something), but neither ROM ever reaches a point where the power button turns the monitor on or off: they're both stuck on the bootloader.
What I did is basically this:
Bash:
$ twrp wite cache
$ twrp wipe system
$ twrp install $ROM.zip
$ twrp format data
$ twrp wipe dalvik
$ twrp wipe cache
$ reboot
If that's a correct way to install a ROM, then I guess I have my answer: some of my phone's hardware is broken
peoro said:
What I did is basically this:
Bash:
Click to expand...
Click to collapse
Use the adb sideload option to flash your ROM. That's the usual way to install it.
Code:
adb shell twrp sideload # to activate the process on client
adb sideload <ROM_PACKAGE> # to activate the process on host
Flashing starts automatically.
xXx yYy said:
You must NOT teach me what ADB is and/or how it works.
Click to expand...
Click to collapse
I'm not teaching. I just gave arguments.
peoro said:
If that's a correct way to install a ROM,
Click to expand...
Click to collapse
Yes, it's the correct way to install. All you need to wipe/format is data.
peoro said:
I tried to install two different ROMs (Lineage and crDroid), but neither manages to boot.
Click to expand...
Click to collapse
Seems you already found the solution yourself
How do you know the ROM does not boot? note first boot takes up to 10 minutes.
alecxs said:
Seems you already found the solution yourself
How do you know the ROM does not boot? note first boot takes up to 10 minutes.
Click to expand...
Click to collapse
When the screen broke, I could tell that the ROM didn't work, because:
1. My phone didn't connect to my router. I can tell by looking at the router's log or at internet services that tell me the last time the device was online.
2. If I try to call or send SMS to SIM on the phone, the phone doesn't ring or vibrate.
3. The screen never turns off. Not even when I press the power button.
All those points still hold with the newly flashed ROM too. Of course now it can't connect to anything, but it still doesn't react to incoming calls or to the power button.
I can kinda see from the glitchy colors on the bottom of the broken LCD that the bootloader animation is displayed, but it seems that it's stuck there...
If you have any ideas on how to debug this, I'm very interested.
This is a dump of `dmesg` (from the custom recovery). It shows a bunch of errors, but I can't tell whether any is about real hardware issues.