Galaxy S III Hard Bricked?? - Galaxy S III Q&A, Help & Troubleshooting

Hey gang,
Got my hands on a brand new S III yesterday and of course jumped straight to rooting it.
The root went fine and CWM was working beautifully. I copied the .zip file for Blackstar rom onto the internal SD card and rebooted into recovery. After running the data wipe/factory reset option as per usual, I used CWM Recovery to install the .zip I copied. It began to to it's thing and then encountered an error. This worried me for obvious reasons, so I factory reset it again and rebooted it with the command in recovery.
Which brings us to now:
The phone is completely non responsive. The computer recognizes it as QHSUSB_DLOAD but Odin doesn't recognize it at all.
The device itself stays cold. No screen. No indicator lights. No vibration.
I cannot boot into CWM or Download mode.
Any helpful ideas, or am I buggered on this one?
Thanks,
Shaiden

Probably won't work but did you try a battery pull? But judging from the info you gave you probably are bricked beyond repair . Your best bet is hope insurance (If you have insurance on the phone) will replace it.
Sent from my SCH-I535 using xda premium

shimp208 said:
Probably won't work but did you try a battery pull? But judging from the info you gave you probably are bricked beyond repair . Your best bet is hope insurance (If you have insurance on the phone) will replace it.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Sorry, forgot to mention that. I did indeed attempt the good old battery pull.
Contemplating trying a usb jig on it, but I'm none too hopeful at this point.

The jig is your only hope at this point.
Should it not work, you'll need to pay around 20 bucks in a phone repair shop (if any are around) to have the device JTAG'ed so it will go to Download mode again.
Make sure your Jig is "good". There are a lot of cheap jigs on Ebay which worked on the S1 and partially the S2 but no longer on the S3 since they
do not have the exact resistance needed to trigger the mode (301kOhm)
You could theoretically claim it to be a malfunctioning Kies upgrade (they seem to sometimes not only cause soft- but also hardbricks) but that would be fraud.

Might be a stupid Q on my part but is it a US/Canadian S3(dual core) version or the international(quad core) as if youve flashed a rom for the wrong version u have bricked it.
Shaiden said:
Hey gang,
Got my hands on a brand new S III yesterday and of course jumped straight to rooting it.
The root went fine and CWM was working beautifully. I copied the .zip file for Blackstar rom onto the internal SD card and rebooted into recovery. After running the data wipe/factory reset option as per usual, I used CWM Recovery to install the .zip I copied. It began to to it's thing and then encountered an error. This worried me for obvious reasons, so I factory reset it again and rebooted it with the command in recovery.
Which brings us to now:
The phone is completely non responsive. The computer recognizes it as QHSUSB_DLOAD but Odin doesn't recognize it at all.
The device itself stays cold. No screen. No indicator lights. No vibration.
I cannot boot into CWM or Download mode.
Any helpful ideas, or am I buggered on this one?
Thanks,
Shaiden
Click to expand...
Click to collapse

Shaiden said:
Hey gang,
Got my hands on a brand new S III yesterday and of course jumped straight to rooting it.
The root went fine and CWM was working beautifully. I copied the .zip file for Blackstar rom onto the internal SD card and rebooted into recovery. After running the data wipe/factory reset option as per usual, I used CWM Recovery to install the .zip I copied. It began to to it's thing and then encountered an error. This worried me for obvious reasons, so I factory reset it again and rebooted it with the command in recovery.
Which brings us to now:
The phone is completely non responsive. The computer recognizes it as QHSUSB_DLOAD but Odin doesn't recognize it at all.
The device itself stays cold. No screen. No indicator lights. No vibration.
I cannot boot into CWM or Download mode.
Any helpful ideas, or am I buggered on this one?
Thanks,
Shaiden
Click to expand...
Click to collapse
What's your model number? Maybe U flashed the wrong rom.
Sent from my GT-I9000(maybe I9300) using Tapatalk 2

SwiftSmoke said:
Might be a stupid Q on my part but is it a US/Canadian S3(dual core) version or the international(quad core) as if youve flashed a rom for the wrong version u have bricked it.
Click to expand...
Click to collapse
It is indeed the North American dual-core model.
And I may have done just that. I admittedly did't check to see which configuration the ROM was meant for.

Shaiden said:
It is indeed the North American dual-core model.
And I may have done just that. I admittedly did't check to see which configuration the ROM was meant for.
Click to expand...
Click to collapse
you should have taken more care in reading stuffs rather than flashing.

Coming from iOS, "brick" isn't really brick. It's just the user doesn't know what to do, but completely fixable.
Being new to Android, over a month in but stock. I didn't know you could literally "brick" a phone. Interesting.

Shaiden said:
It is indeed the North American dual-core model.
And I may have done just that. I admittedly did't check to see which configuration the ROM was meant for.
Click to expand...
Click to collapse
'QHSUSB_DLOAD' means CPU is Qualcom.. so is not international S3 and Blackstar is for international ... hence the BRICK... send back to Samsung...cook a story. All the Best.

Within North America rooting won't void your warranty but in other countries on the international market you do void it that's why I don't root. I don't know what story you will come up with to make it fly but hey best of luck to you sir.

Buy yourself this jig dongle,
http://item.mobileweb.ebay.com/viewitem?itemId=300738858103&index=2&nav=SEARCH&nid=76910404095
If doesn't work buy yourself a new phone...
Sent from my GT-I9300 using xda premium

