Related
Hello XDA I'm new to these forums but i'm hoping you can help me out.
So basically I was following a youtube video I was linked to by a guide on here on how to root my One. and everything was going smoothly and then i got to the stage where i was to boot into recovery mode so i could load into twrp. But what happens on my phone now is the loading screen for recovery mode where it says for developers only ect. will just hang there for a while then the phone will shut off and boot back into regular mode. could use some help. I wouldn't mind resetting and starting fresh if that's what's needed im just not sure how to. thank you guys!
Kdenery said:
Hello XDA I'm new to these forums but i'm hoping you can help me out.
So basically I was following a youtube video I was linked to by a guide on here on how to root my One. and everything was going smoothly and then i got to the stage where i was to boot into recovery mode so i could load into twrp. But what happens on my phone now is the loading screen for recovery mode where it says for developers only ect. will just hang there for a while then the phone will shut off and boot back into regular mode. could use some help. I wouldn't mind resetting and starting fresh if that's what's needed im just not sure how to. thank you guys!
Click to expand...
Click to collapse
read this: http://forum.xda-developers.com/showthread.php?t=1435228
you will need to reflash recovery using fastboot/adb
Aldo101t said:
read this: http://forum.xda-developers.com/showthread.php?t=1435228
you will need to reflash recovery using fastboot/adb
Click to expand...
Click to collapse
first problem, how do i select charge only? and second when i try the first command code posted it just wouldn't work and when i tried it while the phone was slected on fastboot usb (just incase that would work) it said no device.
Ok i figured it out i did everything in that thread. the same thing is happening. it just says entering recovery then restarts in normal mode.
Kdenery said:
Ok i figured it out i did everything in that thread. the same thing is happening. it just says entering recovery then restarts in normal mode.
Click to expand...
Click to collapse
do you have sdk tools installed on your computer.
make sure usb debugging is on, apperently you do.
did you put the recovery image in the folder where fastboot is then run cmd(as administrator) and cd to that folder(example/:cd c:/Program Files/Android/android-sdk/platform-tools or where ever you have it)then adb reboot bootloader>enter----Then fastboot flash recovery(name of recovery image).img>enter--- then type fastboot reboot recovery
If you are unlocked already, watch this https://www.youtube.com/watch?v=rRkAHw_GmIs&feature=youtube_gdata_player
Sent from my HTCONE using Tapatalk 4 Beta
Aldo101t said:
do you have sdk tools installed on your computer.
make sure usb debugging is on, apperently you do.
did you put the recovery image in the folder where fastboot is then run cmd(as administrator) and cd to that folder(example/:cd c:/Program Files/Android/android-sdk/platform-tools or where ever you have it)then adb reboot bootloader>enter----Then fastboot flash recovery(name of recovery image).img>enter--- then type fastboot reboot recovery
Click to expand...
Click to collapse
yes. the problem is that it just stalls out on the entering recovery screen. with the htc logo and motto in the middle.
Kdenery said:
yes. the problem is that it just stalls out on the entering recovery screen. with the htc logo and motto in the middle.
Click to expand...
Click to collapse
which recovery are you installing if its twrp v2.6.0.0 try 2.5.0.0 there was a bug in the 2.6 don't know if they fixed it yet.
Aldo101t said:
which recovery are you installing if its twrp v2.6.0.0 try 2.5.0.0 there was a bug in the 2.6 don't know if they fixed it yet.
Click to expand...
Click to collapse
I tried this yesterday after installing 2.6.0.1 when the problem first happened. then i tried 2.6.0.0 then 2.5.0.0 the problem never went away and today i tried clockwork recovery. same thing. do i need to delete the images i've flashed onto it? if no how?
Kdenery said:
I tried this yesterday after installing 2.6.0.1 when the problem first happened. then i tried 2.6.0.0 then 2.5.0.0 the problem never went away and today i tried clockwork recovery. same thing. do i need to delete the images i've flashed onto it? if no how?
Click to expand...
Click to collapse
no i wouldn't think you do, it just overwrites the other, you're sure your bootloader is unlocked, check in settings under development option to make sure debugging is on.man you got me stumped here.
Kdenery said:
I tried this yesterday after installing 2.6.0.1 when the problem first happened. then i tried 2.6.0.0 then 2.5.0.0 the problem never went away and today i tried clockwork recovery. same thing. do i need to delete the images i've flashed onto it? if no how?
Click to expand...
Click to collapse
Are you typing "fastboot erase cache" without the quotes after you flash the recovery?
Aldo101t said:
no i wouldn't think you do, it just overwrites the other, you're sure your bootloader is unlocked, check in settings under development option to make sure debugging is on.man you got me stumped here.
Click to expand...
Click to collapse
I retried the whole process once more and made sure usb debugging was on and its just frozen again.
bigdaddy619 said:
Are you typing "fastboot erase cache" without the quotes after you flash the recovery?
Click to expand...
Click to collapse
Just tried and made sure to do this. same problem.
Perhaps i'm just being extremely retarded. I am unlocked but not rooted, i thought this was how to get rooted. but maybe im just far off.
Kdenery said:
Perhaps i'm just being extremely retarded. I am unlocked but not rooted, i thought this was how to get rooted. but maybe im just far off.
Click to expand...
Click to collapse
NO, you are NOT retarded, you install recovery, then su to get root, for all intent and purposes you're doing it all right, just can't figure out why it's not working, one more redundant question, you have fastboot under power settings disabled?? Just tryin to cover all the bases
you are installing the recovery for the m7wls(m7spr)?
Aldo101t said:
NO, you are NOT retarded, you install recovery, then su to get root, for all intent and purposes you're doing it all right, just can't figure out why it's not working, one more redundant question, you have fastboot under power settings disabled?? Just tryin to cover all the bases
you are installing the recovery for the m7wls(m7spr)?
Click to expand...
Click to collapse
fast boot is not checked. and i think/hope so, how do i check that?
Kdenery said:
fast boot is not checked. and i think/hope so, how do i check that?
Click to expand...
Click to collapse
in settings under power scroll to the bottom fastboot is there.
Sorry i guess i phrased that wrong. i'm sure fastboot is unchecked, i was asking about the second part of your post, about "you are installing the recovery for the m7wls(m7spr)?"
Kdenery said:
Sorry i guess i phrased that wrong. i'm sure fastboot is unchecked, i was asking about the second part of your post, about "you are installing the recovery for the m7wls(m7spr)?"
Click to expand...
Click to collapse
what exactly is the zip you're using,should be something like(fastboot flash recovery openrecovery-twrp-2.5.0.0-m7wls.img
I've tried
cwm-recovery-vivow
openrecovery-twrp-2.5.0.0-m7
openrecovery-twrp-2.6.0.0-m7
openrecovery-twrp-2.6.0.0-m7wls
openrecovery-twrp-2.6.0.1-m7
recovery-clockwork-6.0.3.2-m7spr
recovery-clockwork-touch-6.0.3.3-m7spr
Hey guys, I need some major help!
I was trying to update my phone earlier today, when I flashed Android Revolution HD 40.3 something very bad happened!
For some reason the ROM did not install properly, and I can't get back into recovery. I was using TWRP and the loading screen comes up for it, but it never fully launches.
I can get into the bootloader, and I tried using the Toolkit under fastboot. It seems like my phone is detected, but when I try and flash anything it doesnt work. Ive flashed both TWRP and clockword. They seem to flash because it will show the loading screen of either one, but it never actually enters the recovery. What should I do?
My phone is S-ON, I am not sure if that is what caused the problem/is what is keeping this an issue.
Thanks for your help
SMGkrome said:
Hey guys, I need some major help!
I was trying to update my phone earlier today, when I flashed Android Revolution HD 40.3 something very bad happened!
For some reason the ROM did not install properly, and I can't get back into recovery. I was using TWRP and the loading screen comes up for it, but it never fully launches.
I can get into the bootloader, and I tried using the Toolkit under fastboot. It seems like my phone is detected, but when I try and flash anything it doesnt work. Ive flashed both TWRP and clockword. They seem to flash because it will show the loading screen of either one, but it never actually enters the recovery. What should I do?
My phone is S-ON, I am not sure if that is what caused the problem/is what is keeping this an issue.
Thanks for your help
Click to expand...
Click to collapse
Does the phone just reboot before it enters recovery? I would try manually flashing a custom recovery image. Here is a link to the exact image I used.
http://forum.xda-developers.com/showthread.php?t=2173863
It's very straightforward once you have fast boot setup. Don't worry I've been in your situation myself!
JasSingh93 said:
Does the phone just reboot before it enters recovery? I would try manually flashing a custom recovery image. Here is a link to the exact image I used.
http://forum.xda-developers.com/showthread.php?t=2173863
It's very straightforward once you have fast boot setup. Don't worry I've been in your situation myself!
Click to expand...
Click to collapse
Thanks for the response!
Was your phone S-ON?? It seems that there are fixes when it is S-OFF, but not S-ON
SMGkrome said:
Thanks for the response!
Was your phone S-ON?? It seems that there are fixes when it is S-OFF, but not S-ON
Click to expand...
Click to collapse
My phone was S-ON at the time, I recently gained S-OFF. You should still be able to flash a new recovery with S-ON. S-OFF is usually only needed for flashing new radios or firmwares.
JasSingh93 said:
My phone was S-ON at the time, I recently gained S-OFF. You should still be able to flash a new recovery with S-ON. S-OFF is usually only needed for flashing new radios or firmwares.
Click to expand...
Click to collapse
How did you flash the recovery? Like I've said, I tried flashing a new recovery via the Toolkit. They do seem to flash, but I cant access the recovery. I'm not sure if my bootloader was relocked or what, but it doesn't go past the intro screen for TWRP or Clockwork
SMGkrome said:
How did you flash the recovery? Like I've said, I tried flashing a new recovery via the Toolkit. They do seem to flash, but I cant access the recovery. I'm not sure if my bootloader was relocked or what, but it doesn't go past the intro screen for TWRP or Clockwork
Click to expand...
Click to collapse
It could be possible that the toolkit is installing an incorrect version maybe? Switch off your phone. Once off hold vol - and power the phone on. This should load up HBOOT and tell you the boot loader status.
This is how I flashed recovery. I entered fastboot and used the commands from that link to flash a new recovery image. Have you used fastboot commands before?
JasSingh93 said:
It could be possible that the toolkit is installing an incorrect version maybe? Switch off your phone. Once off hold vol - and power the phone on. This should load up HBOOT and tell you the boot loader status.
This is how I flashed recovery. I entered fastboot and used the commands from that link to flash a new recovery image. Have you used fastboot commands before?
Click to expand...
Click to collapse
To be honest, I'm pretty new to the fastboot commands. I usually follow guides to root, and flashing ROMs is pretty straightforward.
SMGkrome said:
To be honest, I'm pretty new to the fastboot commands. I usually follow guides to root, and flashing ROMs is pretty straightforward.
Click to expand...
Click to collapse
If you have fastboot setup and working, just boot the phone into fastboot mode and use the commands in that link I gave you.
From fastboot. Use command "fastboot erase cache"
From fastboot. Use command "fastboot flash recovery recovery.img"
Then simply highlight "recovery", tap the power button and the phone should load up clockwordmod recovery.
Easy
JasSingh93 said:
If you have fastboot setup and working, just boot the phone into fastboot mode and use the commands in that link I gave you.
From fastboot. Use command "fastboot erase cache"
From fastboot. Use command "fastboot flash recovery recovery.img"
Then simply highlight "recovery", tap the power button and the phone should load up clockwordmod recovery.
Easy
Click to expand...
Click to collapse
Is fastboot mode just when you hold power and volume down then select fastboot?
SMGkrome said:
Is fastboot mode just when you hold power and volume down then select fastboot?
Click to expand...
Click to collapse
It is
SMGkrome said:
Is fastboot mode just when you hold power and volume down then select fastboot?
Click to expand...
Click to collapse
This is going to make me sound incompetent, but to use fastboot commands I just need to install the ADT Bundle from google for developers?
SMGkrome said:
This is going to make me sound incompetent, but to use fastboot commands I just need to install the ADT Bundle from google for developers?
Click to expand...
Click to collapse
It doesn't make you sound incompetent at all! Yes its just the bundle, then the drivers should be installed with that too. If you're not 100% sure there are plenty of guides online on how to setup fastboot.
For example: http://techbeasts.com/2013/08/26/how-to-install-adb-fastboot-drivers-on-your-windows-pc-guide/
Or if you're lazy like me you can use this: http://forum.xda-developers.com/showthread.php?p=42407269
JasSingh93 said:
It doesn't make you sound incompetent at all! Yes its just the bundle, then the drivers should be installed with that too. If you're not 100% sure there are plenty of guides online on how to setup fastboot.
For example: http://techbeasts.com/2013/08/26/how-to-install-adb-fastboot-drivers-on-your-windows-pc-guide/
Or if you're lazy like me you can use this: http://forum.xda-developers.com/showthread.php?p=42407269
Click to expand...
Click to collapse
Ah, no dice. I followed all the steps, everything seemed to work (thanks for the guide). It flashed the recovery okay. When I restarted the phone, it goes into recovery, shows clockwork mod recovery, version XX and then proceeds to try and boot into my regular system
SMGkrome said:
Ah, no dice. I followed all the steps, everything seemed to work (thanks for the guide). It flashed the recovery okay. When I restarted the phone, it goes into recovery, shows clockwork mod recovery, version XX and then proceeds to try and boot into my regular system
Click to expand...
Click to collapse
Hm, that's really strange. So recovery tried to boot, but the phone restarts and tried to boot normally?
Did you try running the command "fastboot erase cache" in fastboot mode?
JasSingh93 said:
Hm, that's really strange. So recovery tried to boot, but the phone restarts and tried to boot normally?
Did you try running the command "fastboot erase cache" in fastboot mode?
Click to expand...
Click to collapse
Yeah, basically it goes back and forth between trying to get into recovery and try to boot normally but can't boot into either
SMGkrome said:
Yeah, basically it goes back and forth between trying to get into recovery and try to boot normally but can't boot into either
Click to expand...
Click to collapse
OK so new recovery flashed, I would try running "fastboot erase cache". This commonly fixed issues with recoveries failing to boot.
JasSingh93 said:
OK so new recovery flashed, I would try running "fastboot erase cache". This commonly fixed issues with recoveries failing to boot.
Click to expand...
Click to collapse
So I owe you a beer! I guess I must have forgotten that command. Worked perfectly, phone is all good now!
Thanks for all the help
SMGkrome said:
So I owe you a beer! I guess I must have forgotten that command. Worked perfectly, phone is all good now!
Thanks for all the help
Click to expand...
Click to collapse
No worries! Glad you got it working. Happy to help!
Phone doesn't get recognized when plugged into my Mac. Can't get into my phone because it's stuck in "flash mode" and "recovery mode" I think.. These are the only 2 screens I can get to. Cannot get into my phone at all. http://img.wonderhowto.com/img/27/60/63506305015628/0/unlock-your-bootloader-root-your-htc-one-install-custom-recovery-using-twrp.w654.jpg and http://img.wonderhowto.com/img/88/14/63506304904836/0/unlock-your-bootloader-root-your-htc-one-install-custom-recovery-using-twrp.w654.jpg
TynanV said:
Okay, followed this tutorial today (can't post the link but it's called "How to Root HTC One! [Mac, Linux, Windows Tutorial]" and no matter what I do I can't seem to get back to the actual phone (i.e., being able to access the main screen where everything is, if you know what I mean). I've tried going to the recovery screen and hitting reboot but it just takes me back to this TWRP page that has a bunch of options like "Install, Wipe, Backup, Restore, Mount, Setting, etc. I really hope I haven't screwed up my phone permanently. Please help me :crying:
Click to expand...
Click to collapse
how far into the tutorial did you get ?
did you fastboot erase cache after flashing twrp ?
clsA said:
how far into the tutorial did you get ?
did you fastboot erase cache after flashing twrp ?
Click to expand...
Click to collapse
I'm completely new at this and literally just started today, What does flashing twrp mean? I got to the end of the tutorial i believe. Everything worked great until step 28 I think.
TynanV said:
I'm completely new at this and literally just started today, What does flashing twrp mean? I got to the end of the tutorial i believe. Everything worked great until step 28 I think.
Click to expand...
Click to collapse
when you were in the command prompt and run the fastboot commands
fastboot flash recovery TWRP.img
fastboot erase cache
fastboot reboot-bootloader
did you do these, or use an all in one app
clsA said:
how far into the tutorial did you get ?
did you fastboot erase cache after flashing twrp ?
Click to expand...
Click to collapse
clsA said:
when you were in the command prompt and run the fastboot commands
fastboot flash recovery TWRP.img
fastboot erase cache
fastboot reboot-bootloader
did you do these, or use an all in one app
Click to expand...
Click to collapse
I have one in the terminal (I think that's the command prompt on a PC?) called this -
./fastboot-mac flash recovery openrecovery-twrp-2.6.3.0 m7.img
not sure about the other two.
TynanV said:
I have one in the terminal (I think that's the command prompt on a PC?) called this -
./fastboot-mac flash recovery openrecovery-twrp-2.6.3.0 m7.img
not sure about the other two.
Click to expand...
Click to collapse
are you on Sprint ? their is newer recovery for GSM phones
http://techerrata.com/browse/twrp2/m7 - 2.6.3.3 is recommended
make sure you do all 3 commands
clsA said:
are you on Sprint ? their is newer recovery for GSM phones
http://techerrata.com/browse/twrp2/m7 - 2.6.3.3 is recommended
make sure you do all 3 commands
Click to expand...
Click to collapse
I'm with Telus in Canada.
TynanV said:
I'm with Telus in Canada.
Click to expand...
Click to collapse
use TWRP 2.6.3.3 and don't skip any steps
clsA said:
use TWRP 2.6.3.3 and don't skip any steps
Click to expand...
Click to collapse
Thanks, I looked up how to do this though and the 2nd step says, "run fastboot flash recovery twrp-2.6.3.3-m7.img" how do I do this?
TynanV said:
Thanks, I looked up how to do this though and the 2nd step says, "run fastboot flash recovery twrp-2.6.3.3-m7.img" how do I do this?
Click to expand...
Click to collapse
in terminal the same as you did above with version 2.6.3.0
clsA said:
in terminal the same as you did above with version 2.6.3.0
Click to expand...
Click to collapse
Do I need my phone plugged into my Mac? (sorry for all the stupid questions i've just never really done this before).
TynanV said:
Do I need my phone plugged into my Mac? (sorry for all the stupid questions i've just never really done this before).
Click to expand...
Click to collapse
well if you have this many questions .. I think you should stop and read the guides before you do something to the phone that can't be reversed.
start here (go to post 2 Guides) >> http://forum.xda-developers.com/showthread.php?t=2438026
this is the MAC thread >> http://forum.xda-developers.com/showthread.php?t=2245782
Read this >> http://forum.xda-developers.com/showthread.php?t=2273376
once you have a handle on all the steps required to unlock - install recovery - get Root - and Flash Roms then you can start
clsA said:
well if you have this many questions .. I think you should stop and read the guides before you do something to the phone that can't be reversed.
start here (go to post 2 Guides) >> http://forum.xda-developers.com/showthread.php?t=2438026
this is the MAC thread >> http://forum.xda-developers.com/showthread.php?t=2245782
Read this >> http://forum.xda-developers.com/showthread.php?t=2273376
once you have a handle on all the steps required to unlock - install recovery - get Root - and Flash Roms then you can start
Click to expand...
Click to collapse
The problem is I can't transfer any files into the HTC Sync Manager to be able to apply them to my phone because I can't get to the main screen, therefore it does not recognize my phone when it's plugged into my computer..
TynanV said:
The problem is I can't transfer any files into the HTC Sync Manager to be able to apply them to my phone because I can't get to the main screen, therefore it does not recognize my phone when it's plugged into my computer..
Click to expand...
Click to collapse
like i said go do some reading
and uninstall HTC SYNC it's useless
the only tools you'll be using are Terminal / fastboot and ADB
clsA said:
like i said go do some reading
and uninstall HTC SYNC it's useless
the only tools you'll be using are Terminal / fastboot and ADB
Click to expand...
Click to collapse
Okay thanks dude. Gonna head to bed and read up on all that stuff tomorrow morning. If I run into any furthur problems could I PM you for help?
TynanV said:
Okay thanks dude. Gonna head to bed and read up on all that stuff tomorrow morning. If I run into any furthur problems could I PM you for help?
Click to expand...
Click to collapse
just quote me here I'll be with you ...your phone is not dead
you just need more info to get through everything to get back up and running
Okay... After reading a bunch of stuff, I still have no idea what I'm looking for/what I need to actually do. I'm trying to get my HTC One back to stock, and all the guides I'm seeing require the phone to actually be working (mine isn't, it's stock on the TWRP/recovery thing therefore I can't access any of my apps and whatnot). This is getting really frustrating.
Okay, I found a pic online of the part I'm stuck at. Here it is - http://www.tech-recipes.com/wp-content/uploads/2013/05/twrp-recovery-294x500.jpg I can only get to that screen and this one too - http://img.wonderhowto.com/img/88/1...e-install-custom-recovery-using-twrp.w654.jpg I cannot get back to my actual phone's screen, like this one I mean - http://img.wonderhowto.com/img/56/8...sense-style-home-screen-your-htc-one.w654.jpg
TynanV said:
Okay, I found a pic online of the part I'm stuck at. Here it is - http://www.tech-recipes.com/wp-content/uploads/2013/05/twrp-recovery-294x500.jpg I can only get to that screen and this one too - http://img.wonderhowto.com/img/88/1...e-install-custom-recovery-using-twrp.w654.jpg I cannot get back to my actual phone's screen, like this one I mean - http://img.wonderhowto.com/img/56/8...sense-style-home-screen-your-htc-one.w654.jpg
Click to expand...
Click to collapse
lol ok well that's very visual
did you find and read the parts about using fastboot and adb ? on your MAC ?
you should be close
boot to the bootloader (your 2nd screen shot) fastboot usb with phone plugged into you mac
open terminal and type
fastboot erase cache
then
fastboot reboot
does you phone start up now ?
TynanV said:
Okay, followed this tutorial today (can't post the link but it's called "How to Root HTC One! [Mac, Linux, Windows Tutorial]" and no matter what I do I can't seem to get back to the actual phone (i.e., being able to access the main screen where everything is, if you know what I mean). I've tried going to the recovery screen and hitting reboot but it just takes me back to this TWRP page that has a bunch of options like "Install, Wipe, Backup, Restore, Mount, Setting, etc. I really hope I haven't screwed up my phone permanently. Please help me :crying:
Click to expand...
Click to collapse
Try watching tutorial videos on youtube it will help you.
It helped me..
And read things again and agian till you dont get them right. Try to google some things when you are stuck in them.
Sent from my HTC Desire X using XDA Premium 4 mobile app
Here's the story. Got Google Fi package and Nexus 6 today. Decided I'd load Android M preview on Nexus 6. did all the fastboot stuff to get the developer preview installed, then while still in fastboot mode I installed TWRP, then locked fastboot, then rebooted into TWRP. Pushed ROM zip to /sdcard through adb, tried wiping everything failed. Tried flashing zip, everything failed. Decided to reboot. TWRP asked me if I wanted to install SuperSU, i chose to because I thought I might need it to get TWRP working. After rebooting got message "Your device has failed verification and may not work properly" then it powers off. I can boot into fastboot/recovery, but in recovery the touchscreen doesn't work so I can't do anything. Booting normally gives the failed verification message. Tried fastboot format userdata, which I believe is what caused the touchscreen to cease registering in TWRP.
Is there any way for me to recover this thing? Back when I had a Galaxy Nexus, and even with my S5, there's nothing really that can be done that would completely brick the thing. I'm pretty dumbfounded that a Nexus device would be so easily bricked...it's not like I don't have experience with this stuff, I've been rooting and developing Android apps for years.
I have a feeling I have to return the thing, but Amazon has no more stock, and if I buy directly from Google or Motorola I'll have to pay sales tax.
Any help is greatly appreciated.
claytonjn said:
Here's the story. Got Google Fi package and Nexus 6 today. Decided I'd load Android M preview on Nexus 6. did all the fastboot stuff to get the developer preview installed, then while still in fastboot mode I installed TWRP, then locked fastboot, then rebooted into TWRP. Pushed ROM zip to /sdcard through adb, tried wiping everything failed. Tried flashing zip, everything failed. Decided to reboot. TWRP asked me if I wanted to install SuperSU, i chose to because I thought I might need it to get TWRP working. After rebooting got message "Your device has failed verification and may not work properly" then it powers off. I can boot into fastboot/recovery, but in recovery the touchscreen doesn't work so I can't do anything. Booting normally gives the failed verification message. Tried fastboot format userdata, which I believe is what caused the touchscreen to cease registering in TWRP.
Is there any way for me to recover this thing? Back when I had a Galaxy Nexus, and even with my S5, there's nothing really that can be done that would completely brick the thing. I'm pretty dumbfounded that a Nexus device would be so easily bricked...it's not like I don't have experience with this stuff, I've been rooting and developing Android apps for years.
I have a feeling I have to return the thing, but Amazon has no more stock, and if I buy directly from Google or Motorola I'll have to pay sales tax.
Any help is greatly appreciated.
Click to expand...
Click to collapse
Did you lock the bootloader just to be clear?
bricked? no, you just didnt read up in information properly. you relocked your bootloader. as of android 5.0, you have to enable unlocking the bootloader after you boot up in the developer section. since you relocked your bootloader before you checked if your device will boot, you can not unlick your bootloader again, which means you can not use twrp either. what you can try is using fastboot to wipe your cache and data. if that doesnt work, id try to get an rma.
gee2012 said:
Did you lock the bootloader just to be clear?
Click to expand...
Click to collapse
Yes. I still remembered all of the flashboot commands from my Galaxy Nexus. It didn't even occur to me to look anything up.
simms22 said:
bricked? no, you just didnt read up in information properly. you relocked your bootloader. as of android 5.0, you have to enable unlocking the bootloader after you boot up in the developer section. since you relocked your bootloader before you checked if your device will boot, you can not unlick your bootloader again, which means you can not use twrp either. what you can try is using fastboot to wipe your cache and data. if that doesnt work, id try to get an rma.
Click to expand...
Click to collapse
If a device is unusable, without any way to recover it, it's essentially a paperweight, or bricked. So if my only option is an RMA, then it is bricked. I don't mean to sound rude or argumentative by the way... I appreciate your help. Just clarifying the semantics.
Debt from my Developer Edition Galaxy S5 using Tapatalk
have you tried fastboot oem unlock again ?
uicnren said:
have you tried fastboot oem unlock again ?
Click to expand...
Click to collapse
Yes, it says it needs to be enabled in developer options
Sent from my Developer Edition Galaxy S5 using Tapatalk
when you get the failed verification message, what happens after that?
does it ever make it to the M preview?
Also if you wait a little while after that message, you may be able to use adb commands again.
I had the same thing happen with M and TWRP and was able to recover it.
uicnren said:
when you get the failed verification message, what happens after that?
does it ever make it to the M preview?
Also if you wait a little while after that message, you may be able to use adb commands again.
I had the same thing happen with M and TWRP and was able to recover it.
Click to expand...
Click to collapse
It says it will reboot in 5 seconds, but after 5 seconds the screen just goes blank. It appears the device is off, but maybe not.
Do you know what adb commands I would need to use to recover from this state?
Sent from my Developer Edition Galaxy S5 using Tapatalk
claytonjn said:
Yes. I still remembered all of the flashboot commands from my Galaxy Nexus. It didn't even occur to me to look anything up.
If a device is unusable, without any way to recover it, it's essentially a paperweight, or bricked. So if my only option is an RMA, then it is bricked. I don't mean to sound rude or argumentative by the way... I appreciate your help. Just clarifying the semantics.
Debt from my Developer Edition Galaxy S5 using Tapatalk
Click to expand...
Click to collapse
technically, its not bricked, not yet anyways. as many people have fixed this issue using fastboot to wipe cache and data.
well, let it sit for a few minutes after the message, it may just boot normally. That verification message appears with M preview for many users.
you may also see HERE for another possible solution.
if adb is working, chances are pretty good its booting into android, in which case you wont need to do anything else, but let it boot (be patient, it can take several minutes), then retick the selection to allow oem unlock.
simms22 said:
technically, its not bricked, not yet anyways. as many people have fixed this issue using fastboot to wipe cache and data.
Click to expand...
Click to collapse
Unfortunately that is not working for me (Not allowed in locked state!)
uicnren said:
well, let it sit for a few minutes after the message, it may just boot normally. That verification message appears with M preview for many users.
you may also see HERE for another possible solution.
if adb is working, chances are pretty good its booting into android, in which case you wont need to do anything else, but let it boot (be patient, it can take several minutes), then retick the selection to allow oem unlock.
Click to expand...
Click to collapse
ADB works when I boot to TWRP, but when I try to boot normally, after the device will boot in 5 seconds message, the screen goes blank and adb does not work. I let it sit like that for more than 30 minutes. Curiously, when the screen goes blank my PC does chime indicating hardware has been attached.
Can you still get into twrp? If so just move a ROM over to it and flash that, enable OEM unlock restart and unlock boot loader...
claytonjn said:
Unfortunately that is not working for me (Not allowed in locked state!)
ADB works when I boot to TWRP, but when I try to boot normally, after the device will boot in 5 seconds message, the screen goes blank and adb does not work. I let it sit like that for more than 30 minutes. Curiously, when the screen goes blank my PC does chime indicating hardware has been attached.
Click to expand...
Click to collapse
If you have TWRP, boot to bootloader and use the following fastboot commands:
fastboot format userdata
fastboot format cache
Then boot to TWRP, connect to PC. Download a ROM to your PC and drag and drop in the root of internal storage. Then flash the ROM from TWRP, boot up, enable OEM unlock. Then boot back to bootloader and:
fastboot oem unlock
You should be good after that.
holeindalip said:
Can you still get into twrp? If so just move a ROM over to it and flash that, enable OEM unlock restart and unlock boot loader...
Click to expand...
Click to collapse
I can boot into TWRP. At first it was "working" but it couldn't mount /data so I couldn't really do anything (that was the first thing I tried.) Now however when I boot to TWRP it doesn't respond to touch at all... I can get into a shell with adb, but I haven't figured out anything to do from there.
claytonjn said:
I can boot into TWRP. At first it was "working" but it couldn't mount /data so I couldn't really do anything (that was the first thing I tried.) Now however when I boot to TWRP it doesn't respond to touch at all... I can get into a shell with adb, but I haven't figured out anything to do from there.
Click to expand...
Click to collapse
Follow my instructions listed above.
Evolution_Tech said:
Follow my instructions listed above.
Click to expand...
Click to collapse
II'm attempting that now.but fastboot format userdata and fastboot format cache fail. after booting into twrp the Nexus shows up in My Computer, but internal storage does not. I can push a ROM zip to the device with adb, but haven't figured out how to flash it yet because touch doesn't work...
SUCCESS! I was able to flash the ROM .zip using ADB in TRWP using
Code:
ADB push ROM.zip /sdcard/.
ADB shell
twrp install /sdcard/ROM.zip
THANK YOU EVERYONE!
claytonjn said:
SUCCESS! I was able to flash the ROM .zip using ADB in TRWP using
Code:
ADB push ROM.zip /sdcard/.
ADB shell
twrp install /sdcard/ROM.zip
THANK YOU EVERYONE!
Click to expand...
Click to collapse
glad you got it back, persistence pays off.
Lesson learned today? QUIT RE-LOCKING YOUR BOOTLOADER!
You can lock boot loader, you just have to make sure your phone boots first before locking it
So let's say theoretically that someone in their first week of using an Android device (ever) were to boot up the TWRP recovery and wipe their Fire because YOLO. Would anyone have advice for any possible way to revive it? Here's a description of the device's state:
It boots the Amazon logo only, and adb lists the device as unauthorized. If I boot it in recovery it says it's in fastboot mode and adb doesn't recognize the device at all. (Edit: ) Fastboot does recognize it though, but I'm not sure of the best path to take since I can't use adb to push files to the device for reinstallation of the firmware.
So from my view it's a paperweight, and that's cool because what I did was all kinds of dumb (thinking I could still revive it after what I was doing). But before I use it as a door stop, I figured I might ask you guys what you'd do. I'm guessing maybe I boot from an image that allows me to push the firmware to the sdcard, then I can boot from TWRP recovery and install it, but the first image to use there is something I'm not yet sure of.
Have you tried the methods at http://forum.xda-developers.com/amazon-fire/general/unbrick-restore-stock-2015-amazon-fire-t3250639
stultus2 said:
Have you tried the methods at http://forum.xda-developers.com/amazon-fire/general/unbrick-restore-stock-2015-amazon-fire-t3250639
Click to expand...
Click to collapse
Thanks for the reply
I think that's along the lines of what I need to do, but I can't use adb sideload as adb no longer sees the devices in recovery. Fastboot does though.
stultus2 said:
Have you tried the methods at http://forum.xda-developers.com/amazon-fire/general/unbrick-restore-stock-2015-amazon-fire-t3250639
Click to expand...
Click to collapse
Ah you know what, you just encouraged me to read over again and try one different thing. The CM recovery enables adb sideload, and I'm pushing the stock firmware to it now.
Thanks for the help