Database Info

[Q] So confused...

I have completely screwed my phone. I have rooted and ROM'ed at least 5 Android phones in the past.
This one is simply ridiculous.
I have used ODIN and had no problems. Now when I flashed my rom through CWM it just flashes a Samsung screen.
I have redone everything 10 times I am doing everything correctly.
I have tried different ROMs different kernels, same thing every time.
I am lost, and need help PLEASE!

Did you flash a pit file? Repartitioning usually does the trick.
Sent from my SCH-I510 using Tapatalk

Now that I've wiped my phone, how do I disable the voodoo lagfix without being able to do anything on the phone so I can install a ROM? This doesn't make sense to me.

ilovesoad said:
Did you flash a pit file? Repartitioning usually does the trick.
Sent from my SCH-I510 using Tapatalk
Click to expand...
Click to collapse
I'm sorry I don't know what that is.

mjdato said:
I'm sorry I don't know what that is.
Click to expand...
Click to collapse
Check out this thread for info on (and to get) the pit file.

I did this and now my phone will not boot up at all...

This phone is a total piece...

mjdato said:
This phone is a total piece...
Click to expand...
Click to collapse
No, you just do not know what your doing, simple as that. Tons of people here and elsewhere have no problems. You haven't listed what roms and kernels you are trying. My guess is either using froyo rom with GB kernel or not using odin right, it's pretty easy to use but also easy to get wrong, I suggest actually taking some time to learn what to do and what everything is. It's evident you are very impatient by your constant posts in this thread and their content which implies you didn't take the proper time to research what you are doing and how it all works. With some actual useful information like rom and kernel we could probably help

I've been researching this phone and the tools for a week now, and started this process at 1PM, so no im not impatient.
This phone is a piece. It was bad when it came out and it still is crap. I've rooted, Rom'ed and modded every Android phone I've ever had with no issue. Different carriers, different manufacturer's. Never had an issue.
Now, thanks for the lecture Dad, if you have any insight as to why my phone will not boot up after flashing the pit file it would be much appreciated, if not, troll somewheres else.
Thanks!

mjdato said:
if you have any insight as to why my phone will not boot up after flashing the pit file it would be much appreciated, if not, troll somewheres else.
Thanks!
Click to expand...
Click to collapse
Are you drunk? Maybe try again when you sober up?
Sent from my mobile office.

What roms and kernals have you tried?
Are you making sure that you are using the PDA option in Odin instead of phone?
Are you using the PIT option with the right boxes checked/unchecked?
Give us a little more insight on what you have done and what you are trying to do and we will do our best to help you out.
Sent from my SCH-I510 using XDA App

mjdato said:
I've been researching this phone and the tools for a week now, and started this process at 1PM, so no im not impatient.
This phone is a piece. It was bad when it came out and it still is crap. I've rooted, Rom'ed and modded every Android phone I've ever had with no issue. Different carriers, different manufacturer's. Never had an issue.
Now, thanks for the lecture Dad, if you have any insight as to why my phone will not boot up after flashing the pit file it would be much appreciated, if not, troll somewheres else.
Thanks!
Click to expand...
Click to collapse
If you have been researching this phone for weeks wouldn't you have known if it were a piece of #### before you bought it? So far I like the phone very light and reliable. Definitely needs root though the original software is terrible.

jfl14609 said:
If you have been researching this phone for weeks wouldn't you have known if it were a piece of #### before you bought it? So far I like the phone very light and reliable. Definitely needs root though the original software is terrible.
Click to expand...
Click to collapse
If I'm not mistaken when you use a pit file you have to Odin a new rom right after. It wipes everything off the partitions.but I've only used a pit one time so may be wrong . The first few times I flashed this phone I had problems but eventually I caught everything that usually causes a problem. And I was just like you, had been flashing evo, incredible and hero for a long time with no problem. But Samsung gave me a headache. But i was stuck in a bootloop and nothing would flash. I ran the pit then flashed a new tar file and she booted up fine
Didn't mean to quote that post. Oops

Please use the Q&A Forum for questions Thanks
Moving to Q&A

It was given to me by my job. I didn't have a choice if I wanted my bill paid for every month.

Ok, so I have tried:
0808_charge_overclock
NAMELESS_Kernel_Cleanup_Script
ROMS i have tried:
Altered BeastAlpha 5
Eclipse_TW4_v1.1
humble50_rc2

At this point it will not charge or boot up into anything so I'm not sure if it's even recoverable right now....where should I even start?

mkarps said:
Are you drunk? Maybe try again when you sober up?
Sent from my mobile office.
Click to expand...
Click to collapse
I truly wish I was. LOL

