Step-by-step guide for new 2017 Fire HD 10 Owner: Root, FlashFire, Google, Launcher.. - Fire HD 8 and HD 10 General

I have gone through the rooting and upgrading steps. Let me know if there is anything I missed.
1. Prepare PC. Install ADB and Fire HD 10 driver at https://developer.amazon.com/docs/fire-tablets/connecting-adb-to-device.html.
2. Don't connect to Internet. Keep the device offline. The instruction is in the thread for rooting. Note ROM version. I have version 5.6.1.0. Amazon has implemented anti-rollback boot loader since 5.6.1. If you upgrade using official channel, you won't be able to downgrade. If you follow the step below, root 5.6.1, update to 5.6.3 via FlashFire, it will leave the boot loader unchanged and allows you to downgrade if needed
3. Install ES File Explorer. Need to download the APK. Plug in the USB cable, copy the APK file, and use Documents app to file the file and install it.
4. Root.
4a. I first tried HD 10 (2017): Offline rooting. It's an offline process and does not transfer any of your data to internet (so less privacy concerns). It worked on the first try. However, I messed up the upgrade to 5.6.3.0 so I have to restore to stock 5.6.1.0. Then I could not get it to work. It either timed out or reported success but su is not found.
4b. I then went with KingoRoot. [TUT] ROOT HD 10 (7th Gen 2017) - EASY SuperSu (read this before 1st power on!). The rooting process stucked at 78% for a long time (5-10 min) but eventually succeeded
5. Disable OTA update. The instruction is in step 13 in [TUT] ROOT HD 10 (7th Gen 2017) - EASY SuperSu (read this before 1st power on!). I found out the Xposed installer requires internet, even though just briefly. So I decided it's better if I disable OTA.
6. Install Xposed & Flashfire. HD 10 (2017): Xposed, FlashFire, etc.. FF versions. (v0.24 or v.51) are attached in How to install Xposed & Flashfire for easy backups and ROM updates. In my experience, Xposed installer requires internet connection to install the framework. Otherwise you won't get the Official tab. I disabled WiFi once it's done.
6a. v0.51 did not work for me. It always crashes on start-up, regardless if I have time machine set
6b. v0.24 worked. retyre also mentioned it's more reliable in restore backup
7. Upgraded to 5.6.3 HD 10 (2017): Prerooted Xposed 5.6.3.0 image.
7a. I made a big mistake in the first attempt. I renamed the boot.gz and system.gz to .img file instead of extract the file inside the zip. FF accepted the file but generated error during the flash. After that, it got the Amazon bootloop. I had to restore the stock and restart from step 4
7b. Second time around, I put all the folder under /sdcard/FlashFire/Backups. Then I used restore function FF. This is safer and FF will check for md5sum and reject if the files are incorrect. This went through fine. The recovery step is at the bottom.
8. It's possible to disable OS update but continue to update Amazon packages. The instruction is in the second section in same link above How to enable Amazon packages (apk) updates but prevent the ROM updates (keeping root & rootable rom) This allows APK updates and install them in /data/app. The ROM in /system is not touched. It's a good way to stay current while not touching ROM (and keeping root!). Note the image flashed in step 7 already has this taken care of.
9. Install Google Play Store.
@bibikalka has provided the following (post #1)
Amazon Fire 5th Gen [SuperTool] Root, Google play install, block ota updates and more
Click to expand...
Click to collapse
Run this tool and choose the option to install Google.
Worked!
Here are some other candidates but I did not try them.
COMPLETELY 'GOOGLE-IZE' YOUR AMAZON FIRE TAB (Confirmed Working)
[GUIDE] Sideloading Google Apps - 100% WORKING! (ROOT)
https://www.howtogeek.com/232726/how-to-install-the-google-play-store-on-your-amazon-fire-tablet/
10. Change SuperSU to limit app which has root access. SuperSU access workaround for Fire devices. For me: After forced stop, the App tab will show the new app added without reboot. However, the new app does not take effect until reboot. And upon reboot, any app not yet installed will disappear from the App tab
11. Remove lock screen ad. Use the super tool again and worked! Amazon Fire 5th Gen [SuperTool] Root, Google play install, block ota updates and more
12. Replace launcher. New: Any Launcher, No Root (Launcher Hijack V3). It worked but the flicker is killing me. I then used Tips, Tricks, and the Root!. Move Nova to system app using Link2SD and disable Fire Launcher. Much better. Note the following from that thread. And there must be empty line at the bottom of build.prop
You should install Nova as a system app. Then you get the Google Now page without having to install another apk. If you are going to keep Fire Launcher, but leave it disabled, add this line to your build.prop, at the very bottom:
Code:
ro.HOME_APP_ADJ=1
Click to expand...
Click to collapse
13. [ROOT] Enable ALL Lock Screen Lock Options. You need the premium version of Activity Manager. In its settings, these options must be set: Show system app indicator (might be optional), Show not exported activities, Allow ROOT operations. In my experience, about 30% of time after reboot, the screen will loop between screen saver and black and never show the unlock pattern. I have disabled this function and went back to PIN. So I no longer recommend this step.
14. Disable bloatware. [GUIDE] Remove all bloatware from your Fire HD 10 (2017). This is written for 5.6.0. Updated: Amazon System App / Bloatware Tracking Sheet - as of FireOS 5.6.2.0. I did not find a thread for 5.6.3. Note the following 2 if you want to use them
My Account: com.amazon.kindle.otter.oobe
Backup & Restore: com.amazon.device.backup
15. Google Assistant. [GUIDE] [NO ROOT]: Activate FULL Google Assistant!.
Have to install specific version of Google App Google App 8.33.6.21 (arm-v7a) (nodpi) (Android 5.0+) and don't forget to disable auto-update in Play Store. Update: this is working. However, it's a bit sluggish. I have now uninstall Google Assistant.
---- Maybe Later: Other Optimization
Making The Most of Root on Fire Tablet 10 (tweaks/apps/modules/hacks/optimizations).
Appendix
A1. Recovery to stock ROM. The instruction is at Unbrick/Restore/Downgrade Stock Firmware [Amazon Fire HD 8 & HD 10]. This is written for the older version of Fire HD but the steps remain valid. The ROM is available from post 2 in [TUT] ROOT HD 10 (7th Gen 2017) - EASY SuperSu (read this before 1st power on!). I used the below
FireOS 5.6.1.0 (still rootable, but cannot be downgraded to anything earlier!)
update-kindle-40.6.0.5_user_605485120.bin
Click to expand...
Click to collapse

@redhonker
Hmm, must have been hours on XDA to compile this together
For your Google Play Store issue, there is an oldie but goodie - Amazon Fire 5th gen SuperTool. Works like a charm to install Play store on Fire HD 10! In fact, I stopped messing with the GAPPS flashing for Fires even when I have root, and just use this tool. Since 2015, for most tablets the underlying Android is still the same - Lollipop 5.1.1
https://forum.xda-developers.com/amazon-fire/development/amazon-fire-5th-gen-supertool-root-t3272695
https://www.rootjunky.com/

bibikalka said:
@redhonker
Hmm, must have been hours on XDA to compile this together
For your Google Play Store issue, there is an oldie but goodie - Amazon Fire 5th gen SuperTool. Works like a charm to install Play store on Fire HD 10! In fact, I stopped messing with the GAPPS flashing for Fires even when I have root, and just use this tool. Since 2015, for most tablets the underlying Android is still the same - Lollipop 5.1.1
https://forum.xda-developers.com/amazon-fire/development/amazon-fire-5th-gen-supertool-root-t3272695
https://www.rootjunky.com/
Click to expand...
Click to collapse
Thanks, I've added it to the first post. Will try that first.
The link you provided for rootjunky. What should I use from there? I can go to the section for Kindle Fire HD but I think it's the older model. I did own one before and I was able to install TWRP on it. But the 2017 model has no custom recovery available yet, right?

redhonker said:
Thanks, I've added it to the first post. Will try that first.
The link you provided for rootjunky. What should I use from there? I can go to the section for Kindle Fire HD but I think it's the older model. I did own one before and I was able to install TWRP on it. But the 2017 model has no custom recovery available yet, right?
Click to expand...
Click to collapse
Sorry, it was a bit confusing! You should be using this file (it's linked to in the XDA post):
http://rootjunkysdl.com/files/Amazon Fire 5th gen/SuperTool/AmazonFire5thGenSuperTool.zip
Once you unpack, you can start the bat script (under windows), and then it'll have option 2 which will install all Play Store components.

Thank you, this was helpful.. I have ordered a HD 10 as well and plan to do the same.
But, I'm confused on Step 2 and Step 4. In step 4, you say even the latest version can be rooted (which is my understanding as well), but in step 2 you say not to allow it to upgrade to the latest version.
Why not just do all the updates BEFORE rooting? Am I misunderstanding something?

wcarlson40 said:
Thank you, this was helpful.. I have ordered a HD 10 as well and plan to do the same.
But, I'm confused on Step 2 and Step 4. In step 4, you say even the latest version can be rooted (which is my understanding as well), but in step 2 you say not to allow it to upgrade to the latest version.
Why not just do all the updates BEFORE rooting? Am I misunderstanding something?
Click to expand...
Click to collapse
I updated step 2. It refers to anti-rollback so you can't downgrade OS version.
Others have recommended against upgrade first. Maybe Amazon just released a new update and you won't be able to root or downgrade. Practically, it probably won't really happen.

redhonker said:
I just ordered one. I have gathered the following information. Please correct me if there is anything incorrect.
.....
Click to expand...
Click to collapse
This is really great I just got mine yesterday and I was just going to root and remove Amazons stuff. You reminded me that it's probably best to back up something before you start messing with it. I'm used to having a recovery like twrp though, but oh well. I'm wondering what path you will take in regards to installing FF and Xposed and doing a backup. I'm reading your links (from retyre) and it's suggested that you do the backup before installing Xposed (I think) but with FF and SuperSu as system apps. Are u going to use the DD command for back up or just use the altered version FF. I'm just a little confused after reading this links and just wanted to get your thoughts. Incidentally what are you using file explorer for? I would think you can just push it to the tablet than install it alternatively I have a USB to microusb that I think I can mount usb. Thanks. Unless things have changed es file explorer is full of bloat I would suggest mix explorer

I have rooted and installed xposed. I installed google play store and titanium backups. I couldn't really figure out how to install flashfire. But I'm to scared to try to add any modules on xposed as I still can't figure out how to restore my titanium back up??
I haven't done any rooting in a long time, but as far as my memory goes, you make an update.zip file as your backup but you need a custom recover or something to to be able to flash it? like TWRP. is flashfire that equivalent?

@looney417
Yes the bootloader is locked, as of now I guess, and so there is no custom recovery. I do believe flash fire is the method being used for raw backups. One of the links in the first post refers to Retyres work and he also mentioned the Linux command DD to make a back up after you gain root. There is some creative work arounds and some hard work and experimentation done here I think we are benefitting from. I'm struggling with the order of operations here too but I've been playing with and rooting devices since the original Google phone Nexus one and you always try and get a good back up before you start messing around. The one big no-no right now is flashing an older version of the fire OS. This results in a hard brick bc Amazon instituted anti roll back measures in there boot loader.

Hello, I have just rooted my new Fire with the offline method, I have followed all the steps for the newbie listed here but I got stucked at 5) point,
I read couple of times the topics about flashfire and Xposed but I really can't understand some things:
What exactly is Flashfire? Is it an app? Do I need it to upgrade the system?
In order to work FF needs Xposed? Or not?
Why Xposed could be useful on this Fire HD 10?
Last question, in the FF and Xposed topic is written that I have to dd my img?! And then root again?!
I am so sorry for my disability.... Is there any other clear guide to install Xposed and Flashfire? And something that explain why these tools are useful and what aim they pursue
Thank you everyone for this great guides about fire HD btw

I have just purchased a fire HD 10, i am also wanting to root, and install gplay but haven't rooted for a while, i have actually asked Amazon for a return label as i was extremely dissapointed with the poxy adds for the screensaver/lockscreen! I wish Amazon would word things correctly! "With offers" = With ADDS!!! "Without offers" = "Without ADDS"
Other than paying Amazon £10! is there a way to remove them?? Very curious to find out.
Also has anyone had any issues with the brightness slightly fading in and out, ie brightness going up and down?? I have checked the settings, and adaptive brightness is on, however, the lighting in the room is constantly the same and never changes, i have kept it on a stand and monitored it, and it does fade in and out/up and down slightly. Its very odd.
Is this a bug within the OS?
I have even turned off the adaptive brightness and it still does the same?
Was just curious if anyone else had experienced this?
I would also like to remove the bottom nav bar as it is constantly there and really annoying!!
Is there a way to do this, i wish that black bar was transparent, i would then have an actual 10.1" tablet, not a 9.7" one!! Is there a way?
Looks like and Awesome guide, would love to get these issues sorted, and root, but not sure if my experience would be adequet?, some things are a little bit over my head.?

Logoutt said:
Hello, I have just rooted my new Fire with the offline method, I have followed all the steps for the newbie listed here but I got stucked at 5) point,
I read couple of times the topics about flashfire and Xposed but I really can't understand some things:
What exactly is Flashfire? Is it an app? Do I need it to upgrade the system?
In order to work FF needs Xposed? Or not?
Why Xposed could be useful on this Fire HD 10?
Last question, in the FF and Xposed topic is written that I have to dd my img?! And then root again?!
I am so sorry for my disability.... Is there any other clear guide to install Xposed and Flashfire? And something that explain why these tools are useful and what aim they pursue
Thank you everyone for this great guides about fire HD btw
Click to expand...
Click to collapse
I will give it a try before the experts weigh in.
FlashFire is an app. The 2017 Fire HD 10 has a locked bootloader and so far there is no way to install custom recovery. So FlashFire is the only way easy way to backup/upgrade OS.
FlashFire checks date to see when it's valid. If you use v0.24, you need to hack the date. My impression is v0.51 also needs it but I'm not certain. This can be done either by changing the system date or install Xposed with per-app-hack. This is covered in the linked post.
DD is an alternative. It's a command line. If you are comfortable with it, you don't need FF for backup.

