Related
Hi all
I want to root my motorola xoom so I can overclock it and install custom roms. I just recently rooted and installed a custom rom on my nexus s for the first time and I enjoy it!
Just a little info. prior: I bought my Xoom in Canada. When they never release 3.1 I got upset and i believe i flashed the US version onto my device, would this cause any issues?
I started to follow this guide
http://forum.xda-developers.com/showthread.php?t=1278214
It tells us to download the clockwork recovery, but when I go to download the file it gives two options. One is a .zip and the other is .img and I have no idea which to download.
Thanks for the help!!!!
I'm not sure but I don't believe it should matter
Sent from my Gummy Charged GBE 2.1 using XDA App
The only thing though is on the download page it says to make sure you pick the right one so that you dont brick your device
Sent from my Nexus S using XDA App
I wouldn't risk it then
Sent from my Gummy Charged GBE 2.1 using XDA App
chrisjabroni said:
Hi all
I want to root my motorola xoom so I can overclock it and install custom roms. I just recently rooted and installed a custom rom on my nexus s for the first time and I enjoy it!
Just a little info. prior: I bought my Xoom in Canada. When they never release 3.1 I got upset and i believe i flashed the US version onto my device, would this cause any issues?
I started to follow this guide
http://forum.xda-developers.com/showthread.php?t=1278214
It tells us to download the clockwork recovery, but when I go to download the file it gives two options. One is a .zip and the other is .img and I have no idea which to download.
Thanks for the help!!!!
Click to expand...
Click to collapse
Use this guide http://forum.xda-developers.com/showthread.php?t=1249798 and when you read it you will see that you must never try to flash a .zip file via ADB, only an .img file.
This stuff is in the Xoom Heaven thread and also on its own in the General section.
Awesome, I like that guide better, there is more detail.
But will this method work if I have already unlocked boot loader (but perform unlocking again because I'm not sure if i did that or not) and it'll work for any Xoom?
Sent from my Nexus S using XDA App
Should work for any Xoom.
Originally Posted by Azlee105
I already read thru this thread and found out few people having same problem but lastly they don't come out/write here how they solve it. Still looking
Then look through the second half of the solarnz R4c recovery thread in Development. I know there is help there.
Good luck. If I find something I'll post it.
EDIT: I think if you go to post 285 or so in this thread you will start to find some good advice:
http://forum.xda-developers.com/show...y#post18486897
Click to expand...
Click to collapse
from: http://forum.xda-developers.com/showthread.php?p=18486897&highlight=can%27t+flash+recovery#post18486897
So now im stuck here...
I have read the three threads you told people to read. I tried renaming the recovery file. still says "error: cannot load 'recovery.img'
I found another post saying copy all the files in platform tools to the tools folder and try that, and that didnt work.
I'm curious, on my xoom during this process it says "starting fastboot support protocol" should it always say that?
chrisjabroni said:
from: http://forum.xda-developers.com/showthread.php?p=18486897&highlight=can%27t+flash+recovery#post18486897
So now im stuck here...
I have read the three threads you told people to read. I tried renaming the recovery file. still says "error: cannot load 'recovery.img'
I found another post saying copy all the files in platform tools to the tools folder and try that, and that didnt work.
I'm curious, on my xoom during this process it says "starting fastboot support protocol" should it always say that?
Click to expand...
Click to collapse
Yes to the starting fastboot protocol...
Check to make sure you have fastboot.exe in your tools or platform tools folder (whichever you are using)...some people said that it wasn't in the SDK but I did include a link. Without that fastboot.exe file you won't get anywhere.
yupp fastboot.exe is in platform tools, when I started the guide I made sure of it
I just tried something, but it seems weird.
So i was able to unlock the bootloader no problem, and my problem now is with flash the recovery.
I just tried after work again to see if maybe restarting my computer would help. Rather, I got the same error. But for giggles I typed "adb devices" and the xoom didnt show up ...
Any ideas? or does that help?
chrisjabroni said:
yupp fastboot.exe is in platform tools, when I started the guide I made sure of it
Click to expand...
Click to collapse
Make sure the recovery file you are downloading its called solarnz not Tiamat. The Tiamat file is either old or corrupt. The one with solarnz in its name is the newer version.
Hmmmm on the issue with adb...I'm sure it's something simple. I'm going to bed now... catch you in the am.
http://forum.xda-developers.com/showthread.php?t=1074979
Would I use the recovery file (fastboot one) found there?
Sent from my Nexus S
chrisjabroni said:
http://forum.xda-developers.com/showthread.php?t=1074979
Would I use the recovery file (fastboot one) found there?
Sent from my Nexus S
Click to expand...
Click to collapse
Yes, that should work.
Good luck!
Ok so I downloaded that recovery image, but on the thread it says "solarnz" but the actual image when downloaded is identical to the one I originally tried to use.
I tried it anyways figuring that maybe my version of the recovery is corrupted for some reason, still same error.
I'm still getting no devices when i input "adb devices" ... I checked device manager and it is recognized there under the "ADB Interface" as "Mot Single ADB Interface" with no exclamation marks or anything.
*Edit: Ok i'm learning something new every time I try something. I learned that I can't perform an "ADB" command while in fastboot. So i looked up fastboot commands and ran "fastboot devices" and my xoom showed up. Now im even more confused! haha
Weird ...
chrisjabroni said:
Ok so I downloaded that recovery image, but on the thread it says "solarnz" but the actual image when downloaded is identical to the one I originally tried to use.
I tried it anyways figuring that maybe my version of the recovery is corrupted for some reason, still same error.
I'm still getting no devices when i input "adb devices" ... I checked device manager and it is recognized there under the "ADB Interface" as "Mot Single ADB Interface" with no exclamation marks or anything.
*Edit: Ok i'm learning something new every time I try something. I learned that I can't perform an "ADB" command while in fastboot. So i looked up fastboot commands and ran "fastboot devices" and my xoom showed up. Now im even more confused! haha
Weird ...
Click to expand...
Click to collapse
You are right. The image file on solarnz's thread is the Tiamat version, which may not work. Did you check that thread to see if he posted the "solarnz" version? Also, see if anyone might still have the good file in their downloads. I probably do on my home pc. solarnz has requested that we don't put up any mirrors without his permission. but this might be different. I'll see what I can do.
That would be awesome, thanks!
Sent from my Nexus S
ok so I found the "solarnz" recovery image.
http://forum.xda-developers.com/showpost.php?p=14442295&postcount=104
but even still, I get the same error
chrisjabroni said:
ok so I found the "solarnz" recovery image.
http://forum.xda-developers.com/showpost.php?p=14442295&postcount=104
but even still, I get the same error
Click to expand...
Click to collapse
And you had the same issue with the version that is in the OP of his thread? It is probably not the issue of which file you're using but another issue, like with your sdcard...is it in the Xoom and mounted when you try to flash the file through fastboot? Is the sdcard good...have you tested it in another android device, if possible? This is all I can think of at the moment. Good luck.
OK wait should the recovery.img be in platform tools or on the sd card?
But yes, the SD card is/was in my Xoom, it does mount (it shows up in "storage" in settings). I put my SD card in my HTC legend and with file manager I could find the root .zip file
Edit*
Also would plugging my Xoom into a power source and by USB make a difference?
Sent from my Nexus S
Progress circles keep circling til battery dies. Coldboot didn't work. (Although Asus said I shouldn't try android icon.)
Don't want to wipe data if I don't have to because I was in the middle of backing up data when it got stuck (can I connect it to my 2 1/2 yr. old laptop to copy files I need?)
Have all updates except last one two weeks ago. Not under warranty.
hi
Try to connect it to PC when you turn it on..if your computer recognized it...other wise no way to copy data as far as i know..(I am also not a PRO).
For your tablet to boot again i think go into recovery and then wipe everything and it ll re format your tablet then it should be in factory condition.
If this dosent works try my guide see the first posts in here u ll find it!!..
Hope u ll recover it!
You should be able to pull some files, but I don't think you'd be able to get your app data back. The same thing happened to me not too long ago unfortunately and in the end I did end up having to wipe the data. You could try flashing a .blob file. Here's the thread I made, there's good advice in there:
http://forum.xda-developers.com/showthread.php?t=2253834
Sent from my R800i using xda-developers app.
It's nice to be important, but it's more important to be nice.
Can't Find adb download link
UndisputedGuy said:
You should be able to pull some files, but I don't think you'd be able to get your app data back. The same thing happened to me not too long ago unfortunately and in the end I did end up having to wipe the data. You could try flashing a .blob file. Here's the thread I made, there's good advice in there:
http://forum.xda-developers.com/showthread.php?t=2253834
Sent from my R800i using xda-developers app.
It's nice to be important, but it's more important to be nice.
Click to expand...
Click to collapse
Spent 45 min trying to find adb download link (without whole sdk if possible). Where is it.
Did you flash a .blob file?
Like your motto
pjspener said:
Spent 45 min trying to find adb download link (without whole sdk if possible). Where is it.
Did you flash a .blob file?
Like your motto
Click to expand...
Click to collapse
I did flash a .blob file but it didn't work for me. I downloaded the whole Android SDK as mentioned in the guides on the forum
And thanks
Sent from my R800i using xda-developers app.
It's nice to be important, but it's more important to be nice.
How to find Link to sdk with adb
UndisputedGuy said:
I did flash a .blob file but it didn't work for me. I downloaded the whole Android SDK as mentioned in the guides on the forum
And thanks
Sent from my R800i using xda-developers app.
It's nice to be important, but it's more important to be nice.
Click to expand...
Click to collapse
Forgive my ignorance. That link didnt lead me to an sdk with adb in the directories, which sdk do I use?
Also, I cant figure out how to get a list of the guides on this forum or all forums.
Thanks!
If you want to use ADB to try and pull your files, then download the Android SDK from here:
http://developer.android.com/sdk/index.html
You can search on Google for guides on how to use it and try asking if you get stuck
This guide should help you in using Fastboot commands (Method 2):
http://forum.xda-developers.com/showthread.php?t=2187982
While it does say it's for Unlocked Bootloaders, it works on Locked Bootloaders too if I'm not mistaken. The way I saw it when I did it was that I had nothing to lose and it did seem to complete the command just fine although it didn't work after that and I had to wipe the data.
adb devices command didnt work
UndisputedGuy said:
If you want to use ADB to try and pull your files, then download the Android SDK from here:
http://developer.android.com/sdk/index.html
You can search on Google for guides on how to use it and try asking if you get stuck
This guide should help you in using Fastboot commands (Method 2):
http://forum.xda-developers.com/showthread.php?t=2187982
While it does say it's for Unlocked Bootloaders, it works on Locked Bootloaders too if I'm not mistaken. The way I saw it when I did it was that I had nothing to lose and it did seem to complete the command just fine although it didn't work after that and I had to wipe the data.
Click to expand...
Click to collapse
"adb devices" didn't work for me either, how did you make it work? I'm in the same place you were.
Also are there separate adb drivers?
Thanks
Every time I try to flash the OTA update, it first asks me if I want to install the untrusted zip, which doesn't make much sense, because why would an OTA be untrusted?
Then, during the installation, it aborts for some reason. After that it asks if I want to fix root.
I have no idea why any of this is happening, but I can't install the update because of it. What should I do?
Sent from my Nexus 5 using Tapatalk
There should be a reason in recovery why it failed. We'd need to know it before we can help
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
For me at least (I didn't start this thread), it fails because Roboto-Bold.ttf contains unexpected content.
I don't recall ever changing Roboto-Bold.ttf, so I have no idea what about it is unexpected.
CarpeNivem said:
For me at least (I didn't start this thread), it fails because Roboto-Bold.ttf contains unexpected content.
I don't recall ever changing Roboto-Bold.ttf, so I have no idea what about it is unexpected.
Click to expand...
Click to collapse
It's a non standard font installed by something. If you have anything non standard on your phone the ota will fail
Thank you. I understood that.
What I meant to say is, how do I correct it? Where can I find a copy of Roboto-Bold.ttf that the update will be "expecting"?
And then, if/when it complains about another file being unexpected, where did I find THAT? etc, etc.
CarpeNivem said:
Thank you. I understood that.
What I meant to say is, how do I correct it? Where can I find a copy of Roboto-Bold.ttf that the update will be "expecting"?
And then, if/when it complains about another file being unexpected, where did I find THAT? etc, etc.
Click to expand...
Click to collapse
You need to read this http://forum.xda-developers.com/showthread.php?p=47369234. Basically you need to flash the stock system.img
Those instructions include "attach phone to computer while phone is in fastboot mode".
However, when I do that, when I attach my phone to the computer while in fastboot mode, my Nexus 5 is NOT SHOWN when I type "adb devices" OR "fastboot devices".
When my phone is in recovery mode, and I type "adb devices", then it IS shown. Additionally, if my phone is fully booted up as normal, if I type "adb devices", it IS shown then too.
But if there are things which need to be done from the computer at the command prompt (and it seems that there are) while the phone is in fastboot mode, well, I cannot do those things, as my device doesn't seem to recognized at all while in that mode.
CarpeNivem said:
Those instructions include "attach phone to computer while phone is in fastboot mode".
However, when I do that, when I attach my phone to the computer while in fastboot mode, my Nexus 5 is NOT SHOWN when I type "adb devices" OR "fastboot devices".
When my phone is in recovery mode, and I type "adb devices", then it IS shown. Additionally, if my phone is fully booted up as normal, if I type "adb devices", it IS shown then too.
But if there are things which need to be done from the computer at the command prompt (and it seems that there are) while the phone is in fastboot mode, well, I cannot do those things, as my device doesn't seem to recognized at all while in that mode.
Click to expand...
Click to collapse
Google tool adb fastboot drivers xda. Use that to get the drivers working with fastboot
jd1639 said:
You need to read this http://forum.xda-developers.com/showthread.php?p=47369234. Basically you need to flash the stock system.img
Click to expand...
Click to collapse
Will that do anything to root access?
Sent from my Nexus 5 using Tapatalk
kehlan said:
Will that do anything to root access?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
After taking the ota you'll have to re-root
I think it's finally happening. I think I'm finally done. I'm successfully running 4.4.2 on my rooted Nexus 5. Thank you so much for the help (especially since this isn't even my thread; it just had a title which aligned perfectly to my problem, so hopefully the OP was helped along the way also).
To recap, for future use other visitors to this thread...
1. I tried to apply the 4.4.2 update using an OTA.zip file I found elsewhere on the Internet. This is easy. You've probably already done this.
2. I was told "build.prop" contained unexpected content.
3. I remembered that I had changed the DPI, so I changed that back from my personal 420 to the default 480. This resolved the previous error message.
4. I tried again, but this time was told Roboto-Bold.ttf contained unexpected content. I have no idea why that was.
5. I followed SOME of the instructions on this page: http://forum.xda-developers.com/showthread.php?t=2513701
Specifically, from the "Method 2" section, I did the "fastboot flash system C:/image-hammerhead-krt16m/system.img" and "fastboot flash boot C:/image-hammerhead-krt16m/boot.img" commands. That's ALL I DID from the "type these commands" section of those instructions. Doing that, I did NOT lose data! (well, none that I've yet noticed, at least)
6. I tried AGAIN to flash the OTA.zip file from Clockworkmod Recovery. This time it finally worked!
7. I checked Settings > About Phone, and I'm running 4.4.2 now!
8. I'm having trouble changing the DPI back to 420. I'm probably not rooted anymore. I'll have to go do that again. No big deal. Everything else seems fine.
...along the way, I needed to install drivers, for which I tried so many things, I don't even remember anymore what was the best method. I think using "ADB Manager.exe" from within my ADB folder was best. I also, at one point, had to change my USB device type from MTP to PTP. That was done on the phone, by swiping down the notification area.
Ugh, I wish I remembered everything, so I could spell it out as directly and clearly as I would've appreciated it be this morning, but I've seriously done so much recently that I know I'm missing certain steps, and I feel really bad for anyone having problems. There are so many instructions on the Internet that say, "Do this, and then this will happen," but they never explain what to do if that DOESN'T happen. And now here I am, not being any better than any of them. Sorry. Good luck.
Glad you got it working
o I rooted my nexus 5. No issues. Installed TWRP. Same. Downloaded CM and GA to the phone. Then, very foolishly, wiped everything to prep for the install - SD card included. Now, all I can load is TWRP. No ROM to be found - obviously. Computer won't recognize the phone to load a ROM that way. Would be VERY appreciative of any help. TY!S
you can use the 'adb push' command in recovery to transfer a rom zip to the phone via your computer
meangreenie said:
you can use the 'adb push' command in recovery to transfer a rom zip to the phone via your computer
Click to expand...
Click to collapse
I have TWRP v2.6.3.0 installed. The bootloader option takes me to TWRP. The Recovery option just hangs at the Google splash screen. Can you be more specific pls? Thanks for the help.
bradley.robt said:
I have TWRP v2.6.3.0 installed. The bootloader option takes me to TWRP. The Recovery option just hangs at the Google splash screen. Can you be more specific pls? Thanks for the help.
Click to expand...
Click to collapse
Install adb drivers on your computer then go to TWRP recovery with your phone connected to your computer. Type 'adb devices', to check if your phone is detected, it should display your phone's serial number. Then you can 'adb push file' to transfer the cm/gapps zips from your computer to phone's internal sdcard.
So you have no idea how to use ADB? You're in for a real long night. -__-
Read this
http://forum.xda-developers.com/showthread.php?t=2513701
And this
http://forum.xda-developers.com/showthread.php?t=2507905
aldyu said:
Install adb drivers on your computer then go to TWRP recovery with your phone connected to your computer. Type 'adb devices', to check if your phone is detected, it should display your phone's serial number. Then you can 'adb push file' to transfer the cm/gapps zips from your computer to phone's internal sdcard.
Click to expand...
Click to collapse
Sorry, assume 'adb devices' is in the command prompt, but noob town - which folder in the ADT parent folder?
RoyJ said:
So you have no idea how to use ADB? You're in for a real long night. -__-
Read this
http://forum.xda-developers.com/showthread.php?t=2513701
And this
http://forum.xda-developers.com/showthread.php?t=2507905
Click to expand...
Click to collapse
That's what I figured, but...challenge accepted. Thanks for the links.
RoyJ said:
So you have no idea how to use ADB? You're in for a real long night. -__-
Read this
http://forum.xda-developers.com/showthread.php?t=2513701
And this
http://forum.xda-developers.com/showthread.php?t=2507905
Click to expand...
Click to collapse
RoyJ,
Appreciate the help. TY, all's good.
Happened to me a few times tinkering with the gnex, n4...boneheadedly wiped the internal storage. Easiest fix in my opinion is to just flash factory stock and start back from stretch. If not like they said you're in for a long night trying to get your phone to sync up to push the files via adb if you aren't familiar with the stuff.
Do wish you the best. Been there.
I have not been in that situation but couldn't you use a OTG cable (a Y type one which accepts power as well) and a SD card or stick and then mount it within TWRP to access a ROM to flash...?
EDIT: Also consider the Nexus Toolkit - very useful.
I really think that the faster way is to flash stock firmware back (if you have no experience with ADB commands).
Don't be so scared of adb. Its hard if you don't know Linux but adb is really really copy and paste for first time use. (That's how I learned anyways) You learn it once and it stays current and useful.
Sent from my Nexus 7 using XDA Free mobile app
Just install official images of nexus 5. No need to learn complex stuff where u have no idea even abt adb.
TheLastSidekick said:
Don't be so scared of adb. Its hard if you don't know Linux but adb is really really copy and paste for first time use. (That's how I learned anyways) You learn it once and it stays current and useful.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
It's really not that hard.. You plug it in, open a folder, open the prompt and type a few words.. My advice is to try and learn.
sent from my Nexus 5
Seadra said:
Just install official images of nexus 5. No need to learn complex stuff where u have no idea even abt adb.
Click to expand...
Click to collapse
A bit discouraging friend. I say learn on all about adb it's essential for Android. Knowledge is power.
Sent from my Nexus 7 using Tapatalk
Seadra said:
Just install official images of nexus 5. No need to learn complex stuff where u have no idea even abt adb.
Click to expand...
Click to collapse
You need fastboot/adb to do it anyways. Unless you use toolkits, ew.
Glad you got it sorted.
Letharqy said:
You need fastboot/adb to do it anyways. Unless you use toolkits, ew.
Click to expand...
Click to collapse
Yes, just the adb drivers needs to be installed. And I have never used toolkit ever.
TheLastSidekick said:
A bit discouraging friend. I say learn on all about adb it's essential for Android. Knowledge is power.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
No, you didn;t get my point. I told him to straight away restore by images just because his phone wasn't working at all. He can learn all that stuff later, but atleast he should be with no phone at all.
Seadra said:
Yes, just the adb drivers needs to be installed. And I have never used toolkit ever.
Click to expand...
Click to collapse
How would you flash the .imgs without using adb/fastboot?
Letharqy said:
How would you flash the .imgs without using adb/fastboot?
Click to expand...
Click to collapse
by adb drivers, I mean adb/fastboot or SDK and drivers of the phone that's always included.
This phone has had my attention for a while now, and after reading and watching videos on the phone, my biggest question is about root. If Cyanogenmod 11s isn't pre-rooted right out of the box, is there a root method/someone working on a root method and if not, how long will it be until that becomes a reality? If the phone doesn't have root, I'm afraid that I may not be able to go for this phone as I am heavily invested a number of root operations and apps that I have set up on my phone. Let me know if anyone knows anything.
adambombz said:
This phone has had my attention for a while now, and after reading and watching videos on the phone, my biggest question is about root. If Cyanogenmod 11s isn't pre-rooted right out of the box, is there a root method/someone working on a root method and if not, how long will it be until that becomes a reality? If the phone doesn't have root, I'm afraid that I may not be able to go for this phone as I am heavily invested a number of root operations and apps that I have set up on my phone. Let me know if anyone knows anything.
Click to expand...
Click to collapse
It's not rooted out-of-the-box. Google doesn't allow this. But apparently, root will be very easy; just plug it into your computer and enter in a few command lines and you're set (so I've heard). Undoubtedly someone will make a one-click script that makes it even easier.
EDIT: Sorry for that one, was posting too fast without thinking first... Actually rooting includes unlocking bootloader and flashing the required binaries via recovery like said below my post.
Sent from my Desire X using XDA Premium 4 mobile app
dansou901 said:
It will be even easier then that. You'll just have to enable root in developer settings, that's all.
Click to expand...
Click to collapse
Really? Sweet!
Andrew Martonik at Android Central spent almost a month with the phone and had this to say about rooting in the review he released just a couple days ago.
Naturally if you want to root the phone, it's only a quick USB cable plug into your computer and a few command line entries away.
Click to expand...
Click to collapse
Good read, BTW.
OnePlus One Review | Android Central
CafeKampuchia said:
Andrew Martonik at Android Central spent almost a month with the phone and had this to say about rooting in the review he released just a couple days ago.
Good read, BTW.
OnePlus One Review | Android Central
Click to expand...
Click to collapse
That's where I heard it. In any case, it'll be simple; that much was promised from the beginning.
What about SuperSU though? I'm honestly not sure how that gets installed to the right place; the only times I've rooted were with programs that did it for me.
I don't think the retail cm11 will have root. In order to pass android cts, they had to remove root from the release builds. Don't worry, the phone is likely either unlocked or unlockable and it can be rooted with supersu or superuser like a Nexus device. Speculation but I don't see the cm folk going with a locked down phone. Maybe someone who has cm11s should confirm if it has root.
Sent from my HTC One using Tapatalk
dansou901 said:
It will be even easier then that. You'll just have to enable root in developer settings, that's all.
Sent from my Desire X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Oh really? Absolutely ridiculous.
tiny4579 said:
I don't think the retail cm11 will have root. In order to pass android cts, they had to remove root from the release builds. Don't worry, the phone is likely either unlocked or unlockable and it can be rooted with supersu or superuser like a Nexus device. Speculation but I don't see the cm folk going with a locked down phone. Maybe someone who has cm11s should confirm if it has root.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Correct - no retail device shipping with Google CTS/GMS can have root enabled, much less the ability to right OUT OF THE BOX. It has to be done manually by the user, at their discretion.
From what I've read so far, it seems that the phone is fastboot unlocked by default (Normally you'd have to run "fastboot oem unlock"). Since that's already been taken care of, all that would need to be done to gain root is flash a recovery using "fastboot flash recovery recovery.img" (official TWRP build is available), and finally install the SuperSU zip via your newly flashed custom recovery.
Essentially the same method as a Nexus device, other than the fact that the bootloader is already unlocked so that step can be skipped.
Chromium said:
From what I've read so far, it seems that the phone is fastboot unlocked by default (Normally you'd have to run "fastboot oem unlock"). Since that's already been taken care of, all that would need to be done to gain root is flash a recovery using "fastboot flash recovery recovery.img" (official TWRP build is available), and finally install the SuperSU zip via your newly flashed custom recovery.
Essentially the same method as a Nexus device, other than the fact that the bootloader is already unlocked so that step can be skipped.
Click to expand...
Click to collapse
So no way to use CM's SuperUser app huh because that's built into the OS. We'll have to use a 3rd party app like SuperSU?
dmo580 said:
So no way to use CM's SuperUser app huh because that's built into the OS. We'll have to use a 3rd party app like SuperSU?
Click to expand...
Click to collapse
Well, I'm just speculating since I don't actually have the device yet. The CM rom that comes on the phone is not prerooted, nor does it have the Superuser app in it (I'm basing that off an update.zip that's posted in the dev section which doesnt seem to contain the apk). So you'd most likely have to do as I explained above. You dont necessarily have to use SuperSU though. You could probably obtain root by flashing the Superuser zip instead.
cyanogenmod has been planning to separate root for years. i think they are coming up with a simple method of root. maybe just an app install?
You will be able to root with any existing root method with a custom recovery. I'm not sure if cm11s comes with cwm. Anyway rooting is trivial.
Cm I think opted to make root removal so they could get cts approval and install Google Apps.
Sent from my HTC One using Tapatalk
it doesnt come with cwm. thats a different project, by a different group. and you dont necessarily need an alternative recovery, depending on the rooting method.
The Jack of Clubs said:
it doesnt come with cwm. thats a different project, by a different group. and you dont necessarily need an alternative recovery, depending on the rooting method.
Click to expand...
Click to collapse
I wonder if they're using this recovery.
https://github.com/CyanogenMod/android_bootable_recovery-cm
Simple recovery is the working title.
You are correct that custom recoveries aren't always needed for root; however, in Android 4.3 and later, the two primary root applications need to install a superuser daemon which makes rooting outside of recovery more difficult.
tiny4579 said:
You will be able to root with any existing root method with a custom recovery. I'm not sure if cm11s comes with cwm. Anyway rooting is trivial.
Click to expand...
Click to collapse
You all guys keep saying that rooting is trivial, but nobody told how to root. I believe you that it's trivial but - anyway -please tell me how to do this step by step.
I'm actually having trouble getting my 64GB production unit to boot into TWRP or have it flash and stick. fastboot says everything is fine, then rebooting into recovery produces the stock simple recovery.
fastboot boot twrprecovery.img ends up hanging on the fastboot screen, basically nothing happens, but fastboot does stop responding to commands.
I'm sort of at a loss - I've done this to many Nexus devices before, and the idea is the same. My bootloader is unlocked, that went without any issues.
Booting a debug boot.img from https://cyngn.com/products/oneplusone via fastboot just ends up shutting down and showing the battery charging icon.
Volume Up + Power while booting ends up with a black screen - in fact, the only way I can get into recovery is from a booted OS.
Edit: After many tries, trying different cables and unchecking the Settings -> Development -> update recovery with system updates, the TWRP flash succeeded, and the subsequent SuperSU sideload went just fine. Now I'm rooted.
Another tip regarding using Power+VolDn or Power+VolUp - things happen so slowly that if you keep holding Power, it'll actually trip a reboot before it has a chance to load. Just hold the Power button for a few seconds when booting, then let go and keep the VolUp or VolDn pressed.
Chromium said:
Well, I'm just speculating since I don't actually have the device yet. The CM rom that comes on the phone is not prerooted, nor does it have the Superuser app in it (I'm basing that off an update.zip that's posted in the dev section which doesnt seem to contain the apk). So you'd most likely have to do as I explained above. You dont necessarily have to use SuperSU though. You could probably obtain root by flashing the Superuser zip instead.
Click to expand...
Click to collapse
I just did this and it seems to have worked. TiBu just completed..
Used "Fastboot boot TWRP-2.7.1.0.zip" at ADB/Fastboot interface. It booted to TWRP. As I closed, it stated that it looks like "Your device isn't rooted, Do you want to install SuperSU?" To which I said Yes. It rebooted and I was able to open SuperSU, already on the phone, and get root. Then, opened TiBU and performed a full backup.
Archon810 said:
fastboot boot twrprecovery.img ends up hanging on the fastboot screen, basically nothing happens, but fastboot does stop responding to commands.
Click to expand...
Click to collapse
The first time I did this it hung for a while. it eventually boots into the recovery. I think it took about 2 minutes for it to finally boot into it.
Maybe that helps?
Root One+ fastboot devices hnags "waiting for device"
I amd trying to unlock bootlaoder, and install TWRP on my ONE+. I have tried both android SDK, and TOOLKIT FOR ONEPLUS FROM XDA, and I cannot get fastboot devices to recognize my One+.
What I have do so far:
My PC: windows 7 - 64bit
Installed SDK kit form developer.android.com, and installed the latest composite usb driver from Google.
Installed OnePLus toolkit and tried using that, no dice.
when I execute "fastboot devices" from my fastboot folder, my prompt hangs "waiting for device" FOREVER!!!
"ADB DEVICES" WORKS PERFECTLY, AND ECHOES MY SERIAL NUMBER BACK TO ME."