yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 Android Development] lee.wp14:
Since on pie, we repartitioned internal sdcard to the minimum 4MB, thus I don't think LOS14 can work well.

You may try to repartition back by renaming the repit file to the following and flash:

lanchon-repit-20170115-system=1.5G+wipe-data=max+wipe-sdcard=7.2G+wipe-i9100.zip

After that, flash bauner's isorec and bauner's kernel (https://xdaforums.com/devdb/project/dl/?id=27126) (do not reboot in between), and then reboot recovery. Perform a full /data wipe, and proceed to flash bauner's LOS14.

Do tell me if it works, as I never tried it before, I'm cannot confirm that it will work.
[Galaxy Note GT-N7000 Android Development] jerryspring:
I still have that gapps question
[Galaxy Note GT-N7000 Android Development] D@rekills4:
Getting "ERROR 1" when I try to flash the repit file, screenshot attached.

Any suggestions?
[Galaxy Note GT-N7000 Android Development] lee.wp14:
This is interesting. Did you connect your phone to the computer to copy zip files? Try to disconnect the phone from pc before repit.
[Galaxy Note GT-N7000 Android Development] jerryspring:
Yeah. Take the word zip out on the end. Lol

---------- Post added at 05:03 AM ---------- Previous post was at 05:00 AM ----------

https://github.com/rovo89/XposedInstaller/issues/336

Lol
[Galaxy Note GT-N7000 Android Development] D@rekills4:
After viewing some of my old posts in this thread, I see that I never partitioned the phone in the first place.

So I flashed LineageOS 14.0 directly on top of your emulated storage based recovery and it's working.

I already tried everything suggested by TWRP, by removing connection to PC, then rebooting recovery, disabling MTP, etc.

It's not able to read the partition table, I don't think anything is wrong with the file name.
[Galaxy Note GT-N7000 Android Development] lee.wp14:
Thanks for reporting back. The whole repartition to emulated thingy is quite confusing at first, and after quite sometime tinkering around with the sources and some analyzing, it seems that without a repartition everything should work too. But I dare not to attempt this as users over galaxy s2 forums followed the los16 guide closely to repartition their phone before flashing pie. Glad that it works for you!
[Galaxy Note GT-N7000 Android Development] jerryspring:
Dude. I see the output in twrp. U have zip.zip. It won't flash cuz of it!
[Galaxy Note GT-N7000 Android Development] jerryspring:
Seriously?
[Galaxy Note GT-N7000 Android Development] jerryspring:
Error 1 means it can't read the zip cuz it is a conflicting flash! Dude. Ur lucky u didn't bork your phone! You have zip twice in the file name!
[Galaxy Note GT-N7000 Android Development] lee.wp14:
This is a development thread, do not post off-topic stuffs. Arguments are not encouraged. Mind your language.
[Galaxy Note GT-N7000 Android Development] jerryspring:
look at the twrp output. It says failed to flash.......zip.zip.

And I'm not arguing nor is this off topic. The dude's twrp error out put says failed to flash repartition.....zip.zip. I know what I am talking about! Look at his pics and mine!

---------- Post added at 07:23 AM ---------- Previous post was at 07:21 AM ----------

Don't flash zips that have zip named twice in the file! Duh! I bet if he renamed the file with only one "zip" in the file name, it will successfully flash!
[Galaxy Note GT-N7000 Android Development] D@rekills4:
I tried removing the extra .zip and received the same error.

If there was an error due to the extra .zip, I certainly would have not received an error regarding reading the partition table.

EDIT:

And if I did bonk the phone using that partition file, I can always flash via the '.pit' file via Odin and repartition back it's stock state.
[Galaxy Note GT-N7000 Android Development] jerryspring:
I said lucky you didn't...I have flashed less worse and borked mine. Why is the "zip" name twice on that file anyways?

---------- Post added at 03:25 PM ---------- Previous post was at 03:23 PM ----------

I would delete that file and download it again. Or, try the 6gb partition guide, that worked flawless. I tried the other repartitioning, and only the 6 gb worked.

---------- Post added at 03:28 PM ---------- Previous post was at 03:25 PM ----------

I did this one while on Omni rom

https://androidfilehost.com/?fid=962187416754461654
[Galaxy Note GT-N7000 Android Development] D@rekills4:
I have file name extensions disabled in Windows. So when I renamed the file, I added the extra '.zip', not knowing that the file already had a '.zip' extension.

I don't need to repartition because I never partitioned in the first place when flashing LineageOS 16.0, because I already had the required partition sizes for this ROM. I repartitioned the device to my needs around 2 or 3 years ago (with an unnecessary 3GB system for some reason).
[Galaxy Note GT-N7000 Android Development] jerryspring:
What file did you use to repartition then?
[Galaxy Note GT-N7000 Android Development] protheusDK:
Will this rom work for shv-e160k?
[Galaxy Note GT-N7000 Android Development] lee.wp14:
Sorry to inform that it will not work and please do not attempt to follow any of the procedures.

Korean N7000 is powered by a Snapdragon processor whereas the international N7000 is powered by an Exynos processor.

For those N7000 shipping with a Snapdragon processor, you may refer to the AT&T N7000 forum:

https://xdaforums.com/galaxy-note-att

Hope this helps!
[Galaxy Note GT-N7000 Android Development] DualJoe:
Any specific reason why you don't update since 05/2019? There were several security updates by Google since then.
[Galaxy Note GT-N7000 Android Development] WaleedTech:
One question. i'm running Android 8.1(https://xdaforums.com/galaxy-note/development/rom-nightowl-alpha1-t3770815). So what is the procedure for me to upgrade to this one? Am using this ancient device as a movie streamer haha. Also, not sure if it's an exynos or SD variant, the board is an smdk4210.
[Galaxy Note GT-N7000 Android Development] lee.wp14:
I started my college studies, and I can't really spare time for rom development. It will be halted until I have my semester break, which hopefully will give me plenty of time to continue.

There's quite a lot happened over s2 forum since then, including pre-patched magisk kernel which I attempted to do quite sometime before. It's getting more and more interesting. Thanks to rinando, else this rom won't exists too.

EDIT: regarding to your question earlier, it is certain that pie could be too much for such an old device to handle. There are both pros and cons to run pie on n7000. Depends on your usage of n7000, it could be more than enough or of the opposite. Take my n7000 for example, it solely act as my bedside alarm clock, thus running pie on it turns out to be still more than enough to cater my needs. Hope this clarifies.

I also take some opportunity to tinker around with the cpu governor and it turns out to be quite promising. Or perhaps, we might need a more aggressive cpu governor as per what happened with the galaxy s advance running oreo.
[Galaxy Note GT-N7000 Android Development] DualJoe:
The reason why i asked about performance issues is that bauners last beta 15.1 rom had severe issues (intermittent battery drain, cpu leaks, low performance..) and development stopped (previous roms are ok). Your rom would be the first again to run properly (if it does..). I'm still in range of this device and probably will update on the next release.
[Galaxy Note GT-N7000 Android Development] bigal-sa:
I see you call for TWRP.

LOS 14.1 ROM used PhilZ-cwm6-XXLT6-XSA5.06.1 for recovery. Will this work or must I install the TWRP you mention?
[Galaxy Note GT-N7000 Android Development] lex7-n7000:
First, thank you very much for this.

Unfortunately, GPS doesn't work.

Any Idea what I can do?
[Galaxy Note GT-N7000 Android Development] lee.wp14:
I've fixed the GPS on latest build 20190522 so it should work :confused:

Can you get a screenie of your N7000 running GPSTest? Possibly let it under a clear view of sky for around 5 minutes, should be sufficient.
[Galaxy Note GT-N7000 Android Development] lex7-n7000:
https://ibb.co/V9jmLrX
[Galaxy Note GT-N7000 Android Development] lee.wp14:
can you verify if this file exists in the root directory (/) with the exact contents?

https://github.com/leewp14/android_device_samsung_n7000/blob/lineage-16.0/rootdir/init.target.rc
[Galaxy Note GT-N7000 Android Development] lex7-n7000:
There isn't any file like "init.target.rc" :confused:
[Galaxy Note GT-N7000 Android Development] lee.wp14:
It should be there, are you on build 20190522? The older build does not have gps functionality.
[Galaxy Note GT-N7000 Android Development] lex7-n7000:
I double check it.

The File on my SD-card is " lineage-16.0-20190522-UNOFFICIAL-n7000-noassert.zip"

Buildnummer:

lineage_n7000-userdebug 9 PQ3A.190505.022eng.leewp1.20190522.095409 test-keys

Is it possible to add this file "init.target.rc"?
[Galaxy Note GT-N7000 Android Development] lee.wp14:
My apologies for replying late.

The file init.target.rc is stored inside the ramdisk, thus the only way to add the file is modifying the kernel.

However, it might be a mistake on my side, maybe the GPS implementation commit does not take changes on the last built. There's quite some GPS related changes on the source side and I doubt if these changes are there in the last build. You can check if these 5 files exists on your side:

https://github.com/leewp14/android_...448346ddcb12c604f970e031e820f8fd/n7000.mk#L42

*if these files exists, possibly I'm able to assist you by creating a init.d script.

Anyway, I'm running a private build which definitely has GPS functionality - those required files exists and GPS is tested ok. So hopefully for the next build will be having a working GPS. Sorry for the inconvenience, should you need GPS functionality, you might want to revert back to other ROMs instead for the time being.
[Galaxy Note GT-N7000 Android Development] lex7-n7000:
No problem. You don't have to apologize. ;)

Yes, all these files are on my device.

So if you can help me, I would be very grateful.
[Galaxy Note GT-N7000 Android Development] FaKK:
thank you very much for the effort!

managed to flash my old note, but welcome app is constantly not responding, i guess i have some hadrware issues due to its age.
[Galaxy Note GT-N7000 Android Development] lee.wp14:
As per attached, copy the file into /system/etc/init.d (preferably done through TWRP or FX File Manager app to avoid permission problems). Perform a reboot and try the GPS.

Let me know if it works!
[Galaxy Note GT-N7000 Android Development] Tasha T:
Hi

Thank you for bringing Android Pie to the Note 1.

I installed your rom about two months ago and everything worked well.

I made a full backup via TWRP at that time - two months ago.

I decided to wipe my device today, and then attempted to restore from the TWRP backup I had saved.

Unfortunately I am unable to restore my device as i am faced with the following error:

"extractTarFork() process ended with ERROR : 255

Is there anything I can do to solve the above problem and restore my backup ?

Thank you
[Galaxy Note GT-N7000 Android Development] lee.wp14:
Can you reproduce the error and then attach a recovery log?
[Galaxy Note GT-N7000 Android Development] Tasha T:
Attached are 2 recovery logs for 2 different error messages when I try to restore from a TWRP backup.

Thank you
[Galaxy Note GT-N7000 Android Development] lee.wp14:
It is an extraction failure. It seems to be a common issue for older TWRP releases, but it could be other non-TWRP build issues.

You might want to flash the particular system manually and restore only the data partition. My best suggestion is to refrain from restoring the backup unless it is important for you.

Anyway, what's the system of the backup? Is it a backup made before repartitioning in preparation for los16?
[Galaxy Note GT-N7000 Android Development] Tasha T:
Hi. Thank you for having a look at the recovery logs.

The operating system of the backup is Lineage OS 16. I flashed your Lineage 16 rom two months ago and installed all my apps etc., and made a backup thereafter. This backup is important to me as it contains all my apps and corresponding/related info of my device running Lineage OS 16.

I have flashed the system manually as per your suggestion, and then tried to restore the data partition only, but it resulted in the same error, namely:

extractTarFork() process ended with ERROR : 255

I currently have this version of TWRP recovery installed: TWRP-3.1.0-EMU-MIGRATION-M-20170318-noassert.zip

Would flashing another version of TWRP help ?

Any advice on which version of TWRP I could flash which will allow me to restore my saved backup ?

Thank you
[Galaxy Note GT-N7000 Android Development] lex7-n7000:
Sorry for my bad Android/Linux knowledge.

I have no dir /system/etc/init.d

Do I have to create it?
[Galaxy Note GT-N7000 Android Development] JarlPenguin:
Could someone mirror the 3.1.0 IsoRec recovery (I can't download it from XDA for some reason)

Edit: Never mind, I downloaded it using the PC
[Galaxy Note GT-N7000 Android Development] JarlPenguin:
Installed along with OpenGApps Pico and LineageSU, works fine for the most part

Some bugs I noticed:

Sometimes after the screen turns off either 1) the device freezes into a black screen when attempting to turn it back on and a few seconds later acts as if you had just rebooted the device, or 2) you are stuck on the lock screen till you reboot (swiping up does nothing except stay stuck in the swiped up position).

