yashsingh1/xdaforums huggingface dataset:
[Droid Incredible Android Development] shamidude:
I would like to share a tip that helped me format my SD card to NTFS and 64KB block size. When I tried that using Windows Explorer or Device Manager, I was only allowed to pick FAT or FAT32. So I did some googling and I found out that I had to change the "policies" for the drive (from "Device Manager|Disk Drives" then right click on the USB drive and select Properties and open the Policies tab) to "Optimize for performance".

I then opened a command shell and used the "format" command using the "format <drive> /FS:NTFS /A:64K" (replace <drive> with the actual drive that the SD card shows up under).
[Droid Incredible Android Development] ejkeebler:
there was an update on twitter that said something to the effect of hero users have some great things coming, then the next tweet was something like that last post should have said "Incredible"

so maybe it's almost here, maybe another ROM, maybe a rooted OTA, who knows....

*EDIT*

Oops. That last tweet should have said "Incredible" stuff in the pipeline. We are improving things for Inc users. Same as usual: no ETA.

about 19 hours ago via Tweetie for Mac

Hero folks: there is stuff in the pipeline too. No ETA, but we will be improving things.

about 20 hours ago via Tweetie for Mac
[Droid Incredible Android Development] Crackmaggot:
Finally got root. :D Ended up using the provided 2Gb Sandisk microsd card. The only way I could get into recovery with any success in reproducing was to begin formatting the card, then pull it out in the middle of the format. Thus corrupting the file system. I could then repeatedly get ADB running in recovery. Then I grabbed another SD card to load up all the files on.
[Droid Incredible Android Development] mrchambo:
Thanks r pearl and team unrevoked. Patience will be rewarded.

Donation to follow at appropriate time...

JC
[Droid Incredible Android Development] colonel187:
sorry for the noob question but when i use dmesg it scrolls by way to fast and i can't scroll all the way back up to the top it doesn't exist.. can anybody help me make it page by page or tell me how to let cmd.exe show the entire log dump
[Droid Incredible Android Development] krelvinaz:
Reboot your device and then use dmesg.

It will be a lot less data since the device just rebooted.

I don't know how to increase the scroll back buffer in cmd.
[Droid Incredible Android Development] colonel187:
ok thanks, that kinda worked. i am getting two different numbers every time ti do it. 5.48 and 7.26

i still can't seem to hit that window during recovery. grrr so frustrating.
[Droid Incredible Android Development] cantare:
using dmesg to standardize root process

I'm a rank amateur at most things *nix and hacking-wise... but:

1) can't one use some pipe or redirect command to dump dmesg output into a textfile? Sometime relatively soon after a boot-up, get a terminal app going, either on the phone (I use Terminal Emulator) or via an adb shell, and do:

dmesg > /sdcard/dmesglog.txt

As long as you put the output file in some user-writable area (/sdcard or /emmc) I'd think it should work.

2) Has anyone tried to systematically correlate the timing of the critical mmc/adb 'events' with success/failure at rooting? For those who can get ADB running in recovery, can you also dump dmesg and look at it there? If so, does the relative timing of those events square with what happens during a normal boot?

