yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Gear] marvinlh:
Looks awesome, thanks
[Samsung Galaxy Gear] mknrls:
thankss :P
[Samsung Galaxy Gear] veris:
Honestly, this looks awesome, can't wait for it to be coded!
[Samsung Galaxy Gear] re-2007:
thanks... good idea l wish i can help
[Samsung Galaxy Gear] jmorton10:
That does look awesome, but I hope I never have to spend so much time looking at the recovery screen that I worry about how it's themed.... ;)

<JK> I'm just fooling around here
[Samsung Galaxy Gear] freefalling0411:
Flawless looking

Sent from my SM-N900V using Xparent BlueTapatalk 2
[Samsung Galaxy Gear] mknrls:
thanks :D same here but i have to find a coder first :P
[Samsung Galaxy Gear] mknrls:
Responses

i will probably need testers when i coded because i actually dont have the device

hahah:P thannks.

thanks :P i might redesign every trwp page for the gear , we will see!! :)
[Samsung Galaxy Gear] ktetreault14:
Will love to test after Christmas

Sent from my SM-N900T
[Samsung Galaxy Gear] mknrls:
Nice :) but have started coding it yet lol :p
[Samsung Galaxy Gear] BitNotFound:
I'll see what I might be able to do in terms of coding it... That is an awesome theme! I haven't made a TWRP theme, but I learn quickly! Might you be able to post any resource files you used? :)
[Samsung Galaxy Gear] mknrls:
i havent too :P im pretty much learning along the way. i will later on when most other pages design are design.
[Samsung Galaxy Gear] mknrls:
New pics to be posted this week. Coding to be starting very soon. First post been updated (main post) / new name and your support would be much appreciated. :)
[Samsung Galaxy Gear] lnando84:
Here's the TWRP theme I've been working on..all image files are finished and most of the xml is ready, just have to make a few more tweaks(for some reason the theme won't take). Im working on figuring it out and will hopefully have something ready for use soon.. Let me know what you guys think of it in the mean-time..
[Samsung Galaxy Gear] mknrls:
Are u doing this for gear? Because the whole theme had to be 320x320
[Samsung Galaxy Gear] lnando84:
Yes it's for the gear.. And thank you but I already knew my gear watches resolution is 320x320. Must of uploaded the 320x480, let me explain.. When making the theme, I first started by pulling the stock/default TWRP files from my watch. After looking at everything I noticed that the stock curtain image used is actually 320x480. Seeing that confused me so I decided, when making/porting my theme, to do it in both 320x320 and also 320x480..figured one had to be correct. Neither is currently working :( Sorry for the confusion..
[Samsung Galaxy Gear] mknrls:
Alll good :p do u know it dosent work tho?
[Samsung Galaxy Gear] lnando84:
Do I know what doesn't work? As for my theme..yeah isn't working right now and can't figure it out.. I've made a ton of twrp themes in the past(check my sig for examples) just can't get any part of a theme to show up on the watches recovery
[Samsung Galaxy Gear] mknrls:
Revise ur codes, maybe something is preventing from loading or its could be twrp its self
[Galaxy S III Q&A, Help & Troubleshooting] Daeron16:
Hi, I'm not sure what's the problem with my phone I will try to explain so someone could point me into the right direction:

I have a Galaxy S3 bought in Venezuela carrier locked to Movitar, I had it rooted and with a custom firmware (cyanogen), I moved to Spain so I purchased the unlock from galaxy sim unlock. I have put another line from a Spanish carrier and phone can make calls and all. Here's were the problem starts, I notice that the only way to enable mobile data was to activate data roaming which I found odd given that I'm in Spain and it is an spanish carrier. Also notice that the play store still had some icons related to the carrier back in Venezuela and all the recomended, top free, top paid apps where mostly localized to Venezuela. I tried to install some apps from Spain play store and it won't let me. Searching on google found that to change the play store I had to change the country in the Google account which I did with no results, change any payment methods related with the other country in Google Wallet, which I also did and no result.

I think that maybe there is still some information about the original carrier, so I ask the community if someone can point on what could I try to remove any carrier leftover on the phone.

Thanks in advance
[Galaxy S III Q&A, Help & Troubleshooting] JJEgan:
Problem reads as user failed to change modem or CSC .

In recovery format sdcard system data and cache .

Boot to download mode and flash the correct stock rom for your network .
[Galaxy S III Q&A, Help & Troubleshooting] Daeron16:
Hi Thanks for your suggestion, but wouldn't be the same to wipe data and cache from recovery and flash cyanogen 10.2 from recovery? I ask because I have done that and it is still the same issue
[Nexus 5 Accessories] micha.omfg:
Did anyone try both of these and can tell if the high floss clear case worth buying ?

Does the gloss clear protects at all as the Matte back?

By the way, does the back matte white turns yellow?
[Nexus 5 Accessories] rolltideburr:
FYI some guy on androidcentrals forums posted pics of it

link
[Nexus 5 Accessories] micha.omfg:
woah thx for the info =)

