yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 Android Development] bauner:
Did you also test it a complete clean install (with a known working gapps version) and without installing/updating apps from the playstore?

Because there are reports of similar problems in my cm13 rom in the last days.

So it can be possible that a google app update is causing the problem.

Did you try it with other usb cables too? Because a known problem on our device is the usb connector.

Can you access your device over an usb connection in the rom or recovery?

If you can get the rom running again you could also try to flash a stock rom with mobile odin directly on the device

https://xdaforums.com/showthread.php?t=1347899
[Galaxy Note GT-N7000 Android Development] whitedavidp:
Hello and thanks for all. I am sure I had performed a factory reset from within recovery and also wiped dalvik and cache. I also re-flashed using the exact same ROM and gapps files I originally used to migrate to NightOwl from rooted stock. But your comment made me recall that in later Android apps store some of their data outside of /data on the internal storage. And I recalled somewhere, somehow in all of this seeing that there was still old data on the internal storage. No idea how that survived the factory reset. But I never explicitly wiped the internal storage within recovery. So I did that along with another factory reset and wipe of dalvik and cache. So far, things are MUCH better now. No crazy crashing and rebooting. So my Note 1 lives on!

I am however still having USB connectivity issues. It seems that sometimes Win10 "sees" the device as an MTP but doesn't permit me to access anything. If I switch to mass storage, Win10 sometimes "sees" the device as 2 drives. But it does so only transiently. And I have not been able to access anything either way. I have tried multiple cables and USB ports. These all work with my Note 3 so that is not likely the issue but I tried anyhow. In no case can I see the device in Odin under Windows. But now that I have NightOwl working again, I see no reason to return to stock.

So please let others know that they may be able to "solve" the recent problems by being sure to wipe the internal storage as well as all else. It sucks but it seems to help so far. Still I have no idea what caused this but I am sure it was brought on by some app updates. I will try some installs of the suspect apps to see if I can cause this to happen again and will report back.

Thanks
[Galaxy Note GT-N7000 Android Development] whitedavidp:
Well, here it goes again. I installed Xplore File Manager from Play Store (I believe it was the beta version) and it did even make it through the install process of the apk before things went south. Re-did all the wiping in recovery - including internal storage and factory reset. Things are again looking ok. So I tried installing SuperSu. It installs and does not seem to cause any crashes/reboots. But SuperSu does seem to always say su binaries occupied. I have never seen this before despite having many rooted devices with SuperSu.
[Galaxy Note GT-N7000 Android Development] whitedavidp:
It does seem that the beta of Xplore is what caused things to go downhill here. Finally, after doing yet another clean wipe of everything and reflashing NightOwl and gapps I installed a pre-beta version of the app and there are no problems. I have let the developer of that app know but can offer few details.

I am still stumped by the SuperSu thing which persists in saying su binaries are occupied. But I have checked and the phone is indeed rooted and at least root mode in Xplore works.

Cheers
[Galaxy Note GT-N7000 Android Development] bauner:
It seems that the micro usb port on your device is damaged.

This is a known problem on the n7000.

The micro usb board is cheap and easy to replace.

But you need to get exact the same revision (and go sure that you not get a fake board) or you will get signal problems

https://xdaforums.com/showthread.php?t=2421145
[Galaxy Note GT-N7000 Android Development] whitedavidp:
Thanks much for the advice here. I may go this route. But for now I am using this spare device as a security camera and as long as the charging port works, I think I will have to live with this issue.

---------- Post added at 09:56 AM ---------- Previous post was at 09:53 AM ----------

Here is a response from the developer of Xplore. I mention it because, if true, this could easily impact many apps in their latest and following versions. He says:

X-plore version 3.96, when installed on some devices with alternative Cyanogenmod 11/12 ROM, entire Android system can crash and device gets to boot loop.

Why it happens? X-plore now uses latest Android development tools, and these apparently brought some compatibility problem with some ROMs, most likely that's older Cyanogenmod. Simply installing app crashes some system component, even before X-plore has chance to start, so it's not something that could be fixed in X-plore.

There is a bug report sent to Google so that they can fix it. You may click star in the bug report, raising its importance.

There is no way for X-plore to use older Android developer tools, so we shall wait if Google fixes this.​

So FYI for this and even newer versions of NightOwl. Thanks for all!

