Database Info

baseband unknown :((

So i must have messed up my phone while using the all in one root unlocker and so on. Im not sure what i did, but i finally got my phone to boot, and now i get no service. Im on tmobile and it says i have no sim card. When i go into about phone it shows baseband unknown.
I really have no idea what to do. Ive never been stuck in this situation. Maybe someone more experienced can point me in the right direction?
any help would be appreciated!

aamzalag said:
So i must have messed up my phone while using the all in one root unlocker and so on. Im not sure what i did, but i finally got my phone to boot, and now i get no service. Im on tmobile and it says i have no sim card. When i go into about phone it shows baseband unknown.
I really have no idea what to do. Ive never been stuck in this situation. Maybe someone more experienced can point me in the right direction?
any help would be appreciated!
Click to expand...
Click to collapse
so furthermore, it looks like i have no data partition anymore, i can go on my chromebrowser on the phone and browse the web but when i try to install anything it says no sdcard. I also cant move anything to the phone via windows, it just freezes even tho i can see the phone and go into the internal storage.
Im really screwed here. Ive also used the fastboot files to flash back to google stock, but for some reason continue to find everything borked.
HELP PLZ!!! ahah

Also, finding that i cant mount any partition, cache, data, anything liek that. It seems like my partitions have been messed up . Not sure how to resolve that

Well it looks like your the first one to brick the nexus 5. If your imei is missing your screwed.
P.S.A DON'T USE TOOLKITS
Sent from my NEXUS 5

Might be helpful to others to explain exactly what you did to your phone.

lafester said:
Might be helpful to others to explain exactly what you did to your phone.
Click to expand...
Click to collapse
He used a tool kit. Who knows what it did to his phone
Sent from my NEXUS 5

I realize that maybe using the toolkit may not have been a good choice but considering im already here. Constructive advice might be a little more helpful... I know that with my old verizon GS3 if i lost my imei/ similar info, i could nv flash myself and get it back in certain cases. Does a similar thing not exist for the nexus 5? Id imagine that a truly unlocked device like this one should have a method to get back from anything?

aamzalag said:
I realize that maybe using the toolkit may not have been a good choice but considering im already here. Constructive advice might be a little more helpful... I know that with my old verizon GS3 if i lost my imei/ similar info, i could nv flash myself and get it back in certain cases. Does a similar thing not exist for the nexus 5? Id imagine that a truly unlocked device like this one should have a method to get back from anything?
Click to expand...
Click to collapse
If you've flashed the stick images and it hasn't fixed it then you might be out of luck. With the n4 there is a thread on how to restore the phone with LG nv flash in download mode. I don't think the tools or files are available yet for the n5 tho
Sent from my NEXUS 5

i dont know what i did, but i restored the factory image one more time, then booted to stock recovery and wiped all partitions. The phone booted and my imei and baseband are back. Working 100% now. Gonna sit out the rooting and so on for now. time to relax for a bit

So you can't fastboot flash anything? Can you fast boot flash twrp recovery from the android SDK on a PC?
Sent from my Nexus 7

aamzalag said:
i dont know what i did, but i restored the factory image one more time, then booted to stock recovery and wiped all partitions. The phone booted and my imei and baseband are back. Working 100% now. Gonna sit out the rooting and so on for now. time to relax for a bit
Click to expand...
Click to collapse
That's how I fixed my N4. I flashed the factory images 3 times.

Glad it's working finally
Sent from my Nexus 7

Ya, fastboot continued to work, and iw as able to flash the factory images.At first those werent fixing anything. the final time i flashed it right before it worked again, i let the phone sit and run the boot screen for about 30 minutes before i went to stock recovery and wiped. Then it booted perfectly.
The previous times i had flashed twrp and wiped which i believe was the cause in the first place.
Thanks all its working perfect now. The device is amazing,!

aamzalag said:
The previous times i had flashed twrp and wiped which i believe was the cause in the first place.,!
Click to expand...
Click to collapse
Sames just happened to me, but I didnt use a toolkit, i did it all manually.
Quick flash of the factory image sorted it. :victory:
UPDATE: Flashed TWRP again....All ok this time.

You guys unlocked the bootloader first right?
Sent from my SGH-I747

This has just happened to me. I have installed the stock images 2 times now.
Is there anything you guys did differently to make it work?

My N5 decided to wipe the baseband and IMEI when I went to wipe the cache through recovery. Tried to reflash factory images 5 times and each time, when the phone boots up, hangouts, camera and gallery apps force close and I still have no network signal or IMEI/baseband.
Worst bit is all I did was wipe the cache partition, done that a million times and never had this problem
Anyone know what i can do?
I've relocked the bootloader for now but I can't call Google because my only phone is the Nexus 5 so that's out of the question.
Edit:
Managed to fix it by using a slightly different set of fastboot commands.
Here's what I did:
adb reboot bootloader
fastboot flash bootloader bootloader-hammerhead-HHZ11d.img
fastboot reboot-bootloader
fastboot flash radio radio-hammerhead-M8974A-1.0.25.0.17.img
fastboot reboot-bootloader
fastboot -w update image-hammerhead-krt16m.zip
fastboot reboot-bootloader
That worked for me

WRAITH07 said:
My N5 decided to wipe the baseband and IMEI when I went to wipe the cache through recovery. Tried to reflash factory images 5 times and each time, when the phone boots up, hangouts, camera and gallery apps force close and I still have no network signal or IMEI/baseband.
Worst bit is all I did was wipe the cache partition, done that a million times and never had this problem
Anyone know what i can do?
I've relocked the bootloader for now but I can't call Google because my only phone is the Nexus 5 so that's out of the question.
Click to expand...
Click to collapse
After you flash the factory image, boot into recovery and do a factory reset.

You mentioned a cache wipe. Was this in CWM or TWRP? My N5 hung trying to do a cache wipe in CWM. After rebooting the sdcard was inaccessible. The solution was to flash TWRP from fastboot, and do an advanced wipe of only the cache, and give it TIME. Like 5-10 minutes. After another reboot I had the sdcard and radio back, but some write permission issues. One more reboot and everything was ok again.
Sent from my Nexus 5 using Tapatalk

cmstlist said:
You mentioned a cache wipe. Was this in CWM or TWRP? My N5 hung trying to do a cache wipe in CWM. After rebooting the sdcard was inaccessible. The solution was to flash TWRP from fastboot, and do an advanced wipe of only the cache, and give it TIME. Like 5-10 minutes. After another reboot I had the sdcard and radio back, but some write permission issues. One more reboot and everything was ok again.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I had this issue while wiping cache in TWRP 2.6.3.0
Sent from my Nexus 5 using Tapatalk

ADB stuck erasing 'userdata'

Like the title says, I'm stuck at the erasing 'userdata' part of flashing back to stock.
I'm following the information from http://forum.xda-developers.com/showthread.php?t=2513701
I chose to use method 1, since i'm lazy and just want the new 4.4.1. Everything was going well until that part. Please help, I don't want to brick my phone by doing something stupid like unplugging it.... Unless that'll work.
also the little android with the ! is not present. The screen still shows the large android with blue squares inside. I also did not factory reset before i tried to do this.

datboyc said:
Like the title says, I'm stuck at the erasing 'userdata' part of flashing back to stock.
I'm following the information from http://forum.xda-developers.com/showthread.php?t=2513701
I chose to use method 1, since i'm lazy and just want the new 4.4.1. Everything was going well until that part. Please help, I don't want to brick my phone by doing something stupid like unplugging it.... Unless that'll work.
Click to expand...
Click to collapse
formatting partitions can take ages on this phone. i stopped mid-format on cache with an early version of TWRP a couple of weeks ago and it's taken the best part of a day yesterday to sort it out - i couldn't even flash kernels or boot animations without bootloop (on the second boot? wtf??), and ended up going back to stock, locking the bootloader and repeatedly formatting all partitions to sort it! (it might be worth locking and unlocking the bootloader before you put your data back since you're there anyway....)

Well I decided to be brave and boot from TWRP recovery, but when I unplugged the phone ADB showed an error saying "Too many open files in system". The phone then rebooted on its own, and the little android with the ! came up, and the process seems to have worked. Thank you for the information about taking forever on the formatting, I will keep that in mind when I flash a custom recovery again.

I know its a little outdated, but i had the same problems few days ago, and i solved the problem using a pc in windows xp and everything went great, but in Windows 7 everytime got stuck at erasing userdata.

Permission issue fixed!
To all of you that have permission issues, problems etc. check out this on youtube!
[Tutorial] How to Flash ASUS Zenfone 5 CN/TW to WW Firmware [EN]
This made a huge difference on my phone. Phone is much smoother than before and now my speaker has started working again.
Took some time to get it done (couple of hours) but it was worth it!
If you encounter any problems, just read the comments.

huh???
"How to flash Asus Zenfone 5"???
What??
ffs.

[Q] [SOLVED] No EFS backup. IMEI lost.

So, I unlocked bootloader of my N5. Flashed CWM Touch. Didn't make any kinda backup (I know I'm stupid) and flashed paranoid android. Now I'm not getting any signals on it. Please, I'm in need of desperate help. Any solutions?
EDIT:
Flashed stock image, good as new This should help people who are as stupid as me

Do the usual flash cache.img first. Failing that, reflash all stock images
Sent from my Nexus 5 using Tapatalk

Hello,
Did you wipe data/factory reset, cache, dalvic cache before flashing PA rom.zip?
IF not, then head over to recovery and wipe everything.. Now flash pa.zip and gapps.zip and finally reboot...
Just flashing the pa rom won't touch the efs...

rootSU said:
Do the usual flash cache.img first. Failing that, reflash all stock images
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Trying this
vin4yak said:
Hello,
Did you wipe data/factory reset, cache, dalvic cache before flashing PA rom.zip?
IF not, then head over to recovery and wipe everything.. Now flash pa.zip and gapps.zip and finally reboot...
Just flashing the pa rom won't touch the efs...
Click to expand...
Click to collapse
But, I did not wipe data/factory reset..I went into mounts and storage and wiped everything except sd-card

Flashing Cache didn't work..I'm ****ed am I not? Someone please help me

7alvi said:
Flashing Cache didn't work..I'm ****ed am I not? Someone please help me
Click to expand...
Click to collapse
Not yet, flash the factory image. That'll get you to a like new condition.
Sent from my Nexus 5

7alvi said:
Flashing Cache didn't work..I'm ****ed am I not? Someone please help me
Click to expand...
Click to collapse
Go to your custom recovery and wipe everything (data/cache/dalvic)... Now flash the rom.zip and gapps.zip and finally reboot and see whether you're able to get a signal or not?
OR
You could use this guide to return to full stock and check... http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701

jd1639 said:
Not yet, flash the factory image. That'll get you to a like new condition.
Sent from my Nexus 5
Click to expand...
Click to collapse
I'm flashing the stock image as of now. But, how will it restore my efs partition? By wiping everything in recovery in mounts and storage, didnt i wipe it too?

7alvi said:
I'm flashing the stock image as of now. But, how will it restore my efs partition? By wiping everything in recovery in mounts and storage, didnt i wipe it too?
Click to expand...
Click to collapse
Just because the symptoms appear to indicate that you've screwed your efs partition,.doesn't mean you actually have.
Bad /cache and /data have been known to exhibit the same symptoms and flashing cache or returning to stock are known fixes if that's the case
Sent from my Nexus 5 using Tapatalk

rootSU said:
Just because the symptoms appear to indicate that you've screwed your efs partition,.doesn't mean you actually have.
Bad /cache and /data have been known to exhibit the same symptoms and flashing cache or returning to stock are known fixes if that's the case
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I'm flashing stock image but it's kinda stuck on
archive does not contain boot.sig
archive does not contain recovery.sig
It's been like 10 minutes since that. I'm on on old Pentium 4 PC so maybe it's taking time? I dunno!

7alvi said:
I'm flashing stock image but it's kinda stuck on
archive does not contain boot.sig
archive does not contain recovery.sig
It's been like 10 minutes since that. I'm on on old Pentium 4 PC so maybe it's taking time? I dunno!
Click to expand...
Click to collapse
The 2 lines is are normaly
Try again with admin rights

7alvi said:
I'm flashing stock image but it's kinda stuck on
archive does not contain boot.sig
archive does not contain recovery.sig
It's been like 10 minutes since that. I'm on on old Pentium 4 PC so maybe it's taking time? I dunno!
Click to expand...
Click to collapse
That could be because you extracted the image-hammerhead xxxxx.zip file. dont extract it. it should be there like it is on this picture
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

rootSU said:
Just because the symptoms appear to indicate that you've screwed your efs partition,.doesn't mean you actually have.
Bad /cache and /data have been known to exhibit the same symptoms and flashing cache or returning to stock are known fixes if that's the case
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I officially pronounce this phone as un-brickable. Yes it's fixed. IMEI, baseband siganls everything is back... @rootSU I owe you a beer man. I can't emphasize how ****lessly scared I was...thanx a lot!

No worries
Sent from my Nexus 5 using Tapatalk

Just pumping this thread.
I've gone through a few steps but have ran into a snag.
Heres the synopsis;
My device was randomly shutting down while charging so I decided to factory reset to see if that helped.
When I did the the device entered a boot loop and when I went into recovery it would say can't mount cache etc.
I tried re flashing 5.0.1 Lrx22c but again it got stuck in a boot loop.
I managed to flash 4.4.4 and the device finally turns on.
The only problem is that the phone appears to be without any network connection. Google playstore cannot open and crash's and so does the camera and gallery applications. Adding a sim card does nothing to help.
I'm not sure how to fix this problem and I'm at a point where I need to ask for help. I'm Canadian and bought the device through one of our providers, Rogers, and am starting to think that there is a specific set of 'roger' img's that I need to flash and not the ones from the developers site.
Any input would be much appreciated.

Bump bump ^^

There is no such thing as carrier specific factory images. Did you try reflashing the radio, or a different radio? Remove and reinsert Sim? Might be hardware issue otherwise ..
Sent from my Nexus 5 using Tapatalk

At my wit's end.
I realize it's been 2 weeks since you posted but, in the hope that you are subscribed still Radioman66, I'm curious if you did ever manage to fix/reinject your IMEI; I'm Canadian too btw, though I bought my Nexus 5 through Google Play. I've tried flashing stock everything: bootloader, radio, boot, system, cache, userdata via fastboot; only then did my phone reboot properly, but it still has a habit of crashing/rebooting every so often. No IMEI & no cellular reception thus far, so I can only conclude that there is some data corruption at play here. Fortunately it was easy to find my unique IMEI via a sticker on the inside of the back cover of my Nexus 5, for those who aren't aware.
So I'm in the opinion that the issues of bootloops and my IMEI corruption (dialling *#06# on the dialer calls up a bold IMEI header but no number whatsoever) first occurred when my battery drained to zero. I was using a custom rom at the time, Optipop Dark Deodex with f2fs formatted data and cache partitions, + Multirom & multirom compatible TWRP. I'm at a loss for why the EFS partition and thus IMEI would even be accessed by the phone for writing/reading or how a corruption of the partition could even occur. Perhaps I was receiving a text message right at that very moment it turned off? Perhaps f2fs is to blame, who really knows...main thing is my IMEI is corrupted and I'm left with a smart brick, it being no longer a smart phone.
Anyway, long story short it's been like 2 days of searching around but I think this free tool "Setup DFS 15.01.17.0.zip" at cdmatool dot com (can't post link as a newbie so replace dot with a period) may be the real deal; it's possible to download it without registering i.e. demo mode ( which makes you wait tens of seconds between operations). Despite my general comfort with adb, fastboot, cmd tools in general, the CDMAtool's manual is full of stuff and acronyms I don't really know about yet, like COM Ports and what not but I'm hoping to soon understand this tool and will report back my failures/successes. If anyone would be kind enough to perhaps walk me through what I would need to do, I'd be super thankful!!!t
Welp, cheers to not even knowing about the existence of ESN/EFS/IMEI before this unfortunate juncture LMAO--I will definitely make sure to backup my EFS partitions before flashing custom roms from now on...

[Q] Flashing no longer possible: Flash successful but system does not change

Hello!
I can no longer flash anything to my GT-P5110, even factory reset has no effect. The internal storage seems to be read-only.
I think this is a longer story: About one year ago the stock firmware became incredibly slow, to the point that processes started to force close, then my user data was lost, and after factory reset the tablet went into endless boot loop.
So I decided to give CM10 a try and it worked flawlessly. The tablet was fast again. I even could upgrade to CM11 later. But around 2 month ago, only sometimes processes started to force-close or the tablet randomly rebooted itself - mostly during charging. I left it that way in the charger for some days because I had no time to bother with that issue. Then, I tried to factory reset my device only to find out that this has absolutely no effect. Installing app updates: No effect. Changing system settings: No effect. And apps start to force-close at an insane rate short after boot. The device is unusable. My could only shut down and reboot into recovery. I left the tablet lying around, turned off, out of charger, for 2 months. Now I tried to investigate:
When I "adb shell" into recovery and call dmesg, I see lots of these lines:
Code:
mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
I think something is really broken with the internal storage. I tried to flash a newer recovery but it has no effect, even when done from download mode.
Factory reset sometimes fails with an error. Reinstalling CM fails with an error. Wiping cache seemingly succeeds but I'm sure it has no effect. I tried installing SlimRom instead which seemingly succeeds, too - but after reboot I'm greeted with the CM boot logo again.
I tried to flash stock firmware with Odin. It is very very slow, runs for about 15 minutes, then fails at around 50%. Of course: That "half flashed firmware" does in no way affect the device: It still boots CM11 "without problems", then a few seconds after finishing boot (showing home screen), force-closes start to pop-up.
What should I do? I suppose the device is out of warranty for a few weeks or months, now. And even when not: It has been flashed with CM, the triangle counter is not zero. I suppose that combination of problems (read-only/failing storage, non-stock firmware) voids warranty in a way that Samsung will deny any repair. If at least I could return the device to stock firmware things would be different maybe.
Any ideas what I could try? Is it possible that the internal storage is simply fried? fsck'ing the partitions shows no errors, just the data partition is unclean with unwritten journal data but all data is readable. So the internal storage has probably not died. It just sticks to read-only mode for whatever reason.
I've found some posts with similar problems but those seem to be about older Galaxy Tab 1 devices built 2011 or before.

Just reading over this and it sounds very similar to what I'm currently facing, which is doubly annoying as no one else has chipped in a solution
I had reboot issues with my Tab2 10.1 (GT-P5110) on stock so after realizing I'd need to factory reset bite the bullet and rooted so I could use CM10.
Had occasional reboots but nothing I couldn't live with however from yesterday evening the tablet is seemingly stuck in a boot loop. It comes on, some apps fire up and an update starts. Sometimes apps force close then BOOM I get the boot splash screen.
I've tried factory reset in recovery (CWM 6.0.2.7) to no avail and wiping just about everything which also had no noticeable effect as all my settings and the rom are still the same when I get back in (albeit briefly!).
I've tried flashing new recovery via ODIN which reported a success however that also didn't appear to take. I'm beginning to think it some serious file system or storage corruption ;(

Same problem here...
Hopefully someone can come up with a solution or at least a cause. I've tried to Odin every recovery available for my 5113 and nothing has taken. I'm currently on Omni with cwm and tried to update to the latest cwm and twrp and aroma installer yet nothing takes. I too rooted because of the incessant bootloops about 3 months ago.

bigg fella said:
Hopefully someone can come up with a solution or at least a cause. I've tried to Odin every recovery available for my 5113 and nothing has taken. I'm currently on Omni with cwm and tried to update to the latest cwm and twrp and aroma installer yet nothing takes. I too rooted because of the incessant bootloops about 3 months ago.
Click to expand...
Click to collapse
For what I can tell, my device is effectively read-only. Even in download mode (Odin) I cannot even flash a different recovery (tried to flash TWRP, still boots CWM).

hurikhan77 said:
For what I can tell, my device is effectively read-only. Even in download mode (Odin) I cannot even flash a different recovery (tried to flash TWRP, still boots CWM).
Click to expand...
Click to collapse
exactly, can't even uninstall an app. It's as if it boots from a permanent back up because even deleting pictures or files isn't permanently successful. You can uninstall and delete to your hearts content, get false hope, and get crushed after it reboots and everything is unchanged

Not looking very optimistic for this I was getting a similar inkling that it's gone into a permanent RO mode as not even the wipes from recovery have an effect. I'd also tried un-installing apps as I noticed one updating and thought it was crashing it however even when it did fire up and I disabled WLAN to stop Play Store auto-updating and removed the app on the next reboot cycle the app was back:crying::crying:
I fear I may have a big white paperweight....

Sounds like the internal partitions might need to be completely reformatted. This CAN be done through recovery, but is tricky... However without actually having your device in my hand I'm not sure 100 what the best course of action would be. Try searching for the commands to format (or maybe someone else will post them) or maybe PM me for them but no promises. I won't post them publicly on XDA because honestly there are too many users who do stuff like one-click root and don't actually know what they're doing and I don't want to be in some way responsible for someone following the command wrong and bricking their device for good. I don't need that on my conscience. Personal choice.
Sent from my Nexus 4 using XDA Premium HD app

shakatu said:
Sounds like the internal partitions might need to be completely reformatted. This CAN be done through recovery, but is tricky... However without actually having your device in my hand I'm not sure 100 what the best course of action would be. Try searching for the commands to format (or maybe someone else will post them) or maybe PM me for them but no promises. I won't post them publicly on XDA because honestly there are too many users who do stuff like one-click root and don't actually know what they're doing and I don't want to be in some way responsible for someone following the command wrong and bricking their device for good. I don't need that on my conscience. Personal choice.
Sent from my Nexus 4 using XDA Premium HD app
Click to expand...
Click to collapse
Would this method be any different to the way it attempts to reformat the internal partitions when you select to format the various mounts from CWM? If so I'm more then willing to give it a go as I really have nothing to lose as the damn thing is useless atm!

shakatu said:
Sounds like the internal partitions might need to be completely reformatted. This CAN be done through recovery, but is tricky... However without actually having your device in my hand I'm not sure 100 what the best course of action would be. Try searching for the commands to format (or maybe someone else will post them) or maybe PM me for them but no promises. I won't post them publicly on XDA because honestly there are too many users who do stuff like one-click root and don't actually know what they're doing and I don't want to be in some way responsible for someone following the command wrong and bricking their device for good. I don't need that on my conscience. Personal choice.
Sent from my Nexus 4 using XDA Premium HD app
Click to expand...
Click to collapse
Good call......Smart move?

help!!
same issue here , sort of .. i have stock rom and stock recovery and i cannot flash CWM .. no matter how many times i try through ODIN or hemidal nothing changes.. any idea what is going on here?

PMs have been sent. Hopefully it works.
Sent from my Nexus 4 using XDA Premium HD app

im also having this issue with my galaxy tab2 7".. help is badly needed

Well, the proposed fix I had didn't help. Was worth a shot...
Sent from my Nexus 4 using XDA Premium HD app

hope someone finds a solution for this.

No Access to ADB
shakatu said:
PMs have been sent. Hopefully it works.
Sent from my Nexus 4 using XDA Premium HD app
Click to expand...
Click to collapse
Hi Shakatu,thanks for the PM, however, my device in ADB is unauthorised, so wont let me get into shell. Is there a way around this please?

sunnytimes said:
same issue here , sort of .. i have stock rom and stock recovery and i cannot flash CWM .. no matter how many times i try through ODIN or hemidal nothing changes.. any idea what is going on here?
Click to expand...
Click to collapse
Unmark "Auto Reboot" in Odin when CWM is flashed... Stock room overwrites it during start.
After flashed CWM start in Recovery mode and flash new ROM.
this is offtopic in this tread

same problem please help me... :crying:

seagman said:
Unmark "Auto Reboot" in Odin when CWM is flashed... Stock room overwrites it during start.
After flashed CWM start in Recovery mode and flash new ROM.
this is offtopic in this tread
Click to expand...
Click to collapse
i have tried that 100 times .. its also exactlly what this thread is about , not being able to flash because nothing changes..

sunnytimes said:
i have tried that 100 times .. its also exactlly what this thread is about , not being able to flash because nothing changes..
Click to expand...
Click to collapse
same here too, i have same issue.. unable to flash or do anything to my phone....

Probably this is the end for our tab. As off now the tab is useless.
Sent from my GT-N7000 using XDA Free mobile app

Updating to 5.1.1 made phone stuck in boot animation

Hi.
Yesterday I got a notification to update to 5.1.1. ( My nexus 5 was on 5.1, everything stock, never flashed anything before )
I selected 'install' for 5.1.1, and left my phone aside. After a few minutes I saw that it was in the boot animation. I thought it was the process ongoing. Several hours later I decided to restart the phone manually ( obviously something went wrong ).
After rebooting, again, it's stuck there. On the four colored dots swirling around.
I searched on forums, I got the 5.1.1 stock, got ADB, fastboot etc, flashed as the instructions said ( via ./flash-all.sh and via the long version by manually flashing every partition ) EVERY time the same thing, when I boot it's just showing the boot animation forever.
Any idea on what's wrong?

blackjim said:
Hi.
Yesterday I got a notification to update to 5.1.1. ( My nexus 5 was on 5.1, everything stock, never flashed anything before )
I selected 'install' for 5.1.1, and left my phone aside. After a few minutes I saw that it was in the boot animation. I thought it was the process ongoing. Several hours later I decided to restart the phone manually ( obviously something went wrong ).
After rebooting, again, it's stuck there. On the four colored dots swirling around.
I searched on forums, I got the 5.1.1 stock, got ADB, fastboot etc, flashed as the instructions said ( via ./flash-all.sh and via the long version by manually flashing every partition ) EVERY time the same thing, when I boot it's just showing the boot animation forever.
Any idea on what's wrong?
Click to expand...
Click to collapse
I would wipe data.

Sandman-007 said:
I would wipe data.
Click to expand...
Click to collapse
Tried 'Wipe data/factory reset' a couple of times.
Also tried 'Wipe cache partition' later.
No difference at all. It stays for hours on the booting animation.
Can I somehow see the logs or something to see where it's stuck?

I believe you must flash factory images at this point. Just make sure you backup SD Card data or flash each partition manually skipping the userdata.img (this one erases internal storage)
Sent from my Nexus 5 using XDA Forums

Sandman-007 said:
I believe you must flash factory images at this point. Just make sure you backup SD Card data or flash each partition manually skipping the userdata.img (this one erases internal storage)
Sent from my Nexus 5 using XDA Forums
Click to expand...
Click to collapse
Well I did that, I tried 5.1, 5.1.1 and the M image.
None of them works.
At this point I'm tired of doing the whole process every time and waiting for 15 mins to see if it worked.
Thankfully, I called google support and they will send me a replacement.
I'm just very curious how this whole mess happened from a simple OTA update.

blackjim said:
Well I did that, I tried 5.1, 5.1.1 and the M image.
None of them works.
At this point I'm tired of doing the whole process every time and waiting for 15 mins to see if it worked.
Thankfully, I called google support and they will send me a replacement.
I'm just very curious how this whole mess happened from a simple OTA update.
Click to expand...
Click to collapse
If a complete wipe of the phone with factory images didn't fix it sounds like hardware. Possible corrupt NAND I think.
Sent from my Nexus 5 using XDA Forums

Sandman-007 said:
If a complete wipe of the phone with factory images didn't fix it sounds like hardware. Possible corrupt NAND I think.
Sent from my Nexus 5 using XDA Forums
Click to expand...
Click to collapse
Possibly.
In any case, they already sent me a replacement phone.
Google support has been extremely satisfying.