Database Develop

[ROM][TW][RB1][KitKat][4.4.4] FyrestoneROM [SM-T113][27 July 2018]

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.

[Q] Lost my Huawei Camera App

Hey folks,
NOTE: SOLVED, update below
On my VTR-L09 Single Sim, I flashed TWRP to edit /vendor/etc/hosts and then flashed recovery again. I went a wrong path there and had to flash the original recovery in order to do a factory reset & wipe. My /data-Partition was broken during the process, too, because I was accidentally wiped it
After the fresh wipe, I started the phone again and after it loaded, configured it (without restoring from my backup) and after a couple of seconds my camera app disappeared from the home screen. Dafuq? Since then, I tried to recover it a couple of times.
I am now hoping that the B126-Update brings my camera app back when it arrives via OTA, but until then:
Does anyone have an Idea where my camera app went, and how I can get it back?
Obviously, I checked under the disabled apps.
Thanks for sharing your thoughts
I am on VTR-L09C432B123
UPDATE: I worked out a way of re-flashing an official update without funkyhuawei, check out https://forum.xda-developers.com/p10/development/dev-introducing-redlotus-source-huawei-t3601493

Did you try to install another camera app to see if the camera turn on? it's possible that the data folder of camera to be erased.

Lukx said:
Hey folks,
On my VTR-L09 Single Sim, I flashed TWRP to edit /vendor/etc/hosts and then flashed recovery again. I went a wrong path there and had to flash the original recovery in order to do a factory reset & wipe. My /data-Partition was broken during the process, too, because I was accidentally wiped it
After the fresh wipe, I started the phone again and after it loaded, configured it (without restoring from my backup) and after a couple of seconds my camera app disappeared from the home screen. Dafuq? Since then, I tried to recover it a couple of times.
I am now hoping that the B126-Update brings my camera app back when it arrives via OTA, but until then:
Does anyone have an Idea where my camera app went, and how I can get it back?
Obviously, I checked under the disabled apps.
Thanks for sharing your thoughts
I am on VTR-L09C432B123
Click to expand...
Click to collapse
Have you tried the HiSuite system restore option. I never used it. But if it works like the restore option from Samsung and Sony. You should restart your phone in recovery mode and the original firmware will be flashed?

Hey
thanks for your answers.
The hisuite does not support my model yet (argh).
OpenCamera works fine, whatsapp's camera feature as well....
The Gallery App is still there, by the way.

I'm having the same issue too after an unsuccessful root which required me to factory reset my P10. After factory rest the stock camera app is missing..
Could someone upload their stock camera backup file? It would be much appreciated.

I attached the HwCamera2 folder with apk, lib and oat folder from /system/priv-app.
I'm on VTR-L29C432B123.

Jannomag said:
I attached the HwCamera2 folder with apk, lib and oat folder from /system/priv-app.
I'm on VTR-L29C432B123.
Click to expand...
Click to collapse
Thanks for the file. May I know how do I get it installed?
I navigated through the same directory and found the same files as yours. I tried installing the apk file from both my own and yours but it says it is corrupted.

Thanks, @Jannomag. I have found that most other Huawei-Apps in that priv-app folder are also missing (except I am not entirely sad about many of those). I'll keep digging a bit.
*Update* I just found in my /etc/whitelistedapps.xml points to /vendor/etc/whitelistedapps.xml, which in turn does not exist.
could somebody with a working Camera app please check whether that file /vendor/etc/whitelistedapps.xml exists, and what is written in there?
This is just a straw I am holding on to, not a real trace or hint, though.

Lukx said:
Thanks, @Jannomag. I have found that most other Huawei-Apps in that priv-app folder are also missing (except I am not entirely sad about many of those). I'll keep digging a bit.
*Update* I just found in my /etc/whitelistedapps.xml points to /vendor/etc/whitelistedapps.xml, which in turn does not exist.
could somebody with a working Camera app please check whether that file /vendor/etc/whitelistedapps.xml exists, and what is written in there?
This is just a straw I am holding on to, not a real trace or hint, though.
Click to expand...
Click to collapse
Hy Lukx, i have exactly the same problem. Wanted to root my phone, but I couldnt see the zip file in twrp, so i wiped whole data and did formatting the whole phone. after reboot my camera app was gone, also the themes were disappeared. I tried installing the firmware for my huawei (from a russian site but I dont know if its the right firmware) but it stopped at 5%.
My Phones Build Number is: VTR-L09C432B113
Thanks
stilla98

