[Q] S4 i9505 reboot loop after OTA upgrading to Lollipop - Galaxy S 4 Q&A, Help & Troubleshooting

Hi guys,
I have a big problem. Today, Samsung Spain has sent me the OTA upgrade for my device. I've installed it as I always do, I waited until everything finished, I started running the device and everything seemed to work fine, but after an error I had to restart and it has entered in a reboot loop with the Samsung logo.
Do you know anything I can do?
If it helps, my device is encrypted due to company policies. When I switch on the device, it asks for the pin code to unencrypt it, and after that is when it starts to reboot.
Thank you very much for any help you can bring.
Best regards,

I have the same problem with my phone after the OTA update.After the update it work's fine for 2-3 day and the start entering in bootloop over and over.I give him a wipe data/factory reset and it workked fine for 2 days and then the same problem.I put another ROM from Black Edition and after 2 days same problem.Now i put out my sd card to see if is doing the same .
sorry for my english

rpachecoh said:
Hi guys,
I have a big problem. Today, Samsung Spain has sent me the OTA upgrade for my device. I've installed it as I always do, I waited until everything finished, I started running the device and everything seemed to work fine, but after an error I had to restart and it has entered in a reboot loop with the Samsung logo.
Do you know anything I can do?
If it helps, my device is encrypted due to company policies. When I switch on the device, it asks for the pin code to unencrypt it, and after that is when it starts to reboot.
Thank you very much for any help you can bring.
Best regards,
Click to expand...
Click to collapse
Try to factory reset from recovery. If it doesn't work download Russian lollipop ao7 firmware from sammobile
Sent from my Galaxy Note 5 using Tapatalk

I made factory reset at least 10 times until I switched to 4.4.2 about 2 hours ago.I want to see if the problem is Lollipop or my phone.

Finally, I wiped from recovery to factory reset.
I've lost all I had in the device, but almost everything was in the SD card. My problem now is that, as I said, my device was encrypted due to corporate policies and also the SD card was. Now I see the SD card content but seems to be corrupted. I guess it is because I have to decrypt it, but I don't know how to do it, because when I access Settings it only says Encrypt SD card.
Could anyone help me, please?
Thank you very much!

Related

Nexus 4 TWRP encryption with password - I think the phone is gone