There is some input lag which causes touches to sometimes not be detected and causes some games to be nearly impossible to play (e.g. Geometry Dash), this probably can't be fixed

It's mostly the "soft reboots" that annoy me the most. While I was writing this post that same thing happened, causing my progress to be lost
[Galaxy Note GT-N7000 Android Development] lee.wp14:
You may try the galaxys2 los16's twrp 3.3.1 from rinando.

Actually, there are some unofficial workarounds on the internet, you can look it up. However I can't be sure if the workaround works well.

It's ok, everyone learns from nothing to something :)

The init.d folder should exists, so does the init.target.rc. i further checked my sources and my n7000 and found nothing wrong. Are you opening it in twrp or in a root file manager app?

I can't reproduce the reboot problems. Which build number you are using? Since it is soft reboot, you may attach logs from /proc/kmsg after soft reboot.
[Galaxy Note GT-N7000 Android Development] lex7-n7000:
Ok I forget to mount /system but twrp let me copy the file, anyway.

It should now at the right place but gps is still not working.

How can I proof that your script is executed?
[Galaxy Note GT-N7000 Android Development] lee.wp14:
You will need to mount /system first otherwise the file won't persists after reboot.

To proof if it is executed, find for the traces of the script's filename in logcat with logcat -d -b all. We are using selinux permissive so selinux will warn about init.d scripts.

