yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 10.1 Android Development] Superion:
Hello all! OK, so I have a Galaxy 10.1 3G Wi-Fi (N8013), running 4.1.2. I've been trying to figure out how to root it, and so I stumbled upon this thread in my searches. But I'm also wanting to upgrade my tablet to 4.4.2 (KitKat), and that's where things get muddy. Some posts I saw said it wasn't possible, that there wasn't a 4.4.2 release for this device. Others say that it is available OTA, but have reported problems using method 2 to root their device...some people have responded to that by suggesting de-selecting the "auto-reboot" option on Odin when flashing, but success seems to be mixed.

Bottom line: I'm THOROUGHLY confused! I seem to recall from the instructions that I cannot root my device and then obtain 4.4.2...that will remove root. Can someone give me a definitive answer to upgrading my Note 10.1 to 4.4.2 (if I can even find that option!), and THEN rooting using method 2? Will that work?
[Galaxy Note 10.1 Android Development] xlebronx:
I need quick solution because I'm a student and I need this tablet!

I have a problem with my N8013. When I install root, cyanogenmod or stock rom touch pad not working. But S-Pen still working.. I tried *#2663# with dialer get "Unfortunately, Factory Mode has stopped". But *#06# works except null imei number.

What can I do solve this problem?

Please help me!

Best regards,
[Galaxy Note 10.1 Android Development] Komodoketavaran:
Does method2 works on 4.4.2 stock now? Or can i forget about to root it?

Gesendet von meinem GT-N8000 mit Tapatalk
[Galaxy Note 10.1 Android Development] Komodoketavaran:
Nobody knows ?

Gesendet von meinem LG-D290 mit Tapatalk
[Galaxy Note 10.1 Android Development] kraghh:
The web site referenced in this thread, rootgalaxynote.com, seems to have died. Does anyone have info on that? Or a different web site for same material? Or, pointer to another thread or method for rooting the Samsung GT-N80xx series? Thanks.
[Galaxy Note 10.1 Android Development] ST Dog:
The way back machine has it archived.

http://web.archive.org/web/20170606...t-galaxy-note-10-1-easiest-methodcwmmethod-2/

And the download site appears to still have the fikes, you just have to copy the URL and go to the site instead of the archive.

http://downloadandroidrom.com/file/GalaxyNote10.1/rooting/RootGalaxyNote10.1.zip

I have several files saved on Mega (philz, CWM, and more stuff), but would need to search threads to see what they are and how to use them.
[Galaxy Note 10.1 Android Development] locolyric:
i am able to flash cwm, but the root is not working.

downloading lineage 14 and magisk right now.
[Galaxy Note 10.1 Android Development] JJEgan:
Suggest looking at one of the later root tools threads.

I flash

supersu.zip for root.

As per the initial post one .
[Galaxy Note 10.1 Android Development] Gromhelm:
I have a GT-N8013 and followed the steps for Method 2 until I am in Android system recovery. The problem is, I don't see "Install zip from sdcard". These are the options I have:

- reboot system now

- apply update from ADB

- apply update from external storage

- wipe data/factory reset

- wipe cache partition

- apply update from cache

Is there any solution to this issue?

[edit] Got it! I had to disable auto-reboot in odin as suggested earlier

[edit2] Strange, I did everything but Titanium Backup says I don't have root privileges :(
[Galaxy Note 10.1 Android Development] JJEgan:
You cannot install zip from stock recovery that's a basic.

Flash custom recovery via Odin.
[Galaxy Note 10.1 Android Development] hihgwayxda:
I am looking for a ROM from 5.0 for the purpose of manage a USB sound card (5.0 onwards) ¿Why do you think is the better choice?

Thank you very much

Enviado desde mi SM-G930F mediante Tapatalk
[Galaxy Note 10.1 Android Development] JJEgan:
Sorry not a clue about usb sound.
[Galaxy Note 10.1 Android Development] zenhck:
Can I just flash twrp via odin without rooting it first and directly flash custom rom? I have done it many times before on other device. And which custom rom is good and bugless?
[Galaxy Note 10.1 Android Development] zedomax:
Yes of course! Flash Twrp, install rom.
[Galaxy Note 10.1 Android Development] zenhck:
which rom do you suggest for me to flash? I have N8000 version
[Galaxy Note 10.1 Android Development] JJEgan:
TWRP. flashed via Odin as a tar file.

You pick your rom.

Not many live roms now.
[Galaxy Note 10.1 Android Development] zenhck:
what rom r u using
[Galaxy Note 10.1 Android Development] JJEgan:
Stock uk O2 firmware rooted only.

