[ROM][weekly][Official] AICP 12.1 [P600][n1awifi][7.1.2]

[ollimi1]

Lol, your​ message just reminded me to pick ShevT's fix for the setup wizard fc, thanks
http://gerrit.aicp-rom.com/#/c/38045/

Yeah, call me "reminder"!
And I found the reason for the heavy gpu load while charging.
It's the tiny charging animation you can see when you enable batterybar in statusbar and enable the charging animation. I mean this small running dots towards the batterybar... seems to need lots of gpu power for some reason.
While this seems to be normal behavior the heavy load of sometimes 90-100% seems not normal for such a small animation!
And if deaktivated there is immediately no load anymore!

---------- Post added at 16:34 ---------- Previous post was at 16:22 ----------

The 5.18 version has been causing freezes after using Lecture Notes for 15 or so minutes, forcing a reboot and a page or so of lost notes. I'm on LL Bootloader and Prime AICP kernel. Switching back to 4.28 for now. Thanks again for all your hard work mosimchah. You're the MVP keeping this tablet alive!

It's a well known problem and @mosimchah is already working hard to find a fix. It's only a matter of time...:good:

 

[slimjimz81]

ok, I think I may have missed something or just doing it wrong. every time I do an update it gets stuck in a boot loop after flashing. any suggestions? and great ROM by the way

 

[mosimchah]

ok, I think I may have missed something or just doing it wrong. every time I do an update it gets stuck in a boot loop after flashing. any suggestions? and great ROM by the way

Wipe the system, cache, and dalvik cache, and then flash the ROM and beans gapps

 

[DeanoD]

Been tinkering with this new build for a day now. OTA update was a bust, sticks on AICP logo. Same result with a quick wipe and a manual install with Beans minigapps. Were there major changes since last build that would cause the looping? I'm still on the fence about flashing the Prime Kernel. And I've seen several mentions of ShevT's version of TWRP and I keep getting dead links. I'm gonna try full wipe flash to get this to work since everything else has run very well so far. Anybody got a link for ShevT's TWRP?

 

[ollimi1]

Been tinkering with this new build for a day now. OTA update was a bust, sticks on AICP logo. Same result with a quick wipe and a manual install with Beans minigapps. Were there major changes since last build that would cause the looping? I'm still on the fence about flashing the Prime Kernel. And I've seen several mentions of ShevT's version of TWRP and I keep getting dead links. I'm gonna try full wipe flash to get this to work since everything else has run very well so far. Anybody got a link for ShevT's TWRP?

Hi DeanoD.
Here you go, latest is 3.1.1.0:
https://forum.xda-developers.com/ga...p601-lineage-nougat-galaxy-note-10-1-t3546012

If the dl link is still dead, take download below. I've uploaded latest twrp for you.

Did you try to install latest update manually? Try it and wipe cache, dalvik and "system" then flash rom and gapps.

Where did you get the loops?
After booting, when the device starts to allow superuser rights for some apps or before it's fully booted? If it still loops try flashing latest magisk v12 on top, it's sometimes overwritten and gets lost.


@mosimchah
Can I still use the latest kk_bl.img(5-18-17) for latest 05/25 update?

 

[vinayburman]

Been tinkering with this new build for a day now. OTA update was a bust, sticks on AICP logo. Same result with a quick wipe and a manual install with Beans minigapps. Were there major changes since last build that would cause the looping? I'm still on the fence about flashing the Prime Kernel. And I've seen several mentions of ShevT's version of TWRP and I keep getting dead links. I'm gonna try full wipe flash to get this to work since everything else has run very well so far. Anybody got a link for ShevT's TWRP?

I had the same problem. Here is what I did, while stuck on logo I pressed and hold the power button as soon as tablet powered down, I pressed and held the volume up button also. Now I booted to twrp and cleaned dalvik and cache, rebooted to system and problem solved. Another thing I found is if you recharge your tablet powered down, the charging rate is much faster than recharging power on.

 

[Vaizen]

Just dirty flashed 5/25 build, no problems so far, feels a little tiny bit smoother.

Charging time seems normal to me, considering that Temasek's builds took 5h to charge, AICP is golden with 4h.

 

[mosimchah]

