[ROM][TW][RB1][KitKat][4.4.4] FyrestoneROM [SM-T113][27 July 2018] - Galaxy Tab 3 7.0 Android Development

FyrestoneROM T113​The 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:
DOWNLOAD​MD5: 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.

Related

[AOSP][KK][4.4.4] AOSP Pre-Final

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

CM Recovery for Nexus Player (fugu)

This is the CM-12.1 recovery for fugu.
Use the bottom button to navigate. One push to scroll down and long press to select. I've tested both adb side load and install from internal storage. This recovery also supports adb backup, but I haven't tested it yet.
I hope you enjoy not having to fastboot everything.
Download: fugu_cm_recovery-20150418.img
To install just boot bootloader and
Code:
fastboot flash recovery fugu_cm_recovery.img
Dude, quit being so amazing. It's getting ridiculous.
Excellent! This is the first custom recovery available for this device, correct? I suppose this would open the door to something like the Xposed Framework being installed on the Nexus Player but since my device is running on Android 5.1, I'll probably wait until rovo89 officially adds support for the latest version of Android first.
Yes!!! Glad to see you!
@WugFresh
@dhacker29 Sweet! Thank you! May I suggest you don't use dev host to host this file . They use to be good a while back, but now often employ sketchy MITM type "download manager" scams, and other bad practices. From the original dev thread http://forum.xda-developers.com/showthread.php?p=54363645 -
Dear Developers,
It has come to our attention that due to excessive ads that simulate download buttons, fly-by malware APK attacks from Mobogenie, and reused (and potentially dangerous) reused short URLs, Dev-Host no longer meets our minimum acceptable requirements as a hosting affiliate. As such, we are ending our affiliation with this provider. We urge you to find a safer download host for your development projects such as our other affiliates: Goo.im and AndroidFileHost.
Click to expand...
Click to collapse
Just a heads up. I had a bad experience with them before I saw that post.
Also, it would be awesome if you had a naming convention with version number for all future releases (assuming you plan on updating it); like "cm_recovery_fugu_1.0.0.img" or something.
Thanks again! I know lots of people have been patiently waiting and hoping for a fugu recovery. [emoji106] [emoji106] [emoji106]
GabbyWC said:
Excellent! This is the first custom recovery available for this device, correct? I suppose this would open the door to something like the Xposed Framework being installed on the Nexus Player but since my device is running on Android 5.1, I'll probably wait until rovo89 officially adds support for the latest version of Android first.
Click to expand...
Click to collapse
Yes this is the first recovery for the device but last I checked Xsposed had nothing to do with recovery. This will allow for custom firmware like cm-12.1 to be flashed to the device without having to use fastboot.
---------- Post added at 03:27 AM ---------- Previous post was at 03:17 AM ----------
WugFresh said:
@dhacker29 Sweet! Thank you! May I suggest you don't use dev host to host this file . They use to be good a while back, but now often employ sketchy MITM type "download manager" scams, and other bad practices. From the original dev thread http://forum.xda-developers.com/showthread.php?p=54363645 -
Just a heads up. I had a bad experience with them before I saw that post.
Also, it would be awesome if you had a naming convention with version number for all future releases (assuming you plan on updating it); like "cm_recovery_fugu_1.0.0.img" or something.
Thanks again! I know lots of people have been patiently waiting and hoping for a fugu recovery. [emoji106] [emoji106] [emoji106]
Click to expand...
Click to collapse
I have to agree with Wugfresh on this bro AndroidFileHost is great. All you need to do is @ the guy on Twitter and he'll hook you up with a developer account complete with ftp access.
Wugfresh the issue with a revision on this is it's cm's android bootable recovery so technically anytime a commit is made to that repo it would be a revision change.
I'll host the updated image somewhere else tonight and I will be adding the date to the end of the image so you can tell if it is updated.
bkjolly said:
Yes this is the first recovery for the device but last I checked Xsposed had nothing to do with recovery. This will allow for custom firmware like cm-12.1 to be flashed to the device without having to use fastboot.
Click to expand...
Click to collapse
The Q&A for Xposed on Android 5.0 at http://www.xda-developers.com/xposed-framework-for-android-lollipop-is-here/ contains this quote:
I want to install it. Now! What do I have to do?
Make sure that you’ve read my words above and you’re familiar with your phone’s internals. Obviously, you need to be on a Lollipop ROM and have a good backup of your data. For now, I will only publish the ARMv7 version. 64-bit is more complex, so let’s try the “easy” variant first.
For now, the installation has to be performed manually in a custom recovery. Flashing the zip file will install:
* app_process32_xposed and some symlinks
* libexposed_art.so
* libart.so and some related binaries + libraries (based on 5.0.2, enhanced with support for hooking etc.)
* XposedBridge.jar (now stored in /system/framework)
Backups of existing files will be created automatically and could be restored later.
Can confirm a working flash. Everything looks great! Thanks for all the hard work
no option to make a recovery image...whats the point of this then?
I tried to wipe my cache to free some space and it sent my nexus player into a bootloop...whats going on with this?
How exactly does this work? If my device is rooted on 5.1.0 and I flash this custom recovery. Can I make a backup of everything on the device? Then when google goes to update the android version, can I update it, then restore my backup of everything and not lose root? I'm sorry i'm new to custom recovery and not quite sure how they work. Thank you for your help!
Edit
Noob
I'm a bit of a noob - I have managed to ADB a new boot and system image to my nexus player - it's now running lollipop1.6. What does this recovery mean and how is it different than loading a boot and system image? Thanks - Does this require ClockworkMod?
dhacker29 said:
I just got my Nexus Player last night and made a working version of CM recovery for it. Use the bottom button to navigate. One push to scroll down and long press to select. I've tested both adb side load and install from internal storage. This recovery also supports adb backup, but I haven't tested it yet.
I hope you enjoy not having to fastboot everything.
Download: fugu_cm_recovery.img - 8.41 MB
To install just boot bootloader and
Code:
fastboot flash recovery fugu_cm_recovery.img
Click to expand...
Click to collapse
OathYvne said:
How exactly does this work? If my device is rooted on 5.1.0 and I flash this custom recovery. Can I make a backup of everything on the device? Then when google goes to update the android version, can I update it, then restore my backup of everything and not lose root? I'm sorry i'm new to custom recovery and not quite sure how they work. Thank you for your help!
Click to expand...
Click to collapse
if you restored your backup you would be downgrading it from the update you just took. you dont need a custom recovery to back up apps and their data, there are apps for that. a custom recovery makes it so its easier to flash new/custom roms(os), make backups of the current rom(os) so if anything goes wrong you can restore it, flash zips like the supersu zip or xposed framework. if you try take an ota with a custom recovery the ota will fail to install as its looking for the stock recovery(may be diff on a nexus device but its always been like that on the devices i have owned)
OathYvne said:
How exactly does this work? If my device is rooted on 5.1.0 and I flash this custom recovery. Can I make a backup of everything on the device? Then when google goes to update the android version, can I update it, then restore my backup of everything and not lose root? I'm sorry i'm new to custom recovery and not quite sure how they work. Thank you for your help!
Click to expand...
Click to collapse
This recovery does not provide a "nandroid" type backup where all of your info is zipped up and stored on the devices internal storage, where any application can get access to it, but rather supports adb backup. which backs up your information to a file on your computer. See http://forum.xda-developers.com/galaxy-nexus/general/guide-phone-backup-unlock-root-t1420351 for more information on usage.
WugFresh said:
@dhacker29 Sweet! Thank you! May I suggest you don't use dev host to host this file . They use to be good a while back, but now often employ sketchy MITM type "download manager" scams, and other bad practices. From the original dev thread http://forum.xda-developers.com/showthread.php?p=54363645 -
Just a heads up. I had a bad experience with them before I saw that post.
Also, it would be awesome if you had a naming convention with version number for all future releases (assuming you plan on updating it); like "cm_recovery_fugu_1.0.0.img" or something.
Thanks again! I know lots of people have been patiently waiting and hoping for a fugu recovery. [emoji106] [emoji106] [emoji106]
Click to expand...
Click to collapse
I swtiched to andriodfilehost and uploaded the latest version.
dhacker29 said:
I swtiched to andriodfilehost and uploaded the latest version.
Click to expand...
Click to collapse
Thanks for an update. I tried to full backup by following commands.
adb backup -apk -shared -all -f C:\backup20151904.ab
But getting this "Now unlock your device and confirm the backup operation" lines and asking for unlock your deivice to confirm. Any sugestion to pass this. Thanks
Yes it seems Google decided to remove the backup confirmation dialog from TcSettings
So it means adb backup of a full ROM is not possible? Going to try your rom later.
Sent from my Nexus 6 using Tapatalk 2

