Develop Bugs

Issue trying to update to 4.3

(Originally posted this in the wrong forum, so I am reposting here.)
I have the Galaxy Note II with T-Mobile.
Some background: It was running Android 4.1.2. I rooted my phone once, about two weeks ago, just so I could take an image of it in case of an update issue. (I think the software was called nandroid.) Once I took the backup, I unrooted it again.
Since then, doing the Software Update check under settings never returned any results. It would just keep checking until I clicked cancel.
Anyway, when T-Mobile released the 4.3 update Monday morning, I tried updating to it using the Kies software on my PC (by connecting it through the USB cable). It got up to about 60% installation and then just hung for over an hour. So I unplugged the phone, re-plugged it back in, and then attempted the emergency firmware recovery through Kies. It went through this and got upto 76% installation and then just hung again for another hour. I again unplugged it to re-try the emergency recovery again, but every time I connected the phone, Kies would not detect it again. I re-seated the battery, rebooted my computer, uninstalled and reinstalled Kies, but Kies would not detect my phone again.
I am/was running the stock rom, but my phone won't even boot into it's normal screen. Any time I turn it again, i see the screen--"there were errors during firmware upgrade. try emergency recovery in Kies."
I can't even figure out a way to get to a screen where I can install the image I took using Nandroid a few weeks ago.
Any help or advice anyone can provide would be extremely appreciated!

Use Odin to fix it.
If you can put your phone into download mode then it should be 'saveable' ..

Double0EK said:
Use Odin to fix it.
If you can put your phone into download mode then it should be 'saveable' ..
Click to expand...
Click to collapse
I am able to put it into download mode. When I follow the instructions I found for Odin, the process seems to go smoothly. However, once my phone reboots, it stays on the "Samsung Galaxy Note II" screen (with the black background). I've left it like that for over 30 minutes, and it just stays on that screen.
Should there be another step I should be following?