mjdato said:
Ok, so I have tried:
0808_charge_overclock
NAMELESS_Kernel_Cleanup_Script
ROMS i have tried:
Altered BeastAlpha 5
Eclipse_TW4_v1.1
humble50_rc2
Click to expand...
Click to collapse
Well since u partitioned with the pit. Ur phone is sitting there with nothing on it. No rom, no kernel,recovery etc. So i know humble 5 wont work cuz it doesn't include a kernel. Humble 4 will however work. It includes a kernel and a recovery .have u did everything in the "Hoe to fix your phone "thread on top of development section?

mjdato said:
At this point it will not charge or boot up into anything so I'm not sure if it's even recoverable right now....where should I even start?
Click to expand...
Click to collapse
I've had problems at times getting my phone into download mode. Just gonna toss some stuff out there as I'm sure there are people that know more than me. Is there anyway you can have a charged or extra battery charged? I would hmm uninstall the samsung drivers etc..or atleast re install so your phone is recognized when you plug it in the usb. So you can get your phone into download mode and Odin doesnt see it? Have you followed the directions in the stickys on the Dev page to a T? Im sure you have tried all usb ports,different cable, hell different computer. If you still can't get it back up as many have posted they haven't seen to many totally bricked phones I would love to have something to just play around with. If you dont have insurance and cant get it exchanged let me know. Pretty sure though more people will chime in and get things working though.

[Q]Flashing roms help

I have a stock Infuse 4g from AT&T and I would like a step by step, like a tutorial of everything I have to do for flashing custom roms, what to backup, installing CWM, etc. Thanks.

http://forum.xda-developers.com/showthread.php?t=1514886
[REF] Super Infuse Noobie Question Thread. Lots of questions answered
Sent from my SAMSUNG-SGH-I997 using xda premium

Yes, I know about that thread, but they don't answer all of my questions, like for example: I have stock GB, do I still root with super one click? What is the first step in flashing custom roms, rooting and then installing CWM? How do I install CWM? What to use to backup apps? What is Rom manager from the android market and what is it for, is it useful? How to backup contacts? Before flashing, should I remove the sim card? When flashing, is it always done in CWM? If so, what's the exact process?
What I want is more of a fool proof step by step, just to make sure everything goes as smoothly as possible. I had to use Heimdall's one click back to stock to go from froyo to GB UCKJ4 because of the boot loop even though the phone wasn't rooted or anything, it was stock. If I did that, what are my options? What should I do if I want to flash custom roms from scratch? Also, CWM is kept even after a factory reset or a wipe? it doesn't get deleted in any way when you want ti flash another Rom?

Wow, I'm sorry but you should do some research first before you ask these questions. Google has an excellent feature called search. I'm sure if you use it you can find your answers as they have all been asked before. Everything I have learned has been from reading and rereading everything I could before I attempted rooting. Android central has a great guide to everything root. Then come back with questions. Sorry to go off but it seems like people just come here to have their hand held. I'm sure you could find someone to donate to on here that would take you by the hand if that's the route you choose.
Sent from my ADR6425LVW using XDA App

Silvares said:
I have a stock Infuse 4g from AT&T and I would like a step by step, like a tutorial of everything I have to do for flashing custom roms, what to backup, installing CWM, etc. Thanks.
Click to expand...
Click to collapse
Hmm. So how much are you willing to pay for someone who takes time to consolidate this guide. Make it worthwhile for us too

Do I get dibs on this?

qkster said:
Do I get dibs on this?
Click to expand...
Click to collapse
Lol... you may... I only asked that so maybe he would find someone to spoon feed him

diablo009 said:
Lol... you may... I only asked that so maybe he would find someone to spoon feed him
Click to expand...
Click to collapse
lol..somewhere in this thread is the spoon...just have to know where to look.

"There is no spoon."
Sent from my Transformer TF101 using Tapatalk

rxnelson said:
"There is no spoon."
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
He was referring to the link in post 2 by bigjoe.

diablo009 said:
He was referring to the link in post 2 by bigjoe.
Click to expand...
Click to collapse
Yea, I was just goofing. Qksters bald avatar and all the spoon talk reminded me of the matrix....thought someone would get it. Ah well.
Sent from my SAMSUNG-SGH-I997 using Tapatalk

Anyway, thanks qkster, with your Heimdall to UCBL3 and CWM installation I was able to do it. And now I have ZEUS on my Infuse :3.
Now, what are some must have apps rooted or not?

Silvares said:
Anyway, thanks qkster, with your Heimdall to UCBL3 and CWM installation I was able to do it. And now I have ZEUS on my Infuse :3.
Click to expand...
Click to collapse
good job..
See how easy it was?
Anyway, lol..the spoon was on all my signature links

