Related
Hi, I've got a Motorola Defy in Argentina (Carrier: Personal, means telecom). Well, I want to Root it, I've tryied z4mod, the ADB Method, 1 click, etc, and I still got the message "The application xxxx needs root user permissions", btw I have the Root (#) console in "adb shell", but I can't move files to /system/media (whit "AndExplorer" from mobile). Do I have to mount the FS there??
I've got the "Superuser" app working, and some applications whit "Root permissions" (because I've checked Remember my answer on the Popup when the app needs root privilegies)
Im a little bit confused because the version is not similar that you use here.
Version Number: JORLA_U3_6.14.7
Firmware version: 2.1-update1
So, I want to root it, and maybe upgrade to Froyo, but that questions make me scared (specially if i brick it).
What should I do?
PS: I've made a "Backup" with SystemRecovery app. This backup will work if I want to back my firmware to the stock one? (forgive the apps, I don't care).
Nobody can guarantee your backup will work, but it's a risk you'll have to take if you want to hack.
According to my search, your carrier uses UMTS 850 / 1900. This means you could have a different baseband firmware than the T-Mobile users here, and definitely different from the European users. The problem is, the only SBF files available are for European 900/2100.
So first things first, take a nandroid backup from the custom bootstrap recovery if you can get that working. Back up those files somewhere safe.
Read about the "3g fix". There is a folder containing the baseband firmware files, and you'll want to back those up in case you lose 3g on a custom ROM.
If your phone becomes unbootable, you'll have to flash an SBF to boot it, *then* root it again, install custom recovery again, and finally restore the nandroid backup.
Sent from my Nexus One using XDA App
Ok, thanks for the info. I've tryied to do a "nandroid backup" with the upgrade.zip stuff, but it just restarts and do nothing. I can't see any changes on my SDcard.
BTW, how I can run a .apk as root? (I want the AndExplorer to be root so I can copy some stuff to /system). I've got actually a root (#) terminal in adb shell and in Terminal emulator (via command su).
Thanks
cocus said:
Ok, thanks for the info. I've tryied to do a "nandroid backup" with the upgrade.zip stuff, but it just restarts and do nothing. I can't see any changes on my SDcard.
BTW, how I can run a .apk as root? (I want the AndExplorer to be root so I can copy some stuff to /system). I've got actually a root (#) terminal in adb shell and in Terminal emulator (via command su).
Thanks
Click to expand...
Click to collapse
How are you attempting to do this backup?
You need to download the bootstrap custom recovery, and use that to boot into the recovery menu. From there you go into backup/restore.
If you have successfully rooted your phone, then all apps have the opportunity to run as root. They should be able to make the request via Superuser Permissions, which would then prompt you.
Ok, but the bootstrap custom recovery is for 2.51 or similar firmware numbers, I've got 6.14. So, I really didn't test because I don't have experience with this things and I don't want to screw up all.
I tell you, for example, the Terminal Emulator runs on root when I run "su": Android requested Superuser permissions to me, and I ticked remember option, and now I can run "su" without the Superuser request.
BTW, I've got a root shell on adb (when I reboot the phone, I loose the root ). That means that is rooted??? (Got it using RATC)
Well, either it's compatible or it's not. If the bootstrap makes your phone unbootable... I guess you'll have to try for a warranty claim
Sent from my Nexus One using XDA App
Hahaha, I like to flash things and understand how it works, but in this case, I would prefer not screw nothing. Btw, I've buyed it on 15/jan.
So, for my other question the Terminal Emulator runs on root when I run "su": Android requested Superuser permissions to me, and I ticked remember option, and now I can run "su" without the Superuser request.
But when I restart the phone, I loose the # on "adb shell".
BTW, I've found the open source code of an earlier version of my defy on
opensource.motorola.com/sf/go/projects.moto_defy/frs.defy_latam
Anyone knowns how to compile this? I've got Debian lenny, Ubuntu 10.04, Ubuntu 10.10.
Thanks
Compiling a ROM yourself won't help if you can't sign it with Motorola's key. Yay locked bootloader...
Sent from my Nexus One using XDA App
Cocus,
I got the same phone as yours. Also from Personal.
And I am on the same situation, want to flash it, but not to brick it.
Let me know if you find out something ...
Hi, yes you can contact me via PM & I will send all the stuff that I've got. But I only get the rootshell via RageAgainstTheCage. When you reboot it you loose it, but you can use "su" or "rootshell" to get it again.
Now Im playing with C and C++ native code, with the ndk and sdk (no java ). Contact me
z4root worked in argentine (Latin American) defy.
Hi
I have a Motorola Defy like yours , (in Argentina - Carrier: Personal ).
I have rooted successfully using z4root 1.3.0 , that you can get from this post (look attached file at end ):
http://forum.xda-developers.com/showthread.php?t=833953
With z4root 1.3 you have the option of get root temporarily or permanent. The first one doesn't works for me ( no errors but no root ). The permanent root yes, works like a charm .
Hi, It seems that is not working for me... I've touched the permanent option, it restarted and the z4root says that is rooted, but I haven't the root console in adb shell, neither the apps run as root.
Edit: If I try to run "su" on the non-root console($) it says "Permission denied". But, running "rootshell" from RATC, it gives me a root shell.
I am pretty new to this whole android market. I have a stock epic 4g running DI18 and 2.1 update 1, rooted with the one-clicked root available on the sticky note forum[forum.xda-developers.com/showthread.php?t=770388]. It installed superuser and Clockwork Recovery mod 2.5 and i have been able to access that with no problem, even did a system backup. i tried using the remount/unmount feature in this and it read that the filesystem was unmounted and mounted, but i could not figure out how that could operate with the root tools application, because i have to reboot the system and it still reads the same problems. I am not looking to change roms just yet because the SQL benchmark test scores are 49.4 seconds which seem to be enough for me. I am however trying to change the themes, boot animation, and move the cache to SD card. I have downloaded the SetCPU, titanium backup with the available BusyBox in help menu, and Root Tools by Jrummy16. The root tools application works to manage applications, but anytime i try to use any "tweaks or hacks" such as ad blocker, it does not allow it and shows me a screen reading, "unable to remount filesystem read/write." To fix this problem i downloaded android SDK on my windows 32 bit system, and downloaded all of the neccesary drivers. Most of the instructions tell you to access the Command Prompt on the computer and use:
cd\
cd androidsdk\tools
adb devices
The problem is.. once i get the file to read C:\androidSDK\tools, i try to enther adb devices and it reads to me that " 'adb' is not recognized as an internal or external command, operable program or batch file"
I am just trying to get my root tools to work so i can manage my cache and use the ad blocker, and possibly install new roms later. i also tried using the 'su' command and it said it was not recognized.
Few questions:
Is there any steps i missed to be able to develop and change my themes, or is there anything i should have used instead of the programs i used?
Is there a different way to access adb shell on the epic 4g?
Is there another way to change themes/fonts/widgets/scroll animations?
hookinhorns81 said:
I am pretty new to this whole android market. I have a stock epic 4g running DI18 and 2.1 update 1, rooted with the one-clicked root available on the sticky note forum[forum.xda-developers.com/showthread.php?t=770388]. It installed superuser and Clockwork Recovery mod 2.5 and i have been able to access that with no problem, even did a system backup. i tried using the remount/unmount feature in this and it read that the filesystem was unmounted and mounted, but i could not figure out how that could operate with the root tools application, because i have to reboot the system and it still reads the same problems. I am not looking to change roms just yet because the SQL benchmark test scores are 49.4 seconds which seem to be enough for me. I am however trying to change the themes, boot animation, and move the cache to SD card. I have downloaded the SetCPU, titanium backup with the available BusyBox in help menu, and Root Tools by Jrummy16. The root tools application works to manage applications, but anytime i try to use any "tweaks or hacks" such as ad blocker, it does not allow it and shows me a screen reading, "unable to remount filesystem read/write." To fix this problem i downloaded android SDK on my windows 32 bit system, and downloaded all of the neccesary drivers. Most of the instructions tell you to access the Command Prompt on the computer and use:
cd\
cd androidsdk\tools
adb devices
The problem is.. once i get the file to read C:\androidSDK\tools, i try to enther adb devices and it reads to me that " 'adb' is not recognized as an internal or external command, operable program or batch file"
I am just trying to get my root tools to work so i can manage my cache and use the ad blocker, and possibly install new roms later. i also tried using the 'su' command and it said it was not recognized.
Few questions:
Is there any steps i missed to be able to develop and change my themes, or is there anything i should have used instead of the programs i used?
Is there a different way to access adb shell on the epic 4g?
Is there another way to change themes/fonts/widgets/scroll animations?
Click to expand...
Click to collapse
I'm not sure if you had a typo in your original post or if that is how you actually entered the commands on your computer when you tried this, but based on the "paths" you entered, the commands should be:
CD\
CD\androidsdk\tools
adb devices
As for the themes, fonts, etc., there is an app in the market called MetaMorph that will do that for you. You just need to have .zips for it to apply.
There is also a tutorial for MetaMorph "somewhere" in the "Themes" section on XDA. I couldn't find a link to post for you, but I know it's there!
As far as getting in adb if you have windows XP you can go to the tools folder and hold shift and right click it. In the.menu it will say start command prompt here. Click it. Now you are on your tools folder where adb is. Then you can use adb and get into the shell.
Sent From My Evo Killer!
A Work in progress.
DISCLAIMER!
This Document ONLY applies to Acer Iconia A100 devices. For info on upgrading from HC to ICS you can look HERE to see the method I used to upgrade from stock HC 3.2 GEN2 to ICS (Note: This was before the general ICS release. It works on OTA update also) Then follow these directions to get to CWM with Custom ROM.
I'm writing this because we STILL don't seem to have a single clear set of instructions. So here is my attempt at getting one started. Please feel free to point out errors, or help us build a set of directions. I'm not trying replace anyones documentation or take credit for anything. All the info in these directions can already be found here in various posts.
Thanks to Vache, Civato, ZeroNull, Euclid's Brother, Ptesmoke, abliss, aznmode, eew245, crossix, Icewyng, toyface, PG101, Smokku and Everyone else for all the Work an Insight.
ROOT
To root ICS Leaks you need to use mempodroid(info & file here). Eew245 wrote up instructions (on applying mempodroid on A100 to obtain a root shell). ZeroNull also has made a basic script found here that will root the device for you if you prefer.
I use the method outlined by Eew245. You can use your own "su" and "busybox" binaries if you saved them. This method provides full permanent root.
I suggest you install superuser.apk and busybox installer after rooting. Superuser.apk will provide access control for superuser and busybox installer will allow you to update busybox. I also recomend installing terminal emulator(don't forget to configure it to use /system/xbin/sh after you install busybox).
UNLOCK
ZeroNull has made an easy to use package with instructions here If you don't have the Android SDK installed ZeroNulls method works fine. However if you want to use your own platform-tools you will need to modify the scripts first.(Just change the path for adb. Otherwise it will try to look for adb in the scripts working directory instead of platform-tools).
Pic of Bootloader warning about unlocking from Acer
PIC HERE
Lock Unlock Icons from same bootloader screen.
PIC HERE
Note: If you miss the window of oportunity running the script or unlock commands the first time. You DON'T need to rerun the whole script. The a200 bootloader is already installed. You just need to fastboot reboot bootloader again from your console, THEN you can use the vol keys and home to unlock the bootloader. BUT do what ever you feel safest doing and just pay attention and be careful. (Here I'm referring to the waiting too long after the script boots recovery into unlock mode. If you wait too long it times out and you can't choose unlock until you fastboot reboot bootloader again.)
RECOVERY
(make sure you have installed the a200/unlocked bootloader first. You will see a message at the top of the screen that says (UNLOCK MODE) when bootloader is showing it's message at boot.)
Here is the message I'm referring to PIC HERE
NOTE: When installing a Custom Recovery at some point you have to rename /etc/install-recovery.sh or remove it. I would recomend you rename it to install-recovery.sh.bak. You should do this before doing "adb reboot bootloader" otherwise when you try to reboot into recovery from ROM manager you will get a dead android because cwm will be overwriten with the old recovery(and you don't want that). If you DO get a dead android carefully read the directions again. Q. Why didn't I put this in a step? A. Because I dont want people to brick a device so I want to make sure they are paying attention before I tell them to rename a file that will keep the system from fixing recovery if they mess up.
Using Acer Recovery Installer 2.99 Beta(NOT MARKET VERSION)
=======================================
Download .apk enable non-market installers. Run installer, enjoy.
The Acer Recovery Installer 2.99 Beta is found HERE
Using ADB/Fastboot to flash CWM
============================
Use the steps found HERE(obviously don't re-root, unlock, just follow the other parts.
Or you can also use A100 TWRP recovery v2.1.0+ I have not tried it yet. It looks nice, has touch screen functionality, I think it uses a different backup format or something though. I'm not sure and have not had time to read up on it yet.
NOTE: Read my note above about /etc/install-recovery.sh
FLASH FROM CWM
==============
If you used ADB/Fastboot method you will need a way to reboot into CWM. ROM manager or bootloader reboot thingie will work for this.
If you installed Acer Recovery Image you can use it the app to boot into CWM.
CWM 5.5.0.4 uses the Volume Up/Down Toggle to navigate the menu and a short click of the power button to select things. Be careful about what you choose to do in CWM.
MAKE A BACKUP!!
===============
If you have just installed a custom recovery NOW would be a GOOD time to make a backup with CWM.
To Install a Custom ROM
===============
(BE CAREFUL. MAKE SURE The ROM you choose to install DOESN'T have a bootloader.blob and/or /recovery folder inside. Otherwise it could overwrite your CWM)
Just put the .zip file on an SD card and put it into the device. Use ROM Manager or Acer Recovery Installer
More to come, and I will add some pics showing what various screen look like when I'm able.
"I suggest you install superuser.apk and busybox installer after rooting. Superuser.apk will provide access control for superuser and busybox installer will allow you to update busybox. I also recomend installing terminal emulator(don't forget to configure it to use /system/xbin/sh after you install busybox)."
So ZeroNull says to not update busybox ...you say to update it...is there really a problem if you update it??
cheeb said:
"I suggest you install superuser.apk and busybox installer after rooting. Superuser.apk will provide access control for superuser and busybox installer will allow you to update busybox. I also recomend installing terminal emulator(don't forget to configure it to use /system/xbin/sh after you install busybox)."
So ZeroNull says to not update busybox ...you say to update it...is there really a problem if you update it??
Click to expand...
Click to collapse
i +1 the question what will break if i update busy box?
cheeb said:
"I suggest you install superuser.apk and busybox installer after rooting. Superuser.apk will provide access control for superuser and busybox installer will allow you to update busybox. I also recomend installing terminal emulator(don't forget to configure it to use /system/xbin/sh after you install busybox)."
So ZeroNull says to not update busybox ...you say to update it...is there really a problem if you update it??
Click to expand...
Click to collapse
I don't know if this helps or makes things worst, but I have updated busybox after using Zeronull's root script on pretty much every ICS leak, CM9, and Flexreaper without any issues at all. I always read that warning, but ignored it because I need a more complete busybox version for certain tasks I run on my tablet.
NoSudo said:
A Work in progress.
Using ADB/Fastboot to flash CWM
============================
Use the steps found HERE(obviously don't re-root, unlock, just follow the other parts.
Click to expand...
Click to collapse
Just a little tip. Actually same thread post#28 uses very simple method thanks to mapaz04 to flash the recovery.
Great job though!
I did almost the same in my native language.
cheeb said:
"I suggest you install superuser.apk and busybox installer after rooting. Superuser.apk will provide access control for superuser and busybox installer will allow you to update busybox. I also recomend installing terminal emulator(don't forget to configure it to use /system/xbin/sh after you install busybox)."
So ZeroNull says to not update busybox ...you say to update it...is there really a problem if you update it??
Click to expand...
Click to collapse
I have not used ZeroNulls root method. So I am not sure why he says that. I think his script MAY just use the su and busybox in place in /data/local/ or something(not sure havnt D/L the package to figure it out). You CAN setup su and busybox in the correct locations WITHOUT an issue in ICS.
I use the "hard" method which is very simple. I KNOW you can remove the /data/local/tools copy afterwords doing it by hand.
An Explanation:
The reason you have to push su, mempodroid, busybox, and a mount script to /data/local/ is because you can get write access to it WITHOUT su. Then you run mempodroid which does a little magic and tricks system into thinking a shell was started by root. This drops you into the # prompt(temp). Then you mount /system(still using the files from /data/local). Then you copy the files to the correct path inside /system. Once you chmod su and run it you get root becase su is a special kind of executable. It's what is called an SUID application. As long as the permissions are correct to allow you read/exec access to both su and busybox. You no longer need /data/local/tools. At this point you CAN update busybox and su if you like.
P.S. You can also use your OLD su and busybox for the whole thing. I saved my old su and busybox and always just reuse them then update.
If you want to understand more I would suggest reading up on what SUID is all about and also learn about Unix file permissions.
I can confirm that: rooting,bootloader unlock and change on the recovery can be made with OTA update.
Nice work!
gertjanad said:
Nice work!
Click to expand...
Click to collapse
Thanks, and a bump to keep the info around the first page.
Added to bump it back up so people can find it.
Is there a kernel that allows overclocking yet
Sent from my A100 using XDA
I have not played with OCing, I honestly don't see a need.
I know cwm 5.5.0.x has an Overclock menu so I'm guessing yes you can. But I am not familiar enough with the device/cpu to know how the multipliers etc are to be configured, nor do I experience lag or performance issues that would cause me to desire lowering battery efficiency and increase heat for faster performance.
Though I am familiar with the process on PCs both jumpered and jumperless.
Up!
I rooted my kindle fire using kindle fire utility 0.9.6 (after the rooting superuser wasn't installed on my kindle), downloaded twrp, flashed hashcode jelly bean ROM from this link
http://forum.xda-developers.com/showthread.php?t=1766829
and then flashed Superuser-3.1.3-x86-signed.zip which I downloaded from this link
http://androidsu.com/superuser/
but superuser won't work, when I check the root explorer in ES file explorer it tells me that this feature can't work on ur phone
Please I'm really dying out here
Someone Help Pleeeeeeeeeeeeeeeeeease !!!!!
You need the su binary installed as well. But with that being said, why don't you just install the Superuser.apk?
[Edit:] It's late and I'm not paying attention for some reason. Custom ROMs come pre-rooted and you have Jelly Bean installed. Perhaps there's a problem with ES File Explorer?
soupmagnet said:
You need the su binary installed as well. But with that being said, why don't you just install the Superuser.apk?
Click to expand...
Click to collapse
Thank you for replying so fast
how can I install su binary? and about the superuser.apk isn't that what i flashed into my device i have a superuser icon on my desktop but it just won't add any apps to its list.
Thanks again
At the Superuser website, there are three zip files. One is Superuser, one is the su binary, and the other should be both. Not that it matters at this point.
soupmagnet said:
At the Superuser website, there are three zip files. One is Superuser, one is the su binary, and the other should be both. Not that it matters at this point.
Click to expand...
Click to collapse
what do you mean by not that it matters at this point?
can't I just download the zip and flash it?
soupmagnet said:
You need the su binary installed as well. But with that being said, why don't you just install the Superuser.apk?
[Edit:] It's late and I'm not paying attention for some reason. Custom ROMs come pre-rooted and you have Jelly Bean installed. Perhaps there's a problem with ES File Explorer?
Click to expand...
Click to collapse
Maybe you missed this
soupmagnet said:
Maybe you missed this
Click to expand...
Click to collapse
I tried another app called copy paste it and when I try to use it this message appears:
"Your Phone does not appear to be rooted or has not been given root privileges. to use this application please provide root privileges to this applications"
what should I do?
[Edit] ok now i know my device is certainly not rooted i tried orbot, market enabler and market unlocker they all dispatch the same message your device isn't rooted.
can anyone tell me how to root it?
Scarfacew said:
I tried another app called copy paste it and when I try to use it this message appears:
"Your Phone does not appear to be rooted or has not been given root privileges. to use this application please provide root privileges to this applications"
what should I do?
[Edit] ok now i know my device is certainly not rooted i tried orbot, market enabler and market unlocker they all dispatch the same message your device isn't rooted.
can anyone tell me how to root it?
Click to expand...
Click to collapse
I too used the KFU to supposedly root my KF, but when I tried to install Titanium Backup, it gave me the same error message saying that my phone did not have root privileges... I wonder if there is something not installing correctly when using KFU...
"Root" consists of the su binary, which the system uses to give the user root permissions, and Superuser.apk, which keeps a database of what programs you allow to have those permissions. With "su" only, you will still have root permission, but only at the level of command line interface and your apps will not be allowed root permissions. Superuser.apk by itself is worthless. Custom ROMS come pre-rooted so the need to re-root is usually unnecessary unless something happens to one of the above mentioned programs. The only way to be sure if/which one is missing is in recovery via the command line because custom recovery will provide temporary root access.
Code:
adb shell ls /system/xbin
...look for su
Code:
adb shell ls /system/app
...look for Superuser.apk
Superuser can be installed from within the ROM using the .apk (at least in earlier versions it was possible), or in recovery using the command line or by flashing the signed .zip from the superuser website . The su binary can only be installed while in recovery.
Of course it all can be fixed by re-flashing your custom ROM.
It may also be necessary to rename the check-rooted executable, but only if you're running the stock Amazon software.
I think that pretty much covers it.
soupmagnet said:
"Root" consists of the su binary, which the system uses to give the user root permissions, and Superuser.apk, which keeps a database of what programs you allow to have those permissions. With "su" only, you will still have root permission, but only at the level of command line interface and your apps will not be allowed root permissions. Superuser.apk by itself is worthless. Custom ROMS come pre-rooted so the need to re-root is usually unnecessary unless something happens to one of the above mentioned programs. The only way to be sure if/which one is missing is in recovery via the command line because custom recovery will provide temporary root access.
Code:
adb shell ls /system/xbin
...look for su
Code:
adb shell ls /system/app
...look for Superuser.apk
Superuser can be installed from within the ROM using the .apk (at least in earlier versions it was possible), or in recovery using the command line or by flashing the signed .zip from the superuser website . The su binary can only be installed while in recovery.
Of course it all can be fixed by re-flashing your custom ROM.
It may also be necessary to rename the check-rooted executable, but only if you're running the stock Amazon software.
I think that pretty much covers it.
Click to expand...
Click to collapse
Ok now things are getting worse I tried to turn the wifi on and it didn't work, I tried to reboot and power off the tablet but it just won't work
{Edit} I want to know that by re-flashing the ROM is there a guarantee that those problems won't happen again.
One more thing is that I deleted the ROM from my kindle I can't transfer it from my laptop because the kindle hasn't been recognized after the jelly bean and I can't downloaded because wifi isn't working so what should I do
Thanks in advance
Scarfacew said:
Ok now things are getting worse I tried to turn the wifi on and it didn't work, I tried to reboot and power off the tablet but it just won't work
I want to know that by re-flashing the ROM is there a guarantee that those problems won't happen again.
Thanks in advance
Click to expand...
Click to collapse
There are never any guarantees when it comes to computers and system software, but the LIKELINESS is very high that the problem will be fixed.
soupmagnet said:
There are never any guarantees when it comes to computers and system software, but the LIKELINESS is very high that the problem will be fixed.
Click to expand...
Click to collapse
One more thing is that I deleted the ROM from my kindle I can't transfer it from my laptop because the kindle hasn't been recognized since I flashed the jelly bean and I can't downloaded because wifi isn't working so what should I do
Thanks in advance
Boot into recovery and "mount" your sdcard to USB. The computer should still recognize it.
soupmagnet said:
Boot into recovery and "mount" your sdcard to USB. The computer should still recognize it.
Click to expand...
Click to collapse
I re-flashed the Rom, wifi is working so I dl ES file explorer and checked Root explorer, but when superuser request popped, I clicked allow but it didn't work it gave me the same message, the new thing is that superuser app added es file explorer to its list but I still can't copy apps in the app/system file.
I know I bored you to death and I'm really thankful for ur help but I really need the root.
Scarfacew said:
I re-flashed the Rom, wifi is working so I dl ES file explorer and checked Root explorer, but when superuser request popped, I clicked allow but it didn't work it gave me the same message, the new thing is that superuser app added es file explorer to its list but I still can't copy apps in the app/system file.
I know I bored you to death and I'm really thankful for ur help but I really need the root.
Click to expand...
Click to collapse
Ok, well try a different ROM. If the problem persists then we can try to think of something.
I flashed the Alien droid ROM it's working fine till now but I need to know how to install an arabic keyboard please
Thanks
Ok, I have a dumb question, but from where do you run the DOS commands from? (ie. what directory?)..
c:\KFU?
Right-click on your KFU folder and select properties to find the folder's path. It may be different depending on wherever you've installed it.
soupmagnet said:
Right-click on your KFU folder and select properties to find the folder's path. It may be different depending on wherever you've installed it.
Click to expand...
Click to collapse
Thanks. but not sure i understand.
Here is what I'm attempting to do.. using the root method described here: http://forum.xda-developers.com/showthread.php?t=1638452 under "Getting to fastboot mode" there are a series of command line examples that seem to start with adb.... (ex. adb shell chmod 755 /data/local/tmp/fbmode).
Under Rooting the stock software, the first step command line is "adb shell mount system"
my question is from where do I start (directory) so that when I enter these commands they work?
Or are you saying that I need to fun all these from the KFU directory? (or KFU/tools) or some other directory..
I appreciate the help and feedback..
:h my::
Wherever adb is...Right-click on that folder to find it's path so you can "cd" or change directories to it. Alternatively, you can Shift + Right-click on that folder and select something like "Open command window here".
I have been trying for 3 days straight now to modify this phone. So far I have been able to get temp root using king root, and am able to us ADB as su. That's as far as I've gotten. Neither CWM nor TWRP are compatible with my phone. I was going to attempt to manually port CWM to my phone, but I have no idea how to dump the recovery image. I would really like to install some custom firmware on this thing, but it is seeming to be impossible. How can i pull the recovery image off my phone? I've tried using a dozen apps now to try and backup my recovery image but none are doing what I need.The lack of any information or support online is making me rage hard.Wtf dude. Someone please help me.
Please forgive me for double posting. But I could really use some help dumping the rom. I've tried everything. All the guides I'm finding are 2-3 years old.
try this
stock system.img, boot.img, & recovery.img from someone who has not yet installed TWRP or supersu. To do this, install kingroot 4.5 and terminal emulator and run kingroot to get temp root. Then open terminal emulator and enter the following commands without the ""
"su"
"cd /dev/block/platform/7824900.sdhci/by-name"
"dd if=boot of=/sdcard/boot.img"
"dd if=recovery of=/sdcard/recovery.img"
"dd if=system of=/sdcard/system.img"
You will need to make sure you have at least 3GB of internal storage space before doing this just to be safe. The system.img will probably be about 1.5GB I did this and I got all three files saved to the root of my sd card. it would be easier for you do do this your self I am over my data cap so I cant upload the file
Anyone ever find a working root? I just got this phone a week ago and it is pretty dam good phone for the money. I need root so I can tether.
I also am waiting for root this phone is beast and I want compile a custom kernel for it but with root and a source I can't do jack sqwat.