Hello, before I call Samsung in hopes they might give me a RMA, I need help.
I had unlocked the bootloader in the past and had recently installed the IMM26D official stock rom that was not rooted. This worked fine for a month or so then yesterday the phone would not boot up anymore, just sitting at "GOOGLE' across the screen with the unlocked padlock on the bottom. So here is what I have tried ;
I was able to load CWM on it, but once in there, I could not do anything that pointed to the sdcard (mount, mount usb, format, wipe and erase). The minute I tried this, the log would show "Error mounting \sdcard\".
I then tried ODIN to see if I could reload the IMM26D, It would start and get only about 5% of the way and just stop for eternity. I tried the same cable I used before when this worked, and a different one.
And at the last step (Stupidly), I tried doing a fastboot oem lock and it locked it. Now when I go back in and do a fastboot oem unlock, the options come up on the screen and when choosing Yes to unlock, the phone just locks up.
Could this be a corrupted or damaged SDcard in the phone (now I wish it wasn't internal and rather a external one) ?
Is there ANYTHING I can do at this point? Is there a .PIT file specific for this phone that I can try loading with ODIN ?
I would love to somehow load the "stock" recovery back on it but since I can't unlock the bootloader, seems that idea is toast. It would be a lot easier to take to Sprint or send to Samsung if it didn't have CMW on it.
Sorry for the long post, but thanks in advance ..
what happened with this issue? Was it resolved, did you have it swapped with another phone?
Sent from my Nexus S 4G using Tapatalk 2
Ended up calling Samsung and sending it in, luckily it was still under warranty. Looks like they fixed it and waiting for it to return. There was nothing I could do on my end at the time, it was a corrupted internal SD card.
I followed this links w.mobilescommunity.com/android-tips-tutorial/208463-how-root-samsung-galaxy-s-blaze-4g.html[/url] instructions to a "T" and when the phone came back on it stops at the welcome screen no matter what. I tried to install ClockworkMod Recovery per these instructions /theunlockr.com/2012/04/17/how-to-root-and-install-clockworkmod-recovery-on-samsung-galaxy-blaze-4g/[/url] and it seemed to work as I get the OMR mode when I try to get the download screen without having it already cable connected to the PC. When I have it connected to the PC I am able to get to the "Download" mode. OI! I never have had a problem rooting before. The stock OS ICS 4.0.4 was on it and I bought it new from T-Mobile and then it did the OTA update a week ago. I have had nothing on it other than stock and a few camera apps. I have already tried to return it to OEM with the OMR recovery but its still the same, always booting to the welcome screen. When I try to get it into a mode, ether the recovery mode or the download mode, it sometimes vibrates several times and then "May" go into one or the other depending if its cable tethered or not. HELP PLEASE, I disabled and this is my only outside contact short of coming into town to use the Internet at a cafe. Thanks, Jeff
Blaze Soft Brick
fallendaemon said:
I followed this links w.mobilescommunity.com/android-tips-tutorial/208463-how-root-samsung-galaxy-s-blaze-4g.html[/url] instructions to a "T" and when the phone came back on it stops at the welcome screen no matter what. I tried to install ClockworkMod Recovery per these instructions /theunlockr.com/2012/04/17/how-to-root-and-install-clockworkmod-recovery-on-samsung-galaxy-blaze-4g/[/url] and it seemed to work as I get the OMR mode when I try to get the download screen without having it already cable connected to the PC. When I have it connected to the PC I am able to get to the "Download" mode. OI! I never have had a problem rooting before. The stock OS ICS 4.0.4 was on it and I bought it new from T-Mobile and then it did the OTA update a week ago. I have had nothing on it other than stock and a few camera apps. I have already tried to return it to OEM with the OMR recovery but its still the same, always booting to the welcome screen. When I try to get it into a mode, ether the recovery mode or the download mode, it sometimes vibrates several times and then "May" go into one or the other depending if its cable tethered or not. HELP PLEASE, I disabled and this is my only outside contact short of coming into town to use the Internet at a cafe. Thanks, Jeff
Click to expand...
Click to collapse
----- Did you ever get your Blaze fixed?....
pretty much the same problem i have!!! i currently have the samsung galaxy s blaze and rooted it to the custom rom from konane using the odis program, it said passed and auto rebooted my phone, but when it gets to the home screen where you touch the android to set up your phone like its brand new, when i hit the android bot all that happens is a message force closing a bunch of apps appear. i can get to the download mode to install new roms and i've tried to re root back to the stock rom but now my computer doesnt recognize my phone. i've downloaded and installed the samsung drivers from several different forums including the ones recommended here but still nothing. what im wondering is if theres a way to install the rom or driver from an sd card to the phone or something else that im missing, or is my phone just screwed? any and all help is greatly appreciated.
So here's a doozy. First, some background. During a routine update to a new version of my favorite rom, IMEI data got borked. My backup was apparently incomplete, so couldn't restore it that way. My phone has been unable to connect a computer via usb in more than a charging capacity for a few months, so any pc-based tools like ODIN or QPST were out of the question. Only hope was to go back to a rooted stock rom and try the dialer solution. So I try flashing root66 via Mobile ODIN. Note that this overwrites CWM to the stock recovery, in addition to overwriting pretty much everything else. For whatever reason, the OS is now borked. Can't get past the Samsung GSIII screen. I can still reach Download Mode and Recovery, though. However, as mentioned before, ODIN is not an option because no computer can see my device over USB. The recovery is now the stock recovery, so the only thing it will recognize is a signed update.zip from Verizon herself. Anything else I try to flash from external SD gets the whole signature verification error.
To sum:
The Problem
Need to get to a working OS. This likely needs to be stock.
Complications and Constraints
ODIN is not an option, nor is any other pc-based or usb-based tool.
I'm stuck with the stock recovery, which requires signature verification.
Theorized Solutions
I could either somehow flash CWM via signed zip file from stock recovery (don't know if this exists, if it does I haven't been able to find it), or,
I could flash a signed OTA zip, like what would arrive on the phone from Verizon. I've been having a lot of trouble finding one of these, since everyone and their grandmother seems to want to use ODIN to flash leaked OTAs. I'm thinking that of the OTAs, the initial upgrade to JB is probably my best bet, since it likely replaced more of the system than the other OTAs. I'm more than open to suggestions, though.
Thoughts?
Boot into recovery and do a factory reset. That typically is recommended if you're stuck on the boot logo after an Odin flash.
How did you lose usb to pc access? When you install the Samsung drivers from their website, what does your computer do? Which usb cable have you been using?
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
Boot into recovery and do a factory reset. That typically is recommended if you're stuck on the boot logo after an Odin flash.
How did you lose usb to pc access? When you install the Samsung drivers from their website, what does your computer do? Which usb cable have you been using?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Factory reset was the first thing I tried. No go. I've tried every option available in the stock recovery, with no success. Gotta say, not really fond of this whole stock recovery thing. Fairly useless.
I haven't had usb to pc access ever since I played Ingress in a snowstorm a few months ago and some moisture got into the charging port, and I didn't properly dry it out. There's a little bit of corrosion in there now. It still charges fine most of the time (I'm sure not as well or as consistently as when it was new), but it can't connect to the computer in more than a charging capacity. I've tested a large variety of usb cables, most of which worked before the snowstorm, and none give me pc access. Some give me pc access for a few seconds, but none give a connection that's stable enough to run ODIN or QPST or the like.
I should note that I have a microSD to SD adapter, so I can still move files to and from my external SD card. Anything available on the internet can make its way onto my SD card so long as it's 7.96 Gb or smaller.
EDIT: I should clarify that I *did* have usb to pc access before the snowstorm. Samsung drivers worked fine, etc, the typical file transfers over usb worked fine, adb worked fine, etc.
I had the same problem a few months ago when I used mobile odin. I was lucky enough to be able to use the regular ODIN to start from the beginning flash stock everything. You need to get regular ODIN to work. Take the phone to a repair place have them clean the rust and re-soter the connections. That is what I would try. Sorry I wasn't of any more help.
Sent from my SCH-I535 using xda app-developers app
Lehocki said:
I had the same problem a few months ago when I used mobile odin. I was lucky enough to be able to use the regular ODIN to start from the beginning flash stock everything. You need to get regular ODIN to work. Take the phone to a repair place have them clean the rust and re-soter the connections. That is what I would try. Sorry I wasn't of any more help.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I took a closer look at the microUSB port on the phone. On closer inspection, with a bright light, I really don't see any corrosion, and I checked the water damage indicators, and none have been tripped. Which makes me question whether or not the port starting to fail really was related to the snowstorm, or if that was a coincidence. I've decided to just go ahead and get it replaced under warranty--even if I could rescue the system, that faulty port is actually a really huge problem, more so than I had realized. Not being able to use ODIN to un-brick is bad, I've decided. Now the big question is going to be, will they be able to tell the phone's been messed with, and if so, how can I cover my tracks with a bootlooped phone, stock recovery, and no possibility of Odin or Heimdall? I'm thinking it should mostly be okay--in Download mode, everything checks out as normal, except for system status, which says custom. I'm betting that if it came down to it, I could probably argue that it could fail to recognize a borked but otherwise stock system, and therefore call a normal system custom.
If not, though, then I better get started on cracking Samsung's update.zip encryption so I can sign my own injection package with their signature...
adiv.paradise said:
I took a closer look at the microUSB port on the phone. On closer inspection, with a bright light, I really don't see any corrosion, and I checked the water damage indicators, and none have been tripped. Which makes me question whether or not the port starting to fail really was related to the snowstorm, or if that was a coincidence. I've decided to just go ahead and get it replaced under warranty--even if I could rescue the system, that faulty port is actually a really huge problem, more so than I had realized. Not being able to use ODIN to un-brick is bad, I've decided. Now the big question is going to be, will they be able to tell the phone's been messed with, and if so, how can I cover my tracks with a bootlooped phone, stock recovery, and no possibility of Odin or Heimdall? I'm thinking it should mostly be okay--in Download mode, everything checks out as normal, except for system status, which says custom. I'm betting that if it came down to it, I could probably argue that it could fail to recognize a borked but otherwise stock system, and therefore call a normal system custom.
If not, though, then I better get started on cracking Samsung's update.zip encryption so I can sign my own injection package with their signature...
Click to expand...
Click to collapse
If using Windows the USB will act like there are no drivers at times. The fix I found was to connect to PC in charge mode. Then go to download mode while connected to PC. It will reactivate drivers from phone side. Have done this many times on Win8. Worth a shot.
prdog1 said:
If using Windows the USB will act like there are no drivers at times. The fix I found was to connect to PC in charge mode. Then go to download mode while connected to PC. It will reactivate drivers from phone side. Have done this many times on Win8. Worth a shot.
Click to expand...
Click to collapse
Some phone is bricked that not recognize the phone on device manager and won't charge too.
tomy1986.nt said:
Some phone is bricked that not recognize the phone on device manager and won't charge too.
Click to expand...
Click to collapse
His charges.That is not a brick. A brick is black screen with no access to recovery, download mode. A bricked phone will be seen by USB but just as a device and not as an S3. If you have the screens that is a soft brick and need to find what the problem is. Could just be a bad USB port on phone or PC or an operator problem. If have any screen the device is not bricked. Ok I see now. You are looking for JTag work and are in Texas. I would still say send to Josh at Mobile Tech in College Station, Tx cause we know he knows what he is doing. You don't have video of unbricking S3? S2 is old and obsolete and no where near the same device. Also must have RIFF for the device. I can make it pass warranty for free over PM.
prdog1 said:
His charges.That is not a brick. A brick is black screen with no access to recovery, download mode. A bricked phone will be seen by USB but just as a device and not as an S3. If you have the screens that is a soft brick and need to find what the problem is. Could just be a bad USB port on phone or PC or an operator problem. If have any screen the device is not bricked. Ok I see now. You are looking for JTag work and are in Texas. I would still say send to Josh at Mobile Tech in College Station, Tx cause we know he knows what he is doing. You don't have video of unbricking S3? S2 is old and obsolete and no where near the same device. Also must have RIFF for the device. I can make it pass warranty for free over PM.
Click to expand...
Click to collapse
You do not know how the bricked phone look like, some bricked like no power, some like download mode but can not flash firmware, some phone is bricked like wont recognize on device manager.
Please check my video for knowing what kind of device I have already done, and see my feed back on ebay.
tomy1986.nt said:
You do not know how the bricked phone look like, some bricked like no power, some like download mode but can not flash firmware, some phone is bricked like wont recognize on device manager.
Please check my video for knowing what kind of device I have already done, and see my feed back on ebay.
Click to expand...
Click to collapse
If a device can boot to recovery or download or if it charges or is detected when connected to PC then it isn't truly bricked, it's only softbricked. A truly bricked device will not charge, has no LED when connected to PC, can't be detected by PC in any kind of way, will not boot to recovery or download mode and will not power on in any way. This is actually called a "hardbrick".
Sent from my SM-S903VL using Tapatalk
Hello,
Yesterday night i broke my beloved one plus one with the door of my car, the screen is cracked up but the LCD Display still work and show everything; the problem is that the touch detection is dead, i cant access to the phone through my PC since the phone have a pass that lock the memory until it is unlocked
My phone is rooted, but my recovery is TeamWin TOUCH recovery and well the touch doesn't work :/
I am kindda clueless and i really hope one of you might have the solution for me, i have a really important data for study/work as long as photo and part of my live into this phone i'll be devasted if i were loosing all this
I am waiting for any proposition you may have
Thanks
PS: Does anyone know how much would it cost to repair ? Lcd work but i think i saw a leak so it wont last long
This is what i am thinking about right now:
Flashing a new non-touch recovery via fastboot mode
Open the ADB menu and make and ADB backup if possible
Last time i did an ADB it was with the phone fully booted so i don't know if it is possible from the recovery
Also i could open the recovery and access the file from there ? does it bypass the code protection it have on normal boot ?
So, I followed all the basic instructions of getting ADB, downloading and flashing twrp, and my goal was solely to root my phone so I went ahead and got SuperSU as well and installed it through twrp. Everything went fine until I went to reboot my phone and it wouldn't work, it would only boot into twrp no matter what I did. In a moment of foolishness, I decided to go to the reset section of twerp, and switched to partition A (it was on partition B, where everything had been installed). Now my phone only has a black screen, and no amount of trying to soft reset or anything is turning it on. The only indication I have that my phone is doing anything, is that when I plug it in to my pc I can hear the connection sound. I can't access any files on the phone, and ADB doesn't recognize that the phone is plugged in. It's a Moto g7 power phone, and I used the latest versions of the programs. Also, I did do something of a ****ty backup before I started the process, but since my phone wasn't rooted I don't know how much that'll help me. All the stuff I find online says to just install a stock rom or whatever; but I can't even access my phone to do that. Is there ANYTHING I can do or am I ****ed?
Thanks so much for any and all help
Zacigator said:
So, I followed all the basic instructions of getting ADB, downloading and flashing twrp, and my goal was solely to root my phone so I went ahead and got SuperSU as well and installed it through twrp. Everything went fine until I went to reboot my phone and it wouldn't work, it would only boot into twrp no matter what I did. In a moment of foolishness, I decided to go to the reset section of twerp, and switched to partition A (it was on partition B, where everything had been installed). Now my phone only has a black screen, and no amount of trying to soft reset or anything is turning it on. The only indication I have that my phone is doing anything, is that when I plug it in to my pc I can hear the connection sound. I can't access any files on the phone, and ADB doesn't recognize that the phone is plugged in. It's a Moto g7 power phone, and I used the latest versions of the programs. Also, I did do something of a ****ty backup before I started the process, but since my phone wasn't rooted I don't know how much that'll help me. All the stuff I find online says to just install a stock rom or whatever; but I can't even access my phone to do that. Is there ANYTHING I can do or am I ****ed?
Thanks so much for any and all help
Click to expand...
Click to collapse
U are in edl mode u need to search for blank flash it should get u back up and running
Zacigator said:
So, I followed all the basic instructions of getting ADB, downloading and flashing twrp, and my goal was solely to root my phone so I went ahead and got SuperSU as well and installed it through twrp. Everything went fine until I went to reboot my phone and it wouldn't work, it would only boot into twrp no matter what I did. In a moment of foolishness, I decided to go to the reset section of twerp, and switched to partition A (it was on partition B, where everything had been installed). Now my phone only has a black screen, and no amount of trying to soft reset or anything is turning it on. The only indication I have that my phone is doing anything, is that when I plug it in to my pc I can hear the connection sound. I can't access any files on the phone, and ADB doesn't recognize that the phone is plugged in. It's a Moto g7 power phone, and I used the latest versions of the programs. Also, I did do something of a ****ty backup before I started the process, but since my phone wasn't rooted I don't know how much that'll help me. All the stuff I find online says to just install a stock rom or whatever; but I can't even access my phone to do that. Is there ANYTHING I can do or am I ****ed?
Thanks so much for any and all help
Click to expand...
Click to collapse
Did you get it running