Database Develop

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.

xt1254 hangs on bootloader/recovery

Hi all, ive been running custom roms on my phone ever since sunshine was released for it.
In the past 6 months or so, my phone has gotten horrendously bad at booting.
When i turn it on, it will hang on the bootloader warning screen for 2 to 3 minutes before showing any sign that anything is happening.
Im really at a loss, ive done everything but a complete format and sideload.
Not really sure what other information would be required.
what should i do?
also every few days i have to go into apns and click one of the verizon ones again before my data will work, but that might just be a rom issue.

jombo2323 said:
xt1254 hangs on bootloader/recovery
Hi all, ive been running custom roms on my phone ever since sunshine was released for it.
In the past 6 months or so, my phone has gotten horrendously bad at booting.
When i turn it on, it will hang on the bootloader warning screen for 2 to 3 minutes before showing any sign that anything is happening.
Im really at a loss, ive done everything but a complete format and sideload.
Not really sure what other information would be required.
what should i do?
Click to expand...
Click to collapse
At first I thought you were saying your phone was booting to the bootloader screen or even booting to TWRP recovery, which would be very strange. That's happened to people before... which means the phone is really messed up.
But reading your actual write-up, (if you wrote it correctly) instead your phone is just NORMALLY booting. It's just taking a long time. Your phone is just staying stuck on the boot image, which is not the bootloader or recovery screens. It's just an image you see before the boot animation starts until finally you see your normal Android system GUI. In your case, it's the "bootloader warning screen" which is something you should replace.
THIS is the bootloader screen:
{
"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"
}
But instead you're seeing this, right?
It's the boot image Motorola has replaced to warn you your bootloader is unlocked. Yeah, I did it on purpose! As did you. No need to see it every day. You can flash a replacement boot image very easily in TWRP or ADB. <There's several to choose from.
WHY is it hanging on the boot image? You are right that something is wrong, but I don't think your phone is very messed up -- at least it's not booting to the bootloader screen!
You've tried clearing all the caches in TWRP? You've tried dirty flashing your ROM again? Sometimes something can get slightly corrupted and re-flashing your ROM over itself can fix the issue. Clearing all the caches in TWRP and letting all the apps re-optimize can also fix some issues.
Do you have any add-on xposed modules? I would temporarily disable all exposed modules, reboot a couple of times, see what happens? You can always re-enable them later. Xposed modules can conflict with your normal ROM functions and should be used very sparingly. Some modules like Gravity Box are really another ROM and settings in Gravity Box can conflict with settings in your ROM. But to a lesser degree so can almost any other xposed module.
Have you restored your TWRP backup which you made before all this happened? You do have a good TWRP backup, right?
Last, yeah, if none of that works, factory reset and reinstall the ROM.

Are you encrypted? I've noticed that once you encrypt the storage that the phone takes forever to boot. I haven't found any way around that and someone with more knowledge of the hardware than me mentioned that it's because the drivers for HW decrypt acceleration are missing.

I will add to this as I am having the same issue and have moved to another 32GB Turbo for the time being but now I'm having Radio issues with this one.
My 64 was encrypted, running CF's 1.0.8, xposed. Doing restoring the factory image did the same thing. Only thing is now that i think about it TWRP didn't ask for my pin for encryption though like it was before so it may not be encryped. I'm going to be doing some factory images this weekend and see if i can find out the issue and if I find anything I'll post back. Only thing that sucks is I only have one good screen between the two phones lol

Ugh, sorry for the lack of response. Ive been really busy.
To answer all questions. Ive done everything but wipe some crap with fastboot commands and performing a clean flash of the rom. Im on resurrection remix right now, i think i want to change though because my battery life is kinda ****.
Also no xposed, etc, just the basic rom.
Sorry for taking so long and thanks for the responses!

Le S3 x626 bricked issue

Hi, I have checked this thread as I experienced the same issue(If confused what I'm talking about read
www chinaphonearena com/forum/Thread-Question-LeEco-Le-S3-X626-Helio-X20-Bricked ), I was able to get past the phone buttons not working and was able to flash a new firmware. But this led to another issue considering the system.
For one, I am unable to unlock my bootloader, I just receive the error : FAILED (remote: unlock operation is not allowed), and there is no way fro me to get in my android as it always stays on the LeEco POWERED BY ANDROID screen, which then shuts down and reboots.#
As well as this, the display is now very unusual: the LeEco logo is coloured green white and yellow, the display is flipped horizontally and mirrored vertically.
{
"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"
}
The image above shows this.
It's VERY annoying and I hope it can be solved.
NOTE!! I can still use locked bootloader/fastboot, can't use adb and can use SP FLASH TOOL

You need to power the phone and wait till boots. Enter the flipped UI enable developer mode and unlock the bootloader.
All the control are flipped so be patient.
After that enter fastboot and flash the original rom

