Related
Dear friends,
as i have been hanging out in this forum, i have learnt a lot. But still, i cannot understand the attitude why people treat, reply or explain everything in a way that assumes all of us are android experts.
TF700 is my first android device(have been using Apple before) so I really need to improve-or create- fundamental knowledge. Just for your information, replying messages like; "ok now Unlock the Root system instead OTA .21 and blablablabla?" (btw. i am well aware of the fact that this sentence is totally meaningless)
Whatever, my point is it would be wonderful to have a fundamental knowledge thread, also keeping your great posts too at the same time.
Cheers!!
archonur said:
Dear friends,
as i have been hanging out in this forum, i have learnt a lot. But still, i cannot understand the attitude why people treat, reply or explain everything in a way that assumes all of us are android experts.
TF700 is my first android device(have been using Apple before) so I really need to improve-or create- fundamental knowledge. Just for your information, replying messages like; "ok now Unlock the Root system instead OTA .21 and blablablabla?" (btw. i am well aware of the fact that this sentence is totally meaningless)
Whatever, my point is it would be wonderful to have a fundamental knowledge thread, also keeping your great posts too at the same time.
Cheers!!
Click to expand...
Click to collapse
I am a newbie too -- bought the tf101 a couple of months ago - loved it -- told my husband he could have it - I was buying the 700 ! and was lucky enough to be able to order one (we live in Canada..... Tiger Direct.ca had them)
I have learned a lot from this forum -- glad I found it --- but I won't be "unlocking" anything ! the only thing I know how to "root" are my house plants !!! lol !! we don't even own smart phones yet -- we still have dumb phones !!! but I have my TF700 !!!
You mean sth like this?
seems hard, but it's not.
It seems tough in the beginning for noob, but actually you're going to get it. You should read the "Index" pointing out by d14b0ll0s to gain some basic knowledge and familiar with the terminology then you should be fine. Couple key words I want to point out that you should know. Currently TF700 came with a locked boot loader, meaning you not able to flash (install) custom firmware from our developers. This is a biggest issue at the moment. Sure there're workaround but it's a pain in the as...and unstable(could brick your pad if you not doing it right). When you see numbers like 21,22,26, they are firmware version number. The latest should be 26. OTA stands for "over the air" and we referred to firmware push to our pad by Asus, not manually download and install ourselves. Rooted is a process that you gain access as a administrator on your pad (you have full access to your phone), with rooted privilege you can almost do anything with your pad, like uninstall Asus embed software, do a full backup of your entire OS (operating system), modified system files etc... CWM is a tool you installed on your pad in order to flash (install) custom firmware. So at the minimum you should have root, and in the future when new custom firmware arrived, you can install cwm and used this tool to flash them. Keep in mind that with locked boot loader, you can't flash custom firmware. Finally, once you're rooted or have custom firmware installed, your pad will no longer can accepted OTA firmware (firmware push to your pad by Asus). In this case you need to roll back to stock (re installed factory firmware and no root), before you can do OTA update. Currently, I suggest you should stay on the side line and waiting for the OTA 4.1.1 JB (new Operating System called Jelly Bean, version 4.1.1 will be push to your pad by Asus). After reading this post you should be ready to play... good luck!
Sorry, but I don't get it, what is it about Verizon? Is it because you bought yours from Verizon? Mine comes from ASUS and I believe the OTA updates are from ASUS servers. Is it the US-specific thing that you mentioned?
Yeah... Everything is pretty easy even for people that have no clue what they are doing. My suggestion right now is to root but not unlock. Rooting is as simple as running the .bat file and following on screen directions (assuming you are using Windows). The only thing you need to do after the program is finished is to open up the Superuser app (might be SuperSU) and restart after that for safe measure.
Unlocking does VOID YOUR MANUFACTURERS WARRANTY (and possibly all others you may have purchased). Make sure you know what you want to do with an unlocked device before you do it. Personally, I am waiting for a stable JB build before I unlock. But the choice is ultimately up to you.
d14b0ll0s said:
Sorry, but I don't get it, what is it about Verizon? Is it because you bought yours from Verizon? Mine comes from ASUS and I believe the OTA updates are from ASUS servers. Is it the US-specific thing that you mentioned?
Click to expand...
Click to collapse
Sorry you're right, must not awake yet. ASUS that is. Thanks bro.
Your going to be fine try learning how to build aosp from source in a time limit
Sent from my Galaxy Nexus using xda premium
Skullmonkey said:
Yeah... Everything is pretty easy even for people that have no clue what they are doing. My suggestion right now is to root but not unlock. Rooting is as simple as running the .bat file and following on screen directions (assuming you are using Windows). The only thing you need to do after the program is finished is to open up the Superuser app (might be SuperSU) and restart after that for safe measure.
Unlocking does VOID YOUR MANUFACTURERS WARRANTY (and possibly all others you may have purchased). Make sure you know what you want to do with an unlocked device before you do it. Personally, I am waiting for a stable JB build before I unlock. But the choice is ultimately up to you.
Click to expand...
Click to collapse
I agree with Skullmonkey on this. Until you are ready for really hacking the system, all you really need is to root the system (run the DebugFS) to get "administrator access to your device".
You might want to read what buhohitr wrote several times as there is much to be gleaned from it. If it helps, copy/paste the contents of buhohitr's repsonse to a notepad text document and go through it word-for-word, isolate those that you find questionable or troublesome, then research what those words are. Anything that is "super difficult" you can just post back here in the Q&A section and I'm sure someone will help you in no time.
another noob question: does rooting the device void manufacturing warranty?
It does not. Only unlocking the device does.
Sent from my Transformer Infinity!
So if I root my Infinity...
...which pre-included apps can I get rid of?
Also which preloaded apps are best to bump off if I dare a root?
I have never dabbled with android down in the file system much for fear of doing something irreparable.
Well, to the OP: we already have quite a few 'basic' threads going on here, and no one forces you to embark on the more advanced stuff, do we? Just read up on it, and when you feel like you can make the jump, pick it up little by little. We're not all experts in here, but most of us can follow directions of the gurus really good, and we have the advantage of knowing how to save our butts when the excrement impacts the ventilator. (And most of us learnt it the hard way, by bricking and breaking...)
You should be fine in the regular forums, and as the others have said, stay out of the development sections until you feel secure enough to dabble around with unlocking and so on.
Sent from my ASUS Transformer Pad TF700T
buhohitr said:
Currently, I suggest you should stay on the side line and waiting for the OTA 4.1.1 JB (new Operating System called Jelly Bean, version 4.1.1 will be push to your pad by Asus). After reading this post you should be ready to play... good luck!
Click to expand...
Click to collapse
What's the method for unrooting/reflashing to stock at the moment? I rooted because I wanted to use Titanium Backup right after I got back up to .26. If we haven't figured out how to custom flash roms by the time jellybean comes out, I'll need to go back to stock. I would *hate* to have to lose all my apps, and its possible that titanium backup from 4.0.3 to 4.1.1 might royally screw up the system in doing a restore. So, if that's the case, I guess I'll reflash someway and lose everything? Doh.
spinaldex said:
What's the method for unrooting/reflashing to stock at the moment? I rooted because I wanted to use Titanium Backup right after I got back up to .26. If we haven't figured out how to custom flash roms by the time jellybean comes out, I'll need to go back to stock. I would *hate* to have to lose all my apps, and its possible that titanium backup from 4.0.3 to 4.1.1 might royally screw up the system in doing a restore. So, if that's the case, I guess I'll reflash someway and lose everything? Doh.
Click to expand...
Click to collapse
Anyone figure out a way to go back from root back to stock yet so that when Jelly Bean comes out we can upgrade?
spinaldex said:
Anyone figure out a way to go back from root back to stock yet so that when Jelly Bean comes out we can upgrade?
Click to expand...
Click to collapse
One method to get rid of root would be factory reset (power on while holding both the power and volume down while booting and running a factory reset.) But you could probably temporarily unroot with voodoo ota root keeper and then reroot once you install the upgrade to jelly bean with its root keeper.
Sent from my DROIDX using xda app-developers app
ekalb10 said:
One method to get rid of root would be factory reset (power on while holding both the power and volume down while booting and running a factory reset.) But you could probably temporarily unroot with voodoo ota root keeper and then reroot once you install the upgrade to jelly bean with its root keeper.
Click to expand...
Click to collapse
That's not true. Funny I've been responding to the same kind of "advice" a few minutes ago in another thread.
Temporarily unrooting through Root Keeper should work, but rooting has prevented updating firmware only for some users. I was rooted and installed updates both manually and through OTA without experiencing any issues. Getting to stock /system partition basically means restoring stock configuration files (like build.prop etc.), removing /system/xbin/su and any copies made by RootKeeper, as well as things that install to /system like BusyBox.
Even if you're rooted you should be able to update firmware manually through stock recovery (power down, power up, hold power and volume down, release, press volume up, etc., with microSD formatted FAT32 and with EP201_768_SDUPDATE on it, it's already in the how-to threads in the general section).
d14b0ll0s said:
That's not true. Funny I've been responding to the same kind of "advice" a few minutes ago in another thread.
Temporarily unrooting through Root Keeper should work, but rooting has prevented updating firmware only for some users. I was rooted and installed updates both manually and through OTA without experiencing any issues. Getting to stock /system partition basically means restoring stock configuration files (like build.prop etc.), removing /system/xbin/su and any copies made by RootKeeper, as well as things that install to /system like BusyBox.
Even if you're rooted you should be able to update firmware manually through stock recovery (power down, power up, hold power and volume down, release, press volume up, etc., with microSD formatted FAT32 and with EP201_768_SDUPDATE on it, it's already in the how-to threads in the general section).
Click to expand...
Click to collapse
I guess I was just misinformed on the factory reset, sorry if I confused anyone.
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app
d14b0ll0s said:
That's not true. Funny I've been responding to the same kind of "advice" a few minutes ago in another thread.
Temporarily unrooting through Root Keeper should work, but rooting has prevented updating firmware only for some users. I was rooted and installed updates both manually and through OTA without experiencing any issues. Getting to stock /system partition basically means restoring stock configuration files (like build.prop etc.), removing /system/xbin/su and any copies made by RootKeeper, as well as things that install to /system like BusyBox.
Even if you're rooted you should be able to update firmware manually through stock recovery (power down, power up, hold power and volume down, release, press volume up, etc., with microSD formatted FAT32 and with EP201_768_SDUPDATE on it, it's already in the how-to threads in the general section).
Click to expand...
Click to collapse
+ 1 I have rooted several tablets/phone over the last two years and backed it up using voodoo rootkeeper with ZERO issues updating firmware/OTAS. The only thing that happens after updating is that I loose root, but that's where voodoo OTA rootkeeper comes to play. Only a handful of people have had problems. Some are legit while others have messed/modded their device prior to updates. (like removeing system apps or modding build. Props)
"60% of the time, it works everytime. "
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Unroot it again ??
If there are problems with the tablet and it must be repaired on warranty, then I need to unroot it again.
How do I unroot it again ??
Regards Peder
Looks like ASUS needs to update the unlock tool to work on JB?
Clearly states on their site that the unlock is for ICS only.
I of course had to try it for fun (I like punishment?) and surely it failed and luckily didn't leave my tablet any worse for wear.
Are a lot of you guys unlocked? What are the greatest benefits you've found from doing so?
Thanks!
Follow this link, or search others, and downgrade to ICS to unlock: http://forum.xda-developers.com/showthread.php?t=1915598 . If you unlock, you will void your warranty, and can only manually update or use a custom Rom.
amenic said:
Looks like ASUS needs to update the unlock tool to work on JB?
Clearly states on their site that the unlock is for ICS only.
I of course had to try it for fun (I like punishment?) and surely it failed and luckily didn't leave my tablet any worse for wear.
Are a lot of you guys unlocked? What are the greatest benefits you've found from doing so?
Thanks!
Click to expand...
Click to collapse
I'd say the majority of general community users are locked, but they probably just buy a device and would never tinker with it. That's not the inclination of the average XDA gadgeteer so I'd wager that most of us in here are either unlocked, or have tried to unlock but failed.
The main goals of unlocking are threefold:
1) installing a custom recovery (thus enabling Nandroid backups)
2) installing Nvflash (making you have to work very hard at being able to brick your device at all)
3) installing custom ROMs
In fact, the general drive to unlock is in point 3, for if you do not plan on installing a custom ROM on your device, there's far less rational incentive to make a Nandroid backup, and you probably would not need the added security of Nvflash -- ASUS will take care of a brick in that case, I guess. So..... the main question is: to customize or not customize?
MartyHulskemper said:
I'd say the majority of general community users are locked, but they probably just buy a device and would never tinker with it. That's not the inclination of the average XDA gadgeteer so I'd wager that most of us in here are either unlocked, or have tried to unlock but failed.
The main goals of unlocking are threefold:
1) installing a custom recovery (thus enabling Nandroid backups)
2) installing Nvflash (making you have to work very hard at being able to brick your device at all)
3) installing custom ROMs
In fact, the general drive to unlock is in point 3, for if you do not plan on installing a custom ROM on your device, there's far less rational incentive to make a Nandroid backup, and you probably would not need the added security of Nvflash -- ASUS will take care of a brick in that case, I guess. So..... the main question is: to customize or not customize?
Click to expand...
Click to collapse
I'm just extremely unimpressed and often times frustrated by the stock performance so I'm looking to try anything to make it better. I've purchased a 32 GB micro SD card and I'm going to move /cache and /data over to it to see if that helps. I'd like to get in on CM10 but from what I've read it's not ready on the TFI yet but definitely will do that once it is.
I unlocked my TF700 on Jelly Bean using the unlock tool without any issue.
MartyHulskemper said:
2) installing Nvflash (making you have to work very hard at being able to brick your device at all)
Click to expand...
Click to collapse
Sadly I updated to the update right before JB about 10 minutes before the announcement of the Nvflash.
And since you cannot go back down, I am stuck without Nvflash and as such I am staying stock until we get it for JB, then I will unlock and work this old girl.
Didn't work on the 10.4.4.16 firmware 10.4.4.18 seems to work fine - sweet! unlocked!
I have only rooted unlocked the bootloader on a acer a100 7" tab and kept the oringinal stock os but, it only cost $150.00. I have also rooted and nvflashed a Viewsonic G tab but, I did not have to unlock a bootloader. The reason I did not install a custom rom on the Acer a100 was because I did not see any great improvements over the original stock. The Viewsonic however was a different story. The custom roms all the way from froyo to JB has made this tabby 1000% better than it ever was but, with nvflash I could restore it to original condition and send it to Viewsonic for warranty repair or replacement. Will nvflashing the TF700 allow me to do that? Are the custom rom that are out that much better than the Asus JB update? .I can understand rooting because I can install SuperSU, and I think but not sure (i believe I read this will require unlocking the bootloader) a custom recovery so I can backup the boot.img and all apps and install apps that require root. Sorry if this question has be asked but did not get any results when inputting this question that related to the TF700. Thanks
ps: my TF700 is being delivered tomorrow.
lartomar2002 said:
I have only rooted unlocked the bootloader on a acer a100 7" tab and kept the oringinal stock os but, it only cost $150.00. I have also rooted and nvflashed a Viewsonic G tab but, I did not have to unlock a bootloader. The reason I did not install a custom rom on the Acer a100 was because I did not see any great improvements over the original stock. The Viewsonic however was a different story. The custom roms all the way from froyo to JB has made this tabby 1000% better than it ever was but, with nvflash I could restore it to original condition and send it to Viewsonic for warranty repair or replacement. Will nvflashing the TF700 allow me to do that? Are the custom rom that are out that much better than the Asus JB update? .I can understand rooting because I can install SuperSU, and I think but not sure (i believe I read this will require unlocking the bootloader) a custom recovery so I can backup the boot.img and all apps and install apps that require root. Sorry if this question has be asked but did not get any results when inputting this question that related to the TF700. Thanks
ps: my TF700 is being delivered tomorrow.
Click to expand...
Click to collapse
OK, see if I can make this short and clear:
1. If you rooted, you can roll back to original factory state (send back for repair or exchange), with root you can installed rooted application like Titanium backup, setCPU, modify boot.prop, gps.conf etc...)
2. If you unlocked (you void warranty, there is NO WAY you could re lock your device), with unlock you could install NVflash, install custom recovery to do nanodroid backup (backup the OS and all the apps), flash custom rom/kernel etc..
3. If you compare a good device (a device without problem), that running stock JB and custom rom, the speed is about almost the same, the only benefit with custom rom is you could install custom apps, themes etc..but as far as performance and smoothness they about the same.
I found that strip down custom rom like "Cleanrom" does have an advantage with memory since all the bloats are removed, so I have more memory available to the OS. In my opinion, this thing should have 2gb of memory vs 1gb. There are many times, my memory went down below 150 and I do feel the sluggishness. To combat against this issue, I installed memory management app and it's been good since.
buhohitr said:
OK, see if I can make this short and clear:
1. If you rooted, you can roll back to original factory state (send back for repair or exchange), with root you can installed rooted application like Titanium backup, setCPU, modify boot.prop, gps.conf etc...)
2. If you unlocked (you void warranty, there is NO WAY you could re lock your device), with unlock you could install NVflash, install custom recovery to do nanodroid backup (backup the OS and all the apps), flash custom rom/kernel etc..
3. If you compare a good device (a device without problem), that running stock JB and custom rom, the speed is about almost the same, the only benefit with custom rom is you could install custom apps, themes etc..but as far as performance and smoothness they about the same.
I found that strip down custom rom like "Cleanrom" does have an advantage with memory since all the bloats are removed, so I have more memory available to the OS. In my opinion, this thing should have 2gb of memory vs 1gb. There are many times, my memory went down below 150 and I do feel the sluggishness. To combat against this issue, I installed memory management app and it's been good since.
Click to expand...
Click to collapse
Thank you, you were clear and concise. About memory though, could I not use an app like System Tuner Pro or System Cleanup to uninstall the bloatware? I have done that with the Viewsonic G tab it only has 512mb of ram and the developers have squeezed JB into it with approx 100mb of ram left to allow for the different things it has to do. As long as you do not have to many things running at the same time and try to keep recent apps cleared out, JB runs very smoothly.
lartomar2002 said:
Thank you, you were clear and concise. About memory though, could I not use an app like System Tuner Pro or System Cleanup to uninstall the bloatware? I have done that with the Viewsonic G tab it only has 512mb of ram and the developers have squeezed JB into it with approx 100mb of ram left to allow for the different things it has to do. As long as you do not have to many things running at the same time and try to keep recent apps cleared out, JB runs very smoothly.
Click to expand...
Click to collapse
If your device is not rooted, you should not have access to the folders these apps' files reside in. In other words: no, you can't. To me, having root access provides a means of treating my device like I want to, instead of the way the manufacturer wants me to. Apps like Titanium Backup provide data backup and the possibility to side-load easily. And indeed you could kill off bloatware, although a custom ROM mostly takes care of that issue for you. Oh, and Total Commander needs root access to be able to transfer files to and from both the internal and external memory.
MartyHulskemper said:
If your device is not rooted, you should not have access to the folders these apps' files reside in. In other words: no, you can't. To me, having root access provides a means of treating my device like I want to, instead of the way the manufacturer wants me to. Apps like Titanium Backup provide data backup and the possibility to side-load easily. And indeed you could kill off bloatware, although a custom ROM mostly takes care of that issue for you. Oh, and Total Commander needs root access to be able to transfer files to and from both the internal and external memory.[/QUOTEto
Thank you. I had pretty much decided to root which is not a big problem for me. I have done it to 3 or 4 tablets already. I am how ever concerned about unlocking the bootloader and voiding the warranty. I had to return one tablet for warranty work but by nvflashing it I was able to get it back to factory condition. May in the future someone will figure a way around the Asus block, then I will unlock it. I have faith in the xda community.
Click to expand...
Click to collapse
lartomar2002 said:
MartyHulskemper said:
If your device is not rooted, you should not have access to the folders these apps' files reside in. In other words: no, you can't. To me, having root access provides a means of treating my device like I want to, instead of the way the manufacturer wants me to. Apps like Titanium Backup provide data backup and the possibility to side-load easily. And indeed you could kill off bloatware, although a custom ROM mostly takes care of that issue for you. Oh, and Total Commander needs root access to be able to transfer files to and from both the internal and external memory.[/QUOTEto
Thank you. I had pretty much decided to root which is not a big problem for me. I have done it to 3 or 4 tablets already. I am how ever concerned about unlocking the bootloader and voiding the warranty. I had to return one tablet for warranty work but by nvflashing it I was able to get it back to factory condition. May in the future someone will figure a way around the Asus block, then I will unlock it. I have faith in the xda community.
Click to expand...
Click to collapse
Due to the level of encryption, the unlock tool will not be available by third parties. The encryption will not be circumvened, unless ASUS posts the key due to end-of-life. There's a thread somewhere in which we already discussed this. It comes down to either unlock (and you might as well do it now and get the best performance -- the current CleanROM flies!) or not unlock (ever).
Click to expand...
Click to collapse
MartyHulskemper said:
lartomar2002 said:
Due to the level of encryption, the unlock tool will not be available by third parties. The encryption will not be circumvened, unless ASUS posts the key due to end-of-life. There's a thread somewhere in which we already discussed this. It comes down to either unlock (and you might as well do it now and get the best performance -- the current CleanROM flies!) or not unlock (ever).
Click to expand...
Click to collapse
Thank you. You have given me the push I needed to unlock and root but first I would like to install the nvflash. I did it once with a Viewsonic G tab but if I recall it was not this complicated. I have a Win7 64 bit pc and I am not sure which of the 3 drivers I am suppose to use. I have posted in their comment section so hopefully they will get back to me. I have never had to use ADB but I found a web site "ADB for Dummies" that has a guide and a link to download the ADB drivers, not sure how old they are or if they need to be updated. I have only read of "fastboot" in some post but it never pertained to me so I ignored it. As you can see I have some boning up to do. If you could point be to some threads or pages that might speed this along I would greatly appreciate it. Many of you have several months head start on me. Thanks
Click to expand...
Click to collapse
I think the best one is here: http://forum.xda-developers.com/showthread.php?t=1901479, although that is probaby the one you are referring to posting in. Their guides are pretty extensive and cover most issues nicely, but I had one issue I cannot find in the others' posts: I have to restart the adb server before any meaningful connection is made between my x64 W7 machine and the 700. Somehow, it hangs up when it should initialize. It's not ftal, but supremely annoying. Just browse to the platform-tools directory, (SHIFT+)right-click and choose " Open command window here", and input the following commands in there: "adb kill-server" and "adb start-server" whenever you get the message complaining about "too much links"
If you get stuck, you can PM me -- I am going on a vacation, but, knowing me, I'll be in here more than is good for me.
MartyHulskemper said:
I think the best one is here: http://forum.xda-developers.com/showthread.php?t=1901479, although that is probaby the one you are referring to posting in. Their guides are pretty extensive and cover most issues nicely, but I had one issue I cannot find in the others' posts: I have to restart the adb server before any meaningful connection is made between my x64 W7 machine and the 700. Somehow, it hangs up when it should initialize. It's not ftal, but supremely annoying. Just browse to the platform-tools directory, (SHIFT+)right-click and choose " Open command window here", and input the following commands in there: "adb kill-server" and "adb start-server" whenever you get the message complaining about "too much links"
If you get stuck, you can PM me -- I am going on a vacation, but, knowing me, I'll be in here more than is good for me.
Click to expand...
Click to collapse
Yes that is the one. I am going to call it quits for today I have been at this for 8 hrs already.
Hi everyone
First off I would like to thank everyone who contributes on this board, I have been lurking for quite awhile even though I dont have any android devices, the reading is very interesting.
I have just got my first android device today delivered from BH Photo (I am in Australia) and have charged and powered it up. I have been reading on the forums about rooting and then unlocking. The android version appears to be 4.0.3 (ICS).
My questions are these:
Should I root this device and unlock the bootloader with ICS, then install TWRP and make a backup of it. Once this is done then update to JB? The firmware of the tablet is (I think this is right) IM74K:US_epad_9.4.5.26-20120720 and the kernel is 2.6.39.4 [email protected] #1
or
Update the device to JB then root it, but Im a bit confused with the unlocking part here what program is used to unlock the bootloader? Is it the Asus one? Also with rooting programs which one is more commonly used for both ICS and JB? Can I apply a manual update of JB using the Ausrtalian version instead of the US one.
Sorry for all the noob questions. I have read the index and after reading it still had some questions.
Thank you for your time
deathwalker01 said:
Hi everyone
First off I would like to thank everyone who contributes on this board, I have been lurking for quite awhile even though I dont have any android devices, the reading is very interesting.
I have just got my first android device today delivered from BH Photo (I am in Australia) and have charged and powered it up. I have been reading on the forums about rooting and then unlocking. The android version appears to be 4.0.3 (ICS).
My questions are these:
Should I root this device and unlock the bootloader with ICS, then install TWRP and make a backup of it. Once this is done then update to JB? The firmware of the tablet is (I think this is right) IM74K:US_epad_9.4.5.26-20120720 and the kernel is 2.6.39.4 [email protected] #1
or
Update the device to JB then root it, but Im a bit confused with the unlocking part here what program is used to unlock the bootloader? Is it the Asus one? Also with rooting programs which one is more commonly used for both ICS and JB? Can I apply a manual update of JB using the Ausrtalian version instead of the US one.
Sorry for all the noob questions. I have read the index and after reading it still had some questions.
Thank you for your time
Click to expand...
Click to collapse
Welcome to the Community!
There are a few on-going threads regarding this same topic. You might want to read those and make sure you understand the lingo/jargon being used (like: fastboot, bootloader, Recovery, adb. etc) as well as what it's for before you start your hacking.
Some things to keep in mind
Currently to have Root access in JB, you need to get root in ICS then use OTA Keeper to maintain Root for JB update.
The Bootloader unlocker tool is from ASUS and needs to communicate with ASUS servers for it to unlock.
Unlocking the bootloader will void your warrenty. Make sure you have a good device before you do it.
You have a version of tablet (9.4.5.26) that is able to use NVFlash that can help recover your tablet during a soft brick.
You should use an update that is appropriate for your device. If it comes with US, stay with US. Installing an update for a different region might not cause problems but there is no guarantee. Best to avoid the possibility by staying with the region it comes with.
For some reading material, I think that my blog post might help give you some additional details. However, I highly suggest that it be used for research only until you are aware of exactly what you are trying to accomplish. Remember to ask questions if things are confusing or if you are wondering what needs to be done next. 'Tis better to ask and be delayed than to be over-eager and bricked.
Hope this helps you during your first steps of XDA Android hacking!
I just got my TF700 last week and I wanted cleanrom on it and this is the order of stuff I did:
1. Unlocked bootloader
2. Nvflash setup
3. Installed TWRP
4. Flashed official Asus update
5. I lost TWRP so I installed it again
6. Flashed cleanrom
Probably not the most efficient way, but it was easy to do and didn't take too long.
hong90 said:
I just got my TF700 last week and I wanted cleanrom on it and this is the order of stuff I did:
1. Unlocked bootloader
2. Nvflash setup
3. Installed TWRP
4. Flashed official Asus update
5. I lost TWRP so I installed it again
6. Flashed cleanrom
Probably not the most efficient way, but it was easy to do and didn't take too long.
Click to expand...
Click to collapse
It's the most efficient way.
I have nothing to add except for the remark that NvFlash is key -- GET IT WHILE YOU STILL CAN!
I'm not even kidding here. It gives you 100% flexibility in doing whatever you wish (up- as well as downgrading, even the bootloader!) and provides a key benefit in recovering your device when that whale-sized piece of excrement hits the large ventilator running at top speed.
Thanks to everyone that has replied to my post. I have successfully rooted the tablet and unlocked the bootloader. Before I do anything else Im going to run NVflash and back it up. I have a quick question though. I have download NVFlash to my computer and extracted it. Do I need to copy it across to the tablet and then enter fastboot? I havent got an extenal sd card will it save the images to the tablet's hard drive?
Cheers
Deathwalker
i followed this video:
https://www.youtube.com/watch?v=J3ypzUaKxvo&feature=youtube_gdata_player
i watched it before i actually did it once or twice to make sure i know what to do. you don't need an external sd card. following the fastboot steps will pull the files that you need onto the internal one in a folder
Last night I used NVFlash to make backup of the tablet. A big thank you to alienedd as I followed his blog and also the guide from androidmobi team and managed to get the img files done. Is there anyway to test bar for wiping the tablet?
Now all I have left to do is install OTA RootKeeper and TWRP, back up the existing tablet and then flash a custom ROM (Im thinking cleanrom)
You don't need OTA Rootkeeper anymore because you have unlocked you're bootloader. And custom roms like Cleanrom are already pre-rooted so after flashing the cleanrom you will have root anyway.
hey, i just registered here to inform you all that ive figured out a way to root the new rca viking pro, but i cant seem to get supersu to install its updated binaries... i went about it like this, i searched google for kingroot app, installed it, followed the instructions it came with, and for my own benefit, i ran it twice just to make sure it worked. and wala, root! but the downside is they have their own form of su called king user. and i hate it. i hope this info helps someone, as ive came to this site on so many occaisions and everytime something on here bailed me out of a jam, i figured it was bout time i gave to a site that contributed so much to me. i love xda, and i hope someone here can get some nice things going with this tablet. thanks for your time... May
info on the RCT6303W87DK
also, FOR YOUR OWN GOOD, DO NOT CHANGE THE GENERIC.kl file on this device!!! the keyboard that comes with it, and the volume and power buttons on the device will NO LONGER function!!! just got a replacement from wallyworld because of my epic failure.... YOU HAVE BEEN WARNED!!! :good:
I tried a few different methods last night to install supersu binaries effectively breaking root a few times all resulting in using king root to "reroot". The main issue I'm having is it immediately has an update to version 1.9.1 (tablet firmware).. To get around this prompt lock the tablet, turn screen back on but unlock it with camera (bottom right). After doing this you get home rows back. Now since root I'm getting failures to install the update and every time it comes on I'm promoted for the update multiple times. Any ideas?
reemobeens19 said:
I tried a few different methods last night to install supersu binaries effectively breaking root a few times all resulting in using king root to "reroot". The main issue I'm having is it immediately has an update to version 1.9.1 (tablet firmware).. To get around this prompt lock the tablet, turn screen back on but unlock it with camera (bottom right). After doing this you get home rows back. Now since root I'm getting failures to install the update and every time it comes on I'm promoted for the update multiple times. Any ideas?
Click to expand...
Click to collapse
you have to be unrooted to apply system updates... then re root. king root should have an unroot option in app, so un rooting isnt hard. or you can hook the tab to your pc and use kingo to unroot. it will unroot, but it wont root...
I can confirm that kingroot does in fact have an option to unroot. I can also confirm that it is able to reroot after the 1.9.1 update.
Mine updated to that the first time I turned it on and I lost the update file. Can anyone tell a difference before and after the update?
I'm going to do a full stock ROM dump tonight to share. Just in case me or anyone else screws theirs up. I want to install a custom recovery and don't want to take any chances with it. Locked mtk bootloaders are ugly. Especially on these newer chipsets which cannot be unlocked as easily as the old ones.
Btw, before I finally found kingroot I must have tried about thirty different ways to root this thing. I tried several on phone root apps and a bunch of ones which required a pc connection to work and I came up short.
I got partial root with iroot 1.7 something for PC. It installed kingroot and would say that it was granting root to apps but noting actually had root.
Finally I found the latest version of vroot. V1.8 something, it had the same root database number as the earlier iroot which I had, though. Then I installed the pdanet drivers and ran the vroot and it worked! Finally! I spent hours on the stupid thing.
I did try the kingroot (iroot) apk and it couldn't root it and suggested I try the PC version.
What I'm getting at is that possibly fw 1.9.1 is just a security patch that makes it harder to root. Because when I tried the apk it couldn't handle it and I had to use the PC version with pdanet drivers to get it to work. While the apk worked for you on v1.9.0 (mine updated the first time I powered it on).
So if you install the update you might want to watch out for that.
It may be possible to stop the forced ota with fotakill. Just Google the apk and place it in your /system/app folder, then delete it rename the update in your cache folder and restart.
That has always worked for me so far on all of my other Android devices.
Cheers,
-SS
Used titanium back up to freeze the updater. Went to Dev options, enabled show processor usage or something to that nature.. Watched for any thing popping up that said update. I don't remember the exact apk but a simple search with in titanium for the word update returns the only app containing it. This did indeed solve my problem about the constant update. Also another work around to bypass the update, tell it to "download and install" then immediately his stop/cancel download. This will be my last post for now on the device as I no longer own it.
Have a blessed day!
For those wanting wired controller support, tincore works wonderfully. Im using an official xbox360 control and it controls the ui and a majority of my games. Emulators as well. This is pretty much the only way to use a wired control on this tablet as far as i know. I've tried dozens of methods to no avail. Still trying to get su up and running as well. King root does function but id prefer something im used to. Anyone know of a custom recovery that'd work on this thing???
simstimstar said:
I can confirm that kingroot does in fact have an option to unroot. I can also confirm that it is able to reroot after the 1.9.1 update.
Mine updated to that the first time I turned it on and I lost the update file. Can anyone tell a difference before and after the update?
I'm going to do a full stock ROM dump tonight to share. Just in case me or anyone else screws theirs up. I want to install a custom recovery and don't want to take any chances with it. Locked mtk bootloaders are ugly. Especially on these newer chipsets which cannot be unlocked as easily as the old ones.
Btw, before I finally found kingroot I must have tried about thirty different ways to root this thing. I tried several on phone root apps and a bunch of ones which required a pc connection to work and I came up short.
I got partial root with iroot 1.7 something for PC. It installed kingroot and would say that it was granting root to apps but noting actually had root.
Finally I found the latest version of vroot. V1.8 something, it had the same root database number as the earlier iroot which I had, though. Then I installed the pdanet drivers and ran the vroot and it worked! Finally! I spent hours on the stupid thing.
I did try the kingroot (iroot) apk and it couldn't root it and suggested I try the PC version.
What I'm getting at is that possibly fw 1.9.1 is just a security patch that makes it harder to root. Because when I tried the apk it couldn't handle it and I had to use the PC version with pdanet drivers to get it to work. While the apk worked for you on v1.9.0 (mine updated the first time I powered it on).
So if you install the update you might want to watch out for that.
It may be possible to stop the forced ota with fotakill. Just Google the apk and place it in your /system/app folder, then delete it rename the update in your cache folder and restart.
That has always worked for me so far on all of my other Android devices.
Cheers,
-SS
Click to expand...
Click to collapse
When I first got the tablet, i let it update then got the kingroot apk, installed it and it rooted. The one i used is in chinese but it had instructions and i followed them to the t. It worked. And the back up of the rom would be greatly appreciated by ALOT of us trust me. Especially me...?
Overall, this is a pretty nice tablet to own. The space alone is worth the price of admission. The specs are decent as well. Quad core, mali gpu, one gb ram, the detachable keyboard, oh i could go on. Im a heavy gamer and this is perfect for me. I have all the power i need to run everything i use. And with a 32 gb sdcard and 32gb internal, thats plenty storage for pretty much anything. I recommend this device to anyone looking for performance on a budget. 10/10
Yes, I'ts very nice. I couldn't find anything else that would even come close to it in that price range. Even used ones....
I was able to edit some config files for mrkdroidtools and got it working properly with mt8127 for the most part. At least now it will create the proper scatter file (in the correct format) for mt8127. Even though it's working properly to create the scatter, you have to use Windows enabler to allow to click the greyed out scatter file button. Before if you did that it would create a scatter in the old format without correctly identifying partition types and even not setting the correct partition sizes in the scatter. Also the chip was identified incorrectly before and now it's not.
All of the mt8127 scatters I have seen use scatter v1.1.2 (not the old format) and now I got it to output that. With proper scatter you can manually pull each partition correctly in spft.
Mtkdroidtools will now partially work for backup. It will pull firmware.info, mounts.info, and phone.info. along with NVRAM and /system only. Can't pull the others because the partitionsions are locked. Even with insecure adb (root ADB) and selinux set to permissive.. You can get old style scatter from firmware.info and mtk studio, but better to let mtkdroidtools pull the correct one.
It will try to make the CWM recovery but fails out. Magic twrp will now create the correct recovery and push it to the phone (with files from spft backup) but the recovery won't work due to the locked loader.
At least I know my backup works now because I was able to reflash the original recovery with it (this is how I screwed up my first one, which ended up going back to Wal-Mart). That first one stopped booting, but it was still recognized by spft. I just had no backup to fix it with. If they rma it, I'm sure it can be reflashed with original firmware and resold.
I will be putting this all in a toolkit and uploading. This can benefit all devices with mt8127, not just us. I also have the latest spft and I even found the checksum.exe in another package somewhere. This can be used to generate the firmware checksums for spft so you don't have to flash with checksum turned off (safer).
Haven't tried to reroot with mtkdroidtools because I think the supersu is pretty old. Don't think it will work properly in lollipop.
I wish there was a way to unlock the bootloader. I poked around in my backup of it and it clearly references files from NVRAM. Files with checksums and lists. I would think that there would be some other tablet sold under a different brand which is unlocked out there
Somewhere which is the same as ours.
Gotta run. I'll try to upload the toolkit after work if there is time. I need to clean up my backup to remove personal files from data before uploading. If it's an emergency and someone needs backup without /data I can provide now. Don't know if it will work though because kingroot resides on data. Perhaps it will work just can't authorize root.
Cheers!
-SimStim
Again, with the new one I got I couldn't root with the latest iRoot from the PC until pdanet was installed on the phone. Then it worked fine.
Without pdanet it will get temp root, then restart and when kingroot automatic root check runs it says no root and will try again and again in a loop.
With pdanet, temp root, reboot, and it's permanent root.
Just in case anyone is trying to root via this method.
Cheers!
-SimStim
simstimstar said:
Again, with the new one I got I couldn't root with the latest iRoot from the PC until pdanet was installed on the phone. Then it worked fine.
Without pdanet it will get temp root, then restart and when kingroot automatic root check runs it says no root and will try again and again in a loop.
With pdanet, temp root, reboot, and it's permanent root.
Just in case anyone is trying to root via this method.
Cheers!
-SimStim
Click to expand...
Click to collapse
You may be right... The first one i had i let kingoroot on the pc download and install some drivers. And i used pdanet awhile ago for a previous rca tab and never deleted the drivers, so maybe thats why it worked flawlessly the second time. If you have a custom recovery installed, which did you use and how'd you install it?
I tried the "magic" auto-build of CWM and TWRP, but neither one works because of the locked boot loader.
Which also makes me wonder if my backup would work on someone else's tab... The 7" RCA tab on here with the prerooted ROM works because they found another tablet which was the same and had an unlocked bootloader. At least that's what understood from it. I could be wrong though. I didn't read all 35 pages (or however many).
I'll try and double check that
Cheers,
-SimStim
simstimstar said:
I tried the "magic" auto-build of CWM and TWRP, but neither one works because of the locked boot loader.
Which also makes me wonder if my backup would work on someone else's tab... The 7" RCA tab on here with the prerooted ROM works because they found another tablet which was the same and had an unlocked bootloader. At least that's what understood from it. I could be wrong though. I didn't read all 35 pages (or however many).
I'll try and double check that
Cheers,
-SimStim
Click to expand...
Click to collapse
any progress yet? ive been searching hi and lo for custom recoveries that work to no avail. i want to try and unlock the bootloader but im afraid i may screw somthing up if i cant restore a backup. i guess its a chance im willing to take if it furthers development on this tablet. i honestly want to rip lollipop off of here and run jb 4.2.2. personally i think thats the best version of android yet. at least with funcionality. and the fact you can just plug and play on that version is a plus for me!!! hope you come across something....
may
I'm planning to return mine. I started looking around at tablets in this price range and have decided to buy a Pipo M9S instead. The price is pretty close and it absolutely spanks this device in hardware specs.
I'm somewhat biased, because I have an Android tv device based on the RK3288 and I know how fast it is. The hardware video decoder is the best I've seen yet. Plus it is so nice not to have to deal with the locked bootloader.
I wanted an RK3288 based tablet before, but was put off by the $200-300 price range which I had seen on the Pipo P9 and the P1. Then just recently I found that I could get a p7 for ~150 and an M9S for ~$175, so I've decided that I would much rather go that way(M9S).
I will hang on to my backup of this device in case it will come in handy for anyone else in the future.
Cheers,
-SimStim
simstimstar said:
Yes, I'ts very nice. I couldn't find anything else that would even come close to it in that price range. Even used ones....
I was able to edit some config files for mrkdroidtools and got it working properly with mt8127 for the most part. At least now it will create the proper scatter file (in the correct format) for mt8127. Even though it's working properly to create the scatter, you have to use Windows enabler to allow to click the greyed out scatter file button. Before if you did that it would create a scatter in the old format without correctly identifying partition types and even not setting the correct partition sizes in the scatter. Also the chip was identified incorrectly before and now it's not.
All of the mt8127 scatters I have seen use scatter v1.1.2 (not the old format) and now I got it to output that. With proper scatter you can manually pull each partition correctly in spft.
Mtkdroidtools will now partially work for backup. It will pull firmware.info, mounts.info, and phone.info. along with NVRAM and /system only. Can't pull the others because the partitionsions are locked. Even with insecure adb (root ADB) and selinux set to permissive.. You can get old style scatter from firmware.info and mtk studio, but better to let mtkdroidtools pull the correct one.
It will try to make the CWM recovery but fails out. Magic twrp will now create the correct recovery and push it to the phone (with files from spft backup) but the recovery won't work due to the locked loader.
At least I know my backup works now because I was able to reflash the original recovery with it (this is how I screwed up my first one, which ended up going back to Wal-Mart). That first one stopped booting, but it was still recognized by spft. I just had no backup to fix it with. If they rma it, I'm sure it can be reflashed with original firmware and resold.
I will be putting this all in a toolkit and uploading. This can benefit all devices with mt8127, not just us. I also have the latest spft and I even found the checksum.exe in another package somewhere. This can be used to generate the firmware checksums for spft so you don't have to flash with checksum turned off (safer).
Haven't tried to reroot with mtkdroidtools because I think the supersu is pretty old. Don't think it will work properly in lollipop.
I wish there was a way to unlock the bootloader. I poked around in my backup of it and it clearly references files from NVRAM. Files with checksums and lists. I would think that there would be some other tablet sold under a different brand which is unlocked out there
Somewhere which is the same as ours.
Gotta run. I'll try to upload the toolkit after work if there is time. I need to clean up my backup to remove personal files from data before uploading. If it's an emergency and someone needs backup without /data I can provide now. Don't know if it will work though because kingroot resides on data. Perhaps it will work just can't authorize root.
Cheers!
-SimStim
Click to expand...
Click to collapse
if you still have it, can you upload that stock image and the tools you have? or send them to me via email? ive done something terrible and i wish to go back to stock until i figure something else out. if you can do it via email, heres my [email protected]- thanks
How can I contribute
While I haven't had any issues with my DK on v1.9.1, I'm always interested in the latest and greatest Android ROM. I've got my fingers crossed for you on making restore images so you can get another ROM built on this. So, if I can contribute, even if it is paypal'ing $20 to pay toward a second tablet for you to work on, let me know.
Regards,
David
Is anyone working on unlocking the bootloader of this device? Fastboot allows me to see the "press volume up key to unlock" screen using fastboot oem unlock, however it does not respond to volume keys. Being that I got that far could it possibly succeed if it didn't have to prompt for permission?
It's going to be really tough to try and crack it. The RCA 7" tablet here on xda that got an unlocked loader because they found out that there was a Cube branded tablet which was identical, except it had an unlocked boot loader.
RCA is not the actual manufacturer (I forget who is, but cpu-z will tell you I think). Perhaps if someone were to contact the manufacturer and find out which other companies they OEM that tablet hardware to. Then check them out for unlocked bootloaders.
I would be willing to bet that they may not reveal that info so easily, so try looking around for similar hardware.
I found on a benchmarking site that the RCA 10" which doesn't have the keyboard is also the same spec and model number as a model sold by gigabyte. I don't know the status of the bootloader, though. If you flash it you risk bricking your tablet.
MTK is pretty much the opposite of rockchip, who has made their devices nearly brick proof. MTK devices with locked bootloaders are very likely to brick because of the security measures built in, odd and often encrypted filesystems with specific hashes for certain partitions, write protection on the main system partions. It's really a massive pain in the neck. Those are the reasons why I decided to get rid of mine.
It's rooted and someone who doesn't want to build custom ROMs will be perfectly happy with it. Me, I want full access! Really the tablet is pretty nice. Just not if you want custom recovery, kennel, unofficial ROMs, etc.
I'm still looking. It's probably out there somewhere. I'll be sure to post if I see anything.
Cheers,
-SS
How do you know the bootloader is locked? I see walmart has cut the price on them, I haven't seen any rca tablets with bootloader locked.