[Q] Unknown Baseband Version and IMEI - Nexus 5 Q&A, Help & Troubleshooting

Hello,
I had recently bought a Nexus 5 Model LG-D821 of 32gb storage.It was all ok but suddenly got switch off and reboot itself .Then I see welcome screen,select wifi,etc and finally it shows home screen.I got the pop up message notifying "camera has stopped" "gallery has stopped" etc.Then i checked into setting under storage there i see all mine data was erased.I had "32 Gb" of storage now i see total space of "128mb".There was only 5mb available storage.Further, there was unknown baseband version,unknow IMEI and unavailable Network.I take out the sim and inserted again but it doesnt worked.My Nexus 5 is unrooted,locked(bootloader version-HHZ11K) with a Build Number KTU84P currently running android 4.4.4 fully stock. Now I need help from you all expertise.How to fix this problem?Can it be fixed?Any help would be greatly appreciated.I dont know much about technicalities,provide me step by step guide to solve this issue.
:
thank you>>

Sounds like a bad emmc get a warranty replacement I see this a lot from the nexus 5

Yeah, you can try reflashing stock and what not.... But if you just bought it... I'd get it replaced instead.

spinninbsod said:
Sounds like a bad emmc get a warranty replacement I see this a lot from the nexus 5
Click to expand...
Click to collapse
hello,
thanks for the reply but i dont think there is a replacement warranty for this device.I bought from amazon japan there i see 30 days return policy.I dont know what to do..

KJ said:
Yeah, you can try reflashing stock and what not.... But if you just bought it... I'd get it replaced instead.
Click to expand...
Click to collapse
hello,
thank you for the reply.I tried to flash stock but this but unable to do that.It says like this in recovery
E:failed to mount /cache (invalid argument)
E;can't mount /cache/recovery/log
E;can't open /cache/recovery/log
E:failed to mount /cache (invalid argument)
E:Can't mount /cache/recovery/last_log
E:can't open /cache/recovery/last_log
E:failed to mount /cache (invalid argument)
E;can't mount /cache/recovery/last_install
E:can't open /cache/recovery/last_install
E:failed to mount /cache (invalid argument)

Try mobile uncle tool
Sent from my GT-I8262 using XDA Free mobile app

pradip.108 said:
Try mobile uncle tool
Sent from my GT-I8262 using XDA Free mobile app
Click to expand...
Click to collapse
bad idea!!!!!

pradip.108 said:
Try mobile uncle tool
Sent from my GT-I8262 using XDA Free mobile app
Click to expand...
Click to collapse
Its meant for mtk devices nt qualcom

doctor_droid said:
Its meant for mtk devices nt qualcom
Click to expand...
Click to collapse
My friend got trolled by a kid that told him to use that tool for flashing custom recovery on his Xperia L, and he bricked his device

ZammyHedgeFox said:
My friend got trolled by a kid that told him to use that tool for flashing custom recovery on his Xperia L, and he bricked his device
Click to expand...
Click to collapse
Must have been a hardbrick lol

Friend od mine had the same issue. It is emmc failure. There is nothing you can do about it. Had to be send for replacement. In other words flash memory is dead.

yam.riddle said:
hello,
thank you for the reply.I tried to flash stock but this but unable to do that.It says like this in recovery
E:failed to mount /cache (invalid argument)
E;can't mount /cache/recovery/log
E;can't open /cache/recovery/log
E:failed to mount /cache (invalid argument)
E:Can't mount /cache/recovery/last_log
E:can't open /cache/recovery/last_log
E:failed to mount /cache (invalid argument)
E;can't mount /cache/recovery/last_install
E:can't open /cache/recovery/last_install
E:failed to mount /cache (invalid argument)
Click to expand...
Click to collapse
Try flashing just the cache partition through fastboot.
Code:
fastboot erase cache
Code:
fastboot flash cache cache.img

varuntis1993 said:
Try flashing just the cache partition through fastboot.
Code:
fastboot erase cache
Code:
fastboot flash cache cache.img
Click to expand...
Click to collapse
i got this error:
Failed <remote:failed to erase partition>

