Database Info

Boot stops at 'Google', can't mout sdcard in cwm

Hi,
since this morning I have this problem that my Nexus S just boots until the Google logo appears.
I have no idea what caused this. I was just reinstalling the youtube app and rebooted after that and it booted.
Then I noticed that my phone would not change the screen orientation and because it worked in the past I started another reboot. But then it got stuck at the Google logo.
To solve this problem I just wanted to flash my nandroid backup but that didn't work as well cause the recovery was not able to mount the sdcard.
E:Can't mount /sdcard
Does anyone have an idea how to solve this problem? By the way is it possible to pull the Nandroid backup from the phone to my computer with ADB for example. Would be great because (of course) I just have an backup on my phone... (but if not... well, **** happens)
Thanks in advance!

PedroBustamonte said:
Hi,
since this morning I have this problem that my Nexus S just boots until the Google logo appears.
I have no idea what caused this. I was just reinstalling the youtube app and rebooted after that and it booted.
Then I noticed that my phone would not change the screen orientation and because it worked in the past I started another reboot. But then it got stuck at the Google logo.
To solve this problem I just wanted to flash my nandroid backup but that didn't work as well cause the recovery was not able to mount the sdcard.
E:Can't mount /sdcard
Does anyone have an idea how to solve this problem? By the way is it possible to pull the Nandroid backup from the phone to my computer with ADB for example. Would be great because (of course) I just have an backup on my phone... (but if not... well, **** happens)
Thanks in advance!
Click to expand...
Click to collapse
flasgh stock via fastboot and wipe everything DONE!

i had this problem when i flashed a non-cm kernel on a cm-based rom. try flashing a different kernel. know what kernel your rom is compatible to,

Cascabreu said:
flasgh stock via fastboot and wipe everything DONE!
Click to expand...
Click to collapse
So there's no way to get the content of the sdcard before I wipe everything?
ej8989 said:
i had this problem when i flashed a non-cm kernel on a cm-based rom. try flashing a different kernel. know what kernel your rom is compatible to,
Click to expand...
Click to collapse
I'm using ParanoidAndroid with Mamite (the version for cm based roms since PA is also based on cm)

PedroBustamonte said:
So there's no way to get the content of the sdcard before I wipe everything?
I'm using ParanoidAndroid with Mamite (the version for cm based roms since PA is also based on cm)
Click to expand...
Click to collapse
Go to mounts and storage in CWM Recovery and "mount usb storage". That will let you get to your SD card to backup. Then I suggest just a clean wipe and start over.
Note: mount /sdcard just mounts it to the phone. You are wanting to mount it to your computer to pull the files off the external.

mdean1981 said:
Go to mounts and storage in CWM Recovery and "mount usb storage". That will let you get to your SD card to backup. Then I suggest just a clean wipe and start over.
Note: mount /sdcard just mounts it to the phone. You are wanting to mount it to your computer to pull the files off the external.
Click to expand...
Click to collapse
Yup thank you. Already tried that and a lot of other stuff. Seems like my phone's broken. I can't write on or erase /system or /sdcard. I'll try today to lock the bootloader and then unlock it. Maybe that solves the problem...

It will also wipe everything if I remember well
Envoyé depuis mon Nexus S avec Tapatalk

PedroBustamonte said:
Yup thank you. Already tried that and a lot of other stuff. Seems like my phone's broken. I can't write on or erase /system or /sdcard. I'll try today to lock the bootloader and then unlock it. Maybe that solves the problem...
Click to expand...
Click to collapse
dont lock it cuz u wont be able to unlock it after. unlocking requires being able to erase the sdcard
tested it my self yesterday on a phone with the same issue

Cascabreu said:
dont lock it cuz u wont be able to unlock it after. unlocking requires being able to erase the sdcard
tested it my self yesterday on a phone with the same issue
Click to expand...
Click to collapse
Yes you're right. But I really can't think of any thing I could try.

PedroBustamonte said:
Yes you're right. But I really can't think of any thing I could try.
Click to expand...
Click to collapse
It's interesting and maybe fortuite that this is happening to you just as something almost equal happens to me (see here: http://forum.xda-developers.com/showthread.php?t=1972447 ) You should also enter the recovery via adb from your computer if you have it, and check if a) you have mmc* files in /dev/block and b) have mmc error messages in dmesg (in the phone: "dmesg|grep mmc" and look for lines with "error" in them).
Btw to the person who suggested flashing stock thorough fastboot, do you mean stock system, system+boot or system+boot+recovery ? and where could I find those stock .img please? Mine's an i9020a