diggeryo said:
I am able to put it into download mode. When I follow the instructions I found for Odin, the process seems to go smoothly. However, once my phone reboots, it stays on the "Samsung Galaxy Note II" screen (with the black background). I've left it like that for over 30 minutes, and it just stays on that screen.
Should there be another step I should be following?
Click to expand...
Click to collapse
Try installing SuperSU from Playstore
It has an option of doing a FULL UNROOT
I am sure that will help.
If not then install Rom Manager from PS
Through RomManager reboot in Recovery
1.) Wipe device 3x times
2.) Wipe cache 3x times
3.) Under advance you will Find Dalvik Cache -- wipe that 3x times
[MENTION=522570 [MENTION=1065870 [user=1879310]@@@@[/user][/MENTION]@@[/MENTION]@@
But more importantly why would you want 4.3 stock anyway?
Install TWRP Recovery or ClockWorkMod recovery and install/Flash CM1 (Cyagonemod) or any other custom roms 4.4.x kitkat

Nothing is really working for me.
I can't boot into normal mode. I am able to get into "download" mode, but whenever I try to load an image using the Odin software (both a stock image and a Cyagonemod image), it starts to load the image, but just hangs a certain percent of the way through.
I also can't get to that screen where it gives you the text based options to wipe your device, cache, etc.
I've tried loading both TWRP recovery and ClockWorkMod recovery (through Odin), and though it seems to load properly (Odin says "Pass"), when the phone reboots, it goes to the "Samsumg Galaxy Note II" screen (the one with white text on a black background), and just stays there.
I've gotten T-Mobile to agree to send me a new phone. But if I can't get into any of the items I mention above, how can I make sure my old device is wiped before sending it back to them?

Just do this un root with chain fire root away app.
Then use triangle away app.
Then find 4.1.2 MB1 stock Odin tar. The complete package .
Odin to stock .
Reboot and then update via Ota.
You have to un root first and also have to triangle away which removes flash counter in Odin.
System modified status will not allow Ota.
That's the best suggestion I have
Sent from my SGH-T889 using xda app-developers app

diggeryo said:
Nothing is really working for me.
I can't boot into normal mode. I am able to get into "download" mode, but whenever I try to load an image using the Odin software (both a stock image and a Cyagonemod image), it starts to load the image, but just hangs a certain percent of the way through.
I also can't get to that screen where it gives you the text based options to wipe your device, cache, etc.
I've tried loading both TWRP recovery and ClockWorkMod recovery (through Odin), and though it seems to load properly (Odin says "Pass"), when the phone reboots, it goes to the "Samsumg Galaxy Note II" screen (the one with white text on a black background), and just stays there.
I've gotten T-Mobile to agree to send me a new phone. But if I can't get into any of the items I mention above, how can I make sure my old device is wiped before sending it back to them?
Click to expand...
Click to collapse
have you tried booting into recovery? after you load the custom recovery with odin and it reboots, pull the battery put it back, then hold vol up + home and then + power. hold all 3 until recovery. try a factory reset and reboot.
Sent from my SGH-T889 using XDA Premium 4 mobile app

wolfpack612 said:
have you tried booting into recovery? after you load the custom recovery with odin and it reboots, pull the battery put it back, then hold vol up + home and then + power. hold all 3 until recovery. try a factory reset and reboot.
Click to expand...
Click to collapse
I have. It brings me to the same screen with the Samsung Galaxy Note II text on the black background and just stays there.
So, in summary, I can get into download mode (vol down+home+power), but it seems nothing else.

Try factory settings the phone through stock recovery and then check your phone status. It should say 'normal' but if it says 'modified,' download Triangle away and run the tracking setting (it'll make your phone say normal so you can download the OTA). Given you're on tmobile and your phone is the T889 model, check for software updates and install the OTA. Your phone will take a bit and will probably be stuck on the T-Mobile 4G boot screen for several minutes (it's normal). This should work.

Stuck in bootloop can't power to recovery or Odin.

Hello all, as the title states. my Note 2 is stuck in a bootloop. Originally I had the Liquid smooth ROM flashed, I have been running this ROM for several months with no issue. Yesterday I tried to flash the Blissstalk ROM using the usual method: TWRP 2.8.5 > Full wipe > Flash Blissstalk > Wipe dalvik/cache again > Reboot system. Phone loaded up fine went through setup and installing apps fine. I put my phone on charge last night and woke up this morning to it stuck on the Bliss bootscreen. I pulled the battery and tried to boot to recovery (Vol up + home + power) instead of loading recovery my phone went straight to the bootscreen. Tried 3 more times and then 3 times to get it to boot to Odin. Nothing happens other than it goes straight to the bootscreen and gets stuck. Not sure what to do now and looking for a way to, if nothing else, return it to stock so I can start fresh.

Did you try the 3 button combo with no battery and then install the battery with the 3 buttons still pushed? It may sound crazy, and it's tricky too, but I'm hoping that you haven't tried that as to it may be the fix you're looking for.

Make sure you press the vol up+power+home key and keep it pressed until you see the Samsung logo appear. Your switch might be a but loose
Sent from my SGH-I317 using XDA Free mobile app

[Q] Phone turns off automatically

I run a rooted SG S3 on stock 4.1.1 with an old 3.0.56 kt747 kernel
Until recently, I've been running this set up for years without any problems.
I've also updated fairly recent CWM along with the latest SU.
As the title states, my phone has been turning off automatically. After weeks of troubleshooting, I noticed a pattern.
When I press the power button, there are three different scenarios that happen.
The phone goes to sleep normally
The phone goes to sleep and immediately wakes up to the lock screen
The phone displays the shut off menu
If scenario 1 occurs, everything is fine and runs perfectly for an indefinite amount of time until i attempt to put the phone to sleep again.
but, if scenario 2 or 3 occurs, the phone automatically shuts down abruptly, within 1-5 seconds.
This problem still occurs even when I boot into safe mode, and I have eliminated the SD card as a suspect. Furthermore, booting the phone up has become extremely difficult. The boot would sometimes crash after the samsung logo, after the splash screen, or during the boot animation. It takes somewhere around 3-5 tries to fully boot up the phone.
Booting into CWM recovery is still possible, but even that sometimes crashes mid-way. I've also noticed that at certain times, when I click the power button to select an action in CWM, it actually double clicks (thankfully CWM is tolerant to that) and cancels the action I was trying to do. I've done some googling and found that an over sensitive power button is a common occurrence in this model, and while that may explain why the 3 different power button scenarios occur, it still doesn't explain the crash.
Finally, I seemed to have remedied the automatic shut off problem several times by wiping cache from CWM. When I first started having these problems and began troubleshooting, wiping the cache eliminated the problem for about a week before the problem came back. When it did, I uninstalled some apps and re-wiped the cache which eliminated the problem again for several days. However, these periods become shorter and shorter, and now wiping cache does not seem to help at all. I've also tried wiping the delvik cache, but it didn't help.
I'm stumped right now. Any suggestions would be appreciated before I try some more large-scale attempts such as resetting my phone or taking it apart. Thanks everyone!

This definitely fits more in your large-scale attempts category, but it is what I'd try.
I'd grab the stock 4.1.1 firmware from sammobile.com and Odin back to stock. You're fortunate to be on the old firmware, so you can Odin back to stock. When Odin completes successfully, pull battery don't let the phone reboot normally (untick auto reboot in Odin). Boot straight into the stock recovery and do a full wipe. Then reboot your phone normally.
Doing this will correct any problems that exist with your internal storage to the extent possible. If you've still got problems after doing this, it is probably a hardware issue.

jason2678 said:
This definitely fits more in your large-scale attempts category, but it is what I'd try.
I'd grab the stock 4.1.1 firmware from sammobile.com and Odin back to stock. You're fortunate to be on the old firmware, so you can Odin back to stock. When Odin completes successfully, pull battery don't let the phone reboot normally (untick auto reboot in Odin). Boot straight into the stock recovery and do a full wipe. Then reboot your phone normally.
Doing this will correct any problems that exist with your internal storage to the extent possible. If you've still got problems after doing this, it is probably a hardware issue.
Click to expand...
Click to collapse
Yeah, that's part of the reason why i didn't want to upgrade the bootloader for the newer firmwares. I messed around with my phone this morning and its been avoiding the problem ever since. Not exactly sure what I did though lol. Thanks for the reply, I'll try it if the problem comes back over the next few days.

Your phone isn't "crashing," your power button is malfunctioning. The fix is pretty easy. You will need to open your phone up and scrape it off (the phone can be turned on without it). There are youtube videos that show how to remove it.

my tab pro 8.4 has been soft bricked, can anyone help me?

I'll start from the beginining.. Okay so since i bought my tab (3 months ago) i had a battery problem, but it wasnt a bad battery problem. Once it got to 95% battery it stopped charging. Anyway, about a week after that i was unhappy with the performace of touchwiz on my tab so i decided to root it and install the cyanogenmod 12 nightlies. I was happy with cm for a while but eventually i got bored of all the bugs and instabilities so i decided to switch to a touchwiz rom.. This touchwiz rom was a vast improvement from the stock touchwiz so i decided to keep it. However i still wanted to improve the performace so i researched online for apk's/zip's that could improve my tabs performace. I came across crossbreeder and people said it was really good so i decided to install crossbreeder through TWRP. Once installed i rebooted my device and i instantly found many more battery problems. For example my battery would go from 50% to 20% in 5 mins/my battery would run out and i would reboot it and it would have had 40% etc. I downloaded some battery calibrating apps and calibrated my tab. After all that, that battery wasnt so bad. It was still dodgy but no where near as bad as it was straight after installing crossbreeder. Anyway, this was about 1 month ago. Since then, no new problems had occured with the battery until last night. Last night, my battery ent don to 1% then turned off like it should. I put my tab on charge and rebooted however when it rebooted nothing would work. My touchscreen didnt work, my home button didnt work, none of the keys next to the home button didnt work. So i thought that this was no problem and i could just boot into TWRP, factory reset and install the backup that i made. When i tried this, i booted into TWRP successfully however i couldnt press any of the TWRP buttons, again, i thought that this could be solved by flashing the stock firmware through odin. I put my tab into download mode and connected it to my pc, then flashed the stock rom. Once finished it showed a 'pass' and i thought everything was sorted.. When my tab booted up, it again, didnt let me press anything and none of the buttons would work. This is when i panicked. I then went into the stock recovery to factory reset my tab to see if that would work however, when i went into stock recovery, i couldnt go up or down using the volume keys.. So my volume keys didnt work either. I next put my tab in download mode and connected it to my pc. I opened odin and checked the 'Nand erase all' box thinking this would fully reset my whole tab. I then researched the 'nand erase all' function to find that everyone said that it breakes your device and puts it in bootloop etc. After reading this i instantly disconnected the usb from my computer to my tab. I tried rebooting my tab to see if it still booted and it didnt.. (i waited 20 mins). I then ran odin with 'clear efs' box ticked on. Again it didnt boot. I went into stock recovery again to see if the volume keys would work.. they didnt.. Infact when i opened stock recovery it had 3 errors showing (which it didnt last time i opened stock recovery). They all started with 'failed to mount /data'. Now i am here.. Sorry it was such a long read, i thought it would be better if i explained in detail. Thanks to anyone that replies/helps me.

NAND Erase All shouldn't destroy your device. What you need to do is boot into recovery, and choose the Factory Reset/Wipe Data option. From there, reboot and you should be good! Otherwise if it doesn't boot, just flash in Odin again, reboot to recovery, and then Factory Reset/Wipe Data again. We'll get you back up and running in no time
The reason why you are getting those errors is because your data partition is NOT formatted (because NAND Erase All wipes out your partition details, so it looks unformatted), so the recovery and your kernel are not finding your data partition. Your device will be unable to boot without. Factory Reset will reformat your data partition and get everything into place. Let me know how it goes!

My tablet updated and now I can't get it to do anything...

My Galaxy Tab S prompted me for an update last night. I was at 5.0.2, so I'm not certain what I was getting upgraded to but it was about a 190MB download. The download went fine and the install seemed to go OK. However, at the end of the update install, the tablet rebooted, and that's when everything screwed up. It went through a normal reboot sequence but, when it started to come up like it was going to take me to the home screen, I got hundreds of error windows popping up one on top of the other. They all said "Unfortunately, this has stopped." or that has stopped, basically running through pretty much every default pre-installed and me-installed app on my tablet. And they kept appearing faster than I could press OK. I have just a black screen with these white error boxes. I'm never able to get to the home screen at all. I've rebooted. I've completely powered down and waited for several minutes before booting. Nothing seems to help. I keep getting a normal boot sequence, right up until the point that it would relinquish control to me, and then these same hundreds of error boxes and no home screen or any sort of control over my tablet. I have no idea what to do.
Has anyone ever heard of any behavior like this or know what I should do?
Thanks.

try to enter the recovery mode by pressing home+vol up+power button. and reset your device
or you can download your full firmware and flash it using odin.

edan1979 said:
try to enter the recovery mode by pressing home+vol up+power button. and reset your device
or you can download your full firmware and flash it using odin.
Click to expand...
Click to collapse
Just got up for the day and saw your response. I'm on nights right now, sorry.
Thank you very much for your reply. I was able to get into recovery mode. Just to clarify, when you say "reset", are you saying a reboot (the first option) or wipe data/factory reset (the fourth option)?
EDIT:
You can disregard. I went ahead and rebooted, and that did what I figured; pretty much nothing. Basically just rebooted, got out of recovery mode, and booted right back into the state that it was in before, which was screwed up. Factory resetting now.
Thanks.

OK, system wiped OK and it's restoring from a Google Backup right now. So, I guess we'll see how it goes the next time I try to update. I have the Wi-Fi version, just standard SM-T800. Isn't Marshmallow available as an update now? I'll see how things go I guess and see what updates are available.
Gotta remember recovery mode, for when all seems darkest!
Thanks again for your help.

OK, so, my tablet is back up and running, but that update won't install. It isn't causing the same problems as before, but it still won't install. I'm at 5.02 and the update is 190MB. It downloads and it starts to install after I accept the EULA. The screen goes black, the little Samsung logo pops up, then the little Android guy comes up and it says installing update 0%, waits for about two seconds, then the little Android guys is on his side with his cover plate up and it says error, then reboots. I can still use my tablet, I just can't install this update, whatever it is. I'm pretty sure it isn't the Marshmallow update, because I'd heard that was up over 1GB. Still, if I can't get this update, whatever it is, I doubt I'll ever be able to get the Marshmallow update.
Now I'm happy I have my tablet back, but frustrated because it won't update.

definitely it already has MM update. you could go to Odin way. Update it manually. can download the firmware here.
http://updato.com/firmware-archive-select-model?q=T800&order=date&dir=desc&exact=1

edan1979 said:
definitely it already has MM update. you could go to Odin way. Update it manually. can download the firmware here.
http://updato.com/firmware-archive-select-model?q=T800&order=date&dir=desc&exact=1
Click to expand...
Click to collapse
Yeah, I was thinking the same thing. It doesn't seem too hard. I'm reading up on it now. I'll download everything I need and possibly try it this weekend. I intentionally haven't reinstalled a lot on my tablet yet, thinking I was going to go that route.
Hopefully, that will take care of my issues.
Thanks again for the advice.

Well, updating with Odin went off without a hitch. After it had updated, I performed a factory reset, just to be safe, and reinstalled everything. It's running great now and I sitting pretty with 6.0.1.
Thanks again for your help.