Develop Bugs

TrevE.. Bricked my phone!

TrevE you do great work.. and yea i know that this is my own fault for flashing and im not blaming you... BUT i installed (and bought the pro version) your "logging test app v7" and ran the ICQ remove... rebooted my phone like it said to and now its a paper weight... I gets stuck at the "Samsung screen". I tried putting it into "download mode" and odin back to stock and nothing. It goes into the download mode screen but my PC will not pick it up at all. Yes i have the right drivers (I am not a complete noob). I tried it with odin3 v1.85 and v1.61.
Any advice on how to fix it? Any of you guys know if sprint will be able to tell it was rooted when I take it in for a replacement (I have protection).
Phone specs..
epic 4g
stock II22 rooted

persistence pays off. after trying to get my phone into CWM about 50 times it finaly worked! flashing a new rom now... I will not be reloading the app.. but im not going to get a refund either.. keep the buck, you do great things! But if you figure out why this app does not like the epic 4g let me know.

Did you use this? http://forum.xda-developers.com/showthread.php?t=1247108
TrevE develops for HTC devices as far as I'm aware.
If you are looking for the original mod for CIQ removal by k0nane, then go here: http://forum.xda-developers.com/showthread.php?t=1340083

Try removing the battery for a bit before going into download mode. Try both with wall/usb cable connected and/or sd card removed.

http://forum.xda-developers.com/showthread.php?t=1359647

First off, if you don't blame Trev you should change the title...kind of rude. CIQ removal is not the same for all phones. You should have read more. Now to restore your phone follow this thread and if Odin isn't recognizing it no matter what then go to post 2 on using Heimdall to restore your phone:
http://forum.xda-developers.com/showthread.php?t=1052813

I have had many of issues with odin, from not picking up to my screen turning random colors during odin flash.
You wouldn't by chabce have windows 7 64bit because its a pain with that os for some reason.
I would suggest uninstalling the drivers and reinstalling them and it should run through the steps to rehook the drivers for odin, does for me everytime I flash with odin I have to reinstall drivers
Sent from my SPH-D700 using XDA App

Of coerce i dont balm treve... Thats the risk we take when we start to mess with our phones! But his app did crash it!! I sent him a PM so hopefully he will figure it out.. He does amazing this for Android, i have nothing but respect for him! If he tells me he has a problem with my title ill change it..
The first thing i did was take out the SD card but thanks for the heads up.
Odin has never once given me any problems and it now picks up my phone fine.
Thanks for the battery advice! I was only taking out for a minute or so, Ill try it for longer if i have any more troubles.
The phone is working great now.. just had to try to get into CWM about 50 times.

So say you don't blame TrevE yet your title says you do.
Pull the battery leave it out for a say or so and try again.

NissanNick said:
Of coerce i dont balm treve... Thats the risk we take when we start to mess with our phones! But his app did crash it!! I sent him a PM so hopefully he will figure it out.. He does amazing this for Android, i have nothing but respect for him! If he tells me he has a problem with my title ill change it..
The first thing i did was take out the SD card but thanks for the heads up.
Odin has never once given me any problems and it now picks up my phone fine.
Thanks for the battery advice! I was only taking out for a minute or so, Ill try it for longer if i have any more troubles.
The phone is working great now.. just had to try to get into CWM about 50 times.
Click to expand...
Click to collapse
Dude. That is not for our phones. HTC only. TrevE has nothing to do with samsung phones.

Let's just throw an htc sense framework over touchwiz...it'll be fine!
*scoffs*
sent from my always aosp epic

zanderman112 said:
Dude. That is not for our phones. HTC only. TrevE has nothing to do with samsung phones.
Click to expand...
Click to collapse
He should change the title to "I'm an idiot and bricked my phone using an HTC mod by TrevE because I can't read". Much more accurate.
Sent from my SPH-D700 using XDA App

Clockworkmod should still work if you installed a bad framework.
Sent from my SPH-D700 using XDA App

marcusant said:
Clockworkmod should still work if you installed a bad framework.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
He said it did.
sent from my always aosp epic

USB Not working & LOST Clockwork Mod Recovery
Assistance please!!! Need to take back Epic to Sprint.
I was trying to flash the lastest recovery on my my wifes phone and in the process lost recovery(see images) I downloaded ROM Manager and tried reflashing and nothing. I need to take the phone back to SPRINT because the USB stopped working, No ODIN, Wont connect via USB at all........
I need to return system to stock with no USB support at all. Please direct me to the right thread if you have heard of this before.

