Develop Bugs

[Q] Possible brick? Any ideas?

Hey guys, I think I screwed up here and I'm wondering if anyone else has had this problem:
Basically, I had a rooted E4G Touch with a custom ROM installed. I went to install ANOTHER custom ROM THROUGH ODIN, as this previous ROM (I believe it was a Calkulin variant) did NOT have CWM recovery. During the ODIN process, something went wrong, and my computer/ODIN...basically, everything froze up while doing the MODEM portion. NOW I can't do anything.
- CWM was able to install on the thing...but it does not recognize my external SD card now. Every time I try to mount it, I get a "Error mounting /emmc".
- I'm still able to get into download mode on the phone, however the phone is not recognized on any computer I've tried. I've attempted multiple computers/USB cords and nothing picks it up.
I'm running out of ideas here. I picked up a USB jig that should be here soon, so I'm going to try that and reset the counter....which leads me to my next question: If I use that, can I take the thing back to Sprint and get a replacement? I have the insurance plan and everything, so if they won't take it back because of the custom software I guess I could always smash it or something...
Any help would be appreciated!

munson11 said:
Hey guys, I think I screwed up here and I'm wondering if anyone else has had this problem:
Basically, I had a rooted E4G Touch with a custom ROM installed. I went to install ANOTHER custom ROM THROUGH ODIN, as this previous ROM (I believe it was a Calkulin variant) did NOT have CWM recovery. During the ODIN process, something went wrong, and my computer/ODIN...basically, everything froze up while doing the MODEM portion. NOW I can't do anything.
- CWM was able to install on the thing...but it does not recognize my external SD card now. Every time I try to mount it, I get a "Error mounting /emmc".
- I'm still able to get into download mode on the phone, however the phone is not recognized on any computer I've tried. I've attempted multiple computers/USB cords and nothing picks it up.
I'm running out of ideas here. I picked up a USB jig that should be here soon, so I'm going to try that and reset the counter....which leads me to my next question: If I use that, can I take the thing back to Sprint and get a replacement? I have the insurance plan and everything, so if they won't take it back because of the custom software I guess I could always smash it or something...
Any help would be appreciated!
Click to expand...
Click to collapse
The ROM you flashed through ODIN was for this phone, right?
What custom ROM are you referring to that was available through ODIN?

assuming you flashed the right ROM, start with the basics..if you can get into download mode then try a simple reboot of your computer. Sometimes Odin won't recognize after it has been run
Sent from my SPH-D710 using xda premium

barnacles10 said:
The ROM you flashed through ODIN was for this phone, right?
What custom ROM are you referring to that was available through ODIN?
Click to expand...
Click to collapse
It was the CyanogenMod 9 rom that is out there right now. IN the post (I'm having trouble finding it as I'm not at that computer right now) they had an ODIN variation for people such as myself, where you were to flash that and then go back through to update it to the latest version.
JohnCorleone said:
assuming you flashed the right ROM, start with the basics..if you can get into download mode then try a simple reboot of your computer. Sometimes Odin won't recognize after it has been run
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I attempted this as well Went through and rebooted the computer with the phone plugged in. Rebooted with it not plugged in. Plugged the phone in with ODIN on the screen and started it up. Started it up unplugged, went into download mode on the phone, and then plugged it in. Still nothing.
And I just realized I posted this in General and not Q&A...and chance I could get this moved since I am clearly out of my mind right now?

munson11 said:
It was the CyanogenMod 9 rom that is out there right now. IN the post (I'm having trouble finding it as I'm not at that computer right now) they had an ODIN variation for people such as myself, where you were to flash that and then go back through to update it to the latest version.
Click to expand...
Click to collapse
The only odin component involved with flashing CM9 is flashing a gb kernel with a CWM recovery. I haven't seen a cm9 tar, this is why I'm confused. Finding out exactly what you flashed will help in understanding what the problem is.
To flash cm9 you need to odin a gb cwm kernel and then boot to recovery and install cm9. However, that's not a tar, its an update.zip.

barnacles10 said:
The only odin component involved with flashing CM9 is flashing a gb kernel with a CWM recovery. I haven't seen a cm9 tar, this is why I'm confused. Finding out exactly what you flashed will help in understanding what the problem is.
To flash cm9 you need to odin a gb cwm kernel and then boot to recovery and install cm9. However, that's not a tar, its an update.zip.
Click to expand...
Click to collapse
Yeah it was definitely a tar.md5 file, which leads me to believe I was incredibly dumb and possibly flashed a ROM for a different model phone. I'm having difficulty finding the post now which is very strange. This could be one of those moments where I take a good hard look in the mirror and figure out just what the heck I was thinking.
I'll keep looking for what exactly I did wrong, but in the mean time is there anything else I could attempt or look for short of attempting that USB jig and making a trip to Sprint? I'm feeling like a huge idiot right now. I've done this how many times now and when I finally make a mistake, it turns out to be huge.

