This should work on all Qualcomm Snapdragon based Samsung galaxy SIII's, if it doesn't, PM me the model and I'll try and find a solution.
WHILE THIS IS VERY LIKELY TO WORK FOR ANY BOOTLOADER/MODEM/FIRMWARE BRICKED PHONE, THERE IS NO UNCONDITIONAL GUARANTEE THAT THIS WILL WORK FOR YOUR PARTICULAR SITUATION, THERE IS A POSSIBILITY THAT THERE ARE SOME BRICK STATES THAT THIS WILL NOT WORK FOR, but in my experience, almost all cases can be resolved by rewriting the sdcard with correct partitioning.
Disclaimer out of the way, let us begin.
Needed Materials and Files:
EDIT: if you have another phone or know someone else with the same phone have them run this and the output will be a debrick image you can use: busybox dd if=/dev/block/mmcblk0 of=/sdcard/backup.bin bs=1M count=200 if it does not work then change the last number (count=) to something larger and try it. If you create an image please upload it so I can put it into a repository I'm creating
16GB or 32GB class10 microSD card
A hard bricked Samsung galaxy S3 US Cellular
The debrick image for your device:
[[Here is the drive image for a folder containing all the debrick images that I currently have uploaded, more will be coming: https://drive.google.com/folderview?id=0B612qYHFMILfWUlMTTEwdUstcXM&usp=sharing ]]
If you have any images that I missed, please send me a link or, better yet, upload them to drive, make them publicly shared, and share them with me at [email protected], I will put them in this folder for all to use
US Cellular R530: ftp://sdbruington.us/d2usc/SCH-R530_ALIVE_MJA_200MB_16GB.bin
Sprint L710: http://www.mediafire.com/download/23...ph_l710.img.xz
AT&T I747: http://d-h.st/iEy
T-mobile T999: http://www.mediafire.com/download/gr...k_SGH-T999.img
---I did not upload these images, I have simply collected the links over time, please thank Cnexus for his help in finding these and
---helping me to originally unbrick my S3
Your computer
A card reader that will accept the card (another phone will not work as this is an image, and it needs to repartition the SD card)
Either a partition editor (I've heard that you can use dd or something on linux, but I haven't tried) or this: View attachment win32diskimager-v0.9-binary.zip
A wall charger (computer charging isn't as reliable)
Procedure:
1. Take the sdcard and insert it into your computer
2. Download the mentioned image and the software to put it onto the sdcard
3. Use your computer to pull the data already on the card onto your computer hard drive, as the sdcard will be wiped when the image is put onto it
4. use the software that you downloaded earlier to burn the image to the sdcard
5. Remove the battery from the SGS3
6. insert the sdcard into the S3
7. Put the battery into the S3
8. The S3 may boot automatically, or you may have to manually boot it by holding down the power button for 5< seconds
9. If the update that bricked your phone also messed up /system, then you'll have to coerce Odin mode to shove a stock firmware image to your phone, though I've had more than just SOME trouble with that in the past (in other words I haven't been able to get back to stock yet...), if you simply had a radio update or something go wrong, then proceed to the next step.
10. Do a victory dance with your phone in your pocket not the repair bench, or on second thought, make sure you don't drop it, don't create another problem.
11. After that, you can just use your device normally with the sdcard in it without worry of bricking it, though it will not be able to boot if you remove the sdcard;
the only known method of getting it to boot without the sdcard is reflashing stock firmware, which completely wipes the phone and resets everything back to complete stock. Also, Odin mode has, at least for me, objected when I've tried to flash the stock image back onto it, and even if Odin mode was sure of working, backing up ~16GB of data isn't a fast process, especially with the most reliable means being ADB. If you try to flash a stock image and it fails, your device will almost definitely come up with a version of dmode when you try to turn it on with the sdcard (still bricked otherwise) that says something about Kies update failure, the only way of correcting this that I've had success with is flashing an image that won't do much, such as the same recovery that you already had, over odin mode from that special dmode, as while that won't correct the actual brick, it will at least make you able to boot from the sdcard again. I will provide links to the stock images in a little while, once someone gets that far, as I will have to find all but the one from the US Cellular version.
I am currently looking for firmware images that will only flash the bootloader/modem, if anyone knows of an odin file that could do that, please let me know as soon as possible, in the meantime, I will try and create an update.zip that will flash the necessary files; as most bricks are likely cause by an update.zip that was meant for a different device, I am very confident that it can be fixed with another .zip file.---Stay tuned!
---Don't forget, that thanks button won't bite your finger off if you push it:fingers-crossed:
If any of the links are not fully functional, PM me to let me know, and if you have the link to another debrick image for another device, send me the link so I can include it here!
Please note: While there is a similar procedure for Xynos based S3's, they apparently require a physical modification that requires an amount of soldering, so it is most likely best for them to simply take them in for Jtagging and then just not brick them after that.
EDIT: here is the link to a full youtube tutorial that I made, just for those of you who like watching a video instead of getting lost in a written guide https://www.youtube.com/watch?v=-RTAbLBVfMI
EDIT AGAIN: I'm sorry about both of the mediafire links being down, I will try and find some more and upload them to my google drive, along with the others just to make sure they exist somewhere safe.I'm downloading the images now and uploading some that I already have, they will be available in this folder (https://drive.google.com/folderview?id=0B612qYHFMILfWUlMTTEwdUstcXM&usp=sharing) on google drive and will be available by email upon request
here is a sprint image that should work, sorry I haven't tested it http://www.mediafire.com/download/231uhy6l80jx74n/debrick_sph_l710.img.xz
for the t999 4.1: https://www.copy.com/s/xSAswQZbhQX8/t999_debrick.zip for the t999 4.3: https://www.copy.com/s/7ICfKXMC3ccr/T999_4.3_debrick.zip
I know this is becoming a mess of links but here is a link to an xda post that has t999 variant images http://forum.xda-developers.com/showthread.php?t=2439367
here is a sprint 4.4 debrick image: http://www.androidfilehost.com/?fid=23329332407591176
If you want to get your phone to operate without an sd card in there for every boot, stay tuned, I'll have a guide to return to stock soon, though a quick google search shouldn't be that hard if you're desperate
I will clean up this guide in a little bit but currently I have school and such to attend to so it may not be immediate
I know this is getting unwieldy but (big thanks to youdoofus) I have a way to completely debrick and fix it so it doesn't require even the sd to boot.
"Restoring stock bootloader
1) You were able to boot into the ROM
2) Plug your phone into a computer and use MTP mode
3) Move the debrick file onto your internal sdcard (/sdcard/debrick.bin)
4) Disconnect your phone
5) Open up a Terminal Emulator on your phone and input this code
Code:
su
dd if=/sdcard/debrick.bin of=/dev/block/mmcblk0
6) Reboot"
Of course this should be modified for the different versions and types of debrick image as some are img, some are bin, I think there might even be an ISO hanging around somewhere
EDIT: As of October 10th I'm working on a tool that will get an image directly from a stock rom/tar and put it on the SDcard. This is pretty complex so it will probably take a little while, but it should make it easier to get images if all that's required is a stock tar.
I've followed all these guides and haven't had any luck. I did use a CM 4.4 rom and some people are saying i need a debrick.img of a 4.4 to get it working again. i'm on an i-747. can you help?
derget1212 said:
I've followed all these guides and haven't had any luck. I did use a CM 4.4 rom and some people are saying i need a debrick.img of a 4.4 to get it working again. i'm on an i-747. can you help?
Click to expand...
Click to collapse
You don't need a debrick.img of a 4.4 to get it working, you need a debrick.img of the correct bootloader. If you bricked your phone by flashing an older bootloader after upgrading to the 4.3 bootloader, then you need a debrick.img with the 4.3 bootloader.
polobunny said:
You don't need a debrick.img of a 4.4 to get it working, you need a debrick.img of the correct bootloader. If you bricked your phone by flashing an older bootloader after upgrading to the 4.3 bootloader, then you need a debrick.img with the 4.3 bootloader.
Click to expand...
Click to collapse
how do i find out the correct bootloader? i was using this rom http://forum.xda-developers.com/showthread.php?t=2518998 for a couple months and randomly got hard bricked yesterday. any help is greatly appreciated.
Thanks for sharing this
derget1212 said:
how do i find out the correct bootloader? i was using this rom http://forum.xda-developers.com/showthread.php?t=2518998 for a couple months and randomly got hard bricked yesterday. any help is greatly appreciated.
Click to expand...
Click to collapse
Explain your situation. Randomly bricked is very vague. Did you flash anything? Do you remember doing anything? It's important. Phones don't go and "randomly brick" unless of a HW problem, and to either confirm or eliminate that possibility we need more details.
polobunny said:
Explain your situation. Randomly bricked is very vague. Did you flash anything? Do you remember doing anything? It's important. Phones don't go and "randomly brick" unless of a HW problem, and to either confirm or eliminate that possibility we need more details.
Click to expand...
Click to collapse
Like i said, it was totally random. My phone froze and rebooted yesterday. It got to the Samsung logo so i thought everything was okay. I fell asleep and woke up to a bricked phone. After all of my attempts, I got one debrick.img to show something on my screen and it shows "BOOT RECOVERY MODE". Odin sees my phone and tries to fix the PIT and the Bootloader but it always fails. From what i gather, it seems to be a hardware issue.
derget1212 said:
Like i said, it was totally random. My phone froze and rebooted yesterday. It got to the Samsung logo so i thought everything was okay. I fell asleep and woke up to a bricked phone. After all of my attempts, I got one debrick.img to show something on my screen and it shows "BOOT RECOVERY MODE". Odin sees my phone and tries to fix the PIT and the Bootloader but it always fails. From what i gather, it seems to be a hardware issue.
Click to expand...
Click to collapse
Whoa whoa there, if your phone still boots in either recovery or download mode, then you don't need to use a debrick.img.
If you have a custom recovery, you can flash your custom rom. If you don't, you can flash a stock ROM using ODIN in download mode.
polobunny said:
Whoa whoa there, if your phone still boots in either recovery or download mode, then you don't need to use a debrick.img.
If you have a custom recovery, you can flash your custom rom. If you don't, you can flash a stock ROM using ODIN in download mode.
Click to expand...
Click to collapse
It is hard bricked. Without the sd with a debrick.img installed, I get no response at all. And I've tried all the i747 debrick.img files I could find here with no success.
I can get to boot recovery mode with one .img I could find but boot recovery os different than recovery mode. It's essentially useless and Odin doesn't like it.
derget1212 said:
Like i said, it was totally random. My phone froze and rebooted yesterday. It got to the Samsung logo so i thought everything was okay. I fell asleep and woke up to a bricked phone. After all of my attempts, I got one debrick.img to show something on my screen and it shows "BOOT RECOVERY MODE". Odin sees my phone and tries to fix the PIT and the Bootloader but it always fails. From what i gather, it seems to be a hardware issue.
Click to expand...
Click to collapse
It really sounds a lot like the BRICKBUG to me, anyone know how to tell if a chip is insane without it working? And did you have the 4.3 bootloader? If you got that you should have been safe, but if you didn't then the kernel may have burned out the chips from the "bug" (it really doesn't seem too much like a "bug", more like an issue worthy of recall)
Sorry I don't know exactly what's wrong off the top of my head
derget1212 said:
It is hard bricked. Without the sd with a debrick.img installed, I get no response at all. And I've tried all the i747 debrick.img files I could find here with no success.
I can get to boot recovery mode with one .img I could find but boot recovery os different than recovery mode. It's essentially useless and Odin doesn't like it.
Click to expand...
Click to collapse
If you get ANY response at all, then the debrick image is doing its job; what you need is a stock image, I'll try to find a link for you to use. Try using Kies or something, alternatively, as if you have the serial number you can apparently flash it quite cleanly, all data on the phone will be lost though, as it effectively wipes the eMMC.
polobunny said:
You don't need a debrick.img of a 4.4 to get it working, you need a debrick.img of the correct bootloader. If you bricked your phone by flashing an older bootloader after upgrading to the 4.3 bootloader, then you need a debrick.img with the 4.3 bootloader.
Click to expand...
Click to collapse
Exactly
This image gets you in the clear if the ONLY thing screwed up is the boot partition, meaning modem/firmware/bootloader, it does NOT get you fixed if you got your rom F***ed up, and do not expect it to, this will get you into dmode so you can use odin or something like fastboot to flash a /system image or a FULL stock rom if you want to get your bootloader fixed without the SD card being in all the time.
dreamwave said:
If you get ANY response at all, then the debrick image is doing its job; what you need is a stock image, I'll try to find a link for you to use. Try using Kies or something, alternatively, as if you have the serial number you can apparently flash it quite cleanly, all data on the phone will be lost though, as it effectively wipes the eMMC.
Click to expand...
Click to collapse
if anyone can find the correct debrick.img i need to use, i would greatly appreciate it. I have tried Kies and Odin without success. They can see the phone but seem not to be able to access it. I can't flash anything via odin or get to the CWM recovery or download mode. this is a really weird screen i haven't seen before.
derget1212 said:
if anyone can find the correct debrick.img i need to use, i would greatly appreciate it. I have tried Kies and Odin without success. They can see the phone but seem not to be able to access it. I can't flash anything via odin or get to the CWM recovery or download mode. this is a really weird screen i haven't seen before.
Click to expand...
Click to collapse
Is there any way at all to get into dmode? What is windows recognizing it as?
Thanks for sharing.
EvangelineX said:
Thanks for sharing.
Click to expand...
Click to collapse
no problem, I hope it helped!
derget1212 said:
I've followed all these guides and haven't had any luck. I did use a CM 4.4 rom and some people are saying i need a debrick.img of a 4.4 to get it working again. i'm on an i-747. can you help?
Click to expand...
Click to collapse
If you bricked the /system partition AND the boot partition you will need a stock rom as well, just use Odin or something if possible after using a 4.3 image, a 4.4 image is more or less the same as a 4.3 as far as I know, I mean I bricked mine after using cm11 by flashing the wrong rom, it's just that the rom you tried tried to flash a 4.1 bootloader, and thus tripped the eFUSE or something in the Knox bootloader, what you need is a 4.3 unbrick image, as 4.4 didn't really change the modems/bootloader from 4.3, and the unbrick image isn't really that much more than a collection of pieces from the boot partition that are used as an autoboot by the phone when the eMMC fails to load properly.
This is pretty neat..
does it always work?
It's nice to have such a recover method whenever something like this happens to you.
halfdead1993 said:
This is pretty neat..
does it always work?
It's nice to have such a recover method whenever something like this happens to you.
Click to expand...
Click to collapse
I believe it will work on basically anything, as in I haven't seen a case that can't be cured at least somewhat by this, I think it works like an alternative boot, as if the bootloader on the eMMC is corrupted, it seems to remove the boot flag, thus making it so that the phone does not detect a bootable partition, the unbrick image has a partition layout mirroring the one that is supposed to be on the phone, so it is used as the boot partition but then redirects control back to whatever is on the eMMC after the bootloader, think of it as a liveCD on windows, just one that hands control back to the system after it has gotten past booting the BIOS.
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.
Hello Forum,
I am in desperate need of rooting my old Galaxy Express Prime 2 (SM-J327a), because I accidentally deleted all of my images. I cannot find a .tar file to recover the device. I checked TWRP's site, and they don't have a file to support this device yet. Does anyone know another way to root this device, or where I can find a .tar file to use with Odin? I have tried virtually all root apps and programs.
Thank you,
Mosaic Owl
I would like to second this request (though I am not near as desperate). Has anyone tried using the Samsung one click root method for this phone?
Link to modded Odin to skip SHA256
Hydran said:
I would like to second this request (though I am not near as desperate). Has anyone tried using the Samsung one click root method for this phone?
Click to expand...
Click to collapse
I tried loading up One Click Root on my laptop and it said it couldn't find its servers. I also tried flashing twrp for a similar Boost phone, (SM-J327p) knowing there was a risk of bricking it. My J327a was free and I plan to stick with my Moto, so I could afford to risk it, plus I've always been able to un brick anything from graphics cards to phones and game systems.
Anyway, Odin 3.12 gets a few steps into the twrp install, but before it actually begins to install, an error pops up that says "SHA256 is invalid". I searched for a couple of hours, and all I can come up with is that AT&T put an extra check in there to see where the files were coming from, and attempting to install custom recovery will cause this error. A modified Odin was released to skip this check on an older phone, but I could not find a working link to it.
That's what I came here for: a link to the modified Odin that will allow me to install TWRP without that check. If it's posted, DO NOT try flashing the wrong twrp recovery if you can't afford having it bricked for a while like I can.
I guess you would need to start with an eng bootloader that will let your phone boot then work on a tethered root... I'm still looking for binary 2 with rev 2 combination file without luck, all I need is to extract the boot and see if I can reset lock pattern. I tried google account but it does not have the option to lock-relock screen anymore. It's my nephew's phone and my daughter messed it up. I can login the google account and make it ring and locate it but can't disable the pattern. He has no backup of this phone...
Have any one make it done?
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
Hi, I'm having a lot of troubles. My old Samsung S6 was accidentally factory reset and I did not have photo backup through google enabled. My mother died last April and this phone has many photos of her that I have not backed up anywhere else. I've been trying for days to figure out what to do, but I can't make heads or tails of a lot of the information. Some places say the phone can be rooted, some say not, and there are a lot of dubious websites offering the tools needed to root them. I don't know what to do, my phone model is SM-G920V, hardware version is G920V.07, and the build number is MMB29K.G920VVRU4CPF4.
I saw one tool, CF-Autoroot that generated a file set for me to root the phone, but it also said that the bootloader being locked could result in the phone being flashed. Can anyone please help me understand what my options are? If it's complicated, I will learn how to do it, I just need a definite direction to move in. Otherwise, I think I will keep the phone turned off and hope that someday the data can be recovered. I'm very distraught, I used this phone for a long time and a great period of memories will be lost if I cannot restore it. Photorec will not recognize the phone in either Windows or Linux, I assume because I do not have root.
EDIT: Android Version 6.0.1, security patch level June 1st, 2016, Kernel Version 3.10.61
EDIT 2: I've seen some threads talking about downgrading from 6.0.1 to 5.1.1 and then getting root with Odin and TWRP recovery. What's the likelihood any of the photos would be recoverable after all that using Photorec? I'm just looking for any way to get any of the photos. I definitely need root to get Photorec to recognize the phone at least, right? Or is there another program that would work better maybe? I've had good luck with a scrambled flash drive and Photorec in the past so I feel like that's my best option.
I think it only needed adb access if it OEM Unlocked
I have restored using only ADB from Linux
Edit: I don't know about factory reset would have permanently erase the files, I don't know..
But if you erase phone from Odin it is permanent. That is what I know