Blissfull said:
It's interesting and maybe fortuite that this is happening to you just as something almost equal happens to me (see here: http://forum.xda-developers.com/showthread.php?t=1972447 ) You should also enter the recovery via adb from your computer if you have it, and check if a) you have mmc* files in /dev/block and b) have mmc error messages in dmesg (in the phone: "dmesg|grep mmc" and look for lines with "error" in them).
Btw to the person who suggested flashing stock thorough fastboot, do you mean stock system, system+boot or system+boot+recovery ? and where could I find those stock .img please? Mine's an i9020a
Click to expand...
Click to collapse
Factory Images for Nexus Devices
https://developers.google.com/android/nexus/images

Hi ^^
I had the same problem with my Nexus S a long time ago and never found out how to solve it. It seems that the internal memory is corrupted and nothing but replacing the motherboard can solve it. Since I bought mine in the USA but I live in Belgium I never got mine repaired. Sometimes I come back here to see if there is still no solution but each time I'm disappointed...
Sorry.

PedroBustamonte said:
Yes you're right. But I really can't think of any thing I could try.
Click to expand...
Click to collapse
Cascabreu said:
dont lock it cuz u wont be able to unlock it after. unlocking requires being able to erase the sdcard
tested it my self yesterday on a phone with the same issue
Click to expand...
Click to collapse
I can confirm this. I had the same thing happen to my Nexus S 4G recently. I was never able to salvage any data off the sdcard no matter what I tried (various mounting attempts in recovery, any adb command I thought might be helpful, etc.). As a last resort I tried to lock/unlock the bootloader - once I locked it, I was unable to unlock it again, it just froze up after asking me if I was sure I wanted to unlock. I guess that's what happens when the internal sdcard goes to hell. I ended up taking it to my local Sprint store and they replaced the phone with a refurbished one from Samsung (for approximately $35).

[Q] Stuck in bootloop.

Hi everyone.
I have the following problem with a Nexus 5: During an update, the system crashed. The phone is now stuck in an endless bootloop, trying to install the update. When left long enough, the update screens eventually come up, but you are immediately blasted with a ton of errors and no matter what you do, you are unable to complete the update. This, however, is not the problem.
I have tried various utilities in order to flash the phone back to factory settings. I have made use of Unified Android ToolKit, as well as Nexus Root Toolkit, but a problem with the phone itself is preventing me from flashing it and the problem is as follows: I can access the phone via USB, as well as the bootloader, but when I unlock the bootloader to start the flashing, it immediately locks itself again and I'm unable to start the flash process.
I've searched for other instances in which the bootloader won't unlock, but I can't find any information. Is there perhaps a hardware problem preventing me from unlocking the bootloader or can someone help me find a solution to this problem?

Mystical_Titan said:
I've searched for other instances in which the bootloader won't unlock, but I can't find any information. Is there perhaps a hardware problem preventing me from unlocking the bootloader or can someone help me find a solution to this problem?
Click to expand...
Click to collapse
If the lock state reverts on a reboot, 99 times out of 100, it means the internal memory has an issue. RMA.

rootSU said:
If the lock state reverts on a reboot, 99 times out of 100, it means the internal memory has an issue. RMA.
Click to expand...
Click to collapse
Thanks for the fast response. :good:

Mystical_Titan said:
Thanks for the fast response. :good:
Click to expand...
Click to collapse
No probs. Sounds like the update got stuck at the bootloader flash and corrupted. It's probably not a fatal NAND issue, rather corrupt partition or two but it usually means sending it in.
You can try the LG flashtool as a last resort before doing so though, as you never know...
You can find a link to it in the sticky thread in my signature. Best to stay away from actual "toolkits" though and either use fastboot manually or LG flash tool, although fastboot probably cant help you here - just saying for future ref...

Mystical_Titan said:
Hi everyone.
I have the following problem with a Nexus 5: During an update, the system crashed. The phone is now stuck in an endless bootloop, trying to install the update. When left long enough, the update screens eventually come up, but you are immediately blasted with a ton of errors and no matter what you do, you are unable to complete the update. This, however, is not the problem.
I have tried various utilities in order to flash the phone back to factory settings. I have made use of Unified Android ToolKit, as well as Nexus Root Toolkit, but a problem with the phone itself is preventing me from flashing it and the problem is as follows: I can access the phone via USB, as well as the bootloader, but when I unlock the bootloader to start the flashing, it immediately locks itself again and I'm unable to start the flash process.
I've searched for other instances in which the bootloader won't unlock, but I can't find any information. Is there perhaps a hardware problem preventing me from unlocking the bootloader or can someone help me find a solution to this problem?
Click to expand...
Click to collapse
happened to me while installing the new SNAPSHOT version of Cyanogenmod, I wiped everything and reflashed it and it works

