Attached are 2 recovery logs for 2 different error messages when I try to restore from a TWRP backup.
Thank you
Last edited:
Thank you
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?
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
Last edited:
Sorry for my bad Android/Linux knowledge.
I have no dir /system/etc/init.d
Do I have to create it?
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
Edit: Never mind, I downloaded it using the PC
Last edited:
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
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
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.
Ok I forget to mount /system but twrp let me copy the file, anyway.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?
It should now at the right place but gps is still not working.
How can I proof that your script is executed?
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
*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
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
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.
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.
Last edited:
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
Right, I see.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
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
how do I differentiate boot/kernel?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
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.
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.
Sent from my Samsung Galaxy Note 3 using XDA Labs
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.
Sent from my Samsung Galaxy Note 3 using XDA Labs
Release 20191009
CHANGELOG
20191009
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!
CHANGELOG
20191009
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!
Last edited:
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
Sent from my Samsung Galaxy Note 3 using XDA Labs
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
Sent from my Samsung Galaxy Note 3 using XDA Labs
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.
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