Database Info

[ROM][2013.01.09] Lenovo A789,P700i,A660 custom ROM (ICS)

I made a clean ROM based on the factory ROM for the Lenovo A789, A660 and P700i
Cleaned up ROMs:
- A789_S227_cybermaus_V2 (below)
- A789_S228_cybermaus_V2.1 (further below)
Ported ROMs (ported from P700i):
- A789_ROW_S105_cybermaus_ICS_V3 (further below)
- A789_ROW_S106_cybermaus_ICS_V3.1 (Further below)(also for A660 and P700i)
- A789_ROW_S107_cybermaus_ICS_V3.2 (Further below)(also for A660 and P700i)
The current and advised rom to use is A789_ROW_S106_cybermaus_ICS_V3.21
Based on factory ROM A789_S227_120827, and located in my Dev-Host. It is as close to factory as possible, which I hope will be good for stability. It is a flash-utility ROM, because it also holds the latest preloader, uboot and recovery. Assuming those are OK, followup fixes will be update.zip style.
Summery of changes:
- Rooted the phone with Chainfire SuperSu
- Set to boot in US-english, changed name of ROM
- Added MoreLocale for extra languages in 3rd party apps
- Removed Chinese apps, incl Chinese keyboard, removed SmsReg.apk
- Left Lenovo Security (anti-malware) and Lenovo (Go) Launcher intact
- Added Google GAPPS, Play Store, Maps, etc
- Added MobileUncle toolbox, SManager (root explorer). Titanium backup (free version)
- Added fix for location services
- Added CWMT recovery image (modded from 593cn.com)
- Added Skype, Whatsapp, and some others, as auto-install into userdata upon wipe
- Prepared busybox (you need to run script /system/xbin/installbusybox as root if you want it)
- Replaced bootup animation with clean Lenovo butterfly
- Replaced all some audio files with english named ones (thanks mabuc)
- Caller ID bug still present, sorry
- Just as a reminder, these ROMS have English and Chinese only.
Instructions:
By default, the ROM will not overwrite USERDATA or FAT. If you want a clean slate, first extract empty.userdata.rar and/or empty.fat.rar
- Read bgcngm flash tutorial.
- Read it again
- Start Flash Tool (v3.1222, in my Dev-Host)
- Load scatter file
- Take out USB cable and replace battery
- Press the download button in the flash tool
- Connect the USB cable
- Wait for the flashing to complete
A789_S228_cybermaus_V2.1 (no longer current, Use V3 instead)
Based on factory ROM A789_S228_120913, and located in my Dev-Host. Similar to V2, but newer, and a few extra fixes. It should be noted that the S228 is listed to solve unexpected crashes, so an important update in itself.
I do not have a A789, so it is a blind build. Until I get positive feedback, consider untested. Don't be the first to try if you are not experienced.
Summery of changes:
- Same as on V2, and additional
- Removed 2 more chinese apps that I forgot last time
- Prepared busybox (you need to run script /system/xbin/installbusybox as root if you want it)
- Added a tweak so USB-Debug notification is no longer shown
- Added a tweak so Wifi works on all 14 international channels (rather than only the 11 US ones, may be undone if you set a different locale)
Instructions:
This is a update.zip type ROM. So you need the custom recovery, see post #3,
A789_ROW_S105_cybermaus_ICS_v3.03
Based on P700i_ROW_S105_120920, see this separate post.
A789_ROW_S106_cybermaus_ICS_v3.11
Based on P700i_ROW_S106_121001, see this separate post.
Please note that this ROM I also build for the P700i and A660. See same post.
A789_ROW_S107_cybermaus_ICS_v3.2
Based on P700i_ROW_S107_121221, see this separate post.
Please note that this ROM I also build for the P700i and A660. See same post.
Below:
Post #2: Small review and fix of location services
Post #3: Custom recovery image
Post #4: Root your phone / install GAPPS
Also, many issues for the A789 are similar to those of the A750, so if you have questions, do search that Lenovo A750 thread to.
Thanks
Also thanks to bgcngm for his help, and to jazzor for his help
=================
BTW: Due to new forum rules, resulting in a large number of people that cannot post into developer threads and that subsequently PM me, I open op a new Q&A thread.
I am not going to be policing, so you can post where you like, but I invite everyone to use this new thread for any Q&A, and this thread for ROM releases and deep development talk only.
Consequently, if you PM'ed me, look for your reply in this new thread
Thanks
====================
PS: do drop me a reply if you use or tried it! Or press the 'thanks' button.

So, I got my first glimps at the A789. So to speak. My colleague was holding it while we were audio-skype, so I did not actually see it.
His A789 came with a Etotalk ROM by Dean, which I now suspect is a reworked Smileyvvv ROM with Sony Experia interface. Not bad, but as you know, I am a 'factory ROM' guy. My colleague may also be, because he had already replaced the the SE launcher with GO Launcher, which is the default Lenovo one. Also my colleague said it jammed a few times, which it still has not done on my factory A750 ROM.
Most of the phone worked, but a few tips for others out there:
- The phone still has the Called-ID bug. Even though it is newer 4.0,4. I know some of you claim this is solved on ICS Mediatek, but I still claim it is solved in *some* of the cases, not all, it also depends on how your provider sends the caller ID info. Anyway, you can work around it with the prefixer app as reported before.
- It did not come with the MobileUncle tool, but with the Etotalk tool. Which was not updated for the new MT6577 chip, so it had no Engineer Mode. Install the latest MU tool (version 20120813v2.2.0 its in my Dev-Host), so you get one with MT6577 Engineer mode.
- Recovery Mode was hard to get into. Like the newest A750 preloader, you have to press the power putton *just before* you press both volume buttons. But it did came with the CWMR Touch, though its Touch function was broken, so buttons only. They probably simply tried recovery images of other models, and did not properly build one with the A789 kernel, but it does not matter, it works well enough.
- Location services did not work. Update the phone with the ICS_locationfix_v1.3 update using recovery mode. While you are in recovery, also wipe cache. And finally, go into MobileUncle tool, the MTK Engineer mode, and in location settings, change the NetLoc from MEDIATEK to GOOGLE. Now your location services should work.

