OK so the goal is to get a CM10 nightly build on my Asus transformer prime
What i have done so far is unlock the device via downloading the Asus utility to my prime, that seems to have worked fine.
Here is where i think everything went wrong,
I installed sparkyroot on my prime, it seems to have worked fine but when installing superuser app i see "su file does not exist or have correct permissions" but i went and installed the app anyway.
Now im stuck at rom manager app on my asus, when i open the app i get "you must root your phone for rom manger to function" superuser was not found at /system/bin/su...." .
I obviously didn't root properly.
when i try and press flash clockworkmod touch i simply get "an error occurred while trying to run privileged commands"
I messed up can someone please give me clear and noob friendly instructions on how to get to my end goal of CM10 from where i am PLLZZZZZ
http://forum.xda-developers.com/showthread.php?t=1706588
While I can't give specific instructions to get you what you want, I know enough to offer this advice:
- you don't need to root your Prime in its current state!
Once unlocked, you have the ability to install a custom ROM. Any ROM you install will be pre-rooted and your current 'un-rooted' state is of no concern. There is no advantage to being unlocked EXCEPT to install ROMs (all of which will have root by default).
Spend your efforts rowards getting a custom recovery installed then flash CM 10. One last thing, I have read of many problems with CWM running on Prime, and Team Win recovery is the safer option.
Hope I helped, hit thanks if I cleared anything up for you.
Good luck
Once unlocked flash with fastboot a custom recovery and my advice is NOT CWM (softbrick maker) but TWRP. Go in twrp thread and website for instructions.
Then, either you flash a custom ROM, or you can search here in xda (not prime section, general one I guess) the super user zip file to flash it with twrp to stay with your current ROM.
Related
I recently purchased a used Galaxy tab 10.1 I/O, and it had already received the 3.1 OTA update.
Now i want root access for various reasons, and can't seem to find a clear guide on how to do so.. I've found plenty about how to do so on the original 3.0 rom, and that it will carry through the 3.1 update, or for the regular version Galaxy Tab 10.1, but it's my understanding the ROMs were fairly different between the I/O and the retail version and that attempting to cross-pollinate root methods may not be a good idea
although I've rooted and ROMed my fair share of HTC devices and Nooks i'm a little more apprehensive with this unit, as it's my first android device to lack an SD card slot of some sort, so bricking seems like a much worse possibility
The best guide ever is in the development section, it works for your device.
http://forum.xda-developers.com/showthread.php?t=1239185
follow the guide its very easy and worked fine for me
I Return triumphant, and gentlemen, i must say you were incorrect.
The I/O edition does not give you the option to access recovery at any point, even with the Pwr+VOL DN boot.
You can put it into download mode, and certianly use ODIN to install the recovery rom, but you will have no method to actually access recovery to push zip files.
thanks to some quick self education on using fastboot, i was able to root successfully.
To those of you in a similar situation who stumble upon this thread, i invite you to visit:
http://droidbasement.com/db-blog/?p=2439
There you can download CWM in a .img format for use with fastboot.
This link is where you can download fastboot:
http://forum.xda-developers.com/attachment.php?attachmentid=596615&d=1305443483
and you'll need to install PDANet for Android to get the fastboot drivers:
http://junefabrics.com/android/
I belive you'll also need ADB installed from the Android SDK. i do have it installed on this computer, but did not use the ADB command at any point, just fastboot.
Instructions:
1. Download fastboot, PDANet for android, and the recovery image. You'll also need "Samsung_Galaxy_Tab_10.1_root.zip" found in Root.zip from the retail version instructions.
2. Copy the "Samsung_Galaxy_Tab_10.1_root.zip" to the tablet, and and power it off. Disconnect the USB connection
3. Unzip fastboot zip into it's own folder, and then copy your recovery.img file into the same folder.
4. Start the install of PDANet. It will ask you if you want to install drivers about half way through. say yes, and select "Samsung" when the time comes. it will install some drivers and then ask you to try and connect. windows may flare up and say they're unsigned. accept anyway.
5. watch this friendly video on how to start fastboot on your tablet:
http://www.youtube.com/watch?v=sR7vE4IueaU
"fastboot!"
Basically the same as the steps outlined for the retail version, but you will go to the usb icon instead of the box.
6. once the tablet is in fastboot, connect the USB cable. PDA net will recognize it as an ADB connection and try and load itself. it will fail, that's fine. Let the installer exit completely.
7. Open a command line in windows, and get it to the directory fastboot.exe and your recovery image are in.
8. run your fastboot command. i only used it temporarlily, so my command was:
"fastboot boot recovery-cwm_5.0.2.7-sam-tab-10.1.img"
9. the tablet should now boot into the recovery image presented. hooray! follow the remaining instructions from the retail version root, using recovery to load the "Samsung_Galaxy_Tab_10.1_root.zip" and reboot.
10. Once you've done all that, select to reboot. The tablet will reboot. i took the opportunity to disconnect the cable.
11. "Superuser" should now be in your apps, and you're rooted!
Extra Step: Download "Rom Manager" by clockwork from the android market, and install it. from here, opt to flash recovery. Once that's complete, you can now access recovery by launching that program and simply hitting "Reboot into Recovery"
I have no use for this myself but it's not often someone comes back and posts a complete howto on solving their own initial issue. I wish more people would do this. Thanks button clicked.
I just ran into this exact problem and only found this thread after figuring it out on my own. I figured my IO tab just didn't like having clockwork mod installed, but it certainly booted it. I nearly ruined it by accidentally wiping my rom trying to get it to boot at all. I had to repush my install files to the insternal memory using adb after I was able to boot into recovery with fastboot.
I haven't looked around too much (seeing as I only JUST got the damn thing to boot a rom) but is there a fix to that, perhaps installing the retail bootloader?
I'd hate to have to use fastboot everytime my rom doesn't boot. I've gotten used to wiping and installing roms from wherever I am on my other android devices.
I'm not familiar enough with the device to be able to give you a definite answer, but i imagine adding a bootloader from the retail version would give you the recovery option instead of fastboot.
personally, i'm a little more fond of having fastboot around right now, as it's easy enough to get into recovery when flashing things with it, and the bootloader for the I/O is unlocked... i can think of a few fun things to do in the future if i can load any ROM i want into memory, test it, and move on if it's no good... i may even give some of the ICS dailies a try thanks to this.
Always several ways of doing things... glad you got it worked out.
http://forum.xda-developers.com/showpost.php?p=15735928&postcount=2
RootzFan,
that method is flashing an entirely new rom, down to 3.0, just to gain root access and open recovery so you can then return to 3.1.. it has the added byproduct of installing touchwiz.
IMHO, my way is a little cleaner as there is actually zero flashing needed, and you get to keep everything active and installed.
i recommend just going for custom roms - it comes already rooted - yBoot into recovery and flash a custom ROM
I have the IO tab myseldf and have been flawlessly running GalaxyTask custom ROM - http://forum.xda-developers.com/showthread.php?t=1340064
shane86 said:
I recently purchased a used Galaxy tab 10.1 I/O, and it had already received the 3.1 OTA update.
Now i want root access for various reasons, and can't seem to find a clear guide on how to do so.. I've found plenty about how to do so on the original 3.0 rom, and that it will carry through the 3.1 update, or for the regular version Galaxy Tab 10.1, but it's my understanding the ROMs were fairly different between the I/O and the retail version and that attempting to cross-pollinate root methods may not be a good idea
although I've rooted and ROMed my fair share of HTC devices and Nooks i'm a little more apprehensive with this unit, as it's my first android device to lack an SD card slot of some sort, so bricking seems like a much worse possibility
Click to expand...
Click to collapse
oh, def not the best method... just saying it is nice that there are alternatives.
self delete
Fun Stuff.
Hey Everyone,
So, I'm pretty sure I'm going to unlock the bootloader on my Prime, but I had a quick question before I do, and I'm not seeing any sort of threads which help me out that much (Or at least the ones I looked at).
To make the story short, I'm looking to be able to root my tablet and install a custom ROM on there, however, it is to my understanding that there is no way to root the .21 firmware at this time. However, I was wondering if by unlocking the bootloader I would be able to manually push CWM Touch and thusly be able to boot into recovery, installing a rom that is pre-rooted, or even just rolling back to a previous update. I'm fairly familiar with ADB and terminal commands, so I am not shy to get into the nitty gritty if need be.
I apologize in advance if this has already been answered or asked, but, I'm in a time crunch and was looking for some advice !
Thanks for the information,
Horvaticus
Horvaticus said:
Hey Everyone,
So, I'm pretty sure I'm going to unlock the bootloader on my Prime, but I had a quick question before I do, and I'm not seeing any sort of threads which help me out that much (Or at least the ones I looked at).
To make the story short, I'm looking to be able to root my tablet and install a custom ROM on there, however, it is to my understanding that there is no way to root the .21 firmware at this time. However, I was wondering if by unlocking the bootloader I would be able to manually push CWM Touch and thusly be able to boot into recovery, installing a rom that is pre-rooted, or even just rolling back to a previous update. I'm fairly familiar with ADB and terminal commands, so I am not shy to get into the nitty gritty if need be.
I apologize in advance if this has already been answered or asked, but, I'm in a time crunch and was looking for some advice !
Thanks for the information,
Horvaticus
Click to expand...
Click to collapse
um...sorry....it might come across as harsh but you didnt look did you? If your familiar with ADB then you should know that rooting has nothing to do with custom roms. In order to put a custom rom you have to have an unlocked bootloader.
Review the Android development Section for info on roms/bootloaders/rooting
An unlocked bootloader was released and we had a rom available within 2 hours.
If you go to ANY thread with [ROM] they will tell you what you need to do. Easy.
And .21 is cooked into many Roms so far...i'm using virtous Prime and prefer that one so far...(it's really about preference)
So...moral of the story..please read before posting...do a quick search...it's been answered before.
monkeyboywa said:
um...sorry....it might come across as harsh but you didnt look did you? If your familiar with ADB then you should know that rooting has nothing to do with custom roms. In order to put a custom rom you have to have an unlocked bootloader.
Review the Android development Section for info on roms/bootloaders/rooting
An unlocked bootloader was released and we had a rom available within 2 hours.
If you go to ANY thread with [ROM] they will tell you what you need to do. Easy.
And .21 is cooked into many Roms so far...i'm using virtous Prime and prefer that one so far...(it's really about preference)
So...moral of the story..please read before posting...do a quick search...it's been answered before.
Click to expand...
Click to collapse
Well, I know that rooting has nothing to do with Rom installment. Admittedly I was posting from a golf course and didn't take the time to sift through the threads. So, thanks for answering my question, kinda. When I said Root & Install a custom Rom I did not mean that in sequential order. Simply that I would like a Rom that has root baked into it, or be root-able.
Unlock your device via Asus's unlock tool app.
Download and install Rom Manager from Market.
Install CWM via Rom Manager.
Download the rom you want to flash and transfer it to your tablet.
Reboot into CWM and make your first nandroid backup.
Wipe Cache/Factory reset.
Wipe Dalvik Cache
Flash the rom and reboot.
reNeglect said:
Unlock your device via Asus's unlock tool app.
Download and install Rom Manager from Market.
Install CWM via Rom Manager.
Download the rom you want to flash and transfer it to your tablet.
Reboot into CWM and make your first nandroid backup.
Wipe Cache/Factory reset.
Wipe Dalvik Cache
Flash the rom and reboot.
Click to expand...
Click to collapse
you need root access to flash cwm from rom manager, afaik.
Sent from my TF201
reNeglect said:
Unlock your device via Asus's unlock tool app.
Download and install Rom Manager from Market.
Install CWM via Rom Manager.
Download the rom you want to flash and transfer it to your tablet.
Reboot into CWM and make your first nandroid backup.
Wipe Cache/Factory reset.
Wipe Dalvik Cache
Flash the rom and reboot.
Click to expand...
Click to collapse
Yeah, you do. But I unlocked it via the unlock tool APK and then from there just installed CWM via fastboot and pushed the rom and crap to it. Thanks! Installing now!
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.
I was attempting to use the method found here: http://forum.xda-developers.com/showthread.php?t=1690919 to root my EVO 4G LTE, but am unable to post in that thread with questions, as I have less than 10 posts, apparently. My issue is that I go all the way through the process, install ROM manager, and then try to flash the latest ClockworkMod (Superuser 3.0.7 efghi), but it gives me the following error:
"You must root your phone for ROM Manager to function. Superuser was not found at "/system/bin/su" or "/system/xbin/su". Use Google Search on your computer to find instructions to root your phone"
I rebooted into recovery mode, and it does say "UNLOCKED" and "TAMPERED" at the top... in case that's helpful. Does anyone know where I might go to figure this out? I've been combing through the original post by regaw_leinad but haven't spotted anything yet. Any help is appreciated.
CWM doesn't work on our phone. You have to flash TWRP via terminal emulator.
Sent from my EVO using XDA
Yeah they really should put a disclaimer on that cwm thread. You would never know looking at the op that it doesn't work.
Evo_Shift said:
Yeah they really should put a disclaimer on that cwm thread. You would never know looking at the op that it doesn't work.
Click to expand...
Click to collapse
There is a disclaimer and the download was removed from the thread ages ago. This is only an issue for people who don't research first and try to use rom manager to install cwm (no offense to op). ROM manager should have a disclaimer also.
hmm... okay, well thanks for the info. maybe i've hosed something, as after installing the GooManager app as directed on the teamwin site and then initiating the download of the OpenRecoveryScript, it does not seem to do anything after the download, though the app says that it would reboot to install.
i'm still up against a wall with using either the GooManager, or trying to copy the openrecovery script directly onto the internal SD card and using terminal emulator... is there another method? or another way to approach this or start all over or something? it just seems like i can't get anything to work like it's supposed to at this point... even the terminal emulator is telling me that "su" isn't a recognized command... any help is appreciated.
mckraut79 said:
i'm still up against a wall with using either the GooManager, or trying to copy the openrecovery script directly onto the internal SD card and using terminal emulator... is there another method? or another way to approach this or start all over or something? it just seems like i can't get anything to work like it's supposed to at this point... even the terminal emulator is telling me that "su" isn't a recognized command... any help is appreciated.
Click to expand...
Click to collapse
I used the same root process and flashed cwm via rom manager and then had to go to goomanager. Goomanager works since I got twrp working, but I haven't flashed anything since I wanna wait to see if the new roms break lte (if lte comes to Seattle).
i tryed flashing twrp through goo manger also and it didnt work after it downloaded it woulndt reboot.. so i had to flash twrp using terminal emulator.. worked like a charm
Won't break lte like the Wimax issues. Lte info OS stored on the simcard unlike Wimax in a separate partition
sent from my EVO LTE
any advice on the su command not found in terminal emulator? i searched on google and saw other people having similar problems and mentioned making sure that SuperSU was running first which I have installed unbeknownst to me... though if I try to launch SuperSU, it tells me that there is no SU binary installed and SuperSU cannot install it, and all I can do is quit.
Try the flashable in the supersu thread
just to add another note... I also went through the process to install the Android SDK, so that I could connect via adb... after doing that, I can access my device via adb, but after doing "adb shell", I then try to use the su command, and get the same error,
su
/system/bin/sh: not found
what am I missing here? is my phone not truly rooted then?
i rebooted into recovery and verified that the boot loader shows UNLOCKED and TAMPERED (that's desired, right?) and that TWRP was my new recovery image, if that's the term for it. i had already downloaded the latest viperboy image, and booted into twrp and went through the install process for that image..... and the weird thing was everything seemed like it took and it installed. but nothing was different on a reboot. any ideas?
Unlocked and tampered don't necessarily mean you have root. At the risk of sounding stupid I have one question. Have you tried re-running Regaw one click then flashing your desired ROM of choice?
Seems re-running the script has fixed other people's issues.
sent from my LTEvo
believe me, if anything I'm the one that sounds stupid here I'm sure. at any rate, I did run regaw twice, but that was a while ago, and it was because it seemed like the first time through it didn't complete the process successfully for some reason. i can run it again today. after i do that, is the best way to tell if you're rooted to run the terminal emulator and try an su command and see if it's successful or not?
An app that requires root will work, if you get a prompt you should be golden. I would recommend re-running you should be fine, if there is an additional problem there is a fix for what clockwork would have messed up in the twrp thread (on my phone can't find it now), but I think you should be fine.
Edit: I lied, if you have the misc partition issue from trying cwm the fix is in viper Rom thread here. http://forum.xda-developers.com/showthread.php?p=26663638
sent from my LTEvo
well i ran the root method from regaw again and it looks like i'm now good to go as far as i can tell.... i'm running viperboy's ROM... i saw one from flex360 (the super stable/fast one), but not sure which ZIP package to download... so not sure if i will try any others since i'm not sure what to do there (and i can't post in those threads to ask for advice). i see the charmeleon one looks popular also...but then i would have to flash that boot file also? maybe i should just let good enough alone and be happy with the ROM i have.. thanks for all the help and suggestions here, you guys are helpful
No problem, viper Rom is good (running it until cm9 is official) you can flash another Rom but heed any OP warnings. Also, don't be flash happy, it could prove harmful in the end. :beer:
sent from my LTEvo
excellent! thanks for the info... that's really exactly what i wanted to hear... the validation that the rom i have is perfectly fine and just be happy
Also, as for the charmeleon ROM, I believe you SONT need to flash a boot.img. I believe that info is deprecated. Within the first few pages you'll find out for sure.
I believe when joelz first posted the ROM he thought that'd be necessary, but was able to include boot.img in ROM zip.
sent from my Jewel via xda premium.
So I've spent a few hours looking around for how I can upgrade my Transformer Prime to JellyBean and I'm beyond frustrated.
It seems there are so many different guides, and almost all of them for older versions of the prime (< .28). I read through all the rooting guides on the "rolled-up sticky guides" page
It's almost as if you come late to the rooting scene with your device you're out of luck.
Then I decided the best method to approach this is skip rooting my device and simply unlock my bootloader, then use fastboot to load CWM onto my device.
Only problem is I'm reading tons of sketchy looking sites with broken image links on how to do this, and the user comment complaints on those sites don't really raise my confidence.
I found this link:
http://wiki.cyanogenmod.com/wiki/Asus_Transformer_Prime:_Full_Update_Guide
but then read this:
"NOTE: In order to flash CyanogenMod via ROM Manager, root access is required. Attaining root access is outside the scope of this wiki page."
WTF!??!
So can someone here verify if I need root access to flash a ROM if I've already installed CWM?
EDIT:
I was confusing ROM Manager with Clockwork Recovery (in my head they are the same). So the guide is correct, I do need root for ROM Manager, but not for Clockwork Recovery.
So the steps I needed to take were:
1) Unlock the bootloader using the official Asus bootloader unlocker
2) Follow this guide: http://wiki.cyanogenmod.com/wiki/Asus_Transformer_Prime:_Full_Update_Guide, but use the Clockwork Recovery way instead of the ROM Manager way.
3) Enjoy Jelly Bean
ÄIf you want to flash cwm instead of twrp then just head to cwm home site. If you want to flash twrp then head to the twrp thread. Also fastboot shouldn't be too hard to find. Then just follow any guide to flash recovery. Also that guide seems to be messed up obviesly you don't have to be rooted to flash with cwm. http://www.androidauthority.com/install-cwm-5-8-2-0-on-transformer-prime-60909/
Also if you need. That guide should work just fine.
Sent from my GT-I9100 using xda app-developers app