BruKnowsBest said:
happened to me while installing the new SNAPSHOT version of Cyanogenmod, I wiped everything and reflashed it and it works
Click to expand...
Click to collapse
Can anyone suggest some steps for me to try before I RMA the phone? Although, being unable to unlock the bootloader probably limits my options.

Mystical_Titan said:
Can anyone suggest some steps for me to try before I RMA the phone? Although, being unable to unlock the bootloader probably limits my options.
Click to expand...
Click to collapse
I was stuck in the boot animation and when it opened there was a lot of system errors and it would reboot by itself over and over again.
what fixed it was to do a wipe cache and dalvik and reinstall it

BruKnowsBest said:
I was stuck in the boot animation and when it opened there was a lot of system errors and it would reboot by itself over and over again.
what fixed it was to do a wipe cache and dalvik and reinstall it
Click to expand...
Click to collapse
I tried the 'wipe cache' as well, but it returns a bunch of errors as well. I'm starting to think the NAND is screwed. What is dalvik?

Mystical_Titan said:
I tried the 'wipe cache' as well, but it returns a bunch of errors as well. I'm starting to think the NAND is screwed. What is dalvik?
Click to expand...
Click to collapse
Dalvik cannot break your bootloader. Your only option was use lg flashtool and if that failed, RMA. Let's not get false hopes and waste time not doing this.
Sent from my Nexus 5 using Tapatalk

rootSU said:
Dalvik cannot break your bootloader. Your only option was use lg flashtool and if that failed, RMA. Let's not get false hopes and waste time not doing this.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I completely forgot that you mentioned the LG Flashtool, I feel like such an idiot. I'll try that tomorrow as a last resort.

No worries
Sent from my Nexus 5 using Tapatalk

rootSU said:
Dalvik cannot break your bootloader. Your only option was use lg flashtool and if that failed, RMA. Let's not get false hopes and waste time not doing this.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
i thought about LG FLASHTOOL but decided to try reinstaling the rom cuz i had no other option since i forgot to leave a backup rom on the device. So I did it as if I was installing a brand new rom Wiped dalvik, cache and system then reflashed the rom and then the gapps. Even tho it was the same ROM file I had a different outcome. It's working fine now but I did go back to the nightlies after it started working again just to be safe.
Now... people may have a different outcome when trying to solve this issue but this actually worked for me after having a minor heart-attack thinking I was gonna lose all my stuff

BruKnowsBest said:
i thought about LG FLASHTOOL but decided to try reinstaling the rom cuz i had no other option since i forgot to leave a backup rom on the device. So I did it as if I was installing a brand new rom Wiped dalvik, cache and system then reflashed the rom and then the gapps. Even tho it was the same ROM file I had a different outcome. It's working fine now but I did go back to the nightlies after it started working again just to be safe.
Now... people may have a different outcome when trying to solve this issue but this actually worked for me after having a minor heart-attack thinking I was gonna lose all my stuff
Click to expand...
Click to collapse
Yes, but your issue is different to the OP's. His bootloader lock state reverts whenever he changes it. This is a pretty much "fatal" issue. What you did cannot help him unfortunately.

rootSU said:
Yes, but your issue is different to the OP's. His bootloader lock state reverts whenever he changes it. This is a pretty much "fatal" issue. What you did cannot help him unfortunately.
Click to expand...
Click to collapse
oh ok, I misunderstood

rootSU said:
No worries
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It speaks about a KDZ file. What is it and where would I find it?

Mystical_Titan said:
It speaks about a KDZ file. What is it and where would I find it?
Click to expand...
Click to collapse
Not sure, never used it. Are you following the Nexus 5 LG Flash tool guide? If not, have a look. You can get to it via my signature

rootSU said:
Not sure, never used it. Are you following the Nexus 5 LG Flash tool guide? If not, have a look. You can get to it via my signature
Click to expand...
Click to collapse
Well, that's that. This phone is done.

Yup. RMA
Sent from my Nexus 5 using Tapatalk

[Q] Nexus 5 Bootloop

