Database Info

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

[Q] Cyanogen Did Not Work No Service

Hey Everybody
I'm new to the whole rooting process, which I did fine on Saturday the 4th of October 2014. Today (October 8th 2014) I tried to install Cyanogen using the installer, it said it worked, but when my phone rebooted it was in the original version of touchwhiz that came with my Galaxy S3 SGH-I747 Rogers version. I wanted to get my files back, so I went into CWM and tried to recover, which didn't work. I tried again and again and it finally loaded my apps, but I had no service and I was spammed with "failure to load .gapps.google" or something like that. I went into CWM and wiped cache, tried again, same issue. I then wiped everything, went back into it and it still was NOT working. What do I do? I have no service at all! I've tried pulling the SIM and putting it back, but no success. Please HELP!
EDIT: I flashed stock ROM using ODIN, which worked. I would still like to know why CWM didn't work though, and if it is still possible to try to get it to work

lasttimelord12 said:
Hey Everybody
I'm new to the whole rooting process, which I did fine on Saturday the 4th of October 2014. Today (October 8th 2014) I tried to install Cyanogen using the installer, it said it worked, but when my phone rebooted it was in the original version of touchwhiz that came with my Galaxy S3 SGH-I747 Rogers version. I wanted to get my files back, so I went into CWM and tried to recover, which didn't work. I tried again and again and it finally loaded my apps, but I had no service and I was spammed with "failure to load .gapps.google" or something like that. I went into CWM and wiped cache, tried again, same issue. I then wiped everything, went back into it and it still was NOT working. What do I do? I have no service at all! I've tried pulling the SIM and putting it back, but no success. Please HELP!
Click to expand...
Click to collapse
Anybody?

I'm a beginner myself, and i do not know much about installing custom roms on samsung phones, but maybe you did not flash a compatible custom kernel to support the custom rom? it seems like you did not flash gapps either, but that should not stop you from getting network service. my last guess would be that you need to also install a baseband perhaps. all this information should be there in the galaxy s3 section of the forums.

ishaang said:
did not flash a compatible custom kernel to support the custom rom? it seems like you did not flash gapps either, but that should not stop you from getting network service. .
Click to expand...
Click to collapse
Hey there, first off, thank you for replying.
I didn't manually use odin or other flashing software to flash the ROM. Unlike the rooting method (which went smoothly) I used the cyanogen mod installer. The installer itself said that cyanogen was installed successfully, but it was not. After it said this, my screen (on the phone) turned off, and I was brought to a fresh install of touchwhiz. I've actually fixed the networking issue by flashing touchwhiz stock,but that still doesn't explain why my CWM backup wasn't working.

I see...I haven't used the cyanogen mod installer myself so cannot say...
What I suggest is that, if you're up for trying again, to manually flash a rom - either Cyanogenmod or any other. There seem to be a lot of good roms available for your phone, and whichever rom you choose will come with instructions for how to install. The usual method will involve the following steps as far as I know:
- Root
- Unlock Bootloader
- Flash Custom Kernel with recovery
- Flash ROM
- Flash GAPPS
These steps are not difficult at all as long as you follow the instructions for your specific phone. I have a Sony Xperia SL and thats how I installed a custom rom on it many times. Sorry I could not help much not knowing Samsung procedures but good luck!

lasttimelord12 said:
Hey Everybody
I'm new to the whole rooting process, which I did fine on Saturday the 4th of October 2014. Today (October 8th 2014) I tried to install Cyanogen using the installer, it said it worked, but when my phone rebooted it was in the original version of touchwhiz that came with my Galaxy S3 SGH-I747 Rogers version. I wanted to get my files back, so I went into CWM and tried to recover, which didn't work. I tried again and again and it finally loaded my apps, but I had no service and I was spammed with "failure to load .gapps.google" or something like that. I went into CWM and wiped cache, tried again, same issue. I then wiped everything, went back into it and it still was NOT working. What do I do? I have no service at all! I've tried pulling the SIM and putting it back, but no success. Please HELP!
EDIT: I flashed stock ROM using ODIN, which worked. I would still like to know why CWM didn't work though, and if it is still possible to try to get it to work
Click to expand...
Click to collapse
OK,
Download stock ROM for your device from Samsung-updates.com according to device model and region.
Then flash it with Odin.
Good luck

[Q] lollipop out for wifi Note Pro 12.2, link

