hmm i just understood ur situauion. I hv i9220 #4 in my phone. If your phone boots with GT-I9220 logo, then you may try that. If your phone boots with GT-N7000, you should be ok to proceed with custom flashing.Thanks you both for your answer @lee.wp14 and @bauner. For the motherboard this is exactly the reflection I made, the first one (installed in the phone) had a mark "i9220 #4", and on the new one, it is marked "i9220 #2". From the tests I've done with the stock firmwares, it seems like it's not possible to flash a N7000 rom with Odin without a fail (I try with and without the .pit repartition file) from what I understood it would come from the bootloader. Do you think it is necessary to flash the bootloader of the GT-N7000 (like on this tutorial* https://forum.xda-developers.com/showthread.php?t=1660012) and after install this custom rom ?
[ROM][LineageOS14.1][Nougat][Android 7.1.2] NightOwl 20180824
- Thread starter bauner
- Start date
Yeahh ! It work perfectly :laugh: .
After multiple attempts with Odin, I confirm that it is the bootloader that prevents the repartition and the installation of firmwares other than those for China. In order to override this behavior I thought to install the bootloader of the classic version of the Galaxy Note 1 (the GT-N7000 version) as in this tutorial. Unfortunately, again, I could not flash the new bootloader without having an error message with Odin. It seems that this mechanism is also present in the Galaxy SII. I finally installed the custom rom as if my phone was a GT-N7000 (just for try :silly but keeping the bootloader of the GT-I9220. I just replace the first line of the file /META-INF/com/google/android/updater-script (like @bauner told me ) inside "Nightowl-cm13-20161012-n7000-kernel_only.zip" and "Nightowl-lineage14.1-20171126-n7000" by :
I have not noticed any problem for the moment, so good job :good: !
PS: Would it be possible to modify the first line of the updater-script to allow the installation of the next update (if there is one) on the GT-I9220 without modifying the package?
After multiple attempts with Odin, I confirm that it is the bootloader that prevents the repartition and the installation of firmwares other than those for China. In order to override this behavior I thought to install the bootloader of the classic version of the Galaxy Note 1 (the GT-N7000 version) as in this tutorial. Unfortunately, again, I could not flash the new bootloader without having an error message with Odin. It seems that this mechanism is also present in the Galaxy SII. I finally installed the custom rom as if my phone was a GT-N7000 (just for try :silly
but keeping the bootloader of the GT-I9220. I just replace the first line of the file /META-INF/com/google/android/updater-script (like @bauner told me ) inside "Nightowl-cm13-20161012-n7000-kernel_only.zip" and "Nightowl-lineage14.1-20171126-n7000" by :
HTML:
assert(getprop("ro.product.device") == "galaxynote" || getprop("ro.build.product") == "galaxynote" || getprop("ro.product.device") == "n7000" || getprop("ro.build.product") == "n7000" || getprop("ro.product.device") == "N7000" || getprop("ro.build.product") == "N7000" || getprop("ro.product.device") == "GT-N7000" || getprop("ro.build.product") == "GT-N7000" || getprop("ro.build.product") == "GT-I9220" || getprop("ro.product.device") == "GT-I9220" || abort("This package is for device: galaxynote,n7000,N7000,GT-N7000,GT-I9220; this device is " + getprop("ro.product.device") + "."););PS: Would it be possible to modify the first line of the updater-script to allow the installation of the next update (if there is one
) on the GT-I9220 without modifying the package?Attachments
updater-script is only present in flashable zips, so only choice is to modify the package or edit /system/build.prop. Or if you wan easy u can just remove the whole device checking line which i always do, but need to be very sure that the package is the correct zip.Yeahh ! It work perfectly :laugh: .
After multiple attempts with Odin, I confirm that it is the bootloader that prevents the repartition and the installation of firmwares other than those for China. In order to override this behavior I thought to install the bootloader of the classic version of the Galaxy Note 1 (the GT-N7000 version) as in this tutorial. Unfortunately, again, I could not flash the new bootloader without having an error message with Odin. It seems that this mechanism is also present in the Galaxy SII. I finally installed the custom rom as if my phone was a GT-N7000 (just for try :silly
I have not noticed any problem for the moment, so good job :good: !HTML:assert(getprop("ro.product.device") == "galaxynote" || getprop("ro.build.product") == "galaxynote" || getprop("ro.product.device") == "n7000" || getprop("ro.build.product") == "n7000" || getprop("ro.product.device") == "N7000" || getprop("ro.build.product") == "N7000" || getprop("ro.product.device") == "GT-N7000" || getprop("ro.build.product") == "GT-N7000" || getprop("ro.build.product") == "GT-I9220" || getprop("ro.product.device") == "GT-I9220" || abort("This package is for device: galaxynote,n7000,N7000,GT-N7000,GT-I9220; this device is " + getprop("ro.product.device") + "."););
PS: Would it be possible to modify the first line of the updater-script to allow the installation of the next update (if there is one
I have the same china motherboard i9220 and it works fine!!!Hello,
Thanks a lot for your rom and the work of everyone to make this happens, it's fantastic to see a phone as supported by the community
Unfortunately, the motherboard of my Galaxy Note suddenly decided to die :crying
Dead note.
Hi, everyone!
I was using this rom without problems, until the last update. I notice that my sdcard was detected as stranger letters, like "M^zR4~7?k#", and the size was wrong. So, since I understand a little bit of unix, I tried to change the "fstab" file, and after save it, my phone was dead. No sign of boot, recovery, or download mode, no detection by usb cable, no vibration... nothing! Battery is fine, since I have charged on a external charger. Anyone can help me, please? There's another way to make this phone wake up without have to take it to the Samsung support and pay a lot for the fix?
(sorry for my english)
Hi, everyone!
I was using this rom without problems, until the last update. I notice that my sdcard was detected as stranger letters, like "M^zR4~7?k#", and the size was wrong. So, since I understand a little bit of unix, I tried to change the "fstab" file, and after save it, my phone was dead. No sign of boot, recovery, or download mode, no detection by usb cable, no vibration... nothing! Battery is fine, since I have charged on a external charger. Anyone can help me, please? There's another way to make this phone wake up without have to take it to the Samsung support and pay a lot for the fix?
(sorry for my english)
I will add it in the next updateYeahh ! It work perfectly :laugh: .
After multiple attempts with Odin, I confirm that it is the bootloader that prevents the repartition and the installation of firmwares other than those for China. In order to override this behavior I thought to install the bootloader of the classic version of the Galaxy Note 1 (the GT-N7000 version) as in this tutorial. Unfortunately, again, I could not flash the new bootloader without having an error message with Odin. It seems that this mechanism is also present in the Galaxy SII. I finally installed the custom rom as if my phone was a GT-N7000 (just for try :silly
I have not noticed any problem for the moment, so good job :good: !HTML:assert(getprop("ro.product.device") == "galaxynote" || getprop("ro.build.product") == "galaxynote" || getprop("ro.product.device") == "n7000" || getprop("ro.build.product") == "n7000" || getprop("ro.product.device") == "N7000" || getprop("ro.build.product") == "N7000" || getprop("ro.product.device") == "GT-N7000" || getprop("ro.build.product") == "GT-N7000" || getprop("ro.build.product") == "GT-I9220" || getprop("ro.product.device") == "GT-I9220" || abort("This package is for device: galaxynote,n7000,N7000,GT-N7000,GT-I9220; this device is " + getprop("ro.product.device") + "."););
PS: Would it be possible to modify the first line of the updater-script to allow the installation of the next update (if there is one
Accounts gone
Hi there,
got a slightly annoying problem with all accounts on my Note 1 with NightOwl 20171126. I'm using NightOwl 12->14 for quite a while now and very happy to still use my Note perfectly after all these years. Thanks for the hard work!!!
I got a problem with all of my accounts (Google, Dropbox, Mailserver....), they are all gone. If I try to re-login Google, the phone doesn't connect ans Playstore etc don't work, but the Google-account-login works well on the PC for example.
Any tips before I do a complete re-install?
Hi there,
got a slightly annoying problem with all accounts on my Note 1 with NightOwl 20171126. I'm using NightOwl 12->14 for quite a while now and very happy to still use my Note perfectly after all these years. Thanks for the hard work!!!
I got a problem with all of my accounts (Google, Dropbox, Mailserver....), they are all gone. If I try to re-login Google, the phone doesn't connect ans Playstore etc don't work, but the Google-account-login works well on the PC for example.
Any tips before I do a complete re-install?
You could try wiping cache and dalvik in recovery. This may help. You can also try to dirty flash the rom. You will loose nothing by trying...
Good luck!
Thanks, tried this already, didn't change anything
Phone runs well otherwise
Dirty flashing is installing same ROM again?
Or is it ok to reinstall the GApps again .. same Package?
Last edited:
Just flashing the Rom, nothing else.Thanks, tried this already, didn't change anything
Phone runs well otherwise
Dirty flashing is installing same ROM again?
Or is it ok to reinstall the GApps again .. same Package?
Here is a log file from sudden hard reboot, when phone was idle.
Also lost all accounts, google, linkedin etc.
Also lost all accounts, google, linkedin etc.
The application ReadEra does not show the contents of SD-cards
"overview of the contents of the folder is prohibited by the system"
What can I do?
"overview of the contents of the folder is prohibited by the system"
What can I do?
Hi @bauner
what do you think about speed up system by adding:
write /sys/block/mmcblk0/queue/read_ahead_kb 2048
to the init.smdk4210.rc ?
It can significantly boost system start but not only.
Br, n6210
what do you think about speed up system by adding:
write /sys/block/mmcblk0/queue/read_ahead_kb 2048
to the init.smdk4210.rc ?
It can significantly boost system start but not only.
Br, n6210
Another hard reboot. Phone was updating apps and the rebooted.
Log is attached below
Log is attached below
Can anyone help me with this file? PhilZ-cwm6-XXLT5-OXX-5.03.0.tar.md5
Need to download to unlock/root my device.
Need to download to unlock/root my device.
Both of your logs show a forced reboot because of filesystem errors on the /data partition.
You can try to fix it with a filesystem check in twrp recovery
Some apps will have problems with the legacy partition lyout on the n7000.
But I will see if I can do anything for this app in the next version(s).
But it can take some time. Currently I try to fix a stability problem in my next lineage 13 rom...
I will do some tests and maybe set it to a higher value on boot time.
Set it to a high value in general for all partitions is not the best option for all use cases.
Here you can find some informations about it
https://forum.xda-developers.com/showthread.php?t=1032317
https://rapidgator.net/file/fd15848...30-galaxy-note-1gt-n7000/?page=3&tab=comments
Did you try to format the sdcard as internal (adoptable) storage? This is known to cause the strange name.Hi, everyone!
I was using this rom without problems, until the last update. I notice that my sdcard was detected as stranger letters, like "M^zR4~7?k#", and the size was wrong. So, since I understand a little bit of unix, I tried to change the "fstab" file, and after save it, my phone was dead. No sign of boot, recovery, or download mode, no detection by usb cable, no vibration... nothing! Battery is fine, since I have charged on a external charger. Anyone can help me, please? There's another way to make this phone wake up without have to take it to the Samsung support and pay a lot for the fix?
(sorry for my english)
The way to fix the sdcard name would be to format it in the recovery as vfat.
What exactly did you do? Because modifying the fstab file should not cause your problem because it is inside the ramdisk and you can't change it if you simply edit the file.
You can try if the following way will help.
remove battery
connect the device to your pc
hold the vol- button and insert the battery
When charging the phone, phone was shut down. Had to remove the battery befor it started again.
@bauner, log is attached below
@bauner, log is attached below
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone