So I came from 2 HTC devices, the incredible then the rezound and almost never saw stories about bricks or anything of that nature. Almost anything you did could be easily fixed by running an ruu. Anyways, now I'm here and looking through the thread there seems to be a lot of people with bricks and missing radio info( not sure what that's about?) And all sorts if different issues. Anyways, my question is, how much easier is it to hard brick a gs3 compared to other HTC devices?
Sent from my SCH-I535 using xda app-developers app
Most people claiming bricks don't actually have one, and anyone who has actually bricked their phone has almost certainly done something wrong. There is a strange IMEI issue and data loss which is supposedly fixable with QPST. Still, don't ever remember having IMEI issues ever before.
Zalithian said:
Most people claiming bricks don't actually have one, and anyone who has actually bricked their phone has almost certainly done something wrong. There is a strange IMEI issue and data loss which is supposedly fixable with QPST. Still, don't ever remember having IMEI issues ever before.
Click to expand...
Click to collapse
Ok so how badly do you have to screw up to get a hard brick? Also, what is qpst?
Sent from my SCH-I535 using xda app-developers app
werdna87 said:
Ok so how badly do you have to screw up to get a hard brick? Also, what is qpst?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
To hard brick, you pretty much need to flash the wrong thing to the wrong place.
QPST is Qualcomm Product Support Tools, a tool used for some things (including backing up NV/IMEI)
Zalithian said:
To hard brick, you pretty much need to flash the wrong thing to the wrong place.
QPST is Qualcomm Product Support Tools, a tool used for some things (including backing up NV/IMEI)
Click to expand...
Click to collapse
So just by flashing romsn I'm not gonna have an issue with flashing stuff to the wrong place correct? They all include scripts that make sure of that. Also I know we got the bootloader unlocked recently. Is that similar to S-off on HTC devices?
Sent from my SCH-I535 using xda app-developers app
werdna87 said:
So just by flashing romsn I'm not gonna have an issue with flashing stuff to the wrong place correct? They all include scripts that make sure of that. Also I know we got the bootloader unlocked recently. Is that similar to S-off on HTC devices?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Flashing ROMS shouldn't hurt anything if you do it properly/don't do anything stupid in ODIN and have an NV/IMEI backup. I would wait until the IMEI issues are sorted, personally. You can still lose data, your IMEI and be stuck in roaming. I don't know how many people have used QPST backups of their NV to fix their IMEI problems.
I don't know about S-off so I can't comment on any similarities, but with the bootloader unlocked you can flash custom roms/kernels.
Zalithian said:
Flashing ROMS shouldn't hurt anything if you do it properly/don't do anything stupid in ODIN and have an NV/IMEI backup. I would wait until the IMEI issues are sorted, personally. You can still lose data, your IMEI and be stuck in roaming. I don't know how many people have used QPST backups of their NV to fix their IMEI problems.
I don't know about S-off so I can't comment on any similarities, but with the bootloader unlocked you can flash custom roms/kernels.
Click to expand...
Click to collapse
The QPST fix takes like 10 minutes and works fine, without leaving you stuck in roaming, and is even faster if you had the foresight to use QPST to make a backup beforehand. At this point, it's not really something to be worried about unless you're crack flashing at a time when you wouldn't have access to a computer to fix it.
ind3p3nd3nt said:
The QPST fix takes like 10 minutes and works fine, without leaving you stuck in roaming, and is even faster if you had the foresight to use QPST to make a backup beforehand. At this point, it's not really something to be worried about unless you're crack flashing at a time when you wouldn't have access to a computer to fix it.
Click to expand...
Click to collapse
Sounds good then. I hadn't heard of many people using QPST backups to restore their IMEI yet.
Related
So will we still have the IMEI issue even with the unlocked bootloader when flashing AOSP? I know we can fully back up our efs files but jw if its still gonna be an issue? Thanks
Sent from my SCH-I535 using xda premium
killerT721 said:
So will we still have the IMEI issue even with the unlocked bootloader when flashing AOSP? I know we can fully back up our efs files but jw if its still gonna be an issue? Thanks
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
The IMEI issue is unrelated to the bootloader as other carrier versions have experienced the same problems.
killerT721 said:
So will we still have the IMEI issue even with the unlocked bootloader when flashing AOSP? I know we can fully back up our efs files but jw if its still gonna be an issue? Thanks
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
The two are not related. I'm not sure people are entirely sure what causes the IMEI issue.
Most claim it's from flashing AOSP roms however others have reported the same issue even when flashing stock ROMS or flashing nandroids.
I'm assuming if the devs here are bright enough to crack the bootloader, a fix for the IMEI issue will arise soon.
My limited understanding thus far is that you can back up the IMEI, you can restore the IMEI with or without a backup, however there may be a problem with the phone roaming after all is said and done.
Personally I'm holding tight a little longer to see if there is a resolution to the IMEI issue
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
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.
So i bought me a new used nexus 5 on craigslist from some old chinese guy. He said it wasn't connecting to a network no matter what or whose sim cards he used and how many times he rooted it. the phone is on stock unrooted 4.4.2. I got it on the cheap and was hoping ot fix it up and use it. Any idea what might be wrong with it?
butthurtlocker said:
So i bought me a new used nexus 5 on craigslist from some old chinese guy. He said it wasn't connecting to a network no matter what or whose sim cards he used and how many times he rooted it. the phone is on stock unrooted 4.4.2. I got it on the cheap and was hoping ot fix it up and use it. Any idea what might be wrong with it?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2601997
Sounds like the old Chinese guy knew what he was doing.
You don't mention that YOU returned it to stock, you just said it was stock and unrooted. If it is exactly the way he gave it to you I would fastboot flash the stock 4.4.2 images from google and see what that does for you. You could simply have a corrupted file somewhere.
thionylx said:
You don't mention that YOU returned it to stock, you just said it was stock and unrooted. If it is exactly the way he gave it to you I would fastboot flash the stock 4.4.2 images from google and see what that does for you. You could simply have a corrupted file somewhere.
Click to expand...
Click to collapse
Yes when he sold it to me it was stock. I haven't returned it to stock, ive rooted it and tried diff rom/basebad combos and still nothing. Theres also a weird persistent notification that i cant swipe away that says Nework (ROGERS) Unvailable....even when i reset and try a Telus sim! Is there an easier way to flash stock besides fastboot? I am pretty new to this gig and am not too comfortable with fastboot
butthurtlocker said:
Yes when he sold it to me it was stock. I haven't returned it to stock, ive rooted it and tried diff rom/basebad combos and still nothing. Theres also a weird persistent notification that i cant swipe away that says Nework (ROGERS) Unvailable....even when i reset and try a Telus sim! Is there an easier way to flash stock besides fastboot? I am pretty new to this gig and am not too comfortable with fastboot
Click to expand...
Click to collapse
This being a Nexus you have little or no risk of doing damage by playing around. My original Droid X was always threatening to self destruct if you messed up the tiniest little step. Spending a couple hours learning about and installing Fastboot and ADB will be the best investment you can make. Once you learn to use them the fear of messing something up is gone. You can flash roms at will without worry as you can always return to stock and start over.
Flash a Google stock image
Sent from my Nexus 5 using Tapatalk
---------- Post added at 08:15 PM ---------- Previous post was at 08:14 PM ----------
All nexus 5 regardless of carrier should be unlocked
Sent from my Nexus 5 using Tapatalk
butthurtlocker said:
Yes when he sold it to me it was stock. I haven't returned it to stock, ive rooted it and tried diff rom/basebad combos and still nothing. Theres also a weird persistent notification that i cant swipe away that says Nework (ROGERS) Unvailable....even when i reset and try a Telus sim! Is there an easier way to flash stock besides fastboot? I am pretty new to this gig and am not too comfortable with fastboot
Click to expand...
Click to collapse
Just follow method one of this. It's easy http://forum.xda-developers.com/showthread.php?p=47156064
PS, why did you buy a device thinking you could fix it of you don't know fastboot commands
thionylx said:
This being a Nexus you have little or no risk of doing damage by playing around. My original Droid X was always threatening to self destruct if you messed up the tiniest little step. Spending a couple hours learning about and installing Fastboot and ADB will be the best investment you can make. Once you learn to use them the fear of messing something up is gone. You can flash roms at will without worry as you can always return to stock and start over.
Click to expand...
Click to collapse
Thanks man thats a good point!
jd1639 said:
Just follow method one of this. It's easy http://forum.xda-developers.com/showthread.php?p=47156064
PS, why did you buy a device thinking you could fix it of you don't know fastboot commands
Click to expand...
Click to collapse
Oh thats perfect bro thanks, nice and straightforward. Will see how this goes after school. I just htought it was maybe a radio issue or rom issue so i thought i could flash around and fix it. Also it was only 70 bucks and in mint condition aside from this problem so I didn't think it was a bad deal
Sounds like the ESN/IMEI is bad.
Hard to fix ATM.
Sent from my Nexus 5 using Tapatalk
Dragn4rce said:
Sounds like the ESN/IMEI is bad.
Hard to fix ATM.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Oh really?how does that happen!? The imei isn't blacklisted or anything and shows up as a registered imei. I tried flashing stock image and still no dice! Looks like I'm doomed. Any other suggestions?
That usually happens when the following steps occur.
The original owner unlocked bootloader.
They put twrp on it and did a full backup including ESN
The device developed a fault so they RMA'd it.
They restored the backup from the faulty device into the new one.
The ESN is device specific and by restoring it onto a different device you end up with not being able to connect to a network.
You can check by going into the about phone menu in the settings. If it displays your imei then I don't think this is your problem.
Have you tried popping the back cover off and checking the antennae contacts
Sent from my Nexus 4 using xda app-developers app
The good news is the parts are worth more than the $70 you paid for it. Find someone with a busted screen and sell it.
jd1639 said:
The good news is the parts are worth more than the $70 you paid for it. Find someone with a busted screen and sell it.
Click to expand...
Click to collapse
That's a good idea.
Thanks for the advice. Ended up selling it this morning as is to an eager repair junkie. Btw my imei was showing up and the antennas were all in place so still a mystery what was up with it!
Sent from my LG-G2 using xda app-developers app