Related
I successfully rooted my G2x and attempted to flash the hellfire sandwich rom. I believe I did everything correctly, but I have wound up in a situation identical to what is described here:
http://forum.xda-developers.com/showthread.php?t=1059155
I have attempted the suggested recovery steps, but my computer does not detect the g2x when holding the volume buttons and then connecting.
Any help would be greatly appreciated I am more than willing to donate to anyone able to help me out of this mess.
How did you install your recovery? Did you use nvflasher to root and install cwm? Or did you install rom manager and click the flash recovery button?
Sent from my LG-P999 using Tapatalk
This phone is almost impossible to mess up...
Sent from my LG-P999 using XDA
lawdawg45238 said:
How did you install your recovery? Did you use nvflasher to root and install cwm? Or did you install rom manager and click the flash recovery button?
Sent from my LG-P999 using Tapatalk
Click to expand...
Click to collapse
The latter.
theking_13 said:
This phone is almost impossible to mess up...
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
I hope that means this will be easy to fix
It's official, I'm a noob
I didnt see the computer detect it and try to install drivers like in the videos, but when I looked for it under device manager, it was there.
Mods can delete this thread
Another crisis averted by following the directions! Glad to hear you fixed it.
Gilligan87 said:
It's official, I'm a noob
I didnt see the computer detect it and try to install drivers like in the videos, but when I looked for it under device manager, it was there.
Mods can delete this thread
Click to expand...
Click to collapse
Told you it was impossible to brick it.
theking_13 said:
Told you it was impossible to brick it.
Click to expand...
Click to collapse
You were right! Than ****ing god. I JUST bought it last night, too; I almost didn't sleep at all...my girlfriend kept saying "Go to sleep, you'll figure it out in the morning!" Should have just listened, and instead I was up another 2 hours just plugging my phone in and out, rebooting it, and scouring the forums desperately...
jcbofkc said:
Another crisis averted by following the directions! Glad to hear you fixed it.
Click to expand...
Click to collapse
Heheh...actually I didn't follow the directions! The ones that I was watching showed an error message popping up, and to then look in the device manager; I got an error message once but thought it was wrong and then kept trying to replicate it, but no error message showed. I just hadn't thought to just look in the device manager, and when I did, there it was! ^_^
theking_13 said:
Told you it was impossible to brick it.
Click to expand...
Click to collapse
Not impossible, just improbable, if you attach the phone with something which operates at a file-system level you can brick it. Granted with NV flash, we can NV flash CWM back on and we know we can flash a baseband, so there's not much else which we could access that we could permanately screw-up which can't be unscrewed in some fashion.
hope you have the july baseband before rooting, or else you made an extra step for yourself
I HAVE BEEN TRYING TO ROOT MY GALAXY S 4G FOR 4 DAYS NOW AND HAVE BEEN UNSUCCESSFUL IF ANYONE HAS A STEP BY STEP ON HOW TO DO THIS I WOULD LOVE TO KNOW HOW?
I HAVE DOWNLOADED SO MANY DIF. PROGRAMS AND HAVE TRIED YOUTUBE VIDEOS AND EVEN OLD LINKS FROM XDA GOING AS FAR BACK AS 2010 AND I CANT ROOT MY PHONE PLEASE I ASK FOR SOME HELP ???????
IF THERE ARE NEW WAYS OF DOING THE ROOTING??? PLEASE POST THE LINKS AND EXPLANE HOW ITS DONE?????
I replied to your post in the other thread. Please take off the caps lock.
Galaxy_kit said:
I HAVE BEEN TRYING TO ROOT MY GALAXY S 4G FOR 4 DAYS NOW AND HAVE BEEN UNSUCCESSFUL IF ANYONE HAS A STEP BY STEP ON HOW TO DO THIS I WOULD LOVE TO KNOW HOW?
I HAVE DOWNLOADED SO MANY DIF. PROGRAMS AND HAVE TRIED YOUTUBE VIDEOS AND EVEN OLD LINKS FROM XDA GOING AS FAR BACK AS 2010 AND I CANT ROOT MY PHONE PLEASE I ASK FOR SOME HELP ???????
IF THERE ARE NEW WAYS OF DOING THE ROOTING??? PLEASE POST THE LINKS AND EXPLANE HOW ITS DONE?????
Click to expand...
Click to collapse
Superoneclick root
Sent from my SGH-T959V using xda app-developers app
+1 for super one-click, it's always worked for me
Sent from my SGH-T959V using XDA
Thought there was a search button... The wiki thread in the general forum will get you where you want to be...but please the caps button really isn't helping you out much
Sent from...that dark place in the back 40
Have you tried even searching for answers? If not you should, and do some research first. Doing some stupid stuff with your phone can have some consequences.
Follow these steps below (read first before doing it):
1. If you want to be on the safe side you can backup your files and put them in your computer. You can use an app in the market or you can do it yourself (Copy and pasting).
[OPTIONAL]2. You can factory data reset your phone to remove bad stuff when rooting. But its up to the user, I had paranoia since I bricked my first SGS4G.
3. We can now start the rooting process. You can go and download superoneclick: shortfuse[.org]/?page_id=2
4. When downloaded extract those files somewhere inside a folder.
(Just to let those people that have been living under the rock, SOC auto installs drivers)
5. If you have Windows 7 or Vista, you have to run it as an administrator.
6. Once SOC is up and running, DO NOT CHANGE ANY DAMN THING!
7. Go grab your phone, go into Settings > Application > Development > Check ON USB debugging. While in settings go unmount your SD card. This is a crucial step!
8. Go grab your USB wire, plug your phone and plug the other end of the wire to the computer, DO NOT TOUCH ANYTHING IN THE PHONE! Just leave it as it is.
9. If Windows gets a pop-up message in the bottom saying "Installing device..." let it finish.
10. It's time to root and time is not always predictable, close all programs in your computer so it doesn't take up processing. Click "Root" in SuperOneclick, it should start the rooting process, if for some reason it "Stops Responding" DON'T TOUCH A DAMN THING! Let it do it's work! If its not responding its probably sleeping or overwhelmed with Zerglings! That is normal!
11. When its finished go live happily ever after. It's a good idea to let the phone rest for 10 minutes since I assure you, the phone will lag.
Hmm now I'm too scared to root my phone :-/
Mybe ill pay someone to do it for me...that's the scariest write up I've ever seen.
Carl
Shortbus-Driver said:
Hmm now I'm too scared to root my phone :-/
Mybe ill pay someone to do it for me...that's the scariest write up I've ever seen.
Carl
Click to expand...
Click to collapse
Don't be scared, it's actually very easy to do!
LOL
Carl
th3controller said:
Have you tried even searching for answers? If not you should, and do some research first. Doing some stupid stuff with your phone can have some consequences.
Follow these steps below (read first before doing it):
1. If you want to be on the safe side you can backup your files and put them in your computer. You can use an app in the market or you can do it yourself (Copy and pasting).
[OPTIONAL]2. You can factory data reset your phone to remove bad stuff when rooting. But its up to the user, I had paranoia since I bricked my first SGS4G.
3. We can now start the rooting process. You can go and download superoneclick: shortfuse[.org]/?page_id=2
4. When downloaded extract those files somewhere inside a folder.
(Just to let those people that have been living under the rock, SOC auto installs drivers)
5. If you have Windows 7 or Vista, you have to run it as an administrator.
6. Once SOC is up and running, DO NOT CHANGE ANY DAMN THING!
7. Go grab your phone, go into Settings > Application > Development > Check ON USB debugging. While in settings go unmount your SD card. This is a crucial step!
8. Go grab your USB wire, plug your phone and plug the other end of the wire to the computer, DO NOT TOUCH ANYTHING IN THE PHONE! Just leave it as it is.
9. If Windows gets a pop-up message in the bottom saying "Installing device..." let it finish.
10. It's time to root and time is not always predictable, close all programs in your computer so it doesn't take up processing. Click "Root" in SuperOneclick, it should start the rooting process, if for some reason it "Stops Responding" DON'T TOUCH A DAMN THING! Let it do it's work! If its not responding its probably sleeping or overwhelmed with Zerglings! That is normal!
11. When its finished go live happily ever after. It's a good idea to let the phone rest for 10 minutes since I assure you, the phone will lag.
Click to expand...
Click to collapse
You got a thanks. As in for the laugh. The worst guide I have ever seen.
hechoen said:
You got a thanks. As in for the laugh. The worst guide I have ever seen.
Click to expand...
Click to collapse
LOL! It's understandable in my end so its easy enough to root for the SGS4G.
Maybe I'm wrong... been s long time since I rooted... can't you just run 1 click gremlin? Way easier
Sent from my SGH-T959V using xda premium
NewKlNGjames said:
Maybe I'm wrong... been s long time since I rooted... can't you just run 1 click gremlin? Way easier
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
Im sure it would work. However people need to be comfortable with doing it. Handing them a fish sandwich when they ask how to fish is counter-productive.
eollie said:
Im sure it would work. However people need to be comfortable with doing it. Handing them a fish sandwich when they ask how to fish is counter-productive.
Click to expand...
Click to collapse
I agree! That's how come I was so confused and stupid when I first found this site. I followed a video tut for rooting, and they just showed you everything to click with d/l links and all. They never bothered to explain ANYTHING. I was lost as hell.
OP, you look to be in the same boat so if you would like to know what all I did after I rooted and how I got to start learning, search for a thread called "Followed a video tut for rooting"
Just rooted my new SGS3 using New Root Method Released for Verizon’s Galaxy S3, No Odin Required. i did the data & kelvic wipe then install Clean Rom 5.0. All progressed without a hitch. Even backed up with CWM prior to flash.
I rebooted into the new rom and got this: System software not authorized by Verizon Wireless... rebooted several time with same result.
What can I do now? Thanks for your help.
Just a wild guess, but me thinks your bootloader is still locked! But I'm not sure that will even apply because I rooted my device before unlocking the bootloader. But I rooted my device via ODIN first.
You can try EZ-Unlock via the Market. The GUI is still very buggy and will show the status as unknown but the internal workings of the app works good.
You got nothin to loose in trying. Go back to stock and give it another whirl after you've unlocked the bootloader.
Of that fails then I would suggest using the tried and true method..ODIN.
G'luck!
yup your bootloader is still locked
check the downloads thread and use version 1.2.
That means your boatloader is locked. You now must Odin back to stock and start over. Droid style has a guide stickied in the development thread. Follow section 6 of it.
Next time use ez unlock version 1.2 to unlock you boatloader.
Sent from my SGS3 running Eclipse 2.1
downloads list
http://forum.xda-developers.com/showthread.php?t=1850506
tekrhino said:
Just a wild guess, but me thinks your bootloader is still locked! But I'm not sure that will even apply because I rooted my device before unlocking the bootloader. But I rooted my device via ODIN first.
You can try EZ-Unlock via the Market. The GUI is still very buggy and will show the status as unknown but the internal workings of the app works good.
You got nothin to loose in trying. Go back to stock and give it another whirl after you've unlocked the bootloader.
Of that fails then I would suggest using the tried and true method..ODIN.
G'luck!
Click to expand...
Click to collapse
Thanks. I can't get past the warning dialogue screen. Pulled the battery, no good. PC can't see the phone with USB.
Prophotog said:
Thanks. I can't get past the warning dialogue screen. Pulled the battery, no good. PC can't see the phone with USB.
Click to expand...
Click to collapse
Yikes, ok
You have to get into DOWNLOAD MODE.. Power+ Volume Down+ Home key at the same time after a fresh battery pull.
Do a search on the Development forum to set up Odin on your PC.
YOU Must FOLLOW directions EXACTLY our you will have very expensive BRICK!
This forum could help:
http://forum.xda-developers.com/showthread.php?t=1762709
Or even better, this one:
http://forum.xda-developers.com/showthread.php?t=1840030
tekrhino said:
Yikes, ok
You have to get into DOWNLOAD MODE.. Power+ Volume Down+ Home key at the same time after a fresh battery pull.
Do a search on the Development forum to set up Odin on your PC.
YOU Must FOLLOW directions EXACTLY our you will have very expensive BRICK!
This forum could help:
http://forum.xda-developers.com/showthread.php?t=1762709
Or even better, this one:
http://forum.xda-developers.com/showthread.php?t=1840030
Click to expand...
Click to collapse
Thanks to everyone!! Looks to be a long night. :>)
tekrhino said:
Yikes, ok
You have to get into DOWNLOAD MODE.. Power+ Volume Down+ Home key at the same time after a fresh battery pull.
Do a search on the Development forum to set up Odin on your PC.
YOU Must FOLLOW directions EXACTLY our you will have very expensive BRICK!
This forum could help:
http://forum.xda-developers.com/showthread.php?t=1762709
Or even better, this one:
http://forum.xda-developers.com/showthread.php?t=1840030
Click to expand...
Click to collapse
I lol'ed at your post. A little dramatic, don't you think? He's not even close to bricked. Just Odin from download mode back to stock, and redo the steps with bootloader unlock.
Here is a gift (working ez-unlock v1.2)
http://dl.dropbox.com/u/42057363/com.mmmeff.ez.unlock_3.apk
@Techsavvy
Yeah, perhaps a tad overdone on the theatricals.
Cut me some slack, I'm taking acting classes..lol
And... I know... I know..don't quit my day job!
Still having issues. I "think" I am in the download mode. Screen says Downloading.... It has Odin in red in top left corner. Device connects with Odin. BUT I am not getting a PASS message when flashing VRALEC bootchain. Last text line in Odin is: <OSM> Leave CS...
I have tried several attempts.
Suggestions?
Prophotog said:
Still having issues. I "think" I am in the download mode. Screen says Downloading.... It has Odin in red in top left corner. Device connects with Odin. BUT I am not getting a PASS message when flashing VRALEC bootchain. Last text line in Odin is: <OSM> Leave CS...
I have tried several attempts.
Suggestions?
Click to expand...
Click to collapse
No need to do the boot chains. Just follow section 5 of this guide and I recommend root 66 for the ROM you flash
http://forum.xda-developers.com/showthread.php?p=28530394
Sent from my SGS3 running Eclipse 2.1
tekrhino said:
@Techsavvy
Yeah, perhaps a tad overdone on the theatricals.
Cut me some slack, I'm taking acting classes..lol
And... I know... I know..don't quit my day job!
Click to expand...
Click to collapse
I appreciate the theatricals...however, I am having issues with Odin. Can't get the Pass message. I assume the "Downloading..." text means I'm in the download mode. Tried several attempts. I AM glad I'm not close to bricked too! Can't afford $600 or a divorce. Might have to sell a camera instead.
Prophotog said:
Just rooted my new SGS3 using New Root Method Released for Verizon’s Galaxy S3, No Odin Required. i did the data & kelvic wipe then install Clean Rom 5.0. All progressed without a hitch. Even backed up with CWM prior to flash.
I rebooted into the new rom and got this: System software not authorized by Verizon Wireless... rebooted several time with same result.
What can I do now? Thanks for your help.
Click to expand...
Click to collapse
And just for future reference, it's Dalvik, not Kelvic
Sent from my SCH-I535 using xda app-developers app
Prophotog said:
I appreciate the theatricals...however, I am having issues with Odin. Can't get the Pass message. I assume the "Downloading..." text means I'm in the download mode. Tried several attempts. I AM glad I'm not close to bricked too! Can't afford $600 or a divorce. Might have to sell a camera instead.
Click to expand...
Click to collapse
Just a heads up. You can get a real brick with Odin and easy. Follow the guide I linked earlier to a t and you'll be fine
Sent from my SGS3 running Eclipse 2.1
kintwofan said:
Just a heads up. You can get a real brick with Odin and easy. Follow the guide I linked earlier to a t and you'll be fine
Sent from my SGS3 running Eclipse 2.1
Click to expand...
Click to collapse
You are a scholar and a gentleman!! THANK YOU very much. You can have a portrait session on me any time. Name the time and place.
Prophotog said:
You are a scholar and a gentleman!! THANK YOU very much. You can have a portrait session on me any time. Name the time and place.
Click to expand...
Click to collapse
Cool, I take it you're up and running again. Just make sure you use ez unlock 1.2 next time. And the positive is you're an Odin pro now!
Sent from my SGS3 running Eclipse 2.1
Hi, I have a Verizon S3 flashed to Boost Mobile. I tried to gain root by flashing a stock rooted Rom and messed up the flash. I had to take it back to be flashed again  Now I'm more cautious before hand. I should have backed it up before attempting it, I know I know lol can anyone shed some light on how to update a flashed phone as well as how to root it. I could really use the help 
Also after I messed up the boost flash I paniced and flashed a sprint kernel hoping this would fix the problem. Since then anything that I've tried to view including taking camera shots and web browsing if done in landscape mode will be upside down, any remedy for this problem? I know now... root first, flash later. 
Sent from my SPH-L710 using XDA HD
Alex0826 said:
Hi, I have a Verizon S3 flashed to Boost Mobile. I tried to gain root by flashing a stock rooted Rom and messed up the flash. I had to take it back to be flashed again  Now I'm more cautious before hand. I should have backed it up before attempting it, I know I know lol can anyone shed some light on how to update a flashed phone as well as how to root it. I could really use the help 
Also after I messed up the boost flash I paniced and flashed a sprint kernel hoping this would fix the problem. Since then anything that I've tried to view including taking camera shots and web browsing if done in landscape mode will be upside down, any remedy for this problem? I know now... root first, flash later. 
Sent from my SPH-L710 using XDA HD
Click to expand...
Click to collapse
Sprint kernel is causing the inversion. Flash a vzw kernel. Read first flash later.
Sent from my SCH-I535 using xda app-developers app
Who ever did your flash might not done it right cause ya not supposed to lose a flash like that unless he didn't do things right. I can factory reset mine and I wont loose flash
Sent from my SPH-L900 using Tapatalk 2
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.
Normally, I wouldn't ask for help with a problem like this, but I'm rather concerned and could use assistance. Several days ago, I attempted to unlock and root my Verizon GS3. I followed the instructions from the XDA article, along with the ones provided in DroidModd3rX's YouTube video exactly on my VZW GS3, build JZO54K. I hard bricked my phone after flashing the VRALEC bootchain. It only showed up in the Device Manager on Windows 8 as QHSUSB_DLOAD. It was stuck like that as soon as I flashed the bootchain. Is there something I've done wrong that I could have done differently to prevent it from happening? I had just purchased it the day before, so I was able to get a replacement, but I'm highly interested in rooting my device (I've successfully rooted every other phone I've had) and want to ensure this doesn't happen again. Is it a problem with Windows 8, is it the build my phone is running on, or is it perhaps because I had USB Debugging checked on? I just find it odd that I've had this problem when I followed all the proper protocol. And yes, I did check the MD5, it was fine.
Can you get into Odin mode or download mode? If you can, follow this thread. http://forum.xda-developers.com/showthread.php?t=1974114
Sent from my SCH-I535 using xda premium
darthsentinel said:
Normally, I wouldn't ask for help with a problem like this, but I'm rather concerned and could use assistance. Several days ago, I attempted to unlock and root my Verizon GS3. I followed the instructions from the XDA article, along with the ones provided in DroidModd3rX's YouTube video exactly on my VZW GS3, build JZO54K. I hard bricked my phone after flashing the VRALEC bootchain. It only showed up in the Device Manager on Windows 8 as QHSUSB_DLOAD. It was stuck like that as soon as I flashed the bootchain. Is there something I've done wrong that I could have done differently to prevent it from happening? I had just purchased it the day before, so I was able to get a replacement, but I'm highly interested in rooting my device (I've successfully rooted every other phone I've had) and want to ensure this doesn't happen again. Is it a problem with Windows 8, is it the build my phone is running on, or is it perhaps because I had USB Debugging checked on? I just find it odd that I've had this problem when I followed all the proper protocol. And yes, I did check the MD5, it was fine.
Click to expand...
Click to collapse
Just so you know, it isn't the USB debugging. I just did the same procedure using Windows 7 and Odin 3.07 with debugging on, and it worked first shot. Could be Windows 8, but I can't say for certain.
m-cat said:
Can you get into Odin mode or download mode? If you can, follow this thread. http://forum.xda-developers.com/showthread.php?t=1974114
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Nope, it was quite literally hard bricked. No getting it into anything.
a.demarco said:
Just so you know, it isn't the USB debugging. I just did the same procedure using Windows 7 and Odin 3.07 with debugging on, and it worked first shot. Could be Windows 8, but I can't say for certain.
Click to expand...
Click to collapse
Hrmm, well that is annoying, as I don't have access to a Windows 7 Computer to try it again... But thanks for the heads-up!
Are you SURE you followed DroidmodderX's instructions to the T? I've seen this happen from flashing the file in the wrong slot in Odin. Did you make sure to put it in the PDA slot?
I too used this method to root and unlock a while back. I would feel confident using it again if I needed to.
nicholi2789 said:
Are you SURE you followed DroidmodderX's instructions to the T? I've seen this happen from flashing the file in the wrong slot in Odin. Did you make sure to put it in the PDA slot?
I too used this method to root and unlock a while back. I would feel confident using it again if I needed to.
Click to expand...
Click to collapse
Yes, I was very sure to put it in the PDA slot. In fact, I remember double-checking that I did that because I thought it was unusual.
darthsentinel said:
Yes, I was very sure to put it in the PDA slot. In fact, I remember double-checking that I did that because I thought it was unusual.
Click to expand...
Click to collapse
Hmm. Are you sure you got a good download of the bootchain?
nicholi2789 said:
Hmm. Are you sure you got a good download of the bootchain?
Click to expand...
Click to collapse
Almost completely positive. At the very least, the MD5 Matched.
darthsentinel said:
Almost completely positive. At the very least, the MD5 Matched.
Click to expand...
Click to collapse
Okay. So you've installed the correct drivers for your phone as well right? It shows up as SCH-I535 on your computer?
Sent from my MOAR'D Galaxy S3 via tapatalk 2
nicholi2789 said:
Okay. So you've installed the correct drivers for your phone as well right? It shows up as SCH-I535 on your computer?
Sent from my MOAR'D Galaxy S3 via tapatalk 2
Click to expand...
Click to collapse
Yes, it does indeed.
Did you uncheck Auto Reboot when you were supposed to?
darthsentinel said:
Normally, I wouldn't ask for help with a problem like this, but I'm rather concerned and could use assistance. Several days ago, I attempted to unlock and root my Verizon GS3. I followed the instructions from the XDA article, along with the ones provided in DroidModd3rX's YouTube video exactly on my VZW GS3, build JZO54K. I hard bricked my phone after flashing the VRALEC bootchain. It only showed up in the Device Manager on Windows 8 as QHSUSB_DLOAD. It was stuck like that as soon as I flashed the bootchain. Is there something I've done wrong that I could have done differently to prevent it from happening? I had just purchased it the day before, so I was able to get a replacement, but I'm highly interested in rooting my device (I've successfully rooted every other phone I've had) and want to ensure this doesn't happen again. Is it a problem with Windows 8, is it the build my phone is running on, or is it perhaps because I had USB Debugging checked on? I just find it odd that I've had this problem when I followed all the proper protocol. And yes, I did check the MD5, it was fine.
Click to expand...
Click to collapse
I have always followed the guide here. Not sure what version of the OS you have but I odin my phone back to the original factory and then run the root posted here http://forum.xda-developers.com/showthread.php?t=1762709
Super Interesting
I just received two phones from verizon and I followed the same exact instructions, on the first phone it worked like a charm. And on the second phone - at the very same step - it just blinked off and that was all she wrote. I tried a full power cycle, charging all night, and using the USB > PC connection to maybe kick it out of its funk. All I got was the QHSUSB_DLOAD popup when I plugged it in. Searching for that turns up a few things, but mostly for HTC phones. I also installed Keis and tried to redo all the driver junk with that, still nothing. So sad.
I have to ask the most obvious. Hows your battery? I thought I had hard bricked my device too one time and it was just a dead battery.
Sent from my SCH-I535 using xda premium
m-cat said:
I have to ask the most obvious? Hows your battery? I thought I had hard bricked my device too one time and it was just a dead battery.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
The battery was charging all night, I had meant to put this in an edit but had to wait five minutes and wandered off . I also forgot to add that it was a VZW SGS 3 running 4.1.2. I followed these (youtube DOT com SLASH watch?v=K4b9hcWHrW8) instructions. As I said before, it worked fine with the first phone. Second one died on the first step.
Anyways, my friend convinced me to just send it back. I'm not worried as the ROM and everything is stock.
a.demarco said:
Did you uncheck Auto Reboot when you were supposed to?
Click to expand...
Click to collapse
I didn't get to the point, it was hard bricked as soon as I flashed the VRALEC bootchain, which still said it needed auto-reboot checked.
khymbote said:
I have always followed the guide here. Not sure what version of the OS you have but I odin my phone back to the original factory and then run the root posted here http://forum.xda-developers.com/showthread.php?t=1762709
Click to expand...
Click to collapse
The version of the OS I had at the time was 4.1.2. Are you able to flash an earlier version of the OS through Odin?
m-cat said:
I have to ask the most obvious. Hows your battery? I thought I had hard bricked my device too one time and it was just a dead battery.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Sounds like the other guy here had the same problem. My battery was full at the time of flashing. And QHUSB_DLOAD is pretty much a sure sign of a hard brick and not a battery issue as far as I can tell.
Delete thanks
The version of the OS I had at the time was 4.1.2. Are you able to flash an earlier version of the OS through Odin?
Yes I have the OS from the initial release of the phone back in July of last year. I keep it just in case I need to factory restore my phone.