Database Info

[Q] Bricked xt925 - read-only eMMC ?

Hello,
Since yesterday my phone is crashing about 20-30 seconds after properly booting. I can unlock the phone with my lockscreen pattern, I land on my homescreen but process like Google Play Services goes like "x has stopped working".
On CWM I've erased /system and /data and then reflash a rom (Slimkat or CM), Erasing and flashing process on CWM seems to work as planned but when the phone reboot it's still on Slimkat with all my datas, like if nothing have been done in CWM.
So I've rebooted on the bootloader and tried a "fastboot -w", again the process seems to be ok on my pc but when the phone reboot it is still on this f**ked rom with all my datas, like if fastboot have done nothing.
I've tried to flash an up-to-date CWM, same thing again.
I think the eMMC chip are deeply corrupted, they say any writing on it is ok but in fact they are read-only, which may explain why all the process are crashing after the boot and why flashing seams ok but are useless.
What do you think XDA, andy idea about my problem ? Do you think it's an Hardware issue or what can I do to solve it ?

Why not flashing a stock firmware to go back to STOCK?

joel_sinbad said:
Why not flashing a stock firmware to go back to STOCK?
Click to expand...
Click to collapse
I've tried it with RSDLite but same thing again, everyhing seams ok in RSDLite, the 22 blocks are writed but at the reboot it's still the same Slimkat with my datas.

Ezekiel3 said:
I've tried it with RSDLite but same thing again, everyhing seams ok in RSDLite, the 22 blocks are writed but at the reboot it's still the same Slimkat with my datas.
Click to expand...
Click to collapse
if infact it has gone read only as has happened to some other users, there is no known fix. all known angles have been explored, even with input from a developer.
if you find a fix, post it, it may help others.
most likely, you will need a new phone.

I agree with bwen diord...aint never see anyone recover from that, least not yet.

cmh714 said:
I agree with bwen diord...aint never see anyone recover from that, least not yet.
Click to expand...
Click to collapse
I've just see it's possible to boot from the SD card in that case but I'm to lazy to try it.
Goodbye little RAZR HD, we have covered a lot of mileage together, it's time to leave. :angel:
Anyway thanks for the help XDA

[Q] "Unfortunately, IMS Service has stopped"

I'm having issues with my Galaxy S6. I used Odin to return to stock, and now I'm getting an "Unfortunately, IMS Service has stopped" error every 2 or 3 seconds. The phone is essentially unusable.
Other Galaxy phones have had similar issues, and I've tried some of their suggestions. I wiped Media Storage and factory reset the phone through the recovery. I tried to find the DRM app to wipe, but it's not there in the app manager. Does anybody have any suggestions? They are greatly appreciated.
Thanks in advance.

Im having that same issue. I bricked my phone for about a week and I had just got the tar files to open and return my device to stock. Is it saying you have service? Ive been looking this up everywhere and have no luck with the s6 problem.

boristhebladexx said:
I'm having issues with my Galaxy S6. I used Odin to return to stock, and now I'm getting an "Unfortunately, IMS Service has stopped" error every 2 or 3 seconds. The phone is essentially unusable.
Other Galaxy phones have had similar issues, and I've tried some of their suggestions. I wiped Media Storage and factory reset the phone through the recovery. I tried to find the DRM app to wipe, but it's not there in the app manager.
Click to expand...
Click to collapse
Why did you return to stock? If you are planning to return/exchange the phone, then you may run into trouble if it is unusable.
3 options:
1. Attempt to reflash stock via Odin and hope it fixes the problem.
2. Restore a nandroid.
3. Clean flash a custom rom.

sublimaze said:
Why did you return to stock? If you are planning to return/exchange the phone, then you may run into trouble if it is unusable.
3 options:
1. Attempt to reflash stock via Odin and hope it fixes the problem.
2. Restore a nandroid.
3. Clean flash a custom rom.
Click to expand...
Click to collapse
i tried to reflash stock again and the same message kept coming up. i thought that restoring would wipe root so i dont know how you could flash a custom rom onto it. would you do that through the Odin program??

