Sometimes my Nexus S (i9020) hangs on Google logo when booting. This happens let's say 5 of 10 times. However, once it's booted it works just fine.
I have been investigating what's causing it and I have a guess that it's because of internal SD card. But I'm not sure what exactly is wrong with it as mentioned everything works just fine if phone boots.
Why I think it's SD problem? I have tried to install another ROM using CW and when I chose to install zip from SD card, CW just reported that "Can't mount SD card" (something like this). I did couple of restarts and then it worked fine. So it seems to be that phone sometimes cannot mount or recogzine(?) SD card and that's why it hangs on Google logo.
Do you have any ideas what could be wrong with SD? It shouldn't be a contact problem as it works without any problems when phone is finally booted.
I have also tried to format/partition card, but it didn't help.
Someone please correct me if I'm wrong, but I don't think the Nexus S has any SD card. So that would make sense that it cannot mount what doesn't exist.
It has 16GB NAND memory which is basically the same thing as SD card. NAND is a technology used for USB drives, memory cards etc.
And regarding mounting, it says "can't mount" only like 5 of 10 times, other 5 times it works (mounts) perfectly.
xtasy55 said:
Sometimes my Nexus S (i9020) hangs on Google logo when booting. This happens let's say 5 of 10 times. However, once it's booted it works just fine.
I have been investigating what's causing it and I have a guess that it's because of internal SD card. But I'm not sure what exactly is wrong with it as mentioned everything works just fine if phone boots.
Why I think it's SD problem? I have tried to install another ROM using CW and when I chose to install zip from SD card, CW just reported that "Can't mount SD card" (something like this). I did couple of restarts and then it worked fine. So it seems to be that phone sometimes cannot mount or recogzine(?) SD card and that's why it hangs on Google logo.
Do you have any ideas what could be wrong with SD? It shouldn't be a contact problem as it works without any problems when phone is finally booted.
I have also tried to format/partition card, but it didn't help.
Click to expand...
Click to collapse
I have the same problem too. I've, yet, to find out the real cause. I want a warranty replacement unit but I know they are going to say that I'm OOW because it's unlocked.
You have to send it in.
I had this problem last week, after hours of searching the net, I found other people with this problem. Its nothing you can fix your self unless you can take apart your phone and replace the bad part. It really sucks to be without the nexus, but they got mine repaired, I am just waiting for them to send it back. Its says they had to "replace a bad component" on the repair ticket. Good luck.
---------- Post added at 03:56 PM ---------- Previous post was at 03:55 PM ----------
LordPhong said:
I have the same problem too. I've, yet, to find out the real cause. I want a warranty replacement unit but I know they are going to say that I'm OOW because it's unlocked.
Click to expand...
Click to collapse
Lock your boot loader before you send it in, very easy to do via ADB.
smoka206 said:
I had this problem last week, after hours of searching the net, I found other people with this problem. Its nothing you can fix your self unless you can take apart your phone and replace the bad part. It really sucks to be without the nexus, but they got mine repaired, I am just waiting for them to send it back. Its says they had to "replace a bad component" on the repair ticket. Good luck.
---------- Post added at 03:56 PM ---------- Previous post was at 03:55 PM ----------
Lock your boot loader before you send it in, very easy to do via ADB.
Click to expand...
Click to collapse
So, there's no flag somewhere saying that you unlocked your device? What did you tell them the problem was? Mine does it too often.
I'm seeing the same issue on my phone. It sounds like its SD card related but it has to be something with the connection since it only happens during boot time. Correct me if I'm wrong but android doesn't actually need SD card to boot so why would it have an issue. That's what makes me think its something else.
---------- Post added at 04:04 PM ---------- Previous post was at 04:01 PM ----------
LordPhong said:
So, there's no flag somewhere saying that you unlocked your device? What did you tell them the problem was? Mine does it too often.
Click to expand...
Click to collapse
If you can factory restore the phone and then lock it they have no way of knowing you had it rooted. Just make sure your SD storage is cleaned too.
Just wondering if anyone else had this issue and what they did to fix it.
Hi!
If you plan to go for repair your device , then it's no need relocked your bootloader . During the warranty period they will repair it for free.....
->just take a look at this : http://forum.xda-developers.com/showthread.php?t=1360146
.....to understand read all ....and now at this time my phone work very well
surdu_petru said:
If you plan to go for repair your device , then it's no need relocked your bootloader . During the warranty period they will repair it for free.....
->just take a look at this : http://forum.xda-developers.com/showthread.php?t=1360146
.....to understand read all ....and now at this time my phone work very well
Click to expand...
Click to collapse
Thanks but I don't think yours is a same issue. Mine is just stuck on the Google logo. However turning it off and plugging in the charger and there powering after the charge display usually fixes it.
Right now I'm up for more than 3 days without rebooting but I'm afraid that eventually it will go bad and not be able to boot properly.
Related
Getting a screen saying PwrReason: PWR_KEY_PRESS
Unlocked, was running Cyanogen7, wanted to go back to PiCrust. Was wiping battery stats, it took me out of the menu. I accidently went into some other menu and it formatted the phone... Partitioning or something?
Would like to get back to a working phone... I can get into RSD protocol, Fastboot. Recovery spits out an error.
Getting myself the fastboot/RSDLite/drivers again...
Any other guidance would be greatly appreciated...
1) Download CWM, either ROM Manager one (http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-olympus.img) or the romracer one on XDA, either will work
2) Download a ROM
3) boot in fastboot, fastboot flash recovery [the recovery you downloaded]
4) boot in recovery, wipe data and flash a ROM
w00t. almost my plan. I don't have an external card. So already got romracer flashed, but, i think, i'll have to fastboot the 4.5.91 stock rom....so it can format and setup my internal SD card. Then go to picrust. Shame I lost my Pi and Cy7 backups....
edit:
Whew. I thought i had lost everything on the internal sdcard. Once i got romracers cWM back on. and after it failed to flash 4.5.91, i looked around in CWM and was able to see my internal SDCard. Restored my Cy7 for now. My touchscreen was off, but I had backed up my PDS partition a long time ago, flashed that and it was working again.
Now the only "problem" is, on boot, I dont get the Motorola Logo. I instead get a command line style interface. It autoboots to OS in 5s, unless I pick something from the list (RSD,Fastboot,etcetc) Not a HUGE deal, but I hate seeing POSTs on my PCs, so I'd like to get that logo back..or if possible a custom logo?? Any ideas on that?
I have exactly the same problem, could you repair it?? I need to take my phone to de RMA and I have this, I dont know what to do. If you ydgmms or somebody else could give me some help it would be great.
Edit:I could just have installed a recovery but still getting the black screen with the letters.
I leave a screenshot.
santix93 said:
I have exactly the same problem, could you repair it?? I need to take my phone to de RMA and I have this, I dont know what to do. If you ydgmms or somebody else could give me some help it would be great.
Edit:I could just have installed a recovery but still getting the black screen with the letters.
I leave a screenshot.
Click to expand...
Click to collapse
I have the same problem!!!!!!
I was wiping ?? data...i think i entered a wrong selection...pheraps we have partitioned the internal sd......what can we do????
msin84 said:
I have the same problem!!!!!!
I was wiping ?? data...i think i entered a wrong selection...pheraps we have partitioned the internal sd......what can we do????
Click to expand...
Click to collapse
That's exactly what you did..
Not to worry, here you go! http://forum.xda-developers.com/showthread.php?t=1131649
;-)
P. S. I've "fried" my phone a couple of times since I got it, this one though I thought it was done. Took me 7 hours to figure out / repair. Good luck, it's fairly straight forward with the instructions in the thread.
And i also have this problem....http://forum.xda-developers.com/showthread.php?t=1212851
Ok i accidentally partitioned the internal memory
It looks like i need to restore the PSD (what is...??)...but of course i've not backed it up....!!!
Is there anyone that can help me.....??????????
Now i go to sleep....after 2 hours with deep troubles...!
Do you read what it says on posts before yours or do you just type your question & come back hoping for answers..?
msin84 said:
And i also have this problem....http://forum.xda-developers.com/showthread.php?t=1212851
Ok i accidentally partitioned the internal memory
It looks like i need to restore the PSD (what is...??)...but of course i've not backed it up....!!!
Is there anyone that can help me.....??????????
Now i go to sleep....after 2 hours with deep troubles...!
Click to expand...
Click to collapse
Ok...after a lot of pain i was able to solve the problem by flashing the engineering PSD!!!
Now when i power on the phone i also read the hw revision and made date....but i was not able to show the motorola logo...damn....
---------- Post added at 11:15 PM ---------- Previous post was at 10:50 PM ----------
Vangelis13 said:
Do you read what it says on posts before yours or do you just type your question & come back hoping for answers..?
Click to expand...
Click to collapse
Sorry, i was very confused before...full panic (i was thinking to have a 500€ brick)!
THANKS A LOT FOR YOUR 100% WORKING SOLUTION!
Yes i read, it's the same post!
I read through the forum other users experienced both the problems togheter (post on boot and screen alignment issue).
Now i'm not able to set the moto logo instead of the post...!
msin84 said:
Ok...after a lot of pain i was able to solve the problem by flashing the engineering PSD!!!
Now when i power on the phone i also read the hw revision and made date....but i was not able to show the motorola logo...damn....
---------- Post added at 11:15 PM ---------- Previous post was at 10:50 PM ----------
Sorry, i was very confused before...full panic (i was thinking to have a 500€ brick)!
THANKS A LOT FOR YOUR 100% WORKING SOLUTION!
Yes i read, it's the same post!
I read through the forum other users experienced both the problems togheter (post on boot and screen alignment issue).
Now i'm not able to set the moto logo instead of the post...!
Click to expand...
Click to collapse
Were you able to find a fix to restore the red moto logo?
Thanks,
Bruno
Hi! I have Nexus 7 and I've used it for 4 months, it's on warranty. It started to lag couple of days and I rebooted it sometimes, but on the one reboot it didn't start Android and stucked on X logo, after another reboot it started a bootloop from X logo to Google logo on and on. After another reboot it stucks only on Google screen. I've tried to wipe data and cache partition, but it also stucks. I also tried Nexus 7 Toolkit, but it gets an error on unlock bootloader. I also tried to do it via Windows' cmd.exe with fastboot oem unlock, the same problem. I can't find any working method. Please, help.
You can use the toolkit to revert back to set stock rom. Download the stock .img from the toolkit and perform the flash. Make sure you boot to the bootloader to do this.
Entering the command fastboot oem unlock on a unlocked device will not do anything if the bootloader is already unlocked.
Sent from my Nexus 4 using Tapatalk 2
scream4cheese said:
You can use the toolkit to revert back to set stock rom. Download the stock .img from the toolkit and perform the flash. Make sure you boot to the bootloader to do this.
Entering the command fastboot oem unlock on a unlocked device will not do anything if the bootloader is already unlocked.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I'm having the EXACT same problem. Also had my N7 for about 4 mos. I'm going to try the above suggestion also. Please post your results and I'll do the same.
---------- Post added at 10:46 PM ---------- Previous post was at 10:42 PM ----------
scream4cheese said:
You can use the toolkit to revert back to set stock rom. Download the stock .img from the toolkit and perform the flash. Make sure you boot to the bootloader to do this.
Entering the command fastboot oem unlock on a unlocked device will not do anything if the bootloader is already unlocked.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
If I'm already unlocked (not rooted), what steps should I follow? I'm new to all this and, although I've rooted a phone once before, I barely remember what I did back then. I don't even know what you mean by "perform the flash." Can you provide some more specific directions? I have the toolkit downloaded. Thanks!
---------- Post added at 11:34 PM ---------- Previous post was at 10:46 PM ----------
Ok - figuring this out slowly. Can someone tell me where in my folders I can find my bootloader file?
ctychick said:
I'm having the EXACT same problem. Also had my N7 for about 4 mos. I'm going to try the above suggestion also. Please post your results and I'll do the same.
---------- Post added at 10:46 PM ---------- Previous post was at 10:42 PM ----------
If I'm already unlocked (not rooted), what steps should I follow? I'm new to all this and, although I've rooted a phone once before, I barely remember what I did back then. I don't even know what you mean by "perform the flash." Can you provide some more specific directions? I have the toolkit downloaded. Thanks!
---------- Post added at 11:34 PM ---------- Previous post was at 10:46 PM ----------
Ok - figuring this out slowly. Can someone tell me where in my folders I can find my bootloader file?
Click to expand...
Click to collapse
You can't find the bootloader file. It's embedded within the system. Unless you have the flashable zip then you can use that. Why do you need it anyways?
ten char .
Bad block on nand flash
Sent from my ST18i using xda app-developers app
Hi mate*
Dunno if you got things sorted but I had the same problem last week. I'd let the unit run flat and stay flat for a coupla days and bootloop is the price I paid. So, I call Asus who inform me that it's under warranty and to send it in for repair. Fair dos to them that's good service but I don't wanna be without my Nexus for 2 weeks so I have another play with it having previously had no joy resetting it using power and vol up/down etc.*
I'd managed to get some charge into it by waiting for the bootloop to turn it on and then manually turning it off. Not sure how quickly yours restarts but I had lockscreen for 10 seconds or so before restarting the cycle. That said it wasn't long enough to reset to factory settings but it was long enough to turn off wifi. Dunno why I tried this, sheer desperation probably but after a restart with wifi off and a full battery I was able to access my stuff and back it up to pc.*
I then was able to perform a factory reset and set the device up again, including wifi and apps. Since then it's been good as gold (but I won't let it drop below 20% charge!) but as there's only 4 months of warranty left Asus are gonna let me send it in to have a new motherboard anyway - might as well as its been wiped anyhow. The last thing I want if for it to [email protected]#k up a week after the warranty's ran out.*
I hope this helps you or other searching for a fix bud, let us know *
Lolpoppa said:
Hi mate*
Dunno if you got things sorted but I had the same problem last week. I'd let the unit run flat and stay flat for a coupla days and bootloop is the price I paid. So, I call Asus who inform me that it's under warranty and to send it in for repair. Fair dos to them that's good service but I don't wanna be without my Nexus for 2 weeks so I have another play with it having previously had no joy resetting it using power and vol up/down etc.*
I'd managed to get some charge into it by waiting for the bootloop to turn it on and then manually turning it off. Not sure how quickly yours restarts but I had lockscreen for 10 seconds or so before restarting the cycle. That said it wasn't long enough to reset to factory settings but it was long enough to turn off wifi. Dunno why I tried this, sheer desperation probably but after a restart with wifi off and a full battery I was able to access my stuff and back it up to pc.*
I then was able to perform a factory reset and set the device up again, including wifi and apps. Since then it's been good as gold (but I won't let it drop below 20% charge!) but as there's only 4 months of warranty left Asus are gonna let me send it in to have a new motherboard anyway - might as well as its been wiped anyhow. The last thing I want if for it to [email protected]#k up a week after the warranty's ran out.*
I hope this helps you or other searching for a fix bud, let us know *
Click to expand...
Click to collapse
I tries this but it doesnt seem to work for me, i had the same issue as you and now it seems as though it is bricked :/ i tried doing the steps you mentioned but it didnt work for me. i get to the home screen for about 10 secs till it restarts. i want to save my music/pictures and i dont know what to do (i never enabled developer options either) any ideas?
I know this topic is not popular and most people may skip over it but please read. I am NO expert when it comes to this so if anybody can help out it would be most appreciated. I have a T-mobile My touch 4g( NOT the slide version) running ginger bread 2.3.4. I wanted to play a game called "Clash of clans" but it says i need firmware 4.1 or higher. I was bummed because T mobile stopped making upgrades for this phone a long time ago. I saw online from different threads and videos that I need to downgrade the firmware and go back to fre3vo 2.2. OK i'm fine with that. I had no Idea how adb worked so I saw a post on xda this site how to use it for dummies. I now know how to. I followed ALL steps from http://forum.xda-developers.com/showthread.php?t=1178912 on how I should go about this process. Everything went smooth up until the "Downgrading steps." I finally learned how to place the zip file named "PD15IMG.zip" in the root of sd card. Ok i had it. I also followed the manual downgrade routine. The phone went into boot-loader mode. The phone scanned the file and that took maybe 2 min before it asked me to update. I hit yes to update. I waited for the phone to update then it shut off. I guess the phone restarted to a black screen. The only thing I could see was the top portion bar where the battery and time info is. The rest of the screen was completely black. I took the battery out thinking that maybe the phone just needed to be restarted and this was the worst thing to happen. I turned the phone on and now the screen will NOT boot past the "t mobile mytouch 4g logo screen. I have no idea what to do from here. I went to go back to clockworkmod to see if i could repeat the process. The package scans like before then it asks me to update then I said yes. This is where the phone says its "updating" in pink letter on the side but NO progress is being made. Nothing happens and the phone seems unresponsive. I took the battery out and went back to clockworkmod. I tried to hit 'Factory Reset' but it just stays highlighted on factory reset and it wont move up and down. Nothing works. I took the battery out and re tried clockworkmod. I tried hitting recovery and then a "phone with a "green arrow" below shows up then the screen goes black and the phone vibrates 7 times then nothing else happens. I can no longer access the phone on my computer. Normally when I plugged it in the F: drive folder came up indicating I could change contents in the Sd card. I heard that you can change the setting using terminal and when i try typing "adb shell" it said it cannot find my phone and that my phone inst connected although it is connected to my computer. I have windows 7 Toshiba satellite so nothing is bad on the PC. Battery, cable, everything is fine no defects with the phone.
Also
A little information when ClockWorkMod is up. This is exactly what it says and this is exactly the color as it shows.
GLACIER PUT SHIP S-ON
HBOOT-0.89.0005
MICROP-0429
RADIO-26.11.04.03_M
eMMC-boot
Apr 14 2011, 13;18;22
HBOOT
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
Since I can no longer access the phone on my pc I took the micro sim sd out and placed it in my samsung galaxy player 3.6 From there I can at least change what goes into the Sd card. I have searched countless hours and nothing else comes up. I CANNOT go back to the normal mode my phone used to be. I just freezes past mytouch4g screen. Please help anybody. I want to downgrade ginger bread 2.3.4 to fre3vo 2.2 so i can root and upgrade to jelly bean or something higher to play clash of clans since this phone wasn't compatable. Please somebody help. Can I ever use my phone again? Does this mean it's bricked? I'm an apple user so I have little experience with android. Somebody anybody help me out?
Here are a few links i used in the process
http://lifehacker.com/5853519/how-do-i-fix-my-bricked-android-phone
http://forum.xda-developers.com/showthread.php?t=863899
help me please
Bolt34 said:
I know this topic is not popular and most people may skip over it but please read. I am NO expert when it comes to this so if anybody can help out it would be most appreciated. I have a T-mobile My touch 4g( NOT the slide version) running ginger bread 2.3.4. I wanted to play a game called "Clash of clans" but it says i need firmware 4.1 or higher. I was bummed because T mobile stopped making upgrades for this phone a long time ago. I saw online from different threads and videos that I need to downgrade the firmware and go back to fre3vo 2.2. OK i'm fine with that. I had no Idea how adb worked so I saw a post on xda this site how to use it for dummies. I now know how to. I followed ALL steps from http://forum.xda-developers.com/showthread.php?t=1178912 on how I should go about this process. Everything went smooth up until the "Downgrading steps." I finally learned how to place the zip file named "PD15IMG.zip" in the root of sd card. Ok i had it. I also followed the manual downgrade routine. The phone went into boot-loader mode. The phone scanned the file and that took maybe 2 min before it asked me to update. I hit yes to update. I waited for the phone to update then it shut off. I guess the phone restarted to a black screen. The only thing I could see was the top portion bar where the battery and time info is. The rest of the screen was completely black. I took the battery out thinking that maybe the phone just needed to be restarted and this was the worst thing to happen. I turned the phone on and now the screen will NOT boot past the "t mobile mytouch 4g logo screen. I have no idea what to do from here. I went to go back to clockworkmod to see if i could repeat the process. The package scans like before then it asks me to update then I said yes. This is where the phone says its "updating" in pink letter on the side but NO progress is being made. Nothing happens and the phone seems unresponsive. I took the battery out and went back to clockworkmod. I tried to hit 'Factory Reset' but it just stays highlighted on factory reset and it wont move up and down. Nothing works. I took the battery out and re tried clockworkmod. I tried hitting recovery and then a "phone with a "green arrow" below shows up then the screen goes black and the phone vibrates 7 times then nothing else happens. I can no longer access the phone on my computer. Normally when I plugged it in the F: drive folder came up indicating I could change contents in the Sd card. I heard that you can change the setting using terminal and when i try typing "adb shell" it said it cannot find my phone and that my phone inst connected although it is connected to my computer. I have windows 7 Toshiba satellite so nothing is bad on the PC. Battery, cable, everything is fine no defects with the phone.
Also
A little information when ClockWorkMod is up. This is exactly what it says and this is exactly the color as it shows.
GLACIER PUT SHIP S-ON
HBOOT-0.89.0005
MICROP-0429
RADIO-26.11.04.03_M
eMMC-boot
Apr 14 2011, 13;18;22
HBOOT
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
Since I can no longer access the phone on my pc I took the micro sim sd out and placed it in my samsung galaxy player 3.6 From there I can at least change what goes into the Sd card. I have searched countless hours and nothing else comes up. I CANNOT go back to the normal mode my phone used to be. I just freezes past mytouch4g screen. Please help anybody. I want to downgrade ginger bread 2.3.4 to fre3vo 2.2 so i can root and upgrade to jelly bean or something higher to play clash of clans since this phone wasn't compatable. Please somebody help. Can I ever use my phone again? Does this mean it's bricked? I'm an apple user so I have little experience with android. Somebody anybody help me out?
Here are a few links i used in the process
http://lifehacker.com/5853519/how-do-i-fix-my-bricked-android-phone
http://forum.xda-developers.com/showthread.php?t=863899
help me please
Click to expand...
Click to collapse
Bro calm down. I've been though panic attacks like this too lol
Open clockworkmod
To select or scroll use the TRACKPAD
Put a rom on your sdcard, find any in the resource bible in the development section
Do a factory reset and flash that rom
And yay,
N_otori0us_ said:
Bro calm down. I've been though panic attacks like this too lol
Open clockworkmod
To select or scroll use the TRACKPAD
Put a rom on your sdcard, find any in the resource bible in the development section
Do a factory reset and flash that rom
And yay,
Click to expand...
Click to collapse
-It won't allow me to use the track pad I can only use the volume up and down buttons to scroll. What rom should I put on my sd card? If you have a link or something that would be great.. Also when I try to factory reset the phone just freezes. I don't know what to do.
any rom
That screen you posted information from is called H-BOOT, it's like the factory boot loader. Clockwork MOD will show up after that but from what I'm gathering you didn't even install that in the first place. In H-BOOT you can only use the volume buttons and the power button to select so that is all normal.
So you downloaded the stock ROM and in the process of downgrading got stuck. If the SD card still works in other devices do you still have PD15IMG.zip on the card?
Also did you make sure to download the proper drivers for ADB and also for your phone? The ADB ones you should be able to find on this forum and the HTC ones you could get directly from you carriers website, and most likely somewhere on this forum. It will be up to you to really read, read, read, but I don't mind point you in the right direction.
You will find links of information with in this post http://forum.xda-developers.com/showthread.php?t=2288189
I would read through s-off / s-on and true rooting. I feel like you're missing drivers and basically just have nothing installed on the phone. So you aren't bricked, you just need to do more research. Bricked is the phone shows no screen at all and won't even turn on. I've done it once, and you are luckily not there. I believe the first time I rooted this phone I had the same problem of "is it installing...did I miss something...eff it, battery pull...oh no!"
Also select the recovery option and let me know what happens, if it advances you to the next screen that is what is actually Clockwork Mod recovery. If you actually have that then we are even better. I'll keep checking back tonight for ya.
tonyMEGAphone said:
That screen you posted information from is called H-BOOT, it's like the factory boot loader. Clockwork MOD will show up after that but from what I'm gathering you didn't even install that in the first place. In H-BOOT you can only use the volume buttons and the power button to select so that is all normal.
So you downloaded the stock ROM and in the process of downgrading got stuck. If the SD card still works in other devices do you still have PD15IMG.zip on the card?
Also did you make sure to download the proper drivers for ADB and also for your phone? The ADB ones you should be able to find on this forum and the HTC ones you could get directly from you carriers website, and most likely somewhere on this forum. It will be up to you to really read, read, read, but I don't mind point you in the right direction.
You will find links of information with in this post http://forum.xda-developers.com/showthread.php?t=2288189
I would read through s-off / s-on and true rooting. I feel like you're missing drivers and basically just have nothing installed on the phone. So you aren't bricked, you just need to do more research. Bricked is the phone shows no screen at all and won't even turn on. I've done it once, and you are luckily not there. I believe the first time I rooted this phone I had the same problem of "is it installing...did I miss something...eff it, battery pull...oh no!"
Also select the recovery option and let me know what happens, if it advances you to the next screen that is what is actually Clockwork Mod recovery. If you actually have that then we are even better. I'll keep checking back tonight for ya.
Click to expand...
Click to collapse
I appreciate the comment and help. Sorry i didn't know that I wasnt in colckworkmod just yet. Im new to android as I am an apple person. Some of the links i've found on this site are outdated or used by sites that are no longer running. If possible could you help direct me to the appropriate link so that I can download the correct rom? thank you so much!
first
First in your Hboot screen scroll with the volume button to "Recovery" and let me know what happens.
---------- Post added at 04:36 PM ---------- Previous post was at 04:29 PM ----------
Also did you go to tmobile and install the HTC drivers under the support menu for your phone?
These are all must I read through your post and also am currently reading the link you said you followed but if you didn't do all these prerequisite work it's no wonder why you froze up.
---------- Post added at 04:52 PM ---------- Previous post was at 04:36 PM ----------
I see, you said the Recovery goes black and vibrates 7 times. Something didn't install right. At this stage of working with your phone you won't see the F: drive pop up until we fully get you downgraded and get the ROM operational.
See what you can do with this link. Follow it and even redownload items from it. It's more updated then the one you used.
http://forum.xda-developers.com/showthread.php?t=928370
And let me know how it goes, and if I helped click the little thanks button~ like i said before I'll have time tonight to go back and forth and try and make this work. You just need to read your face off. HTC's can be tricky but at least it's not MOTOROLA...
---------- Post added at 05:11 PM ---------- Previous post was at 04:52 PM ----------
Found another thread too
http://forum.xda-developers.com/showthread.php?t=1538859&page=6
Page 4 has a link to some PD15IMG.zip files that could work, Page 5 has someone confirming which one works and then Page 6 this guy posts a video on how he fixed his.
Also make sure the phone is charged a low battery can cause boot loops, try and format the SD card and only have PD15IMG.zip be the only file.
lol I missed the fact that he's still in bootloader.
Bro just try flashing that stock img again
tonyMEGAphone said:
First in your Hboot screen scroll with the volume button to "Recovery" and let me know what happens.
---------- Post added at 04:36 PM ---------- Previous post was at 04:29 PM ----------
Also did you go to tmobile and install the HTC drivers under the support menu for your phone?
These are all must I read through your post and also am currently reading the link you said you followed but if you didn't do all these prerequisite work it's no wonder why you froze up.
---------- Post added at 04:52 PM ---------- Previous post was at 04:36 PM ----------
I see, you said the Recovery goes black and vibrates 7 times. Something didn't install right. At this stage of working with your phone you won't see the F: drive pop up until we fully get you downgraded and get the ROM operational.
See what you can do with this link. Follow it and even redownload items from it. It's more updated then the one you used.
http://forum.xda-developers.com/showthread.php?t=928370
And let me know how it goes, and if I helped click the little thanks button~ like i said before I'll have time tonight to go back and forth and try and make this work. You just need to read your face off. HTC's can be tricky but at least it's not MOTOROLA...
---------- Post added at 05:11 PM ---------- Previous post was at 04:52 PM ----------
Found another thread too
http://forum.xda-developers.com/showthread.php?t=1538859&page=6
Page 4 has a link to some PD15IMG.zip files that could work, Page 5 has someone confirming which one works and then Page 6 this guy posts a video on how he fixed his.
Also make sure the phone is charged a low battery can cause boot loops, try and format the SD card and only have PD15IMG.zip be the only file.
Click to expand...
Click to collapse
Ok Im going to try this now. Just hold on in there for me.
Lets see if this works
tonyMEGAphone said:
First in your Hboot screen scroll with the volume button to "Recovery" and let me know what happens.
---------- Post added at 04:36 PM ---------- Previous post was at 04:29 PM ----------
Also did you go to tmobile and install the HTC drivers under the support menu for your phone?
These are all must I read through your post and also am currently reading the link you said you followed but if you didn't do all these prerequisite work it's no wonder why you froze up.
---------- Post added at 04:52 PM ---------- Previous post was at 04:36 PM ----------
I see, you said the Recovery goes black and vibrates 7 times. Something didn't install right. At this stage of working with your phone you won't see the F: drive pop up until we fully get you downgraded and get the ROM operational.
See what you can do with this link. Follow it and even redownload items from it. It's more updated then the one you used.
http://forum.xda-developers.com/showthread.php?t=928370
And let me know how it goes, and if I helped click the little thanks button~ like i said before I'll have time tonight to go back and forth and try and make this work. You just need to read your face off. HTC's can be tricky but at least it's not MOTOROLA...
---------- Post added at 05:11 PM ---------- Previous post was at 04:52 PM ----------
Found another thread too
http://forum.xda-developers.com/showthread.php?t=1538859&page=6
Page 4 has a link to some PD15IMG.zip files that could work, Page 5 has someone confirming which one works and then Page 6 this guy posts a video on how he fixed his.
Also make sure the phone is charged a low battery can cause boot loops, try and format the SD card and only have PD15IMG.zip be the only file.
Click to expand...
Click to collapse
So I found a new img file and the same thing happens. It says it's updating but doesnt make any progess and it looks like its frozen. What should I do?
N_otori0us_ said:
lol I missed the fact that he's still in bootloader.
Bro just try flashing that stock img again
Click to expand...
Click to collapse
tonyMEGAphone said:
First in your Hboot screen scroll with the volume button to "Recovery" and let me know what happens.
---------- Post added at 04:36 PM ---------- Previous post was at 04:29 PM ----------
Also did you go to tmobile and install the HTC drivers under the support menu for your phone?
These are all must I read through your post and also am currently reading the link you said you followed but if you didn't do all these prerequisite work it's no wonder why you froze up.
---------- Post added at 04:52 PM ---------- Previous post was at 04:36 PM ----------
I see, you said the Recovery goes black and vibrates 7 times. Something didn't install right. At this stage of working with your phone you won't see the F: drive pop up until we fully get you downgraded and get the ROM operational.
See what you can do with this link. Follow it and even redownload items from it. It's more updated then the one you used.
http://forum.xda-developers.com/showthread.php?t=928370
And let me know how it goes, and if I helped click the little thanks button~ like i said before I'll have time tonight to go back and forth and try and make this work. You just need to read your face off. HTC's can be tricky but at least it's not MOTOROLA...
---------- Post added at 05:11 PM ---------- Previous post was at 04:52 PM ----------
Found another thread too
http://forum.xda-developers.com/showthread.php?t=1538859&page=6
Page 4 has a link to some PD15IMG.zip files that could work, Page 5 has someone confirming which one works and then Page 6 this guy posts a video on how he fixed his.
Also make sure the phone is charged a low battery can cause boot loops, try and format the SD card and only have PD15IMG.zip be the only file.
Click to expand...
Click to collapse
When I went to recovery mode..it went to a black screen with like a green symbol and box. Then the entire screen went blank and I noticed the phone vibrated "7" times. What should I do?
Bolt34 said:
When I went to recovery mode..it went to a black screen with like a green symbol and box. Then the entire screen went blank and I noticed the phone vibrated "7" times. What should I do?
Click to expand...
Click to collapse
7 vibrates of death.
Dun dun daaaaaa.
That's a brick. I think.
Sent from my HTC Glacier
N_otori0us_ said:
7 vibrates of death.
Dun dun daaaaaa.
That's a brick. I think.
Sent from my HTC Glacier
Click to expand...
Click to collapse
So in other words...I can't fix the phone then?
N_otori0us_ said:
7 vibrates of death.
Dun dun daaaaaa.
That's a brick. I think.
Sent from my HTC Glacier
Click to expand...
Click to collapse
Couldn't that just be due to a low battery also?
---------- Post added at 05:08 PM ---------- Previous post was at 05:00 PM ----------
These people couldn't even get into the Bootloader. That's why I believe there is slightly still hope for you.
http://forum.xda-developers.com/showthread.php?t=2188591
tonyMEGAphone said:
Couldn't that just be due to a low battery also?
---------- Post added at 05:08 PM ---------- Previous post was at 05:00 PM ----------
These people couldn't even get into the Bootloader. That's why I believe there is slightly still hope for you.
http://forum.xda-developers.com/showthread.php?t=2188591
Click to expand...
Click to collapse
I made sure the phone was fully charged and I had it plugged in. That couldn't be it.
last
Bolt34 said:
I made sure the phone was fully charged and I had it plugged in. That couldn't be it.
Click to expand...
Click to collapse
My last thread attempt, and if this doesn't work. I'd say check out Craigslist for a new phone. My Glacier 4G antenna, the actual hardware, I believe is shot. So I'm going to have to down grade and run through a similar process so I can send it back for a replacement. These things can get tricky so I feel your bricked pain. I've bricked a Motorola Atrix before.
http://forum.xda-developers.com/showthread.php?t=2329869
If none of this works. It's time to put it in a shoe box and bury it in the back yard.
Hi everybody, I enjoyed my stock N4 for almost a year and today several apps started to crash suddenly, after that the device rebooted itself and never got out of the bootloop. I immediatly booted into recovery and tried to wipe the cache memory and perform a factory reset but I cannot do either of the two, the error I get is something like "can't mount cache partition".
What should I do? How did this happen?!? I really need my phone back asap.
Thanks everybody!
Flash the stock images.
Chromium_ said:
Flash the stock images.
Click to expand...
Click to collapse
Ok I will but...How can this happen? A fully stock phone who never had a problem suddenly corrupts it's partitions?! (This is my understanding of the situation, correct me if I am wrong)
Thanks again for the link
Update: unlocking the bootloader works but when I reboot it appears to be locked again.
flashing the bootloader img file fails.
chikosneff said:
Update: unlocking the bootloader works but when I reboot it appears to be locked again.
flashing the bootloader img file fails.
Click to expand...
Click to collapse
sounds like your storage itself fails. thats the same issue that happens when the storage goes bad.
simms22 said:
sounds like your storage itself fails. thats the same issue that happens when the storage goes bad.
Click to expand...
Click to collapse
Thanks for helping, yes it looks like..so I can throw away my phone or there's something more I can try?
It feels so weird because it's one of the few phones I always kept stock, never fell, never had a single problem. Damn.
chikosneff said:
Thanks for helping, yes it looks like..so I can throw away my phone or there's something more I can try?
It feels so weird because it's one of the few phones I always kept stock, never fell, never had a single problem. Damn.
Click to expand...
Click to collapse
You could give this a try, but I really doubt it'll do much. I guess its worth a shot though.
chikosneff said:
Ok I will but...How can this happen? A fully stock phone who never had a problem suddenly corrupts it's partitions?! (This is my understanding of the situation, correct me if I am wrong)
Thanks again for the link
Click to expand...
Click to collapse
chikosneff said:
Update: unlocking the bootloader works but when I reboot it appears to be locked again.
flashing the bootloader img file fails.
Click to expand...
Click to collapse
Tried to Toolkit yet ? http://forum.xda-developers.com/showthread.php?t=1766475
Why did it happen? A phone is basically a mini computer, same as when you have to reload a computer OS sometimes,(failing hardware, bad app???)
Timboe73 said:
Tried to Toolkit yet ? http://forum.xda-developers.com/showthread.php?t=1766475
Why did it happen? A phone is basically a mini computer, same as when you have to reload a computer OS sometimes,(failing hardware, bad app???)
Click to expand...
Click to collapse
I'll give it a shot thanks, but I am afraid that the fastboot flash error is pretty clear :crying:
I get the phone being a computer, and I am totally ready to reload an OS...but I am not so ready to see the storage fails so suddenly leaving me with no phone, especially because this phone has received more care than any other phone I ever had..
Timboe73 said:
Tried to Toolkit yet ? http://forum.xda-developers.com/showthread.php?t=1766475
Click to expand...
Click to collapse
If its failing when he does it manually via fastboot commands, its very unlikely that using a toolkit will change anything. A toolkit simply runs the same fastboot commands behind a GUI.
Switched to windows to give the toolkit a try, then I will follow the unbrick procedure...I still cannot believe that this phone is lost without even having experienced the fun to mess it up with my own hands
chikosneff said:
Switched to windows to give the toolkit a try, then I will follow the unbrick procedure...I still cannot believe that this phone is lost without even having experienced the fun to mess it up with my own hands
Click to expand...
Click to collapse
As expected: toolkit not working. Since the bootloader " relocks" itself after rebooting the toolkit is unable to flash it afterwards.
Will try to contact google support but I am currently living in Europe I don't think it will be easy to get help.
Any other help is greatly appreciated. Thanks everybody.
1. if its within the warrenty period, this is something that would be covered.
2. its fixable. it can be professionally repaired, or you can try to do it yourself with the right parts.
but you will lose whatever you had in your storage, if you havent already.
another case reported :/
i think some batches of nexus 4 contains emmc brick bugs
just see this thread, more then 5 or 6 have been reported here.
http://forum.xda-developers.com/showthread.php?t=2259334
so after reading that thread i **** my self, because if this occured to my nexus i will have no warranty no google claims no nothing because i live in Pakistan.
So i ran emmc check app on my phone to check what it shows.
my emmc check shows i have "NO, Sane chip"
this means i am safe? if it give me "Yes, Insane chip" then i,m not safe according the my theory.
EMMC check app also shows the chip type, my chip type is "016g92"
googling this chip type i came across no specific results, one from S3 sudden death thread discussion. one person reports he have the 016g92 type and it is a safe chip according to other folks.
and one person having a galaxy s3 bricked his emmcs chip and claim the warranty. after the phone returns his chip type change to 016g92
http://smartphone.usofttech.com/t85915.html
so they change the emmc chip to 016g92.
can i surely assume that my nexus is safe from this serious hardware defect?
also any one here run the emmc chip and do give there chips type here, as i want to confirm if i,m safe or not. if not i,m going to sale my phone here. because the lose will be unbearable for me if the brick did occured
---------- Post added at 11:48 AM ---------- Previous post was at 11:37 AM ----------
simms22 said:
1. if its within the warrenty period, this is something that would be covered.
2. its fixable. it can be professionally repaired, or you can try to do it yourself with the right parts.
but you will lose whatever you had in your storage, if you havent already.
Click to expand...
Click to collapse
Dear Sir do advice me
simms22 said:
1. if its within the warrenty period, this is something that would be covered.
2. its fixable. it can be professionally repaired, or you can try to do it yourself with the right parts.
but you will lose whatever you had in your storage, if you havent already.
Click to expand...
Click to collapse
I still have 2 weeks of warranty left but I'll be in Europe till next year..I will try to ask the warranty service if I can send it in at my own expense.
Damn a worldwide warranty service doesn't look so useless now as it looked when I bought it :laugh:
PHONE BACK FROM THE DEAD!!!
So I got in touch with google's customer care to arrange the RMA and just to show them that my phone was impossible to recover I jumped ahead and told 'em: ok let's do a factory reset together so that I can show you what's the problem....
Fastboot>recovery>>data wipe....COMPLETED!
I cannot understand why did it work, I tried to wipe it at least ten times yesterday.
So now I have my N4 back working. What's your opinion on what happened? Do you feel like the problem is going to show up again soon? Is there anything I should do now that it's working? I just did a factory reset, not the cache wipe.
Just FYI: RMA from oversea is a pain in the ass, you have to ship the phone back to somebody in the U.S. and THEN ask for the RMA.
I wish I had your luck, mine did the same thing about 2 weeks ago. Couldn't get it to factory reset either. Mounting issue. My RMA came in yesterday. I'm enjoying the new phone though. It's even got the little nubs on the back. Mine original was a creaky 1st or 2nd batch one, I think. I will miss all the memories, pics, and data on my old one though.
SefEXE said:
I wish I had your luck, mine did the same thing about 2 weeks ago. Couldn't get it to factory reset either. Mounting issue. My RMA came in yesterday. I'm enjoying the new phone though. It's even got the little nubs on the back. Mine original was a creaky 1st or 2nd batch one, I think. I will miss all the memories, pics, and data on my old one though.
Click to expand...
Click to collapse
Since I feel this problem is hardware related I do not feel completely safe and I believe you were the lucky one getting the RMA
I had no choice, I should have sent the phone back to the US and then ask for the RMA...big pain in the ass
:fingers-crossed: let's hope this thing holds
I need help, my phone went into a Bootloop. I have tried to flash the factory image (7.0 and 6.0.1) using NRT and manually and still does not pass the Google logo. It does not let me enter the recovery, it only restarts continuously. When flashing the factory image did not give me any error, even the computer detects it in fastboot mode.
All this happened when I was about to open an application and suddenly I shut down and began to restart continuously. I had using android 7.0 stock.
Exact thing happened to me and I flashed both 7 and 6.0.1 and wiped data and caches multiple times.. nothing seems to work.. any ideas?
Tried everything but still bootloops.
Same thing here, although I was on a 7.1 build. There must be a flaw that can cause this to happen in recent build(s), I was trying to share a picture and it froze and bricked like this suddenly. I tried every combination of formatting and flashing stock images and whatnot but no luck.
Seanmiz said:
Same thing here, although I was on a 7.1 build. There must be a flaw that can cause this to happen in recent build(s), I was trying to share a picture and it froze and bricked like this suddenly. I tried every combination of formatting and flashing stock images and whatnot but no luck.
Click to expand...
Click to collapse
Your Nexus 6P uses Samsung eMMC doesn't?
I've seen countless threads here and on reddit about this.
My phone hard bricked last week and I suspect the Samsung emmc is to blame, too many people are having the exact same issue without a solution in sight. I am absolutely unable to access the recovery or anything on the emmc for that matter.
See if you're still covered under warranty (mine was 5 days past its warranty, and Google refused to help), otherwise you're SOL. I think we need to make some noise about it and have AP or another site pick up on this.
darksmartz said:
Your Nexus 6P uses Samsung eMMC doesn't?
Click to expand...
Click to collapse
I believe it was Samsung, yes. I RMA'd it right away after exhausting all flashing efforts.
darksmartz said:
Your Nexus 6P uses Samsung eMMC doesn't?
Click to expand...
Click to collapse
How do I know if my 6p uses Samsung eMMC? What is this, btw?
Edit
Nevermind. I just figured out. Mine is Toshiba, btw.
Rafsxd said:
How do I know if my 6p uses Samsung eMMC? What is this, btw?
Edit
Nevermind. I just figured out. Mine is Toshiba, btw.
Click to expand...
Click to collapse
how did you find this out ? would be nice to tell people so they can check to find out if they will be at risk
brichardson1991 said:
how did you find this out ? would be nice to tell people so they can check to find out if they will be at risk
Click to expand...
Click to collapse
You can find this information on the Bootloader screen listed under eMMC about halfway down the list.
Same problem, samsung memory here
Same for me too,i send my phone back to amazon
Envoyé de mon HUAWEI VNS-L31 en utilisant Tapatalk
Mine uses a Toshiba eMMC and bootloops nevertheless. Not sure if this is actually what's causing it. At this point my only thought is that there was a bad batch of devices as so far no one could find a pattern on what exactly causes the bootloops.
seco2004 said:
Mine uses a Toshiba eMMC and bootloops nevertheless. Not sure if this is actually what's causing it. At this point my only thought is that there was a bad batch of devices as so far no one could find a pattern on what exactly causes the bootloops.
Click to expand...
Click to collapse
Yeah, it doesn't actually seem to be related to eMMC brand. It was very strange, because after it happened, I was able to flash 7.0 stock and regain OS use on a very touchy level. I couldn't access USB connectivity, the home button didn't work most of the time, and if I tried to do too much with it, it would go right back into infinite bootloops. After accomplishing this 2 or 3 times, I could never again get back into the OS.
I could wipe and flash all of the partitions with no errors, I could always get into stock recovery, but TWRP never worked.
Was anyone *not* on the November patch level of v7.0+?
Seanmiz said:
Yeah, it doesn't actually seem to be related to eMMC brand. It was very strange, because after it happened, I was able to flash 7.0 stock and regain OS use on a very touchy level. I couldn't access USB connectivity, the home button didn't work most of the time, and if I tried to do too much with it, it would go right back into infinite bootloops. After accomplishing this 2 or 3 times, I could never again get back into the OS.
I could wipe and flash all of the partitions with no errors, I could always get into stock recovery, but TWRP never worked.
Was anyone *not* on the November patch level of v7.0+?
Click to expand...
Click to collapse
When this first started for me I was on the latest beta build, October security patch.
Same issue here - 64MB Samsung memory.
Google support are aware of the issue, they sent out a replacement no questions asked. For some reason, the guy suggested (but he said unofficially) tapping on the power button. Anybody have any clue why this would be relevant?
Regardless, I'm in a position where I can access fastboot, but nothing else. Can anyone think of any data recovery options at this point?
---------- Post added at 12:26 PM ---------- Previous post was at 12:20 PM ----------
To follow up on my previous post - just before I hit a reboot that threw me into the bootloop, I encountered a hard freeze. I received a bug report after the hard freeze and this is now sitting in my gmail drafts. Would this bug report have any pertinent information here?
thisisgil said:
For some reason, the guy suggested (but he said unofficially) tapping on the power button. Anybody have any clue why this would be relevant?
Click to expand...
Click to collapse
I know exactly why it's relevant!
He's trying to make sure it's not a shoddy power button. My Galaxy SII back in the day had a common power button failure where it would think that you are just constantly hitting/holding the power button if you even breathed on it. My phone would bootloop or suddenly reboot constantly because it was getting power button commands from the poor quality button. Better quality buttons along with other methods of locking/unlocking the phone to reduce power presses have mostly prevented this sort of thing these days.