Unless the intervals are the same (or at least proportional in some definable way that doesn't depend on the specific phone in question), it would seem that looking at dmesg from a normal boot would be of little value to the user who can't get ADB in recovery. Which is where I still am, despite many trials with various methods...<groan>
[Droid Incredible Android Development] :
Yea as DC_Stryker (a known dude here on XDA) said much earlier in this thread, Unrevoked team should create a port of Unrevoked to Eris. Even though the Eris is EOL'd (end of life) by Big Red (verizon) I think they should tag the Eris along as another phone that Unrevoked supports, just like they added the HTC Hero to the list. :D
[Droid Incredible Android Development] rpearl:
have someone with an Eris talk to us.
[Droid Incredible Android Development] tcberg2010:
My wife got an eris, already rooted though, would be willing to help however i can.
[Droid Incredible Android Development] mortymouse:
I have an unrooted Eris that I have been trying to root with every possible way and have not been able to do it. If there is something I can do to help, please advise.
[Droid Incredible Android Development] s197:
Thanks very much for all of your hard work. Is an alternate (ie. easier) root method being worked on? I know you guys do not like to give out ETAs, and I've been following your tweets, so I'm not asking for anything specific, but just knowing an alternative is in the works would be helpful.

If something is in the pipeline then I'm content to wait rather than deal with the race headache and spending money on additional SD cards.
[Droid Incredible Android Development] mozetti:
I'm pretty sure rpearl is referring to the Incredible "easy" root method here. I asked for confirmation, someone seconded it, and then rpearl replied about the Incredible.
[Droid Incredible Android Development] Jinnai:
I have a phone with hboot-0.79 (just arrived in the mail yesterday) and I have been trying all day to get this thing rooted. Nothing works. Doesn't matter what method or what card I use (and I have a few). Anyone else with .79 gotten this to work? I just can't get adb in recovery. Everything I've tried with card inserting/removing or usb inserting/removing and while it does the usb disconnect sound and then usb connect sound, I never get anything other than device not found. So I'm wondering if .79 is something new and fixes this and I'm wasting my time, or if I'm just not hitting the magic spot.
[Droid Incredible Android Development] rpearl:
Yes, 0.79 works fine.

Hopefully a new method very soon.
[Droid Incredible Android Development] Jinnai:
Great, thanks for the answer. I guess that means I just haven't found a "good enough" (slow enough?) card yet from my collection. When I saw how simple it was for some people (2nd video of how to root an HTC Incredible in 10 minutes on YouTube) I started feeling a little discouraged. It might be time to head to Best Buy, buy an assortment of cards, and carefully open each to try while saving the receipts.
[Droid Incredible Android Development] rfarrah:
.... or just wait a little longer for another option, according to rpearl.
[Droid Incredible Android Development] shoman24v:
I'm waiting, you all might as well too.
[Droid Incredible Android Development] Jinnai:
Maybe I'm jaded, but I've seen too many "soon"s for this type of thing turn into weeks, and in a couple cases months. Don't get me wrong, they've done absolutely great work. Besides, if something easier that works does come out before I make it to Best Buy then they're definitely getting a donation for the cost of at least one of the cards. (And I'll still save on gas money.)
[Droid Incredible Android Development] Xxq TZ pxX:
After a lot of trying, I was able to root my Dinc by following the first method shown in the 10 minute root video on youtube, but with a few modifications (I used the regular 2gb card that came with my Dinc). This is the only way I could get it to work, and I've since rooted it again using this method:

1. Format the card (regular format, not quick) to FAT.

2. Copy just the files in the sdk/tools directory to the card (I think it will be around 13mb)

3. Right before choosing "Recovery", pop the card out. Choose Recovery, and press the card back in simultaneously as the windows hardware insert/device connect sound plays.

It make take you a few tries (took me about 5-10 each time) but it just works. I really hope this works for you because I know how frustrating this is! Good luck.
[Droid Incredible Android Development] s197:
Ryan,

Thanks for the update and all the hard work you guys are putting in, much appreciated!
[Droid Incredible Android Development] Jinnai:
You got me thinking and I started ignoring everyone's recommendations for timings. I went back to the first page that showed a good dmesg, then I did a normal boot and as soon as the white htc screen showed up I started counting 5 seconds, then I inserted the memory card. When it came up I did a dmesg from the adb shell and looked at the timing for both the adb warning and the mmc1 state detect. Then I started practicing with normal boots until I got it (make sure to do a full shutdown, not battery pull if you do this) so that the mmc1 notice wrapped around the adb warning. I then used that timing with a recovery boot and it didn't work.

Next I booted normal with the card in and looked at the adb warning timing. It was a full 2 seconds earlier than if I had popped the card in during boot. Using that info I subtracted 2 seconds off my previously calculated time, booted to recovery, inserted at the right time, and bingo, it worked. I can replicate it every time now with the card that shipped with the phone. It seems to depend not only on the card being used, but also the computer you're connected to as to when the adb warning shows up.

So you may not have meant to, but you planted the idea that got it working for. Sadly I've run into another problem... following the official instructions when I reboot and try to su it waits for a couple seconds then says permission denied. So I rebooted to adb recovery and tried again... but this time I used the instructions in the YouTube video. Sadly... that didn't work either because when I got to the ln -s portion it said permission denied. So while I can get root in recovery, I can't seem to make it stick.

