Out of the blue my Nexus 5 totally flipped out. It only recognizes 215MB of 16GB internal storage, the rest is missing. It's also not getting service. Also, every time I reboot the phone, it goes back to totally factory stock. So I tried unlocking it, successfully, but then on reboot it was locked again. Need to unlock and install custom recovery so I can flash a new ROM, but I can't because of the reset thing. Any ideas?
Rma the device. It sounds like your emmc flash memory is bad. You have the symptoms
Sent from my Nexus 5 using XDA Free mobile app
Log please. Perhaps you messed up with partitions just like me yesterday
GR0S said:
Log please. Perhaps you messed up with partitions just like me yesterday
Click to expand...
Click to collapse
What logs? There's basically no storage on the device, and when I plug it into my computer, it sees the phone but it's totally empty. I did nothing to any partitions. This is my wife's phone, and she's been using it bone stock since she got it a few months ago. She wouldn't let me do anything to it, no rooting, no unlocking, and she doesn't do anything to it herself except use basic apps. It just started doing this on its own. I think we'll RMA it.
RemeCA said:
What logs? There's basically no storage on the device, and when I plug it into my computer, it sees the phone but it's totally empty. I did nothing to any partitions. This is my wife's phone, and she's been using it bone stock since she got it a few months ago. She wouldn't let me do anything to it, no rooting, no unlocking, and she doesn't do anything to it herself except use basic apps. It just started doing this on its own. I think we'll RMA it.
Click to expand...
Click to collapse
go RMA then. Just thought you messed up like me yesterday (no radio, no modem).
Related
Not sure what caused this, I crack flash CM nightlies, constantly convert partitions from ext-3 to ext-4 using beta kernels and at some point in between lost the ability for any computer to recognize my phone mounting (both internal and external). Tried three different computers, two different cables, swapped sd cards, reformatting card and nothing... All that happens when plugging into computer is a charge symbol.
My SD card is accessible through file managers and is mounted just fine to phone (accurate storage space). So I took it into Tmobile and they overnight-ed me a new g2x phone which is expected to come Monday. Claimed it was a hardware failure and acknowledged I had a custom rom and to make sure I put the stock one back . The only problem it is impossible to get the stock recovery image and remove root without a computer so I will be sending them a rooted stock rom with custom recovery. Hopefully they don't charge me for it...
Just wish I knew the cause whether or not it was a bad build or human error issue. Hopefully LG or Tmobile dont charge me full price when they see the firmware has been tampered with. I could always format the system with nothing on it so it just sticks on the LG symbol and has no rom to load up i suppose lol
I had to replace my first g2x because of this. No amount of software/external hardware troubleshooting fixed it. Luckily, I got mine at Costco which has a 90 day return policy. Ill try to find the thread I made... same symptoms though.
Also, my issue occurred on stock rom unrooted, so it wasn't the result of phone tinkering.
Here is the link: http://forum.xda-developers.com/showthread.php?t=1104397
Happened to me to on my first g2x....sometimes (randlmly) it would start working again n so when it did work I was able to bring back to stock n unroot n then a few hrs later the USB stopped working again...got a new one thru warranty and have been fine since
Sent from my LG-P999 using XDA App
dominante58 said:
Happened to me to on my first g2x....sometimes (randlmly) it would start working again n so when it did work I was able to bring back to stock n unroot n then a few hrs later the USB stopped working again...got a new one thru warranty and have been fine since
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
I had this problem on my first G2X phone also. It stopped working then somehow it worked for 1 min then never again. I had to replace that phone.
brdma said:
Here is the link: http://forum.xda-developers.com/showthread.php?t=1104397
Click to expand...
Click to collapse
Yup, this definitely looks like the same issue despite I am rooted and you were stock which is proof to me that it is a defective hardware and not provoked from me tampering with the firmware. Just hope they dont throw a fit when and if they find it rooted with custom recovery image.
My GF has a completely stock SGS4G that I just updated to GB via Kies. She is having issues with the phone locking up and rebooting randomly. This happens a few times a day. I was just wondering if you all had any ideas/hints/tips that you could give me to help her with this issue. She's not to happy with me that I updated her phone and will not let me flash any roms or even root it. Thanks in advance!
Factory data reset, maybe?
I learned long ago not to ever even touch my wife's phone.
No touch... no blame.
But yea... factory reset it. Back up all her stuff first and wrote down a list of her apps and such.
Sent from my SGH-T959V using XDA App
camalus said:
I learned long ago not to ever even touch my wife's phone.
No touch... no blame.
But yea... factory reset it. Back up all her stuff first and wrote down a list of her apps and such.
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
hahaha. that is SO true! every time i try to help someone, i always get blamed if something goes wrong..and its usually their fault! one time someone pulled out their sd card while playing music and it messed up the card and they blamed me because i rooted their phone...
anyway, OP, i had a similar problem on my dad's phone. i backed up my sdcard pics/music/docs and then went into 3e recovery. factory reset and wiped cache. then i went into the privacy setting and formatted everything including the sd card. this seemed to fix it for me.
camalus said:
I learned long ago not to ever even touch my wife's phone.
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
Yeah. I lost my sgs4g by messing with my wife's g2.
Kies?
The OP said "...updated to GB via Kies..." So if your suggestion still leaves issues, I would pick of the stock rom from here (search for it in either development or q&a) and reflash. Others have reported problems with Kies, so I only used kies to the point where where I could receive the download from my temp folder, then flashed with Odin. Worked for me, but you may want to search for a link to the rom in these forums.
jager555 said:
hahaha. that is SO true! every time i try to help someone, i always get blamed if something goes wrong..and its usually their fault! one time someone pulled out their sd card while playing music and it messed up the card and they blamed me because i rooted their phone...
anyway, OP, i had a similar problem on my dad's phone. i backed up my sdcard pics/music/docs and then went into 3e recovery. factory reset and wiped cache. then i went into the privacy setting and formatted everything including the sd card. this seemed to fix it for me.
Click to expand...
Click to collapse
I've looked around quite a bit, but can't find anyone who has had this problem when restoring. I was trying out Paranoid Android 3.10 D2VZW on my Galaxy SIII, and decided to go back to JellyBam 8.2.0 D2VZW. Both are 4.2.2 ROMs. I rebooted into CWM Recovery, wiped data and cache (can't remember if I wiped the Dalvik), and restored my JellyBam backup. The restore went fine, and I rebooted the system from CWM...nothing! Phone is completely black, no boot up at all. I tried the power button, a battery pull, booting into recovery, and booting into download. When I plug my phone into my computer (a Mac with Windows running in Parallels), I get QHSUSB_DLOAD. So far my research tells me this means my phone is hard-bricked. If I plug in without a battery, I get a red LED light that extinguishes after a few minutes. My understanding of hard-bricking is that it's caused by flashing ROMs not intended for my phone (i.e. an international version ROM). Why would my phone hard-brick if the last thing I did is restore a backup from a previously-working ROM built for my phone? I didn't check the md5, but if the md5 failed wouldn't the restore fail too? I literally can't do anything with my phone. No display, no Odin/download, no recovery. The only indications that it isn't completely fried are the red LED and my computer recognizing the QHSUSB_DLOAD and making a notification sound when it's connected or disconnected. I have no problem sending it to be JTAGed if need be, but I'm not 100% that it's hard-bricked. Any suggestions?
ransdell2 said:
I've looked around quite a bit, but can't find anyone who has had this problem when restoring. I was trying out Paranoid Android 3.10 D2VZW on my Galaxy SIII, and decided to go back to JellyBam 8.2.0 D2VZW. Both are 4.2.2 ROMs. I rebooted into CWM Recovery, wiped data and cache (can't remember if I wiped the Dalvik), and restored my JellyBam backup. The restore went fine, and I rebooted the system from CWM...nothing! Phone is completely black, no boot up at all. I tried the power button, a battery pull, booting into recovery, and booting into download. When I plug my phone into my computer (a Mac with Windows running in Parallels), I get QHSUSB_DLOAD. So far my research tells me this means my phone is hard-bricked. If I plug in without a battery, I get a red LED light that extinguishes after a few minutes. My understanding of hard-bricking is that it's caused by flashing ROMs not intended for my phone (i.e. an international version ROM). Why would my phone hard-brick if the last thing I did is restore a backup from a previously-working ROM built for my phone? I didn't check the md5, but if the md5 failed wouldn't the restore fail too? I literally can't do anything with my phone. No display, no Odin/download, no recovery. The only indications that it isn't completely fried are the red LED and my computer recognizing the QHSUSB_DLOAD and making a notification sound when it's connected or disconnected. I have no problem sending it to be JTAGed if need be, but I'm not 100% that it's hard-bricked. Any suggestions?
Click to expand...
Click to collapse
It's definitely hard bricked, whatever happened is very strange though, as a nandroid doesn't usually mess up your boot partition.
Flashing a rom not intended for your phone can cause a hard brick, but that's not the only way it can happen. Somewhere in the restore process your boot partition got corrupted. Your base coding somehow is not being recognized, and your computer and phone can't tell what's supposed to run. A jtag is really your only option.
TWRP offers you the option to disable the boot and recovery partition when restoring. After you fix your phone, I'd recommend trying that out so you're absolutely sure your boot partition doesn't get touched. Those really don't need to be restored anyway.
Sorry that happened to you.
Sent from my SCH-I535 using Tapatalk 2
Bummer. Thanks for the input. I kinda figured that was the case, but was hoping I was missing something. Guess I'm going to have it JTAGed, probably by Mobile Tech Videos. The process looks fairly simple. If the equipment costs were comparable to having someone else do it I might do it myself, but if that were the case everyone else would be doing that too! I'll let you know how it goes.
ransdell2 said:
Bummer. Thanks for the input. I kinda figured that was the case, but was hoping I was missing something. Guess I'm going to have it JTAGed, probably by Mobile Tech Videos. The process looks fairly simple. If the equipment costs were comparable to having someone else do it I might do it myself, but if that were the case everyone else would be doing that too! I'll let you know how it goes.
Click to expand...
Click to collapse
I think the price is reasonable if you factor in equipment and labor.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
I think the price is reasonable if you factor in equipment and labor.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Got my phone JTAGed by Patrick Walls (whose service is available on eBay for ~$35), and it works great. Fast service and great communication from Patrick. The phone came back unrooted with a stock 4.1.2 ROM. Of course I immediately re-rooted it and flashed a fresh JellyBAM ROM to it (with a huge feeling of trepidation), and so far everything is working, with the exception of the camera (I get "Can't connect to camera" after taking one picture, and a reboot is the only thing that enables the camera again, for one pictures, then can't connect, reboot, one pic, can't connect, etc.).
Having never hard-bricked before after many, many ROM changes on a Fascinate and about 10 ROM changes on my S3, I'm a little nervous about changing them now. Is my hesitation unfounded providing I don't mess with the bootchain? To root my phone I flashed the VRALEC bootchain, then TWRP, then rooted, then JellyBAM, then the VRBMD3 bootchain, as per this rooting guide:
http://forum.xda-developers.com/showthread.php?t=2046439
Now that I've put my phone back to the Jelly Bean bootchain, I should be free to flash ROMs built for my device without a serious concern about hard-bricking, right?
ransdell2 said:
Got my phone JTAGed by Patrick Walls (whose service is available on eBay for ~$35), and it works great. Fast service and great communication from Patrick. The phone came back unrooted with a stock 4.1.2 ROM. Of course I immediately re-rooted it and flashed a fresh JellyBAM ROM to it (with a huge feeling of trepidation), and so far everything is working, with the exception of the camera (I get "Can't connect to camera" after taking one picture, and a reboot is the only thing that enables the camera again, for one pictures, then can't connect, reboot, one pic, can't connect, etc.).
Having never hard-bricked before after many, many ROM changes on a Fascinate and about 10 ROM changes on my S3, I'm a little nervous about changing them now. Is my hesitation unfounded providing I don't mess with the bootchain? To root my phone I flashed the VRALEC bootchain, then TWRP, then rooted, then JellyBAM, then the VRBMD3 bootchain, as per this rooting guide:
http://forum.xda-developers.com/showthread.php?t=2046439
Now that I've put my phone back to the Jelly Bean bootchain, I should be free to flash ROMs built for my device without a serious concern about hard-bricking, right?
Click to expand...
Click to collapse
Glad you got it working.
There's always a risk of something going wrong and a hard brick reoccurring, you just had bad luck. I don't think your brick had anything to do with your bootchain.
I think what probably happened was when you made a nandroid in cwm, the boot partition somehow got corrupted. CWM by default restores your boot, recovery, data, system, and cache partitions. In the advanced restore section, you can restore one at a time but you have no way of simply disabling a particular partition from being restored. I think since the boot partition was messed up, it erased your good data and hard-bricked your phone.
TWRP by default only backs up your data, cache, and system partitions and leaves your boot and recovery partitions alone. If you restore that backup, then there's pretty much no way a hard brick can happen. I can't think of any reason why you really need to backup your recovery or boot partition.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Glad you got it working.
There's always a risk of something going wrong and a hard brick reoccurring, you just had bad luck. I don't think your brick had anything to do with your bootchain.
I think what probably happened was when you made a nandroid in cwm, the boot partition somehow got corrupted. CWM by default restores your boot, recovery, data, system, and cache partitions. In the advanced restore section, you can restore one at a time but you have no way of simply disabling a particular partition from being restored. I think since the boot partition was messed up, it erased your good data and hard-bricked your phone.
TWRP by default only backs up your data, cache, and system partitions and leaves your boot and recovery partitions alone. If you restore that backup, then there's pretty much no way a hard brick can happen. I can't think of any reason why you really need to backup your recovery or boot partition.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Great, thanks for the info! I'll make sure that the boot and recovery partitions aren't touched in the future. I've primarily used CWM, but am probably just going to stick with TWRP.
Recently I unlocked bootloader, installed twrp and succesfully rooted my device, but while I was tinkering with my device I accidentally wipe all data, partition, etc in TWRP now I guess I wiped out everything including OS !!!
How can I restore ? Do I need to flash new hammerhead image ?
Right now I'm following this tutorial
http://forum.xda-developers.com/showthread.php?t=2513701
It'll be great if anyone of you can point me right way.
You can just flash any custom rom using this
http://forum.xda-developers.com/showthread.php?t=2575150
Or
Follow the thread you posted to restore a factory image..
But restoring a factory image will unroot your device..
You have twrp so the first thing you did was make a nandroid, right? Live and learn.
Thanks for the help, I just flashed new image. Everything works good except wifi, random drops + slow speed.
I contacted google for replacement and they send me RMA form. Unrooted the phone, bootlocker locked + flag reset.
Thanks for the help, I just flashed new image. Everything works good except wifi, random drops + slow speed.
I contacted google for replacement and they send me RMA form. Unrooted the phone, bootlocker locked + flag reset.
Huh? You're doing an RMA why?
sent from my hammerhead
albertpaulp said:
Thanks for the help, I just flashed new image. Everything works good except wifi, random drops + slow speed.
I contacted google for replacement and they send me RMA form. Unrooted the phone, bootlocker locked + flag reset.
Click to expand...
Click to collapse
Why are you rma'ing it. Was wifi messed up before you erased everything?
jd1639 said:
Why are you rma'ing it. Was wifi messed up before you erased everything?
Click to expand...
Click to collapse
Before rooting wifi problem was rarely occur now after rooting problem arise more frequently, now even after unrooting wifi is super slow sometimes not even connecting. I hate RMAing but seems like no other way.
http://forum.xda-developers.com/showthread.php?t=2586410
jd1639 said:
You have twrp so the first thing you did was make a nandroid, right? Live and learn.
Click to expand...
Click to collapse
Awesome advice. I made a nandroid of my N5 first thing after getting all my apps straight. Playing with flashing a rom in TWRP I did a manual "wipe data" which proceded to wipe out the entire SDCARD in the process including my nandroid. Sooooo.... Yes, make a nandroid but also back it up to your computer or dropbox right away.
albertpaulp said:
Before rooting wifi problem was rarely occur now after rooting problem arise more frequently, now even after unrooting wifi is super slow sometimes not even connecting. I hate RMAing but seems like no other way.
http://forum.xda-developers.com/showthread.php?t=2586410
Click to expand...
Click to collapse
Don't RMA it, there's nothing wrong with the hardware. All you have to do is reflash the factory image. If you didn't know what you were doing, you shouldn't have been messing around with your phone in the first place. Reflash your phone back to its factory state and next time do your homework before you start tinkering. People like you are going to cause Google to change their return policy so that returns are much more heavily scrutinized.
BirchBarlow said:
Don't RMA it, there's nothing wrong with the hardware. All you have to do is reflash the factory image. If you didn't know what you were doing, you shouldn't have been messing around with your phone in the first place. Reflash your phone back to its factory state and next time do your homework before you start tinkering. People like you are going to cause Google to change their return policy so that returns are much more heavily scrutinized.
Click to expand...
Click to collapse
Before rooting wifi problem was rarely occur now after rooting problem arise more frequently, now even after unrooting wifi is super slow sometimes not even connecting. I hate RMAing but seems like no other way.
Click to expand...
Click to collapse
You know how to read right ? also I did reflashed to stock image and unrooted + locked bootloader but problem persists, what do you propose I do now ? I started loving my phone now I'm getting new one, it's hard for me too, it's like adopting a son.
Let me start by saying that I am not new to rooting and flashing firmware, its just been a while since I last did it. I've had a nexus 5 for a few months with sprint in the US. I continually have reception issues and dropped calls so I took the phone in to a store. Before I could do that I had to reset everything to stock. I had no trouble doing any of that. I made a complete backup of my ROM before I did all that using TWRP. I went to the store and they told me to turn off lte in order to reduce dropped calls. After the I got home I set to work re-rooting and unlocking my bootlaoder. However when I went to restore in TWRP it would not recognize the backup even though it had been made only a few hours before. I spent several hours trying to get TWRP to recognize the backup. Whenever I navigated to the directory containing the backup the directory was always empty. I even tried zipping the backup and flashing it but it did not work. Eventually I decided to cut my losses and move on. I plan on taking the phone back to sprint tomorrow because I still have horrible reception issues. I really want to avoid having to go through the whole ordeal again but I am not sure what I did wrong. The only thing I can think of is that immediately after making the backup I moved it off the device onto my laptop but did not modify it in any way. I had some experience with CWM back when I had my old HP touchpad but none with TWRP, however they don't seem that different. Any help is greatly appreciated.
UserNumberZero said:
Let me start by saying that I am not new to rooting and flashing firmware, its just been a while since I last did it. I've had a nexus 5 for a few months with sprint in the US. I continually have reception issues and dropped calls so I took the phone in to a store. Before I could do that I had to reset everything to stock. I had no trouble doing any of that. I made a complete backup of my ROM before I did all that using TWRP. I went to the store and they told me to turn off lte in order to reduce dropped calls. After the I got home I set to work re-rooting and unlocking my bootlaoder. However when I went to restore in TWRP it would not recognize the backup even though it had been made only a few hours before. I spent several hours trying to get TWRP to recognize the backup. Whenever I navigated to the directory containing the backup the directory was always empty. I even tried zipping the backup and flashing it but it did not work. Eventually I decided to cut my losses and move on. I plan on taking the phone back to sprint tomorrow because I still have horrible reception issues. I really want to avoid having to go through the whole ordeal again but I am not sure what I did wrong. The only thing I can think of is that immediately after making the backup I moved it off the device onto my laptop but did not modify it in any way. I had some experience with CWM back when I had my old HP touchpad but none with TWRP, however they don't seem that different. Any help is greatly appreciated.
Click to expand...
Click to collapse
Did you put your backups in the correct sub-directory?
Should be something like: TWRP/BACKUPS/87095jgjg9034/nameofyourbackup
upndwn4par said:
Did you put your backups in the correct sub-directory?
Should be something like: TWRP/BACKUPS/87095jgjg9034/nameofyourbackup
Click to expand...
Click to collapse
Yes, I did. I even tried renaming the backup to "backup" and still had no luck.
Well, this is interesting. I went to Sprint today and they weren't much help but before I went there I reset everything back to stock. I made a backup yesterday and when I got home I put it on my phone and it was recognized immediately by TWRP and I was able to restore it. Not sure what I did wrong last time, if I did anything wrong at all.
UserNumberZero said:
Well, this is interesting. I went to Sprint today and they weren't much help but before I went there I reset everything back to stock. I made a backup yesterday and when I got home I put it on my phone and it was recognized immediately by TWRP and I was able to restore it. Not sure what I did wrong last time, if I did anything wrong at all.
Click to expand...
Click to collapse
Yeah, that's a bit odd. Glad you got it working now.
Sent from some device using XDA Premium mobile app