posted there a question as well, and yet i want to hear what people in here have to say
[Nexus 5 Accessories] sn0warmy:
From my experience, clear TPU cases tend to turn yellow fairly quickly even in very clean environments.

With that said, I'm using the Diztronic matte black case and absolutely love it.
[Nexus 5 Accessories] micha.omfg:
well i have searched and read about these clear cases including diztronic clear case and saw

some people say their case became yellow.

I guess ill go on the black one although its kinda disappointing.

My new white nexus is on his way buy he will never show its true color nor its "Nexus" brand in a black case.

What about a smoke grey case? will it be available soon?

and if not... what other

GOOD

choices do i have?
[Nexus 5 Accessories] r a g n o r:
This yellowish colour is not about dust or dirty environments, but about UV, which degrades the material.

But it is often doped to avoid this (that's why old computers used to turn yellowish but not the new ones).
[Nexus 5 Accessories] micha.omfg:
i guess im not gonna buy the gloss one, but are there any alternatives so the white color will be seen? or ill just buy the black matte?
[Nexus 5 Accessories] Jimmy2u:
Hi

this yellowish problem is a matter of worry for sure...in that case you can go up with Matte Back...but as far my experience I use white snap on case with kickstand for my N5 and it works very fine..the grip on the phone is very fine and there is no issue of even getting that yellowish thing also...I got it from Fommy a re seller website...you can also check out their may be you find it a better one you are looking for...its a snap on with kickstand for Nexus 5

Thanks !!!
[Nexus 5 Accessories] micha.omfg:
does it make the phone much fatter? >:
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] jfeades1:
I was messing with the build.prop file in a root browser and then tried to restart my tablet now it is stuck on a blank screen after showing the galaxy note 10.1 2014. I can get into recovery and into download mode but am not sure what to do next. Any help?
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] Engineer_Borisov:
Had the same problem. After editing the file built.prop device stuck with a dark screen. You can go to download mode and flash the rom. If the battery is completely discharged then not including tablet charge it before flashing.
[Defy Q&A, Help & Troubleshooting] brendza:
Hi guys. I wanted to install Kit Kat on my defy, follow instruction entered TWRP, nandroid backup, wipe everything except sdcard, install recovery, reboot and now I'm stucked in Android system recovery (3e) and dont know how to proced from here. I only have theses options:

1. Apply sdcard:update.zip

2. Wipe data/factory reset

3. wipe cache partition

Under these it says:

E: Can't mount CACHE:recovery/command

E: Can't mount CACHE:recovery/caller

E: Can't mount CACHE:recovery/log

When I apply sdcard:update.zip it says Faild to open /sdcard/update.zip (No such file or directory), which is normal as my update.zip is on /sdcard/ROM/update.zip.

I also tried to wipe cache partition but nothing happened.

