Ok I wasnt paying attention when the guy at best buy was messing with my tablet I bought today and I think it updated to ics 4.1 or whatever its on now. But I have managed to unlock my tablet but I cant seem to root it for some reason. Is their anyway to go back to the factor honeycomb or am I F'ed?
EchoM3TH said:
Ok I wasnt paying attention when the guy at best buy was messing with my tablet I bought today and I think it updated to ics 4.1 or whatever its on now. But I have managed to unlock my tablet but I cant seem to root it for some reason. Is their anyway to go back to the factor honeycomb or am I F'ed?
Click to expand...
Click to collapse
If you have unlocked the bootloader just boot into CWM make a nandroid backup then flash a custom rom and you should be rooted with a custom rom. If you're looking for a more custom feel. Try AOKP (All Open Kang Project) they have a extension in settings app thats called rom control and lets you change a lot of things. Then maybe if you're tired of the ICS blue scheme try out my theme for AOKP =) link is in my sig.
Theres really no reason to stay stock since you've already unlocked the bootloader so yeah. But if you're looking for a stock asus rom, but with some optimizations your next best bet would be Virtuous and WSG Roms.
I don't know the relationship between unlocking and rooting....but if you're on a stock ROM, it can't be rooted yet....the 'root tool" hasn't been developed yet.....but I don't know how unlocking affects the process
it gives me a little dead android.
EchoM3TH said:
it gives me a little dea d android.
Click to expand...
Click to collapse
If you unlocked BEFORE it was updated, then you're right....read the threads on recovering from that situation.
I guess my question is, are you sure it's unlocked (the answer is probably YES), but I had a rooted V15, with some modded files....and got the dead guy.....had to update to v21 via the SD card.
Good luck
EchoM3TH said:
it gives me a little dead android.
Click to expand...
Click to collapse
Did you or did you not unlock your prime using the asus unlock tool app? If you did after you have unlocked your prime.
1. Go to market and download rom manager
2. Install CWM via rom manager.
3. Download a Custom Rom and transfer it to your tablet.
4. Boot into CWM Via Make sure its powered off, hold power and volume down till you see some white fine printed words on your upper left hand side. Then hit the Volume Up.
5. Once your into CWM using your Volume buttons (Power button to select) to navigate to Backup/restore & create your first nandroid backup.
6. Install the custom rom you have downloaded.
7.Boot it up.
8.Profit????
My device is unlocked i went through the vipers way too root/unlock device, it says that it rooted it but I went to see if superuser was on my tablet it wasnt. so i downloaded via market place and went to update the binary and its say busybox not found then says ok. checking md5sum okay then install path fail.
EchoM3TH said:
My device is unlocked i went through the vipers way too root/unlock device, it says that it rooted it but I went to see if superuser was on my tablet it wasnt. so i downloaded via market place and went to update the binary and its say busybox not found then says ok. checking md5sum okay then install path fail.
Click to expand...
Click to collapse
Again & again i must stress the fact that you should search and do some reading. Vipers Tool does not work with .21 so can you now boot into your tablet.
Root = allowing you to have system file access
Unlock = allowing you to install a custom recovery, thus letting you install custom roms.
Unlocking voids your warranty, while root does not. If you don't mind the voided warranty boot into your tablet and open the app drawer and look for the unlocking tool. Then run it and you should be unlocked. Then follow my previous post.
reNeglect said:
Again & again i must stress the fact that you should search and do some reading. Vipers Tool does not work with .21 so can you now boot into your tablet.
Root = allowing you to have system file access
Unlock = allowing you to install a custom recovery, thus letting you install custom roms.
Unlocking voids your warranty, while root does not. If you don't mind the voided warranty boot into your tablet and open the app drawer and look for the unlocking tool. Then run it and you should be unlocked. Then follow my previous post.
Click to expand...
Click to collapse
That still tells me its not rooted. can I downgrade to a older version like.20 or something. I did it once with my Evo4g.
Related
A friend of mine had her Eris metroflashed to MetroPCS. Calls and SMS work, but she wants me to provision the rest of it to work like i did with my own Eris on metro. I tried it to find out the Eris one click root app is not on the market anymore however i had the APK, erisone.apk. I loaded it to her SD card and downloaded Astro File Manager and attempted to install, which it proceeded to tell me it couldnt be installed on that phone. All i need is RA-Eris recovery as i will be loading a custom ROM. Is there an easy way to change the recovery on it so i can do this? I was thinking i just needed to update to 2.1 OTA (can someone provide the link? the old link from google doesnt work anymore) then the Erisone.apk will work (this apk loads custom recovery as well as a root very easily). I need to load a custom ROM before i can begin with the provisioning, what do you guys think i should do?
Does this work http://forum.xda-developers.com/showthread.php?t=742228?
Or see this list of options that scary alien provided http://forum.xda-developers.com/showthread.php?p=10013596#post10013596.
roirraW "edor" ehT said:
Does this work http://forum.xda-developers.com/showthread.php?t=742228?
Or see this list of options that scary alien provided http://forum.xda-developers.com/showthread.php?p=10013596#post10013596.
Click to expand...
Click to collapse
The top one is one i tried. The bottom link there mainly concerns rooting. Im trying to install a custom rom thats already rooted so i don't care much for rooting but i guess its necessary to install a new recovery image right? All i want to do is install ra-eris recovery so i can load a custom rom. The one click method you linked automatically installs a new recovery image and thats what im really after. I just don't think that one you linked is compatible with 1.5
Helgaiden said:
The top one is one i tried. The bottom link there mainly concerns rooting. Im trying to install a custom rom thats already rooted so i don't care much for rooting but i guess its necessary to install a new recovery image right? All i want to do is install ra-eris recovery so i can load a custom rom. The one click method you linked automatically installs a new recovery image and thats what im really after. I just don't think that one you linked is compatible with 1.5
Click to expand...
Click to collapse
You have to be rooted and have a custom recovery in order to install a custom ROM.
Editing...ignore what I had posted in this space before.
The second link (starts with "Failing that...") says it works with 1.5.
You have to be rooted to have a custom recovery. This i know...but can you have a custom recovery without being rooted? I dont care about getting this phone rooted, i just want a custom recovery on it.
Helgaiden said:
You have to be rooted to have a custom recovery. This i know...but can you have a custom recovery without being rooted? I dont care about getting this phone rooted, i just want a custom recovery on it.
Click to expand...
Click to collapse
You HAVE to be rooted to change: recovery, kernel, hboot, ROM, and radio. The only exceptions are official updates, whether they be OTA or running a RUU update from Windows with the phone connected.
Root access effectively means being able to change things you're not normally allowed to change.
If you want a custom recovery on your phone, you're going to have to root it. To be technically fully rooted, you would probably have to change your hboot (referred to as S=OFF), too, but it doesn't sound like you need that part. This may not be the answer that you want, but it is what it is.
roirraW "edor" ehT said:
You HAVE to be rooted to change: recovery, kernel, hboot, ROM, and radio. The only exceptions are official updates, whether they be OTA or running a RUU update from Windows with the phone connected.
Root access effectively means being able to change things you're not normally allowed to change.
If you want a custom recovery on your phone, you're going to have to root it. To be technically fully rooted, you would probably have to change your hboot (referred to as S=OFF), too, but it doesn't sound like you need that part. This may not be the answer that you want, but it is what it is.
Click to expand...
Click to collapse
Okay, i will try one of those other root methods then. Do any of them install a custom recovery as part of the process like the universal one click root does?
Helgaiden said:
Okay, i will try one of those other root methods then. Do any of them install a custom recovery as part of the process like the universal one click root does?
Click to expand...
Click to collapse
I'm sure they all probably do, but I'm sure they say definitively in their threads, too. Everyone who roots wants to install a custom recovery so that they can flash rooted ROMs. Most everyone, anyway. Only those who just want the stock ROM but rooted wouldn't care about the recovery, but those are a minority.
Alright cool. Im gonna do the last method from Scary Allen's post. Just a question though..
i hook up the phone to the PC then click install_root.bat. That should do what i want, however in what mode should the phone be in when i have it plugged in? Powered on like normal, in the stock hboot/recovery mode...??
Helgaiden said:
Alright cool. Im gonna do the last method from Scary Allen's post. Just a question though..
i hook up the phone to the PC then click install_root.bat. That should do what i want, however in what mode should the phone be in when i have it plugged in? Powered on like normal, in the stock hboot/recovery mode...??
Click to expand...
Click to collapse
You should keep questions about various methods of doing things in the original thread. If it doesn't say in the thread about what mode it should be in, then you'll have to ask GrdLock. If it doesn't specify then maybe it doesn't matter what mode it's in. The only thing it specifies is:
MAKE SURE YOUR SDCARD IS NOT MOUNTED TO YOUR COMPUTER OR THIS WON'T WORK!!!!
Click to expand...
Click to collapse
roirraW "edor" ehT said:
You should keep questions about various methods of doing things in the original thread. If it doesn't say in the thread about what mode it should be in, then you'll have to ask GrdLock. If it doesn't specify then maybe it doesn't matter what mode it's in. The only thing it specifies is:
Click to expand...
Click to collapse
yeah i got that much out of it. Okay, thanks for your help.
The jcase "One Click" .apk does not work on 1.5, as you discovered.
Note that the root exploit method that One Click employs does work on 1.5 - but unfortunately the One Click app itself only runs on 2.1.
The Universal Eris Root for Dummies! method will work on both 1.5 and 2.1; it uses the same (wag3slav3) rooting exploit, but does not require the 2.1 OS to be running in order to work correctly. All it does to your phone is to install the Amon_RA custom recovery - exactly what you are looking for.
This method is the same one referenced by scary alien in his post mentioned above - the second URL in his post.
I've said this before, but I'll say it again: when you say "rooted", it means different things to different people. The most general definition is that you have "installed something on your phone which gives you privileges to alter some or all of the phone software which the device manufacturer did not intend".
So - you can have an engineering bootloader on a phone, but a completely stock OS... and that would be a "rooted" phone. Same deal for a set of root tools installed in the OS, but a S-ON bootloader and a stock recovery partition. Or a stock bootloader, a stock OS, but a custom recovery - again, that is also a "rooted" phone. In all three cases, you now have the means to alter whatever you want on the phone. That's all that "rooted" really means; it doesn't necessarily mean that the OS has been kanged up.
bftb0
ahh confirmation it doesnt work on 1.5, nice haha. Well thanks. Ill look into the Dummies root method but right now im leaning toward's GRDLOCK's method. At least i know i have good valid options though, thanks!
OK, I bought this off ebay back in august of last year and it has been amazing phone running on boost mobile flawless... but why I am here today is I had a friend ask me to use my phone and there has always been a bugging alert to update my phone but I was told to never update the phone just the apps. Well my friend seen the alert and it downloaded the update and installed it without me knowing but the problem is I no longer have root access and my setcpu app lost its ability to control my phone so now my phone is dieing in like half the time it used to last for... I need help getting it all back. The phone still works on everything but root access and my data connection seems much slower now.
whenever you update phone you lose root that's why peeps upload n share so you can flash and so, pretty sure you need to root again.
THISIS50 if its hot its here
storxtdi said:
OK, I bought this off ebay back in august of last year and it has been amazing phone running on boost mobile flawless... but why I am here today is I had a friend ask me to use my phone and there has always been a bugging alert to update my phone but I was told to never update the phone just the apps. Well my friend seen the alert and it downloaded the update and installed it without me knowing but the problem is I no longer have root access and my setcpu app lost its ability to control my phone so now my phone is dieing in like half the time it used to last for... I need help getting it all back. The phone still works on everything but root access and my data connection seems much slower now.
Click to expand...
Click to collapse
you'll have to regain root access. the easiest method is probably to flash the superuser.zip file through the custom recovery.
if you don't have a custom recovery, one easy method to flash, given you have the fastboot binary loaded on a computer is: fastboot flash recovery c:\custom-recovery.img
the superuser.zip can be found in a few places. goo-inside.me should have a mirror copy of it.
best of luck!
can u possibly go into more details on how I can do the custom root flashing. I never flashed this phone it came this way when i purchasedd it. I have played with rooting before on a previous phone but its been a while and i am not on top of current technology on rooting and flashing
joeykrim said:
you'll have to regain root access. the easiest method is probably to flash the superuser.zip file through the custom recovery.
if you don't have a custom recovery, one easy method to flash, given you have the fastboot binary loaded on a computer is: fastboot flash recovery c:\custom-recovery.img
the superuser.zip can be found in a few places. goo-inside.me should have a mirror copy of it.
best of luck!
Click to expand...
Click to collapse
storxtdi said:
can u possibly go into more details on how I can do the custom root flashing. I never flashed this phone it came this way when i purchasedd it. I have played with rooting before on a previous phone but its been a while and i am not on top of current technology on rooting and flashing
Click to expand...
Click to collapse
sure. you didn't provide any questions around the procedures i previously provided, so i'm not sure where exactly to elaborate details.
once you've unlocked the bootloader, you'll want to load a custom recovery. the custom recovery runs as root in recovery mode and therefore is an easy route to adding root access for the normal android mode.
to flash the custom recovery use this command: fastboot flash recovery c:\recovery.img
to boot into the recovery, adb reboot recovery or hold vol down + pwr and select recovery from the bootloader menu.
once in the custom recovery, select the superuser.zip file to flash. the superuser.zip file can be obtained from goo-inside.me/superuser and should be stored on the /sdcard in order to load from the custom recovery.
best of luck!
Ok I recently got a tf201. I have finally decided 2 go for it and trying 2 get a custom rom.
Untill now (using a SGS) I needed 2 root the phone then get a custom kernel then apply the rom.
How is the procedure for a prime? I tried 2 root but shortly found out that i had the .21 update, Im guesing I can downgrade not sure.
does "unlock" = root?
can some1 clarify the process tree to get to a new rom?
http://transformerprimeroot.com/tra...ow-to-unlock-bootloader-on-transformer-prime/ <--- how hard is it 2 succeed this without bricking it?
b3ava said:
Ok I recently got a tf201. I have finally decided 2 go for it and trying 2 get a custom rom.
Untill now (using a SGS) I needed 2 root the phone then get a custom kernel then apply the rom.
How is the procedure for a prime? I tried 2 root but shortly found out that i had the .21 update, Im guesing I can downgrade not sure.
does "unlock" = root?
If any1 can redirect me 2 the appropriate topics I can never spot out what I want :/ and can some1 clarify the process tree to get to a new rom?
Click to expand...
Click to collapse
You will have to unlock via the asus unlock tool (you can just google that and get it directly off of the Asus website). Then you will have to use Fastboot to flash CWM onto your device. From there the usual, back up the stock rom, and install any custom rom of your liking.
omac_ranger said:
You will have to unlock via the asus unlock tool (you can just google that and get it directly off of the Asus website). Then you will have to use Fastboot to flash CWM onto your device. From there the usual, back up the stock rom, and install any custom rom of your liking.
Click to expand...
Click to collapse
unlock tool from asus website. ok but can u explain 1 thing 2 me? if its on asus website why does it void your warranty? and root and unlock are different?
If you are planning to flash a custom rom, check out androwookie v1.2 its good.
Unlock gives you the ability to install a custom recovery e.g. cwm, you then use this to flash a pre-rooted rom. Root just means having access to the root directory. It enables access to features and functions that are normally made inaccessible.
Using the fastboot method is pretty simple and guides can be found easily. I just did it yesterday after having previously only rooted and installed cm 7+9 on my sgs2.
Thats my understanding anyway
b3ava said:
unlock tool from asus website. ok but can u explain 1 thing 2 me? if its on asus website why does it void your warranty? and root and unlock are different?
Click to expand...
Click to collapse
It's just one of their stipulations. Most manufacturers are like that in regards to using their unlock tools.
Root = enhanced permissions to run apps like Titanium Backup, Root Explorer (if you're modifying anything in the/System directory), stuff like that.
Unlock = your bootloader is "unlocked," you can now put ClockworkMod recovery on your device, flash ROMs and kernels. These things can't be done while only being rooted.
I hope I cleared it up for you a bit
Sent from my ADR6425LVW using XDA Premium.
SteveG12543 said:
It's just one of their stipulations. Most
Root = enhanced permissions to run apps like Titanium Backup, Root Explorer (if you're modifying anything in the/System directory), stuff like that.
Unlock = your bootloader is "unlocked," you can now put ClockworkMod recovery on your device, flash ROMs and kernels. These things can't be done while only being rooted.
Sent from my ADR6425LVW using XDA Premium.
Click to expand...
Click to collapse
so with unlocking the device I wont have root privs? so things like you said titanium backup wont work?
1 more thing. is unlocking considered harder? and does any1 have a video of unlocking so that I know what I can expect b4 freaking out?
b3ava said:
so with unlocking the device I wont have root privs? so things like you said titanium backup wont work?
1 more thing. is unlocking considered harder? and does any1 have a video of unlocking so that I know what I can expect b4 freaking out?
Click to expand...
Click to collapse
Unlocking doesn't instantly get you root, it just makes rooting a lot easier to do. Like they said, unlock, put CWM on it, flash a rooted ROM and bam, rooted. But correct, apps like Titanium won't work if you're only unlocked, you would need root.
As far as I know, unlocking just requires downloading the .apk from Asus' site, installing it and going through the prompts. It doesn't sound hard at all. I personally don't know the ins and outs of it, as I never unlocked my Prime, but that's all it really sounded like. Sounds pretty simple. I believe there's some videos on it on YouTube though.
Sent from my ADR6425LVW using XDA Premium.
SteveG12543 said:
Unlocking doesn't instantly get you root, it just makes rooting a lot easier to do. Like they said, unlock, put CWM on it, flash a rooted ROM and bam, rooted. But correct, apps like Titanium won't work if you're only unlocked, you would need root.
As far as I know, unlocking just requires downloading the .apk from Asus' site, installing it and going through the prompts. It doesn't sound hard at all. I personally don't know the ins and outs of it, as I never unlocked my Prime, but that's all it really sounded like. Sounds pretty simple. I believe there's some videos on it on YouTube though.
Sent from my ADR6425LVW using XDA Premium.
Click to expand...
Click to collapse
buddy thanx for all of this info was just wondering if the link i posted is the process for this unlocking? as every1 is describing? and where do i get that CWM?
b3ava said:
buddy thanx for all of this info was just wondering if the link i posted is the process for this unlocking? as every1 is describing? and where do i get that CWM?
Click to expand...
Click to collapse
No problem! And yep, the link in the first post is a great looking guide for unlocking. Nice and easy, step by step. And after you have unlocked, just download ROM Manager from the market and you can flash CWM through the app itself. From my understanding that's the easiest way to do it, at least. Sorry it's been a few days since I responded, I haven't really been checking out the Q&A section lately
Sent from my Transformer Prime TF201 using XDA Premium HD app.
Bootloader unlock:
Custom Kernel possible
Official updates impossible
Waranty impacted
CWM backups possible
Need to use community ROMs in future
improved but not great chance of recovering from bad ROM flash (really needs NVFLASH)
Rooted:
Now possible with firmwares up to .28
Permits write access to /system partition
Makes it easier to brick and block OTA updates
Should be reversable
Allows most tweaks to be applied except for replacing kernel (which is a prerequisite for some kernels)
Going to make this a FAQ I think...
This guide will enable you to easily root your phone in 6 steps. I've taken out the mystery and complications.
1) Go to HTC Dev site and manually unlock your bootloader. Select "register" and create your account.
1a) After you are registered select "all other supported models" in the pull down box
1b) Click "begin unlock bootloader". it will ask "are you sure" yes of course you are. acknowledge legal terms. then continue.
1c) Ignore the battery pull instructions as we can't pull the battery. hold down the power key and the volume down key until the bottom buttons stop flashing and your phone shuts off (don't worry if you take a screenshot. It happens all the time). then release ONLY THE POWER BUTTON. Keep holding the volume down key until the bootloader screen shows up.
1d) Follow "step 3" and the rest of the instructions as listed on the HTC site to unlock your bootloader manually.
2) Install android ADB/SDK on your pc. This video shows how to do it nicely:
2a) ****NEW UPDATED 03/05/13*** Alternatively if you DON'T want to install ADB/SDK you can just download the NON-FLASHABLE platform-tools.zip file located in my dropbox folder here.
Just extract this folder to your desktop using WINZIP or whatever archive tool you use and proceed to step 3.
3) Open a command line in your "platform-tools" folder by holding shift+right click anywhere within the folder and selecting the menu option "open a command window here". Then click here to install TWRP using fastboot. Follow the "Download - Fastboot Method:" instructions.
3a) If your phone isn't detected by windows please install the proper USB drivers for your operating system. Go here for 32bit. Go here for 64 bit.
4) Flash SuperSu and Busybox on your device:
4a) Click here and download the latest version of SuperSu. save it to your sdcard.
4b) Go to my dropbox and download Busybox 1.20.2 and save it to your sdcard.
5) Reboot into recovery (via the bootloader selection)
6) Flash the SuperSu zip and the Busybox zip listed in 4a and 4b
That's it!
"So now what?" you may be asking.
You are now free to flash ROMs that support s-on.
Two are my favorites are
(1) Stock with Goodies. (my personal favorite and the one I use today). This is a great ROM for beginners and people who prefer a slimmed down ROM (minus the bloat) and lots of free memory!
(2) Viper4G. This is a ROM for more experienced users and offers TONS of customization.
You can also run apps from Google play that required ROOT access!
If you're feeling slightly adventurous you can flash a custom kernel (which will allow you to overclock your phone). Two of the kernels I use are:
(1) ElementalX by flar2. Click here to take a trip over there. This one is especially important to flash as it seems HTC was up to shenanigans with the latest HBoot (2.09).
If you're unlucky enough to have HBoot 2.09 they have RESTRICTED access to your /system partition. What does this mean to you? It means that if any app writes to your /system partition (ROOTED or not) the phone will "panic" and reboot. Shady behavior if you ask me. The solution? Flash this kernel! it will give you write access so that everything works properly.
(2) The Arc-Reactor kernel! This one is for people that are s-off (see below for an explanation of s-off) only! It's the kernel I currently use and is the fastest kernel out there! Highly recommended if you decide to go s-off!!!
If and when you're feeling more adventurous you can go "s-off" (security off) which removes any security limitations of your phone. It makes flashing ROMs and updating firmware a lot easier. You can find out about s-off by taking a trip over to the DirtyRacun thread here. I will NOT walk you through this process. They will totally help you on their IRC channel. Just read post # 1 in that thread.
There's also a new method of s-off which literally takes 2 minutes. It's called facepalm and is located here But is NOT for the feint of heart, bad typers, nor people that cannot follow instructions! Why? One typo here and your phone is a brick. A paperweight. Useless. Well...you can recover...but that's not the purpose of this thread. If you DO brick your phone PM me. I'll help you out.
I take NO credit for any of this. It's all out there to learn I just put it all together. In one spot. Any questions feel free to PM me.
If I helped you out hit the THANKS button...or buy me a beer! Either way lol!
Tested and works with 3.16.651.3 (even if you took the OTA and have hboot 2.09 and are s-on)
Did you use SuperSU or Superuser for root access? Either way could you please update the binary to see if it succeeds or if you get an instant reboot?
lancemoreland said:
Did you use SuperSU or Superuser for root access? Either way could you please update the binary to see if it succeeds or if you get an instant reboot?
Click to expand...
Click to collapse
Everyone that is using supersu is experiencing that issue. The program itself will grant superuser access to your device. You don't need to open it. When you try and open it it will attempt to update the binary and then reboot the phone. You can ALWAYS reflash a new version of supersu when they update it.
To be clear: I'm up and running on my phone right now with superuser access. I'm fine unless I try to open the supersu program itself. Then I experience this issue you pointed out.
rawintellect said:
Everyone that is using supersu is experiencing that issue. The program itself will grant superuser access to your device. You don't need to open it. When you try and open it it will attempt to update the binary and then reboot the phone. You can ALWAYS reflash a new version of supersu when they update it.
To be clear: I'm up and running on my phone right now with superuser access. I'm fine unless I try to open the supersu program itself. Then I experience this issue you pointed out.
Click to expand...
Click to collapse
I agree. I am up and running also but the new hboot locks the system partition and any app that tries to write to it will cause a reboot. Ad-free is another example.
lancemoreland said:
I agree. I am up and running also but the new hboot locks the system partition and any app that tries to write to it will cause a reboot. Ad-free is another example.
Click to expand...
Click to collapse
Indeed this is a well documented problem but really not what this thread is about. Perhaps you can check out THIS thread where they are discussing this issue at length and hopefully they will come up with a solution for it?
http://forum.xda-developers.com/showthread.php?t=1538053
It also looks as though chainfire (the OP) is working on a fix if I read the last few posts correctly. and when he gets it I will update this post with it.
rawintellect said:
It also looks as though chainfire (the OP) is working on a fix if I read the last few posts correctly. and when he gets it I will update this post with it.
Click to expand...
Click to collapse
Yes I am participating in that thread. Chainfire is looking for a work around for his specific app, other apps that write to the system partition will no longer work. The point is that with Hboot 2.09 there are limitations and we will not enjoy full root as we have before when we were s-on.
Updated with an alternative superuser program.
SuperSU would ask to update binary and then just reboot. This fixed my problem for being able to access/deny and turn off messages. However it did not uninstall superSU will this cause a conflict having them both?
Edit: Okay I am dumb, I had to uninstall superSU first. Then I reflashed superuser to be able to have root privileges for my apps. When I just reflashed superuser hoping it would get ride of and superuser and keep root it did not.
Thanks it worked!
Help with rooting please.
So my phone was updated OTA without being rooted to 3.15.651.16 but now it is frozen. The touch screen will work temporarily upon a simulated battery pull and then freeze again only for me to simpull again and then it freeze again. I've gone into the bootloader and factory reset and wiped the cache but it's still messed up. So I think that maybe it's the software not installing correctly or something because this only started happening immediately after I download the new update.
I'm thinking about rooting my phone and even though I'm a pretty techy person this is new to me. I'm hoping that if I root my phone I can put it back to the stock software before the update and then just re-update OTA stock to the new update. I think that may fix it. Do y'all have any input it would be greatly appreciated as I have been dealing with this useless phone for over a week now.
Thanks.
MrSteez said:
So my phone was updated OTA without being rooted to 3.15.651.16 but now it is frozen. The touch screen will work temporarily upon a simulated battery pull and then freeze again only for me to simpull again and then it freeze again. I've gone into the bootloader and factory reset and wiped the cache but it's still messed up. So I think that maybe it's the software not installing correctly or something because this only started happening immediately after I download the new update.
I'm thinking about rooting my phone and even though I'm a pretty techy person this is new to me. I'm hoping that if I root my phone I can put it back to the stock software before the update and then just re-update OTA stock to the new update. I think that may fix it. Do y'all have any input it would be greatly appreciated as I have been dealing with this useless phone for over a week now.
Thanks.
Click to expand...
Click to collapse
Well my suggestion is to go ahead and unlock your phone, flash a recovery and root it using my instructions. Then if you want BONE stock flash the odexed version of Jellybean that Viperboy has in his thread located here: http://forum.xda-developers.com/showthread.php?t=2045929
Why am I suggesting you do this? Because the OTA was very bugged. HTC is VERY slow with fixes. Developers can fix errors in the base errors usually faster than HTC. And most importantly when you are feeling like a change you can flash a custom zip at any time. The ONLY downside to unlocking and rooting is that you void your warranty with HTC, but NOT with sprint! Sprint will still honor a replacement phone when you RELOCK your phone and use the RUU (which isn't available yet but will be) to bring it back to stock. Your bootloader will say *RELOCKED* which lets them know you unlocked it but again they will honor a replacement.
Updated thread with instructions on manually uninstalling supersu first before installing superuser 3.2
Thank you very much!
rawintellect said:
Well my suggestion is to go ahead and unlock your phone, flash a recovery and root it using my instructions. Then if you want BONE stock flash the odexed version of Jellybean that Viperboy has in his thread located here: http://forum.xda-developers.com/showthread.php?t=2045929
Why am I suggesting you do this? Because the OTA was very bugged. HTC is VERY slow with fixes. Developers can fix errors in the base errors usually faster than HTC. And most importantly when you are feeling like a change you can flash a custom zip at any time. The ONLY downside to unlocking and rooting is that you void your warranty with HTC, but NOT with sprint! Sprint will still honor a replacement phone when you RELOCK your phone and use the RUU (which isn't available yet but will be) to bring it back to stock. Your bootloader will say *RELOCKED* which lets them know you unlocked it but again they will honor a replacement.
Click to expand...
Click to collapse
Thanks I seriously appreciate it. I'm at work right now (I actually work at Sprint by the way which is why I'm not worried about having the phone replaced my tech will do it regardless) so I'm probably gonna look over your instructions carefully and then do this tomorrow. I'll let you know what happens I'm really hoping this will do it. It has to be some kind of serious installation bug in the new update because I never had this problem until literally minutes after updating.
And then after the completely stock RUU comes out (with no root or anything special) I can go back to completely locked and stock again? That's what I think I'd prefer but who knows I'm a Android and tech fanboy maybe I'll prefer the root.
MrSteez said:
Thanks I seriously appreciate it. I'm at work right now (I actually work at Sprint by the way which is why I'm not worried about having the phone replaced my tech will do it regardless) so I'm probably gonna look over your instructions carefully and then do this tomorrow. I'll let you know what happens I'm really hoping this will do it. It has to be some kind of serious installation bug in the new update because I never had this problem until literally minutes after updating.
And then after the completely stock RUU comes out (with no root or anything special) I can go back to completely locked and stock again? That's what I think I'd prefer but who knows I'm a Android and tech fanboy maybe I'll prefer the root.
Click to expand...
Click to collapse
yes. going back to stock is as simple as this:
(1) Boot your phone into the bootloader. make sure fastboot is selected. if you have the drivers installed correctly your phone will read "fastboot usb"
(2) if you followed my instructions on rooting you have ADB/SDK installed. so issue the command to relock your phone. type: fastboot oem lock
(3) run the RUU for 3.15.651.16. Done. Your bootloader will say *relocked* but it will be 100% stock.
Uh oh
I think i messed up. I did not see busy box installed and SuperSU is not updating.
The file listed in step 6 contains busybox. It also contains supersu. You want to flash the superuser file after flashing the file in step 6. It will overlay supersu with superuser 3.2. There is no need to update superuser 3.2 once you flashed it. It is the latest release.
Sent from my EVO using xda app-developers app
do i need to just flash the new superuser and it will fix the binary problema nd the titanium problem?
mobilecj said:
do i need to just flash the new superuser and it will fix the binary problema nd the titanium problem?
Click to expand...
Click to collapse
I replied to your email. But check my first post on the subject of superuser and how to uninstall supersu. if you need to that is. I tested this myself and it did uninstall supersu for me by just flashing superuser 3.2. Some people have reported this doesn't work for them.
okay sorry just got both i am going to try it now.. Its all knew to me it seemed like the information was explaining a dual process and i only had acquired one problem.. will post back in a few!
Hey XDA, can we talk? cause im about to cry man tears.
First off you are much better at android then I am, this isn't me trying to sound humble, I suck and the threat of bricking my toys scares me.
Today I found a way to get root access without unlocking my bootloader and I was thrilled, it was easy and it worked! I had root access and then decided I was going to try to install CyanogenMod 10 (latest nightly) and so I installed ROM Manager and downloaded CyanogenMod, when I tried to boot to recovery mode (hold down volume and power, then up volume) I would get the dead android with an exclamation point, every time.
So I decided to unlock my bootloader, I went searching and came across the ASUS official bootloader unlocker and it said the unlocker was for ICS and I have already upgraded the ASUS rom to jellybean, I decided to try the unlock device app anyway and now when I restart the words "this device is unlocked" show in the top left corner, I thought that meant the bootloader is unlocked but when I restart into recovery mode I still get the dead android.
I cant find any information anywhere about how to unlock an ASUS jellybean bootloader and I am only guessing that why I keep getting the dead android.
Anyway, if you can help thats awesome, I am usually the kind of guy that can read and find the answers but **** me if I cant find them anywhere, I was never good at the world of bootloaders, whether PC or Android and I am hoping to find a hand and learn something more here
Thanks
I know its my first time here to post but I have read loads of stuff off this site.
78 people read this already, one of you must be able to point my dumbass in the right direction?
bueller, bueller ...:crying:
Once I get an idea of what I am doing wrong and why I keep getting the dead android, I think I will try to install AndroWook 2.2
ArghMonkey said:
Once I get an idea of what I am doing wrong and why I keep getting the dead android, I think I will try to install AndroWook 2.2
Click to expand...
Click to collapse
You are unlocked but you do not have a custom recovery installed yet.
Go to the TWRP thread and follow the instructions for installing TWRP for the JB bootloader. Do not install CWM.
Make sure you get the correct TWRP for the JB bootloader.
flumpster said:
You are unlocked but you do not have a custom recovery installed yet.
Go to the TWRP thread and follow the instructions for installing TWRP for the JB bootloader. Do not install CWM.
Make sure you get the correct TWRP for the JB bootloader.
Click to expand...
Click to collapse
Sweet, im on it right now
Wow, there are TWRP threads everywhere, several downloads, I even did a search within the transformer prime subthread and cant find one version mentioned for the JB bootloader.
Ill keep looking ...
Lost again.
So I found this
http://teamw.in/project/twrp2/93
But then I read this
"We STRONGLY recommend users enable and backup your device before flashing custom roms/recoveries with nvflash courtesy of AndroidRoot.mobi (this also makes your device essentially "brick-proof") - you need to be on the ICS bootloader to do this, if you have taken the JB OTA from Asus you cannot get nvflash access.
If you have updated to the JB OTA bootloader then you must use the -JB version of the recovery, flashing the non -JB version could potentially permanently brick your device (unless you have nvflash as noted above)."
And have no idea which way I should proceed, should I downgrade? no idea how to do that, I think I read somewhere if I have the official formware updates from ASUS that I can stick it on my microSD and the asus recovery will see it and install the downgrade.
Or should I just go for it, that bricking is a risk but low?
I know I am running jellybean but I still dont have a clue exactly what bootloader I have, I assume there are several versions under jellybean but I cant find any guides to tell me exactly where to find what bootloader version I have.
1: Can anyone tell me how I find exactly which bootloader I am running? I have JB installed (4.1.1)
2: So what version of TWRP do I need to download?
3: How would I install TWRP?
and yes, I am unlocked and rooted, help!
Download TWRP 2.5.0.0 for JB blob from here: http://teamw.in/project/twrp2/93
Rename to twrp.blob
Use command prompt on your computer to flash recovery to tablet using this command: fastboot -i 0x0b05 flash recovery twrp.blob
....................
Follow this thread: http://forum.xda-developers.com/showthread.php?t=2038464
---------- Post added at 12:37 PM ---------- Previous post was at 12:35 PM ----------
ArghMonkey said:
Lost again.
So I found this
http://teamw.in/project/twrp2/93
But then I read this
"We STRONGLY recommend users enable and backup your device before flashing custom roms/recoveries with nvflash courtesy of AndroidRoot.mobi (this also makes your device essentially "brick-proof") - you need to be on the ICS bootloader to do this, if you have taken the JB OTA from Asus you cannot get nvflash access.
If you have updated to the JB OTA bootloader then you must use the -JB version of the recovery, flashing the non -JB version could potentially permanently brick your device (unless you have nvflash as noted above)."
And have no idea which way I should proceed, should I downgrade? no idea how to do that, I think I read somewhere if I have the official formware updates from ASUS that I can stick it on my microSD and the asus recovery will see it and install the downgrade.
Or should I just go for it, that bricking is a risk but low?
I know I am running jellybean but I still dont have a clue exactly what bootloader I have, I assume there are several versions under jellybean but I cant find any guides to tell me exactly where to find what bootloader version I have.
Click to expand...
Click to collapse
You can't use NVFlash because you are on the JB bootloader. You can't downgrade to ICS.
Great links!
Thanks for your help, I will report back once I try this
ArghMonkey said:
Great links!
Thanks for your help, I will report back once I try this
Click to expand...
Click to collapse
Any update? I've had my Prime for over a year. Rooted tonight, looking to unlock the bootloader and flash a custom ROM. Interested to hear the results.
Flash TWRP:
Once unlocked, power it off. Once off power it on by holding BOTH volume down and power buttons. When you see the menu appear the first option is RCK. press Volume Down to change the cursor to be over the USB logo (two presses of the button) and press volume up. This puts your device in fastboot mode
Back on your computer you should hopefully see a successfull driver install for fastboot. I got all my drivers from downloading and installing the Android SDK so you may or may not need to do that. Android SDK
If all is prepared and you are in fastboot with drivers loaded:
On your computer hold shift and right click on the folder where fastboot and the twrp.blob file are and you will see a context menu. Click on "Open Command Window Here" (Vista + only or if you installed powertools on 2000/XP)
Click to expand...
Click to collapse
Ok, so I followed your link, I downloaded the Android SDK and when I opened it I see a million things, the Google USB Driver was highlighted so I installed it, are there other drivers im supposed to install before I go to the next step?!
Lavman72 said:
Any update? I've had my Prime for over a year. Rooted tonight, looking to unlock the bootloader and flash a custom ROM. Interested to hear the results.
Click to expand...
Click to collapse
Working on it right now, flashed twrp over, prime is starting up right now *fingers crossed*
and yes! it booted to stock, now to transfer over supersu ...
Awesome TWRP is alive and in charge, now to flash with Androwook!
It aint over but its getting close
ArghMonkey said:
Awesome TWRP is alive and in charge, now to flash with Androwook!
It aint over but its getting close
Click to expand...
Click to collapse
That's great news. Did you follow the steps on this thread?
http://forum.xda-developers.com/showthread.php?t=2038464
Any suggestions or pointers? I've rooted/installed custom roms on many phones, but this one seems to be the most complicated/risky.
Lavman72 said:
That's great news. Did you follow the steps on this thread?
http://forum.xda-developers.com/showthread.php?t=2038464
Any suggestions or pointers? I've rooted/installed custom roms on many phones, but this one seems to be the most complicated/risky.
Click to expand...
Click to collapse
Yup, thats how i did it.
The biggest obstacle is unclear instructions or instructions that assume the reader is not a noob *L*
ArghMonkey said:
Yup, thats how i did it.
The biggest obstacle is unclear instructions or instructions that assume the reader is not a noob *L*
Click to expand...
Click to collapse
Excellent. I'll probably give it a go in the next couple of days. Strange that the Unlock tool works. I've read other posts that state if you are already on JB (which I am) the unlook tool won't work.
Lavman72 said:
Excellent. I'll probably give it a go in the next couple of days. Strange that the Unlock tool works. I've read other posts that state if you are already on JB (which I am) the unlook tool won't work.
Click to expand...
Click to collapse
Everything is totally installed and working great now, Whew, what a relief!
Thanks folks!
ArghMonkey said:
Everything is totally installed and working great now, Whew, what a relief!
Thanks folks!
Click to expand...
Click to collapse
Rooted: Check
Unlocked bootloader: Check
Tired though, and it's late. So I'm going to hold off on the final steps.