Update The likely culprit, at least for the "install button" problem, appears to be an app called Velis Auto Brightness. A little over three weeks after this problem first arose, I switched my ROM to Dandroid. In deciding what apps gradually to add back, I ran across comments like the following for Velis:
Cannot press install from an APK Found a bug that needs fixing. With this app enabled for some reason installing from an APK it renders the Install button useless but the cancel button still works. As soon as I disabled this App, the Install button worked again.
Click to expand...
Click to collapse
Nice, but one slight issue I really like this app. Very useful and easy to use. My only issue is that when the app is active, if I turn off system auto brightness and try to raise the brightness, Velis overrides this and forces auto brightness.
Click to expand...
Click to collapse
Recently, I had problems with my S3, on which I'd been running Stockorama v2. Starting July 3, the install button stopped working. The eventual solution, alas, was only temporary. I restored a June 27 nandroid and reinstalled apps, except for one that I suspected of causing the problem because it had only recently been installed before the problem occurred,
That worked for almost three weeks, until the phone function stopped working. Whatever telephone number I entered, the phone tried to call 333223. At that point, I had available to me a phone that couldn't make, but could receive, calls or, if I restored a different nandroid, a phone the seemingly functioned fully, except that I could not install any app that required pressing the on-screen install button.
From reading the latter thread and general considerations, I decided to do a clean reinstall of Stockorama. First, I wiped everything and used Odin to install mrRobinson's root66. I wiped again and used mobile Odin to install Stockorama v2. Before doing so, I backed up IMEI and EFS.
Reinstalling Stockorama was frustrating because the Aroma installer kept hanging. Late last night (early this morning), the installer completed. Leaving the phone plugged in to an electric outlet, I went to bed with the screen displaying "Samsung Galaxy SIII." I figured that, come morning, I'd be able to complete the process of setting up the phone.
Instead, I have some kind of brick. When I awoke and checked the phone, the screen had the same display as when I went to bed. Foolishly, perhaps, I thought that pressing the power button might help. It didn't.
Now, although the phone was continuously plugged in, pressing the power button first does nothing or, eventually displays a completely discharged battery with no indication that the phone is charging.
Pressing the power button just now with the phone unplugged again displayed "Samsung Galaxy SIII." FWIW, I've plugged the phone back in.
What to do next is a mystery to me, however.
As always, all advice is appreciated.
I managed to get into Download mode and am using Odin to install, again, root66. Assuming that succeeds, I expect I could use baby-step guidance to prepare the phone for and, once again, install Stockorama. Alternatively, at this point I'd consider another custom ROM that, like Stockorama, is lean and close to stock.
RebDovid said:
I managed to get into Download mode and am using Odin to install, again, root66. Assuming that succeeds, I expect I could use baby-step guidance to prepare the phone for and, once again, install Stockorama. Alternatively, at this point I'd consider another custom ROM that, like Stockorama, is lean and close to stock.
Click to expand...
Click to collapse
1) Aroma is notorious for freezing. Until the recent update, it could, at times, be pretty much unusable. This is not a problem with your device. The new update seems to have fixed those problems, but since Stockorama has not been updated, it is still using the old version.
2) Your issues sound a lot like malware (can't install, can't make outgoing calls). I'm not familiar with any Android malware, but crippling the phone's main functions seems like a good target.
3) You flashed root66 with Odin. Then go on to say you used Mobile ODIN to flash Stockorama. This would imply that your root66 setup was functioning before you flashed Stockorama. Is this true, or have I misunderstood you?
4) Describe to me your "complete wipe" process. Are you using the stock recovery's factory reset? Are you manually wiping the system partition as well? If not stock, what custom recovery are you using, and what version?
5) When you get stuck on the splash screen, you need to factory reset. But, going from one TW ROM to another TW ROM would not require this usually, and could be indicative of another issue. Like bad hardware.
6) If root66 is fine, and you are blaming the ROM, you could go for another one. I personally use S3Rx. I would try Dandroid if it had Wifi Calling. Don't see the point in using TW if I can't have Wifi Calling. Sorry. It's actually pretty handy to have with T-Mobile's less than stellar coverage when out of the city.
7) What firmware are you running? It's an educated guess that you are trying to use the MD5 root66, but what about your bootloader, baseband, rpm, rz, sbl? What versions are those?
Aerowinder said:
1) Aroma is notorious for freezing. Until the recent update, it could, at times, be pretty much unusable. This is not a problem with your device. The new update seems to have fixed those problems, but since Stockorama has not been updated, it is still using the old version.
Click to expand...
Click to collapse
Understood
2] Your issues sound a lot like malware (can't install, can't make outgoing calls). I'm not familiar with any Android malware, but crippling the phone's main functions seems like a good target.
Click to expand...
Click to collapse
You may be right. But I use both Lookout and Avast.
3) You flashed root66 with Odin. Then go on to say you used Mobile ODIN to flash Stockorama. This would imply that your root66 setup was functioning before you flashed Stockorama. Is this true, or have I misunderstood you?
Click to expand...
Click to collapse
Yes, root66 appeared to be functioning. I signed into my Google accounts; reinstalled Root Checker; checked root; and reinstalled Mobile ODIN.
4) Describe to me your "complete wipe" process. Are you using the stock recovery's factory reset? Are you manually wiping the system partition as well? If not stock, what custom recovery are you using, and what version?
Click to expand...
Click to collapse
It was late last night, and I didn't write down my steps. (My bad.) So far as I can recall, from the current TWRP recovery I checked all the available wipe boxes. After wiping, I then went into Download mode, connected the phone to my pc, started Odin, added root66 as the PDA, and clicked start.
I'm not sure what you mean by manually wiping the system.
In installing Stockorama, I chose the full wipe option.
5) When you get stuck on the splash screen, you need to factory reset. But, going from one TW ROM to another TW ROM would not require this usually, and could be indicative of another issue. Like bad hardware.
Click to expand...
Click to collapse
What kind of hardware problem could I have? How do I check?
6) If root66 is fine, and you are blaming the ROM, you could go for another one. I personally use S3Rx. I would try Dandroid if it had Wifi Calling. Don't see the point in using TW if I can't have Wifi Calling. Sorry. It's actually pretty handy to have with T-Mobile's less than stellar coverage when out of the city.
Click to expand...
Click to collapse
I'm not blaming the ROM. I'm simply at a loss.
Why do you use S3Rx? What do you like and dislike about it?
7) What firmware are you running? It's an educated guess that you are trying to use the MD5 root66, but what about your bootloader, baseband, rpm, rz, sbl? What versions are those?
Click to expand...
Click to collapse
I don't know what all the acronyms stand for. But this is what I can tell you.
From "About device," I'm running Android version 4.1.2 and Baseband version T999UVDMD5. The Kernel version is
3.0.31-1128078
[email protected] #2
SMP PREEMPT Mon Apr 15 11:59:10 KST
2013
The Build number is JZ054K.T999UVDMD5
RebDovid said:
Understood
You may be right. But I use both Lookout and Avast.
Yes, root66 appeared to be functioning. I signed into my Google accounts; reinstalled Root Checker; checked root; and reinstalled Mobile ODIN.
It was late last night, and I didn't write down my steps. (My bad.) So far as I can recall, from the current TWRP recovery I checked all the available wipe boxes. After wiping, I then went into Download mode, connected the phone to my pc, started Odin, added root66 as the PDA, and clicked start.
I'm not sure what you mean by manually wiping the system.
In installing Stockorama, I chose the full wipe option.
What kind of hardware problem could I have? How do I check?
I'm not blaming the ROM. I'm simply at a loss.
Why do you use S3Rx? What do you like and dislike about it?
I don't know what all the acronyms stand for. But this is what I can tell you.
From "About device," I'm running Android version 4.1.2 and Baseband version T999UVDMD5. The Kernel version is
3.0.31-1128078
[email protected] #2
SMP PREEMPT Mon Apr 15 11:59:10 KST
2013
The Build number is JZ054K.T999UVDMD5
Click to expand...
Click to collapse
This may not be the case on android, but I know on pc having mulyiple av programs causes all sorts of fun problems! Personally, I don't think any android av apps are worth anything.
Anytime you get hung up at the splash screen, you have to factory reset. If this were hw related it would do this regardless of your rom. And just to clarify, when moving between touchwiz roms, this can happen when when you go backwards from something like MD5 to LJA. This doesn't always happen, but it does happen.
Manually wiping means going into recovery and choosing wipe/format system before flashing your rom.
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
This may not be the case on android, but I know on pc having mulyiple av programs causes all sorts of fun problems! Personally, I don't think any android av apps are worth anything.
Anytime you get hung up at the splash screen, you have to factory reset. If this were hw related it would do this regardless of your rom. And just to clarify, when moving between touchwiz roms, this can happen when when you go backwards from something like MD5 to LJA. This doesn't always happen, but it does happen.
Manually wiping means going into recovery and choosing wipe/format system before flashing your rom.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I failed again with Stockorama. To get a working phone, I restored my root66 nandroid.
At all relevant times, I've been on MD5.
I wonder whether I should try:
(a) restoring stock and trying (i) Stockorama or (ii) S3Rx; or
(b) installing S3Rx.
Before trying either, or something else, I'll pull the PIT file for you. Please just give me instructions.
Related
I just entered the world of a rooted phone, all exciting and new. I used triangle away, and everything is well. I even turned off the debugging mode as i thought i was all done with things rooting and didn't need it.
The next day I realize there is update for supersu, so i accept, if gives me two choices in the update, i choose one, and now my phone is the in GTN7100 loop non stop. Seems of the two options, I choose wrongly. I can put it into download mode. I think I can put it into recovery mode too.
I used this method to boot.
galaxy-note2.wonderhowto.com/how-to/root-your-samsung-galaxy-note-2-using-odin-for-windows-so-easy-your-grandma-can-do-it-0146884
I did perform some basic backups with kies and i believe an app called my backup, so in the worst case, I believe i can recover everything if had to do some kind of reset that would erase all the data. (I am hoping to avoid that, as the recovery may be a learning process if any challenges with it)
its with 4.1.2 and I am not sure if any other details I should provide. so i feel proud i got this far, sad the supersu update made some kind of corruption. i know you guys may be extremely busy and i thank you so much in advance.
Try getting into recovery (CMW or Philz touch) and re-flash a ROM?
thank you bunglebp
bunglebp said:
Try getting into recovery (CMW or Philz touch) and re-flash a ROM?
Click to expand...
Click to collapse
Thank you so much for your reply bunglebp.
I believe I had the CMW when i rooted. Reflashing the ROM won't lose the data, or will? This is new territory for me, so I am going step be step.
Volume up - home - power, i think i understand this far. I just don't want to make any mistakes and follow to a T to bring the phone back up with least work at it if possible.
Macguyer2000 said:
Thank you so much for your reply bunglebp.
I believe I had the CMW when i rooted. Reflashing the ROM won't lose the data, or will? This is new territory for me, so I am going step be step.
Volume up - home - power, i think i understand this far. I just don't want to make any mistakes and follow to a T to bring the phone back up with least work at it if possible.
Click to expand...
Click to collapse
Yes your description of how to get into recovery is correct. But your description of your situation is light on details, hard to get a clear picture, but I feel your pain!
If you have a ROM sitting on your phone that you can reflash in recovery, do it. You won't lose any media on your internal memory e.g. pictured, movies. All your app settings will remain if you don't wipe anything in recovery prior to flashing - but in your situation I suggest a full wipe & reset to (hopefully) clear out any problems.
As for upgrading SU, I'm wondering what you mean by two options? Let us know how you get on. Also feel free to PM me if you're truly stuck, I've been there myself and received help that saved me untold stress.
tweeny80 said:
Yes your description of how to get into recovery is correct. But your description of your situation is light on details, hard to get a clear picture, but I feel your pain!
If you have a ROM sitting on your phone that you can reflash in recovery, do it. You won't lose any media on your internal memory e.g. pictured, movies. All your app settings will remain if you don't wipe anything in recovery prior to flashing - but in your situation I suggest a full wipe & reset to (hopefully) clear out any problems.
As for upgrading SU, I'm wondering what you mean by two options? Let us know how you get on. Also feel free to PM me if you're truly stuck, I've been there myself and received help that saved me untold stress.
Click to expand...
Click to collapse
When I was welcomed to update supersu, it had a left choice (normal) and a right side choice cwm/twrp (not sure the spelling) I choose the right.
I really want to first thank you so so much.
Which options within the recovery should i choose?
When I did try to repeat the original root process, I got a PIT message that just stayed and did not change. I was on slow machine, but I think it was because the debug usb was off or as i was starting to hear, the partition might be changed in the rooting process? Not sure how that would relate. likely because the debug was off
The pain and fear that broke the phone is really intense. Plus, I use it all the time, before this happened. what information do you need?
Macguyer2000 said:
When I was welcomed to update supersu, it had a left choice (normal) and a right side choice cwm/twrp (not sure the spelling) I choose the right.
I really want to first thank you so so much.
Which options within the recovery should i choose?
When I did try to repeat the original root process, I got a PIT message that just stayed and did not change. I was on slow machine, but I think it was because the debug usb was off or as i was starting to hear, the partition might be changed in the rooting process? Not sure how that would relate. likely because the debug was off
The pain and fear that broke the phone is really intense. Plus, I use it all the time, before this happened. what information do you need?
Click to expand...
Click to collapse
My assumptions are you were successfully rooted, I'm unsure if you are on stock ROM or custom ROM, you updated SU and ended up in bootloop. You are able to get into recovery - do you have a ROM already sitting on your phone, that you can flash/install? If yes, do that. But first, in recovery look for options named factory reset, do that. You suggested you have CWM recovery - there is option to wipe cache, then under advanced option, is wipe dalvik cache, do those. I hope I adequately described the menu structure, my phone is not with me right now to check.
Really, we just want to get you back into a functioning ROM, and stop the bootloops. As for updating SU, I assume you tried updating from recovery? If so, stick to the Play Store updates only.
Again lemme know how you get on, and confirm my assumptions so I can help further if needed.
tweeny80 said:
My assumptions are you were successfully rooted, I'm unsure if you are on stock ROM or custom ROM, you updated SU and ended up in bootloop. You are able to get into recovery - do you have a ROM already sitting on your phone, that you can flash/install? If yes, do that. But first, in recovery look for options named factory reset, do that. You suggested you have CWM recovery - there is option to wipe cache, then under advanced option, is wipe dalvik cache, do those. I hope I adequately described the menu structure, my phone is not with me right now to check.
Really, we just want to get you back into a functioning ROM, and stop the bootloops. As for updating SU, I assume you tried updating from recovery? If so, stick to the Play Store updates only.
Again lemme know how you get on, and confirm my assumptions so I can help further if needed.
Click to expand...
Click to collapse
[If you don't already have it, download and install the Samsung USB Drivers. Now, download and unzip the GalaxyNote2Root.zip file. Open the ODIN program by double-clicking the odin3 v1.85.exe application file.] from the website i followed. with this catchy title:
How to Root Your Samsung Galaxy Note 2 Using ODIN for Windows (So Easy Your Grandma Can Do It)
and it rooted with no problem...just that boot loop the next day when updating supersu...and using the google only site is a good idea.
I am having trouble to get the recovery mode on. I can go into download mode easily, but to go into recovery appears to be a trickier issue. I just can't get it. Can you guide me on this....
Simply reflash rom and reroot again.
Flashing stock rom won't erase data. So if after flashing rom device boot up normally, tour data will be there intact, incase it doesn't boot normally after flashing rom then you may need to wipe it.
Sent from my GT-N7100 using xda premium
Macguyer2000 said:
I just entered the world of a rooted phone, all exciting and new. I used triangle away, and everything is well. I even turned off the debugging mode as i thought i was all done with things rooting and didn't need it.
The next day I realize there is update for supersu, so i accept, if gives me two choices in the update, i choose one, and now my phone is the in GTN7100 loop non stop. Seems of the two options, I choose wrongly. I can put it into download mode. I think I can put it into recovery mode too.
I used this method to boot.
galaxy-note2.wonderhowto.com/how-to/root-your-samsung-galaxy-note-2-using-odin-for-windows-so-easy-your-grandma-can-do-it-0146884
I did perform some basic backups with kies and i believe an app called my backup, so in the worst case, I believe i can recover everything if had to do some kind of reset that would erase all the data. (I am hoping to avoid that, as the recovery may be a learning process if any challenges with it)
its with 4.1.2 and I am not sure if any other details I should provide. so i feel proud i got this far, sad the supersu update made some kind of corruption. i know you guys may be extremely busy and i thank you so much in advance.
Click to expand...
Click to collapse
Just to let you know I have used both sources of available update for super su.
And have never had any problems, I highly doubt your boot loop is anything todo with the su update. The guus on here at xda are superb and will have you back up and running no problem.
GT N7105 with XDA Premium......that is all......
bearusa said:
Just to let you know I have used both sources of available update for super su.
And have never had any problems, I highly doubt your boot loop is anything todo with the su update. The guus on here at xda are superb and will have you back up and running no problem.
GT N7105 with XDA Premium......that is all......
Click to expand...
Click to collapse
thank you for the positive thinking. but I think I have a serious problem here.
I can not get into recovery, as much as i try.
Before all this happened, i unticked usb debug.
I can however get into download mode.
I really feel that i have critically wounded my phone.
Macguyer2000 said:
thank you for the positive thinking. but I think I have a serious problem here.
I can not get into recovery, as much as i try.
Before all this happened, i unticked usb debug.
I can however get into download mode.
I really feel that i have critically wounded my phone.
Click to expand...
Click to collapse
Enter download mode and reflash the recovery using odin. Unticking debug should not put your phone into bootloop neither. . You have to make sure your flashing the correct recovery or rom for your phone model. Depending if you have n7100 or n7105..
GT N7105 with XDA Premium......that is all......
bearusa said:
Enter download mode and reflash the recovery using odin. Unticking debug should not put your phone into bootloop neither. . You have to make sure your flashing the correct recovery or rom for your phone model. Depending if you have n7100 or n7105..
GT N7105 with XDA Premium......that is all......
Click to expand...
Click to collapse
OK, let me make sure I understand correctly..I can put some of my fears/worries to rest.
Let me restate
My situation is a bootloop.
My usb debugging is off. (the day after the rooting, I didn't think I needed it on anymore, as I completed the root)
Later that day, just moment before the loop happened, I was updating SuperSu. (something the phone didn't like)
I found: I can go into download mode. I can not go into recovery mode.
(a phone with a bootloop, usb debugging is off, and download mode is accessible)
So:
(When rooting, I opened Odin, I selected the PDA option, choose the proper file, and pressed start. Yellow changed to Green and we were done)
So Now, I open Odin, select the PDA option, choose the correct file for my phone (GT N7100) from likely the samsung website, I see the Yellow, hit start, yellow turns to green, and we're ok?
That simple thing I said 24 hr ago, still you are here.
It has nothing to do with usb debugging.
If you keep it enable /disable, it won't make any difference in flashing.
Sent from my GT-N7100 using xda premium
Phone is OK now!
dr.ketan said:
That simple thing I said 24 hr ago, still you are here.
It has nothing to do with usb debugging.
If you keep it enable /disable, it won't make any difference in flashing.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
I want to say thank you to everyone. I flashed recovery and it told of bad install. I rebooted and everything is FINE!
Thank you so much!
Moderators, please forgive me in not in the right place...
Came home from a glorious week of camping and decided to check out some 4.4.4 ROM's on my phone...
Already running older version of C-ROM, so backed up and flashed the KK 4.4.4 version. That's where it the wheels came off my bus..
Phone booted so damn slow, then there were hundred's of FC's, rendering the phone unuseable. Rebooted, cleared Dalvik and Cache but same difference. The phone died, the battery would NOT charge! No matter what! Try as I may...NO GO!!! For hours! Feared it was that issue wherein the S3 motherboard dies and the phone has to be replaced by Samsung. Kept trying...finally get the phone to boot into TWRP. Whew!!! Still the phone kept complaining that the battery was dead. WTF?!
Restored the back up I had made...accidentally grabbed another backup from december of last year (Cyanogenmod), so had to recover my C-ROM back instead...RESTORE FAILS! Tried a few times but still failed. Tried to re-flash the latest C-ROM, but STILL fails...everything I'm trying fails.
I read the output and see an error, "Unable to wipe /system" ...found a thread where a user, using TWRP, had the same error with their ROM they were trying to flash. Eventually, the fix was to delete the make_4fs (or whatever it's called) from /sbin directory. Did so and was able to flash my Cyanogen, but could not restore my C-ROM backup. That STILL fails, however, no error in the live output while it's restoring. Just ends up Failing at the end of the restore process. The live logs indicate that it's using the 2fs (or whatever it's called), which was successful in flashing my Cyanogen ROM...why will it not restore my C-ROM back? :crying:
Any help would be greatly appreciated.
kojam said:
Moderators, please forgive me in not in the right place...
Came home from a glorious week of camping and decided to check out some 4.4.4 ROM's on my phone...
Already running older version of C-ROM, so backed up and flashed the KK 4.4.4 version. That's where it the wheels came off my bus..
Phone booted so damn slow, then there were hundred's of FC's, rendering the phone unuseable. Rebooted, cleared Dalvik and Cache but same difference. The phone died, the battery would NOT charge! No matter what! Try as I may...NO GO!!! For hours! Feared it was that issue wherein the S3 motherboard dies and the phone has to be replaced by Samsung. Kept trying...finally get the phone to boot into TWRP. Whew!!! Still the phone kept complaining that the battery was dead. WTF?!
Restored the back up I had made...accidentally grabbed another backup from december of last year (Cyanogenmod), so had to recover my C-ROM back instead...RESTORE FAILS! Tried a few times but still failed. Tried to re-flash the latest C-ROM, but STILL fails...everything I'm trying fails.
I read the output and see an error, "Unable to wipe /system" ...found a thread where a user, using TWRP, had the same error with their ROM they were trying to flash. Eventually, the fix was to delete the make_4fs (or whatever it's called) from /sbin directory. Did so and was able to flash my Cyanogen, but could not restore my C-ROM backup. That STILL fails, however, no error in the live output while it's restoring. Just ends up Failing at the end of the restore process. The live logs indicate that it's using the 2fs (or whatever it's called), which was successful in flashing my Cyanogen ROM...why will it not restore my C-ROM back? :crying:
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Have you tried using ODIN to restore back to stock? If you can get the phone up and running, you may be able to restore from your old backups.
Bass_Man25 said:
Have you tried using ODIN to restore back to stock? If you can get the phone up and running, you may be able to restore from your old backups.
Click to expand...
Click to collapse
Thanks bud.
Oh, I got the phone up and running on the Cyanogen dated dec/2013.
ODIN? Never thought of it. Been such a long time. I do need to get stock on here so I can all the latest official radios etc, then put custom ROMs.
Been such a loooooong time since used ODIN though. Shouldn't be hard to get back on the horse.
Thanks for the suggestion!!!
any idea why this happened? anyone?
as an fyi, I tried to put the lastest SlimROM on but same difference. (i'm really pressed for time always. so I decided this is the quickest thing to try). seems the only thing that will flash is my Cyanogen from December. Strange...
Will have to give ODIN a try if I can ever get the time some day..
Odin shouldn't be a much longer process. Start flash, walk away. When you return 10 minutes to a few hours later, it'll be sitting there waiting for you, all nice and stock!
Anyway, one thing I dont recall seeing you tried is a factory reset. Chances are, that's what caused all your FC. Roms will always take a while on first boot. But all those FC were likely due to incompatible data. Then you may have encountered more data corruption as the system worked overtime trying to resolve all those conflicts.
Its purely a theory, but there's a good chance you will never be able to find exactly what caused all of your issues. Dont lose sleep over it is my best advice! A couple of tips though....
Never wipe/format system! Had you been able to successfully do so, and then nothing would still flash, there would no longer be an o/s to boot into! All roms will format your system partition as the first step in the flash, so there's just no need to do this manually. Most flash failures occur before the flash actually starts, meaning if there's a problem, most times you'll still be able to reboot normally.
Update your firmware. If its been a while since taking an ota or updating via Odin, you're probably on an older firmware build which is known to cause problems with many more recent roms. Most simply will not flash if not updated.
Also, by flashing your up to date firmware in Odin, you will likely fix any corruption which may have occurred on some of those partitions. Good chance you'll be able to flash whatever you want after an Odin firmware update and factory reset.
Hope that helps! Good luck!
DocHoliday77 said:
Odin shouldn't be a much longer process. Start flash, walk away. When you return 10 minutes to a few hours later, it'll be sitting there waiting for you, all nice and stock!
Anyway, one thing I dont recall seeing you tried is a factory reset. Chances are, that's what caused all your FC. Roms will always take a while on first boot. But all those FC were likely due to incompatible data. Then you may have encountered more data corruption as the system worked overtime trying to resolve all those conflicts.
Its purely a theory, but there's a good chance you will never be able to find exactly what caused all of your issues. Dont lose sleep over it is my best advice! A couple of tips though....
Never wipe/format system! Had you been able to successfully do so, and then nothing would still flash, there would no longer be an o/s to boot into! All roms will format your system partition as the first step in the flash, so there's just no need to do this manually. Most flash failures occur before the flash actually starts, meaning if there's a problem, most times you'll still be able to reboot normally.
Update your firmware. If its been a while since taking an ota or updating via Odin, you're probably on an older firmware build which is known to cause problems with many more recent roms. Most simply will not flash if not updated.
Also, by flashing your up to date firmware in Odin, you will likely fix any corruption which may have occurred on some of those partitions. Good chance you'll be able to flash whatever you want after an Odin firmware update and factory reset.
Hope that helps! Good luck!
Click to expand...
Click to collapse
What's up, Doc? Sorry for that...
I downloaded Odin this morning. I should have gotten the link from XDA. The site i got it from looked official, however, tons of endless pop-ups after I installed it. Freak!!!
Then found the xda links. Not sure which version to get because i didn't see which one handles the S3. The latest version (3.09) should, no?
As well, where do i get the stock ROM from? Forgive me for all these questions. Been extremely busy with work these past few months. No time to play around with my phone everything. I'm forgetting more than I know.
A full wipe was done. In TWRP, system was check (it's always checked) automatically when wiping to flash a new ROM.
Thanks again!
Everything you need is in my sig. Go to the firmware thread and the stock or root66 firmware listed there us what you flash in odin. Version 3.09 is fine btw.
DocHoliday77 said:
Everything you need is in my sig. Go to the firmware thread and the stock or root66 firmware listed there us what you flash in odin. Version 3.09 is fine btw.
Click to expand...
Click to collapse
Thanks!
S.O.S!!!
kojam said:
Thanks!
Click to expand...
Click to collapse
Downloaded the rooted firmware from your link and the ODIN (3.09)...
Flashed the firmware (making sure to get the correct one for WIND)...ODIN did it's thing...got a green pass...the phone rebooted...got the Samsung symbol, little swoosh animation, and the accompanying sound effect that goes with the swoosh-thing...THE PHONE NEVER BOOTED UP AN O/S!
Did it at about 11:30 last night, left it, got up this morn, and phone STILL in same status!
Found out that site where I downloaded the firmware had an issue last night. They posted this morn, apologizing to people about a D.O.D attack that may have caused dropped downloads. I downloaded the firmware again this morn, flashed with ODIN, got a pass....SAME THING!!! Phone
Had to quickly pack up my laptop to bring with me to the office. Will try the official, non-rooted firmware to see if I can get it to go.
Problems' that my team went from 12 to 2 people...my partner's off today...and I got a LOUD MOUTH across from me who WILL NOT leave me alone, no matter what I say or do. LOL.
Any suggestions?
In the words of George Costanza:
"I'm BACK, babyyyyyyy!!!!!"
The official firmware worked!
Phone's back online. Thanks for all your help. Will have to see about rooting later...as well, want to see how the battery operates on stock firmware. I've tried EVERYTHING under the sun to preserve batt life and NOTHING worked!!!
Tried EVERY KERNEL noted to be good on battery life, tried TONS of apps that were supposed to help, turned off as much as I could, etc....
batt still not good. I give up. Every diagnostic app says batt is very good. I dunno...
Earplugs! Lol! I definitely feel for you about your work status! Been there!
About the firmware though, if the download had been corrupted, it would've failed the initial check done by Odin. You are probably ok. Dont worry just yet!
If it is hanging up at the Samsung screen, you probably just need to factory reset. Almost always fixes this. (It happens due to incompatible data left from your previous rom)
This will wipe internal sdcard though, so if you haven't backed up yet, the next thing to fo is flash TWRP via Odin. You can then use its built in file manager to copy whst you need first. Or you can then flash an insecure kernel and use adb if you're familiar with that.
The Doc is in!
if the download had been corrupted, it would've failed the initial check done by Odin
Click to expand...
Click to collapse
That's EXACTLY my thought too. That was really perplexing...
I am up again...
Facotry Reset? How do I do that if stuck at the Samsung splash though?
Now that i know the official firmware works, maybe i'll, try again with the rooted firmware, try to factory reset when stuck, and continue to flash TWRP as you described above. Don't mind factory resetting. I've taken everything I need.
Oh!!!!
I noticed that all the apps I had before flashing the firmware are STILL on my phone. I would have thought that they would have been wiped out completely when lord ODIN was doing her thing.
....and battery life is STILL pretty bad...
Phone's been charging...became fully charged...unplugged it..it was down to 84% after only about 30/mins.
Will see how it goes after doing the factory wipe.
Again, how do i do a factory wipe if stuck at the Samsung swoosh after I re-flash the rooted firmware ?
Maybe your battery is dying. it happens. That would explain a big drop from the start.
To factory reset if you're stuck at boot up, turn the phone off, then boot up into recovery. Hold volume up, home and power. After it vibrates, release power only, continue holding the other two until you see recovery booting up.
If stock recovery is installed, choose factory reset.
In TWRP (probably similar in cwm) go to Wipe and choose factory reset there. In TWRP and CWM, factory resetting does not wipe your internal sdcard. Stock recovery will.
And as for Odin, it doesn't actually touch the user data partition, so all your apps and data are preserved. This is great when just upgrading from one build to the next, but is the reason a factory reset is required if coming from a non touchwiz rom.
---------- Post added at 03:59 PM ---------- Previous post was at 03:53 PM ----------
How old is your battery? The S3 is at the age where people who bought it when it was first released will start to notice the battery is beginning to degrade.
You can also get an app called Better Battery Stats here on xda (paid version in the play store). Its the goto utility for investigating problems with battery drain. Run it for a day after a full charge and then check its logs for persistent wakelocks. The app thread should explain its use better than I can, but if you are having trouble you can always post your bbs log here for one of us to look over. (This isnt my strongest area, but there are a few others around that may also be able to help. )
In the past few days after flashing alliance v2 i noticed that my phone would freeze then power cycle when I attempted to make or receive a call. Everything else works, I tried a different rom and still having the same issue. Any ideas?
eeeeeeeeek said:
In the past few days after flashing alliance v2 i noticed that my phone would freeze then power cycle when I attempted to make or receive a call. Everything else works, I tried a different rom and still having the same issue. Any ideas?
Click to expand...
Click to collapse
Take a look at posts 2 and 3 of this thread.
http://forum.xda-developers.com/showthread.php?t=3067828
HELP!!! Need a PIT file for N4
Odd problems that carry past factory reset and ROM flashes require a better flush. And clean install.
samep said:
Take a look at posts 2 and 3 of this thread.
http://forum.xda-developers.com/showthread.php?t=3067828
HELP!!! Need a PIT file for N4
Odd problems that carry past factory reset and ROM flashes require a better flush. And clean install.
Click to expand...
Click to collapse
So I had already started when I saw that, though the second post on that thread is a little confusing. However I had already odin back, booted up, but didn't wipe it, so instead I hooked it up to samsung kies, and did a full restore from kies. Made a test call, still froze, and crashed. So re rooted and put twrp then did an excessive number of advanced wipes. I even used the repair option to repair system then data. Just flashed vision and waiting on it too boot to see. Should I move further questions to that thread?
eeeeeeeeek said:
So I had already started when I saw that, though the second post on that thread is a little confusing. However I had already odin back, booted up, but didn't wipe it, so instead I hooked it up to samsung kies, and did a full restore from kies. Made a test call, still froze, and crashed. So re rooted and put twrp then did an excessive number of advanced wipes. I even used the repair option to repair system then data. Just flashed vision and waiting on it too boot to see. Should I move further questions to that thread?
Click to expand...
Click to collapse
I'd suggest keeping your posts on this thread. Just referred to that to save time.
Try the steps. Ask if not clear. If it sounds too extreme, start with the factory reset, Odin and factory reset again before flashing a deodexed ROM like Alliance. Update with results.
eeeeeeeeek said:
So I had already started when I saw that, though the second post on that thread is a little confusing. However I had already odin back, booted up, but didn't wipe it, so instead I hooked it up to samsung kies, and did a full restore from kies. Made a test call, still froze, and crashed. So re rooted and put twrp then did an excessive number of advanced wipes. I even used the repair option to repair system then data. Just flashed vision and waiting on it too boot to see. Should I move further questions to that thread?
Click to expand...
Click to collapse
Ii did as follows and tried several other ways, same results on factory image, unless I have a bad image, I pulled it off of one of the forums here
Are you powering down prior to Odin of stock tar? Did you use your PC to download the tar? Have you tried doing this without the sdcard? The full wipes are important.
Try the NIE stock tar.
http://forum.xda-developers.com/showthread.php?p=56853341
samep said:
Are you powering down prior to Odin of stock tar? Did you use your PC to download the tar? Have you tried doing this without the sdcard? The full wipes are important.
Try the NIE stock tar.
Click to expand...
Click to collapse
Ive wiped everything and formatted data repeatedly......I had a nand backup i forgot about, I'm going to restore that and see. I haven't tried flashing anything without the sd card from recovery, I have removed my SD card for the moment. It does seem like this is the issue, something with the partition. It's of course possible I didn't follow directions properly, though I feel I have. I'll also try NIE if need be. It's very bizzare issue. everything else works fine.
Update: Flashed NK2 stock tar, tried to make a call, same thing, phone freezes and powercycles.
Update 2: I even tried a different dialer, same results. Could a hardware issue cause this?
My suggestion is to try the factory reset, power down, Odin and Dial*##72786# to reprovision the phone; data profile update and try again.
Still fails? Could be hardware failure.
Anyone else?
samep said:
My suggestion is to try the factory reset, power down, Odin and Dial*##72786# to reprovision the phone; data profile update and try again.
Still fails? Could be hardware failure.
Anyone else?
Click to expand...
Click to collapse
Ive done all of this, even the 72786, tried wifi calling too just to be sure. maybe something with the antennai
Outside of a good suggestion, I'd stay with stock, call Sprint support. If not resolved there, setup a tech appointment.
Sent from my SM-N910P using Tapatalk
Hello. When my device was updated to KitKat, the WiFi stopped turning on. It doesn't fail to connect, it just will not turn on at all. I tried an app called "WiFi Fixer", which didn't work, but in the "Known Issues" section it said this was caused by the "Android framework not interacting with the WiFi driver" and said to flash a custom ROM.
I rooted, installed TWRP, and flashed CM 12.1 successfully. The WiFi still wouldn't turn on. I then decided it was probably a hardware issue that coincidentally showed itself at the same time as the update. So then, I installed Cheetah Mobile launcher, and one of their themes, and was resigned to not having WiFi.
I got bored with the CM theme, and installed the Dark Material theme. At this point the phone started acting buggy, not waking from wakelock, force closing, and randomly rebooting. So i then deleted cache and dalvick cache, and re-flashed from the CM 12.1 zip i had saved on my SD. The bugs would not stop, almost making my phone unusable. The only bright side of this was that my WiFi was turning on and working! I thought maybe the hardware problem had fixed itself somehow, but I still wanted to have a usable phone. I kept re-flashing from the existing CM 12.1 zip, the WiFi kept working, but the buggy behavior wouldn't go away.
I figured that maybe the CM 12.1 zip on my SD was corrupted, so I downloaded another copy from CyanogenMod, installed it on my SD, and erased the old copy. Then, I wiped everything and re-flashed with the new zip. The buggy behavior went away, but WiFi stopped working again! I'm thoroughly confused now.
If it's a hardware issue, why does it come and go with ROMs/ themes? I thought it may be a kernel issue, so I flashed Ktoonsez K747 kernel, which is working fine, but I still don't have WiFi. Did the themes I installed earlier change the kernel in some way to make my WiFi work temporarily? Is there a fix for this? Is it a known problem? I researched the forums but the only answers I found for similar problems were from earlier versions (2013) of Android/ CyanogenMod ROMs.
At this point, I'm willing to give anything a try, I've even opened the phone, inspected, un-plugged, and replugged the WiFi antenna. If it was a hardware issue, would I expect to see any damage, like a fried circuit or something? Is there any test to check if it's hardware vs. software?Can I buy a replacement antenna?
I'm pretty broke and can't afford a new phone, which is why I'm trying to resuscitate this one When it works, it's sufficient for my use.
Please help, I really want WiFi back! Thanks in advance for any advice.
Full odin back to stock. Best solution.
Get odin here at the bottom of the page. The firmware is there too. If you create a free account the download goes much faster.
Also, re flashing the same cm12.1 over and over won't help. Have you tried the newest nightly? After odin back to stock, if you want cm, use the latest.
If you don't have a pc, you can try flashfire, but I haven't tried it.
madbat99 said:
Full odin back to stock. Best solution.
Get odin... at the bottom of the page. The firmware is there too. If you create a free account the download goes much faster.
Also, re flashing the same cm12.1 over and over won't help. Have you tried the newest nightly? After odin back to stock, if you want cm, use the latest.
If you don't have a pc, you can try flashfire, but I haven't tried it.
Click to expand...
Click to collapse
Thanks, I'm downloading it now. Does it matter that this is an older build? I started with L710VPUDOH1, but this download is a previous version, L710VPUDNJ2.
I found this, which has the L710VPUDOH1 build in a zip...
Google > "L710VPUDOH1 opensource samsung" > first result (I'm too new on XDA to post outside links!)
within the zip is Kernel.tar and Platform. tar. which I have done nothing with, as I'm not sure if it's what I need. Do you think I should flash these? or just go with the NJ2 build?
Thank you for your insight, and taking the time to help me!
dieseldeeznutz said:
Thanks, I'm downloading it now. Does it matter that this is an older build? I started with L710VPUDOH1, but this download is a previous version, L710VPUDNJ2.
I found this, which has the L710VPUDOH1 build in a zip...
Google > "L710VPUDOH1 opensource samsung" > first result (I'm too new on XDA to post outside links!)
within the zip is Kernel.tar and Platform. tar. which I have done nothing with, as I'm not sure if it's what I need. Do you think I should flash these? or just go with the NJ2 build?
Thank you for your insight, and taking the time to help me!
Click to expand...
Click to collapse
No. For many reasons. First, its not the rom, its just the update. No one has made a flashable rom zip. Second, official updates won't flash in custom recovery and it would never flash because you're rooted.
So basically its not the full rom, its the official update zip, just a patch.
Gotta flash a .tar. Unless your on the triband model, nj2 should be fine
madbat99 said:
No. For many reasons. First, its not the rom, its just the update. No one has made a flashable rom zip. Second, official updates won't flash in custom recovery and it would never flash because you're rooted.
So basically its not the full rom, its the official update zip, just a patch.
Gotta flash a .tar. Unless your on the triband model, nj2 should be fine
Click to expand...
Click to collapse
Flashed back to stock, and updated to OH1 successfully, but still no wifi. It's greyed out and won't turn on
I would think it was a hardware problem, except that it all started when my phone updated to 4.4.2. I've found many others with this problem online, but no fixes. Can I flash back to 4.3? or can I flash a new modem/radio(?) file. I thought I saw one in my searches but can't seem to find it now
Thanks again
dieseldeeznutz said:
Flashed back to stock, and updated to OH1 successfully, but still no wifi. It's greyed out and won't turn on
I would think it was a hardware problem, except that it all started when my phone updated to 4.4.2. I've found many others with this problem online, but no fixes. Can I flash back to 4.3? or can I flash a new modem/radio(?) file. I thought I saw one in my searches but can't seem to find it now
Thanks again
Click to expand...
Click to collapse
No, do not try to flash 4.3. You will hard brick, and your phone will be a paperweight. Same thing if you try flashing any pre Knox modems/radios.
Are you flashing something else with this? It's something on your device if a tar flash in odin didn't fix it. Did you factory reset after odin?
madbat99 said:
No, do not try to flash 4.3. You will hard brick, and your phone will be a paperweight. Same thing if you try flashing any pre Knox modems/radios.
Are you flashing something else with this? It's something on your device if a tar flash in odin didn't fix it. Did you factory reset after odin?
Click to expand...
Click to collapse
Yes, I factory reset, cleared all caches, rebooted into safe mode, changed wifi settings in service mode... did an ancient Indian wifi fixing dance, spoke soothingly to it, then cursed at it :laugh: maybe it's a hardware problem with coincidental timing that's also happened the same exact way to other people
dieseldeeznutz said:
Yes, I factory reset, cleared all caches, rebooted into safe mode, changed wifi settings in service mode... did an ancient Indian wifi fixing dance, spoke soothingly to it, then cursed at it :laugh: maybe it's a hardware problem with coincidental timing that's also happened the same exact way to other people
Click to expand...
Click to collapse
Lmao, funny. I heard it happening to people a while back. Can't remember what caused or fixed it. Some fixed it with custom kernel but the kernel is waaay outdated now. But it was kt747 by ktoonsez. But its so old. What carrier are you on? Sprint, virgin Mobile, boost?
madbat99 said:
Lmao, funny. I heard it happening to people a while back. Can't remember what caused or fixed it. Some fixed it with custom kernel but the kernel is waaay outdated now. But it was kt747 by ktoonsez. But its so old. What carrier are you on? Sprint, virgin Mobile, boost?
Click to expand...
Click to collapse
I'm on Sprint.
this just happended to me the other night actually, did you find solution? Apparently just taking out the battery and resetting solved it for a lot of people, but not me. I will tell you what did work though! (keeps randomly doing it again but at least i can gfet it to work aghain even if only for a littlw bit)
First check with root explorer if you have this fike "data\misc\wifi\wpa_supplicant.conf "
I guess it has something to do withthis file, and your android not writing to the right spot, but i honestly have no idea so ill continue. what i did (i saw i didnt have the file either) i dialed *#0011# then hit menu, and then hit wifi, and turned off the bottom switch "wifi power save mode". I exited service menu tried wifi a couple times still same thing, so i went back into service menu and reenabled the switch, then i turned off the phone by pulliung out battery. I logged into my custom recovery and checked out the file explorer in twrp, and voila there that mysery file was! So i cleared dalvick and cache, rebooted into rom, (wicked x v8.2) and attempted wifi and it was working again. so take whatever conclusion youd like but im too tired to keep my eyes open at the moment and good luck, pissed me off cuz wifi was all i had no service, of course
skinnykinney said:
this just happended to me the other night actually, did you find solution? Apparently just taking out the battery and resetting solved it for a lot of people, but not me. I will tell you what did work though! (keeps randomly doing it again but at least i can gfet it to work aghain even if only for a littlw bit)
First check with root explorer if you have this fike "data\misc\wifi\wpa_supplicant.conf "
I guess it has something to do withthis file, and your android not writing to the right spot, but i honestly have no idea so ill continue. what i did (i saw i didnt have the file either) i dialed *#0011# then hit menu, and then hit wifi, and turned off the bottom switch "wifi power save mode". I exited service menu tried wifi a couple times still same thing, so i went back into service menu and reenabled the switch, then i turned off the phone by pulliung out battery. I logged into my custom recovery and checked out the file explorer in twrp, and voila there that mysery file was! So i cleared dalvick and cache, rebooted into rom, (wicked x v8.2) and attempted wifi and it was working again. so take whatever conclusion youd like but im too tired to keep my eyes open at the moment and good luck, pissed me off cuz wifi was all i had no service, of course
Click to expand...
Click to collapse
I have that file on my phone. So I understand, you originally didn't have that file, but after doing the steps you listed it magically appears, and then wifi works? I really wish I could get it to work. Also, you said it keeps happening... so the file keeps dissappearing on you? Thanks for the response.
So...
Last week, my wife's Tab S went into a bootloop. She runs complete stock, we haven't rooted, or anything. There had been a notification about an update, but she hadn't touched it. She'd updated to Lollipop at some point last year, but hadn't applied the absolute latest update. One day last week, she just turned it on, and it started bootlooping.
Because it was so stock, there were no backups, no nandroids, or anything like that. No Custom Recovery. I told her "well, we can just do a factory reset. You'll lose everything, but once we get you back up and running, it'll just re-download everything from the Goog." So we factory reset it. Looked good for a minute, booted into the first screen, enter in your Wi-Fi password, all that. As soon as we got the Wi-Fi password entered, however, it re-booted. And keep rebooting. Bootloop city. No problem. I walked her through (over the phone) using Odin to flash the latest Lollipop firmware. No dice. It appeared to flash successfully, but still bootlooped.
Over the weekend, I tried using Kies to flash the most official firmware I could find. Everything was successful -computer recognized the device, was able to download "direct from the source," as it were, but it got stuck at 69% twice before failing. I read somewhere that one had to run Kies in administrator mode to get it to successfully complete. So I did, and it got past 69%, successfully completing the flash. STILL NO LUCK. STILL WITH THE BOOTLOOPS.
Last night, I realized that I hadn't flashed in Odin using Administrator Mode. Tried it, using latest 5.0.2 (XAR-Cellular South). Flashed successfully, all appeared well. Still bootlooped.
So, I'm stuck. I can get into recovery, I can get into Download Mode, I can successfully flash. I just can't get the darn thing booted.
Thoughts, anyone? Should I try flashing a Custom ROM? How hard is that using Odin? Thanks in advance.
Ok this will take a few tries but here is my method of dealing with this situation
1) Flash stock using Odin
2) AS SOON AS the screen goes blank, start holding Power+Volume Up+Home
3) When recovery boots, release the buttons
4) Use the volume buttons to select "Wipe data/factory reset"
5) Press power to confirm
6) Reboot
If that doesn't work, you may either:
1) (more likely) Installing a ROM will fix the problem
2) (unlikely but possible) You might have worn NAND pages, which I doubt but could cause this behavior.
Nandr0idC0nsumer said:
Ok this will take a few tries but here is my method of dealing with this situation
1) Flash stock using Odin
2) AS SOON AS the screen goes blank, start holding Power+Volume Up+Home
3) When recovery boots, release the buttons
4) Use the volume buttons to select "Wipe data/factory reset"
5) Press power to confirm
6) Reboot
If that doesn't work, you may either:
1) (more likely) Installing a ROM will fix the problem
2) (unlikely but possible) You might have worn NAND pages, which I doubt but could cause this behavior.
Click to expand...
Click to collapse
Thanks, I'll try these steps tonight when I get home, and report back!
All right, here's something interesting. Before I tried your first step, I remembered that the other night, I left it stuck at the Samsung logo -it was just kind of stuck there, and since the behavior was a little different than I'd seen before (not continuous bootlooping), I thought I'd boot into recovery and wipe. I did, I wiped (factory reset), and rebooted. The tablet booted into the first screen, Accessibility/Wi-Fi, blahblah. This was where it usually rebooted. On a hunch, I bypassed entering in my WiFi key. I then bypassed almost everything else (Samsung account, Google account, etc.), expecting that the tablet would reboot at any moment. But I made it to the front apps page, where it shows you the side-launcher, the Magazine-Flipboard thingie, and whatnot. Wi-Fi still not connected, though. I opened up the app drawer, and scrolled around. Looked really good for a moment. I even took a picture with the camera, and viewed it in Gallery! Feeling brave, I thought, "well, maybe it just needed a couple of minutes before firing up the radio." So I went into settings, and inputted my WiFi key. It connected. And rebooted into its bootloop. (getting so tired of that boot-sound).
Went ahead and flashed the most original stock firmware I could find. As always, flashed successfully. As soon as it booted, I made my way to recovery, and wiped, per your instructions. No luck. Bootloop again.
It's something in the WiFi is what I've come to think as a result of the above. Which I don't entirely understand, as I thought the radio got re-flashed with the firmware.
I'm ready to try flashing a Custom Rom. Can I do that through Odin, or should I try and flash TWRP, and do it through there? Will TWRP flash without a working (bootable) OS?
All right. Thanks for your response!
Try this as a test.
First make a full backup of every partition with twrp including the EFS <<IMPORTANT!
Get it booting again without wifi then root the device and delete the EFS folder or delete it in recovery.
Reboot the device and try and enable wifi.
ashyx said:
Try this as a test.
First make a full backup of every partition with twrp including the EFS <<IMPORTANT!
Get it booting again without wifi then root the device and delete the EFS folder or delete it in recovery.
Reboot the device and try and enable wifi.
Click to expand...
Click to collapse
Got TWRP installed. Won't backup. Fails at 16% (system partition, I think). Just powers down to battery indicator in the middle of the backup. Looks like it backs up the EFS, though, since it's the first one. And when I go into TWRP's Restore option, there's a backup there (though I don't dare try and restore it).
Now I have to figure out a way to get the Custom ROM and GAPPS I downloaded onto the tablet without a reliable boot... It's gotten to the front screen a time or two tonight, but starts looping even when I bypass the WiFi setup.
Entered adb/TWRP interface. Tried to push two files, a Custom ROM file, and a GAPPS file. The ROM failed, with some sort of "Error 7," incompatible data, blahblah... Just out of curiosity, I tried to push the GAPPS file, and that failed after about 6%, and the tablet powered off.
I'm running out of ideas.
copied a custom rom to a USB/OTG stick (thumbdrive), and plugged it in. Fired up TWRP, tried to install. Wouldn't. Wouldn't install GAPPS, either. Looks like the only way it wants to flash anything is through ODIN or KIES.
The Latest...
All right...
I remembered that sometimes the TWRP version mattered. When I installed TRWP last night, I installed the latest and greatest, 3.0.2. Last night after I gave up, I remembered that sometimes, the latest and greatest TWRP doesn't install things perfectly. So, this morning, I downloaded TWRP 2.8.6-ish onto the USB/OTG device, and re-flashed the recovery partition. To be honest, I was surprised that TWRP was even able to flash that (but the TWRP image is only like 9.8 MB, so...)...
Got TWRP 2.8.6.0 flashed, and rebooted into TWRP. Immediately decided to try and re-flash the custom ROM that I'd tried unsuccessfully to flash last night, since the thumbdrive was still plugged in. Resurrection Remix Lollipop. Lined up GAPPS in the queue, as well. The ROM *appeared* to flash better than it had in TWRP 3.0.2, but it was sort of hard to see... GAPPS failed, and I was prepared to watch another round of bootloops. It did bootloop, sort of. The RR splash screen appeared, said that it was installing (or preparing) xx out of XX apps. Then, it rebooted. I figured it was doing its bootloop thing. However, it got to the same screen, "installing xx out of XX apps. Except that XX number had gone down, and the xx number had gone up. It repeated this action about 4 times --the last time I saw it reboot, it was "installing 1 out of 2 apps." And then...?
It booted into the RR lockscreen.
Of course, there were no GAPPS. In fact, there are something like only 20 apps total on the tablet. But it appears somewhat stable at the moment. (See picture).
Afraid to try and connect WiFi, afraid that it'll just bootloop.
Speaking of bootloop. At one point, once we got it booted, my wife hit an option in the Settings. LCD Density, I believe. As soon as she hit it (she literally just placed her finger over the 320 default option), the tablet rebooted. No loop, though. Rebooted straight back to the RR lockscreen.
So I appear to have a somewhat stable OS flashed onto the tablet at the moment. No GAPPS, though. No WiFi.
Anybody have a suggestion on where to go from here? I have my doubts as to whether or not I can even back up this configuration.
Sorry about all the updates. I kind of figured that if *anyone* else ever goes through what I'm going through, they'll have some sense of all the different things that can be tried in resurrecting a bricked/bootlooping device. I appreciate everyone's efforts to date -thank you so much, @Lightn1ng and @ashyx.
All right, because I can't leave well enough alone....
I got WiFi up and working. Tablet still stable and working. Wheeeee.... No GAPPS, though.
Downloaded GAPPS, second-smallest package from opengapps- only 128M (5.1 ARM package). Downloaded it in Android, from the tablet! Tried to flash it in TWRP. Failed, tablet rebooted halfway (not even) through. Now it's bootlooping again...
I should've left well enough alone, and waited for someone. Have tried re-installing Resurrection Remix, but tablet keeps failing to flash. Might have to try and flash a different TWRP. I don't know...
Have you tried another Gapps? Also, is this the WiFi only model or the LTE model we're talking about?
Lightn1ng said:
Have you tried another Gapps? Also, is this the WiFi only model or the LTE model we're talking about?
Click to expand...
Click to collapse
It's the WiFi-only model - SM-T800.
It's kind of weird. I thought it might be some sort of internal memory problem (like the worn Nand pages you mentioned), since almost anything I try to do in TWRP fails (although I was able to flash an entire Custom ROM the one time AND get it booted) -but backing up isn't working, whether it's to internal/external SD. And the fact that I can flash perfectly (subjective term there) well using Odin or Kies tells me that whatever problems the tablet is having, something's getting through.
I'll try a different GAPPS package. Right now, though, TWRP isn't letting me flash hardly anything, and moving files back and forth on this thing is just awful.
AGH - I was so close!
daina said:
It's the WiFi-only model - SM-T800.
It's kind of weird. I thought it might be some sort of internal memory problem (like the worn Nand pages you mentioned), since almost anything I try to do in TWRP fails (although I was able to flash an entire Custom ROM the one time AND get it booted) -but backing up isn't working, whether it's to internal/external SD. And the fact that I can flash perfectly (subjective term there) well using Odin or Kies tells me that whatever problems the tablet is having, something's getting through.
I'll try a different GAPPS package. Right now, though, TWRP isn't letting me flash hardly anything, and moving files back and forth on this thing is just awful.
AGH - I was so close!
Click to expand...
Click to collapse
I'm running out of ideas!
Maybe somebody else with a T800 could backup their entire EMMC using
Code:
dd if=/dev/mmcblk0 of=/sdcard/full_nand_dump.bin
And you take the file on your tablet and do
Code:
dd if=/sdcard/full_nand_dump.bin of=/dev/mmcblk0
And restore YOUR efs folder using TWRP.
THIS IS A DANGEROUS OPERATION AND I AM NOT RESPONSIBLE FOR ANYTHING THAT GOES WRONG!
---------- Post added at 08:01 PM ---------- Previous post was at 07:57 PM ----------
@ashyx Any more ideas before I go ahead with my evil world domination plan to recover this device?
I wouldnt carry out any risky operations until a full backup can be made with twrp or you may end up with an unrecoverable device.
If twrp cannot backup the system partition then there is an issue with the partition.
Try backup again and post the recovery log, it may contain some relative information.
I have the same issues and have tried eveything. I was rooted and running the latest Pheonix rom on my sm-t800. Last Wednesday (8-10) I starting getting boot loops out of nowhere, no new apps nothing just a daily driver. I've been through everything on here and have gone back to bone stock but to no avail, the boot loops just keep coming. I can connect to wifi and get things set up but if I try to use anything more than 'light usage' the tab starts its boot loops again and rows fits for about 10 minutes and always different timing on the boot. Sometimes it will make it to the Samsung logo, sometime only to Tab S and sometimes about 10 seconds of usage.. I know this isn't helping much but wanted to let you know there are more of us with the same problem. Will be blab to try anything to help said issue.
Exactly the same issue on my LTE version.
Samsung support just asked me 230€ for a new motherboard.
I refused to repair. I think it is related to nand memory..
Hello I have both the 8.4" and 10.5" I updated the 8.4" to Android 5.02 nothing but boot loops my other is still on 442 and I wont be updating it as its working fine. I have been reading a few posts and the problem was right in front of me all the time I have 2 internet connections 2.4 GHZ and 5.0 GHZ if I connect to the 5.0 GHZ I get boot loops but if I stay on 2.4 GHZ no problems what so ever so I may just install a custom rom and my 10.5 tab and stay clear of the faster internet.
srfairhurst said:
Hello I have both the 8.4" and 10.5" I updated the 8.4" to Android 5.02 nothing but boot loops my other is still on 442 and I wont be updating it as its working fine. I have been reading a few posts and the problem was right in front of me all the time I have 2 internet connections 2.4 GHZ and 5.0 GHZ if I connect to the 5.0 GHZ I get boot loops but if I stay on 2.4 GHZ no problems what so ever so I may just install a custom rom and my 10.5 tab and stay clear of the faster internet.
Click to expand...
Click to collapse
Why not just update to Marshmallow? Absolutely no issues for me.
ashyx said:
Why not just update to Marshmallow? Absolutely no issues for me.
Click to expand...
Click to collapse
Now i figured out its the wifi thats causing the problem i will update to android 6.01 or if i can find a good custom rom il risk that.
daina said:
It's the WiFi-only model - SM-T800.
It's kind of weird. I thought it might be some sort of internal memory problem (like the worn Nand pages you mentioned), since almost anything I try to do in TWRP fails (although I was able to flash an entire Custom ROM the one time AND get it booted) -but backing up isn't working, whether it's to internal/external SD. And the fact that I can flash perfectly (subjective term there) well using Odin or Kies tells me that whatever problems the tablet is having, something's getting through.
I'll try a different GAPPS package. Right now, though, TWRP isn't letting me flash hardly anything, and moving files back and forth on this thing is just awful.
AGH - I was so close!
Click to expand...
Click to collapse
DrinkSlinger said:
I have the same issues and have tried eveything. I was rooted and running the latest Pheonix rom on my sm-t800. Last Wednesday (8-10) I starting getting boot loops out of nowhere, no new apps nothing just a daily driver. I've been through everything on here and have gone back to bone stock but to no avail, the boot loops just keep coming. I can connect to wifi and get things set up but if I try to use anything more than 'light usage' the tab starts its boot loops again and rows fits for about 10 minutes and always different timing on the boot. Sometimes it will make it to the Samsung logo, sometime only to Tab S and sometimes about 10 seconds of usage.. I know this isn't helping much but wanted to let you know there are more of us with the same problem. Will be blab to try anything to help said issue.
Click to expand...
Click to collapse
Hello,
and the rest of story??
i can flash TWRP in download mode, and i can intall zip by TWRP , the lineage rom,
but, cant odin flash official md5 file, it stucks on logo.