Funny thing... I am suspecting that some version mismatch of the recovery or boot partition during the Wipe might be the cause, although I do not have any proof of that.
I am currently trying to write a free alternative to funkyhuawei, so we can flash the full firmware easily again. I think i won't be done with that before mid next week, though...
I am using the OpenCamera app in the meantime.

Lukx said:
Funny thing... I am suspecting that some version mismatch of the recovery or boot partition during the Wipe might be the cause, although I do not have any proof of that.
I am currently trying to write a free alternative to funkyhuawei, so we can flash the full firmware easily again. I think i won't be done with that before mid next week, though...
I am using the OpenCamera app in the meantime.
Click to expand...
Click to collapse
So you are telling me, that the funkyhuawei method works? I saw that my Version is supported. Should I try it?
Thanks

stilla98 said:
So you are telling me, that the funkyhuawei method works? I saw that my Version is supported. Should I try it?
Thanks
Click to expand...
Click to collapse
I didn't say that
But as FH reflashes your phone fully, it should do a full recovery. If you feel like investing money into that, why not try? Otherwise, I recommend you wait along with me for another week and see how far I get with my approach, which I promise to release for free...

Lukx said:
I didn't say that
But as FH reflashes your phone fully, it should do a full recovery. If you feel like investing money into that, why not try? Otherwise, I recommend you wait along with me for another week and see how far I get with my approach, which I promise to release for free...
Click to expand...
Click to collapse
Okay , i will wait for it. I will also install the opencamera app.. by the way, do you also have problems with the design? im having only one design and i cannot add more..

stilla98 said:
im having only one design and i cannot add more..
Click to expand...
Click to collapse
I never really use the theme feature, as I have found "my" favorite theme initially and it's now in the Huawei Backup I carry around through reflashes (highly recommended, it stores on SD card). But the "Designs" app seems to show me a couple of designs, yes. I don't want to try downloading them right now, though.

Lukx said:
I never really use the theme feature, as I have found "my" favorite theme initially and it's now in the Huawei Backup I carry around through reflashes (highly recommended, it stores on SD card). But the "Designs" app seems to show me a couple of designs, yes. I don't want to try downloading them right now, though.
Click to expand...
Click to collapse
okay, i hadnt a microsd card since yesterday, i also backed up my phone before wiping and formatting but there are still no themes, i will try installing them on sd card.. thank you for your help

just install via fastboot boot.img recovery.img cust.img system.img
i have same problem but i can fix it

Same problem
Lukx said:
Hey folks,
NOTE: SOLVED, update below
On my VTR-L09 Single Sim, I flashed TWRP to edit /vendor/etc/hosts and then flashed recovery again. I went a wrong path there and had to flash the original recovery in order to do a factory reset & wipe. My /data-Partition was broken during the process, too, because I was accidentally wiped it
After the fresh wipe, I started the phone again and after it loaded, configured it (without restoring from my backup) and after a couple of seconds my camera app disappeared from the home screen. Dafuq? Since then, I tried to recover it a couple of times.
I am now hoping that the B126-Update brings my camera app back when it arrives via OTA, but until then:
Does anyone have an Idea where my camera app went, and how I can get it back?
Obviously, I checked under the disabled apps.
Thanks for sharing your thoughts
I am on VTR-L09C432B123
UPDATE: I worked out a way of re-flashing an official update without funkyhuawei, check out https://forum.xda-developers.com/p10/development/dev-introducing-redlotus-source-huawei-t3601493
Click to expand...
Click to collapse
I have the same problem with my Huawei p10, don't have the camera apk but I can use with the open camera. did you fix the problem? Thank you

been there done that
Guy all you need is follow step on this link to restock rom and start unlock bootloader again

You can try to restore factory settings.

Oreo OTAs

Close thread

Should I bother trying this? What's new? I'm on U firmware which I like but should I wipe to go to Oreo?

