Related
Hi!
First off, if I have posted in the wrong place, I am sorry and if necessary please move to relevant location!
Right, I have had a major problem with my HTC Desire, I spent all day & night yesterday trying to fix!
I rebooted the device as it was running short of memory, then phone just got stuck on the white HTC boot screen & wouldnt move from that, so I restored a backup of the phone using Nandroid, but I had the same result, fine I thought, Id just download a RUU to reflash the device, this didnt work and came up with errors, BUT what I did manage to do is take the rom.zip and make a new ROM in Cygwin which flashed perfectly and I ended up with a stock 2.2 and all seemed to be back to normal, so I then tried to restore a backup again, but same problem, white HTC screen so I have came to the conclusion that I will have to TRY to re-create my old ROM & settings using this stock ROM!
So far I have managed to root the ROM & add everything that my old ROM had (was using the latest Lee Droid ROM - man big respect to you for what you do!!) but there are a few things missing which I do not know about and this is where I need all your help with!
Below are the bits I desperately need including with the ROM (my phone wont install any other ROMS other than the stock 2.2 I said earlier) I am not expecting the members here to do it all for me, BUT if you could point me in the right direction to either the posts with directions for what I need or other places where I can find the bits & how to do it!
*** Wireless N support (my router is N & so are the other wireless devices)
*** An overclocked kernel (such as Lee Droid's V2.2e_A2SD ROM)
*** The ability to wake up & unlock the phone with the optical thumb trackpad
*** The reboot option when long press on unlock button (ideally the nice, clear menu that includes Hibernate from the new HD ROMS)
*** Branding & naming the ROM (as Lee Droid does on his ROMS)
*** Custom wallpapers instead of stock wallpapers
I am sorry for the long post, but I really NEED this completed ASAP and I know with all your help, I can do it!
Also, I am making a simple program on my PC to custom ROMS (add & delete apps, alarms, ringtones & notifications etc) which I will upload for the community when it has been completed & working 100%!
Thanks in advance & I hope that you can find it in your hearts to help me!
Arty
I don't think nandroid restores the kernel. After you do a restore with it, you need to flash a kernel that is compatible with the rom being restored.
Personally, when I restore I backup on my phone, I reinstall the rom and then just restore /data from my nandroid backup.
Thanks for your fast reply DiGi760, however I think you misunderstand!
I need a kernel that supports overclocking the CPU as I use SetCPU and so far its just the standard 998MHZ I can set the clock to, where I would like it to be higher, like 1038MHZ or whatever it is
Your backup copy is broken. You can't "really" recover from this. Just reflash 2.2 and update it to whatever you had before and start over. You may be able to manually pull stuff from your SD card where the nandroid backup was written to but that would be a tedious amount of work.
Thanks Syn Ack, why would the backup AND the info on my phone corrupt at the same time?
I do actually have a copy of the Clockwork folder from memory card stored onto my PC, but none of the backups will restore (I have a total of 10 going back a few months) but none will restore, not even any other ROMS that Ive downloaded with ROM Manager or from forums will install to it, only the 2.2 ROM that came with the RUU file I downloaded.
An update on my progress of making my new ROM:
I have managed to get the Reboot menu integrated into my ROM, so now I am just stuck on the following:
Wireless N support
Overclocked Kernel
Unlock the phone with trackpad
Branding & naming
Custom wallpapers
so if anybody can help me I'd really appreciate it!
Wow, its been over a week and no replies, why cant anybody see it in themselves to help? after all, you all was newbies once too, just remember how you felt when nobody answered a post you *REALLY* needed help with!!!
Just saying
Gees thanks for nothing u lot!!!!
This is an extremely simple ROM modification to the standard Advent Vega 1.10 system image that only alters a couple of things. These are as follows:
/system partition size increased from 128mb to 155mb. (The reason for this will be explained below)
su and SuperUser.apk added - You can use root apps as standard now.
ClockworkMod Recovery built-in.
Added Pauls simple recovery reboot app to get into CWM recovery.
That's all! No google apps, nothing else, just these simple changes. This isn't intended to be used as an everyday ROM (although there is no reason why you couldn't).
The main reason for this, is to be used as ROM base for VegaComb (and any other ROM you wish to use). I have been struggling with the Vega's default partition sizes while trying to port Honeycomb, and rather than spending tons of time trying to make stuff way smaller than it was ever intended to be, this seems like the better option.
So, flash this in nVflash recovery mode (exactly the same as the stock 1.10 image) and off you go. Done. No need to do anything else. You can use this base with any ROM, the ONLY downside is that 30mb of storage has been re-allocated from /data to /system, which most people won't even notice.
ALL future versions of VegaComb will require that you use this modded system image as a base (as they will require more than 125mb of /system space). To return your partitions back to the way they were, just re-flash the stock 1.10 image from www.myadventvega.co.uk (this is the ONLY way to restore your partition sizes, restoring from a Nandroid backup will NOT change your partition sizes back). You DON'T have to return to stock when you want to switch from using VegaComb, all other ROMs should work perfectly fine on top of this base, including Corvus5 and CM7.
Also, it's handy to have this in case you brick your Vega as CWM is pre-installed
AS ALWAYS MAKE SURE YOU NANDROID BACKUP BEFORE FLASHING ANYTHING!
Download ModdedStock_1.10 v2 Here!
Woo Hoo, good sign for things to come
Good work, Love the idea of a bigger /system..saves a lot of messing around moving apps to /data. Cheers. Paul
Just can't get this to install :-(
Keeps coming up with unknown device found!!
Ooops, forgot to plug the charger in.........sorry :-(
I use ubuntu will this work through wine or would i be better off trying to borrow a windows MC
Flash without usb cable?
Is there a way to flash this ROM without using the USB cable and recovery mode since my VPAD10s is giving a huge pain with windows 7 and the driver so I can not make it work.
Is there a version to be used with rom manager?
Thanks guys.
You need to use your PC because this ROM changes the partition sizes in the internal memory, and you need a PC program (nvflash) for that purpose.
Damn! thanks Logseman, I will keep on trying to get my tablet recognized over w7 can´t believe it´s so hard to make it work. wish me luck
Hope over to the Modaco Vega forum and search for YAUDIG and AUDI. They'll get the drivers installed for you.
simonta said:
Hope over to the Modaco Vega forum and search for YAUDIG and AUDI. They'll get the drivers installed for you.
Click to expand...
Click to collapse
Thanks simonta, already tried AUDI´s soft but no luck.
I´m starting to think that the issue might be with my pc/w7.
Great stuff!
Rgds
Lok
Hi:
Currently using vegacomb 0.6, i want to nandroid backup, install the new Rom base, then nandroid restore, and then upgrade to vegacomb 0.7 via the upgrade patch, in order not to loose all my settings.
So I would like to do a Nandroid backup, but being Android illiterate, i havent found how to do it in vegacomb 0.7.
Another question is , as I have moved most apps to SD, if there would be any problem regarding the base rom change and nandroid bacup-restore
Thanks for any hint/pointer
Which gapps should I use it for this built?
Zebwen said:
This is an extremely simple ROM modification to the standard Advent Vega 1.10 system image that only alters a couple of things. These are as follows:
/system partition size increased from 128mb to 155mb. (The reason for this will be explained below)
su and SuperUser.apk added - You can use root apps as standard now.
ClockworkMod Recovery built-in.
Added Pauls simple recovery reboot app to get into CWM recovery.
That's all! No google apps, nothing else, just these simple changes. This isn't intended to be used as an everyday ROM (although there is no reason why you couldn't).
The main reason for this, is to be used as ROM base for VegaComb (and any other ROM you wish to use). I have been struggling with the Vega's default partition sizes while trying to port Honeycomb, and rather than spending tons of time trying to make stuff way smaller than it was ever intended to be, this seems like the better option.
So, flash this in nVflash recovery mode (exactly the same as the stock 1.10 image) and off you go. Done. No need to do anything else. You can use this base with any ROM, the ONLY downside is that 30mb of storage has been re-allocated from /data to /system, which most people won't even notice.
ALL future versions of VegaComb will require that you use this modded system image as a base (as they will require more than 125mb of /system space). To return your partitions back to the way they were, just re-flash the stock 1.10 image from www.myadventvega.co.uk (this is the ONLY way to restore your partition sizes, restoring from a Nandroid backup will NOT change your partition sizes back). You DON'T have to return to stock when you want to switch from using VegaComb, all other ROMs should work perfectly fine on top of this base, including Corvus5 and CM7.
Also, it's handy to have this in case you brick your Vega as CWM is pre-installed
AS ALWAYS MAKE SURE YOU NANDROID BACKUP BEFORE FLASHING ANYTHING!
Download ModdedStock_1.10 v2 Here!
Click to expand...
Click to collapse
Thanks. one questions. Which gapps should I use for this built?
Thanks again.
hi, can i flashed this rom using CWM?
No, you can only flash it using a pc.
@all
Can someone please tell me how to use the nvflash, cause i'm clueless. I've searched using google but no luck, even on YouTube. I've downloaded nvflash but I can't work it. It keeps telling me about the drivers, although I installed the drivers. Any help would be great.
Thank you in advance.
jayk32 said:
@all
Can someone please tell me how to use the nvflash, cause i'm clueless. I've searched using google but no luck, even on YouTube. I've downloaded nvflash but I can't work it. It keeps telling me about the drivers, although I installed the drivers. Any help would be great.
Thank you in advance.
Click to expand...
Click to collapse
Hi
Switch off your Vega.
Connect it to the PC with the USB Cable.
Hold the power button on the Vega for 2 secs
Hold the back button while still holding the power button for a further 2 secs.
Release the power button but keep holding the back button for a further 2 secs.
You should now have a black screen and the Vega should be recognized on your PC (check in Control panel under USB for Nvidia Harmony or Shuttle)
The above assumes that you have installed the drivers.
Then open Modded Stock v1 or 2 which you should have already downloaded to the PC and it will install on the Vega (Vega will show NV Flash mopde across the top of the screen)
Once Modded stock is installed go to the apps menu and the recovery app is there. If you have already downloaded and put on your SD Card, the Vegacomb 9n Rom run the recovery and it will put you into CWM.
Wipe data, cache and in advanced the Dalvik cache.
Then select install from SD card and select the Rom and it will install.
If you continue to have problems Google Vegatools 4.1 and download and install
and it can do all the hard work.
Hope this helps
Stransky
Hi guys, sorry to hijack the thread an take it slightly off course but........
Buy flashing this stock modded rom, will it reset my touch screen issues? Read that its a pretty common problem.
I've tried the fix at modaco, and it works.......for a very brief period, then back to just half of my landscape screen being recognized?
I've only had my Vega a week, can any other of you more experianced fellows point me towards a fix? It would be much appreciated.
Sent from my VegaComb using xda premium
Thanks for a awesome rom.One questions,having problems with the sensor.Is there a simple solution to this?i have wiped dalvic cache but didnt help.I want to play games like NFS Shift and ather other games with sensor abilities.
Why not use Custom MTD ?
http://forum.xda-developers.com/showthread.php?t=717874
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.
Hi
I have a Samsung Galaxy GT-I5801 with me for past couple of years.
Its current OS spec are:
Firmware version- 2.2
Baseband version- I5801DDJP2
Kernel version- 2.6.32.9 [email protected] #2
Build Number- FROYO.DDJP6
My phone has become kind of slow, like for even basic tasks like opening call log or messaging app, it takes good 10-15 seconds. Sometimes it even goes unresponsive when trying to end a call thus causing call to continue thus carrier balance reduction. There are no 3rd party apps installed on it. Even updating the pre-installed apps gives the message of memory being low.
Now my query is:
Will flashing it to a custom ROM will improve its working at least in the basic areas of call and texting?
If so, then which is the most suitable custom ROM?
Is it necessary to root the phone before flashing it ?
Which tool is best/easiest for said purposes?
Please go easy on me, I've been out of the IT and tech game since past 1 year and bit rusty on these things
RudraP said:
Will flashing it to a custom ROM will improve its working at least in the basic areas of call and texting?
If so, then which is the most suitable custom ROM?
Is it necessary to root the phone before flashing it ?
Which tool is best/easiest for said purposes?
Click to expand...
Click to collapse
I would say yes. I don't know what is causing the freezes, but (beside that this could also be a hardware problem) a custom ROM should fix that.
Any GB-based ROM should do a fine job. There are also Froyo-based ROMs for our device. The CM7.2 build by marcellusbe does a very good job.
Nope. If you flash via Odin (Flash-Software for Windows) you just need a usb-connection. If you flash it via recovery, you may need to flash a custom recovery first.
Derp - another proud Galaxy3 user :highfive:
DerpyDerp said:
I would say yes. I don't know what is causing the freezes, but (beside that this could also be a hardware problem) a custom ROM should fix that.
Any GB-based ROM should do a fine job. There are also Froyo-based ROMs for our device. The CM7.2 build by marcellusbe does a very good job.
Nope. If you flash via Odin (Flash-Software for Windows) you just need a usb-connection. If you flash it via recovery, you may need to flash a custom recovery first.
Derp - another proud Galaxy3 user :highfive:
Click to expand...
Click to collapse
I tried SuperOneClick but it failed to even detect my phone, let alone root. Tried rooting directly through phone by installing z4root on it. It too failed to root my device, just a blue screen saying "Running Exploit" with z4mod logo kept on displaying for 10-15 minutes, after which phone switched off itself. Had to power it back on myself. Tried it couple of times more but no success.
So now if I use Odin to directly flash the firmware to a modded one, would it work, considering the fact that the phone hasn't been rooted. More importantly, would it be wise to do so? Don't want to hard brick the device as its my backup device after my Xperia SP took a plunge in the water and now fails to even boot, just vibrates thrice and that's it.
Update:
Took a leap of faith with Odin and Cyanogen & now the device is rockin' like a grandma with a new hip replacement Lags no more, operation is smooth, but a 2nd minor problem has cropped up.
It now refuses to install any app from Play Store citing Insufficient Space. I changed the default installation space to external but still the problem persists.
Update 2:
For my above mentioned problem, looks like something to do with Gapps but I don't know what it is and what to do about it. Moreover as today I tried to make calls or send messages, I found out I'm unable to do so. The dialler dials after good 2-3 minutes of pressing/selecting the dial option for a number while message inbox is empty but it refuses the receive any sms citing Inbox is full. I thought just flashing the firmware should do the trick but looks like it just was the tip of the iceberg.
You can find the gapps (Google Apps - like Play Store, Gmail, ...) here:
http://goo.im/gapps/
Assuming you're on Gingerbread (CM 7.x) it's this package: http://goo.im/gapps/gapps-gb-20110828-signed.zip
Put this zip-file on your SD card, power off your phone and/or reboot to recovery. Navigate to "Select zip from sd card" -> select your gapps.zip and flash. Then "wipe cache" and "wipe dalvik cache" anywhere in the submenus Just to make sure the gapps get recognized correctly.
Another trick for expanding the internal storage is Link2SD. You need a 2-partition sd-card for this. 1. partition with FAT and 2. one with ext2/3/4
Link2SD will mount this second partition to the internal storage to expand your storage for apps and other system stuff.
You know... Getting the most of a half-dead low-end device needs a bit of geekiness
bad zip
Well I selected erase all data option in the phone which booted it into recovery mode. Here I cleared the cache and the user data. When I tried to install zip file from sd card it gave the following error message, "Can't open /sdcard/gapps-gb-20110828-signed.zip (bad) Installation Aborted"
What seems to be the problem now?
Update:
Tried again and this time it worked. Now everything is running fine. Thanks a ton for the help mate, can't express my gratitude through words.
I do want to ask one thing here.
If I install this, http://forum.xda-developers.com/showthread.php?t=1803180, will the JB experience be coupled with performance drop ?
Honestly Cyanogen has turned me into a junkie, now I want to try on the new but stable mods. Moreover as my Xperia SP is now out of warranty, I'm planning to get it fixed and then root and flash it too!
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.