• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

LineageOS 18.1 Android 11 for GT-N8000 GT-N8005 GT-N8010 GT-N8013 GT-N8020 Beta

Search This thread

html6405

Recognized Developer
Jan 15, 2016
1,573
1,430
So is it possible that the twrp is too large damaged the modem or bootloader ?
If the image is to large, you should have problems with flashing.
The bootloader would resist the file, if you were flashing with dd, it should also check the file size.

But, I hope your modified TWRP uses the correct fstab, otherwise you could modify the wrong partition.
 

aliveday

Member
May 5, 2021
32
4
If the image is to large, you should have problems with flashing.
The bootloader would resist the file, if you were flashing with dd, it should also check the file size.

But, I hope your modified TWRP uses the correct fstab, otherwise you could modify the wrong partition.
In fact, I may have modified twrp very very large before, i added ttf files and pictures to it. I don’t know why I didn’t report an error when I flashed in with Odin, my sim card socket was broken before, so I have not found this problem until I decided to use sim a few days ago.
I know that my technology is very low, so I dare not modify fstab and the like, It still caused trouble. lol~
 

arbabatz

New member
Mar 22, 2018
4
3
I have a problem and I don't know if it is general, I cannot download from the browsers, and save it in the internal memory ... some way to solve it
 

Don Carnage

Senior Member
I found out the reason, because of the tool carliv_image_kitchen, I used this tool to beautify and translate twrp before. A few minutes ago i just tried to use this tool to unpack twrp and repack it without changing any settings, i found that the volume of the repackaged twrp became larger, and the Baseband was lost after brushing it into the tablet.
So is it possible that the twrp is too large damaged the modem or bootloader ?
Sure enough, difficulties make people progress, I really learned a lot of new knowledge and technology these days.
Thanks.

The recovery partition is right in front of the modem partition, so if you have an image that is bigger than 8MB you will write into the modem partition and corrupt it. I've had this happen to me with the boot partition which corrupted recovery and the device went into a boot loop because none of the two could be booted. I had to use download mode to fix it.
 

Flanagan331

Member
Oct 13, 2021
8
0
The recovery partition is right in front of the modem partition, so if you have an image that is bigger than 8MB you will write into the modem partition and corrupt it. I've had this happen to me with the boot partition which corrupted recovery and the device went into a boot loop because none of the two could be booted. I had to use download mode to fix it.
I don't no if my problem is the same. But i can't use Wifi.
It's possible to flash a stock 4.4.2 modem image with odin after flashed the custom rom onto device?
In order to fix the corrupt image?
I see a MODEM image and its size 12mb ...(>8)

Sorry for my ignorance <3
 

Don Carnage

Senior Member
I don't no if my problem is the same. But i can't use Wifi.
It's possible to flash a stock 4.4.2 modem image with odin after flashed the custom rom onto device?
In order to fix the corrupt image?
I see a MODEM image and its size 12mb ...(>8)

Sorry for my ignorance <3
The modem (radio) partition is 32MB, so this is fine, the image will fit.
 

aliveday

Member
May 5, 2021
32
4
The recovery partition is right in front of the modem partition, so if you have an image that is bigger than 8MB you will write into the modem partition and corrupt it. I've had this happen to me with the boot partition which corrupted recovery and the device went into a boot loop because none of the two could be booted. I had to use download mode to fix it.

This is really the case, lol, i have learned new knowledge, and i will not make such mistakes again.
 

utsc

Senior Member
Aug 20, 2011
121
9
Does anyone know if we still have the boot loop error associated with SD card or have it been resolved?
 

SlimsyT

New member
Oct 17, 2021
2
3
Thank you html6405! Took an old GT-N8013 that was unusable with the stock Samsung 4.1.2 OS due to it running out of SDRAM frequently, freezing up, and crashing. Installed LineageOS 18.1 flawlessly per your instructions, and now it's working great (WIFI, sound, video, camera, Bluetooth, haptics, ext SD card (FAT32), even the S-Pen all seem to work OK). No problems to report. Excellent work with keeping electronics out of the landfill and saving some cash. Enjoy a beer on me.
 

