Database Info

[Q] (Help!) Hard bricked skyrocket?

Hey guys,
So I have the Galaxy S2 Skyrocket with AT&T and I have it rooted etc. Today I tried flashing the MIUI rom, but was unsuccessful due to a message saying "Installation aborted". So I did as I read to do and wiped cache, Delvik or w/e, and then I reformatted the SDcard to redownload the ROM, however when I rebooted the next time it did not boot back up. Now I have the phone completely dead it would seem, I have tried the button combinations, etc to no avail.
What happened and is there anything I can do?
How can my phone be bricked if I never got to install a new ROM? I can't be without it for too long so any answers would be appreciated
Thanks,
Smernst

When you say button combinations are you saying you tried to get into download mode?
Sent from my SAMSUNG-SGH-I727

Sheolrock said:
When you say button combinations are you saying you tried to get into download mode?
Sent from my SAMSUNG-SGH-I727
Click to expand...
Click to collapse
Yes, exactly that

Smernst said:
Yes, exactly that
Click to expand...
Click to collapse
Sometimes download mode can work even if the screen isn't turning on. You should follow the instructions for download mode and see if Odin recognizes the phone.
Sent from my SAMSUNG-SGH-I727

Well there are symptoms of Brick See below and find ur category!!!!
appdroid said:
Brick → When used in reference to consumer electronics, "brick" describes a device that cannot function in any capacity (such as a device with damaged firmware). This usage derives from the fact that some electronic devices (and their detachable power supplies) are vaguely brick-shaped, and so those which do not function are useful only as actual bricks. The term can also be used as a verb. For example, "I bricked my phone when I tried to modify its firmware.
Hard Brick → When your phone does not turn on at all. When you can’t get in to CWR/CWM Or Stock recovery. You are basically screwed. If its hard brick Here is thread that will help you!!!
Soft Brick → When your phone bootloops. When you can get into CWR/CWM. When You can use jigtag to get into download mode.
Click to expand...
Click to collapse
Smernst said:
Yes, exactly that
Click to expand...
Click to collapse

appdroid said:
Well there are symptoms of Brick See below and find ur category!!!!
Click to expand...
Click to collapse
UPDATE:
I just went in to the AT&T store and they are sending me a new phone tonight and it should be here tomorrow!
Now, does anyone have a guide to recommend for getting, say, MIUI onto the Samsung Galaxy S2 Skyrocket? I don't know enough about the versions, mp5, etc to do it alone, and a safe guide would really help me
Thanks

MIUI rite now is not daily driver has lots of bugs and Here is link scroll down it will give you step by step instructions.
Smernst said:
UPDATE:
I just went in to the AT&T store and they are sending me a new phone tonight and it should be here tomorrow!
Now, does anyone have a guide to recommend for getting, say, MIUI onto the Samsung Galaxy S2 Skyrocket? I don't know enough about the versions, mp5, etc to do it alone, and a safe guide would really help me
Thanks
Click to expand...
Click to collapse

Got it, thanks
Also, if my phone is truly hard-bricked the AT&T guys that I return it to will not be able to tell that it is rooted will they?
Thanks

No att ppl are dumb and they can't even turn on the phone so they won't be able to say that it was rooted. When they ask you anything about rooting just pretend like you don't know what they are talking about.
Smernst said:
Got it, thanks
Also, if my phone is truly hard-bricked the AT&T guys that I return it to will not be able to tell that it is rooted will they?
Thanks
Click to expand...
Click to collapse

appdroid said:
No att ppl are dumb and they can't even turn on the phone so they won't be able to say that it was rooted. When they ask you anything about rooting just pretend like you don't know what they are talking about.
Click to expand...
Click to collapse
Okay sweet thank you for all the help!
See you around
Smernst

Hope next phone doesn't give you any grief.
Sent from my SAMSUNG-SGH-I727 using xda premium

i727 black screen after bad flash pls help

