[Q] Internal Memory issue - Optimus L3, L5, L7 Q&A, Help & Troubleshooting

Hi im having trouble restoring my phone to factory, i tried everything, kdz, key combination, backup option, it seems that no matter what i change on the phone, it stays the same, i think it can be an internal memory issue, sort of locked, or write protected. Also i can't push files to device. the phone is not rooted and i have stock.

Matias.s said:
Hi im having trouble restoring my phone to factory, i tried everything, kdz, key combination, backup option, it seems that no matter what i change on the phone, it stays the same, i think it can be an internal memory issue, sort of locked, or write protected. Also i can't push files to device. the phone is not rooted and i have stock.
Click to expand...
Click to collapse
I have the same problem. Any idea to solve it?

Related

Galaxy S4 stops working

Hey guys, i've got a Galaxy s4 running 4.4.2 android version and all of a sudden my device started freezing and stopped working, I don't even know how to describe the problem, i haven't installed new apps or downloaded anything since a month and this problem just started yesterday.
Basically, my phone just stops working all of a sudden, the "X app isn't responding. Do you want to close it?" with whatever app I have on the moment, and after that, the screen just freezes, I can lock my phone and unlock it, but nothing happens, just the same screen frozen, and I have to reset my phone, but the problem is that I have that problem happen to me like 5 minutes after I restart my phone, so basically, my phone is unusable because of this problem, and I don't know what to do to fix this. Any suggestion guys?
I would definitely try and back up any data you need from the phone. Then, I would perform a factory reset from recovery to see it that solves the issue.
audit13 said:
I would definitely try and back up any data you need from the phone. Then, I would perform a factory reset from recovery to see it that solves the issue.
Click to expand...
Click to collapse
I would if I could, but actually I don't think I have enough time to backup all my data before the device freezes, but in the end, if there is no other possible solution, I will just factory reset it even without backup
Thanks, though.
jadriangz said:
I would if I could, but actually I don't think I have enough time to backup all my data before the device freezes, but in the end, if there is no other possible solution, I will just factory reset it even without backup
Thanks, though.
Click to expand...
Click to collapse
Try pressing the menu button when powering up your phone. that way you will get into safe mode. Maybe then you can make backups.
or
You can flash a custom recovery. Like TWRP and then boot into the recovery. There you have Aroma filemanager and then you can transfer the files to an external sd card.
Lennyz1988 said:
Try pressing the menu button when powering up your phone. that way you will get into safe mode. Maybe then you can make backups.
or
You can flash a custom recovery. Like TWRP and then boot into the recovery. There you have Aroma filemanager and then you can transfer the files to an external sd card.
Click to expand...
Click to collapse
Great! thanks man, I'll definitley try those options :good: .

"Decryption unsuccessful" message on stock 7.0/7.1.1

