Tried everything but still can't UNROOT asus transformer prime - Asus Eee Pad Transformer Prime

Ok my friend had rooted my Asus Transformer Prime TF201 and now have something called CyanogenMod9 on it. Well I don't like it rooted and wanted it off and back to stock. But when I tried unrooting it, nothing happen. I can't find my back ups files. I believe I try almost every method of unrooting it but no luck. I don't know if I'm doing something wrong or what but please help Can anyone suggest any ideas, I just want my Transformer Primer TF201 back to stock and the stock apps as if it was taken brand new out of the box. Please help and thank you.

If you upgrade to craiggomez jb. But why. I lost root and i cant stand it. I would honestly just leave. Obviously you dont know what root can do for you and what it is. Keep inmind if you do this you will lose root and also lose you custom recovery. You cant even except updates on jb from asus or you will brick your device, Just go to another rom and dont use rooted apps. If you continue on and unroot you are pretty stupid. Please dont do it you will regret it in the end

tebiren said:
Ok my friend had rooted my Asus Transformer Prime TF201 and now have something called CyanogenMod9 on it. Well I don't like it rooted and wanted it off and back to stock. But when I tried unrooting it, nothing happen. I can't find my back ups files. I believe I try almost every method of unrooting it but no luck. I don't know if I'm doing something wrong or what but please help Can anyone suggest any ideas, I just want my Transformer Primer TF201 back to stock and the stock apps as if it was taken brand new out of the box. Please help and thank you.
Click to expand...
Click to collapse
There are two different concepts to be aware of: 1) rooting and 2) unlocking
Rooting: Rooting is basically just taking admin access to the ROM to allow you to do things like uninstall or freeze apps that were built into the ROM that you don't want, or make other changes that the system will not normally let you do. If you are rooted, and on the stock ROM it is possible to go back to an un-rooted state.
Unlocking: Unlocking is basically taking control over the boot loader to allow you to install custom ROM's i.e. ROM's (complete operating systems) that didn't come from Asus. Once you are unlocked, there is no way back to a locked state.
Cyanogen Mod 9 is a custom ROM. That means you must be unlocked and there is no way to re-lock the device. However it does mean that if you don't like Cyanogen Mod 9, you can try one of many other custom ROM's. Read about them in the developer's section.

ratman6161 said:
There are two different concepts to be aware of: 1) rooting and 2) unlocking
Rooting: Rooting is basically just taking admin access to the ROM to allow you to do things like uninstall or freeze apps that were built into the ROM that you don't want, or make other changes that the system will not normally let you do. If you are rooted, and on the stock ROM it is possible to go back to an un-rooted state.
Unlocking: Unlocking is basically taking control over the boot loader to allow you to install custom ROM's i.e. ROM's (complete operating systems) that didn't come from Asus. Once you are unlocked, there is no way back to a locked state.
Cyanogen Mod 9 is a custom ROM. That means you must be unlocked and there is no way to re-lock the device. However it does mean that if you don't like Cyanogen Mod 9, you can try one of many other custom ROM's. Read about them in the developer's section.
Click to expand...
Click to collapse
Thank you very much,

Related

[Q] Downgrading, rooting a success... messed up afterwords?

