I need some help to revive an almost dead OG Grand Prime G530-H variant - Galaxy Grand Prime Q&A, Help & Troubleshooting

I already have a much better Xiaomi Redmi 7A phone, but that's besides the point. I really want to make this phone work again.
The problem:
I have a Samsung Galaxy Grand Prime (G530-H). It charges properly, is in pristine condition (visually), and feel quite new. My dad bought it sometime in 2015 and it survived up till now, but at the end of 2019, it would occasionally experience some unwanted reboots. Now, this phone will not stay stable for anymore than a minute at best. One minute of usage an bam! It reboots itself. Everything else seems to be working the camera and video works, file explorer works, messages, etc. works but whenever I take a picture or do anything that involves a read/write operation, the phone starts to reboot. I tried going into the recovery, (it does not reboot while inside the recovery menu), and resetting the phone, only to get this error message:
# MANUAL MODE #
-- Appling Multi-CSC. . .
Applied the CSC-code : PAK
did not match sized '/system/csc/common/system/csc/others.xml' (No such file or directory)
-- Wiping data. . .
Formatting data. . .
E: format_volume: make_ext64fs failed on /dev/block/bootdevice/by-name/userdata
Formatting /cache. . .
E: format_volume: make_ext64fs failed on /dev/block/bootdevice/by-name/cache
Data wipe complete.
It says "Data wipe complete" at the end, but nothing actually gets erased and the reboot upon read-write problem persists. I've heard that this usually points to faulty eMMC memory and that might be the case since the phone is five years old, but as I said, it does not shut off inside the recovery mode, so maybe it is fixable... any thoughts?

Related

Phone won't boot after charging overnight

Hey, I'm in a very strange situation. The thing is I left my phone to charge overnight just like usual (made it reboot before doing so), when I woke up today I've noticed that it was bootlooping like crazy along with being very hot to the touch, like it was about to go off :x. Rebooting resulted in nothing, phone still bootloops. After entering TWRP and trying to look for my backup I also noticed that it shows "Internal storage (0mb)", what is totally weird considering that I've been doing absolutely no software modifications lately (I'm on Lineage). I also cannot mount data in "Mount" section, backing it up is also not an option.
I havent't tried yet to restore my full back up I've made around a month ago, is there any way I can revive the data partition?
Ok, since my backup is missing I've decided to reinstall the rom. But I can't format the Data partition at all . TWRP just goes "Failed to mount '/data' (Invalid argument), Unable to wipe /data). What should I do? Is the phone internal memory dead or what?
OK SOLVED. I entered erecovery and formatted my data. Now I reinstalled Lineage and everything works again... apart from photos of my doggy lost . Damn, I have completely no idea what caused that Data partition failure

FE rebooting constantly after update. Ideas?

FE is rebooting every minute after recent Dec. update. Cleared delvik cache and says "can't find /misc partition." from reading it seems clearing everything to reset will cause the phone not to start so am waiting. if some way not to lose everything I'll try that first.
Seems the only answers are:
1) ignore it, that error doesnt matter anymore. Some can. Except many wipe data and then can't restart anyway.
2) ‎others say Samsung replaced their phones (or replaced the board) because unfixable due to some weird hardware-update Matrix electro-wedgie.
3) ‎people tried to rebuild /misc and was a nightmare that didnt end with anything beside tears.
I was first thinking I could just re-do the last update and be all good like a normal update.. But that doesn't work I think tho not sure why. If so, how so?
Thank you, good sirs.
-Please respond as tho talking to your mom or a small child. Thanks
You can try flashing stock firmware in Odin.

Messed my LG G2 big time