you used the wrong method for the wrong phone!
NissanNick said:
Of coerce i dont balm treve... Thats the risk we take when we start to mess with our phones! But his app did crash it!! I sent him a PM so hopefully he will figure it out.. He does amazing this for Android, i have nothing but respect for him! If he tells me he has a problem with my title ill change it..
Click to expand...
Click to collapse
No dude, his app didn't crash it. You did because you used the wrong method for the wrong phone!

The app couldnt have.
Sent from my SPH-D700 using XDA App

Looks like to me that you are one stock recovery so u should be Ok... someone correct me if im wrong
[email protected] said:
Assistance please!!! Need to take back Epic to Sprint.
I was trying to flash the lastest recovery on my my wifes phone and in the process lost recovery(see images) I downloaded ROM Manager and tried reflashing and nothing. I need to take the phone back to SPRINT because the USB stopped working, No ODIN, Wont connect via USB at all........
I need to return system to stock with no USB support at all. Please direct me to the right thread if you have heard of this before.
Click to expand...
Click to collapse
Sent from my SPH-D700 using XDA App

phatryan69 said:
Looks like to me that you are one stock recovery so u should be Ok... someone correct me if im wrong
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
He was on clockworkmod and he is still on a custom rom...
Sent from my SPH-D700 using XDA App

This is not a beat treve app up.. This was just to get advice on how to unbrick my phone and see if maybe he could fix it for the epic... This thread is great lol. I named the title that to mainly get everyone attention because i was worried about not having a working phone....
I dont blame treve or his app really... as a matter of fact i took full responsibility for it.
And yes i did brick my phone because im i moron that used the wrong app... but i am still finding all this great.

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

[Q] Phone bricked, possibly bad CWM flash file

So Ive had my GS3 for a few weeks now and no issues, been stock rooted with the 6.0.1.2 CWM (non touch).
Was browsing around on the General forum and noticed this sticky called "[INDEX] AT&T GS III - I747 {ROMs/Root/Recovery.. etc}"
In there was a 6.0.1.4 CWM, I noticed both were CWM flashable. One for touch and nontouch.
So I downloaded it directly to the phone, booted into CWM, flashed the touch version, and told it to reboot recovery. And since then the phone is basically bricked. It never turned back on, screen remains black. Nothing happens. Cant force it into Download mode either. I took the battery out and put the USB cable in and all I get is the RED LED for about 1min. I get a qhsusb_dload driver that doesnt load on the computer, nothing else. So the phone is basically bricked.
I then decided to see what happened, i downloaded the flash file that was in that thread which is here
http://dl.dropbox.com/u/31151290/CWM/CWM_Touch_6.0.1.4.zip
When I open it and look at the updater-script, I see a problem. This is flashing the recovery to mmcblk0p8
The i747's recovery partition is mmcblk0p18
So this thread that is referencing these two CWMs probably should be pulled or fixed, cause p8 partition is tz. Not sure what that is, but it almost looks like its completely screwed the bootloader part.
Any way to recover this or is JTAG service the only option for my paper weight?
Dixit

I've heard on another thread someone installing CWM Touch had the same problem, vaguely light yours.
All I can say from what knowledge I have is Odin or getting a Jig. Last resort's are better than Service, lol.
Goodluck :]

Jig won't work. You are hard bricked sorry for your bad luck!!! I had a hard brick and had to send mine for jtag repair. If you live in the states you could send your phone to get repaired and get it back in 4 business days average. (varies).
If you still have warrenty... go that route!!
Sent from my Desire HD using Tapatalk 2

http://forum.xda-developers.com/showthread.php?p=32113899
Check this thread
Sent from my SGH-I747 using xda app-developers app

What sucks is the thread is a sticky and points to these two CWM files to use and technically both are wrong. The moderators need to pull those two links. As I mentioned earlier, those two zips are flashing to pEIGHT (p8) when it whould be pEIGHTEEN(p18). Thats why it got bricked.
Dixit

I did the same thing. It was for the Galaxy Nexus. The person linked to a single post, so it was to hard to tell what that recovery was for. I still wonder if that person did it on purpose.
Sent from my SAMSUNG-SGH-I747 using xda premium

