Some say "Bricking" is when the phone doesn't turn on at all, or does and displays and does nothing; some say there are different states of bricking. In any case... I'm only an intermediate, and I did not have any booting problems before this. So, with the least-common denominator in mind, please read on.
I have a Samsung Galaxy S3, SGH-i747 ATT. It was out of warranty anyway and I've flashed custom ROMs on it many times before without issue. I dropped it about a week ago and the LCD broke. Upon having it fixed, I noticed it no longer booted properly. I am able to get into ODIN's download mode, and I am able to flash stock recovery, but neither have proven helpful.
I was originally running Slimkat 4.4, but decided to flash back to the stock Android ROM since it would no longer boot properly anyway. This is where it gets strange.
First I attempted to flash CWM and TWRP as my recoveries. ODIN said both were successful in flashing on their respective attempts, but each one was simply a black screen after the Samsung logo disappeared. The blue text in the top-left letting me know it was booting into recovery was present with the logo, but after it disappeared, nothing.
So I tried to install stock recovery, and to my surprise, it worked, though it's really not useful for anything. Chainfire's CF-autoroot was also flashable and functional, but when I tried using adb to push files to the device, I would get several errors:
From the ADB command line, when trying to push something, I'd get "Error: closed".
From the recovery's log, sometimes when I'd successfully send a ROM to be installed, I'd get various notifications, such as: "Failed to verify whole-file signature" and "Incorrect footer", "Installation aborted".
When I attempt to flash any ROMs via ODIN, I get a few different errors, including (Not verbatim, these are from memory):
REV CHECK FAIL
DEV UNSUPPORTED
FUSED 2 > BINARY 0 [This one is especially confusing to me]
SECURE CHECK FAIL
and one from the ODIN side that said something along the lines of "HLOS-BIN" or something when it failed to flash.
So I can turn the device on, get to download mode, and even flash the stock ROM and CF-autoroot... but after 20 hours of reading other people's similar problems and varying degrees of success in their solving them, I'm stumped. I hope someone here might be able to share their superior knowledge vis-a-vis Android!
-Krust
Update
I've tried many things.
Right now I'm trying to re-flash Slimkat 4.4 (Which I was already using), and I know anything JB 4.3 or above will restrict the bootloader from downgrading, so maybe that was the problem. But if this doesn't work... I'm not sure what to do. Will post error updates if any.
-Krust
Same Status
I still get REV CHECK FAIL Fused 2 > Binary 0 error.
I believe this is from attempting to flash to a version lower than what I had (4.4).
I am unable to find stock firmware for the ATT SGH-i747 for 4.4 or above.
Please help! This is my only phone, and I know it can be restored because I can still get into download mode, but something's blocking ODIN from performing the flash, even on packages that seem to be the correct version.
Update
From what I have been able to find, I will need to update to an Android variant 4.4.2 or above due to the restricted bootloader.
My only problem... I haven't been able to FIND any stock ROMs for 4.4.2.
Everything I try returns a variety of errors, the most common being FUSED 2 > BINARY 0 (Which I now understand means I am attempting to downgrade) because I have not been able to find anything like Slimkat 4.4.2 that is in .tar format to flash.
I am very stuck and confused, and this is my only phone. Lesson learned: Keep up with the nuances of updates. But for now, I really need to get this fixed. Does anyone have experience with this particular problem?
Update
I was able to flash a modded TWRP recovery and was able to boot into it.
However, when I try to install ROMs via zip, I get the error E: Cannot execute binary update file.
One ROM, a Slimkat for i747M (Which isn't even my phone), appeared to flash successfully, but wouldn't boot.
GApps for Slimkat 4.4.4 was also able to flash successfully on its own, but the corresponding Slimkat could not.
I am quite stuck. Please help.
Hi,
Try posting your question here:
AT&T Galaxy S III Q&A, Help & Troubleshooting
The experts there may be able to help.
Good luck!
Hey, I made this account to ask this question I'm pretty desperate,
My phone was acting up (overheating, WiFi didn't work half the time), so I decided to reflash my cyanogenmod rom, me being the idoit that I am I didn't do a backup before formatting my phone, I tried to flash the zip file but twrp kept crashing, so the next logical step was to use ADB sideload to flash the rom, that didn't work as well as I expected either the install kept failing at 88% as I was rebooting the phone for yet another attempt, recovery wouldn't start at all, at that point I was pretty frustrated, so I decided to flash the phone back to stock touchwiz, I downloaded the stock firmware and attempted to flash it with odin, low and behold that didn't work either (auth error), I tried again multiple times with firmware files downloaded from different sites but those didn't work either, I also tried flashing stock PIT files to no avail.
So here I am at 5 am with a bricked phone and 8gb of tar files on my desktop any help at all would be greatly appreciated.
Thanks in advance.
i know this thread is old, but can you get to download mode still?
What's the model and type of phone is this ?
hey all
I did a basic root on my samsung galaxy s6 a few days ago. just installed superSu and gave me root access. after that I installed TWRP which I then used to try and install the xposed framework. From then on my phone is stuck on the samsung screen saying kernel is not seandroid enforcing. I downloaded the stock rom for my phone (sm-g920F on 6.01) and attempted to flash it via odin 3.07 but it always failed after the sboot.
i have searched to try and find a solution but nothing I can find will work. can anyone help?
so i got my s6 working after flashing a full stock firmware i found via a link on this forum (i forget which one...sorry)
it gave me BL_G920FXXU3DPBG_CL7086820_QB8626574_REV02_user_low_ship.tar.md5
AP_G920FXXU3DPBG_CL7086820_QB8626574_REV02_user_low_ship.tar.md5
CP_G920FXXU3DPB6_CL7086820_QB8569466_REV02_user_low_ship.tar.md5
CSC_BTU_G920FBTU3DPB1_CL7140831_QB8460122_REV02_user_low_ship.tar.md5
it also recommended that I flash the pit file ZEROFLTE_EUR_OPEN.pit.
this was all done via the latest version of odin. initially, the flashing failed at cm.bin so I reflashed omitting the bootloader and all seemed to be well.
My phone set up fine and then I realised that it will not recognise my sim...or any sim for that matter. in settings under sim card status...every entry is listed as unavailable. IMEI is unknown as is baseband version.
i realise that I have obviously messed up big time with the initial flashing (uhuh....backup...backup....backup) but I would really like some help to get my phone back up and running as a ...well...phone.
any help or suggestions would be most appreciated.
thanks in advance x
vickstew2000 said:
so i got my s6 working after flashing a full stock firmware i found via a link on this forum (i forget which one...sorry)
it gave me BL_G920FXXU3DPBG_CL7086820_QB8626574_REV02_user_low_ship.tar.md5
AP_G920FXXU3DPBG_CL7086820_QB8626574_REV02_user_low_ship.tar.md5
CP_G920FXXU3DPB6_CL7086820_QB8569466_REV02_user_low_ship.tar.md5
CSC_BTU_G920FBTU3DPB1_CL7140831_QB8460122_REV02_user_low_ship.tar.md5
it also recommended that I flash the pit file ZEROFLTE_EUR_OPEN.pit.
this was all done via the latest version of odin. initially, the flashing failed at cm.bin so I reflashed omitting the bootloader and all seemed to be well.
My phone set up fine and then I realised that it will not recognise my sim...or any sim for that matter. in settings under sim card status...every entry is listed as unavailable. IMEI is unknown as is baseband version.
i realise that I have obviously messed up big time with the initial flashing (uhuh....backup...backup....backup) but I would really like some help to get my phone back up and running as a ...well...phone.
any help or suggestions would be most appreciated.
thanks in advance x
Click to expand...
Click to collapse
Try smart switch. Not sure if it could restore the imei but it could bring the phone back to original csc when you bought it.
Sent from my SM-G925F
Rosli59564 said:
Try smart switch. Not sure if it could restore the imei but it could bring the phone back to original csc when you bought it.
Sent from my SM-G925F
Click to expand...
Click to collapse
i had tried several times to connect to smart switch but it would not recognise my phone. after a lot of faffing about I finally managed to get it to do an emergency recovery and all seems well so far. it even restored my imei number so thanks for that suggestion Rosli. much appreciated xx
When u install xposed did u ude the special wanam version of the framework
Would say whipe cashe and wait a little while for stock roms like 40 minutes after first time install
Greetings.
I didn't post in very long time on this forum,since I could handle most of the problems on my own,now I need some andvanced tips and advices,so I'm reporting in.
I bough myself a Samsung Galaxy S4 Black Edition last year here in Bosnia and Hercegovina.Beautiful phone,never got a scratch on it,It had Android 4.2.2 Jelly Bean out of the box but all of the features from basic S4 except one,it couldn't update firmware to Lolipop 5.0.1.
That used to bother me,since I had much older devices that supported JB and this phone was just special,enough that I couldn't let it be my daily driver having unused potential,so i threw myself at work(which will later prove a very bad decision).
I checked for OTA updates in the settings and that option would litteraly do nothing,providing no info,or searching for new updates.
Smash that Build number,got into developer mode,toggle USB debugging,Install Kies on PC,run it as Admin,download latest drivers,connect the device,Firmware update asks for IMEI and s/n,type them in,says to check my s/n and IMEI,do that few times under different compatibility options,still the same.
I thought it must be something bad with data/catche so i reset to recovery mode and wipe them out,setup the phone,enter the OTA update for second time,it shows me "Your device have been modified, Software updates are not available", check device status and it states "Samsung",after several attempts it sometime said "Modified" sometimes "Samsung",Kies didn't recognise the device through all this process.
I was already lost here,but I thought,hell Kies isn't working,neather is OTA,i could flash using Odin,that might do the trick.
Went to Sammobile,downloaded latest drivers and Odin,found one Firmware that I though was compatible.,unbloked them in properties and set to rin as Admin.
Uninstalled Kies and checked for leftover drivers again,and it was all clear to go,ran odin,mounted firmware,set device in download mode and started flashing but Odin poped out "complete(write) operation fail" error.
Didn't want to try fixing it,went straight back to SM and downloaded two other firmwares,one said "complete(write) operation fail",and the other "Re-Partition operation failed",so I thought Odin was bad,since I checked on two PC's with several USB ports.
Download two more versions of Odin and find a stock s4 PIT file here somewhere for repartrition error.
Extracted everything,unblocked and ran with privilegies,same thing on both Odin versions,except that only Odin 3.07 could flash the pit file alone with no problems it passed.
Next time i ran download mode i tried to flash the firmware write fail came up again,extracted recovery and flashed it alone,worked like a charm,so I tried flashing once again,it proceedes a little further with same write error.
Reset the phone to wipe data and catche and it goes into "Firmware Upgrade Encountered An Issue Error",Install kies,it still doesn't recognise the phone.
Out of option right now I go for search of alternative recovery software,and I found the famous "Dr.Fone" (how stupid I was to not read all those,"if it wasn't for this software my phone would die" comments)
Installed it,ran recovery my phone shuts down and displays "set warranty bit: kernel message",from this point nothing works except recovery mode,so I install CWM recovery and flash a Custom ROM,now only this option that sets my phone in working order and I want to recover it's Firmware back,Anyone that could help me with this issue,or had it solved before?
Atleast give it a try.
this amount of pain can't be titled
Drow_Warlord said:
Greetings.
I didn't post in very long time on this forum,since I could handle most of the problems on my own,now I need some andvanced tips and advices,so I'm reporting in.
I bough myself a Samsung Galaxy S4 Black Edition last year here in Bosnia and Hercegovina.Beautiful phone,never got a scratch on it,It had Android 4.2.2 Jelly Bean out of the box but all of the features from basic S4 except one,it couldn't update firmware to Lolipop 5.0.1.
That used to bother me,since I had much older devices that supported JB and this phone was just special,enough that I couldn't let it be my daily driver having unused potential,so i threw myself at work(which will later prove a very bad decision).
I checked for OTA updates in the settings and that option would litteraly do nothing,providing no info,or searching for new updates.
Smash that Build number,got into developer mode,toggle USB debugging,Install Kies on PC,run it as Admin,download latest drivers,connect the device,Firmware update asks for IMEI and s/n,type them in,says to check my s/n and IMEI,do that few times under different compatibility options,still the same.
I thought it must be something bad with data/catche so i reset to recovery mode and wipe them out,setup the phone,enter the OTA update for second time,it shows me "Your device have been modified, Software updates are not available", check device status and it states "Samsung",after several attempts it sometime said "Modified" sometimes "Samsung",Kies didn't recognise the device through all this process.
I was already lost here,but I thought,hell Kies isn't working,neather is OTA,i could flash using Odin,that might do the trick.
Went to Sammobile,downloaded latest drivers and Odin,found one Firmware that I though was compatible.,unbloked them in properties and set to rin as Admin.
Uninstalled Kies and checked for leftover drivers again,and it was all clear to go,ran odin,mounted firmware,set device in download mode and started flashing but Odin poped out "complete(write) operation fail" error.
Didn't want to try fixing it,went straight back to SM and downloaded two other firmwares,one said "complete(write) operation fail",and the other "Re-Partition operation failed",so I thought Odin was bad,since I checked on two PC's with several USB ports.
Download two more versions of Odin and find a stock s4 PIT file here somewhere for repartrition error.
Extracted everything,unblocked and ran with privilegies,same thing on both Odin versions,except that only Odin 3.07 could flash the pit file alone with no problems it passed.
Next time i ran download mode i tried to flash the firmware write fail came up again,extracted recovery and flashed it alone,worked like a charm,so I tried flashing once again,it proceedes a little further with same write error.
Reset the phone to wipe data and catche and it goes into "Firmware Upgrade Encountered An Issue Error",Install kies,it still doesn't recognise the phone.
Out of option right now I go for search of alternative recovery software,and I found the famous "Dr.Fone" (how stupid I was to not read all those,"if it wasn't for this software my phone would die" comments)
Installed it,ran recovery my phone shuts down and displays "set warranty bit: kernel message",from this point nothing works except recovery mode,so I install CWM recovery and flash a Custom ROM,now only this option that sets my phone in working order and I want to recover it's Firmware back,Anyone that could help me with this issue,or had it solved before?
Atleast give it a try.
Click to expand...
Click to collapse
Day#4 Fail compilation
I see that this gets no response,but I'll continue this thread just in case I fix this and somebody else gets into same problem themselves.
I mentioned before that I somehow flashed custom ROM over CWM and that helped my phone boot into working state after bootloop error caused by greatest Android software there is on the internet,the legendary "Dr.Fone"
The Custom rom used was "[OFFICIAL][i9500][5.1.x] CyanogenMod 12.1 for Samsung Galaxy S4 [NIGHTLY]" From xda user: Alberto96 (thank you friend).
After several other failed attempts of implementing Stock firmware on this bricked device over the PC,I got to the point where I think that it's literally imposible to make it work since I tried so many ways and patterns of installation with no difference in the outcome results whatsoever.
I took a moment to rethink my strat over this and googled other ways of flashing that firmware without using PC.
Found 2 possible solutions that I'm trying to make use of,first is Odin Mobile and the Other is FlashFire.
Since both require rooted devices,finding way to root bricked S4 wasn't a very pleasant experiance,since flashing SuperSU through CWM recovery didn't work,Odin managed to flash me nice Autoroot from Chainfire over the custom ROM I installed before,I found a problem even there since the I9505 autoroot wouldn't work,the custom firware had changed the phone model to I9507 that I downloaded the Autoroot for,was a confusing issue,but I managed to root it anyways.
Page I used for this purpose was Chainfire Autoroot database(sorry if I'm violating forum rules but I think this could be left here without further discussion about it).
After rebooting the device I downloaded Rootcheck software along with SuperSU and FlashFire which confirmed that it's fully unlocked/rooted.
Now I'm recharging my phone so I can later tonight go ahead and transfer firmware to it's SD card and try to flash it once again with FlashFire,last option I'm thinking of as of now if this wouldn't have any progress is to download Odin mobile and try another flash,I'm running out of ideas on this one.
Sorry for the long posts,but these get no respose so who cares.