Related
Hello,
just got a Samsung Galaxy S in China (under the name of samsung GT-I9008) and use it with China Telecom as the carrier/operator
Specs as follows
Model Name : GT-I9008
Hardware version : 1.0
Firmware version : Ophone OS 2.0
Kernel : 2.6.29 Zeus 1
To my biggest disappointment, the phone doesnt come with Android market but with the Mobile phone operator own device called MM ( Mobile Market) which is only in Chinese !! and very limited in terms of applications you could download.
Is there any way I could install instead Android Market ?
Many thanks in advance for your reply
Christophe
I have the same problem in middle east.
Any help please.
I helped a friend with the same phone. Basically do the following:
1. Download and install z4root
2. Download the Cyanogenmod Google Apps (EPE54B)
3. Open up the update.zip file and get Vending.apk out of \system\app\ and copy to SD card using UMS mode.
4. Use File Explorer on the phone to copy the file from /sdcard to /data/app
5. Reboot
Any luck installing Google Apps on i9008 (Samsung Galaxy S for TD-SCDMA)?
Guys,
I followed the instructions posted on this thread and other sites, to help a friend who recently bought this phone. Successfully rooted the phone. Installed the Google Apps as instructed, but they all are malfunctioning to the point of being unusable.
- Gmail - only works OK with one account, will not allow extra accounts
- Google Maps - zooming does not function
- YouTube - does not even start
- Market - gets stuck at 0% download point for any downloaded apps
If someone managed to install any (or all of these) Google Apps on their i9008, I would be grateful for instructions on how to properly install.
thanks!!
I installed after updating the official ROM to the latest version. This is 2.1 eclair rather than 2.0 based so may explain why it doesn't work for some people. In that case, using the cyanogenmod 4 gapps files may work.
Another possibility is that not all files were copied from the extracted update.zip to the relevant places under /system (yes, it is /system, not /data as I mentioned in my last post)
These would be /system/app, /system/framework etc.
I daresay that you'll need to copy all files from the folders in update.zip over to the right places. I had to delete some of the Chinese apps to make space for all gapps.
Tell me if it works for you. Cheers.
Hi ,
thanks for your input! As I am not at all an expert on technical stuff and do not want to have my phone no longer working, please let me recap :
- I have downloaded the file z4root.1.3.0.apk --> then i have to install it on my SD card and launch the application?
- Checked to download the "Cyanogenmod Google Apps (EPE54B) and it appears on ur link that there are dozens of different files according to phone models but none for the Samsung GT I-9008. Kindly let me know which one to consider.
Did your friend with the same phone eventually managed to have all google apps including the english android market by doing such installation?
Again, the specs of my phone are :
Model Name : GT-I9008
Hardware version : 1.0
Firmware version : Ophone OS 2.0
Much appreciate your help !
Best
Christophe
Yes, we did manage to get the English market (and many Google apps) running properly.
With zroot, install then run it, choose the permanent root option. It'll reboot the phone to finish the rooting.
The gapps version you need to download is listed in the Cyanogenmod 5 row (android 2.1 or eclair based) and is under the HDPI column (means high dots per inch, or just a high resolution display as the i9008 has). Any of the links in that entry should be fine if they work.
I have realised that in my last post, I mentioned copying to /system/app. This is not possible unless you do the following:
Get http://androidterm.googlecode.com/files/Term.apk install same way as zroot.
Run it then type:
su
mount -o remount,rw /system
Quit out of it then copy the extracted contents of update.zip to the corresponding directories under /system using file explorer.
Same thing happened to me w/
Model Name : GT-I9008
Hardware version : 1.0
Firmware version : Ophone OS 2.0
I had to follow the instructions above
thanks for your input..
Is your phone also operated by China Mobile ? was told that it was not possible to root the GT I-9008 being operated by China Mobile.
Anyhow, will try and follow above process.
Well I have watched an interview for Galaxy S2 and they showed a new technology in it...And told that they are challenging the Android market as Android challenged the Iphone...
How about this? Any news?
Hi, now I need some help...
I playing with my China Mobile I9008 yesterday, and as I trying without sucess to find a way to install the market, I think I installed a wrong version of clockworkmod, now my I9008 is bricked (I think). Its starts but after first screen (where's appears I9008 name and so on) the boot come back to ophone screen and keep in this looping more than 20 times... full wipe and others doesn't work
In my mind if I apply again the update.zip can solve, but my file having problems showing erros, can not read the file, etc...
I tryed to find this file but I have no success...
Someone can help me? have some update.zip to my i9008ZMJI1 firmware version?
Thanks.
Install factory image
Ok, I've been trying to find a way to install CM (and the market app) onto my GT-I9008L and have managed to nearly brick my phone a number of times. The only thing I have succeeded in is rooting my phone (use Z4root) and installing a fresh factory image.
(I apologize for broken links, XDA doesn't trust me to post clickable links yet)
To install a fresh factory image:
a) Get the software from this Chinese thread: bbs.dkdiy.net/thread-12788-1-1.html
--The first message in the thread has a link to a RAR file that contains everything you need. Including all the tools & the image itself
--To see the link you'll have to create an account and post to the thread
--I was able to do it by using a combination of google chrome and google translate to work my through the free registration process.
b) run Odin v1.81 (I've tried other versions of Odin...they don't work)
c) select the files shown in this image: www .dkdiy.net/article.asp?id=633
d) the file versions in the image don't match the RAR file. The key is put the CSC file into the CSC blank, the CP file in the "phone" blank, the "all low" file into the PDA blank and the PIT file into the PIT blank
e) make sure you have selected the checkboxes in the image
f) start your phone by holding volume-down+home+power
g) when you see the yellow android digging plug your phone into your computer (you may need the samsung drivers)
h) wait for odin to detect your phone (the first box under ID:COM will turn yellow and list the com-port that your phone is connected to)
i) hit start, wait about 3 minutes, you will see the progress bar update every 5-10 seconds
j) it will auto reboot and finish the installation
To root your phone I followed the instructions on this chinese thread (use google chrome to get an instant translation):
ibbs.91.com/thread-53590-1-1. html
DUDE!!!
I think i got some good news.
I have the same problem with my new S2 bought in China, no Android market. I've been searching all around the web to try to fix it.
It is still not working for me, but i got a little bit farther though.
I find the hint here
http://forum.xda-developers.com/showthread.php?t=1351283
So what i did and what you can try is:
1) Install GoogleServicesFramework.apk
This seems to be the issue, as when you install it you can see the permissions Google requires, and pretty much says the can access ALL the data in your phone. (It would explain the censorship)
2) Install Android Market with any .apk you can find
3) Launch Android Market
The change for me is i can now input my account login. But it still fails connecting to google to actually login. Maybe because i'm still in china and it blocks the connection.
Could any one try this outside china and tell me if it works?
Cheers
EDIT:
By connecting my APN and Wifi (instead of wifi alone) i managed to finally loggin. I HOW NOW ACCESS TO ANDROID MARKET !!!
But not so fast. I have access to the market, but i get an error when downloading an app. So it is still not working, but getting closer. I sent an e-mail to google see if they can fix this (seems my account and my device are still not linked). Waiting for the reply...
Alright it's working now !!!
After exchanging a couple e-mail with google, i managed to download some apps.
I've been testing it for a couple hours now, works like a charm.
GUIDE SGS4 GSM vs CDMA, Unlocking, Rooting,Info on XDA, Flashing,4 noobs & beginners
First off: if you find this useful, please hit the THANKS button, instead of posting thank you in the comments
Over the course of the past three months (and more specifically, over the past week), I'd like to think I've gone from complete noob to proficient android ROM flasher/ phone dude. However, it took many, many hours of searching for info scattered across this site and others, so I figured I'd give compiling all I've learned a shot, into one comprehensive thread that really covers all the stuff you need to learn from the ground up.
Will do so in the next couple 10 posts, topics being:
*Step (-1): What type of network/ phone technology does your phone use?
*Step (0): is your phone networked locked?
*Step (0.5): DECIDING YOU WANT TO ROOT YOUR DEVICE!/ Put a custom operating system on that thaaaang
*Step1: figure out what your device is- specific phone and model
*Step2: figure out how to root (gain root access to) your device looking at XDA forums
*Step3: Follow instructions, root device
*Step4: backup all your apps and app data
*Step5: Install a custom recovery either ClockWorkRecovery (CWR) or Team Win Recovery Project (TWRP), and do a nandroid backup!
*Step6: Choose which ROM or multiple ROMS you want to try out, and download the zipfile to your phone's internal memory or
*Step7: Step 7: flash the ROM and restore your apps!
NOTE: YOU TWEEK YOUR PHONE/ FOLLOW MY ADVICE AT YOUR OWN RISK
I just learned this stuff myself, so I thought now would be a good time to explain it, while I can still remember what if feels like to have no idea what I'm doing haha.
Before I go further, there are similar intro threads to this...for example, this one does a decent job of explaining that by modding your phone, you may void the warranty (although there are ways to restore your device to a state such that you can't tell you ever modded, it, like triangle away, etc.) http://forum.xda-developers.com/showthread.php?t=1118120
I posted this here because a couple of these steps use the Galaxy S4 i9500 as an example...so if you have that phone this thread should be particularly helpful.
Step(-1): What type of network/ phone technology does your phone use?
If you are OUTSIDE the USA, 99% chance the answer to this question is GSM, meaning your phone number is attached to a little plastic sim card that you can put into/ out of your phone...you should check anyways though to be sure.
If you are in the US, you may have a phone which uses CDMA, a technology that does not use Sim cards (true if your carrier is Verizon or Sprint). Phones that JUST use CDMA are sort of "Hardwired" to their networks, making it much more of a hassle to switch carriers; plus, basically everywhere else in the world uses GSM, so if you plan on traveling outside the USA, you probably won't be able to use your phone abroad. If you have a fancy new smart phone, it may have the hardware to use both CDMA and GSM networks, (for example, all Iphones models 4s and above), so check your phone specs.
In the US, the major carriers that use GSM are ATT and Tmobile. I prefer getting phones from these guys, because I know I'll be able to relatively easily use my phone anywhere in the world, and easily switch between cheap, prepaid, contract free plans (like straight talk or ultramobile), which rent out the networks of major carriers like ATT and Tmobile.
Step(0): is your phone networked locked?
ans: This is mostly a non-issue to folks outside the US, or if you don't plan on switching your carrier, but if you plan on travelling abroad or switching your carrier, and have a CDMA phone, you have a tough road ahead that I cannot advise you on . I would suggest checking out this site and buying a slightly used android gsm phone (att or tmobile branded) http://swappa.com/ .
However, if you have a GSM phone you got in the US, your phone may be configured so that putting sim cards from different carriers in it won't give you any service (aka "locked" or "network locked"). Check by taking a friend's Sim card using a different network than you and popping it into your phone; if you have service/ can make and receive calls, the phone is NOT locked. There are probably more sophisticated ways of checking if your phone is network locked, but above is probably the most straightforward.
There are some methods of unlocking your phone for free, but if you have a newer phone it may not work. Plenty of online sites that sell you unlock codes for between $7-$25, and send the code over email either instantly or a day at most after you buy it. Definitely worth it in my opinion; one site I've used a bunch is http://www.cellunlocker.net/
NOTE: if you have your phone on a contract, you are still obligated to pay your carrier throughout the time of your contract, else you pay some cancellation fee. So be aware of that.
Step 0.5 DECIDING YOU WANT TO ROOT YOUR DEVICE!/ Put a custom operating system (ROM)
SO, now let's say you've network unlocked your awesome GSM android smartphone, and you want to travel with it to another country, like for example, India. Because you unlocked it, you can buy a cheap local Sim card and use it in your phone, fully enjoying mobile 4g data (well, more like 3.5G, using HSPA+, not so much 4G LTE in India yet, but I digress). OR, you can use a $45 a month prepaid plan where you get unlimted everything and have no contract, instead of paying $80 a month or some garbage. AWESOME!
However, let's say you got a Tmobile phone and want to use the phone's capability of being a portable wifi hotspot, broadcasting the mobile data it's getting to your computer...turns out you can't do that in India (or on cheap prepaid plans in US, for that matter). I discovered that since I was using a Tmobile branded phone, the Tmobile "stock" operating system of the phone won't let you use the wifi hotspot unless you have Tmobile's special "hotspot plan"...it also hard codes a bunch of shi**y bloatware apps on your phone that suck. Some BULLS**T, eh?
Luckily, there are plenty of free and easy ways to "root" (gain root acccess) to your phone (and plenty of resources telling you how to do so!), and install custom android operating systems on your phone, which
1.) don't have any stupid bloatware apps
2.) let you use all the hardware features of your phone regardless of carrier
The result is a more powerful phone that runs faster, uses less battery life, and is generally just way more badass. Probably the best resource for how to do all of this is the xda-developers forums (http://forum.xda-developers.com/ ) Very vibrant community, and lots of people will help...just follow the rules though, explained tongue and cheeck in the following video ( http://www.youtube.com/watch?v=JmvCpR45LKA ). The main site for xda-developers is www.xda-developers.com, they also do cool vides and stuff on what's up with phone stuff. HOWEVER, if you are not careful you can mess up your phone, so that it's about as good as a paperweight (called "bricking" your phone). So just read all the instructions before you do stuff, yeah?
The following is more or less the beginning steps I did to root and install a custom ROM on a friend's Galaxy S4, which is an international model and so not network locked. The same general process could be applied to your phone as well, but again--this is only a general guide--your phone can (and probably will) have it's own exceptions to the general process. LOOK THEM UP!
Steps 1,2,3: find device model, research how to gain root, ROOT!
Step1: figure out what your device is- specific phone and model
ans: for example, my friend's phone I am setting up for him is the Samsung Galaxy S4 model i9500
**************************************************
Step2: figure out how to root (gain root access to) your device
ans: Off all the devices on xda forums (http://forum.xda-developers.com/index.php?tab=top), found my device ( http://forum.xda-developers.com/galaxy-s4) , found the proper forum (http://forum.xda-developers.com/galaxy-s4/help) , then searched in that specific forum to find the proper thread http://forum.xda-developers.com/showthread.php?t=2419762 , see Q4
**************************************************
Step3: Follow instructions, root device
ans: Instructions are at http://forum.xda-developers.com/showthread.php?t=2292615
NOTE: You must have the proper USB drivers installed, meaning either installing the sdk (software developer kit) from google and getting adb (android debugging bridge) set up (this is the best way to do it, really, especially if you want to mess around with phones more...tutorial on how to setup adb here http://androidcentral.us/2013/08/how-to-install-android-adb-and-fastboot-on-windows/ ) . If you can already transfer music and stuff from your computer, it may work without adb. Be sure your USB cable is not too beat up, and if possible, is the one that came with the device.
adb is very useful for communicating between pretty much any android phone and your computer. You can use it to push files on the computer through the terminal interface, even if the phone's file system doesn't show up for whatever reason on the computer when you connect it via USB ( more on that here http://log.amitshah.net/2012/05/using-adb-to-copy-files-to-from-your-android-device/ ), and a cool little program to send files from your computer to the device in a slightly more straightforward way, if you already have adb installed (http://www.xda-developers.com/android/push-files-to-your-device-with-quick-adb-pusher/)
Also, make sure you have USB debugging enabled. It should be in the Develpors options, which you may have to "activate" to see...see here http://gs4.wonderhowto.com/how-to/enable-hidden-developer-options-your-samsung-galaxy-s4-0146687/
If you are rooting a samsung device, you will probably have to use a program called ODIN. Other android devices allow you to do root through a method called flashboot. In general there are tons of ways to root devices, just make sure the one you are using has been tested and you follow the instructions exactly.
CONGRATS! you are rooted. That's half the battle. Rooting the phone will add a "Super User" app of some kind, which will basically controll which apps have access to the internal files of the phone (located on the "root" of the phone's flash drive). Some apps that are very useful for flashing custom ROMS (like ROM manager) and backing up your apps and their associated data (like Titanium backup) require root access, so you'll need to have rooted your phone first, and then when you open those apps for the first time, tap "allow" when it asks about granting root access.
some cool apps can only be downloaded if your phone has Root, like this gameboy emulator: https://play.google.com/store/apps/details?id=eu.codlab.src.game&hl=en
and here are some good Root apps to have, apparently
http://www.youtube.com/watch?v=jX4ir9r84YA
Step4: backup all your apps and app data
When you do eventually install a custom ROM on onto your phone, it will start out with little to no apps. The best way to get up and running again as quick as possible is to back up all your apps and data with Titanium Backup (mentioned above), which requires root access. Here's a great video on How to use the free version: http://www.youtube.com/watch?v=gQWoWfTA88k ....the video makes a good point in that if you are backing up your apps for a new ROM you are about to flash, you should only backup the User apps. Backing up and restoring the system data as well might cause some problems in the new ROM
While you don't need to to buy the pro version, I would recommend it--7 bucks, but it allows you to restore all the apps you've backed up much faster by letting you back them up into a zip file that you'll later be able to flash on your phone. Very useful, more on that in a bit...video talking about that here: http://www.youtube.com/watch?v=dRR5FONGJUA
Step5: Install a custom recovery either ClockWorkRecovery (CWR) or Team Win Recovery
By "custom recovery", i mean a custom version of the boot/ recovery interface, which lets you do a lot more with your device besides just restore it to factory settings. These custom recoveries will let you do a full backup of your device (often called a "nandroid backup"--this should be the first thing you do after you root your device!), as well as flash custom phone operating systems (ROMS) onto your phone; useful if you want to fully use all the hardware features of your phone, and not have the bloatware apps from the manufacurers hard-coded into your phone.
It's worth noting here that it's VERY important to install the correct version of CWR or TWRP. Usually to download CWR for your device, you can just download an app called ROM manager (again, after you've rooted your phone), which will recognize your device and then install the proper CWR version on it.
NOTE: If you have a more esoteric model of phone (like I do--the Samsung Galaxy S3 T999L, an LTE version of the S3 that came out in 2013, a while after the initial S3 launch), you may have to flash a custom recovery of a similar and more popular phone model to flash some custom ROMS (in my case, I had to flash the the Galaxy S3 model T999 version of CWR). For weird esoteric cases like this, it may be worth it to buy a useful app, ROMToolbox pro, which will let you flash a custom recovery for a userdefined device onto your phone in the paid version (it's like $5). Most times you shouldn't have to worry about this stuff, but just make sure you read any instrutions on XDA forums carefully before doing stuff.
As mentioned before, before messing around with your phone anymore, do a nandroid backup--super easy and essential if you make a mistake installing the wrong ROM or Recovery. Doing a nandroid backup will create a .zip file that contains a full "image" of your phone--all your data, apps, settings, a snapshot of your phone exactly the way it was when you took it. In creating this backup you can save it to your phone's micro SD card, or the phones internal memory. Regardless, always a good idea to save a copy on your computer too when you are done.
For the Samsung galaxy S4 i9500, looks like TWRP is the recovery to flash: http://forum.xda-developers.com/showthread.php?t=2361122
Step6: Choose which ROM or multiple ROMS you want to try out, and dl zipfile to phone
Now comes the fun part. Do some research on what custom ROM you'll want to try out. Some basic principles about ROMS:
Roms based on the Stock OS: These ROMS are based on the manufacturer firmware/ OS that the phone shipped with. So for Samsung devices, for example, these types of ROMS are Touchwiz based (because "TouchWiz" is the name Samsung has given to it's proprietary software that is responsible for a lot of the bell and whistle tricks you see in Galaxy S4 commercials, for example) These Roms are usually about 700 MB in size, and may still have some of the samsung apps installed if you do like to use them.
AOSP or AOKP ROMS:
AOSP (Android Open Source Project) ROMS are those that ship with "vanilla" android, meaning they don't have any manufacturer bloatware--they come with more or less the bare bones apps required to run the system. These ROMS will be much smaller, around 100-150 MB in size. The most popular of these is CyanogenMod, which is often referred to as just CM (for example, CM11.0.1 stands for CyanogenMod version 11.0.1). The guy who made clockworkrecovery, Koush (a legendary android developer of sorts, it seems), now works for the CyanogenMod development team ( think)
AOKP is the name of another popular AOSP based ROM. AOKP stands for Android Open Kang Project, Kanging being some jargon for stealing code and messing with it or something. Apparently it was used as a joke and then stuck, in the same sense that their mascot being a unicorn stuck (which I think is awesome haha).
IMPORTANT POINT ABOUT AOSP ROMS:
If you flash an AOSP Rom, the google play store will NOT be installed by default. In order to fix that, you'll need to flash another zip file containing the play store app as well as other basic google apps (gapps for short) as soon as you flash the Rom itself. You can find the proper gapps zips that go with the proper AOSP roms here: http://goo.im/gapps
There are couple apps that will let you download the ROM files directly to your interal storage from the app itself, like Rom Manager. However, to make sure you have the most up to date version of the ROM, you should visit the ROM's website directly.
Custom ROMS will often have a most recent stable build, and a most recent "nightly" build. The nightly builds may have some new experimental features, but may be a little buggy.
Step 7: flash the ROM and restore your apps!
So here's a pretty good short video walking through how to flash a ROM, although uses a different recovery interface besides CWR or TWRP : http://www.youtube.com/watch?v=nxTwGwtUBbk ....this does a good job of explaining the basic idea, however--
A.)you get the zip file of the ROM you want to flash on your internal or removable SD card
B.) reboot into recovery mode (often by holding down the volume down key and power button at the same time when your power is off, but you should look up what it is for your specific device)
C.) do a Wipe or Factory Reset. THis should not wipe the data on your SD card or phone's Internal SD card
D.) Wipe the Cache or the Dalvik Cache, whatever it is called (though on TWRP, the wipe feature does both a factory reset and cache wipe at once)
E.) install from SD card the zip file containing the ROM you are going to flash
F.) If the Rom is an AOSP based ROM, install the zip file containing the proper package of google apps
G.) reboot system
Again, the above are just general steps. If you want to see someone flashing a ROM with the recovery you are using (and I would recommend CWR or TWRP), just search for it on Youtube.
Now, if you plan on restoring your apps by flashing a Titanium Backup zip file, you first want to reboot into the new ROM, and skip the part when it asks you if you want to restore your phone using your google account (you can do that later). Then reboot into recovery and flash the Titanium backup zip file. got this info here: http://www.s3forums.com/forum/galax...backup-pros-update-zip-restore-your-apps.html
And that's about it! let me know if I got anything wrong. If you do have questions, I'll try my best to answer them, but again, I've just learned all this stuff as well, so I may not know.
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.
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...
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.