I recently got the Note 5 and I rooted and installed Moar Rom. The phone started to freeze and crash repeatedly. After trouble shooting and deleting apps/resetting it would still freeze, crash, reboot. I decided to restore the backup I made after root. I went into twrp, wiped the phone and started the restore, it froze mid restore and crashed and rebooted. Now there is no os on the phone and recovery will not work for more than 30 seconds without freezing and crashing. I have tried odin to flash a stock tar and start over but it always fails. 9/10 it hangs when trying to get pit, otherwise it just fails. I have trued to adb sideload as well but again the phone will not stay on long enough to finish any transfers. Any ideas??
jdestef90 said:
I recently got the Note 5 and I rooted and installed Moar Rom. The phone started to freeze and crash repeatedly. After trouble shooting and deleting apps/resetting it would still freeze, crash, reboot. I decided to restore the backup I made after root. I went into twrp, wiped the phone and started the restore, it froze mid restore and crashed and rebooted. Now there is no os on the phone and recovery will not work for more than 30 seconds without freezing and crashing. I have tried odin to flash a stock tar and start over but it always fails. 9/10 it hangs when trying to get pit, otherwise it just fails. I have trued to adb sideload as well but again the phone will not stay on long enough to finish any transfers. Any ideas??
Click to expand...
Click to collapse
Take it in and have it looked at.
Related
Alright, so here's the issue. I searched and could not find anything close to this...
I have stock JH7 installed. Installed Clockwork (via Rom Manager,) backed up my ROM, Metamorphed a theme, didn't like the theme, tried to use Clockwork to restore from my backup. Clockwork would go through all of the files, but when it gets to "ReceivedFiles," it just hangs. I let it run through the night, approximately 5 hours, and in the morning it was still in the restore process at this same step. I knew something was wrong, so I unplugged, removed battery, and booted it up. My phone just sat at the Galaxy 'S' screen and would not start up.
After several more attempts with 2 different backups (always hanging at the same place) I finally wiped data, cache, & dalvik cach, then booted it up. All was well and working stock. Then I shut down, booted into recovery, opened Clockwork, and attempted to restore again. My phone is currently sitting at the same step as before.
Any clues? I've attached a picture of its screen.
Did you pull the battery out? Mine is stuck as well....was updating to Serendipity 5.1.
Finding update package...
Opening update package...
installing update....
And it's been there for over half hour
I pulled it and can get back in the phone just fine. It seems to still get stuck there though.
I tried to update my rooted note but it just keeps rebooting. It goes through the set-up with percentage at the bottom, gets to 100% and then reboots like it's going to start. However, instead of starting, it just instead tries to upgrade again. It keeps going through this cycle.
I started it and used Odin to flash initial .tar with root in it and it's doing the same thing.
Please help!!!
grimloktt said:
I tried to update my rooted note but it just keeps rebooting. It goes through the set-up with percentage at the bottom, gets to 100% and then reboots like it's going to start. However, instead of starting, it just instead tries to upgrade again. It keeps going through this cycle.
I started it and used Odin to flash initial .tar with root in it and it's doing the same thing.
Please help!!!
Click to expand...
Click to collapse
Well, my suggestion would be to load up Kies on your computer. Connect the tablet, and see if you can do a firmware repair seeing as how you seemingly already tried to ODIN in another rom. Maybe you can try to boot into CWM and wipe the cache, dalvik, and factory reset, but I'm not so sure that will do anything for you.
OK. Used the update/tar from this file. Got me up and running but then gave me a message that update failed to install. I did, however, lose root rights.
http://forum.xda-developers.com/showthread.php?t=1847706&page=2
As risky as I am, I checked software update and found another update--this time smaller in size. Downloaded and installing...Wish me luck.
OK, That's appearing to work! Machine is rebooting and is again "optimizing applications."
yeah, the recent update came in 2 flavors. stock to LI3 which was 75 and LH2 to LI3 which was 40mb.
Glad to hear you got it up and running!
My phone was working just fine before I went to bed. I woke up this morning an my phone was stuck at the "Samsung Galaxy SIII" boot screen. I can't seem to get my phone back to a working state Here's what I've done so far:
I rebooted my device - didn't work.
I rebooted into recovery, wiped everything and installed clean rom 7 - no luck.
I've tried to ODIN back to stock and ODIN freezes immediately after it starts (for periods > 30 mins).
I've tried ODIN with two different USB cables.
Any idea on how I can get my phone back to a working state?
I am seeing the product name in download mode, so I don't suspect the "sudden death syndrome" that I've read about with the S3.
BlueCross said:
My phone was working just fine before I went to bed. I woke up this morning an my phone was stuck at the "Samsung Galaxy SIII" boot screen. I can't seem to get my phone back to a working state Here's what I've done so far:
I rebooted my device - didn't work.
I rebooted into recovery, wiped everything and installed clean rom 7 - no luck.
I've tried to ODIN back to stock and ODIN freezes immediately after it starts (for periods > 30 mins).
I've tried ODIN with two different USB cables.
Any idea on how I can get my phone back to a working state?
I am seeing the product name in download mode, so I don't suspect the "sudden death syndrome" that I've read about with the S3.
Click to expand...
Click to collapse
When you flash a new rom in recovery, what exactly happens? Does it completely finish, and when you reboot it gets stuck at the boot screen? Also have you tried restoring a backup?
You might have a bad rom download, but that doesn't explain why odin keeps failing. Try to do a factory reset without flashing anything and see if it'll boot up.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
When you flash a new rom in recovery, what exactly happens? Does it completely finish, and when you reboot it gets stuck at the boot screen? Also have you tried restoring a backup?
You might have a bad rom download, but that doesn't explain why odin keeps failing. Try to do a factory reset without flashing anything and see if it'll boot up.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
When installing the rom, it completes and reboots like normal. I've tried three different roms (and they've worked in the past) with no luck, so I don' think I have a bad download. Restoring a backup fails every time - I have multiple backups.
I've also done the factory reset - no go.
BlueCross said:
When installing the rom, it completes and reboots like normal. I've tried three different roms (and they've worked in the past) with no luck, so I don' think I have a bad download. Restoring a backup fails every time - I have multiple backups.
I've also done the factory reset - no go.
Click to expand...
Click to collapse
I'm pretty sure this is your problem.
http://forum.xda-developers.com/showthread.php?p=30386309
This should fix everything. It sounds like a data writing issue.
Sent from my SCH-I535 using Tapatalk 2
Ok, so I think I may have finally killed one of my S2 Skyrockets.
I attempted to use the factory reset function from within Candy 5.1.1. However, on reboot the phone entered TWRP, or rather tried. Instead of booting into the recovery, it just kept restarting over and over again. I couldn't get it to boot into the OS or TWRP.
Thinking I had just soft-bricked it, I went into ODIN mode and uploaded a full restore image. Now I don't get stuck in a TWRP bootloop, I am stuck in a different bootloot. I see "Rethink Possible" go black, wait a few seconds, then it restarts again. I have pulled the battery out several times, attempted to boot into recovery (where I get the original TWRP bootloop) etc.
Is there any way to recover this device, or am I hosed?
[UPDATE]
Ok, this was one of the scarier things I've run into, but I recovered the phone. I used the sammobile version of the UCMC1 image (which blows away everything). This didn't reboot, it just hung. However, I was able to get into 3e (the stock recovery) and do a factory reset. THAT got me past the block. I'm now in the process of putting TWRP back on along with Candy.
Apparently you REALLY don't want to screw with the factory reset function...
My Samsung Galaxy S6 Edge is not booting even after a factory reset
A mobile app. for Android was installed successfully and since then I’m only having issues with my Samsung mobile:
- Since the installation of both the Hockey & Mobile Banking apps, my mobile freezes during any regular action and after a few seconds the device auto-restarts itself intermittently; this happened during the weekend while in use;
- Sunday night I uninstalled both the Hockey & Mobile Banking apps and the phone continued to freeze and restart intermittently. I was able to boot in SAFE MODE.
- This morning after the phone was turned off and turned on, the phone is not loading; the boot is looping and unable to reach the menu. I’m able to boot in SAFE MODE.
- This morning I did a Factory Reset, when done I get the “welcome” screen and right thereafter, the mobile freezes, auto-restarts and the boot keep looping.
Any help would be highly appreciated.
Hey guys, any suggestions...? I tried last night restoring the OS using Samsung Smart Switch application and the process went just fine the first time and during the setup process the phone just restarted against and for stuck in bootloop again.
I did a second attempt but after the PC is don and the phone boots it gets stuck.
Sometimes after restoring stock firmware and you get a bootloop, you have to boot to stock recovery and factory reset then wipe cache partition.
I know you said you did that once before you posted, you did that before you used SmartSwitch. Have you tried factory reset since restoring with SmartSwitch?
Yes, I did with SS last night; I did it again this morning and after completing the 100% software download, it started updating the device and at 97% it stopped and got the message "FAILED".
now as we speak, I restarted it again and now it's at 66^ downloading the files.
How can I perform a clean install using SS...? or do I need ODIN...? I want to keep the mobile as original as possible.
If you can find your stock firmware, download it and flash it with Odin, it's more reliable.
Maybe a stupid question: Where can I find my stock firmware...?
My info:
PDAIX / CSCI2 / PHONE: PHH (XFA)
I found the Firmware on SAMMOBILE: https://www.sammobile.com/firmwares/galaxy-s6-edge/SM-G925F/XFA/download/G925FXXU4DPIX/108273/
Is this a stock Firmware and reliable source...?
Sammobile is a very reliable source, if that firmware is the newest one for your model number and country/region/carrier then you're good to go.
I did install Firmware corresponding to my phone (PDAIX / CSCI2 / PHONE: PHH (XFA)) using Odin, I can use the phone for like 2 or 3 minutes and then it freezes, restarts and gets into boot loop.
Any more drastic measurements to take...? Is there an online tool to test the hardware function(s)...?
After flashing stock firmware, have you tried booting to stock recovery then do the factory reset and wipe cache then reboot.
Yes, I did...!
In ODIN, do I load only the "AP"...?
In most situations, AP is all you need if the firmware is an all in one firmware file, if you have a 4 part firmware then you need to put each part in its corresponding tab/slot in Odin.
Sometimes you have to flash more than once to be successful.
My phone is running like a horse now...! No more intermittent restarts nor boot looping.
I just did a clean install of Android 7.
The clean install of Android 7 went fine and now it's working back again, was because I changed the "Reactivation Lock" to OFF; I think this helped.