Database Info

[Q] Is it safe to do a full reset ?? (Stock TGY ICS)

Hello dear XDA members
I am going to sell my Galaxy tab 7.7 P6800 gsm/3G with original TGY CSC updated via kies to 4.0.4 ZSLP7. The device is made in Vietnam.
the question is, IS IT SAFE to do a FULL RESET FROM SETTINGS ? (I must give the new owner a fresh system)
note that everything is stock, no root nor custom kernel, not even CWM, nothing changed in the system, all Samsung Bloatware
you may ask me why am going to sell my 7.7 ? Because i can't own two devices (not enough money) I must sell this to get a note 2 (just wanted to use a new device, I must do so otherwise the price of my 7.7 will drop a lot after a year or two)
using the 7.7 was a joy, a great device with a gorgeous screen, no question about it.

Afaik, you should be safe to wipe from settings, someone can correct me if i'm wrong. Do not wipe from recovery, from what I have read this can trigger the super brick bug.
Sent from my GT-N8000 using XDA Premium HD app
A couple of extra options for safer wipe:
Go back to HC then wipe. Afaik HC recovery mmc_cap_erase flag is disabled.
Flash Locerra's CWM from here http://forum.xda-developers.com/showthread.php?t=1542897 and wipe from there, flash back to stock through odin. I believe this version of CWM has mmc_cap_erase flag is disabled.

thanks mate
well i don't understand how a big firme like Samsung can put a deadly option withing settings!
anyway, I hope the note 2 doesn't have this creepy brick bug.
anyone can confirm the brick from settings? someone must already did it by now? (of course on the same conditions)
best regards
Sifou
Galaxy Tab 7.7

The author of this thread suggests that you can corrupt the memory just by deleting large files. So just offhand, I'm going to suggest it's UNSAFE.
(Ask them to be sure.)

[DISCUSSION][4.3] Knox Bootloader