[CUSTOM RECOVERY] TWRP Recovery

DISCLAIMER
We are not responsible for any damage, bootloop, bricked or broken tablets and Relationships.
Team @csolanol & @diegocr is back!!!
Notice
This recovery can't be flashed to the tablet meanwhile the bootloader is locked. We don't have any way to unlock it for now so you must launch it this way:
Code:
fastboot boot TWRP_Fire_2.8.7.0_adb.img
Edit: Project became stable. Got rid of the backlight error thanks to @diegocr.
Download
https://www.androidfilehost.com/?fid=24269982087018181
Update 2015-12-14
MTP working, if doesn't mount disable and re-enable
Don't use USB storage, not working
Update 2015-12-13
Added adb & USB storage mount USB storage not working
XDA:DevDB Information
[CUSTOM RECOVERY] TWRP Recovery, Tool/Utility for the Amazon Fire
Contributors
csolanol, diegocr
Version Information
Status: Stable
Current Stable Version: 1
Stable Release Date: 2015-11-09
Created 2015-11-06
Last Updated 2015-12-14
Video: 2015 Fire: Booting TWRP, Rooting, Installing Gapps
Basic Directions
Download/Install Drivers
Verify Divers were installed Correctly
Download/Install ADB/Fastboot files
Test Fastboot commands
Download Twrp.img from link in post #1
Boot Custom Recovery with
Code:
fastboot boot TWRP_Fire_recovery.img
check root status with https://play.google.com/store/apps/details?id=com.jrummyapps.rootchecker
This is a temporary recovery, it must be booted with fastboot commands, every time want to use it.
What you can do with a Custom Recovery
Root Stock rom with SuperSu.zip
Install Google Apps Select Arm | 5.1 | pico version
Install Xposed Framwork
Backup Rom
Install Custom ROM
Install Stock Firmware (UnBrick)
...
I know this sounds stupid but cant you sign your images by getting the amazon api key or something?
Awesomeslayerg said:
I know this sounds stupid but cant you sign your images by getting the amazon api key or something?
Click to expand...
Click to collapse
I don't think there is anyway to do that which is why signed software is generally trust-able.
bullet25 said:
I don't think there is anyway to do that which is why signed software is generally trust-able.
Click to expand...
Click to collapse
Well i've seen people using lg sign tool or something to sign there images to flash thier images and make them bootable.
keep up the great work now we just gotta get custom rom installed
Can Flashify be used to boot into the recovery?
niphoet said:
Can Flashify be used to boot into the recovery?
Click to expand...
Click to collapse
no, can not
Sent from my KFFOWI using Tapatalk
Hopefully we'll get custom roms soon... AOSP on a $50, quality, device would be awesome!
THANK YOU!!! Making a backup now! I don't know if this is important or not but when I started my backup, it showed the command screen, and the first line I saw there was in red, and said
Code:
[COLOR="Red"]E:Find_File: Error opening '/sys/class/backlight'[/COLOR]
again, don't know if it's a big deal or not but thanks again so glad I can now make a backup and to OTG USB thumb drive even!!! THANKS!!!!!!!!!!!
petermg said:
THANK YOU!!! Making a backup now! I don't know if this is important or not but when I started my backup, it showed the command screen, and the first line I saw there was in red, and said
Code:
[COLOR="Red"]E:Find_File: Error opening '/sys/class/backlight'[/COLOR]
again, don't know if it's a big deal or not but thanks again so glad I can now make a backup and to OTG USB thumb drive even!!! THANKS!!!!!!!!!!!
Click to expand...
Click to collapse
Just ignore that line.
Any Tom development started yet?
Awesomeslayerg said:
Any Tom development started yet?
Click to expand...
Click to collapse
Yes, however right now I'm just doing a highly customized, de-bloated, de-amazon'd, pre-rooted, stock based rom. I don't know if anyone is working on AOSP or CM based roms at the moment.
added video to post #2
Harry44 said:
Yes, however right now I'm just doing a highly customized, de-bloated, de-amazon'd, pre-rooted, stock based rom. I don't know if anyone is working on AOSP or CM based roms at the moment.
Click to expand...
Click to collapse
That sounds really great. I tried to make a deblooated rom, but I broke the settings application by accident. I guess I'll just wait until someone else releases theirs... :/
SD, I am trying to install TWRP as per the video. For some reason, my files look different then your and I am running Win 10. Any advice? Thanks much.
PS: When I get to the command prompt,, mine just opens up to my system, not the ADB folder....
EDIT: Ok, got it to go, don't know how, but it worked. Anyone else notice the device runs a little sluggish after this? Thanks!
hey since this is running lollipop amazon os. cany you guys make a costom rom like the hdx developers do that can be booted without unlocking the bootloader. they use safestrap which is like twrp but for locked bootloaders and install custom roms. they arnt fully custom they have amazon aspects that let it boot with the locked bootloader but it is almost fully custom the hdx has a nexus rom and a cm11 rom they made for it.
sandman512 said:
SD, I am trying to install TWRP as per the video. For some reason, my files look different then your and I am running Win 10. Any advice? Thanks much.
PS: When I get to the command prompt,, mine just opens up to my system, not the ADB folder....
EDIT: Ok, got it to go, don't know how, but it worked. Anyone else notice the device runs a little sluggish after this? Thanks!
Click to expand...
Click to collapse
Did you install Google apps zip?
It's not unusual for google services to slow down a device
sd_shadow said:
Did you install Google apps zip?
It's not unusual for google services to slow down a device
Click to expand...
Click to collapse
Thanks for the reply. Yes, did install the Google Apps Zip? Can that be uninstalled?
sandman512 said:
Thanks for the reply. Yes, did install the Google Apps Zip? Can that be uninstalled?
Click to expand...
Click to collapse
Not as easily as it they were installed.
Use a root file manager, to delete or rename or move.
Use titanium backup pro or similar app, to freeze google apps
you freeze all google apps, and see if performance improved, them unfreeze google apps one at a time to see which ones are causing issues.

