Database Info

Can my Nexus be fixed?

Hello all
I suspect that either my Nexus has a hardware fault (internal memory) or I bricked it somehow.
For the past few weeks the phone has been getting stuck on the google boot screen quite a lot - It takes several attempts
to start up each time so I've been trying to keep the battery from running down.
The other day while I was attempting to switch roms I put the stock img on my SD card but when I went to flash it CWM
couldnt mount my (internal) SD Card. Senior forum member Caliban2 suggested that it could be my recovery so I installed CWM 6.0.0.7 non-touch using fastboot and, like magic, the phone started up -though I suspect this may have been luck.
I rebooted the phone out of curiosity and it got stuck on the google boot screen - no amount of battery pulling and restarting could coax
it back to life, so I went into CWM again to discover that it could not mount the SD Card, I was getting the 'cannot mount' and 'E:Unable to open ums lunfile(no such file or directory)' error messages. My windows 7 PC could see the phone but said that their was non memory inserted. Out of curiosity I installed CWM 5.0.2.0 but that produced the same results.
So now my phone appears dead, is the internal memory or something related to it is broken? I have seen things on here about using an unbricking tool in Debian Linux or flashing stock using odin but I confess that I have not tried these solutions and don't fully understand them (yet).I wussed out and dropped the phone into a local repair workshop, I imagine they will be trying these same steps themselves and they say it will take them a few days to get back to me.
My problem is that I need a phone for work and I gave my backup phone (HTC Hero) to my dad recently. Should I just take the plunge
and go out today and buy a new phone? Or is there a reasonable chance that these guys can fix my nexus s, or that I might be able to?
I'm a relative 'noob' at this so I thank you all for your advice in advance, it's much appreciated.
Derek

Do a search for flashing fastboot images. Download the 4.0.4 fastboot image from google and flash it as directed through fastboot. This may sort out your problems.
Afterward, if necessary, format the /sdcard too. I would do this afterward so that maybe you can get a backup of all the stuff on it before it's gone forever.

Thanks, will do. It's in the shop at the moment, I suspect this is probably what they're doing now.
Perhaps subconsciously I'm just looking for someone to tell me it's irreparable so I can rush out
and pick up a Galaxy Nexus.
Harbb said:
Do a search for flashing fastboot images. Download the 4.0.4 fastboot image from google and flash it as directed through fastboot. This may sort out your problems.
Afterward, if necessary, format the /sdcard too. I would do this afterward so that maybe you can get a backup of all the stuff on it before it's gone forever.
Click to expand...
Click to collapse

Hey Harbb
Just wanted to give you an update on this, got it back from the shop who said they would need to send it to Samsung for a hardware repair, didn't expect it to work but fastbooted the stock bootloader, radio and image to the device and it's now working!
I've already moved onto a Galaxy Nexus on contract but at least now I can make a bit of money back off my old phone.
Thanks again for the advice
Derek
Harbb said:
Do a search for flashing fastboot images. Download the 4.0.4 fastboot image from google and flash it as directed through fastboot. This may sort out your problems.
Afterward, if necessary, format the /sdcard too. I would do this afterward so that maybe you can get a backup of all the stuff on it before it's gone forever.
Click to expand...
Click to collapse

[Q] Help with SGH-T959W only booting into recovery

Hello, all. I hope someone can help me with my SGH-T959W. Right now I'm at the point where the phone has CWM installed, but will only boot into recovery no matter what I do. I've followed the N00b guide to Flashing/Fixing the SGS4G, but clearly I'm missing something.
I tried to follow the Windows-based procedure for the SGH-T959W, but was unable to get version 1.40 to execute, and was unable to locate version 1.31.
So, given that the SGH-T959W and SGH-T959V are the same phone except for the bootloader, I tried the Java-based Stock KJ-6 + Root. The first time I tried it, the upload failed after the PIT, and the phone was no longer able to boot into anything other than download mode. I eventually managed to get it to the point where it tried to flash the modem, but I was never able to get the modem to flash successfully. I tried both under Windows and Linux, using two different PCs and every USB cable I could find, since I know those tend to be dodgy. Still, I've never gotten past flashing the modem, though sometimes it's done worse.
But at this point, I had a phone that would dutifully boot into CWM, so I could change strategy anyway. So I grabbed the unofficial Cyanogenmod 10.1, copied it to the root of the SD card, and tried to load that via CWM. It failed the hardware check.
That's problem #1. Is it possible to modify Cyanogenmod to check for the 959W instead of only the 959V?
Now, problem #2. I decided to give Slim ICS a whirl, since it's light on requirements and a 512MB/1GHz device would probably appreciate a lighter load. The two packages claim to install, but the progress bar never reaches 100%, and when I try to boot the phone, it just boots into CWM. It's a newer version of CWM now, and the startup logo is different, so something worked, but clearly not everything.
When installing, I did mount UMMU, factory reset, wipe the cache and the Davlik cache, mount UMMU, install, then fix perms. But I still get that loop back to CWM.
So something critical didn’t take, however many times I tried (I've lost count, but I think I'm going on 10), and I don't know the architecture well enough to know where to start looking. I'm pretty comfortable with other operating systems, but this is only the second Android device I've tried to customize.
I suspect I can’t solve any other problem until I solve problem #2, regardless of which distro I end up wanting to run.
Sorry for the long-winded post, but I figured the more questions I answered up front, the better the chances of fixing this would be.
Thanks for any help you're willing to offer a n00b.
Dave F.

