Related
First things first:
Code:
#include <std_disclaimer.h>
/*
* 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.
*/
The team:
We are a team, for more informations check this link: click thinghy
Because I own the device, I will manage this thread.
About the ROM:
General Features
Stock 4.4.4
Camera (photo and video) works. NFC (probably).
No bugs, everything works. (hopefully). ---- Look here.
Thats it.
Installation guide:
Copy ROM and gapps to sdcard
Flash ROM
Flash Gapps
Reboot and enjoy.
Credits to:
@broodplank1337
Downloads:
AOSP-prefinal
Google Apps
SuperSU
Screenshots:
Check attachments.
Terms and Conditions / Agreement.
If you want to say "Thanks!":
There are many ways to show your support to the developer. You can:
Press the "Thanks" button.
Hit the donation button and "buy me a beer".
Share your opinion about my work and write some feedback in the thread.
Advertise my work to your friends.
Rate my thread with 5 stars.
Sharing policy:
If you want to share my ROM to your friends or on other Forums, you are free to do it ,but please follow these rules:
Inform me about using my work by sending me a message. You don’t need my permission, but inform me.
Include a link to original thread.
Give proper credits for what you used.
Sharing is one thing, but please respect some areas of my work like:
ROM name, parts of my work that are not supposed to be used by others without proper permission.
Copyright:
So, you like my ROM and want to use it as a base or include parts of it in your ROM?
You will need my permissions to do it, so please PM me.Any copying without my permissions is considered a KANG!
Include link to my thread from where you took particular files
Give proper credits for what you used.
.
Support:
If you have any issues or questions, please feel free to post them.
If you want to get the fastest and the best answer - ask the question in the thread.
Don't PM me, i don't have time to read all my messages.
you won't know when you need more space. reserved.
Thanks for making the thread, I am really happy to see that my AOSP works good on the xperia Z2!
Everybody enjoy the rom
Your group link isn't working, who's on the team?
Edit: Wait i just rewrote the link.. this works! Will try soon!
Edit 2: Tried the ROM for a bit.
Art works, so that's what I've been using, so these issues might be due to that.
In settings, Advanced force crashes.
In Apps, clearing data of any app causes a soft reboot. I think the clearing of the data actually works, but it still soft reboots.
Titanium backup is stuck on "Asking for root rights" . so i tried checking SuperSU but said it had to be updated, but TWRP way wouldn't work, it just rebooted on a black screen with an orange led and i eventually had to connect to computer and ADB reboot. I don't actually think it's rooted.
I also can't get into recovery.. do i have to fastboot flash a recovery everytime I need to enter it?
Other than that it's smoother than anything I've tried on this ROM!
I really want to install this rom. I just have 2 questions, first what are the known bugs and also what am I gonna lose? x reality, 4k recording everything is gonna be gone?
shahabk818 said:
I really want to install this rom. I just have 2 questions, first what are the known bugs and also what am I gonna lose? x reality, 4k recording everything is gonna be gone?
Click to expand...
Click to collapse
Yes, you will lose Sony features. It's stock android, nothing more, nothing less.
Costinutz32 said:
Yes, you will lose Sony features. It's stock android, nothing more, nothing less.
Click to expand...
Click to collapse
I have issues with the sony's version, My question is how stable this rom is at the moment (I realize it can be work in progress) and also are the radios compatible with t mobile usa?
shahabk818 said:
I have issues with the sony's version, My question is how stable this rom is at the moment (I realize it can be work in progress) and also are the radios compatible with t mobile usa?
Click to expand...
Click to collapse
Rom is stable, didn't find an issue after 1-2 hours of testing. But we have no support for T-mobile devices.
Costinutz32 said:
Rom is stable, didn't find an issue after 1-2 hours of testing. But we have no support for T-mobile devices.
Click to expand...
Click to collapse
so it means its not gonna work with t mobile? Sorry this is really important i'm not even rooted, if i want to install it i have to make sure its gonna work for me
Sebba513 said:
Your group link isn't working, who's on the team?
Edit: Wait i just rewrote the link.. this works! Will try soon!
Edit 2: Tried the ROM for a bit.
Art works, so that's what I've been using, so these issues might be due to that.
In settings, Advanced force crashes.
In Apps, clearing data of any app causes a soft reboot. I think the clearing of the data actually works, but it still soft reboots.
Titanium backup is stuck on "Asking for root rights" . so i tried checking SuperSU but said it had to be updated, but TWRP way wouldn't work, it just rebooted on a black screen with an orange led and i eventually had to connect to computer and ADB reboot. I don't actually think it's rooted.
I also can't get into recovery.. do i have to fastboot flash a recovery everytime I need to enter it?
Other than that it's smoother than anything I've tried on this ROM!
Click to expand...
Click to collapse
The link works now, my bad.
Thank you for your reports, i will check them myself.
Can you please tell me what steps did you follow to install the rom ?
Costinutz32 said:
The link works now, my bad.
Thank you for your reports, i will check them myself.
Can you please tell me what steps did you follow to install the rom ?
Click to expand...
Click to collapse
I was on doomlord's kernel, first i used TWRP, formatted everything including system and internal storage.
Then installed ROM, gapps, and supersu, all from the links in OP. I tried the same things in CWM. I reverted back to doomlord's kernel each time for recovery, then flashed the ROM to get it to boot again. Can you integrate a recovery into the ROM?
shahabk818 said:
so it means its not gonna work with t mobile? Sorry this is really important i'm not even rooted, if i want to install it i have to make sure its gonna work for me
Click to expand...
Click to collapse
As far as i know, t-mobile kernels are different from our kernels. Correct me if i'm wrong.
I will pm you with some questions, maybe i can help you out.
Sebba513 said:
I was on doomlord's kernel, first i used TWRP, formatted everything including system and internal storage.
Then installed ROM, gapps, and supersu, all from the links in OP. I tried the same things in CWM. I reverted back to doomlord's kernel each time for recovery, then flashed the ROM to get it to boot again. Can you integrate a recovery into the ROM?
Click to expand...
Click to collapse
Recoveries are included with kernels. I will make an Aroma installer script, so everyone would choose his kernel. The one included in the ROM is what i considered is the most stable.
Sebba513 said:
Your group link isn't working, who's on the team?
Edit: Wait i just rewrote the link.. this works! Will try soon!
Edit 2: Tried the ROM for a bit.
Art works, so that's what I've been using, so these issues might be due to that.
In settings, Advanced force crashes.
In Apps, clearing data of any app causes a soft reboot. I think the clearing of the data actually works, but it still soft reboots.
Titanium backup is stuck on "Asking for root rights" . so i tried checking SuperSU but said it had to be updated, but TWRP way wouldn't work, it just rebooted on a black screen with an orange led and i eventually had to connect to computer and ADB reboot. I don't actually think it's rooted.
I also can't get into recovery.. do i have to fastboot flash a recovery everytime I need to enter it?
Other than that it's smoother than anything I've tried on this ROM!
Click to expand...
Click to collapse
After some diggin' into it, here is what i found :
The Advanced options crashes for a pretty dumb reason. The activity is not declared in the manifest. Will be fixed or removed. I don't know why it is even there, as it's a cm app.
About the clear data thing, i'll need to decompile some apps so i can see what's wrong in there. Will be fixed.
I am still looking into the super-user problem, i don't know what's causing it.
Thanks again!
Costinutz32 said:
After some diggin' into it, here is what i found :
The Advanced options crashes for a pretty dumb reason. The activity is not declared in the manifest. Will be fixed or removed. I don't know why it is even there, as it's a cm app.
About the clear data thing, i'll need to decompile some apps so i can see what's wrong in there. Will be fixed.
I am still looking into the super-user problem, i don't know what's causing it.
Thanks again!
Click to expand...
Click to collapse
Awesome! Can't wait to try new versions, this will probably become my main ROM! good work on getting back to me :good:
I still remember you guys are from Samsung Galaxy S Plus development ! Now we meet again ! :laugh:
Costinutz32 said:
After some diggin' into it, here is what i found :
The Advanced options crashes for a pretty dumb reason. The activity is not declared in the manifest. Will be fixed or removed. I don't know why it is even there, as it's a cm app.
About the clear data thing, i'll need to decompile some apps so i can see what's wrong in there. Will be fixed.
I am still looking into the super-user problem, i don't know what's causing it.
Thanks again!
Click to expand...
Click to collapse
The app crashes because it has not been included. (the apk is missing) also these settings provide extra options such as setting the vibration strength and enabling/disabling fast charging (if kernel supports). so I really recommend adding it.
for super user it is that you want to place a line in some init (in /etc) or in install-recovery.sh:
Code:
# Activate SuperUser Daemon if existing
if [ -e /system/xbin/daemonsu ]; then
/system/xbin/daemonsu --auto-daemon
fi
or implement init.d support would also do the trick. Users still need to install superuser (through cwm) themselfs tho
Good
thanks man , i will flash it
Code:
#include
/*
* Your warranty is now void.
*
* We are 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 us for messing up your device, we will laugh at you.
*
*/
When coming from any other ROM, you must do a factory reset / clean flash.
The first boot can take a very long time. Don't assume that it is a bad flash, boot loop, etc. until it has sat for at least 5 minutes.
Links
ROM: http://download.cyanogenmod.org/?device=victara
Changelog: http://www.cmxlog.com/13/victara
GAPPS: I don't what is the best one yet, but I am personally using Slim mini. OpenGapps are also recommended often.
PROTIP: Be sure to flash gapps at the same time you flash the rom. If you boot into cm-13.0 without gapps and attempt to flash them later, you're going to have a bad time
Sensors / Ambient Display
If you have "Ambient Display" enabled in Settings >> Display then:
* the stow sensor and flat up sensor will pulse the display when the phone is picked up
* the IR sensors will pulse the display when you wave your hand over the phone
By default the "doorknob" gesture will launch the camera and the chop-chop gesture will toggle the torch.
Finally, when there is an incoming call, waving your hand over the phone will silence the ringer.
If you want to change the behaviour of these various gestures, go to Settings >> Gestures and you can change all of those options.
Known Issues
* TBD
Other Issues?
Before posting on this thread, make sure of a few things:
You've utilized the search function of the forums. Nothing irritates me more than lazy people who do not search for an answer before asking.
If you are the only one having a problem. Boot into recovery, wipe data/factory reset, reflash the rom/gapps and nothing else. Boot up and see if the problem persists.
Make sure your post is relevant to this thread. "I'm having problems rooting/unlocking" is NOT relevant here.
LOGS LOGS LOGS!!!! Use this: SysLog by Tortel
XDA:DevDB Information
Official CM-13.0 nightly releases, ROM for the Moto X 2014
Contributors
crpalmer, invisiblek
ROM OS Version: 6.0.x Marshmallow
Version Information
Status: Nightly
Created 2015-11-24
Last Updated 2015-11-25
Reserved
Nice !
BEST ANDROID, only facebook & messenger cashes but i found some apks working fine now i guess can't update thm
Thanks a lot!
---------- Post added at 09:40 PM ---------- Previous post was at 09:39 PM ----------
Snapchat and Facebook force closing here
kasrawis said:
BEST ANDROID, only facebook & messenger cashes but i found some apks working fine now i guess can't update thm
Click to expand...
Click to collapse
these should be fixed in the next nightly (assuming i get the patch finished in time, worst case scenario the one after that)
kasrawis said:
BEST ANDROID, only facebook & messenger cashes but i found some apks working fine now i guess can't update thm
Click to expand...
Click to collapse
In other forums, I saw that it can be operated as follows:
Using Root Explorer, find and delete the "libsslx.so" /data/app/com.facebook.orca-1/lib/arm file directory
In my case, it works.
The problem is that I do this, every time you restart the phone
Excuse me for my bad english. Or at least, forgive the translator of Google.
Is root finally working or still broken???
gianboy said:
Is root finally working or still broken???
Click to expand...
Click to collapse
Root works for root apps but does not allow to make changes on /system
Sent from my XT1092 using Tapatalk
invisiblek said:
these should be fixed in the next nightly (assuming i get the patch finished in time, worst case scenario the one after that)
Click to expand...
Click to collapse
Great! So Snapchat should also work with the patch? It force closes every time on cm13.
Sent from my Moto X
Google Camera FC when trying to launch video recorder.
Snapchat and facebook are working on the 11/25 build, Google camera from play store is working to. Thanks!
crpalmer said:
Code:
#include
/*
* Your warranty is now void.
*
* We are 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 us for messing up your device, we will laugh at you.
*
*/
When coming from any other ROM, you must do a factory reset / clean flash.
The first boot can take a very long time. Don't assume that it is a bad flash, boot loop, etc. until it has sat for at least 5 minutes.
Links
ROM: http://download.cyanogenmod.org/?device=victara
Changelog: http://www.cmxlog.com/13/victara
GAPPS: I don't what is the best one yet, but I am personally using Slim mini.
Sensors / Ambient Display
If you have "Ambient Display" enabled in Settings >> Display then:
* the stow sensor and flat up sensor will pulse the display when the phone is picked up
* the IR sensors will pulse the display when you wave your hand over the phone
By default the "doorknob" gesture will launch the camera and the chop-chop gesture will toggle the torch.
Finally, when there is an incoming call, waving your hand over the phone will silence the ringer.
If you want to change the behaviour of these various gestures, go to Settings >> Gestures and you can change all of those options.
Known Issues
* TBD
Other Issues?
Before posting on this thread, make sure of a few things:
You've utilized the search function of the forums. Nothing irritates me more than lazy people who do not search for an answer before asking.
If you are the only one having a problem. Boot into recovery, wipe data/factory reset, reflash the rom/gapps and nothing else. Boot up and see if the problem persists.
Make sure your post is relevant to this thread. "I'm having problems rooting/unlocking" is NOT relevant here.
LOGS LOGS LOGS!!!! Use this: SysLog by Tortel
XDA:DevDB Information
Official CM-13.0 nightly releases, ROM for the Moto X 2014
Contributors
crpalmer, invisiblek
ROM OS Version: 6.0.x Marshmallow
Version Information
Status: Nightly
Created 2015-11-24
Last Updated 2015-11-24
Click to expand...
Click to collapse
gapps ???
http://opengapps.org/?api=6.0&variant=nano
I can't seem to enter recovery since I've installed cm13 (yesterday's build). I'm trying to instal today's build but I'm unable to because I can't enter recovery mode. Initially I was using TWRP, then I installed CM's recovery, but that didn't work either.
Any thoughts?
felipevsw said:
I can't seem to enter recovery since I've installed cm13 (yesterday's build). I'm trying to instal today's build but I'm unable to because I can't enter recovery mode. Initially I was using TWRP, then I installed CM's recovery, but that didn't work either.
Any thoughts?
Click to expand...
Click to collapse
i had the same problem, the only solution was to flash the stock rom back, let it boot once and than reflash twrp.
That's exactly what I was going to try now.
uluf said:
i had the same problem, the only solution was to flash the stock rom back, let it boot once and than reflash twrp.
Click to expand...
Click to collapse
felipevsw said:
That's exactly what I was going to try now.
Click to expand...
Click to collapse
felipevsw said:
I can't seem to enter recovery since I've installed cm13 (yesterday's build). I'm trying to instal today's build but I'm unable to because I can't enter recovery mode. Initially I was using TWRP, then I installed CM's recovery, but that didn't work either.
Any thoughts?
Click to expand...
Click to collapse
I was able to get in with this recovery: http://forum.xda-developers.com/showpost.php?p=61558425&postcount=222
Side note - does anyone else get these weird artifacts in the nav keys area when in landscape mode in certain apps? It's duplicated my bluetooth icon here but it has done all sorts of weird corruption other times...
surrealjam said:
Side note - does anyone else get these weird artifacts in the nav keys area when in landscape mode in certain apps? It's duplicated my bluetooth icon here but it has done all sorts of weird corruption other times...
Click to expand...
Click to collapse
+1
Camera Bug
@crpalmer, @invisiblek: came accross a bug... Took a snap with Google Camera successfully once. Second time I try, the image freezes when I click the shoot button. I can interact with the camera app in some ways, like the swipe-from-left for options, and I can interact with the navbar, status bar, etc. But the image remains frozen, it isn't saved, and I can't proceed to click another pic until I restart the phone. Log attached; verbose; from CMAction to bring up camera, to close of camera.
Disclaimer:
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 the tools/files!
* 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.
*
*/
You NEED a MicroSD, and it WILL be formatted during this process.
THIS WILL NOT WORK ON GALAXY S3/GALAXY S4/GALAXY S6|e/Galaxy S7|e. It will NOT work on AT&T.
We can't help you root or teach you how to use ADB. It's important you have the ability to do these things or research them a bit before blindly using this.
Click to expand...
Click to collapse
This is a summarized guide with the required files to upgrade and unlock the new bootlloader required for Android 6.0.1 Marshmallow (N910VVRU2CPD1) on Verizon Samsung Galaxy Note 4 (SM-N910V). Extended details about each step (e.g., rooting) can be found in the General Section of this forum.
If you're already on unlocked Android 6.0.1 Marshmallow bootloader, you can extract and flash the DevEd partial firmware via Odin to upgrade:
N910VVRU2CQL1_PartialFirmware_DevEd.tar.md5.7z
This will upgrade the base firmware (NON-HLOS, modem, rpm, sbl1, sdi, and tz) to N910VVRU2CQL1.
Click to expand...
Click to collapse
Requirements:
Verizon Samung Galaxy Note 4 (SM-N910V)
All files in the Download Section
Odin installed on Windows
ADB installed on Windows, Mac, or Linux
Click to expand...
Click to collapse
Notes:
If you own a Developer Edition, you can still use this method unless you want to keep your original CID and signature. If so, make backup of your aboot and CID! You may contact @ryanbg to create a special unlock binary for your own device.
Everyone should unlock his bootloader on Lollipop to save extra steps and prevent complications. The official thread (or any guides based on it) will change your device CID to 150100523231384d4100657e54fc1200 which will match and allow for direct unlocking of the Marshmallow bootloader. Otherwise, the unlock binary will change your decvice CID and reboot, which may end up with a bootloop that requires extra step(s) to fix.
It's recommended to wipe data (factory reset) in stock recovery after Odin flash of full firmware.
Make appropriate backups of everything before trying this.
Click to expand...
Click to collapse
Instructions:
Unlock your Lollipop bootloader to match CID (start here)
You can ignore this step if you did it already. If not and for Developer Edition owners, I'd recommend to flash N910VVRU2BPA1 Full Firmware via Odin before unlocking.
Boot into Download Mode
Extract and flash N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar.md5 via Odin
This will make you on Lollipop with Marshmallow bootchain/firmware/modem, which is rootable.
Root your device (Check General Section for detailed instructions)
Note that WiFi will not work due to the updated bootloader, but you can use Mobile data if needed for rooting.
Unlock the bootloader using the same method:
Code:
[email protected]:/ # cd /data/local/tmp/
[email protected]:/ # chmod 777 samsung_unlock_n4-fix <
[email protected]:/ # ./samsung_unlock_n4-fix
============================== samdunk unlock 0.0.1 ==============================
NOTE 3 BETA UNLOCK!!!!!!!!!!!!!
this application comes with NO WARRANTY (express or implied)
this binary may not be rehosted, repackaged, one-clicked, etc.
there is no support provided for this application
this application has been tested on the Verizon Galaxy S5 only
it may work on the AT&T Galaxy S5, and possibly other similar Galaxy devices
there are no compatibility checks, do your research first
if run on an incompatible phone, it will likely permanently ruin the device
we STRONGLY advise against running any binary not obtained from the official source
official source is available at http://github.com/beaups/SamsungCID
SD card is required, all data on the SD card will be destroyed
changing to this developer CID may have other implications
the psn derived from the CID may be used for critical services
changing this psn may cause unexpected behavior or loss of services
continue at your own risk, you've been warned
aboot dev signature research credit to ryanbg
http://forum.xda-developers.com/member.php?u=766721
eMMC vulnerability, exploit, and the code you are running by beaups (sean beaupre)
http://forum.xda-developers.com/member.php?u=711482
Do you understand the implications of these warnings?
(Yes/No)
[+] CID at boot time is/was: 150100523231384d4100657e54fc1200
[+] dev CID matching, proceding to unlock
[+] backing up loaders, this will take a few minutes
[+] loaders successfully backed up
[+] success! powering off device, hopefully its not bricked!
Boot into Download Mode
Extract and flash twrp-3.0.2-0-trltevzw.tar.md5 via Odin
Boot into TWRP recovery
Flash MM Safe Upgrade, JasmineROM, or any MM TW (or MM+ AOSP-based) ROM
Extract and flash N910VVRU2CQL1_PartialFirmware_DevEd.tar.md5.7z via Odin
This will upgrade the base firmware (NON-HLOS, modem, rpm, sbl1, sdi, and tz) to N910VVRU2CQL1.
Reboot to system
ENJOY!
Click to expand...
Click to collapse
.
XDA:DevDB Information
Bootloaader Unlock, Tool/Utility for the Verizon Samsung Galaxy Note 4
Contributors
hsbadr, ryanbg, beaups
Source Code: https://github.com/beaups/SamsungCID
Version Information
Status: Stable
Created 2016-06-14
Last Updated 2018-01-21
Reserved
Reserved
Thank you Hsbadr.
Sent from my SM-N910V using Tapatalk
@hsbadr @ryanbg @beaups thanks for all the hard work in unlocking new bootloader
Can we run this already?
Edit: Doesn't seem like all the files are available yet.
Sent from my Unlocked/Rooted SM-N910V using XDA-Developers mobile app
Where does one find the N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar.md5 file?
Bicknasty said:
Where does one find the N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar.md5 file?
Click to expand...
Click to collapse
Looks like its still in testing. I dont see the file either.
tolymatev said:
Looks like its still in testing. I dont see the file yet either.
Click to expand...
Click to collapse
blah, that's what I get for resetting before downloading the necessary files
Extra Virgin said:
thanks for all the hard work in unlocking new bootloader
Click to expand...
Click to collapse
You're welcome.
tolymatev said:
Can we run this already?
Click to expand...
Click to collapse
Sure. Why is it posted then?!
Bicknasty said:
Where does one find the N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar.md5 file?
Click to expand...
Click to collapse
tolymatev said:
Looks like its still in testing. I dont see the file either.
Click to expand...
Click to collapse
Bicknasty said:
blah, that's what I get for resetting before downloading the necessary files
Click to expand...
Click to collapse
Click to expand...
Click to collapse
No, it's already tested a few days ago. I just recreated the tar to include MM modem and NON-HLOS so that you don't have to flash extra tars. I'll upload it very soon, but in the meanwhile, you can familiarize yourself with the process and do any preliminary steps (backups, LP unlock, ... etc)
Thank you @hsbadr ....I.m glad your here with us
If I took the OTA, would I have to rollback to 5.1.1 and do this?
datstudandre said:
If I took the OTA, would I have to rollback to 5.1.1 and do this?
Click to expand...
Click to collapse
Yes, unless another method exists.
hsbadr said:
You're welcome.
Sure. Why is it posted then?!
No, it's already tested a few days ago. I just recreated the tar to include MM modem and NON-HLOS so that you don't have to flash extra tars. I'll upload it very soon, but in the meanwhile, you can familiarize yourself with the process and do any preliminary steps (backups, LP unlock, ... etc)
Click to expand...
Click to collapse
You are the greatest man, thanks!
For anybody who looked before but didn't notice, the missing firmware file has been uploaded and linked in the OP
I'm a little confused where does adb come into play at when do we flash the note 4 fix sorry the instructions seem a little vague....sorry....
ct_tec313 said:
I'm a little confused where does adb come into play at when do we flash the note 4 fix sorry the instructions seem a little vague....sorry....
Click to expand...
Click to collapse
If it's like the original root process you have to push a file via ADB.
ct_tec313 said:
I'm a little confused where does adb come into play at when do we flash the note 4 fix sorry the instructions seem a little vague....sorry....
Click to expand...
Click to collapse
Follow the link in the 1st step! It's probably b/c you own a developer edition and never tried to unlock/upgrade the bootloader before. Simply, you need ADB to push the unlock binary to /data/local/tmp and execute it after rooting. Theoretically, this can be done in Terminal Emulator on device, but we prefer to use ADB since users should increase their knowledge before trying something dangerous like this one.
Thank you I do own a developer edition...lol I know how to use adb I'm just a little rusty
..
Sent from my SM-N910V using Tapatalk
hsbadr said:
Disclaimer:
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.
*
*/
You NEED a MicroSD, and it WILL be formatted during this process.
This is a summarized guide with the required files to upgrade and unlock the new bootlloader required for Android 6.0.1 Marshmallow (N910VVRU2CPD1) on Verizon Samsung Galaxy Note 4 (SM-N910V). Extended details about each step (e.g., rooting) can be found in the General Section of this forum.
Requirements:
Notes:
Instructions:
.
XDA:DevDB Information
Bootloaader Unlock, Tool/Utility for the Verizon Samsung Galaxy Note 4
Contributors
hsbadr, ryanbg, beaups
Source Code: https://github.com/beaups/SamsungCID
Version Information
Status: Beta
Created 2016-06-14
Last Updated 2016-06-13
Click to expand...
Click to collapse
Is there anyway us Verizon Edge guys can get our unlock binary updated for MM? :fingers-crossed:
FyrestoneROM T113The simplicity of TouchWiz system without superfluous
Code:
* Your warranty is now void.
*
* We're 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 us for messing up your device, we will laugh at you.
*
Introduction:
This Rom is the stock samsung without annoying apps and with some tweaks made to make your life easier.
I have a lot to do for make it better, but I hope you appreciate my work, if you don't thanks for giving me a chance.
Features:
Based on T113XXU0ARB1
Debolated - Samsung and Google apps (350 MB of useless apps)
Deodexed
Zipaligned
Faster animation scale
Knox Free
Removed boot sound
Rooted with SuperSu
Busybox
Sony System signature - Feel free to install sony apps from play store!
AOSP Keyboard
Removed Samsung Update
Allow apps access to external storage
Removed Loud volume warning
Cyanogen/LineageOS UI sounds
Tweaks:
Battery Tweaks
Better scrolling
Video acceleration and HW debugging
Better RAM management
Google DNS
Download Link:
DOWNLOADMD5: b7694314c6cfe88f013522b86319210d
Old version [4 Feb 2017]: DOWNLOAD
MD5: 283aa300c00ae227b4362945925db4b4
Old version [4 Jan 2017]: DOWNLOAD
MD5: 6f97e788b0b2571742b256e6fcaf1e86
How to install The Rom:
Update your bootloader and baseband to XXU0ARB1 before flash!
1. Flash TWRP 2.8.7.0.tar with Odin 3.12.10.
2. Flash TWRP 3.0.2-0.img inside the recovery (Select Install image and choose Recovery partition).
3. Reboot into TWRP 3.0.2-0.
4. Copy FyrestoneROM_T113_XXXXX.zip in your SD Card.
5. Wipe: System, Data, Cache and Dalvik.
6. Optional – Wipe Internal Storage.
7. Install FyrestoneROM_T113_XXXXX.
8. Reboot and wait about 10 minutes.
How to install The Firmware:
1. Download and extract a zip file containing your desired firmware.
2. Open Odin Tool.
3. Boot your device in the "Download Mode":
(Press Volume Down, Power and Home buttons at same time for 5-8 seconds until download mode is active.)
4. Connect your device to PC via the USB cable while in download mode.
5. Next, check the "Auto Reboot" and "F. Reset Time" options in Odin Tool.
6. Hit the AP/PDA button then browse and select a tar.md5 file from the extracted folder.
7. Finally press the start button to begin flashing the firmware update on your device.
Credits:
Google for Android OS
Samsung for FW and source
Sony for System signature
Cyanogenmod for File manager
@SuperR for the kitchen
@bravonova for Build.prop Tweaks
@Chainfire for SuperSu
@mrRobinson for AdAway
XDA:DevDB Information
FyrestoneROM, ROM for the Samsung Galaxy Tab 3
Contributors
Jimbus369
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: T113XXU0AQA1
Based On: STOCK Samsung
Version Information
Status: Stable
Current Stable Version: 2.0
Stable Release Date: 2017-02-04
Created 2017-01-04
Last Updated 2018-08-18
Reserved
Changelog:
27 July 2018:
Updated to XXU0ARB1
Fixed all previous issues
Removed Cyanogen File manager and Adawey
Now Thunderoar Kernel v5.0 is fully compatible
Updated Busybox and SuperSu
4 Feb 2017:
Updated to XXU0AQA1
Removed some Bloatware
Deodexed
Zipaligned
Faster animation scale
Allow apps access to external storage
Loud volume warning removed
Cyanogen/LineageOS UI sounds
Battery Tweaks
Increase Quality Of Media Streaming
Fixed Google DNS
Fixed Calendar Sync
Various build.prop changes
Various fix
4 Jan 2017:
Initial release
Known issues:
Calendar doesn't synchronize --> Calendar_sync_fix.zip
Tablet doesn't support vpn functionality --> VPN_FIX.zip
Print spooler does not works --> PrintSpooler_FIX.zip
Fantastic! Finally we've got a rom of our very own, for which you've got my immense thanks. I'm very much looking forward to trying it out.
Unfortunately when I flashed it there was a loooong wait on the Samsung logo, and then... Well, after an hour I booted back to recovery to start over.
I honestly don't think your rom was the problem though, because from some point last night everything I tried - custom rom flashing and nandroid backup restores - wound up the same way. Odin + stock + root got a usable system at least, and today's been too busy to try again. But when I do I'll post back about how it goes.
(Sadly, I can't go back in time to see what order I did things and look for a pattern if this happens again. In case it might be useful to anyone, I know for sure I'd gotten stock set up comfortably and made a complete backup before giving thunderoar's T113 kernel a whirl, and that went swimmingly. Even had mounts2sd properly recognizing external sd set up after a long struggle, though not actually enabled yet. Don't know what else i did between making that backup and trying to flash this, but it's likely I just screwed something up somehow.)
PushyPhoenix said:
Fantastic! Finally we've got a rom of our very own, for which you've got my immense thanks. I'm very much looking forward to trying it out.
Unfortunately when I flashed it there was a loooong wait on the Samsung logo, and then... Well, after an hour I booted back to recovery to start over.
I honestly don't think your rom was the problem though, because from some point last night everything I tried - custom rom flashing and nandroid backup restores - wound up the same way. Odin + stock + root got a usable system at least, and today's been too busy to try again. But when I do I'll post back about how it goes.
(Sadly, I can't go back in time to see what order I did things and look for a pattern if this happens again. In case it might be useful to anyone, I know for sure I'd gotten stock set up comfortably and made a complete backup before giving thunderoar's T113 kernel a whirl, and that went swimmingly. Even had mounts2sd properly recognizing external sd set up after a long struggle, though not actually enabled yet. Don't know what else i did between making that backup and trying to flash this, but it's likely I just screwed something up somehow.)
Click to expand...
Click to collapse
Upgrade your firmware to PH5 before flash and use TWRP 3.0.2-0.
Firmware: http://samsung-updates.com/device/?id=SM-T113
TWRP: https://dl.twrp.me/goyave/
Wipe all partition in TWRP:
System, Cache, Dalvik and if you can internal Storage.
Thunderoar Kernel isn't compatible with PH5 firmware for the moment.
Let me know how it goes
Thanks so much for responding even though I didn't specifically ask.
Pretty much all my knowledge comes from following instructions in these forums and piecing little bits of information together, so I've got a few questions - trying to understand the "why" behind these things in order to be more self-sufficient. Please feel free to point me towards resources where I can learn more!
Jimbus369 said:
Upgrade your firmware to PH5 before flash and use TWRP 3.0.2-0.
Click to expand...
Click to collapse
This is a surprise to me - I'd always thought that when flashing a new ROM, everything gets replaced. I never would have figured this part out on my own!
Firmware: http://samsung-updates.com/device/?id=SM-T113
Click to expand...
Click to collapse
There's no Canadian version - but should I presume that, since this is a Wi-Fi only device, the CSC isn't too important?
How much does this matter even when using a device with a network connection?
TWRP: https://dl.twrp.me/goyave/
Click to expand...
Click to collapse
(Ooops, forgot to do this right off the bat. My bad!)
Does recovery version generally make a big difference?
Wipe all partition in TWRP:
System, Cache, Dalvik and if you can internal Storage.
Click to expand...
Click to collapse
I've been wiping Data as well - is that not necessary?
Does wiping Internal Storage have a big effect? I suppose there's a fair bit of app-specific stuff in there that could cause issues?
Thunderoar Kernel isn't compatible with PH5 firmware for the moment.
Click to expand...
Click to collapse
Ah well, soon enough!
Let me know how it goes
Click to expand...
Click to collapse
Of course! You're investing time in putting this together, and helping out users; the very least I can do is let you know what's going on with that time you've invested!
Okay, about to check on the firmware installation!
PushyPhoenix said:
This is a surprise to me - I'd always thought that when flashing a new ROM, everything gets replaced. I never would have figured this part out on my own!
Click to expand...
Click to collapse
When you install a rom, especially a TW one, in most case you need a specific Bootloader to cause it to start and work smoothly.
Wikipedia:
A boot loader is a computer program that loads an operating system or some other system software for the computer after completion of the power-on self-tests; it is the loader for the operating system itself. Within the hard reboot process, it runs after completion of the self-tests, then loads and runs the software. A boot loader is loaded into main memory from persistent memory, such as a hard disk drive or, in some older computers, from a medium such as punched cards, punched tape, or magnetic tape. The boot loader then loads and executes the processes that finalize the boot. Like POST processes, the boot loader code comes from a "hard-wired" and persistent location; if that location is too limited for some reason, that primary boot loader calls a second-stage boot loader or a secondary program loader.
The bootloader runs your rom with specific instructions, if the rom does not support an older bootloader simply does not boot. My rom does not support the older bootloader. A zip flash in this case cannot upgrade a delicate part like the bootloader. You need to flash the newer one with Odin.
There's no Canadian version - but should I presume that, since this is a Wi-Fi only device, the CSC isn't too important?
How much does this matter even when using a device with a network connection?
Click to expand...
Click to collapse
The latest update for your country is PA5. Try with THIS.
Your country code is XAC.
The CSC (Sale Country Code) Is that part of the firmware that contains all the telephone operator customizations (e.g. WAP, MMS) for the intended country. As far as i know, It is not important for us.
(Ooops, forgot to do this right off the bat. My bad!)
Does recovery version generally make a big difference?
Click to expand...
Click to collapse
Yes, the Recovery can make the difference.
I've been wiping Data as well - is that not necessary?
Does wiping Internal Storage have a big effect? I suppose there's a fair bit of app-specific stuff in there that could cause issues?
Click to expand...
Click to collapse
I forgot to write data, my bad! But i wrote it in the instructions in the first topic. For personal experience i had different issues when I didn't formatted the Internal Storage. The Android folder, .thumbnails and others, can create issues.
Ah well, soon enough!
Click to expand...
Click to collapse
I hope that in the next update we could use this kernel. :fingers-crossed:
Of course! You're investing time in putting this together, and helping out users; the very least I can do is let you know what's going on with that time you've invested!
Okay, about to check on the firmware installation!
Click to expand...
Click to collapse
I want to give my best support at all users in difficulty, if you have a problem just ask. :good: :good:
Sorry for my english
Jimbus369 said:
Sorry for my english
Click to expand...
Click to collapse
You're doing just fine!
I'll reply more later, but wanted to report that it's installed and running very smoothly! Haven't played around much but will do at home later.
If you've got any tips for getting mounts2sd up and running I'd really appreciate it!
PushyPhoenix said:
You're doing just fine!
I'll reply more later, but wanted to report that it's installed and running very smoothly! Haven't played around much but will do at home later.
If you've got any tips for getting mounts2sd up and running I'd really appreciate it!
Click to expand...
Click to collapse
I'm happy to hear it. Anyway, I don't know how mounts2sd works. Have you already tried HERE?
Jimbus369 said:
I'm happy to hear it. Anyway, I don't know how mounts2sd works. Have you already tried HERE?
Click to expand...
Click to collapse
Yup, that's the app I'm using, but haven't been able to get my external partition mounted properly. I did manage it once, think it was with thunderoar's kernel though.
Sent from my SM-G900W8 using XDA Labs
Jimbus369 said:
I'm happy to hear it.
Click to expand...
Click to collapse
Life has gotten in the way of playing around with this, but thought I'd send you an update as I said I would...
Your rom is running really nicely on my tablet as I use it daily. It's smooth and small, with no unexpected reboots or fc's on installed apps. Didn't wipe internal SD but it hasn't given me any issues with existing data (probably because there wasn't much to start with).
One thing that has caused a problem is calendar sync. It looks like you've taken out the actual syncing service, so when I try to access my calendars through any app I'm asked to add a new Google account, even though everything's already set up in "Accounts" under Settings. I haven't tried running the "calendars.providers.apk" from my other phone, that should fix the problem - but I don't want to use the wrong version and break something!
Also, I've confirmed that the only time I got mounts2sd working, it was with thunderoar's kernel. So guess that's going to have to wait.
A few adjustments I made to the setup were to uninstall all "unnecessary" system apps (not needed to run the device), and re-install them from the store. This way I've got 676mb free on /system and still over 1.5GB free on internal storage.
I've also added a multi-reboot menu to make getting into recovery or download mode simpler, and this is loading more quickly on your rom than stock. I've also had to modify permissions.xml to allow apps to access external storage by default, and made another tweak to disable the "loud volume warning" (don't remember quite what it was offhand).
Would you consider adding these to a future version?
Again, thanks SO much for putting this together, answering questions, and doing your thing. It's greatly appreciated!
PushyPhoenix said:
Life has gotten in the way of playing around with this, but thought I'd send you an update as I said I would...
Your rom is running really nicely on my tablet as I use it daily. It's smooth and small, with no unexpected reboots or fc's on installed apps. Didn't wipe internal SD but it hasn't given me any issues with existing data (probably because there wasn't much to start with).
One thing that has caused a problem is calendar sync. It looks like you've taken out the actual syncing service, so when I try to access my calendars through any app I'm asked to add a new Google account, even though everything's already set up in "Accounts" under Settings. I haven't tried running the "calendars.providers.apk" from my other phone, that should fix the problem - but I don't want to use the wrong version and break something!
Also, I've confirmed that the only time I got mounts2sd working, it was with thunderoar's kernel. So guess that's going to have to wait.
A few adjustments I made to the setup were to uninstall all "unnecessary" system apps (not needed to run the device), and re-install them from the store. This way I've got 676mb free on /system and still over 1.5GB free on internal storage.
I've also added a multi-reboot menu to make getting into recovery or download mode simpler, and this is loading more quickly on your rom than stock. I've also had to modify permissions.xml to allow apps to access external storage by default, and made another tweak to disable the "loud volume warning" (don't remember quite what it was offhand).
Would you consider adding these to a future version?
Again, thanks SO much for putting this together, answering questions, and doing your thing. It's greatly appreciated!
Click to expand...
Click to collapse
The calendar sync issue should be fixed in the next update.
Anyway, If I have enough time, the next update should contain a lot of new features. Your suggestions are already planned :good:
Jimbus369 said:
When you install a rom, especially a TW one, in most case you need a specific Bootloader to cause it to start and work smoothly.
....
The bootloader runs your rom with specific instructions, if the rom does not support an older bootloader simply does not boot. My rom does not support the older bootloader. A zip flash in this case cannot upgrade a delicate part like the bootloader. You need to flash the newer one with Odin.
Click to expand...
Click to collapse
One more question about this: The way you've worded the second paragraph seems to imply only that older bootloaders don't work with newer roms, so are newer bootloaders backwards compatible? Say I've got the PH5 bootloader installed and I want to restore a backup of the previous firmware, do I have to flash that firmware first?
Sorry if it seems obvious, this is how we learn!
Sent from my SM-G900W8 using XDA Labs
PushyPhoenix said:
One more question about this: The way you've worded the second paragraph seems to imply only that older bootloaders don't work with newer roms, so are newer bootloaders backwards compatible? Say I've got the PH5 bootloader installed and I want to restore a backup of the previous firmware, do I have to flash that firmware first?
Sorry if it seems obvious, this is how we learn!
Sent from my SM-G900W8 using XDA Labs
Click to expand...
Click to collapse
Absolutely it isn't obvious, don't worry . The Bootloader, for my personal experience, are backwards compatible. I don't have a scientific knowledge about this, but for what I did with other device it can work. Just try :fingers-crossed:, don't forget a full backup.
Calendar_sync_fix.zip
Here is a fix for calendar sync.
@PushyPhoenix Thanks for reporting this issue
Jimbus369 said:
Calendar_sync_fix.zip
Here is a fix for calendar sync.
@PushyPhoenix Thanks for reporting this issue
Click to expand...
Click to collapse
This is a huge help, as one reason for getting this tablet was to use the calendar on a bigger screen.... Thanks so much!
---------- Post added at 10:58 PM ---------- Previous post was at 10:50 PM ----------
Jimbus369 said:
The Bootloader, for my personal experience, are backwards compatible. I don't have a scientific knowledge about this, but for what I did with other device it can work. Just try :fingers-crossed:
Click to expand...
Click to collapse
Fantastic - it worked on my S5 (had to restore a backup to retrieve some data).
don't forget a full backup.
Click to expand...
Click to collapse
Never! The most important thing, along with wiping.
When is coming to FyrestoneROM V2 ?
And thank you very much. So love...
Does this work on sm-t116ny ?
Because no development for sm-t116ny .
dhruvpatel_9880 said:
Does this work on sm-t116ny ?
Because no development for sm-t116ny .
Click to expand...
Click to collapse
I don't think it can work. If your device codename is Goyave you can try. Let me know if it works
Jimbus369 said:
I don't think it can work. If your device codename is Goyave you can try. Let me know if it works
Click to expand...
Click to collapse
First of all thanks for replying
My device codename is Goyave3g5m probably .
Can you please tell me which all models have same codename "Goyave"?
And cm 11 for sm-t116 works well on my sm-t116ny.
I will try and let you know does it boots .
---------- Post added at 01:55 PM ---------- Previous post was at 01:40 PM ----------
It is working on sm-t116ny
But wifi hotspot not working
Please help
dhruvpatel_9880 said:
First of all thanks for replying
My device codename is Goyave3g5m probably .
Can you please tell me which all models have same codename "Goyave"?
And cm 11 for sm-t116 works well on my sm-t116ny.
I will try and let you know does it boots .
---------- Post added at 01:55 PM ---------- Previous post was at 01:40 PM ----------
It is working on sm-t116ny
But wifi hotspot not working
Click to expand...
Click to collapse
T113/T113nu and T116/T116ny have a similar codename and hardware (The recovery have goyave codename, therefore any rom with goyave codename can be flashed). For the hotspot, maybe some missing libraries, a different driver or a different kernel makes hotspot broken. Try to restore your kernel from a previous backup.
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,
this is nearly completely based on:
LineageOS 19.1 (Android 12L) for GT-N8000 GT-N8005 GT-N8010 GT-N8013 GT-N8020 BETA
/* * 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...
forum.xda-developers.com
Thats why we still have the same bugs, if I solve them, both will receive updates.
Here you can see how far everything is working for now.
Spoiler: Whats working
N8000, N8010, N8013, N8020:
Boot
Bluetooth
Audio
Graphics
Cameras
Sensors
GPS
Wifi
USB
Video playback (HW/SW)
Tethering via USB, WIFI and Bluetooth
consumerir transmitter
Stylus with gestures and hovering icon
RIL
much more...
Spoiler: Whats not working
Random reboots
sec_keyboard, dock keyboard station, because it drains the battery somehow
Screen lightning bug
Long screenshot
SD-Card can't be formatted as internal storage, this will cause a bootloop
Spoiler: Links
TWRP
N8000 / N8005 Rom
N8010 / N8013 Rom
N8020 Rom
Spoiler: Changelog
15.03.2022
01.04.2022
13.07.2022
18.08.2022
Spoiler: Don't like my boot picture?
If you don't like it, reboot into recovery and type the following command:
adb shell (or use TWRP's terminal)
bash /data/param_restore.sh
reboot
Uploaded a prepared package to build your own boot picture
https://androidfilehost.com/?fid=7161016148664799666
There is no space for gapps, if you don't expand the system partition manually.
I would recommend to use microG instead,
here you can find the installation instructions:
Spoiler: microG instructions
Download Magisk 24.1 and flash it via TWRP (yes, flash the APK file), reboot
Open Magisk and update the App (and do a reboot if it's asking)
Enable Zygisk in Magisk
Download and install microG installer in the Magisk manager, reboot
Download and install safetynet-fix in the Magisk manager, reboot
Check with a safetynet checker app and you should pass
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
Spoiler: How to install it?
Instructions
XDA:DevDB Information
[ROM][12.x][N8000/N801x/N8020][BETA] crDroid 8.3, ROM for the Samsung Galaxy Note 10.1
Contributors
html6405
Source Code: https://github.com/html6405
ROM OS Version: 12.x S
ROM Kernel: Linux 3.x
ROM Firmware Required: TWRP 3.5.2
Based On: crDroid, LineageOS
Selinux: permissive, this only makes sense as soon the ROM is stable.
Version Information
Status: Beta
Created 2022-03-12
Last Updated 2022-08-18
*reserved
First of all, thank you for that ROM. It keeps my beloved Tablet alive
Yesterday I installed it exactly like discribed. After flashing (without Gapps) and the newest version of TWTP. The Rom stucks with the wizard at the "no Sim card inserted" screen. The tablet n8010 didn't got a Sim slot?!
I tried to erase "data" partition, but had no luck.
The lineage os from your page works like a charm.
What can I do?thanks
Avalon01 said:
First of all, thank you for that ROM. It keeps my beloved Tablet alive
Yesterday I installed it exactly like discribed. After flashing (without Gapps) and the newest version of TWTP. The Rom stucks with the wizard at the "no Sim card inserted" screen. The tablet n8010 didn't got a Sim slot?!
I tried to erase "data" partition, but had no luck.
The lineage os from your page works like a charm.
What can I do?thanks
Click to expand...
Click to collapse
Hi,
thanks for your report,
I've honestly thought that I've fixed this problem in the build of yesterday,
did you try this one or the build from the 12.03?
YES! Thank you. It's fixed. Yesterday I tried the Version from the day bevore yesterday
Best regards
Avalon01 said:
YES! Thank you. It's fixed. Yesterday I tried the Version from the day bevore yesterday
Best regards
Click to expand...
Click to collapse
Great .
Update 15.03.2022:
Fixed setup wizard completely
Fixed Updater crash
Hopefully improved screen lightning bug
I didn't get Magisk to work. After flash (the file which is linked here) and starting Magisk app it wants to update. It updates to newest version. After reboot it wants to update boot image. But it fails. "no image found"
If I play this game with the latest version (factory reset, erasing system +flash your image + install 24.3) the all says after opening "there is something to install, do you want to reboot?" like this. If I push yes it says "setup failed" and nothing. Magisk (root) does nothing.
The second problem is video performance. I tested vlc with several configuration. But it lags. Screen freezes. I got a Samsung tab 3 with a custom rom ( Android 7) and it runs like hell
The Gt n8010 must be much better! So I think it's a problem coming from an driver!?
I hope you like that feedback here.
Best regards
Avalon01 said:
I didn't get Magisk to work. After flash (the file which is linked here) and starting Magisk app it wants to update. It updates to newest version. After reboot it wants to update boot image. But it fails. "no image found"
Click to expand...
Click to collapse
Hi,
try Magisk v23 or 24.1, newer version will cause problems.
Avalon01 said:
The second problem is video performance. I tested vlc with several configuration. But it lags. Screen freezes. I got a Samsung tab 3 with a custom rom ( Android 7) and it runs like hell
Click to expand...
Click to collapse
It depends on which video format is used,
in the first version, OMX.SEC.AVC.Decoder was removed,
because it starts some videos the first minute weirdly.
Could you give it a retry with the most recent version?
Also, I would need a logcat while performing some action, otherwise I can't do anything.
And well, this is Android 12, it may also run like hell with Android 7 .
Avalon01 said:
The Gt n8010 must be much better! So I think it's a problem coming from an driver!?
Click to expand...
Click to collapse
It must not, consider that you're running Android 12 on a 10 year old device, it's not a problem of a driver,
it's more a decoding issue.
@html6405
Best new rom for our old N80.. series.......still a lot better than LineageOS19 I think....
@html6405
Sorry, but I have some problems with VPN....
Theres no possibility to customize vpn (no "+" sign)
And another problem (same as with lineageOS17-19):
Some apps (for example covPass or some banking apps (phototan)) are not able to scan (camera function fails)
But nevertheless: Best rom with many customisation possibillities (from crdroid)
Hey,
Good morning, CR Droid 8.3 was released with android 12L, Will this Rom receive this update?
Alexfs said:
Hey,
Good morning, CR Droid 8.3 was released with android 12L, Will this Rom receive this update?
Click to expand...
Click to collapse
Thats already in work
Update 01.04.2021:
Synced with crDroid 8.3 sources (Android 12L)
Fixed boot problem, which mostly appeared after booting from TWRP
Fixed shutdown bug (device restarted sometimes instead)
Implemented Boeffla sound
Switched from Camera2 to OpenCamera because of implementation problems, this means that the flashlight won't work until I've fixed this
Attention: a clean installation is needed!
html6405 said:
Update 01.04.2021:
Synced with crDroid 8.3 sources (Android 12L)
Fixed boot problem, which mostly appeared after booting from TWRP
Fixed shutdown bug (device restarted sometimes instead)
Implemented Boeffla sound
Switched from Camera2 to OpenCamera because of implementation problems, this means that the flashlight won't work until I've fixed this
Attention: a clean installation is needed!
Click to expand...
Click to collapse
Lets test
@html6405 AVC decoder enabled, right?
Vladdrako said:
@html6405 AVC decoder enabled, right?
Click to expand...
Click to collapse
Still disabled.
What GApps do I install? I tried the Mindthegapps and Nikgapps from the LineageOs 19.1 thread but all of them keep telling me that I "have not enough space to install GApps".
Operator69 said:
What GApps do I install? I tried the Mindthegapps and Nikgapps from the LineageOs 19.1 thread but all of them keep telling me that I "have not enough space to install GApps".
Click to expand...
Click to collapse
None of them will fit, you would have to expand your system partition.
Is there a how to?
Maybe that's the problem here with my n8010. After installing some apps got fc. And magisk definitely DON'T work for me. After install (every time clean) many apps are closing immediately after start. And the system is laggy. I tested versions 22.0,23.0 and 24.1. All with a new and clean installed system. Flashing via twrp.
The only systems which work are lineage 16.0 and 19.1 WITHOUT root
19.1 without root works very stable and fast. Cr doesn't. Maybe you are working with an other device E.G. N8000. And the version for n8010 has a problem. Or I have to increase some partition or space!?
BTW thank you for the great ROM!