Related
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 have jailbroken many an iphone and ipod, and I have recently bought the S6. I am keen to root but it seems far more potentially troublsome, and far less straightforward, or maybe its just because I am learning for the first time.
I bought this in New Zealand from Spark. I assume it is locked?
Is the bootloader locked?
I couldnt find the matching build on Chainfire, Can this particular model be rooted?
Is there any guide to rooting? It seems all the information is spread out all over the place and no definitive guide and FAQ.
I can't even find the original stock rom.
Is rooting not similar to jailbreaking in the way it is done?
My specs:
Model: SM-G920I
Android: 5.0.2
Build: LRX22G.G920IDVU1AOD1
Thank you in advance.
AAANNNDDDYYY said:
I have jailbroken many an iphone and ipod, and I have recently bought the S6. I am keen to root but it seems far more potentially troublsome, and far less straightforward, or maybe its just because I am learning for the first time.
I bought this in New Zealand from Spark. I assume it is locked?
Is the bootloader locked?
I couldnt find the matching build on Chainfire, Can this particular model be rooted?
Is there any guide to rooting? It seems all the information is spread out all over the place and no definitive guide and FAQ.
I can't even find the original stock rom.
Is rooting not similar to jailbreaking in the way it is done?
My specs:
Model: SM-G920I
Android: 5.0.2
Build: LRX22G.G920IDVU1AOD1
Thank you in advance.
Click to expand...
Click to collapse
I have the SM-G920I and it's rooted.
Rooting the G920I is apparently not as straightforward as others but still possible.
I had to flash TWRP via Odin, then flash the [BETA][2015.04.28] SuperSU v2.49 package via recovery.
Details when I get back from work, or some kind soul decides to help.
There is a stock image thread and a few stock roms floating around. Request / search lower down in that thread
Thanks, is it better to reset the s6 before rooting? For a clean root?
And about all the warnings about 'you do this at your own risk blah blah'. If you do everything properly how could you actually hard brick the device? If you do it properly the worst that should happen is a soft brick, in which case you just restore the phone and try again right?
AAANNNDDDYYY said:
Thanks, is it better to reset the s6 before rooting? For a clean root?
And about all the warnings about 'you do this at your own risk blah blah'. If you do everything properly how could you actually hard brick the device? If you do it properly the worst that should happen is a soft brick, in which case you just restore the phone and try again right?
Click to expand...
Click to collapse
Here is my experience, a fellow kiwi on Spark (with a 2D branded phone). I too have the 920I running on A0D1 via OTA.
It is unlikely Spark firmwares have locked bootloaders.
So long as you can get to download mode (holding volume down, home and the power button for up to 10 seconds), you can bring your phone back to life if something goes wrong . You will want a copy of Spark's firmware handy before you start, you can get it from here . Just in case.
Use the USB cable that come with your phone and make sure you have the drivers installed.
Any ways, first I flashed TWRP via Odin (through download mode Andy), flash was successful, however booting into recovery hung my phone. Managed to get back to download mode from there and flashed CF-Root for 920I. Boot loop.
Back to download mode and flashed CF-Root for 920F. Success, rooted and booted. Andy, if all you are looking for is root, avoiding the TWRP flash may work and going straight to CF-Root. Others have had issues with this, I'm not sure. I'd try the 920I first and if no good try the 920F. Again, as long as you can get to download mode, you can flash Sparks firmware through Odin to restore it to stock. Good luck and remember, attempting any of this WILL trip KNOX. If your using this as a company phone, you will run into issues. Can't imagine we will see Samsung pay any time soon in NZ.
For those interested in TWRP, after the root was obtained, my recovery was still busted. I flashed the TWRP image via Flashify and now I have also have TWRP. Good times.
Thanks mate, it all seems quite confusing, makes me want to go back to Iphone hahaha. I am not a dev, I just like the freedom to be able to do whatever I damn well please on my phone that I paid for.
This tutorial the way to go?
youtube.com/watch?v=BW5P8zqkFpY
AAANNNDDDYYY said:
Thanks mate, it all seems quite confusing, makes me want to go back to Iphone hahaha. I am not a dev, I just like the freedom to be able to do whatever I damn well please on my phone that I paid for.
This tutorial the way to go?
youtube.com/watch?v=BW5P8zqkFpY
Click to expand...
Click to collapse
What the chap did in that video was exactly what my original plan was to root and install TWRP. Where I got stuck is the TWRP recovery hung so I couldn't flash SuperSU. Good run down of the basics of flashing with Odin though.
What I did after the recovery got stuck was return to download mode and flash CF-Root again through Odin (same process as in the video). The one for the 920I didn't actually work (boot loop), the 920F CF-Root worked fine though. Probably has something to do with these CF-Roots having been build on a older firmware as you noted in your OP. Then, once you have root, you can flash a custom recovery (such as TWRP) through Flashify (available on Play Store).
It certainly can be confusing with all the trial and error reported in these forums, this is largely because the devices are new. The Devs' will iron out the bugs in due course making the process much simpler. You could wait a few weeks and check back, or grab yourself a stock Spark firmware and have a crack. Flashing this trough Odin will return you to stock provided you can get your phone to download mode. No responsibility from my end.
Another thing, you will lose OTA updates. You will find newer firmwares here as they get released, to update its as simple as flashing them through Odin.
Yes the G920I listed on Chainfires site is for the AOC6 build, but I am on the AOD1 build.
Another thing, should i factory reset before rooting?
AAANNNDDDYYY said:
Yes the G920I listed on Chainfires site is for the AOC6 build, but I am on the AOD1 build.
Another thing, should i factory reset before rooting?
Click to expand...
Click to collapse
Nah, don't bother. The process will retain all your settings and data too.
So just confirm that i can root my g920I with build AOD1 with this meathod?
---------- Post added at 05:45 PM ---------- Previous post was at 05:33 PM ----------
d0ce said:
What the chap did in that video was exactly what my original plan was to root and install TWRP. Where I got stuck is the TWRP recovery hung so I couldn't flash SuperSU. Good run down of the basics of flashing with Odin though.
What I did after the recovery got stuck was return to download mode and flash CF-Root again through Odin (same process as in the video). The one for the 920I didn't actually work (boot loop), the 920F CF-Root worked fine though. Probably has something to do with these CF-Roots having been build on a older firmware as you noted in your OP. Then, once you have root, you can flash a custom recovery (such as TWRP) through Flashify (available on Play Store).
It certainly can be confusing with all the trial and error reported in these forums, this is largely because the devices are new. The Devs' will iron out the bugs in due course making the process much simpler. You could wait a few weeks and check back, or grab yourself a stock Spark firmware and have a crack. Flashing this trough Odin will return you to stock provided you can get your phone to download mode. No responsibility from my end.
Another thing, you will lose OTA updates. You will find newer firmwares here as they get released, to update its as simple as flashing them through Odin.
Click to expand...
Click to collapse
So just confirm that i can root my g920I with build AOD1 with this meathod?
d0ce said:
What the chap did in that video was exactly what my original plan was to root and install TWRP. Where I got stuck is the TWRP recovery hung so I couldn't flash SuperSU. Good run down of the basics of flashing with Odin though.
What I did after the recovery got stuck was return to download mode and flash CF-Root again through Odin (same process as in the video). The one for the 920I didn't actually work (boot loop), the 920F CF-Root worked fine though. Probably has something to do with these CF-Roots having been build on a older firmware as you noted in your OP. Then, once you have root, you can flash a custom recovery (such as TWRP) through Flashify (available on Play Store).
It certainly can be confusing with all the trial and error reported in these forums, this is largely because the devices are new. The Devs' will iron out the bugs in due course making the process much simpler. You could wait a few weeks and check back, or grab yourself a stock Spark firmware and have a crack. Flashing this trough Odin will return you to stock provided you can get your phone to download mode. No responsibility from my end.
Another thing, you will lose OTA updates. You will find newer firmwares here as they get released, to update its as simple as flashing them through Odin.
Click to expand...
Click to collapse
So were you able to install TWRP?
CF Root works for me with 920I version, but flashing TWRP forces it not to boot past the Samsung Logo.
Likewise with flashing a custom kernel also forces it not to boot past the Samsung Logo
Im on the C4 Australia build.. thinking about trying to flash a later 920I build to see if it'll help
s3ct0r said:
So were you able to install TWRP?
CF Root works for me with 920I version, but flashing TWRP forces it not to boot past the Samsung Logo.
Likewise with flashing a custom kernel also forces it not to boot past the Samsung Logo
Im on the C4 Australia build.. thinking about trying to flash a later 920I build to see if it'll help
Click to expand...
Click to collapse
Did someone figure this out? I have the Sm-920i and I get stuck at the Samsung splash screen after flashing twrp! So I have to Odin the cf-auto-root... I've tried flashify also... It won't work... Stuck @ Galaxy S6 screen what gives is it the SM-920I OR ME? I have had many Galaxy phones in the past but this one is pissing me off
Kjc99 said:
Did someone figure this out? I have the Sm-920i and I get stuck at the Samsung splash screen after flashing twrp! So I have to Odin the cf-auto-root... I've tried flashify also... It won't work... Stuck @ Galaxy S6 screen what gives is it the SM-920I OR ME? I have had many Galaxy phones in the past but this one is pissing me off
Click to expand...
Click to collapse
Yeah flash the New Zealand 1D firmware and TWRP will work perfectly. But note that to get root, you will have to use cf-auto-root for the 920G Model
Best of luck
s3ct0r said:
Yeah flash the New Zealand 1D firmware and TWRP will work perfectly. But note that to get root, you will have to use cf-auto-root for the 920G Model
Best of luck
Click to expand...
Click to collapse
How come it has to be the New Zealand? I'm trying to backup my carriers crappy baked rom just in case I need to return... Is there anyway to back it up without a custom recovery but rooted? Because if I flash the new Zealand before making a backup and have to return they will see I have messed with the phone because they put a boot animation
Kjc99 said:
How come it has to be the New Zealand? I'm trying to backup my carriers crappy baked rom just in case I need to return... Is there anyway to back it up without a custom recovery but rooted? Because if I flash the new Zealand before making a backup and have to return they will see I have messed with the phone because they put a boot animation
Click to expand...
Click to collapse
Doesn't have to be the New Zealand one, I just used it since I'm in Australia. Any 920I firmware should work just make sure it's at least 1D. I only tried those firmwares, and always had success
My carrier is GCI wireless in Alaska, USA... No way to download there firmware...also is twrp it? No more cwm or philz recovery?
Sorry forgot to add current firmware pic
s3ct0r said:
Doesn't have to be the New Zealand one, I just used it since I'm in Australia. Any 920I firmware should work just make sure it's at least 1D. I only tried those firmwares, and always had success
Click to expand...
Click to collapse
Cool thanks for the info!
Update thank you @s3ct0r...worked on the 1st try.... Now I'm working on the deep sleep issue...
Kjc99 said:
Update thank you @s3ct0r...worked on the 1st try.... Now I'm working on the deep sleep issue...
Click to expand...
Click to collapse
Flash the ktoonsez Kernel, or the flashable zip from the Cf-AutoRoot topic
s3ct0r said:
Flash the ktoonsez Kernel, or the flashable zip from the Cf-AutoRoot topic
Click to expand...
Click to collapse
Is ktoonsez a stable kernel, I remember using it on my S4 but skipped it last year on my S5 because it had to many tweaks... Can I use it with a stock rom? Alliance?
this is the second time i've soft bricked my phone in the past 6 days and if this is fixable i will probably consider researching for weeks at a time before trying anything new..
anyway, the first time i soft bricked my phone last week, my s6 was rooted (via chainfire, G920IDVU1AOC6) but i decided to unroot so i could update software. after unrooting with SuperSU, i attempted to update by using smart switch and then something went wrong with that process (my firmware was at G920IDVU1AOC4) which i then fixed by flashing G920IDVU1BOE3 (latest stock firmware) WITHOUT the hidden.img
backstory out of the way, i wanted to flash TWRP so i could install xposed installer. i used the same chainfire firmware that worked the week prior (above) and so now my phone is soft bricked
things i've tried:
- flashing recovery of AOC4 - i can get back into recovery mode with the older firmware
- flashing AOC4 stock firmware with AND without the hidden.img
- flashing the BOE3 stock firmware with AND without the hidden.img
i'm still able to get into download mode and stock recovery and i've already tried wiping cache and factory reset but nothing works.
i continue to get FAILED on odin
if anyone is able to bring my phone back from purgatory for the second time it would be greatly appreciated.
thanks in advanced, mojo.
Ok, I soft bricked my s6 too :/ its fine now so dont worry, actually, I read somewhere the problem of failing is in Odin, and you need to flash the stock recovery and then recocery.img you extracted from it in a way odin can read, im from my phone now so I will try to search it out, hope I will find. Dont worry dude your s6 is alive.
Ok i found it, http://forum.xda-developers.com/galaxy-s6/help/solved-stuck-download-mode-failed-odin-t3104736 , I burned stock and then the file he supplied,worked like a charm.
JusTeN_ said:
Ok, I soft bricked my s6 too :/ its fine now so dont worry, actually, I read somewhere the problem of failing is in Odin, and you need to flash the stock recovery and then recocery.img you extracted from it in a way odin can read, im from my phone now so I will try to search it out, hope I will find. Dont worry dude your s6 is alive.
Ok i found it, http://forum.xda-developers.com/galaxy-s6/help/solved-stuck-download-mode-failed-odin-t3104736 , I burned stock and then the file he supplied,worked like a charm.
Click to expand...
Click to collapse
thank you so much for your reply and reassurance! i'll try this out right now and update on the results
UPDATE: i tried flashing stock and then the my-recovery.img.tar and i could get into recovery but i was stuck in boot loop.
is there something i'm doing that's incorrect?
Saafir said:
Did you remove the cable, boot download mode, then reconnect and let the driver install screen complete on your PC? Sorry if its a bit redundant but I had made this mistake before.
Click to expand...
Click to collapse
yes i have reconnected each time but thanks anyway!
JusTeN_ said:
Ok, I soft bricked my s6 too :/ its fine now so dont worry, actually, I read somewhere the problem of failing is in Odin, and you need to flash the stock recovery and then recocery.img you extracted from it in a way odin can read, im from my phone now so I will try to search it out, hope I will find. Dont worry dude your s6 is alive.
Ok i found it, http://forum.xda-developers.com/galaxy-s6/help/solved-stuck-download-mode-failed-odin-t3104736 , I burned stock and then the file he supplied,worked like a charm.
Click to expand...
Click to collapse
I FIXED IT.
i'm not exactly sure of the steps i took, as i had to keep waiting for my Unified Android Toolkit to create the tars but essentially what i did was i flashed;
- stock BOE3 WITHOUT hidden.img
- TWRP recovery (was able to boot into twrp and when i looked through some settings (reboot) it said i had no OS installed for some reason
- from this info i tried flashing the AOC4 older firmware WITHOUT hidden.img then it worked.
do you think it is worth attempting the smart switch thing mentioned in that link you posted?
i wouldn't want to run into this problem again..
my lord.. so SOMEHOW i managed to get myself into this for THE THIRD TIME..
once i got it fixed, just a few hours ago, everything was fine and i was then able to flash CF root again.
but once i tried to install TWRP (it worked before i fixed the second time) odin FAILED again and i'm back to square one.
i'm unsure how to properly fix it and the steps i took before aren't working now and i can't even flash any recoveries (whether its AOC4, BOE3 or TWRP)
can anyone suggest anything else please?? i'm in panic mode again lol
this is definitely the last time i try to do any type of configuration with this device.
Do you have recovery now? Maybe burn some custom rom? ..
JusTeN_ said:
Do you have recovery now? Maybe burn some custom rom? ..
Click to expand...
Click to collapse
now i can't flash the twrp .. it won't work. this suck so much!
UPDATE (final update, hopefully ): fixed it AGAIN.
after going through this hellish nightmare for the 3rd time and reading countless threads, i've discovered that the FAILs on odin may be occurring due to the corruption of the firmware file.
so if anyone goes through my problem, CREATE A COPY of the desired firmware before flashing with odin!
thanks justen for your patience and attempts to help me!
Here is what I did so far to get here.
First I followed the guide to root my phone, and to be honest, all was perfect. I had to restore stock rom cause my first few tries failed. But seems I flashed a rom for a different provider. It worked anyway, but I don't have my sim card in that phone, it's temporarily in another device.
I had a little issue in settings, where battery was coming up two times in the list. That bugged me, I wanted to restore the rom and see if a full restore would take care of this issue, but somehow, after I installed twrp and rooted my phone, I can no longer flash anything stock with odin, it fails.
If I try to flash the AP tar.md5 file, it fails when it gets to system. And then after rebooting, I see this message:
"An error has occurred while updating the device software. Use the emergency recovery function in the Smart Switch PC Software"
I tried installing smart switch and kies, and both software doesn't detect my device in download mode or twrp (obviously)...
So to get rid of the emergency message, I flashed twrp again with odin, and been successful. If I tried to flash the AP image again, or CSC, it fails. And then I get the message back.
After flashing twrp, I'm stuck in a boot loop. Would need to restore system I think, but cannot seem to be able to do it with Odin.
Any possible way to recover my device?
Update: Turns out I must have made a mistake with the firmware I thought I had flashed, versus the one I was trying to flash and was failing. I downloaded the latest october firmware and it's currently flashing in odin!
This not be posted in development !
mchlbenner said:
This not be posted in development !
Click to expand...
Click to collapse
Sorry about that, I thought it was related to the topic. Obviously, you saw that I do not have a thousand posts around here, a wise thing to do would have been to suggest me where should I have posted this, and how can I move my thread around? Do I wait for a mod to move it himself?
pleclair said:
Here is what I did so far to get here.
First I followed the guide to root my phone, and to be honest, all was perfect. I had to restore stock rom cause my first few tries failed. But seems I flashed a rom for a different provider. It worked anyway, but I don't have my sim card in that phone, it's temporarily in another device.
I had a little issue in settings, where battery was coming up two times in the list. That bugged me, I wanted to restore the rom and see if a full restore would take care of this issue, but somehow, after I installed twrp and rooted my phone, I can no longer flash anything stock with odin, it fails.
If I try to flash the AP tar.md5 file, it fails when it gets to system. And then after rebooting, I see this message:
"An error has occurred while updating the device software. Use the emergency recovery function in the Smart Switch PC Software"
I tried installing smart switch and kies, and both software doesn't detect my device in download mode or twrp (obviously)...
So to get rid of the emergency message, I flashed twrp again with odin, and been successful. If I tried to flash the AP image again, or CSC, it fails. And then I get the message back.
After flashing twrp, I'm stuck in a boot loop. Would need to restore system I think, but cannot seem to be able to do it with Odin.
Any possible way to recover my device?
Click to expand...
Click to collapse
You forgot to flash all of them
BL, AP, CP, CSC
pleclair said:
Sorry about that, I thought it was related to the topic. Obviously, you saw that I do not have a thousand posts around here, a wise thing to do would have been to suggest me where should I have posted this, and how can I move my thread around? Do I wait for a mod to move it himself?
Click to expand...
Click to collapse
Just because you have a lot of post you don't post question in development section.
587.saboor said:
You forgot to flash all of them
BL, AP, CP, CSC
Click to expand...
Click to collapse
I did flashed all of them. But it always fails. No matter if I select only BL, AP, CP, CSC... or all of them. Almost seems like twrp is preventing write or something else does.
It fails after a few seconds in the process. Is there any kind of log generated by odin? If so, where can I find it? I don't see much information beside that it fails.
OEM unlock checked in dev options?
USB debuging checked? these were always the go to mischecks...
back when I had the galaxy a5 2017 520W canada unit I flashed a european rom to see if FM radio was going to work. it Worked, but I had the simular issue with battery showing up twice AND I ended up tripping knox while doing it. phone seemed to work fine other then that issue and the radio worked as well.
Flashed it back to 520W stock... later sold the phone... no issues. perhaps it was different with nougat
supertac said:
OEM unlock checked in dev options?
USB debuging checked? these were always the go to mischecks...
back when I had the galaxy a5 2017 520W canada unit I flashed a european rom to see if FM radio was going to work. it Worked, but I had the simular issue with battery showing up twice AND I ended up tripping knox while doing it. phone seemed to work fine other then that issue and the radio worked as well.
Flashed it back to 520W stock... later sold the phone... no issues. perhaps it was different with nougat
Click to expand...
Click to collapse
Yeah, I have those two checked. For some reasons, I was tired that night, and was actually trying to flash 7.1.1 firmware, while having already upgraded to 8.0. So I believe this operation wasn't getting thru because of that. I was tired, and picked the wrong folder, and flashed 7.1.1. Well, I was trying to flash, but it kept failing, but had a tiny bit done, enough to screw this up like this.
When I picked the right folder, 8.0, then it worked.
As for tripping knox, you probably tripped it while flashing twrp. I believe it trips it, haven't heard of a way to do it.
pleclair said:
Yeah, I have those two checked. For some reasons, I was tired that night, and was actually trying to flash 7.1.1 firmware, while having already upgraded to 8.0. So I believe this operation wasn't getting thru because of that. I was tired, and picked the wrong folder, and flashed 7.1.1. Well, I was trying to flash, but it kept failing, but had a tiny bit done, enough to screw this up like this.
When I picked the right folder, 8.0, then it worked.
As for tripping knox, you probably tripped it while flashing twrp. I believe it trips it, haven't heard of a way to do it.
Click to expand...
Click to collapse
nope. NEVER flashed twrp once on the A5- the european firmware tripped it on the 520W
desperately trying to un brick my note 5. I've been trying for weeks now to recover my phone after a rooting mishap had caused loss of imei and baseband. in the process of attempting to repair that issue I have managed to completely soft brick the damn thing. I have been to the deepest corners of google in search of this specific 4 file repair download and can not find anything that is free. I've even signed up for accounts on gsm flash and the like only to be disappointed that signing up wasn't enough to get the files I need... if anyone has a link or the files themselves I would be very thankful for there help. to be clear I can not flash standard stock rom through Odin. the process completes and the phone boots but than erases at 32 percent and will only boot to recovery with dm verity error or download mode. I've tried a few different official stock roms. I've tried flashing the one file home.tar as well as un packing and flashing boot, system, modem, cache neither of which have worked. I can't find a hidden image file to remove before flashing so unless I'm missing something im out of ideas.. the repair. firmware seems to be my last hope... also to hell out anyone trying to assist. I flashed a. efs file when trying to restore imei and that in turn re enabled frp lock.. so I believe both frp lock and oem lock are enabled. so any combination file or modified at all is out of the question... I believe it's repair or nothing. there are a few free 4 file repair downloads out there but they aren't the same number im not sure if there are any compatible enough that I could flash one of them and they work? so if any one knows of other models compatible. with the SM-N920TUVU4EQJ3 let me know so I can try to get this mess sorted out. I apologize if this has been asked somewhere els or if I'm in the wrong forum. but this seemed the most suited for my case. thank you to anyone who may be able to help
anybody?
is anyone able to help me out?
thatspideyguy said:
desperately trying to un brick my note 5. I've been trying for weeks now to recover my phone after a rooting mishap had caused loss of imei and baseband. in the process of attempting to repair that issue I have managed to completely soft brick the damn thing. I have been to the deepest corners of google in search of this specific 4 file repair download and can not find anything that is free. I've even signed up for accounts on gsm flash and the like only to be disappointed that signing up wasn't enough to get the files I need... if anyone has a link or the files themselves I would be very thankful for there help. to be clear I can not flash standard stock rom through Odin. the process completes and the phone boots but than erases at 32 percent and will only boot to recovery with dm verity error or download mode. I've tried a few different official stock roms. I've tried flashing the one file home.tar as well as un packing and flashing boot, system, modem, cache neither of which have worked. I can't find a hidden image file to remove before flashing so unless I'm missing something im out of ideas.. the repair. firmware seems to be my last hope... also to hell out anyone trying to assist. I flashed a. efs file when trying to restore imei and that in turn re enabled frp lock.. so I believe both frp lock and oem lock are enabled. so any combination file or modified at all is out of the question... I believe it's repair or nothing. there are a few free 4 file repair downloads out there but they aren't the same number im not sure if there are any compatible enough that I could flash one of them and they work? so if any one knows of other models compatible. with the SM-N920TUVU4EQJ3 let me know so I can try to get this mess sorted out. I apologize if this has been asked somewhere els or if I'm in the wrong forum. but this seemed the most suited for my case. thank you to anyone who may be able to help
Click to expand...
Click to collapse
thatspideyguy said:
is anyone able to help me out?
Click to expand...
Click to collapse
Hi I had the same issue with my note 5 SM-N920T I managed to fix it by downloading a pre rooted with SU rom from xda I also had the twrp custom bootloader installed first for some reason my pc still picked up my phone and I was still able to upload the rom to the twrp location on the device. having done that I was the able to copy the zip file over to my device and flash it.
When I had the rom installed I was then able to download the original android rom (android 5 in my case) from sam mobile they also had the most up-to-date android 7 rom as well for the device then it was just a case of using android repair to un root the bootloader and install the original android bootloader this was also on sam mobile.
Then make sure the phone has a full battery as flash the stock firmware as you would normally with odin and have the latest Samsung drivers installed on yore system or it will fail.
After the flash has taken place the first boot will take some time my note 5 took around 45 min's and then when fully back up and running I had to spend a good 2 hours reinstalling and updating all my software and OTA updates.