I think what you were doing with heimdall is the way to go except the t959w doesn't like modems and I think there's some way to leave out the modem part but eh.. I'm not that well versed. Anyway here's a link that may or may not be relevant
http://forum.xda-developers.com/showthread.php?t=1956025

Please read forum rules before posting.
Questions and request for assistance go in the Q&A section.
Thread has been moved.
Thank you for your future attention to this.
Have a great day!

dfarquhar said:
Hello, all. I hope someone can help me with my SGH-T959W. Right now I'm at the point where the phone has CWM installed, but will only boot into recovery no matter what I do. I've followed the N00b guide to Flashing/Fixing the SGS4G, but clearly I'm missing something.
I tried to follow the Windows-based procedure for the SGH-T959W, but was unable to get version 1.40 to execute, and was unable to locate version 1.31.
Click to expand...
Click to collapse
Look here for 1.3.1.
dfarquhar said:
So, given that the SGH-T959W and SGH-T959V are the same phone except for the bootloader, I tried the Java-based Stock KJ-6 + Root. The first time I tried it, the upload failed after the PIT, and the phone was no longer able to boot into anything other than download mode. I eventually managed to get it to the point where it tried to flash the modem, but I was never able to get the modem to flash successfully. I tried both under Windows and Linux, using two different PCs and every USB cable I could find, since I know those tend to be dodgy. Still, I've never gotten past flashing the modem, though sometimes it's done worse.
But at this point, I had a phone that would dutifully boot into CWM, so I could change strategy anyway. So I grabbed the unofficial Cyanogenmod 10.1, copied it to the root of the SD card, and tried to load that via CWM. It failed the hardware check.
That's problem #1. Is it possible to modify Cyanogenmod to check for the 959W instead of only the 959V?
Click to expand...
Click to collapse
Nope, not a CWM issue. Ever since TeamAcid and I started on CM9 (and I believe the last few CM7 builds) added support for T959W. Almost everyone (thankfully! ) has kanged those device trees and also support T959W. I'm sure other T959W users will chime in to tell you that 97% of all roms here work on T959W. (GB and forward)
dfarquhar said:
Now, problem #2. I decided to give Slim ICS a whirl, since it's light on requirements and a 512MB/1GHz device would probably appreciate a lighter load. The two packages claim to install, but the progress bar never reaches 100%, and when I try to boot the phone, it just boots into CWM. It's a newer version of CWM now, and the startup logo is different, so something worked, but clearly not everything.
When installing, I did mount UMMU, factory reset, wipe the cache and the Davlik cache, mount UMMU, install, then fix perms. But I still get that loop back to CWM.
Click to expand...
Click to collapse
Crazy mount setups shouldn't matter anymore. That was an oldschool Froyo/Early GB thing. Almost all new CWM install scripts do the right thing now.
dfarquhar said:
So something critical didn’t take, however many times I tried (I've lost count, but I think I'm going on 10), and I don't know the architecture well enough to know where to start looking. I'm pretty comfortable with other operating systems, but this is only the second Android device I've tried to customize.
I suspect I can’t solve any other problem until I solve problem #2, regardless of which distro I end up wanting to run.
Sorry for the long-winded post, but I figured the more questions I answered up front, the better the chances of fixing this would be.
Thanks for any help you're willing to offer a n00b.
Dave F.
Click to expand...
Click to collapse
I like the long posts! Especially when then they contain more detail for me to help you figure out your problem with. I'm also partial to the short posts that include logs!
TwitchyEye said:
I think what you were doing with heimdall is the way to go except the t959w doesn't like modems and I think there's some way to leave out the modem part but eh.. I'm not that well versed. Anyway here's a link that may or may not be relevant
http://forum.xda-developers.com/showthread.php?t=1956025
Click to expand...
Click to collapse
@TwitchyEye you're right That is the heimdall oneclick that should be used.
@dfarquhar I think using the heimdall oneclick that @getochkn made should be the right path for you. Make sure you use the right version of heimdall. Make sure you completely remove the old version (software and drivers), use zdiag to make absolutely sure!
If all else fails, post here again! (maybe with logs )

Thanks everyone. I grabbed v 1.3.1, so I'm getting ready to try it now.
If anything goes wrong, I'll look into where the logs are stored and how to retrieve them, and I'll be back. Assuming I can't use the logs to figure it out on my own of course.

