Related
Would anybody be able to provide any insight on how i could fix my s3 that appears to be stuck on boot? i received my warranty fixed device from samsung today and upon rerooting it, i forgot to unlock the bootloader i then went to the "Verizon has detected unauthorized software" screen. After which, I followed this thread http://forum.xda-developers.com/showthread.php?t=1840030 hoping to get back to stock. But after following these directions, the phone boots to a Samsung custom (Unlocked) screen and then it goes to the galaxy s3 boot screen and remains there, if anybody could provide any assistance, that would be awesome. I'd just hate to get laughed at if i bring it into a verizon store. thanks and happy holidays.
Boot into recovery and do a factory reset.
Sent from my SCH-I535 using Tapatalk 4
SlimSnoopOS said:
Boot into recovery and do a factory reset.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
I've tried that a few times already. No luck thus far
ImBarone said:
Would anybody be able to provide any insight on how i could fix my s3 that appears to be stuck on boot? i received my warranty fixed device from samsung today and upon rerooting it, i forgot to unlock the bootloader i then went to the "Verizon has detected unauthorized software" screen. After which, I followed this thread http://forum.xda-developers.com/showthread.php?t=1840030 hoping to get back to stock. But after following these directions, the phone boots to a Samsung custom (Unlocked) screen and then it goes to the galaxy s3 boot screen and remains there, if anybody could provide any assistance, that would be awesome. I'd just hate to get laughed at if i bring it into a verizon store. thanks and happy holidays.
Click to expand...
Click to collapse
What baseband are you on ?
jlyle said:
What baseband are you on ?
Click to expand...
Click to collapse
i was on vrbmf1 when i got it back but ive been trying to flash back to the stock to hopefully get out of the "unauthorized software" screen. when i tried to wipe system and data and then restart from the stock recovery menu, i got an error message saying that the directory /system didnt exist, yet ive tried flashing back to stock twice and both processes finished through odin
ImBarone said:
i was on vrbmf1 when i got it back but ive been trying to flash back to the stock to hopefully get out of the "unauthorized software" screen. when i tried to wipe system and data and then restart from the stock recovery menu, i got an error message saying that the directory /system didnt exist, yet ive tried flashing back to stock twice and both processes finished through odin
Click to expand...
Click to collapse
Are you 100% sure you was on MF1 and Verizon did not ship it to you with 4.3.
If you was on MF1 Odin should flash fine and resolve any issues. If you was on 4.3 than you have issues if you ran Odin
jlyle said:
Are you 100% sure you was on MF1 and Verizon did not ship it to you with 4.3.
If you was on MF1 Odin should flash fine and resolve any issues. If you was on 4.3 than you have issues if you ran Odin
Click to expand...
Click to collapse
1000% sure that it was 4.1.2 and MF1 because it was trying to push an OTA update that i kept canceling. should i attempt reflashing through odin again? and if so could you link me to something specifically i should flash and possibly some instructions because ive been without a phone for 2 weeks and wouldnt like to wait til october for another one....
thanks
ImBarone said:
Would anybody be able to provide any insight on how i could fix my s3 that appears to be stuck on boot? i received my warranty fixed device from samsung today and upon rerooting it, i forgot to unlock the bootloader i then went to the "Verizon has detected unauthorized software" screen. After which, I followed this thread http://forum.xda-developers.com/showthread.php?t=1840030 hoping to get back to stock. But after following these directions, the phone boots to a Samsung custom (Unlocked) screen and then it goes to the galaxy s3 boot screen and remains there, if anybody could provide any assistance, that would be awesome. I'd just hate to get laughed at if i bring it into a verizon store. thanks and happy holidays.
Click to expand...
Click to collapse
If it was fixed or replaced by Samsung they usually update to newest software before returning it. If it was on 4.3 and you tried to unlock it is now bricked beyond our ability to repair at this time.Can't unlock, flash custom recovery or downgrade to 4.1.2 or lower or it will brick. If was on 4.1.2 just need to Odin stock tar.If it hangs then a Factory reset in stock recovery will usually fix it. Need more info on what build you were actually on when started.
prdog1 said:
If it was fixed or replaced by Samsung they usually update to newest software before returning it. If it was on 4.3 and you tried to unlock it is now bricked beyond our ability to repair at this time.Can't unlock, flash custom recovery or downgrade to 4.1.2 or lower or it will brick. If was on 4.1.2 just need to Odin stock tar.If it hangs then a Factory reset in stock recovery will usually fix it. Need more info on what build you were actually on when started.
Click to expand...
Click to collapse
im completely sure it was NOT 4.3 though. it flashed fine when i ran this http://forum.xda-developers.com/showthread.php?t=2046439 i just forgot to flash the bootloader unlock through recovery so then i tried reflashing stock and now im here. and where could you point me in the direction of a stock tar and some instructions because ive been using the ones on the original thread i linked with no luck
Remove .tar from zip and flash in Odin. If was on MF! it should fix with no more than a factory reset in stock recovery. Then run Beans casual to reroot and unlock.
http://www.androidfilehost.com/?fid=23134718111254196
http://forum.xda-developers.com/showthread.php?t=2332825
prdog1 said:
Remove .tar from zip and flash in Odin. If was on MF! it should fix with no more than a factory reset in stock recovery. Then run Beans casual to reroot and unlock.
http://www.androidfilehost.com/user/settings-dev-files.php?action=show-files&flid=7111#
http://forum.xda-developers.com/showthread.php?t=2332825
Click to expand...
Click to collapse
the androidfilehost link is giving me this
"Access Denied
Sorry!
It looks like you don't have permission to access that folder. Make sure the url you are trying to access is correct.
http://forum.xda-developers.com/showthread.php?p=48799846
If you feel this is in error, please contact us."
Do you get a "PASS" when you run Odin ?. Run the tar from PR and all should be good (Iv ran it many times HA)
ImBarone said:
the androidfilehost link is giving me this
"Access Denied
Sorry!
It looks like you don't have permission to access that folder. Make sure the url you are trying to access is correct.
http://forum.xda-developers.com/showthread.php?p=48799846
If you feel this is in error, please contact us."
Click to expand...
Click to collapse
Try again with this link.
http://www.androidfilehost.com/?fid=23134718111254196
jlyle said:
Do you get a "PASS" when you run Odin ?. Run the tar from PR and all should be good (Iv ran it many times HA)
Click to expand...
Click to collapse
im currently flashing the root66.tar through odin hopefully my problem will be solved afterwards
jlyle said:
Do you get a "PASS" when you run Odin ?. Run the tar from PR and all should be good (Iv ran it many times HA)
Click to expand...
Click to collapse
ok so i no luck with the root66.tar file im going to try the other one now. should i be checking the nand erase all box?
ImBarone said:
ok so i no luck with the root66.tar file im going to try the other one now. should i be checking the nand erase all box?
Click to expand...
Click to collapse
Leave everything in odin as is..dont check or uncheck anything
Make sure u put in PDA
Make sure you have a solid connection with cable .. that will cause issues too
Your in download mode right ? HA / just checking
ImBarone said:
Would anybody be able to provide any insight on how i could fix my s3 that appears to be stuck on boot? i received my warranty fixed device from samsung today and upon rerooting it, i forgot to unlock the bootloader i then went to the "Verizon has detected unauthorized software" screen. After which, I followed this thread http://forum.xda-developers.com/showthread.php?t=1840030 hoping to get back to stock. But after following these directions, the phone boots to a Samsung custom (Unlocked) screen and then it goes to the galaxy s3 boot screen and remains there, if anybody could provide any assistance, that would be awesome. I'd just hate to get laughed at if i bring it into a verizon store. thanks and happy holidays.
Click to expand...
Click to collapse
Boot into download mode and on the screen where the option to continue or restart phone, choose to restart your phone. This worked for me just this morning, for some reason it bypasses the check.
Sent from my SCH-I535 using XDA Premium 4 mobile app
jlyle said:
Leave everything in odin as is..dont check or uncheck anything
Make sure u put in PDA
Make sure you have a solid connection with cable .. that will cause issues too
Click to expand...
Click to collapse
im trying with the stock MF1 file now. left everything checked normally as it always is in odin lets see how this goes. would it be common for a boot to hang on the "Samsung Galaxy s3" screen coming off of odin?
ImBarone said:
im trying with the stock MF1 file now. left everything checked normally as it always is in odin lets see how this goes. would it be common for a boot to hang on the "Samsung Galaxy s3" screen coming off of odin?
Click to expand...
Click to collapse
Odin will reboot your phone.. are you getting Pass in Odin ??
ImBarone said:
im trying with the stock MF1 file now. left everything checked normally as it always is in odin lets see how this goes. would it be common for a boot to hang on the "Samsung Galaxy s3" screen coming off of odin?
Click to expand...
Click to collapse
Yes. It is common for it to reboot but bootloop. Pull battery and then boot into stock recovery and factory reset. Then it should boot.
Hello everyone. I'm beginning to have a few system problems, (their leader being an overheating system). I'm likely going to have to return the device to Verizon. If so, I'll need to return to stock ROM. I'm running 4.3 OTA and have already hardbricked the device once. I know that with the 4.3 OTA update, flashing options have been restricted. I currently can't put phone in recovery mode. I trip the flash counter and get a message about unauthorized firmware being detected.
That being said, given my situation, is there any tried and true method to return the phone to the original out of the box status?
Thank you in advance for your time and knowledge.
TwistedPoet said:
Hello everyone. I'm beginning to have a few system problems, (their leader being an overheating system). I'm likely going to have to return the device to Verizon. If so, I'll need to return to stock ROM. I'm running 4.3 OTA and have already hardbricked the device once. I know that with the 4.3 OTA update, flashing options have been restricted. I currently can't put phone in recovery mode. I trip the flash counter and get a message about unauthorized firmware being detected.
That being said, given my situation, is there any tried and true method to return the phone to the original out of the box status?
Thank you in advance for your time and knowledge.
Click to expand...
Click to collapse
Probably you need to pick the hard brick option, but I give you both:
SOFT BRICK - able to get to download mode
http://forum.xda-developers.com/showthread.php?t=2586319
------------------------------
HARD BRICK - phone not turn on
http://forum.xda-developers.com/showthread.php?t=2581166
buhohitr said:
Probably you need to pick the hard brick option, but I give you both:
SOFT BRICK - able to get to download mode
http://forum.xda-developers.com/showthread.php?t=2586319
------------------------------
HARD BRICK - phone not turn on
http://forum.xda-developers.com/showthread.php?t=2581166
Click to expand...
Click to collapse
I had previously neglected to even attempt to upload the recovery.img. (Huge Oversight). However, I ran it successfully (at least I thought), rebooted the phone into recovery mode and still received same yellow triangle error message.
TwistedPoet said:
I had previously neglected to even attempt to upload the recovery.img. (Huge Oversight). However, I ran it successfully (at least I thought), rebooted the phone into recovery mode and still received same yellow triangle error message.
Click to expand...
Click to collapse
Now if you able to boot into recovery you need to follow the exact steps here:
SOFT BRICK - able to get to download mode
http://forum.xda-developers.com/show....php?t=2586319
Just flash recovery will not fix the issue.
buhohitr said:
Now if you able to boot into recovery you need to follow the exact steps here:
SOFT BRICK - able to get to download mode
http://forum.xda-developers.com/show....php?t=2586319
Just flash recovery will not fix the issue.
Click to expand...
Click to collapse
http://forum.xda-developers.com/show....php?t=2586319 - (Dead Link....404 Error)
Please pardon my ignorance but those instructions don't appear to be helpful for restoring the ability to turn the phone on in recovery mode or for getting the phone back to 4.1.2 firmware. Again, please forgive my inability to grasp this.
TwistedPoet said:
http://forum.xda-developers.com/show....php?t=2586319 - (Dead Link....404 Error)
Please pardon my ignorance but those instructions don't appear to be helpful for restoring the ability to turn the phone on in recovery mode or for getting the phone back to 4.1.2 firmware. Again, please forgive my inability to grasp this.
Click to expand...
Click to collapse
That's because there's no way to go back, you are stuck on the 4.3 update.
All you can run is stock 4.3 firmware. It's literally posted everywhere in these forums, and if you searched first you would have found all the answers you needed before you started flashing things that will brick your phone.
This is what you have to do to get a functioning phone again:
http://forum.xda-developers.com/showthread.php?t=2586319
After that, read everything here to understand what you're limited to and what can be safely flashed to the 4.3 update:
http://forum.xda-developers.com/showthread.php?t=2639337
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
That's because there's no way to go back, you are stuck on the 4.3 update.
All you can run is stock 4.3 firmware. It's literally posted everywhere in these forums, and if you searched first you would have found all the answers you needed before you started flashing things that will brick your phone.
This is what you have to do to get a functioning phone again:
http://forum.xda-developers.com/showthread.php?t=2586319
After that, read everything here to understand what you're limited to and what can be safely flashed to the 4.3 update:
http://forum.xda-developers.com/showthread.php?t=2639337
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for that but the title of my post should have indicated that I have done some significant searching. I've already restored the phone to working condition. It was the EZ Unlocker that bricked me. I did neglect in my joy of returning my phone from the dead to flash the recovery.img. I flashed it today and am still unable to get recovery mode. I'm following the SoftBrick guide that buhohitr posted and I'm hoping that I don't find myself in a bootloop afterwards. The second link you provided is very thorough and informative. I bookmarked it for future reference.
At last I got to know lot of things from this thread as I'm new to this trade.
TwistedPoet said:
Thanks for that but the title of my post should have indicated that I have done some significant searching. I've already restored the phone to working condition. It was the EZ Unlocker that bricked me. I did neglect in my joy of returning my phone from the dead to flash the recovery.img. I flashed it today and am still unable to get recovery mode. I'm following the SoftBrick guide that buhohitr posted and I'm hoping that I don't find myself in a bootloop afterwards. The second link you provided is very thorough and informative. I bookmarked it for future reference.
Click to expand...
Click to collapse
Update - With some very helpful guides and a little but of explanation, I was able to return to stock ROM, which returned my ability to boot into recovery mode. I also successfully flashed Safe strap Recovery onto my device. After looking at the guide about which custom ROM's can be flashed onto the phone, I'm considering using one but I am a tad hesitant. I know very very little about framework, kernels and modules. So, I guess we'll see. Thanks for the simply excellent links and your time!!!!!
Hello guys. I have a Galaxy S3 (Verizon). Specifically, a SCH-I535. It is running Android 4.3. It has been rooted before, when it had 4.2, but after I did the update, I still have the SU app, but I can't use it because im not rooted. (I think) So hypothetically, say I wanted to install CyanogenMod. Could I? If so, what version? I have Android 4.3. Is it still possible to root? Thanks for any help.
bio4554 said:
Hello guys. I have a Galaxy S3 (Verizon). Specifically, a SCH-I535. It is running Android 4.3. It has been rooted before, when it had 4.2, but after I did the update, I still have the SU app, but I can't use it because im not rooted. (I think) So hypothetically, say I wanted to install CyanogenMod. Could I? If so, what version? I have Android 4.3. Is it still possible to root? Thanks for any help.
Click to expand...
Click to collapse
You can root 4.3 using saferoot, but you cannot flash CyanogenMod or any other AOSP based ROMs. You can only flash 4.3 Touchwiz ROMs using safestrap. You need to be on the ML1 version of 4.3, not the NC1 version. Everything you need to know can be found in the below linked thread:
http://forum.xda-developers.com/showthread.php?t=2639337
landshark68 said:
You can root 4.3 using saferoot, but you cannot flash CyanogenMod or any other AOSP based ROMs. You can only flash 4.3 Touchwiz ROMs using safestrap. You need to be on the ML1 version of 4.3, not the NC1 version. Everything you need to know can be found in the below linked thread:
http://forum.xda-developers.com/showthread.php?t=2639337
Click to expand...
Click to collapse
\
Ok so my next question, how do I tell if I have NC1, or ML1? Also, will this void my warranty? It says Saferoot will not. Sorry, im such a noob.
bio4554 said:
\
Ok so my next question, how do I tell if I have NC1, or ML1? Also, will this void my warranty? It says Saferoot will not. Sorry, im such a noob.
Click to expand...
Click to collapse
Go to your about phone screen and look at your baseband version and build number and see what the last 3 characters are. And your warranty is only good for 1 year from the original date of purchase, which I would assume has long since passed. So I wouldn't worry about this voiding your warranty.
landshark68 said:
Go to your about phone screen and look at your baseband version and build number and see what the last 3 characters are. And your warranty is only good for 1 year from the original date of purchase, which I would assume has long since passed. So I wouldn't worry about this voiding your warranty.
Click to expand...
Click to collapse
Ok thanks so much! I have rooted my phone after flashing ML1, and now I was wondering if I could install CWM Recovery? If so, how? Thanks for all the help.
bio4554 said:
Ok thanks so much! I have rooted my phone after flashing ML1, and now I was wondering if I could install CWM Recovery? If so, how? Thanks for all the help.
Click to expand...
Click to collapse
Check out my first response to you in this thread. You cannot install any kind of custom recovery on ML1. Safestrap is basically your custom recovery. Click on the link in my first response and read up. In the thread I linked you will find a link about Safestrap and a bunch of information you will need.
landshark68 said:
Check out my first response to you in this thread. You cannot install any kind of custom recovery on ML1. Safestrap is basically your custom recovery. Click on the link in my first response and read up. In the thread I linked you will find a link about Safestrap and a bunch of information you will need.
Click to expand...
Click to collapse
Ok, so basically I installed Safestrap, Rooted, and all was well. Then I went and looked for some custom Touchwiz ROMs, and found this one.
CoolROM 8 Core Edition
I downloaded it, created a new ROM slot on Safestrap, flashed it to the phone with safestrap, then rebooted. First off, the Samsung logo that appears right when you turn on, with the open padlock, is gone. For a split second, a white line appears. Then it goes to the Safestrap, I hit continue, it does first boot like normal, and gets stuck on the samsung logo again. "The last one before android appears". I pulled battery, rebooted. Same as first time, except it booted into android. The setup appears, and now another problem pops up. I cant turn on WiFi. It says turned off, I press the toggle button, but it doesnt turn to the ON state. Please help! I really want to use CleanROM!
bio4554 said:
Ok, so basically I installed Safestrap, Rooted, and all was well. Then I went and looked for some custom Touchwiz ROMs, and found this one.
CoolROM 8 Core Edition
I downloaded it, created a new ROM slot on Safestrap, flashed it to the phone with safestrap, then rebooted. First off, the Samsung logo that appears right when you turn on, with the open padlock, is gone. For a split second, a white line appears. Then it goes to the Safestrap, I hit continue, it does first boot like normal, and gets stuck on the samsung logo again. "The last one before android appears". I pulled battery, rebooted. Same as first time, except it booted into android. The setup appears, and now another problem pops up. I cant turn on WiFi. It says turned off, I press the toggle button, but it doesnt turn to the ON state. Please help! I really want to use CleanROM!
Click to expand...
Click to collapse
Look in the OP of the safestrap thread. Every time you flash a ROM though safestrap you have to also flash the kernel modules in the same flashing session in order for WiFi to work.
landshark68 said:
Look in the OP of the safestrap thread. Every time you flash a ROM though safestrap you have to also flash the kernel modules in the same flashing session in order for WiFi to work.
Click to expand...
Click to collapse
Omg thank you so much landshark,you have helped me so much. I now have a rooted S3 with Safestrap, and CleanROM 8.1. Everything is working fine. Now my final question(probably not), is there any possible way at all to unlock the bootloader on this thing? If not, is there anyone working on something like that? If not at all, that's ok. Im still satisfied with it so far. Thanks again. Also, on Safestrap, after I hit continue it has a kind of delay before the boot animation is shown(AKA it starts up). Is there any way to change this?
bio4554 said:
Omg thank you so much landshark,you have helped me so much. I now have a rooted S3 with Safestrap, and CleanROM 8.1. Everything is working fine. Now my final question(probably not), is there any possible way at all to unlock the bootloader on this thing? If not, is there anyone working on something like that? If not at all, that's ok. Im still satisfied with it so far. Thanks again. Also, on Safestrap, after I hit continue it has a kind of delay before the boot animation is shown(AKA it starts up). Is there any way to change this?
Click to expand...
Click to collapse
Not possible at all to unlock the bootloader, you are stuck with it. As far as I know, no one is working on trying to figure out a way to unlock the bootloader. All attempts at finding an exploit to unlock the bootloader have not had any success. The bootloader on the S4 was locked down in the same way before the S3, and that hasn't been cracked yet either.
As far as changing the delay on start up with safestrap, best to ask that question in the safestrap thread as I have never used safestrap and just read the thread to stay informed.
All,
I got myself into a bit of pickle and could use some advice.
First, device information:
Nexus 5 Hammerhead D821(E)
Hw version rev_11
Bootloader version HHZ11k
Secure boot enabled
lock state unlocked
I think it's 4.4.2 or 4.4.3. I haven't installed KitKat.
Also running some xposed modules and Teamwin recovery but haven't flashed a rom or kernel
The issue
About an hour ago I got into the com.android.systemui. The screen keeps flashing and I'm lucky if I can power off the device. No chance of starting an app or getting into settings. When the device is powered up I can not access file folders through Explorer, in bootloader the device is not even recognized.
I figure I need to do a factory reset but seeing that I can't reach settings I don't know how to do this exactly (I assume it's OK to do with a rooted device that's still running the custom ROM?) Should I do it through TWRP? And if so, how do I proceed? I've read a few threads that deal with similar issues but I haven't found a manual that I feel fits completely which make some uncomfortable to try.
Thanks very much in advance,
T
Also, I just found this one: http://forum.xda-developers.com/goo...l-06-03-14-one-click-factory-restore-t2513937
Would that be the right way to go?
First of all there isn't such thing as a "soft brick" It's either bricked or it's not.
You said you haven't "installed KitKat", well 4.4.x is KK. You sure you know what you're doing?
I suggest you see the first link of my signature and read some threads before you proceed with doing anything further to your device. You should be able to reflash factory images.
Lethargy said:
First of all there isn't such thing as a "soft brick" It's either bricked or it's not.
You said you haven't "installed KitKat", well 4.4.x is KK. You sure you know what you're doing?
I suggest you see the first link of my signature and read some threads before you proceed with doing anything further to your device. You should be able to reflash factory images.
Click to expand...
Click to collapse
Thanks for the swift reply Lethargy,
I referred to softbrick as in I can still boot but it gets into a loop I can't get out of. Apologies for the confusion re KitKat, I meant I hadn't installed 4.4.4.
I actually just ran the One click recover in the thread I mentioned and it worked like a charm, can use the phone again so marking this as solved!
Taeglian said:
Thanks for the swift reply Lethargy,
I referred to softbrick as in I can still boot but it gets into a loop I can't get out of. Apologies for the confusion re KitKat, I meant I hadn't installed 4.4.4.
Click to expand...
Click to collapse
That would be a "bootloop" or non-boot, not a "soft-brick".
Taeglian said:
I actually just ran the One click recover in the thread I mentioned and it worked like a charm, can use the phone again so marking this as solved!
Click to expand...
Click to collapse
Cool. But I do still suggest you have a look at various threads in the first link of my signature to learn a little more.
Hi, I got an old Galaxy S3 to play around with today and I think I may have bricked it. It was on the latest 4.4.2 build and I attempted to downgrade it to unlock the bootloader. Obviously, it didn't work but I though I would just be able to flash back to stock. I have tried every tutorial I can find but I can not get back to stock. When flashing in ODIN it always fails. kies never connects to the device, and the Verizon repair tool doesn't detect the device.
When I try to boot the phone it says "firmware upgrade encountered an issue. Please use software repair assistant & try again"
I am still able to boot into download mode.
Does anyone have any idea how to fix this?
mpalomba3 said:
Hi, I got an old Galaxy S3 to play around with today and I think I may have bricked it. It was on the latest 4.4.2 build and I attempted to downgrade it to unlock the bootloader. Obviously, it didn't work but I though I would just be able to flash back to stock. I have tried every tutorial I can find but I can not get back to stock. When flashing in ODIN it always fails. kies never connects to the device, and the Verizon repair tool doesn't detect the device.
When I try to boot the phone it says "firmware upgrade encountered an issue. Please use software repair assistant & try again"
I am still able to boot into download mode.
Does anyone have any idea how to fix this?
Click to expand...
Click to collapse
If you are using Odin in attempts to flash stock 4.4.2 and that is failing I am at a loss. If Odin flashes of 4.3 are failing, then I would say use 4.4.2. I doubt you need to try debrick images, if one is available for the i535, since you can boot into download mode. I don't have any info about the VZW repair tool or Kies, I haven't used them.
http://forum.xda-developers.com/showthread.php?t=1734949
dawgdoc said:
If you are using Odin in attempts to flash stock 4.4.2 and that is failing I am at a loss. If Odin flashes of 4.3 are failing, then I would say use 4.4.2. I doubt you need to try debrick images, if one is available for the i535, since you can boot into download mode. I don't have any info about the VZW repair tool or Kies, I haven't used them.
Click to expand...
Click to collapse
landshark68 said:
http://forum.xda-developers.com/showthread.php?t=1734949
Click to expand...
Click to collapse
Thanks, I managed to figure out the problem. I thought I was flashing 4.4.2 images but I was actually flashing 4.3 images. I downloaded the latest image and managed to flash it in Odin without a problem.
Thanks again for responding