Anybody tried this?

vineet381 said:
Anybody tried this?
Click to expand...
Click to collapse
Personally I think is not worth it. This is not final build and will delete data from your device. Then next one will show up in couple days or even (maybe) tomorrow. If I will you I will wait for around another 3-4 weeks to get more stable build.
Sent from my SM-N950U using XDA Premium HD app

I tried it -- the installation took about an hour in Recovery, mainly stayed in the "Patching system files". This install *WILL* wipe your phone (not your SD card though).
The build was super fast (even faster than a fresh Nougat flash).
There were two things that caused me to flash back to Nougat.
- The Wi-Fi was extremely weak. At my desk at work, I can normally see 6 Wi-Fi networks. 4 of them are in my office. With Oreo, I could only see two of them, and it struggled to stay connected to the one that I normally have full signal on.
- Also, my AT&T Gear S2 Classic could not be connected. Upon attempting to pair (after confirming the PIN on phone/watch) Samsung Gear gave a message stating that I need to ensure my phone was compatible and that I had the latest Samsung Gear app. I confirmed that there were no available updates for ANYTHING in the Play Store and Galaxy Apps. Both stores showed that my app was up to date.
If it weren't for those two issues, I'd still be on the Oreo build right now.
Another point -- I experienced my first freeze/reboot on this phone in Oreo. I've had the phone since June of last year and never had any freeze/reboot issues previously. Never dropped or gotten the phone wet, etc.
Hope this helps anyone who is wanting to flash the build!
vineet381 said:
Anybody tried this?
Click to expand...
Click to collapse

DO you know can i install this update on my 935U model and how can i do it ?

You need to ODIN to 935A's latest build (BRA1) then you can upgrade to this Oreo build by flashing it in Recovery.
Janitor87 said:
DO you know can i install this update on my 935U model and how can i do it ?
Click to expand...
Click to collapse

Can you please provide me with the link on this Odin file because I can not find any working link. NOw i'm using BKQH1
nivron said:
You need to ODIN to 935A's latest build (BRA1) then you can upgrade to this Oreo build by flashing it in Recovery.
Click to expand...
Click to collapse

BRA1 ODIN Files
Thanks to @norbarb for that link. I downloaded it the other day. You will have to unRAR the files after you open the initial ZIP file -- otherwise ODIN won't find the files.
Janitor87 said:
Can you please provide me with the link on this Odin file because I can not find any working link. NOw i'm using BKQH1
Click to expand...
Click to collapse

I don't have a windows PC at the moment. Can you plz provide me with a OTA update files. I updated G935AUCS4BQH1-to-S4BQJ2
HOw much updates i should update to the G935AUCS4BRA1
Thank you.
nivron said:
BRA1 ODIN Files
Thanks to @norbarb for that link. I downloaded it the other day. You will have to unRAR the files after you open the initial ZIP file -- otherwise ODIN won't find the files.
Click to expand...
Click to collapse

Janitor87 said:
I don't have a windows PC at the moment. Can you plz provide me with a OTA update files. I updated G935AUCS4BQH1-to-S4BQJ2
HOw much updates i should update to the G935AUCS4BRA1
Thank you.
Click to expand...
Click to collapse
Without a PC, you cannot update to Oreo unless you're already on the AT&T G935A firmware.
Sent from my SM-G955U using Tapatalk

As far as I can tell, there's not an OTA sideload update path to BRA1. Someone else may be able to chime in with it.
I assume you are not an AT&T customer, otherwise you could use the official OTA method to get to BRA1.
Janitor87 said:
I don't have a windows PC at the moment. Can you plz provide me with a OTA update files. I updated G935AUCS4BQH1-to-S4BQJ2
HOw much updates i should update to the G935AUCS4BRA1
Thank you.
Click to expand...
Click to collapse