dfarquhar said:
Thanks everyone. I grabbed v 1.3.1, so I'm getting ready to try it now.
If anything goes wrong, I'll look into where the logs are stored and how to retrieve them, and I'll be back. Assuming I can't use the logs to figure it out on my own of course.
Click to expand...
Click to collapse
Sometimes, it's just the output you see on your screen is a good enough log

bhundven said:
Sometimes, it's just the output you see on your screen is a good enough log
Click to expand...
Click to collapse
Got it working! Heimdall 1.3.1 was the key. I then turned around and flashed Slim ICS since I had it on the SD card already, and it worked. I'm debating whether to move on to Slim Bean, but maybe I need to leave well enough alone for a few days now that I have a working phone.
Thanks again,
Dave

GT-P3100 is restarting in every 10-15 seconds, ROM & recovery is not changing

Hi Guys,
I have GT-P3100 (Samsung Galaxy Tab2), I recently flashed Mokee ROM 4.4.4 (biggest mistake). The ROM (worked for 5-6 months) keeps restarting in every 10-15 seconds. I have tried to re-flash the ROM, but nothing is happening, I have also tried to flash the other ROMs but for most of the time I am getting this error "E: Error executing updater binary in zip 'location of the ROM file'", and even any ROM successfully installs nothing happens (the old Mokee ROM starts again on reboot, I mean come on).
I have TWRP and I tried to flash a new recovery i.e. CWM through Odin, after a successful flash TWRP starts again like the Mokee ROM.
I have also tried to flash the stock ROM fro Samsung through Odin but it fails in the middle, i have tried it multiple times. I have tried to wipe my entire phone memory, but the data and the installed ROM is still there even after a successful memory wipe
My phone keeps rebooting, I can't flash the same or any other ROM. I can't wipe my data, I can't install any other custom recovery. Nothing is happening.
The installed corrupted Mokee ROM is kind of a sticky ghost i can't get rid of. I would highly appreciate if you guys can help me out here.
If have some logs, please feel free to have a look if required. Since I am a new member I am not allowed to share a link and something is stopping to paste the logs here ( detecting a web link in the logs)
Please feel free to ask me for logs, I am always reachable at [email protected]
Thanks in advance .. I love my device.