RU is Russian firmware ??
[Galaxy Note 10.1 Android Development] tinybutstrong:
Someone would mind to give me a hand to accomplish the rooting. I just followed the video instructions, but after to restart to recovery there is no CMW for my surprise, I get the Android system recovery. Any hint what to do? As you can see I'm a little newbie.

Odin result:

<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)

ERR found the solution, it is very simple, read bellow:

https://xdaforums.com/showthread.php?t=1831152&page=64#634
[Galaxy Note 10.1 Android Development] ST Dog:
From the old site I linked:

Q: I don’t see ClockworkMod Recovery when I enter recovery, I see stock Android recovery.

A: With newer software updates, you may be encountering this error because it will overwrite ClockworkMod Recovery upon reboot. *To get around this, simply boot into ClockworkMod Recovery right after flashing in ODIN. *You can set auto-reboot off in ODIN then when done, just hold down Power and Volume Down straight to bootloader menu
[Galaxy Note 10.1 Android Development] tinybutstrong:
Yeah, I managed to get it working, thanks. My problem now is that "adb reboot bootloader" just boots normally and if I try boot to bootloader holding power + vol - buttons it doesn't accept any fastboot/adb command there. I need to install TWRP.
[Galaxy Note 10.1 Android Development] ST Dog:
Yeh, I don't think that CWM supports ADB (not sure any version does, it's been a long time).

But for sure get TWRP.

https://dl.twrp.me/n8000

https://dl.twrp.me/n801x

Not sue I ever tried to enter recovery with ADB on this device.

But the command is reboot recovery

bot bootloader.
[Galaxy Note 10.1 Android Development] tinybutstrong:
Interesting, in this case how to flash TWRP? o.0

>adb devices

List of devices attached

4107b2a8005f7f67 device

>adb bot bootloader

adb: usage: unknown command bot

>adb reboot bootloader

(just boots normally to Android)

>adb reboot recovery

