yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 10.1 Android Development] surfdev:
I'm sorry if this has been asked before but I couldn't find it in this thread.

I used Method 1 and haven't done the OTA update yet. I am having problems mounting the system partition as rw just like others are reporting with Method 1. I am wondering if there is any way I can fix it without updating to the new OTA firmware. I read that if I Odin CWM and then flash SU on top of the root injected firmware, it will cause a bootloop.

any ideas?

Thanks! :)
[Galaxy Note 10.1 Android Development] Mhbr549:
Wow. Dejavu man. That was my issue too (think I was actually the first to report having that problem). I ended up having to return and exchange mine due to the bootloop because there was really not anything out to help me fix it yet. If I had it to do over again though, I would feel a lot more confident now with the new kernel that Entropy put out, as well as his preinjected root tar file that I have posted here: https://hotfile.com/dl/168708093/504b8e2/UEALH2_prerooted.tar.7z.html.

Also the stock UEALH2 is here if you want to Odin flash it: http://www.peejeshare.com/files/363...ALH2_1015435_REV00_user_low_ship.tar.rar.html

I'm not sure about trying to re-root using CWM method 2 in your current situation. I would definitely not let it update OTA though. If you do update, I would use Odin personally. Most of the issues I've read were from people who allowed OTA.

If I had it to do over again, I would likely flash the stock UEALH2 firmware, and then root using CWM method 2. If I ended up in a bootloop, I would then flash Entropy's new Kernel and see if that fixed it. Get other's opinions though before you jump on my advice. I am NOT an expert on all things Note 10.1.
[Galaxy Note 10.1 Android Development] californiarailroader:
I still haven't rooted mine, maybe I'll wait until all the little issues get fixed. I have been rooting for a long time now, but the rooting methods for this, at least right now, seem iffy at best.
[Galaxy Note 10.1 Android Development] skeeterpro:
Yeah. Think I'm on board your "train of thought" also.....:D
[Galaxy Note 10.1 Android Development] BeerChameleon:
Rooting method of clockwork work fine.. just be careful of what u press when scrolling through I recommend using the volume to scroll and zedomax says that too, then flash twrp recovery and you will be set :D

If you lose spen or touch screen Odin stock or of that doesn't work odin prerooted tar and entropy kernel with triangle away and reset your count, these are the ways that have fixed pen and touch screen problems

Sent from a Baked Black Jelly Belly
[Galaxy Note 10.1 Android Development] Z a p i x:
Used the CMW rooting method, then got the OTA notice. Copied the update zip to the sd card directory and tried to update through CMW (as I have with my S3), but it didn't work. Odined back to stock recovery, and ran the update. it failed around 24%. Error 7 iirc and it suggested updating via Kies. Updated via Kies (which worked, just took a while to install Kies PC), and Odined back to CMW and re ran the SU zip. Didn't have to reset or anything. Problem free. Not losing CMW, and touch screen and s-pen didn't stop working.
[Galaxy Note 10.1 Android Development] BeerChameleon:
Nevermind miss read this...

Sent from my GT-N8013
[Galaxy Note 10.1 Android Development] californiarailroader:
Well, I'm already on the latest OTA Update, ULEAH2, so what method would be best to use?
[Galaxy Note 10.1 Android Development] BeerChameleon:
Use the cclockwork method, then get goo manager app and install open recovery twrp. Then u will be set :)

Sent from my GT-N8013
[Galaxy Note 10.1 Android Development] californiarailroader:
Excellent, thanks David!
[Galaxy Note 10.1 Android Development] BeerChameleon:
Btw when u root via cw make sure in Odin u uncheck auto reboot and check f reset time ;) then boot directly clockwork flash superuser zip, then via a root explorer like es file explorer check under system/etc/install-recovery.sh if u see this sh file delete it ;)

Sent from my GT-N8013
[Galaxy Note 10.1 Android Development] californiarailroader:
CRAP, I lost all touch on my screen, why does this thing have to be so complicated?

Edit-Thank goodness for this-

http://xdaforums.com/showthread.php?t=1849994

I'll just download TWRP from Goo manager after I am up and running again.

---------- Post added at 12:39 AM ---------- Previous post was at 12:15 AM ----------