So, I have read a lot about TWRP sometimes bugging out and randomly encrypting phones and adding a password to which the user either never set it up or that TWRP doesn't accept it. This has recently happened to me and I cannot use my phone and I don't know what to do.
I have had the bootloader of my phone unlocked since day 1 when I bought my phone (release date last year) and have been running PA ever since. I have never had any problems with it, until about 5 days ago, when I grabbed my phone and everything started crashing and the camera was apparently not available. I didn't know what was the deal with it, so I rebooted the phone and it entered a bootloop (it hangs on the Google logo for about 5 minutes and then it hangs on the PA logo screen forever). I went on to the bootloader and started TWRP to see what was the deal. I originally wanted to grab certain files off the phone in case I had to do a system format, but when I got to TWRP, it asked me for a password which I have never set up and I tried every combination I could think of but it always failed. Everything was encrypted and without the password I couldn't get to it. I tried wiping everything including a factory reset before resorting to a system format (which I read about it and apparently is meant to be the solution). Everything failed because it couldn't access the /cache, /data, nothing. I went on to do a system format and although that is meant to wipe the phone and remove encryptions, it also failed to wipe the /cache and although TWRP says that the wipe is successful, the phone is still encrypted, the password is still around and it bootloops. I have tried the system format like 50 times and always the same.
Can anyone help me out with this? I am currently travelling around but am at a hostel where there is great internet and pcs, so I can install drivers, toolkits and such. I actually started looking around for new phones, since I cannot for the life of me get the phone to start again.
Note: The phone was working perfectly fine, I put it down to have dinner and once I finished, I tried to use it and it started to bug out. I also read around about this, and everyone's issue gets fixed after a system format.
Any help, would be greatly appreciated, that phone is the only net device I have on this trip and it sucks to not have any way to contact anyone.
Thanks.
Bump
Don't blame TWRP for something it doesn't do.
Looks like your device have an EMMC failure, sorry.
You can try installing factory image, or last resort restoring by download mode, but I think the flash memory in your phone is gone.
http://forum.xda-developers.com/showthread.php?t=2347060
sent from nexus 4
eksasol said:
Don't blame TWRP for something it doesn't do.
Looks like your device have an EMMC failure, sorry.
You can try installing factory image, or last resort restoring by download mode, but I think the flash memory in your phone is gone.
http://forum.xda-developers.com/showthread.php?t=2347060
sent from nexus 4
Click to expand...
Click to collapse
I didn't mean to blame TWRP. It is just that it was when I am on it that I get asked for the password and I was under the impression that it was TWRP that did the encrypting (I am in no way a developer or even very knowledgeable when it comes to the under the hood stuff, I usually only follow the tutorials). But thanks for the reply and the link, I will try that and hopefully get the phone back working.
Also, I did read in a thread that apparently this can occur due to hardware failure, I was just hoping this wasn't the case.
This happened to me on an old phone. Not sure why. Factory image fixed it. Could be a different issue but its worth a shot.
Sent from my Nexus 4 using XDA Premium 4 mobile app
It's happening to me now too
Sent using T-Mobile S4 4.3 MK2
LEGEND94 said:
It's happening to me now too
Sent using T-Mobile S4 4.3 MK2
Click to expand...
Click to collapse
Did it suddenly happen or did you change ROMs?
I tried a new rom for the first time and then went back to wicked 9.1, I'm thinking that triggered something.
I think I got a fix though, look here: http://forum.xda-developers.com/showthread.php?t=2588377
Sent using T-Mobile S4 4.3 MK2

SM-T530 Lollipop update problems

Hey guys,
My wifes Tab 4 recently did the OTA update to Lollipop (5.0.1) and has been having a problem ever since. After being in use for a few minutes after the update it suddenly locked up and rebooted itself. Thought nothing of it at first, but then it did it again, and now randomly reboots all the time, sometimes after only a minute of use. I've tried clearing the cache partition and factory reset, neither gave any improvement. Then i figured maybe the OTA download was the probblem so i flashed it back to Kitkat using Odin and all worked fine again for a few days. I turned off the OTA update checke and she was perfectly happy with it again.......
......until it downloaded the update all over again.
Before allowing it to update again i connected it to the PC and did the update via Kies instead. All seemed to be fine for about 5 minutes and then started rebooting. Again, cleared cache and factory reset. Again no improvement.
Then tried flashing the update via Odin again. Still no improvement.
I'm drawing a blank on this one. I've tried everything I can think of and still not been able to solve this one. The only thing i've been able to figure out so far is that for whatever reason it doesn'T randomly reboot if its connected to the PC via USB...............
Anyone got any ideas how to sort this?? Samsung have offered to take it in for repair and I'Ve been offered a refund from the retailer, but I'd rather avoid those options if possible.
Thanks!
I have the same problem and nobody Knows. I will back to kitkat. let me know if you fixed. sorry for my english im cuban.

SM910F Note 4 5.1.1 Random Freezes and Restarts

