yashsingh1/xdaforums huggingface dataset:
[Transformer TF300T Q&A, Help & Troubleshooting] krunkpirate:
Hello All,

A long time ago I followed the process to get a nvflash backup of my TF300T unlocked bootloader. I have the files on my google drive still as a just in case. Today I went to play hearthstone and found it is unsupported, one user reported it works fine on KatKiss ROM Lollipop 5.0.1_r1. I went to install it and noticed that TWRP is on 2.8.0.3 and 2.8.x is required for KatKiss, I am currently on 2.7.0.1 TWRP. Getting lost in all the noise about bootloader versions and wondering if I need to update that. Can I proceed on my current bootloader as is? Fastboot shows WW_epad-10.6.1.15.3-20130416 (I swear this was a US_ version before I did the nvflash noise.) If I do need to update the bootloader what is the recommended process?

Thanks,
[Transformer TF300T Q&A, Help & Troubleshooting] lj50036:
You do need to update your bootloader to one ending in 27.5 .....

Download the firmware for the 'WW' 'SKU' from the Asus website

Find the blob inside zip file after you extract it twice.....

Flash the blob with fastboot .....

Let me know if I can help along the way .....

Thx Josh
[Transformer TF300T Q&A, Help & Troubleshooting] krunkpirate:
Took the following steps it hit the usual unlocked in the upper right splash screen and went to an ASUS logo with a spinning wheel. Taking a really, really, long time just spinning. Assuming this fails for whatever reason what steps should I take next? How long should I leave it before I take action?

C:\Users\Kelvin\AppData\Local\Android\sdk\platform-tools>fastboot devices

015d25687a2c1e0e fastboot

C:\Users\Kelvin\AppData\Local\Android\sdk\platform-tools>fastboot -i 0x0b05 flash staging blob

sending 'staging' (800931 KB)...

OKAY [139.777s]

writing 'staging'...

OKAY [155.844s]

finished. total time: 295.623s

C:\Users\Kelvin\AppData\Local\Android\sdk\platform-tools>fastboot -i 0x0b05 reboot

rebooting...

finished. total time: 0.020s

Thanks,
[Transformer TF300T Q&A, Help & Troubleshooting] lj50036:
You made sure you got the right 'SKU'

Go here skip to the first fastboot command .....

Make sure you read my comments between the commands .....

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

Thx Josh
[Transformer TF300T Q&A, Help & Troubleshooting] krunkpirate:
Well like I said in my initial post I swear it was US before the nvflash backup stuff. Either way I switched over to fastboot and the bootloader showed the updated version. Installed TWRP 2.8.3.0 and installed KatKiss, its currently in the process of booting. If this fails I'll switch to the guide you provided and update with my results.

