Database Develop

[HOW TO] Safely Update Your Radio For Froyo Using Fastboot

UPDATING YOUR RADIO
IMPORTANT - READ ALL OF THIS POST​
I originally wrote this post for Kang-o-rama but, considering everybody will need to update their radio at some stage, though I would x-post it here. Hopefully a mod will sticky, at least for the next three or four weeks.
You phone is designed to support updating the radio image. The radio image is primarily used to control the mobile communication of your phone. Other functions are sometimes offloaded to the radio cpu including, in the case of the Nexus, some video processing. Because of the codependencies between the radio, the kernel and the rom, it is occasionally necessary to update your radio.
Froyo (Android 2.2) requires a new radio and so does CyanogenMod 6.0 and Kang-o-rama 1.0.
Updating your radio is safe if you do it properly and carefully. It is very unsafe if you do not. One of the consequences of a failed radio update is a bricked (useless) phone. This risk is not the same when updating a kernel or a rom.
To update your radio to a suitable version for Kang-o-rama 1.0, Froyo or CyanogenMod 6.0 using fastboot follow the following instructions below carefully. The scope of this guide does not extend to getting fastboot working on your computer and your phone connected. Please see the sticky threads in this forum and search for additional information if you are unsure.
Fully charge your phone
Download the radio image from the link below
Compare the MD5 checksum of the file you downloaded with the one printed below. This is very important, please do it. For Windows or OSX you can use the free HashTab application.
Connect your phone to your computer
Reboot your phone into the bootloader (fastboot mode)
At the command prompt on your computer type: fastboot devices
A value like HTXXXXXXXXXXX should be displayed with the word fastboot next to it
Your phone screen should have FASTBOOT USB on it
If all of the above is not exactly as described DO NOT PROCEED and resolve your fastboot problem
To proceed, make sure your downloaded file is in your current directory
At the command prompt type: fastboot flash radio froyo-radio-32.36.00.28U_4.06.00.02_2.img - you must type it correctly!
Now, observe the computer and be patient TOUCH NOTHING!!
The process will copy the image to your phone, write the image to the radio partition and perform some magic be patient TOUCH NOTHING!!
Watch the little indicator at the top of your phone screen.
Once the process appears to finish (it may not say complete) wait a further FULL 60 SECONDS and be patient TOUCH NOTHING!!
Then, and only then, reboot your phone.
Your phone should reboot to your normal home screen and you should get a mobile connection.
Remember, if you're still using an older rom some things won't work. Best you now upgrade to Kang-o-rama 1.0!
Download: froyo-radio-32.36.00.28U_4.06.00.02_2.img
MD5 Checksum: 3321c196d8ec1cf748fd20c3c4068520
Take care.

Reserved for who only knows what...

Is there a zip file that can be downloaded to the N1? I don't have access to a computer,at least not for awhile.

after the cmd says writing radio it finishes and my phone stays on the fastboot screen. I can use the volume buttons to move the selector and reboot but the radio on the fastboot screen still says RADIO-4.06.00.12.7

when u use fastboot , it doesnt reboot itself n u have to reboot it urself and after it has flashed in fastboot u are safe to do anything but only after the red bar on the top right corner disappears. Red one comes after green one. Then u have to type fastboot reboot or use the menu to reboot. It will do nothing magical after than but boot straight to the system. U mixed up recovery flashing and fastboot

how about flash via Recovery ? I think its safer and much more convenient

U r most probably gonna f up using recovery. My experience some days ago with my cliq lol

cronin4392 said:
after the cmd says writing radio it finishes and my phone stays on the fastboot screen. I can use the volume buttons to move the selector and reboot but the radio on the fastboot screen still says RADIO-4.06.00.12.7
Click to expand...
Click to collapse
I'm having this same exact issue. I followed the instructions exactly all the way to reboot.
It's weird because the 720p mod works fine afterwards where before it would crash the phone when trying to record or open the camera settings.

Man please someone anyone help me. i have done exactly what the steps say and fastboot wont comply. all i get is C:\Users\Whoisc_walk>fastboot flash radio froyo-radio-32.36.00.28U_4.06.00.02_2.
img
error: cannot load 'froyo-radio-32.36.00.28U_4.06.00.02_2.img'
im not really sure what i did wrong. i think it may be the directory but as far as i know its in the correct one. so im getting frustrated so im asking for help
figured it out it was a directory problem

C_walk said:
Man please someone anyone help me. i have done exactly what the steps say and fastboot wont comply. all i get is C:\Users\Whoisc_walk>fastboot flash radio froyo-radio-32.36.00.28U_4.06.00.02_2.
img
error: cannot load 'froyo-radio-32.36.00.28U_4.06.00.02_2.img'
im not really sure what i did wrong. i think it may be the directory but as far as i know its in the correct one. so im getting frustrated so im asking for help
figured it out it was a directory problem
Click to expand...
Click to collapse
Have to be in the directory where fastboot is.. from there you can flash the Radio.

I always got "verify fail" messages, could anyone help me? Thanks
C:\Downloads\android>fastboot flash radio froyo-radio-32.36.00.28U_4.06.00.02_2.img
sending 'radio' (26112 KB)... OKAY [ 3.656s]
writing 'radio'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 7.609s

silentfishwm said:
I always got "verify fail" messages, could anyone help me? Thanks
C:\Downloads\android>fastboot flash radio froyo-radio-32.36.00.28U_4.06.00.02_2.img
sending 'radio' (26112 KB)... OKAY [ 3.656s]
writing 'radio'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 7.609s
Click to expand...
Click to collapse
Try downloading the img again, check the MD5.
Also make sure your battery is fully charged.

djmcnz, thanks for your help, I double checked the MD5, it's correct and the phone was fully charged. Any other possible cause of this error?
djmcnz said:
Try downloading the img again, check the MD5.
Also make sure your battery is fully charged.
Click to expand...
Click to collapse

silentfishwm said:
djmcnz, thanks for your help, I double checked the MD5, it's correct and the phone was fully charged. Any other possible cause of this error?
Click to expand...
Click to collapse
You are running a rooted phone with a custom recovery image correct?

