yashsingh1/xdaforums huggingface dataset:
[Droid Incredible Android Development] contagous:
... When I was looking around I couldn't find anything saying these was bad :(, I have a nandroid backup from before I did it, so Should be able to get back if any probs...

Every time I've looked around I saw lots of people say these was ok, although its been around a week since I last checked around, I had everything saved in a Notepad document ready...

What you think I should notice? and should I go back? I thought removing those app's was fine.....

is it not?...

Can you point me to some of those links saying its bad? cos All i find are people saying they removed lots...

I never used any of these apps, what would they impact?

another note...

Managed to get wifi tethering working thanks to finally finding the unrevoked page about it again.

*edit*

also on Clockwork 2.5 now
[Droid Incredible Android Development] thatdudebutch:
Is there a changelog for the new recovery? Just wondering if I need to bother with this right now, as I'm on original root and recovery.
[Droid Incredible Android Development] contagous:
I think its on 1st page, and its to do with fixing the bug they found with communication on windows...

So easy to do tho, figured i'd stay upto date
[Droid Incredible Android Development] obsidianblackhawk:
I'm not sure if this helps at all with the communication error people are receiving, but i found that if i uninstalled the drivers and then reinstalled the drivers again, using the ones that come with unrEVOked3, that i no longer have this issue and am able to repeatedly run the process without fault after that.
[Droid Incredible Android Development] thejosher:
This was the most painless root/jailbreak I've ever experienced :D Thanks UnrEVOked team :D
[Droid Incredible Android Development] contagous:
Dude explain please, cos I haven't seen anything around... U got me a little worried...

I only use Gmail contacts on my phone, and never use twitter or FriendStream or htc mail, so what can i break by removing these?
[Droid Incredible Android Development] heffe2001:
Is anybody else having problems with the 2.5 clockworkmod? It's telling me that it failed to mount both the /data and /cache folders:

Can't Mount /dev/block/mmcblk0p2 (File exists)

Can't mount CACHE:recovery/command

Can't mount /dev/block/mmcblk0p2 (File exists)

Can't mount CACHE:recovery/log

Can't mount /dev/block/mmcblk0p2 (File exists)

I'm wondering if somehow the clockworkmod linked earlier was for a different phone, and now I'm stuck with a recovery that doesn't, and a phone that won't boot (I can get into recovery though, just can't wipe the data or cache folders, and it won't complete a rom install, fails writing to /data).

Definitely a bad nand/flash in this phone, got it reflashed back to stock, no clockwork, etc, and it still won't boot. I was getting bad block errors in the dmesg log files, so I'm guessing I'll be heading back to the verizon store shortly and will have to wait ANOTHER friggin month.
[Droid Incredible Android Development] jdmba:
Heres one

There is definitely more than just these threads, but its a good start:

http://xdaforums.com/showthread.php?t=701589

http://xdaforums.com/showthread.php?t=710009
[Droid Incredible Android Development] contagous:
Thanks but after reading those, I still don't see any major problems...

My Accounts & Sync runs fine, ain't getting any FC's and like I said, I only use Gmail contacts and have never not once used FriendStream or any of the apps I removed... So no sync was set up for any of them...

I guess i'll post back if I see any errors, but haven't seen anything as of yet, and I've tested everything I do on my phone as everyday thing, seems to all be working.

Thanks for the info tho, kinda scared me, but after reading those posts, feel a

