• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [Virgin Mobile] Hard bricked

taatoken said:
I Hard brick saturday flashing to LiquidSmooth. I am abou to follow up the steps listed [GUIDE]Unbrick a Hard Bricked SPRINT Galaxy S3 (Without JTAG) ; is there anything special I need to do since I am on a VM phone?
Click to expand...

Flashing a ROM shouldn't be able to brick your phone. Can you give us more details. What exactly did you flash, what did you wipe? Can you boot to recovery? Can you restore a nandroid? Is the phone recognized by your computer/Odin?
 
upconvert said:
Flashing a ROM shouldn't be able to brick your phone. Can you give us more details. What exactly did you flash, what did you wipe? Can you boot to recovery? Can you restore a nandroid? Is the phone recognized by your computer/Odin?
Click to expand...

Basically I was flashing to the rom, Flash went great. Pressed reboot in philz recovery and the screen shut off. The screen has not come on despite all my efforts.

What exactly did you flash?
Modified LiquidSmooth Nightly (3/10 Build), PA GApps Full Modular 20140307

what did you wipe?
clean wipe for new rom install using philz recovery

Can you boot to recovery?
No I can not. Screen doesn't come on. Yes, I have tried every trick to make the phone come on except a USB Jig(its on its way)

Can you restore a nandroid?
No I can not. Screen will no appear

]Is the phone recognized by your computer/Odin?
No/No

Thanks for all your help :)
 
Have u pulled the battery and put back in then hold the 3 button combo to get back into recovery?
 
This is odd. To say the very least I think you have a hardware issue. I have bricked my phone many times and this issue your having must be board related. If you remove the battery and plug the phone in and see no red light on the front ( with battery out ) then it is fubared and better hope its got a factory warranty. I usually busy my screen and send it back or something like the power button don't work heh. I'm on phone #5 this year :)
 
I agree with J4. Sounds like your motherboard may have failed. I had it happen with my last phone. Thankfully, it was still under warranty and LG replaced it. If that is indeed what happened, no need to worry about sending in a rooted phone. They won't be able to tell.

If you cannot get into download mode or recovery and your phone is less than a year old, send it to Samsung. If you don't know exactly how old the phone is, Samsung knows when it was activated and can tell you if it is still under warranty.

Good luck.
 
taatoken said:
yes,i have done that multiple times
Click to expand...

That sucks. I don't see how flashing a ROM could have borked your recovery. Maybe you have a hardware issue that just happened to show up then. If you do the volume up, home, power combo for 6 seconds, then plug into a PC, do you have adb access?
 
j475328 said:
This is odd. To say the very least I think you have a hardware issue. I have bricked my phone many times and this issue your having must be board related. If you remove the battery and plug the phone in and see no red light on the front ( with battery out ) then it is fubared and better hope its got a factory warranty. I usually busy my screen and send it back or something like the power button don't work heh. I'm on phone #5 this year :)
Click to expand...

I do get a red light when i plug it in without the battery, though. HOPE?:dontknow:

upconvert said:
That sucks. I don't see how flashing a ROM could have borked your recovery. Maybe you have a hardware issue that just happened to show up then. If you do the volume up, home, power combo for 6 seconds, then plug into a PC, do you have adb access?
Click to expand...

Still nothing though.
 
Dude the red Light is the key. Your phones still alive. What u need to do is get a debrick image from over at XDA developers. Burn it to a 16gb SD card and then reboot into recovery mode. It will boot from the SD card and then u will have to Odin a stock ROM and re root and all that hot mess.
 
Cause the red light is just saying JTAG me and jack off a lot of time. I never JTAG nothing and when u Odin the ROM if your phone had Knox before then u have to use a Knox ROM. Trust me there is no way around that bs I tried. Phone 4 went like that.
 
Here's is something Shabby gave us over in the Boost section. It will work for VM. Just replace the Boost files with VM. This is it. If this won't save your phone then it truly is a brick.

For those of you who don't know Shabby, he's one of the resident gurus here at Android Forums.

Here is the link to his tutorial.
http://androidforums.com/showthread.php?p=6153866
 
j475328 said:
Dude the red Light is the key. Your phones still alive. What u need to do is get a debrick image from over at XDA developers. Burn it to a 16gb SD card and then reboot into recovery mode. It will boot from the SD card and then u will have to Odin a stock ROM and re root and all that hot mess.
Click to expand...
thanks for the hope. I did that already still no response from my phone bu tI read on XDA one user had to keep doing the button combo 30 times and the phone some how come back alive.
wetbiker7 said:
Here's is something Shabby gave us over in the Boost section. It will work for VM. Just replace the Boost files with VM. This is it. If this won't save your phone then it truly is a brick.