Hello there xda.
I have a Samsung Galaxy Note 4 SM910F.
So what is happening to my phone is that whenever I am in any random app lets say reddit or even chrome for example. It will like freeze for a minute or two and then unfreeze.
In more extreme cases it will reboot.
So this happened randomly because I flashed a Stock unbloated 5.1.1 ROM from here back in december and everything was working smoothly and stuff. I had xposed installed and all my apps. Then in February it started with this random freeze/reboot. I had not installed anything else apart from what I had for the last 3 months.
So I restarted the phone, changed the battery and stuff to see whether that will fix it. However it didn't. So I formatted the phone (the soft type) just so I can install another ROM. So I tried another ROM, flashed the correct CP and BL and stuff and then just installed chrome and whatsapp. After an hour or two the same thing happened. So this time I factory reset he phone, like a complete wipe and I installed the unbloated ROM once again with few apps. Same thing happened...
So my last resort was to install Cyonagen Mod. After an hour or two same thing happened...
I don't know what is the problem. I read about some peoples phones emmc failing and thus the freezing, but I am not sure yet.
Please could you guys explain what I should do to fix this?
Thank in advance!
I have the same problem. Starting on mid january. I'm on stock 5.1.1 with root and twrp recovery
Tried backup and factory reset
I went back to stock after I factory reset the phone. And still had the same problems.
People say that its a hardware problem... So I guess I'll have to send it back to Samsung soon.
I think I tripped the knox. I just have to unroot and get it back once again to stock and send it back. I hope that they accept it.
i have the same problem. my model is SM-N910W8 and I bought it from 2nd hand, so no receipt and no prove of purchase.
can I still send it back to samsung to fix it?
same problem as you and now my phone died completely .
my phone was 4 months and he has not supported any longer he died naturally lol.
my operator gave me another free under warranty because the phone had a faulty motherboard and after several back galaxy note 4
This started happening to me a week or so ago and my phone just got stuck in a boot loop after it froze and rebooted. I'm on the latest stock firmware. Tried factory reset, reflashed stock firmware, nothing helps. It still reboots (sometimes it almost gets booted completely, other times it reboots after 2 seconds.
Just disable finger print. Yes that magic feature offered by Samsung is causing more hungry that happiness since S5
EclipseX said:
Just disable finger print. Yes that magic feature offered by Samsung is causing more hungry that happiness since S5
Click to expand...
Click to collapse
Many thanks. This was driving me mad for a few days, I had tried three different ROMS, completely wiping everything. I eventually went back to stock, which I'm still running and it was the same; it would run fine for a few hours and then start to lock up until eventually it would either reboot or stop responding and I'd have to pull the battery to restart it.
Just not selecting fingerprint security doesn't work, you have to force stop "Fingerprints" in Application Manager (All).
just do not setup the finger print lol. I was having those problemes too when I bought the note 4 until someone tell "do not setup the finger print" lol, not I'm a happy user.... I hope that android 6.0.1 solve the probleme
HXOY said:
Many thanks. This was driving me mad for a few days, I had tried three different ROMS, completely wiping everything. I eventually went back to stock, which I'm still running and it was the same; it would run fine for a few hours and then start to lock up until eventually it would either reboot or stop responding and I'd have to pull the battery to restart it.
Just not selecting fingerprint security doesn't work, you have to force stop "Fingerprints" in Application Manager (All).
Click to expand...
Click to collapse
EclipseX said:
just do not setup the finger print lol. I was having those problemes too when I bought the note 4 until someone tell "do not setup the finger print" lol, not I'm a happy user.... I hope that android 6.0.1 solve the probleme
Click to expand...
Click to collapse
Spoke too soon, it's started rebooting itself again.
Same problems here since 2 days. I was on original 5.1.1 software... Very strange all those people with the same problems
did the problem was resolved ? started to have the same problem 3 days ago ! was on 6- flashed stock with full wipe..nothing ! downgraded to 5.1 with full wipe via odin...again nothing !
WTF [email protected]!
Davids said:
did the problem was resolved ? started to have the same problem 3 days ago ! was on 6- flashed stock with full wipe..nothing ! downgraded to 5.1 with full wipe via odin...again nothing !
WTF [email protected]!
Click to expand...
Click to collapse
Still having the same issue around the same time everyone else started experiencing it.
I also was rooted and had xposed installed on 4.4.4 before the issue started happening.
Try the solution provided here & report back..
http://forum.xda-developers.com/note-4/help/note-4-sm-n910f-freeze-restart-issue-t3439111

