These are the original steps I used
https://www.youtube.com/watch?v=QU7vi388dMk
I just followed the bootloader instructions and then followed the way to root the phone.
TWRP
SuperSU
From the video used.
Alright so I'll start from the top, I have the HTC One M7 from T-Mobile and I purchased a Straight Talk SIM plus service and went to install everything.
I was originally on T-Mobile but they upped my bill to 80 a month, so I switched to MetroPCS but MetroPCS is really slow down here so I decided to switch to Straight Talk but I just read online that they are both on the T-Mobile network and are both the same in regards to speed...(so my mess up I guess? Unless that's not right.) I am in Tuscon, AZ.
Anyways, I tried changing the APN and it just kept disappearing I used the most basic setting at first and it kept switching to the LOCKED T-Mobile APN and the internet/mms won't work only calling/texting.
So I tried using a more advanced APN and instead it just disappeared, it won't save even after I touch "Save" so my search began and I saw things about Sunshine but I didn't buy this phone outright I got it a year ago online for 200$ and I am completely broke right now so I can't afford the 25$ but I need to be able to use my phone because I already paid for the coverage (Straight Talk) and I am trying to get in contact with a potential job.
So to reiterate I used both basic and more detailed APN information neither works, first one saves but goes back to T-Mobile's APN, second one doesn't save at all it disappears. I went to Straight Talk and got the APN information but once again nothing worked.
So I read online about using Titanium Backup and converting APN Backup And Restore to a system app so I can alter the APN, but I every time I tried using TB(I paid for it by the way so I can use the full version) it would hang on, "Processing please wait" I waited well over thirty minutes. I restarted my phone and for some reason the app was deleted.
So I continued to look more and found out about the S-Lock and Rumrunner, so I continued on with that and tried using Rumrunner but the ADB thing wasn't installed so I used this link, (http://forum.xda-developers.com/showthread.php?p=48915118) tried again and I got all the way to the end (after disabling firewall/antivirus) and was stuck with the "Get unsecured" kernel error, the "Choose one of two options, bye!!!" message. So I looked into that as well, I found this one called, TrickDroid ROM (https://www.youtube.com/watch?v=5KEesTRHixE) I did all the backing up using TWRP and TB then proceeded to go to (http://lifehacker.com/how-to-flash-a-rom-to-your-android-phone-30885281) I put the ZIP file in my phone then went to TWRP recovery, I went to install it and it just hanged on the "Flashing 1 of 1" I found out that it had something to do with, "Mounting" or whatever in TWRP and I didn't so I restarted my phone.
I tried going back into recovery mode after the restart multiple times and it wouldn't work, I picked it and it just loaded into FASTBOOT every time and wouldn't load the recovery mode. So, once again, I looked into this and found Squabbi's HTC One tool kit, 3.2. I downloaded it and got it to work on my phone, I followed these instructions, (http://forums.androidcentral.com/ht...48-htc-one-won-t-boot-into-twrp-recovery.html)
Reboot to HBOOT
select FASTBOOT to get to FASTBOOT USB mode
Make sure the device is in and you have fastboot on your machine
fastboot flash the recovery image
Immediately try to go into the recovery via the HBOOT menu
If no dice, reboot the system and make sure "fast boot" is unchecked in the power options. It might be unrelated, but still: do it.
Go back and try again, but after flashing recovery, reboot the bootloader and then immediately go to recovery.
If successful, reboot system then reboot back into HBOOT and then to recovery to confirm.
I went into the tool and used "Recovery," I downloaded the TWRP one for T-Mobile and clicked on, "Reboot Bootloader" then it restarted my phone and put me in the white screen, I did the flash recovery and everything went through so I went into recovery.
This is where I am at right now, I went into recovery and TWRP is saying I have 0MB internal storage but when I plug the phone to my computer I can see everything is still installed. Also, usually I read online when people have this problem their phone doesn't work at all, strangely enough mine will boot into the OS and allow me to make phone calls text and use apps, so basically the phone ITSELF is unaffected, which I haven't seen on here so either I'm a crazy exception or people just don't post a lot on here.
I also went back into Squabbi's tool and got the error that my device is offline and now I just got the error (Permission Denied)
To reiterate, my TWRP says 0MB internal storage after doing a flash recovery and I went to "Wipe" and cleared the dvleck (or something) and the cache before trying to do the install of the ROM trickdroid but my phone still completely functions.
My HBB is 1.7 I believe and I am not sure what other information you'll need, all the sites referenced above is everything I've tried and used. I know Straight Talk works on this phone because as long as I can set the APN I can successfully use it.
Please don't respond with, "If you can afford this phone blahblah code" I could afford the phone two years ago when I had a job and money, but that doesn't mean I can afford the code.
If there's anyone that can help me I'd really appreciate it.
neitousama said:
These are the original steps I used
https://www.youtube.com/watch?v=QU7vi388dMk
I just followed the bootloader instructions and then followed the way to root the phone.
TWRP
SuperSU
From the video used.
Alright so I'll start from the top, I have the HTC One M7 from T-Mobile and I purchased a Straight Talk SIM plus service and went to install everything.
I was originally on T-Mobile but they upped my bill to 80 a month, so I switched to MetroPCS but MetroPCS is really slow down here so I decided to switch to Straight Talk but I just read online that they are both on the T-Mobile network and are both the same in regards to speed...(so my mess up I guess? Unless that's not right.) I am in Tuscon, AZ.
Anyways, I tried changing the APN and it just kept disappearing I used the most basic setting at first and it kept switching to the LOCKED T-Mobile APN and the internet/mms won't work only calling/texting.
So I tried using a more advanced APN and instead it just disappeared, it won't save even after I touch "Save" so my search began and I saw things about Sunshine but I didn't buy this phone outright I got it a year ago online for 200$ and I am completely broke right now so I can't afford the 25$ but I need to be able to use my phone because I already paid for the coverage (Straight Talk) and I am trying to get in contact with a potential job.
So to reiterate I used both basic and more detailed APN information neither works, first one saves but goes back to T-Mobile's APN, second one doesn't save at all it disappears. I went to Straight Talk and got the APN information but once again nothing worked.
So I read online about using Titanium Backup and converting APN Backup And Restore to a system app so I can alter the APN, but I every time I tried using TB(I paid for it by the way so I can use the full version) it would hang on, "Processing please wait" I waited well over thirty minutes. I restarted my phone and for some reason the app was deleted.
So I continued to look more and found out about the S-Lock and Rumrunner, so I continued on with that and tried using Rumrunner but the ADB thing wasn't installed so I used this link, (http://forum.xda-developers.com/showthread.php?p=48915118) tried again and I got all the way to the end (after disabling firewall/antivirus) and was stuck with the "Get unsecured" kernel error, the "Choose one of two options, bye!!!" message. So I looked into that as well, I found this one called, TrickDroid ROM (https://www.youtube.com/watch?v=5KEesTRHixE) I did all the backing up using TWRP and TB then proceeded to go to (http://lifehacker.com/how-to-flash-a-rom-to-your-android-phone-30885281) I put the ZIP file in my phone then went to TWRP recovery, I went to install it and it just hanged on the "Flashing 1 of 1" I found out that it had something to do with, "Mounting" or whatever in TWRP and I didn't so I restarted my phone.
I tried going back into recovery mode after the restart multiple times and it wouldn't work, I picked it and it just loaded into FASTBOOT every time and wouldn't load the recovery mode. So, once again, I looked into this and found Squabbi's HTC One tool kit, 3.2. I downloaded it and got it to work on my phone, I followed these instructions, (http://forums.androidcentral.com/ht...48-htc-one-won-t-boot-into-twrp-recovery.html)
Reboot to HBOOT
select FASTBOOT to get to FASTBOOT USB mode
Make sure the device is in and you have fastboot on your machine
fastboot flash the recovery image
Immediately try to go into the recovery via the HBOOT menu
If no dice, reboot the system and make sure "fast boot" is unchecked in the power options. It might be unrelated, but still: do it.
Go back and try again, but after flashing recovery, reboot the bootloader and then immediately go to recovery.
If successful, reboot system then reboot back into HBOOT and then to recovery to confirm.
I went into the tool and used "Recovery," I downloaded the TWRP one for T-Mobile and clicked on, "Reboot Bootloader" then it restarted my phone and put me in the white screen, I did the flash recovery and everything went through so I went into recovery.
This is where I am at right now, I went into recovery and TWRP is saying I have 0MB internal storage but when I plug the phone to my computer I can see everything is still installed. Also, usually I read online when people have this problem their phone doesn't work at all, strangely enough mine will boot into the OS and allow me to make phone calls text and use apps, so basically the phone ITSELF is unaffected, which I haven't seen on here so either I'm a crazy exception or people just don't post a lot on here.
I also went back into Squabbi's tool and got the error that my device is offline and now I just got the error (Permission Denied)
To reiterate, my TWRP says 0MB internal storage after doing a flash recovery and I went to "Wipe" and cleared the dvleck (or something) and the cache before trying to do the install of the ROM trickdroid but my phone still completely functions.
My HBB is 1.7 I believe and I am not sure what other information you'll need, all the sites referenced above is everything I've tried and used. I know Straight Talk works on this phone because as long as I can set the APN I can successfully use it.
Please don't respond with, "If you can afford this phone blahblah code" I could afford the phone two years ago when I had a job and money, but that doesn't mean I can afford the code.
If there's anyone that can help me I'd really appreciate it.
Click to expand...
Click to collapse
First for your 0mb storage in twrp, this issue is in most cases caused by a corrupted data partition which is probably not your case since your phone is working fine. You might not have installed the right twrp version. Can you post a link to the exact version of TWRP you have flashed?
For your APN issue, I'm presuming your phone is already sim-unlocked right? That might only be an issue with the stock T-MOB rom not allowing you to edit the APN. You'll probably be fine after flashing another rom.
S-off (rumrunner) is not related to APN problems. + Rumrunner won't work on hboot 1.57, only Sunshine will but anyway S-OFF is not really needed if you can fix it by flashing a rom.
So make sure you flash the right twrp version for GSM (2.8.6.0) then make a nandroid backup of your current config (and better to make a copy of this backup on your computer) and then see if the 0mb issue is solved, if yes flash your rom and try to set your APN again, If its still says 0mb then you'll have to fix the corrupted partitions.
alray said:
First for your 0mb storage in twrp, this issue is in most cases caused by a corrupted data partition which is probably not your case since your phone is working fine. You might not have installed the right twrp version. Can you post a link to the exact version of TWRP you have flashed?
For your APN issue, I'm presuming your phone is already sim-unlocked right? That might only be an issue with the stock T-MOB rom not allowing you to edit the APN. You'll probably be fine after flashing another rom.
S-off (rumrunner) is not related to APN problems. + Rumrunner won't work on hboot 1.57, only Sunshine will but anyway S-OFF is not really needed if you can fix it by flashing a rom.
So make sure you flash the right twrp version for GSM then make a nandroid backup of your current config (and better to make a copy of this backup on your computer) and then see if the 0mb issue is solved, if yes flash your rom and try to set your APN again, If its still says 0mb then you'll have to fix the corrupted partitions.
Click to expand...
Click to collapse
Well I searched high and low and I finally found this thing called, ".img" and it was the original android one supposedly, so I used the toolkit to flash it and I guess it wiped everything off my phone and now it's factory again, strangely enough on the white screen it still says "Tampered" "Unlocked" so now I guess I just have to run through the motions again?
I am so new to this, I only unlocked/rooted/custom recovery'd my phone so that I can hack into some games I was playing to have more fun but after this whole issue with the Straight Talk thing I realized I had to go far above and beyond..
The link for TWRP is htconem7gsm
(Wouldn't let me post the link)
Are there like manuals online on how to do this? I see so many threads, so many questions so many different ways of doing all this and it's VERY confusing.
For instance, I saw something about bulletproof and liquidsmooth, what are those? Now that I have more information, once I can change the APN I would like to install the cream of the crop, if possible.
I believe my phone is sim unlocked, when I put in the new sim card it doesn't say sim read error or anything and it lets me make calls/texts but it won't let me access the web or do MMS because of the APN settings.
I just would like some step by steps on how to change the APN and get all these things back on my android, I don't like the stock stuff so.
My first initial change was going to use Titanium Back-up to make APN Backup And Restore a system app so I could change the APN since the phone locked out my ability to use 3rd party apps to change it, but to change that to a system app required s-off, so...
I've just been sitting here rattling my brain trying to figure this out. If you can help that'd be amazing..
Thanks for the response by the way.
neitousama said:
Well I searched high and low and I finally found this thing called, ".img" and it was the original android one supposedly, so I used the toolkit to flash it and I guess it wiped everything off my phone and now it's factory again, strangely enough on the white screen it still says "Tampered" "Unlocked" so now I guess I just have to run through the motions again?
I am so new to this, I only unlocked/rooted/custom recovery'd my phone so that I can hack into some games I was playing to have more fun but after this whole issue with the Straight Talk thing I realized I had to go far above and beyond..
The link for TWRP is htconem7gsm
(Wouldn't let me post the link)
Are there like manuals online on how to do this? I see so many threads, so many questions so many different ways of doing all this and it's VERY confusing.
For instance, I saw something about bulletproof and liquidsmooth, what are those? Now that I have more information, once I can change the APN I would like to install the cream of the crop, if possible.
I believe my phone is sim unlocked, when I put in the new sim card it doesn't say sim read error or anything and it lets me make calls/texts but it won't let me access the web or do MMS because of the APN settings.
I just would like some step by steps on how to change the APN and get all these things back on my android, I don't like the stock stuff so.
My first initial change was going to use Titanium Back-up to make APN Backup And Restore a system app so I could change the APN since the phone locked out my ability to use 3rd party apps to change it, but to change that to a system app required s-off, so...
I've just been sitting here rattling my brain trying to figure this out. If you can help that'd be amazing..
Thanks for the response by the way.
Click to expand...
Click to collapse
Start over from scratch
First get rid of any tool kits and instead, install adb and fastboot. Minimal adb and fastboot will work fine.
flash TWRP recovery 2.8.6.0:
Download twrp 2.8.6.0 and save it in the same folder you have installed minimal adb and fastboot (C:\Programs\minimal adb and fastboot\)
boot in bootloader mode, select fastboot so "fastboot usb" is shown in red.
open a fastboot terminal window (start menu --> program --> minimal and and fastboot --> minimal adb and fastboot)
type:
Code:
fastboot flash recovery twrp-2.8.6.0-m7.img
fastboot erase cache
fastboot reboot-bootloader
Then boot in twrp recovery. Does it still says 0 mb?
alray said:
Start over from scratch
First get rid of any tool kits and instead, install adb and fastboot. Minimal adb and fastboot will work fine.
flash TWRP recovery 2.8.6.0:
Download twrp 2.8.6.0 and save it in the same folder you have installed minimal adb and fastboot (C:\Programs\minimal adb and fastboot\)
boot in bootloader mode, select fastboot so "fastboot usb" is shown in red.
open a fastboot terminal window (start menu --> program --> minimal and and fastboot --> minimal adb and fastboot)
type:
Code:
fastboot flash recovery twrp-2.8.6.0-m7.img
fastboot erase cache
fastboot reboot-bootloader
Then boot in twrp recovery. Does it still says 0 mb?
Click to expand...
Click to collapse
Well this is unusual, whenever I tried opening it from the desktop icon it just takes me to command prompt, when I go to the folder (Located in x86 I'm running Windows 8) and I try opening fastboot or adb and a bunch of text from a command prompt-looking thing shows up, flashes quickly and then closes again.
What did I do wrong?
alray said:
Start over from scratch
First get rid of any tool kits and instead, install adb and fastboot. Minimal adb and fastboot will work fine.
flash TWRP recovery 2.8.6.0:
Download twrp 2.8.6.0 and save it in the same folder you have installed minimal adb and fastboot (C:\Programs\minimal adb and fastboot\)
boot in bootloader mode, select fastboot so "fastboot usb" is shown in red.
open a fastboot terminal window (start menu --> program --> minimal and and fastboot --> minimal adb and fastboot)
type:
Code:
fastboot flash recovery twrp-2.8.6.0-m7.img
fastboot erase cache
fastboot reboot-bootloader
Then boot in twrp recovery. Does it still says 0 mb?
Click to expand...
Click to collapse
Nevermind I go it to work I swear sometimes things can be so whacky,
No now it's showing the internal data amount, it's not zero anymore.
Now what?
Well I managed to get twrp back on and installed....only issue now is where do I go for the APN stuff?
I appreciate all your help...whenever you get back online I really need to know the rest.
neitousama said:
Well I managed to get twrp back on and installed....only issue now is where do I go for the APN stuff?
I appreciate all your help...whenever you get back online I really need to know the rest.
Click to expand...
Click to collapse
Now that you have twrp correctly installed on your phone, copy the rom you want to flash on your phone storage then in twrp go to "install" and flash the rom. After the phone reboot try to configure your new apn (settings ---> mobile data --> access point name
alray said:
Now that you have twrp correctly installed on your phone, copy the rom you want to flash on your phone storage then in twrp go to "install" and flash the rom. After the phone reboot try to configure your new apn (settings ---> mobile data --> access point name
Click to expand...
Click to collapse
Where do I find those? Is bulletproof the best?
Also, when I tried installing that one ROM the trickdroid, it just hanged on the flash screen, someone said I needed to mount or something of the sort before flashing ROM? I am unsure...I'm a noob...sorry
neitousama said:
Where do I find those?
Click to expand...
Click to collapse
In the rom section of this forum
Is bulletproof the best?
Click to expand...
Click to collapse
Bulletproof isn't a rom its a kernel
Also, when I tried installing that one ROM the trickdroid, it just hanged on the flash screen
Click to expand...
Click to collapse
and you were installing it using the wrong recovery... If trickdroid is the rom you want then it should flash fine now. WOuld suggest to use a rom like maximus. arhd or insertcoin.
Related
ok, so I used the all-in-one tool kit (from the development area) to root my phone. The CWM went fine. I tried to flash the explosion rom (developers area again) and when it rebooted it went into the "development purposes only" screen. I can boot into bootloader and access the hboot and fastboot options. I tried going into recovery and factory reset, but it just reboots into the developer screen again. Any advice on how to remedy this is greatly appreciated!!!
Thank you
Missing customize/mns and cid folder, flash other rom to fix.
desirech4cker said:
Missing customize/mns and cid folder, flash other rom to fix.
Click to expand...
Click to collapse
I hate to say it, but can you dumb that down a bit... I am a bit of a noob
.
Dumb version: the dev that made the rom removed folder mns and cid folder to remove htc sense stuff which is needed for htc framework, or has some missing values in the xml, if you still don't understand ask it in the explosion rom thread about the bug.
desirech4cker said:
.
Dumb version: the dev that made the rom removed folder mns and cid folder to remove htc sense stuff which is needed for htc framework, or has some missing values in the xml, if you still don't understand ask it in the explosion rom thread about the bug.
Click to expand...
Click to collapse
ok, thanks., I clicked the button for ya. So, I got the why it happened, still not sure what to do now. I did the CWM before, but now when I try to boot to recovery, it kicks me back to the "developer screen." I've tried redoing the CWM, but still can't get into it, so I don't know how to wipe everything and/or flash a new rom.
Connect phone to usb turned on even it's on developer screen or on homescreen type "adb reboot recovery" in windows cmd, be sure your on adb folder when you used to unlock your bootloader.
Then it will shut off and be in recovery, if still can't go to recovery reflash recovery.img typing "fastboot flash recovery recovery.img" in bootloader mode, then go back to fastboot and choose recovery.
desirech4cker said:
Connect phone to usb turned on even it's on developer screen or on homescreen type "adb reboot recovery" in windows cmd, be sure your on adb folder when you used to unlock your bootloader.
Then it will shut off and be in recovery, if still can't go to recovery reflash recovery.img typing "fastboot flash recovery recovery.img" in bootloader mode, then go back to fastboot and choose recovery.
Click to expand...
Click to collapse
rebooted to recovery, kicked back to "dev screen", flashed recovery.img (cwm), successful. Returned to bootlloader, clicked recovery, kicked back to "dev screen." Any other ideas? I don't know if I can click that button multiple time, but I'm going to try and I really appreciate your patience.
Ok, So I played pissed off retail customer and got them to replace my phone... Love it...
Anyways, I just had one question before I risk tanking another phone. I know a lot of people run GSM, but mine is CDMA, can I root, and run the unknown rom as laid out in the noob guide in the general discussion area? or was that part of my problem in the first place?
gsxrrocker said:
Ok, So I played pissed off retail customer and got them to replace my phone... Love it...
Anyways, I just had one question before I risk tanking another phone. I know a lot of people run GSM, but mine is CDMA, can I root, and run the unknown rom as laid out in the noob guide in the general discussion area? or was that part of my problem in the first place?
Click to expand...
Click to collapse
You could do it but I think you might lose access to your network because of the different radios but I'm not 100% sure.
If you are gonna try tho you should probably make sure you have a ruu for your network (if you can find one) so you can flash it back if anything goes wrong.
Sent from my HTC Desire C using xda app-developers app
You can't flash roms bcoz it's all for GSM that's why you got problems.
gsxrrocker said:
ok, so I used the all-in-one tool kit (from the development area) to root my phone. The CWM went fine. I tried to flash the explosion rom (developers area again) and when it rebooted it went into the "development purposes only" screen. I can boot into bootloader and access the hboot and fastboot options. I tried going into recovery and factory reset, but it just reboots into the developer screen again. Any advice on how to remedy this is greatly appreciated!!!
Thank you
Click to expand...
Click to collapse
Wait...how did you gain root and what recovery were you trying to flash that ROM with. My CDMA Desire C will not root or boot into recovery. The superuser script requires you to be able to boot a custom recovery to flash it...and all I get is the developer screen error like you. AI have posted for how to find info on building a recovery for the CDMA version, but noone has responded. And there are no sources for our CDMA version listed, which I complained to HTC about. But they misunderstood my complaint as a complaint that we were not upgraded to JB yet...dummköpfe
Hi I was rooting my HTC one and was able to do so successfully. Then I tried to flash roms and it didn't work with TWRP so I tried clockwork. That's when everything went to hell. I was stuck in the bootloader loop and it just kept booting to that. Then I tried to follow this guide
http://forum.xda-developers.com/showthread.php?t=2258809
and I did method 1 but when I ran one of the commands I saw failed. Now my HTC One is just stuck on the screen with a silver HTC logo and I can't even turn it off. I would really appreciate any insights and advice. I tried doing it on my own but clearly I kept ****ing up and could really use some help.
limache said:
Hi I was rooting my HTC one and was able to do so successfully. Then I tried to flash roms and it didn't work with TWRP so I tried clockwork. That's when everything went to hell. I was stuck in the bootloader loop and it just kept booting to that. Then I tried to follow this guide
http://forum.xda-developers.com/showthread.php?t=2258809
and I did method 1 but when I ran one of the commands I saw failed. Now my HTC One is just stuck on the screen with a silver HTC logo and I can't even turn it off. I would really appreciate any insights and advice. I tried doing it on my own but clearly I kept ****ing up and could really use some help.
Click to expand...
Click to collapse
This is a softbrick not a (hard)brick. this is fixable. Try putting it under a bright light and holding down pwr + vol dwn (dont ask just do it) and see if the soft buttons start blinking. if so, you should feel a buzz when it reboots, and then keep holding down vol dwn and that should put you into bootloader. from there you can get to fastboot (and maybe even recovery)
Toxicoblivion said:
This is a softbrick not a (hard)brick. this is fixable. Try putting it under a bright light and holding down pwr + vol dwn (dont ask just do it) and see if the soft buttons start blinking. if so, you should feel a buzz when it reboots, and then keep holding down vol dwn and that should put you into bootloader. from there you can get to fastboot (and maybe even recovery)
Click to expand...
Click to collapse
I've got to ask. A bright light? Is he doing surgery as well? What's the reason for the light?
Sent from my HTCONE using xda premium
Quis89 said:
I've got to ask. A bright light? Is he doing surgery as well? What's the reason for the light?
Sent from my HTCONE using xda premium
Click to expand...
Click to collapse
for some reason multiple people have reported successful reboots under bright light in which previously (sometimes within minutes) earlier would not work in a dark environment. i have no idea why it works, but ive heard it work enough times, its worth adding it in.
Toxicoblivion said:
for some reason multiple people have reported successful reboots under bright light in which previously (sometimes within minutes) earlier would not work in a dark environment. i have no idea why it works, but ive heard it work enough times, its worth adding it in.
Click to expand...
Click to collapse
It's thought this is a safety feature so that you can't accidentally long press power and restart in dark places like your pocket.
@rider5512 Sounds right to me. Thanks for clarifying.
Toxicoblivion said:
This is a softbrick not a (hard)brick. this is fixable. Try putting it under a bright light and holding down pwr + vol dwn (dont ask just do it) and see if the soft buttons start blinking. if so, you should feel a buzz when it reboots, and then keep holding down vol dwn and that should put you into bootloader. from there you can get to fastboot (and maybe even recovery)
Click to expand...
Click to collapse
Thanks Toxic!!- so I tried that and I'm back in the bootloader now! I guess the bright light made a difference as I messed up my phone last night. It didn't buzz but now I'm back in the bootloader. How should I go about fixing this now that I can access the bootloader and recovery? I really don't want to half ass this again lol.
It also says "TAMPERED" "RELOCKED" on the top as well.
I'm thinking of following the instructions for method 2 from this thread.
http://forum.xda-developers.com/showthread.php?t=2258809
Would this be correct or do I need to do anything else first?
limache said:
Thanks Toxic!!- so I tried that and I'm back in the bootloader now! I guess the bright light made a difference as I messed up my phone last night. It didn't buzz but now I'm back in the bootloader. How should I go about fixing this now that I can access the bootloader and recovery? I really don't want to half ass this again lol.
It also says "TAMPERED" "RELOCKED" on the top as well.
I'm thinking of following the instructions for method 2 from this thread.
http://forum.xda-developers.com/showthread.php?t=2258809
Would this be correct or do I need to do anything else first?
Click to expand...
Click to collapse
Method 2 looks good.
Just remember that you will have to unlock your bootloader again. You will probably have to request a new token at htcdev.
Then flash recovery from toolkit and sideload and install new rom.
crushalot said:
Method 2 looks good.
Just remember that you will have to unlock your bootloader again. You will probably have to request a new token at htcdev.
Then flash recovery from toolkit and sideload and install new rom.
Click to expand...
Click to collapse
Great I'm just concerned at getting this to work again.
EDIT - So I am trying method 2 right now - I am trying to boot into recovery but it just brings me back to bootloader. I cannot access recovery so when I try sideloading the rom it doesn't work. It says "error device not found" in cmd prompt but I already installed the HTC drivers though. Any advice?
So that means I have to go through the whole process of unlocking the bootloader and rooting it. So can I just use this tool by Hasoon2000 instead of going through manually typing in cmd prompts in the future?
In regards to requesting the new token, can you clarify? Are you saying that since I activated the old token, it cannot be activated anymore and I need to contact HTC Dev directly?
limache said:
Great I'm just concerned at getting this to work again.
EDIT - So I am trying method 2 right now - I am trying to boot into recovery but it just brings me back to bootloader. I cannot access recovery so when I try sideloading the rom it doesn't work. It says "error device not found" in cmd prompt but I already installed the HTC drivers though. Any advice?
So that means I have to go through the whole process of unlocking the bootloader and rooting it. So can I just use this tool by Hasoon2000 instead of going through manually typing in cmd prompts in the future?
In regards to requesting the new token, can you clarify? Are you saying that since I activated the old token, it cannot be activated anymore and I need to contact HTC Dev directly?
Click to expand...
Click to collapse
fastboot erase cache
limache said:
Great I'm just concerned at getting this to work again.
EDIT - So I am trying method 2 right now - I am trying to boot into recovery but it just brings me back to bootloader. I cannot access recovery so when I try sideloading the rom it doesn't work. It says "error device not found" in cmd prompt but I already installed the HTC drivers though. Any advice?
So that means I have to go through the whole process of unlocking the bootloader and rooting it. So can I just use this tool by Hasoon2000 instead of going through manually typing in cmd prompts in the future?
In regards to requesting the new token, can you clarify? Are you saying that since I activated the old token, it cannot be activated anymore and I need to contact HTC Dev directly?
Click to expand...
Click to collapse
You need to flash a new custom recovery again before you can boot into it and sideload. You won't be able to do that until you unlock your bootloader again.
You do have to do the whole process of unlocking the bootloader and installing a custom recovery from the toolkit.
You will need to get a new unlock token from htcdev (however you did it before, manually or with the toolkit) since you can only use the unlock token's once it seems. No biggie, just need to do the process again to get that new token you will need to unlock you bootloader before you will be able to do anything in recovery.
crushalot said:
You need to flash a new custom recovery again before you can boot into it and sideload. You won't be able to do that until you unlock your bootloader again.
You do have to do the whole process of unlocking the bootloader and installing a custom recovery from the toolkit.
You will need to get a new unlock token from htcdev (however you did it before, manually or with the toolkit) since you can only use the unlock token's once it seems. No biggie, just need to do the process again to get that new token you will need to unlock you bootloader before you will be able to do anything in recovery.
Click to expand...
Click to collapse
Thank you crushalot!
So I am following this guide.
http://htconeroot.com/htc-one-root/how-to-root-htc-one-windowsmaclinux/
I successfully unlocked the bootloader and now I need to flash the recovery. In Step 23, he copies the file "CWM-SuperSU-v1.30.zip" into the internal storage. Since I cannot access the internal storage of the phone, is this step necessary to flashing recovery? Can I just skip over to step 24 and run "fastboot flash recovery openrecovery-twrp-2.4.0.0-m7.img" ?
Edit - Okay so I used Hasoon's toolkit to flash the recovery and I think it worked. However, now I am trying to sideload the rom and having issues. I selected "ADB Sideload a ROM" and i manually went into recovery and TWRP (the toolkit can't send it into recovery for some reason). I selected "sideload a rom" on the HTC and then it shows you a bar that says "Swipe to sideload". I wasn't sure if I needed to do that or not but I tried running the toolkit and sideloading the rom and i got "error: closed" in command prompt.
in TWRP there are messages saying "unable to mount /data, recreate data/media folder, internal storage etc".
limache said:
Thank you crushalot!
So I am following this guide.
http://htconeroot.com/htc-one-root/how-to-root-htc-one-windowsmaclinux/
I successfully unlocked the bootloader and now I need to flash the recovery. In Step 23, he copies the file "CWM-SuperSU-v1.30.zip" into the internal storage. Since I cannot access the internal storage of the phone, is this step necessary to flashing recovery? Can I just skip over to step 24 and run "fastboot flash recovery openrecovery-twrp-2.4.0.0-m7.img" ?
Edit - Okay so I used Hasoon's toolkit to flash the recovery and I think it worked. However, now I am trying to sideload the rom and having issues. I selected "ADB Sideload a ROM" and i manually went into recovery and TWRP (the toolkit can't send it into recovery for some reason). I selected "sideload a rom" on the HTC and then it shows you a bar that says "Swipe to sideload". I wasn't sure if I needed to do that or not but I tried running the toolkit and sideloading the rom and i got "error: closed" in command prompt.
in TWRP there are messages saying "unable to mount /data, recreate data/media folder, internal storage etc".
Click to expand...
Click to collapse
"In Step 23, he copies the file "CWM-SuperSU-v1.30.zip" into the internal storage. Since I cannot access the internal storage of the phone, is this step necessary to flashing recovery? Can I just skip over to step 24 and run "fastboot flash recovery openrecovery-twrp-2.4.0.0-m7.img" ?"
That is done in order to give root access to the currently installed rom. You are going to install a new rom, so you don't have to do that until you get the rom installed.
You are now the 3rd user I have run into that is having the issue where you can't mount anything in recovery and I'm not sure why. Some users report that re locking and unlocking the bootloader fixes this, but you just did that, so I'm not sure why this is happening.
Within the toolkit try the perm root option? Perhaps there is something I can't think of since I rooted mine, the day I got it awhile back.
"Rooting The Device To root your device, first make sure you have unlocked the bootloader and installed a custom recovery. Next, select the ‘Perm Root’ option (the last one) from the Extras section and follow the instructions to get root access in no time."
To any other advanced users who may be able to answer this:
Does the recovery need the installed rom to have the SU binaries before it can mount the system in recovery? Does recovery need to be granted SU though some other means before mounting?
crushalot said:
"In Step 23, he copies the file "CWM-SuperSU-v1.30.zip" into the internal storage. Since I cannot access the internal storage of the phone, is this step necessary to flashing recovery? Can I just skip over to step 24 and run "fastboot flash recovery openrecovery-twrp-2.4.0.0-m7.img" ?"
That is done in order to give root access to the currently installed rom. You are going to install a new rom, so you don't have to do that until you get the rom installed.
You are now the 3rd user I have run into that is having the issue where you can't mount anything in recovery and I'm not sure why. Some users report that re locking and unlocking the bootloader fixes this, but you just did that, so I'm not sure why this is happening.
Within the toolkit try the perm root option? Perhaps there is something I can't think of since I rooted mine, the day I got it awhile back.
"Rooting The Device To root your device, first make sure you have unlocked the bootloader and installed a custom recovery. Next, select the ‘Perm Root’ option (the last one) from the Extras section and follow the instructions to get root access in no time."
To any other advanced users who may be able to answer this:
Does the recovery need the installed rom to have the SU binaries before it can mount the system in recovery? Does recovery need to be granted SU though some other means before mounting?
Click to expand...
Click to collapse
Okay I just tried Perm room - nothing happened except it showed 776 KB/s. I remember a few days ago there was a system update from HTC and I updated it OTA - would that affect this at all?
Just to be clear, I run the program, go into recovery, go into adb sideload, then I select the rom on the PC. Then I swipe across the bar to mount the rom and then it fails to mount and I get "error closed" in command prompt.
I know it is a pain in the ass, and users not familiar with adb/fastboot commands and using the toolkit mess it up.
Flashing recovery in fastboot after you pointed to your adb/fastboot folder you need to do:
fastboot erase cache
fastboot flash recovery name-of-your-recovery.img
fastboot erase cache
As you got it flashed successfully but you have problems sideliadung it with adb, get yourself a OTG cable and a USB storage stick, put the custom ROM.zip on there and then choose 'flash .zip from external storage' or s.thing like that. I don't know if that option is available in TWRP but it is in ClockworkMod.
Once you have booted successfully up into the ROM, go back into recovery and do a Nandroid back up, and keep it on that stick and on the internal storage if your One!
Good luck
Sent from my HTC One using xda premium
hardstuffmuc said:
I know it is a pain in the ass, and users not familiar with adb/fastboot commands and using the toolkit mess it up.
Flashing recovery in fastboot after you pointed to your adb/fastboot folder you need to do:
fastboot erase cache
fastboot flash recovery name-of-your-recovery.img
fastboot erase cache
As you got it flashed successfully but you have problems sideliadung it with adb, get yourself a OTG cable and a USB storage stick, put the custom ROM.zip on there and then choose 'flash .zip from external storage' or s.thing like that. I don't know if that option is available in TWRP but it is in ClockworkMod.
Once you have booted successfully up into the ROM, go back into recovery and do a Nandroid back up, and keep it on that stick and on the internal storage if your One!
Good luck
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Hmm so can I use the toolkit to do this? I don't have the actual recoveries of TWRP and CWM. If I have TWRP on this installed, can I flash Clockwork as well or do you have to choose one or the other?
I just want to clarify - are you saying that I should be doing this manually instead of using the toolkit to install CWM or TWRP? When I use the toolkit, does it erase the cache?
Btw, when I plug in my phone, it detects it as an F drive but I cannot access the actual internal storage. What does this mean? I have the drivers installed already.
limache said:
Okay I just tried Perm room - nothing happened except it showed 776 KB/s. I remember a few days ago there was a system update from HTC and I updated it OTA - would that affect this at all?
Just to be clear, I run the program, go into recovery, go into adb sideload, then I select the rom on the PC. Then I swipe across the bar to mount the rom and then it fails to mount and I get "error closed" in command prompt.
Click to expand...
Click to collapse
Yes, every user that I encountered with this issue had done an OTA update. Not exactly sure why or how that is causing these issues.
Yes, your procedure for sideload is correct, however you are unable to flash anything or use recovery at all because when in recovery the internal storage won't mount, so it can't perform any actions.
Need to do some more reading for: unable to mount in recovery
---------- Post added at 01:54 PM ---------- Previous post was at 01:49 PM ----------
limache said:
Hmm so can I use the toolkit to do this? I don't have the actual recoveries of TWRP and CWM. If I have TWRP on this installed, can I flash Clockwork as well or do you have to choose one or the other?
I just want to clarify - are you saying that I should be doing this manually instead of using the toolkit to install CWM or TWRP? When I use the toolkit, does it erase the cache?
Btw, when I plug in my phone, it detects it as an F drive but I cannot access the actual internal storage. What does this mean? I have the drivers installed already.
Click to expand...
Click to collapse
I don't think the toolkit is the issue. The cache erase can also be done from the toolkit with the Erase Cache in the Commands section. Never hurts to try this, but the issue is not being able to mount storage in recovery. I think you could install either recovery and it wouldn't matter as they would both have the same issue. Generally, I prefer TWRP anyway.
You can't access the phones internal storage when connected via USB when the phone is in recovery or fastboot. So that is normal.
limache said:
Hmm so can I use the toolkit to do this? I don't have the actual recoveries of TWRP and CWM. If I have TWRP on this installed, can I flash Clockwork as well or do you have to choose one or the other?
I just want to clarify - are you saying that I should be doing this manually instead of using the toolkit to install CWM or TWRP? When I use the toolkit, does it erase the cache?
Btw, when I plug in my phone, it detects it as an F drive but I cannot access the actual internal storage. What does this mean? I have the drivers installed already.
Click to expand...
Click to collapse
crushalot said:
Yes, every user that I encountered with this issue had done an OTA update. Not exactly sure why or how that is causing these issues.
Yes, your procedure for sideload is correct, however you are unable to flash anything or use recovery at all because when in recovery the internal storage won't mount, so it can't perform any actions.
Need to do some more reading for: unable to mount in recovery
---------- Post added at 01:54 PM ---------- Previous post was at 01:49 PM ----------
I don't think the toolkit is the issue. The cache erase can also be done from the toolkit with the Erase Cache in the Commands section. Never hurts to try this, but the issue is not being able to mount storage in recovery. I think you could install either recovery and it wouldn't matter as they would both have the same issue. Generally, I prefer TWRP anyway.
You can't access the phones internal storage when connected via USB when the phone is in recovery or fastboot. So that is normal.
Click to expand...
Click to collapse
Hmmm okay so the other poster's suggestion was to get an OTG cable (a micro usb to USB cable right?) and connect the USB with the ROM directly the phone. Do you think this would be a big difference or no? I just don't know if the issue is the internal storage itself or the mode of pushing the ROM.
Otherwise, I'm pretty much scratching my head and have no idea what else I could do =/.
Just for anyone else who's having issues, I've tried using TWRP's install function with the OTG cable but it still doesn't mount. Just letting people know.
if you are noob to recover your phone you can try some services like this
i revived my HTC one by them
http://goo.gl/1DMXlq
Hey all! I'm having some big problems getting my phone working. I was running Venom One rom for a while but then decided to try out something else and installed the CM 11S. Again phone worked perfectly but I got used to using Venom so I wanted to go back to it. And that's where I fu**ed it I think... I've installed the rom (I'm using T.W.R.P 2.7.1.1, standard cache and data format) like previously and again everything went smoothly with no errors. However, when I restarted the phone it got stuck on HTC logo. But it wasn't stuck like you couldn't do anything, I could lock the screen and when I unlocked it it would present me with the usual lock screen, time, taskbar etc. but when you unlocked it it went back to the HTC logo after a while an error popped up saying that the htc dialler was not responding. I haven't came across something like that ever before... So I went back to recovery and flashed the system again and again I had the exact same issue. So then I went and formatted everything including my internal storage, and that's where I made the biggest mistake. I forgot that I had the rom zip on internal storage and I'd lose it if I format the partition. No problem you'd say BUT I can't copy anything onto the phone.
When I connect the phone to my PC in recovery mode it just refuses to mount!! No matter which partition I want to mount, nothing comes up in my computer. I went on to the device manager and surely enough the HTC One is an unknown device... I tried side-loading the rom but the adb can't connect to the phone. I tried re-installing the HTC sync just to make sure I definitely have the usb drivers but still no luck. ADB devices command shows no devices connected. I've run out of ideas and I'm regretting my decision to try different roms...
I really don't want to buy a new phone so if anyone has ANY ideas please right it down. Thanks in advance!
bboybtek said:
Hey all! I'm having some big problems getting my phone working. I was running Venom One rom for a while but then decided to try out something else and installed the CM 11S. Again phone worked perfectly but I got used to using Venom so I wanted to go back to it. And that's where I fu**ed it I think... I've installed the rom (I'm using T.W.R.P 2.7.1.1, standard cache and data format) like previously and again everything went smoothly with no errors. However, when I restarted the phone it got stuck on HTC logo. But it wasn't stuck like you couldn't do anything, I could lock the screen and when I unlocked it it would present me with the usual lock screen, time, taskbar etc. but when you unlocked it it went back to the HTC logo after a while an error popped up saying that the htc dialler was not responding. I haven't came across something like that ever before... So I went back to recovery and flashed the system again and again I had the exact same issue. So then I went and formatted everything including my internal storage, and that's where I made the biggest mistake. I forgot that I had the rom zip on internal storage and I'd lose it if I format the partition. No problem you'd say BUT I can't copy anything onto the phone.
When I connect the phone to my PC in recovery mode it just refuses to mount!! No matter which partition I want to mount, nothing comes up in my computer. I went on to the device manager and surely enough the HTC One is an unknown device... I tried side-loading the rom but the adb can't connect to the phone. I tried re-installing the HTC sync just to make sure I definitely have the usb drivers but still no luck. ADB devices command shows no devices connected. I've run out of ideas and I'm regretting my decision to try different roms...
I really don't want to buy a new phone so if anyone has ANY ideas please right it down. Thanks in advance!
Click to expand...
Click to collapse
don't worry, you'll not have to buy another phone. Your issue is one of the most common issue we see here. First I will recommend you to use twrp 2.7.1.1 only to flash CM11 based roms and use twrp 2.6.3.3 or 2.6.3.4 for any Sense based roms.
You will first need to fix your drivers issue so you can adb push or adb sideload the rom to your phone again. there is a guide linked in my signature (nkk71's guide). In this thread, there is instruction (in the FAQ #2) about how to solve drivers issues.
When your drivers issue are solved, flash twrp 2.6.3.3:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
then boot in twrp 2.6.3.3 and adb push or sideload venom and hopefully it will be able to boot and it will be stable.
alray said:
don't worry, you'll not have to buy another phone. Your issue is one of the most common issue we see here. First I will recommend you to use twrp 2.7.1.1 only to flash CM11 based roms and use twrp 2.6.3.3 or 2.6.3.4 for any Sense based roms.
You will first need to fix your drivers issue so you can adb push or adb sideload the rom to your phone again. there is a guide linked in my signature (nkk71's guide). In this thread, there is instruction (in the FAQ #2) about how to solve drivers issues.
When your drivers issue are solved, flash twrp 2.6.3.3:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
then boot in twrp 2.6.3.3 and adb push or sideload venom and hopefully it will be able to boot and it will be stable.
Click to expand...
Click to collapse
The only weird thing is, I used the 2.7.1.1 to flash the sense rom in first place and everything worked fine :/ . Anyway, thanks for the shout! :good: I'll give it a try right now and see how it goes.
Right, I'm having problems installing the drivers for some reason. The ones downloaded from this thread don't seem to be doing anything at all. When click on them they show up for a split second in task manager and then they disappear. No install wizard no nothing. So i downloaded the ones for Windows 7 from here but this just gives me a message that "Windows could not find driver software for your device." . I mean, what the hell?
Edit: Right, after a lot of struggle I've managed to successfully bring my phone back to life! I have no idea what caused the issues with installing the drivers. I've spent ages deleting every trace of HTC drivers, then installed Windows 7 ones and somehow it worked. Then flashed t.w.r.p 2.6.3.3 and venom and it seems to be working smoothly! Hopefully no more problems . Thanks a lot for helping out man!
I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it. Nobody mentioned anything about it completely wiping the phone, including the internal SD card. I set most of the stuff back up again but realized that it was suffering from the bug on the old radio version that causes it to lose LTE randomly.
I went and rebooted into TWRP to try and flash it, and TWRP showed a completely empty sdcard partition and said it could not mount '/data'. I enabled "require pattern to boot," thinking it may not have known to decrypt the partition without that, and now I can't get into TWRP at all. I tried disabling the "require pattern to boot" option again but no luck. It shows the "Google" logo for about 5 seconds, then the blue "TEAMWIN" logo for about 3 seconds, then reboots to the "Google" logo and proceeds to boot normally. I should note that I have CM12.1 installed, and the latest TWRP. I've tried reflashing TWRP and that didn't help; I also did "fastboot format cache" and then "fastboot flash cache cache.img" using the stock factory cache.img. I got the radio flashed using fastboot, but I'd really like to have a working recovery.
briman0094 said:
I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it. Nobody mentioned anything about it completely wiping the phone, including the internal SD card. I set most of the stuff back up again but realized that it was suffering from the bug on the old radio version that causes it to lose LTE randomly.
I went and rebooted into TWRP to try and flash it, and TWRP showed a completely empty sdcard partition and said it could not mount '/data'. I enabled "require pattern to boot," thinking it may not have known to decrypt the partition without that, and now I can't get into TWRP at all. I tried disabling the "require pattern to boot" option again but no luck. It shows the "Google" logo for about 5 seconds, then the blue "TEAMWIN" logo for about 3 seconds, then reboots to the "Google" logo and proceeds to boot normally. I should note that I have CM12.1 installed, and the latest TWRP. I've tried reflashing TWRP and that didn't help; I also did "fastboot format cache" and then "fastboot flash cache cache.img" using the stock factory cache.img. I got the radio flashed using fastboot, but I'd really like to have a working recovery.
Click to expand...
Click to collapse
no working recovery with a locked bootloader, sorry. if the bootloader is locked, you cant flash anything. its locked. to flash things, you need an unlocked bootloader. its like locking a door, but expecting it to open magically when you walk up to it.
simms22 said:
no working recovery with a locked bootloader, sorry. if the bootloader is locked, you cant flash anything. its locked. to flash things, you need an unlocked bootloader. its like locking a door, but expecting it to open magically when you walk up to it.
Click to expand...
Click to collapse
I forgot to mention that I re-unlocked the bootloader. I can also boot the OS so I'd be able to enable OEM unlock again if needed.
briman0094 said:
I forgot to mention that I re-unlocked the bootloader. I can also boot the OS so I'd be able to enable OEM unlock again if needed.
Click to expand...
Click to collapse
important thing to forget to mention
So what happened when you reflashed the lasted version of twrp for your device after verifying the downloads md5?
simms22 said:
important thing to forget to mention
Click to expand...
Click to collapse
I guess I assumed that when I said "continues to boot normally" people would assume I could re-enable "OEM Unlock" if needed
scryan said:
So what happened when you reflashed the lasted version of twrp for your device after verifying the downloads md5?
Click to expand...
Click to collapse
All the console output indicates success, and it boots to the initial "TEAMWIN" logo for a few seconds and reboots.
No Recovery Similiar issue
briman0094 said:
I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it. Nobody mentioned anything about it completely wiping the phone, including the internal SD card. I set most of the stuff back up again but realized that it was suffering from the bug on the old radio version that causes it to lose LTE randomly.
I went and rebooted into TWRP to try and flash it, and TWRP showed a completely empty sdcard partition and said it could not mount '/data'. I enabled "require pattern to boot," thinking it may not have known to decrypt the partition without that, and now I can't get into TWRP at all. I tried disabling the "require pattern to boot" option again but no luck. It shows the "Google" logo for about 5 seconds, then the blue "TEAMWIN" logo for about 3 seconds, then reboots to the "Google" logo and proceeds to boot normally. I should note that I have CM12.1 installed, and the latest TWRP. I've tried reflashing TWRP and that didn't help; I also did "fastboot format cache" and then "fastboot flash cache cache.img" using the stock factory cache.img. I got the radio flashed using fastboot, but I'd really like to have a working recovery.
Click to expand...
Click to collapse
Briman, I seem to have a similar issue on my and wife's Google Nexus 6s. I unlocked and rooted using Wug Tool Kit I used in years past with seamless success. To confirm root CM 12.1 I can get into bootloader, Teamwin. From there I am to flash the Superuser, Busybox and TWRP zips under SD\iReady to Flash\Rootfiles..... Only I am not given an option on the menu? I am struggling with using the command prompt and proper paths from SDK Tools so that is not an option at this moment. I see a File Manager that shows this path but am hesitant to use it as I have READ this could cause damage ( brick) to the system. Watching your thread for answers or possibilities. I know the senior members as Simm22 dislike tool kits and so do I. I am simply trying to grow and learn.
ray6279 said:
Briman, I seem to have a similar issue on my and wife's Google Nexus 6s. I unlocked and rooted using Wug Tool Kit I used in years past with seamless success. To confirm root CM 12.1 I can get into bootloader, Teamwin. From there I am to flash the Superuser, Busybox and TWRP zips under SD\iReady to Flash\Rootfiles..... Only I am not given an option on the menu? I am struggling with using the command prompt and proper paths from SDK Tools so that is not an option at this moment. I see a File Manager that shows this path but am hesitant to use it as I have READ this could cause damage ( brick) to the system. Watching your thread for answers or possibilities. I know the senior members as Simm22 dislike tool kits and so do I. I am simply trying to grow and learn.
Click to expand...
Click to collapse
na, toolkits work fine. sure, they occasionally do mess up, but its not very ofver. i generally like ut when noobies do the rooting the correct way the first time, that way they can learn some basic things about how everything works. then, they can yse toolkits all they
btw, teamwin isnt your bootloader, its your recovery. team win = twrp. now all you need to do is download the latest supersu and flash it via your recovery, and the you can install a busybox app from tbe play store, and use it to unstall .
briman0094 said:
I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it.
Click to expand...
Click to collapse
Saw that bit of advice where? I can't think of a single thing re-locking the bootloader would fix.
nhizzat said:
Saw that bit of advice where? I can't think of a single thing re-locking the bootloader would fix.
Click to expand...
Click to collapse
A screenshot of an e-mail from a Google employee regarding Android Pay and SafetyNet.
50% JOY No Fastboot?
simms22 said:
na, toolkits work fine. sure, they occasionally do mess up, but its not very ofver. i generally like ut when noobies do the rooting the correct way the first time, that way they can learn some basic things about how everything works. then, they can yse toolkits all they
btw, teamwin isnt your bootloader, its your recovery. team win = twrp. now all you need to do is download the latest supersu and flash it via your recovery, and the you can install a busybox app from tbe play store, and use it to unstall .
Click to expand...
Click to collapse
I followed your directions while working on my Nexus6 phone. Was able to access bootloader then install iReady files. Worked perfectly and phone loaded SUPERUSER, BUSYBOX & PERM RECOVERY. Not so much on wife's Nexus 6. I get thru UNLOCK & ROOT w/custom recovery on the Wug Fresh Tool Kit. At RECOVERY menu pulls up SD - Up one level. No option is allowed to continue on and load the three mentioned packages. I then able to reboot to system. Does it appear I am bootloading but not fastbooting? Will try and insert images.
ray6279 said:
I followed your directions while working on my Nexus6 phone. Was able to access bootloader then install iReady files. Worked perfectly and phone loaded SUPERUSER, BUSYBOX & PERM RECOVERY. Not so much on wife's Nexus 6. I get thru UNLOCK & ROOT w/custom recovery on the Wug Fresh Tool Kit. At RECOVERY menu pulls up SD - Up one level. No option is allowed to continue on and load the three mentioned packages. I then able to reboot to system. Does it appear I am bootloading but not fastbooting? Will try and insert images.
Click to expand...
Click to collapse
one question.. what is perm recovery?? the only recovery that works on the n6 is twrp recovery.
and when you are in her recovery, is it showing you the right location where the files should be? if nit, you csn change the lication.
Simm & Others. Thank you for your good words and suggestions. It would be easier for me to list what I did not attempt rather than what I did try. . I tried nearly most functions in the Wug Fresh ( by Harold) v2.0.5 after failing to find the correct command prompt to use ADB. What happened is an odditity. Mind you, I've been on these two Nexus 6 phones for 4-6hours a day for about ten days! Day later, Happened to be waiting for wife in parking lot and picked up phone and pressed SuperUser. Viola! It went into TWRP and gave me an RECOVERY option. On impluse, I flashed TWRP and Superuser zips. It took and processed. however, the best part of this is the hands on learning experience of booting, flashing, wiping, language, terms, SDK, Android and more. Once I figure out my path problem on my windows based PC to loading ABD commands I am continuing my self study of Android and App development. How do I get the packages out of the SDK Tool Kit to folders in PC? Thanks all.
ray6279 said:
Simm & Others. Thank you for your good words and suggestions. It would be easier for me to list what I did not attempt rather than what I did try. . I tried nearly most functions in the Wug Fresh ( by Harold) v2.0.5 after failing to find the correct command prompt to use ADB. What happened is an odditity. Mind you, I've been on these two Nexus 6 phones for 4-6hours a day for about ten days! Day later, Happened to be waiting for wife in parking lot and picked up phone and pressed SuperUser. Viola! It went into TWRP and gave me an RECOVERY option. On impluse, I flashed TWRP and Superuser zips. It took and processed. however, the best part of this is the hands on learning experience of booting, flashing, wiping, language, terms, SDK, Android and more. Once I figure out my path problem on my windows based PC to loading ABD commands I am continuing my self study of Android and App development. How do I get the packages out of the SDK Tool Kit to folders in PC? Thanks all.
Click to expand...
Click to collapse
your welcome, but you are still off in one bit of fact. you use fastboot, not adb, to flash a recovery(and system.img)
edit.. you can use apps like flashify to flash recovery, if you have root already.
So BOOTLOADER is the USB connection between the device and PC. FASTBOOT is the process via we make changes in the device via the PC. ADB is the device language via which we communicate. So do I still need to flash a system recovery image? Flashify App? I already went thru install>iready to flash> superuser (version)>busybox>flash>reboot>system. I'm going cross eyed from reading. The wiping part worries me as I fear formatting or deleting essential data.
ray6279 said:
So BOOTLOADER is the USB connection between the device and PC. FASTBOOT is the process via we make changes in the device via the PC. ADB is the device language via which we communicate. So do I still need to flash a system recovery image? Flashify App? I already went thru install>iready to flash> superuser (version)>busybox>flash>reboot>system. I'm going cross eyed from reading. The wiping part worries me as I fear formatting or deleting essential data.
Click to expand...
Click to collapse
ok, when wiping, dont do the first option wipe, itll wipe your whole phone clean. you need to select the advanced options and pick what you want wiped. fastboot is the way to unlock your bootloader, or flash a recovery. also, you use it to flash a system.img or any part of it.
adb is a general linux that can be used with android, anywhere but in the bootloader(only fastboot in the bootloader).
bootloader isnt the usb connection between the device and the pc, its part of the phone that boots it and decides if the rom is safe to run. thats why we unlock it. so we can flash roms eithout googles key.
fastboot is the tool that you use to do whatever needs to be fone in the bootloader, adb everywhere else.
a recovery you need if you want to flash custom roms, kernels, supersu, or other mods. you can also wipe different partitions with the recovery, or make a "nandroid' backup. thats a bavkup of everything. its like a complete snapshot of everything during the time you made it. if you ever mess up your phone, you can restore it, and you will be at the exact same place when you made the backup.
anything else?
I've followed all of the steps from this guide: http://forum.xda-developers.com/showpost.php?p=56938530&postcount=1
I've got to the end where I am running the code snippets to flash everything, but everything fails. The error stated is FAILED: remote failure. I am not sure if this is related to my developer options being turned off, but I think it might be.
Is there a way to turn developer options on while in fastboot mode or perhaps a way around this error? The reason I am stuck in the fastboot is because the boot image can't be validated, I am not at the fastboot by choice, haha.
No. If your recovery is still stock, flash the Android N Preview 1 OTA or an Android 6.0.1 OTA image from Google. One of those will restore your Nexus to operating condition, and from there you can try again. If your recovery is TWRP, flash a custom ROM.
Strephon Alkhalikoi said:
No. If your recovery is still stock, flash the Android N Preview 1 OTA or an Android 6.0.1 OTA image from Google. One of those will restore your Nexus to operating condition, and from there you can try again. If your recovery is TWRP, flash a custom ROM.
Click to expand...
Click to collapse
I apologize for my ignorance since this is all new to me, but could you explain a few things to me.
Is this what you're referring to when you say Android N Preview 1 OTA: 'https://developer.android.com/preview/download.html'
Secondly, in order to flash these, am I still following the steps I was before, or should I be following a new set of steps?
You don't need the N Preview anymore. Download your Android 6.0.1 image from the Google page and flash using the instructions given on that page.
I went to the page and followed the directions. Still doesn't work. The flash-all script reboots after the first two commands, which lock the phone. But even then, it is still giving the error FAILED:remote failure.
me too!
I seem to be having the exact same issue! i just bought a Nexus 6 online that wasn't booting, it would only show a green led when plugged in. so here I am doing everything I can think of to fix the issue but then I get hit with the "remote failure" when i try to oem unlock the bootloader! (and since the phone wont't boot i can't check the "unlock bootloader" box in the developer options) so yeah I am going to keep researching this but if anyone has any good ideas about to get around the bootloader being locked please jump right in.
anyways I may have deeper issues, the battery will not charge. i know this because when i load up the fastboot menu, which i have to do by holding the buttons while plugging it in, it should say battery charging but all it says is battery ok
I also can't load recovery because when im in the fastboot menu and i choose recovery the phone freezes and the green led comes back on... *sigh*
They have the full ota packages posted on Google site now you can and push through the stock recovery
Here just make sure you get the shame version
https://developers.google.com/android/nexus/ota#hammerhead
Sent from my Nexus 6 using XDA-Developers mobile app
I have the OTA. I also installed Wugs toolkit.
My phone is in fastboot mode due to the boot image not being able to be validated. I didn't voluntarily open up fastboot using the shortcut.
The phone is UNLOCKED until bootloader is rebooted, then it is LOCKED. If I click start, it becomes UNLOCKED again. Wug's toolkit tries to UNLOCK the phone even while the phone says it is UNLOCKED. I don't think the phone is actually UNLOCKED, however whenever it tells me it is UNLOCKED, I try to proceed with flashing and it gives me a remote failure message on each command.
The next thing I am going try is the drivers and Wug's toolkit has a driver option, so I will try that. Besides the drivers, any other ideas?
You seem to be inexperienced in rooting Android devices. If you aren't, I apologize for the assumption. However, you should learn how to use adb and fastboot without relying on the toolkit. Toolkits tend to hide diagnostic messages that adb and fastboot generate while running. This missing information makes solving problems much more difficult.
Strephon Alkhalikoi said:
You seem to be inexperienced in rooting Android devices. If you aren't, I apologize for the assumption. However, you should learn how to use adb and fastboot without relying on the toolkit. Toolkits tend to hide diagnostic messages that adb and fastboot generate while running. This missing information makes solving problems much more difficult.
Click to expand...
Click to collapse
I am inexperienced, I stated that earlier. I have check a bunch of different forum posts and a bunch of different guides. Nothing seems to be helping and it seems like such a simple problem, a boot image that can't be validated. I am not trying to do anything special with my phone, I am just trying to get it to work. I woke up and it was stuck in this 'AP Fastboot Flash Mode (Secure)' mode. It is very bare bones, not even similar to the screens within videos I have seen. One moment the phone says it's UNLOCKED, the next it's LOCKED.
You are the expert, I am not. I am merely following your directions and they don't seem to be working. I did some outside research, came to a toolkit. Toolkits are great for beginners, especially since they are UI built, are built by someone who knows the area of interest, which makes researching easier and more efficient, but on top of that, it seems to be getting me much farther than your advice, although nothing is successful at this moment.
Here is a little more context into my situation. My phone seems to be recognized by Fastboot, but not ADB (From what I found, fastboot will find devices in fastboot, and adb will find devices functioning normally, don't know how true that is.). In addition, my phone seems to switch from UNLOCKED TO LOCKED after reboots, but can become UNLOCKED again if I push ANY button. Every command I issue (i.e flash bootloader, flash radio, flash system, flash userdata) result in the message, FAILED:remote failure, which I am not sure how to avoid (I have googled, checked these forums, checked other forums and there doesn't seem to be much, if any documentation on the error), but I think it is related to the fact my developer options are turned OFF. My next course of action is to install new drivers (I checked my drivers which are said to be up to date, I also installed google USB driver through the sdk, but now I am going to look into an adb or universal driver?) and attempt to rerun everything successfully.
If you have any other ideas, or don't think its the drivers, feel free to bring it up.
As a couple of fellows said before, try this:
https://developers.google.com/android/nexus/ota
Flash a FULL OTA from the link above, not a factory image. To flash any OTA you don't need to be unlocked. I think you might be confusing the terms (with the OTA you don't have to flash anything using fastboot)
In the link there are the instructions, it's pretty straight forward and easy if you have the correct drivers installed.
OTA requires that u can startup into recovery, I cannot I can startup fastboot through key combo but when I go to select recovery the green led comes back on and the screen displaying the fastboot options remains static
I think the phone freezes because it does not appear to be able to use the battery. though there is a firm battery connection it will not charge or power on without being plugged in. maybe when I select recovery I can quickly unplug and replug the USB and maybe hold the power button to try to simulate a successful reboot.. idk just thinking aloud and working with what I got..
I also can not start in recovery mode and the OTA requires ADB, which isn't recognizing my device. I have also stated that I have followed those instructions, and nothing resulted from them, except the same messages I have been stating these last few posts.
I will try this first chance I get later tonight..
http://forum.xda-developers.com/nexus-6/help/solution-stuck-bootloop-locked-t3053783
Listen the ota doesn't get installed through fast boot, you have to select recovery through the fast boot then install the update by pushing it as bootloader does not need to be unlocked!
Sent from my Nexus 6 using XDA-Developers mobile app
holeindalip said:
Listen the ota doesn't get installed through fast boot, you have to select recovery through the fast boot then install the update by pushing it as bootloader does not need to be unlocked!
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Ok, well it seems we are at an impasse. You seem to think I can do something, so I am going to show some pictures of my screen. Its going to be blurry because I had to take it with my computer, so I apologize, but I will elaborate on each picture.
Qwertyismypw said:
Ok, well it seems we are at an impasse. You seem to think I can do something, so I am going to show some pictures of my screen. Its going to be blurry because I had to take it with my computer, so I apologize, but I will elaborate on each picture.
Click to expand...
Click to collapse
The first two pictures are when the phone is 'UNLOCKED'. The second two pictures are when the phone is 'LOCKED'. The moment I press anything in 'LOCKED' mode, the little android man goes away, and it becomes the first two pictures. WHENEVER I push a button in 'UNLOCKED' mode, nothing happens, except in the bootloader logs screen says, 'FAILED TO VALIDATE BOOT IMAGE RET -1'. I have done everything on that OTA page in every way possible. It has done me no good.
Ok, I made a little progress I think. Wugs toolkit allowed me to use TWRP on my phone and ADB is recognizing my phone now. There are a lot of options within TWRP though, so I am going to look through them all for anything relevant. Anything I should keep an extra eye out for?
If you can use twrp just download a custom ROM to your phone and move it over to SD card and flash it, then you will be able to boot and unlock the bootloader in developer ootions, that is your best bet, if you keep getting force closes after flashing a custom ROM your going to have to do a factory reset from within twrp
Sent from my Nexus 6 using XDA-Developers mobile app
holeindalip said:
If you can use twrp just download a custom ROM to your phone and move it over to SD card and flash it, then you will be able to boot and unlock the bootloader in developer ootions, that is your best bet, if you keep getting force closes after flashing a custom ROM your going to have to do a factory reset from within twrp
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
I don't have an SD card, can I move it to the internal storage? And how exactly do I do this? I can't copy/paste anything into the phone (it says the phone doesn't actually exist, even though adb is recognizing it as in recovery) or do I sideload it? When I try to sideload it though, the device disappears (and device manager sees nexus 6 under other devices, but the driver isn't up to date and no drivers seem to work. I've tried the google usb driver with no luck.) and it won't allow me to sideload it.