Develop Bugs

Unrevoked 3.21 need Help

Could someone please help.
I am trying to root using the Unrevoked Beta 3.21 to root my phone. I get to the end in Unrevoked and it states "failed to flash recovery image"
This is what I have done:
1. Installed all drivers - Device manager does stat ADB Interface just like the guide states.
2. Installed the Relfash packgage
3. Phone is in "debbuging mode"
4. Charge Only is selected
5. Using Windows xp
One strange thing that I do notice is that when the Unrevoked program tells you to select the Hboot usb on my phone and when I do so it flashes blue or green wording that says "no Image" when it looks like its trying to load an image. Afterwards the phone goes into the reboot phase and then states "Failed to flash recovery image". Help is much appreciated.

drivers
i'd mak esure you have everything else uninstalled, every doubletwist, htc software and drivers get it all off, then reboot install unrevoked drivers, then 3.21
thats what i did last night, and it worked.

dguidry12 said:
Could someone please help.
I am trying to root using the Unrevoked Beta 3.21 to root my phone. I get to the end in Unrevoked and it states "failed to flash recovery image"
This is what I have done:
1. Installed all drivers - Device manager does stat ADB Interface just like the guide states.
2. Installed the Relfash packgage
3. Phone is in "debbuging mode"
4. Charge Only is selected
5. Using Windows xp
One strange thing that I do notice is that when the Unrevoked program tells you to select the Hboot usb on my phone and when I do so it flashes blue or green wording that says "no Image" when it looks like its trying to load an image. Afterwards the phone goes into the reboot phase and then states "Failed to flash recovery image". Help is much appreciated.
Click to expand...
Click to collapse
Uninstall HTC Sync if you have it installed.

Hey folks thanks for the help you all gave. I finally got it to work last night. What I did was unistalled everything that I had downloaded and started fresh from the beginning of the directions. It was all good after and worked flawless. Now im moving on to see what "root" actually is and how it benefits me.
Thanks,

dguidry12 said:
Could someone please help.
I am trying to root using the Unrevoked Beta 3.21 to root my phone. I get to the end in Unrevoked and it states "failed to flash recovery image"
This is what I have done:
1. Installed all drivers - Device manager does stat ADB Interface just like the guide states.
2. Installed the Relfash packgage
3. Phone is in "debbuging mode"
4. Charge Only is selected
5. Using Windows xp
One strange thing that I do notice is that when the Unrevoked program tells you to select the Hboot usb on my phone and when I do so it flashes blue or green wording that says "no Image" when it looks like its trying to load an image. Afterwards the phone goes into the reboot phase and then states "Failed to flash recovery image". Help is much appreciated.
Click to expand...
Click to collapse
I have a similar problem, I down loaded from IRC and few others on other thread tried them all and I get the same results. in the flash it says killing adb bug then waiting for device debug usb and stays that way. what am I doing wrong I deleted everything HTC, drivers ect. I used usb tethering on pdanet to get everything do I delete that as well? is there a more precise guide in detail from start to finish for noob as there is one for the 1.26.561.6 version.
thanks

hi guys
i just upgraded to 2.2
i also followed everything. but whenever i start 3.21 , it will not detect my htc desire. im using windows 7.
i never installed sync programs etc. evrytime i plugged in my phone to 3.21, i can see the yellow ! ADB. is it normal? and can u guys help unrevoked my phone. thank you guys.

evo help please
I'm currently trying to root my Evo for the first time and as afar as the software goes i downloaded everything that i needed to when i comes time to go to the device manager i cant find the Android 1.0 in other devices i followed the guide to the letter but it still wont show up does anyone know why??????? and what do i need to do to get it to show....(android usb devices shows up when it's plugged in from usb and when i click the drop down it just says my HTC if that helps any i'm also using windows xp...)

[Q] Inc not recognized by ADB on Mac

Hey all,
My Incredible won't be recognized by ADB on my Mac through the terminal. I type in "adb devices" and it returns "List of connected devices" but doesn't actually list anything. If I try something like "adb shell" it says "error: no devices connected". What could the issue be?? I have a PC as well and ADB works fine on the PC.
If it helps at all the phone is recognized through fastboot on my Mac but I can't perform any operations... I tried to flash a new recovery through fastboot and when I tried to do "fastboot erase recovery" it returned something like "erase recovery failed status malformed"...
Thanks!