This is the second time I get this message. First time was on stock Android 7.0. next time, ~2 weeks later on stock Android 7.1.1. To revive my phone I had to perform a factory reset twice.
What causes this message? Is it software or hardware related? I assumed the former, but the fact that it happened twice after a reset and on a new version made me wonder...
I'm heading to a country without 3G coverage and barely any WiFi, so if this happens then, I'm screwed on 2 levels: -Loss of pictures, due to not able to back-up -Not able to reset, since that requires WiFi.
Anyone else who had this issue? Any recommendations, RMA?
Full error message: "Decryption unsuccessful" The password that you entered is correct but unfortunately your data is corrupt. To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google account"
Thx.
You can set the phone to back up without wifi if you are good with that I've had my phone since December I have not had that happen odd.
Sent from my Nexus 6P using Tapatalk
gjkrisa said:
You can set the phone to back up without wifi if you are good with that I've had my phone since December I have not had that happen odd.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
And how would you do that? Can't seem to find any way to do that...
In Google photos there is in settings also drive after that I believe the rest of settings will back up w/o wifi I know photos will
Sent from my Nexus 6P using Tapatalk
Dytoonn said:
This is the second time I get this message. First time was on stock Android 7.0. next time, ~2 weeks later on stock Android 7.1.1. To revive my phone I had to perform a factory reset twice.
What causes this message? Is it software or hardware related? I assumed the former, but the fact that it happened twice after a reset and on a new version made me wonder...
I'm heading to a country without 3G coverage and barely any WiFi, so if this happens then, I'm screwed on 2 levels: -Loss of pictures, due to not able to back-up -Not able to reset, since that requires WiFi.
Anyone else who had this issue? Any recommendations, RMA?
Full error message: "Decryption unsuccessful" The password that you entered is correct but unfortunately your data is corrupt. To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google account"
Thx.
Click to expand...
Click to collapse
Did you experience any random reboots?
When you say stock you confirm that it's full stock (no root and running google's kernel) ?
rchtk said:
Did you experience any random reboots?
When you say stock you confirm that it's full stock (no root and running google's kernel) ?
Click to expand...
Click to collapse
Never had any troubles with random reboots.
My phone froze, got unresponsive. I had to restart, and when it tried to boot I got this message. This happened twice.
No root, standard kernel. Bootloader not even unlocked.
Dytoonn said:
Never had any troubles with random reboots.
My phone froze, got unresponsive. I had to restart, and when it tried to boot I got this message. This happened twice.
No root, standard kernel. Bootloader not even unlocked.
Click to expand...
Click to collapse
That's it. Storage corruption and the decryption unsuccessful is a consequence of your problem.
Sorry but that looks like a defective device.
ram/emmc/power, it's hard to find without root/twrp. Unless an update got wrong but I don't think that would show these symptoms.
First, I would also raise a PR on google to see what they suggest: https://source.android.com/source/report-bugs.html
You really need to backup your data and have a backup phone in case the following gets you a brick..
I'd actually try flashing factory images (you won't be able to flash recovery image but others yes ). Make sure to record the messages returned on your PC to see if something went wrong. The update process is a bit dumb, it goes on even if errors are encountered so even if it finishes it doesn't mean much.
Once the device is flashed, if it boots, you could try filling your data partition by moving big files using usb transfer. When its full, reboot and see what's happening.
If you are short on time, prepare the RMA process...
edit: oh btw, I'm sure people would be interested to get the information displayed in bootloader mode (power on the phone by pressing volume down)
rchtk said:
That's it. Storage corruption and the decryption unsuccessful is a consequence of your problem.
Sorry but that looks like a defective device.
ram/emmc/power, it's hard to find without root/twrp. Unless an update got wrong but I don't think that would show these symptoms.
First, I would also raise a PR on google to see what they suggest: https://source.android.com/source/report-bugs.html
You really need to backup your data and have a backup phone in case the following gets you a brick..
I'd actually try flashing factory images (you won't be able to flash recovery image but others yes ). Make sure to record the messages returned on your PC to see if something went wrong. The update process is a bit dumb, it goes on even if errors are encountered so even if it finishes it doesn't mean much.
Once the device is flashed, if it boots, you could try filling your data partition by moving big files using usb transfer. When its full, reboot and see what's happening.
If you are short on time, prepare the RMA process...
edit: oh btw, I'm sure people would be interested to get the information displayed in bootloader mode (power on the phone by pressing volume down)
Click to expand...
Click to collapse
Thanks for your reply.
I sent it for an RMA, so unfortunately not able to do what you described. Couldn't chance it getting this error message when abroad.
Curious though if they will grant an RMA, nothing much is looking wrong at the moment. Hope they will, because else I'm screwed.
If they don't, though, I'll see if I can get the information displayed in bootloader mode.
I'm having the same issue.
Same message, only I'm BL unlocked, rooted and twrp.
It happened twice. Once on 7.1 DP1, and again on DP2.
Once I get into recovery, the system is encrypted, and I can't do a thing.
I'm going to try and back up to a flash drive, and try to mount that in twrp if it happens again.
rwj5279955 said:
I'm having the same issue.
Same message, only I'm BL unlocked, rooted and twrp.
It happened twice. Once on 7.1 DP1, and again on DP2.
Once I get into recovery, the system is encrypted, and I can't do a thing.
I'm going to try and back up to a flash drive, and try to mount that in twrp if it happens again.
Click to expand...
Click to collapse
Recent Twrp now supports full disk encryption so you should be able to see your files? And even do a backup from there. Take twrp 3.0.2-3
rchtk said:
Recent Twrp now supports full disk encryption so you should be able to see your files? And even do a backup from there. Take twrp 3.0.2-3
Click to expand...
Click to collapse
Strange, that's exactly the version I'm using.
rwj5279955 said:
Strange, that's exactly the version I'm using.
Click to expand...
Click to collapse
Weird. I don't have twrp so I can't check but you should see your data. Maybe the partition needs to be mounted (I think it is by default though). No /data/media ? /sdcard is the same but as a virtualized FAT file system to be able to be access from Windows. Could be that /sdcard is empty in twrp but /data/media shouldn't.
rchtk said:
Weird. I don't have twrp so I can't check but you should see your data. Maybe the partition needs to be mounted (I think it is by default though). No /data/media ? /sdcard is the same but as a virtualized FAT file system to be able to be access from Windows. Could be that /sdcard is empty in twrp but /data/media shouldn't.
Click to expand...
Click to collapse
I'll have to look if it happens again.
I only remember trying to access /sdcard. Empty
https://twrp.me/faq/datamedia.html
Same issue , rooted and twrp noto e4 plus , any help ? Idk what's is going on
Joeykatie said:
Same issue , rooted and twrp noto e4 plus , any help ? Idk what's is going on
Click to expand...
Click to collapse
If I understand this thread flash custom kernel like ElementalX to unencrypt your device.