yam.riddle said:
i got this error:
Failed <remote:failed to erase partition>
Click to expand...
Click to collapse
Try relocking your bootloader with fastboot oem lock, them reboot the bootloader. If it stays locked, then try LG Flashtool. If it reverts to being unlocked after the reboot then your eMMC is damaged and you'll have to RMA.

Well, my Nexus 5 had a similar problem, but mine was unable to mount /persist.
So all thanks to this, my Nexus 5 was saved. You might want to try this if that doesn't work.

Lethargy said:
Try relocking your bootloader with fastboot oem lock, them reboot the bootloader. If it stays locked, then try LG Flashtool. If it reverts to being unlocked after the reboot then your eMMC is damaged and you'll have to RMA.
Click to expand...
Click to collapse
hello,
It is by default locked.when i hit fastboot oem unlock,bootloader is unlocked but after reboot in bootloader it stays locked.Does LG Flashtool works in my case?

yam.riddle said:
hello,
It is by default locked.when i hit fastboot oem unlock,bootloader is unlocked but after reboot in bootloader it stays locked.Does LG Flashtool works in my case?
Click to expand...
Click to collapse
Probably not but you can try. Most likely you'll have to RMA.

Related

[Q] Urgent - Boot loop and unable to restore to stock.

Alright guys, I've got a question. I have my brothers nexus s that has had CM9 A11 on it and we decided to move to the latest CM9. Long story short, I am no longer able to boot the phone up, but can only access CWM Recovery and Bootloader/Fastboot mode. Trying to boot results in a bootloop. I need help getting this thing back to stock however I can. I've tried to flash recovery.img via fastboot but cannot get my computer to recognize the phone in order to do what I need. He would like his phone back ASAP and I hate to tell him its bricked for a few days. Thanks!
Download full OTA ROM from the link in my signature. Boot into CWM, mount USB storage, and transfer the file to SD card. Flash it. Done.
Just make sure you download the correct ROM for your phone model.
Sent from my Nexus S using xda premium
Video on that page will show you how to install drivers on a windows-based machine to recognise the phone for fastboot, and provide files to do so.
Also, can't you go into CWM --> mounts and storage --> mount usb storage (while plugged into the computer) then copy over any files you need, then flash through recovery.
I forgot to mention that I am getting this when trying to format cache:
E:Can't find misc
E:failed to find "cache" partition to mount at "/cache"
E:Can't mount /cache/recovery/command
E:Can't find misc
E:failed to find "cache" partition to mount at "/cache"
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to find "cache" partition to mount at "/cache"
E:Can't mount /cache/recovery/latest_log
E:Can't open /cache/recovery/latest_log
E:Can't find misc
E:failed to find "cache" partition to mount at "/cache"
I tried to install the OTA update like you said but got the following:
assert failed: write_raw_image("/tmp/boot.img".
"boot")
E:Error in /sdcard/(OTA file name here)
(status 7)
Installation aborted.
Maybe the internal SD card is bad? Any thoughts?
When you get the drivers installed, download the latest 5.0.2.0 CWM from here.
Alright, so I got fastboot to recognize the phone, but am having another problem. It gave me an error when I gave the command to flash the new CWM. I tried to install pdanet for the drivers, and the phone says at the bottom "FASTBOOT STATUS - FAILInvalid Command". I really think something has been corrupted, any ideas on how to fix it/restore it? Thanks for all the help guys.
Fastboot status is not a command.
Fastboot devices is the command you use to test if it sees the device . The serial number will show.
uh oh sounds like someone flashed brickROM V1
Sent from my Nexus S 4G using XDA App. Developer of brickROM, and OP of XDA Thread of The Year 2011.

Nexus 5 crashes and doesn't open

