Database Users

Permission issues with su and rom .3

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

Terminal Emiulater

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

Major problems with downgrading GB ROM

I am trying to downgrade from stock GB 2.3.3 ROM.
My SD card has now disappeared when i tried to put the PD98img.zip file on it.
When i tried to change from USB charging to disk drive there isn't any option anymore for disk drive.
However the SD drive and it's contents is shown in Astro file manager, very strange
I did this as per instructions:
1. Download Gingerbreak, and install it. Then tap root button.
2. You might get force close errors, just click the force close button and let Gingerbreak do it's job
3. Gingerbreak will, in the end, usually say that something went wrong. Just leave it open in your phone, and connect your phone to a PC. Charge only, USB Debugging enabled!
4. Open up a cmd and go to Downgrade folder, execute commands: (after command "su", allow SuperUser in phone)
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/misc_version
adb shell
su
If you got "#" in the result, you have temporary root! Proceed with commands:
Code:
cd /data/local/tmp
./misc_version -s 1.31.405.6
Next step is to put the PD98img.zip file on SD card so i tried to change the USB connection but the option is gone to connect to the SD.
Also when i go to Settings my SD card is not available, the system can not see any SD and i can't mount it either, it's gone.
What should i do now?

put the SD into ur pc, simples

Take out the sd card and reinsert it.
Then put the PD file on the SD card before beginning the process.

I rebooted it now and now i can choose USB disk drive.
What is the cause this was happening in the first place? somehow Gingerbreak did something.

I think it was trying to remove things whilst still mid adb shell.

[EDIT] Said something that wasn't quite right so removed, thanks for the heads up jkoljo.
Sent using witchcraft via XDA Developers Premium App.

That is incorrect, gingerbreak also works without S-OFF, like in the downgrade guide. The difference is, with S-OFF you get permanent root, and without it only temporary, which is enough for downgrading.
Sent from my Desire HD using Tapatalk

jkoljo said:
That is incorrect, gingerbreak also works without S-OFF, like in the downgrade guide. The difference is, with S-OFF you get permanent root, and without it only temporary, which is enough for downgrading.
Click to expand...
Click to collapse
My bad, I must have mis-understood something someone said to me previously.
Sent using witchcraft via XDA Developers Premium App.

Ok everything fine now running latest Lee, thanks.

Anyone had success with telus dhd?
Sent from my Desire HD using Tapatalk

goodrench said:
Anyone had success with telus dhd?
Click to expand...
Click to collapse
What problems are you having trying to downgrade your Telus DHD?
Sent from my Ericsson T39m

goodrench said:
Anyone had success with telus dhd?
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
what, with gingerbread or downgrading.... in my case, both.
gingerbreak will say its attempting, let it go into standby, then go back to using the phone, gingerbreak will say there's an error, reboot the phone..... you're rooted.
If you want to go downgrade, just use the RUU, it overides everything (something that the recovery tool isnt able to do when using the p98img.zip)
Downgrading and rooting with simple steps and no code entry, Made it, and it works for the Telus DHD and Inspire 4G
(Our Telus DHD's are the exact hardware twin of the Inspire 4G; unlike the Euro/Asian DHD's which have different radio controllers)

My trouble is getting su to work. Gingerbreak gets to the error message and when I "adb shell " to the phone it will not accept su. (Permission denied)
What ruu are you referring to? I tried 1.32 and 1.84, and they both fail.
I attempted to use the ruu downloaded from the link in the previous post and it failed saying bootloader version error.
Any thoughts?

success!!!
Had an old version of superuser installed from the telus dhd permanent root files that I previously downloaded. Uninstalled superuser and downloaded from market.
Also had phone unplugged from pc while running gingerbreak. previously left it plugged in through whole procedure.
Hope this helps someone else.

3 phones in 3 days...what are the odds?

Got my MT4G wednesday...couldn't root with visionary
Got it replaced yesterday...couldn't root with visionary
Got it replayed today...can't root with visionary.
3 phones, in 3 days...all cannot root with visionary
Something weird is going on here. The odds of this happening have to be astronomical, or is this phone going to sh*t now?

I also had problems Rooting a friends new MT4G a couple days ago with the VISIONary Method and Thats all I had ever used. I think it's somthing with the new phones? Did you try the G-FREE Method?

