yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] ROFLpwn:
I recently bought a brand new Lg g3 phone form Verizon. Before I rooted, my data seemed to work great. The phone came with Lollipop 5.0.1. I rooted it using the one click root and installed Jasmine rom v8.0. Everything seemed to be working fine until I tried using my data. When I turn it on, The symbol sits on the top of my screen. I am still able to make calls and messages but I cannot use any apps that require internet unless connected to wifi. I turned airplane mode on and off then the arrows of the 4GLTE symbol flashed but then stopped. I went into the settings and specified my APN which is VZWINTERNET but that didn't seem to do anything. I turned off my phone and took the sim card out and put it back in but that didn't work either. Anyone know how to fix this?
[Android Q&A, Help & Troubleshooting] huber.francesco:
Try to reset the phone. volume up+Home button+Power button.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] tropicallazerbeams:
Hey everyone I recently bricked my kindle fire because I was not careful enough about loading a custom ROM. Long story short I followed the instructions for a kindle fire HD7 instead of HDX7. Luckily, Amazon's customer service is WAY better than their operating systems because I was able to return my bricked device and get a new one within 3 days!

That being said, I was wondering if anyone here could provide a good, clear guide, or at least overview of the steps I need to take to install cyanogenmod 11 or some other custom ROM on my kindle fire hdx 7. I have been searching for a decent guide, but haven't been able to find one. Links to actual resources would be even better. I don't mind searching on my own, but I need at least enough information to not screw up my device again. Any help anyone could give me would be very appreciated! Thank you!

and just for reference my device is Kindle Fire HDX 7" THOR currently running FireOS 4.5.5
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] DB126:
Amazon support is usually quite responsive. Be aware device replacement for software issues under warranty is a one-time courtesy. You own the replacement (actually a refurb).

High level steps required to prep your device for CM11 (or Nexus v4):

- rollback to FireOS 3.2.8

- upgrade to FireOS 4.5.2

- root with Kingroot or other method

- block OTA (over-the-air updates) - step #1

- install Safestrap v4

- flash a Safestrap v4 compatible rom (currently CM11 or Nexus v4)

The above links are NOT click and execute! There are no step-by-step guides, helpful videos, comprehensive tutorials (despite titles suggesting otherwise), etc. You have to dive into the forums and wade through hundreds of posts (many off-topic/extraneous) to get feel for the detailed procedures. There are some outstanding posts but you'll need to find them. Be aware some steps carry significant risks including a full-on brick from which there is no recovery. Read instructions carefully and be sure to ask questions before taking action.

A few tips:

- download everything you need in advance storing them in uniquely named folders. Some steps mandate your HDX be isolated from any networks. While most items can be retrieved via USB tether it is much easier to simply head for the folder on your HDX when the file is needed.

- understand what USB debug means and know how to enable in FireOS

- install minimal adb + fastboot and learn basic adb commands such as 'install' and 'push'

- ES File Explorer is your friend; alway keep a copy of the apk on your device for installation when needed.

- never perform a 'factory reset' unless specifically advised to do so by someone experienced with HDX devices; many sad tales begin with 'I did a factor reset ...'