or you can add a line at the end of script file:

touch /sdcard/test

and afterwards check if the file exists.

Or you might want to wait for my next release, should be ready in a few days if possible (I'm not sure, I will be having driving test in a few days). I just tested the GPS just now :D

*my n7000 has a relatively weak GPS :3 it took decades to get a fix :laugh:

EDIT: as long as GPSTest shows at least one satellite, then the gps daemon is running :)
[Galaxy Note GT-N7000 Android Development] JarlPenguin:
I was using the May 22nd build. Unfortunately I can't get any logs anymore because my n7000 is stuck in an endless bootloop on the boot logo, and attempting to boot into recovery causes a crash to the boot logo as well. What doesn't help is that my microUSB port is broken
[Galaxy Note GT-N7000 Android Development] lee.wp14:
You shouldn't have done any flashing at all while your USB port is broken.

It is hard to determine the cause of issue without any logs, it could be a software or hardware issue.

Furthermore, you stated that your device is semi-faulty (usb broken), it makes things more complicated.
[Galaxy Note GT-N7000 Android Development] lex7-n7000:
The test file is created, but GPS still not work.

I will wait for your next release :)
[Galaxy Note GT-N7000 Android Development] JarlPenguin:
To be honest, I don't mind that it is broken for now, since I do not use it as my daily driver

