yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 Android Development] Gold Mix:
Don't Even Think About It

No, AFAIK SHV-E160L has Qualcomm Snapdragon SOC whereas N7000 has Samsung Exynos. To confirm, install any phone info app like cpu-z or similar and check SOC, it could be shown as cpu/chipset/platform. If it shows anything other than Exynos 4210, don't even think about it.

You should only look for roms made for your model number, or if there are other Note variants with the same SOC. Otherwise, you will brick your phone
[Galaxy Note GT-N7000 Android Development] umarharoon:
I was asking this cause i have read many post about where you can convert SHV-E160L TO N7000. So if i convert my SHV-E160L TO N7000 can i use this rom? is it possible?
[Galaxy Note GT-N7000 Android Development] Gold Mix:
I remember seeing some nonsense posts about conversion before. IMPOSSIBLE. You can convert devices of different models, only if they have identical hardware.

They can play with firmware files and make it show anything they like, even a different brand, but that doesn't change a thing. The hardware is what matters!
[Galaxy Note GT-N7000 Android Development] tuxayo:
Hi :)

Is only looking at the SOC ok?

Could a variant with a different model be also not safe for flashing?

edit: modem, not model....
[Galaxy Note GT-N7000 Android Development] tuxayo:
Thanks lee.wp14 for giving a new life to the old N7000 that I got from my father :)

Great for testing stuff, troubleshooting issues and for a backup phone.

Speaking of troubleshooting issues:

Does anyone here has an idea why could the OS stop booting being stuck at the animation?

After a week of light usage with various boots. Now the animation never stop for more than 20 min and it seems to give up after some times.

The logcat (attached) shows that it boots far enough to have adb working (hence the logcat ^^) and it tries and fails in loop to start some services.

I literally have WTF errors due to Terrible Failures.

01-01 08:56:21.244 28756 28756 E AndroidRuntime: Error reporting WTF
01-01 08:56:21.244 28756 28756 E AndroidRuntime: java.lang.NullPointerException: Attempt to invoke interface method 'boolean android.app.IActivityManager.handleApplicationWtf(android.os.IBinder, java.lang.String, boolean, android.app.ApplicationErrorReport$ParcelableCrashInfo)' on a null object reference
01-01 08:56:21.244 28756 28756 E AndroidRuntime:	at com.android.internal.os.RuntimeInit.wtf(RuntimeInit.java:387)
01-01 08:56:21.244 28756 28756 E AndroidRuntime:	at android.util.Log$1.onTerribleFailure(Log.java:110)
01-01 08:56:21.244 28756 28756 E AndroidRuntime:	at android.util.Log.wtf(Log.java:304)
01-01 08:56:21.244 28756 28756 E AndroidRuntime:	at android.util.Slog.wtf(Slog.java:82)

I don't remember any significant event before the phone stopped booting beside maybe a battery exhaustion.

dmesg attached also.

logs: https://drop.infini.fr/r/UOf5IzKoBS#EJhx/qN6NWtHLMVBGo47pJE6iNJckefEP4KExgI4Stw=

Is the actual error "No start tag found in package manager settings"

?
[Galaxy Note GT-N7000 Android Development] AlGaib:
Hello there,

I just found a Galaxy Note n7000 in the trash and it is working quite properly, I'd like to flash lineageOS to it but I don't understand how flashing works on this device, all the tutorials for flashing TWRP assume you already have TWRP or CWM but I have none of this on the phone? It seems that the recovery should be bundle with the ROM from what I understand but I don't find any rom that I can just flash with Odin to then have TWRP or CWM and bring a more modern ROM with a modern Recovery...

So yeah my question is, how do I get on with modding my n7000 when it is totally unmodified?

Edit: So yeah I managed to follow the LOS13 topic instructions to start from scratch, I install LOS13 and TWRP 3.1.0-0 build2 recovery (IsoRec) but when I flash the new recovery to then install the LOS16 rom my phone gets stuck in a bootloop and I have to start again from scratch (maybe I don't get some flashing instructions, I put the zip file in "n7000/misc/recovery" but I'm not sure if that's what really required, either way I don't see much more options...

Can anyone here guide me a little bit for this step? Any help would be greatly appreciated :)
[Galaxy Note GT-N7000 Android Development] Gold Mix:
If it's identical hardware, the rom should work fine. Yes, in some cases there will be issues with the modem and you will need to try to change its default settings and see if that works, or flash the modem for your region.

---------- Post added at 10:10 AM ---------- Previous post was at 09:39 AM ----------

This is the culprit. Did you try to start the phone before charging, and it switched off during boot?