Help with Pure Nexus Project would be greatly appreciated

I am new to my Nexus 6 and new to flashing custom roms. I have read the thread all morning long and still don't feel comfortable with what information I have obtained. I'm currently running marshmallow 6.0 rooted with supersu 2.52. How can I flash the latest pure Nexus project 6.0.1 correctly? I do have TWRP recovery installed and I'm running on build number MRA58R
Make a backup in TWRP, wipe your system partition, Flash the ROM zip and the GAPPS zip, reboot, profit. If anything fails you can roll back to your backup and try again.
Real simple. Download the latest built as well as the latest google apps (gapps)
Reboot to TWRP
Do a backup, so you have a restore point if something happens
Go to wipe->advanced wipe and choose both caches, system and data. DO NOT wipe internal storage
Go to install, choose the ROM and gapps and install them
Reboot
You will now be on the latest. You will have to set your phone up again, and all your text messages, home screen, act will be gone but all your stuff on your sdcard (internal storage) will be untouched.
You can also get real ambitious and make backups with something like titanium backup of all your apps and data and restore it after booting PN, but try to not back up system apps or system data (it should be an option... I dont know, I never use tibu). The main thing you lose without backing up is texts, I usually just deal with it/redownload apps/set up home screen again.
On future updates, unless there are major changes and its indicated by a majority of people in the PN thread, just dirty flash.
That is, backup, wipe caches, install new ROM version( I wouldn't reflash gapps ) this will leave all your apps, settings, ect... But should only be done when flashing the same or a very similar ROM. If you dirty flash and experience problems, go back and clean flash as I first instructed.
So I should not worry about flashing the new 32r radio?
shouldnt this have been one of the first things to learn BEFORE you ever rooted your phone? yea, nice job jumping in before learning your way around. i bet you even used a toolkit to root your device..
Everyone's got to start somewhere. And no toolkit here but thanks for your input! And thank you for the helpful responses.
roy.garlington said:
Everyone's got to start somewhere. And no toolkit here but thanks for your input! And thank you for the helpful responses.
Click to expand...
Click to collapse
no tool kit? ok, your -1 on not learning before rooting has a +1 right by it, for rooting the proper way. you just might earn some respect
Hey there simbo, what do you say about flashing the radio?
Sure. Or don't.
Whatever.
The radio is pretty separate from android. Its basically drivers to tell you phone how to use hardware.
FI has certain requirements for activation that may check what radio you have, but outside of that run what ever works good for you., its not going to for sure be any specific one. Newer may often be better but its not uncommon that an older one may work a little better.
Different apps can help you monitor (I dunno which ones... But I know its a thing ), you can also go into about phone -> status -> sim status and check signal strength where lower dBm is better(well a lower numeric value... Its technically a negative number, so higher is better i.e. -113 is worse then -104). This will vary slightly minute to minute and place to place so just taking a glance once won't really settle it for you
I just use it for a day or two, pay attention to how my signal is (just kinda how often did I have decent # of bars, nothing scientific), and check battery stats clicking on cell standby and looking at % of time with out signal.
roy.garlington said:
Hey there simbo, what do you say about flashing the radio?
Click to expand...
Click to collapse
youre choice. you can try any of the radios, from previous android versions, on any android version. they arent specific. im using the 27R radio. whichever one works best for you, thats whats important
roy.garlington said:
I am new to my Nexus 6 and new to flashing custom roms. I have read the thread all morning long and still don't feel comfortable with what information I have obtained. I'm currently running marshmallow 6.0 rooted with supersu 2.52. How can I flash the latest pure Nexus project 6.0.1 correctly? I do have TWRP recovery installed and I'm running on build number MRA58R
Click to expand...
Click to collapse
Well, it's all very easy if you read a little. Still i will give you one extra tip in case you start flashing all kinds of roms: You unlocked your bootloader. Before doing that you enabled "OEM unlocking" in 'Developer options'. Leave that enabled (this setting is 'sticky'. even when you wipe the device)!!!!. Leaving OEM unlocking enabled will disable "Device Protection" that causes sometimes a 72 hours lock-out from your Google account.

[ROM][OneUI 2.5][TWRP] NcX 2.5 for A71 [SM-A715F]

NcX 2.5 A71 ROM​Pretty straight forward, I took OneUI 2.5 firmware, debloated it and added a few features which can be found here: Link to MODs
My plan is to make this the best version of OneUI 2.5 with more features and fixed things (my mission is to fix Secure Folder in the near future) Fixed
Anyway, let's get started.
Code:
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 flashing 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. HARD!
Features!​
TWRP Included
Full OneUI 2.5 features
Debloated
Added camera features
Dolby Atmos without earphones
Optimized
Edge Lighting fully enabled
Secure Folder fixed
Smart View fixed
Samsung Health fixed
Samsung OCR service
Bugs!​
Secure Folder broken (will try to fix later) Fixed on 2.5.1
Samsung Pass broken (because of knox 0x1, duh) Removed from ROM, it will never work.
Bug with AOD brightness when you use fingerprint unlock method. This bug happens when you have AOD to always show. If AOD is showing, then you turn the screen on to only show lockscreen clock and then turn the screen off for AOD to show, the brightness of AOD will reduce to the most minimal and it will be hard to see, regardless of what brightness you set up. There are 2 ways to getting rid of this bug:
Disable unlocking phone with fingerprint
Unlocking your phone and then locking it again. This will only fix it until you trigger the bug again
Fixed, clock animation removed.
You tell me
Changelog!​
25/Oct/2020 (NcX 2.5.2):
Added 60 fps recording on selfie cam
Added wide selfies. (a biiiiit buggy, but serviceable)
Added 24 fps recording modes on pro video mode
Fixed Samsung Health
Added Samsung OCR Service for better text extraction
12/Oct/2020 (NcX 2.5.1):
Secure Folder fixed
Smart View fixed
AOD bug fixed
Removed Samsung Pass
Removed Samsung Daily
Removed "Tips" app
Removed Bixby
Added camera features
08/Oct/2020: Release
Links!​
(V2.5.2)Google Drive
(V2.5.1)Google Drive
(V2.5)Google Drive
Prequisites​MANDATORY ALWAYS: SD Card. It IS possible to have it on internal storage but ONLY if you are not encrypted. If you are encrypted, then you will need to FORMAT DATA and that will delete everything in your internal storage and you won't be able to add it back to internal storage with TWRP because MTP is broken.​For installing 2.5.1/2.5.2:
Installing and following NcX 2.5 installation steps, as well as its prequesites
TWRP Installed (included in NcX 2.5)
Download multidisabler.zip (link: From Telegram Group (also attached on this thread) and add to SD Card or internal storage
Download Magisk zip installer to your SD Card or internal storage
For installing 2.5:
Update to bootloader U3 (either install OneUI 2.1 or OneUI 2.5 fully with Odin), otherwise you will have problems with camera
Fully unlock bootloader. I don't mean just turning OEM unlock on in developer settings , I mean FULLY unlock. If you didn't know, Samsung changed up how you unlock the bootloader on newer devices like this one. @topjohnwu gets a little more specific here: Explanation but I'm going to quote the important stuff to FULLY unlock bootloader:
Unlocking BL on modern Samsung devices have some caveats, so I figure this would be helpful.
Allow bootloader unlocking in Developer options → OEM unlocking
Reboot to download mode: reboot and press the download mode key combo for your device.
Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.
If you think the bootloader is fully unlocked, it is actually not! Samsung introduced VaultKeeper, meaning the bootloader will still reject any unofficial partitions before VaultKeeper explicitly allows it.
Go through the initial setup. Skip through all the steps since data will be wiped again later.
Connect the device to Internet during the setup.
Enable developer options, and confirm that the OEM unlocking option exists and is grayed out. This means the VaultKeeper service has unleashed the bootloader.
Your bootloader now accepts unofficial images in download mode.
Click to expand...
Click to collapse
Download Magisk zip installer to your SD Card or internal storage
Download multidisabler.zip (link: From Telegram Group and also attached in this thread) and add to SD Card or internal storage
Instructions!​For installing 2.5.1/2.5.2:
Reboot to TWRP
Flash NcX 2.5.1.img or NcX 2.5.2 as "super" image in TWRP
Reboot to Recovery
Format data if you are coming from Stock ROM. If you are coming from NcX 2.5 then you don't need to wipe or format, you can just skip this step.
Flash multidisabler (this is required always)
Flash Magisk zip (optional)
Reboot and wait patiently
For installing 2.5:
Reboot to download mode and add AP_NcX 2.5 A71 in AP on Odin
Uncheck the Auto reboot option in Odin
Flash
When it is finished, force a manual reboot (keep pressing VOL - and Power buttons together)
Immediately when phone reboots, boot to recovery mode (VOL + and Power button)
If your phone was unencrypted before, just do a normal wipe. If your phone was not unencrypted before, do a full data format (Go to WIPE option in TWRP, select FORMAT DATA button at the bottom and they type yes on the keyboard. This will completely wipe your internal storage so be sure to backup and photos, music, etc... you have in internal media.)
Flash multidisabler to ensure you do not get encrypted
Flash magisk (I don't know if this is mandatory, I would fully recommend it though)
Reboot and wait patiently
Credits!​ @ananjaser1211 for all your help and always willing to lend a helping hand
@SuperR. For his Super R's Kitchen which you can find here: https://forum.xda-developers.com/ap...dows-linux-superr-s-kitchen-v3-0-0-0-t3601702
@topjohnwu for Magisk
@sac23 for his tutorial on how to fix Secure Folder which you can find here: https://forum.xda-developers.com/showpost.php?p=82978861&postcount=1522
@Belco02 for the extra camera modes and features
@ianmacd in Telegram group TWRP/Root Samsung Android Devices for compiling TWRP for us
@ Samsung for the firmware
@ Team TWRP for their amazing recovery
@ To users like you!
If you feel I missed you, please give me a PM so I can add you
XDA:DevDB Information
NcX 2.5 for A71, ROM for the Samsung Galaxy A71
Contributors
ShaDisNX255, Ian Macdonald
Source Code: https://github.com/ianmacd/twrp_a71
Source Code: https://github.com/ianmacd/a71
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Based On: OneUI 2.5
Version Information
Status: Stable
Current Stable Version: 2.5
Stable Release Date: 2020-10-08
Created 2020-10-08
Last Updated 2020-10-08
Join our Telegram group​
Code:
Check out the latest projects on our Telegram group, where we share our advancement on new things and try to help as best as we can.
For anything already released, please ask here in XDA
Link: Telegram Group
Join our Discord group​
Code:
Check out the latest projects on our Discord, where we share our advancement on new things and try to help as best as we can.
For anything already released, please ask here in XDA
Link: Discord
Android group in spanish
Link: Grupo Android​
FAQ
[Q] My phone is stuck in bootloop/infinite boot, what should I do?
[A] It is normal for first instalation to take aprox 10-20 minutes on first boot, let it sit for a little bit
[Q] Even after 20 minutes, my phone is still in a bootloop/infinite boot, what can I do?
[A] It is possible that your previoius Android setup is conflicting with this new setup. Please, do the following:
1. FORMAT DATA (not WIPE, FORMAT!)
2. Try the instalation of NcX again
[Q] I've found a bug, what should I do
[A] Please read the "Bugs" section of the thread to see if your bug has been reported, if it hasn't, please let me know exactly what the problem is so I can take a look
[Q] I flashed magisk on TWRP but no apps are asking for SU Permission
[A] Make sure you have the Magisk Manager app installed
[Q] I don't see Magisk Manager in my apps
[A] You need to download the manager from the official source: https://github.com/topjohnwu/Magisk
[Q] Something bothers me and I want it fixed/changed
[A] Please, kindly make a request and if it's within my grasp, I'll try to fix it. Just, don't be rude and demand something. Either that or return to stock, your choice
How to report a bug/Ask for a change​
Over the small amount of time I've been doing my edits and shared them with the community, I've noticed something that seems to irritate me. I can't speak for all the developers on this forum, but I do edits/ROMs/PORTs/etc... to what I like. I don't work for anybody else but me. I share my work because it may have something of value to other people and/or some people may share the same taste as me on regards to what they want on a ROM.
That being said, that doesn't mean I will completely ignore what the community has to say.
First and foremost, it must be said, I am merely a beginner. I do not claim to be a professional developer that knows how to add everything, I am nowhere close and I learn as I go.
There are ways to ask for something and/or report a bug when it comes to ROMs, and this post is my attempt to try to explain how to (and how not to) report a bug in order to help me out as much as possible to try to fix something
You can also ask for something to be added, but there are also ways to ask for something
So, here we go
Keep in mind:
I do not add stuff that can easily be downloaded from the Playstore
I, myself, don't do kernel edits
I COULD remove stuff if NOBODY uses it
---REPORTING BUGS---​
How NOT to report a bug:
"SystemUI (or any app)is crashing, please help!"
"Instagram doesn't allow me to edit my post, what could be wrong?"
"My bank account app is not letting me do such thing"
These posts are sort of pointless as they only state something but I have no context on what could be causing it. Also, I can't really control (for the most part) third-party apps, so if you're going to ask about them this way, don't even bother
A slightly better way to report a bug:
"I clean installed the ROM and was working fine, after I installed Facebook and logged in, I immediately uploaded a photo and SystemUI started to crash. Can you look in to it?"
"I tried to install Black Neon theme (a link to it would work as well) and it was working fine until I tried to activate AOD (or anything else for some reason) and SystemUI (or any other app) is crashing, could you look in to it?"
"My bank account app doesn't let me take a screenshot of my accounts. I get a toast notification saying "Can't take screenshot due to security policy"
As you can see, this provides a bit more context and explanation on your current situation. This gives me a little more detail on trying to replicate the problem and hopefully could fix it by replicating it. Well, except for point #3 which is out of my hands for the most part (I think). If you include what kernel you're using would make everything better! Also any significant change that would require root (like xposed and or anything that modifies /system also needs to be informed for better results)
The BEST way to report a bug:
LOGCAT!!!!!!!!!!!!!!!!!!
Please learn the ins and outs of a logcat, this really helps a lot on finding what the problem is. Also, please give a brief explanation as the above examples when providing a log cat
---ASKING FOR STUFF TO BE ADDED---​
How NOT to ask for stuff:
On your next update, add iris scanner
You should add (app) on your next update
Hey, please add (app or feature) on your next update
No, I do not work for you. Even if you say please like the third example, that doesn't mean you're being polite. It still sounds like an order lol so you should probably rephrase your request.
How to ask for stuff to be added to my work:
Would you be so kind to add (feature) to your ROM, if possible?
Would it be possible to add this app to your ROM?
Please, can you add (feature) to your ROM, if it isn't much to ask?
See how politeness makes everything better? You're not demanding it, you're just politely asking to see if maybe it is within my grasp to add something. And if all request would be like this, I can assure you I'd try my best to add said feature
I hope this is useful to you or I at least hope that some people read it.
If not, I can just tell you to return to stock ROM, probably better than any ROM I put out anyway
Enjoy guys, keep on the lookout for updates. I plan on adding more MODs and fixes
Attach the singletake .xml also here
sankhauaa said:
Attach the singletake .xml also here
Click to expand...
Click to collapse
I'll hold it off.
Plan on adding a future update with this and more stuff included
Good mod! Downloading...
well done mate, nice to see
New update hopefully tomorrow.
What's new?
-Fix Secure Folder, now working
-Fix Smart View mirroring, now working
-Adding CSC features, in progress
When i try to do the process of unlocking again It say after long press volume up. Lock Bootloader? Guess thats not what i want? My device is rooted stock with twrp installed..... Do you have an idea.?
I want to install your rom.
hans3103 said:
When i try to do the process of unlocking again It say after long press volume up. Lock Bootloader? Guess thats not what i want? My device is rooted stock with twrp installed..... Do you have an idea.?
I want to install your rom.
Click to expand...
Click to collapse
If you've already rooted, that means you have fully unlocked bootloader and it means that you can now freely install my ROM.
I installed it, it look very good. Its a big timesaver also. I used to root this device in a time comsuming way. This rom is very easy.... Very nice work!
hans3103 said:
I installed it, it look very good. Its a big timesaver also. I used to root this device in a time comsuming way. This rom is very easy.... Very nice work!
Click to expand...
Click to collapse
Thanks, next version will be easier to flash, just with super.img flash on TWRP.
ShaDisNX255 said:
Thanks, next version will be easier to flash, just with super.img flash on TWRP.
Click to expand...
Click to collapse
I will try it for sure, can I do an update or do I have to make a clean install?
hans3103 said:
I will try it for sure, can I do an update or do I have to make a clean install?
Click to expand...
Click to collapse
It can be installed with current version so no need to wipe data
ShaDisNX255 said:
It can be installed with current version so no need to wipe data
Click to expand...
Click to collapse
Very nice....many thanks!
nice business friend
Even if resizing in vendor, it will be nice because it will be very possible to make mod and custom kernel
No idea
my galaxy a71 its still in bootloop. bootloader fully unlocked with oem activated. data formated, installed decrypted data, and magisk zip installed, pls help..
zorexblade said:
my galaxy a71 its still in bootloop. bootloader fully unlocked with oem activated. data formated, installed decrypted data, and magisk zip installed, pls help..
Click to expand...
Click to collapse
Are you getting to boot animation?
Were there any red messages in TWRP when you were installing?

Categories

Resources