LiquidPhoenix said:
i tried to reflash stock again and the same message kept coming up. i thought that restoring would wipe root so i dont know how you could flash a custom rom onto it. would you do that through the Odin program??
Click to expand...
Click to collapse
Did you try restoring a nandroid?
Sent from my SM-G920T using Tapatalk

sublimaze said:
Did you try restoring a nandroid?
Sent from my SM-G920T using Tapatalk
Click to expand...
Click to collapse
i never backed up a nandroid. im pretty new to android phones and the deep stuff because the only thing i ever learned was iphone. do they auto backup? and if so, how could i restore it??
thank you for your patience, i know its driving you crazy haha.

LiquidPhoenix said:
i never backed up a nandroid. im pretty new to android phones and the deep stuff because the only thing i ever learned was iphone. do they auto backup? and if so, how could i restore it??
Click to expand...
Click to collapse
Android lollipop gives you the option to transfer your apps to a new device when you setup the new device. You are also given this option when you flash a custom lollilop rom, because the setup wizard will see this as a new device. However, you should always make a backup of a good working rom setup prior to flashing a new rom or any mods. When I say a "good working rom ", I mean a rom that you might possibly want to go back to, in case your next rom flash doesn't go well or it has major issues that prevent you from using it as a daily driver (which you won't know until you flash it, obviously). The stock rom is definitely a "good working rom", and you should ALWAYS make a backup of stock before flashing anything else.
Since you don't have a backup of stock, then you are stuck with Odin getting you back to bone stock, which apparently isn't quite doing the job. The only other thing I can suggest is flashing a stock rooted rom (eg, no mods other than root). But make sure you clean flash, which also means mounting & wiping /system in recovery. I forgot how to do it in CWM/Phil's recovery, but in TWRP go to Mount, tap /system then go back to the main menu, go to Wipe > Advanced and select cache, dalvik cache, data and system, then swipe to erase. Now you have a totally clean slate.

sublimaze said:
Android lollipop gives you the option to transfer your apps to a new device when you setup the new device. You are also given this option when you flash a custom lollilop rom, because the setup wizard will see this as a new device. However, you should always make a backup of a good working rom setup prior to flashing a new rom or any mods. When I say a "good working rom ", I mean a rom that you might possibly want to go back to, in case your next rom flash doesn't go well or it has major issues that prevent you from using it as a daily driver (which you won't know until you flash it, obviously). The stock rom is definitely a "good working rom", and you should ALWAYS make a backup of stock before flashing anything else.
Since you don't have a backup of stock, then you are stuck with Odin getting you back to bone stock, which apparently isn't quite doing the job. The only other thing I can suggest is flashing a stock rooted rom (eg, no mods other than root). But make sure you clean flash, which also means mounting & wiping /system in recovery. I forgot how to do it in CWM/Phil's recovery, but in TWRP go to Mount, tap /system then go back to the main menu, go to Wipe > Advanced and select cache, dalvik cache, data and system, then swipe to erase. Now you have a totally clean slate.
Click to expand...
Click to collapse
Ive tried looking online for software thats compatible with my carrier (cricket) but I couldnt find it. The way that I bricked my phone was trying to flash TWRP recovery on my phone. Cricket is through at&t and has the locked bootloader. I used pingpong root to root it but apparently it wasnt compatible with my phone. I'm kinda stuck.

LiquidPhoenix said:
Ive tried looking online for software thats compatible with my carrier (cricket) but I couldnt find it. The way that I bricked my phone was trying to flash TWRP recovery on my phone. Cricket is through at&t and has the locked bootloader. I used pingpong root to root it but apparently it wasnt compatible with my phone. I'm kinda stuck.
Click to expand...
Click to collapse
I have never messed with Cricket phones. I know they piggyback on the AT&T network, but I don't know if the firmwares are different. You could go to a Cricket store and look at the display S6 to find out the exact firmware version, and try to find that on the web (posting in the AT&T forum might yield a faster response). But trying to flash TWRP was not a good idea. Good luck!

I was attempting to return the phone to stock so I could sell it. I flashed the Cricket firmware, and ever since then I get the IMS service error. I can't flash a new ROM because I unrooted through Pingpong Root. When I flash through Odin, I only flash the AP .tar. Would it make a difference if I flashed all 4 (BL, AP, CP, CSC)?

