OK.. so here it is in a nutshell... my S22 is soft-bricked...
I plugged my phone into my Mac (my primary computer) to back everything up. But, Smart Switch said I need to update the phone's version of Smart Switch. This was the fatal mistake. It hung the process. Over an hour later with zero movement on the progress bar I finally unplugged the phone.
Now, it is stuck in Odin mode. Well, I can boot to recovery mode. but none of the options work at all. I keep getting errors saying the partition geometry is corrupted. Normally, this would not be much of a problem, if I could mount the phone on my computers. I have a Mac, and a Forensics laptop setup with Odin3, as well as a number of other apps.
On my mac, in the Linux terminal, I cannot gain access to the device no matter what I have tried so far. I tried adb sideboot, but it cannot gain access to the device.
On the PC, the driver will not recognize the device. I updated to the newest Samsung Adroid drivers, with no joy. If I plug in my Android tablet, the driver is identified as "ssudb.sys". When I plug in my s22, the PC will not allow me to use this driver, insisting it be a .inf file. When I point it to the newest Samsung drivers, it says I am already using the best driver available, which of course does not work.
Natrually, since it is stuck in Odin mode, the s22 will not boot, so therefor I have no control over any aspect of the device.
Please help.
It is most critical I recover the /data partition. But, I would certainly like to have my phone back operational as well. I am stuck using an old s6 with very limited options in the meantime.
PLEAE HELP!
Thank you
How did it come to being bricked?
raul6 said:
How did it come to being bricked?
Click to expand...
Click to collapse
I believe he already said so, although I've never used smartswich before and I'm unsure how updating an application would cause a brick, unless I'm missing something or he meant the phone software itself needed the update and that's where things went wonky
"I plugged my phone into my Mac (my primary computer) to back everything up. But, Smart Switch said I need to update the phone's version of Smart Switch. This was the fatal mistake. It hung the process. Over an hour later with zero movement on the progress bar I finally unplugged the phone."
AthlonGFX said:
I believe he already said so, although I've never used smartswich before and I'm unsure how updating an application would cause a brick, unless I'm missing
Click to expand...
Click to collapse
It shouldn't cause brick and also software update popup comes before any operation commences
Since you can get into odin download mode, download your phones software from samfw.com or SamMobile.com and flash it with Odin.
When you download the firmware, it will be a zip file. Extract it and you'll get 5 files (starting with BL, AP, CP, CSC, and HOME_CSC)
When you're flashing with Odin, use HOME_CSC for the CSC slot and you won't wipe your data. Don't use CSC or it will wipe your data. Do not use anything for the USERDATA slot in Odin.
Odin 3 will not work. It gets stuck at setup connection. I have all the binaries, including the .pit file.
The partition information on the android is hosed.
So far, I have tried- (on Windows)
Odin 3.14.1
Odin 3.14.4
Droidkit
Fonelab
ADB sideload
Ultfone Android System Repair
Ultfone Android Data Recovery
Reiboot for Android
Android Studio (I have no idea even where to begin with this app)
And several apps on my Mac as well.
I have no joy with any attempts so far.
I finally managed to get the ddrivers installed so at least some of the apps like Odin will see the phone. But that's about it.
Also, I have a replacement phone coming tomorrow, but I still need my data- documents and imagery.
Ghostvet said:
So far, I have tried- (on Windows)
Odin 3.14.1
Odin 3.14.4
Droidkit
Fonelab
ADB sideload
Ultfone Android System Repair
Ultfone Android Data Recovery
Reiboot for Android
Android Studio (I have no idea even where to begin with this app)
And several apps on my Mac as well.
I have no joy with any attempts so far.
I finally managed to get the ddrivers installed so at least some of the apps like Odin will see the phone. But that's about it.
Click to expand...
Click to collapse
Use patched odin 3.13
kraz01 said:
Use patched odin 3.13
Click to expand...
Click to collapse
Why? What would that do that a newer version wouldn't?
Could you solve the problem? Could you at least recover your data?
No luck. Just shipped it off to Samsung with explicit instructions not to wipe the /data. I told them only to fix the partitions and not to write anything to the /data drive so I can dramatically recover the data.
Related
AARRRGGHHH! <whew>
Before it gets said, I *have* been reading. Reading, reading, reading. I'm trying to understand the whens, whys, and where-to-fors.
Specifically, this is about flashing the Tab 2 7.0:
Is it developer's preference that determines which we (users) need to use?
Is there any rhyme or reason (or differences) to which USB drivers to use?
Is there a consistent and reliable method for getting into a consistent and reliable starting state on both the tablet and the PC?
There are almost as many written procedures as there are .md5, .pit, and .img files. Some work - sometimes. Some don't work - sometimes.
I've booted, re-booted, and restarted so many times - I'm afraid I'm wearing this thing out.
I'm on my third Tab 2, and here is what I did to root every time:
1. Do not update the stock fimrware.
2. Open up Odin. Put your tablet in download mode (Power + volume down). Drivers are automatically installed.
3. Load CWM recovery through Odin.
4. Install the root zip or a custom rooted ROM through CWM.
Honestly, the type of files you're given tells you what to use to flash. I think odin only flashes md5/tar files and with heimdall, you get to choose what to flash. So yeah, this depends on developer preferences. You don't NEED to set up ADB, unless you wan't terminal access to your phone through your PC. If you do, install Kies from samsung's website. ADB drivers should automatically install once you plug in your tablet. You can then uninstall kies.
That's pretty much it. I do agree with you though, it can be quite confusing to newbies to sort through the mess and figure out what to do. heimdall/odin/recoveries/unsecured boot files etc etc.
nphil said:
1. Do not update the stock fimrware.
Click to expand...
Click to collapse
Too late! But thanks just the same.
nphil said:
You don't NEED to set up ADB, unless you wan't terminal access to your phone through your PC. If you do, install Kies from samsung's website. ADB drivers should automatically install once you plug in your tablet. You can then uninstall kies.
Click to expand...
Click to collapse
My story starts with my first root which left me with a crappy tablet. So I flashed it back to IML74K.P3113UEALCB with CWM and took the OTA to IML74K-P3113UEALD3, which left me rootless. Then, to restore root, I flashed it with ML74K_P3113UEALD3_unsecuredboot.img through Heimdall. A couple of the write-ups specify using Zadig.exe to install the USB drivers. And since the next step uses Odin, the only way I could get the tablet recognized was to let Kies connect to it first. That left me convinced that Heimdall has to use the same drivers that get installed by Zadig, and Odin has to use the Samsung drivers.
Maybe it's only on my ancient PC, but in the course of all this I discovered that Odin is picky about which USB port I use. Heimdall doesn't care. (Just one more thing to drive me nuts!) So maybe I don't need two sets of USB drivers - just the Samsung drivers? Now that I'm a *little* more experienced with the GT2, maybe I won't need Heimdall or ADB at all.
Based on what you said, I'm going to try removing all the crap I've installed and start over. I didn't know until this morning that I didn't have to install the entire freaking ADK (Just ADB.zip).
I did a really, really dumb thing a few months ago. I flashed a wrong something or another to fix an issue I had with my keyboard crashing after flashing another wrong thing..
Anywho, I couldn't get the damn keyboard to stop crashing for the life of me, so I set out to FORMAT/ CLEAR EVERYTHING ON MY PHONE. Yikes.
At this point, I can boot into recovery(CWM) and DL mode, but my PC will not recognize my phone at all. I installed your S3 toolkit v7.0, hoping it would help, but nay.
I cannot boot fully into Android to allow usb debugging, etc.
I can mount and unmount internal sd, cache, etc, but no drivers are being installed because it is not being recognized.
I've uninstalled Kies, etc.
HALP!HALP!
Daniel_NC said:
I did a really, really dumb thing a few months ago. I flashed a wrong something or another to fix an issue I had with my keyboard crashing after flashing another wrong thing..
Anywho, I couldn't get the damn keyboard to stop crashing for the life of me, so I set out to FORMAT/ CLEAR EVERYTHING ON MY PHONE. Yikes.
At this point, I can boot into recovery(CWM) and DL mode, but my PC will not recognize my phone at all. I installed your S3 toolkit v7.0, hoping it would help, but nay.
I cannot boot fully into Android to allow usb debugging, etc.
I can mount and unmount internal sd, cache, etc, but no drivers are being installed because it is not being recognized.
I've uninstalled Kies, etc.
HALP!HALP!
Click to expand...
Click to collapse
If you boot into DL mode and run odin on your PC does it fail to see the device?
apacseven said:
If you boot into DL mode and run odin on your PC does it fail to see the device?
Click to expand...
Click to collapse
I'm waiting on my PC to free up again(currently on a Mac). I had not tried Odin because in the past I was unable to mount internal SD, which I understood was keeping it from being recognized. I instead thought the Toolkit would do the trick automatically, though I most likely had the wrong idea. Everything is mountable again (for some odd reason), so I will give it a go.
Could I accomplish downloading drivers and flashing rom to device using Odin alone? Or should I use the Toolkit?
Thanks!
Daniel_NC said:
I'm waiting on my PC to free up again(currently on a Mac). I had not tried Odin because in the past I was unable to mount internal SD, which I understood was keeping it from being recognized. I instead thought the Toolkit would do the trick automatically, though I most likely had the wrong idea. Everything is mountable again (for some odd reason), so I will give it a go.
Could I accomplish downloading drivers and flashing rom to device using Odin alone? Or should I use the Toolkit?
Thanks!
Click to expand...
Click to collapse
Installing the drivers is independent from using odin. Install the drivers on the PC, fire up odin, connect phone (that has been booted into DL mode) and see if it connects. If it does, just flash a stock image and you are back in business.
You can use this driver http://d-h.st/vMk
apacseven said:
Installing the drivers is independent from using odin. Install the drivers on the PC, fire up odin, connect phone (that has been booted into DL mode) and see if it connects. If it does, just flash a stock image and you are back in business.
You can use this driver ...
Thanks!! I'll give it a shot now.
Click to expand...
Click to collapse
apacseven said:
Installing the drivers is independent from using odin. Install the drivers on the PC, fire up odin, connect phone (that has been booted into DL mode) and see if it connects. If it does, just flash a stock image and you are back in business.
You can use this driver......
Click to expand...
Click to collapse
Odin is not recognizing the device. Should I unmount or mount anything on the device for this to work properly? I have drivers installed.
Bought a banged up s6 demo unit on ebay. All I want is a pocketable tablet.
The demo software keeps respawning. Even using the pass codes and resetting.
Update recovery wipe says MDM doesn't allow wipe.
I would love to just Odin a ROM but Odin doesn't recognise when plugged in download mode.
I've tried many different Odin 3.10.6 3.9 etc
Tried dev mode adb to adb push various cfroot twpr etc.
but signature not verified. I can push files like this!!
Also the USB is recognised for normal file transfer.
I can't change the recovery without root.
Can't get root without decent recovery.
What can I do? What is wrong with Odin?
Demo unit...it has antitheft measures built in to protect against theft. I'd get your money back if you can.
Just to let you know Quarzar Odin recognises my S6 demo unit. I may try to flash a custom recovery. I hope nothing goes wrong... Do I need to root first to install a custom recovery with ODIN?
quatzar said:
Bought a banged up s6 demo unit on ebay. All I want is a pocketable tablet.
The demo software keeps respawning. Even using the pass codes and resetting.
Update recovery wipe says MDM doesn't allow wipe.
I would love to just Odin a ROM but Odin doesn't recognise when plugged in download mode.
I've tried many different Odin 3.10.6 3.9 etc
Tried dev mode adb to adb push various cfroot twpr etc.
but signature not verified. I can push files like this!!
Also the USB is recognised for normal file transfer.
I can't change the recovery without root.
Can't get root without decent recovery.
What can I do? What is wrong with Odin?
Click to expand...
Click to collapse
This sounds like more of a driver issue than an Odin issue. What does your device show up as in device manager?
I have a rooted S7 with TWRP recovery on it and i recently deleted my OS by accident as i was just trying to reset my phone to factory settings. Now the only thing i can do is boot into recovery mode and download mode, or i can just get stuck at a boot loop.
I have googled and googled and seen so many ways to try and fix this issue but nothing has worked for me. Heres a list of the issues i have and what i've tried so far. [Using Windows 10]
Installing Odin (3.12.3) and stock Samsung firmware from here.
Installing the necessary USB drivers from here.
My PC wont recognize my samsung device in either modes (recovery/download) and Odin wont recognize my phone either, as well as i cant find anything under "Device Manager".
Tried using ADB to transfer files to my S7 but when i activate ADB in recovery mode it just loads for a couple of seconds until it displays an error with no explanation.
I even tried downloading ADB drivers and necessary tools i got from this guide.
I also tried wiping Dalvik cache and cache.
I have tried three different USB cables on all available USB slots on my desktop PC and the one USB slot in my Surface and nothing works.
I have tried rooting previous phones but I'm still new to this rooting thing and there's a lot i don*t understand. Perhaps i downloaded the wrong USB drivers, or maybe I'm just unlucky. I just really need some help to understand how to fix this. If it can't be fixed is it possible to remove all traces of rooting on my phone?
The phone needs to be in Download Mode to use ODIN
The only sign it is connected is a COM port lit up at the top of the ODIN window
Add the .MD5 ROM to AP and hit start
Hello everyone,
so my phone is soft-bricked after failure attempt to flash combination files in order to fix the csc.
I follow this thread, but the problem actually has nothing with that.
I used the latest patched odin V3.13.1, with a combination file named COMBINATION_FAC_FA80_G965USQU3ARG2.tar, and the proccess failed at flashing the system, and now i'm stuck; unable to flash other firmwares.
Before that, the phone was working perfectly after I've flashed a G965U1 firmware on it, in order to get rid of the bloatware of the original branded G965U (I don't live in the US).
Also, it successfully OTA updated to the latest G965U1UEU3ARK5 Firmware just a few days ago.
Things that I've tried so far with no success:
*Used different usb ports, both usb 2 and usb 3; and different cables
*Using both an Intel-based PC, and an AMD-based. (I know it may sound unrelated, but thats actually what prevented me from flashing the G965U1 fmwr the first time I tried, because i was using and AMD PC)
*Reinstalling Drives, installing latest kies, installing latest samsung smart switch
*using older versions of Odin
*tried to install the original Sprint firmware (v2) G965USQS2ARF4 through odin
*tried to install the G965U1UEU3ARK5 firmware through odin
The phone is stuck in download mode. sometimes if I disconnect and reconnect it, I get an unrecognized usb device message. so I need to reboot the phone again to download mode so the pc will recognize it.
and the result is always a failure:
either due to rev check, with the original OEM firmware
during the installation at 'vendor'/'system' step, due to auth error, when trying the G965USQU3ARG2 Combination file or the G965U1UEU3ARK5 files with patched odin
or even before that step with older versions of odin.
I'm out of ideas... I hope someone here has the knowledge to help in some way, Please...
Amsiman said:
Hello everyone,
so my phone is soft-bricked after failure attempt to flash combination files in order to fix the csc.
I follow this thread, but the problem actually has nothing with that.
I used the latest patched odin V3.13.1, with a combination file named COMBINATION_FAC_FA80_G965USQU3ARG2.tar, and the proccess failed at flashing the system, and now i'm stuck; unable to flash other firmwares.
Before that, the phone was working perfectly after I've flashed a G965U1 firmware on it, in order to get rid of the bloatware of the original branded G965U (I don't live in the US).
Also, it successfully OTA updated to the latest G965U1UEU3ARK5 Firmware just a few days ago.
Things that I've tried so far with no success:
*Used different usb ports, both usb 2 and usb 3; and different cables
*Using both an Intel-based PC, and an AMD-based. (I know it may sound unrelated, but thats actually what prevented me from flashing the G965U1 fmwr the first time I tried, because i was using and AMD PC)
*Reinstalling Drives, installing latest kies, installing latest samsung smart switch
*using older versions of Odin
*tried to install the original Sprint firmware (v2) G965USQS2ARF4 through odin
*tried to install the G965U1UEU3ARK5 firmware through odin
The phone is stuck in download mode. sometimes if I disconnect and reconnect it, I get an unrecognized usb device message. so I need to reboot the phone again to download mode so the pc will recognize it.
and the result is always a failure:
either due to rev check, with the original OEM firmware
during the installation at 'vendor'/'system' step, due to auth error, when trying the G965USQU3ARG2 Combination file or the G965U1UEU3ARK5 files with patched odin
or even before that step with older versions of odin.
I'm out of ideas... I hope someone here has the knowledge to help in some way, Please...
Click to expand...
Click to collapse
Guys at imeigurus has a service. Check on them. Those guys have access to special Samsung firmware that they can manipulate Samsung's as they like. They do what others can't, they can support you remotely using teamviewer. But snap the download pic here let me see
show me your device in download mode
leonardojt said:
Guys at imeigurus has a service. Check on them. Those guys have access to special Samsung firmware that they can manipulate Samsung's as they like. They do what others can't, they can support you remotely using teamviewer. But snap the download pic here let me see
Click to expand...
Click to collapse
successnbd said:
show me your device in download mode
Click to expand...
Click to collapse
OK so that's how it looked like:
download-mode
after writing this post I realized that I haven't tried flashing an OEM rev3 firmware
so I downloaded one after finding out which one is the right file
and I tried flashing it on a completly other pc than the 2 I've already tried it on
and it worked:victory:
here's the recovery after the successful flash:
recovery