bit better...
[Droid Incredible Android Development] droidyourlookingfor:
Hi i am trying to root my dinc using a ubuntu live cd on my powerbook and when i try to run reflash i get the error " ./reflash: 1: Syntax error: "(" unexpected "

Anybody know what to do? Thanks in advance I'm new to ubuntu btw.
[Droid Incredible Android Development] jdmba:
Huh?

While I am unfamliar with your issue (and certainly wish you luck), I am somewhat perplexed that on page 11 of a thread which has its fair share of "it worked; thanks" you would posit that the link was for the wrong phone ... unless you don't have an Incredible, that is.

At any rate, I suggest redownloading everything from a different browser to ensure you didn't get a bad download, and try again.
[Droid Incredible Android Development] heffe2001:
I asked mainly because I had a lockup, then the phone went into a boot loop shortly after installing the 2.5v of clockworkmod. Thought somehow the version I pulled down had an issue (it's possible my download was corrupted). Ends up that the problem is a faulty nand flash chip, gets bad block errors on a format. Reflashed the phone with the factory image, and STILL couldn't get it to work (but it covered the fact that I had rooted & had the recovery image on it). I'm getting shipped a FRU unit by Monday, so hopefully I'll be back in business shortly.
[Droid Incredible Android Development] trillonometry:
so when they say added support for droid eris they really mean?????

because I get "communications with phone unexpectedly interrupted" every single time
[Droid Incredible Android Development] najaboy:
www.twitter.com/unrevoked
[Droid Incredible Android Development] NancyKV:
Communication Error

Everyone who is having the communication error, just make sure you remove the HTC drivers on your PC that came with the phone. You also want to make sure you remove HTC Sync. Once you do both, you'll be able to finish up in less than 5 minutes. Even tho the unrEVOked team said that they're working on the issue, this is all that is needed.
[Droid Incredible Android Development] baram:
It's actually an issue more with windows itself. Uninstalling that does help some hanging but the "communications error" when it tries to reboot into recovery isn't solved by that, typically.
[Droid Incredible Android Development] c24vkrayzie:
If I download this will I be able to update it if sprint sends another ota update? I'm just wondering if it does any damage to my evo
[Droid Incredible Android Development] Hatman41:
Unrevoked v3.1 is out http://www.unrevoked.com/recovery/

v3.1:

Fixed “Communications with phone unexpectedly interrupted.” error occurring on Windows version.

Updated to ClockworkMod Recovery 2.5.0.1

Program sets su permissions even when su is present.

***EDIT***

Well this is incorrect. The communications with the phone Communications with phone unexpectedly interrupted is still happening when trying to send the flasher to a HTC ERIS
[Droid Incredible Android Development] jdmba:
V3.1 Released

unrEVOked released v3.1 to solve the communications and superuser issues; first post updated.
[Droid Incredible Android Development] Hatman41:
The communications with the phone Communications with phone unexpectedly interrupted is still happening when trying to send the flasher to a HTC ERIS
[Droid Incredible Android Development] Shadowmite:
we need you to tell us exactly what messages come up before this. eris support is still fairly new but it should work...
[Droid Incredible Android Development] Hatman41:
I plug the phone in...launch the software...it says pushing image...then it says pushing flasher...and then I get that communications error.
[Droid Incredible Android Development] shoman24v:
Got the 2.5 clockwork pushed. Thanks guys.
[Droid Incredible Android Development] Shadowmite:
Hmm, make sure you don't have any htc software running on the pc, or any software that connects to the phone at all. If in doubt, uninstall it. Windows is VERY picky about it's devices and drivers. Make sure you have installed OUR driver (via the html file included in the release).

That is a completely different spot in the code for a communications issue, but in general, the issue is due to something interrupting communications with the phone to our program. We talk via a secondary protocol to it, so anything else will cause problems. Even if it's just a music program trying to check the phones drives for music it'll kill it. Make sure you are choose charge only. Follow the advice listed in post 1 of the reflash tool release if you can.
[Droid Incredible Android Development] SoccerCore11:
I used this to flash my incredible, worked fantastically. Unplugged the incredible, plugged in my Eris, and I get the communications error before it even reboots. Eris was on charge only. It is not pre-rooted.
[Droid Incredible Android Development] Hatman41:
I used this progam fine with my INC but when I plug in the ERIS I get to the part were it pushes the flasher and then get the communication error. The ERIS is in charge only.
[Droid Incredible Android Development] whitezombie:
Having Trouble Using unrEVOked

Phone: 1st generation HTC EVO 4G

1. installed the windows driver (worked fine)

2. enabled debugging mode, and always stay powered-on

3. ran unrEVOked

4. plugged USB cable in

5. unrEVOked rebooted my phone

6. selected the BOOT thingy with down arrow and power button

7. noticed from a scroller on the screen said "No Image" like 4 times

8. it reboot my phone

9. phone loaded normal, unrEVOked says "Flashing recovery image. Do not touch your phone!"

it's been stuck on this screen on the unrEVOked program for 10 minutes now and my phone is sitting on the normal home screen.

Am I doing something wrong?
[Droid Incredible Android Development] bhazard451:
There was no need to touch your phone and select BOOT. It does it automatically (for my incredible anyway)
[Droid Incredible Android Development] whitezombie:
The instructions on the unrEVOked say

"Press volume down to "HBOOT USB", then press the power button"

I followed the instructions per the GUI.
[Droid Incredible Android Development] Shadowmite:
For those having issues with comm errors, just in general and would like some more verbose output, please replace reflash.exe with:

http://www.shadowmite.com/temp/reflash_debug.exe

Obviously this only applies to windows and the current 3.1 release. Please post pastebin links to your output and we can try to help based on where the issue is. Note you MUST run this from the same folder the other package extracted to. This is only the executable.
[Droid Incredible Android Development] whitezombie:
stuck at:

"DEBUG: Pushing recovery image."
[Droid Incredible Android Development] :
Man, would love this for my HTC Magic 32A.

Thanks for the tool anyway.
[Droid Incredible Android Development] whitezombie:
Stuck at ...

http : // img130.imageshack.us/img130/523/statgp.jpg
[Droid Incredible Android Development] whitezombie:
Pc36diag.zip?

When going through the HBOOT USB step, selecting this option scrolls:

"SD Checking ..."

pc36diag.zip --- Not Found

pc36diag.nbh --- Not Found
[Droid Incredible Android Development] Hatman41:
Shadowmite here is the info.

unrEVOked recovery reflash tool

git 7bb95e5

DEBUG: Killing any existing adb daemons...

DEBUG: The adb service is not running.

DEBUG: Waiting for device. Plug phone in now and enable USB debugging.

DEBUG: Found a Droid Eris.

DEBUG: Pushing recovery image.

DEBUG: Pushing flasher...

DEBUG: Waiting for reboot...

rawadb_open: remote closed the connection looking for target "reboot"

DEBUG: Communications with phone unexpectedly interrupted. Try again.

I am doing this on the same PC as I use for my Dinc and it works fine on my Dinc. On the ERIS I have charge only selected and I do have debugging checked.
[Droid Incredible Android Development] nathan_barstow14:
Mine does the exact same thing. I have ran the v3.1 reflash several times. Help would be appreciated
[Droid Incredible Android Development] altpersona:
im going out on a dumbass limb here....

iv got a

sprint hero

2.1-update 1

baseband 2.42.01.04.27

build/software 2.27.651.6

on an xp pc i uninstalled the htc drivers and sync

installed the hboot drivers

installed the unrevoked.apk on the phone

ran the apk, it took a minute and said 'done'.

a. did it work, could it have worked?

b. how do i know if it worked.

if it did not work, but could have, what would i have done wrong?

if it did not work, but could not have worked, well, dang it. i didnt see anything saying i was wasting my time..
[Droid Incredible Android Development] Mr. Spontaneous:
You're not supposed to use the apk. The apk was the original EVO root method.

Go to the unrevoked page and download the tool for your OS and follow the instructions provided.
[Droid Incredible Android Development] Mr. Spontaneous:
So, I sucessfully rooted and reflashed using the 3.0 tool, and now 3.1 is out. I know they say that we don't need to run 3.1, but is it worth doing so just for Clockwork 2.5? Or is there another method one should use to upgrade clockwork?
[Droid Incredible Android Development] altpersona:
i did this

unrevoked. /recovery

got reflash_package.exe

extracted contents.

followed this : hboot driver.

i get the device manager : android phone part.

when i restart the phone that goes away, and moves the phone to disk drives.

i run reflash and it never finds the device.
[Droid Incredible Android Development] Mr. Spontaneous:
Have you tried running the reflash and then plugging the phone in? Be sure you have debug mode enabled on your phone (Settings > Applications > Development > Enable USB debugging)
[Droid Incredible Android Development] altpersona:
rebooted xp system, just to clear its head...

ran reflash

plugged in phone w/ debug enable

waiting for device...

rechecked device manager, no entry for phone at all. reinstalling driver,

vol down + power..

vol up fast boot

add hardware android bootloader

device manager > android bootloader > device cannot start (code 10)

restart phone w/ menu button

reflasher waiting for device

tried many combinations of plugging the phone it, running reflasher
[Droid Incredible Android Development] Mr. Spontaneous:
Stupid question: does the tool work on XP? There may be a driver issue...
[Droid Incredible Android Development] altpersona:
if i thought i would have better luck on my linux machines i would do that in a heart beat, but most 'easy' hacks work better on xp.. :rolleyes:
[Droid Incredible Android Development] altpersona:
for giggles i tried it on my ubuntu box

sudo ./reflash

terminal: unrEVOked recovery reflash tool

git 7bb95e5

reflash: Device "heroc" is not supported at this time.
[Droid Incredible Android Development] Shadowmite:
honestly these work far better on mac/linux. Those are our native platforms. windows was included for the masses, but the driver interface layer adds complexity that seems to have weird bugs. Not to mention the sync apps that run on windows. If you have the means, use the linux release. it should be near flawless. Just remember to run as root!

oh, but yes, heroc is not a supported platform. It has a seperate program to root it based on the hstools exploit. Goto unrevoked.com and click on the hero...
[Droid Incredible Android Development] altpersona:
thats what i did first, it gave me unrevoked.apk

i installed it, installed drivers, ran the app, it said done, and thats where i am.. but i dont think it took.
[Droid Incredible Android Development] Shadowmite:
if you adb shell and run su do you get root or prompted on phone for superuser?
[Droid Incredible Android Development] Hatman41:
I do not have access to a Linux box. The owner of the phone does have a Mac and he tried it on his Mac and had the same problem.
[Droid Incredible Android Development] altpersona:
~/ sdk/sdk/tools/sudo ./adb shell

makes likes it running, but is just a blank line.

i type su, and it prompts for password
[Droid Incredible Android Development] Mr. Spontaneous:
Wait, you're not using an Incredible? That's why.

Note, this is a Droid Incredible forum, if you're using otherwise (and need to post here), mention the handset difference!
[Droid Incredible Android Development] altpersona:
yip, not incredible, was pointed here...
[Droid Incredible Android Development] killer2239:
Ok.... so interesting enough regarding people still showing latest version as 2.0.2.1

If you use 3.1, youll notice the recovery screen it leaves you at is 2.5.0.1 , so you reboot and if you go to rom manager after reboot it shows 2.0.2.1 as installed and current version. If you do boot to recovery it says version 2.0.2.1. BUT.... if you power off the phone. And hold volume down and turn the phone on into recovery, it gives you version 2.5.0.1

Anyone else have the same issue?
[Droid Incredible Android Development] mrchambo:
Yep, what you said. Same thing for me...

JC
[Droid Incredible Android Development] TNS201:
Rom manager probably tried to flash your recovery, it cannot do so due to nand lock still. It will appear you wrote it after the reboot, and say the other recovery, but when you reboot your phone again it will be the correct version.
[Droid Incredible Android Development] Shadowmite:
I'm sorry, this really screams that you need to learn more linux! Try:

sudo ~/sdk/sdk/tools/adb shell (guessing at your path based on your previous entry)
[Droid Incredible Android Development] killer2239:
Viewing through rom manager says 2.0.2.1 and if you boot the phone up with volume down and power it says 2.5.0.1, So which is the correct version? When i first rooted the phone i did it a week ago, with the 10minute root video and the video the same person made about NAND to do backup.
[Droid Incredible Android Development] wraithdu:
For the love... some of you need to READ more than you type. Rest your fingers, exercise your eyes.

On the Inc, NAND is locked. Outside of Unrevoked's reflash tool, NO ONE and NOTHING is flashing your recovery partition. When you invoke recovery through ROM Manager, it reboots and runs an update.zip that puts you into a fake (albeit fully functional) recovery. This does NOT FLASH your recovery partition. This fake recovery will be whatever version you have most recently downloaded through ROM Manager. If it was version 1, when you reboot through ROM Manager you would be in recovery version 1. This has NOTHING TO DO with whatever version you actually have flashed in your recovery partition. You can boot into your REAL recovery via 'adb reboot recovery' or by powering down and entering recovery through HBOOT.

Someone needs to sticky this information or stop new people from posting for a few days or something cause this idiocy has to end.
[Droid Incredible Android Development] altpersona:
what i did, as far as executing a program in linux, is typically what works.

sdk is my shorting the actual folder name for speed of typing on here. its much for functional on my box to

cd /andro*

cd/ andro*

cd tools

sudo ./adb shell

su

than to sudo /big long list of dirrectorys/./command

anywho, my search is over for now, unrevoked is not gonna cut it for me.

thanks for the helps..
[Droid Incredible Android Development] Shadowmite:
I'm sorry, I'm not trying to offend you, let's look at your line:

~/ sdk/sdk/tools/sudo ./adb shell

What this does is look for sudo in ~/sdk/sdk/tools, which I don't know about your system, might or might not be there. then proceeds to use adb from the current directory instead. That just seems like it's out of order. in general if you can run adb shell as root, you can check what I asked about. How about checking if you have superuser in your menu?
[Droid Incredible Android Development] cuban11182:
Nevermind.
[Droid Incredible Android Development] jdmba:
Welp

The current v3.1 has 2.5.0.1 already built in; so you don't have to do anything special.

To flash v2.5.0.1 using v3.1 or v2.1 you follow the instructions ON THE VERY FIRST POST OF THIS THREAD.
[Droid Incredible Android Development] cuban11182:
THX. Was just a little confused.
[Droid Incredible Android Development] giantcrazy:
Thanks to the unRevoked team for the easy root - had gone though the painful process with my own phone a couple of weeks ago, but saved my wife's for the one-touch root. Just finished her, painless and as easy as possible. Now, to make sure she doesn't accidentally get herself the OTA somehow.
[Droid Incredible Android Development] heffe2001:
There was another report of the EXACT SAME problem I had after loading 2.5.0.1, same symptoms, and the only thing both our phones had in common is clockworkmod 2.5.0.1 being loaded.

He's getting these:

E:Can't mount /dev/block/mmcblk0p2

(File exists)

E:Can't mount CACHE:recovery/command

I got that, and an additional error about the DATA partition. I'm wondering now if it really IS a bad nand on my phone (but at this point it's hopelessly bricked, no power, no led flicker with battery, usb or without, she's dead Jim).

When I get my new phone, I'll likely use 3.1 to load it, but if I want to go with the older clockwork, will it be a problem to downgrade it with 3.1 after it roots and configures the phone?
[Droid Incredible Android Development] s197:
I'd like to install Clockwork 2.5, I'm already rooted via unrevoked 3.0.

I know the first post has instructions but it says to use unrevoked 3.0 (which I deleted after rooting) and now only unrevoked 3.1 is available on the website. My question is, if I use unrevoked 3.1, do I just run the entire process over again or do I just point version 3.1 to the new img file?
[Droid Incredible Android Development] bhazard451:
3.1 has 2.5 already in it. Just run 3.1, no need to a separate img.
[Droid Incredible Android Development] dangeross:
i am on a mac, running snow leopard. attempted the reflash program with clockwork and anonra's image.

i get the communications interrupted error everytime.
[Droid Incredible Android Development] droidberry:
unrEVOked recovery reflash tool

git 7bb95e5

DEBUG: Killing any existing adb daemons...

DEBUG: The adb service is not running.

DEBUG: Waiting for device. Plug phone in now and enable USB debugging.

DEBUG: Found a Droid Eris.

DEBUG: Pushing recovery image.

DEBUG: Pushing flasher...

DEBUG: Waiting for reboot...

rawadb_open: remote closed the connection looking for target "reboot"

DEBUG: Communications with phone unexpectedly interrupted. Try again.
[Droid Incredible Android Development] Mr. Spontaneous:
Try a different USB cable/port.
[Droid Incredible Android Development] derickmc:
i used this to root my phone. it worked just fine, however i dont have a wifi tether app, but i do have superuser. anyone know why?
[Droid Incredible Android Development] s197:
you need to install tether. THere are directions at the bottom of the unrevoked wiki page.
[Droid Incredible Android Development] kagy:
Okay from terminal, cd to where reflash is

type sudo ./reflash

enter your password and off you go.

I got the same error when I typed sudo sh ./reflash ; however the sh isn't needed as it is a binary file not a shell script.
[Droid Incredible Android Development] droidberry:
Tried a different port with same result. Trying to find different cable. :D
[Droid Incredible Android Development] elmatatan:
please help....

Can anybody tell me if it is safe to install ota update from sprint 1.47 after rooting htc evo with unrevoked 3.1, I rooted my evo baseband 1.39 with unrevoked 3.1 everything is working fine but now I want to install latest ota update and I'm afraid to mess up my phone.. Thanks everyone for your help
[Droid Incredible Android Development] rpearl:
The OTA will remove root, but you can still use unrevoked3 on the new sprint 1.47 OTA
[Droid Incredible Android Development] checo346:
I see I'm not the only one getting the "communication with phone....." error on Windows with the Eris.

Anybody with Windows been able to do the Eris?

I've tried all USB ports on my laptop and desktop and 3 different cables with no luck.
[Droid Incredible Android Development] clambert11:
I was confused about this too.

The unrevoked homepage displays the following phones:

Evo

[*]Hero

Aria

Desire

Incredible

The unrevoked rootwiki, which still shows traces of unrevoked2 in it lists the following supported devices:

Sprint EVO 4G (HTC Supersonic)

Droid Incredible (HTC Incredible)

HTC Desire

HTC Aria

[*]Droid Eris (HTC DesireC)

I haven't seen much success, if any, on the Eris. I may be wrong but I think the wiki is incorrect and should list the Hero instead. Forgive me if I am indeed wrong.