Galaxy Note 10.1 Root? - Galaxy Note 10.1 Q&A, Help & Troubleshooting

So I just traded my Tab 2 10.1 (and a little $$) with a family member for their Note 10.1 (2012, WiFi). I have experience with rooting and installing custom ROMs and Kernels both on the Tab 2 and this (Galaxy S2 LTE) but I'm confused on how to do it on the Note. I've looked around and couldn't find a single, solid way to root it. I've read of Odin flashes and CWM recoveries, but I can't make sense of them.
So far I've used Odin to root my GS2 and the Tab, but apparently the Odin method for the Note is a limited root(?).
The CWM recovery way seems simple enough, but I'm wondering if I can get root access for apps without problems and whether it's possible to flash custom ROMs on it. I've seen on the forums of people who weren't able to use titanium backup properly, which would be a problem for me.
Also, I'd like to know if simply flashing a recovery will allow safe OTA updates, or if not, flashing new firmwares.
If you've made it this far, thanks for your time.
Sent from my iPoop-destroying Sammy GS2 LTE

Have you really search?
[RECOVERY][RootGuide][ALL NOTE 10.1]Official CWM Recovery Touch & Non-Touch 6.0.3.6

Thank you. I ended up flashing a recovery through odin. Running the Hyperdrive rom now. Highly recommended.
Sent from my GT-N8010 using xda app-developers app

Related

Bricked while flashing a kernel with Mobile ODIN?

Hello!
I have rooted my Samsung Galaxy Tab 7.7 successfully, then I installed Mobile ODIN Pro 3.4.5 and tried to flash clockworkmod recovery using the kernel file from wiki.cyanogenmod.com/wiki/Samsung_Galaxy_Tab_(GSM):_Full_Update_Guide (specifically, "Technomancer's Kernel with the ClockworkMod Recovery"). The device rebooted and started making clicking noises (while stuck at "Samsung Galaxy Tab"). I waited for some time, rebooted it again... Now it doesn't make clicking noises, but still stuck.
Have I superbricked it *again*? I know that it would brick when made full wipe, but Mobile ODIN isn't supposed to wipe while flashing a kernel...
Please help me. Just today I got it from service centre, and I really don't want to wait another two weeks.
Thanks in advance
UPDATE 1: Wow, I was able to flash clockworkmod recovery through Heimdall 1.3.1 (something that I wasn’t able to do previously). Running memory check… maybe it is going to be fine after all [crosses fingers]. For all those who want to flash clockworkmod recovery on their Galaxy Tabs: don’t use Mobile ODIN, don’t use Heimdall 1.3.2 and flash the latest recovery (v6).
UPDATE 2: No errors! Now I am going to try to install Paranoid Android 2.23 (no official CM9 builds for P6800 yet).
Artyom.Kazak said:
Hello!
I have rooted my Samsung Galaxy Tab 7.7 successfully, then I installed Mobile ODIN Pro 3.4.5 and tried to flash clockworkmod recovery using the kernel file from wiki.cyanogenmod.com/wiki/Samsung_Galaxy_Tab_(GSM):_Full_Update_Guide (specifically, "Technomancer's Kernel with the ClockworkMod Recovery"). The device rebooted and started making clicking noises (while stuck at "Samsung Galaxy Tab"). I waited for some time, rebooted it again... Now it doesn't make clicking noises, but still stuck.
Have I superbricked it *again*? I know that it would brick when made full wipe, but Mobile ODIN isn't supposed to wipe while flashing a kernel...
Please help me. Just today I got it from service centre, and I really don't want to wait another two weeks.
Thanks in advance
UPDATE 1: Wow, I was able to flash clockworkmod recovery through Heimdall 1.3.1 (something that I wasn’t able to do previously). Running memory check… maybe it is going to be fine after all [crosses fingers]. For all those who want to flash clockworkmod recovery on their Galaxy Tabs: don’t use Mobile ODIN, don’t use Heimdall 1.3.2 and flash the latest recovery (v6).
UPDATE 2: No errors! Now I am going to try to install Paranoid Android 2.23 (no official CM9 builds for P6800 yet).
Click to expand...
Click to collapse
You realize you flashed a recovery for a completely different device and you are lucky to get your tablet running again, don't you? The "Galaxy Tab" is a 2010 device, one of the first Android tablets; it came with Froyo. Ours is over a year more recent, with a much improved architecture. The "Tab" was an overgrown Galaxy S; ours is an overgrown Galaxy Note.
Check the development board (for the 7.7 ). You should use either the latest CWM 6.x.x from locerra or TWRP, you will find them there. Also, you'll see that there are CM9/10 ports to our device (by locerra), in addition to ParanoidAndroid (ported by Androguide.fr).
Steve_max said:
You realize you flashed a recovery for a completely different device and you are lucky to get your tablet running again, don't you? The "Galaxy Tab" is a 2010 device, one of the first Android tablets; it came with Froyo. Ours is over a year more recent, with a much improved architecture. The "Tab" was an overgrown Galaxy S; ours is an overgrown Galaxy Note.
Check the development board (for the 7.7 ). You should use either the latest CWM 6.x.x from locerra or TWRP, you will find them there. Also, you'll see that there are CM9/10 ports to our device (by locerra), in addition to ParanoidAndroid (ported by Androguide.fr).
Click to expand...
Click to collapse
Ouch.
Now when you said it… Guess I’m very lucky. Thanks a lot! I swear I will pay more attention to, er, everything in the future
Artyom.Kazak said:
Ouch.
Now when you said it… Guess I’m very lucky. Thanks a lot! I swear I will pay more attention to, er, everything in the future
Click to expand...
Click to collapse
No worries, **** happens. Take care of the device (we are vulnerable to a pretty nasty bug, if you use the older or touch CWM). And as usual, #BlameSamsung for the confusing nomenclature...