I have waked up and noticed that the phone is stuck on google logo, i tried to restore factory settings but that was not applicable
so i followed that post http://forum.xda-developers.com/showthread.php?t=2513701 to unlock the bootloader and install factory rom
after several tries my mobile phone can't start and when it starts the apps begin to crash one after the other, I noticed that the mobile recognize a memory of 250 MB (although I have a 32 GB storage) and I think thats the problem
Now I can open the recovery mode but the following errors appears:
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/log_log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
E:failed to mount /cache (Invalid argument)
So I don't know what to do!!!!! please help
Unfortunately, it looks like the emmc has died. RMA it asap.
vin4yak said:
Unfortunately, it looks like the emmc has died. RMA it asap.
Click to expand...
Click to collapse
what is the emmc???
ahmedaziz555 said:
what is the emmc???
Click to expand...
Click to collapse
The internal flash memory module (32GB) of your phone.
Same thing happened to me. Was stuck in loading screen. Reset to factory settings. My apps would crash and I cant connect to my network. I also followed that same guide but it didn't help.
Yep, phone's internal storage is probably dead. RMA!
Just curious: for how much time did you use your phone before crashing? Was it completely stock?
Simonna said:
Just curious: for how much time did you use your phone before crashing? Was it completely stock?
Click to expand...
Click to collapse
Yes it was completely stock and i used the phone for 2 weeks

[Q]Datawind UbiSlate 7c+ edge tablet cwm loop

I flashed my ubislate 7c+ edge with the wrong recovery, and i believe it wiped all partitions.I have already tried every possible method found in any nook and corner of the internet.
I'm stuck in cwm recovery loop, it will boot to nothing but cwm recovery.
LiveSuite isnt working, i have like 4-5 images out of which atleast ONE of them must be the correct firmware(all of these i found on xda and the internet which was said that it would work) BUT none work since partitions are gone...
recovery says like cant mount system
cant mount emmc.... etc
Pheonix card doesnt work either, shows sprite error
I can make neither head nor tail of it.
Can anyone show me a way with which i could manually fix this tablet by either writing the partitions manually somehow or doing some magic trick(lol)? Please enlighten me.:crying::crying::crying:
bump
Edit : Hot news !!
After months of pure hopelessness ! I opened my back cover(for the 3rd time), moved the sticker and noted the board number(pcb number i guess?).
A sticker was covering it from being seen lol ! I noted it and googled the number.Found 3 firmwares for it. The first showed nothing in livesuit 1.07. Went till 3% and nothing happened. In livesuit 1.11 it showed x162 error(for a gazillionth time).I was hanging on the edge now. Had downloaded only 2 firmwares.
Tried the 2nd one and boom ! it went past 4% and i watched with glee as upgrade succeeded!! So my partition was wiped, but this managed to rewrite it.(Pats myself).
No datawind logo on boot. Everything works perfectly.
Link to working rom.I'll never try to upgrade this thing again lol .
NoobInToto said:
bump
Edit : Hot news !!
After months of pure hopelessness ! I opened my back cover(for the 3rd time), moved the sticker and noted the board number(pcb number i guess?).
A sticker was covering it from being seen lol ! I noted it and googled the number.Found 3 firmwares for it. The first showed nothing in livesuit 1.07. Went till 3% and nothing happened. In livesuit 1.11 it showed x162 error(for a gazillionth time).I was hanging on the edge now. Had downloaded only 2 firmwares.
Tried the 2nd one and boom ! it went past 4% and i watched with glee as upgrade succeeded!! So my partition was wiped, but this managed to rewrite it.(Pats myself).
No datawind logo on boot. Everything works perfectly.
Link to working rom.I'll never try to upgrade this thing again lol .
Click to expand...
Click to collapse
first procedure got error
*********************
CWM-based Recovery v
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/lost_log
E:Can't open /cache/recovery/lost_log
--- installation /sdcard/rom.zip
E:Can't mount /cache/recovery/last_install
E:Failed to open last_install: No such file or directory
second procedure got errors
******************************
UbiSlate 7c+ start only in recovery mode
and display following messages
CWM-based Recovery v6.o.1.2
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
trying to recover with recovering backup
it will display an error message like
Checking MD5 sums........
Erasing boot image...
Restoring system.......
E:format_volume: make_extf4fs failed on /dev/block/nandd
error while formatting system
is there any solutions for that
phonix card got error
aasifnasim said:
first procedure got error
*********************
CWM-based Recovery v
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/lost_log
E:Can't open /cache/recovery/lost_log
--- installation /sdcard/rom.zip
E:Can't mount /cache/recovery/last_install
E:Failed to open last_install: No such file or directory
second procedure got errors
******************************
UbiSlate 7c+ start only in recovery mode
and display following messages
CWM-based Recovery v6.o.1.2
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
trying to recover with recovering backup
it will display an error message like
Checking MD5 sums........
Erasing boot image...
Restoring system.......
E:format_volume: make_extf4fs failed on /dev/block/nandd
error while formatting system
is there any solutions for that
phonix card got error
Click to expand...
Click to collapse
Dude. You need to flash ROM via livesuit. Nothing else will work I promise.
Unzip that file and you will find the image to flash.
Good luck.
NoobInToto said:
Dude. You need to flash ROM via livesuit. Nothing else will work I promise.
Unzip that file and you will find the image to flash.
Good luck.
Click to expand...
Click to collapse
i also did that
but it goes upto 3% and gives and error after 3% update
aasifnasim said:
i also did that
but it goes upto 3% and gives and error after 3% update
Click to expand...
Click to collapse
What tablet do you have? Where is the camera located?
Dear Sir/Madam,
Greetings of the Day.
We regret any inconvenience caused.
This is to inform you that kindly share your contact no so that we can assist you further regarding the Service Center address.
Alternatively you can contact our support number at 18601800013.
Thank you so much for your patience and co-operation.
Regards,
DATAWIND INNOVATIONS.