Lenovo A789 Recovery
I created a recovery image for the Lenovo A789 based on ClockWorkMod Touch 5.5.0.4. However, I do not own a A789, so until I have reports of it working, consider it untested. You can download it from my Dev-Host: File A789_S22x_recovery_cybermaus.rar
NOTE: It has come to my attention this recovery works well, except the nandroid backup function, which is broken. If you value nandroid backup, install the APKHOT one below.
While doing this, I also found a full APKHOT distro which had what seems to be a CLockWorkMod (non-Touch) recovery in it, so I extracted that and also uploaded it. That too you can download from my Dev-Host: File A789_S22x_recovery_apkhot.rar
Both of them you will have to flash using the flash tool, using bgcngm's excellent manual, and the V3.1222 of the flash utilities and drivers, also in my Dev-Host. If you flashed my V2 ROM, you do not need to do this, as the recovery is already part of that.
Once you have the recovery installed, you can enter it by pressing both VolumeUp/Down while booting the phone. Due to an issue with the preloader, it may be needed to press the power button slightly before both volume buttons. If the phone seems stuck, it means the preloader messed up, remove battery and try again.
Inside the recovery (the Touch variant) you can navigate not only by its physical buttons, but also by screen buttons, and by gestures: swipe up/down for up/down, left for back and right for enter.
The first few people using this, please report your findings, good or bad.
PS: As alwasy, thanks to bgcngm for his unpack utilities, which I used to modify the recovery.img

Lenovo A789 Root; GAPPS, Location DIY
Its been mentioned before, but if you have a working recovery (like above, hopefully), you can always yourself root your phone. Simply install (from inside the recovery) chainfire's "CMW installable ZIP"
Link to his post: (ignore his big red requires root warning)
The file you need is labeled "CWM installable ZIP" at the bottom.
Direct link to the file you need to install via recovery update.zip
And while you are at it: You probably also want to install the latest Google Mobile Services (better known as GAPPS) from CyanogenMod V9:
Explaining wiki from CyanogenMod
The file you need is called gapps-ics-20120429-signed.zip and can be found here
You probably also want to wipe your cache partition after doing this.
To complete this DIY of fixing factory ROM: On Chine phone typically the location services do not work. Update the phone with my A750 V1.3 update using recovery mode. (it works on the A789 because it is a minor update, but *DO NOT* any of the other A750 updates on the A789. I repeat, do *NOT* flash A750 on A789). While you are in recovery, also wipe cache. And finally, go into MobileUncle tool, the MTK Engineer mode, and in location settings, change the NetLoc from MEDIATEK to GOOGLE. Now your location services should work.
Good luck
PS: If either update.zip refuses to install, remember to turn off the checksum and assert checks in the recovery.
And thanks to Chainfire for his work, and the team at CyanogenMod for theirs.