[Q] Note 10.1 4G N8020 messed up

Hi all. Tried my first root + custom rom installation and i messed up the device..
i had the newest KIES firmware update (phone XXBMA5) and (XXBMA6) and i rooted the device with odin (3.07). That went OK.
Then i installed the CWM recovery with odin and that was OK too.
Then i downloaded the latest Omega Rom (i missread that it supports N8020) and followed the installation instructions to the point where it started installing Omega V2.0 from SDCARD and then it asked me to select device from a list that included only (N8000,N8010,N8013)..
So the situation now is that i have working odin, working CWM and backup of the EFS (img+tar) but no working recovery. i live in Finland and the device is Sonera locked i think, so the stock roms (international) do not work i guess.
KIES has a backup of my Note but i can't even get to a point where KIES discovers the device.
So basically i think i need a working ROM for my model (Note 10.1 4G N8020), or can i recover the original samsung software somehow ?
Any advices ?
Removed
Just a thought, but can't you reflash CWM or the stock recovery?
If you didn't install the rom why do you need to re-install anything. Just powering down and powering up should have left you as was....
Alajarvi84 said:
working CWM .......... but no working recovery.
Click to expand...
Click to collapse
Maybe i'm missing something but isn't CWM your custom recovery?
It doesn't sound like you've actually installed any rom yet.The Omega installer doesn't actually install anything until a few steps after the one you mentioned about the model type.
I'm with ultramag69 on this one. You should still be on a stock rom unless you already wiped your original rom.
Hi again. Problem solved, just had to do emergency thing from KIES. Like i said this was the first time trying root + custom ro install and to be honest it went to ****. Somehow i managed to delete the stock firmware so that is why the recovery gave me (no files). I did make some backup but when tried to restore it said MD5 mismatch or something. At first the KIES emergency recovery could not find the device, but after i switched from CWMcto stock recovery it worked.
So what did i learn from all this ? Nothing, because i am getting too old (tired+lazy ) to do proper investigation. So one could say my strategy is to bang my head to the wall as long as it takes to go trough. Even if i could just go around it
So basically i am now at the point where i started, with stock 4.1.2 rooted. Used the triangle away to wipe the (6) custom installs or something away, but it still says custom in the settings> information. Does this mean that OTA won't work ? Any way around it ? Because i would like to check now and then that is my version of android the newest one..
Could someone recommend a custom ROM for my Note 10.1 4G (LTE) N8020 4.1.2 because the only one i was able to find was the CyanogenMod (or something) and it basically makes the S-Pen (almost) useless. What i would like is the Omega ROM, but like stated before the installation only supported N8000, N8010 & N8013...
Added screenshot from info.
Thanks anyway
What is truly amazing is that i did not brick the device tough..
switch from cwm to stock
Alajarvi84 said:
Hi again. Problem solved, just had to do emergency thing from KIES. Like i said this was the first time trying root + custom ro install and to be honest it went to ****. Somehow i managed to delete the stock firmware so that is why the recovery gave me (no files). I did make some backup but when tried to restore it said MD5 mismatch or something. At first the KIES emergency recovery could not find the device, but after i switched from CWMcto stock recovery it worked.
So what did i learn from all this ? Nothing, because i am getting too old (tired+lazy ) to do proper investigation. So one could say my strategy is to bang my head to the wall as long as it takes to go trough. Even if i could just go around it
So basically i am now at the point where i started, with stock 4.1.2 rooted. Used the triangle away to wipe the (6) custom installs or something away, but it still says custom in the settings> information. Does this mean that OTA won't work ? Any way around it ? Because i would like to check now and then that is my version of android the newest one..
Could someone recommend a custom ROM for my Note 10.1 4G (LTE) N8020 4.1.2 because the only one i was able to find was the CyanogenMod (or something) and it basically makes the S-Pen (almost) useless. What i would like is the Omega ROM, but like stated before the installation only supported N8000, N8010 & N8013...
Added screenshot from info.
Thanks anyway
Click to expand...
Click to collapse
How did you switch from CWM to stock? I have having a problem syncing with kies also using omega rom on n8013.
jjndimp said:
How did you switch from CWM to stock? I have having a problem syncing with kies also using omega rom on n8013.
Click to expand...
Click to collapse
I was not easy, i just tried the download mode over and over again with KIES open in windows and somehow it finally did find my device and offered a emergency restore. That is it, and the device was restored to default "original state".
OMG.... one would think after nearly having bricked your device you would either A) stop messing around with it or, B) read and learn more about what you're wanting to achieve and THEN maybe trying something with the ABSOLUTE certainty that a backup to restore is available to you in case of any mishap!
Moral of story :
Don't do anything until you are absolutely sure you have read EVERYTHING about what you are going to do.
For others wanting to mess with their devices, take heed! You may not be as lucky as OP (or troller) whichever is applicable.
There comes a certain point, that when crossed one does not care what happens to the device at hand. After fighting with my n8020 for several days in a row i couldn't care less, and like said before i dont have the level of enhusiasm like i had when i was younger. Of course i know now what went wrong.. But seriously, these are just overpriced toys, so it's not a matter of life and death.
Sent from my GT-N8020 using XDA Premium HD app

