Hey guys,
I'm forcing some super strange problems with my beloved OnePlus 9 Pro since yesterday. I already did everything I could imagine for the whole 2 days, but doesn't matter what I try, it's not helping. I hope you can maybe help me out with your ideas, as I don't know what else I should do!
It all started yesterday in the morning, where I noticed that the screen rotation was not working, even after I restarted the phone (which is definitely taking longer now than before). During the day I noticed that the phone got overheated a lot of times (I know overheating is an issue but since the last update it worked pretty well with mine), even though it was in the shadow, at 25 degrees without any hard tasks, thus I noticed the first software bugs e.g. unlocking took a lot of time, with black screen, fingerprint sensor not visible, apps lagging...In the display settings, I can't change the video enhancement settings because it's telling me the phone is too hot - all the time! The next I noticed that the video function in the original camera app is suuuuper laggy, so it's not possible to take any video at all (attached a screen recording). Other camera apps work fine for the video, but hardware detection apps can just detect the 12MP sensor? During the day I then ran a sensor identification app which was able to identify all the sensors on another device but showed error messages for all my sensors (attached as well). I ran multiple security scans (Bitdefender, Avast, AVG, Kaspersky...) without any problems. Also, I updated the software and already did a hard reset - which changed nothing.
Now it's getting even more strange... As the phone got slower and slower with the day, I checked the storage and noticed that a huge amount (more than half of my whole storage) is full of system data AND IT KEEPS EXPANDING WITH ANY MINUTE. I have to delete more and more of my private data to keep the phone running... I attached you some screenshots over the time to recognize the growing data.
I hope so much that you can help me out with that! Already thanking you for your responses...
Some background information about my device...
It's a OnePlus 9 Pro, 256gb, 12 GB RAM EU Original Oxigin 12 Version (installed the new update around a week ago), non-rooted. I've installed some MOD APKs but always kept scanning with Bitdefender after that - anyway, I know that's not super safe.
Thanks so much,
Max
Screen record of the camera bug:
Record_2022-02-13-20-07-20.mp4
drive.google.com
I would think possibly factory reset w/wipe data might fix? I would be weary of mod apks. I hope it's something simple and am not sure but thought I'd share what comes to mind.
If you did a factory reset and it didn't help you with your issue, I would STRONGLY suggest using MSM tool to re-flash your phone and eliminate any possible issues with the OS. If you're not ready to use MSM, well, than claim your warranty...
Btw. MSM tool is for unbricking OP phone, it's nothing complicated or "dangerous". But it does a clean flash from the scratch on the phone including formating all the partitions, etc...
Safe mode and see what it does.
If it still doing it it sounds like a mobo failure.
No rootkit should have survived the factory reset unless you reloaded it How much internet bandwidth is it using at idle? Think back to what you did when it started. In the last month or so?
Try to find what is running in the background.
If you come up with nothing try reflashing to the last known good version... not the newest.
If it continues, it's almost certainly hardware. Flash memory shouldn't get corrupted so even if a reflash fixes it... keep an eye on it.
blackhawk said:
Safe mode and see what it does.
If it still doing it it sounds like a mobo failure.
No rootkit should have survived the factory reset unless you reloaded it How much internet bandwidth is it using at idle? Think back to what you did when it started. In the last month or so?
Try to find what is running in the background.
If you come up with nothing try reflashing to the last known good version... not the newest.
If it continues, it's almost certainly hardware. Flash memory shouldn't get corrupted so even if a reflash fixes it... keep an eye on it.
Click to expand...
Click to collapse
Could be possible, as I restored a backup. But even before I restored the backup, I had the screen rotation and camera lagging problems without having anything intalled but the fresh OS. I really just started 2 days ago out of nothing, that's why I was so surprised. Also, the internet bandwith is quite normal, and it keeps expanding the system data without running internet connection... have the phone off the whole day now as it is not possible to use any app at all as the system data is at 70% of the whole storage now and still keeps growing... Always have to delete another app to use my phone for 5 min lol .
I'll try the safe mode and see what's happening. After that, I'll try to wipe the whole data again, like @Samuel Holland suggested and will reflash with MSM like @ekin_strops told (to an older version than).
Thank you very much so far guys,
I will keep you posted!
Max
baacon said:
Could be possible, as I restored a backup. But even before I restored the backup, I had the screen rotation and camera lagging problems without having anything intalled but the fresh OS. I really just started 2 days ago out of nothing, that's why I was so surprised. Also, the internet bandwith is quite normal, and it keeps expanding the system data without running internet connection... have the phone off the whole day now as it is not possible to use any app at all as the system data is at 70% of the whole storage now and still keeps growing... Always have to delete another app to use my phone for 5 min lol .
I'll try the safe mode and see what's happening. After that, I'll try to wipe the whole data again, like @Samuel Holland suggested and will reflash with MSM like @ekin_strops told (to an older version than).
Thank you very much so far guys,
I will keep you posted!
Max
Click to expand...
Click to collapse
Msm is the only thing if you were rooted and had malware get in the system
blackhawk said:
Safe mode and see what it does.
If it still doing it it sounds like a mobo failure.
No rootkit should have survived the factory reset unless you reloaded it How much internet bandwidth is it using at idle? Think back to what you did when it started. In the last month or so?
Try to find what is running in the background.
If you come up with nothing try reflashing to the last known good version... not the newest.
If it continues, it's almost certainly hardware. Flash memory shouldn't get corrupted so even if a reflash fixes it... keep an eye on it.
Click to expand...
Click to collapse
Just tried it in Safe Mode now... screen rotation and video function are still not working, and the system data is also still expanding (around 1,5gb in 10 min). I'll try to flash from the beginning with MSM tool now and see what happens.
After an hour, I'm still figuring out how to boot my OP to EDL mode... watched dozens of YouTube videos, but it's always ending in fastboot mode after I connected it to my pc (even just when holding the volume buttons without power button). Also, in fastboot mode it's not getting recognized by my pc. Any ideas on that? Or this there any other method to force it into EDL mode?
baacon said:
After an hour, I'm still figuring out how to boot my OP to EDL mode... watched dozens of YouTube videos, but it's always ending in fastboot mode after I connected it to my pc (even just when holding the volume buttons without power button). Also, in fastboot mode it's not getting recognized by my pc. Any ideas on that? Or this there any other method to force it into EDL mode?
Click to expand...
Click to collapse
Reboot the PC...
Try a different cable and port.
Check Windows Event Viewer for error messages.
Driver, is the right one loaded? Try updating or rolling it back.
Try different sequence or timing with the buttons.
baacon said:
Also, in fastboot mode it's not getting recognized by my pc
Click to expand...
Click to collapse
Update driver in device manager. Choose from list of manufacturers, ONEPLUS, and reinstall all 3 again.
Also, Check status of adb devices. If it's "unauthorized" authorization was revoked. You need to unplug the phone then delete this file : C:/users/<username>/.android/adb key
And replug your phone, then allow connection again.
A last resort is to extract payload.bin, then flash all partitions again. Here's a good tutorial. Never tried it though...
How to Unbrick OnePlus 9/Pro via Fastboot Commands
In this comprehensive guide, we will show you the steps to unbrick the OnePlus 9 and 9 Pro devices via Fastboot Commands.
www.droidwin.com
baacon said:
After an hour, I'm still figuring out how to boot my OP to EDL mode... watched dozens of YouTube videos, but it's always ending in fastboot mode after I connected it to my pc (even just when holding the volume buttons without power button). Also, in fastboot mode it's not getting recognized by my pc. Any ideas on that? Or this there any other method to force it into EDL mode?
Click to expand...
Click to collapse
temp boot twrp. in twrp reboot edl mode.
baacon said:
After an hour, I'm still figuring out how to boot my OP to EDL mode... watched dozens of YouTube videos, but it's always ending in fastboot mode after I connected it to my pc (even just when holding the volume buttons without power button). Also, in fastboot mode it's not getting recognized by my pc. Any ideas on that? Or this there any other method to force it into EDL mode?
Click to expand...
Click to collapse
had the same issue.
I somehow expected some kind of special EDL screen on my phone.
but its just black.
start the MSM tool with pressing the start button.
shut down the phone.
Hold both volumes in to get in Qualcomm EDL mode and the screen will stay black. While holding, plug in the USB cable from your phone to your computer. Let volumes go alter plugged in.
additional info:
MSM tool for OP9pro you can find here : MSM tool OP9pro
More guides how to use it find here : MSM guide
vincemue said:
had the same issue.
I somehow expected some kind of special EDL screen on my phone.
but its just black.
start the MSM tool with pressing the start button.
shut down the phone.
Hold both volumes in to get in Qualcomm EDL mode and the screen will stay black. While holding, plug in the USB cable from your phone to your computer. Let volumes go alter plugged in.
additional info:
MSM tool for OP9pro you can find here : MSM tool OP9pro
More guides how to use it find here : MSM guide
Click to expand...
Click to collapse
yes, it's exactly the same with mine... I noticed that the problem is the Qualcomm driver, as the device is shown with an error in other devices. Already tried to reinstall it 3 times, as well, with the Windows driver verification deactivated. Also tried the manual way, but it always says that windows can't find drivers in my Qualcomm folder... Will try it with another computer later and see how it works.
baacon said:
yes, it's exactly the same with mine... I noticed that the problem is the Qualcomm driver, as the device is shown with an error in other devices. Already tried to reinstall it 3 times, as well, with the Windows driver verification deactivated. Also tried the manual way, but it always says that windows can't find drivers in my Qualcomm folder... Will try it with another computer later and see how it works.
Click to expand...
Click to collapse
Try online automatic driver update.
My friend, after using MSM tool, do NOT restore back-up!
If you restore it is all for nothing.
Alright, it worked now - the problem with the MSM tool worked with another laptop, don't know what was wrong with the other one. The good news is that the video function in the camera app is now working again (which is super important for me) BUT the sensors are still all not working and won't be detected by the phone. Do you have any other idea what could cause that? They stopped working from one day to another without any physical damage or anything. I'll also keep you posted about the storage (if it still keeps growing), so far it's growing but because the device installs all the updates...
(and for sure I'm going to install everything manual now )
baacon said:
Alright, it worked now - the problem with the MSM tool worked with another laptop, don't know what was wrong with the other one. The good news is that the video function in the camera app is now working again (which is super important for me) BUT the sensors are still all not working and won't be detected by the phone. Do you have any other idea what could cause that? They stopped working from one day to another without any physical damage or anything. I'll also keep you posted about the storage (if it still keeps growing), so far it's growing but because the device installs all the updates...
(and for sure I'm going to install everything manual now )
Click to expand...
Click to collapse
Try it in safe mode. Don't update anything until sensors are tested. If no go, check for system updates. The firmware may have become corrupted, reflash to the known good stock rom. Firmware shouldn't go corrupt and if so may indicate a mobo failure... keep an eye on it.
blackhawk said:
Try it in safe mode. Don't update anything until sensors are tested. If no go, check for system updates. The firmware may have become corrupted, reflash to the known good stock rom. Firmware shouldn't go corrupt and if so may indicate a mobo failure... keep an eye on it.
Click to expand...
Click to collapse
I am back to my latest known version of Android that worked well with my sensors. I also already tried in safe mode again. The crazy thing is that the sensors are not even shown in apps like device info 360 - it says that my phone has 0 sensors.
baacon said:
I am back to my latest known version of Android that worked well with my sensors. I also already tried in safe mode again. The crazy thing is that the sensors are not even shown in apps like device info 360 - it says that my phone has 0 sensors.
Click to expand...
Click to collapse
It's possible you lost a chipset. It show battery temperature? A repair manual be useful if you could dredge one up online.
Related
I've had my Samsung Galaxy Tab S 8.4 (SM-T705Y) for just over two years now and it has worked brilliantly beside the odd issue here and there, including the device freezing from time-to-time. Each time that particular freezing issue has happened, I've used the 'Power and Volume Down buttons' technique and it has successfully fixed the issue.
Now, a few days ago, I was using my tablet for normal morning things; music app playing in the background, YouTube opened on the side, using the preinstalled Browser and Google Chrome apps, etc. I am not sure if it was updating any Google or Samsung apps at the time. The screen froze up so I left it for a few minutes, seeing if it would unfreeze. When it didn't, I used the same Power and Volume Down technique, which successfully forced-restarted the tablet. There was a small mistake I made doing this; I was holding down both the Power button and Volume Up button. It took me around thirty seconds to realise why the screen wasn't turning off and switched to the Volume Down button. At the time, both my earphones and the charging cord were connected.
However, upon the loading screen, I noticed that it did not pass the Samsung logo screen with the little explosion of blue circles and just kept replaying the same animation repeatedly. The Application History and Back buttons did not light up and the device did not vibrate as it normally does when it boots up. I repeated the Power-Volume Down technique to see if that would fix the issue. Once again, the tablet rebooted normally but was stuck at the logo screen playing the animation. I tried this same force-restart again, this time without the charger plugged in. No change.
So, I left it running through the animation while doing Google searches through forums and getting into contact with Samsung as to what the issue could be. I'll list down below what my tablet can and can't do at the moment and hopefully someone will have a clue as to what is going on and how to fix it. I will point out now that it was not going through a firmware update at the time, the device is not rooted and nor do I plan on taking that path with it, and I have not made any changes to it that can void the warranty.
It can:
- Recharge (The battery icon will show up if it is force-restarted and the charger is plugged in at the time.)
- Reboot (It's not exactly stuck in a bootloop, more of just the 'explosion' animation replaying over-and-over.)
- Enter Recovery Mode
It cannot:
- Enter Safe Mode
- Be Shut Down without the charger attached (As stated above, the device will only turn off with the Power-Volume Down buttons held for about 30 seconds and that causes the device to restart, not turn off. The only way for it to completely shut down is to have the charger connected and then unplug it after the battery icon appears.)
I have tried removing the SD card and placing it back in, power-cycling it, letting it run on the animation until the battery runs out and then letting it recharge to 100% before turning it on again, connecting it to Samsung Smart Switch (which recognises that there is a Samsung device connected, but not being able to register the device itself), and wiping the Partition Cache (Also note; the Recovery Mode has the 'No Command' sign with the android laying down and the red triangle with the exclamation point above it. Clearing the Partition Cache seemed to go smoothly, however when I chose the 'reboot device now' option, the 'No Command' sign changed to 'Error!' and rebooted the device anyway.) I am now currently trying another technique written on a different website (though since I am a new user, I cannot post up URLs at the moment). So far, plugging in the earphones alone hasn't worked and the device is currently connected to my laptop - which is shut off - and still has the earphones connected, but the animation is the only thing the screen is still showing.
I have important files saved in the internal storage of my Tab S and I do not have them backed up, which is the only issue that's stopping me from just going ahead and doing a Factory Reset as I cannot lose these files.
I am unsure if my Tab S is soft-bricked or if this is another issue entirely and I just missed something that could have already fixed it.
Yes, this is a long and detailed post, but hopefully with these details, someone will be able to help with this issue. If I can restore my Tab S to its condition before the freeze, that would be amazing, but I can definitely settle with only being able to salvage my files from the internal storage and then performing a Factory Reset on it.
Thank you in advance~
It might be a corrupt partition. The way i know involve rooting or the other one might format your device to factory setting.
edan1979 said:
It might be a corrupt partition. The way i know involve rooting or the other one might format your device to factory setting.
Click to expand...
Click to collapse
Really? I might look into that a bit more, thanks! With the second method you mentioned, how likely are the chances of it formatting the device to the factory settings?
AussieMouse said:
Really? I might look into that a bit more, thanks! With the second method you mentioned, how likely are the chances of it formatting the device to the factory settings?
Click to expand...
Click to collapse
download the official firmware and flash it via odin. it usually fix this type of problem. but usually the files on the internal storage/sdcard will be intact. only the data apps will be gone. this will not break your warranty (its already 2 yo device... no more warranty anyway ^_^)
edan1979 said:
download the official firmware and flash it via odin. it usually fix this type of problem. but usually the files on the internal storage/sdcard will be intact. only the data apps will be gone. this will not break your warranty (its already 2 yo device... no more warranty anyway ^_^)
Click to expand...
Click to collapse
Alright, I'll try that and let you know how it goes. Is there any specific website I should download the firmware (4.4.2 KitKat) from? (Yeah, I agree with you there! Still, just to be on the safe side~)
KIT KAT? ok that's old... hahaha... why dont you try MM. I think you can search for it at fw.updato.com probably can see all related firmware there.
edan1979 said:
KIT KAT? ok that's old... hahaha... why dont you try MM. I think you can search for it at fw.updato.com probably can see all related firmware there.
Click to expand...
Click to collapse
Haha Yeah, I'm not too fond of installing software updates due to past experiences~ I'll have a look around.
AussieMouse said:
Haha Yeah, I'm not too fond of installing software updates due to past experiences~ I'll have a look around.
Click to expand...
Click to collapse
MM is ok. I dont have any problem with it.
edan1979 said:
MM is ok. I dont have any problem with it.
Click to expand...
Click to collapse
Thank you so much for your help! I managed to find the KitKat 4.4.2 firmware on SamMobile and flashing it restored everything~
I'm something of a noob here, so I appreciate your patience and help.
My wife's Nexus 5x applied the latest update for 7.1.1 and her phone then fell victim to the dreaded bootloop. I was able to get through this guide to apply a rescue OTA: https://drive.google.com/file/d/0Bz6x7k-VkpUJam5Mc1hKa09PVGc/view (sorry, I can't post the hyperlink to an external site since I'm so new here, lol).
All of the steps completed down to step 21, when I tried reboot after the update - it rebooted then went right back into the boot loop.
The OTA I used was for Bullhead N4F26O (which is the one I should use based on the guide). I also tried N4F26I, but the OTA failed and it went straight to the bootloop.
I ran out the battery, charged it a bit, and tried again, but ran into the same problem (update completes, reboot, bootloop starts again).
Does anyone else have any more ideas on what I can try? At this point all I really care to do is recover any photos I can from the device (my wife forgot to setup image backup on her phone and USB debugging was never turned on). Google Fi already offered to send out a replacement, so I'm not worried about getting the device fully functional again.
Thanks for your help.
Not sure exactly what happened, but the phone was plugged into my PC stuck in the bootloop. I unplugged the phone and it booted...it didn't have much of a charge, so I quickly turned on developer mode, USB debugging, and some other option I noticed about allowing unlocking of the OEM bootloader. Also, I checked the backup settings for her photos and they were set to backup automatically, but just on a secondary Google account.
If anyone has any ideas for resurrecting the phone, I'd appreciate it (for the sake of learning if nothing else). Thanks
LeChuck5000 said:
Not sure exactly what happened, but the phone was plugged into my PC stuck in the bootloop. I unplugged the phone and it booted...it didn't have much of a charge, so I quickly turned on developer mode, USB debugging, and some other option I noticed about allowing unlocking of the OEM bootloader. Also, I checked the backup settings for her photos and they were set to backup automatically, but just on a secondary Google account.
If anyone has any ideas for resurrecting the phone, I'd appreciate it (for the sake of learning if nothing else). Thanks
Click to expand...
Click to collapse
Exactly how did you apply the update? Over the phone or fastboot? Can you get to fastboot mode (bootloader)? Unlocking the bootloader will erase everything.
Tulsadiver said:
Exactly how did you apply the update? Over the phone or fastboot? Can you get to fastboot mode (bootloader)? Unlocking the bootloader will erase everything.
Click to expand...
Click to collapse
I can get it into fastboot, and can sometimes get it into recovery (but not consistently...it often just goes into the bootloop when I try to launch recovery).
To apply the update I just followed the guide I linked to in my OP. First, installed the adb, fastboot, & usb drivers on my computer. I then put the phone into recovery, and wiped the partition cache. I then connected the phone to my PC, picked Apply update from ADB on the phone, and ran adb sideload c:\MyNexus\bullhead-ota-n4f26i-06953aec.zip from the command line on my PC.
Heat the EMMC Chip. I tried every type of flashing to fix it, nothing did. Then I did what a lot of people said and tried to heat the emmc chip and it worked perfectly. It's been working fine for the past 3 days and I hope it stays that way.
Arrivale said:
Heat the EMMC Chip. I tried every type of flashing to fix it, nothing did. Then I did what a lot of people said and tried to heat the emmc chip and it worked perfectly. It's been working fine for the past 3 days and I hope it stays that way.
Click to expand...
Click to collapse
You stick it in the oven? Use a heat gun? How hot/long?
tallgrasshawk said:
You stick it in the oven? Use a heat gun? How hot/long?
Click to expand...
Click to collapse
Heat gun, I put aluminum foil at the end of the gun to make it narrow and easy to target just the emmc. Keep it on for around 30sec x 3
How else?
Arrivale said:
Heat gun, I put aluminum foil at the end of the gun to make it narrow and easy to target just the emmc. Keep it on for around 30sec x 3
Click to expand...
Click to collapse
I don't have a heat gun, how else can I heat it? Also, excuse my ignorance, I'm new to phone thing since my Nexus 5x went into bootloop last week I've learned a lot, fast. Where exactly is the EMMC? How else can I heat it? I'm desperate to get this phone working as I just went overseas and Nexus won't send a replacement here
My attempt at the Rescue OTA fails in step 19, I can't get the device state to be "unlocked" does anyone know how to unlock it when the phone is in bootloop? (So all I really have access to is command prompt, which says I can't unlock the oem) HELP!?!
Device is fine and can be used via bluetooth mouse / keyboard - however, touchscreen went completly dead
formatted it - changed image, same result
anyone have any idea how to fix it , like a link to a video - part needed - or even a UK store
thanks
I have a similar issue.
I've had my Pixel C for around 11 Months, purchased direct from the google store in November 2017.
Last week I opened the tablet and the screen was totally unresponsive. The physical buttons were working so after several forced reboots which did not help I went for the Nuclear option and restored the device to factory defaults. This didn't work either and I was still unable to interact with the screen so logged a call with Google. I was about to invoke the warranty when suddenly the device responded again after a further reboot. I agreed with the support person that I would keep it for the time being, hoping it was just a glitch
Unfortunately the problem has recurred twice again and the only way to recover seems to be to power the device off, leave it for a "while" and power on.. not exactly scientific.
Has anyone else experienced similar issues? The device received a security update mid last week so I wonder if this is more than coincidence.
Any road, in this state the device is completely unreliable so I'll be looking to return it. I'm assuming google will not have any new replacements so I need to find an alternative android tablet
touch screen pixel c unreliable
owens2000 said:
I have a similar issue.
Has anyone else experienced similar issues? The device received a security update mid last week so I wonder if this is more than coincidence.
Any road, in this state the device is completely unreliable so I'll be looking to return it. I'm assuming google will not have any new replacements so I need to find an alternative android tablet
Click to expand...
Click to collapse
Same for me. The touchscreen is unresponsive, thought it would be hardware damaged, but did a couple of restarts, and all of a sudden I was able to type ten letters, then unresponsive again. Were you able to resolve this issue? Thanks!
after the last few updates the screen would respond less and less. This last update last night killed the screen completely. Zero response! I honestly think this is an error on their part but even if they fixed it in an update I cant get in to install the update!
I wanted to root and install a custom rom to see if that would fix it but honestly Ive been out of the loop for so long and without going into dev mode Im not sure I can at all.
tevil said:
I wanted to root and install a custom rom to see if that would fix it but honestly Ive been out of the loop for so long and without going into dev mode Im not sure I can at all.
Click to expand...
Click to collapse
I know how you feel. Same here, touchscreen became unresponsive before I could do any settings to flash anything else e.g twrp. Please share your next steps. Thanks
milgrave said:
I know how you feel. Same here, touchscreen became unresponsive before I could do any settings to flash anything else e.g twrp. Please share your next steps. Thanks
Click to expand...
Click to collapse
Im working on trying to unlock the bootloader right now. I tried the toolkit but its giving me a syntax error on trying to flash in fastboot since thats the only thing I can get to. Whats crazy is even the android recovery option is corrupt and this is a stock tablet. I really think google did this to these devices on purpose or unintentionally but has no intention on fixing them. I couldnt even run the update any since there is no way for me to get to anything.
Im looking for instructions on how to do everything from fastboot and ADB but everything is so outdated.
milgrave said:
I know how you feel. Same here, touchscreen became unresponsive before I could do any settings to flash anything else e.g twrp. Please share your next steps. Thanks
Click to expand...
Click to collapse
Hey sorry to post twice but try these. I just tried these steps and got my tablet fully wiped (do caches first) and working. Im enabling USB debugging and bootloader unlock and doing it all now. This was proven to be a google update issue to me.
Perform a master reset
https://thedroidguy.com/2019/08/how...3-xl-touchscreen-not-responding-issue-1094388
To factory reset your Google Pixel 3 XL:
Turn off your Google Pixel 3 XL.
Press and hold the Power+Volume Down buttons until bootloader mode (image of an Android with Start above it) appears, then release.
Select Recovery mode. You can use the Volume buttons to cycle through the available options and the Power button to select. The device will flash the Google start screen momentarily and then restarts in Recovery mode.
If presented with an image of a broken Android with “No Command” printed on the screen, press and hold the Power button. Press the Volume Up button once. Then release the Power button.
From the Android Recovery screen, select Wipe data/factory reset.
Select Yes. Wait for several minutes for the factory data reset process to complete.
Select Reboot system now. Allow several minutes for the factory data reset and reboot processes to complete.
Set the phone up again.
from there I just now used wugfreshs tool kit to unlock the bootloader and Im going to install TWRP and probably a custom rom to avoid updating again.
Update: def a software issue. I worked fine with this tablet for a few hours. Installed 1 app then it locked again. Opera browser. I've had my suspicions of the app for a while which is why I tested this app first. I'm using those same steps again to wipe and seeing if the touchscreen works again. I had trouble getting twrp and a room loaded due to encryption. There is apparently a decrypt file you need to install recovery and root. I can't seem to locate the correct one but wugs toolbox sees the device fine once the drivers are installed.
Ill keep this running and updated with results.
Full wipe and reset again and the screens not working again. What stinks is I once again can't get it into dev mode. I guess maybe it is a hardware issue. Sad, this thing has always been in a case and babied. I still think tho it's a bug with newer releases and the hardware in certain C's. It's beyond warranty though so what can we say to Google at this point. It's not even an old tablet and was pretty pricey. My Nexus 9 still runs perfectly!
I decided to apply heat to the CPU using a heat gun for 15 seconds. It was extremely hot. I tapped the CPU a few times with another object to see if that would help. Once I put my phone back together, the phone finally turned on, however it would not boot.
So while I can actually fire my phone on now without putting it into the freezer and I can even get into recovery without any issue, the phone will not boot into the system. I have completely backed up all of my files, moved around many files, left the phone in recovery for an hour, and successfully flashed several roms in an attempt to boot into the system, none of this has worked. Instead my phone hangs on "life's good", it does not reboot itself, it stays on this screen for an eternity.
I would like to hear any ideas! I want to test updating the bootloader by flashing the stock rom, but I don't remember which firmware I last flashed and this could brick if flashed in the wrong order, does anyone know how to check the firmware? Another idea, is there any way to debug the boot or is there a boot log to see where it is hanging?
Thanks!
RandomUSA said:
I decided to apply heat to the CPU using a heat gun for 15 seconds. It was extremely hot. I tapped the CPU a few times with another object to see if that would help. Once I put my phone back together, the phone finally turned on, however it would not boot.
So while I can actually fire my phone on now without putting it into the freezer and I can even get into recovery without any issue, the phone will not boot into the system. I have completely backed up all of my files, moved around many files, left the phone in recovery for an hour, and successfully flashed several roms in an attempt to boot into the system, none of this has worked. Instead my phone hangs on "life's good", it does not reboot itself, it stays on this screen for an eternity.
I would like to hear any ideas! I want to test updating the bootloader by flashing the stock rom, but I don't remember which firmware I last flashed and this could brick if flashed in the wrong order, does anyone know how to check the firmware? Another idea, is there any way to debug the boot or is there a boot log to see where it is hanging?
Thanks!
Click to expand...
Click to collapse
Just flash V20p, is good to fix and to downgrade from Nougat.
Maybe you didn't heat only the CPU... the audio chip don't like to heated.
Try vol- + Power, when you see the logo release power for a second and press and keep it, maybe you're able to factory reset.
If it doesn't work, take out battery and put it back again, turn on the phone (even if is stuck on LG logo) and leave it for about 10 minutes.
RuedasLocas said:
Just flash V20p, is good to fix and to downgrade from Nougat.
Maybe you didn't heat only the CPU... the audio chip don't like to heated.
Try vol- + Power, when you see the logo release power for a second and press and keep it, maybe you're able to factory reset.
If it doesn't work, take out battery and put it back again, turn on the phone (even if is stuck on LG logo) and leave it for about 10 minutes.
Click to expand...
Click to collapse
I am certain I did not exclusively heat up the CPU, the board is very small and the output of the heatgun is relatively large. Anyway, I couldn't find anything through google that would indicate heating up the audio chip would cause boot issues, if you have any more information on this I would appreciate it.
The vol-+power allows me to get to my TWRP install, I have an unlocked bootloader and TWRP installed as my recovery. I have completely wiped the device before attempting to install various roms. I have not tried installing 20p as it seems you need to be either on 20o or 20p and I am not sure if downgrading is safe (assuming I am on a later version).
I am shooting in the dark even trying to install a new ROM, the one I had should work obviously. I would really like to check what firmware I am on before upgrading/risking permanently bricking the device. Any boot debugging would be extremely useful if possible
RandomUSA said:
I am certain I did not exclusively heat up the CPU, the board is very small and the output of the heatgun is relatively large. Anyway, I couldn't find anything through google that would indicate heating up the audio chip would cause boot issues, if you have any more information on this I would appreciate it.
The vol-+power allows me to get to my TWRP install, I have an unlocked bootloader and TWRP installed as my recovery. I have completely wiped the device before attempting to install various roms. I have not tried installing 20p as it seems you need to be either on 20o or 20p and I am not sure if downgrading is safe (assuming I am on a later version).
I am shooting in the dark even trying to install a new ROM, the one I had should work obviously. I would really like to check what firmware I am on before upgrading/risking permanently bricking the device. Any boot debugging would be extremely useful if possible
Click to expand...
Click to collapse
I got a very delayed boot up when I thought that my problem with one of the microphones was related with bad welding also. So, I heat it (Qualcomm WCD9330 Audio Codec) and it took a lot for the phone 1st boot after that.
The V20p is flashable no matter what version you have before, just need the right "8994.dll" file to be installed without problems. You can extract it from the v20p.kdz.
Good luck!
RuedasLocas said:
I got a very delayed boot up when I thought that my problem with one of the microphones was related with bad welding also. So, I heat it (Qualcomm WCD9330 Audio Codec) and it took a lot for the phone 1st boot after that.
The V20p is flashable no matter what version you have before, just need the right "8994.dll" file to be installed without problems. You can extract it from the v20p.kdz.
Good luck!
Click to expand...
Click to collapse
I might try playing with the audio chip, but there's currently no indication that the phone will progress past the boot screen. Instead of updating my phone via TWRP, I decided to get set up with LGUP following your advice. I have tried refurbish/upgrade without luck. The process seems to complete entirely and successfully, however my phone still hangs on the boot screen. Perhaps noteworthy, at the boot screen the phone is in standby mode and windows identifies the device as "LGE AndroidNet USB Serial Port (COM4)". This is the same as when it is put into download mode.
Do you know if this is normal behavior?
RandomUSA said:
I might try playing with the audio chip, but there's currently no indication that the phone will progress past the boot screen. Instead of updating my phone via TWRP, I decided to get set up with LGUP following your advice. I have tried refurbish/upgrade without luck. The process seems to complete entirely and successfully, however my phone still hangs on the boot screen. Perhaps noteworthy, at the boot screen the phone is in standby mode and windows identifies the device as "LGE AndroidNet USB Serial Port (COM4)". This is the same as when it is put into download mode.
Do you know if this is normal behavior?
Click to expand...
Click to collapse
Try to don't mess with the audio chip!
Turn ON the phone with no cable connected.
Mine have that long boot only the 1st time, after that behaves normally.
Mine when I connect to PC (USB2), option "Only Charge" on the phone and turn ON, is shown in Device manager as "Android device/ Android Sooner Single ADB Interface"
Also as "Device/G4"
After change the option "Only Charge" to "Multimidia Devica (MTP)", is shown as "Android Device/LGE Mobile ADB Interface".
Also as "Portable Device/G4", and, "Modems/LGE Mobile USB Modem".
Of course that until your phone boot completly you can't do any changes...
In "Firmware Update" mode, comes as "LGE AndroidNet USB Serial Port (COM4)" and also as "Modems/ LGE AndroidNet USB Modem".
BTW... you install "LGUSBModemDriver_Eng_WHQL_Ver_4.9.4_All" and "LGMobileDriver_WHQL_Ver_4.2.0" ? Maybe it helps to have those installed before flash.
Maybe it is the same in some devices (also depending on the phone Firmware version) to have those or others but, mine only work with those two installed.
Try this:
Re-flash with LGUP using the v20p again.
After the process is done and the long boot starts (wait 5 minutes or so), take out the battery, let the phone cool down for 10 minutes.
Insert the battery back on the phone and turn it ON.
Leave it until boot finish, go for a walk, watch some TV, forget about the phone.
Of course that if after 30 minutes stills without boot up, you can consider that you have a problem. And me out of ideas... sorry.
Wish you all the best luck on that, regarrds.
RandomUSA said:
I decided to apply heat to the CPU using a heat gun for 15 seconds. It was extremely hot. I tapped the CPU a few times with another object to see if that would help. Once I put my phone back together, the phone finally turned on, however it would not boot.
So while I can actually fire my phone on now without putting it into the freezer and I can even get into recovery without any issue, the phone will not boot into the system. I have completely backed up all of my files, moved around many files, left the phone in recovery for an hour, and successfully flashed several roms in an attempt to boot into the system, none of this has worked. Instead my phone hangs on "life's good", it does not reboot itself, it stays on this screen for an eternity.
I would like to hear any ideas! I want to test updating the bootloader by flashing the stock rom, but I don't remember which firmware I last flashed and this could brick if flashed in the wrong order, does anyone know how to check the firmware? Another idea, is there any way to debug the boot or is there a boot log to see where it is hanging?
Thanks!
Click to expand...
Click to collapse
first of all: what model? we have 11 models for the g4 and not all behave the same way.
second: use SALT. SALT shows your previously installed firmware
third: try flashing custom ROMs instead of STOCK
fourth: I guess you know about http://bit.do/ilapofixg4 ?
.
steadfasterX said:
...
third: try flashing custom ROMs instead of STOCK
...
.
Click to expand...
Click to collapse
Hi @steadfasterX!
I have a question... apart "bugs", what else have a custom ROM that can make a device with hardware issues run better?
I'm asking because I never had/saw a custom ROM working 100%, even without hardware issues, at least on LG.
There's always something that doesn't work, or, with quality/performance issues.
My doubt is, if a device have problems to boot with the firmware that was exclusively made for it, won't have the same or more issues with another one?
In case of faulty hardware, firmware (stock or not) will make any difference?
Don't think that I'm kind of messing with you. I really have those doubts.
Regards
RuedasLocas said:
Hi @steadfasterX!
I have a question... apart "bugs", what else have a custom ROM that can make a device with hardware issues run better?
I'm asking because I never had/saw a custom ROM working 100%, even without hardware issues, at least on LG.
There's always something that doesn't work, or, with quality/performance issues.
My doubt is, if a device have problems to boot with the firmware that was exclusively made for it, won't have the same or more issues with another one?
In case of faulty hardware, firmware (stock or not) will make any difference?
Don't think that I'm kind of messing with you. I really have those doubts.
Regards
Click to expand...
Click to collapse
I do not say a custom ROM is running better... but for debugging issues its easier to run custom ROMs and they do not have many of the dependencies a STOCK ROM has (like several partitions we never need on custom ROMs but on stock) which can prevent from booting.
.
steadfasterX said:
I do not say a custom ROM is running better... but for debugging issues its easier to run custom ROMs and they do not have many of the dependencies a STOCK ROM has (like several partitions we never need on custom ROMs but on stock) which can prevent from booting.
.
Click to expand...
Click to collapse
Thanks for responding! I have a t-mobile h811 variant, LGUP/SALT currently shows my firmware as 20p, I decided to try updating to 20x using lg bridge, but the firmware is still listed as 20p despite the process being completed 'successfully'.
I know that flashing the KDZ worked because it overwrote my recovery and I no longer have access to TWRP. Before flashing the KDZ I tried several ROMS (stock 20p, aokp, lineage OS).
Now the phone is bordering on being a paperweight because I have no means of installing TWRP. I have an unlocked bootloader but there is no way for me to enter the bootloader. Is it possible to repackage a KDZ with a custom boot image or custom recovery?
Before flashing the KDZ and losing access to TWRP, I tried modifying the system boot.img to limit the number of cores that could be used to 4, and even 2 cores without any luck.
Right now, I don't think the phone has any bootloop issue or heat related problem because powering on the phone has become perfectly functional, the phone does not reboot itself (just stays at "Life's Good" with the blue blinking LED), recovery worked fine and handled a lot of load for hours reaching 40C+ on the CPU and with no issue.
Hi guys,
I attached my brand new Galaxy S20 Ultra to my PC and started Smart Switch today. The Software showed an update for my device so I downloaded it and started the update process. Unfortunately, Smart Switch got stuck during the update process at 68%. Nothing happened, cables and all still attached. It just didn't proceed any further for hours.
I decided to take the path of stopping the process, using the key combination shown on my device. It now said, recover your device software with Smart Switch Emergency recovery function. I started this and guess what: it also stopped at 68%.
I "rebooted" the device (volume down + power for approx. 10 seconds) and it starts again in recovery mode.
I manually filled in the recovery code and it seemed like Smart Switch was downloading the OS again. Started the recovery process and it is stuck at 68% again.
Now I am just super afraid that I bricked the device by using Samsungs original software.
Anyone her to help or have similar experiences?
Thanks for any advice on how to proceed.
Julius
What exactly were you trying to do? I mean normally you hook up old phone and use smart switch to update new phone. So why was you connected to a PC? It does sound like you bricked it.
So now you probably need to flash the ROM.
I read that smart switch is a good and valid source to check for updates. I never thought that an official Samsung software can be so bad at something so basic, resulting in bricking my phone...
Stop using smart switch to update your phone. You haven't hard bricked it because you still have recovery. It's called a soft brick. Download Odin 13.3_3B from here on xda. Do not use the 13.4 because it's suspected to have a fishy call back to a server from a dll that's in the program folder. Download the atch firmware for your model from sammobile or get it in this s20 ultra forum. You should be able to flash the new firmware.
Thanks @freebee269. Does flashing the firmware with Odin void my warranty or does this only count for rooting devices? (Sorry for stupid questions)
Julius_GER said:
Thanks @freebee269. Does flashing the firmware with Odin void my warranty or does this only count for rooting devices? (Sorry for stupid questions)
Click to expand...
Click to collapse
Odin uses official firmware from Samsung so no warranty voided.
Julius_GER said:
Hi guys,
I attached my brand new Galaxy S20 Ultra to my PC and started Smart Switch today. The Software showed an update for my device so I downloaded it and started the update process. Unfortunately, Smart Switch got stuck during the update process at 68%. Nothing happened, cables and all still attached. It just didn't proceed any further for hours.
I decided to take the path of stopping the process, using the key combination shown on my device. It now said, recover your device software with Smart Switch Emergency recovery function. I started this and guess what: it also stopped at 68%.
I "rebooted" the device (volume down + power for approx. 10 seconds) and it starts again in recovery mode.
I manually filled in the recovery code and it seemed like Smart Switch was downloading the OS again. Started the recovery process and it is stuck at 68% again.
Now I am just super afraid that I bricked the device by using Samsungs original software.
Anyone her to help or have similar experiences?
Thanks for any advice on how to proceed.
Julius
Click to expand...
Click to collapse
What kind of USB Port did you use?
Try again using a USB 2.0 port, Samsung always had problems with it's software and USB 3.0 ports.
Use USB 2.0 and try again.
Hi guys, i have a similar problem as (xReem).
Attached my GT SM-T515/10.1 tab to smart switch where the software was unable to recognise my device!? Was advised to use the Emergency Code function but i have no code due to backing up my data to sd card! I have Magisk and TWRP installed where my device was working beforehand, but since attaching to smart switch, my device is now totally "dysfunctional"!!!
Error message as follows...
...An error as occurred while updating the software. Use the Emergency Recovery function in the Smart Switch PC software. ...
Like i sad, i have no code!!!
I am able to get to the device unlock choice screen and if i choose to restart, my device always boots to the Smart Switch Emergency Code screen?! If i choose the device unlock or download screens, both screens are accessible! Tried to flash my original firmware (BTU-T515XXU3ASK5-20191224095700) using Odin3_v3.14.1 and twrp-3.3.1-6-T515XXU3ASK5-20200215 with no joy (Fail!)
Although i'm totally @"#$%* off about this, as its a new device, i am also curious if someone has ever cracked this... 'Smart Switch No Code' problem before. Hmm...
Anyways, any help appriciated...
Oh! Cannot access recovery at all...
Any help appriciated.
klantee said:
Hi guys, i have a similar problem as (xReem).
Attached my GT SM-T515/10.1 tab to smart switch where the software was unable to recognise my device!? Was advised to use the Emergency Code function but i have no code due to backing up my data to sd card! I have Magisk and TWRP installed where my device was working beforehand, but since attaching to smart switch, my device is now totally "dysfunctional"!!!
Error message as follows...
...An error as occurred while updating the software. Use the Emergency Recovery function in the Smart Switch PC software. ...
Like i sad, i have no code!!!
I am able to get to the device unlock choice screen and if i choose to restart, my device always boots to the Smart Switch Emergency Code screen?! If i choose the device unlock or download screens, both screens are accessible! Tried to flash my original firmware (BTU-T515XXU3ASK5-20191224095700) using Odin3_v3.14.1 and twrp-3.3.1-6-T515XXU3ASK5-20200215 with no joy (Fail!)
Although i'm totally @"#$%* off about this, as its a new device, i am also curious if someone has ever cracked this... 'Smart Switch No Code' problem before. Hmm...
Anyways, any help appriciated...
Oh! Cannot access recovery at all...
Any help appriciated.
Click to expand...
Click to collapse
Did you ever get things working ? If not, when you flashed with Odin - did you use the PATCHED Version ? THis is necessary when flashing firmware via Odin on the S20 Ultra.....
You can download Odin 3.14.1_3b here: https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Be sure to download the PATCHED version of 3.14.1_3b (it is located as an attached file at the bottom of the first post in the OP at the link above. Hope this helps.
Geekser said:
Did you ever get things working ? If not, when you flashed with Odin - did you use the PATCHED Version ? THis is necessary when flashing firmware via Odin on the S20 Ultra.....
You can download Odin 3.14.1_3b here: https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Be sure to download the PATCHED version of 3.14.1_3b (it is located as an attached file at the bottom of the first post in the OP at the link above. Hope this helps.
Click to expand...
Click to collapse
No, to answer your first question, and yes used the patched version of Odin you state but with no joy.
(would another version of Odin be better for my device model?)
I just need to find a way to flash the original stock recovery. Having the TWRP installed as mentioned earlier is blocking my path, and I have now tripped knox! So no more options available to access the unlock oem screen. Now frp is off, oem is on!
Also, I was wondering if anyone had thought about a totally updated version of the old "ALL IN ONE TOOL" which was available for some earlier makes of phone devices? I think due to manufacturers security upgrades of today's phones we could all do with something like this?
I heard you can do a NAND/Reset wipe via the Odin options screen which would allow you to install a new rom???
Oh, my predicament was based on Julius's post, not xReem. Sorry for the confusion.
klantee said:
No, to answer your first question, and yes used the patched version of Odin you state but with no joy.
(would another version of Odin be better for my device model?)
I just need to find a way to flash the original stock recovery. Having the TWRP installed as mentioned earlier is blocking my path, and I have now tripped knox! So no more options available to access the unlock oem screen. Now frp is off, oem is on!
Also, I was wondering if anyone had thought about a totally updated version of the old "ALL IN ONE TOOL" which was available for some earlier makes of phone devices? I think due to manufacturers security upgrades of today's phones we could all do with something like this?
I heard you can do a NAND/Reset wipe via the Odin options screen which would allow you to install a new rom???
Oh, my predicament was based on Julius's post, not xReem. Sorry for the confusion.
Click to expand...
Click to collapse
Sorry for your troubles - wish I could help you but you have done everything I would have tried. Maybe, if you haven't already done this - leave the phone on until the battery runs out completely. Then, recharge the phone for a while so the battery has some juice again and then get the phone back into download mode by pressing volume up and volume down at the same time - then plug in the USB - it shoul.d launch into download mode again - then try flashing again with the patched odin.
If you have already done this - then I don't know how what else to suggest.
I wish you luck and hope you are able to get things working again.
Geekser said:
Sorry for your troubles - wish I could help you but you have done everything I would have tried. Maybe, if you haven't already done this - leave the phone on until the battery runs out completely. Then, recharge the phone for a while so the battery has some juice again and then get the phone back into download mode by pressing volume up and volume down at the same time - then plug in the USB - it shoul.d launch into download mode again - then try flashing again with the patched odin.
If you have already done this - then I don't know how what else to suggest.
I wish you luck and hope you are able to get things working again.
Click to expand...
Click to collapse
Thanks for the advice. I'll try what you suggest and see what happens. Stay well!
Julius_GER said:
Hi guys,
I attached my brand new Galaxy S20 Ultra to my PC and started Smart Switch today. The Software showed an update for my device so I downloaded it and started the update process. Unfortunately, Smart Switch got stuck during the update process at 68%. Nothing happened, cables and all still attached. It just didn't proceed any further for hours.
I decided to take the path of stopping the process, using the key combination shown on my device. It now said, recover your device software with Smart Switch Emergency recovery function. I started this and guess what: it also stopped at 68%.
I "rebooted" the device (volume down + power for approx. 10 seconds) and it starts again in recovery mode.
I manually filled in the recovery code and it seemed like Smart Switch was downloading the OS again. Started the recovery process and it is stuck at 68% again.
Now I am just super afraid that I bricked the device by using Samsungs original software.
Anyone her to help or have similar experiences?
Thanks for any advice on how to proceed.
Julius
Click to expand...
Click to collapse
Hey Julius, did you get your phone to work. I am having the same issue.
Update:
I am good now. I was using the thunderbolt cable that came with the phone and update would get stuck at the same point everything with odin 3.13 and 3.14.
I used a USB 3 to thunderbolt cable that I had from an older phone and it work.
What I used:
Windows 10 x64 1909
USB 3 to thunderbolt cable
USB driver downloaded from Samsung support. I think it is the same driver that comes with smart switch because when I installed it, it prompted
to reinstall driver.
Odin3 v3.13.3_3B_PatcheD from here https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572. ( I think 3.14 will work too.
I really think the cable was the only problem)
Firmware downloaded with SamFirm
klantee said:
Thanks for the advice. I'll try what you suggest and see what happens. Stay well!
Click to expand...
Click to collapse
Open Odin as administrator and if using a stock AP file always use the HOME-CSC of the same firmware in CSC slot. Sometimes Odin plays the fool and gets stuck.
ASHLEY117 said:
Open Odin as administrator and if using a stock AP file always use the HOME-CSC of the same firmware in CSC slot. Sometimes Odin plays the fool and gets stuck.
Click to expand...
Click to collapse
Wow! This nearly worked!!!
Managed to get a (((PASS))) on Odin and my tab actually rebooted into the Samsung logo!!!
Soon after this though tab immediately Boots back into download mode??? Tried the same steps but without any progress???
I feel I'm close to cracking this but need some more advice on how to build on such "progress"!?
Many thanks for your advice...
klantee said:
Wow! This nearly worked!!!
Managed to get a (((PASS))) on Odin and my tab actually rebooted into the Samsung logo!!!
Soon after this though tab immediately Boots back into download mode??? Tried the same steps but without any progress???
I feel I'm close to cracking this but need some more advice on how to build on such "progress"!?
Many thanks for your advice...
Click to expand...
Click to collapse
Try with all slots filled but with CSC file not HOME-CSC. That may help as it flashes pit file to factory reset
ASHLEY117 said:
Try with all slots filled but with CSC file not HOME-CSC. That may help as it flashes pit file to factory reset
Click to expand...
Click to collapse
Tried your suggestion with no joy. Will keep trying though as I feel this issue can be cracked. Many thanks...
Geekser said:
Sorry for your troubles - wish I could help you but you have done everything I would have tried. Maybe, if you haven't already done this - leave the phone on until the battery runs out completely. Then, recharge the phone for a while so the battery has some juice again and then get the phone back into download mode by pressing volume up and volume down at the same time - then plug in the USB - it shoul.d launch into download mode again - then try flashing again with the patched odin.
If you have already done this - then I don't know how what else to suggest.
I wish you luck and hope you are able to get things working again.
Click to expand...
Click to collapse
(((SUCCESS)))!!! :laugh::laugh::laugh:
Done what you suggested by waiting until my battery ran out!
I downloaded a different software version and as soon as I plugged my tab into my PC with USB, i flashed the new software with no problems!!!
Flashed TWRP, Magisk and Multidisabler problemless the same!
The lesson learnt here...
...(ONLY FOR THOSE WHO KNOW WHAT THEY ARE DOING)...
...is to probably only have 30% battery when flashing!!! This way you won't have to wait weeks for such a large capacity battery to run down, like I did!
I knew I'd crack it!
klantee said:
(((SUCCESS)))!!! :laugh::laugh::laugh:
Done what you suggested by waiting until my battery ran out!
I downloaded a different software version and as soon as I plugged my tab into my PC with USB, i flashed the new software with no problems!!!
Flashed TWRP, Magisk and Multidisabler problemless the same!
The lesson learnt here...
...(ONLY FOR THOSE WHO KNOW WHAT THEY ARE DOING)...
...is to probably only have 30% battery when flashing!!! This way you won't have to wait weeks for such a large capacity battery to run down, like I did!
I knew I'd crack it!
Click to expand...
Click to collapse
Glad I could hel;p- I know how frustrating it is when things seem like you can never get things to work - anyway - best of luck - and be sure to hit thanks If I helped you.
Hi Do you lose your data (vids and pics) via this method? i have had same thing happen on my s20+