So let me start by saying I am 100% a noob, and I have read many threads trying to get to the bottom of my problem to no avail. I am sorry if there is a solution for my problem somewhere, I've been working on this issue for 24 hours and have yet to find it.
My girlfriend was apparently using google maps on here relatively new phone (running 5.0.1) and it crashed. Upon restarting it was stuck on the coloured dots screen for several hours. She has not installed any third party apps, only those from the playstore and not too many of them at that.
I tried factory reset and received a bunch of errors about failing to load the E:// or something like that. The phone still would not boot up.
I downloaded minimal fastboot thinger on my windows 8.1 laptop and tried to flash a new image of 5.0.1 on it, IIRC I received errors about E:// again
Got Wugfresh NRT and tried TWRP wiped all (still saw some stuff about E:// failing to mount and such) then tried to unroot flash stock with soft brick/bootloop checked.
Still bootlooped for over an hour when I started it up.
Tried flashing 4.4.4 instead. It worked. Phone booted up. Gallery/Camera do not work however at this point. Tried updating to 5.0.1.... phone restarted bootloop for 8 hours and counting.
Flashed 4.4.4 again, Followed Full Driver Installation Guide in NRT exactly. Tried Flash Stock + Unroot with Device is on/Normal checked this time instead. Now it has been colored dots screen for about 20 minutes.
So I can load 4.4.4 but no matter how I've tried to install lollipop 5.0.1, it stays on booting screen forever.
What do?
Thank you so much in advance and apologies for being a noob.
EDIT: More googling today. Looks like my E:/Persist partition is corrupted or something, trying to figure out how to repair it right now.

Anjo_Smash said:
So let me start by saying I am 100% a noob, and I have read many threads trying to get to the bottom of my problem to no avail. I am sorry if there is a solution for my problem somewhere, I've been working on this issue for 24 hours and have yet to find it.
My girlfriend was apparently using google maps on here relatively new phone (running 5.0.1) and it crashed. Upon restarting it was stuck on the coloured dots screen for several hours. She has not installed any third party apps, only those from the playstore and not too many of them at that.
I tried factory reset and received a bunch of errors about failing to load the E:// or something like that. The phone still would not boot up.
I downloaded minimal fastboot thinger on my windows 8.1 laptop and tried to flash a new image of 5.0.1 on it, IIRC I received errors about E:// again
Got Wugfresh NRT and tried TWRP wiped all (still saw some stuff about E:// failing to mount and such) then tried to unroot flash stock with soft brick/bootloop checked.
Still bootlooped for over an hour when I started it up.
Tried flashing 4.4.4 instead. It worked. Phone booted up. Gallery/Camera do not work however at this point. Tried updating to 5.0.1.... phone restarted bootloop for 8 hours and counting.
Flashed 4.4.4 again, Followed Full Driver Installation Guide in NRT exactly. Tried Flash Stock + Unroot with Device is on/Normal checked this time instead. Now it has been colored dots screen for about 20 minutes.
So I can load 4.4.4 but no matter how I've tried to install lollipop 5.0.1, it stays on booting screen forever.
What do?
Thank you so much in advance and apologies for being a noob.
Click to expand...
Click to collapse
If I can bet it must be a corrupted persist partition. Lollipop will not boot if its gets corrupted but kitkat will do. If you could tell what is the actual error you see in twrp or cwm recovery then we could identfy the actual problem. But I am 90% sure the mount error is about persist partition.

bitdomo said:
If I can bet it must be a corrupted persist partition. Lollipop will not boot if its gets corrupted but kitkat will do. If you could tell what is the actual error you see in twrp or cwm recovery then we could identfy the actual problem. But I am 90% sure the mount error is about persist partition.
Click to expand...
Click to collapse
You are correct sir I literally just identified that as the problem 5 minutes ago. Now the question is how do I fix it.

Anjo_Smash said:
You are correct sir I literally just identified that as the problem 5 minutes ago. Now the question is how do I fix it.
Click to expand...
Click to collapse
I made a thread about it. Here it is http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576

bitdomo said:
I made a thread about it. Here is it http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
Click to expand...
Click to collapse
I'm actually looking at that right now! Downloading Java and Android SDK atm. Of course still a little shaky on a couple terms in your guide hopefully I can sort it out. Really confused as to how Google Maps on a vanilla nexus 5 could corrupt a partition like that, its all google endorsed and official. They should be fixing my phone not me lol.

Anjo_Smash said:
I'm actually looking at that right now! Downloading Java and Android SDK atm. Of course still a little shaky on a couple terms in your guide hopefully I can sort it out. Really confused as to how Google Maps on a vanilla nexus 5 could corrupt a partition like that, its all google endorsed and official. They should be fixing my phone not me lol.
Click to expand...
Click to collapse
If you want to make it quick then allow me to join to your pc through teamviewer. Send your ID and Passowrd to my e-mail: [email protected]
If you try to do it alone and you face a problem then I might not be here, because it is already past 11:30pm here.

bitdomo said:
If you want to make it quick then allow me to join to your pc through teamviewer. Send your ID and Passowrd to my e-mail: [email protected]
If you try to do it alone and you face a problem then I might not be here, because it is already past 11:30pm here.
Click to expand...
Click to collapse
Thanks for the offer. I'll try on my own and get back to you maybe tomorrow if I can't get it down.

Alright so I am definitely having problems running adb shell. even if I change the directory in cmd to my adb.exe location (android\android-sdk\platform-tools) I keep getting the error adb shell is not a recognized blah blah blah....
NVM got it working. Whenever I get frustrated enough to make a post I end up finally finding a solution.

ALRIGHT I have Lollipop up and running thanks to your guide on fixing persist partition. Thank you so much! Question: I have a nexus 5 and it does not have an sd card. I'm not sure how to proceed in doing the steps you described involving mac addresses. I did use a hex editor and make those files, but not sure where to put them in my phones internal storage, and how to direct adb to said location. Any help with that?

Anjo_Smash said:
ALRIGHT I have Lollipop up and running thanks to your guide on fixing persist partition. Thank you so much! Question: I have a nexus 5 and it does not have an sd card. I'm not sure how to proceed in doing the steps you described involving mac addresses. I did use a hex editor and make those files, but not sure where to put them in my phones internal storage, and how to direct adb to said location. Any help with that?
Click to expand...
Click to collapse
Just copy them to the root of your internal storage, then follow the guide.
I mean you just open the phone's internal storage from your PC and you dont open any folder. You just copy it there.
The guide is for nexus 5, but some people refer to the internal storage as sdcard too. I know it is a bit confusing. Thanks to point it out. I will make clear in my guide now.

AH I see ok I will do that tonight. Ran in to another problem though it may be related to the mac address thing I haven't done yet, not sure how that all works. The phone randomly restarts every few minutes and it won't connect to the carrier either. Also if it matters I left the boot loader unlocked for now until the phone is working properly, if that affects anything.

Anjo_Smash said:
AH I see ok I will do that tonight. Ran in to another problem though it may be related to the mac address thing I haven't done yet, not sure how that all works. The phone randomly restarts every few minutes and it won't connect to the carrier either. Also if it matters I left the boot loader unlocked for now until the phone is working properly, if that affects anything.
Click to expand...
Click to collapse
The lock state of the bootloader does not matter, but this random reboots after a few minutes is something to worry about. Your phone should not do that after formating persist partition.

bitdomo said:
The lock state of the bootloader does not matter, but this random reboots after a few minutes is something to worry about. Your phone should not do that after formating persist partition.
Click to expand...
Click to collapse
Should I try formatting it again?

Anjo_Smash said:
Should I try formatting it again?
Click to expand...
Click to collapse
Give another try formating persist, but I am here now. So, if you want I can do everything for you through teamviewer. You just have to send the log in informations to my email address.

bitdomo said:
Give another try formating persist, but I am here now. So, if you want I can do everything for you through teamviewer. You just have to send the log in informations to my email address.
Click to expand...
Click to collapse
Ok I'm going to install team viewer then.

bitdomo said:
Give another try formating persist, but I am here now. So, if you want I can do everything for you through teamviewer. You just have to send the log in informations to my email address.
Click to expand...
Click to collapse
I'm all set up, so let me know when you are available friend, thanks for your help.

Anjo_Smash said:
I'm all set up, so let me know when you are available friend, thanks for your help.
Click to expand...
Click to collapse
I am here, send the login infos -> [email protected]

23GB System Data Usage?? internal memory shrunk to 8GB

I just noticed that after a factory restore, my device shows 23GB system data used. Is this normal?
Free space is only 7.45GB even though this is a 32GB model.
I'm not sure what it was before, but only noticing after flashing the H959 firmware.
Does anyone else have this issue?
EDIT: it seems that my device shows a total size of 8gb when connected to pc.. but in settings > storage it shows 32gb with 23gb used by system data

No. I have 13GB free with a bunch of apps installed.

it seems that my device's sd card somehow resized itself to 8gb. I have no idea how to fix this.

Hoping for some feedback on this.. I installed parted on the phone to take a look at the partitions
This seems really confusing:
48 5755MB 31.2GB 25.5GB ext4 userdata
25.5GB is being used for userdata after a factory reset.

Do you have a lot of music and vids in your storage?
Sent from my GT-I8190 using XDA Free mobile app
---------- Post added at 08:32 PM ---------- Previous post was at 08:31 PM ----------
A factory reset doesn't delet them.
Sent from my GT-I8190 using XDA Free mobile app

No
this is the storage being used after a factory reset, so with absolutely no data on the phone, apparently 25.5GB is in userdata somewhere

So it seems that this is caused by flashing the 955 rom on a non-955 device. I guess it has to do with the 16gb/32gb storage space difference.
So moral of the story: If you don't have a 955, don't flash a 955 rom.
...That aside, does anyone know how I can fix this? flashing back to the original rom doesn't work. Does this mean the partitions are permanently screwed up? Will there at least be some hope when a custom recovery becomes available?

I'm in the same boat. After flashing 955 rom on my 959, there becomes 23.9 GB of system data occupied on my drive. Maybe if the bootloader is unlocked, then we can edit the partitions, but for now, it'd be gone for good. My plan is to wait till the official 959 15A rollout and then go to service center and blame the update made my drive occupied with junks. .. hope it works.

dd if=/dev/zero of=/dev/block/mmcblk0pXX
bbs.angeeks.com/thread-3933743-1-2.html

ddfzl said:
dd if=/dev/zero of=/dev/block/mmcblk0pXX
bbs.angeeks.com/thread-3933743-1-2.html
Click to expand...
Click to collapse
seems like there's a fix to the problem. but Google Translate does a terrible job to make me understand what they're saying. And their attachment is also not available to me coz I'm not a registered member. Can you help us more with the solution?

spiderx_mm said:
seems like there's a fix to the problem. but Google Translate does a terrible job to make me understand what they're saying. And their attachment is also not available to me coz I'm not a registered member. Can you help us more with the solution?
Click to expand...
Click to collapse
https://mega.co.nz/#!408CFTJZ!gz_UWMHArmC0AyYkyTMhW0Sw0amDBKpXPhhcVDNBa5U

as far as it make sense to me, what they've written there is you need to run the app and the phone will automatically rebooted. if the phone rebooted successfully back, then the fix would failed.
in order to fix successfully, the phone must show an error. then you can flash a 959 rom to complete the fix.
so far I've tried, the phone always successfully rebooted. I saw "/system/bin/sh: su: not found" error. So I guess the phone must be rooted. I'm on V10D which I'm not sure if it can be rooted. Well, at least .. we know this thing can be fixed. let's try to root and try again.

spiderx_mm said:
as far as it make sense to me, what they've written there is you need to run the app and the phone will automatically rebooted. if the phone rebooted successfully back, then the fix would failed.
in order to fix successfully, the phone must show an error. then you can flash a 959 rom to complete the fix.
so far I've tried, the phone always successfully rebooted. I saw "/system/bin/sh: su: not found" error. So I guess the phone must be rooted. I'm on V10D which I'm not sure if it can be rooted. Well, at least .. we know this thing can be fixed. let's try to root and try again.
Click to expand...
Click to collapse
1:root your device
2nly test pass on my H959,you'll better not try on other device,maybe this can destory your partition

ddfzl said:
1:root your device
2nly test pass on my H959,you'll better not try on other device,maybe this can destory your partition
Click to expand...
Click to collapse
my device is H959 but I'm on version V10D which i don't know how to root. ..
Edit:
OK, I'll downgrade to V10C and then try again. Hope that would work.

spiderx_mm said:
my device is H959 but I'm on version V10D which i don't know how to root. ..
Edit:
OK, I'll downgrade to V10C and then try again. Hope that would work.
Click to expand...
Click to collapse
http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW48GDJF220GAD97C1AFYGB/H95910C_00.kdz
root your device
only test pass on my H959,you'll better not try on other device,maybe this can destory your partition
confirm that you have installed correct LG drive,and switch on USB debug
if your phone restarted in 5 sec and with no error tips ,that mean falled,then you need to run this tool one more times until your phone hint you like 'setup error' and cannot into desktop,or your phone cannot power on,then just neet to flash KDZ of correct verson.32G will be back when it done.

ddfzl said:
http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW48GDJF220GAD97C1AFYGB/H95910C_00.kdz
root your device
only test pass on my H959,you'll better not try on other device,maybe this can destory your partition
confirm that you have installed correct LG drive,and switch on USB debug
if your phone restarted in 5 sec and with no error tips ,that mean falled,then you need to run this tool one more times until your phone hint you like 'setup error' and cannot into desktop,or your phone cannot power on,then just neet to flash KDZ of correct verson.32G will be back when it done.
Click to expand...
Click to collapse
now on V10C and rooted. when i run the repair exe, i got this error "error: device not found". the phone is still rebooting successfully. :crying:

spiderx_mm said:
now on V10C and rooted. when i run the repair exe, i got this error "error: device not found". the phone is still rebooting successfully. :crying:
Click to expand...
Click to collapse
confirm that you have installed correct LG drive,and switch on USB debug

ddfzl said:
confirm that you have installed correct LG drive,and switch on USB debug
Click to expand...
Click to collapse
yes, it's confirmed. and it works!!!! it works for apparently no reason :laugh: I tried repeatedly as per the instruction, and finally the phone rebooted into safe mode. then I put it back to download mode and flash the latest firmware (V10D-SEA-XX) and now the 23.9 GB System data is reduced to 9.44 GB. !

AWESOME thanks guys I will try this later

My LG Flex2 F510 after running repair my Memory have just only 9GB.Please help me restore my partion....

Internal Storage seems gone

Hey, i have oneplus 6.I have unlocked the bootloader,i have stock rom and my phone was rooted with magisk. Few days ago i unrooted my phone, clicked uninstall in magisk and it started unrooting. Then if it was done i clicked reboot and after that my phone was only able to boot into twrp. It couldnt boot into ROM.Nothing on the internet helped,so i flashed my stock ROM again (i was on my stock rom already) from flash drive. It went well and my phone booted up. But since that my phone doesn't show internal storage. In file manager it shows 10/128 GB used, but if i try to look into my storage it doesnt show anything. Also if i try to take photos, it cant,and i also cant download and update several apps in play store.
Can somebody help me? Can somebody explain what happened?Does somebody know how to fix it if its even possible?
Ty for help :')

It happens to me once. I think storage encryption is broken. try factory reset

kimmix05 said:
It happens to me once. I think storage encryption is broken. try factory reset
Click to expand...
Click to collapse
Hi kimmix, and thx trying to help. I havent done the factory reset yet, but i want to say that my phone doesnt have root either twrp anymore. Unlocked bootloader is ofc still there. Do i need to do factory reset from phone settings then(settings/system/recovery and resets/factory reset), somehow from my stock recovery or i need to put twrp again to my phone (from pc)?

This happened me a day or two ago.
Drove me really crazy, tried bunch of stuff flashing full zips over and over. Nothing fixed it.
Then inside twrp I used fix contents button (if I recall correctly it should be under advanced menu)
And that totally solved my problem, It should solve yours too.
Before factory resetting boot twrp via fastboot and try.
Hope this helps because that gave me some sleepless nights.

abasba said:
This happened me a day or two ago.
Drove me really crazy, tried bunch of stuff flashing full zips over and over. Nothing fixed it.
Then inside twrp I used fix contents button (if I recall correctly it should be under advanced menu)
And that totally solved my problem, It should solve yours too.
Before factory resetting boot twrp via fastboot and try.
Hope this helps because that gave me some sleepless nights.
Click to expand...
Click to collapse
Hey, ty for help. I'm gonna try this as soon as possible :')

Hope it helps. Otherwise you always can use msmdownloadtool to fix issues.

abasba said:
This happened me a day or two ago.
Drove me really crazy, tried bunch of stuff flashing full zips over and over. Nothing fixed it.
Then inside twrp I used fix contents button (if I recall correctly it should be under advanced menu)
And that totally solved my problem, It should solve yours too.
Before factory resetting boot twrp via fastboot and try.
Hope this helps because that gave me some sleepless nights.
Click to expand...
Click to collapse
Hey again, one little question. Did understand you correctly...
1. Put twrp again to device (i have done this for now)
2. Do factory reset (havent done)
3.Do 'fix contents' (havent done)
Ty for help

Zenquad said:
Hey, ty for help. I'm gonna try this as soon as possible :')
Click to expand...
Click to collapse
Zenquad said:
Hey again, one little question. Did understand you correctly...
1. Put twrp again to device (i have done this for now)
2. Do factory reset (havent done)
3.Do 'fix contents' (havent done)
Ty for help
Click to expand...
Click to collapse
Skip step 2 for now, if it does not help then sure flash oos on both slots then use fix contents again