I'm thinking it's either the kernel partition is corrupted or some of the system files are corrupted. I managed to force a connection and it appears that the bootloader charging animation appears, not the LineageOS one. If I can manage to connect the phone to the PC, I'll try reflashing the recovery and going on from there.

Also I've tested Bluetooth Audio, it works fine.
[Galaxy Note GT-N7000 Android Development] lee.wp14:
Sure, do keep me updated if you don't mind :good:

My house has several bad n7000 usb boards :laugh: that's why I'm concerned about the faulty usb. I see you are a dev too, i guess I don't have to worry :)
[Galaxy Note GT-N7000 Android Development] JarlPenguin:
Right, I see.

I managed to get heimdall to detect it, and downloaded the PIT file: https://del.dog/upatikezoy

Now I have two questions: is /dev/block/mmcblk0p5 the BOOT or KERNEL partition (and if it is the BOOT partition what should I flash to the KERNEL partition & vice versa)? and is the RECOVERY partition used to store the IsoRec TWRP recovery?

Thanks for helping me out :)
[Galaxy Note GT-N7000 Android Development] lee.wp14:
how do I differentiate boot/kernel? :D I also don't know, when I use heimdall I just identify by the partition ID. The partition id is +1 of the mmcblk0px value.

My understanding is that a packed boot image (which includes the zImage and a inbuilt recovery) goes to mmcblk0p5, if I'm not mistaken it should be identified as partition id 6 on heimdall.