silentfishwm said:
I always got "verify fail" messages, could anyone help me? Thanks
C:\Downloads\android>fastboot flash radio froyo-radio-32.36.00.28U_4.06.00.02_2.img
sending 'radio' (26112 KB)... OKAY [ 3.656s]
writing 'radio'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 7.609s
Click to expand...
Click to collapse
Is your bootloader unlocked? Or did you root without unlocking the bootloader?
________________________
N1 w/ XDA App

Ooopps.... I'm using a rooted phone with locked bootloader, I'm an idiot
Is there anyway for my phone to make a radio update?
djmcnz said:
You are running a rooted phone with a custom recovery image correct?
Click to expand...
Click to collapse

J.L.C, yes I rooted my phone without unlocking the bootloader...
Any way to update radio in such case?
J.L.C. said:
Is your bootloader unlocked? Or did you root without unlocking the bootloader?
________________________
N1 w/ XDA App
Click to expand...
Click to collapse

silentfishwm said:
J.L.C, yes I rooted my phone without unlocking the bootloader...
Any way to update radio in such case?
Click to expand...
Click to collapse
In that case you have to update the radio though recovery with a zip file.
________________________
N1 w/ XDA App

Thanks J.L.C., I have got the radio updated with an update.zip
J.L.C. said:
In that case you have to update the radio though recovery with a zip file.
________________________
N1 w/ XDA App
Click to expand...
Click to collapse

I have an unlocked g1 for at&t if I update the radio will I have to unlock it again

[Q] Boot hangs at white HTC screen, cannot boot recovery, no ADB

I suspect some type of hardware failure... the phone had been working fine, suddenly it was frozen at the lock screen. Pulled battery, now it just shows the white HTC screen forever.
HOME + Power = No recovery, just white HTC screen. Not detected by ADB.
Volume Down + Power = HBOOT (3 skateboards)
Volume Up from HBOOT = USB Fastboot, fastboot.exe will detect the phone.
HOME from HBOOT (Recovery) = Indefinite white HTC boot screen.
Tried reflashing recovery via fastboot: "fastboot update recovery-RA-heroc-v162.img" but response is "FAILED (remote: not allow)
Tried Sprint RUU but got CID error, read about and created goldcard and then the RUU installed 100% without error....
... but the phone still just hangs at the white HTC screen.
Brick?

I know how you feel. I'm having the EXACTLY same issue and desperately need help.

I wouldn't feel so bad if I had been jacking with the phone trying to do something crazy, but it has been running great with no tweaking for months and suddenly it does this.
I am inclined to just assume hardware failure of some type, but HBOOT and RUU working make me second guess myself so I haven't tossed it into the trash just yet...

what root method did you use? link please. are you s-off? if you don't know, then you're s-on. also, do you have adb (usb debugging)? you can rebuild the phone - no RUU needed - by either adb pushing recovery to the phone, or by flashing a HERCIMG while in s-off bootloader.

He said in the op that adb isn't working...
il Duce said:
what root method did you use? link please. are you s-off? if you don't know, then you're s-on. also, do you have adb (usb debugging)? you can rebuild the phone - no RUU needed - by either adb pushing recovery to the phone, or by flashing a HERCIMG while in s-off bootloader.
Click to expand...
Click to collapse
Sent from my Hero running aosp Froyo.

D3FAULT said:
He said in the op that adb isn't working...
Sent from my Hero running aosp Froyo.
Click to expand...
Click to collapse
hmmm, ok, well I guess the other part of my post would be the important part then. HERCIMG if he has s-off might work.... trying to come up with some ideas, thanks for the wildly helpful input though, douche.

Farkonian said:
I suspect some type of hardware failure... the phone had been working fine, suddenly it was frozen at the lock screen. Pulled battery, now it just shows the white HTC screen forever.
HOME + Power = No recovery, just white HTC screen. Not detected by ADB.
Volume Down + Power = HBOOT (3 skateboards)
Volume Up from HBOOT = USB Fastboot, fastboot.exe will detect the phone.
HOME from HBOOT (Recovery) = Indefinite white HTC boot screen.
Tried reflashing recovery via fastboot: "fastboot update recovery-RA-heroc-v162.img" but response is "FAILED (remote: not allow)
Tried Sprint RUU but got CID error, read about and created goldcard and then the RUU installed 100% without error....
... but the phone still just hangs at the white HTC screen.
Brick?
Click to expand...
Click to collapse
another q - when in fastboot, the command you put in "fastboot update ...." is wrong, that's for a rom zip. I assume you're using cmd, so, the first thing you should type is "fastboot devices" your phone should list. Then type "fastboot shell" you should get the # symbol. Then your command should say "fastboot erase recovery" then "fastboot flash recovery <filename> .... (the recovery you want)". I don't know if this is what you typed or not, as you didn't say, but did you? If not, give it a try. I just read this in the threads I linked below, hope it helps.
Here's a couple helpful links for fastboot
http://forum.xda-developers.com/showthread.php?t=532719
http://forum.xda-developers.com/showthread.php?t=517874
Here's for s-off and making a HERCIMG
http://forum.xda-developers.com/showthread.php?t=759955
http://forum.xda-developers.com/showthread.php?t=765429

il Duce said:
another q - when in fastboot, the command you put in "fastboot update ...." is wrong I think - are you in cmd? I assume so, the first thing you should type is "fastboot devices" your phone should list. Then type "fastboot shell" you should get the # symbol. Then your command should say "fastboot erase recovery" then "fastboot flash recovery <filename> .... (the recovery you want)". I don't know if this is what you typed or not, as you didn't say, but did you? If not, give it a try. I just read this in the threads I linked below, hope it helps.
Here's a couple helpful links for fastboot
http://forum.xda-developers.com/showthread.php?t=532719
http://forum.xda-developers.com/showthread.php?t=517874
Here's for s-off and making a HERCIMG
http://forum.xda-developers.com/showthread.php?t=759955
http://forum.xda-developers.com/showthread.php?t=765429
Click to expand...
Click to collapse
As you suspected, I was doing fastboot wrong. I will attempt reflashing via fastboot again and report the results. Thanks.
*EDIT* -- Well, that was short lived:
Code:
C:\Temp\android-sdk-windows\tools>fastboot devices
HT04DHF02850 fastboot
C:\Temp\android-sdk-windows\tools>fastboot shell
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
C:\Temp\android-sdk-windows\tools>
Am I still doing something wrong? Wrong version of fastboot perhaps?