Massive softbrick (haven't found a solution yet)

Hello everyone,
So here's my story: I got a 6P short after release and it's been amazing. After switching from a S6 I couldn't be happier until 3 days ago.
I was playing around with my phone (checking for updates on the play store if I recall correctly) and I was going to switch from 4g to wifi. I went ahead and pulled down my notification shade and went to press WiFi but misclicked and hit Hotspot which was below it. My phone suddenly froze big time and this is for the first time ever since purchase.
At first I thought I'd wait it out since the device was completely unresponsive, home button didn't work and neither did anything on screen. Buttons didn't make a difference either. 10 minutes went by and I ended up force restarting by holding down power + volume up. First part of my bootup went fine but when it got to the android boot animation after I put in my pin to allow the device to start it dropped from the smooth usual framerate down to 1 frame every 10-15 seconds and it slowed down further until it came to a complete halt around the time the android letters appear.
My first thought was corrupt rom so I went ahead and wiped data from the stock recovery. I was running completely stock with no modifications whatsoever. That didn't do anything. Phone still froze in the same boot phase. Desperate I unlocked bootloader to flash a clean fresh image to try to fix it and to my surprise that didn't change a thing.
As I was getting pretty desperate already I had one more idea and that was to flash up to the Dev preview. To my huge surprise it booted and I jumped from excitement. So I started setting up my phone again. I got past the prompt to insert sim card and I was now at the screen to choose a wifi network. As soon as I clicked into that the phone froze up again and at that point I lost all hope.
I wiped data in stock recovery and shut the phone down for the night. On day 3, today I woke up and tried starting the phone and it worked as if nothing had happened. I went through the setup and set up my phone on the N preview. At a certain point I was planning to go back to the latest official build but for now I was happy my phone was back from the dead. Later today I tried to restart my phone to clear all running apps etc and it froze up on boot.
I'm losing all hope that I'll be resolving this myself so I'm reaching out to the community to see if anyone's had this happen to them before and hopefuly for a solution. It's still under warranty so I can eventually send it back to the retailer but I'd rather not have a phone for 3 weeks.
Any and all help is appreciated.
Thank you for reading through my long and probably pretty boring story!
Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?
To the OP, is there any reason you did not flash to release version 6 instead of Dev preview ?
Also, any reason you can not simply do the "unenroll" from https://www.google.com/android/beta ?
It will require you to setup certain settings again as you will be back to a "factory reset".
DJBhardwaj said:
Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?
Click to expand...
Click to collapse
DJBhardwaj, i haven't specifically erased those partitions. I was under the impression wipe userdata along with reflashing did that. I will try that tonight when I get home!
Xdafly, I only updated up to N as a last resort because at first I had a locked BL. I was planning to unenrol but that would've been too late as it self bricked after a restart.
DJBhardwaj said:
Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?
Click to expand...
Click to collapse
Well I just did the erase thingy and my phone booted but wifi won't turn on. Enabling hotspot doesn't brick anymore but I now suspect WiFi might've been the issue. Any tips on how to find out what it could be and possibly fix it?
Edit: 2 restarts and a factory reset later I'm back to bricked same way as before.
try safe mode
mr.dj26 said:
try safe mode
Click to expand...
Click to collapse
That was my first thought, that was the restart that bricked it again. Safe mode shouldn't have made a difference since I hadn't even logged into Google account for apps.
After reading the very first post; sounds like bad WiFi hardware.
All the hanging has been related to WiFi or Hotspot.
I think you should get a replacement
Sent from my Purified NexusixP
If Someone Helped You Then Dont Just say Thanks...Hit The Thanks Button!
Is your phone rooted and did you install Xposed?
Over the weekend I shutdown my 6p (stock rooted with April security patch, Xposed v80) and charged it. When it turned it back up I kept getting "Unfortunately, nfc service has stopped". Long story short: I ended up factory reset my phone and reinstalled EVERYTHING and I still got into bootloop. Then I came across
https://github.com/rovo89/Xposed/issues/113
https://github.com/rovo89/android_art/issues/28
At the end of the second post rovo89 (developer of Xposed) fixed the bug in V83. I wiped my 6p once more and installed everything with v83. Problem solved.
Good luck!

Question on SM P580

My Samsung SM P580 was giving me problems recently, and I'm waiting for a new (non Samsung) tablet to arrive. I wanted to try to root my current one (which I've done before). Long story short, I installed older firmware, didn't like it, and reinstalled 8.0 successfully. Did I leave it there? NOOOOOO . . . I wanted to root it so I could use the sd card for internal storage (which is a separate song and dance as many of you know). I installed twrp, but must have clicked on a wrong setting. When I rebooted the tablet it always went straight into twrp. Only option from there: reboot. I did a hard shut down and plugged in the tablet for the night.
Today: I thought "hey, I can reinstall the firmware, hopefully that will fix the twrp issue" Heh heh . . . no. Using ODIN I reinstalled the 8.0 (which worked last time). It seemed to be hunky dorey, ODIN said it was successful, when I rebooted the tablet it gave me a message that it was updating. Then the Samsung Galaxy Tab A showed up . . . and the Samsung logo starting flashing. Awesome. It did that for a moment or two, the screen went blank. A moment or two later the Samsung Galaxy Tab A showed up again, followed by the logo. I let it do this for about 20 minutes, remembering the last time I rooted it took a few for things to settle in. Nothin. ODIN it again, this time I get a message stating an updating error occurred. This is where my tablet is now.
Only thing I could think of was that I messed around so much with firmware, that the tablet is filled with info and has no idea what to do. I can't use the twrp either, it won't come up. Any ideas on how to start from scratch with something like this? I had nothing important on the tablet, nothing backed up was needed. Thoughts?
UPDATE:
I was able to install twrp and boot into it. After doing a data wipe, I was going to attempt in install Lineage; I got everything on an SD card, put it in. Hit Install, Select Storage . . . the internal storage said zero. I considered rebooting it, but I got a warning that there was no OS installed, was I sure I wanted to reboot? I most certainly was not, and I didn't try to install the Lineage for fear of f****** that up too.
vstarjewel said:
My Samsung SM P580 was giving me problems recently, and I'm waiting for a new (non Samsung) tablet to arrive. I wanted to try to root my current one (which I've done before). Long story short, I installed older firmware, didn't like it, and reinstalled 8.0 successfully. Did I leave it there? NOOOOOO . . . I wanted to root it so I could use the sd card for internal storage (which is a separate song and dance as many of you know). I installed twrp, but must have clicked on a wrong setting. When I rebooted the tablet it always went straight into twrp. Only option from there: reboot. I did a hard shut down and plugged in the tablet for the night.
Today: I thought "hey, I can reinstall the firmware, hopefully that will fix the twrp issue" Heh heh . . . no. Using ODIN I reinstalled the 8.0 (which worked last time). It seemed to be hunky dorey, ODIN said it was successful, when I rebooted the tablet it gave me a message that it was updating. Then the Samsung Galaxy Tab A showed up . . . and the Samsung logo starting flashing. Awesome. It did that for a moment or two, the screen went blank. A moment or two later the Samsung Galaxy Tab A showed up again, followed by the logo. I let it do this for about 20 minutes, remembering the last time I rooted it took a few for things to settle in. Nothin. ODIN it again, this time I get a message stating an updating error occurred. This is where my tablet is now.
Only thing I could think of was that I messed around so much with firmware, that the tablet is filled with info and has no idea what to do. I can't use the twrp either, it won't come up. Any ideas on how to start from scratch with something like this? I had nothing important on the tablet, nothing backed up was needed. Thoughts?
UPDATE:
I was able to install twrp and boot into it. After doing a data wipe, I was going to attempt in install Lineage; I got everything on an SD card, put it in. Hit Install, Select Storage . . . the internal storage said zero. I considered rebooting it, but I got a warning that there was no OS installed, was I sure I wanted to reboot? I most certainly was not, and I didn't try to install the Lineage for fear of f****** that up too.
Click to expand...
Click to collapse
Maybe better to flash a recent stock Samsung firmware with Odin. At least to get it working again.

Categories

Resources