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.
Related
I have a Galaxy Nexus GSM phone running Android 4.0.2. Occasionally I am noticing the following behavior:
The Data Usage section in the Settings when clicked freezes, becomes completely unresponsive and the whole Settings app needs to be "killed" using the "Recent apps" in order to function again. When I click on Data Usage again, though, the Settings app freezes again.
I noticed that when this happens the phone's wake time becomes significantly higher. The battery stats show that it is almost constantly awake even if the screen has been off for hours. Going through the application list in the Battery stats shows that "Android system" is keeping the phone awake.
I found a temporary solution to be the following - connect to a wifi network, open the browser and browse through 1-2 pages, then turn the wifi off again. This makes the Data Usage section become responsive again and the Awake time becomes significantly lower.
However, the bug comes back again in a few hours - usually in about 8-12 to 24 hours or so (I have not found any pattern and the timeframe varies greatly).
I did a factory reset and it helped for 2-3 days and then the issue started appearing again.
I have seen many threads describing battery issues but not with this exact pattern and I decided to share and see if anyone else is experiencing it?
Upping the thread a little...
I also have experience this. Yesterday I restarted my phone on a place where I have no known wifi networks and I cannot access the Data usage menu and my attempt freezes the settings window. My nexus keep awake all the time. I fixed it later by connecting to to wifi.
I experienced this before and in situation where you start the phone with wifi off, and again fixed it when you turn it on and connect to a network.
Samsung Galaxy Nexus 4.0.2.
Were you able to find a more permanent solution, apart from connecting to a wifi temporarily? This solution woks only for a little time for me and then the problem re-appears.
Personally, since the hardware itself works fine, I'd backup everything and flash the stock image from Google. If you're not comfortable with that, then have your phone swapped out under warranty. This sounds like a bad flash (before reflashing to get 4.0.4, my data viewer would miss entire apps and occasionally reset itself mid-cycle, defeating its entire purpose), so those are really your only two options.
You could also see if there's a random app causing problems, but I doubt that's the issue here.
ATnTdude said:
Personally, since the hardware itself works fine, I'd backup everything and flash the stock image from Google. If you're not comfortable with that, then have your phone swapped out under warranty. This sounds like a bad flash (before reflashing to get 4.0.4, my data viewer would miss entire apps and occasionally reset itself mid-cycle, defeating its entire purpose), so those are really your only two options.
You could also see if there's a random app causing problems, but I doubt that's the issue here.
Click to expand...
Click to collapse
Thank you for your suggestions. I have recently made a factory reset and the problem was still there, so I believe it is not caused by a 3rd patry app.
I am willing to try flashing the Google stock image. I believe I can find more details how this is done but do you think that I will be able to do it if I am not rooted?
wyvorn said:
Thank you for your suggestions. I have recently made a factory reset and the problem was still there, so I believe it is not caused by a 3rd patry app.
I am willing to try flashing the Google stock image. I believe I can find more details how this is done but do you think that I will be able to do it if I am not rooted?
Click to expand...
Click to collapse
Download the Nexus Toolkit from this thread:
http://forum.xda-developers.com/showthread.php?t=1454314
1) Select your model of phone (I'm assuming GSM/HSPA since you're from Europe)
2) Click the "Drivers" button and follow all prompts to download and install the needed PC drivers.
3) (Optional) Click Backup Apps + Data. Follow on-screen instructions to save all of your apps to your PC, because we will be wiping your phone in the next step. Do NOT save system apps and settings, since you have a bad flash. If you have anything saved to the virtual SD card, copy it off now as well.
4) Put your phone into fastboot mode (turn off, then hold Volume + and - at the same time and then press powe button). Click "Unlock" button on tollkit and follow all prompts. This will unlock your bootloader. This will also erase everything on your phone. Your phone will reboot when it's done. Turn it back off and boot back into fastboot.
5) Click "Flash Stock and Unroot" on toolkit. This will download the proper files from Google and flash your phone. Your phone will be factory-new. It will not be rooted.
6) (Optional) You can also click "OEM Lock" button if you want to relock your bootloader. This really doesn't make a difference if you're planning to stay on stock ROM. Personally, I'd keep it unlocked unless you plan on exchanging the phone.
7) Click Restore Apps + Data if you backed up your apps from before.
ATnTdude said:
Download the Nexus Toolkit from this thread:
http://forum.xda-developers.com/showthread.php?t=1454314
1) Select your model of phone (I'm assuming GSM/HSPA since you're from Europe)
2) Click the "Drivers" button and follow all prompts to download and install the needed PC drivers.
3) (Optional) Click Backup Apps + Data. Follow on-screen instructions to save all of your apps to your PC, because we will be wiping your phone in the next step. Do NOT save system apps and settings, since you have a bad flash. If you have anything saved to the virtual SD card, copy it off now as well.
4) Put your phone into fastboot mode (turn off, then hold Volume + and - at the same time and then press powe button). Click "Unlock" button on tollkit and follow all prompts. This will unlock your bootloader. This will also erase everything on your phone. Your phone will reboot when it's done. Turn it back off and boot back into fastboot.
5) Click "Flash Stock and Unroot" on toolkit. This will download the proper files from Google and flash your phone. Your phone will be factory-new. It will not be rooted.
6) (Optional) You can also click "OEM Lock" button if you want to relock your bootloader. This really doesn't make a difference if you're planning to stay on stock ROM. Personally, I'd keep it unlocked unless you plan on exchanging the phone.
7) Click Restore Apps + Data if you backed up your apps from before.
Click to expand...
Click to collapse
The steps that you provided worked very well (I hit a few bumps with the drivers but managed to work them out). I re-flashed the stock image and everything seems to be OK so far. I will be checking if the problem with the Data Monitor is resolved and will report here.
Thanks so much for your help!
damencho said:
I also have experience this. Yesterday I restarted my phone on a place where I have no known wifi networks and I cannot access the Data usage menu and my attempt freezes the settings window. My nexus keep awake all the time. I fixed it later by connecting to to wifi.
I experienced this before and in situation where you start the phone with wifi off, and again fixed it when you turn it on and connect to a network.
Samsung Galaxy Nexus 4.0.2.
Click to expand...
Click to collapse
Something similar is happening on my LTE Galaxy Nexus in the Settings Menu. After a while when I click 'More' in the Settings menu the Settings app freezes and must be closed, otherwise the phone is inoperable.
What's scary is that it started happening AFTER I flashed the recovery image, because I enabled encryption while running a custom ROM, so the only way out was to flash the recovery images from scratch. Perhaps something went wonky during the flashing process, so I am going to follow the steps listed in a later thread.
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 rooted and ran a couple diff custom ROMs: cm10.1.3 and infamous alpha, both with oc kernels (never set mhz past 2051). Began getting random reboots, alot while running the Alpha ROM, and a couple while running cm10.1.3 which I thought was weird because its a RC. should be stable, right? Anyway, got tired of RRs, so I decided to unroot and got stock, till I had some free time.to tinker with it. Well guess what, getting RRs EVEN IN UNROOTED STOCK. Any ideas?
I'm not exactly sure what steps you have taken to get back to Stock, where you're still having random reboots, but I'll let you know what I've done in the past to get to Stock which resolved the issues:
- Factory reset device from device. Save and/or move your Internal files/data prior as you'll be wiping Internal. I'd remove my extSdCard prior to Factory reset and after moving files to it.
- ODIN Samsung Stock Firmware
http://samsung-updates.com/details/9595/Galaxy_S_4_T-Mobile/SGH-M919/TMB/M919UVUAMDL.html
- After the device boots, you'll probably get stuck on the Samsung splash boot screen. After a few minutes - -
- pull the battery, replace the battery but Don't power the device on
- Place device in Stock Recovery mode by pressing Power and Vol up buttons at the same time.
Release the buttons when you see the blue letters appear in the upper left hand corner of the screen.
- Scroll to Factory reset using the volume buttons.
(During the above process, you'll see the Android on its side with a Red X on him/her.)
- press the power button to lock in Factory reset
Let the Recovery scroll through its script
(during this process the Android will come to life )
- After the script is completed which takes less than a minute or so, scroll to reboot and select it with the power button.
- the device will now boot.
Important: while the device is booting, the screen will stay on the T-Mobilessplash screen for what will seem forever. Don't panic. The screen will show T-Mobile across the screen for about 15 or so minutes. Could be a little more or a little less. The device will then continue and complete the booting cycle.
Some notes:
1) during the above process, I have removed my extSdCard card as I didn't want tottake a chanceiit would be wiped. ODIN doesn't wipe extSdCard card but I don'tbneed it during theiprocess so I remove it in case Murphy decides to pay a visit.
2) during ROM flashes, I've experienced almost every issue youccan imagine. This occurred while using TWRP 2.5.0.2, but only when flashing ROMs with Aroma. For months prior, I had zero issues.
The problems I was experiencing were:
Random reboots, splash screen freezes, bootloops, installation of choices in Aroma which only partially installed, issues which didn't seem to havesan answer, and when you found the solution, that solution wouldn't work when the issue appeared again.
- constantly ODINing back to stock
- sometimes in Recovery, I couldn't get past the TWRP lockscreen, and only wiping Internal SD resolved the issue so I could do a Factory reset. I was doing this so often, that I left all files on my extSdCard so Iewouldn't lose my data when I had to wipe internal. It was faster this way as I didn't have to keep moving stuff back & forth.
After endless hours of troubleshooting and aggravation, I changed Recoveries.
I installed Philz Touch Recovery, and I have had Zero issues since installing it about 3 or so weeks ago, which have included multiple ROM flashes with Aroma.
I didn't want to switch Recoveries as I was very used to TWRP, but I just couldn't deal with the new found issues I was having so I made the switch and haven't looked back. Some people don't have issues with TWRP, but I wasn't one of them
Hopefully you can relate to some of my experiences which I have written above, which may help you to resolve some of the issues you're experiencing.
Yes. Thats the file I used and also the steps. I dont know what the deal is.
twatts723 said:
Yes. Thats the file I used and also the steps. I dont know what the deal is.
Click to expand...
Click to collapse
If you:
Wiped Internal SD
ODINd Stock Firmware
which flashed successfully
and are still having random rebooting.....
I can only suggest:
Check your device settings, if you haven't done so already to insure you're running:
Stock ROM
Stock modem/radio
And that all settings are stock.
If everything checks out, I can only suggest to:
Download the Samsung Stock Firmware file again
Check the md5 checksum
ODIN Samsung Stock Firmware again
And see how it goes.
So it turns out, if once you flash the stock firmware through odin, you just have to let it "settle in" for a couple days and all the problems go away. Thanks man.
twatts723 said:
So it turns out, if once you flash the stock firmware through odin, you just have to let it "settle in" for a couple days and all the problems go away. Thanks man.
Click to expand...
Click to collapse
Glad everything worked out for you.
Don't shy away from custom ROMs though, as you'll be missing out on some good stuff
As a note, there can be many thinks which can contribute to issues after the installation of a Custom ROM, Kernels, etc. such as:
Bad downloads, corrupted files, app conflicts, dirty flashes instead of Full wipes, etc., etc.
Another issue can be related to the Recovery you are using.
I had many, many issues regarding flashing ROMs which installed with Aroma.
Prior to ROMs w/Aroma, I had Zero issues.
I suggest using Philz Touch Recovery.
In case you don't have it installed and want to try it, I'll post a link to the download page.
Flash the proper file for your specific carrier.
Install the tar file with ODIN or
Flash the zip file with your Recovery......
Well, I come from sgs2. On that device, I could flash everything through cmw, and just use darkside super wipe and darkside cache wipe. No problem. Every rom from cm to amatuer custom blibbidy blobbidy, no problem. When I rooted my s4, I went straight to twrp because everyone said it was better. I flashed cm10.1.3 rc - rr. Infamous alpha v.7, which was supposed to be stable - rr. I went back to stock, rooted again, and kept stock tw, and only flashed ktoonz kernel, which is supposed to be one of the best for this device. Everything ran great, but guess what - rr. So I gave up. Went back totally stock. Working a lot of hours at work right now. We slow down after thanksgiving, so I'll probably start flashing again around that time. Thanks for thw help though
cheers.
I've got a T-Mobile Note 3 that I picked it up on launch day last Thursday at a T-mobile store. I proceeded to root the phone with Odin, then restore via Titanium Backup and then fix the backup with "restorecon -R -v /data". Life has been great until last night. Initially I got a circle with a line through it instead of the mobile signal and my cellular link would not connect, but my wifi was fine. When the problem was sill occurring this morning I figured it was an odd cellular problem and rebooted the phone this morning when it persisted. Now the phone is rebooting a few minutes after it completes booting.
It will boot normally, then I'll unlock the phone and get my window manager (Holo)...then I'll get the error "Process system isn't responding. Do you want to close it?". Then I get the error "Unfortunately, Favorite Apps has stopped." Regardless whether I interact with those error messages the phone then reboots a minute later. I have *not* done a restore from CWM ever and the phone doesn't seem to have suffered any physical damage.
The things I've tried include:
*) power down, remove sdcard, then reboot
*) power down, remove sim card, then reboot
*) power down, remove sim card, remove sdcard, then reboot
*) clear cache, then reboot
*) clear dalvik-cache, then reboot
*) clear dalvik-cache and cache, then reboot
*) clear dalvik-cache, clean cache, then wipe to factory, then reboot
In all the above scenarios nothing has changed. The phone reboots after it completes booting.
In the past, I've rooted and flashed on a G1, a G2, and an S3. I've bricked my S3 that had to be repaired via JTAG. This reboot problem with my Note 3 is completely unlike any of the things I've seen with previous phones.
I've read through some of the other threads about reboot loops, but all the threads I've read were caused by a CWM restore and have no solution yet.
Does anyone know the cause of this and what could fix it?
digitalfiend said:
I've got a T-Mobile Note 3 that I picked it up on launch day last Thursday at a T-mobile store. I proceeded to root the phone with Odin, then restore via Titanium Backup and then fix the backup with "restorecon -R -v /data". Life has been great until last night. Initially I got a circle with a line through it instead of the mobile signal and my cellular link would not connect, but my wifi was fine. When the problem was sill occurring this morning I figured it was an odd cellular problem and rebooted the phone this morning when it persisted. Now the phone is rebooting a few minutes after it completes booting.
It will boot normally, then I'll unlock the phone and get my window manager (Holo)...then I'll get the error "Process system isn't responding. Do you want to close it?". Then I get the error "Unfortunately, Favorite Apps has stopped." Regardless whether I interact with those error messages the phone then reboots a minute later. I have *not* done a restore from CWM ever and the phone doesn't seem to have suffered any physical damage.
The things I've tried include:
*) power down, remove sdcard, then reboot
*) power down, remove sim card, then reboot
*) power down, remove sim card, remove sdcard, then reboot
*) clear cache, then reboot
*) clear dalvik-cache, then reboot
*) clear dalvik-cache and cache, then reboot
*) clear dalvik-cache, clean cache, then wipe to factory, then reboot
In all the above scenarios nothing has changed. The phone reboots after it completes booting.
In the past, I've rooted and flashed on a G1, a G2, and an S3. I've bricked my S3 that had to be repaired via JTAG. This reboot problem with my Note 3 is completely unlike any of the things I've seen with previous phones.
I've read through some of the other threads about reboot loops, but all the threads I've read were caused by a CWM restore and have no solution yet.
Does anyone know the cause of this and what could fix it?
Click to expand...
Click to collapse
I would just Odin to stock and restart. I'm guessing some app your restored form another phone did it.
YellowGTO said:
I would just Odin to stock and restart. I'm guessing some app your restored form another phone did it.
Click to expand...
Click to collapse
I don't believe it was an app that was restored because the restore had run perfectly for 5 full days. I completed the restore last Thursday...that's what makes this so unusual.
Do you know where to get the stock zips to use with Odin?
digitalfiend said:
I don't believe it was an app that was restored because the restore had run perfectly for 5 full days. I completed the restore last Thursday...that's what makes this so unusual.
Do you know where to get the stock zips to use with Odin?
Click to expand...
Click to collapse
There's some stock Odin tar files in the Android development forum. Download and flash using Odin. Once it reboots, remove battery and manually boot into stock recovery and do a factory reset/wipe. Reboot and it should work.
Sent from my SGH-T889
jmerlos said:
There's some stock Odin tar files in the Android development forum. Download and flash using Odin. Once it reboots, remove battery and manually boot into stock recovery and do a factory reset/wipe. Reboot and it should work.
Sent from my SGH-T889
Click to expand...
Click to collapse
It looks as if the stock tar in zip format (N900TUVUBMI7_N900TTMBBMI7_TMB.zip) can be downloaded from either of these links:
http://forum.xda-developers.com/showthread.php?t=2465764 (faster download link)
http://forum.xda-developers.com/showthread.php?t=2468275 (slow download link)
I just finished downloading from the first link and after extracting the zip file I have these files:
N900TUVUBMI7_N900TTMBBMI7_N900TUVUBMI7_HOME.tar.md5
SS_DL.dll
This seems like an obvious thing, but want to ask because of how odd this problem is: Do I simply flash the "N900TUVUBMI7_N900TTMBBMI7_N900TUVUBMI7_HOME.tar.md5" file the same way that I flashed the CWM through Odin?
Yes, but IIRC, just uncheck reboot, reboot manually into recovery, then wipe, factory reset, etc. Pull your battery, reboot. Check the TWRP thread, it has exact directions.
sgh-TWEAKED-889©
Warrior1975 said:
Yes, but IIRC, just uncheck reboot, reboot manually into recovery, then wipe, factory reset, etc. Pull your battery, reboot. Check the TWRP thread, it has exact directions.
sgh-TWEAKED-889©
Click to expand...
Click to collapse
Got it, thank you! Here's what I'm referencing for the Odin options:
http://forum.xda-developers.com/showpost.php?p=46110842&postcount=2
I'll flash this and update the thread.
Good luck bro!!
sgh-TWEAKED-889©
Ok, I flashed with Odin then once it completed I got the "PASS!" status in Odin. I shut down Odin, pulled the battery from the Note 3, then allowed the phone to boot. There was a "booting recovery" message in blue at the top of the screen before the phone booted, then it booted to the "samsung logo", then the animated circular logo, then the white screen with the "T-Mobile 4G LTE" logo, then rebooted. The second boot, it did the same thing but stayed on the "T-Mobile 4G LTE" screen for many minutes...then it seemed as if it was completing it's reboot because I got the notification bar with the time and the circle with the line through it for the cell signal strength. I got the same error when the phone seemed to have completed booting, then a reboot. Now it's back to the same place it started in it's rebooting cycle.
This makes absolutely no sense at all. If I'd have done a CWM restore then I could understand that...but there's no reason for this that I can see. The phone acts as if it was knocked off of the T-Mobile network and now it finishes it's booting cycle long enough to be rebooted.
So now I have a useless Note 3. I'm game for taking the phone back to the T-Mobile store and requesting that they replace the phone, which they probably would, but I have no guarantee that this wouldn't happen again. I'm open to suggestions as long as they don't cause me to brick my phone completely.
I finished installing TWRP and darthrom successfully. However, after the darthrom finishes booting I have the exact same problem with the phone rebooting that the stock ROM had.
I'm back to square one.
I'm open to suggestions.
There are a lot of people having boot loop problems even without root though they are spread out among various sub forums. Try this thread for example:
http://forum.xda-developers.com/show....php?t=2467005[Q] Reboot cycle after restart help
Sent from my SAMSUNG-SGH-I317
Dumbo53 said:
There are a lot of people having boot loop problems even without root though they are spread out among various sub forums. Try this thread for example:
http://forum.xda-developers.com/show....php?t=2467005[Q] Reboot cycle after restart help
Sent from my SAMSUNG-SGH-I317
Click to expand...
Click to collapse
I saw a couple threads last night when I was searching around on the web about other models of phones with SIM socket and SIM card issues. I'm beginning to think that my issue is hardware-related, and not software. I did another wipe last night based on this thread's post: http://forum.xda-developers.com/showpost.php?p=46157872&postcount=6&nocache=1&z=7848000959493220
Instead of simply wiping, I formatted /data/, then wiped, then I flashed on the stock ROM, then flashed on the darth rom. I got slightly different results once the phone was done with it's firstboot - it kept giving me the error that a new SIM card had been installed and the phone needed to be rebooted. This causes me to suspect the physical hardware of my Note 3 or the SIM card. I have ruled out the SIM card because I've been using it in my old G2 since this started, via an adapter for the G2's SIM socket, and it's been fine. I'm planning on taking the phone to T-Mobile today and seeing what they can sort out with either a SIM exchange or phone exchange.
The note 3 misbehaved the same way while in the T-Mobile store. They swapped the phone out under warranty after asking only the basic questions and trying a factory reset. The same SIM card in the new note 3 works fine.
I'm on the same boat. Got my Note 3 this morning, rooted an hour ago with CMW, made backup and flashed Stock ROM from Jovy. Result: bootloop. Restore backup and still on bootloop. DLing the Odin stock .tar to see if it helps. Any more suggestions?
Edit: After flashing with Odin the stock tar from Sammy all it's good...at least for now.
Wally72 said:
I'm on the same boat. Got my Note 3 this morning, rooted an hour ago with CMW, made backup and flashed Stock ROM from Jovy. Result: bootloop. Restore backup and still on bootloop. DLing the Odin stock .tar to see if it helps. Any more suggestions?
Edit: After flashing with Odin the stock tar from Sammy all it's good...at least for now.
Click to expand...
Click to collapse
How far into the booting process would you get before the phone rebooted?
digitalfiend said:
How far into the booting process would you get before the phone rebooted?
Click to expand...
Click to collapse
Never passed Samsung! In my case, flashing the .tar with Odin from Samfirmware fixed my issue. I think imma wait for a more stable recovery.
Sent from my SM-N900T using Tapatalk now Free
Wally72 said:
Never passed Samsung! In my case, flashing the .tar with Odin from Samfirmware fixed my issue.
Click to expand...
Click to collapse
Interesting...it sounds like you had the boot loop that many others have had...it's cool to hear that you got it fixed. I think my problem was hardware-based since the phone completed it's boot process and *then* had issues. Luckily T-Mobile was there for me and helped out.
Wally72 said:
I think imma wait for a more stable recovery.
Click to expand...
Click to collapse
I know what you mean as far as waiting for a stable recovery. If it's any help, I've decided to stay far away from the recovery restore and simply use Titanium backup to do restores. It's more work than a nandroid recovery, but it reliably does it's job well for me.
digitalfiend said:
Interesting...it sounds like you had the boot loop that many others have had...it's cool to hear that you got it fixed. I think my problem was hardware-based since the phone completed it's boot process and *then* had issues. Luckily T-Mobile was there for me and helped out.
I know what you mean as far as waiting for a stable recovery. If it's any help, I've decided to stay far away from the recovery restore and simply use Titanium backup to do restores. It's more work than a nandroid recovery, but it reliably does it's job well for me.
Click to expand...
Click to collapse
Well...I'm doing a lot of reading. I can't stand this "stock look" and me, every time I root a phone, I always do my own modifications within the ROM I choose to flash. SystemUI and apk's. I only change the .png's, therefore, getting the visual look I want/like. Always done it with certain ROMs/Themes. I downloaded Jovy's stock ROM and made the visual changes I wanted. I flashed and got into that bootloop scenario. Restore backup with CWM provided by Zedomax and made it worse. I think the problem is recovery (at least from what I've read). In this case, CWM been less unstable than TWRP. I f you read a bit around, must ppl if not all, had the "dead bootloop" issue with TWRP. I haven't read from anybody yet having the "dead bootloop" with CWM. Ppl with CWM that flashed their backup and got that bootloop, fixed it flashing back to stock, where ppl that had TWRP have tried to flash back to stock and their phones never boot completely
Again...imma wait a little more for good reports as far as recovery goes!
Bigbiff has a file he uploaded, it may be a fix for the bootlooping issue. You'd be the first to try at this point. It's linked below, but the entire thread is in the OG development of tmobile.
http://forum.xda-developers.com/showthread.php?p=46379854
sgh-TWEAKED-889©
I've never seen so many issues with a brand new flagship phone before. Makes me think it wasn't tested fully before release. I mean all these problems!
Even though I returned my N3 after I tried restoring and getting bootloop of death, I feel this model is really flawed. Hearing new things everyday.
So I got a warranty refurb sent to me from Google I started it up and loaded it up from a backup.
Since then I just manually install my apps don't restore from backup up the back up seems to be worse right away.
From the factory room I tied a factory reset and on setting up the phone Google play services would crash instently couldn't do anything same after the next factory resetnusing the recovery menu of holding power button then long hitting volume up.
So that's when I reflashed updated factory rom.
Since day one Google service, Google maps, Google photos and Google play services all have random crashes they seem to happen the most around 4am 12pm 4pm 7pm
I have tried deleting app caches and storage still happens I have removed myself from the beta programs still have issues
I have factory reset a few times I've gone a day without installing third party apps and I just can't go without something's but even no third party apps I have issues but less
I have reloaded the Android rom to both partition a and b and I seem to get an issue on partition a seems to always never boot stays at the loading screen some times I boot and it's like the radio never booted says no sim and no signal reboot and everything works.
Sometimes when having crashing issues the apps will get very pixilated looking in the app drawer also on a boot I had the Google splash screen fill-up the whole screen and poor quality.
From what I know about pcs typically I'd start testing ram and hdd if those were good then I'd say the motherboard is bad and then that's usually the end of issues
Anyone got ideas I can try. Are there ways to test ram and storage?
gjkrisa said:
So I got a warranty refurb sent to me from Google I started it up and loaded it up from a backup.
Since then I just manually install my apps don't restore from backup up the back up seems to be worse right away.
From the factory room I tied a factory reset and on setting up the phone Google play services would crash instently couldn't do anything same after the next factory resetnusing the recovery menu of holding power button then long hitting volume up.
So that's when I reflashed updated factory rom.
Since day one Google service, Google maps, Google photos and Google play services all have random crashes they seem to happen the most around 4am 12pm 4pm 7pm
I have tried deleting app caches and storage still happens I have removed myself from the beta programs still have issues
I have factory reset a few times I've gone a day without installing third party apps and I just can't go without something's but even no third party apps I have issues but less
I have reloaded the Android rom to both partition a and b and I seem to get an issue on partition a seems to always never boot stays at the loading screen some times I boot and it's like the radio never booted says no sim and no signal reboot and everything works.
Sometimes when having crashing issues the apps will get very pixilated looking in the app drawer also on a boot I had the Google splash screen fill-up the whole screen and poor quality.
From what I know about pcs typically I'd start testing ram and hdd if those were good then I'd say the motherboard is bad and then that's usually the end of issues
Anyone got ideas I can try. Are there ways to test ram and storage?
Click to expand...
Click to collapse
From your post, I'm really not sure If I understand how you first started out of the box, but you did eventually flash a full Google image without modifying the flash-all script, right? In other words you did not remove the "-w" switch and allowed the script to wipe data and begin fresh? Before ruling it a hardware issue, you may want to try Deuce's Script which seems to have some success in restoring the phone to a factory state and recovering from various problems. Try to avoid the temptation of just jumping in and running the script... take the time to read up first before you get started. Best of luck! :good:
v12xke said:
From your post, I'm really not sure If I understand how you first started out of the box, but you did eventually flash a full Google image without modifying the flash-all script, right? In other words you did not remove the "-w" switch and allowed the script to wipe data and begin fresh? Before ruling it a hardware issue, you may want to try Deuce's Script which seems to have some success in restoring the phone to a factory state and recovering from various problems. Try to avoid the temptation of just jumping in and running the script... take the time to read up first before you get started. Best of luck! :good:
Click to expand...
Click to collapse
Returned previous phone because the vibrate motor stopped and thought it would be nice to get a newer phone that wasn't rushed released maybe.
When flashed new rom yes just ran the script since all you need to do is double tap on it as long as all updated adb/fastboot is in same folder also looked up how to manually switch partition which looked like it was only doing one partition.
Thanks you for letting me know about the other script I'll try that.
Sent from my Pixel 2 XL using Tapatalk
Tried it still same issue most time the issues would be non existent untill I opened an app at the wrong time then it was like i got hit with a virus or something.
But sent out the refurb got another refurb have had 0 issues thank goodness! Glad I'm done with that.