So this file flashed successfully in ODIN, then it rebooted and it's stuck on Andy with the spinning globe, now what? I knew I shouldn't have gone through with this :(

Update:It gets to about 30%, then sits there for several minutes, and then reboots, rinse, repeat. what the crap? It looks like I might have to do an exchange with Amazon, this stinks. I'm stuck in an endless loop :( MAD MAD MAD, now I have a useless tablet, GRRRRRR, off to Amazon to get an exchange, unless somebody can figure out how to fix this.

---------- Post added at 12:51 AM ---------- Previous post was at 12:39 AM ----------

I'm flashing it again, if this doesn't work then it's definitely exchange time.
[Galaxy Note 10.1 Android Development] Z a p i x:
Dunno if it will help or not, but have you tried to run Odin again using a different USB port and/or different cable? As a once non believer in the whole cable bit, I've learned first hand the cable can make difference. Once thought I had completely bricked my Epic 4G -.- Was not a good night, but it ended well after I tried a different cable. Might not help, but worth trying imo if you can.
[Galaxy Note 10.1 Android Development] californiarailroader:
I will try that, thanks! Yeah, I've had to change cables and ports on devices too, let's hope for a successful operation! :D
[Galaxy Note 10.1 Android Development] akxak:
Keep gentle... rooting is a process not supported by Samsung (and even more not appreciated by them). It lowers certain security barriers which is a risk for users not knowing what they are doing.

So the process uses internal tools (although the manufacturers could add such a feature on their own similiar to developer options combined with a clear warning).

There are several threads regarding these kind of problems but normally, as long as you can get the Note into download mode, you can reflash with Odin.

What I did:

- Got my stock Note 10.1 (N8000, 3G, 16 GB, Europe).

- Installed CWM 6.0.1.1 with Odin

- Installed SuperSU.zip with CWM

- read about the OTA updated, checked for an OTA update but found none

- connected to Kies, the update was offered and installed

- SuperSU and CWM gone (the update overwrites the whole part)

- Reinstalled CWM as above.

- Reinstalled SuperSU.zip as above

- Downloaded TriangleAway and sucessfully reset the flash counter from 2 to 0 (strictly follow the instructions if you do that!)

Result: Note 10.1 running smoothly. Thanks to zedomax and chainfire, excellent work.

From what I read here, you could try Kies to completely restore the Note 10.1 or reflash a stock rom for your device (if one is here). Then try CWM and SuperSU.

From my point of CWM as recovery does not interact with the main Android system. SuperSu simply adds two files allowing to gain root priviledges.
[Galaxy Note 10.1 Android Development] californiarailroader:
I will try that next if this doesn't work, thanks

Edit-Kies it is, I couldn't get the other way to work. Man, Kies is sure taking a long time to install.
[Galaxy Note 10.1 Android Development] Z a p i x:
In Kies under the TOOLS option, there's an option Emergency firmware recovery

Guessing that's what you'll want to use! Good luck! :D

And to root, do exactly as akxak suggested. That's the same thing I did. Easy and it works.

Oh, and my guess is Kies if it restores the tablet to working will likely upgrade the firmware as well. If so, that will be one less step.
[Galaxy Note 10.1 Android Development] californiarailroader:
Thanks, Kies is asking for a recovery code now, what is it?

---------- Post added at 01:54 AM ---------- Previous post was at 01:37 AM ----------

Another issue, when I select Emergency Recovery the device disconnects, and disappears from my PC.
[Galaxy Note 10.1 Android Development] californiarailroader:
Well, I've tried everything, I did finally get it back up, but when I remove the S Pen, all touch response ceases. I tried flashing the rooted, stock odin file, the stock, unrooted odin file, stock kernel, reset, wiped, same thing touch disappears when the S Pen is removed (or when it's left out, then put back in). So, unless you guys know another thing to do, I am going to get an exchange with Amazon.

I think the problem is that none of those files wipe the device, and I can't get it to do an emergency firmware update in Kies, when I select the option to do that it drops the connection to the Note 10.1.
[Galaxy Note 10.1 Android Development] akxak:
Do you have the note in download mode when trying this (Power off, Power on with Power on and Volume down pressed, confirm the question with volume up)?
[Galaxy Note 10.1 Android Development] californiarailroader:
Yep, it wouldn't even recognize the device when in download mode. I FINALLY got my touch and S Pen back though, by flashing this kernel-

http://xdaforums.com/showthread.php?t=1849015

So, I'm back up again, FINALLY :D

---------- Post added at 05:35 AM ---------- Previous post was at 05:00 AM ----------

Okay, after getting back up I rooted using the CWM method-

1.Flash CWM

2.Immediately boot into recovery

3.Flash SU

4.Reboot

5.Download Goo Manager

6.Open Goo Manager, install recovery

