Related
Hi all
My Note 4 screen has started locking up (i.e. continuing to work in the background and the screen is still responding to system events (SMS notifications etc) but it is not responding to touch.
I have tried several factory resets, after which the screen stays responsive for about 3 or 4 pages, then locks up again.
Background: the phone was rooted about a year ago, to get around the SD card restriction, and has worked fine up until the last week. I gave the phone to a friend who put CWM-based recovery manager and the latest Samsung Android 5.1.1 on it. After setting the phone up successfully and downloading all my apps on to it and getting everything running perfectly, I used CWM to back up the OS image onto the SD card.
Phone worked great for about a day, then started freezing. Wiping the caches / restoring / factory resets and all permutations of these have so far proved ineffective...
Any pointers or suggestions gratefully received :fingers-crossed:
Vaughan
v00n said:
Hi all
My Note 4 screen has started locking up (i.e. continuing to work in the background and the screen is still responding to system events (SMS notifications etc) but it is not responding to touch.
I have tried several factory resets, after which the screen stays responsive for about 3 or 4 pages, then locks up again.
Background: the phone was rooted about a year ago, to get around the SD card restriction, and has worked fine up until the last week. I gave the phone to a friend who put CWM-based recovery manager and the latest Samsung Android 5.1.1 on it. After setting the phone up successfully and downloading all my apps on to it and getting everything running perfectly, I used CWM to back up the OS image onto the SD card.
Phone worked great for about a day, then started freezing. Wiping the caches / restoring / factory resets and all permutations of these have so far proved ineffective...
Any pointers or suggestions gratefully received :fingers-crossed:
Vaughan
Click to expand...
Click to collapse
You do have a Developer Device , right?
Sent from my SM-N910V using Tapatalk
jpcalhoun said:
You do have a Developer Device , right?
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
Not sure what you mean.. I am not a developer yet, just an interested amateur.
I took the phone in to a repair shop last night, the guy reckoned the problem was down to a poor screen replacement, and they hadn't used the correct bonding cement, and that the screen had separated from the LCD such that capacitance couldn't do its thing.
However if this were the case, the screen would not work at all, even briefly after a system reset.
v00n said:
I took the phone in to a repair shop last night, the guy reckoned the problem was down to a poor screen replacement, and they hadn't used the correct bonding cement, and that the screen had separated from the LCD such that capacitance couldn't do its thing..
Click to expand...
Click to collapse
I should add that the repairer is simply dismantling and rebuilding the phone to see if it's a loose/dirty connector somewhere. He's not going to try to fix it with firmware/software.
v00n said:
I should add that the repairer is simply dismantling and rebuilding the phone to see if it's a loose/dirty connector somewhere. He's not going to try to fix it with firmware/software.
Click to expand...
Click to collapse
The retail version of the Note 4 cannot be rooted, only the Developer Edition of the Note 4 can be rooted and only the Developer Edition has an unlocked bootloader which will allow the installation of a custom recovery like twrp and root. There are a couple of ways to tell if you have a developer device but the fastest is to remove the battery and see if the words "Developer Device" is printed on the phone's casing. If you don't see "Developer Device" printed then you don't have a developer device so you cannot root the phone, you cannot install twrp or other custom recovery and you cannot install a custom ROM.
jpcalhoun said:
The retail version of the Note 4 cannot be rooted, only the Developer Edition of the Note 4 can be rooted and only the Developer Edition has an unlocked bootloader which will allow the installation of a custom recovery like twrp and root. There are a couple of ways to tell if you have a developer device but the fastest is to remove the battery and see if the words "Developer Device" is printed on the phone's casing. If you don't see "Developer Device" printed then you don't have a developer device so you cannot root the phone, you cannot install twrp or other custom recovery and you cannot install a custom ROM.
Click to expand...
Click to collapse
I posted this question in the wrong forum. I am in the UK, I bought the phone directly from Samsung UK the day it came out. It is not a Verizon phone. If I could find a way to delete or lock off this thread I would.
I have now re-posted the question in the main Note 4 forum.
Hi everybody,
i have a new Mi A2 Lite. I purchased it from a private person, not a shop, but it was still in foil and opened by me. It works nicely, is fast, the phone feels fine, i like it. It has AndroidONE, Oreo, on it. If i search for updates, it tells me that it is up to date and there are no updates. The same for the security patches - they are from nov. 2018, which is nearly a year ago, but there are no updates either.
I wanted to install android 9, so i did lots of tricks and things like using a VPN to poland and resetting the phone and so on, but to no avail - there are no updates.
so...
(1) is there something that can be done wrong? why wouldnt the phone find updates?
(2) is there a way to flash the official OTA zip without unlocking? I do not want a special kernel or rom, i dont want to modyfy anything on the os, i just want the official, latest os on the phone
(3) Any other ideas?
Thanks in advance
damaltor said:
It has AndroidONE, Oreo, on it. If i search for updates, it tells me that it is up to date and there are no updates.
Click to expand...
Click to collapse
Hi!
Could you please share a screenshot showing your actual Android build number and kernel version? You might have a fake A2 lite (Redmi 6 Pro).
Edit: Don't flash anything before you're sure that your device is a geniue A2 lite, otherwise you will brick your device.
yep, i heard about that. unfortunately, i did flash it by now, but the flash worked perfectly. i unlocked the bootloader with fastboot, flashed the last fastboot package, and re-locked the bootloader. the device is now on android pie and it still works nicely. is there any way to find out if it is genuine after flashing?
So, now i can say the following:
- the deveice works still well with the flashed software.
- the device did just find and download the google security patches of sep 2019
- the imei of the device passes the xiaomi authentication test
so, i am somewhat sure that the device is an original.
still, i am interested why the device was stuck on the old version. maybe it could only handle incremental updates and the old incremental update was not available anymore?
Hi!
I have simmiliar issue. New, 100% original Mi A2 Lite. It downloaded 1GB update 8.0 to 8.1 (?), but no update for Android 9, and now it is stuck.
My screens:
ibb.co/SKjNJ6D
ibb.co/YR4793D
Regards!
Facing The same in my Mi A1
The same thing is happening with my Mi A1, I have Android 8.1 an I hadn't update to Android 9. Every day the notification for Android 9 would appear in my phone, saying that is available.
Today that update didn't show and when I checked for updates, it said I was already up to date.
Sorry for my English, I barely know it
Well i could probably Help you to flash your device but you should be sure that the device is not a fake, too. I cannot help you with that though. I will look in here tomorrow and give you a few hints to the flashing process.
So, the screenshots of the A2 Lite look pretty mich exactly like mine did. for me the only way was to reflash the device. if you are interested, i can tell you how, but there is a risk of bricking your device if it is a fake a2 lite. i cannot tell by your screenshots, maybe @thorin0815 can?
Otherwise, do you want to try it and risk ist?
edit: you can put in your imei here to check your phone, though i would not entirely trust it.
https://www.mi.com/global/shield#imei_en
*Deleted* *replay *
chriss7777 said:
Hi!
I have simmiliar issue. New, 100% original Mi A2 Lite. It downloaded 1GB update 8.0 to 8.1 (?), but no update for Android 9, and now it is stuck.
Click to expand...
Click to collapse
You're right, your device looks like a geniue A2 lite. We never had an update from 8.0 to 8.1, it was shipped with 8.1.
Maybe Xiaomi pulled the incremental (8.1->9.0) OTA updates from their servers.
The "safest" way to update would be to flash the latest available full firmware via Miflash tool.
well, thats what i did. fortunately there is no longer the need to wait for hours or days to unlock the bootloader, it works in an instant now even without registration.
thorin0815 said:
You're right, your device looks like a geniue A2 lite. We never had an update from 8.0 to 8.1, it was shipped with 8.1.
Maybe Xiaomi pulled the incremental (8.1->9.0) OTA updates from their servers.
The "safest" way to update would be to flash the latest available full firmware via Miflash tool.
Click to expand...
Click to collapse
I did not notice what update it was downloading. I unboxed it, then I connect to WiFi and it started downloading. Anyway it downloaded aprox. 1GB of data, then restart and update. And now it is stuck with 8.1. I thought it will be Android 9 after update with latest patches.
I validate IMEI's on site and it is valid, also it has all google logos, and so on.
Is there any comprehensive update manual for MiFlash for this model?
Well, Not that I know of one that is really complete and up to date. But here you are (own phone, own risk!). Back up your phone first!
Switch on your phone.
Go to settings, about phone.
Tap the build number multiple times until "you are a developer".
Open the developer options.
Switch on USB debugging.
Switch on "allow unlocking bootloader".
Leave settings.
Download this, and install it, answering yes to all three questions:
https://forum.xda-developers.com/showthread.php?t=2588979
Connect the phone and when asked, accept the adb debug question on your phone. Your computer is now allowed to debug your phone.
Also download your new os from here:
https://xiaomifirmwareupdater.com/miui/ (put your phone model in there and download the latest fastboot image)
Unpack it. Depending on your packing program you might have to unpack twice - you should have a few folders and files.
Download the mi flash tool here:
https://www.xiaomiflash.com/
Now you are ready. Take a deep breath. Make sure your phone is charged, 50% should be enough.
Disconnect and Switch off the phone. Hold volume down and power until a rabbit working on an Android robot is seen on the screen. Now reconnect the cable.
Open a command window on the computer by pressing windows+R and entering "cmd".
In that window, type "fastboot oem unlock" and press enter. You should get the answer "OKAY".
If your phone reboots now, hold volume down and power again until the rabbit is there again.
Start miflash. Show miflash the folder in which you unpacked the os files.
In the lower right select "clean and lock" and then press update, select your phone, and press flash.
Flashing now takes roundabout 5 minutes.
Afterwards your phone should reboot into Android 9. Your data will be gone (though my phone managed to keep a few of it's settings for some reason).
Good luck!
damaltor said:
Well, Not that I know of one that is really complete and up to date. But here you are (own phone, own risk!). Back up your phone first!
Afterwards your phone should reboot into Android 9. Your data will be gone (though my phone managed to keep a few of it's settings for some reason).
Good luck!
Click to expand...
Click to collapse
It works like a charm. Also now it is updating with new security patch. Thanks damaltor!
No problem, good to hear that it worked!
Hi,
I have applied firware update for years without problems but today I am stumped.
I tried to update todate from 6ETLL firmware to the newer 6FUBD both Android 11.
Set up Odin using 3.14.4 and started ok.
Then I had the install stopping and disconnecing to the phone.
Eventually I disconnected the phone lead and it now wont boot passed the error message -
An error has occurred while updating the device software.
Use the Emmergency recovery function in the Smart Switch PC software.
So I installed this on my pc it it fails to recognise the phone even in Emmergency recovery mode.
I have tried all methods of trying to reboot the phone but it always comes back to the above arror message and wont go into recover mode or download mode.
I did not but this from O2 but directly from Samsund and its just out of warrantee.
I dont know wheer the service center is in the Uk and thats a lst resort anyway.
Any suggestions please.
Repaste from my other reply on the UI3 update :
"
Odin hates thunderbolt - If you plan on using a USB-C port make sure it's not thunderbolt. It will fail half way in and freeze. Get a well rated cable and do it via USB concentrator directly
If you get stuck and you cannot access recovery via key combo or smartswitch emergency recovery use Odin
Open options and select get device info - It will reboot directly to the recovery if it was previously written (check the log). After that disable the get device info option and reconnect the cable (select files for flashing again - should go smoothly.
If after the reboot and setup you get a moisture warning on the USB port - this does not make nay sense but it works - Turn off the Note, plug in a usb cable on the PC and reboot the phone connected to the cable - It will reset the sensor warning and should work flawlessly.
Hope to have helped - Had a bit of a jarring adventure setting this one up this time.
The lag in the animation is there, however, I think it's the animation timer that is set higher (slower) it's not slow "per se" but it shows. "
Bomm,
I must say.... I dont know how to thank you. Your post saved my Note 10.
I emailed Samsung repair and after 2 days they said phone xxxxx if you need it repaired under warrantee.
I waited a week for the phone to lose its battery and when booted back on charge cane up with the same error.
So I went back on xda and you had kindly posted the exact fix I needed. I didn't expect that. I know now if I have the same issue again. It was my pc I think using usb-c to usb-c like you said. Thank you so much.
I didn't get any warnings at all. booted up fine.
Johny1fin said:
I didn't get any warnings at all. booted up fine.
Click to expand...
Click to collapse
had the same issue. I was stumped at first too
I've tried all the posts but when I say start in odin, the phone restarts and gives an error
As you say you are super, my friend, I applied it step by step, the phone entered the download mode.
Not sure why you want Q or above on the 10+.
I'm still running on Pie/One UI. Fast, very stable and zero issues. Last reload was back in June.
If the OS is running well and fulfilling its mission let sleeping dogs lie.
One issue is if we don't keep up to date then at some point Samsung will stop support on a particular phone and the phone can be years out if date.
They may then be on a version unsupported by the apps suppliers and will be more difficult to sell if you want to buy a new phone.
Johny1fin said:
One issue is if we don't keep up to date then at some point Samsung will stop support on a particular phone and the phone can be years out if date.
They may then be on a version unsupported by the apps suppliers and will be more difficult to sell if you want to buy a new phone.
Click to expand...
Click to collapse
No problem here. All my PCs, their XPx64/W7 OSs as well as my Androids Kitkat/Pie OSs are now unsupported.
No issues and all continue to fulfill their missions.
Forced learning curves waste my time and offer little in return. My last learning curves were from Kitkat to Pie and XPx64 to W7.
I stopped updating with the best versions of both MS and Android. I don't rat's arse if it stays like that for the next 10 years... or if my Windows machines mutate into Pie or Linux machines
Whatever works best for me.
It's not just the bugs that won't get fixed it's the vulnerabilities as well, then the apps stop working. I actually enjoy upgrading my kit and amon Windows 10 21h1. Anti virus packages mat stop working as well.
Johny1fin said:
It's not just the bugs that won't get fixed it's the vulnerabilities as well, then the apps stop working. I actually enjoy upgrading my kit and amon Windows 10 21h1. Anti virus packages mat stop working as well.
Click to expand...
Click to collapse
I've never had a malware or virus issue that required a factory reset in over 7 years of using Android. More than half of the time was using out of date OS's. My current Pie OS is over a year out of date.
99% of rootkits, viruses etc are uploaded by the user. There's no protecting the stupid.
I have redundant complete backups so a factory reset will cost me normally 2 hours and at worst case 6-8 hours if I need to restore the SD card.
You waste far more time then this fighting with the bugs, the learning curve and the forced factory reset that a major firmware update requires.
I get to use the OS of my choice... you get whatever they throw at you and the ride that comes with it.
Hi guys!
Here's a little trick, if someone might not get the Android 12 OTA update: the update is already on the official website, but for some reason the interface wasn't edited, or I don't know... So, if you rewrite the version number in the download link, the download will start. XD
EU: https://rom.download.nubia.com/Europe/NX669J/V510/NX669J-update.zip
North America & Asia: https://rom.download.nubia.com/Europe&Asia/NX669J/V610/NX669J-update.zip
I completely reset the phone before that, with Mitool, in EDL mode. Everything works, 5Ghz Wifi, Volte, etc., so far I have not experienced any errors. The interface looks smoother, but that might just be because of the clean phone. I like the new Gamespace much better. If you don't like it or if you find errors, you can use the Mitool-EDL method to revert to any previous version.
The update was pulled from OTA due to bugs - some users experienced boot loops that required full reset (you did that anyhow).
In my case, I've had cellular network issues where it appears the device disconnects from the network when on WiFi - phone calls are no longer received and legacy SMS/MMS won't send/receive until WiFi is disabled or the SIM is toggled off/on.
An update is apparently on its way, but it's been over 3 weeks now.
Says "everyone" but then leaves out RM6R
Gunhawk32 said:
Says "everyone" but then leaves out RM6R
Click to expand...
Click to collapse
Sorry, by everyone I meant not only those who are sent OTA. Android 12 has already been released for the 6R in China, so I think it will arrive soon for the 6R as well. :/
An Droid said:
The update was pulled from OTA due to bugs - some users experienced boot loops that required full reset (you did that anyhow).
In my case, I've had cellular network issues where it appears the device disconnects from the network when on WiFi - phone calls are no longer received and legacy SMS/MMS won't send/receive until WiFi is disabled or the SIM is toggled off/on.
An update is apparently on its way, but it's been over 3 weeks now.
Click to expand...
Click to collapse
I did a completely clean update. I completely formatted it, deleted all partitions /even the "persist" by accident, but I managed to restore it, but that's another story/.
Then I reset the phone using the Mitool-EDL method and then updated the clean system to EUCommon-V5.10.
The only mistake is that it lists the battery as 3550 mah instead of 5050 mah.
What you write about not receiving calls on Wi-Fi, etc., also occurred to me on the V3.28 system. If I set the mobile network as preferred in the vowifi settings, the error disappeared. Now I haven't experienced this error, vowifi works normally even in wifi preferred mode.
So far, I have not experienced any errors apart from the incorrect listing of the battery, although I cannot test 5G because it is not yet installed at our place...:/
Pisti870923 said:
Sorry, by everyone I meant not only those who are sent OTA. Android 12 has already been released for the 6R in China, so I think it will arrive soon for the 6R as well. :/
Click to expand...
Click to collapse
I doubt it since it took 7-9 months for the android 12 update to release globally for the RM6 & 6 pro after it came out in china.
An Droid said:
The update was pulled from OTA due to bugs - some users experienced boot loops that required full reset (you did that anyhow).
In my case, I've had cellular network issues where it appears the device disconnects from the network when on WiFi - phone calls are no longer received and legacy SMS/MMS won't send/receive until WiFi is disabled or the SIM is toggled off/on.
An update is apparently on its way, but it's been over 3 weeks now.
Click to expand...
Click to collapse
bro i have the same issue
do you solve it
Please i
Pisti870923 said:
Hi guys!
Here's a little trick, if someone might not get the Android 12 OTA update: the update is already on the official website, but for some reason the interface wasn't edited, or I don't know... So, if you rewrite the version number in the download link, the download will start. XD
EU: https://rom.download.nubia.com/Europe/NX669J/V510/NX669J-update.zip
North America & Asia: https://rom.download.nubia.com/Europe&Asia/NX669J/V610/NX669J-update.zip
I completely reset the phone before that, with Mitool, in EDL mode. Everything works, 5Ghz Wifi, Volte, etc., so far I have not experienced any errors. The interface looks smoother, but that might just be because of the clean phone. I like the new Gamespace much better. If you don't like it or if you find errors, you can use the Mitool-EDL method to revert to any previous version.
Click to expand...
Click to collapse
do you have instructions or video .i dont have experience with that
moatazamer83 said:
do you have instructions or video .i dont have experience with that
Click to expand...
Click to collapse
I'll describe how I did it, but I can't promise that everything will work the same way for everyone. I don't know if there are hardware differences between each phone because I could only test it with mine /RM6P/. If someone tries it, do it at your own risk!
Be sure to save the "persist" partition before doing anything!!! Also save Qcn, these two are very important!!!
1. Backup partitions:
2. Backup Qcn:
3. /Optional/ Erase ALL:
After backup, I entered the partition manager in qfil, and after right-clicking, I clicked on "erase entire flash". But it's not absolutely necessary, but I definitely wanted a clean install. When I returned from Chinese Android 12 to EU 11 and didn't do this, the first time I started it, the phone setup got stuck in the wizard and wouldn't let me continue. From this I realized that the Mitool-EDL method alone does not completely clean the phone.
If you have completely reformatted the phone with qfil, you will need to restore the "persist" partition and Qcn with qfil after Mitool is finished. If you haven't formatted it completely, you don't need to restore it, but you should still have a backup of them, you never know when you'll need them, believe me!
4. And here is the description of the much talked about Mitool-EDL method:
RM6/6Pro Unbrick Tool - EDL Flash / Switch from CN to EU
Hello guys, I received the following unbrick tool from my supplier in Shenzhen - China and wanted to share it with you since I noticed that many people are desperate to fix their RM6 and swap it to EU. The process is super easy: 1) Download &...
forum.xda-developers.com
5. Update rom:
If you're done with Mitool, you download the ROM you want, copy it to the internal storage and install it with local update in system update!
I did it this way and still found no errors. (Except that it says the battery is 3550mah). I use the EU510.
After Mitool finished, any rom goes up with local update, I tried EU328, UN428, CN810, UN610 and EU510
This method did not require unlocking the bootloader.
According to my theory, I could root with qfil without opening the bootloader, but I haven't tested it yet. If I try it sometime, I will write about my experience.
Two more things:
1: The Firehose file is in the "image" folder of the Mitool pack, it is also needed for Qfil.
2: If someone wants to enter EDL mode from Fastboot after updating to Android 12, the phone will restart immediately. You have to make an Edl cable from a USB data cable, or buy one and use it to enter Edl mode.
It actually seems complicated, but the point is that the black/GND/ and green/data+/ wires have to be touched together while plugging the cable into the phone, and then after a few seconds they have to be separated from each other. The switched-off phone will thus immediately switch to Edl mode.
Pisti870923 said:
Two more things:
1: The Firehose file is in the "image" folder of the Mitool pack, it is also needed for Qfil.
2: If someone wants to enter EDL mode from Fastboot after updating to Android 12, the phone will restart immediately. You have to make an Edl cable from a USB data cable, or buy one and use it to enter Edl mode.
It actually seems complicated, but the point is that the black/GND/ and green/data+/ wires have to be touched together while plugging the cable into the phone, and then after a few seconds they have to be separated from each other. The switched-off phone will thus immediately switch to Edl mode.
Click to expand...
Click to collapse
oh my god i can't do it bro
but thx alot for your help should i wait fix from company
moatazamer83 said:
bro i have the same issue
do you solve it
Please i
Click to expand...
Click to collapse
Bro me to i don't have network for calling before it wasn't a probleem but android 12 is smooth tho sad Nubia has to present it like this
An Droid said:
The update was pulled from OTA due to bugs - some users experienced boot loops that required full reset (you did that anyhow).
In my case, I've had cellular network issues where it appears the device disconnects from the network when on WiFi - phone calls are no longer received and legacy SMS/MMS won't send/receive until WiFi is disabled or the SIM is toggled off/on.
An update is apparently on its way, but it's been over 3 weeks now.
Click to expand...
Click to collapse
Bro i got same network problem it's really sad Nubia has to present android 12 like this tho do you know something more
There's a new update on the Nubia download site for the RM6 - this is Android 12:
USE AT YOUR OWN RISK!!!
North America - v.6.12
https://rom.download.nubia.com/Europe%26Asia/NX669J/V612/NX669J-update.zip
Europe - v.5.12:
https://rom.download.nubia.com/Europe/NX669J/V512/NX669J-update.zip
I've installed v.6.12 on my NA RM6 and all is well so far. Cellular issues seem better if not resolved - need more time to confirm.
An Droid said:
There's a new update on the Nubia download site for the RM6 - this is Android 12:
USE AT YOUR OWN RISK!!!
North America - v.6.12
https://rom.download.nubia.com/Europe%26Asia/NX669J/V612/NX669J-update.zip
Europe - v.5.12:
https://rom.download.nubia.com/Europe/NX669J/V512/NX669J-update.zip
I've installed v.6.12 on my NA RM6 and all is well so far. Cellular issues seem better if not resolved - need more time to confirm.
Click to expand...
Click to collapse
thx bro i will wait for your feedback .should i reset before installing
An Droid said:
There's a new update on the Nubia download site for the RM6 - this is Android 12:
USE AT YOUR OWN RISK!!!
North America - v.6.12
https://rom.download.nubia.com/Europe%26Asia/NX669J/V612/NX669J-update.zip
Europe - v.5.12:
https://rom.download.nubia.com/Europe/NX669J/V512/NX669J-update.zip
I've installed v.6.12 on my NA RM6 and all is well so far. Cellular issues seem better if not resolved - need more time to confirm.
Click to expand...
Click to collapse
3.28/4.28 is still the last available version on the official website. The only problem with this trick of rewriting the version number in the download link is that we don't know what was fixed in each version...:/
moatazamer83 said:
thx bro i will wait for your feedback .should i reset before installing
Click to expand...
Click to collapse
Pisti870923 said:
3.28/4.28 is still the last available version on the official website. The only problem with this trick of rewriting the version number in the download link is that we don't know what was fixed in each version...:/
Click to expand...
Click to collapse
I've installed it too the network problem seems to be fixed but I need time to to confirm if this is solved
Pisti870923 said:
3.28/4.28 is still the last available version on the official website. The only problem with this trick of rewriting the version number in the download link is that we don't know what was fixed in each version...:/
Click to expand...
Click to collapse
Once installed, you can pull up the changelog (if there is one!).
This is from v.6.12:
An Droid said:
Once installed, you can pull up the changelog (if there is one!).
This is from v.6.12:
Click to expand...
Click to collapse
I have EU version the changelog is the same as v.5.10 idk why
I think only if you get it with an OTA update... This is what I see:
Hi, I have a fold 3, which turned off during normal use and never turned on again, when turned on it remains stuck on the "samsung galaxy logo".
In recovery I tried the update via sd by downloading the firmware from samfw, but it gives error
E: libfs_mgr error updating for slotselect
E: libfs_mgr failed to mount sdcard.
Connecting it to the PC detects that it connects but does not recognize it and does not work, drivers and adb installed.
Install the latest version of the software
The phone was pin / fingerprint locked
It hasn't been formatted, does anyone have any advice on how to do this? At least to recover the data.
How to update your Samsung Galaxy smartphone and install official firmware
Follow these instructions to manually install Android updates through recovery and full firmware using Odin on Samsung Galaxy smartphones.
www.xda-developers.com
If under warranty send to Samsung.
Sounds like a hardware failure.
If so mucking with the firmware may brick it.
Like mate above wrote send to service. I supposed need replace motherboard in this case.
_GRIZZLY_ said:
Like mate above wrote send to service. I supposed need replace motherboard in this case.
Click to expand...
Click to collapse
might not need to be the motherboard, it depends on what part is faulty.
Akira_Kitsune said:
might not need to be the motherboard, it depends on what part is faulty.
Click to expand...
Click to collapse
Maybe yes but rather no chance know it without service.
try use smartswitch from samsung,there is emergency recovery
ashcze said:
try use smartswitch from samsung,there is emergency recovery
Click to expand...
Click to collapse
thanks for the information, however, that software is not detected, I managed to get it read by adb and odin, through odin I tried to install the latest version of the software, it doesn't give errors but then it doesn't start when I restart.
Through adb it stays on the verifyng update package and doesn't install.
Mak563 said:
thanks for the information, however, that software is not detected, I managed to get it read by adb and odin, through odin I tried to install the latest version of the software, it doesn't give errors but then it doesn't start when I restart.
Through adb it stays on the verifyng update package and doesn't install.
Click to expand...
Click to collapse
So in my opinion you are exhaust possibilities rescue in home and unfortunetly need send device to service.
In over a decade of using Androids (all Samsung) I've never seen a firmware failure. Occasionally the user data partition got skewed almost always by a 3rd party app. On a stock flagship Samsung the chances of firmware corruption is almost zero unless there's an outright hardware failure...
The N10+ in my hand load is over 2.5 yo, last update was 3 years ago. Still fast and stable with minimal maintenance. That's what a stock Android is (or should be) capable of... if you don't update it.
blackhawk said:
In over a decade of using Androids (all Samsung) I've never seen a firmware failure. Occasionally the user data partition got skewed almost always by a 3rd party app. On a stock flagship Samsung the chances of firmware corruption is almost zero unless there's an outright hardware failure...
The N10+ in my hand load is over 2.5 yo, last update was 3 years ago. Still fast and stable with minimal maintenance. That's what a stock Android is (or should be) capable of... if you don't update it.
Click to expand...
Click to collapse
Yes, I can confirm too that with example Note 5, Note 9 and now fold 2 older software (max next only one big update to newer version android) is the most stable and battery friendly. Newer version maybe looking "newer" have few intersting function but for daily use usually are little more lags, lottery with battery life. Especially my old Note 5 with android 6 which had when I bught running very nice and now, even after clean install last stock software in this case android 7 Note 5 have a lot of lags and running like the cheapest android device. This my one of a lot example like newer software isn't always better.
Mak563 said:
Hi, I have a fold 3, which turned off during normal use and never turned on again, when turned on it remains stuck on the "samsung galaxy logo".
In recovery I tried the update via sd by downloading the firmware from samfw, but it gives error
E: libfs_mgr error updating for slotselect
E: libfs_mgr failed to mount sdcard.
Connecting it to the PC detects that it connects but does not recognize it and does not work, drivers and adb installed.
Install the latest version of the software
The phone was pin / fingerprint locked
It hasn't been formatted, does anyone have any advice on how to do this? At least to recover the data.
How to update your Samsung Galaxy smartphone and install official firmware
Follow these instructions to manually install Android updates through recovery and full firmware using Odin on Samsung Galaxy smartphones.
www.xda-developers.com
Click to expand...
Click to collapse
Did you tried to make complete wipe from the recovery menu? I know you care about your data but at this point Samsung won't help you and they will probably try to wipe the device first.
In the end not being able to recover it from recovery, I sent it under warranty and they replaced the motherboard.