Related
Hello, I just got my new GS3 yesterday. Eager to root and ROM and all the fun stuff. I rooted and unlocked, and used Odin to flash CWM Recovery. Flashed the latest version of Android Revolution HD 16. I wiped cache, dalvik, the whole 9 yards. I did not WIPE boot.img though. Flashed Android Revolution 16, it all went good. Clicked Reboot Phone in CWM Recovery and nothing. No LED light on when plugged into USB or via wall charger. No Download mode, or recovery. Nothing, like nothing at all. Anything you guys suggest?
EDIT: I am not sure if it is Hard Bricked. When I plug it into my PC, it makes a sound. Also tries to install a driver and fails every time.
EDIT2: Okay guys, my fault. Downloaded a ROM that was meant for a different model/type GS3 forum when I have a Verizon GS3 (SCH-1535). Anyone know how to fix this problem? Please disregard this incorrect forum post.
If you flashed anything related to the international S3, Google search J-tag! Or return the device and play dumb...
droidstyle said:
Google search J-tag! Or return the device and play dumb...
Click to expand...
Click to collapse
I am paying for full coverage every month too, and okay, couldn't I also get a Usb JIG to force download mode?
T Greezy said:
I am paying for full coverage every month too, and okay, couldn't I also get a Usb JIG to force download mode?
Click to expand...
Click to collapse
No read my edited post. You most likely hardbricked your device, meaning you no longer have download mode.
droidstyle said:
No read my edited post. You most likely hardbricked your device, meaning you no longer have download mode.
Click to expand...
Click to collapse
Well, I NOW have a red LED on my phone when it is plugged into the PC without battery, sd card, or sim card. Is that a good sign?
T Greezy said:
Well, I NOW have a red LED on my phone when it is plugged into the PC without battery, sd card, or sim card. Is that a good sign?
Click to expand...
Click to collapse
No that verifies what i previously posted.
droidstyle said:
No that verifies what i previously posted.
Click to expand...
Click to collapse
I have faith, thought. I can maybe push something using ADB you think?
You need J-tag.
If there was a way to fix it yourself, nobody on here would worry about bricked phones.
Gotta be super careful and read every single word of a ROM thread and if you aren't sure if it will work for your phone or not, just ask and someone will say either yes or no
Sent from my SCH-I535 using xda app-developers app
josh995 said:
You need J-tag.
If there was a way to fix it yourself, nobody on here would worry about bricked phones.
Gotta be super careful and read every single word of a ROM thread and if you aren't sure if it will work for your phone or not, just ask and someone will say either yes or no
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I guess so. I read something about plugging the phone into the pc without the battery so the red light would come on. Then, you would hold a combination of buttons, and while you're still holding them, put the battery back in while you're still holding them. I guess J-Tag is the only way? Where can I get this? Someone link me. Thanks!
T Greezy said:
I guess so. I read something about plugging the phone into the pc without the battery so the red light would come on. Then, you would hold a combination of buttons, and while you're still holding them, put the battery back in while you're still holding them. I guess J-Tag is the only way? Where can I get this? Someone link me. Thanks!
Click to expand...
Click to collapse
Look like I'm going to drop 60 bucks for a JTAG service? Anyone please stop me if this is not the only way to fix this
email me at [email protected]!
No one is going to stop you. You flashed an international ROM on an s3. This is a known method of hard bricking your s3.
Sent from my SCH-I535 using xda app-developers app
T Greezy said:
Look like I'm going to drop 60 bucks for a JTAG service? Anyone please stop me if this is not the only way to fix this
email me at [email protected]!
Click to expand...
Click to collapse
That sounds about right. Luckily it's $60 and not $600 for a new phone
Sent from my SCH-I535 using xda app-developers app
Same thing happened to me. Needed a j-tag but risked calling Verizon told them my phone wouldn't come on all they asked me was if I damaged it with water or heat. (Either Verizon doesn't care or actually they just scrap the phone) I was rooted and unlocked but flashed the wrong carrier rom. Now I have a replacement phone that cost me $0.
They sent me the 16g and not the 32g by mistake I figured I've pushed my luck enough
Sent from my SCH-I535 using Tapatalk 2
First go to Get.cm download a d2vzw rom. Put it on your sd card. Put the sd card into phone
If you have ADB on your computer do
Code:
adb reboot recovery
You should boot in Clockwork Recovery.
From there flash the D2VZW Rom, Wipe Data,
That should save you.
ericerk said:
First go to Get.cm download a d2vzw rom. Put it on your sd card. Put the sd card into phone
If you have ADB on your computer do
Code:
adb reboot recovery
You should boot in Clockwork Recovery.
From there flash the D2VZW Rom, Wipe Data,
That should save you.
Click to expand...
Click to collapse
How do you figure? How can you adb recovery when the device wont turn on? The device is hardbricked plain and simple...your advice is simply false hope.
I do have a question for the op and the other guy who flashed an international ROM. Were did you get them and how did you find then ( like was it a site you googled?) I've noticed a lot of these lately and am wondering if it's something that can be avoided (besides the obvious read what you're flashing)
To the adb guy there us no recovery on his phone it was overwritten by part of the international ROM. he needs to JTAG his phone, don't call Verizon. You did this to your own phone, pay the 60 and learn your lesson.
Sent from my SGS3 running Eclipse 2.1
droidstyle said:
How do you figure? How can you adb recovery when the device wont turn on? The device is hardbricked plain and simple...your advice is simply false hope.
Click to expand...
Click to collapse
One day someone is going to find a way to unbrick the hard brick, lol. Eventually. Anyways, if it was "dead" then why would it show my S3 as "QHSUSB_DLOAD"? and attempts to install a driver. I'm gonna try to find the right driver to manually install, and troubleshoot from there. I mean come on guys, be optimistic. How great if this problem was RESOLVED? Also, the download mode got wiped/overwritten from a different ROM for a different model of the GS3. What about the Recovery? CWM? If I can just magically, somehow, maybe even push some type of command. Even maybe ADB? Or something in the terminal. I'm really trying to find a solution. So in the future, we will have a SOLUTION.
Anyways, I'm going to be shipping my GS3 Monday or Tuesday for Samsung to repair (If they can) or replace for no charge!
Wish me luck guys, gonna be really thinking out of the box.
Hope you can figure it out. But someone had a way to fix a hard brick.... The JTAG
Sent from my SGS3 running Eclipse 2.1
Okay guys, I've actually have gotten some good progress, I hope! I came across a thread that a guy named (therockk) he also, hard bricked his S3. Sent him a PM, and he told me he got ODIN to recognize his hard bricked S3 "WITHOUT" download mode. He said he found a driver for QHSUSB_DLOAD and manually applied the driver update. His PC, then recognized his S3 as a ID CODE: COM10 - I do not know what that means, I asked around. Some people say that it is the code for when your phone is connected in Download Mode? Nevertheless, this is good in my eyes. The phone as now, recognized as COM10 in ODIN, in its hard-bricked stage. This could be that also, maybe, the phone will be recognized in ADB/Fastboot commands. Maybe we can get something going here guys! I'm trying to look on the bright side. I'll keep you posted.
EDIT: Okay guys, was looking at some screenshots of the CODE ID's. Like I said, my buddy "therockk" said he got ODIN to recognize his phone as a COM10, while being hard-bricked. I am guessing there are different CODE ID's for each model/version of the S3. I did make an observation that he, has a different model S3 ( i747 ) and he got his to see COM10. Which means it was Added!! - My Verizon S3 (SCH-1525) should come up as COM4 when the PC recognizes it. When I do get my PC to recognize my S3, I will confirm that my SCH-1535 phone comes up as COM4, if not, I will confirm the correct CODE ID. therockk's i747 came up as a COM10, that is confirmed.
EDIT 2: Okay guys! Updated the driver successfully! QSHUSB_DLOAD is now Qualcomm HS-USB QDLoader 9008 (COM8). I feel like we're getting closer. Now to see if Odin will pick it up!
I can probably help you through this problem after work tonight if you are still having trouble. Just pm me around 10pm est
Sent from my SCH-I535 using xda app-developers app
So I had a Galaxy S1 Captivate for about 2 year and my wife has a Fascinate and I rooted/flashed them both like it was my job for the last couple years. I never once hard bricked either and for the most part knew what I was doing. I have a couple home made jigs so DL mode or (soft bricks) were never an issue. My question to you guys is I'm trying to gauge how difficult/risky is it to root and rom the GS3 (Verizon model specifically). The reason I'm wondering this info is because I personally don't own my GS3, it is property of my company and I don't want to chance bricking or not being able to easily flash back to stock unless it has gotten easier or less risky since the original Galaxy lineup. I mean if you had 2.3 bootloaders on your GS1 and you had access to a jig, there was pretty much a 0% chance of hard bricking unless you do something really stupid. Sorry for rambling on!
jayjr1105 said:
So I had a Galaxy S1 Captivate for about 2 year and my wife has a Fascinate and I rooted/flashed them both like it was my job for the last couple years. I never once hard bricked either and for the most part knew what I was doing. I have a couple home made jigs so DL mode or (soft bricks) were never an issue. My question to you guys is I'm trying to gauge how difficult/risky is it to root and rom the GS3 (Verizon model specifically). The reason I'm wondering this info is because I personally don't own my GS3, it is property of my company and I don't want to chance bricking or not being able to easily flash back to stock unless it has gotten easier or less risky since the original Galaxy lineup. I mean if you had 2.3 bootloaders on your GS1 and you had access to a jig, there was pretty much a 0% chance of hard bricking unless you do something really stupid. Sorry for rambling on!
Click to expand...
Click to collapse
I came from the Fascinate and this phone is just as easy to flash. Just make sure you read the OP and only flash things made for the US versions and you'll be fine. If something gets hosed, you can always odin back. Here is a great guide to get you started.
http://forum.xda-developers.com/showthread.php?t=1762709
Sent from my SCH-I535 using xda app-developers app
Deliquified said:
I came from the Fascinate and this phone is just as easy to flash. Just make sure you read the OP and only flash things made for the US versions and you'll be fine. If something gets hosed, you can always odin back. Here is a great guide to get you started.
http://forum.xda-developers.com/showthread.php?t=1762709
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I haven't checked that link out yet but how easy is it to go back to the Verizon stock ROM if need be?
Does the ROM procedure go something like this?...
Power Off, DL mode with jig, ODIN a CWM or Kernel package with CWM, mount SD, drag and drop ROM, Flash, win?
well...
well the good news is that you don't have to flash a custom rom for root. I just rooted and unlocked my phone while still running the stock rom. =) i'd post my tutorial but I'm a new member and I have 8 more posts to do before I can post in development.
eorly420 said:
well the good news is that you don't have to flash a custom rom for root. I just rooted and unlocked my phone while still running the stock rom. =) i'd post my tutorial but I'm a new member and I have 8 more posts to do before I can post in development.
Click to expand...
Click to collapse
There is already an in depth tutorial for that as well as one for those who have the recent OTA.
http://forum.xda-developers.com/showthread.php?t=2046439
The above link is those with the jelly bean OTA.
http://forum.xda-developers.com/showthread.php?t=1762709
This above is the in depth guide I was talking about. It was posted on 7/10/12. So there is no need for another tutorial unless you found a new way to do it. If you are talking about RootDebugFS then there is a tutorial for that here as well as the SuperSU version here as well.
I also came from a fascinate which was super easy to flash. As long as you read up on your homework this phone is cake to flash.
You shouldn't have many problems. If you need help, PM me. I'm glad to help.
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
So I'm wondering one last thing. I hear about a "flash counter" on the GS3... anything I need to be really careful about to not trip this "counter"? Will Verizon void the warranty if tripped?
Thanks again guys!
Also, I'm going to be using this phone a lot for work and I ported my old personal number to Google Voice so this will be my personal phone as well, so I need the phone to be pretty solid and stable, should I be looking to flash Original ROMs or from the regular development section?
jayjr1105 said:
So I'm wondering one last thing. I hear about a "flash counter" on the GS3... anything I need to be really careful about to not trip this "counter"? Will Verizon void the warranty if tripped?
Thanks again guys!
Also, I'm going to be using this phone a lot for work and I ported my old personal number to Google Voice so this will be my personal phone as well, so I need the phone to be pretty solid and stable, should I be looking to flash Original ROMs or from the regular development section?
Click to expand...
Click to collapse
Once your rooted, you can download Triangle Away from the App Store and that will restore the counter to 0.
lvgdgts said:
Once your rooted, you can download Triangle Away from the App Store and that will restore the counter to 0.
Click to expand...
Click to collapse
Thanks! Do you need to run the app every time you flash or just right before you would need to take it in to Verizon for warranty/service?
jayjr1105 said:
Thanks! Do you need to run the app every time you flash or just right before you would need to take it in to Verizon for warranty/service?
Click to expand...
Click to collapse
If you unlock bootloader before you flash recovery you will not trip flash counter. If counter is tripped must use Triangle Away while still on stock rom. That being said flash counter does not affect anything except warranty and requires you to Odin stock root, run triangle Away then Odin full stock so best to fix as soon as you root and unlock to avoid extra work at time of return to Verizon.
prdog1 said:
If you unlock bootloader before you flash recovery you will not trip flash counter. If counter is tripped must use Triangle Away while still on stock rom. That being said flash counter does not affect anything except warranty and requires you to Odin stock root, run triangle Away then Odin full stock so best to fix as soon as you root and unlock to avoid extra work at time of return to Verizon.
Click to expand...
Click to collapse
Is there a way to just see if you tripped the flash counter without Triangle Away?
I was following a tutorial on rooting my Galaxy S3 and by mistake I loaded the "VRALEC.bootchain.tar.md5" file under the boot loader option rather than the PDA option.
This was the tutorial "How To Root Verizon Samsung Galaxy S3 4.1.2/4.1.1 & Install CWM Recovery! SCH-I535."
Now my phone won't boot at all and isn't being recognized by my computer when plugged in. Any help with this is greatly appreciated!
dsims9t said:
I was following a tutorial on rooting my Galaxy S3 and by mistake I loaded the "VRALEC.bootchain.tar.md5" file under the boot loader option rather than the PDA option.
This was the tutorial "How To Root Verizon Samsung Galaxy S3 4.1.2/4.1.1 & Install CWM Recovery! SCH-I535."
Now my phone won't boot at all and isn't being recognized by my computer when plugged in. Any help with this is greatly appreciated!
Click to expand...
Click to collapse
If your phone doesn't power on at all no led, no recovery or download access, no vibration even, then I'm afraid by putting the VRALEC.bootchain.tar.md5 in the wrong spot and flashing it through Odin you have hard bricked your phone. At this point warranty would be your best option.
Sent from my SCH-I535 using xda premium
shimp208 said:
If your phone doesn't power on at all no led, no recovery or download access, no vibration even, then I'm afraid by putting the VRALEC.bootchain.tar.md5 in the wrong spot and flashing it through Odin you have hard bricked your phone. At this point warranty would be your best option.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Dude he voided his warranty by rooting so JTAG is best option.
jmxc23 said:
Dude he voided his warranty by rooting so JTAG is best option.
Click to expand...
Click to collapse
Dude...
If anyone at Verizon has any clue why a phone won;t turn on , then you might be right, but they don;t and they don;t have the time to worry with it, so they will just replace it if its less than a year old.
DigitalMD said:
Dude...
If anyone at Verizon has any clue why a phone won;t turn on , then you might be right, but they don;t and they don;t have the time to worry with it, so they will just replace it if its less than a year old.
Click to expand...
Click to collapse
That part is true.
So there's absolutely no way to recover it at this point. I didn't get a warranty on it specifically because I was planning on running Cyanogenmod.
It has a 1 year warranty that Verizon will honor
Sent from my SCH-I535 using xda app-developers app
dsims9t said:
So there's absolutely no way to recover it at this point. I didn't get a warranty on it specifically because I was planning on running Cyanogenmod.
Click to expand...
Click to collapse
No, there is a way to recover it. There just is not a fixable way via xda. Third party services such as MobileTechVideos can fix your phone via jtag as a few others suggest.
dsims9t said:
So there's absolutely no way to recover it at this point. I didn't get a warranty on it specifically because I was planning on running Cyanogenmod.
Click to expand...
Click to collapse
If you don't have a warranty on your device the only other real option is to use JTAG to revive the phone. I would recommend checking out this place that will repair your bricked Galaxy S3 for you.
Seems to be an almost daily occurrence. Reading a new thread because someone can't follow directions and bricking their phone.
Sent from my SCH-I535 using xda premium
bbqsfire said:
Seems to be an almost daily occurrence. Reading a new thread because someone can't follow directions and bricking their phone.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
He was simply asking if it could be fixed, which is kind of what this section is for. I personally would've asked the same question if it happened to me because I haven't seen any questions based on this specific chain of events. He just put the file in the wrong slot, could happen to people, now this specific question will be able to be searched for by people who actually search.
So to answer the question, your bootloader is kind of your essential command for your phone that starts the booting process. You basically erased that with a file that doesn't execute that process. Luckily a jtag is able to rewrite that entire command. I think it's only $60, which is well worth the cost.
Sent from my SCH-I535 using Tapatalk 2
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
I rooted my Verizon gs3 using Saferoot (I think). I dropped the phone and cracked the screen and digitizer (phone will power on but can't see anything on the screen). I've received my insurance replacement phone and have to send the cracked one back. Is there any way to unroot the phone before I return it? I did trade for the phone used so I could plead ignorance and say that the previous owner must have done it if Verizon catches it. TIA
cdput said:
I rooted my Verizon gs3 using Saferoot (I think). I dropped the phone and cracked the screen and digitizer (phone will power on but can't see anything on the screen). I've received my insurance replacement phone and have to send the cracked one back. Is there any way to unroot the phone before I return it? I did trade for the phone used so I could plead ignorance and say that the previous owner must have done it if Verizon catches it. TIA
Click to expand...
Click to collapse
Look for a program that will display your screen through the computer.
Or you could simply flash a stock 4.4.2 rom through download mode, then everything looks like it hasn't been touched. Download mode is easy to get into and you don't need a working screen.
Sent from my HTC6525LVW using Tapatalk
Thanks! I'll have to do some research on getting into download mode or if you can please point me to a guide. I've never flashed a rom to my phone (although I have thought about it). The main thing that I've ever needed has been root to be able to use the wifi tethering.
cdput said:
Thanks! I'll have to do some research on getting into download mode or if you happen to be able to point me to a guide. I've never flashed a rom to my phone (although I have thought about it). The main thing that I've ever needed has been root to be able to use the wifi tethering.
Click to expand...
Click to collapse
Power off phone, then it's power +volume down +home. Once it boots, give it a minute then hit volume up. You can verify you're in download mode if Odin recognizes your phone.
Sent from my HTC6525LVW using Tapatalk
BadUsername said:
Power off phone, then it's power +volume down +home. Once it boots, give it a minute then hit volume up. You can verify you're in download mode if Odin recognizes your phone.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Thanks again! I am a complete noob when it comes to Odin so I'll research. I mess with this type stuff strictly for myself and just to see if I can. So I don't do it often. I normally don't ask questions unless I just can't seem to find the answers on my own.
cdput said:
Thanks again! I am a complete noob when it comes to Odin so I'll research. I mess with this type stuff strictly for myself and just to see if I can. So I don't do it often. I normally don't ask questions unless I just can't seem to find the answers on my own.
Click to expand...
Click to collapse
Check the softbrick repair guide, instructions are completely laid out for you, just make sure you use a 4.4 rom not the included 4.3 rom.
Sent from my HTC6525LVW using Tapatalk
BadUsername said:
Check the softbrick repair guide, instructions are completely laid out for you, just make sure you use a 4.4 rom not the included 4.3 rom.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Thanks so much!