Could someone help me?
[Defy Q&A, Help & Troubleshooting] leandrolutz:
Wich ROM are you using? :confused:
[Defy Q&A, Help & Troubleshooting] thekguy:
Flash sbf. Root phone. Install cm10.2. Install update-recovery.zip. Install KitKat
[Defy Q&A, Help & Troubleshooting] brendza:
Thank you for answers.

[MENTION=4878609]leandrolutz[/MENTION] - It was one that Quarx built, from 02.12.13 CM.

[MENTION=2150021]thekguy[/MENTION] - I had to flash SBF, now I'm on Android 2.2.2. I'll follow your instructions. Just have one question, should I install CWM or TWRP? I follow guide, in which I installed update-recovery.zip from TWRP after wiping all date except those on sd-card. then After that, I couldnt get into new recovery. Is this right order to update to KitKat?
[Defy Q&A, Help & Troubleshooting] leandrolutz:
SBF, root, 2ndinit. Then you install CM10 (4.1), reboot, install CM10.2 (4.3), reboot, install update-recovery.zip, REBOOT (without any wipe), install CM11 (4.4).

DO you want to use ART or DALVIK? :highfive:
[Defy Q&A, Help & Troubleshooting] thekguy:
You will need to use twrp, the one included with the respective build. From 4.3, you should flash recovery zip, reboot without wiping, and from recovery you should be able to flash kk

There's a button dedicated to thanks :)
[Defy Q&A, Help & Troubleshooting] brendza:
Thanks all for your help. I installed 4.3 and after that flashed recovery where I made a mistake and wipe dalvik cache after instaling (did this before yours answers):crying:. After restart, I couldnt enter twrp recovery (as soon as I enter defy restarts), only bootmenu and stock recovery from there. Luckily I havent wiped system so I still have 4.3 installed. Then I tried to install recovery from GooManager (didn't make it), stock recovery where I get message: "Failied to verify whole-file signature. Signature verification failed. Installation aborted".

Is there any way to install twrp without having to do all from the begining (sbf, root...)? :confused:
[Defy Q&A, Help & Troubleshooting] brendza:
Hey guys, problems again. Didnt find way to install recovery so I decided to do all steps (sbf, root, 10.1...) again.

First I entered bootloader, connected usb, RSD lite and flashed same sbf as I did few days ago. Unlike last time, this time it wont flash, RSD did his job (erasing flash memory, flashing code group...) and when it comes to reboting, in RSD is written finished, but defy didnt turn on, not even motorola logo on screen. Take out battery, try to get into stock recovery and bootloader (volume down and up+power on), but still nothing. Then tried other sbf, 3 od them (retail French) but same thing happened every time, dead screen). Only thing that points that tel.is alive is white led that turns on when I connect it to PC.

I cant understand why 2 days ago when I flashed sbf, everything was fine and this time it refuses do complete. Only difference is that this time it was installed Android 4.3 and last time 4.2.2.

Any suggestions.:confused:
[Defy Q&A, Help & Troubleshooting] thekguy:
If your current sbf isn't working, try dfp 231 or a sbf newer than your current one. It should get you at least to stock recovery, from where you can wipe data and revive your defy.

From 4.3, just flash update recovery, don't wipe or flash anything else. Reboot, and enter recovery once again. Now install 4.4 and it should work

Although, that should not have occurred just by dalvik wipe. Make sure the 4.3 build you use is recent

FYI you could have fixed recovery by extracting and overwriting bootmenu folder from zip :)
[Defy Q&A, Help & Troubleshooting] brendza:
Hey thekguy, thank you very much. I managed to revive my defy with 4.5.1-134 DFP-231 Retail.en.EU CEE and now I'm using Android 2.3.6. I'm reading another topic http://xdaforums.com/showthread.php?t=1820282 where it says that after flashing 4.5.1-134 DFP-231 Retail.en.EU CEE, it should than be flashed with rooted SBF 4.5.1-134 DFP-231 Retail.en.EU CEE Rooted SBF.

Should I also flash this second SBF or go directly to 4.3?

