hey imnuts, any reason why you used superuser instead of supersu? im just wondering because in the gs3 forums folks reported supersu works better with jellybean.
Last edited:
[ROOT] VZW Note 2 Root Package
- Thread starter imnuts
- Start date
-
- Tags
- development
Personal preference sort of. It was also easier for me to download the binaries for Superuser to copy them over compared to trying to find the download package for SuperSU. I can easily make a new revision with SuperSU if people experience problems with what is up now.
SuperSU a better option once custom kernels are available. Some kernel settings won't stick on boot with superuser in 4.1 and onward. At least it's that way on the Galaxy Nexus.
imnuts- any chance you can add a VZW tethering fix to this? Picking up my Note 2 tomorrow and planning to flash this as soon as I get it.
No need for a tethering fix. I'm bone stock and tethering is working. Just set up your ssid and password and use a toggle widget like Fattin toggle widgit to turn on tethering
Sent from my SCH-I605 using Tapatalk 2
I may be incorrect, but If your on a new limited / share everything plan you don't need a fix. If your like myself and others who still have unlimited data plan then yes you need a fix.
Sent from my SCH-I605 using Tapatalk 2
I'm a little afraid.
The device looks to have a blue status bar that is full...on Odin, It says this...and everything is still and has been for about 10 minutes now.
what should I do?
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> ý7zXZ
<ID:0/009> NAND Write Start!!
UPDATE:
It failed...I am able to get back into Download mode....Tried a second time...same result
The device looks to have a blue status bar that is full...on Odin, It says this...and everything is still and has been for about 10 minutes now.
what should I do?
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> ý7zXZ
<ID:0/009> NAND Write Start!!
UPDATE:
It failed...I am able to get back into Download mode....Tried a second time...same result
Last edited:
I'll get it uploaded to a mirror when I can, but the reason that it is likely slow is due to the number of downloads it's getting. I have had 1100+ downloads and counting of the root package, another 450 of the deodexed root package, 250 downloads of the stock Odin, and another 125 of the straight deodexed files. That is 2.1 TB of bandwidth in less than a week. I didn't think it would be an issue with downloads as I've never had a problem in the past, even with big hits in bandwidth, but the downloads have pretty much been continuous since posted, so I guess it does eventually get affected. You'll just have to live with it until I can get it mirrored.
I am on unlimited. If you change the ssid and password in the stock hotspot app and launch with a widget tethering works just fine. I have tested with a Nabi and a Nexus 7
Sent from my Galaxy Note II with Tapatalk 2
---------- Post added at 08:01 PM ---------- Previous post was at 07:45 PM ----------
Sorry to go off topic. Thanks nuts for the factory image and the root.
Sent from my Galaxy Note II with Tapatalk 2
Help!!!
been trying to go back to stock but every I select the md5 file to put in PDA I get a "No binary is selected!"
Not sure what is going on. Is there a setting in odin that might need changing?
been trying to go back to stock but every I select the md5 file to put in PDA I get a "No binary is selected!"
Not sure what is going on. Is there a setting in odin that might need changing?
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> t0ltevzw_root.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> system.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
When I try to install I keep getting this. The only rom that works for me is root66, I've checked everywhere done almost everything possible, reinstalled drivers, switched computers, tried different roms, I'm just beyond lost here. If somebody, anybody could help me out n in his to get this thing unlocked I'd be beyond grateful.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> t0ltevzw_root.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> system.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
When I try to install I keep getting this. The only rom that works for me is root66, I've checked everywhere done almost everything possible, reinstalled drivers, switched computers, tried different roms, I'm just beyond lost here. If somebody, anybody could help me out n in his to get this thing unlocked I'd be beyond grateful.
I decided I wanted to keep SuperSU and followed the instructions in this post for removing Superuser manually. Everything seems to still be working correctly.
Hey IM:
Any chance of making the bone stock rooted rom available in zip for TWRP flashing? Not sure what's involved, but I messed up my stock rooted back up but I'd like to mess around with stock. There are some close to stock roms but they are themed with ASOP, and that's what I want to avoid.
Thanks!
Any chance of making the bone stock rooted rom available in zip for TWRP flashing? Not sure what's involved, but I messed up my stock rooted back up but I'd like to mess around with stock. There are some close to stock roms but they are themed with ASOP, and that's what I want to avoid.
Thanks!
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
34I know what you're thinking "We already have root, why do we want and/or need this?". Well, if you followed the root thread, you would have seen that the package posted was built off of two images. There was the early firmware posting that it was first made from, then a system pull in a rar archive that was used to put the root package on the latest firmware. In the processes, there were issues with permissions and other items missing. The people involved did a great job with what they had, but I don't like hacked up solutions to problems.
So, to fix that, I had a stock system.img for the release firmware. This allowed me to build a fully stock root package with no missing files or incorrect permissions. While it took some time to get this tested and verified working without having the device, I was able to get it. Thanks goes to Adrynalyne, Mibix, and AstainHellBring (and anyone else) from IRC for testing several packages (Freenode, #galaxy-note-2). This is only the start of things to come, and I plan on slowly working on a ROM based on this then. I also made a deodexed version of the same package. Download and flash that if you wish, but it was more to verify that nothing broke in the deodexing process and to get a working base for a custom ROM.
DOWNLOADS
Stock Rooted Image
Mirror 1
Mirror 2
Deodexed Stock Rooted Image
Mirror 1
Mirror 2
INSTRUCTIONS
- Download one of the above packages for flashing.
- Extract the file (7zip works to extract).
- Open Odin (download that elsewhere), and put the extracted tar.md5 in the PDA spot
- (Re)Boot your phone into download mode and plug it in to your computer
- With it recognized in Odin, press start
- Once the phone boots up, all should be well. If you notice issues, boot into recovery and wipe data and this should fix the problems.
- If you still have issues after wiping the /data and performing a factory reset, please post here.
NOTE: I am not responsible for any ill effects caused to you, your loved ones, you phone, or anything else as a result of flashing this. Do so at your own risk as I won't be held responsible.4
It is significantly easier to theme and modify deodexed versions compared to what ships.
If/when I get enough money, yes. For the moment, I have a few people I know that are testing things for me.
If you already have root and/or have done other changes to /system, then there isn't a need to flash this. It is meant more for people that haven't yet rooted. If you have only done root, this shouldn't change anything for you. If you have rooted and made other changes (deleting apps/etc.), then it will undo those changes, and possibly force you to factory reset. Nothing has been deleted from either package, just root and busybox being added.
Deodexed v. stock is mainly for ease of modification. After the first boot, there is no speed difference in the two, though you may save a little bit of storage on the stock version. Functionally, they are identical, just that if one was looking to theme or make other changes, it is easier to do on the Deodexed version. I plan on starting a ROM then, maybe with the help of a few people, and this will start with the deodexed version and will get its own thread if it comes.
Just to answer any future questions, if you're already rooted, you don't need this. It was created as a better starting point for anyone that has not yet rooted their phone.3
Yeah, going to try to get something together working with someone else
I can do pretty much everything ROM-wise without a phone, minus testing. While having a device would make it easier, it will just save time really as I wouldn't need to find someone to test for me.
Also, this root package was built from the official firmware and not a dump from a phone.2
I'll get it uploaded to a mirror when I can, but the reason that it is likely slow is due to the number of downloads it's getting. I have had 1100+ downloads and counting of the root package, another 450 of the deodexed root package, 250 downloads of the stock Odin, and another 125 of the straight deodexed files. That is 2.1 TB of bandwidth in less than a week. I didn't think it would be an issue with downloads as I've never had a problem in the past, even with big hits in bandwidth, but the downloads have pretty much been continuous since posted, so I guess it does eventually get affected. You'll just have to live with it until I can get it mirrored.
