Related
I felt my nexus reboot during class today(it was in my pocket) and then it got stuck in a reboot loop, it freezes during boot animation and starts over.
I have tried to pull out the battery, to do a cold boot as well.
It is rooted, and i followed one of the early tutorials to do so (i don't remember exactly which).
Is there anything i can do without loosing my data(no backup, i know,stupid me).
Can i try to reset the bootloader for example?
I have also received 3 system updates the last week, assumable from samsung, (yakjuxw). But it hasn't increased my android version. I don't know if this has anything to do with my problem, but i feel like i should mention it.
+1 on this too...i was checking my messages this morning and it just rebooted. havent had this ever happen to me, no matter wiping, reflashing, restore....nothing works...just keeps rebooting at google screen 4 or 5 times...then it just stays on the screen, phone starts to heat up too.
Same here, I installed Chrome bate last night. Did you guys do the same? I wonder if it is the cause of the problem.
i did try out chrome beta yesterday, but ended up uninstalling it. im on a ir10 modaco kitchen rom with a 1.35ghz oc custom kernal.
I am on stock rom without root.
I found the below and it scares me. Looks like there isn't any fix...
http://androidforums.com/samsung-galaxy-nexus/493450-dreaded-bootloop.html
Snobjorn said:
I felt my nexus reboot during class today(it was in my pocket) and then it got stuck in a reboot loop, it freezes during boot animation and starts over.
I have tried to pull out the battery, to do a cold boot as well.
It is rooted, and i followed one of the early tutorials to do so (i don't remember exactly which).
Is there anything i can do without loosing my data(no backup, i know,stupid me).
Can i try to reset the bootloader for example?
I have also received 3 system updates the last week, assumable from samsung, (yakjuxw). But it hasn't increased my android version. I don't know if this has anything to do with my problem, but i feel like i should mention it.
Click to expand...
Click to collapse
Can you access the bootloader?
Snobjorn said:
I felt my nexus reboot during class today(it was in my pocket) and then it got stuck in a reboot loop, it freezes during boot animation and starts over.
I have tried to pull out the battery, to do a cold boot as well.
It is rooted, and i followed one of the early tutorials to do so (i don't remember exactly which).
Is there anything i can do without loosing my data(no backup, i know,stupid me).
Can i try to reset the bootloader for example?
I have also received 3 system updates the last week, assumable from samsung, (yakjuxw). But it hasn't increased my android version. I don't know if this has anything to do with my problem, but i feel like i should mention it.
Click to expand...
Click to collapse
i am pretty sure if you reset the bootloader it will wipe everything. just go into recovery and do a factory reset (last option of course).
I installed google chrome earlier today aswell.
I have now tried to restore from an earlier nandroid backup, but it fail at the \data stage.
Factory reset didnt help either.
edit:
However, i was able to pull data using adb. Saved my images atleast.
also: i have clockworkmod v5.5.0.2
Do you have the SDK installed on your pc? If so, you should connect it and run ddms. You can then watch the log and see where your phone is crashing. Maybe that would give a starting point to what is wrong.
I start ddms, and my phone pops up under devices witha nomber as name, ther after '??' and 'unknown' nothing else. This is when my phone is in clockworkmod recovery . it disappears when i try reboot.
Hmmm that's weird. You might have to try flashing the stock images in fastboot.
El Daddy said:
Hmmm that's weird. You might have to try flashing the stock images in fastboot.
Click to expand...
Click to collapse
Hell yeah! This worked for me.
Sent from my Galaxy Nexus using xda premium
Hello All, This is my first time posting so could not post directly into http://forum.xda-developers.com/showthread.php?t=2021640&page=23.
I’ve been having a problem with SPH-D710 FK23 and from what I’ve read and searched, it doesn’t seem to be common but would like to ask the experts. I’ve installed FK23 from the above thread [LINK][ROM][ODIN][TAR]SPH-D710 FK23 (FK23 Modem/Kernel/ROM - Root/Stock), trying first the Rooted_Nodata but then using Rooted_Restore. I’ve redone the phone three times now using Rooted_Restore and the first thing that seems very odd is that the internal USB did not get wiped. After it completed and booted, the items on the internal USB (such as in the downloads directory) were still present. Once I entered my Google account, the apps reinstalled from Google.
Aside from not seeming to completely wipe the device, there didn’t appear to be any problem until I turned on Bluetooth. Once Bluetooth was turned on and paired with my BlueAnt Q2 v.1.1, the device would freeze and reboot. At this point, I’m not able to turn off Bluetooth as even after rebooting (including a battery pull) the system only responds to touch during the initial few moments of boot while showing scanning and/or initializing SD. After a few moments, no screen interaction will respond other than vibration feedback when pressing any of the four bottom buttons. Volume up/down is not responsive though the power button will still blank or turn the screen on. Aside from that the device appears locked than will eventually reboot itself.
Has anyone seen similar and/or any suggestions?
kdean7 said:
Hello All, This is my first time posting so could not post directly into http://forum.xda-developers.com/showthread.php?t=2021640&page=23.
I’ve been having a problem with SPH-D710 FK23 and from what I’ve read and searched, it doesn’t seem to be common but would like to ask the experts. I’ve installed FK23 from the above thread [LINK][ROM][ODIN][TAR]SPH-D710 FK23 (FK23 Modem/Kernel/ROM - Root/Stock), trying first the Rooted_Nodata but then using Rooted_Restore. I’ve redone the phone three times now using Rooted_Restore and the first thing that seems very odd is that the internal USB did not get wiped. After it completed and booted, the items on the internal USB (such as in the downloads directory) were still present. Once I entered my Google account, the apps reinstalled from Google.
Aside from not seeming to completely wipe the device, there didn’t appear to be any problem until I turned on Bluetooth. Once Bluetooth was turned on and paired with my BlueAnt Q2 v.1.1, the device would freeze and reboot. At this point, I’m not able to turn off Bluetooth as even after rebooting (including a battery pull) the system only responds to touch during the initial few moments of boot while showing scanning and/or initializing SD. After a few moments, no screen interaction will respond other than vibration feedback when pressing any of the four bottom buttons. Volume up/down is not responsive though the power button will still blank or turn the screen on. Aside from that the device appears locked than will eventually reboot itself.
Has anyone seen similar and/or any suggestions?
Click to expand...
Click to collapse
Actually think I have an answer for this now... and it has to do with the change to the storage structure and/or mount points. Before the main mount point for /sdcard was... /sdcard. Now looks like it's /storage/sdcard0. That's the only reason I can think of why it would fail - the script is still triggered so only if it didn't find /sdcard would it skip.
garwynn said:
Actually think I have an answer for this now... and it has to do with the change to the storage structure and/or mount points. Before the main mount point for /sdcard was... /sdcard. Now looks like it's /storage/sdcard0. That's the only reason I can think of why it would fail - the script is still triggered so only if it didn't find /sdcard would it skip.
Click to expand...
Click to collapse
Any idea on the unresonsiveness and rebooting?
kdean7 said:
Any idea on the unresonsiveness and rebooting?
Click to expand...
Click to collapse
Think it's part of the nodata flash effects still lingering.
Try this:
1) Flash FI27 full restore (rooted)
2) Reboot to Odin
3) Flash FK23 full restore (rooted)
That should fix it if it's old data not playing nice.
If it still happens after this the next step we'll do is check your battery.
garwynn said:
Think it's part of the nodata flash effects still lingering.
Try this:
1) Flash FI27 full restore (rooted)
2) Reboot to Odin
3) Flash FK23 full restore (rooted)
That should fix it if it's old data not playing nice.
If it still happens after this the next step we'll do is check your battery.
Click to expand...
Click to collapse
Is it possible that kdean7's problems are because of restoring Google's backup during the initial configuration process?
garwynn said:
Think it's part of the nodata flash effects still lingering.
Try this:
1) Flash FI27 full restore (rooted)
2) Reboot to Odin
3) Flash FK23 full restore (rooted)
That should fix it if it's old data not playing nice.
If it still happens after this the next step we'll do is check your battery.
Click to expand...
Click to collapse
Not sure if what i've done is the same outcome as above but did this yesterday before this was posted. Booted to recovery mode and wiped device / factory restore then flashed FK23 full restore (rooted). SInce then, I've added back my google account, added my Samsung account, added one exchange email and one pop3 email and have been letting the device self-update and reinstall the apps from the Play store. Made one test call and a couple txt messages. I've been waiting until no further updated occur before turning bluetooth back on but so far have't seen any random reboots though don't think I've used it long enough to see any screen locking. More to come as I test further this morning.
kdean7 said:
Not sure if what i've done is the same outcome as above but did this yesterday before this was posted. Booted to recovery mode and wiped device / factory restore then flashed FK23 full restore (rooted). SInce then, I've added back my google account, added my Samsung account, added one exchange email and one pop3 email and have been letting the device self-update and reinstall the apps from the Play store. Made one test call and a couple txt messages. I've been waiting until no further updated occur before turning bluetooth back on but so far have't seen any random reboots though don't think I've used it long enough to see any screen locking. More to come as I test further this morning.
Click to expand...
Click to collapse
Don't recall if the factory reset wipes USB storage, that would be the only possible difference.
Hope that gets you back into shape, will be checking during the day to see if you need any further help!
Same thing happening still
garwynn said:
Don't recall if the factory reset wipes USB storage, that would be the only possible difference.
Hope that gets you back into shape, will be checking during the day to see if you need any further help!
Click to expand...
Click to collapse
Same symptoms happened again. I am going to make another attempt based on the the previous method starting back at ics.
garwynn said:
Think it's part of the nodata flash effects still lingering.
Try this:
1) Flash FI27 full restore (rooted)
2) Reboot to Odin
3) Flash FK23 full restore (rooted)
That should fix it if it's old data not playing nice.
If it still happens after this the next step we'll do is check your battery.
Click to expand...
Click to collapse
This will sound like a very basic NOOB question but I want to ensure I do this exactly as suggested. I've flashed using SPH-D710_FI27_CL1127689_Rooted_Restore.
For reboot to Odin; Is that mean to boot by holding the Down Vol + Pwr then just powering down from that screen? Or possibly boot by holding Up + Vol and selecting one of those options?
I would also like to say THANK YOU to everyone who has been working on the D710. I've been following postings on this device and the knowledge everyone shares is simply amazing!!!
Still Freezing
kdean7 said:
This will sound like a very basic NOOB question but I want to ensure I do this exactly as suggested. I've flashed using SPH-D710_FI27_CL1127689_Rooted_Restore.
For reboot to Odin; Is that mean to boot by holding the Down Vol + Pwr then just powering down from that screen? Or possibly boot by holding Up + Vol and selecting one of those options?
I would also like to say THANK YOU to everyone who has been working on the D710. I've been following postings on this device and the knowledge everyone shares is simply amazing!!!
Click to expand...
Click to collapse
After installing SPH-D710_FI27_CL1127689_Rooted_Restore.exe, booting into odin mode, then installing SPH-D710_FK23_549262_Rooted_Restore.exe, I provided account information for Google and Samsung but this time did not allow the automatic reinstall of apps from the play store. The phone seemed to not exhibit any issues until after the apps shown as needing updates from the play store and the installation of IP Cam Viewer Pro, the phone again started freezing and became unresponsive.
I appreciate the suggestions but will move back to FI27 for a while.
kdean7 said:
After installing SPH-D710_FI27_CL1127689_Rooted_Restore.exe, booting into odin mode, then installing SPH-D710_FK23_549262_Rooted_Restore.exe, I provided account information for Google and Samsung but this time did not allow the automatic reinstall of apps from the play store. The phone seemed to not exhibit any issues until after the apps shown as needing updates from the play store and the installation of IP Cam Viewer Pro, the phone again started freezing and became unresponsive.
I appreciate the suggestions but will move back to FI27 for a while.
Click to expand...
Click to collapse
Think one of your apps may not like the JB build. You could try installing 1-2 at a time and see when it starts acting up to get a better idea of which one it may be...
Sent from my SPH-D710 using Tapatalk 2
Found app causing crash
Looks like I may have found the app causing the crash. Breaking News Newtork (BNN). I saw that it crashed after installing that app last time as I was taking everything very slow and testing after individual apps. It wasn't immediate upon install, only after a reboot. So far without that being reinstalled, things are still working. Still running with minimal apps but so far so good.
My rooted KF got bricked by the new OS update that was released last night. It boots as normal, gets to the locker screen, and whether you unlock it or not, reboots about 15 seconds later to a screen showing the Android guy and an exclamation point in a yellow triangle. Then, if you start touching the screen, 4 buttons will show up on the side, up/down, select, and back... but they do nothing. Reboot again and it takes me to TWRP.
I know how to wipe my KF and reinstall everything, but I was hoping that someone might know of a fix for this. Especially because I just got a new computer and am still in the process of getting my normal apps installed, let alone Android SDKs that I use once in a blue moon. Plus, I have a few games that I would rather not lose my progress on.
BTW, I rooted my dad's KF the exact same way as mine and his just lost root access with the update, everything else is fine. Kinda weird.
TIA
What OS update? Your new computer will not need sdk. Also you will not escape having to wipe if something has gone amuck, unless you get lucky to be able to flash the prior system to revert the defect. You could just flash modaco http://forum.xda-developers.com/showthread.php?t=1439916 no more losing root from OTA`S. You may also get lucky and be able to flash modaco if you`re on rooted stock or previously rooted stock 6.3.1 without wiping.
Thepooch said:
What OS update? Your new computer will not need sdk. Also you will not escape having to wipe if something has gone amuck, unless you get lucky to be able to flash the prior system to revert the defect. You could just flash modaco http://forum.xda-developers.com/showthread.php?t=1439916 no more losing root from OTA`S.
Click to expand...
Click to collapse
About 3am last night, I found my KF bricked after just using it about 30 minutes before (the wifi was on and it was hooked up to the charger). Today, I checked on my dad's KF and he has his wifi turned off. I turned it on and it instantly rebooted to just a "command line" screen saying that it was installing an update. Took about 10 minutes and then rebooted and worked fine, except that it was unrooted. I read somewhere in the Amazon Forums today that they did roll out an update and plan on spending 2 weeks doing it to keep from bogging down their network. Granted, their Software Update page doesn't say anything about it yet.
BTW, thanks for the other info, I'll have to check it out. Sounds like I'll have to wipe it (or at least restore from a 2-3 month old backup and see how the update goes again). But that's cool that I won't need to install the Android SDK.
Explains why some are instantly being unrooted or like in your case bricked strange thing is that it doesn`t change the system version it`s still 6.3.1 figures that Amazon would pull something like this.
Hey, I did manage to find a quick fix!
In the recovery mode, I decided to try using the Fix Permissions option. Still had the same problem.
I then just used the Clear Cache option and my KF was back up and running... and still rooted.
The only issue I have found so far is that I had to change the permission to allow changing the wallpaper, just uncheck the "write" permissions, (which was probably reset by the Fix Permissions option I ran). Other than that 2 second fix, everything is fine.
Granted, I'm waiting for Amazon to do an auto-check for some file that was in the cache that told it that it had installed the latest upgrade, and since I wiped that, it may install it again. If it does, I'll post it in this thread that my quick fix didn't work. But so far so good.
It turns out that my quick fix is only a temp fix.
Twice tonight I had to clear the cache again via the recovery menu. The first time it happened, I had just finished reading and hit the power button to put it in sleep mode, which caused it to instantly reboot and then do the same thing as I mentioned above. It boots up, and within 5 second of getting the locker screen, whether you unlock it or not, it starts shutting down and reboots ending up with the screen in the attached pic (those dots are just dust that appear super bright for some weird reason because you can't see them except in the pic).
So I cleared the cache again, everything was fine, and then about an hour later I found it sitting on that screen again. Clearing the cache fixed it again, but obvious this is a reoccurring problem.
Anyone have any ideas?
I'm reluctant to do a reinstall yet because I'm afraid I'll just end up with the same problem... along with none of my apps installed.
I have the same issue my temp solution is turn off wifi asap after lock-screen appear, wait abt 1-2 minutes then I can turn on wifi and use as normal.
Everything will fine for few hours. Any permanent solution plz? I remember that it occurred after i update something from Amazon app store, maybe : apps...
Sent from my Kindle Fire using xda premium
The permanent solution is to flash another rom preferably modaco if you want the stock experience. Full wipe, your apps can all be redownloaded that is the least of your worries at this point. probably a really good time to upgrade your bootloader and recovery if you haven`t flash both of these zips as zips in twrp if are behind the curve http://forum.xda-developers.com/showpost.php?p=30780737&postcount=180 and http://forum.xda-developers.com/showthread.php?t=1632375 only get them from where I`m directing you or use smirkit http://forum.xda-developers.com/showthread.php?t=1500935.
thanks for your help. This is done with the below solution
1) Copy the update bin file to the /sdcard as update.zip
Download stock ROM : https://s3.amazonaws.com/kindle-fire-updates/update-kindle-6.3.1_D01E_4107920.bin
copy update-kindle-6.3.1_D01E_4107920.bin into Kindle Fire and re-name to update.zip
2) From the main menu of CWM, "Wipe cache from partion" to remove the existing files in the data and cache partitions
3) From the main menu of CWM, press the "Install update.zip" button to flash the stock software onto your device.
no data/application lost accept FFF and CWM
Wiping cache doesn`t remove data in twrp its factory reset that you need to concern yourself with and unfortunately there is data loss. You may have succeeded but others put themselves in a position of needing a factory cable after not properly wiping when flashing stock. This is because the data is what the kindle has a tough time handling after a complete stock flash. Flashing modaco is far safer, truth is that it will leave your recovery and bootloader intact providing a far better safety net if something were to go wrong. Also if you create a backup before you flash if something does go wrong at least you can restore a half crap backup, wipeout recovery and this is no longer possible just saying. I see far more people fail to flash stock than I ever do flashing modaco.
Thanks for the info guys.
Considering the post in the Amazon Forums said this update was being pushed out over a 2 week period, I'm just going to keep my WiFi off (unless needed) and wait until everyone should have received the update and then see how it plays out. Considering it doesn't change the software version number, I'm thinking that this update may be just targeting rooted Fires. And BTW, it appears that the post was removed, because I can't find it again. Maybe they remove any that mention rooting? I just stumbled upon it via a Google search... 99% of the question in their forum are just idiotic.
Directv used to pull this stunt all the time to bust people with hacked cards that allowed them to get all their channels for free (usually a few hours before some big PPV event). They finally completely stopped the ability to hack cards by rolling out parts of their code over a long period of time, a year or so. When the final piece was put in place, the previous parts of their code had already been integrated into the hacked card software, because it appeared safe, and along with upgrading the type of cards they used during that same period of time, pretty much eliminated the ability to cheat Directv. I'm not saying that Amazon is going to those lengths to stop people from rooting their KFs,.. but who knows? It may be costing them too much with people bricking their KFs by trying to root them. Plus, they may also be losing revenue by people getting their free apps (with ads) from the Playstore instead of Amazon. And considering they pretty much sell their Fires for cost, they definitely rely on revenue generated by buying and using things via a stock KF.
BTW, this whole issue had almost perfect timing... I was planning on wiping my KF because it definitely is slower than when I first got it (which was day 1 of its release). I've read that Gingerbread doesn't clean up after itself too well, especially not as good as ICS (kinda like a Windows registry just gets filled with junk over time, and no cleaner beats a fresh install). It also appears that the ICS roms are actually working reliably these days, compared to the last time I checked. So, in a couple weeks, I'll get to have some fun. I am a Windows/Cisco System Engineer, so this kinda stuff is fun for me.
F.Y.I.
It seems that Amazon did do a incremental update on the Original Kindle Fire version
6.3.1_user_4107720, April 30 build to 6.3.1_user_4107920, November 27 build.
I looked thru the update and the only things I found changed are to do with the
Wifi driver, launcher icons, boot animation, and boot.img; attached the changed file below.
I have not tried to update mine, will attempt this weekend.
Thank you Tera Tike for the info at least this confirms that it's not just a fluke users of rooted stock should be warned appreciate your research. I do wonder why they would change boot animation and IMG seems a bit haneous.
Thepooch said:
Thank you Tera Tike for the info at least this confirms that it's not just a fluke users of rooted stock should be warned appreciate your research. I do wonder why they would change boot animation and IMG seems a bit haneous.
Click to expand...
Click to collapse
It seems they increased the resolution of the images in the file, but for me I can not see the difference.
For me I wonder what they changed in the WiFi driver file, tiap_drv.ko.
Kindle Fire Reboot Problem Solved - Install MoDaCo Rom
Thepooch said:
Wiping cache doesn`t remove data in twrp its factory reset that you need to concern yourself with and unfortunately there is data loss. You may have succeeded but others put themselves in a position of needing a factory cable after not properly wiping when flashing stock. This is because the data is what the kindle has a tough time handling after a complete stock flash. Flashing modaco is far safer, truth is that it will leave your recovery and bootloader intact providing a far better safety net if something were to go wrong. Also if you create a backup before you flash if something does go wrong at least you can restore a half crap backup, wipeout recovery and this is no longer possible just saying. I see far more people fail to flash stock than I ever do flashing modaco.
Click to expand...
Click to collapse
I took Thepooch's advice and installed MoDaCo rom on my KF. It was a snap. I had FireFireFire installed with TWRP. Just downloaded MoDaCo to PC copied to KF. Rebooted to FireFireFire Installed with Install Zip utility. Took a few minutes. Rebooted didn't loose any data , apps or functionality. Its still rooted. THANKS!
No problem you can find the entire uncomplicated method here http://forum.xda-developers.com/showthread.php?t=1923010 or at least a synopsis of the concept.
I have been on all the Root66 versions, and have had no problems ever...... till this UVDM5
I made a CWM backup (2 just to be sure) and proceeded to flash this new version that I have been waiting for so anxiously!
After it booted up, my desktop was the same, and all the apps showed, but talkback was already turned on, and I could no way get to the settings to turn that #$%%$ thing off. Heck, I could not even get to anything at all. It kept talking and reciting numbers everytime I tried to do anything. It was "Frozen" on the main homescreen, and could not do anything. I sometimes could get to the app drawer and that, too, would not scroll or do anything. I Re-flashed the thing after doing another download with the usual cache, dalvic blow out, and it acted the same way...
I decided to revert to the backup and tried to get to recovery (CWM).... That, too was gone! Stock recovery. I flashed the only version I had of CWM and it booted, and declared both of my backups were "corrupt" after it was almost done restoring?????? WTF!!!
I then reloaded UVDMD5 again, got the same results so did a factory restore and got to install my ROM manager, and re-flashed CWM to the version it uses, and tried the restore.....
It worked, and now after some pressure packed moments, I'm back to the UVLJA. I have to go on a trip tomorrow, (in a few hours) and need the phone working. PHEW! if anyone knows why the hiccup that I had occurred, please chime in and let me know. I still want the new OS and after my return, I plan to do the update again.... Hopefully....... Just gotta ccalm m my nnnneerves a bit before I attempt it again!
bobolinko said:
I have been on all the Root66 versions, and have had no problems ever...... till this UVDM5
I made a CWM backup (2 just to be sure) and proceeded to flash this new version that I have been waiting for so anxiously!
After it booted up, my desktop was the same, and all the apps showed, but talkback was already turned on, and I could no way get to the settings to turn that #$%%$ thing off. Heck, I could not even get to anything at all. It kept talking and reciting numbers everytime I tried to do anything. It was "Frozen" on the main homescreen, and could not do anything. I sometimes could get to the app drawer and that, too, would not scroll or do anything. I Re-flashed the thing after doing another download with the usual cache, dalvic blow out, and it acted the same way...
I decided to revert to the backup and tried to get to recovery (CWM).... That, too was gone! Stock recovery. I flashed the only version I had of CWM and it booted, and declared both of my backups were "corrupt" after it was almost done restoring?????? WTF!!!
I then reloaded UVDMD5 again, got the same results so did a factory restore and got to install my ROM manager, and re-flashed CWM to the version it uses, and tried the restore.....
It worked, and now after some pressure packed moments, I'm back to the UVLJA. I have to go on a trip tomorrow, (in a few hours) and need the phone working. PHEW! if anyone knows why the hiccup that I had occurred, please chime in and let me know. I still want the new OS and after my return, I plan to do the update again.... Hopefully....... Just gotta ccalm m my nnnneerves a bit before I attempt it again!
Click to expand...
Click to collapse
It seems to be an issue with the latest version of TalkBack on most roms. I had the issue already and from what I read in the forums, many other people have to. My advice, as soon as you flash a rom, uninstall or freeze talkback and DO NOT let it update to the latest version. Im not too sure what the issue is but hope Google fixes that soon.
I think also that I had a problem before when I installed the stock 4.1.2, it seemed to take my sdcard and renamed it to 0 on the sdcard. Took me a few hours to figure that out. I then copied everything that was in the folder 0 over everything in the root of the sdcard and it was back to normal.
Thanks! (Clicked it already)
I did notice a LOT of stuff was on the external card after the final recovery to the older version and had to clean up the external SD card.
You were right! I had no means to freeze the TalkBack, or do anything at all while within the OS itself, so no alternative was available to me at that time except a Factory Restore. The re-installation of my software was just going to take too long, so I did a recovery using the same version of CWM and was back where I was before the fiasco. Good thing I got it going.... Ida been really screwed! LOL. I'll try again maybe later, when I get home.
When I do try again, I'll remove the SD Card and then do the install using a spare one.
Have a great day!
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.