yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Q&A, Help & Troubleshooting] Chromium:
Sounds like somethings wrong with your recovery. Get into the bootloader and reflash TWRP using "fastboot flash recovery FileNameOfTWRP.img"
[Nexus 5 Q&A, Help & Troubleshooting] Synyster06Gates:
Would using flashify work here?

It's been a recurring theme on the PAC forum
[Nexus 5 Q&A, Help & Troubleshooting] Chromium:
Yea that should work too, but if not, fastboot is the way to go.
[Nexus 5 Q&A, Help & Troubleshooting] Synyster06Gates:
EDIT : Very very strange. Flashing TWRP again via Flashify got it to work. It seems something in PAC Rom is corrupting the recovery. I think if I get this all worked out then I'm going to have to go back to DK until it's all worked out. I wish there was another ROMs with all the same features as these two but got updates (whereas DK doesn't any more) and is stable enough to DD (lots of FC with PAC).

EDIT 2: Just tried to reboot into recovery again. After booting teh ROM just for a few minutes the recovery was corrupted. I can't access internal memory from recovery any more, even if I get it to boot. It doesn't make any sense as the ROM has full access to it all.

To be clear, TWRP says Internal Storage - 0
[Nexus 5 Q&A, Help & Troubleshooting] GUGUITOMTG4:
Here could be the solution. http://xdaforums.com/showthread.php?t=2513701

Flash the cache.img

if it wont work, will have to flash-all
[Nexus 5 Q&A, Help & Troubleshooting] Synyster06Gates:
That worked! Thank you!

I actually used to go around the Q&A forum telling people to do just that when they were having issues with wiping on early TWRP versions. Surprised I didn't think to try it. All back on DK now and hunting for a new ROM. :victory:
[Nexus 5 Q&A, Help & Troubleshooting] numel007:
Sounds like you solved it, but I think you could've also done an adb reboot recovery command. Not sure if that works though since I usually only use fastboot.
[Nexus 5 Q&A, Help & Troubleshooting] Synyster06Gates:
After flashing teh recovery again, I could get INTO it, but the data was not showing up so I couldn't actually do anything from within TWRP. It read I had 0mb internal storage.
[Xperia Z1 Compact Q&A, Help & Troubleshooting] kuzibri:
[SIZE=+2]This thread has been created for Questions & Answers/Troubleshooting[/SIZE]​

[SIZE=+2]Specific to LiquidSmooth Amami[/SIZE]

LiquidSmooth Amami[/COLOR]

Please feel free to share issues, questions and offer help

It is always best to thank a ROM OP, in lieu of simply posting "Thank you".

Please keep discussion focused, on the topic described in the OP

​
[Xperia Z1 Compact Q&A, Help & Troubleshooting] slonn:
Is it possible to choose a camera other than stock on the lock screen? I use Snap Camera instead of stock

--

Sendt fra Z1C
[Xperia Z1 Compact Q&A, Help & Troubleshooting] Sithra:
GPS no longer works

Love this ROM but it appears that something is interfering with my GPS

Working fine using - Z1C-Unofficial-DooMKernel-v21

Then flashed LS-KK-v3.2-2014-10-04-amami & GPS no longer works

I have tried a later release, but this caused problems with the onscreen navigation not working properly (Home did not return Home!)

Any suggestions as to where I should look for answers?
[Xperia Z1 Compact Q&A, Help & Troubleshooting] CyborgCygnus:
Gesture Typing/Keyboard Sliding minimizes the keyboard.

When I try to slide over letters to spell a word the keyboard will minimize it self as soon as I start sliding & I'm unable to use that function. Would it be a problem with the settings or the Slim Gapps I installed?
[Xperia Z1 Compact Q&A, Help & Troubleshooting] Varset:
Quiet hours settings for first ring

Hi, guys!

Tell me please, how set not two (three, four, five, six) ring in incoming call bypass, and one? First ring for starred contacts accessed call and notifications?

Sorry for my english :)
[8125, K-JAM, P4300, MDA Vario General] gizm0luvsu:
ok i was wondering is there any other way to sync mp3 or movie files to my wizard other then wmp. It lags soooo bad.
[8125, K-JAM, P4300, MDA Vario General] nolodude:
You can always open My computer -> Mobile device and copy them over.
[Galaxy S 4 Q&A, Help & Troubleshooting] Gab!:
Hello Xda community,

Personally i own an unbranded GS4 i9500( currently i have Android Jellu Bean) and i wanted to know which version of kit kat is the best to update to, since there are many options in sammobile.

- Country: India

PDA: I9500XXUFNB3

CSC: I9500ODDFNB3