Farkonian said:
As you suspected, I was doing fastboot wrong. I will attempt reflashing via fastboot again and report the results. Thanks.
Click to expand...
Click to collapse
good, I just pm'd you as well, I edited the post with better detail, and yes please do post results, and good luck.

Must run out the door to work, but will likely have the opportunity to mess with the phone at the office... I'll check back in a while to see if there is something else I can try. Thanks for the help.

Farkonian said:
Must run out the door to work, but will likely have the opportunity to mess with the phone at the office... I'll check back in a while to see if there is something else I can try. Thanks for the help.
Click to expand...
Click to collapse
I can't really decipher what was wrong. The part where you typed fastboot shell? looks like you didn't get the # right? Try the commands without that, the guide is old, but the commands are right. Try:
fastboot erase recovery
fastboot flash recovery "recovery.img"
of course where it says "recovery.img" put in the actual name of the recovery. good luck
Report back.

il Duce said:
hmmm, ok, well I guess the other part of my post would be the important part then. HERCIMG if he has s-off might work.... trying to come up with some ideas, thanks for the wildly helpful input though, douche.
Click to expand...
Click to collapse
Wasn't trying to be a douche, but okay.

The command "fastboot shell" does not put me into a "#" prompt, I just get the fastboot help text. I might as well have typed "fastboot lasagna" <GRIN>
"fastboot erase recovery" results in an error message "FAILED (remote: not allow)". I get same error message for everything I try in fastboot.

Farkonian said:
The command "fastboot shell" does not put me into a "#" prompt, I just get the fastboot help text. I might as well have typed "fastboot lasagna" <GRIN>
"fastboot erase recovery" results in an error message "FAILED (remote: not allow)". I get same error message for everything I try in fastboot.
Click to expand...
Click to collapse
do you have the eng-spl (I just assumed you did)? from here:http://forum.xda-developers.com/showthread.php?t=765237
if you don't have an s-off hboot, or an eng-spl fastboot, I am out of ideas... You may be able to get more answers in here http://webirc.fossnet.info:9090/?channels=aospbot, but only if you are REALLY REALLY patient, and of course you may be screwed. You are NOT bricked, I just can't come up with a way to fix it, my brain is fryed. lol.

il Duce said:
do you have the eng-spl (I just assumed you did)? from here:http://forum.xda-developers.com/showthread.php?t=765237
if you don't have an s-off hboot, or an eng-spl fastboot, I am out of ideas... You may be able to get more answers in here http://webirc.fossnet.info:9090/?channels=aospbot, but only if you are REALLY REALLY patient, and of course you may be screwed. You are NOT bricked, I just can't come up with a way to fix it, my brain is fryed. lol.
Click to expand...
Click to collapse
I don't think I understand what I am supposed to do with this... it appears to be an image to flash, but so far I have been completely unable to flash anything to the phone. Thoughts?

Farkonian said:
I don't think I understand what I am supposed to do with this... it appears to be an image to flash, but so far I have been completely unable to flash anything to the phone. Thoughts?
Click to expand...
Click to collapse
if you can't boot into recovery, or a rom, and you don't have adb access, or and eng-spl fastboot, or an s-off hboot, I am lost. There may be a way, but I don't know what it would be, sorry.

So the ENG-SPL boot would have to have already been flashed to the phone to be useful now?

Farkonian said:
So the ENG-SPL boot would have to have already been flashed to the phone to be useful now?
Click to expand...
Click to collapse
yes, or s-off hboot. I believe that is why you get the not allowed error.