Update: When I tried the official method it flat out didn't work. When I tried the YouTube method originally it was using the files from the official walkthrough and that seems to be what was screwing things up. I used the files from the YouTube method and followed those instructions and it worked perfectly. I now have a rooted Incredible. Thanks for everything. :D So I guess it's confirmed some methods still work on the phones shipping right now from Verizon.
[Droid Incredible Android Development] bast525:
This method makes more sense to me than anything else anyone has posted on trying to obtain root. This should take all of the guesswork and luck out of the equation. I'm going to try this when I get home.
[Droid Incredible Android Development] cantare:
Jinnai, since you're working on this and can replicate your adb in recovery step at will, maybe you can answer the question I asked a few pages back: What does dmesg look like when run from adb in recovery (do the mmc messages 'wrap' around the adb warning or is there an offset), and how do the timings compare with what you saw during normal boot and/or booting with delayed card insert?

I've played around with your method for the last hour or so...seemed like the adbd warning floated between 8-10 sec on my setup over multiple runs. I was able to engineer a few 'close calls' between that and the mmc stuff, but never quite got it to 'wrap'. I started trying with recovery boots when I thought I had an idea of what happened when, but no luck getting ADB running there yet.

With Ryan's recent allusions to a better method, hopefully this'll all be moot soon.
[Droid Incredible Android Development] dccoh:
So, ive been doing this too. But im still a bit cloudy when to insert the card.

What msg is the important msg to not when booting up and doing a dmesg?

My "warning: adb" message differs only about .5 seconds, so im sure im doing something wrong.

In the end, when in recovery mode,hitting the button, and getting the next htc white screen, at what point 'message wise' should i be putting in my card?

Ive tried everything and im at wits end. I have my stopwatch out trying to beat this thing :)
[Droid Incredible Android Development] bast525:
ok I tried dmesg to see where my "warning: adb" message is and man it's ALL over the place.

I think it's important to do this while booting with the sd card removed completely as remember, you are trying to see when adb starts so you know WHEN to insert the card. Booting with the card inserted seemed to change the times that adb wanted to start. I got it most consistently around 6.4 seconds, however, this was also affected by how I shut down. If I did a normal shut down (holding power button select power off), then powered on with no sd card, dmesg showed the warning adb message almost always 6.4-6.5 seconds. If I did a battery pull and normal boot with no sd card, warning: adb message would show at any point between 5.4 and 20.xx seconds!!!

I did several boots into recovery and aimed for 6.4-6.5 seconds to insert the card using a stop watch that showed tents of a second but no luck...
[Droid Incredible Android Development] rpearl:
Soon is on the matter of days, not "weeks or months" as has been said. The root we have works, perfectly, reliably, and consistently. We just have to package it up (and make sure HTC won't find it for a while :P)

We are doing so. I expect progress this weekend--we have day jobs, and can't work on this quite as much during the week.

Once again, however, we don't want to give an ETA. But it's not like we haven't found anything.
[Droid Incredible Android Development] bast525:
See now THAT is good news and very specific, enough to give the hopeless hope and maybe patience for the impatient (myself included!). Up until now things have just been so vague it's nice to have something a lot more specific. Well, I think I will stop wearing out my SD card slot now and just wait for the easy root. I've tried so many hundreds of times and am just tired of it :P I only want it for Titanium Backup, to use my LED as a flashlight, and to remove City ID anyways.... I love the stock rom so far and haven't felt the need to switch.

Ah well... soon... soon
[Droid Incredible Android Development] Jinnai:
You want the dmesg to appear similar to what's on the first post of this thread. All that matters is the "warning: `adbd' uses 32-bit capabilities" appears between "mmc1: Slot status change detected" and "mmcblk1: mmc1:ff0e SD02G 1.83 GiB" or whatever card model and size you're using. The card itself can expand or shrink the window between those two lines, which is why some cards make it easier than others. For me, I noticed that my adb message moved around about half a second which is why generally I can get in recovery first try, but occasionally it takes 2 or 3 tries. How much that moves around (if you're following the exact same recovery boot process each time on your phone) is going to depend entirely on your computer. I have no idea what aspect of the computer affects it, but my guess is either how fast your adb shell loop is running or what's going on with your usb hub (other devices connected, etc.)

For me, if I boot the phone normal with no card in and then insert the card while it's booting, the adb message is generally at 8.8 to 9.2 seconds after the white screen appears. If I boot the phone normal with the card in, and leave it in, the adb message moves earlier to about 7 seconds. I know the recovery boot is shorter than the normal boot, so I cut off those two seconds I saw the adb message shift and on a recovery boot if I aim for 7.2 seconds I nail it about 90% of the time. On a side note, my phone makes the "cricket" noise at about 6.8 seconds regardless of what mode it boots into, so I think aiming for that might be coincidence (it doesn't move around the same as the adb message), but maybe not since my success is so close to when that noise happens.

