Hello all!
I recently got gifted a Samsung Galaxy Z Fold4 and it's one of the nicest phones I've had. I am not sure why I can't find any info online about this phone or the topic on this forum but I am in search of some answers. I don't know how I got to this state but I broke the phone.... I was playing around installing some apk games when all of the sudden one of them didn't install. I searched for the app but it was nowhere in sight. I am not sure if the phone is virused(after countless factory resets) but it started behaving really weirdly after. No apps where loading(it was just an infinite loading screen), when I tried to log in into apps it was nearly impossible because of the infinite loading which after some time turned into an "operation failed" screen. After I factory reset the phone, I noticed even stranger behavior. The "Getting your phone ready" screen was taking ages and sometimes even failing. then, when I tried to log in with iCloud in smart switch, I would get blocked by an infinite loading which required a restart. The first time I fixed the phone by going into the boot screen(or however it's called) by connecting to a PC and then erased cache partition and factory reset. This seemed to fix the phone. Fast forward some time later, I was messing with another game apk when the same thing happened again but this time, the previous solution was tried but to no avail. Now I am stuck with a bricked phone which is slower than a Nokia and sometimes it even fails completely. Also tried booting into bootloader but the phone would just restart itself and not work. I am in desperate need of help since I can't see this brick on my desk getting dustier day by day. I can provide all the info needed if necessary.
I'm sorry if this is the wrong topic or not the right place. I am new to this community.
Thanks in advance
My first question is have you tried to reflash the stock firmware with ODIN? see if that fixes any issues.
secondly, why install dodgy apks twice? once should have been the warning needed.
Related
Hi Guys,
I was trying to install a custom rom on my galaxy tab.I downloaded Rom Manager from market and was trying to take backup by booting my phone and tried to take Nandroid backup but not able to find that when I rebooted my tab.So i tried to find a app on market by searching "nandroid" and found 3 apps as a search result and I downloaded 3rd app from market.
After that I rebooted my tab and It is not coming up.It is showing samsung startup screen and then screen is active but not showing anything and keep on vibrating in every few seconds.I am not able to see anything on my screen now but I can get reboot screen with options like:-
reboot
clear cache data
wipe out all data
Please let me know what should I need to do to get my tab up and running... Its very urgent...
Thanks in advance
I'm having the same issue w/ my HTC Thunderbolt (ADR6400). I followed the directions and used the files referenced in the forums here. This is the "Easy Flash" app method. I did have the 605.6 software on the device stock from HTC. I was initially not able to get past step one (it would not actually write the files. After trying it about 5 times, it finally flashed and rebooted on its own and installed the old 1.03.605.10 software. It took a long time to finally boot back up, and now every time I try to connect it via USB w/ Debugging Mode on to do steps 2 and 3 it crashes the device and like Survivor's Tab situation, gets stuck w/ the boot-up screen
Is there a way to either A) get around this crashing-on-debugging-mode issue to finish the rooting, or B) restore it to its original firmware? At least it turns on, but I posted in this thread since the solution for him is probably the same as for me (whatever that might be). I've rooted other Linux-derived OSes before (Ie, WebOS 1.4x), and didn't have these kinds of issues. Any ideas would be most helpful to both of us.
Like so many others, my phone spontaneously developed the infamous bootloop problem. I've had the phone for less than a year, so Sprint will replace the phone for free, but I have a lot of things stored on internal memory of the device that I would very much like to retrieve before the exchange.
I've tried freezing it and heating it--both techniques succeeded in getting the phone to boot up, but not long enough to do anything other than confirm that all my data is still there.
I've been searching the web and this forum and found the guides about disabling big cores, but it seems that the files do not apply to my version of the phone, the LS991. Other guides describe booting the phone into recovery mode or fastboot/download mode, both of which I've done successfully, but I haven't been able to find out what to do from there. ADB only seems to recognize the phone is there when it's in "sideload mode."
Yes, I rooted my phone shortly after I got it, but I don't have any custom recovery installed because at the time, and apparently still, there aren't any available for this model!
So here I am with a phone that has my data on it but won't boot, and all the solutions beyond extreme temperature and hope are unavailable for this version.
Am I missing something? Is there a reason that a chunk of the population facing this growing problem have been left without the means of doing anything about it? Has someone produced the tools (either a custom recovery or a big cores disabling file) and I just can't find them anywhere?
Again, I'm not the first to ask, but I'm asking anyway. If anyone knows something that would help, please speak up!
Hi guys
I love my Pixel C. It's fast and huge, and will run pretty much everything
That is until recently, when subsystems started to misbehave: I couldn't get sound on my movies unless I rebooted and the microphone was ignored
The Nougat 7.1.1 update had been waiting for a few days so I let it download and install. There was no perceptible difference except that my WiFi, which had been stable, started dropping out every five minutes
I cleared things out, as I had accumulated 55GB of unwanted apps and data, and rebooted to no effect
So I went for a reset from the settings menu. That never terminated after three hours of waiting
I rebooted into the bootloader and tried the factory reset from there. That was a little more promising, but it hung in the boot animation
I have an image of the latest v7.1.1 to install, but I can't find a way to access my tablet from adb, so basically I'm stuffed, right before Christmas
Does anyone have any insight on this?
Borodin said:
Hi guys
I love my Pixel C. It's fast and huge, and will run pretty much everything
That is until recently, when subsystems started to misbehave: I couldn't get sound on my movies unless I rebooted and the microphone was ignored
The Nougat 7.1.1 update had been waiting for a few days so I let it download and install. There was no perceptible difference except that my WiFi, which had been stable, started dropping out every five minutes
I cleared things out, as I had accumulated 55GB of unwanted apps and data, and rebooted to no effect
So I went for a reset from the settings menu. That never terminated after three hours of waiting
I rebooted into the bootloader and tried the factory reset from there. That was a little more promising, but it hung in the boot animation
I have an image of the latest v7.1.1 to install, but I can't find a way to access my tablet from adb, so basically I'm stuffed, right before Christmas
Does anyone have any insight on this?
Click to expand...
Click to collapse
Hello,
I will move your thread to the right section where experts will be able to assist you.
Regards
Vatsal,
Forum Moderator.
@Borodin
Try this command from bootloader: fastboot continue
I've also posted this on Reddit and the OnePlus forums, but I'm hoping I can find an answer here, too.
Long story short: I really messed up my phone and I'm looking for help getting it to at least boot into the system. Lots of weird, confusing things have happened within the past few days, so bear with me; might be a long story, but I'll try to give you the abridged version.
I run locked and unrooted. I flashed OOS Beta 3 over 4.7.6 on my 5T, wiped my cache, and everything was wonderful for a week. Then one day, I got a system message saying "Bluetooth has stopped". I cleared that and thought nothing of it, but I got another message saying "Bluetooth keeps stopping". This message would actually pop up (with no exaggeration) every second. I could only stop the messages completely after going to the Bluetooth app and clearing the data, then disabling Bluetooth Scanning.
I figured the problem would fix itself, but the next day when I tried to connect to my car via Bluetooth, my phone would freak out again like the previous day. I had to listen to a CD like it was 1996. I thought I could fix the problem with a Factory Reset. As soon as I hit the Welcome screen, "Bluetooth has stopped". When I went to check the Storage section of the Bluetooth app in the Applications list, the app portion read 0 bytes. What? Even when I went into Settings --> Bluetooth and tried to turn it on, nothing would happen. I thought maybe I should revert back to 4.7.4 and start from the very beginning.
That served no purpose. The Bluetooth symbol did show temporarily in the Status bar as I was setting up my phone, but eventually disappeared, with the Bluetooth app once again taking up a whopping 0 bytes. I've done various combinations of installs, but I cannot get Bluetooth to function normally. And at some point, my phone developed a new problem: any time I hit the Bluetooth button in Quick Settings, the phone would eventually reboot on its own. Later, it wouldn't need any input from me at all. It would just be sitting in the Lock screen and reboot.
Icing on the cake: I got desperate, unlocked the bootloader, deleted the system and cache partition in fastboot, then wiped the data in Recovery with the hope that doing a completely fresh install would fix the problem, but at some point my internal storage got wiped and now I have no ROM on my phone to install. Even better: I'm having some real problems trying to install OOS (any version) on my phone via ADB sideload. I keep getting the message "cannot read <filename.zip>", even though it's in the correct folder.
I am currently back on my OnePlus 3 and the proud owner of a very sleek brick. I used to root and unlock Nexus devices and Moto X's, so I'm pretty embarrassed that I managed to ruin my phone while it was running (basically) all stock. It can still boot into Bootloader and stock Recovery. Is there anything at all that I can do to at least load OOS (or any ROM)? Do I have to send it back to OnePlus and beg for a replacement? Will they even take this phone in it's current state? Am I just SOL?
I've run out of ideas and patience. I'm really hoping someone out there can help me. At the very least, thanks for reading my long sob story. Hopefully this never happens to you.
try flash orero based twrp and flahs stock 5.0.3 zip in twrp, see if it works. then figure out the reset.
Why would you delete system from fastboot? Does people not formating partition from recovery more often？
The twrp I use
https://forum.xda-developers.com/oneplus-5t/development/recovery-twrp-3-2-1-0-oreo-8-0-8-1-t3729673
Update: I managed to unbrick my phone using an unbrick tool. The process was pretty painless and it will revert your 5T back to OOS 4.7.4 no matter what you did to it. Props to Drasm19 from the OnePlus forums and the geniuses behind this tool! Funnily enough, I was ultimately led back here:
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012
You guys more than likely already knew about this tool, but definitely keep this in mind if you manage to brick your phone like I did.
Now I'm back to my original problem: Bluetooth is really messed up. This is what I'm talking about:
https://imgur.com/gallery/eEkbX
No matter what I do, no matter how many times I flash any version of OOS, this is always the result. As you can see, even with the toggle in the "on" position, Bluetooth refuses to do what it's supposed to do and the app takes up 0 bytes. Something is up...
I've searched a lot of threads that reference Bluetooth issues, but it looks like I'm the only one with this problem. I'm open to any and all suggestions that'll help me solve this and get back to using my 5T. I already miss those awesome navigation gestures.
Thanks again for your time and help.
im not really a developer type, but a while back it was easy to root and un root with kingo. and i could put things in the system with FX. please bare with me a sec.. p9's i like, but getting some glitches. when the gboard went byby, on reset, i had to set up my welcome screen by shouting at the phone.. 'at sign' does give you @ but to get capitals you have to trick it, eg. 'USA' to get an upper case 'u'
anyway, i got in, and got gboard from 'my apps' ..fine but of course, wont survive another reset.
so about the missing bluetooth.. iv got the directory info. and the missing files. thanks ..but i didnt want to wipe the phone, it seems rooting has become a can of worms.
wouldnt it be nice if there was a nice (no root) app , to run bluetooth from the apps ? so that 'joe blow' doesnt have to throw his phone away, cos it doesnt work in the car ect.. thanks
Hi everybody I am new here so I apologize for my lack of knowledge.
This past Sunday evening I attempted an OTA update on my Verizon S10+. Upon the phone restarting post-update it went into a reboot loop. I have tried everything I am capable of and cannot get it out of the loop. I can access the recovery menu (may not be correct term) and have cleared the cache partition, attempted to "fix apps". Also have attempted to launch in safe mode, also have let the phone go totally dead and restart, but still looping.
Here is the issue, I am fairly certain a factory reset would fix it, I found maybe one or two people with this exact problem after this most recent March update. They said factory reset worked. However, I have some pictures on the phone's internal storage that is not backed up anywhere. I know, very stupid of me to not have been backing up, I should know better.
Last night was my final attempt at a fix that hopefully wouldn't wipe my pictures. I attempted (and I thought I succeeded) to flash the March update to the phone using Odin. Hoping that might result in a successful install of the update and resolve the issue.
No change after flashing the phone. I don't know what to do to try to save those pictures, I was wondering what would happen if I waited for the next update and then tried to flash that to the phone using Odin.
I'm at a loss, you all seem very knowledgeable and helpful and I am already appreciative of the help I have found in past threads here. Any suggestions/thoughts would be great.
Thanks,
Sam
@hainguyenthao Just generously spent a solid hour and a half helping me. It appears I did not flash my phone correctly and/or the data on my phone was already toast after the initial OTA update failure that caused the reboot loop.
Fixed by @hainguyenthao even though I screwed up my own data. Phone is working again!