munson11 said:
It was the CyanogenMod 9 rom that is out there right now. IN the post (I'm having trouble finding it as I'm not at that computer right now) they had an ODIN variation for people such as myself, where you were to flash that and then go back through to update it to the latest version.
I attempted this as well Went through and rebooted the computer with the phone plugged in. Rebooted with it not plugged in. Plugged the phone in with ODIN on the screen and started it up. Started it up unplugged, went into download mode on the phone, and then plugged it in. Still nothing.
And I just realized I posted this in General and not Q&A...and chance I could get this moved since I am clearly out of my mind right now?
Click to expand...
Click to collapse
Maybe you should post the link to exactly what you were flashing...

http://www.addictivetips.com/mobile/cyanogenmod-9-galaxy-s-ii-download/
Please tell me this isnt what you flashed.
Sent from my SPH-D710 using xda premium

munson11 said:
Yeah it was definitely a tar.md5 file, which leads me to believe I was incredibly dumb and possibly flashed a ROM for a different model phone. I'm having difficulty finding the post now which is very strange. This could be one of those moments where I take a good hard look in the mirror and figure out just what the heck I was thinking.
I'll keep looking for what exactly I did wrong, but in the mean time is there anything else I could attempt or look for short of attempting that USB jig and making a trip to Sprint? I'm feeling like a huge idiot right now. I've done this how many times now and when I finally make a mistake, it turns out to be huge.
Click to expand...
Click to collapse
Well ultimately you can try uninstalling / reinstalling drivers. But you say this issue exists across multiple pcs so that likely isn't it.
You can try another cable and see if you have any success with that.
Other then that, it kinda really depends what is in that tar you flashed. Once you find it, post the link, and that will help troubleshoot your issue.

playya said:
Maybe you should post the link to exactly what you were flashing...
Click to expand...
Click to collapse
lballer69 said:
http://www.addictivetips.com/mobile/cyanogenmod-9-galaxy-s-ii-download/
Please tell me this isnt what you flashed.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Haha I am a freaking idiot. How in the heck did I manage to do this...I definitely flashed this: http://forum.xda-developers.com/showthread.php?t=1419102
I do not know what was going through my head last night...but it was not any sort of smart thoughts. A rope and a sturdy tree are what I require at this point, correct?
Whatever insults you guys would like to throw at me, I will take. I clearly deserve them :'(

munson11 said:
Haha I am a freaking idiot. How in the heck did I manage to do this...I definitely flashed this: http://forum.xda-developers.com/showthread.php?t=1419102
I do not know what was going through my head last night...but it was not any sort of smart thoughts. A rope and a sturdy tree are what I require at this point, correct?
Whatever insults you guys would like to throw at me, I will take. I clearly deserve them :'(
Click to expand...
Click to collapse
Did you flash the bootloader from that device? ie did your steps include this? \/
Make sure you're running ICS bootloaders lower than LPH: Download (flash as PDA with odin or extract and $ sudo heimdall flash --primary-boot boot.bin --secondary-boot Sbl.bin)
Click to expand...
Click to collapse

barnacles10 said:
Did you flash the bootloader from that device? ie did your steps include this? \/
Click to expand...
Click to collapse
Negative, I started right at the "Using the noob-proof ODIN method:". It said noob-proof and I decided that would be the easiest. It turns out it is very easy...if you're flashing to the correct phone Plus, I'd used ODIN before and felt comfortable with it.

Ha ha that's the first one for this method......look up jtag they may fix it for u if u don't have USB .... About 60 with shipping
Sent from my SPH-D710 using Tapatalk 2 Beta-5

munson11 said:
Negative, I started right at the "Using the noob-proof ODIN method:". It said noob-proof and I decided that would be the easiest. It turns out it is very easy...if you're flashing to the correct phone Plus, I'd used ODIN before and felt comfortable with it.
Click to expand...
Click to collapse
I just downloaded the tar to have a look at whats included.
After flashing this you'll have a bootloader for the intl. sgs2. This is a problem many ran into when original SGS2 leaked tars started surfacing as well.
JTAG might be able to fix it, I'm not sure whether people with this issue were successful or not with JTAG repair as the intl gs2 flashing boat seems to have sailed now. However, a jig will likely do nothing, unfortunately.

barnacles10 said:
I just downloaded the tar to have a look at whats included.
After flashing this you'll have a bootloader for the intl. sgs2. This is a problem many ran into when original SGS2 leaked tars started surfacing as well.
JTAG might be able to fix it, I'm not sure whether people with this issue were successful or not with JTAG repair as the intl gs2 flashing boat seems to have sailed now. However, a jig will likely do nothing, unfortunately.
Click to expand...
Click to collapse
Ok thank you for your help on this. You don't think a jig will reset the counter or anything so that I can take it back to Sprint? If not, I'm not above "dropping" it on the ground and using the insurance I have on it for a replacement.

