Just got my T-Mobile H901BK, ran the OEM Unlock and it worked!
[img]http://i.imgur.com/pnTbYCQ.png[/img]
I suppose I can write up a How-To:
1) Enable Developer Options and USB Debugging
2) Under Developer Options, check the box for Enable OEM Unlock.
3) Run an adb terminal (Nexus Root Toolkit has this in Advanced Utilities if you want the fast way).
4) In the adb prompt, type "adb reboot bootloader" or power the phone off and hold Power+VolUp buttons or Nexus Root Toolkit can do it for you in Adv. Util.
5) The phone should reboot to the LG screen with small writing in the top left of the screen.
6) In the adb prompt, type "fastboot oem unlock".
7) In the adb prompt, type "fastboot getvar unlocked".
8) You're done, you can reboot your phone however you want, I used "fastboot reboot". Enjoy!
TheJesus said:
Just got my T-Mobile H901BK, ran the OEM Unlock and it worked!
[img]http://i.imgur.com/pnTbYCQ.png[/img]
Click to expand...
Click to collapse
Right on! To the tmobile store i go! :highfive:
Also, if you don't know how to do it. Enable developer options, in dev options check the box for "OEM Unlock", open up an adb terminal (I used the Nexus Root Toolkit because it's very simple), reboot to bootloader (power and volume up), fastboot oem unlock, fastboot getvar unlocked (if yes, you're done), fastboot reboot.
This will factory reset your phone and disable some security features supposedly.
OK.... Root.
Woot!
Sent from my SGH-T889 using Tapatalk
charlieb620 said:
OK.... Root.
Click to expand...
Click to collapse
Working on it, phone is restoring after factory reset. Any recommended root method?
TheJesus said:
Working on it, phone is restoring after factory reset. Any recommended root method?
Click to expand...
Click to collapse
Unless there is a image to unbrick the phone I wouldn't try anything just yet tbh. I have a couple of ideas though.
---------- Post added at 02:12 PM ---------- Previous post was at 02:05 PM ----------
Safest method without bricking would be:
http://kingrootdownload.com/download/Kingroot_4.5.apk
charlieb620 said:
Unless there is a image to unbrick the phone I wouldn't try anything just yet tbh. I have a couple of ideas though.
---------- Post added at 02:12 PM ---------- Previous post was at 02:05 PM ----------
Safest method without bricking would be:
http://kingrootdownload.com/download/Kingroot_4.5.apk
Click to expand...
Click to collapse
No root strategy available from KingRoot :/
TheJesus said:
No root strategy available from KingRoot :/
Click to expand...
Click to collapse
We're going to have to extract the recovery img and have someone create twrp for the device and then flash su..
TheJesus said:
Just got my T-Mobile H901BK, ran the OEM Unlock and it worked!
[img]http://i.imgur.com/pnTbYCQ.png[/img]
Click to expand...
Click to collapse
I don't have the phone yet, but have a question. Do you have to type in those commands or just choose them from a list of commands?
Sent from my unknown using Xparent BlueTapatalk 2
btvolta said:
I don't have the phone yet, but have a question. Do you have to type in those commands or just choose them from a list of commands?
Sent from my unknown using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Either or....
You can use the nexus kit or do it manually through cmd
Swizzle82 said:
We're going to have to extract the recovery img and have someone create twrp for the device and then flash su..
Click to expand...
Click to collapse
You tell me how and I'll at least try the extraction. Gonna be on the road for a few hours, might as well do something.
btvolta said:
I don't have the phone yet, but have a question. Do you have to type in those commands or just choose them from a list of commands?
Sent from my unknown using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
I typed them in. Nexus Root Toolkit isn't designed for our phone, but these are adb commands that work universally.
TheJesus said:
You tell me how and I'll at least try the extraction. Gonna be on the road for a few hours, might as well do something.
I typed them in. Nexus Root Toolkit isn't designed for our phone, but these are adb commands that work universally.
Click to expand...
Click to collapse
The easiest way I believe is from te kdz we don't have yet.. There are other ways, but I haven't had to do that in years.. Might have to have a more knowledgeable person handle all that. Might be able to boot into fast boot and type get recovery.img someone will still have to create twrp though..
charlieb620 said:
Either or....
You can use the nexus kit or do it manually through cmd
Click to expand...
Click to collapse
So with the Nexus toolkit, you just choose unlock and it does it automatically? I've never had to unlock before because I've always been on Samsung. Also, would terminal emulator work?
Great news!!! Thanks!
btvolta said:
So with the Nexus toolkit, you just choose unlock and it does it automatically? I've never had to unlock before because I've always been on Samsung. Also, would terminal emulator work?
Click to expand...
Click to collapse
I would do it manually through cmd(with admin privileges)
Great news. Picking mine up in the morning
I want to make sure, also, H901BK is the model ? i cant find any info on this.
joachim123 said:
I want to make sure, also, H901BK is the model ? i cant find any info on this.
Click to expand...
Click to collapse
Yes, I posted that on Reddit for someone who asked.
This really just made this phone the best buy of 2015. I love this forum
Sent from my SM-N915T using Tapatalk
Related
I just recently rooted my HTC One X and and now attempting to unlock the bootloader using HTC Dev. I've gotten my folder set up with all of the correct files (ADB and such) as well as gotten Android SDK installed. So far I've gotten into my command prompt and navigated to my file called "fastboot" that contains all of my adb files. I'm stuck at the fastboot unlock token stage. Whenever I enter that I get this error-
C:\fastboot>fastboot oem get_identifier_token
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
Click to expand...
Click to collapse
I've played around with it and tried different things, but still get this error. I am in bootloader/fastboot mode so that isn't the problem.
One thing I find interesting is that if I do "adb devices" I get
C:\fastboot>adb devices
List of devices attached
Click to expand...
Click to collapse
So as you can see, it doesn't say there are any devices connected. Is this normal?
Please, if you see what I'm doing wrong it'd be great if you could help me out!
tanner4137 said:
I just recently rooted my HTC One X and and now attempting to unlock the bootloader using HTC Dev. I've gotten my folder set up with all of the correct files (ADB and such) as well as gotten Android SDK installed. So far I've gotten into my command prompt and navigated to my file called "fastboot" that contains all of my adb files. I'm stuck at the fastboot unlock token stage. Whenever I enter that I get this error-
I've played around with it and tried different things, but still get this error. I am in bootloader/fastboot mode so that isn't the problem.
One thing I find interesting is that if I do "adb devices" I get
So as you can see, it doesn't say there are any devices connected. Is this normal?
Please, if you see what I'm doing wrong it'd be great if you could help me out!
Click to expand...
Click to collapse
If I'm not mistaken you need to super Cid before doing that I'd suggest just using and following this thread http://forum.xda-developers.com/showthread.php?t=1672284
Thank you so much! I got that done, unlocked the bootloader, and installed TWRP recovery. Now before I install CleanROM do I have to flash the boot.img using "fastboot flash boot boot.img" or am I good to just flash the whole .zip file through recovery?
tanner4137 said:
Thank you so much! I got that done, unlocked the bootloader, and installed TWRP recovery. Now before I install CleanROM do I have to flash the boot.img using "fastboot flash boot boot.img" or am I good to just flash the whole .zip file through recovery?
Click to expand...
Click to collapse
Depends ...what firmware r u on 1.73 or 1.85
---------- Post added at 02:18 AM ---------- Previous post was at 02:17 AM ----------
If you're on 1.73 you don't have to do anything but on not sure about 1.85 ill get back to you :angel:
1.85
tanner4137 said:
1.85
Click to expand...
Click to collapse
Unless you took the 2.20 update you dodon't have to do that so go ahead and flash clean rom and enjoy 99.7% ssure
Could I see where you found this?
tanner4137 said:
Could I see where you found this?
Click to expand...
Click to collapse
A couple different threads now I'm 99.9 percent sure you isn't have to flash the boot img. U can post in the q and a section if you really must you'll get a straight answer there
First you do have adb files installed? If you do make sure you install the drivers. Just install HTC Sync and make sure that it's not running in the task bar. Then try again. I'm almost sure that the drivers are missing in this case.
Sent from my HTC One XL using xda premium
TheNightHawk223 said:
First you do have adb files installed? If you do make sure you install the drivers. Just install HTC Sync and make sure that it's not running in the task bar. Then try again. I'm almost sure that the drivers are missing in this case.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Lol, thanks. If you read above you can see that I solved that. What I'm needing to know now is if I have to flash a boot.img before I flash a ROM, or if I can just download the .zip and flash it from recovery.
tanner4137 said:
Lol, thanks. If you read above you can see that I solved that. What I'm needing to know now is if I have to flash a boot.img before I flash a ROM, or if I can just download the .zip and flash it from recovery.
Click to expand...
Click to collapse
Sorry I'm just incredibly lazy and forget to read sometimes , well since you never took the 2.20 RUU/OTA you just have to run the zip unless the instructions for the rom specificly says to flash the boot.img.
Sent from my HTC One XL using xda premium
Some back story. My N5 was stock/rooted, with stock recovery. I had installed the beta Xposed framework, using this post as a guide. Following the install, during the reboot, my phone never restarted. Since then it has not been able to turn on.
Things I have tried:
I have done method 1 & 2 of this guide
I am able to lock and unlock the bootloader, it is currently locked.
I have tried the command fastboot -w
I am unable to perform a factory reset, it hangs at /data
If there is any ideas as to what I should do next, please don't hesitate to let me know.
If I am able to get the Tamper Flag reset, then my plan is to look into the RMA option.
Also, I have been following this thread for info.
jimburke57 said:
Some back story. My N5 was stock/rooted, with stock recovery. I had installed the beta Xposed framework, using this post as a guide. Following the install, during the reboot, my phone never restarted. Since then it has not been able to turn on.
Things I have tried:
I have done method 1 & 2 of this guide
I am able to lock and unlock the bootloader, it is currently locked.
I have tried the command fastboot -w
I am unable to perform a factory reset, it hangs at /data
If there is any ideas as to what I should do next, please don't hesitate to let me know.
If I am able to get the Tamper Flag reset, then my plan is to look into the RMA option.
Also, I have been following this thread for info.
Click to expand...
Click to collapse
when you unlock the phone, and reboot the bootloader, does it stay locked or is it unlocked?
Zepius said:
when you unlock the phone, and reboot the bootloader, does it stay locked or is it unlocked?
Click to expand...
Click to collapse
So earlier when i did this, the phone would freeze. Now it went through with it, and is now showing the animated android images, with a moving bar at the bottom. It has been there for about 4 minutes now.
jimburke57 said:
So earlier when i did this, the phone would freeze. Now it went through with it, and is now showing the animated android images, with a moving bar at the bottom. It has been there for about 4 minutes now.
Click to expand...
Click to collapse
this still does not answer my question.
it sounds like your phone is not dead however. please follow the return to stock thread in the general forum and you should be ok.
Zepius said:
this still does not answer my question.
it sounds like your phone is not dead however. please follow the return to stock thread in the general forum and you should be ok.
Click to expand...
Click to collapse
I have followed it already. The images on the first post are my result.
It is showing as unlocked at the booloader and on fastboot oem device-info.
follow the 2nd post, not the 2nd method in this thread and tell us the results.
http://forum.xda-developers.com/showthread.php?t=2513701
Zepius said:
follow the 2nd post, not the 2nd method in this thread and tell us the results.
http://forum.xda-developers.com/showthread.php?t=2513701
Click to expand...
Click to collapse
Same thing as before. All of the erase commands get processed, but when it gets the the system.img it fails to write it.
I think you've done her in. Can you get into recovery? You might be able to push the tamper zip and then run it in recovery.
jd1639 said:
I think you've done her in. Can you get into recovery? You might be able to push the tamper zip and then run it in recovery.
Click to expand...
Click to collapse
I am able to access recovery. This is exactly what I am trying to do at the moment, but now I cannot adb sideload the zip. For some reason the N5 is not being recognized by windows.
jimburke57 said:
I am able to access recovery. This is exactly what I am trying to do at the moment, but now I cannot adb sideload the zip. For some reason the N5 is not being recognized by windows.
Click to expand...
Click to collapse
Use Galaxy Nexus drivers, and make sure you have updated the SDK for the latest adb.
orangekid said:
Use Galaxy Nexus drivers, and make sure you have updated the SDK for the latest adb.
Click to expand...
Click to collapse
Are you talking about these drivers?
jimburke57 said:
Are you talking about these drivers?
Click to expand...
Click to collapse
No, I have had success getting the Nexus 5 working on ADB with the Samsung Galaxy Nexus drivers. Don't ask me why, but it works for me.
orangekid said:
No, I have had success getting the Nexus 5 working on ADB with the Samsung Galaxy Nexus drivers. Don't ask me why, but it works for me.
Click to expand...
Click to collapse
So an update, I am able to sideload the zip in recovery, however, during the install, it fails.
jimburke57 said:
So an update, I am able to sideload the zip in recovery, however, during the install, it fails.
Click to expand...
Click to collapse
Have you tried flashing stock kitkat (from google) via fastboot?
orangekid said:
Have you tried flashing stock kitkat (from google) via fastboot?
Click to expand...
Click to collapse
yes, many times
So this is just a shot in the dark, but the fastboot command screenshot you posted, you had the command "fastboot flash bootloader."
I haven't read the articles you're using, but is there a reason you're flashing a bootloader after unlocking it? Wouldn't that just lock the bootloader again?
I'd start fastboot oem unlock, fastboot flash recovery, and then adb sideload the .zip you are using once you're in recovery.
Good luck.
pantlessjim said:
So this is just a shot in the dark, but the fastboot command screenshot you posted, you had the command "fastboot flash bootloader."
I haven't read the articles you're using, but is there a reason you're flashing a bootloader after unlocking it? Wouldn't that just lock the bootloader again?
I'd start fastboot oem unlock, fastboot flash recovery, and then adb sideload the .zip you are using once you're in recovery.
Good luck.
Click to expand...
Click to collapse
I am just following the guide for How to return to stock. But to answer your question, no it does not re-lock the bootloader.
Here is some additional information. When I perform a factory reset in recovery it freezes while formatting /data. And when flashing the stock images, I am able to flash everything successfully except for the system.img
jimburke57 said:
I am just following the guide for How to return to stock. But to answer your question, no it does not re-lock the bootloader.
Click to expand...
Click to collapse
Have you tried just dirty flashing stock / rooted thru recovery?
edit: or restoring a backup?
Hey guys,
I just got this phone a day ago and wanted to try out the Cataclysm ROM today.
I was following the following guide on how to root the Nexus 5:
androidrootz.com/2013/11/how-to-root-nexus-5-windowsmaclinuxubun.html
I got up to step 9:
9. Connect your Nexus 5 to your computer and transfer "UPDATE-SuperSU-v1.65.zip". This file is located in "RootNexus5" folder you downloaded earlier.
But it didn't allow me to transfer the file to the phone.
I assume it is unrooted, cause it says unlocked and it has an unlocked photo when I boot up my device. But I don't think it was fully rooted?? (I'm assuming because I wasn't able to complete the final steps).
So I decided that I'm just going to unroot it and stick with the stock ROM.
Any thoughts on how I can unroot it? Would it be okay to use Wugfresh's unrooter? Even though I didn't use it to root the phone?
wugfresh.com/nrt/
Please let me know. Thanks!! :good:
since your bootloader is already unlocked, just fastboot flash a custom recovery and then use adb to push the rom you want to your phone.
there are several threads on how to do this.
Zepius said:
since your bootloader is already unlocked, just fastboot flash a custom recovery and then use adb to push the rom you want to your phone.
there are several threads on how to do this.
Click to expand...
Click to collapse
Thanks for the quick reply; I'm looking to revert back to stock and unrooting my phone.
I tried using wpug's tool, but it says ADB device not found... I'm using windows XP for what it's worth. I'm stuck...
perfectbluelion said:
Thanks for the quick reply; I'm looking to revert back to stock and unrooting my phone.
I tried using wpug's tool, but it says ADB device not found... I'm using windows XP for what it's worth. I'm stuck...
Click to expand...
Click to collapse
if you never rooted your phone, its just unlocked bootloader so its still stock.
Zepius said:
if you never rooted your phone, its just unlocked bootloader so its still stock.
Click to expand...
Click to collapse
Thanks Zep.
I'm not even sure if I rooted the phone or not, but I got up to step 9 of the following guide (did not complete step 9)
androidrootz.com/2013/11/how-to-root-nexus-5-windowsmaclinuxubun.html
Is my phone fully rooted?
I'm attaching two photos of how my phone looks when:
1. I hit both volume and the power buttons:
SECURE BOOT - enabled
LOCK STATE - unlocked
2. When I boot up (picture of unlocked lock)
If only my bootloader is unlocked, how do I lock it back? I want to have it back the way it came from Google incase I need to return for warranty purposes.
Thanks a lot! :good:
1) your phone is not rooted if you did not flash supersu.zip which you said you didnt.
2) to lock your bootloader use: fastboot oem lock.
^ there is a return to stock thread on how to do this.
Those pics won't show if you're rooted. By your description I doubt you are. You never flashed supersu.
To lock the bootloader do
fastboot oem lock.
You should follow this guide to unlock and root http://forum.xda-developers.com/showthread.php?p=47025283
---------- Post added at 09:43 AM ---------- Previous post was at 09:39 AM ----------
Darn,I hate that when it happens. Good thing we have him the same answers
Zepius said:
1) your phone is not rooted if you did not flash supersu.zip which you said you didnt.
2) to lock your bootloader use: fastboot oem lock.
^ there is a return to stock thread on how to do this.
Click to expand...
Click to collapse
jd1639 said:
Those pics won't show if you're rooted. By your description I doubt you are. You never flashed supersu.
To lock the bootloader do
fastboot oem lock.
You should follow this guide to unlock and root http://forum.xda-developers.com/showthread.php?p=47025283
---------- Post added at 09:43 AM ---------- Previous post was at 09:39 AM ----------
Darn,I hate that when it happens. Good thing we have him the same answers
Click to expand...
Click to collapse
Thanks gentlemen. Will read up on fastboot oem lock, try it out, and advise on results. :good: Fingers crossed...
If you are getting device not found when you try to use ADB, that means that you either don't have the right drivers installed, or that you are not using a 'good' USB port. Try a different port.
Zepius, jd1639, All:
Is there a guide to doing a fastboot oem lock?
It's not the following thread right:
http://forum.xda-developers.com/showthread.php?t=2513701
Not sure if there's a specific guide for locking the bootloader, most of them is for unrooting (which I don't need, correct?).
Thanks a lot guys!
perfectbluelion said:
Zepius, jd1639, All:
Is there a guide to doing a fastboot oem lock?
It's not the following thread right:
http://forum.xda-developers.com/showthread.php?t=2513701
Not sure if there's a specific guide for locking the bootloader, most of them is for unrooting (which I don't need, correct?).
Thanks a lot guys!
Click to expand...
Click to collapse
its literally typing the command in the command window: fastboot oem lock
perfectbluelion said:
Zepius, jd1639, All:
Is there a guide to doing a fastboot oem lock?
It's not the following thread right:
http://forum.xda-developers.com/showthread.php?t=2513701
Not sure if there's a specific guide for locking the bootloader, most of them is for unrooting (which I don't need, correct?).
Thanks a lot guys!
Click to expand...
Click to collapse
Yes that one... we assume you fastboot flashed recovery so you need to return that too.
If you don't know what you've done, follow the whole guide and fully return to stock.
Otherwise, cherry pick what you need from the guide
-----------------------
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
OK in am new to this if I root my phone with one root brand or what ever it's called can I unroot with the same kind or something different
UnderstandFones said:
OK in am new to this if I root my phone with one root brand or what ever it's called can I unroot with the same kind or something different
Click to expand...
Click to collapse
Okay, to first learn what is root and what it entails, read this http://forum.xda-developers.com/google-nexus-5/help/faq-to-android-read-post-root-t2508292
Once you have understanding of what it is, there are other guides to help you with the different aspects of it and possibilities of what you can do with your phone. Refer to this http://forum.xda-developers.com/goo...urce-guides-info-threads-linked-read-t2784527
Sounds like someone who doesn't know what "root" actually is :/
Also wrong section, and read the stickies.
Google search is your friend.
Google " fastboot "&" adb " along with the word and # " Nexus 5 ".
If you read and understand than it is harder to brick your device
Nexus 5 rastakat 4.4.3 via Tapatalk app
fxdil said:
Okay, to first learn what is root and what it entails, read this http://forum.xda-developers.com/google-nexus-5/help/faq-to-android-read-post-root-t2508292
Once you have understanding of what it is, there are other guides to help you with the different aspects of it and possibilities of what you can do with your phone. Refer to this http://forum.xda-developers.com/goo...urce-guides-info-threads-linked-read-t2784527
Click to expand...
Click to collapse
I understand root sorry I didn't make that clear. However I have three question. #1 Do I root before I get a recovery?#2 Do need a computer to root?
UnderstandFones said:
I understand root sorry I didn't make that clear. However I have three question. #1 Do I root before I get a recovery?#2 Do need a computer to root?
Click to expand...
Click to collapse
You only posed two..
1. No. You need to unlock the bootloader first, from there you can install a custom recovery.
2. Highly recommended. There are tools nowadays that simplifies the process, but nothing works as best as doing it manually. You'll get to learn more, understand how your phone works, and it's much easier overall for the people at this forum to help you if you encounter a problem, if you understand the terms we use and how things are done.
Sent using Etch-a-Sketch.
fxdil said:
You only posed two..
1. No. You need to unlock the bootloader first, from there you can install a custom recovery.
2. Highly recommended. There are tools nowadays that simplifies the process, but nothing works as best as doing it manually. You'll get to learn more, understand how your phone works, and it's much easier overall for the people at this forum to help you if you encounter a problem, if you understand the terms we use and how things are done.
Sent using Etch-a-Sketch.
Click to expand...
Click to collapse
Sorry I also didn't mention I unlocked the bootloader yesterday
UnderstandFones said:
Sorry I also didn't mention I unlocked the bootloader yesterday
Click to expand...
Click to collapse
Did you unlock using adb?
Then you should be on your way to rooting. Remember to flash a custom recovery first, that's very important.
Sent using Etch-a-Sketch.
@UnderstandFones Read all the threads which I've linked in my signature. Please read them thoroughly as it seems that your basics are not yet cleared.
fxdil said:
Did you unlock using adb?
Then you should be on your way to rooting. Remember to flash a custom recovery first, that's very important.
Sent using Etch-a-Sketch.
Click to expand...
Click to collapse
I followed these directions I don't know if it used adb but I think I remember seeing it.
fxdil said:
Did you unlock using adb?
.
Click to expand...
Click to collapse
You can't unlock the bootloader using adb. It needs to be unlocked when the phone is in fastboot mode using a fastboot command.
UnderstandFones said:
I followed these directions I don't know if it used adb but I think I remember seeing it.
Click to expand...
Click to collapse
If you have already unlocked the bootloader, then download a recovery, extract the recovery.img file and then flash it via fastboot. All these steps can be accessed by following the thread linked in my signature.
vin4yak said:
You can't unlock the bootloader using adb. It needs to be unlocked when the phone is in fastboot mode using a fastboot command.
If you have already unlocked the bootloader, then download a recovery, extract the recovery.img file and then flash it via fastboot. All these steps can be accessed by following the thread linked in my signature.[/QUOTE
Where I am confused is when I download the recovery in this case twrp 2.7.1.1 and the superSU and put them in the android platform folder, do I then turn my phone off and fastboot mode and unzip the superSU in the platform folder?
Click to expand...
Click to collapse
vin4yak said:
You can't unlock the bootloader using adb. It needs to be unlocked when the phone is in fastboot mode using a fastboot command.
If you have already unlocked the bootloader, then download a recovery, extract the recovery.img file and then flash it via fastboot. All these steps can be accessed by following the thread linked in my signature.
Click to expand...
Click to collapse
I didn't tell him to unlock using adb did I? Merely pointing out to do it manually, he must have had to download adb to his computer, given that he's not even sure how he unlocked his bootloader.
UnderstandFones said:
Where I am confused is when I download the recovery in this case twrp 2.7.1.1 and the superSU and put them in the android platform folder, do I then turn my phone off and fastboot mode and unzip the superSU in the platform folder?
Click to expand...
Click to collapse
Will you please read the thread named "[GUIDE] Nexus 5 - How to Unlock Bootloader, Install Custom Recovery and Root" which is linked in my signature. Read it thoroughly and then post questions. Please get your basics cleared first.
Put the twrp img file in platform tools folder and then open a cmd window from there to run fastboot commands. Yes, you need to go into fastboot mode to run fastboot commands.
fxdil said:
I didn't tell him to unlock using adb did I? Merely pointing out to do it manually, he must have had to download adb to his computer, given that he's not even sure how he unlocked his bootloader.
Click to expand...
Click to collapse
Just for the sake of accuracy and to be pedantic, fastboot and adb are completely different. fastboot.exe and adb.exe do completely different things. All thats needed unlock the bootloader is fastboot.exe and USB drivers. This can all be done without downloading adb.exe
Sent from my Nexus 5 using Tapatalk
Where I am confused is when I download the recovery in this case twrp 2.7.1.1 and the superSU and put them in the android platform folder, do I then turn my phone off and fastboot mode and unzip the superSU in the platform folder?
Click to expand...
Click to collapse
Turn your phone off, boot into bootloader, then fastboot the recovery image.
Once done, reboot into your new custom recovery, use adb to push the superSU zip to your phone (do not unzip it, leave it as it is), use your custom recovery to locate to the zip, then install it.
fxdil said:
I didn't tell him to unlock using adb did I? Merely pointing out to do it manually, he must have had to download adb to his computer, given that he's not even sure how he unlocked his bootloader.
Click to expand...
Click to collapse
You said, "Did you unlock using adb? Then you should be on your way to rooting."
Anyone would interpret this as if your accepting that the bootloader is unlocked with adb. Which isn't correct. In any case, if that's not what you meant, my bad!
vin4yak said:
Will you please read the thread named "[GUIDE] Nexus 5 - How to Unlock Bootloader, Install Custom Recovery and Root" which is linked in my signature. Read it thoroughly and then post questions. Please get your basics cleared first.
Put the twrp img file in platform tools folder and then open a cmd window from there to run fastboot commands. Yes, you need to go into fastboot mode to run fastboot commands.
Click to expand...
Click to collapse
I am doing what you are telling me in your thread. when I open the command window and input the first code it say "the system cannot find the path specified" that the problem / what has been done fore this to say that?
UnderstandFones said:
I am doing what you are telling me in your thread. when I open the command window and input the first code it say "the system cannot find the path specified" that the problem / what has been done fore this to say that?
Click to expand...
Click to collapse
Post a screenshot please
Sent from my Nexus 5 using Tapatalk
UnderstandFones said:
I am doing what you are telling me in your thread. when I open the command window and input the first code it say "the system cannot find the path specified" that the problem / what has been done fore this to say that?
Click to expand...
Click to collapse
You get that error because the twrp file which you're trying to flash isn't in the platform tools folder.
Here are some things you need to check:
1. Have you navigated correctly to the twrp file path in fastboot?
2. Is the twrp file named correctly? if it's recovery.img then the command would be fastboot flash recovery recovery.img
3. Make sure you have file extensions seen in windows explorer so that you can confirm the file extension.
Tested vroot and framaroot but both are not working. This is a cheap tablet provided by Tmobile just these recent weeks. I do not think the root method is the same as the other pixi 7 sold in other places since they have different processors, S410 for Tmo version. Any one knows?
Solved : #45
Try rooting it using pc and root genius software on pc
It will work.
Peace
droid_god said:
Try rooting it using pc and root genius software on pc
It will work.
Peace
Click to expand...
Click to collapse
thanks but no luck,,,,,,
Use an app named root master on your android
droid_god said:
Use an app named root master on your android
Click to expand...
Click to collapse
thanks but still not working.......
Hmm it seems that you have to flash a custom recovery before rooting.
May i know that your device have a download mode or not
droid_god said:
Hmm it seems that you have to flash a custom recovery before rooting.
May i know that your device have a download mode or not
Click to expand...
Click to collapse
not sure if this is.....but i guess this is the recovery instead.
In recovery go to reboot to bootloader amd the send me thd pics.
Yes this is recovery
droid_god said:
In recovery go to reboot to bootloader amd the send me thd pics.
Yes this is recovery
Click to expand...
Click to collapse
stuck here
Seems your bootloader is locked. It has to be unlocked by adb and some commands
i see! Can it be done simply or need to wait for professionals?
Search the google anf you will get your results
droid_god said:
Search the google anf you will get your results
Click to expand...
Click to collapse
thx !
You can use the adb commands like adb oem unlock
droid_god said:
You can use the adb commands like adb oem unlock
Click to expand...
Click to collapse
I will try..... do I need to put the device in mtp mode or.....? just type adb in cmd and type oem unlock?
You can use the adb commands like adb oem unlock
Well truly i have not unlocked my bootloader. Never faced a problem like this. As my bootloader got automatically unlocked when i tried to root.
Pleaae post a good method here if you find one
You can unlock the bootloader using fastboot. That's as far as I've gotten so far.
Yes you have got correct
droid_god said:
Yes you have got correct
Click to expand...
Click to collapse
Unlock Boot loader doesn't help much with root. I tried all the root apps and nothing at all works.without a boot.IMG we're stuck.
You can try flashing a custom recovery amd then glaahimg root update.zip.
Lile we do for samaung devives