yashsingh1/xdaforums huggingface dataset:
[Zuk Z1 Themes and Apps] Extentho:
Hello, i m interested in running multiple roms on Lenovo Zuk. I have found there are few apps who do this, such as: MultiROM, dual boot. Problem is none of these support Lenovo Zuk Z1 right now. So, is there a way to try another rom without having to uninstall or reflash the ROM in use?
[Zuk Z1 Themes and Apps] Darth:
You've asked this already in the correct section for questions, which this section isnt.

http://xdaforums.com/zuk-z1/help/run-multiple-roms-lenovo-zuk-z1-t3317375

I'll close this thread. :good:
[Verizon LG G3] iBolski:
I have an app called Alarm Clock xTreme. Since upgrading to Marshmallow, my alarm has not gone off. I've tested it during the day and it goes off. What I'm wondering is, could Doze be affecting it since I haven't used my phone while I sleep so maybe the app itself doesn't work right now? I'll check the app page and possibly email the developer, but it did work when I set the alarm to go off 15 minutes later, but maybe Doze mode hadn't kicked in yet?

I haven't tried the default Clock alarm yet to see if that works.

My next step is possibly to uninstall the app and reinstall it fresh to see if that helps, but I can't afford to miss my alarm a third day in a row. I've been lucky that I woke up in enough time to get ready for work and not be late. :eek:
[Verizon LG G3] roirraW "edor" ehT:
Yep, you have to add that app to the exceptions list for Doze. Although I did it with a couple apps on 46A already, now I can't remember where I found the option. Without Greenify or another app's "Aggressive" Doze, the default Marshmallow Doze takes a couple hours to kick in.
[Verizon LG G3] iBolski:
Got it. Here's how to do it:

Go to Settings

Next, select Battery

Select Battery Usage

Under the Battery Optimization section, select the Ignore Optimizations

Then, put check marks next to the apps you don't want to be battery optimized (that is, "dozed").
[Verizon LG G3] roirraW "edor" ehT:
Ah! Thank you! It's kinda intuitive where the option is but it's too deep. I would suggest it should be at the very top when you select Battery.
[Verizon LG G3] iBolski:
Yup. I concur. In the standard Marshmallow instructions, it's not that deep. I think it's Settings->Battery->Battery Optimizations. Looks like LG/VZW decided to hide it a level deeper. At least now I know where to go if I start seeing apps not working while in Doze mode.

It appears I could have just used the normal default Clock app alarm as that appears to not be affected by Doze. Not sure why I purchased Alarm Clock Xtreme, other than I believe it was an Amazon Free App of the Day app.
[Verizon LG G3] roirraW "edor" ehT:
I, too, had Alarm Clock Xtreme first as a free Amazon app and then I might have paid for the Play Store version since Amazon's store would often stop being updated with the latest versions. I use Google Clock from the Play Store, now.
[Verizon LG G3] iBolski:
That's what I'm getting ready to do. Not sure why I kept using Alarm Clock Xtreme. Sounds like we were in the same boat with it. I think I too repurchased it from Google Play. lol! Must be a C-Bus thing or something.
[Verizon LG G3] roirraW "edor" ehT:
LOL, forgot about that.
[Verizon LG G3] andip:
Thx 4 the help roirraW "edor" ehT + question

Hey guys, Andi from the ACX team here. Two things:

1.	We are working on fixing the alarm not going off issue in Android M. For now, there’s the fix that roirraW "edor" ehT mentioned. (thanks for that btw). New update should be out soon with bug fixes and a pretty cool new feature.