@mosimchah
Can I still use the latest kk_bl.img(5-18-17) for latest 05/25 update?

Yes, nothing changed kernel side

 

[DeanoD]

Where did you get the loops?
After booting, when the device starts to allow superuser rights for some apps or before it's fully booted? If it still loops try flashing latest magisk v12 on top, it's sometimes overwritten and gets lost.

I was getting the AICP logo onscreen, and there it sat. I downloaded the ROM again to make sure that there was no bad files, but when I tried to flash the Prime Kernel, everything yarped it back at me. Corrupt, files md5 errors, etc. So I'm back to checking my downloads all over again. Gonna try clean flash, not sure what to do with the Prime Kernel crapping out. ;-DeanoD

 

[haighpaul]

Where did you get the loops?
After booting, when the device starts to allow superuser rights for some apps or before it's fully booted? If it still loops try flashing latest magisk v12 on top, it's sometimes overwritten and gets lost.

I was getting the AICP logo onscreen, and there it sat. I downloaded the ROM again to make sure that there was no bad files, but when I tried to flash the Prime Kernel, everything yarped it back at me. Corrupt, files md5 errors, etc. So I'm back to checking my downloads all over again. Gonna try clean flash, not sure what to do with the Prime Kernel crapping out. ;-DeanoD

Yes, I was unable to get past the logo with OTA/dirty flash. Tablet hot quite hit while it was stuck too. In the end a clean flash worked and all is fine even if it took a lot of time setting up everything again.

 

[ollimi1]

Where did you get the loops?
After booting, when the device starts to allow superuser rights for some apps or before it's fully booted? If it still loops try flashing latest magisk v12 on top, it's sometimes overwritten and gets lost.

I was getting the AICP logo onscreen, and there it sat. I downloaded the ROM again to make sure that there was no bad files, but when I tried to flash the Prime Kernel, everything yarped it back at me. Corrupt, files md5 errors, etc. So I'm back to checking my downloads all over again. Gonna try clean flash, not sure what to do with the Prime Kernel crapping out. ;-DeanoD

You need Prime v7.4 for LL bootloader when you already installed the LL_bootloader.
I do not know when you downloaded it, but I know the kernels were exchanged for some reason. (Kk_bl_kernel was for ll_bl and vice versa)
Hitman has already corrected this, but perhaps you have still caught the swapped kernels?!
If you download everything again, it should fold with a clean installation! :fingers-crossed:

---------- Post added at 09:07 ---------- Previous post was at 09:03 ----------

Yes, I was unable to get past the logo with OTA/dirty flash. Tablet hot quite hit while it was stuck too. In the end a clean flash worked and all is fine even if it took a lot of time setting up everything again.

Hey haighpaul,
You can restore your data partition from previous backup after a clean flashing if you have one. But in front of it I would try to install latest OTA manually incl. system wipe, then flash rom and gapps again.
You can still make a clean flash if it does not work.

 

[haighpaul]

Hey haighpaul,
You can restore your data partition from previous backup after a clean flashing if you have one. But in front of it I would try to install latest OTA manually incl. system wipe, then flash rom and gapps again.
You can still make a clean flash if it does not work.

Thanks for the help. I did have a backup so I tried restoring just the data partition on top of a clean install. Unfortunately TWRP gave an error 'extractTarFork() process ended with error 255 during the restore. This was the same backup I used to recover from the point when dirty flashing got stuck at the AICP logo so it worked up until the new system ROM was successfully clean flashed. Very strange but looks like data partition is the issue. I'm on LL bootloader.

 

[ollimi1]

Thanks for the help. I did have a backup so I tried restoring just the data partition on top of a clean install. Unfortunately TWRP gave an error 'extractTarFork() process ended with error 255 during the restore. This was the same backup I used to recover from the point when dirty flashing got stuck at the AICP logo so it worked up until the new system ROM was successfully clean flashed. Very strange but looks like data partition is the issue. I'm on LL bootloader.

Maybe try a full wipe incl. data media next time you got these issues. Maybe some very old leftovers or the likes..
I've got a very similar issues when I went from Temasek's 5.1 to 6.0 and a full wipe solved it.

 

[DeanoD]

