Related
Two days ago my Galaxy Note 10.1 gt-n8010 got stuck at the initial screen (Samsung Galaxy Note 10.1)
It was working normally, and it was last successfully upgraded to a custom rom and CWM 6.0.3.6 a month ago.
The custom rom was (to my best knowledge Android Revolution HD 11.2 - 4.1.2)
Booting into recovery and download modes works.
CWM recovery works partially. Erasing Cache en resetting to factory works, and sometimes results in getting to the second splash screen of the boot process where it again gets stuck (Samsung animation keeps glowing), but more it keeps getting stuck at he first boot screen.
Erasing Dalvic cache leads to immediate reboot.
CWM log files cant be opened / external sd card can't be reached/mounted.
So CWM is only working for a small part.
I've attached images of the CWM screens including a log-screen that shows that files and folders cannot be found.
Using ODIN, to flash a new CWM or custom/original ROM result in a FAIL message.
Tried different ODIN version, two original Samsung data cables and two computers. Alle the same result. FAIL.
I'm hesitant to continue now without some help. I might do more harm and destroy all chances there are to recover this tablet.
I've flashed all my phones and tablets before. I'm not an expert, but never had a mishap, because I triple read the instructions. The situation that arises now is not a result of a failed upgrade/flash, but suddenly appeared one morning.
On the last days i thought i had also broken my tablet and i had more or less the same problem. If i were you i would directly download an official 4.4.2 and flash it via odin. Then if you everything works i would try whatever you want to flash
Try changing recovery. Give TWRP a try. Had it happen with a phone and switching recoveries solved it.
Sent from my SM-N900T using XDA Free mobile app
Well I had the same problem due to toooo many consecutive reboots
I was on gnabo then wid twrp
then I reflashed 4.4.2 update via odin and everything was a breeze after that
and one more thing
be sure to change the recovery cause the same one might not work again
well at least it didn't do worth me
I use philz now
Can't flash anything
Tried everything I could find but nothing works. I'm using windows 7 and cannot flash anything using Odin.
Download mode and CWM recovery still boot.
Are there other ways to communicate and reprogram the galaxy note 10.1?
Deadbeef said:
Tried everything I could find but nothing works. I'm using windows 7 and cannot flash anything using Odin.
Download mode and CWM recovery still boot.
Are there other ways to communicate and reprogram the galaxy note 10.1?
Click to expand...
Click to collapse
are you sure you do not have a bad cable
I've used two different original Samsung cables. Same result.
Brick?
Change a Odin version like odin 3.07 http://forum.xda-developers.com/showthread.php?t=1837605?
your odin shows your device is Samsung I9505 Galaxy S4
Where does Odin show the device is a i9505? It's a n8010.
reCAPTCHA
I am having similar issues (Galaxy Note 10.1 N8010 Gnabo ROM) - stuck on the samsung logo (never managed to get past it though) boots into recovery but can't mount sd card OR internal storage. Can't flash anything using Odin, always gets a Complete(Write) operation failed. Any suggestions ?
Looks like we're both in the same sinking boat.
Sorry for late reply
Deadbeef said:
Where does Odin show the device is a i9505? It's a n8010.
Click to expand...
Click to collapse
Sorry for late reply
Your Odin Screen Shot Say i9505 as your device
Deadbeef said:
Looks like we're both in the same sinking boat.
Click to expand...
Click to collapse
I join u guys as well....
also was on gnabo rom and suddenly stuck on Samsung screen... however what's different from you is that I have a N8000 and Odin flashing shows "PASS". But whatever I flash doesn't boot... I think I need to open a thread about it.
georgesmh said:
I join u guys as well....
also was on gnabo rom and suddenly stuck on Samsung screen... however what's different from you is that I have a N8000 and Odin flashing shows "PASS". But whatever I flash doesn't boot... I think I need to open a thread about it.
Click to expand...
Click to collapse
Same here with Ganbo v7 since ysterday....
Just get stuck on Samsung logo and nothing works, even reverting to older backup image
Agyar said:
Same here with Ganbo v7 since ysterday....
Just get stuck on Samsung logo and nothing works, even reverting to older backup image
Click to expand...
Click to collapse
guys did any of you solve the problem??
georgesmh said:
guys did any of you solve the problem??
Click to expand...
Click to collapse
Nothing yet.... I've tried one old backup of v5 I've had and that won't boot now as well...
Really strange. I'm hoping to get it working somehow over the weekend latest, since I'll be on business trip next week and would like to have operating device on airplanes.
Agyar said:
Nothing yet.... I've tried one old backup of v5 I've had and that won't boot now as well...
Really strange. I'm hoping to get it working somehow over the weekend latest, since I'll be on business trip next week and would like to have operating device on airplanes.
Click to expand...
Click to collapse
maybe it's a problem from Gnabo ROM itself??? What's really sad is nobody on the threads knows how to help us
Uni starts next week!
georgesmh said:
maybe it's a problem from Gnabo ROM itself??? What's really sad is nobody on the threads knows how to help us
Uni starts next week!
Click to expand...
Click to collapse
I've seen few other occurrences of this on different roms on various forums, so probably not Gnabo issue. also, nobody nowhere had a fix for it
I had similar problem last November with a stock 4.4.2 ROM. Fortunately it was still in warranty (2 years in the UK) and Samsung took it in and replaced both battery and main board. They did not explain what was wrong, only that they were seeing quite a few with this issue. Could it be flash failure?
dmarchant said:
I had similar problem last November with a stock 4.4.2 ROM. Fortunately it was still in warranty (2 years in the UK) and Samsung took it in and replaced both battery and main board. They did not explain what was wrong, only that they were seeing quite a few with this issue. Could it be flash failure?
Click to expand...
Click to collapse
I don't think it was flash failure, at least not in my case, since device worked without any issue for quite a while after last flashing... what was different now is that my battery was drained out for the first time i quite a while...
Hey guys, I just got my Note Pro a week ago and just started looking into rooting. I keep getting a notification about a 128mb stability update. I would assume it's gonna update to the latest build but I'm not sure what the latest build is or if it'll be rootable afterwords. my current build is KOT49H.P900UEU1ANAE. What is the latest build #? Is there a list of updates somewhere detailing what the improvements are? I just want to root, debloat, turn off OTA and remove KNOX.
Edit: sorry forgot to mention it's just the wife model SM-P900
So 48 views and not one person can tell me the latest build# ? I'll figure out the rest.
Sent from my SM-N900V using Tapatalk
Have you checked SamMobile?
http://www.sammobile.com/firmwares/database/SM-P900/XAR/
How i got there:
http://www.sammobile.com
1. Click Firmware on the top.
2. Click the greyed out firmware database link under the blue banner.
3. Under "Select your firmware" I picked Tablet-->Android-->SM-P900....-->Cellular South (which matches the US variants)
muzzy996 said:
Have you checked SamMobile?
http://www.sammobile.com/firmwares/database/SM-P900/XAR/
How i got there:
http://www.sammobile.com
1. Click Firmware on the top.
2. Click the greyed out firmware database link under the blue banner.
3. Under "Select your firmware" I picked Tablet-->Android-->SM-P900....-->Cellular South (which matches the US variants)
Click to expand...
Click to collapse
Thanks muzzy! I had already been to SamMobile but all it had was foreign countries listed. I didn't know about Cellular South being the US version. I'll look again.
Edit: oh look a list of the updates and release dates! My Wi - fi reception seems slow, do any of the update fix that?
I honestly can't say. I'm on NC5 which is dated back in April and have no major issues.
I'm rooted and debloated though, not that this would impact the wifi performance . .
48 views doesn't mean 48 users. About 44 of those are Google Content Crawler, which is Google search engine's bots crawling the net for content to display in google.com. It is an automated process.
Samsung doesn't release changelists, so we don't know what each update does beyond what we can see.
Thanks for the help guys! I just accepted the first update and it took me to ANC5. I guess I'll have to accept all updates until current and then try CF-Auto-Root. I'll report back then.
Actually I just got my tablet like a week ago as well. I m on the same build no as well....haven't updated yet. I also haven't installed Knox either. There is a download arrow on the Knox icon and if I click the icon it starts downloading so I just cancel it. I am thinking of rooting as well. Well what I m trying to say is...keep the thread updated and I will just follow your lead.....hehe.
It always helps to know your country as well as different countries are on slightly different versions. You can always go to sanmobile.com, click on firmware and search for p-900. That will give you the list of all the latest ROMs for different countries / carriers. US based ROMs are listed as "Cellular South".
Successful Root!
Okay guys sorry it's taken so long to respond, I had hernia surgery on Monday so I've been behind on getting this rooted.
My plan was to use CF-Auto-Root and then load TWRP recovery and then load "Debloat Stock Variant" by Gatsrom. I decided to do it in that order because I wasn't sure I could load a custom recovery without being rooted first.
I accepted all updates up to the current = P900UEU1BNK1. Using Win 7 and loaded Samsung drivers. Downloaded ODIN 3.09, Odin 3.07 came with CF-Auto-Root and downloaded TWRP. Booted into download mode and made sure ODIN recognized my P900. And this is when to fun began! Everything seem to be going okay but I did run into a snag. I used ODIN 3.07 because that's what came with Auto- Root and I'd read somewhere of people having trouble with 3.09??? Anyways I got a red "FAIL" message and my screen displayed multicolored lines. I tried running it in ODIN 3.09 and got the same result. (i didn't disconnect anything between the 3.07 or 3.09 attempts, maybe i should have?). I disconnected my P900 and it rebooted giving me a Firmware Error screen telling me to use Kies "Recovery Mode". I tried Kies Recovery but Kies3 wouldn't even recognize the P900. (I started freaking a little at this point!) Anyways, I decided to try and load TWRP because I thought I've got nothing to lose! I loaded TWRP into ODIN and it took, so I thought, because my P900 rebooted into an up and running normal state. (Big Sigh!) I tried booting into recovery but TWRP didn't take, it came up to stock recovery, trying to load TWRP just kicked the P900 out of the Firmware Error state it was in?? I decided to give Auto-Root another go after rebooting Win 7. Used ODIN 3.09 this time and everything went fine and I was rooted! Then I loaded TWRP and it loaded fine! I performed a TWRP backup at this point and things seem to be running smoothly. I still need to load the Debloat Variant, that's what's on my plate for today.
http://forum.xda-developers.com/showthread.php?t=2656551
http://forum.xda-developers.com/showthread.php?t=2706982
http://forum.xda-developers.com/gal...t/rom-original-stock-debloated-stock-t2860069
You are a much braver sole than I. Hope all goes smoothly.
I could be wrong but I would think that if one is going to a different ROM then rooting isn't necessary. Simply use Odin to flash TWRP but ensure that auto reboot is not enabled in Odin when you do it. If you allow the device to begin booting into stock system it's going to overwrite recovery again (with stock recovery) so what you want to do is flash TWRP, and once it's flashed FORCE a reboot directly into recovery again using the hardware keys on the device. At that point you can do an nandroid backup and then flash your ROM.
Sent from my SM-P900 using Tapatalk
treetopsranch said:
You are a much braver sole than I. Hope all goes smoothly.
Click to expand...
Click to collapse
I'm not that brave treetop! I just know my way around a computer and I've rooted a few of these things. Plus I know the guys here on XDA are good at helping out if you hit a snag. Luckily I figured this one out on my own! You've just gotta do your research before jumping in and search read, search read, search read! I provided some links to get you started....get to it!
muzzy99 said:
I could be wrong but I would think that if one is going to a different ROM then rooting isn't necessary. Simply use Odin to flash TWRP but ensure that auto reboot is not enabled in Odin when you do it. If you allow the device to begin booting into stock system it's going to overwrite recovery again (with stock recovery) so what you want to do is flash TWRP, and once it's flashed FORCE a reboot directly into recovery again using the hardware keys on the device. At that point you can do an nandroid backup and then flash your ROM.
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
Thanks for the info muzzy, I'll remember that for next time! :good:
I did get the Debloat Variant up and running and loaded Xposed framework with sdcard full access. Everything seems to be running smoothly!
Ok So I finally got to it and successfully rooted (in first try, if I may add ). Thanks to xblue's guide/heroic efforts I avoided certain things and everything went smoothly. So Basically I installed samsung drivers using Kies, rebooted pc (Win 8.1). Downloaded cf autoroot and downloaded odin 3.09 as autoroot comes with 3.07. Replaced ONLY 3.07 odin exe with 3.09. Started Odin in Admin mode, put the tablet in download mode. Attched to pc and Odin recognized it. Then Gave it a final thought......lol. Pressed Start, device booted couple times. Then PASS appeared on the Odin window after like 30 secs. Installed root checker...successfully rooted. Installed TWRP via odin and flashed that successfully. Made a full back up and installed a ROM of my choice. I am a happy camper.
Sweet Deal singhsta! I'm glad my efforts were a help!
i would update to the latest version.. i tried using the original one that you have however i got the screen flicker issue so had to update.. the first update isnt very good wifi keeps dropping but the most recent version doesn't tho you may have a bug where every time you unlock the screen the tablet is still asleep even though the icons are visible so you have to lock the screen again and unlock. however if you factory reset this bug goes away.
i find the latest version is the most stable and battery life is better if you disable all the unnecessary apps that you can i usually get rid of most of the samsung back up apps and all the google ones bar the ones it needs to run play store etc and maintaining the ones that sync for back up.
wifi was really slow when i first got it and would drop very annoying but now it seems better but have experienced slow wifi i think it's a hardware issue all note pro's have in built that should have been sorted by the latest build. i hope they finally give it an update in the coming months even to 4.4.4. or something.
Good afternoon gents!
This is the first time I post on this forum so I apologize in advance if I am not going to provide all the details regarding my problem. I'll try to be as explicit I can with my issue.
A couple of weeks ago I bought a LG Nexus 5, second hand. After one day of use the device started to randomly reboot. The odd thing is that the reboots seem to be "soft". After the device restarts there is no data loss, even the recent apps are still there. The reboots are as random as I can get, when browsing with Chrome, checking emails, or playing a game.
I tried several fixes, including costum kernels, costum ROMs and so. The problem persisted with the official KitKat 4.4.4 and Lollipop 5.0, 5.0.1 and 5.1.
Currently I am running stock Lollipop 5.1 with stock kernel and TWRP 2.8.5.2 recovery and the device is rooted.
Below I attached a screenshot with the device's current configuration and a text file with the kmsg log from the last reboot.
Faulty power button.
Reboot phone into bootloader/fastboot.
If it random reboots in the bootloader too, it's likely the power button.
Nope, I already tested this. The device reboots during use, either heavy or simply browsing the menu.
Sent from my Nexus 5 using XDA Free mobile app
I noticed this in your Log
"<6>[ 0.514020] [email protected]: Power-off reason: Triggered from UVLO (Under Voltage Lock Out)"
Just curious, Are you undervolting?
I don't know exactly what undevolting implies. Could you give me more details please?
vektor1993 said:
I don't know exactly what undevolting implies. Could you give me more details please?
Click to expand...
Click to collapse
Lowering the voltage the CPU runs at, at certain frequencies.
I understand. No, I did no change any of the voltages. In that log that I posted up there the device is rooted and has TWRP 2.8.5.2 with stock lollipop 5.1 and stock kernel. Later yesterday evening i installed xtrasmooth rom with franco kernel and the phone only restarted in Here Maps from Nokia. I'll run more tests, but from this I draw the conclusion that it is a software problem, not a hardware one. Unfortunately I can't RMA the phone. Do you lads have any other opinions?
vektor1993 said:
I understand. No, I did no change any of the voltages. In that log that I posted up there the device is rooted and has TWRP 2.8.5.2 with stock lollipop 5.1 and stock kernel. Later yesterday evening i installed xtrasmooth rom with franco kernel and the phone only restarted in Here Maps from Nokia. I'll run more tests, but from this I draw the conclusion that it is a software problem, not a hardware one. Unfortunately I can't RMA the phone. Do you lads have any other opinions?
Click to expand...
Click to collapse
Try posting another log if it happens again.
I'm back with the latest ksmg log here. I searched for fixes all over the internet and nothing seemed to fix the problem. Restarts also occur in safe mode. Below is the latest last_kmsg.
vektor1993 said:
I'm back with the latest ksmg log here. I searched for fixes all over the internet and nothing seemed to fix the problem. Restarts also occur in safe mode. Below is the latest last_kmsg.
Click to expand...
Click to collapse
This log shows a kernel panic.
My n5 reboot today without any reason
That was the only thing I understood from the log too. Do you have any idea what's the reason for these kernel panics and a possible way to fix them?
I experienced today three more random reboots. I attached down the logs. As an unexperienced users point of view all of them are produced by a "Unable to handle kernel paging request at virtual address" . Could anyone throw a look on them and give me a possible reason for these reboots and a possible fix? Thank you in advance
vektor1993 said:
I experienced today three more random reboots. I attached down the logs. As an unexperienced users point of view all of them are produced by a "Unable to handle kernel paging request at virtual address" . Could anyone throw a look on them and give me a possible reason for these reboots and a possible fix? Thank you in advance
Click to expand...
Click to collapse
Same problem as this guy
http://forum.xda-developers.com/showpost.php?p=59551481&postcount=8615
having the same problem. i'm running 5.1, but dont know if it's caused by that, cause i just got this phone as a refurbished one from google.
Good day lads!
I tried since the last post more possible fixes, and the only thing that showed some resuslt was downgrading to 4.4 bu the device still resarts exactly once a day. I am going to switch to another phone.
having the same problem. i'm running 5.1, but dont know if it's caused by that, cause i just got this phone as a refurbished one from google.
Click to expand...
Click to collapse
If you just recieved a new device and you have the possibility to RMA it, I suggest doing it. I went as far as page 30 on google searching possbile fixes and came up with no valid result.
I just flashed the latest CM12 and it's great. Also installed TWRP.
The only issue is that now when I boot my P900 shows in red: Kernel is not seandroid enforcing.
Is this a problem and, how do I get rid of it?
Agrajag27 said:
I just flashed the latest CM12 and it's great. Also installed TWRP.
The only issue is that now when I boot my P900 shows in red: Kernel is not seandroid enforcing.
Is this a problem and, how do I get rid of it?
Click to expand...
Click to collapse
your bootloader detects that, so there is no way to get rid of it.
my note 4 does this but I have actually never seen it on my P900, could you give more details on your exact model, rom, and kernel? I'm curious.
one way around that, I think, would be a kernel that is enforcing at boot, then use a script or an app to toggle it back to permissive (if necessary for your purposes)
edit: oops I see now -- CM 12, but still.. are you using the lollipop bootloader from the official update?
Hmmm.... I just rooted my Note Pro last night, stock rom with TWRP (latest). And though it boots up fine otherwise, I'm also getting the "Not SEAndroid enforcing" message. Would like that gone. And it is interesting that CM12 is having the same issue, because I was beginning to think about flashing it and ditching stock Lollipop.
Specifics: I used Odin 3.10 from a Windows 7 laptop for my initial boot flash of the CF-Auto-Root-v1awifi-v1awifixx-smp900.tar.md5 file to the tablet. No errors were reported. I also flashed TWRP 2.8.7 that way. Again, no errors. There was a beta version of SuperSU (2.49) but I didn't install that. Think I'll try it next... and hope for the best. I did install SuperSU Pro (2.46) once I'd booted the tablet, but maybe that's not available on boot?
Sterist said:
could you give more details on your exact model, rom, and kernel? I'm curious.
Click to expand...
Click to collapse
SM-P900 like you.
CyanogenMod Version: 12.1-20150707-UNOFFICIAL-v1awifi
Android version 5.1.1
Kernel version: 3.4.104-g7e89e2e
[email protected] #1
Tue Jul 7 19:20:11 MSK 2015
Agrajag27 said:
SM-P900 like you.
CyanogenMod Version: 12.1-20150707-UNOFFICIAL-v1awifi
Android version 5.1.1
Kernel version: 3.4.104-g7e89e2e
[email protected] #1
Tue Jul 7 19:20:11 MSK 2015
Click to expand...
Click to collapse
but did you at some point OTA or odin to Samsung lollipop before CM12.1?
Sterist said:
but did you at some point OTA or odin to Samsung lollipop before CM12.1?
Click to expand...
Click to collapse
Yes. I OTA 5.0.2.
I guess the big questions are:
1. Is there a fix that doesn't involve jumping back to KitKat?
2. Is having this issue in any way bad other than seeing that message on boot as everything else seems to be working.
Agrajag27 said:
Yes. I OTA 5.0.2.
I guess the big questions are:
1. Is there a fix that doesn't involve jumping back to KitKat?
2. Is having this issue in any way bad other than seeing that message on boot as everything else seems to be working.
Click to expand...
Click to collapse
I don't think there would be a way to go back to kitkat, even if you wanted to, after having installed the lollipop bootloader (happens when you OTA or Odin to stock lollipop)
to the user it's no problem at all -- it's just a visual notification to stores when you take the device back that it's been customized / modded, and voids the knox warrantee hence "Set warrantee bit: kernel"
knox, despite popular belief, is just a form of security and productive software for corporations to rely on when giving their employees a "work phone" to use, so they know that any potentially sensitive corporate information is safe from the security risks of rooting (though virtually never exploited, rest assured)
that's the most relevant answer I can give you, without repeating what I explained in my previous post *hint* lol
Slightly confused about something I'm seeing. The error is that it's NOT enforcing, but Settings, About Tablet says it IS enforcing.
Also, you mention setting to Permissive with an app (which I've found) but that sounds like it won't be enforcing either and thus we'll still have the message.
Agrajag27 said:
Slightly confused about something I'm seeing. The error is that it's NOT enforcing, but Settings, About Tablet says it IS enforcing.
Also, you mention setting to Permissive with an app (which I've found) but that sounds like it won't be enforcing either and thus we'll still have the message.
Click to expand...
Click to collapse
the display at boot is not an error, just a notification of sorts.
the only thing I can think of is the CM maintainer may have compiled the kernel to boot as permissive and switch back via script for compatibility.
I have seen some roms that do this. not many, nor recently. I wouldn't worry about it though, especially since it's a Wi-Fi device that doesn't have any reason to visit a carrier store.
also note that the notification will show when booting a permissive recovery kernel -- these notifications are not permanent nor need to be "cleared" or "reset" they just inform the user (or technician) of the S.E.A. mode of the respective kernel at the time of boot.
Thanks. I can live with that. I'm a bit OCD and an old QA professional so it'll give me pause every time I reboot and see it, but I'll get over it. <grin>
Otherwise, I have to say, the tablet is working better than EVER with CM 12.x. Apps that caused crashes no longer do. Bluetooth keyboard works again. It's faster. I have only a single bug (the running apps list sometimes has graphic issues).
Tried lineage-14.1-20170305-UNOFFICIAL-n8013.zip on a Galaxy Note 10.1 GT-N8010 (16GB), but after reboot, i am stuck in a never ending "boot logo" (?) (blue circle repeatedly shifting from right to left on a blue bow, nothing else), tried it twice, waited twice for more than 15mins, nothing changed (nevertheless, I could successfully install cm-13.0-20160831-UNOFFICIAL-n8013.zip).
Has anybody sucessfully installed 14.1 on a GT-N8010 ?
Further info: I have an additional 64GB-SD-card where I stored the aforementioned lineage file as well as open_gapps-arm-7.1-nano-20170418.zip and open_gapps-arm-7.1-stock-20170418.zip.
Tried all installations (also cm-13) using twrp-2.8.6.0-gt-n8010.
Any comments appreciated, even more so if they help getting 14.1 installed.
Regards
aqua14
2017-04-19 10:30 (MESZ)
Additional observation while again trying to install lineage-14.1-20170305-UNOFFICIAL-n8013.zip:
* Meanwhile I found that lirokoa recomended the TWRP version mentioned in the CM13 thread, i.e. twrp-2.8.7.0-gt-n8013 (instead of 2.8.6.0 in my first try) and managed to install it on my Galaxy GT-N8010, but after all, this made no difference.
* However, while carefully watching the flash log I found that the "target" was logged to be "samsung/p4noterfxx/p4noterf: 4.4.2/....", and not "samsung/p4notewifi...." as I rather would expect for a GT-N8010.
Hence my question: can it be that (a) either during the paketing of lineage-14.1-20170305-UNOFFICIAL-n8013 something went wrong, or that (b) my tablet pretends to be a different one (namely GT-N8000)? I suspect this confusion could be the reason of the aforementioned boot trouble.
At least I am sure of this fact: I haven't got a tablet with phone function, its the version only having the wifi function, and in the system info provided by JellyBean as well as KitKat I could read its the GT-N8010.
Any constructive hints or suggestions appreciated
Regards
aqua14
Additional observation:
* Both lineage-14.1-20170305-UNOFFICIAL-n8013.zip and lineage-14.1-20170116-UNOFFICIAL-n8013.zip don't work on my GT-N8010 (reboot after flashing leads to a boot loop) , whereas cm-14.1-20161208-UNOFFICIAL-n8013.zip did work (not everything tested yet, but wifi, installing apps (another keyboard, file manager, ...) worked ok.
2017-04-20
Eventually ...
I guessed just from the beginning, that the right path might again be hidden in all the tidbits given in the discussion around the lineage 14.1 thread (hxxps://forum.xda-developers.com/galaxy-note-10-1/development/rom-nougat-t3505239)
... and indeed! It took me a while to crawl through all comments, questions, answers, and unfortunately also complaints, the latter in some parts being expressed even in close-to-nasty manners. Being a developer as well (DB area) I as well appreciate constructive criticism and prefer it to demotivating complaint. However, some of the participants obviously never have learnt making an effort to keep the difference between both, maybe they are even unlucky enough not to perceive hours and hours of voluntary work of their contemporaries as a gift. Hey guys! Behave!
Whatsoever. I finally made the way through the texts and even managed to install the latest version (lineage-14.1-20170305-UNOFFICIAL-n8013.zip) and ... beneath my sincere thanks going to lirokoa (taking a bow 4 u), I'd like to greet and thank all the testers *and* contributors of helpful hints (regarding the installation of the ROM itself as well a manifold of aspects to special apps), also including especially those who took their time to precisely & factually describe which procedure did fail (!), which -in sum- made my day start successfully now!
For all those still struggling: keep trying!
After all this reading I restarted a new try and had my breakthough ~after having read the following comments in the aforementioned thread: #352/p.36, #364+#365/p.37 and some others of similar content, hence thanks also to alessandro_xda, hektor2hektor2, CDiazF04, but also all the others who keep the discussion vivid and interesting, and a special smile to miz_pimp for having increased the level of friendliness throughout the course .
And yes, I agree that many contributors are right in suggesting to include the one or other hint to the post #2 of liroka.
I guess it's presumably just lack of time on his side that this has not yet happened. On the other hand... :-> if I could walk through all the interesing discussion in one evening and draw my conclusions in order to get a free ride to another "new life" of my ol' N8010, ... I am quite positive that others can do so as well.
Continuously following the discussion...
aqua14
Thanks guys!
Just had the same problem. I just needed to upgrade twrp and try again. I really appreciate this site! Now my old tablet is doing better than my husband's new one.
Finally loaded Lineage 14.1
I have just updated my GT-N8010 with lineage-14.1-20170810-UNOFFICIAL-n8013.zip + open_gapps-arm-7.1-mini-20181010.zip & used the latest TWERP release 3.0.2 to do this.
I initially tried loading these two as above, the first issue was that having loaded them the tablet would get stuck with a battery symbol and would not boot. The way I found around this was to boot the tablet into Odin mode but choose Reboot Phone rather than going into Odin itself. This then enabled Lineage to boot but it then got stuck in a loop, the lineage logo would go through its line with a moving O, then have three O's and start again.
Eventually I found that I could get cm-13.0-20160831-UNOFFICIAL-n8013.zip to load with open_gapps-arm-7.1-mini-20181010.zip and this worked well. I then did a dirty load (No Wiping) of lineage-14.1-20170810-UNOFFICIAL-n8013.zip and this is now working without problems.
Hope this helps and best of luck!!
macgd016 said:
Finally loaded Lineage 14.1
I have just updated my GT-N8010 with lineage-14.1-20170810-UNOFFICIAL-n8013.zip + open_gapps-arm-7.1-mini-20181010.zip & used the latest TWERP release 3.0.2 to do this.
I initially tried loading these two as above, the first issue was that having loaded them the tablet would get stuck with a battery symbol and would not boot. The way I found around this was to boot the tablet into Odin mode but choose Reboot Phone rather than going into Odin itself. This then enabled Lineage to boot but it then got stuck in a loop, the lineage logo would go through its line with a moving O, then have three O's and start again.
Eventually I found that I could get cm-13.0-20160831-UNOFFICIAL-n8013.zip to load with open_gapps-arm-7.1-mini-20181010.zip and this worked well. I then did a dirty load (No Wiping) of lineage-14.1-20170810-UNOFFICIAL-n8013.zip and this is now working without problems.
Hope this helps and best of luck!!
Click to expand...
Click to collapse
Have you tried out my LineageOS 14.1 ROM? https://androidfilehost.com/?fid=1322778262904016892
I'm sorry to say that I have not as I was not aware of your rom till now so thanks for for your post and I have downloaded it just in case I find issues with 14.1-20170810. Out of interest how does it differ from 14.1-20170810
macgd016 said:
I'm sorry to say that I have not as I was not aware of your rom till now so thanks for for your post and I have downloaded it just in case I find issues with 14.1-20170810. Out of interest how does it differ from 14.1-20170810
Click to expand...
Click to collapse
Mine is more up-to-date. But I will be making a update for that ROM later this week.
Here is my thread for the ROM: https://forum.xda-developers.com/galaxy-note-10-1/development/rom-lineageos-14-1-t3848514
Oreo rom for Samsung galaxy note 10.1 gt n8000
Pls any Oreo rom for gt n8000 my nougat rom can't play videos since i rooted it, after unrooting it still can't play any video. Pls is there any fix.
Flash stock rom via Odin.
JJEgan said:
Flash stock rom via Odin.
Click to expand...
Click to collapse
Will flashing the phone with lineage 14.1 again help? Cus I can't go back using stock rom
Back to stock then flash custom rom.
Problems fixes use SEARCH.
Rom is in testing so its up to you to flash with potential problems or not .
I have the same problem. Note 10.1 N8010 and it is stuck on the logo " blue circle repeatedly shifting from right to left on a blue bow".
I cannot locate the file TWRP for the note 10.1 N8010.
The suggestions were to update Twrp but the file I have found online is (
twrp-3.4.0-0-lt03wifiue.img.tar7.5M2020-06-23 21:11:34 EDT
This file is loaded using odin and it is successful but the Twrp doesn't work anymore. Therefore, I had to go back and load the file (twrp-2.8.6.0-gt-n8010.tar).
Can someone please help me with this issue.
TWRP site is twrp.me
Có ai up rom android 7.1.2 hoặc 9.1 cho galaxy GT-N8010, qua TeamViewer không? cảm ơn.
[email protected]
Translated by GT:
Has anyone uploaded rom android 7.1.2 or 9.1 for galaxy GT-N8010, via TeamViewer? thank.
[email protected]
See your other post