And the rest are from different countries(Trinidad and Tobago, Saudi Arabia, Vietnam, Thailand, Malaysia, Singapore, Indonesia) but they have the same PDA and CSC, unfortunately it isnt released in my country yet...

PDA: I9500XXUFNB7

CSC: I9500OLBFNB4

Thank you in advance (:
[Galaxy S 4 Q&A, Help & Troubleshooting] Joku1981:
The best u can do for avoid problems is:

1- Conect it to Kies 3 for know ur code region. CSC are the 3 letters btw parenthesis. The list of codes for region is HERE

2- Wait the update for ur code region. Why? Each country is different (some have LTE, others only 3g, differents modems, etc).

3- If its try for try.... select the one u wish but take care of the step 2 :highfive:
[Galaxy S 4 Q&A, Help & Troubleshooting] exynoss:
Indian one is quite stable and battery friendly.
[Galaxy S 4 Q&A, Help & Troubleshooting] Gab!:
Im from Argentina, is it ok if i flash the indian one? i doubt that the Argentinian firmware will be released any time soon..
[Galaxy S 4 Q&A, Help & Troubleshooting] juanmoller:
Both are safe

As the i9500 does not have LTE, is safe to flash both. I did saw some improvments in phone calls and time to do the call in the indian version from the latest Omega Rom. The v18 was based on Russian version and v19 is based on indian.

Hope this help.
[Galaxy S II Q&A, Help & Troubleshooting] ian619420:
Has anyone drop test i9100 s2?
[Galaxy S II Q&A, Help & Troubleshooting] MistahBungle:
You first.
[Galaxy S II Q&A, Help & Troubleshooting] Paul_Kolanjian:
What a thread :p

Well, since the Galaxy S2 comes with Gorilla Glass, the compression of the glass's material is too good to break that easily. I accidentally dropped my phone on a rocky road, thought I broke the glass but all what happened was scratch the phone's screen protector. Don't try doing absurd moves or intentionally dropping your phone, unless you don't need your phone anymore, go for breaking it :p
[Galaxy S II Q&A, Help & Troubleshooting] MistahBungle:
You done spamming the board/getting your post count up yet ? :rolleyes:
[Galaxy S II Q&A, Help & Troubleshooting] Paul_Kolanjian:
I've made this account a year and a half ago since I wanted to report a major issue on a ROM back then. However, I never used it and rather made another account due to forgetting the account's every single information (including the email). So, dear "Senior Member" MistahBungle, I was once a Recognized Contributor 2 months before losing the account, instead of bashing useless threads and spilling your happiness and joy, try and help someone out, but thanks for your respect fellow user :cowboy:
[Galaxy S II Q&A, Help & Troubleshooting] Vivek_Neel:
But he is increasing his post count only by helping members in f&q section. :)

Not posting in off topic threads.
[Galaxy S II Q&A, Help & Troubleshooting] andrewwright:
Lmao. Rc and you forget you're email??!! Someone's talking Billy :rolleyes:

Also look on YouTube for drop tests as there are many.
[HTC Sensation XL] skkrilec:
Hello i have a problem with my htc sensation xl. i have deleted all data cache partion and system files so i have no os instaled and i'm stuck on boot logo. My pc can't recognized the phone thru the usb cable. I have instaled twrp and bootloader and also have unlocked bootloader. I have try many usb drivers,adb drivers and fastboot drivers. I don't know if this will help but here is my radio nm: 383160016_M.
[Motorola Atrix 2] Pikachu8119:
Hi, i have problem with jbx, on any version of jbx kernel i have issue, after ending a call my phone stucks on the black screen. Does anybody have this too?
[Motorola Atrix 2] PhoenixNghi:
This is a common bug.

Go to trickersmod > turn off Hotplug. This may help.
[Galaxy S 4 Q&A, Help & Troubleshooting] vampire_f00d:
Hi all,

Are there any S4 rooms currently available that support reverse tethering? I used to have an HTC One X and found this to be a godsend but have been unable to find a rom with native reverse tethering, was hoping someone may have some suggestions. My carrier is o2 UK any help is greatly appreciated thanks.
[Galaxy S 4 Q&A, Help & Troubleshooting] exynoss:
Reversed tehering not available in stock rom but is a app available in xda itself. Few months back its posted In portal also.
[Galaxy S 4 Q&A, Help & Troubleshooting] vampire_f00d:
I know it's not available in stock, which sucks, but I've read that if it can wifi tether then it should be able to reverse tether. Was wondering if any of the awesome devs had made any custom roms that had this included.
[Galaxy S 4 Q&A, Help & Troubleshooting] exynoss:
No no dev developed that type of rom.