boristhebladexx said:
I was attempting to return the phone to stock so I could sell it. I flashed the Cricket firmware, and ever since then I get the IMS service error. I can't flash a new ROM because I unrooted through Pingpong Root. When I flash through Odin, I only flash the AP .tar. Would it make a difference if I flashed all 4 (BL, AP, CP, CSC)?
Click to expand...
Click to collapse
I tried this just now and all it said was "attempt thread failed (0/0)"

boristhebladexx said:
I was attempting to return the phone to stock so I could sell it. I flashed the Cricket firmware, and ever since then I get the IMS service error. I can't flash a new ROM because I unrooted through Pingpong Root. When I flash through Odin, I only flash the AP .tar. Would it make a difference if I flashed all 4 (BL, AP, CP, CSC)?
Click to expand...
Click to collapse
Yes it does make a difference to flash it into 4 different parts in case you have the entire firmware

Just wanted to throw my 2 cents in here, i woke to this lovely issue, which was rendering my phone unusable. I use a program call YouMail for voicemail, creeps my friends out when they get to my voice mail. Uninstall this program after wiping every cache imaginable, voila, no more issue. I haven't tried to reinstall it yet since i need to get some work done. Hope it helps in some way.

I have the same problem after flashing the stock firmware thru Odin on my S6 from Cricket. I also tried Factory Resert and Wiping the Cache, nothing seems to help at all. I get the annoying message about the IMS service. I've tried clearing the cache from contacts, ims service but no luck at at. Is there any other ROMs out there for the S6 from Cricket. Right now my phone is completely stock and has no service. Any word of advice would help, Thanks !
Edit: I flashed the CSC file thru odin and it got rid of the IMS error but now I have no service.

SRobby said:
Just wanted to throw my 2 cents in here, i woke to this lovely issue, which was rendering my phone unusable. I use a program call YouMail for voicemail, creeps my friends out when they get to my voice mail. Uninstall this program after wiping every cache imaginable, voila, no more issue. I haven't tried to reinstall it yet since i need to get some work done. Hope it helps in some way.
Click to expand...
Click to collapse
Not an expert in any sense of the term, so ignore this if it's dumb. When the OP and others having this issue are bringing your phones back up, does the issue start prior to phone setup? Or is your Google account restoring some app that could be causing the issue?

it didnt solve my problem
I have the s6 edge though ..do i have to wipe and install the rom again??