This sounds like the dreaded eMMC (internal storage) bug that can affect some Tab2 devices, the symptoms sound similar (unable to boot properly, chip contents became read-only). This bug is caused by faulty firmware in some eMMC chips that cause problems when a particular instruction is issued (won't happen on recent ROMs and recoveries, but too late in your case). I remember there being some people who got hit by it here in XDA, but the only working solutions I remember is either replacing the eMMC chip or updating its firmware. Both solutions aren't at all easy, so I think bringing the tab to a service center would be the best option.

putr4s said:
This sounds like the dreaded eMMC (internal storage) bug that can affect some Tab2 devices, the symptoms sound similar (unable to boot properly, chip contents became read-only). This bug is caused by faulty firmware in some eMMC chips that cause problems when a particular instruction is issued (won't happen on recent ROMs and recoveries, but too late in your case). I remember there being some people who got hit by it here in XDA, but the only working solutions I remember is either replacing the eMMC chip or updating its firmware. Both solutions aren't at all easy, so I think bringing the tab to a service center would be the best option.
Click to expand...
Click to collapse
Thanks for your help. I think now I am in deep trouble in terms of phone. My device is rooted so the service center will not help me out. Perhaps I should figure out a way to do this by my own or find someone who can do this for me.
If I can have some more information, I may be able to fix this. Your information is good I am following the lead. Please share any info your think I should know, I am sure with help I will be able to find a way.
Thanks, keep rocking.

You got it fixed??
i am also facing the same issue. I flash through odin but when rebooted the old rom and recovery is there.
Odin flash is successful. but no change on EMMC content.
git it fixed?? please let me know.

bindasboy said:
You got it fixed??
i am also facing the same issue. I flash through odin but when rebooted the old rom and recovery is there.
Odin flash is successful. but no change on EMMC content.
git it fixed?? please let me know.
Click to expand...
Click to collapse
Hi,
The issue is still there, as you can see people told me the this may be caused due to an error or a malware in eMMC card of the phone (memory controller). I tried to do some research and found eMMc could be the possible problem.
I believe I installed a Chinese ROM i.e. Mokee (so called open source but I can't find its code anywhere, perhaps a fake ROM) and they did something with my phone's MBR (Master Boot Record). Re-configuring the eMMC card if so, is not an easy task and require proper equipment and knowledge of using those equipment.
I bought a new phone instead and not going to use any Chinese product ever again in my life, I hope you will be able to find a better solution for the phone.
Odin is not helpful in this case as eMMC will not take command from it. Feel free to try more option though.
Stay in touch, I am a little lazy but I will be here.

[email protected] said:
Hi,
The issue is still there, as you can see people told me the this may be caused due to an error or a malware in eMMC card of the phone (memory controller). I tried to do some research and found eMMc could be the possible problem.
I believe I installed a Chinese ROM i.e. Mokee (so called open source but I can't find its code anywhere, perhaps a fake ROM) and they did something with my phone's MBR (Master Boot Record). Re-configuring the eMMC card if so, is not an easy task and require proper equipment and knowledge of using those equipment.
I bought a new phone instead and not going to use any Chinese product ever again in my life, I hope you will be able to find a better solution for the phone.
Odin is not helpful in this case as eMMC will not take command from it. Feel free to try more option though.
Stay in touch, I am a little lazy but I will be here.
Click to expand...
Click to collapse
I don't think it is the ROM's fault as it worked for 5-6 months according to you.
Sent from my espresso3g using XDA Labs

Lightracer said:
I don't think it is the ROM's fault as it worked for 5-6 months according to you.
Sent from my espresso3g using XDA Labs
Click to expand...
Click to collapse
The ROM was installed and I never tempered with it, I became aware of the tempering when I tried to remove it or wipe internal memory. It's called a Ghostware, I checked and a lot of people with this ROM has the same problem. I hope someone will come up with some solution soon without needing to solder eMMC etc.

[email protected] said:
The ROM was installed and I never tempered with it, I became aware of the tempering when I tried to remove it or wipe internal memory. It's called a Ghostware, I checked and a lot of people with this ROM has the same problem. I hope someone will come up with some solution soon without needing to solder eMMC etc.
Click to expand...
Click to collapse
Maybe you could try asking for a solution in the ROM's thread.
Sent from my espresso3g using XDA Labs

[email protected] said:
Hi,
The issue is still there, as you can see people told me the this may be caused due to an error or a malware in eMMC card of the phone (memory controller). I tried to do some research and found eMMc could be the possible problem.
I believe I installed a Chinese ROM i.e. Mokee (so called open source but I can't find its code anywhere, perhaps a fake ROM) and they did something with my phone's MBR (Master Boot Record). Re-configuring the eMMC card if so, is not an easy task and require proper equipment and knowledge of using those equipment.
I bought a new phone instead and not going to use any Chinese product ever again in my life, I hope you will be able to find a better solution for the phone.
Odin is not helpful in this case as eMMC will not take command from it. Feel free to try more option though.
Stay in touch, I am a little lazy but I will be here.
Click to expand...
Click to collapse
The problem was with the eMMC of p3100 and not the ROM.
The only fix is using jtag, replace eMMC or get new motherboard.

I agree with @bindasboy. The symptoms are exactly the same as the emmc brick bug.
Sent from my espresso3g using XDA Labs

Can you fix EFS Partition?

Hey all, I did a bad thing. Please help.
Just wanna start off by saying I'm really stupid and things like this make me not want to modify my device anymore. I recently updated to 10.3.0, and after flashing something in the wrong order, I soft bricked my OP6. Since I wanted to basically start over with Android 10, I decided to just do a full wipe, without reading how to. I wiped all partitions through TWRP (Which I very quickly learned is a stupid thing to do) because that it how I went about installing new ROMs on my old phone. That left me with just the bootloader on my phone and nothing more. So I used fastboot to flash recovery and 10.3.0 and everything was fine, or at least I thought.
Everything has been fine for about a week now, until my phone randomly restarted. Upon reboot, my sim card wasn't reading and whenever I tried going to it's settings, it would say "com.android.phone keeps stopping" and after a bunch of searching around... I learned what an EFS Partition is and I'm pretty sure that bad boy is gone. Putting *#06# in the keypad gives me a MEID number, but no IMEI number.
So my question now is, is there anything I can do? I found a few posts that say you could try flashing ColorOS (but there is only an unofficial port for OP6), one comment I found said to use a program called EFS Professional and flash back to stock, and some others suggested MSM tool? Which I haven't used, so I have no clue what that's about. Does anyone have experience or a suggestion for me, please? Any help is greatly appreciated.
My phone is also completely working right now, apart from sim card use. The sim was also 100% working for about a week, before it randomly rebooted, is that normal? I just want to get my phone back to working order, I'm done with modifying. I feel stupid and defeated lmao, oh man, pls help.

Juwapa said:
Hey all, I did a bad thing. Please help.
Just wanna start off by saying I'm really stupid and things like this make me not want to modify my device anymore. I recently updated to 10.3.0, and after flashing something in the wrong order, I soft bricked my OP6. Since I wanted to basically start over with Android 10, I decided to just do a full wipe, without reading how to. I wiped all partitions through TWRP (Which I very quickly learned is a stupid thing to do) because that it how I went about installing new ROMs on my old phone. That left me with just the bootloader on my phone and nothing more. So I used fastboot to flash recovery and 10.3.0 and everything was fine, or at least I thought.
Everything has been fine for about a week now, until my phone randomly restarted. Upon reboot, my sim card wasn't reading and whenever I tried going to it's settings, it would say "com.android.phone keeps stopping" and after a bunch of searching around... I learned what an EFS Partition is and I'm pretty sure that bad boy is gone. Putting *#06# in the keypad gives me a MEID number, but no IMEI number.
So my question now is, is there anything I can do? I found a few posts that say you could try flashing ColorOS (but there is only an unofficial port for OP6), one comment I found said to use a program called EFS Professional and flash back to stock, and some others suggested MSM tool? Which I haven't used, so I have no clue what that's about. Does anyone have experience or a suggestion for me, please? Any help is greatly appreciated.
My phone is also completely working right now, apart from sim card use. The sim was also 100% working for about a week, before it randomly rebooted, is that normal? I just want to get my phone back to working order, I'm done with modifying. I feel stupid and defeated lmao, oh man, pls help.
Click to expand...
Click to collapse
Alright calm down, yes what you have done isn't smart to do but nothing is gonna change that, we can't go back in time.
First of I would start with restoring your device by using the the MSM Download Tool which you can find here --> https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
All you need to know is described in the thread, read it carefully before attempting to restore your device. It will re-lock the bootloader, wipe the internal storage and restore all the partitions on your device. Make sure you made a backup of all your important files which might be stored on your device. If those instructions are still not clear enough you could watch this video which shows how to restore your device, here is a link to that video --> https://www.youtube.com/watch?v=jtc7EhNsfPA&feature=youtu.be
After restoring your device you should check if your device shows it's IMEI number again, if not I can't help you further. I've never used the EFS Professional tool with the OP6. So attempting to restore the IMEI with that tool is on your own risk.
I hope you learn from this experience, you should always make backups of the important partitions of your device before even thinking about modifying the system on your device in any way. This won't change your current situation by saying this but it will be helpful in the future.
Good luck!

Mr.FREE_Bird said:
Alright calm down, yes what you have done isn't smart to do but nothing is gonna change that, we can't go back in time.
First of I would start with restoring your device by using the the MSM Download Tool which you can find here --> https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
All you need to know is described in the thread, read it carefully before attempting to restore your device. It will re-lock the bootloader, wipe the internal storage and restore all the partitions on your device. Make sure you made a backup of all your important files which might be stored on your device. If those instructions are still not clear enough you could watch this video which shows how to restore your device, here is a link to that video -->
&feature=youtu.be
After restoring your device you should check if your device shows it's IMEI number again, if not I can't help you further. I've never used the EFS Professional tool with the OP6. So attempting to restore the IMEI with that tool is on your own risk.
I hope you learn from this experience, you should always make backups of the important partitions of your device before even thinking about modifying the system on your device in any way. This won't change your current situation by saying this but it will be helpful in the future.
Good luck!
Click to expand...
Click to collapse
Hi, thank you so much for the quick reply. So apparently it was just a problem with xXx NoLimits, I think? I tried uninstalling it right after making the original post and now my sim is working like normal. I'm confused because I don't think I had any settings with NoLimits that should of affected the sim or even storage of my phone. So why would it work fine for a week and just randomly decide to kill itself like that? As you can see in the screenshots, my IMEI was missing and is now back.
But I'm still worried about when I had wiped all partitions, is there something funky going on with the partitions/storage of my device? Is the "EFS Partition" the only partition that can be permanently lost? If I can still make a backup of it, I should definitely do that, and is there anything else I specifically should make sure I have backed up?

Juwapa said:
Hi, thank you so much for the quick reply. So apparently it was just a problem with xXx NoLimits, I think? I tried uninstalling it right after making the original post and now my sim is working like normal. I'm confused because I don't think I had any settings with NoLimits that should of affected the sim or even storage of my phone. So why would it work fine for a week and just randomly decide to kill itself like that? As you can see in the screenshots, my IMEI was missing and is now back.
But I'm still worried about when I had wiped all partitions, is there something funky going on with the partitions/storage of my device? Is the "EFS Partition" the only partition that can be permanently lost? If I can still make a backup of it, I should definitely do that, and is there anything else I specifically should make sure I have backed up?
Click to expand...
Click to collapse
No problem!
Strange, sounds like something you configured in your xXx NoLimits config caused some trouble. Maybe you debloated an app that causes this behavior? It would be a guessing game for me.
If I was you I would restore the device using the MSM Download Tool to start clean again. After that I would make a full system backup using TWRP. So in case you do lose the EFS partition or something else you will have something to fall back on.
The EFS partition can indeed be lost but you would really need to badly mess with the system on your device. I've only once experienced a lost IMEI number after a system update on my LG G4 but I could restore it using the EFS Professional tool. The actual EFS partition was still there I think but got corrupted somehow. Luckily I had made a backup of that partition with TWRP but I still needed to write the IMEI number to it manually. You should just always make backups before attempting to modify the system on your device. Lesson learned right?

Mr.FREE_Bird said:
No problem!
Strange, sounds like something you configured in your xXx NoLimits config caused some trouble. Maybe you debloated an app that causes this behavior? It would be a guessing game for me.
If I was you I would restore the device using the MSM Download Tool to start clean again. After that I would make a full system backup using TWRP. So in case you do lose the EFS partition or something else you will have something to fall back on.
The EFS partition can indeed be lost but you would really need to badly mess with the system on your device. I've only once experienced a lost IMEI number after a system update on my LG G4 but I could restore it using the EFS Professional tool. The actual EFS partition was still there I think but got corrupted somehow. Luckily I had made a backup of that partition with TWRP but I still needed to write the IMEI number to it manually. You should just always make backups before attempting to modify the system on your device. Lesson learned right?
Click to expand...
Click to collapse
Thank you so much for this info. May I ask what the best way to actually backup the EFS Partition would be? After a quick google search, a few different apps popped up. But based on your reply, I'm assuming you've done this before, so is there a certain method you would suggest for a noob like myself?
And as far as using the MSM Tool for a complete reset/backup, do you think that would really be necessary? From what I've read, newer versions of TWRP don't even let you delete/backup the EFS Partition, which means it would be unlikely that I even actually touched that partition, right? And my experience was most likely caused by some xXx NoLimits setting then, I'd assume. I think what messed me up when I first upgraded to 10.3.0, was that I accidentally wiped the Vender partition (which I believe is what the recovery is now on?) Which is why I had to flash via fastboot. But still, I would like to backup the EFS Partition just to be assured I won't have this come up in the future. But outside of the EFS Partition, isn't it pretty easy to fix any Partition/Bricks that might occur on the OnePlus 6?
And again, thank you so much for taking the time to respond to a silly goose like me. I've made it this far without damaging ant of my phones but I think it's about time I stop playing with fire and actually read/backup important stuff haha.

Nolimit and random reboot in android 10.0.3? Turn off kernel tweaks in Nolimit profiles, and then flash Nolimit. It will be fine.

Juwapa said:
Thank you so much for this info. May I ask what the best way to actually backup the EFS Partition would be? After a quick google search, a few different apps popped up. But based on your reply, I'm assuming you've done this before, so is there a certain method you would suggest for a noob like myself?
And as far as using the MSM Tool for a complete reset/backup, do you think that would really be necessary? From what I've read, newer versions of TWRP don't even let you delete/backup the EFS Partition, which means it would be unlikely that I even actually touched that partition, right? And my experience was most likely caused by some xXx NoLimits setting then, I'd assume. I think what messed me up when I first upgraded to 10.3.0, was that I accidentally wiped the Vender partition (which I believe is what the recovery is now on?) Which is why I had to flash via fastboot. But still, I would like to backup the EFS Partition just to be assured I won't have this come up in the future. But outside of the EFS Partition, isn't it pretty easy to fix any Partition/Bricks that might occur on the OnePlus 6?
And again, thank you so much for taking the time to respond to a silly goose like me. I've made it this far without damaging ant of my phones but I think it's about time I stop playing with fire and actually read/backup important stuff haha.
Click to expand...
Click to collapse
I have always used TWRP for making a backup of the EFS Partition, the option to do so is still available in the backup section in TWRP. It is indeed very unlikely you ever touched that partition but as you experienced it isn't hard to mess up the installation of your system so you should definitely back it up just to be sure you could restore it if something goes wrong. If I'm not mistaken the recovery is actually written to the boot partition and not the vendor partition or that has changed since Android 10. But I don't see any reason to ever wipe the vendor partition. You should always carefully read instructions before installing any kind of software so you are sure you are doing it right. And yes, fixing soft bricks on the OP6 isn't hard to do when you know what you are doing. Doing research is very important, by doing so you know what you are doing, how you should do it and you will have a higher chance to fix errors in case things don't turn out to work as they should. Luckily things didn't go very wrong for you but I hope you'll spend some time doing research before you are going to modify the system on your device. It will prevent a lot of trouble. But by making mistakes you will learn to right. Oh and I almost forgot to mention that you should copy your backups to an other device or storage in case your internal storage gets wiped.
It's not a problem to give a helping hand, that's what this place is for. I'm always glad to help those who kindly ask for help. :good:

Mr.FREE_Bird said:
I have always used TWRP for making a backup of the EFS Partition, the option to do so is still available in the backup section in TWRP. It is indeed very unlikely you ever touched that partition but as you experienced it isn't hard to mess up the installation of your system so you should definitely back it up just to be sure you could restore it if something goes wrong. If I'm not mistaken the recovery is actually written to the boot partition and not the vendor partition or that has changed since Android 10. But I don't see any reason to ever wipe the vendor partition. You should always carefully read instructions before installing any kind of software so you are sure you are doing it right. And yes, fixing soft bricks on the OP6 isn't hard to do when you know what you are doing. Doing research is very important, by doing so you know what you are doing, how you should do it and you will have a higher chance to fix errors in case things don't turn out to work as they should. Luckily things didn't go very wrong for you but I hope you'll spend some time doing research before you are going to modify the system on your device. It will prevent a lot of trouble. But by making mistakes you will learn to right. Oh and I almost forgot to mention that you should copy your backups to an other device or storage in case your internal storage gets wiped.
It's not a problem to give a helping hand, that's what this place is for. I'm always glad to help those who kindly ask for help. :good:
Click to expand...
Click to collapse
So I finally had time to sit down and make backups of my device. I made a backup of just the EFS and Modem Partition only and I made another complete backup of everything. This should be all I need right?
And yes, I will keep the backups on my PC and on the flash drive I keep my current rom, recovery, kernel, and magisk on.

Shyciii said:
Nolimit and random reboot in android 10.0.3? Turn off kernel tweaks in Nolimit profiles, and then flash Nolimit. It will be fine.
Click to expand...
Click to collapse
I could be wrong, but I don't think I had KernelTweaks on to begin with. I keep reading people are having problems with it, so I think I'll just stop using it. And it wasn't reboots that were the problem, I only had the one reboot. The problem was my phone wasn't recognizing my sim card nor did it give me my IMEI number, which is why I thought I might of messed up the EFS Partition. But thank you for the reply.

I'm about out of options anyone tried using smt download mode on msm tool.? Then restoring efs partitions.? And had any success. I'm getting a sha 256 does not match error on msm tool when trying to download super partition. Op8 verizon bricked.

Brick. Stuck at "Qualcomm Crashdump"

Hi all,
My op6 is stuck, unable to reboot normally with the famous Qualcomm Crashdump mode message.
The phone has the bootloader unlocked, with TWRP recovery.
1 day ago I could access the recovery even reboot with the power+volume buttons, but it got to a point where it crashes all the time, unable to do anything.
Currently is only able to enter fastboot mode.
I have heard about the MSMDownload Tool.
- Does this tool keep the files/data in the internal memory?
For me the most important thing is to be able to recover the data.
The qualcom dumpcrash mode returns several different messages like:
- stack-protector kernel stack is corrupted in:--schedule*0xB90/OXOd0 (not exact numbers)
- fatal exceptinforece_signalinject.isra.8
Is there any chance of trying something?
I am extremely anxious and worried about the situation
Please help.

Ganapatya said:
Hi all,
My op6 is stuck, unable to reboot normally with the famous Qualcomm Crashdump mode message.
The phone has the bootloader unlocked, with TWRP recovery.
1 day ago I could access the recovery even reboot with the power+volume buttons, but it got to a point where it crashes all the time, unable to do anything.
Currently is only able to enter fastboot mode.
I have heard about the MSMDownload Tool.
- Does this tool keep the files/data in the internal memory?
For me the most important thing is to be able to recover the data.
The qualcom dumpcrash mode returns several different messages like:
- stack-protector kernel stack is corrupted in:--schedule*0xB90/OXOd0 (not exact numbers)
- fatal exceptinforece_signalinject.isra.8
Is there any chance of trying something?
I am extremely anxious and worried about the situation
Please help.
Click to expand...
Click to collapse
to start: it's good thing that you can get into fastboot mode. From there you should be able to do a complete re-install of your device, e.g. using the official LineageOS instructions.
Now to your situation: unfortunately you don't write too much about it like, is your phone running stock OOS or some custom ROM? If it's a custom ROM I'd say you open a topic in the according thread. Then: how much do you know about flashing recoveries, ROMs etc.
Regarding your data: in your current situation it may be extremely difficult if not impossible to secure any personal data now. How I understand it you cannot access the crucial partitions from the bootloader, at least I never heard of methods to get there. Although, people more knowledgeable than me may know of ways. So I do hope you are having recent backups at hand, on your PC or where-ever.
In that case I would start all over (and that's how I got out of a similar situation several months ago): flash recovery, flash latest OOS to both slots, factory reset / wipe everything (to remove any encrypted data you won't be able to access anyways), flash you ROM of choice incl. other part like GAPPS, if needed, do basic setup and then finally try to recover anything that is in you backups.
I wish you a lot of patience and good luck, you'll need it, I'm afraid.

lm089 said:
to start: it's good thing that you can get into fastboot mode. From there you should be able to do a complete re-install of your device, e.g. using the official LineageOS instructions.
Now to your situation: unfortunately you don't write too much about it like, is your phone running stock OOS or some custom ROM? If it's a custom ROM I'd say you open a topic in the according thread. Then: how much do you know about flashing recoveries, ROMs etc.
Regarding your data: in your current situation it may be extremely difficult if not impossible to secure any personal data now. How I understand it you cannot access the crucial partitions from the bootloader, at least I never heard of methods to get there. Although, people more knowledgeable than me may know of ways. So I do hope you are having recent backups at hand, on your PC or where-ever.
In that case I would start all over (and that's how I got out of a similar situation several months ago): flash recovery, flash latest OOS to both slots, factory reset / wipe everything (to remove any encrypted data you won't be able to access anyways), flash you ROM of choice incl. other part like GAPPS, if needed, do basic setup and then finally try to recover anything that is in you backups.
I wish you a lot of patience and good luck, you'll need it, I'm afraid.
Click to expand...
Click to collapse
Thank you for your reply.
is your phone running stock OOS or some custom ROM?
Click to expand...
Click to collapse
Stock OOS, android 10, last release.
Then: how much do you know about flashing recoveries, ROMs etc.
Click to expand...
Click to collapse
I have basic experience installing customs roms, rooting, twrp, unlock fastboot...following tutorials, of course.
Regarding your data: in your current situation it may be extremely difficult if not impossible to secure any personal data now. How I understand it you cannot access the crucial partitions from the bootloader, at least I never heard of methods to get there. Although, people more knowledgeable than me may know of ways. So I do hope you are having recent backups at hand, on your PC or where-ever.
Click to expand...
Click to collapse
here someone says that in theory it would be possible if you have the usb debugging enable, but silly me I had it open but I deactivated it I think, so I'm not sure if I have access or not.
OnePlus 6 Stuck At "Qualcomm Crashdump" Screen All A Sudden | Data Retrieval Critical
Hi good people at XDA. This is my first post on this website and I am absolutely hoping to receive help from you all to find a way out of the depressing and extremely anxious situation I'm in. I was using my OP6 normally today and while I was...
forum.xda-developers.com
Code:
adb devices
mkdir "C:\RECOVERED_DATA"
adb pull /sdcard C:\RECOVERED_DATA
and then finally try to recover anything that is in you backups.
Click to expand...
Click to collapse
but if I do all that flashing process any backups that are in the internal memory will be erased, right?
I had photos, files, whatsapp chat history, documents...etc and they were all in the internal memory. It is not a great loss but it is important for me to be able to recover it.
in your current situation it may be extremely difficult if not impossible to secure any personal data now
Click to expand...
Click to collapse
for me it is more important to recover the files than to recover the phone. your words are discouraging
I have read other posts and maybe being able to install on top (dirty install) the same rom I have, would leave the system as it, is being able to access my files. Not even installing the whole rom but extracting the boot image from the rom and then installing it. but I don't know if I can install a rom or boot image from fastboot, or if I need to have a working TWRP first.
It is said here:
- https://forum.xda-developers.com/t/...over-without-data-loss.4080725/#post-82257413
- https://forum.xda-developers.com/t/...over-without-data-loss.4080725/#post-82261087

Ganapatya said:
your words are discouraging
Click to expand...
Click to collapse
of course that is not my intention. I just try to be realistic
As I wrote in my post, my knowledge is quite basic. I know what I read , and what I experienced with my different devices. So again: you may find instructions and real-life stories showing you ways out of there.
My experience is that you cannot connect your OP6 phone to your PC via ADB while in bootloader / fastboot mode.
a) It's either one or the other: bootloader <=> fastboot or recovery / system <=> adb. Other devices may have different options but we're not talking about Samsung but about OP.
b) I did some additional research last night but I couldn't find a single source talking about *read* access to user data from fastboot. All you can do there is flash i.e. overwrite partitions
c) keep in mind that most probably your personal data are encrypted. So even if you find a way to access your personal data from bootloader / fastboot you may not be able to read it
d) I never used MSMtool, never had to. But I did some more research about it. It looks as if you could re-flash stock ROM using that tool but to the cost of wiping everything. At least that is what the tutorials I found are saying
That said I'd say you don't have much to lose and can go trying out some things.
From my experience the qualcomm crashdump error can have it's source in a malfunctioning recovery solution; I had that when flashing a wrong TWRP version that would not be in harmony with the previously flashed OOS firmware.
From what I read our devices don't have a separate recovery partition, instead it somehow lives somewhere/somehow in the boot partition (experts: please don't crucify me if that is wrong ). So if that is the case one idea would be to extract the boot image from the stock ROM image then flash that to /boot/ from fastboot. Don't know whether that really works and helps, but in theory you would have a default boot partition and kernel *without* a conflicting recovery solution.
In case you're successful you may be able to boot into system and make backups of everything that's valuable to you.
Again: this is extremely wild guessing here, and you'll have to read in a bit on how to properly extract parts of the ROM image.
I also would *strongly* recommend that you continue asking for help in a more technical thread like the LOS19.1 one or Funk Wizard's thread about unlocking and flashing our OP6.
I wish you all luck you need!

I think your best bet it a HW solution, get someone to:
1. replace the modem IC, it's the possible cause of the qualcomm crash
2. solder a direct connection to the internal memory so you can recover your data