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

Mods The root club [Root only]

Well, the process has started. I'm gathering tools and needed stuff to root my note 2

I think I broke my phone. Its been hung at Samsung for like 5 minutes now and counting
 
What did you do?

Chances are it can be saved. Its pretty hard to actually brick a device. The risk is always there though
 
Odin pass
Mtp USB driver fail
Device hung at Samsung

Now what?

Does someone have a direct link to the mtp drivers? Windows refuses to install because device cannot start.

I have a brick until I get that stupid driver. I knew better then this.
 
ajdroidx said:
Does someone have a direct link to the mtp drivers? Windows refuses to install because device cannot start.

I have a brick until I get that stupid driver. I knew better then this.
Click to expand...

should be able to get them right on samsung's website. just look for your phone and it should be available under downloads.
 
I did manage to get the device manager to show Samsung mobile device to show with no yellow triangle only for the driver install to fail

One last ditch effort.... I am trying to use the gs3 tool kit to install the mtp drivers for me. Fingers crossed

Did not work. How do I uninstall the drivers so I can try to install again.

At this point I am done. No more rooting. I have a brick because of a driver issue.
 
ajdroidx said:
Did not work. How do I uninstall the drivers so I can try to install again.

At this point I am done. No more rooting. I have a brick because of a driver issue.
Click to expand...

The easiest way I know is through the use of a free program called USBDeview. That should list every usb driver you ever installed and gives you the option to delete them.
 
Ran as admin, uninstall everything Samsung, reboot ran the driver software only to be told it was installed. No idea what to do.

I have changed ports, rebooted reinstalled drivers. The mtp driver should not be an issue. I wonder if its the actual image

Good news and bad news:

Bad news:

I am done rooting. I am not sure for how long, but honestly my device was working just fine prior to me tinkering with it.

The good news?

In a last ditch effort, I did a factory reset. It worked! I think....
 
Hey guys, owning 3 devices, Droid Incredible, HTC Hero, and LG motion 4G. All have been rooted all have a custom rom except for the motion(locked bootloader). The incredible is running tiny's cm10.1 rom using inverted gapps! Awesome! Only a couple of glitches camcorder not full working camera flickers. My hero is between Someone's cm10 kang with a lot of issues and cm7 is running perfect and to get the most of my phone I'm using the firerat mod Google it its awesome lol. The motion is rooted with a lot of limitations we're able to flash cm10 but not the kernel we have working wifi no data or calling I believe. I'm a flashoholic so any mods are welcome :)
 
dreadnatty08 said:
Aj, may be time to go back to a Nexus. ;):)
Click to expand...

ajdroidx said:
I thought about the nexus 10 but its made by Samsung :rolleyes: so I can see issues.

Its not a huge deal if I cannot root my note. Its a great device as is.
Click to expand...

I had the Nexus S (made by Samsung, easy to root, ROM etc.)
I then got the GSII, which was a nightmare. Pretty easy to permanently brick after the ICS update also. Galaxy Nexus didn't have the same issues as the GSII.

Moral of the story.... Trust that Google will do the right thing and not make rooting and tinkering difficult.
 
i just got the nexus 7... it is so nice.

I normally root all my android phones.. but was thinking to leave it alone because it is great the way it is with ADW Launcher.
Then i read some of the things i might do with root.. and now.. i might root it.

I had thought rooting a nexus ANYTHING.. would be a simple affair... because it is a Nexus! looks like my SGS3 is the easiest.
and in order to root the nexus i have to unlock the bootloader.. which wipes the whole nexus. oh-well.. if i have to re-setup the nexus7.. then i will find a good ROM too.
 
Rooting any nexus is a breeze.

Personally, I think Google does it right. Rooting should require a wipe. Its a potential security concern otherwise.
 
Rooting other devices that are not nexus devices usually require exploiting a weakness in the os. OEM's and carriers don't want you rooting because it can lead to problems in the hands of people who aren't careful, or if it's stolen. Being able to root a nexus is so easy that needing to use an exploit is unnecessary and as such, rooting a nexus is the same across just about every nexus device.
 
You know, to think about it, I did not really have these issues with a 32bit version of windows 7 whilst my old desktop was running. Just getting the initial drivers installed.