(CWM recovery GUI, can't flash TWRP from there, right? it is a .img file)

>fastboot command doesn't work at all, stuck in "waiting for any device"

---------- Post added at 01:15 ---------- Previous post was at 00:51 ----------

Oh, problem solved. I just converted TWRP .img to .tar and used Odin software to flash it.

More info:

https://xdaforums.com/note-4/general/convert-twrp-img-to-tar-odineasy-t3355944

https://www.theandroidsoul.com/how-to-install-twrp-recovery-using-odin/

Thanks ST Dog!
[Galaxy Note 10.1 Android Development] ST Dog:
Once you have root you can use Flashify or manually with dd from a root shell.
[Galaxy Note 10.1 Android Development] erikjonpeterson:
Same here. Seems like the OTA will screw up current root methods.
[Galaxy Note 10.1 Android Development] chrisreese:
I'm having the exact same problem. I was rooted, reverted to stock and applied the OTA, now I can't get CWM load. Odin shows that everything flashed without errors, but it still boots into the stock recovery.
[Galaxy Note 10.1 Android Development] knives of ice:
Yep same here....man been so long since I didn't have root on a device it really does suck not having it to block ads on websites
[Galaxy Note 10.1 Android Development] jjsam:
Thanks. Will give this a try. If not, I'll have to return mine. :(

---------- Post added at 11:47 PM ---------- Previous post was at 11:41 PM ----------

I got mine from amazon and will see if they will do an exchange. If not, I'll have to wait for a solution... hopefully sooner then later, as is, mine won't shut off and stuck in an endless update loop. Think I'll reflash it with method 1 again and see.
[Galaxy Note 10.1 Android Development] crystalstylez:
Sounds like they have it just like the tab 2 10.1 now. Cwm will have to have a setting to disable this. Its basically reflashing the stock recovery upon reboot. Flash odin but untick auto reboot. After its done power the tab down manually and power it back up / go in to cwm the manual way. I rooted 2 tab 2 10.1s today and had the same issue until i did it that way.
[Galaxy Note 10.1 Android Development] BeerChameleon:
so this worked for you?

So:

1. Flash CW in odin and make sure all is unchecked including auto reboot.

2. Power down manually and power back on and boot into clockwork?

This will work?
[Galaxy Note 10.1 Android Development] crystalstylez:
Just uncheck auto reboot. I have not did this tablet yet but those senarios are the same exact issues i had while rooting the tab 2 10.1 today. Until i didi it this way , it did not work. Therefore ita probably same senario.
[Galaxy Note 10.1 Android Development] BeerChameleon:
well test it and let us know. I could test it when i get off work in a couple hours.
[Galaxy Note 10.1 Android Development] vanillanesquik:
Tested, works! Just don't auto-reboot in odin.

I accidently flashed the old kernel on top of the new one and my pen wont function. Is there anyone that can make a flashable odin or cw dump of the new one?
[Galaxy Note 10.1 Android Development] crystalstylez:
Great figured thats what was happening like the tab 2
[Galaxy Note 10.1 Android Development] BeerChameleon:
Alright!!! Thanking you both in a sec, let me get on tapatalk to bypass the thank limit :p

---------- Post added at 04:21 PM ---------- Previous post was at 04:15 PM ----------

Cant u just odin the whole new rom? :confused:

Yes i know its a pain, But its an option.
[Galaxy Note 10.1 Android Development] vanillanesquik:
I have not rebooted the tablet yet since entering into CW so whether it will flash stock recovery on reboot I cant say for sure. I am making a backup in case I do not get a flashable version of the new kernel.

I had an issue that has not been posted yet. After updating firmware through kies I tried to flash CW through ODIN and managed to disable all touch functions. I freaked out and flashed stock recovery and no change. I then flashed the stock recovery/kernel and my touch functions returned but lost pen function. I am hoping there is some way to overcome this without reflashing the whole system via odin.

I downloaded the ODIN file uploaded by jaaka78 but to my knowledge this will wipe all data which is my last resort. I have made a CW backup just in case this goes south. I wish I waited a bit longer for this root method.
[Galaxy Note 10.1 Android Development] BeerChameleon:
If i lost a feuture like s pen abilities or touchscrenn I would Flash Full Odin firmware stat. :eek: Just me.

Also can you try rebooting the go into clockwork?
[Galaxy Note 10.1 Android Development] vanillanesquik:
Yes rebooting recovery took me straight to CW so SUCCESS!

When making CW backup does it also backup the current kernel? if i was to odin the new ROM then restore CW I would be in the same situation right?
[Galaxy Note 10.1 Android Development] BeerChameleon:
A full backup I believe backs up everything. I haven't backed up anything in clockwork or TWRP in forever LOL I just wipe and restore apps with titanium. :p
[Galaxy Note 10.1 Android Development] vanillanesquik:
Backing up via Titanium at the moment then flashing the Kies MD5 that was posted.

I flashed the MD5 file and it completed successfully but my system was not wiped and the faulty kernel is still present. Is there anyone who can help me with this issue. I need the new kernel/full system wipe so I can fix this.

Thank You
[Galaxy Note 10.1 Android Development] Entropy512:
The issues with entering recovery may be due to the OTA updating the bootloader.

I'm not sure. I pulled the update ZIP and also pulled my current bootloader after seeing that the OTA update touches mmcblk0p1

I would not advise that anyone accepts the OTA until it's found whether the bootloader is the root cause of these recovery issues.

In addition, the OTA adds a new script at /system/etc/install-recovery.sh which will generate a recovery image from the stock kernel, if you're running the stock kernel.

Also, it binary-patches each file - so if one file mismatches it's probably going to bomb out. My guess is there's something slightly modified in zedo's drop beyond just adding su and Superuser...
[Galaxy Note 10.1 Android Development] BeerChameleon:
Too late lol i did this at 7am this morning. Also is it still ok to root using the 2nd method? It seems that if you dont check reboot in odin it seems to work.
[Galaxy Note 10.1 Android Development] Entropy512:
Yeah, and once rooted you can nuke /system/etc/install-recovery.sh so it doesn't keep nuking CWM.

If anyone wants to pick apart the OTA - http://d-h.st/b21 - Again, I do not advise flashing this.
[Galaxy Note 10.1 Android Development] knives of ice:
i just tried it and it definitely does not work for me. i've never had root this is a brand new unit that i accepted the update on. checking not to reboot in odin made no difference when i go to boot into recovery it is still the stock android recovery not CWM and i'm flashing everything correctly with success in Odin so i know thats not the problem.
[Galaxy Note 10.1 Android Development] Entropy512:
You have to boot IMMEDIATELY from Odin into recovery - If you don't, install-recovery.sh will run.
[Galaxy Note 10.1 Android Development] crystalstylez:
Make sure when you untick auto rebbot and odin is finished, to hold the power button to turn off. The press and hold the power + vol down until you see the logo. Once logo appears let go of power and continue holding the volume down. This should boot you in to CWM. If the cmw is the newest it may give you the option to disable that script as it did when i did the tab 2 10.1 today. It should work this way. If it does not boot in to cwm you didi something wrong and start over.
[Galaxy Note 10.1 Android Development] knives of ice:
Excellent thanks. I assume its done by first shutting off then holding volume up again
[Galaxy Note 10.1 Android Development] BeerChameleon:
So i shouldnt have issues rooting if i boot directly into clockwork then booting then delete the above file?

Also do we have an md5 tar for the original rom before the update?
[Galaxy Note 10.1 Android Development] Entropy512:
What I can't figure out is that I don't seem to have that install-recovery script on my system... I flashed the .tar from http://xdaforums.com/showthread.php?t=1847706

Has anyone tried to reboot a few times after the flashed the KIES dump?
[Galaxy Note 10.1 Android Development] jjsam:
Nope, reflashing with UEALGB release does not fix the update loop. After flashing, it reboots and continues with the OTA update and gets stuck at 100%... holds for a couple minutes before rebooting only to continue the loop once again.

On one of the other threads, I did find a suggestion to use the stock recovery (found on method 2), which claims it works. To a degree, it did, it cause the OTA to fail and when the note rebooted, it booted into Android again... but upon closer inspection, it did cause 1 binary count. Now I'm not sure what to do, perhaps look for stock GT-N8013 to restore to stock and wait a while for further development before rooting again.
[Galaxy Note 10.1 Android Development] knives of ice:
Thanks...this fixed it
[Galaxy Note 10.1 Android Development] akxak:
I installed the update via Odin (as it was not offered OTA) and had to reinstall CWM. But at least in the version here, recovery seems not to be reinstalled. I just rebooted my device, CWM was still there and there is not install-recovery.sh /system/etc.
[Galaxy Note 10.1 Android Development] Entropy512:
Some people are claiming they got it via kies, others didn't. You and I both seem to have gotten clean updates without that crap.

The OTA will definitely install that install-recovery stuff.

I wonder if there's some logic that will only put in install-recovery if it thinks recovery is corrupted? I didn't have CWM installed when I flashed.
[Galaxy Note 10.1 Android Development] BeerChameleon:
Well F*CK, i tried the clockwork method and i don't know if i messed something up when trying to reboot in clockwork and the scrolling but no i have no touch screen/ pen, i am downloading the odin file hopefully it will fix it. :(
[Galaxy Note 10.1 Android Development] knives of ice:
there is no touchscreen support in this version of CWM that is loaded you need to navigate with the volume buttons and use power to confirm a selection. hopefully at some point soon we'll get TWRP support.

ok so this version of rooting worked after booting directly into CWM from Odin, but if you try to go back into recovery after rebooting the device it goes back into stock recovery, but i still maintain root. do i delete the file mentioned above as soon as a flash CWM the first time from odin as soon as my tablet reboots to prevent this?
[Galaxy Note 10.1 Android Development] iofthestorm:
Rooting instructions for new OTA

Actually, it does have touchscreen support but it's flakey. If you don't want to flash something random accidentally don't use the touchscreen lol.

Here's my concise version of what to do to get root and CWM with the new OTA. No offense zedo, but I hate watching videos for things that could be explained in a few lines of text :P

0) Copy the SU/superSU zip file to your tablet.