cybermaus said:
Before I can help, please provide some info:
Can you tell me what ROM you have?
Which flash tools did you use to root?
Also, do you have a working recovery?
Click to expand...
Click to collapse
hwonggc said:
I fix the proximity thingy. it's caused by my lousy screen protector. But i've got another bigger problem now. I've accidentally uninstalled the default system home screen. I cant assess anything now. I tried flashing a recovery inside but it still doesn't work as factory. I use SP flash tool v3.1.222.00
---------- Post added at 06:32 AM ---------- Previous post was at 06:18 AM ----------
dont think my recovery is working. Could you please provide me with a working recovery? =(
Click to expand...
Click to collapse
Yes, a recovery is on the todo.
But for now, you did not answer my questions yet:
- Can you tell me what ROM you have? Or had. Original Lenovo Factory, Etotalk-Dean, some other?
- Which flash tools did you use to root? Or rather, which files did you flash using that tool to deal with root. Actually, the fact that you had to root it yourself probably means you had factory ROM, but please confirm.
As stated, I am uploading S221 original to my Dev-Host. Flash that with the flash tool. On short notice, that is all I can do. On longer notice, I will help you, but give me some time.
Edit: In fact: You you already have messed up your recovery, and I do not have a A789 to play with myself, you may be my guinea pig for the recovery build. So I will work on that today. (as today is not a working day for me anyway). If you do not mind being a tester. After all, the damage is already done, and you apparently already know how to flash using the utility.
EDIT: @ hwonggc : Please test recovery in post#3. Just update your post below with results, or PM me. I would like to avoid too many new posts on this while we are testing.

cybermaus said:
Yes, a recovery is on the todo.
But for now, you did not answer my questions yet:
- Can you tell me what ROM you have? Or had. Original Lenovo Factory, Etotalk-Dean, some other?
- Which flash tools did you use to root? Or rather, which files did you flash using that tool to deal with root. Actually, the fact that you had to root it yourself probably means you had factory ROM, but please confirm.
As stated, I am uploading S221 original to my 4Shared. Flash that with the flash tool. On short notice, that is all I can do. On longer notice, I will help you, but give me some time.
Edit: In fact: You you already have messed up your recovery, and I do not have a A789 to play with myself, you may be my guinea pig for the recovery build. So I will work on that today. (as today is not a working day for me anyway). If you do not mind being a tester. After all, the damage is already done, and you apparently already know how to flash using the utility.
Click to expand...
Click to collapse
Yes yes. I had the factory rom. I got the phone just yesterday evening and this afternoon it's half dead already. I use smart phone flash tool to root using a file i got from http://www.fight.org.ua/publications...novo_A789.html. Everything was fine until I deleted the original home UI and the apex launcher also. So there isn't anything I can do. I'm downloading the S223 from some russian site and try, hopefully I can find some luck there. Downloading slowly~ sighhhh.
---------- Post added at 07:49 AM ---------- Previous post was at 07:40 AM ----------
BTW~ i'm willing to test out your rom too! I wouldn't want to sound too demanding, put please please put in the play store will ya?

I posted the custom build, see first post. It may take a while before I can get it uploaded, I am on a bad link.
Also, there have been 20 downloads on the recovery image. Come on guys, someone must be able to provide feedback about it working or not!

A789_S227_cybermaus_V2 ROM is working
Hello
Thanks for Your work.
Your A789_S227_cybermaus_V2 ROM is working.
Simple Flashing and start without problems. Now I must check some functions.
Thx again
basell
Edit:
The 3g connections don't work at first run. After restore they start but in My opinion with less sensitivity (compare to stock rom). It's look like A789 loose some frequency on witch can work.
Edit2:
And they have some strange behavior - After couple min of data connection (on 3G) they disconnect with information - "Restricted access changed" and the same is when I try to choose network manually. After that sometimes they login to 3G sometimes they change to EDGE.
In Stock version (S221) was not this kind of problems.
Edit3:
In place with good 3G signal I have no problem with data transfer.
How Can I check on witch frequency (2100,900,850) I have connected My data transfer?

Thanks for testing
Well, I definitely did not mess with any of the 3G stuff. So if it is true that 3G is less sensitive, then I would claim it is true for the factory S227 vs factory S221, and not directly related to my cleanup of it.
But (sorry to say so) I have learned to take claims of improved or degraded radio sensitivity with a grain of salt, even for the factory ones.
Having said that: Restoring S221 radio into S227 firmware is easy. The radio is separate firmware file, and I can extract the S221, S223 and S227 firmware in a separate file, so you can test. Were you actually using factory S221, or some other?
As to whether it is using 2100, 900 or 850: I can probably figure out how to get that info, *BUT* reality is that your provider most likely has only one frequency anyway. Most, pretty much all, EU providers are on 2100. The phone could not get to 900, simply because your provider does not have that frequency in the air (not for 3G anyway). And 850 is not supported at all on this phone.
Anyway, inside MU utility, engineer mode, bandmode, you can check/set the frequencies that are supported.
But please run a proper test if 3G is really degraded. As stated. it is so often a empty claim, I am somewhat careful to follow it. You want me to extract the 3 versions of firmware files in update.zip files?
Also, what country/vendor are you? please list the MMC and MNC from inside the APN settings.

Hi
If You will prepare this files I can test it tomorrow.
I'm from Poland and I have two frequency on data transfer - 2100 and 900. But I don't know if A789 use only one or change them. The place I'm test the signal is poor and I don't see if I work on 2100 or 900.
If You can, pleas tell me what kind of tests I can do to do that properly

Ok, here they are. update.zip type.
I only have S221 and S227, but the firmware files were indeed different, in more than just their timestamps. Of course, normally I would assume newer is better. So to make it clear: below files only replace the radio&dsp firmware, not the phone firmware.
Try to test honestly for yourself. Same conditions, same place, same time (because network load can make a difference)
It is possible that 3G really is degraded in S227, but as mentioned, I learned to not jump to conclusions just because the network is having a bad day.
WARNING: I retracted the two attachment, because I made a typo in the installer script. While the firmware is for the A789 (MT6577), the installer script is for the A750 (MT6575). Sorry. I will upload the correct ones in a moment.... Anyone that took a copy of these files before Oct 14, delete them!!!
I suspect the install would simply have failed, no harm done, but best to get rid of all copies anyway
BTW: basell, is that why you asked how to install? Really, if you ask for help, you should provide a bit more info. Anyway, I attached newer scripts, if you still want to try.

sorry for My question but :
How to install this firmware?

Like any update.zip on android. Go into recovery (see post #3) and apply the update.zip

i have the problem that the netlocation doesn't work with google maps, i flashed the cyber update 1.3, nothing changed, what should I do now?

And this is on what phone and ROM?
Anyway, to quote myself: "While you are in recovery, also wipe cache. And finally, go into MobileUncle tool, the MTK Engineer mode, and in location settings, change the NetLoc from MEDIATEK to GOOGLE. Now your location services should work."

many thanks, Cybermaus, netlocation works again after your instruction

Hi,
Thank you very much for building the ROM !!
I am using it for 3 days now and I am happy to report no problems with it. Everything works and most important: no more freezes !!!
my A789 came with the Etotalk by Dean ROM which was mostly OK, but was freezing from time to time (some days not at all, other days several times a day - most of the times when hanging up a call or, when trying to do wake it from standby: I was pressing the power button, but the screen would not light up).
Other things I like about this ROM:
- all phone functions work great
- Google Play works perfectly
- is rooted
- it has the Lenovo battery app, which is great! I am not 100% sure if this is the reason, but the battery life went from 1 day to 2 days
- I had no issues flashing it
- CWMT recovery works
Also, so far, I did not experience any 3G issues

I have written a small review of the Lenovo Security app, which you guys may want to put back on your phone if it was cooked out of it.

jman0 said:
Thinking it twice, I've remembered another reason. One of the things I like most about the apkhot rom I'm using is that the external sdcard is mounted on /sdcard and not /mnt/sdcard2, which avoids problems with many apps. I tried one of the newest apkhot roms, based on s227, and none of the tricks to exchange /sdcard and /mnt/sdcard2 worked with it.
Click to expand...
Click to collapse
Well, that is actually an easy change to perform, just change the /etc/fstab.vold
However, if you go into settings->storage, the first option is default write disk. Change it from USB storage(the internal SD) to SD (the external SD)
So no hacking is needed at all.....

I've been running your rom for around 6 hours now. Everything runs fine. The 3G connection worked without much trouble. The only thing I haven't been able to do is performing a backup with the CWM Touch Recovery. So, I've just flashed the recovery I had on the apkhot rom I was using, using Mobileuncle tools, and now I've been able to create a backup.
So far, so good, and I've noticed a slight performance increase, too.

Mtk6575 star n8000 guide official roms and custom roms

MTK 6575 STAR N8000 GUIDE AND BEST CUSTOM ROM INSTALLATION GUIDE.
<ul>
<li>First off I started this thread to seperate the current thread for this phone that is riddled with question and answeres and it is super difficult to find what you need to find in the thread. I am writing this guide and thread to give back to the forum for the many days and hours I spent finding everything I needed to find, to root, flash and mod this phone properly. My hopes are with my knowledge on the subject you wont have to spend hours of fruitless searching like I did to find what you need. I'd like this thread to stay uncluddered with multitude of questions if you have them, message me or go to this thread here and post please: http://forum.xda-developers.com/showthread.php?t=1695210&page=96
<li>I would like for anyone finding new ROMS, making custom firmwares for this phone to please add them here to begin a nice list of ROMS custom or official for people to be able to find them in one place.
<li>First off i'd like to give credit were credit is due. Shout outs to;
angelobiz
Bruno Martins
Kyrie1965
sas007
and anyone else I may be forgeting I appologize
The Guide
<li>Follow Bruno Martins guide for setting up sp flasher here: http://bm-smartphone-reviews.blogspot.it/2012/05/mt6575-flashing-tutorial.html#comment-form
<li>​Just some notes and observations that were not mentioned in his guide that will help. In order to install the drivers try right clicking the driver for your system and selecting install. If that doesn't work here is what you do. Turn off your phone, take the battery out, put it back in (if you don't do this it will just show a charging symbol) now plug it in, it should attempt to install the drivers and fail, at this point go to your start button, search programs and files and type device manager, when it comes up select the one with an exclamation point and right click it, select update drivers, point it to the driver folder and then your operating system folder, i.e. vista, windows 7. If the attempt to install does not work download http://narod.ru/disk/57204199001.bb08022cc3658b67af84bc83bd330b0c/20120705_e1808_v75_jbl1.zip.html extract the folder.
<li>Download http://www.mediafire.com/download.php?htx4lkktne1jmzg recovery image and place and replace the recovery in the folder above.
<li>Do not have your phone connected to your computer, open sp flashtool downloaded from Bruno martins guide select scatter-loading on the right select the scatter file in the extracted folder, deselect everything but the recovery i.e. only have recovery selected! Click the download button.
<li>Turn off your phone, remove the battery, put the battery back in plug in your phone, it should now attempt to install drivers, again it will fail, start, search programs and files, device manager, right click the one with the exclamation mark, select update, select driver folder, select your windows version, yes on any warnings, now installed.
<li>NOTE: I recommend never plugging in your phone until you hit the download button and it says searching with sp flashtool. It doesn't react if it's plugged in before then.
<li>O.K. So at this point you should have your drivers installed and recovery as well. Almost there.
So next download http://www.sendspace.com/file/oj1fv2 2 gb internal memmory and 500 mb external. Essentially what this zip does is make your phone have 2 gigs of internal space and 500 mb external instead of 500 mb internal and 2 gigs external, super cool.
Don't do anything yet though.
<li>Next download http://www.sendspace.com/file/uj3jqx This is the ultimate rom I spent some time on for our phones, it's android 4.06 while it's not orriginally mine I fixed a lot of issues and made it much, much, better and pre-rooted with buisy box.
<li>Next download http://www.sendspace.com/file/7yfizd That's right GOOGLE NOW fully working, really cool, works perfect you'll love it!
<li>Now that you have them downloaded put them on your SD card. Here is were people kept telling me if your external doesn't work you can just put it on your internal Sd card. DON”T DO IT! If your external doesn't work you put a smaller one in a 2 gig works nicely, I had a 16 gig and it wouldn't read, had an old 2 gigger laying around and read it just fine. Heres why you don't use the internal, your flashing the internal memmory!! It will mess everything up!
<li>That said, files on the sd card put it in your phone.
<li>Press power while holding the up or + volume, release power continue to hold the volume and you'll eventually go into recovery menu.
<li>Use volume to navigate power to select.
<li>Select wipe data/factory reset, confirm.
<li>Select wipe cache partition, confirm
<li>select advanced, select wipe dalvik cache, confirm.
<li>Now select install zip from sd card, choose zip from sd card and select the custom rom file, confirm.
<li>Go back and reboot, let the phone reboot to system, as a side note screen will be moving white, its just the wallpaper. After full boot up let system settle then hold power and select recovery.
<li>Once back in recovery select install zip from sdcard, choose zip from sdcard and select the 2 gig zip, install.
<li>Select choose zip from sd card and select the google now zip and install, now reboot your phone, and love the awesomeness. By the way it's just google in your app dawer or choosable when you select the microphone on your home screen.
FLASHING OTHER ROMS
<li>There are two different types of ROMS you can flash.
<li>Official-These are official builds and releases made for your phone. These will be flashed by using sp flashtool. Now our phones also have unique hadware sometimes different from phone to phone. Chinese are pretty infamous for mixing and matching hardware. That being said you need to have software settings set for your particular hardware. You do this by using a particular software called SP MDT which you can download here: http://www.sendspace.com/file/6kee8d When you download the file run it. Select your scatter file, then select the button with the question marks, select unlock, the first one on the left is for your rear camera, middle is for front and finally right is for your screen setting which most people have trouble with and think they bricked their phone. The only way to truly test this is trial and error, if your screens normal you''ve selected the right screen setting, if your cameras work they are also on the right setting. Now close SP MDT and it auto saves the settings for you and use sp flashtool as normal.
<li>Custom-These are modded and themed developer ROMS, these are installed by flashing from recovery and generally do not effect your screen and camera settings because the do not contain uboot data.
Troubleshooting
<li>Don't flash NVRAM and UBOOT if your phone already works fine with cameras and LCD screen!
<li>My phone will not connect to install drivers- Many methods have been mentioned, but the one that works is-power your phone off, take out the battery wait 5 sec, put battery back in, now plug in your phone to the pc, it should attempt to install drivers and fail, go to start then type in the search box device manager, select it, right click the one with the exclamation mark, choose update. If that doesn't work, run sp flashtool select your scatter file choose what you want to install, select download button, now follow the steps provided above and plug in your phone. Also The cord that you use to pluggin to your computer may be the issue, if it does not transfere files when you plug it in normally then it wont work for the drivers, some of them are charge only I found that out myself when two of mine didn't work.
<li>My sd card can't mount in recovery-Most likely cause SD card is incompatible i.e. too big, use a smaller 2 gig card, do not use internal memmory as others suggest, it can mess things up and I advise against it.
<li>SCREEN PROBLEMS! Psychedelic colors, black, white, gray and others. CAMERA PROBLEMS! No camera, wont focus etc. Etc.... You need two programs spflashtool found here: http://www.sendspace.com/file/bh81se and SP_MDT found here: http://www.sendspace.com/file/6kee8d You also need an official firmware. Open SP_MDT go to the box that says scatter file, point it to your official firmware scatter file, then click the box with all the question marks, press unlock, the first option is your rear camera, the second option is your front facing camera, the last option is your lcd settings which make it look normal (not phsychedelic and wacky). Now these settings vary from phone to phone so you just have to trial and error them, basically if your screen is right, the seting is right, if your camera works the setting is correct. Now you can close the SP_MDT don't worry it saves your settings for you even though you just close it. Go into SP Flash tool Now you can flash the whole ROM but you don't have too, you only need to select UBOOT it will give you a warning it's perfectly fine, thats all you need to flash to fix your settings, and it wont mess up your current ROM.
Official Roms
<li>Flash With SP Flash tool, Do Not Check UBOOT or NVRAM Unless you have already messed up camera and LCD settings in which case you need to follow the troubleshooting section.
Firmware Stock
Latest (05.07.2012) official firmware for N8000 - 20120705_e1808_v75_jbl1l THANKS TO Kyrie1965
http://narod.ru/disk/57204199001.bb08022cc3658b67af84bc83bd330b0c/20120705_e1808_v75_jbl1.zip.html
stock firmware 9 May:
http://115.com/file/dpnafvtw
stock firmware 19 may
new firmware with better wireless signal
http://115.com/file/e7jyi2dv
N8000-root-wifi-20120519.zip
click on green box for download
*20120612_e1808_v75_jbl1
Latest (05.07.2012) official firmware for N8000 -*20120705_e1808_v75_jbl1l http://narod.ru/disk/57204199001.bb08022cc3658b67af84bc83bd330b0c/20120705_e1808_v75_jbl1.zip.html
Custom ROMS
<li>Flashed with recovery, wont mess with display and camera settings already set, wont fix them either.
My Favorite Also There Are UPDATES
http://www.sendspace.com/file/uj3jqx
UPDATED To 2.1 http://www.sendspace.com/file/k5uwoh
More Live Wallpapers http://www.sendspace.com/file/yuelii
</ul>
SCREENSHOTS
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
A 4.03 custom rom
http://www.sendspace.com/file/2pwtc6
Feel Free to add more, as will I. If you like this thread feel free to thank me if you really like it please DONATE thanks.

NICE
Wow, thanks for putting the time into making a comprehensible thread. Cant wait to get some free time to root my n8000. How's the battery life in the ROM and are there any bugs? will report back if i run into any issues.

Hello
what is the point of having two threads for the same device.?
why did you not just post this there in the correct place?
surly it is much better to have one place to go to for all the answers and to ask, the N8000 thread has developed as the device has
you will just be adding to others confusion
good luck.

If you visit any of the other threads Of different phones they actually contain multiple threads which keep things uncluttered, so that people can find what they need that was my goal with this thread. They don't just contain one huge single thread.
Sent from my N8000 using xda app-developers app

thanks for your work!one question: your rom is good with battery? is it ondemand or performance dispatcher?

Incompatible apps
Thanks for the guide I've now got the 4.0.6 Rom on my phone. one problem, the play store says a lot of apps aren't compatible with my phone. I'm assuming this is because its a 4.0.6 Rom is there anyway to make the play store think you have 4.0.4 so it will let you download them or any other way to download these supposedly incompatible apps?

there is no android 4.0.6 this rom is based on android 4.0.3
lewisqpr said:
Thanks for the guide I've now got the 4.0.6 Rom on my phone. one problem, the play store says a lot of apps aren't compatible with my phone. I'm assuming this is because its a 4.0.6 Rom is there anyway to make the play store think you have 4.0.4 so it will let you download them or any other way to download these supposedly incompatible apps?
Click to expand...
Click to collapse

pjrollo2000 said:
there is no android 4.0.6 this rom is based on android 4.0.3
Click to expand...
Click to collapse
Okay I've now tried a 4.0.4 Rom and its still saying loads of apps are not compatible when downloading from google play? These apps worked fine when I was on the stock 4.0.3 Rom.

sendspace.com/file/uj3jqx was 4.0.6 is a moded version of android 4.0.3 the build.prop file has been edited 4.0.6 there is a build.prop file somewhere that lets google play compatible with all apps.
lewisqpr said:
Okay I thought this one here sendspace.com/file/uj3jqx was 4.0.6. Are other people having problems with apps not being compatible with there phones when downloading from google play?
Click to expand...
Click to collapse
---------- Post added at 06:49 PM ---------- Previous post was at 06:29 PM ----------
I have tried all of the moded roms from the Russian and Chinese sites where all these roms come from if the dpi is set to anything over than 240 google play most apps are not compatible check your build.prop file /system there will be something like this ro.sf.lcd_density=190 delete it then try google play again if you want a different dpi you need a moded google play apk

pjrollo2000 said:
sendspace.com/file/uj3jqx was 4.0.6 is a moded version of android 4.0.3 the build.prop file has been edited 4.0.6 there is a build.prop file somewhere that lets google play compatible with all apps.
---------- Post added at 06:49 PM ---------- Previous post was at 06:29 PM ----------
I have tried all of the moded roms from the Russian and Chinese sites where all these roms come from if the dpi is set to anything over than 240 google play most apps are not compatible check your build.prop file /system there will be something like this ro.sf.lcd_density=190 delete it then try google play again if you want a different dpi you need a moded google play apk
Click to expand...
Click to collapse
I changed the lcd density, the model and product name in the build.prop file and now its letting me download all the apps. Thanks for your help.

Those are for jbl1
Can u made it for jbl2 ?
Sent from my GT-N7000 using xda premium

xpresotw said:
Those are for jbl1
Can u made it for jbl2 ?
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
This is really important to note. Newer phones have JBL2, and the JBL1 stuff at worst soft-bricks them and at best takes away auto-focus from the camera (still working on this, but seems permanent for now).

waiting

Actually the rom was created by alexey arsenev, will work on jbl2 but need to flash with jbl2 boot image.. But autofocus will not function..
Sent from my GT-N7000 using xda app-developers app

Can you upload it to someother host
i am unable to download anything
stock firmware 19 may
new firmware with better wireless signal
http://115.com/file/e7jyi2dv

oh no.....
thanks...
i did everything in your post i still have the blurry image and to worsen the problem after reboot my phone language is in russian

google now
I've watched the "noob" video for posting - but not really sure if this is the right place to post. Please don't shout at me
I've watched a few videos about getting "google now" working on ICS - but I have little Android experiece and do not want to break the phone. Has anybody done it successfully on this ? can u point me at a failsafe utube video (or something else) to get this done without my loss of £120GBP ? Thx...

niman1 said:
I've watched the "noob" video for posting - but not really sure if this is the right place to post. Please don't shout at me
I've watched a few videos about getting "google now" working on ICS - but I have little Android experiece and do not want to break the phone. Has anybody done it successfully on this ? can u point me at a failsafe utube video (or something else) to get this done without my loss of £120GBP ? Thx...
Click to expand...
Click to collapse
Yes -- it works! I've done it.
I'm sorry that you're not going to find one step-by-step guide for this phone, but all the info is here.
This is a very hard phone to "break" in a permanent sense, but I'd read as much as you could stand before you began to avoid headaches that others have had before you. Between the two threads here, there are 150 or so pages of info. Especially important things to note: Make sure you have the right phone (not quite as easy it sounds) and make sure you note all the current details of your software before you get under the hood.
In order to use Google Now, you'll first need to root your phone and install a custom recovery (if those don't make sense, use the Google to search for an overview).
For our phone, I'd start with the first page of this thread: http://forum.xda-developers.com/showthread.php?t=1695210
So, the question becomes: Do you have root and a custom recovery?
FWIW, Google Now is interesting but has yet to seem revolutionary to me. Seems like something that will be amazing three or four generations from now.

