Related
Before you post, "BLAKDSKF READ OTHER FORUMS BLUSDFLU!!!!!!!111!!!", please, PLEASE, read the whole post. I am not illiterate or a fool. I've spent the last few days researching similar posts, both on xda and other sites, and as far as I've found, this is the only post of this kind on the Verizon SGSIII forums, though there are some that are somewhat similar in the other SGSIII forums (though I think the root of the problem is different). If you can prove me wrong, please redirect.
The Long Story:
ok. SO. I was trying to root my SGSIII, unlock the bootloader, and install CM10. Simple enough, right? Not so. I got through the rooting tutorial at Link 1 relatively smoothly. For the record, I did the composite root and bootloader combo, and I installed CWM Touch Recovery, as per the guide. I also restored the Jellybean Bootchain. I think it was at this point I downloaded Titanium Backup (because forethought is not my forte) and backed up all my apps. I also made a backup with CWM Recovery, but there were errors. I forget the reason, but it aborted backup. I then tried to make a backup onto my external sd card, and some other errors popped up. Mainly that it couldn't find /android.secure (something along those lines) or /sd-ext (might have been something else. I'm going off memory) and skipped them. It still made the backup, so my illiterate, foolish self decided to roll with it and go ahead.
I then went ahead to Link 2, and with it being 2 AM, I stupidly decided to screw trying to figure out how to use Heimdall 1.4rc1 and continue to use ODIN for flashing. After all what's the difference, I thought. One flashing program is the same as another. I flashed the first two files. Well, in truth, I'm not sure if I flashed the first file. Since I just made a single folder for all the SGSIII Verizon flashing stuff, I had two files with similar names at the time. One from Link 1 and one from Link 2. The only difference was one was a boot chain, the other was a boot loader. Also, one ended with .md5 while the other ended with .tar. Sadly I tiredly picked one and flashed it. I think it was the .md5 one, but I'm not sure. Around this point, my micro sd card reader broke, so I decided to just use my other phone (Motorola Photon 4g running Joker's CM9) as a reader of sorts. I swapped them, used my phone to put the zip from Link 2 on it, and swapped them back. I say this because I'm not sure if that is what broke my md5sums or not (more on that in a sec).
Well, surprise, surprise, my phone got stuck on the animated, colorful "4G LTE" boot screen, except it was fully black, though the noise was playing. I think to myself, "No biggie. I'll just restore my previous backup," so I go back to restore it when I get the error 'md5sum mismatch'. I look up the problem, and after extensive, 3AM research (read: clicked the first link on google and blindly followed), I went with one guys advice, which was to create a blank nandroid.md5 file to force the restore. I figured, "Hey. This is pretty risky. I think I'll just restore the bootloader instead of the whole restore." Or at least that's what was going through my head as I went through with restoring the whole backup. Lo and behold, /system was corrupted, I assume, and it aborted restoring it. I reboot my phone only to find out that my phone gets stuck on the SGSIII boot logo. This is where I am now. I would go through with flashing a stock rom onto it to undo everything I've done, but ODIN won't recognize my phone anymore. I can still get into Download and Recovery Mode. All my backups are useless at the moment.
In Short:
I tried to root, unlock the bootloader, and flash CM10 on it
I messed up and ended up restoring a broken backup, md5sums be screwed.
Now ODIN won't recognize my phone and it's stuck at the SGSIII boot screen.
Is there any way to fix this or at least return it back to stock so I can start again?
If there's any other information you need, just ask. I'd be happy to give it. :laugh: This is my first post on these forums, so I'm not sure what information is standard. If you have any idea of what it might be, please drop a comment or something rather than just leaving. I'd like to know that people are actually reading this post.
And on an unrelated note, every time I try to flash with Heimdall, I get an error about there not being a certain .dll file, even though I downloaded the package from Link 2. Am I doing something wrong?
EDIT: I've already tried factory resetting and wiping the cache/dalvik cache. Most of my info is backed up anyway.
Links:
Link 1: http://forum.xda-developers.com/showthread.php?t=2046439
Link 2: http://wiki.cyanogenmod.org/w/Install_CM_for_d2vzw
What happens when you plug your phone into your PC? Have you tried deleting the drivers then reinstalling them either from Samsung or from the Kies program? You really have to try to mess up this phone and it seems like you definitely tried very hard in this regard.
Edit: Idk anything about Heimdall, I use Odin only so I can't help you there.
SlimSnoopOS said:
What happens when you plug your phone into your PC? Have you tried deleting the drivers then reinstalling them either from Samsung or from the Kies program? You really have to try to mess up this phone and it seems like you definitely tried very hard in this regard.
Edit: Idk anything about Heimdall, I use Odin only so I can't help you there.
Click to expand...
Click to collapse
I hadn't noticed before, but my phone doesn't even show a charge screen when plugged in, but that might just be the settings on the phone pre-root. I'm not sure because I left the phone on to see if it was just a time thing. The phone died and I have to recharge it.
After goofing around with the phone while on the charger for a while, I can get a charge screen to show up for a second. The standard "battery with a loading circle" type symbol for this type of error.
I just reinstalled the drivers. I'll let the phone charge for about 10 minutes or so, then test the phone.
dudeman9199 said:
I hadn't noticed before, but my phone doesn't even show a charge screen when plugged in, but that might just be the settings on the phone pre-root. I'm not sure because I left the phone on to see if it was just a time thing. The phone died and I have to recharge it.
After goofing around with the phone while on the charger for a while, I can get a charge screen to show up for a second. The standard "battery with a loading circle" type symbol for this type of error.
I just reinstalled the drivers. I'll let the phone charge for about 10 minutes or so, then test the phone.
Click to expand...
Click to collapse
Well if it died you should leave it on the charger longer than ten minutes if it is charging. If Odin recognizes it, your first step would be to try flashing a stock image.
SlimSnoopOS said:
Well if it died you should leave it on the charger longer than ten minutes if it is charging. If Odin recognizes it, your first step would be to try flashing a stock image.
Click to expand...
Click to collapse
Thanks. It would seem that it now recognizes the phone, from what I can tell. As soon as I get a stock rom, I'll flash it and post an update.
dudeman9199 said:
Thanks. It would seem that it now recognizes the phone, from what I can tell. As soon as I get a stock rom, I'll flash it and post an update.
Click to expand...
Click to collapse
Great! Use Droidstyle's guide or MrRobinson's thread for the proper images. Should be a good starting point.
Sent from my SCH-I535 using xda app-developers app
I just wanted to add that THIS is how you do a first post or any help needed post! Great details and is obvious you researchedyour problem as well.
The errors in cwm are actually normal. I think the corrupt backups are unrelated.
Sent from my SCH-I605 (AKA NOTE 2)
SlimSnoopOS said:
Great! Use Droidstyle's guide or MrRobinson's thread for the proper images. Should be a good starting point.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Thanks. I've finally booted up into the setup wizard. I guess from here on I can re-root, unlock the bootloader, and *hopefully* get a working backup and eventually flash CM10.
I guess this means Problem Solved? Again, Thanks.
kintwofan said:
I just wanted to add that THIS is how you do a first post or any help needed post! Great details and is obvious you researchedyour problem as well.
The errors in cwm are actually normal. I think the corrupt backups are unrelated.
Sent from my SCH-I605 (AKA NOTE 2)
Click to expand...
Click to collapse
Thanks. I'm just gonna assume that the problems stemmed from swapping the sd card and leave it at that.
dudeman9199 said:
Thanks. I've finally booted up into the setup wizard. I guess from here on I can re-root, unlock the bootloader, and *hopefully* get a working backup and eventually flash CM10.
I guess this means Problem Solved? Again, Thanks.
Thanks. I'm just gonna assume that the problems stemmed from swapping the sd card and leave it at that.
Click to expand...
Click to collapse
Perfect! Which thread did you end up using btw?
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
Perfect! Which thread did you end up using btw?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I used droidstyle's thread for getting the stock rom.
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
I thought I would change the title of my thread as the issue seems to have changed. I hope that isn't a problem. I am able to get into loader mode just fine and have loaded CWM twice through ODIN but am unable to get the internal SD Card to mount or USB mode to work. HAs anyone seen this before? I searched carefully and could not find any reference to my problem. I was careful to uncheck re-partition but there is a chance I may have not, I suppose. Would that cause my problem? Any input would be most appreciated....I'm stuck.
Well, the good news is as long as you have Odin mode nothing is broken that cant be fixed the bad news is, I've been following your progress, and I'm stumped and out of ideas :-/ the way I understand it, you have a working Clockwork Mod recovery, you can boot to recovery. Correct? When you try to mount USB mode in Mounts and Storage, it gives you an error? Do you have an external microSD that you could copy a ROM over to and try to flash from there?
Which version of CMW did you flash,I found issues with ver 6.XXX and went back to ver 5.XXX non touch. In the newer versions including touch USB and mounting the drives didn't work for me. I thought it was my phone because of everything I've done since rooting
Sent from my GT-N7100 using xda app-developers app
flyers00 said:
Which version of CMW did you flash,I found issues with ver 6.XXX and went back to ver 5.XXX non touch. In the newer versions including touch USB and mounting the drives didn't work for me. I thought it was my phone because of everything I've done since rooting
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
i believe (based on the other thread he was in) that he's using the 5.xxx version from k0nane's thread (which is what I'm using)
jparnell8839 said:
i believe (based on the other thread he was in) that he's using the 5.xxx version from k0nane's thread (which is what I'm using)
Click to expand...
Click to collapse
I wasn't sure either that's why I threw it out there. I'm using the same version from k0oane 5.XXX as well
Sent from my GT-N7100 using xda app-developers app
Interesting Thought
jparnell8839 said:
Well, the good news is as long as you have Odin mode nothing is broken that cant be fixed the bad news is, I've been following your progress, and I'm stumped and out of ideas :-/ the way I understand it, you have a working Clockwork Mod recovery, you can boot to recovery. Correct? When you try to mount USB mode in Mounts and Storage, it gives you an error? Do you have an external microSD that you could copy a ROM over to and try to flash from there?
Click to expand...
Click to collapse
Sounds interesting, but wouldn't this explode needing to access the internal SD? i don't know if my PC has a SD Slot, but that is easy enough to fix. I'll try the solution below then this one.. One step at a time. Glad I've got a stumper even if it is a pain in my @ss.
Thanks again to all for the thoughts.
Mike in Houston
CWM 5.0.0.4
flyers00 said:
Which version of CMW did you flash,I found issues with ver 6.XXX and went back to ver 5.XXX non touch. In the newer versions including touch USB and mounting the drives didn't work for me. I thought it was my phone because of everything I've done since rooting
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
I'm using CWM 5.5.0.4 Still stumped. IF I did something stupid I sure wish I knew what it is. Phone is one week old and of course store claims it is my fault..........rrrrgh. I bought a Galaxy Express to hold me over until I get this fixed. The store offered me a job if I could fix it and as I'm not working, I'm calling in all the troops to help me here if possible........Thanks a million. or a thousand. They don't pay much.I Just checked and the sd card ext will not mount either in CWM and gives errors. I'd like to mod the express I bought to replace this one but am a bit gun shy now. It seems this problem is buried pretty deep.
Stil grateful but in need of help..
Ready to send it off to a JTAG repair shop but as I can still boot into both download and recovery modes there must be something I can do myself to fix this. Anybody out there??????
mikesmccurdy said:
Ready to send it off to a JTAG repair shop but as I can still boot into both download and recovery modes there must be something I can do myself to fix this. Anybody out there??????
Click to expand...
Click to collapse
All you've gotta do is Odin the ORIGINAL GB or ICS from Sammobile. Your soft bricked (no biggie). Your more than likely missing a few important files that GB or ICS could fix. I'd go with GB, IMO
Close but no cigar.
jbats said:
All you've gotta do is Odin the ORIGINAL GB or ICS from Sammobile. Your soft bricked (no biggie). Your more than likely missing a few important files that GB or ICS could fix. I'd go with GB, IMO
Click to expand...
Click to collapse
I went to Sammobile and downloaded the firmware but it comes in Zip format and Odin does not recognize that rrgh. I can't get it onto a sd card because it won't mount in CWM. Thanks for the suggestion. I'll hold off for another response before I ship it out. Seems like I should be able to find something to flash on here somewhere, but i'm stumped.......
You need to unzip the file and extract the files there's a tar file inside. Use the instructions in konanes thread with the file you have. I can walk you through it better tommorow when I get off work, its very easy.
jbats said:
You need to unzip the file and extract the files there's a tar file inside. Use the instructions in konanes thread with the file you have. I can walk you through it better tommorow when I get off work, its very easy.
Click to expand...
Click to collapse
I can't imagine someone would be so kind as to take their time to walk a stranger through a process. (Even if I would). I'm having a hard time finding konanes thread on this subject and would appreciate any direction to it so I won't be such a bother. Sorry for the delay in response, but I've been on a short vacation. Thanks to all.
mikesmccurdy said:
I can't imagine someone would be so kind as to take their time to walk a stranger through a process. (Even if I would). I'm having a hard time finding konanes thread on this subject and would appreciate any direction to it so I won't be such a bother. Sorry for the delay in response, but I've been on a short vacation. Thanks to all.
Click to expand...
Click to collapse
Here is the thread http://forum.xda-developers.com/showthread.php?t=1591601 now just grab the GB zip from sammobile and extract the tar and follow the instructions in the thread.:good:
Progress but no prize......
jbats said:
Here is the thread http://forum.xda-developers.com/showthread.php?t=1591601 now just grab the GB zip from sammobile and extract the tar and follow the instructions in the thread.:good:
Click to expand...
Click to collapse
Well I found it before you replied and low and behold I am able to boot my phone. Now it won't recognize the sim card. I made sure the SIM works in another phone. BTW this is a T-Mobile phone originally but I run on simple mobile. I tried the unlocking process but I did not pay for an unlock code because it won't boot to the unlock code screen. It just goes all the way through and then reports "no sim card Emergency calls only" Thanks for getting me this far. The phone worked fine before I started playing with it. Now I'm really stumped...rrgh.
Thanks
Mike in Houston with dead Blaze. And the store was going to offer me a job if I got it working....
Moving backwards
mikesmccurdy said:
Well I found it before you replied and low and behold I am able to boot my phone. Now it won't recognize the sim card. I made sure the SIM works in another phone. BTW this is a T-Mobile phone originally but I run on simple mobile. I tried the unlocking process but I did not pay for an unlock code because it won't boot to the unlock code screen. It just goes all the way through and then reports "no sim card Emergency calls only" Thanks for getting me this far. The phone worked fine before I started playing with it. Now I'm really stumped...rrgh.
Thanks
Mike in Houston with dead Blaze. And the store was going to offer me a job if I got it working....
Click to expand...
Click to collapse
Also of note only flashing T769UMB1 from Sammobile will allow the phone to boot at all. Whet I try to flash the root kernel the phone locks up as always at the blue bar when it completes and when reflashing T769UMB1 I go into CWM and am still unable to mount the SD Cards or USB Storage. Appears my little bit of progress was in vain. When it does boot as mentioned above, I still have "no sim card" Any advice would be appreciated. Being a NOOB, I am unsure if I started out with GB or ICS in the first place it that offers any assistance.
Any advice is greatly appreciated.
You need to buy an unlock code, than you can enter it through your dialer.
---------- Post added at 11:02 PM ---------- Previous post was at 10:59 PM ----------
You skipped the next step. You can't flash from GB to the latest. You have to do it in steps first GB than ICS uvlh5 than uvlmb1, uvlh5 was a prerequisette to the latest mb1. Start over...
Still grateful and lost.....
jbats said:
You need to buy an unlock code, than you can enter it through your dialer.
---------- Post added at 11:02 PM ---------- Previous post was at 10:59 PM ----------
You skipped the next step. You can't flash from GB to the latest. You have to do it in steps first GB than ICS uvlh5 than uvlmb1, uvlh5 was a prerequisette to the latest mb1. Start over...
Click to expand...
Click to collapse
I have done as you suggested and really appreciate all the time you have taken to help me out. When I loaded UVLH5 the phone said it was updating 62 apps as it booted and I was in the same predicament. The phone boots and recognizes the internal memory card but will not recoginze my SIM card. I thought it was supposed to ask for an unlock code when it saw the foreign sim as I have seen that on other sites. The phone just boots and says "No SIM card" whether or not one is installed. Would sending it off for a JTAG repair solve my problem? I think I may have screwed the pooch so to speak when I loaded uvimb1. I am determined to fix this phone. It shouldn't be so difficult, famous last words. I think there may be a way to force the dialer to allow me to enter an unlock code, but before I spend more money on the phone I want to make sure that is what I need to do. I also cannot seem to get back into CWM for some reason. Maybe the button sequence has changed with the update. Confirming that procedure would be quite helpful.
mikesmccurdy said:
I went to Sammobile and downloaded the firmware but it comes in Zip format and Odin does not recognize that rrgh. I can't get it onto a sd card because it won't mount in CWM. Thanks for the suggestion. I'll hold off for another response before I ship it out. Seems like I should be able to find something to flash on here somewhere, but i'm stumped.......
Click to expand...
Click to collapse
You need an account with samfirmware and you should be downloading a .tar.md5 file. Shouldn't be a zip. Just curious, what's inside the zip?
I've got a serious problem. I stupidly decided to update my S3 to 4.3. I then tried to root with old Casual method, no harm to the phone but not rooted.. Used saferoot, still no harm. I got root successfully, and updated the SU binary and disabled Samsung KNOX. Then I tried to use the "flash insecure aboot" option from Casual, and after restart now I've got a full brick. Can't boot system, recovery, or download. In fact, when I plug it in the charging animation doesn't even pop up. What should I do?
EDIT: Well I think I ought to explain what happened a bit more. Skip this section if you want, likely TL;DR.
I admit I did a lot of incredibly stupid things to my phone. First I updated directly on the phone, through Settings>About phone>Software update. Everything worked fine, and I was happy with 4.3. (I did factory resets before and after the update)
Then I rebooted and discovered many things including a new boot animation and sound which I was displeased with. Also,even though the new icons are nice, most of what I noticed was eye candy. I tried to root using casual. After a reboot, the phone still worked, but Root Checker said that root wasn't setup properly. Next I tried using saferoot, which is a method designed for 4.3, but not the Verizon S3. That worked and rooted successfully.
Then I opened the SuperSU app. It asked me to update the SU binary and disable Samsung KNOX (which I had no prior knowledge of)
It still worked fine after that. Then I tried "Flash insecure aboot" in Casual. And that's when everything stopped working.
EDIT 12/19/2013: I fixed it permanently! All credit goes to SpyroDazee for his wonderful guide here: http://forum.xda-developers.com/showthread.php?t=2581166
I restored stock bootloader, and can now boot without an SD card!
Well I've done a lot of searching, and it doesn't look like there is too much I can do. I've found some repair services that claim to fix it, but I really don't know at this point. I've also heard that you could get a debrick image and write it to a 16GB class 10 microSD card which may fix it. Any thoughts?
Think your hard bricked
Sent from my SCH-I535 using Tapatalk
ultpokemonfan said:
Well I've done a lot of searching, and it doesn't look like there is too much I can do. I've found some repair services that claim to fix it, but I really don't know at this point. I've also heard that you could get a debrick image and write it to a 16GB class 10 microSD card which may fix it. Any thoughts?
Click to expand...
Click to collapse
You are Hard Bricked. Follow this guide very carefully. It may just save your phone. Make sure you use a Class 10 SDcard that matches the size of your phone.
http://goo.gl/LJfOuZ
Sent from my SCH-I535 using Tapatalk
ultpokemonfan said:
And that's when everything stopped working.
Click to expand...
Click to collapse
Did that guide help?
Sent from my SCH-I535 using Tapatalk
Sandman-007 said:
Did that guide help?
Click to expand...
Click to collapse
I love when they come for help, but then never reply...
Sorry for the long delay. Sadly, I don't have a microSD card to test this on right now. However, I've ordered one and it should be coming soon. I'll post back once I've got it and tried following the guide.
Well I'm not having any luck so far. I got my class 10 16GB microSD card today. I tried following both the guide that Sandman-007 linked and a guide from this forum thread: http://forum.xda-developers.com/showthread.php?t=2581166
Nothing is working. I tried each guide a few times each, rewriting the debrick image each time I tried.
I read that u have to try multiple times trial and error but if still don't work then JTAG is ur solution.
Flashing an insecure aboot or ANY recovery will brick the phone with 4.3
Sent from my SCH-I535 using xda app-developers app
I got it to boot. I just had to charge it! Not fully fixed yet, but getting there!
ultpokemonfan said:
I got it to boot. I just had to charge it! Not fully fixed yet, but getting there!
Click to expand...
Click to collapse
Keeping it charged is Key .. What you need to bring it to life
Recently tried to unroot due to issues with the vibrate motor not working for any notifications or anything. Also, apps started to fail more frequently it was all just becoming a big headache. I had thought for sure I enabled OEM unlocking but at this point its obvious I did not. Currently I can not get phone to boot besides to the encryption page and no idea what pin code would be. I have tried everything imaginable under the sun. In adb I ran the oem unlock string which caused all these issues. If I try to boot into recovery I get the message "Your device is corrupt. It cant be trusted and will not boot". If I try to boot normally i get the message "Your device has loaded a different operating system" then boots to the encryption lock page. I have placed the RUU and other files and attempted the SD card way of running the files to no avail. Does anyone have any other advice to getting this thing back on?
Edit: this can be closed. I flashed nearly every file I could find but nothing would take. Doing it both the adb and SD card method. Finally, I found the zip that the phone finally liked and it finally flashed. OH man cant be any happier to finally have my baby back on. Anyone else become stuck in this issue, just do as others have said, find the correct zip, flash it, and all will be ok.
mbaseball3 said:
Recently tried to unroot due to issues with the vibrate motor not working for any notifications or anything. Also, apps started to fail more frequently it was all just becoming a big headache. I had thought for sure I enabled OEM unlocking but at this point its obvious I did not. Currently I can not get phone to boot besides to the encryption page and no idea what pin code would be. I have tried everything imaginable under the sun. In adb I ran the oem unlock string which caused all these issues. If I try to boot into recovery I get the message "Your device is corrupt. It cant be trusted and will not boot". If I try to boot normally i get the message "Your device has loaded a different operating system" then boots to the encryption lock page. I have placed the RUU and other files and attempted the SD card way of running the files to no avail. Does anyone have any other advice to getting this thing back on?
Edit: this can be closed. I flashed nearly every file I could find but nothing would take. Doing it both the adb and SD card method. Finally, I found the zip that the phone finally liked and it finally flashed. OH man cant be any happier to finally have my baby back on. Anyone else become stuck in this issue, just do as others have said, find the correct zip, flash it, and all will be ok.
Click to expand...
Click to collapse
I'm in this predicament at the moment. I am not able to find the zip file with the same OS as my phone (2.42.617.6)
I am looking at this spreadsheet to locate the correct zip file. Could anyone help me, please? Thanks.
https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit#gid=0
mauiblue said:
I'm in this predicament at the moment. I am not able to find the zip file with the same OS as my phone (2.42.617.6)
I am looking at this spreadsheet to locate the correct zip file. Could anyone help me, please? Thanks.
https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit#gid=0
Click to expand...
Click to collapse
38 or 39 should work. The last octet doesn't matter as that is just sub version. So long as the first 3 octets match ie 2.42.617, your good to go.
shivadow said:
38 or 39 should work. The last octet doesn't matter as that is just sub version. So long as the first 3 octets match ie 2.42.617, your good to go.
Click to expand...
Click to collapse
Thanks shivadow for responding to my post. So I downloaded one of the one of the latest versions (from the zip variant link) and renamed it "firmware.zip" I am using ADB to do the process (https://forum.xda-developers.com/u11/how-to/collection-htcu-u11-ruu-firmware-t3612048) and I get this error:
C:\adb>fastboot flash zip firmware.zip
target reported max download size of 2399200000 bytes
error: cannot load 'firmware.zip'
I renamed it a couple other times and I still get that error above. My phone (U11) is in the download mode. Just for giggles when I type in on the command prompt "fastboot oem rebootRUU" I get to a screen that has HTC on it and says and the warning "Security Warning. If you flash this phone with any ROM that was not officially released by HTC you take the risk of releasing...." When I give the command to flash the zip file I get the same error as above.
I am hopeful that I can get this phone back to normal running status. I just need to get the right commands and files to do this.
I appreciate any and all help to get my phone back to normal again. Aloha.
Sorry just saw all the updates. Notifications turned off apparently. Since I was able to get phone back on I can say it's not like it used to. I've tried to run the RUU which fails every time. And my signal has turned to absolute crap; constant dropped signal and barely any LTE. So, I'm no help since all I've done is get the phone on but not working properly lol.
mauiblue said:
I'm in this predicament at the moment. I am not able to find the zip file with the same OS as my phone (2.42.617.6)
I am looking at this spreadsheet to locate the correct zip file. Could anyone help me, please? Thanks.
https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit#gid=0
Click to expand...
Click to collapse
Sent from my 2PZC5 using Tapatalk
mbaseball3 said:
Sorry just saw all the updates. Notifications turned off apparently. Since I was able to get phone back on I can say it's not like it used to. I've tried to run the RUU which fails every time. And my signal has turned to absolute crap; constant dropped signal and barely any LTE. So, I'm no help since all I've done is get the phone on but not working properly lol.
Sent from my 2PZC5 using Tapatalk
Click to expand...
Click to collapse
Aloha and thanks for taking the time to respond. Well you got farther than me as I was not able to get my phone out of trouble. Tomorrow will make two weeks since I sent my phone out to HTC. I just got the new HTC U12+ yesterday as I can't go without a reliable set because I need one for my jobs.
Next time if I do unlock the bootloader on any phone I will figure out how to do the process of rooting, updating, and not bricking the phone.
I hope you sort things out with your phone.
Sent from my HTC U12+ using Tapatalk
I'm not sure about getting further when it feels messed up still, ha. Yeah I get ya though, had the same experience freaking out that I wouldn't have a phone for work. Fortunately I had my cracked screen m10 that served as a backup until I was able to get the u11 to boot. I swear the last phones I rooted were less hassle than these more complex devices. Hope HTC can get it figured out for you.
mauiblue said:
Aloha and thanks for taking the time to respond. Well you got farther than me as I was not able to get my phone out of trouble. Tomorrow will make two weeks since I sent my phone out to HTC. I just got the new HTC U12+ yesterday as I can't go without a reliable set because I need one for my jobs.
Next time if I do unlock the bootloader on any phone I will figure out how to do the process of rooting, updating, and not bricking the phone.
I hope you sort things out with your phone.
Sent from my HTC U12+ using Tapatalk
Click to expand...
Click to collapse
Sent from my 2PZC5 using Tapatalk
I agree that the past phones were not so hard to unlock, root, update, and tweak. Now with the U12+ dual A/B slot partition and multiple files that are needed to root the phone it can be overwhelming.
I'm sure HTC will be able fix the phone but at what cost? I'm just waiting it out and hoping for the best.
Aloha!
Sent from my HTC U12+ using Tapatalk