debug turned on? Thought that it needed to be adb

Yeah debug is on.... also in case it didn't go without saying I'm rooted.
Hope someone can help with this!
Sent from my ADR6300 using XDA Premium App

Anyone have any ideas on this one?

Go here and follow steps for your system.....
http://androidsamurai.com/forum/viewtopic.php?f=12&t=4&sid=e1f4ce4f9ba69613dca7ba5db4a711a2
if I helped please don't hesitate to hit the thanks button
Sent from my Incredible using XDA App

Thanks for the advice, but I had already followed those directions when installing the SDK. As I said, the phone is recognized just fine on a Windows machine so I can only assume it's some setting that's perhaps incorrect on my Mac? Maybe in System Prefs?
I dunno. It isn't the biggest deal but it'd be nice to be able to use the ADB on my Mac without needing to boot up the PC. Thanks!

nufan947 said:
Thanks for the advice, but I had already followed those directions when installing the SDK. As I said, the phone is recognized just fine on a Windows machine so I can only assume it's some setting that's perhaps incorrect on my Mac? Maybe in System Prefs?
I dunno. It isn't the biggest deal but it'd be nice to be able to use the ADB on my Mac without needing to boot up the PC. Thanks!
Click to expand...
Click to collapse
Are you positive your path is correct..... and if it is check and make sure there are no spaces or weird characters....
Sent from my Incredible using XDA App

was it working before and it stopped working? I noticed that my Mac doesn't recognized the phone every once in a while with CM7 and the Incredikernel. I have to unplug it and plug it back in couple times to get it to register.

newtoroot said:
Are you positive your path is correct..... and if it is check and make sure there are no spaces or weird characters....
Click to expand...
Click to collapse
I'm pretty sure it's correct because the Terminal recognizes the "adb" commands as valid. For example, I can run "adb shell" and it returns "error:device not found". So I don't think that's the issue...
Grooby97 said:
was it working before and it stopped working? I noticed that my Mac doesn't recognized the phone every once in a while with CM7 and the Incredikernel. I have to unplug it and plug it back in couple times to get it to register.
Click to expand...
Click to collapse
The thing is, the computer recognizes the phone just fine. I can plug it in and select "disk drive" and both the phone and SD card mount without an problem. But when I try to run adb commands that's when it doesn't seem to see it for some reason.... I really don't get why this could be, when without changing a single setting on the phone it works fine on a PC. I'm probably missing something obvious, but I don't know what that might be.....

nufan947 said:
I'm pretty sure it's correct because the Terminal recognizes the "adb" commands as valid. For example, I can run "adb shell" and it returns "error:device not found". So I don't think that's the issue...
The thing is, the computer recognizes the phone just fine. I can plug it in and select "disk drive" and both the phone and SD card mount without an problem. But when I try to run adb commands that's when it doesn't seem to see it for some reason.... I really don't get why this could be, when without changing a single setting on the phone it works fine on a PC. I'm probably missing something obvious, but I don't know what that might be.....
Click to expand...
Click to collapse
forgive me if im asking a dumb question im just trying to help you narrow down your problem,,,,,, did you check and make sure usb debugging is checked? and if you type adb devices what does it say? ive noticed on the newer sdk that i installed they moved adb to platform tools and out of tools so you might check those things

Yeah, USB debugging is checked... when I type "adb devices" I get "List of devices attached" and it doesn't actually list anything. And yeah, the Terminal is definitely pointing to the right folder, I don't think I'd be getting any sort of response if it was pointing towards the wrong place, right?
ADB definitely works. It just doesn't like my phone for some reason

Well it definitely works on OS X 10.6 that's what my laptop uses. Have you tried parallels or bootcamping into a version of Windows? My work iMac is a piece of dirt and does not like adb thru mac os x but works fine with win xp on parallels.

Yeah, I'm running 10.6 on my laptop as well... right now for when I want to use ADB I've just been running XP on my bootcamp partition, which works fine. It's not the worst solution in the world, but I'd prefer being able to do it on the Mac side of things, which is where I spend far more time.
This is very mysterious....

[Q] How do I fix the "device not found" error?