Thanks again.
[Defy Q&A, Help & Troubleshooting] thekguy:
Root with framaroot, no need for 2nd sbf
[JASJAR, XDA Exec, MDA Pro General] erezj:
hi all.

i have the XDA EXEC and i dont want to run the EX-ROM.

i do reset after HR and it doesnt install all the O2 stuff.

but i dont have the video dailer.

what cab file do i need or how can i add the dailer without the O2 suff..

pleaaase help.. :?

thanks
[JASJAR, XDA Exec, MDA Pro General] findus:
There are two files you need to run, here they are...

HTH

Fin
[JASJAR, XDA Exec, MDA Pro General] erezj:
thanks it work great!!!
[JASJAR, XDA Exec, MDA Pro General] philtech44:
What about the Orange ROM files??
[JASJAR, XDA Exec, MDA Pro General] Melty:
The Orange ROM contains the Enable_VT_RTPlugin_0727_2_signed.CAB file as well, but not the other one. The other one only seems to disable call waiting anyway, so you shouldn't need it.
[JASJAR, XDA Exec, MDA Pro General] findus:
Didnt realise that was what it did - have removed it to avoid any confusion!

Cheers,

Fin
[JASJAR, XDA Exec, MDA Pro General] Melty:
I've been looking at EXACTLY what each CAB file does and I keep meaning to write a post explaining, but I haven't got round to it yet. Maybe I'll get some time tonight...
[JASJAR, XDA Exec, MDA Pro General] findus:
Have you seen this thread...

http://xdaforums.com/viewtopic.php?p=179142#179142
[JASJAR, XDA Exec, MDA Pro General] Dare2Dream:
is it ok ?

To remove O2 customization on xda exec, we hard-reset & before custom install we soft reset.

Can I use the same method on MDA pro to avoid T-mobile customisation ??
[JASJAR, XDA Exec, MDA Pro General] findus:
Re: is it ok ?

