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.
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.
I have rooted two phones in the past but do not feel comfortable rooting my Verizon Galaxy S III. I'm looking to pay someone $15-$25 for their time to root my phone remotely. I'll pay through paypal, then provide my logmein user name and password so whoever can remotely complete the root while I watch. PLEASE, no first timers. I'll make a selection from those that respond. Thanks!!
follow a guide, take notes if you have to. print it out, highlight and read up. theres also videos that you can watch which you can pause and do each step alongside the video. thats how i started as I was cautious at first also.
it can be overwhelming at first, but its really not that difficult.
you can do what you want though. good luck.
ddurandSGS3 said:
follow a guide, take notes if you have to. print it out, highlight and read up. theres also videos that you can watch which you can pause and do each step alongside the video. thats how i started as I was cautious at first also.
it can be overwhelming at first, but its really not that difficult.
you can do what you want though. good luck.
Click to expand...
Click to collapse
I've read over the guide multiple times and think I may just go ahead and try it. Thanks for the encouragement.... seems like that's all I needed..... lol
randino41 said:
I've read over the guide multiple times and think I may just go ahead and try it. Thanks for the encouragement.... seems like that's all I needed..... lol
Click to expand...
Click to collapse
Shouldn't be too difficult, Open1your1eyes0 made a very easy to follow guide.
Good luck!
Sent from my SCH-I535 using Tapatalk 4 Beta
SlimSnoopOS said:
Shouldn't be too difficult, Open1your1eyes0 made a very easy to follow guide.
Good luck!
Sent from my SCH-I535 using Tapatalk 4 Beta
Click to expand...
Click to collapse
One thing I couldn't find in the thread. Is an SD card mandatory? I don't have currently have one but will get one if necessary.
sd card isnt mandatory. the larger TW roms can be close to 1gb in size though.
theyre cheap on amazon if you wanted to grab one.
use that 15-25$ you were gonna pay someone to root with and buy a case and sdcard!
Yep, like others have said, read up and follow the guide. If you have any questions, just ask.
A few tips, make sure you unlock your bootloader and only flash roms for the Verizon galaxy s3.
Sent from my SCH-I535 using xda app-developers app
bobAbooE said:
Yep, like others have said, read up and follow the guide. If you have any questions, just ask.
A few tips, make sure you unlock your bootloader and only flash roms for the Verizon galaxy s3.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
ddurandSGS3 said:
sd card isnt mandatory. the larger TW roms can be close to 1gb in size though.
theyre cheap on amazon if you wanted to grab one.
use that 15-25$ you were gonna pay someone to root with and buy a case and sdcard!
Click to expand...
Click to collapse
Yal are awesome. Thanks. Ill post results later.
I walked a guy though it over the phone on XDA 2 nights ago. He fully rooted his S4. I have all the files as well for rooting the S3. If you need help PM me a number to call and I;ll assist from start to finish.
randino41 said:
One thing I couldn't find in the thread. Is an SD card mandatory? I don't have currently have one but will get one if necessary.
Click to expand...
Click to collapse
ddurandSGS3 said:
sd card isnt mandatory. the larger TW roms can be close to 1gb in size though.
theyre cheap on amazon if you wanted to grab one.
use that 15-25$ you were gonna pay someone to root with and buy a case and sdcard!
Click to expand...
Click to collapse
SD cards are not mandatory as mentioned before, but they are highly recommended as the only way you can lose data on them is if you explicitly tell your phone to format the card, a ROM flash will not format the card, and a ROM will never need the card to be formatted.
randino41 said:
I've read over the guide multiple times and think I may just go ahead and try it. Thanks for the encouragement.... seems like that's all I needed..... lol
Click to expand...
Click to collapse
The great part is even if you mess up and brick your phone you can always Odin back.
Trust me having the ability to Odin back saved me a few times.
Back up your imei and make a nandroid after you root just in case.
clean Rom/xda powerd by zero-lemon & tweaked out Guided by the power of Zeus kernel!!
Like everyone has said before follow the guides and it really is simple. make sure you read them several times and watch the videos. it is better to understand what you are doing upfront. I made the mistake of rooting a friend's phone one time and rooting my fiance's phone. It became a nightmare because he didn't take the time to read through the forums here on xda like I had asked him and it was constantly a pain trying to help him. I figured my fiance's incredible needed all the help it could get and she loved it rooted but with rooting there is always the occasional issue and it was easier for me to get her a note 2 then keep having her upset about her phone.
rooting sch-i535
very easy to root. Just did mine this weekend, took an hour or two of reading and trying several things. don't buy the gs3 toolkit v7.4.5 as it didnt work for me.. I think it was driver related but the recovery loads never worked.
What did work is, download odin 3.07, the vralec bootchain, cwm, and superuser w/ bootloader. you have to know what version you are on. go to settings, about phone. if it is 4.1.1 or 4.1.2 go here:
http://forum.xda-developers.com/showthread.php?t=2046439
follow the instructions step by step. In fact I'd highly recommend watching the video first and following it STEP BY STEP exactly how he does it.
Notes:
step3: get the Both Root and Unlocked Bootloader SuperUser. this needs to be on your External SDcard in your phone to follow the instructions per se. You are going to use 'load zip file from external SDcard' on the Recovery step.
The other files should be on your computer in your odin folder (or elsewhere that you can find them). All you need is VRALEC and CWM which will be loaded via the PDA button in Odin ONLY.
step5: I didn't restore the factory bootchain. just left it as is.. working fine for me
if you dont boot into custom recovery directly after flashing the VRALEC bootchain the phone will detect that you are screwing with it and reload the factory bootchain! it happened to me the first time. Had to flash a couple times and do things in the correct order to finally get CWM on there. You can see the difference between the factory recovery and CWM recovery (it has a little hat in the middle of the screen and text is different, etc) As long as you flash it with the PDA button ONLY you will be fine. DO NOT USE BOOTLOADER BUTTON IN ODIN AT ALL! Be very careful with Odin and triple-check that you are using the correct settings. It's very easy, but you can potentially brick your phone if you are not carefully looking at every setting. Take your time! :fingers-crossed:
This is my first post ever here so I'm sorry if I'm breaking some rule (read the forum rules so I don't think I am) or if it's in the wrong subforum (although this does seem like a help & troubleshooting topic to me).
A little backstory is probably necessary.
I rooted my s3 (latest OTA update) via CASUAL (thread: http://forum.xda-developers.com/showthread.php?t=2332825) and it seemed like it worked for the most part, although it didn't boot into twrp like it should have and instead booted into normal recovery. I just assumed that it was because something went wrong with the recovery installation so I just thought "ok whatever."
Root access was there, and I assumed the bootloader was unlocked since I read several places that when it's unlocked, the initial samsung boot logo appears for about a second as opposed to several seconds when it's locked. So I just assumed all i needed was to reinstall a custom recovery and I was golden.
Installed ROM Manager, flashed CWM through the app, and rebooted the phone, and as it was booting into recovery I was greeted with the infamous "NO CUSTOM SOFTWARE ALLOWED PLEASE ALERT PAPA VERIZON IMMEDIATELY" warning.
I was about to flash back to stock through odin (which i regretted since I've had bad experiences in the past using it) when I figured out I could get the device to boot normally by clicking cancel in the download mode confirmation window. I guess it kept trying to reboot to recovery after every unsuccessful boot, which made it seem like it was softbricked to me.
Phone is operating normally now, and it should after another reboot as long as it doesn't try to go into recovery again (though I'm kind of afraid to even do that).
Is there any way without Odin I can fix my recovery and/or bootloader? I'm not sure what the problem is here and I don't think this sort of thing is a common searchable issue. Google/XDA search didn't bring up anything that sounded like someone had 100% the same problem I do.
Also on a semi-related note, does EZ-Unlock still work with this latest OTA? And if my bootloader is potentially unlocked already, would unlocking it again through EZ-Unlock break something?
Sleix said:
This is my first post ever here so I'm sorry if I'm breaking some rule (read the forum rules so I don't think I am) or if it's in the wrong subforum (although this does seem like a help & troubleshooting topic to me).
A little backstory is probably necessary.
I rooted my s3 (latest OTA update) via CASUAL (thread: http://forum.xda-developers.com/showthread.php?t=2332825) and it seemed like it worked for the most part, although it didn't boot into twrp like it should have and instead booted into normal recovery. I just assumed that it was because something went wrong with the recovery installation so I just thought "ok whatever."
Root access was there, and I assumed the bootloader was unlocked since I read several places that when it's unlocked, the initial samsung boot logo appears for about a second as opposed to several seconds when it's locked. So I just assumed all i needed was to reinstall a custom recovery and I was golden.
Installed ROM Manager, flashed CWM through the app, and rebooted the phone, and as it was booting into recovery I was greeted with the infamous "NO CUSTOM SOFTWARE ALLOWED PLEASE ALERT PAPA VERIZON IMMEDIATELY" warning.
I was about to flash back to stock through odin (which i regretted since I've had bad experiences in the past using it) when I figured out I could get the device to boot normally by clicking cancel in the download mode confirmation window, rebooting the phone normally. I guess it kept trying to reboot to recovery after every unsuccessful boot, which made it seem like it was softbricked to me.
Phone is operating normally now, and it should after another reboot as long as it doesn't try to go into recovery again (though I'm kind of afraid to even do that).
Is there any way without Odin I can fix my recovery and/or bootloader? I'm not sure what the problem is here and I don't think this sort of thing is a common searchable issue. Google/XDA search didn't bring up anything that sounded like someone had 100% the same problem I do.
Also on a semi-related note, does EZ-Unlock still work with this latest OTA? And if my bootloader is potentially unlocked already, would unlocking it again through EZ-Unlock break something?
Click to expand...
Click to collapse
That is really weird...
I was reading it and was going to suggest easy unlock v1.2,you will not break anything using that app.
If that still doesn't work, try to flash TWRP through goo manager and see if it somehow fixes your recovery issue.
It sounds to me that your Bootloader is unlocked though... But give it a shot.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
That is really weird...
I was reading it and was going to suggest easy unlock v1.2,you will not break anything using that app.
If that still doesn't work, try to flash TWRP through goo manager and see if it somehow fixes your recovery issue.
It sounds to me that your Bootloader is unlocked though... But give it a shot.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the quick response.
That was going to be what I tried first, that's why I asked about it.
I'll wait for a little more input before trying it though if it's really that weird of an issue.
Sleix said:
Thanks for the quick response.
That was going to be what I tried first, that's why I asked about it.
I'll wait for a little more input before trying it though if it's really that weird of an issue.
Click to expand...
Click to collapse
It's just strange that you only get that message with recovery mode, it normally will not do that.
At the very worst, an odin back to stock is pretty easy. Just follow the same process, but use ez recovery instead of rom manager. It was made specifically for our phone, and never gives me any issues when installing recoveries.
I still think if you use ez unlock it'll probably fix the issue completely. Let me know if you figure it out. Good luck.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
It's just strange that you only get that message with recovery mode, it normally will not do that.
At the very worst, an odin back to stock is pretty easy. Just follow the same process, but use ez recovery instead of rom manager. It was made specifically for our phone, and never gives me any issues when installing recoveries.
I still think if you use ez unlock it'll probably fix the issue completely. Let me know if you figure it out. Good luck.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks. Used ez unlock to unlock the bootloader. It was previously labeled as "Unknown".
Downloading ez recovery right now. Do you think I need to reinstall my recovery just to make sure?
Sleix said:
Thanks. Used ez unlock to unlock the bootloader. It was previously labeled as "Unknown".
Downloading ez recovery right now. Do you think I need to reinstall my recovery just to make sure?
Click to expand...
Click to collapse
No, but it wouldn't hurt.
Use 1.2 of ez unlock, versions 1.3 and 1.4 will give an unknown message. There have also been lots of reports saying that version 1.4 did not unlock their bootloader.
These are the most recent recoveries, download and flash in the ez recovery app if you need to.
http://forum.xda-developers.com/showthread.php?t=2096735
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
No, but it wouldn't hurt.
Use 1.2, versions 1.3 and 1.4 will give an unknown message. There have also been lots of reports saying that version 1.4 did not unlock their bootloader.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Reflashed CMW (I used the version provided by ez recovery, please let me know if that's a problem) just in case and it worked like a charm. Thanks!
Also I did use version 1.2. I actually had it sitting on my phone's home screen before I made this thread.
It still showed up as "Unknown". Maybe that indicated the problem?
Regardless, this problem seems to have been fixed. Now it's time to do some research on verizon s3 roms.
Also another semi-unrelated note, it seems I tripped a flash counter somewhere along the line.
Is Triangle Away one of those apps that is just "open and press a button"? I've been kind of wary of using it since it has that huge warning in app's description.
Sleix said:
Reflashed CMW (I used the version provided by ez recovery, please let me know if that's a problem) just in case and it worked like a charm. Thanks!
Also I did use version 1.2. I actually had it sitting on my phone's home screen before I made this thread.
It still showed up as "Unknown". Maybe that indicated the problem?
Regardless, this problem seems to have been fixed. Now it's time to do some research on verizon s3 roms.
Also another semi-unrelated note, it seems I tripped a flash counter somewhere along the line.
Is Triangle Away one of those apps that is just "open and press a button"? I've been kind of wary of using it since it has that huge warning in app's description.
Click to expand...
Click to collapse
Glad to hear it's working! Strange issue but looks like you ironed it out.
Triangle away is the app you would use. You tripped it using the rooting method injecting your recovery through odin, it's a big warning because it messes with your boot partition. If it fails and borks your boot partition, then you'd have to jtag your phone to fix it.
I personally wouldn't use it unless I was turning in my phone for service or replacement. But the app has great reviews and not many reports of bricks.
Before flashing anything, use a newer recovery image. The one provided by ez recovery is from last year, the newer versions are better written to prevent possible errors that come up with jellybean.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Glad to hear it's working! Strange issue but looks like you ironed it out.
Triangle away is the app you would use. You tripped it using the rooting method injecting your recovery through odin, it's a big warning because it messes with your boot partition. If it fails and borks your boot partition, then you'd have to jtag your phone to fix it.
I personally wouldn't use it unless I was turning in my phone for service or replacement. But the app has great reviews and not many reports of bricks.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I'll keep that in mind, thanks again!
Any roms you'd recommend?
Sleix said:
I'll keep that in mind, thanks again!
Any roms you'd recommend?
Click to expand...
Click to collapse
Read through the op's and decide based on what you're looking for.
Mostly stock, very stable:
Clean rom, bonestock, darthstalker x1.
More modified stocks, more buggy but can run very well:
Hyperdrive, axis, goodness, moar
AOSP isn't my cup of tea, but they are fast and lag free.
Make sure you update your recovery image first, I edited my last post but think you missed it.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Read through the op's and decide based on what you're looking for.
Mostly stock, very stable:
Clean rom, bonestock, darthstalker x1.
More modified stocks, more buggy but can run very well:
Hyperdrive, axis, goodness, moar
AOSP isn't my cup of tea, but they are fast and lag free.
Make sure you update your recovery image first, I edited my last post but think you missed it.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Will do. Thanks for pointing that edit out.
I have a stock 4.3 d2vzw, Some how my friend tried to root and unlock the bootloader with ez unlock 1.2. Now the phone is "qhsusb dload" - hard brick. I tried over 20 hrs+ with micro sd tricks. It didn't work. Any one help!! Please help, anybody? Or only JTAG can help.
Sent from my HTC One using xda app-developers app
magicianq007 said:
I have a stock 4.3 d2vzw, Some how my friend tried to root and unlock the bootloader with ez unlock 1.2. Now the phone is "qhsusb dload" - hard brick. I tried over 20 hrs+ with micro sd tricks. It didn't work. Any one help!! Please help, anybody? Or only JTAG can help.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
If you can access ODIN mode, then there's a script that fixes bricks like that. Look around the VZW Galaxy S3 threads.
And if you actually read around, people kept telling others that the bootloader is locked. So trying to use EZ Unlock is a BIG NO. That's why it bricked.
If you stuck to stock Android 4.1.2, then there would be no issue with using EZ Unlock. But since you're on stock Android 4.3, that's a big no. You'll definitely get bricked like the way you are right now.
If you truly are hard hard bricked maybe you will get insperation for a fix. NOT FOR THE S3 OR SAMSUNG but maybe helpful http://forum.xda-developers.com/showthread.php?t=1522351
Bricked after trying ez unlock.....garbage!!!...
I have tried the sd card method on this phone multiple times...i have even tried placing all the debrick image files directly into the root of the sd card...tried multiple brand sd cards with no luck!!! thanks alot ez unlocker...may need to change the name to ez bricker!!! Oh and as far as telling people about "reading around"...no where did I see when reading about this ez unlock any mention of it bricking devices on 4.3! Are there any debrick files that anyone on here has used to unbrick this thing or what? As of right now...the phone is hardbricked to the point that odin doesn't recognize it...any ideas or help maybe using linux ...a nice step by step would be cool! thanks
crazy32horse said:
I have tried the sd card method on this phone multiple times...i have even tried placing all the debrick image files directly into the root of the sd card...tried multiple brand sd cards with no luck!!! thanks alot ez unlocker...may need to change the name to ez bricker!!! Oh and as far as telling people about "reading around"...no where did I see when reading about this ez unlock any mention of it bricking devices on 4.3! Are there any debrick files that anyone on here has used to unbrick this thing or what? As of right now...the phone is hardbricked to the point that odin doesn't recognize it...any ideas or help maybe using linux ...a nice step by step would be cool! thanks
Click to expand...
Click to collapse
First of all, you're not supposed to even try to unlock the boot loader if you accepted the 4.3 OTA. The reason your phone got bricked was because you tried to unlock the boot loader after getting the 4.3 OTA. Don't blame the EZ unlock app for your mistakes.
http://forum.xda-developers.com/showthread.php?t=2581166
A link by Spyro for you in case you can't access the boot loader or ODIN mode at all. If you're able to get into ODIN mode, Pagel has a thread that explains how to fix that too. All you have to do is look.
Pagel's thread.
http://forum.xda-developers.com/showthread.php?t=2586319
I have tried the first link method, it didn't work. I believe it's new hard brick because of ez unlocked. I don't blame ez unlocked, I should think before I try it. Thank you for your help,.
Sent from my HTC One using xda app-developers app
OK..I was DEAD in the water. Spent the last 2 days trying to un-brick the phone.
Samsung S3, VZW i535, Rooted, partially un-bloated, and unlocked until [email protected]$#! upgraded itself to Android 4.3 (#@!%$!#%@#$%@#$%@#$)
Unwittingly while trying to do a full Nandroid backup of the system, I ran across a problem which looked like it needed to be unlocked again. Upon unlocking it still worked, until I attempted the CWM recovery backup - Instant Black Screen power off.
Unresponsive to Power. Unresponsive to Power+Home+Vup - Unresponsive to Power+Home+Vdn. Not visible to ODIN or to USB...it would have a red-light when plugging in ISB for about 5 mins, then red light off. No vibration, no flicker of the screen, nothing. 100% UNResponsive phone.
I attempted a Jog - No Dice. Forget it.
I attempted to use WinDisk32 to create an image of "Verizon_Galaxy_S_3_Debrick.img" to the SD Card from the video of the kid thats 10:22 long, and his second video thats 12+ min long. Nope. Nada (I attempted at least 20 times)
His video ONLY works from pre 4.3 upgraded phones. He spent so much time doing that video he should add the extra link to the other debrick.bin file and he would be a guru!!! hehe
Attempted a few other thing as well since I now was sure it was fully hard-bricked FUBAR.
Then I kept thinking to myself that it must have something to do with Android 4.3 and its bootloader...came here again and found this thread which lead me to the "After 4.3 upgrade" file of "Debrick.bin" - Used WinDisk32 to the SAME SD card, stuck it in, stuck battery in, and worked first time.
Can Only boot with SD card in phone for time being but hey, im 100% up. And I also can make the SD card back to its full 16GB using SDFormatter - free on the net.
Thank you all.
note: I think we need a new term: "Hard-Soft-Bricked" - reason is that if the power buttons still send a signal to the board to attempt a boot from the CD Card, then its technically still responsive, we just cant see that its responsive. Unlike a total hard-brick that isnt really doing anything from the buttons at all and only responds to a powered JTAG attempt.
ez bricker...
Hi i have the vzw s3 and used ez unlocker 1.2 to unlock the bootloader and it said "that was easy" then the phone was bricked ...also worth noting im on jb 4.1.2
Need help from Hard Brick
My phone is bricked after unlock bootloader via EZ-Unlocker. How Can I Un-brick my phone.
I tried SD card method but failed.
My Phone OS was: 4.4.2
Model: SGH-i535
Having exact same problem as the person above... Used ez unlocked 1.2 and the phone does not do anything now... Not odin recovery, not booting, nothing.... Tried the sd trick but did not work. Please kindly help me if there is something else....
Thank you very very much!
My Phone OS was: 4.4.2
Model: SGH-i535
I'm having the same problem ...
I try a usb JIT ... doesn't work ...
Did you try with a 4.4.2 debrick.img to your SD ?
My Phone OS was: 4.4.2
Model: SGH-T999V
here's what is on the apps page on rootzwiki <----- idk if im spelling it right
Since I know a lot of people do not thoroughly read threads or posts, I am again posting my warning at the bottom of the OP:
***Admin Edit*** - This app has not been updated since 2012 and does not work on any bootloaders since the ML1 4.3 OTA. If you have taken the 4.3 OTAs of ML1 or NC1 or the 4.4.2 OTA of NE1, do not download and try to use this app to unlock your bootloader. You will hard brick your device. The app is no longer even available on the play store.
Dont ever try ez unlocker
Exactly same problem was with me. tried unlocking bootloader of SCH-I535 and got it HARD BRICKED
SD card tricks wont work. The only solution is JTAG. My device remains at the repairing shop for 3 MONTHS. it goes from shop after shop and another shop... and after 3 months i get it back. and still its Wifi was not working and also the network signals drop frequently
lets give some tips for feature tries if u on 4.3+ dont bother trying to unlock u wont only brick trust me ive tried
1 never ever erase your modem or boot partion if u do u cant reboot u phone into download mode hard bricked send it in to get fixed
think only way fix it in this state is bootloader already unlocked lol so if locked forget trying does no good
im on 4.4.2 stock bootloader still locked can be rooted easy useing odon it works but u cant do upgrades ota after rooted so be happyy with your changes cause there whay u set it stays problem with customs id the google store apps dont all work like google camery my fav dont work on alot them stock works grat so far no custom beats 4.4.2 yet cept in maybe promtness but got bugs in stor and camera cant go with my cam or music google store are a must
This will fix the Problem
http://forum.xda-developers.com/showthread.php?p=35189036#post35189036
I have the same issue
EZ-unlocker Bricked my Galaxy S3 Varizon i535
Same happened to me after using EZ-Unlocker this F**king app made my mobile dead i tried everything found online but unable to boot my phone
My Phone OS was: 4.4.2
Model: SGH-i535
eh1san said:
Same happened to me after using EZ-Unlocker this F**king app made my mobile dead i tried everything found online but unable to boot my phone
My Phone OS was: 4.4.2
Model: SGH-i535
Click to expand...
Click to collapse
Above it is stated that the sdcard debrick images do not work. If that is true in your case the only option available may be a jtag service.
eh1san said:
Same happened to me after using EZ-Unlocker this F**king app made my mobile dead i tried everything found online but unable to boot my phone
My Phone OS was: 4.4.2
Model: SGH-i535
Click to expand...
Click to collapse
No, this app did not make your mobile dead. You not doing the proper research and reading before trying to use this app made your mobile dead. Your fault not the fault of the app.
landshark68 said:
No, this app did not make your mobile dead. You not doing the proper research and reading before trying to use this app made your mobile dead. Your fault not the fault of the app.
Click to expand...
Click to collapse
bro shouldn't this app give a warning popup message to user when we open this app that "don't try this app on Android 4.4.2 this app will brick your phone"
eh1san said:
bro shouldn't this app give a warning popup message to user when we open this app that "don't try this app on Android 4.4.2 this app will brick your phone"
Click to expand...
Click to collapse
In the app? Nope. The app has long since been removed from the Play Store. Also, the original place this app was distributed has a bright red warning indicating users on 4.3 and 4.4.2 should not use it:
http://rootzwiki.com/topic/32456-ap...lock-your-bootloader-pre-43-bootloaders-only/
Edit: I'm referring to "EZ Unlock" btw. Any app by any other name, even a slight deviation in spelling, is not the original app to unlock the bootloader on a VZW S3 on 4.1.2.
Sent from my Nexus 5X using Tapatalk