For those of you who don't know Shabby, he's one of the resident gurus here at Android Forums.

Here is the link to his tutorial.
How to truly unbrick your SGS3 - Boost SGS3 - Android Forums
Click to expand...

Do I use "there" ODIN Backup for --> SPH-L710_MD7 stock?
 
It is not unheard of to Hard Brick our phone while flashing a ROM, seeing as most ROMs edit the boot partition with a custom kernel or otherwise. If you had MD5/KNOX on the phone, you dun goofed. If you plug it into your computer and Device Manager says "QHSUSB_DLOAD" as an Unrecognized Device... you've tripped KNOX and there is absolutely nothing you can do (I'm speaking out of 110% experience, I've done it.)

The Unbricking without a jtag/jig or even with a jig do not work for MK5, unfortunately, Unless they updated the debrick image since I've tried.

My phone was covered under a retailer (shall not be named) protection plan and I was able to swap my phone without sending it out for service. If you happen to get a new phone that has MD# firmware on it, DO NOT OTA, follow instructions on here & XDA to get MK5 firmware without KNOX onto the phone.
 
FatalIll said:
It is not unheard of to Hard Brick our phone while flashing a ROM, seeing as most ROMs edit the boot partition with a custom kernel or otherwise. If you had MD5/KNOX on the phone, you dun goofed. If you plug it into your computer and Device Manager says "QHSUSB_DLOAD" as an Unrecognized Device... you've tripped KNOX and there is absolutely nothing you can do (I'm speaking out of 110% experience, I've done it.)

The Unbricking without a jtag/jig or even with a jig do not work for MK5, unfortunately, Unless they updated the debrick image since I've tried.

My phone was covered under a retailer (shall not be named) protection plan and I was able to swap my phone without sending it out for service. If you happen to get a new phone that has MD# firmware on it, DO NOT OTA, follow instructions on here & XDA to get MK5 firmware without KNOX onto the phone.
Click to expand...


might not be unheard of but it is very rare to get hard brick from a rom flash, typically you end up with a soft brick or bootloops but being as recovery is separate from the OS your usually able to still get into it, being as none of these roms here have anything thatll cause knox to lock you out


if you flash a rom with your sdcard formatted in exfat that can result in awful things as exfat isnt supported and can become corrupt or unreadable whenever it wants to but again id atleast think recovery would still be able to be accessed

besides all that i would probly have to agree with everyone else, the phone seems to still partially be there but it seems like a hardware failure may have happened at the time of flashing, which is just an uncontrollable issue with electronics, questions never is will it fail cause its a 100% going to at somepoint, but more when will it fail and will the warranty still be intact

Planned Product Failure, all companies now a days do it,apple is the biggest of them all top do it and they have gotten good at it lol, theyve been sued over it a few times
 
FatalIll said:
It is not unheard of to Hard Brick our phone while flashing a ROM, seeing as most ROMs edit the boot partition with a custom kernel or otherwise. If you had MD5/KNOX on the phone, you dun goofed. If you plug it into your computer and Device Manager says "QHSUSB_DLOAD" as an Unrecognized Device... you've tripped KNOX and there is absolutely nothing you can do (I'm speaking out of 110% experience, I've done it.)

The Unbricking without a jtag/jig or even with a jig do not work for MK5, unfortunately, Unless they updated the debrick image since I've tried.

My phone was covered under a retailer (shall not be named) protection plan and I was able to swap my phone without sending it out for service. If you happen to get a new phone that has MD# firmware on it, DO NOT OTA, follow instructions on here & XDA to get MK5 firmware without KNOX onto the phone.
Click to expand...

I don't know how i trip knox because I been using the lastet Carbon Rom and just want to switch after using liquidsmooth on my HTC EVO 3d.(should have bought
triangle away:()

Tokens210 said:
might not be unheard of but it is very rare to get hard brick from a rom flash, typically you end up with a soft brick or bootloops but being as recovery is separate from the OS your usually able to still get into it, being as none of these roms here have anything thatll cause knox to lock you out


if you flash a rom with your sdcard formatted in exfat that can result in awful things as exfat isnt supported and can become corrupt or unreadable whenever it wants to but again id atleast think recovery would still be able to be accessed