bibikalka said:
Sorry, it was a bit confusing! You should be using this file (it's linked to in the XDA post):
http://rootjunkysdl.com/files/Amazon Fire 5th gen/SuperTool/AmazonFire5thGenSuperTool.zip
Once you unpack, you can start the bat script (under windows), and then it'll have option 2 which will install all Play Store components.
Click to expand...
Click to collapse
Sorry, one more question for you. If we use the FF v0.51 you provided, do we still need date hack? If not, will it work without Xposed?
Thanks

Is there any guide like this for the 8th Gen(2018) or does this apply?

Just wanted to ask again if there is a definative way to get rid of the bottom nav bar? Really hate that black bar that takes away a portion of the screen, would be really nice if there was a way that it could be made trasparent, and works with the fire 10.1 (2017) model. Also want to keep everything stock.

fleebleflam said:
I have just purchased a fire HD 10, i am also wanting to root, and install gplay but haven't rooted for a while, i have actually asked Amazon for a return label as i was extremely dissapointed with the poxy adds for the screensaver/lockscreen! I wish Amazon would word things correctly! "With offers" = With ADDS!!! "Without offers" = "Without ADDS"
Other than paying Amazon £10! is there a way to remove them?? Very curious to find out.
Click to expand...
Click to collapse
You can call Amazon, or start a web chat with them, and tell them this device is a gift for young child, and some of those ads shows on lock screen are not appropriate for kids. then they will remove all the lock screen ads for you. you also can go to your amazon account to unsbscribe those offers, it will cost you some money. or, you can find in here some guide to help you remove the ads in lock screen. good luck, mate!

28mufields said:
You can call Amazon, or start a web chat with them, and tell them this device is a gift for young child, and some of those ads shows on lock screen are not appropriate for kids. then they will remove all the lock screen ads for you. you also can go to your amazon account to unsbscribe those offers, it will cost you some money. or, you can find in here some guide to help you remove the ads in lock screen. good luck, mate!
Click to expand...
Click to collapse
I have been very fortunate to get the adds removed by Amazon, a manager gave me a courtesy call and said they would remove them for me for free!
So that's the adds sorted, i'm more concerned about the bottom nav bar its so frustrating just being there permanently! It's now a 9.7" tablet not a 10.1"!!
Is there a way to make it transparent, or to maybe swipe up from the bottom when you need it?
Any help with this would be greatly appreciated.?

playerpatrick said:
Is there any guide like this for the 8th Gen(2018) or does this apply?
Click to expand...
Click to collapse
If I search on Amazon, only the 2017 7th gen Fire HD 10 will show up. Where do you see the 8th Gen 2018?

There is no 8th gen 10.1" tablet. Amazon presently, only sell the 2017 10.1" model that is the latest one. I just purchased one last week, and i also thought there was a 2018 10.1" model. But there isn't until Amazon release another one.
The latest 2018 model is only the 8" model.

I have completed the setup of the tablet and updated the first post.

Related

RCA RCT6203W46 Pro10 Tablet: Catch-all Thread

Fellow Pro10 6203 users:
Welcome! As we do not yet have a forum dedicated to this device, I am creating this thread to serve as a means to share everything that I've come to discover about the usage of this inexpensive yet capable Android tablet. This thread will include varying topics such as rooting, custom recovery, accessories, customization apps, custom ROM's, and anything else I might come across that may enhance our experience with the product. I have found no real one-stop source for information concerning this device, so I am beginning this one that I hope everyone that owns one will find useful. Please feel free to ask questions and add constructive commentary
Tech Specs:
Model Number: RCT6203W46KB
Operating System: Android 4.4.2
CPU Chip: Quad Core
CPU Chipset Model Number: MTK MT8127 1.5GHz
GPU: Mali-450 MP
Resolution: 1024x600
Density: 160dpi
Screen Features: 10.1 Thin-film Transistor
RAM: 1GB
RAM Type: DDR3
Storage Capacity: 16GB
Camera: Yes (Front & Back)
Camera Specifications: Front Facing 0.3M pixel webcam (640x480), Rear 2M pixel webcam (1600x1200)
Battery Life: 6 hours
Battery Life Details: Playback downloaded video with WiFi turn off
Connectivity/Audio: Headphone jack, Micro USB, DC jack, Micro HDMI
Dimensions: 262(W)x165(H)x11.5(D)
Weight: 921g
Software: Walmart, Sam's Club, Vudu, eMusic, Kingsoft Office
Included Accessories: Power adapter, Keyboard Folio
If you happen to find something here worth your while, please hit the thanks button!
Rooting
Always remember, you root your device AT YOUR OWN RISK. Rooting will void your warranty and you may brick your device in attempting this. Its a choice and you're the only one who can make it.
Rooting instructions (tested up to RCA firmware 1.9.50):
(Beginning with a tablet never before rooted, or has been completely unrooted prior)
1. On your tablet, go to Settings > About tablet > Build number and tap the build number 7 times. This will unhide the Developer options menu.
2. Tap the Developer options menu. Enable it by sliding the slider to the right in top bar. Select "USB debugging" by placing a check mark in the box next to it.
3. Go to Settings > Security. Select "Unknown sources" by placing a check mark in the box next to it. Deselect "Verify apps" by removing the check mark in the box (you can enable it again afterwards if you wish).
4. Connect your tablet to PC via USB.
5. Download the Windows iRoot rooting application here.
6. Install the app.
7. Start iRoot and follow instructions to root. Remember to enable USB permissions on tablet when prompted.
8. Once successfully completed, download and install SuperSU from here to replace the Chinese root manager called Superuser 1.0.4.
9. Start SuperSU and you will be asked for permission, choose to allow.
10. SuperSU will prompt to install SU binary, go ahead with OK and install normally (not TWRP). IT IS VERY IMPORTANT TO INSTALL THE BINARY.
11. Once SuperSU is installed and the binary updated, you can uninstall Superuser 1.0.4 and the second app it installs, something like "Clean Master" (unless you want it).
Happiness is now achieved with having a rooted device
* For further details regarding root, please see "Rooting considerations" in the Misc. section below.
Custom Recovery
Always remember, you install a custom recovery on your device AT YOUR OWN RISK. Installing a custom recovery will void your warranty and you may brick your device in attempting this. Its a choice and you're the only one who can make it.
99% of the credit for this section goes to johnemc2, PatF and mexicandroid for creating and contributing to this thread. Although it was created for a different but similar RCA tablet model, they provided everything I am going to reiterate here. Also the original thread for TWRP on MediaTek devices (which is the chipset for these RCA tablets) is here, and all credit goes to yuweng for this. Make sure to hit the thanks button in the respective threads for these guys!
TWRP installation instructions (tested up to RCA firmware 1.9.50):
1. Device must be rooted. See rooting section above or use another method of your choice.
2. Download the TWRP recovery image for the 6203 from here. Rename it by deleting "[RCA 6203 TWRP - Remove this tag]" so that the file name reads only "recovery.img" (with no quotes of course).
3. Place this file on your external sdcard.
4. Download and install [ROOT] Rashr Flash Tool from here. If the app suggests updates, go ahead and install them.
5. Rashr will ask you to make a backup. If you try, it will fail. Not to worry too much though, a stock recovery image is available below.
6. Start Rashr. From the menu, tap Recovery from Storage. From the "Pick a file" menu select /storage/emulated. Select /storage/, then select sdcard1/. From there select the recovery.img file you saved in step 3.
7. It will give you a warning prompt asking if you are sure. If so, select "Yes please" to install TWRP.
8. Upon successful flashing of TWRP you will have the choice to boot into the custom recovery, go check it out!
9. One procedural maintenance item to perform after: I have noticed that the rashr app holds on to a large amount of data for some reason and haven't found the need. Once you reboot, you can go into Settings > Apps > All and find Rashr and clear data to reclaim the space.
Good guide for using TWRP can be found here.
How to manually get into recovery (TWRP or stock):
From a powered off state, simultaneously depress the power and volume up buttons until the white RCA boot screen appears. Once this screen appears, release the power button but REMAIN DEPRESSING THE VOLUME UP BUTTON until you are in recovery.
Stock recovery installation:
It is the exact same procedure as was with TWRP, with the exception of step 2. Instead download the stock recovery image from here, rename it by deleting "[RCA 6203 Stock Repacked - Remove this tag]" so that the file name reads only "recovery.img" (with no quotes of course). Continue on using step 3 above. Check out why you might need the stock recovery image in the "Firmware updating considerations" area of the Misc. section below.
Ultimate happiness and assurance is now achieved with having a custom recovery installed on your device to back it up!
Accessories
Here are some of the accessories I am currently using for the 6203:
Cases:
The keyboard case is good, but I found it cumbersome in most cases and unnecessary. So I purchased this case from Ebay. Here are some photos of mine. I have had it for 5+ months with no issue upon daily use.
Screen Protectors:
I purchased this anti-glare and anti-fingerprint screen protector from Amazon. Although they now have it for the 6203, at the time they only had them for the 6103 and I had to modify it. But 5 months later it is still great. Being anti-glare means there is a slight matte to them, but overall I found it hardly effected the clarity of the screen. It really kept having to wipe off the screen due to fingerprints to a minimum!
I am just sharing what I have found to work for our devices and hope it helps you too in some way!
Customization Apps
Customization apps that require root (seeing rooting section above):
Xposed Framework. Man is this awesome. Here is the description from the site: Xposed is a framework for modules that can change the behavior of the system and apps without touching any APKs. That's great because it means that modules can work for different versions and even ROMs without any changes (as long as the original code was not changed too much). It's also easy to undo. As all changes are done in the memory, you just need to deactivate the module and reboot to get your original system back. There are many other advantages, but here is just one more: Multiple modules can do changes to the same part of the system or app. With modified APKs, you to decide for one. No way to combine them, unless the author builds multiple APKs with different combinations. You can find version 2.6.1 for our tablet here (select "show older versions" at the bottom of the page).
GravityBox [KK]. TONS of customization for our device. Find it here.
Customization apps that do not require root:
Blacked out or inverted apps. I love darkened apps. I prefer a black or dark background to most apps. It looks good and is easier on the eyes! You can download the Team Blacked Out updater apk from here. You can download many popular apps that have been "blacked out" by this team.
I am just sharing these apps for fellow fans of customization. Enjoy!
Custom ROM's
[reserved]
Misc.
Rooting considerations:
Although there is a risk of bricking the device in doing so, to date I have rolled through both the 1.3.51 and 1.9.50 RCA updates without the update being hindered by having my device rooted prior (never unrooted), and I have not lost root once the update completes. Although I have not tried this without, I believe this may be because I use SuperSU Pro OTA survival. This app is not necessary, but the free version does not have the "OTA survival mode" that the pro version possesses. I recommend spending the $3.75 for purchase.
Firmware updating considerations:
If you delete any of the bloatware apps that comes preloaded (VUDU, Walmart, Sam's Club, Opera, etc.) and try to update the device, it will soft brick your tablet. This is because the update performs a core app comparison check to test validity prior to completing installation. You will only be able to get into stock recovery once this happens. Therefore my recommendation is not to delete any of these apps but instead use Titanium or MyBackup Pro to freeze them, and prior to attempting any firmware update remember to UNFREEZE THEM FIRST. This will save you any headache with the firmware updates.
I do not think you can install an official firmware update via TWRP, so you may need to reinstall the stock recovery to do this. See the "Custom Recovery" section above.
Misc. #2
[reserved]
One frustrating thing about our device is that some apps will not install from the Play store. It will state "this item is not compatible with your device". Well I have tried many methods to circumvent this, including changing prop files and using apps that fake screen densities. I don't recommend that . Instead I sideload. I use a Google Chrome extension called APK Downloader. You can get it here. To set up it will ask for devide ID info. I plug in the number for my S4. Once downloaded, I just copy the apk over to my tablet and install from there. The only caveat to this is that it does not work for purchased apps.
There are other ways to procure the app and sideload, but this is the method I use most often for the 6203.
I have a support request in to RCA for these concerns (here is the text as I sent):
Hello,
I have 3 questions. The first is that by reading the specs for this tablet the CPU is supposed to be set for 1.5Ghz. But when you use the tablet, it is only set for 1300Mhz (1.3Ghz) (I can provide screenshots). Which is wrong and why?
My second question is do we have any access to a complete firmware ROM that can be used via recovery? This would be nice to have in case the tablet is soft bricked for any reason. Update ROMs do not provide this.
Lastly, is there anywhere to download USB drivers for this tablet?
Thanks in advance for your help.
From RCA:
Glen (RCA Support)
Apr 27, 3:18 PM
1) The max threshold is 1.5Ghz. The reason it is running at 1.3 is probably because your not using its absolute full capacity
2) We dont have the ROM
3) Is this for the USB stick or memory stick?
Glen
Technical Support
#Madeforyourlifestyle
My response:
Glen,
Here are my responses:
1. I have attached 3 screenshots from independent apps that all report the CPU set for 1.3Ghz and not 1.5Ghz. In fact they show the governor as having the range for the CPU set to 598-1300mhz. I believe this happened in the firmware 1.9.50 update and was not the case prior. Can you check to see why this was done? We purchased tablets that were intending on having a 1.5Ghz processor.
2. You will see many returns then from tablets that were soft bricked due to the most recent update corrupting the system file, and then only allowing people to boot into recovery and not into Android.
3. No, USB drivers as in this explanation: http://developer.android.com/tools/extras/oem-usb.html
Thanks. I really appreciate your assistance with these questions. Please let me know if there is any other information I can offer.
From RCA 5/4/15:
Glen (RCA Support)
May 4, 3:43 PM
The tablet will use the 1.5Ghz only when it will take big update like firmware updates.
#Madeforyourlifestyle
My response:
Glen,
There is no way for the Android kernel to know only to use full CPU capability during an upgrade procedure. Its there for all operations or it is not.
Can I have my concern escalated to your engineering team? As I said previous, the system showed 1.5Ghz was available in processing speed before the last upgrade.
Thanks
From RCA 5-7-15:
Hello,
We'd love to hear what you think of our customer service. Please take a moment to answer one simple question by clicking either link below:
How would you rate the support you received?
Good, I'm satisfied
Bad, I'm unsatisfied
Conclusion:
So apparently RCA doesn't intend to do anything about the most recent update failures outside of performing RMA's for people, and also doesn't care to answer why these tabs are advertised as 1.5Ghz and are being throttled to 1.3.
Rct6203w46-android4.4.2-3101-v50-v1.3.71
What can I do with this or this - no ROM Backups, and an annoying 'brick' on my table?
I successfully rooted with KingRoot and tried to manually switch to SuperSU with a script I found.
The script seemed workable. I found all of the targets and: # root.sh ... oh *hi*
The transition failed and after trying to 'clean up' remnants the script seemed to have missed, the screen froze: RESET BUTTON - nothing, nothing, nothing.
I wish I hadn't believed it would work without a 'dd ... system.img'. The tablet had about 12hrs mileage and is now a very new [Black Friday] $49 item about to be smashed on the driveway.
I read somewhere that RCA will not be distributing winusb drivers.
*uc* it - i b-roke i-t! :victory:
It's Alive! After the battery drained, 2 weeks later, it booted!
removed supersu
probeafargavin said:
What can I do with this or this - no ROM Backups, and an annoying 'brick' on my table?
I successfully rooted with KingRoot and tried to manually switch to SuperSU with a script I found.
The script seemed workable. I found all of the targets and: # root.sh ... oh *hi*
The transition failed and after trying to 'clean up' remnants the script seemed to have missed, the screen froze: RESET BUTTON - nothing, nothing, nothing.
I wish I hadn't believed it would work without a 'dd ... system.img'. The tablet had about 12hrs mileage and is now a very new [Black Friday] $49 item about to be smashed on the driveway.
I read somewhere that RCA will not be distributing winusb drivers.
*uc* it - i b-roke i-t! :victory:
It's Alive! After the battery drained, 2 weeks later, it booted!
removed supersu
Click to expand...
Click to collapse
probeafargavin,
Sorry for slow reply. Been a busy month! I recommend sending the unit back to RCA for an RMA. I had to do this once and although it took a month, I received back a working tablet. It doesn't matter that you did this, they will not check. They will end up sending you back a refurbed tablet. Mine works fine.
-droidify
Needing Help
I rooted my device (same exact make/ model you have listed). Well it just so happens that now I am not able to open the Google App store. I have clicked the app logo so many times now and all what I see is what looks like the app is about to open but it just disappears about a half second later.
Looks like I am no longer able to use the back button also. I have tried factory resetting the device yet problem remains. Clearing cache of the Google Play app, no results. Please help!!!!! I would surely appreciate it, I'm sure you can imagine how devastated I am over this.
C_Cee said:
I rooted my device (same exact make/ model you have listed). Well it just so happens that now I am not able to open the Google App store. I have clicked the app logo so many times now and all what I see is what looks like the app is about to open but it just disappears about a half second later.
Looks like I am no longer able to use the back button also. I have tried factory resetting the device yet problem remains. Clearing cache of the Google Play app, no results. Please help!!!!! I would surely appreciate it, I'm sure you can imagine how devastated I am over this.
Click to expand...
Click to collapse
C_Cee unless you have TWRP installed and had a back up, there is not much you can do. I would RMA the tablet through RCA. I had to do this once and it was a pretty quick turn around.
-Droidify
RCT203W46L Questions
Hi,
I have just purchased the above and rooted it with Kingroot. This is the lollipop 5.0 version.
a) a stagefright detector from lookout reports this device is vulnerable to this hack. Any thoughts?
b) are the twrp and stock recovery images pointed to by droidify post #2 and #3 still usable? even though its lollipop5.0?
Any help appreciated before I mod this thing!!
Thanks
kwmike said:
Hi,
I have just purchased the above and rooted it with Kingroot. This is the lollipop 5.0 version.
a) a stagefright detector from lookout reports this device is vulnerable to this hack. Any thoughts?
b) are the twrp and stock recovery images pointed to by droidify post #2 and #3 still usable? even though its lollipop5.0?
Any help appreciated before I mod this thing!!
Thanks
Click to expand...
Click to collapse
Lollipop is going to have a different recovery, so what I posted likely will not work and may cause serious problems if attempted. Not sure about stagefright vulnerabilities.
Any advance?
No more advance in this device?
drakedalfa said:
No more advance in this device?
Click to expand...
Click to collapse
My tablet is still going. Although not my daily driver device, I use it to watch videos on break at work and to read on. There hasn't been any development for this device that I am aware of and unlikely to be considering it is not that popular.
Flashing recovery from build Build: RCT6303W87DK-ANDROID5.0-V63-V1.12.20-B
kwmike said:
Hi,
I have just purchased the above and rooted it with Kingroot. This is the lollipop 5.0 version.
a) a stagefright detector from lookout reports this device is vulnerable to this hack. Any thoughts?
b) are the twrp and stock recovery images pointed to by droidify post #2 and #3 still usable? even though its lollipop5.0?
Any help appreciated before I mod this thing!!
Thanks
Click to expand...
Click to collapse
Aloha -
I just received one of these today:
Model: RCT6303W87DK (32GB)
Android version: Lollipop 5.0.
Kernel: 3.10.54
Build: RCT6303W87DK-ANDROID5.0-V63-V1.12.20-B
I installed NewKingrootV4.62_C133_B233_en_release_2015_11_24_105203.apk downloaded from www\.kingroot\.net
On the first attempt, Kingroot rebooted at 22%, and failed to root. I repeated the procedure without rebooting, and achieved root on the second attempt.
I am curious to know if you flashed TWRP and, if so, what results you had.
Also: does anyone know if, in fact, the 5.0 loader actually is different from the 4.4.2 loader.
Thanks in advance.
I'm confused, is this thread on the RCA Pro 10 RCT6203W46KB or for it's successor (I assume) the RCA 10 Viking Pro RCT6303W87DK. I ask because I have the RCT6303W87DK and am looking to see if there are any ROMs for it, as I would prefer to be running Android 5.1.2 or 6.0 over 5.0.

