I have a faulty Galaxy S5 (G900M). One day I was using it normally and suddenly it rebooted and wouldn't boot to the stock ROM anymore, being stuck at the boot logo. I then decided to install CyanogenMOD and it worked. Now I want to sell the phone, so I want to revert it to stock ROM, but flashing a stock firmware gives me the same error as before.
What can be the issue?
First boot can take as long as 15 minutes. Did you allow such a length of time? IF so, pull battery, boot in recovery, wipe cache and dalvik cache, boot system and try
Related
I tried loading a different rom and thought it was bricked. I followed a guide to get it back to stock and when it boots the Verizon logo. When I boot into recovery I get this screen
EDIT: I repeated the steps and it is working!
Bad flash, download fresh and try again.
sent from my sock drawer
This is normal behavior.
When you use heimdall or odin it doesn't completely wipe data and cache before reflashing the system partition. If you are using a non-stock rom this leaves incompatible data that is used during the boot process, so the stock rom will bootloop. Once you go into stock recovery and wipe data/cache, it will remove the incompatible data and the rom will boot normally.
I'm not sure why i can't get it working but i was flashing back to stock rom. I have the correct rom and everything flashes fine on odin. I am unable to reboot to recovery. it says its loading and goes to black screen, and tries to boot to OS again. I tried flashing twrp with odin and same thing. I flashed the stock rom multiple times and it just won't boot. I even used Kies to flash it to stock rom and it was successful however stuck at boot logo again. The one thing i didnt do was wipe data/cache etc before flashing to stock rom but every tutorial i seen doesnt state to do it before the flash anyway. Has anyone ran into this problem before?
How are you able to get into download mode to flash rom but not be able to go into recovery? I had this issue once with my note 2 and went into recovery and wiped data and rebooted successfully....
I have an S4 i9505, never rooted or flashed any custom roms. Running the latest OS version from Samsung.
Phone was on the desk while I was working, suddenly it vibrated and turned off.
Now it's stuck in a boot loop, sometimes gets stuck on the Samsung logo.
Tried booting to recovery, worked on my 3rd attempt. Wiped cache, booted past the logo into the carrier logo and the SAMSUNG logo and then went back in the loop.
I have not installed any harfmul apps, I don't want to do a factory wipe yet because of precious data on the device.
Is there anything more I can try?
Download a stock ROM for your device from sammobile.com and install it using Odin. Since Odin doesn't wipe data when it installs, your data should be safe. With luck, the reinstall will correct your bootloop.
Like the title says, my phone gets stuck at the boot logo (not bootloader) after I try to flash any custom ROM to which I solve by restoring to a stock rooted nandroid backup of 6.0.
Here's my flash process:
1. Reboot to TWRP
2. Do clean wipe
3. Flash ROM (DU for example)
4. Flash gapps
5. Reboot
TWRP flashes the ROMs and necessary gapps without any issues but no matter what it gets stuck at the boot logo after rebooting. This wasn't a problem in the past as I was using Orion, DU, AICP, etc. Would using the restore-to-stock tool help in this case? The only thing stopping me from using it is the fact that it would wipe my internal storage. Any help would be greatly appreciated. Thanks!
EDIT: I decided to restore to stock and wipe user data and I'm now finally able to get past the the boot logo
How long are you waiting? First boot can exceed 20 minutes just sitting there looking like it's not doing anything...
Sometimes first boot take.more than half an hour
Sorry to revive this but Im getting the same problem... Did u managed to install any rom after u flash the stock rom? Should I do that? How long should I wait on first boot?
Hello,
I have an i9505 LTE International version (jflte) for about 4,5 years, working perfectly with the latest LineageOS until yesterday when my phone suddenly shut off itself (as like as I removed the battery). I tried then to turn it on again but restarted itself after the LineageOS logo appeared. I thought there was something wrong with the OS, so I've booted to recovery TWRP to flash the same OS again. The strange thing is that TWRP stopped flashing at +/- 20% freezing itself. After that I was not able to boot to recovery anymore.
I removed the battery, SIM card and microSD for about three hours. Tried again only with the battery and was able to install LineageOS again. After booting with the fresh installed LineageOS (I formatted the /system /data /cache partitions) the system was very unstable and slow. After 10 seconds the screen went completely pink and it shut off again and never came up (showing me the boot logo and rebooting - bootloop).
I removed the battery again and tried to flash, after one day, with odin the stock firmware. I had no issues while flashing but the OS won't boot. Therefore I flashed the TWRP to the recovery partition and it doesn't work. After 10 minutes without the battery I am able to boot TWRP but when I try to, for example, copy the logs to /data TWRP freezes and I cannot do anything else but hard reboot.
Someone knows what's going on here? Could the eMMC be seriously damaged/corrupted?
The strange thing is that, without the battery for 10 minutes plugged in, I am able to boot to TWRP and navigate through the menu - although after trying to format the /data and /cache partitions TWRP freezes. After a reboot I cannot boot to recovery anymore (it remains stuck on the samsung logo screen with the RECOVERY BOOTING and Set Warranty Bit: recovery headings.
My fathers old S4 has a similar issue, https://forum.xda-developers.com/galaxy-s4/help/s4-i9505-wont-past-screen-boots-t3810088
It seems so strange, I'm currently trying to get the files left on the phone safely of but it crashed when trying to do so and now I can't enter recovery.
But I'm trying to troubleshoot it as good as possible without risking loosing the files, and the strange this is that many S4s seems to have problems with the fact that it is a random restart and then goes into bootloop. But the thing that worries me the most is the fact that you were running Lineage while my father was running stock TouchWiz based on 5.0.1. That leads me to believe that this is a hardware issue, I'm considering unscrewing it and try to troubleshoot it. Going to get my hands on my fathers old extra batteries for his S4 tommorow, will see if that makes a difference.
Did you wipe the /data partition after flashing the stock rom? I had the same issue... After flashing LOS, my phone is bootlooping randomly and i tried to flash stock rom. ODIN does not wipe the data partition after flashing the original stock samsung firmware so the OS can`t boot due incompatible data( The lineage os data with android 7.1.2 is not compatible with lollipop). Try to flash the stock rom again, wait until your device restarts to the robot and hold the vol up+home+on/off to get into stock recovery. Perform a factory reset and then restart. You have to wait a bit (maybe 10 min)