abasba said:
This happened me a day or two ago.
Drove me really crazy, tried bunch of stuff flashing full zips over and over. Nothing fixed it.
Then inside twrp I used fix contents button (if I recall correctly it should be under advanced menu)
And that totally solved my problem, It should solve yours too.
Before factory resetting boot twrp via fastboot and try.
Hope this helps because that gave me some sleepless nights.
Click to expand...
Click to collapse
Hey, sry for so many queations but...
I looked around in this forum and saw people having same-kind of problems. The replys told to do the 'format data'. Will it help my problem to be fixed?
And if it does, so i nees to just:
1. Boot to twrp
2. Select wipe then format data then confirmation
3. Then reboot
Is it just simple, am i missing some steps, please tell me. And thank you very much for help

abasba said:
Skip step 2 for now, if it does not help then sure flash oos on both slots then use fix contents again
Click to expand...
Click to collapse
Ty for answering, did you mean :
1. Boot to twrp
2. Do 'fix contents'
3. Boot to system
And if doesnt work then
1. Boot to twrp
2. Do factory reset
3. Flash stock rom to A
4. Boot to B
5. Flash stock rom to B
6. Wipe cache
7. Do 'fix contents'
8. Reboot
Am i right?

abasba said:
This happened me a day or two ago.
Drove me really crazy, tried bunch of stuff flashing full zips over and over. Nothing fixed it.
Then inside twrp I used fix contents button (if I recall correctly it should be under advanced menu)
And that totally solved my problem, It should solve yours too.
Before factory resetting boot twrp via fastboot and try.
Hope this helps because that gave me some sleepless nights.
Click to expand...
Click to collapse
Talking about 'fix contents'.
If i try do this it shows "it can cause system unable to boot up". Can you tell me, in wich situation or what can cause that after doing 'fix contents', device is not able to boot up.
Ty for help :')