Good luck.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] tropicallazerbeams:
Wow, awesome, this was exactly what I was looking for. I just finished installing CM11, the whole process took me about an hour now that I understand what to do. Thanks for the guide, I have a feeling this will help more people than just me. I would add one more step for anyone else looking: When installing your custom ROM, go ahead and install gapps (https://wiki.cyanogenmod.org/w/Google_Apps) so that you can access the google play store from your new ROM.

Here are some decent video guides on how to use Safestrap in case anyone needed help with that:

(https://www.youtube.com/watch?v=K6fPF5UZsWw) General Safestrap usage

(https://www.youtube.com/watch?v=xR0WXCITq2Q) Specifically how to install a custom ROM

So I have just a few more questions now, CM11 can only access about 8 out of the 16GB on the device. Is there a way to expand that memory to the entire 16GB? I should probably just be satisfied with my progress so far, but I honestly would not miss the stock fireOS if it would give me more space.

When/if I need to update CM, do I need to flash each and every update via recovery?

Thanks for all the help so far, you da man!
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] DB126:
Based on a few reports CM11 works best in the stock slot. Seems WiFi won't enter a low power state in secondary slots resulting in excessive battery drain. Thoughts:

- backup up stock slot in SS recovery. Save archive off-device.

- backup cm11 slot, switch to slot slot and restore

- after stock slot w/cm11 confirmed ok delete secondary slot(s)

You'll have access to the full 16GB with ability to restore FireOS if needed.

---------- Post added at 08:00 AM ---------- Previous post was at 07:55 AM ----------

Thanks - nice find.

[MENTION=5749760]ggow[/MENTION] - possible add to SS v4 OP or separate thread for newbies.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] ggow:
- Added links to the OP of Safestrap 4.0.1 thread :)
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] tropicallazerbeams:
Okay I ran into one more problem. I followed your instructions on switching ROM-1 to ROM-STOCK, but when I was restoring the contents of ROM-1 to ROM-STOCK, the procedure failed. It didn't say why, it just showed up in red text saying "failed". So it rebooted, but since ROM-STOCK was selected and a restoration had just failed on it, nothing happens when I boot up. It is stuck on the grey kindle fire logo. Is there a way that I can get into safestrap?
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] DB126:
Well crap - that's not good. The symptoms suggest Safestrap v4 may have been damaged. I assume you tried waiting, rebooted multiple times, powered off/on, etc. Is there any indication Safestrap (or any environment beyond the grey boot screen) is present?
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] tropicallazerbeams:
hehe, looks like I may have bricked my 2nd Fire....Tried waiting, rebooting and everything, still broke..... So Safestrap never really appeared to be damaged when it was rebooting after the installation failure. If I had to guess, I would say that ROM-1 and safestrap are totally fine, the only problem is that I can't access them because ROM-STOCK is selected. So what if I got my hands on one of those factory fastboot cables, do you think I could boot straight into fastboot, change my boot options to boot into recovery or my ROM-1?
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] jeryll:
Sorry, with locked bootloader fastboot mode on HDX is practically useless, factory cable won't help you. Did you by any chance when you created ROM-1 slot changed data partition to bigger size? That would explain why restoration to STOCK slot failed. If you can't enter safestrap recovery at boot time, that means it IS damaged.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] tropicallazerbeams:
Yeah I did change the partition size when I created ROM-1. Thanks for all the help fellas, but it looks like I am right back where I started. Good thing my tablet was a gift :P
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] alberto1414:
Im going to follow the process since I have at 4.5.2 rooted before.

How do I create the rom-1 to later install on stock without brick?

Or I should install directly to stock without doing rom-1?
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] DB126:
Review the video in the Safestrap v4 OP for general usage info. For a variety of reasons I recommend only using the stock slot in SS v4. You should create a backup of the stock slot containing FireOS before flashing a new rom. Keep a copy off-device.

http://xdaforums.com/showthread.php?p=61410598
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] alberto1414:
When being on safestrap after back up the stock slot.

do I have to do anything before flashing the new rom? like some wipes os what?

Can help with steps?

1. wipe? what to wipe?

2. flash?

3. factory reset?

I saw the instructions on the hdx nexus v4. but it doesnt say anything before flash. I think they talk about a new rom slot. but mine has the fire os.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] DB126:
I suggest you do some additional reading to gain confidence in the process. Briefly:

- backup the stock rom slot before taking any other action (use backup option within Safestrap v4)

- nothing needs to be done before flashing a new rom (Nexus v4 or CM11 only)

- each rom has its own requirements but in general performing a factory reset from within Safestrap is recommended. This is NOT the same thing as doing a factory reset from the Kindle recovery menu. Never to that unless instructed by an experienced member of the community.

While others may be willing to do so I will not provide a 'step-by-step' as all the information you need is one of the following threads. Reading and gaining confidence the the best way to avoid a mistake that could cripple your device. Community members are happy to answer specific questions as you become familiar with the details.

Safestrap v4

Nexus v4

CM11 for HDX (Safestrap build)
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] m1kemyer5:
Read through posts now, thanks for the help
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] Cl4ncy:
Just one note: if it says factory reset in the installation notes it's the standard wipe only, i.e. you open the wipe menu, and swipe to wipe - do NOT go into advanced wipe!