[Q] OnePlus Bootloop / access to partition lost

2 weeks ago, my oneplus stucked in a bootloop. it just restarted itself and after the oneplus logo, endless bootanimation
Infos: Oneplus china version 64 GB black, not rooted, before error no twrp installed
I think I tried everything, different versions of twrp and via adb sideload tried to flash different official .zip versions of cygnmod. always the same error:
E: Unable to mount '/cache'
E: Unable to mount '/cache'
E: Unable to mount /data/meida/TWRP/ . twrps when trying to read settings file.
E: No valid storage partitions found for MTP.
E: Unable to mount '/data'
E: Unable to mount '/data'
I also tried different toolboxes (chinese omnipotent toolbox; oneplus one toolkit) flashing process was ok, but then it restarted and still bootloop.
does anyone know this problem and has a solution? thanks in advance...
+1
n J o y said:
+1
Click to expand...
Click to collapse
This sounds serious,
@timmaaa @timmaaa
waterdaan said:
This sounds serious,
@timmaaa @timmaaa
Click to expand...
Click to collapse
E: Unable to mount ' /data'
E: Unable to mount ' /cache'
E: Unable to mount storage.
E: Unable to mount /data/media during GUI start up.
and in fastboot trying to flash userdata (or anything)--> "FAILED (remote: failed to erase partition)".
The phone works only in fastboot or recovery, also with otg.
I think that OPO needs a script to recreate the partition in storage (?)
This is way over my head, you should wait for timmaaa to respond
n J o y said:
E: Unable to mount ' /data'
E: Unable to mount ' /cache'
E: Unable to mount storage.
E: Unable to mount /data/media during GUI start up.
and in fastboot trying to flash userdata (or anything)--> "FAILED (remote: failed to erase partition)".
The phone works only in fastboot or recovery, also with otg.
I think that OPO needs a script to recreate the partition in storage (?)
Click to expand...
Click to collapse
Go to my guide thread here:
http://forum.xda-developers.com/showthread.php?t=2839471
Follow the instructions in Section 8.
timmaaa said:
Go to my guide thread here:
http://forum.xda-developers.com/showthread.php?t=2839471
Follow the instructions in Section 8.
Click to expand...
Click to collapse
Thank you very much for helping everybody out
Much appreciated!!!
You're the best
timmaaa said:
Go to my guide thread here:
http://forum.xda-developers.com/showthread.php?t=2839471
Follow the instructions in Section 8.
Click to expand...
Click to collapse
If i try to flash something on fastboot it says --> "FAILED (remote: failed to erase partition)".
hi,
i already have 2 opos with this issue, one which is my own and one i ordered for a friend. the phone just rebooted itself at some point and was stuck in a bootloop. access to recovery and fastboot work, but recovery cant mount /system, /data, /persist, and /firmware. formatting doesnt help, flashing factory images gets stuck when flashing either system.img or userdata.img,
the first phone is already shipped out for rma and the second one will soon be shipped out.
maybe there is a problem with the memory chips themselves?
n J o y said:
If i try to flash something on fastboot it says --> "FAILED (remote: failed to erase partition)".
Click to expand...
Click to collapse
Ok, you might need to try one of these:
http://forum.xda-developers.com/showthread.php?t=2970390
http://forum.xda-developers.com/showthread.php?t=2991851
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
Transmitted via Bacon

