• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Leaker has achieved root!

Has anyone thought of making a program the will do all the typing and such, kind of like the one for the current 1.5 root?

Edit: I mean, I know it's new, but .Bat files don't take long to make.

Edit2: And by new, I mean the root/exploit.
 
hopefully I qualify for the "high quality"
I've got 3 leaker friends that have been trying this. Not one has achieved Root.
We're not giving up though. I've got my Widow Widow Eris next to me "rooting" us on.
 
Ive done quite a bit of work trying to get this to work. Ive messed with drivers, and no matter what it doesnt get detected in recovery, so it fails. If anyone on here gets it to work, then ill believe its not just some stunt by a couple of kids.
 
SyDTRaKKeD said:
can't get my drivers to change from "HTC Android Phone.... whatever" to "Android Composite ADB Interface".....
Click to expand...

The thing is... Were not trying to do that. We need BOTH of them up. My guess is that the android phone is like the storage or whatever and the adb is... well adb. And you cant change something to something its not. We need a way to get adb to persist after going into recovery. Im assuming thats where the SD card is supposed to come in... like lag the phone out so it doesnt remember to shut down adb. I can connect fine in fastboot, then back out, and its still there up until like 6 seconds after i click recovery. Im assuming theres a key moment to put in the sd but when is what the "successfuls" are refusing to tell us.

I hope its not faked. But in anycase, im not going to be on tomorrow until like 9. So it better be a rock solid root process by then...
 
Hiroshika said:
Ive done quite a bit of work trying to get this to work. Ive messed with drivers, and no matter what it doesnt get detected in recovery, so it fails. If anyone on here gets it to work, then ill believe its not just some stunt by a couple of kids.
Click to expand...

I've got mine to detect as Removable Disk G but I can't seam to replicated it
 
scary alien said:
Look at the number of folks that have trouble with the "normal" rooting instructions.
Click to expand...

I don't want to call it a hoax, but it has important attributes of a hoax, not the least of which is the huge difference between this thread and the root thread: success being reported in the root thread, no provable, credible success being reported here (with screenies).
 
Frisco said:
I don't want to call it a hoax...
Click to expand...
I'll go out on a limb and say it is. And people without root will whine that I'm discouraging development, criticizing people who are trying, etc, etc. No, sorry, it's worse when people give others false hope about something.
 
It could be a "hoax by exaggeration," more than as some jerk messing with people for laughs or whatever. It was a failure, but he doesn't want to admit that.

It could also be a "hoax by hoping somebody will figure out what to do." They report their efforts as successful, then leave it up to the masses to produce a geek out there who will pop up and say, "Oh.. I get it, he forgot to tell us to ... blah and then blah blah.. it does work."

Or both.
 
yes.... i'm back on the skeptic side of things after trying this method over and over and over again... and i know the guy says "its luck" getting the sd card in at the right moment but i think more people, people who have been trying this method over and over and over again (who knows how many times), would have gotten lucky by now if that were the case...
 
SyDTRaKKeD said:
yes.... i'm back on the skeptic side of things after trying this method over and over and over again... and i know the guy says "its luck" getting the sd card in at the right moment but i think more people, people who have been trying this method over and over and over again (who knows how many times), would have gotten lucky by now if that were the case...
Click to expand...

Well, including a variable with no true parameters to it does add weight to the hoax suspicions.

If it walks like a duck and quacks like a duck, it's a duck.
 
I got windows to recognize the device is bootloader by modifying the android_winusb.inf.

In device manager double click on the unknown usb device and go to details. This will give you the device instance id. It may be different for your device but this is what I added to the android_winusb.inf file:


;HTC Desire (Eris)
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C98&MI_01\6&8DF607A&0&0001
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C98\HT9AJHG01384
%CompositeAdbInterface% = USB_Install, USB\VID_046D&PID_C529\5&2DE04A89&0&2
;

Saved the file and booted the phone into recovery. I heard the windows "ding" that notified me of a usb device being plugged in. After this I start running the adb devices command (use the loop file if you want). I've tried the detection process with the SD card in, sd card out, removing/inserting but haven't gotten adb to recognize the device. How ever I do get a message that adb can't find the running process and it tries to start it. This is as far as I have gotten thus far.

Also after tweaking the inf file, fastboot usb was available from the boot menu. I tried to push amon's recovery using "fastboot flash recover recovery.img" but get a write restriction. Another note is that the sdcard needs to be inserted before it will attempt to flash the image.

I'm sorry if my information has offended some of the other users on this forum. I tend to troll forums and not post too often. Check posts with same user name on straightrazorplace.com and 600rr.net.

Hopefully those someone will find this information useful and may have some tips and or continuation to my found process to get this to work.
 
I have a rooted phone, but I wanted to look into this as I used to own a 1.49 and it sucked butt not being able to do whatever I wanted with it. Unfortunately, after reading the entire thread, I'd conclude there is a 99.99% chance of someone trying to pull a fast one.

We already knew about the video being shady at the 20 second mark and the lights dimming for a magic trick that no one is allowed to view, but...............

One of the OPs posts stated "what makes you think I rooted more than one?" (paraphrased).

Ok, think about this:

If he just *happened* to stumble upon this fix, how would he just *happen* to have his video camera on his ONE PHONE that he rooted at EXACTLY the right moments when it rooted?

If you happened to stumble across this fix, and only had one phone, wouldn't it make sense that you wouldn't have the camera on for that one short segment out of hours/days/weeks/months of trial and error?