Just saw this:
http://phandroid.com/2015/05/18/note-pro-12-2-lollipop/
I was planning on giving it a try. I don't have any files I need to save on the tablet.
I rooted the tablet recently and am running a rooted stock 4.4.2 ROM. I have titanium backup on there with a lot of stuff frozen, and xposed frame work.
I realizing flashing this lollipop ROM will unroot my tablet, but I'm wondering if I should do some kind of full wipe/dalvik clearing etc? Is there any other steps I need to take before installing a non rooted ROM on an already-rooted device?
I'm running the stock recovery at this time (but could flash something else if recommended.)

i checked out the link. it seems like the update is only for the LTE version (p905), unless im seeing it incorrectly, i wouldnt mind losing root whilst trying the new update

crap... you're right, the article itself refers to the "wifi only" version multiple times, but then the file is for the LTE... what a bummer. Erroneous article. Thanks for pointing it out before I flashed it.

Good catch !
Good catch there, I must admit I got quite excited seeing that lollipop was ready for the Note Pro 12.2!!!. I too have the WiFi version of the NotePRO 12.2'' P-900, and am chomping at the bit for Lollipop, more-so than for my main use phone (Note 3 SM-N9005).
I'm still on the stock firmware, enjoying the tablet as-is, but struggling to find many Apps where the UI has been crafted / coded / mod'd / re-written etc, with a tablet in mind!!
I've been patient to-date re: Lollpop, but will subscribe to this forum thread in case of news . Are there other sources I can / should be subscribed to, that you would suggest? .
Thank you, and cheers... :silly:

Owd-Larrd said:
Are there other sources I can / should be subscribed to, that you would suggest? .
Click to expand...
Click to collapse
Just keep an eye on Sammobile. They're the ones with the firmware and the news. (The original article is from Sammobile.)
http://www.sammobile.com/firmwares/database/SM-P900/

spaceturd3000 said:
Just saw this:
http://phandroid.com/2015/05/18/note-pro-12-2-lollipop/
I was planning on giving it a try. I don't have any files I need to save on the tablet.
I rooted the tablet recently and am running a rooted stock 4.4.2 ROM. I have titanium backup on there with a lot of stuff frozen, and xposed frame work.
I realizing flashing this lollipop ROM will unroot my tablet, but I'm wondering if I should do some kind of full wipe/dalvik clearing etc? Is there any other steps I need to take before installing a non rooted ROM on an already-rooted device?
I'm running the stock recovery at this time (but could flash something else if recommended.)
Click to expand...
Click to collapse
Could you help me out? I have a Note 12.2 that I tried to root when I first got it a year ago. It tripped Knox but still did not get root. I would love to get to where you're at: KK 4.4.2 with TiBu, xposed, etc. Can you point me to some instructions that work?

Vlip3 said:
Could you help me out? I have a Note 12.2 that I tried to root when I first got it a year ago. It tripped Knox but still did not get root. I would love to get to where you're at: KK 4.4.2 with TiBu, xposed, etc. Can you point me to some instructions that work?
Click to expand...
Click to collapse
Sorry for the late reply! If I remember correctly, I used the "near stock untouched" version found here:
http://forum.xda-developers.com/gal...t/rom-original-stock-debloated-stock-t2860069
But I forget! I do know that I have the stock recovery. I rooted/Flashed ROM with ODIN. But didn't install custom Recovery.

How far can I upgrade my GT-N8013?

If the following table is correct then I have a GT-N8013. I'm running KitKat 4.4.2 on it: (N8010XXUDNE4_N8010BTUDNF1_BTU_N8013.tar.md5).
How close can one get to the latest version of Android and still have a working GT-N8013?
GT-N8000 - Wifi+3G+calling
GT-N8005 - Wifi+3G
GT-N8010 - Wifi (Except USA)
GT-N8013 - Wifi (Only USA)
GT-N8020 - Wifi+LTE

KK 4.4.2 is the last release from Samsung .
Android then see your models custom rom section .

JJEgan said:
KK 4.4.2 is the last release from Samsung .
Android then see your models custom rom section .
Click to expand...
Click to collapse
I've just picked up a used 10.1 (first edition) and am hoping to get it onto 5.1.1 or 6.01.
I see a custom CM ROM from Cyanogen, that states it's 6.0 official, but when I go to the site the release is really old for the 8013, and I'm not sure if it's been grouped in with the more recent beta group that is linked in the thread or if it's not.
I also see an older Cyanogen thread for 12, but that's pre 6.0 and appears to be somewhat abandoned.
My Note 3 is on phronesis 6.0.1, and I would like to get the Note 10.1 to as close to that as possible, without dealing with any major bugs.
Thank you for your assistance.

