Related
Got my Desire S back from repair with a mainboard replacement. Replaced as updating multiple apps seems to have fired it. Under warranty.
New board is noticeably cooler when running for hours on WIFI.
What I notice is they've also formatted the MMC card, and I can only see 4 basic folders there, all empty.
I don't see a backup image etc.
Is this correct?
If I have to hard reset, is there a hidden image on there somewhere, or do I have to get one etc.
It's not rooted and s-on, where it will stay due to warranty, or at least until I am sure the Mainboard can stand up to a lot of multitasking etc.
Bump:
Anyone?
DDesires said:
Got my Desire S back from repair with a mainboard replacement. Replaced as updating multiple apps seems to have fired it. Under warranty.
New board is noticeably cooler when running for hours on WIFI.
What I notice is they've also formatted the MMC card, and I can only see 4 basic folders there, all empty.
I don't see a backup image etc.
Is this correct?
If I have to hard reset, is there a hidden image on there somewhere, or do I have to get one etc.
It's not rooted and s-on, where it will stay due to warranty, or at least until I am sure the Mainboard can stand up to a lot of multitasking etc.
Click to expand...
Click to collapse
The only reason that a backup image would have existed on you MMC is if you S-OFF'd and rooted your phone and previously took a Nandroid backup using either CWM recovery or ROM manager.
The fact that one doesn't exist now isn't a problem, as if your intending on keeping your warranty in tact you will no longer be able to take any further backups and wouldn't have the permissions to restore any previous/old backups
you can ultimately format your MMC card and android will re-create any files of directories that it needs to use on it.
This is correct - So stop worrying!
Thanks for that, just the info I was looking for. Didn't quite get that HTC didn't store a backup image on the MMC card before
i understand that you have pull out an in the battery and you fried your emmc chip
how much cost the reparation? did the guaranty cover the cost?
because i have the same problem but i hat gone a little further whit the flashing and rooming stuff.
I have a NS4G from Sprint that I recently upgraded to the oICS43 rom from AOSP. While playing around with some of the settings I decided that I was going to encrypt the phone, as I'm a bit of a geek about security as well as the fact that there's quite often client information and such on my phone, so it would be nice to keep people locked out if I ever lose it or it gets stolen. Well, it started up a little dialog that flipped by before I was able to read it and then it went to the boot animation (the one with all of the colors going across the screen.) I figured that this was just what it was going to do during this process, but it's been going on for over an hour and a half and I'm starting to get worried. I know that it says that it can take over an hour, but this just seems really weird that it would have people sit there for that long with no sort of warning about not powering down your phone, no progress bar, etc. If any of you have encrypted your phone please let me know if this is what things are supposed to be looking like at this point. I do have a lot of stuff on the phone (12gb of the 16 filled, about 375 apps installed) so I understand that mine would probably take a little bit longer than normal, so really I'm hoping to just get some reassurance here.
TIA
P.S. Would there be any way to have ADB let me know what's going on right now with the phone? If so, what would the commands for that be?
Update: Over 2 hours now...same screen. What do you guys think that I should do, keep waiting or just pull the battery?
unfortunately seems you're the only one look for encryption on your phone, but i'll follow up, seems interesting to me
I've come to the conclusion that it was some kind of failure, now I pulled the battery and I'm in the process of getting everything back to working.
Well, getting everything back up and running was a huge PITA. I'm going to actually try to figure out what happened, though, just so that I can report back. I had to reformat and wipe everything on the phone, and the phone itself couldn't mount the /sdcard. I had to have CWM mount the /sdcard and then reformat it from Windows.
Somebody else posted that encryption completely fubared their phone yesterday. That thread is probably in the Nexus General Forum.
Snt frm my Nxs S 4G sng xd prm
After getting the phone back up and running (you have to go and individually format each section, as well as factory reset and wipe both caches, then mount the /sdcard in windows and format that way from CWM because it won't be able to mount /sdcard) I was able to start fresh with oICS43 and the phone is now currently encrypting itself successfully. It takes a LONG time, as it's 83% done after 45 minutes. Just so that anybody that's curious about it knows, you'll see a screen that says "Encrypting" across the top with a little jigsaw puzzle android guy on the screen. If you just see the flowing colors boot splash that means you just fudged up your phone.
I will pay FIFTY DOLLARS ($50.00) to the person or team that provides a solution to this problem.
After swapping batteries in my Droid Charge, I often (but not always) get a huge number of force close crashes when it boots up. The apps that usually force close on reboot are Google Docs, FlexT9 keyboard, GoSMS Pro and App Protector.
My phone is running Imnuts's Infinity Rom 1211, plus his battery addin and his widgets. However, this problem also existed when I was running Gummy Charged 2.1.
I own several batteries. In fact, I own seven of them. I have a drop-in charger at home, at work and in my car. There's always at least one fresh battery at all locations. I mention this because I realize that there is something about "battery stats" that you can wipe (using CWM Recovery). Maybe the phone is not smart enough to keep track of so many unique batteries?
When I swap a battery and then I get an a~~load of force close crashes, the phone will come up as though the ROM had just been installed. It asks me for my Google Account info just like it was being configured for the very first time.
When this happens, I have to reconfigure my two Google accounts (home and work), let it resync all the data on those two accounts, then reinstall many applications.
I asked about this once when I was still running Gummy Charged and the suggestion came back that it was a software issue that could most easily be remedied by changing to a newer ROM. The poster said that Gummy Charged wasn't being actively supported anymore, but Infinity was and suggested I go that route.
Q. -- What sort of process / event related to swapping batteries (or merely rebooting) could cause the phone to come up like it's never been configured before?
Whenever I install a ROM, I always wipe the Dalvik Cache and wipe the internal SD (but not the 32 gb removable SD card). Whenever I move from one ROM to another ROM, I always fall back to factory stock first. Any time I installed Infinity ROM, I received no errors of any kind (and same for when I installed other ROMs in the past).
When my phone works correctly, I really like the Droid Charge. When it doesn't, I want to take a large cache of weapons and ammunition to a postal facility. I can't tolerate this any longer. I have to solve the problem (forever) or I have to give up and buy another phone.
FIFTY BUCKS BY PAYPAL FOR THE SOLUTION.
SoonerLater said:
I will pay FIFTY DOLLARS ($50.00) to the person or team that provides a solution to this problem.
After swapping batteries in my Droid Charge, I often (but not always) get a huge number of force close crashes when it boots up. The apps that usually force close on reboot are Google Docs, FlexT9 keyboard, GoSMS Pro and App Protector.
My phone is running Imnuts's Infinity Rom 1211, plus his battery addin and his widgets. However, this problem also existed when I was running Gummy Charged 2.1.
I own several batteries. In fact, I own seven of them. I have a drop-in charger at home, at work and in my car. There's always at least one fresh battery at all locations. I mention this because I realize that there is something about "battery stats" that you can wipe (using CWM Recovery). Maybe the phone is not smart enough to keep track of so many unique batteries?
When I swap a battery and then I get an a~~load of force close crashes, the phone will come up as though the ROM had just been installed. It asks me for my Google Account info just like it was being configured for the very first time.
When this happens, I have to reconfigure my two Google accounts (home and work), let it resync all the data on those two accounts, then reinstall many applications.
I asked about this once when I was still running Gummy Charged and the suggestion came back that it was a software issue that could most easily be remedied by changing to a newer ROM. The poster said that Gummy Charged wasn't being actively supported anymore, but Infinity was and suggested I go that route.
Q. -- What sort of process / event related to swapping batteries (or merely rebooting) could cause the phone to come up like it's never been configured before?
Whenever I install a ROM, I always wipe the Dalvik Cache and wipe the internal SD (but not the 32 gb removable SD card). Whenever I move from one ROM to another ROM, I always fall back to factory stock first. Any time I installed Infinity ROM, I received no errors of any kind (and same for when I installed other ROMs in the past).
When my phone works correctly, I really like the Droid Charge. When it doesn't, I want to take a large cache of weapons and ammunition to a postal facility. I can't tolerate this any longer. I have to solve the problem (forever) or I have to give up and buy another phone.
FIFTY BUCKS BY PAYPAL FOR THE SOLUTION.
Click to expand...
Click to collapse
are all these batteries OEM (Samsung made for the Charge) ones? I wouldn't know even where to begin for a fix as I've never heard of this before... the only issue I could see would be if they were third party batteries but even then they wouldn't crash the system they would just maybe not charge unless in a separate battery charger
Please use the Q&A Forum for questions Thanks
Moving to Q&A
anoninja118 said:
are all these batteries OEM (Samsung made for the Charge) ones?
Click to expand...
Click to collapse
Yep. Every one of them is the real McCoy, made by Samsung and either purchased from the local Verizon store or from Amazon (not an Amazon vendor, but from Amazon itself).
SoonerLater said:
I will pay FIFTY DOLLARS ($50.00) to the person or team that provides a solution to this problem.
After swapping batteries in my Droid Charge, I often (but not always) get a huge number of force close crashes when it boots up. The apps that usually force close on reboot are Google Docs, FlexT9 keyboard, GoSMS Pro and App Protector.
My phone is running Imnuts's Infinity Rom 1211, plus his battery addin and his widgets. However, this problem also existed when I was running Gummy Charged 2.1.
I own several batteries. In fact, I own seven of them. I have a drop-in charger at home, at work and in my car. There's always at least one fresh battery at all locations. I mention this because I realize that there is something about "battery stats" that you can wipe (using CWM Recovery). Maybe the phone is not smart enough to keep track of so many unique batteries?
When I swap a battery and then I get an a~~load of force close crashes, the phone will come up as though the ROM had just been installed. It asks me for my Google Account info just like it was being configured for the very first time.
When this happens, I have to reconfigure my two Google accounts (home and work), let it resync all the data on those two accounts, then reinstall many applications.
I asked about this once when I was still running Gummy Charged and the suggestion came back that it was a software issue that could most easily be remedied by changing to a newer ROM. The poster said that Gummy Charged wasn't being actively supported anymore, but Infinity was and suggested I go that route.
Q. -- What sort of process / event related to swapping batteries (or merely rebooting) could cause the phone to come up like it's never been configured before?
Whenever I install a ROM, I always wipe the Dalvik Cache and wipe the internal SD (but not the 32 gb removable SD card). Whenever I move from one ROM to another ROM, I always fall back to factory stock first. Any time I installed Infinity ROM, I received no errors of any kind (and same for when I installed other ROMs in the past).
When my phone works correctly, I really like the Droid Charge. When it doesn't, I want to take a large cache of weapons and ammunition to a postal facility. I can't tolerate this any longer. I have to solve the problem (forever) or I have to give up and buy another phone.
FIFTY BUCKS BY PAYPAL FOR THE SOLUTION.
Click to expand...
Click to collapse
have you tried flashing back to stock rom and keeping it that way for a day or two seeing if that made a difference?
*edit* i did read that you do flash back to stock but i dont know if you automatically flashed back to the other ROM without trying it out first
The solution is make a full backup of your apps and data (use mybackup or titanium. I used mybackup since it's faster and it only show your installed apps, not the system apps). Odin stock EP4d and Pit files then boot up to normal screen. Shutdown and Odin either TweakStock + kernel or Tweakstock with immosey kernel if you want Ext4 lagfix. If you're using Mybackup, first restore data, reboot, then restore apps. You should be good to go. I had this issue before, after done all above, I'm currently use all kind of batteries with all kind of different voltages without any problem (1600mah, 1800mah, 3500mah, 3600mah). I swapped them in and out everyday without issue. Good luck. Just want to help you out.
buhohitr said:
The solution is make a full backup of your apps and data (use mybackup or titanium. I used mybackup since it's faster and it only show your installed apps, not the system apps). Odin stock EP4d and Pit files then boot up to normal screen. Shutdown and Odin either TweakStock + kernel or Tweakstock with immosey kernel if you want Ext4 lagfix. If you're using Mybackup, first restore data, reboot, then restore apps. You should be good to go. I had this issue before, after done all above, I'm currently use all kind of batteries with all kind of different voltages without any problem (1600mah, 1800mah, 3500mah, 3600mah). I swapped them in and out everyday without issue. Good luck. Just want to help you out.
Click to expand...
Click to collapse
yea that about sums it up
but fyi im having issues with the flash player on tweakstock and i dont know if it is just mine,
if you dont really use the flash player then go for it, its a great rom
ferny_dx said:
have you tried flashing back to stock rom and keeping it that way for a day or two seeing if that made a difference?
*edit* i did read that you do flash back to stock but i dont know if you automatically flashed back to the other ROM without trying it out first
Click to expand...
Click to collapse
I flash back to stock. Let it boot. Verify that it seems to be running ok, then I flash the custom rom on top of it. I don't go back to stock and then run stock for a day or two. I'm back on stock for... about... ten minutes.
I don't completely 100% wipe the phone, since to install a new rom, I use Clockwork Mod which reads the new rom from a zip file on the internal memory. If I wiped the phone, then the zip wouldn't be there to install. I suppose that I could use ODIN to install the rom instead, but installing from a zip using CWM is so easy by comparison to Odin.
I don't wipe the 32gb external SD card -- ever. I suppose that there could be some sort of latent flaw in the card that might be remedied by reformatting the external SD card, then rewriting all the data. However, if it had a flaw, I wonder why it would only become evident when the phone reboots.
I don't know, but I assume that the phone keeps "battery stats" on different batteries (that they have some sort of unique identifier that is read by the phone so it can tell one battery from another). If that's the case.... I wonder... do I simply have more batteries than any moderately sane human has? Do I have so many batteries that I've exposed a flaw in the operating system when it tries to keep track of more batteries than it's designed for?
buhohitr said:
The solution is make a full backup of your apps and data (use mybackup or titanium. I used mybackup since it's faster and it only show your installed apps, not the system apps). Odin stock EP4d and Pit files then boot up to normal screen. Shutdown and Odin either TweakStock + kernel or Tweakstock with immosey kernel if you want Ext4 lagfix. If you're using Mybackup, first restore data, reboot, then restore apps. You should be good to go. I had this issue before, after done all above, I'm currently use all kind of batteries with all kind of different voltages without any problem (1600mah, 1800mah, 3500mah, 3600mah). I swapped them in and out everyday without issue. Good luck. Just want to help you out.
Click to expand...
Click to collapse
You're the first person I've found that had a similar problem. I'll go to Tweakstock tonight and report back. Thank you for your help. I note your just want to help you out and I appreciate the generosity of your time.
SoonerLater said:
I flash back to stock. Let it boot. Verify that it seems to be running ok, then I flash the custom rom on top of it. I don't go back to stock and then run stock for a day or two. I'm back on stock for... about... ten minutes.
I don't completely 100% wipe the phone, since to install a new rom, I use Clockwork Mod which reads the new rom from a zip file on the internal memory. If I wiped the phone, then the zip wouldn't be there to install. I suppose that I could use ODIN to install the rom instead, but installing from a zip using CWM is so easy by comparison to Odin.
I don't wipe the 32gb external SD card -- ever. I suppose that there could be some sort of latent flaw in the card that might be remedied by reformatting the external SD card, then rewriting all the data. However, if it had a flaw, I wonder why it would only become evident when the phone reboots.
I don't know, but I assume that the phone keeps "battery stats" on different batteries (that they have some sort of unique identifier that is read by the phone so it can tell one battery from another). If that's the case.... I wonder... do I simply have more batteries than any moderately sane human has? Do I have so many batteries that I've exposed a flaw in the operating system when it tries to keep track of more batteries than it's designed for?
Click to expand...
Click to collapse
i dont think so, the FCs shouldn't have anything to do with the battery thats something else completely in my opinion,
I would say give it a shot on stock rom, just restart it a few times see if there are still FCs
do you use the ALL-IN-ONE file to flash it?
---------- Post added at 11:36 AM ---------- Previous post was at 11:31 AM ----------
how ive fixed most isssues on my Charge has involved flashing files from this thread
http://forum.xda-developers.com/showthread.php?t=1111486
just find what version you want download the PIT and put them in odin,
i don't know if you should or not but i have a habit of taking out my sd just in case
i uncheck all of the options except for re-partition and i have have a completely stock phone
i do lose all contacts and such which should be backed up prior to this process, although im pretty sure you know that
How are you shutting down the phone? through the power menu, holding down power, pulling battery...
It seems all your FC issues are of apps that normally run in background. An improper shutdown could corrupt the file while it's reading/writing.
Sent from my SCH-I510 using xda premium
ferny_dx said:
yea that about sums it up
but fyi im having issues with the flash player on tweakstock and i dont know if it is just mine,
if you dont really use the flash player then go for it, its a great rom
Click to expand...
Click to collapse
flash player issue fixed heres the thread
http://forum.xda-developers.com/showthread.php?p=21536370#post21536370
SoonerLater said:
I flash back to stock. Let it boot. Verify that it seems to be running ok, then I flash the custom rom on top of it. I don't go back to stock and then run stock for a day or two. I'm back on stock for... about... ten minutes.
I don't completely 100% wipe the phone, since to install a new rom, I use Clockwork Mod which reads the new rom from a zip file on the internal memory. If I wiped the phone, then the zip wouldn't be there to install. I suppose that I could use ODIN to install the rom instead, but installing from a zip using CWM is so easy by comparison to Odin.
I don't wipe the 32gb external SD card -- ever. I suppose that there could be some sort of latent flaw in the card that might be remedied by reformatting the external SD card, then rewriting all the data. However, if it had a flaw, I wonder why it would only become evident when the phone reboots.
I don't know, but I assume that the phone keeps "battery stats" on different batteries (that they have some sort of unique identifier that is read by the phone so it can tell one battery from another). If that's the case.... I wonder... do I simply have more batteries than any moderately sane human has? Do I have so many batteries that I've exposed a flaw in the operating system when it tries to keep track of more batteries than it's designed for?
Click to expand...
Click to collapse
Same here, check out my collections
fc after battery swap
Galaxy Note
I find my battery is pretty loose, and it has dropped out on me a couple times and if the phone is running it force closes everything on boot and requires a flash to even become useable again.
Wyrez said:
Galaxy Note
I find my battery is pretty loose, and it has dropped out on me a couple times and if the phone is running it force closes everything on boot and requires a flash to even become useable again.
Click to expand...
Click to collapse
Wrong forum
Sent from my handheld Linux computer using electromagnetic radiation.
Charge Note
I had the same thing happen to me once. Both removed and inserted batteries were stock. It was last fall sometime, so I prolly was on an infinity build. Maybe. Anyhow, you're not alone. Except for the frequency I have this notion that perhaps I did not let it fully power down, but I can't say for sure. Fortunately, it only happened the one time. I only data wiped reflashed in cwm, titanium, blah blah blah, and that was it.
A Note Sent from my SCH-I510 using Tapatalk 2
Fix permissions? lol
s3 turning off randomly requiring battery pull to restart. here is the breakdown to date problem occured,verizon tech sent replacement phone, that phone did it so sent it back and kept original phone, replaced sims card, problem still there, replaced battery, problem still there replaced phone again, still there, replaced sims card and battery again,guess what phone is still shutting off randomly, stock rom,factory mode (no apps)nothing not even email linked all software ota up to date. all is documented by verizon and and sumsung but everytime i talk to them all i get is the same old we can send you a like new phone after all the resets and ect., i dont want another s3 that is reman wich i know does they same thing and i didnt really want to exchange what i thought was the best for a droid wich verizon wants to do and sammy wants to send reman. i have already had two other reman phones that do the same thing. now here is the kicker i own 3 total s3's and now guess what one of the other is doing it now too. is there anybody else having this problem? is there a way to track what is running when it shuts down?would a different kerrnel help? would a different rom help? could this be my account with verizon? any help at all i dont know what to do?
more info
i am starting to think this is a problem with the screen not waking up and staying dark and not necessarly shutting down. any ideas on ways to check this?
coop245 said:
i am starting to think this is a problem with the screen not waking up and staying dark and not necessarly shutting down. any ideas on ways to check this?
Click to expand...
Click to collapse
Try another rom although it sounds like an app. Can't be the phone on that many of them. You only one reporting this problem so has to be something you are putting on phone.
prdog1 said:
Try another rom although it sounds like an app. Can't be the phone on that many of them. You only one reporting this problem so has to be something you are putting on phone.
Click to expand...
Click to collapse
both phones are doing this on stock. no apps installed
My friend had 8 replacements through verizon before he got a good one. So try a couple more times maybe. I know it is really inconvenient but honestly the GS3 is the best Android on Verizon right now (arguably atleast) and they probably won't let you trade up to a Razr HD Maxx which is the only one I would recommend.
I'm having the same problem apparently. I just bought this phone used and activated it monday night. That night, i plugged the phone into the charger while i slept and the phone shut off overnight. Phone wouldnt turn on with the power button - required a battery pull to restart.
Going through tuesday, the phone worked fine. However, in the evening, the phone was idle for a few hours, and when I went to check it before going to bed I found it had powered off again! Required another battery pull to restart...plugged it into the charger, and went to sleep. When I woke up, I again found (for the third time) that the phone had powered down, and required another battery pull to restart.
Going into wednesday, phone is working fine. Then I leave it idle in the afternoon for a few hours during work, and when I get ready to drive home, I find it is again powered down, requiring a battery pull to restart (fourth time in less than 2 days).
Now I go to visit verizon, and the rep tells me (after I think he was looking through some company forums for answers) that I should try clearing the cache from every app, since maybe the data was corrupted during my OTA update to JB (which i installed monday night), and some app was causing this problem. So I do that, and the same thing happens again overnight...battery pull etc...
I'm figuring next I'm going to do a factory data reset, possibly tonight. This is supposed to be my sister's christmas gift! Hah...trying to work the bugs out before tuesday. Any thoughts?
Starting a post with I'm not crazy sound like something a crazy person would say.... just saying.... But I agree with the earlier post that it could be app or rom based and only effecting the screen. These are the options I see you having:
1. Try freezing any apps you've installed one at a time and see if it stops
2. Make nandriod and try another rom and then come back if that doesnt fix it
3. Try this thread to clear everything and upgrade http://forum.xda-developers.com/showthread.php?t=1984436
-This method formats internal and external sd card AND bumps you up to rooted JB in the process. Use VRBLK3.
4. Get a replacement phone
KjK89 said:
Starting a post with I'm not crazy sound like something a crazy person would say.... just saying.... But I agree with the earlier post that it could be app or rom based and only effecting the screen. These are the options I see you having:
1. Try freezing any apps you've installed one at a time and see if it stops
2. Make nandriod and try another rom and then come back if that doesnt fix it
3. Try this thread to clear everything and upgrade http://forum.xda-developers.com/showthread.php?t=1984436
-This method formats internal and external sd card AND bumps you up to rooted JB in the process. Use VRBLK3.
4. Get a replacement phone
Click to expand...
Click to collapse
These options might work for the OP, but only #4 could work for me since i'm not rooting this phone (its for my sister). If I find a fix for my issue, i'll post here.
Are you guys using an sd card? If so it might be a corrupt file that the system goes over and gets stuck on, messing the cell up. Did you try making a backup on pc, formating your card (fat32) and putting you stuff back on it? Or take the card out and see if you get the same problem without it. If you're going thru all the replacements then its gotta be something that you use in common with all of em. GL!
Hello everyone, I've enjoyed my sgs3 for several years now a few months after its release. It's been through hell and back but has worked never skipping a beat until about a week ago.
The screen suddenly became non-responsive. I'm thinking the digitizer is probably bad or something. Someone recommended restoring the factory rom via odin as a last resort. Although I doubt this will work, because not only was I unable to unlock the phone in the rom, I also was unable to unlock twrp. This leads me to believe digitizer issues. Now I could buy the digitizer with a screen for about 65 dollars or just buy a used sgs3 for a few more bucks from swappa. The problem is I don't have those few bucks to spend. Hell I'm on selectel's cheapest non-data plan for goodness sake.
I have successfully put MB1 back on the phone via odin. However this replaces the stock recovery, and I am unable to wipe data in the stock recovery because you must use the power button to select the options. I ripped that out over a year ago when it was causing me problems with random rebooting. I did all I could to keep the power button going using several methods, which worked for a while but eventually I pulled the damn thing out. I realize I could take apart the phone solder two wires to the board and use that for a makeshift switch but I don't want to go through that in all honesty.
What do you experts here think? Is it now junk ready to be sold for scrap or given away, or does anyone know of a way to wipe data so I can at least get it to boot and maybe just maybe salvage this thing? I just bought a nice new hybrid case about 2 days before this occurred for about 4 bucks because my case was falling apart..
I'd like to be able to wipe data/cache from odin, or somehow use adb from the odin screen. Stock recovery isn't an option and I can't for the life of me get TWRP or CWM touch to flash. I don't know why but it fails every time. I've read and read until I'm blue in the face, and there's a sticky here in this section about using the sdcard to unbrick phones, but my pc doesn't have a card reader so that's a no go too.
Thanks in advance
griz.droidx said:
Hello everyone, I've enjoyed my sgs3 for several years now a few months after its release. It's been through hell and back but has worked never skipping a beat until about a week ago.
The screen suddenly became non-responsive. I'm thinking the digitizer is probably bad or something. Someone recommended restoring the factory rom via odin as a last resort. Although I doubt this will work, because not only was I unable to unlock the phone in the rom, I also was unable to unlock twrp. This leads me to believe digitizer issues. Now I could buy the digitizer with a screen for about 65 dollars or just buy a used sgs3 for a few more bucks from swappa. The problem is I don't have those few bucks to spend. Hell I'm on selectel's cheapest non-data plan for goodness sake.
I have successfully put MB1 back on the phone via odin. However this replaces the stock recovery, and I am unable to wipe data in the stock recovery because you must use the power button to select the options. I ripped that out over a year ago when it was causing me problems with random rebooting. I did all I could to keep the power button going using several methods, which worked for a while but eventually I pulled the damn thing out. I realize I could take apart the phone solder two wires to the board and use that for a makeshift switch but I don't want to go through that in all honesty.
What do you experts here think? Is it now junk ready to be sold for scrap or given away, or does anyone know of a way to wipe data so I can at least get it to boot and maybe just maybe salvage this thing? I just bought a nice new hybrid case about 2 days before this occurred for about 4 bucks because my case was falling apart..
I'd like to be able to wipe data/cache from odin, or somehow use adb from the odin screen. Stock recovery isn't an option and I can't for the life of me get TWRP or CWM touch to flash. I don't know why but it fails every time. I've read and read until I'm blue in the face, and there's a sticky here in this section about using the sdcard to unbrick phones, but my pc doesn't have a card reader so that's a no go too.
Thanks in advance
Click to expand...
Click to collapse
Hmm, not sure, can you get the phone to boot? You have touch access still?
You could simply reroot the thing without touching the phone at all, then use Odin to flash twrp to your phone once it's rooted. Before you can use adb you have to activate debugging, which is impossible without being able to use the touch screen.
There is no adb command for what you're asking for. However, it's possible through fastboot. But I don't think we ever got fastboot to work for the S3. It's a specific bootloader menu similar to download mode.
If you cant do it in an easy way, I'd suggest getting another phone.
Thanks, yeah, I'm not going to repair it when I can buy one for 69-70 or get a better one for a little more. I'm not crazy about some of the newer devices being locked down so hard or not having removable batteries or sd card slots. I know they exist. Guess I'll have to do some homework if it comes to that. The touch access is the issue along with not having the power button, and no it won't boot. It goes past two boot images, static images, then loops during the boot ani. I've let it sit for about 10 minutes. This should be plenty of time.
Thanks for the reply
griz.droidx said:
Thanks, yeah, I'm not going to repair it when I can buy one for 69-70 or get a better one for a little more. I'm not crazy about some of the newer devices being locked down so hard or not having removable batteries or sd card slots. I know they exist. Guess I'll have to do some homework if it comes to that. The touch access is the issue along with not having the power button, and no it won't boot. It goes past two boot images, static images, then loops during the boot ani. I've let it sit for about 10 minutes. This should be plenty of time.
Thanks for the reply
Click to expand...
Click to collapse
sounds like you're doing everything you can.
As a last ditch effort to give your phone a bit of life, you could just load the newest version. Sure it'll lock your phone and you won't be able to unlock it anymore, but if you load all the latest software it'll be completely stock. I'm sure it'll boot up then, then you can see exactly what you have to work with.
Thanks for the reply again, I think I'm going to stick with MB1 for now. I don't want to lock it up at the moment. Although I doubt the experience could be that much different, better in some ways and worse in others by doing that, I prefer freedom if I can keep it. ha ha. Master Cylinder has mentioned a few more things to try and should they work, I'll post the results here.
I did use a paper clip to activate a data cache wipe in stock recovery since I don't have a power button. This was the first time I needed the button in over a year, I was going to solder two pieces of wire to use as a power button but my soldering iron is shot.
thanks again