No cause Gfree is windows and I have OSX, so I'm SOL on that...which is why I'll probably switch to the G2X if I can't get to another computer with windows.

use cm method

bosina said:
use cm method
Click to expand...
Click to collapse
which is what? Never even heard of that...

You keep replacing your device because you can't root it? Seriously? Why? You think the devices are damaged in some way because you can't root them?

coupetastic-droid said:
You keep replacing your device because you can't root it? Seriously? Why? You think the devices are damaged in some way because you can't root them?
Click to expand...
Click to collapse
So it's my computer's fault?
There is a thread going on about bad eMMC's that won't allow you to root...so yes, it is the device...
way to be a d*ck dude!

I think you're likely incorrect about the reason you can't root it. My myTouch4G has the good eMMC, yet I was unable to root it using Visionary. Gfree worked without a hitch though. Also, why do you think gfree is exclusive to any OS? I think it should work on any OS, as gfree is executed on the phone, not via your PC. You run gfree through terminal emulator or through adb shell.

I've gone through half a dozen mytouch 4gs because they all keep turning off on me. I get the feeling that t-mobile just sends out refurb after refurb so you keep getting phones with the bad chip. At least I wouldn't be surprised considering my experience with this phone.
I also have the M4G2DE chip and I could not root with visionary. I don't know if my sleep of death problems are related to this but like I said before I wouldn't be surprised.

crawler9 said:
I think you're likely incorrect about the reason you can't root it. My myTouch4G has the good eMMC, yet I was unable to root it using Visionary. Gfree worked without a hitch though. Also, why do you think gfree is exclusive to any OS? I think it should work on any OS, as gfree is executed on the phone, not via your PC. You run gfree through terminal emulator or through adb shell.
Click to expand...
Click to collapse
excuse me, according to the thread in the general section, the MT4G can come with bad eMMC's. I have no proof of this of course, just going off what I read. I tend to give people the benefit of the doubt, when I see other's with the same issues at least.
The instructions on the gfree method are for windows...do the same exact commands apply to OSX if I use terminal? I'm not a mac guy, by any means, but I figured commands and all would be different between OS's.

Yes, it's highly suspected that certain eMMcs are more prone to failing, though this hasn't definitively been determined yet.
The instructions in the gfree thread should be universal. I used them successfully on Ubuntu. For some reason, I couldn't get Visionary to properly function on my device either. Apparently it did work after a factory reset, after I restored it to stock again, but first time around, I used z4root to temp root and manually installed the superuser application from the market instead of the step that tells you to use Visionary in the gfree instructions.

crawler9 said:
Yes, it's highly suspected that certain eMMcs are more prone to failing, though this hasn't definitively been determined yet.
The instructions in the gfree thread should be universal. I used them successfully on Ubuntu. For some reason, I couldn't get Visionary to properly function on my device either. Apparently it did work after a factory reset, after I restored it to stock again, but first time around, I used z4root to temp root and manually installed the superuser application from the market instead of the step that tells you to use Visionary in the gfree instructions.
Click to expand...
Click to collapse
but what's the "C" drive called on OSX (as per the instructions)...right now my android-sdk-mac_x64 folder is in the macintosh hd

bballcat03 said:
but what's the "C" drive called on OSX (as per the instructions)...right now my android-sdk-mac_x64 folder is in the macintosh hd
Click to expand...
Click to collapse
I don't see any mention at all of the C drive in the gfree thread. Are you following the same thread I am? http://forum.xda-developers.com/showthread.php?t=858996

crawler9 said:
I don't see any mention at all of the C drive in the gfree thread. Are you following the same thread I am? http://forum.xda-developers.com/showthread.php?t=858996
Click to expand...
Click to collapse
yup same thread, but in order to get to the "tools" portion, you had to do C right? It says I'm supposed to "cd your way to your SDK tools directory"...how do you do that on OSX?
cause when I do step 4 ""adb push gfree /data/local""....I type that into terminal and it says "command not found"

