Just switched to this phone from a ZenFone 2 and I love it. Unlocked the bootloader and installed LOS14.1 almost immediately after getting it in my possession.
However, I've been having issues with Sync.Me.
Every time it gets to the screen where you enter your number, it doesn't progress past "Please Wait..." after clicking continue. I went back to stock to see if it was the app at fault, but it worked flawlessly.
Related
This has happened twice in the almost 2 weeks that I've had the phone (most recently today).
I'm on T-Mobile and rooted using the GS3 Toolkit v1.0 and the "ALLINONE [Flash Insecure Boot, CWM, Root phone + Install Busybox]" option. I can't remember if the first time it happened was before or after this, but I think before.
So, most recently, I opened Contacts, scrolled down, opened a contact, then the phone became unresponsive. After a about 5 seconds, the screen briefly went black, back to the home screen, and mobile data was along with cell signal. Those came back up after a couple seconds and everything worked fine. At no point did I receive a popup about an application needing to close.
Anyone else experience anything like this with their GS3 or another phone? Just wondering if I need to get a replacement or just ignore. Or maybe flash a new ROM if it's software and not hardware.
So here's the story.
I have a Note 3 I acquired that was in pretty rough shape. According to the person that gave it to me, they had tried to flash a rom that was unstable and crashed the device causing a boot loop he couldn't recover from. So he reported it lost and got a new one.
The first thing I tried was installing stock firmware using odin. This at least allowed the phone to fully boot up. But, it would still restart after about 10 mins of usage. The next thing I tried was flashing TWRP on to the phone and doing a complete wipe of the phone. Then I flashed the stock firmware using odin.
This has brought the phone more or less back to a usable state. However, there are new problems.
The phone reboots at random. Usually after being on for an hour or longer. Also, the phone won't power down. When I long press the power button and select power off, the screen shows that it's powering down. The phone stays on the power down screen for about 2 mins then the phone reboots.
I've tried a factory reset and reflashing the stock firmware.
Also, since the phone was reported lost it's been black listed. So if anyone has a program I can use to generate an IMEI number that would be helpful.
Your phone is blacklisted. Trying to obtain an IMEI number for it is illegal, fraudulent and against xda rules. Reported.
All true but go easy on the dude. I'd never heard of blacklists til a month ago. We all gotta learn [emoji56]
Sent from my SM-N9005 using Tapatalk
Thread closed for the reasons stated in post #2
tl;dr at the bottom
Alright so I'm out of ideas on how to fix this phone, couple of days ago my mom came to me complaining that her S5 was giving her trouble. When she handed me the phone, it was in a bootloop of showing the Samsung Galaxy S5 screen, playing the theme and vibrating afterwards then rebooting. I took out the battery and tried to power it on, it ended up successfully booting into android. So from here, I figured there must have been some malware on the device, I downloaded Malwarebytes from the Google Play Store and ran a scan on the device. However in the middle of scanning, the device turned off it's screen and rebooted. (Malwarebytes found 2 malware on the device at that point) So now I'm convinced it's most likely malware and eventually removed all the detected malware on the device. I gave it back to my mom thinking it was fixed.
Moments later she came back saying that it's still giving issues, my first thought "wdf, it was working wasn't it?". I looked at the phone again, and tried to wake up the device using the power button. The 2 soft keys at the bottom lit up however the screen was still black. At this point, the phone was still working fine, the only issue was the screen wouldn't wake up. So I decided to do a battery pull once again to reboot it and it results in the bootloop once again. I did some googling and found various solutions to this, one of them involved wiping the cache from recovery, so it tried it. Booted into recovery and wiped the partition cache (i think that was it), after it wiped and was about to reboot, I noticed a brief "error icon" just before it rebooted. After this point I could not boot into recovery at all (it would just show a black screen and I would assume that the phone turned off) and it was still in a bootloop. It was only after trying to turn on the phone after trying to boot into recovery that the idea of the phone wasn't off and the screen was just black entered my mind. (Because usually if the phone is off, you can turn it on by holding the power button, the phone would not turn on until after a battery pull)
So at this point, it was late at night and I was tired. I left the battery out and just went to bed. The next day I tried to turn it on again and to my surprise it booted up fine but I was skeptical. I had a theory that the device would work fine as long as the screen remained on, so I set the screen timeout to 10 minutes and kept it on for probably 30 minutes while I continued to google. Since it stayed working during that period of time, I thought perhaps locking the device triggers the issue. I turned of "Power Button instantly locks device" and proceeded to turn off the screen using the power button. When I tried to turn it on, it was back to the same problem (black screen, device is working fine, soft keys lit up). I did a battery pull once again in an attempt to reboot and now it was back to problem #2 (boot loop, can't enter recovery). At this point in time, I considered doing a factory reset but since I couldn't enter recovery, I'd most likely have to re-flash the stock firmware.
Since I didn't have much experience flashing android devices (I personally only flashed 2 or 3 devices ever, all of them were successful but I still didn't really trust myself), I had it sent to a local cellphone company and had them try to fix it. Eventually I got the device back, but they were unable to fix the problem (they tried to flash a stock and custom rom). Now I'm back to square 1, the phone is still in a bootloop, no sound, no vibration this time, I don't have much experience with phones since I've only owned 2 in my life. The phone seems to be soft bricked pretty good, I've still got 1 more trick to try (full stock firmware flash) before I call it quits, any ideas?
tl;dr
- device is stuck in a bootloop (issue 1)
- i was able to enter recovery mode once, now it's not accessible
- download mode is accessible
- the device has been able to boot successfully a couple times, but then it has another issue.
- device's screen would not wake up after turning off, softkeys still worked, everything else still worked. (issue 2)
- the device was sent to a local phone repair company to fix (unsuccessful)
- currently device is stuck on issue 1
additional notes
- device has not been dropped or wet
- device has been owned for more than a year without problems
- this problem was recent (3 days)
- no sd card
- dark screen was turned off
theories
- screen could be malfunctioning or defective somehow, but then if it can show the bootscreen and download mode screen fine it seems unlikely also since it's been working fine for over a year
- it's a software issue of some sort, but has already been flashed by local phone repair to no success, then again I'm assuming they just did a basic recovery flash and called it quits
I would like to share my experience on how I saved my Nexus 6P which was bootlooping with bootloader locked and inaccessible recovery mode.
The problem started when I had updated my phone with latest OTA update 8.1.0 (Oreo). While I was browsing fb after the update, suddenly the phone froze and restarted. And ever since that moment it begun to bootloop. I tried to access recovery from Fastboot so that I can clear the cache which would most of the time resolve the bootloop issue however this time around I was unable to go to the recovery mode too. I wouldn't been able to flash from fastboot since bootloader was locked. There is no way to get around this unless I would be able to load the OS and go into Developer option to turn on "Enable OEM unlock" in the settings.
Since I would not be able to flash the stock ROM or get into recovery mode, I contacted Google support for help. They directed me to Huawei Support. Huawei told that since my phone is out of 1 year warranty they would not be able to service this phone and would cost me nearly $400 for getting me a replacement. Spending $400 for 20 months old phone was absurd.
I started to explore online what are the options available given the tight situation that I was into. I came across few forums discussing about using a heat gun above the finger print sensor to throttle the CPU which may stop the phone from bootlooping. I used a hair dryer to heat the phone while the phone is continuously bootlooping. I would heat for about 7 - 10 mins to an extent where I would not be able to hold the phone anymore. After nearly 7 to 8 failed attempts spread over 2 weeks, the magic worked.
The last attempt was slightly different. Here is what I did -
1. Battery was fully drained
2. I started to charge the phone while I kept it outside my window for about 20 mins. Temp outside was around 15 degrees Fahrenheit. (Did this step since I read somewhere that keeping the phone in refrigerator and restarting would resolve bootloop issue) However it continued to bootloop.
3. While the phone continued to bootloop, I allowed the phone to charge overnight.
4. Next day I saw that the phone did not restart like how it used to. It was stuck at GOOGLE and would not restart.
5. I disconnected from the charger. Went to fastboot and switched off the phone.
6. I started to heat the phone using hair dryer with the phone switched off for about 10 mins. I held it was a cloth since it gets hot pretty fast.
7. Paused for a sec, turned on the phone (it was bootlooping) and continued to heat the phone for another 5 mins. (by then I gave up)
8. Stopped heating. I left the phone and went out to work on something else. After half an hour, when i returned I saw that the phone was completely switched off and was not bootlooping. I got excited since I know that the phone was fully charged overnight and there is no way that the phone would have died due to battery drain.
9. I immediately turned on by holding on to the VOL down button. I selected recovery from fastboot. To my surprise for the first time in 2 weeks I was able to go into recovery mode. I cleared cache and restarted the phone in Normal mode.
10. Phone booted properly and loaded the OS.
11. First thing I did was to go into developer options and turn on "ENABLE OEM UNLOCK" option. (By now I knew how important it was to have this enabled. THIS COULD SAVE YOUR $549 PHONE!!)
12. Took a backup of all the files and unlocked the bootloader.
I downgraded the OS to 7.1.2 (Aug release) which I felt was a stable one for Nexus 6P. I also did a h/w check and all the tests passed CPU / Memory is fine. I am still not sure what could have caused the bootloop but the fact that it happened after the Oreo OTA would make me to stay away from upgrading the Android version beyond 7.1.2.
Working but not enough
Hey, first thank you so much for sharing your experience. It gave a guide to follow step by step which I really appreciate. I have tried the heating tecnique and has partially worked 3 times, google logo turns into the other google logo but at a really low speed, then it switches off my phone. I tried to start on Safety Mode as you said but it just says "Not command" nex to an android icon. Any aditional advice?. Thank you
Speed1908 said:
I would like to share my experience on how I saved my Nexus 6P which was bootlooping with bootloader locked and inaccessible recovery mode.
The problem started when I had updated my phone with latest OTA update 8.1.0 (Oreo). While I was browsing fb after the update, suddenly the phone froze and restarted. And ever since that moment it begun to bootloop. I tried to access recovery from Fastboot so that I can clear the cache which would most of the time resolve the bootloop issue however this time around I was unable to go to the recovery mode too. I wouldn't been able to flash from fastboot since bootloader was locked. There is no way to get around this unless I would be able to load the OS and go into Developer option to turn on "Enable OEM unlock" in the settings.
Since I would not be able to flash the stock ROM or get into recovery mode, I contacted Google support for help. They directed me to Huawei Support. Huawei told that since my phone is out of 1 year warranty they would not be able to service this phone and would cost me nearly $400 for getting me a replacement. Spending $400 for 20 months old phone was absurd.
I started to explore online what are the options available given the tight situation that I was into. I came across few forums discussing about using a heat gun above the finger print sensor to throttle the CPU which may stop the phone from bootlooping. I used a hair dryer to heat the phone while the phone is continuously bootlooping. I would heat for about 7 - 10 mins to an extent where I would not be able to hold the phone anymore. After nearly 7 to 8 failed attempts spread over 2 weeks, the magic worked.
The last attempt was slightly different. Here is what I did -
1. Battery was fully drained
2. I started to charge the phone while I kept it outside my window for about 20 mins. Temp outside was around 15 degrees Fahrenheit. (Did this step since I read somewhere that keeping the phone in refrigerator and restarting would resolve bootloop issue) However it continued to bootloop.
3. While the phone continued to bootloop, I allowed the phone to charge overnight.
4. Next day I saw that the phone did not restart like how it used to. It was stuck at GOOGLE and would not restart.
5. I disconnected from the charger. Went to fastboot and switched off the phone.
6. I started to heat the phone using hair dryer with the phone switched off for about 10 mins. I held it was a cloth since it gets hot pretty fast.
7. Paused for a sec, turned on the phone (it was bootlooping) and continued to heat the phone for another 5 mins. (by then I gave up)
8. Stopped heating. I left the phone and went out to work on something else. After half an hour, when i returned I saw that the phone was completely switched off and was not bootlooping. I got excited since I know that the phone was fully charged overnight and there is no way that the phone would have died due to battery drain.
9. I immediately turned on by holding on to the VOL down button. I selected recovery from fastboot. To my surprise for the first time in 2 weeks I was able to go into recovery mode. I cleared cache and restarted the phone in Normal mode.
10. Phone booted properly and loaded the OS.
11. First thing I did was to go into developer options and turn on "ENABLE OEM UNLOCK" option. (By now I knew how important it was to have this enabled. THIS COULD SAVE YOUR $549 PHONE!!)
12. Took a backup of all the files and unlocked the bootloader.
I downgraded the OS to 7.1.2 (Aug release) which I felt was a stable one for Nexus 6P. I also did a h/w check and all the tests passed CPU / Memory is fine. I am still not sure what could have caused the bootloop but the fact that it happened after the Oreo OTA would make me to stay away from upgrading the Android version beyond 7.1.2.
Click to expand...
Click to collapse
---------- Post added at 05:18 PM ---------- Previous post was at 05:09 PM ----------
I just waited like 5 or 10 minutes and my phone started in system. Just enough to activate stuff in developers options!
arkanthos said:
Hey, first thank you so much for sharing your experience. It gave a guide to follow step by step which I really appreciate. I have tried the heating tecnique and has partially worked 3 times, google logo turns into the other google logo but at a really low speed, then it switches off my phone. I tried to start on Safety Mode as you said but it just says "Not command" nex to an android icon. Any aditional advice?. Thank you
Click to expand...
Click to collapse
I just had this happen to me. Friday evening, I noticed an update and I usually read reviews prior to downloading, but I clicked anyways. All seemed fine until Saturday night, was in fb, watching a cooking video and clicked on a link for the recipe when my phone went blank and to the Google screen. tried for 2 days to reboot, get into boot-loader, recovery, anything!
Luckily, I have 9 more days on my Square Trade warranty. They required me to take to a fix-it store (all they could try was a battery pull, which was unsuccessful). Square Trade sourced me a replacement, so it came in last night and I am downloading all my apps and trying to get back "to normal".
I did do an Android update, at the urging of my son, since he has the same phone. Now I see one more, that is a small update. Worried if I should download or not?
I just found this forum and haven't yet gone searching for help on it.
This info is good to know.
Thanks and take care!
Thank you save my life again i have no hair dryer and place it on my rick cooking about 10 mins after that it boot slow gooe animated and i format factory and clear cach first try and succeeded
Hi! I have an S10+ Snapdragon, I bought it a year ago, the firsts weeks the phone worked perfectly, but as time passed, the phone started to reboot suddenly, no matter what I was doing, sometimes playing music, watching videos, or chatting in whatsapp or telegram. Then, I don't know why, the phone got bricked, got stuck in the boot animation and it only started in recovery mode, I made a factory reset from recovery mode, and the phone started only in safe mode. I took it to the technician and he flashed it with Odin and the phone worked again, but still with the sudden reboots.
Few months later, the phone got bricked again, it got stuck in download mode, with the message "hash of data does not match digest in descriptor" in the top left corner, another technician said me it was necessary to change the "motherboard" of the phone, he changed it and the phone worked again and still with the sudden reboots.
Sometimes the phone reboots completely, sometimes it reboots from the end of the boot animation and sometimes it seems that the systemUI restarts because the screen gets black and I have to unlock the phone with my pin again but the apps processes still running normally. Once, the phone rebooted and it got stuck in the lock screen, I wrote my PIN and the phone got back to the lock screen again, and so on... I have to reset it from the recovery mode and it worked again.
Nowadays, the phone stills rebooting suddenly and any app stops working anytime. I've noticed that when it reboots, the middle left side of the phone heats.
Someone knows what can be? Thx in advance for reading and for any help