munson11 said:
Ok thank you for your help on this. You don't think a jig will reset the counter or anything so that I can take it back to Sprint? If not, I'm not above "dropping" it on the ground and using the insurance I have on it for a replacement.
Click to expand...
Click to collapse
I don't foresee it working only because your phone isn't recognized by your pc and the problem doesnt lie on the pc side.
The problem is instead with the port on the phone which leads me to believe it won't recognize a jig either.
A jtag if successful will leave you with more money in your pocket and a non-returb. Something to consider if you've got a backup phone you can use for a few days.

barnacles10 said:
I don't foresee it working only because your phone isn't recognized by your pc and the problem doesnt lie on the pc side.
The problem is instead with the port on the phone which leads me to believe it won't recognize a jig either.
A jtag if successful will leave you with more money in your pocket and a non-returb. Something to consider if you've got a backup phone you can use for a few days.
Click to expand...
Click to collapse
I don't see sprint replacing it with cm9 On it .... And u will need mobile Odin to get back to stock but with it not mounting the Emmc probably can't do that .... That is your hope to get back to stock using mobile Odin someway .... Triangle away app will reset Odin count but with no radio you need to get apps to do it and no sd from what u said ...maybe tell insurance u lost it and get it replaced
Jtag should work also since there is no emmc failure like the blue light of death bricks ...
Sent from my SPH-D710 using Tapatalk 2 Beta-5

Am I in brick city?

So i tried to update my AOKP with just using my phone. And after the reboot.. nothing happened. So i did a battery pull and now when I turn on my baby the led goes blue and stays there.. frozen. No access to recovery or download.
Black screen and blue led.. so yeah.
What I'm asking is.. there's no way of coming back?
Sent from my Old Evo using xda premium

Also.. I semi-bricked before and was able to fix via download mode.. so I know my way around.
Sent from my PC36100 using xda premium

When you updated AOKP you flashed the EL26 CWM kernel as per the instructions in all AOSP roms up until now? Both the recovery in AOKP 37 and the Zip for AOKP 39 (as far as I am aware) are not safe to flash in ICS Recovery.
BLoD is a sign that the bootloader is borked. Normally this is something fixable via JTAG. But it is also caused at Random by the Super Brick bug which can not be fixed. Sounds like you flashed not only an unsafe Zip but in an unsafe recovery and if you tell me you factory reset that would be even worse.
Our phone has a bug in its eMMC firmware which needs to be patched. All of the former ICS leaks have had kernels that can trigger it and last i checked only the Nighlies for CM9 have a safe updater binary used in conjunction with a made safe recovery are generally safe to flash from ICS. Which is exactly why the threads tell you to use the EL26 CWM kernel which if mobile can be flashed via mobile odin. Failure to do so will eventually at random trigger the bug.

Blue LED and not able to get phone into Odin mode = Hard Brick

another one bites the dust......i just don't know how the directions could be any more clear on flashing ICS ROM's. Maybe we need a sticky in every forum in bold letters that says:
"READ ME BEFORE FLASHING!"

I read the warnings and all that jazz. It was just a bad download thanks to the 4G. Mistakes happen. Relax @ above poster.
Yeah I went about it the right way. I have insurance with Sprint, hopefully I'll get lucky and get a new phone.
Thanks to the rest that answered.
Sent from my PC36100 using xda premium

