[Q] Gray screen - dead/killed One - One (M7) Q&A, Help & Troubleshooting

Hi,
I've tried to change mid number according http://forum.xda-developers.com/showthread.php?t=2322820 but I guess I did sth wrong and now my One wont start, its just gray-dotted screen and freeze.
Enyone please help

ziolooo said:
Hi,
I've tried to change mid number according http://forum.xda-developers.com/showthread.php?t=2322820 but I guess I did sth wrong and now my One wont start, its just gray-dotted screen and freeze.
Enyone please help
Click to expand...
Click to collapse
From the guide you linked, gray screen is normal:
Step 6:
When you start your command prompt follow the steps in the picture below. PLEASE BE PATIENT!! After flashing the ENG HBOOT your HTC One will not boot up but you'll just get a gray spotted screen. Your device is not bricked. You can still use adb commands to write the model ID and CID even with a gray screen. WHEN REBOOTING HOLD DOWN POWER BUTTON FOR A FEW SECONDS. You might have to press and hold power button and volume down button when rebooting your phone

dgtiii said:
From the guide you linked, gray screen is normal:
Step 6:
When you start your command prompt follow the steps in the picture below. PLEASE BE PATIENT!! After flashing the ENG HBOOT your HTC One will not boot up but you'll just get a gray spotted screen. Your device is not bricked. You can still use adb commands to write the model ID and CID even with a gray screen. WHEN REBOOTING HOLD DOWN POWER BUTTON FOR A FEW SECONDS. You might have to press and hold power button and volume down button when rebooting your phone
Click to expand...
Click to collapse
But I tried "HOLD DOWN POWER BUTTON FOR A FEW SECONDS" and nothing happend - just gray screen.
I flashed zip and progress bar stopped at ~80% (on rebootRUU) so I reset it and saw gray screen - I tried do this few times and phone just restarted dand stopped at gray screen.
Mayba I should wait longer ?

Yea the eng hboot took a while to even show up on my phone. It says the adb commands will still work, did you change the numbers already? It won't boot up right if you don't flash an hboot intended for our phones after you're done
Sent from my HTC One using Tapatalk 4 Beta

Have you read the thread in the link you posted? It says it gets stuck at 80%, reboot and your phone will have a grey screen, proceed to next step, which is writing the MID.
You've stated that you did the first two but now it's at a grey screen ... Do the next step like it tells you. I don't get why you keep rebooting it and questioning the grey screen when it tells you that is normal and tells you what to do next?

AllAboutTheCore said:
Have you read the thread in the link you posted? It says it gets stuck at 80%, reboot and your phone will have a grey screen, proceed to next step, which is writing the MID.
You've stated that you did the first two but now it's at a grey screen ... Do the next step like it tells you. I don't get why you keep rebooting it and questioning the grey screen when it tells you that is normal and tells you what to do next?
Click to expand...
Click to collapse
OK I did as You said and I changed mid cid etc
But now still I cannot witch on phone, it's still just grey screen. I can type fastboot commands, I tried fastboot reboot(-bootoloader) and it just turn dark and thats all ;/
-- And I did next 3 times and now its OK.
Thanks for help

I'm also able to type in fastboot command but now adb, what can I do??? Did I just brick the most amazing phone???

I'm stuck on the same gray screen and I can't do anything. It's not accepting fastboot commands and says waiting for device and RUU is not recognizing the device

AllAboutTheCore said:
Have you read the thread in the link you posted? It says it gets stuck at 80%, reboot and your phone will have a grey screen, proceed to next step, which is writing the MID.
You've stated that you did the first two but now it's at a grey screen ... Do the next step like it tells you. I don't get why you keep rebooting it and questioning the grey screen when it tells you that is normal and tells you what to do next?
Click to expand...
Click to collapse
Hey! I have the same issue. I cannot even user adb or fastboot.
when hit the commands, it says 'Waiting for device'
I cannot even switch off the phone it is reboot continuously. Plz help

m.babudas said:
Hey! I have the same issue. I cannot even user adb or fastboot.
when hit the commands, it says 'Waiting for device'
I cannot even switch off the phone it is reboot continuously. Plz help
Click to expand...
Click to collapse
I don't get why ppl are still using this method to change the MID despite all the warnings posted in the old thread where you can find the instructions how to flash the eng hboot. There are now really faster, easier and safer methods to change the MID.
So I guess you have flashed the eng hboot using a windows 8 or 10 computer right and now you don't have fastboot connectivity anymore? The eng hboot is version 1.43 and windows 8 and 10 are only supported since version 1.54. If this is the case, you'll have to find a Windows 7 computer to finish the process. Note that you'll need to use a 1.xx.xxx.x RUU.exe. Using newer RUU with this method will not work.