I discovered that if I try to install the RUU without the goldcard, it fails but puts the phone into a different bootloader mode (black screen with HTC). From this screen I can use fastboot to push files, but they all fail the signature check.
Code:
C:\Program Files (x86)\android-sdk-windows\tools>fastboot flash recovery recovery-RA-heroc-v1.6.2.img
sending 'recovery' (3720 KB)... OKAY [ 4.942s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 5.891s
I suppose this is still of no value... unless there is a signed recovery replacement to try flashing?

Farkonian said:
I discovered that if I try to install the RUU without the goldcard, it fails but puts the phone into a different bootloader mode (black screen with HTC). From this screen I can use fastboot to push files, but they all fail the signature check.
Code:
C:\Program Files (x86)\android-sdk-windows\tools>fastboot flash recovery recovery-RA-heroc-v1.6.2.img
sending 'recovery' (3720 KB)... OKAY [ 4.942s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 5.891s
I suppose this is still of no value... unless there is a signed recovery replacement to try flashing?
Click to expand...
Click to collapse
try a different recovery, like darch ra 1.7, or clockwork

[Q] my hero can't boot into recovery .. Can anyone help me

my hero cdma can't boot into recovery and can't work only in the normal position after use (fastboot oem boot)
when i power the device and unplug USB cable show me in the screen this lines
Code:
HERO XC SHIP S-OFF
HBOOT-1.47.0000 (HERO20000)
MICROP-0110
TOUCH PANEL-SYN0104
RADIO-2.41.05.02.99
Mar 1 2010, 16:02:39
RUU
Even when I press volume down + power .. the screen remains black and does not show anything
I tried a lot to work root and flash recovery.img again by (recovery-RA-heroc-v1.6.2.img) .. but every time i enter ((reboot recovery)) does not appear to me anything except previous message ..
my software v2.27.651.5
pardon me because i can't speak english well .. and I ask for your immediate help

Place this on the root of your sdcard. Boot into hboot (fastboot) and press the down volume key, that's hboot mode. It'll find the HERCIMG.zip, which is just the RUU and after it flashes you're phone will be back to stock.

DoonRoman said:
my hero cdma can't boot into recovery and can't work only in the normal position after use (fastboot oem boot)
when i power the device and unplug USB cable show me in the screen this lines
Code:
HERO XC SHIP S-OFF
HBOOT-1.47.0000 (HERO20000)
MICROP-0110
TOUCH PANEL-SYN0104
RADIO-2.41.05.02.99
Mar 1 2010, 16:02:39
RUU
Even when I press volume down + power .. the screen remains black and does not show anything
I tried a lot to work root and flash recovery.img again by (recovery-RA-heroc-v1.6.2.img) .. but every time i enter ((reboot recovery)) does not appear to me anything except previous message ..
my software v2.27.651.5
pardon me because i can't speak english well .. and I ask for your immediate help
Click to expand...
Click to collapse
Im having the same exact error
what i did first is that i accessed the recovery mode without knowing and i did the wipe/factory default settings
it brought me to a black screen with only the top slider while that the recovery mode was working
later i installed the ruu software 2.27.651.6 and downloaded it from htc website , at the end of the installing it showed file error cant open
i thought i was just that software (and i didnt download it right) later i tried installing the 1.27 , 1.56 , 2.27.651.5 and the 2.27.651.6 again and it still gave me the same error
after searching on the net i found the command fastboot oem boot which works only with 2.27.651.5 and the 2.27.651.6 version now i cant open my htc hero sprint without this command ,
is there a way to fix it ? please help

It sounds to me like the only way you'll be able to fix your phone is through adb. I'm not sure of the exact steps, but read up on the procedures that have been written up on using adb and you should be able to find what you need. That's all I can think of...

cytherian said:
It sounds to me like the only way you'll be able to fix your phone is through adb. I'm not sure of the exact steps, but read up on the procedures that have been written up on using adb and you should be able to find what you need. That's all I can think of...
Click to expand...
Click to collapse
im already familiar to the adb and fastboot commands , tho i dont know the exact steps to fix my problem , because the other steps i found on the net crashes at a point such as flash_image says it cant find the image , and the fastboot flash update.zip says image is not supported

mrxuser said:
im already familiar to the adb and fastboot commands , tho i dont know the exact steps to fix my problem , because the other steps i found on the net crashes at a point such as flash_image says it cant find the image , and the fastboot flash update.zip says image is not supported
Click to expand...
Click to collapse
Bummer... well, sorry I don't know what else to tell you at this point. If you follow the steps for putting your phone completely back to stock and it crashes before it completes, then your phone may have a hardware problem. Did you overclock it at all?

cytherian said:
Bummer... well, sorry I don't know what else to tell you at this point. If you follow the steps for putting your phone completely back to stock and it crashes before it completes, then your phone may have a hardware problem. Did you overclock it at all?
Click to expand...
Click to collapse
what do u mean by overclocking

mrxuser said:
what do u mean by overclocking
Click to expand...
Click to collapse
Overclocking makes the phone faster, in simple terms. It's risky. I assume that you didn't?

ElementalBeatz said:
Overclocking makes the phone faster, in simple terms. It's risky. I assume that you didn't?
Click to expand...
Click to collapse
yes never done it before, would the phone be fixed if i did?

No, I only brought it up because overclocking can challenge the hardware and if it overheats then you might run into functional issues. If you didn't overclock then this isn't a factor.
I don't have my main computer handy with all of my browser shortcuts (I've got quite a library from researching rooting, modding, etc), but I know for certain that there are at least 3+ ways to load a new recovery program onto your phone, or get back to a stock ROM even if you brick your phone. You'll have to take the time to search the forums for those earlier guides, the ones before programs were developed to make rooting and flashing ROM's easier (not needing to know much about adb). AndroidForums has quite a few good ones. Check out their FAQ for the HTC Hero.
One other thing... I noticed your bootloader is 1.47. I had issues with that bootloader, with trying to set S-OFF. I had to override with 1.46. You might want to try an earlier bootloader.

cytherian said:
No, I only brought it up because overclocking can challenge the hardware and if it overheats then you might run into functional issues. If you didn't overclock then this isn't a factor.
I don't have my main computer handy with all of my browser shortcuts (I've got quite a library from researching rooting, modding, etc), but I know for certain that there are at least 3+ ways to load a new recovery program onto your phone, or get back to a stock ROM even if you brick your phone. You'll have to take the time to search the forums for those earlier guides, the ones before programs were developed to make rooting and flashing ROM's easier (not needing to know much about adb). AndroidForums has quite a few good ones. Check out their FAQ for the HTC Hero.
One other thing... I noticed your bootloader is 1.47. I had issues with that bootloader, with trying to set S-OFF. I had to override with 1.46. You might want to try an earlier bootloader.
Click to expand...
Click to collapse
If u dont mind can u show me how to install earilier bootloaders ?