Some progress.
I managed to update mine to Marshmallow 6.0.1 (cm-13.0-20160523-UNOFFICIAL-n8013.zip) via CWM v6.0.3.6 but Google Apps keeps crashing.
I've tried both open_gapps-arm-6.0-nano-20160721.zip (Open GApps) and gapps-600-base-20151107-1-signed.zip. Both take hours to install and just keep crashing whenever you try to do anything.
Anyone have any luck getting cm-13.0-20160523-UNOFFICIAL-n8013.zip / and GApps.zip working?

Basil Rathbone said:
I managed to update mine to Marshmallow 6.0.1 (cm-13.0-20160523-UNOFFICIAL-n8013.zip) via CWM v6.0.3.6 but Google Apps keeps crashing.
I've tried both open_gapps-arm-6.0-nano-20160721.zip (Open GApps) and gapps-600-base-20151107-1-signed.zip. Both take hours to install and just keep crashing whenever you try to do anything.
Anyone have any luck getting cm-13.0-20160523-UNOFFICIAL-n8013.zip / and GApps.zip working?
Click to expand...
Click to collapse
I had it crashing initially too, with CM-13.
I reinstalled the ROM, root, twrp, everything. I also made sure to install the latest "Stock" Gapps, before rebooting once the ROM was in place. Since then I have not had any issues.
I did however have some issues using the nano package. Hope that helps.

Still no joy
I still can't get CM-13 to work. I use CWM. I made sure I was using the latest CWM 6.0.4.6.
I booted into CWM, factory reset and cleared cache. Flashed cm-13.0-20160523-UNOFFICIAL-n8013.zip.
I then factory reset and cleared cache again and flashed gapps-600-base-20151107-1-signed.zip.
I then factory reset and cleared cache again and rebooted.
No joy.
What actual gApps and CM-13 did you use? Maybe I need to use the same version of TWRP as you used?
I'm stumped.
--------------------------------------------------------------------------------
bladebarrier said:
I had it crashing initially too, with CM-13.
I reinstalled the ROM, root, twrp, everything. I also made sure to install the latest "Stock" Gapps, before rebooting once the ROM was in place. Since then I have not had any issues.
I did however have some issues using the nano package. Hope that helps.
Click to expand...
Click to collapse

Basil Rathbone said:
I still can't get CM-13 to work. I use CWM. I made sure I was using the latest CWM 6.0.4.6.
I booted into CWM, factory reset and cleared cache. Flashed cm-13.0-20160523-UNOFFICIAL-n8013.zip.
I then factory reset and cleared cache again and flashed gapps-600-base-20151107-1-signed.zip.
I then factory reset and cleared cache again and rebooted.
No joy.
What actual gApps and CM-13 did you use? Maybe I need to use the same version of TWRP as you used?
I'm stumped.
--------------------------------------------------------------------------------
Click to expand...
Click to collapse
I used the ARM 6.0 Stock version for CM 13. http://wiki.cyanogenmod.org/w/Google_Apps#Downloads
I ended up swapping to the 2014 model because I got a good deal on a Verizon version (which is locked but oh well), so I don't recall the TWRP that I ran. It sounds like that sometimes gives people issues.
I do recall that using the nano version of gapps was not working for me. Could be a coincidence, but I had constant crashes when I tried using it.
This is the thread I used to grab the ROM and TWRP: http://forum.xda-developers.com/galaxy-note-10-1/development/rom-lollipop-t3269375

It helps to read the installation notes properly
The problem(s) I was having were resolved by using twrp-2.8.7.0-gt-n8013 instead of N8013-CWM-Touch-6.04.6. I also used open_gapps-arm-6.0-stock-20160803 instead of nano but I really think it was TWRP that made everything work.
I'm now running cm-13.0-20160523-UNOFFICIAL-n8013 without any problems.
I consider this thread closed.

Basil Rathbone said:
If the following table is correct then I have a GT-N8013. I'm running KitKat 4.4.2 on it: (N8010XXUDNE4_N8010BTUDNF1_BTU_N8013.tar.md5).
How close can one get to the latest version of Android and still have a working GT-N8013?
GT-N8000 - Wifi+3G+calling
GT-N8005 - Wifi+3G
GT-N8010 - Wifi (Except USA)
GT-N8013 - Wifi (Only USA)
GT-N8020 - Wifi+LTE
Click to expand...
Click to collapse
How did you get KitKat on n8013. It was never released and no one successfully flashed 4.4 n8010 to n8013. Odin keeps giving an error. Please I've been trying for years now since it's been 2 years since update was released and doesn't look like it'll ever release (**** yoi Samsung with your update **** and regions)

Anyone have any luck? I've had this tablet since 2013 and I stopped using it because it has always been such a laggy sluggish experience. I thought I would try putting an AOSP ROM on it to see if that helped. Everything is so old for this device that it's nearly impossible to find the old files, ROMs, recoverys, etc. I can't even get TWRP or CWM to work on it. Maybe it's not worth the trouble anymore.