Shameless plug: this is an excellent reason to use my app, Hide Updates in Play Store. Check it out!
[Galaxy Note GT-N7000 Android Development] whitedavidp:
Just FYI, I went to check out Mobile Odin and it not only costs a fair bit but it also says to use Flashify. But Flashify would not seem to want to install the .zip so I decided to try and flash stock via Odin on another computer running XP. I installed the exact same drivers as I did on Win10 and that worked with my Note 3 phone. On that computer, once I changed USB from MTP to mass storage, both internal and external SD were recognized and displayed. I then went into download mode and Odin and again the device was recognized. So maybe a Win10 issue? glad I kept this other machine around. Flashing completed but now I have a bootloop. So I managed to get into stock recovery and performed a wipe of cache and a factory reset. Now I am running stock 4.1.2. Thanks for all!
[Galaxy Note GT-N7000 Android Development] noxcrate:
Hello, i've got some problem which is 'Unfortunately, Trebuchet has stoppped' After that, my phone keep rebooting itself. Thanks for the help.
[Galaxy Note GT-N7000 Android Development] whitedavidp:
You MAY want to check out my posts just previous to yours. If this started happening after a recent app update, it could be related. I updated to the most recent X-plore version and wham! all sorts of things starting going badly. It turns out that there is a know and reported problem with some of Google's app building tools and this seems to only cause problems for CM-based ROMS. I went back to rooted stock ROM on my device and the save version of X-plore causes no issues at all. This is not to say the issue is with CM or NightOwl, but only to say that they seem to be most affected. No idea why. In my case I had to erase EVERYTHING, (including all internal storage).
[Galaxy Note GT-N7000 Android Development] suhas_greeneyes:
Hello Everyone. I am using this rom from quite a long time.

Today suddenly my phone got restarted automatically and got stuck on nightowl screen.

After multiple restarts same thing happened. Andoid is starting up , it installed all gapps to 100 and again the same stuck on nightowl.

I clean wipe from recovery, installed the rom again. And good thing is phone boots up. But as soon as i started installing apps from playstore phone restarted again and got stuck on same nightowl screen.

I really don't know what to do. Please help guys.

Thanx in advance.
[Galaxy Note GT-N7000 Android Development] whitedavidp:
Consider the post immediately above yours.
[Galaxy Note GT-N7000 Android Development] suhas_greeneyes:
So what will be the solution to stay on the current rom??

I don't want to get back on stock rom.

Thanx.
[Galaxy Note GT-N7000 Android Development] whitedavidp:
Cannot say for sure that this is YOUR issue. But it well could be. I ended up going back to the stock ROM but am right now trying to install a later NightOwl since the stock ROM has some issues for me. You might just be able to boot into custom recovery and re-install your NightOwl. But I strongly urge you to first wipe everything - including internal SD card. It is a giant pain. But that is what I needed to do.
[Galaxy Note GT-N7000 Android Development] DoktorImEinsatz:
I would suggest you try to identify the problematic app. Do not inatall it. This helped in my case. In my situation it was a wifi management app.
[Galaxy Note GT-N7000 Android Development] suhas_greeneyes:
Thanx for help.But i guess i just finished installing the rom and started downloading whatsapp and facebook app.

Before the download completes phone got restarted and stuck on nightowl logo.
[Galaxy Note GT-N7000 Android Development] PRDR:
Are you using Greenify? For me, with the Marshmallow version of this ROM, the last few updates of that app caused the same effects you are experiencing now. When you reinstall the ROM, just tell Google not to install that app. Hopefully that will fix your issue. Then, again, it is not exactly the same ROM, but it might be worth the try. Good luck.
[Galaxy Note GT-N7000 Android Development] @quarius:
I dont know how to format the card to vfat by using TWRP. Plz show me this :confused:
[Galaxy Note GT-N7000 Android Development] Prinus:
[ROM][CM12.1][Lollipop][Android 5.1.1] NightOwl 20170312

I use TWRP 3.1.0-0 but if you are on a different version it should be similar (-ish).

In TWRP select Wipe / Advanced Wipe select sdcard0 choose Repair or Change File System / Change File System / Fat then Swipe to Change.

Please remember anything that is on the sdcard0 will be erased, so if needed make your backups first.