Hi everyone,
I installed AospExtended 8.1 ROM ten days ago and I rooted my device using Magisk afterwards. Everything was working perfectly for 10 days and I was completely satisfied with the ROM but yesterday my device rebooted itself and I ve got nothing but the black screen glowing after the LG logo. After 10-15 attempts I turned on my device successfully but it rebooted itself after few minutes again. I tried to perform clean installation of the ROM again using the TWRP recovery but every time I failed to wipe and got messages like failed to mount storage, system, data, failed to mount cache etc... Any help would be appreciated:angel:.
krovo said:
Hi everyone,
I installed AospExtended 8.1 ROM ten days ago and I rooted my device using Magisk afterwards. Everything was working perfectly for 10 days and I was completely satisfied with the ROM but yesterday my device rebooted itself and I ve got nothing but the black screen glowing after the LG logo. After 10-15 attempts I turned on my device successfully but it rebooted itself after few minutes again. I tried to perform clean installation of the ROM again using the TWRP recovery but every time I failed to wipe and got messages like failed to mount storage, system, data, failed to mount cache etc... Any help would be appreciated:angel:.
Click to expand...
Click to collapse
Hey bro did u try to mount manually in mount option?
umeshbluezzz said:
Hey bro did u try to mount manually in mount option?
Click to expand...
Click to collapse
I can't tick any of the boxes in the mount option, it says my internal storage is O MB. I tried the option which is suggested by lot of people, to change file system of data from ext4 to ext2,3... in the wipe option but I failed every time and got E:unable to mount storage message.
krovo said:
I can't tick any of the boxes in the mount option, it says my internal storage is O MB. I tried the option which is suggested by lot of people, to change file system of data from ext4 to ext2,3... in the wipe option but I failed every time and got E:unable to mount storage message.
Click to expand...
Click to collapse
Try to go everything back to stock.
umeshbluezzz said:
Try to go everything back to stock.
Click to expand...
Click to collapse
I tried by using the LG flash tool but my PC wont recognize my phone... (phone wont go into the download mode)
krovo said:
I tried by using the LG flash tool but my PC wont recognize my phone... (phone wont go into the download mode)
Click to expand...
Click to collapse
Thats pretty bad.i will ask my friends if they have any solution.
I had no luck with fixing the problem i wrote about earlier. Would replacing the motherboard solve anything?
Emmc dead I guess
sometimes my phone shows the capacity of my internal storage and I perform the installation of the custom rom and gapps. After rebooting the phone it goes into the twrp and shows that capacity is 0 Mb again...

Shuttering and dm-verity verification failed

