Related
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
So first off thanks for reading and trying to help.
I am having the following problem:
First of no updates were installed recently. I did update to the latest December update in early January.
Few days ago my phone SM-N910T froze up and seemed to have shut down. After being unable to restart i pulled the battery, put it back in and nothing happened. I left it out for 5 minutes plugged it back in and the phone booted up. But as soon as the screen turned off the phone heated up and would not turn on. I've been dying to just start anew anyway so I tried using Kies to restore the phone however this failed twice.
I downloaded Odin and Stock N910T3UVS3EPK2.
I flashed TWRP Recovery. And then tried to Flash the firmware which failed several times and i started getting errors.
“Could not do normal boot, mmc_read failed”
Kernel is not seandroid enforcing
as well as others.
After rebooting it several times it started working I was able to log in and set everything up, but the phone started freezing up again.
I blew everything away did a Data Wipe in TWRP. I then downloaded N910T3UVS3EPK2 Stock Rooted Odex from here.
When trying to flash it, it failed several times. and i started getting No Pit Binary errors. After trying several times with different cables and USB ports it finally took. But i am still having the same problems with freezing and restarting.
THE ONLY THING THAT HELPED: And this is a band aid fix, is I installed the wake lock app from the google store and enable Partial Wake Lock.
The phone is stable but only until i restart it at which point it goes into Download Mode and i have to restart several times and prey it boots up.
HALP! :crying:
I had the same problem, and MANY MANY others have this issue too. For months i fought with it without any success. I ordered new motherboard and now my phone is working again.
Please check General forum. There is a big thread about installing KitKat from another phone which apparently fixed this issue. Dig around that thread and read about it, might be a solution!
AntonJart said:
I had the same problem, and MANY MANY others have this issue too. For months i fought with it without any success. I ordered new motherboard and now my phone is working again.
Please check General forum. There is a big thread about installing KitKat from another phone which apparently fixed this issue. Dig around that thread and read about it, might be a solution!
Click to expand...
Click to collapse
I saw that thread, but most of those people started having the issue after the update. If the kit kat update fixes it then i'm at a loss. And since a new board fixed the issue for you that means most likely the the memory is beginning to fail. That's how SSDs die anyway.
tempy1 said:
So first off thanks for reading and trying to help.
I am having the following problem:
First of no updates were installed recently. I did update to the latest December update in early January.
Few days ago my phone SM-N910T froze up and seemed to have shut down. After being unable to restart i pulled the battery, put it back in and nothing happened. I left it out for 5 minutes plugged it back in and the phone booted up. But as soon as the screen turned off the phone heated up and would not turn on. I've been dying to just start anew anyway so I tried using Kies to restore the phone however this failed twice.
I downloaded Odin and Stock N910T3UVS3EPK2.
I flashed TWRP Recovery. And then tried to Flash the firmware which failed several times and i started getting errors.
“Could not do normal boot, mmc_read failed”
Kernel is not seandroid enforcing
as well as others.
After rebooting it several times it started working I was able to log in and set everything up, but the phone started freezing up again.
I blew everything away did a Data Wipe in TWRP. I then downloaded N910T3UVS3EPK2 Stock Rooted Odex from here.
When trying to flash it, it failed several times. and i started getting No Pit Binary errors. After trying several times with different cables and USB ports it finally took. But i am still having the same problems with freezing and restarting.
THE ONLY THING THAT HELPED: And this is a band aid fix, is I installed the wake lock app from the google store and enable Partial Wake Lock.
The phone is stable but only until i restart it at which point it goes into Download Mode and i have to restart several times and prey it boots up.
HALP! :crying:
Click to expand...
Click to collapse
Do you have "T3"or "T" model?
The files given below is for "T" variant do not try if you have T3.
It sounds crazy to tell you but trust me this will work.
Put your phone in freezer for about 2 hours then do the steps below if you want to recover your device as it was before.
Go to download mode
Flash 5.0.1 modem via odin choose (CP) tab this will fix emmc read fail error.
https://www.androidfilehost.com/?fid=24052804347820086
Dont reboot to system go to download mode again.
Then flash full 5.1.1 lollipop ok1 firmware
https://www.androidfilehost.com/?fid=312968873555011894
.once it pass dont let the phone reboot.
Go to stock recovery and wipe cache & data factory reset.
Reboot wait 10 minutes dont touch anything let the phone rest.
Complete setup and dont download anything any apps go to software update and take all marshmallow ota updates.
Once finish do factory reset again and you will get clean operating system without any issues.
Trex888 said:
Do you have "T3"or "T" model?
The files given below is for "T" variant do not try if you have T3.
It sounds crazy to tell you but trust me this will work.
Put your phone in freezer for about 2 hours then do the steps below if you want to recover your device as it was before.
Go to download mode
Flash 5.0.1 modem via odin choose (CP) tab this will fix emmc read fail error.
https://www.androidfilehost.com/?fid=24052804347820086
Dont reboot to system go to download mode again.
Then flash full 5.1.1 lollipop ok1 firmware
https://www.androidfilehost.com/?fid=312968873555011894
.once it pass dont let the phone reboot.
Go to stock recovery and wipe cache & data factory reset.
Reboot wait 10 minutes dont touch anything let the phone rest.
Complete setup and dont download anything any apps go to software update and take all marshmallow ota updates.
Once finish do factory reset again and you will get clean operating system without any issues.
Click to expand...
Click to collapse
I have the " T " variant
I've read this before. I am a logical person I want to understand why this would work. Also when placing the phone in the freezer (i feel like i'm being pranked) do i place it in there with the battery?
I will definitely try this since I have nothing to lose. But i have a phone heavy next few weeks and i don't have a backup
tempy1 said:
I have the " T " variant
I've read this before. I am a logical person I want to understand why this would work. Also when placing the phone in the freezer (i feel like i'm being pranked) do i place it in there with the battery?
I will definitely try this since I have nothing to lose. But i have a phone heavy next few weeks and i don't have a backup
Click to expand...
Click to collapse
Without battery in freezer.
No idea how it works but good thing is hopefully it will work cuz lot of users even recover their hard bricked devices by this.
As you said you have nothing to lose so give it a try and make sure be patient dont give up and do this when you have enough time to do at least couple of hours.
I should mention that I had an 'injured' 910t after upgrading, and the freezer thing worked for months. I think there is a thermal issue and something is physically getting de-soldered in the motherboard. @Trex888, I will try your fix - I got a NEW Note4 2 weeks ago and it is running 5.0.1 and it bricked....
IF ANY OTHER COMPANY SOLD A PHONE WITH STYLUS, i WOULD TOSS THE NOTE4 IN THE TRASH....
keithwwalker said:
I should mention that I had an 'injured' 910t after upgrading, and the freezer thing worked for months. I think there is a thermal issue and something is physically getting de-soldered in the motherboard. @Trex888, I will try your fix - I got a NEW Note4 2 weeks ago and it is running 5.0.1 and it bricked....
IF ANY OTHER COMPANY SOLD A PHONE WITH STYLUS, i WOULD TOSS THE NOTE4 IN THE TRASH....
Click to expand...
Click to collapse
so wait the freezer thing was not even a permanent fix?
No, the freezer sometimes helps you get a bricked device so that it turns on. It doesn't fix thermal issues. I believe it helps some electrical connection that has broken come into contact again.
I can't go to download mode or recovery. I tried both ways But there is no way to use my device.
Trex888 said:
Do you have "T3"or "T" model?
The files given below is for "T" variant do not try if you have T3.
It sounds crazy to tell you but trust me this will work.
Put your phone in freezer for about 2 hours then do the steps below if you want to recover your device as it was before.
Go to download mode
Flash 5.0.1 modem via odin choose (CP) tab this will fix emmc read fail error.
https://www.androidfilehost.com/?fid=24052804347820086
Dont reboot to system go to download mode again.
Then flash full 5.1.1 lollipop ok1 firmware
https://www.androidfilehost.com/?fid=312968873555011894
.once it pass dont let the phone reboot.
Go to stock recovery and wipe cache & data factory reset.
Reboot wait 10 minutes dont touch anything let the phone rest.
Complete setup and dont download anything any apps go to software update and take all marshmallow ota updates.
Once finish do factory reset again and you will get clean operating system without any issues.
Click to expand...
Click to collapse
So i recently had a baby, thus i had no time at all to get my phone to work. WakeLock app was working alright.
But last night the phone just died. all attempts to revive failed. I left it in the freezer until the morning and it booted up but quickly locked up after about 5 minutes of use and became unresponsive.
I tried your method.
I failed right away. Modem could not be written..
I tried flashing the pit files like i did previously and that failed as well.
Any suggestions are appreciated. I am phoneless
EDIT#2: After I left the phone in the freezer for longer (3 hours). The odin firmware update went through !!!! This furtherst i've gone so far.
I went into recovery and did everything you said.
BUT now i have Kernel Panic Upload Mode on my screen with a little green android
EDit#3 few battery pulls later. And an over 15 minute wait time on the android logo and then about the same on the t-mobile logo i got into the OS. I did the OTA update, the phone heated up and a few restarts later it froze up like it did previously
Back to square 1
EDIT: THIS helped for a few days
https://forum.xda-developers.com/note-4-tmobile/general/ddi-mmcread-failed-boot-error-fix-t3434335
Day 2: and all went back to the phone not waking up and after screen is turned off
Hello Friends,
Yesterday I was chatting on whatsapp and suddenly my le2 restarts, and then a blue splash screen appears and device keeps on booting,
hence I went to recovery and clear the data, but that also didnt help me,
Then i flash the 13s rom via Flashone 1.9 then also same problem happens, sometimes it went to optimizing apps 3 of 4 and again restarts with blue LED, i were unable to switch it off,
after draining the whole battery I keep mobile to charge but now it is not charging, it only showing Red Solid LED Continuously.
Now I am also Unable to boot into recovery or fastboot mode.
I again flash the stock 13s rom via flashone 1.9 , i got success msg but then also mobile is not booting nor it is charging.
Note: I am on complete stock rom on locked bootloader, never unlocked or rooted, used as come in box.
Please give me a solution on this, I have searched everywhere but not getting any solutions.
Thanks in advance
Try to check your USB cable, most of the time charging issue is due to cable
shubham1358 said:
Try to check your USB cable, most of the time charging issue is due to cable
Click to expand...
Click to collapse
Cable is ok. I have another Le2 and it is charging with that cable very well
I am facing same problem. How you solve this issue? Blue led blinks after flashing any rom and bootloop.
xerol said:
Hello Friends,
Yesterday I was chatting on whatsapp and suddenly my le2 restarts, and then a blue splash screen appears and device keeps on booting,
hence I went to recovery and clear the data, but that also didnt help me,
Then i flash the 13s rom via Flashone 1.9 then also same problem happens, sometimes it went to optimizing apps 3 of 4 and again restarts with blue LED, i were unable to switch it off,
after draining the whole battery I keep mobile to charge but now it is not charging, it only showing Red Solid LED Continuously.
Now I am also Unable to boot into recovery or fastboot mode.
I again flash the stock 13s rom via flashone 1.9 , i got success msg but then also mobile is not booting nor it is charging.
Note: I am on complete stock rom on locked bootloader, never unlocked or rooted, used as come in box.
Please give me a solution on this, I have searched everywhere but not getting any solutions.
Thanks in advance
Click to expand...
Click to collapse
I also have the exact same problem. Phone started rebooting as soon as it booted up. Somehow i managed to unlock the bootloader, but to no avail. Can't seems to find any rom which can boot up. So practically i have a bricked device with trwp. Formatted the system and other partitions with twrp, flashed many roms. Still the result is same. Bootloops.
Hi,
try to to reimage your phone with QFIL from this site:
https://www.techpoison.in/2017/12/how-to-flash-letv-le-2-x526-stock.html
I downloaded everything from there, QFIL, Sparse image and drivers. My phone was bricked, but its working normally now. After you flash the image your phone should charge normally, just try to boot it up. In my case i had issues with baseband, not detected, no sim function and no wifi and phone was restarting each 3-4 minutes, but it was operable. Basedband issues can be solved by hard reseting the phone and updating it to 21s using the local update, just put the 21s stock renamed to update.zip to internal storage and run system update. When you get the error - APK missing, just boot it up again and retry the local update, should work fine the second time, i just deleted the update.zip and put back again and ran the update.
---------- Post added at 03:24 PM ---------- Previous post was at 03:18 PM ----------
Forthe55 said:
I also have the exact same problem. Phone started rebooting as soon as it booted up. Somehow i managed to unlock the bootloader, but to no avail. Can't seems to find any rom which can boot up. So practically i have a bricked device with trwp. Formatted the system and other partitions with twrp, flashed many roms. Still the result is same. Bootloops.
Click to expand...
Click to collapse
Flash the 21s bootloader + modem, one ZIP file, should work fine. Not sure what ROM did you install last time. You can give it a shot with with MIUI 10 - its nougat.
I had similar issues, see my topic, maybe it helps a bit.
https://forum.xda-developers.com/le-2/help/x526-bricked-unknown-baseband-4g-t3838093
Modem + bootloader 21s.
https://drive.google.com/file/d/0B_R...FxTGxlMHM/view
Brother same thing happened to me, a week ago. I cant say about your problem but my problem was due to faulty power button. Actually due to that reason my phone actually kept restarting itself. It showed red light blinking while charging and wasn't able to bypass the optimizing app screen. I also thought it was a software issue but actually it wasn't. I spent about 2 hours figuring out what the actual problem was. The problem was: As we know when power button is hard pressed for about 10-15 seconds it reboots itself.
Although the repair shop guy didn't put new power button but he added a tiny piece of paper in between the power button and body housing to prevent the issue and voila the problem was solved.
delltech1 said:
Hi,
try to to reimage your phone with QFIL from this site:
https://www.techpoison.in/2017/12/how-to-flash-letv-le-2-x526-stock.html
I downloaded everything from there, QFIL, Sparse image and drivers. My phone was bricked, but its working normally now. After you flash the image your phone should charge normally, just try to boot it up. In my case i had issues with baseband, not detected, no sim function and no wifi and phone was restarting each 3-4 minutes, but it was operable. Basedband issues can be solved by hard reseting the phone and updating it to 21s using the local update, just put the 21s stock renamed to update.zip to internal storage and run system update. When you get the error - APK missing, just boot it up again and retry the local update, should work fine the second time, i just deleted the update.zip and put back again and ran the update.
---------- Post added at 03:24 PM ---------- Previous post was at 03:18 PM ----------
Flash the 21s bootloader + modem, one ZIP file, should work fine. Not sure what ROM did you install last time. You can give it a shot with with MIUI 10 - its nougat.
I had similar issues, see my topic, maybe it helps a bit.
https://forum.xda-developers.com/le-2/help/x526-bricked-unknown-baseband-4g-t3838093
Modem + bootloader 21s.
https://drive.google.com/file/d/0B_R...FxTGxlMHM/view
Click to expand...
Click to collapse
Hi, Thanks. I actually did that first, flashing through qfil the same rom. it helped me to go to settings after umpteen attempts to go past language selection screen, and i was just able to oem unlock and enable usb debugging (actually after a 2nd partial failed flashing). the phone kept freezing within seconds of booting up. Now After i unlocked the bootloader and installing twrp and flashing many roms thru twrp, i am still having the same problem of booting up and freezing at start-up. cant flash again through qfil, as i will again loose the unlocked bootloader and twrp.
At least , now i can try different roms to see which can unbrick it. last one used was the twrp flashable rom based on eui (small eui by aurel) but it also freezes on language selection screen or beyond.
I am running out of ideas, lets see.
2nd partial failed flashing? any issues during the flash process? i had some issues when i used usb 3.0, 2.0 worked fine for me. If you have also charging issues stay in twrp and let the phone charge properly, its slower but should work fine. You can try to flash the 21s bootloader with modem, maybe it will boot properly. But try it only when you are able to enter the fastboot mode, longpress volume down and power for 10-15 seconds, if that is working you should be able to flash twrp via fastboot and you can experiment a bit. Try to find the chinesse twrp 3.0.2.0 and try to flash the stock 21s version. Should be also an image file, in standard twrp go to install - image, after selecting the image file click on recovery and install, after installation go back, reboot, recovery. Copy 21s to storage, wipe data, cache, dalvik and flash it, chinesse twrp will skip version check and will let you install the stock image, after install reboot but click on do not replace recovery button - this will keep the chinesse twrp installed.
If nothing helps it can be only a HW failure, maybe the power button, try usb 2.0 port during the flash process, i had issues with 3.0 on my pc, if that doesnt help.try a different cable, no more suggestions, sorry.
delltech1 said:
2nd partial failed flashing? any issues during the flash process? i had some issues when i used usb 3.0, 2.0 worked fine for me. If you have also charging issues stay in twrp and let the phone charge properly, its slower but should work fine. You can try to flash the 21s bootloader with modem, maybe it will boot properly. But try it only when you are able to enter the fastboot mode, longpress volume down and power for 10-15 seconds, if that is working you should be able to flash twrp via fastboot and you can experiment a bit. Try to find the chinesse twrp 3.0.2.0 and try to flash the stock 21s version. Should be also an image file, in standard twrp go to install - image, after selecting the image file click on recovery and install, after installation go back, reboot, recovery. Copy 21s to storage, wipe data, cache, dalvik and flash it, chinesse twrp will skip version check and will let you install the stock image, after install reboot but click on do not replace recovery button - this will keep the chinesse twrp installed.
Click to expand...
Click to collapse
My phone has been flashed multiple times by qfil method. And always it hangs at initial setup (so it boots up, but hangs at language selection or further up screens, before setup can complete and launcher could be loaded).
While trying to flash again with qfil once it stopped at 25 percent (because the battery went dead). Charged the battery and booted up the phone, and i was surprised it booted up. After 2-3 attempts i was able to reach the launcher screen and immediately enabled developer options and oem unlock / usb debugging. Only had few split seconds to do this and the phone froze again. After that i installed twrp and hence treying different roms. Most fail at setup.
Just tried MIUI 9PRO ROM. It also froze at setup multiple times, but once i was able to complete the setup and miui launcher is up , but it reboots or turn off the phone just after that. So cant do anything with the phone. Unsure of whether a newer bootloader will help in these freezing issues as i have been able to boot up at least in some roms only if for few seconds. Will try to tinker the settings of miui rom (if the phone let me do it before freezing/hanging). Lets see. Thanks for suggestions. More suggestions welcome, because i am still unsure weather this is a software or hardware related problem. I am guessing that it may have something to do with Google security as earlier i was getting msg that phone has been wrongly resetted and needs to verify with Google (but i couldn't get a chance to use the same account, as phone kept freezing at setup).
Did you fully charge the battery, if not let it fully charge in twrp. Flashing the roms in twrp works everytime or do you see any errors? Before you flash anything disconnect the usb cable.
---------- Post added at 09:54 PM ---------- Previous post was at 09:47 PM ----------
Try to flash the 21s bootloarder with modem, one zip using twrp. Go to fastboot mode and wipe modems. fastboot erase modem1st fastboot erase modem2st. Put the phone to flash mode and reimage with qfil. Before you do it write down both imeis, you can find them also on the original package on the backside. Also try to remove all sim cards from the phone and try a different cable. If nothing helps, hw issue, maybe the power button mention earlier in this thread.
After reflash skip everything at setup and reset phone to factory defaults. OEM is already unlocked, you dont have to do it again.
I have charged the phone fully before any flashing after that error. I can flash the phone through twrp without any error msg. The phone boots up most of times in various roms but hangs at or after the initial setup screens show (like language selection etc). Flashed the modem+bootloader, success, but it showed bootloader version as 20s (not 21s). Tried the commands u mentioned to erase modems, it say error failed, no such partition found. I had checked the partitions with parted and 56 partitions are there including the modemst1 & 2.
Now re flashed via qfil , did as advised but again the same problem of hanging / freezing at or after initialization screens of various roms.
Forthe55 said:
I have charged the phone fully before any flashing after that error. I can flash the phone through twrp without any error msg. The phone boots up most of times in various roms but hangs at or after the initial setup screens show (like language selection etc). Flashed the modem+bootloader, success, but it showed bootloader version as 20s (not 21s). Tried the commands u mentioned to erase modems, it say error failed, no such partition found. I had checked the partitions with parted and 56 partitions are there including the modemst1 & 2.
Now re flashed via qfil , did as advised but again the same problem of hanging / freezing at or after initialization screens of various roms.
Click to expand...
Click to collapse
Yeah sorry i screwed the command its fastboot erase modest1 modemst2, my bad.
Just now i was able to complete the initialization (setup screen) of sparse image india rom. I can reach the launcher and settings for few seconds before the device freezes or reboots.
So the same problem , with which i started, the only good thing is that i have been able to set oem unlock to on, so that i can flash trwp and various roms (but all fail with the same freezing issues)
Forthe55 said:
Just now i was able to complete the initialization (setup screen) of sparse image india rom. I can reach the launcher and settings for few seconds before the device freezes or reboots.
So the same problem , with which i started, the only good thing is that i have been able to set oem unlock to on, so that i can flash trwp and various roms (but all fail with the same freezing issues)
Click to expand...
Click to collapse
So you erased modems and reflashed with qfil right? If so i assume its a HW problem. Try the fix with the power button, i ran out of ideas
Last thing which can help maybe: https://www.youtube.com/watch?v=LH3VOIlLfvo&t=135s
Download 21s stock image + the chinesse twrp, links should be under the video, i think so, or look somewhere in the forum for new links. Try to reflash the 21s, some people reported that freezing issues were gone after installing the latest EUI. Basically you can do the same after QFIL reflash but you need enough time to copy the ZIP file as UPDATE.ZIP to the internal storage and run the local update via setting, system update and local update, i hope that TWRP will work for you, just follow the video tutorial.
delltech1 said:
Last thing which can help maybe: https://www.youtube.com/watch?v=LH3VOIlLfvo&t=135s
Download 21s stock image + the chinesse twrp, links should be under the video, i think so, or look somewhere in the forum for new links. Try to reflash the 21s, some people reported that freezing issues were gone after installing the latest EUI. Basically you can do the same after QFIL reflash but you need enough time to copy the ZIP file as UPDATE.ZIP to the internal storage and run the local update via setting, system update and local update, i hope that TWRP will work for you, just follow the video tutorial.
Click to expand...
Click to collapse
Did that also, the same problem. The phone freezes after the os is booted. I was wondering what is that isnt touched by flashing ( in download mode or fastboot mode or through twrp). I may need to tinker that. The roms are all fine in the sense they all stop at the same points. Something in the phones partition, which isnt touched by flashing? (There must be, as i flashed with qfil, the oem unlock remains, the bootloader didn't lock, and it remains unaffected by re-imaging)
Try this, maybe it helps:
https://forum.xda-developers.com/le-2/help/issues-installing-twrp-rom-le-s3-x522-t3618662/page2
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
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