So I have a very odd problem, and I'm fairly experienced with repairing, rooting, and reverting phones to stock which have custom roms, in this case I have a completely stock note 5 which was experiencing a boot loop error at the note 5 model number screen. Going through the motions I normally would, hard reset, nope, safe mode, nope, wipe cache, nope, master reset, nope, so I flash the firmware with a stock rom, which worked, but resulted in the same problem, rebooting at the model number screen just before the samsung logo every few seconds, tried 3 other firmware versions and downloads, also no. Not sure whats up with this thing, but anyone have any ideas? I personally know the user, family, phone wasnt physically damaged or exposed to water. I'm also getting no command just before entering recovery and failed to mount/ preload (no such file or directory) during the master reset. Its been forever sense I've meddled with a note 5 and cannot remember if these are normal, or related to the issue, I dont ever remember seeing these with my own note 5.
I ran into this exact same problem weeks ago on my S7. I tried flashing 7.0 on my 930V and for whatever reason the phone went into the exact same bootloop showing the Samsung logo every few seconds, vibrating, etc. I got back into download mode but wasn't able to fix it. Then went into Recovery and it only said in blue letters in the top left "Recovery rebooting" and kept flashing that message. Lucky for me I was under warranty and sent it to Samsung. They replaced it free of charge. I ended up trading for a Note 5. I kept running into issues with my S7 and network issues so I traded it.
Anyway, I'm like you in the fact I'm pretty comfortable rooting, repairing devices etc. But I still don't know what I did to mess up that S7 in Odin. Just wanted to share that I had a similar situation. Hope you were able to get a new phone or fix your issue.
sinkableelk said:
So I have a very odd problem, and I'm fairly experienced with repairing, rooting, and reverting phones to stock which have custom roms, in this case I have a completely stock note 5 which was experiencing a boot loop error at the note 5 model number screen. Going through the motions I normally would, hard reset, nope, safe mode, nope, wipe cache, nope, master reset, nope, so I flash the firmware with a stock rom, which worked, but resulted in the same problem, rebooting at the model number screen just before the samsung logo every few seconds, tried 3 other firmware versions and downloads, also no. Not sure whats up with this thing, but anyone have any ideas? I personally know the user, family, phone wasnt physically damaged or exposed to water. I'm also getting no command just before entering recovery and failed to mount/ preload (no such file or directory) during the master reset. Its been forever sense I've meddled with a note 5 and cannot remember if these are normal, or related to the issue, I dont ever remember seeing these with my own note 5.
Click to expand...
Click to collapse
My suggestion is this..
Download the latest version of TWRP
Boot to Download Mode
Odin flash TWRP
Boot to TWRP Recovery
Full wipe including internal storage x 2
Format DATA x 2
Odin flash the latest firmware for your device
(All 4 - BLUE, AP, CP, CSC)
OR
Use Smart Switch Emergency Recovery to restore the firmware.
Hope this helps. Good luck and happy flashing! Let's us know what happens.
Sent from my Samsung SM-G955U using XDA Labs
Related
They say once your device is turning on, its not a hard brick, well explain this. My motorola Nexus 6 won't boot, when I try to power it on, it shows the Google logo then shuts off immediately. When I plug in the charger from a complete power off, the white battery sign keeps flashing, it shows for 1 second then shuts off then repeats the cycle of showing the battery sign then shutting off. It boots into bootloader/fastboot mode fine, and I have tried flashing the factory image, forced flash each partition individually, YES ALL OF THEM, YES I HAVE THE LATEST SDK YES THE LATEST FASTBOOT AND ADB, YES I CHECKED THE MD5 OF THE FILES, YES I USED DIFFERENT CABLES PORTS AND COMPUTERS. it flashes fine in terminal all the files go through with result ''OKAY'' but it still shuts off immediately while showing the first google logo after i reboot. It won't even boot into stock recovery after the flash, it just shuts off after the google logo. i tried with costum revovery same result. i tried 5.0 LRX210 and 5.1 LRX22C. This isn't my first nexus, in know that flashing factory image should fix 99% of issues, ive been flashing phones and rooting for years and i know that nexus devices are somewhat impossible to hardbrick. i made sure to exhaust every option i knew of before posting here, Ive tried the toolkit and its options countless times ive had many sleepless nights now over this. Please help.
P.S I didn't purchase officially from google or Motorola, I bought it for $580 from a guy who claimed he bricked it trying to install a font pack ''iFont'' so I figured let me buy it and restore factory image, easy win. Didn't work. He said he rooted it, installed custom recovery and euphoria os rom. Then he installed the fontpack, it told him to reboot to apply changes, and when he rebooted it wouldn't boot past google screen after that. not even to the boot animation, It just shuts off. When its off and u plug in the charger it does the same thing, you just keep seeing the charging symbol over and over because its constantly rebooting. Its a T-Mobile Nexus 6 BTW, model number XT1103. I am now looking at a motherboard for the nexus 6 on ebay which is $300, as this is the only thing i see left to do. Please any help would be appreciated. I can promise a hefty $$$ reward for any individual that helps me recover it to a working state.
I think they say as long as you can get to the BOOTLOADER it's not a hard brick. But as far as the issue itself, I have no idea. You said you flashed the factory images and it still didn't help?
U manually flashed the images correct? Any errors when flashing? Are you using the flash all bat script or flashing each file separate?
Sent from my Nexus 6 using Tapatalk
Its all BS, there's not really such a thing as a soft. A Brick is a Brick. If your phone is bricked, the only fix is to send it for repair so the manufacturer can fix it. If it can be fixed without doing that, its not a brick.
rootSU said:
Its all BS, there's not really such a thing as a soft. A Brick is a Brick. If your phone is bricked, the only fix is to send it for repair so the manufacturer can fix it. If it can be fixed without doing that, its not a brick.
Click to expand...
Click to collapse
I've heard it called a "sponge" I like that lol
shard111 said:
I think they say as long as you can get to the BOOTLOADER it's not a hard brick. But as far as the issue itself, I have no idea. You said you flashed the factory images and it still didn't help?
Click to expand...
Click to collapse
coldconfession13 said:
U manually flashed the images correct? Any errors when flashing? Are you using the flash all bat script or flashing each file separate?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
rootSU said:
Its all BS, there's not really such a thing as a soft. A Brick is a Brick. If your phone is bricked, the only fix is to send it for repair so the manufacturer can fix it. If it can be fixed without doing that, its not a brick.
Click to expand...
Click to collapse
i flashed each file separately yes no errors when flashing everything went through okay but still wont pass google screen
If it can stay connected while flashing. Does it reboot when connected like charging and stay in bootloop?
Sent from my Nexus 6 using Tapatalk
coldconfession13 said:
If it can stay connected while flashing. Does it reboot when connected like charging and stay in bootloop?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
no.
but after flashing the factory img, you might have to wipe data for it to boot.
jeromechrome1 said:
They say once your device is turning on, its not a hard brick, well explain this. My motorola Nexus 6 won't boot, when I try to power it on, it shows the Google logo then shuts off immediately. When I plug in the charger from a complete power off, the white battery sign keeps flashing, it shows for 1 second then shuts off then repeats the cycle of showing the battery sign then shutting off. It boots into bootloader/fastboot mode fine, and I have tried flashing the factory image, forced flash each partition individually, YES ALL OF THEM, YES I HAVE THE LATEST SDK YES THE LATEST FASTBOOT AND ADB, YES I CHECKED THE MD5 OF THE FILES, YES I USED DIFFERENT CABLES PORTS AND COMPUTERS. it flashes fine in terminal all the files go through with result ''OKAY'' but it still shuts off immediately while showing the first google logo after i reboot. It won't even boot into stock recovery after the flash, it just shuts off after the google logo. i tried with costum revovery same result. i tried 5.0 LRX210 and 5.1 LRX22C. This isn't my first nexus, in know that flashing factory image should fix 99% of issues, ive been flashing phones and rooting for years and i know that nexus devices are somewhat impossible to hardbrick. i made sure to exhaust every option i knew of before posting here, Ive tried the toolkit and its options countless times ive had many sleepless nights now over this. Please help.
Click to expand...
Click to collapse
NONE of this suggests that your phone is a brick. In fact, it all proves that it is NOT a brick.
*which is not to say that it isn't BROKEN.
"i tried with costum revovery same result. i tried 5.0 LRX210 and 5.1 LRX22C"
Let me ask you this; did it reboot when you booted into a custom recovery? If custom recovery worked, then it seems like the unit can still be saved.
BTW: LRX22C is also 5.0. Specifically, 5.0.1. 5.1 is not available yet.
So a little bit of clarifications first;
HAVE you tried to perform a factory wipe (via recovery) or otherwise FORMAT (not "fastboot erase") the data and cache partitions? No part of your message mentions formatting the data or cache partitions. If the init is unable to manipulate/mount a possibly corrupt data or cache partition (or possibly some other partitions as well), then it WILL REBOOT.
In addition, some logs of the reboot could be useful if you are able to obtain any. A somewhat modified boot image can enable adb and kernel logging at a point from before the reboot occurs.
P.S I didn't purchase officially from google or Motorola, I bought it for $580 from a guy who claimed he bricked it trying to install a font pack ''iFont'' so I figured let me buy it and restore factory image, easy win. Didn't work. He said he rooted it, installed custom recovery and euphoria os rom. Then he installed the fontpack, it told him to reboot to apply changes, and when he rebooted it wouldn't boot past google screen after that. not even to the boot animation, It just shuts off. When its off and u plug in the charger it does the same thing, you just keep seeing the charging symbol over and over because its constantly rebooting. Its a T-Mobile Nexus 6 BTW, model number XT1103. I am now looking at a motherboard for the nexus 6 on ebay which is $300, as this is the only thing i see left to do. Please any help would be appreciated. I can promise a hefty $$$ reward for any individual that helps me recover it to a working state.
Click to expand...
Click to collapse
I don't think you need a new mainboard.
If what he explained to you is correct, then my previous about fixing corrupt data partitions should solve the issue for you.
Agree with the guy above me. Same thing happened to me on my Nexus 9. Manual flashes all successful but could not boot. Booted into recovery and did a factory wipe and all was well. I know this is the nexus 6, but it sounds like corrupted data.
My S6 edge is in a bootloop. I put off the 5.1.1 OTA for a while when my wifi would not turn on. Rebooted, still didnt work. I decided to do the update. installation went great but now its in a boot loop. I flashed the firmware (BOG7) using Odin. It worked. The phone was back on again but then it shut off after a few hours.
Its been stuck in the bootloop again. I flashed BOG7 again. Ive Flashed BOG9. Ive flashed the stock PIT. Ive tried ADB sideload. Smartswitch and Kies do not recognize the device. Of course, Ive wiped cache and factory reset. Attempted booting in safemode. All flashes were successful but when it reboots, It says "erasing" and goes to bootloop (Samsung powered by android).... Drivers are installed and working. MTP is not installed and I cant find the file.
Please .
same problem
I'm having the same problem with boot loop on g925v stock. I'm wondering if the op or anyone else can help!
No mater what I do, phone reboots after almost exactly 1min9 sec. Just enough time to select a language, but not get past the next "activation" screen.
Background: Phone has never been rooted, at first was on og5 and started freezing on the verizon logo, so I factory data reset, and after that nothing has really changed. knox has not been tripped, frp not tripped
First I tried flashing og5 with odin,
(of course checked md5, and odin=pass, then after flashing, I always tried several combinations of booting to recovery for wipe cache partition/ factory reset / and also power down by holding volume down and power button, then select boot in safe mode)
Then tried flashing og7, still boot loop
then tried flashing og9, 3 times, again, also many attempts of factory data reset/ wipe cache partition / safe mode.
I am starting to think this may be a hardware problem, BUT unfortunately I do not have samsung warranty available on this phone so I am pretty much stuck messing with it.
In researching the issue, I have run across quite a few similar freeze/boot loop problems all over the web, and never any real solutions, for both g925v, g920v, and other s6 models. I've also seen a stock s6 g920v that freezes randomly, flashing stock og9 never helped, owner was planning to replace the battery and see if that helps (I have not heard back).
I've tried looking at the boot log but I'm no expert. I know I can't downgrade, but I'm wondering if there is anything I can do with adb, or any other bootloaders that I could try flashing over the og9 (even if just temporarily, assuming I will flash stock og9 again after).
Thanks for any encouragement, help or advice.
I finally gave up on my GS6 Edge because upon carefully taking it apart for the 3rd time I noticed physical damage up by the wifi receiver and SIM card slot. My advice would be to try the things I tried (above) and, if it's not a hardware issue, it may fix the problem. Good luck.
beefriendly said:
I'm having the same problem with boot loop on g925v stock. I'm wondering if the op or anyone else can help!
No mater what I do, phone reboots after almost exactly 1min9 sec. Just enough time to select a language, but not get past the next "activation" screen.
Background: Phone has never been rooted, at first was on og5 and started freezing on the verizon logo, so I factory data reset, and after that nothing has really changed. knox has not been tripped, frp not tripped
First I tried flashing og5 with odin,
(of course checked md5, and odin=pass, then after flashing, I always tried several combinations of booting to recovery for wipe cache partition/ factory reset / and also power down by holding volume down and power button, then select boot in safe mode)
Then tried flashing og7, still boot loop
then tried flashing og9, 3 times, again, also many attempts of factory data reset/ wipe cache partition / safe mode.
I am starting to think this may be a hardware problem, BUT unfortunately I do not have samsung warranty available on this phone so I am pretty much stuck messing with it.
In researching the issue, I have run across quite a few similar freeze/boot loop problems all over the web, and never any real solutions, for both g925v, g920v, and other s6 models. I've also seen a stock s6 g920v that freezes randomly, flashing stock og9 never helped, owner was planning to replace the battery and see if that helps (I have not heard back).
I've tried looking at the boot log but I'm no expert. I know I can't downgrade, but I'm wondering if there is anything I can do with adb, or any other bootloaders that I could try flashing over the og9 (even if just temporarily, assuming I will flash stock og9 again after).
Thanks for any encouragement, help or advice.
Click to expand...
Click to collapse
Hi. I have note 5 sm-920c with multiBoot,AryaMod ROM installed as primary rom and DrKetan secondary. All well and fine since this morning when I tried an app that changes resolutions (I changed to 1080x1920 and things stared crashing: systemUI, AirView, etc). After rebooting there wasn't anything on the screen but the wallpaper. So I connected the phone to USB and ran a few ADB commands to restore the resolution. After restaring everything was back to normal. Then out of the blue my phone restarted by itself and went into a bootloop: showing the black screen with samsung galaxy note 5 (and the little red text kernel is not seandroid enforcing - because of the multiboot) and immediately restarting. It wouldn't even get to the bootanimation. So I entered recovery and first wiped cache and dalvik - same thing happened. Flashed multiboot cleaner - same thing happened.
So now I'm trying to do a full reset to install a new rom. And the phone restarts DURING the reset while being in recovery. That's what scares me - because I haven't seen anyphone do this (it's not my first flashing exp). It doesn't even go into bootloader, it just keeps restaring. Only thing that works in the custom recovery - CWM.
Do you think it's a hardware fault? Like the sdcard failing? Or just software. Should I keep on trying flashing something from the phone since the files are there and I can still access them? Can I flash anything from Odin without entering the bootloader?
I'm asking now because I think it's serious and I don't want to **** it up anymore than I already did. Warranty is a NOGO right now, I at least have to get it to stock recovery even if the knox bit is tripped.
Any help appreciated.
my galaxy note 4 (sm-n910t) caught in bootloop . i dont know what caused it. the phone simply restarts upto first bootscreen, ie upto 'samsung galaxy note 4' and then vibrates and then restarts.this process continues upto battery is down or i pull out battery.the phone is not entering to recovery mode but enters to download mode.
i have tried installing stock rom from sammobiles but it won't help.i have also installed custom recovery twrp but that also won't help to enter to recovery mode,
i am trapped pls help..
You didn't mention how you tried to install the stock ROM . Did you use Odin?
I just fixed mine with the same issue. I was able to boot into recovery and download mode but mostly download mode without bootloop when I had the usb cable plugged in. I used ADB when I could to boot into download mode, but the buttons worked too. Trying to restart the phone only lopped after the Google screen.
I followed several guides here to flash stock with Odin and wipe cache etc but none solved my boot loop issue. almost gave up but there is a video on You Tube that said the battery warping in the cause of the boot loop. The battery, after/during quick charge, may heat up and change shape causing the issue. Today I installed my new battery purchased on amazon and no more issues.
Now I am on stock and have to find a good rom.
If you do decide to flash back to stock there are a lot of good guides. You may find yourself stuck on the T-mobile screen for 15 minutes when booting for the first time but that is ok. If you still boot loop after installing stock and wiping cache I would try the battery.
Nabeel mhd said:
my galaxy note 4 (sm-n910t) caught in bootloop . i dont know what caused it. the phone simply restarts upto first bootscreen, ie upto 'samsung galaxy note 4' and then vibrates and then restarts.this process continues upto battery is down or i pull out battery.the phone is not entering to recovery mode but enters to download mode.
i have tried installing stock rom from sammobiles but it won't help.i have also installed custom recovery twrp but that also won't help to enter to recovery mode,
i am trapped pls help..
Click to expand...
Click to collapse
hi OP,
did you find any solution to your problem?
Hello all. I'm also pasting this in the T-mobile thread in case it can be of benefit to someone. This is advice to use as a very last resort if you are experiencing the recovery bootloop issue AND you don't have the emmc failure bug. I had the recovery reboot, sudden shutdown with no warning, etc. issue for the past two weeks. I tried everything on Google and Youtube to fix my problem with no success. I flashed multiple stock ROMS and recovery tars (stock and TWRP) via ODIN, but nothing worked. Oddly enough, I never received the emmc error that I have read about. Also, in the few times that my phone booted normally, I even loaded the Wakelock Power Manager app, set it to partial wakelock and my phone STILL continued to bootloop. As a last resort, I bought a new battery, but the reboot problems continued in Android 4.4.4 Kitkat, 6.0 Marshmallow, 7.1 Nougat and 8.1 Oreo ROMS. Well, here is what finally helped me to get my phone back operational. I had a backup ROM from a previous install and a TWRP flashable version of the same ROM on my SD card (in case the phone did not stay on for the full restore). I put the phone into a ziplock bag into a freezer for about 20 min. (thankfully this time TWRP stayed on long enough for me to do the following):
1) copy all the files I wanted to save from internal storage to a computer.
2) performed a full wipe (Dalvic, Cache, System, etc. Like when flashing a ROM, but this time also internal storage. Note: Please do not wipe both internal and SD card, as you may have a difficult time trying to load the ROM file back on the sd card (assuming you don't have a card reader).
3) After wiping, I was able to restore my stock ROM backup (or you can just flash the stock ROM).
I can't be 100% sure, but I think my wiping internal and then flashing the stock ROM finally did the trick. Since this morning, the phone has been pretty much back to as it was before. In either case, I'm sharing this with the hope that it helps someone else.
Sent from my SM-N910T using Tapatalk
chrismcnally123 said:
I just fixed mine with the same issue. I was able to boot into recovery and download mode but mostly download mode without bootloop when I had the usb cable plugged in. I used ADB when I could to boot into download mode, but the buttons worked too. Trying to restart the phone only lopped after the Google screen.
I followed several guides here to flash stock with Odin and wipe cache etc but none solved my boot loop issue. almost gave up but there is a video on You Tube that said the battery warping in the cause of the boot loop. The battery, after/during quick charge, may heat up and change shape causing the issue. Today I installed my new battery purchased on amazon and no more issues.
Now I am on stock and have to find a good rom.
If you do decide to flash back to stock there are a lot of good guides. You may find yourself stuck on the T-mobile screen for 15 minutes when booting for the first time but that is ok. If you still boot loop after installing stock and wiping cache I would try the battery.
Click to expand...
Click to collapse
Thanks sir! I have the same issue! it's working now after replace the battery
OK, using my phone normally rooted. I sometimes get random reboots and it bootloops. I have to force reboot a few times by holding power, bixby, volume down etc etc and it boots up normally.
This time, it did the same thing and force rebooting got me to the lockscreen but kept rebooting at that screen. I plugged in to the computer and forced reboot and it worked fine but for some reason but it made me start the whole setup process again as if I factory reset the phone but everything was still there except settings were reset.
Brightness wasn't working, so I tried to reboot to see if it would fix the problem but it started to bootlooping again and NOW I can't get past the lockscreen without it rebooting.
What do I do. I tried wiping cache in recovery but no dice. Can I reflash the firmware in odin? I don't want to lose any data. I know about flashing home csc instead but I'm rooted and I don't have the modified ap file from magisk, so wouldn't it just wipe my phone?
From my experience with the Galaxy S3 and S4, you will need to flash the firmware with Odin which will wipe everything. Use Samsung smart switch or TWRP to make a back-up of your data.
StoneyJSG said:
From my experience with the Galaxy S3 and S4, you will need to flash the firmware with Odin which will wipe everything. Use Samsung smart switch or TWRP to make a back-up of your data.
Click to expand...
Click to collapse
things have significantly changed since those days, but youre half right. In the new firmwares, there are 5 files. 3 of them have to be flashes as normal, but the last 2 are the CSC and HOME_CSC, you can shoose whichever of the 2 you want to flash depending on whether or not youll end up factory resetting. HOME_CSC doesnt wipe whereas CSC does.
OP, flash the HOME_CSC and the other 3 files as normal in Odin and you should retain your data and fix whatever part of the firmware is having a seizure. If the problem persists, then youre stuck with alternate methods of data recovery, including but not limited to ADB'ing into it while in the bootloader screen so long that you have ADB enabled in dev settings and then flashing the CSC to reset it. If THAT doesnt fix it, then youre prolly boned. Prolly a hardware issue at that point.
Where do you get HOME_CSC files from? Been looking for it for my AT&T firmware.