Guys,
I bought used Note 4, that was "broken" in a way that it shutters. Sometimes I have to wait ~1 sec until it responses.
It was with some stock rom 5.1, glitches ware unbearable. Factory reset didn't help.
So I decided to go with other roms. And I found "dm-verity verification failed" and "Need to check DRK first" errors:
Could this have anything to do with it shuttering??
Then I installed TWRP and went with clean Dalvik / Art Cache, System, Data, Internal Storage, Cache.
Installed [ROM][UNOFFICIAL][9] LineageOS 16.0 [tblte][trlte][trlteduos]
Issue still occurs but it's less often. Sometimes it doesn't occurs at all.
And then I ried Havoc-OS
And again issue still occurs but it's less often. Sometimes it doesn't occurs at all.
I have no issues with reboots or permanent hangs. Just those shuttering/glitches/response hangs.
I tried to check logcat but there's to much information and I don't know what to look for.
Guys do you have any suggestions what to look for ?
So I found this video about emmc issue:
https://www.youtube.com/watch?v=5pJ7s9RBtdQ
And I ran this benchmark twice:
And those results seems to be fine, only random read little bit slow, but overall looks good I think.
I also rebooted device and benchmarked it for the third time, just after booting up and results are very similar.
Any ideas what's causing this issue?
no-verity-opt-encrypt-6.1.zip*
instructions
In TWRP go to advanced wipe and select dalvk/cache and data then wipe(do not reboot). Afterwards, go back to wipe and select formate data(must type yes/do not reboot). Next, power of the device (optional pull the battery), reboot back to recovery, install the*
If it works, then flash this after installing on every new rom you flash. Good luck
no-verity-opt-encrypt-6.1.zip, power off and reboot.
https://forum.xda-developers.com/and...ustom-t3549210
Download
https://build.nethunter.com/android-...y-opt-encrypt/
Mr. JAVI said:
no-verity-opt-encrypt-6.1.zip*
instructions
In TWRP go to advanced wipe and select dalvk/cache and data then wipe(do not reboot). Afterwards, go back to wipe and select formate data(must type yes/do not reboot). Next, power of the device (optional pull the battery), reboot back to recovery, install the*
If it works, then flash this after installing on every new rom you flash. Good luck
no-verity-opt-encrypt-6.1.zip, power off and reboot.
https://forum.xda-developers.com/and...ustom-t3549210
Download
https://build.nethunter.com/android-...y-opt-encrypt/
Click to expand...
Click to collapse
I found both proper links, thanks!
https://forum.xda-developers.com/an...zip-lazyflasher-tool-flashing-custom-t3549210
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
nothing changed, still "dm-verity verification failed"
still glitches and micro-hangs
is no-verity-opt-encrypt even solution for my problems?
crott said:
nothing changed, still "dm-verity verification failed"
still glitches and micro-hangs
is no-verity-opt-encrypt even solution for my problems?
Click to expand...
Click to collapse
It work on my old Note 4 n910p.
I know of another one if you want the link hit me up with a like.
Here another thread that provides a link and a download .zip.
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
PS. You'll need to turn off any ad blockers you may have in order to access the download link from the tread.
---------- Post added at 08:37 PM ---------- Previous post was at 08:20 PM ----------
crott said:
So I found this video about emmc issue:
https://www.youtube.com/watch?v=5pJ7s9RBtdQ
And I ran this benchmark twice:
And those results seems to be fine, only random read little bit slow, but overall looks good I think.
I also rebooted device and benchmarked it for the third time, just after booting up and results are very similar.
Any ideas what's causing this issue?
Click to expand...
Click to collapse
Over the years, I've had quite a few N4's. Lost a couple and bought I a couple just for parts. One of then worked well eight months when suddenly it began to has issues for no apparent reason. Even after a complete wipe and a clean official firmware flahing via Odin the issues continued. It wasn't until my N4 suddenly turned off and rebooted inyo a screen I had never seen before. It said "fail to read internal " and "emmc" or "mmc".
With stock recovery you might find some useful information checking "recovery logs"
DM-Verity stands for Device Maper Verification and DRK stands fot Device Root Key. They are part of the security of your phone's deap level software. The common believe that flashing the official factory firmware is a "fix all" is not completely true. It doesn't fix or replace dm-verity or drk issues . However, there are exceptions with mixed results flashing what they call "4files" or in this case 5 files witch includes the PIT ( Partition Information Table) file. I wouldn't recommend this as its a very risky endeavor. The PIT partitions will likely wipe you imei and without that you will not be able to carrier connect your device or even worse heard bricking your device. Its certain not for the novice. This would be my very, very, very last resort if all else fails and if my phone was in worse condition than what you have described.
Before you continue, I strongly recommend making a complete back up to external sd. By complete, I mean checking all boxes when in TWRP. The EFS is not part of a TWRP standard backup.
PS. Its unfortunate the no-opt-encrypted. zip did not have positive results as it did on my Note 4. Even so, its more like a patch .zip than a complete fix.

[Help] Moto G7 X1962-1 Soft Bricked; Won't recognize internal storage

A very long story short, I have learned that I should not seek out a career in phone repair.
I've bricked my phone by trying to flash a custom ROM onto it. I don't quite remember how I did it, but I wound up wiping the system partition. It won't recognize internal storage, TWRP says I have a storage size of 0 MB, wiping does nothing, changing file systems does nothing, formatting does nothing, I am unable to install anything on the device. Custom firmware won't install because of invalid partition names.
Through all of the guides I've found online, nothing has worked so far. Fails to mount '/data' as that is an invalid argument, unable to mount storage, can't repair internal storage as it gives me an "invalid partition selection" messasge, everything I do just pops up more and more errors and I'm worried that I've wasted even more money.
Any help would be much appreciated.
Update: Woke up this morning, booted the phone up ready to struggle with it even further, only to have it boot up to AEX and go through the setup process. I have no clue whatsoever how or why it is working, but I have a functional phone now.

Categories

Resources