accidentally thank you [emoji12]
[Samsung Galaxy Nexus] kansasboy001:
I am not a developer for this rom, I just found it and am sharing.

Cyan Fox is based on Cynogen Mod 11,but with some performance improvements and some ui changes.

Check it out here

http://cyanfox-rom.com/downloads/?folder=toroplus/
[Samsung Galaxy Nexus] cmoG530:
Do you know what features it has? Thanks BTW. :)
[Samsung Galaxy Nexus] kansasboy001:
All features of cm, just performance and stability tweaks.
[Sprint Samsung Galaxy Note 3] KoolCharisma:
Hey guys, I don't post here often, but I'm not new to this. It was through this forum that I first started rooting with mfy s3.

I just got a note 3 through Sprint. I've gotten used to getting off the grid, so I immediately jumped to root it. I decided on Jellybomb after reading some reviews. Then I downloaded everything necessary to make the jump: Odin, 1.85 and 3.09, jellybomb, cwm 6.0, twrp 7, auto-root, and the original roms in case I had to hop back.

First I went with Chainfires auto-root. I didn't seem to have any problem flashing that. The problem came with flashing twrp and the new rom. I can't remember which one was giving me trouble (I've been fighting it almost a week now). Somehow some way the phone has been stuck in an autoboot that says "seandroid not enforcing" and either "warranty bit: recovery" or "warranty bit: kernel". I tried new kernels. I tried things in different order. I can get into recovery but only after going immediately after autoroot. Even there you have a broken android.

Please help. I've been without a phone for a week.
[Sprint Samsung Galaxy Note 3] micmars:
[MENTION=5211230]KoolCharisma[/MENTION], first off, you're not in bad shape at all.

Let's start your weekend with this in your rear view mirror. What rom was on your phone prior to doing any of this, Jellybean MJ4, or KitKat NAB?

Knowing the above will dictate how you get to where ya want to be...

Sent from my SM-N900P using Xparent BlueTapatalk 2
[Sprint Samsung Galaxy Note 3] KoolCharisma:
Alright!

Thanks for the help! I have a girlfriend, who is very upset with me, because she thinks I was very irresponsible to break it.

Ok, the phone originally came with Jellybean, but three days later, it did a system upgrade and I got kitkat.

It's possible maybe JellyBomb just wasn't designed for kitkat? I didn't see anything to suggest that.

The order of things was:

1: I used the autoroot or Odin to flash a new Recovery. Unfortunately I can't remember which.

2. The second was whatever I didn't do the first time.

3. From that point I tried to use the recovery to instal JellyBomb and as far as I could tell, it worked.

4. Reboot. Now it's stuck in a loop. it either kicks up the seandroid enforcing warranty: kernell. Or "" recovery.

5. I can get it into recovery by running a second autoroot, but it won't let me successfully install a ROM.

6. I can also go into download mode, but ODIN says fail on everything accept installing the autoroot.

7. I've gone ahead and tried going back to stock, but the tars are flawed or something.

So to summarize it, I've been running in circles and I'm starting to sort of loose track of what I've tried or what else I could try. I simply don't have the money to buy another $700 phone.
[Sprint Samsung Galaxy Note 3] micmars:
You're girlfriend has a point, as the above is circuitous.

Now, download either the One-Click here, or stock tar here, flash either the one-click from it's own package (It contains an EXE file that does the entire restore for you) or the tar from PC Odin, and when complete, meet me back here.

While that's happening, download this NABD update zip here (it's a small file in the bottom of he OP, look for it and grab it from freeza's thread I just linked, and put it on your PC (it will eventually reside on your external SD, but you're not putting it there until you're back to stock). Do NOT flash recovery or root until you respond. And please quote this message, as I'll get an email when you do.

Then grab this recovery file (it'll go on your PC), this latest TWRP for KitKat V 2.7.0.0, and this SU 1.93 for our phone, just in case you need it (the latter will go on your phone). I am giving you choices. All of this should take no more than 20 minutes, planning included.

Write back if you need help.

Good luck!
[Sprint Samsung Galaxy Note 3] KoolCharisma:
Right On!

You've given me hope. I got everything I need here and I'm definitely seeing some new pieces that have been missing from the process thus far. So this returns me to stock, got it, but with the addition of SU and TWRP, does that open the choice up to root/and or flash other ROMS? I'm almost scared to fool with it now, but I definitely don't want to go to stock.

NAB file seems like it may take 12 hours to install, so unfortunately I can't give you immediate results. At least I'm not stuck with the same old pattern and expecting different results.

What ROM are you running?
[Sprint Samsung Galaxy Note 3] micmars:
Do not worry about the rom I'm running.

There's no reason for this to take long.

Flashing the one-click or tar?

Sent from my SM-N900P using Xparent BlueTapatalk 2
[Sprint Samsung Galaxy Note 3] KoolCharisma:
It got worse

Just when things were looking up, the situation changed. Now it will only give me the "seandroid not enforcing warranty bit: recovery" message. From there it just cycles it will not allow the EXE file to recognize the phone nor can Odin see it. I assume of course because I can't get it into download mode.

So I'm really confused now. A few hours ago I had access to a broken recovery and a download mode that wasn't working. Now It seems I lost access to both. What gives?
[Sprint Samsung Galaxy Note 3] KoolCharisma:
WE GOT IT!!!

I scoured all over this sight and online and didn't see mention of this app anywhere. Now You've fixed it!

So where do we go from here? I'm a big nervous going for a root a second time, but I simply can't use stock anymore.
[Sprint Samsung Galaxy Note 3] micmars:
Dude, you have to quote me or I'm not going to get realtime updates on your progress.

OK, so you have a working stock rom?

If yes, plug your phone into your computer, dump the NABD update file I gave you into into your SD card, and put the root file I gave you onto your phone's internal memory.

Now, power off your phone.

Boot into stock recovery (you'll get there, you may encounter recovery loops, don't panic, it's perfectly normal, just be patient, hold power + home plus volume up), you should be in stock recovery.

Now using the volume keys, navigate to apply update zip from external SD. Hit home to select, then navigate to the NABD zip file you copied. Install it.

After that, you're on NABD stock.

Next step is to install custom recovery.

After booting your phone on stock, skip past the setup screens, and just let the phone do its garbage setup, then reboot for good measure, then power off.

Now, open PC Odin (run as administrator from Windows), and put the TWRP file I gave you into the PDA slot.

Now, take off the casing, and hold the phone in your hand, have your fingers at the ready to hold volume up + home, don't do it, just be ready. Now put the phone in download mode (home + volume down + power). Plug the phone into the same USB port on your phone that you used to copy the files onto it.

Ready, hit start on Odin. That recovery file flashes in like 5 seconds. The moment it finishes flashing and begins to power cycle, hit those keys (volume up + home), and you're in TWRP.

From TWRP, navigate to the place on your SD card where you put the superuser zip, and flash it.

You now have a rooted phone with working recovery. From here you can do whatever you want.

Good luck!

Sent from my SM-N900P using Xparent BlueTapatalk 2
[Sprint Samsung Galaxy Note 3] KoolCharisma:
NABD

Trying now to go From NAB to NABD. I'm doing it in stock recovery. First off I realized that When it first pulls into recovery, the broken Android comes up. It let me navigate to install NABD and seems to reach the very end of installation but then it stops at "patching modem.bin img". nothing appears broken, but I'm I'm afraid to unplug it or to try and boot it back into stock.
[Sprint Samsung Galaxy Note 3] micmars:
Those patch files are upgrading the OS build top NABD. Let it run its course.

Sent from my SM-N900P using Xparent BlueTapatalk 2
[Sprint Samsung Galaxy Note 3] KoolCharisma:
It won't let me go through with it. Or at least I didn't have patients for it. I was able to get the phone back to a full reboot and then go back in and flash TWRP. TWRP works and is now my recovery, but I'm unable to upgrade NABD or Establish Root.
[Sprint Samsung Galaxy Note 3] micmars:
Then...

Then don't upgrade to NABD; if you attempted to root the device or flash recovery prior to upgrading to NABD, the update will never flash.

If you still lack the ability to start your phone, just reflash NAB One-Click or tar and call it a day. Move straight to flashing recovery and rooting. Or just recovery and a pre-rooted ROM.

Let me know what you'd like to attain, and we can take it from there. NAB is good enough.

If you stilll want to try NABD, note that the upgrade to NABD took me a while to get it right, as I had trouble getting into stock recovery. Please let me know if the upgrade to NABD file is the same file size as this. If yes, then skip NABD and go straight to recovery and root.
[Sprint Samsung Galaxy Note 3] KoolCharisma:
Almost there

We're definitely working with the same NABD while. So I guess I will do as suggested and go back to stock with the EXE. Then I will try to work my way back to a rooted phone with custom recovery.

I will say at this point that I'm certain I'll want another ROM. I can't stand stock. I'm just very fearful that with this whole KNOX bit, it is far less predictable to stay off the grid so to speak. There's also the question of which ROM. I never reach for the vastly different ones, but I don't want something simple like CM. My favorite ROM on the S3 was Liquidsmooth. I had trouble however upgrrading to KitKat on my S3 so now I don't know if I can trust that on my phone. I'm definitely open for suggestions.
[Sprint Samsung Galaxy Note 3] micmars:
Pick a Direction...

When this first started, you had been on an AOSP rom, yes? If so, then you need to decide if you still want that. If you want a reliable phone that has everything functioning as the manufacturer intended (and that is a very wide berth as to whether that is a good thing), then you should pick a TouchWiz KitKat ROM for now and run with it. If you want a working phone that is reliable with no bells and whistles, then go with one of freeza's Stocksh DeOdex or Odex rooted roms.

You should not be afraid of Knox, you should merely choose what you want and head that direction. You'll get there.

However, I understand the reticence; I get pretty anxious when doing this stuff, even over the smallest of things Those whom help me here can vouch for that, as I've driven many of hem insane.
[Sprint Samsung Galaxy Note 3] KoolCharisma:
Alright here we go again. I've reflashed stock and now I'm attempting to upgrade to NABD with Stock Recovery. Now I'm stuck again in recovery at the very end of the flash where it says: "Patching modem.bin img".

I was on Liquidsmooth, which I believe was a touchwiz, but to be honest, I'm not sure between the two, which probably explains a lot as to why I was having trouble flashing on the S3.

Where do I go from here?
[Sprint Samsung Galaxy Note 3] KoolCharisma:
Is the problem hung up on the modem specifically, or is that just what the screen happens to be displaying at the time. It seems more to me that there is just one small piece of the whole puzzle that doesn't add up. I'm up supposed to do some full wipes and formatting to get my way through this?
[Sprint Samsung Galaxy Note 3] micmars:
Just skip the NABD update and go straight to root and/or recovery.

Sent from my SM-N900P using Xparent BlueTapatalk 2
[Sprint Samsung Galaxy Note 3] KoolCharisma:
Well see that's just the problem. My recovery seems to be broken because it loads the Android with the knocked out droid. It will not allow me to install the update, root, nor the recovery. So my phone recognizes the mod and won't let me out of it. It keeps coming up with a warning that some unauthorized changes have been made. I HATE STOCK!
[Sprint Samsung Galaxy Note 3] KoolCharisma:
The phone can't stay this way. I tried the auto root with no success either.
[Android Themes] Martini3001:
Hey,

I made a few buttons for app-developers and modders. Have a look and load it 4 free.

The buttons are ideal to convert them to draw9-patch. ;)

-> DOWNLOAD <-

Best wishes, have a nice weekend!

Martin
[8125, K-JAM, P4300, MDA Vario General] yozh:
I upgraded to 2.24 Tmobile official beta ROM. and it seems that I cant get phone calls while im streaming thru EDGE/GPRS not just streaming also like browsing and stuff, phone calls go straight to voicemail, is this how it was on 2.17 or 2.21 ? Because I tought it worked before !!!! Can anyone confirm please...
[8125, K-JAM, P4300, MDA Vario General] yozh:
Can some one please verify regarding this, can some one just try browsing somethign and call them selvs and see if it goes straight tru to voice mail on a diffrent ROM please....
[8125, K-JAM, P4300, MDA Vario General] bgsdks:
Yozh:

I had an 8125 on the Cingular network running Summiter's 2.17 ROM, and the phone call always interrupted any web surfing I was doing, and/or disconnected IM+ (which uses gprs/edge).

That phone broke (d'oh!) and I got another one that was running the stock ROM. Same thing.

I now have a new 8125, and just upgraded to Summiter's 2.3 ROM (thank you Summiter!), and the phone acts the same.

I've never experienced an issue where the phone call goes directly to voice mail... that I know of. :)
[8125, K-JAM, P4300, MDA Vario General] yozh:
Very strange, I tought thats what mine used to do before the 2.24 ROM it used to interupt the GPRS session for a phone call. ANyone else that can confirm that this is just an issue in 2.24 ROM ?
[8125, K-JAM, P4300, MDA Vario General] yozh:
Anyone else that can confirm this ?
[8125, K-JAM, P4300, MDA Vario General] yozh:
Or maybe there is a registry setting for this ?
[8125, K-JAM, P4300, MDA Vario General] dangerous_dom:
I have always thought it depends on what your gprs connection was doing.

if it is connected but idle, then calls will come through. if it is connected and in use, downloading a file or something, then it won't be interupted by a call.

as far as I know, this is the way gprs was desgined to work. can anyone confirm?
[8125, K-JAM, P4300, MDA Vario General] yozh:
I dont want to go back to the 2.17 ROM just to test this. But it looks like no one out there would do it for me :(.... I could of sworn that it worked before..