Galaxy note N7000 screen freezing after root

Just wondering if anyone had any experience with this issue. I rooted using philZ kernel, and it was stable for about 3 weeks. Thereafter the screen stopped recognising gestures with my s-pen (& finger) and, after trying to restore from recovery mode, I could not get past the GTN7000 start up icon.
Have managed get phone working again after flashing stock ROM using Odin, but it's not rooted now, which I miss........any ideas?
P.s. I must say I'm new to all this, and have looked around the site for similar threads relating to this issue but haven't found any
Cheers
Sent from Screen freezing after root my GT-N7000 using xda premium

[Q] Build Properties

I have a Samsung Galaxy Note 10.1 GT-N8013. However when i first got the tablet i decided to root it and while it was still new there weren't many tools to use and somehow i managed to change the device props. and now parts of my tab think its a GT-N8000 and wont let any GT-N8013 ROMs be flashed. But i try to flash ROMs for a GT-N8000 and they wont work either. I have only been able to flash ROMs or Recoverys through Odin. I have flashed a stock ROM with no effect.
Is there anyway to return all of my build props to stock settings.?
ogre55 said:
I have a Samsung Galaxy Note 10.1 GT-N8013. However when i first got the tablet i decided to root it and while it was still new there weren't many tools to use and somehow i managed to change the device props. and now parts of my tab think its a GT-N8000 and wont let any GT-N8013 ROMs be flashed. But i try to flash ROMs for a GT-N8000 and they wont work either. I have only been able to flash ROMs or Recoverys through Odin. I have flashed a stock ROM with no effect.
Is there anyway to return all of my build props to stock settings.?
Click to expand...
Click to collapse
I also flashed a custom ROM at one time that made my device appear to be a GT-N8000.
Mine is now back to normal after flashing a stock GT-N8013 firmware and then doing a factory reset.
Before you do that there is an advantage to having you tablet seen as GT-N8000, you can obtain apps from the play store that are not available for the GT-N8013 but are for the GT-N8000. First go to Google Play and get Device ID run it and write down the device ID for future use. Then get a PC program called Real APK Leecher. It will allow you to download any .apk file from Google play that is free and or that you have purchased.
ogre55 said:
I have a Samsung Galaxy Note 10.1 GT-N8013. However when i first got the tablet i decided to root it and while it was still new there weren't many tools to use and somehow i managed to change the device props. and now parts of my tab think its a GT-N8000 and wont let any GT-N8013 ROMs be flashed. But i try to flash ROMs for a GT-N8000 and they wont work either. I have only been able to flash ROMs or Recoverys through Odin. I have flashed a stock ROM with no effect.
Is there anyway to return all of my build props to stock settings.?
Click to expand...
Click to collapse
Edit the Build Prop there is even an app on Play .