7.Recovery installed, reboot into TWRP successful

8.Get some sleep, what a night! LOL

So, I'm rooted now with TWRP, and on the latest OTA, yay!
[Galaxy Note 10.1 Android Development] Z a p i x:
Glad to hear you recovered from the original attempt!
[Galaxy Note 10.1 Android Development] mpazevedo:
Incomplete Nandroid backups

I have been having incomplete backs on both TWRP and CWM. It gets to the last file during system backup and then it reboots with any notification if it was complete. I got root via the first method then installed TWRP via goo manager. Once in recovery I tried to make a back up to internal and external sd card. I thought it might be TWRP so I then grabbed the tar file and extracted the recovery.img file from the CWM and dd via android terminal. Rebooted to CWM recovery and am having the same issues trying to back up to internal or external SD card. 32gb btw fat32. It keeps rebooting at the very end of the backup. Anyone else having this experience?
[Galaxy Note 10.1 Android Development] Entropy512:
I had that occur multiple times yesterday.

For whatever reason, this device is highly prone to /system getting corrupted. The nature of the corruption is such that the device works normally, EXCEPT /system gets force-mounted as read-only. In addition, if you try to do a Nandroid backup, the device reboots due to a hung-task timeout.

I think there's some subtlety with how root-injected Odin-flashable images are built that this device doesn't like - Every root-injected image that has been built for this device has weird-ass problems I've never seen before, the issue I had last night and you describe is one of them.

In my case, I used dsixda kitchen to take the UEALH2 Kies dump and make a deodexed CWM-flashable system ZIP out of it. (Note: Some additional work needs to be done for dsixda kitchen with this device, it will not generate a usable update-binary and the updater-script format/mount commands must be manually fixed.) That backed up fine.

The "fugly hack" workaround is to enter CWM and format system before the backup. Then you will get a backup with everything BUT /system backed up - to restore the device from that backup you'd need to restore, then flash /system in Odin.
[Galaxy Note 10.1 Android Development] Mhbr549:
Have you had any experience or feedback from anyone who has tried to do backups who rooted via CWM method 2 and not the root injection? I'm getting close to pulling the trigger on rooting this new unit but can't push myself over the edge yet until I feel safe with it. Also, I know this isn't the correct forum for it, but I can't seem to get any feedback or find info on what was included in the UEALH2 update. Do you know? I can't decide whether to update prior to rooting or just root the old firmware. What do you think?
[Galaxy Note 10.1 Android Development] SoCaliTrojan:
I have flashed both methods and still can't mount the system partition. ES file explorer can mount it right after the first boot from a flash, but before I can even rename a system file, it fails. I get a "failed to mount" message afterward after trying to unmount and remount.

As for the boot loop, I think you should have a couple of firmware downloaded. I downloaded one firmware and the same firmware from someone else's mirror of that firmware. One of them causes my device to boot loop, while the other one doesn't. Both should be the same, unless one was uploaded with an error.
[Galaxy Note 10.1 Android Development] californiarailroader:
Thanks, me too! I thought for sure I'd screwed it up.
[Galaxy Note 10.1 Android Development] cyfunger:
Help Needed in Rooting the ZSALG7 Rom Version

:crying:My rom version is the ZSALG7.

I have followed the whole instruction carefull and flashed the rom several times, but still I can't install ClockworkMod Touch Recovery to my tablet, except the custom binary download count has been increased to 4!

What should I do to get root?

How to reset the custom binary download count to zero?

I desperately need your help in rooting the device and reseting the binary count!:crying:
[Galaxy Note 10.1 Android Development] zedomax:
Try just following one method, you shouldn't have to root twice, either root-injected or CWM. How are you trying to mount the system partition? ADB remount does not work (You have to remove some files for that), you can use this instead in adb if you are trying to mount:

mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
[Galaxy Note 10.1 Android Development] californiarailroader:
I wouldn't get too upset about the counter thing, I haven't yet heard of anyone denied warranty or return service over it.
[Galaxy Note 10.1 Android Development] zedomax:
what is exactly happening when you install CWM? Binary count can be resetted (not sure if triangle away supports it but Entropy confirmed working).
[Galaxy Note 10.1 Android Development] californiarailroader:
I think you mean reset ;) :D
[Galaxy Note 10.1 Android Development] zedomax:
damn reset doesn't have past tense? damn broken auto correct!
[Galaxy Note 10.1 Android Development] jsitta:
So I have a note with the update, but I'm not very excellent at working with mobile devices. Some of my must-have apps require root, so I will eventually have to follow someone extremely wonderful's guide. With all the reported problems, I'm worried this method might be over my head. Is it reasonable to wait for someone to engineer an idiot-proof method,or do I just need to suck it up and hope for the best with this method?
[Galaxy Note 10.1 Android Development] zedomax:
If you are worried, just use the CWM method 2, very easy, it only gives you custom recovery and you root.
[Galaxy Note 10.1 Android Development] SoCaliTrojan:
I just tried it and it gave me an error saying read-only file system.