Now it so happens [MENTION=5749760]ggow[/MENTION] implemented a System-wipe-protection in Safestrap v4 to prevent more bricked devices, but usually you should NOT have any reason to open the advanced wipe menu. Wiping System in Safestrap v3.7x is lethal (doesn't concern Safestrap v4 users, but can't be mentioned often enough).
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] alberto1414:
Hi to all looking to have a custom rom, I recommend CM11 because it gives you a safe try and the wifi works.

Many new people trying nexus v4 are stuck.

If you like me, new to these things go with CM11.

I started with fire os 4.5.5 and downgrade to 3.2.8 to later upgrade to 4.5.2 , root and safestrap 4. create a new rom slot with default(no modification on size). to later install there the CM11 and everything without touching the stock slot of fire os 4.5.2.

If any one wants my personal experience, simple PM I'll be glad to help. just in this particular situation I just explained.

Thanks to the dev that made this posible.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] DB126:
Quick clarifications to [MENTION=2454115]alberto1414[/MENTION]'s comments:

- both Nexus v4 and CM11 run equally well in the stock (default) slot of Safestrap v4. There is no significant difference in stability or performance.

- creating one or more secondary slots allows multiple roms to reside on the device at the same time; a reboot is required to switch between roms.

- CM11 can function in a secondary slot; Nexus v4 and FireOS v4 can not as WiFi only works in the stock slot.

- flashing either Nexus v4 or CM11 to the stock slot overwrites FireOS; however this is not a problem as FireOS v4.5.2 can be restored at a later time either from a backup created by the user or as a 'fresh' install using a custom version available here.

- individuals who flashed Nexus v4 to the stock slot are not "stuck"; they can restore or reinstall FireOS 4.5.2 as outlined above.

- creating/using a secondary slot in Safestrap v4 significantly increases battery consumption. Root cause has yet to be identified but it appears the device never enters 'deep sleep' when secondary slots are in use.

- permanent device storage is shared across slots. This can become a problem on 16GB or 32GB devices. In contrast, all available storage is available to the stock slot if secondary slots are not created.

- Safestrap compatible roms are created/tested in the stock slot. Functionality and stability in secondary slots is not assured.
[Sprint Samsung Galaxy Note 3] ddarkone:
hi all, just got phone today, I know it's 2 notes behind, but this one was affordable, I have read and searched for 3 hours and no luck with root. Odin want recognize my phone, I've been rooting and flashing ROMs for 7 years, and I have never encountered this issue with Odin. But this also my first time using Odin with windows 7. Can anyone help me root, my phone is on 4.4 with NK4, thanks.
[Sprint Samsung Galaxy Note 3] ddarkone:
got it solved
[Sprint Samsung Galaxy S III] a13013:
Decided to root my s3 sph l710t using the guide here. Downloaded evverything and extracted etc. The odin website said i had to flash twrp first so i started following the steps but after i clicked on start odin froze and nothing is happening and my phone is still connected in dowload mode and i dont know what to do. Someone please help me!
[Sprint Samsung Galaxy S III] a13013:
fixed

I ended up doing a battery pull -- which initially caused some concern when it still showed the "downloading do not shut down target screen -- but one the screen went black, I pulled the USB cable, booted into download mode but selected "no" and my phone booted back up as normal. Crisis averted!
[Galaxy Note5 Q&A, Help & Troubleshooting] PrsnlCrcl:
I was playing around with the camera today and took a couple of photos using selective focus. When I view the files in the gallery, there is an icon on the photo showing that it is a selective focus photo. If I click on that icon, I get an error message that says "all actions associated with this action have been turned off, blocked, or disabled. I have disabled some packages, but didn't think I blocked anything that should affect this. Can someone let me know what happens when they click on the icon for a selective focus photo? Thanks in advance.
[Galaxy Note5 Q&A, Help & Troubleshooting] rlsroufe:
You disabled com.sec.Android.ofviewer (out of focus viewer). Re-enable it.
[Galaxy Note5 Q&A, Help & Troubleshooting] PrsnlCrcl:
Thank you so much! I guess that makes sense, now...lol!
[Oppo R7 Plus] Nomuto:
I have my R7 plusf bootloader unlocked and install TWRP recovery.

After install my phone keep boot to TWRP not into system.

Now I want to go back to stock firmware.

I have stock firmware file to flash but have to flash from stock recovery.