Hi sir.. thanks for your sharing.. i use this rom from a mont h ago... its running stable.. can you porting paranoid android rom for our phone Star N8000..??
Sent from my Star N8000..

dangk said:
Hi sir.. thanks for your sharing.. i use this rom from a mont h ago... its running stable.. can you porting paranoid android rom for our phone Star N8000..??
Sent from my Star N8000..
Click to expand...
Click to collapse
Me? I'm sorry ... I've never tried porting anything before.

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.

Lenovo S8 A7600 [Official Rom] [Instructions]

Hello
Seeing there is very little info about this model, I decided to make available my findings. Initially I was a bit annoyed with the phone in the start. The "stock" rom was a disaster (malware-ridden, non-official). First I tried to de-bloat that but the whole rom was just bad and unstable. Since then I've learned some things, and newer official builds have surfaced.
Also I should say; this phone is basically a K3 Note with 720p screen (another difference is MT6752M cpu instead of MT6752 in the K3 Note) and it's very similar to the A7000 model.
The best rom I have tried so far is this : VIBEUI_V2.5_1532_5.1797.1_ST_A7600_CU ---> DL - This is latest official stock Rom for the 7600 (not 7600M which is Chinese version)
Here is also TWRP recovery with english + chinese language: DL
Rename ROM to "update.zip", use stock recovery and flash (probably best to use stock lenovo recovery first to make sure everything gets flashed, can be flashed with twrp but I suspect it only flashes boot and system), boot it up, finish the setup wizard, turn it off. Use SPflashtool to flash TWRP, turn off again.
Start phone in recovery mode (Press volume Up + Down, and power button. Hold until recovery appears). Now you can flash Gapps (arm64, lollipop 5.0, opengapps.org), SuperSU, xposed arm64 lollipop, etc.
I have been able to get a very pleasing phone doing this. I don't really feel right now that much is missing, and I'm not annoyed by various other problems. Using xposed modules gravity box, GEL settings, Lollipop memory fix, etc.
This Rom has very little bloatware, there are some chinese apps, but they can easily be uninstalled - don't even need root. There are a few more you can uninstall using root if you want, but be careful not to break the system.
I'm not going to explain everything in great detail here. Using SPFlashTool is explained so many other places. Getting supersu and xposed also explained everywhere.
If I could I would integrate all in to one flashable package, but I'm not a rom cooker. Sorry
PS: As you can see in the image, i use iFONT xposed. But I don't enable it as xposed module, that caused problems. I just used it to download a font and applied it. It's system wide, and it works
There's a newer link in post #6 with the latest firmware
There's a newer link in post #10 with TWRP 3.0.2.3