Unfortunately ims has stopped working pop up
I noticed the spinning sync icon at the top my s7 phone. It was constantly trying to sync my messengers app to the cloud. (I tuned the sync function off an it seems to have stopped the annoying message from popping up. :good::fingers-crossed:

eeee
boristhebladexx said:
I was attempting to return the phone to stock so I could sell it. I flashed the Cricket firmware, and ever since then I get the IMS service error. I can't flash a new ROM because I unrooted through Pingpong Root. When I flash through Odin, I only flash the AP .tar. Would it make a difference if I flashed all 4 (BL, AP, CP, CSC)?
Click to expand...
Click to collapse
just root the device an then install root unistaller
find all apps with the word ims
unistall all apps
restart phone
Magic!!!!

Stuck in Optimizing App xxx of xxx

I recently upgraded my phone from 4.4.4 to the latest OTA. It was working fine for a while but it crashed, rebooted and keeps (re)optimizing the apps. It'll get stuck on some of them for a long time and might make it through, or I hard reboot it and it does it all over. Whenever it does make it through, it says "starting apps" and then reboots and does it all over again.
I've cleared the cache multiple times and restored the stock recovery, but still not working. Does anyone else have any other suggestions that I could try??
Also I read somewhere that there was a zip I could possibly flash to use all the cores, as lollipop only uses one during this process? Does anyone know where that is?
Thanks.

natboy said:
I recently upgraded my phone from 4.4.4 to the latest OTA. It was working fine for a while but it crashed, rebooted and keeps (re)optimizing the apps. It'll get stuck on some of them for a long time and might make it through, or I hard reboot it and it does it all over. Whenever it does make it through, it says "starting apps" and then reboots and does it all over again.
I've cleared the cache multiple times and restored the stock recovery, but still not working. Does anyone else have any other suggestions that I could try??
Also I read somewhere that there was a zip I could possibly flash to use all the cores, as lollipop only uses one during this process? Does anyone know where that is?
Thanks.
Click to expand...
Click to collapse
To make things clearer. Previous what ROM were you on? After your proclaimed (OTA), what was the ROM suppose to be?

I went from the Oneplus One CM 4.4.4 to the CM 5.1 OTA. Not sure why you're don't believe me..

I think I might have bad memory or flash or something at this point..
So since yesterday I've tried using the tutorials here to flash stock Kitkat with the same errors happening. When it boots up, I get a done of crashes on things like gapps and process.acore. I also tried flashing the stock Lollipop; both using the non fastboot and fastboot way. Every time wiping everything with all the same results. The only rom I've had some slight uptime with has been slimrom without gapps as there's not much running there. Once I add the gapps package to it, processes start crashing again.
Does anyone know of a memory/cpu/flash test I could try, or any other suggestions? Thank you.

A Standard Update Put my Phone into a Reboot Loop? Why? But it does Unlock.

Galaxy s8 on Verizon, a standard update notice kept appearing past few days, finally installed it. The minute it finished, it is now in an endless restarting loop. The phone does unlock and show my homescreen. I can get into it, but I only get about 10 seconds to do stuff then it freezes/restarts. Tried Clear Partition Cache in the recovery mode. Tried Safe Mode. No luck.
When I rush over to Settings>Software Update, and click it, it says "Software update in progress"....so it makes me think it is the remnants of the new software update completing itself, and that causes the rebooting. The final stages perhaps? Is there a way to CEASE that the second I unlock my phone? To stop all the background stuff.
Or maybe wouldnt make a difference. Any ideas besides factory reset? Way to revert back?
Wanted to backup a few recent pictures first.

A factory reset is the last resort to fix this.
Maybe it's theme related. Try toggling the button layout (settings -> display -> navigation bar) a couple of times.
If you have substratum installed, try disabling it.
If you want to back up your pictures;
Have you tried accessing the phone using a computer? Either just through a file explorer or by using ADB? To use ADB, you may need to get into settings -developer mode

I tried plugging into a computer, but I only have about 10 seconds, so I dont get enough time to access the files. I get into the phone drive on windows Samsung Galaxy>DCIM> CAMERA> ...then it reboots.
Developer mode is already enabled. Can ADB be used while on the recovery mode screen? I can access that command line looking screen as long as needed.
But accessing the phone normally like turning it on and unlocking the screen would not work, I would keep losing the connection when it reboots.

halfhumble said:
Galaxy s8 on Verizon, a standard update notice kept appearing past few days, finally installed it. The minute it finished, it is now in an endless restarting loop. The phone does unlock and show my homescreen. I can get into it, but I only get about 10 seconds to do stuff then it freezes/restarts. Tried Clear Partition Cache in the recovery mode. Tried Safe Mode. No luck.
When I rush over to Settings>Software Update, and click it, it says "Software update in progress"....so it makes me think it is the remnants of the new software update completing itself, and that causes the rebooting. The final stages perhaps? Is there a way to CEASE that the second I unlock my phone? To stop all the background stuff.
Or maybe wouldnt make a difference. Any ideas besides factory reset? Way to revert back?
Wanted to backup a few recent pictures first.
Click to expand...
Click to collapse
Try downloading that same version of Odin flashable stock firmware from the internet, the same version as the update that you received, then flash that via Odin. As long as the update does not upgrade your bootloader or your binary, it will not wipe your user data(pics).
But first....
If you can get to the homescreen and unlock the device, don't touch anything else once the device opens, just connect it to PC and retrieve your photos from the internal storage, then factory reset the device.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
Try downloading that same version of Odin flashable stock firmware from the internet, the same version as the update that you received, then flash that via Odin. As long as the update does not upgrade your bootloader or your binary, it will not wipe your user data(pics).
Click to expand...
Click to collapse
I dont know what version the update was that caused it or how I would find out. But I ended up getting it fixed.
I just downloaded the most recent version firmware from SamFW.com, and used that one. The First flash, the phone was worse! It was now stuck at the samsung logo looping. I flashed it a second time, then it worked! Phone back to normal and backed up my pictures. I had used the home CSC file too, and none of my user data was wiped. I thought it was supposed to wipe that, got lucky
I assume once that OTA update comes back and tries to install, I may have this problem all over again. I can't go forever without the security updates.
Droidriven said:
If you can get to the homescreen and unlock the device, don't touch anything else once the device opens, just connect it to PC and retrieve your photos from the internal storage, then factory reset the device.
Click to expand...
Click to collapse
^
I had tried that a couple times, it lasts about 15 seconds then restarts. Not enough time, I would get to the DCIM folder but before pics loaded, it froze and restarted.

halfhumble said:
I dont know what version the update was that caused it or how I would find out. But I ended up getting it fixed.
I just downloaded the most recent version firmware from SamFW.com, and used that one. The First flash, the phone was worse! It was now stuck at the samsung logo looping. I flashed it a second time, then it worked! Phone back to normal and backed up my pictures. I had used the home CSC file too, and none of my user data was wiped. I thought it was supposed to wipe that, got lucky
I assume once that OTA update comes back and tries to install, I may have this problem all over again. I can't go forever without the security updates.
^
I had tried that a couple times, it lasts about 15 seconds then restarts. Not enough time, I would get to the DCIM folder but before pics loaded, it froze and restarted.
Click to expand...
Click to collapse
The most recent version that you downloaded might be the same update. The OTA updates and the Odin flashable updates are the same thing, the OTA update is just more automated. Flashing the same version as the OTA update via Odin, yields the same results. I think the Home CSC is the one that doesn't wipe user data. I think the Home CSC is intended for users that intend on keeping the device and using it in the same region/network and the other CSC is intended for users that want to sell the device or use the device in a different region or if you have a custom ROM and custom recovery on the device and you want to restore to stock. I could be wrong though.
If you do get a prompt for an OTA update, backup your data then factory reset the device then allow the device to update. That should prevent any further issues with updating via OTA.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
The most recent version that you downloaded might be the same update. The OTA updates and the Odin flashable updates are the same thing, the OTA update is just more automated. Flashing the same version as the OTA update via Odin, yields the same results. I think the Home CSC is the one that doesn't wipe user data. I think the Home CSC is intended for users that intend on keeping the device and using it in the same region/network and the other CSC is intended for users that want to sell the device or use the device in a different region. I could be wrong though.
If you do get a prompt for an OTA update, backup your data then factory reset the device then allow the device to update. That should prevent any further issues with updating via OTA.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Okay, I see.
Well when the phone did boot back up normally after the 2nd flash, there was a pop up that said software update unsuccessful. So I'm not sure if the same OTA update actually updated per se. But yeah, next time Im ready, I've got everything backed up!
Thanks so much!

halfhumble said:
Okay, I see.
Well when the phone did boot back up normally after the 2nd flash, there was a pop up that said software update unsuccessful. So I'm not sure if the same OTA update actually updated per se. But yeah, next time Im ready, I've got everything backed up!
Thanks so much!
Click to expand...
Click to collapse
I always prefer updating via Odin instead of OTA, it is much better and less chance of issues such as bootloop or random reboot. These are the issues you were having. I actually suggest using Odin or Smart Switch on PC the next time an update is available. Or, on older devices, use Odin or Samsung Kies to update. OTA is frequently unreliable, it commonly causes bugs, especially if the update is a newer android version than what is already on the device, it usually causes conflicts due to user data from your previous system apps and user settings conflicting with the new system because of differences between the older system apps and the newer system apps or differences in settings in the older system conflicting with changes in how the newer system settings are handled. Systems don't like using system data that was created by another system when there are differences between the two systems.
Another method that can be used is if your manufacturer/carrier releases a stock update.zip that can be flashed via stock recovery, they are made specifically for flashing via stock recovery ONLY, they are not the same as the stock firmware file that is flashed via Odin. These can be downloaded to the phone's internal/external memory then you boot into stock recovery then factory reset/wipe cache in recovery(backup data before wiping) then you can flash the update.zip. Alternatively, you can flash the update.zip without resetting/wiping(this is called a "dirty" flash), in theory, a dirty flash is useful when you don't want to wipe data or lose data. But that comes with a chance of causing bugs, as you have discovered for yourself during your update process.
Sent from my SM-S767VL using Tapatalk

Flashing Kernel Patch for RMM on unsupported Note 9 caused it to stop booting

Hello,
I've been trying to root my Note 9 using the "N960F_DS_N_Oreo_Root_for_OEM_issue_devices_V5" which I've found online and i believe it is based on what was developed by Dr. Ketan.
While flashing this setup, I selected "Proceed with ROM Flash and Multi tool", "Patch for OEM issue", "Flash Kernel Patch for RMM" and then "Root with Magisk". Once the installation is done and the device is rebooted, the phone no longer boots. It shows the logo Galaxy Note 9 powered by Android then black screen then loop again to Galaxy Note 9 logo and it stays in this loop. I can only break the loop by entering to the Download Mode and loading TWRP and staying there.
I'm suspecting that the "Flash Kernel Patch for RMM" that I've selected is not supported on my Note 9 Model.
Is there a way to revert back this change? or may be install back the default kernel?
Appreciate your help!
Regards,
Elias

As I can see you are proud owner of a softbricked phone.
My recommendation: re-flash phone's Stock ROM to get rid off of all mods you applied to the phone.

jwoegerbauer said:
As I can see you are proud owner of a softbricked phone.
My recommendation: re-flash phone's Stock ROM to get rid off of all mods you applied to the phone.
Click to expand...
Click to collapse
Thanks for your help.
I've downloaded this: https://androidfilehost.com/?fid=4349826312261705548
It's around 4.8GB. Is this what you're referring to?
Just to give some background, the phone got an accidental factory reset (which I still don't understand how) and i'm trying to retrieve at least some of the deleted data (mainly pictures/videos). All the recovery tools requested to have the phone rooted in order to do a deep scan. So I started this learning journey myself since no phone repair store was off help.
Would reflashing the phone stock ROM affect my chances of retrieving my data?
Thanks!

The Factory Reset performed erased all your user data: though they are still physically present on device, their entry in Android's MTF got removed. IMO it requires a forensic tool to recover them.
As soon as you re-flash the phone with Stock ROM the disk space utilised by user data again gets wiped ( means a new MFT gets created), so the chance to recover user data previously stored there is NULL.

jwoegerbauer said:
The Factory Reset performed erased all your user data: though they are still physically present on device, their entry in Android's MTF got removed. IMO it requires a forensic tool to recover them.
As soon as you re-flash the phone with Stock ROM the disk space utilised by user data again gets wiped ( means a new MFT gets created), so the chance to recover user data previously stored there is NULL.
Click to expand...
Click to collapse
I was checking this thread on this form: https://4pda.to/forum/index.php?showtopic=915992&st=520
it seems that it's the same problem as mine and he was able to resolve it by flashing the original kernel. Not sure how i can do the same.

EN90 said:
I was checking this thread on this form: https://4pda.to/forum/index.php?showtopic=915992&st=520
it seems that it's the same problem as mine and he was able to resolve it by flashing the original kernel. Not sure how i can do the same.
Click to expand...
Click to collapse
With regards to recovering wiped user data: As I can see you didn't get it.

jwoegerbauer said:
With regards to recovering wiped user data: As I can see you didn't get it.
Click to expand...
Click to collapse
hmmm, what i understood is that if I go and flash the phone with Stock ROM (to make it boot again) I'll lose any chance of getting my data back even with a forensic tool. Is that what you meant?
So I was trying to say that what if I just flash back the original kernel to solve my booting issue, would it also affect the possibility of retrieving the lost data?
Unless I'm confused with the terminologies and flashing kernel is the same as flashing the Stock ROM. I'm quite new to this .
I appreciate your help!

@EN90
As with Android
Kernel is the core part of Android OS and is based on Linux. It is the system which initializes, configures and sets all hardware components for use. It prepares the complete system for functioning. It consits of several sub-systems and services.
Stock ROM is a read only memory chip on the phone's motherboard that contains the Android OS image that boots every time you turn on your phone. A ROM contains full Android OS system and a few system apps that comes pre installed with the device.