The exact same thing happened to me. I followed a guide to re-calibrate the battery, by fully discharging the battery until phone switched itself off, and couldn't start again, and then fully charged the battery before starting. The phone went into boot loop. The only way I could solve it is by doing a factory reset.

I think this is a serious bug in this rom. So if you exhaust your battery, or find your phone switched off. Don't attempt to start it before sufficiently charging the battery

---------- Post added at 10:54 AM ---------- Previous post was at 10:10 AM ----------

If you need help, provide detailed description of your issue. Which version are you trying to install, 20190522 or 20191009, and which recovery? There are 2 of them!

if you are installing 20191009, you must follow the instructions in post #2 README FIRST
[Galaxy Note GT-N7000 Android Development] tuxayo:
Thanks for the clarification.

Hoooooo. I didn't know it was at 0% so I started it. I don't remember if it naturally got again 0.5% and thus tried to boot. Or if just refused to boot at all and I had to charge it.

So this is likely the root cause.

Because it would cause some corruption? Is your /data also formated to F2FS?
[Galaxy Note GT-N7000 Android Development] Gold Mix:
Yes, initially my /data was F2FS when this happened. Do you think it could be related?

I changed it later on to Ext4 not because of this, but one thing, I was getting some weird erratic bluetooth transferred files behavior showing 0 size and not opening. I don't know, if this could also be related to emulated storage! Another thing, one day out of the blue when I was using chrome, it went to a kernel panic, and neither phone nor recovery worked, only showing black screen kernel panic, and only download mode worked. Anyway, I managed to solve it basically by trial and error trying many different things as described in a previous post. I thought this could be a reason so I formatted /data to Ext4

Now I'm facing another issue :laugh: I use this phone mainly for a professional telegram group I joined, and several times already while writing a message, it freezes for a while and then I get a black screen watchdog reset. It works fine after restart, but this is becoming tiring really. This rom is nice, but I don't think it's stable. I think I'll probably go back to [MENTION=799465]bauner[/MENTION] Nightowl 14.1
[Galaxy Note GT-N7000 Android Development] tuxayo:
This is actually the second time it happens to me. I've reinstalled on a ext4 /data partition and I will see if the issue happens again.
[Galaxy Note GT-N7000 Android Development] krizstyle711:
Noob here (like, REAL noob). Is there a baby steps beginner guide to do this (links appreciated)?

I am eager to make android 9 available on my N7000 (I have a SM-G7102 that I am using so its just to make available a secondary phone)

Also, just to confirm, "proceed to bauner's LOS13.0 thread for installation steps", is it "ROM LineageOS13.0 Marshmallow Android 6.0.1 NightOwl 20171029-Fixed"? do I follow that or apply the steps in this post but referring to the Bauner post?

Thank you so much!
[Galaxy Note GT-N7000 Android Development] andromaider:
I've the same Error when I was flashing the script, while it was flashed external SD nor /tmp.
[Galaxy Note GT-N7000 Android Development] lee.wp14:
EDIT: no more long grandmother stories. This ROM is back to work in progress now.

If you happen to be able to get a GPS fix, or able to get any GPS signals, do ping me at once. Thank you.
[Galaxy Note GT-N7000 Android Development] lee.wp14:
Yes, you are correct.

Which recovery you are on now?

I actually didn't believe in F2FS causing problems because I never had troubles with F2FS for like years. Every device that I use, if there's F2Fs support then definitely I will use F2FS.

I once hear my friend say that he stay away from F2Fs because it is buggy. Now I believe.

I will now advise everyone who use this ROM to switch to ext4 whenever possible.

@tuxayo thanks for your logs. Indeed, it should be problems with F2FS. The errors are related to I/O. How is it with ext4 now?

@Gold Mix thanks a lot dude. You helped a lot of people. About the problem with Telegram, I will check on it once I'm done with my stuffs.

And also, those who has tried their GPS and have it working please ping me. Just wanted to know how many of you got it working.
[Galaxy Note GT-N7000 Android Development] bro55her:
I installed this rom without any problem after that I flashed stock 4.1.2 and pit with odin then rooted and philz again but when ever I flash bauners kernels to update my recovery device bootlops I tried cm 12 and cm13 kernel before insalling this rom there was no problem. Can someone help? (At the moment I am using Stock 4.1.2 I flashed it after bootlop with odin no problem with stock rom) but I need help with this. Thank you :)
[Galaxy Note GT-N7000 Android Development] DoktorImEinsatz:
Just for the record: I'm on F2FS and everything is fine.
[Galaxy Note GT-N7000 Android Development] lee.wp14:
Can you still restore your device back to stock using odin?