2.	On a different note, we would like to hear from you and understand why you chose to download an alarm from the Playstore and not use the stock one. Doesn’t matter if you use our app or another alarm clock app. To make it worth your time, there’s an Amazon voucher for those who talk to us. More details here: bit.ly/1Ufi72A - Please help us make ACX better, we really want to hear what you have to say.
[G2 Q&A, Help & Troubleshooting] Abhishekreddy:
Hi guys i hav lg g2 d800...my phone showing oly lg logo nd notification light after lollipop update(i thought my phone model is d802 nd updated to lolipop through pc suite bt acually my phone model is lg g2 d800) nd it is not entering into fastboot mode nd download mode plz plz help me guys it will be great fulll thnk u guys help me....
[Honor 6, 6 Plus Q&A, Help & Troubleshooting] monmon20077:
i used the source in this thread:

http://xdaforums.com/honor-6/help/honor-6-android-6-0-emui-4-0-update-t3314139#post65315904

upgraded directly form b521 to b805 (H60-L04), but the battery drain is very high... tried to upgrade to b806, 807, 810 all failed tried to downgrade to b521 or any other version but also failed..

please need help.. the battery empty in less than a day
[Honor 6, 6 Plus Q&A, Help & Troubleshooting] Steve Giordano:
You have twrp backup of your b805 ?
[Honor 6, 6 Plus Q&A, Help & Troubleshooting] monmon20077:
no.. why??
[Honor 6, 6 Plus Q&A, Help & Troubleshooting] Steve Giordano:
For correct downgrade to lollipop, first you make a twrp backup.

Your current version is L04-C432B805 ?

Guide to make a backup:

UNLOCK BOOTLOADER WITH MULTITOOL

Download

TWRP_2.8.7.0_EN_EMUI_4.0_v4.img

AND

ADB

Copy TWRP_2.8.7.0_EN_EMUI_4.0_v4.img in the adb folder,

turn off the device and boot into fastboot mode

in adb folder run cmd.exe as administrator and type these commands:

fastboot devices

If the device is recognized correctly displaying a series of numbers;

Then type

fastboot flash recovery TWRP_2.8.7.0_EN_EMUI_4.0_v4.img

fastboot reboot

Disconnect the USB cable and press volume up + power (press 8 - 10 seconds) to enter into recovery.

Into Recovery:

BACKUP (ALL)

After finish save the backup the folder TWRP (with the backup).

After this you flash a stock recovery and stock boot.img of b803 firmware

and install downgrade package for b803, after this, install Lollipop firmware ;)
[Honor 6, 6 Plus Q&A, Help & Troubleshooting] monmon20077:
it says build number: L04_2015_1120_1100 .... what does this mean???
[Honor 6, 6 Plus Q&A, Help & Troubleshooting] monmon20077:
i tried all the downgrade packages in this thread, but the installation fails at 36% every time,,, what shoud i do... please help

i also have a question.. i always put the update.app in the dload folder in SD card.. should i try to put it in internal storage.. will it differ or harm the phone ??
[Honor 6, 6 Plus Q&A, Help & Troubleshooting] monmon20077:
i am L04 and tried to put it on internal storage and alos failed at 36%