Related

[Q] Help me to brick my SGSII!

Hey guys!
I need a little help, I want to hardbrick my phone(for warranty purposes since i have some issues...last owner overclocked it like hell... )
I actually have a plan to do it:
I am running a 4.1.1 JB rom and Siyah kernel...
so first I am going to reset the phone to its factory state(flash stock rom, kernel ect.).. and now here's where I need help..
I need a method to brick it, that is undetectable that I've done any changes to it...in one word, hardbrick not to boot up and stuff!
Thanks!
Sorry if I posted this in the wrong section, I'm reading the forums for a long time, but this is my first post on it!
I once went into CWM, mounts and storage and formatted everything... Worked for me. Well if by worked you mean hard bricked
Sent from my GT-I9100 using Tapatalk 2
DPluss said:
Hey guys!
I need a little help, I want to hardbrick my phone(for warranty purposes since i have some issues...last owner overclocked it like hell... )
I actually have a plan to do it:
I am running a 4.1.1 JB rom and Siyah kernel...
so first I am going to reset the phone to its factory state(flash stock rom, kernel ect.).. and now here's where I need help..
I need a method to brick it, that is undetectable that I've done any changes to it...in one word, hardbrick not to boot up and stuff!
Thanks!
Sorry if I posted this in the wrong section, I'm reading the forums for a long time, but this is my first post on it!
Click to expand...
Click to collapse
Easy, flash a stock 4.0.4 firmware and keep it on stock kernel.
then just boot into recovery and start wiping everything.
Dont know if this is undetectable though
Moving to Q&A, please post all future questions there.
Thanks
The-Hulk
Poroto said:
Easy, flash a stock 4.0.4 firmware and keep it on stock kernel.
then just boot into recovery and start wiping everything.
Dont know if this is undetectable though
Click to expand...
Click to collapse
But if I reflash the stock kernel, it will flash the stock recovery, or not?
The stock recovery has wiping options too?
I had a little research on other bricking topics(other phone brands) throught xda and most peoples advice was to flash corrupted files through Odin,
like a boot.img or a corrupted update.zip to prevent the phone from even getting into download mode, making it an excelent paperweight I think that is fully undetectable sinc they cant do anything with it, and I can then tell that it will not boot up, I did nothing to it, tested with another battery, never fell, never got liquid, it was in a case, it has not even a scratch on it I would not do this if it wasn't necessary...I'ts always overheating like hell(I really tried everything to prevent that), even on charger, this is my second battery, my touchcreen response is poor, the bottom buttons are also laggy...I just want replacement before it's too late...It might hold up longer but my warranty expires on 31. Oct.
Deleted.
I would try using a firmware not meant for your phone and pull the plug out half way through flashing it with odin.
Then hope it gets hot around the camera and wont come on.....lol
Jokesy said:
Let's be reasonable here.
1. If you are not the first owner of the phone, then you might not be lucky with warranty service.
2. What are the issues you are facing? Can you list them?
Click to expand...
Click to collapse
umm.. i'm the second owner, of course first, i will go and see my provider, and ask them about the warranty(will not bring the phone in first lol)!
Basicly the warranty sheet has no personal information, just the phone type, the IMEI, and the date when the other bought it!
The issues are, serious overheating around the camera area...it can never be interrupted, if the phone is on, it keeps overheating after about half an hour, I don't know what is the ideal temperature of a working device but after an hour I can't hold my phone without a thick case(or gloves lol)! It heavily affects the camera, focus has major issues, sometimes it says "can't connect to camera", touchscreen can be a little laggy when its hot...When I bought it from previous owner I didn't noticed it because on forums people kept complaining about heating, but then I realized that I was an idiot...I tried stock official roms, GB,CSI, and now JB, nothing changed!
DPluss said:
But if I reflash the stock kernel, it will flash the stock recovery, or not?
The stock recovery has wiping options too?
I had a little research on other bricking topics(other phone brands) throught xda and most peoples advice was to flash corrupted files through Odin,
like a boot.img or a corrupted update.zip to prevent the phone from even getting into download mode, making it an excelent paperweight I think that is fully undetectable sinc they cant do anything with it, and I can then tell that it will not boot up, I did nothing to it, tested with another battery, never fell, never got liquid, it was in a case, it has not even a scratch on it I would not do this if it wasn't necessary...I'ts always overheating like hell(I really tried everything to prevent that), even on charger, this is my second battery, my touchcreen response is poor, the bottom buttons are also laggy...I just want replacement before it's too late...It might hold up longer but my warranty expires on 31. Oct.
Click to expand...
Click to collapse
it only works if you have a faulty emmc chip
Rick Roll said:
it only works if you have a faulty emmc chip
Click to expand...
Click to collapse
How do I know that? My phone was first out in 31.10.2011.
DPluss said:
How do I know that? My phone was first out in 31.10.2011.
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check&hl=es
Deleted.
Thanks you very much!
Its says:
"Brick bug?
YES. Insane chip."
So if I revert everything to stock and then I start wiping stuff in recovery itt will hardbricked?
Can't it be even fixed in Download mode with Odin?
Jokesy said:
Ok.
very simple way to hard brick your phone.
Flash the wrong bootloader!
PS: first confirm that you can claim warranty service.
Click to expand...
Click to collapse
I will confirm it!
So for example if I flash another phones boot.img throught Odin than it's a full disaster that can never be repaired?
Thank you!
Siyah kernel 3.1rc6 lol
DPluss said:
Thanks you very much!
Its says:
"Brick bug?
YES. Insane chip."
So if I revert everything to stock and then I start wiping stuff in recovery itt will hardbricked?
Can't it be even fixed in Download mode with Odin?
Click to expand...
Click to collapse
Exactly, flash a stock 4.0.4 firmware and start wiping, not even a jtag service fixes that lol. or yeah, as jokesy said, flash a wrong bootloader
theunderling said:
Siyah kernel 3.1rc6 lol
Click to expand...
Click to collapse
Lol, yeah, S3 kernel, I think that should work... I really want to do something that can't be reversed
What do you think? If I flash it, it would still go to the first screen? The one that says "Samsung Galaxy S2", or no response for ever?
Poroto said:
Exactly, flash a stock 4.0.4 firmware and start wiping, not even a jtag service fixes that lol. or yeah, as jokesy said, flash a wrong bootloader
Click to expand...
Click to collapse
Thanks! I almost have all the info I need! Umm.. so if I wipe it's unreversable, and if I flash a wrong bootloader or kernel? Could Jtag service fix that?
Deleted.
Jokesy said:
boot.img as far as i know is the kernel.
1. you need to download bootloader.tar Galaxy NOte GT N7000 (or any other samsung phone) and flash as pda via odin
or
2. you can download Galaxy SII bootloader.tar here.
then remove your cable as soon as odin starts writing the bootloader.
Gameover!
Click to expand...
Click to collapse
Thanks, haha I think I will try to pull out the cable when the flashing start but first I will ask my provider about the warranty of course