Thanks mate! Glad things work fine for you.
[Galaxy Note GT-N7000 Android Development] bro55her:
Can you still restore your device back to stock using odin?

Yes I restored my device and using stock at the moment but if I flash bauners kernels It bootloops so I tried to flash another rom I was using before miui rom gt n7000 and device bootloops, before flashing this rom and twrp emu there was no problem with these something strange happened looks like even I cant fix it it is not big deal it is not my main device but its legendary GT N7000 thx btw and i like installing roms and tinkering so I dont wanna stuck with stock rom :) thank you
[Galaxy Note GT-N7000 Android Development] tuxayo:
My GPS seems to be working pretty normally, aside from not being able to fix GLONASS satellites.

Though I remember that like 3 times in the previous 2 months, suddenly had no visible satellites and had to reboot the phone to be in a working situation again.

It didn't happened to me in a while though I'm using the GPS a lot.

Thanks for the confirmation. What part of the logs mention I/Os. I couldn't understand this mess.

My ext4 is fine despite many voluntary and involuntary abuse to reproduce the issue. Now I'm switching to F2FS to confirm that it causes issues. Not my main phone so I can try anything dangerous on it if that can help.

^^
[Galaxy Note GT-N7000 Android Development] lee.wp14:
It's kinda weird. Anyway which stock ROM you are on? Official jellybean or ICS/GB?
[Galaxy Note GT-N7000 Android Development] lee.wp14:
For your information, we are using BCM4751 which is technically the same gps chipset on N7100, I9300, Nexus 7, Nexus 9. Since quite sometimes before, the smdk4210/4412 developers has been using gps blobs from Nexus 9, in which the UnlegacyAndroid project kind of like make changes to their gps blobs so it works on newer android. And also worth mentioning, Nexus 7 and Nexus 9 has official 5.1.1, if we were to compare with our samsung devices. So developers use the gps implementation from nexus 9 developers.

Since Android 8.0, the gps implementation from Nexus 9 developers didn't work well. The driver is working, the chipset is working, and the problem is you won't get a fix. You might sometimes, even not able to get any satellite signals. I was told by a I9300 developer that the AGPS is not working so it will slow down the gps fix greatly.

There are I9300 users claiming that their GPS is working and can get a fix. So it's the same situation here at least. I have a new n7000 device in which it is initially from CM12 and I tested the gps before flashing to LOS16. CM12 gets a fix in 3 seconds. LOS16 didn't even able to get satellites signals at all for me. From my past experiences with LOS16, I was able to get a fix after more than 12minutes, on highway. Getting gps fix is like finding needle on the ocean floor to me.

To sum things up:

1. Already for certain AGPS is not working since Oreo.

2. How the hell some users can get fix while some cannot. If you can get a fix then Congratulations! :D

Maybe I should get a GPS-only device and try see if I can get a fix. It will be great if my country launches a gps satellite.

If you see the part after "--------- beginning of system", there's such a line:

01-01 08:50:08.884 21838 21838 E UserManagerService: Unable to read user 0

user 0, which means the system is attempting to read your data, default user is user 0. It is in location /data/user/0.

So... without loading user 0, for certain the system won't boot.

Back to the f2fs problem. Let's assume that f2fs caused data corruption. If you are using a f2fs setup, then you have at least the /data formatted as F2FS. So let's say that somehow /data got corrupted. Here's the cause then.

Although like the user above earlier, I never have problems with F2FS. Maybe it's just luck tho. Nevertheless, Ext4 is the best! I really find EXT4 a very stable filesystem.
[Galaxy Note GT-N7000 Android Development] bro55her:
Official 4.1.2 Jellybean
[Galaxy Note GT-N7000 Android Development] lee.wp14:
Maybe you can start from something lower like cm11, and slowly move on.
[Galaxy Note GT-N7000 Android Development] bro55her:
I dont have time for slowly moving.

Maybe I will try that later.

But thank you :)
[Galaxy Note GT-N7000 Android Development] lee.wp14:
https://xdaforums.com/showpost.php?p=79333071&postcount=179

A good read on F2FS.
[Galaxy Note GT-N7000 Android Development] bro55her:
I fixed my problem :D

My device wasnt booting when flash bauner cm kernels so I flashed twrp from the cwm after flashing bauner kernel now I can install roms again. Btw great rom I will use this again.
[Galaxy Note GT-N7000 Android Development] Werve:
I tried several times to install this Rom and I realized:

- installing TWRP-3.1.0-EMU-MIGRATION-M-20170318-noassert.zip I can't run lanchon-twrp-patcher-20160417-n7000.zip because it indicates an error in the recovery image. And I can't flash the rom because the device is marked as i9100

- I can correctly run lanchon-twrp-patcher-20160417-n7000.zip if I installed i9100-LOS-16.0-Emulated-Storage-TWRP-3.3.1-1.img and also the ROM but at startup it displays the animation for several minutes and then the device restarts in recovery.

I tried both ext4 and f2fs partitions type. I tried flash recovery.img and boot.img.
[Galaxy Note GT-N7000 Android Development] lee.wp14:
Did you override the rom kernel with other kernel after ROM zip installation?

Yes, you'll need to patch the twrp on the latest twrp (3.3.1-1). This comes after the repartitioning.

Edit: my apologies, there's a missing step in the firdt post to indicate the installation of twrp 3.3.1-1. Will update it soon.
[Galaxy Note GT-N7000 Android Development] mp0:
Installing release 20200225 coming from 20191009, tried many times including total wipe, no phone.

many thanks for your work :) .
[Galaxy Note GT-N7000 Android Development] lee.wp14:
What do you mean by no phone?
[Galaxy Note GT-N7000 Android Development] mp0:
After starting I've been asked for my sim-pin, all ok, phone unlocked. phone tries to connect to my service-provider, no connection. manual looking for all providers, no connections. endless looking for.
[Galaxy Note GT-N7000 Android Development] lee.wp14:
Wow seriously… sorry to hear that ?