Hi,do you have custom rom for lenovo s8 a7600?

askermk2000 said:
Hello
The best rom I have tried so far is this : VIBEUI_V2.5_1532_5.1797.1_ST_A7600_CU ---> - This is latest official stock Rom for the 7600 (not 7600M which is Chinese version)
Here is also TWRP recovery with english + chinese language:
Click to expand...
Click to collapse
sorry, I had to remove your links, because I have small amount of posts and I am not allowed to submit post with urls - even if quoted.
Hi!
Do you know way to install other languages into ROM (or add them and somehow rebuild ROM), I am searching informations for last few days with no succes. The main problem is when international apps using EN for directory, when all information in directory should be in my language (polish). Changing locale helps, but settings are crashing with changed locales..
Also I installed xposed, but system tells me that xposed is not installed... I heard about it from your post and found only version v79 for sdk 21. I need to remove search box from desktop at google now.

Any custom rom for this device ?

Hi everyone, hi @askermk2000
I just received my Lenovo S8 A7600 "Golden Warrior" phone from an Asian vendor, it came with VIBEUI_V2.5_1524_5.1460.1_ST_A7600_CU and SuperSU was seemingly installed when I first turned on phone (asked me to update binary).
Specs are MTK6752M 64-bit OctaCore, 2GB RAM, 8GB storage.
Can I install your version VIBEUI_V2.5_1532_5.1797.1_ST_A7600_CU through the Lenovo stock recovery/flash (phone) as you suggest?
You mention "not 7600M" so I am not sure...
I also see in other places that there's even a newer VibeUI version VIBEUI_V2.5_1537_5.1978.1_ST_A7600_CU, any idea where to get it and if it is compatible? I cannot find any download link...
Thanks...