Yes you can, just install the cabs you need afterwards (there's some useful patches)
[Fascinate Q&A, Help & Troubleshooting] bobbyt23:
I can't get my laptop to recognize my Fascinate. I'm on a 4.2.2 ROM. I've tried several different drivers for my laptop, but still can't get it to recognize it so I can use Odin. Any suggestions? Thanks in advance for any help.
[Fascinate Q&A, Help & Troubleshooting] Payton95:
It could be the cord, the usb port, or the computer itself. I had the same problem a couple of times but fixed it by switching usb ports. I found that some ports worked and some didn't.(Weird huh?:confused:) If that doesn't work then you may have to try a different computer.
[Fascinate Q&A, Help & Troubleshooting] bobbyt23:
See, I thought it might be those things too. I've changed cords, ports, and computers. No luck.
[Fascinate Q&A, Help & Troubleshooting] bobbyt23:
Does anybody have the correct drivers that in supposed to have installed on my computer? I'm on Udevs CM 4.4 ROM.
[Nexus One Q&A, Help & Troubleshooting] bergidum67:
Hello,

I have a nexus one with Cyanogenmod 7.1. A few days ago it was reset alone and until now it gets stuck in X home screen.

No possible to entry in recovery, only Fastboot mode.

I have read the forum and the conclusion I've reached is to flash a new recovery, but tried several commands of flashing without positive result.

This is the version of the Fastboot:

*** UNLOCKED ***

NEXUSONE PVT SHIP S-ON

HBOOT-0.35.0017

MICROP-0b15

TOUCH PANEL-SYNT0103

RADIO-5.12.00.08

Oct 12 2010, 14:33:16

These are some examples of what I've tried so far:

fastboot devices

HT05CP80**** fastboot

fastboot erase recovey

erasing 'recovery'...

FAILED <remote: not allowed>

finished. total time: 0.070s

fastboot flash recovery recovery.img (recovery-RA-passion-v2.2.1.img)

sending 'recovery' <3366 kB>...

OKAY [0.484s]

writing 'recovery'...

FAILED <remote: image update error>

finished. total time: 62.182s

fastboot boot recovery.img

downloading 'boot.img'...

OKAY[...]

booting...

OKAY[...]

finished. total time:0.571s

After that, the screen stucks with X picture. It's necessary to power off the phone to re-entry in fastboot screen mode.

Also, I've tried blackrose to get S-OFF, of course with manual procedure. But whenever I use a command to flash, It gets the "image update error"

Also, I've tried PASSIMG.ZIP procedure, but every parition is flashed the result is PU error.

Would welcome help to get the phone repaired!!

Many Thanks for your time,

Berciano
[Verizon Samsung Galaxy S 4] matt9141:
i have the verizon gs4 with MI1 and used root del la vega to root it how do i get back to the way it was before i rooted it
[Verizon Samsung Galaxy S 4] richii0207:
Odin
[Verizon Samsung Galaxy S 4] matt9141:
I do know that i need to use odin but cant find the stock firmware
[Verizon Samsung Galaxy S 4] riker147:
Here. http://xdaforums.com/showthread.php?t=2301259 :p
[Verizon Samsung Galaxy S 4] matt9141:
thank you so much it works
[Sony Xperia ZL] lhun:
Hi everyone.

Some interesting things I've been working on lately. I actually own a Generic BE c6603 Xperia Z. I live in Canada, and our latest LTE here is largely 1700/2100 AWS, with some 2600 splashed in. The HSPA+ network also supports AWS. We're waiting on the 700mhz auction to happen soon.

For a while now, I've been using Xperia ZL baseband c6506 .434 to get LTE support due to 2600 channel on the c6603. Now, it's confusing as to why this works.

The c6603 hardware already supported 2600mhz (but we never got LTE prior). Why then, does it suddenly get LTE when you flash the c6506 baseband (which is supposed to support AWS) but NOT AWS hspa+? When you check the supported frequencies section, you haven't added anything new, it just works. The T-Mobile c6506 radio in theory is actually closer to the 6602 yet somehow, it magically works.

The thought comes down to three things, correct me if I'm wrong.

Either:

1) The baseband modifies the listed frequency ranges of the existing 2600mhz band to something that picks up our LTE range in Canada, but isn't adding any frequencies the radio doesn't PHYSICALLY support, because the hardware is different.

or:

2) The baseband modifies the radio to support ALL the bands Tmobile's c6506 but the existing overlay APK framework-res from the 6603 is disabling AWS on a software level, and the hardware isn't different.

or:

3) The hardware isn't different, but the kernel drivers have been modified to exclude the other bands.

Does anyone know which it is?
[Samsung Epic 4G Touch] mr. ya-di-da:
I'm using cm9 that has the team win recovery. When I try to flash the cm 11 kitkat rom it says fail. Do i need to use a cwm recovery or is the download link bad ?
[Samsung Epic 4G Touch] Gil81:
Flash it from cwm... but after the flash completes, reboot recovery and do you're wipes ( again ) and flash kitkat from it's recovery. Then reboot.

Let it chill for a few minutes, then boot back to recovery and flash you're 4.4 gapps.

This process always worked for me on 4.3 and I'm assuming it will work on 4.4. But I've not flashed 4.4 yet. So proceed with caution.

Good luck...
[Samsung Epic 4G Touch] mr. ya-di-da:
I will try it when I get home from work so I can use Odin to flash a cwm recovery. Everytime I use mobile Odin to flash a recovery it bricks my phone ....why does that happen ?
[Samsung Epic 4G Touch] Gil81:
I'm not sure about the mobile Odin issue... are you making sure the tar file for the kernel is a good download and that it is compatible with the Android version and rom you're trying to run...?

Try downloading the Directboot EL29 kernel from rwilco12's repo.. ( make sure you get the Directboot EL29 kernel and not the stock el29 kernel )

After you have it and the rom you want on you're sdcard... use mobile Odin to flash the el29 db kernel.. it should boot to recovery on it's own..

Push volume up, volume down, volume up... this enables the power button as the select button...

