Database Info

[GUIDE] Root Cheat Sheet

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?

[APP - Nexus, MT3G, Droid, Evo, Hero] Search2Play - Control Music with the Search Key

Hello all, I just completed an app I'd like to share with you all.
It's called Search2Play, it lets you play and pause your music by pressing a button on your device. On most devices, it is the search key. Currently, the Nexus & MyTouch 3G both use the Search key, whereas the Droid uses the Camera key. If you have physical keys (i.e. Droid, MT3G, G1, etc) then it will work when the phone is locked, but if you have capacitive keys (Nexus, Moment, Eris, Incredible, etc) then the screen must be on (lockscreen works, and fully unlocked of course).
It is available on the market under the name "Search2Play (Root Required)". It's totally free.
It requires root permissions to install. It also requires that you have a version of BusyBox that supports the "cp" command. Only Droid users probably have to worry about the busybox version, as most other custom ROMs have that already. Droid users, I recommend CyanogenMod for Droid or Bugless Beast as I know both of them have the right version.
It does not run in the background or install a service, just makes some changes to a few files on the /system partition.
The UI is very simple, just two buttons and some text explaining the app. Once you hit install, it will ask for permission to use root, you must hit accept or the app won't serve its purpose
The other button, "Restore", lets you remove the mod and go back to stock settings, where the search button brings up search, etc.
Supported Devices:
Nexus
Spica
Hero (GSM & CDMA)
Galaxy S devices (all US variants and probably the i9000 as well. It's not tested)
MyTouch 3G
Droid 1 (I've been told DX & D2 work as well, though I'm not sure how :?)
Evo (must be NAND unlocked or S-OFF)
Desire (must be NAND unlocked or S-OFF)
Free Version on Market:
{
"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"
}
Or click this from your device: Search2Play Free
See the Market to view a screenshot. Please give me some feedback. Thanks! Hope you enjoy the app :
FOR DEVICE REQUESTS SEE POST #3

Changelog:
1.4.1 thru 2.1:
Add support for Evo, GSM Hero, CDMA Hero, & Samsung Spica (thanks to Aasheet Kumar for the files I needed for Spica support!)
1.4:
Fixed rare root checking bug on some Droid ROMs, and maybe some Nexus ROMs too
1.6+ only now, sorry, it's not like any device this works for isn't updated to at least 1.6
1.3:
Now checks if the SD card is present on launch instead of just crashing if it's not there
Cleaned things up more
Merged some code between the donate & free versions
Better checks to see if it can be installed
1.2.5:
FINALLY stopped it from causing buttons to stop working. Checks for compatibility, and throws an error if it detects it can't run.
1.2:
Droid support!!
More should fix a few FC issues some people have seen. Let me know if you have problems.
1.1.2:
Fixes the not restoring bug
1.1.1:
Failed attempt at fixing the not restoring bug.
1.1:
Support for low res devices.
Now works with MT3G! Since it has a hard search key, it will even work when the phone is locked
Deletes files from SD card once done installing.
Cleaned up more code.
1.0.1:
Sets system back to Read-Only once finished installing
Cleaned up some code, if you have FCs let me know.
1.0:
Base release

If you want to request support for your device here's what I need. Note that your device must be able to be rooted and the system partition must be able to get read/write access from userspace. I.E. any Desire or Evo or any other recent HTC device with a NAND lock will not work, unless it has been NAND unlocked with an S-OFF bootloader, like via Unrevoked.. If your device has all that, get this info and send me an email at [email protected]
Run the command "adb shell mount" and tell me the output. I don't need the whole thing, just the line referring to the system partition. I.E. "/dev/block/mtdblock3 on /system type yaffs2 (ro,relatime)" is the line on the Nexus, it should be similar to that.
Then, run "adb shell getprop" and tell me the 1-4 lines related to the keyboard, like hw.keyboards.*.devname and tell me those lines. I.E the Nexus returns "mahimahi-keypad". Yours should be similar.
Finally, run "adb shell ls /system/usr/keylayout/". It should return a list of files all ending in ".kl"
Remember the keypad name from step 2? Good
There should be a ".kl" file matching that name (like mahimahi-keypad.kl). Pull that file with "adb pull /system/usr/keylayout/keypadname.kl directory" with directory being the folder you want to pull the file to and keypad name being the name from step 2.
Zip that file, and then send it to me please.
That should be it, if you have any questions or problems with this list hit me up on GTalk or email me. [email protected] for both GTalk & email.

Dear geniusdog
I just tried out your app.
I installed it, run it, pressed the install button, allowed root access and rebooted mynexus one. But after that reboot, my sell doesn't react on anypressed buttons anymore. I can only use the touchscreen...
I also tried to restore in your app, but there appeared a window saying that the app is not responding anymore.
How can I manually restore it? Is there a command or some files, I can edit?
Thanks for your help

bayoffire said:
Dear geniusdog
I just tried out your app.
I installed it, run it, pressed the install button, allowed root access and rebooted mynexus one. But after that reboot, my sell doesn't react on anypressed buttons anymore. I can only use the touchscreen...
I also tried to restore in your app, but there appeared a window saying that the app is not responding anymore.
How can I manually restore it? Is there a command or some files, I can edit?
Thanks for your help
Click to expand...
Click to collapse
Sorry for the issue. I have uploaded a new version of both apps that should fix the problem. If you can download the app and install it again, otherwise, PM me & I will give you manual instructions to restore it.
Also, just some technical details, the problem was caused because I had set it to create the directory on the start of the application. After that I removed it once you clicked the button & the install was finished. Because of that, if you clicked restore after install, it would fail to find the directory and then proceed to FC. Sorry for the trouble

Droid Support!!!!

Help!!!!!
I have installed V1.0.4, but my touch keys(back, Menu, Home and Search) don't work.
Then I have tried to restore it, but it's failed.
How could I fix it? Thanks.
My Rom is 2.1-update1 rooted.

hahabear said:
Help!!!!!
I have installed V1.0.4, but my touch keys(back, Menu, Home and Search) don't work.
Then I have tried to restore it, but it's failed.
How could I fix it? Thanks.
My Rom is 2.1-update1 rooted.
Click to expand...
Click to collapse
Hmm I dont have this issue, how does it fail? Does it just freeze, or does it FC, or does it say it finishes then do nothing? Also, what ROM, CM? Enomther? Please let me know so I can work on this.
Also, to fix it, download the attached file, & run the following commands (you must have ADB set up):
adb remount
adb shell rm /system/usr/keylayout/mahimahi-keypad.kl
adb push *path to downloaded file* /system/usr/keylayout/mahimahi-keypad.kl
Or you can just reflash your ROM, either way you'll get the same thing.

My phone is Nexus one.
My rom is Official v2.1-updated1.
When I execute the command as your indication.
"adb shell rm /system/usr/keylayout/mahimahi-keypad.kl"
rm failed for /system/usr/keylayout/mahimahi-keypad.kl, No such file or directory
What's wrong? And thank you for your quick reply.

hahabear said:
My phone is Nexus one.
My rom is Official v2.1-updated1.
When I execute the command as your indication.
"adb shell rm /system/usr/keylayout/mahimahi-keypad.kl"
rm failed for /system/usr/keylayout/mahimahi-keypad.kl, No such file or directory
What's wrong? And thank you for your quick reply.
Click to expand...
Click to collapse
Ok excellent that answers the second part of my question its failing to copy the file back over after deleting the original on certain ROMs.
You can just skip that step and go on to the "adb push" step. Also, can you run the command "adb shell cp" and tell me the output?

bingo! Thanks for your help. It's resolved.
On the other hand, I could get the mod.kl from SD Card, push again, Search2play will work, is that right?

hahabear said:
bingo! Thanks for your help. It's resolved.
On the other hand, I could get the mod.kl from SD Card, push again, Search2play will work, is that right?
Click to expand...
Click to collapse
Yes, but can you tell me what it says if you run the command "adb shell cp"
That will tell me if the issue is with the version of BusyBox on some ROMs.

Geniusdog254 said:
Yes, but can you tell me what it says if you run the command "adb shell cp"
That will tell me if the issue is with the version of BusyBox on some ROMs.
Click to expand...
Click to collapse
C:\N1root>adb shell cp
cp: not found
My god!!! It means there is not cp command in my phone?

hahabear said:
C:\N1root>adb shell cp
cp: not found
My god!!! It means there is not cp command in my phone?
Click to expand...
Click to collapse
Yeah exactly lol. Not sure if that was sarcasm or what, but thats what is causing the FC's and the failures some people are getting. And theres not a damn thing I can do about it.
I would recommend installing the CyanogenMod ROM, since it is fast, adds extra features, and supports cp Then the app will work just fine

Anyway. Thanks for your help. You are so kind. I will try new ROM later. And I will support your work. cu.

hahabear said:
Anyway. Thanks for your help. You are so kind. I will try new ROM later. And I will support your work. cu.
Click to expand...
Click to collapse
Thanks you very much for your support. Glad I could help you, if you have any other problems please email me, email listed in the market

Donate version now just to support me, added support for all devices to free version.
Please donate!

1.3 version uploaded
See changelog.

Any updates on newer phones?

KaliKot said:
Any updates on newer phones?
Click to expand...
Click to collapse
I can make it work for any phone without a NAND lock. Any requests?
I need to do the Galaxy S series, but the only one I can test is the Epic and I'm not sure if the others have different mount tables or not. Desire still has NAND lock so I can't do it. Not sure about Droid2/X. Just email/Twitter/PM me or post here with a request. I'll get back to you.

Garminfone full hard root Achieved

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 ?

[RECOVERY]CWM Touch 6.0.2.8 for MEDION LIFETAB P9514 [25.2.2013]

{
"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!

[Zte][warp7]Permroot[kingroot]

Will type up better guide later on gonna include my ota i pulled as well maybe help someone
btw do at ur own risk im not responsable if u mess the phone up
added batch script hope it works to automate the process and guide u. before u can use this guide or batch script make sure to enable developer settings and adb
you can download it this https://forum.xda-developers.com/attachment.php?attachmentid=4181698&stc=1&d=1497456929 extract it go into the folder find root.bat double click file.
or follow the guide below
1.need to get temp root with king root first grab that here https://kingroot.net/ grab file for android not windows version
grab this file https://forum.xda-developers.com/attachment.php?attachmentid=4180414&stc=1&d=1497364232
2.once extracted go inside folder. hold down shift key and right click inside the folder. click open command window here
{
"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"
}
unhide for root guide
3. type this "su"
then continue guide
4. type this "getprop ro.product.name"
should show output "ZTE_BEAM"
5. type this "setprop persist.sys.k ZTE_BEAM"
6. type this "getprop persist.sys.k"
output "ZTE_BEAM"
7. type this "cd /dev/block/platform/soc.0/7824900.sdhci/by-name/"
Lets backup recovery
8. type this "dd if=recovery of=/sdcard/recovery.img"
Lets write boot to recovery!
9. type this "dd if=boot of=recovery"
10. type this inside of adb shell "reboot recovery"
if u get black screen just hold power down to reboot
once booted up
make sure your still inside adb command prompt
11. type this "adb shell"
12. type this "su"
13. type this "id"
should show this output
"uid=0(root) gid=0(root) context=u:r:shell:s0"
then to set permissive
14. type this "setenforce 0"
15. type this "getenforce"
output "Permissive"
16. to test if mount system rw while still root type "mount -o remount,rw /system"
if it mounts no errors then system is writeable
reboot
if for some reason u cant write to system u can try
run this command in adb shell or terminal
reboot disemmcwp
to re-enable write protection issue this command
reboot emmcwpenab
working on replacing king with supersu til then perm root with kingroot
enjoy
and u wanna donate for my hard work click here http://paypal.me/riley60
to restore recovery back to stock u can do once u have perm root do this to restore recovery
type this inside of adb shell dd of=recovery if=/sdcard/recovery.img
hit the thanks button if my post was helpful
original guide here
thanks jcase for his guide for me to base on
https://plus.google.com/+JustinCaseA...ts/KzgyHLgVhwo
also dont forget to hit the thank you button if this post was helpful
ota file attached may help some that are bricked
to remove annoying lock screen with ads
open king root then touch the 3 dots goto settings
then touch accelerate charging turn switch it off
then that annoying part is gone if purify is installed remove it and everything should be good.

Awesome, do you know if this will work on the ZTE Warp Elite?

everyone get their phone rooted ok

Well 2 things...
1: can you lost a guide on how you did those steps?
2: if I already did a software update for my phone, would that affect my chances of getting my phone permanently rooted?

those steps are the guide if you dont know what adb is or how to use it or king root then u could look both those up for guides on the 2. after u know how to use both its pretty much gain temp root have adb open then paste commands make sure they say the same as the guide for outputs follow all steps and should be good. unless they released an update that make it android n im sure it will work. once i send in these 2 dead phones to get repaired ill make a video guide of the steps in guide. as i dont know if it will break root to try redo all the steps to show everything i did.i will see if i can automate the process with batch script. aka filename.bat

updated the guide lil for if anyone who is lil new to adb etc

I've used adb when dealing with moto phones. But this has me confused as to what to actually put in cmd prompt. Either way you're a God among us. I'm going to attempt and see if I can get it working. Thank you for your work sir. Hope to see a batch script some day.

added batch script

No errors so far. Just a little sluggish.

Stevenbew said:
No errors so far. Just a little sluggish.
Click to expand...
Click to collapse
um no errors from what and whats sluggish and for anyone who asks i used the lastest kingroot version

Just errors in general. Nothing is giving me any problems. My phone was a little sluggish after first rebooting. Almost acted like a temp root until I ran the reboot disemmcwp cmd. Then no problems.

Stevenbew said:
Just errors in general. Nothing is giving me any problems. My phone was a little sluggish after first rebooting. Almost acted like a temp root until I ran the reboot disemmcwp cmd. Then no problems.
Click to expand...
Click to collapse
did u use script or manual

madvane20 said:
did u use script or manual
Click to expand...
Click to collapse
I did it manually. Knowing exactly what to type after you edited made everything alot easier to understand.

Stevenbew said:
I did it manually. Knowing exactly what to type after you edited made everything alot easier to understand.
Click to expand...
Click to collapse
ok i only asked cause im already rooted so i couldnt really test the script but it should work and at the end it tells what commands to type in to test. looks like i may need to edit the guide lil bit later and edit my script

I read the guide over and over. While I think I may understand, I'm still afraid to attempt this since it is my only phone and I cannot replace it currently if something were to go wrong. Your typing style makes it somewhat difficult to understand but nonetheless, thank you. I'll attempt when I'm able to replace the phone if something goes wrong.

Heartseed said:
I read the guide over and over. While I think I may understand, I'm still afraid to attempt this since it is my only phone and I cannot replace it currently if something were to go wrong. Your typing style makes it somewhat difficult to understand but nonetheless, thank you. I'll attempt when I'm able to replace the phone if something goes wrong.
Click to expand...
Click to collapse
use to batch script after u get temp root it will do most of the work for you and guide u through the rest

I need help, I can not do temporary root, so neither method allows me to enter the ADB get the SU command, should the phone have any condition before trying to apply them? My phone has software version 0B09 and the options are unlocked OEM and USB debugging, which I am doing wrong, any commentary? thank you!

Pirela said:
I need help, I can not do temporary root, so neither method allows me to enter the ADB get the SU command, should the phone have any condition before trying to apply them? My phone has software version 0B09 and the options are unlocked OEM and USB debugging, which I am doing wrong, any commentary? thank you!
Click to expand...
Click to collapse
grab the newest king root then if it fails keep trying it til it goes through. if it fails uninstall king root reboot reinstall try again. also try adding this commands first if it works without root "reboot disemmcwp" without quotes then try install king root and root see if u get temp root. then if it makes it easier i have a batch script made in the minimal adb and fastboot package

madvane20 said:
grab the newest king root then if it fails keep trying it til it goes through. if it fails uninstall king root reboot reinstall try again. also try adding this commands first if it works without root "reboot disemmcwp" without quotes then try install king root and root see if u get temp root. then if it makes it easier i have a batch script made in the minimal adb and fastboot package
Click to expand...
Click to collapse
Mandvane20 Thanks for your answer and interest
It was not possible to have some temp root, I tried with king root apk and pc, also with kingo root, I went to recovery and deleted the cache, I have force stop the application, I uninstalled and reinstalled, use reboot Disemmcwp, I have made multiple attempts and none has worked, I keep reading, searching and learning, I hope to get some way

Pirela said:
Mandvane20 Thanks for your answer and interest
It was not possible to have some temp root, I tried with king root apk and pc, also with kingo root, I went to recovery and deleted the cache, I have force stop the application, I uninstalled and reinstalled, use reboot Disemmcwp, I have made multiple attempts and none has worked, I keep reading, searching and learning, I hope to get some way
Click to expand...
Click to collapse
connect to pc open adb shell run king root while its trying to root keep typing su in adb shell tell it says root. or til it doesnt give u the error saying no su then proceed with guide see if that works