yes isorec goes to the recovery partition.
[Galaxy Note GT-N7000 Android Development] asusgarb:
Hi. I've already asked it, but my previous post has misteriously disappeared.

Now I'm using NightOwl 14.1 on my Note 1. I use it almost only as GPS navigator with Google Maps or Sigyc.

14.1 is low and a bit laggy. With this rom can I increase my Note's performances? Will it be even a bit snappier?

Sorry for not trying myself, but I use it almost everyday in car, so before changing room I would like to hear some opinion of some users.

Thank you very much, I appreciate if you want to help me.
[Galaxy Note GT-N7000 Android Development] lee.wp14:
Release 20191009

CHANGELOG

20191009

- kernel: panel brightness optimization from i9300

- kernel: adjust unified memory allocation size

- kernel: disable logging

- kernel: disable pegasusq core lock

- kernel: switch to ZEN I/O scheduler

- kernel: fix tuning table for Q1 (credits to rINanDO)

- kernel: misc source updates from rINanDO, ChronoMonochrome, ComicoTeam

- galaxys2-common: remove SamsungDoze

- galaxys2-common: use low-end video codecs (credits to ChronoMonochrome)

- galaxys2-common: make sure burn-in protection is enabled

- galaxys2-common: wifi hotspot channel 1-11 instead of 1,6,11 only

- galaxys2-common: platform specific gcc optimization flags

- galaxys2-common: lower haptic feedback intensity

- galaxys2-common: dual-speaker output implementation (back speaker + earpice speaker)

- galaxys2-common: fix RIL PIN unlock (credits to rINanDO)

- galaxys2-common: misc source updates from rINanDO

- n7000: increase minimum adjustable brightness threshold

- n7000: fake vendor security patch level

- n7000: conditionally reset max17041 fuel gauge on boot

- hardware/samsung: added missing OUI mapping [SEMCO - 50:cc:f8] (credits to J..J)

- general: upstream source updates, security patch 2019-09-05

Installation Notes:

For this build, you must update your kernel and recovery beforehand! This is due to some changes in fstab.

1. Go to the Google Drive download link in second post.

2. In n7000 > misc > kernel folder, download boot-222aec6.img

3. In n7000 > misc > recovery folder, download i9100-LOS-16.0-Emulated-Storage-TWRP-3.3.1-1.img by rINanDO

