yashsingh1/xdaforums huggingface dataset:
[Xperia Z General] yasan:
Android: 4.2.2

Build number: 10.3.1.A.0.244

Kernel: 3.4.0-g3865184 Tue Jul 2 07:57:34 2013

Customization: 1270-6697 R4B

Branding: Generic ES

Country: Spain

Download:

Firmware:

https://mega.co.nz/#!AIUBXZgL!BsFM5QxSdEoIe9nJ7Kzkhxo51epo34MxARYlfqBhKM0

.

Kernel:

https://mega.co.nz/#!pR9CWZiB!PEicAEHAA721XVG3YAEEsj_DWI4_tELx8CZumCE7LPI

Baseband:

https://mega.co.nz/#!4IlUnSTK!O5GCM3fv9v4rEz8x5NF4fmbt8DFGsX_AQ3w2T-xiq5s

DooMLoRD's rooting 10.3.1.A.0.244 Firmware

http://xdaforums.com/showthread.php?t=2386405
[Galaxy S 4 Q&A, Help & Troubleshooting] A-Sweaty-Wombat:
Hello,

I would like to download and install a custom ROM for my Galaxy S4 I9505.

Here is the list of desirables for it:

Ultra stable.

Buttery smooth 0 lag.

NOT TouchWiz based.

MUST have all Galaxy S4 features like air gestures, air view, smart stay/pause and so on.

MUST support LTE.

MUST have all working features!

MUST include (or support) the default Galaxy S4 camera app.

Yes I have looked on XDA and galaxys4root.com to try and find it myself but galaxys4root.com is limited and XDA has way too many to sift through and narrow down, I'm not just lazy!

All help on this is appreciated, if this ROM doesn't actually exist yet, get making it because it's the perfect combination!