Please try to replace this file from the older build (I'm away from pc):

/system/vendor/lib/libsecril-client.so

Or you can get it here:

https://github.com/leewp14/propriet...00/proprietary/system/lib/libsecril-client.so

But it makes no sense because unlike the wifi, all n7000 has same modem so it should work if it works on my side. Strange.
[Galaxy Note GT-N7000 Android Development] Werve:
I have never flashed a kernel after Rom but I have tried a few times before, using Nightowl-lineage14.1-20180318-n7000-kernel_only.zip

There is also a strange behavior of Wifi. Trying to install the bauner's roms again, Wifi doesn't seem to work (on some roms it scans the networks correctly but doesn't connect). The only Rom that still seems to work is by restoring a backup of RR 5.5.1, but if it does a factory reset it also stops working.

Edit: Actually the wifi scan seems display fake SSID (comparing with a scan from another device at the same time)
[Galaxy Note GT-N7000 Android Development] lee.wp14:
This is really strange.

So the latest build simply won't work at all on your phone?

About the wifi, can you check the contents of /data/.cid.info? This is to see whether your mac address is being mapped in the macloader library.
[Galaxy Note GT-N7000 Android Development] Werve:
All the different attempts were made with the last build, I'll try another version later (any preference?).

I didn't specify that I also tried flashing isoRec disabler.

Also in the last tests (bauner's roms) I repartitioned the sdcard at 8G so data is at 5G, it's a problem for this build (should I repartition?).

I assume that /data/.cid.info I need to see it on the roms with wifi working, so I'm reinstalling the backup.

That file isn't in the backup of RR. There are .wifiver.info and .mac.info

.wifiver.info

DHD_ver: 1.141.44.4 (r)

Firm_ver: wl0: Dec 5 2012 00:59:58 version 5.99.10 (JB) (WFD)

Nv_info: manfid=0x2d0

.mac.info

50:CC:F8:4C:0D:59

EDIT: I think I figured out what's causing the wifi. I noticed that creating a guest network on the router did not present connection problems, so after several tests on the settings I found that even leaving the Protected Management Frames on "capable" did not allow note 1 to connect. Strange that it works if i restore the backup with his own /data

I tried to flash boot-222aec6.img kernel but still latest build after some minutes in boot animation it will reboot to recovery

The same happen with 20191009 build with following the installation notes.

Here the recovery logs https://mega.nz/#F!EohTFDhB!9JGn9O2tVQmbt_9g4cT2iQ
[Galaxy Note GT-N7000 Android Development] mp0:
Tried so, but no works. Hint: in version 20200225 there is no libsecril-client.so.
[Galaxy Note GT-N7000 Android Development] lee.wp14:
Your situation I was able to recreate (it happened to me last night), when I attempted to use a aosp kernel on lineageos. LineageOS services failed to load on boot and cause the kernel to panic. After looping for a few minutes due to failed in starting the zygote, it will reboot into recovery. That's the reason I asked whether did you override the kernel but for your case you didn't so... unless we have the logs, we don't know what's the problem.

I attached a file here (extract the zip) so that you put it in /system/etc/init.d after performing a clean install of the latest build. Afterwards, you may reboot and let it loop until it reboot into recovery, and you may get the logs from /data/local/logcat.txt and attach here.

For the wifi, 50:CC:F8 is listed in the mac address mapping in macloader. However, if there's no /data/.cid.info means macloader is not being loaded. I'm not really sure what it has to do with the normal usage of wifi but according to other people macloader is quite important to get the wifi work well. I'm quite a new n7000 user so I'm not pretty sure what it has to do with the wifi. By the way, my n7000 is also 50:CC:f8.

you can try to get a root shell and execute "macloader" and see if it runs. If command not found, maybe macloader is not included in the rom.
[Galaxy Note GT-N7000 Android Development] lee.wp14:
]I attempted to use source-built libsecril-client.so for this latest release, and as per checking the libsecril-client.so is now in /system/lib instead of /system/vendor/lib. You may delete that one and try put the old one in /system/vendor/lib again.

I think I broke the SIM PIN Operation in the latest release. Try reverting all the changes to libsecril-client.so (or perform zip install again) and turn off PIN Lock using another phone and try put it back again on this phone.
[Galaxy Note GT-N7000 Android Development] Werve:
How can I attach a file directly here? (maybe I can't until I get 10 messages?)

Attached here https://mega.nz/#!RxZ2xYwC!l6xt9RxKSePTL6XByYYxe-zywiu7qBz2po5o_Hk2nXo (in the same folder of previous link)
[Galaxy Note GT-N7000 Android Development] lee.wp14:
Thanks for the log.

Try to delete /data/system/storage.xml and see. It seems the system is confused with your storage configuration.

And just to confirm,

1. Are you on twrp 3.3.1-1?

2. Did you wipe fully the data partition? Not the tick to format, but the one that you press " format data" and type yes to format.
[Galaxy Note GT-N7000 Android Development] mp0:
That's it! With PIN-lock OFF it runs like a charm :) . Thank you very much and happy coding!
[Galaxy Note GT-N7000 Android Development] lee.wp14:
Thanks for the feedback and sorry for the trouble! I will revert the effected changes in next build.
[Galaxy Note GT-N7000 Android Development] Werve:
There is no /data/system/storage.xml

1. Yes

2. Oh, no tried that now. Reinstalled rom, but still the same.

New log: https://mega.nz/#!5hZwRCwK!5KRPNbdyEE-MabtZDhSXpjX7v0tYgcaX0vWO4q8bObw
[Galaxy Note GT-N7000 Android Development] lee.wp14:
Did you install the TWRP app when prompted?

03-06 17:10:51.100 7186 7186 E System : java.lang.IllegalStateException: Signature|privileged permissions not in privapp-permissions whitelist: {me.twrp.twrpapp: android.permission.READ_PRECISE_PHONE_STATE, me.twrp.twrpapp: android.permission.BATTERY_STATS, me.twrp.twrpapp: android.permission.PACKAGE_USAGE_STATS}
03-06 17:10:51.100 7186 7186 E System : at com.android.server.pm.permission.PermissionManagerService.systemReady(PermissionManagerService.java:2005)
0

Didn't saw this just now as I was reading the logs on phone.

You may try to delete the app manually and reboot see if the issue persists, the app is in /system/priv-app/twrpapp.
[Galaxy Note GT-N7000 Android Development] Werve:
Yes i did.

With the recovery file manager after reboot (with the log) the /system have only 2 folder bin , usr and none files.

Good news, reinstalled the rom without the TWRP app and it finally booted! Thanks for the help :)
[Galaxy Note GT-N7000 Android Development] lee.wp14:
Glad it works for you now! As a side note, you will have to mount /system in the twrp MOUNT menu beforehand, or else it will only show files which exists in the ramdisk.
[Galaxy Note GT-N7000 Android Development] tuxayo:
I was able to break my install 5 or 6 times by trying to boot without enough battery to cause a shutdown during boot.

Also by removing the battery during boot. It wasn't as efficient as messing with battery level. A bit surprising.

Anyway, the results confirm that the build of 2019-10-09 with the kernel 3.0.101 are not safe to use with F2FS
[Galaxy Note GT-N7000 Android Development] lee.wp14:
Thanks for the feedback. By judging from the way how f2fs works (you can read the post that I shared earlier) this is to be expected.

I will try to get more f2fs fixes should there's any.

We can't say that f2fs is bad… it's the way how it provides advantages over ext4.
[Galaxy Note GT-N7000 Android Development] tuxayo:
After reading I had the impression there were no issues actually. :o

Is testing with the latest build useful?