I agree with Rican Bomba... Not everyone is a Android hacking Guru. We are all trying to learn here. I bricked my phone and i did follow QBking77's instructions (Who i believe to be the best at explaining things thoroughly in his videos) yet, there are so many post that aren't clear. I had force closes like crazy on AOKP and before i found the one poster that said don't wipe in ICS... I had done it and lights out R.I.P. First E4GT. I have flashed way too many times to count without incident. Some posters put more info on how not to brick than others. I followed QBking's method to a tee and something was still wrong... I don't blame him (He makes things crystal clear and is great at what he does), things happened and that was that. I learned something from a poster who was very clear and i won't make the mistake again (not to mention I'm leaving AOKP alone lol). Take it easy on these guys, they will learn soon with a little friendly direction

Rican Bx Bomba said:
I read the warnings and all that jazz. It was just a bad download thanks to the 4G. Mistakes happen. Relax @ above poster.
Yeah I went about it the right way. I have insurance with Sprint, hopefully I'll get lucky and get a new phone.
Thanks to the rest that answered.
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
Never never never never download a ROM through Mobile Network... and if you do, make sure you check the md5. I think almost all of my 4G ROM downloads have been corrupt

iniz94 said:
Never never never never download a ROM through Mobile Network... and if you do, make sure you check the md5. I think almost all of my 4G ROM downloads have been corrupt
Click to expand...
Click to collapse
Flashaholic lol no computer access at my job and at home at the moment.
Sent from my PC36100 using xda premium

Download mode - Odin will only recognize when phone is booted up

I am at my wits end right now. I can see my phone on com3 when it is booted up all the way, but it will not see it when in download mode. I erroneously flashed this file earlier, forgetting I did not have a regular GSII: I9100_APBOOT_I9100XXKP2_CL17109_REV02_eng_mid_ship.tar.md5
What other information would help diagnose this problem?
I currently have stock EL26 installed.
Alternatively, is it safe to install CM9 from this recovery? Seems to me I should resolve this first..
edit: I do not have an unrecognized device, I have tried more than one usb cable and port

Try this:
Redownload the drivers for the phone, install them and let your cpu reset. See if Odin sees your phone then.
I know with my GT10.1 it takes a few seconds more for Odin to see it so... But my ET4G pops up pretty fast.
The EL26/CWM is the kernel/recovery that you want to use when your flashing CM9 Alfa 5 and below.
But like you said... You may want to figure out why Odin isn't seeing your phone when it's in download mode.
Also... Do you have Kies installed on your cpu??? It'll cause problems with Odin to.
Have you tried Mobile Odin for what you want to do. I do almost everything involving CM and flashing with it. Works like a charm.
Sent From My Galaxy Class Star Fighter...

How in the hell do you forget you don't have a international version?! Smh
Sent from my SPH-D710 using xda premium

fryingpan0613 said:
How in the hell do you forget you don't have a international version?! Smh
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
WoW... He just edited his post as I was replying... Doesn't flashing an international tar mess up the bootloader??? I'm really not to sure where you go next.
If his phone still boots up okay couldn't help still use Mobile Odin and flash the right setup.
What was that old school Saturday morning psa... "Reading is fundamental" or something like that.
Sent From My Galaxy Class Star Fighter...

What is the right setup to use? A fresh GB rom install? I am at a loss at this point.
Yeah I ****ed up, I have not messed with my phone in many months.
Edit: driver reinstall did not work, do not have kies installed. mobile odin works on GB then? I can use the e4gt-autofix if that makes a difference. Updating from the stock recovery does not seem to work, it will start, then give me the ! triangle with sad android.

hilo4321 said:
What is the right setup to use? A fresh GB rom install? I am at a loss at this point.
Yeah I ****ed up, I have not messed with my phone in many months.
Edit: driver reinstall did not work, do not have kies installed. mobile odin works on GB then? I can use the e4gt-autofix if that makes a difference. Updating from the stock recovery does not seem to work, it will start, then give me the ! triangle with sad android.
Click to expand...
Click to collapse
Unfortunately my friend, I think you are hosed. The international PIT file is exceptionally different from the one we use for our phone. I don't remember the specifics but basically it remaps your partitions and causes USB to not work correctly. Your best bet is to try a JTAG service. I've heard MobileTechVideos.com is pretty well rated.
Sorry!

My phone is currently functioning properly when booted up. What are the implications of this beyond not being able to change roms (and not having a notification bar..wtf)?
Edit: ok I take it back, mass storage is not working either. also, I am definitely willing to buy Mobile Odin if anyone has any ideas.

hilo4321 said:
What is the right setup to use? A fresh GB rom install? I am at a loss at this point.
Yeah I ****ed up, I have not messed with my phone in many months.
Click to expand...
Click to collapse
Not getting on you m8 but... Flashing a rom for another device even if it's the same model is really really bad. Like rwilco said, yes the International GS2 and our ET4G's are the same devices but there software is very different.
hilo4321 said:
My phone is currently functioning properly when booted up. What are the implications of this beyond not being able to change roms (and not having a notification bar..wtf)?
Click to expand...
Click to collapse
Well... Like you said, most likely you will not be able to make any changes as in roms, kernels or things like that. And if you have any hardware issue you won't be able to get any support from Sprint. And you sure as hell won't be able to receive any OTA's from Sprint or Samsung.
Can you do something for use... Go to "Settings" then "About Phone" and under "Model Number" & "Baseband Version" and tell us what it says there.
I'm not really sure this would/can help you but if your phone still boots and runs you maybe able to Odin the right tar file and see if that fixes it. I mean it could work but I really doubt it. And what's the worst that could happen... It could brick it, then you could file an insurance claim... Just saying...
Where did you get the file from that you flashed??? Most likely not from this (ET4G) forum, should have read up a bit more before you started messing around with flashing roms again. Some things aren't easily fixable.
Sent From My Galaxy10.1 Class Starship....

I am a lucky SOB. I was able to use e4gtauto-sfx to put el29/CWM back on to my phone, and as a result I restored my nandroid backup. I have full function back, except, of course, no odin in download mode.
My baseband is S710.10 S.EK02 with standard model number sph d710.
I believe it came from the android forums, but like i said it was in the SGII area.
What tar file would I be looking for?

Doing some research m8... Give me a few mins....
Make sure you have Mobile Odin installed.
Sent From My Galaxy Class Star Fighter...

hilo4321 said:
I am a lucky SOB. I was able to use e4gtauto-sfx to put el29/CWM back on to my phone, and as a result I restored my nandroid backup. I have full function back, except, of course, no odin in download mode.
Click to expand...
Click to collapse
Ok... Yes you are my friend!!!! But I fear we are not completely out of the woods as of yet. You still have the "no Odin in download" thing still. And that could still be an issue, but at least your back up and running.
hilo4321 said:
My baseband is S710.10 S.EK02 with standard model number sph d710.
Click to expand...
Click to collapse
This is telling me that your on an older baseband... I'm running CM9 and my baseband reads "EL29" which I think is the most resent/updated baseband. I don't want to scare you but I really wish a dev would jump in here and shed some of there wisdom. (I'm almost to the point where I'm winging it.) But I feel we need to get your baseband to EL29.
hilo4321 said:
I believe it came from the android forums, but like i said it was in the SGII area.
Click to expand...
Click to collapse
From now on promise us you'll just use this site and forum for all of your download needs.... Please.
hilo4321 said:
What tar file would I be looking for?
Click to expand...
Click to collapse
Try this post... http://forum.xda-developers.com/showthread.php?t=1433101
Follow the instructions for the Android Install, about halfway down in the first post.
Sent From My Galaxy10.1 Class Starship....

Oh sweet Jesus, I promise.
Now when I do this will this wipe everything? I'm not terribly clear on that. Seems to me that it will.
I really appreciate the help man.

There are 2 different versions... One will wipe everything and one will leave all of your user data intact.
And like I said, I'm not a 100% sure this will fix it but I think we are moving in the right direction.
And not a problem... It's helping me learn more about what goes on inside our devices.
I am still a little worried about your bootloader though. If that was jacked up by flashing the wrong rom I don't know if this will fix it.
Question, when you hook up your device to your cpu when it's booted up are you still able to do things like transfer files and such???
Sent From My Galaxy10.1 Class Starship....

I can use mass USB now. I wont be able to test the el29 now though as I'm away now. I will report back when I can.

hilo4321 said:
I can use mass USB now. I wont be able to test the el29 now though as I'm away now. I will report back when I can.
Click to expand...
Click to collapse
That's great brother.... I'm really glad I could help ya get up and running to the point where you can a least have a use able device.
Sent From My Galaxy10.1 Class Starship....

EL29 was the last version of Gingerbread put out. You'll be able to use mobile Odin to flash stuff but you'll never get the USB to recognize in DL mode. I think jtag might be the only way to restore complete functionality.
---------- Post added at 11:42 PM ---------- Previous post was at 11:36 PM ----------
For now you'll be alright as long as you can get into recovery mode fine then you can flash modems in there(since mobile Odin can't flash them for our phone).