UPDATE: rom booted successfully and im in business. Thanks!
[8125, K-JAM, P4300, MDA Vario ROM Development] nottoosmart:
Ok, so with WM6 still in its "testing" phase and a few bugs that just wont seem to go away, I am being promoted at work and it will require me to use my phone as a tool for the job. ie direct push and all. Should i go back to my carriers WM5 release or Stick with WM6 in hopes that they will fix the rumored direct push issues?
[8125, K-JAM, P4300, MDA Vario ROM Development] icezar:
i never got a direct pus problem on wm6... I use my mobile for work and i am using mb edition. I think is quite ok... on Faria`s i got some problems with gprs switching on and off all the time.... strange....
[8125, K-JAM, P4300, MDA Vario ROM Development] nottoosmart:
I've never used direct push. how do I go about setting it up. I can put together an exchange box if needed
[8125, K-JAM, P4300, MDA Vario ROM Development] bradsnw:
I have experimented with all the WM6 releases, and have not encountered any issues at all with push mail and my Exchange 2003 Server. Within a couple of seconds of a new e-mail reaching my desktop, it hits my phone.

I also have my POP3 account check for messages at 1 hour intervals. No probs there either.
[8125, K-JAM, P4300, MDA Vario ROM Development] achick:
I was one of the unlucky ones who did have a problem with push email on Farias WM6 ROM. It would sync the first time the phone was switched on, but then some time later would randomly stop working even though the GPRS connection was still up and Activesync said it was 'Connected' - only a manual resync would get it going again.

I tried multiple radio ROMS, 2.19, 2.25, 2.47 and 2.61 (hoping it was a radio ROM problem) but to no avail. Interestingly, I never had this particular problem with the MB WM6 rom - but that ROM had other issues, so in the end (as always) I've dropped back to Farias 3.3 ROM which is rock solid in every area.

Don't get me wrong those of you who take offence easily - Farias ROMS are great and I'm not knocking him any way - it's just "one of those things" that's probably quirky to my setup. If when he produces a new version, I'll test again.

Andrew
[8125, K-JAM, P4300, MDA Vario ROM Development] Dr Puttingham:
Most odd. Like bradsnw I've never had a direct push problem. This includes the more than 50 individual devices I've setup in the past, the 10 or so that I upgrade on a regular basis and mine. As Faria's tester and Junior Chef in Training my poor lil 8125 has seen just about every ROM variant (and mutant) imaginable, but never a DP problem. (And I've created some near bricking ROM's let me tell you!)

One thing I always do however is to not create my initial AS profile with my PC but on my device directly. (This is the only way I can get my task OTA) and I probably hard reset my device on the shoulder of Interstate 95 or a McDonalds parking lot as many times as I do at home.
[8125, K-JAM, P4300, MDA Vario ROM Development] notyourdaddy:
I've never had an issue with Direct Push/Exchange 2003 while using WM6 either.
[8125, K-JAM, P4300, MDA Vario ROM Development] achick:
I agree - very odd. I've never had push fail before on the multitude of ROMS I've tried - those sort of problems always happened 'to other people' and not me ;^)

I tried all the usual stuff, resets, new partnerships, reloading the same ROM, new radio ROMS, certificates, etc etc etc. But in the end, I had to get the phone working 'for work', so went back to 3.3. Like I said, when Farias next ROM comes out, I'll try it again.

cheers,

Andrew
[8125, K-JAM, P4300, MDA Vario ROM Development] dwny:
There's nothing wrong with your push email.

Connected is good, it means that you have a connection with the server and you're up to date. This is how it shows in WM6

When you see "Synchronized Today" with a time, this means that was the last time your device updated with the server for whatever reason....@ tihs point, if you have signal....do a manual sync.

Again...CONNECTED...is good ......... SYNCHRONIZED TODAY...is ok

If your device doesnt synchronize folders at all :mad: ....you need to adjust your network connections and get the web to work 1st and then push email.

This isn't faria specific, that's how WM6 works.
[8125, K-JAM, P4300, MDA Vario ROM Development] dwny:
You need an exchange account.

I use www.4smartphone.com. It's a paid service that's cheap and I let them deal with the headaches of maintaining a server. The service has been 100% so far, not to try to sell you.

If you have the means and time to set up a box, let me know and I'll help as much as I can.
[8125, K-JAM, P4300, MDA Vario ROM Development] SL:
No problem at all with DP mail. I just give it to the people at IT and they set it up nicely for me. And I have taken it in daily because I keep changing roms!

But I am stopping at Faria's for now
[8125, K-JAM, P4300, MDA Vario ROM Development] achick:
dwny, I appreciate your reply, but I beg to differ. I've been using push mail for a long time now, and I know when it's working or not - I'm not going to bore everybody with pointless detail, but:

I had a working internet connection via GPRS - I could surf using Pocket IE.

It would "automatically" sync my folders via GPRS when I turned the phone on. It would then stop working later.

Manually syncing is not push email? I had set the schedule settings to 'as items arrive' - why would I sync manually?

And as I said previously, I did not get the problem with the MB WM6 rom, nor the PDAviet 3 or 4 and I do not get the problem with Farias 3.3. Mail arrives automatically via GPRS (usually a a few seconds before it hits my desktop outlook) just fine in every ROM I've tried except Faria's latest. But I'll repeat - I'm not in any way 'blaming' Faria. It's just one of those things.

Andrew
[8125, K-JAM, P4300, MDA Vario ROM Development] dwny:
Again...this is how it works in WM6

When your device says "Connected" ... you are up to date.

While there..press Menu > Status and it will tell you when your device last synchronized.

WM5 shows "last synchronized" when up to date

WM6 shows "last synchronized" when not up to date.

What I experienced:

When I get "last synchronized" ... I also don't have internet and everything was working. I go to connections and change the name of the connection and all is well. Try this & see if it works for you.....
[8125, K-JAM, P4300, MDA Vario ROM Development] achick:
dwny, you ARE persistant! :)

"Again...this is how it works in WM6"

But it *wasn't* working!

I could tell it was not sychronizing because I would get 25 emails arriving in my Outlook inbox over period of an hour, and none of them arrived on my PDA! If I simply manually synced, they would all coming flooding in.

But let's not dwell on this anymore - I'm back on 3.3 now. If I find some time, I'll do a fresh download of the ROM and try again.

thanks for you time,

Andrew
[8125, K-JAM, P4300, MDA Vario ROM Development] baarod:
Outlook

First, you get too damn much email. 25/hour? What are you, the president? ;)

Seriously though, something has to be running to be able to get those push notifications. With all the tweaking people do I'm not surprised that things end up breaking. My suggestions are these:

1) Turn off X Button or whatever you are currently using to close rather than hide applications. WM5 and 6 were never designed for the apps to be closed every time. Many have background features that they depend on -- like poutlook. Why do you think it's in your \windows\startup folder.

2) It is *still* in your \windows\startup folder right? ;)

Those are your hints -- all I know is that push worked fine for me as long as I left something there to push to.
[8125, K-JAM, P4300, MDA Vario ROM Development] achick:
President? - lol... I wish... :)

I get automated warnings and messages from databases and servers. And when things aren't running well, I get LOTS of emails.

Yep, poutlook was in my startup.... :p

Anyway, after seeing all these success stories, I downloaded the ROM again (didn't trust the last download) and reflashed. Followed exactly the same procedure as normal (I flash ROMS regularly, so literally have my set routine) and guess what?

Works fine - 'straight out of the box'. I did nothing different to every other flash I've ever done....:eek:

Andrew

P.S. I now have an 'officially recognised' issue with the 2.61 radio ROM. But at least I'm back in the fold...
[8125, K-JAM, P4300, MDA Vario ROM Development] johnnylavah:
i am running the mun rom on tmobile usa and have no problems with exhange mail...push is working 100%

FYI - i am using the 2.61.11 radio rom
[8125, K-JAM, P4300, MDA Vario ROM Development] dwny:
Glad to see a fresh install worked for you.

Be careful with radio 2.61.11, it's known to cause dialpad issues and missed calls with the newer roms.
[Sprint Samsung Galaxy Note 3] R1000:


No login cleared. App/Data nothing bought app 5 min ago for the 3rd time in two years Google play won't remember. That I buy it or other apps free version. Works only help guys help
[Nexus 6 Q&A, Help & Troubleshooting] jonpaterson:
Hello All,

I have noticed that when my BT headset is connected, and I answer the phone with the handset, the screen does not turn off. this works perfectly if I turn the BT headset off. Has anyone noticed anything similar?

Jon
[Nexus 6 Q&A, Help & Troubleshooting] Pilz:
Yep..mine does the same thing. I noticed it when I would get a call while driving. My phone is connected to my car and it would not turn the display off until I hit the power button. I just keep my phone plugged into my outlet (quick charger) so I don't lose battery by having it idle while on a call or listening to music.
[HTC One S] QA Bot:
Q&A for Minfree settings in CM12 Roms

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.

Before posting, please use the forum search and read through the discussion thread for Minfree settings in CM12 Roms. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy! :)
[HTC One S] Elias_67:
Everything works fine. But, after a reboot all the established rights go back. How can I leave permanently?
[HTC One S] derkleinebroicher:
Which rom do you run exactly? And what are the settings, it goes back to? Actually i'm searching for a way, to make settings via an init.d script, which should make them permanently. But this might still take a while - I am a beginner.
[HTC One S] Elias_67:
I have [ROM][5.0.2][21-DEC] CyanogenMod 12 Lollipop . I come all the way and it works perfectly. With the replacement of rights and setting Minfree no reboot or closing app. ( I use free Memory Manager app from Play Store)
[HTC One S] derkleinebroicher:
I've installed the same Rom, in my case the permissions are set to rw-rw-rw. Everything works fine with these settings, so no reason, to change anything Even though I would like to know, why the settings do not persist.
[HTC One S] Elias_67:
I am also a beginner. ) I just wrote rw-rw-rw. But after reboot Memory Manager it can not see and enter the settings. But if you go to the folder and replace it again rw rw rw, everything returns correctly.
[HTC One S] derkleinebroicher:
Did you tap the "Apply at boot" in MemoryManager?
[HTC One S] Elias_67:
Yes, I have it marked.
[Sony Xperia M] mov2day:
Hi All

i Was trying to flash TWRP img file using fastboot after that my Xperia M is not switching on and im not able to connect my phone in Fastboot method to my PC and flash tool is also not detecting my phone. Please help is there any way to recover my phone..

Only thing happening is when i press power button my phone vibrates

Thanks in Advance
[Sony Xperia M] somberchocks:
Which TWRP img file did you flash? Jelly Bean or Lollipop one? Which os version are you on?

Well if your firmware's messed up, fastboot probably won't detect it. Think you need to get stock firmware and flash it via flashmode in Flash Tool but if its not getting recognized at all then that's a dead end.

Did you try reinstalling all the drivers via Flash tool to see if the phone gets detected?
[Asus Padfone X and S] evusas:
[deleted]
[G3 Q&A, Help & Troubleshooting] mustang2012:
Is anyone experienced signal drop out since upgrade to lollipop? I never experienced this in kikat but notice this issue since flashed lollipop rom ( ANDROID HD V 7.4)

Is anyone experienced this with any other lollipop rom and how did you guys fix this?

Thanks in advance :)
[G3 Q&A, Help & Troubleshooting] Showtek1980:
This is a wild guess but if you've flashed a lollipop rom ..maybe your network or phone isn't ready for the update? Just enjoy kitkat and xposed and wait for your network to push out the update.. ;) I'm in South Korea and my device F400k hasn't received the update just yet.. I'm NOT looking forward to Lollipop that much because Xposed isn't compatible with Lollipop just yet :) .. Hope you can find a solution for your problem :fingers-crossed:
[G3 Q&A, Help & Troubleshooting] mustang2012:
That makes sense in way... Thanks for your information :)
[Verizon LG G2] QA Bot:
Q&A for [dev] vs98026a kdz file

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.

Before posting, please use the forum search and read through the discussion thread for [dev] vs98026a kdz file. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy! :)
[Verizon LG G2] LGHomie:
is there way to root without downgrading

I have the same phone you have LG G2 Vs98026a
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] zswielder:
I asked around in 2 different threads dedicated to Safestrap, but I never got any help, so I am making this post. I hope someone can help me. I recently bought Kindle Fire HDX 64GB LTE version. I rooted it using KFHDX ToolKit v0.95 just fine. I disabled OTA update, installed SuperSu, and installed safestrap. It went all fine except safestrap isn't working. If I try to reboot into safestrap, I get a black screen with a momentary noise/flicker(?). It doesn't do anything until I shut it down using the power button. I'm able to boot into Kindle just fine after that. I uninstalled safestrap for now. My OS version is 13.3.2.1. I also tried installing safestrap from apk itself (3.72), but I got the same result. I don't know what to do now.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] yujikaido79:
I am running safestrap 3.75 and updated my system version is 3.2.4 per a tutorial I followed on herehttp://xdaforums.com/kindle-fire-hdx/general/tut-kindle-rooted-otaed-safestrapped-t2954893. You could try the updated versions and see if that makes any difference.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] zswielder:
Is yours LTE version? I learned about that possibility, but I wasn't sure if the firmware posted was for the WiFi version or LTE version. I don't want to flush it if I may lose LTE.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] yujikaido79:
I have heard if you go to the Nexus Rom you may lose it since its only built for the Wifi model. Yes I only have the wifi model. I don't believe it would mess up the LTE by updating though. Its still stock kindle version. Maybe someone with a LTE model can help you further if you are still unsure.
[General Questions and Answers] Nofan Tasi:
Hi all

I own and have owned various android devices. All of them are/were rooted

and ran/run various ROMs.

My question is:

There are always some files in /, which, at first sight, are not part

of ROM zips.

What is their purpose? Is their purpose documented?

I am not asking for purpose of all those individual files but rather wonder which

ones are essential and perhaps ROM independent and which ones are

potential garbage.

For example here are the files in question for

1) gt-i9505 (currently running 4.4.4 aosp)

charger

default.prop

file_contexts

fstab.qcom

init

init.carrier.rc

init.environ.rc

init.local.rc

init.qcom.class_core.sh

init.qcom.class_main.sh

init.qcom.early_boot.sh

init.qcom.lpm_boot.sh

init.qcom.rc

init.qcom.sh

init.qcom.syspart_fixup.sh

init.qcom.usb.rc

init.qcom.usb.sh

init.rc

init.recovery.qcom.rc

init.target.rc

init.trace.rc

init.usb.rc

lpm.rc

property_contexts

seapp_contexts

sepolicy

ueventd.qcom.rc

ueventd.rc

2) sm-g3815 (currently running 4.4.2 stock (rooted))

default.prop

file_contexts

fstab.qcom

init

init.carrier.rc

init.container.rc

init.environ.rc

initlogo.rle

init.qcom.class_core.sh

init.qcom.early_boot.sh

init.qcom.rc

init.qcom.sh

init.qcom.syspart_fixup.sh

init.qcom.usb.rc

init.qcom.usb.sh

init.rc

init.ril.rc

init.ril.sh

init.target.rc

init.trace.rc

init.usb.rc

property_contexts

publiccert.pem

seapp_contexts

sepolicy

sepolicy_version

ueventd.qcom.rc

ueventd.rc

3) s9714 (currently running 4.1.1 stock (rooted, deodexed, zipaligned))

fstab.qcom

init

init.carrier.rc

init.container.rc

init.environ.rc

initlogo.rle

init.qcom.class_core.sh

init.qcom.early_boot.sh

init.qcom.rc

init.qcom.sh

init.qcom.syspart_fixup.sh

init.qcom.usb.rc

init.qcom.usb.sh

init.rc

init.ril.rc

init.ril.sh

init.target.rc

init.trace.rc

init.usb.rc

property_contexts

publiccert.pem

seapp_contexts

sepolicy

sepolicy_version

ueventd.qcom.rc

ueventd.rc
[General Questions and Answers] zelendel:
None of them are garbage. They all relate to working different things on your device. Leave them alone.
[General Questions and Answers] Nofan Tasi:
and are they ever updated?

also can one say they are ROM independent or does each one incrementally originate from some (previous) ROM?
[General Questions and Answers] zelendel:
They are rom and device dependent. They get wiped on every rom flash
[General Questions and Answers] Nofan Tasi:
Interesting, there is not a single rom update (neither one that copies files nor one that flashes partitions) I looked at so far that would touch files in / (such as the *.rc ones)

I must be missing something obvious. Can you give an example?

Could it be these files are specific to ramdisk in boot image?
[General Questions and Answers] Nofan Tasi:
seems files in / come from ramdisk indeed :silly:
[Windows Mobile Development and Hacking General] tipok:
ZUNE created by using WindowsCE but it's M$ signed and not hackabke, but:

If we playing asf files (created by VLC) after little time player just "cold" reboots without any messages. Maybe we can write "hallo world application" inserted in asf file. And rewrite recovery.bin bootloader?
[Android Q&A, Help & Troubleshooting] tbolt1:
Hello everyone

I have a Samsung galaxy s4 I 9500 it is rooted but will not allow me

To install cwm or twrp or anything that might help . I have tried

Rom manager, rom install and everything else I could think of.

I cannot program, have no computer and I have run out of ideas.
[Moto G Q&A, Help & Troubleshooting] TravisTX:
I have a Moto G XT1034 that is stuck in a boot loop. I am not able to get to fastboot or recovery, it just keeps rebooting over and over again. It started at about 50% battery, now it's at 0% even though it's been plugged in for most of that time. This device has an unlocked bootloader, is rooted, and has been running kitkat for almost a year. Nothing that I can think of has changed today.

Things I have tried:

Holding vol up + vol down + power for 4 seconds

Holding vol down + power for 4 seconds

Holding power for 120 seconds

Letting the battery drain completely, and then plugging it in. It just starts with the reboot cycle again.

Any ideas?
[Moto G Q&A, Help & Troubleshooting] jman1234:
That doesn't seem right. Try holding volume down and power for longer than 4 seconds.
[Moto G Q&A, Help & Troubleshooting] TravisTX:
Here's a video of me holding vol down + power for 120 seconds, as advised in Q28 of this sticky. Doesn't get me to fastboot.
[Moto G Q&A, Help & Troubleshooting] TravisTX:
I have a second moto g here, and have swapped the batteries, so the broken one has a fully charged battery. The bootloop continues when fully changed. Video here. Holding vol down + power for a few seconds, or 120 seconds also doesn't do anything when fully charged.
[Moto G Q&A, Help & Troubleshooting] seshuganesh2011:
power off device....then fastly press volume down + power button for 4 secs and release

---------- Post added at 02:57 PM ---------- Previous post was at 02:52 PM ----------

flash costom recovery....using adb fastboot command
[Moto G Q&A, Help & Troubleshooting] TravisTX:
Thanks for the replies.

I am not able to power it off. I have found two ways of "powering off" which are to either let the battery drain, or to hold buttons during the black screen part of the boot loop.

If I wait for the black screen part of the boot loop, and quickly press vol down + power, it will stay black as long as I'm holding those buttons. If I hold them for 4 second and release, it then enters the boot loop a few seconds later. If I hold them for 120 seconds and release, it does the same thing a few seconds after releasing.