Alexfs

Senior Member
Oct 7, 2014
58
20
The recovery partition is right in front of the modem partition, so if you have an image that is bigger than 8MB you will write into the modem partition and corrupt it. I've had this happen to me with the boot partition which corrupted recovery and the device went into a boot loop because none of the two could be booted. I had to use download mode to fix it.
Good morning,
Don Carnage, I'm glad to see you're still interested in our tablet. Not to be rude, as I know you asked not to ask, but is there any hope that we still have an upgrade to kernel 5 or have you abandoned the project?
 

jhriverap

New member
Oct 21, 2021
3
2
Thank you html6405! Took an old GT-N8013 that was unusable with the stock Samsung 4.1.2 OS due to it running out of SDRAM frequently, freezing up, and crashing. Installed LineageOS 18.1 flawlessly per your instructions, and now it's working great (WIFI, sound, video, camera, Bluetooth, haptics, ext SD card (FAT32), even the S-Pen all seem to work OK). No problems to report. Excellent work with keeping electronics out of the landfill and saving some cash. Enjoy a beer on me.
Hi SlimsyT, newbie here. Can you please share the link to html6405's instructions? Thanks
 

html6405

Recognized Developer
Jan 15, 2016
1,573
1,430
Update 26.10.2021:
  • N8020: Fixed modem crash issue in Kernel, the connection still get's lost sometimes and you still have to reset the APN settings after every boot, I'm working on this...
 
Last edited:
  • Like
Reactions: themediapadguy

