Related
This is a very strange issue, I'll describe it here. I bought recently a OnePlus One in Spain. I've followed these steps:
1. Install CWM from High on Android guide
2. Install Android 5.1.1 from Gizbot guide (which comes from this XDA guide).
I finished the steps and got Android working perfectly. I love how smooth it is and all. However, I was ready to leave so I unplugged the USB (official cable). The phone freezes for few seconds and then it reboots. Now, I have tried many things and been in the same point many times, so there are two behaviours that can occur:
- When starting from the beginning with the cable unplugged, the Dirty Unicorn spinning wheel just freezes and reboot. It keeps doing so constantly. Reboot hell.
- When starting with the USB connected, but after a reset from disconnecting it, it goes into "Android is starting... Optimizing app 8 of X". There are two odd things here: the X is a different number each time it reboots, like 55 or 90, and then it freezes apparently at Google Apps and reboots again. Same reboot hell, but longer.
Now, I can turn it off, enter into recovery mode and reinstall everything. This is what allowed me to test exactly when it breaks. In any case it will only even start the Android 5.1.1 if the USB is connected.
My question is, any idea why this is happening? Any recommended step once inside Android to try to avoid this?Otherwise I'll try with another ROM, but I think that it's super odd and it looks like it might be fixed easily by someone who understands the system better than me...
Few extra details:
- Battery is 100%, so no apparent problem there.
- I'm using Ubuntu 15.04 on the computer side.
- I don't have a SIM card yet.
PS, if trying other ROM/gapps, which one do you recommend?
fpresencia said:
This is a very strange issue, I'll describe it here. I bought recently a OnePlus One in Spain. I've followed these steps:
1. Install CWM from High on Android guide
2. Install Android 5.1.1 from Gizbot guide (which comes from this XDA guide).
I finished the steps and got Android working perfectly. I love how smooth it is and all. However, I was ready to leave so I unplugged the USB (official cable). The phone freezes for few seconds and then it reboots. Now, I have tried many things and been in the same point many times, so there are two behaviours that can occur:
- When starting from the beginning with the cable unplugged, the Dirty Unicorn spinning wheel just freezes and reboot. It keeps doing so constantly. Reboot hell.
- When starting with the USB connected, but after a reset from disconnecting it, it goes into "Android is starting... Optimizing app 8 of X". There are two odd things here: the X is a different number each time it reboots, like 55 or 90, and then it freezes apparently at Google Apps and reboots again. Same reboot hell, but longer.
Now, I can turn it off, enter into recovery mode and reinstall everything. This is what allowed me to test exactly when it breaks. In any case it will only even start the Android 5.1.1 if the USB is connected.
My question is, any idea why this is happening? Any recommended step once inside Android to try to avoid this?Otherwise I'll try with another ROM, but I think that it's super odd and it looks like it might be fixed easily by someone who understands the system better than me...
Few extra details:
- Battery is 100%, so no apparent problem there.
- I'm using Ubuntu 15.04 on the computer side.
- I don't have a SIM card yet.
PS, if trying other ROM/gapps, which one do you recommend?
Click to expand...
Click to collapse
Same issue here, did you ever figure it out?
Had the same issue today but with another rom. Fixed it by first installing CM12 latest release and booting, then flashing custom rom + Gapps + Kernel.
Maybe this helps for you as well!
Hi guys
any solution to this issue?? It happens to me as well, now with latest Oxygen ROM (from yesterday).
When it is unplugged it will reboot. not if plugged in.
Help!!
Can you give us specific details as to what ROM, Kernel, and Gapps versions you used? This problem is a seemingly unfixable one at the moment.
I have an old Mi1s here that I was planning to mess around with. However, I found that booting into recovery and bootloader sent the phone into bootloop.
Furthermore, after I tried to wipe the phone's data, the OS (MIUI v5 stock) now forcibly returns to the home screen every time I try to open an app. I can't do anything in settings unless I move very fast.
Plugging the phone into a computer or charger does nothing when the phone is in OS. Not even any charging. adb devices returns nothing. However, when the phone is powered off and plugged in, the phone's power LED turns on and the phone charges. adb devices returns its number and says it is unauthorized.
First, I will say that I have done an extensive amount of searching and reading about boot loops and issues with the Note 4 before posting this. After days of dead ends, I have to ask for help...
About a week ago (end of January 2017), I installed the Verizon security patch update for Android 6.0.1 for my Note 4 (SM-N910V): MMB29M.N910VVRS2CQA1. Everything was normal until this past Friday night, when I used a flashlight app (had been installed since I had the phone and used often) and it spun into a bootloop. Battery was at 20% at the time, and since I've had the phone, the battery quickly discharges below ~15%.
Situational Details:
Anyways, the bootloop goes all the way to the home screen, and often the touchscreen is active for a few seconds (varies) before it freezes for 5 seconds and continues the bootloop. It's worth noting that during the bootloop, the screen gets incrediby hot at a specific point: horizontally across from the power button and vertically below the light sensor.
Also, I'm able to access the recovery menu, download menu, and boot menu. Also, when a power cable is connected to the phone (with battery inside), the phone screen shows the empty charging battery symbol and then immediately turns on, without me having to press the power button. After that, the only way to actually power off the phone is to remove the battery or let it bootloop until it dies.
So far, I've tried the following without success:
-Wiping partition cache
-Factory data reset
-Flashing stock ROM with Odin. Though Odin recognized the device in the USB port and it accepted the ROM which I loaded it with, there was no activity from Odin to the phone once I clicked "Start". I'm using the original USB cable that came with the phone (the one that I charge it with), and the USB port is working fine.
-Using Kies3/Kies2.6/Smartswitch to revert back to factory stock ROM. Though Kies3 is allegedly the correct software, they all display an error message that my device is not supported, when I attach a USB cable to my laptop from my phone (regardless of USB port).
-When using Kies3 to try Tools > Firmware upgrade and Initialisation, Kies accepts "SM-N910V" as the model number, but it displays an error message that my S/N is incorrect, though I am copying and verifiying the IMEI from under the battery compartment (I also registered my phone with Samsung using this IMEI, so I know it's valid).
-Wiping partition cache 5x + Factory data reset 5x before rebooting
When in the recovery mode, the current android version MMB29M.N910VVRS2CQA1 is listed, which I find incredibly bizarre, since I thought it would have flashed to the stock ROM after a factory data reset. *shrug*
It's crossed my mind that the exceedingly hot temps may be causing the boot loop, but genuinely do not know if that's true or why it would become so hot in the first place. Either way, I just want to toss the idea out that maybe I have a hardware issue that's causing such overheating.
Anyways, at this point, I'm totally confused about what to do, especially since it's not totally bricked. Any/all help is greatly appreciated.
Anybody have any thoughts at all? I'm more and more open to the theory that it's overheating and causing a boot loop. When it's been sitting for a long time at room temperature, the screen remains at full brightness on the Verizon splash screen, and does so until it gets stupidly hot near the microSD / SIM slots... then it boots up for ~5-15 seconds, freezes for 5 seconds, and boot loops again.
I may try to thoroughly wrap my phone in plastic wrap and apply an ice pack before attempting to use it again. I find it hard to believe that the culprit is batteries since the issue happens with both batteries that I have (purchased separately at different times).
Ok, I had my Note 4 totally cold yesterday and booted it up normally. I discovered a few things while playing with it:
When the first reboot happened,the usual hot spot was hardly to room temperature. I tried this exact same test again this morning, with the same results... the hot spot was not even to room temperature when it froze and rebooting.
It's worth noting that I figured out the screen does not freeze if the display is constantly moving, regardless of phone temperature. For example, I normally try to do something/anything prior to the phone freezing and rebooting, like establish a file transfer type usb connection to my laptop, instead of the default 'charge' type connection. Well, to go through the settings menu and pick out the connection type, the screen will always hang for a split second as it loads the next set of menus. Normally, it would freeze at this point and reset. But today, I decided to click on the Apps button and oscillate my finger on the screen to flip between pages of apps... and it worked for several minutes straight.
I know my problem seems incredibly strange, but do any of these symptoms have any plausible explanation? I'd hate to think there is literally nothing that I do and that my $$$ Note 4 phone is now a brick.
1weirdtrick said:
First, I will say that I have done an extensive amount of searching and reading about boot loops and issues with the Note 4 before posting this. After days of dead ends, I have to ask for help...
About a week ago (end of January 2017), I installed the Verizon security patch update for Android 6.0.1 for my Note 4 (SM-N910V): MMB29M.N910VVRS2CQA1. Everything was normal until this past Friday night, when I used a flashlight app (had been installed since I had the phone and used often) and it spun into a bootloop. Battery was at 20% at the time, and since I've had the phone, the battery quickly discharges below ~15%.
Situational Details:
Anyways, the bootloop goes all the way to the home screen, and often the touchscreen is active for a few seconds (varies) before it freezes for 5 seconds and continues the bootloop. It's worth noting that during the bootloop, the screen gets incrediby hot at a specific point: horizontally across from the power button and vertically below the light sensor.
Also, I'm able to access the recovery menu, download menu, and boot menu. Also, when a power cable is connected to the phone (with battery inside), the phone screen shows the empty charging battery symbol and then immediately turns on, without me having to press the power button. After that, the only way to actually power off the phone is to remove the battery or let it bootloop until it dies.
So far, I've tried the following without success:
-Wiping partition cache
-Factory data reset
-Flashing stock ROM with Odin. Though Odin recognized the device in the USB port and it accepted the ROM which I loaded it with, there was no activity from Odin to the phone once I clicked "Start". I'm using the original USB cable that came with the phone (the one that I charge it with), and the USB port is working fine.
-Using Kies3/Kies2.6/Smartswitch to revert back to factory stock ROM. Though Kies3 is allegedly the correct software, they all display an error message that my device is not supported, when I attach a USB cable to my laptop from my phone (regardless of USB port).
-When using Kies3 to try Tools > Firmware upgrade and Initialisation, Kies accepts "SM-N910V" as the model number, but it displays an error message that my S/N is incorrect, though I am copying and verifiying the IMEI from under the battery compartment (I also registered my phone with Samsung using this IMEI, so I know it's valid).
-Wiping partition cache 5x + Factory data reset 5x before rebooting
When in the recovery mode, the current android version MMB29M.N910VVRS2CQA1 is listed, which I find incredibly bizarre, since I thought it would have flashed to the stock ROM after a factory data reset. *shrug*
It's crossed my mind that the exceedingly hot temps may be causing the boot loop, but genuinely do not know if that's true or why it would become so hot in the first place. Either way, I just want to toss the idea out that maybe I have a hardware issue that's causing such overheating.
Anyways, at this point, I'm totally confused about what to do, especially since it's not totally bricked. Any/all help is greatly appreciated.
Click to expand...
Click to collapse
Do you have USB debugging turned on? Do you have all of the USB drivers for Samsung phones installed? Are you using the stock USB cable when you use Odin?
If you can't get Odin to flash your firmware(it has to be the same version you have or newer, it can't be older), then you may have a hardware issue that is a result of the excess heat you mentioned.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
Do you have USB debugging turned on? Do you have all of the USB drivers for Samsung phones installed? Are you using the stock USB cable when you use Odin?
If you can't get Odin to flash your firmware(it has to be the same version you have or newer, it can't be older), then you may have a hardware issue that is a result of the excess heat you mentioned.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I didn't have USB debugging turned on before. I turned it on (under developer options... which I barely have time to access before it restarts), but now both my laptop and desktop won't recognize the device via any USB port. I do have the USB drivers for Samsung phones installed and have re-installed them a few times, to be safe. Also, I am only using the stock USB cable when doing any of these things.
1weirdtrick said:
I didn't have USB debugging turned on before. I turned it on (under developer options... which I barely have time to access before it restarts), but now both my laptop and desktop won't recognize the device via any USB port. I do have the USB drivers for Samsung phones installed and have re-installed them a few times, to be safe. Also, I am only using the stock USB cable when doing any of these things.
Click to expand...
Click to collapse
Does the device show in device manager? What is it labelled as in device manager?
Sent from my SM-S903VL using Tapatalk
Droidriven said:
Does the device show in device manager? What is it labelled as in device manager?
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Assuming you mean the device manager in Windows, it's only showing as "Unknown USB Device (Device Descriptor Request Failed)".
Two new interesting notes:
When I enter Maintenance Boot Mode (Down Volume + Power to boot) and select USB Debug Mode, it now just performs a normal reboot. I can't recall for certain if this was any different in the past.
When I have the ability to access Developer options, I can definitely see that USB debugging is checked. Also, when I select 'USB configuration', 'charging' is pre-selected by default. When "MTP" (media transfer protocol) is selected, the developer mode menu still displays the value as 'charging', even though subsequently accessing the 'USB configuration' sub-menu shows that MTP is selected. Weird.
1weirdtrick said:
Assuming you mean the device manager in Windows, it's only showing as "Unknown USB Device (Device Descriptor Request Failed)".
Two new interesting notes:
When I enter Maintenance Boot Mode (Down Volume + Power to boot) and select USB Debug Mode, it now just performs a normal reboot. I can't recall for certain if this was any different in the past.
When I have the ability to access Developer options, I can definitely see that USB debugging is checked. Also, when I select 'USB configuration', 'charging' is pre-selected by default. When "MTP" (media transfer protocol) is selected, the developer mode menu still displays the value as 'charging', even though subsequently accessing the 'USB configuration' sub-menu shows that MTP is selected. Weird.
Click to expand...
Click to collapse
Have you tried booting to safe mode, if it boots to safe mode then it's a user app or a user app update that is causing your bootloop. In safe mode you can uninstall whatever app or app update caused it.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
Have you tried booting to safe mode, if it boots to safe mode then it's a user app or a user app update that is causing your bootloop. In safe mode you can uninstall whatever app or app update caused it.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Yeah, I thought about that, too. I've tried safe mode even after factory resets + cache wipes and it still boot loops. ("Safe mode" does indeed display in the bottom left of the display/GUI) Good thoughts, though.
1weirdtrick said:
Yeah, I thought about that, too. I've tried safe mode even after factory resets + cache wipes and it still boot loops. ("Safe mode" does indeed display in the bottom left of the display/GUI) Good thoughts, though.
Click to expand...
Click to collapse
Starting to sound like a hardware issue.
Sent from my SM-S903VL using Tapatalk
Yesterday as I was using my device just like I normally would. Browsing the web. It suddenly froze. Then it proceeded to shut down and turn itself back on and started the restart procedure. This is normal and since the Tablet is 4+ years old it used to sometimes shutdown during usage and turn itself on again. But this time it didn't. It showed the Amazon logo, went on the shining Fire logo and after staying on it for a while. It shuts itself off and again starts from the Amazon logo. I thought that if I just keep it doing that for a while it would fix itself. Sadly it did not. Luckily though it does boot to the Bootloader and I thought that maybe clearing the cache partitions would do the trick. It did not. Again I thought if I cleared the data it would fix it. That did not work either.
I never tried to root or do anything on that device. I didn't even have playstore installed. I use that device as my daily web browsing machine so I really need it to work.
Please Help
(This is my first ever forum post so please forgive me if I do anything wrong)
Hello, my phone today did something very strange, the screen began to turn off and on, and the touch stopped working, try to restart it, and curiously while initial screen works normally, is when it starts MIUI itself that begins to present the failure, the screen goes black, although it sounds the boot sound, and if I press the power button, the screen what it does is flashing without responding the touchscreen (as indicated above), my phone has the latest official version (global), and do not have any changes in the operating system, or anything special. I tried to delete the configuration using the phone menu (volume up + power) sweeping the system, and as I indicated, at that time the phone seems to work properly (until I give start the operating system, and begins to fail), I do not know what else to do, since I had never activated the developer features, or USB debugging and not even think about unlocking the bootloader.
I guess I will have to take it to repair, but I want to avoid ending up being scammed by some nonsense or bug in the system, and that I return the phone as a scrap (most technicians, always end up missing and surplus parts, damn it).
Any guidance or advice would be most welcome,
Blessings.
luismmusic said:
Hello, my phone today did something very strange, the screen began to turn off and on, and the touch stopped working, try to restart it, and curiously while initial screen works normally, is when it starts MIUI itself that begins to present the failure, the screen goes black, although it sounds the boot sound, and if I press the power button, the screen what it does is flashing without responding the touchscreen (as indicated above), my phone has the latest official version (global), and do not have any changes in the operating system, or anything special. I tried to delete the configuration using the phone menu (volume up + power) sweeping the system, and as I indicated, at that time the phone seems to work properly (until I give start the operating system, and begins to fail), I do not know what else to do, since I had never activated the developer features, or USB debugging and not even think about unlocking the bootloader.
I guess I will have to take it to repair, but I want to avoid ending up being scammed by some nonsense or bug in the system, and that I return the phone as a scrap (most technicians, always end up missing and surplus parts, damn it).
Any guidance or advice would be most welcome,
Blessings.
Click to expand...
Click to collapse
did you try to installing the firmware with miflash?
tutibreaker said:
did you try to installing the firmware with miflash?
Click to expand...
Click to collapse
Can you tell me where to get that tool? The fact is that I have tried several, and they tell me that I need to have USB debugging activated, and/or have the bootloader unlocked.
In other words, isn't there a tool that allows me to reinstall the software (which the phone already has installed), without having to activate anything in particular on the phone? I am not changing the rom from one region to another, nor am I installing a custom rom, I just need to try to see if what the phone has is a software failure or not.
luismmusic said:
Can you tell me where to get that tool? The fact is that I have tried several, and they tell me that I need to have USB debugging activated, and/or have the bootloader unlocked.
In other words, isn't there a tool that allows me to reinstall the software (which the phone already has installed), without having to activate anything in particular on the phone? I am not changing the rom from one region to another, nor am I installing a custom rom, I just need to try to see if what the phone has is a software failure or not.
Click to expand...
Click to collapse
using edl mode you can flash your phone but most tool than use that mode are paid
tutibreaker said:
using edl mode you can flash your phone but most tool than use that mode are paid
Click to expand...
Click to collapse
Yes, I see, or Xiaomi is very confident that the equipment they sell will be few, that they will present faults, that can be solved by the user himself simply by reinstalling the system, or as always the Peter principle, they are arriving little by little to its level of ineptitude, releasing dozens of models per year, without really caring about giving really reliable user support, although I think that is already a general policy, almost no manufacturer offers the option of completely reinstalling the phone software from a management app, as happened a couple of years ago, in fact I think that Xiaomi's own application has become obsolete and out of circulation, right?
Because my point remains the same, if my phone is completely vanilla, and for x, y or z situation I need to reinstall the software, then what the hell is the need for the user to have the developer options enabled, and the USB debug ? That makes no sense to me, because I have to pay a third party, for something that is completely free on the internet and freely accessible, but that the company itself now hinders the user from being able to restore his phone without so much complication.
I don't know if I'll be crying and complaining too much about it.
Well I have no choice but to breathe deeply, and that the technician can really find the problem and that it is repairable, and does not give me back a pot.