[Q] ADB on Rooting - G2 and Desire Z Q&A, Help & Troubleshooting

I am going to root using the [GUIDE][30/06/2011]Root AND Downgrade Desire Z/G2(S-OFF/ClockWorkMod) -No Gingerbread topic to root. I have a question though regarding ADB as i dont want to brick my phone.
when it says :
Now you are ready to begin:
1. Open a CMD prompt window
2. Navigate your way to the folder with psneuter & misc_version IN CMD PROMPT. (So the cmd prompt window should be something like this C:\RootVision> )
3. Now we will use the following 5 commands one after the other
Code:
adb push psneuter /data/local/tmp
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/psneuter
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/psneuter
adb shell
do i need to mount the phone or just do this:
Plug phone in
turn on usb debugging
navigate to folder
type in 5 commands or do i need to "register" or "identify" the phone that I want to move the psneuter for example to ? or do I just type in the commands without doing anything ?
so basically I dont need to connect to my phone it does it automatically.
in other words if I just plug my phone in and open up cmd and the first 2 commands are this:
cd C:/RootVision
adb push psneuter /data/local/tmp
Then psneuter will be 'pushed' to my phones /data/local/tmp directory ?
Sorry for the confusing post but trying to get my confusion across.

bump..................

As long as you are in the adb folder it will work by just entering the commands. If you feel more comfortable knowing adb properly sees your phone just type 'adb devices' in command prompt while in your adb folder. It should return something like 'HTC0098755432' or something with a lot of numbers, as long as it doesn't say "No Devices Found" then you're good
Edit: Also I seriously recommend the wiki here on xda for rooting, it's much more concise and provides links to everything you could need
Sent from my Bulletproof G2

PaganAng3l said:
As long as you are in the adb folder it will work by just entering the commands. If you feel more comfortable knowing adb properly sees your phone just type 'adb devices' in command prompt while in your adb folder. It should return something like 'HTC0098755432' or something with a lot of numbers, as long as it doesn't say "No Devices Found" then you're good
Edit: Also I seriously recommend the wiki here on xda for rooting, it's much more concise and provides links to everything you could need
Sent from my Bulletproof G2
Click to expand...
Click to collapse
I find the layout too hard on the eye. Would the topic I referred to work safely to root the desire z ?

If you find it hard on the eye, use the cyanogenmod guide
It's just a stripped down version of the xda wiki.
-Nipqer

trippinz said:
I find the layout too hard on the eye. Would the topic I referred to work safely to root the desire z ?
Click to expand...
Click to collapse
It would most likely work, although being a guide already 4 months out of date, I can't say for sure. What I am absolutely sure of is that the xda wiki or the cyanogen wiki pointed out by the post above me will work and work safely with little to no chance of brick as long as you follow the instructions. Ultimately it's your device to do with as you wish, we simply were pointing out guides that are tested and known to be good
Sent from my Bulletproof G2

Related

adb shell