abasba said:
Skip step 2 for now, if it does not help then sure flash oos on both slots then use fix contents again
Click to expand...
Click to collapse
And if 'format data' helps to fix this problem also then wich solution should i choose:
1. Fixing contents
2. Formating data

Zenquad said:
And if 'format data' helps to fix this problem also then wich solution should i choose:
1. Fixing contents
2. Formating data
Click to expand...
Click to collapse
I have no idea if formatting data helps or not actually. You can try it
---------- Post added at 09:35 PM ---------- Previous post was at 09:33 PM ----------
Zenquad said:
Talking about 'fix contents'.
If i try do this it shows "it can cause system unable to boot up". Can you tell me, in wich situation or what can cause that after doing 'fix contents', device is not able to boot up.
Ty for help :')
Click to expand...
Click to collapse
I am not a dev nor I have no idea what does fix contents actually do. It just fixed my issue so I thought it could solve yours too

or you could just reflash stock rom from msmdownload tool to lessen the hassle lol.

blaspheme000 said:
or you could just reflash stock rom from msmdownload tool to lessen the hassle lol.
Click to expand...
Click to collapse
Hey, ok ill try )

abasba said:
This happened me a day or two ago.
Drove me really crazy, tried bunch of stuff flashing full zips over and over. Nothing fixed it.
Then inside twrp I used fix contents button (if I recall correctly it should be under advanced menu)
And that totally solved my problem, It should solve yours too.
Before factory resetting boot twrp via fastboot and try.
Hope this helps because that gave me some sleepless nights.
Click to expand...
Click to collapse
After decrypting the cell phone I have the same problem. I did what you suggested and it all turned out. Storage came back a thousand thanks

avirale123 said:
After decrypting the cell phone I have the same problem. I did what you suggested and it all turned out. Storage came back a thousand thanks
Click to expand...
Click to collapse
Hey, i saw 'fix contexts' fixed your problem. What is "phone decrypting" and how did you do that? Maybe i did something similar that made my internal storage "go away".

Zenquad said:
Hey, i saw 'fix contexts' fixed your problem. What is "phone decrypting" and how did you do that? Maybe i did something similar that made my internal storage "go away".
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-6/how-to/tutorial-decrypt-flash-rom-pie-oreo-roms-t3838643

avirale123 said:
https://forum.xda-developers.com/oneplus-6/how-to/tutorial-decrypt-flash-rom-pie-oreo-roms-t3838643
Click to expand...
Click to collapse
Hey again!
So i see you did that, what was in the instructions. And then your internal storage "was gone"? Then you did 'fix contexts'? Am i right?

Zenquad said:
Hey again!
So i see you did that, what was in the instructions. And then your internal storage "was gone"? Then you did 'fix contexts'? Am i right?
Click to expand...
Click to collapse
exactly. If it does not help you do not waste more time and use the tool to recover the system