damtrx_ said:
You need to power the phone and wait till boots. Enter the flipped UI enable developer mode and unlock the bootloader.
All the control are flipped so be patient.
After that enter fastboot and flash the original rom
Click to expand...
Click to collapse
Thanks for the reply, I fixed the issue the same day, I just fixed it using the second part to tickernel's red light unbrick tutorial, I completely missed it out. The rom I was using where everything was inverted was just to unbrick the phone, then after I'd have to flash the rom provided by tickernel to fix. It worked again and an advantage was that there was no more ORANGE state, I didn't have to patch to hide the message nor wait the 5 seconds, so now I can flash custom roms on my phone without the message. The method you provided wasn't the fix, before opening this thread I double checked and saw your method, but thanks anyway .

it was necessary to use a mirror. for example, in the bathroom

after brick and ressurect what write in (telephone settings) model?

Shekor said:
after brick and ressurect what write in (telephone settings) model?
Click to expand...
Click to collapse
it depends on which model is taken ROM. It does not play any role. Can be changed to Build.prop

Kychera22 said:
it depends on which model is taken ROM. It does not play any role. Can be changed to Build.prop
Click to expand...
Click to collapse
after bad ressurects i return my device le x626. to le x620 with eui 5.8.018S (stab.) it works normal. But was some bugs with 4g on (turn phone off) and google programs don's start.
But i fixed it all, now it works great, but i think is it bad?

take the stock firmware 28. and install. why use the old version? maybe get my firmware.
to use google apps. you need to download google installer, then after installation, in the settings give permissions to all Google apps.
and correctly to do so: to install firmware, then to start system and to configure it. and then only install the google gapps.

Update on unbrick
With my phone unbricked, it now works perfectly. But now the battery drains very fast. It drops by around 25% in less than half an hour with normal use such as watching videos on youtube in "360p" with all my apps closed, but still the battery drains. I have tried flashing different roms and clearing all partitions in twrp and flashing the CUOCO AND WOLFRED x.28s custom stock roms, but still the issue persists. This is very unusual as before my phone bricked, the battery would hold up for at least an hour before falling by 10 to 20 %. Does anyone have any speculations on why or any fixes? Please help.
UPDATE: I fixed by flashing the international version system.img only if you need it send me a message and I'll put up a link.

ASUS ROG Phone 2 E:Failed...