dixit said:
What sucks is the thread is a sticky and points to these two CWM files to use and technically both are wrong. The moderators need to pull those two links. As I mentioned earlier, those two zips are flashing to pEIGHT (p8) when it whould be pEIGHTEEN(p18). Thats why it got bricked.
Dixit
Click to expand...
Click to collapse
If you feel that strongly about it, report the thread. In Web view or on your pc, look to the right of a post, next to the post count for that thread. Little yellow triangle. Press that. I usually mark 99.9% of the stuff i report as post/thread maintenance. After that, you'll get a pm from the moderator handling the report. Then you'll get another when the report is considered to be handled.

ouch.. good luck man

mrhaley30705 said:
If you feel that strongly about it, report the thread. In Web view or on your pc, look to the right of a post, next to the post count for that thread. Little yellow triangle. Press that. I usually mark 99.9% of the stuff i report as post/thread maintenance. After that, you'll get a pm from the moderator handling the report. Then you'll get another when the report is considered to be handled.
Click to expand...
Click to collapse
Thanks, forgot to come back in here and update it, the moderators did get in touch with the OP of that thread and I talked to them and he did already pull the links for those files. He has been trying to get in touch (about 4 messages now) to the original developer but cannot so for now he is just going to leave them off as he agreed with me, it should NOT be flashing p8 when in fact its p18.
Thanks to the moderators on moving on this when we reported it.
Dixit

dixit said:
Thanks, forgot to come back in here and update it, the moderators did get in touch with the OP of that thread and I talked to them and he did already pull the links for those files. He has been trying to get in touch (about 4 messages now) to the original developer but cannot so for now he is just going to leave them off as he agreed with me, it should NOT be flashing p8 when in fact its p18.
Thanks to the moderators on moving on this when we reported it.
Dixit
Click to expand...
Click to collapse
What will you do with your bricked S3 ?

jorioux said:
What will you do with your bricked S3 ?
Click to expand...
Click to collapse
Tried a bunch of things, no go. Only QPST tools sees it but we dont have enough information from anyone on how to use this tool on the S3, we dont have all the files (or no one has developed them yet) like they have on some of the other threads like the HTC one where they can entirely bring the phone back in a hard brick (where it just shows up as QHSUSB download mode).
So probably send it into get JTAG'ed.
Dixit

[Q] Mobile Odin Pro messing up

Hey guys I was using mobile odin pro, getting ready to go back to stock but staying rooted. So i downloaded stock rooted rom and went to mobile odin. In mobile odin there is an option to wipe cache and dalvik cache so I checked them and hit wipe. I was on about 26% and it warned me that when flashing anything it's recommended to be atleast 50%. I continued anyway cause I was simply wiping cache. It began loading then said rebooting into recovery and never turned on. From what I see it looks like it might be hard brick (won't boot into download mode or recovery). I was wondering have any of you experienced this and is it stay repairable without jtag or do I have to send it to MobileTechVideos (again)?
Hope you guys can help, kinda ironic since I was trying to revert back to stock and stop flashing different roms all the time.

Wow I guess no one else has ran into this issue. Or maybe you guys are tired of so many bricked questions, as so am I, but I thought my case was different since it was from using mobile Odin app instead of the usual "accidently flashed an international rom, now won't boot" thread.
Sent from my PC36100 using xda app-developers app
Edit: Can a mod please delete thread if possible. Will just send in for repair, couldn't find fix anywhere.

re: your issue
Cyphers23 said:
Wow I guess no one else has ran into this issue. Or maybe you guys are tired of so many bricked questions, as so am I, but I thought my case was different since it was from using mobile Odin app instead of the usual "accidently flashed an international rom, now won't boot" thread.
Sent from my PC36100 using xda app-developers app
Edit: Can a mod please delete thread if possible. Will just send in for repair, couldn't find fix anywhere.
Click to expand...
Click to collapse
Your case is not that different than all the other cases similar to yours, you
either did not read all the instructions or you decided not to follow them.

Misterjunky said:
Your case is not that different than all the other cases similar to yours, you
either did not read all the instructions or you decided not to follow them.
Click to expand...
Click to collapse
Yeah maybe possible but they were rather shorts steps, I think they were about 6. Simply written too, don't think I missed anything. After reading online some, I've found that mobile Odin has been known of causing bricks on certain devices. Though the op of the thread said it worked perfect on his. It's ok though I'm just going to get it jtagged, then only rooting it on stock. Well until when TW 4.2 is available to us that is .
Sent from my PC36100 using xda app-developers app