1) Boot into ODIN mode by holding volume down and power. Volume down is the one closest to power.

2) Open ODIN on your computer, select the CWM tar.md5 file in the PDA slot, uncheck auto reboot.

3) Hit start. It should flash recovery successfully

4) Now you want to boot directly into CWM, or you'll lose it. So while holding down volume UP (the one farther from power), hold down the power button. When you see the Samsung Galaxy Note 10.1 logo, let go of power, or else you'll keep rebooting, but keep holding volume UP. Or at least that's what I had to do, which was kind of surprising coming from other Samsung devices.

5) Once in CWM, flash the superSU zip file. Congratulations, you have root, but if you reboot now the firmware will nuke CWM. We don't want to have to flash it again, so let's remove the shell script that nukes CWM.

6) Under mounts and storage in CWM, mount system.

7) Back on your computer, run adb shell. If you forget to mount system it'll complain because it can't find sh, silly adb. For a second I thought Samsung didn't include sh out of the box and then I realized that makes no sense.

8) Type su to become root

9) rm /system/etc/install-recovery.sh

Congratulations, now you've got CWM and su and Samsung won't do anything about it.
[Galaxy Note 10.1 Android Development] JojoSteez:
This is what I did but CWM asked if I wanted to fix the recovery from being overwritten. I selected yes and all is well. I can boot into CWM every time.
[Galaxy Note 10.1 Android Development] iofthestorm:
Oh weird. By the way, I lost S Pen support after rooting so maybe those on the OTA should not root. Is yours still working?
[Galaxy Note 10.1 Android Development] BeerChameleon:
Mine isn't rooted but, I tried rooted and got into clockwork but I tried scrolling with my fingers I know stupid and I think I hit something I wasn't suppose too and caused my touch screen to complete lay give out then I tried a bunch of stuff and the only way to get touch back no pen is flash a stock kernel/recovery that entropy posted in another thread. What is weird is I am on the latest update and kies says it too and I don't know where to go from here.

