Providing a summary in the beginning, to help you understand the situation.
Summary: Left phone to charge overnight. Woke up to a bootloop stuck at the model name screen.
After a long night with friends, I came home with my phone at around 8% battery. Since I had a lot of work to do in the morning, I decided to charge it overnight and have a full battery to work with. However, things went upside-down as I woke up.
Sleepy me thinks it's just one of those auto-restart updates, but after over 30 minutes, it's still stuck at the model name. That's when I start to get worried. I boot it to the recovery, where "E: [libfs_mgr] is_dt_compatible (): firmware info was not valid : '/proc/device-tree/firmware/android/compatible: No such file or directory" appears at the bottom, followed by a "dm-verity verification failed..." message. I don't know why my phone's behaving like this or stuck in this loop since I use it only for simple things (messaging, calls, social media, browsing etc.).
The only way to turn the phone off when it's stuck in this bootloop is by holding the Volume Down + Power button for a few seconds while the phone is connected to the charger. Any other method, just results in it restarting and bootlooping all over again. I tried booting it into safe mode, but that too, obviously failed.
I live in India but for the better part of the last three years, I've been a student at a university here in Japan. My graduation is next week, and I'm scheduled to go back to India and work in mid-April. As a result, I've got a lot of items to sell, and to give up the house I lived in and complete the procedures that one usually does when exiting the country (bank accounts, insurance etc.). However, since I have a sim card here in Japan, a lot of the mentioned items are linked to it, making it difficult now that I can't use it.
I've so far wiped all data and cache on my phone, and it still won't boot properly. I'm really scared but holding it together. If any of you have any idea what to do with regards to this, please comment.
Try flashing the latest firmware from sammobile. Use Odin... If you haven't done that
---------- Post added at 08:52 AM ---------- Previous post was at 08:51 AM ----------
Dm me if u need further help with that
same problem with note8 n950n
soyuz4u said:
Try flashing the latest firmware from sammobile. Use Odin... If you haven't done that
---------- Post added at 08:52 AM ---------- Previous post was at 08:51 AM ----------
Dm me if u need further help with that
Click to expand...
Click to collapse
I have the exact issue like him, tried to flash stock firmware , but doesnt want to install it.
Tried to flash only PIT file, no luck.
It happened exactly like he described, during an over the night charge, then stuck in the model name screen. Not even Samrt Switch doesnt reconise it
Safe mode
Have you tried booting into safe mode?
+1, just woke up after overnight charge and stuck in bootloop,
-> unable to power off by pressing power key + volume down, had to open back glass to disconnect battery to turn it off, glass was already little cracked, so didn't mind opening it up.
-> when i try recovery mode key combo, it stays in model name screen for a brief period and then goes into the beginning of "installing update" recovery screen but after that restarts again to "samsung note 8" model name screen.
-> tried using odin 13.3 with firmware from sammobile, used the latest one available date 2021-8-2, odin resulted in pass But after restart in installing firmware step, it stopped at 24% with an error yellow exclamation and then restarts and runs into install firmware loop.
Anyone have solved this without loosing data?
Flash official rom using odin
Related
I bought this on swappa and it was previously rooted. The guy restored it to DOK2, non-rooted before he sold he told me. I got it and it worked fine. I turned it off, wanted to go to download mode for ODIN, and nothing. The screen won't turn on, no LED lights up with charger plugged in or anything. I left the battery out for about 30 minutes, and held the power button to get rid of any residual power.
Finally I try one last time and it turns on, but get some weird message and goes straight to the download screen.. Screenshots attached
This first
Hooked to ODIN (both 3.09 and also tried 3.10.6) and it shows that it's added succesfully. As soon I tried flashing something, it said PIT partition not available..
Downloaded the complete firmware to hopefully reset it, and again, same error. Phones shows this
What can I do?? I hope theres some master flash I can do to bypass ODIN and reset the phone.. If I remember correctly, my last S4 was able to be flashed in a different mode to factory image. Anything like this? Hopefully or it be 350 down the drain..
Tried again and on the phone shows another error this time under UDC start " mmx_read fail"
I have an update, hope it helps.. After sitting for X amount of time, I can boot the phone up normally and everything works as intended. However as soon I turn it off, it won't turn back on for X amount of time again. However long it takes for it to completely discharge. Holding down the power button without the battery inside doesn't seem to make a difference.
I tried doing a factory reset, however since that shuts the phone down, it again won't come back on until I wait...
And I cannot flash anything in ODIN, no new firmware or anything since it has the PIT error described above. I DO have another note 4, same specs, company that is rooted. Any way to take the PIT partition of that one and copy it to ODIN to try and fix the broken one?
When you say you flashed the full firmware with Odin did that include the pit file. It's not generally needed unless the partition is messed up. Here is the link to the pit file posted by eduardog131
https://www.androidfilehost.com/?fid=24369303960684492
I have not used this file myself, sorry I could not be more help
Hi All,
Sorry if this is asked before. I have a new Note 5 unlocked. I turned it on yesterday and started using it. Late at night, its screen froze. I tried pressing Power+Volume_Down buttons to restart the phone. The phone restarted but the the screen was black. Only the notification light was on (blue).
In the morning, the light was still on and the phone was froze. I tried restarting it and I succeeded it. Then I realized the phone was very, I mean veeeery slow. By the time, a firmware update notification popped up. I believe it was Marsmallow update. I hit the yes button. The phone started the update and was stuck at %24. Then it restarted itself. The update process starts over and when it reaches %24, it starts over.
This happened before with my note 4 when I tried to root it. This phone is brand new and is not rooted. However, I transferred my Google profile but I did not select to download my previous apps. So, I don't think it is rooting issue but stucking at the same percentage makes me nervous.
I tried to get into recovery mode but the button combination does not work at all. So I can neither factory reset nor clear the cahe partition. When I press Volume_Down+Home+Power buttons, a custom rom download screen appears but Volume_Up+Home+Power buttons do not work at all. I cannot shut off the phone. It constantly restarts itself, starts the update, fails at %24 and starts the process over again.
What might be the problem? How can I fix this?
Regards
Hi,
Try flashing some stockfirmware via Odin (ideally something of the same android version i.e. lollipop/marshmallow). Once it's installed you should be able to access recovery from which I strongly recommend clearing your cache afterwards as you've already suggested. If you are not worried about loosing any data, then flash new firmware that is inclusive of BL/CP/CSC files too (each one has a category for such in Odin). With the latter, by all means flash marshmallow etc. :good:
Regards
Dear all,
I have a Samsung Galaxy Tab S2 8.0 WIFI purchased last year (exactly to the day) in Cali. I believe it came with 5.1.1 XAR version.
A month later, my troubles began. I flashed with 6.0 Samsung WIFI ROM from some other country and the tab soon started to randomly turn off while being used. I am not sure if this is coincidental or not. When restarted, it would sometime fully boot, only to turn off while doing any mundane task surfing etc. and at other times, start and turn off as soon as the SAMSUNG logo comes. Weirdly, when I wait a day or two, it would start fully and work for a few minutes to half an hour
When I put it to charge, only rarely does the green battery logo came up, but most frequently I got a flashing thunderbolt sign.
I sent it to Samsung and it came back apparently with the correct firmware installed and the repair note said, faulty data cable replaced. But in a week of usage, the same problems started. I don't live in the US currently and so I don't have local warranty and don't have any means to send it back to Samsung USA. I've tried all remedies I could find, charging it to 100%, holding volume down and power for 15-30 seconds to simulate a battery reset, etc. to no avail. These days. it wouldn't even stay on long enough to access recovery mode, before turning off.
Yesterday, I installed Nougat 7.0 ROM from XAR on it and tried to start it. same problem. It says updating applications xx out of 26, and then turn off. When I try to access recovery, I got the android logo and when it gets to "Erasing", it would turn off. Then now that the warranty has expired, I installed TWRP (twrp_3.1.0-1_sm-t710_13317.tar) and this time I somehow goto to TWRP recovery mode, I just left it on there to see how long it would last, instead of immediately erasing the caches and restarting.
After that once, I couldn't get it to stay on long enough to access recovery. So I tried to go back to OEM ROM using Smart Switch, but to no avail once again. The Download mode still says Custom even after Smart Switch emergency recovery
I have tried flashing various other things (5.1.1 Samsung ROM, 6.0 ROM from UK with AP, BL and CSC files, TWRP 5.1.1 permissive ROM, TWRP), in various jumbled orde,r out of frustration. Nothing worked. here's a list of ROMs I've tried:
T710XXU2DQCL_T710UVS2DQC1_EON
SM-T710_1_20170406180713_vd28gnex7t_fac
SM-T710_1_20170330211239_qkurg70e9y
5.1.1_T710XXU1BOH7_T710XAR1BOH7_XAR
twrp_2.8.7.1_LL_5.1.1_t710
twrp_3.1.0-1_sm-t710_13317
t710_5.1.1_boot
Right now, the only thing I can access is Download mode and it says Current Binary: Custom, System Status: Custom, AP SWREV B:2 K:0 S:0 and worse than before, the tab turns off at the Powered by Android logo and when I plug it in, it doesn't charge but I get this boot loop (with the just the powered by android screen flashing)
would it help to re-partition and nand erase all and install a fresh ROM with a PIT file, if so can someone please share me their PIT file for this model??
I am out of ideas, and ready to break this expensive brick
appreciate any help,
thanks
V
vvsarana said:
Dear all,
I have a Samsung Galaxy Tab S2 8.0 WIFI purchased last year (exactly to the day) in Cali. I believe it came with 5.1.1 XAR version.
A month later, my troubles began. I flashed with 6.0 Samsung WIFI ROM from some other country and the tab soon started to randomly turn off while being used. I am not sure if this is coincidental or not. When restarted, it would sometime fully boot, only to turn off while doing any mundane task surfing etc. and at other times, start and turn off as soon as the SAMSUNG logo comes. Weirdly, when I wait a day or two, it would start fully and work for a few minutes to half an hour
When I put it to charge, only rarely does the green battery logo came up, but most frequently I got a flashing thunderbolt sign.
I sent it to Samsung and it came back apparently with the correct firmware installed and the repair note said, faulty data cable replaced. But in a week of usage, the same problems started. I don't live in the US currently and so I don't have local warranty and don't have any means to send it back to Samsung USA. I've tried all remedies I could find, charging it to 100%, holding volume down and power for 15-30 seconds to simulate a battery reset, etc. to no avail. These days. it wouldn't even stay on long enough to access recovery mode, before turning off.
Yesterday, I installed Nougat 7.0 ROM from XAR on it and tried to start it. same problem. It says updating applications xx out of 26, and then turn off. When I try to access recovery, I got the android logo and when it gets to "Erasing", it would turn off. Then now that the warranty has expired, I installed TWRP (twrp_3.1.0-1_sm-t710_13317.tar) and this time I somehow goto to TWRP recovery mode, I just left it on there to see how long it would last, instead of immediately erasing the caches and restarting.
After that once, I couldn't get it to stay on long enough to access recovery. So I tried to go back to OEM ROM using Smart Switch, but to no avail once again. The Download mode still says Custom even after Smart Switch emergency recovery
I have tried flashing various other things (5.1.1 Samsung ROM, 6.0 ROM from UK with AP, BL and CSC files, TWRP 5.1.1 permissive ROM, TWRP), in various jumbled orde,r out of frustration. Nothing worked. here's a list of ROMs I've tried:
T710XXU2DQCL_T710UVS2DQC1_EON
SM-T710_1_20170406180713_vd28gnex7t_fac
SM-T710_1_20170330211239_qkurg70e9y
5.1.1_T710XXU1BOH7_T710XAR1BOH7_XAR
twrp_2.8.7.1_LL_5.1.1_t710
twrp_3.1.0-1_sm-t710_13317
t710_5.1.1_boot
Right now, the only thing I can access is Download mode and it says Current Binary: Custom, System Status: Custom, AP SWREV B:2 K:0 S:0 and worse than before, the tab turns off at the Powered by Android logo and when I plug it in, it doesn't charge but I get this boot loop (with the just the powered by android screen flashing)
would it help to re-partition and nand erase all and install a fresh ROM with a PIT file, if so can someone please share me their PIT file for this model??
I am out of ideas, and ready to break this expensive brick
appreciate any help,
thanks
V
Click to expand...
Click to collapse
Well i hve the same problem like you.. idk wht should i do with this condition.. bootloop.. always restart until logo.. :crying:
Please anyone help to solve our problem..
Your issue seems related to power. It seems your device doesn't charge correctly and is turning off due to running out of battery.
What does TWRP report as the charge state?
Do you get the same issue when the device is plugged in to the mains?
ashyx said:
Your issue seems related to power. It seems your device doesn't charge correctly and is turning off due to running out of battery.
What does TWRP report as the charge state?
Do you get the same issue when the device is plugged in to the mains?
Click to expand...
Click to collapse
hi ashyx, I am pretty sure that battery isn't the issue here. even though the grey battery logo with a thunderbolt flashes while turned off and plugged in for charging, after a while it does charge anyhow. I can get it to 100%. Plugging in makes no difference.
I am thinking it could be a power button problem or a faulty usb port perhaps, if it is indeed a hardware fault?
vvsarana said:
hi ashyx, I am pretty sure that battery isn't the issue here. even though the grey battery logo with a thunderbolt flashes while turned off and plugged in for charging, after a while it does charge anyhow. I can get it to 100%. Plugging in makes no difference.
I am thinking it could be a power button problem or a faulty usb port perhaps, if it is indeed a hardware fault?
Click to expand...
Click to collapse
Did you ever resolved this issue? Curious if you have a solution.
Hi, I've recently bought a Samsung Note 9, secondhand, yet still new condition. Courier dropped the delivery and I was impressed with what I received, unboxing through to switching it on. Awesome display, features, speed, etc.. unfortunately, it didn't last long. Went through the initial setup, google acc, personal preferences, up to the point where security features needed to be activated. As I wanted to enroll fingerprints, it asked for passkey before biometrics could be recorded. I entered a 5 digit code, again to confirm, and then it was set. Then the trouble started. Phone locked by pressing the power button then refused to unlock with the passcode that I've just saved. After a while of trying to enter the key I've used, as well as some alternative combinations for in case I've made a mistake (twice?), I've resorted to boot into recovery mode by switching off the device and pressing bixby+vol up+pwr. Booted into recovery, chose factory reset and let it run.
It finished in less than a second, before I chose to reboot device. Only to see the screen stay dark with red words top left corner of screen: Only official firmware to be installed something something. And that's what I kept on getting, did abovementioned step again, same issue, tried formatting cache, same issue, tried lacking storage boot, same issue, tried flashing custom rom via Odin, same issue, tried to find official firmware and installed that same issue. I've noticed that none of the packages I try to install works due to an error stating that Signature Verification Failed. Every time, whether I try sideloading via adb, updating via sdcard or flashing with Odin, I get the same result. Last try was flashing the bootloader with an recovery zip I found somewhere and now it just bootloops the Samsung Galaxy Note 9 startup screen, vibrates, restarts and same screen again. Even if I let it loop, it keeps on forever. I can still access bootloader, recovery and Download mode with pressing the button combinations, but nothing I try of the options available resolves the problem.
I'm really at a point where I don't know what to do or try, please advise. Here's some additional info that might help:
Samsung Galaxy Note 9 SM-N960F Crownlte.
Support SINGLE-SKU
Block-Based OTA
Supported API: 3
samsung/crownltexx/crownlte9/PPR1.180610.011/N960FXXU3CSI3
After a few of my flashing attempts, abovementioned line now reads:
Block-Based OTA
Supported API: 3
samsung/crownltexx/crownlte9/PPR1.180610.011/N960FXXU3CSF9
Its the Exynos version of the Note 9. Any direction or help will be much appreciated.
Thanx
Sdejager2 said:
Hi, I've recently bought a Samsung Note 9, secondhand, yet still new condition. Courier dropped the delivery and I was impressed with what I received, unboxing through to switching it on. Awesome display, features, speed, etc.. unfortunately, it didn't last long. Went through the initial setup, google acc, personal preferences, up to the point where security features needed to be activated. As I wanted to enroll fingerprints, it asked for passkey before biometrics could be recorded. I entered a 5 digit code, again to confirm, and then it was set. Then the trouble started. Phone locked by pressing the power button then refused to unlock with the passcode that I've just saved. After a while of trying to enter the key I've used, as well as some alternative combinations for in case I've made a mistake (twice?), I've resorted to boot into recovery mode by switching off the device and pressing bixby+vol up+pwr. Booted into recovery, chose factory reset and let it run.
It finished in less than a second, before I chose to reboot device. Only to see the screen stay dark with red words top left corner of screen: Only official firmware to be installed something something. And that's what I kept on getting, did abovementioned step again, same issue, tried formatting cache, same issue, tried lacking storage boot, same issue, tried flashing custom rom via Odin, same issue, tried to find official firmware and installed that same issue. I've noticed that none of the packages I try to install works due to an error stating that Signature Verification Failed. Every time, whether I try sideloading via adb, updating via sdcard or flashing with Odin, I get the same result. Last try was flashing the bootloader with an recovery zip I found somewhere and now it just bootloops the Samsung Galaxy Note 9 startup screen, vibrates, restarts and same screen again. Even if I let it loop, it keeps on forever. I can still access bootloader, recovery and Download mode with pressing the button combinations, but nothing I try of the options available resolves the problem.
I'm really at a point where I don't know what to do or try, please advise. Here's some additional info that might help:
Samsung Galaxy Note 9 SM-N960F Crownlte.
Support SINGLE-SKU
Block-Based OTA
Supported API: 3
samsung/crownltexx/crownlte9/PPR1.180610.011/N960FXXU3CSI3
After a few of my flashing attempts, abovementioned line now reads:
Block-Based OTA
Supported API: 3
samsung/crownltexx/crownlte9/PPR1.180610.011/N960FXXU3CSF9
Its the Exynos version of the Note 9. Any direction or help will be much appreciated.
Thanx
Click to expand...
Click to collapse
1. Install official stock rom from sammobile from this link (doesn't matter which you download):
https://www.sammobile.com/samsung/galaxy-note9/firmware/#SM-N960F
2. Load up Odin, put corresponding files to their slots, AP to AP, BL to BL, etc..
3. Boot into download mode (phone powered off, press and hol volume down + bixby button and insert cable to computer)
4. Flash it, wait for it to boot up.
Ok, I'll try that today and hopefully my next reply will be me posting from the Note. Let's hold thumbs.
Thanx
How did you solve the problem.. Same here.. Stuck at bootloop
Am unable enter in to download mode.. Tried hundreds of times
Minzlife said:
Am unable enter in to download mode.. Tried hundreds of times
Click to expand...
Click to collapse
try this
Plug your phone to pc
Hold power button + volume down for a few seconds
Then right before the phone logo shows, bixby + volume down
Now download mode shows. Flash stock rom
Hi !
Mi cellphone worked well for one month and yesterday began restarting by itself, I tought It was a problem with the button ON; but today it gets worst, the phone doesn't restart to the menu home, it just keeps turning on in "Bison" and then it turns off, and again "bison" and turns off, here a link
I can't use the recovery mode because the times i reached it the phone turns off; there's a mode to block phone's turning off? maybe using some buttons?
Please I beg you, help.
i have got the same problem with my bison also ,on one month it was work properly bt nw restart it self every 4 seconds
can you give more information? Did you unlock the bootloader? Did you install another OS? Did you use Magisk?
Or was it a stock image with locked bootloader? And failed on its own? Its possible there was an OTA update but I cant tell with the info you supplied.
Hi, I just update the software from the provider (i think is a OTA update, a normal update).... and then the problem appears, it takes a few of days to show the bootloop; i dont do anything else.
Now im triying to flashing the rom but it's SO ****ing difficult, because the phone restarts always, but not completely.
I tried to use the default recovery mode, but the phone restarts...
I was thinking about some file to block the bootloop while flashing? it that possible?
Using the flash i just do download, and to finish the process it left just 3 files: supersu, cache and userdata, but it restaaaaarts :C ... i tried the option "upgrade firmware" but formating stops at 88% XD
I was thinking about a full format, it could be worse, no?
BuckyMalone said:
can you give more information? Did you unlock the bootloader? Did you install another OS? Did you use Magisk?
Or was it a stock image with locked bootloader? And failed on its own? Its possible there was an OTA update but I cant tell with the info you supplied.
Click to expand...
Click to collapse
YES, after that loop of boot problem,it came in normal after flash by SP flash(firmware upgrage),, then problem arose again,flash secondly by SP flash(formart all and download),this time it start normal but with another problem(TEE and google unwriten key,lost of IMEIs),i decide unlock bootloader and root it by magisk (follows umidigi comunity tutorial)bt all fail,it remain loop of booting it take more than 1mins show bison last log before start and shotdown again,,,off botton respond very slow on power on.
My Bison had this same infinite boot loop problem and I found out that the problem is in the short-circuited power switch. You have to open it and disconnect the flat from the side buttons to test