Let me just throw this out there: as a noob myself, I understand where op is coming from. On forums this large, it is easy to get lost. I also find that I spend so much time reading things that don't answer my questions. I know that's part of the process though, but can feel pretty overwhelming.
May I suggest that not just 1 person has to answer all the questions. Maybe u come across a post like this and answer just 1 or 2 questions, or paste in a link or 2 to where the specific question is answered.
Also, I know that I've asked a question in the most appropriate place & someone has come back saying it's not the right place, even though it's in the q&a - noob - device forum. It's just hard at first. So, pls, don't bust op's chops too bad, b/c somewhere on here it says that it helps everyone if anyone takes some of their time to educate.
Sent from my SAMSUNG-SGH-I997 using XDA
---------- Post added at 03:55 PM ---------- Previous post was at 03:08 PM ----------
Noob here too, but I have done some of this successfully, and then I played around too much and really, really bricked my phone - but fixed it, so I have learned a bit. These are my thoughts:
Silvares said:
I have stock GB, do I still root with super one click?
Click to expand...
Click to collapse
Yes. Get rooted. I've used S-O-C twice. Had to play around with it first. I think I ended up being successful by doing it thru my phone, not on the PC.
Silvares said:
What is the first step in flashing custom roms, rooting and then installing CWM? How do I install CWM?
What to use to backup apps? How to backup contacts?
Click to expand...
Click to collapse
1st step - root, then - backup more than just 1 way-use some from market and put things in more than 1 place; Titanium Backup seems to be standard around here too. Here is a great youtube link that helped me a lot to prepare: http://youtu.be/ozNVeGPUlU8
Silvares said:
What I want is more of a fool proof step by step, just to make sure everything goes as smoothly as possible.
Click to expand...
Click to collapse
Doesn't exist. Try to find a good youtube and follow along.
Silvares said:
I had to use Heimdall's one click back to stock to go from froyo to GB UCKJ4 because of the boot loop even though the phone wasn't rooted or anything, it was stock. If I did that, what are my options?
Click to expand...
Click to collapse
When I got bricked last night, after trying 2 methods and much freaking out, GTG worked. Working link for that download is here: http://www.mediafire.com/?i57410xodydx5l1. Thread here → http://forum.xda-developers.com/showthread.php?t=1116251
Silvares said:
Also, CWM is kept even after a factory reset or a wipe? it doesn't get deleted in any way when you want ti flash another Rom?
Click to expand...
Click to collapse
It stayed for me, even through brick.
I know you got your questions answered, but maybe this will help you, or someone else, in the future. Again, I'm no expert - far from it - but this is what worked for me. Good luck!

Can't think of another way of saying this...HELP!
So, I was able to get 3e and clockworkmod recovery installed on my Infuse. (A great accomplishment for me, trust me)
I went through the process of wiping data and caches to install my new ROM but I put the two zips (Cyan7 & Google Apps) on the external sdcard so when I went to install them I couldn't see them. I thought my only option then was to chose to restore from backup in CM recovery and now I'm stuck on the Samsung boot logo.
I tried a battery pull and VOLup/VOLdwn/POWER to try to get into recovery but I'm still stuck on the boot logo. What can I do now?
I'd really appreciate your help. Cheers.

feroxcvpiditas said:
So, I was able to get 3e and clockworkmod recovery installed on my Infuse. (A great accomplishment for me, trust me)
I went through the process of wiping data and caches to install my new ROM but I put the two zips (Cyan7 & Google Apps) on the external sdcard so when I went to install them I couldn't see them. I thought my only option then was to chose to restore from backup in CM recovery and now I'm stuck on the Samsung boot logo.
I tried a battery pull and VOLup/VOLdwn/POWER to try to get into recovery but I'm still stuck on the boot logo. What can I do now?
I'd really appreciate your help. Cheers.
Click to expand...
Click to collapse
No need to recover. Simple enough. U've tried restarting normal, and it didn't work?

No unfortunately...
I'm stuck on the Samsung boot logo. I think my battery pull after being frozen after the restore didn't help matters. I've tried vol+/vol-/power and vol-/power and still can't get into recovery. Plugged into my MAC it's not recognized.

feroxcvpiditas said:
I'm stuck on the Samsung boot logo. I think my battery pull after being frozen after the restore didn't help matters. I've tried vol+/vol-/power and vol-/power and still can't get into recovery. Plugged into my MAC it's not recognized.
Click to expand...
Click to collapse
Well, if it were me, I'd pull batt and let it sit while I search this site to see what other people have done when stuck in the loop. You're sure to find answers somewhere in/related to being bricked threads, though I'm sure you're not bricked, so relax and take a breath. I'd offer other suggestions, but I'm too new, so it'd just be speculation on my part.

