Database Info

HD7 Stuck on White HTC Boot Screen

Hey Guys,
I need help,
here is my problem:
My HD7 restart it self. After enter Pin i go to Pictures Hub and it loads,loads,loads after 5 min my device does nothing so i took battery off. My Device start up and stuck on HTC White Screen.
I can go to Tri-Colored Screen, can go to Restore(Checksum)
After one Restore everything works. Now the same problem appeared again. Now i dont want to restore my device again.
Is there a way to start the device without hardrest??
Hope someone can help me.
Sorry for bad english.

Sounds like you may have bad hardware. I'm assuming you've never flashed a custom ROM or anything like that? I hate to break it to you, but your only options at this point are probably either retore again and hope for some reason it works this time, hard reset and hope the problem was in writable storage and not in ROM, flash a custom ROM 9if your bootloader is compatible) and hope that fixes it, or get a warranty replacement for a defective device.

Thanks for your help. I have tested Custom Rom's and Stock Rom's but the problem doesn't go so i have read that it can be a memory card problem. I know my device felt sometimes to the ground so i opened the phone and the memcard was not really inside the socket so i but it inside and all works fine.

[Q] Need help repairing my Nexus s I9020?

i brought the phone at launch, its a T-Mobile version Super AMOLED I9020, im in india though, using indian sim.
the phone was previously rooted, then unrooted, then rooted, then unrooted again. then filnally i was using unrooted nexus s, but with unlocked bootloader and stock recovery.
4-5 months after this, the phone started stucking on google logo.
it used to stuck at google logo at times but a quick battery pull would fix it, one day it didnt. since then it always stuck at the google logo on boot and never turned on, except some 1 out of 1 million times after connecting to computer.
i tired to format the whole phone using stock recovery, it was successful and the phone turned on, but next time when it switched off, same problem again but this time even formatting wont work, the formatting from stock recovery would just display an error that it failed to find a file and formatting aborted.
i tried everything, hundreds of stuff from google and XDA but nothing seems to be working.
today i managed to flash CWR to it. i tired to then erase sdcard but it says failed to mount /sdcard . i also tried other things like update from sd card(i have a ICS update.zip file in the memory) but still it said failed to mount sdcard, tried to wipe-> 'error mounting sdcard'
and now i dont know what ive done but when i boot the phone(normally) it doesnt even display the google logo, it enters bootloader by itself and says 'fastboot mode - no boot or recovery img'
bootloader is still unlocked, CWR is still there and accessible.
i took it to samsung service centre too, they said they will have to replace the motherboard(quoting me 400$ for it lol)
this is my last try really, ive been trying to fix this thing from ages!
is there anything that can be done?
going to sell it if i still cant fix it

