Related
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.
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.
STOCK ANDROID 6.0 MARSHMALLOW ROM
FOR THE LENOVO TAB 3 8"/TB3-850F
TWRP FLASHABLE ZIP
FORCE ENCRYPTION & DM-VERITY DISABLED
DISCLAIMER: Your warranty will be voided by installing this ROM, unlocking your bootloader, or flashing a custom recovery. You hereby assume sole responsibility for any positive or negative consequences incurred by flashing this ROM. As always, flashing your Android device or otherwise altering its file system & partitions involves an inherent risk. I am not responsible for any devices which are bricked or otherwise rendered inoperable as a result of flashing this ROM. However, in such scenarios,
I will provide all support feasibly possible. Follow the simple instructions carefully and you should experience no adverse affects.
Lenovo's open source code for this ROM encompasses both the 850F & 850M variants of this tablet. Therefore, this ROM should be completely compatible with the TB3-850M as well.
NOTES:
This Stock Android 6.0 ROM is virtually unmodified. However, it should be noted that dm-verity (device mapping) and force encryption have been disabled via patched boot image. This is the most current stock OS for the Lenovo Tab 3 8"; therefore, no OTAs will need to be installed subsequent to flashing this ROM. In order to ensure that force encryption gets disabled, it is imperative that the /userdata (Data) partition is formatted in TWRP prior to Installation. Please carefully follow the below instructions.
For those members who want a pure stock experience, but also want root access of the stock OS, I'm currently compiling a deodexed & zipaligned version of this ROM, fully rooted with Magisk 14.0 & BusyBox binaries pre-installed.
SPECIFICATIONS:
Android Version: 6.0 Marshmallow
Build No: TB3-850F_S100031_171010_ROW
Kernel Version: 3.18.19
SDK Version: 23
Software Version: TB3-850F_160412
Build ID: MRA58K
Android Security Patch Level: 9/05/2017
Runtime Version: ART 2.1.0
Hardware Version: LenovoPad TB3-850F
Board Platform: MediaTek MT6735M
CPU: 64-Bit, Quad-Core Cortex A-53 - 1.0GHz
GPU: Mali T720 - 450MHz
RAM: 1GB
OS Build Date: 10/10/2017
Source Code: http://pcsupport.lenovo.com/us/en/products/tablets/a-series/tab3-8/downloads/ds112711
REQUIREMENTS:
1. Unlocked bootloader;
2. TWRP recovery;
This is a pure stock, unmodified, TWRP flashable Android 6.0 Marshmallow ROM for the Lenovo Tab 3 8". This ROM was compiled from the most recent stock /boot and /system images. However, as noted previously, the boot image has been unpacked, patched, and repacked in order to disable dm-verity and force encryption. Because raw firmware images were used in compiling this ROM, the file size is in excess of 1GB (approximately 1.35GB).
INSTRUCTIONS:
1. Download the ROM from the link provided and save it to your external micro SD card. Do not save to internal storage, as your /data partition will need to be formatted prior to installation;
2. Boot your tablet into TWRP recovery;
3. Wipe /system, /data, /cache & /Dalvik-ART cache. Also, select "Wipe", then "Format Data." This step is crucial to ensure disabling of force encryption. Please note that once installed, you may go to SETTINGS>>SECURITY and opt to encrypt the userdata on the tablet;
4. Select INSTALL, navigate to the location in which you saved the ROM zip file, and initiate installation. Flashing will complete in approximately 3 - 4 minutes;
5. Reboot system.
You should now have unmodified stock Android 6.0 installed on your Tab 3, as well as disabled dm-verity and disabled force encryption.
DOWNLOAD LINKS:
Stock Android 6.0 ROM --
TB3-850F_S100031_171010_ROW: https://drive.google.com/file/d/1iMf0Ns_XWGpYlNmXCvUsW_1DfaRMeIuO/view?usp=drivesdk
Stock Recovery Image: https://drive.google.com/file/d/1D6A7b080luzsSf0xLJSCqPBNeQLSWo94/view?usp=drivesdk
Unpatched Stock Boot Image: https://drive.google.com/file/d/1azgIrPbfJHBzZF9R4IUMxIGNga6vjipD/view?usp=drivesdk
Lenovo File Manager (APK): https://forum.xda-developers.com/android/general/app-lenovo-file-manager-lenovo-tab-3-8-t3706161
Lenovo Tab 3 8" User Guide --
TB3-850F & TB3-850M (English)(PDF): https://drive.google.com/file/d/18gCTfuZecJnlB0ddBIN02YPaDpuvmzov/view?usp=drivesdk
Older Build(s):
TB3-850F_S100030_161209_ROW: https://drive.google.com/file/d/0B1Sfod4HWfk2aTNtVmJHZGpWZEE/view?usp=drivesdk
BUGS: Please report any and all bugs, no matter how seemingly trivial or insignificant. For those members with the knowledge, please submit a proper bug report. If you are not sure how, simply provide as many facts & details as possible. If you are having problems with apps, please specify as to whether the app is from Google Play. Also, please DO NOT submit bug reports unless you are utilizing this ROM in its present form -- unmodified, pure stock. Custom kernels, mods & tweaks (e.g. Xposed framework) & any deviations from pure stock will make it futile to analyze bug reports. Instead, provide with detail the precise nature of the problem. If reporting a bug, please specify if you are rooted (systemless or system-mode) and/or have BusyBox binaries installed. Submit screenshots of bugs if possible.
Brilliant! Will download now and report back later. Thank you.
My custom ROM for this tablet should be coming out of the Android Kitchen later this evening. I've dubbed it Ethereal OS v1.1 [Android 6.0.1]. Extremely lightweight yet moderately feature packed.
MotoJunkie01 said:
My custom ROM for this tablet should be coming out of the Android Kitchen later this evening. I've dubbed it Ethereal OS v1.1 [Android 6.0.1]. Extremely lightweight yet moderately feature packed.
Click to expand...
Click to collapse
Nice!
After flashing the stock zip TWRP says unknown error. It booted up fine to where you login to your gmail and "bluetooth sharing has stopped working" pops up. Bluetooth can not be turned on within settings. I can not double swipe down to get to the notifications and the "Home" and "Recents" buttons do not seem to work although they both vibrate when pressed.
I will flash stock with SPFT and try your stock rom again.
stonedpsycho said:
Nice!
After flashing the stock zip TWRP says unknown error. It booted up fine to where you login to your gmail and "bluetooth sharing has stopped working" pops up. Bluetooth can not be turned on within settings. I can not double swipe down to get to the notifications and the "Home" and "Recents" buttons do not seem to work although they both vibrate when pressed.
I will flash stock with SPFT and try your stock rom again.
Click to expand...
Click to collapse
I got the same error with Bluetooth Share force closing two times at the setup screen. Probably a corruption issue during archiving the ROM. I'll do an md5 and archive the ROM again.
Seemed to work, however the loading images and screen is still lenovo. Also they lenovo apps are still there.
rongallant said:
Seemed to work, however the loading images and screen is still lenovo. Also they lenovo apps are still there.
Click to expand...
Click to collapse
This is not a custom ROM. This is pure stock. The Lenovo boot logo, boot animation & apps are supposed to be there. Like the title implies this an "Unmodified" stock ROM.
MotoJunkie01 said:
This is not a custom ROM. This is pure stock. The Lenovo boot logo, boot animation & apps are supposed to be there. Like the title implies this an "Unmodified" stock ROM.
Click to expand...
Click to collapse
My bad, understood.
On another note, I am finding it very buggy. The home and overview buttons do not work. They show you clicked it along with the haptic feedback, but nothing happens. The back button works and is the only way I know to get back to the home screen.
Also the tool panel you pull from the top stops working after a little while until I reboot. Then works for a little while.
The Play store downloads barely work. They show pending and nothing happens. I force quite, cleared the cache, disabled, reverted to the stock app and it works for a little bit. Then the other Play Store app comes back. Anyways, I am not complaining. I appreciate the work you put into this. It's awesome we get to do it at all. Just giving my feedback. P.S. It's a new TB3-850F.
rongallant said:
My bad, understood.
On another note, I am finding it very buggy. The home and overview buttons do not work. They show you clicked it along with the haptic feedback, but nothing happens. The back button works and is the only way I know to get back to the home screen.
Also the tool panel you pull from the top stops working after a little while until I reboot. Then works for a little while.
The Play store downloads barely work. They show pending and nothing happens. I force quite, cleared the cache, disabled, reverted to the stock app and it works for a little bit. Then the other Play Store app comes back. Anyways, I am not complaining. I appreciate the work you put into this. It's awesome we get to do it at all. Just giving my feedback. P.S. It's a new TB3-850F.
Click to expand...
Click to collapse
Yes. Very buggy indeed. I have determined that the bugs are due to corruption during the unpacking of the system image. I'm repacking the ROM now to alleviate the bugs. Thanks for your input...
I've managed to fix the major bugs reported upon initial install of the ROM -- Recents & Home Buttons, Quick Pulldown Menu, Google Framework bugs, New App Shortcut bugs, etc. Simply corruption during packing (archiving) the ROM zip. I will try my best to get a new build posted sometime today.
MotoJunkie01 said:
I've managed to fix the major bugs reported upon initial install of the ROM -- Recents & Home Buttons, Quick Pulldown Menu, Google Framework bugs, New App Shortcut bugs, etc. Simply corruption during packing (archiving) the ROM zip. I will try my best to get a new build posted sometime today.
Click to expand...
Click to collapse
Dear MotoJunkie
İs it possible to upload stock Fm Radio Aplication(offline radio) of Tab3 8? İn my Turkish model, theres no Fm radio aplication. I need it to use tablet in my car.
Thanks
MotoJunkie01 said:
I've managed to fix the major bugs reported upon initial install of the ROM -- Recents & Home Buttons, Quick Pulldown Menu, Google Framework bugs, New App Shortcut bugs, etc. Simply corruption during packing (archiving) the ROM zip. I will try my best to get a new build posted sometime today.
Click to expand...
Click to collapse
Did you get around to uploading it? I am unable to use the OTA update file. Says its missing 'android-info.txt'
Also, anyone care to point me to a way to get back to stock/unrooted?? Nooooo, I didn't backup my ROM first. That would have made way to much sense.
I've been out of commission, unfortunately, due to impending health issues once again. I know that hospital food sucks, that the pretty nurses don't typically put out easy, and that the hospital WiFi restrictions can easily be bypassed with a proxy server address. Lol. And that's all I've learned in the past ten days. Anyway, hope to be back in my daily routine in the next day or so and finishing some stuff up for this device.
Hi, is this thread alive? I'm interested in solution because i have about 60 tablets and need a solution to clone form one source tablet (config, apps, wlan, users, etc.) to other 59. I have tried adb backup --twrp and it went ok, but when i tried restore it gave errors with system partition and now i can only recover tablet with factory ROM from this thread (but it is buggy and cannot put it int to production like this). Is it possible to create system rom from other working tablet? Iwill be very pleased If You can write step by step, how to create zipped rom from working device so i can then upload it to share with others.
spiker_80 said:
Hi, is this thread alive? I'm interested in solution because i have about 60 tablets and need a solution to clone form one source tablet (config, apps, wlan, users, etc.) to other 59. I have tried adb backup --twrp and it went ok, but when i tried restore it gave errors with system partition and now i can only recover tablet with factory ROM from this thread (but it is buggy and cannot put it int to production like this). Is it possible to create system rom from other working tablet? Iwill be very pleased If You can write step by step, how to create zipped rom from working device so i can then upload it to share with others.
Click to expand...
Click to collapse
The thread is alive and I'm currently ironing out the errors on the posted ROM. The errors are due to a couple of permissions which are omitted on my updater-script file. I'll be posting an updated and hopefully error free release this week. Thanks for your interest and sorry for the delay in development. I've had a number of health issues of late and I'm now recovering.
Problem after wiping /system
Hi,
I´m new right here. I bought a new TB3-850F and wanted to flash the Original Stock Rom. After opening the Bootloader and booting into twrp like this way https://forum.xda-developers.com/android/general/guide-lenovo-tab3-8-tb3-850f-t3559786 I wiped the /data /System /dalvic and /Cache. After that I rebooted the system.
But it only shows after starting the Lenovo-Logo. No more booting. Because of this I can´t start the fastboot modus with Minimal ADB and Fastboot.
Is there some idea how I can boot into fastboot?
Many thanks for your help,
sailor1977
sailor1977 said:
Hi,
I´m new right here. I bought a new TB3-850F and wanted to flash the Original Stock Rom. After opening the Bootloader and booting into twrp like this way https://forum.xda-developers.com/android/general/guide-lenovo-tab3-8-tb3-850f-t3559786 I wiped the /data /System /dalvic and /Cache. After that I rebooted the system.
But it only shows after starting the Lenovo-Logo. No more booting. Because of this I can´t start the fastboot modus with Minimal ADB and Fastboot.
Is there some idea how I can boot into fastboot?
Many thanks for your help,
sailor1977
Click to expand...
Click to collapse
I´ve got a solution: After powering down, press power, wait 1 sec then hold both vol up & down also (all 3 Buttons) until vibrates. After starting in recovery Modus hold power button und press once the vol up.
With help of: https://forum.xda-developers.com/android/help/lenovo-tab3-8-2016-custom-recovery-t3483454 post #66
Ok. I've debugged the Stock 6.0 ROM in the OP. Fixed the Bluetooth force close issue at startup and the bugs involving the hardware buttons and the pull down menu. I'm traveling for work at the moment. Soon as I'm back home Monday I'll post the fixed build in the OP.
MotoJunkie01 said:
Ok. I've debugged the Stock 6.0 ROM in the OP. Fixed the Bluetooth force close issue at startup and the bugs involving the hardware buttons and the pull down menu. I'm traveling for work at the moment. Soon as I'm back home Monday I'll post the fixed build in the OP.
Click to expand...
Click to collapse
Cheers buddy. Good stuff ??
@Hemphiz, I hope all is well my friend. Something I wanted to get your input on. It seems that a few members have been experiencing boot loops and other problems after following the TWRP & Root thread I revised. I'm sort of at a brick wall in terms of figuring out what's going on. I'm thinking that maybe there are regional variants that are incompatible with the TWRP we use. Or, it could be one of those situations where instructions are not being closely followed. What are your thoughts? Thanks.
I was testing out a MOD for enabling phone call recording on my U11.
Unfortunately it didn't work out.... but also took away my 'End Call' & 'Speakerphone' buttons from the dialer (rest of the functions seem okay).
I tried to flash back to stock Telephony but it did not change anything.
Now I have to Flight Mode to end a call:laugh: & left with no speakerphone function.
Any help/ advice please......?
Pheeewwwwww!
Seemingly sorted - I just re-installed "Telephony+DD_DS.apk" via SE, done the trick.
However, I have 2 Telephony folders sitting in my PRIV-APP folder now..... ("Telephony" & "Telephony+DD_DS.apk") I am sure the 1st was not there pre-MOD trial - and I cannot delete this extra (unnecessary??) folder via SE either.
Are you stock or on a custom ROM? If on custom ROM just dirty flash ROM next time.
Unified support thread for Pie Xperia XZ ROMs
You can discuss the following here:
Unofficial OmniROM 9.0 for Xperia XZ
Project Treble for Xperia XZ
AOSP Nightly Pie builds for Xperia XZ
Please keep the development threads clean and help each other out in this thread instead.
Telegram Group for General Discussion
Reporting bugs
Important: Read the bug list before posting. Anyone can add bugs to the list, just follow the rules.
DO NOT REPORT ISSUES WITH GSIs! Ask the GSI maintainer to fix them!
I will repeat the rules again here:
Rules:
New bugs must include version where error popped up and which oem version you are using
Only reproducible errors
Should include adb logcat, we CANNOT help you otherwise! (linked in a pastebin service like https://del.dog)
Must include clear description what is wrong
If it is a visual/SystemUI bug, only report it here
If it is an internal bug(e.g. fingerprint crashes device), report it to the Sony bugtracker as well!
Always try to fix the bug yourself first! Then submit a pull request to Sony
Must search if error has already been reported (bug tracker, this document, dev buglist)
If you've reported the issue somewhere else already and just want to track it here as well, add a link
Before reporting a bug, always make sure to isolate it. That means, wipe everything, install only the ROM without GApps and Magisk and see if the problem still exists. Only then report the bug!
Reserved #2
Im a hour ago flashed an newest Omni build and its stucks on bootanimation ? I had flashed: OEM Tone V5, Omni 24-01-2019, Magisk 18.0 and Open Gapps Pico 27-01-2019
---------- Post added at 08:04 PM ---------- Previous post was at 07:13 PM ----------
Now i have the answer. With gapps is smthg not good for Omni. I used RR Treble with that and there it was working :/
How about camera? Still dark photos or maybe something change in New builds?
i just flashed aosp_f8331_2019-02-06-NIGHTLY.zip.
then... my telephone receiver and microphone not work (no voice)
delichik said:
i just flashed aosp_f8331_2019-02-06-NIGHTLY.zip.
then... my telephone receiver and microphone not work (no voice)
Click to expand...
Click to collapse
Post logs or we can't help you. Are you running GApps? Do you mean you can't call at all? Or just no sound? This level of information you're providing is useless for helping you.
Slawek1995 said:
How about camera? Still dark photos or maybe something change in New builds?
Click to expand...
Click to collapse
You can help out with the calibration of the RGBC-IR sensor(named "CASH"
Stick this into /vendor/etc/cash_expcol_calibration.xml https://git.ix5.org/felix/device-sony-kagura/commit/a0253f3de75c52bccb9275ee7eda6cd2f9db539c and tweak the values. You need to restart the CASH server via "stop cashsvr" and then "start cashsvr" after you've modified the values. You can then grep the logcat for "cash" and see the generated values.
The "clear" value is for brightness, you can then adjust the exposure and ISO for the individual steps.
local__hero said:
Post logs or we can't help you. Are you running GApps? Do you mean you can't call at all? Or just no sound? This level of information you're providing is useless for helping you.
You can help out with the calibration of the RGBC-IR sensor(named CASH
Stick this into /vendor/etc/cash_expcol_calibration.xml and tweak the values. You need to restart the CASH server via "stop cashsvr" and then "start cashsvr" after you've modified the values. You can then grep the logcat for "cash" and see the generated values.
The "clear" value is for brightness, you can then adjust the exposure and ISO for the individual steps.
Click to expand...
Click to collapse
oh sorry, i found it is my mistake.
i flashed the official ftf, then flash your rom. now its alright.
thanks for your work
I didn't try aosp roms since long time. Still front camera focus problems(stuck on macro)? Gcam mod works? If yes wich version is adviced? Thanks.
porting of xperia xz3 (pie)
why are developers not make porting of xperia xz3 (pie) to xperia xz dual and use it for stock and unlocked stock?
Which of the 3 versions is the most stable and could be the candidate to remove the official ROM? ... or would I have to wait a little longer? ... I'm tired of not receiving updates, and I get the feeling that the phone is getting slower
When headset connected and playing music (blackplayer) if a notification comes up music stops giving sound but playing. After trying opening volume up & down closing all applications it comes back. Same thing happens if a call comes in when listening music. Music stops but i can't hear any voice from call, doing some things and closing call waiting for the another or i call back it fixes.
Anyone having same problems?
Using oem5 f8331, feb 06 build android 9.0 from sx.ix5.org
RGBC-IR sensor corrects when? The camera quality is really bad
Hey guys!
Sorry if I write in the wrong place. But I flashed OmniROM 9.0 and have some problems:
- If I call they don't hear me and I don't hear them (Not even calling sounds, tried with 100% working Bluetooth headset too)
- Microphone not work in any apps
- Only the lower speaker works
- When phone turn on the first thing I see after boot animation is an error message; "There is an internal problem with your device" or something like this in my language
- IDK why but the phone slows down extremly for no reason sometimes. But the bigger plreblem is the call problem.
Xperia XZ Single SIM
Hello
I have problems with the call audio disappearing.
I installed the system and checked yesterday that everything worked, but for whatever reason today I have no sound during calls.
I have attached the dmesg and logcat Hello
I have problems with the call audio disappearing.
I installed the system and checked yesterday that everything worked, but for whatever reason today I have no sound during calls.
I have attached the dmesg and logcat on del.dog <slash> arepacivaf.coffeescript
(seems I cannot post links due to forum rules)
Based on the output from dmesg, it looks like there might be something SElinux related going on.
I have the same problem with or without bluetooth headset connected.
I am running the latest FTF for my region (192) and OEM version 6.
If you need more info or I should be posting this somewhere else, please point me in the right direction
Thank you
Based on the output from dmesg, it looks like there might be something SElinux related going on.
I have the same problem with or without bluetooth headset connected.
I am running the latest FTF for my region (192) and OEM version 6.
If you need more info or I should be posting this somewhere else, please point me in the right direction
Thank you
Okay... I installed latest rom, latest oem, the old (working) TWRP and...
It's okay now. Everything seems to work.
SoulJahN2 said:
When headset connected and playing music (blackplayer) if a notification comes up music stops giving sound but playing. After trying opening volume up & down closing all applications it comes back. Same thing happens if a call comes in when listening music. Music stops but i can't hear any voice from call, doing some things and closing call waiting for the another or i call back it fixes.
Anyone having same problems?
Using oem5 f8331, feb 06 build android 9.0 from sx.ix5.org
Click to expand...
Click to collapse
Please give us a clean log and file a bug report at the sonyxperiadev bug tracker.
Make a clean re-install without Magisk or GApps and get a logcat and dmesg from boot until your calling issue.
Botchcamp said:
I have problems with the call audio disappearing.
I installed the system and checked yesterday that everything worked, but for whatever reason today I have no sound during calls.
I am running the latest FTF for my region (192) and OEM version 6.
Click to expand...
Click to collapse
What ROM are you running? Which version? Did you wipe/format userdata before installing the ROM?
Botchcamp said:
I have attached the dmesg and logcat on del.dog/arepacivaf.coffeescript
Based on the output from dmesg, it looks like there might be something SElinux related going on.
I have the same problem with or without bluetooth headset connected.
Click to expand...
Click to collapse
It looks like you are running Magisk and GApps. Please clean-install without them and get us a clean log.
Then open an issue at the sonyxperiadev bug tracker.
xda is a horrible place to to actual development, so please try to follow the guides and report bugs in the appropriate places, we cannot monitor everything here.
Se Neo said:
why are developers not make porting of xperia xz3 (pie) to xperia xz dual and use it for stock and unlocked stock?
Click to expand...
Click to collapse
For a number of reasons, here are some examples:
Copyright. Sony software is copyrighted and if we "ported" it, we could get sued.
Different platforms: The Xperia XZ is based on the Snapdragon 820 chipset. The XZ3 is based on the SDM845 chipset. They have different CPU architectures and capabilities.
It's hard when you don't have the source. We compile everything from open-source projects here. If you try to port stuff from the XZ3, you have to decompile the binaries to make them work with the Xperia XZ.
Hello there, i have a problem here about installing aosp rom on my XZ F8831 phone, can i ask it here? So i followed everything on your page including latest tft, flashing oem, flashing dsp, but my phone stuck on white sony logo without installing magisk/gapps. When i try to reinstall it but with gapps, i got this message when i try to flash the gapps, "this gapps is for device that have 9.0 android, your device is 8.0" something like that, so i assume anything i do before is useless, because my phone still on 8.0. Please can someone help me? Im sorry for the bad english
Hey guys!
I have problem with Treble on XZ (Single SIM)
I want to try some interesting GSIs but I never able to make any of them work. I tried like 10 different GSIs already.
So if someone can help me telling what I do wrong and someone can help me to make even one GSI work I would be super happy.
So I started everything from the beggining so reflashing the stock rom with flashtool, then flash the modded TWRP oem-vendor and then flash AOSP treble.
Then wipe everything (I tried without wipe and wipe system too not just caches and data. Every combination)
Then "fastboot flash system gsi.img"
When done I turn on phone SONY logo then restart and loop
So I read need to fix dsp (I not really understand this part) but I don't know how to use the codes or if I use them I got errors (I will write down errors if need)
So I used this;
https://sx.ix5.org/files/builds/kagura/misc/dsp-label-fixer.zip
After I installed gsi I turn on phone in recovery mode then flash dsp-label-fixer.zip. Is this ok? Need to do after every single flash or not even need?
Or if I need to use the codes where to write to make it work?;
Code:
[COLOR="DimGray"]su
# It might be either /system/vendor/dsp or /vendor/dsp depending on your device
# Just try both until one succeeds
mount -o remount,rw /system/vendor/dsp
chcon -R u:object_r:adsprpcd_file:s0 /dsp[/COLOR]
When I ask help last time you I get an answer about selinux. I don't really know if it's help or not, but I downloaded permissiver and flashed it. Same question than with dsp. Need to flash every time or after every rom install and before boot it?
What can be wrong? Why I never make trough the SONY logo with GSIs?
I already isntalled OmniROM and Pie 9.0 rom without problem. Even Treble is boot but without GSI, after installing a GSI image bootloop.
I read a lot and watched videos but still the same problem.
I hope someone will help me, I want to learn but I don't know what I do wrong and what to learn exactly. ?
Sorry for a lot long questions and bad English and being dumb.
Thank you for the answer!
KikiGames