konsti said:
Hi everyone, hi @askermk2000
I just received my Lenovo S8 A7600 "Golden Warrior" phone from an Asian vendor, it came with VIBEUI_V2.5_1524_5.1460.1_ST_A7600_CU and SuperSU was seemingly installed when I first turned on phone (asked me to update binary).
Specs are MTK6752M 64-bit OctaCore, 2GB RAM, 8GB storage.
Can I install your version VIBEUI_V2.5_1532_5.1797.1_ST_A7600_CU through the Lenovo stock recovery/flash (phone) as you suggest?
You mention "not 7600M" so I am not sure...
I also see in other places that there's even a newer VibeUI version VIBEUI_V2.5_1537_5.1978.1_ST_A7600_CU, any idea where to get it and if it is compatible? I cannot find any download link...
Thanks...
Click to expand...
Click to collapse
Hello
It's wise of you to remove that dubious vendor firmware.
Since "A7600M" is a model number, or simply name of the phone, I would be surprised if it doesn't say so anywhere. Look at the packaging, phone and battery compartment etc. If you don't see A7600M anywhere, it's likely not that model.
See here: Lenovo Inquiry Page
At the bottom there you'll find link for the latest official (Full) firmware.

Thank you @askermk2000 for your kind and immediate reply.
This known asian vendor on their page mentions: Lenovo "Golden Warrior" S8 A7600, 4G, LTE, MTK6752M @1.5GHz 64bit OctaCore, 2GB RAM, 8GB storage, 5.5inch HD IPS screen, OTG, Android 5.0 Phone
In settings, the ROM version is: VIBEUI_V2.5_1524_5.1460.1_ST_A7600_CU, no bloatware; was surprised to see SuperSU pre-installed but the vendor does have a service (at a cost) to provide pre-rooted phones (which I did NOT order but maybe got).
The (Lenovo) box doesn't mention much, even under the phone I can see a lot of Chinese, so it's definitely for China -- vendor wrote it's unlocked for world use on their page.
The mentioned model is A7600 on the rear, there's only a A838 reference besides model (i.e. QQ-A838-xxxxxx) but not much more than that.
I suspect these may be older stock they wanted to get rid of.
As you can see, the model is (S8) A7600, not A7600M. The chipset has "M" i.e. is MTK6752M.
So can I not use the official latest (full) firmware that you posted, via stock recovery?
Is this not for MTK6752M processor? Will this firmware brick the phone, you think?
Thank you very much in advance!

konsti said:
Thank you @askermk2000 for your kind and immediate reply.
This known asian vendor on their page mentions: Lenovo "Golden Warrior" S8 A7600, 4G, LTE, MTK6752M @1.5GHz 64bit OctaCore, 2GB RAM, 8GB storage, 5.5inch HD IPS screen, OTG, Android 5.0 Phone
In settings, the ROM version is: VIBEUI_V2.5_1524_5.1460.1_ST_A7600_CU, no bloatware; was surprised to see SuperSU pre-installed but the vendor does have a service (at a cost) to provide pre-rooted phones (which I did NOT order but maybe got).
The (Lenovo) box doesn't mention much, even under the phone I can see a lot of Chinese, so it's definitely for China -- vendor wrote it's unlocked for world use on their page.
The mentioned model is A7600 on the rear, there's only a A838 reference besides model (i.e. QQ-A838-xxxxxx) but not much more than that.
I suspect these may be older stock they wanted to get rid of.
As you can see, the model is (S8) A7600, not A7600M. The chipset has "M" i.e. is MTK6752M.
So can I not use the official latest (full) firmware that you posted, via stock recovery?
Is this not for MTK6752M processor? Will this firmware brick the phone, you think?
Thank you very much in advance!
Click to expand...
Click to collapse
No, your phone is the right model, as you said "Unlocked for world use", the A7600M only works in china.
MTK6752M is the chipset used - it has nothing to do with A7600M, that there are two M's there is a coincidence.
So you can go ahead and use the latest firmware.