Hello, I was watching YT a few weeks ago and the phone (ASUS ROG Phone 2 tencent edition version 8/128) decided to reboot by itself. It done it before but this time it wouldn't get past the starting logo and restart again! It would keep looping until the battery ran empty... SO I booted in recovery mode, tried to factory reset and get E:Failed to save locale.
A friend has been trying to help me fix the phone and this was the result (screenshot). He can't figure it out.
{
"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 tried searching the forum with no luck. Anyone know if this problem is fixable and could guide us in the right direction?

did you backup your phone precautiously before
if you havent u lost all your important files
is your phone under warranty

Lavithiran -=-=-= said:
if you havent u lost all your important files
Click to expand...
Click to collapse
Hey, haven't backed up before at any point and don't have warrenty. Is there a way to get the phone working again?
Can't find old screenshot; if I remember correctly the first time I tried to factory reset after looping it said "driver E missing" something along that line. Up to that point never tried to change anything on the device by using a usb or PC.

mosa00 said:
Hello, I was watching YT a few weeks ago and the phone (ASUS ROG Phone 2 tencent edition version 8/128) decided to reboot by itself. It done it before but this time it wouldn't get past the starting logo and restart again! It would keep looping until the battery ran empty... SO I booted in recovery mode, tried to factory reset and get E:Failed to save locale.
A friend has been trying to help me fix the phone and this was the result (screenshot). He can't figure it out.
View attachment 5640881
I've tried searching the forum with no luck. Anyone know if this problem is fixable and could guide us in the right direction?
Click to expand...
Click to collapse
Do it this way:
1. Make a Wipe
2. Download this file https://androidfilehost.com/?fid=8889791610682901175
3. Run fastboot bootloader and connect to computer (side port)
4. Unpack and run "flashall_AFT.cmd" wait for the phone to reset and start up.
Should help.

mosa00 said:
Hey, haven't backed up before at any point and don't have warrenty. Is there a way to get the phone working again?
Can't find old screenshot; if I remember correctly the first time I tried to factory reset after looping it said "driver E missing" something along that line. Up to that point never tried to change anything on the device by using a usb or PC.
Click to expand...
Click to collapse
i dont think so you can retrive your old files

My phone is FUBAR'D

Wrote this message to Google support. I don't suspect I'll hear anything from anybody but I'll post here for my fellow Pixel brothers and sisters that perhaps may experience something similar. I'm disappointed. I know the phone is relatively inexpensive (cheap) and you get what you pay for (?) but this points to bad hardware, simple and plain. How does my 2019 LG G7 on android 9 (!!??) outlast a 4a5g?? I expected more but, alas it is what it is. Peace out, Pixel 4a5g.
"Over my time since I've been on Google Fi I've used and bought a few devices. I started out with a Pixel 4a, then upgraded to the 4a5g and now I'm on the 6 Pro. I love Google phones and have always been a fan since days of the Nexus devices. I was disappointed when my 4a5g started bootlooping 2 months ago. It has never been unlocked or have I attempted to flash ROMs on it. It would eventually stop and boot back up, last for a week or so then bootloop again. This time around it continued for a longer period of time. When I went to try to do a factory reset it is stuck in Fastboot saying "no valid slot to boot." Based on the research on this issue I realize the phone is pretty much dead, even though I can use Google's own Flash tool to flash factory images for it. The phone is no longer under warranty and your support doesn't give any other options than paying for repair upt to $350, which is beyond the worth of the device. I am disappointed that the phone bootlooped to the point of death after only owning the device for LESS THAN 2 YEARS. (Nov 2020). My previous device, a LG G7 that I previously had on Verizon lasted longer, and my dad still uses that phone to this day. I purchased that phone in March of 2019. I know this post will only fall on deaf ears and no one can do anything about it but for the first time in a long time I'm disappointed by a Google phone."
{
"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"
}

Why not reflash since those ROMs are easily available? You have access fastboot, no?

Kaynejulian said:
Why not reflash since those ROMs are easily available? You have access fastboot, no?
Click to expand...
Click to collapse
I've been flashing and re-flashing this phone for 2 days.

What's the output? What is error code? What commands are you using? What does fastboot getvar all show?

I'm using the android flash site to flash the phone with a stock image from Google. It goes through the process with no errors, then it acts like it's going to boot, bootloops twice then goes to the pictured fastboot mode showing "no valid slot to boot." Fastboot shows the build number (android 11 or 12 depending on which I've flashed) but when i try to wipe data i get /system/bin/tune2fs is missing.

I thought mine was also. I used this site to get it back to a running rom
Web installer · ProtonAOSP
Quickly and easily install ProtonAOSP on your phone in as little as 4 minutes.
protonaosp.org

Thordim said:
I thought mine was also. I used this site to get it back to a running rom
Web installer · ProtonAOSP
Quickly and easily install ProtonAOSP on your phone in as little as 4 minutes.
protonaosp.org
Click to expand...
Click to collapse
Thanks for trying, I get file format is not recognized error message. I tried manually installing the Pixel Experience ROM and even got that ROM's recovery to flash, and flashed the ROM, all went well exactly as the website said but then it said that the phone is corrupted and bootlooped. Flashed the stock 12.1 image using the Android Flash Tool, back to above error message after 2 bootloops.

Wonder if there is any way to check NAND integrity on this device. It's like you flash and reflash and somehow it loses it "bits". Which is weird. I would be temped to try to "semi-brick" it and see if a manual flash (via fastbboot) over all the individual partitions one at a time, would resolve issue, assuing NAND is still ok. That sucks man. I'm sorry.

smokejumper76 said:
Wonder if there is any way to check NAND integrity on this device. It's like you flash and reflash and somehow it loses it "bits". Which is weird. I would be temped to try to "semi-brick" it and see if a manual flash (via fastbboot) over all the individual partitions one at a time, would resolve issue, assuing NAND is still ok. That sucks man. I'm sorry.
Click to expand...
Click to collapse
What confuses me is that even when I manually flash a custom ROM or stock image it goes through the process just fine, no error messages. It boots up, does the little G circle animation and right as it's about to go to the next screen.. bam, it reboots. Does it a second time, then immediately goes to the above-mentioned screen shot. So I think somewhere the hardware or storage drive or whatever you want to call it is broken. I wonder if I triggered it when I tried to enter fastboot during one of the times I tried to factory reset it. I dunno... I'm attempted to let the battery die then recharge and try again or something.
It's ok, I'm sort of over it.. my feelings are hurt at this point. I've been Rooting and Romming since the days of Moto Droid X2, Galaxy Note 2 (before vzw locked their bootloader) and the Nexus 6, so when I got into the Pixel phones I was relieved when I didn't feel like I didn't have to do all of that just to get the phone to feeling like it's working smoothly. I have a 4a that has a broken screen, this one and a 6 Pro (factory), so I've really liked the Google Pixel devices and the software experience. So for this to start bootlooping even without me tinkering with it for over a year is just a disappointment.

If anyone can understand it, here are screenshots of the recover.log file from the recovery screen.

Tried flashing the first Android 11 OTA image from the Google Images site, A4 October 2020 as it's a unlocked Google purchased phone. I noticed it goes through the motions but says status 0 then further that system/bin/tune2fs is missing so nothing is being written. This must be happening every time I try to flash but I'm not actually seeing that nothing's happening on the Google flash website.

Have you already tried the Android Flash Tool? Given the circumstances I would recommend checking the Force flash all partitions box.

yeah, that was the first thing i did, tried 11, 12, 13 beta, 13 official... nothing. Lineage too.