dde333 said:
Well, if it were me, I'd pull batt and let it sit while I search this site to see what other people have done when stuck in the loop. You're sure to find answers somewhere in/related to being bricked threads, though I'm sure you're not bricked, so relax and take a breath. I'd offer other suggestions, but I'm too new, so it'd just be speculation on my part.
Click to expand...
Click to collapse
Cheers, I think I will do that. I'm feverishly scouring the site and the interweb...I just hope I don't have to re-flash a stock ROM and start all over again. Of course that would be better than having a paperweight I suppose.
---------- Post added at 07:56 PM ---------- Previous post was at 07:46 PM ----------
Well, I got into Download mode using the vol+/vol- then usb plugin. Just don't know what to do next. At least something is happening...back to my research...

feroxcvpiditas said:
Cheers, I think I will do that. I'm feverishly scouring the site and the interweb...I just hope I don't have to re-flash a stock ROM and start all over again. Of course that would be better than having a paperweight I suppose.
---------- Post added at 07:56 PM ---------- Previous post was at 07:46 PM ----------
Well, I got into Download mode using the vol+/vol- then usb plugin. Just don't know what to do next. At least something is happening...back to my research...
Click to expand...
Click to collapse
fero,
you dont need to look very far...
http://forum.xda-developers.com/showthread.php?t=1524081
the link to unbrick and how to has always been right on my signature links...
read my beginner guide...

[Q] Does anyone know what's wrong with this screen?

I was trying to update my mom's Infuse to ICS, then all of a sudden this (attached) happened. Heimdall had just given me the libusb.dll error (I needed to update the bootloader cause I kept getting rainbows in CWM), so I was unplugging the phone so I could get the right drivers.
I have a horrible feeling I did something very wrong. I can't imagine why what I was doing would have caused this though, since the cmd had gone back to a default state after giving the error.
Is there any way to fix this?? Thanks a ton in advance!

mvgc3 said:
I was trying to update my mom's Infuse to ICS, then all of a sudden this (attached) happened. Heimdall had just given me the libusb.dll error (I needed to update the bootloader cause I kept getting rainbows in CWM), so I was unplugging the phone so I could get the right drivers.
I have a horrible feeling I did something very wrong. I can't imagine why what I was doing would have caused this though, since the cmd had gone back to a default state after giving the error.
Is there any way to fix this?? Thanks a ton in advance!
Click to expand...
Click to collapse
can you get it into download mode...?
if so run the one click again and you might have to check the box for bootloaders, on the second run...meaning I would run it twice...

It does that immediately on power up. Doesn't even get to the Samsung screen. Odin will recognize the phone, but when I try to flash a return to stock package (which I used earlier perfectly fine), it says the md5 is invalid.
Like I said, I never even got to the point of installing the bootloader since I forgot about the drivers. Are you saying I should install the drivers and try to flash the bootloader again?
Thanks so much for the help! I've never had this much trouble with a phone before
EDIT: I'm a dumbass. since I couldn't see the screen, I forgot to press up again after entering download mode. Odin is now in the process of installing the aforementioned return to stock package. And I think it worked!
You have no idea how grateful I am of you for pointing that out! I feel kind of dumb for not trying it, but when the screen looked like that I could only assume there was no functionality!
THANKS AGAIN! Times a million!

Lol ok let us know when you get it up and running....kk
Sent from my SAMSUNG-SGH-I717 using xda premium

