[Q] LG-AS730 -- Instructions to root - General Questions and Answers

This is our first Android device: LG-AS730 – Optimus Select (for carrier Revol)
-
SCR Version: AS73010b_Revol
Software version: AS73011A
Andriod version: 4.0.4
Kernel version: 3.0.8
OUR GOAL:
Root the phone for security reasons in addition to getting rid of all the bloat and/or unwanted apps. We don’t like syncing, or the sharing and storing of our data (cloud). We do however respect open source. That said, we have never rooted, see above, “our first android device”. What is in place, if anything to accomplish our goal –without loosing functionality and/or bricking our device?
-
Our XDA search term “LG-AS730”, and “AS-730” yields no results at this point in time.

Root AS730 / Development
This method will work for the AS730.
http://forum.xda-developers.com/showthread.php?t=1886460
Be aware our phone has a locked bootloader + CRC Check, which means if you remove certain system apps, you will be greeted with a "Security Error" message on system start, resulting in a shiny new brick.
I already bricked mine, and luckily I still has a couple days left on my 15 day warranty with Revol to get a replacement ( I said it was an update gone wrong )
(After which, I found the .cab file on the LG server to hopefully restore (Haven't verified yet))
I'm currently looking into ways to remove the CRC check.
I'll be making a post soon with an attached .cab / other information on our device.
It just sucks our device has almost no documentation or development.
If anyone would like to help with development or anything, PM me.

veris said:
This method will work for the AS730.
http://forum.xda-developers.com/showthread.php?t=1886460
Be aware our phone has a locked bootloader + CRC Check, which means if you remove certain system apps, you will be greeted with a "Security Error" message on system start, resulting in a shiny new brick.
I already bricked mine, and luckily I still has a couple days left on my 15 day warranty with Revol to get a replacement ( I said it was an update gone wrong )
(After which, I found the .cab file on the LG server to hopefully restore (Haven't verified yet))
I'm currently looking into ways to remove the CRC check.
I'll be making a post soon with an attached .cab / other information on our device.
It just sucks our device has almost no documentation or development.
If anyone would like to help with development or anything, PM me.
Click to expand...
Click to collapse
Glad to see that my excuse works in other places xD. I do have a rooted System.img, just no way to flash it to the phone. (At least, I believe I still have the rooted system.img file). With our model, LG Mobile Phone Support Tool doesn't decompress a system.img.ext4 while flashing which is what caused my brick. I tried splicing back together a BIN file and literally ****ed the partitions.

??
AS_730 said:
This is our first Android device: LG-AS730 – Optimus Select (for carrier Revol)
-
SCR Version: AS73010b_Revol
Software version: AS73011A
Andriod version: 4.0.4
Kernel version: 3.0.8
OUR GOAL:
Root the phone for security reasons in addition to getting rid of all the bloat and/or unwanted apps. We don’t like syncing, or the sharing and storing of our data (cloud). We do however respect open source. That said, we have never rooted, see above, “our first android device”. What is in place, if anything to accomplish our goal –without loosing functionality and/or bricking our device?
-
Our XDA search term “LG-AS730”, and “AS-730” yields no results at this point in time.
Click to expand...
Click to collapse
Do u have the original rom

Related

New Recovery Flasher ! [updated 20090904]

http://zenthought.org/content/project/flashrec
Tool to flash the recovery image on Android phones. The so-called “one click root”.
No longer includes CyanogenMod Recovery 1.4 , but will download the correct CyanogenMod Recovery 1.4 for your phone.
Allows flashing any image (type the path or url to it).
Works on “32B” and “32A” phones.
Uses CVE-2009-2692 , which is patched in firmwares released after August 2009.
Also allows you to back up and restore the current image (to /sdcard/recovery-backup.img)
NOTE: I just found this update and have nothing to do with the actual project - though I am grateful for the work and would like to share the info!
Bluetooth access is only used to create a socket for exploiting the bug – Bluetooth does not need to be enabled, as it is not really used.
Pre-compiled: flashrec-1.1-20090904.apk (Allow non-market apps on phone to install)
Source: flashrec-1.1-20090904.tar.gz
SVN: flashrec on Google Code
Note: I am not involved in this project, just sharing the hard work of someone else.
Trying right now on a G1 Dev phone.
Awesome app! The real universal rooting tool!! (for now at least
I heard about this a couple days ago. Will this thing still work after donut? Also would this be in here or in the app section?
Does anyone have their original backup before they rooted their phone? I need it in order to get my phone back to unroot. I need it in order to restore my splash image since my hardware keyboard isn't completely working.
Any help will gladly be appreciated.
Old News
this has been posted quite a few places already
josharmour said:
Trying right now on a G1 Dev phone.
Click to expand...
Click to collapse
Isn't the dev phone already rooted?

Root Miphone

Hi everyone!
Got this Miphone A3 yesterday, and I been searching like a fool after information about this damn phone but it ain't a easy thing to find.
But hey, what do you expect from a cloned iphone
So here's my question:
Anyone sitting on a Miphone and have you done anything with it, most imporant for everything, ROOTED?
Phone info on the phone:
Model number:
A8
Where I bought it, it said A3 on the site (mobino1), same on the battery.
But instead of the iPhone Ui it has the Android Ui pretty sweet that it didnt have the iPhone Ui.
Firmware:
1.5
Don't have Android Market app, but everything looks like Android, also works to install . apk apps tried to install apps from 1.6+ but doesn't work.
Kernel:
2.6.25
Build number:
Linkworld Project .0002_A.1_01r_100129
Been looking for that build number for a while now, don't have any info at all on that one.
Hope some1 here has some info, would be a blessing for me!
EDIT:
I found my way into what i think is the recovery mode, came up a where is said enter flash mode put in usb cable, with red background. Then when i did that, the screen turn blue saying "Enter Flash mode, Begin to flash image..."
Been reading a lot, and i never came up with that kind of "bootloader" just saying that
hope some1 could give me some tips
hi, one of the stores provided firmware from A3, I do not know how fresh. ussd queries are unsuccessful, after ussd calls to hang up. In flash mode turns pressing the upper side volume buttons and switch.
depositfilescom/files/0po3pwcu6 - miphone A3 rom
thanks for that one!
flashed my phone, worked! but it wasnt the same version. this one was with the iphone ui (using ahome)
Model number:
A3
Build number: A3 Project.0001_18r_100411
Seems like my 3G connection does not work with this version. ussd, unsuccessful on this version too, same with previous version.
I was wondering, tried to open the one.bin (flash image) but cannot extract it. Any way to extract the image and try to reconfigure the build?
the phone using "tavor platform" flashing software, anyone know anything about tavor platform?
still trying 2 modify the rom I have, no luck so far.
I do also have this phone from mobino1...
how do you try to modify the firmware you have?
Regards,
xift
miphone a3
I too am with the same problem I have software for Tavor flashing but without success for updated the firmware is in a single bin file without being able to extract and modify
if anyone knows how do to then updated
xift said:
I do also have this phone from mobino1...
how do you try to modify the firmware you have?
Regards,
xift
Click to expand...
Click to collapse
I been trying to extract the .bin file MagicIso can read the file using it "missing files" but can't read the files when extracted. Trying to find a program that could read the rom file, have you done anything to update the phone? Do you have a rom file, if so could you upload it pls?
tried to get the firmware from mobino1 but they just ignore mig those bastards.
Ernest25
miphone a3
I too am with the same problem I have software for Tavor flashing but without success for updated the firmware is in a single bin file without being able to extract and modify
if anyone knows how do to then updated
Click to expand...
Click to collapse
Do you want to flash your phone with the .bin file you already have or do you want to know how to update the phone to android 1.6+?
To flash your phone with tavor flashing software, you need to run the flash program in XP and press "volume up" and "power" on the phone to get to flash mode, then plug in the usb with the flash program open, and it automatically flash the phone.
About updating the phone to a newer version of android I have not a solution.
I been trying to, get info on the hardware so I could try to cook a own rom with at least android 2.0
Cheers
sorry i don't have the firmware as a rom file either...
and these mobino1 bastards ignore me too ^^
although they admitted they could contact the developers...
new firmware would be nice... or at least the current firmware.
I did not downgrade it yet and I think I won't do that.
Another problem could be that the bootloader only runs signed firmware image (just guessing).
I know how to flash I want is a newer room the problem these Chinese are not then updated dependent on us for a updated
(question) has a possibility to use, one firmware and change to a bin file to MiPhone a3
xift said:
sorry i don't have the firmware as a rom file either...
and these mobino1 bastards ignore me too ^^
although they admitted they could contact the developers...
new firmware would be nice... or at least the current firmware.
I did not downgrade it yet and I think I won't do that.
Another problem could be that the bootloader only runs signed firmware image (just guessing).
Click to expand...
Click to collapse
Ernest25 said:
I know how to flash I want is a newer room the problem these Chinese are not then updated dependent on us for a updated
(question) has a possibility to use, one firmware and change to a bin file to MiPhone a3
Click to expand...
Click to collapse
If they just told me straight up, we just sell the phone, we don't have any contact what so ever with the manufacture or developers I would accept it. But this just pissed me off.
I've been asking around on other sites that sells the phone, waiting on answers from them. Hopefully they are more friendly.
Don't downgrade, that was a mistake for me (the rom file azat182 nicely posted).
I tried something yesterday, made a own .bin file with android 2.1 but the flash program wouldn't start with it (parse ini error) so I tricked the flash program that it would flash the one.bin (azat182) rom file.
After it opened I replaced the .bin file with mine. Everything seems to work fine, did every step it should like, root system etc finished 100% when I tried to turn the phone on I couldn't, maybe it didn't know were the power "button" source came from.
The android source was made for an other phone, so I wasn't surprised.
Plugged the usb back in, and luckily the phone connected somehow with the computer so I flash it with the (azat182) rom and I'm back at square -1
but now I think, if I could find out the hardware/drivers on this damn phone it would work to cook a own rom using that method.
Cheers
Oh hey, someone else with one of these phones. I've been messing with mine for a while, started out with the A8 rom (from fastcardtech), and have flashed the A3 rom to the device. I've noticed that the gps works a lot better in the A3 rom than the A8, so it's not much of a downgrade, imo. Recently I've made some headway with an android 2.1 port to the device.
Anyway, this device isn't hard to root. If you adb into it, you can get root from the device by remounting /system as RW and pushing a fixed su binary to /system/bin, or wherever it goes, it's been a while
The MTD partitioning in the Miphone's rom is a big giant mess. The rom is split into 25 partitions, the kernel isn't in boot.img like it's supposed to be, neither are the kernel parameters.
The bootloader is dumb, it doesn't check for signed images. The A3 image and A8 image are both engineering builds.
wow you seem to know a lot about it...
does 3g work for you in the a3 rom? also gps doesn't work for me in a8... so a3 could be a possibility if 3g worked.
how did you adb your phone? I could not connect... the driver just didn't show a phone. although I changed the vendor ids etc...
could you write a short tutorial of some sort? would be nice!
if you are root, couldn't you make a backup of your firmware?
is there a downloadable a8 rom at fastcardtech?
regards, xift
I haven't been able to get 3g working, just edge. I don't think the 3g will work in the US, as none of the carriers will work with just wcdma2100, but I'm no expert on the subject. I've had reasonably good luck with the gps with an app called Maverick, but I don't have a data plan currently, so no agps. With gps alone, it takes about a minute or so in an open area to acquire a lock.
For ADB, there's a driver in the android sdk, but don't bother with it. Instead, the phone's going to show up as a rndis/ethernet gadget. For windows, drivers for this can be found at webos-internals.org/wiki/USBnet_networking_setup, just the .inf is all you'll need; MacOS and Linux will just see the ethernet gadget. Once that's installed, the phone will show up on the PC side as a network interface that will need an IP address; I've been using 169.254.231.10 and subnet 255.255.255.0. Once your network interface is configured, you should be able to run adb connect 169.254.231.168:5555, assuming you've got your android sdk tool set up already. From there, you can adb shell in and poke around. Once you get an adb shell, you'll have a root prompt, but to get 'rooted' so that other android apps can make use of it, you'll want to run adb remount to remount /system as RW, then copy a working version of su over to the phone. I think superuser whitelist comes with one.
I don't usually go to that much trouble, as I end up cycling between the A3 firmware and my Eclair build a lot, and the A3 rom is jacked up to where it's a pain to get a terminal emulator running on it. Adb from my desktop seems to get the most mileage.
Fastcardtech didn't have any useful information about recovery firmware that they had, a release date for an android 2.1 rom, information on the manufacturer, anything.
Wow thanks a lot... I tried with the sdk driver.
port 5555 seemed blocked there although it was obviously responding (took much longer than other ports). Thanks for your help - I'll try that one.
Could you upload your eclaire build?
I don't have much time at the moment because of my bachelor's thesis. But I'd like to see that and maybe I could help a bit. Although I do not have any experience with mobile devices etc.
You may need to mess with the usb debugging option. After flashing to the a3 rom, it's enabled. I remember it being the same between the a8 and a3 roms.
At some point, yeah, I'll my eclair build up. I'd like to at least get bluetooth, gsm and wifi going again before I do. I don't have a rom that you'd be able to flash currently; more like a big pile of build scripts, and install scripts for the android system and ramdisk.
yeah I understand that. You could open a google code project or something.
nice to know that there is somebody working on this.
usb debugging is enabled by default. I'll just have to try again.
thanks for your help so far.
file inf
I not have disk only cd and dvd when I will install the drive without the disk says no drive found I save the file as usbnet-pre.inf
if anyone can help me pls
well I also had problems installing the driver in windows ...
It always said something like "No driver found at that location".
You could try on linux though... It worked like a charm for me.
I'm root now
@nsigma is there anything I could provide you from the a8 image?
xift said:
well I also had problems installing the driver in windows ...
It always said something like "No driver found at that location".
You could try on linux though... It worked like a charm for me.
I'm root now
@nsigma is there anything I could provide you from the a8 image?
Click to expand...
Click to collapse
linux complicated for me but thank you I hope good news from you about how root this bastard mobile
I have the A3 if you're interested I can pass to you

[Q] What's the difference between a device OS, apps, and firmware

I've done some research but many sources seem to either use the terms interchangeably or as separate items. I figured no better place than get the info directly from xda users. So basically I am trying to figure out what the differences are between an android app, and android OS, and android firmware. Your explanation will be much appreciated.
Also while i'm here if anyone could tell me what the difference in unlocking a phone, rooting a phone, and flashing a phone is that would be great.
Thanks in advance!
Az Tek said:
I've done some research but many sources seem to either use the terms interchangeably or as separate items. I figured no better place than get the info directly from xda users. So basically I am trying to figure out what the differences are between an android app, and android OS, and android firmware. Your explanation will be much appreciated.
Also while i'm here if anyone could tell me what the difference in unlocking a phone, rooting a phone, and flashing a phone is that would be great.
Thanks in advance!
Click to expand...
Click to collapse
What a bunch of questions All informations are already written doen on XDA but i'll post a short overview
app = installable appliction e.g. a camera app or messenger app
OS = operating system ~ the installed Android version (e.g. Gingerbread 2.3 or KitKat 4.4). Can be preinstalled "stock rom" or a manually installed "custom rom"
firmware = all system partitions bundled in one archive. Can be used to restore phone. Every manufacturer has its own firmware format.
unlocking = Either sim unlock for using all providers OR unlock the "bootloader" which is needed for some phones if you want to install modified software e.g. a "custom rom" or "root acces"
"root access" means ability to read/write/delete to all partitions even e.g. system
"flashing" describes the installation process for e.g. a firmware or custom rom or any other system parts that can't be installed via Android itself.

RCA RCT6203W46 Pro10 Tablet: Catch-all Thread

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

[Help]I Un-rooted my Phone so I can run a certain app but still run into problems

Hello, as the title says, I un-rooted my phone a few days ago... I used KingRoot, and I also used the Un-Root option on their windows app when I un-rooted my phone. I also used Root Checker App and the Terminal Emulator App from Google Play to verify, the results showed that my phone is no longer rooted.
Note: I'm also very newbie and most of the time, very clueless when it comes to these Android Rooting business, so I would appreciate it as well if the answers will be newbie friendly, and I apologize as well if I'm asking to be spoonfed for the solutions; I only have very limited time, and me hunting for answers in google resulted in hours of wasted time, except on me being able to learn just the meaning of a very few terminologies, too few to be considered significant I think.
~~(Might be helpful) Details:
-The model is: Samsung Galaxy Core Duos GT-I8262, and is running the Android Jelly Bean (Android Version 4.1.2)
-For a more detailed firmware/rom info (after dialing *#1234#):
AP: I8262XXAMG6
CP (Baseband Version): I8262DXAMH1
CDC: I8262OLBBMH2
Kernel Version:
3.4.0-1322246-user
[email protected] #1
SMP PREEMPT Mon Jul 22 17:26:39
KST 2013
~~Situation:
Now the thing is, the app I am using no longer allows phones who are rooted, so I un-rooted my phone, and to begin with, I haven't really done anything with my phone being rooted, since back then I was trying to fit my games on my external SD card by installing apps which requires root... but everything I tried with my limited time didn't work even with root, so I did not bother to do anything root-related (like installing certain UI modification and such). The only thing that got installed on my phone is this KingRoot app (which I prevented from installing any other app that it offered), and is since then removed.
Now, I un-rooted my phone using the Windows App that KingRoot provided, and I even used Root Checker app from Google Play and even checked my root status using the Terminal Emulator; results are all cleared, my phone is no longer rooted.
But when I run this app, it still gives me an error code that the devs themselves provided... an error code that indicates that my phone is either Rooted, is a China Phone, or other problems.
For the first two problems; Rooted or China Phone; I'm supposed to be cleared of this, and my phone is a Samsung bought from an official dealer...
As for the third problem: one of my friends who uses the same app told me that my problem might lie on my ROM not being a "Global" one... from the Firmware info I provided, I can see an area code called 'DX' (which should stand for Indonesia, Malaysia, Philippines, Singapore, Vietnam, and I am in the Philippines right now).
~~Problems:
There comes a whole lot of new problems, but first, to sum up my whole problem:
--What should I do with my phone to change its ROM or Firmware (what should I change between these two to begin with?) so that it becomes "Global" and would finally allow me to run this App (a Game), WHILE at the same time, still allows me to use my Sim Card in the country I am in right now and still being able to keep all my data intact (assuming Flashing a ROM would erase my phone's data particularly in the internal storage)?
Specific Problems:
-With my limited time, I only am able to find tutorials that allows one to flash a ROM using a Rooted Device... should I root my phone again and do the flashing then remove the root? And before that... really, what in the world should I do? (Refers to my question above on my problem summary), like, how should I flash this ROM while my device is unrooted, what should I do? (I'm really sorry for this question, but I hope someone will help me on this...)
-I am having dilemmas with backing up my data in my phone, such as my notes on the built-in Memo App, and my research said I have to use Titanium Backup... which requires a rooted device to work... can I just use this "Backup and Reset" from my phone's Settings and would still allow me retrieve my notes on my Memo App as well as my contacts and Text Messages intact after I flashed this "Global" ROM?
-I cannot seem to find a ROM that is "Global"(?) for my Smartphone Model and Android Version whenever I search google... can anyone of you who are knowledgeable enough provide me with such? Searching for it using google is not giving me any exact answers...
-I have read during my research earlier that when I flashed a ROM that is not in my country, my Sim Card would fail to work? Then what should I do to make this phone have this "Global" ROM/Firmware which will allow me to run this App, while at the same time, still allows me to use my Sim Card in this country without any problems?
-To begin with, from the data I provided:
AP: I8262XXAMG6
CP (Baseband Version): I8262DXAMH1
I see from the AP the area code 'XX' which denotes that it's Austria, Belgium, France, Germany, Hungary, Italy, Spain, United Kingdom, right? Then isn't my phone "Global" already? I'm very, VERY confused...
---
These are all the questions I have in my mind right now. I hope someone would help me with my problems, and clarify necessary things from my problem. If someone could also direct me to a tutorial of sorts, on flashing a "Global" rom that would enable me to run this App, while still making my phone's data intact and still allows me to use my Sim Card for communication purposes here in the Philippines, would greatly be appreciated as well.
Thank you all in advance, sorry for the long post too, I tried giving all the details I could and asking all the questions I could that might help pinpoint the problem as well as might help in providing me a solution that would work to fix my problem.

Categories

Resources