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.
Hey guys...As a few of you know, my phone met its demise last night for (seemingly) no reason. I had recently backed up my ROM through Rom Manager and tried out a few themes from the market.
Anyways, when I plugged my phone into my computer, I see that it tried to install some drivers and then I see "QHSUSB_DLOAD" as my phone.
Ive noticed that all TRULY bricked phones (not just the sensation) all have this "QHSUSB_DLOAD" in common. No one has yet to figure out what this is or how to fix this.
Tmobile chalked it up to hardware failure and has a new (likely refurbished ) on its way.
I think we need to figure out what the heck this is. A few mentioned a connection between Rom Manager, CWM, and QHSUSB_DLOAD. I, for one, will make dang sure that Rom Manager stays off my phone...Any other ideas?
Until this is worked out, its VERY likely that rooting COULD randomly cause the dreaded true brick, QHSUSB_DLOAD style.
Matt
Just swayed my decision on wether to root or not.
So does it turn on? You are a bit unclear about your situation. Does it charge, when you charge it. And does the PC recognize it when you connect it to the PC?
Actually this is well documented. You are in Qualcomm high speed USB download mode. It is typically caused by a problem with your processor and or it's software. Either it is crapping out or more likely something corrupted the software, either by flashing a custom kernel that isn't 100% stable with the hardware (since kernel source for this phone is incomplete this IS possible) or it's just bad luck. Voltage tweaks can have a long term detrimental effect on hardware.
Hey guys, it is dead as a door knob.
http://forum.xda-developers.com/showthread.php?t=1321110
That ought to sum things up...
Im sure its bricked...I just want to look more into this as I have yet to find a single case where this was solved. It just gets pushed aside since no one knows.
Behold_this said:
Actually this is well documented. You are in Qualcomm high speed USB download mode. It is typically caused by a problem with your processor and or it's software. Either it crapped out or more likely you corrupted the software, either by flashing a custom kernel that isn't 100% stable with the hardware since kernel source for this phone is incomplete this IS possible. Voltage tweaks can have a long term detrimental effect on hardware.
Click to expand...
Click to collapse
I was using cm7, build 9 and fauxs kernel build 8. I dont do UVing or OVing and have kept the CPU speed to 1.18Ghz.
My computer told me that it failed to install whatever it felt it needed.
So this is known? Am I correct in thinking that this is a 100% brick then, or is there anything, save from tearing it open, that can be done to fix it?
Although I have a new one coming, Id like to get to the bottom of this for everyone else.
Matt
Well, yes...and no. For all intensive purposes it is bricked, however, if it's just software HTC (or anyone with a leaked loader) could recover it easily. If it's hardware then nothing can be done. You can find the Qualcomm drivers online but still need the loader (all I've found are motorola sbf's nothing for HTC). Basically you did the only thing you can at this point, but now you have a little more info on it.
Behold_this said:
Well, yes...and no. For all intensive purposes it is bricked, however, if it's just software HTC (or anyone with a leaked loader) could recover it easily. If it's hardware then nothing can be done. You can find the Qualcomm drivers online but still need the loader (all I've found at motorola sbf's nothing for HTC). Basically you did the only thing you can at this point, but now you have a little more info on it.
Click to expand...
Click to collapse
Someone could get an XDA style Nobel prize for coming out with something that could fix this phone when this happens.
Im guessing that is what a JTAG does? Would be great once warranty time is over!
I am suspicious this could be another build quality issue with HTC...Day one with this phone had the same sort of thing happen, but it eventually booted. Perhaps this was just waiting to happen?
Or, I wonder if it is related to CWM and Rom Manager? This seems to be a RARE occurance considering how many people flash the above mentioned ROM and kernel without this happening. The last thing I did before charging was backing up in Rom Manager.
Jtag is a little extreme as it involves soldering and messing with internal components, plus don't think it's been done on this chip set, but I could be wrong. The ROM is usually less of a concern then custom kernels are. Also ROM manager sucks and many times is very buggy. It is safer to do all those kinds of things through recovery. Uninstall ROM manager and forget it ever existed (just my opinion).
Behold_this said:
Jtag is a little extreme as it involves soldering and messing with internal components, plus don't think it's been done on this chip set, but I could be wrong. The ROM is usually less of a concern then custom kernels are. Also ROM manager sucks and many times is very buggy. It is safer to do all those kinds of things through recovery. Uninstall ROM manager and forget it ever existed (just my opinion).
Click to expand...
Click to collapse
Okay, how about this...I intend to S-off and reinstall CWM the SECOND I get my new phone. LOL...Should I erase my ROMs+kernels from the SD card and start over from scratch, or can I just boot up again like nothing happened?
I guess its safer to start over, huh?
EDIT: I have been reading over stories involving a hard brick and QHSUSB_DLOAD. It seems it ALL came from SD card partitioning in CWM. I was also in recovery that day restoring my ROM when I accidentally touched the screen and the phone rebooted. (After restoring) I thought it was just rebooting recovery. I wonder if something else happened? The phone booted up fine and worked for some time after. The last thing done was charging the phone via wall charger, seeing it was done, and then unplugging.
Matt
it may not be necessary, but I would. I'd just redownload all the software I plan on loading from the start and give it a clean slate, but that's just me. Also be very careful with resorting apps and data since we really don't know the total cause of your issue. All in all you probably won't have to deal with this again as long as you minimize your risk.
nice. maybe there are aliens inside your phone! Just a thought as it seems everyone seems to just turn around when they see this problem. some of the brave ones got taken by the aliens too for snooping out too much
vitusdoom said:
nice. maybe there are aliens inside your phone! Just a thought as it seems everyone seems to just turn around when they see this problem. some of the brave ones got taken by the aliens too for snooping out too much
Click to expand...
Click to collapse
Im the alien!
Yea, I never saw this happening to me. I read carefully before I do anything and have never tried anything fancy.
Im guessing that QHSUSB_DLOAD lets you know the phone is fully erased and waiting for something to be flashed the elite way? (From the factory via their gadgets). To date, NO ONE has recovered from this.
Man Id love to be the one to recover! I crapped myself when I saw QHSUSB_DLOAD mentioned on my computer. Its the kiss of death.
I also have to wait till next week to get my replacement despite me opting for the fastest most $$$ method of shipping. UPS Express is the fastest and will take till monday (which means tuesday since no one will be around to sign for it).
Ugg..
Matt
Doh! that just sucks Matt. but then again, thats way better than having some hardware issue and being fixed (anything with hardware issue fixed surely ends up going back to the guys that fixed it. they seem to put some time bomb in there so you'll go back crying to fix it again and again. lol) haven't had this issue ever since.(was flashing my phones way back then) maybe im just lucky. hopefully i will not encounter this. (the only thing I bricked was my brand new PSP2002. just bought it from US and im way over in NZ mate - didn't have a option to return it. )
where does this QHSUSB_DLOAD appear? would this come up when you turn the device on? because i've seen some devices that are bricked, they just lit up and goes off and never charges and can't go to bootloader. thinking this is 100% bricked or this QHSUSB thingy is the pure brick?
vitusdoom said:
Doh! that just sucks Matt. but then again, thats way better than having some hardware issue and being fixed (anything with hardware issue fixed surely ends up going back to the guys that fixed it. they seem to put some time bomb in there so you'll go back crying to fix it again and again. lol) haven't had this issue ever since.(was flashing my phones way back then) maybe im just lucky. hopefully i will not encounter this. (the only thing I bricked was my brand new PSP2002. just bought it from US and im way over in NZ mate - didn't have a option to return it. )
where does this QHSUSB_DLOAD appear? would this come up when you turn the device on? because i've seen some devices that are bricked, they just lit up and goes off and never charges and can't go to bootloader. thinking this is 100% bricked or this QHSUSB thingy is the pure brick?
Click to expand...
Click to collapse
The message QHSUSB_DLOAD appears the first time I tried to connect via USB to my computer. It showed up on my computer down where usb notifications occur. After it told me it couldnt install hardware, that was it. No more action from either the phone or the computer. Its like the world just passed right by my poor phone.
Maybe I will get lucky and get a phone free of dust as well! I was waiting on calling in that care package for later...Oh well.
Matt
Oooh nice! so the device really has a black screen and that message appeared on driver installation on you computer.
most of the people in the net just mentions that this driver is missing. If the driver is missing, maybe it did really get corrupted(software because of rom-manager not pointing to this ) but yeah, could also be hardware failure. did it say on your computer that it was installing some drivers for that QHSUSB_DLOAD? and it failed? what about HTC? did you see anything from HTC about this?
vitusdoom said:
The message QHSUSB_DLOAD appears the first time I tried to connect via USB to my computer. It showed up on my computer down where usb notifications occur. After it told me it couldnt install hardware, that was it. No more action from either the phone or the computer. Its like the world just passed right by my poor phone
Click to expand...
Click to collapse
this is the EXACT problem im having! on my tmobile SGS2
not sure if this has already been mentioned but what do you guys think of this?
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-ii-jtag-brick-repair/
Hey guys,
I'm in the same situation too.... I've been flashing hundreds of roms and all kind of software on a lot of different android phones...but this is the first time ever I came across something like that where I feel that this is the end of it!!!! I made a mistake...by not paying attention flashing an HD2 rom to my sensation!!! You know some time s**t happens... and here we go...I got a completely dead bricked sensation with nothing i can do, even I've been searching and reading for 2 days with no luck what so ever...so I guess no one is able to find a solution for this issue yet!!!!Which is too bad: confused: .I wish I was able to find some solution to this problem so I can get my phone back to life and help every one else who might end up with this issue. Because I think a lot of people might be in this situation!!!. I tried every thing I can possibly do with m y knowledge and the results was all dead ends. I just hope that this issue will be taken to the next level by some one...like all the other phones that it can be unbricked...so why not the sensation!!!?. Any one can come up with and ideas for this please help us as a community to get pass by this dead end on our Htc sensations.
Guys i have absolutely same problem with my sensation, i believe there must be a way how to bring our phones back to life. Im sure that on my phone its just software problem caused by backing to s-on(got bricked right after adb rebootbootloader). So if some1 find out how to unbrick, PLEASE post it. I dont want to solve it by warrany, because its little far for me :-(
Sorry if this is the wrong place to post - just wanted to share my unpleasant experience.
I've bricked my phone in a peculiar way - it appears to be a hard brick, non-responsive to any buttons. Plugging in to the computer gets me the dreaded qhusb_dload QPST download mode. Not a good sign.
It wasn't due to faulty ROM flashing, either. I made a bad edit to /system/etc/vold.fstab fiddling with the way the internal and external SD cards get mounted - mmc1 instead of mmc2. After one reboot, I had some sd card corrupted errors. Proceeding to format the card may have been my fatal error. By the second reboot, I was bricked. D'oh. I imagine I had accidentally mounted a partition of the internal emmc that is critical to normal operations, then tried to wipe it.
From what I've read, a USB jig won't do much good, but it's worth a try.
Anyone messing around with their /system folder, be warned.
That's sux, but on a good note, $50 and a little waiting will get your phone back, or you could just warranty that sucker ;-) give more refurb units to some other xda members lol
I sense another refurb sale on ATT.com. Sorry to hear about that, sounds bad. No guts no glory right?
I purchased this as a refurb, too. The cycle continues...
Not sure how the whole exchange process will work in this case. I mean, I can exchange for a different phone, or a new Skyrocket and pay the difference, but I really had my heart set on a cheapo skyrocket. Perhaps if I take this up with Samsung instead?
Ur 90 warranty is over already? That sux then. I personally would pay $50 and get it de-bricked, its the cheapest/best option.
I didn't expect much in the way of warranties because I purchased this refurbished. With Samsung customer service I didn't have much luck. However, I just got off the phone with AT&T, and they're overnighting me a replacement, which is cool. They have a 30 day policy on any web store items, so I'm covered. Anyways, lesson learned
check this thread, please: http://forum.xda-developers.com/showthread.php?t=1522351
RussianBear said:
check this thread, please: http://forum.xda-developers.com/showthread.php?t=1522351
Click to expand...
Click to collapse
Are you in thw process of bringing that to the skyrocket?
silver03wrx said:
Are you in thw process of bringing that to the skyrocket?
Click to expand...
Click to collapse
we need all the help we can get. just a bunch of curious noobs, ya know
the main discovery we did with sensation was to make the emmc visible to any pc it's connected to, then overwriting whatever was messed up (like the hboot) with a stock version of that file.
in theory, you should be able to do this to any phone running on a qualcomm chipset once it's in the qhsusb_dload mode. still lots to test, but anyone is welcome to participate, of course!
Do you have a skyrocket that your testing on?
Obviously you know its much different then hboot
On htc.
silver03wrx said:
Do you have a skyrocket that your testing on?
Obviously you know its much different then hboot
On htc.
Click to expand...
Click to collapse
nope, just sensation. they both run on a qualcomm chipset though, so i'm just speculating here.
the bricks we're "saving" right now are for people that executed s-on without fully reading the instruction, thereby leaving them in qhsusb_dload mode. your cases might be specific to a different area, but the principal is still the same:
find what is messed up and replace it with the correct file via open emmc
Big progress made for APQ8060 and MSM86xx processors. Sensation hard brick solution coming very soon and SkyRocket/T-Mobile Galaxy S II solutions already solved...
What's this I smell? Possible de-brick
Sent from my SAMSUNG-SGH-I727
I also experience this problem on my xperia L
I messed up with vold.fstab and now my phone can't enter flashmode or it doesn't turn on also
amnher said:
I also experience this problem on my xperia L
I messed up with vold.fstab and now my phone can't enter flashmode or it doesn't turn on also
Click to expand...
Click to collapse
i have the same problem xperia miro
any updates ?
First off, I am not unhappy with my Skyrocket in general. To be fair I only purchased it because my Nexus One broke and needed a new phone, but it's been exhibiting some very annoying things that I can't tell are "common" with this phone or if they're specific to my own model. Full disclosure, I have rooted and installed different ROMS on my phone, but many of these issues have existed since before I made all the modifications. I don't know if they're because of a bad battery, bad phone, or a bit of both.
1. Battery life is ATROCIOUS. Yes I know this is not that uncommon, but considering I'm not using LTE (because AT&T thinks Puerto Rico is more important than providing service to an actual STATE that is one of the most prolific in the nation) and I don't have a lot of background processes grabbing data. I mainly use my phone during the week to check facebook and twitter and such, but in about 8 hours I can be down to 20% power. I don't recall my battery life being that bad with my N1.
2. Sometimes I'll turn on my phone and it can't contact the AT&T network. I'll have to reboot, sometimes requiring that I do a battery pull. Speaking of battery pulls..
3. Sometimes when I leave my phone to charge overnight and then disconnect the charger, the 100% message does not come up, nor does the phone turn on. Once again, another battery pull. Also, more often than not the phone isn't actually fully charged.
Anyone else experiencing this? What would you all suggest? Should I go to AT&T and demand a replacement (obviously after I restore back to stock features and possibly run the counter wipe) or just get a new battery (which I think that AT&T should pay for) or just suck it up and deal with it?
Actually talk to at&t they might send a replacement battery for free
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Yea something isn't right with your phone. Sorry you had to go through all that.
~PsyCl0ne
Sent from my SAMSUNG-SGH-I727 using XDA
Yeah, sounds like a defective battery or device. Might as well go for the new device.
Go back to stock. Reset flash counter. Get real pissy at the store and demand a replacement. Get a replacement phone.
Stupid question: How do i reset the flash counter? I mean I know there's a file out there that does it, but do I go into recovery and just do "install from Zip file?" Also, will doing the return to Stock also remove my CWM recovery?
Just flash the zip in cwm. You'll still have cwm after but your count will be NO.
Then Odin back to stock using the Samsung UCKJ2 tar (not the one in the soft brick thread). For me, sometimes going into download mode using the two button combo trips the counter again, sometimes not. Using a jig to get into dl mode will prevent tripping it (Google how to make your own--its really easy)
Sent from my SAMSUNG-SGH-I727 using xda premium
i went from the Nexus One as well. As for the general Android experience i really miss my Nexus One, but over all the dual-core cpu, expanded memory and bigger screen is enough of a reason to stick with it. I'm just patiently waiting for CM9 to come out. I'm not a big fan of Manufacturer's bloated UI's.
Fellow nexus users have you installed texasice just to taste aosp ics it's built from evervolv and runs great on the n1..... I kinda miss my track ball too but i do love the screen and speed of the lte network and the processor
Sent from my SAMSUNG-SGH-I727 using xda premium
skrambled said:
Just flash the zip in cwm. You'll still have cwm after but your count will be NO.
Then Odin back to stock using the Samsung UCKJ2 tar (not the one in the soft brick thread). For me, sometimes going into download mode using the two button combo trips the counter again, sometimes not. Using a jig to get into dl mode will prevent tripping it (Google how to make your own--its really easy)
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Where can I get that? I looked around and it seems to be at SamMobile.com, but it says I need to register to get the file. Is it somewhere else on here? Why shouldn't I use the one from the softbrick thread?
dvandam said:
Where can I get that? I looked around and it seems to be at SamMobile.com, but it says I need to register to get the file. Is it somewhere else on here? Why shouldn't I use the one from the softbrick thread?
Click to expand...
Click to collapse
The one in the soft brick thread doesn't flash the modem (not sure about the kernel, but maybe not). I'll post a link in a few when I get back to my desk
EDIT: This one: http://forum.xda-developers.com/showthread.php?t=1349207&highlight=uckj2
Once you download the file you'll need to unzip it. It'll ask for a password, enter sampro.pl . Once it's unzipped, open Odin (right click and click "Run as Administrator"). In the PDA slot place the file called HOME_SGS-I727user_CL626051.REV02.tar.md5 . Put into download mode and connect phone. Make sure Odin sees your phone (yellow COM box). Make sure nothing is checked other than Auto Reboot (DO NOT CLICK RE-PARTITION OR YOU WILL BRICK). Click Start and let it do it's thing.
Sent from my SAMSUNG-SGH-I727 using xda premium
skrambled said:
The one in the soft brick thread doesn't flash the modem (not sure about the kernel, but maybe not). I'll post a link in a few when I get back to my desk
EDIT: This one: http://forum.xda-developers.com/showthread.php?t=1349207&highlight=uckj2
Once you download the file you'll need to unzip it. It'll ask for a password, enter sampro.pl . Once it's unzipped, open Odin (right click and click "Run as Administrator"). In the PDA slot place the file called HOME_SGS-I727user_CL626051.REV02.tar.md5 . Put into download mode and connect phone. Make sure Odin sees your phone (yellow COM box). Make sure nothing is checked other than Auto Reboot (DO NOT CLICK RE-PARTITION OR YOU WILL BRICK). Click Start and let it do it's thing.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Thanks for the info.
So basically I go and get the counter reset here first: http://forum.xda-developers.com/showthread.php?t=1575712
Then I go do the Odin thing to send the phone back to it's not as cool state? Out of curiosity after I do the flash back, how can I check the flash counter?
dvandam said:
Thanks for the info.
So basically I go and get the counter reset here first: http://forum.xda-developers.com/showthread.php?t=1575712
Then I go do the Odin thing to send the phone back to it's not as cool state? Out of curiosity after I do the flash back, how can I check the flash counter?
Click to expand...
Click to collapse
Yes, first do the counter reset, then Odin back to stock. After you flash back to stock you can check the flash counter by going into download mod. You don't need to have Odin open on your computer, just have the USB plugged in to your pc, and after pulling the battery and reinserting it, hold down the volume up+down keys as you plug in the USB. You'll get the yellow warning but click up. It should say:
ODIN MODE
PRODUCT NAME: SGH-I727
CUSTOM BINARY: NO
CURRENT BINARY: SAMSUNG OFFICIAL
Before you send it back you'll want to go into Settings/About Phone and make sure your baseband is UCKJ2, with the original kernel version (2.6.35.11). Lastly, go into Settings/Security and do a Factory Data Reset (check Format USB Storage to wipe out everything you have on there). Reboot and make sure you get the initial setup screen.
I'll try this all soon and head back to the AT&T store this weekend after I take a double shot of tequila so my inhibitions go down so I won't take any guff (but hopefully won't get me to Mel Gibson levels..)
I have a weird question: If I did a Nandroid/CWM backup and then did the Odin thing, what would happen if I rooted then reinstalled CWM and then did a restore? Would my phone go back to what it was or does it not work that way?
On a COMPLETELY unrelated topic I found this to be amusing from Gizmodo..
http://gizmodo.com/5903436/this-is-objectively-the-worst-default-email-signature
dvandam said:
I'll try this all soon and head back to the AT&T store this weekend after I take a double shot of tequila so my inhibitions go down so I won't take any guff (but hopefully won't get me to Mel Gibson levels..)
I have a weird question: If I did a Nandroid/CWM backup and then did the Odin thing, what would happen if I rooted then reinstalled CWM and then did a restore? Would my phone go back to what it was or does it not work that way?
On a COMPLETELY unrelated topic I found this to be amusing from Gizmodo..
http://gizmodo.com/5903436/this-is-objectively-the-worst-default-email-signature
Click to expand...
Click to collapse
Nandroid backups tend to be a little buggy and you might find weird things happening (or you could brick altogether--not likely but possible).
I'd recommend using Titanium Backup to back up all your apps, and then backing up the Titanium folder, along with any pictures, music, etc. you want to keep to a desktop computer.
You're better off getting off to a fresh start with a new device and not introducing any bugs that may have been leftover on your Nandroid backup (including potential bugs that may be related to the problems you're having).
skrambled said:
Nandroid backups tend to be a little buggy and you might find weird things happening (or you could brick altogether--not likely but possible).
I'd recommend using Titanium Backup to back up all your apps, and then backing up the Titanium folder, along with any pictures, music, etc. you want to keep to a desktop computer.
You're better off getting off to a fresh start with a new device and not introducing any bugs that may have been leftover on your Nandroid backup (including potential bugs that may be related to the problems you're having).
Click to expand...
Click to collapse
That was my original plan. Just thought it would be nice to bypass a few steps if I could.
Also, I lol'd at that article man! I don't use the stock email app so I hadn't run into this.
It is a phone worth bragging about having, but imo any signature block with two trademark symbols in it is going a little overboard.
Out of curiosity do you know how long this is supposed to take? It seems like it's been on <ID:0/003> system.img.ext4 for an uncomfortably long amount of time..
dvandam said:
1. Battery life is ATROCIOUS. Yes I know this is not that uncommon, but considering I'm not using LTE (because AT&T thinks Puerto Rico is more important than providing service to an actual STATE that is one of the most prolific in the nation) and I don't have a lot of background processes grabbing data. I mainly use my phone during the week to check facebook and twitter and such, but in about 8 hours I can be down to 20% power. I don't recall my battery life being that bad with my N1.
Click to expand...
Click to collapse
What's wrong with puerto pico? My girlfriend is puerto rican and she's gorgeous. hahaha
Anyway this happened with my T989, swap it!!! Or use warranty with Samsung if you must.
dvandam said:
Out of curiosity do you know how long this is supposed to take? It seems like it's been on <ID:0/003> system.img.ext4 for an uncomfortably long amount of time..
Click to expand...
Click to collapse
Took a long time last time I did it.
Still stuck there?
Sent from my SAMSUNG-SGH-I727 using xda premium
skrambled said:
Took a long time last time I did it.
Still stuck there?
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
I ended up going against all conventional wisdom and turned off the phone. Now it's giving me the Yellow Triangle but I re-started ODIN and re-ran the process and now it's running at a more acceptable pace. I Don't know if it'll work, but now it's on amss.bin as opposed to being stuck on that section for like 30 minutes.
Of course now it's taking an excessive amount of time on the amss.bin step... I knew I should have started this earlier in the night (and with less drinks in my system..) It also says "MODEM" on the top left white box..
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