I'm getting similar results with latest build. Heck, even TWRP itself is getting in on the total crap party. When flashing current build with a valid known working beansgapps that even gives me errors. Having props also with Prime Kernel not installing. It does seem to point to a huge conflict with data not being fully wiped. I'm afraid to go full on format until I see less error messages. Even got TWRP turning red just before reboot! Not my kind of fireworks. Will be staying with previous official build for now. ;-DeanoD

 

[ollimi1]

I'm getting similar results with latest build. Heck, even TWRP itself is getting in on the total crap party. When flashing current build with a valid known working beansgapps that even gives me errors. Having props also with Prime Kernel not installing. It does seem to point to a huge conflict with data not being fully wiped. I'm afraid to go full on format until I see less error messages. Even got TWRP turning red just before reboot! Not my kind of fireworks. Will be staying with previous official build for now. ;-DeanoD

Sh..!
Unhappy to hear that, buddy!
Hopefully you can bring an older version to run.
Maybe try a full wipe/factory reset next time(incl.data media) and make sure you use ext4 as file system not f2fs.
You can see the used file system in trwp protocoll.
Maybe re-format the whole data partition, there is a repair option to change or format file systems.
:thumbs pressed:

 

[DeanoD]

Forked?

I'm having problems left, right and up my wahzoo! EVERY file that I have downloaded recently seem to be corrupted!
Tried to flash ShevT's TWRP and get md5 errors, corrupt file messages. I tried flashing Prime Kernel, and it is the right one, and it almost shot me out of recovery. And now, when I boot to recovery, it's behaving like it has a short circuit. Half of the screens are missing and when I try to touch the screen for input, it seems to randomly run files on it's own.
Could that be from using a 3rd-party app to boot into recovery? I just d/l a new TWRP from the link and it show the md5 wrong. I'm beginning to think I may have finally run out of luck with my note.
Should I just go for broke and reformat with a full install? Just don't understand why this is happening. Can't trust the files that I do have anymore. ;-DeanoD

 

[ollimi1]

I'm having problems left, right and up my wahzoo! EVERY file that I have downloaded recently seem to be corrupted!
Tried to flash ShevT's TWRP and get md5 errors, corrupt file messages. I tried flashing Prime Kernel, and it is the right one, and it almost shot me out of recovery. And now, when I boot to recovery, it's behaving like it has a short circuit. Half of the screens are missing and when I try to touch the screen for input, it seems to randomly run files on it's own.
Could that be from using a 3rd-party app to boot into recovery? I just d/l a new TWRP from the link and it show the md5 wrong. I'm beginning to think I may have finally run out of luck with my note.
Should I just go for broke and reformat with a full install? Just don't understand why this is happening. Can't trust the files that I do have anymore. ;-DeanoD

Holy moly, it's getting more and more worse, man.
Try to download the files via another browser and if it not help, try download it with another device or with a PC. You can transfering the files to your ext.sdcard when they are okay and flash it from there.
I would also remove the third party app and try start into recovery via power&volume- button combi.

And I would definately do a full format to remove all old files and especially these leftovers from touchwiz. As you know, app data will not been removed by a "normal" data wipe and they can really lead into trouble when switching often between TW5.1 and latest AOSP. Transfer the necessary files (rom, gapps, twrp, kernel) to your external memory card and safe other important files there.

I've got many several issues in the past few years with different samsung devices and the internal storage(s2, s3,..) and most of the time a full wipe/format of the whole data partition was able to solve it.
Another possible reason could be the display connector, it is connected by a flatband cable which gladly unmount or get loose from time to time.
I've already fixed it by myself and it's really simple!
However, you need to open the device to verify this (There are some how-to's on youtube, search keywords: Fix blackscreen on Samsung Note10.1/p600).
But I still hope a full wipe/format of your internal storage will fix it... because the removing of the backside is very time-consuming because you have to loosen many little snap-locks.

 

[Falloutboy2000]

So far very stable Rom - thanks again
Funny, mobile device eats most of battery?!?
I dont have... P600

 

[mosimchah]

So far very stable Rom - thanks again
Funny, mobile device eats most of battery?!?
I dont have... P600

Mobile data doesn't take up any battery, it just looks like it does in that one instance

 

[OMIGHTY1]

Cannot update

The links for all recent updates lead to a 404 error. What's up with that?