Hmmm... I do have an idea. Its a complicated work around... I will need a VM to do so, or dual boot, or temp install windows 7 32bit to a external harddrive, boot from that, load the drivers and such, and don't activate windows 7.

I would be a bit skeptical trying this with a VM, however.

Its a long work around, but it may work. But I am not sure if I want to possibly brick my device should it not work. A factory reset worked once, I am not sure if it would do the trick again.

On my 32bit desktop, I had the PDAnet drivers installed. When I rooted the S3s I used the desktop, and had no issues. I also used the toolkit. I also know there is a toolkit for the Note II that has the AT&T version.
 
I was going to try one more time before I do the complicated process I detailed in a previous post. I was going to just use the "toolkit" but found it has an update out that I cannot seem to download unless I am using the donate version, which I cannot find at the time.

Also found the build my Note 2 has, is not available yet to be rooted, at least via the tool kit.

Guess I put rooting this thing on the back burner for a while. Oh well...
 
I am firmly in this club. As far as Android I started with the Motorola A855. A developer style phone on VZW. The bootloader was never locked, but the root exploits were varied as the Android versions progressed; I received it just after release, Nov 9, 2009 and once the root exploit was released around Dec 9. 2009 to hack the update from 2.0 to 2.0.1 I applied it. Easy as pie. Never looked back. And that made me never want to own a phone that had an encrypted bootloader, even though I was a full on batwings (Motorola) fanboi.

I then waited until another developer phone would be released on VZW. that would be one with the Nexus moniker, the Samsung Galaxy Nexus. I owned it for about three days before rooting it just to make sure it was a good working phone. Done.

But my experience goes back much further to the 'dumb phones', just like OverByter in post #94 and EarlyMon in post #96.

You guys have no idea how easy it is on Android. On Android, we 'flash' a ROM.

For me, my experience was all Motorola, and 'flashing' back in those days, meant flashing to your E815, V3m, V9m a different carriers firmware using RSD Lite, and then making edits with tools that you had to pull up very specific areas in bytes of the firmware, then make edits to the bits, write those edits and hope it worked. We used seem editors, RSD CDMA General, QPST, RadioComm and maybe one or two others. Very powerful tools, one wrong step and you're totally screwed.

Long story short, the process was way more intense, and any wrong turn would give you an malfunctioning phone. That is why sometimes I have been snarky here. You Android guys have it pretty easy. In those 'dumbphone' days, you had to print out the guide and check off the steps as you went.

Here's my 'other' history:

  • Motorola V3m: flashed to Vivo (a South American provider) firmware and working on VZW network. .mp3 player, sdcard "USB Mass Storage" unlocked, tethering unlocked, forgot the rest.
  • Motorola V3m: Branded VZW phone flashed to USCC firmware. Taken to a USCC store and activated, albeit with some weird looks from the clerk.
  • Motorola V3m: Helped others flash to Metro PCS firmware to make the phone fully functional on Metro PCS system; far removed from what Metro PCS called a 'flash'.
  • Motorola V9m: Flashed to USCC firmware, then the Telus upgrade so Java was installed. Yes Opera, yes Gmaps, yes unlocked GPS chip, yes Java games.
  • Motorola A4500: My first smartphone running Win Mo 6.1. GPS unlock by 'null' so we could side load Google Maps. This took some RSD Lite flashing as well to get to the compatible firmware on it first.
Oh but wait, there's more. How's about using some of those same tools to get the Motorola A855 working on another CDMA carrier:

http://www.howardforums.com/showthread.php/1593533-service-programming-on-the-moto-droid

Yeah, I was 'raised' over at HoFo; where "read more, post less" was the axiom. I had to read through posts sometimes 50+ pages long to get where I wanted to go. This site is much more friendly. We Android folks have it easy.

OK, now I'm done.
 
Bender_-I-m-Back-Baby-.jpg


I got root!

Used CF root. I need to donate Chainfire some thanks :)

It worked on 4.1.2, I got multi window still, and... it tripped my flash counter. Oh well.
 
had to do a reinstall this morning do to some adb issue's which i'm still having so must definitely be the ROM. Got a letter in to the dev and will have to see what he finds out. ah the love of updating. :p
 
You must log in or register to reply here.
Back
Top Bottom