So it seems I've really put myself into a bad spot, here.
I recently rooted my phone (Verizon S3) using towelroot, which seemed to work exceedingly well, so I decided to try to make a NANDroid backup using ClockworkMod. I installed ROM Manager, set that up, and chose the "restart in Clockwork recovery mode option", which didn't work. I soon realized I forgot to unlock my bootloader so, at the recommendation of a few sites, used EZ-Unlock to try to do that. The app reported that it was successful, so I tried restarting my phone in Clockwork recovery mode again. To my utter horror, my phone did not turn on, and has not turned on since.
When I say that it doesn't turn on, I mean that it gives me no audio, vibrational, or visual feedback, almost like there's no battery in the phone. I've pulled the battery and also attempted to do the fix outlined in a video, but to no avail. (I would post the link if the forum allowed me to. The title of the video is "Unbrick hard bricked Verizon Galaxy S3 running 4.3 Jelly Bean")
Feel free to scold me all you like for my irresponsibility and stupidity, it's probably deserved. Any help will be hugely appreciated, though! Thank you so much!
Edit: I guess I should mention that this is my first time doing this sort of thing to an Android device. However, I do like to think I "know my way around", as they say. (although I guess not enough to avoid messing things up!)
Velovix said:
So it seems I've really put myself into a bad spot, here.
I recently rooted my phone (Verizon S3) using towelroot, which seemed to work exceedingly well, so I decided to try to make a NANDroid backup using ClockworkMod. I installed ROM Manager, set that up, and chose the "restart in Clockwork recovery mode option", which didn't work. I soon realized I forgot to unlock my bootloader so, at the recommendation of a few sites, used EZ-Unlock to try to do that. The app reported that it was successful, so I tried restarting my phone in Clockwork recovery mode again. To my utter horror, my phone did not turn on, and has not turned on since.
When I say that it doesn't turn on, I mean that it gives me no audio, vibrational, or visual feedback, almost like there's no battery in the phone. I've pulled the battery and also attempted to do the fix outlined in a video, but to no avail. (I would post the link if the forum allowed me to. The title of the video is "Unbrick hard bricked Verizon Galaxy S3 running 4.3 Jelly Bean")
Feel free to scold me all you like for my irresponsibility and stupidity, it's probably deserved. Any help will be hugely appreciated, though! Thank you so much!
Edit: I guess I should mention that this is my first time doing this sort of thing to an Android device. However, I do like to think I "know my way around", as they say. (although I guess not enough to avoid messing things up!)
Click to expand...
Click to collapse
You need to report your post so it can be moved to the Verizon s3 forums where you can get help for your problem.
Darke5tShad0w said:
You need to report your post so it can be moved to the Verizon s3 forums where you can get help for your problem.
Click to expand...
Click to collapse
Oh, my mistake. I'll do that right away. Thank you!
Velovix said:
Oh, my mistake. I'll do that right away. Thank you!
Click to expand...
Click to collapse
No problems. This is the forum for the International version and we don't have locked bootloaders so you will have more chance in there than you will here.
can you get the phone to go in to download mode? that power+home+vol down
Timothy08 said:
can you get the phone to go in to download mode? that power+home+vol down
Click to expand...
Click to collapse
No, unfortunately, I cannot. I hope I'm not already out of luck.
Velovix said:
No, unfortunately, I cannot. I hope I'm not already out of luck.
Click to expand...
Click to collapse
Was your phone on android 4.3 before you tried to unlock bootloader? If so, that isn't good.
sjpritch25 said:
Was your phone on android 4.3 before you tried to unlock bootloader? If so, that isn't good.
Click to expand...
Click to collapse
Uhh, yes, it was.. Any suggestions?
Velovix said:
Uhh, yes, it was.. Any suggestions?
Click to expand...
Click to collapse
Maybe try looking at the unbrick thread in the q&a?
Velovix said:
Uhh, yes, it was.. Any suggestions?
Click to expand...
Click to collapse
Do what the guy above suggested. Oh just so you know when you are on 4.3 you can not unlock your bootloader. Only root. Also once on 4.3 you can not downgrade to any earlier firmware versions. You can thank Verizon for that.
Sent from my SCH-I535 using Tapatalk
YevOmega said:
Maybe try looking at the unbrick thread in the q&a?
Click to expand...
Click to collapse
If you're referring to "[GUIDE] Debrick your bricked SCH-I535! [BOOTLOADER/HARDBRICK]", I have tried that a few times. I guess I could give it a few more shots if that's my only option.
Sandman-007 said:
Do what the guy above suggested. Oh just so you know when you are on 4.3 you can not unlock your bootloader. Only root. Also once on 4.3 you can not downgrade to any earlier firmware versions. You can thank Verizon for that.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
That's awful. I guess I was looking at a guide for a non-Verzion phone. Thank you for the information, though.
So, if I understand my situation, I guess the question now is: How can I lock my bootloader back up while it's hardbricked, correct?
Velovix said:
So, if I understand my situation, I guess the question now is: How can I lock my bootloader back up while it's hardbricked, correct?
Click to expand...
Click to collapse
No. Your only focus is on getting the phone to boot back up. The only method that we have to do so is the bootloader/hardbrick thread by SpryroDazee posted at the top of our Q/A section.
SlimSnoopOS said:
No. Your only focus is on getting the phone to boot back up. The only method that we have to do so is the bootloader/hardbrick thread by SpryroDazee posted at the top of our Q/A section.
Click to expand...
Click to collapse
Alright, I'll see what I can do. Thanks for the help!
Velovix said:
Alright, I'll see what I can do. Thanks for the help!
Click to expand...
Click to collapse
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-iii-s3-bootloader-downgrade-service/
This might help. Try mobile tech videos. they can Jtag and downgrade for you.
Related
Hey guys,I have a rooted inspire 4g with Jellytime R7 and I turned it on and after the bootanimation It goes into blackness and does nothing....This has happened before but I would simply just factory reset it and all would be good until now...My volume down is broken and I can't get into recovery please help.It would mean a ton
Please help guys!
LogicDeifying said:
Please help guys!
Click to expand...
Click to collapse
A couple things,
1~ The title of your thread is simply to vague. Try re-naming it to something other then I need help.
2~ It is Sunday, you will probably have a better chance of receiving help tomorrow. Please do not bump your own thread you need to have some patients.
Thank you
TonyStark said:
A couple things,
1~ The title of your thread is simply to vague. Try re-naming it to something other then I need help.
2~ It is Sunday, you will probably have a better chance of receiving help tomorrow. Please do not bump your own thread you need to have some patients.
Thank you
Click to expand...
Click to collapse
Ok thank you Stark,Do you have any advise?
LogicDeifying said:
Ok thank you Stark,Do you have any advise?
Click to expand...
Click to collapse
It sounds like you may be having more going on then the rom. From the little you have said, it sounds like your hardware my now be causing additional issues. Have you checked YT for "How to's" for the device?
TonyStark said:
It sounds like you may have more going on then the rom. It sounds like your hardware my now be causing additional issues. Have you checked YT for "How to's" for the device?
Click to expand...
Click to collapse
I have I tried doing this one that un-roots the device with Ace Hack...And It requires Usb Debugging but it's not on...
Frankly I don't see how you are going to get out of this one unless you go in there and find a way to press the vol down button, either by sticking a pin in your phone in that area or opening it up to get it pressed.
You cannot get into Fastboot or Recovery unless you do so.
You did not enable USB debugging so you can't input ADB commands during the boot-loop.
Is there an emergency reset button on this phone? (the HD2 had a small one in the back that could be used to hard reset the phone i believe).
Mine showed similar until I flashed the kernel.
Is it unlocked? S-On? S-off? Have you run a RUU to return to stock get debugging back? Have you tried flashing anything from fastboot? And...have you changed your incredibly undescriptive title?
Hi all.
How can I wipe my Nexus 5 so it is a plain Kit Kat 4.4.2 (like the day I received it) and just root it? it's currently in 4.4.2 and rooted, but with a lot of stuf in it too. My main concern is how to wipe once it's rooted, and how to reroot.
For those who like to read, a little more info:
I have a Nexus 5 which received 2 days ago. I come from an iPhone 5S, so... pretty newbie...
I unlocked the bootloader and rooted the device after unboxing, and have been using it since. Problems are:
1. I just found out about CWM and its capabilities, and I intend to use the backups a lot.
2. I kind of ****ed up with a couple of apps I regret installing.
3. After a backup I just did today, it asked to whether or not fix the recovery (or something like that). Selected YES, nothing happened. It then asked to fix the root... said YES and screwed it completely. I had to put SuperSu in the phone as a ZIP and manually install it again to recover my root access. It kind of looks "dirty" now, lol.
Anyways, I'd like to make a whole device backup from CWM with Kit Kat out of the box, no extra apps installed. Just rooted. Then install all my stuff, sync contacts and so on, and make another backup.
That's why I want to erase the device and have it all clean (just rooted).
Thanks!
Start here http://forum.xda-developers.com/showthread.php?p=47156064
Then go here
http://forum.xda-developers.com/showthread.php?p=47025283
jd1639 said:
Start here http://forum.xda-developers.com/showthread.php?p=47156064
Then go here
http://forum.xda-developers.com/showthread.php?p=47025283
Click to expand...
Click to collapse
Thanks! Can link 2 be replaced with just running CF-Auto-Root? That's what I used the first time and worked great.
rwed said:
Thanks! Can link 2 be replaced with just running CF-Auto-Root? That's what I used the first time and worked great.
Click to expand...
Click to collapse
It can, but I'd recommend you do it per the link.
jd1639 said:
It can, but I'd recommend you do it per the link.
Click to expand...
Click to collapse
Mmm. OK. And why? (Just curious at this point)
rwed said:
Mmm. OK. And why? (Just curious at this point)
Click to expand...
Click to collapse
Because the 2nd method furnishes you with knowledge and experience to help you understand and learn things that cf auto root "automates" for you. Using our recommended method, you will have a head start in knowing how to do things you may need to do to recover your device from various scenarios.
...for example, had you used that method last time - applying logic and knowledge, you may not have created this thread
Sent from my Nexus 5 using Tapatalk
rootSU said:
...for example, had you used that method last time - applying logic and knowledge, you may not have created this thread
Click to expand...
Click to collapse
lol OK. Thanks guys.
I come from iOS after several years. Please bear that in mind.
We're just offering you the benefit of our collective experience. Some of us have been doing this for years so please understand - we're not giving you grief. We have your best interests in mind
Sent from my Nexus 5 using Tapatalk
rootSU said:
We're just offering you the benefit of our collective experience. Some of us have been doing this for years so please understand - we're not giving you grief. We have your best interests in mind
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Oh please, I know. I was just hiding my ignorance under the iOS carpet.
Will give a read to both links tomorrow. Will definitely do link1 on friday if I find the time, and will then consider either doing link2 or going the CF-Auto-Root way.
I'll let you know how this all ends.
Again, thanks!
Update:
Followed steps in link1. Everything went fine.
Gave a deep read to link2. Found it understandable and easy to do and follow, but decided to go the CF-Auto-Root way just because I had done it before and worked nicely...
Everything OK. Something weird happened -again- though. After the clean restore and root, I installed CWM and proceeded to make a backup of the plain system. After it, it asked to fix root again. I had previously said YES, which lead to a broken root, so I said NO this time. Same thing happened!! I lost root and had to manually install SuperSu 1.93 from ZIP in CWM... Why does this happen?
Anyways, I have another question. If one day I decide to restore from this backup I just made, will it be exactly as doing a complete restore following link1?
Thanks!
jd1639 said:
Start here http://forum.xda-developers.com/showthread.php?p=47156064
Then go here
http://forum.xda-developers.com/showthread.php?p=47025283
Click to expand...
Click to collapse
rootSU said:
Because the 2nd method furnishes you with knowledge and experience to help you understand and learn things that cf auto root "automates" for you. Using our recommended method, you will have a head start in knowing how to do things you may need to do to recover your device from various scenarios.
...for example, had you used that method last time - applying logic and knowledge, you may not have created this thread
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Stop using cwm... use twrp or philz which can turn the nag off.
Sent from my Nexus 5 using Tapatalk
rwed said:
Update:
Followed steps in link1. Everything went fine.
Gave a deep read to link2. Found it understandable and easy to do and follow, but decided to go the CF-Auto-Root way just because I had done it before and worked nicely...
Everything OK. Something weird happened -again- though. After the clean restore and root, I installed CWM and proceeded to make a backup of the plain system. After it, it asked to fix root again. I had previously said YES, which lead to a broken root, so I said NO this time. Same thing happened!! I lost root and had to manually install SuperSu 1.93 from ZIP in CWM... Why does this happen?
Anyways, I have another question. If one day I decide to restore from this backup I just made, will it be exactly as doing a complete restore following link1?
Thanks!
Click to expand...
Click to collapse
Flash this in cwm http://d-h.st/YpG. It'll put twrp on
Oh damn it... Really? OK, a couple of quick questions:
1. Did reinstalling SuperSu leave junk in the file system?
2. Will flashing TWRP leave anything either?
My OCD would probably make me restore again if the answer to any of those questions is yes.
rootSU said:
Stop using cwm... use twrp or philz which can turn the nag off.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
jd1639 said:
Flash this in cwm http://d-h.st/YpG. It'll put twrp on
Click to expand...
Click to collapse
rwed said:
Oh damn it... Really? OK, a couple of quick questions:
1. Did reinstalling SuperSu leave junk in the file system?
2. Will flashing TWRP leave anything either?
My OCD would probably make me restore again if the answer to any of those questions is yes.
Click to expand...
Click to collapse
No to both your questions.
jd1639 said:
No to both your questions.
Click to expand...
Click to collapse
Thank you very much!
I just saw that TWRP is in version 5.7.3 in the Play Store. Any reason why you linked to 2.6.3.4? I'm asking because I guess it'll update as soon as I boot. Right?
rwed said:
Thank you very much!
I just saw that TWRP is in version 5.7.3 in the Play Store. Any reason why you linked to 2.6.3.4? I'm asking because I guess it'll update as soon as I boot. Right?
Click to expand...
Click to collapse
Not for the nexus 5. I think you're looking at cwm.
jd1639 said:
Not for the nexus 5. I think you're looking at cwm.
Click to expand...
Click to collapse
I saw it here: https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager
rwed said:
I saw it here: https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager
Click to expand...
Click to collapse
I just looked at it. I'm not sure what that is. The file I linked you to is the latest image from goo.im which is the official twrp depository.
jd1639 said:
I just looked at it. I'm not sure what that is. The file I linked you to is the latest image from goo.im which is the official twrp depository.
Click to expand...
Click to collapse
I'll just install your file, specially if you can't even tell what that thing I linked is. Thank you jd. :good:
rwed said:
Thank you very much!
I just saw that TWRP is in version 5.7.3 in the Play Store. Any reason why you linked to 2.6.3.4? I'm asking because I guess it'll update as soon as I boot. Right?
Click to expand...
Click to collapse
That's the twrp manager. Different things. One is an app and one is a recovery
Sent from my Nexus 5
Hi everyone!
Just a little question, as I'm facing this situation right here:
is there a way to revive a phone that doesn't boot, nor lets me access recovery mode or fastboot or bootloader?
UltimateGoblin said:
Hi everyone!
Just a little question, as I'm facing this situation right here:
is there a way to revive a phone that doesn't boot, nor lets me access recovery mode or fastboot or bootloader?
Click to expand...
Click to collapse
Which phone are you talking about?
I'm talking about the Alcatel V860. It's absolutely an uncommon model, that's the reason why I'm speaking in general.
UltimateGoblin said:
I'm talking about the Alcatel V860. It's absolutely an uncommon model, that's the reason why I'm speaking in general.
Click to expand...
Click to collapse
Please ask specific questions as its related to the phone model. I'm not hopefully about it. You can get it serviced by "bootloader repair" Should be about 40$.
Some of the more common phones can be unbricked on your own.
LS.xD said:
Please ask specific questions as its related to the phone model. I'm not hopefully about it. You can get it serviced by "bootloader repair" Should be about 40$.
Some of the more common phones can be unbricked on your own.
Click to expand...
Click to collapse
I've already posted here, but I received only one answer, so I decided to speak more general just to know if it is theoretically possible to rescue a phone in the situation I described.
Anyway, do you think that there is no way that the pc can communicate with a phone that doesn't even reach the bootloader?
Ok, I'll ask a different question: the phone I'm talking about ended up this bad while flashing an official OTA.
How is that possible?
I thought there was no possible way that an OTA messed with the bootloader, or the recovery... or fastboot! Doesn anyone know what could possibly have gone wrong during the update?
UltimateGoblin said:
Ok, I'll ask a different question: the phone I'm talking about ended up this bad while flashing an official OTA.
How is that possible?
I thought there was no possible way that an OTA messed with the bootloader, or the recovery... or fastboot! Doesn anyone know what could possibly have gone wrong during the update?
Click to expand...
Click to collapse
Actually, it seems like your phone is bricked, there are some methods to unbrick some phones but I don't know if they would work for you, just try to do a Google search how to unbrick a bricked phone, and it might return with some useful stuff, try everything that's possible, because nothing worst can happen over a brick(except it can blast in your hand if you connect a high voltage in place of battery)(lol, it won't happen! )
Hit Thanks if I helped sent from my SM-T211
Already done that, I'm giving up if my pc cannot communicate with the phone.
At this point I'd only like to know how could an OTA corrupt the bootloader.
UltimateGoblin said:
Already done that, I'm giving up if my pc cannot communicate with the phone.
At this point I'd only like to know how could an OTA corrupt the bootloader.
Click to expand...
Click to collapse
Only thing you can do now is, go to store(from where you buy your phone, act dumb and tell them that this won't turn on, they might replace your phone!
Hit Thanks if I helped sent from my SM-T211
Thanks. Anyone else?
UltimateGoblin said:
Thanks. Anyone else?
Click to expand...
Click to collapse
So, what exactly you did?
Hit Thanks if I helped sent from my SM-T211
It wasn't me, it was my cousin, who flashed an OTA which apparently corrupted all the layers of the OS. I believe him, but I find it incredibly difficult to happen, so I wanted to know if that could really happen.
UltimateGoblin said:
It wasn't me, it was my cousin, who flashed an OTA which apparently corrupted all the layers of the OS. I believe him, but I find it incredibly difficult to happen, so I wanted to know if that could really happen.
Click to expand...
Click to collapse
What do you mean by ota corrupting all layers of os?
I never heard of it.
Hit Thanks if I helped sent from my SM-T211
It means that the flashing went bad and now the phone is unusable. I cannot make it communicate with the pc. No access to recovery nor bootloader nor fastboot nor anything.
UltimateGoblin said:
It means that the flashing went bad and now the phone is unusable. I cannot make it communicate with the pc. No access to recovery nor bootloader nor fastboot nor anything.
Click to expand...
Click to collapse
Try smart phone flash tool(on pc), I recently came across a thread in which author said he have a hard bricked xolo phone and it don't boot to anything, but responds to SP Flash tool. Give it a try, if might work.
I don't have it's link, Google it
Hit Thanks if I helped sent from my SM-T211
UltimateGoblin said:
It means that the flashing went bad and now the phone is unusable. I cannot make it communicate with the pc. No access to recovery nor bootloader nor fastboot nor anything.
Click to expand...
Click to collapse
Did that worked?
Sent from my SM-T211 using xda app-developers app
ON: Galaxy S3 4.4.2 Verizon(d2vzw) -->OK, I know you all may think I didn't read the other debrick threads, your wrong. I made this new thread because i HAVE tried endlessy every method of debrick on this forum and the internet, and no success. I was messing around with safestrap and decided to try and flash a rom called flashingdroid: for some reason. So i did as usual, boot into recovery(safestrap 3.75) and wipe current os and flash the new one. So i wiped my stock rom(after making a backup) and installed/flashed the new one(flashingdroid) and after seemingly a successful flash, i pressed reboot. Then it went downhill. One second after i pressed reboot, the screen flashed quickly, then shutoff, for good. I couldn't boot it or get into recovery or odin or ANYTHING. I tried the microsd method of debricking with minimal success. It will only give me one vibration, then black scree with that method. Nothing else has worked. I know this was a noob mistake somehow, but does anyone know any special tricks or something? Will a good jig maybe work? I have doubt verizon or samsung will accept it back(it was well rooted!). Please anything/anybody help! I really don't want to buy a new phone or jtag it. Thanks!:crying:
You may have read the debrick threads, but what you should have done from the beginning was read and pay attention to which forum you were in. You flashed a ROM for the International version of the S3 onto your Verizon S3. You almost certainly turned your phone into a shiny paper weight. JTAG may be your only hope. If you don't have one, check out mobiletechvideos.com. I'm not familiar enough with safestrap to know if that may have actually saved you since it is not a traditional recovery and I don't know if it touches all the partitions. In the future, research, research, and research, and pay very close attention to exactly what you are flashing onto your phone. For the Verizon S3, you should only flash ROMs from this sub-forum. And when using safestrap, you are restricted to only flashing ROMs with the same build number as what your phone is currently on in a stock condition.
Ok...Thanks
landshark68 said:
You may have read the debrick threads, but what you should have done from the beginning was read and pay attention to which forum you were in. You flashed a ROM for the International version of the S3 onto your Verizon S3. You almost certainly turned your phone into a shiny paper weight. JTAG may be your only hope. If you don't have one, check out mobiletechvideos.com. I'm not familiar enough with safestrap to know if that may have actually saved you since it is not a traditional recovery and I don't know if it touches all the partitions. In the future, research, research, and research, and pay very close attention to exactly what you are flashing onto your phone. For the Verizon S3, you should only flash ROMs from this sub-forum. And when using safestrap, you are restricted to only flashing ROMs with the same build number as what your phone is currently on in a stock condition.
Click to expand...
Click to collapse
Im kinda tired of my so confined locked bootloader and phone model anyways. Im going to purchase a $20 JTAG service off ebay, hope that works.
Root Wizard said:
Im kinda tired of my so confined locked bootloader and phone model anyways. Im going to purchase a $20 JTAG service off ebay, hope that works.
Click to expand...
Click to collapse
I'd be very careful with eBay, they tend to be junk. I've been an eBay member over 10 years and ran into a lot of it
Sent from my Nexus 5
Try MicroSD 16GB (2GB not work)
Confused About What's Possible for Modding a Stock Verizon S3
Can someone please steer me in the right direction? I have a Verizon Galaxy S3 running 4.4.2 stock. I recently rooted my phone, but I realize I am very limited as to any mods I can make due to the locked bootloader. Am I able to modify my OS in some way at all (Safestrap) to make my phone run better, or am I just too late in going about this? I've read so much on this subject, but the more I read, it seems the more confused I get. I want to be careful not to brick my phone and would love to see some precise directions on what I could do. Thanks a million for any help at all!
straykat said:
Can someone please steer me in the right direction? I have a Verizon Galaxy S3 running 4.4.2 stock. I recently rooted my phone, but I realize I am very limited as to any mods I can make due to the locked bootloader. Am I able to modify my OS in some way at all (Safestrap) to make my phone run better, or am I just too late in going about this? I've read so much on this subject, but the more I read, it seems the more confused I get. I want to be careful not to brick my phone and would love to see some precise directions on what I could do. Thanks a million for any help at all!
Click to expand...
Click to collapse
You should be able to install xposed but as far as mods your very limited to what you can do with it
Sent from my Nexus 5
ShapesBlue said:
You should be able to install xposed but as far as mods your very limited to what you can do with it
Sent from my Nexus 5
Click to expand...
Click to collapse
Hey, thanks a lot for that! As much as I've read, I've never heard of xposed. I'll research it and see what it takes and what it will do for my phone. If it helps at all, which I'm sure it will, that would be great. Thanks again for your reply!
straykat said:
Hey, thanks a lot for that! As much as I've read, I've never heard of xposed. I'll research it and see what it takes and what it will do for my phone. If it helps at all, which I'm sure it will, that would be great. Thanks again for your reply!
Click to expand...
Click to collapse
Your very welcome. That's what xda is all about. Helping others
Sent from my Nexus 5
XDA Forum - the best place for learning...
ShapesBlue said:
Your very welcome. That's what xda is all about. Helping others
Sent from my Nexus 5
Click to expand...
Click to collapse
ShapesBlue-
It's hard to compare this forum with the others. I believe the people here are the most knowledgeable and, like you, very helpful. Funny enough, or not, I posed a related question on another site (initials AC), and it took over 150 views and a week later before anybody offered a reply. Anyway, I can see there is lots of information on this forum about xposed, so now I'll go and learn as much as I can about it. Thanks again for your help!
Btw, here's a link for others like me who are clueless about xposed: http://forum.xda-developers.com/showthread.php?t=2299428
straykat said:
ShapesBlue-
It's hard to compare this forum with the others. I believe the people here are the most knowledgeable and, like you, very helpful. Funny enough, or not, I posed a related question on another site (initials AC), and it took over 150 views and a week later before anybody offered a reply. Anyway, I can see there is lots of information on this forum about xposed, so now I'll go and learn as much as I can about it. Thanks again for your help!
Btw, here's a link for others like me who are clueless about xposed: http://forum.xda-developers.com/showthread.php?t=2299428
Click to expand...
Click to collapse
I've been around the web going on nearly 20 years and I'd have to agree some are more helpful than others. I find xda to be a great resource for anything android or windows phone related. And yes I agree some are a lot more helpful than others. The guys and gals still lurking around the VZW S3 forums have been here since the beginning for this phone and even though mine is no longer active I still use it daily, mostly for games but will probably never give it up. It was my first true (I'm comparing it to the HTC thunderbolt) android phone
Sent from my Nexus 5
Can't Believe What I - did! - - - Need Help Rebooting Phone
ShapesBlue said:
I've been around the web going on nearly 20 years and I'd have to agree some are more helpful than others. I find xda to be a great resource for anything android or windows phone related. And yes I agree some are a lot more helpful than others. The guys and gals still lurking around the VZW S3 forums have been here since the beginning for this phone and even though mine is no longer active I still use it daily, mostly for games but will probably never give it up. It was my first true (I'm comparing it to the HTC thunderbolt) android phone
Sent from my Nexus 5
Click to expand...
Click to collapse
ShapesBlue-
I seem to have gotten into big trouble - I hope there's a solution. I learned all about Xposed and installed it along with about a dozen modules. Everything was working great, except the torch/flashlight... [I wanted that! ] so, I saw a download for a module on this forum to fix the flashlight... http://forum.xda-developers.com/xposed/modules/xposed-flashlight-fixer-fix-devices-t2867267 . Well, since doing that, I think I realized that I should have left the flashlight alone! When I tried to reboot after adding the module to xposed, I ended up in what i believe is a boot loop. The Samsung screen comes on, and then it gets stuck on the red Verizon screen. I never dreamed that a module installation could cause this; and I guess I figured if it ever happened I could get into recovery mode and restore everthing. Btw, I had done a complete backup of my phone using Titanium on my sd card.
So, here's what I can/can't do now. I can push "down-volume-button" + home + power to get to screen where you can download a cusom OS - then pushing volume-up-button goes to screen that says "Downloading...Do not turn off target!! (Nothing seems to happen from here.) - - - I cannot enter recovery mode by pressing "volume-up" + home + power keys. When I do that I get the big yellow triangle with message - System software not authorized...go to nearest Verizon store. hmmmm.... So, am I hard bricked or soft bricked? Do I have a way out? Thanks very much for any help with this!
straykat said:
ShapesBlue-
I seem to have gotten into big trouble - I hope there's a solution. I learned all about Xposed and installed it along with about a dozen modules. Everything was working great, except the torch/flashlight... [I wanted that! ] so, I saw a download for a module on this forum to fix the flashlight... http://forum.xda-developers.com/xposed/modules/xposed-flashlight-fixer-fix-devices-t2867267 . Well, since doing that, I think I realized that I should have left the flashlight alone! When I tried to reboot after adding the module to xposed, I ended up in what i believe is a boot loop. The Samsung screen comes on, and then it gets stuck on the red Verizon screen. I never dreamed that a module installation could cause this; and I guess I figured if it ever happened I could get into recovery mode and restore everthing. Btw, I had done a complete backup of my phone using Titanium on my sd card.
So, here's what I can/can't do now. I can push "down-volume-button" + home + power to get to screen where you can download a cusom OS - then pushing volume-up-button goes to screen that says "Downloading...Do not turn off target!! (Nothing seems to happen from here.) - - - I cannot enter recovery mode by pressing "volume-up" + home + power keys. When I do that I get the big yellow triangle with message - System software not authorized...go to nearest Verizon store. hmmmm.... So, am I hard bricked or soft bricked? Do I have a way out? Thanks very much for any help with this!
Click to expand...
Click to collapse
No problem. Your soft bricked and it seems your on the latest firmware, correct me if I'm wrong
4.4.2 NE1? If so you can use Odin to flash back to stock 4.4.2 and you should be ok
Sent from my Nexus 5
ShapesBlue said:
No problem. Your soft bricked and it seems your on the latest firmware, correct me if I'm wrong
4.4.2 NE1? If so you can use Odin to flash back to stock 4.4.2 and you should be ok
Sent from my Nexus 5
Click to expand...
Click to collapse
ShapesBlue-
That's great news!!! Thanks!
I believe my phone was on 4.4.3. A file I used in my rooting process using Towelroot was I535VRUDNE1_I535VZWDNE1_VZW; I used Odin before for the root procedure, so the program of course is on my PC. Is there a thread around with instructions how to flash back to the stock firmware? Thanks again a million for getting back to me!
straykat said:
ShapesBlue-
That's great news!!! Thanks!
I believe my phone was on 4.4.3. A file I used in my rooting process using Towelroot was I535VRUDNE1_I535VZWDNE1_VZW; I used Odin before for the root procedure, so the program of course is on my PC. Is there a thread around with instructions how to flash back to the stock firmware? Thanks again a million for getting back to me!
Click to expand...
Click to collapse
But of course. Check this out which should get you what you need
http://forum.xda-developers.com/showthread.php?t=2639337
Sent from my Nexus 5
Try kies
straykat said:
ShapesBlue-
That's great news!!! Thanks!
I believe my phone was on 4.4.3. A file I used in my rooting process using Towelroot was I535VRUDNE1_I535VZWDNE1_VZW; I used Odin before for the root procedure, so the program of course is on my PC. Is there a thread around with instructions how to flash back to the stock firmware? Thanks again a million for getting back to me!
Click to expand...
Click to collapse
Instead of odin, you could try using samasung kies 3 and use its emergencey firmware recovery tool which dl's and intalls the correct, latest firmware on your device.
What you do:
Install kies 3 on your computer.
Boot to odin mode on your phone.
Click on tools in kies.
Select emergency firmware recovery option.
Follow on screen directions.
Hope I helped!
ShapesBlue said:
But of course. Check this out which should get you what you need
http://forum.xda-developers.com/showthread.php?t=2639337
Sent from my Nexus 5
Click to expand...
Click to collapse
Shapes Blue & Root Wizard,
Thanks much for your replies. Is it possible for me, having had 4.4.3 on phone, to go to 4.3 instead of 4.4.2? Seems some people think that's an advantage, but I'm not sure. If I did do that, could I still run xposed?
Btw, RW, I tried using your idea, but when I was attempting to do the emergency Firmware Recovery, it asked for a computer code...??? So, that method doesn't seem to be a good route for me, but thanks for the tip!
You guys don't know how happy I am to have you come to the rescue! I've been using an old iPhone 4 for calls, etc.... during the day which I don't like at all! I'll be real glad to get back to AndroidLand. Thanks again!!!
straykat said:
Shapes Blue & Root Wizard,
Thanks much for your replies. Is it possible for me, having had 4.4.3 on phone, to go to 4.3 instead of 4.4.2? Seems some people think that's an advantage, but I'm not sure. If I did do that, could I still run xposed?
Btw, RW, I tried using your idea, but when I was attempting to do the emergency Firmware Recovery, it asked for a computer code...??? So, that method doesn't seem to be a good route for me, but thanks for the tip!
You guys don't know how happy I am to have you come to the rescue! I've been using an old iPhone 4 for calls, etc.... during the day which I don't like at all! I'll be real glad to get back to AndroidLand. Thanks again!!!
Click to expand...
Click to collapse
I'm 100% sure the last update on the VZW S3 was 4.4.2 NE1. As long as you can root the phone you should be able to run xposed without an issue
And no you cannot downgrade to anything other than what your currently on
Sent from my Nexus 5
---------- Post added at 06:51 PM ---------- Previous post was at 06:50 PM ----------
Root Wizard said:
Instead of odin, you could try using samasung kies 3 and use its emergencey firmware recovery tool which dl's and intalls the correct, latest firmware on your device.
What you do:
Install kies 3 on your computer.
Boot to odin mode on your phone.
Click on tools in kies.
Select emergency firmware recovery option.
Follow on screen directions.
Hope I helped!
Click to expand...
Click to collapse
Kies won't always work as it should
Sent from my Nexus 5
Still Not Up & Running...
ShapesBlue-
Believe-it-or-not, I still haven't been able to get my s3 back up & running. When I open Odin3 v 3.09 and try to flash the firmware 1534VRUDNE1 . . . . .tar.md5 , it doesn't successfully load to the s3. I've attached a screenshot showing the Odin screen. It show "All threads completed. (succeed 0 failed 1) - btw, when I click on the firmware file within Odin, nothing appears in the box to the right of the AP field; is that correct?
Thanks for any guidance you can provide.
straykat said:
ShapesBlue-
Believe-it-or-not, I still haven't been able to get my s3 back up & running. When I open Odin3 v 3.09 and try to flash the firmware 1534VRUDNE1 . . . . .tar.md5 , it doesn't successfully load to the s3. I've attached a screenshot showing the Odin screen. It show "All threads completed. (succeed 0 failed 1) - btw, when I click on the firmware file within Odin, nothing appears in the box to the right of the AP field; is that correct?
Thanks for any guidance you can provide.
Click to expand...
Click to collapse
I can't open it. It's in the newest word format docx. I personally haven't had to do this myself and it's been awhile since I've used Odin. Damn MS having to have all files in there own format
Edit: trying to download docs by Google and seeing if it opens
Sent from my Nexus 5
---------- Post added at 08:48 PM ---------- Previous post was at 08:40 PM ----------
straykat said:
ShapesBlue-
Believe-it-or-not, I still haven't been able to get my s3 back up & running. When I open Odin3 v 3.09 and try to flash the firmware 1534VRUDNE1 . . . . .tar.md5 , it doesn't successfully load to the s3. I've attached a screenshot showing the Odin screen. It show "All threads completed. (succeed 0 failed 1) - btw, when I click on the firmware file within Odin, nothing appears in the box to the right of the AP field; is that correct?
Thanks for any guidance you can provide.
Click to expand...
Click to collapse
Can you get into recovery?
I was able to open it once I downloaded docs by google. It's been so long since I used it though. I can't recall off hand how to use it to be honest
Sent from my Nexus 5
Ok I think I really may have messed up big time with this guys so I'm begging for some help.
]So I just recently bought a AT&T LG G3 on ebay in excellent condition everything worked great until I started experimenting. I rooted it using KingRoot but later decided I'd rather use another method of root because I prefer SuperSu to manage my root access...Anyways to make a long story very short. I needed to get into download mode but Kill Switch had already locked me out because I rooted it..I did not know that McAfee would lock my phone when I rooted.. and so as a last ditch effort I attempted to wipe the entire drive and re-flash the OS well to my surprise that did completely erase the OS as expected but not the Kill Switch. So now im stuck at LG Welcome screen and cant do anything.. I'm at the mercy of the web help PLEASE!!! smh
TriLTorch said:
Ok I think I really may have messed up big time with this guys so I'm begging for some help.
]So I just recently bought a AT&T LG G3 on ebay in excellent condition everything worked great until I started experimenting. I rooted it using KingRoot but later decided I'd rather use another method of root because I prefer SuperSu to manage my root access...Anyways to make a long story very short. I needed to get into download mode but Kill Switch had already locked me out because I rooted it..I did not know that McAfee would lock my phone when I rooted.. and so as a last ditch effort I attempted to wipe the entire drive and re-flash the OS well to my surprise that did completely erase the OS as expected but not the Kill Switch. So now im stuck at LG Welcome screen and cant do anything.. I'm at the mercy of the web help PLEASE!!! smh
Click to expand...
Click to collapse
You can't get passed that. There's no way around it. Only way if it's even possible is to pay a phone store that has a box that might can fix it. But other wise chances are slim
Sent from my iPhone using Tapatalk
hyelton said:
You can't get passed that. There's no way around it. Only way if it's even possible is to pay a phone store that has a box that might can fix it. But other wise chances are slim
Click to expand...
Click to collapse
Dang please dont tell me that I honestly just bought this phone a week ago..heh..Ive rooted and flashed multiple phones in my time but have never seen a "kill switch".
TriLTorch said:
Dang please dont tell me that I honestly just bought this phone a week ago..heh..Ive rooted and flashed multiple phones in my time but have never seen a "kill switch".
Click to expand...
Click to collapse
you can try this.
http://forum.xda-developers.com/spr...very-guide-t3132359/post61280085#post61280085
Jahanzaibawan said:
you can try this.
http://forum.xda-developers.com/spr...very-guide-t3132359/post61280085#post61280085
Click to expand...
Click to collapse
Thank you I will try this!!
TriLTorch said:
Thank you I will try this!!
Click to expand...
Click to collapse
Don't think that will work with the kill switch issue. That is if you loose download mode. But worth a shot.
Sent from my iPhone using Tapatalk
Jahanzaibawan said:
you can try this.
http://forum.xda-developers.com/spr...very-guide-t3132359/post61280085#post61280085
Click to expand...
Click to collapse
This method worked after many hours of trying and trying thank you for this ...unfortunately the phone which was unlock is now locked again and says that it is permanently locked to AT&T.. any Ideas?
TriLTorch said:
This method worked after many hours of trying and trying thank you for this ...unfortunately the phone which was unlock is now locked again and says that it is permanently locked to AT&T.. any Ideas?
Click to expand...
Click to collapse
What do you mean says its permanently locked to AT&T? Screen shot? Is it asking for a sim unlock code?
Sent from my iPhone using Tapatalk
hyelton said:
What do you mean says its permanently locked to AT&T? Screen shot? Is it asking for a sim unlock code?
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Yea the SIM unlock is permanently locked and I havent even had the opportunity to put a unlock code in. After finally getting the Download mode working and getting the OS back on it Dial 2945#*850# to insert unlock code and it says "this phone is permanently locked and can not be unlocked" I haven't even made a wrong attempt at it yet its just already locked.
Jahanzaibawan said:
you can try this.
http://forum.xda-developers.com/spr...very-guide-t3132359/post61280085#post61280085
Click to expand...
Click to collapse
This link worked pretty flawlessly just took a few tries shorting the pins out and plugging in the computer simultaneously but once the phone shows as its plugged into a com port and you have your tot file and dll ready for flash read directions very very carefully and this works great thank you so much!
TriLTorch said:
This link worked pretty flawlessly just took a few tries shorting the pins out and plugging in the computer simultaneously but once the phone shows as its plugged into a com port and you have your tot file and dll ready for flash read directions very very carefully and this works great thank you so much!
Click to expand...
Click to collapse
welcome buddy.?