Hey Im new and have a few questions

Hey Im Sixthg but call me six. I have rooted my Samsung Galaxy Tab 2 7.0 (GT-p3113) and flashed my recovery with CWM 6.0.3.7. I have a stock gaming rom and my Original rom backed up. Would it be possible for someone to Customize my rom and change the User Interface? If so, are you willing to do it for free?
Also I would like to keep my downloaded apps when I install custom roms....how would i do that?
Sixthg said:
Hey Im Sixthg but call me six. I have rooted my Samsung Galaxy Tab 2 7.0 (GT-p3113) and flashed my recovery with CWM 6.0.3.7. I have a stock gaming rom and my Original rom backed up. Would it be possible for someone to Customize my rom and change the User Interface? If so, are you willing to do it for free?
Also I would like to keep my downloaded apps when I install custom roms....how would i do that?
Click to expand...
Click to collapse
Hey there,
I,m new too but i'm not devs here, i'm a noob user so probably i'm not going to help much. If I'm explaining something that you are already know, I apologise.
Yet from my little experience, i did flash the latest recovery CWM 6.0.5.1 (i suggest you try it to flash the latest version available too) and using CM 12 build 20140215 unofficial lollipop version on my P3100. All of them you can found on thread by Android-Andi. Just make sure you download and flash the correct version for your P3113 / probably same as P3110 (*I use P3100).
I can't paste his link of work as its on his signature. BUT, you can found it on "Galaxy Tab 2 7" Android Development". On his androidfilehost you may find all the necessary files such as latest rom (twrp, cwm, omni, etc) and customize rom for kitkat or lollipop. He also made slim version for both of it. He also help how to do it. But be aware to backup everything first as usual. as what I did was a clean install thus it may not bring back any bugs with it. So it means download all the apps manually. But if you connect the game with google play your data will stay the same (I guess).
Just my 5cents. Sorry if it doesnt help much or didn't answer your questions. Hope someone could explain it better
Best of luck.
No with clockworkmod recovery it is best to have the one Rom manager recommends for a device. And seeing as no roms have been made for p3113 or p3110 I flashed it with the p3100 recovery. The one it downloaded and flashed is 6.0.2.7 because that recovery is meant for p3100. Nightlies I found out are full builds and with the app link2sd you can convert apps to system apps so you do not loss them when flashing a new rom. So thats what I did with my downloaded apps. Now as I have aslo backed up everything. I need to download a working nightly.
Also I would like to know if I could somehow take away the samsung dependency? They have too many apps that are key to my system's functionality.

Categories

Resources