Edit: Removed typo
[Galaxy Note GT-N7000 Android Development] @quarius:
I have done it. thank you very much :D
[Galaxy Note GT-N7000 Android Development] toarpad:
Bootloop problem, any solution instead of wipe data?

Hey guys,

Story: I switched on the Wifi to download the latest updates from play store, and I left the phone to idle. An hour later I checked my phone again and realised that it rebooted and stuck into a bootloop. Tried to remove the battery for 5 mins ,tried to delete caches ,non of these worked yet. Wipe data /full reinstall would be the final solution for me, I want to try other options first.

Any idea/tip what can I do?

Thank you
[Galaxy Note GT-N7000 Android Development] TheVic!:
You could try clearing cache and dalvik first. If that doesnt work, then try a dirty flash. One of These usually does the trick.
[Galaxy Note GT-N7000 Android Development] toarpad:
I read some forum lately: turns out one of the updated app caused the trouble, so its a wide-problem.
[Galaxy Note GT-N7000 Android Development] angelowi96:
I flash this kernel, everything it"s okay. But my file manager force close every i browse my files. I download root explorer, it's have same problem.. Anyone can give me answer how to fix it? Sorry if my english so bad...
[Galaxy Note GT-N7000 Android Development] bauner:
can you go into settings-storage or will it also force close?

Did you also try it with a known working file manager like es file explorer?

https://play.google.com/store/apps/details?id=com.estrongs.android.pop
[Galaxy Note GT-N7000 Android Development] angelowi96:
I have try root explorer and es file manager, but it's have same problem... Flash again maybe fix that problem. I'll try again
[Galaxy Note GT-N7000 Android Development] whitedavidp:
I recently had terrible problems with some apps on this ROM. It later turned out to be Xplore File Manager. That developer (and likely others) transitioned his development from an older Android dev platform to the newer one and the problems began. But only on CM-based ROM. I posted about it here and it likely impacted other CM-based ROM as well although I don't know for sure. I had to completely re-install the ROM after clearing everything including the internal SD. I then installed an older version of XPlore and it worked fine. The developer of Xplore has released a new version said to fix this. But I haven't tried it. Of course, your issue could be different.
[Galaxy Note GT-N7000 Android Development] bauner:
can you go into settings-storage or will it also force close?
[Galaxy Note GT-N7000 Android Development] IronRoo:
FYI, should anyone run into a similar problem

