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.
I was running Inspired Ace. All was good, and I decided to flash LeeDroid.
I used the EXT4 conversion/wipe, then installed LeeDroid.
I had tons of problem with LeeDroid, such as messaging being very slow, FCs when trying to make/receive a phone call, etc. It wasn't my cup of tea... so I decided to go back to Inspired Ace.
Restored the backup, and things aren't working like it used to:
*Flash videos embedded on websites sometimes crash the browser
*Netflix doesn't work at all, regardless of which fix I try (rmk's or fenny's)
*Youtube lags/stutters like mad
So, I did a fresh install:
*Wiping data, system, cache
*Installing fresh Inspired Ace
First boot, LeeDroid default background was showing in the Inspired Ace. There were 2 of every system apps (2 calculators, 2 call histories, etc).
Wiped data/system/cache again, and installed fresh Inspired Ace again (downloaded a new copy, incase the last copy was corrupted).
Same deal... 2 of every system app, and LeeDroid default background.
I decided "whatever" at this point, and installed all my apps, and this time, like previously, nothing that involves videos work (flash embed, netflix fix, youtube).
What's going on?
TL;DR- I installed LeeDroid, didn't like it, did a fresh install of Inspired Ace, components of LeeDroid was still left behind despite formatting system/data/cache, and apps, such as browser, netflix, youtube, doesn't work.
1. Copy ur backup to computer, reformat ur SD, restore the backup to SD.
2. Go to recovery, and clear data, cache and dalvik cache.
3. Try restoring ur back up now. It should work, and not have traces of anything. Apps like dolphin browser store data on sdcard.
Just get a warranty replacement.
knarfl1 said:
Just get a warranty replacement.
Click to expand...
Click to collapse
What? Seriously?
That'll help persuade HTC to ease up on their locked bootloader policy. Lots.
Inspired Ace 1.0.1¦ XDA Premium
diablo009 said:
1. Copy ur backup to computer, reformat ur SD, restore the backup to SD.
2. Go to recovery, and clear data, cache and dalvik cache.
3. Try restoring ur back up now. It should work, and not have traces of anything. Apps like dolphin browser store data on sdcard.
Click to expand...
Click to collapse
Forgot to mention but yes, I have tried formatting my SD card, as well try a brand new one that hasn't been used with this phone before.
Just throwing this out, but would running the RUU possibly get you back to a blank slate from which to start over?
I've never run it myself, but my assumption of what it ends up doing is pretty much returning the phone to its out-of-the-box state, ignoring what's on the phone at the time (aside from S-On/s-off.
I would also assume you'd have to re-root.
Just a thought.
Inspired Ace 1.0.1¦ XDA Premium
Also, running the RUU (the new one found at http://forum.xda-developers.com/showthread.php?t=1058042 ) from HBOOT as Scott_S mentioned would also update your radio if you have not already done so. However, as I found out, you will either have to install a file explorer to delete the PD98IMG.zip from the sd card, or install ROM Manager to boot to CWM in order to flash back to Inspired Ace, or whatever ROM you decide on. I did the same thing two days ago. If you boot to HBOOT with the update file on your ZIP all i could do was install or reboot (as it scans for update then only prompts install and if you say no, it prompts reboot) and the RUU does not include Rom Manger. You probably already knew that but just throwing it out there.
EDIT:Forgot to mention, this RUU is already rooted. No re-rooting necessary other than that, same as original stock un-rooted RUU
Scott_S said:
What? Seriously?
That'll help persuade HTC to ease up on their locked bootloader policy. Lots.
Inspired Ace 1.0.1¦ XDA Premium
Click to expand...
Click to collapse
No worries. The phone will be refurbed and sold for profit again (or fixed and given back as a warranty replacement).
Fyi it is not HTC that wants to lock/encrypt the BLs: It's ATT.
You gonna tell everyone to stop tethering for free?
Scott_S said:
Just throwing this out, but would running the RUU possibly get you back to a blank slate from which to start over?
Click to expand...
Click to collapse
Yea, why not. I'll first try the "cracked" RUU, and if that doesn't work, do a full unroot, and reroot it.
And if THAT doesn't work... I don't know.
willwalk93 said:
Also, running the RUU (the new one found at http://forum.xda-developers.com/showthread.php?t=1058042 ) from HBOOT as Scott_S mentioned would also update your radio if you have not already done so.
Click to expand...
Click to collapse
Yea, already have 06.06.30.
knarfl1 said:
No worries. The phone will be refurbed and sold for profit again (or fixed and given back as a warranty replacement).
Fyi it is not HTC that wants to lock/encrypt the BLs: It's ATT.
You gonna tell everyone to stop tethering for free?
Click to expand...
Click to collapse
I guarantee even carrier unlocked versions will (and already DO)have signed bootloaders, and I doubt its all att. When people brick their phones, send them in for warranty replacement, its still costing HTC money no matter how you look at it. At the very least, manhours. It might not take long to fix, but it adds up. If they figure the cost for letting us do what we want to do with bootloaders/kernels/roms is more than what they lose by pissing us (very small percentage of total users) modders off, then they have a motive ($) to keep us out.
When you hack a phone, YOU(not you specifically, end user), take a risk knowing you may mess up and brick your phone, if you return it as a brick, the HTC devs are not dumb. I'm sure they know exactly how it happened when they get it.
I still have a bricked atrix that I paid almost full price for from trying to crack the POS. Didn't really feel I had the right to return it, when I f'd up trying to find a way around the bootloader.
And people who use theirs phones as their entire internet service tethering for free don't help either
di11igaf said:
I guarantee even carrier unlocked versions will (and already DO)have signed bootloaders, and I doubt its all att. When people brick their phones, send them in for warranty replacement, its still costing HTC money no matter how you look at it. At the very least, manhours. It might not take long to fix, but it adds up. If they figure the cost for letting us do what we want to do with bootloaders/kernels/roms is more than what they lose by pissing us (very small percentage of total users) modders off, then they have a motive ($) to keep us out.
When you hack a phone, YOU(not you specifically, end user), take a risk knowing you may mess up and brick your phone, if you return it as a brick, the HTC devs are not dumb. I'm sure they know exactly how it happened when they get it.
I still have a bricked atrix that I paid almost full price for from trying to crack the POS. Didn't really feel I had the right to return it, when I f'd up trying to find a way around the bootloader.
And people who use theirs phones as their entire internet service tethering for free don't help either
Click to expand...
Click to collapse
Exactly.
It's the attitude expressed by the post you and I responded to that doesn't help our situation. It doesn't matter whether it's ATT or HTC that's driving the bootloader thing, the end result, and most likely the motivation behind it, is the same.
Inspired Ace 1.0.1¦ XDA Premium
Printerscape said:
Yea, why not. I'll first try the "cracked" RUU, and if that doesn't work, do a full unroot, and reroot it.
And if THAT doesn't work... I don't know.
Click to expand...
Click to collapse
Doesn't work, after flashing MDJ's ViVO.
*sigh*
di11igaf said:
I guarantee even carrier unlocked versions will (and already DO)have signed bootloaders, and I doubt its all att. When people brick their phones, send them in for warranty replacement, its still costing HTC money no matter how you look at it. At the very least, manhours. It might not take long to fix, but it adds up. If they figure the cost for letting us do what we want to do with bootloaders/kernels/roms is more than what they lose by pissing us (very small percentage of total users) modders off, then they have a motive ($) to keep us out.
When you hack a phone, YOU(not you specifically, end user), take a risk knowing you may mess up and brick your phone, if you return it as a brick, the HTC devs are not dumb. I'm sure they know exactly how it happened when they get it.
I still have a bricked atrix that I paid almost full price for from trying to crack the POS. Didn't really feel I had the right to return it, when I f'd up trying to find a way around the bootloader.
And people who use theirs phones as their entire internet service tethering for free don't help either
Click to expand...
Click to collapse
Product returns are part of doing business. With over 100 million accounts, there will be millions of phones returned every year for whatever reason. Some people got the Inspire just to tide them over for 30 days until the Atrix was available (or got the Atrix and found out it is a turd and returned it for an Inspire.)
As for the enthuasist segment, though small in terms of percentage, size of the community has passed the critical mass long time ago. BTW, HTC is NOT locking their bootloaders. [updated]
Howbeit should we try to appease AT&T to stay in their good graces? Then modders should:
- Stop using free tethering.
- Get off the unlimited data plan gained via iP2 scheme and go back to 250MB/2Gb plans.
- Removing tweaks that improve data speed.
- Removing hacked Netflix app.
- Un-root.
- Only use phones sold by AT&T on AT&T network.
- etc...
I'm sorry your Atrix is bricked. Sell its parts on eBay?
You did not mention wiping the dalvik cache. That is a must.
Scott_S said:
Exactly.
It's the attitude expressed by the post you and I responded to that doesn't help our situation. It doesn't matter whether it's ATT or HTC that's driving the bootloader thing, the end result, and most likely the motivation behind it, is the same.
Inspired Ace 1.0.1¦ XDA Premium
Click to expand...
Click to collapse
Haha. I spoke one minute too soon. Read the news from HTC about locking bootloaders. Your concern is unwarranted.
Printerscape said:
Doesn't work, after flashing MDJ's ViVO.
*sigh*
Click to expand...
Click to collapse
That's not a completely pure RUU, though. Stock recovery and hboot has been removed from that.
Try the pure RUU.
Inspired Ace 1.0.1¦ XDA Premium
When you do the EXT4 wipe can it still read the files on your sd card? I did my flashing with another SD than the one I use normally so there was not chance of messing my card up. Do I need to reformat the every day sd card?
Thanks,
Thorsgal
knarfl1 said:
Haha. I spoke one minute too soon. Read the news from HTC about locking bootloaders. Your concern is unwarranted.
Click to expand...
Click to collapse
You're absolutely correct... Now.
I wasn't aware at the time of those earlier posts of the latest development, that HTC had gone ahead and scrapped the locked bootloader thing.
Still, I think the least we can do in return for HTC doing right by us, is to mod these phones with a clear head, not carlessly, educating ourselves prior to undertaking some of these processes, and exhaust all resources available to us in trying to solve any problems that result, that are of our own making.
If that fails, then the noble thing to do is ask them how much it would cost to "repair" our ****-ups, not pass the burden back on them under the guise of a "warranty replacement" for supposedly "defective phone."
It's lying, and it just feels morally wrong.
Inspired Ace 1.0.1¦ XDA Premium
Scott_S said:
You're absolutely correct... Now.
I wasn't aware at the time of those earlier posts of the latest development, that HTC had gone ahead and scrapped the locked bootloader thing.
Still, I think the least we can do in return for HTC doing right by us, is to mod these phones with a clear head, not carlessly, educating ourselves prior to undertaking some of these processes, and exhaust all resources available to us in trying to solve any problems that result, that are of our own making.
If that fails, then the noble thing to do is ask them how much it would cost to "repair" our ****-ups, not pass the burden back on them under the guise of a "warranty replacement" for supposedly "defective phone."
It's lying, and it just feels morally wrong.
Inspired Ace 1.0.1¦ XDA Premium
Click to expand...
Click to collapse
Exactly. I wish more people were honorable and if they bricked their phones, write it off as tuition in the school of hard knocks and move on. Or, since it is pretty difficult to hard-brick a HTC device, take the time to reflash it stock, then see about a return.
Just a few people not knowing what they are doing and either returning their devices, or trying up HTC's support can mean HTC will re-lock bootloaders just so they don't have to deal with that element, as the returns hit them in the pocketbook big time.
mlts22 said:
...
Just a few people not knowing what they are doing and either returning their devices, or trying up HTC's support can mean HTC will re-lock bootloaders just so they don't have to deal with that element, as the returns hit them in the pocketbook big time.
Click to expand...
Click to collapse
Some people just waltz into doing these things thinking everything is a "one-click" process, for some phones maybe, but these newer ones it's not quite that simple.
And I think a lot of people who end up doing as you illustrated, warranty returning/tying up their tech support, don't even realize they're dealing with a "*soft*-brick," not a perma-brick -- something that, if they could get out of panic mode long enough, they would realize the fixes are at their fingertips, via XDA.
Apologies to the OP, didn't want to derail the thread, just kinda happened that way...
Inspired Ace 1.0.1¦ XDA Premium
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
Please keep in mind I have never rooted a phone and have no idea how to.
Ok so I Don't know if I should root my Sensation, or just leave it as is. I know there are risks to rooting, but I hear rooting makes phone's more customizable?
So.. Please post:
-The Advantages of rooting
-The DisAdvantages
-The Risks
-For a noob like me, on a scale of 1-10 how hard will it be? 10 = Hardest
-Should I root, and why.
Thank you!
Go to google.com and type in "what is rooting android" now spend the next 30minutes-1hour reading and learning.
Sent from my Sensation using xda premium
From a scale from 1-10, I think it'd be like a 2. Its fairly simple if you read the instructions carefully.
Sent from my HTC Sensation Z710e
You should definitely root! It gives you complete control over your phone and customize it whatever way you want!
On a scale from 1-10, i think it'll be 2 too. Its really easy if you follow the instructions clearly.If you don't, there might be a chance of bricking your phone if you messed up somewhere badly. The chances are really slim though!
Sent from my fingers to appear on your screen magically.
Root gives u absolute control over your phone. Like admin rights on a windows computer. No disadvantages. Lots of advantages (read: a lot of cool programs out there that require root privileges)
The risk is not following instructions and turning your phone into an expensive paperweight. For a noob like you, if you can follow instructions, difficulty level is a 1. Likelihood of you bricking your phone is negatively correlated with your SAT score.
Sent from my HTC Sensation
Real question is:
Does the phone do what you want it to do as it is now?
If the answer is 'yes' then rooting isn't really neccessary. The ONLY reason I've rooted is to remove all the system apps I don't use. I use my own ROM which is basic and does what I want it to do
EddyOS said:
Real question is:
Does the phone do what you want it to do as it is now?
If the answer is 'yes' then rooting isn't really neccessary. The ONLY reason I've rooted is to remove all the system apps I don't use. I use my own ROM which is basic and does what I want it to do
Click to expand...
Click to collapse
Prety much this ... for a noob rooting is totally useless .. many people do it to strip the phone off useless aps to make it faster ... which fact lost its point for me with new OTA release with which Sense became fast enought to prevent example me from bothering with rooting. At this moment theres no reason good enough for me to do it.
Another group of people are those who root just to be pimp and IN even if its totally worthless for them.
Different group of people are those who use root/s-off for changing/modifying/creating custom ROMs with either some sort of tweaked HTC Sense with transparency, various MODs and that kind of stuff, or totally different graphic layout (which reason i never fully understood since i bought Sensation for its Sense .. hence the HTC brand .. innit?)
So yea ask urself ... does the phone have all i need? if the answer is yes, then theres no need for rooting for you.
Thats my subjective point of view.
If you root you can customize your phone the way you like it, or atleast the ways developers make available to you. i just rooted my phone for the first time and it was way easier than i thought it was. before you flash a new rom, make sure you backup your device with titanium backup. then after its flashed, you can easily restore all your apps and data with titanium backup. the only data you really lose is your home screen apps because you have to put all your apps and widgets back on your own.
EddyOS said:
Real question is:
Does the phone do what you want it to do as it is now?
If the answer is 'yes' then rooting isn't really neccessary. The ONLY reason I've rooted is to remove all the system apps I don't use. I use my own ROM which is basic and does what I want it to do
Click to expand...
Click to collapse
^^^This is THE perfect response to the question
I've not rooted and unless I need ICS and it won't come to the Sensation (to be honest, by the time you NEED ice cream sandwich the Sensation will likely be old tech) so I'll need a custom ROM, or there's some work related can't live without app that requires root, I can't see myself ever needing to do it.
I have rooted my 7 weeks old Sensation after only 3 weeks. Initially I thought I would never have to do so, but there were 2 things which made me unhappy: bloatware and the bitpool problem which causes crappy sound while listening to music over bluetooth headset. After all I flashed the device with as much as 7 separate roms and since today I'm happy with CM7 alpha 4. It's like a completely different device So I'd always say yes, but it depends on how your needs are.
You should root. Simply because there are many awesom apps in the market that required the root. With a rooted phone, you can do whatever you want.
The risk is your phone can be bricked. But i rooted many android phone but no brick to me, you should give it a try
What amazing apps are there for rooted devices? I'm thinking of rooting mine, mainly for the extra customisation options, but don't know if I can be bothered backing up all my apps and data. You have to back up sd card too don't you?
Sent from my brain
tibuchivn said:
You should root. Simply because there are many awesom apps in the market that required the root. With a rooted phone, you can do whatever you want.
The risk is your phone can be bricked. But i rooted many android phone but no brick to me, you should give it a try
Click to expand...
Click to collapse
Thx. Couldn't have said it better. No risk - no fun
---------- Post added at 10:01 PM ---------- Previous post was at 09:54 PM ----------
yourpassenger said:
What amazing apps are there for rooted devices? I'm thinking of rooting mine, mainly for the extra customisation options, but don't know if I can be bothered backing up all my apps and data. You have to back up sd card too don't you?
Sent from my brain
Click to expand...
Click to collapse
Titanium Backup
Root Explorer
AdFree
you can even install the HTC Beats Music mod, if you want to. I've tested that and it really sounds better. I even miss that on CM7, but I love CM7 for other reasons...
I'm sure, I forgot some apps, but it's late here
Regarding backup:
I usually have Titanium Backup for my apps & apps data (important and convenient, when moving to another rom) plus a general (clockworkmod) backup of the whole phone rom prior to flashing to be able to easily go back if something goes wrong...
im not stranger to rooting as i have done all kinds of crazy crap to my vibrant, i have the sensation and im not so sure if i want to root. Its cause i hear Htc devices are alot easier to brick, and i don't wanna risk messing with the bootloader. So far its running great, wifi tether, screenshots, i don't think you really need it.
well.
i thought im not happy with my phone so i rooted.
i installed the revolution room , it looked promising but im not happy.
my phone getting super hot while playing and some time rebooting it self and dont stop reboot until i remove the battery
as someone else said if u happy with your phone just leave it.
BshadoW1 said:
well.
i thought im not happy with my phone so i rooted.
i installed the revolution room , it looked promising but im not happy.
my phone getting super hot while playing and some time rebooting it self and dont stop reboot until i remove the battery
as someone else said if u happy with your phone just leave it.
Click to expand...
Click to collapse
And if you're not happy with your phone send it back for a replacement
Course now you'll have to get it back to it's original condition and un-root it to do that...
And how about spoonfeeding???
Dude... Please read, read and read some more.
What ya'll get with root.... almost all access to all the files....
Here comes the question? What ya gonna do with it?
Do you need that?.... Don't think so. Yer probably thinking of supping yer phone...
Installing different ROM.... Then... ROMs come rooted already.
What you might ask for is: Should I S-OFF my phone?
That's up to you. You lose yer warranty if S-OFF discovered, but you can do whatever you want with yer phone....
Hope I explained as simple as it comes...
Tester
---------- Post added at 05:14 PM ---------- Previous post was at 05:07 PM ----------
xaccers said:
And if you're not happy with your phone send it back for a replacement
Course now you'll have to get it back to it's original condition and un-root it to do that...
Click to expand...
Click to collapse
Dude....
Replacement not gonna do a crap... To be honest...
If he plays games and all other 9 yards.... His battery has to be glowing!!!
JMO.
Tester
Tester30 said:
Dude....
Replacement not gonna do a crap... To be honest...
If he plays games and all other 9 yards.... His battery has to be glowing!!!
JMO.
Tester
Click to expand...
Click to collapse
Mine doesn't. I've never had a reboot due to over heating, or gotten too hot to touch, and that's even with streaming music via bluetooth, downloading over 3G and using GPS. Likewise while playing graphics intensive games with online content it's got warm but not over heated.
Some handsets have suffered an over heating issue and rightly have been replaced under warranty.
You should root, really you don't know what your missing, Android Revolution is best ROM out there and root ting is vary safe.
OK I am also new to rooting.. Can anyone suggest me link on how to root my sensation.. Plus after rooting do I need to change Kernel and Radio? (Though I still don't understand both terms).
My only concern is the slow performance. The phone should run faster for a 1.2 Ghz processor...
I just want to know cuz I'm a coward and I don't want to flash my own roms
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
cpu999 said:
I just want to know cuz I'm a coward and I don't want to flash my own roms
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
You are my hero of the day
Seriously though, a couple things can cause bricks. Battery pull during radio flash. Flashing a kernel with the wrong mount points. Formatting internal memory is a good way. Not like normal in recovery when you wipe, but in the way when you make your updater-script and aren't paying close attention to what your doing, lol. Yes, I have done this, haha.
There is plenty more ways for sure, but just pay close attention to what your doing and watch other devs around you and learn what they are doing and you'll be fine.
And how do you recover? USB isn't an option anymore and you need a JTAG or similar?
lap777 said:
And how do you recover? USB isn't an option anymore and you need a JTAG or similar?
Click to expand...
Click to collapse
Well normally there isn't a way to recover, hence "hard bricked". But, if there is a way there will be a recovery method posted somewhere in your device forums to recover bricks. Its a hard thing to come back from though.
Here is a pretty good example of a hard brick that a fix was eventually found for quite awhile after the device was released, went through eol, and people started leaving for newer devices. All credits go to the legend, Doug Piston of course. HTC Droid Incredible and its 5 vibe hard brick: http://forum.xda-developers.com/showthread.php?t=1110865
I heard jcase (teamandirc) say the GS3 is pretty easy to recover though, so I'm not sure you'd have much issue if you did brick. I'm not familiar with Samsung, I use HTC devices, so I'm not sure what method you boys would use.
I know for HTC devices, bricks most commonly occur when we accidentally mount something wrong, format something incorrectly, or a lot here lately, libs. Libs can cause issues to. The good thing though is we have the protection of a secure bootloader, s-on, which means if something harmful is flashed it won't hurt the phone since the bootloader is unlocked through HTC but still s-on. I think Samsung is about the same in this area. But I don't know. I'm just bored and felt like typing a bunch of text, lol
Good man.
Sent from my ZTE N881E using xda premium