Related
I followed http://theunlockr.com/2009/08/27/how-to-root-your-htc-hero-in-one-click/ and rooted my phone successfully.
Afterwards i installed the SU and Superuser.apk as suggested on other tutorials, verified it from the computer (shell su) and clicked always allow on the window that popped up on the phone.
But every time i tryed to use the su (for instance with g1teather) i get a black empty window named "SU Request" that wont load.
since i figured i failed with a unknown part of my previous experiments, i threw in modaco´s updated rom image as described here:
http://theunlockr.com/2009/08/27/how-to-load-a-custom-rom-on-your-htc-hero/
And still the SU Request window wont load properly.
This is quite irritating since i cant turn on/off wifi teather or any of the other stuff for witch i rooted my phone (and voided warranty), so i feel a bit pissed off atm..
Can anyone plz help me figure this out?
Try turning on USB Debugging in Settings > Application Settings > Development
I'm pretty sure I remember that helping someone else
i was a bit vauge..
the first time the SU Request window loaded, it loaded fine.
But that was the last time it worked..
will try the usb debug and post feedback in a bit
the usb debug worked like a charm!
on/off tethering works flawlessly now, thanks a bunch for your help!
no problem matey :]
Hey guys,
Im new to Android and after being a BlackBerry user for 8 years, anyway heres my issue.
1. I did the root rom per the instructions...no problem
2. flashed the recovery and have that working...no problem
3. downloaded the .3 rom with the built in busybox and su...Here's where things get confussing for me.
I tried to use adb and it asks me (are you root?), tried adb remount and got (operation not permitted) the usb debug is on and working and the su app on the phone maintains a black screen....(I think this is not right...)
Then I closed out the current cmd window...opened a fresh cmd window and typed>adb shell and got $, then i entered su and got # from here im stuck, what are the commands to get back to adb shell and su also how do I get the whitelist permissions working...
In short adb shell worked fine with the original root rom, I'm sure its an operator error any help is appreciated.
Chris
SO if I understood correctly you already have v3 installed?
If you do check on your phone its probably asking you for permission on the phone when you click on always allow the command should go thru adb.
make sure you have debuggin on otherwise all you will get is a black screen when su permission pops up.
t2noob said:
SO if I understood correctly you already have v3 installed?
If you do check on your phone its probably asking you for permission on the phone when you click on always allow the command should go thru adb.
make sure you have debuggin on otherwise all you will get is a black screen when su permission pops up.
Click to expand...
Click to collapse
can you guys post a walk through for noobies? imstuckat black screen
vash8806 said:
can you guys post a walk through for noobies? imstuckat black screen
Click to expand...
Click to collapse
There are plenty around... seriously google it. But, this specific issue I just experienced. Seems on the custom ROM that is out (EvilEris) the SU request screen doesn't work right off the bat. I went and used an app on the device to request root (terminal) then when the black screen pops up, hit back or home, or action. As the phone is basically frozen at this point it prompted me to forceclose the superuser.apk. I did. Once forceclosed, it worked fine.
adb shell
su
look at phone, click allways all
...
..
.
jcase
jcase said:
adb shell
su
look at phone, click allways all
...
..
.
jcase
Click to expand...
Click to collapse
Or just download Terminal Emulator from Market.
open it up.
Type su.
Hit allow/always allow.
Now try it for other stuff (like wireless tether) and see if it pops up instead of a black screen.
haha..I simply went to settings>Applications>Development and checked the USB debugging mode.... [read it on another thread...should have read before I posted...haha]
vash8806 said:
haha..I simply went to settings>Applications>Development and checked the USB debugging mode.... [read it on another thread...should have read before I posted...haha]
Click to expand...
Click to collapse
niiiice
Does anyone know if this works on HD2 Android:
http://www.android-devs.com/?p=33
I did all the steps and have downloaded the Terminal Emulater from the market, but when i type SU in it nothing happenes,Im trying to install Armenian Language pack on it.
BTW Im using Mdeejay Froyo Sense v.23 clean #15.
If you type in su, at first it looks exactly like this $ su.
After you hit the enter key, there should be only a hash #.
If there's only a hash, you're now working with root rights.
on the Devs web site its mentioned>(then wait for the superuser screen and press yes)
this phrase is confusing me since no Superuser screen is coming up.
hagba said:
on the Devs web site its mentioned>(then wait for the superuser screen and press yes)
this phrase is confusing me since no Superuser screen is coming up.
Click to expand...
Click to collapse
That is no problem because are phones are already rooted so you don't need any superuser. If your terminal look like I described it, just go on. I'm pretty sure your phone will give out errors if it doesn't work.
ok thanks I will give it a try as soon as get back from the work.
I see just $, No #.
Just try it, no matter what key it shows.
ok I will thanks again
hello !
I'm new here and newbie in general. What is more, I'm french !
My desire z and I would like a root, but the uberroot method, using visionary, stops for me at the temroot step with this message : su permission denied
So i'd like to use the "clean" method ( http://forum.xda-developers.com/showthread.php?t=843014 )
but it's a bit difficult to understand why it doesn't work either !
Aaargh !
This works for just about any phone, give it a try...
http://forum.xda-developers.com/showthread.php?t=803682
Xanaki said:
This works for just about any phone, give it a try...
http://forum.xda-developers.com/showthread.php?t=803682
Click to expand...
Click to collapse
G2 is not one of them
try this
http://forum.xda-developers.com/showthread.php?t=801206
there are like 2 or 3 methods
pretty straight forward.
thanks, let's read that.
The most up-to-date method is in the Wiki - http://forum.xda-developers.com/wik...cess_.28Permanent_Root_.2F_.22Permaroot.22.29
However, you don't have the 1.72 ROM do you ? Because that needs a different procedure, due to HTC closing down some of the previously-exploited security loopholes - http://forum.xda-developers.com/showthread.php?t=905261
I carefully avoided installing the 1.72 !
I'm still "su permission denied" right now, and try to multisearch the website before asking more questions.
Well, it seems like I won't solve this by myself.
Thanks, Steviewevie
I installed sdk and usb drivers on my computer. Now, the question is : why does nothing happen when I use the cmd and write : " adb push su /sdcard/su " ?!!!!
I'm finally root and s-off, thanks to the "bad" visionary method !
What's the risk exactly with visionary ?
antoinoid said:
I installed sdk and usb drivers on my computer. Now, the question is : why does nothing happen when I use the cmd and write : " adb push su /sdcard/su " ?!!!!
Click to expand...
Click to collapse
Were you typing that command from your PC's command prompt ? What error message did you get ? Some people do an "adb shell" first and then run that adb, and that's not right because then you're running it on your phone and you'll get an error.
antoinoid said:
I'm finally root and s-off, thanks to the "bad" visionary method !
What's the risk exactly with visionary ?
Click to expand...
Click to collapse
Well, it seems to have a much higher chance of ending up stuck in a boot loop compared to other methods. But if you are back up and working again then it was obviously fine for you !
Visionary and Z4root ...or any root app is harmless. S-off is when you may find a few thin ice moments.... but that's what backups are for. Rom manager or titanum backup work just fine for me.
G2 CM6.1.1 (free)
ok. if I understand, as I'm alive, let's rock then !
so how did you get past permission denied?
damn, i am stuck at the permission denied phase in terminal emulator after typing su then hitting enter.
its seems like the person above figure it out and posted back to say they figured it out, but neglected to give any insight as to how they resolved the issue, save for:
"I'm finally root and s-off, thanks to the "bad" visionary method !
What's the risk exactly with visionary ?"
so anybody can help please?
i don't know what is meant by the "bad" visionary method. i'm pretty sure i used visionary r14 and the instructions found at:
the unlockr site for the how to get permanent root issue
i did seem to have s-off indicated when i held down the volume down button and the start button. i am never quite sure how to restart the phone when i get to that point, i think i just held the power button down, then an option for restart or shut down or something appeared and i toggled the volume switch down to that and pressed the start button and the phone restarted.
one other thing, when i go back into visionary and attempt to follow the last instructions:
"Open Visionary and Uncheck TempRoot on Boot and click Temproot Now.
12. Then select Attempt Perm Root Now and the phone should reboot.
13. Once the phone reboots, open Terminal Emulator on the phone and type su and hit enter. If you get the # symbol, you have permanent root access and S-OFF, enjoy!"
i don't know where i should leave the "set system r/w after root" item checked (which it is) the subheading for that option reads:
"system partiion will be mounted r/w after root process completes
by the way, I am using a fat32 formatted microsd card that is class 4 or so and 32gb that i got off walmart.com for about 100 bucks.
peace
I am new at this and I try VisonaryPlus and my phone keep hanging when I do temproot and I get permission denied. I try almost all the option I found online including the one user the Terminal Emulator and still cannot root. Can some please help.
Hi everyone.
First, I'm a noob on all this flashing Roms thing, so I'm a bit overwhelmed here. So please feel free to correct me if I'm saying the biggest mistake of all times.
I was setting up a Samsung Galaxy Tab 4 10.1 (SM-T530) for one of my colleagues, and was using Samsung's Device Configuration Tool (DCT) to set up most preferences.
I've played around some settings, and removed access to the "Settings" area, but I mistakenly thought that I still could adjust the profile afterwards, via DCT!
Unfortunately, it seems I've removed access to the Network "stack", so my device is isolated from the world.
When you remove access to "Settings", Samsung's tools immediately disables access to USB, Wifi, Bluetooth, SD card and other ways of connecting.
The device works, but cannot access anything, not even the machine that inserted the Security Policy.
I've tried to wipe data / factory reset on boot, but it says: MDM does not allow factoryReset
So my questions are:
- what should I do next?
- are there ways of bypassing security, to restore access and inject a new profile?
- should I flash a new ROM? (couldn't find a Stock version of it so far).
Thanks in advance to any kind soul that may spend his precious time helping this stupid f*ckup.
Also found this other guy that had the same problem as me, but the thread doesn't reflect the solution.
http://forum.xda-developers.com/galaxy-tab-3/help/reset-t2880721#post61484468
urbgimtam said:
Also found this other guy that had the same problem as me, but the thread doesn't reflect the solution.
http://forum.xda-developers.com/galaxy-tab-3/help/reset-t2880721#post61484468
Click to expand...
Click to collapse
U,
hi, after some attempts at starting settings or anything else from a terminal command line, for example
am start -a android.intent.action.MAIN -n com.android.settings/com.android.settings
Note- the above command still fails when;
am start --user 0 -a android.intent.action.MAIN -n com.android.settings/com.android.settings
not the correct "program", com.android.settings does not exist, but i just wanted to see about the permission issue , so when;
am start --user -2 -a android.intent.action.MAIN -n com.android.settings/com.android.settings
still denied.
i am learning you cannot do so as user, at least this way. You need to be rooted.
You are likely going to need to reflash firmware completely.
Alternately, flash a custom recovery so you can get adb access as root from terminal and try a surgical strike by that route
to undo what you did, after some research of course to figure out what changes you need to undo.
if you get that "fixed" then likely you can overwrite the custom recovery with a stock recovery from an sm-t530 device
If you know anyone who can get the above command corrected and working then that might be the way?
moonbutt74 said:
U,
hi, after some attempts at starting settings or anything else from a terminal command line, for example
am start -a android.intent.action.MAIN -n com.android.settings/com.android.settings
Note- the above command still fails when;
am start --user 0 -a android.intent.action.MAIN -n com.android.settings/com.android.settings
not the correct "program", com.android.settings does not exist, but i just wanted to see about the permission issue , so when;
am start --user -2 -a android.intent.action.MAIN -n com.android.settings/com.android.settings
still denied.
i am learning you cannot do so as user, at least this way. You need to be rooted.
You are likely going to need to reflash firmware completely.
Alternately, flash a custom recovery so you can get adb access as root from terminal and try a surgical strike by that route
to undo what you did, after some research of course to figure out what changes you need to undo.
if you get that "fixed" then likely you can overwrite the custom recovery with a stock recovery from an sm-t530 device
If you know anyone who can get the above command corrected and working then that might be the way?
Click to expand...
Click to collapse
Hi moonbutt74, and thanks for helping.
Just finished trying to flash an official ROM, which downloaded and installed successfully, but the problem still maintains...
I'm learning as I go, here, so I may be saying something wrong.
Shouldn't I just need to wipe the data? After all, this may just be a permissions problem, right?
When I flashed the ROM (using ODIN 3.09), it has options to "re-partition" and "Nand Erase All". Should I try one of these?
Also, when choosing the "apply update from adb", it says: "Now send the package you want to apply to the device with 'adb sideload <filename>'.
I've done the following:
"adb devices" to start adb-server and list the device (successful)
"adb sideload [pathtofile]" (successfull) - file is uploaded.
Device then says "E: footer is wrong" and "E: signature verification failed".
So no go.
Also, I just realized I don't have access to adb, as it says "error: closed" if you do any operation except "adb sideload".
So now, to root, what must I do? Flash a rooted ROM?
I do have other identical devices - is there a way to take an image from one of them and upload to the "bad" one?
Kind regards again, thanks for helping out.
Hi,
DO NOT play with Odin, no repartition or anything similar,
At this point you need to flash a custom recovery and root the tab, and/or find out what this samsung tool did and where,
Rule Number 1- never take on a job like that for someone else
So if the tab owner gives the go ahead, flash a custom recovery and root
Then;
first while in regular operation, plug tab into pc and try this in terminal ON TAB,
you must su first, su -c does not do it
su
echo 1 > /data/property/persist.service.adb.enable
now if you get the device pickup notification on pc, get terminal on pc open and run
adb shell
if that goes through run
mount
if all partitions are mounted then you should be good to go as far as access.
From there you will need to find out where this configuration software set and wrote what it did and undo it or correct it.
Try one of these recoveries https://www.androidfilehost.com/?w=files&flid=23537
for sm-t530nu recovery build rename from
sm-t530nu-Philz-6_58_9-final-recovery.tar.md5
to
sm-t530nu-Philz-6_58_9-final-recovery.tar
When you flash the recovery UNCHECK auto restart function in Odin, when flash is complete [res-ok]
unplug tab and manually reboot to RECOVERY --- Home Vol+ Power
if you don't the rom wil rewrite stock recovery and you will have to do it again
m