Your baseband (modem) should not matter and changing it won't have any affect on your problem. Good luck and let us know how out turns out.

Solved
I am posting now in case someone comes upon this post down the road.
I am now running cyanogen 9 on my e4gt. This thread saved me, as I was finally able to get odin to work. With that, I was able to flash a new recovery onto my phone (I used StockCWM-EL26). Then once I got that on there I flashed over to the Beta 1 build of Cyanogenmod for e4gt.
I'm sorry I can't be more clear or provide links, it took me a lot of crawling around the forums to figure this out. Perhaps someone more knowledgeable than I can clean up/expand my post. Let me tell you though, it feels really good to get this thing running smoothly again.
If you have any questions I'll try to help.
Good luck, idiot!

That's awesome dude. Remember stay in this forum :beer::thumbup:
sent from MY BAD A$$ ET4G

Help! phone won't turn on (t959d koodo)

Hi,
I just got the phone and flashed a custom recovery. I flashed a new rom (liquidsmooth) and it looked like it was successful. I selected reboot and the screen shut off. Now, It won't turn on. It's possible that the battery died but shouldn't it turn on again once I plug in the usb cable? Is it possible to brick the device from cwm?
thanks

Dear lord I hope that's a typo because this is the t989(d) forums. If it is a typo and you're using a t989 then you probably need to wipe cache/dalvik.
Sent from my SAMSUNG-SGH-T989

As Mr. Mintharis said... I'm hoping as well that you had a typo and you didnt flash a T989 (GALAXY S2 TMobile) rom on a (GALAXY S) device. If so your probably hard bricked. If that was a typo and you did flash a rom and it wont turn on then there may be a few problems that are solvable. I got a few questions.
1. DId you do a factory reset before installing? Did you wipe system?
2. Can you get into CWM?
3. Can you get into Download Mode?
If you cant get into download mode, recovery, or get the phone to boot then you are in serious trouble because the phone is a a fancy paper weight. If you can however, you could try doing a full reset on all the settings and deleting cache/dalvik and then reflashing and trying again. However you may be in luck since you said you just got the phone. I'm assuming you got it from your carrier (I'm guessing its T-Mobile, idk any other carriers for this device) and they will replace a broken device (that does not have extensive physical damage or water damage) within 20 days of purchase date. Since your phone is hard bricked they will do it completely for free with no charge (usually... if they do.. it will be about 5$) and then you're good. They will overnight a phone to you and you just send your old one back when you get it (MAKE SURE TO ASK FOR DIRECTIONS ON HOW TO PROPERLY SEND IT BACK!).
Sorry for the long post but wanted to be through and give you alot of answers in 1 time so we dont drag this post out.