Janitor87 said:
I don't have a windows PC at the moment. Can you plz provide me with a OTA update files. I updated G935AUCS4BQH1-to-S4BQJ2
HOw much updates i should update to the G935AUCS4BRA1
Thank you.
Click to expand...
Click to collapse
https://samsung.firmware.science/download?url=48775/1488/SS-G935AUCS4BQJ2-to-U4BQK2-UP
https://samsung.firmware.science/download?url=48775/1488/SS-G935AUCU4BQK2-to-S4BQL1-UP
https://samsung.firmware.science/download?url=48775/1488/SS-G935AUCS4BQL1-to-S4BRA1-UP
https://samsung.firmware.science/download?url=48775/1488/SS-G935AUCS4BRA1-to-U4CRB5-UP
In that order
Sent from my SM-G955U using Tapatalk

You are right. I'm using the Verizon 935V model anbd now I flashed ATT firmware and wanna try to install OREO update
nivron said:
As far as I can tell, there's not an OTA sideload update path to BRA1. Someone else may be able to chime in with it.
I assume you are not an AT&T customer, otherwise you could use the official OTA method to get to BRA1.
Click to expand...
Click to collapse

Janitor87 said:
You are right. I'm using the Verizon 935V model anbd now I flashed ATT firmware and wanna try to install OREO update
Click to expand...
Click to collapse
You're in luck then, I've laid out all the OTAs you need to install to your device.
Sent from my SM-G955U using Tapatalk

I'm trying to update now.... I will inform if I will be a lucky man and successfully update my phone
FatalONEM8 said:
You're in luck then, I've laid out all the OTAs you need to install to your device.
Sent from my SM-G955U using Tapatalk
Click to expand...
Click to collapse
---------- Post added at 19:49 ---------- Previous post was at 19:12 ----------
[email protected]:/home/alex/Downloads# adb sideload update.zip
serving: 'update.zip' (~31%) * failed to read command: Success
I can not update
---------- Post added at 20:02 ---------- Previous post was at 19:49 ----------
I found my issue I forgot to enable USB debugging mode. It has fixed my issue.
-------------------------------
Janitor87 said:
I'm trying to update now.... I will inform if I will be a lucky man and successfully update my phone
---------- Post added at 19:49 ---------- Previous post was at 19:12 ----------
[email protected]:/home/alex/Downloads# adb sideload update.zip
serving: 'update.zip' (~31%) * failed to read command: Success
I can not update
Click to expand...
Click to collapse

nivron said:
I tried it -- the installation took about an hour in Recovery, mainly stayed in the "Patching system files". This install *WILL* wipe your phone (not your SD card though).
The build was super fast (even faster than a fresh Nougat flash).
There were two things that caused me to flash back to Nougat.
- The Wi-Fi was extremely weak. At my desk at work, I can normally see 6 Wi-Fi networks. 4 of them are in my office. With Oreo, I could only see two of them, and it struggled to stay connected to the one that I normally have full signal on.
- Also, my AT&T Gear S2 Classic could not be connected. Upon attempting to pair (after confirming the PIN on phone/watch) Samsung Gear gave a message stating that I need to ensure my phone was compatible and that I had the latest Samsung Gear app. I confirmed that there were no available updates for ANYTHING in the Play Store and Galaxy Apps. Both stores showed that my app was up to date.
If it weren't for those two issues, I'd still be on the Oreo build right now.
Another point -- I experienced my first freeze/reboot on this phone in Oreo. I've had the phone since June of last year and never had any freeze/reboot issues previously. Never dropped or gotten the phone wet, etc.
Hope this helps anyone who is wanting to flash the build!
Click to expand...
Click to collapse
Thanks for the feeback, I tried this and I agree on weak Wifi on Oreo. I will keep and play with it for sometime before going back to Nougat. Hopefully new stable version shows up soon.

You are a lucky man because i'm flashing via adb and only 59 %. Which issue with a WiFi ? Can you please provide me more information and maybe do you know who will it fix ?
Thank you
vineet381 said:
Thanks for the feeback, I tried this and I agree on weak Wifi on Oreo. I will keep and play with it for sometime before going back to Nougat. Hopefully new stable version shows up soon.
Click to expand...
Click to collapse