i noticed that any downgrade fails at 36% and any upgrade (tried to 806, 807 and 810) all failed at 5%.. any eplanation or solution for this.. i'm afraid that when the official stable release comes out i won't be able to upgrade to it :(:confused:
[Honor 6, 6 Plus Q&A, Help & Troubleshooting] monmon20077:
i don't know how to do this.. can you send me the files please. i appreciate your help.. thx
[Honor 6, 6 Plus Q&A, Help & Troubleshooting] monmon20077:
i did flash boot.img and recovery.img and still downgrade failing at 36%.. what should i do now??
[Wileyfox Storm] maxxie00:
Hello, I have a problem with my storm. Two days ago I received it and flashed the then latest cm13 and its corresponding recovery. Everything seemed to work just fine until yesterday when there appeared to be an ota update. After the download finished, the phone rebooted itself and is since then stuck with a black flickering screen. Every attempt to start the phone using recovery or bootloader seems to fail, as the phone keeps showing me the black flickering screen, no matter the combination of keys (vol+/vol-) I use to turn it on. If during the black screen I plug the phone to the computer adb can actually see the phone but says it's not authorized to perform any command. On the other hand fastboot won't even see the device.

Is there anything else I can try before sending it back to wileyfox?

Thank you in advance
[Wileyfox Storm] maxxie00:
I've made some progress, I found out that the device can be forced to Qualcomm HS-USB QDLoader 9008 mode by turning it off and then connecting it to usb while holding vol+ and vol-.

I've also found the stock firmware at https://cyngn.com/support.

Now it would be great if somebody could help me, and the others in my situation, to figure the wole QFIL unbricking out, because I'm overwhelmed, and can't seem to find the right info on google.

Thanks to anyone who'll care to help, or share some info
[Wileyfox Storm] miSAKe:
I had a similar issue so have created a thread with stock recovery instructions, which resolved the issue for me.

http://xdaforums.com/wileyfox-storm/help/how-to-flash-stock-images-brick-recovery-t3319617

I hope this helps.
[Wileyfox Storm] maxxie00:
Thank you for your reply.

Unfortunately this does not seem to be applicable to my case because on my device fastboot mode doesn't seem to work.

I've spent an entire afternoon trying to get it to boot to fastboot mode using different vol keys combinations and timings, but none of them seemed to work. No matter the combination, it just kept booting to a black screen flickering.

I'm starting to think that it could be some problem unrelated to my actions because if, as I think it is, recovery mode and fastboot mode are two separated things, nothing I did would justify this kind of behaviour.
[Wileyfox Storm] miSAKe:
Sorry to hear you are still having trouble, it does sound like the same issue, was a CM13 update from the last couple of days, upon reboot I saw the wileyfox logo but when the Cyanogen logo would normally show during boot it displayed a black screen, which would flicker every few seconds. Holding vol- and power to reboot resulted in the same thing so I was unable use recovery.

When the display was black and connected via USB I was able to see the device using ADB but like you no commands were authorised.

Leaving the phone plugged in via USB and holding down vol+ and power until it rebooted I was able to enter fastboot, once the fastboot prompt was displayed on the screen I attempted using fastboot to boot from a custom recovery, unfortunately that just resulted in the same blank screen for me. I also tried booting the stock recovery with the same result, I admit I did not try many older CM recoveries, but I wanted to revert to CM12.1 anyway, as the accelerometer and gyroscope not working in CM13 at the moment is no good for me.

Only thing that worked was a stock restore, so I think something beyond the recovery got broken as you could not even boot a previously working recovery.

For the sake of sanity it may be work getting someone else try booting it into fastboot before resorting to Wileyfox support. Though your phone is really new so could claim a refund or replacement from the seller, that would probably be faster.

FYI if you do end up sending it to Wileyfox support they do flash it back to stock, I had a broken screen replaced, was repaired and back to me in just under 2 weeks.
[Wileyfox Storm] maxxie00:
What would be exactly the timing for it to boot to fastboot mode?

Because I just tried (again...) to plug it to the computer while powered off, then it powered on on its own.

After that I rebooted it by holding together power and vol+ and immediately after it rebooted (right after the vibration) I let the power button go and kept holding the vol+ until the black screen appeared again... no fastboot
[Wileyfox Storm] miSAKe:
Hi,

Just tried a few combinations to check timings for you.

Powered off, not plugged in, holding vol+ while plugging in phone end of usb connected to computer, keep holding vol+ -> boots straight to fastboot.

Powered on, already connected to computer via usb, holding vol+ and power, release power when vibrates to indicate reboot but keep holding vol+ -> boots straight to fastboot.

Are you seeing the black and white Wileyfox logo when first booting? When going to fastboot it should skip that. If you are not seeing the logo it might not show the fastboot screen either. You can try following the steps above and then issuing fastboot devices from a command/shell session to see if you are in fastboot mode.

I hope that is of some help.
[Wileyfox Storm] maxxie00:
Thank you but I can confirm that neither of these combinations work for me. When rebooted/powered the device shows the wileyfox's logo.

If I use your first method it just seems to freeze on the wileyfox's logo screen, and the computer won't even see it (it's not listed on the usb devices list) so fastboot's not an option.

If I use your second method, or any other I tried, it shows me the wileyfox's logo and then proceeds to the black screen, which can be seen just by adb (not fastboot) but I'm not authorized to perform any action like you described for your issue.

I'm out of ideas so I'm sending it back and getting it replaced. On the cyanogenmod irc they told me that to brick it like that it cannot be done just by accident but it should require a lot of deliberate effort, and that just installing cm13 + recovery doesn't justify this problem nor does an OTA update, so it's probably some other (hardware?) issue with a very bad timing.

I'm kind of sure it's not the vol+ button that's damaged, because if I leave the device powered off and then proceed to plug the USB while holding together vol+ and vol- it powers on, but the screen stays off meaning the Qualcomm HS-USB QDLoader 9008 mode has been triggered.

Anyway thank you for your help, I could rule out my inability to start the fastboot mode and blame it on the phone xD

Hope I'll be luckier with the next one...
[Wileyfox Storm] miSAKe:
No problem, I hope you have more luck with the replacement.
[Wileyfox Storm] maxxie00:
Here I am again, new device, still can't boot to fastboot mode (this time I didn't flash anything, just unlocked bootloader so it's not bricked).

"adb reboot-bootloader" works, advanced reboot menu works, yet the vol+ combination hangs on the vendor's logo.

I'm contacting cyanogen os people to try to understand what might be the issue...

Could you please confirm that your device boots into fastboot mode when using the vol+ way? thank you
[Wileyfox Storm] miSAKe:
Hello again,

So these 5 methods work for me, someone else may have other experiences:

Phone powered off, hold vol+ while connecting USB, other end of USB already plugged into PC, continue holding vol+ until booted to fastboot (almost instant).

Phone powered on, already connected to USB, other end of USB already plugged into PC, hold vol+ and power until reboot vibrate, continue holding vol+ until booted to fastboot (almost instant).

Phone powered on and in OS, already connected to USB, other end of USB already plugged into PC, debug enabled, from ADB console, adb reboot fastboot or adb reboot bootloader

Phone powered on and in OS, advanced reboot options turned on, hold power, select reboot, select bootloader, reboot

Phone powered on and in Recovery, select reboot to bootloader

Currently I am running stock everything.

Perhaps try different USB cables or ports, though I still get to fastboot without the USB cable plugged in.

My Storm was a pre-order so is one of the first releases, it is possible they have changed something since.

Edit: I have come across a thread on the Cyanogen forums which implies this may be related to encrypting your device: http://forum.cyanogenmod.org/topic/117661-bootloader-hangs/ - I see you have been there already :)

as reference mine is not encrypted at the moment
[Android Q&A, Help & Troubleshooting] anurag061:
Friends i woke up and found black screen on my phonethen i took out bettery and put it again but it shows only zen logo and goes off and after some hours later i saw my phone goes dead it not show any boot logo.i try heard reset it but nathing happen.phone didnot turn on.when i flash stock firmware again with sp flash tool then it shows BROM ERROR : S_FT_ENABLE_DRAM_FAIL (4032) please help me to get my phone back.

Thanks in advance
[Android Q&A, Help & Troubleshooting] anurag061:
Please help me my phone is dead.
[Android Q&A, Help & Troubleshooting] anurag061:
Please help anyone
[Android Q&A, Help & Troubleshooting] anurag061:
Please help me:(:(:(:(:(:(:(
[Nexus 6 Q&A, Help & Troubleshooting] nozzleman_85:
Long story short. was flashing roms/mods on a spare Nexus 6 of mine and ended up in a bootloop. Now i'd NORMALLY just boot into recovery/fastboot and fix it or restore a backup but that is where i'm running into my fabolous problem of mine. The volume down button is broke so you can't push it in and or hold it. So what i'm wanting to know is if anyone knows a workaround for booting into recovery or fastboot so i can restore this phone. ANY suggestions are welcome. Thank you!
[Nexus 6 Q&A, Help & Troubleshooting] dahawthorne:
"adb reboot bootloader"?
[Nexus 6 Q&A, Help & Troubleshooting] Paradoxxx:
He's lucky if ADB daemon starts :P, otherwise he won't be able to adb it.
[Nexus 6 Q&A, Help & Troubleshooting] simms22:
connect to fastboot while you're in the bootloader, then type reboot recovery
[Nexus 6 Q&A, Help & Troubleshooting] blanco2701:
how can he get to bootloader if the volume down button is dead? lol... I think his only option is to fix that button.
[Nexus 6 Q&A, Help & Troubleshooting] simms22:
good point, but occasionally during bootloops, itll boot into the bootloader. only other thing i can think of is to power it off, and try to connect it to adb, the try reboot recovery.
[Nexus 6 Q&A, Help & Troubleshooting] StykerB:
ya know this is something I always just took for granted but now I'm gonna be checking my volume buttons everytime I flash something...
[Nexus 6 Q&A, Help & Troubleshooting] aiiee:
As painful as this is to admit, this is one time a knowledge of adb and fastboot might be helpful :)
[Nexus 6 Q&A, Help & Troubleshooting] nozzleman_85:
Can't get get into fastboot if im stuck in a bootloop smart one...try reading before posting a stupid reply/answer like this...
[Nexus 6 Q&A, Help & Troubleshooting] simms22:
sure you can, that's an easy one. power your n6 off, then boot up with the power button + volume down pressed, this will boot you into the bootloader. the bootloader is the ONLY place that fastboot works. duh.. :silly:

oh, btw, I AM dumb. broken volume down button, right.
[Nexus 6 Q&A, Help & Troubleshooting] aiiee:
LIghten up Percival, it was meant in a humorous fashion.
[Nexus 6 Q&A, Help & Troubleshooting] nozzleman_85:
My bad...
[Nexus 6 Q&A, Help & Troubleshooting] aiiee:
me too. I forget sarcasm doesn't translate in ascii.

Can you not take the back off and use a small pin or pry tool to depress vol down?
[Nexus 6 Q&A, Help & Troubleshooting] nozzleman_85:
Tried using the Sim removal tool and using the small hole in the Sim tray area, unfortunately it just bent the tool all to hell
[XDA Assist] Zouhaman:
Hi guys I have problem when I using the psiphon vpn to download from popcorn time I think it's from the port and when I use other vpn with port 80 work.

Please help me !
[XDA Assist] Darth:
Hi,

We don't discuss tv and movie piracy on XDA.

Thread closed .

Darth

Forum Moderator
[LG G Pro 2] samsudtabrin:
I have installed a custom recovery. But can't go to the recovery option using these two keys. I can go via app,but i'm afraid if i brick the phone,then that method won't work. Please enlighten me. Thanks in advance.
[LG G Pro 2] pato2015:
Kitkat recovery vol down + power logo appear pres vol up and vol down same time.

Lolipop vol up +power... Logo appear release vol up keep pressing power... Korean language appear press power again.

Download mode press power+ vol up... Then release power.
[LG G Pro 2] atiftariq1:
Don't Worry,

Download ADB toolkit

go to shell

and run command by on debugging on in developer option..

developer option can be on 'About Phone'---> Software Information---->Build Number (Click 10 times)

command: adb reboot recovery
[LG G Pro 2] coavasic:
If you have custom recovery, use only kitkat method.

1. Power off device

2. Hold volume down and power button at the same time

3. When lg logo appears release for second and now hold volume up and volume down at the same time

It is a little tricky and you maybe need to restart device multiple times

4. You will get "Factory data reset" screen

Now, if you have custom recovery you can select "Yes" and enter recovery, this will not format your data. But if you have stock recovery it will format.
[JAMin, XDA Neo, S200 ROM Development] yltan:
Guys,

Can we flash our Prophet with this ROM since the hardware are all the same.

HTC Touch (Wasabi Green) ROM Code (1.17.707.2G WWE).

http://xdaforums.com/showthread.php?t=328181.

More over this ROM is directly from Dopodasia.

Thanks...
[JAMin, XDA Neo, S200 ROM Development] iiiox:
haha!

Just to kill time....I'm flashing it...

1 min later....and....of course, failed!
[JAMin, XDA Neo, S200 ROM Development] hma4:
who said the hardware are all the same ? :) i don't think flashing this rom would be a good idea. although you can always try ;)
[JAMin, XDA Neo, S200 ROM Development] gullum:
If it's only the green you want then just dump the rom and copy all the .brn and .png for the cube to the windows folder
[JAMin, XDA Neo, S200 ROM Development] yltan:
Just checking if this ROM is suitable for Prophet. Would be nice if we can upgrade this from Dopod. Too bad then...
[JAMin, XDA Neo, S200 ROM Development] wanwarlock:
damn dude... so ur prophet is dead then???
[Moto G 2015 Q&A, Help & Troubleshooting] sticktornado:
The 2015 Moto G is a fair phone, but what hit, if any, would it take when the device is encrypted? Battery life? Read/write speed? Heating up?
[Moto G 2015 Q&A, Help & Troubleshooting] u42671:
See

http://xdaforums.com/2015-moto-g/general/to-encrypt-to-encrypt-t3255638
[Moto G 2015 Q&A, Help & Troubleshooting] JainMayurD:
Check

http://xdaforums.com/2015-moto-g/help/encrypt-phone-feature-moto-g-3rd-gen-t3302292
[Moto G 2015 Q&A, Help & Troubleshooting] u42671:
Sorry, no idea why encryption is not possible in your case or wheather this might be related to your phone being rooted.

All I know is, that for me encrypting the Moto G3 did work just fine and there was no noticable performance impact. My Moto G is not rooted and still was on Lollipop back then.

Meanwhile I updated to Marshmallow via OTA. No problems with the update, despite the encryption. And still no noticable performance impact.
[Moto G 2015 Q&A, Help & Troubleshooting] mouse256:
I've my moto 3G (1GB version) encryption for a couple of months now, and I must say I did not notice a real performance impact. The only think I did notice is I now have to reboot the phone once a week or so as it suddenly becomes slow. I did not experience that before encryption. This was on android 5.1

I've now just upgraded to Marshmallow, besides that everything is still working, I can't provide much performance info.
[Galaxy S6 Edge+ Q&A, Help & Troubleshooting] Wesley_NL:
hey guys i have a question,

is there a way to get more or beter offers from tabjoy? i mean the offers that i get are webgams witch don't give a sh*t and the installed apps only give 1np in dream girlferind, it is like what am i doing it for , i tried to google but i can get get wiser out of these so i thought maby to ask here,

what i did/tried

1. reset android id

2. wipe tapjoy cache

3. reboot phone

4. a new email adress

but no changes in tabjoy
[Galaxy S6 Edge+ Q&A, Help & Troubleshooting] lawrence750:
i think it uses the phone imei
[T-Mobile LG G4] patcal:
I have recently upgraded to MM on my H811. I found out that LG has disabled the feature to mount SD cards as internal storage. OK that sucks but I have lots of space for my other media. I am having nothing but problems. Titanium Backup seems to fail when I set the backup folder to the SD. Quickpic, which I have used for ages keeps giving me this message when I try to delete or modify camera images that are on the SD card. For the record, Quickpic permissions are set to for it to access storage.

Pat
[T-Mobile LG G4] dontbeweakvato:
I was making twrp backups to ext SD card. But it won't restore the same twrp backup from ext SD. Wtf?
[T-Mobile LG G4] patcal:
For now, I went back to 5.1. Too many other problems all solved now that I am back on 5.1 Maybe when we get a few updates in I will try again.