ads

Affichage des articles dont le libellé est bootlooping. Afficher tous les articles
Affichage des articles dont le libellé est bootlooping. Afficher tous les articles

jeudi 3 septembre 2015

Sprint note 5 boot-looping



I tried to install a custom rom on my sprint note 5 just now and now it is boot-looping. How do I get it to stop boot-looping? Any help would be most appreciated thanks in advance. Btw it doesn't recognize any of my buttons either for some reason or another.



vendredi 28 août 2015

(Help!!!!) Bricked The Phone, Now Bootlooping



So, I tried to install CWM today on my InFocus M330 with the MTK Droid Root & Tools but now it won't boot up, it just bootloops. I can't even go into recovery mode, I can just enter the Fastboot mode but I think that the bootloader is locked and InFocus won't tell me how to unlock it. And because the bootloader is locked, I can't do anything in the Fastboot mode, my PC won't even detect the phone with the command "fastboot devices".



jeudi 27 août 2015

Chinese M9 bootlooping after OTA



Hi All,

Really hoping someone can suggest a possible solution for this one, only had the phone a few months!

So, Chinese released M9. Unlocked. Stock recovery, not rooted. Gapps installled.
Everything perfect, then today I got the 5.1 update.
Seemed like a slightly iffy install process...looked a little like it failed a couple of times and tried again.
Finally finished, the phone shows the white screen with the one logo, takes a while, opens on the desktop and turns off, back to the white screen with the logo.

I have been able to boot into safe mode, which is stable
I have been able to get to download mode and bootloader. Neither of these offer a cache wipe or a factory reset.
I have not been able to get into recovery mode, it shows a phone with a red triangle and an exclamation point.

So for my (largely uneducated) part I have two theories for the cause:

1) Gapps is somehow proving a problem, either faulting the install or causing a fatal error on startup
2) Since the update was notified and downloaded while on a VPN via Hong Kong, I wonder if I accidentally ended up with the HK version in which case I suspect there may be hardware differences (at least the radio). This seems unlikely, I would hope there were enough checks in place to prevent this happening.

No solid idea where to go from here. I have not yet tried ADB access, but even if I can connect, what will I do? Flash a new ROM? I'd rather not. And surely I'd need to root in order to do that....

At a loss, any potential solutions welcomed whole heartedly!
Thanks...