Develop Bugs

Need help with blank screen

Few days ago, my G2's screen just went blank (dark blueish if I press any buttons on it). I live in Canada, so can't send it back to Tmobile since I'm not with them. But, I can send it back to HTC since it's still under warranty. Only problem is that I rooted the phone and s-off and then flashed Virtous Rom on it couple of months ago.
With the help of a senior member (eunkipark92), i was able to install ADB, and using that I can see that it recognizes my device when connected with PC. Now, I don't know whether the problem is with my phone's software or with the hardware (screen) itself.
I say that because I had a pattern set up to unlock the code before the screen went blank and even now I can swipe my finger on the screen in the specific manner that I used to before and it would unlock the phone. The screen still remains blank (dark blue) ofcourse, but I can change the phone's profile from vibration to loud etc after unlocking the screen by pressing the volume key up or down.
I was told by another member (PaganAng31) that if I can totally brick the phone using a command in ADB something like "dd = /dev/block/mmblk1p3" there will be noway for HTC people to figure out whether or not the phone was rooted before. But he wasn't sure and asked me to post here.
Now my first attempt will be to fix it somehow or unroot the phone and put the stock rom back in using ADB and then send it back to HTC. If I can't do that, then I would totally brick it (only if it's 100% sure that HTC won't figure out that this phone was rooted before) so that they can totally flash it or change the screen or send me a replacement. Also what's the exact command that is used in ADB and how do you use it for totally bricking the phone?
Any kind of help will be appreciated. Thanks

Its probably hardware issue. I heard that g2 screen will just stop working...display failure..
I read this somewhere before I purchased g2 but I still bought it anyway.
Anyways..
Have you downloaded the hboot engineer and recovery.img?
I would like to give you step by step instruction but I haven't used adb since I got rid of my nexus one...so I don't really rememebr the commands to flash stuffs:/ sorry.
If it is software issue you can fix it since you were able to get adb working
But if it doesn't work flashing a new hboot,recovery and a new rom its mostly lcd failure or ribbon is damaged.
U can use hboot pc10img method to put ur stock rom and radio. But I don't know a way to unroot it if you can't see the screen.
When I had nexus one and when I had to send it for repair.
(My bootloader was unlocked with stock rom)
They didn't charge me for rooting. Just my experience with htc.
If there is anything I can help pm me.
Sent from my HTC Desire Z using Tapatalk

eunkipark92 said:
Its probably hardware issue. I heard that g2 screen will just stop working...display failure..
I read this somewhere before I purchased g2 but I still bought it anyway.
Anyways..
Have you downloaded the hboot engineer and recovery.img?
I would like to give you step by step instruction but I haven't used adb since I got rid of my nexus one...so I don't really rememebr the commands to flash stuffs:/ sorry.
If it is software issue you can fix it since you were able to get adb working
But if it doesn't work flashing a new hboot,recovery and a new rom its mostly lcd failure or ribbon is damaged.
U can use hboot pc10img method to put ur stock rom and radio. But I don't know a way to unroot it if you can't see the screen.
When I had nexus one and when I had to send it for repair.
(My bootloader was unlocked with stock rom)
They didn't charge me for rooting. Just my experience with htc.
If there is anything I can help pm me.
Sent from my HTC Desire Z using Tapatalk
Click to expand...
Click to collapse
Ok. So what's the first step now? Do we reflash hboot and recovery? I flashed it 3 months ago using this method:
http://forum.xda-developers.com/showthread.php?t=833965
Now to reflash it, do we use this method on the wiki and just follow it. It looks pretty straight forward?
http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
If that's the one, then the link to Engineering hboot for Tmobile G2 is broken. Any alternative?
Also do you know the command to completely brick the phone in ADB in case we are unable to fix it?

I am interested as well. Coincidentally my screen just went completely black 3 hours ago. I think the lcd is dead. Last thing I did earlier today was that I flashed from the ..04.30 radio to the ..02.26 while troubleshooting HSDPA issues.
I think I could settle for adb shell commands to flash the roms if anyone can point me to a link. Closest i've found is a link to the G1 forums (I used to have one) but that shows how to a manual nandriod restore which is a bit different.
Last resort as the OP is asking, will creating a typo while following a rooting guild do the trick?