Top Liked Posts

  • 1
    Thx for your report, it's sometimes really hard to reproduce this bug, than I will give it another attempt.

    Magisk removed magisk hide and the safety net check, I'm still getting a pass with the SafetyNet Test app from the playstore.

    Great :).

    This seems like a frequent issue now. Hope we'll have some fix. Will this affect the display or hardware btw?

    Update: The following reproduced the issue for me it seems -

    Played JetAudio Plus and kept the device idle and display off while playing the music. Turned the display on by pressing the power key after 5 minutes.

    IMG_20211206_134228.jpg
  • 4
    Update 03.12.2021:
    • Fixed tethering
    • Fixed wifi mac adress in settings
    • Some tweaks
    • Fixed NetGuard support in Kernel
    • Disabled WPA3 in RRO overlay
    • Enabled default gesture navigation
    • Enabled 1704 MHz if you wan't to overclock
    • Enabled dex preopt
    • Would be nice if someone could report if the screen lightning bug is gone now
    2
    The reason they removed it is somewhat documented in the commit history here:
    1
    Thx for your report, it's sometimes really hard to reproduce this bug, than I will give it another attempt.

    Magisk removed magisk hide and the safety net check, I'm still getting a pass with the SafetyNet Test app from the playstore.

    Great :).

    This seems like a frequent issue now. Hope we'll have some fix. Will this affect the display or hardware btw?

    Update: The following reproduced the issue for me it seems -

    Played JetAudio Plus and kept the device idle and display off while playing the music. Turned the display on by pressing the power key after 5 minutes.

    IMG_20211206_134228.jpg
    1
    Thats the thing, why I didn't got this problem.
    You simply could download an older version and upgrade afterwards,
    or just wait until I've fixed the setup wizard.

    LineageOS overworked this, there are many commits, one of them broke the skip button, I will fix this and push a new update...
    Thank you! I will waiting for your next updated! Thank for keep make this old device update!
  • 61
    Code:
    /*
    * Your warranty is now void.
    *
    * I am not responsible for bricked devices, dead SD cards,
    * thermonuclear war, or you getting fired because the alarm app failed. Please
    * do some research if you have any concerns about features included in this ROM
    * before flashing it! YOU are choosing to make these modifications, and if
    * you point the finger at me for messing up your device, I will laugh at you.
    *
    */


    Hi,

    here you can find my preview build version of LineageOS 18.1 for our Samsung Galaxy Note 10.1 devices.
    At first I want to thank @forkbomb444, @rINanDO, @ChronoMonochrome for all your work which helped me a lot to bring this up.

    This is a early BETA build, so don't install it if you want a completley stable rom and don't report my already listet bugs!

    I'm working nearly every day on our N80xx devices, because LOS18 runs much smoother than LOS17.1, I will continue here.

    When you have BitGapps installed, you have to reflash them after every update!

    Here you can see how far everything is working for now.

    N8000, N8010, N8013, N8020:
    • Boot
    • Audio
    • Bluetooth
    • Graphics
    • Cameras
    • Sensors
    • Wifi
    • GPS
    • USB
    • Video playback (HW/SW)
    • Tethering via USB, WIFI and Bluetooth
    • consumerir transmitter
    • Stylus with gestures and hovering icon
    • sec keyboard dock
    • RIL on N8000 (mobile connection)
    • much more...
    • Video recording with both cameras
    • Power off charging animation fixed
    • GPS
    • LiveDisplay
    • Magisk Root fixed
    • OTA Updates
    • Screen Cast, Chromecast did work, Samsung TV not
    • Main camera sometimes can't take a picture (reopen app or lower resolution)
    • Random reboots
    • Maybe more
    • N8020: RIL works 90%
    • Screen lightning bug
    • SD-Card can't be formatted as internal storage, this will cause a bootloop
    You could use a gps.conf from https://app.box.com/s/w57s1v1n3hie7l5lk28i for your location and replace /system/etc/gps.conf.
    Or you try GPS Server Optimizer app for a faster 3D fix.
    For both methods you need root rights.
    If you are going to use Gapps,
    here you can download them:
    Open Gapps test versions
    For the others, you can use microG in future.

    If you plan to use a sim card in your device, I would recommend to disable the pin code before with another device.
    In some cases the sim card becomes unusable while typing in the code.

    Do you like my work?
    Than you can simply hit the thanks button and consider to spend me a coffee or a beer,
    I'm doing this in my free time and it also costs a lot of money to buy hardware.

    donate

    XDA:DevDB Information
    [ROM][11.x][N8000/N801x/N8020][BETA] LineageOS 18.1, ROM for the Samsung Galaxy Note 10.1

    Contributors

    html6405
    Source Code: https://github.com/html6405

    ROM OS Version: 11.x R
    ROM Kernel: Linux 3.x
    ROM Firmware Required: TWRP 3.4.0
    Based On: LineageOS
    Selinux: permissive, this only makes sense as soon the ROM is stable.

    Version Information
    Status:
    Beta

    Created 2020-12-21
    Last Updated 2021-12-03
    14
    This ROM is alpha, nobody can force me to bring any updates,
    I'm doing this in my freetime, so be thankful if you get something.

    I will proceed here as soon as I will have time, I didn't have LOS16.0 completed and I'm working hard to provide you a stable ROM.
    LOS 16.0 is our major version, on LOS18.1 is much more work todo and much more framework hackings to get LOS18.1 as good compatible as possible.

    I'm overtaking many things I make for LOS16.0 to 18.1, but this take's time.
    I hate it if I get stressed, so please be patent or do it by your own,
    this takes really much time, debugging, try things and so on.
    8
    Update 15.01.2020, N8000:
    • Fixed a problem with mobile data
    • Improved GPS, but it's still not perfect
    • Another stability fix
    Only via OTA.
    7
    New TWRP builds are up :).
    7
    Update 14.01.2021:
    • many stability fixes in kernel
    • many net back ports to improve kernel compatibility
    • improved performance
    • fixed audio and video recording
    • fixed samsung doze
    • Volume button wakeup crash fixed
    And again, don't forget to reflash BitGapps...