I already searched and followed the sticky thread in rooting, but failed. Already tried one click root, failed also. I bought my N1 (pre-owned). Anyone can help me please.? I already googled it and view all possible results.:crying:
try superoneclick root.
Sent from my Nexus One using Tapatalk
anmino said:
I already searched and followed the sticky thread in rooting, but failed. Already tried one click root, failed also. I bought my N1 (pre-owned). Anyone can help me please.? I already googled it and view all possible results.:crying:
Click to expand...
Click to collapse
Ignore that. Just use this.
http://forum.xda-developers.com/showthread.php?t=1000357
You might be able to use Blackrose to get S-OFF via an exploit but I'm pretty sure the methods have been patched in 2.3.6 so do it properly.
PC:
Get Android SDK.
Unzip.
Run SDK Manager
Download USB Driver
Run a terminal/command prompt
cd into platform-tools
Phone:
Turn off phone.
Hold down Vol Down.
Press Power
Should say "fastboot"
Stick in USB Cable
PC:
If drivers are missing point to
android-sdk\extras\google
In terminal you opened earlier type
fastboot devices
You should see your device in a list, if not, try again with installing drivers for your OS.
If in list, type
fastboot oem unlock
Unlock Bootloader voids warranty.
I am not responsible for anything, if this doesn't work, don't blame me.
Sarkie said:
Ignore that. Just use this.
http://forum.xda-developers.com/showthread.php?t=1000357
You might be able to use Blackrose to get S-OFF via an exploit but I'm pretty sure the methods have been patched in 2.3.6 so do it properly.
PC:
Get Android SDK.
Unzip.
Run SDK Manager
Download USB Driver
Run a terminal/command prompt
cd into platform-tools
Phone:
Turn off phone.
Hold down Vol Down.
Press Power
Should say "fastboot"
Stick in USB Cable
PC:
If drivers are missing point to
android-sdk\extras\google
In terminal you opened earlier type
fastboot devices
You should see your device in a list, if not, try again with installing drivers for your OS.
If in list, type
fastboot oem unlock
Unlock Bootloader voids warranty.
I am not responsible for anything, if this doesn't work, don't blame me.
Click to expand...
Click to collapse
Okay. It says my bootloader is unlocked. Is this already rooted?
Hello ,
Im new here and i tried to flash a file and right now i cant start my phone .
the only thing i can do is get into bootloader , i looked all around videos and threads , tried to unbrick unroot flash a diffrent rom . nothing works . i can't get s-off , my computer cant recognize the phone , no adb commands work,
the only thing i was able to do is to reinstall twrp recovery.
Any ideas please ? i beileve there's an answer online before i go to the store to fix it . please help im new to android (only 3 months)
Thank you .
messsiah said:
Hello ,
Im new here and i tried to flash a file and right now i cant start my phone .
the only thing i can do is get into bootloader , i looked all around videos and threads , tried to unbrick unroot flash a diffrent rom . nothing works . i can't get s-off , my computer cant recognize the phone , no adb commands work,
the only thing i was able to do is to reinstall twrp recovery.
Any ideas please ? i beileve there's an answer online before i go to the store to fix it . please help im new to android (only 3 months)
Thank you .
Click to expand...
Click to collapse
You may install the HTC Drivers... and ADB works only on system or recovery... otherwise you have to use fastboot commands. So I'd recommand flashing a Stock ROM from TWRP, you can get a stock rom from here: http://forum.xda-developers.com/showthread.php?t=2224752 (thanks Mike1986 for providing such awesome ROMs)... then you should have a working phone again. At least: If you can enter the bootloader EVERYTHING is fine and you didn't f*** up your HTC One.
Hit the Thanksbutton if it helped or ask me for further clarification
LibertyMarine said:
You may install the HTC Drivers... and ADB works only on system or recovery... otherwise you have to use fastboot commands. So I'd recommand flashing a Stock ROM from TWRP, you can get a stock rom from here: http://forum.xda-developers.com/showthread.php?t=2224752 (thanks Mike1986 for providing such awesome ROMs)... then you should have a working phone again. At least: If you can enter the bootloader EVERYTHING is fine and you didn't f*** up your HTC One.
Hit the Thanksbutton if it helped or ask me for further clarification
Click to expand...
Click to collapse
First of all thank you for the quick response ,and for callming down a bit.
but like i said i am new to this stuff if you can please tell me where can i get the htc drivers because all i can see in the htc site is the htc sync manager ..... and second when i tried to use adb it says that there is not response from my device , like it cannot recognize it. i downloaded the files in the link you posted here . please if you can tell me with more details what to do or if you can direct me to another post with step by step instractions i will really appriciate it .
messsiah said:
First of all thank you for the quick response ,and for callming down a bit.
but like i said i am new to this stuff if you can please tell me where can i get the htc drivers because all i can see in the htc site is the htc sync manager ..... and second when i tried to use adb it says that there is not response from my device , like it cannot recognize it. i downloaded the files in the link you posted here . please if you can tell me with more details what to do or if you can direct me to another post with step by step instractions i will really appriciate it .
Click to expand...
Click to collapse
Okay, first here you have the correct adb and fastboot files, I uploaded them quickliy for you, I think this way they should work properly:
http://uploaded.net/file/ykwya517
Next thing are these HTC Drivers, in this post are a few of them: http://forum.xda-developers.com/showthread.php?t=2089508 and on my computer there are the 4.3.0.001 drivers, so I'd recommand downloading those(Credits go to @mdmower):
http://www.mediafire.com/download/n5y93fdgkvexpwc/HTC+Driver+4.3.0.001.exe
Now shut down your phone and boot in into the bootloader with pressing the power button and the volume down button. Then select fastboot and enter this menu. Now if the drivers are installed correctly there should be written FASTBOOT USB. I think you said you are unlocked... so the following command should run just fine. Open a command prompt and navigate to the folder where adb and fastboot are placed. In this folder you copy your custom recovery(TWRP) and you flash it with this command:
Code:
fastboot flash recovery [recoveryname].img
And DON'T worry about adb in the bootloader! ADB doesn't work with the bootloader. Now you boot into your recovery by chosing Recovery somewhere in your bootloader. If you are in the bootloader you somehow need to push the ROM to your HTC One... This should work with this command...
Code:
adb push "C:\FolderWhereRomIsStored\rom.zip" "/data/media/0/rom.zip"
And if this doesn't copy it correctly simply place your zip on your computer to a folder that is empty and push this folder to your HTC One with:
Code:
adb push "C:\FolderWhereRomIsStored" "/data/media/0"
Now you are good to go, simply flash the zip form TWRP. I think you know how this works Simply go to install and then chose the zip and flash it.
If you now want to s off... then ask me again. I'll give you an advice
LibertyMarine said:
Okay, first here you have the correct adb and fastboot files, I uploaded them quickliy for you, I think this way they should work properly:
http://uploaded.net/file/ykwya517
Next thing are these HTC Drivers, in this post are a few of them: http://forum.xda-developers.com/showthread.php?t=2089508 and on my computer there are the 4.3.0.001 drivers, so I'd recommand downloading those(Credits go to @mdmower):
http://www.mediafire.com/download/n5y93fdgkvexpwc/HTC+Driver+4.3.0.001.exe
Now shut down your phone and boot in into the bootloader with pressing the power button and the volume down button. Then select fastboot and enter this menu. Now if the drivers are installed correctly there should be written FASTBOOT USB. I think you said you are unlocked... so the following command should run just fine. Open a command prompt and navigate to the folder where adb and fastboot are placed. In this folder you copy your custom recovery(TWRP) and you flash it with this command:
Code:
fastboot flash recovery [recoveryname].img
And DON'T worry about adb in the bootloader! ADB doesn't work with the bootloader. Now you boot into your recovery by chosing Recovery somewhere in your bootloader. If you are in the bootloader you somehow need to push the ROM to your HTC One... This should work with this command...
Code:
adb push "C:\FolderWhereRomIsStored\rom.zip" "/data/media/0/rom.zip"
And if this doesn't copy it correctly simply place your zip on your computer to a folder that is empty and push this folder to your HTC One with:
Code:
adb push "C:\FolderWhereRomIsStored" "/data/media/0"
Now you are good to go, simply flash the zip form TWRP. I think you know how this works Simply go to install and then chose the zip and flash it.
If you now want to s off... then ask me again. I'll give you an advice
Click to expand...
Click to collapse
Thank you very much !!! worked ! saved me ....
messsiah said:
Thank you very much !!! worked ! saved me ....
Click to expand...
Click to collapse
Good to know that it worked As some kind of a hint I'd recommand not to proceed s off at the moment because with this security system disabled, you are able to destroy many more partitions such as the bootloader and this would result with irreparable damage to your device and it would be hardbricked. So my advice is: Keep your hands away from S OFF for a few weeks and use rumrunner s off if you are sure that you can understand adb/fastboot basics. I really don't want to say that you are stupid or a noob, this is truly NOT the case! Everyone needs experience and the only way to get experience is to read through forums, to read statements from people that hardbricked their device and many more thing But you have a working phone right now, that is important :highfive:
( I posted this elsewhere, but i guess its beter in the actual HTCONE section) , mod feel free to delete my other one, thank you.
Good afternoon, !!!
First and foremost , I want to thank you all in advance for ANY and help, time & consideration with my current issue. I will try my best to be clear, and give all relevant info here in my first post. Please bear with me, I am pretty good when it comes to following directions, but i havent been able to find a CLEAR solution to this yet, and worried about further screwing up my phone.
** I use a mac. I currently dont have access to a PC, so i am looking for a mac remedy if possible.
I have an HTCONE m7. Tmobile.
- Bootloader - Unlocked
- S- ON
- Rooted
I kept getting a OTA software update notice for 5.14xxx, i understand the install kept failing due to the bootloader being unlocked and/or root. So after being annoyed for not able to get it, i began googling ways to get the update but to no avail. So i decided to do CM11, & recovery which i installed with no problem via, Cyanogenmod Installer.
After doing so, i realized i lost my Tmobile Wifi Calling (Yes, my own fault for not further checking that scenario before doing cm11), The wifi calling is needed 10000%, due to bad service in my apartment. Prior to finding out that cm11 doesnt contain the tmobile wifi calling , I attempted another system update thru the phone, (I assume it was updating cm11).
This is where the problem began, phone rebooted to Cyanogenmod simple recovery ,
1st few times that i tried = "apply update" > choose from internal storage , i searched different folders for the "update" file, but to no avail. The phone wouldnt start up, or install anything , and will just stay on the simple recovery. I even attempted an adb sideload. But couldnt figure that out correctly either.
After a few failed attempts, I tried wiping the phone, cache, factory reset etc. now the phone still stays on simple recovery, and all folders are gone, except for an o/ folder, that contains a clockworkmod folder, which contains nothing.
So now basically,Do i have to eventually get back to STOCK on this phone, to regain tmobile wifi calling ? IF So i need the easiest, mac friendly route to go .
Again, i thank you ALLLLL in advance, & my apologies if this is in the wrong section. Please note ive done my fair share of googling , and reading up on this. But consistently run into a problem.
OnlyEYEShine said:
Good afternoon, !!!
First and foremost , I want to thank you all in advance for ANY and help, time & consideration with my current issue. I will try my best to be clear, and give all relevant info here in my first post. Please bear with me, I am pretty good when it comes to following directions, but i havent been able to find a CLEAR solution to this yet, and worried about further screwing up my phone.
** I use a mac. I currently dont have access to a PC, so i am looking for a mac remedy if possible.
I have an HTCONE m7. Tmobile.
- Bootloader - Unlocked
- S- ON
- Rooted
I kept getting a OTA software update notice for 5.14xxx, i understand the install kept failing due to the bootloader being unlocked and/or root. So after being annoyed for not able to get it, i began googling ways to get the update but to no avail. So i decided to do CM11, & recovery which i installed with no problem via, Cyanogenmod Installer.
After doing so, i realized i lost my Tmobile Wifi Calling (Yes, my own fault for not further checking that scenario before doing cm11), The wifi calling is needed 10000%, due to bad service in my apartment. Prior to finding out that cm11 doesnt contain the tmobile wifi calling , I attempted another system update thru the phone, (I assume it was updating cm11).
This is where the problem began, phone rebooted to Cyanogenmod simple recovery ,
1st few times that i tried = "apply update" > choose from internal storage , i searched different folders for the "update" file, but to no avail. The phone wouldnt start up, or install anything , and will just stay on the simple recovery. I even attempted an adb sideload. But couldnt figure that out correctly either.
After a few failed attempts, I tried wiping the phone, cache, factory reset etc. now the phone still stays on simple recovery, and all folders are gone, except for an o/ folder, that contains a clockworkmod folder, which contains nothing.
So now basically,Do i have to eventually get back to STOCK on this phone, to regain tmobile wifi calling ? IF So i need the easiest, mac friendly route to go .
Again, i thank you ALLLLL in advance, & my apologies if this is in the wrong section. Please note ive done my fair share of googling , and reading up on this. But consistently run into a problem.
Click to expand...
Click to collapse
Here is a TWRP nandroid backup. You will have to put TWRP 2.6.3.3 on your phone. You will unzip the file and the resulting folder you will put on your phone in the following directory: //sdcard/TWRP/BACKUP/<Serial #>/<Name_of_folder>. If you are not able to get TWRP on your phone and the folder on your phone then you will need to find a Windows machine. Here is what you will need to do:
** Extract the RUU and grab the rom.zip file. This is the most important file you need from the RUU and afterwards you can delete the RUU exe if you want. To get the rom.zip from your RUU exe file, you just need to run the RUU exe file once, and then when the window is ready and waiting for you to press on the "Next" button, just leave it open and go to your temp folder. I'm using Windows XP SP3 32-bit and my temp folder is located at this path: C:\Documents and Settings\Administrator\Local Settings\Temp. Now, you will see several files and folders. Sort everything in that temp folder based on "Date Modified" with the most recent folder showing up above all other folders. This is the folder you want. The folder name will be bunch of letters and numbers. Inside that folder you will find several files, but what you need is rom.zip and android-info.txt. Copy both these files and paste them somewhere safe on your hard drive. The android-info.txt contains crucial information about the compatibility of that RUU for your phone.
** Go to your bootloader. Do:
Code:
fastboot oem lock
fastboot oem rebootRUU
This will reboot your HTC One and you will see a black screen with a silver HTC logo. Now, you will need to access the rom.zip file and flash it. I have copied my rom.zip to my adb folder located at: C:/mini-sdk/rom.zip. So, type:
Code:
fastboot flash zip C:/mini-sdk/rom.zip
Don't touch anything during the flash process. It will start and after some time, you will see FAILED error. Don't worry; it's the file preparation process if you have firmware higher than that of the RUU. Just do the same command again and the flash process will complete successfully this time. Look at the Command Prompt to know when the flash is complete. At the same time if you look at your phone, you will notice a green progress bar. When the flashing is complete on the Command Prompt, you will notice that the green bar is stuck at about 95%. This is normal. It's just a bug in the progress bar - what matters is the output from the Command Prompt window.
** Then, you reboot. Do:
Code:
fastboot reboot
This will restart your phone. Let it boot up. It might take a little longer for the first boot up sequence. You will then have completely stock software (firmware & ROM). Go to your bootloader and check that you are S-ON/OFF and Bootloader lock/unlock are unchanged from before the RUU rom.zip flashing procedure. You can now also receive OTA updates.
majmoz said:
Here is a TWRP nandroid backup. You will have to put TWRP 2.6.3.3 on your phone. You will unzip the file and the resulting folder you will put on your phone in the following directory: //sdcard/TWRP/BACKUP/<Serial #>/<Name_of_folder>. If you are not able to get TWRP on your phone and the folder on your phone then you will need to find a Windows machine. Here is what you will need to do:
** Extract the RUU and grab the rom.zip file. This is the most important file you need from the RUU and afterwards you can delete the RUU exe if you want. To get the rom.zip from your RUU exe file, you just need to run the RUU exe file once, and then when the window is ready and waiting for you to press on the "Next" button, just leave it open and go to your temp folder. I'm using Windows XP SP3 32-bit and my temp folder is located at this path: C:\Documents and Settings\Administrator\Local Settings\Temp. Now, you will see several files and folders. Sort everything in that temp folder based on "Date Modified" with the most recent folder showing up above all other folders. This is the folder you want. The folder name will be bunch of letters and numbers. Inside that folder you will find several files, but what you need is rom.zip and android-info.txt. Copy both these files and paste them somewhere safe on your hard drive. The android-info.txt contains crucial information about the compatibility of that RUU for your phone.
** Go to your bootloader. Do:
Code:
fastboot oem lock
fastboot oem rebootRUU
This will reboot your HTC One and you will see a black screen with a silver HTC logo. Now, you will need to access the rom.zip file and flash it. I have copied my rom.zip to my adb folder located at: C:/mini-sdk/rom.zip. So, type:
Code:
fastboot flash zip C:/mini-sdk/rom.zip
Don't touch anything during the flash process. It will start and after some time, you will see FAILED error. Don't worry; it's the file preparation process if you have firmware higher than that of the RUU. Just do the same command again and the flash process will complete successfully this time. Look at the Command Prompt to know when the flash is complete. At the same time if you look at your phone, you will notice a green progress bar. When the flashing is complete on the Command Prompt, you will notice that the green bar is stuck at about 95%. This is normal. It's just a bug in the progress bar - what matters is the output from the Command Prompt window.
** Then, you reboot. Do:
Code:
fastboot reboot
This will restart your phone. Let it boot up. It might take a little longer for the first boot up sequence. You will then have completely stock software (firmware & ROM). Go to your bootloader and check that you are S-ON/OFF and Bootloader lock/unlock are unchanged from before the RUU rom.zip flashing procedure. You can now also receive OTA updates.
Click to expand...
Click to collapse
Thanks for the info !!!,
But right off of the top, i am confused. I am currently downloading TMRP nandroid back up, as you said in beginning. Thing is i am unaware how to get that file onto my phone. Since it is stuck on the recovery page.... (DL is going to take a while on this machine), But if this fails, ill probably end up just tossing the phone, as i dont know anyone , nor have access to a PC machine. Sadly.
update - will attempt to push this thru via Terminal / adb will keep u posted !
-Update .. @majmoz well, i got hold of a PC laptop, did an adb / fastboot installed, dl'd the RUU, but i cant find the file from it after running the RUU. I even did cmd - Echo %temp% to make sure i was in the correct temp folder etc. Searched every sub folder there , and no zip files , or android.txt files was found . and i sorted them as u said as well.
Will continue trying tho...
Updated again - Well this time as RUU was installing again, i went to the temp files faster, and found 2 files Rom_01 & Rom_02 both zip files. But was unable to find any android text file. So now im at a standstill.
OnlyEYEShine said:
update - will attempt to push this thru via Terminal / adb will keep u posted !
-Update .. @majmoz well, i got hold of a PC laptop, did an adb / fastboot installed, dl'd the RUU, but i cant find the file from it after running the RUU. I even did cmd - Echo %temp% to make sure i was in the correct temp folder etc. Searched every sub folder there , and no zip files , or android.txt files was found . and i sorted them as u said as well.
Will continue trying tho...
Click to expand...
Click to collapse
The RUU Update Window should still be on the computer when you are looking for the files. Once the RUU goes past the first screen, the folder will be erased. You should also sort the /Temp folder by date so the most recent folder is at the top.
majmoz said:
The RUU Update Window should still be on the computer when you are looking for the files. Once the RUU goes past the first screen, the folder will be erased. You should also sort the /Temp folder by date so the most recent folder is at the top.
Click to expand...
Click to collapse
If i would of refreshed the page i would of seen your response, as i just re-editted my last post. with another update. =0)
I found 2 files with rom, Rom_01 & Rom_02 , both are zip files. but i cant find any android text file .
another thing, i am trying to find adb devices , but it is not locating my phone . I was able to earlier reboot into bootloader , etc. Now it tells me repeatedly that device is not found , i have tried adb kill-server, start-server etc. .. and phone is still on cyanogen simple recovery screen . .
Thanks again for ur time & help .. .definetly is appreciated !
OnlyEYEShine said:
If i would of refreshed the page i would of seen your response, as i just re-editted my last post. with another update. =0)
I found 2 files with rom, Rom_01 & Rom_02 , both are zip files. but i cant find any android text file .
another thing, i am trying to find adb devices , but it is not locating my phone . I was able to earlier reboot into bootloader , etc. Now it tells me repeatedly that device is not found , i have tried adb kill-server, start-server etc. .. and phone is still on cyanogen simple recovery screen . .
Thanks again for ur time & help .. .definetly is appreciated !
Click to expand...
Click to collapse
Keep both ROM files and save them for future use. Since you are able to use the PC, I would just run the RUU from the PC. Then in the future try to figure out how to run the two ROM files on your Mac. Just start the RUU again and let it do its thing.
majmoz said:
Keep both ROM files and save them for future use. Since you are able to use the PC, I would just run the RUU from the PC. Then in the future try to figure out how to run the two ROM files on your Mac. Just start the RUU again and let it do its thing.
Click to expand...
Click to collapse
Hey hey , good morning. Had some errands to do last nite then fell asleep. Going to attempt this again today . Oh, and i did run the RUU on the PC so thats where ill keep them also.
Will attempt to see if i can even connect to the phone with ADB, it seemed as if i was unable to last nite.
-update I got the phone to load to bootloader, & to fastboot usb I will try now to attempt this after coffee.. =0)
HAHAHAHHAHA ,, Oh man. Ok well being that it was pretty late last nite, and i had just woken up earlier .... I didnt realize that the RUU actually does the entire process on the PC. and that i DIDNT need to use cmd., and adb etc.
I want to thank you a TON @majmoz With my day or two of aggravation , then to just not get it right last nite.. I think i wasnt there mentally to actually read and pay attention.
My phone is in set up mode now. So i am 99% sure it is all good... Again, thanks , i definetly appreciate it !
OnlyEYEShine said:
HAHAHAHHAHA ,, Oh man. Ok well being that it was pretty late last nite, and i had just woken up earlier .... I didnt realize that the RUU actually does the entire process on the PC. and that i DIDNT need to use cmd., and adb etc.
I want to thank you a TON @majmoz With my day or two of aggravation , then to just not get it right last nite.. I think i wasnt there mentally to actually read and pay attention.
My phone is in set up mode now. So i am 99% sure it is all good... Again, thanks , i definetly appreciate it !
Click to expand...
Click to collapse
Glad you are back in business! :good:
@majmoz Hey i tried sending a PM earlier . but i see it never went thru in my sent Messages.
Just wondering if you can help me one last time. As i stated, i MUST have tmobile wifi calling. I initially had my bootloader unlocked months ago, and only rooted it few days before this brick issue.
Now since i did this process to fix the phone, i see bootloader = Relocked.
I dont want to add any custom roms etc, I simple want to root the device again. I know when i just did it , it was quick n easy and simple. But as im googling for the process now, i cant seem to find any that is similar to what i just did a few days ago. The processes seem extremely long. I think i just added a superuser apk of sorts , and it rooted.
Thanks again !
OnlyEYEShine said:
@majmoz Hey i tried sending a PM earlier . but i see it never went thru in my sent Messages.
Just wondering if you can help me one last time. As i stated, i MUST have tmobile wifi calling. I initially had my bootloader unlocked months ago, and only rooted it few days before this brick issue.
Now since i did this process to fix the phone, i see bootloader = Relocked.
I dont want to add any custom roms etc, I simple want to root the device again. I know when i just did it , it was quick n easy and simple. But as im googling for the process now, i cant seem to find any that is similar to what i just did a few days ago. The processes seem extremely long. I think i just added a superuser apk of sorts , and it rooted.
Thanks again !
Click to expand...
Click to collapse
Here is a step by step guide with pictures. This is called the HTCDev method and it is pretty standard. It just looks like a lot of steps but it isn't that bad.
majmoz said:
Here is a step by step guide with pictures. This is called the HTCDev method and it is pretty standard. It just looks like a lot of steps but it isn't that bad.
Click to expand...
Click to collapse
Gotcha, will try this in an hour or so . Have some errands to run. Thanks again !
OnlyEYEShine said:
Gotcha, will try this in an hour or so . Have some errands to run. Thanks again !
Click to expand...
Click to collapse
Keep this for future reference on how to flash the two RUU ROM zip files:
From nkk71's SuperGUIDE to returning 100% back to stock - Post #1211
http://forum.xda-developers.com/showpost.php?p=55921790&postcount=1211
How to flash two RUU ROM zip files
Code:
[B]fastboot oem rebootRUU
fastboot flash zip RUU_ROM_1.zip [COLOR="Red"][I]<-- hboot preupdate[/I][/COLOR]
fastboot flash zip RUU_ROM_1.zip[COLOR="Red"][I] <-- rest of the files in "1"[/I][/COLOR]
fastboot flash zip RUU_ROM_2.zip [I][COLOR="Red"]<-- files in "2" (kernel, touchscreen drivers 2, wipe userdate)[/COLOR][/I]
fastboot reboot-bootloader
[/B]
Click to expand...
Click to collapse
Alright, I somewhat hate Android 6.0, and that's because of my hard time rooting my Nexus 6, which is, at this point, becoming immensely irritating. If I'm allowed to do so here, since this is a Q&A board, I need to ask how the hell to root this thing, because of Android's new thing where I have to install a custom kernal to get root.
All I really know, now, ids that I need to unlock the bootloader of the phone, which I've been trying to do (installed SDK's platform tools, made sure my Nexus 6 Windows drivers are installed, but when I open a command prompt to unlock the bootloader, I'm met with a, "no devices found," response, so I have no clue what to do, and need some help, because with how many tutorials I've looked up for how to do this, and none of them working, I'm about heady to break my monitor. If anyone can explain what the **** I'm doing wrong, or link to a tutorial for how to unlock the bootloader, that actually explains what's needed to do so, it'd be appreciated.
Da-JesuZ said:
Alright, I somewhat hate Android 6.0, and that's because of my hard time rooting my Nexus 6, which is, at this point, becoming immensely irritating. If I'm allowed to do so here, since this is a Q&A board, I need to ask how the hell to root this thing, because of Android's new thing where I have to install a custom kernal to get root.
All I really know, now, ids that I need to unlock the bootloader of the phone, which I've been trying to do (installed SDK's platform tools, made sure my Nexus 6 Windows drivers are installed, but when I open a command prompt to unlock the bootloader, I'm met with a, "no devices found," response, so I have no clue what to do, and need some help, because with how many tutorials I've looked up for how to do this, and none of them working, I'm about heady to break my monitor. If anyone can explain what the **** I'm doing wrong, or link to a tutorial for how to unlock the bootloader, that actually explains what's needed to do so, it'd be appreciated.
Click to expand...
Click to collapse
This is how i always root the phone:
- Enable usb debugging and ENABLE OEM UNLOCKING in developer options
- Reboot into the bootloader and type fastboot oem unlock and let the phone boot up
- Flash TWRP in fastboot
- Go to recovery and flash a modified boot.zip (all custom kernels will do)
- Flash the latest superSU.zip, also in recovery
- Done
Here is a tut for the adb setup (Windows) http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/.
- Reboot into the bootloader and type fastboot oem unlock and let the phone boot up
That's my problem. Opening up the command prompt and typing, "fastboot OEM unlock," does absolutely nothing. No prompts come up on the phone. It just sits there, and doesn't do anything.
Da-JesuZ said:
- Reboot into the bootloader and type fastboot oem unlock and let the phone boot up
That's my problem. Opening up the command prompt and typing, "fastboot OEM unlock," does absolutely nothing. No prompts come up on the phone. It just sits there, and doesn't do anything.
Click to expand...
Click to collapse
Do you see a serial number in fastboot if you type: fastboot devices? If not your drivers aren`t installed correctly or adb isn`t setup correctly.
gee2012 said:
Do you see a serial number in fastboot if you type: fastboot devices? If not your drivers aren`t installed correctly or adb isn`t setup correctly.
Click to expand...
Click to collapse
I'm using Windows Vista, so I had to add an underscore, and type, "fastboot oem_unlock," to get the bootloader unlocked. Everything is restoring, now, however, I'm wondering if I'll have to do something similar with flashing TWRP, and the kernal I'm attempting to install. I don't know programming or cmd commands.
Da-JesuZ said:
I'm using Windows Vista, so I had to add an underscore, and type, "fastboot oem_unlock," to get the bootloader unlocked. Everything is restoring, now, however, I'm wondering if I'll have to do something similar with flashing TWRP, and the kernal I'm attempting to install. I don't know programming or cmd commands.
Click to expand...
Click to collapse
You only have to flash the TWRP.img file in fastboot, the rest (boot/superSU) are zip files to be flashed in recovery. I have no experience with Vista so can`t help you there, maybe there is some info about it on Google/YouTube.