icruisin said:
I am interested as well. Coincidentally my screen just went completely black 3 hours ago. I think the lcd is dead. Last thing I did earlier today was that I flashed from the ..04.30 radio to the ..02.26 while troubleshooting HSDPA issues.
I think I could settle for adb shell commands to flash the roms if anyone can point me to a link. Closest i've found is a link to the G1 forums (I used to have one) but that shows how to a manual nandriod restore which is a bit different.
Last resort as the OP is asking, will creating a typo while following a rooting guild do the trick?
Click to expand...
Click to collapse
Good luck buddy. Let me know if you find a way to get it fixed or brick it. From another thread I found the command is something like:
dd if=/dev/zero of=/dev/block/mmcblk0p*
Where * = the partition number.
But I just don't know how to apply it.

Did you guys get this going? Op sent me a pm for help a few days back and I just got this. I had the same thing happen.
You can brick using the dd= command. You would follow the OLD eng hboot root guide except instead of having the real hboot.img you would have a random text file named hboot.img inplace of it. HOWEVER, YOU DO NOT WANT TO DO THAT.
You can put back to stock. Make sure phone has a good charge or it won't flash properly.
First things first. If there is anything you want to save off the phone first, ie good (bad) pic mess from your gf or similar , then search on googl.code or xda for screencast. It allows you to see the phones screen on your comp screen (requires adb installed and working). It works in the os, and in recovery, but unfortunatly doesn't work in fastboot.
After everything you want is saved, backup your sdcard to your comp, and clean off sdcard. If you are rooted per gfree use it to revert back to s-on (if you are old eng hboot only method, skip that step). Replace the misc.img as per the unroot guide. Then put the stock shipped PC10IMG on the root of your sdcard. Boot into fastboot by holding down vol and power. Give it few mins to read and load pcimg, let's say 5 mins to be safe. Press vol up to confirm to reflash ( I know u can't see screen, but have faith). It will reboot in the middle of process to flash radio, then will finish flashing. It should only take 10 mins, but leave it for like 30 to be safe. Then press power button to reboot.
At this time it should boot into stock os. Remember first boot take awhile, so give it a min. To confirm it worked, do 2 things. On comp type adb remount and should say not allowed. Also try using screencast should not work since usb debugging is required for it, and its turned off by default on stock os.
Goodluck, hope this helps. If anyone finds this usefull of needs any help, let me know.

fastludeh22 said:
Did you guys get this going? Op sent me a pm for help a few days back and I just got this. I had the same thing happen.
You can brick using the dd= command. You would follow the OLD eng hboot root guide except instead of having the real hboot.img you would have a random text file named hboot.img inplace of it. HOWEVER, YOU DO NOT WANT TO DO THAT.
You can put back to stock. Make sure phone has a good charge or it won't flash properly.
First things first. If there is anything you want to save off the phone first, ie good (bad) pic mess from your gf or similar , then search on googl.code or xda for screencast. It allows you to see the phones screen on your comp screen (requires adb installed and working). It works in the os, and in recovery, but unfortunatly doesn't work in fastboot.
After everything you want is saved, backup your sdcard to your comp, and clean off sdcard. If you are rooted per gfree use it to revert back to s-on (if you are old eng hboot only method, skip that step). Replace the misc.img as per the unroot guide. Then put the stock shipped PC10IMG on the root of your sdcard. Boot into fastboot by holding down vol and power. Give it few mins to read and load pcimg, let's say 5 mins to be safe. Press vol up to confirm to reflash ( I know u can't see screen, but have faith). It will reboot in the middle of process to flash radio, then will finish flashing. It should only take 10 mins, but leave it for like 30 to be safe. Then press power button to reboot.
At this time it should boot into stock os. Remember first boot take awhile, so give it a min. To confirm it worked, do 2 things. On comp type adb remount and should say not allowed. Also try using screencast should not work since usb debugging is required for it, and its turned off by default on stock os.
Goodluck, hope this helps. If anyone finds this usefull of needs any help, let me know.
Click to expand...
Click to collapse
Thanks. I know what to do next time if my G2 is messed up But I already bricked my phone last week and sent it back for repair, since I couldn't find any other to way fix it.

[Tutorial] Unbrick your softbricked HTC Wildfire S