Can someone provide stock recovery.img or point out where to download or teach me how to extract from stock firmware (If possible).

To get back my phone to work again.

Thank you very much and sorry for my bad English.
[Oppo R7 Plus] Nexus5-32GB:
http://community.oppo.com/en/forum.php?mod=viewthread&tid=41243&extra=
[Oppo R7 Plus] Nomuto:
Thank you very much, but that is for R7f not R7 plusf
[Oppo R7 Plus] Nexus5-32GB:
oh, sorry, my mistake. I am still waiting for my own OPPO R7+ so cant help you yet :(
[Oppo R7 Plus] Mulham82:
Dear Nomuto,

Please find the below link for the required stock recovery image.

http://community.oppo.com/en/forum.php?mod=viewthread&tid=41969&extra=

Thanks.
[Oppo R7 Plus] vahid123456:
@Mulham82 The link does not work, do you have any other working link for the stock recovery image please.

Thanks.
[Nexus 6 Q&A, Help & Troubleshooting] tjlmbklr:
I see this annoying error whenever i am in TWRP. I thought I had it resolved when I flashed the stock ROM then flashed my current run CM-12.1-20150902-NIGHTLY-shamu obtained from Cyanogens website.

Then today I let it run the latest OTA and forgot I would lose root. So I attempted to root again only get get stuck at the boot screen. I eventually did a dirty flash of the same CM 12.1 and now I am back to normal and I was able to root again. But I still get the error E: Unable to mount storage.

Also, I am now also unable to see my Nexus in Windows to explore Internal Storage but was able to before I tried rooting.

Thanks in advance.
[Nexus 6 Q&A, Help & Troubleshooting] prdog1:
Sounds like a good time to do full wipe and clean install. Including TWRP and root.
[Nexus 6 Q&A, Help & Troubleshooting] tjlmbklr:
That's the thing, I thought I did all that properly and then flashed the latest CM 12.1 but noticed last night after a failed root that it is now giving the error again.

Would using my backup after I flashed the stock ROM cause the error to come back? I am just looking for the easiest way to avoid reconfiguring my phone and apps again.
[Nexus 6 Q&A, Help & Troubleshooting] prdog1:
Good chance it is that CM12 borking it. Flash anything you want. It either fixes it or it don't. Can always flash back to stock to troubleshoot. :cool:
[Nexus 6 Q&A, Help & Troubleshooting] scryan:
Are you encrypted, with a password to decrypt on boot?

If you have like a swipe password , when rebooting into TWRP you will never the normal android to allow you to enter your password, instead you *should* get one in TWRP, however it will just prompt you for an alphanumeric password.

If you cancel out of that, or enter the wrong password (or don't have an alphanumeric password to enter), I believe it gives you this message... and obviously will fail to mount the encrypted partition.

If this is the case, boot back into system, turn off all passwords/security and it should work fine (no need to decrypt)
[Nexus 6 Q&A, Help & Troubleshooting] tjlmbklr:
I am not really sure what this is so my guess is now. I do have my phone set with a 'pattern unlock to boot and unlock the phone. How do I tell if I am encrypted?
[Nexus 6 Q&A, Help & Troubleshooting] scryan:
Your encrypted if you did not install a kernel that supports no forced encryption, the reformat your user data partition via fastboot,

The phone is encrypted by default.

the fact that your device requires pattern unlock at boot, and not just to unlock is a pretty good indicator, but try going into security and select encrypt phone. If it does not give you warnings, remind you to charge and offer to let you encrypt, it is because you already are. Turn off the pattern needed to boot at least, if not any unlock security in general before rebooting to recovery to avoid this error.
[Nexus 6 Q&A, Help & Troubleshooting] tjlmbklr:
Well I haven't changed my kernel and it says Encrypted in my settings. So I could potentially stay on my current setup and resolve my error if I install another kernel?

So here's what I hope will be an easy answer, what is the best method to flash a kernel? I have only tried it once and failed since my phone failed to boot afterwards.

Any recommendations on which kernel to use with CM?

Thanks for the help.
[Nexus 6 Q&A, Help & Troubleshooting] scryan:
No.

And CM comes with its own kernel, that does not force encryption.

The kernel is not "encrypted" or "decrypted", the stock kernel forces encryption, others don't. But if your encrypted, you are encrypted until you reformat userdata (obviously this wipes phone) so that it is not encrypted.

On encryption:

https://wiki.archlinux.org/index.php/Disk_encryption

(not related to nexus, other then it explains encryption, and nexus is encrypted)

You don't need to disable encryption, but obviously since you have your phone set up to require a pattern supply the decryption key to the system, and your booting into twrp BEFORE you can supply the key for decryption... twrp is not going to have any way to read the encrypted partition. Just turn the security off before rebooting to recovery.

Alternatively you can look up threads here on decrypting your phone, and follow those instructions. You will get a very minor performance boost too... but it does mean that if your phone is lost or stolen your data is a little more accessible.
[Nexus 6 Q&A, Help & Troubleshooting] tjlmbklr:
Thanks. I hope to figure this all out tonight.
[Nexus 6 Q&A, Help & Troubleshooting] scryan:
The thread on it is a little confusing IMO, maybe just me.

Just remember encryption is about how the data is stored on the partition NOT a setting in the kernel. The kernel only comes into play because the kernel used stock on the nexus 6 has code to check if you are using encryption, and if you are not it forces you to encrypt your data before it boots.

So step one is make sure you have a kernel that does not force encryption. I have not seen a 3rd party nexus kernel with encryption set to enforced, that would be weird.

Step two is to actually go ahead and make your user data partition not encrypted. This has to be done by reformating in fastboot, see tutorial thread for commands. When you reformat, by default the partition will not be encrypted.

Just make sure that when you an update you don't flash the stock kernel and boot, because this will wipe your device when it forces you to encrypt (You could probably power down or cancel some how? Have never tried...)

This would most likely happen if you ran stock, and you fastboot flashed a new system and boot (boot contains kernel)

Alternatively, don't mess with any of this. You don't need to be unencrypted to mount your data in recovery, you just need to set up security in android to not require any kind of pin to boot (I used to just turn unlock to swipe instead of pattern before I wanted to use recovery). There is some performance lost with encryption, but they vastly improved encrypted performance with 5.1.1, and not being encrypted only gives you a tiny bump in performance. just A LITTLE more snappy imo.
[Nexus 6 Q&A, Help & Troubleshooting] prdog1:
LeanKernel decrypt is an option as it should be in all Kernels and is one of the better ones. The top kernel developers make it an option. Many noobs post unencrypted kernels where they only change the ramdisk and there is no other option. Can have performance and encryption as you say especially with the Google code updates. :cool:
[Nexus 6 Q&A, Help & Troubleshooting] scryan:
Super random and unrelated plug for leankernel, but OK thanks. :good:

There are plenty of popular kernels, I have found Zen good, many like Elite and Hells Core as well.
[8125, K-JAM, P4300, MDA Vario General] freeyayo50:
For the past week and a half, TimeWizard.exe has been causing me many problems. I regularly get timewizard notifications errors on soft resets and coming out of standby. And when i get the errors, I get about 5-8 of them at once.

Even after doing a hard reset and than installing several applications, I get this problem.

I installed Memmaid v2.0 and looked at the notification queue. There was about 20-30 entries for TimeWizard.exe. Most of them were under Time Based. I deleted all the duplicate and dangling entries.

I currently have SPB Time v2.1.5 (build 949) installed. Could this possibly be the source of the problem??

*Note*I had this version installed for a couple months before the recent hard-reset and had no problems.

Also, what does TimeWizard do??? Do I really need it??
[8125, K-JAM, P4300, MDA Vario General] freeyayo50:
UPDATE:

So far, since my last post, I have not had any problems with timewizard.exe. I have the PA v1.61 installed and have not seen a problem (which i thought it was). There are 2 more apps im considering that might be causing the problems...SPB Time & Slide2Unlock.

I will be installing Slide2Unlock next.
[Windows 10 Mobile] Knu2Lav:
I have read somewhere that you can tweak the registry on the Lumia 930 so that you can ad an extra column of tiles, just like on the large screen devices like the 1520. Since the 930 has the same resolution as the large screens, it should not be a problem.. I am not familiar with editing the registry, so I was hoping that someone else might know how.. :)
[Windows 10 Mobile] ca_guri01:
Try this http://xdaforums.com/windows-10/windows-10-mobile/wptweakers-2015-08-17-added-5th-quick-t3180474