OK for the sake of information to everyone, I did the following:
0. Formatted SD card from within the phone (just to be sure). Then charged battery fully to 100%.
1. Copy (via PC) the latest firmware zip file (currently is VIBEUI_V2.5_1628_5.2186.1_ST_A7600_CU_WC5DAF1811.zip about 1GB size) to root of my SD card. This file looks like a recovery type, but files inside (some IMG, DAT and scatter files) could be flashable from PC (i.e. like SP Flash Tool etc.).
2. Renamed it update.zip
3. Put SD and battery back to phone.
4. Started phone in recovery mode: Pressed Volume Up + Down and Power buttons simultaneously; held them until recovery screen appeared. First, Lenovo logo, then a screen to choose language (Chinese/English); pressed English.
5. Selected the Install Upgrade Pack menu and pressed "YES" to the warning about encrypted phones.
6. Waited for update with circle-type update progress; for some reason it got seemingly stuck at 75% for some period. Waited patiently to finish.
7. I selected "Back" to go and clean user data.
8. Once done, I pressed back touch-button and selected "Restart".
9. Waited to see what happens. Was curiously greeted with a white chinese splash-screen saying "4G" something. Waited...
10. Phone next booted to the usual Lenovo logo, with some chinese text at the bottom and three dots [...] flashing with thin white progress-line (most likely "rebuilding apps"?). This took a while, too.
11. The phone finally went into the wizard in Chinese, and then offered choice of English or Chinese as wizard language.
Wizard finished OK, then went to Settings -> About device -> ROM is upgraded indeed to VibeUI v2.5-1628 and Android 5.0.2.
NOTE: There's a LOT of chinese stuff, unfortunately, I guess it's part of the ROM; obviously this ROM is non-rooted...
However, the asian vendor installed/shipped ROM (VIBEUI_V2.5_1524_5.1460.1_ST_A7600_CU) was very light and fast -- I guess a deodex version? Or a VibeUI port?
Many thanks @askermk2000 for your help nevertheless.
Any idea, compared to your experience., if...
a) if your URL for latest firmware is maybe only for China? Your first post photos/screenshots don't have such Chinese apps On this ROM version, the shutdown logo is again that white chinese splash-screen with a big red "4G". Perhaps there's some other version for non-Chinese region?
b) if there's a stock, deodex ROM like that one? How did the Asian vendor find such light ROM, I am curious -- in that shipped ROM version, I had many menu languages. Now I only have English and Chinese as choices
c) if I need TWRP so I can flash Play Store, gapps and SuperSU? I don't think stock Recovery allows for these, any idea?
Cheers mate.

konsti said:
OK for the sake of information to everyone, I did the following:
0. Formatted SD card from within the phone (just to be sure). Then charged battery fully to 100%.
1. Copy (via PC) the latest firmware zip file (currently is VIBEUI_V2.5_1628_5.2186.1_ST_A7600_CU_WC5DAF1811.zip about 1GB size) to root of my SD card. This file looks like a recovery type, but files inside (some IMG, DAT and scatter files) could be flashable from PC (i.e. like SP Flash Tool etc.).
2. Renamed it update.zip
3. Put SD and battery back to phone.
4. Started phone in recovery mode: Pressed Volume Up + Down and Power buttons simultaneously; held them until recovery screen appeared. First, Lenovo logo, then a screen to choose language (Chinese/English); pressed English.
5. Selected the Install Upgrade Pack menu and pressed "YES" to the warning about encrypted phones.
6. Waited for update with circle-type update progress; for some reason it got seemingly stuck at 75% for some period. Waited patiently to finish.
7. I selected "Back" to go and clean user data.
8. Once done, I pressed back touch-button and selected "Restart".
9. Waited to see what happens. Was curiously greeted with a white chinese splash-screen saying "4G" something. Waited...
10. Phone next booted to the usual Lenovo logo, with some chinese text at the bottom and three dots [...] flashing with thin white progress-line (most likely "rebuilding apps"?). This took a while, too.
11. The phone finally went into the wizard in Chinese, and then offered choice of English or Chinese as wizard language.
Wizard finishedOK, then went to Settings -> About device -> ROM is upgraded indeed to VibeUI v2.5-1628 and Android 5.0.2.
There's a LOT of chinese stuff, unfortunately, I guess it's part of the ROM; obviously this ROM is non-rooted.
But the installed/shipped ROM (VIBEUI_V2.5_1524_5.1460.1_ST_A7600_CU) was very light and fast -- I guess a deodex version? Or a VibeUI port?
Many thanks @askermk2000 for your help nevertheless. Your photos/screenshots however don't have such Chinese apps...
Any idea, compared to your experience., if...
a) if your linked latest firmware is maybe only for China? The shutdown logo is again that white chinese splash-screen with a big red "4G". Perhaps there's some other version for non-Chinese region?
b) if there's a stock, deodex ROM like that one? How did the Asian vendor find such light ROM, I am curious -- in that shipped ROM version, I had many menu languages. Now I only have English and Chinese as choices
c) if I need TWRP so I can flash Play Store, gapps and SuperSU? I don't think stock Recovery allows for these, any idea?
Cheers mate.
Click to expand...
Click to collapse
Hello again
Yes, the official Chinese rom only has Eng/Chinese language. There may be a way to add more, idk because I only need English. The 4G boot logo is normal, was there on the rom linked in the first post also.
All the Chinese apps (or almost all) can be uninstalled without root permission. I never experience the rom to be less than fast and good, but I always immediately uninstalled the chinese apps, they do me no good anyways.
The rom you where supplied with is what is called ROW (international). If it's possible to get an updated ROW rom idk. All I know is that if you want a clean unhampered ROM, then the one I've shown you is the way to go.
PS: Yes you need custom recovery to flash the other stuff. Here is an updated TWRP: TWRP-3.0.2.3
^^This recovery has wrong device description in build.prop (actually it uses Lenovo K3) as a consequence you will receive error if trying to flash ROM's. So try the old one if you get these errors.