Your phone is said to be bricked when you screw up with your radio partition of your phone. This contains the bootloader which loads the operating system. This is a hard brick and needs expensive hardware to fix. I can only help you with a soft brick.
benjamingwynn said:
Most people seen to not know the difference between a soft brick, a boot failure and a total brick.
Boot failure: commonly referred to as 'the HTC screen', 'the white screen' and of cause the 'help me my phone is stuck - problem'. This problem can be caused by many things, including the kernel, library's and ramdisk (think of a ramdisk like a map of your phones internal hardware). This can easily be resolved by flashing a new ROM.
Soft brick: Is where your phone gives out no screen output, but does give out some vibrations or you can access the bootloader utility/hboot, this can be fixed by flashing an RUU
Brick: your phone is as useless as a brick. It does not turn on nor make any vibrations, and you can not access the bootloader utility. There is no way to fix this.
Here's some ways to avoid soft bricking/bricking:
- Don't flash unofficial radio firmware
- Don't flash unofficial hboot software
- Don't throw your phone
- Don't flash anything suspicious in hboot
- Don't flash an RUU not designed for your phone
Here's some common misunderstandings:
- Roms, on there own will never brick your phone
- Kernels will never brick your phone
- The bootloader is not the radio
- Too many flashes will not brick your phone (however, you may make the internal memory smaller by KB because of bad sectors, but that story is for another time )
Sent from my HTC Wildfire S A510e using xda premium
Click to expand...
Click to collapse
Thanks to benjamingwynn for the above info. Original post
It is a good practice to keep at least 3 nandroid backups on your sd card or computer. Also, making a goldcard is also necessary to run an RUU and to flash a PG76IMG.zip these things make it easier to unbrick your phone
Install ADB and Fastboot here first.
A Soft brick may be of many types.
The 3/5/7 vibe Brick (common with A510c)
This is Qualcomm Diagnostics mode.
--> How To Fix It (Click here)
You have to use a PG76IMG.zip extracted from your RUU, and not the file given in that post.
kalaker said:
To extract from the RUU,
Launch RUU (For this to be easiest, close all other running applications)
At the screen for the README, launch Windows Explorer
In the navigation/address bar type "%TEMP%" without the quotes.
Choose the first long-named folder (actually, the most recent) and open it.
Follow folders until you get to where there is a whole, big list (it should only be 1 or 2 subfolders).
Look for ROM.zip
Drag to desktop
Rename to PG76IMG.zip
Put it on SD Card.
Click to expand...
Click to collapse
Phone doesn't boot but goes to recovery saying something like E:/ Invalid command argument
Your boot partition is messed up
-->How to fix it
-Flash your ROM again
or
-Flash another ROM
or
-Restore a nandroid backup.
If that didn't work,
-Extract the boot.img from your ROM zip and and copy it where ADB and Fastboot are.
-boot into your bootloader [wait 15 sec] select 'fastboot' and press power.
-type
Code:
fastboot flash boot boot.img
Reboot
Stuck on splash screen (White backgound with green 'htc')
Wait for at least 20 minutes to be sure its really stuck.
--> How to fix it
-remove the battery, boot into recovery, Wipe Data/Factory reset and try again
-still doesn't boot?
Restore a nandroid backup/Flash another Rom
Bootloop (Bootanimation plays repeatedly)
Connect the phone to your computer, run a logcat using the
Code:
adb logcat
command and look for repeating blocks
--> How to fix it
-remove the battery, boot into recovery, Wipe Data/Factory reset and try again
-still doesn't boot?
Restore a nandroid backup/Flash another Rom
Dont forget to click the Thanks button!!
Please leave your feedback/comments/corrections
Inform me if something is wrong and i will fix it

HI I have a 3 vibe brick on my CDMA VM USA HTC Wildfire S. It started with phone restarting and so I tried to recover though CWMod recovery, as I had backed it up when I first rooted my phone. During recovery it failed. I rebooted my phone then was stuck on the splash screen, after that I tried a battery pull and wound up with the 3 vibe brick. I have tried this method 4 times now, nothing seems to change, 3 vibes on power + vol down, wait 5 min, press vol up, wait 5 min again press vol up, no vibe, no nothing. screen stays black, no other vibes, do a battery pull, start over, same thing again. Any suggestions would be greatly appreciated cause I have no backup phone at the moment.

I'm sorry that's my mistake you have to do that with a PG76IMG.zip, not pb31img. Extract it from the ruu of your carrier and then follow the procedure
Sent from my HTC Wildfire S A510e

Ok cool. I was kinda thinking that's what it was, cause every time I was in hboot before this happened that's what it looked for, but I wasn't sure. Not really familiar with android but learning. Thanks again, btw, it works and you rock.

fr33kachu said:
Ok cool. I was kinda thinking that's what it was, cause every time I was in hboot before this happened that's what it looked for, but I wasn't sure. Not really familiar with android but learning. Thanks again, btw, it works and you rock.
Click to expand...
Click to collapse
So you're unbricked now? Could you post the PG76IMG for other users?