vineet381 said:
Thanks for the feeback, I tried this and I agree on weak Wifi on Oreo. I will keep and play with it for sometime before going back to Nougat. Hopefully new stable version shows up soon.
Click to expand...
Click to collapse
I face the same issues you have described. Originally after applying the Oreo update, I was not able to enable Bluetooth nor WiFi. I had to reboot to recovery and wipe cache.
Once that was done, I was able to get WiFi and Bluetooth to work.
I have the Galaxy Fit2 and was not able to sync watch to the phone with the same error you received. ( I tried the version 3..1.80.80109 of Samsung Accessory Service as suggested in another thread, no luck.)
WiFi as you described is pitiful, luckily I don't rely on WiFi as much so I will continue on with this Oreo build.

Does anyone know how to turn off the red heart rate sensor light off? It is accidentally turning on even if I dont get my finger on it after oreo update
---------- Post added at 02:19 PM ---------- Previous post was at 02:08 PM ----------
Janitor87 said:
You are a lucky man because i'm flashing via adb and only 59 %. Which issue with a WiFi ? Can you please provide me more information and maybe do you know who will it fix ?
Thank you
Click to expand...
Click to collapse
Wifi issue meaning weak signals in Wifi connection on Oreo. I simply followed the steps in flashing through SD card and it took a while (40 mins or so) but eventually it went through the install.

Missing product code

I have installed a couple of roms to test, but last night I got screwed up, I don't know what I did wrong why the product code went missing. I installed @_alexndr's [ROM][N950F/DS/N][ALEXNDR] * U5CRHA * DevBase v5.9 * Encryption support [Sep-16] rom. After it booted up, i noticed that it as so sluggish, I did wipe everything before installing the rom. so I decided to go back to stock. I noticed when I went to download mode the
"carrier id" is now blank whereas it was PAK before it was gone, also I went to settings it displayed XTC/XTC/ .
I did backup my efs
How do I restore my original product code?
Please help

Excuse me, off topic, but what font are you using?

winol said:
Excuse me, off topic, but what font are you using?
Click to expand...
Click to collapse
I'm using Googlesans