Thank you to the mastermind who finds a ROM fit for my specification :D:D:D:D:D:D:D:D:D:D:D:D
[Galaxy S 4 Q&A, Help & Troubleshooting] andymihail:
While I agree I would like to have such Rom, true fact is that it does simply not exist.
[Galaxy S 4 Q&A, Help & Troubleshooting] A-Sweaty-Wombat:
Damn... Such a shame. If I knew how to make a decent ROM I'd do it myself!
[Galaxy S 4 Q&A, Help & Troubleshooting] gee2012:
There are some good roms around that come close to what you want. Just try a few and maybe use a custom kernel and you`ll find the right combo to suits your needs. Looking for that is part of the fun ;)
[Galaxy S 4 Q&A, Help & Troubleshooting] A-Sweaty-Wombat:
I'm very picky unfortunately... I don't understand why there isn't yet a ROM that has a nice sleek UI, is blazingly fast and has an insane amount of features including Samsung features like air view/gestures etc.

I also get bored of ROMs and kernels very quickly because I miss one thing or another :/
[Galaxy S 4 Q&A, Help & Troubleshooting] gee2012:
There are: like Omega v11 is very good and customisable, Android Revolution is close to stock with tweaks, Wanam Lite is good. You have to try them yourself bro cause everyone has a different setup and needs.
[Galaxy S 4 Q&A, Help & Troubleshooting] -Falco:
There is no 'prefect' ROM as everyone has needs and wants, in order to find the ROM that best fits your needs and wants you will have to try them all with the many different kernels. Me I only use deviant development roms, and pacman or domination (they are merging so doesn't matter.) But others may only use cynanogen because we all like something different and have found our 'perfect' ROMs

~~~~~~~~~~~~~~~~~~~~~

I am always on the mobile app and am always 'trying' to help others and moderators on the forum and learning something new everyday. I make stupid posts sometimes, but I never repeat a mistake more than once. I may not be a developer, but I know alot of stuff, so feel free to messsge me any questions and I'll be happy to answer them to the best of my ability.

~~~~~~~~~~~~~~~~~~~~~

I'm starting a video game company with my friend where we will be making Android games. message me for more info or go here: http://xdaforums.com/showthread.php?t=2290843
[T-Mobile Samsung Galaxy Note II] COCODRILO45:
hi guys im returning my note 2 to back to asurion i just got it last tuesaday but the ear piece on the phone dont work so im sending it back i rooted the phone i tried triangle away to reset the custom binary count back to 0 but had no luck its already back to stock via odin but it still says custom binary download : yes (1 count) current binary :samsung official system status : official yous guys think asurion will give me a hard time if i return the phone like that ? dont now what to do ? thanks in advanced :good:
[T-Mobile Samsung Galaxy Note II] Coug76:
If you are returning on asurion warranty you will need to use Triangle Away to reset your counter and be certain that you are back to stock.

Hastily spouted for your befuddlement
[T-Mobile Samsung Galaxy Note II] COCODRILO45:
i already did i flashed stock kernel and stock recovery and and then tried triangle away and then return to stock via odin and still it says custom binary download : yes (1 count)
[T-Mobile Samsung Galaxy Note II] tony yayo:
Try a factory reset.
[T-Mobile Samsung Galaxy Note II] COCODRILO45:
forgot to mention that i did that to after all the otheir steps i did a factory reset via stock recovery :eek:
[T-Mobile Samsung Galaxy Note II] tony yayo:
Try doing it from the settings menu instead. I believe I had to do that before. Dont know what the difference is between the 2 ways but give it a shot
[T-Mobile Samsung Galaxy Note II] ionic7:
Need to root run triangle away then unroot
[Acer Iconia A500] nobodysktr:
Installed the latest jellytime i could find for a501 http://xdaforums.com/showthread.php?t=2279244&highlight=a501+rom

and I noticed that the front facing camera is not an option in the camera app. Has anyone else seen this or figured out a fix?
[Acer Iconia A500] roxalex:
Try Thor's Rom
[Nexus 7 Q&A, Help & Troubleshooting] Arroma:
Hello Forums,

I went on vacation like 2 months ago, and i brought my Nexus with me, and I thought i had lost it. My relatives found it and it was handed to me. With this being said, my nexus was uncharged for the duration of the time, and when i tried to recharge it, it flickered several times and nothing happened. I found that i should hard reset and and put it into recovery mode, but it would always say booting failed.

I searched everywhere and found that i should try and flash the stock image so i looked up several guides on how to do so. On this site i found to use a Wugfresh toolkit. When i tried flashing on both occasions, each time the cmd prompt would come up it would say

sending 'bootloader' <2096KB>....

FAILED <remote: Bootloader is locked.>

finished. total time: 0.012s

rebooting into bootloader....

OKAY

finished. total time:0.021s

<waiting for device>

BUT, my device won't ever reboot. I would always have to press power vol up and vol down.

I noticed that this is a reacurring pattern. I is unable to reboot on its own.I searched everywhere and cannot find a solution.

I am able to get into the menu

FASBOOT MODE

PRODUCT NAME

VARIANT

ETC ETC

LOCK STATE-LOCKED

I would think to unlock it, but it wont ever reboot when i tried to.

I have also tried opening cover to see if the battery wire was loose, it was slightly out of place but i put it back, but same thing.
[Nexus 7 Q&A, Help & Troubleshooting] chrisbo4:
Since you can access the bootloader, I would recommend learning how to use fastboot. I had a similar situation, and fastboot saved my N7. I'm not that experienced with fastboot, but learning was pretty simple. Search Google for instructions on how to set up SDK. Let me know if you run into any problems, and I'll do what I can to help.
[Nexus 7 Q&A, Help & Troubleshooting] Arroma:
im following a guide, but im stuck where i have to update my drivers. since my Nexus is off, when i go into the device manager, all i see is APX under other devices. Do i turn on my nexus in bootloader, or update the APX drivers?

EDIT: I did get the drivers working when i put it into bootloader , so when i look at the device manager i see "Google Nexus 7 Bootloader Interface". When i put in adb devices in the command prompt, i see

List of devices attached

C:\Users\etc\etc\....

I dont get a serial number, i dont know what im doing wrong ):
[Nexus 7 Q&A, Help & Troubleshooting] chrisbo4:
Okay, and the command prompt is where I had some trouble too. Unfortunately all of the tutorials I read assume that that the user already knows how to use a command prompt, which I didn't. So you'll want to make sure your SDK manager has "platform-tools" & "USB drivers" up to date. Also make sure that your factory image has been extracted and placed in the platform-tools folder. I used 7-zip to extract.

When you're in the command prompt, type "cd android-sdk-windows", then "cd platform-tools". From there you're ready to use fastboot. You can type "fastboot devices", and you should (if everything is installed correctly) see your devices serial number displayed. From there you can type the necessary commands to restore your device.
[Nexus 7 Q&A, Help & Troubleshooting] jt.one:
android adb folder (password to zip is jt100)

^ download that and extract the Android folder to the root of your C: harddrive (so it'll be C:/Android) this is the main adb/fastboot/whatever folder you'll ever need,

ever.

- hold down shift and then right click within the android folder and select "open a command prompt here" (or something like that)

-fyi...the command 'adb devices' is for when your device is booted up to the android homescreen and 'fastboot devices' is obviously when you're in bootloader

-'fastboot oem unlock' is to unlock the bootloader

then, if you have the 4.3 factory image from google on hand...

-extract the initial zip, and you'll get like 5 files

-copy those 5 files to the same C:/Android folder from earlier

-make sure your nexus is in bootloader screen and then just double click the 'flashall' .BAT file (if you're running windows OS) and android will auto wipe and flash everything

-just let it sit and wait for your device to boot to setup screen
[Nexus 7 Q&A, Help & Troubleshooting] Arroma:
i do see the serial, but now im unsure of what commands to use, the guide said to do oem fastboot unlock, but it failed
[Nexus 7 Q&A, Help & Troubleshooting] chrisbo4:
The command you'll want to use if you want your bootloader unlocked is "fastboot oem unlock" Just a hint, every command should begin with "fastboot". If all you want to do is restore the factory image, I can help you with those commands as well.
[Nexus 7 Q&A, Help & Troubleshooting] exglynco:
You're limited to Fastboot commands when your device is booted to the boot loader. ADB commands only work if you can get booted into Android. You'll have to recover your tablet strictly using fastboot commands. Wugfresh's root toolkit should work now that you have the device drivers loaded. First step is to unlock the boot loader. Then proceed with flashing the factory image.
[Nexus 7 Q&A, Help & Troubleshooting] Arroma:
wugfresh doesnt work, it always fails to unlock, even using the commands, says Unknown Error
[Nexus 7 Q&A, Help & Troubleshooting] jt.one:
read my earlier post, forget using the damn toolkit
[Nexus 7 Q&A, Help & Troubleshooting] chrisbo4:
[MENTION=4090690]jt.one[/MENTION] I agree using a toolkit is a waste of time, especially when the OP has already accessed fastboot. He's practically done.
[Nexus 7 Q&A, Help & Troubleshooting] Arroma:
mandad since

Right so, i did everything you said, and it was working, until somewhere along the middle it failed cause its still locked, but i cant unlock it cause it always fails to unlock due to an unkown error ):
[Nexus 7 Q&A, Help & Troubleshooting] exglynco:
After sending fastboot devices, and getting a serial number, send fastboot oem unlock. Then flash a factory image. Here's a good tutorial on how to flash Android 4.3..
[Nexus 7 Q&A, Help & Troubleshooting] jt.one:
even though you did 'fastboot oem unlock'..... your bootloader refuses to unlock?

now that is strange... :confused:
[Nexus 7 Q&A, Help & Troubleshooting] Arroma:
i dont understand either, errors everytime ):
[Nexus 7 Q&A, Help & Troubleshooting] exglynco:
You don't see a fastboot response like this?

Then you'll need to tell us specifically, every error message that pops up.
[Nexus 7 Q&A, Help & Troubleshooting] Arroma:
i do see that, and i use the power button for yes, here ill copy and paste what i saw on the internet some guy is having the same problem im having, only noone replied to his thread

"My problem is that I cant unlock my bootloader.

This is what I tried:

fastboot oem unlock

This is the result:

(bootloader) erasing userdata...

(bootloader) erasing userdata done

(bootloader) erasing cache...

(bootloader) erasing cache done

(bootloader) unlocking...

FAILED (remote: (Unknown error code))

On my device in fastboot it just adds the text "unlocking now......" and nothing happens. If I try to reboot with i.e fastboot reboot-bootloader the device screen is just black, im not sure its even on."

-cant give credit to the guy cause i cant post links yet,

sorry on not being clear enough, i really appreciate your help
[Nexus 7 Q&A, Help & Troubleshooting] chrisbo4:
You're device wouldn't boot prior to unlocking the bootloader, right? I would try flashing the factory images, then unlocking the bootloader... if that;s possible.
[Nexus 7 Q&A, Help & Troubleshooting] Arroma:
chtfte was

im not sure i understand, i cant flash anything because its still locked
[Nexus 7 Q&A, Help & Troubleshooting] chrisbo4:
I apologize, just a crazy idea I had.
[Nexus 7 Q&A, Help & Troubleshooting] exglynco:
It looks like a rough road ahead. I searched for the error message you get, and there doesn't seem to be a common cause for it. I saw comments that the error may be caused by corrupted files or data in one of the partitions.

If it were my device, and I didn't have anything to lose (i.e., the device is toast anyway), I'd fastboot format boot, fastboot format recovery, fastboot format system, fastboot format data, fastboot format cache, and fastboot format misc.Then I'd try the unlock command again.

Edit: changed erroneous fastback commands to correct fastboot commands.
[Nexus 7 Q&A, Help & Troubleshooting] Arroma:
what is that, and how do you go about doing it? Will it destroy my device?
[Nexus 7 Q&A, Help & Troubleshooting] exglynco:
The different fastboot format commands simply clean up all the internal Android partitions. But in doing so, they completely wipe your device of its ability to boot, go into recovery, etc. You should be able to reflash another boot image, another recovery image,etc. to the cleaned-up partitions. But you should have been able to unlock the bootloader, too.

So, what I described is a last-chance attempt, to try only after you've exhausted all other possibilities to unlock the bootloader.

You have looked at the lock image that appears with the word Google during booting, and it is locked, right?
[Nexus 7 Q&A, Help & Troubleshooting] Arroma:
well during booting all i see is the word Google, i dont see a lock image like you have described.
[Nexus 7 Q&A, Help & Troubleshooting] exglynco:
Not to worry. When the bootloader is unlocked, the lock image is unlocked. My N7s have been unlocked forever, so I guessed there's a locked image when you're locked. My bad.
[Nexus 7 Q&A, Help & Troubleshooting] ojoel:
unlock

I also was stuck at the google screen, fastboot erased everything and could not unlock bootloader. In the command prompt i get unknown error but on the screen it says "Neither USP nor CAC partitions found....toast?

Edit-

I tried flashing 4.2.2 and 4.3 image, says

Device version-bootloader is '4.13'.

Update requires '4.18'.

going to try 4.1.2

Edit-

4.1.2 is no go either, requires an older version 3.41...does anyone have a factory image that requires 4.13 boot loader?
[Nexus 4 Q&A, Help & Troubleshooting] smapdi:
I started with a stock 4.2.2 and the only modification to the phone was unlocked bootloader and root (no custom recovery or anything like that).

The phone has had a couple of SOD instances but they were very rare. After doing a sideload OTA update I've had it SOD twice in the last 2 days. I haven't re-rooted this phone (waiting for SuperSU to be less...hacky) or installed anything to mess with power management. I read that there may be a netflix SOD issue but it's not applicable as I don't have the app.

Anyone else get SOD with 4.3 or am I the only one?
[Nexus 4 Q&A, Help & Troubleshooting] pfederighi:
You are not alone. My wife's phone is experiencing the same issues. I have chosen not to install the update for this very reason. Hopefully it will get fixed and there will be a new update in the near future. Sorry I don't yet have a solution.
[Nexus 4 Q&A, Help & Troubleshooting] Kitch16:
Yeah, me too. I have had instances where it has just completely shut off and i've had to hard reboot. My other half also has a similar issue on the N4 and these were when I was on stock. I'm now running PA 3.90 and I haven't had any (as of yet)
[Nexus 4 Q&A, Help & Troubleshooting] pfederighi:
For what it's worth, doing a "factory reset" cured my wife's phone of the issue. Be sure to do a backup of important data like contacts and picture first.
[Xperia Tablet Z Original Android Development] lowtraxx:
Disclaimer: I am not responsible if this bricks your device, kills your cat or starts World War 3!

I compiled CM 10.2 for the Tablet Z LTE Version. So far everything seems to work. Do not forget to make a Backup before flashing this.

I wiped data before I tried it, so I don't know if you can flash this over CM 10.1.

Working:

- Bluetooth (sending a file)

- GPS (Going outside getting a fix in 5 seconds)

- LTE (Internet with WiFi off)

- WiFi (Internet with WiFi on)

- Sound (Played Youtube Video)

- Graphics (Epic Citadel Benchmark

- Touchscreen

- SDCard

Not Working:

- Nothing I noticed

Download:

ROM - Dev-Host

GApps - here

Changelog:

[31/07/13] - Initial build with added blobs from the Xperia Z 10.3.A.0.423 fw

[01/08/13] - Added current firmware blobs from Sonys 307 fw as well as from the Xperia Z 10.3.1.A.0.244 fw
[Xperia Tablet Z Original Android Development] scumpicule:
Hi thanks for the rom

Uve some screensshots ?
[Xperia Tablet Z Original Android Development] izy-one:
Its just a nightly build or why is it unofficial?
[Xperia Tablet Z Original Android Development] lowtraxx:
I built the official tree, but added a few binary blobs updated from the 307 firmware and the Xperia Z 4.2.2 release. Its not an official nightly from CM hence the UNOFFICIAL :)
[Xperia Tablet Z Original Android Development] izy-one:
How is it with bugs? Its stable enought for daily use? You said you added some stuff from the .307 Firmware... Is the better touchscreen Performance included?
[Xperia Tablet Z Original Android Development] lowtraxx:
The Touchscreen Fix is included. The only bug I encountered yesterday was a rendering issue with the keyboard in Chrome. But with the Update today this is gone for me. I used it for a day now and for me its as stable as CM 10.1 was. But that is subjective, your opinion may differ.
[Xperia Tablet Z Original Android Development] lowtraxx:
New build uploaded. Also a Screenshot for your viewing pleasure :D Epic Citadel with Ultra High Quality running at Full Resolution with 33.4 FPS
[Xperia Tablet Z Original Android Development] gabx:
Thank you much for your build. I installed it with no issues and until now, everything seems under control.

Good job.
[Xperia Tablet Z Original Android Development] zylstrajs:
Thanks a lot for throwing this together... everything is working great besides the (previously mentioned) screen issue in chrome. The only thing besides that that I've been struggling with is the absence of tablet UI, but it's a small price to pay for the jump from Sony's 4.1.2 to a functional 4.3 Rom.
[Xperia Tablet Z Original Android Development] lowtraxx:
Hi, have you tried the latest build (01/08/13)? It is much smoother and for me the screen issue in Chrome is gone.
[Xperia Tablet Z Original Android Development] razer1224:
Letmme Update with 4th August Build

does it need blobs to boot up?
[Xperia Tablet Z Original Android Development] izy-one:
Is there a Manual how to install this?
[Xperia Tablet Z Original Android Development] isimobile:
Anybody that can confirm of you turn NFC off you cannot turn it on again?
[Xperia Tablet Z Original Android Development] nioman:
Does it work....

Been using this ROM for a few days. It works quite well. It seems to be much faster then the older CM versions.

I have only found a few problems with this.

First is the keyboard. It cliches some times. This happens mostly when using chrome or other browsers. Part of the screen goes black and then comes back to life. After this happening sometimes the keyboard is not visible at all . No biggie, the buttons still work so you can just press the arrow down to get rid of the keyboard and then open it again.

The clock crashes. This has happened at least 3 times. Does not seem to effect the ROM however.

The biggest problems actually seem to be with the gpu. I play real racing 3...A LOT. There are often problems with the graphics that I have never seen before with the older CM versions. The cars simply won´t show at all and sometimes the textures are in the wrong places. This might however be a problem with the game and not the rom itself

I have installed the ROM twice and both times I have suffered from the same problems. Nevertheless I like this ROM and I think it is one of the best at the moment. I will continue to use it and hope that it will be updated to be even greater in the future.
[Xperia Tablet Z Original Android Development] atamig:
Hello,

can I flash this Rom on a 311? Wifi only?

Gesendet von meinem SGP311 mit Tapatalk 4
[Xperia Tablet Z Original Android Development] izy-one:
Please keep your eyes open... Some threads under this there is the thread for your pollux_windy WiFi version
[Xperia Tablet Z Original Android Development] lowtraxx:
If it is wanted I could upload a new build. The Problem is, it would be untested, because I am experimenting with something Stock ATM and so you would need to backup and try if it works and then report here. Would some of you be willing to test? If so, PM me and I will send you a link with a current UNTESTED build. You would need to give me feedback, and if it works (as good or better as the last one) I would publish it. Otherwise I will provide one tested by me in two or more weeks, after my Project with the Stock ROM is completed.
[Xperia Tablet Z Original Android Development] eman2001:
lowtraxx;

Thankyou so much for this rom, this is the best thing that happened to my tablet :laugh: i love it, my tablet feels so much faster and better battery life, no problems so far and everything works :good:;)
[Xperia Tablet Z Original Android Development] remma:
Seems that since yesterday there is an official nightly as well :)
[Xperia Tablet Z Original Android Development] eman2001:
yes u can turn it back on just restart the tablet a few times seems to fix it for me, now i can turn it on and off as i see fit :good:
[Samsung Epic 4G Touch] S1lv3r_DrAg0n:
Hi, I know this is a bit of a noob question, but I want to flash a new kernel, and I don't know which kernels are safe to flash. I'm running CM 10.1 Wild for the Night with CWM 6.0.3.3 . I have a EL29 modem and the current kernel is something like 3.0.64-CM-q31f128d. As to why I want to flash a new kernel it's because I have an audio problem (http://xdaforums.com/showthread.php?t=2374061) and other people with the same problem, but the GT-I9100 version of the s2, have reported it fixed by flashing the dorimanx kernel. However, I can't flash that one because it's only for the GT-I9100 right? So my question is which kernel can I flash?
[Samsung Epic 4G Touch] bigj231:
I believe the only current AOSP kernels are the standard CM one (and its derivatives) and the LightningZap kernel. The CM one is the standard one in most of the AOSP ROMS.
[Samsung Epic 4G Touch] S1lv3r_DrAg0n:
Yeah I believe the cyanogenmod one is what I currently have. Is it possible to flash the LightningZap kernel using Mobile Odin while keeping my current Cyanogenmod 10.1 setup? Thanks for the quick reply!
[Samsung Epic 4G Touch] graydiggy:
As long as there is a tar for it, yes. If they have a zip, you can flash from your current custom recovery. Either way nothing will change but kernel and recovery.
[Samsung Epic 4G Touch] S1lv3r_DrAg0n:
Ok thanks