besides all that i would probly have to agree with everyone else, the phone seems to still partially be there but it seems like a hardware failure may have happened at the time of flashing, which is just an uncontrollable issue with electronics, questions never is will it fail cause its a 100% going to at somepoint, but more when will it fail and will the warranty still be intact

Planned Product Failure, all companies now a days do it,apple is the biggest of them all top do it and they have gotten good at it lol, theyve been sued over it a few times
Click to expand...

Well its still under warranty, so I that
 
taatoken said:
thanks for the hope. I did that already still no response from my phone bu tI read on XDA one user had to keep doing the button combo 30 times and the phone some how come back alive.


Do I use "there" ODIN Backup for --> SPH-L710_MD7 stock?
Click to expand...

Pretty sure that's a Boost image. You might want to ask Shabby. Struckn might know whether you can use that image. You may need to locate the VM image. If Boost has their own then one was made for VM too.

I just read your last comment and you said your phone is under warranty. Personally, I would send that pesky SOB to the factory. :D
 
wetbiker7 said:
Pretty sure that's a Boost image. You might want to ask Shabby. Struckn might no whether you can use that image. You may need to locate the VM image. If Boost has their own then one was made for VM too.

I just read your last comment and you said your phone is under warranty. Personally, I would send that pesky SOB to the factory. :D
Click to expand...


same, id send it back

now that you said it was the carbon rom as well ive seen many ppl have no issues with it, well flashing it anyway lol, i wonder if you had a bad download but still id figure recovery wold still work even if that was so

again all i can come back to is but the craziest luck ever you may have had a hardware failure after the flash, maybe the first boot was too much for it and it gave out, in which case be happy it did it now while still undr warranty lol


PS triangle away will do nothing on the S3, no rom has a bootloader or anything like that to trip knox and the knox "trip" is an e-fuse, cannot be undone once done
 
Tokens210 said:
same, id send it back

now that you said it was the carbon rom as well ive seen many ppl have no issues with it, well flashing it anyway lol, i wonder if you had a bad download but still id figure recovery wold still work even if that was so

again all i can come back to is but the craziest luck ever you may have had a hardware failure after the flash, maybe the first boot was too much for it and it gave out, in which case be happy it did it now while still undr warranty lol


PS triangle away will do nothing on the S3, no rom has a bootloader or anything like that to trip knox and the knox "trip" is an e-fuse, cannot be undone once done
Click to expand...

Yep. I'm thinking hardware failure too. I agree. He should have still been able to boot into recovery.

Back to the factory!
 
As long as the ROM you tried to install doesn't have a bootloader in it then you haven't tripped Knox and killed it. You can trip Knox by installing a ROM just fine and it doesn't do anything but ruin warranty. If you install a stock ROM from before knox, it will have a bootloader and a boot loader flash will destroy it and make it unfixable.
 
I'm curious if he mistakenly flash an international version? It could cause the issue he's having and people mistakenly do this often.

I've been thinking about this thread and what could have caused this besides hardware failure. Flashing an international ROM is the only thing I can think of.

So, to the author of the OP, @taatoken. Can you double check the ROM, if you still have a copy of it on a pc or elsewhere, and verify the ROM you flashed isn't for the international version of the S3?

Thanks,
WB7
 
wetbiker7 said:
I'm curious if he mistakenly flash an international version? It could cause the issue he's having and people mistakenly do this often.

I've been thinking about this thread and what could have caused this besides hardware failure. Flashing an international ROM is the only thing I can think of.

So, to the author of the OP, @taatoken. Can you double check the ROM, if you still have a copy of it on a pc or elsewhere, and verify the ROM you flashed isn't for the international version of the S3?

Thanks,
WB7
Click to expand...
Yup, verified the rom and it was the correct version. I got my replacement but now im being a lil baby about rooting it again. this week I have had some bad tech karma. OH BTdubs USB JIG did Jack diddly butt-to-ground squat. But I can add it to my tech box or loan it out to someone who needs it.
 
taatoken said:
Yup, verified the rom and it was the correct version. I got my replacement but now im being a lil baby about rooting it again. this week I have had some bad tech karma. OH BTdubs USB JIG did Jack diddly butt-to-ground squat. But I can add it to my tech box or loan it out to someone who needs it.
Click to expand...


OK, thanks for verifying that. My gears start turning when stuff like this happens. Especially when the user is flashing the correct files. As we've discussed, when that happens it's usually hardware. Since you've verified that the the correct zip was flashed I'd say that the probability of MB failure is around 99
 
You must log in or register to reply here.
Back
Top Bottom