I know triangle away works because i had to use it when i tried method 2 hoping to be able to mount /system
[Galaxy Note 10.1 Android Development] jsitta:
Thanks for this extra little bit of guidance, Zedo.
[Galaxy Note 10.1 Android Development] Entropy512:
Since we have kernels that support TA, triggering the flash counter is less of an issue than it previously was.

That said, I really want to figure out why both prerooted images available consistently result in corrupted /system partitions - These partitions cannot be mounted RW, and will cause a reboot due to hung task timeout if you try to do a Nandroid backup.

I won't be able to look at this until this weekend - it's a problem for both Zedo's UEALGB and my UEALH2.
[Galaxy Note 10.1 Android Development] BeerChameleon:
While or doing that can u provide a stock non rooted tar for the old firmware?

Sent from a Baked Black Jelly Belly
[Galaxy Note 10.1 Android Development] zedomax:
Did you type "su"?
[Galaxy Note 10.1 Android Development] Entropy512:
It would suffer from the same issues - Odin needs "sparse" ext4 images for flashing. Somehow the process of "sparsifying" these images is causing them to be bogus. It's weird, I've never seen this before.

I've got one idea to look into this weekend when I get back from my trip... It might be necessary to tell the image build tool that the partition is a few megs smaller than it really is - only thing I can think of at this point.
[Galaxy Note 10.1 Android Development] SoCaliTrojan:
Yes, of course. Otherwise it would say that the operation is not allowed.
[Galaxy Note 10.1 Android Development] zedomax:
Oh, same thing happened to me earlier, you can simply update binaries in SuperSU, then try again, it will work fine after that.

Just run SuperSU at least once after rooting, and also make sure to kill any rooted apps after doing that. cheers.
[Galaxy Note 10.1 Android Development] SoCaliTrojan:
I ran SuperSU, then rebooted. It successfully mounted, so I tried to update my ad- blocking software. The software failed. l then tried to re-mount, but got the error message again that it is a read-only file system. Such a weird problem...
[Galaxy Note 10.1 Android Development] surfdev:
Thanks for looking into it Entropy. I'm also stuck with the same thing.

