Hi, My Mi A3 keeps restarting. If i stay a while without using the phone it simply restarts and expects sim code to start again. The result is that ithou knowing i'm contantly with the phone shut down. Anyone can help? Thanks
You need to provide a bit more information than that.
Have you flashed anything at all to the device (magisk, twrp, ROM, any kind of mod)
Is it completely stock?
If so it sounds like a software issue and reflashing the stock rom with mi flash tools may help
garylawwd said:
You need to provide a bit more information than that.
Have you flashed anything at all to the device (magisk, twrp, ROM, any kind of mod)
Is it completely stock?
If so it sounds like a software issue and reflashing the stock rom with mi flash tools may help
Click to expand...
Click to collapse
Hi, thanks for the prompt reply. Yes, is just stock ROM. Android 9 plus november security patch. Already did a factory reset and the problem remains. The only uncommon thig i've noticed was an android.process.acore error which i today tried to solve by seaching solutions online. Thanks
jcoelho111 said:
Hi, thanks for the prompt reply. Yes, is just stock ROM. Android 9 plus november security patch. Already did a factory reset and the problem remains. The only uncommon thig i've noticed was an android.process.acore error which i today tried to solve by seaching solutions online. Thanks
Click to expand...
Click to collapse
That's an issue with your contacts and nothing to do with random reboots which may indicate that the update to November sec patch might have caused this issue. Something may have happened when you updated and caused some files to get messed up somehow which is why a factory reset won't work.
That's why it still hasn't fixed the android.process.acore error or the random reboots
As I said in my previous post, reflash the latest rom with mi flash tools and that issue may very well get fixed.
garylawwd said:
That's an issue with your contacts and nothing to do with random reboots which may indicate that the update to November sec patch might have caused this issue. Something may have happened when you updated and caused some files to get messed up somehow which is why a factory reset won't work.
That's why it still hasn't fixed the android.process.acore error or the random reboots
As I said in my previous post, reflash the latest rom with mi flash tools and that issue may very well get fixed.
Click to expand...
Click to collapse
ok. thanks once again
wipe format cache data everything internal storage too( it will delete ALL ypur photos,videos etc.) flash stock rom or any custom rom . i hope it will be solved
jcoelho111 said:
Hi, My Mi A3 keeps restarting. If i stay a while without using the phone it simply restarts and expects sim code to start again. The result is that ithou knowing i'm contantly with the phone shut down. Anyone can help? Thanks
Click to expand...
Click to collapse
How often does it happen? You could try connecting your phone to a PC and keep running "adb logcat" to catch the crash. Also try capturing logcat right after a reboot, it might contain some useful info about the crash.
With root you could get additional info:
Kernel Log:
adb shell su -c dmesg > dmesg.log
Last_kmsg:
adb shell su -c "cat /proc/last_kmsg" > last_kmsg.log
sasukeob said:
wipe format cache data everything internal storage too( it will delete ALL ypur photos,videos etc.) flash stock rom or any custom rom . i hope it will be solved
Click to expand...
Click to collapse
thanks
_mysiak_ said:
How often does it happen? You could try connecting your phone to a PC and keep running "adb logcat" to catch the crash. Also try capturing logcat right after a reboot, it might contain some useful info about the crash.
With root you could get additional info:
Kernel Log:
adb shell su -c dmesg > dmesg.log
Last_kmsg:
adb shell su -c "cat /proc/last_kmsg" > last_kmsg.log
Click to expand...
Click to collapse
thanks
I got the same problem...How do I reflash the latest rom with mi flash tools?
any one tried with Miflash till now? please update your feed back here
---------- Post added at 12:45 PM ---------- Previous post was at 12:28 PM ----------
@garylawwd
A3 have ufs memory and all ufs have different configuration than emmc partitions need to set active partition if you will not set active partition the phone will boot looping or hang on logo and make restarts
Click to expand...
Click to collapse
do you think any problem with this file system (Mi update team is not that dumb) but simply asking
in my case it restarts with boot loops , auto formates it self if you connect charging wire (with erasing mentioned for 15seconds) and fails to restar for 3 time and bootups with welcome language selection screen!
Ended up here because my Mi A3 is becoming increasingly unstable. It rebooted three times around lunch time. I've just installed the May 2020 update and it's already restarted once already
I'm going to have to consider returning it - my mobile is my main business phone too so can't have this level of instability and hassle Sadly a very black mark against Xiaomi. I've recommended their phones to several friends and clients because they were great phones.
Hmm... whilst typing this message it's just restarted again...
Related
On 2.9 version, mm 6.01, mokee rom, boost mode, experiencing constant 'sign in to network ' notifications for both cellular and WiFi networks while the network connection is ok.
Screen is attached.
I have the same issue. It even says 'no internet connection. But all works fine. Its bothering me though.
dimdimdim said:
On 2.9 version, mm 6.01, mokee rom, boost mode, experiencing constant 'sign in to network ' notifications for both cellular and WiFi networks while the network connection is ok.
Screen is attached.
Click to expand...
Click to collapse
And even more. I disabled all the settings in greenify one by one and then disabled the exposed module, then reboot, then deleted greenify via force stop/clear data/uninstall, then cleared all the caches and... Nothing happened. The notifications are still here.
The only difference I see the Internet speed is seemingly lower. So, I've run Google fiber test and found it says 'no servers responded '.
So, there is a problem.
Taking into account I see no other answers here, I will re-flash the rom keeping my data. Hope, the changes were made to system, so it should help.
I didnt have the issue by reflashing. It just suddenly started to happen. I gonna flash my ROM to the latest and hope it gets resolved. This is a dealbreaker for me. Hope it gets solved fast.
avsmartmobiles said:
I didnt have the issue by reflashing. It just suddenly started to happen. I gonna flash my ROM to the latest and hope it gets resolved. This is a dealbreaker for me. Hope it gets solved fast.
Click to expand...
Click to collapse
No, the problem occured not after a rom reflash, but just after greenify installation. I used system reflash in hopes to fix the issue. But it doesn't help. Seems, the changes are somewhere in data and I just don't know where.
dimdimdim said:
No, the problem occured not after a rom reflash, but just after greenify installation. I used system reflash in hopes to fix the issue. But it doesn't help. Seems, the changes are somewhere in data and I just don't know where.
Click to expand...
Click to collapse
Check this url: https://www.reddit.com/r/cyanogenmod/comments/4jo86y/cm13_wifi_connected_with_no_internet_sign_but/
I dont know how to do it. Do you know what we have to do?
avsmartmobiles said:
Check this url: https://www.reddit.com/r/cyanogenmod/comments/4jo86y/cm13_wifi_connected_with_no_internet_sign_but/
I dont know how to do it. Do you know what we have to do?
Click to expand...
Click to collapse
Okay, seems there is a way to fix it, close to what you've found: http://android.stackexchange.com/qu...ction-how-to-remove-exclamation-mark-on-wi-fi
The steps:
1. You should be rooted
2. Install any terminal emulator
3. Run it
4. Enter su
5. press enter
6. Enter
settings put global captive_portal_detection_enabled 0
7. Press enter
8. Reboot
I've check it and it works for me.
I'm not sure it's the best solution, but it works for this problem at least.
Damn im a noob i cant even post an Image here. I did the Steps u Said but I get : global captive_portal_detection_enabled 0
The program 'global' is not installed. Install it by executing:
apt install global
$
Van you print Screen it for me please ?
I cant seem to fix it. I get An error in the command. See printscreen. Please Help.
avsmartmobiles said:
I cant seem to fix it. I get An error in the command. See printscreen. Please Help.
Click to expand...
Click to collapse
You must enter first command
su
After that press
enter
And then copy the whole line of the command
settings put global captive_portal_detection_enabled 0
And then press
enter
again.
On the second screen you made it correct but forget to enter
su
before
dimdimdim said:
You must enter first command
su
After that press
enter
And then copy the whole line of the command
settings put global captive_portal_detection_enabled 0
And then press
enter
again.
On the second screen you made it correct but forget to enter
su
before
Click to expand...
Click to collapse
Thanks a lot men I think its fixed.
But now, as I supposed, the sign in to networks, which really need sign in (all public hotspots), doesn't throw out the notification.
I suppose it's still possible to sign via browser, but...
Worked for me
Thanks Bro! It worked for my mokee L 5.1 Rom on xiaomi Redmi 1s
dimdimdim said:
Okay, seems there is a way to fix it, close to what you've found: http://android.stackexchange.com/qu...ction-how-to-remove-exclamation-mark-on-wi-fi
The steps:
1. You should be rooted
2. Install any terminal emulator
3. Run it
4. Enter su
5. press enter
6. Enter
settings put global captive_portal_detection_enabled 0
7. Press enter
8. Reboot
I've check it and it works for me.
I'm not sure it's the best solution, but it works for this problem at least.
Click to expand...
Click to collapse
Thanks for this! I recently received the OTA update to 7.1.1 on my Nexus 6P. After the update, it kept pestering me to sign into my company's wifi portal page. When I clicked the alert, the page would load and then the entire window would close. If I tried again, the same thing would happen. The alert would immediately return and I couldn't figure out how to get rid of it. I'm not using Greenify so I hope this solution helps others who have a similar problem.
Thanks. It worked for me.
Hi All,
I'm really not sure how to go about with this so hopefully I can get some help here. I have a Note 4 (N910T) model which was never able to do OTA update from it's 5.1.1 state. It'd download the patch and upon reboot, it'd say installation fail.
Eventually I went into the rabbit hole and used Odin to try to update the phone to 6.0.1. No luck either as it'd just get stuck on aboot. I rebooted the phone and tried to use Smartswtich from samsung and hoped that it'd update using that. Not only does it not work and stuck in the "Odin Mode (fast track)" screen, it eventually tell me that I need to go through recovery to get it back.
I didn't know what to do at that point, so I've decided to try my luck again with Odin. This time, the patch went through successfully with my surprise. However upon reboot after the patch is installed, it gave me an error "DRK not found" error. I simply reboot the phone and all seems to be working. On 6.0.1, no lagging issue, no wireless/mobile network issue, nothing.
However, I do want to know if I still have an error of DRK not found, and would like to patch that hole before any problem occurs. Can any one help? I haven't rooted the phone yet.
bump, any help would be welcomed. Thanks!! :crying:
Is it still giving that error upon every reboot or it was only on the first reboot? If you aren't having other issues and your IMEI / service / etc is fine, then nothing to worry about.
You also kept mentioning "patch". This is not common usage. What file did you flash via Odin?
Thanks for the reply!! this is what i downloaded to update the firmware using Odin:
rootmygalaxy.net/download-install-n910tuvu2epe3-marshmallow-t-mobile-note-4 (http at front)
the IMEI seems fine, and it doesn't show the error upon reboot except the first time. However the phone seems to freeze quite often now for no reason at all. Not sure how to troubleshoot that one.
es0tericcha0s said:
Is it still giving that error upon every reboot or it was only on the first reboot? If you aren't having other issues and your IMEI / service / etc is fine, then nothing to worry about.
You also kept mentioning "patch". This is not common usage. What file did you flash via Odin?
Click to expand...
Click to collapse
oc9653 said:
Thanks for the reply!! this is what i downloaded to update the firmware using Odin:
rootmygalaxy.net/download-install-n910tuvu2epe3-marshmallow-t-mobile-note-4 (http at front)
the IMEI seems fine, and it doesn't show the error upon reboot except the first time. However the phone seems to freeze quite often now for no reason at all. Not sure how to troubleshoot that one.
Click to expand...
Click to collapse
Did you install the 1st link there from the Download button or the 2nd one for the n910t3 file located @ androidfile?
I actually used another firmware today and so far it seems to not lag AS much.. but still freezes with no apparent reason:
http://forum.xda-developers.com/note-4-tmobile/development/roms-10-29-2014-t2922618
The one that I downloaded was N910TUVS2EPG2_N910TTMB2EPG2_TMB = v6.0.1 = Build date Thu, 07 Jul 2016 13:33:23 +0000 = NEWEST UPLOADED FIRMWARE
The reason I flash again is because I tried to root my device using CF_auto root, which upon reboot, caused an error of "Kernel is not Seandroid enforcing" on boot menu.
Oh and the DRK error comes back everytime after i flash the firmware, but it only appears once, and no more on subsequent reboots. My IMEI looks fine but my S/N upon typing *#60# is (none)
bump .. phone is rebooting more and more, and it's freezing more often now... help please!!
[email protected],
just bought myself an Ulefone T1 from aliexpress and I am wondering if there is any lineageos development out there for this phone? Is anybody planning to develop for this?
cheers
JohnnyT
Stay tunned. The phone is new and development will yet. Dont worry is a great phone and Ulefone is better than yesterday.
https://www.needrom.com/category/ulefone/t1-ulefone/
It will hardly receive official updates, let alone custom ROMs (same fate as the 96% of MediaTek devices out there).
any update . i just bought this phone from banggood. my asus zenfone 3 wifi is failing. so needed something to fill the gap
Finally received my t1 after 11 weeks of waiting!!
Everything works fine apart from the battery usage which is a round 10% per hour on standby with no usage!!
FOLLOW-UP
Following lots of research found that Whatsapp was still trying to verify the phone thru SMS and was draining the battery. Uninstalled and re-installed Whatsapp and verified by manually entering SMS pin.
Now appears to running okay at just over 2% per hour battery drain with bluetooth and GPS set on.
i think i got a thud. reboots when connected to 5g wifi and sometimes when doing stuff on the phone. what a POS phone. never again ulefone!
I am very happy with my T1. High performance, loads of RAM and storage in a decent looking dual SIM package for a very reasonable price tag. First official OTA update yesterday. Also there are rumors about 8.0 upgrade till end of the year.
JohnnyT
Alicklee said:
i think i got a thud. reboots when connected to 5g wifi and sometimes when doing stuff on the phone. what a POS phone. never again ulefone!
Click to expand...
Click to collapse
Mine does occasional reboot. I think its when my mail app is in 'recent apps'. When I clear recent apps. The phone seems more stable, but it's early days.
If anyone finds a fix, please post to the group.
I had my first ota update so that was a plus although it didn't solve the rebooting or activate the 'so called' second camera.
Pickles871 said:
Mine does occasional reboot. I think its when my mail app is in 'recent apps'. When I clear recent apps. The phone seems more stable, but it's early days.
If anyone finds a fix, please post to the group.
I had my first ota update so that was a plus although it didn't solve the rebooting or activate the 'so called' second camera.
Click to expand...
Click to collapse
Do you have yours rooted and your bootloader unlocked? I am getting the update prompt but being unlocked and rooted I'm not sure it will take the update. Some phones tend to brick. Also all of a sudden I am having an issue with "android process.media has stopped" Can't figure out what's causing it but since it started the device has become quite laggy
Mine is not rooted. Its still as out of the box. I have rooted previous phones but find that some of the apps I want to use won't run on rooted phones, like certain banking apps. I don't know if the restarts are an Android 7.0 symptom or hardware/software based. There are so many different views on this it's almost impossible to figure out the causes. For me I keep trying different app and phone settings in the hope that something eventually solves the issue. Maybe a future firmware update will sort it. I live in hope (but don't hold your breath). More likely a new phone will be acquired at some point!
by any chance any of you have gps problems in waze or maps????
Pickles871 said:
Mine is not rooted. Its still as out of the box. I have rooted previous phones but find that some of the apps I want to use won't run on rooted phones, like certain banking apps. I don't know if the restarts are an Android 7.0 symptom or hardware/software based. There are so many different views on this it's almost impossible to figure out the causes. For me I keep trying different app and phone settings in the hope that something eventually solves the issue. Maybe a future firmware update will sort it. I live in hope (but don't hold your breath). More likely a new phone will be acquired at some point!
Click to expand...
Click to collapse
you need to proper root with magisk. and only use magisk, not other super user apps.
with magisk hide you can cheat banking apps or any app thinking the phone is not rooted.
nieXas said:
you need to proper root with magisk. and only use magisk, not other super user apps.
with magisk hide you can cheat banking apps or any app thinking the phone is not rooted.
Click to expand...
Click to collapse
Thats useful to know. Many thanks
Made Lineage 14.1 work on my Ulefone T1 (adb shell hacked)
Hi everyone,
i've been digging around for the last few weeks on my T1 and now i've finally made it boot. I dont know exactly what is working and what not but i can tell WLAN is NOT working for now! The kernel repo at my github was not working so i used the stock one. You may download it as well as the TWRP recovery i made alongside the ROM. But you need to wipe /data partition so all user data is lost in the process. Also while TWRP needs a reboot after wiping /data step 2 & 3 may need to be repeated once. For now i was not able to flash and boot the recovery (working on it) but it can be booted into as follows (when booted into the stock system):
UPDATE: Made it work - it's booting without hacking via ADB-Shell. The parts marked --- obsolete --- are not needed any more.
1.) Disable OEM-Lock in Developer-Options (google if necessary how to do that)
2.) Reboot and keep the upper volume button button pressed until it booted into recovery. If the "no command" screen is displayed, press the power and upper volume button together once again and you shuld reside in the stock recovery. Use it to reboot into fastboot (bootloader).
3.) In fastboot mode, while beeing in the same folder as the downloaded files, type the following:
Code:
fastboot boot recovery.img
4.) Wait for TWRP to boot up and enter the following (within the same folder):
Code:
adb push lineage-14.1-*-UNOFFICIAL-t1.zip /sdcard/
5.) Finally you may flash the Lineage zip file in TWRP (if you have wiped your /data partition at least i needed to)
----------------------------------- obsolete -----------------------------------
6.) Let it reboot into system and while displaying the Linage bootanimation (for now) i had to execute a few commands on adb shell. So, with adb installed, you need to enter the following commands in a common linux/windows shell:
adb shell /vendor/bin/nvram_daemon &
adb shell /system/bin/nvram_proximity &
adb shell /vendor/bin/nvram_agent_binder &
adb shell /system/bin/agoldnvram &
adb shell /system/bin/audioserver &
Click to expand...
Click to collapse
I'm not sure if they are all needed but afterwards my T1 bootet up correcty (more or less). Unfortunately a few drivers are missing as it seems while WLAN is not working for now.
http://d0ndroid.janeiskla.de/lineage-14.1-20180928-UNOFFICIAL-t1.zip
and the recovery
http://d0ndroid.janeiskla.de/recovery.img.
----------------------------------- obsolete -----------------------------------
After fixing another few things the only remaining things i found not working are fingerprint & RIL but I'm looking into that right now. The current builds will always be uploaded to:
http://d0ndroid.janeiskla.de/
The sources i used besides the default Lineage ones are on github:
https://github.com/d0n?tab=repositories
Have fun! And let me know if you make progress on your own
Greez,
d0n
Hi d0n22, are you still working with this rom?
Hi!
I'm running stock Android Pie and I installed Swift Installer overlays to get a dark theme. Yesterday I tapped on the system update just before remembering to disable overlays before doing so... and no way to cancel the update before it actually installed it
Now my phone won't start properly: I get the Samsung logo, then I enter my pattern do decrypt the phone, then it loads and when finished loading it restarts immediately. The second time, instead or restarting immediately it will display the wallpaper for a few seconds, then black screen for a few seconds, and then the Samsung logo disappearing as it shuts the system down. And then it boots me into a special recovery mode with 4 options:
Try again
Erase App data
Power off
View Rescue log
Viewing the rescue log shows me it really is a system UI issue that's very likely because of the Swift Installer overlay: Attempt to invoke virtual method 'int com.android.systemui.statusbar.notification.FakeShadowViw.getVisibility()' on a null object reference
Trying again does the same as before, "Erase App data" doesn't help either, and "Power off" actually reboots to the regular recovery mode, with different options:
Reboot system now (same result)
Apply update from ADB
Apply update from SD card
wipe data/factory reset
wipe cache partition
Mount /system
view recovery logs
run graphics test
run locale test
Power off
Lacking storage booting
From the document from the Play Store page of Swift Installer, you can download a rescue script (rescue_Pie.zip). I tried sideloading that file using adb (option 2), and from an SD card (option 3)
and both yield the same result:
Code:
E:footer is wrong
Update package verification took 0.2s (result 1).
E:signature verification failed
E:error:21
Installation aborted
I tried wiping the cache partition and that didn't help, I tried booting with Safe Mode and that didn't help, the only obvious option left that I can see is to do a factory reset, but there are photos from my last trip I would hate to lose and since my phone is encrypted, doing a factory reset would lose the encryption key and I wouldn't be able to recover them.
Would there be any way to
Get the rescue script to run properly, or
Get access to a shell to run the bash commands from the script myself (it's really simple), or
Erase everything BUT my user data, or
Get my photos out of my phone from recovery mode, or
Stop the phone from rebooting long enough for me to try and get my photos out to my computer
It seems really dumb that there is no way to restart with all non-stock apps disabled or to reset the system without losing photos and such...
Thanks for your time and any help!
Try flashing the latest CSAB build with CSC_Home using ODIN. That should essentially replace Android and retain your data. Hopefully that will override the overlay with stock OneUI. If you can't, you can at least flash back to BRK2, CSC_Home, disable overlays, then push forward to CSAB through OTA.?
---------- Post added at 01:44 AM ---------- Previous post was at 01:40 AM ----------
The latter would probably be your best bet in keeping your files.
Thanks for the quick reply!
I downloaded Odin, your answers are a bit cryptic to me, I started downloading the latest firmware (which has the same version id as shown in recovery mode before you edited your message.
I assume BRK2 is the previous version, and would match the overlays I installed so I can boot properly. ls there a guide to stock version names
loomie209 said:
Thanks for the quick reply!
I downloaded Odin, your answers are a bit cryptic to me, I started downloading the latest firmware (which has the same version id as shown in recovery mode before you edited your message.
I assume BRK2 is the previous version, and would match the overlays I installed so I can boot properly. ls there a guide to stock version names
Click to expand...
Click to collapse
I'm assuming you're currently running CSAB on a G965U. You'll need the BRK2 firmware package (doesn't matter what carrier). Flash that using ODIN and for CSC you will use CSC_Home to retain your data. That would essentially put you back to preupdate. You'd then disable the overlay and allow it to update to CSAB on its own, however I think Samsung blocked overlays in Pie all together so you may not be able to use them again.
---------- Post added at 02:29 AM ---------- Previous post was at 02:21 AM ----------
There is no "guide" per say... If you're on a carrier branded US G965U device, you'll want to downgrade from pie (CSAB) to BRK2 (Oreo) and flash the CSC_Home file (NOT CSC_OMC that will wipe).
If you're on the Exynos or international unlocked, I can't help you because those firmware builds are out of my scope.
Thanks a lot for your help!
I flashed G965FXXU2BRK2 on my phone using Odin, and it got stuck in a loop of loading and "Optimizing app X of 72" Over and over again without rebooting. I tried to wipe the cache data and reboot but still the same.
So I flashed G96FXXU2CSA2 (which was the version I had already apparently) and now I seem to be back to my starting point: same behaviour, same error in the log...
My phone is a G965F.
I am having this exact same issue all my Galaxy note 10 plus using synergy and substratum lite. I have been steaming my phone using these same methods since the note 10 plus was released and all of a sudden today I start getting issues to wear my phone automatically boots into a boot loop. I have reset my phone twice now and then I theme it and it works fine but then I went to switch themes and all of a sudden phone shut off in into bootloop. Did you ever get any explanation?
I'm having a strange issue after flashing latest firmware on my Tab S7 (SM-T870)...
When I try to flash an update with odin I'm using "HOME_CSC" as I want to keep the data on the device. However it results in a boot loop to recovery where I have 3 options
1. Restart the phone
2. Factory reset
3. Check logs
Restarting the phone just restarts it and boots to the same menu.
I've checked the logs and saw an error saying:
Unable to set property "ro.boottime.init.mount.cache"
I've tried wiping cache in recovery as well, but that didn't help.
Anyone here who can help me out?
Thanks!
Lif3mau5 said:
I'm having a strange issue after flashing latest firmware on my Tab S7 (SM-T870)...
When I try to flash an update with odin I'm using "HOME_CSC" as I want to keep the data on the device. However it results in a boot loop to recovery where I have 3 options
1. Restart the phone
2. Factory reset
3. Check logs
Restarting the phone just restarts it and boots to the same menu.
I've checked the logs and saw an error saying:
Unable to set property "ro.boottime.init.mount.cache"
I've tried wiping cache in recovery as well, but that didn't help.
Anyone here who can help me out?
Thanks!
Click to expand...
Click to collapse
Maybe try to reflash previous firmware version.
There is no need to run after the lastest update.
Vntnox said:
Maybe try to reflash previous firmware version.
There is no need to run after the lastest update.
Click to expand...
Click to collapse
No I tried it but only factory reset does help -.-
This is why I hate Samsung for Security reasons after a f***ing Update ...
I have the same problem, but i didn't update from Odin.
Just OTA september update, and the phone randomly goes in bootloop like once in a week.
Same here. Does anyone have any news?
same here. im in a bootloop and not even factory reset helps. i can access recovery and download mode and have flashed newest firmware three times via Odin with "pass," wiped cache, name it i've done it. I'm despondent. Does
Samsung not have the equivalent of Oneplus's MSM tool? four days have i worked furiously to save my phone.
sorry to revive, but I'm having this issue as well on my z fold 4.
Factory reset helped for about a week, and back to bootloops every 3 min or so.
PASS received in Odin, had to use micro usb cable with C-adapter as c->c did not allow Odin to complete flash (stuck at ~95% on "Super").
Not sure which error in the logs apply, but the "unable to set property "ro.boottime.init.mount.cache" to "0": error code: 0xb, try count 1-3" seem to be cause for alarm.
Has anyone fixed this?