That's my mistake, it was supposed to read t989d.
1) I did do a factory resets
2) & 3) I can't turn on the phone or get into download mode
I bought it from koodo (carrier in Canada) yesterday. I'm going to try to exchange it today; hopefully they'll do it. For future references, is there a specific way I should be flashing? I used to have a t959, the t-mobile vibrant, and never had any issues with cwm because it never touched download mode. Anyways, thanks for the replies.
Edit: I did flash using odin which hung a couple of times. Regardless, i eventually got it back to original condition by flashing the custom recovery (by odin with green pass) and doing a nandroid backup. The bad odin flashes should have been negated when I did nandroid backup, no?

You said you had the problems after you flashed liquidsmooth? Exactly which file did you download and flash from the site?
Sent from my SGH-T989 using xda premium

Ok, just figured it out. I flashed wrong version of liquid smooth. The link in their thread goes to their facebook page and I clicked on the first link like an idiot. I got it exchanged a few minutes ago so all's well that ends well. Thanks all for the replies.
Lesson of the day: Don't be stupid.

mani_is_ms said:
Ok, just figured it out. I flashed wrong version of liquid smooth. The link in their thread goes to their facebook page and I clicked on the first link like an idiot. I got it exchanged a few minutes ago so all's well that ends well. Thanks all for the replies.
Lesson of the day: Don't be stupid.
Click to expand...
Click to collapse
Read read read.. If you are not 100% sure what you are doing just ask someone.. Sometimes you will get flamed for it but it's better than getting a bricked phone lol and you'll most likely get an answer..
I'm glad you got it replaced
Sent from my SGH-T989 using xda premium

My phone is bricked?

Hello every one! so yesterday while doing nothing but leaving my phone on a markipilers youtube video, I see my screen go off I try to turn it back on and nothing happens. I tried power cycling and its still off, just not responding to anything, no sound no light no nothing. I tried then going to recovery mode but well... nothing happened. The only thing that actually makes any responses is when I connect it using a USB to my laptop, my laptop beeps, its not suposed to beep it is broken so is it bricked?
My device is a rooted Samsung galaxy s4 mini i19192 or so I hope it is.
I really hope that this is the right place to be redirected to assistant if not then Iam really sorry, thank you so much every one and have a fantastic day!
Edit: I forgot to mention two things.
1st: It does not seem to charge the battary, I kniw this because I have another identical one though the battary works fine in the working one
2nd: My PC reads it as (something?)_dload, Sadly I do not have acess to a computer just yet. Thanks again

Any help.. please?

Khaled125 said:
Hello every one! so yesterday while doing nothing but leaving my phone on a markipilers youtube video, I see my screen go off I try to turn it back on and nothing happens. I tried power cycling and its still off, just not responding to anything, no sound no light no nothing. I tried then going to recovery mode but well... nothing happened. The only thing that actually makes any responses is when I connect it using a USB to my laptop, my laptop beeps, its not suposed to beep it is broken so is it bricked?
My device is a rooted Samsung galaxy s4 mini i19192 or so I hope it is.
I really hope that this is the right place to be redirected to assistant if not then Iam really sorry, thank you so much every one and have a fantastic day!
Edit: I forgot to mention two things.
1st: It does not seem to charge the battary, I kniw this because I have another identical one though the battary works fine in the working one
2nd: My PC reads it as (something?)_dload, Sadly I do not have acess to a computer just yet. Thanks again
Click to expand...
Click to collapse
probably QHSUSB_DLOAD, which is a hard brick, you might be able to fix with a debrick image
Sent from my Galaxy S4 Mini using XDA Labs

its in fact qshusb_dload but iam still a bit clueless on the reason or which method to solve. I read its because the cpu is trying to boot from the sd card and has something to do with something called emmac that is terrible in the s4 so I read three methods to solve
1- Just your method
2- Cooling the emmc?
and three, this
http://cellphonetrackers.org/qhsusb_dload-fix-qualcomm-soc.html
so Iam a bit distracted on what to even do or how to do it, any help would be apriciated plus any further notices about how to even avoid the problem
and thank you so much @IronRoo for your noticable contributions to these stuff!