usb connection
Hi, really good tutorial bud, mine is stuck on 7 or five vibe seems random at the moment...transffered zip to sd but I think my battery is dead and does not seem to charge on charger and laptop not recognising usb connection (though red led comes on....do I need to find alternative way to charge battery ? Also if in diagnostics mode would this show in device manager... as I am guessing if it does not that means I aint so phone is truly bricked...
Thanks ahead
Ben

So did you try the method shown?

thank you mate! really help for us keep sharing!
Sent from my HTC Wildfire S A510e using Tapatalk 2

hard brick?
Hey all.
I recently purchased a Wildfire S(no simlock, no branding) from ebay. The touchscreen was responding very randomly so (without giving it too much thought, sigh) I decided to flash it. I'm in Germany so I used "RUU_Marvel_S_HTC_Europe_2.13.401.3_Radio_47.23c.35.3037_7.54.39.28M_release_236989_signed.exe"
I don't know what I did wrong but now I seem to have a bricked phone. When powered on it displays nothing, it doesn't vibrate and it is not recognizes by Windows when connected via USB, it doesn't even show up in the Device Manager as some sort of device. The display keeps turning on and off every 2,3 seconds regardless if I turn the phone on or i just plug in the battery so now it sits with no battery waiting to be salvaged.
Can you confirm that I have a hard bricked phone? I've read that it is possible to unbrick the HTC Sensation by putting it in QDL mode.
Can this be done with the Wildfire S? I saw two little holes near the upper right corner of the battery.
If it is absolutely impossible for the Wildfire S, can you recommend a place in Munich where I could get my phone fixed? What's a reasonable price so I don't get ripped off?
Thank you all! I hope I've posted in the right forum. Should I open a new thread for this?
Ciao.

Did you unlock your bootloader? If not, you can claim your warranty

vbhtt said:
Did you unlock your bootloader? If not, you can claim your warranty
Click to expand...
Click to collapse
I've got it from ebay, so I don't have any receipt, just the phone. Also didn't bother to check that before bricking it.

vbhtt said:
So did you try the method shown?
Click to expand...
Click to collapse
Yes mate I tryed..get as far as 5 vibe sometimes 7 vibes sometimes led on or off, wait 5 mins push up vol wait at least 10 mins push up again and no single buzz..gutted...I am unlocked so screwed there. Is there no way to get usb connection to do it the old way.

@ B3NJY What phone do you have (marvel/mavelc, which carrier)? Which pg76img did you use? Did you make a goldcard?
@machofx Can you boot into the bootloader? (remove and replace battery, press and hold vol- and power)

sigh
vbhtt said:
@ B3NJY What phone do you have (marvel/mavelc, which carrier)? Which pg76img did you use? Did you make a goldcard?
@machofx Can you boot into the bootloader? (remove and replace battery, press and hold vol- and power)
Click to expand...
Click to collapse
I can't boot into the bootloader. As I said, nothing is displayed when I turn the phone on nor does it vibrate, it just turns the backlight on and off every two seconds.
P.S. I tried VolumeDown+Power button after removing the battery, didn't work!

machofx said:
I can't boot into the bootloader. As I said, nothing is displayed when I turn the phone on nor does it vibrate, it just turns the backlight on and off every two seconds.
P.S. I tried VolumeDown+Power button after removing the battery, didn't work!
Click to expand...
Click to collapse
I think the ruu did not install properly. You probably have a hard brick. ( read 1st paragraph of 1st post)

I am pretty sure its marvel c and my carrier is 02uk I got it unlocked soff in shop,
I installed .sense rom but didnt like it so restored in recovery and all was fine but always had a problem with ota updates so tryed to do it manually, managed once but tryed latest update and its bricked me to black screen, volume down gives me 5/7 vibes.....
MARVEL PVT SHIP S-OFF RL
HBOOT - 1.08.0000
MICROP - 0451
RADIO - 7.53.39.03M
S/W 2.13.401.2
I got the rom from here....link proved on this site...
http://www.mediafire.com/?ih6amhh2kzm4q6g which was the correct one I think for europe, I cannot make goldcard if I cannot connect to usb can I ?

B3NJY said:
I am pretty sure its marvel c and my carrier is 02uk I got it unlocked soff in shop,
I installed .sense rom but didnt like it so restored in recovery and all was fine but always had a problem with ota updates so tryed to do it manually, managed once but tryed latest update and its bricked me to black screen, volume down gives me 5/7 vibes.....
MARVEL PVT SHIP S-OFF RL
HBOOT - 1.08.0000
MICROP - 0451
RADIO - 7.53.39.03M
S/W 2.13.401.2
I got the rom from here....link proved on this site...
http://www.mediafire.com/?ih6amhh2kzm4q6g which was the correct one I think for europe, I cannot make goldcard if I cannot connect to usb can I ?
Click to expand...
Click to collapse
My friend, you have a marvel, not marvelc. ( if it was a marvelc, then the 1st line would be MARVELC EVT1 S-OFF RL & O2 doesn't sell the marvelc). When did you check this?Which PG76IMG is that? It should have a higher s/w number than yours ( you can do it if it is lower also, but that is a much longer procedure). You can make a goldcard by putting your sd card in another htc phone also.

Help me
I cannot remember when I copied those details down but I have access to my girlfriends wildfire buzz or card reader can you help me with it please if you have time....I am on shifts at the moment and off to work now till 11.00pm but if you can find time to give me a guide I would really appreciate it....I dont think I am anywhere near as smart as you but I am sure I can follow your links and instructions...it may help a lot more people and in my eyes should be a sticky.
Thank you
Ben

B3NJY said:
I cannot remember when I copied those details down but I have access to my girlfriends wildfire buzz or card reader can you help me with it please if you have time....I am on shifts at the moment and off to work now till 11.00pm but if you can find time to give me a guide I would really appreciate it....I dont think I am anywhere near as smart as you but I am sure I can follow your links and instructions...it may help a lot more people and in my eyes should be a sticky.
Thank you
Ben
Click to expand...
Click to collapse
Well there are a lot of tutorials on the internet on how to make a goldcard. Just use Google
Sent from my HTC Wildfire S A510e using Tapatalk 2

my phone is doing the one where the screen stays white with the green htc logo i forgot to back mine up and flashing any roms are not helping
wildfire s unlocked bootloader with s-off marvelc
h-boot-1.10.0001
microp-0354
radio-0.94.00.0109
please help if u can my girlfriend is gonna kill me and/or steal my triumph lol
thank you for any help

Installed HBOOT drivers and phone now boot loops

Hello,
As the subject line states, I followed the instructions for adding the HBOOT drivers to my computer and my computer now reads Android Phone --> Android Bootloader Interface. When I went to reboot the phone, it began to boot loop with the HTC Incredible splash screen, then screen turn black, then screen turns white vibrate once and display the same HTC Incredible splash screen. It does this over and and over. Nothing was installed on the phone, it is not rooted. None of the other features work such as Recovery, Clear Storage, or Factory Reset.
Here are the specs as stated in HBOOT mode:
*** UNLOCKED ***
Incredible XD SHIP S-ON
HBOOT- 1.02.0000
MICROP- 0417
TOUCH PANEL- ATMELC03_16ac
RADIO- 2.15.10.07.07
DEC 21, 2011
It was working prior to the installation of the USB driver install and it was running 2.3.4.
If you all can give me a heads up as to where to look, I would be most grateful. I've researched but no one seems to have this problem. Nothing was installed on the phone itself, just the drivers to the computer and now it boot loops. I think it may be a defective product, but I want to ensure that there is absolutely nothing I can do to fix it before I contact the seller and ask for a replacement or a refund. Thank you all very much for your time.

jml30 said:
Hello,
As the subject line states, I followed the instructions for adding the HBOOT drivers to my computer and my computer now reads Android Phone --> Android Bootloader Interface. When I went to reboot the phone, it began to boot loop with the HTC Incredible splash screen, then screen turn black, then screen turns white vibrate once and display the same HTC Incredible splash screen. It does this over and and over. Nothing was installed on the phone, it is not rooted. None of the other features work such as Recovery, Clear Storage, or Factory Reset.
Here are the specs as stated in HBOOT mode:
*** UNLOCKED ***
Incredible XD SHIP S-ON
HBOOT- 1.02.0000
MICROP- 0417
TOUCH PANEL- ATMELC03_16ac
RADIO- 2.15.10.07.07
DEC 21, 2011
It was working prior to the installation of the USB driver install and it was running 2.3.4.
If you all can give me a heads up as to where to look, I would be most grateful. I've researched but no one seems to have this problem. Nothing was installed on the phone itself, just the drivers to the computer and now it boot loops. I think it may be a defective product, but I want to ensure that there is absolutely nothing I can do to fix it before I contact the seller and ask for a replacement or a refund. Thank you all very much for your time.
Click to expand...
Click to collapse
Have you tried fastboot flashing cwm recovery.img (http://dinc.does-it.net/Guide_Root_New_Hboot/recovery.img) again to see if you can gain access to it. If that dosent work i would try the latest ruu.exe with a pc (http://dinc.does-it.net/Stock_Image...0_Incredible_C_hboot_1.02.0000_4.08.605.2.exe).

Thank you for replying, cmlusco, and thank you all for viewing.
So, I doubt this is resolved but this morning I was having the problems I described. Before I left, I turned the phone off and let it charge all day. When I came home, the charging light went from orange to green. I unplugged it and turned it on. All of a sudden, it turns on as normal. All of the screens are empty, but it looks like all of the features work. This phone is haunted and it makes me doubt if I should even proceed to root it. I want to root it via Unrevoked but with how it flipped out over installing regular drivers and now currently showing in Windows Device Manager as Android Composite ADB Interface rather than Android Bootloader Interface, I think I'll hold off. Anyway, thank you all for viewing and thanks again, cmlusco, for taking time out and replying to post.

jml30 said:
Thank you for replying, cmlusco, and thank you all for viewing.
So, I doubt this is resolved but this morning I was having the problems I described. Before I left, I turned the phone off and let it charge all day. When I came home, the charging light went from orange to green. I unplugged it and turned it on. All of a sudden, it turns on as normal. All of the screens are empty, but it looks like all of the features work. This phone is haunted and it makes me doubt if I should even proceed to root it. I want to root it via Unrevoked but with how it flipped out over installing regular drivers and now currently showing in Windows Device Manager as Android Composite ADB Interface rather than Android Bootloader Interface, I think I'll hold off. Anyway, thank you all for viewing and thanks again, cmlusco, for taking time out and replying to post.
Click to expand...
Click to collapse
Pretty sure it says Android Composite ADB interface because the phone is plugged in and booted up normally. Try shutting down and going into HBOOT and then plug in the cord and see what Device Manager says. If so, you could proceed with trying to root.
I got the same boot loop, and after charging fully, it quit doing it. I got the recovery pushed to the phone but the root process failed with UnrEVOked stating “Error: failed to get root. Is your firmware too new?” So the next thing I'm going to try is uninstalling all market apps that I downloaded as they say that can cause a conflict. Won't be able to try that until Thursday though.
If by chance you were able to root the phone with UnrEVOked successfully, let me know how you did it so I can use the same procedure.
radio I'm on: 2.15.10.07.07

mjolnir677 said:
Pretty sure it says Android Composite ADB interface because the phone is plugged in and booted up normally. Try shutting down and going into HBOOT and then plug in the cord and see what Device Manager says. If so, you could proceed with trying to root.
I got the same boot loop, and after charging fully, it quit doing it. I got the recovery pushed to the phone but the root process failed with UnrEVOked stating “Error: failed to get root. Is your firmware too new?” So the next thing I'm going to try is uninstalling all market apps that I downloaded as they say that can cause a conflict. Won't be able to try that until Thursday though.
If by chance you were able to root the phone with UnrEVOked successfully, let me know how you did it so I can use the same procedure.
radio I'm on: 2.15.10.07.07
Click to expand...
Click to collapse
What version of hboot do you have?

nschiwy said:
what version of hboot do you have?
Click to expand...
Click to collapse
hboot-0.92.0000

mjolnir677 said:
hboot-0.92.0000
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1306400
I personally recommend the zergrush method which is in the second post on this thread but people have had success with both ways

[Q] Nexuz 7 stuck at the google logo

Hello I need a but of help my Nexus 7 is showing my nothing but the google logo and at the store earlier it showed the android with his chest up and a red triangle. it doesnt even show the moving colors after i turn it on it just sits and says google like a paper weight. i can turn it off and on but nothing more. the geek squad at best buy told me to ask for help here at Xda. last thing i was doing with it was opening deer hunter 2013 and next i go to see if it opened and it stuck on the google logo. can anyone help me fix my tablet? its not under store warranty only manufactures.

Well, sucks to be you.....just kidding...but that does suck. Now, on to more serious matters...
Do you have access to your bootloader? (hold the power button + the vol up button at the same time) If you do, you might want to look into rooting the tablet. Based on the content of your post, I am assuming that you haven't. There is plenty information about rooting the Nexus 7.2 tablet (and just about every other Android device). Simply Google "root Nexus 7 2013" and you will quickly find your answer.
Also, how much do you know about rooting and the sort? I want to know before I waste my time giving details about info that you are aware of.

aarsyl said:
Well, sucks to be you.....just kidding...but that does suck. Now, on to more serious matters...
Do you have access to your bootloader? (hold the power button + the vol up button at the same time) If you do, you might want to look into rooting the tablet. Based on the content of your post, I am assuming that you haven't. There is plenty information about rooting the Nexus 7.2 tablet (and just about every other Android device). Simply Google "root Nexus 7 2013" and you will quickly find your answer.
Also, how much do you know about rooting and the sort? I want to know before I waste my time giving details about info that you are aware of.
Click to expand...
Click to collapse
i dont know anything about rooting. i dont have access to the boot loader. i did a few days ago now it wont even show up, the guy and best buy tried to bring it up and its like it was showing a dead android or something chest open with a red triangle above it. he said someting about maybe have to flash a new or or something like that on to it, it wont show me anything just stays off or shows the google logo when its on

Sigh...that is the bootloader. Maybe...he could have booted into the stock recovery, which shows this or something similar for most devices. Please remember, they are reps...they may know about the software, but usually they speak from their experience or their perspective. I'm glad that he sent you here for a second opinion.
Hold the volume down button and power button to get into the bootloader. You should see some options at the top of the screen saying Start, Restart bootloader, Recovery Mode, Power Off. Not sure if those are the exact options, but it's pretty close.
Also, you need to look into rooting your device. You need to download some files first. You'll need adb, fastboot, and drivers for your Nexus.
And one last thing....what Computer OS do you use? The rooting process is slightly different for each one (Windows 7, 8/8.1, Mac OS, & Linux). If you are into computers, and you have Linux installed on a device, good for you. That is my preference when rooting, as Android is built from Linux, and naturally supported without the need for drivers.

I had similar problems when I first bought it. Going into recovery and resetting the tablet cured it. You will lost all your data BTW.

He's facing the loss of his entire tablet, so I'm sure that data loss isn't the biggest thing to worry about.
But yes, just about every solution involves a clean wipe of data.
_______________________________________
Phone: HTC EVO 4G LTE
Sense 5, S-Off
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel
_______________________________________

I'm stuck on the google logo too. I had my tablet plugged in over night and when I opened the cover this morning it woke up, but as soon I tried to access anything it rebooted and stuck.
I'm unlocked and have tried various thing. NRT doesn't recognize it as an ADB device so I don't think that will work. Fastboot works, but I keep getting "FAILED (remote: flash write failure)" when I try to use the factory flash all, or the instructions found here: http://forum.xda-developers.com/showthread.php?t=2381582
I can use fastboot to query the device and get it to return "flo" but it seems like the flash storage has failed.
if it's truly horked, can I use "fastboot oem lock" to relock it and attempt a warranty replacement?

sean67854 said:
I'm stuck on the google logo too. I had my tablet plugged in over night and when I opened the cover this morning it woke up, but as soon I tried to access anything it rebooted and stuck.
I'm unlocked and have tried various thing. NRT doesn't recognize it as an ADB device so I don't think that will work. Fastboot works, but I keep getting "FAILED (remote: flash write failure)" when I try to use the factory flash all, or the instructions found here: http://forum.xda-developers.com/showthread.php?t=2381582
I can use fastboot to query the device and get it to return "flo" but it seems like the flash storage has failed.
if it's truly horked, can I use "fastboot oem lock" to relock it and attempt a warranty replacement?
Click to expand...
Click to collapse
You can try Method 2 from this post: http://forum.xda-developers.com/showthread.php?t=2513701
I know it's for the N5, but I used this one for both my Galaxy Nexus, N5 and N7. Since they are all Nexuses (Nexi?), the same general procedures apply. I always prefer to do it all manually, step-by-step, which is why I went with Method 2 in the OP of that thread. Obviously, since this is the N7, just skip the radio flashing command. Everything else is the pretty much exactly the same. If this doesn't work in fastboot, then it's probably a hardware failure.

[Q] USB debugging selected but not working

Hi everyone.
I had a 4 year old Incredible, rooted, running Touch of Blue 3, and after much abuse and the screen finally cracking, I decided to switch. I was given another Incredible that was largely unused for years. I turned it on and activated it tonight, and the USB debugging option was usable (icon showed when enabled). I'm not sure what it was running..but the OTA updates ran and finished apparently and now it seems that USB debugging (and disk mounting) aren't working. I have searched and searched across the tubes and I've tried every solution I could find. Tried different cables, tried different ports, tried different computers and nothing. Absolutely nothing. (Running Win7x64 btw) I've installed the 3.0.0.007 drivers, I've installed the absolute latest drivers, I've booted into the recovery mode and did factory resets, I installed an older version of HTC Sync and newer versions, I've got the AdbDriverInstaller..everything I've found and still the USB debugging option, while enabled, does not seem to activate.
When, using the bootloader menu, I try the recovery option..after a moment I get the red exclamation mark and still nothing.
I have absolutely no idea what to do. My previous rooting experience with this same model phone was a snap by following the nice instructions I found...but this time it's turned into a nightmare. I'll admit I'm a "follow the cookbook" kind of phone user (and not nearly as knowledgeable or as into it as a lot of people are), but I'm just about at it wits end. So I turn to you of this fabled forum for guidance.
I'm sure I'm leaving something out..but here's the bootloader info:
INCREDIBLEC XD SHIP S-ON
HBOOT-1.07.0000
MICROP-0417
TOUCH PANEL-AMELC03_16ac
RADIO-2.15.10.12.20
Software number is 4.08.605.19 710RD
Please help show how ignorant I am about the whole phone hacking scene by telling me the one setting or trick I need to to do get this back working, so I can get back to truly being able to use my device. Thanks in advice!

RevRaven said:
Hi everyone.
I had a 4 year old Incredible, rooted, running Touch of Blue 3, and after much abuse and the screen finally cracking, I decided to switch. I was given another Incredible that was largely unused for years. I turned it on and activated it tonight, and the USB debugging option was usable (icon showed when enabled). I'm not sure what it was running..but the OTA updates ran and finished apparently and now it seems that USB debugging (and disk mounting) aren't working. I have searched and searched across the tubes and I've tried every solution I could find. Tried different cables, tried different ports, tried different computers and nothing. Absolutely nothing. (Running Win7x64 btw) I've installed the 3.0.0.007 drivers, I've installed the absolute latest drivers, I've booted into the recovery mode and did factory resets, I installed an older version of HTC Sync and newer versions, I've got the AdbDriverInstaller..everything I've found and still the USB debugging option, while enabled, does not seem to activate.
When, using the bootloader menu, I try the recovery option..after a moment I get the red exclamation mark and still nothing.
I have absolutely no idea what to do. My previous rooting experience with this same model phone was a snap by following the nice instructions I found...but this time it's turned into a nightmare. I'll admit I'm a "follow the cookbook" kind of phone user (and not nearly as knowledgeable or as into it as a lot of people are), but I'm just about at it wits end. So I turn to you of this fabled forum for guidance.
I'm sure I'm leaving something out..but here's the bootloader info:
INCREDIBLEC XD SHIP S-ON
HBOOT-1.07.0000
MICROP-0417
TOUCH PANEL-AMELC03_16ac
RADIO-2.15.10.12.20
Software number is 4.08.605.19 710RD
Please help show how ignorant I am about the whole phone hacking scene by telling me the one setting or trick I need to to do get this back working, so I can get back to truly being able to use my device. Thanks in advice!
Click to expand...
Click to collapse
I don't really have an idea what is going on, but do fastboot commands work over USB? Try following the guide for unlocking the bootloader:
http://forum.xda-developers.com/showthread.php?t=1600904
You already have the latest HBOOT, so it 'should' just work. If adb isn't working, you'll need to power the phone off, then hold 'volume down' down while powering it on to get into the bootloader. (you may need to use the volume rocker and power button to select bootloader or fastboot, don't remember off the top of my head and it's been a while.) From there, you should be able to continue with the fastboot commands, unlock the bootloader, flash your favorite custom recovery, and I believe you know where to go from there.

musical_chairs said:
I don't really have an idea what is going on, but do fastboot commands work over USB? Try following the guide for unlocking the bootloader:
http://forum.xda-developers.com/showthread.php?t=1600904
You already have the latest HBOOT, so it 'should' just work. If adb isn't working, you'll need to power the phone off, then hold 'volume down' down while powering it on to get into the bootloader. (you may need to use the volume rocker and power button to select bootloader or fastboot, don't remember off the top of my head and it's been a while.) From there, you should be able to continue with the fastboot commands, unlock the bootloader, flash your favorite custom recovery, and I believe you know where to go from there.
Click to expand...
Click to collapse
I've got into fastboot..but there's still nothing I can do. No USB connection is recognized in any form, but it was being seen before the OTA updates started happening. Is it possible that the updates somehow borked debug mode/disk mounting?