Hello!
I made an 'upgrade' from Mate 20 Pro, I thought getting used S21 ultra would be better (and much cheaper) than s23.
S21 ultra 128GB arrived in perfect condition no scratches, even on the frame. It was after factory reset, so I begun by downloading android update.
It switched off few times - I left it alone, battery ~80%, but connected to charger anyway.
After a while, I checked on notification panel if it's ready - I started changing every basic thing in settings
Then after I left it for a minute idle - it switched off - I thought that it's normal after an update, so I switched it on and went back to adjusting settings.
Then it switched off again. and after it switched off 3rd time, device was response less
I can't go into download mode, safe mode, anything.
I even went to Samsung support, they checked battery, charging port, buttons etc, and said that they can't help me.
The guy I bought it from is still in contact with me, I trust that everything was alright before - I am waiting for his reply about the Samsung's support verdict.
I also emailed samsung abut what happened - despite that the warranty is off, top of the line device breaking hours after an official update is not ok
But I am trying to unbrick it on my own
When I connect phone with USB, press power and Vol - I got windows error about device not recognised (Code 43)
Please tell me there is a way for me, I am also thinking about buying another used model with broken both glasses, just to get cheaper motherboard to transplant it into my device
Make sure you didn't accidentally put it in edl mode
ebowen 747 said:
Make sure you didn't accidentally put it in edl mode
Click to expand...
Click to collapse
I tried to flash it with stock ROM with Odin with "0 succesful / 0 failed" so I guess EDL is off [unfortunatelly]?
Odin flashes in a different mode. Edl is for factory flashing. The phone will seem dead, black screen no response. Research how to put the phone in edl and how to get it out. Also called 9008 mode
ebowen 747 said:
Odin flashes in a different mode. Edl is for factory flashing. The phone will seem dead, black screen no response. Research how to put the phone in edl and how to get it out. Also called 9008 mode
Click to expand...
Click to collapse
Thanks for an idea, unfortunatelly as far as I researched,
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If phone were in EDL, I would get another view in device manager?
I downloaded Qualcomm drivers, restarted windows, and replugged phone - only response is after pressing Vol down + Power - error "Device malfunctioned, couldn't be recognized and such a view in device manager
It was worth a shot
UPDATE:
Somehow I managed (20th try in 5 days) to get into download mode:
Flashed it succesfully in Odin to latest firmware:
And wiped cache and factory reset phone in recovery mode
I was so happy, I almost bought another used S21 with broken screen, but cancelled as the download mode came on.
I logged into my account, set pin, fingerprint, started to adjust settings to my liking. Then I Cconnected my 40W Huawei charger (I know that S21u has max 25W but I read that it won't harm it. Fast charging popped up, I pressed ok, fidget with settings, then when I went to get my sim from older phone I came back to once again non-responsive phone.
I again can not get into download mode, safe mode, or recovery mode.
Help, I don't know what to do, I will give it a rest once again, but I have no idea how to prevent this from happening again. Will enabling USB debugging do anything?
Or maybe I will actually buy another phone for motherboard transplant
I flashed it successfully with Odin, then cleared cache and factory reset it in recovery
The phone was working! I logged in, started setting pin, fingerprint etc.
Left it to charge and went to my old phone, so I could put my SIM card into now working Samsung.
I came back with SIM and S21 ultra is not responding again.
Please help me with those questions:
If I managed to flash it correctly, then the problem lies in motherboard and is not a software problem?
would motherboard transplant from other phone work for me?
what else can I try?
Thank You in advance
Related
I'm doing the firmware upgrade using Kies off Windows 7 32bit to my Bell Samsung Galaxy S Vibrant i90000. The unit is stock, right out of the box.
It says "Upgrade in progress" and "The upgrade has started". The progress bar is around 15 to 20% and has not progressed during the last 25 minutes. TheGalaxy displays a uniform purple screen.
This is a Bell unit and it does have the now infamous no recovery/download mode keys problem (I checked before starting). So that wont be an option if I kill it.
Is this supposed to take so long or am I screwed?
I'm a new user, so I'm not allowed to post an outside link to this screen shot:
www dot davidkennedy dot com/Photos/UpgradeInProgress.png
ouch!....
Why the heck did you go ahead and flashed your phone, knowing the 3 buttons area dead?
the upgrade does not take more than 5 minutes
the whole process takes about 5 min
it's been over 25 min, and download bar is not complete, chances are your phone will be bricked after you unplug it.
call Samsung/Bell
tell them exactly that
the phone is stuck downloading the new firmware via KIES
they will most likely replace the phone for you
After 1h I killed it (on the windows side).
Phone was still purple screen so I pressed power. Came back with screen of death (the "phone ... exclamation ... pc" image).
I figured that was the end of that phone but...
I restarted Kies and reclicked upgrade firmware. Then I read some interresting stuff I had never seen in the discussions. Kies said the previous upgrade had failed. It told me to to into recovery mode so that I could re-up the firware. Instructions were given to enter recovery so that it could begin.
Strangely, the instructions indicated pressing Home and Volume Down then press and hold power. I figure this text is just wrong, as either they mean to go into Download mode or they should be telling me to press volume up.
Anyhow, I did what they said, and as usual it didnt work. So I removed the batttery and tried again. Failed. Removed the battery again and tried again. Failed. One last time... AND IT WORKED!!!!! Apparently if you just try over and over it will eventually go into recovery/download. I got the download logo and started the Firmware restore.
Guest what... It's stuck at around 5% and it's been 15 minutes again !!!!
I'm about to brick this phone myself; with a real brick.
hey glad to hear you can get into the Download Mode
consider trying the upgrade on another machine
seems like the USB port on that PC is not very stable
if all else fails you can also try Odin3 to flash JH2
davidke - did you keep the USB cable plugged into the computer and phone while doing the "remove battery, put battery back, 3 button combination" ?
I have the same problem with my SGS: the dreaded phone-!-computer image, 3 button combination not working and when plugged in Windows doesn't see it at all.
this screen?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yes, this screen.
neutrin,
Yes, I kept the usb cable plugged in.
I believe this is a clue to the underlying reason for the 3 button combo failure.
It did not work before the attempted upgrade. But after the failed upgrade there is no firmware in the device... so the the combo works.
In my case the combo always works now, first try. I dont know why I had to do several times before getting it once.
In my case the phone is bricked. I cant get anything to connect to it properly. Tried Kies, ADB and Odin. My PC sees it on the USB and the device says "Downloading" with the yellow android doing street work, but that's it.
Anybody have any suggestions? I'm gonna take it back to the store in a bit. I've had it with (no-so-)smart phones.
don't you have another PC you can try it on?
either Kies or Odin should be able to flash you to JH2 or whatever version you choose
You talked me into it... one last hope for this phone.
Downloading everything to my laptop and will try Kies, ODIN and adb.
Will report back later.
It worked.
I was bricked and you saved me. Thanks.
Kies: No go. Odin: Worked.
Reloaded UGJH2 and phone is back to normal. Reinstalling my apps...
I'll post another thread explaining how I accidentally got into Download Mode on a phone with the 3 button combo disabled. Might be interresting for others.
congrats!
that is great news!
I have a SFR (french operator) branded SGS and rumor is that this function is disabled on some of the phones sold by them. Many owners of SFR branded SGS complain about this.
I would be thrilled if your method worked. Please post a link to the new thread when you start it. Thanks!
You wont want to try it. But this is the link:
http://forum.xda-developers.com/showthread.php?t=769871
@neutrin post your results after you are done trying those methods
No success with this method. Not even after the phone got pretty warm (1 hour connected to USB). I held the buttons pressed for 5-10 minutes in a row, several times. It seems the SFR branded phones are really crippled.
i was pretty sure it was not going to work for truely disabled phones
Oh well... I'm going to have to wait for a JTAG solution.
I just can't imagine why would SFR and perhaps other operators want this function disabled just for some of the SGS they sell.
i'm pretty sure it has to do with the network operators requesting the feature to be removed, to prevent the phone from being unlocked
That didn't prevent the unlock on mine. There must be another reason. Perhaps prevent debranding?
I did something stupid because I kept getting the samsung boot loop. What had happened was that I successfully installed the khasmod rom for the Verizon tab but tried backing up rom through clockwork program, tab rebooted itself after pressing "back up rom". Tab got stuck in boot loop, so I used heimdall to flash a STOCK Verizon firmware(to also include boot.bin and sbl files). It successfully flashed and the tab went blank and never came back. With that said where can put this under... A lop-sided table leg crutch or a book shelf holder? All jokes aside, anyone know the next course of action?
oscaria said:
I did something stupid because I kept getting the samsung boot loop. What had happened was that I successfully installed the khasmod rom for the Verizon tab but tried backing up rom through clockwork program, tab rebooted itself after pressing "back up rom". Tab got stuck in boot loop, so I used heimdall to flash a STOCK Verizon firmware(to also include boot.bin and sbl files). It successfully flashed and the tab went blank and never came back. With that said where can put this under... A lop-sided table leg crutch or a book shelf holder? All jokes aside, anyone know the next course of action?
Click to expand...
Click to collapse
more details...
does the tab light up at all or is it just a black screen and wont turn on at all?
wait a few days to let it die all the way out and stick it on the original samsung usb wall charger...if you dont get a battery icon on the screen id say youre pretty much done.
i bricked mine but luckily i was still within my 2 week window with t-mo and they exchanged it...i mean they couldnt put it in bootloader to see if it had been hacked so what else could they do.
i read a post about a special cable you can make with a certain resistor wired into it so when you plug it into the tab it resets something and will let you go into download mode again...
BUT...if i remember correctly, it only worked when you get stuck at a splash screen, and if the tab wont turn on at all, it wont work.
any other paperweight ideas?
google around a bit more and see if theres some kind of option...i think you could try and send it to samsung if its under its 1yr warranty still, but thats a gamble if they DO get it working and see youve hacked it...voiding your warranty.
i just wonder if they could get it to turn on, and find your recovery, they still have to send it back to you...so if they fix the turning on issue, slap it in download and do the rest yourself. thatd be my last resort, fingers crossed bro, i know how ya feel right now, it sucked for me
No lights at all...
Tried: holding down power and vol down for 10 mins in the John.
Plugging into USB with CPU or charger and no battery icon... Left overnight even.
It's like it's sleeping or in an inception searching for something.
I've done hd2 and G2 but the flashing here is ultra brick mode capable...
Can you print the exact command you used for Heimdall? Assuming you entered all the files in the correct place then I assume it's simply a matter of flashing a primary or secondary bootloader that is not designed for your device. If the primary bootloader is still okay then you can use a custom jig to boot your device into download mode using the backup secondary bootloader. Search the forums for "custom jig", you might have more luck in the Galaxy S section though.
Is it kinda hard too do
Well to I've print screened my Heimdall setup in the pic below...
I 'm pretty sure I did myself in with the boot.bin and sbl.bin files --- I had the Khasmod v2. rom installed previous to this flash and sure enough -- I recalled reading something about not flashing such files due to bootloader lock or something to that effect.
Here is the web address of the file I got for the Stock Verizon Heimdall files:
http://www.droidforums.net/forum/sa...84-how-restore-vzw-galaxy-tab-stock-dj11.html
Im curious about that jig custom process for the galaxy S that I guess would work for the Tab...But I don't think my laptop would read or recognize an incepted Tab that wouldn't go into download or recovery or telephone --?---computer mode.
I'm pretty darn certain I would never touch a firmware upgrade or rom or kernal install with a 7inch Tab....I'm OTA all the way if my tab comes back alive
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://www.flickr.com/photos/[email protected]/5595802236/
for the print screen pic of heimdall setup
I did this exact thing to my tab... So there is no solution?
Sent from my SGH-T959 using XDA Premium App
Hold the power button down by itself for about 10 seconds, let go, then do it again.
If nothing happens either time, put it on the shelf for about a week, then try it again, then plug it into the proper charger for a couple of hours, then try it again.
If it does nothing at any stage, then you can try returning it under warranty and see if they'll take pity on you.
I was in worse situation than u few days back, I tired going back stock jk2 from OverCome rom.
Tab got stuck in 'Phone connecting to PC mode' It's worst than the Samsung loop.
I read somewhere than 'if odin can detect yr tab, then it's not brick' just that u need the correct files.
lollypop said:
I was in worse situation than u few days back, I tired going back stock jk2 from OverCome rom.
Tab got stuck in 'Phone connecting to PC mode' It's worst than the Samsung loop.
I read somewhere than 'if odin can detect yr tab, then it's not brick' just that u need the correct files.
Click to expand...
Click to collapse
Your problem is fixable. My tab is bricked. Won't turn on, odin won't recognise.. Nothing. I am sending it into samsung tomorrow hoping they will do something about it.
Sent from my SGH-T959 using XDA Premium App
I'm in the exact same boat. Flashed those exact same files using Heimdall and now the thing won't turn on at all. I'm gonna give it a few days to see if the battery drains and plugging it in starts something up. Otherwise I guess I have no choice but to send it to Samsung as well.
I was in the same boat. I was trying to flash back to stock in oldin and something went wrong, tablet would do anything but show lights at bottom. Call carrier and Samsung said was covered under the one year manufacture warranty. I was without tablet for 2 weeks but not out of and money.
I can toggle the option in the developer menu, but it don't show on the PC.
If I exit that menu and go back in, USB debugging is off again.
I've tried a restart without affect. Any ideas?
I've had the same issue. I've simply turned it on, went back one step, then into the developer settings again and checked if it was still on. It wasn't, so I did this repeatedly until it stayed on. Since then it never turned off again.
Also, disconnect it from the PC. As far as I can remember it only stayed on if it was activated while disconnected. I couldn't activate it before when it was connected.
Still having problems with this. Thought it may have been a bug with 106 firmware, but upgraded to 107 last night and issue persists.
Any help or ideas please? I've tried activating it several times in a row and can't get it to stick at all
I have just come across this issue. I suddenly lost root, and any time I try to open an app that requires root it just closes.
Then I noticed that USB debugging wasn't on. It had been fine for over a week, now it just won't stick no matter what I try.
Anyone found a solution yet?
Also turn on the option for allow debugging only in charge mode. That should fix it
AaronAverage said:
I've had the same issue. I've simply turned it on, went back one step, then into the developer settings again and checked if it was still on. It wasn't, so I did this repeatedly until it stayed on. Since then it never turned off again.
Also, disconnect it from the PC. As far as I can remember it only stayed on if it was activated while disconnected. I couldn't activate it before when it was connected.
Click to expand...
Click to collapse
I did the same as i was getting frustrated adb couldn't get it but at the end i made it work, even if sometimes adb devices don't get the device so i have to switch between transfer files and charge only mode, after a couple of time adb recognize the device and I'm good to go
Still having trouble with this. Still unable to turn the setting on.
Also discovered today I couldn't select the transfer files button when connected to the PC, kept going back to charge only.
I found the setting only sticks when the USB is connected and if you visit the dev settings while it is unplugged it will be switched off again.
mushtafa said:
Still having trouble with this. Still unable to turn the setting on.
Also discovered today I couldn't select the transfer files button when connected to the PC, kept going back to charge only.
Click to expand...
Click to collapse
I have the same problem. I am VERY glad when someone knows how to fix this truely but I have a tip for you: Charge the p20 pro to 100% and then plug it in the usb port. You can then enable usb debugging and for me it then does the trick and works as long as i dont unplug it. If I unplug it, I need full charge (100%) first and then can debug again.
For my Laptop with which I am debugging, windows 10 displays "current overvoltage at the usb connection" and I can neither access my normal data on the phone (just charging modus is enabled) nor debugging. MTP connection is enabled but it still does not work.
Have the same issue myself, could this be a logic problem as indicated here ?
https://forum.xda-developers.com/mate-9/help/udb-debugging-wont-stay-t3711939
mrabcx said:
Have the same issue myself, could this be a logic problem as indicated here ?
https://forum.xda-developers.com/mate-9/help/udb-debugging-wont-stay-t3711939
Click to expand...
Click to collapse
Just tried it out with so much hope that this would work. Unfortunately it does not work. I have the "Allow ADB debugging in charge only mode"-switch on and the "Always prompt when connecting to USB"-switch off. Does it work for all of you if the phone is charged 100%
I updated the firmware to .128 and the fault persists. Was hoping it was just a bug
Same problerm here. Worked fine for 4 weeks, stopped working yesterday. FW .120. Tried all the hints, no luck. Other suggestions?
I have same problem.... I use debug mode for connect p20 to pc and use it from remote.... damn now i'm ****ed with tis BIG BUG. Version .128
adivorandroid said:
I have same problem.... I use debug mode for connect p20 to pc and use it from remote.... damn now i'm ****ed with tis BIG BUG. Version .128
Click to expand...
Click to collapse
Did you managed to remote debug successfully?
NO, same bug in last .128
Does someone know how to reach out to huawei so they fix it? Because it seems to be a major problem for several devices, not just one.
I'm very angry for this... i can't use my phone during my job at pc, all for a stupid BUG !!!!
I'm writing to Huawei ... I hope to receive a reply soon
.131 will be available soon ... we hope for the solve bug problem
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I found a workaround except from waiting for 100% charge: Use a usb c to usb c cable, on my laptop and with my cable the energy drain is not higher than allowed then
title
Redmi Note 9 4G
The phone reboots into Qualcomm 9008 mode after a non-artificial cause and requests a data rescue method
Simple description
My English is not very good, if the robot translation causes you to be unable to understand, please be sure to ask several times until you are clear
A friend recommended to me to go on XDA forum to try to ask the rescue method, I have not done anything bad, simply carry out the system application freeze, factory original system
In the early morning before the accident, the phone used everything normal, slept for about seven or eight hours, after getting up the phone is not smooth, at that time some applications can not be opened, but alipay Google play version, can be opened normally, play the small program components
After several checks, as well as connecting to a Windows 10 computer, the device manager showed Qualcomm HS-USB QDLoader 9008 (COM 3)
I really did not artificially want to enter the 9008 mode, the application freezes only for simple, de-advertising
Have not executed any adb, or adb into EDL commands
So I would like to ask you all if the data inside is still saved? What is the way to save it? And the data of phone calls and SMS are also very important
Mobile Phone Information
Model: Redmi Note 9 4G
Memory: 8 GB
Storage: 256 GB
Version: V12.0.6.0.QJQCNXM (if memory serves, factory pre-installed untouched and un-upgraded)
Upgrade: Off, did not allow any automatic system / software upgrades
Unlock: BootLoad to meet the unlocking conditions, before the incident did not operate to unlock
Brush: No, factory pre-installed system, only Adb freeze a few non-Kami system applications
Purchased: Jingdong, 2021-01-23, https ://item .jd .com/100009845167 .html
Activation: left for a while, about 2021-02-? The end of the year to bind mi account (I forget the exact date)
Backup: None, old phone is Note 4X data is still there (old), but disconnected from N9 existing data for about six months
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Device Manager
>> ports (COM and LPT)
Qualcomm HS-USB QDLoader 9008 (COM 3)
The phone black screen, Fastboot and other hard button trigger, the screen are no response, there is no splash screen and normal shutdown charging screen prompt
Long press the power button, the computer will have a device connection sound (dong dong), followed by two to three seconds interval device interruption connection (ding dong) beep
Question content
1、Is there any rescue for the data stored in the built-in storage, the data is only stored locally not on the cloud (important)
2、Do you have a suitable and reliable tutorial for successful brick rescue (important)
(not a thousand unreliable network hydrology, preferably their own / friends of reliable and feasible credibility of successful experience)
3, according to my complete description of these attempts to operate the evaluation, whether the phone is still saved
Hy guys, i want to ask. But first I want to let you know that this is not my phone, I use this phone only temporarily, but I am here and asking because there is something that makes me (sometimes) feel very very upset and frustrated.
This is my brother's phone, and he also asked me to help him in fixing the problem I was about to ask...
The problem is: Automatic freezes and reboots
That simple isn't it? But the impact is big, during that phase I can only use this phone for only a few minutes because my phone keeps freezes and auto reboots, basically during that phase, I can't do anything, all I can do is wait until it returns to normal or turn off my phone for a few minutes which is obviously quite long, more than 10 minutes going like that (freezes and auto reboots). Version number 52.1.A xxxxx (I forgot, there are clearly 3 numbers at the end), I tried to downgrade to version number 52.1.A.3.92 but it didn't change anything.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
oh yeah, the trigger is a change in everything related to connectivity (WiFi, bluetooth, gps, sim card, etc), even when activating auto-rotate. Hard reset, flashing, downgrade, reset connectivity, nothing helps. Can anyone provide a solution? can downgrading the android version or using a custom rom help? is this just a software bug or a hardware problem?
thank you
OctanovaFX said:
Hy guys, i want to ask. But first I want to let you know that this is not my phone, I use this phone only temporarily, but I am here and asking because there is something that makes me (sometimes) feel very very upset and frustrated.
This is my brother's phone, and he also asked me to help him in fixing the problem I was about to ask...
The problem is: Automatic freezes and reboots
That simple isn't it? But the impact is big, during that phase I can only use this phone for only a few minutes because my phone keeps freezes and auto reboots, basically during that phase, I can't do anything, all I can do is wait until it returns to normal or turn off my phone for a few minutes which is obviously quite long, more than 10 minutes going like that (freezes and auto reboots). Version number 52.1.A xxxxx (I forgot, there are clearly 3 numbers at the end), I tried to downgrade to version number 52.1.A.3.92 but it didn't change anything.
View attachment 5622717
oh yeah, the trigger is a change in everything related to connectivity (WiFi, bluetooth, gps, sim card, etc), even when activating auto-rotate. Hard reset, flashing, downgrade, reset connectivity, nothing helps. Can anyone provide a solution? can downgrading the android version or using a custom rom help? is this just a software bug or a hardware problem?
thank you
Click to expand...
Click to collapse
I'm also having the same problem. Is there any solution?
I have same problem
My xz3 is so01l
I guess ta broken
Who can help fix?
hey i have had this problem for months now. Recently I flashed to a custom version (originally on SOV39) and i rooted my device and the problem still persisted. However, I found a temporary fix without messing with the hardware.
By disabling the sensors and then rebooting. It stopped randomly restarting and I can even use the device with airplane mode turned off while having all the internet functions working.
You can find it on Developer Settings - Quick Settings Developer Tiles - Sensors Off. From there you can just toggle it off on the Quickbar menu and reboot the device. Hopefully it works for you too!
I have same reboot problem, only restarts after a min in normal mode. Works fine in flight and safe mode
I took a notice it can be the cell radio as it is off in plane mode.
I find side sense and one hand mode. Is it the things to turn off? I have the same problem, works fine in flight or safe mode. Some wrote it could be the cell radio.
I have checked for the updated version of Android System Webview as another wrote in another thread it could be that by going to Apps and Storage - Play Store. But it is not on my phone so that can't be the problem for me. I have turned off 2 sensors, side and one hand mode but it restarts after a halv min in normal mode.
Oldschool297 said:
I have checked for the updated version of Android System Webview as another wrote in another thread it could be that by going to Apps and Storage - Play Store. But it is not on my phone so that can't be the problem for me. I have turned off 2 sensors, side and one hand mode but it restarts after a halv min in normal mode.
Click to expand...
Click to collapse
I tried the same solution (update system webview) and didn´t work for me, I´m currently performing a software repair to see if it helps, the thing is that my phone doesn´t reboot as often but still it´s upseting me.
I was able to partially solve my problem with my phone, I took out the black antenna frame and very carefully placed transparent scotch tape (because it´s thinner than medical tape) in all the contacts that are marked in red in the atached picture but now I´m thinking that I shouls have placed tape also on the places marked with green.
So what change I experienced on my phone with this method?
well the phone now has Network and wifi signal all the time and very ocassionaly it does lose the network and wifi signal for a second but when this happen the phone does not say that there is no sim card and does not freeze and restart, it just recovers signal by itself and I can continue using the phone.