Root on fire HD 10 - but no custom recovery or ROMs?

Can someone help me understand how we can have root methods for the HD 10, but no custom recovery or ROMs?
Any news or updates on the effort here? I'm willing to pay or donate to get it done!
I REALLY want to turn my tablet into an Android tablet... Not a fire tablet with an almost Android experience.
If we can get some one to create safestrap probably we can have a custom Rom !ade
There's no ROM(s) because root was just gained in December. So far as I know, no developers own a HD 10 (at least none that have said so) so no one is able to build one. I am willing to try, but unfortunately I don't have all the resources yet. There is no custom recovery because the bootloader is still locked (so far as I know). Its very hard, almost impossible to get a custom recovery on a locked device. Give it some more time. Maybe @ggow will surprise us.
DragonFire1024 said:
There's no ROM(s) because root was just gained in December. So far as I know, no developers own a HD 10 (at least none that have said so) so no one is able to build one. I am willing to try, but unfortunately I don't have all the resources yet. There is no custom recovery because the bootloader is still locked (so far as I know). Its very hard, almost impossible to get a custom recovery on a locked device. Give it some more time. Maybe @ggow will surprise us.
Click to expand...
Click to collapse
I have a 'maybe dumb' problem, because we only can flash with FlashFire.
Months ago, I owned a Samsung Galaxy Core Prime. I tried to compile Oreo for it. But, what happened to me is, before I get the ROM to BOOT, I compiled it exactly 17 times, fixing bugs. I never had a problem because I had the TWRP handy, but in this case we will not have a custom recovery at all. If the ROM fails to boot, we'll have to sideload stock ROM. Sideloading stock 17 times... doesn't it look tedious? From my experience, any developer no matter how clever he is, will have to compile at least 10 or so times before getting the ROM to boot???
Thanks!
Supersonic27543 said:
I have a 'maybe dumb' problem, because we only can flash with FlashFire.
Months ago, I owned a Samsung Galaxy Core Prime. I tried to compile Oreo for it. But, what happened to me is, before I get the ROM to BOOT, I compiled it exactly 17 times, fixing bugs. I never had a problem because I had the TWRP handy, but in this case we will not have a custom recovery at all. If the ROM fails to boot, we'll have to sideload stock ROM. Sideloading stock 17 times... doesn't it look tedious? From my experience, any developer no matter how clever he is, will have to compile at least 10 or so times before getting the ROM to boot???
Thanks!
Click to expand...
Click to collapse
To be honest, FireOS is pretty awesome with root and debloated. I've not had a single problem debloating, and I'm still going lol.
DragonFire1024 said:
To be honest, FireOS is pretty awesome with root and debloated. I've not had a single problem debloating, and I'm still going lol.
Click to expand...
Click to collapse
Hi! I pretty much agree with you. But you never know what it can do until you flash stock Android.
Thanks!
Supersonic27543 said:
Hi! I pretty much agree with you. But you never know what it can do until you flash stock Android.
Thanks!
Click to expand...
Click to collapse
That's one of my projects
DragonFire1024 said:
To be honest, FireOS is pretty awesome with root and debloated. I've not had a single problem debloating, and I'm still going lol.
Click to expand...
Click to collapse
Could be that I don't know how to solve the problems I have, but for me not all the Google play applications I want (for my kid) work. Issues vary from validating my authorized purchase to core functionality of applications not working. Some of the applications refer to Android os content and services that either aren't in fire os, are named differently, or have different functionality.
Not to mention that I dislike my son's user experience... He's only 3, quite smart but I've not been able to strike a good balance of protecting him and allowing him to actually use his tablet without learning wierd tricks to access Google play apps.
I'm ok if I have to stay on Fire Os if I can have complete control over profiles, launchers and have a genuine experience using my Google Play applications. Some of the FreeTime stuff is ok... My son might like some of it. But more importantly I want him to have the far superior applications on Google Play which are not currently available on Fire.
I'm willing to contribute to get a custom rom on the fire 10.
I really want to compile one, my skills are getting blunt without some compiling, but it turns out that I only have a HD 8.
Can someone please educate me on getting the GPS to work with google maps, like my phone? My HD 10 7th gen is rooted w/supersu. I have xposed and flashfire installed.
Is a custom ROM really required for this? I tried GPS tethering over hotpot but even that didn't work properly. I wish Amazon had their own proper NAV app to use the GPS chip, could be a bonus to being a prime member.
kferling said:
Can someone please educate me on getting the GPS to work with google maps, naively like my phone? My HD 10 7th gen is rooted w/supersu. I have Xposed and flashfire installed.
Is a custom ROM really required for this? I tried GPS tethering over hotpot but even that didn't work properly. I wish Amazon had their own proper NAV app to use the GPS chip, could be a bonus to being a prime member.
Click to expand...
Click to collapse
Clear data of 4 Google apps. Uninstall and reboot. Make sure nothing of the apps are left in /data/data. If so, delete folders and reboot. When booted again, toggle off location services for about 30 seconds and turn it back on. Then install the 4 APKs in this exact order: gfs_login, gfs, gms, vending. After install wait about a minute or two and reboot then log in. Wait several minutes, watching the two desktop icons. When they flash, the apps have updated. Go to location services and it might be turned off. If so, turn it on and press accept/yes for ALL OPTIONS. If it's turned on, toggle it off for 30 seconds then turn it on and again accept/yes all boxes that appear.
Sent from my Galaxy S4 using XDA Labs
DragonFire1024 said:
Clear data of 4 Google apps. Uninstall and reboot. Make sure nothing of the apps are left in /data/data. If so, delete folders and reboot. When booted again, toggle off location services for about 30 seconds and turn it back on. Then install the 4 APKs in this exact order: gfs_login, gfs, gms, vending. After install wait about a minute or two and reboot then log in. Wait several minutes, watching the two desktop icons. When they flash, the apps have updated. Go to location services and it might be turned off. If so, turn it on and press accept/yes for ALL OPTIONS. If it's turned on, toggle it off for 30 seconds then turn it on and again accept/yes all boxes that appear.
Click to expand...
Click to collapse
Thanks, although I did not get location prompts at the end. :/
Data was wiped for all 4, and uninstalled. rebooted and verified no data with ES.
Installed google apks in the exact order, waited 2 minutes, rebooted, then logged into playstore.
Went to home screen, saw apps flash after waiting. Went to location services (was off) turned on and no prompts
Turned off, waited 30 secs, turned back on, still no prompts.
Is this any different from your guide here?
Step 6. states "Once all the APKs are installed, open the Play Store and sign into your account and IMMEDIATELY go to settings and TURN OFF auto-updates. "
Perhaps that's what I need to do?
Just ordered an HD10, will this tutorial still work? https://forum.xda-developers.com/hd...7-root-box-t3726443/post75187398#post75187398
Will that debloat Fire OS also?
So I've figured out numerous things that get this closer to a custom rom. I just want to report my progress. As I'm working to get my PC in a good enough shape to run Windows and Linux again, I can't compile from source yet. my biggest issue is space. I need to free a lot up. But that doesn't mean anything.
I have been able to track down a lot of useful old school tools here on XDA. The amount of resources that exist on this site never cease to amaze me. Given what I've been doing to these tablets (the resources are old, 2012 onward), I kept looking in that era for tools to assist in getting us to a rom. In the past week I've been able to do these things, with success but have not tested a rom yet. Amazon has had it a bit more difficult with this device.
- Successfully deodexed the stock ROM 5.6.1.0. This was very easy to do...once I found tool that was compatible with deodexing Lollipop. Apparently it not easy to do.
- Successful library integration and editing of a stock AOSP Gallery3d apk. Fully 100% operational and full picture editing availability. Combine my wallpaper discovery, Amazon Photos is no longer required as a wallpaper or gallery source.
- Successfully addition of other surprises
- Figured out how Amazon restocks the ROM on a reflash. In the update.bin is a .dat file. When compiled, produces the system files in whole fresh stock. This can be edited then recompiled back into a system.img or can be used to build a ROM .zip style. That also means once I can build from source, a real ROM can be built.
- Will be pre-rooted with busy box.
- Viper4Android
- Ad blocking from open source free ware.
- Includes my framework and Settings mods.
Any questions please feel free to ask.
Have a new 2015 HD 10. Will definitely be following your progress
FuNKSioN said:
Have a new 2015 HD 10. Will definitely be following your progress
Click to expand...
Click to collapse
Or a severe lack of progress...
I have been at it for hours and hours and I am no closer than I was when I made my last post. I've looked at dozens of updater-scripts and the mount points are no different than the Fire 7, but it just won't flash a zip and when the rare chance comes along that the zip does flash, booting doesn't get past the white Amazon logo (first power on logo). I finally managed to get nearly all of the script right, and now when I add assert getprop for device ID verification, it rejects it despite the fields being properly filled out. I'm not giving up, I just need to figure out why.
On a side note, I have been able to do a switcheroo on the system, sorta. In trying to further mod the settings apk, I have been able to use a settings apk from an AOSP rom to replace FireTabletSettings. There is a trick...uninstall the stock FireTabletSettings APK, wipe the caches and dalvik, and took a resigned AOSP settings apk (test key signed), installed it as a user app then converted it to a system app. It installs fine, but I can only get half of it to work. I haven't tried with the framework or systemUI yet because I haven't been successful with the settings.
Back to the drawing boards...
Sent from my Galaxy S4 using XDA Labs
DragonFire1024 said:
Or a severe lack of progress...
I have been at it for hours and hours and I am no closer than I was when I made my last post. I've looked at dozens of updater-scripts and the mount points are no different than the Fire 7, but it just won't flash a zip and when the rare chance comes along that the zip does flash, booting doesn't get past the white Amazon logo (first power on logo). I finally managed to get nearly all of the script right, and now when I add assert getprop for device ID verification, it rejects it despite the fields being properly filled out. I'm not giving up, I just need to figure out why.
On a side note, I have been able to do a switcheroo on the system, sorta. In trying to further mod the settings apk, I have been able to use a settings apk from an AOSP rom to replace FireTabletSettings. There is a trick...uninstall the stock FireTabletSettings APK, wipe the caches and dalvik, and took a resigned AOSP settings apk (test key signed), installed it as a user app then converted it to a system app. It installs fine, but I can only get half of it to work. I haven't tried with the framework or systemUI yet because I haven't been successful with the settings.
Back to the drawing boards...
Click to expand...
Click to collapse
Try digging in files. I guarantee that Amazon took a very similar approach as Samsung did, requiring you to flash a break encryption zip.
I would try to help, as I've made several AOSP roms, but that was when Android 4.4 was the newest and you could compile it with 4 gb of ram.
Once I upgrade or get a new PC, I will most definitely install Linux, and try to help this forum.
---------- Post added at 06:31 AM ---------- Previous post was at 06:26 AM ----------
DragonFire1024 said:
Or a severe lack of progress...
I have been at it for hours and hours and I am no closer than I was when I made my last post. I've looked at dozens of updater-scripts and the mount points are no different than the Fire 7, but it just won't flash a zip and when the rare chance comes along that the zip does flash, booting doesn't get past the white Amazon logo (first power on logo). I finally managed to get nearly all of the script right, and now when I add assert getprop for device ID verification, it rejects it despite the fields being properly filled out. I'm not giving up, I just need to figure out why.
On a side note, I have been able to do a switcheroo on the system, sorta. In trying to further mod the settings apk, I have been able to use a settings apk from an AOSP rom to replace FireTabletSettings. There is a trick...uninstall the stock FireTabletSettings APK, wipe the caches and dalvik, and took a resigned AOSP settings apk (test key signed), installed it as a user app then converted it to a system app. It installs fine, but I can only get half of it to work. I haven't tried with the framework or systemUI yet because I haven't been successful with the settings.
Back to the drawing boards...
Click to expand...
Click to collapse
Haven't been up-to-date.
Do we have TWRP? If not how are you flashing the files?
I'd be open to porting TWRP to the HD 10 and maybe the 8 if we needed.
Reason being TWRP backups can be converted to a flashable .zip file, meaning that once you've gotten all the AOSP apps working (settings, gallery, etc) you could theme it, debloat it, deodex it, and everything else then save it and convert it to a zip. Would save people the time of doing it, and would be one step forward.
TechNash said:
Try digging in files. I guarantee that Amazon took a very similar approach as Samsung did, requiring you to flash a break encryption zip.
I would try to help, as I've made several AOSP roms, but that was when Android 4.4 was the newest and you could compile it with 4 gb of ram.
Once I upgrade or get a new PC, I will most definitely install Linux, and try to help this forum.
---------- Post added at 06:31 AM ---------- Previous post was at 06:26 AM ----------
Haven't been up-to-date.
Do we have TWRP? If not how are you flashing the files?
I'd be open to porting TWRP to the HD 10 and maybe the 8 if we needed.
Reason being TWRP backups can be converted to a flashable .zip file, meaning that once you've gotten all the AOSP apps working (settings, gallery, etc) you could theme it, debloat it, deodex it, and everything else then save it and convert it to a zip. Would save people the time of doing it, and would be one step forward.
Click to expand...
Click to collapse
Not sure about the encryption. It has to be a script problem, or the system partition won't accept zips and that's the barrier. However if I just flash the system directory instead, everything works fine. I can flash stuff into it just fine that way, but seems any time I go the way of the partition, I can't win. Flashing your own system image works too. However I haven't been able to get one to flash if I modify it. So I can decompile a system.img add to it, remove items and recompile it and it won't flash.
I am using flash fire to flash zips. We still have a locked bootloader so twrp isn't a likely option.
Sent from my Galaxy S4 using XDA Labs
DragonFire1024 said:
So I've figured out numerous things that get this closer to a custom rom. I just want to report my progress. As I'm working to get my PC in a good enough shape to run Windows and Linux again, I can't compile from source yet. my biggest issue is space. I need to free a lot up. But that doesn't mean anything.
I have been able to track down a lot of useful old school tools here on XDA. The amount of resources that exist on this site never cease to amaze me. Given what I've been doing to these tablets (the resources are old, 2012 onward), I kept looking in that era for tools to assist in getting us to a rom. In the past week I've been able to do these things, with success but have not tested a rom yet. Amazon has had it a bit more difficult with this device.
- Successfully deodexed the stock ROM 5.6.1.0. This was very easy to do...once I found tool that was compatible with deodexing Lollipop. Apparently it not easy to do.
- Successful library integration and editing of a stock AOSP Gallery3d apk. Fully 100% operational and full picture editing availability. Combine my wallpaper discovery, Amazon Photos is no longer required as a wallpaper or gallery source.
- Successfully addition of other surprises
- Figured out how Amazon restocks the ROM on a reflash. In the update.bin is a .dat file. When compiled, produces the system files in whole fresh stock. This can be edited then recompiled back into a system.img or can be used to build a ROM .zip style. That also means once I can build from source, a real ROM can be built.
- Will be pre-rooted with busy box.
- Viper4Android
- Ad blocking from open source free ware.
- Includes my framework and Settings mods.
Any questions please feel free to ask.
Click to expand...
Click to collapse
I mean, if PC performance is an issue I can give you access to a brand new xeon if it means there will be a custom ROM out.
Been thinking about buying the Fire HD 10 this black Friday and flash the Amazon garbage out, and was amazed to see none exist even though it has been a year since they figured out the rooting.
This will be an outstanding value if it was possible...