And then there's the sock puppet FNG that comes in and says "yay, I got it to work." Someone who has rarely ever posted, and the only other responses are "if you guys are gonna accuse me of anything, then I'm just going to quietly leave."

ummmmmmmmmm............ ..............ya...

Then I review his loop.bat, and oh the hours of entertaining fun you guys must be having with that trying to get it to pop at the "exact" time, right after you pull out and reinsert the card, oh wait, I forgot to add something: stand on your head, and touch your toes, and all the while watching the command screen as one command loops in a circle in near orgasmic anticipation.

Here's the contents for those that didn't look:

:TOP
adb devices
GOTO TOP

My guess would be a bunch of really young guys who got drunk one night and thought something would be funny are now trying to back peddle by telling everyone "it's about the timing." It's the only way to get out of looking like a liar while keeping everyone engaged and occupied.

Is it possible that they have the one phone in the world with the one operating system in the world with the one driver in the world that worked?

I suppose it's possible that aliens will land on earth and give a few of us free ice cream while we take joy rides in their chocolate covered space cruisers, but I'd tend to go in favor of the most logical explanation: there's nothing to see here.

I hope he makes me out to be a liar, because anyone getting a new Eris is going to be stuck with 1.49, but I think I'll pass on holding my breath.
 
Here's the BIG kick in the nuts:

adb devices

That command does not DO ANYTHING to the device. It simply lists the connected devices. I say we find out where the guy lives and have a blanket party :D

(joke... that's a JOKE...)
 
His video doesn't show the process or steps. It simply shows a rooted phone and a phone with HBoot 1.49 S-On.

And this part I'm not sure, but I think running any 'adb' command will try and launch the adb daemon on the phone (adbd). That's what is needed, to get the daemon up and running. At the unrevoked site, they do list "adb devices" as an alternate method.
 
hallstevenson said:
His video doesn't show the process or steps. It simply shows a rooted phone and a phone with HBoot 1.49 S-On.

And this part I'm not sure, but I think running any 'adb' command will try and launch the adb daemon on the phone (adbd). That's what is needed, to get the daemon up and running. At the unrevoked site, they do list "adb devices" as an alternate method.
Click to expand...
That's exactly it with the video. It adds no credibility, or even methodology to the mix. Simply fuel for the fire.

You may be right that the command is less of an actual command and more of a trigger. My understanding was that adb devices simply listed a device with the daemon active (in that it either exists or it doesn't, nothing in between), but I'm still too noob to make an absolute judgment call on that one. It does hit a sore spot, because it touches on an entire community of hopeful people.

Dangling the carrot... It sucks.
 
if you guys want root so bad. Go to barnes & nobles get some books and learn how to do it. You could have root by now, considering how long it has taken for something like this to even come aroun.
 
chaM87 said:
if you guys want root so bad. Go to barnes & nobles get some books and learn how to do it. You could have root by now, considering how long it has taken for something like this to even come aroun.
Click to expand...
LOL... Rooting is not a matter of education. It's a way of circumventing the protection placed on a phone. It is hacking. This is why it has taken so long to find a solution...

It's not something you just look up in a book :D:p
 
majorpay said:
You may be right that the command is less of an actual command and more of a trigger. My understanding was that adb devices simply listed a device with the daemon active (in that it either exists or it doesn't, nothing in between), but I'm still too noob to make an absolute judgment call on that one. It does hit a sore spot, because it touches on an entire community of hopeful people.
Click to expand...
Yes, it's more of a trigger... From the unrevoked site, public:adb_in_recovery [RootWiki], they list two methods, one using 'adb shell' in a loop and different method (the one where you insert/remove the SD card while booting, etc, etc) that uses the command 'adb devices'.
 
majorpay said:
LOL... Rooting is not a matter of education. It's a way of circumventing the protection placed on a phone. It is hacking. This is why it has taken so long to find a solution...

It's not something you just look up in a book :D:p
Click to expand...

There are ways to "Hard" flash to the older boot loader and you can with enough books learn how to create and program the device to do it.

You will have to disassemble the phone and odds are you may brick the first few until you get it right but it is very possible.

While that is not technically rooting your phone, it would allow you to install the root.

Back in the day we used to take an identical bios chips out and use them to hack flash bad flashed proms.
 
Alright guys, I justed deleted 14 posts out of this thread for being off topic and/or rude personal attacks.

1 - Let's try to stay on topic from here on out.

2 - Personal attacks will not be tolerated on this forum. If any of you have forgotten them, please take this time to glance over the rules as well as the zero tolerance policy. Links conveniently located in my signature below.
 
Ok... first off I would like to say that I'm one of the skeptics here after trying this method many times...

now I know its one thing to be skeptical that these two actually used this process to achieve root on Eris... but...

there's no reason to criticize the actual process. saying that the loop command is just a ploy to make us sit there and watch our screens like idiots would be incorrect...

This process has worked on other phones... namely the myTouch 3g... check out the video on the actual page with the instructions... its a step by step tut but using the mt3g and everything works just fine and dandy (no SD card pulling required...)

Another thing that does lead me to be a skeptic tho is the fact that in the beginning of that thread... the guy is lol'ing in every response he makes to ppls questions... like he's getting a kick out of the fact that ppl are getting so excited and believing him...
 
You must log in or register to reply here.
Back
Top Bottom