Related
I look at some forums on how to do it and I'm pretty positive I can do it. But what exactly are the risks?
Is there a chance of brick?
Will I lose data?
Is it even a necessary upgrade?
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Yes, there is a chance for a brick but that is rather minimal. It's the same risk that you take each time you use ODIN one click to return to stock.
Before you flash be sure to do a backup using TiBu for your apps and I use "export to external SD card" for my contacts.
Necessary upgrade? That is all up to you to decide. I did it because I wanted something new.
McKillroy11 said:
I look at some forums on how to do it and I'm pretty positive I can do it. But what exactly are the risks?
Is there a chance of brick?
Will I lose data?
Is it even a necessary upgrade?
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
1.Of coarse there is a chance of a brick. Anytime you flash your device there is a potential of something going wrong. Doesn't happen that often, but it does happen. Luckily, we have lots of ways of getting out of a jam.
2.You shouldn't lose any data if you back up properly. If you need to use a computer and manually drag your pictures and music or whatever to a safe spot, or like the user above me use TiBu and make a backup of your apps and data and stuff.
3.It is not a necessary upgrade, but it is indeed exactly that.. an "upgrade"
I'm not gonna talk up which gingerbread ROMs I like, but I will say i cannot go back to froyo. The smooth, lag-free experience i have had with gingerbread has been more than pleasant.
But as always read the OP and instructions...and of coarse re-read just to be sure.
Like Nike, just do it.
Coreym said:
1.Of coarse there is a chance of a brick. Anytime you flash your device there is a potential of something going wrong. Doesn't happen that often, but it does happen. Luckily, we have lots of ways of getting out of a jam.
Click to expand...
Click to collapse
1. Is not true. You DON'T risk bricking EVERYTIME you flash ANYTHING. The only time you risk a brick (and I mean brick as in not a thing coming out of the phone, nothing not one little sign of life at all. Nothing. Anything other than that is NOT a brick) is when you are flashing bootloaders, but if you are not flashing bootloaders, which most of the time you aren't you can not brick the worst that can happen is a situation that is commonly (and stupidly) called a "soft brick" that's just when something is broken and it can't boot all the way to a functioning OS, but again that example isn't a brick at all because it's 99.9% of the time recoverable.
OP you are flashing bootloaders so in this case there is a small risk of a brick. But like was said it's the exact same risk as odin one click.
studacris said:
1. Is not true. You DON'T risk bricking EVERYTIME you flash ANYTHING. The only time you risk a brick (and I mean brick as in not a damn thing coming out of the phone, nothing not one little sign of life at all. Nothing. Anything other than that is NOT a brick) is when you are flashing bootloaders, but if you are not flashing bootloaders, which most of the time you aren't you can not brick the worst that can happen is a situation that is commonly (and stupidly) called a "soft brick" that's just when something is broken and it can't boot all the way to a functioning OS, but again that example isn't a brick at all because it's 99.9% of the time recoverable.
OP you are flashing bootloaders so in this case there is a small risk of a brick. But like was said it's the exact same risk as odin one click.
Click to expand...
Click to collapse
I didn't mean to be so critical .. I more meant to say what I said in my second sentence about something COULD go wrong but thanks for explaining it better for the OP
Sent from my SGH-I897 using XDA Premium App
Even if you do brick it's nothing to freak out about. 9 times out of 10 just putting the phone into download mode and using Odin again does the trick. Even if you need to build/buy a jig, the chances that it's so bricked that you'd need to JTAG it or send it in are ridiculously small.
Superalpaca said:
Even if you do brick it's nothing to freak out about. 9 times out of 10 just putting the phone into download mode and using Odin again does the trick. Even if you need to build/buy a jig, the chances that it's so bricked that you'd need to JTAG it or send it in are ridiculously small.
Click to expand...
Click to collapse
See it's this kind of stuff I'm talking about. This loose use of the term brick.
If you can recover it by any means other than jtag it's not a brick. There are no different degrees of bricking, if it's bricked it doesn't do a anything. Not a single solitary bit of computing, it just sits there doing nothing no matter what. Dead. A corpse.
It's either bricked or not. Just because the kernel/rom is broken and it doesn't boot properly does not mean it's bricked at all. If the bootloaders are intact and it tries to boot but fails at the kernel/rom level that is easily fixed. Throwing the term brick around in that situation, even when you add the retarded "soft brick" modifier, will just scare the poop out of a noob who just needs to remain calm and take the proper steps to have a working phone.
studacris said:
See it's this kind of stuff I'm talking about. This loose use of the term brick.
If you can recover it by any means other than jtag it's not a brick. There are no different degrees of bricking, if it's bricked it doesn't do a damn thing. Not a single solitary bit of computing, it just sits there doing nothing no matter what. Dead. A corpse.
It's either bricked or not. Just because the kernel/rom is broken and it doesn't boot properly does not mean it's bricked at all. If the bootloaders are intact and it tries to boot but fails at the kernel/rom level that is easily fixed. Throwing the term brick around in that situation, even when you add the retarded "soft brick" modifier, will just scare the **** out of a noob who just needs to remain calm and take the proper steps to have a working phone.
Click to expand...
Click to collapse
I hear ya and totally agree. But you do realize not that long ago, A LOT of people referred to the phone-!-computer screen as being "bricked". We know now that we are pretty far off from having an actual "bricked" phone in a lot of situations. But even the devs used to refer to that as a bricked device. Just gonna take some time for everyone to figure it out.
For me I went on YouTube and found joshs' video on how to flash continuum. It was very helpful and gave me the main idea of how the process is
Sent from my GT-I9000 using XDA App
Coreym said:
I hear ya and totally agree. But you do realize not that long ago, A LOT of people referred to the phone-!-computer screen as being "bricked". We know now that we are pretty far off from having an actual "bricked" phone in a lot of situations. But even the devs used to refer to that as a bricked device. Just gonna take some time for everyone to figure it out.
Click to expand...
Click to collapse
Which is why I'm trying to nip that in the bud from now on, or actually about a month ago when I coined the phrase, "soft bricked" is now called "clayed" because there is no such thing as a soft brick in the real world or the phone world, if a brick is soft it hasn't been baked yet in the kiln so it's still just clay, but it works in phone terms too if you have a brick you can't mold it or change anything about it, it's a brick. With clay it's still moldable and able to be worked with.
And the phone....!....pc seen just means a flash was incomplete. flashing anything successfully, even a modem, will get rid of that screen.
Granted if the kernel/rom is still incomplete it won't boot completely and be working, it'll just be "clayed" in a bootloop. So a complete odin rom is probably needed to have a working phone, but like I said flashing anything successfully will at least get rid of that screen.
dreezy1209 said:
For me I went on YouTube and found joshs' video on how to flash continuum. It was very helpful and gave me the main idea of how the process is
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
You got that URL for the YouTube video?
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
McKillroy11 said:
You got that URL for the YouTube video?
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
http://www.youtube.com/watch?v=UOyx5JQ_8_I
in the video he uses talon kernel, i wouldnt suggest that because now most roms are not based on jvb which that talon is, so if yoou fallow the steps with that kernel and flash a jvh based rom it will bootloop, i suggest a kernel in this thread:http://forum.xda-developers.com/showthread.php?t=1042543
if its a jvh rom grab this one:I9000_reoriented_vG.1.2_novoo.tar
studacris said:
Which is why I'm trying to nip that in the bud from now on, or actually about a month ago when I coined the phrase, "soft bricked" is now called "clayed" because there is no such thing as a soft brick in the real world or the phone world, if a brick is soft it hasn't been baked yet in the kiln so it's still just clay, but it works in phone terms too if you have a brick you can't mold it or change anything about it, it's a brick. With clay it's still moldable and able to be worked with.
And the phone....!....pc seen just means a flash was incomplete. flashing anything successfully, even a modem, will get rid of that screen.
Granted if the kernel/rom is still incomplete it won't boot completely and be working, it'll just be "clayed" in a bootloop. So a complete odin rom is probably needed to have a working phone, but like I said flashing anything successfully will at least get rid of that screen.
Click to expand...
Click to collapse
"clayed"... I like it.. It makes a lot more sense than "soft-bricked" I myself will start to use that phrase thanks!
studacris said:
See it's this kind of stuff I'm talking about. This loose use of the term brick.
If you can recover it by any means other than jtag it's not a brick. There are no different degrees of bricking, if it's bricked it doesn't do a damn thing. Not a single solitary bit of computing, it just sits there doing nothing no matter what. Dead. A corpse.
It's either bricked or not. Just because the kernel/rom is broken and it doesn't boot properly does not mean it's bricked at all. If the bootloaders are intact and it tries to boot but fails at the kernel/rom level that is easily fixed. Throwing the term brick around in that situation, even when you add the retarded "soft brick" modifier, will just scare the **** out of a noob who just needs to remain calm and take the proper steps to have a working phone.
Click to expand...
Click to collapse
I agree, but it's a term that everybody uses. Sort of like how a ton of metal music is called "hardcore", even when it's not hardcore. Etc. I guess I just assumed that when I gave different conditions for each degree of "brick"(or clay, whatever the terminology), a noob or otherwise inexperienced person could distinguish the difference rather than see "brick" and freak out.
I dunno, I've "bricked" my phone to the point of requiring a jig before, it's super easy and nothing to get freaked out about. If anything, it's a wonderful learning experience, which is something people should be expecting when they do this sort of stuff anyways. It isn't an iPhone.
I watched the video and I don't know how to downgrade to 2.1. Also will I need to re-root my phone after going to gingerbread or the downgrade?
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Superalpaca said:
I agree, but it's a term that everybody uses. Sort of like how a ton of metal music is called "hardcore", even when it's not hardcore. Etc. I guess I just assumed that when I gave different conditions for each degree of "brick"(or clay, whatever the terminology), a noob or otherwise inexperienced person could distinguish the difference rather than see "brick" and freak out.
I dunno, I've "bricked" my phone to the point of requiring a jig before, it's super easy and nothing to get freaked out about. If anything, it's a wonderful learning experience, which is something people should be expecting when they do this sort of stuff anyways. It isn't an iPhone.
Click to expand...
Click to collapse
ive done it on purpose out of curiosity and wanting to see for myself, like i mentioned earlier the phone...!....pc just means a flash was marked incomplete so a fun learning experience: Flash a kernel with odin and yank the chord halfway through the flash. you might get a screen with a pretty color followed by the phone....!.....pc screen. now flash a modem with odin and let that finish like normal, the phone...!...pc screen will no longer be there, it will still be clayed because the kernel is broken, but it wont have that screen anymore. then flash the kernel like normal and it will be fixed likje nothing ever happened. this has no risk of bricking whatsoever because there are no bootloaders involved in the flash.
ive never had to use the jig i built my button combos have always worked, i still built one cause its super easy and handy to have if i ever need it but i just never have
McKillroy11 said:
I watched the video and I don't know how to downgrade to 2.1. Also will I need to re-root my phone after going to gingerbread or the downgrade?
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
if you are flashing a custom rom and not staying on stock gingerbread then it will already be rooted.
to return to stock everything (stock bootloaders also) use odin one click. http://forum.xda-developers.com/showthread.php?t=731989
to return to a stock rom but still retain the gingerbread bootloaders use this package http://forum.xda-developers.com/showthread.php?t=995143
both of those methods of returning to stock would be an out of the box unrooted stock rom.
McKillroy11 said:
I watched the video and I don't know how to downgrade to 2.1. Also will I need to re-root my phone after going to gingerbread or the downgrade?
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
Use odin3 oneclick downloader. That will put you back at stock 2.1
Here it is. But if you don't know how to use it. You should really learn it.
http://www.megaupload.com/?d=SBSMALFJ
here's a vid for Odin:
http://www.youtube.com/watch?v=UDtxnH4lFuk
Sent from my SGH-I897 using XDA Premium App
studacris said:
Which is why I'm trying to nip that in the bud from now on, or actually about a month ago when I coined the phrase, "soft bricked" is now called "clayed" because there is no such thing as a soft brick in the real world or the phone world
Click to expand...
Click to collapse
I agree the term "brick" is thrown around too liberally, but I was under the impression that a "soft brick" was a SOFTware problem, and a "hard brick" was a HARDware problem. I guess I was mistaken, since "hard bricks" can still be the result of software issues. (right?)
Sent from a phone inside a phone inside a KFC inside a McDonald's.
twvance said:
I agree the term "brick" is thrown around too liberally, but I was under the impression that a "soft brick" was a SOFTware problem, and a "hard brick" was a HARDware problem. I guess I was mistaken, since "hard bricks" can still be the result of software issues. (right?)
Sent from a phone inside a phone inside a KFC inside a McDonald's.
Click to expand...
Click to collapse
A hard brick occurs when the bootloaders are written improperly or gingerbread and froyo bootloaders are mixed. Completely software. If the bootloaders can't load the boot sequence you get absolutly nothing from it.
You can still recover from a hard brick with jtag, if it was a hardware problem like severe water damage there is no coming back from that at all. So I guess that's just called a broken phone.
So I rooted my Samsung Infuse and installed Clockwork recovery using the appropriate method for flashing the - v3 or ve or what it might be called - recovery. So then using Clockwork I backed up my current ROM (Stock). It acted funny later after so I decided to just go back and restore from a previous ROM. It said there were problems mounting a few things. Don't remember what those were. However, here is the real kicker; I may have used update.zip from the previous phone (Which seemed to be a T-Mobile My touch 3G with a 32A something and a 32B something else, similar to the Fender) I had since all I did was switch out the external SD cards since they were both the same size and I had all of my music on the My Touch.
So, if it did flash the Update.zip, is my phone, for the most part, completely bricked? It's symptoms include:
- Static pictures
- Will not boot into recovery
- Will display 'Samsung' but then cuts to static afterwards.
- Shows Battery meter when plugged in and my computer still recognizes and installs the device drivers.
- It will boot into Download mode. Dunno if that actually will help at this point.
If it still turns on you're golden. Just look for the ultimate unbrick thread in the development section and follow the op instructions to go back to stock. The unbrick also is pre rooted and had the right recovery installed, so you're good to flash stuff after
Sent from my SAMSUNG-SGH-I997R using XDA Premium App
Cool, so somehow this fixed a phone which had a Fender radio flash. Since that's the case, what should I be worried about in the future that might permanently brick my phone?
Mr.Brosnan said:
Cool, so somehow this fixed a phone which had a Fender radio flash. Since that's the case, what should I be worried about in the future that might permanently brick my phone?
Click to expand...
Click to collapse
Trashing your partitions and bootloaders. Tho I'm not an expert on Samsung devices those seem to be the main causes of true bricks.
Sent from my HTC Thunderbolt
So if I change the partitions to like an ext3 filesystem is that considered trashing it? Yes, I'm fairly new to this entire in depth Android experience. I only took the Android over the iPhone because I am experienced with Linux and only touched a MAC (Referring to the Apple Operating System and not MAC cosmetics) three times.
Well, now I can't download anything in the market due to an 'Unknown error'. I mean, I can receive emails, I think I can call and text. I just can't use my smart phone to do dumb things now. This is a very disturbing complication and I will set off to find the cure for this ailment by posting here again.
Mr.Brosnan said:
Well, now I can't download anything in the market due to an 'Unknown error'. I mean, I can receive emails, I think I can call and text. I just can't use my smart phone to do dumb things now. This is a very disturbing complication and I will set off to find the cure for this ailment by posting here again.
Click to expand...
Click to collapse
you could try a factory reset or
you could just start over
http://forum.xda-developers.com/showthread.php?t=1116251
and or
http://forum.xda-developers.com/showthread.php?t=1092021
JBO1018 said:
Trashing your partitions and bootloaders. Tho I'm not an expert on Samsung devices those seem to be the main causes of true bricks.
Sent from my HTC Thunderbolt
Click to expand...
Click to collapse
Mainly bootloaders, and ours have enough protection that it's difficult to trash them.
It's next to impossible to hardbrick our phone. Worst case you put it in a state where you need to Odin/Heimdall something to fix it.
Entropy512 said:
Mainly bootloaders, and ours have enough protection that it's difficult to trash them.
It's next to impossible to hardbrick our phone. Worst case you put it in a state where you need to Odin/Heimdall something to fix it.
Click to expand...
Click to collapse
Good stuff to know considering my next phone is a toss up at this point between the Prime and Vigor.
Sent from my HTC Thunderbolt
Hi ! Well technically im not new to the forum b/c i have a nexus one and use that ... part of the forum a lot but im tryin to help a friend right now.. He has a thunderbolt, and got it pretty close to initial release. He's had many problems with it like periodic need of restarts, and losing like a decent portion of is battery AFTER restart (example before start, 50%, after restart, 40-45%...), text msging problems like (example... "Hi" to John Doe, *send*... it does not appear in the window, go back to the messaging home screen... u see "Hi" sent to Harry Potter instead.. doesnt happen a lot but business wise, once or twice can cause the lost of business... =/ luckily clients have forgave him so far...
and of cos theres like other problems thats hes been experiencing but those are two that came to mind just now..
so wondering, what procedures to help him root/flash a new rom so he can get a better and faster use of his phone (OH another thing, its working quite slow... D i was lookin around the thunderbolt forum, theres roms like synergyrom and of cos cm7 that are really popular.. then reading in some areas, using the revolutionary method is a good way to start to..root? is the revolutionary method the way to get the bootloader or what.. lol yah im noob >_> surprising i got cm7 on my n1 lol
Many people would ***** at ya for not reading the stickies... naughty naughty. In any case yes you want revolutionary. And yes it provides s-off and an unlocked bootloader. Alternatively for the random SMS problem you can just download an alternate messaging app. I use chomp. If I helped ya hit the thanks!
My name is Revos I'm a recovering flashaholic running Liquid Gingerbread 3.0
All your questions answered Here
i actually did read it.. just didnt really understand it cuz it was different then how it was done for my nexus one...
If there are parts that you do not completely understand go ahead and ask specific questions. Nobody will be upset if you are trying to make sure you know what your doing. Which parts did you not understand?
so what i understand so far... you need to obtain S-Off and unlocked boot loader..
theres a few ways in obtaining that? mr1/ota permroot or revolutionary.. there are people saying revolutionary (or the quick n easy way) has a higher chance in bricking phone.. is that true? b/c i wanna use the way that has the lowest or one of the lower chance to brick the phone.. Yah i want it done fast but i want it done the safest way too.. was reading the instructions and it says it uses the clockwork recovery.. iirc.. there was between clockwork and amun-ra ??
for the most part it looks kind of similar to the process i did with my nexus one..
after it being rooted and having the bootloader... do i just look for those custom firmware packages like uhm cm7 or synergy (or what do you people recommend that you like??) and flash it from sd card in bootloader??
Of all the reading I did about revolutionary I didnt notice anyone bricking their phone. I'm not saying it didn't happen, but it seemed to run smooth for most everyone that followed the directions.
You will install CCW while your running the revolutionary.
And to answer your last question, yes you will just download whatever rom you choose to the root of your sdcard, flash it from recovery.
*sigh* friend hesistant to get it done because he has insurance on the phone... guess ill wait until he's willing ahaha thx for the help !
All the more reason to root. Worst case he bricks it. If he doesn't brick it he will learn how much more fun and enjoyable the Tbolt is with the ability to flash new roms, or change whatever he wants.
Insurance covers phones "accidentally" dropped into the toilet...
yah hes worried if it gets bricked.. hes all for the fixing ...
The only way you are going to brick your phone is if you don't follow the directions. Just make sure you do a nandroid backup through the bootloader and go from there. If your friend is to afraid to do it I'm sure you can check Craigslist for people to root it for you. I'd do it for you but I don't know if the forum allows it.
Sent from my ADR6400L using Tapatalk
Tell him to grow some and root. Hes gonna have to eventually do it anyways to avoid issues like hes been having. Of he does an insurance claim they're just gonna send him a refurbished one and who's to say all the issues were solved with that one after it was sent back? I don't get how people can complain, ask for help and then be reluctant. Whatever you do make sure you sit him down and walk him through it otherwise if he has any issues he'll be calling and blaming you. Been there and laughed and laughed. Good luck.
Sent from my HTC ThunderBolt using XDA App
I'm ashamed to admit it, but I'm in the same boat almost. I still haven't rooted and rom'd yet for similar reasons. That said, I'm pretty close, especially with the logging fiasco. From what I've read, there haven't been any legit reports of bricking due to Revolutionary, at least used correctly. Most people say it's only when you try an old method of rooting or otherwise don't follow directions.
ponyboy82 said:
I'm ashamed to admit it, but I'm in the same boat almost. I still haven't rooted and rom'd yet for similar reasons. That said, I'm pretty close, especially with the logging fiasco. From what I've read, there haven't been any legit reports of bricking due to Revolutionary, at least used correctly. Most people say it's only when you try an old method of rooting or otherwise don't follow directions.
Click to expand...
Click to collapse
Trust me... It's a LOT less scary after you do it than before. I've helped walk some people through the old ADB method with success and Revolutionary is idiot proof by comparison.
Okay, before I get started, I am no noob when it comes to adb, linux, qpst, and htc phones. That being said, I was recently making and flashing several splash screens for my AT&T one x. unfortunately, I made a typo whle "dd" pushing the last one to my phone. In the typo I sent the splash screen to blk0p4 instead of 0p14, so when I typed in "adb reboot" my phone shut down, and never came back up. It now shows as QHSUSB_DLOAD in windows. I've spent countless hours searching xda, android central, and various other sites for a possible fix. I've tried the unbricking project, Jet method, and everything else I can find. The device shows up in linux, but my partitions do not show. So basically what I'm looking for is anyone with any fresh ideas on how to get it back to life. My warranty is void, as my phone is disassembled right now, so the battery didn't die while stuck in this mode. I'm really hoping I can escape this without sending my phone into jtag service. Anyone with any ideas to help? If I'm not around on XDA, you can usually always get me on gtalk @ [email protected]. Hopefully someone with more knowledge than I, can help me get my phone back in working order.
It sounds like you're on hboot 1.14? p4 is the extended partition table, but I assume you know that. You're in the same boat as people who flashed Tegra 3 roms.
AFAIK, there is no fix for that sort of brick short of jtag. A lot of smart people have been working on it without success.
iElvis said:
It sounds like you're on hboot 1.14? p4 is the extended partition table, but I assume you know that. You're in the same boat as people who flashed Tegra 3 roms.
AFAIK, there is no fix for that sort of brick short of jtag. A lot of smart people have been working on it without success.
Click to expand...
Click to collapse
yes, the phone came to me with hboot 1.14. And the only thing I knew about 0p4, was that I had to hex edit it to htcdev unlock, before s-off. Everything keeps pointing to jtag being the only option to fix my phone.
Correct. Jtag is the only way you would be able to revive your device.
Sent from my HTC One X using xda premium
Myrder said:
Correct. Jtag is the only way you would be able to revive your device.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
kind of figured that. I've searched everywhere trying to find another fix. Looks like I'll be paying $65 to send my phone in for jtag...
Mods can delete this thread if you wish.
Call me paranoid, but after reading the thread on Unbricking that got bumped a couple days ago, I'm a little afraid I might one day brick my device. Even though I take all the precautions, it looks like bad luck has set upon a handful of guys, and I feel like it might happen to us all one day. I'd feel at ease, after reading that thread, however I don't have a PC and I have virtually no way of getting my hands on one!! Is there no way to do this on a Mac? Is any dev working on this or able to point me to instructions in case this happens to me? I just want to be ready..
Kinda surprised I couldn't find any threads on this.
The only way you can brick this phone is if you stupidly flash a ROM not meant for this phone. Please know the difference between soft brick and hard brick. Also there isn't any proven method to un-brick a soft bricked S 3 for the MAC. The last time I checked the MAC is a PC made by Apple running its own OS just like an iPhone is a smartphone, an iPad is a tablet and an iPod is an MP3 player but that is an whole other story.
Best response you'll get is to try using Heimdall, if it's working for our phone, if you absolutely must use Mac. Not many people have been trying that from what I see and I doubt there will be any change either. Besides that, find someone with a Windows PC and fix any issue you have.
And I completely agree with jmxc23.
Sent from my SCH-I535 using xda app-developers app
npro1464 said:
Call me paranoid, but after reading the thread on Unbricking that got bumped a couple days ago, I'm a little afraid I might one day brick my device. Even though I take all the precautions, it looks like bad luck has set upon a handful of guys, and I feel like it might happen to us all one day. I'd feel at ease, after reading that thread, however I don't have a PC and I have virtually no way of getting my hands on one!! Is there no way to do this on a Mac? Is any dev working on this or able to point me to instructions in case this happens to me? I just want to be ready..
Kinda surprised I couldn't find any threads on this.
Click to expand...
Click to collapse
You could use a virtual machine that runs windows. But yes, your options are very limited when trying to work with this phone on a mac.
You need a JTAG to unbrick!
mandiw777 said:
You need a JTAG to unbrick!
Click to expand...
Click to collapse
That is for hard bricking. The OP is talking about soft bricking the device there IS a difference between the two.
jmxc23 said:
The only way you can brick this phone is if you stupidly flash a ROM not meant for this phone. Please know the difference between soft brick and hard brick. Also there isn't any proven method to un-brick a soft bricked S 3 for the MAC. The last time I checked the MAC is a PC made by Apple running its own OS just like an iPhone is a smartphone, an iPad is a tablet and an iPod is an MP3 player but that is an whole other story.
Click to expand...
Click to collapse
So as long as I don't flash a non VZ rom I should be good and shouldn't get a soft brick? I don't mind having to boot into recovery to fix something, but having to find a PC might cost me a day or two without a phone, and a big fight with my wife. It might be worth my money to invest in Parallels..
Sent from my SCH-I535 using Tapatalk 2
npro1464 said:
So as long as I don't flash a non VZ rom I should be good and shouldn't get a soft brick? I don't mind having to boot into recovery to fix something, but having to find a PC might cost me a day or two without a phone, and a big fight with my wife. It might be worth my money to invest in Parallels..
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
If you're a consistent flasher, at some point you will need to use Odin. Maybe not enough times to justify spending money to solve your problem, but you're going to have to borrow someone's PC or use windows eventually unless someone comes up with some Mac development
That sucks. If I reset the flash counter does that help prevent this at all?
Sent from my SCH-I535 using Tapatalk 2
npro1464 said:
That sucks. If I reset the flash counter does that help prevent this at all?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Resetting the flash counter is utterly pointless until you need to exchange the phone via warranty. So, no it does not.
Sent from my SCH-I535 using xda app-developers app
So there is no way to fix a soft brick with heimdall? Ive been looking everywhere for a guide or any help. Im stuck at a softbrick and have no access to a windows computer. Any advice?
j.minds said:
So there is no way to fix a soft brick with heimdall? Ive been looking everywhere for a guide or any help. Im stuck at a softbrick and have no access to a windows computer. Any advice?
Click to expand...
Click to collapse
Download a Windows 8 or 7 trial and install bootcamp.
Surge1223