hey. Should i always flash those zips when i want to flash new rom? - modem, boot, bootloader etc. or i just can flash only ROM.
from xda-developers http://ift.tt/237GHnT
via IFTTT
samedi 2 avril 2016
Should I buy the A5 (2016)?
I am coming from xperia z2 and it is fully broken now . I'm asking that should I buy this phone for more of a camera usage? I use my z2 to take photos a lot. I was wondering if this phone is a step up from my z2. Please help.
from xda-developers http://ift.tt/1RTmHUr
via IFTTT
Requesting Blankflash Files From Motorolla
Hey Moto G users
I'm attempting to email Motorola demanding them to release the blankflash files as I amongst many others are facing hard bricked phones.
To cut a long story short, one of my Moto G phones the Moto G 2014 (XT1072 aka Thea) worked fine and then suddenly it decided to not boot up (infinite boot animation screen). I sent it to Motorola and they sent it on to a repair company. I had an email from the repair company saying the phone had been rooted, which clearly it wasn't as the bootloader was still locked. Of course the method I have always rooted phones is via a custom recovery which means an unlocked bootloader is required.
Eventually the phone came back to me and they refused to touch the phone any longer. As Motorola didn't care from this point I thought about unlocking the bootloader. However, that didn't actually work as there was a message on the bootloader screen displaying 'Enable OEM Unlock in developer options'. This was impossible as I already knew the phone wouldn't boot and the only way to unlock the bootloader was to enable the option in the developer settings within the OS.
After playing around with some clear cache and formatting commands (which I obviously tried before I sent the phone off) via fastboot and an attempted bootloader unlock command (not done before until received back from the repair company), miraculously the phone did boot up and I was able to do an OTA update to Android 6 (Marshmallow). I did however keep the bootloader unlocked as everything seemed to run fine with the new update. After 4 days use of my phone the phone repeated apps crashing and eventually the infinite boot animation came back. From here I decided to unlock the bootloader and re-flash a stock ROM for this phone. The 5.0.2 ROM worked and I tried an OTA update to 6.0, the phone powered off and now the phone no longer boots and the bootloader is non-existent.
All I'm going to say is the Moto G series of phones are far one of the most popular, cheap, powerful, bargain phones on the market and it is a shame for them to die off never to be used again when bootloader corruptions occur. I'm going to email Motorola UK and share this thread with them showing a poll of users that also would like access to the blankflash files so we can start our phones on a clean slate. My phone may be a hardware issue but I want to at least give it another attempt by re-partitioning the phone and re-flashing it.
Thanks for reading
Will
I'm attempting to email Motorola demanding them to release the blankflash files as I amongst many others are facing hard bricked phones.
To cut a long story short, one of my Moto G phones the Moto G 2014 (XT1072 aka Thea) worked fine and then suddenly it decided to not boot up (infinite boot animation screen). I sent it to Motorola and they sent it on to a repair company. I had an email from the repair company saying the phone had been rooted, which clearly it wasn't as the bootloader was still locked. Of course the method I have always rooted phones is via a custom recovery which means an unlocked bootloader is required.
Eventually the phone came back to me and they refused to touch the phone any longer. As Motorola didn't care from this point I thought about unlocking the bootloader. However, that didn't actually work as there was a message on the bootloader screen displaying 'Enable OEM Unlock in developer options'. This was impossible as I already knew the phone wouldn't boot and the only way to unlock the bootloader was to enable the option in the developer settings within the OS.
After playing around with some clear cache and formatting commands (which I obviously tried before I sent the phone off) via fastboot and an attempted bootloader unlock command (not done before until received back from the repair company), miraculously the phone did boot up and I was able to do an OTA update to Android 6 (Marshmallow). I did however keep the bootloader unlocked as everything seemed to run fine with the new update. After 4 days use of my phone the phone repeated apps crashing and eventually the infinite boot animation came back. From here I decided to unlock the bootloader and re-flash a stock ROM for this phone. The 5.0.2 ROM worked and I tried an OTA update to 6.0, the phone powered off and now the phone no longer boots and the bootloader is non-existent.
All I'm going to say is the Moto G series of phones are far one of the most popular, cheap, powerful, bargain phones on the market and it is a shame for them to die off never to be used again when bootloader corruptions occur. I'm going to email Motorola UK and share this thread with them showing a poll of users that also would like access to the blankflash files so we can start our phones on a clean slate. My phone may be a hardware issue but I want to at least give it another attempt by re-partitioning the phone and re-flashing it.
Thanks for reading
Will
from xda-developers http://ift.tt/237GDVk
via IFTTT
Battery not charging to 100%
I have a stock nexus 6p that hasn't been rooted or been unlocked and I plugged it in last night and it wouldn't charge fully.
I attached a screen shot of it.
I attached a screen shot of it.
from xda-developers http://ift.tt/1RTmErD
via IFTTT
Volume boost
Is there any way to boost the earphone jack volume without rooting? It's quite a bit lower that iPhone 6s - or old Galaxy s5, for that matter.
from xda-developers http://ift.tt/237GD7S
via IFTTT
Battery drain
Hello people
I bought z3compact, and I started to have big problems with battery drain, I tried to downgrade on 5.0.2, then tried factory, then 6.0.1 beta, and at least I tried custom rom Lolipop Slim and everytime is same story, I barely had one day battery juice, and when i go to sleep, I lose more than 20% thorough the night, when I go to settings number one in battery using is Cell standby, SOT I have barely 2 hours.
Is there any help, I think the radio is problem.
Thank you very much
I bought z3compact, and I started to have big problems with battery drain, I tried to downgrade on 5.0.2, then tried factory, then 6.0.1 beta, and at least I tried custom rom Lolipop Slim and everytime is same story, I barely had one day battery juice, and when i go to sleep, I lose more than 20% thorough the night, when I go to settings number one in battery using is Cell standby, SOT I have barely 2 hours.
Is there any help, I think the radio is problem.
Thank you very much
from xda-developers http://ift.tt/1RTmCjy
via IFTTT
Android Wear on Smartwatch
Hello,
I'm with a hardware company. How do we load Android Wear onto a smartwatch?
I'm with a hardware company. How do we load Android Wear onto a smartwatch?
from xda-developers http://ift.tt/237GAZI
via IFTTT
Inscription à :
Articles (Atom)