[Mod]Fortnite Galaxy Skin (Samsung Device)

***Please excuse the current limited details as I'm on mobile and not at pc yet. Will post more details bout version used and bulid.prop***
++++I'm no expert and when you do this you WILL get alot of force closes! Also network will not work, YOU MUST use WiFi! This is only to get your skin and then flash back to your preferred rom+++++
××××To verify after first boot that the modifications worked, check under settings and you should have an S-pen option now. Also if you press the power button it Should say Tablet and not phone.××××
So the Galaxy Skin redemption period is almost over, and as I promised I would release the method I used to redeem the skin on S8+ (g955u) devices. This may work for other devices, your results may vary. I have used this method on about 10 G955u devices and has worked everytime and I don't know anyone else doing this method.
Looking at the specs between the Tab S4 and the G955U they both use the 835 so that's why I chose this device to try and get it to work since they were more similar.
The steps in this guide are gonna be specific to the U variants since the Bootloaders are locked, so ways of altering the system are different than bl unlocked devices (aka exynos), but making the changes im doing on your device might work. I have no exynos variant to test.
**proceed at your own risk. You will be doing alot of flashing for the Rom. This is required to enter and exit safestrap. **
Required:
-T830 (Tab S4) Oreo AP Image (Need System Folder)
AP_T830XXU1ARGH - Version I used
-G955U Oreo Safestrap (These have Locked BL/No root on Oreo so we need safestrap mod system)
1:
Download a T830 Oreo Rom and get the system folder from the AP.Tar (I'll post my exact version once at PC)
2:
Modify the System folder, we want to delete some stuff to try and keep use from not booting due to incompatibility. The only folders we need are:
App/Bin/Etc/Framework/Lib/Lib64/priv-app/build.prop
3:
Now we want to flash our device with Oreo, and before boot modify the system. For U variants get the Oreo Safestrap build. After flashing the Rom, immediately follow the steps to boot into safestrap!!! We do not want to regular boot!!
4:
Copy over your folders to internal or an sd card for flashing in safestrap. Using any method you want you want to copy and overwrite the files on your phone. I do this in the command line but you can do it graphically but will take much longer. Lastly, copy over the build.prop attached at the bottom; setup is disabled because phone would never allow me to go through it and would lock up.
5:
After you have flashed over the files and the build.prop, you need to flash the device out of safestrap and proceed with a normal boot. This is SLOW don't panic, you should immediately be on home screen with a couple of force closes.
***You must do the following using Samsung Apps only!****
6:
Start the Galaxy App Store it should update. Note: if you can't see the app store, this happened to me a few times. Go to settings>accounts>Samsung and sign in. After you sign in click the apps option and then it should update.
You MUST have the current version of app store!
7:
Inside Galaxy Apps, make sure Samsung Billing is up-to-date. If you can't find it to update don't worry. There is a method in another step were we verify it's updated that will update it as well.
8:
Install the fortnite installer through Galaxy Apps! Doing any other install method will keep you from getting skin! You should get a pop-up about getting the skin.
9:
After fortnite is installed and running, DO NOT START A GAME!!!!!! Go to the STORE!! Not skins but the store where you buy V-Bucks!!!
10:
Click to buy any pack of bucks, were not buying anything here. It will most likely ask you to sign-up. Sign in using your Samsung account. You will get 1 of 2 messages. 1 saying you need to update Samsung Billing OR a message asking you how you would like to pay.
You need to get to the point where it asks for your payment method. If you are not getting Samsung, go to settings and there should be an option for Payment that allows you to change to Samsung
11:
Now everything is verified and setup, play 3 games and should have your skin in about 12-24 hours. All of mine took about 12-16 hours to appear.
Note: The first time I did this the skin did not show up on my phone after the time period. I logged into the account on my Xbox and got the redemption message, but the others did redeem on phone. So if after 24 hours if you don't have it login to another platform.
I had actually wrote this guide about 5 days ago but when I was posting it got deleted and I got frustrated. I will try and get the files uploaded so it's an easier process, I just wanted to get this up quickly as skins can't be redeemed after March 7!!

[debloat-ROM] Back Bacon UI one ui for Canada, eh? SM-A530W October Release

October release is available with or without root
Made a few changes as far as adding in some apk's to hopefully make it stable for everyone.
Besides that, the usual with normal default font BUT lots more choices in the font section.
Enjoy!
*if anyone has solid reasons to remove any apk files i've put back please let me know as some I should not have been removing and others... not so sure
I will no longer be able to provide new copies of this after the October security patch. I no longer own an A8 2018 and without a device to test the work, I do not feel it is appropriate to continue the project. I'd like to thank everyone that participated and I hope you enjoyed using it! If anything changes in the future that will allow me to provide the latest edited firmware, I will definitely be providing it here for you. I am using an S7 now so if you own one and like this work, there shall be downloads available there similar to this one. (Already testing).
Anyone that would like to continue on their own or have access to files used in making it I will try to include as much as possible from the link provided below by the end of October. There is currently a slightly outdated set of files and instructions (from June I believe) on how I made it already available.
Thanks Again!
Oct Security patch zip ready for download
Available with or without root AND with or without exo font - also an attempt to allow printing feature version. "Attempt" meaning I've placed a set of apk files into a separate and clearly labelled zip on the main download page that may allow proper use of the feature which has not been validated as operational by me or any other user. The "print fix" zip is rooted with exo font
This was made ONLY for the SM-A530W! Please do not use if not W (Canadian) variant. Check your phone info before attempting to flash
All ROMS/extras here:
https://drive.google.com/drive/folders/12Vwzn1CxNdT-ISsrOnSL4D353Nr14iRb?usp=sharing
The ROM will function very well and does not require any special patches, kernels, etc except obviously TWRP
Any additional issues you face with added mods most likely will need to be addressed with the creator
*Built by Superr's Kitchen*
Over 100 apps removed
***Find my mobile and pop-up asking to store lockscreen info removed- BE AWARE reduced ability to locate lost device!***
retro shutdown qmg
Overloaded notifications and ringtones
Oreo Weather (pie weather is a serious downgrade)
August Security release
FM tuner and App Lock (Next Radio may now be used starting from July 2019). Gee, THANKS SAMMY! What took you so long? Was it the polar bears?
Goofy selfie stickers that are funny... and creepy *big thanks to hadesRom genius Corsicanu for the find*
Other typical CSC changes
If your plan has wifi calling, turn it on/off once in phone settings to "break in" the qs tile
Dedicated Screen Recorder access in launcher with no shortcut style appearance (if deleted may be re-enabled with activity launcher as shortcut)
Chrome can be safely disabled at any time if desired and auto replaced with system webview
dm-verity + force encrypt already removed
Magisk rooted
Installation is easy as pie
BACK UP FIRST!
Wipe caches, data, system. Internal may be safely wiped and give the "freshest" install but is optional. Then flash away.
Once flash completes, just reboot.
-*Usage*-
You are free to use any ideas/changes included in the zip. In fact, I encourage you to do so. I've mostly pieced together work from other very difficult projects to create this. Nobody has asked me to add, remove or alter anything contained within this page or in shared downloads. Their work is everywhere and it's what made this possible.
Built with Superr's Kitchen
Some screens to sample below. yay
nobody home
empty
I followed your instructions. I was already updated to pie previous to flashing your rom. I am not able to get root. Any ideas why. I also have the Canadian version. Good job on the Rom, I like it. I wish I could get root.
Ok. I can't really suggest anything other than the obvious.
But you've let it boot once before trying, and are adding the apk as well after flashing magisk in twrp?
Hard to figure that one out. If you're using Magisk, i am assuming.
burnt_31 said:
I followed your instructions. I was already updated to pie previous to flashing your rom. I am not able to get root. Any ideas why. I also have the Canadian version. Good job on the Rom, I like it. I wish I could get root.
Click to expand...
Click to collapse
Have you tried 19.1 you may need to flash twice.
I used magisk 19.1. First I used supersu and magisk uninstaller first. I have root now. Thanks for your help. It amazes me that sometime we over look the simplest thing.
burnt_31 said:
I used magisk 19.1. First I used supersu and magisk uninstaller first. I have root now. Thanks for your help. It amazes me that sometime we over look the simplest thing.
Click to expand...
Click to collapse
I know exactly what you mean. I do it all the time.
Nice you got it going. It's pretty lame if you don't root this. I just cut it up and added a couple things and they can be taken out, except radio and the recorder.
Curious if i got it right. If you're on anything other than VMC, is call recording and other micro features working? All the cscfeature xml files are decrypted so you can see what was done.
Everything seems to be working. I appreciate the work, Canadians are usually the last to get Roms. Most are made for the sm-a530f model. I was using the wrong method. One post said about waiting 166 hrs to reboot your phone after zipping RMM_State Bypass etc. etc.. Your way is simple. Once I get a chance I wlll have a look at what you have done, I work long hours. And as you said, what is the point if you cant root. Thanks again.
burnt_31 said:
Everything seems to be working. I appreciate the work, Canadians are usually the last to get Roms. Most are made for the sm-a530f model. I was using the wrong method. One post said about waiting 166 hrs to reboot your phone after zipping RMM_State Bypass etc. etc.. Your way is simple. Once I get a chance I wlll have a look at what you have done, I work long hours. And as you said, what is the point if you cant root. Thanks again.
Click to expand...
Click to collapse
It is 168 hours no reboots and rmm did work that rmm was for Oreo.
I think his would be fine but no guarantees.
Custom kernel 2.0 flash twice.
Light rom works without issue make sure you flash magisk.
Hello I have a530f model with lastest pie version for Russia. I would like to install native screen recorder. Can yo help me ? Please. My email is [email protected]. thanks
fabian_barrios said:
Hello I have a530f model with lastest pie version for Russia. I would like to install native screen recorder. Can yo help me ? Please. My email is [email protected]. thanks
Click to expand...
Click to collapse
Yeah bud. If you unzip the attached file, you can place it in /system/priv-app/ and make sure the permissions are set correctly for the folder and apk. Compare with other apps in the directoty and make it the same.
Then get the activity launcher app from the play store. Use that to make a link for it.
Getting random freezes sometimes, have to reboot phone using hardware buttons. Using Freedom A8
boominboodhoo said:
Getting random freezes sometimes, have to reboot phone using hardware buttons. Using Freedom A8
Click to expand...
Click to collapse
okay thanks for that. It is probably from my csc edits. I can adjust for freedom and hope it makes a difference.
Anything else to mention about it? What you did before flashing, are you using latest twrp, root or non root.... anything at all
no-verity... favourite snack... p.i.n. number(s)... oops sorry not the last two. My mistake. TOO MUCH info. Disregard.
Do a search on xda for rooting your model for the correct version of twrp. U will need no verify no encript. I used the latest Magisk to root. Supersu did not work. I used twrp for the A8 plus and had problems. Get the right one. It's a great rom. https://www.google.com/amp/s/forum....ery-twrp-3-2-2-0-galaxy-a8-2018-t3818201/amp/
I am looking at the csc for FMC and it appears i have doubled an entry. I need to go over all of them to see if i've done it elsewhere. I will have 2 updated ones hopefully late tonight. (Takes forever to upload).
Not sure if that is the cause but i will definitely adjust it.
Quick question in regards to your Rom. I been using it for a while now. Its the best one I can find, I did post a few times at the start. By any chance, did u get adoptable storage working? I know Samsung removed it in Pie. I tried root essentials but still no luck. Thus is not my first time rooting or installing roms. I started with the HTC 1. Lol. So far, u have the best rom for the A8 2018. Its nice and clean. Almost compares with lineage in my opinion. Thanks again. And by the way, I am Canadian.
Thanks
Hey i appreciate the gesture but even though i "made" this, i did it because of other people. SuperR is an invaluable tool. Then you got magisk, the twrp recovery and heck even give ol' Sammy some credit, haha. All i did was spend time learning everything from this site. I can't stress that enough. I still have not paid for superR and i am going to see how i can right after this.
ANYWAY!
Your question. I've never attempted it but i am very certain there's a magisk module that'll do it.
It involved formatting sd to ext 4 or 3. So i will get on it. Got a few 64 gig cards to spare. If you have a computer, grab the superR linux distro. I've run it on 32 bit machines. K... pay superr... adopt a card heheh.
I will look again in the magisk module section. And I give everybody right now credit for all their hard work and sharing it amongst all of us. Thank you. Thank you. I love modding my phones and I could not do it without everybody's help. All my PC's are 64bit.
Nice. If you need any help just ask. Just bought the kitchen.
I'll have something very soon. Mexico's pie has the classic csc folder of old. I think we should unify with some fiesta pie zip ui sorta thingy... um rom.

What should I know about old tablets?

I'm about to buy an old tablet - probably a kindle fire of some sort but I'm not sure yet. I was told by a store worker at a gadget shop that old tablets have some kind of "update block" meaning they can't be updated anymore or something. I don't remember the details but he seemed to be saying you can't download newer apps on the old devices or something. I can go back and ask for more details but I am just hoping that someone here knows what I am talking about and can fill me in on what I need to know before buying an old tablet?
I have hacked devices before (e.g. my sony psp way back or my ps3) and don't really mind rooting/jailbreaking a device, as long as it isn't too time-consuming. I basically just want an android tablet that can run new and old apps etc. Nothing fancy. Just a basic device for apps that I might need from time to time as well as using it while on the go for internet etc.
Each app gets compiled to be run on specific Android versions.: It's the app developer who defines the minimum and the maximum Android version his app can run on. So it's obvious not all apps are backwards-compatible.
jwoegerbauer said:
Each app gets compiled to be run on specific Android versions.: It's the app developer who defines the minimum and the maximum Android version his app can run on. So it's obvious not all apps are backwards-compatible.
Click to expand...
Click to collapse
I did not know that, very interesting. So what is the "update block" or whatever it is that the store person was telling me about and how does one overcome it? I know old androids only update "firmware" to a certain point, right? What happens after that? How do I run apps that are compiled to run on newer versions?
Thanks
Don't know what the store person had in mind. True is that an update is a patch for an existing Android version - what gets rolled out by OEM / carrier if they deem it necessary - whereas an upgrade is a complete replacement of an existing Android version by a higher version ( e.g. Android 4 -> Android 5 ) - what is never rolled out by OEM / carrier.
What you need is an upgrade. Because OEM / carrier certainly don't offer one you have to install a Custom ROM that matches the old tablet's hardware specs, what in turn requires you before install a Custom Recovery that is suitable to the tablet.
jwoegerbauer said:
Don't know what the store person had in mind. True is that an update is a patch for an existing Android version - what gets rolled out by OEM / carrier if they deem it necessary - whereas an upgrade is a complete replacement of an existing Android version by a higher version ( e.g. Android 4 -> Android 5 ) - what is never rolled out by OEM / carrier.
What you need is an upgrade. Because OEM / carrier certainly don't offer one you have to install a Custom ROM that matches the old tablet's hardware specs, what in turn requires you before install a Custom Recovery that is suitable to the tablet.
Click to expand...
Click to collapse
Right, so if I've done my (light) research correctly it would go something like this for a kindle fire HD, right? :
1. Root
2. Install android somehow
3. Upgrade the android to latest version
This is after very quick research I did on transforming a kindle fire HD to an android tablet so apologies if it doesn't make sense.
Assuming it does though, is root really necessary or can one go directly from kindle --> android? Also will step 3 already give the latest android version or is an upgrade usually needed (or would it just depend on how you actually do step 2?)
Thanks!
arkiltk said:
Right, so if I've done my (light) research correctly it would go something like this for a kindle fire HD, right? :
1. Root
2. Install android somehow
3. Upgrade the android to latest version
This is after very quick research I did on transforming a kindle fire HD to an android tablet so apologies if it doesn't make sense.
Assuming it does though, is root really necessary or can one go directly from kindle --> android? Also will step 3 already give the latest android version or is an upgrade usually needed (or would it just depend on how you actually do step 2?)
Thanks!
Click to expand...
Click to collapse
Which Kindle Fire HD were you looking at?
arkiltk said:
Right, so if I've done my (light) research correctly it would go something like this for a kindle fire HD, right? :
1. Root
2. Install android somehow
3. Upgrade the android to latest version
This is after very quick research I did on transforming a kindle fire HD to an android tablet so apologies if it doesn't make sense.
Assuming it does though, is root really necessary or can one go directly from kindle --> android? Also will step 3 already give the latest android version or is an upgrade usually needed (or would it just depend on how you actually do step 2?)
Thanks!
Click to expand...
Click to collapse
It's NOT needed to root Android.
To flash a Custom Recovery like TWRP it's only needed that device's bootloader got unlocked before.
Look inside here:
How to Install TWRP Recovery on Android without Root - Make Tech Easier
TWRP allows the user to install, backup, and restore firmware on an Android device. Here's how to install TWRP on Android without rooting.
www.maketecheasier.com
EonOfBlack said:
Which Kindle Fire HD were you looking at?
Click to expand...
Click to collapse
Not sure yet but it seems like the shop has a lot of variety within my budget from kindle fire HD 2012 to kindle fire 7" 2015 5th gen. It also has a handful of other brands within my budget: google nexus, acer iconia, lenovo smarttab, generic android tablets, etc.
jwoegerbauer said:
It's NOT needed to root Android.
To flash a Custom Recovery like TWRP it's only needed that device's bootloader got unlocked before.
Look inside here:
How to Install TWRP Recovery on Android without Root - Make Tech Easier
TWRP allows the user to install, backup, and restore firmware on an Android device. Here's how to install TWRP on Android without rooting.
www.maketecheasier.com
Click to expand...
Click to collapse
Does this work for kindle fire too or just android? If only android is that what you would recommend? The reason I want a kindle fire is because I had one before for a short time and liked it. But a previous generic android tablet I had overheated at the back making it very uncomfortable on the hands. I can send you a list of the options I have at the moment if that would help?
arkiltk said:
Not sure yet but it seems like the shop has a lot of variety within my budget from kindle fire HD 2012 to kindle fire 7" 2015 5th gen. It also has a handful of other brands within my budget: google nexus, acer iconia, lenovo smarttab, generic android tablets, etc.
Does this work for kindle fire too or just android? If only android is that what you would recommend? The reason I want a kindle fire is because I had one before for a short time and liked it. But a previous generic android tablet I had overheated at the back making it very uncomfortable on the hands. I can send you a list of the options I have at the moment if that would help?
Click to expand...
Click to collapse
If you're wanting to have the latest updates on your tablet, I'd say pick another device that isn't a Amazon tablet. Other tablets often have better support for custom ROMs and firmware. While you can find custom ROMs and firmware available for Kindle Fire tablets, they are often outdated and abandoned. You can flash TWRP onto a Kindle Fire, but most of that time that will only give you the ability to root it.

Categories

Resources