Hey everyone,
Have Prime with .21 Firmware
Did/do NOT want unlocked bootloader, but I want the root.
Downgraded the Prime to the .15
Rooted it using the ViperMod
-Now this next part if it doesn't make sense I blame it on me being sick, and it being late here.-
So, it wasn't offering the OTA .21 update to me after this.
I read that wiping the cache was a step that I may have missed.
From my experience with tinkering with the old Galaxy S and rooting/throwing on custom roms I remembered that CWM is the way to go for this!
Puts on Rom Manager
Flashes CWM and then the new CWM Touch after that.
Tries to reboot into recovery mode so that I can do the wipe.
Doesn't work from manual hard reset, adb commands, or from the Rom Manager UI.
Now I just want to get rid of CWM and go back with stock recovery, and then just push the .21 blob on there instead.
Please tell me I didn't somehow unlock my bootloader... >_< I thought I would have had to agree to something to do that.
If I didn't, how do I pull the CWM off, but keep the root and the bootloader UNLOCKED.
Yes, I have been hunting through the Forum, and through Google. I'm finding things that are close, but just far off enough that I'm not sure the answers are applying to this situation.
(By the way, if I did something completely stupid in my thought process let me know... but I'm still going to bank on being sick and tired )
You cant install cwm unless you unlocked your bootloader... So im not sure how you flashed it with rom manager. Are you sure you didnt select the option to unlock and install cwm in viperMOD?
Positive that I didn't. Mainly because it mentioned the unlock tool in the same line as CWM.
Everything that I did after following Wolf's directions was through Rom Manager (aka the CWM install and ROM backup).
another advice: don't think "cwm" when you want to install asus blobs
still, everything i read so far says that to install cwm you need unlocked bootloader.
Sent from my Transformer Prime TF201
bk201doesntexist said:
another advice: don't think "cwm" when you want to install asus blobs
still, everything i read so far says that to install cwm you need unlocked bootloader.
Sent from my Transformer Prime TF201
Click to expand...
Click to collapse
I don't think that I was "thinking" properly >_<. But I will make sure and keep that in mind.
That's what I've read too. What's strange is that, unless some program did it without telling me that it did it, I avoided anything that looked like it said "unlock".
So, just did some more Google searching and came across this link: http://forum.xda-developers.com/showthread.php?t=1575138
(tl;dr Don't need to unlock bootloader, just need to have root)
I know it's not a TF201 thread, but should the principles still apply (you actually have to read the thread to see what I mean).
Alright, after a little more reading, investigating on the prime, and putting a little more thought into it I think I've come to believe that (even though OM Manager thinks it is) CWM isn't actually installed on the Prime. I'm thinking that when ROM Manager supposedly flashed it, it only installed a random file or two that it could. the ONLY CWM folders I could find in ANY directory on my prime was in the sdcard folder and the clockworkmod folder.
I just deleted that, restarted, and it isn't broken... yet.

Just Need to Clarify a Few Things

Hey guys,
Bit of an Android noob here but I am quite tech savvy. I am gonna root my Prime and install Androwook on it but first I would just like to go over some things. I have had a look around at a lot of guides and that and have figured to do this I need to unlock the bootloader using ASUS' own app fro their support, then I need to install CWM on it through the unlocked bootloader and then I can backup and install new ROMS. But which point is the root, I can't seem to find a clear answer or is it a whole new step all together? And also could you please guide me if this is completely wrong because I am paranoid about my Prime and would hate to end up with it bricked. Sorry if this is sort of in the wrong area or a bit of a repeated question, just paranoid!
Thanks,
I saw your post completely randomly, but I think I have your answer. Rooting your device can be done at any point by either unlockroot.com or DoomLord's toolkit somewhere on the site. It has no effect on installing roms/unlocking bootloaders. It simply gives you more control over a device. I hope I understood your question and helped. Good luck
Sent from my Sony Xperia Neo using xda app-developers app
Ok, thanks, that clears a lot up. I will check that out. I didn't know it was that easy. Could I also ask, which part of the process risks the device been bricked?
mdemons12 said:
Ok, thanks, that clears a lot up. I will check that out. I didn't know it was that easy. Could I also ask, which part of the process risks the device been bricked?
Click to expand...
Click to collapse
Well unlocking the bootloader SHOULD be safe if yu're unlocking by offficial means. What can damage your device is flashing the wrong files. So be REALLY careful with what you flash on your device and always double-check the tutorials in the given thread
if i remember correctly, they said you need root was to install cwm onto your system
the rooting process is very easy anyways
http://forum.xda-developers.com/showthread.php?t=1706588
for the unlocking use the asus official one (This will void ALL warranties so if you brick your prime, well then GG)
and as above post says, most things should be very save so long as you follow to the dot.
when it says DO NOT POWER THE SYSTEM DOWN, just follow what it says and don't power things down, you should be fine
download things that are for you ONLY don't go to other threads trying to install iOS onto your prime (not that its possible.... that i know of)
just read it make sure you understand you won't brick anything~
Yes well I plan on putting the Androwook rom on which seems pretty darn stable. If ASUS comes out with a JB rom for the Prime and I was on the Androwook ROM, would it still be possible to update?
mdemons12 said:
Yes well I plan on putting the Androwook rom on which seems pretty darn stable. If ASUS comes out with a JB rom for the Prime and I was on the Androwook ROM, would it still be possible to update?
Click to expand...
Click to collapse
yes the devs will be able to put jelly bean on the prime if we get the official update :fingers-crossed:
mdemons12 said:
Yes well I plan on putting the Androwook rom on which seems pretty darn stable. If ASUS comes out with a JB rom for the Prime and I was on the Androwook ROM, would it still be possible to update?
Click to expand...
Click to collapse
It is worth noting that you probably don't need to go through the root process if you are installing a custom ROM. Many (most?) custom roms grant super-user permissions by default.
well it does say in the requirements of Androwook that it requires a root.
one suggestion though, use TWRP as your recovery mode. quite handy...
mdemons12 said:
well it does say in the requirements of Androwook that it requires a root.
Click to expand...
Click to collapse
The reason you root your device is to gain superuser permissions. Most OEM versions of Android don't give you SU permissions because it is possible you could mess up your device by deleting systems files or changing hidden settings. However most custom ROMs give you superuser permissions by default.
After unlocking your Prime, I would recommend installing TWRP using the fastboot method, so that you don't need to install root first. Then you can backup your stock and flash AndroWook from TWRP. AndroWook is already rooted, so you won't need to worry about adding extra steps for root.
~Azrael's Kiss~
OK, thanks for the replies. I think I will wait a little and test the device for any major problems before I root and unlock because I don't want to have to send it back for an RMA.
So from what I have read around I need to:
1. Unlock bootloader using the ASUS tool
2. Install CWM or similar and backup my current ROM although I have seen trouble with installing 2.1 with CWM so I think I might use TWRP
3. Install Androwook 2.1 and from what I have read skip some things like bravia engine, sd wipe sqlite vacuum and add sio io scheduler.
There seem to be so many options with the installer which makes it a bit confusing but first up I think I will use the 1.6GHz Kernel or something and keep it mainly stock.

[Q] Downgrading from JB to ICS

Hi Guys,
I've skimmed around this forum for the last few days and gone through some of the posts regarding getting JB on my TF201 and after a couple of days using it and being really unsatisfied with it I've decided I really want to downgrade back to ICS.
I've searched but the scenarios regarding downgrades don't really seem to match my own circumstances. My device isn't unlocked, was rooted through "DebugfsRoot" and then updated to JB using the guides from the forums.
I've attempted putting "WW_epad-user-9.4.2.28" on the root of my MicroSD card to use the "!" triangle method. JB does recognise this as an attempt to downgrade and warns me approriately about losing everything on the tablet which isn't an issue. The downgrade seems to proceed, Andy whirs away and various progress bars complete. Upon rebooting though there is no change to the device whatsoever and JB is still on there.
I've tried copying the blob from that zip onto the device itself and using Terminal Emulator to force the tablet to downgrade to that on the next reboot. The same process happens and there's no change to the tablet upon rebooting.
Has anyone tried this successfully yet? Or will I perhaps have to attempt unlocking the device to get a new ROM on there? I don't know if I'm overlooking something simple but any help would be greatly appreciated!
Lolatron said:
Hi Guys,
I've skimmed around this forum for the last few days and gone through some of the posts regarding getting JB on my TF201 and after a couple of days using it and being really unsatisfied with it I've decided I really want to downgrade back to ICS.
I've searched but the scenarios regarding downgrades don't really seem to match my own circumstances. My device isn't unlocked, was rooted through "DebugfsRoot" and then updated to JB using the guides from the forums.
I've attempted putting "WW_epad-user-9.4.2.28" on the root of my MicroSD card to use the "!" triangle method. JB does recognise this as an attempt to downgrade and warns me approriately about losing everything on the tablet which isn't an issue. The downgrade seems to proceed, Andy whirs away and various progress bars complete. Upon rebooting though there is no change to the device whatsoever and JB is still on there.
I've tried copying the blob from that zip onto the device itself and using Terminal Emulator to force the tablet to downgrade to that on the next reboot. The same process happens and there's no change to the tablet upon rebooting.
Has anyone tried this successfully yet? Or will I perhaps have to attempt unlocking the device to get a new ROM on there? I don't know if I'm overlooking something simple but any help would be greatly appreciated!
Click to expand...
Click to collapse
I've had the same experience and it's very frustrating. My devices is even unlocked and that doesn't help.
@skaforey
if your device is unlocked you should be able to change the recovery system and then use the new recovery to load any image you want onto the device.
@Lolatron
yeah, I've been reading and trying various things the last few days too, but it seems there is no way to downgrade from JB back to ICS with a locked device.
There are a few things I enjoy on JB (like the fixed IO problems of the dock that make the sdcard slot finally useable), but I'm really missing my root acess that got wiped with JB. I'll probably unlock it if we can't find a way to regain root in the next few weeks.
Root access wasn't an issue for me, even after numerous wipes and resets I've kept that and have carried on as normal.
For me it's sluggishness (after a factory reset) on the launcher, huge frame rate drops on games, my Chrome bookmarks no longer syncing and absolutely horrible touch screen keyboard response. Overall it's a huge step down from the previous update, it's just a poor user experience.
Sent from my GT-I9100 using xda app-developers app
dopef1sh said:
@skaforey
if your device is unlocked you should be able to change the recovery system and then use the new recovery to load any image you want onto the device.
@Lolatron
yeah, I've been reading and trying various things the last few days too, but it seems there is no way to downgrade from JB back to ICS with a locked device.
There are a few things I enjoy on JB (like the fixed IO problems of the dock that make the sdcard slot finally useable), but I'm really missing my root acess that got wiped with JB. I'll probably unlock it if we can't find a way to regain root in the next few weeks.
Click to expand...
Click to collapse
You cant revert back to the ICS bootloader once you have flashed the newer JB bootloader, unless of course you have done your NVFlash backups.
Danny-B- said:
You cant revert back to the ICS bootloader once you have flashed the newer JB bootloader, unless of course you have done your NVFlash backups.
Click to expand...
Click to collapse
Awww man, I feel foolish for not knowing what NVFlash is... safe to assume I haven't done that! Ahh well... hopefully time might bring a solution along, gotta put up with this for the time being then. Thanks for the info!

[Q] Best Backup Pre and Post Root/Bootloader Unlock?

Cannot seem to find the answer for this specific device. Will have the ATT USA version of the HOX+ and want to know:
What is the Best Back Up App to get before rooting or anything like that, something that can be found in the Play store? Obviously would want it to backup the basics like calender, contacts, email accounts, etc. Also though, need a backup app that will backup installed App Data like say my game progress for Dead Trigger. I'm reading that once you root your device all App Data is erased to scratch, would hate to invest hours into an app only to have to start all over once Rooted when it does become available for ATT USA version.
Then once i am Rooted, what is the best Rooted Backup App to install that will backup everything above and anything else i would need before unlocking Bootloader and flashing roms?
Seems there's unroot backups and rooted backups but hundreds on the Play store and hate to find out the hard way which ones actually work and do what i need and which ones don't.
Appreciate any help on this and hope soon there will be stickies in this thread explaining such things to Androids Newbs like me so once this device is released tomorrow you guys don't get countless threads started like mine. Thank you
Is this right?
Upon doing more research online please correct me if i'm wrong here. From my understanding this is the process needed to flash a custom rom:
1. Root your device. Rooting actually does not delete any data or files but virtually "unlocks" (almost like jailbreaking Ios) your device for further access/tweaking abilities.
2. Now that i am rooted i can install titanium backup (is this the best rooted backup, see it mentioned by you guys a lot here) and this rooted backup app will backup virtually everything on my device including app data.
3. Once rooted, i can now install custom recovery (what exactly is this and what does it do?). I'm guessing custom recovery is needed for unlocking the bootloader incase there is a problem custom recovery will recover your device (hints the name custom recovery)?
4. Now i have my device rooted, everything including app data backed up with titanium backup, custom recovery installed, now i can unlock bootloader. Once i unlock bootloader i will then need to restore my device with titanium backup. Now my phone is basically fully unlocked (fully jailbroken) and can now flash any custom rom available for my specific device (ATT HOX+ USA model)?
I see something mentioned about ADB but do not understand what this does or is used for? It seems it is another way of backing up the phone but if so, where is the backup file saved and used for exactly?
Just trying to figure this all out guys, please be easy on me. Trust me i've been researching and just trying to put all the pieces to this android puzzle together here, newb to android and first android device (very excited and just want to do it all right and not have issues of course).
If i'm missing any steps or have them out of order please let me know. I understand there is no root yet for this specific device but just saying if everything was available the steps i laid out is what i would do?
Thank you in advance for your patience and help, greatly appreciate the community here and all you guys do for us.
Sorry one more thing. Once i am rooted, unlocked bootloader, flashing custom roms having a great time. What exactly do the warranty people look for if i need to send my device in for replacement under warranty?
Do they void it if my device is rooted, or unlocked bootloader, or both?
If so, is root and or bootloader unlock reversible if i needed to return my device under warranty for say a hardware issue?
I'm sure i can flash the stock rom back so the warranty people won't see a custom one on the device but do they look for Root or Bootloader?
Just trying to cover all my bases here, thank you.

[Q] TWRP/Custom Status

Hey guys. Sorry if this has been answered before. I've looked and didn't see it in here so I figured I'd ask. I really don't want to set my phone into "custom" status in case I drop it or break it somehow Anyway, my question is will installing TWRP recovery from GooManager get me a "custom" status? Also, if I install a custom ROM, is there anyway to "trick" it into saying "Official" when I have ROMs and TWRP installed? I really wanted to install ROMs, but I'm too afraid of dropping it or something while the ROM is installed. Thanks!
I believe the "Custom" shows up periodically if you have a custom ROM installed. But really, it shouldn't bother people so much. It's pretty easy to tell if a custom ROM is installed without rebooting the phone. If Verizon cared that much, they could find out. FWIW, I didn't see "Custom" with the open padlock at boot when running stock rooted (aside from during the root process using the pre-release kernel.) It was only after installing a custom ROM that I see it periodically now.
Tortuga said:
I believe the "Custom" shows up periodically if you have a custom ROM installed. But really, it shouldn't bother people so much. It's pretty easy to tell if a custom ROM is installed without rebooting the phone. If Verizon cared that much, they could find out. FWIW, I didn't see "Custom" with the open padlock at boot when running stock rooted (aside from during the root process using the pre-release kernel.) It was only after installing a custom ROM that I see it periodically now.
Click to expand...
Click to collapse
Thanks for your reply But the reason I'm asking is because I wanted to know if there's any way to install a recovery or custom ROM while keeping the "official" status for warranty reasons. Is there?
Dark_Spark said:
Thanks for your reply But the reason I'm asking is because I wanted to know if there's any way to install a recovery or custom ROM while keeping the "official" status for warranty reasons. Is there?
Click to expand...
Click to collapse
If you were to physically damage it, you would likely still be able to boot to download mode and Odin back to 100% stock. In that case you'd have what you are asking for. I don't believe there is a way to spoof the phone into thinking it's fully official. Like I said, if Verizon/Asurion/etc care enough, they should be able to find out unless you flash back to pre-root stock. Someone else can correct me if I'm wrong.
Tortuga said:
If you were to physically damage it, you would likely still be able to boot to download mode and Odin back to 100% stock. In that case you'd have what you are asking for. I don't believe there is a way to spoof the phone into thinking it's fully official. Like I said, if Verizon/Asurion/etc care enough, they should be able to find out unless you flash back to pre-root stock. Someone else can correct me if I'm wrong.
Click to expand...
Click to collapse
Sorry to ask a million questions, but I used to have my GS4 on the stock ROM but rooted but with TWRP recovery. The statuses everywhere read as Samsung Official. I mean even in ODIN mode too. Is that what they check for in the warranty process? Or can they detect if it was just rooted or have a custom recovery and deny a warranty claim? Thanks for your patience with me.
Dark_Spark said:
Sorry to ask a million questions, but I used to have my GS4 on the stock ROM but rooted but with TWRP recovery. The statuses everywhere read as Samsung Official. I mean even in ODIN mode too. Is that what they check for in the warranty process? Or can they detect if it was just rooted or have a custom recovery and deny a warranty claim? Thanks for your patience with me.
Click to expand...
Click to collapse
Happy to help...but I really don't know what Verizon or the insurance provider would check. Some individuals within those places will probably check more thoroughly than others. But I've heard several stories of people taking their phone to Verizon, the tech seeing that it's rooted/fully custom, and replacing it anyway.
If you ever need to take it in for a warranty claim (hardware issue) I'd go back to stock first, but that's my personal opinion.
Edit: Even if it's just stock w/ root, a decently savvy tech could tell just by looking into your app list and seeing "SuperSU" or "SuperUser" or any other root-required apps.
Dark_Spark said:
Hey guys. Sorry if this has been answered before. I've looked and didn't see it in here so I figured I'd ask. I really don't want to set my phone into "custom" status in case I drop it or break it somehow Anyway, my question is will installing TWRP recovery from GooManager get me a "custom" status? Also, if I install a custom ROM, is there anyway to "trick" it into saying "Official" when I have ROMs and TWRP installed? I really wanted to install ROMs, but I'm too afraid of dropping it or something while the ROM is installed. Thanks!
Click to expand...
Click to collapse
No ,there is no method published till now. Possibility to do that is less then 20% since we cant access the hidden scripts for analysing binary counts..
Sent from my GT-I8552 using xda app-developers app
Tortuga said:
Happy to help...but I really don't know what Verizon or the insurance provider would check. Some individuals within those places will probably check more thoroughly than others. But I've heard several stories of people taking their phone to Verizon, the tech seeing that it's rooted/fully custom, and replacing it anyway.
If you ever need to take it in for a warranty claim (hardware issue) I'd go back to stock first, but that's my personal opinion.
Edit: Even if it's just stock w/ root, a decently savvy tech could tell just by looking into your app list and seeing "SuperSU" or "SuperUser" or any other root-required apps.
Click to expand...
Click to collapse
Thank you!

Categories

Resources