Can someone post a pic of clockwork mods advanced options and options please to see if I can find what I accidently hit?

Sent from a Baked Black Jelly Belly
[Galaxy Note 10.1 Android Development] californiarailroader:
So rooting kills the S Pen functionality? That's weird, I know on the AT&T Galaxy Note (i717) that some ROM's can kill it, but rooting killing it is new. I was just about to root mine, but I am going to wait until that is sorted out.
[Galaxy Note 10.1 Android Development] crystalstylez:
It does not. I used method 2 and my pen is fine.
[Galaxy Note 10.1 Android Development] californiarailroader:
Thanks, I think I'll go ahead and root it! I was going to use Method 2 anyway, but I wanted to make sure.
[Galaxy Note 10.1 Android Development] Entropy512:
It seems far more likely to derp up if you use CWM than if you use a root-injected image - I have a complete root-injected package in the Development section (root-injecting stock firmware isn't original...)
[Galaxy Note 10.1 Android Development] BeerChameleon:
Thank god for entropys triangle away kernel and triangle away.

I am now on the latest firmware and rooted with clockwork :D
[Galaxy Note 10.1 Android Development] opimpao:
Is there any way to remove the binary count on my note 10.1? I don't know all of the implications of having the count increase but I have seen ways to remove the count on my SG3. I didn't realize that I needed to uncheck the auto reboot in Odin and so I ended up with a count of 2. Is it bad to have the count get high? Is there a limit to the amount of times you can flash?
[Galaxy Note 10.1 Android Development] BeerChameleon:
yes..

Download Entropys TA kernel.

Launch the triangle away app. Costs 2.50 on the market. reset the count. Then change back to stock kernel cause of wifi issues on that kernel.
[Galaxy Note 10.1 Android Development] Mhbr549:
Do we have the kernel in a flashable tar for the updated ROM? I missed that link if we do.
[Galaxy Note 10.1 Android Development] BeerChameleon:
Its a flashable tar via odin. I am unsure if it is based off the new or old firmware. But it saved my note!! :)
[Galaxy Note 10.1 Android Development] Mhbr549:
Where is it?
[Galaxy Note 10.1 Android Development] BeerChameleon:
In original development :rolleyes:

Sent from a Baked Black Jelly Belly
[Galaxy Note 10.1 Android Development] iofthestorm:
Rooting in combination with the OTA might kill functionality. I was able to get it back by flashing Entropy512's ODIN dump though. If you want to upgrade I would just flash that rather than root separately. I don't know if zedo's CWM has issues or what the problem is.
[Galaxy Note 10.1 Android Development] skeeterpro:
You used the pre-rooted ODIN or stock non root?
[Galaxy Note 10.1 Android Development] iofthestorm:
I used Entropy512's pre rooted Odin. Although in that thread there was one guy who had the exact opposite experience as me, he flashed that and it broke his S Pen and going back to the old version and rooting fixed it. To me it seems like the update is probably not worth it, I think there's something finicky about the touch screen and S Pen drivers that causes them to freak out when you flash stuff.
[Galaxy Note 10.1 Android Development] skeeterpro:
Interesting. Unfortunately I've already taken the OTA. Does Entropy's pre root ODIN include the OTA?

Ah. Look like it does upon further review. Might ride this out for now before rooting. Looks like davidrules CWM instructions might be the way to go right now.
[Galaxy Note 10.1 Android Development] BeerChameleon:
Well something is up with the update considering the pulled it it seems.. but I am on it and rooted and doing just fine, but it wasn't easy figuring out how to fix my touch screen and spen

Sent from a Baked Black Jelly Belly
[Galaxy Note 10.1 Android Development] Mhbr549:
Samsung pulled it?
[Galaxy Note 10.1 Android Development] skeeterpro:
I can well imagine!

Too bad there isn't an ODIN-compatible copy of pre-OTA LG2. Or at least I've not encountered one.