Related
[Kernel][Ref] Samsung Gravity Smart SGH-T589 Technical info & custom kernel project
The Samsung Gravity SMART is a low-midrange Froyo-based Android phone. It hasn't gotten a lot of attention because it's on an unpopular carrier (T-Mobile) and LOL QWERTY KEYBOARD. I intend to change that.
Technical Specifications
Below is information I've gleaned from spec sheets, Internet research, and judicious use of a loupe on my wife's broken phone.
Platform: Qualcomm S1 Snapdragon 7227 @ 800Mhz
CPU: ARM1136EJ-S
Touchscreen: ATMEL mXT224E
WiFi: Broadcom 4329
GPU: Adreno 200
RAM: 320MB, 275MB accessible
Bluetooth: ???
[more later--I'm at work and don't have all my notes]
Kernel development
I don't have anything to release yet. As a proof-of-concept, I've successfully compiled the sources provided by Samsung. It boots, but two big issues prevent me from releasing anything:
The coordinates on the digitizer are inverted--i.e. tapping the top left corner activates the bottom right, and vice versa.
The menu, back, and search capacitive buttons don't work at all.
Upcoming Features
Here's what I'm planning to add to the kernel once driver issues are resolved:
More CPU frequency scaling options
More scheduler/governor options
What's not planned
Gingerbread/ICS (phone needs updated boot loader to support 2.6.35 or later Linux kernels so we are stuck w/ Froyo for now)
I managed to hack the touchscreen driver to kinda-sorta work (at least the axes are correct now), but it's still not quite right. It's very inaccurate, which makes drawing anything (i.e. trying to play Draw Something) not work at all.
ATMEL has released drivers for the mXT series (including the 224E) but I'm having trouble getting it to work properly. Going to compare it against the kinda-working driver and see if I can fix it.
I found part of the problem, but I'm still having trouble with getting the driver to even load. Still, I discovered that the stock touchscreen driver only supports 2 simultaneous touches--the chip actually supports up to 10 simultaneous. I'm hoping to get the driver working so it's actually usable.
I have a friend with this phone i'm curious to see what you can do with it!
Man, this touchscreen driver is kicking my butt.
The official Atmel drivers don't work at all--the i2c call(s) fail during initialization and you get no touchscreen input.
The driver in the kernel released by Samsung is broken, too. In the default configuration, both axis are inverted so you have to tap the top-right of the screen to tap on something that's actually in the bottom-left. And the navigation buttons at the bottom don't work at all (menu/back/search).
So far all I've managed to do is at least get the orientation fixed, but the driver's still broken--you can't tap on anything on the edges (left/right), and the scaling is wrong so taps are mis-aligned in different parts of the screen. It's hard to describe, but comparing the output of YAMTT on stock kernel vs. compiled kernel shows glaring problems.
At this point I am trying to fix the Samsung driver, since it at least partially works. In the process, I'm doing a pretty massive code cleanup, mainly code organization and complete debug info that will make it easier to dissect exactly how the driver works and hopefully find the cause of the freaky behavior.
I've overhauled the debug output of the Samsung driver so that it's easier to parse via grep. The next trick will be actually fixing the driver.. but I'm going to be gone for annual training for the next two weeks, so things will be on hold until I get back.
I'm very excited to see what can be done with this for the phone.
This is my girlfriend's first android phone and while she's enjoying it, I want the experience to be better for her.
Good luck with your training!
SefEXE said:
I'm very excited to see what can be done with this for the phone.
This is my girlfriend's first android phone and while she's enjoying it, I want the experience to be better for her.
Good luck with your training!
Click to expand...
Click to collapse
Nice choice
This is a powerful device but unfourtuneally is an unpopular one, so there is not many developers with the Gravity
I strongly recommend you to install to follow and install this ROM on your girlfriend's phone: http://forum.xda-developers.com/showthread.php?t=1320187
Well, I've managed to get a 3.6.35.7 kernel to boot on the phone.
Samsung released the kernel source for the SGH-T589W which seems to be a Gingerbread edition of the Gravity Smart. The kernel builds successfully and manages to boot, but it gets stuck on a black screen. However, it does show up in the 'adb devices' list, so it's a start.
I believe the problem is the lack of both the OneNAND driver (AKA LinuStoreIII) and the RFS filesystem support. The modules from the stock kernel are compiled against 3.6.32.x so they don't work with the newer kernel.
My Google-Fu has turned up partial source for the same version of LinuStoreIII for the 3.6.35.7 kernel, and it successfully compiled. However, I haven't had any luck finding an RFS module.
EDIT: I think I found what I need, but I won't know until I get home!
gblues said:
Well, I've managed to get a 3.6.35.7 kernel to boot on the phone.
Samsung released the kernel source for the SGH-T589W which seems to be a Gingerbread edition of the Gravity Smart. The kernel builds successfully and manages to boot, but it gets stuck on a black screen. However, it does show up in the 'adb devices' list, so it's a start.
I believe the problem is the lack of both the OneNAND driver (AKA LinuStoreIII) and the RFS filesystem support. The modules from the stock kernel are compiled against 3.6.32.x so they don't work with the newer kernel.
My Google-Fu has turned up partial source for the same version of LinuStoreIII for the 3.6.35.7 kernel, and it successfully compiled. However, I haven't had any luck finding an RFS module.
EDIT: I think I found what I need, but I won't know until I get home!
Click to expand...
Click to collapse
NICE, keep us with update with the news :highfive:
Well, I thought I had something, but it's still not working quite right. I've got the parts for my debug cable on order. Should get here within the next week.
Well, I haven't yet gotten the serial output yet, but I do have a much more detailed output from dmesg now. I'm attaching it below.
Ugh. Samsung's OSRC is being a pain in the butt.
I contacted them requesting the correct driver. Their response: "That is the correct driver."
I responded, "Did you actually test it? Because when I compile the code you provided, the x/y axes are inverted." Their response: "Herp derp Samsung Proprietary."
My most recent response: "Don't give me that proprietary BS. The driver is GPL. If you used any of the code that's in that driver, you need to publish your modifications to it."
We'll see what happens next...
Your dedication to this project continues to provide me with a glimmer of hope for the 589. I thank you sir. Down with herp derp.
Sent from my SGH-T589 using xda app-developers app
Well, now they're claiming that the driver is the one they used in the shipping kernel. Oy!
In other news... I successfully booted Gingerbread on the phone using a stock kernel. I cheated a bit, though. I'll describe how I did it, in case anyone doubts me. The post is intentionally vague because it's not fully usable, wifi doesn't work at all, and I'm not currently at home and able to fully document the process. If anyone is actually interested in trying this out, I'll consider writing a script to automate it.
Known issues with this method:
- network time doesn't seem to work right
- wifi definitely doesn't work right
- usb mode doesn't appear at all
- The phone reports itself as a Galaxy Ace in the Settings screen.
OK, the steps:
First, the things you will need:
1) Stock SGH-T589 firmware (samfirmware.com has it)
2) Stock Galaxy Ace firmware (again on samfirmware.com)
3) unpack-bootimg.pl (google it). This is used to extract the kernel and ramdisk from boot.img
4) mkbootimg (google, or build from source). This is used to re-create the boot.img file
Steps:
- Start by unpacking each firmware package into its own folder.
- From the SGH-T589 folder, delete everything except boot.img
- From the Ace folder, delete everything except boot.img and system.rfs (MAKE SURE YOU DELETE arm11boot.img)
- Now, make an empty folder and copy the stock boot.img into it. Unpack it with unpack-boot.img.pl
- Make another empty folder and put the Ace's boot.img into it. Unpack it also.
- delete the boot.img-kernel.gz from the Ace's folder
- delete boot.img-ramdisk/lib/modules/*.ko
- copy boot.img-kernel.gz from the stock folder to the ace one.
- copy boot.img-ramdisk/lib/modules/*.ko from stock folder to corresponding dir of the ace one.
- copy boot.img-ramdisk/COOPER.rle from stock folder to ace one (optional, preserves the Gravity Smart boot splash screen)
- now, repack the boot.img-ramdisk folder into the CPIO archive
- next rebuild the boot.img file
- lastly, create ODIN archive with the rebuilt boot.img and the Ace's system.rfs
Flash the resulting tar.md5 file using Odin 4.40 USA.
Hi gblues. Very good work so far! Are you planning on porting CWM recovery? It's been ported to very similar phones, like the Ace, Gio, and Mini.
ShaunOfTheLive said:
Hi gblues. Very good work so far! Are you planning on porting CWM recovery? It's been ported to very similar phones, like the Ace, Gio, and Mini.
Click to expand...
Click to collapse
I used a similar technique (unpack, replace kernel/kernel drivers, repack) on the Galaxy Ace CWM recovery and it seems to work. Unfortunately, when I tried to use it to flash the Ace's ICS port, I get a black screen with "A N D R O I D" in the middle (note: this is after extracting the boot.img and doing the unpack/swap/repack process and flashing with ODIN). I suspect that ICS requires kernel features that simply aren't in the stock 2.6.32 kernel.
After doing some more long-term tests, my accomplishment above is a good proof-of-concept but it's not ready for prime time. Landscape mode is completely broken. Games like "Cut the Rope" only give you a black screen. The QWERTY keyboard is borked (mainly alt-keys). The SD card disappeared completely until a reboot. USB mode doesn't work. The accelerometer doesn't seem to work. The stock web browser crashes. Wifi doesn't work. The list goes on.
So that gets back to getting a custom kernel working...
GUIDE SGS4 GSM vs CDMA, Unlocking, Rooting,Info on XDA, Flashing,4 noobs & beginners
First off: if you find this useful, please hit the THANKS button, instead of posting thank you in the comments
Over the course of the past three months (and more specifically, over the past week), I'd like to think I've gone from complete noob to proficient android ROM flasher/ phone dude. However, it took many, many hours of searching for info scattered across this site and others, so I figured I'd give compiling all I've learned a shot, into one comprehensive thread that really covers all the stuff you need to learn from the ground up.
Will do so in the next couple 10 posts, topics being:
*Step (-1): What type of network/ phone technology does your phone use?
*Step (0): is your phone networked locked?
*Step (0.5): DECIDING YOU WANT TO ROOT YOUR DEVICE!/ Put a custom operating system on that thaaaang
*Step1: figure out what your device is- specific phone and model
*Step2: figure out how to root (gain root access to) your device looking at XDA forums
*Step3: Follow instructions, root device
*Step4: backup all your apps and app data
*Step5: Install a custom recovery either ClockWorkRecovery (CWR) or Team Win Recovery Project (TWRP), and do a nandroid backup!
*Step6: Choose which ROM or multiple ROMS you want to try out, and download the zipfile to your phone's internal memory or
*Step7: Step 7: flash the ROM and restore your apps!
NOTE: YOU TWEEK YOUR PHONE/ FOLLOW MY ADVICE AT YOUR OWN RISK
I just learned this stuff myself, so I thought now would be a good time to explain it, while I can still remember what if feels like to have no idea what I'm doing haha.
Before I go further, there are similar intro threads to this...for example, this one does a decent job of explaining that by modding your phone, you may void the warranty (although there are ways to restore your device to a state such that you can't tell you ever modded, it, like triangle away, etc.) http://forum.xda-developers.com/showthread.php?t=1118120
I posted this here because a couple of these steps use the Galaxy S4 i9500 as an example...so if you have that phone this thread should be particularly helpful.
Step(-1): What type of network/ phone technology does your phone use?
If you are OUTSIDE the USA, 99% chance the answer to this question is GSM, meaning your phone number is attached to a little plastic sim card that you can put into/ out of your phone...you should check anyways though to be sure.
If you are in the US, you may have a phone which uses CDMA, a technology that does not use Sim cards (true if your carrier is Verizon or Sprint). Phones that JUST use CDMA are sort of "Hardwired" to their networks, making it much more of a hassle to switch carriers; plus, basically everywhere else in the world uses GSM, so if you plan on traveling outside the USA, you probably won't be able to use your phone abroad. If you have a fancy new smart phone, it may have the hardware to use both CDMA and GSM networks, (for example, all Iphones models 4s and above), so check your phone specs.
In the US, the major carriers that use GSM are ATT and Tmobile. I prefer getting phones from these guys, because I know I'll be able to relatively easily use my phone anywhere in the world, and easily switch between cheap, prepaid, contract free plans (like straight talk or ultramobile), which rent out the networks of major carriers like ATT and Tmobile.
Step(0): is your phone networked locked?
ans: This is mostly a non-issue to folks outside the US, or if you don't plan on switching your carrier, but if you plan on travelling abroad or switching your carrier, and have a CDMA phone, you have a tough road ahead that I cannot advise you on . I would suggest checking out this site and buying a slightly used android gsm phone (att or tmobile branded) http://swappa.com/ .
However, if you have a GSM phone you got in the US, your phone may be configured so that putting sim cards from different carriers in it won't give you any service (aka "locked" or "network locked"). Check by taking a friend's Sim card using a different network than you and popping it into your phone; if you have service/ can make and receive calls, the phone is NOT locked. There are probably more sophisticated ways of checking if your phone is network locked, but above is probably the most straightforward.
There are some methods of unlocking your phone for free, but if you have a newer phone it may not work. Plenty of online sites that sell you unlock codes for between $7-$25, and send the code over email either instantly or a day at most after you buy it. Definitely worth it in my opinion; one site I've used a bunch is http://www.cellunlocker.net/
NOTE: if you have your phone on a contract, you are still obligated to pay your carrier throughout the time of your contract, else you pay some cancellation fee. So be aware of that.
Step 0.5 DECIDING YOU WANT TO ROOT YOUR DEVICE!/ Put a custom operating system (ROM)
SO, now let's say you've network unlocked your awesome GSM android smartphone, and you want to travel with it to another country, like for example, India. Because you unlocked it, you can buy a cheap local Sim card and use it in your phone, fully enjoying mobile 4g data (well, more like 3.5G, using HSPA+, not so much 4G LTE in India yet, but I digress). OR, you can use a $45 a month prepaid plan where you get unlimted everything and have no contract, instead of paying $80 a month or some garbage. AWESOME!
However, let's say you got a Tmobile phone and want to use the phone's capability of being a portable wifi hotspot, broadcasting the mobile data it's getting to your computer...turns out you can't do that in India (or on cheap prepaid plans in US, for that matter). I discovered that since I was using a Tmobile branded phone, the Tmobile "stock" operating system of the phone won't let you use the wifi hotspot unless you have Tmobile's special "hotspot plan"...it also hard codes a bunch of shi**y bloatware apps on your phone that suck. Some BULLS**T, eh?
Luckily, there are plenty of free and easy ways to "root" (gain root acccess) to your phone (and plenty of resources telling you how to do so!), and install custom android operating systems on your phone, which
1.) don't have any stupid bloatware apps
2.) let you use all the hardware features of your phone regardless of carrier
The result is a more powerful phone that runs faster, uses less battery life, and is generally just way more badass. Probably the best resource for how to do all of this is the xda-developers forums (http://forum.xda-developers.com/ ) Very vibrant community, and lots of people will help...just follow the rules though, explained tongue and cheeck in the following video ( http://www.youtube.com/watch?v=JmvCpR45LKA ). The main site for xda-developers is www.xda-developers.com, they also do cool vides and stuff on what's up with phone stuff. HOWEVER, if you are not careful you can mess up your phone, so that it's about as good as a paperweight (called "bricking" your phone). So just read all the instructions before you do stuff, yeah?
The following is more or less the beginning steps I did to root and install a custom ROM on a friend's Galaxy S4, which is an international model and so not network locked. The same general process could be applied to your phone as well, but again--this is only a general guide--your phone can (and probably will) have it's own exceptions to the general process. LOOK THEM UP!
Steps 1,2,3: find device model, research how to gain root, ROOT!
Step1: figure out what your device is- specific phone and model
ans: for example, my friend's phone I am setting up for him is the Samsung Galaxy S4 model i9500
**************************************************
Step2: figure out how to root (gain root access to) your device
ans: Off all the devices on xda forums (http://forum.xda-developers.com/index.php?tab=top), found my device ( http://forum.xda-developers.com/galaxy-s4) , found the proper forum (http://forum.xda-developers.com/galaxy-s4/help) , then searched in that specific forum to find the proper thread http://forum.xda-developers.com/showthread.php?t=2419762 , see Q4
**************************************************
Step3: Follow instructions, root device
ans: Instructions are at http://forum.xda-developers.com/showthread.php?t=2292615
NOTE: You must have the proper USB drivers installed, meaning either installing the sdk (software developer kit) from google and getting adb (android debugging bridge) set up (this is the best way to do it, really, especially if you want to mess around with phones more...tutorial on how to setup adb here http://androidcentral.us/2013/08/how-to-install-android-adb-and-fastboot-on-windows/ ) . If you can already transfer music and stuff from your computer, it may work without adb. Be sure your USB cable is not too beat up, and if possible, is the one that came with the device.
adb is very useful for communicating between pretty much any android phone and your computer. You can use it to push files on the computer through the terminal interface, even if the phone's file system doesn't show up for whatever reason on the computer when you connect it via USB ( more on that here http://log.amitshah.net/2012/05/using-adb-to-copy-files-to-from-your-android-device/ ), and a cool little program to send files from your computer to the device in a slightly more straightforward way, if you already have adb installed (http://www.xda-developers.com/android/push-files-to-your-device-with-quick-adb-pusher/)
Also, make sure you have USB debugging enabled. It should be in the Develpors options, which you may have to "activate" to see...see here http://gs4.wonderhowto.com/how-to/enable-hidden-developer-options-your-samsung-galaxy-s4-0146687/
If you are rooting a samsung device, you will probably have to use a program called ODIN. Other android devices allow you to do root through a method called flashboot. In general there are tons of ways to root devices, just make sure the one you are using has been tested and you follow the instructions exactly.
CONGRATS! you are rooted. That's half the battle. Rooting the phone will add a "Super User" app of some kind, which will basically controll which apps have access to the internal files of the phone (located on the "root" of the phone's flash drive). Some apps that are very useful for flashing custom ROMS (like ROM manager) and backing up your apps and their associated data (like Titanium backup) require root access, so you'll need to have rooted your phone first, and then when you open those apps for the first time, tap "allow" when it asks about granting root access.
some cool apps can only be downloaded if your phone has Root, like this gameboy emulator: https://play.google.com/store/apps/details?id=eu.codlab.src.game&hl=en
and here are some good Root apps to have, apparently
http://www.youtube.com/watch?v=jX4ir9r84YA
Step4: backup all your apps and app data
When you do eventually install a custom ROM on onto your phone, it will start out with little to no apps. The best way to get up and running again as quick as possible is to back up all your apps and data with Titanium Backup (mentioned above), which requires root access. Here's a great video on How to use the free version: http://www.youtube.com/watch?v=gQWoWfTA88k ....the video makes a good point in that if you are backing up your apps for a new ROM you are about to flash, you should only backup the User apps. Backing up and restoring the system data as well might cause some problems in the new ROM
While you don't need to to buy the pro version, I would recommend it--7 bucks, but it allows you to restore all the apps you've backed up much faster by letting you back them up into a zip file that you'll later be able to flash on your phone. Very useful, more on that in a bit...video talking about that here: http://www.youtube.com/watch?v=dRR5FONGJUA
Step5: Install a custom recovery either ClockWorkRecovery (CWR) or Team Win Recovery
By "custom recovery", i mean a custom version of the boot/ recovery interface, which lets you do a lot more with your device besides just restore it to factory settings. These custom recoveries will let you do a full backup of your device (often called a "nandroid backup"--this should be the first thing you do after you root your device!), as well as flash custom phone operating systems (ROMS) onto your phone; useful if you want to fully use all the hardware features of your phone, and not have the bloatware apps from the manufacurers hard-coded into your phone.
It's worth noting here that it's VERY important to install the correct version of CWR or TWRP. Usually to download CWR for your device, you can just download an app called ROM manager (again, after you've rooted your phone), which will recognize your device and then install the proper CWR version on it.
NOTE: If you have a more esoteric model of phone (like I do--the Samsung Galaxy S3 T999L, an LTE version of the S3 that came out in 2013, a while after the initial S3 launch), you may have to flash a custom recovery of a similar and more popular phone model to flash some custom ROMS (in my case, I had to flash the the Galaxy S3 model T999 version of CWR). For weird esoteric cases like this, it may be worth it to buy a useful app, ROMToolbox pro, which will let you flash a custom recovery for a userdefined device onto your phone in the paid version (it's like $5). Most times you shouldn't have to worry about this stuff, but just make sure you read any instrutions on XDA forums carefully before doing stuff.
As mentioned before, before messing around with your phone anymore, do a nandroid backup--super easy and essential if you make a mistake installing the wrong ROM or Recovery. Doing a nandroid backup will create a .zip file that contains a full "image" of your phone--all your data, apps, settings, a snapshot of your phone exactly the way it was when you took it. In creating this backup you can save it to your phone's micro SD card, or the phones internal memory. Regardless, always a good idea to save a copy on your computer too when you are done.
For the Samsung galaxy S4 i9500, looks like TWRP is the recovery to flash: http://forum.xda-developers.com/showthread.php?t=2361122
Step6: Choose which ROM or multiple ROMS you want to try out, and dl zipfile to phone
Now comes the fun part. Do some research on what custom ROM you'll want to try out. Some basic principles about ROMS:
Roms based on the Stock OS: These ROMS are based on the manufacturer firmware/ OS that the phone shipped with. So for Samsung devices, for example, these types of ROMS are Touchwiz based (because "TouchWiz" is the name Samsung has given to it's proprietary software that is responsible for a lot of the bell and whistle tricks you see in Galaxy S4 commercials, for example) These Roms are usually about 700 MB in size, and may still have some of the samsung apps installed if you do like to use them.
AOSP or AOKP ROMS:
AOSP (Android Open Source Project) ROMS are those that ship with "vanilla" android, meaning they don't have any manufacturer bloatware--they come with more or less the bare bones apps required to run the system. These ROMS will be much smaller, around 100-150 MB in size. The most popular of these is CyanogenMod, which is often referred to as just CM (for example, CM11.0.1 stands for CyanogenMod version 11.0.1). The guy who made clockworkrecovery, Koush (a legendary android developer of sorts, it seems), now works for the CyanogenMod development team ( think)
AOKP is the name of another popular AOSP based ROM. AOKP stands for Android Open Kang Project, Kanging being some jargon for stealing code and messing with it or something. Apparently it was used as a joke and then stuck, in the same sense that their mascot being a unicorn stuck (which I think is awesome haha).
IMPORTANT POINT ABOUT AOSP ROMS:
If you flash an AOSP Rom, the google play store will NOT be installed by default. In order to fix that, you'll need to flash another zip file containing the play store app as well as other basic google apps (gapps for short) as soon as you flash the Rom itself. You can find the proper gapps zips that go with the proper AOSP roms here: http://goo.im/gapps
There are couple apps that will let you download the ROM files directly to your interal storage from the app itself, like Rom Manager. However, to make sure you have the most up to date version of the ROM, you should visit the ROM's website directly.
Custom ROMS will often have a most recent stable build, and a most recent "nightly" build. The nightly builds may have some new experimental features, but may be a little buggy.
Step 7: flash the ROM and restore your apps!
So here's a pretty good short video walking through how to flash a ROM, although uses a different recovery interface besides CWR or TWRP : http://www.youtube.com/watch?v=nxTwGwtUBbk ....this does a good job of explaining the basic idea, however--
A.)you get the zip file of the ROM you want to flash on your internal or removable SD card
B.) reboot into recovery mode (often by holding down the volume down key and power button at the same time when your power is off, but you should look up what it is for your specific device)
C.) do a Wipe or Factory Reset. THis should not wipe the data on your SD card or phone's Internal SD card
D.) Wipe the Cache or the Dalvik Cache, whatever it is called (though on TWRP, the wipe feature does both a factory reset and cache wipe at once)
E.) install from SD card the zip file containing the ROM you are going to flash
F.) If the Rom is an AOSP based ROM, install the zip file containing the proper package of google apps
G.) reboot system
Again, the above are just general steps. If you want to see someone flashing a ROM with the recovery you are using (and I would recommend CWR or TWRP), just search for it on Youtube.
Now, if you plan on restoring your apps by flashing a Titanium Backup zip file, you first want to reboot into the new ROM, and skip the part when it asks you if you want to restore your phone using your google account (you can do that later). Then reboot into recovery and flash the Titanium backup zip file. got this info here: http://www.s3forums.com/forum/galax...backup-pros-update-zip-restore-your-apps.html
And that's about it! let me know if I got anything wrong. If you do have questions, I'll try my best to answer them, but again, I've just learned all this stuff as well, so I may not know.
DISCLAIMER: You will be flashing your phone at your own risk. You are solely responsible for anything you do to your phone, so make sure you are well informed and well prepared before deciding to flash or install anything on your device.
Here You Can Get Link to Latest Kernal and Android Lolipop 5.0.2 (CyanogenMod 12)
The purpose of this thread is to provide a 'reference site' for anything related to ROMs and kernels, be it original stock, modified stock or custom images for the Samsung Galaxy S II LTE smartphone(SHV-E110s Korean)
How to Root Samsung Galaxy S2 HD LTE SHV-E110S
Ever considered performing a rooting on your Galaxy S2 HD LTE SHV-E110S? If you haven’t, you should. It’s very beneficial for your smartphone. And we’ll soon tell you why we think that!
If the Samsung SHV-E110S hasn’t experienced root access before, you have a guide to help it do that. We are here to present the advantages and disadvantages of this procedure, as well as info on the rooting app we used.
The smartphone you have is one of the many devices SRSRoot is compatible with. This tool we’re mentioning now is the app we referred to earlier. This tool provides all the pros your phone needs to be improved.
From the get-go you should know that with root access, your handset will get custom ROMs. Apart from that, the device will have many root-only apps and new features. Its dual-core 1.5 GHz Scorpion CPU will perform better and your phone will receive customization tweaks. Superuser and admin permission will appear, as well. Then there are battery tweaks, too.
Android 2.3.6 Gingerbread is your smartphone’s operating system. The SRSRoot fully accepts it and doesn’t delete it. Powered by an SRS Server, this rooting app works with every available Build ID.The one we thought we’d use for your phone was this: GINGERBREAD.EL10.
The advantages of this method
You’re using a device whose other name is Galaxy S II HD LTE SHV-E120S. If the handset receives an upgrade, it will have its root access and system partition revoked and deleted, respectively. When root access gets on your smartphone, expect to have the warranty revoked. But don’t expect damaged internal / external SD cards or crucial content.
Various brands can experience the SRSRoot app.
The root access allows you to enjoy, apart from what’s already been said, another advantage. You can unroot the phone at any time.
Prerequisites
The Galaxy S2 LTE SHV-E110S has to pass through specific pre-requisites in order to receive the rooting app. Here they are:
How to Root Samsung Galaxy S2 HD LTE SHV-E110S
Ever considered performing a rooting on your Galaxy S2 HD LTE SHV-E110S? If you haven’t, you should. It’s very beneficial for your smartphone. And we’ll soon tell you why we think that!
If the Samsung SHV-E110S hasn’t experienced root access before, you have a guide to help it do that. We are here to present the advantages and disadvantages of this procedure, as well as info on the rooting app we used.
The smartphone you have is one of the many devices SRSRoot is compatible with. This tool we’re mentioning now is the app we referred to earlier. This tool provides all the pros your phone needs to be improved.
From the get-go you should know that with root access, your handset will get custom ROMs. Apart from that, the device will have many root-only apps and new features. Its dual-core 1.5 GHz Scorpion CPU will perform better and your phone will receive customization tweaks. Superuser and admin permission will appear, as well. Then there are battery tweaks, too.
Android 2.3.6 Gingerbread is your smartphone’s operating system. The SRSRoot fully accepts it and doesn’t delete it. Powered by an SRS Server, this rooting app works with every available Build ID.The one we thought we’d use for your phone was this: GINGERBREAD.EL10.galaxy-SHV-E110S
The advantages of this method
You’re using a device whose other name is Galaxy S II HD LTE SHV-E120S. If the handset receives an upgrade, it will have its root access and system partition revoked and deleted, respectively. When root access gets on your smartphone, expect to have the warranty revoked. But don’t expect damaged internal / external SD cards or crucial content.
Various brands can experience the SRSRoot app.
The root access allows you to enjoy, apart from what’s already been said, another advantage. You can unroot the phone at any time.
Prerequisites
The Galaxy S2 LTE SHV-E110S has to pass through specific pre-requisites in order to receive the rooting app. Here they are:
a standard backup should be performed;
a full NANDroid backup is something you should perform next;
your notebook must be running Windows;
the security software installed on the notebook have to be deactivated till you’re done with the rooting;
check and see if your smartphone’s in need of a charged battery;
in case the battery levels are very low, make sure you charge the Galaxy S2 SHV-E110S;
download, on your notebook, USB drivers for your smartphone;
enable the smartphone’s USB Debugging;
have the notebook’s security software deactivated.
Step by step instructions
Do this for the first step: download, on your laptop, this dedicated software. The place where this app is on this page.
Once you click on a download button located on it, the app will download itself on your laptop. After this is over, you’ll have to install the app on the laptop.
Open it on the same device, then do the following: tap Menu and Settings. Take a peek under the latter and there you’ll come across this option: Unknown Sources.
After you activate it, you should do this: turn on USB Debugging. If you activated it before now, you’d better move on.
The next step you need to perform: generate a connection between your handset and laptop. The connection has to be initiated with the phone’s personal USB cord. After you’ve used it, let the connection happen. This should take no longer than a couple of minutes.
In case the plugging needs a longer period of time, you can redo the steps up until this one. Should the connection have already been established, be sure to do this: activate Root Device (All Methods).
This is the part where the rooting begins. Give the rooting some time to be done. The time you’ll have to wait should be approximately 10-15 minutes.
Restart your phone if the rooting is done. If it isn’t, you can repeat our steps. After the smartphone has started once more, you are free to go to your Galaxy S2 HD LTE SHV-E110S and get a feel of the rooting goodies we previously told you about.
If you are done with this, decide if you want to keep the root access. In case you don’t want to, you have the SRSRoot app to use in order to get rid of the root access.
Reference :droidgator
Note:This Rooting is Not required in Latest Custom Roms as Super User is Already Added in it
Now Its Time To install Recovery into Your Device
If you are one of the users of the HD LTE variant of Samsung Galaxy S2 smartphone, then we have some good news for you. The developers over at XDA Forum have successfully ported the ClockworkMod Recovery to Galaxy S2 HD LTE phone and the following guide explains how you can install the same on your SGS2 HD LTE smartphone.
I. Before You Begin:
1. The custom recovery will replace the stock recovery on your phone. So, you won’t be able to boot into the stock recovery afterwards.
2. Make sure your phone is fully charged, so you won’t face any problem during the process.
II. Downloading Required Files:
1. Download the Odin Tool --- http://forum.xda-developers.com/galaxy-s3/themes-apps/27-08-2013-odin-3-09-odin-1-85-versions-t2189539
Note Download Odin 1.85
2. Download the ClockworkMod Recovery Image .
http://forum.xda-developers.com/attachment.php?attachmentid=3104743&stc=1&d=1420732132
This Zip Contain a notepad in that there is link of recovery.
III. Installing ClockworkMod Recovery on Galaxy S2 HD LTE:
1. Download and place both the Odin as well as Recovery Image onto your Desktop,
2. Extract files from the Odin archive to your Desktop.
3. Double-click the Odin3_v1.85.exe file to launch the Odin Tool.
4. Turn OFF your smartphone using the Power key.
5. Reboot your phone into the Download Mode. To do so, press and hold Volume DOWN+Power keys together.
6. Press the Volume UP key to enter the download mode.
7. Connect your phone to your PC using the USB cable that came with it.
8. From the Odin Tool, select BOOTLOADER option and choose the Recovery Image you downloaded earlier.
9. Do NOT modify any other settings in the Odin, hit the Start button to commence the flashing process.
10. As soon as it has finished flashing recovery, your phone will reboot.
Great job ! You have successfully installed the ClockworkMod Recovery on your Galaxy S2 HD LTE smartphone. The custom ROMs are now a click away from your phone.
You can now root your phone using the ClockworkMod Recovery. Please see our guide on how to root Samsung Galaxy S2 HD LTE.
Reference:theunlockr
Now Its Time To install Custom Rom
This is an unofficial CyanogenMod 12 Lollipop ROM for our dear SHV-E110s. This is currently a work-in-progress, so you can expect to run into problems while using it.
You must perform a full wipe (wipe /data,/system,/cache,/dalvik cache) before installing this ROM for the first time. New updates can be flashed on top without wiping anything.
The first boot will take about 10 minutes.
DOWNLAOD LINKS : These link are not mine this is just a reference post and reposting you those links here in a text document as attachment please do not mirror :good:
http://forum.xda-developers.com/attachment.php?attachmentid=3104743&stc=1&d=1420732132
Screenshots:
http://forum.xda-developers.com/attachment.php?attachmentid=3104811&stc=1&d=1420734671
Instructions :
Download ROM
Download Gapps
Reboot into recovery
Select Wipe-SYSTEM,DATA,CACHE,DALVIK CACHE
Flash ROM
Flash Kernel
flash gapps
flash Super SU
wipe cache and dalvik cache
And Reboot
If ur stuck at boot or if ur having bootloops then wipe Dalvik cache and wipe cache!!!!
The first boot will take about 10+ minutes.
CREDITS: LIQUIDANDROID
Note: This is Just a refrence Link;Developer is LIQUIDANDROID TEAM
Will it work for Korean s2 shv m250k
just couriuos, where is the ROms file ??
I think there is no ROM in the link Given.
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.
Hello to all, as the title I wanted to ask for advice about the quality of the installation I made notes for the Roma 4, I mean I have a samsung note 3 neo lte which as you know is not a lightning war, being the lollipop yet arrived for my device, I read that the above rom for my device is quite an improvement, and in fact by neophyte I launched in the installation as follows: I place the phone in debug mode, after that through odin I installed the root, After restarting I always installed via Odin TWRP-2.8.5.0-hlltexx-4.4.img finally restart by pressing the volume +, Home and Power, I found myself in the mask "teamwin" where I ran the command wipe full in the sense that I made clear the screen, after which I launched the installation of Notes-4-MINI10 N7505 everything went according guidance, the communicator is improved to 100%, but unfortunately I realized that by pressing on the icon gallery gives me problems in the open, pointing to a hypothetical lack of memory is obviously not true, and also something much more serious working with whatsap not allow me to reintegrate into ap my whole history backupped make, so reluctantly I had to reinstall the original file rom samsung, now I come to the heart, in your having read that the project x this rom was closed for completion of that bug and injuries, possibly could have been me to commit some nonsense given by my inexperience about ?, also because unlike the guide suggested that you install on samsung Flashify ( for root users) after which click "recovery image" and download "Philz", I did not follow this path because when I went into the app and cliccavo the aforementioned routes was an orange circle that ran for hours without giving me any results.
I thank all those who will want to possibly give me some advice about.