Khaled125 said:
its in fact qshusb_dload but iam still a bit clueless on the reason or which method to solve. I read its because the cpu is trying to boot from the sd card and has something to do with something called emmac that is terrible in the s4 so I read three methods to solve
1- Just your method
2- Cooling the emmc?
and three, this
http://cellphonetrackers.org/qhsusb_dload-fix-qualcomm-soc.html
so Iam a bit distracted on what to even do or how to do it, any help would be apriciated plus any further notices about how to even avoid the problem
and thank you so much @IronRoo for your noticable contributions to these stuff!
Click to expand...
Click to collapse
Yes, the eMMC is prone to fail/corruption on our phones, at least I think. The eMMC is the internal SD memory. Hopefully yours is just corrupt.
The cooling trick is probably only good if there is a bad soldier joint on the chip and will probably only work a few minutes as the board will heat up once turned on
I would try the debrick file as that's probably the easiest. See also Valenti's post on other Samsung device, as better write up on one (Samsung Mega maybe?) as well as by the others who originally come up with the debrick idea to get a better idea of what to do.
I guess (without researching) the method in your link is the same principle as the debrick file but may work even if debrick doesn't work as not dependant on having a matching file from phone with same bootloader (???? I don't know as haven't looked into that method)
Also you can send phone away for jtag if nothing else works
Sent from my Galaxy S4 Mini using XDA Labs

IronRoo said:
Yes, the eMMC is prone to fail/corruption on our phones, at least I think. The eMMC is the internal SD memory. Hopefully yours is just corrupt.
The cooling trick is probably only good if there is a bad soldier joint on the chip and will probably only work a few minutes as the board will heat up once turned on
I would try the debrick file as that's probably the easiest. See also Valenti's post on other Samsung device, as better write up on one (Samsung Mega maybe?) as well as by the others who originally come up with the debrick idea to get a better idea of what to do.
I guess (without researching) the method in your link is the same principle as the debrick file but may work even if debrick doesn't work as not dependant on having a matching file from phone with same bootloader (???? I don't know as haven't looked into that method)
Also you can send phone away for jtag if nothing else works
Click to expand...
Click to collapse
Thats great! thank you. however can you give me a link to download that file / tutorial as iam not sure google would help me in that. second off I have no idea where Valenti's post either so that would just be fantastic if you can, Thanks again for every thing!

