Hi, can someone point me into the right process to root this phone with latest SuperSU binaries and latest TWRP for this device? I own a 6045Y. Thanks in advance.
Edit: while waiting for an answer i tried the most basic task: unlocking the bootloader. Unfortunately, i get this error:
Code:
D:\Desktop\adb>fastboot -i 0x1bbb oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.003s
The device is brand new, i opened the box this morning.
Band 12 needed for T-Mobile
The same issue here.
I have got 6.0.1 over OTA update on my 6045. I am looking to install TWRP on it, root the phone, and then flash the old radios.
Please advise me how to install TWRP on 6.0.1.
The answer was in a thread on the same page as yours. Something along the lines of "now that I have marshmallow, how do I root?".
You need to learn to use the search.
http://forum.xda-developers.com/showpost.php?p=67644383&postcount=486
I forgot to mention in the OP, i'm not on Marshmallow. I'm still on 5.0.2-010 09. I supposed it being a 6045Y and coming fresh out of the box you guys figured out i couldn't have been on MM yet. But anyway it still seems strange that they locked those fastboot commands... Am i doing anything wrong? I should be able to unlock bootloader just entering the right command while in fastboot mode right?
plumbe0 said:
I forgot to mention in the OP, i'm not on Marshmallow. I'm still on 5.0.2-010 09. I supposed it being a 6045Y and coming fresh out of the box you guys figured out i couldn't have been on MM yet. But anyway it still seems strange that they locked the bootloader... Am i doing anything wrong? I should be able to unlock bootloader just entering the right command while in fastboot mode right?
Click to expand...
Click to collapse
The bootloader always comes locked. It's nothing new. Go to this thread by DallasCZ http://forum.xda-developers.com/idol-3/general/guide-unlock-bootloader-root-alcatel-t3161878 and follow the steps completely. Don't skip any.
Unfortunately I have got installed the OTA (factory) 6.0.1 ROM on my idol 3. Those steps would not on the device. There is a thread referring fastboot commands being disabled on 6.0.1.
I have downloaded Panasonic Firmware Eluga switch and also ADB drivers, but it could not find my device.
kingoftheafro said:
The bootloader always comes locked. It's nothing new. Go to this thread by DallasCZ http://forum.xda-developers.com/idol-3/general/guide-unlock-bootloader-root-alcatel-t3161878 and follow the steps completely. Don't skip any.
Click to expand...
Click to collapse
I don't mean to be rude or anything, but haven't you read my first post? I can't unlock the bootloader because entering the commands in the guide gives me an error, while unlocking the bootloader on 5.0.2 should be possible (already did it on an idol3 of my friend).
plumbe0 said:
I don't mean to be rude or anything, but haven't you read my first post? I can't unlock the bootloader because entering the commands in the guide gives me an error, while unlocking the bootloader on 5.0.2 should be possible (already did it on an idol3 of my friend).
Click to expand...
Click to collapse
I did read your first post. Since there can be a plethora of issues you can be having such as, not having usb debugging enabled, making sure your phone has set permissions for adb on your computer to access phone, making sure your drivers are correctly installed, etc I decided to send you the link that would pretty much tell you everything just to be safe. So I can pretty much expect you didn't read the whole thread so why not try the 3 things I stated and see if that solves your issue.
kingoftheafro said:
I did read your first post. Since there can be a plethora of issues you can be having such as, not having usb debugging enabled, making sure your phone has set permissions for adb on your computer to access phone, making sure your drivers are correctly installed, etc I decided to send you the link that would pretty much tell you everything just to be safe. So I can pretty much expect you didn't read the whole thread so why not try the 3 things I stated and see if that solves your issue.
Click to expand...
Click to collapse
USB Debugging is active, i have the drivers installed, PC has been secured access to USB debug. Still get the error.
plumbe0 said:
USB Debugging is active, i have the drivers installed, PC has been secured access to USB debug. Still get the error.
Click to expand...
Click to collapse
Interesting. I've never come across that issue so I'm a bit stumped and haven't a way currently to replicate said issue. I'm completely at a loss. Unless someone else had this issue or someone else has more experience with this I don't know what else to recommend.
It turns out that the bootloader is unlocked even if adb says that the OEM unlock is not available. Tried with 3 different devices on latest firmware (5.0.2-010 09) and i managed to get root and twrp even if fastboot -i 0x1bbb oem device-info says the bootloader is locked.
Only you Root with systemless....follow instructions
write in twrp terminal?
echo SYSTEMLESS=true >> /data/.supersu
flash the supersu zip and then wipe cache and davik cache...
Alek Dev said:
Only you Root with systemless....follow instructions
write in twrp terminal?
echo SYSTEMLESS=true >> /data/.supersu
flash the supersu zip and then wipe cache and davik cache...
Click to expand...
Click to collapse
What? I couldn't understand a thing of what you've said.
Related
Hello everyone!
I need some help rooting my tf300t, because what I've read here and there was somewhat useless, since everyone sais different stuff. For first I'd like to ask for your help in clarifying which one is first. I have read guides in which rooting was first than pushing the recovery, and I have read ones in which fasbooting recovery was the first thing to do, and than flashing su. I have tried both methods, with no luck. When I try to fastboot twrp onto my device, it sais 'waiting for device'. I read that this means fastboot is not properly configured, but I am an administrator on my PC and I have the proper drivers, since adb reboot-bootloader works. So thats for flashing twrp first. Then rooting first. I tried with motochopper, but that does no work on 10.6.1.27.5. So I tried pushing root files manually, but when adb shell /data/local/temp, it sais failure. So if you could help me, of what did I do wrong, I'd greatly appreciate it.
Shad0w32 said:
Hello everyone!
I need some help rooting my tf300t, because what I've read here and there was somewhat useless, since everyone sais different stuff. For first I'd like to ask for your help in clarifying which one is first. I have read guides in which rooting was first than pushing the recovery, and I have read ones in which fasbooting recovery was the first thing to do, and than flashing su. I have tried both methods, with no luck. When I try to fastboot twrp onto my device, it sais 'waiting for device'. I read that this means fastboot is not properly configured, but I am an administrator on my PC and I have the proper drivers, since adb reboot-bootloader works. So thats for flashing twrp first. Then rooting first. I tried with motochopper, but that does no work on 10.6.1.27.5. So I tried pushing root files manually, but when adb shell /data/local/temp, it sais failure. So if you could help me, of what did I do wrong, I'd greatly appreciate it.
Click to expand...
Click to collapse
First make sure that you have unlocked your bootloader (text in the upper right corner of boot screen). What I did first was flash TWRP from ADB. In your case, you would flash the stock ROM, and then flash SU.
cmendonc2 said:
First make sure that you have unlocked your bootloader (text in the upper right corner of boot screen). What I did first was flash TWRP from ADB. In your case, you would flash the stock ROM, and then flash SU.
Click to expand...
Click to collapse
I know I'm unlocked sorry for not mentioning that, though even that was strange, because the unlock device app should have wiped the memory, but it didn't, and still unlocked. But I don't exactly understand what you mean by flashing the stock ROM, then SU. And if you mean that do that with twrp, I can't because fastboot flash recovery twrp.blob just waits for device. Is there another method which I can flash it with? Thanks in advance
Shad0w32 said:
I know I'm unlocked sorry for not mentioning that, though even that was strange, because the unlock device app should have wiped the memory, but it didn't, and still unlocked. But I don't exactly understand what you mean by flashing the stock ROM, then SU. And if you mean that do that with twrp, I can't because fastboot flash recovery twrp.blob just waits for device. Is there another method which I can flash it with? Thanks in advance
Click to expand...
Click to collapse
If it says "waiting for device," your PC is not communicating with the tab. What Windows version do you use? Does "fastboot device" command from fastboot mode on tab return any serial number? It should show a serial number before you can flash TWRP onto the tab. And where did you read that unlocking the device would wipe the memory?
Get fastboot to work first, then you can flash whatever. Otherwise, if you're on stock recovery, try loading the rom zip file onto your sd card and flash it using RCK option. If you have no idea what I'm talking about, read first, so you don't brick your tab just because you have no idea what the heck you're doing.
graphdarnell said:
If it says "waiting for device," your PC is not communicating with the tab. What Windows version do you use? Does "fastboot device" command from fastboot mode on tab return any serial number? It should show a serial number before you can flash TWRP onto the tab. And where did you read that unlocking the device would wipe the memory?
Get fastboot to work first, then you can flash whatever. Otherwise, if you're on stock recovery, try loading the rom zip file onto your sd card and flash it using RCK option. If you have no idea what I'm talking about, read first, so you don't brick your tab just because you have no idea what the heck you're doing.
Click to expand...
Click to collapse
For first, I downgraded my device, so I could root it with motochopper. Then I flashed recovery with the way explained here:http://forum.xda-developers.com/showthread.php?t=1845377
Now twrp seems to be working, i can start it, but it cant mount anything, so i cant flash anything from the device. Both 2.5 and 2.4.4 does this. Goo manager cant find a recovery for this device, so i cant use that either. Fastboot still cant see my tab. Im on windows 7, with proper drivers
Nevermind my stupidity, I installed the wrong recovery, not the one for the 4.2 bootloader. By now I'm a proud owner of a tf300t with cyanogenmod on it Thank you both though, for trying to help
Hello all,
I'm working on my tf700t, attempting to install TWRP 2.7.1.1. I'm not running into much success.
I've used fastboot, but it is giving me the error "FAILED (remote: (InvalidState))"
I've also attempted to use the TWRP Manager app on the Play store. When I try to use the "Install TWRP" option, it gives me the error "This is somewhat embarrassing, isn't it? It seems we can't find what you're looking for."
I haven't tried the manual install from img file option, because I haven't found a TWRP img file (just .blob). I have done a fair bit of searching, but I'm not ruling out that the problem exists between the chair and keyboard.
As things stand, I've already used fastboot to erase the previous bootloader so that I was working with a clean start, as recommended by Demkantor's guide. So my Infinity is still booting in stock fine, but it has no bootloader left Fastboot does still seem to work, I should note.
Any ideas? I'd be happy to provide screenshots or work to answer any questions people may have, in order to get this thing working.
Thank you in advance!
Asymptotex said:
Hello all,
I'm working on my tf700t, attempting to install TWRP 2.7.1.1. I'm not running into much success.
I've used fastboot, but it is giving me the error "FAILED (remote: (InvalidState))"
I've also attempted to use the TWRP Manager app on the Play store. When I try to use the "Install TWRP" option, it gives me the error "This is somewhat embarrassing, isn't it? It seems we can't find what you're looking for."
I haven't tried the manual install from img file option, because I haven't found a TWRP img file (just .blob). I have done a fair bit of searching, but I'm not ruling out that the problem exists between the chair and keyboard.
As things stand, I've already used fastboot to erase the previous bootloader so that I was working with a clean start, as recommended by Demkantor's guide. So my Infinity is still booting in stock fine, but it has no bootloader left Fastboot does still seem to work, I should note.
Any ideas? I'd be happy to provide screenshots or work to answer any questions people may have, in order to get this thing working.
Thank you in advance!
Click to expand...
Click to collapse
Lots of questions...
If you refer to this guide: http://forum.xda-developers.com/showthread.php?t=2277112
it is NOT specific for this tablet. You can follow the general instructions to set up adb/fastboot on your PC, but that's it. The rest will not work as described on this tablet.
Did you unlock the bootloader with the Asus unlock tool?
You did not erase your bootloader. The tablet would not boot without one. So what did you do?
IF your bootloader is unlocked you either do not have the correct drivers installed or you are trying this on a USB 3.0 port or you're not running the command as administrator or.... something else...
You may want to check out this:
http://forum.xda-developers.com/showthread.php?t=2688891
As Bernd says sounds to me like you haven't unlocked the bootloader yet.
I am having the same problem as Asymptotex in regard to TWRP Manager when clicked on install TWRP. I know my bootloader is unlocked because it says so in the upper left corner when turned on.
ils01 said:
I am having the same problem as Asymptotex in regard to TWRP Manager when clicked on install TWRP. I know my bootloader is unlocked because it says so in the upper left corner when turned on.
Click to expand...
Click to collapse
Use fastboot. It is worth it to get it working. I guarantee it ?
berndblb said:
Use fastboot. It is worth it to get it working. I guarantee it ?
Click to expand...
Click to collapse
Thank you. Was looking into an easy and idiot proof way.
Hi!
I have a serious problem here. I offered to try and fix a friend's HTC One SV (4.2.2 Jelly bean). His battery died a few days ago, everything was working fine before that. He charged the phone and tried turning it on, but now it gets stuck on the HTC One welcome screen. (I've added a photo of the bootloader screen as well) The phone is not rooted. I've tried everything - clearing cache, recovery mode, factory reset.. Nothing helps. While researching for solutions, I stumbled upon a post where they said that if it were rooted, a custom recovery or RUU would be possible.
Since I am a bit of a newbie to rooting and hacking in general, then I'd like to ask if it's possible to root the damn thing now that it's not turning itself on properly and unlock the bootloader so I could flash a new ROM for example. Will it do any harm? Do you have any suggestions?
P.S.
Taking it back to the shop is an option and I am aware that warranty will void once it's unlocked. Despite this, we're willing to give it a try.
Thanks in advance.
I'm a bit confused, about that "Security Warning" on the picture. Not normal at all!
But if you really want to root, unlock your bootloader at htcdev.com.
Follow the steps, they provide a guide on their website, how to unlock.
old.splatterhand said:
I'm a bit confused, about that "Security Warning" on the picture. Not normal at all!
But if you really want to root, unlock your bootloader at htcdev.com.
Follow the steps, they provide a guide on their website, how to unlock.
Click to expand...
Click to collapse
Turned the phone on and went to the bootloader, the security warning is gone. That's good, I assume? What about this ***tampered*** part?
raisinette said:
Turned the phone on and went to the bootloader, the security warning is gone. That's good, I assume? What about this ***tampered*** part?
Click to expand...
Click to collapse
It seems the phone was unlocked/S-off already, and the one who locked it back to stock forgot to reset the Tampered flag.
old.splatterhand said:
It seems the phone was unlocked/S-off already, and the one who locked it back to stock forgot to reset the Tampered flag.
Click to expand...
Click to collapse
That can't be. He is the first owner and hasn't touched it in any way.
Tampered appears only after unlocking the bootloader.
Maybe a refurbished device!?!
old.splatterhand said:
Tampered appears only after unlocking the bootloader.
Maybe a refurbished device!?!
Click to expand...
Click to collapse
Ah, yes! I completely forgot about that. He had its power button repaired a few months, perhaps the tech guys did something with it.
Will this change anything?
No, not really. You need to unlock at htcdev.com.
Thats your first step.
old.splatterhand said:
No, not really. You need to unlock at htcdev.com.
Thats your first step.
Click to expand...
Click to collapse
I've been trying to do that for the past 2 days, but I'm stuck at step 5 - when I type in cmd ''fastboot oem get_identifier_token'', it says ''fastboot is not recognized as an interal or external command, operable program or batch file''. When I clicked on the fastboot.exe, it said something like adbwinapi.dll is missing. Downloaded that, the error was gone.
I've googled for solutions and so far none of them have worked. What could be wrong?
raisinette said:
I've been trying to do that for the past 2 days, but I'm stuck at step 5 - when I type in cmd ''fastboot oem get_identifier_token'', it says ''fastboot is not recognized as an interal or external command, operable program or batch file''. When I clicked on the fastboot.exe, it said something like adbwinapi.dll is missing. Downloaded that, the error was gone.
I've googled for solutions and so far none of them have worked. What could be wrong?
Click to expand...
Click to collapse
Do you have htc drivers installed on your pc?
old.splatterhand said:
Do you have htc drivers installed on your pc?
Click to expand...
Click to collapse
I have HTC Sync Manager. The drivers should come along with that, or not?
EDIT: Something odd happened - the phone started bootlooping, so I did a factory reset and then a red text appeared saying ''this build is for development purposes only.... etc''. I have not started unlocking the phone, it was simply connected to the usb while the bootloader was open. After the hard reset it does not bootloop anymore, but it is still stuck on the welcome screen. Thought it may be important.
I don't know, what happened to your device. But you need to solve this fastboot issue on your pc to proceed.
Also check, if the bootloader still is locked.
old.splatterhand said:
I don't know, what happened to your device. But you need to solve this fastboot issue on your pc to proceed.
Also check, if the bootloader still is locked.
Click to expand...
Click to collapse
I finally got my bootloader unlocked - it turns out Windows 8.1 was the problem. I couldn't manually install any drivers, so I refreshed my Windows back to 8.0, that helped.
Now, I'd like to root it and flash a custom rom to see if it helps me get out of the stuck HTC screen, but every rooting guide requires USB debugging to be enabled. How can I do that if I can't access the settings, because the phone won't turn on?
You can boot into bootloader, do that. Plug your phone to the pc and make sure your phone is in fastboot (usb) mode, not in hboot mode.
Download this three things:
- http://download.chainfire.eu/supersu
(copy to sdcard of your phone)
- the recovery from first post of this thread http://forum.xda-developers.com/showthread.php?p=41456540#post41456540
(copy to the folder on your pc where your fastboot.exe is)
this stock rom for your variant (or another rom for your variant http://forum.xda-developers.com/showthread.php?t=2512742
(copy to sdcard of your phone)
Follow the "How to" in recovery thread to flash recovery, then follow the "How to" in the rom thread to flash the rom from recovery and at last step flash supersu.zip from recovery.
old.splatterhand said:
You can boot into bootloader, do that. Plug your phone to the pc and make sure your phone is in fastboot (usb) mode, not in hboot mode.
Download this three things:
- http://download.chainfire.eu/supersu
(copy to sdcard of your phone)
- the recovery from first post of this thread http://forum.xda-developers.com/showthread.php?p=41456540#post41456540
(copy to the folder on your pc where your fastboot.exe is)
this stock rom for your variant (or another rom for your variant http://forum.xda-developers.com/showthread.php?t=2512742
(copy to sdcard of your phone)
Follow the "How to" in recovery thread to flash recovery, then follow the "How to" in the rom thread to flash the rom from recovery and at last step flash supersu.zip from recovery.
Click to expand...
Click to collapse
Thanks for taking the time to help, your instructions and advice has been indescribably useful
The phone is working fine again and it's all thanks to you.
Cool, you're welcome :laugh:
I tried to root my Opo, but it started to go wrong after i flashed it. It went to reboot into TWRP, but all that happened was it crashed. the 1+ logo comes on and then the screen goes blank. This Happens all the time when I try a "fastboot oem unlock", factory reset, or a boot recovery.. the fastboot does work, but the device is also locked and i can't do a recovery due to this. I tried to do the root tutorial on youtube by C4ETech.. help please!
@nickizm, when you boot to fastboot and enter the command "fastboot devices", can you see your device listed on the screen?
Thanks for the reply.. The fastboot work fines apart from when I try to unlock the devices and it reboots into recovery, it crashes and doesn't unlock.. the rest of the phone works fine apart from the recovery... my bootloader is also locked and I can't unlock it due to crashing
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screem enabled: false
I can't be certain but I'm pretty sure I read a similar issue to this a few days ago that was caused by not having the latest fastboot software, the user resolved it by downloading the latest android sdk and trying again.
Worth a shot.
Hope it helps.
Powered by Bacon
I had trouble when I first tried to root. Twrp wouldn't install. I ran some command which loaded it up but didn't install it on the phone, I was the able to root my phone.
Make sure you have latest oneplus one drivers. Have you tried using oneplus one toolkit to install recovery?
Sent from my Oneplus One using XDA Free mobile app.
I've tried to install a recovery, but my device is locked. If i do a "fastboot oem unlock" is just crashes on me when it going into recovery. I also get the same crash when I do a factory data reset or if I reboot into recovery. I think it's definitely something to do with the recovery, but since my device is locked i'm not sure what to do?... cheers again
nickizm said:
I've tried to install a recovery, but my device is locked. If i do a "fastboot oem unlock" is just crashes on me when it going into recovery. I also get the same crash when I do a factory data reset or if I reboot into recovery. I think it's definitely something to do with the recovery, but since my device is locked i'm not sure what to do?... cheers again
Click to expand...
Click to collapse
Did you try with the latest android sdk?
Powered by Bacon
I'm sure I did.. It wasn't that old.. I can try again, but the problem is I won't be able to unlock my phone??
is this the right link? http://developer.android.com/sdk/installing/index.html?pkg=studio
New drivers, exactly the same
Have you tried using a toolkit to do the unlock for you? People usually advise against using toolkits to do it for you as it prevents you gaining the experience of doing it yourself, but since it's not working when doing it yourself I don't see any harm in trying a toolkit.
You can find several options at the bottom of @timmaaa's resources roll-up thread here
Rkr87 said:
Have you tried using a toolkit to do the unlock for you? People usually advise against using toolkits to do it for you as it prevents you gaining the experience of doing it yourself, but since it's not working when doing it yourself I don't see any harm in trying a toolkit.
You can find several options at the bottom of @timmaaa's resources roll-up thread here
Click to expand...
Click to collapse
Yea i have also tried the tool kit V2
My problem is that the recovery is damaged in some way and my device is locked. i can't "fastboot oem unlock" as it just crashes when it goes to reboot.. is there a way to unlock my device with another method or can the recovery be repaired some how? i'm such noob
patstar5 said:
I had trouble when I first tried to root. Twrp wouldn't install. I ran some command which loaded it up but didn't install it on the phone, I was the able to root my phone.
Make sure you have latest oneplus one drivers. Have you tried using oneplus one toolkit to install recovery?
Sent from my Oneplus One using XDA Free mobile app.
Click to expand...
Click to collapse
Ye i tried that as well.. can't unlock the device as it just crashes when it goes to reboot into recovery
I think you might be out of luck, unless someone here more knowledgeable than I can help.
If you have a recovery image (not zip) you can try running the following command (make sure the img file is in the same directory as your adb/fastboot files and rename it "recovery");
Code:
fastboot boot recovery.img
What this allows you to do is boot into the TWRP recovery without having it installed on your phone, but I think I read somewhere that this command no longer works.
EDIT: If the above command will let you boot into TWRP, you'll want to read the guide here and flash the script.
Rkr87 said:
I think you might be out of luck, unless someone here more knowledgeable than I can help.
If you have a recovery image (not zip) you can try running the following command (make sure the img file is in the same directory as your adb/fastboot files and rename it "recovery");
Code:
fastboot boot recovery.img
What this allows you to do is boot into the TWRP recovery without having it installed on your phone, but I think I read somewhere that this command no longer works.
EDIT: If the above command will let you boot into TWRP, you'll want to read the guide here and flash the script.
Click to expand...
Click to collapse
I've tried that as well, but as my device is locked it won't allow it.. I'm stuck in limbo for now unless there is a way to unlock my device or repair the recovery? thanks for trying anyways
nickizm said:
I've tried that as well, but as my device is locked it won't allow it.. I'm stuck in limbo for now unless there is a way to unlock my device or repair the recovery? thanks for trying anyways
Click to expand...
Click to collapse
One last effort, after a bit of reading I've seen a few people with your issue have resolved it by flashing ColorOS (Chinese Stock ROM) and then going back to a custom rom once everything is fixed.
You can find a guide on how to do this here
Rkr87 said:
One last effort, after a bit of reading I've seen a few people with your issue have resolved it by flashing ColorOS (Chinese Stock ROM) and then going back to a custom rom once everything is fixed.
You can find a guide on how to do this here
Click to expand...
Click to collapse
Cheers mate! I just had a quick flick through it and it looks promising? the only problem seems to be with drivers in windows 7 which i am also using.. I'll see if I can do it via linux or i'll have to install xp on my old laptop or something.. I'll save this for tomorrow tho as it's late and will let you know how I get on with it. thanks for the help
nickizm said:
Cheers mate! I just had a quick flick through it and it looks promising? the only problem seems to be with drivers in windows 7 which i am also using.. I'll see if I can do it via linux or i'll have to install xp on my old laptop or something.. I'll save this for tomorrow tho as it's late and will let you know how I get on with it. thanks for the help
Click to expand...
Click to collapse
No worries! Let me know how it goes good luck!
Rkr87 said:
No worries! Let me know how it goes good luck!
Click to expand...
Click to collapse
Definitely! cheers again
nickizm said:
I tried to root my Opo, but it started to go wrong after i flashed it. It went to reboot into TWRP, but all that happened was it crashed. the 1+ logo comes on and then the screen goes blank. This Happens all the time when I try a "fastboot oem unlock", factory reset, or a boot recovery.. the fastboot does work, but the device is also locked and i can't do a recovery due to this. I tried to do the root tutorial on youtube by C4ETech.. help please!
Click to expand...
Click to collapse
can you give a little detail about
"device is also locked and i can't do a recovery due to this"
you did fastboot oem unlock. so saved data is wiped. but you should be able to boot into android system,
if so, enable "developer options" by clicking "settings" --> "about phone" --> "Build Number" click it 7 times,
then go into settings developer options and enable USB debugging.
then, use not fastboot, but adb to boot into recovery.
adb reboot recovery
Click to expand...
Click to collapse
there you can got into recovery.
Gh05tShie1d said:
can you give a little detail about
"device is also locked and i can't do a recovery due to this"
you did fastboot oem unlock. so saved data is wiped. but you should be able to boot into android system,
if so, enable "developer options" by clicking "settings" --> "about phone" --> "Build Number" click it 7 times,
then go into settings developer options and enable USB debugging.
then, use not fastboot, but adb to boot into recovery.
there you can got into recovery.
Click to expand...
Click to collapse
That doesn't work as my device crashes when it goes into recovery..
eg: "fastboot oem unlock", factory reset, or a boot recovery all crash as my recovery isn't working. When my device goes to reboot in recovery the 1+ logo comes up, fades out to like a blueish from the white 1+ logo and crashes.. so basically it's looked and I can't get into recovery.. thanks for trying
Android 6.0.1, build number MOB30H
I have a brand new nexus 5 that I want to root. Using ota, I accepted the system updates to 6.0.1 with the Android security patch of May 1, 2016. (not sure if that was a good idea or not but it's done now....). Now I want to root it with a twrp recovery.
Like most run of the mill users I've only rooted a device 2-3 times in my life, so my memory is rusty on how exactly to do it. I searched this forum and found many threads about this or that rooting problem which just confused me further. I know I need to unlock the bootloader and then flash a twrp recovery but I am not sure of the exact sequence of steps.
1. When I connect the nexus 5 to my windows pc using adb, it appears in Windows but the nexus 5 folder is empty. I have developer options available and usb debugging is on but I can't find where the mtp switch is.
2. Adb.
I have adb installed in Windows. The command "adb devices" returns the nexus 5 number unauthorized.
Don't know what "unauthorized" means or what to do about it.
I've done nothing further because I don't want to mess things up. Please help me resolve questions 1 and 2. Then, I presume I need to
A. unlock the bootloader
Fastboot command?
B. What's next?
Thanks for any help.
Two things, have you enabled developer options. Go to settings, about phone and tap build number 7 times. In developer options you can change USB configuration and you'll also need to enable OEM unlock. Then unlock and root your device per the guide in the general section.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Two things, have you enabled developer options. Go to settings, about phone and tap build number 7 times. In developer options you can change USB configuration and you'll also need to enable OEM unlock. Then unlock and root your device per the guide in the general section.
Click to expand...
Click to collapse
Just to add,not to confuse him even more, there is no Oem unlock option for Nexus 5
Sent from my Alps Q10101 using XDA Labs
You need to connect the phone in fastboot mode, run the command "fastboot oem unlock:, accept the agreement using the volume and power buttons, reboot into fastboot mode, flash twrp, copy the latest version of supersu.zip to the phone's internal memory, and flash supersu.zip from twrp.
You can install TWRP and root without using ADB commands.
Yes I already had developer options working and also usb debug on.
Discovered that mtp is a problem in marshmallow. I finally got file transfer working.
audit13 said:
You need to connect the phone in fastboot mode, run the command "fastboot oem unlock:, accept the agreement using the volume and power buttons, reboot into fastboot mode, flash twrp, copy the latest version of supersu.zip to the phone's internal memory, and flash supersu.zip from twrp.
You can install TWRP and root without using ADB commands.
Click to expand...
Click to collapse
Thank you very much. That is very helpful.
I didn't know you could "install TWRP and root without using ADB commands". How do you do that?
BTW, I updated the new nexus 5 to marshmallow inadvertently. When I root I'll probably use a 5.1.1 image. Good idea?
Stevica Smederevac said:
Just to add,not to confuse him even more, there is no Oem unlock option for Nexus 5
Sent from my Alps Q10101 using XDA Labs
Click to expand...
Click to collapse
Yep, my bad. Sorry about that. My 5 crapped out and have the 5x now. Amazing how fast you forget things, lol.
Sent from my Nexus 9 using XDA Free mobile app
Download and flash twrp in fastboot mode: https://dl.twrp.me/hammerhead/twrp-3.0.2-0-hammerhead.img.html
Download supersu.zip and save it to the phone's internal memory: https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip
Boot the phone into fasboot mode, open a command prompt, type fastboot devices and press enter. If the device is recognized, you'll see the device's serial number. Unlock the bootloader by typing "fastboot oem unlock" and use the volume/power button to accept the agreement and unlock the bootloader. Unlocking the bootloader will wipe the phone's data and cache.
To install TWRP, boot the phone into fastboot mode, connect it to the computer, open a command prompt, and type "fastboot flash recovery name-of-TWRP-file,img" and press enter. After flashing, immediately boot into recovery using the power and volume buttons, and then flash supersu.zip.
Thank you so much audit13. I really appreciate your help.
One question if I may. Reading on the web about rooting the nexus 5 running marshmallow I came across a couple of sites that said I should download and flash "ElementalX kernel and SuperSU 2.52" in addition to supersu.
I've never had to install a separate kernel when I rooted in the past. I notice you don't add flashing a kernel either. Can I ignore flashing a special kernel?
Thank you so very much for your clear instructions.
Some root methods require a rootable kernel. The latest supersu should root mm.
Thank you. Ran into a problem. That's why people like me are afraid of rooting.
Bootloader is now unlocked. Thanks.
With the N5 in fastboot mode, I connected it again with the laptop.
From the laptop command prompt I ussued "fastboot devices" and it found the phone.
Problem:
1. Fastboot flash recovery.img
(I had renamed the twrp 3.0.2 img file to recovery. Img)
Result:
unknown partition 'recovery.img'
error: cannot determine image filename for' recovery.img'
Tried by downloading a fresh copy and using its original filename.
Same result.
What am I doing wrong?
Thank you.
Found my error. I forgot the word recovery.
I now flashed twrp successfully!
When I went to flash supersu I discovered that the supersu I had downloaded was no longer in download folder. Guess it got wiped. So I rebooted into system and will download it again. Hope that does not mess up things.
Edit:
All went well. Re-downloaded SuperSU, installed fine and I'm home free.
Thank you all, especially audit13. This is a nerve-wracking process for people who only do it rarely. Glad it is over. The rest is easy!
I spoke too soon. I believe I now have a boot loop? What I have is that the horizontal turning balls of marshmallow go around forever and never finish booting.
How do I exit from this?
So close, but not there!
Edit
I rebooted into twrp, deleted cache, davlik. Still in bootloop.
Deleted data. Still in bootloop.
Help.
Reflash the entire stock rom and start over.
Try the latest beta of supersu: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Great you are still here.
Need more details.
You say reflash stock rom. Where do I get it? How do I get it into the phone? Do I flash it through twrp?
How to flash factory image: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Factory images are here: https://developers.google.com/android/nexus/ota#hammerhead
Thank you again. Will do.
I think I know what went wrong. After I flashed twrp the phone rebooted into system before I could stop it and I think I interrupted it somewhere to return to twrp to flash Supersu. Anyway, glad I didn't brick it. Thanks again for being there.
It's morning now and after a good night's sleep I'm less rattled. Will get breakfast and start again.
I'm going out with my wife for breakfast.
I haven't followed the marshmallow threads but I recall reading about lingering problems with marshmallow. I also like to use xprivacy and gravitybox. So I'm thinking of flashing the latest 5.1.1 instead of 6. Any thoughts?
I like both ROMs but my battery life seems a bit better on MM. I'm sticking with unrooted stock ROMs on all of my phones for now.
Being a "flashaholic" is tiring!
audit13, I know you know this but it was so simple to do (once you know how.....!). It took me the whole of 20 minutes, if that, to download the files, flash 5.1.1, flash twrp and install SuperSU. Makes you wonder why I had so much trouble before!
Well when you don't know the command syntax (forget to write which partition to flash to) and are frozen with fear that you will brick the phone, it is a scary process. Once I knew how, I breezed through it. Problem is that by the next time I need to do this, I will have forgotten how or will worry that the process has changed.
I just want to thank you more than I can say for helping and hanging in while I made my mistakes. I wish there was a way I could thank you with more than words. You were great!
P.S. This time I used the beta SuperSU. Don't know if it made any difference.