Do you're wipes... and flash 4.4...reboot recovery... do wipes.. ( data, cache, dalvik, and format system )...flash 4.4 again.. reboot.. settle in for a few minutes and then boot recovery and flash gapps 4.4...reboot.

Let me know how it goes... I'll stick around tonight until we get ya up and running...
[Samsung Epic 4G Touch] mr. ya-di-da:
It failed.. (status 7)
[Samsung Epic 4G Touch] Gil81:
Ok... I'll try to get to it tomorrow... but Thursday at the latest.
[Samsung Epic 4G Touch] mr. ya-di-da:
OK thx. I saw that other people where getting the same fail (status 7) let me know what u find.
[Samsung Epic 4G Touch] bilgerryan:
Status 7 is a syntax error in the updater script... Probably missing a semicolon or something silly like that.
[Samsung Epic 4G Touch] Bender_Bending_Rodriguez:
Not related to this issue, unsure if it would be better etiquette to make my own thread for this, but an issue I'm having with dastins CM11 ROM (12-04-13 version) is that I have two "Internal Storages" instead of one (I do not own/use a SD card)

On CM10/10.1/10.2 I had one internal storage, but on CM11 I have a 2GB internal storage and then a second internal storage (that things seem to not be installed to at all) with the remainder of my devices space.

One of the applications I used a lot on stock TouchWiz and earlier versions of CM is larger than two gigs, so on CM11 I can't even install it because it says I have insufficient storage. Is there a way I can combine the two internal storages into one, so it functions like it did on CM10.2 so I can use all of my devices space instead of only 2GB?

---------

Another question, and this one I'm probably just being blind and not seeing it, or maybe this setting is in a different location in KitKat, is my phone is set to USB mass storage instead of MTP. Normally I head over to Settings > Storage > hit the menu key and change USB connection type to MTP, but the menu key doesn't seem to do anything anymore on the Storage page. Where would I change to MTP instead of Mass Storage, or how can I just disable Mass Storage, I honestly don't care about being able to get any files on/off the device, but 90% of the time I'm charging on USB and I just don't want a full screen prompt showing up every time I touch my phone saying "Hey! It's Plugged In! Do you want to turn USB Storage on?"
[Samsung Epic 4G Touch] dirtyhewr:
You need to flash cm11 with the newest cwm... The old regular way of the"safe" recovery doesnt work... The easy way Is to download the blasphemy kernel and install it then boot back into recovery... It will be cwm 6.0.4.5... Flash the rom with this and no status 7...

Hope this helps...
[Samsung Epic 4G Touch] easyrider77:
I have an EL29 direct boot zip file that works with agats and even the newer cwms to flash back to.

I've tested it on the following recoveries and not had an issue at all:

agats (both 1.3 and 1.4), stock twiz, and the latest CWM they are useing.

I have gone to el29 direct boot with all of the above and had no issues, it goes into el29 recovery just fine.

DO keep in mind though I made this zip mainly for flashing into roms, not as a stand alone kernel, so you may have issues wif you use this as your standard go to kernel with the rom. Mst roms already have thier own kernel anyways, so that's normally not an issue, jsut so you are aware this is basically used for flashing roms not as the normal kernel.

I can host it on dev-host if anyone is interested, otherwise I won't bother.....and I ask because sometimes people just don't wanna be bothered, so I always ask......anyways let me know I will host it.

Just as a side note the steps I have done are as follows:

-reboot to recovery

-flash el29 zip file within said recovery (as I said I've tested this on all the above and it works fine)

-reboot recovery (it will be el29 now)

It should be back to the el29 recovery and you can flash from there.

Done this on hood pope (4.3), Viluminati (4.4 and 4.4.1 KitKat), cm10.1 (4.2.2) and stock Twiz rooted (not stock Twiz recovery) but agats recovery 1.3 and 1.4.

Those that don't know how to activate the power button to select what you do is toggle up > down >up > down until it says something about it being activated, you can then just use power to select your option.