Since it says I can't post a reply in the Liquid's thread because I'm a new user. Yes, I'm actually a newb user. Here's what happened.
I did a backup of everything, including my current ROM which was rooted stock VZW ICS. MyBackup Pro'd everything, used Clockwork Recovery Mod and flashed the touchy GUI for the recovery mode. Backed up the nandroid as stated. Downloaded the Liquid ROM zip and then went into the CWM recovery mode. Wiped cache partition, then Dalvik cache and did a wipe factory data reset (bad idea, probably) and then it was done flashing in about 5 seconds (which I thought was a bit quick.. it said success!) so then I rebooted. Now it's dead.
It won't even turn on, did a battery pull (this is while the battery was at 100% because I was still plugged in via USB) and put it back in 5 mins later. It won't turn on at all, even with all of the methods like holding down the volume and home buttons, so I'm guessing it's bricked.
I'm already thinking of calling Verizon to add insurance on this to get a replacement if there's no other solution.
Wow that's terrible I've never heard of this situation but I will look into it and post any solutions
Unleashing the force using my new Jedi powers!
---------- Post added at 03:53 AM ---------- Previous post was at 03:41 AM ----------
So far this is what I've found - > http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-iii-jtag-brick-repair/
Unleashing the force using my new Jedi powers!
I'm not liking the cost of this thing... I've had this phone for two weeks so I may just call them and tell them that it stopped working and get a replacement.
Good idea I'm sure that'll work
Unleashing the force using my new Jedi powers!
Sorry for not looking. There's a thread on this already here: http://forum.xda-developers.com/showthread.php?t=1846682
Mods please close this.
Thought so, a friend pointed it out for me. Apparently I forgot to put on a Jelly Bean bootloader of some kind, which resulted in this. I didn't fully pay attention to the fact that the Liquid ROM I installed was a Jelly Bean OS. Called Verizon, they're sending me a reconditioned phone. Hopefully it isn't as bad as it sounds...
N0wy0ud1e said:
Thought so, a friend pointed it out for me. Apparently I forgot to put on a Jelly Bean bootloader of some kind, which resulted in this. I didn't fully pay attention to the fact that the Liquid ROM I installed was a Jelly Bean OS. Called Verizon, they're sending me a reconditioned phone. Hopefully it isn't as bad as it sounds...
Click to expand...
Click to collapse
It's better than the one in your hand.
Sent from my SCH-I535 using Tapatalk 2
N0wy0ud1e said:
Thought so, a friend pointed it out for me. Apparently I forgot to put on a Jelly Bean bootloader of some kind, which resulted in this. I didn't fully pay attention to the fact that the Liquid ROM I installed was a Jelly Bean OS. Called Verizon, they're sending me a reconditioned phone. Hopefully it isn't as bad as it sounds...
Click to expand...
Click to collapse
Please take this kindly...but you need to do ALOT more research before flashing anything on your device. There is no jelly bean bootloader, you have to unlock the stock bootloader so you can flash custom roms/kernels. If you fail this step, then you get a soft brick. Please read the stickies in dev section.
N0wy0ud1e said:
Thought so, a friend pointed it out for me. Apparently I forgot to put on a Jelly Bean bootloader of some kind, which resulted in this. I didn't fully pay attention to the fact that the Liquid ROM I installed was a Jelly Bean OS. Called Verizon, they're sending me a reconditioned phone. Hopefully it isn't as bad as it sounds...
Click to expand...
Click to collapse
Wow. Just wow. Never thought I would say it, but I actually feel bad for Verizon for having to replace your phone due to you not researching things.
N0wy0ud1e said:
Thought so, a friend pointed it out for me. Apparently I forgot to put on a Jelly Bean bootloader of some kind, which resulted in this. I didn't fully pay attention to the fact that the Liquid ROM I installed was a Jelly Bean OS. Called Verizon, they're sending me a reconditioned phone. Hopefully it isn't as bad as it sounds...
Click to expand...
Click to collapse
I'd buy your "bricked one". With a little work you could have prevented this.
Sent from my SCH-I535 using xda app-developers app
It makes one wonder why verizon decided to lock the bootloader.
jtiger12 said:
It makes one wonder why verizon decided to lock the bootloader.
Click to expand...
Click to collapse
Well it surely couldn't be because of all the warranty fraud :/
Sent from my htc_jewel using Tapatalk 2
bobloblaw1 said:
Well it surely couldn't be because of all the warranty fraud :/
Sent from my htc_jewel using Tapatalk 2
Click to expand...
Click to collapse
Lulz
bobloblaw1 said:
Well it surely couldn't be because of all the warranty fraud :/
Sent from my htc_jewel using Tapatalk 2
Click to expand...
Click to collapse
Warranty fraud? You mean where someone breaks their phone by improperly flashing something onto it, then lies to Verizon to get the phone replaced at Verizon's expense? That NEVER happens.:silly:
what does "not turn on" mean
I flashed LIQUIDSMOOTH - Gaps and the awsome Koontz kernel a few days ago and my phone won't reboot. I have no idea what happened (My battery might have run down durring the install. The primary symptom is -- It doesn't "turn on" and I can't get to CWM recovery but I can get to Samsung download mode. Home, Power Vol down opens Samsung download mode.
I was a click away from sending it off to the fixer (Don't want to report another one lost or stolen) -- The fix costs $100+ and I would be without my device for at least 1 week.
I have been researching solutions for 2 days and while it has been time consuming and has taken time away from the family, I think I will be able to un-brick, re-root, flash an AOKP or AOSP ROM + the KT747 (I think thats the name) and be up and running in an hour or two....
Not all bricks are lack of research
tomc99999 said:
I flashed LIQUIDSMOOTH - Gaps and the awsome Koontz kernel a few days ago and my phone won't reboot. I have no idea what happened (My battery might have run down durring the install. The primary symptom is -- It doesn't "turn on" and I can't get to CWM recovery but I can get to Samsung download mode. Home, Power Vol down opens Samsung download mode.
I was a click away from sending it off to the fixer (Don't want to report another one lost or stolen) -- The fix costs $100+ and I would be without my device for at least 1 week.
I have been researching solutions for 2 days and while it has been time consuming and has taken time away from the family, I think I will be able to un-brick, re-root, flash an AOKP or AOSP ROM + the KT747 (I think thats the name) and be up and running in an hour or two....
Click to expand...
Click to collapse
was running clean rom, went to jelly beans V15,, after a few weeks battery drain was bad reflashed all was ok,, then went to flash carbon rom and same issue, cant reboot, cant do anything, battery pull and Vol up with power and home does nothing.. seems samsung also has a motherboard flaw that shorts out. not rom related but i am sure all the rebooting is not helping. around 150-200 reboots it dies,.,. xda has a whole write up on it. so maybe the people worried they researched to little might have been doing it right and the junk portion of the phone gave out. I will take my replacement thank you very much. call it warantee fraud if you will but if its not software related it not from a bad flash.. those you can recover from, odin or one click should save your bacon. A fried pico or micro fuse or other bad part is different.
Related
I was trying to update my mom's Infuse to ICS, then all of a sudden this (attached) happened. Heimdall had just given me the libusb.dll error (I needed to update the bootloader cause I kept getting rainbows in CWM), so I was unplugging the phone so I could get the right drivers.
I have a horrible feeling I did something very wrong. I can't imagine why what I was doing would have caused this though, since the cmd had gone back to a default state after giving the error.
Is there any way to fix this?? Thanks a ton in advance!
mvgc3 said:
I was trying to update my mom's Infuse to ICS, then all of a sudden this (attached) happened. Heimdall had just given me the libusb.dll error (I needed to update the bootloader cause I kept getting rainbows in CWM), so I was unplugging the phone so I could get the right drivers.
I have a horrible feeling I did something very wrong. I can't imagine why what I was doing would have caused this though, since the cmd had gone back to a default state after giving the error.
Is there any way to fix this?? Thanks a ton in advance!
Click to expand...
Click to collapse
can you get it into download mode...?
if so run the one click again and you might have to check the box for bootloaders, on the second run...meaning I would run it twice...
It does that immediately on power up. Doesn't even get to the Samsung screen. Odin will recognize the phone, but when I try to flash a return to stock package (which I used earlier perfectly fine), it says the md5 is invalid.
Like I said, I never even got to the point of installing the bootloader since I forgot about the drivers. Are you saying I should install the drivers and try to flash the bootloader again?
Thanks so much for the help! I've never had this much trouble with a phone before
EDIT: I'm a dumbass. since I couldn't see the screen, I forgot to press up again after entering download mode. Odin is now in the process of installing the aforementioned return to stock package. And I think it worked!
You have no idea how grateful I am of you for pointing that out! I feel kind of dumb for not trying it, but when the screen looked like that I could only assume there was no functionality!
THANKS AGAIN! Times a million!
Lol ok let us know when you get it up and running....kk
Sent from my SAMSUNG-SGH-I717 using xda premium
What EXACTLY gave you the idea to put your mother's phone on a ROM that half works and has many bugs? Just trying to understand... I could have done this to my friend's mom's atrix, but I didn't because the stock ROM will always have the least bugs for unpopular devices like ours. (ones that don't get official support for CM or AKOP or anything)
wayzata said:
What EXACTLY gave you the idea to put your mother's phone on a ROM that half works and has many bugs? Just trying to understand... I could have done this to my friend's mom's atrix, but I didn't because the stock ROM will always have the least bugs for unpopular devices like ours. (ones that don't get official support for CM or AKOP or anything)
Click to expand...
Click to collapse
whooo there...slow your roll...
the op has the options to put what he wants, and actually if you have been tracking the ICS/CM9/AOKP threads they have made leaps in the smashing of bugs....actually very stable and good to go now, seeing how just months ago we didn't even have any ver of ICS, and yes it takes homework to install..
and you kept stock on your friends Mommy phone well that was between you and him and Mommy...
so long story short....as far as unpopular, I see this device being sold and for a high demand on CL and Ebay...with all the support given here...that is my IMHO...as is yours
+10 Char
bigjoe2675 said:
whooo there...slow your roll...
the op has the options to put what he wants, and actually if you have not been tracking the ICS/CM9/AOKP threads they have made leaps in the smashing of bugs....actually very stable and good to go now, seeing how just months ago we didn't even have any ver of ICS, and yes it takes homework to install..
and you kept stock on your friends Mommy phone well that was between you and him and Mommy...
so long story short....as far as unpopular, I see this device being sold and for a high demand on CL and Ebay...with all the support given here...that is plenty IMHO...as is yours
Click to expand...
Click to collapse
This makes about as much sense in English as it does in Japanese.
wayzata said:
This makes about as much sense in English as it does in Japanese.
Click to expand...
Click to collapse
You are a smart guy... i am sure you understood me....
Arigatou gozaimasu btw...just leave it as that....
Hajimemashita Joe sama
Sent from my SGH-I997 using xda premium
mvgc3 said:
I was trying to update my mom's Infuse to ICS, then all of a sudden this (attached) happened. Heimdall had just given me the libusb.dll error (I needed to update the bootloader cause I kept getting rainbows in CWM), so I was unplugging the phone so I could get the right drivers.
I have a horrible feeling I did something very wrong. I can't imagine why what I was doing would have caused this though, since the cmd had gone back to a default state after giving the error.
Is there any way to fix this?? Thanks a ton in advance!
Click to expand...
Click to collapse
Same thing happened to mine when i flashed back to stock. Kept trying download mode and finally worked. Keep trying and also try recovery. Worked for me
Sent from my SAMSUNG-SGH-I717 using xda premium
wayzata said:
What EXACTLY gave you the idea to put your mother's phone on a ROM that half works and has many bugs? Just trying to understand... I could have done this to my friend's mom's atrix, but I didn't because the stock ROM will always have the least bugs for unpopular devices like ours. (ones that don't get official support for CM or AKOP or anything)
Click to expand...
Click to collapse
First of all, every once in a while, she asks me if there are any updates yet.
Second, there's only a short list of insignificant bugs mentioned in the ICS topics.
I flashed GB on it a while back, and I figured since CWM and everything was set up already I wouldn't have a problem; flash, reboot, flash again, done. Unfortunately, it wasn't flashing the second time for whatever reason, and I figured it had something to do with the now half-functional CWM.
Anyway, to those of you who weren't unreasonably judging me, and rather decided to help: Thank you, the phone is now back up and running!
Prometh1216 said:
Hajimemashita Joe sama
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
LOL, woooooooootttttttt
Same thing happened to me. What I did was send my phone back to Samsung tell them everything ( except about rooting) they will email you a label then ship it off and get back in about 1 week. They will put stock gingerbread on it. Hopes this helps.
Sent from my SAMSUNG-SGH-I997 using Tapatalk 2
I just hard bricked my sgs3. FIRST TIME EVER!! I've been flashing roms,kernels, etc since the MyTouch3.
Little back story.....
I flashed the LSmooth - Linaro 4.2.1 Jelly Bean Rom with CWM6. I noticed that I could not find my nandroid backups. Searched XDA and saw a thread that stated that TWRP is compatible with 4.2.1 and it will move the internal /sdcard from /0 back to its original file location, etc, etc. I went to GooManager, downloaded the twrp.tar (d2vzw), then went to MobileOdin, loaded the .tar file and flashed.
BOOM!!! No power, DOA. dead ass!! :crying::crying:
(( FACE SLAP )) then I remembered via build.prop it was configured as "maguro" and not "d2vzw". So, I'm assuming that since I failed to edit the build.prop before flashing the d2vzw TWRP recovery, it bricked my phone.
-- No power via wall, usb
-- No download / recovery mode
-- NOTHING!
My question is, if I were to call in and ask for a warranty exchange, what is the likely hood of Verizon troubleshooting, reviving my phone and figuring it out that its been rooted?
Or, should I just send my phone to someone that can JTAG it for me?
Idk if you're permanently hard bricked. Reason being is because this person flashed the latest twrp using GooManager but it installed the Maguro version. Different method but they were able to get out of it. Have you tried pulling the battery then booting holding all three buttons for like 15-20 seconds? Might take a few tries.
Verizon could care less I think.
I have had three droid razrs replaced just because of a boot loop and if they would look into the memory, they could clearly see I rooted if.
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
Idk if you're permanently hard bricked. Reason being is because this person flashed the latest twrp using GooManager but it installed the Maguro version. Different method but they were able to get out of it. Have you tried pulling the battery then booting holding all three buttons for like 15-20 seconds? Might take a few tries.
Click to expand...
Click to collapse
I saw that post, lol. I tried that, but I will try it again. thanks
barrackOBAMA said:
Verizon could care less I think.
I have had three droid razrs replaced just because of a boot loop and if they would look into the memory, they could clearly see I rooted if.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Cool! Thanks!
MOD Close Thread, pls
MOD,
Can you close this thread please. Got my replacement today, so I'm Good.!!
Well I was doing a back up and flashed a new ROM, Blinky's revenge, and when I went to reboot nothing. My battery was at 94%.
When I got to plug in the charger I do not even get the battery icon. I cannot reboot into CWM I get nothing.
Do I now own a nice paper weight?
It is still under the one year warrenty. Will they know what happened if I send it in and tell them it is not working period?
Thank you
What phone do you have?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Galaxy 2 skyrocket SGH i727
catchjeff said:
Galaxy 2 skyrocket SGH i727
Click to expand...
Click to collapse
Can you get into download mode?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
catchjeff said:
Galaxy 2 skyrocket SGH i727
Click to expand...
Click to collapse
Are you sure you got the right rom for the i727, where did you get it from. If it doesn't turn on or boot up no one can tell that you tried to flash a rom. It sure sounds like you've bricked it. Any luck getting odin to recognize it. If it does, flash the stock rom.
Sent from the short bus
catchjeff said:
Well I was doing a back up and flashed a new ROM, Blinky's revenge, and when I went to reboot nothing. My battery was at 94%.
When I got to plug in the charger I do not even get the battery icon. I cannot reboot into CWM I get nothing.
Do I now own a nice paper weight?
It is still under the one year warrenty. Will they know what happened if I send it in and tell them it is not working period?
Thank you
Click to expand...
Click to collapse
here's how you check for a heart beat on the phone plug it into the PC and see if you get a Qhusb DL if you do enjoy the paper weight... and maybe an exchange might but the carrier can only give you an answer
Gosh dang it mother F$*%er thats where I messed up.
I can not get into download mode nor get odin to reconize it. It is officially a paper weight. I put in for an exchange with AT&T should be here tomorrow.
I flashed the wrong ROM. I flashed for the I777 not the i727. I hit the wrong button when I was installing I meant to go back but hit the power button by error and that is what did it.
Thank you everyone for your help. It is the first time I ever bricked a phone and I have rooted about 9 different phones and this was completely my error.
Now here is a question. Will they be able to tell it was rooted and I bricked it?
Probably not. From experience, I don't think you need to worry.
Sent from the short bus
catchjeff said:
Gosh dang it mother F$*%er thats where I messed up.
I can not get into download mode nor get odin to reconize it. It is officially a paper weight. I put in for an exchange with AT&T should be here tomorrow.
I flashed the wrong ROM. I flashed for the I777 not the i727. I hit the wrong button when I was installing I meant to go back but hit the power button by error and that is what did it.
Thank you everyone for your help. It is the first time I ever bricked a phone and I have rooted about 9 different phones and this was completely my error.
Now here is a question. Will they be able to tell it was rooted and I bricked it?
Click to expand...
Click to collapse
No they won't be able to tell anything.
Question...why did you have a Rom for a different phone on your sd card?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
xcrazydx said:
No they won't be able to tell anything.
Question...why did you have a Rom for a different phone on your sd card?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Stupid error. I was using my QR code reader to download and must have hit the wrong QR code and just from habit I hit download. Never made this mistake before ever.
I just want to kick myself in the arse.
catchjeff said:
Stupid error. I was using my QR code reader to download and must have hit the wrong QR code and just from habit I hit download. Never made this mistake before ever.
I just want to kick myself in the arse.
Click to expand...
Click to collapse
Poo happens. Luckily, you're within a year, so it's just a couple weeks without a Skyrocket (if it won't turn on, Sammy can't tell that it was rooted and bricked on a flash). If you were outside of 12 months, well, that would've been a pretty costly lesson. I still double-check the file name before flashing anything on any of my phones, including my Cappy, just to make absolutely certain I'm not about to flash something for a different phone by mistake.
T.J. Bender said:
Poo happens. Luckily, you're within a year, so it's just a couple weeks without a Skyrocket (if it won't turn on, Sammy can't tell that it was rooted and bricked on a flash). If you were outside of 12 months, well, that would've been a pretty costly lesson. I still double-check the file name before flashing anything on any of my phones, including my Cappy, just to make absolutely certain I'm not about to flash something for a different phone by mistake.
Click to expand...
Click to collapse
Yeah I was within a year and just got my new phone yesterday and wiped all the rom and kernals off my sd card and will just take the time to redo everyting which is kind of fun for me. I get to do most of this stuff at work on my work pc.
Thank you everyone
Your the bomb
I just hit you all with a thanks!!!!
That is what I love about this community, you guys and gals are there for us when we need it and even when we do not.
I got it rooted and CWM on there now time to wipe and re do my roms. Just glad I got a backup of my previous setup before the bricking.
Ladies and Gents,
I made sure I chose the correct RUU based on my CID (CWS__001)
I relocked my phone and attempted to install "RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_ 0.24p.32.09.06_10.130.32.34_release_signed.exe". After the RUU finished my phone seems to be hard bricked.
Won't Boot.
No power lights.
I knew this could happen when flashing an international version. AFTER getting owned I also found this post http://forum.xda-developers.com/showthread.php?t=2181929. Which was blatantly in the beginning of the forum. Has anyone found a fix for this issue, or is my only option JTAG repair?
Thanks,
Ryan
ryan9316 said:
Ladies and Gents,
I made sure I chose the correct RUU based on my CID (CWS__001)
I relocked my phone and attempted to install "RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_ 0.24p.32.09.06_10.130.32.34_release_signed.exe". After the RUU finished my phone seems to be hard bricked.
Won't Boot.
No power lights.
I knew this could happen when flashing an international version. AFTER getting owned I also found this post http://forum.xda-developers.com/showthread.php?t=2181929. Which was blatantly in the beginning of the forum. Has anyone found a fix for this issue, or is my only option JTAG repair?
Thanks,
Ryan
Click to expand...
Click to collapse
You could take your phone back and tell them it won't boot etc.
If you can't get it to boot neither can they, so no-one will know it's been unlocked/rooted.
Some people will say this is fraudulent, but hey, if you can live with yourself who cares what anyone else thinks?
Pft I returned mine to Telus when the same thing happened to me. The way I see it, it was HTC's RUU that bricked my phone, not me. Like you, I did not have supercid and was S-ON.
You could try the unbrick Evita thread. If you make it past step 3 you can save your phone.
You'll need to boot to Linux.
Sent from my One X using xda app-developers app
exad said:
Pft I returned mine to Telus when the same thing happened to me. The way I see it, it was HTC's RUU that bricked my phone, not me. Like you, I did not have supercid and was S-ON.
You could try the unbrick Evita thread. If you make it past step 3 you can save your phone.
You'll need to boot to Linux.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I saw this and will give it a try, thank you for the advice!
ryan9316 said:
I saw this and will give it a try, thank you for the advice!
Click to expand...
Click to collapse
I bricked my phone trying to install elementalx and phone wouldn't boot at all and no lights. sent it in for jtag and they told me emmc controller was unresponsive and sent it back to me. looks like I may have to trash the phone... or make a few bucks on ebay.
mkalbarc said:
I bricked my phone trying to install elementalx and phone wouldn't boot at all and no lights. sent it in for jtag and they told me emmc controller was unresponsive and sent it back to me. looks like I may have to trash the phone... or make a few bucks on ebay.
Click to expand...
Click to collapse
Did they refund you? I was going to send it into mobiletechvideos for JTAG. I don't see the phones selling for more than 100$ on ebay.
ryan9316 said:
Did they refund you? I was going to send it into mobiletechvideos for JTAG. I don't see the phones selling for more than 100$ on ebay.
Click to expand...
Click to collapse
If the emmc controller isn't responding, it's worth even less than that.
Sent from my One X using xda app-developers app
ryan9316 said:
Did they refund you? I was going to send it into mobiletechvideos for JTAG. I don't see the phones selling for more than 100$ on ebay.
Click to expand...
Click to collapse
they did refund. minus the cost of shipping and something else, however. it was worth a try though... All I know though is I will never touch an elemental kernel again... not worth it that's for sure...
mkalbarc said:
they did refund. minus the cost of shipping and something else, however. it was worth a try though... All I know though is I will never touch an elemental kernel again... not worth it that's for sure...
Click to expand...
Click to collapse
Just curious about your situation. Did the kernel flash successfully and then just not boot? What ROM were you flashing it over? Tons of people, myself included, have flashed that kernel without issue so I'm interested in what exactly happened.
pside15 said:
Just curious about your situation. Did the kernel flash successfully and then just not boot? What ROM were you flashing it over? Tons of people, myself included, have flashed that kernel without issue so I'm interested in what exactly happened.
Click to expand...
Click to collapse
Sure, I too have used their kernels and have never had an issue until this time. So I started to install the kernel and it froze at I believe 60%? Then it sat... It said the flash could take awhile so to just wait so I did... For 2 hours. I knew something wasn't right because no elemental flash has taken my phone longer than a few minutes before this one so without thinking i'd hurt anything I held the buttons to hard power off the phone. After it shut off it's been completely dead since. No charge lights, no sign of any life at all other then the QHSUSB_DLOAD under device manager when plugged into my PC. the rom that I had flashed was the latest cleanrom. super bummed but i'll get over it. the worst part about this was I had pics of my kids that I had not backed up that are now lost.
mkalbarc said:
Sure, I too have used their kernels and have never had an issue until this time. So I started to install the kernel and it froze at I believe 60%? Then it sat... It said the flash could take awhile so to just wait so I did... For 2 hours. I knew something wasn't right because no elemental flash has taken my phone longer than a few minutes before this one so without thinking i'd hurt anything I held the buttons to hard power off the phone. After it shut off it's been completely dead since. No charge lights, no sign of any life at all other then the QHSUSB_DLOAD under device manager when plugged into my PC. super bummed but i'll get over it. the worst part about this was I had pics of my kids that I had not backed up that are now lost.
Click to expand...
Click to collapse
That does suck about the pictures. That would upset me more than the phone as well. I went and looked at the thread after I saw your post and saw a couple of other bricks aside from yours in the last couple of hundred posts. Very unfortunate that flashing a kernel bricked it. I try to stay away from anything that uses the Aroma Installer unless there are no other options, not saying that was the problem, but I've had numerous issues with it previously. After seeing multiple bricks from a basic kernel flash I'm going to definitely be more cautious about what I flash from now on. I'd be totally screwed if I bricked this phone. Anyway, hope you end up with something better out of this, like the HTC One.
pside15 said:
That does suck about the pictures. That would upset me more than the phone as well. I went and looked at the thread after I saw your post and saw a couple of other bricks aside from yours in the last couple of hundred posts. Very unfortunate that flashing a kernel bricked it. I try to stay away from anything that uses the Aroma Installer unless there are no other options, not saying that was the problem, but I've had numerous issues with it previously. After seeing multiple bricks from a basic kernel flash I'm going to definitely be more cautious about what I flash from now on. I'd be totally screwed if I bricked this phone. Anyway, hope you end up with something better out of this, like the HTC One.
Click to expand...
Click to collapse
Funny thing about the One... I was thinking about getting it but after this issue I will never look at another phone that doesn't have a removable sd card...
I think a key thing to note here is that you are flashing software that has been altered by someone you don't know and you can never be sure that things will work out. There's huge risks associated with rooting/unlocking your phone. If there wasn't HTC would warrant your phone regardless of what you do.
If you don't have an answer to the question "What will I do when I brick my phone?" don't root. Whenever modding anything, consoles, phones, set top boxes, I always assume that I will render it unusable. If that doesn't sit well with me, I don't modify it. That should be the general rule of thumb to follow.
Sent from my One X using xda app-developers app
3 words: Dropbox Camera Upload.
exad said:
I think a key thing to note here is that you are flashing software that has been altered by someone you don't know and you can never be sure that things will work out. There's huge risks associated with rooting/unlocking your phone. If there wasn't HTC would warrant your phone regardless of what you do.
If you don't have an answer to the question "What will I do when I brick my phone?" don't root. Whenever modding anything, consoles, phones, set top boxes, I always assume that I will render it unusable. If that doesn't sit well with me, I don't modify it. That should be the general rule of thumb to follow.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Very well said... I always get a little nervous when screwing with a new $500+ device.
Sent from my HTC One X using xda app-developers app
iElvis said:
3 words: Dropbox Camera Upload.
Click to expand...
Click to collapse
Thank you for the advice! I will remember that with my next phone.
I just use g+ to instantly upload my photos. Unlimited space is hard to argue with
Sent from my One X using xda app-developers app
phone not able to boot
guys please help me out I flashed stock root JB ROM after that my device wont boot just white screen with HTC logo. The phone boots into recovery but I wiped the sd card SD card mount error is being returned.
Clockworkmod recovery v6.0.3.1 S off
anuj.sherawat said:
guys please help me out I flashed stock root JB ROM after that my device wont boot just white screen with HTC logo. The phone boots into recovery but I wiped the sd card SD card mount error is being returned.
Clockworkmod recovery v6.0.3.1 S off
Click to expand...
Click to collapse
Install twrp 2.3.3.1 and reformat sd card with a pc. Move Rom to sd and reflash. And also what hboot? I know you said s-off bit did you fastboot the boot.img and see is that helped?
Sent from my HTC One X using xda app-developers app
31ken31 said:
Install twrp 2.3.3.1 and reformat sd card with a pc. Move Rom to sd and reflash. And also what hboot? I know you said s-off bit did you fastboot the boot.img and see is that helped?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
thanks first of all I was on CMW, formatted the drive as computer prompted, lost the data but was able to flash the ROM and fastboot the boot image to phone.
Now only one problem the phone restarts and then goes to boot loop everytime I have to fastboot the boot image file.
DO I need to change the recovery and is there any way to by pass the fastboot process? Sorry for noob question
okay i upgraded to 4.3 OTA and tried to revert back and soft bricked my phone. I still have access to download mode and the stock recovery. I know now that i can not revert but is there any way of getting it back to 4.3 so i can have a phone again?
thanks for the future help.
This is similar what happened to me. I have never done anything with my phone as far as rooting and I tried reverting to stock 4.1.2. In Odin I kept getting the "Nand Start! Fail (Auth)" because of the locked bootloader I guess. I flashed some other firmware that was unofficial with the locked bootloader and now I get the "unauthorized software detected" and I cant do anything but enter Odin download mode. What should I do?
that is exactly what is happing to me. same error and all.
Once you took the OTA 4.3 you got locked in. No way of going back.
Sent from my SCH-I535 using Tapatalk
I dont want to go back just get rid of the soft brick so i can use it
im having the same problem and need to get it fixed please help anyone???!!!! im leaving for florida in two days and have nothing else. HELP!!!!
If you took the OTA and tried to flash 4.1.2 Odin or unlock bootloader you are Hard bricked , no method or recovering it yet.
If you have stock recovery and download mode , only hope is wait for 4.3 .tar file
Theres no custom recovery I can flash and flash some other software or something?
Elemt said:
Theres no custom recovery I can flash and flash some other software or something?
Click to expand...
Click to collapse
Nope , once you take 4.3 OTA you done , no flashing anything. And once you try to flash recovery or revert to older software you are bricked.
Sorry to be the bear of bad news.
There is a full thread of why and how so many devices have been bricked
http://forum.xda-developers.com/showthread.php?t=2575661
jlyle said:
Nope , once you take 4.3 OTA you done , no flashing anything. And once you try to flash recovery or revert to older software you are bricked.
Sorry to be the bear of bad news.
There is a full thread of why and how so many devices have been bricked
http://forum.xda-developers.com/showthread.php?t=2575661
Click to expand...
Click to collapse
Do you know if anyone is working on a fix? or a .tar file of 4.3?
dvdavid2 said:
Do you know if anyone is working on a fix? or a .tar file of 4.3?
Click to expand...
Click to collapse
Thanks for the info. hopefully a fix will be done soon. And do you know how i should keep to see when the work around is finished .
thanks in advanced guys.
This might give you a chance to unbrick.... possibly
http://forum.xda-developers.com/showthread.php?t=2581166
I got the "unauthorised software detected" on my phone like 3 days ago from messing up on a recovery and all I did was go into the Verizon store and said idk what happened and they called technical support and they asked me if I flashed software on my phone and I just said "no, I just plugged it into my laptop and it did this" so they said they will just send me a new sgs3 and I just got it today.
Pretty simple.
And I don't have insurance .
Hit thanks if I helped
Sent from my SCH-I535 using xda app-developers app
ScubaSteev said:
I got the "unauthorised software detected" on my phone like 3 days ago from messing up on a recovery and all I did was go into the Verizon store and said idk what happened and they called technical support and they asked me if I flashed software on my phone and I just said "no, I just plugged it into my laptop and it did this" so they said they will just send me a new sgs3 and I just got it today.
Pretty simple.
And I don't have insurance .
Hit thanks if I helped
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Funny thing is Verizon can tell if phone was hacked with, and can choose to add the cost of phone to your bill so this method is not highly recommended.
Sent from my SCH-I535 using xda app-developers app
jlyle said:
Funny thing is Verizon can tell if phone was hacked with, and can choose to add the cost of phone to your bill so this method is not highly recommended.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Any break throughs????
dvdavid2 said:
Any break throughs????
Click to expand...
Click to collapse
None that I have seen
Sent from my SCH-I535 using xda app-developers app
jlyle said:
Funny thing is Verizon can tell if phone was hacked with, and can choose to add the cost of phone to your bill so this method is not highly recommended.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Not to mention it is basically fraud, and is the main reason Verizon decided to start locking down phones in the first place.
I understand everyone is taking risks when flashing custom, and flashes can go wrong even when you do everything right, but there is VERY little chance of bricking your phone if you take your time and do a bit of research before you hit any buttons. And if you do manage to brick your phone, man up and pay for a new phone or pay for it to be fixed. Otherwise stop treating your $600 piece of technology like a toy.
BattsNotIncld said:
Not to mention it is basically fraud, and is the main reason Verizon decided to start locking down phones in the first place.
I understand everyone is taking risks when flashing custom, and flashes can go wrong even when you do everything right, but there is VERY little chance of bricking your phone if you take your time and do a bit of research before you hit any buttons. And if you do manage to brick your phone, man up and pay for a new phone or pay for it to be fixed. Otherwise stop treating your $600 piece of technology like a toy.
Click to expand...
Click to collapse
The first time I ever rooted, I was worried about bricking. So i read everything I could find relevant.
Why in the world anyone would flash without reading is beyond me. Every single thread in Verizon Galaxy S3 at least mentions, if not totally devoted, to how bad 4.3 is and if you flash something on it you will brick.
I just don't get it.
Sent from my Last Ever Samsung Device.
If you do a battery pull and start back up in download mode (might take a couple of times to get it to work) then use the Verizon software upgrade assistant it should fix it but you will be stuck with 4.3. Worked for me