Note 4 bad internal memory

Hi! I have a SM-N910F and I think that the internal memory has some serious problems. At first the phone was lagging; next, when I was trying to copy some files for backup I was getting errors on my phone and also on my pc. When I tried to reflash it with kies, I needed two attempts to make it work (phone was stuck at "flashing firmware" stage). The inital setup after restore was painful, as the phone was lagging and not responding (even randomly rebooting). Finally, after I installed some apps, the phone randomly rebooted in recovery mode. My question is: Is there any way to use only the sd card (for system and firmware) and isolate the internal memory? Thanks!
Drake97 said:
Hi! I have a SM-N910F and I think that the internal memory has some serious problems. At first the phone was lagging; next, when I was trying to copy some files for backup I was getting errors on my phone and also on my pc. When I tried to reflash it with kies, I needed two attempts to make it work (phone was stuck at "flashing firmware" stage). The inital setup after restore was painful, as the phone was lagging and not responding (even randomly rebooting). Finally, after I installed some apps, the phone randomly rebooted in recovery mode. My question is: Is there any way to use only the sd card (for system and firmware) and isolate the internal memory? Thanks!
Click to expand...
Click to collapse
I've seen someone do something similar in here before, try and give it a search. But i think it still utilized some of the internal memory for the kernel if i remember correctly.
Also what kind of errors are you getting when transfering files?
Diload said:
I've seen someone do something similar in here before, try and give it a search. But i think it still utilized some of the internal memory for the kernel if i remember correctly.
Also what kind of errors are you getting when transfering files?
Click to expand...
Click to collapse
When I transfer files over mtp on windows 10 I get errors like: "Make sure these file are available on PC". On the phone I can't remember exactly what was the error in file explorer.
Random Resetting and Lagging Note 4 - Poss EMMC Mem Failure
Drake97 said:
When I transfer files over mtp on windows 10 I get errors like: "Make sure these file are available on PC". On the phone I can't remember exactly what was the error in file explorer.
Click to expand...
Click to collapse
For the past 10 days I have had the same problem. Random restarts and resetting. Very laggy phone. I have Factory reset it 3 times, and it still has the issues. I am convinced the EMM chip has problems/failed. I have flashed roms many times, and am not new to it. I got the latest stock rom with the PIT file (prob not needed), and set about to flash it. It fails straight away with a "write" failure no matter what I do. Looks like I will need a new motherboard or EMM chip replacement unless there is another option. Kies 3 does not even see the phone. Odin does, but all attempts to re-flash have failed so far.
rammitt said:
For the past 10 days I have had the same problem. Random restarts and resetting. Very laggy phone. I have Factory reset it 3 times, and it still has the issues. I am convinced the EMM chip has problems/failed. I have flashed roms many times, and am not new to it. I got the latest stock rom with the PIT file (prob not needed), and set about to flash it. It fails straight away with a "write" failure no matter what I do. Looks like I will need a new motherboard or EMM chip replacement unless there is another option. Kies 3 does not even see the phone. Odin does, but all attempts to re-flash have failed so far.
Click to expand...
Click to collapse
Odin fails to flash for me too, I think the storage chip is dead. I didn't flash any roms at all, not even root, so probably it is age related. Maybe it works in your case: try to download all files from: https://mega.nz/#F!QIMmFRIT!Ns3AM-n0FUoMqOOWUif9ng!YN9lgLRI except the APQ8084, load them in ODIN in their places (PIT, BL, AP, CP, CSC, ) and try to flash; maybe "NAND erase all" would help, but I am not sure.

My LG E610 internal storage is in read-only mode, and the phone won't even root..

My old faithful LG E610 developed a problem I couldn't solve myself, and I've been forum reading quite a lot.
Android version 4.0.3, firmware LG-E610-V10l-NOV-06-2012, never ever been tampered with before.
Suddenly one morning, the internal memory became read-only and the phone is virtually useless because keeps giving me various app errors and reboots every now and then. There is no way to delete anything on it, there is no way to save anything on it, there is no way to install anything too; at first looks like it does but then it reboots unexpectedly and everything is as before. It performs factory reset, then reboots and everything is as before. Hard reset using the physical buttons, then reboots and everything is as before. I even tried to flash another stock rom, looked like the procedure went fine, then rebooted and everything was as before. I have tried to root it in a few different ways but to no avail
Is there anyone who has a solution for rooting an Android phone with the internal storage in read-only mode? (or to revert the file system in a normal read-write state). Thanks a lot.