Remember, the time listed in the dmesg is not the same as you will count with a stopwatch after hitting the power button, just use those numbers for points of reference. If you can't get the adb warning to stay within about half a second regularly, I have no idea how you could reliably do this. If it is stable for you, and you think you know the right time to insert the card then try multiple attempts at that time, then adjust it a tiny fraction and try multiple attempts, repeat for about a second in each direction.

But if you're a patient person, then wait for the new and improved reliable method that rpearl has graciously let us know is coming. :D
[Droid Incredible Android Development] mrchambo:
Ryan and the rest of team unrEVOked...

Thanks again for all your combined effort. I am a patient man and will wait for the next step in the process. Just wanted y'all to know how much we appreciate your hard work...

JC
[Droid Incredible Android Development] heliotropeUCSD:
thanks to rpearl and unrevoked

rpearl and everyone- I've been following you guys in anticipation of receiving my DINC on the 15th (waaaay backordered) and the news that a packaged root is coming makes me very happy. Thanks for all your efforts- I'm looking forward to using, enjoying, and donating!
[Droid Incredible Android Development] shoman24v:
Can't wait for the release, defiantly will donate when I get root :D
[Droid Incredible Android Development] Raptor567:
I'll also be waiting patiently for a packaged root method. Thanks for all the work you guys on unrevoked have put in.
[Droid Incredible Android Development] commissionerg:
Me too. I can't wait. I am just curious though. What is so different about the Incredible that it takes longer than the other htc phones? The EVO was pretty much rooted before it was even official release. I still commend you gentlemen for your hard work.
[Droid Incredible Android Development] rpearl:
The EVO was easy to root. See the disclosure.
[Droid Incredible Android Development] commissionerg:
Thank you (jonnybueno) your post (#201) helped me finish off my root. The final step is left off from the wiki. Now I got it to stick. Thank you soo much.
[Droid Incredible Android Development] WildZontar:
Before I do this, what exactly has to happen for the phone to become bricked? So I can avoid doing that while I try to root it.
[Droid Incredible Android Development] ryan000111:
Am I supposed to be doing the dmesg command in a terminal app on the phone or in the cmd window on my host pc? I guess that's the part I'm most thrown off by. If I run it on a terminal app from the phone it says something like 5.03 mmc1 slot status change detected ... 5.54 mmc1 high speed detected .... 9.17 adbd uses 32bit ... give or take a few 1/100ths of a second depending on how I shut down the phone(ie battery pull / normal shut down) I too have been stuck trying to get ADB to reboot into recovery. If I am using the add/remove SD card method, at what point do I start counting to readd the SD card? Am I waiting until that 9.17 sec mark to try and offset the start up of adbd?

Forgive me if this was better explained in a previous post. I work in a call center and am just reading through these forums in between calls... >.<
[Droid Incredible Android Development] jumbotron:
Yesssir!

Your instructions worked like a charm! After failing for 4 hrs, and going through countless variations of timing/methods...reformatting my SD card to NTFS finally got me to get the elusive "error message."

Although I made one mistake, I left the SD card (2gig Sandisk from BB) in it's converter after reformatting back to FAT32 from NTFS on accident. Thought it was in the phone so I ran the, adb shell and somehow got the error message.

I freaked out but then put the SD in and ran the 1.bat command and push payload and it somehow worked. Complete beginner's luck, even got rid of CityID app too!

Just wanted to say thank you to all and you since your steps were clear and concise...and they last one I was willing to read/try. THANK YOU!
[Droid Incredible Android Development] k_flan:
Thank you

Thank you to all the devs working on the Incredible!!!

I was able to root with the 2gb card that came from VZ. Used the usb connect sound in win 7 x64, inserted sdhc about 3/4 sec after hearing the start of the sound. Used the usb drivers provided in the unrevoked recovery flash tool thread (was it just the 3 extra lines in the two sections?).

Can't wait for the roms to get worked out!
[Droid Incredible Android Development] ryan000111:
I just wanted to say that after spending 7 hours prior to tonight trying the various methods that this one worked for me. I'm not saying that this is a cure all method since by reading other posts it seems diff methods are working better for diff people...but this worked the very first time for me.
[Droid Incredible Android Development] prchohan:
Any update on packaged root?

Hi dev team. First off, thanks a lot for all your hard work. With your day jobs, this is a huge service you are doing to the community. Understand that it may take time but do we have any update on the packaged root?

Thanks again.
[Droid Incredible Android Development] s197:
They post updates on twitter (twitter.com/unrevoked) from time to time. Here's the last:
[Droid Incredible Android Development] vzw:
Months out now still no real root process.... I know unrevoked team is working on one but Htc must have done a great job with this one to have it this long without having a simpler root process....

Heres to still hanging on to the hope it will be sooner than later...
[Droid Incredible Android Development] Archangel:
Can't wait for something a whole heck of a lot easier then what is out now, then you can count on def contributions!
[Droid Incredible Android Development] mpadgett:
Unrevoked tweeted today:

Something you might like is on its way... See you tomorrow!
[Droid Incredible Android Development] mrchambo:
Fantastic! Thanks for the heads up...

JC
[Droid Incredible Android Development] shoman24v:
I'm hoping 1 click root :)
[Droid Incredible Android Development] outsid0r:
agreed, really hoping this is what we have all been waiting for!
[Droid Incredible Android Development] reagianicparable:
Haha, my micro SD card that I was using to root got corrupted and I had to spend $10 on the PNY card. That would be my luck.
[Droid Incredible Android Development] Joe92T:
So i did the previously posted unlock procedure thats been deleted.. it didnt really seem to do anything.. whenever i try to SU while running android it still says permission denied.. and then whenever i try to adb push something to the /system folder it still says that its a read-only system, so i dont know if anything actually unlocked or not

This should be fine to discuss as the thread has been deleted and IM NOT POSTING ANY PROCEDURE on how to do this, im just saying "hey i did what was previously posted, and this is what happened"
[Droid Incredible Android Development] reagianicparable:
@Joe92T: Are you asking for help? Try the new procedure. If it tells you permission denied, then it was not rooted. The nand is locked down even if you are rooted except through the unrevoked exploit, wo that is why it tells you read only.
[Droid Incredible Android Development] kentoe:
New link? I forget if this has been around for a few weeks.

http://unrevoked.com/incredible/

"Incredibly fast root"
[Droid Incredible Android Development] outsid0r:
nope same link, still waitin for it to come out
[Droid Incredible Android Development] gbishop18:
unrevoked's twitter said something we've all been waiting for is coming tomorrow. sweet
[Droid Incredible Android Development] shoman24v:
I hope more then a website ;)

JK can't wait!
[Droid Incredible Android Development] Joe92T:
I am asking for help.. i have a 100% stock rom on my phone, i havent rooted it in any way, its hboot 79... Anyway i did the nand unlock that was posted last night for afew hours before taken down, and even after doing the nand unlock and booting into android it still says permission denied and says /system is a read only file, so im wondering if the posted nand unlock even unlocked anything in the first place, because if it did wouldnt i have free reign even while running android and not recovery
[Droid Incredible Android Development] reagianicparable:
To use that nand unlock, you need root first. Period. Root, then nand. Not the other way.

Also, if you had root, then used that tool that was posted and rebooted, you would not have the nand unlock anymore. But either way, you need to be rooted first.