Related

Stuck at Bootlogo

Hello all,
I have a friends sprint hero cdma that was rooted with z4root. He was flashing a mod that changed the text from green to orange and the phone froze. He waited quite a while then decided to hard reset. When he put the battery back in and rebooted the phone and the phone would not boot past white HTC bootlogo. The phone will not boot into recovery and the PC will recognize the phone, but the system will not mount so the ruu will not detect the phone either. HTC sync does not detect the phone being connected either. I am using a program called USBDeview and it shows the driver is there and says it is connected but none of the programs detect its connection. Any ideas?
Thanks in advance. Again this is not my phone and I am not familiar with rooting procedures with this phone, but I see a great learning experience in front of me and love these challenges.
this should be in QnA.
Hold power + vol down. will get you into HBOOT. if you flashed the eng-spl that unlocks fastboot you can erase and flash new. Tutorials are somewhere in this forum.
Sorry for the wrong forum. The phone will not hboot or boot into recovery
If it gets that far, you should be able to run the RUU. It'll restore everything to stock ;-)
Sent from my Epic using XDA App
The phone does not connect all the way for some reason. The RUU does not see device and neither does ADB. In device manger, when the device is connected it is assigned a drive letter and I can right click and go to properties and details and the description says android phone. I am out of ideas. Even when the device is connected and assigned a drive letter I can open file explorer and click on the device and the directory is blank. The SD card does not even show up, but if I take sd and put it in an adapter the sd card is still in tact with everything on it.
Sounds like a driver went haywire try searching the dev section for my thread on how to install adb. I know you have it already but try the diffrent drivers. I would post a link but I'm mobile. Hope it helps
Something.About.Me.U.Dont.Like
Its.Cool.I.Understand.
.AWAH.
Power off
hold vol up and power on
should be in fast boot mode
plug in your USB cable
should now be in fast boot usb mode
run RUU from the computer
RUU should recognise the phone and start installing
I will try this when I get home. So what would cause the phone to act like this? I have read quite a few threads in my quest to fix this phone and a ton of ppl claim bout the only way to brick the hero is by flashing a GSM vs of a. Zip instead of the cdma version. Is this true? I ask because the phone almost acts like it has been locked out somehow.
What happens when you boot into fastboot mode? I held the buttons but the hero still hangs at the white HTC screen.
nordy420 said:
I will try this when I get home. So what would cause the phone to act like this? I have read quite a few threads in my quest to fix this phone and a ton of ppl claim bout the only way to brick the hero is by flashing a GSM vs of a. Zip instead of the cdma version. Is this true? I ask because the phone almost acts like it has been locked out somehow.
Click to expand...
Click to collapse
Yes this is basically true. But if you get the HTC screen, chances are that it is not bricked. I have to ask, did you flash anything like a radio for GSM? If not, then you might need to just let it sit there for an exstended period of time and see if it boots. When I do certain things to my phone, it might take up to 15 minutes to get by the HTC logo screen.
nordy420 said:
What happens when you boot into fastboot mode? I held the buttons but the hero still hangs at the white HTC screen.
Click to expand...
Click to collapse
I wish I could take a screen shot and show you but the phone is not recognised at that point except by the RUU when it is waiting for bootloader. Bootloader is another name for fastboot.
It would be a white screen with green letters and it will say fastboot near the top under the green letters. At the bottom of the screen there will be 3 android characters on skate boards.
This is what you should see. Try again
Important: Make sure the USB is not conected at this time
Power off
Hold volume up, then press the red key (power on)
Fastboot screen comes up
At this point plug in the USB. It will change from Fastboot to Fastboot USB
Run RUU .5 or .6 from the computer
It will get to a point where the install says waiting for bootloader
from there it should start installing
If you can't get to the bootloader screen (fastboot) then I am not sure how to help you
Let me know if it works for you.
Edit: If you are not using ENG SPL or have S-Off read this post. You will need a working knowledge of how to use ADB.
http://forum.xda-developers.com/showthread.php?t=958968
Usually you are still able to get into fastboot, especially if you see the htc screen. Unless you (not really you) destroy the recovery and/or the misc partitions.Did you do this exactly (some people don't do it exactly) pull the battery, reinsert the battery, holding volume up and while holding volume up press the power (end call) button.
If you did then while the phone is stuck on the HTC screen do ......
Open up a command window. Either cd into your windows-sdk/tools folder or just type in the commands if you have the tools folder set as a global environment.
Code:
adb devices
Does it show you a device is connected? If it does you should be able to flash a new recovery image or at least a system.img to get it back up and running.
Thank you for the help by the way. I am not the owner of the phone, I am just more patient than the owner and have nothing to lose if it is screwed lol. http://androidforums.com/sprint-hero-all-things-root/259735-bricked.html. Here is his desperate cry for help after it happened. I own a Droid x and have no idea what he was actually trying to do, but maybe after you read what he did then maybe we can come up with a fix. I agree with you supporters that the phone is not bricked but it is sure being stubborn. Please let me know what ya think. Thanks.
unCoRrUpTeD said:
Usually you are still able to get into fastboot, especially if you see the htc screen. Unless you (not really you) destroy the recovery and/or the misc partitions.Did you do this exactly (some people don't do it exactly) pull the battery, reinsert the battery, holding volume up and while holding volume up press the power (end call) button.
If you did then while the phone is stuck on the HTC screen do ......
Open up a command window. Either cd into your windows-sdk/tools folder or just type in the commands if you have the tools folder set as a global environment.
Code:
adb devices
Does it show you a device is connected? If it does you should be able to flash a new recovery image or at least a system.img to get it back up and running.
Click to expand...
Click to collapse
I will try this when I get home. I did do a battery pull but I did not leave it out very long, but the screen never changed for me, just stayed white with HTC logo in the middle.
Be very sure to disconnect the USB. That was the step I was missing and I could not get it to boot to recovery when it was stuck at the logo. Once the USB was disconnected, took the battery out, put it back in, and held down the home button while pushing the power. That worked! Woot!
Lynne
No luck. The phone will not boot into anything to where a PC will recognize it.
nordy420 said:
No luck. The phone will not boot into anything to where a PC will recognize it.
Click to expand...
Click to collapse
Have you downloaded android commander and gave that a shot? androidcommander.com
android commander recognises the phone when it is at the logo screen. it will see all but the sdcard.
within android commander menu, there is a reboot to bootloader command
Ill try it, and report back
So I messed with android commander a little and could not get it to detect the device. I really think that it is a driver issue. I cannot get the HTC driver to install for the phone. A different driver has been installed for the device and windows will not let me manually install one. I can use the install legacy and the HTC driver is there but it will not correlate with the phone when connected.

[Q] Help! - Bricked Incredible S, S-ON, unable to boot past HTC logo

Hi guys,
what I have:
Optus (AU) HTC Incredible S - it was running 2.3.3 fine, no hacks/root or anything has been done to it. [I've done a vol down + power button hboot thingy and it says S-ON]
what happened:
I connected the phone to a WIFI network to update my apps, it started updating many apps. mid-way through the updates, the phone became unresponsive and apparently hung, left it alone for a few hours, it remained hung.
I disconnected the power and pulled the battery.
The phone has since refused to boot past the HTC splash logo.
What I've tried:
I've tried rooting the phone with Revolutionary - however I can't complete the steps as I am unable to boot the phone.
I've tried Hboot with the [PG32IMG.zip] file - nothing seemed to change
I've tried usb fastboot with adb and fastboot - Signature verification failed [well, it is S-ON]
I've tried recovery - failed, gave me 3 arrows, 2 in a circular pattern and one straight, followed by a phone icon and a red triangle and ! mark
I've tried running the RUU.exe file for 2.3.3 optus, but it does not get past 'rebooting to bootloader'
Current situation:
I've spent around 6 hours trying to figure out what went wrong and make it work ... but nothing seems to work ... so guys ... i really could use some help ...
btw, I can't warranty it as I purchased the phone in Australia, but now am in Singapore ... I'll be returning to Australia in January though ...
All help and suggestions will be greatly appreciated ...
Thanks!
expiredyoghurt said:
Hi guys,
what I have:
Optus (AU) HTC Incredible S - it was running 2.3.3 fine, no hacks/root or anything has been done to it. [I've done a vol down + power button hboot thingy and it says S-ON]
what happened:
I connected the phone to a WIFI network to update my apps, it started updating many apps. mid-way through the updates, the phone became unresponsive and apparently hung, left it alone for a few hours, it remained hung.
I disconnected the power and pulled the battery.
The phone has since refused to boot past the HTC splash logo.
What I've tried:
I've tried rooting the phone with Revolutionary - however I can't complete the steps as I am unable to boot the phone.
I've tried Hboot with the [PG32IMG.zip] file - nothing seemed to change
I've tried usb fastboot with adb and fastboot - Signature verification failed [well, it is S-ON]
I've tried recovery - failed, gave me 3 arrows, 2 in a circular pattern and one straight, followed by a phone icon and a red triangle and ! mark
I've tried running the RUU.exe file for 2.3.3 optus, but it does not get past 'rebooting to bootloader'
Current situation:
I've spent around 6 hours trying to figure out what went wrong and make it work ... but nothing seems to work ... so guys ... i really could use some help ...
btw, I can't warranty it as I purchased the phone in Australia, but now am in Singapore ... I'll be returning to Australia in January though ...
All help and suggestions will be greatly appreciated ...
Thanks!
Click to expand...
Click to collapse
You better wait till january and claim the warranty!
hey buddy
well , the easy way to solve your problem is to download the stock rom for your device , and install it using the offical HTC exe ( the rom exe ) .
it will do it all and get your device like brand new .
hope this solve it .
If the above doesn't work send it to any htc repair center. You have to pay but whatever.
hassanhm said:
hey buddy
well , the easy way to solve your problem is to download the stock rom for your device , and install it using the offical HTC exe ( the rom exe ) .
it will do it all and get your device like brand new .
hope this solve it .
Click to expand...
Click to collapse
Hey hassanhm,
thanks for the reply. I've tried searching the HTC official website for the stock rom, however it is not available for download due to the fact that firmware upgrades are now over the air ..
i've downloaded the RUU rom by optus (RUU_Vivo_Gingerbread_S_Optus_AU_2.12.980.2_R_Radio _20.2803.30.085AU_3805.04.03.12_M_release_185028_s igned
http://www.filefactory.com/file/cfdd...028_signed.exe) found here - http://forum.xda-developers.com/showthread.php?t=1033922 - however it just gets stuck on the booting to bootloader step ...
if there a different stock rom exe file i should be using?
Thanks!
I'm a singaporean. Its uncommon to see this kinda stuff :/
looks like dead motherboard i saw thing like that already
I'm from Singapore. I had this issue, spent a day flashing and rebooting to try and fix it. Then I have up and just flashed an official ROM, I think any one will do, then sent it to HTC. It was still s-off but they didn't care. Took just 3 days and they sent it back, fixed and like brand new. I suggest you don't waste time and just sent to HTC. it will come back s-on but you can just root it again.
Hope this helps!
Sent from my HTC Incredible S using XDA App
There's one but when they put latest Hboot (1.16.0000)then it's harder to flash ROM than 1.13.0000. Hope you get your phone back and it's working
expiredyoghurt said:
Hi guys,
what I have:
Optus (AU) HTC Incredible S - it was running 2.3.3 fine, no hacks/root or anything has been done to it. [I've done a vol down + power button hboot thingy and it says S-ON]
what happened:
I connected the phone to a WIFI network to update my apps, it started updating many apps. mid-way through the updates, the phone became unresponsive and apparently hung, left it alone for a few hours, it remained hung.
I disconnected the power and pulled the battery.
The phone has since refused to boot past the HTC splash logo.
What I've tried:
I've tried rooting the phone with Revolutionary - however I can't complete the steps as I am unable to boot the phone.
I've tried Hboot with the [PG32IMG.zip] file - nothing seemed to change
I've tried usb fastboot with adb and fastboot - Signature verification failed [well, it is S-ON]
I've tried recovery - failed, gave me 3 arrows, 2 in a circular pattern and one straight, followed by a phone icon and a red triangle and ! mark
I've tried running the RUU.exe file for 2.3.3 optus, but it does not get past 'rebooting to bootloader'
Current situation:
I've spent around 6 hours trying to figure out what went wrong and make it work ... but nothing seems to work ... so guys ... i really could use some help ...
btw, I can't warranty it as I purchased the phone in Australia, but now am in Singapore ... I'll be returning to Australia in January though ...
All help and suggestions will be greatly appreciated ...
Thanks!
Click to expand...
Click to collapse
If you claim warranty : YOU LOSS A CHANCE TO HAVE BIG FUN I'm exactly on your situation (may be worse), but probably we feel different. I can only boot into fastboot and hboot ... LOL
expiredyoghurt said:
Hi guys,
what I have:
Optus (AU) HTC Incredible S - it was running 2.3.3 fine, no hacks/root or anything has been done to it. [I've done a vol down + power button hboot thingy and it says S-ON]
what happened:
I connected the phone to a WIFI network to update my apps, it started updating many apps. mid-way through the updates, the phone became unresponsive and apparently hung, left it alone for a few hours, it remained hung.
I disconnected the power and pulled the battery.
The phone has since refused to boot past the HTC splash logo.
Click to expand...
Click to collapse
You must be able to revive, since you did not do anything related to s-off, rooting etc. rooting, s-offing are for modding addict fellow
[/QUOTE]
What I've tried:
I've tried rooting the phone with Revolutionary - however I can't complete the steps as I am unable to boot the phone.
[/QUOTE]
Revolutionary only work on phone with NORMAL BOOTING (Android booting). If you did on fastboot then (I Think) you start create big trouble
I've tried Hboot with the [PG32IMG.zip] file - nothing seemed to change
Click to expand...
Click to collapse
This will only work for UPDATE, mean you must use higher version of ROM than in the phone (if you are s-on) -CMIIW-
I've tried usb fastboot with adb and fastboot - Signature verification failed [well, it is S-ON]
I've tried recovery - failed, gave me 3 arrows, 2 in a circular pattern and one straight, followed by a phone icon and a red triangle and ! mark
I've tried running the RUU.exe file for 2.3.3 optus, but it does not get past 'rebooting to bootloader'
Current situation:
I've spent around 6 hours trying to figure out what went wrong and make it work ... but nothing seems to work ... so guys ... i really could use some help ...
Click to expand...
Click to collapse
can you post your mainver : FYI, I could NOT resolve my vivo since my situation is worse than you, but probably my experience with unsuccesfull result will give different output ... who knows.
on fastboot (I'm sure You know how to do) fastboot getvar all (windows command) and post the output for our analysing together and help each other.
btw, I can't warranty it as I purchased the phone in Australia, but now am in Singapore ... I'll be returning to Australia in January though ...
All help and suggestions will be greatly appreciated ...
Thanks!
Click to expand...
Click to collapse
You will loss a big FUN on your life !!! by choosing easy way.
i have the same problem with a unit of incredible s. will not continue booting up past the htc logo.
Is this a software problem? cause im thinking maybe its the motherboard.
ice_pick88 said:
i have the same problem with a unit of incredible s. will not continue booting up past the htc logo.
Is this a software problem? cause im thinking maybe its the motherboard
Click to expand...
Click to collapse
.
what did you do before stuck. Can you boot into bootloader (?) are you S-ON or S-OFF (?) what is Hboot version do you have. To have bootloader state : press power and volume down button SIMULTANEOUSLY if within TEN MINUTES you do not have bootloader status you should stop and let us know here
Thanks for the reply. Its S-On, Hboot 1.13, I was simply browsing using the phone when it restarted and stuck with the htc logo.
ice_pick88 said:
Thanks for the reply. Its S-On, Hboot 1.13, I was simply browsing using the phone when it restarted and stuck with the htc logo.
Click to expand...
Click to collapse
I'm wondering. You probably did not enable fastboot option > setting > power > UNTHICK fastboot item.
On your today phone state you can not do it. Do you remember ? you enable fastboot option or not. Presumed you enable fastboot option then you can go to bootloader by pressing power and volume down buttons simultaneously > once you come into bootloader there is an option FACTORY RESET. If you see RED TRIANGLE. No other choice (AFAIK) you need to download the RUU of your phone and just run RUU ... all your personal user data will be wiped.
x1123 said:
I'm wondering. You probably did not enable fastboot option > setting > power > UNTHICK fastboot item.
On your today phone state you can not do it. Do you remember ? you enable fastboot option or not. Presumed you enable fastboot option then you can go to bootloader by pressing power and volume down buttons simultaneously > once you come into bootloader there is an option FACTORY RESET. If you see RED TRIANGLE. No other choice (AFAIK) you need to download the RUU of your phone and just run RUU ... all your personal user data will be wiped.
Click to expand...
Click to collapse
Thanks again for the reply. when i choose the factory reset the phone hangs but when i select recovery it goes to the red triangle logo. Where and how can i know whats RUU of my phone? Sorry im literally a noob.
3 days ago, i was having the same problen but i could solve it
Here what you can do:
1. Eject your sd card and insert another android phone. You can create a gold card over another android phone (Making gold card is completely independent from android version or phone model. Trust me.). You can search the forum, there are a lot of guides for making a gold card.
2. Boot into fastboot, plug your usb cable. Open a windows console, and send that command:
Fastboot getvar mainver
It will tell you your mainver.
3. Go here: http://forum.xda-developers.co m/showthread.php?t=1359555 .
In there, you can find original rom list. Choose one which has higher mainver than yours then download it. The thread also explains how to install the original rom.
Hth.
-R
programci_84 said:
3 days ago, i was having the same problen but i could solve it
Here what you can do:
1. Eject your sd card and insert another android phone. You can create a gold card over another android phone (Making gold card is completely independent from android version or phone model. Trust me.). You can search the forum, there are a lot of guides for making a gold card.
2. Boot into fastboot, plug your usb cable. Open a windows console, and send that command:
Fastboot getvar mainver
It will tell you your mainver.
3. Go here: http://forum.xda-developers.co m/showthread.php?t=1359555 .
In there, you can find original rom list. Choose one which has higher mainver than yours then download it. The thread also explains how to install the original rom.
Hth.
-R
Click to expand...
Click to collapse
Just for additional info. If you can not find another android/windows phone to get sdcard CID (you have only one phone and now in trouble). You can use any laptop with Built In card reader at PCI slot and NOT USB STORAGE if you were not have BOTH ... it's time to ask help your neighbour or your friends
Unlock bootloader through htcdev.com (phone doesn't have to boot normally to do this and it remains S-ON)
Flash clockwork recovery
Do arhd wipe
Flash any rom you want
flash the boot.img of that rom
there done
fallenwout said:
Unlock bootloader through htcdev.com (phone doesn't have to boot normally to do this and it remains S-ON)
Flash clockwork recovery
Do arhd wipe
Flash any rom you want
flash the boot.img of that rom
there done
Click to expand...
Click to collapse
Good day,
Thanks for the replies. Im having problem with this step. Im doing the unlocking the bootloader of the phone but when im in the process of inputting the cmd command "fastboot oem get_identifier_token" it gets me the " <waiting for device>
I have installed the latest htc sync version and updated all the drivers but it looks like my pc doesnt detect the incredible s.
Need suggestion guys.
Ill try the Gold card step later maybe it will work.
Thanks again.

Did I just brick my Hero? Help!

Some basic info about my phone-
HBOOT 1.47.0000
Radio 2.42.01.04.23
Carrier- iWireless (Kroger, Sprint subsidary)
S-ON
Alright, so I was just using my phone as normal. Running CM7.2 and ClockWorkMod Recovery. I turned off my phone, everything was fine. When I went to turn it on again, it showed the green HTC logo, as per normal, then it suddenly rebooted. There, it showed the green HTC logo again, and it'll just stay there. So I tried to boot into recovery (pulled the battery, put it back in, held the red end call button + volume down, got into hboot, then pressed home to go to recovery).
The thing is- it did the same thing. Reboot before it gets to recovery, and then stuck at the HTC Logo. I tried using the Sprint RUU, didn't work- it told me to download the right RUU for this phone, and gives me an error 131. I used the flashable RUU found in this thread (found here), in conjunction with this tutorial (found here). It gave me an error that looked like this when I ran "fastboot flash zip *flashable RUU zip path*"
Code:
FAILED (remote: 42 custom id check fail)
I believe it has something to do with the fact that it is NOT a Sprint branded phone. It doesn't even have a Google logo on the back.
Since it's not S-OFF, I can't flash a recovery via fastboot. I'm stuck. Help?
*TO CLARIFY*
I can't get into Recovery, or the actual system. I also can't access adb. The only part I can access is the bootloader and fastboot.
How much battery did you have left before you turned your phone off ?? Also what was the reason you turned your phone off ??? Also you linked to the use fastboot thread did you already type the "fastboot reboot reboot RUU" command ??
#Root-Hack_Mod*Always\
laie1472 said:
How much battery did you have left before you turned your phone off ?? Also what was the reason you turned your phone off ??? Also you linked to the use fastboot thread did you already type the "fastboot reboot reboot RUU" command ??
#Root-Hack_Mod*Always\
Click to expand...
Click to collapse
About 75% if I remember correctly. Only light usage. And I just turned it off in school, we were taking a test. Nothing abnormal about turning it off. And yes, several times. Tried flashing recovery/system/boot in every way possible, using that command and not using that command. I noticed something else- it seems like the NAND memory is completely wiped. There is NOTHING on the phone, other than the bootloader.
After you ran that command you tried to flash a zip or no ??? And more info on when you say the bootloader is the only thing on the phone would be appreciated. Also when you plug your phone into your pc does it recognize in its current state ??? Also when you boot into the bootloader what info is now displayed ???
#Root-Hack_Mod*Always\
laie1472 said:
After you ran that command you tried to flash a zip or no ??? And more info on when you say the bootloader is the only thing on the phone would be appreciated. Also when you plug your phone into your pc does it recognize in its current state ??? Also when you boot into the bootloader what info is now displayed ???
#Root-Hack_Mod*Always\
Click to expand...
Click to collapse
Yes, I tried flashing multiple times. As I said, it fails with a CID check failure. And it doesn't seem that there's anything on the NAND anymore, as it doesn't even get to the boot logo, and recovery will just restart the phone.
My PC recognizes my phone, only in fastboot. And just normal bootloader info- model number, baseband, etc.

Please help, I'm stuck on grey screen while changing MID?

I have been following this guide http://forum.xda-developers.com/showthread.php?t=2322820 - by shadowboy23 -to change phone MID and I got stuck on the grey screen. All the steps have been successful and I still couldn't get past the grey screen. The computer can't recognize the phone and the fastboot adb commands won't work -waiting for device. I have tried to reboot the phone and I'm still stuck on that grey screen. RUU gives me error 170!!!! What can I do?
edit: moved to other thread http://forum.xda-developers.com/show....php?t=2542529
alray said:
If I understand, you flashed eng hboot, it rebooted to grey screen, you did change mid with "fasboot oem writemid" then cid with "fastboot oem writecid". After, you lunched that ruu.exe and it said. Error 170 and right after usb/fastboot aren't working?
Error 170 is a usb connection failure. Do you have latest drivers with htc sync unistalled? Maybe you want to try witj another usb port/cable.
As long that you can boot your phone to that grey screen you SHOULD be able to send fastboot commands
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Hi @alray, can you please post here: http://forum.xda-developers.com/showthread.php?t=2542529
let's try and keep all the info in one thread, thank you :good:

[Q] Can't get past white HTC logo screen, stock rom(?) details within

EDIT FOR DETAIL: I CAN GET TO AND USE FASTBOOT, THAT SEEMS TO BE IT (Well, I could before it went into an infinite bootloop, but once the battery runs down I can probably get back in)
Hi All,
I received a HTC ONE today (Model on back: PNO7140) - got it for cheap from an op shop but sold as-is :/
When I plugged it in there was a red flashing light so I held power + vol+/- and it booted to the white HTC logo and then turned off but showed a solid red LED, so i left it to charge for a couple hours.
Now I'm having a look at it and it always turns off after the HTC logo.. I can get into the setup screen with vol- but factory reset seems to just freeze as soon as I press it (left for maybe five minutes?) - fastboot activates OK and the device shows up on my win7 pc.
I've attached a getvar all from fastboot and I'll type out the first few lines shown in fastboot on the device, let me know if you need anything else:
*** LOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.56.0000
RADIO-4A.23.3263.28
etc..
Going to bootloader just reboots the phone, shows the HTC logo, then turns off and device QHUSB_DLOAD shows up without drivers in device manager (same thing that happens when device is powered down from fastboot).
I have ADB and fastboot installed on this PC, I've done rom updates in the past but got quickly lost when trying to figure my way through this one so thought I"d ask for help before messing anything up.
Thanks anyone and everyone
e: oh one other thing sometimes it will show the Battery with lightning bolt symbol too - although fastboot says battery status is good.. also it seems to take awhile to turn on, like I have to hold the power button for about 10 seconds.. don't know if that's normal? I'm not covering the light sensor.
defroster said:
Hi All,
I received a HTC ONE today (Model on back: PNO7140) - got it for cheap from an op shop but sold as-is :/
When I plugged it in there was a red flashing light so I held power + vol+/- and it booted to the white HTC logo and then turned off but showed a solid red LED, so i left it to charge for a couple hours.
Now I'm having a look at it and it always turns off after the HTC logo.. I can get into the setup screen with vol- but factory reset seems to just freeze as soon as I press it (left for maybe five minutes?) - fastboot activates OK and the device shows up on my win7 pc.
I've attached a getvar all from fastboot and I'll type out the first few lines shown in fastboot on the device, let me know if you need anything else:
*** LOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.56.0000
RADIO-4A.23.3263.28
etc..
Going to bootloader just reboots the phone, shows the HTC logo, then turns off and device QHUSB_DLOAD shows up without drivers in device manager (same thing that happens when device is powered down from fastboot).
I have ADB and fastboot installed on this PC, I've done rom updates in the past but got quickly lost when trying to figure my way through this one so thought I"d ask for help before messing anything up.
Thanks anyone and everyone
e: oh one other thing sometimes it will show the Battery with lightning bolt symbol too - although fastboot says battery status is good.. also it seems to take awhile to turn on, like I have to hold the power button for about 10 seconds.. don't know if that's normal? I'm not covering the light sensor.
Click to expand...
Click to collapse
Try the solution from this thread: http://forum.xda-developers.com/showthread.php?t=2770684
Good luck!
That seems pretty full on. I have a Linux live CD somewhere but should I not try something simpler first?
Keeping in mind fastboot seems to work?
So far I've tried running revive.sh - device not found, tried unlocking via htcdev - it shows the unlock notification request on the phone but after i push yes it reboots and bootloader still reports locked i think? tried rumrunner but it won't run from bootloader.
Heeeeelp!
tried:
chmod 755 PblClear
sudo modprobe qcserial
sudo ./PblClear
and it actually got past the HTC screen to the next HTC screen with beats logo and made a noise... sat there for a minute, then turned itself off...
progress of sorts?
E: unable to repeat that so it may have been unrelated
Is it possible to push a ROM via fastboot? Given that I'm s-on etc?
If I"m not mistaken I can't really do anything from fastboot unless the bootloader is unlocked?
I've tried the HTCdev method a bunch of times, after I click yes it just freezes for a second, reboots and is the same as before (locked).
and now it's in an infinite bootloop !
I can't stop the damn thing power cycling!
Escaped the bootloop but it goes into one whenever turned on or plugged in now :/
anyone?
No one has any ideas?
defroster said:
If I"m not mistaken I can't really do anything from fastboot unless the bootloader is unlocked?
I've tried the HTCdev method a bunch of times, after I click yes it just freezes for a second, reboots and is the same as before (locked).
Click to expand...
Click to collapse
http://xda7.androidrevolution.org/db_mirror/Firmware/HTC/HTC_One/707/4.20.707.7.zip
Download this and flash it with fastboot. This is signed firmware and requires a locked bootloader so that's not a problem.
As I said in the unbrick thread know one has confirmed this did or didn't work. Try it and please let me know the result.
Download the firmware and rename the file firmware.zip and put it in your fastboot folder.
Reboot the phone into the bootloader and connect fastbootusb.
In the fastboot command line type.
Code:
fastboot erase cache
Code:
fastboot oem rebootRUU
case sensitive
Your phone will reboot to a black screen with silver HTC logo. This is ruu mode we can now flash the firmware.
Code:
fastboot flash zip firmware.zip
The first flash is just a pre-update. The screen will go off and then return to ruu mode. Flash the zip again immediately.
Code:
fastboot flash zip firmware.zip
The second flash will flash the firmware, the progress bar on the screen will not reach 100% this is normal as long as the command line has finished it's output it's done.
Code:
fastboot reboot-bootloader
Once that's done (be sure to delete any old Unlock_code.bin you already have from htcdev) then go and complete the full unlock procedure to get a new Unlock_code.bin and try to unlock it again.
:fingers-crossed:
The idea is by flashing firmware your reinstalling hboot, do with new hboot and unlock code hopefully it will work but as I say I can't confirm it. Worth a try though.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Categories

Resources