possible option
You may be able to use a USB jig to get it into download mode to attempt to flash it back to working order. You can get them fairly cheap on ebay and i know you can make them if you have a little skill with a soldering iron and find the right thread. otherwise it's probably a no go....

Exactly what I DIDN'T want to happen....

So I've had the S4 for 1 month now and at first I really didn't want to root or change the ROM. I actually like the TW interface and think it's great as it is. I've been rooting and changing ROMs going back to the MyTouch, but for some reason the S4 had me worried. I debated over and over about doing it, but after getting tired of the bloatware, constant ads being displayed and wanting to stop the horrible startup/shutdown music, the time came for me to root it.
So, after pouring over many hours of reading and deciding the method, I went with the Chainfire route. I chose this because from what I read (and this may have been where I misunderstood something??), if I ONLY root the phone, don't install a custom recovery then I will still be able to receive OTAs (when and IF they come from TMO). So after a couple of heart-stopping moments at 2am last night with about 4 ODIN fails, I finally got it rooted. Turns out, the USB cable I was using might have been the problem. I went out to the car and got the original cable that came with the phone and it worked on the first try with that. I thought for sure I had hard bricked the phone when it came up with an error message at startup regarding a firmware problem.
Anyhow, to make a long story short, after doing the rooting, I checked the update option in settings and it's telling me the phone has been modified and is unable to receive updates. I then ran the triangle away program to reset the binary counter back to Samsung Official/Official, which it's reporting now instead of Custom, but then checking the updater it still reports the same thing. This is what I didn't want to have happen!
Any suggestions on how to rectify this or have I crossed that line and might as well just go ahead and put a recovery on there and do a backup and leave it at that until the day comes I decide to slap a custom ROM on it?
Thanks for letting me rant, but I would like some assistance if possible.

patriot1973 said:
So I've had the S4 for 1 month now and at first I really didn't want to root or change the ROM. I actually like the TW interface and think it's great as it is. I've been rooting and changing ROMs going back to the MyTouch, but for some reason the S4 had me worried. I debated over and over about doing it, but after getting tired of the bloatware, constant ads being displayed and wanting to stop the horrible startup/shutdown music, the time came for me to root it.
So, after pouring over many hours of reading and deciding the method, I went with the Chainfire route. I chose this because from what I read (and this may have been where I misunderstood something??), if I ONLY root the phone, don't install a custom recovery then I will still be able to receive OTAs (when and IF they come from TMO). So after a couple of heart-stopping moments at 2am last night with about 4 ODIN fails, I finally got it rooted. Turns out, the USB cable I was using might have been the problem. I went out to the car and got the original cable that came with the phone and it worked on the first try with that. I thought for sure I had hard bricked the phone when it came up with an error message at startup regarding a firmware problem.
Anyhow, to make a long story short, after doing the rooting, I checked the update option in settings and it's telling me the phone has been modified and is unable to receive updates. I then ran the triangle away program to reset the binary counter back to Samsung Official/Official, which it's reporting now instead of Custom, but then checking the updater it still reports the same thing. This is what I didn't want to have happen!
Any suggestions on how to rectify this or have I crossed that line and might as well just go ahead and put a recovery on there and do a backup and leave it at that until the day comes I decide to slap a custom ROM on it?
Thanks for letting me rant, but I would like some assistance if possible.
Click to expand...
Click to collapse
If you've reset your binary counter and have modified nothing else, just unroot and you should be able to receive updates again.

Go into the Triangle Away app and check system modified workaround and problem solved
Sent from my SGH-M919 using Tapatalk 2

jbreeze228 said:
Go into the Triangle Away app and check system modified workaround and problem solved
Sent from my SGH-M919 using Tapatalk 2
Click to expand...
Click to collapse
This. It explains this right in the app.

jbreeze228 said:
Go into the Triangle Away app and check system modified workaround and problem solved
Sent from my SGH-M919 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for pointing me in the right direction. I went ahead and got SuperSU Pro because that's the only way the feature in Triangle Away will work. It was after 2am when I was rooting and having problems so I wasn't too sharp.
Thanks!