[Q] Nexus 5 is stuck on boot screen with the circles after automatically turning off

Left my phone to charge over night and woke it up finding it turned off. (You can imagine the shock!!)
I turned it on back and it has been stuck on the boot screen with the flying dots since then. (Annoyed!!)
When I go into recovery mode and try deleting cache or wipe data I get a lot of error messages saying can't mount cache/recovery/log
Can't unlock boatloader to flash stock. It keeps relocking upon each restart.
Each time I wipe I get these error messages.
Wiping data...
Formatting/data...
- hide quoted text -
E: Failed to mount/cache (Invalid argument)
E: Can't mount /cache/ recovery/log
E: Can't open/cache/ recovery/ log
E: Failed to mount/cache (Invalid argument)
E: Can't mount /cache/ recovery/last_log
E: Can't open/cache/ recovery /last_log
E: Failed to mount/cache (Invalid argument)
E: Can't mount /cache/ recovery/last_install
E: Can't open/cache/ recovery/ last_install
Data wipe complete
- hide quoted text -
E: Failed to mount/cache (Invalid argument)
E: Can't mount /cache/ recovery/log
E: Can't open/cache/ recovery/ log
E: Failed to mount/cache (Invalid argument)
E: Can't mount /cache/ recovery/last_log
E: Can't open/cache/ recovery /last_log
E: Failed to mount/cache (Invalid argument)
E: Can't mount /cache/ recovery/last_install
E: Can't open/cache/ recovery/ last_install
E: Failed to mount/cache (Invalid argument)
Can someone please help me. I am really frustrated. Please don't tell me it's a hardware problem....
Um this sounds like a hardware problem. Sorry
Sent from my Nexus 5 using Tapatalk
Your NAND is fried. Definitely a hardware issue. RMA in you only option.
theesotericone said:
Your NAND is fried. Definitely a hardware issue. RMA in you only option.
Click to expand...
Click to collapse
I feel like crying right now. My phone does not have any warranty.
I've been compiling NAND failures for the last few months - am I right to assume your phone was 100 % stock?
So far, my WAG is related to the ftrim. We do know they've improved the way it works in the last couple of updates - and made it more aggressive as well.
That does track well with the emmc casualties I'm seeing. But it could be a red herring as well - wear and NAND quality being the most obvious factors.
I wonder, how many of the failures occurred after a night-long charging ( which triggers ftrim) ?
Sent from my Nexus 5 using XDA Free mobile app
Niflheimer said:
I've been compiling NAND failures for the last few months - am I right to assume your phone was 100 % stock?
So far, my WAG is related to the ftrim. We do know they've improved the way it works in the last couple of updates - and made it more aggressive as well.
That does track well with the emmc casualties I'm seeing. But it could be a red herring as well - wear and NAND quality being the most obvious factors.
I wonder, how many of the failures occurred after a night-long charging ( which triggers ftrim) ?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Yes 100% stock and unrooted.
I don't know. I woke up and found it turned off. Then I got a bunch of error messages when I tried wiping cache and data.
Is it by some chance possible to save my phone??? I really need to know. I've been up searching the web. I realize I'm not alone now.
Phone_evolution said:
Is it by some chance possible to save my phone???
Click to expand...
Click to collapse
No. The memory is bad. Sorry man those are the facts.
By normal means? A straight and categoric no. In theory we could try reformat it externally, maybe even read it but... It's not gonna happen - at least not affordable.
Buying the emmc chip and replacing it is doable - but again probably not affordable if u don't already have the tools.
Sent from my Nexus 5 using XDA Free mobile app
Niflheimer said:
By normal means? A straight and categoric no. In theory we could try reformat it externally, maybe even read it but... It's not gonna happen - at least not affordable.
Buying the emmc chip and replacing it is doable - but again probably not affordable if u don't already have the tools.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
In a recovery there is an option which is apply update from ADB. Neither that can help me???
Instead of buying parts to fix the device, you should look into getting a new replacement

Categories

Resources