I'm trying to return back to stock using this method for mac. I rooted it on my mac, so I know it's possible. But this time around, when I go to run the wizard I get "error: device not found" messages each time.
1. Android File Transfer boots up when I plug in my nexus, so I know the computer recognizes it to some extent.
2. I AM using the original USB cable.
3. I have tried using both USB ports on my macbook pro.
4. USB debugging is on (and has been since I first rooted my phone).
Stumped, and I've searched many places for help, but I can't get past the 'not found' message. HELP.
(Thanks)

Are you on a custom ROM? If the ROM has a fast charge option, disable that first and then connect.

I'm using MoDaCo's 4.0.4 ... I'm not aware of any fast charge option.

[Q] Bricked Verizon Gnex. Need assistance

My Verizon Galaxy Nexus is bricked. I was having issues with it receiving mobile network signal, so by using TWRP, i factory reset and in the process decided to swipe the internal space. (my first big mistake). I lost all my images, custom roms, gapps, files.
I was unable to boot the phone and decided to use the trusty ODIN back to stock. ...I've done this previously without any issues. I downloaded all the factory 4.0.4 images and attempted many times. I can't remember all the fancy lingo but I believe it continued to get stuck at "NAND write." I was also having troubles with my phone reading "fastboot error" while at the green android screen. It reads "fastboot command read error- 2147483647"
When I tried using wugfresh's gnex tool kit I was able to flash Boot, Bootloader, Radio, Recovery ... but not system. Gave me the ADB error. I'm currently unable to install the adb drivers ... or they're not being recognized because I can't boot my device and select development options.
The "1-click 4.0.4 back to stock toolkit" shows red circles for both fastboot and adb. I'm completely lost .... and frustrated at this point.
I used the "galaxy nexus toolkit" and when it executes it writes everything but also says FAILED at the end of every line. At this point I feel my two biggest issues are ADB driver so my phone's not recognized .... also something to do with the partition on the internal sd. I don't think these programs know where to write the data on my phone...........
This go around, I'm unsure what happened but I'm left with the phone, Yellow Triangle! and computer monitor icon. I was able to odin a file called "u1_02_20110310_emmc_EXT4.pit" (unsure how or where I came up with this file...) which PASSED and the phone reboots back to the green android icon screen.
I've tried many ODIN versions, three different usb cables and three computers, with all ports. I'm still getting hung up with PDA and PHONE files when trying to odin back to stock. The device shows up on ODIN and the files are reading ... it just gets hung up like the pc can't communicate with the phone.
I'm sorry for not having the language to express in detail what I'm enduring. I will be receiving a replacement device in the mail tomorrow and hoping I can connect it to the PC and hopefully have the driver's install properly.
Any and all help would be appreciated.

I am able to boot into ODIN mode and also the screen with green android with chest open. It reads in red letters "no revocery or boot img"
The device is still in locked status.
...sure hope this passes the brief Verizon inspection.

My tool failed you? I have other ideas. Pm me
Sent from my Galaxy Nexus using xda app-developers app

vabeachfc3s said:
My tool failed you? I have other ideas. Pm me
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I'm sorry, I tried but your profile only shows skype chat. I'm really unsure how to PM through these forums.
I was able to keep bootloader unlocked and attempted everything once more. I have no ADB access due to the phone not being able to power on and select development tools option.
Fastboot fails on everything primarily due to "partition" issues. .......... I locked the bootloader and boxed it up "as is"

[Q] One click root issues.

Hi there, I've recently tried rooting my lgg3 but im running into a few problems.
Just to clarify:
I've installed the drivers
Enabled USB de-bugging
Used task manager to end abd.
Tried MTP and PTP
But when ever I run the Oneclick root, it failes to start abd, then fails daemon, and then 'successfully' starts demon only to fail it again. It does this about 3 times before re-booting the phone into download mode.
From there, it asks me to wait for SuperSU to install, which it never does.
I'm really stuck here and could use any help. I've also tried using the GUI and .bat rooting tools, the .bat gets further into it than the actual, updated GUI, rebooting the phone, whereas the gui fails at the start as it cant start abd nor daemon.

For starters, please update with:
Your variant (model number)
Current Android software version
Which one-click root tool you are trying to use
The output from 'adb devices' entered into ADB