After updating some apps (wife hadn't done it for a few months), though I cant say if this was actually related or just a coincidence or someone tried to hack her(see below), the phone kept getting the message saying, "“Unfortunately, Trebuchet has stopped" making the phone unusable as it just kept popping back up. I tried a couple of things to fix it incl. wiping cache & dalvik through TWRP, reflashed ROM, reflashed ROM & OpenGapps (using the switch from another Gapps provider as per the TWRP FAQ, as I still was on an old TKGApps package! Which could have been the reason). Anyhow, nothing fixed it!

So I have taken the opportunity to upgrade her to NightOwl 14.1, something I've wanted to do for a long time but she wouldn't let me, anyhow it's now VERY important to upgrade I believe due to the two very bad security related bugs BlueBorn & KRACK so I recommend EVERYONE also upgrades! ;) Now you may think you won't be affected but Avast popped up a message saying something like "warning, your SSID has changed" so could have been a neighbour trying to use the Krack exploit (but probably just a coincidence) & we would have never known without Avast!!
[Galaxy Note GT-N7000 Android Development] whitedavidp:
Hi there. As I posted here, I think your issue was caused by some recent versions of apps where their dev's migrated from an older version of the development tools to a newer version. This seemed to affect only CM-based firmware (for reasons unknown to me). I know this happened on NightOwl 13 as well. I was told by the dev of the app that trashed my NightOwl 12 install (Xplore File Manager - great app and dev) that there was a bug posted with Google. I know that the same dev has released a newer version of that app which he claims fixes this problem. I have since moved on to NightOwl 13 but am not yet ready to risk this install by trying to update.
[Galaxy Note GT-N7000 Android Development] IronRoo:
Thanks for your reply. I did see your posts previously and did wonder if that was the issue but thought it wasn't related as Trebuchet was not mentioned, but you could certainly be right. Anyhow I've taken the chance to move up to Android 7.1 so the wife is on the same as me now. Good to hear you have fixed yours also.
[Galaxy Note GT-N7000 Android Development] Boombastical:
Hi IronRoo, I'm still on NightOwl 12.1 and I have already one month the same issue with „Trebuchet“ launcher and also with „Nova launcher“ not be able to stay in memory and force close in the almost infinite loop. I wrote „almost“ because I had a „luck“ few times to fully open my list of apps from trebuchet and to use all apps which I wanted living them open and restart them from opened apps. Also, I found other way to use my apps and to start them from „Play store“ and one more way is to install „Revo uninstaller“ and then from that app there is an option to open any installed app too... I tried same like you clearing all caches even I tried the „dirty install“ of whole ROM with gapps but it didn't fix it... So, at this point I'm on the way to remove one by one app and trying to see if it will help to stop crashing trebuchet because I also suspect that recent update of some of the app has to do with this problem. I am on the way to install Lineage 13.1 after that so we'll see the progres after all this... How do you like Lineage 14.1 comparing with older versions of it... ?
[Galaxy Note GT-N7000 Android Development] IronRoo:
Thanks for the tip, I also managed to get trebuchet working briefly, but it didn't last long & the wife wouldn't have been able to cope with work arounds.

I've been on LOS14 on an S4 Mini for about 6mths & was on CM13 & LOS13 before that. Now that LOS14 has the quick settings tile back I'm very happy with it, especially the one tap quick settings menu for WiFi etc. Wife is also very happy with it on her note & she doesn't like to change as a rule. So I'd say going straight to LOS14 is worthwhile, everything has been working perfectly on her phone. Only issue for me is LinuxSE is not enforced on these two new Nightowl ROM, but I will edit (hopefully as I haven't checked if kernel supports, or even if it must)
[Galaxy Note GT-N7000 Android Development] bruderherz:
Thanks a lot!!!!

The best Rom that I've ever tried

After testing 10 various Roms, this one ia really alive and old device is working so well, as of it were new one. Thanks a lot for this fantastic work!!!!!

Best wishes,

Thanks!
[Galaxy Note GT-N7000 Android Development] hayati1:
Yes, good and smooth...
[Galaxy Note GT-N7000 Android Development] imamemass:
Verry good yeah
[Galaxy Note GT-N7000 Android Development] drickles:
Got a question. So I'm tryna flash this rom but then it dawned on me. After flashing the phillz outdated recovery my sd card seems not to be able to mount in the recovery. But then it works perfectly when the phone is on.

My question is is the sd card not mounting because the recovery is outdated? Because my usb port has a problem and I don't have any master reset options like odin or kies available to me in case i install the updated recovery, phone cant boot up, and my sd card still wont mount. That means I've doomed my phone.
[Galaxy Note GT-N7000 Android Development] bauner:
There are no known problems with the sdcards in the recovery.

Are both sdcards not working?

Did you try to format it in the recovery as vfat?

There is also a app mobile odin lite/pro which can flash (stock)Roms without a pc

https://xdaforums.com/showthread.php?t=1347899

https://play.google.com/store/apps/details?id=eu.chainfire.mobileodin.pro
[Galaxy Note GT-N7000 Android Development] Nautikus:
Endless boot loop

Hi,

I use the CM 12.1 (built 20170312) since two years without problems :). Suddenly, the Note 1 starts booting and it says that the applications are optimized. When all apps are optimized the Note 1 boots and starts from the beginning :(.

My guess is, that there is not enough space in the partition to finally start the system. What can I do? I went into the recovery mode (PhilZ Touch 6.59.0) and made a "wipe cache", but the problem is not solved.

I`m planning to repartition using Lanchon's REPIT. But he mentioned, that this might not work with PhilZ.

I would appreciate any advice.

Thank you in advance

Frank
[Galaxy Note GT-N7000 Android Development] Eddicts:
Try to reinstall/reflash the cm rom again.
[Galaxy Note GT-N7000 Android Development] Nautikus:
boot loop when starting apps

Thank you for the suggestion. I successfully installed update package Nightowl-cm12.1-20170312-n7000.zip again. But still after optimizing the 116 apps it says "starting apps" and than it boots again.
[Galaxy Note GT-N7000 Android Development] bauner:
This could be the same problem wich many users have also with lineage 13

Here you can find some more informations:

https://xdaforums.com/showpost.php?p=74283137&postcount=364

You can try to do a complete clean install again.

Then only install 1 app at each time.

If you will run int the problem again then you know which app will cause it and you can ask the developer for a app update which is builded with build tools >=27
[Galaxy Note GT-N7000 Android Development] whitedavidp:
When this happened to me it was after just updating some apps. It turned out to be a problem with an app called Xplore but it was due to something in Google's app build system that is supposedly been fixed. To get around this I had to erase the internal SD card memory before flashing NightOwl since some part of the app remained in there and was causing the problem. Good luck.
[Galaxy Note GT-N7000 Android Development] drickles:
How do you do that please? I'm faced with a similar problem after I factory reset my phone. Now I can't download or store anything on the phone. Can't even snap pictures. Camera hits me up with that same error every time I open it. I've tried flashing the repartition zip plenty of times in hopes of fixing this But it doesn't work. It seems there is a partition missing or not showing up. I would have placed my phone in a pc to try and see if I could format that partition but problem is my usb port is busted and can't display the contents on my phone on a pc. Please help me out anybody.
[Galaxy Note GT-N7000 Android Development] whitedavidp:
Not sure I exactly recall but I am pretty sure I must have done this from within recovery. It was NOT a standard wipe option as I recall.
[Galaxy Note GT-N7000 Android Development] drickles:
Thanks man. What you said really helped. Gave me the idea of formatting the sdcard0 and system partition all together from recovery and installing the rom from scratch. After doing that I reflashed the repartitioning zip and it worked. Thanks a lot.
[Galaxy Note GT-N7000 Android Development] whitedavidp:
Glad that helped. Be careful adding apps back. It is likely that one of the last apps installed before this happened is the issue. Not blaming the app developer.
[Galaxy Note GT-N7000 Android Development] _Vicky _7:
Storage Not Working

after falsh rom external storage not open..can not open file

error-external storage has stooped

external storage keep stoping.
[Galaxy Note GT-N7000 Android Development] Nautikus:
Mobile Phone in Boot loop

"erase the internal SD card memory" means most probably to enter recovery mode (PhilZ Touch 6) go to "wipe and format option" further to "custom", than I can select between "format /system", "format /cache", "format /data", "format /preload" or "format /storage/sdcard0".

What would be your suggestion?
[Galaxy Note GT-N7000 Android Development] bauner:
this seems to be a problem with one of your sdcards.

first you can try to remove your external sdcard and try it again.

if it now will work you need to format your external sdcard1 in the recovery as vfat

if it will also not work then try to format the internal sdcard0 in the recovery as vfat

if you got the bootloop after installing an app then a factory reset should fix it.

If you have installed any mods like xposed then you should try a complete clean install.

factory reset-format /system-install rom +gapps
[Galaxy Note GT-N7000 Android Development] ICEBERok:
Hey. Need help, some applications cause bootloop on this firmware, they say about BugBash-1052, and problem with Gradle. I know that this problem has surfaced in many CMs 12.1 and 13 and has already been solved with the help of patches. I install a patch for CM 12.1, the lib "libandroidfw" is updated, but the phone does not load beyond the model name. Help please solve the problem, maybe you need a patch specifically for this firmware? On LOS 14, there is no such problem, but I would like to stay on 5.1.1. Thank you in advance

I do not speak English well, I wrote with an interpreter, so I apologize. if something goes wrong.
[Galaxy Note GT-N7000 Android Development] dreamteam:
head's up

https://xdaforums.com/showpost.php?p=74842530&postcount=464
[Galaxy Note GT-N7000 Android Development] bauner:
I will make a new cm12.1 rom with the fix included in the next time
[Galaxy Note GT-N7000 Android Development] dreamteam:
it is a great news !!!!! many thanks to bauner
[Galaxy Note GT-N7000 Android Development] ICEBERok:
Thank you very much for the help!

If you do not mind, I would also like to ask you which of your firmware is best for N7000, 5.1.1 or 6.0.1?

Due to the above mentioned problem, I have now gone over to LOS 13, on it a third-party patch helped to solve the problem, on the whole, everything is fine with it. Many thanks for your hard work.
[Galaxy Note GT-N7000 Android Development] bauner:
The CM 12.1 20180124 rom is finish

Changes:

* Fixed some Apps/App updates can cause a bootloop

* Fixed whatsapp videocall colors with back camera

* Allow installation on GT-I9220

This will be my last cm12.1 version