[A2017G] LineageOS 14.1 - Can not access TWRP anymore, can't get through setup either

Hey folks,
I did not find anything on this issue, seems to be rather unique. Let me describe the problem.
This is my father's Axon 7 and he wanted me to get him a different ROM on there, which I did, and it worked smoothly until today. It kept crashing, freezing and was literally unusable for unknown reasons.
So since he was going to be gone for the next few days, I had no choice but to remove the ROM and data and reflash it. HOWEVER I did not delete the internal storage since I did not think it would be necessary. Sitting in the setup, I had issues getting through it, it will not pop up the keyboard to let me type the wifi password neither does it let me pass through if I wanted to use mobile data. It simply gets stuck. Sometimes random android processes tend to crash and put me at the start of the setup and I can't get to the settings which does prevent me from enabling USB-debugging or OEM unlock.
If I try to get into the recovery (which is still on there) it will simply get stuck on the screen that says ZTE, did not work through fastboot either, same issue.
(I do personally think that some app data is corrupted and causes the issue, since I wiped everything except internal storage and I still have major issues)
So here am I, stuck. I hope someone can enlighten me, or tell me how stupid I am and point me at something completely obvious. Thanks
OmegaFighter said:
Hey folks,
I did not find anything on this issue, seems to be rather unique. Let me describe the problem.
This is my father's Axon 7 and he wanted me to get him a different ROM on there, which I did, and it worked smoothly until today. It kept crashing, freezing and was literally unusable for unknown reasons.
So since he was going to be gone for the next few days, I had no choice but to remove the ROM and data and reflash it. HOWEVER I did not delete the internal storage since I did not think it would be necessary. Sitting in the setup, I had issues getting through it, it will not pop up the keyboard to let me type the wifi password neither does it let me pass through if I wanted to use mobile data. It simply gets stuck. Sometimes random android processes tend to crash and put me at the start of the setup and I can't get to the settings which does prevent me from enabling USB-debugging or OEM unlock.
If I try to get into the recovery (which is still on there) it will simply get stuck on the screen that says ZTE, did not work through fastboot either, same issue.
(I do personally think that some app data is corrupted and causes the issue, since I wiped everything except internal storage and I still have major issues)
So here am I, stuck. I hope someone can enlighten me, or tell me how stupid I am and point me at something completely obvious. Thanks
Click to expand...
Click to collapse
well, you can use EDL maybe?
The fastest way out is downloading the A2017G_FULL_EDL file from our Russian friends and use MiFlash while in EDL mode to flash the cluster**ck of a phone that you have.
The closest thing I've seen was a friend's Galaxy Grand 2 (like 5 years old) that maybe had a part of the system corrupted or a slightly dead eMMC. a bunch of stuff just crashed for no apparent reason. I reflashed the system and it got fixed for some time, then it started doing some weird sh!t again (after booting, you have an 80% chance that it will just freeze forever, hard reboot needed). But let's hope for the best and see if you can recover it by reflashing stock totally. If it still doesn't work you might be able to relock the BL and claim the warranty
Choose an username... said:
well, you can use EDL maybe?
The fastest way out is downloading the A2017G_FULL_EDL file from our Russian friends and use MiFlash while in EDL mode to flash the cluster**ck of a phone that you have.
The closest thing I've seen was a friend's Galaxy Grand 2 (like 5 years old) that maybe had a part of the system corrupted or a slightly dead eMMC. a bunch of stuff just crashed for no apparent reason. I reflashed the system and it got fixed for some time, then it started doing some weird sh!t again (after booting, you have an 80% chance that it will just freeze forever, hard reboot needed). But let's hope for the best and see if you can recover it by reflashing stock totally. If it still doesn't work you might be able to relock the BL and claim the warranty
Click to expand...
Click to collapse
Hey,
After a long day I managed to fix it, I was able to use the adb in fastboot and could reinstall the recovery and managed to run it, deleted internal storage and reinstalled everything. Seems to have done the trick. I hope it will keep working now.
OmegaFighter said:
Hey,
After a long day I managed to fix it, I was able to use the adb in fastboot and could reinstall the recovery and managed to run it, deleted internal storage and reinstalled everything. Seems to have done the trick. I hope it will keep working now.
Click to expand...
Click to collapse
good

Categories

Resources