Related
Is it possible to complete the whole process on a mac? I don't have a PC.
i found this.
http://www.droidfilez.com/Evo4GRoot.html
dont know what it is/how it works though.
proceed at your own risk.
yes, all you need to root is adb!
download the adb sdk for mac and use the terminal app in utilities to execute adb commands
after you set up the sdk execute the commands, like the examples :
./adb devices
./adb shell
./adb push
just follow the guides to root and wheerever it says to use adb use ./adb instead because your on a mac.
hope you got the jist of what im saying
i wouldnt use the above post "automated rooter" just yet... you're new to this, you should research mroe about the automated rooter and if it does what it says it does. wait till it comes up on xda?
EDIT : follow the guide that waterboy100 posted below if you want to do it without adb. i would encourage you to learn adb though as its simple and will help you learn more about rooting in the long run.
this guy should have a post up soon too
http://forum.xda-developers.com/showthread.php?t=701152
chim4ira312 said:
yes, all you need to root is adb!
download the adb sdk for mac and use the terminal app in utilities to execute adb commands
after you set up the sdk execute the commands, like the examples :
./adb devices
./adb shell
./adb push
just follow the guides to root and wheerever it says to use adb use ./adb instead because your on a mac.
hope you got the jist of what im saying
i wouldnt use the above post "automated rooter" just yet... you're new to this, you should research mroe about the automated rooter and if it does what it says it does. wait till it comes up on xda?
EDIT : follow the guide that waterboy100 posted below if you want to do it without adb. i would encourage you to learn adb though as its simple and will help you learn more about rooting in the long run.
Click to expand...
Click to collapse
I am downloading the sdk now and I am interested in this. I have the 1st root completed and I am trying to get the second section done and I am having a hell of a time :/
you can totally do every rooting ability in Mac. I got a hackintosh and downloaded the ADB kit and just plug in the phone and ADB recognized in an instance. No need to install driver like Windows.
I just did the rull NAND unlocking with root on my Mac.
Awesome I downloaded the files and I'll try doing it today. I wanted to remove some Sprint Apps and maybe flash a ROM later one when the builds become more solid and bugs get worked out.
By the way I'm playing Pocket Empires to kill time and it's pretty cool. If I root will I have to start the game all over again?
i've done everything on my mac...works great!
I'm lost as hell. I found this thread:
http://www.androidpolice.com/2010/0...-write-permissions-to-system-incredible-next/
I did the unrevoked thing and I see this icon called SuperUser Permissions in my app list.
Am I able to proceed and fully root or do I have to re-do the root with the Toast method? This looks too complicated and by the way I tried the ./adb thing on my mac and I get errors saying "No such file or directory".
im trying to push the pcimg to sdcard and its saying access denied
Why do you guys say "Oh, I did it on my mac" without saying HOW you did it on your mac? Regular instructions dont work so you obviously did something special to make it work... I keep getting permission denied BS
Here you go dude. Step by step instructions along with the download links. I followed this to the T and it worked out find for me:
http://forum.androidcentral.com/htc-evo-4g-roms-hacks/17766-how-full-root-evo-4g-mac.html
Ive tried the black prince video, the unlockr method and the original xda perm root guide and my G2 will not perm root. Seriously need some help.
do you have adb and sdk installed?
>
no such thing!
its just smarter than you (;
lol
it is funny that you mention the black prince video, because that is what i used. im not sure, but i followed that video exactly and got it my first try. just watch the video very carefully, and follow EVERYTHING that he does and it should work. if not, then i am really not sure. obviously, you just need "S-off"
Are you using Visionary ? I would suggest the rage method, IMHO it's a lot more reliable and you can see if anything goes wrong because you're using individual commands.
i know its possible because I rooted my friends G2 just days before I got mine. I don't have adb, to be honest as soon as i see that it takes more than just installing a program on my pc, i flee, and its not because im new to android or rooting or anything like that, i just don't have a whole lot of spare time. And i DO have S-OFF. Like ill do everything in the blackprince video, then after I'm done I'll got and test the root by typing SU in terminal, and it says permission denied. Or for any of the other methods, same thing.
Now if someone could give me a REAL WALK THROUGH on how to do it in ADB and not just assume I already know how to use it and use vocabulary I don't understand because I've never used the program, i would be willing to try that method. It's just all the walkthroughs for ADB ive found just assume I've already used it before and know how to use it.
adamtheindien said:
Now if someone could give me a REAL WALK THROUGH on how to do it in ADB and not just assume I already know how to use it and use vocabulary I don't understand because I've never used the program, i would be willing to try that method. It's just all the walkthroughs for ADB ive found just assume I've already used it before and know how to use it.
Click to expand...
Click to collapse
Download HTC Sync from the HTC website (look in the downloads section), and install that on your PC. That'll give you all the USB drivers you need.
Download the Android SDK from http://developer.android.com/sdk/index.html and install it on your PC. Be sure to read the guide on installing it at http://developer.android.com/sdk/installing.html
Plug your phone in to your PC using the original HTC cable (do not use a third-party cable for this) and type "adb devices" at your PC's command prompt, and tell us if it can see your phone. It should show up your phone's serial number (don't tell us exactly what that is, this is a public forum), but if there's an error then we need to sort that first.
Edit - partially prompted by this request, I've started an "adb for Noobs" guide (very much a work-in-progress) at http://forum.xda-developers.com/showthread.php?t=865685
installed htc synce, sdk, jdk for sdk, went into command prompt, typed adb devices, said adb was recognized as any kind of command.
and thank you for starting that guide, definitely something that needed to be done.
http://www.youtube.com/watch?v=A1SOSXwkc_8
adamtheindien said:
installed htc synce, sdk, jdk for sdk, went into command prompt, typed adb devices, said adb was recognized as any kind of command.
and thank you for starting that guide, definitely something that needed to be done.
Click to expand...
Click to collapse
when you type adb devices does it recognize your device?
Super easy way.... http://forum.xda-developers.com/showthread.php?t=834228 just copy paste the codes.
Your phone might be s-off, but not allowing you to do any su commands. Mine was, but I just installed rom manager and it flashed clockwork recover no problem, then I flashed cyanogen and everything was good. Go into hboot and just make sure it says s-off, then do the rom manager bit. Try it and see if it works.
no it doesnt do anything. just says its not a command. and ive already looked at that link, i'm already lost when it tells me to navigate to a folder in a command window.
yeah, but i cant use rom manager since i dont have super user permissions. do i just temp root then try to install a rom? that seems sketchy. haha.
Earlier you said that you have S-OFF. If this is the case, then just open up Market and download Superuser by ChainsDD. Then you should be good to go.
adamtheindien said:
no it doesnt do anything. just says its not a command. and ive already looked at that link, i'm already lost when it tells me to navigate to a folder in a command window.
Click to expand...
Click to collapse
When you type "adb" on your PC, Windows needs to know where to find the "adb" program to run it. So you either need to specifically add the directory containing adb to your Windows PATH variable (which you can do in the environmental variables section, which will be in different places on different operating systems - on XP you need to right-click on My Computer, then select Properties, then Advanced, then the "Environmental Variables" button) - or you need to cd to where adb is stored under where you installed the Android SDK, and run it from that folder.
pretend youre explaining this to a five year old...
ok, which operating system do you have on your PC ?
Where did you install the Android SDK, i.e. which folder on the PC did you put it in ?
never mind guys, did what that dude said and just installed a rom with temp root and im all good now. thanks for everyones help though, sorry for my lack of knowledge in adb and what not.
In the process of following the rooting wiki, had hella problems getting adb working. Got adb connected finally, got the money sign, tried first instruction, got adbermission denied. What could be the problem? Did a google search as well. I have the contents of adb tools, in the same place as g free, as it is completely impossible to start up adb shell, and then navigate to a completely different folder. Also, before moving adb tools, tried long addresses of the gfree stuff, same deal.
Did you do "adb shell" and then you tried more adb commands and got "permission denied" ?
If so, then that's because "adb shell" starts a command prompt session on your phone, and the adb commands need to be run on your PC, not your phone. So don't do the "adb shell" first.
So wait a second, you're saying that the wonderful wiki, either is in the wrong order, or requires me to follow the pc, and phone steps simultaneously? Because im running them from my pc. Which would be implied by my saying im following the wiki. Fyi, i meant the one on the g2, involving rooting the g2, on the xda-dev site. I've done this before, i know how to use adb. this is the first time i have rooted a g2. Don't mean to sound like a ****, but you basically didnt read anything i wrote.
The Wiki isn't in the wrong order. But IMHO it's very confusing that it shows a $ prompt when it shows "adb push" etc, because that makes it looks like it is run on the phone. But it's assuming you're running from Linux/Mac. On a PC the prompt for your adb commands would be C:\ or similar.
The Wiki doesn't tell you to run "adb shell"
So the answer to my question was yes, it works, but i had to wait 5 minutes to post this. I dont understand why there cant be a note that, unless you put adb into your path, cmd isnt going to recognize it unless its in the folder you're using. I feel no need to put a tool that i will use maybe once a year at most into path. also, when i just checked the wiki now, i noticed how the dollar signs had changed to c:/ ha ha. and sorry about the rudeness, at first it just seemed like you were making fun of me.
jenlow said:
Okay, so before i opened the adb shell from cmd, when i would type adb push, i would get adb is not recognized as an internal or external command. so, my solution of putting the adb tools into gfree, should work now once i cd to the gfree folder?
Click to expand...
Click to collapse
That's an issue with your path not being setup properly on your PC. You can adb adb's folder to the path to mean you can run it from anywhere. Otherwise you need to put the gfree tools etc in the same folder as adb, then cd to there and run the commands.
Or if the path is setup properly, cd to where the gfree tools are and start doing your "adb push" etc from there.
I have just edited the Wiki to show a "C:\" prompt for the stuff that's run on the PC, to try and avoid this confusion.
Did it work ?
jenlow said:
In the process of following the rooting wiki, had hella problems getting adb working. Got adb connected finally, got the money sign, tried first instruction, got adbermission denied. What could be the problem? Did a google search as well. I have the contents of adb tools, in the same place as g free, as it is completely impossible to start up adb shell, and then navigate to a completely different folder. Also, before moving adb tools, tried long addresses of the gfree stuff, same deal.
Click to expand...
Click to collapse
the "permission denied" thing... from the phone? Or from the computer? You know you need to be root in order to access the hardware, or at least set the permissions on the hardware to be accessible to your user account....???
And... you DID enable adb on the phone side, didn't you?
I used the Wiki and am now perm rooted. A few tips that may help you since they helped me to get it done. I opened a command prompt and noted the default path that opened. For me it was C:\Users\Ed . I used windows explorer to navigate there and open up the Ed folder and created a new folder in Ed that I named pr. This is where I unzipped both of the gfree zip files...into that same folder. When temp rooting and perm rooting, I simply opened up the command prompt, it opened to C:\Users\Ed and then I typed cd pr then I hit enter. That set me up to input the commands in the right place both times and it worked out just fine.
Another thing that I noticed. After temp rooting, I had to ctrl alt del to open up task manager and close down adb.exe (as noted in the instructions that appeared in terminal emulator). I couldn't load adb again until I closed it down and let it restart itself. When I entered the first command in the perm root process adb started up again by itself and all went well.
Good Luck! It is well worth it. I now have Cyanogen's latest stable build loaded along with the Google apps package that I found online.
Ed
OH! yeah, it did work. i thought i said that somewhere ha. I am currently running CM 6.1.1 now. I've decided that since the adb file, and necessary files are tiny i can just move them around to whatever i need to use adb for. Path editing should only be done by hand in linux And jesus CM has improved since i had it on my cliq. I'm like 90% sure i'm going to make a donation out of the school funds.
Root my phone!!! HELP
Hi Guys
I've tried root and my cell phone, but it is not. I've tried almost everything I have .. First I tried to root using the terminal emulator''''by typing different commands ..
Also, I tried the program''Visionary''but when I pressed the application so that it was held to root, but then the screen goes black, and I had to press the home button to get out of the situation ..
Also tried I saw another app called ''Universal androot'' and when I pressed root, then came the''Failed! No ~~~~~~~~~ Fu goo ..'' I also tried''app ''superoneclick I pressed the root, also came the''error: protocol fault (no status)''
What should i suppose to do, to fix this problem.. please reply
Thaaaanks!!!
mannær said:
Hi Guys
I've tried root and my cell phone, but it is not. I've tried almost everything I have .. First I tried to root using the terminal emulator''''by typing different commands ..
Also, I tried the program''Visionary''but when I pressed the application so that it was held to root, but then the screen goes black, and I had to press the home button to get out of the situation ..
Also tried I saw another app called ''Universal androot'' and when I pressed root, then came the''Failed! No ~~~~~~~~~ Fu goo ..'' I also tried''app ''superoneclick I pressed the root, also came the''error: protocol fault (no status)''
What should i suppose to do, to fix this problem.. please reply
Thaaaanks!!!
Click to expand...
Click to collapse
None of those apps work with the G2 to perm root without extra steps. And in that case only Visionary. You need to check out the vision wiki page.
Ed thoroughly described how to make it work. I did the exact same thing he did and got it last night.
jenlow said:
OH! yeah, it did work. i thought i said that somewhere ha. I am currently running CM 6.1.1 now. I've decided that since the adb file, and necessary files are tiny i can just move them around to whatever i need to use adb for. Path editing should only be done by hand in linux And jesus CM has improved since i had it on my cliq. I'm like 90% sure i'm going to make a donation out of the school funds.
Click to expand...
Click to collapse
What method did you use to root your cliq, and did you still have 3G? I have stock motoblur 2.1 on it now, I have it for a backup phone (got a G2), but I would like to root it.
About 3 hours ago, I won a Desire Z (wheeey!) at the HTC London meetup. Naturally, I came straight here after the help I got in January rooting my Desire.
I used the Visionary method and obtained temp root status, and then attempted perm root, which seemed to work. All of the guides I have read include a bunch of steps after this, one of which included deleting Visionary, which I then did. I just turned the phone off, took the battery out for a bit and then turned it back on. I still have the Superuser icon and the Terminal Emulator indicates that I have root access... is that it then? It's that simple?
Please tell me if I've done anything wrong, as I don't want to flash Cyanogen and Clockwork Recovery if it's all going to go to hell on me. Any advice or confirmation on whether or not I've obtained perm root would be lovely.
Oh, my firmware version is 1.34.405... etc. Is this simply the last version which allows for such easy root?
Arconaught said:
About 3 hours ago, I won a Desire Z (wheeey!) at the HTC London meetup. Naturally, I came straight here after the help I got in January rooting my Desire.
I used the Visionary method and obtained temp root status, and then attempted perm root, which seemed to work. All of the guides I have read include a bunch of steps after this, one of which included deleting Visionary, which I then did. I just turned the phone off, took the battery out for a bit and then turned it back on. I still have the Superuser icon and the Terminal Emulator indicates that I have root access... is that it then? It's that simple?
Please tell me if I've done anything wrong, as I don't want to flash Cyanogen and Clockwork Recovery if it's all going to go to hell on me. Any advice or confirmation on whether or not I've obtained perm root would be lovely.
Oh, my firmware version is 1.34.405... etc. Is this simply the last version which allows for such easy root?
Click to expand...
Click to collapse
Having the SuperUser icon just means the app is installed, open up terminal and type 'su' to see if it throws up any errors
Sent from my HTC Vision using XDA App
I should have mentioned that I did that and got the # symbol, am I good to go?
Arconaught said:
I should have mentioned that I did that and got the # symbol, am I good to go?
Click to expand...
Click to collapse
In theory, yes; in practice, no. Visionary (with the G2/Desire Z, at least) is known to be a bit buggy. You shouldn't have any issues installing custom ROMs but, I would recommend using the wiki method to root.
Sent from my HTC Vision using XDA App
OriginalGabriel said:
In theory, yes; in practice, no. Visionary (with the G2/Desire Z, at least) is known to be a bit buggy. You shouldn't have any issues installing custom ROMs but, I would recommend using the wiki method to root.
Click to expand...
Click to collapse
My understanding, if he already used Visionary to root, and it worked than he should be good to go. Either it works, or it doesn't. The risk with Visionary is that it sometimes corrupts some partitions, which causes the phone to not boot. I haven't read any conclusive reports on Visionary causing long term issues (correct me if I'm wrong).
redpoint73 said:
My understanding, if he already used Visionary to root, and it worked than he should be good to go. Either it works, or it doesn't. The risk with Visionary is that it sometimes corrupts some partitions, which causes the phone to not boot. I haven't read any conclusive reports on Visionary causing long term issues (correct me if I'm wrong).
Click to expand...
Click to collapse
This is my understanding as well, though I'd probably still use GFREE to get S-OFF if I were OP.
That's my next question, I'm using this guide ( http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2 ) to try and get S-Off to flash Cyanogen and I'm wondering what step to start on, assuming from your replies that I'm rooted already.
I know it's a bit of a dumb question, but I just don't wanna fudge my new phone.
Arconaught said:
That's my next question, I'm using this guide ( http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2 ) to try and get S-Off to flash Cyanogen and I'm wondering what step to start on, assuming from your replies that I'm rooted already.
I know it's a bit of a dumb question, but I just don't wanna fudge my new phone.
Click to expand...
Click to collapse
I used the wiki method myself, those that used other methods (like Visionary) and were told to root via the wiki seem to have all just started at the beginning, from what I've read.
Sent from my HTC Vision using XDA App
Arconaught said:
That's my next question, I'm using this guide ( http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2 ) to try and get S-Off to flash Cyanogen and I'm wondering what step to start on, assuming from your replies that I'm rooted already.
I know it's a bit of a dumb question, but I just don't wanna fudge my new phone.
Click to expand...
Click to collapse
Whoa the Wiki method is completely different, looks like it was rewritten on 04/01.
You can completely ignore the temp rooting steps and concentrate on the gfree steps
From the "Necessary Files" section you need gfree, flash_image and ClockWorkMod Recovery
I would use the latest ClockWorkMod recovery rather than the one listed on the Wiki:
http://mirrorbrain.cyanogenmod.com/cm/recoveries/recovery-clockwork-3.0.2.4-vision.img (of course it's only the latest as of the time of this writing)
From step 2 you need to use:
Code:
$ adb push gfree /data/local/tmp/
$ adb push flash_image /data/local/tmp/
From step 2.a you need to use:
Code:
$ adb push recovery-clockwork-3.0.2.4-vision.img /data/local/tmp/recovery.img
Again note that the file name for CWM will depend on the version of CWM you are using.
Skip to step 4.b you need to use:
Code:
# cd /data/local/tmp
# ./gfree -f
# ./flash_image recovery recovery.img
# sync
Continue on as normal from here.
I skipped the temp root and perm root sections as you are already perm root.
I also skipped the ENG HBOOT parts, since that's not strictly necessary and the most risky part of the whole process (one mistake can result in a brick). If you want to flash the ENG HBOOT you would need to follow steps 4.a instead of 4.b, (you would also need the necessary HBOOT of course) the only command you need to omit from 4.a or 4.b is "# ./root_psn" which is the script which establishes permanent root.
Thanks a lot so far man, but I'm still stuck. I have adb, when I open it in the SDK, it flows for a bit, then closes. This is right, right? I'm meant to do all of these prompts via the cmd window?
OK, I've now sorted adb, but I can't get anything to work past that. Nothing will transfer to my phone and I'm going to kill... somebody.
Arconaught said:
OK, I've now sorted adb, but I can't get anything to work past that. Nothing will transfer to my phone and I'm going to kill... somebody.
Click to expand...
Click to collapse
You say you've sorted adb, but can you be more specific please ? What works and what doesn't work exactly ?
Ah, yeah, sorry. I got to the point where when I type in "adb devices" in the command window, it shows me my phone, with the serial number and whatnot. However, whenever i try the command:
$ adb push gfree /data/local/tmp/
It just won't work. I have all the files together in my desktop at the moment, having moved them from the downloads folder on my laptop. Is there a specific place I should have the stuff I need to send to my phone?
There is a great write up here about getting adb working. It sounds like either you didn't set up a "path" to use those commands anywhere or if you don't want to do that make sure your files are in the same folder as your adb.
Sent from my HTC Vision using XDA App
Arconaught said:
Ah, yeah, sorry. I got to the point where when I type in "adb devices" in the command window, it shows me my phone, with the serial number and whatnot. However, whenever i try the command:
$ adb push gfree /data/local/tmp/
It just won't work. I have all the files together in my desktop at the moment, having moved them from the downloads folder on my laptop. Is there a specific place I should have the stuff I need to send to my phone?
Click to expand...
Click to collapse
You need to have the files (extracted from the ZIP files you downloaded) in the same folder you run the ADB commands, if your ADB is in your path you should be able to run ADB commands from any folder.
To summarize you need to extract all the zips you downloaded under necessary files, all to the same folder. The open a command prompt and CD to that folder before you start using your adb push commands.
shortlived said:
There is a great write up here about getting adb working.
Click to expand...
Click to collapse
Yeah, steviewevie wrote it:
http://forum.xda-developers.com/showthread.php?t=865685
But it looks like he is willing to give the OP some personalized help.
Right, thanks guys, I think I'm making some progress.
ADB is all set up, and as far as I'm aware, having:
program files > android sdk > platform tools
on my path should mean I can open adb from anywhere right? I have all of the extracted files in platform tools, where adb is, in my program files... is this right, or have I completely missed the point here?
I keep getting "cannot stat 'gfree':: No such file or directory"
Sorry, I seem really stupid concerning this whole thing, but I'm sure it's something equally obvious that I'm just not seeing.
New problem. I worked out what I'd done wrong there, and got everything onto my phone. However, when trying to change the directory to /data/local/tmp, I keep getting "The system cannot find the path specified"
Now what am I doing wrong?
Arconaught said:
New problem. I worked out what I'd done wrong there, and got everything onto my phone. However, when trying to change the directory to /data/local/tmp, I keep getting "The system cannot find the path specified"
Now what am I doing wrong?
Click to expand...
Click to collapse
Remember you are running those commands (everything in that section) from an ADB shell, not from the Windows command prompt.
Excuse my ignorance, but what exactly do you mean by that? What should I do?
I created the pathways needed to open files in command prompt and set the pathways to C:\Android-sdk\tools and C:\Android-sdk\platform-tools. I have unzipped and installed everything and placed the files in the platform-tools folder, but i cannot access the files through prompt. it tells me C:\android-sdk\platform-tools is not recognized as and internal or external command. Please someone help... i havent worked with DOS since i was in high school 14+yrs ago.
So you changed your PATH environment variable to include 'C:\Android-sdk\tools' and platform-tools?
That just lets cmd run exe's from those folders regardless of where it is pointed, it will not let you access other files from those folders.
You still need to either change where cmd is pointed (using the 'cd' command) or you can move the files to where cmd is currently pointed (probably C:\Users\Username>')
-Nipqer
Still need some assistance, when starting to downgrade from gingerbread its telling me that i dont have a device detected. I have USB debugging on, so i dont know what i should do; any ideas
PvtJoker said:
Still need some assistance, when starting to downgrade from gingerbread its telling me that i dont have a device detected. I have USB debugging on, so i dont know what i should do; any ideas
Click to expand...
Click to collapse
Hello noob.
Did you install the USB drivers ( HTC Sync software )?
shared_ptr said:
Hello noob.
Did you install the USB drivers ( HTC Sync software )?
Click to expand...
Click to collapse
Im not sure if i installed the USB drivers. I installed everything that the wiki guide said to. I am gonna try again once i get home.
PvtJoker said:
Im not sure if i installed the USB drivers. I installed everything that the wiki guide said to. I am gonna try again once i get home.
Click to expand...
Click to collapse
I faced the same problem. My Windows PC didn't recognize the attached Android-device (Check Windows Device Manager).
After following the instructions as described in the following thread it suddenly worked and I could successfully root my device:
[Tutorial] Adb Driver Android 1.0 Install
Cheers
pemphix
Please help
Well i got the USB driver installed and ran adb Devices.... it picked up my phone but now when im running adb push fre3vo /data/local/tmp i get the message "cannot stat "fre3vo" no such file or directory". Am i suppose to be in C:\users\name\Android-sdk\platform-tools\ to run the adb push?
If so, need some help with command prompt. Im running windows 7,
need to either edit the path in environmental variables or make sure all the files needed and adb.exe are in the same folder and change directories to there, i have a guide to setup fastboot (and adb is the same setup for the most part) HERE
Ok, Well i got Command prompt to start working. i remembered how to path in dos but my first go round with commands didnt work so i have to try another line to exploit.. wish me luck:fingers-crossed:
I will keep that in mind.. right now im trying to get the exploit to work.. i have gone through 1 thru 3 and got nothing yet...
so you successfully downgraded to 2.2 and are now trying to temp root? maybe like the guide you are using so we know what steps 1 through 3 are and explain what isnt working if you have issues
xda wiki, cyanogen wiki and strawmetals pdf guide are simple easy and trust worthy. i hope one of these is the guide you are using
In process of downgrading
demkantor said:
so you successfully downgraded to 2.2 and are now trying to temp root? maybe like the guide you are using so we know what steps 1 through 3 are and explain what isnt working if you have issues
xda wiki, cyanogen wiki and strawmetals pdf guide are simple easy and trust worthy. i hope one of these is the guide you are using
Click to expand...
Click to collapse
I have gotten as far as "# dd if=/dev/block/mmcblk0p17 bs=1 skip=160 count=10 1.00.000.010+0 records in 10+0 records out 10 bytes transferred in 0.001 secs (10000 bytes/sec)". Now the next step is to downgrade. the command line is:
> adb push su /data/local/tmp/
> adb push busybox /data/local/tmp/
> adb push fixsu.sh /data/local/tmp/
> adb install SuperUser.apk
> adb shell chmod 755 /data/local/tmp/fixsu.sh
> adb shell /data/local/tmp/fixsu.sh
but my command prompt is still # what do i do to
skip that, thats just for temp root which is pretty unnecessary. just downgrade and move on
I know i sound really stupid, but where is the Root of my SD card??? Please dont tell me its just the card itself...
yup, dont put files in a folder is what that means
Ok, now im in Hboot, but i dont understand what im suppose to do next. How do i work bootloader to downgrade. Once in bootloader i see; fastboot, recovery, factory reset, simlock and image crc
if the PC10IMG.zip is on the root of sd card and is named properly it will do it for you, just boot into hboot and let it do its thing.
if you want to do it the fastboot way (my preference but both work fine) then follow setherios guide to do it that way
---------- Post added at 05:01 PM ---------- Previous post was at 05:00 PM ----------
oh and always check md5sums when flashing firmware, its a good habit to have
Now here is an important question. If i had to turn off my phone before the Hboot took, do i have to go thru the entire process again? or can i just do the reboot bootloader?
well i just tried to fastboot flash zip StockRom.zip and it said cannot load StockRom.zip any ideas how to get it to work??
are you using window? if so know that it may be hiding the file extentions, so pc10img.zip should be named pc10img
etc, this may be your issue other than that you will have to copy and paste your issues so I can see what you are doing and why its failing
Sent from my HTC Vision using xda premium