I'm in about the same spot. If you have a Linux box available, you might try Adam Outler's "Unbrickable Resurrector." (http://forum.xda-developers.com/showthread.php?t=1397393) It's supposed to be a last gasp kind of thing before you give up. However... I ran it and it crashes -- not the phone, the software itself. Sigh.
I got here by making a backup, then unintentionally erasing everything on the phone, including the backup, the boot image, and the recovery image (the backup, presumably). That's what the message "no boot or recovery img" seems to be saying. Fastboot doesn't work either.
So here's my last gasp before I take it in for repair: apparently you can buy or build a micro-USB connector called a "USB jig" -- it's just a connector with a resistor connecting a pin that's usually not connected. This is supposed to put the phone into download mode, where you can copy a recovery image to the phone. Then you can use CWM to install a new image.
-Rod

It sounds like your mem is shot.
Sent from my Nexus S

I've had a similar problem to this and to solve it I just locked the boot loader and then unlocked it again and everything was back to normal for me. You could try that and see if it works
Sent from my Nexus S using Tapatalk

sell faulty nexus phone
HI
I am intrested in buying a faulty nexus s phone . If in case this is of no use to you then I am ready to buy this.
contact me at 7838448028
Regards
Amit

amity_coolin said:
HI
I am intrested in buying a faulty nexus s phone . If in case this is of no use to you then I am ready to buy this.
contact me at 7838448028
Regards
Amit
Click to expand...
Click to collapse
R u still interested in a faulty Nexus S?

Hi.
My solution may sound a bit strange but me too have the same problem.
Just heat the phone a bit and see if it boots.
Heat it from a hot air source such as laptop heatsink area.
Just get the cell phone warm and it may boit up.
I know it may sound strange but it has worked for me everytime.
Regards
Sent from my xperia TX via xda premium

[Q] Nexus S 4G issues accessing \sdcard\ no bootup

Hello, before I call Samsung in hopes they might give me a RMA, I need help.
I had unlocked the bootloader in the past and had recently installed the IMM26D official stock rom that was not rooted. This worked fine for a month or so then yesterday the phone would not boot up anymore, just sitting at "GOOGLE' across the screen with the unlocked padlock on the bottom. So here is what I have tried ;
I was able to load CWM on it, but once in there, I could not do anything that pointed to the sdcard (mount, mount usb, format, wipe and erase). The minute I tried this, the log would show "Error mounting \sdcard\".
I then tried ODIN to see if I could reload the IMM26D, It would start and get only about 5% of the way and just stop for eternity. I tried the same cable I used before when this worked, and a different one.
And at the last step (Stupidly), I tried doing a fastboot oem lock and it locked it. Now when I go back in and do a fastboot oem unlock, the options come up on the screen and when choosing Yes to unlock, the phone just locks up.
Could this be a corrupted or damaged SDcard in the phone (now I wish it wasn't internal and rather a external one) ?
Is there ANYTHING I can do at this point? Is there a .PIT file specific for this phone that I can try loading with ODIN ?
I would love to somehow load the "stock" recovery back on it but since I can't unlock the bootloader, seems that idea is toast. It would be a lot easier to take to Sprint or send to Samsung if it didn't have CMW on it.
Sorry for the long post, but thanks in advance ..

what happened with this issue? Was it resolved, did you have it swapped with another phone?
Sent from my Nexus S 4G using Tapatalk 2

Ended up calling Samsung and sending it in, luckily it was still under warranty. Looks like they fixed it and waiting for it to return. There was nothing I could do on my end at the time, it was a corrupted internal SD card.

[Q] I just updated and now my shield is frozen on the boot splash

I never rooted or unlocked the bootloader, not sure what's up. I had a 32gb SD card in it if that matters.
Anyone know what I could try and do?

Try to flash stock from fastboot, maybe something on your system has been corrupted... Are you rooted or bootloader unlocked?

thegunrun said:
I never rooted or unlocked the bootloader, not sure what's up. I had a 32gb SD card in it if that matters.
Anyone know what I could try and do?
Click to expand...
Click to collapse
You can try to recover to the recovery image.
https://developer.nvidia.com/sites/default/files/akamai/mobile/shield/HowTo-Flash-Recovery-Image.txt
You can find the boot, system and recovery .img's here
http://forum.xda-developers.com/showthread.php?t=2388870
The blob and tegra114-roth here
https://drive.google.com/?authuser=0#folders/0B7j6Imwr_sirRnl5MFRRR2sxRWM
I would upload the userdata.img, but it's too big for me to upload, and I don't think it is needed...

Guys, the OP mentioned that he has not unlocked/rooted his device, so he cannot flash the recovery image.
That should definitely not happen on an unlocked device. Can you at least see the splash animation? Things to try (in that order):
1) On the boot splash animation, connect SHIELD to your PC and try to run "adb logcat" to see if you can see what is crashing. Attach the log here if you can get it.
2) If you cannot use adb, reboot your SHIELD while holding the back and home buttons. This will bring you to the bootloader menu. Then connect to your PC and try to "fastboot erase userdata" and "fastboot erase cache" before doing "fastboot reboot". This will remove all your user data, so your SHIELD should boot again correctly provided the OTA went without any issue. You might not like the idea of losing your user data though.
3) Contact NVIDIA. You have not unlocked your SHIELD, just did a regular OTA. This is covered by the warranty so they should be able to help you.

Gnurou said:
....That should definitely not happen on an unlocked device. Can you at least see the splash animation? Things to try (in that order):....
Click to expand...
Click to collapse
Fixed that line for you.
If the device is locked getting Nvidia to fix the software should not be a problem.

I had the same problem. NVidia swapped out my Shield with a retail refurbished unit.

Happened to me but I shut it down using the nvidia button and let it sit for a few minutes and it booted.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.

i have got the same problem
its impossible to boot in 4.3. the only few times i got it, it tooks 10 ton 15 minutes
i go back to 4.2 and i had the same problem. the only way to get the shield back to normal is to format all (system, data, etc..) through cwmr
when i trie to update to 4.3 trought ota, i got the same problem and i have to repeat the proccess again to come back to 4.2
in 4.2 boots ok, and everything works, but i cant update
any ideas?

My boot-up problem seemed to have been caused by my 64GB SanDisk MicroSD card. When I pulled it out to transfer it to my replacement Shield, the original came up. Try pulling out your SD card before powering on if you are still having trouble.

jdsemler said:
My boot-up problem seemed to have been caused by my 64GB SanDisk MicroSD card. When I pulled it out to transfer it to my replacement Shield, the original came up. Try pulling out your SD card before powering on if you are still having trouble.
Click to expand...
Click to collapse
hi, i tried to boot without the sd and i get the same result
stock in boot logo
i thing the problem its something related with the ota update an my boot.img
someone has access to boot, system and recovery img from update 63?
maybe if i install from bootloader i get something
thanks in advance

If you power on holding back and home, you will boot into a menu. If you go into Recovery, do you get any options? On mine, it would say "No Command" and be stuck there. If yours also says "No Command", you can't really load anything using recovery.
You should consider going here. You'll have to either login or create a login, but after that, you can submit your problem to NVidia. That's what I did, and they shipped me a new unit overnight with a prepaid label to send my unit back.