perhaps providing a stock old firmware that we can Odin and then root using method 2 would be a good temporary solution.
[Galaxy Note 10.1 Android Development] zedomax:
It might be a problem with the Ad blocking software, see if you can use ES File Explorer and mount.
[Galaxy Note 10.1 Android Development] SoCaliTrojan:
No, apparently it will only mount for a second before becoming read only. I cant even rename a system file fast enough (Shutter.ogg to Shutter.off...yes, i don't like my devices making sounds). Basically i can only mount it for like 3 seconds after a reboot before it becomes unmountable.

If i use ES file explorer, this is what happens:

1. Click "mount file system". 1st time results in successful mount.

2. Click on it again to unmount.

3. Click it a 3rd time (and each successive attempt) results in "failed to mount."

None of my root apps can mount /system. Terminal, for instance. My device works otherwise...i just have to learn to ignore the ads until this problem is fixed...

I read somewhere that you bought your device from somewhere that had it in stock before everyone else. Could it be that yours is from an earlier batch that doesn't have this issue?
[Galaxy Note 10.1 Android Development] antique_sonic:
Hi zedomax,

I have googled for rooting n8000.

And found this post.

Since i m at XWALH1, i would like to try. But i dunno whether the rooting is the same like urs or not.

Perhaps u know abt this, and can give me some advice ?

http://bestandroidtips.com/root-galaxy-note-n8000-on-xwalh1-android-4-0-4-official-firmware.html/2

Thanks,

WJ
[Galaxy Note 10.1 Android Development] zedomax:
So if you mount the 1st time and try to delete a file it doesn't work?
[Galaxy Note 10.1 Android Development] rogeriocamorim:
How can i backup mine stock kernel and firmware if some thing got wrong ?
[Galaxy Note 10.1 Android Development] zedomax:
Use the CWM root method but before you flash the super user zip file, do a backup ROM in CWM. That's it!
[Galaxy Note 10.1 Android Development] SoCaliTrojan:
Right. It seems to mount for only a second after the first attempt. Or maybe milliseconds. Maybe it thinks it successfully mounted when it didn't even mount?
[Galaxy Note 10.1 Android Development] akxak:
That's the method I (re)rooted my N8000 with. The original one and after applying ther ALH2 update with Kies.
[Galaxy Note 10.1 Android Development] antique_sonic:
Would it increase binary counter and give a yellow triangle ?

Thanks,
[Galaxy Note 10.1 Android Development] zedomax:
hmmmm not exactly sure whats going on as mount is working flawless here do u have n8000 or n8013?
[Galaxy Note 10.1 Android Development] Mhbr549:
I think that most everyone who rooted with the CWM method as opposed to the prerooted injection method can mount with no issue. Preroot injection and Note 10.1 don't seem to like each other. On my first device, I did root injection and could not mount r/w. Mine bricked when trying re-root with CWM and change to superuser from SuperSU. You know more than me on these things, but if I were him, and if he's on a n8013, I would flash stock recovery, wipe data with stock recovery, and then flash the stock UEAHL2 since it's the only bone-stock firmware we have right now, and then re-root using your CWM method 2. What do you think?
[Galaxy Note 10.1 Android Development] akxak:
Yes.... no.

The binary counter increases, but I never saw a yellow triangle on my Note 10.1

And thanks to Chainfire, there is the triangleaway app with which the counter can be reset. Mine does read 0 instead 2 and "original" instead of "custom". Stick to the instructions.
[Galaxy Note 10.1 Android Development] ninelo:
Does it matter if the counter shows "0" instead of "No"? My original not rooted device shows [Custom binary dounload: No] but you say that the counter resets to "0".
[Galaxy Note 10.1 Android Development] sotmax:
does anyone have the files for the 2nd rooting method and also the stock recovery>

Links are really sucks....they are down all the time.

If someone have them i can add them to my drive to have them available..

Also are those files ok for 8010?

Thanks...
[Galaxy Note 10.1 Android Development] akxak:
That's always the problem when stating something from memory:

My Note 10.1 says in download mode:

Custom binary download: No

Current binary: Samsung Official

System status: Official

after TriangleAways although CWM recovery is installed and the device is rooted.
[Galaxy Note 10.1 Android Development] antique_sonic:
Will all my installation apps be removed or still there after the rooting?

:)

Sent from xda-developers Galaxy N7000 ICS 4.0.4 LRK / CriskeloROM v.11.1 / Speedmod K3-12
[Galaxy Note 10.1 Android Development] akxak:
They are not affected, the device remains as is. The recovery has no influence on the running system and installing SuperSU just adds two files to the system partition to enable su.
[Galaxy Note 10.1 Android Development] antique_sonic:
Thanks man...

Anyway, u have the link for triangle away apk ?
[Galaxy Note 10.1 Android Development] crystalstylez:
You can always buy it from the playstore and support the dev. :rolleyes:

You can also find it here on xda also.
[Galaxy Note 10.1 Android Development] SoCaliTrojan:
I have the n8013.
[Galaxy Note 10.1 Android Development] connectsys:
I used the attached files for CMW method on my 8010, installed and rooted fine, dont have any problems.
[Galaxy Note 10.1 Android Development] antique_sonic:
:)

1 more thing before I root my device...

By rooting N8000, would it be able to move app to SD card ?

because currently even with SD card inside, I am not able to move apps to SD card (no button to press to move app to sd).

or it's a norm for tablet for not able to move app to SD card ?

hehe... sorry, this is my first tablet, and my first attempt to root. So, i really dunno whether the impact would be the same with N7000 or not.

:p

Thanks for help.

WJ
[Verizon Samsung Galaxy S III] tonytownsend:
Does anyone else power button wobble a little bit? I took it back to the Verizon store and he got there last 16GB to replace my phone power button felt perfect on the replacement but it had a paint bubble near the volume rocker. So I went to a another Verizon kiosk and tried two they felt the same as mine. Then I went to a third Verizon store and tried yet another one...... same issue is this just how the button is supposed to be?
[Verizon Samsung Galaxy S III] RCOVA:
Yeah I'm assuming. Because I had a case on my SGS3 and when I tried to take the case off to do a battery pull the button just popped off. I had a mini heart attack. I found it on the ground, popped it back in and everything works fine.