bballcat03 said:
yup same thread, but in order to get to the "tools" portion, you had to do C right? It says I'm supposed to "cd your way to your SDK tools directory"...how do you do that on OSX?
cause when I do step 4 ""adb push gfree /data/local""....I type that into terminal and it says "command not found"
Click to expand...
Click to collapse
Never used MAC OS, but it seems like the cd command would work the same way. Just open terminal or a prompt or whatever you use in MAC and type "ls" and hit enter. That should show you all the files or directories in that folder. Use that to find your way around to where your SDK is located. To go up a folder, you can type "cd .." or to enter another folder located in your current working directory, "cd insertfoldernamehere". Maybe someone with a little more experience with MACs can help you with exactly where your SDK is, but that should help if you can play around with it for a while.

@crawler9 u must have great patients for ignorance... if he can't figure out how to use his comp, goodluck on getting him to understand android... not trying to sound like a **** OP but educate urself a bit more on things u r unsure of..
Sent from my demonSPEED Glacier

thederekjay said:
@crawler9 u must have great patients for ignorance... if he can't figure out how to use his comp, goodluck on getting him to understand android... not trying to sound like a **** OP but educate urself a bit more on things u r unsure of..
Sent from my demonSPEED Glacier
Click to expand...
Click to collapse
thanks @$$.
I had a MT4G before, but I was on windows...I could do everything perfectly fine, never had an issue. Flashed and rooted flawlessly
But I switched to mac, and don't know my way around this full yet. So I'm trying to admittedly re-learn everything as I went a few months without my MT4G before getting it replaced.
Thanks for your input! Next time just keep your mouth shut if you don't have anything constructive to add, hmmm?

bballcat03 said:
which is what? Never even heard of that...
Click to expand...
Click to collapse
http://wiki.cyanogenmod.com/index.php?title=TMobile_myTouch_4G:_Full_Update_Guide
that is cm method...
\the best you can find and the most easy

Thanks everyone for the help! Got it rooted and up and running...finally. Trial and error might not be fun, but it get's the job done and you learn!

I rooted mine using the gfree method and didn't even have to touch a computer... All through terminal...
Sent from my doped up HTC Glacier.

[Q] i want to root my HTC Desire Z..

i have these specs:
model number: HTC Desire Z A7272
IMEI SV: 01
Android Version: 2.2.1
kernesystem: 2.6.32.21-g6e170e7
[email protected] #1
softwarenumber: 1.82.405.1
i am guessing that i need to follow the downgrade guide, and the root guide next.
or has the circumstances changed since the guides was written ?

This is the best guide and is regularly updated http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
Sent from my HTC Desire S using XDA Premium App

Hey, I downgraded and rooted my Desire Z by using the wiki few weeks back. Took me about one hour in total, reading through everything and following the instructions! Have you downloaded the ADB? I just used DroidExplorer which I find so much easier to use!
Sent from my HTC Vision using XDA App

..
DroidExplorer instead of ADB ?
i downloaded ADB but cant get the cmd prompt to serve me
c:\> ADB devices
it prompts: "'adb' is not recognized as an internal bla bla bla.."
so im of to a bad start. even before im really getting started

krankdroid said:
DroidExplorer instead of ADB ?
i downloaded ADB but cant get the cmd prompt to serve me
c:\> ADB devices
it prompts: "'adb' is not recognized as an internal bla bla bla.."
so im of to a bad start. even before im really getting started
Click to expand...
Click to collapse
You need to change to the directory where adb is. It will be something like c:\>Android-sdk\platform tools
Sent from my HTC Desire S using XDA Premium App

krankdroid said:
DroidExplorer instead of ADB ?
Click to expand...
Click to collapse
Yeah it's so much easier to manage then ADB. It's basically like using Windows Explorer but for your phone, so it's really easy to add apps and files or whatever to your phone without having to remember to use ADB codes (especially if your a beginner like me).
It comes with the Android SDK everything setup so you don't need to deal with the setup of the ADB which saves the hassle and time. All you would need to do is just point CMD in the path of the ADB inside Droid Explorer and you're good to go! I would post a link for you but I cant obviously, so just give it a Google and you'll find it.

Your IMEI (and probably IMSI?) is personal information that you should not post on the internet. Not sure exactly what nefarious things can be done with it (if any), but it also has no real bearing on the discussion (whether the phone can be rooted), so you best take it off.