upbeatwrench said:
I have installed a couple of roms to test, but last night I got screwed up, I don't know what I did wrong why the product code went missing. I installed @_alexndr's [ROM][N950F/DS/N][ALEXNDR] * U5CRHA * DevBase v5.9 * Encryption support [Sep-16] rom. After it booted up, i noticed that it as so sluggish, I did wipe everything before installing the rom. so I decided to go back to stock. I noticed when I went to download mode the
"carrier id" is now blank whereas it was PAK before it was gone, also I went to settings it displayed XTC/XTC/ .
I did backup my efs
How do I restore my original product code?
Please help
Click to expand...
Click to collapse
This minor issue is NOT related to my ROM and has been disscussed in my thread long time ago
See below disscussion (#252 - #256), especially @dr.ketan's statement (#256):
https://forum.xda-developers.com/showthread.php?p=76121821&postcount=256

_alexndr said:
This minor issue is NOT related to my ROM and has been disscussed in my thread long time ago
See below disscussion (#252 - #256), especially @dr.ketan's statement (#256):
https://forum.xda-developers.com/showthread.php?p=76121821&postcount=256
Click to expand...
Click to collapse
also, after flashing stock firmware, I had the data erased (didn't used the HOME_CSC), after I enable developer options, OEM Unlock is already there and the option is ticked

_alexndr said:
This minor issue is NOT related to my ROM and has been disscussed in my thread long time ago
See below disscussion (#252 - #256), especially @dr.ketan's statement (#256):
https://forum.xda-developers.com/showthread.php?p=76121821&postcount=256
Click to expand...
Click to collapse
I have later more studied and found this code is in bootloader and strongly believe this specifically happens when you flash BL and modem with TWRP instead of odin. I request users to check this. Though this seems purely a cosmetic glitch and yet haven't found any ill effect practically.

dr.ketan said:
I have later more studied and found this code is in bootloader and strongly believe this specifically happens when you flash BL and modem with TWRP instead of odin. I request users to check this. Though this seems purely a cosmetic glitch and yet haven't found any ill effect practically.
Click to expand...
Click to collapse
Is this because of some ROMs with such options to update BL/CP before installing the rom may have cause the issue?

upbeatwrench said:
Is this because of some ROMs with such options to update BL/CP before installing the rom may have cause the issue?
Click to expand...
Click to collapse
This is what is my speculation, if someone don't have this issue and flash BL and Modem with TWRP and if he/she get this error, we can confirm it.
But this code is simply a cosmetic and I haven't seen any issue related to this.

upbeatwrench said:
I have installed a couple of roms to test, but last night I got screwed up, I don't know what I did wrong why the product code went missing. I installed @_alexndr's [ROM][N950F/DS/N][ALEXNDR] * U5CRHA * DevBase v5.9 * Encryption support [Sep-16] rom. After it booted up, i noticed that it as so sluggish, I did wipe everything before installing the rom [...]
Click to expand...
Click to collapse
BTW: Side note - my ROM is NOT sluggish but you just experienced latest Magisk's issue after clean install. More info you will find in similar S8's thread (post #280):
https://forum.xda-developers.com/showthread.php?p=77657344&postcount=280
... I just forgot to put same info in N8 thread

dr.ketan said:
This is what is my speculation, if someone don't have this issue and flash BL and Modem with TWRP and if he/she get this error, we can confirm it.
But this code is simply a cosmetic and I haven't seen any issue related to this.
Click to expand...
Click to collapse
I see, if that's the case, I did tick those options cause I thought it would be better to update BL/CP
anyways, I thought missing the product code or the 3rd csc was a huge problem because as I was installing different roms after I lost it and reinstall the stock FW, there was a lot of lag and every rom that I install, I did wipe/format data,cache before installing a new one.
Another one problem I encountered was everytime I download root explorer app and try to modify some cscfeatures, the SystemUI stops, sometimes even after a few minutes after it restarted, the SystemUI stops.
anyway, I thought these problems was related to the product code being missing, but it's all good now, everything is working just fine :good:

I have had this problem for ages, over 6 months, had flashed a number of roms and different country stock files before I noticed it had changed.
I had not used Dev-Base at the point of realising the change though.
I have never had any issues in functionality despite this. Not seeing anyone else with it, I assumed Samsung maybe updated something for unlocked phones.

_alexndr said:
BTW: Side note - my ROM is NOT sluggish but you just experienced latest Magisk's issue after clean install. More info you will find in similar S8's thread (post #280):
https://forum.xda-developers.com/showthread.php?p=77657344&postcount=280
... I just forgot to put same info in N8 thread
Click to expand...
Click to collapse
Yup, sorry about that, I thought it was only yours,
thanks for letting me know that Magisk was responsible for that extreme lag

upbeatwrench said:
I see, if that's the case, I did tick those options cause I thought it would be better to update BL/CP
anyways, I thought missing the product code or the 3rd csc was a huge problem because as I was installing different roms after I lost it and reinstall the stock FW, there was a lot of lag and every rom that I install, I did wipe/format data,cache before installing a new one.
Another one problem I encountered was everytime I download root explorer app and try to modify some cscfeatures, the SystemUI stops, sometimes even after a few minutes after it restarted, the SystemUI stops.
anyway, I thought these problems was related to the product code being missing, but it's all good now, everything is working just fine :good:
Click to expand...
Click to collapse
Nope, None of such issue is related to missing code.
this error I have on my N8 and I remember once I had flashed BL and modem via TWRP , though at that time I have no idea otherwise I can confirm it. I have made small tool to restore missing code too but never shared (Nor I am using) because t requires to patch on every boot. So my suggestion is just forget it.

Note 8 T-Mob downgrade after update to Pie Beta

Hey All, any chance of getting a step by step to downgrade back to CRK1 or latest Oreo build. I attempted to do so, using the firmware from SamMobile, and it failed during the "Updating System" step with an "Error!" message at 32%. Odin had registered a pass. I installed the Ap, Bl, Cp, and the clean CSC. There was only 30ish percent of battery remaining if that would make a difference. I also had the December update installed when I updated to the DLR6 version.

pzzamakr1999 said:
Hey All, any chance of getting a step by step to downgrade back to CRK1 or latest Oreo build. I attempted to do so, using the firmware from SamMobile, and it failed during the "Updating System" step with an "Error!" message at 32%. Odin had registered a pass. I installed the Ap, Bl, Cp, and the clean CSC. There was only 30ish percent of battery remaining if that would make a difference. I also had the December update installed when I updated to the DLR6 version.
Click to expand...
Click to collapse
logs from odin? Or any error code or anything?

Nothing from Odin at all. Odin registered it as a Pass. And I'm unsure how I would pull logs from the phone. Once the "Error!" appears during update, the phone will enter a bootloop unless I hold down the power button to enter Recovery. I was able to successfully enter Recovery, reinstall the Pie Beta Update from my SD card, and the phone works fine again. However, I do use Samsung Pay, and I've noticed that service has suffered considerably, so I'd like to go back to Oreo for the moment.

pzzamakr1999 said:
Nothing from Odin at all. Odin registered it as a Pass. And I'm unsure how I would pull logs from the phone. Once the "Error!" appears during update, the phone will enter a bootloop unless I hold down the power button to enter Recovery. I was able to successfully enter Recovery, reinstall the Pie Beta Update from my SD card, and the phone works fine again. However, I do use Samsung Pay, and I've noticed that service has suffered considerably, so I'd like to go back to Oreo for the moment.
Click to expand...
Click to collapse
I wouldnt be suprised if samsung locked going back same what they did with nougat/oreo . I cant help u, sry

pzzamakr1999 said:
Hey All, any chance of getting a step by step to downgrade back to CRK1 or latest Oreo build. I attempted to do so, using the firmware from SamMobile, and it failed during the "Updating System" step with an "Error!" message at 32%. Odin had registered a pass. I installed the Ap, Bl, Cp, and the clean CSC. There was only 30ish percent of battery remaining if that would make a difference. I also had the December update installed when I updated to the DLR6 version.
Click to expand...
Click to collapse
Which ODIN are you using? Make sure you're using the modded 3.13.1. Try this: Uncheck the auto-reboot option on ODIN. Flash the Oreo firmware and let it finish. Once it's done, manually reboot into recovery and perform a factory reset. Then boot into the OS.
ScaleneVirus288 said:
I wouldnt be suprised if samsung locked going back same what they did with nougat/oreo . I cant help u, sry
Click to expand...
Click to collapse
That only happens when they update the bootloader version. It has nothing to do with the OS version. The Pie leaks are still on the v5 bootloader.

Ok, I will give that a try. I will admit, I'm really enjoying Pie, and its user interface tweaks. I just may forego Samsung Pay and wait until Pie is out of Beta.
On that note, is there any way to install the old radio and use the Oreo radio rather than the one bundled with Pie, assuming that Pie has a new radio bundled. Because that is kinda the Beta killer.
And last comment, once Pie is out of Beta, what will I have to do to upgrade to the "Release" version. Will it be an Odin install, or should an OTA take care of it?

pzzamakr1999 said:
Ok, I will give that a try. I will admit, I'm really enjoying Pie, and its user interface tweaks. I just may forego Samsung Pay and wait until Pie is out of Beta.
On that note, is there any way to install the old radio and use the Oreo radio rather than the one bundled with Pie, assuming that Pie has a new radio bundled. Because that is kinda the Beta killer.
And last comment, once Pie is out of Beta, what will I have to do to upgrade to the "Release" version. Will it be an Odin install, or should an OTA take care of it?
Click to expand...
Click to collapse
Also check the USB port, use the older USB port this has happened to me or PC and see the phone is probably not compatible with newest USB port....
Sent from my SM-N960U using Tapatalk

pzzamakr1999 said:
Ok, I will give that a try. I will admit, I'm really enjoying Pie, and its user interface tweaks. I just may forego Samsung Pay and wait until Pie is out of Beta.
On that note, is there any way to install the old radio and use the Oreo radio rather than the one bundled with Pie, assuming that Pie has a new radio bundled. Because that is kinda the Beta killer.
And last comment, once Pie is out of Beta, what will I have to do to upgrade to the "Release" version. Will it be an Odin install, or should an OTA take care of it?
Click to expand...
Click to collapse
What issues are you having with Spay? It seems to work for everyone else, me included.
No, you can't flash a different radio.
Not sure yet what will be required when when the official drops. Won't know until it drops.

So the Pay app opens fine, and it authenticates the card without issue. It will also allow me to put my fingerprint in, and then have the countdown start. However, it doesn't seem to enable the mag spoofer or the nfc chip, and when put next to a mag reader or Pay system, nothing happens. The countdown will continue, and will restart if I ask it to. But again, the phone doesnt seem to do anything.

pzzamakr1999 said:
So the Pay app opens fine, and it authenticates the card without issue. It will also allow me to put my fingerprint in, and then have the countdown start. However, it doesn't seem to enable the mag spoofer or the nfc chip, and when put next to a mag reader or Pay system, nothing happens. The countdown will continue, and will restart if I ask it to. But again, the phone doesnt seem to do anything.
Click to expand...
Click to collapse
Weird. I'll have to try it. I thought it was working, but now I'm not sure. I use my Gear S3 so often to pay, now I'm not sure LOL.

Update on the effort to revert back to CRK1.
Used the modified Odin, and un-checked auto-reboot. Phone remained in Download mode.
I could not figure out a way to go from Download mode to recovery mode directly. If someone knows how to do this, it would be appreciated if you could let me know.
However, rather than the "Error!" message, I received a "Erasing" message. Than the phone rebooted, and just kept rebooting, going from T-Mobile splash screen to Samsung and back over and over, with some optimizing apps screens thrown in for good measure.
So I tried again with auto-reboot on, and this time received the "Error!" message, and was able to go into recovery once that happened.
The odd thing is, nothing on my phone was changed, other than having to redo the Samsung biometrics for security. All of my apps and accounts and emails were already there, undeleted.

One more update on the S-Pay. After reinstalling the Update.zip from my SD card in Recovery, iIt does seem like there may have been a change. It is now doing the vibrate thing, which I don't think it was doing before. I will put it to the test later this week.

Downgrade Successful
Performed Factory Reset from Phone menus. (not doing so kept resulting in an unauthorized factory reset prompt)
Performed Factory Reset from Recovery Menu.
Cleared Cache through Recovery Menu
Used Patched Odin
Kept Auto-Restart Checked
Used SamMobile CRK1
Phone restarted successfully.

pzzamakr1999 said:
Performed Factory Reset from Phone menus. (not doing so kept resulting in an unauthorized factory reset prompt)
Performed Factory Reset from Recovery Menu.
Cleared Cache through Recovery Menu
Used Patched Odin
Kept Auto-Restart Checked
Used SamMobile CRK1
Phone restarted successfully.
Click to expand...
Click to collapse
Yes! I'm sorry I thought I told you to try a factory reset. You have to factory reset when downgrading. Otherwise bootloop city. Sorry I wasn't more clear, I could've saved you some frustration.
---------- Post added at 11:18 AM ---------- Previous post was at 11:17 AM ----------
I just went back and re-read my posts. I never said try a factroy reset first. Grrr...I'm so sorry!

Mr. Orange 645 said:
Yes! I'm sorry I thought I told you to try a factory reset. You have to factory reset when downgrading. Otherwise bootloop city. Sorry I wasn't more clear, I could've saved you some frustration.
---------- Post added at 11:18 AM ---------- Previous post was at 11:17 AM ----------
I just went back and re-read my posts. I never said try a factroy reset first. Grrr...I'm so sorry!
Click to expand...
Click to collapse
No worries, and I did very much appreciate the help. I should have realized that that should come first. I was a bit frustrated and wasn't thinking logically. It was actually the "fixing apps" message you get when you upgrade that clued me in I wasn't properly resetting the phone prior to install.
Regardless, its all good, and now that I know how to do it, I'll be more inclined to try these out in the future.

Any specific reason for the downgrade? Anything not working?

Camera issues on pie beta
My ar emoji not working on this pie update and sometimes force closes any1 else having this issue

Fitted2 said:
My ar emoji not working on this pie update and sometimes force closes any1 else having this issue
Click to expand...
Click to collapse
Yes

Mr. Orange 645 said:
Yes
Click to expand...
Click to collapse
You downgraded because no AR emoji? And what force closes are you having?

dami00976 said:
You downgraded because no AR emoji? And what force closes are you having?
Click to expand...
Click to collapse
I never said I downgraded.