Related
I'm attempting to root my HTC Desire, but having some problems.
I am following the guide here: theunlockr .com /2010/06/07/how-to-root-the-htc-desire/ but I haven't made a goldcard because my device is unbranded. Perhaps this is where I went wrong?
Everything seemed to be going fine until: 7. Now on the computer double click the “step2-windows.bat” file and wait for it to finish.
The command prompt flashes briefly, but I took a screenshot and the error was 'device not found'
I'm really not sure what to do at this point..
Thanks!
Flaphal said:
I'm attempting to root my HTC Desire, but having some problems.
I am following the guide here: theunlockr .com /2010/06/07/how-to-root-the-htc-desire/ but I haven't made a goldcard because my device is unbranded. Perhaps this is where I went wrong?
Everything seemed to be going fine until: 7. Now on the computer double click the “step2-windows.bat” file and wait for it to finish.
The command prompt flashes briefly, but I took a screenshot and the error was 'device not found'
I'm really not sure what to do at this point..
Thanks!
Click to expand...
Click to collapse
Have you got HTC Sync installed? This is not a goldcard error as that would be Custom ID Error
Did step 1 complete correctly?
There is no step 2 anymore on modaco's method
try following this guide as it is the original post by Paul and all others are just copy/paste's (or bad rewritten) guides
I do have HTC Sync installed, yes.
Step1 did appear to complete correctly, but at one point I spotted the word FAILED in command prompt, but they everything continued apparently at normal.
My phone is currently at the recovery screen with the ! is it safe to pull the battery? It isn't responding to the power button.
The FAILED error was something like.. 42 device id check fail
Yeah if you are at the red triangle then you can pull the battery..
I'd use the guide on modaco. It's foolproof and very easy to follow.
Yes, it's safe to pull out battery.
I had the same problem with step 2, then I've found out the modaco method without step 2, and it worked out fine.
I would do the rooting under Linux!I had enough trouble with it under windows (maybe because of x64).
Sent from my HTC Desire using XDA App
reason for "device not found" is missing drivers for bootloader mode.
believe me, its much more easier to root your device under Linux liveCD, than cheating with drivers for windows.
good luck
The riskfree method on modaco works perfectly. I unrooted by using a stock ruu earlier to remove unrevoked, and use the riskfree method to root again. It's easy and painless on win7 64bit.
I think the step one didn't complete properly for the OP anyway as he said he seen an error at that stage.
Ok, using the riskfree modaco method now. Everything fine until installing update from SD card. E: failed to verify whole-file signature. Esignature verification failed. Installation aborted.
Is this due to not using a goldcard? I tried to make one but it kept saying it the card was damaged and needed formatting each time.
Edit. also the email I get in the goldcard creation process has the subject 'Your generated G1 goldcard' I'm not sure why it says G1? but the gold card process doesn't work and says I need to format the disk for it to be usable.
In the first posts you said your device is unbranded. So why did you made a goldcard? It's not necessary
Also make sure to use the files as you can download in the Modaco thread I posted in post #5
I think I must have misunderstood what unbranded meant. Or maybe it was just a coincidence, but it worked once I used the goldcard.
The phone came from T Mobile, but lacks and T Mobile branding on the case or any T Mobile apps.
Then it's proberly branded, you can verify by the ROM version (search the forum for it). I don't think it can harm to use a goldcard with a non-branded device anyway (correct me if i'm wrong).
Also try to download the files from the Modaco forum again (and don't rename any files)
If that doesn't work, take a look at these search results. I can remember I had the same problem as you have, dunno exactly what solved it, but these search results def. helped me
Hello xda, in accordance with the signup video I have scoured the earth looking for an answer. However I'm not sure how much necro posting is frowned upon here so I thought it would be safer to just start a new thread.
I have an HTC Desire HD from Telus(for use on the Rogers network). I am in the process of rooting it but have encountered a problem. I can gain temporary root on the terminal emulator(Because the $ turns to #) however when attempting to run clockwork flash clockworkmod recovery I get the error "An error occurred while attempting to run privileged commands!"
I get the same error when attempting the "Fix Permissions" so I'm currently at a loss of what to do.
I have the ninja superuser icon in the apps menu however when I open it the screen is blank. I am unsure if this is how it is supposed to be or not. I have seen several references to a permission box that pops up during some of the steps but I haven't seen that at all.
I've tried four separate methods, the last of which coming from this thread http://forum.xda-developers.com/showthread.php?t=954997
I am currently at step B.d which involves running the S-OFF tool and Easy Radio OFF tool. But still clockwork will not flash a backup, and when I restart the phone I can not get super user to work on the terminal (ie by typing su) and must use the rage method to regain temporary root.
Also, I don't know if this is related or not, but when I restart the phone and attempt to boot in recovery mode, the volume buttons don't allow me to select other options, and instead the phone just forces me to reboot normally.
Some more facts:
model HTC Desire HD A9191
Build # 1.32.405.6
Android 2.2
Anymore info I'm probably forgetting just ask away!
So my question is: Can anyone identify what the issue is?
Thanks much for taking the time to read my question.
Does visionary not work for you?
I've seen that alot of success has been gained by doing temp root and perm root through it?
It does sound like the rage method might not be working for you from what I can tell..
I do want to check all the steps you followed before where fine?
Sent from outer space on my DHD running beatmod gingersense v1.3
Visionary was how I rooted mine. Worth a try if you havent tried it: http://android.modaco.com/content/software/320350/19-nov-r14-visionary-one-click-root/
Thanks for the visionary suggestion, but Visionary still isn't working :/
Has visionary been tested with the Telus Desire? I heard there was a difference. What happens when I attempt to temproot is it moves to a blank screen then goes back to the menu.
When I used visionary on 1.32 it did not always work first try ... generally always worked after 2 runs. then used it to perm root
It works. You do not have Telus software in your phone anymore.
Sent from my Desire HD using Tapatalk
Try my method (I made it because the methods I found for my Telus desire HD were flaky at best and only got temproots from it.)
Since you already flashed to 1.32 start at step 2
If you want to go gingerbread, dl the 2.36.405 ruu and use that and your pc to put 2.3.3 on it (dont worry, it works fine, i was using it since it came out and built a rom based off that, kingdom, and pyramid roms for my own sense 3 rom) and use the gingerbreak method.
http://driphter.com/index.php?topic=3867.0
Still haven't managed to get root. JSLEnterprises my antivirus won't let me download your file :/
I'm at a loss for what to do.
lemonpartyz said:
Still haven't managed to get root. JSLEnterprises my antivirus won't let me download your file :/
I'm at a loss for what to do.
Click to expand...
Click to collapse
Disable your Antivirus (Avast say's its malicious), Norton or F-Prot says its clean.
and Internet Explorer 9 says its not trustworthy (because there's .bat files in the zip), Firefox says its fine.
There is no malicious code in the zip, you can edit each individual batch file in the Resource folder to see the code. Its very simple and basic.
I disabled my antivirus, but when I run Install Visionary nothing happens. The CMD window opens and says it has been succesfuly installed but nothing has been installed, and nothing appeared in the app menu.
Edit: I went into the resource folder and then followed the steps from there and everything worked, except I still don't have the # symbol in terminal (even when entering "su") and ROM manager still gives me the same error.
lemonpartyz said:
I disabled my antivirus, but when I run Install Visionary nothing happens. The CMD window opens and says it has been succesfuly installed but nothing has been installed, and nothing appeared in the app menu.
Click to expand...
Click to collapse
go into the resource folder, edit the visionary install batch in notepad, delete the "cls" line, save and exit
rerun it with the phone attached. See if it truly installed successfully.
lemonpartyz said:
I disabled my antivirus, but when I run Install Visionary nothing happens. The CMD window opens and says it has been succesfuly installed but nothing has been installed, and nothing appeared in the app menu.
Edit: I went into the resource folder and then followed the steps from there and everything worked, except I still don't have the # symbol in terminal (even when entering "su") and ROM manager still gives me the same error.
Click to expand...
Click to collapse
you dont need to use the termial in my method.
Once visionary is installed, and you run it, and everything is done exactly whats described in my 9 easy steps thread (along with outcomes along the way), then you should be perm rooted, with s-off and eng-off with supercid.
I managed to install visionary with your method, however when running Eng-S I encountered the error "Bootloader corrupt, DO NOT REBOOT! Seek help from XDA!"
Help?
Edit: Followed the advice here http://forum.xda-developers.com/showthread.php?p=14936635 and s-off worked properly this time. Hopefully my DHD won't brick on reboot. Could super user be the problem? it never asks me for permissions or anything, all I have is an icon and a blank screen when i open the app.
Edit2: Rom manager took three attempts to install correctly. Still the same result "An error occurred while attempting to run privileged commands!"
FML
lemonpartyz said:
I managed to install visionary with your method, however when running Eng-S I encountered the error "Bootloader corrupt, DO NOT REBOOT! Seek help from XDA!"
Help?
Edit: Followed the advice here http://forum.xda-developers.com/showthread.php?p=14936635 and s-off worked properly this time. Hopefully my DHD won't brick on reboot. Could super user be the problem? it never asks me for permissions or anything, all I have is an icon and a blank screen when i open the app.
Edit2: Rom manager took three attempts to install correctly. Still the same result "An error occurred while attempting to run privileged commands!"
FML
Click to expand...
Click to collapse
looks like the superuser application isnt running properly.
I would use the 1.32 ruu (not the pd98img.zip off the sd) and then from a fresh install (without resoring any data other than google account to visit the market)
run through the visionary, s-off tool, eng-off tool, and then reboot again, then install rom manager from the market, run it, it should ask you for permission and may hang for a second, and then say you have about 5 seconds to allow root permissions.
Then install rom's away. if you're not into making seperate rom specific app folders on your sd card, google JSL Er3BuS. its a sense 3 rom without the extra scripts.
How do I install the 1.32 RUU if I can't install it from the SD card?
Thanks!
lemonpartyz said:
How do I install the 1.32 RUU if I can't install it from the SD card?
Thanks!
Click to expand...
Click to collapse
It is very easy mate,
1. Download the RUU of your choice from http://shipped-roms.com/index.php?category=android&model=Ace
2. Put your phone in charge mode only with USB debug on.
3. Make sure you have HTC Sync installed on your PC, and close HTC Sync application from your system bar in windows (make sure that HTC Sync is not running as all you need is the driver)
4. Right click on the RUU file and select "Run as Administrator"
5. Connect your DHD by the USB cable to your PC.
6. Click some boxed and "next"s.
7. Waiting!
8. Profit!
I tried following the steps here http://forum.xda-developers.com/showthread.php?t=841890
But got the error "ERROR [120]: Low MAIN BATTERY POWER. When the battery is above 30%.
This is getting ridiculous lol
I'm sorry I'm such a bother.
naailalzuhir said:
It is very easy mate,
1. Download the RUU of your choice from http://shipped-roms.com/index.php?category=android&model=Ace
2. Put your phone in charge mode only with USB debug on.
3. Make sure you have HTC Sync installed on your PC, and close HTC Sync application from your system bar in windows (make sure that HTC Sync is not running as all you need is the driver)
4. Right click on the RUU file and select "Run as Administrator"
5. Connect your DHD by the USB cable to your PC.
6. Click some boxed and "next"s.
7. Waiting!
8. Profit!
Click to expand...
Click to collapse
Tried this, now the update process has taken 45 minutes.
Well, it took 5 hours to finish, but finish it finally did. Rom manager installed no problem, flashed no problem and I am in the process of installing cryogen. Thanks everyone for their help and kind words.
Fingers crossed cryogen works.
I'm going away for the weekend, but when I come back I'll update this thread with the full details of what went down so hopefully someone will be helped by my many many hours spent raging.
-Lemonpartyz
lemonpartyz said:
Well, it took 5 hours to finish, but finish it finally did. Rom manager installed no problem, flashed no problem and I am in the process of installing cryogen. Thanks everyone for their help.
Click to expand...
Click to collapse
Glad its sorted for you , and hoping it status that way...enjoy your custom roms setting your phone free
Look forward to your post letting us know how its going.
Sent from outer space on my DHD running beatmod gingersense v1.3
Marvelc Problem SolvingWe all have problems with our Marvelc, so why isn't there a guide for it? There is.
If you're having issues, check out my guide at http://teamblueridge.com/marvelc-problem-solving/ for how to fix the most common issues.
You don't have to live with a hard-to-manage Marvelc anymore.
Changelog:
May 24, 2012 10:12 PM EDT
Added a link to vbhtt's tutorial for solving different brick types.
July 19, 2012 8:04 AM EDT
Revised guide to say that all Marvelc HBOOTs can be S-OFF'd.
August 7, 2012 3:48 PM EDT
Revised to say how to fix <remote: not allowed>
Explain issues with Three-Vibe Brick
August 7, 2012 4:59 PM EDT
Link to guide on Team BlueRidge site.
Three Vibe Brick
So far, no 100% guaranteed method has been found to cure the infamous three-vibe brick. Your phone is presently in Qualcomm Diagnostics Mode
Click to expand...
Click to collapse
I have posted a tutorial to unbrick a wfs, and i also posted how to get out of the three vibe brick. I don't know if it really works (because i don't have a marvelc) but a user has reported it working.
vbhtt said:
I have posted a tutorial to unbrick a wfs, and i also posted how to get out of the three vibe brick. I don't know if it really works (because i don't have a marvelc) but a user has reported it working.
Click to expand...
Click to collapse
I apologize. I heard that in some cases, not even that could fix it. I meant to say that there is not a fix that works in 100% of scenarios (my three-vibe could not be rectified without the use of JTAG, which I did not want to get into here.)
kalaker said:
I apologize. I heard that in some cases, not even that could fix it. I meant to say that there is not a fix that works in 100% of scenarios (my three-vibe could not be rectified without the use of JTAG, which I did not want to get into here.)
Click to expand...
Click to collapse
There's no need to apologise my friend I was not trying to tell you that you are wrong, i was trying to help you!!!!
vbhtt said:
There's no need to apologise my friend I was not trying to tell you that you are wrong, i was trying to help you!!!!
Click to expand...
Click to collapse
Oh! I understand that! I was just trying to provide a common method that I had read. I understand you weren't saying I was wrong. I was actually about to add something about your tutorial, but I had another project I was working on.
Yes, my goal is that this can be a place to help most Marvelc users solve most of their problems with as many alternatives as possible while still being fairly noob-friendly.
Thank you for reminding me of your tutorial as it slipped my mind while I was writing this in the beginning!
Hi I read your thread and I can some what understand it Hopefully you can shed some light on my situation My marvelc htc wfs is stuck at the white htc screen and won't go any farther I've flashed and reflashed roms ive always formatted data and other necessary items like I should. I did flash one rom that worked but wasn't happy with it, it worked fine but was going for cm7 now that I've read at least 100 posts I come to understand its not to reliable anyway and was just wanting anything to work stock rom would be great I understand I may need to update my CWM my current version is 5.0.2.6 I've read 5.0.2.8 was more stable for the wfs but I have no clue how to flash it when I currently have no rom on my phone. this is what my hboot says currently
***unlocked***
marvelc evt1 ship s-off RL
HBOOT-1.09.0000
Microp-0354
Radio-0.94.00.0824
Hopefully the info will help you out. any help would be so grateful thanks
CoLlisiionZz said:
Hi I read your thread and I can some what understand it Hopefully you can shed some light on my situation My marvelc htc wfs is stuck at the white htc screen and won't go any farther I've flashed and reflashed roms ive always formatted data and other necessary items like I should. I did flash one rom that worked but wasn't happy with it, it worked fine but was going for cm7 now that I've read at least 100 posts I come to understand its not to reliable anyway and was just wanting anything to work stock rom would be great I understand I may need to update my CWM my current version is 5.0.2.6 I've read 5.0.2.8 was more stable for the wfs but I have no clue how to flash it when I currently have no rom on my phone. this is what my hboot says currently
***unlocked***
marvelc evt1 ship s-off RL
HBOOT-1.09.0000
Microp-0354
Radio-0.94.00.0824
Hopefully the info will help you out. any help would be so grateful thanks
Click to expand...
Click to collapse
What you need to do is download ClockWork Mod 5.0.2.8 from http://download.clockorkmod.com/recoveries/recovery-clockwork-5.0.2.8-marvelc.img and then rename it to recovery.img. If you're on Windows, put it into the same directory as your ADB and fastboot commands. Next, you'll need to put your phone in fast boot mode. Go into HBOOT and choose "Fastboot" by scrolling with the volume keys and selecting with the power key.
Connect your phone to your computer.
Next, depending on the OS of your computer, launch Command Prompt (Windows) or Terminal (Linux/Mac). Navigate to the directory with recovery.img. Now type: fastboot flash recovery recovery.img and then power off your phone when it's done.
Now boot into recovery. Go to HBOOT and choose recovery. Now, get on your computer and find a ROM that you like (something fairly stable). Download it. Find Simon's super wipe. Download it.
Connect your phone to your computer (if you removed it earlier).
In recovery, scroll to Mounts and Storage. Go to USB Connect or something similar (it will be near the bottom). Then on your computer, place your desired rom and the super wipe. Remove the phone from your computer and choose "Go back" on your phone. Go back to the main menu.
Backup.
Flash the super wipe. Then flash your ROM.
Go back to the main menu and reboot.
Sent from my NookColor using XDA
Great!! thanks this seems legit I will try this as soon as I get to my PC uhm I have windows btw and have no clue how to put the cwm into my adb / fastboot directory but I will search more about it when possible thanks for your help
Well, if you're on Windows, you should have a directory like C:\Android\ or something like that.
If you're on a Mac just do:
Code:
fastboot flash recovery /path/to/recovery.img
If you want to have the file anywhere on Windows, you still need to have fastboot somewhere and then do the same command I just typed above.
For more instructions, follow the instructions in the guide under "I can't flash a custom recovery"
Ok In your tutorial you say "go to the folder "tools" and launch "android". Download "Android SDK Platform-Tools" " when I try to launch android nothing happens only a black cmd: box will appear for a split second then goes away. The android I'm trying to launch in the tools folder is a Windows Batch File is this the correct file?
CoLlisiionZz said:
Ok In your tutorial you say "go to the folder "tools" and launch "android". Download "Android SDK Platform-Tools" " when I try to launch android nothing happens only a black cmd: box will appear for a split second then goes away. The android I'm trying to launch in the tools folder is a Windows Batch File is this the correct file?
Click to expand...
Click to collapse
Do you have Java installed? http://www.java.com/en/download/manual.jsp
Also, you should get the JDK: http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1637583.html
See if that works.
kalaker said:
Do you have Java installed? http://www.java.com/en/download/manual.jsp
Also, you should get the JDK: http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1637583.html
See if that works.
Click to expand...
Click to collapse
I downloaded java and the JDK file installed etc
Tried unzipping the sdk file again then went to the android tried to launch and same result I'm on (windows 7 64x bit).
I downloaded something when I was searching forums that kind of sounded like the file I'm suppose to be downloading the platform tools but there called android tools instead here's the files in it below
adb
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot
Do you think this is the same thing? I've flashed roms on the Optimus V before so I am a little familiar with the platform tools but when i downloaded them last time I just have to go into SDK manager.
CoLlisiionZz said:
I downloaded java and the JDK file installed etc
Tried unzipping the sdk file again then went to the android tried to launch and same result I'm on (windows 7 64x bit).
I downloaded something when I was searching forums that kind of sounded like the file I'm suppose to be downloading the platform tools but there called android tools instead here's the files in it below
adb
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot
Do you think this is the same thing? I've flashed roms on the Optimus V before so I am a little familiar with the platform tools but when i downloaded them last time I just have to go into SDK manager.
Click to expand...
Click to collapse
That's what you want. Move them into a folder at the root of your hard drive (C:\) called "Android". (C:\Android\)
Okay great!! I went ahead and tried doing some command prompts and this is what I typed
I'm in the android file it currently says
C:\Android>
I tried typing "adb reboot bootloader" and it says
*daeon not running. starting it now on port 5037 *
*daemon started successfully *
error: device not found
now my phone is connected to my PC its in fastboot mode it says in red on my phone FASTBOOT USB so I know for sure it's connected is there something wrong?
CoLlisiionZz said:
Okay great!! I went ahead and tried doing some command prompts and this is what I typed
I'm in the android file it currently says
C:\Android>
I tried typing "adb reboot bootloader" and it says
*daeon not running. starting it now on port 5037 *
*daemon started successfully *
error: device not found
now my phone is connected to my PC its in fastboot mode it says in red on my phone FASTBOOT USB so I know for sure it's connected is there something wrong?
Click to expand...
Click to collapse
You're already in the bootloader. Fastboot is the bootloader, or at least part of it. You have use fastboot commands in fastboot.
kalaker said:
You're already in the bootloader. Fastboot is the bootloader, or at least part of it. You have use fastboot commands in fastboot.
Click to expand...
Click to collapse
Okay that's what I kind of thought so I tried typing fastboot flash recovery recovery.img
and it says
error: cannot load 'recovery.img'
it is placed in the same directory as the tools are too.
---------- Post added at 06:10 PM ---------- Previous post was at 06:05 PM ----------
Okay nvm I tried something and it worked!!!
I went and re downloaded your CWM on your tutorial and deleted the one I renamed and didn't rename it this time just kept it the way it was I then tried flashing it and success I'm now going to reboot my hboot and see if it worked but also I was searching forums and google but could not come across simmons super wipe... I will keep looking though but if you have time maybe throw a link on a post for me but thanks for helping me I hope it goes smooth from now on
CoLlisiionZz said:
Okay that's what I kind of thought so I tried typing I was searching forums and google but could not come across simmons super wipe... I will keep looking though but if you have time maybe throw a link on a post for me but thanks for helping me I hope it goes smooth from now on
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1598143
I'm glad to hear you got it working!
A thought just occured that I may have overlooked in my many (unsuccessful) attempts of curing a sent-to-me 3 vibe...
Correct me if I'm wrong on this, but sd needs to be made a goldcard; so that PG76IMG.zip will auto-load...
Been a long time since I attempted but I don't remember if I checked the sd to make sure it was goldcard'd. I will go charge it up and test this new theory tomorrow (still sitting in a side-basket at work). Sometimes my mind takes a minute to put ALL the pieces together
Rob
Sent from my Marvelc using Tapatalk 2
insink71 said:
A thought just occured that I may have overlooked in my many (unsuccessful) attempts of curing a sent-to-me 3 vibe...
Correct me if I'm wrong on this, but sd needs to be made a goldcard; so that PG76IMG.zip will auto-load...
Been a long time since I attempted but I don't remember if I checked the sd to make sure it was goldcard'd. I will go charge it up and test this new theory tomorrow (still sitting in a side-basket at work). Sometimes my mind takes a minute to put ALL the pieces together
Rob
Sent from my Marvelc using Tapatalk 2
Click to expand...
Click to collapse
Right, a Goldcard (unless one is S-OFF or ENG) will be required. However, achieving a goldcard requires ADB access to your phone. (The Simple GoldCard tool reads a file in /proc/*/*/ I believe to get the CID required for goldcard.) Now, ADB access is quite difficult with a bricked phone as you cannot boot into Android (or recovery) and to get S-OFF you would need to borrow the HTC Wildfire S (it MUST be a Wildfire S) to get the goldcard required.
Even with what I just said, depending on how bad your phone is bricked (Flashing a GSM RUU, for example), you may have a 100% bricked radio, thus resulting in an entirely bricked HBOOT not allowing you flash a PG76IMG.zip.
Another idea I have is that the Marvel is a PG761**** for the model number, and an incorrect RUU is the most common brick for Marvelc. What may be an issue is that the Marvelc is a PG762**** model number. The current files we have for un-bricking are Marvelc, but the android-info.txt for modelid says PG762000, therefore a GSM HBOOT (especially a locked, RUU HBOOT) would not take that file as it is for Marvelc.
What I think would be necessary is: a goldcard + a PG76IMG.zip with a GSM android-info.txt, but Marvelc radio, ROM, HBOOT, etc.
This is my idea on how we may need to do this. However, as the GSM HBOOT cannot get S-OFF without XTC-Clip which we can't use due to a lack of SIM card slot.
To get a 100% working-in-all-methods 3-Vibe Brick Recovery Method, we are waiting for the people in the S-OFF thread to get a full software S-OFF. However, even with that, we may still have issues...
I have spent a lot of time thinking about this, actually. (I'm a planner; not a dev :crying: so I can't be of much help with the dev part.) However, if it ever becomes a Team BlueRidge project to fix this type of brick (or a project by any group) I will be happy to plan (but not test just yet).
Since now we're moving into a very difficult and not-so-noob-friendly as I am intending for this thread to be, it may be a good idea to either start a new brainstorming thread or to PM or IRC or something.
Anyway, those are my thoughts.
I tried posting to the relevant thread on xda but I don't have enough posts. Anyway, I uninstalled the default drivers and installed the drivers from the toolkit but Windows keeps trying to reinstall the default drivers. I end up with the phone showing up under "Portable Devices" as "SAMSUNG-SGH-I747" and under a new section "SAMSUNG Android Phone" as "SAMSUNG Android ADB Interface". Not sure if that's how it should be or not, but the toolkit does show a code and "device" at the top of the main menu...
The first time I ran the ALLINONE rooting option I got some errors during the verification steps related to "su" not being found (it went away before I could get a screenshot). I rebooted the pc and the phone and tried again and got a java IllegalStateException saying "Cannot broadcast before boot is completed"
I tried it a third time and got a couple errors saying that it failed to restore the recovery files ("No such file or directory"). The next step failed when trying to push Busybox to my phone ("error: device not found").
USB Debugging was enabled. Any idea what on Earth I'm doing wrong?!
Edit: It appears CWM was installed and I can get into it but there's no SuperUser app in my app drawer...
I guess my first question would be what version of the SG3 do you have, as the very first line of his post says "IMPORTANT: DO NOT USE THIS TOOLKIT TO ROOT OR FLASH CUSTOM RECOVERY ON A SNAPDRAGON MODEL SGS3 AS THE INCLUDED IMAGES WILL NOT WORK ON IT". If you go to you settings>about phone>hardware it will tell you if you have the qualcomm snapdragon CPU.
dntesinfrno said:
I guess my first question would be what version of the SG3 do you have, as the very first line of his post says "IMPORTANT: DO NOT USE THIS TOOLKIT TO ROOT OR FLASH CUSTOM RECOVERY ON A SNAPDRAGON MODEL SGS3 AS THE INCLUDED IMAGES WILL NOT WORK ON IT". If you go to you settings>about phone>hardware it will tell you if you have the qualcomm snapdragon CPU.
Click to expand...
Click to collapse
I have the Snapdragon version of the toolkit referenced here: http://forum.xda-developers.com/showthread.php?t=1746665
I see, i'm downloading the file's now to take a look but just reading the post i can tell you the recoveries in this package are outdated, not to say they wont work but there are significant changes between those and the current versions.
*Edit* - You said CWM did install but the SU app did not, do you by chance have root access as well? Just shooting in the dark here but if so you can simply download the SU app from the market and go about your merry way. If not I would suggest just using odin to flash the approtiate stock rooted rom from THIS THREAD which also includes the SU app (if i recall from when i last used it). After looking through the packaged files the toolkit includes odin which is used to flash a root inject stock rom based on your selection as to which device you select. Not knowing how this executable handles unexpected errors i would simply run odin manually from the toolkit folder and make sure it is recognizing your device properly using this guide which also includes a link to the samsung usb drivers. I don't know how these drivers in the toolkit compare to the linked drivers on the odin thread but would install those just to be sure its not a driver issue. Also another thing to check would be to make sure you are using the usb micro cable that came with your GS3 as many people have had flashing issues using other cables.
I had a problem when entering the command promts, on the first computer I tried. I would freeze the computer. After switching to a new computer everything worked okay, except I couldn't flash the last radio zip. Nevertheless I was able able to complete the process and use revolutionary. Got MROM installed and everything appears to be working fine. No idea why my computer was freezing during the tacoroot process.
Windows OS running - HTC drivers properly installed ?? Antivirus & firewall temporary disabled (as it could be blocking access) ??
Check MD5's for the various files downloaded ? Usin the OEM micro-usb cable or generic (unlikely, but just check to eliminate it) and try using a different usb port to run the installation? Outdated Android toolkits/adb loaded & need to be renewed to latest ones?
More specifics would help - any error or pop-up messages or logs ??
(BTW, I just used tacoroot earlier this week to "rescue" a semi-bricked DI2 after RUU, rooted it again (adb - manually) with S-Off and the device is good as new, back on a custom Sense rom again after calling into VZW first (complicated story ...)
You don't flash the radio. you put the file on your sd card with a specific name, can't recall it but lots of references to it, you'll find it no problem, and then you go into the bootloader. It'll automatically install the new radio. don't forget to wipe, and change the file name.
Jasonp0 said:
You don't flash the radio. you put the file on your sd card with a specific name, can't recall it but lots of references to it, you'll find it no problem, and then you go into the bootloader. It'll automatically install the new radio. don't forget to wipe, and change the file name.
Click to expand...
Click to collapse
PG32IMG.zip is what it needs to be named, and when he says wipe you need to wipe dalvik cache and cache... o yeah, and after your done and booted hp make sure to use a file manager and delete the file off your sd card or it will try to keep reinstalling it
Sent from my Incredible 2 using xda app-developers app