Since you can't get your phone fully booted, you won't be able to use ADB. But if you can load the bootloader into Fastboot USB, then use "fastboot". Read up on the Fastboot Wiki and Flash Tutorial. The only caveat is that I've seen two variations on flashing the bootloader using fastboot. Whereas the Wiki I linked shows "fastboot flash boot boot.img", I've also seen "fastboot flash hboot.img" (but I think that may be a typo--certainly it'll let you know).
If you have a ZIP file instead of an IMG file, there will be an "hboot.img" within the ZIP file. I think the fastboot is intelligent enough to know that it needs to be applied to the boot partition. So, you can also do this:
* fastboot oem rebootRUU //Boot into RUU, which lets you flash HBOOT, radio, etc.
* fastboot flash zip [zipname.zip] //Replace zipname.zip with the actual name of the file you are flashing
-- or --
* fastboot flash boot [boot.img]
However, if your current bootloader state is S-ON, you may not be able to execute those commands successfully. I know for myself I had to install ROM Manager to override the hboot 1.47 S-ON that I had installed, which downgraded the hboot. From there I was able to override and flash hboot 1.46 S-OFF.

cytherian said:
Since you can't get your phone fully booted, you won't be able to use ADB. But if you can load the bootloader into Fastboot USB, then use "fastboot". Read up on the Fastboot Wiki.
Click to expand...
Click to collapse
I already told u that i can use Adb and fastboot , i cant open my phone unless i use this command fastboot oem boot ,

Well good luck with that...

cytherian said:
Since you can't get your phone fully booted, you won't be able to use ADB. But if you can load the bootloader into Fastboot USB, then use "fastboot". Read up on the Fastboot Wiki and Flash Tutorial. The only caveat is that I've seen two variations on flashing the bootloader using fastboot. Whereas the Wiki I linked shows "fastboot flash boot boot.img", I've also seen "fastboot flash hboot.img" (but I think that may be a typo--certainly it'll let you know).
If you have a ZIP file instead of an IMG file, there will be an "hboot.img" within the ZIP file. I think the fastboot is intelligent enough to know that it needs to be applied to the boot partition. So, you can also do this:
* fastboot oem rebootRUU //Boot into RUU, which lets you flash HBOOT, radio, etc.
* fastboot flash zip [zipname.zip] //Replace zipname.zip with the actual name of the file you are flashing
-- or --
* fastboot flash boot [boot.img]
However, if your current bootloader state is S-ON, you may not be able to execute those commands successfully. I know for myself I had to install ROM Manager to override the hboot 1.47 S-ON that I had installed, which downgraded the hboot. From there I was able to override and flash hboot 1.46 S-OFF.
Click to expand...
Click to collapse
here is the problem while flashing using fastboot
fastboot flash radio radio1.img
sending 'radio' (21376 KB)...
OKAY [ 24.089s]
writing 'radio'...
FAILED (remote: image type not support)
finished. total time: 24.108s
or here when i use flash the zip
fastboot flash zip update.zip
sending 'zip' (118067 KB)...
OKAY [129.171s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 132.015s
why does the (remote: image type not support) or the (remote: 24 parsing android-info fail) appear

Have you tried what I posted yet?

Shelnutt2 said:
Have you tried what I posted yet?
Click to expand...
Click to collapse
the problem is that i cant no more enter the hboot menu but i can use the fastboot commands while the Htc silver Logo appears
> fastboot devices
HT9BEHF03035 fastboot
and when i used this command
>fastboot flash zip HERCIMG.zip
sending 'zip' (114210 KB)...
OKAY [129.813s]
writing 'zip'...
its stuck on writing 'zip' and havent done anything for more than 20 min , whats wrong here ??!!

mrxuser said:
the problem is that i cant no more enter the hboot menu but i can use the fastboot commands while the Htc silver Logo appears
> fastboot devices
HT9BEHF03035 fastboot
and when i used this command
>fastboot flash zip HERCIMG.zip
sending 'zip' (114210 KB)...
OKAY [129.813s]
writing 'zip'...
its stuck on writing 'zip' and havent done anything for more than 20 min , whats wrong here ??!!
Click to expand...
Click to collapse
so there's nothing to help

Guys , Arent there anything to do to my program ,,, if somebody knows ,,,, please tell me

[Q] Stuck in RElocked bootloader cannot unlock

Hello, I've been raking up the other xda posts all night and can't seem to find the right solution for my situation. Am a total noob so would really appreciate any instructions, whether to solve the problem or to point me to the right post. Quite lost here.
So, I've been trying to return my HTC one to stock (hk version; CID: HTC__622; modelid: PN0714000) and got into trouble. I used to have CM 10.2 with TWRP recovery. So I used TWRP to install what I thought was a stock ROM (not sure if I'm using the terms right) My current situation, in gist:
(1) Can only load into bootloader, if reboot normally then I get htc splash screen then black screen. -->Refuses to boot into the operating system!!!!!! All I get is the htc flash screen then the black screen until eternity (or I force reboot it by holding vol down and power button under strong light-- tip I got from these parts)
(2) Bootloader (top of) reads "tampered" (which I'm least concerned with) and "relocked"
(at one point it said "security warning" as well… but then that disappeared-- see below)
(3) I cannot use adb via either my Mac/ Windows, I have downloaded google SDK and updated HTC drivers on both machines-- adb devices command simply does not register my phone
(4) atm I am only communicating to my phone via fastboot commands… of which I know next to nth except what are commonly found in these forums…
(5) My machine is still S-off. Before my troubles, it was hboot 1.54, after messing around with it, it's now 1.55 if that makes any difference.
I desperate need my phone for the working week…. PLEASE HELP!!!
FYI: I'm on a Mac, but I do have access to a Windows machine running Windows 7
What I have done so far:-
(1) So I was trying to get back to stock, right? First thing I did was used HTC1guru's Guru reset. The ROM I installed was actually for the Asia WWE variant.
Anyway, so I installed it, and it worked, to the extent that I could get OTA notifications and downloaded the update. But HTC could not verify it and did not allow me to install the update. Because I wanted the Kitkat update, I looked up the net to see what could be the problem.
(2) The next mistake I made (probably a mistake) was to think that I had to relock the bootloader. So I did that. Now my Bootloader is relocked and I cannot, for the life of me unlock it again (I've tried going through the HTC dev steps and flashing the new Unlock_code.bin again but I can't unlock it)
At this point, the bootloader also read "security warning" under "relocked"
Subsequent to relocking it, I can't get into my operating system anymore. The only 2 outcomes I get on reboot are (1) HTC splash screen followed by black screen; OR (2) bootloader (if I do power + vol down)
(3) As one 'brilliant' idea followed another 'brilliant' idea, I also did the following list of silly and probably mistaken things our of sheer desperation. Throwing the kitchen sink in really. But none of them really worked because they all say sign not verified or sth to that effect-- I honestly am beginning to forget the order in which things unfolded… but if that's relevant, let me know and I'll try to recall more details.
(a) flash a recovery.img (stock, for both Asia WWE and HK version which I found on the web; and also TWRP)
(b) flash boot.img from Asia WWE
(c )tried rumrunner (can't do because adb won't work)
My latest attempt has been flash oem reboot RUU (then used zip of HK version 1.29.708 Rom zip)
and my phone is now stuck at the grey HTC on black background screen one gets after the first reboot RUU command (terminal has not prompted me to enter a second rebootRUU command yet!)
I don't know what to do. I don't even know if I should unplug the phone and redo the rebootRUU thing…
:crying: PLEASE HELP!!!!

FURTHER to the above
jaqzilch said:
...
My latest attempt has been flash oem reboot RUU (then used zip of HK version 1.29.708 Rom zip)
and my phone is now stuck at the grey HTC on black background screen one gets after the first reboot RUU command (terminal has not prompted me to enter a second rebootRUU command yet!)
I don't know what to do. I don't even know if I should unplug the phone and redo the rebootRUU thing…
:crying: PLEASE HELP!!!!
Click to expand...
Click to collapse
I've unplugged the phone, rebooted into bootloader, and made a second attempt to rebootRUU with HKvariant 1.29 zip… still gets stuck after 1st rebootRUU command (i.e. black screen with grey HTC logo)
Please do help,

jaqzilch said:
Hello, I've been raking up the other xda posts all night and can't seem to find the right solution for my situation. Am a total noob so would really appreciate any instructions, whether to solve the problem or to point me to the right post. Quite lost here.
So, I've been trying to return my HTC one to stock (hk version; CID: HTC__622; modelid: PN0714000) and got into trouble. I used to have CM 10.2 with TWRP recovery. So I used TWRP to install what I thought was a stock ROM (not sure if I'm using the terms right) My current situation, in gist:
(1) Can only load into bootloader, if reboot normally then I get htc splash screen then black screen. -->Refuses to boot into the operating system!!!!!! All I get is the htc flash screen then the black screen until eternity (or I force reboot it by holding vol down and power button under strong light-- tip I got from these parts)
(2) Bootloader (top of) reads "tampered" (which I'm least concerned with) and "relocked"
(at one point it said "security warning" as well… but then that disappeared-- see below)
(3) I cannot use adb via either my Mac/ Windows, I have downloaded google SDK and updated HTC drivers on both machines-- adb devices command simply does not register my phone
(4) atm I am only communicating to my phone via fastboot commands… of which I know next to nth except what are commonly found in these forums…
(5) My machine is still S-off. Before my troubles, it was hboot 1.54, after messing around with it, it's now 1.55 if that makes any difference.
I desperate need my phone for the working week…. PLEASE HELP!!!
FYI: I'm on a Mac, but I do have access to a Windows machine running Windows 7
What I have done so far:-
(1) So I was trying to get back to stock, right? First thing I did was used HTC1guru's Guru reset. The ROM I installed was actually for the Asia WWE variant.
Anyway, so I installed it, and it worked, to the extent that I could get OTA notifications and downloaded the update. But HTC could not verify it and did not allow me to install the update. Because I wanted the Kitkat update, I looked up the net to see what could be the problem.
(2) The next mistake I made (probably a mistake) was to think that I had to relock the bootloader. So I did that. Now my Bootloader is relocked and I cannot, for the life of me unlock it again (I've tried going through the HTC dev steps and flashing the new Unlock_code.bin again but I can't unlock it)
At this point, the bootloader also read "security warning" under "relocked"
Subsequent to relocking it, I can't get into my operating system anymore. The only 2 outcomes I get on reboot are (1) HTC splash screen followed by black screen; OR (2) bootloader (if I do power + vol down)
(3) As one 'brilliant' idea followed another 'brilliant' idea, I also did the following list of silly and probably mistaken things our of sheer desperation. Throwing the kitchen sink in really. But none of them really worked because they all say sign not verified or sth to that effect-- I honestly am beginning to forget the order in which things unfolded… but if that's relevant, let me know and I'll try to recall more details.
(a) flash a recovery.img (stock, for both Asia WWE and HK version which I found on the web; and also TWRP)
(b) flash boot.img from Asia WWE
(c )tried rumrunner (can't do because adb won't work)
My latest attempt has been flash oem reboot RUU (then used zip of HK version 1.29.708 Rom zip)
and my phone is now stuck at the grey HTC on black background screen one gets after the first reboot RUU command (terminal has not prompted me to enter a second rebootRUU command yet!)
I don't know what to do. I don't even know if I should unplug the phone and redo the rebootRUU thing…
:crying: PLEASE HELP!!!!
Click to expand...
Click to collapse
Ok...
First flash a recovery(use Case 2):
No Recovery? No Problem​​
Oh sh*t here we can have several kind of problems Still no problem But let's first download the recovery.
http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.6.3.3-m7.img
(MD5 hash: 72067AEFB69541D40E8420D7AA46408D)
Case 1 - Normal error with unlocked and s off or s on:
Boot your phone into the fastboot mode
Eat a piece of cheese
Enter this command
Code:
fastboot erase cache
Followed by this command
Code:
fastboot flash recovery "C:\path_to_recovery\recovery_name.img"
And enter the recovery and follow the next piece of guide
Case 2 - For some stupid reason you are s off (that's a MUST) and Relocked:
Sorry, you need this recovery:
https://www.mediafire.com/?ni177radvko5xu7 (If it doesn't work, PM me)
(MD5 hash: F2893CDC17C788B2E49AECEA8C02DCB4)
Boot your awesome HTC One into fastboot
Change CID to superCID using this command (make sure you used 8 times a '1')
Code:
fastboot oem writecid 11111111
Enter this command
Code:
fastboot oem rebootRUU
Wait until your Pc recognized your phone again and enter this command
Code:
fastboot flash zip "C:\path_to_zip\firmware.zip"
(This may delete all your data)
Happy rebooting with this command
Code:
fastboot reboot-bootloader
Enter the recovery and let's unlock the bootloader...
You can unlock your bootloader using these commands(thanks @scotty1223 for your thread!):
[how to] lock/unlock your bootloader without htcdev(s-off required)
If this doesn't work in recovery because you get superSU or permission errors, use this tool here instead:
http://www.htc1guru.com/guides/guru-bootloader-reset/
You can simply push the ZIP file to your HTC One using one of these commands:
Code:
adb push "C:\path_to_zip\zip_name.zip" /sdcard/bootloader_reset.zip
If this one results in supersu and permission errors, try these paths(Thanks @Sneakyghost for this advice!)
Code:
adb push "C:\path_to_zip\zip_name.zip" /storage/emulated/0/bootloader_reset.zip
Code:
adb push "C:\path_to_zip\zip_name.zip" /data/media/0/bootloader_reset.zip
Case 3 - You totally ****ed up your recovery and data partition:
Right now, I am pretty busy and I don't have time to develop this, check this guide there and post your question there, but pls don't spam @mike1986.
How to: fix a corrupted DATA partition on the HTC One
​
now you are unlocked and s off... so what we're gonna do depends on what you want to achieve... I didn't really get what you meant in the first post.. you want to be again 100% stock on a Asian ROM ?
with the unlocked bootloader and s off and the custom recovery you are pretty much able to flash the rom you want to the device... how to do this:
http://forum.xda-developers.com/showthread.php?t=2632736
or:
Bootloop, No OS, Totally f*cked up OS? No Problem​​
THIS WILL DELETA ALL YOUR APPS AND APP DATA BUT NOT SDCARD!​
First of all, make a factory reset in TWRP... then follow the next steps.
Now the key step here copying the rom.zip to your sdcard. You do this this way
Since you are in the recovery you should be able, no.. actually will be able to use adb commands
To copy the rom zip us this command:
Code:
adb push "C:\path_to_rom\rom_name.zip" /sdcard/rom.zip
If this one results in supersu and permission errors, try these paths(Thanks @Sneakyghost for this advice!)
Code:
adb push "C:\path_to_rom\rom_name.zip" /storage/emulated/0/rom.zip
Code:
adb push "C:\path_to_rom\rom_name.zip" /data/media/0/rom.zip
Now, in the recovery, choose install and select the rom you should've just copied and install/flash it.
After that make a factory reset, the standart when chosing wipe in TWRP.
Happy rebooting!
​
---------- Post added at 11:43 AM ---------- Previous post was at 11:39 AM ----------
jaqzilch said:
I've unplugged the phone, rebooted into bootloader, and made a second attempt to rebootRUU with HKvariant 1.29 zip… still gets stuck after 1st rebootRUU command (i.e. black screen with grey HTC logo)
Please do help,
Click to expand...
Click to collapse
ok, ok ok... wait with flashing RUUs... you'll mess up your phone if you continue flashing these RUUs

LibertyMarine said:
Ok...
First flash a recovery(use Case 2):
...
[/INDENT][/INDENT]
---------- Post added at 11:43 AM ---------- Previous post was at 11:39 AM ----------
ok, ok ok... wait with flashing RUUs... you'll mess up your phone if you continue flashing these RUUs
Click to expand...
Click to collapse
Hello, LibertyMarine, thanks for the response!
I've already downloaded TWRP recovery from the TWRP website, is the one you give me different?
Re: Case one-- I've actually tried flashing the TWRP recovery image before, but it doesn't seem to work. Thing is, I've idiotically relocked my HTC one now, so that might be the problem.
This is what I get when I try to flash TWRP recovery:-
fastboot flash recovery TWRPrecovery.img
target reported max download size of 1526722560 bytes
sending 'recovery' (9948 KB)...
OKAY [ 11.854s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 12.707s
as for unlocking my relocked bootloader, I've tried numerous times and I simply cannot get my relocked bootloader to unlock again. Whenever I put in the "fastboot flash unlocktoken Unlock_code.bin" (and yes, I've put the Unlock_code.bin into the same folder as fastboot and adb, the terminal gets stuck at "sending 'unlocktoken' (0 KB)…"
and nothing happens on my phone.
Re: Case two-- I'm one of those poor S-on folks so…
Re: Case 3-- looks like they need custom recovery flashed already… but (see Case one above), I can't seem to flash TWRP on my poor phone … : (
As to the last solution-- totally f-ed up OS etc…. again, I don't have TWRP… nor can I used adb
I'd be ever so grateful if I can just find a way to put twrp on my phone again! o gawd….
THanks again for all suggestions!!

jaqzilch said:
Hello, LibertyMarine, thanks for the response!
I've already downloaded TWRP recovery from the TWRP website, is the one you give me different?
Re: Case one-- I've actually tried flashing the TWRP recovery image before, but it doesn't seem to work. Thing is, I've idiotically relocked my HTC one now, so that might be the problem.
This is what I get when I try to flash TWRP recovery:-
fastboot flash recovery TWRPrecovery.img
target reported max download size of 1526722560 bytes
sending 'recovery' (9948 KB)...
OKAY [ 11.854s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 12.707s
Click to expand...
Click to collapse
yeah.. that's because you are locked ....
jaqzilch said:
as for unlocking my relocked bootloader, I've tried numerous times and I simply cannot get my relocked bootloader to unlock again. Whenever I put in the "fastboot flash unlocktoken Unlock_code.bin" (and yes, I've put the Unlock_code.bin into the same folder as fastboot and adb, the terminal gets stuck at "sending 'unlocktoken' (0 KB)…"
Click to expand...
Click to collapse
hmmm... have you tried redownloading/rerequesting a unlock token ?
try that... try requesting a new one and try flashing this one...
jaqzilch said:
and nothing happens on my phone.
Click to expand...
Click to collapse
haven't had such an issue.. I'll do some research on this topic..
jaqzilch said:
Re: Case two-- I'm one of those poor S-on folks so…
Click to expand...
Click to collapse
I don't know why.. I though you were s off... sorry... I must have commuted you with an other guy
jaqzilch said:
Re: Case 3-- looks like they need custom recovery flashed already… but (see Case one above), I can't seem to flash TWRP on my poor phone … : (
As to the last solution-- totally f-ed up OS etc…. again, I don't have TWRP… nor can I used adb
I'd be ever so grateful if I can just find a way to put twrp on my phone again! o gawd….
THanks again for all suggestions!!
Click to expand...
Click to collapse
Yeah... case 3 needs a custom recovery.. but you won't need that one anyways.. because your data partition seems to be OK

[Q] N6 is just DEAD,,, NOT OPERATING AT ALL(HELP!)

Hello, everyone.
So, about an week ago, I posted a thread to ask for your help regarding my broken N6. Since then, nothing has changed(but got worse, I guess...?). Here is what is happening with my N6 right now.
1) It powers up(thank god) but goes straight to the boot-loader screen(I believe this means that my device doesn't have system image file within the device)
2) On boot-loader menu(Start, Restart bootloader, Recovery mode, Power off, Factory, Barcodes, BP Tools, QCOM, Bootlaoder logs), only few are working(Restart bootlodaer, Power off, Barcodes). When I try to perform other than these, it just goes back to main boot-loader screen.
3) I tried to use both Nexus Root Tool kit and manual installation of each image but doesn't work for both of them(From this, I believe that my phone is just BROKEN)
With this happening, conclusion that I can think of is
1) There is no 'Recovery' available in my device(that's why I can't do anything to recover my device)
2) ADB is not functioning.
Only solution that I can think of from this point is that contact Motorola and replace my device(which is what I am currently doing but Motorola has huge problem with their customer service that I am waiting for their answer for about 2 weeks now)
If possible, would there other options that I can repair this device by myself?
I appreciate your attention.
Sincerely.

Adb has no impact on bootloader. What do you mean doesn't work when you fastboot the factory image?
Sent from my Nexus 6 using XDA Free mobile app

your problem is the use of toolkits. stay away from them, unless you know what you are doing!
your phone doesnt have any rom on it. you can.. 1. flash the factory img via fastboot, like you are supposed to do(not via a toolkit), or 2. unlock the bootloader, flash a custom recovery then while in the custom recovery adb push a rom, gapps, and supersu and flash them that way. what you did does not give you the right for a trade in.

The two previous posters are correct. You just need to fastboot flash the factory rom and factory recovery. It is fairly simple, if you take the time to read how to do it. There are posts all over XDA for beginners on how to do this. And I cannot stress how correct @simms22 is. Toolkits may seem to make things easy, but when there is a problem, you need to know how to manually fix it. I just personally stay away from toolkits. And I was in your shoes. I didn't know jack about flashing roms and such. Just reading XDA got me to where I am. (and i am still learning!)

Like the others have pointed out, you are fine. You have access to your bootloader screen, this is a Nexus. Take a deep breath. Take some time and read this site about flashing a factory image. Please do it the best way - manually with fastboot commands. If you get stuck come back here and someone will help. It really is easy. Please repeat after me "I will avoid all toolkits from now one".
Start with this and read lots.
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008

Flashing the factory image should still work from boot loader with fast boot.
Follow the second link for manual flashing after downloading the zip from the first link.
https://developers.google.com/android/nexus/images
If you run into the missing system.img problem here is the link to fix it:
http://www.androidpolice.com/2014/11/12/running-into-the-dreaded-missing-system-img-error-flashing-android-5-0-factory-images-heres-how-to-get-around-it/
This way you can start from the beginning.

Problem with flashing factory image manually.
First, thanks everyone for helping me by providing useful information but there is a problem when I flash factory image manually.
Whenever I try to flash image(for example, 'boot.img', or other images, I always get the same error 'FAILED <remote failure>' and not installed on my device. From here, I have no idea what to do.

chg911225 said:
First, thanks everyone for helping me by providing useful information but there is a problem when I flash factory image manually.
Whenever I try to flash image(for example, 'boot.img', or other images, I always get the same error 'FAILED <remote failure>' and not installed on my device. From here, I have no idea what to do.
Click to expand...
Click to collapse
first off, does fastboot see your device?? you can check by typing.. fastboot devices
if it doesnt see your device, do you have the driver instslled?

simms22 said:
first off, does fastboot see your device?? you can check by typing.. fastboot devices
if it doesnt see your device, do you have the driver instslled?
Click to expand...
Click to collapse
fastboot detects my device. but when I tried to TWRP recovery, it shows following error.
sending 'recovery' <11668 KB>...
OKAY [ 0.375s]
writing 'recovery'...
<bootloader> Failed to erase partition
<bootloader> Failed to flash partition recovery
FAILED <remote failure>
finished. total. time: 6.133s

chg911225 said:
fastboot detects my device. but when I tried to TWRP recovery, it shows following error.
sending 'recovery' <11668 KB>...
OKAY [ 0.375s]
writing 'recovery'...
<bootloader> Failed to erase partition
<bootloader> Failed to flash partition recovery
FAILED <remote failure>
finished. total. time: 6.133s
Click to expand...
Click to collapse
look for the command to erase the recovery partition. youll have to google it as i dont know(or remember) it. i dont even own a computer :angel:
then youll have to reflash the recovery.

simms22 said:
look for the command to erase the recovery partition. youll have to google it as i dont know(or remember) it. i dont even own a computer :angel:
then youll have to reflash the recovery.
Click to expand...
Click to collapse
found the command "fastboot erase recovery" but not working with following error message.
fastboot erase recovery
erasing 'recovery'
<bootloader> Erase allowed in unlocked state
<bootloader> Failed to erase partition
FAILED <remote failure>
finished. total time: 5.763s
*my phone is unlocked for sure(I checked 'fastboot oem unlock' and it said
fastboot oem unlock
...
<bootloader> Device already unlocked!
FAILED<remote failure>
finished. total time: 0.003s

​
chg911225 said:
found the command "fastboot erase recovery" but not working with following error message.
fastboot erase recovery
erasing 'recovery'
<bootloader> Erase allowed in unlocked state
<bootloader> Failed to erase partition
FAILED <remote failure>
finished. total time: 5.763s
*my phone is unlocked for sure(I checked 'fastboot oem unlock' and it said
fastboot oem unlock
...
<bootloader> Device already unlocked!
FAILED<remote failure>
finished. total time: 0.003s
Click to expand...
Click to collapse
i have no idea, but this is a good thread to read and post questions about fastboot in http://forum.xda-developers.com/nexus-6/general/noob-read-adb-fastboot-how-help-t3006500

RIP. What did you do to your N6?

OP how did you install your fastboot. I would assume you did it from within a toolkit. That is probably your problem. If that is the case, please do this. Go here and install the .exe: http://developer.android.com/sdk/index.html#Other
It's big I know it but just do it please.
Make sure everything (SDK) gets installed in a folder path like c:\android or something you will easily remember. This is very important because it is within this folder you will place the extracted factory image files (.img). Place all full unzipped .img files in this folder.
Please follow method #2 in this excellent guide:
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008

zetsumeikuro said:
RIP. What did you do to your N6?
Click to expand...
Click to collapse
One day it just shut down by itself and since then it's like this. I just contact Motorola and they are going to ship me new device with different color(idk y they are still having problem with their stocking their devices in because what I had was Cloud White 32Gb but only model that were present when I contact them was Midnight blue with 32Gb, other options are all out of stock. really wished they had a white color...)

This phone is a damn Nexus, it can't die. It's user error.
Sent from my Nexus 6