Related
G'day guys,
I was trying to install a custom recovery after unlocking the bootloader and something horribly went wrong
during the install, phone seemed to hang, gave it a good amount of time to do it stuff but nothing happend.
Didn't think much of it as i thought i could just start again with the install, but had no joy. Then somehow in
my panic i have managed to lock the bootloader again really making it difficult to do anything.
As it stands at the moment, i can do the following with the phone.
Can get into the fastboot screen
Cannot get into recovery.
Will start normally and show the powered by android screen then will just sit there as if it was starting (which it doesn't)
I was using the following guide :http://forum.xda-developers.com/showthread.php?t=2788632 for the process.
I must also stress that this isn't the 1st time i have tried to root android phones and have successfully rooted my S2,S3 and note 2.
That being said i have totally rooted this OPO.
I have spent the last 3 days basically reading any thread in this forum with the hope of reversing this cockup
and have tried many but to no avail. Basically road blocked i think by the locked bootloader.
The only thing i haven't tried yet is using a computer with Win xp as Win 7 is a pain in the arse for drivers.
Any of you guys got some idea whether this fixable or should i just give up and bin it? I don't want too and would love to be able to get
it back up running but this has really done my head in.
Cheers
U can flash factory images from fastboot:http://forum.xda-developers.com/oneplus-one/orig-development/discussion-cyanogenmod-11s-t2840305
ashishv said:
U can flash factory images from fastboot:http://forum.xda-developers.com/oneplus-one/orig-development/discussion-cyanogenmod-11s-t2840305
Click to expand...
Click to collapse
Not with a locked bootloader.
Transmitted via Bacon
---------- Post added at 07:09 PM ---------- Previous post was at 07:07 PM ----------
Moatmonster said:
G'day guys,
I was trying to install a custom recovery after unlocking the bootloader and something horribly went wrong
during the install, phone seemed to hang, gave it a good amount of time to do it stuff but nothing happend.
Didn't think much of it as i thought i could just start again with the install, but had no joy. Then somehow in
my panic i have managed to lock the bootloader again really making it difficult to do anything.
As it stands at the moment, i can do the following with the phone.
Can get into the fastboot screen
Cannot get into recovery.
Will start normally and show the powered by android screen then will just sit there as if it was starting (which it doesn't)
I was using the following guide :http://forum.xda-developers.com/showthread.php?t=2788632 for the process.
I must also stress that this isn't the 1st time i have tried to root android phones and have successfully rooted my S2,S3 and note 2.
That being said i have totally rooted this OPO.
I have spent the last 3 days basically reading any thread in this forum with the hope of reversing this cockup
and have tried many but to no avail. Basically road blocked i think by the locked bootloader.
The only thing i haven't tried yet is using a computer with Win xp as Win 7 is a pain in the arse for drivers.
Any of you guys got some idea whether this fixable or should i just give up and bin it? I don't want too and would love to be able to get
it back up running but this has really done my head in.
Cheers
Click to expand...
Click to collapse
I'm assuming that all subsequent attempts to unlock the bootloader again (fastboot oem unlock) are failing?
Transmitted via Bacon
timmaaa said:
Not with a locked bootloader.
Transmitted via Bacon
---------- Post added at 07:09 PM ---------- Previous post was at 07:07 PM ----------
I'm assuming that all subsequent attempts to unlock the bootloader again (fastboot oem unlock) are failing?
Transmitted via Bacon
Click to expand...
Click to collapse
Yeah, thats right timmaaa, no joy at all in unlocking again.
It just hangs on the powered by android screen after hitting enter.
Moatmonster said:
Yeah, thats right timmaaa, no joy at all in unlocking again.
It just hangs on the powered by android screen after hitting enter.
Click to expand...
Click to collapse
Let me search for something that might help, leave it with me.
Transmitted via Bacon
Cheers mate.
What build of CM11S are/were you on?
Transmitted via Bacon
timmaaa said:
What build of CM11S are/were you on?
Transmitted via Bacon
Click to expand...
Click to collapse
Pretty sure it was 38R ?, i definitely updated just after i got the phone in early October.
Moatmonster said:
Pretty sure it was 38R ?, i definitely updated just after i got the phone in early October.
Click to expand...
Click to collapse
Ah, that's a shame, the method I was thinking of won't work since that update. This is it:
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
It relies on you being able to boot a recovery as opposed to actually flashing it, and then flashing a script with that recovery. I'm 99.9% sure that you can't do that since the 38R update though. It's worth a try, connect your phone in fastboot mode and try to boot a recovery (the following command assumes that you have 'openrecovery-twrp-2.8.1.0-bacon.img' in your fastboot folder).
Code:
fastboot boot openrecovery-twrp-2.8.1.0-bacon.img
Like I said, it probably won't work, but it's worth a shot.
Transmitted via Bacon
Will have a crack when i get home, thanks for your help.
No good mate as you said.
Moatmonster said:
No good mate as you said.
Click to expand...
Click to collapse
Bummer. @zephiK, do you have any ideas?
Transmitted via Bacon
Edit: After looking through some oneplus forums, looks like they have tried to issue out a patch for this issue. Have you tried this? I would try it out first and see if it helps. Again, the below one people were really bricked, hope it helps.
I haven't had to use this, and the thread is long, but a very good read. Please go to this thread. A lot of people were able to get their devices working again by using a few tools on windows machines xp win7 and win 8.1. Basically bricked device like the one you are looking at, then installing color OS somehow brought it back to life. The drivers are in chinese, but just clicking next gets them installed correctly. Mostly everyone there is in QHUSB_Bulk mode, not sure if you are or not, but worth a shot.
Hi
can you help me either to put another language into the phone, or help me put cyanongen instead of the color Os i got with the oneplus i bought-
i tried the https://www.youtube.com/watch?v=QDKOEtN9pbo but it fails as soon as i install from sdcard.
i dont know any other method that works.
Thanks a lot!
METAL66 said:
Hi
can you help me either to put another language into the phone, or help me put cyanongen instead of the color Os i got with the oneplus i bought-
i tried the https://www.youtube.com/watch?v=QDKOEtN9pbo but it fails as soon as i install from sdcard.
i dont know any other method that works.
Thanks a lot!
Click to expand...
Click to collapse
Go to my guide thread here:
http://forum.xda-developers.com/showthread.php?t=2839471
Follow Sections 1-4 and then Section 8.
Transmitted via Bacon
Dear Timmaa
after Code:
fastboot oem device-info
It should have a couple of lines there, both with the flag set to true.
Please note: this will erase all user data from your device, it is best to do this before turning your phone on for the first time, otherwise make sure you backup anything important.
the fastboot is still on the screen, how do i move to step 2 ? just remove the cable? force restart or how ?
Are you saying that fastboot isn't working?
Transmitted via Bacon
timmaaa said:
Are you saying that fastboot isn't working?
Transmitted via Bacon
Click to expand...
Click to collapse
i see fastboot in english and chinese on the phone, i do the commands on cmd prompt, but nothing happens to the phone when i finish the steps.
You didn't answer my question though, is fastboot working? Are you getting a response in your command prompt when you enter commands? Try this:
Code:
fastboot devices
What's the result?
Transmitted via Bacon
yes it was working in the cmd, everything was fine, except the step of the .img
now when i start the phone, i have an icon on top saying supersu is ready to root, tap to root.
METAL66 said:
yes it was working in the cmd, everything was fine, except the step of the .img
now when i start the phone, i have an icon on top saying supersu is ready to root, tap to root.
Click to expand...
Click to collapse
Your posts are very vague, it's really difficult to help unless you're going to provide detailed information.
Transmitted via Bacon
ok i will try to make a very detailed answer, sorry. await the answer in few hours.
detailed video of how i did it
timmaaa said:
Your posts are very vague, it's really difficult to help unless you're going to provide detailed information.
Transmitted via Bacon
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=4N0evbwCNgI&feature=youtu.be
hope this works better ?
timmaaa said:
Your posts are very vague, it's really difficult to help unless you're going to provide detailed information.
Transmitted via Bacon
Click to expand...
Click to collapse
did you see my video ?
METAL66 said:
did you see my video ?
Click to expand...
Click to collapse
Yes I got time to watch your video. Everything you're doing is correct, the reason that your attempts to flash a recovery with fastboot failed is because there was a major flaw in my guide, somehow I had left the command incomplete the last time I edited it. I've fixed it now though. So, if you still have the downloaded recovery named as 'recovery.img' the correct command is this:
Code:
fastboot flash recovery recovery.img
The reason you couldn't find the 'update cm recovery' option in Developer Options is because my guide is more aimed at people who have the international model and therefore have CM11S installed on their device, 'update cm recovery' is a CM11S option and so isn't present on ColorOS.
I'm sorry it's taken me so long to get back to you, but thankyou for taking the time to make such a clear and descriptive video to outline the problem you were having. If you have any further questions I'd be happy to help you.
Transmitted via Bacon
timmaaa said:
Yes I got time to watch your video. Everything you're doing is correct, the reason that your attempts to flash a recovery with fastboot failed is because there was a major flaw in my guide, somehow I had left the command incomplete the last time I edited it. I've fixed it now though. So, if you still have the downloaded recovery named as 'recovery.img' the correct command is this:
Code:
fastboot flash recovery recovery.img
The reason you couldn't find the 'update cm recovery' option in Developer Options is because my guide is more aimed at people who have the international model and therefore have CM11S installed on their device, 'update cm recovery' is a CM11S option and so isn't present on ColorOS.
I'm sorry it's taken me so long to get back to you, but thankyou for taking the time to make such a clear and descriptive video to outline the problem you were having. If you have any further questions I'd be happy to help you.
Transmitted via Bacon
Click to expand...
Click to collapse
Thank you timmaa., it worked just few minutes before you sent the answer.
again thanks for your attention.
METAL66 said:
Thank you timmaa., it worked just few minutes before you sent the answer.
again thanks for your attention.
Click to expand...
Click to collapse
Cool, glad you got it sorted out. If you have any questions in future please don't hesitate to ask here:
http://forum.xda-developers.com/showthread.php?t=2839471
Transmitted via Bacon
Thanks, now there are some problems with the network, is this normal? can it be solved?
METAL66 said:
Thanks, now there are some problems with the network, is this normal? can it be solved?
Click to expand...
Click to collapse
What kind of problem? Are you still on ColorOS or are you on CM11S now?
Transmitted via Bacon
timmaaa said:
What kind of problem? Are you still on ColorOS or are you on CM11S now?
Transmitted via Bacon
Click to expand...
Click to collapse
i am now on CM11, i guess, the color os version, is not intended for international sale? internet is not working at all ! ? i mean the sim card internet, the wifi is fine
METAL66 said:
i am now on CM11, i guess, the color os version, is not intended for international sale? internet is not working at all ! ? i mean the sim card internet, the wifi is fine
Click to expand...
Click to collapse
The ColorOS version is the same as the international version apart from missing just one LTE band. Have you double checked your APN settings? Go into Settings/Mobile Network/Access Point Names and make sure they're correct.
Transmitted via Bacon
timmaaa said:
The ColorOS version is the same as the international version apart from missing just one LTE band. Have you double checked your APN settings? Go into Settings/Mobile Network/Access Point Names and make sure they're correct.
Transmitted via Bacon
Click to expand...
Click to collapse
Thanks, it worked perfectly, i dont know why the APN settings were empty, but now it works.
perfect, thanks a lot timmaaa
No problems [emoji3]
Transmitted via Bacon
Hey guys,
I am pretty new to the rooting stuff on the Nexus.
I read the sticky threat from rootSU (http://forum.xda-developers.com/goo...urce-guides-info-threads-linked-read-t2784527) and followed his description. So I installed ADB and fastboot through the "15 sec. installer" (http://forum.xda-developers.com/showthread.php?t=2588979).
So fast so good, everything went fine. But as I tried to "check" if ADB and fastboot are recognizing my device with the command "adb devices" and "fastboot devices" in cmd, I got some strange output (look at the picture).
How can it be that ADB "sees" my device and fastboot not? What I did wrong there?
(I didn't installed the drivers with the 15 sec tool; when I plugged in my device to the computer, it downloaded the drivers itself)
Any help would be very appreciated!
Follow the next step on my thread and install the naked drivers
Okay thank you!
I'll try it tonight and report back.
I also thought of a problem with the drivers, but I thought that I messed up with installing ADB and fastboot somehow, because ADB could recognize my device.
One question again: When I uninstall the Nexus 5 drivers and I reconnect my phone to the pc, it download the driver itself.. How can I stop that to install the naked drivers?
Blackbox421 said:
Okay thank you!
I'll try it tonight and report back.
I also thought of a problem with the drivers, but I thought that I messed up with installing ADB and fastboot somehow, because ADB could recognize my device.
One question again: When I uninstall the Nexus 5 drivers and I reconnect my phone to the pc, it download the driver itself.. How can I stop that to install the naked drivers?
Click to expand...
Click to collapse
Remember - adb ONLY works when Android is booted up or you're in recovery, fastboot ONLY works when you're in the bootloader
EddyOS said:
Remember - adb ONLY works when Android is booted up or you're in recovery, fastboot ONLY works when you're in the bootloader
Click to expand...
Click to collapse
Damn, thats it! I am so dumb! I don't know how I could forget that.. I read it some hours ago.
After I went into bootloader mode, fastboot recognized my device!
Thanks a lot guys, now I can go to the next step to root my device! =)
Btw.. another question, which is offtopic - does it makes a difference to root KitKat or Lollipop? I guess the guides around here are all made for KitKat and I don't want to mess up. :/ Thx!
Blackbox421 said:
Damn, thats it! I am so dumb! I don't know how I could forget that.. I read it some hours ago.
After I went into bootloader mode, fastboot recognized my device!
Thanks a lot guys, now I can go to the next step to root my device! =)
Btw.. another question, which is offtopic - does it makes a difference to root KitKat or Lollipop? I guess the guides around here are all made for KitKat and I don't want to mess up. :/ Thx!
Click to expand...
Click to collapse
@rootSU has posted some new guides on rooting Lollipop, so best read his threads in the General section
To root Lollipop you have to use Chainfire Auto Root. There is extra security in Lollipop that keeps the old root method from KitKat from working.
Oh I see..thats annoying. But thank you for your answers! I guess I'll read those threads. =)
Btw.. Can you guys tell me if I understood everything..:
To go back to the official 4.4.4., I don't have to root my device, right? I "only" have to unlock my bootloader and flash the official factory image through fastboot. And afterwards I could root my device using the guides around here on xda.
Blackbox421 said:
Oh I see..thats annoying. But thank you for your answers! I guess I'll read those threads. =)
Btw.. Can you guys tell me if I understood everything..:
To go back to the official 4.4.4., I don't have to root my device, right? I "only" have to unlock my bootloader and flash the official factory image through fastboot. And afterwards I could root my device using the guides around here on xda.
Click to expand...
Click to collapse
That's correct!
EddyOS said:
That's correct!
Click to expand...
Click to collapse
Oh, actually thats all I wanted! =)
On my old Samsung Galaxy Ace you had to root your device first, before you even could install another stock rom, thats why I thought it would be the same for the Nexus 5.
Thanks alot, I'll save my data on my PC now and start with the "downgrading"!
Blackbox421 said:
Oh, actually thats all I wanted! =)
On my old Samsung Galaxy Ace you had to root your device first, before you even could install another stock rom, thats why I thought it would be the same for the Nexus 5.
Thanks alot, I'll save my data on my PC now and start with the "downgrading"!
Click to expand...
Click to collapse
It's all very easy with a Nexus device
EddyOS said:
It's all very easy with a Nexus device
Click to expand...
Click to collapse
Yeah I think I got it now. I unlocked my bootloader and flashed the official 4.4.4. factory image from the google developers website. Afterwards I booted into the stock recovery and wiped data/factory reset and reboot. Everything is fine now!
Thank you for your help! Learned a lot of basic understandings.
Jnewell05 said:
To root Lollipop you have to use Chainfire Auto Root. There is extra security in Lollipop that keeps the old root method from KitKat from working.
Click to expand...
Click to collapse
There are multiple methods. Cf auto root is just one of them.
I documented all methods in general. There's a link to my thread from "sticky roll-up in general
rootSU said:
There are multiple methods. Cf auto root is just one of them.
I documented all methods in general. There's a link to my thread from "sticky roll-up in general
Click to expand...
Click to collapse
Huh, I thought the methods from your thread would be only for KitKat
Blackbox421 said:
Huh, I thought the methods from your thread would be only for KitKat
Click to expand...
Click to collapse
I usualy root my Nexus by booting into a custom recovery (TWRP), flash the latest superSU.zip and any mod i want and reboot/done That way i keep my stock recovery.
I have a problem with rooting my Oneplus One. It all goes well until twrp needs to start.
My screen is all black and its not reacting to anything. I have to wait till the battery is empty to turn off.
Also when its in this stage my laptop gives me an error: 'USB Device is Not Recognized'.
I hope you can help me.
Did you check the md5 of the recovery image before flashing it? Please copy/paste the text from the command prompt on a flash attempt.
Transmitted via Bacon
Can you access fastboot mode?
It all goes well until i have to restart into bootmode where i have to flash su.
Hard reset wont work when the screen turns black.
hazefetish said:
It all goes well until i have to restart into bootmode where i have to flash su.
Hard reset wont work when the screen turns black.
Click to expand...
Click to collapse
That doesn't make sense, what do you mean by bootmode? And you didn't answer either of my questions, I asked those for a reason, if you're not going to provide the information that's needed it's pretty much impossible to help you.
Transmitted via Bacon
You can always turn off your phone by holding the power button for 10 seconds.
Try fastbooting the latest TWRP. => http://techerrata.com/browse/twrp2/bacon
It's possible that you have flashed a corrupted file or even a TWRP for a different device.
Alright
Ive tried it again.
At the moment it should boot into twrp the screen turns black.
It shows up as normal adb device, its still connected but my screen wont show me a picture.
I did it with Oneplus One Toolkit 2.0.
Did everything the steps told me.
You still haven't answered my questions...
Transmitted via Bacon
I didnt check the md5 hash but due to the tool its the right iso.
And i cant copy something out of the command promt because it closes automatically.
When i did it the command promt way i didnt even get a message that something failed.
Stop using a tool to do it and do it yourself. It's simple. I have detailed instructions in my guide thread.
Transmitted via Bacon
timmaaa said:
Stop using a tool to do it and do it yourself. It's simple. I have detailed instructions in my guide thread.
Transmitted via Bacon
Click to expand...
Click to collapse
I have done it myself and it didnt work...
As i said in my previous post
Thread can be closed i renounce rooting my device.
hazefetish said:
I have done it myself and it didnt work...
As i said in my previous post
Thread can be closed i renounce rooting my device.
Click to expand...
Click to collapse
If you actually tried to work with us in solving your problem you'd have it done in no time, this is the easiest phone in the world to root. And at no point did you mention doing it yourself, you've only mentioned using a tool.
Transmitted via Bacon
timmaaa said:
If you actually tried to work with us in solving your problem you'd have it done in no time, this is the easiest phone in the world to root.
Transmitted via Bacon
Click to expand...
Click to collapse
Dude what is your problem?
I said everything i know.
I tried it several times with the tool and command promt.
I did i the exact same way and it wasnt working.
Then you come here, behaving like a pro in this things, turns out: no solution from you.
Just because it worked for you that easy doesnt mean it have to be the same for my opo.
Electronics arent always predictable so why cant it be that something on my opo doesnt work while on yours its working?
I refuse to work with you.
When i did it the command promt way i didnt even get a message that something failed.
Click to expand...
Click to collapse
Plus, you should always check the md5 of any file you're going to flash to your device. It's possible you have a corrupt download. If you flash the recovery yourself the command window won't choose automatically, then you can copy/paste the text here. Bit the first thing I'd be doing is checking the md5.
Transmitted via Bacon
---------- Post added at 08:18 AM ---------- Previous post was at 08:15 AM ----------
hazefetish said:
Dude what is your problem?
I said everything i know.
I tried it several times with the tool and command promt.
I did i the exact same way and it wasnt working.
Then you come here, behaving like a pro in this things, turns out: no solution from you.
Just because it worked for you that easy doesnt mean it have to be the same for my opo.
Electronics arent always predictable so why cant it be that something on my opo doesnt work while on yours its working?
I refuse to work with you.
Click to expand...
Click to collapse
My problem is you came here asking for help, and then it took me asking three times over the course of 19 hours for you to answer me. We need this information in order to help you, which I'm trying to do. Electronics are predictable, this process is predictable, but you need to go about it the right way (checking the md5, flashing manually with fastboot). Now, have you only tried to flash TWRP or have you tried ow odd the other recoveries too?
Transmitted via Bacon
timmaaa said:
Plus, you should always check the md5 of any file you're going to flash to your device. It's possible you have a corrupt download. If you flash the recovery yourself the command window won't choose automatically, then you can copy/paste the text here. Bit the first thing I'd be doing is checking the md5.
Transmitted via Bacon
---------- Post added at 08:18 AM ---------- Previous post was at 08:15 AM ----------
My problem is you came here asking for help, and then it took me asking three times over the course of 31 hours for you to answer me. We need this information in order to help you, which I'm trying to do. Electronics are predictable, this process is predictable, but you need to go about it the right way (checking the md5, flashing manually with fastboot). Now, have you only tried to flash TWRP or have you tried ow odd the other recoveries too?
Transmitted via Bacon
Click to expand...
Click to collapse
I didnt say electronics arent predictable per se. But there are situations where you cant comprehend what went wrong or why it went wrong.
hazefetish said:
I didnt say electronics arent predictable per se. But there are situations where you cant comprehend what went wrong or why it went wrong.
Click to expand...
Click to collapse
We can though, we can find out what went wrong by investigating. I'm trying to help you, but I need this information:
Check the md5, let me know if it matches or not.
Make another manual attempt and copy the text here.
And answer whether you've tried any recovery other than TWRP.
Transmitted via Bacon
timmaaa said:
Stop using a tool to do it and do it yourself. It's simple. I have detailed instructions in my guide thread.
Transmitted via Bacon
Click to expand...
Click to collapse
Listen to Timmaaa.... His guides & other experts from XDA-OPO forums has helped me understand a lot of things about rooting, flashing & other areas.........
Don't be arrogant toward a person trying to help. As he (timmaaa) said its very simple, You need to run about 2 commands and it will take about 5mins. I can make you a batch file if you don't even want to do that.
skyguy126 said:
Don't be arrogant toward a person trying to help. As he (timmaaa) said its very simple, You need to run about 2 commands and it will take about 5mins. I can make you a batch file if you don't even want to do that.
Click to expand...
Click to collapse
It's a nice idea, very generous, but I don't think it's the right way to go, nobody learns anything when using an automated process.
Transmitted via Bacon
Is it possible to root one plus one, without deleting any data and apps from it? I just want root access but don't want any custom rom.
yes, of course..
root doesn't delete any of your data
senaferdy79 said:
yes, of course..
root doesn't delete any of your data
Click to expand...
Click to collapse
Thanks for that. How can I do that?
#newtorooting
senaferdy79 said:
yes, of course..
root doesn't delete any of your data
Click to expand...
Click to collapse
That isn't technically true. In order to get root you must have a custom recovery installed. In order to install a custom recovery you must unlock the bootloader. Unlocking the bootloader wipes the device.
---------- Post added at 08:13 PM ---------- Previous post was at 08:10 PM ----------
sourabhkejriwal said:
Thanks for that. How can I do that?
#newtorooting
Click to expand...
Click to collapse
Sorry you got your hopes up, but the other poster isn't right. As per my reply to him you need to unlock your bootloader first, which is going to wipe your device. I'd suggest backing up any files that you have that are important to you. As for your apps and settings, you'll have to set them up again afterwards. Go to my guide thread here:
http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
You need to follow (in order) sections 1, 2, 3, and 4. This will give you root access on your stock ROM. You should also follow section 10, it's very important that you make a backup of your EFS partition.
timmaaa said:
That isn't technically true. In order to get root you must have a custom recovery installed. In order to install a custom recovery you must unlock the bootloader. Unlocking the bootloader wipes the device.[
Click to expand...
Click to collapse
So are you saying all the many how to's that tell you that you can skip installing recover are wrong? Apparently, I don't have enough posts yet to create a link but I've seen posts here on XDA that say other wise and the one I have in front of me at the moment is from ibtimes . com titled "how-root-oneplus-one-install-twrp-recovery-1450708"
Their "Step-7" reads
Step-7: If you want to root the phone without installing TWRP recovery, type the following command
fastboot boot twrp.img
Click to expand...
Click to collapse
I guess the real question being, why would you need a custom recovery?
pdhx said:
So are you saying all the many how to's that tell you that you can skip installing recover are wrong? Apparently, I don't have enough posts yet to create a link but I've seen posts here on XDA that say other wise and the one I have in front of me at the moment is from ibtimes . com titled "how-root-oneplus-one-install-twrp-recovery-1450708"
Their "Step-7" reads
I guess the real question being, why would you need a custom recovery?
Click to expand...
Click to collapse
You're looking at outdated information. They used to be correct, but now they are wrong. This is because you can no longer use the fastboot boot recovery.img command with a locked bootloader. In fact, that functionality was removed quite some time ago.
You need a custom recovery because that's how you flash SuperSU to get root. There's no way around it.
Transmitted via Bacon
The default recovery will only flash cm signed zip, which is another reason for needing a custom recovery. That method you mention at ibtimes meant that it would allow you to, for one boot cycle, do a "live boot" of twrp
Sent From Lollipopified Bacon Goodness!
But how is anything going to be written to the system partition if it is locked ?
timmaaa said:
You're looking at outdated information. They used to be correct, but now they are wrong. This is because you can no longer use the fastboot boot recovery.img command with a locked bootloader. In fact, that functionality was removed quite some time ago.
You need a custom recovery because that's how you flash SuperSU to get root. There's no way around it.
Click to expand...
Click to collapse
Ugh, was afraid of that, you might want to add a comment to that effect to your guide....
Would have been nice to just add a setting to the default recovery to allow you to toggle whether you need a signed zip or not. Sucks that I could root my SGS III (which is far less hacker friendly than the One) without wiping it but I can't do that for the One, all i want is root for the moment. However, after playing around some more I'm getting stick before I even get that far; I can get ADB to find the device but when I adb reboot bootloader I cannot get fastboot to find the device. I've tried multiple drivers, different USB ports. When my One goes into fastboot the screen seems awfully dim, almost like it hasn't completely initialized, is that normal? And if so, any suggestions on why I can get adb to work but not fastboot?
pdhx said:
Ugh, was afraid of that, you might want to add a comment to that effect to your guide....
Would have been nice to just add a setting to the default recovery to allow you to toggle whether you need a signed zip or not. Sucks that I could root my SGS III (which is far less hacker friendly than the One) without wiping it but I can't do that for the One, all i want is root for the moment. However, after playing around some more I'm getting stick before I even get that far; I can get ADB to find the device but when I adb reboot bootloader I cannot get fastboot to find the device. I've tried multiple drivers, different USB ports. When my One goes into fastboot the screen seems awfully dim, almost like it hasn't completely initialized, is that normal? And if so, any suggestions on why I can get adb to work but not fastboot?
Click to expand...
Click to collapse
The one's bootloader is not like a nexus one where you can at least reboot recovery etc, once it boots thats it
what do get when you type fastboot devices ?
bombadier said:
The one's bootloader is not like a nexus one where you can at least reboot recovery etc, once it boots thats it
Click to expand...
Click to collapse
Which seems to be somewhat limiting for such an otherwise developer friendly device?
bombadier said:
what do get when you type fastboot devices ?
Click to expand...
Click to collapse
Nada, nothing, nil. however, "adb devices" works fine... WTF?
pdhx said:
Which seems to be somewhat limiting for such an otherwise developer friendly device?
Nada, nothing, nil. however, "adb devices" works fine... WTF?
Click to expand...
Click to collapse
Point one was just to say there is not anything really you can do in the bootloader, being able to reboot to recovery etc is actually a handy feature
Try a different fastboot.exe ? if you say that adb works perfectly then there has to be something wrong with your fastboot binary
I have attached my one,download and change the name back to .exe and see what happens
Going to need more info in order to help
bombadier said:
Point one was just to say there is not anything really you can do in the bootloader, being able to reboot to recovery etc is actually a handy feature
Try a different fastboot.exe ? if you say that adb works perfectly then there has to be something wrong with your fastboot binary
I have attached my one,download and change the name back to .exe and see what happens
Going to need more info in order to help
Click to expand...
Click to collapse
Fair point about bootloader, what I don't get is why they forced you to have to do the unlock to root? All I started out wanting to do was install Titanium and run a Nandroid or two. Guess if I'm going to have to wipe I guess I may end up installing a Lollipop ROM. However, I still can't get there. The fast boot you supplied gives the same problem. I was running the latest fastboot from the Android SDK and your's appears to be the same (though I haven't done a binary compare). As far as I can tell that leaves the device drivers, the laptop, or the phone itself. I'm running Win 7 SP 1 64 bit and I've tried various drivers including the Samsung the Google generic and they make no difference. Not sure how they would since adb works but I've seen some suggestions that drivers can be finicky in this regard.
What else can I tell you that might help?
Seems since I can get into the recovery that comes with the phone I could maybe get a works around somehow?
pdhx said:
Fair point about bootloader, what I don't get is why they forced you to have to do the unlock to root? All I started out wanting to do was install Titanium and run a Nandroid or two. Guess if I'm going to have to wipe I guess I may end up installing a Lollipop ROM. However, I still can't get there. The fast boot you supplied gives the same problem. I was running the latest fastboot from the Android SDK and your's appears to be the same (though I haven't done a binary compare). As far as I can tell that leaves the device drivers, the laptop, or the phone itself. I'm running Win 7 SP 1 64 bit and I've tried various drivers including the Samsung the Google generic and they make no difference. Not sure how they would since adb works but I've seen some suggestions that drivers can be finicky in this regard.
What else can I tell you that might help?
Seems since I can get into the recovery that comes with the phone I could maybe get a works around somehow?
Click to expand...
Click to collapse
They're "forcing" you to unlock the bootloader in order to root the device because that's the universally accepted standard (unlock bootloader, install custom recovery, flash root). Some devices have super secure bootloaders and that's why you end up needing to use hacks to get those devices rooted, but that isn't the normal way to go about it. Anyway, there's no advantage to leaving the bootloader at all. There's also no disadvantage to unlocking the bootloader at all. You might say that the fact that the device is wiped during the unlocking process is a disadvantage, but that fact is very well documented both here, on the OnePlus forums, and pretty much any other reputable tech site that mentions unlocking the bootloader on this phone. The point to that last sentence? It pays to research a device thoroughly before buying it, or before using it, the wiping of the device is no issue at all if you do it when you receive the phone (prior to using it), like many people have. But in your situation you're just going to have to backup any important media from the phone prior to unlocking.
Anyway, on to your fastboot issue. Exactly which drivers do you have installed on your PC? Do you have any other phone drivers or software installed on the PC? And do you have access to another PC in case the one you're using is the source of the issue?
Got it, 27th try (give or take) is the charm.... Had to use USBdeview and uninstall the Google and the Qualcomm drivers. Reinstalled the Google drivers (after a reboot) and got it to work. Guess I could have figured that out from dev manager by watching what drivers got activated while fastboot was active but nothing ever jumped out at me as an obvious culprit.
Interesting to note that TWRP now automatically prompts you to install SuperSU if you reboot after installing it. Maybe it found the zip but either way, nice touch!
Now to go and decide what ROM to install....
Thanks for your help!
I would suggest temasek unofficial cm12 ROM. Been using it pretty much as a daily driver since version 1.something of the ROM and no problems. At this point it's been almost a month of not having to boot into my cm11s ROM lol. I use it with AK kernel, seems like a good match cuz both devs are working together looks like. Flash AK ukm special edition after flashing his kernel and install synapse from play store if you want to play around with settings of the kernel
Sent From Lollipopified Bacon Goodness!
zenix23456 said:
I have been using AnyRooter for months and it is quite good to root OnePlus phones.
Click to expand...
Click to collapse
Except the Oneplus One.