redpoint73 said:
Your IMEI (and probably IMSI?) is personal information that you should not post on the internet. Not sure exactly what nefarious things can be done with it (if any), but it also has no real bearing on the discussion (whether the phone can be rooted), so you best take it off.
Click to expand...
Click to collapse
I agree to delete imei number
Sent from my HTC Desire Z using XDA App

ok..
so now ADB is working with my phone..
the next step is downgrading. that will wipe my device. so how on earth do i take a backup, if i need to wipe my device, before i can root, so that i can take a titanium backup?
is it just tuff luck for me?.. goodbye apps and widgets? or can i backup before i root ?

You can use any backup/restore app to do the job.
The guide someone posted earlier in the thread works flawlessly there're only a few things to remember:
When using ADB when pushing files make sure you're in the same folder as the file itself otherwise it'll return the error "No such file or directory".
If you followed the guide to setting up ADB then you will have changed "Path" under "System Variables" in "Environmental Variables" (Right-click My Computer > Advanced tab > Environmental Variables) to include the following:
";C:\Android\android-sdk\platform-tools;C:\Android\android-sdk\tools"
(No quotes and leave out the semicolon at the beginning if there already is one.)
Change C:\Android\android-sdk\ to wherever ADB is on your comp and you can issue ADB commands from any from almost anywhere on the comp rather than having to be in the same folder as it.
Other than that I can't think of much else other than to follow the instructions and ask for help if you get stuck.

I got ADB working..
I will stick to posting if i run into any problems.
But before i can root i need to downgrade my device first. And this procedure will wipe my phone..
I also need to root before i can do a titanium backup.
I have taken a mybackup pro backup. But that is only apps, media and data. And not a complete backup. As i understand it i cannot create a real backup unless i root right?
And to root i need to perform a downgrade that will wipe my device..
So no matter what i will loose all my stuff if i want to root..
Via HTC Desire Z

Your Gmail and Contacts are synched to Google, so no need to back those up. If you want to backup your SMS and MMS, I have been using SMS Backup+, and it works well. It backs up SMS/MMS to Gmail, and restores SMS to the phone (unfortunately does not restore MMS pics to the phone, but those will be saved on Gmail). It also supposed to backup the call log, but it doesn't restore properly for me after switching ROMs.
If you want to backup things like games saves, root is usually need to access those files. Although, there are apps on the Market to backup your Angry Birds progress, if you want that!
Any other things you want backed up before you downgrade?

If you follow the guide to root your Desire Z you shouldn't run into much problems.
There's a few recent post on the forum with similar questions and will be more then happy to help you get rooted. Like I mentioned to someone earlier, I rooted by DZ just now for about 2weeks. Yeah I did brick my phone twice but I did manage to get everything back to working and rooted. My only mistake was that I hadn't created and fallowed the goldcard process but once that was done anything to do with ADB worked like a charm.

i am now trying to learn the INFOCID of my device..
but something is up.
Code:
cd C:\android-sdk-windows\platform-tools
adb reboot bootloader
fastboot oem boot
the first time i tried it. i wrote "adb reboot bootloader"
it booted up with into the volume button navigation. i then wrote "fastboot oem boot"
and it told me "fastboot is not a command"
It start to load when choosing fastboot on the device, but then stops with an error and goes back to boot menu.
the info i obtained from the first command was:
Code:
vision PVT Ship S-on
Hboot-0.85.0010
microp-0425
radio-26.04.02.17_M2
eMMC-boot
no INFOCID there as far as i can see
could someone help a newbie out ?
I need to know my infocid before i can downgrade

KalC87 said:
Hey, I downgraded and rooted my Desire Z by using the wiki few weeks back. Took me about one hour in total, reading through everything and following the instructions! Have you downloaded the ADB? I just used DroidExplorer which I find so much easier to use!
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Hi hoe did you do with droid explorer i can't there is a tutorial or something??

krankdroid said:
....
the first time i tried it. i wrote "adb reboot bootloader"
it booted up with into the volume button navigation. i then wrote "fastboot oem boot"
and it told me "fastboot is not a command"
It start to load when choosing fastboot on the device, but then stops with an error and goes back to boot menu.
....
Click to expand...
Click to collapse
I got fastboot from the HTC Dev Center.