ok so i tried to follow the instructions to get my phone rooted!
but im running into a snag....
im here roughly
Check if your phone is detected by ADB
Open up Command Prompt (Go to run, type in cmd, press enter)
Type in
Code:
cd C:\android-sdk-windows\tools === Press Enter
adb devices === You should see your device listed
adb shell === you should see # in the next line
Now you are all set to run adb commands
Note: for a list of commands type in 'adb' in cmd
CONGRATS YOU NOW HAVE ADB FULLY RUNNING!
except when i type adb shell i get a "$" instead of a "#" in the next line
im not sure if i did something wrong/installed drivers wrong or what??!! any help would be appreciated!
to get your phone rooted, read the rooting tutorial in the development section.
but, in answer to your question, you are getting the '$' instead of the '#' because you do not have root access in your shell.
to have root access in shell, you need to have installed the rooted img, which will then allow for temporary installation of a custom recovery, which must be pushed while the phone is in recovery mode already. then, you can adb shell to the root prompt
ok im very very new too all this! so i apologize up front for not knowing exactly what your talking about! i have been following this guide to root my phone-
forum.xda-developers(DOT)com/showthread.php?t=532719
(take out the (DOT) and make it .com
some1 on this site refereed it to me because i needed to know how to do EVERYTHING from start to finish!
so i am still stuck any help(detailed very detailed help) would be appreciated!

[Q] Help with setting up adb shell

I must be stupid or something cause I'm stuck on getting this to work. Can someone help me finalize setting up adb shell?
This is where I am so far:
I have installed phone driver and Android SDK. In SDK have installed packages API 2 through 8, usb driver package 3, etc.
What do I need to do when opening SDK manager? My phone is in tether mode but it just sits there. What am I not doing?
Thanks.
No love from the community on this one??
I'm a little confused.
When you set the evo to usb debugging and open a command prompt, cd to your sdk/tools dir, enter "adb devices" does your evo show up? It should be listed as a serial #.
Yes.....an HT### serial comes up which I am assuming is the phone. Guessing I can now just run the commands I need and it will communicate with the phone?
My confusion was that I was running the SDK Manager.exe and expecting it to find my phone and produce the adb shell.
Ok! You should be good to go. Just enter "adb shell" and you are set.
Good deal....thx.
Ok....thought I had this working. However, when in adb shell any commands I put in tells me "adb: not found".
What do I need to do from this point?
Let me clarify this.....
When I list devices it does find my phone. But, when issuing the adb shell command and trying to enter anything from the "#" prompt it always says "adb: not found".
I must be missing a step or something.
I'm kind of confused, mostly because I don't know what it is you're doing in a shell, but once you're in the shell and you get the # sign, there's no need to type in adb before your commands, for example, from the command line you would navigate to your tools folder. For me it would be
cd AndroidSDK/tools
./adb shell
Some jibber jabber about daemon starting
#
From then on I could run whatever command I planned on running in the shell like
echo 1 > /sys/class/leds/flashlight/brightness
And not
./adb echo 1 > /sys/class/leds/flashlight/brightness
CCallahan said:
Let me clarify this.....
When I list devices it does find my phone. But, when issuing the adb shell command and trying to enter anything from the "#" prompt it always says "adb: not found".
I must be missing a step or something.
Click to expand...
Click to collapse
What exactly are you trying to accomplish? Then we can determine what's going on.
I'm running Myn's RLS4 and am trying to change the power bar in the notifications.
Trying to follow the instructions in this link: http://forum.xda-developers.com/showthread.php?t=836721
OK. What part are you getting stuck at?
Edit: for this code, you do not need to be in the ADB shell:
Code:
adb remount
adb push widget.txt /system/customize/
adb reboot
You just need to cd to your tools folder of the SDK in your command prompt.
CCallahan said:
I'm running Myn's RLS4 and am trying to change the power bar in the notifications.
Trying to follow the instructions in this link: http://forum.xda-developers.com/showthread.php?t=836721
Click to expand...
Click to collapse
The commands he has given here
Code:
adb remount adb push widget.txt /system/customize/ adb reboot
do not require you to be in an adb shell, you just open up the command window do an adb remount then type in his commands one by one and male sure you have the .txt file that specifies what widgets you're going to use is in the tools folder of your AndroidSDK folder so that adb can locate and push it to its respective directory.
Ok...that worked.
Knew I was doing something wrong. Was trying to run those commands from the adb shell....makes sense that it could not find adb.
Thanks.
i have no adb shell at all can anyone help?

ADB

I'm trying the rage root method after reading up on all the stuff. I managed to get adb installed and connected, but i can't use adb actions.
I type in c\androidsdk\tools\adb shell
$ su
$ SUermission denied
even without su, if i try to type "adb push su /sdcard/su" it says adb permission denied.
I have kept my phone screen on as per another thread, but i do not get a prompt that asks for adb permissions. Am i missing an app or something? I do have debugging and screen awke both on.
I have placed the g2 root folder in the androidsdk\tools\ folder, both just the files and the entire folder just to be sure.
Obviously I'm new to adb, so If i'm doing something completely wrong just let me know.
as long as you're not rooted (temp or perma) you can't use "su" in adb-commands... If you tell a little more about what you're trying to push, then I can help some more
Im just trying to root the phone with rage since visionary seems unreliable.
Im trying to adb push the su/ sdcard/su as per the first line of instruction in the rage temp root guide
hehe... I used the visionary root, and it have worked good for me btw, I think you should've posted in the rage-thread instead of opening a new topic, but now it's already opened so here it goes
firstly... are you sure you're in the right folder, and have the folder "su" in there?
If so, don't go into "adb shell"... use the lines exactly as stated in the OP. adb inside an adb shell won't give the results you want... Post back if it doesn't work
$ adb push su /sdcard/su
$ adb push Superuser.apk /sdcard/Superuser.apk
$ adb push rage /data/local/tmp/rage
$ adb push busybox /data/local/tmp/busybox
$ adb push root /data/local/tmp/root
$ adb shell chmod 0755 /data/local/tmp/*
Click to expand...
Click to collapse
I don't think Im using adb right then, how do I just type in "adb push ...?" If I do that, it just says that the command is not recognized internally or externally.
For example,
Adb push su/ sdcard/su
gives me that error.
I've tried to set a path directly to adb, but that didn't work, so I was manually going
AndroidSKD\tools\ Adb push su/ sdcard/su but that also didnt work.
I don't have the $ prompt without shell, is that wrong?
I'm pretty sure Im in the right folder, as androidsdk\tools\adb gives me the adb directory, just nothing else works. What exactly does SU folder mean? I have the su file in the tools folder, dont know about the su folder.
Ok, my adb stuff is in c:\tools .. so when I first open command prompt, I have to type this:
cd c:\tools
That puts me into the correct folder. If yours is in C, then you'd probably have to do this:
cd c:\androidsdk\tools
Then type:
adb devices
It should at least give you SOME sort of output, either with your device number (if it's connected, and adb is working properly), or just say devices, with no numbers (incorrectly)
dwang93 said:
I don't think Im using adb right then, how do I just type in "adb push ...?" If I do that, it just says that the command is not recognized internally or externally.
For example,
Adb push su/ sdcard/su
gives me that error.
I've tried to set a path directly to adb, but that didn't work, so I was manually going
AndroidSKD\tools\ Adb push su/ sdcard/su but that also didnt work.
I don't have the $ prompt without shell, is that wrong?
I'm pretty sure Im in the right folder, as androidsdk\tools\adb gives me the adb directory, just nothing else works. What exactly does SU folder mean? I have the su file in the tools folder, dont know about the su folder.
Click to expand...
Click to collapse
You, apparently, need to read some more.
Do it exactly as written here
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
FYI you will not see the $ symbol. that just indicated the next line you have to enter in commnad prompt. Each time you see $ just mean you type that line then press enter. Wait to see a result of transfer from prompt then enter next line and so on.
rsxtypes72 said:
You, apparently, need to read some more.
Do it exactly as written here
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
Click to expand...
Click to collapse
This!! I'll be kind though.
Make your life easy. Unzip the contents of g2TempRoot, to your tools folder, in sdk. So, unzip the g2temproot to your desktop. Go into that folder. Copy all, and move them to c:\androidsdk\tools. Now, once that's done, go into command prompt. cd c:\androidsdk\tools. Then, do as follows, as per that link
$ adb push su /sdcard/su
$ adb push Superuser.apk /sdcard/Superuser.apk
$ adb push rage /data/local/tmp/rage
$ adb push busybox /data/local/tmp/busybox
$ adb push root /data/local/tmp/root
$ adb shell chmod 0755 /data/local/tmp/*
(Sorry I couldn't be of more help, as I used VisionaryR12 and it worked fine for me.)
One more word of advise...
I would recommend you try temp root first.
Become used to using adb then try to get full root.
When you use temp root everything you do is temporary only.
Rebooting will reset everything back to stock so its good practice.
thanks for the help guys, but i figured it out. I just wasn't in the right directories from the get go.
Edit: Just finished the perm root! And it didn't brick.
dwang93 said:
thanks for the help guys, but i figured it out. I just wasn't in the right directories from the get go.
any tips on going onto the perm root?
Click to expand...
Click to collapse
Read .. research .. double check .. triple check .. and right before you do it .. check again. As you're doing it, go over every letter, space, and character to make sure it's as it should be.
On the subject of adb, I have it installed, but when I run adb devices to find my phone, I get "???????????? no permissions". What am I doing wrong here?
Daughain said:
On the subject of adb, I have it installed, but when I run adb devices to find my phone, I get "???????????? no permissions". What am I doing wrong here?
Click to expand...
Click to collapse
Upload a screen shot of your command window
with the error
dwang93 said:
thanks for the help guys, but i figured it out. I just wasn't in the right directories from the get go.
Edit: Just finished the perm root! And it didn't brick.
Click to expand...
Click to collapse
dude..I think I am doing something like you...could you please post what you did....I think is an issue of directories..but I'm not that familiar with adb and i have not been able to figure this out.....
Thanks!!!

Having problems rooting

ADB is not friendly to me. I was able to root my g1 with pure ease. I cant get started with adb, I dont know why I cant get $, I've read several guides and I'm just about to give up. I'm running 2.2 on my g2.
I do have a couple of questions:
Are rooting with rage or visionary 14 the only way to root?
Are there any root guides out there that dont require ADB?
ADB is a ****ing pain in the ass to me, especially since I've tried everything and cant get it to work. Also, the drivers that go on Win7 64bit just dont work.
Also when I do have root, can I get android updates?
Any help would be thankfully appreciated. Sorry if I'm a pain in the ass, but I'd like to know if there is an easier way.
I think you need the q&a section
Sent from my HTC Vision using XDA App
This will help u get adb working...
http://forum.xda-developers.com/showthread.php?t=865685
If you can't figure out adb, you definitely shouldn't be rooting your phone.
Some ROMS disable OTA notifications while others allow it. However, so long as you have a custom recovery, even if you get the notification and download it, you wont be able to flash it.
dictionary said:
If you can't figure out adb, you definitely shouldn't be rooting your phone.
Some ROMS disable OTA notifications while others allow it. However, so long as you have a custom recovery, even if you get the notification and download it, you wont be able to flash it.
Click to expand...
Click to collapse
while my knowledge of adb isnt stellar, I have run into problems using it. I'm going to try this new link to the guide and see if it works.
Still if anyone knows other solutions, chime in.
Try the guide linked above. The drivers in the HTC Sync package (see the guide) definitely do work on Win 7 64-bit.
Clicked on SDK Manager.exe and it gave me the attached message; anti-virus is off and bare ass minimum services are running and I added the line in variables.
Any ideas?
sorry about the ****ty pics
cwis said:
Clicked on SDK Manager.exe and it gave me the attached message; anti-virus is off and bare ass minimum services are running and I added the line in variables.
Any ideas?
Click to expand...
Click to collapse
Did you definitely add it to your path as it is suggesting in that window ? If so, I think you may need to reboot to pick that change up.
I did that just in case.
Actually, that path field was empty. So, I added it as is.
look up droid explorer
I made some leeway:
C:\Program Files (x86)\android-sdk-windows\tools>adb shell
$
$ adb push su /sdcard/su
$ adb push su /sdcard/su
$ adb: permission denied
good grief!!!!!!!
I've completely removed visionary before starting this procedure. Did I need temproot before attempting this?
Downloading and installing Droid Explorer. Thanks!
Also, I'm using this guide: http://forum.xda-developers.com/showthread.php?t=834228
No matter what I've done, permission denied.
The steps you are trying are actually to get temproot (it's an alternate method to Visionary), so you don't need to already be temprooted.
You don't want to run "adb push" commands after you have run "adb shell". ADB commands will no longer work until you exit the shell (simply type exit and hit enter---you'll notice your command prompt will change back to normal). If you are following the guide you linked to, you'll notice adb shell is not run prior to running the first push command.
ianmcquinn said:
The steps you are trying are actually to get temproot (it's an alternate method to Visionary), so you don't need to already be temprooted.
You don't want to run "adb push" commands after you have run "adb shell". ADB commands will no longer work until you exit the shell (simply type exit and hit enter---you'll notice your command prompt will change back to normal). If you are following the guide you linked to, you'll notice adb shell is not run prior to running the first push command.
Click to expand...
Click to collapse
^^^^ what he said.
You are trying to run adb on your phone there, which isn't right. That's your phone's command prompt, the "$". "adb" is something totally different on your phone. You need to run the adb commands on your PC. That's why "adb shell" worked (because you ran it on your PC), then "adb push" didn't (because you tried to run it on your phone).
steviewevie said:
^^^^ what he said.
You are trying to run adb on your phone there, which isn't right. That's your phone's command prompt, the "$". "adb" is something totally different on your phone. You need to run the adb commands on your PC. That's why "adb shell" worked (because you ran it on your PC), then "adb push" didn't (because you tried to run it on your phone).
Click to expand...
Click to collapse
I did run the commands from my pc. But still permission denied.
cwis said:
I did run the commands from my pc. But still permission denied.
Click to expand...
Click to collapse
"permission denied" is a message from your phone, not your PC.
The $ prompt that you copied and pasted up shows that you were running the commands on your phone. As soon as you do "adb shell", then any commands you are entering after that are going on your phone, even though they're physically being typed on your PC - because your PC has started a command prompt on your phone, as shown by the $ prompt.
cwis said:
I did run the commands from my pc. But still permission denied.
Click to expand...
Click to collapse
Basically, don't start by typing adb shell. The instructions you are trying to follow don't even say to do that anywhere. I highly recommend you reread the instructions very carefully and follow them exactly. Rooting this phone is actually pretty simple if you just do exactly as the guide states. If you don't know what you are doing and mistype something in some of the later steps though, you can seriously screw up your phone...
I think part of the confusion is that the commands listed on the guide all have "$" at the beginning of them, probably because whoever wrote that was using a Linux PC or maybe a Mac. You are actually executing these commands from your Windows command shell so they will look more like:
D:\Android SDK\platform-tools>adb push su /sdcard/su
Click to expand...
Click to collapse
(depending on where you have the SDK installed)
instead of:
$ adb push su /sdcard/su
Click to expand...
Click to collapse
but of course you only need to type:
adb push su /sdcard/su
Click to expand...
Click to collapse
Again these are typed from your windows command shell.

[Q] Downgrade 2.36.405.8

I have a Desire HD with Gingerbread running. I wanted to root my phone, but it seems it is impossible without downgrading.
I have read the tutorials on this site, but every time I type a ''push'' command, I get a very big list of words, like ''Android Debug'' etc. When I have completed all the steps the resul is a $...
I have also tried the GingerBreak method, but when I do so my phone acts very strange, it won't read my SD card until I reboot and when I start Superuser it says that Superuser has to be closed.
Also I have the downgrade folder, but I think the one I have is for Froyo devices, because the Psneuter file is in there, and no GingerBreak.
So, does anyone have a clear tutorial woth download links for the files I need???
I have searched Google, xda, and lots of more sites, but I really can't find any help.....
Thanks for reading,
Desley
Ok,
Firstly you will need to downgrade following this
http://forum.xda-developers.com/showthread.php?t=905003
If you are running a branded phone then you need a Goldcard
Found here
http://www.addictivetips.com/mobile/how-to-make-gold-card-for-htc-desire-hd/
Then follow this guide to get root and Radio s-off
http://forum.xda-developers.com/showthread.php?t=857537
Then if you want to have eng s-off (to flash radios)
http://forum.xda-developers.com/showthread.php?t=855403
I had the same problems you are encountering , as long as you follow the steps through it should go well , of course if you get stuck let me know and I can guide you through it as well.
I have this problem to but i have the right downgrade map with gingerbreak in it. Yesterday i tried 100 of times and at last i got # but i coulden't write anything more in cmd but the # there. NOw today i tried agian with theese steps http://forum.xda-developers.com/showpost.php?p=13367691&postcount=1134
But now i get the Su: Permission denied and nothing pops up in my phone saying do you allow this. What should i do i'm running 2.26.405.8
I have tried the Gingerbreak app to with all the steps but the circel that's spinning keps doing that for like 15min and nothing happens. And yes i have done the factory reset many times and tried agian. Please somebody help
Ok , have you followed all steps I provided above?..
Some things to note are that between each step reboot , it helped me to wipe my sd card.
Have you got the htc sync drivers installed? (make sure htc sync is closed!)
Are you provider locked/is there network bloatware on the phone in which case you would need a goldcard?
If poss can you provide a screenshot of what you have for me and I can help you more
Sent from outer space on my DHD running beatmod gingersense v1.3
Nope my phone is not branded, fully unlocked. I have htc sync i have everything i need from the tutorial. When i have done this
adb push misc_version /data/local/tmp
adb push GingerBreak /data/local/tmp
adb shell chmod 777 /data/local/tmp/misc_version
adb shell chmod 777 /data/local/tmp/GingerBreak
And then write adb shell i get a $ then i write su and i get permission denied
Then i start all over agian and try
adb push misc_version /data/local/tmp
adb push GingerBreak /data/local/tmp
adb shell chmod 777 /data/local/tmp/misc_version
adb shell chmod 777 /data/local/tmp/GingerBreak
adb shell /data/local/tmp/GingerBreak
Then i get things to work and i come to the# but then i can't write antthing more, it's just locked. And everything have passed but one of the lines is like message something failed. And in Su binary voutdated i tap to check for updates in superuser and it says there is a new version of the su binary press Ok to update i press Ok. Then it says An eroor occurred and su was not updated. A zip file, (su-2.3.1-bin-signed. zip) has been placed in your sdcard please reboot into recovery mode ans flash it to update your su binary.
AmirAli44 said:
Then i start all over agian and try
adb push misc_version /data/local/tmp
adb push GingerBreak /data/local/tmp
adb shell chmod 777 /data/local/tmp/misc_version
adb shell chmod 777 /data/local/tmp/GingerBreak
adb shell /data/local/tmp/GingerBreak
Click to expand...
Click to collapse
Try after
adb push misc_version /data/local/tmp
adb push GingerBreak /data/local/tmp
adb shell chmod 777 /data/local/tmp/misc_version
adb shell chmod 777 /data/local/tmp/GingerBreak
Adb shell
./data/local/temp/GingerBreak
don't type the data local bit after adb command , just in case I think you entered the command wrong?
Sent from outer space on my DHD running beatmod gingersense v1.3
steeveeo said:
Try after
adb push misc_version /data/local/tmp
adb push GingerBreak /data/local/tmp
adb shell chmod 777 /data/local/tmp/misc_version
adb shell chmod 777 /data/local/tmp/GingerBreak
Adb shell
./data/local/temp/GingerBreak
don't type the data local bit after adb command , just in case I think you entered the command wrong?
Sent from outer space on my DHD running beatmod gingersense v1.3
Click to expand...
Click to collapse
When i do that i get $
When i write
adb push misc_version /data/local/tmp
adb push GingerBreak /data/local/tmp
adb shell chmod 777 /data/local/tmp/misc_version
adb shell chmod 777 /data/local/tmp/GingerBreak
adb shell /data/local/tmp/GingerBreak
the # comes but i cant write anything and i got all the [*] vold: but just one of them one says [-] sendmsg<> failed?
HELP!
Please anybody i want the new sence 3.0 help me root
I sent u a couple of pm's with some more suggestions
I donny know if u tried them?
Sent from outer space on my DHD running beatmod gingersense v1.3
AmirAli44 said:
Please anybody i want the new sence 3.0 help me root
Click to expand...
Click to collapse
me tooooo
AmirAli44 said:
What should i do i'm running 2.26.405.8
I have tried the Gingerbreak app....
Click to expand...
Click to collapse
What is your Android version?
Is it Froyo or Gingerbread?
Send from my CoreDroid'ed Desire HD
I downgraded yesterday and it didn't work at first but had to do factory reset and it worked after that (If you get some msgfailed text at the end like I did).
I'm stuck :'(
Hi, I'm Maaria, and very very new to all of this!
So I have a desire HD which is locked to all networks except orange. I really want to root my phone so I can customise it and such, and I want to unlock it. I know I need to downgrade and stuff but I don't know how to do this. I mean do I have to get a gold card because it's locked to orange or do I just do it? And I don't even know how to get to the cmd folders or anything :/ I have no idea what to do, I've been looking all over the forum, and internet, this was the best thread I found but its still a bit confusing, for me. :/ I'm really sorry for being a complete idiot when it comes to this stuff but can anyone please help me? I really want to learn how to do it, I'm just totally confused with what to do
Maaria said:
I know I need to downgrade and stuff but I don't know how to do this. I mean do I have to get a gold card because it's locked to orange or do I just do it? And I don't even know how to get to the cmd folders or anything :/ I have no idea what to do, I've been looking all over the forum, and internet, this was the best thread I found but its still a bit confusing, for me. :/ I'm really sorry for being a complete idiot when it comes to this stuff
Click to expand...
Click to collapse
Ok ,
Firstly everyones new to this at some point , gotta start somewhere.
You are correct you will need a goldcard to downgrade which is in one of my links above
Cmd= command prompt , you can type cmd in your search bar in windows and it will bring it up for you , our find it in your accessories.
Something important to note, if you've upgraded to 2.3.7 downgrade is not possible at the moment , but keep an eye out as I'm sure it'll happen.
Any questions can pm me and I will help as I struggled for some time and picked up a lot of info from the site .
Good luck
Sent from outer space on my DHD running beatmod gingersense v1.3
welcome here ,any help ???
evanbigfan said:
welcome here ,any help ???
Click to expand...
Click to collapse
Hi, are you struggling to root as well?..
Will need some info.
Branded/unbranded device
froyo/gingerbread system
If you're running 2.3.7 there's no fix at the moment..
Just the basics , if I have a more specific problem then post it and can have a look.
Sent from outer space on my DHD running beatmod gingersense v1.3
What means branded?
Also got stuck, but never maked a goldcard.
Thnx
Harganeth said:
What means branded?
Also got stuck, but never maked a goldcard.
Thnx
Click to expand...
Click to collapse
Provider/network locked...
And ok , where did u get stuck? If you let me know some more details I can help you more.
Sent from outer space on my DHD running beatmod gingersense v1.3
How do i know if my phone is Provider/Network locked?
And steve, i will try out your steps so for now only this question and will see later if it works : thnx anyways

Categories

Resources