Database Develop

Nexus 5 Error Updating

Received the phone. Insert SIM, unpackaged and booted up. Setup wifi and was told I *need* to install an update (you can't get around this).
Attempted to download the update. The progress bar filled up as you might expect, but when it got to the end it waited for a while, then restarted. This repeated 3 times.
Rebooted the phone manually and tried again. This time the system update download completed and the phone reboot automatically. Got part way through the update and encountered an error.
{
"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"
}
I've factory reset numerous times and repeated the process. It always ends in the same error.
My recovery console is as follows:
Can someone please upload a photo of their recovery mode details, I want to know if my version matches.

Benjamin Dobell said:
Received the phone. Insert SIM, unpackaged and booted up. Setup wifi and was told I *need* to install an update (you can't get around this).
Attempted to download the update. The progress bar filled up as you might expect, but when it got to the end it waited for a while, then restarted. This repeated 3 times.
Rebooted the phone manually and tried again. This time the system update download completed and the phone reboot automatically. Got part way through the update and encountered an error.
I've factory reset numerous times and repeated the process. It always ends in the same error.
My recovery console is as follows:
Can someone please upload a photo of their recovery mode details, I want to know if my version matches.
Click to expand...
Click to collapse
https://developers.google.com/android/nexus/images#hammerhead
It looks like D820 and D821 use the same firmware? Needs verification, but you'll probably need to flash that.

Flash the factory image from google
Sent from my Nexus 5 using Tapatalk

Vanhoud said:
Flash the factory image from google
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yeah, I already have the firmware downloaded on my PC... just not sure if that will impede my ability to make a warranty claim when it doesn't work

Yeah flashing worked... well Wallet crashed when it first boot. But it no longer needed to download and update and hence I setup the phone.

Benjamin Dobell said:
Yeah flashing worked... well Wallet crashed when it first boot. But it no longer needed to download and update and hence I setup the phone.
Click to expand...
Click to collapse
Woo-hoo!
Sent from my Nexus 5 using Tapatalk

Vanhoud said:
Woo-hoo!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Not so fast unfortunately.
Getting crashes all over the system, installing apps, opening settings etc.
Seems to be SecurityExceptions mostly

Benjamin Dobell said:
Not so fast unfortunately.
Getting crashes all over the system, installing apps, opening settings etc.
Seems to be SecurityExceptions mostly
Click to expand...
Click to collapse
Relock that Nexus and send it back. Hardware failure
Sent from my Nexus 5 using Tapatalk

Vanhoud said:
Relock that Nexus and send it back. Hardware failure
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Strangely enough, after relocking and rebooting I'm yet to see an exception. I'll stick with it for a little while longer and see how I go.

Damn, looks like I'm going to have to RMA.
Chrome crashes (in native code) and bluetooth tethering stops working after a while (whilst the phone itself can still access the Internet).
EDIT: Ugh, and just made my first phone call. I hope it's just this defective phone, but the call quality was disgusting.

Nexus 5 no command !!?
How do you solve the no command on update, I have just took it out of the box it completed the update did not restart and now says no command what do I do ?!!
---------- Post added at 11:53 AM ---------- Previous post was at 11:23 AM ----------
-Nexus5- said:
How do you solve the no command on update, I have just took it out of the box it completed the update did not restart and now says no command what do I do ?!!
Click to expand...
Click to collapse
ANYONE ?

[Q] Help! Corrupted screen on brand new Moto X after bootloader unlock

Hey guys,
I just opened my wife's new T-Mobile Moto X tonight. I wanted to unlock the bootloader, root it, and then relock it.
I unlocked the bootloader using Motorola's website. Worked just fine. Turned it on and set it up. The KitKat OTA came up. I downloaded it and hit install. It rebooted a couple of times into stock recovery, then it appeared to hang on the Motorola screen, but I didn't touch anything. It finally booted up but the screen was corrupted. I could swipe on the screen and feel the unlock ring but nothing was changing on the screen, and when I used the unlock ring the screen then went blank. I tried turning it off and then on again but it didn't fix anything. I then tried to reboot into fastboot and it looks like this:
{
"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"
}
If I type fastboot devices, then my device shows up. But the screen is always corrupted with that snow! Has anyone ever seen this? What do I do? The ONLY thing I did was unlock the bootloader and then run the OTA. How did this happen?!
Thanks so much for any help!
FF

frascaflyer said:
Hey guys,
I just opened my wife's new T-Mobile Moto X tonight. I wanted to unlock the bootloader, root it, and then relock it.
I unlocked the bootloader using Motorola's website. Worked just fine. Turned it on and set it up. The KitKat OTA came up. I downloaded it and hit install. It rebooted a couple of times into stock recovery, then it appeared to hang on the Motorola screen, but I didn't touch anything. It finally booted up but the screen was corrupted. I could swipe on the screen and feel the unlock ring but nothing was changing on the screen, and when I used the unlock ring the screen then went blank. I tried turning it off and then on again but it didn't fix anything. I then tried to reboot into fastboot and it looks like this:
View attachment 2449640
If I type fastboot devices, then my device shows up. But the screen is always corrupted with that snow! Has anyone ever seen this? What do I do? The ONLY thing I did was unlock the bootloader and then run the OTA. How did this happen?!
Thanks so much for any help!
FF
Click to expand...
Click to collapse
Try to rsdlite back to stock. Its not your fault, it has everything to do with the ota as far as I see, I assume you where running 4.2? Flash the lastest T-Mobile 4.4 sbf firmware.
Sent on my Moto X
---------- Post added at 12:54 AM ---------- Previous post was at 12:46 AM ----------
Here's the firmware http://forum.xda-developers.com/showthread.php?t=2538394
Sent from my A2109A using Tapatalk 4
---------- Post added at 12:56 AM ---------- Previous post was at 12:54 AM ----------
Heres rsdlite thread http://forum.xda-developers.com/showthread.php?t=2446515
Sent from my A2109A using Tapatalk 4

flashallthetime said:
Try to rsdlite back to stock. Its not your fault, it has everything to do with the ota as far as I see, I assume you where running 4.2? Flash the lastest T-Mobile 4.4 sbf firmware.
Click to expand...
Click to collapse
Thanks for the help. I just did this, twice, and it didn't fix anything. I still have the snow screen for the bootloader, and nothing on the screen for anything else. It makes noises when it boots, like the vibration and what I assume is some sort of Motorola jingle, but that's it. What the heck could the OTA have done?!

Never mind
Sent from my XT1053 using XDA Premium 4 mobile app

I'm going to guess hardware problems on this one. See if Tmobile will replace it.

frascaflyer said:
Thanks for the help. I just did this, twice, and it didn't fix anything. I still have the snow screen for the bootloader, and nothing on the screen for anything else. It makes noises when it boots, like the vibration and what I assume is some sort of Motorola jingle, but that's it. What the heck could the OTA have done?!
Click to expand...
Click to collapse
Are you able to boot into bootloader? Hold the power button, the screen should go dark. The keep holding the power button and hold the volume button (as soon as the screen goes dark) and it should boot into the bootloader.

chaoslimits said:
Are you able to boot into bootloader? Hold the power button, the screen should go dark. The keep holding the power button and hold the volume button (as soon as the screen goes dark) and it should boot into the bootloader.
Click to expand...
Click to collapse
Yeah, the screenshot I posted is what I get when I reboot into the bootloader. I know something is loading because when it is in that state and I use "fastboot devices" I see the device, and I can flash things to it, lock it, unlock it, etc. So RSD Lite worked, i.e., it flashed the stock image; it's just that the screen still doesn't work and the bootloader shows the screen that I posted.

frascaflyer said:
Yeah, the screenshot I posted is what I get when I reboot into the bootloader. I know something is loading because when it is in that state and I use "fastboot devices" I see the device, and I can flash things to it, lock it, unlock it, etc. So RSD Lite worked, i.e., it flashed the stock image; it's just that the screen still doesn't work and the bootloader shows the screen that I posted.
Click to expand...
Click to collapse
Yeah, I guess it sounds like a hardware issue like others have said. If you're not seeing the actual text in fastboot mode. Try calling Motorola, their customer support has been really great for me.

frascaflyer said:
Yeah, the screenshot I posted is what I get when I reboot into the bootloader. I know something is loading because when it is in that state and I use "fastboot devices" I see the device, and I can flash things to it, lock it, unlock it, etc. So RSD Lite worked, i.e., it flashed the stock image; it's just that the screen still doesn't work and the bootloader shows the screen that I posted.
Click to expand...
Click to collapse
Relock it and take it back, actually you really don't need to relock it as you can't even see anything in the fastboot screen
Sent on my Moto X

Yeah, I relocked it and I'm exchanging it for a new one. I was a little nervous since I had already requested the unlock code from the website, but they are processing the exchange no problem. Thanks for all the help... At least it doesn't look like I did anything or was missing an obvious fix!

frascaflyer said:
Yeah, I relocked it and I'm exchanging it for a new one. I was a little nervous since I had already requested the unlock code from the website, but they are processing the exchange no problem. Thanks for all the help... At least it doesn't look like I did anything or was missing an obvious fix!
Click to expand...
Click to collapse
No, if rsdlite doesn't work, well ITS A ZOMBIE PHONE
Sent from my A2109A using Tapatalk 4

can you try to fastboot flash a logo.bin from a previous release ?
- get the 4.2 release (From whoever posted it)
- put your device in fastboot mode
- flash only the logo.bin from this old image in the logo partition
$ fastboot flash logo logo.bin
$ fastboot reboot
flashallthetime said:
Relock it and take it back, actually you really don't need to relock it as you can't even see anything in the fastboot screen
Sent on my Moto X
Click to expand...
Click to collapse

planktoid said:
can you try to fastboot flash a logo.bin from a previous release ?
Click to expand...
Click to collapse
I don't see why not but I thought there's only one boot logo anyways
Sent from my A2109A using Tapatalk 4

flashallthetime said:
I don't see why not but I thought there's only one boot logo anyways
Sent from my A2109A using Tapatalk 4
Click to expand...
Click to collapse
Just try it
Sent from my XT1058 using XDA Premium 4 mobile app

[Q] Stuck On White HTC Boot Screen PLEASE HELP!!!

When I first turn on it'll stay stuck in HTC white screen logo till battery dies.
If I hold volume rocker and power button to try to factory reset it'll try to initiate but then show and a phone logo with red exclamation mark.
I am almost positive i can restore this phone to working order because i remember a while back i put a galaxy s3 into similar condition and restored it using a program.. Ive been out of this stuff for a while so i forgot how i did it with the s3.
I WAS GIVEN THIS HTC AND IT WAS LIKE THIS WHEN I GOT IT.

plotgee said:
When I first turn on it'll stay stuck in HTC white screen logo till battery dies.
If I hold volume rocker and power button to try to factory reset it'll try to initiate but then show and a phone logo with red exclamation mark.
I am almost positive i can restore this phone to working order because i remember a while back i put a galaxy s3 into similar condition and restored it using a program.. Ive been out of this stuff for a while so i forgot how i did it with the s3.
I WAS GIVEN THIS HTC AND IT WAS LIKE THIS WHEN I GOT IT.
Click to expand...
Click to collapse
Don't worry, this problem has cropped up before, and you're right, it is fixable. This is most commonly attributed to some weirdness with the boot.img flashed to your phone. Firstly, do you have a Vivid, Velocity, or Raider? And what provider does it use (e.g. AT&T)?
The first thing you'll want to try and do is pop out the battery, put it back in, then hold "volume down" and "power" until you get to the bootloader (it sounds like you've already gotten there):
{
"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"
}
You'll notice in the top portion, mine says "unlocked". Yours may say this, but may also say "locked" or "re-locked".
First thing's first; you'll want to download FASTBOOT (http://www.mediafire.com/download/9ylow29klhccc0x/Fastboot.zip)
and the HTC drivers (this is what I had in my flashing folder, so I upped it to mega: https://mega.co.nz/#!CV5RxY7L!Z_VNph4KoGyYKJJjoUCGPAFZ7xZPOWRbvH2UKsCXCi0)
just run the htc drivers and follow directions, nothing too major. Extract the contents of "fastboot.zip" to somewhere that's easy to access and remember (such as c:\FASTBOOT).
We're not going to do anything yet, this is just preparation.
If your bootloader is "locked" or "re-locked", then you can try restoring the original firmware with RUU. You'll want to read this thread first though:
http://forum.xda-developers.com/showthread.php?t=1562890
Always need to be careful.
If you are "unlocked", then you need to boot your phone into the bootloader, select "fastboot" (by pressing power when "fastboot" is highlighted), and connect the phone to your computer via a data usb cable. Then, open a command prompt window, and type in: "<c:\FASTBOOT\fastboot.exe> oem lock", where <c:\FASTBOOT\fastboot.exe> is replaced with the location of your fastboot.exe.
I would recommend flashing the recovery image located in the thread I linked to just before (follow instructions provided), and only THEN applying an RUU update. Which RUU you apply is dependent on which device you have.
If anything is unclear, or you have any questions, PLEASE ask in reply to this post; it's better to go slowly and be sure of what you're doing.
sidenote:
I noticed you said you had previously owned an S3 and managed to fix the problem with that; if you are pretty familiar with flashing roms, you can also try to flash a custom ROM and see if that fixes your problem (guides should be on Vivid General or Q&A).

projectisaac said:
Don't worry, this problem has cropped up before, and you're right, it is fixable. This is most commonly attributed to some weirdness with the boot.img flashed to your phone. Firstly, do you have a Vivid, Velocity, or Raider? And what provider does it use (e.g. AT&T)?
The first thing you'll want to try and do is pop out the battery, put it back in, then hold "volume down" and "power" until you get to the bootloader (it sounds like you've already gotten there):
You'll notice in the top portion, mine says "unlocked". Yours may say this, but may also say "locked" or "re-locked".
First thing's first; you'll want to download FASTBOOT (http://www.mediafire.com/download/9ylow29klhccc0x/Fastboot.zip)
and the HTC drivers (this is what I had in my flashing folder, so I upped it to mega: https://mega.co.nz/#!CV5RxY7L!Z_VNph4KoGyYKJJjoUCGPAFZ7xZPOWRbvH2UKsCXCi0)
just run the htc drivers and follow directions, nothing too major. Extract the contents of "fastboot.zip" to somewhere that's easy to access and remember (such as c:\FASTBOOT).
We're not going to do anything yet, this is just preparation.
If your bootloader is "locked" or "re-locked", then you can try restoring the original firmware with RUU. You'll want to read this thread first though:
http://forum.xda-developers.com/showthread.php?t=1562890
Always need to be careful.
If you are "unlocked", then you need to boot your phone into the bootloader, select "fastboot" (by pressing power when "fastboot" is highlighted), and connect the phone to your computer via a data usb cable. Then, open a command prompt window, and type in: "<c:\FASTBOOT\fastboot.exe> oem lock", where <c:\FASTBOOT\fastboot.exe> is replaced with the location of your fastboot.exe.
I would recommend flashing the recovery image located in the thread I linked to just before (follow instructions provided), and only THEN applying an RUU update. Which RUU you apply is dependent on which device you have.
If anything is unclear, or you have any questions, PLEASE ask in reply to this post; it's better to go slowly and be sure of what you're doing.
sidenote:
I noticed you said you had previously owned an S3 and managed to fix the problem with that; if you are pretty familiar with flashing roms, you can also try to flash a custom ROM and see if that fixes your problem (guides should be on Vivid General or Q&A).
Click to expand...
Click to collapse
I have the vivid , and yes it says *** locked ***
I downloaded and installed everything you listed above and I am currently going through RUU process as I type this..
Thanks, I hope this works.

Fingers crossed here. Let me know what happens.
Sent from my Vivid 4G using xda app-developers app

Alright! So apparently this solution worked (got a PM from OP)!

New oneplus 3T unbrick tutorial. (errno:258 solved)

Hi guys!
I got a really painful hard brick, i thought the device would be completely dead (msmdownloadtool always said errno: 258 while downloading system.img)
So i decided to mix two tutorials and i finally fixed it. There you have it.
1.) Make sure driver signature enforcement is disabled.
2.) Try these drivers,one of them might work too :
https://www.androidfilehost.com/?fid=24052804347799753
https://www.androidfilehost.com/?fid=24269982086990168
https://www.androidfilehost.com/?fid=24349802275800175
https://www.androidfilehost.com/?fid=24349802275800173
https://www.androidfilehost.com/?fid=24349802275800171
3.)
Download this :- http://www.mediafire.com/download/4a...6wc67/Qualcomm 1.00.11.rar
Keep phone disconnected from PC.
Open the folder "qc" and install the Test Certificate in the following Stores: Trusted Root, Trusted Publisher, Third-Party Root and Personal
Run the Qualcomm setup wizard (also located in the qc folder)
When completed, restart your PC again with Driver Signature Disabled. (Optional but preferred)
The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install.
When all of this is done, press the power button for 40 seconds and then, plug your phone while you press volume up. On control panel/devices and printers you will see your phone as Qualcomm 9008 or something like that.
Unbricktool(OP3T): https://mega.nz/#!Q1YnTTAT!gnLf6NEkS...1-vReKx7B1VVpI
run this tool as administrator and a green text will pop.
Do not use the front usb of your pc, try with the ones in the back.
Do not try the oneplus 3 unbrick tutorials, they wont work and you can kill your device since the unbrick oneplus 3 tutorials are using oneplus 3 exclusive files.

nobody?

I have the exact same problem ?

nikolajkracht said:
I have the exact same problem
Click to expand...
Click to collapse
after 1 night the device did not boot anymore and when i try to run the msmdownloadtool it always fails at the system.img step. I think i'll send it to oneplus and see if they can fix it or replace the device, ill tell them that i tried to update to android 7 and the device did not boot anymore

You should all try https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306 and follow it to the letter. It saved my OPT3 for sure.

gee2012 said:
You should all try https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306 and follow it to the letter. It saved my OPT3 for sure.
Click to expand...
Click to collapse
we are using that tutorial and the phone is still dead haha

Sonificado said:
we are using that tutorial and the phone is still dead haha
Click to expand...
Click to collapse
Try it again, maybe you made a misstake . My phone couldnt boot anymore too after an OTA update because the system partition couldn`t be read, but this tutorial saved it.

gee2012 said:
Try it again, maybe you made a misstake . My phone couldnt boot anymore too after an OTA update because the system partition couldn`t be read, but this tutorial saved it.
Click to expand...
Click to collapse
at the moment my phone does not vibrate/logo/nothing, i can only press vol+ and plug it on the computer and the let goes yellow but when i run the tool and it fails, the led turns orange

Sonificado said:
at the moment my phone does not vibrate/logo/nothing, i can only press vol+ and plug it on the computer and the let goes yellow but when i run the tool and it fails, the led turns orange
Click to expand...
Click to collapse
Are you sure the Qualcomm drivers we`re installed correctly?

gee2012 said:
Are you sure the Qualcomm drivers we`re installed correctly?
Click to expand...
Click to collapse
just tried again and it happened again
{
"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"
}

Sonificado said:
just tried again and it happened again
Click to expand...
Click to collapse
I had to try multiple times too before all went well to be honest. Try rebooting the PC and give it a few more shots, you got nothing to loose anyway.

gee2012 said:
I had to try multiple times too before all went well to be honest. Try rebooting the PC and give it a few more shots, you got nothing to loose anyway.
Click to expand...
Click to collapse
you think oneplus support will help me?

Sonificado said:
you think oneplus support will help me?
Click to expand...
Click to collapse
Think so, they offered me remote assistence to revive the phone but i fixed it myself luckily. Give them a ring or send a mail for assistence and i`am sure they`ll help you

gee2012 said:
Think so, they offered me remote assistence to revive the phone but i fixed it myself luckily. Give them a ring or send a mail for assistence and i`am sure they`ll help you
Click to expand...
Click to collapse
ill talk with them on the spanish chat tomorrow, let's see what they say.

Sonificado said:
ill talk with them on the spanish chat tomorrow, let's see what they say.
Click to expand...
Click to collapse
Oke, good luck then, i`am sure it will all be worked out.

I had the same problem with my phone, you should try to install a different version of the MSM tool and (maybe) try flashing different zips till one works. I had that error and a few other error codes after hard bricking and i finally got it to work before i called support. There's a lot of variables, sometimes you just gotta play around with it when you're hard bricked, worth a shot.

Sonificado said:
just tried again and it happened again
Click to expand...
Click to collapse
Random one try changing the com port of your device to 39. Wouldn't work on any port but that for me for some reason.

manor7777 said:
Random one try changing the com port of your device to 39. Wouldn't work on any port but that for me for some reason.
Click to expand...
Click to collapse
It worked on port 11 for me. Guess it differs from user to user.

gee2012 said:
It worked on port 11 for me. Guess it differs from user to user.
Click to expand...
Click to collapse
I think it depends if things on your pc are using com ports. Glad to know it worked and that I could kind of help you

manor7777 said:
Random one try changing the com port of your device to 39. Wouldn't work on any port but that for me for some reason.
Click to expand...
Click to collapse
gee2012 said:
It worked on port 11 for me. Guess it differs from user to user.
Click to expand...
Click to collapse
IT WORKED!!!!!! i just changed the port to another one and the msm download tool went right to the end

The users Data Partition has crashed

I updated my honor 3c manually to B310. It worked find for some days and now I see this error message when i switch it on. Tried hard reset and everything else that i know but no luck.
{
"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"
}
Is it a hardware issue? Do i have to change board or what? Any idea?

:bump: anyone??

Hi.
It's a rare problem with Huawei phones, Sadly. My friend faced the same issue on honor 4C and the only was to change the motherboard. It's that the Memory chip gets corrupted and the only way is to replace it. That's what I have known so far and the solution I got was to change the motherboard. It's not a software problem but a hardware one. Not a pro I am.

asif7372 said:
I updated my honor 3c manually to B310. It worked find for some days and now I see this error message when i switch it on. Tried hard reset and everything else that i know but no luck.
Is it a hardware issue? Do i have to change board or what? Any idea?
Click to expand...
Click to collapse
Its a software issue AFAIK. did u tried to factory reset ur phone ?

he mentioned he already made hard reset

There were only two things for data partition corrupt .
1) using a wrong filesystem which the system cant identify
2) hardware corrupted.
Am pretty sure if second happend ur phone is dead .
But it seems it bootsup and assume this as a soft brick and u can get back to life if u reply me as fast as i reply u .

gopinaidu77 said:
There were only two things for data partition corrupt .
1) using a wrong filesystem which the system cant identify
2) hardware corrupted.
Am pretty sure if second happend ur phone is dead .
But it seems it bootsup and assume this as a soft brick and u can get back to life if u reply me as fast as i reply u .
Click to expand...
Click to collapse
2nd one is highly irrecoverable.
Sent from my Honor 8 using XDA Labs

adriansticoid said:
2nd one is highly irrecoverable.
Click to expand...
Click to collapse
Yes it is , when second one happens . Only way is by getting a replacement with a new phone or board

gopinaidu77 said:
Yes it is , when second one happens . Only way is by getting a replacement with a new phone or board
Click to expand...
Click to collapse
I'd say it's better to get a new phone. To save time and hassle.
Sent from my Honor 8 using XDA Labs

adriansticoid said:
I'd say it's better to get a new phone. To save time and hassle.
Click to expand...
Click to collapse
Let him try in service center first

But adrian , if sc can replace he might get a brand new phone

same happened with my honor 3c.. stuck on this error screen.. phone not getting stock
same happened with my honor 3c.. stuck on this error screen.. phone not getting stock rom in recovery.. not getting format.. what should i do now.. please help me help me please...

Barve.shashank said:
same happened with my honor 3c.. stuck on this error screen.. phone not getting stock rom in recovery.. not getting format.. what should i do now.. please help me help me please...
Click to expand...
Click to collapse
How did it end up into this state have you done any modifications ?
Like flashing any rom or installing any update ?

Honor 3c partition crash
miststudent2011 said:
How did it end up into this state have you done any modifications ?
Like flashing any rom or installing any update ?
Click to expand...
Click to collapse
Thanks for reply. I did nothing like this. I bought it in june 2014. Then it was officially kitkat updated in 2015. After that everything was going well. Just did 2-3 times the factory reset and stock rom because of hanging problem and setting stopped issue. All was going well. Then suddenly it happened one day when i was using it normally. I was already tried to connect with pc but not responding. Tried to install stock rom in recovery mode but it failed. Now what should i do?

Barve.shashank said:
Thanks for reply. I did nothing like this. I bought it in june 2014. Then it was officially kitkat updated in 2015. After that everything was going well. Just did 2-3 times the factory reset and stock rom because of hanging problem and setting stopped issue. All was going well. Then suddenly it happened one day when i was using it normally. I was already tried to connect with pc but not responding. Tried to install stock rom in recovery mode but it failed. Now what should i do?
Click to expand...
Click to collapse
Do you have unlocked bootloader ?

Honor 3c partition crash
miststudent2011 said:
Do you have unlocked bootloader ?
Click to expand...
Click to collapse
No it's not unlocked and i never tried it.

Barve.shashank said:
No it's not unlocked and i never tried it.
Click to expand...
Click to collapse
Can you unlock your bootloader?
So our work becomes easier

Barve.shashank said:
No it's not unlocked and i never tried it.
Click to expand...
Click to collapse
U can unlock it as said by mist

Honor 3c partition crash
miststudent2011 said:
Can you unlock your bootloader?
So our work becomes easier
Click to expand...
Click to collapse
I can not connect mobile to pc. When i connected then only charging status appear.. So how can I do it?

Barve.shashank said:
I can not connect mobile to pc. When i connected then only charging status appear.. So how can I do it?
Click to expand...
Click to collapse
Force shutdown your phone and restart it by pressing vol+ and power button .
Report what happen when done so.