Related
A day or two ago I unlocked my ChaCha using the HTCDev.com instructions. I then used DooMLoRD_v4_ROOT-zergRush-busybox-su to root it. Everything was going fine until I apparently deleted one too many system apps and now my phone is in extremis.
The problem: As the phone boots up and reaches the HTC logo screen, just when the main interface should appear, an error pops up. It says:
Code:
Sorry!
The process com.htc.bg has stopped unexpectedly. Please try again.
[Force close]
When I close it, the HTC logo appears again as the main GUI is reinitialised, which leads to the same error popping up again, thus entering into an infinite loop.
I can just about manage to connect the phone to my PC as a disk drive, but it's not connected in such a way that RUU or unrooting applications can "find" it from within Windows, so if I'm to fix this it's gotta be from the SD card/Hboot.
Details:
* HTC ChaCha with the latest Android firmware.
* Unlocked and rooted, but remains S-ON (Superuser was installed and worked).
* Used Titanium to delete apps, but made backups and have them on my hard drive for safe keeping but can't access the phone in order to restore them properly.
* I was unable to restore backed-up system apps prior to this critical problem emerging, which I think is because my phone isn't "truly" rooted. I can apparently remove from but not add to the protected areas of the phone.
* I've tried flashing the device with numerous recovery ROMs and they all fail (wrong image, etc.). I'm having an extremely difficult time finding the original ROM anywhere and more importantly finding one which will work without the phone being connected to the PC at any stage of the flashing job.
* Factory resets and recovery boots don't seem to have any effect.
* It's a carrier-locked/branded phone, from Three/Hutchison 3G UK. I'm locked into my contract for another year at least.
* Before I rebooted the phone for the last time [prior to the beginning of the above problem] I noticed that my ringtones and related media were all gone and I was unable to download new ones even using third-party apps; the "unable to download sound" error was constantly popping up and when I received messages or phone calls the phone would vibrate but wouldn't play any tones.
* My brother and I spent the better part of 6 hours scouring the net and trying every combination of steps we could think of to try and resolve this. I wouldn't have posted here if I wasn't at the end of my tether and if I hadn't tried every solution I could find from others on various forums including this one, nor would I be so quick to reveal myself to be a deletion-happy moron to a forum of experts (I saw that anti-noob YouTube clip!).
Is there any hope of fixing this issue given my obvious lack of critical faculties?
Thank you for reading this.
You can always install clockworkmod recovery and from there a custom rom. Check the relevant thread, it is pinned.
OK,
don't panic. I almost thought you'd hard bricked your phone when modifying the NAND. This is a soft brick and ALL soft bricks can be recovered, they just take a bit of pain and suffering. Sometimes more suffering than others, but that's irrelevant.
Question, you say you can't restore system apps? How did you try? If a phone is perm rooted, it's rooted. Obviously a temp root is different to a perm root, but I believe this is a perm root as you can REMOVE apps from the system memory. If a root wasn't perm, every app would be sandboxed so no app, including titaniumbackup would work.
* Unlocked and rooted, but remains S-ON (Superuser was installed and worked).
Click to expand...
Click to collapse
S-ON is part of HTC's snap on BL protection. The fact your phone is S-ON is now not that important, the BL is unlocked, thats what matters.
* Used Titanium to delete apps, but made backups and have them on my hard drive for safe keeping but can't access the phone in order to restore them properly.
Click to expand...
Click to collapse
Ok, important advice here (for future ref), you shouldn't go mad with deleting unless you've tried freezing first. Freezing allows you to recover by simply doing a factory reset. Most bootloaders (including HTC's) allow you to perform an emergency factory reset from there. You might lose all the **** on there, but you will have a working phone. You also need to be careful with TitaniumBackup, I'm sure you didn't remove the obvious important ones, but the fact you lost access to your audio means you removed a sound/media package. Next time, google "HTC chacha, safe to remove" as more people root this phone in the next few weeks, safe to remove lists will appear. For SGS (my phone) there is a whole shared google doc with a list of system apps, and the consequence of removing them.
* I was unable to restore backed-up system apps prior to this critical problem emerging, which I think is because my phone isn't "truly" rooted. I can apparently remove from but not add to the protected areas of the phone.
Click to expand...
Click to collapse
You can't restore a system app if there is a conflict. Try and identify the conflict.
* I've tried flashing the device with numerous recovery ROMs and they all fail (wrong image, etc.). I'm having an extremely difficult time finding the original ROM anywhere and more importantly finding one which will work without the phone being connected to the PC at any stage of the flashing job.
Click to expand...
Click to collapse
By the sounds of it, you are using ROMs designed for CWM. If you are going to do that, flash CWM first. There are shed loads of tutorials. If you want to install the stock rom all over again, just download the stock RUU.
* Factory resets and recovery boots don't seem to have any effect.
Click to expand...
Click to collapse
See above about freezing.
* It's a carrier-locked/branded phone, from Three/Hutchison 3G UK. I'm locked into my contract for another year at least.
Click to expand...
Click to collapse
Doesn't matter, you'll fix it, guarantee it.
* Before I rebooted the phone for the last time [prior to the beginning of the above problem] I noticed that my ringtones and related media were all gone and I was unable to download new ones even using third-party apps; the "unable to download sound" error was constantly popping up and when I received messages or phone calls the phone would vibrate but wouldn't play any tones.
Click to expand...
Click to collapse
See what I said above.
* My brother and I spent the better part of 6 hours scouring the net and trying every combination of steps we could think of to try and resolve this. I wouldn't have posted here if I wasn't at the end of my tether and if I hadn't tried every solution I could find from others on various forums including this one, nor would I be so quick to reveal myself to be a deletion-happy moron to a forum of experts (I saw that anti-noob YouTube clip!).
Click to expand...
Click to collapse
Have you tried every combination of steps? You've clearly not tried CWM. I'm not suggesting that as a silver bullet (personally, I try to avoid CWM if I can) but it's the best way to give you low level access to the NAND so you could easily flash an OTA ROM, modded ROM or even return it to stock dead quick.
For a safe to remove list, check the Themes and Apps section.
skezza said:
OK,
don't panic. I almost thought you'd hard bricked your phone when modifying the NAND. This is a soft brick and ALL soft bricks can be recovered, they just take a bit of pain and suffering. Sometimes more suffering than others, but that's irrelevant.
Click to expand...
Click to collapse
Music to my ears!
skezza said:
Question, you say you can't restore system apps? How did you try? If a phone is perm rooted, it's rooted. Obviously a temp root is different to a perm root, but I believe this is a perm root as you can REMOVE apps from the system memory. If a root wasn't perm, every app would be sandboxed so no app, including titaniumbackup would work.
Click to expand...
Click to collapse
In Titanium Backup I tried restoring the backups I made; the "Recovering Backup" notice would just hang indefinitely until I forced TB to close. This only happened with system apps. The backed up files are still on my PC hard drive from when I copied them from my SD card, but I'm not sure they're of any use at this stage.
skezza said:
S-ON is part of HTC's snap on BL protection. The fact your phone is S-ON is now not that important, the BL is unlocked, thats what matters.
Click to expand...
Click to collapse
Ahhh, this is probably my problem then. I ignored most of the fixes and workarounds listed as [S-OFF] because I didn't think they'd work for my device haha.
skezza said:
Ok, important advice here (for future ref), you shouldn't go mad with deleting unless you've tried freezing first. Freezing allows you to recover by simply doing a factory reset. Most bootloaders (including HTC's) allow you to perform an emergency factory reset from there. You might lose all the **** on there, but you will have a working phone. You also need to be careful with TitaniumBackup, I'm sure you didn't remove the obvious important ones, but the fact you lost access to your audio means you removed a sound/media package. Next time, google "HTC chacha, safe to remove" as more people root this phone in the next few weeks, safe to remove lists will appear. For SGS (my phone) there is a whole shared google doc with a list of system apps, and the consequence of removing them.
Click to expand...
Click to collapse
I'm disappointed in myself for being so haphazard in my deleting, I'm usually not that stupid but I think I was a little overexcited to have finally gotten rid of some of the bloatware that'd irritated me for so long haha. I was like "oh boy, I can save even more battery power and internal space if I just remove a little more!". Lesson learnt
skezza said:
By the sounds of it, you are using ROMs designed for CWM. If you are going to do that, flash CWM first. There are shed loads of tutorials. If you want to install the stock rom all over again, just download the stock RUU.
...
Have you tried every combination of steps? You've clearly not tried CWM. I'm not suggesting that as a silver bullet (personally, I try to avoid CWM if I can) but it's the best way to give you low level access to the NAND so you could easily flash an OTA ROM, modded ROM or even return it to stock dead quick.
Click to expand...
Click to collapse
As I said above I didn't realise I could make use of [S-OFF] materials so I didn't even attempt them for fear of making matters worse. I just now attempted to flash CWM and it hung on "parsing" which is what happened with previous flash attempts. If a flash attempt doesn't hang on "parsing" it parses for a second and then goes back to the main menu, apparently having no effect.
I'd be lying if I said I'm not overwhelmed by all of this; the tutorials I've read seem to assume a fair degree of prior knowledge that I definitely don't have haha. I hope I don't stretch anyone's patience here, but if you could explain it to me like a 6-year-old whose mother drank heavily during pregnancy I think it will help move things along!
Thank you for the thorough reply, much appreciated
Follow this to flash CWM, you need to do it with your computer and using fastboot, this is needed for S-ON phones.
http://forum.xda-developers.com/showthread.php?t=1449681
dapaua said:
Follow this to flash CWM, you need to do it with your computer and using fastboot, this is needed for S-ON phones.
http://forum.xda-developers.com/showthread.php?t=1449681
Click to expand...
Click to collapse
Unfortunately I can't do anything via my computer; my phone isn't "discovered" by the command line, unrooting tools or anything else. It does allow me to access the SD card as a hard drive but that's all it does. Obviously this wasn't the case before my problems started, because I used my PC to root and unlock the phone originally, but now the phone's boot process can't reach a point where it becomes receptive to the PC's commands. I don't know why it lets me access the SD card though.
Is there any way to do this without my PC being involved beyond transferring files to the SD card? If not, am I screwed? haha
Thanks mate!
Can you boot into the bootloader (Whith the phone off, press Volume down + power for five seconds)?
Then boot into it, move up with the volume keys and then choose fastboot.
Then follow the procedures in the link I posted previously http://forum.xda-developers.com/showthread.php?t=1449681 (start from step 3). Fastboot mode should be recognized.
The fastboot binary is here C:\Program Files (x86)\Android\android-sdk\tools , if you installed the android SDK, which I asume you did.
Good luck, I hope this works!
dapaua said:
Can you boot into the bootloader (Whith the phone off, press Volume down + power for five seconds)?
Then boot into it, move up with the volume keys and then choose fastboot.
Then follow the procedures in the link I posted previously http://forum.xda-developers.com/showthread.php?t=1449681 (start from step 3). Fastboot mode should be recognized.
Click to expand...
Click to collapse
Dear CHRIST thank you for that - I didn't know about this feature, and it worked! I was able to connect to my PC and do everything I needed to. I used the command line to flash the CWM, then followed instructions for partitioning the SD card and installing a custom ROM. I feel like a real [email protected] I wonder if Anonymous are looking for any new recruits...
dapaua said:
Good luck, I hope this works!
Click to expand...
Click to collapse
It did - I'm back in business!! Thank you mate, if I could fellate you via WiFi I probably would. You'd have to be wearing some anti-virus trousers though, I'm not a slut.
Cheers!
PaddyM said:
Dear CHRIST thank you for that - I didn't...
Click to expand...
Click to collapse
Great news (I thought you already knew about the recovery menu feature otherwise I'd have mentioned it).
As I said in my reply earlier, every soft brick can be fixed somehow. Some are just harder than others. If I'm honest, it seems like yours was pretty straightforward once you got into the Recovery menu.
By the way, if you decide you want to return to stock, you can do that quite easily. Also, if I was you, do the freezing technique I suggested earlier and use the safe list that's available.
If you keep CWM, do a Nandroid backup. You don't have to keep it on your SD, but they are great for doing a very fast recovery. I can usually restore my phone in about 10 - 15 minutes using Nandroid.
PaddyM said:
Dear CHRIST thank you for that - I didn't know about this feature, and it worked! I was able to connect to my PC and do everything I needed to. I used the command line to flash the CWM, then followed instructions for partitioning the SD card and installing a custom ROM. I feel like a real [email protected] I wonder if Anonymous are looking for any new recruits...
It did - I'm back in business!! Thank you mate, if I could fellate you via WiFi I probably would. You'd have to be wearing some anti-virus trousers though, I'm not a slut.
Cheers!
Click to expand...
Click to collapse
I'm happy it worked. Let's hope WiFi technology improves in the future
skezza said:
Great news (I thought you already knew about the recovery menu feature otherwise I'd have mentioned it).
Click to expand...
Click to collapse
I knew about the recovery menu (the stock one, at least) but I didn't realise I could go into the Fastboot option and for the phone to then be recognisable to the PC, thus making it possible to flash via the command line. If I had known that I probably wouldn't have needed to post this thread at all haha.
skezza said:
As I said in my reply earlier, every soft brick can be fixed somehow. Some are just harder than others. If I'm honest, it seems like yours was pretty straightforward once you got into the Recovery menu.
Click to expand...
Click to collapse
Yeah... I think if it happened to one of you guys you probably would have had it sorted in about 6 minutes. 3 days isn't bad for my first attempt though! hahaha
skezza said:
By the way, if you decide you want to return to stock, you can do that quite easily. Also, if I was you, do the freezing technique I suggested earlier and use the safe list that's available.
If you keep CWM, do a Nandroid backup. You don't have to keep it on your SD, but they are great for doing a very fast recovery. I can usually restore my phone in about 10 - 15 minutes using Nandroid.
Click to expand...
Click to collapse
Thanks for the advice man, I'll definitely be looking into the Nandroid backup option, although I hope I've learnt enough from this experience to have no need for it
Thanks to everyone who posted here, I appreciate the patience and the tolerance of my noobery.
Funnily enough, I tried TitaniumBackup today and the original poster is correct. While you can freeze, remove apps etc, you can't return them. especially system. I've not tried any of the alternative install methods that TB uses, but it's quite interesting.
TB is a bit quirky, I think. The system apps won't restore at all, but sometimes apps that I've downloaded myself will restore and other times they won't (the "Restoring App" notice just hangs there indefinitely). I usually find that forcing TB to close and then trying again does the trick, but I can't figure out why it happens in the first place.
Im wondering if anyone else has worked out a good configuration that will allow it to work every time?
I'm sure it's been beaten like a dead horse... Yes I have searched all over XDA and other resources. It seems every time I think I find something... I'm one setting short or one model away from what would work.
Been working on this way too long and now I ask for your help.
I have a client who lost her daughter. (She drown). She has her phone (S3 I535 verizon) but no idea what the lock pin would be and has tried a couple but none work. Unfortunately she's on attempt 8/10 so two more tries and the phone factory resets and all is lost.
She really wants to recover her daughter's pictures and if possible remove the screen lock without losing data (either works for her if it can be done).
I've tried everything I can find.
While she has her gmail and password, when we logged in device manager listed no active devices. (was able to recover some pictures from a backup, but it appears gmail didn't back up more than a couple from a couple years ago.)
Logged into samsung to remote unlock it, but again, no devices on account.
ADB is a no-go because USB debugging is OFF
Tried to put TWRP on it but odin failed
(Found a thread here that seems to be quality but can't load the program in stock recovery and cant get CWM or TWRP on it without debugging.)
Any ideas?
I do not know the android version, but I suspect it is the newest. I used my old S3 to replicate it so I could try these things without damaging her phone and losing the data, and it's running 4.4.2
If you couldn't flash a recovery using Odin then you're probably right about it being on one of the newer versions(your phone), the boot loader got locked up tight and the only recovery we have available is Safestrap. This is a tough one. I'm no expert by far, take what I'm saying with a grain of salt and do your own researching before taking any action after reading this! I see two ways of recovering some or all data if the bootloader is locked(and the device storage isn't encrypted)
1. If you don't have equipment to directly read/write to the internal storage then point her somewhere that specializes in data recovery on smart phones.
2. Factory reset the device, try to recover "deleted" data.
If the bootloader wasn't/isn't locked down then you could probably flash a rom that didn't have the lock screen pin/pattern ect implemented. I don't have the i535 but I know that the prepaid version checks the system partition when flashing via Odin so this probably wouldn't work if it's locked but I can't confirm wether or not this is checked on the i535
Can you enter the stock recovery on the daughters phone just to verify if its updated or not. Should be a string near the top. If it ends with ne1 its on 4.4.2 and I don't recall the one for 4.3. If you're unable to enter the recovery because you have to enter the pin before there's an actual lock screen(with the clock, status bar, wallpaper ect) then it's likely encrypted and there's nothing that you can do about that.
OpenSourcererSweg said:
If you couldn't flash a recovery using Odin then you're probably right about it being on one of the newer versions(your phone), the boot loader got locked up tight and the only recovery we have available is Safestrap. This is a tough one. I'm no expert by far, take what I'm saying with a grain of salt and do your own researching before taking any action after reading this! I see two ways of recovering some or all data if the bootloader is locked(and the device storage isn't encrypted)
1. If you don't have equipment to directly read/write to the internal storage then point her somewhere that specializes in data recovery on smart phones.
2. Factory reset the device, try to recover "deleted" data.
If the bootloader wasn't/isn't locked down then you could probably flash a rom that didn't have the lock screen pin/pattern ect implemented. I don't have the i535 but I know that the prepaid version checks the system partition when flashing via Odin so this probably wouldn't work if it's locked but I can't confirm wether or not this is checked on the i535
Can you enter the stock recovery on the daughters phone just to verify if its updated or not. Should be a string near the top. If it ends with ne1 its on 4.4.2 and I don't recall the one for 4.3. If you're unable to enter the recovery because you have to enter the pin before there's an actual lock screen(with the clock, status bar, wallpaper ect) then it's likely encrypted and there's nothing that you can do about that.
Click to expand...
Click to collapse
I can enter recovery mode and I do believe it is 4.4.2.
because of the delicate nature of her phone (being her passed on daughter's and she used 9 of 10 attempts to guess her pin) I pulled my S3 out of the drawer (coincidentally I stopped using it about 2 weeks after she passed) and everything is identical down to the recovery string at the top. I know it's running the same software and I have all kinds of old pictures and texts on it like she would have and I am logged into gmail on it like she is. I locked the screen on MINE and I know the PIN on MINE. I also saved a backup of my stuff so I'm using my phone as the tester since I was able to put in in the identical situation
I have room to play because of that. Once I have success on mine, I'll try what worked on mine on hers.
So far I've tried...
play.google unlock... While I have now been able to get her device to appear on device manager on google's site, they changed it so that when I remote lock it the screen lock pin does NOT change.
I called Google, Samsung, and VERIZON. None have the ability to change or remove lock screen pin.
I tried ADB, but it doesn't detect any devices when I ADB shell or ADB device.
USB DEBUGGING IS OFF (or we wouldn't be having this convo)
It has stock recovery and not CWM or TWRP (again if I could get one of those on there, we wouldn't be having this convo) (tried ODIN flashing TWRP on, but fails)
---------------------------
Every direction I head I hit a brick wall.
I've never heard of being able to recover data from internal SDcard after reset. Didn't think that was possible.
FYI. recovery mode string is...
ANDROID system recovery <3e>
KOT49H.I535VRUDNE1
Wking46 said:
I can enter recovery mode and I do believe it is 4.4.2.
because of the delicate nature of her phone (being her passed on daughter's and she used 9 of 10 attempts to guess her pin) I pulled my S3 out of the drawer (coincidentally I stopped using it about 2 weeks after she passed) and everything is identical down to the recovery string at the top. I know it's running the same software and I have all kinds of old pictures and texts on it like she would have and I am logged into gmail on it like she is. I locked the screen on MINE and I know the PIN on MINE. I also saved a backup of my stuff so I'm using my phone as the tester since I was able to put in in the identical situation
I have room to play because of that. Once I have success on mine, I'll try what worked on mine on hers.
So far I've tried...
play.google unlock... While I have now been able to get her device to appear on device manager on google's site, they changed it so that when I remote lock it the screen lock pin does NOT change.
I called Google, Samsung, and VERIZON. None have the ability to change or remove lock screen pin.
I tried ADB, but it doesn't detect any devices when I ADB shell or ADB device.
USB DEBUGGING IS OFF (or we wouldn't be having this convo)
It has stock recovery and not CWM or TWRP (again if I could get one of those on there, we wouldn't be having this convo) (tried ODIN flashing TWRP on, but fails)
---------------------------
Every direction I head I hit a brick wall.
I've never heard of being able to recover data from internal SDcard after reset. Didn't think that was possible.
Click to expand...
Click to collapse
With HDDs I know it's possible as I have done it before. The only issue is not overwriting the data when reinstalling a operating system ect. Flash is abit dififfrent but still doesnt overwrite deleted data as soon as its deleted. If you're willing to try it on your gs3 first then go for it. Since the data is very important, I would have her take it to someone who specializes in data recovery instead of trying to wipe it and get the data off it just in case.
Are you able to remotely install applications though the Google Play site or by other means? Might be able to get a shell from one of the ssh server apps if they run the server on startup. If you can get a shell you should be able to work from there.
OpenSourcererSweg said:
With HDDs I know it's possible as I have done it before. The only issue is not overwriting the data when reinstalling a operating system ect. Flash is abit dififfrent but still doesnt overwrite deleted data as soon as its deleted. If you're willing to try it on your gs3 first then go for it. Since the data is very important, I would have her take it to someone who specializes in data recovery instead of trying to wipe it and get the data off it just in case.
Are you able to remotely install applications though the Google Play site or by other means? Might be able to get a shell from one of the ssh server apps if they run the server on startup. If you can get a shell you should be able to work from there.
Click to expand...
Click to collapse
I can remotely install apps via google play site. If I could find a shell that works on startup... please let me know what that does for me?
Wking46 said:
I can remotely install apps via google play site. If I could find a shell that works on startup... please let me know what that does for me?
Click to expand...
Click to collapse
SSH access may let you transfer some files on the device to another machine. (Assuming that it will connect to known wifi networks while locked)
OpenSourcererSweg said:
SSH access may let you transfer some files on the device to another machine. (Assuming that it will connect to known wifi networks while locked)
Click to expand...
Click to collapse
No such luck. Looks like all of them would need me to log in to set them up, which defeats the purpose.
I may have to wait and see if tech changes over time and keep trying until it does.
Wking46 said:
No such luck. Looks like all of them would need me to log in to set them up, which defeats the purpose.
I may have to wait and see if tech changes over time and keep trying until it does.
Click to expand...
Click to collapse
Take a look at this, https://www.nowsecure.com/blog/2015/06/16/remote-code-execution-as-system-user-on-samsung-phones/ may be able to remove the pin. Sorry if discussion about this isn't allowed or frowned upon. Seems like a pain and it may not work for the s3
OpenSourcererSweg said:
Take a look at this, https://www.nowsecure.com/blog/2015/06/16/remote-code-execution-as-system-user-on-samsung-phones/ may be able to remove the pin. Sorry if discussion about this isn't allowed or frowned upon. Seems like a pain and it may not work for the s3
Click to expand...
Click to collapse
Doesn't effect S3 vzw. only S4 and up
Wking46 said:
Doesn't effect S3 vzw. only S4 and up
Click to expand...
Click to collapse
Ah I read "swift" as Swype and my Prepaid Verizon GS3 came with Swype preinstalled.
I have an idea, perhaps try the Verizon repair software "repair" the device to back up data while in Odin mode? I don't recall if it will require a password or anything.I don't believe it required USB debugging to be enabled, don't know if it works while in Odin mode. I don't know if the backups are encrypted or not. You can try using sandboxie to see where it keeps the backed up data. I don't know if it will backup data while you're in Odin mode though. Worth trying I suppose. Don't have time try my The self or I would. Sorry for the rushed message, I'll be home in about an hour though.
Hey guys!
To start, I want to say what an amazing place XDA is and how much information and knowledge you can get from here and how awesome the moderators are. I don't think I could ever find another amazing and/or helpful community such as those found here! Thanks to all who have helped me out with my Android issues!
Now to my issue and I apologize ahead of time if there is another thread (or related thread) found in the forum.
As the title states, I have a 2013 Motorola Moto G XT1031 Boost Mobile device. I had upgraded it to Lollipop 5.0.2 or 5.1 when it came out (I can't remember which one it was) and I had then decided to root it. I can say that I believe I was successful in rooting the device because I was able to install Supersu and use RootChecker to verify the install. Everything was going okay until i decided to research and eventually install a custom recovery and attempt to install a custom ROM. Well, let's just say that the recovery install was a bust...
In doing my research for a custom recovery, I found that TWRP had a custom recovery for my phone and apparently for my firmware via TWRP's app on the Play Store. So, I searched for my device in their in-app search for a custom recovery, downloaded it and installed it from the app. Now, my gut told me that this probably wouldn't work and that I should probably be installing a custom recovery via CLI. Nope. I didn't do this. Instead, like I said, I installed a custom recovery from the app itself. That screwed things up for me. I have no idea if it was the install, but my phone began to act incredibly strange. When in the TWRP recovery, my screen had this line that would continuously scroll from top to bottom. It wasn't a completely solid line, but it was transparent, almost like an empty thermometer glass stick was going down the screen. It was weird and not normal. I figured the phone's software was partially broken. It only did this in the TWRP recovery. Nowhere else did this happen. It was slightly annoying.
Later on I decided to install a custom ROM. Again, I did the necessary research to find out if there were any ROMs available for my phone (using XDA of course and others) and found that there were a few out there. So, I downloaded one (wish I could remember which one) and attempted to install it...keyword there. After attempting the install, my phone would not boot. Like at all. Dead. So back to the drawing board I went to try and reverse the damage. Using XDA (ironically) and a plethora of other sites, I tried to resurrect my phone and bring it back to life. After countless hours of trying and trying and trying and more and more research, I just gave up. The phone is dead. Great. $170 spent on a phone to break it a year later.
It's been roughly 4-5 months since I have attempted to redo the process and after another minor attempt, somehow I was able to remove the root completely, including the custom recovery and ROM. I don't know what the heck I did, but it worked....sort of. The phone is now stuck in a bootloop on the logo and sometimes the "bootloader has been unlocked" screen when try and factory reset the phone from the default recovery. When trying to reinstall the stock firmware, I read everywhere that I need the phone to have USB-debugging set and to have this and that. I have this and that installed on my PC, but obviously cannot enable USB-debugging which is needed for ADB and fastboot to recognize my device.
So, my question for anyone who would like to help me out is this: what are my options? Is the phone recoverable? Is there any way I can get ADB/fastboot to see my device and finally install the stock firmware on the phone? I have the proper drivers installed and ADB/fastboot are on my PC. Any help would be amazing, even if you have to tell me to junk it.
blckdragn22 said:
When trying to reinstall the stock firmware, I read everywhere that I need the phone to have USB-debugging set
Click to expand...
Click to collapse
This is incorrect, where did you read that? To reinstall the stock firmware using fastboot, you must be able to boot to the bootloader menu only.
I heard this from a few websites actually, although I could never find a situational fix for my phone. I am trying to restore back to Lollipop without a custom recovery, because within the past hour I found out TWRP was never fully removed when I tried booting into recovery from the AP Fastboot menu when doing to power+vol down option. The TWRP logo shows for about 10 seconds and then the phone tries booting normally, showing the unlocked bootloader warning.
So, yes I can boot into the bootloader menu all day long with no problems. It's just an selection I make doesn't get me anywhere. My question I guess now is: how do I go about reinstalling stock firmware via the bootloader menu. I have Minimal ADB and Fastboot installed on my PC. If I need the full ADB, I can download that. And of course I'd need the firmware, too.
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
_that said:
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Click to expand...
Click to collapse
This thread had the firmware I was looking for thank you. I believe I have the flashing stock firmware process down, I hope. I'l refer to the guide if I need help. Thank you so much!
_that said:
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Click to expand...
Click to collapse
I am trying to follow the steps listed here http://forum.xda-developers.com/showthread.php?t=2542219&page=35 and for some reason I cannot run any of the commands pertaining to the sparsechunks. This is what I get:
Is there anything you could tell me about that?
Edit: I was able to figure what the issue was when trying to write the sparsechunks. I had to insert a "." after 'sparsechunk' because that is how the file is named in the folder. However, now I am getting a new error, but it takes place on the phone screen. Every time I attempt to write a sparsechunk, it will initiate the process of doing so, but on the phone I'll get what appears to be an error saying, "Image is too large" in pink lettering. Why does this happen? Each sparsechunk file is at least 4MB less than the max-sparse-size according to the ADB and my phone, which is set to 256MB. Is there any way to change that?
blckdragn22 said:
However, now I am getting a new error, but it takes place on the phone screen. Every time I attempt to write a sparsechunk, it will initiate the process of doing so, but on the phone I'll get what appears to be an error saying, "Image is too large" in pink lettering. Why does this happen? Each sparsechunk file is at least 4MB less than the max-sparse-size according to the ADB and my phone, which is set to 256MB. Is there any way to change that?
Click to expand...
Click to collapse
Check which sparsechunk files you have and make sure you flash all of them in ascending order. If it still fails, copy/paste the contents of your command prompt window (no screenshots please).
_that said:
Check which sparsechunk files you have and make sure you flash all of them in ascending order. If it still fails, copy/paste the contents of your command prompt window (no screenshots please).
Click to expand...
Click to collapse
I will try that. There was a ...sparsechunks.0 as well apart from sparsechunks.1, sparsechunks.2 and sparsechunks.3. Shall I include that, too?
And adding the screenshot was an amateur mistake. My bad.
@_that this worked like a charm. Phone is 100% working ans usable now. Incredibly helpful. Thank you so much!
Hi everybody,
Yesterday I was using my beloved(!) Vivo Nex S (Chinese 256GB version, no root, removed some bloatware some months ago, Nova launcher, rest original) in a normal way, put it away and wanted to use it again about 1 minute later again. When I tried to access the fingerprint reader, I recognized, that the fingerprint reader didn't get green when approaching my finger. After about 2 seconds of trying, my Nex made a reset.
I could only turn it on by pressing the power button for more than 10 seconds begining from there. Until then, I just see the Nex Logo, then the stars flying, then the Nex Logo again. It changes colors, again and again, and after about 2 minutes it shuts down and vibrates twice.
Starting the phone while pressing down the volume up button at the same time, brings me to the chinese Fastboot mode menu. I've the desicion between reboot (no other effect than described above) and Recovery. Chosing recovery, it shows the Vivo Logo again and after about 2 seconds "Your device is corrupt. It can't be trusted and will not boot. Visit this link on another device: g.co/ABH". After 30 seconds it shuts down. No access to the recovery menu!
I contacted the (Indian) chat from Vivo support. The Vivo support doesn't want to be responsible, because I bought my phone in China. Sending it back would probably mean, that I definitely lose my data and that it will take a long time until it's back.
So I tried to get access over USB. I can see "Qualcomm HS-USB Diagnostics 900E" [SIC, it's NOT 9008!] on COM7. I then tried to get access using ADB, where I'm really unfamiliar with. Didn't get any connection. So I tried QFIL, where I could see my phone in the top line of the program, but didn't get any access. (Neither I'm a pro there...)
So, now my biggest hope at the moment: Is there a possibility to get access to my phone using ASTool? I read about it, that it should be a great helper in such problems, and that there could be some hope, that I could even save my data by just flashing some "sectors" of the original system. But there's another problem: This software seems to be not freeware, and all the hacks around have trojans inside.
What do you think about it? Does anybody of you pros have a clue, how to get into the phone, flash a new boot there and how to save my data (about 220GB, desoldering of the memory is not (yet) an option)?
Thanks A LOT in advance to everyone!
Edimahler said:
Hi everybody,
Yesterday I was using my beloved(!) Vivo Nex S (Chinese 256GB version, no root, removed some bloatware some months ago, Nova launcher, rest original) in a normal way, put it away and wanted to use it again about 1 minute later again. When I tried to access the fingerprint reader, I recognized, that the fingerprint reader didn't get green when approaching my finger. After about 2 seconds of trying, my Nex made a reset.
I could only turn it on by pressing the power button for more than 10 seconds begining from there. Until then, I just see the Nex Logo, then the stars flying, then the Nex Logo again. It changes colors, again and again, and after about 2 minutes it shuts down and vibrates twice.
Starting the phone while pressing down the volume up button at the same time, brings me to the chinese Fastboot mode menu. I've the desicion between reboot (no other effect than described above) and Recovery. Chosing recovery, it shows the Vivo Logo again and after about 2 seconds "Your device is corrupt. It can't be trusted and will not boot. Visit this link on another device: g.co/ABH". After 30 seconds it shuts down. No access to the recovery menu!
I contacted the (Indian) chat from Vivo support. The Vivo support doesn't want to be responsible, because I bought my phone in China. Sending it back would probably mean, that I definitely lose my data and that it will take a long time until it's back.
So I tried to get access over USB. I can see "Qualcomm HS-USB Diagnostics 900E" [SIC, it's NOT 9008!] on COM7. I then tried to get access using ADB, where I'm really unfamiliar with. Didn't get any connection. So I tried QFIL, where I could see my phone in the top line of the program, but didn't get any access. (Neither I'm a pro there...)
So, now my biggest hope at the moment: Is there a possibility to get access to my phone using ASTool? I read about it, that it should be a great helper in such problems, and that there could be some hope, that I could even save my data by just flashing some "sectors" of the original system. But there's another problem: This software seems to be not freeware, and all the hacks around have trojans inside.
What do you think about it? Does anybody of you pros have a clue, how to get into the phone, flash a new boot there and how to save my data (about 220GB, desoldering of the memory is not (yet) an option)?
Thanks A LOT in advance to everyone!
Click to expand...
Click to collapse
That sucks. I don't have a solution but I'm curious as to what is taking up 220GB on your phone?
I suggest rescuing the phone first and forgetting about the data.
Twotems said:
That sucks. I don't have a solution but I'm curious as to what is taking up 220GB on your phone?
I suggest rescuing the phone first and forgetting about the data.
Click to expand...
Click to collapse
Well... As long as there is some free flash space, it will be used, right? There are especially 4K movies from our trip to Australia and from my construction works at home (I'm building a pretty special smart home), because the picture quality of the phone was much better than the one of the Lumix TZ81. Some of them luckily have been backuped already.
Well, I could also try to wipe the whole memory first, but I thought I could try to just flash the boot area and get back my data as well and then afterwards make a proper installation again.
But how to enter the phone now again? Any ideas? And should I try the global ROM then (would be my favourite) or just the Chinese again?
Thanks for any comments...
Edimahler said:
Well... As long as there is some free flash space, it will be used, right? There are especially 4K movies from our trip to Australia and from my construction works at home (I'm building a pretty special smart home), because the picture quality of the phone was much better than the one of the Lumix TZ81. Some of them luckily have been backuped already.
Well, I could also try to wipe the whole memory first, but I thought I could try to just flash the boot area and get back my data as well and then afterwards make a proper installation again.
But how to enter the phone now again? Any ideas? And should I try the global ROM then (would be my favourite) or just the Chinese again?
Thanks for any comments...
Click to expand...
Click to collapse
I can't help you unfortunately. But I know you can't flash the global rom to the Chinese version and vice versa.
The only alternative solution is find experience third-party service in your country.
Otherwise you must send it to China and local Vivo service point.
And always take backup your staff on phone to pc or external drive now you wouldn't have worry if you had taken backup.
No 1 rule owning any kind electronic devices is to have backup because you never know with electronics device they're always a chance for hardware failure.
You don't leave this thing to luck.
Sent from my iPad using Tapatalk
Yes, I read a lot about the global ROM on Chinese Vivo Nex in the according thread in the meantime. I'm even thinking in opening my phone and bridge the contacts to get into the 9008 mode forballvofbyou (and for me of course ) instead of sending it back to China. But I'm afraid that I wouldn't even recognize, if I was successful there...
And yes, of course I learned that a (recent) backup would have been nice...
Now, for the moment I plan to flash the chinese ROM first again, in order to maybe being able to savevsome of my data first. Is AFT the right way? There's some kind of a "hack" needed in order to use it, and this one seems to have a Trojan inside! Isvthere a "trojanfree" solution somewhere?
Best regards and thanks a lot for your replies!
Disable Windows defender and run the tool.
That's what I did myself when tried last summer flash global rom to Chinese version.
There's instructions and video tutorial here at Vivo Nex thread a member who upload about how to flash using AFTool
https://forum.xda-developers.com/nex/how-to/rom-vivo-nex-global-rom-1-7-18-service-t3831866/page2
Post 15.
But in order to flash Chinese rom you need having the full zip file and I don't know if there's a indipended source of downloaded.
Easy firmware site has only global rom but not Chinese one last time check.
And doubt Vivo support will provide you that file you'll need in order re flashing you existing Chinese rom version.
Sent from my iPad using Tapatalk
paatha13 said:
Disable Windows defender and run the tool.
Click to expand...
Click to collapse
Well, there's a Trojan in the authorisation tool in the version I got. Did you have to activate yours using this activation tool under your link, or is it usable without this activation as well?
paatha13 said:
But in order to flash Chinese rom you need having the full zip file and I don't know if there's a indipended source of downloaded.
Easy firmware site has only global rom but not Chinese one last time check.
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
I think, I would even need the Flashfile itself, as I'm not able to transfer the files from a ZIP-file into the internal memory anymore. And yes, you're right. Have been searching the Chinese ROM now for hours, but didn't find it anywhere... :crying:
Found the Chinese (official!) download of the ROM, just for those, who are interested:
http://sysupwrdl.vivo.com.cn/upgrad...es/PD1805_A_1.21.3-update-full_1541422501.zip
It's not even needed to have a stupid Baidu account (which is just registerable using a chinese phone number, which again is just possible to use a Russian phone number creater, which again is not so easy because most of the numbers are already bloked, which...). No, it's just a normal, direct download link!
And hey guys: This evening my Vivo Nex just started to be able to enter the Fastboot menu again!!! Why ever, but that's partial good news (for me at least).
And again for all of them, who want to have an English translation of the menu structure; Here it is !
- Reboot System
- Wipe Data
---- Clear Cache
---- Restore all settings
---- Clear all data
---- Return
- Install Update
---- Mobile phone storage
---- SD card
---- Return
- System repair mode
---- Enter system repair mode
--------- Restart
--------- Download latest version and installation (using WLAN)
--------- Shutdown
---- Cancel
- Power down
- Advanced options
---- Upgrade via USB
---- Upgrade Systems & 3rd party applications
--------- Mobile phone storage
--------- SD card
--------- Return
---- Verify system file integrity
---- Open ADB restart
---- View the upgrade log
---- Return
Some words, what I've seen on my soft bricked phone this evening:
- Wipe data -- Clear Cache: Tried this, but without any changes in behaviour
- Install Update -- Mobile phone storage: Didn't find any backup from Vivo in all the folders and subfolders on my phone. Even though, I could see the whole folder structure from my phone, so theoretically all the data are still there!
- Install Update -- SD card: Just trying this, as soon as the download of the Chinese ROM finished. Maybe with a dirty Flash I would be able to reboot?
BTW: IS THERE A WAY TO JUST FLASH SOME SINGLE FILES INSTEAD OF THE WHOLE ZIP FILE?
- System repair mode -- Download latest version and installation: A message pops up, that nearby WLANs are being searched. But after about 10 seconds it turns back to the previous menu, whithout any success.
- Advanced options -- Verify system file integrity: I get a pass here!!! Unbelievable... Don't know what's still hindering my phone to boot up just in a normal way...
- Advanced options -- Open ADB restart: Could this maybe help to enter the 9008 mode, which many of you out there are trying to reach? Don't understand this in detail, so please don't be mad about me, if this is a silly question...
Thanks for your patience with me, and hope, that some of the information could maybe also help someone of you out there...?
Edimahler said:
Well, there's a Trojan in the authorisation tool in the version I got. Did you have to activate yours using this activation tool under your link, or is it usable without this activation as well?
Click to expand...
Click to collapse
Use this and check for Trojan without extracking the zip file.
virustotal.com
Windows defender its not that trustable and it's full of **** many times when detect something that's not harmful actually.
Yes you need to activate via username and password given on instructions.
Sent from my iPad using Tapatalk
paatha13 said:
Yes you need to activate via username and password given on instructions.
Click to expand...
Click to collapse
Seems as I found an already patched version now, which also seems to be free of malware (at least on my PC, using the Windows defender):
https://mega.nz/#!zrohlSBL!5geOCXwSFHMPCACKjOqLNVF_V8t1jFvZc6FrZj63xOM
Next problem: Can I use AFTool (which is up now) to flash the Chinese ROM to my Vivo Nex again, without having the 9008 mode? And how to do it? Most videos showing solutions in the internet are about cracking the software and not how to use it afterwards...
Well, I tried to find the "fastboot_flash_all" file in my downloaded version of the firmware. But can't find it there (see below).
Because of this I tried using QFIL, but can't find the MBN file again... Boah, it's a really hard puzzle this time...
Unfortunately I can't help you further as my knowledge and only experience was when tried last summer to flash global to Chinese version but it failed and dropped any further examination and leave it as it is.
I haven't tried re flashing existing rom wearing Chinese version device using AFTOOL.
Vivo tools really sucks on those aspect and they're not helping either but just saying to anyone has problem visit Vivo official service.
All the info you can get here xda is the specific topic only provide you above.
Maybe you can try sent pm to member who gave all the information and idea of how using AFTOOL.
Sent from my iPad using Tapatalk
paatha13 said:
Unfortunately I can't help you further as my knowledge and only experience was when tried last summer to flash global to Chinese version but it failed and dropped any further examination and leave it as it is.
Click to expand...
Click to collapse
Dear paatha13, Thanks anyway for your support and your ideas! In the meantime I maybe "accidentially" unlocked the boatloader. Being desperate, I tried everything. Hope it didn't really happen or at least, that it won't have an influence on the warranty of the device... Yes, maybe it's just better to give up there and send it back for "Mainboard exchange", as they call it.
If you're still interested in trying to change to the global version (for me it's really in the background at the moment), maybe this "Unlocking-tool" could help you somehow. I posted the link in the according thread here:
https://forum.xda-developers.com/nex/how-to/guide-vivo-nex-s-apps-safe-to-uninstall-t3813308/page17#post79131637
(in Message #165)
paatha13 said:
Vivo tools really sucks on those aspect and they're not helping either but just saying to anyone has problem visit Vivo official service.
Click to expand...
Click to collapse
Completely agree, it really sucks, that they aren't interested in helping in an easy way by blocking everything.
Well, thanks again, hope I'll be able to help also once. Even if it's only in a "mental supporting" way.
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