As most users know, people who flashed Sammy's 4.3 stock with ODIN have the infamous and (yet) unremovable Knox bootloader. This bootloader is known for causing numerous FC's, freezes and random reboots to people who flash custom roms/kernels.
For me (and for most users, I believe), the custom roms/kernels are the main reason why I love Android (and xda too), thus the Knox bootloader has became one hell of a headache for me and other people who unfortunately have been naive enough to flash stock 4.3 in the early days.
It doesn't matter if we have flashed the Knox bootloader by oversight, or just because we didn't know it was included in the stock 4.3 (as the i9300 stock 4.3 was Knox free). What does matter, is that many people are now having problems in enjoying their favorite custom roms and kernels thanks to this evil invention by Samsung.
Therefore, and as I didn't see any thread like this one, I created this thread so we can discuss what we can do to, at least, minimize the problems cause by this bootloader. I am not even dreaming with restoring our warranty. At this moment, I just want to peacefully enjoy the custom roms and kernels that the great developers of xda release for our beloved I9305.
Although I haven't seen many developers talking about this problem in our device's threads, I noticed that some have already tried to trick the bootloader and avoid the FC's (like @Hbohd, for example). However, I think that this is a huge task and should be done with the help of everyone. I know by first hand that we have many talented developers working for our device (and for others too) and I'm sure that we, united, could, at least, try to do something about this and teach Samsung not to mess with our devices. I have always stood for the policy that says "I've paid for my device, thus I should be able to do anything I want with it".
Note: If any of you developers have some idea but don't know how to test it because you don't have the Knox bootloader, I don't mind to test it on my I9305 (and I'm sure that other users don't mind too). I'm using Alliance ROM v2+ with Boeffla Kernel v5.1+ and Knox bootloader.
Let's start the brainstorming: (I warn you guys that I don't know much about Android developing, so please bear with me if I say any stupidity)
- As we know, our brother i9300 doesn't have Knox included in stock 4.3. As one the main differences between I9300 and I9305 is the RAM, maybe this Knox thing is something that uses some RAM?
- I can reproduce a FC that only happened to me since I have Knox (I am supposing that Knox-free 4.3 users don't have this FC): everytime I benchmark my I9305 with AnTuTu, it FC's in the 3D test. Always. Maybe Knox is related to Mali drivers?
- Can we trick the Knox bootloader by changing SELinux status or Samsung root restriction status? @Hbohd already tried something like that but it didn't seem to be conclusive. But I guess that at this point no possibilities should be eliminated.
- And what about restoring the old bootloader from 4.1.2? We already know that restoring previous nandroid backups or flashing stock 4.1.2 from ODIN are useless...
So, what you guys think?
Please, be free to say anything you want, as long as it is on topic. In my opinion, we are currently far away from the solution so any help is welcome

I have Knox and running cm 11 no problems here..
Flash counter is at 6 maybe its The boeffla ?
Tested antutu no problems here
Sent from my GT-I9305 using xda app-developers app

toeterbaas said:
I have Knox and running cm 11 no problems here..
Flash counter is at 6 maybe its The boeffla ?
Tested antutu no problems here
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
Well, that's a surprise to me, thanks for informing.
Regarding what you said, it seems that Knox only brings problems when you use a custom stock based ROM or Kernel (or both).
However, you (and other people who have Knox + non-stock ROMs) would still benefit from a possible solution that would revert our bootloader and restore our warranty. If that is ever possible

My counter is on 4 but for knox there is a special/ extra counter.
Maybe some modders can try let the boot loader think that the
moded kernel is an original stock kernel?
name installation scripts with original kernel letters
and is it possible to make the modded kernel with same filesize
like stock kernel?
regards
sonic76

I think is custom kernel wich causes all your troubles . I experienced same problems , even network signal loss with custom kernel .
Lately I am using kenar2's deodexed , rooted rom with kernel replaced to the original . I have no problem and battery life is great . I uninstalled all bloat including Knox software .
Let's give custom kernels some time to mature and I think we can continue to use them and custom roms like we used to do.
Of course we have to live with voided warranty .

I do use a custom ROM.
Its cm 11 but The kernel is standard and i have zero problems here.
I used other roms to no problems.
I had problems with stock ROM rooted and boeffla kernel.
So it must be The kernel.
I am not affraid of The waranty because never ever one of nu phones broke from Samsung and i had a lot of Samsung phones
Sent from my GT-I9305 using xda app-developers app

Not sure if anyone has mentioned this before, but I will describe the FC/freeze behaviour in a bit more detail, based on my experiences running boeffla for at least a few days. My config is stock rom (self-rooted), knox bootloader. I do run a few xposed mods but turning xposed off doesn't seem to affect the problem.
- At boot everything is perfect. I can open any app without force close.
- After an hour or two, or it may be related to the number/type of apps opening, force closes or freezes will begin.
- Some apps seem to force close more than others. Chrome force closes often but other apps like stock internet seem generally OK.
- Often, after the first FC (or a few), the app will not be able to run again (launching it results in immediate FC or black screen).
- The longer the phone is on (or perhaps in use), the more FC's will occur. Eventually, I even had system apps (e.g. Settings) FC/refuse to open and the phone becomes unstable enough to reboot. It doesn't seem to get much worse when idling though - phone generally stays stable overnight (if it was stable when I went to sleep).
BTW, has anyone requested updated i9305 sources yet from samsung or knows the best process to do so?

oswade said:
Not sure if anyone has mentioned this before, but I will describe the FC/freeze behaviour in a bit more detail, based on my experiences running boeffla for at least a few days. My config is stock rom (self-rooted), knox bootloader. I do run a few xposed mods but turning xposed off doesn't seem to affect the problem.
- At boot everything is perfect. I can open any app without force close.
- After an hour or two, or it may be related to the number/type of apps opening, force closes or freezes will begin.
- Some apps seem to force close more than others. Chrome force closes often but other apps like stock internet seem generally OK.
- Often, after the first FC (or a few), the app will not be able to run again (launching it results in immediate FC or black screen).
- The longer the phone is on (or perhaps in use), the more FC's will occur. Eventually, I even had system apps (e.g. Settings) FC/refuse to open and the phone becomes unstable enough to reboot. It doesn't seem to get much worse when idling though - phone generally stays stable overnight (if it was stable when I went to sleep).
BTW, has anyone requested updated i9305 sources yet from samsung or knows the best process to do so?
Click to expand...
Click to collapse
Did you tried different version of boeffla and the yank kernel to.

Why do you think you have knox bootloader? Even if you have it, question is does it work in a way it works on newer devices, where according to Samsung, bootloader uses eFuse to flash/check knox flag.
When you reboot into download mode, do you see knox flag mentioned. Counter someone above mentioned has nothing to do with knox, and can be set zero with triangle away, chain fire's app.
Sent from my GT-I9505 using Tapatalk

You cant set Knox to 0×0
Only ROM counts :thumbup:
Sent from my GT-I9305 using xda app-developers app

toeterbaas said:
I do use a custom ROM.
Its cm 11 but The kernel is standard and i have zero problems here.
I used other roms to no problems.
I had problems with stock ROM rooted and boeffla kernel.
So it must be The kernel.
I am not affraid of The waranty because never ever one of nu phones broke from Samsung and i had a lot of Samsung phones
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
On AOSP roms there are no problems. They appear on 4.3 Samsung Stock roms + Knox bootloader + custom kernel.
oswade said:
Not sure if anyone has mentioned this before, but I will describe the FC/freeze behaviour in a bit more detail, based on my experiences running boeffla for at least a few days. My config is stock rom (self-rooted), knox bootloader. I do run a few xposed mods but turning xposed off doesn't seem to affect the problem.
- At boot everything is perfect. I can open any app without force close.
- After an hour or two, or it may be related to the number/type of apps opening, force closes or freezes will begin.
- Some apps seem to force close more than others. Chrome force closes often but other apps like stock internet seem generally OK.
- Often, after the first FC (or a few), the app will not be able to run again (launching it results in immediate FC or black screen).
- The longer the phone is on (or perhaps in use), the more FC's will occur. Eventually, I even had system apps (e.g. Settings) FC/refuse to open and the phone becomes unstable enough to reboot. It doesn't seem to get much worse when idling though - phone generally stays stable overnight (if it was stable when I went to sleep).
BTW, has anyone requested updated i9305 sources yet from samsung or knows the best process to do so?
Click to expand...
Click to collapse
Thanks for your input, that is something new man !
In fact, I have just seen a new sourcedrop for our i9305 - might be interesting!!!

Hbohd said:
Thanks for your input, that is something new man !
In fact, I have just seen a new sourcedrop for our i9305 - might be interesting!!!
Click to expand...
Click to collapse
no worries .
Nice, i hope the sources provide us with an easy fix!

Post some of the dumpstate_app_error.txt.gz from data/log after the fcs
Sent from my GT-I9305 using Tapatalk

Edit: forgot to turn on logger

Goldie said:
Post some of the dumpstate_app_error.txt.gz from data/log after the fcs
Sent from my GT-I9305 using Tapatalk
Click to expand...
Click to collapse
Here is mine, right after AnTuTu FC in 3D test.
I rebooted the phone, forced the FC by doing a 3D benchmark and then uploaded the file. I hope it is what you want

Thanks but you need to turn logging on in boeffla settings first
Sent from my GT-I9305 using Tapatalk

Goldie said:
Thanks but you need to turn logging on in boeffla settings first
Sent from my GT-I9305 using Tapatalk
Click to expand...
Click to collapse
You're right... My bad! Here it is again, same procedure...

I have an idea how to restore knox-free bootloader, maybe all we need is unbrick SDCARD (like for i9300 http://forum.xda-developers.com/showthread.php?t=1916796) made on i9305 with 4.1.2 room. I have heard of several cases where I9305 came into SDCARD mode and overwrite curent bootloader with data of the sdcard. For go in to SDCARD mode they hold volume up + volmne down + home + power in the same time.
All I need is dd image for unbrick SDCARD for i9305 and I will try.
Sorry for my english.

guys try out boeffla beta 12. i think it has fixed the knox bootloader problems but itll be good if someone else can confirm.

oswade said:
guys try out boeffla beta 12. i think it has fixed the knox bootloader problems but itll be good if someone else can confirm.
Click to expand...
Click to collapse
I have Internet FC, Gapp's FC, my mobile was 2 times down means display black and mobile won't wake up,
no reaktion by long press power button so i have to pull out the battery....!
I have boeffla beta 12 with no tweaks over boeffla app!
regards
Sonic76

Burned by Root/Custom ROMS - do I try again or quit...

The last Android device I rooted/rom'd was a ZTE Blade (Orange San Francisco) - went well for a few weeks but one day it got stuck on the 'Green Android' screen at startup and that was that.
On that basis I've been reluctant to root/rom other devices since - but my S3 (Orange UK) drives me nuts with all it's bundled crapware so I gave-in and rooted it (latest CF-Auto-Root) and then used Mobile Odin Pro to install the latest SlimROM
That worked OK for a day - then it reset itself and would only boot into recovery (by default) or download (if forced)
I've reinstalled stock firmware from desktop Odin and it seems fine - question is am I
a - unlucky
b - just not very good at this stuff
and would I be better off
a - trying again with a different setup
b - just leaving it as-is

somewhatdog said:
The last Android device I rooted/rom'd was a ZTE Blade (Orange San Francisco) - went well for a few weeks but one day it got stuck on the 'Green Android' screen at startup and that was that.
On that basis I've been reluctant to root/rom other devices since - but my S3 (Orange UK) drives me nuts with all it's bundled crapware so I gave-in and rooted it (latest CF-Auto-Root) and then used Mobile Odin Pro to install the latest SlimROM
That worked OK for a day - then it reset itself and would only boot into recovery (by default) or download (if forced)
I've reinstalled stock firmware from desktop Odin and it seems fine - question is am I
a - unlucky
b - just not very good at this stuff
and would I be better off
a - trying again with a different setup
b - just leaving it as-is
Click to expand...
Click to collapse
its a strange story, i just think your unlucky i have never had rooted a phone only for it to boot into recovery Only. if you really want to try again go for it. maybe third times a charm?

Trozzul said:
its a strange story, i just think your unlucky i have never had rooted a phone only for it to boot into recovery Only. if you really want to try again go for it. maybe third times a charm?
Click to expand...
Click to collapse
Well I did that and this time it froze partway through installing (Mobile Odin) so I guess I'm more than unlucky and perhaps this phone (an i9300 - standard international model) is on the fritz?
I might switch back to the older approach using a custom recovery and see if that works any better - I've not bricked it yet!
Update: I switched to good-old CWM and installed Cyanogen 10.2 - I know, it's a boring choice but the main benefit at this point is that it seems to have worked at least - 'stock' Android over Touchwiz? We'll see how I get along with that then. ;0

somewhatdog said:
Well I did that and this time it froze partway through installing (Mobile Odin) so I guess I'm more than unlucky and perhaps this phone (an i9300 - standard international model) is on the fritz?
I might switch back to the older approach using a custom recovery and see if that works any better - I've not bricked it yet!
Update: I switched to good-old CWM and installed Cyanogen 10.2 - I know, it's a boring choice but the main benefit at this point is that it seems to have worked at least - 'stock' Android over Touchwiz? We'll see how I get along with that then. ;0
Click to expand...
Click to collapse
Haha stock android is not boring, its the best looking, I can't stand all the other ui's sense motoblur and all the nonsense. Touchwiz was the only good looking ui thought I can be pretty laggy

[Q] Help flashing Note 2 (E250/N7105) any custom ROM, fix SIM/IMEI issue

First of all, I'm a complete noob. I just joined the xda forum today after a year of following developments especially for custom roms and apps.
I have a pre-owned rooted Samsung Galaxy Note 2 (Android v4.1.1) which the "About Device" indicates is model n7105. I really wanted to "upgrade" its capabilities and features to a level close to Note 3 and/or KitKat goodness. So after reading a lot about how to flash custom ROMS, I tried Ditto Note 3 v5 (http://forum.xda-developers.com/show....php?t=2589715). Everything went well during the installation but after reboot it got stuck in the logo screen. After waiting for 10 minutes I flashed it AGAIN but with the same result. Finally after waiting for 20 minutes, I restored my phone to its backup. Now my phone can no longer detect my SIM card and my IMEI is null/unknown, even after factory reset. I made a big mistake! Then I remembered that that the original owner mentioned it's a converted E250 KOREAN version but I'm no longer able to contact her. This phone has been rooted and tweaked many times for over a year now, and having it serviced is no longer an option.
I definitely still want to flash DN3 (or any custom ROM compatible with E250) but I also need how to revert E250 to N7105 and fix my "Insert SIM card" problem. So where do I go from here? Any help/comments/suggestions on my specific case would be greatly appreciated! I am willing to learn whatever it takes to get this done and experiment.
Note: I didn't find clear answers to these in related forums and I'm also not yet able to post anything there. Hoping someone knowledgeable and helpful reads this.

103
I would begin with calming yourself down :]
There's always chance to flash proper rom so don't worry.
Pick up proper DN distribution suitable for Your device and flash again.
Remember to clean system for new rom, wipe data/factory reset and also wipe cache and dalvik cache, format system, and flash the thing again.
Remember that not always rom will boot from the first kick.. it often happens to me (freeze on first screen - not Samsung but the one with Note2 screen), it's as easy as taking the battery off the device and reconnecting it again for awhile and then power on again (sometimes it works in thrid attepmt so be patient, once it runs there should be no more further problems)
I hope You will solve Your problem.
Good luck!

Yep I totally agree with roozxx on that
Sent from my GT-N7100 using XDA Premium 4 mobile app

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