[Q] Hard bricked two times need help

First let me put it out there that I have been rooting and installing roms for multiple phones with no issue ever.
I tried to install *TheCollective*AoCP - CP4.4 for i717 on my note and it hard bricked the first one I don't know why but it did. No biggie so I went through warranty and got a new one today. Heres my process (Assume I have samsung usb drivers already installed and battery is 100%)
Enable USB debugging
Used Odin3 v1.83
Used cwm-touch-i717-120414.tar.md5
Downloaded *TheCollective*AoCP - CP4.4 for i717
Downloaded gapps-jb-20120726-signed
Added both to SD card
Boot into Recovery
NANDroid backup
Wipe data/Factory reset
Wipe Dalvik cache
Format /system
Install ZIP From SD Card (RoM first then gapps)
Reboot.....wont turn on at all black screen nothing from phone
What am I doing wrong?
Someone please tell me.
Dont format /system. It's not necessary. I do everything you did. Except I Use TWRP... I dont see anything wrong with your process
See and on the first phone I didnt format the system and it bricked so I thought it was because I didnt format the system thats why I did it on my note
Edit: Being a broke college student I can't afford this mistake again. If anyone can help me (specific to this rom) that I'm doing wrong or what may be wrong with my phone that would be awesome.
I did everything right I looked through the rom thread well into 100 pages and nobody has had any issues.
I've never hard bricked any other phone before and I had my original note on another rom as well.
It was only until I used that rom did it hard brick or as far as I know it hard bricked.
Can anybody respond to give me a hint as to what happened?
Post a picture of your note. I want to "see" this device.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Fact of the matter is;
The packaged rom you refer to dose not contain bootloaders. So its really quiet unlikely its hard bricked unless you flash it to a device its not ment for.
The recovery in question is the one I use as well so that also should not cause an issue.
Have you tried a jig? To get back into download mode?
I really want to see this device you own I have a feeling you may be flashing the wrong device files.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Johnsondr80 said:
Fact of the matter is;
The packaged rom you refer to dose not contain bootloaders. So its really quiet unlikely its hard bricked unless you flash it to a device its not ment for.
The recovery in question is the one I use as well so that also should not cause an issue.
Have you tried a jig? To get back into download mode?
I really want to see this device you own I have a feeling you may be flashing the wrong device files.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Click to expand...
Click to collapse
I do not own a jig right now as I lost mine.
heres pic
http://imgur.com/DkseY
Sorry for bad writing...its late
I know that the device is not booting at all. no vibrate, no sound just a black screen.
I've heard amazing things about the rom hence why I wanna try it. I don't mean any disrespect to any of the rom developers.
I thank you for even responding! I'm pretty sure it's on my end I just wanna find out what.
Dark_lupus said:
I know that the device is not booting at all. no vibrate, no sound just a black screen.
I've heard amazing things about the rom hence why I wanna try it. I don't mean any disrespect to any of the rom developers.
I thank you for even responding! I'm pretty sure it's on my end I just wanna find out what.
Click to expand...
Click to collapse
example of a jig(s): http://www.cellularfactory.com/det.jsp?d=57293&c=658122
http://www.youtube.com/watch?v=5G5sHPPnins
i dont know if this is the one that will work for you but its what you need, if you are hard bricked.. did you try pulling batteries and getting into download mode by holding volume down and power and plugging in usb (all without the battery in device) ?
dont know if it will work but give it a shot.
mejori said:
example of a jig(s): http://www.cellularfactory.com/det.jsp?d=57293&c=658122
http://www.youtube.com/watch?v=5G5sHPPnins
i dont know if this is the one that will work for you but its what you need, if you are hard bricked.. did you try pulling batteries and getting into download mode by holding volume down and power and plugging in usb (all without the battery in device) ?
dont know if it will work but give it a shot.
Click to expand...
Click to collapse
Tried it that way when connected to my computer just kept giving me a you need to format G: etc etc over and over again (multiple windows) until i unplugged it.
Dark_lupus said:
Tried it that way when connected to my computer just kept giving me a you need to format G: etc etc over and over again (multiple windows) until i unplugged it.
Click to expand...
Click to collapse
This statement made me think of something else:
1: What cable did you use?
2: Were both phones bricked while flashing from the same PC?
I ask that, because if your phone is unplugged part way through a bootloader being installed... But you don't have to unplug it, it could be a faulty USB cable or bad PC drivers :/
Ive rooted and romd a ton of devices myself never ever bricked one until I came across this one... i own a jig and no recovery no boot whatsoever my only conclusion as to why this happened to me.. is a while back people were reporting a few certain phones had a "brick bug" there's an actual app to run and check to give you some peace of mind.
Sent from my SAMSUNG-SGH-I717 using xda premium
Snarksneeze said:
This statement made me think of something else:
1: What cable did you use?
2: Were both phones bricked while flashing from the same PC?
I ask that, because if your phone is unplugged part way through a bootloader being installed... But you don't have to unplug it, it could be a faulty USB cable or bad PC drivers :/
Click to expand...
Click to collapse
Used the cable that came with both phones, the old cable for the old phone and the new cable for the new phone
both phones used the same pc.(never had any issue before) Both phones were 100% battery and unplugged while installing the roms though\
Only until after installing the roms did the phone not come back on. (meaning after installing CWM I restarted the phone and it started up fine issue only happened after I installed the rom)
Brick bugs?
So squeezed my way into a replacement.
Scared to try another rom but I think that I will try another one and see if it works. My phone will be here tuesday.
Should I use another computer to do load CWM? Throw some advice as I'm pretty sure this is the last time I can get another phone for a while
Hi... I hard bricked my at&t sgh-i717 in the same way... same rom... same format system... and the phone would not start up, not recovery mode or download mode. I built a jig, that work correctly with the samsung S2, but on the Note no effect :crying:
---------- Post added at 06:14 PM ---------- Previous post was at 06:09 PM ----------
Can I do something to revive my Note?
Dark_lupus said:
So squeezed my way into a replacement.
Scared to try another rom but I think that I will try another one and see if it works. My phone will be here tuesday.
Should I use another computer to do load CWM? Throw some advice as I'm pretty sure this is the last time I can get another phone for a while
Click to expand...
Click to collapse
I bricked a phone and soft bricked a phone and brought it back to normal just recently - The problem that i have is that i actually provide a flashing service to my customers and the guy i had dealt with used samsung kies and downloaded ICS which brings many issues to the table when flashing the easy way. Rather than mess around i decided to go about things the easy way below;
--Enter ODIN mode on i717, Download & Flash the STock Gingerbread 2.3.3 AT&T Rom (which is linked in Da_g's Thread) using ODIN on ur PC i(500MB zip)
--install the DA_G OC root kernel
--then install TWRP.zip via Odin or flash CWM
--then Download and flash Jellbean ROM of your choice / GAPPs. (after you wipe cache x3 and dalvik x3
Make sure you have all the samsung galaxy note drivers installed on your computer... if you are unsure REINSTALL them. Trust me
BigBison420 said:
I bricked a phone and soft bricked a phone and brought it back to normal just recently - The problem that i have is that i actually provide a flashing service to my customers and the guy i had dealt with used samsung kies and downloaded ICS which brings many issues to the table when flashing the easy way. Rather than mess around i decided to go about things the easy way below;
--Enter ODIN mode on i717, Download & Flash the STock Gingerbread 2.3.3 AT&T Rom (which is linked in Da_g's Thread) using ODIN on ur PC i(500MB zip)
--install the DA_G OC root kernel
--then install TWRP.zip via Odin or flash CWM
--then Download and flash Jellbean ROM of your choice / GAPPs. (after you wipe cache x3 and dalvik x3
Make sure you have all the samsung galaxy note drivers installed on your computer... if you are unsure REINSTALL them. Trust me
Click to expand...
Click to collapse
Hi... my note would not power on... so no recovery/download mode... When i plug it to my pc, it's recognized like "qualcom device" or something similar... kies is up to date and the drivers are ok... but Odin is useless :crying:
First rule.
Flash packages built for your device.
Second rule.
Follow install instruction.
If your having problems its one of those that you failed at.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Hi,
First I would like to say thanks for all the hard and awesome work.
I'm a noob/longime lurker, and don't have enough posts to be able to post on the thread itself, hence the PM.
I just wanted to share a suggestion if you can change your naming convention of your download files on the mirror site (or in general).
I had trouble downloading from the main link which kept timing out on me. So I used the dev-host mirror link, which has 4 links, but ended up downloading the wrong ROM. I should've gotten the i747 one (for AT&T) but instead got the i727 one, as I mistakenly thought these were just all different mirror links to the same file.
Long story short, this ended up bricking my phone, which is now getting exchanged at AT&T.
I know this is completely due to my noobness, and lesson learned,
but my suggestion is if you can change the naming convention of the files, (especially on the download mirror) or somehow make the difference in the files more obvious than just the 1 character digit difference located in the middle of the file name.
This may help other soul avoid making the same mistake I did.
Click to expand...
Click to collapse
Please read the zip file name in its entirety.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Johnsondr80 said:
First rule.
Flash packages built for your device.
Second rule.
Follow install instruction.
If your having problems its one of those that you failed at.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Click to expand...
Click to collapse
Hi Johnsondr80... i flashed the right rom... for the right phone... I have an at&t shg-i717, and i717 was written on the name of the file i flashed... i'm only asking if you could help me to get back my phone... nothing more brother

Cant't get my S2 to start. No image AT ALL

I had just flashed my phone to CF-Root 5.6. It all went very well, took about 8 seconds, and it rebootet normally.
Then my plan was to update to JELLYBAM - v5.1.0.
I copied the .zip file into the SD card, and entered recovery mode.
I Wiped the data/cache, and installed it.
In the middle of the installation, all of sudden, the phone went black.
I tried to turn it on, put out and in the battery, enter recovery mode and download mode and connect it to the pc. Nothing worked.
I can't get any picture on the phone anymore, and i really need help with this. I have tried everything that i know about.. :crying:
How do i fix this??
rotweb 1-2
Simmyen said:
I had just flashed my phone to CF-Root 5.6. It all went very well, took about 8 seconds, and it rebootet normally.
Then my plan was to update to JELLYBAM - v5.1.0.
I copied the .zip file into the SD card, and entered recovery mode.
I Wiped the data/cache, and installed it.
In the middle of the installation, all of sudden, the phone went black.
I tried to turn it on, put out and in the battery, enter recovery mode and download mode and connect it to the pc. Nothing worked.
I can't get any picture on the phone anymore, and i really need help with this. I have tried everything that i know about.. :crying:
How do i fix this??
Click to expand...
Click to collapse
Hey the exact same thing happened to me yesterday, and I was also installing JellyBam. I followed the exact same steps as you and my phone also went black during installation and is now hard bricked and needs to be JTAG repaired in order to work.
Looks like you guys have encountered phonus brickedus
This happened to me too, yesterday. There are lots of threads that discuss these things. If you cant access anything you can try a jig. (look it up)
I, however, tried jig and JTAG but no solutions found so i sent it to service center. Now i just pray to god that they don't find out that my phone's rooted (which makes my warranty vioded).
As far as my expertise says, if you cant find a Jig or JTAG solution, send it to service. When my phone arrives (if it does) i can tell you if they knew that i had rooted or not.
Regards.
PS. Did you follow it's flashing steps carefully?
WardenBerret said:
Looks like you guys have encountered phonus brickedus
This happened to me too, yesterday. There are lots of threads that discuss these things. If you cant access anything you can try a jig. (look it up)
I, however, tried jig and JTAG but no solutions found so i sent it to service center. Now i just pray to god that they don't find out that my phone's rooted (which makes my warranty vioded).
As far as my expertise says, if you cant find a Jig or JTAG solution, send it to service. When my phone arrives (if it does) i can tell you if they knew that i had rooted or not.
Regards.
PS. Did you follow it's flashing steps carefully?
Click to expand...
Click to collapse
If Jtag couldn't bring it back to life, they won't know, don't worry
WardenBerret said:
PS. Did you follow it's flashing steps carefully?
Click to expand...
Click to collapse
Yes. I followed them very carefully. Did everything that i was supposed to do..
Could it be a bug in the kernel?
Simmyen said:
Yes. I followed them very carefully. Did everything that i was supposed to do..
Could it be a bug in the kernel?
Click to expand...
Click to collapse
What ROM were you on? 4.0.4?
gastonw said:
What ROM were you on? 4.0.4?
Click to expand...
Click to collapse
Yep... the official 4.0.4
gastonw said:
What ROM were you on? 4.0.4?
Click to expand...
Click to collapse
What diff does that make? He was on custom kernel not stock.
Did you guys have at least 55% battery? On some occasions flashing roms can use allot of processing power and drain unusual amounts of battery. For example sometimes I have been on full battery, flashed a rom and its used 40% so if you guys was on low battery it could have died and screwed up your rom, kernel or worse your bootloader resulting in brick.
Sure that custom kernel was safe atheist?
Sounds like emmc to me.....
Sent from my GT-I9100 using xda app-developers app
rsr1 said:
Hey the exact same thing happened to me yesterday, and I was also installing JellyBam. I followed the exact same steps as you and my phone also went black during installation and is now hard bricked and needs to be JTAG repaired in order to work.
Click to expand...
Click to collapse
Exactly the same with me i9100. how can we make it?
Simmyen said:
I had just flashed my phone to CF-Root 5.6. It all went very well, took about 8 seconds, and it rebootet normally.
Then my plan was to update to JELLYBAM - v5.1.0.
I copied the .zip file into the SD card, and entered recovery mode.
I Wiped the data/cache, and installed it.
In the middle of the installation, all of sudden, the phone went black.
I tried to turn it on, put out and in the battery, enter recovery mode and download mode and connect it to the pc. Nothing worked.
I can't get any picture on the phone anymore, and i really need help with this. I have tried everything that i know about.. :crying:
How do i fix this??
Click to expand...
Click to collapse
I also don't think it was the bug as the phone died while flashing the rom, not during the wipe. Perhaps it was a bad download or a link that took users to a rom for the wrong model of phone. Hopefully every user effected will get there phone repaired.
Sent from my GT-I9100 using xda premium

!HELP! Unroot SCH I545 w/ broken USB port

The USB port for my S4 recently stopped working. I called verizon for a replacement. Unfortunately, I am unable to unroot my S4 because it will not connect to ODIN. I could not find a mobile ODIN app compatible with the sch-i545. Does anybody have any suggestions how I could unroot my device. All and any help is greatly appreciated!!!!
I have TWRP and am running the Jelly "Beans" ROM
Mr Frog said:
The USB port for my S4 recently stopped working. I called verizon for a replacement. Unfortunately, I am unable to unroot my S4 because it will not connect to ODIN. I could not find a mobile ODIN app compatible with the sch-i545. Does anybody have any suggestions how I could unroot my device. All and any help is greatly appreciated!!!!
Click to expand...
Click to collapse
Did you try to do the factory reset?
Dolphlungegrin said:
Did you try to do the factory reset?
Click to expand...
Click to collapse
I don't believe that would work. I am rooted running a custom stock rom. I'll include that in the original post
not sure but maybe triangle away and try this http://www.youtube.com/watch?v=dBPUdazXh6c if you cant clear the bianary counter it will still say modified .. didnt realize mobile odin didnt work with sch-i545
Mr Frog said:
I don't believe that would work. I am rooted running a custom stock rom. I'll include that in the original post
Click to expand...
Click to collapse
What ROM? That will work if you still have access to a reset method inside the UI. If you have a ROM on there you must be running MDK, can't you just wipe the data off the phone with CWM or TWRP? The Root binary should be un-installed when you boot back up. Just delete the SuperSu app and you should be home free.
SO_dank said:
not sure but maybe triangle away and try this http://www.youtube.com/watch?v=dBPUdazXh6c if you cant clear the bianary counter it will still say modified .. didnt realize mobile odin didnt work with sch-i545
Click to expand...
Click to collapse
I have used triangle away successfully and it did reset the counter.
Dolphlungegrin said:
What ROM? That will work if you still have access to a reset method inside the UI. If you have a ROM on there you must be running MDK, can't you just wipe the data off the phone with CWM or TWRP? The Root binary should be un-installed when you boot back up. Just delete the SuperSu app and you should be home free.
Click to expand...
Click to collapse
Please correct me if im wrong or misunderstanding what you are saying but i dont believe that would work. If I boot into TWRP and clear all the data I don't believe there will be anything for the phone to boot into. There wont be a rom for it to boot into and it would still have a custom recovery instead of the stock one.
Mr Frog said:
I have used triangle away successfully and it did reset the counter.
Please correct me if im wrong or misunderstanding what you are saying but i dont believe that would work. If I boot into TWRP and clear all the data I don't believe there will be anything for the phone to boot into. There wont be a rom for it to boot into and it would still have a custom recovery instead of the stock one.
Click to expand...
Click to collapse
After the data wipe you could reinstall the original ROM couldn't you? Long as you have the file on your microsd card. That would probably just reflash your ROM though, it may not erase the binaries. Damn. Well I'm sure there is a way to do it like this. It's just been a while since I've messed around with the TWRP recovery mode.
Do you have cwm on the phone. . If you do your sol. You can't wipe that without an odin to my knowledge. . But if your just rooted.. triangle away. .undo root. Remove su factory reset. . Should be clear. .
Dolphlungegrin said:
After the data wipe you could reinstall the original ROM couldn't you? Long as you have the file on your microsd card. That would probably just reflash your ROM though, it may not erase the binaries. Damn. Well I'm sure there is a way to do it like this. It's just been a while since I've messed around with the TWRP recovery mode.
Click to expand...
Click to collapse
Hey so I'm in a similar boat - I have a Verizon S4 with the ME7 firmware that the usb port will no longer connect and won't charge unless the phone is off (and only when it's plugged in to a computer, not a wall). It was rooted so I followed the instructions above to unroot it.
But here's where I think I'm in trouble - I had loaded the TWRP bootloader before I found out it wouldn't work with the ME7 firmware, and never bothered flashing the phone back (stupid, I know). Is there no way to flash back to stock rom via the SD card? Right now when I go into recovery mode, it just goes to the "Downloading" screen. Does anybody know a way I can get TWRP off?
Sorry hope I'm not thread-jacking but this is the most relevant thread I've found to ask this in.
Sure it's not the cable.. if your in a position where you need to stock odin me7 you need usb.. Make sure it's not the cable although it could be phone usb is screwed due to your phone error.. you have insurance??
bretbretterson said:
Hey so I'm in a similar boat - I have a Verizon S4 with the ME7 firmware that the usb port will no longer connect and won't charge unless the phone is off (and only when it's plugged in to a computer, not a wall). It was rooted so I followed the instructions above to unroot it.
But here's where I think I'm in trouble - I had loaded the TWRP bootloader before I found out it wouldn't work with the ME7 firmware, and never bothered flashing the phone back (stupid, I know). Is there no way to flash back to stock rom via the SD card? Right now when I go into recovery mode, it just goes to the "Downloading" screen. Does anybody know a way I can get TWRP off?
Sorry hope I'm not thread-jacking but this is the most relevant thread I've found to ask this in.
Click to expand...
Click to collapse
The only way I know to solve your problem is to reflash ME7 using ODIN. If you have the ME7 firmware already you can't use the TWRP or CWM recovery partitions at all. With out those operating your stuck using ODIN and your USB port. Have you tried another cable?
Dolphlungegrin said:
The only way I know to solve your problem is to reflash ME7 using ODIN. If you have the ME7 firmware already you can't use the TWRP or CWM recovery partitions at all. With out those operating your stuck using ODIN and your USB port. Have you tried another cable?
Click to expand...
Click to collapse
Yeah I've tried a couple different cables, a couple different pc's, a couple different chargers. It will only charge when it's off, connected to a pc. When turning it on "usb cable connected" flashes up top, even though it's not. When it is connected and turned on and below 15%, it tells you to connect to a power source. I searched this and low and behold, several other s4 owners are having the same issue. It started happening two nights ago after I didn't get the phone on a charger before it died, then I charged it overnight - next morning it wouldn't start up. I don't think it has anything to do with having the twrp bootloader though, because it had been on there a couple weeks and restarted more than once with no issues.
If anyone knows how to fix the usb thing, I've got...lets say a $50 reward up for grabs. Not much but it's all I can afford to not void my warranty.
bretbretterson said:
Yeah I've tried a couple different cables, a couple different pc's, a couple different chargers. It will only charge when it's off, connected to a pc. When turning it on "usb cable connected" flashes up top, even though it's not. When it is connected and turned on and below 15%, it tells you to connect to a power source. I searched this and low and behold, several other s4 owners are having the same issue. It started happening two nights ago after I didn't get the phone on a charger before it died, then I charged it overnight - next morning it wouldn't start up. I don't think it has anything to do with having the twrp bootloader though, because it had been on there a couple weeks and restarted more than once with no issues.
If anyone knows how to fix the usb thing, I've got...lets say a $50 reward up for grabs. Not much but it's all I can afford to not void my warranty.
Click to expand...
Click to collapse
The problem with the custom recovery partition you have on there is that it prevents you from doing a factory reset in the settings menu. At least as far as I'm aware. If mobile ODIN worked on our phones I would say download that and re-flash with the tar file on your msd card. SafeStrap might be a way to give this a try. I can't link to another forum in here but I would look into that.
Maybe replace the usb port yourself
https://www.youtube.com/watch?v=F5e3r_2N15c
Dolphlungegrin said:
The problem with the custom recovery partition you have on there is that it prevents you from doing a factory reset in the settings menu. At least as far as I'm aware. If mobile ODIN worked on our phones I would say download that and re-flash with the tar file on your msd card. SafeStrap might be a way to give this a try. I can't link to another forum in here but I would look into that.
Click to expand...
Click to collapse
Well I'm not exactly sure what did it, but I used a small flathead screwdriver to bend the connector inside the usb port up a little, as I read that can be an issue with these phones, and used an old cable from a blackberry, and one of the two let me get it connected to the pc and flashed back to the stock rom via ODIN. Still won't charge with any combination of wall chargers/cables, so I'm going to take it in to Verizon. But it's a huge sigh of relief knowing that they won't be able to claim I damaged it by putting a custom bootloader on. Thanks for the input. Hope OP gets his problems sorted also.
bretbretterson said:
But here's where I think I'm in trouble - I had loaded the TWRP bootloader before I found out it wouldn't work with the ME7 firmware, and never bothered flashing the phone back (stupid, I know). Is there no way to flash back to stock rom via the SD card? Right now when I go into recovery mode, it just goes to the "Downloading" screen. Does anybody know a way I can get TWRP off?
.
Click to expand...
Click to collapse
If you were on me7 you shouldn't have been able to get twrp as your recovery. So if you are on me7 then your recovery is still stock even if you tried to flash twrp.
Sent from my VZW Galaxy S4 using Tapatalk 4
nativi said:
If you were on me7 you shouldn't have been able to get twrp as your recovery. So if you are on me7 then your recovery is still stock even if you tried to flash twrp.
Sent from my VZW Galaxy S4 using Tapatalk 4
Click to expand...
Click to collapse
That may have been true, I might have been trying the wrong buttons to get to recovery. Still learning some stuff. But the twrp loader definitely changed the splash and download screen enough that I needed to get it off so that no red flags will be thrown when I take it in to Verizon to have them look at it.
Thanks for everybody's help! I managed to connect to ODIN by pushing the usb in different ways until I got a connection and sent it back to Verizon completely stock
Sent from my SCH-I545 using xda app-developers app

[Q] In doghouse - Bricked my wife's i9205

I bought her an unlocked i9205 back in December. It was rooted already. I put SU and TWRP on it and did a backup of it. Well she kinda trashed it so I did a TWRP restore which ended with an error. Now it just boots to the Samsung logo. Do I need to load a new ROM now? I'm hoping I can find something to just put on an SD card and flash with TWRP. Any help is good. I have a PC setup with drivers for it. PDANET, ADB, etc.. No Odin though.
- Joe
JoeLansing said:
I bought her an unlocked i9205 back in December. It was rooted already. I put SU and TWRP on it and did a backup of it. Well she kinda trashed it so I did a TWRP restore which ended with an error. Now it just boots to the Samsung logo. Do I need to load a new ROM now? I'm hoping I can find something to just put on an SD card and flash with TWRP. Any help is good. I have a PC setup with drivers for it. PDANET, ADB, etc.. No Odin though.
- Joe
Click to expand...
Click to collapse
if you can get into recovery. try installing a new ROM
bnb25 said:
if you can get into recovery. try installing a new ROM
Click to expand...
Click to collapse
I can get into TWRP recovery. Will any ROM work with that? Can you recommend any ROMs? The stock one was fine but it was so full of Samsung bloat it really didn't have much available RAM left of it's 1.5GB after boot. I guess I don't care as long as it's stable and works so I can get out of the doghouse...LOL
- Joe
JoeLansing said:
I can get into TWRP recovery. Will any ROM work with that? Cahttp://forum.xda-developers.com/showthread.php?t=2608110 you recommend any ROMs? The stock one was fine but it was so full of Samsung bloat it really didn't have much available RAM left of it's 1.5GB after boot. I guess I don't care as long as it's stable and works so I can get out of the doghouse...LOL
- Joe
Click to expand...
Click to collapse
Try megafire mj2 v3x her3 in xda, it is stock with all the bloatware removed. Its is completely lag free.
JoeLansing said:
I can get into TWRP recovery. Will any ROM work with that? Can you recommend any ROMs? The stock one was fine but it was so full of Samsung bloat it really didn't have much available RAM left of it's 1.5GB after boot. I guess I don't care as long as it's stable and works so I can get out of the doghouse...LOL
- Joe
Click to expand...
Click to collapse
Grab Odin and flash stock ROM
*S.O.F.A*2SHAYNEZ*K.C.C.O*
Thanks guys. I'm trying a MegaFireMj2V3 just cuz I already downloaded it. Stock kinda sucked. I'd look and she'd have 3 apps running with low memory warnings. It was rooted and I'd uninstall a lot of bloat, but somehow it would auto update all the bloat right back within minutes. I'll go back to stock if needed but I want to try something de-crapped first.
- Joe
It's worse now.
Ok. Flashing MegaFireMj2V3 was a fail. It seems as if the system partition always fails. So I got Odin and a stock ROM. That failed also, and now I just have a couple of little red lines telling me to use Kies Recovery or something. And I can't get Kies to connect to it. My PC sees it. Samsung USB drivers install. Kies sees it plugged in but just lays there saying CONNECTING. I paid like $400 for this turkey for my wife for Christmas and now she's yelling at me that I blew it up.. I guess I can keep trying Kies but it's looking fail so far. This really stinks. I bought it on Amazon. It's supposed to have a 2 year warranty. It's Unlocked International Version with Warranty. But I don't know what country?
- Joe
JoeLansing said:
Thanks guys. I'm trying a MegaFireMj2V3 just cuz I already downloaded it. Stock kinda sucked. I'd look and she'd have 3 apps running with low memory warnings. It was rooted and I'd uninstall a lot of bloat, but somehow it would auto update all the bloat right back within minutes. I'll go back to stock if needed but I want to try something de-crapped first.
- Joe
Click to expand...
Click to collapse
JoeLansing said:
Ok. Flashing MegaFireMj2V3 was a fail. It seems as if the system partition always fails. So I got Odin and a stock ROM. That failed also, and now I just have a couple of little red lines telling me to use Kies Recovery or something. And I can't get Kies to connect to it. My PC sees it. Samsung USB drivers install. Kies sees it plugged in but just lays there saying CONNECTING. I paid like $400 for this turkey for my wife for Christmas and now she's yelling at me that I blew it up.. I guess I can keep trying Kies but it's looking fail so far. This really stinks. I bought it on Amazon. It's supposed to have a 2 year warranty. It's Unlocked International Version with Warranty. But I don't know what country?
- Joe
Click to expand...
Click to collapse
I you have the twpr try to change the recovery to the latest one.....try philz touch recovery
I think u have an old recovery
Sent from my GT-I9205 using xda app-developers app
shazzl said:
I you have the twpr try to change the recovery to the latest one.....try philz touch recovery
I think u have an old recovery
Sent from my GT-I9205 using xda app-developers app
Click to expand...
Click to collapse
I don't have any recovery anymore. It boots to a small failed update message. It's toast unless I can get Kies to work somehow.
- Joe
there is a way to use Kies to get Stock on there.. It involves typing in the words of your model or something like that./
maybe someone here can remember better than I.
On the Note, Ive seen it alot. there is a certian way that you have to type in the make and model and it will stock-ize you.
That is "IF" you can get it to connect to Kies..
I'll suggest you use a different USB cable..
Some will and some wont connect.....
good luck
Why don't you to flash a stock rom with Odin, I think you have dounload mode (as you don't have custom recovery it is the only way) ?
Search YOUR rom on sammobile, or the same level (not possible to doungrade you shall have more problem ! )
Lol this also happened to me but to recover, since you now only have download mode, connect it to Odin on your PC and find a brand new firmware. Try the latest versions because that's your best shot of recovering it. It doesn't matter what region you pick as long as that the model number is the same. Do note however that if you fail the flash KNOX will trip up and you will void the warranty. If it doesn't fail, it should boot up to the Samsung logo. If it still bootloops, go into recovery (since it should be there now), and wipe everything. Then your phone should boot up nicely.
Note: New firmware contains KNOX so rooting and installing custom recovery is now dangerous.
Sent from my GT-I9200 using Tapatalk

Categories

Resources