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
Related
Hello
First of all, let me explain the situation:
My phone is the Oneplus One, currently with no OS, the reason being - because i wanted to re-root my phone after the Oneplus updated (this update was a while ago) either way many problems occurred and i figured the easiest way to re-root my device is to simply wipe it, and try again on a clean slate.
I attempted to wipe my phone, but did it the complete wrong way. Instead of using the OS's wiping strategy, i may of used the recovery's one instead, doing so i clean swooped the OS right off my phone.
At the moment, the phone has no OS installed - nor is the phone rooted. The phone isn't capable of passing files over through usb debugging because the computer doesn't recognise it no more. (It did have usb debugging turn't on). Of course i need to reinstall an OS on the phone. The TWRP recovery is working fine. But i do not know how to do it. I looked up things such as mounting, didn't really understand the vague explanations given by the helpers of this forum (i am slow haha ). If someone is able to point me in the right direction in how to simply put an OS back into the phone some how i would be grateful.
I did read up on one post that suggested making a system.img placing the OS inside and flashing it over using fastboot mode. Which brings me to the question. Is it possible to use command to install an OS on my Oneplus whilst in fastboot mode?
RazorCJ123 said:
Hello
First of all, let me explain the situation:
My phone is the Oneplus One, currently with no OS, the reason being - because i wanted to re-root my phone after the Oneplus updated (this update was a while ago) either way many problems occurred and i figured the easiest way to re-root my device is to simply wipe it, and try again on a clean slate.
I attempted to wipe my phone, but did it the complete wrong way. Instead of using the OS's wiping strategy, i may of used the recovery's one instead, doing so i clean swooped the OS right off my phone.
At the moment, the phone has no OS installed - nor is the phone rooted. The phone isn't capable of passing files over through usb debugging because the computer doesn't recognise it no more. (It did have usb debugging turn't on). Of course i need to reinstall an OS on the phone. The TWRP recovery is working fine. But i do not know how to do it. I looked up things such as mounting, didn't really understand the vague explanations given by the helpers of this forum (i am slow haha ). If someone is able to point me in the right direction in how to simply put an OS back into the phone some how i would be grateful.
I did read up on one post that suggested making a system.img placing the OS inside and flashing it over using fastboot mode. Which brings me to the question. Is it possible to use command to install an OS on my Oneplus whilst in fastboot mode?
Click to expand...
Click to collapse
See section 8 of my guide:
http://forum.xda-developers.com/showthread.php?t=2839471
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!
I'm fed up with people on this forum. I keep trying to engage people in a discussion, a conversation to explain some things to me and No one seems willing. It's like there are No Rooting gurus that can answer my simple questions. On a forum full of Android developers, I'm very disappointed, I thought i'd get tons of help. If you read this, Please consider staying to have a discussion/conversation with me.
Preface to The Discussion:
I have used both Android and Linux in the past, I know what Super User is, I use it in Zorin 12 Linux and own a rooted (kingroot) android tablet. I am trying to get information on rooting my Figo Atrium phone by trying to understand Rooting better in general. perhaps this discussion will make since to you and together you can help me find a way to root my phone - But I Must have a back and forth or I'll never understand this. - I know there are many exploits to root a phone used by tools like kingroot. I know these exploits are many and varied depending on your phone's CPU architecture, and software and not all root tools with work with my device. . I know the bootloader has to be unlocked and one must have USB Debugging enabled in Developer Options. I know some phone manufacturers make tools that help you root your phone (MTK Droid Tools) So far, none of these tools can root my phone.
Let's Start The Discussion Here:
I was able to not root but my Upgrade my phone from Lollipop to Marshmallow. I did this using SP Flash Tool and these instructions (which were badly translated and which as you can see by the comments in the video, I had to correct due to bad translation) See this video and comments by me to understand. https://www.youtube.com/watch?v=EEIJM2YjNzE - I used SP Flash Tool and a Rom Figo provided. After I figured out the botched instructions, I was able to upgrade my device with no problems.
Question 1: Isn't this essentially the same process that is used for Rooting? It proves my bootloader is unlocked and the phone does have the ability to flash a new Rom. <- Based on That, doesn't it seem to you that my phone would be in fact Rootable?
If you think so, tell me why, if you think Not, tell me why.
Question 2: If you think So, then: Someone suggested to me that using a tool like Magisk or SuperSU may be able to root my device. Does this seem likely to you based on what I've told you so far? No one in the SuperSU sub forum can answer this question.
If you think No, then we'll discuss this more. I'll wait for your replies. Thank you.
Rooting is, simply said, placing a 'su' binary in the system folder. SU means switch user, when you give that command you're instructing Android to give you root user privileage. OEM's don't want that to happen so they won't include it in their ROMs. Tools like supersu are made to copy that 'su' file to the system partition. There are a lot of ways to explain this, I'm just giving you something quick and easy to understand.
Now regarding your questions;
1) Flashing anything requires the bootloader to be unlocked on most phones. BUT MTK phones don't. (Except some HTC phones). SP Flash Tool can flash any partition without needing to unlock. It's dangerous security wise, but this means its also easier to root.
Infact all MTK phones are rootable. So don't worry about that.
2) How to root? The best way to root is with supersu. (You can also try magisk if you want to use Android Pay).
You need a custom recovery like TWRP first.
I found one here which is for your same CPU. https://www.needrom.com/download/twrp-recovery-13/
^I am just giving you a link to recovery which uses the same CPU so It may or may not work. PLEASE take a backup of your original recovery before doing anything.
Now download SuperSU zip file from here https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.82-201705271822.zip
Don't open it, just keep it in your sd card.
Flash the recovery using SP Flash Tool (check only the recovery box and select this file). Now unplug the phone and press Volume Up+Power Button to boot into recovery.
Then if it says swipe to allow modifications, swipe.
Now goto Install->Select the Supersu.zip file you downloaded->Swipe and reboot.
That's it! You're rooted!
Thanks.. again, you've answered things others couldn't. Much appreciated.
You say, " You need a custom recovery like TWRP first.
I found one here which is for your same CPU. https://www.needrom.com/download/twrp-recovery-13/
^I am just giving you a link to recovery which uses the same CPU so It may or may not work. PLEASE take a backup of your original recovery before doing anything."
Lets say Twrp doesn't work. What is this for, just to re-flash your original rom in case twrp fails at making a backup? ( I assume the tool makes your installed rom flashable in case the root doesn't work and you need to revert back to your original system) I have the SP Tool and the Rom for Marshmallow that works with my device from Figo. Can I use that if Twrp fails - or am I not understanding what twrp is used for? Just checking before I start this. Otherwise, I'll try to follow your instructions to the letter and see what happens.
Still Looking ?
STILL Looking? IF so, a few thoughts .... It is a nice phone for the price. The newer version eventually coming out looks even nicer, and for now, it is still my backup phone to my Figo Gravity. Discovered Figos when I got totally fed up with BLU phones.
ONE - If you have upgraded your Atrium to Marshmallow, as I did, none of the rooting methods that worked on Lollipop will work, so forget about them.
TWO - Down in Developer Settings you need to make sure OEM unlocking is allowed.
THREE - ASSUMING you have a TWRP build that will work, it is pretty simple. Take the ROM image that FIGO sent you and replace the "recovery.img" file with the TWRP (re-name it recovery.img and save the old one as recovery.old JUST IN CASE) file. It will be much larger than the factory ROM recovery image and that's fine. The scatter table, if you read hex addresses, provides for enough space to do this. Flash ONLY the recovery (TWRP) image, and be sure to DOWNLOAD ONLY with the SP FLASH tool. If uncertain, DO NOT PROCEED. It can be a real pain in the arse to re-do things if you accidentally format or upgrade things you didn't mean to. ASSUMING that worked, you can boot into TWRP by holding down the power / volume buttons (I assume you are familiar with this sequence).
FOUR - it is entirely possible that the next time you boot the thing normally, TWRP will be blown away. Happened to me a few times. There is some setting down in the boot image that causes this and I will have to dig up my notes to see exactly what the heck it was. It required taking apart the boot image - I used Carliv - fixing the one setting, and then re-packing and re-flashing it, BUT, you can ALWAYS keep replacing the TWRP image as needed. Inconvenient, but better than a sharp stick in the eye.
FIVE - when booted into TWRP, you should be able to flash SU, which will give you root, and it should STAY rooted after that unless and until you uninstall SU. FLASHIFY is STRONGLY recommended as a VERY useful app for rooted devices. TWRP, if you are unfamiliar with it, is SO MUCH MORE than just a recovery replacement. Handiest whole device backup there is. Has saved my bacon on several devices through numerous acts of personal stupidity. :crying:
SIX - IF ALL ELSE FAILS, you can ALWAYS revert to the factory image ROM. Just DOWNLOAD ONLY rather than Upgrade and DO NOT Format.
Hello, here's my problem: I accidentally put a schematic as a code on my phone that I immediately forgot. Now that I only have access to the lock screen, I can't put my phone in file transfer mode because I'd like to retrieve it before resetting my phone (which is, by the way, a Redmi Note 6 pro up-to-date, not rooted, no TWRP, and the bootloader is still locked). It's possible to use ADB to retrieve files, but I can't allow access to the computer from my phone either, so ADb is unusable when my phone is turned on. Nevertheless, it's obviously possible to use it in recovery mode, if you have the right drivers. I went to look for them, but during the installation, Windows tells me that a better driver, ADB devices, is already installed, and I can't install my driver. I obviously tried to find a way to ignore this warning, notably by asking during the manual driver installation to search the hard drive, but it tells me via this method that no driver is contained in the indicated directory (which is wrong, at least from what I see, the necessary files are all there).
So I search either :
- a driver that won't have this problem and that will allow adb to work in recovery mode;
- a way to force the installation of this driver;
- another way to use ADB in recovery mode;
- another way to recover my files while the phone is locked and I can't give it access to the computer.
Otherwise, any idea that can solve my problem is fine with me.
Thank you in advance and have a nice day!
https://c.mi.com/thread-2207444-1-0.html
For drivers.
And use OrangeFox Recovery
He can't install any custom rec. The phone not unlocked. I don't think you have a Chance to get your data. For future make the most files that you don't wanna Lose on a sd card not on intern storage.
Update: on little search on Google i found this Blog. https://www.androiddata-recovery.com/blog/how-to-retrieve-deleted-data-from-xiaomi-redmi-phones
On method 4 is maybe a reason for your matter.
ALcAtRas500 said:
He can't install any custom rec. The phone not unlocked. I don't think you have a Chance to get your data. For future make the most files that you don't wanna Lose on a sd card not on intern storage.
Update: on little search on Google i found this Blog.
On method 4 is maybe a reason for your matter.
Click to expand...
Click to collapse
Thanks, I will try this and and I'll up the topic and say whether or not I passed. And don't worry, I won't make that mistake twice, that'll teach me...
Kyrela said:
Thanks, I will try this and and I'll up the topic and say whether or not I passed. And don't worry, I won't make that mistake twice, that'll teach me...
Click to expand...
Click to collapse
The message wasn't sent... well, I was saying that the website was affiliated with a software, and was totally lying since the data recovery function is only compatible with samsung. So it looks like there's no solution for me...
Kyrela said:
The message wasn't sent... well, I was saying that the website was affiliated with a software, and was totally lying since the data recovery function is only compatible with samsung. So it looks like there's no solution for me...
Click to expand...
Click to collapse
Unfortunately for you you cannot recover your files. As your phone's bootloader is locked and even though some softwares claim to work even with formatted phones they don't because of encryption and this new type of formatting where the data gets destroyed. Even It happened to me once I had unlocked and rotted my phone by for some reason when I was going back to stock ROM my phone data got destroyed dueto my carelessness during encryption and that's the story. After that I tried different softwares to recover photos but non of them worked. Only thing is you can get your Device unlocked
Hello everyone,
So I've been off the fourms for quite some time, woun't go in detail about that. And as some might know I've broke my LCD touch screen. I got a replacement and replaced it with no isuess, works perfectly.
But...
I forgot the gesutre key I set on this phone because I haven't used it for months, and used my other A217F for the replacement.
I haven't been doing anything related to android so I forgot quite the stuff I use to know. My question is how can I bypass the disk encryption and pull the GESTURE.KEY from USERDATA. It OEM unlocked, rooted via magisk, and runs TWRP custom recovery. This is quite the older version of TWRP. I can flash it to the new one but the SYSTEM root is still under encryption. Idk if maybe I can dissasemble it from the SCATTAR, or pulling it via ADB (wich probably woun't work). I also want to help others who want to achive this so that's also one of the points for this thread. I'll list some of the info of this phone:
SM-A125F
BUF9 firmware SW_REV 1
Patched BOOT and VBMETA images via magisk
Custom recovery (TWRP)
Fixed IMEI and BASEBAND
Thanks,
Krypton
You can't bypass encryption.That's the point of it.To make sure the data is unreadable without the right key.If there was a way to read encrypted data without the key then it would be pointless
jesus201820 said:
You can't bypass encryption.That's the point of it.To make sure the data is unreadable without the right key.If there was a way to read encrypted data without the key then it would be pointless
Click to expand...
Click to collapse
Yea Ik the point is it can still be forceivly disabled via running unsinged firmware. It's OEM unlocked, I should have every ability possible.