MrAwesome75 said:
Anyone have any luck? I've had this tablet since 2013 and I stopped using it because it has always been such a laggy sluggish experience. I thought I would try putting an AOSP ROM on it to see if that helped. Everything is so old for this device that it's nearly impossible to find the old files, ROMs, recoverys, etc. I can't even get TWRP or CWM to work on it. Maybe it's not worth the trouble anymore.
Click to expand...
Click to collapse
Well official only kitkat if you are international (Samsung decided not to release a lot of device updates in the us for kit kat including the s3, galaxy light, and this one). However I think you can get CM 13.1, idk about anything more recent but there is a (slightly) active community for it still left. Its a shame that this flagship tablet was neglected. I hope it doesn't happen with future Samsung ones but I've avoided buying any. I still use mine on jellybean for basic internet browsing and games

zMrAwesome75 said:
Quote:
Anyone have any luck? I've had this tablet since 2013 and I stopped using it because it has always been such a laggy sluggish experience. I thought I would try putting an AOSP ROM on it to see if that helped. Everything is so old for this device that it's nearly impossible to find the old files, ROMs, recoverys, etc. I can't even get TWRP or CWM to work on it. Maybe it's not worth the trouble anymore.
Click to expand...
Click to collapse
Not sure if you're still looking but I just installed Android Nougat v7.1.2 using the instructions provided here:
https://forum.xda-developers.com/showthread.php?t=2185119
I have a N8010 that topped out at 4.1.2. I flashed to a N8013 kernel/rom about 2 years ago which maxed out at 4.2.2 . I just recently found that link to the LineageOS build (Formerly Cyanogenmod) when I was contemplating buying a new tablet. The tablet was getting a bit sluggish so I decided to go ahead and blast it out and see what happened. I was VERY pleasantly surprised! Had some issues getting the Recovery flashed but once I did, it was pretty smooth from there. I had backed up all the apps so once I got it booted and restored all the apps, I was surprised how responsive it is. Oh, and you can say goodbye to all those SD card issues that the Note 10.1 had since this version of Android integrates the external SD with the internal SD so everything gets installed on the external card. No need for apps like folder mount, etc.
I highly recommend it. The only issue is that you lose the integrated S-Pen functionality but you can reinstall some of those apps from the play store and bring back a lot of those features. Some 3rd party apps actually work better.
Good luck!

7.1.2 on GT-N80013
I am currently running an unoffical build I picked up here on xda it is an unofficial Lineage OS build. I haven't currently found any bugs... camera works, bluetooth works, wifi works... at least for me. The build number is 14.1-20170810-unnofficial-n8013

Hannover2k said:
Not sure if you're still looking but I just installed Android Nougat v7.1.2 using the instructions provided here:
https://forum.xda-developers.com/showthread.php?t=2185119
I have a N8010 that topped out at 4.1.2. I flashed to a N8013 kernel/rom about 2 years ago which maxed out at 4.2.2 . I just recently found that link to the LineageOS build (Formerly Cyanogenmod) when I was contemplating buying a new tablet. The tablet was getting a bit sluggish so I decided to go ahead and blast it out and see what happened. I was VERY pleasantly surprised! Had some issues getting the Recovery flashed but once I did, it was pretty smooth from there. I had backed up all the apps so once I got it booted and restored all the apps, I was surprised how responsive it is. Oh, and you can say goodbye to all those SD card issues that the Note 10.1 had since this version of Android integrates the external SD with the internal SD so everything gets installed on the external card. No need for apps like folder mount, etc.
I highly recommend it. The only issue is that you lose the integrated S-Pen functionality but you can reinstall some of those apps from the play store and bring back a lot of those features. Some 3rd party apps actually work better.
Good luck!
Click to expand...
Click to collapse
I'd appreciate a link to the rom you installed. Thx.

I'm interested as well I'm still running original os. Also wondering if the rom update works well on these tablets since they are older. As Android matures the os gets bigger which can impact performance on older CPUs.

cloves said:
I'm interested as well I'm still running original os. Also wondering if the rom update works well on these tablets since they are older. As Android matures the os gets bigger which can impact performance on older CPUs.
Click to expand...
Click to collapse
I recently installed Lineage OS 14 and it is working great.
Tablet is stable, everything works, great battery life.
All devices work gps, etc...
The s-pen will not work like it did stock but there are apps you can get that seem to work better
Squid and Sketch for drawing....squid seems cool if you write with stylus
Install Magisk instead of supersu.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445