Related
Greetings,
I am looking for an easy to understand method of root.
I have read the new user thread. I am afraid with this so called "easy" method for beginners, there is a lot of jargon used that I simply don't understand.
For example in the thread for easy root, I am lost at step #2 where I am instructed to:
"Note that adb is required.
Push misc.img, busybox, and psnueter using the following commands:"
I don't know what adb is let alone how to push misc.img, busybox and psnueter.
Can someone please point me to the instructions for absolute morons to this process like me.
Thanks in advance.
priapos said:
Greetings,
I am looking for an easy to understand method of root.
I have read the new user thread. I am afraid with this so called "easy" method for beginners, there is a lot of jargon used that I simply don't understand.
For example in the thread for easy root, I am lost at step #2 where I am instructed to:
"Note that adb is required.
Push misc.img, busybox, and psnueter using the following commands:"
I don't know what adb is let alone how to push misc.img, busybox and psnueter.
Can someone please point me to the instructions for absolute morons to this process like me.
Thanks in advance.
Click to expand...
Click to collapse
Android adb http://developer.android.com/guide/developing/tools/adb.html
which is in the sdk http://developer.android.com/sdk/index.html
You dont really need to know what the other tools are listed do, you just need to do what it says with them and the tools are linked in the thread you're reading to download I assume. If they aren't, then read through the manual method that is stickied in the developer's forum. A link for the tools (misc.img, busybox, and psnueter) can be found there.
I was a little nervous at first myself. I read over the directions several times and then found some information on how to get adb installed and working. Once I got that step understood the actual rooting process was super easy. You can cut and paste all the commands to ensure you don't typo. Just make sure to validate your checksums to save any potential headaches. My first attempt at it took about 20 minutes and I had absolutely ZERO issues.
It is well worth your time and effort. It is also far better to use this method than the easy root 1 steps as you will gain a slightly better understanding of how your phone works and what steps you can take when you inevitably mess something up flashing ROMS, mods and radios
Thanks for the quick reply.
I am not nervous, I just don't understand what any of this is.
I don't know what adb is or how to use it.
I don't know what copy and pasting the commands means.
I certainly don't know what "validate checksums" are.
I realize I am coming across as a comlete shmo, but explaining how to do this with more computer jargon doesn't clarify the process.
I really need instructions for dooshbags like me.
Thanks in advance.
There are also videos on YouTube showing JCases method and adb setup. I would link but I'm on my phone but it shouldn't be to hard to find.
Sent from my ADR6400L using XDA App
priapos said:
Thanks for the quick reply.
I am not nervous, I just don't understand what any of this is.
I don't know what adb is or how to use it.
I don't know what copy and pasting the commands means.
I certainly don't know what "validate checksums" are.
I realize I am coming across as a comlete shmo, but explaining how to do this with more computer jargon doesn't clarify the process.
I really need instructions for dooshbags like me.
Thanks in advance.
Click to expand...
Click to collapse
reading through this might help http://forum.xda-developers.com/showthread.php?t=1143188
There is no "easy", reliable way to root sans ADB and command lines. You will need to know this stuff before you try to root. You're going to need ADB in any event. If learning it isn't knowledge you desire, you shouldn't root your phone. For terms, you should refer to the dictionary stickied at the top of the forum. The best way to learn is to get the Android SDK, set it up, make sure your drivers are there, then play with ADB. Do simply stuff like check your serial number, the md5 of files on your SDcard, and harmless stuff like that. If you've got any questions along the way, feel free to PM me any time. I'm here often. And I'm usually faster than hunting through forums or the internet.
priapos said:
Greetings,
I am looking for an easy to understand method of root.
I have read the new user thread. I am afraid with this so called "easy" method for beginners, there is a lot of jargon used that I simply don't understand.
For example in the thread for easy root, I am lost at step #2 where I am instructed to:
"Note that adb is required.
Push misc.img, busybox, and psnueter using the following commands:"
I don't know what adb is let alone how to push misc.img, busybox and psnueter.
Can someone please point me to the instructions for absolute morons to this process like me.
Thanks in advance.
Click to expand...
Click to collapse
From what i think if u dont want the adb command line ****s you should try the software named "z4root". It automatically roots your phone.
Worked for me. And i think itz the easiest method available.
After installing the apk.
Open the application, click PERMANENT ROOT,
Then dnt let your phone sleep or lock itself, wait for about 10 minutes,
After the process reboot ypur phone.
Voila, you are rooted ..
Am new to the forums. please guide me..
Thanks and sorry for my poor english. Hope you like this.
Cheers!
__________________________________________________________
MODEL : LG Optimus GT540 (Rooted)
MOD : SwiftDroid v2.0 M6 (Based on CyanogenMod v7.1 RC0)
KERNEL : 2.6.29 (VirtualBox #309)
BUILD : GRJ22
RECOVERY : ClockworkMod Recovery v4.0
___________________________________________________________
BusyBox v1.19
SuperUser v2.3
SetCPU v2.2
I would not recommend "easy" root methods, since there is greater room for error. Understanding ADB will help you in the long run
MeAt.HoOk said:
From what i think if u dont want the adb command line ****s you should try the software named "z4root". It automatically roots your phone.
Worked for me. And i think itz the easiest method available.
After installing the apk.
Open the application, click PERMANENT ROOT,
Then dnt let your phone sleep or lock itself, wait for about 10 minutes,
After the process reboot ypur phone.
Voila, you are rooted ..
Am new to the forums. please guide me..
Thanks and sorry for my poor english. Hope you like this.
Cheers!
__________________________________________________________
MODEL : LG Optimus GT540 (Rooted)
MOD : SwiftDroid v2.0 M6 (Based on CyanogenMod v7.1 RC0)
KERNEL : 2.6.29 (VirtualBox #309)
BUILD : GRJ22
RECOVERY : ClockworkMod Recovery v4.0
___________________________________________________________
BusyBox v1.19
SuperUser v2.3
SetCPU v2.2
Click to expand...
Click to collapse
Don't think z4root works on the Thunderbolt just search youtube for Thunderbolt root and watch the tutorials. Links are provided for everything that needs to be downloaded.
Sent from my ADR6400L using XDA Premium App
I know z4root doesn't work for any modern HTC. You can have permanent root without s-off. The only way to do that is through ADB, using an engineering hboot, and applying various exploits. All the "easy" root methods are just scripts that do what jcase's guide lays out. And unlike the guide, if something goes south, you're lost and screwed. I think it would be safe to say "easy" roots have probably bricked more phones than anything else.
loonatik78 said:
I know z4root doesn't work for any modern HTC. You can have permanent root without s-off. The only way to do that is through ADB, using an engineering hboot, and applying various exploits. All the "easy" root methods are just scripts that do what jcase's guide lays out. And unlike the guide, if something goes south, you're lost and screwed. I think it would be safe to say "easy" roots have probably bricked more phones than anything else.
Click to expand...
Click to collapse
Is that u dbzfanatic? Looks awfully similar, lol.
Sent from my ADR6400L using XDA Premium App
nerogold said:
Is that u dbzfanatic? Looks awfully similar, lol.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
Nope. Just a pieced up, inked up, "I been everywhere, man", freak of many talents and interests. Android phones are just one of them.
loonatik78 said:
Nope. Just a pieced up, inked up, "I been everywhere, man", freak of many talents and interests. Android phones are just one of them.
Click to expand...
Click to collapse
Sorry man I just wanted to say thanks to the other user I mentioned ,his method of rooting was and still is a great help to me already rooted 5 bolts and currently on #6 as I'm typing.
Sent from my ADR6400L using XDA Premium App
Do a google search for thunderbolt auto root. There is one posted in the Thuderbolt forums. I can't link directly to it because I don't have enough posts yet. I tested it on my wife's thunderbolt without a problem.
Greywolf66 said:
Do a google search for thunderbolt auto root. There is one posted in the Thuderbolt forums. I can't link directly to it because I don't have enough posts yet. I tested it on my wife's thunderbolt without a problem.
Click to expand...
Click to collapse
Yep, and the past guy to go that route, after being warned it was highly prone to failure, had it fail. Then he came back looking for help, but nobody could because what went wrong wasn't at all clear. Just not wise.
Ive used the one click root four times with no issues. Four diffrent tb's from 3 diffrent states. 2 of them had alrdy takin the ota's. Dont have the link handy but if was a time saver. Though a half arse understanding of the method helps avoid issues. Ill post the link when i get home.
Sent from my ADR6400L using XDA Premium App
loonatik78 said:
Yep, and the past guy to go that route, after being warned it was highly prone to failure, had it fail. Then he came back looking for help, but nobody could because what went wrong wasn't at all clear. Just not wise.
Click to expand...
Click to collapse
I rooted mine manually first. As you said in a previous post most "easy" roots are just scripts. That's what the one I used on my wife's was. I was following along the text of the batch file as I was running it so that if something happened I would know at what part of the script I was at. I had no problems with it though.
I'll agree that I could see where if someone where to run into a problem using script without any knowledge of what the script was doing they would probably end in a very bad place.
I think the obvious was missed in this thread: The OP is not a candidate for rooting. It's a risky task for experienced users and a non-task for noobs. He hasn't even stated a valid need for rooting the phone.
TabGuy said:
I think the obvious was missed in this thread: The OP is not a candidate for rooting. It's a risky task for experienced users and a non-task for noobs. He hasn't even stated a valid need for rooting the phone.
Click to expand...
Click to collapse
Come on, cut him some slack. Everyone was new once. He has already been warned.
Sent from my ADR6400L using XDA App
priapos said:
Thanks for the quick reply.
I am not nervous, I just don't understand what any of this is.
I don't know what adb is or how to use it.
I don't know what copy and pasting the commands means.
I certainly don't know what "validate checksums" are.
I realize I am coming across as a comlete shmo, but explaining how to do this with more computer jargon doesn't clarify the process.
I really need instructions for dooshbags like me.
Thanks in advance.
Click to expand...
Click to collapse
ADB "Android Development Bridge" Simply put just helps you develop apps and fix bugs. (In this case, you will use this to reinstall Android without a locked bootloader (a.k.a. S-Off) (the bootloader is code that is run when you first turn on your device that tells Android to run).
You don't have to know how to use ADB, but you must install it on your computer.
As far as copying and pasting commands go, the tutorial that you choose to visit will tell you to type this command ex: cp image.zip/sdcard/
You will just copy this code out of your browser (FireFox/Internet Explorer/Chrome/etc.) and paste it into a command line.
Your command line will depend on what operating system you use on your pc. Ex for Windows, you will use "Command Prompt" or on Linux/MAC you will use "Terminal".
As far as validation checksums goes, it is used to make sure that the file that you downloaded is 100% the same file that the developer made.
Basically, open up your command line and type (without quotes) "md5 image.zip" also, make sure you change to "image.zip" with whatever/where you file is at.
I would be more specific with these instructions I'd I knew what OS (operating system) you are using on your computer is.
After you type in the command and hit enter, it will spit out a long string of gibberish. Just make sure this "checksum" is the EXACT same as whatever the devolver put in the tutorial you are following.
As far as putting together an idiot proof guide, you will have to forgive us, but I don't think the people here want to have a bunch of people here flooding the forums with very basic questions that have been answered already on the internet. However, don't let that stop you from asking questions. Just make sure you help yourself first (Google what you don't understand) and then ask for clarification.
P.S. I claim touchscreen amnesty for any typos.
Sent from my ADR6400L using XDA App
Currently i am looking for information regarding debloating a rom through either adb, terminal, modifying the odin file, signed CWM zip,or any other way if possible. I saw a thread somewhere that gave info on doing this throughh adb.
if anyone has any links threads or any where i can start from please post it in here or if any developers or modders know please share. Many thanks in advance for anyone who can help.
codelinx said:
Currently i am looking for information regarding debloating a rom through either adb, terminal, modifying the odin file, signed CWM zip,or any other way if possible. I saw a thread somewhere that gave info on doing this throughh adb.
if anyone has any links threads or any where i can start from please post it in here or if any developers or modders know please share. Many thanks in advance for anyone who can help.
Click to expand...
Click to collapse
If I'm not mistaken (I'm not an expert with ADB) you can use the commands to 'pull' an .apk out just like you would 'push' or install one. Aside from that you can use Titanium Backup to freeze and hide apps you don't want, or use Root Explorer to manually delete/rename system apps. I wouldn't use the option to tamper with an Odin or CWM package unless you really know what you're doing. And of course you would need to know what can be removed safely and what can't, there is a thread somewhere with this info I will look for it...
okay thanks alot i was looking and i couldnt find it because i remember some of the commands for
su
*some command*
rm /system/app/*filename*.apk
*another command*
*another command*
then thats it i think, but i do not want to tamper without some homework being done. i prob wouldnt mess with a odin or cwm package unless someone could give me a start point to get more info. i know a magician wouldnt share their secrets so i am sure the rom developers wouldnt really either ^^
I used Root Explorer from the market, and delete those apks not needed.
Yea I know how to do that, which isn't hard, but I read somewhere and there are commands to remove and I'd rather use the command lines because it also takes about removing something else somewhere....like "symlink" or something to that effect
4G LTE TAPATALKED
Among our TF700 Forums/Fora, there have been some people with issues involving the acquisition of the legendary root. It seems that though it is simple to get under typical circumstances, it is possible to encounter atypical difficulty for whatever the reason. I will try to gather information from the problems people have encountered and post possible solutions. Let it be known that I, myself, have not personally encountered these issues nor am I a Master Rooter of the Transformer series. I merely want to collect and present possible solutions so that those with problems will have an easier time of finding things to try and get their Infinity properly rooted.
If you have questions regarding why DebugFS isn't working, I propose you consult the main thread here. If none of these methods work, please start your own thread involving the things you have tried and the issues you are encountering as it will be easier for those much more intelligent than I to assist you with your problems.
Notes:
You do not need an unlocked bootloader to get root access.
Rooting the TF700 does not void your warranty - unlocking the bootloader does. (e.g. Not the same thing)
All commands will be listed in "double quotes" - the quotes should not be typed.
Make sure to always use the most up-to-date version of sparkm3's DebugFS script.
I will be updating this thread as I come across more problems / solutions.
DebugFS doesn't complete:
Make sure that ASUS Sync is disabled in Settings -> Accounts & Sync
Make sure Unknown Sources is enabled under Settings -> Security (under Device Administration)
Make sure USB Debugging is enabled under Settings -> Developer Options
Make sure you have installed the drivers (you can download the drivers from sparkym3's OP)
-It should show up in Windows Device Manager as an adb composite device
Make sure your computer can see the device (use adb from within the DebugFS package and type in "adb devices" - a list should show up with your device in the list)
Make sure that ASUS Sync is uninstalled from your PC
Try a different computer
When DebugFS does complete, you should be able to open up Terminal Emulator, type in "su" and your prompt should turn from "$" to "#". Alternatively, you should be able to do the same thing via adb ("adb shell" then "su").
DebugFS does complete but still can't get root:
Try to run the SuperUser application
Try to uninstall and reinstall SuperUser
Try to run the SuperUser Update Fixer (thanks to okantomi)
If all else fails, you can give this a try. (thanks to d14b0ll0s)
Hopefully, this list will eventually help someone.
Thanks for this, well done (I'm going to add a link to this in my tweaks how-to if that's ok).
I believe you could add this one to the list.
Just received my champagne today fully updated .26, got root, busybox, and titanium back up with no problems... New to all this but had no problems getting rooted. Love the infinity (C7) so far GPS works,no light bleeds, good wifi, pretty smooth, hopefully the future updates wont screw my tablet and unlike the 4 primes I had when when it first came out defect after defect. Looks like this one maybe a keeper.
d14b0ll0s said:
Thanks for this, well done (I'm going to add a link to this in my tweaks how-to if that's ok).
I believe you could add this one to the list.
Click to expand...
Click to collapse
You can link to this thread if you believe that it will be helpful for others to read over. Any sort of suggestions of what you think would be easier to follow or details I should provide are welcome.
Also, I read over that post you noted and I have a question about that. The post mentions changing "adb wait-for-device" and suggests that it could be changed to "pause". Reading over the batch file though, it seems that sparky uses both "pause <CON" and "@pause <CON" so it makes me believe that perhaps one of those would be more appropriate. What do you think? or should I be directing this question to sparky?
Edit: I placed a request for the information in the main DebugFS thread.
I believe wait-for-device is more appropriate for a script, while pause is better for manual adb management (just imagine what happens).
d14b0ll0s said:
I believe wait-for-device is more appropriate for a script, while pause is better for manual adb management (just imagine what happens).
Click to expand...
Click to collapse
My question was whether when modifying the batch file if the person should be using "pause" or "pause <CON" as mentioned in burningcf's post
(Copy & Vomited from post)
Alternatively, if you don't feel comfortable with executing the adb actions by hand, you might want to just replace all occurrences of
Code:
adb wait-for-device
with
Code:
pause
(or something like that.)
(/Vomit)
which may be something to try before actually going for a line-by-line manual execution.
Perhaps I should just add a link to the post itself but I'm worried that it might go over some people's heads as to what is going on there. Well, let's see if I can get some more background from sparky and then I'll include what I can.
d14b0ll0s said:
Thanks for this, well done (I'm going to add a link to this in my tweaks how-to if that's ok).
I believe you could add this one to the list.
Click to expand...
Click to collapse
If you would like to update this post you linked to, I update the tool a few days ago to include pauses along with the wait-for-device calls. I removed the pointless lines that got left in there, and I am using a better way to determine su access. Finally, I updated it to kill asus sync if it is running.
The new version that should have all the fixes is v2.2
---------- Post added at 01:36 AM ---------- Previous post was at 01:33 AM ----------
alienedd said:
My question was whether when modifying the batch file if the person should be using "pause" or "pause <CON" as mentioned in burningcf's post
(Copy & Vomited from post)
Alternatively, if you don't feel comfortable with executing the adb actions by hand, you might want to just replace all occurrences of
Code:
adb wait-for-device
with
Code:
pause
(or something like that.)
(/Vomit)
which may be something to try before actually going for a line-by-line manual execution.
Perhaps I should just add a link to the post itself but I'm worried that it might go over some people's heads as to what is going on there. Well, let's see if I can get some more background from sparky and then I'll include what I can.
Click to expand...
Click to collapse
I responded to your post in the other thread, but I will copy it here as well, for easy reading.
There should be no difference between the pause that starts with @ and the one that doesn't (as far as this is concerned), I don't know how both got in there.
The reason that I added <CON to the end was because the script was ignoring the pauses and just continuing anyway (because it already had input stored in the buffer). The <CON just insures that the input is coming from the console (user) instead of some other buffer.
sparkym3 said:
I responded to your post in the other thread, but I will copy it here as well, for easy reading.
There should be no difference between the pause that starts with @ and the one that doesn't (as far as this is concerned), I don't know how both got in there.
The reason that I added <CON to the end was because the script was ignoring the pauses and just continuing anyway (because it already had input stored in the buffer). The <CON just insures that the input is coming from the console (user) instead of some other buffer.
Click to expand...
Click to collapse
Thanks for the explanation in feedback in both threads. Much appreciated it.
Added d14b0ll0s's link to post for "last resort" situations.
alienedd said:
My question was whether when modifying the batch file if the person should be using "pause" or "pause <CON" as mentioned in burningcf's post
Perhaps I should just add a link to the post itself but I'm worried that it might go over some people's heads as to what is going on there. Well, let's see if I can get some more background from sparky and then I'll include what I can.
Click to expand...
Click to collapse
Sorry for reading your post neglectfully, I was sleepy already but I believe sparkym3 responded to it now.
sparkym3 said:
If you would like to update this post you linked to, I update the tool a few days ago to include pauses along with the wait-for-device calls. I removed the pointless lines that got left in there, and I am using a better way to determine su access. Finally, I updated it to kill asus sync if it is running.
The new version that should have all the fixes is v2.2
Click to expand...
Click to collapse
Good job, thanks for this! I will update the rooting part in the tweaks thread.
And I believe there is no reason to add the pause solution here now or just you could mention it's obsolete.
Great post > thanks .... but ......
alienedd said:
Among our TF700 Forums/Fora,.......
If you have questions regarding why DebugFS isn't working, I propose you consult the main thread here. If none of these methods work, please start your own thread involving the things you have tried and the issues you are encountering as it will be easier for those much more intelligent than I to assist you with your problems.
Notes:
You do not need an unlocked bootloader to get root access.
All commands will be listed in "double quotes" - the quotes should not be typed.
Make sure to always use the most up-to-date version of sparkm3's DebugFS script.
I will be updating this thread as I come across more problems / solutions.
DebugFS doesn't complete:
Make sure that ASUS Sync is disabled in Settings -> Accounts & Sync
Make sure Unknown Sources is enabled under Settings -> Security (under Device Administration)
Make sure USB Debugging is enabled under Settings -> Developer Options
Make sure you have installed the drivers (you can download the drivers from sparkym3's OP)
-It should show up in Windows Device Manager as an adb composite device
Make sure your computer can see the device (use adb from within the DebugFS package and type in "adb devices" - a list should show up with your device in the list)
Make sure that ASUS Sync is uninstalled from your PC
Try a different computer
When DebugFS does complete, you should be able to open up Terminal Emulator, type in "su" and your prompt should turn from "$" to "#". Alternatively, you should be able to do the same thing via adb ("adb shell" then "su").
DebugFS does complete but still can't get root:
Try to run the SuperUser application
Try to uninstall and reinstall SuperUser
Try to run the SuperUser Update Fixer (thanks to okantomi)
If all else fails, you can give this a try. (thanks to d14b0ll0s)
Hopefully, this list will eventually help someone.
Click to expand...
Click to collapse
>> sorry if I am missing something >>> pls forgive as am very very NEW TO this " rooting" process
AND am still trying to GET MY TF700 from this crazy 'bay plac e !!!
so my question(s) is...
a) what hardware I need? or Does the transfermer (TF700) come with a USB cable to connect to PC
b) if not ; where can I get one of these ordered > so am ready when i get mine.
c) from what I read @ asus website > doing ROOT and UNLOCKING = voids warranty!! true ??
thanks in advance for answers
Debbie1759 said:
>> sorry if I am missing something >>> pls forgive as am very very NEW TO this " rooting" process
AND am still trying to GET MY TF700 from this crazy 'bay plac e !!!
so my question(s) is...
a) what hardware I need? or Does the transfermer (TF700) come with a USB cable to connect to PC
b) if not ; where can I get one of these ordered > so am ready when i get mine.
c) from what I read @ asus website > doing ROOT and UNLOCKING = voids warranty!! true ??
thanks in advance for answers
Click to expand...
Click to collapse
A) It comes with it
B) no need
C) Rooting does not void warranty but Unlocking will void your warranty.
Sent from my ASUS Transformer Pad TF700T using XDA Premium App
After deleting asus sync, then reisntalling superuser from the market did the trick thanks!
Thanks
jjdevega said:
A) It comes with it
B) no need
C) Rooting does not void warranty but Unlocking will void your warranty.
Sent from my ASUS Transformer Pad TF700T using XDA Premium App
Click to expand...
Click to collapse
Thanks for info..
> looking forward to grabbin this bad boy and ridin him to ROOT ! :angel:
d14b0ll0s said:
Thanks for this, well done (I'm going to add a link to this in my tweaks how-to if that's ok).
I believe you could add this one to the list.
Click to expand...
Click to collapse
having trouble getting rooted and tried your link, everything went fine, it even shows the uid and gid as = 0, but i still dont have root when i boot up and run root checker or superuser to update binaries. starting to look like i might have to go back to stock recovery and do a fresh install of firmware. I have even flashed TWRP through fastboot and installed a rooted rom (Zues v4) and still had no root. Really at a loss for what to do next.
Somehting that might help
alienedd said:
DebugFS does complete but still can't get root:
Try to run the SuperUser application
Try to uninstall and reinstall SuperUser
Try to run the SuperUser Update Fixer (thanks to okantomi)
If all else fails, you can give this a try. (thanks to d14b0ll0s)
Hopefully, this list will eventually help someone.
Click to expand...
Click to collapse
Thanks very much for all your guide, I have always use XDA forums and learn alot about android devices. I want to tell you that yesterday I try to root my TF700 like 10 times and in 3 different computers! I follow all the steps and eveything but I wasn't able to Root it. But in my last try.. I went to setting and in USB Debugging (it was enable) I disable it and enable it again, and then try with the Debug and it finally WORK :laugh:
So well maybe this will help someone that could be in my situation.
Sorry for my bad english.
I give up. I tried DebugFS, and that didn't work completely. Superuser seemed to be working but Busybox installer & TiBu didn't see root. I tried the manual commands in this thread and it's still not working. Screw this. Everyone that posted help threads on rooting & unlocking & etc. has done fabulous work, including this thread. But I'm just destined to live a rootless life.
*I have no interest in installing a custom ROM till JB is pushed out and I know the ROMs are reliable. I don't want to have to deal with so many bugs.
das0527 said:
I give up. I tried DebugFS, and that didn't work completely. Superuser seemed to be working but Busybox installer & TiBu didn't see root. I tried the manual commands in this thread and it's still not working. Screw this. Everyone that posted help threads on rooting & unlocking & etc. has done fabulous work, including this thread. But I'm just destined to live a rootless life.
*I have no interest in installing a custom ROM till JB is pushed out and I know the ROMs are reliable. I don't want to have to deal with so many bugs.
Click to expand...
Click to collapse
I was in the same boat. I finally installed Black Bean rom which is JB based and it gave me root. The development seems to have tripled just in
Sent from my ICS Razr
---------- Post added at 11:36 AM ---------- Previous post was at 11:25 AM ----------
I was in the exact same boat. Installing Baked Black Bean rom gave me root. I understand your concern with JB roms, however, there are only 2 bugs I have experienced-no GPS and portrait mode. Although they sound like big issues they really aren't. Any game or app I use that runs in portrait only mode works fine. Also I have seen 3 to 4 roms drop in the last 2 days. It will not be long until the devs fix all issues. This is a popoular device among Apple haters and I foresee a lot of really good stuff coming for this tablet. Just try out a JB rom and see how you like it...you can always go back. Hope this helps...I was just as frustrated as you.
Sent from my ICS Razr
Will, thank you for the advice. However, until the custom ROMs become more stable - or until JB is pushed out officially - I'm very wary of unlocking & flashing a custom ROM.
das0527 said:
Will, thank you for the advice. However, until the custom ROMs become more stable - or until JB is pushed out officially - I'm very wary of unlocking & flashing a custom ROM.
Click to expand...
Click to collapse
This is how i kind of feel to. My galaxy nexus feeds all my flashing needs.
worked for me
das0527 said:
I give up. I tried DebugFS, and that didn't work completely. Superuser seemed to be working but Busybox installer & TiBu didn't see root. I tried the manual commands in this thread and it's still not working. Screw this. Everyone that posted help threads on rooting & unlocking & etc. has done fabulous work, including this thread. But I'm just destined to live a rootless life.
*I have no interest in installing a custom ROM till JB is pushed out and I know the ROMs are reliable. I don't want to have to deal with so many bugs.
Click to expand...
Click to collapse
>> am still using Virgin TF700..(recovered from FACTORY BACKUP) but did try the ROOT...using the "DebugFS" method..
and it works >>>>> MUST REMEMBER to stop/switch off this apps = ASUS SYNC..... that is something that got me @ first try..
DOH! than I realised .. and once turned off = worked like a charm !!!
just my 0.02c worth !
IF THERE IS A POST ABOUT THIS ALREADY PLEASE DON'T WASTE YOUR TIME AND JUST REDIRECT ME TO THE LINK
As said above, if the link you give me for the steps are hard (I cant do complex stuff, i only understand simple instructions) you can re write the steps here for me to get a better understanding
Okay, i am kind of irritated with the whole 15 levels of volume for Android devices and i wish to increase the range upto 30, 50 is preferred.
I've tried this link HERE
And obviously it didn't work because it is made for a Samsung device which is not mine
So done with the intro (Sorry if I bore you )
I will just tell you what I have and what i need
What I have:
I use an Xperia Mini Pro Sk17i
Running on Cyanogenmod 9.1 (ICS)
Yes it is rooted (No duh)
What I want:
Better range for my volume from 0-15 to 0-30 (50 is appreciated)
At least a frameworkmod.zip
Easy instructions or link to where i can do all this if it has been done
I know if there is a thread about this this will just make me look lazy or something but no, i have been searching around (still am) but i decided to ask so that a kind, charming, knowledgeable person (Trying to attract you ) can step forward and help me
Hope I can get a reply
Additional info can be asked at your request
There must be a specific rom for that..
.........................................................................................................................................................................................................................................
PLS PRESS THE THANKS BUTTON, IT MAKES ME FEEL BETTER.......:good:
Streetryders_2000 said:
There must be a specific rom for that..
.........................................................................................................................................................................................................................................
PLS PRESS THE THANKS BUTTON, IT MAKES ME FEEL BETTER.......:good:
Click to expand...
Click to collapse
I shall if you help me out more
Anywho, im sure you dont need a specific ROM for that
I've seen certain devices just have a framework.jar or framework.zip you need to install which just changes some codes
I found one thread HERE after some extensive searching and that volume fix is for my phone, it is not a Rom. I dont know if it will work with CM9.1 Mango but I am just doing a nandroid backup right now and I am going to try it
No helps?
Come on, im sure someone can help me out
Please?
Naweed Reza said:
I shall if you help me out more
Anywho, im sure you dont need a specific ROM for that
I've seen certain devices just have a framework.jar or framework.zip you need to install which just changes some codes
I found one thread HERE after some extensive searching and that volume fix is for my phone, it is not a Rom. I dont know if it will work with CM9.1 Mango but I am just doing a nandroid backup right now and I am going to try it
Click to expand...
Click to collapse
Okay, Prior to what I have said about trying this Fix from the link i provided.
It doesn't work
I am just stuck in the CM boot screen, I've changed the permissions as mentioned in the Topic
This post is solved thanks to numerous people
THIS POST HAS BEEN SOLVED THANKS TO NUMEROUS PEOPLE
Okay so I managed to get 30 steps of volume ^_^ :victory: (Yes I am jumping for Joy)
So anyways, alot of editing, i will be posting links to where i got help to and.... also make the steps easier incase any newbie (Like me) comes by
So yeah
I would Like to credit Dexter93 from #xda-rc who took his time to help me out
Recognized Contributor Chat Support Link HERE
Go to that link so you can access the link to have a chat with the recognized contributors if you have any doubts, they help alot ^_^
And if you are lucky they should be online most of the time
How I managed to do it
This is just for people who need to change their volume on their Mini Pro or other devices
Things you need :
Java software Development Kit
Download Latest JDK (Just download the Latest JDK, not JRE)
smali/baksmali tool (Thanks to the Korean guy, 'vorcot')
Download here
Have Notepad
Have your Framework.jar file on your desktop
Now sometimes Java might not be recognized in cmd
This will be noticed when you use Backsmali.bat (Happened to me)
You can get such message like: "Java Is Not Recognized As An Internal Or External Command"
So to fix that watch this video
Credits to the guy because I thought i would never fix it
After that
Go HERE
And follow the steps from "A. Basic Steps"
and in one step to change the volume you cant just put 30 or 100, it must be in hexadecimal form
You can use the converter here
Just enter a number on the decimal are which is your regular 1-Infinite numbers and click convert
Hope it helps for people who need it :good:
And Any questions can be asked
When I am free, i will make a full Tutorial for complete newbies
Hi every one
just need to confirm from professional people here , i need to edit build.prop on my A9 device without rooting so that i could make some connection with my car screen (stupid screen accept only Samsung and LG) , Is that possible?
amro ibrahim said:
Hi every one
just need to confirm from professional people here , i need to edit build.prop on my A9 device without rooting so that i could make some connection with my car screen (stupid screen accept only Samsung and LG) , Is that possible?
Click to expand...
Click to collapse
First, this question gets asked A LOT so a simple search here or google will show numerous others asking this and their findings. It doesn't matter if its not specifically referring to HTC A9 or in this specific forum either.
That being said....to answer your question.....NO! ^_^ You will most likely need root to even access the system root folder where your build prop. You may find it using some app possibly that doesn't require root, open it and change values, HOWEVER, you will never be able to save these changes without root, sorry.
If you are knowledgeable on unpacking system images or have firmware.zip/tar etc that you can dig through and find the build prop, edit it on windows/linux/mac repack or rezip and flash it successfully....thats one way.
Another way would be to use ADB to pull what you want and push it back to system afterwards.....but not to sure as my phone(s) usually are rooted and never tried to use ADB unrooted. Somethings tells me that this too won't work but go for it.
mcbright80 said:
First, this question gets asked A LOT so a simple search here or google will show numerous others asking this and their findings. It doesn't matter if its not specifically referring to HTC A9 or in this specific forum either.
That being said....to answer your question.....NO! ^_^ You will most likely need root to even access the system root folder where your build prop. You may find it using some app possibly that doesn't require root, open it and change values, HOWEVER, you will never be able to save these changes without root, sorry.
If you are knowledgeable on unpacking system images or have firmware.zip/tar etc that you can dig through and find the build prop, edit it on windows/linux/mac repack or rezip and flash it successfully....thats one way.
Another way would be to use ADB to pull what you want and push it back to system afterwards.....but not to sure as my phone(s) usually are rooted and never tried to use ADB unrooted. Somethings tells me that this too won't work but go for it.
Click to expand...
Click to collapse
Actually i searched a LOT but i have found the TWO answers "Yes you can" AND "No you can not" , also people says yes you can giving steps i have no idea about it like this one
1. Make a process which executes "getprop" from the "/system/bin/getprop" directory and initialize the String which we want to get (ro.board.platform in example).
2. Make a BufferedReader which gets the value (String) by retrieving the data from a inputStreamReader().
3.Convert the BufferedReader to String.
. That is why i asked here again to get clear answer which i get it and many thanks for you
amro ibrahim said:
Actually i searched a LOT but i have found the TWO answers "Yes you can" AND "No you can not" , also people says yes you can giving steps i have no idea about it like this one
1. Make a process which executes "getprop" from the "/system/bin/getprop" directory and initialize the String which we want to get (ro.board.platform in example).
2. Make a BufferedReader which gets the value (String) by retrieving the data from a inputStreamReader().
3.Convert the BufferedReader to String.
. That is why i asked here again to get clear answer which i get it and many thanks for you
Click to expand...
Click to collapse
LOL i understand the frustration. I also spend a ridiculous amount of time scouring forums and any other place online for the many questions i need help with only to get fractured/incomplete answers or conflicting ones like you stated where it seems like the answer is both yes and no or whatever....its a real pain. Truthfully, I said you wouldn't be able to do this without root due to the level of difficulty of the other options trying without root. Creating bufferedreader etc is all Java Programming. You will need a decent working knowledge of java programming to be able to do what that guide was talking about.....i figured you might not have that so I said that NO to your question here. I know some of what that guide was explaining enough to create some of that they described but still not enough to feel comfy attempting. Your best option, i think, will be to extract the build prop from a stock.img and repack the system.img after editing the build.prop. Use 7zip to unzip/rezip the system.img and notepad++ to open/edit the build.prop and flash image in your recovery. You could also use Android Kitchen if you can. Plenty of tutorials on this. I linked two below for ya though. '
What were you looking to edit in the Build.prop anyhow? I assume you are disinclined to root/unlock bootloader for warranty issues correct?
BTW, sorry for such a late response...I am not always here for days at a time usually so.....
dsixda's Android Kitchen - http://forum.xda-developers.com/showthread.php?t=633246
Super-Rs - http://forum.xda-developers.com/chef-central/android/kitchen-superrs-kitchen-t3202296
mcbright80 said:
LOL i understand the frustration. I also spend a ridiculous amount of time scouring forums and any other place online for the many questions i need help with only to get fractured/incomplete answers or conflicting ones like you stated where it seems like the answer is both yes and no or whatever....its a real pain. Truthfully, I said you wouldn't be able to do this without root due to the level of difficulty of the other options trying without root. Creating bufferedreader etc is all Java Programming. You will need a decent working knowledge of java programming to be able to do what that guide was talking about.....i figured you might not have that so I said that NO to your question here. I know some of what that guide was explaining enough to create some of that they described but still not enough to feel comfy attempting. Your best option, i think, will be to extract the build prop from a stock.img and repack the system.img after editing the build.prop. Use 7zip to unzip/rezip the system.img and notepad++ to open/edit the build.prop and flash image in your recovery. You could also use Android Kitchen if you can. Plenty of tutorials on this. I linked two below for ya though. '
What were you looking to edit in the Build.prop anyhow? I assume you are disinclined to root/unlock bootloader for warranty issues correct?
BTW, sorry for such a late response...I am not always here for days at a time usually so.....
dsixda's Android Kitchen - http://forum.xda-developers.com/showthread.php?t=633246
Super-Rs - http://forum.xda-developers.com/chef-central/android/kitchen-superrs-kitchen-t3202296
Click to expand...
Click to collapse
Thanks again for your replay , actually i still trying to proceed your way .. i think i am too close to do it , but you know after one or two hour of Trying&searching i say to my self let us unlock this phone and finish this matter .. any way i am using the Android Kitchen and i hope i could do it