What EXACTLY gave you the idea to put your mother's phone on a ROM that half works and has many bugs? Just trying to understand... I could have done this to my friend's mom's atrix, but I didn't because the stock ROM will always have the least bugs for unpopular devices like ours. (ones that don't get official support for CM or AKOP or anything)

wayzata said:
What EXACTLY gave you the idea to put your mother's phone on a ROM that half works and has many bugs? Just trying to understand... I could have done this to my friend's mom's atrix, but I didn't because the stock ROM will always have the least bugs for unpopular devices like ours. (ones that don't get official support for CM or AKOP or anything)
Click to expand...
Click to collapse
whooo there...slow your roll...
the op has the options to put what he wants, and actually if you have been tracking the ICS/CM9/AOKP threads they have made leaps in the smashing of bugs....actually very stable and good to go now, seeing how just months ago we didn't even have any ver of ICS, and yes it takes homework to install..
and you kept stock on your friends Mommy phone well that was between you and him and Mommy...
so long story short....as far as unpopular, I see this device being sold and for a high demand on CL and Ebay...with all the support given here...that is my IMHO...as is yours

+10 Char

bigjoe2675 said:
whooo there...slow your roll...
the op has the options to put what he wants, and actually if you have not been tracking the ICS/CM9/AOKP threads they have made leaps in the smashing of bugs....actually very stable and good to go now, seeing how just months ago we didn't even have any ver of ICS, and yes it takes homework to install..
and you kept stock on your friends Mommy phone well that was between you and him and Mommy...
so long story short....as far as unpopular, I see this device being sold and for a high demand on CL and Ebay...with all the support given here...that is plenty IMHO...as is yours
Click to expand...
Click to collapse
This makes about as much sense in English as it does in Japanese.

wayzata said:
This makes about as much sense in English as it does in Japanese.
Click to expand...
Click to collapse
You are a smart guy... i am sure you understood me....
Arigatou gozaimasu btw...just leave it as that....

Hajimemashita Joe sama
Sent from my SGH-I997 using xda premium

mvgc3 said:
I was trying to update my mom's Infuse to ICS, then all of a sudden this (attached) happened. Heimdall had just given me the libusb.dll error (I needed to update the bootloader cause I kept getting rainbows in CWM), so I was unplugging the phone so I could get the right drivers.
I have a horrible feeling I did something very wrong. I can't imagine why what I was doing would have caused this though, since the cmd had gone back to a default state after giving the error.
Is there any way to fix this?? Thanks a ton in advance!
Click to expand...
Click to collapse
Same thing happened to mine when i flashed back to stock. Kept trying download mode and finally worked. Keep trying and also try recovery. Worked for me
Sent from my SAMSUNG-SGH-I717 using xda premium

wayzata said:
What EXACTLY gave you the idea to put your mother's phone on a ROM that half works and has many bugs? Just trying to understand... I could have done this to my friend's mom's atrix, but I didn't because the stock ROM will always have the least bugs for unpopular devices like ours. (ones that don't get official support for CM or AKOP or anything)
Click to expand...
Click to collapse
First of all, every once in a while, she asks me if there are any updates yet.
Second, there's only a short list of insignificant bugs mentioned in the ICS topics.
I flashed GB on it a while back, and I figured since CWM and everything was set up already I wouldn't have a problem; flash, reboot, flash again, done. Unfortunately, it wasn't flashing the second time for whatever reason, and I figured it had something to do with the now half-functional CWM.
Anyway, to those of you who weren't unreasonably judging me, and rather decided to help: Thank you, the phone is now back up and running!

Prometh1216 said:
Hajimemashita Joe sama
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
LOL, woooooooootttttttt

Same thing happened to me. What I did was send my phone back to Samsung tell them everything ( except about rooting) they will email you a label then ship it off and get back in about 1 week. They will put stock gingerbread on it. Hopes this helps.
Sent from my SAMSUNG-SGH-I997 using Tapatalk 2

Accidentally tried to flash International ROM, help.

On my Verizon GS3.
I was using a stock-rooted ROM, and then today tried to install the latest wanamlite.
Even though it says No Wipe, I did just to be safe in CWM (or so I thought).
When trying to flash the ROM, I got the "assert failed:write_raw_image("/tmp/boot.img","boot")" error , and I remember seeing a (status 7) error
Then I tried to reboot... and then nothing but a black screen.
I've tried the Volume Down + Home + Power button to get into "Download Mode" with no success.
I would appreciate any help towards getting this rom on my device.
PS. I've searched, and read these threads
- http://forum.xda-developers.com/show....php?t=1045887
- http://forum.xda-developers.com/show....php?t=1767226
- http://forum.xda-developers.com/show....php?t=1526599

Have you taken out the battery and waited at least 5 minutes to if you can get it to download mode?

First - wrong forum. This should be in Q/A
Second - What? You can't flash international ROMS on a US Version of the S3. Your phone is probably hard bricked if you can't turn it on or get into download mode.Try charging it for a while, and a battery pull at some point but if you still can't turn it on, it's a paperweight. Read up next time before flashing. Looks like you need a JTAG.
Spend $60 here to get it fixed.
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-iii-jtag-brick-repair/

^Wasn't sure if this was right or wrong, has to do with Roms, but you're right. If I can move it myself, I will.
And you're right again with that second statement. I didn't successfully flash the international rom, but attempted to, and messed up.
Thanks for the repair link, I'll have to consider that if I can't fix it myself.

AB_ said:
^Wasn't sure if this was right or wrong, has to do with Roms, but you're right. If I can move it myself, I will.
And you're right again with that second statement. I didn't successfully flash the international rom, but attempted to, and messed up.
Thanks for the repair link, I'll have to consider that if I can't fix it myself.
Click to expand...
Click to collapse
Best of luck. If it's a hard brick you probably will have to send it in. JTAG requires some technical expertise and equipment, but it's around $60 (not sure about shipping) so it's a lot better than buying a new phone. If you could turn your phone on but not get into download mode, a USB jig could possibly work.

You can't go to download, but can you get back to recovery? Also, development thread isn't for things related to ROMs but for releases. Also remove your battery plug your phone in, put the battery back in and watch the led, what color does it turn?
Sent from my SCH-I535 using xda app-developers app

ODIN?

Best chance of help and not to get flamed is to not post a thread in development
Read forum rules and stickies before posting
Questions go in Q&A
Thread Moved
FNM

Zalithian said:
Best of luck. If it's a hard brick you probably will have to send it in. JTAG requires some technical expertise and equipment, but it's around $60 (not sure about shipping) so it's a lot better than buying a new phone. If you could turn your phone on but not get into download mode, a USB jig could possibly work.
Click to expand...
Click to collapse
Appreciate it man.
I see someone on eBay offering a fix for $30. Thanks for notifying me about this service existing.
kintwofan said:
You can't go to download, but can you get back to recovery? Also, development thread isn't for things related to ROMs but for releases. Also remove your battery plug your phone in, put the battery back in and watch the led, what color does it turn?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Can't go into recovery. And I'll remember that for now on, just having an off day.
With the battery and the SD card both out, and with the phone plugged in, the LED is red. It turned off after a while.
And thanks Kenny.

AB_ said:
Appreciate it man.
I see someone on eBay offering a fix for $30. Thanks for notifying me about this service existing.
Can't go into recovery. And I'll remember that for now on, just having an off day.
With the battery and the SD card both out, and with the phone plugged in, the LED is red. It turned off after a while.
And thanks Kenny.
Click to expand...
Click to collapse
Ya sorry, was just giving you a heads up. And the red light means it's hard bricked. I'll try to find the reference for you, but sorry.
Sent from my SCH-I535 using xda app-developers app

kintwofan said:
Ya sorry, was just giving you a heads up. And the red light means it's hard bricked. I'll try to find the reference for you, but sorry.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
It's all good, no reference needed.
$30 doesn't seem too bad, not as bad as being 2 weeks without this phone.. (especially when the only backup phone I have available with me is an Omnia .. :crying:

AB_ said:
It's all good, no reference needed.
$30 doesn't seem too bad, not as bad as being 2 weeks without this phone.. (especially when the only backup phone I have available with me is an Omnia .. :crying:
Click to expand...
Click to collapse
$30 is better than $60, but the other place seems pretty reliable with quick turnaround. I don't know how legit that ebay place is, so maybe it's worth it to pony up a little extra.

Zalithian said:
First - wrong forum. This should be in Q/A
Second - What? You can't flash international ROMS on a US Version of the S3. Your phone is probably hard bricked if you can't turn it on or get into download mode.Try charging it for a while, and a battery pull at some point but if you still can't turn it on, it's a paperweight. Read up next time before flashing. Looks like you need a JTAG.
Spend $60 here to get it fixed.
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-iii-jtag-brick-repair/
Click to expand...
Click to collapse
This is Q&A...

CovXX said:
This is Q&A...
Click to expand...
Click to collapse
Look at post #8 by the Moderator on page 1 of this thread. Thread was originally posted in Development section and moved to Q & A

CovXX said:
This is Q&A...
Click to expand...
Click to collapse
Yea, I mistakenly posted this in the Development section.

I would highly suggest trying the USB jig, I've heard you can get them for a few bucks on ebay, so it'd be worth a shot. If your skilled with electronics you can make a simply USB adapter with a 300k Ohm resistor across the data pins.
---------- Post added at 09:07 PM ---------- Previous post was at 09:06 PM ----------
And just a general question about hard bricks, how does one prevent their phone from entering download mode unless they flashed something over the bootloader/download partition? Or do many international roms typically include the boot partition in them?

noingwhat said:
I would highly suggest trying the USB jig, I've heard you can get them for a few bucks on ebay, so it'd be worth a shot. If your skilled with electronics you can make a simply USB adapter with a 300k Ohm resistor across the data pins.
---------- Post added at 09:07 PM ---------- Previous post was at 09:06 PM ----------
And just a general question about hard bricks, how does one prevent their phone from entering download mode unless they flashed something over the bootloader/download partition? Or do many international roms typically include the boot partition in them?
Click to expand...
Click to collapse
The international S3 has a different partition layout than the us s3. So for example, if the cwm zip that flashes the rom wants to flash a kernel to a partition that is earlier in the boot chain (maybe aboot), then you've now accidentally overwrote the wrong partition.
The easiest way to see exactly what partitions may be affected is to extract rom zip to a folder on your pc and look in the updater-script file (buried in META-INF/com/google/android) that cwm uses to flash the ROM and kernel.
You should see some statements that attempt to mount or write to partitions (mmcblk0p5, mmcblk0p7, etc). If you compare the list of partitions in the ROM's cwm uodater-script to the list of US s3 partitions in the opening post of Adam's Bootloader Unlocking thread (in the original development forum), you could see where things went wrong (e.g. accidentally flash a kernel to mmcblk0p5 instead of mmcblk0p7, etc).
Also, keep in mind that some partitions are smaller than others so writing could have poured over into an adjacent partition.
Sent from my SCH-I535 using xda premium

[Q] I think my phone is bricked

as title states hard bricked after install of orthus eight then rebooted and nothing. followed instructions and still bricked. i have flashed many roms i don't know what went wrong with this flash. Will a jig work to unbrick to download mode? I have tried several methods to get into download and cant seem to succeed.

Re: [Q] Orthus eight hard bricked phone
I don't think the rom had anything to do with it. I've flashed it and it's fine.
What was the best thing before sliced bread?

baddogie said:
as title states hard bricked after install of orthus eight then rebooted and nothing. followed instructions and still bricked. i have flashed many roms i don't know what went wrong with this flash. Will a jig work to unbrick to download mode? I have tried several methods to get into download and cant seem to succeed.
Click to expand...
Click to collapse
What exactly did you do? And don't just say, "I followed the instructions." I need to know exactly what you did every step of the way from downloading Orthus Eight to laying the cornerstone of your new brick house.
I'll ask this first obvious question because so often it reveals the true problem: what kind of phone do you have?

Lets not go straight in to flaming a user just because he has no posts. I know for a fact there is a brick problem in AOSP 4.2.2. Lets hear him out.

baddogie said:
Will a jig work to unbrick to download mode?
Click to expand...
Click to collapse
I'm not an expert but if you really hard brick the phone then jig would be your solution.
You may want to read the posts on "[ROM][10.1]SUPERLITE CM10.1 JB 4.2.2 > 79mb < | SLGAPPS 10MB | FEB28/13" page 2 and 3 and try to get in touch with the user who bricked the phone and was going to try "JTAG brick repair"
BTW I also installed the ROM and is working smooth.
P.S. I don't think anyone is blaming Ortus8 ROM while the question ... and request for support ... was regarding jig

Re: [Q] Orthus eight hard bricked phone
prbassplayer said:
Lets not go straight in to flaming a user just because he has no posts. I know for a fact there is a brick problem in AOSP 4.2.2. Lets hear him out.
Click to expand...
Click to collapse
A Randomly appearing brick that only affects some and not others this i want proof of sir mod or not i want validation.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
---------- Post added at 05:28 AM ---------- Previous post was at 05:27 AM ----------
err1max1 said:
I'm not an expert but if you really hard brick the phone then jig would be your solution.
You may want to read the posts on "[ROM][10.1]SUPERLITE CM10.1 JB 4.2.2 > 79mb < | SLGAPPS 10MB | FEB28/13" page 2 and 3 and try to get in touch with the user who bricked the phone and was going to try "JTAG brick repair"
BTW I also installed the ROM and is working smooth.
P.S. I don't think anyone is blaming Ortus8 ROM while the question ... and request for support ... was regarding jig
Click to expand...
Click to collapse
A jig does nothing for a hard brick. You don't need a jig to get to DL mode if soft brick. In short a jig is worthless.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

mtdew said:
A Randomly appearing brick that only affects some and not others this i want proof of sir mod or not i want validation.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
---------- Post added at 05:28 AM ---------- Previous post was at 05:27 AM ----------
A jig does nothing for a hard brick. You don't need a jig to get to DL mode if soft brick. In short a jig is worthless.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
In my opinion it has to do with the kernel, course I could be wrong. However I had 2 testers brick with CM's kernel. I've seen similar reports with the 4.2.2 AOKP around here. In the 2 cases I'm sure the phone booted and ran fine, then randomly locked up and dead. No life afterwards. I understand we all make mistake by both my testers where doing something different when it happen, and the fact the device booted fine THEN bricked (again my particular case) means it flashed fine and whole booted something happen (I believe it blew partitions, possibly secondary or third, if this device has a third, bootloader). If I had any better proof I would have found a solution, or tried to already.

Re: [Q] Orthus eight hard bricked phone
prbassplayer said:
In my opinion it has to do with the kernel, course I could be wrong. However I had 2 testers brick with CM's kernel. I've seen similar reports with the 4.2.2 AOKP around here. In the 2 cases I'm sure the phone booted and ran fine, then randomly locked up and dead. No life afterwards. I understand we all make mistake by both my testers where doing something different when it happen, and the fact the device booted fine THEN bricked (again my particular case) means it flashed fine and whole booted something happen (I believe it blew partitions, possibly secondary or third, if this device has a third, bootloader). If I had any better proof I would have found a solution, or tried to already.
Click to expand...
Click to collapse
I find it hard to believe this was random or attributed to to cm's kernel if nothing else it would be based on something particular to their hardware or your build as you would see a ton of these on cm's thread. You are placing blame in an unlikely place as well.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

Re: [Q] Orthus eight hard bricked phone
mtdew said:
I find it hard to believe this was random or attributed to to cm's kernel if nothing else it would be based on something particular to their hardware or your build as you would see a ton of these on cm's thread. You are placing blame in an unlikely place as well.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Well I was using cms device folders and my qcom hardware folders are constabtly updated with cms commits. Only difference are overlays files and that we use slim.mk which is mostly a copied cm.mk only fixed source locations. Don't know what I did different to create a brick zip. Not my first rodeo, though I'm no expert that's for sure.
Sent from my Nexus 4 using Tapatalk 2

Re: [Q] Orthus eight hard bricked phone
prbassplayer said:
Well I was using cms device folders and my qcom hardware folders are constabtly updated with cms commits. Only difference are overlays files and that we use slim.mk which is mostly a copied cm.mk only fixed source locations. Don't know what I did different to create a brick zip. Not my first rodeo, though I'm no expert that's for sure.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Again if it was cm's doing this would be far more widespread. Something's not adding up, also several people have successfully flashed orthus this is user error nothing more.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

mtdew said:
Again if it was cm's doing this would be far more widespread. Something's not adding up, also several people have successfully flashed orthus this is user error nothing more.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Mate Tell me something I don't know. Same thing with Slim. My test builds where flashed by 50+ people only 2 bricked, so happen both I had most communication with as they where helping me debug the camera problem I had. Like I said if I had a better idea of where the problem laid I wouldn't have stopped working with it (I still fiddle with the code) I just don't have any concrete evidence to work with to merit the chance of bricking other members devices. I originally thought it was me but not the case. There has been posts about this happening on AOKP, I believe on CM (not sure if it was here or not). I'm not saying its a wide spread problem, however its there.

Re: [Q] Orthus eight hard bricked phone
Aokp for this device? Cm for this device? Were the members who bricked very experienced? I'm not saying you don't know what you're talking about but i never trust testers and i especially don't trust people saying such and such ROM bricked my device. I've seen this all too often and all it does is spread fear and give good devs bad names.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

Re: [Q] Orthus eight hard bricked phone
Just as an fyi, I loaded Orthus onto my skyrocket just now. Booted fine, restoring apps now
Sent from my SGH-I317 using Tapatalk 2

Re: [Q] Orthus eight hard bricked phone
Been running it since it dropped absolutely no issues smoothest 4.2.2 ROM out.
Sent from my SGH-I727 using xda premium

Re: [Q] Orthus eight hard bricked phone
I'd love to try and help this user.
What methods have you tried to get into download mode?
You said you can reboot, then get nothing. Is that a blank screen? Does the backlight come on?
What recovery were you on? What steps to flash?
Can you get to the device via adb?
Even if I can't help you, maybe we can narrow down the issue.. Whatever it may be.
Sent from my SGH-I727 using Tapatalk 2

damn another brick bug, i thought it was all done with
as for blaming the op, if he had the sr and flashed an sr rom whichever rom that would be, we cant blame the op since theres nothing he could do wrong to actually hardbrick the phone , yes he could softbrick but not hardbrick it.
definition of the bug imo is its totally random, 1 out of x phones it will happen to

T.J. Bender said:
What exactly did you do? And don't just say, "I followed the instructions." I need to know exactly what you did every step of the way from downloading Orthus Eight to laying the cornerstone of your new brick house.
I'll ask this first obvious question because so often it reveals the true problem: what kind of phone do you have?
Click to expand...
Click to collapse
I have a samsung galaxy s2 skyrocket sigh i727. I downloaded the rom from the forums here (i think the link was goo.im) and transfered to my internal sd. I wiped data factory reset, wiped cache patroon, wiped system, wiped delvil cache then flash downloaded zip and half way through the android in background fell over and triangle showed up. I tried restoring backups and eving wiping did not work so I went to advance and restart recovery and the device turned off and now will not respond to anything.

Re: [Q] Orthus eight hard bricked phone
Be careful with goo. I've never been sure what I've downloaded from it.
Most likely not a problem with the rom.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

mtdew said:
Aokp for this device? Cm for this device? Were the members who bricked very experienced? I'm not saying you don't know what you're talking about but i never trust testers and i especially don't trust people saying such and such ROM bricked my device. I've seen this all too often and all it does is spread fear and give good devs bad names.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
I'm not trying to give any dev a bad name I was just trying to specify what rom I was flashing when this happend

baddogie said:
I have a samsung galaxy s2 skyrocket sigh i727. I downloaded the rom from the forums here (i think the link was goo.im) and transfered to my internal sd. I wiped data factory reset, wiped cache patroon, wiped system, wiped delvil cache then flash downloaded zip and half way through the android in background fell over and triangle showed up. I tried restoring backups and eving wiping did not work so I went to advance and restart recovery and the device turned off and now will not respond to anything.
Click to expand...
Click to collapse
OK. Moving the file from external to internal could cause a corruption. It could have been a bad DL from the start. Hence the reason checking MD5s is so imortant. Either way you should still be able to enter recovery. No ROM that is flashable touches the recovery partition. Pull out your external sdcard and access it with a comp. Copy that files full name here.