The phone has a problem with booting, and I think I could easily fix it by flashing the stock firmware through ODIN, but it didn't go as expected.
The stock firmware was flashed successfully, according to ODIN. After flashing, the device rebooted. I am thinking that it will boot into the system, but instead, it booted into recovery. In the recovery, it is said there that it is installing a system update, which is kind of normal. Then, it is said "Erasing". I'm not sure what it is erasing, or did it even erased something. After that, it will power off.
When powering it on again, it went into recovery mode. Then, it said "Installing system update", and after that, it said "No command". Eventually, it will power off again, just like before.
Can someone help me with this problem?
Device: Samsung Galaxy Note 5
Mode Number: SM-N92080X
Related
As I said, the phone is not currently bricked. I can do a normal boot into the OS and Download Mode, however recovery is a different story.
I believe the issue stems from the latest OTA update to version VS98026A. I had a custom ROM on here before, but the developer stopped support so I went back to stock doing a complete wipe through TWRP, including both caches, system, data, and internal storage. I then flashed the stock Verizon ROM for version 24A, rooted, temp unrooted to take the OTA for VoLTE, restored root, and installed TWRP. I have been unable to boot into recovery AT ALL. I have tried through the TWRP manager app and ADB. Both times I was simply presented with a fastboot screen stating processing commands eternally, I let it sit there for a good 10 minutes to be sure. I also tried different versions of TWRP, but they all either failed entirely and just rebooted normally or gave me fastboot.
I have access to ADB terminal on my PC, the TWRP manager app, fastboot (I know, not ideal), and download mode. I can flash most parts of the system through ADB, with a little help. I have the basics down.
I've got backups of everything from when I had TWRP on here before, even my EFS. Any suggestions, no matter how drastic, are welcome.
UPDATE: I've used fastboot to replace my boot, aboot, laf, and recovery partitions. Now when I enter recovery, I'm presented with the android with the red exclamation triangle, but no recovery options.
Just to try it I put TWRP back on and I still get fastboot.
Starcruiser322 said:
As I said, the phone is not currently bricked. I can do a normal boot into the OS and Download Mode, however recovery is a different story.
I believe the issue stems from the latest OTA update to version VS98026A. I had a custom ROM on here before, but the developer stopped support so I went back to stock doing a complete wipe through TWRP, including both caches, system, data, and internal storage. I then flashed the stock Verizon ROM for version 24A, rooted, temp unrooted to take the OTA for VoLTE, restored root, and installed TWRP. I have been unable to boot into recovery AT ALL. I have tried through the TWRP manager app and ADB. Both times I was simply presented with a fastboot screen stating processing commands eternally, I let it sit there for a good 10 minutes to be sure. I also tried different versions of TWRP, but they all either failed entirely and just rebooted normally or gave me fastboot.
I have access to ADB terminal on my PC, the TWRP manager app, fastboot (I know, not ideal), and download mode. I can flash most parts of the system through ADB, with a little help. I have the basics down.
I've got backups of everything from when I had TWRP on here before, even my EFS. Any suggestions, no matter how drastic, are welcome.
UPDATE: I've used fastboot to replace my boot, aboot, laf, and recovery partitions. Now when I enter recovery, I'm presented with the android with the red exclamation triangle, but no recovery options.
Just to try it I put TWRP back on and I still get fastboot.
Click to expand...
Click to collapse
Was there ever a resolution to this?
I believe I might be having the same issue.
Sent from my LG-VS980
Well, it was sort of resolved for me. If you follow the steps in THIS THREAD, you better hope you have enough battery to last through the process. If you do, great, you'll have your phone back in running order soon enough. A bit of Linux experience helps with this.
After my battery died it refused to come back on, and I brought it to the Verizon store and told them I woke up one day and it wouldn't turn on.
They replaced it under warranty.
I assume other major carriers would do the same.
Is your phone still under warranty? What model and carrier?
After a bit of searching, I did confirm that the 26A update locks the bootloader and implements tighter security policies.
Rooted ok. I went to install a clockworkmod recovery so I could backup my current ROM before I try flashing something new. Oh, I need SDK, ok, installed. Oh, I need platform-tools, ok, installed.
So I run that and then the phone reboots to a screen saying AP fastboot flash mode. I am able to get the phone working with the 3 button method; phone runs fine, but reboot goes to fastboot screen.
I installed ROM Manager. I think I properly flashed CWM, but no change.
My bootloader was locked. So I worked around, motopacalypse; now bootloader is unlocked.
Currently my computer does not show the phone in Explorer (?!).
I flashed cwm again successfully. No change.
How can I clean up this fastboot problem?
Atrix HD android 4.0.4
System version: 77.12.22.MB886.att.en.us
Also the battery icon has a question mark.
Going with more trial and error; in ROM Manager, I chose reset permissions. A flurry of code goes by. Then it suggests I reboot. I go to shut down, but the phone will not. It now perpetually shows Shutting down spinning circle. What has happened?
Boot loop probably. Just hold all power button forever .after it shuts down,hold all three buttons to get to ap again. Then chose recovery.
Sent from my ATRIX HD using Tapatalk
Hey guys,
i'm in trouble installing a custom ROM on a S4 Active (GT-I9295, Baseband IXXUDOB4, 5.0.1).
Flashed CF--Autoroot with Odin, no problem.
Then i flashed TWRP, Odin showed its green "PASS!"-message but i can't boot into recovery.
I'm well aware of the timing issue when doing the first reboot into a custom recovery, and i assure you this isn't the problem.
I tried countless times, after a while i installed ROM manager to try if i could flash the ROM file that way.
It installed another custom recovery -CWM- on top, and also showed up the TWRP recovery:
http://imgur.com/kSSiuld
Still, booting into any recovery does not work, neither from ROM managers menu or via any button-press combination.
When pressing vol up+home+power, the phone shows the blue "revovery loading"-line AND the red line *****ing about the root, but continues to boot as if it had been switched on normally.
I even looked for the ominous "install-sh" script in system/etc to understand why nothing gets me into recovery-
what the heck can this be?!
Did the same thing to S6 and S5 without any hassle, i'm stuck with this for several days now and i am running out of ideas.
Anyone...?
Not a very technical answer, but have you tried pulling the battery out for 30 seconds and trying again?
Yes we did, unfortunately, this also didn`t help.
Tried loads of things actually, still impossible to access that damn recovery
I'm a complete newbie to android phone modding, and I was really proud of myself when I was able to install the Cyanogen 12.1 and Google Apps onto my Samsung S3 Mini. However, I made the mistake of trying to put my work email on it, which requires that my phone be encrypted. Well, I guess the encryption and rooted phone didn't want to play nice together, so I got the error message that my phone would be factory reset. Boo! Well, it got worse. Instead of a factory reset, my rooted phone now is stuck in what I have now learned is called a bootloop. Basically I turn my phone on, and the Cyanogen start screen (with the text "TEAMWIN") just infinitely flashes on the screen until I pull the battery.
I have tried using Odin 3.07 and cm12.1_golden.nova.20160210.ODIN_TWRP.tar.md5. I do the three button system boot, connect the usb, run Odin, get the phone recognized, and then install the .md5 in the PDA section of Odin. It tells me that it succeeded, but when I restart my phone it's still the same bootloop. I also tried swearing, but that didn't help either.
Has anyone else out there had experience with Cyanogen and this particular error? I would love to get this phone working again... preferably with either a Lollipop version of android or back to Cyanogen 12.1.
Any info would be greatly appreciated! Thanks everyone.
So I've got an update if anyone's interested... I can't call it progress, but it's a different problem now.
I was able to download and use Odin to do what was shown on this link: http://forum.xda-developers.com/showthread.php?t=2122548&highlight=root
Everything worked in Odin, the phone rebooted, and went to the Team Win Recovery Project diagnostics screen, rebooted again, and then to the samsung logo. However, it immediately goes to the "Encryption Failed" error screen, and the only option is to 'reset device'. Of course, doing this just reboots the phone and it then has the Team Win loading screen, Team Win Recovery Project diags screen, Samsung logo, and back to the 'Encryption Failed' screen again. So now I have a new infinite loop to solve. *sigh*
any thoughts?
Have you been able to get into TWRP? If you are, maybe you could wipe everything from there and flash the recovery version of your ROM.
I was able to put the stock bootloader onto the phone using Odin, download the original tar from here: http://live.samsung-updates.com/index.php?device=GT-I8190, then used the stock bootloader to install it from the sd card. Everything went fine, but now when I boot the phone it just hangs on the Samsung Galaxy S3 mini GT-i18190 start screen indefinitely. Is this progress, or have I created a new problem now?
You're playing around with heavy stuff. I won't recommend using an upgrade flash (CM over Odin) as an full flash. Please try flashing a stock image.
If you did something wrong to the partitioning, then it's likely to not allow you to do a successfull factory reset. Maybe you can try re-flashing a stock Odin image with PIT repartitioning.
Remember to try to backup the EFS folder, doing that kind of flash might wipe it.
So I tried to mod my phone (with this, if you're interested https://forum.xda-developers.com/gal...creen-t3759567) but I did something stupid. I thought TWRP was working properly but I'd installed Oreo and didn't wipe data. Well I installed the zip anyway. At the end, an error showed up (could not mount /data or something similar) and my phone will now not boot.
If I try to boot the phone, it just vibrates and stays black. Volume Down + Power + Bixby gets the phone out of this state and the charging screen shows again. I can't boot into TWRP at all. I can boot into download mode but Odin keeps failing when I try to reflash the XEF Oreo firmware (screenshot is in the attachment, it says passed but doesn't attempt to flash the files). I managed to flash TWRP which worked but since I can't boot into it it didn't help. Anthing else I can flash with Odin, or can anybody tell me what's going on / if it's unrecoverable? (I've tried a couple of different versions, they all exhibit the same behaviour)
chemeleon said:
So I tried to mod my phone (with this, if you're interested https://forum.xda-developers.com/gal...creen-t3759567) but I did something stupid. I thought TWRP was working properly but I'd installed Oreo and didn't wipe data. Well I installed the zip anyway. At the end, an error showed up (could not mount /data or something similar) and my phone will now not boot.
If I try to boot the phone, it just vibrates and stays black. Volume Down + Power + Bixby gets the phone out of this state and the charging screen shows again. I can't boot into TWRP at all. I can boot into download mode but Odin keeps failing when I try to reflash the XEF Oreo firmware (screenshot is in the attachment, it says passed but doesn't attempt to flash the files). I managed to flash TWRP which worked but since I can't boot into it it didn't help. Anthing else I can flash with Odin, or can anybody tell me what's going on / if it's unrecoverable? (I've tried a couple of different versions, they all exhibit the same behaviour)
Click to expand...
Click to collapse
There is a newer version of odin, are you using that? You will need that to flash Oreo. Can get it in the link below. Odin v3.13.1
https://forum.xda-developers.com/galaxy-note-8/how-to/official-stock-firmware-update-odin-t3677072
Doh! Had it already, was the only one I didn't try. It's flashing now. Many thanks