Khaled125 said:
Thats great! thank you. however can you give me a link to download that file / tutorial as iam not sure google would help me in that. second off I have no idea where Valenti's post either so that would just be fantastic if you can, Thanks again for every thing!
Click to expand...
Click to collapse
There are some debrick files here for some of the S4 Mini models (some have broken links but some still work, or find others on internet. This is also one of the thread started by @ValenteL
http://forum.xda-developers.com/showthread.php?t=2625628&page=10
Sent from my Galaxy S4 Mini using XDA Labs

IronRoo said:
There are some debrick files here for some of the S4 Mini models (some have broken links but some still work, or find others on internet. This is also one of the thread started by @ValenteL
http://forum.xda-developers.com/showthread.php?t=2625628&page=10
Click to expand...
Click to collapse
Wanderful, Thank you! should I mark this as solved?

IronRoo said:
There are some debrick files here for some of the S4 Mini models (some have broken links but some still work, or find others on internet. This is also one of the thread started by @ValenteL
http://forum.xda-developers.com/showthread.php?t=2625628&page=10
Click to expand...
Click to collapse
I have been searching for ever and still zero luck on finding either a way through the s4 mini nor the actual debrick file... all I could find was for the s3 all over, any help?

Khaled125 said:
I have been searching for ever and still zero luck on finding either a way through the s4 mini nor the actual debrick file... all I could find was for the s3 all over, any help?
Click to expand...
Click to collapse
Did you try the two debrick images in my post dated the 22nd March in the thread I posted above?
Actually I also pulled one from my phone after I read you can generate one from Cyanogenmod phones that will also work, I will post that on the above thread also a bit later.
Sent from my Galaxy S4 Mini using XDA Labs

IronRoo said:
Did you try the two debrick images in my post dated the 22nd March in the thread I posted above?
Actually I also pulled one from my phone after I read you can generate one from Cyanogenmod phones that will also work, I will post that on the above thread also a bit later.
Click to expand...
Click to collapse
Just found it, Though if your link would have directed to page 8 rather than 10 that would have been fantastic! I thought You ment the main post which also helped me alot. How ever do I really have to downoad monster legands to be able to download the foking file?

oh never mind, Just a damn ad

IronRoo said:
Did you try the two debrick images in my post dated the 22nd March in the thread I posted above?
Actually I also pulled one from my phone after I read you can generate one from Cyanogenmod phones that will also work, I will post that on the above thread also a bit later.
Click to expand...
Click to collapse
Oh and how do you flash that thing to recovery, How do you pull that debrick file? is really confusing me

And please pardon me if my questions are spammy or annoying, There are a whole lot of steps through it and neither google nor the forum seem to be answering it so I might just consult you for that.
From what I understand, You flash the debrick file to the sd card using this 32 bit sd flasher thing and then it just works because the booting files are on the sd card but it will not boot without it. So how can you fix the corrupted boot loader AND how can I restore my sd card back to normal, I have seen a video for it but he is using ubuntu and command lines and stuff.

Khaled125 said:
Oh and how do you flash that thing to recovery, How do you pull that debrick file? is really confusing me
Click to expand...
Click to collapse
The original post by @ValenteL was a file to generate a debrick image, but you need a working phone to use that.
People with phones that are already bricked have to get a debrick file from someone else. This debrick image must be put onto an 16Gig (some report success with 32gig) SD card that is formatted (so you will lose everything else on it) and then the phone will boot with it instead of internal mmc to get your phone going (you have to keep the SD in) so you can then recover data and also hopefully flash a new rom later so you don't need to always boot from SD.
Sent from my Galaxy S4 Mini using XDA Labs

IronRoo said:
The original post by @ValenteL was a file to generate a debrick image, but you need a working phone to use that.
People with phones that are already bricked have to get a debrick file from someone else. This debrick image must be put onto an 16Gig (some report success with 32gig) SD card that is formatted (so you will lose everything else on it) and then the phone will boot with it instead of internal mmc to get your phone going (you have to keep the SD in) so you can then recover data and also hopefully flash a new rom later so you don't need to always boot from SD.
Click to expand...
Click to collapse
Yes, that was what I understood already but thank you anyway! My question was How? on both creating the debrick file and restoring both sd card (too make it work as a readable card rather than a booting device if it does not already) and fix the phones internal memory without actually reseting the whole phone and if there are no way else to fix internal memory... to back up the whole thing.
thank you!

IronRoo said:
Did you try the two debrick images in my post dated the 22nd March in the thread I posted above?
Actually I also pulled one from my phone after I read you can generate one from Cyanogenmod phones that will also work, I will post that on the above thread also a bit later.
Sent from my Galaxy S4 Mini using XDA Labs
Click to expand...
Click to collapse
WANDEFUL! My phone actually viperated and showed color!
however.. it gives this on a black screen.
boot recovery
check boot partitions
copy from t flash
boot recovery
write 139008
reboot
and obviously reboots, thoughts?

My last two posts are the most important now, if you or any one else can answer that would be fantastic!
some notes: after searching the thing does not mention emmc nor odin at all like for some others with the same issue... just this plain text.
I had upgraded my android version to 4.4.2 not 4.2.2 so I assume that is important, thanks again and please answer as soon as you can as that would be great! thank you for every thing @IronRoo

Khaled125 said:
My last two posts are the most important now, if you or any one else can answer that would be fantastic!
some notes: after searching the thing does not mention emmc nor odin at all like for some others with the same issue... just this plain text.
I had upgraded my android version to 4.4.2 not 4.2.2 so I assume that is important, thanks again and please answer as soon as you can as that would be great! thank you for every thing @IronRoo
Click to expand...
Click to collapse
I think the important thing is the bootloader (& pit must be the same) that if I recall was updated from the version you mention to ver 2. So you need a debrick with the ver 2 bootloader. (but I am not 100% sure about this, only read some stuff last year) My phone BL is ver 1
a guy on the below Mega thread with an I9195 did get a stop further by repeating multiple times
http://forum.xda-developers.com/showthread.php?t=2600976&page=4
But still didn't fix phone fully
read next few pages, one guy used freeze fix white partial success, might be useful if you want to get data off phone.
Also another link that may offer help
but probably your emmc is bad, is my guess
gotta go now, work calls
Sent from my Galaxy S4 Mini using XDA Labs

IronRoo said:
I think the important thing is the bootloader, that if I recall was updated from the version you mention to ver 2. So you need a debrick with the ver 2 bootloader. (but I am not 100% sure about this, only read some stuff last year) My phone BL is ver 1
a guy on the below Mega thread with an I9195 did get a stop further by repeating multiple times
http://forum.xda-developers.com/showthread.php?t=2600976&page=4
But still didn't fix phone fully
read next few pages, one guy used freeze fix white partial success, might be useful if you want to get data off phone.
Also another link that may offer help
but probably your emmc is bad, is my guess
gotta go now, work calls
Sent from my Galaxy S4 Mini using XDA Labs
Click to expand...
Click to collapse
Thats great! good luck at your work, when you are back though I need to tell you this
I have another device of the exact same model that is kikkat not rooted (kitkat will have bootloader version 2 right?) if only I knew how to get the file out and then do all the stuff again, ill keep searching since you are at work now, will keep you updated. please help about it though if you can*
so if someone say for example has android 5 on an s4 mini, he will never get his phone back to work unless some one made a debrick file for it? if the previous statments were true?
My questions are:
Extract that file from the other phone, if I managed to answer it ill tell you.
To get my SD card back to work and fix my emmc
Iam not giving up on my emmc yet though, iam sure there is a way to solve it, if not then how to fix that failed emmc?
thanks again!