4. Put these files in your n7000. Go to TWRP > Install > Install Image. Choose the boot-222aec6.img and flash to Boot.

5. Do not reboot yet. Go back and choose i9100-LOS-16.0-Emulated-Storage-TWRP-3.3.1-1.img and flash to Recovery.

6. Reboot Recovery. Your n7000 should now reboot into TWRP 3.3.1-1. Proceed to flash the build.

Notes:

- Due to source changes in this build's kernel, the screen is unable to turn off in TWRP, kindly take note!

- I've implemented dual-speaker output, now in speaker mode, the sound output will be using both back speaker and the front earpice speaker.

- GPS is tested working and is able to get a fix. Kindly ensure your GPS antenna/connection is in good condition if you are facing GPS issues. First fix might take longer than usual.

- You are able to reset the MAX17041 fuel gauge (battery meter) by editing ro.max17041.fg_reset_soc=0 to =1 in build.prop, then reboot. Remember to set back to =0 when not needed.

- GAPPS users, if you get the Android Setup notification, just disable Android Setup in Settings > Apps and Notifications.

- This should be the last build for the time being :3 Thanks for using this ROM!
[Galaxy Note GT-N7000 Android Development] asusgarb:
Thank you very much for this last build. I'm curious now to try it.

Just a question. On Lineage 14.1 I installed nano gapps, because I was trying to use Google assistant but when I tried I received and error and I couldn't use vocal commands.

Was it a ROM related problem or the device is too old to make it working?

Because if it's a device problem I'll use Pico gapps instead
[Galaxy Note GT-N7000 Android Development] lee.wp14:
I have no problems with google assistant voice commands on n7000 so far when using los14. However as a heads up my build won't support google assistant because it is missing some necessary configurations.
[Galaxy Note GT-N7000 Android Development] Digger_m:
I have managed to get los16.0 to boot up all good then I flashed gapps

open_gapps-arm-9.0-nano-20191010.zip

When I boot to system I get the boot logo for 10 minutes of so then it reboots in to recovery.

Is this the correct version of gapps

If it is anyone have any ideas what I did wrong.

I replaced the charging board on my note to install this hoping I've made a simple mistake.
[Galaxy Note GT-N7000 Android Development] lee.wp14:
try to install again see? flash the rom zip and the gapps together then only boot it.

If cannot you try to use pico gapps see. So far I only tested pico gapps.
[Galaxy Note GT-N7000 Android Development] Digger_m:
I have re-flashed Los 16 and Pico gapps. It flashed with no errors. It boots to logo for about 10 minutes then then reboots to recovery. Could you put a link to your gapps .

My others thought is the partitioning isn't as it should be I did run the partitioning tool. I do remember a few ROMs back having to use Odin and pit files . I will look threw the files I've collected to refresh my memory. Thank you for your very prompt reply really hope we can figure this out .
[Galaxy Note GT-N7000 Android Development] lee.wp14:
Please try again a clean install without gapps. If it works then something is wrong with the gapps. I don't think there's something wrong with the repartition as long as you have followed the instructions in OP.

Where did you download your gapps? Did you get it from opengapps.org?

EDIT: seems like is gapps issue, users are complaining with opengapps 20191010 over the galaxy s2 forum. Try this gapps instead, which I am using:

https://sourceforge.net/projects/op...open_gapps-arm-9.0-pico-20191006.zip/download
[Galaxy Note GT-N7000 Android Development] Digger_m:
I have managed to get booted with the gapps you posted . Thank you of posting that link. I did find that it wouldn't boot with i9100-LOS-16.0-Emulated-Storage-TWRP-3.3.1-1 install

I re-flashed TWRP-3.1.0-EMU-MIGRATION-M-20170318-noassert.zip. to get it to boot with gapps.

All that I need is to figure out how to get rooted properly.