1st time flashing my phone
following steps on odin3
according to instruction i need to use odin3+PDA
I DID odin3+PIT+START
and now my phone go into download mode
try 3 bottom reset
try connection to computer (detects the new hardware QHSUSB_DLOAD)
no download screen
no odin3
what should i do
------------------------
UPDATE
ok now i know my phone is hard brick
is it possible to send it back to Samsung and have it reflash? (i know it's not under warranty but can it be done? or anyone know how much it might cost me)
--------------------------------
UPDATE WITH FIX
called samsung repair center
told them i was doing over the air update for new fw
phone lost connection and wont turn on the next day
asked me what happened
i answered i did update last night, when i wake up phone wont turn on
asked me did flash it by myself
i just play stupid and say i dont understand
asked me will phone go into recovery mode
i answered no
samsung repair center gave me a repair ticket number
Product Symptoms : Technical Inquiry/Mobile OS Updates/Incomplete Software Upgrade
Warranty : In Warranty
send it back to samsung (they check to see if water dmg, nothing found, replace mainboard and reflash it)
LOL I AM SO HAPPY I CALLED
i will be a good boy next time, wont be messing around with custom rom anymore, learned my lesson.

Sounds like a hard brick
Might try getting it replaced by your carrier.
Sent from my SGH-I727

Sheolrock said:
Sounds like a hard brick
Might try getting it replaced by your carrier.
Sent from my SGH-I727
Click to expand...
Click to collapse
"Hi -Insert ATT Service Rep Name Here-. I woke up this morning and my phone wouldn't turn on anymore, please help me fix it"

lol this suxs i am going back to silly ios
didn't realize android phone can brick by using the wrong software

summerof2008 said:
lol this suxs i am going back to silly ios
didn't realize android phone can brick by using the wrong software
Click to expand...
Click to collapse
Really? You had no idea it was possible to brick a phone by flashing firmware that wasn't made for it? Really?
Sent from my SGH-I777

summerof2008 said:
lol this suxs i am going back to silly ios
didn't realize android phone can brick by using the wrong software
Click to expand...
Click to collapse
Wrong software?
Sent from my SGH-I727

for noobs like me, android is too complicated.
i don't hate it, i think it's for more advance users.
after using the android for a couple week i still think ios is a lot ez to use.

IOS is garbage plain and simple. Apple forces you to use things THEIR way. With android you can fully customize every aspect of your phone. I've had an iphone and their crap compared to Android, especially this skyrocket.

Restore
Try going into recovery mode (turn phone on while holding both volume buttons) and if u made a backup before restore to it, if not then mount ur usb storage from there and put a new rom on it in the root folder then try to install that but try a clean wipe and all that first to
all this can be done in the recovery menu

summerof2008 said:
for noobs like me, android is too complicated.
i don't hate it, i think it's for more advance users.
after using the android for a couple week i still think ios is a lot ez to use.
Click to expand...
Click to collapse
It's not android that's complicated.. You could have stay stock and use different launchers to achieve alot of customized looks but you JUMPED in and it sounds like you might have not have been prepared with enough info... I'm going to give you some good advice someone gave me....search is your friend, and YouTube is your friend, and follow the damn instructions... Those words have helped me.. I also say know when your ready to play with the systems. There's nothing wrong with reading all the post and using them for reference material.
Sent from my Xoom using xda premium

guys i got my phone fixed.
anyone with a hard brick should try to call sasung repair center and do what i did.

Details?
Sent from my SAMSUNG-SGH-I727 using xda premium

summerof2008 said:
guys i got my phone fixed.
anyone with a hard brick should try to call sasung repair center and do what i did.
Click to expand...
Click to collapse
What exactly did they do to it?
Sent from my SAMSUNG-SGH-I727 using xda premium

It wasn't that he flashed wrong software its that he flashed a non pit file in the pit. Doesn't pit basically set up the file system and partition everything?

[Q] Hard Bricked? Don't see how....

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

Flashed My Phone Incorrectly Now It Won't Boot

I was following a tutorial on rooting my Galaxy S3 and by mistake I loaded the "VRALEC.bootchain.tar.md5" file under the boot loader option rather than the PDA option.
This was the tutorial "How To Root Verizon Samsung Galaxy S3 4.1.2/4.1.1 & Install CWM Recovery! SCH-I535."
Now my phone won't boot at all and isn't being recognized by my computer when plugged in. Any help with this is greatly appreciated!

dsims9t said:
I was following a tutorial on rooting my Galaxy S3 and by mistake I loaded the "VRALEC.bootchain.tar.md5" file under the boot loader option rather than the PDA option.
This was the tutorial "How To Root Verizon Samsung Galaxy S3 4.1.2/4.1.1 & Install CWM Recovery! SCH-I535."
Now my phone won't boot at all and isn't being recognized by my computer when plugged in. Any help with this is greatly appreciated!
Click to expand...
Click to collapse
If your phone doesn't power on at all no led, no recovery or download access, no vibration even, then I'm afraid by putting the VRALEC.bootchain.tar.md5 in the wrong spot and flashing it through Odin you have hard bricked your phone. At this point warranty would be your best option.
Sent from my SCH-I535 using xda premium

shimp208 said:
If your phone doesn't power on at all no led, no recovery or download access, no vibration even, then I'm afraid by putting the VRALEC.bootchain.tar.md5 in the wrong spot and flashing it through Odin you have hard bricked your phone. At this point warranty would be your best option.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Dude he voided his warranty by rooting so JTAG is best option.

jmxc23 said:
Dude he voided his warranty by rooting so JTAG is best option.
Click to expand...
Click to collapse
Dude...
If anyone at Verizon has any clue why a phone won;t turn on , then you might be right, but they don;t and they don;t have the time to worry with it, so they will just replace it if its less than a year old.

DigitalMD said:
Dude...
If anyone at Verizon has any clue why a phone won;t turn on , then you might be right, but they don;t and they don;t have the time to worry with it, so they will just replace it if its less than a year old.
Click to expand...
Click to collapse
That part is true.

So there's absolutely no way to recover it at this point. I didn't get a warranty on it specifically because I was planning on running Cyanogenmod.

It has a 1 year warranty that Verizon will honor
Sent from my SCH-I535 using xda app-developers app

dsims9t said:
So there's absolutely no way to recover it at this point. I didn't get a warranty on it specifically because I was planning on running Cyanogenmod.
Click to expand...
Click to collapse
No, there is a way to recover it. There just is not a fixable way via xda. Third party services such as MobileTechVideos can fix your phone via jtag as a few others suggest.

dsims9t said:
So there's absolutely no way to recover it at this point. I didn't get a warranty on it specifically because I was planning on running Cyanogenmod.
Click to expand...
Click to collapse
If you don't have a warranty on your device the only other real option is to use JTAG to revive the phone. I would recommend checking out this place that will repair your bricked Galaxy S3 for you.

Seems to be an almost daily occurrence. Reading a new thread because someone can't follow directions and bricking their phone.
Sent from my SCH-I535 using xda premium

bbqsfire said:
Seems to be an almost daily occurrence. Reading a new thread because someone can't follow directions and bricking their phone.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
He was simply asking if it could be fixed, which is kind of what this section is for. I personally would've asked the same question if it happened to me because I haven't seen any questions based on this specific chain of events. He just put the file in the wrong slot, could happen to people, now this specific question will be able to be searched for by people who actually search.
So to answer the question, your bootloader is kind of your essential command for your phone that starts the booting process. You basically erased that with a file that doesn't execute that process. Luckily a jtag is able to rewrite that entire command. I think it's only $60, which is well worth the cost.
Sent from my SCH-I535 using Tapatalk 2

Root and Unlock Boot loader for 4.3?

Did a Google and forum search and couldn't find anything concrete. Any help would be appreciated. Thanks in advance.
Sent from my SCH-I535 using Tapatalk

ProtheusIRC said:
Did a Google and forum search and couldn't find anything concrete. Any help would be appreciated. Thanks in advance.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
With 4.3, the bootloader is locked permanent and at the moment there's no way to unlock. Once on 4.3 you can't downgrade or flash custom rom/kernel or custom recovery, however, you can root 4.3 with saferoot here http://forum.xda-developers.com/showthread.php?t=2565758

So no CWM? Is anyone working on it? What about this "Safestrap"?
Sent from my SCH-I535 using Tapatalk

ProtheusIRC said:
So no CWM? Is anyone working on it? What about this "Safestrap"?
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Yes no CWM or TWRP since the bootloader is locked. Safestrap is a method of installing a separate loader from the locked one, it's working on some model like att S4, note, but not Verizon S3. The software is not stable yet, still have many bugs and glitches. I won't touch it...not just yet.

Lol ok. Well at least we have root.
Sent from my SCH-I535 using Tapatalk

ProtheusIRC said:
Lol ok. Well at least we have root.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I'm still keeping my ears open for an unlocked bootloder. Root is all well and good, but I'm getting jittery about flashing a different rom. Any news about progress on this?

akambience said:
I'm still keeping my ears open for an unlocked bootloder. Root is all well and good, but I'm getting jittery about flashing a different rom. Any news about progress on this?
Click to expand...
Click to collapse
The bootloader will never be unlocked. The original bootloader on the Verizon s3 wasn't even "unlocked." It was a completely different boot image that was leaked. AFAIK, no bootloader has ever been unlocked through hard coding. There are simply loopholes & workarounds. Kexec and Safestrap are two examples of workarounds. They are pretty much just as good as the real thing so there is still hope for those crack-flashers taken off guard by the new update.
Still, I can't sympathize with people who start threads like these: There have been countless "I took the 4.3 update. How do I flash ROMs?" posts. If you were really into flashing, you would never be in this situation.
It's the cardinal rule. NEVER ACCEPT OTAs!!!!!!

BattsNotIncld said:
The bootloader will never be unlocked. The original bootloader on the Verizon s3 wasn't even "unlocked." It was a completely different boot image that was leaked. AFAIK, no bootloader has ever been unlocked through hard coding. There are simply loopholes & workarounds. Kexec and Safestrap are two examples of workarounds. They are pretty much just as good as the real thing so there is still hope for those crack-flashers taken off guard by the new update.
Still, I can't sympathize with people who start threads like these: There have been countless "I took the 4.3 update. How do I flash ROMs?" posts. If you were really into flashing, you would never be in this situation.
It's the cardinal rule. NEVER ACCEPT OTAs!!!!!!
Click to expand...
Click to collapse
You didn't have to word it in that way. You sounded as if you were talking to a child, and then told me, in not so many words "Boo hoo, cry about it". This thread is old and I've learned quit a bit since then so next time you necro post, how about not being such a ****?
Sent from my SCH-I535 using Tapatalk

ProtheusIRC said:
You didn't have to word it in that way. You sounded as if you were talking to a child, and then told me, in not so many words "Boo hoo, cry about it". This thread is old and I've learned quit a bit since then so next time you necro post, how about not being such a ****?
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Didn't mean to come off as a ****. I was just responding to the bootloader comment and went off on a rant. Sorry if you were offended.

I was, but you are one of the few who take responsibility for offending someone, so it's cool.
BattsNotIncld said:
Still, I can't sympathize with people who start threads like these
Click to expand...
Click to collapse
This was the part that offended me the most. Now, I'm by no means a noob, but I am man enough to admit there are LOTS of things I don't know. This phone was my brothers. HE took the OTA then traded it to me. So I was trying to find a way out of it. I've come to terms (I think) with being stuck with a locked bootloader but I am hopeful about kexec. Who knows?
Apology accepted.
Sent from my SCH-I535 using Tapatalk

Yeah since I didn't even know your whole story, I wasn't necessarily referring to you (even though it sounded like that). I was more referring to people that said they knowingly accepted the OTA. I just worded it very poorly.
That's unfortunate how you ended up with the locked bootloader, but the devs we have are outstanding and I'm sure they'll get a workaround going very soon. :good:

Haha This is what happened when no one unlocked the boot loader..lol
Sent from my Galaxy Nexus using xda premium

Don't do it!!!I unlocked the boot loader with ez unlock app and booted into recovery and hard bricked my sch i535. Just got it back got fixed with jtag. Gabbyanne on eBay is a life saver... Don't do it to yourself. Trust me
Sent from my SCH-I535 using Tapatalk[/QUOTE]

Germanlopez007 said:
Don't do it!!!I unlocked the boot loader with ez unlock app and booted into recovery and hard bricked my sch i535. Just got it back got fixed with jtag. Gabbyanne on eBay is a life saver... Don't do it to yourself. Trust me
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Out of curiosity did jtag get you back to 4.1.2? I don't think anyone has reported one way or the other. From what I understand it should be impossible even for jtag but it's always good to verify.

ThePagel said:
Out of curiosity did jtag get you back to 4.1.2? I don't think anyone has reported one way or the other. From what I understand it should be impossible even for jtag but it's always good to verify.
Click to expand...
Click to collapse
It is impossible, you can't jtag the bootloader over the 4.3 baseband. It's more complicated after the update because the hardware keys are different. Changing the bootloader is only changing the software.
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
It is impossible, you can't jtag the bootloader over the 4.3 baseband. It's more complicated after the update because the hardware keys are different. Changing the bootloader is only changing the software.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I know just waned to make sure. You can never be sure until it is tried. For example invisiblek said that the ml1 firmware will brick the phone if you upgrade from a phone with the insecure bootloader because that's what happened to the s4 that took a 4.3 upgrade. Well I know from experience that wasn't true. Theory is just that until it has been tested who knows what samsung might have forgotten to do that might allow jtag to do that. Plus I have yet to hear if anyone has tried. Not saying it hasn't been done I just haven't seen anyone say more than got it back and it works.
*edit* I just found that thread he said you will brick and I must of missed the part where he said you probably wont if you upgrade the entire boot chain. But how would you end up in that scenario of being bricked? The root66 tars took out the entire boot chain and added only the insecure bootloader.

ThePagel said:
I know just waned to make sure. You can never be sure until it is tried. For example invisiblek said that the ml1 firmware will brick the phone if you upgrade from a phone with the insecure bootloader because that's what happened to the s4 that took a 4.3 upgrade. Well I know from experience that wasn't true. Theory is just that until it has been tested who knows what samsung might have forgotten to do that might allow jtag to do that. Plus I have yet to hear if anyone has tried. Not saying it hasn't been done I just haven't seen anyone say more than got it back and it works.
Click to expand...
Click to collapse
I get what you're saying, if it wasn't hardware coded then it could theoretically work.
The same thing could be accomplished through Odin though by flashing boot chains, ez unlock also proves it's hardware signed. Jtag would do the same thing ez unlock does, just on a more holistic level.
Best bet would be to Jtag a 4.3 developer edition bootloader, but I don't think it exists, because making one widely available for developer edition phones would be handing us an unlocked bootloader. They'd have to be made on a per phone basis with specific keys for each device. I highly doubt it exists, but if it did it might work if we could figure out how it's getting around the bootloader, like what step it's bypassing.
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
I get what you're saying, if it wasn't hardware coded then it could theoretically work.
The same thing could be accomplished through Odin though by flashing boot chains, ez unlock also proves it's hardware signed. Jtag would do the same thing ez unlock does, just on a more holistic level.
Best bet would be to Jtag a 4.3 developer edition bootloader, but I don't think it exists, because making one widely available for developer edition phones would be handing us an unlocked bootloader. They'd have to be made on a per phone basis with specific keys for each device. I highly doubt it exists, but if it did it might work if we could figure out how it's getting around the bootloader, like what step it's bypassing.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Truth but I had a idea a couple months ago but I don't have the balls to try it. With these qualcomm gs3 phones there is a emergency boot from sd card for the aboot. If you were hard bricked it might be possible to boot to the insecure bootloader that way. You could never do the flash back trick with terminal emulate so it wouldn't be a true fix but who cares unless you need your sd card (I do but I have learned to love 4.3).

ThePagel said:
Truth but I had a idea a couple months ago but I don't have the balls to try it. With these qualcomm gs3 phones there is a emergency boot from sd card for the aboot. If you were hard bricked it might be possible to boot to the insecure bootloader that way. You could never do the flash back trick with terminal emulate so it wouldn't be a true fix but who cares unless you need your sd card (I do but I have learned to love 4.3).
Click to expand...
Click to collapse
Really?
Ya, if you could do that you could simply run straight from the aboot file without the secure checks. That might actually work, but you'd have to get the insecure aboot loaded without it locking the phone, you'd have to try it immediately after loading the aboot image before a reboot.
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
Really?
Ya, if you could do that you could simply run straight from the aboot file without the secure checks. That might actually work, but you'd have to get the insecure aboot loaded without it locking the phone, you'd have to try it immediately after loading the aboot image before a reboot.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
well you would need the debrick file from the insecure bootloader. that is what the debrick image is its the aboot image. So now that I think about it a little more the only way that would work is if qualcomm has its own bootchain and I would not doubt if it did but I am not technical enough to figure that out. the only way for people like me to find out is try and I will not purposelessly brick to try. I cant even justify asking someone who is hard bricked to try it. They are already mad it happened why add that extra stress.
---------- Post added at 03:34 AM ---------- Previous post was at 03:30 AM ----------
holy cow its 3:23 here I better go to bed so I can wake up at 9 and hopefully not fall asleep driving tomorrow.