Hi, Thanks for your answer. Im able to update the shield throught fastboot. This is hoy i can downgrade from 4.3 to 4.2.
Moreover ,i cant get a new unit, cause i live in spain, (and i already unlock my bootloader)

cg_gm said:
Hi, Thanks for your answer. Im able to update the shield throught fastboot. This is hoy i can downgrade from 4.3 to 4.2.
Moreover ,i cant get a new unit, cause i live in spain, (and i already unlock my bootloader)
Click to expand...
Click to collapse
good news!!! last update (64) solve the problem. now im in 4.3 and all is working ok
thanks for your help, hope thath nvidia dont mess up with the updates again

Pixel stuck in bootloader loop and unable to boot in recovery

As per title, it just happened while I was using the phone while charging. Trying my luck as I'm not in the country(Australia) that I bought my Pixel from. Grateful for any suggestion that the sub can provide. Non rooted stock rom

You're only able to get into bootloader and that's all? I would suggest unlock the bootloader, a factory reset will follow. Try rebooting after that. If that doesn't work, at least your unlocked and you can fastboot boot twrp and reset that way or flash a stock rom. If nothing works you "may" have a defective device. I'm no expert but I would try those things first.

Yes only bootloader. What you have mentioned do not require recovery mode right ? Cos I can't boot into it. Thanks for your reply

k.s.deviate said:
You're only able to get into bootloader and that's all? I would suggest unlock the bootloader, a factory reset will follow. Try rebooting after that. If that doesn't work, at least your unlocked and you can fastboot boot twrp and reset that way or flash a stock rom. If nothing works you "may" have a defective device. I'm no expert but I would try those things first.
Click to expand...
Click to collapse
The bootloader would have needed to have been unlocked already.

indifferent1 said:
The bootloader would have needed to have been unlocked already.
Click to expand...
Click to collapse
no it doesnt, I suggested unlocking the bootloader first, that way it factory resets. this might fix the problem, if not its unlocked so he can flash the factory image.

Bump? I'm having this problem as well.

Same here. How would we unlock the bootloader of the phone when it's stuck in either a Google screen the reboots over and over again, or the bootloader interface (that won't load recovery)? Sorry about the noob question, but I'm not sure how to do it.

graymoment said:
Same here. How would we unlock the bootloader of the phone when it's stuck in either a Google screen the reboots over and over again, or the bootloader interface (that won't load recovery)? Sorry about the noob question, but I'm not sure how to do it.
Click to expand...
Click to collapse
I'm having the same issue. My wife's Pixel entered a continuous boot loop today. It only loads the white screen that says "Google." I can enter the bootloader, but when I select "recover," it goes back to the bootloop. As far as I know, she is on Android 8.1, debugging mode is off and the phone is 100% factory.
If anyone has solved this issue, it would be greatly appreciated!
Thanks

has anyone figured this out?? this happened to me today, i was using the phone, the poof it restarted itself and stayed in a boot loop. i can get into the recovery, i tried wipe/factory reset. any suggestions? google told me i need to send it to whatever company to get it fixed or get a new phone. verizon told me to go through insurance. insurance told me to go through verizon because i may be able to use the extended warranty. went back to verizon but they wont take it because the screen cracked a year ago. its not a deep crack and it didnt affect the phone at all, never had an issue. so now i go back to assurion and now they need an affidavit about my screen being cracked. im at a loss.... i havent rooted a phone since my droid x, then s3 days. so im essentially new again!

Same issue here. Phone starts on the bootloader (shows device is locked), but won't start recovery or boot any further.
I'm guessing it's time for a new phone? I hadn't taken the Android 10 update yet, so it was running Pie.
[edit] it's dead - won't let me unlock bootloader or switch boot slots

thedosbox said:
Same issue here. Phone starts on the bootloader (shows device is locked), but won't start recovery or boot any further.
I'm guessing it's time for a new phone? I hadn't taken the Android 10 update yet, so it was running Pie.
[edit] it's dead - won't let me unlock bootloader or switch boot slots
Click to expand...
Click to collapse
I had the same thing happen yesterday (not long after the Android 10 update). I was finally able to get it to boot after multiple tries and it stayed up long enough for me to enable "OEM unlocking" in Developer options. Now at least I have the option of unlocking the bootloader and re-flashing the OS with an image directly from Google.
Has anyone been able to get past this problem by reflashing the image? I suspect the underlying problem is some kind of hardware fault with eMMC, DDR, or the SOC itself.
One other interesting behavior I noticed is that the only way to shut it down and stop the bootloop is to select the "Power off" option in the bootloader menu. However, if I plug it in to charge when it is fully powered "off", it will start up the bootloop again.

Same sitution here. A couple of days after installaing it suddenly went inte a G-bootloop frenzy.
Erratic though, sometimes I could boot up (2-3/40 boots) but then it froze and started again.
Also Recovery and Safemode is very hard to get into.
Got in once or twice out of 100 boots, Bootloader Fastboot is generally reachable though.
It exhausted the battery and now I'm holding off trying to interfere, until I get more info off the net.