HI everyone, hi @askermk2000 and many many thanks for sharing your TWRP version 3.0.2.3 with us.
I followed this thread on how to root the Lenovo S8 A7600 phone and downloaded the tools needed (SP Flash Tool v5.1452.00 and VCOM drivers) on my Windows 7 laptop; then, installed them accordingly. Many thanks to @XxpikaachuuxX for providing links and steps on his thread!
1. Started up SP Flash Tool with administrator rights.
2. Chose the scatter file that was inside your shared TWRP-3.0.2.3 zip file; recovery image is automatically selected.
3. Shut down phone, remove battery.
4. Made sure all boxes in list were unchecked, except "recovery" then pressed "Download" button.
5 . Plugged phone on USB cable to PC, then inserted battery under the phone, as instructed.
6. Windows made a "USB plugged" sound, then SP Flash Tool detected phone OK and flashed recovery fine (there was the green tick-mark shown!)
7. Removed cable, removed battery, waited 10 seconds, re-inserted battery.
Then, copied to my SD card root folder, via PC (card reader) the following:
a) UPDATE-SuperSU-v2.46.zip
b) gapps-lp-20150211-signed.zip from this thread (lp=Lollipop)
(I had downloaded and installed wrong Gapps for 5.1 Android, but we need 5.0 version for this ROM--silly me. I just re-flashed via TWRP the correct package).
Went into recovery by pressing briefly Power then when the short vibration was felt, pressed VOL+ and VOL- and POWER simultaneously; the pleasant splash-screen of TWRP was shown!
1. Installed the needed SuperSU; then went back.
2. Installed gapps.
3. Wiped cache and Davlik (inside TWRP) then rebooted phone i.e. "system".
4. Waited patiently as it took a few minutes to go on the main Home screen.
5. Created Google account in "Settings" then went straight to "PlayStore" to update all applications, including SuperSU.
6. Ran SuperSU and upon request, updated the binary "normally" and rebooted just fine.
NOTE: In the Wi-Fi detected lists, since my first ever boot of this phone, I get a (fake?) SSID entry "NVRAM WARNING: Err = 0x10" which is apparently easily fixed for other phones. Do you guys you also got that?
A bunch of final questions to you, @askermk2000 when you have time to reply.
1) Does the stock weather display on a Home page work for you? I only get Chinese cities, location doesn't work as it says "city not found". Manual input of e.g. Europe cities doesn't show results, either.
2) Despite removing most via "Settings -> App Manager", any suggestions oh how to remove some further chinese apps that are marked "system app"? This article suggests NoBloat Free, Titanium Backup, System App Remover and App Master. I am not familiar with this approach but for example, "LenovoStore" could be removed...
3) Do you have by any chance the original, black b/g, folding (yes, boring) Lenovo animation boot logo to share? I see there's a file logo.bin for SP Flash Tools but others talk about /system/media/bootanimation.zip file... I ask if you have it, as the "Boot Animations" PlayStore app may not have the stock Lenovo boot. Perhaps flashing it via SP Flash Tool is better?
4) Will you kindly share any updates here to TWRP versions, whenever released? Do you anticipate any update in the coming 1-2 months, for example? (not sure there are bugs in TWRP-3.0.2.3, if any)
5) If there is a newer Lenovo official ROM available (than today) we obviously lose the TWRP recovery if we flash it all via SP Flash Tools; but we keep TWRP recovery if we update to the new ROM via TWRP, correct?
Thank you.

konsti said:
HI everyone, hi @askermk2000 and many many thanks for sharing your TWRP version 3.0.2.3 with us.
I followed this thread on how to root the Lenovo S8 A7600 phone and downloaded the tools needed (SP Flash Tool v5.1452.00 and VCOM drivers) on my Windows 7 laptop; then, installed them accordingly. Many thanks to @XxpikaachuuxX for providing links and steps on his thread!
1. Started up SP Flash Tool with administrator rights.
2. Chose the scatter file that was inside your shared TWRP-3.0.2.3 zip file; recovery image is automatically selected.
3. Shut down phone, remove battery.
4. Made sure all boxes in list were unchecked, except "recovery" then pressed "Download" button.
5 . Plugged phone on USB cable to PC, then inserted battery under the phone, as instructed.
6. Windows made a "USB plugged" sound, then SP Flash Tool detected phone OK and flashed recovery fine (there was the green tick-mark shown!)
7. Removed cable, removed battery, waited 10 seconds, re-inserted battery.
Then, copied to my SD card root folder, via PC (card reader) the following:
a) UPDATE-SuperSU-v2.46.zip
b) gapps-lp-20150211-signed.zip from this thread (lp=Lollipop)
(I had downloaded and installed wrong Gapps for 5.1 Android, but we need 5.0 version for this ROM--silly me. I just re-flashed via TWRP the correct package).
Went into recovery by pressing briefly Power then when the short vibration was felt, pressed VOL+ and VOL- and POWER simultaneously; the pleasant splash-screen of TWRP was shown!
1. Installed the needed SuperSU; then went back.
2. Installed gapps.
3. Wiped cache and Davlik (inside TWRP) then rebooted phone i.e. "system".
4. Waited patiently as it took a few minutes to go on the main Home screen.
5. Created Google account in "Settings" then went straight to "PlayStore" to update all applications, including SuperSU.
6. Ran SuperSU and upon request, updated the binary "normally" and rebooted just fine.
NOTE: In the Wi-Fi detected lists, since my first ever boot of this phone, I get a (fake?) SSID entry "NVRAM WARNING: Err = 0x10" which is apparently easily fixed for other phones. Do you guys you also got that?
A bunch of final questions to you, @askermk2000 when you have time to reply.
1) Does the stock weather display on a Home page work for you? I only get Chinese cities, location doesn't work as it says "city not found". Manual input of e.g. Europe cities doesn't show results, either.
2) Despite removing most via "Settings -> App Manager", any suggestions oh how to remove some further chinese apps that are marked "system app"? This article suggests NoBloat Free, Titanium Backup, System App Remover and App Master. I am not familiar with this approach but for example, "LenovoStore" could be removed...
3) Do you have by any chance the original, black b/g, folding (yes, boring) Lenovo animation boot logo to share? I see there's a file logo.bin for SP Flash Tools but others talk about /system/media/bootanimation.zip file... I ask if you have it, as the "Boot Animations" PlayStore app may not have the stock Lenovo boot. Perhaps flashing it via SP Flash Tool is better?
4) Will you kindly share any updates here to TWRP versions, whenever released? Do you anticipate any update in the coming 1-2 months, for example? (not sure there are bugs in TWRP-3.0.2.3, if any)
5) If there is a newer Lenovo official ROM available (than today) we obviously lose the TWRP recovery if we flash it all via SP Flash Tools; but we keep TWRP recovery if we update to the new ROM via TWRP, correct?
Thank you.
Click to expand...
Click to collapse
About that Wi-Fi problem. No I don't have it, and I was reading that page with the fix. It seems it's caused by using wrong settings in SPFlashtool, so likely the vendor did this when applying his trash firmware.
If you wifi is not working (as some reported in that thread) I would of course try to get a refund.
Weather gadget only has Chinese cities, yes I noticed that so I was using yahoo weather instead on my phone.
I would suggest Titanium Backup, it's what I use.
No, sorry I don't have any boot logos or animations.
This phone is a bit slow on the updates. But if there's an update, you can do it through the OTA update function which only downloads the changes as a patch. Though If your phone is heavily modified it might not work correctly. Could try a factory reset first, or simply start a fresh.
Then you would probably need to download the original recovery and flash that first.
PS: You can break the system by removing too much of the lenovo stuff. Remember VibeUi is heavily integrated and impossible to remove completely. Also, for gapps go to www.opengapps.org

help
Can you help me a bit? I got an infected phone and i need to install a new rom to keep myself safe. (im kinda noob to installing stuff like these)

First bootanimation "china4Gchina", second ok and poweroff ok.
Please help to change to first animation or delete.
Thanks.

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...