yashsingh1/xdaforums huggingface dataset:
[Droid RAZR M Android Development] aviwdoowks:
You must flash the op's boot. You must have come from a nonstock rom/kernel?
[Droid RAZR M Android Development] Coronado is dead:
Flashing boot fixed it. Actually came from stock, so no idea of the issue.

And now titanium won't restore the moto email app or text program. Hmmm.

Anyway, thanks!
[Droid RAZR M Android Development] Q9Nap:
are you trying to restore from a stock odexed backup? if so, it won't work because this rom has had framework modifications and has been reodexed. pulling whatever apks from the stock deodexed rom should work...
[Droid RAZR M Android Development] Coronado is dead:
Ah, yes I am. Would you have any advice on how to do that? Would I just copy them from system/app?

Oh wait, from the stock DEodexed rom. Hmm. I'll hunt around for that I guess.

EDIT: Oh, it's on your site!
[Droid RAZR M Android Development] Q9Nap:
you can copy to /system/app and set permissions to rw-r-r, or just tap to install. the deodexed build is in the same folder linked in the op. you could also try the dst build, which includes moto email and stock messaging app.
[Droid RAZR M Android Development] Coronado is dead:
Very strange. Won't install, and the MotoEmail.apk is already there anyway. I'll try the DST I guess.

---------- Post added at 09:05 PM ---------- Previous post was at 08:27 PM ----------

Hmm, yeah, I even installed the DST (not exactly what I wanted), and tried backup up its email/text apks. Still won't install. Oh well, thanks for all the help, I'll have to abandon for now :)
[Droid RAZR M Android Development] Coronado is dead:
So my phone has been acting funny since I tried installing this (flashed the rom, boot, and radio). I restored to my earlier stock 98.30.1 install.

Does anyone have the boot and radio for that stock version that I could try and reflash at this point? I know the restore should have taken care of them but something is up (GPS keeps losing reception, BT kicks off oddly, etc).

Also, since installing this rom fastboot is kicking an error message stating "Variable unknown" but still flashing the recovery.img I am feeding it.

I assume this is just my phone acting up, not this rom, but since I installed it last any help reverting would be greatly appreciated. Thanks!
[Droid RAZR M Android Development] Q9Nap:
no idea what could be causing the strange issues. this rom isn't heavily modified, just has a lot of bloat removed.

here are all of the publlicly available fastboot files for xt907:

http://sbf.droid-developers.org/phone.php?device=8
[Droid RAZR M Android Development] Coronado is dead:
Thank you for the links.

It must be something else, not the rom. I am noting that I can remove files from my SD card and add new ones, but TWRP still lists the files that I had on the card at the time of the install of this new TWRP. And since they are not really there they cause it to fail a lot of things. Again, no idea what happened or how to fix this since fastboot is giving that weird flash image. I will just RSD lite this sucker and restore a backup from 2 days ago and see if that works.
[Droid RAZR M Android Development] Q9Nap:
np. btw, if you accepted ota update to a newer version than the fxz you're trying to flash, or have flashed a full fxz newer than what you're downgrading to (in other words, if you have a newer gpt_main0.bin) you'll want to comment out or remove the line in the xml that flashes gpt_main0.bin. otherwise rsdlite will fail when trying to flash it.
[Droid RAZR M Android Development] Coronado is dead:
Hmm, I will try that.

EDIT: That seems to be working. What is that exactly? Will this mess me up once they put 4.4 out?

Also, since I am on the newest stock rom anyways, any idea how that happened? Could another rom have had something newer or faked a version number or something? Very confused on how this worked or what it could mean for the future.

Thanks!

EDIT 2: maybe I should just make a new thread ;) I still get the variable not supported message when flashing in Fastboot, but everything seems to flash correctly. So strange.
[Droid RAZR M Android Development] Q9Nap:
Gpt is the partition table. It contains security version for the other partitions and prevents downgrading on locked devices. It has a security version itself which is checked at boot. Once it is upgraded, it can't be reverted, but isn't really necessary on unlocked devices since the boot loader will allow flashing anything.

ROMs usually touch only the boot and system partitions, sometimes the logo and modern partitions. It is unnecessary to touch any of the other partitions.

Variable not supported is common, it displays for me as well but isn't a problem.
[Droid RAZR M Android Development] Coronado is dead:
In the end the memory card died, lol. I assume it wasn't the rom, just a bad card. bestBuy replaced it for me, so I'll try this again later :) Probably the root of a number of issues I had.
[Droid RAZR M Android Development] Disillusioned:
[MENTION=1567974]Q9Nap[/MENTION]

Nice ROM and great efforts. Few points that I would like to highlight:

1. Boned ROM should have Messages, Circle Widget (these are basics that are needed)

2. Ciphering Fix should be included (IMHO) http://xdaforums.com/showthread.php?t=2167606

3. Description of dst odexed and other ROMs - even though its understandable, details around what they contain would be helpful.
[Droid RAZR M Android Development] Q9Nap:
glad you figured out the issue!

thanks for the feedback! yeah bones is missing a lot of stuff, but that's the point of it.

all removed apps are either downloadable from the play store or have replacements available in the play store. i debated whether or not to remove messaging since it is a basic function, but due to sms integration being available in hangouts as well as many other sms apps being available, i decided to remove it. i'm not a fan of the circle widget mainly because it works only on the stock launcher and seems to drain battery faster (maybe my imagination), but it can be pulled from the stock deodexed build and added back if desired; same with any other removed apps.

that ciphering fix looks interesting, haven't seen or heard of it before. i don't have the issue that it fixes though.

as for a description of roms other than bones, mainly dst, they can be found on droid-hive where i originally posted them:

xt907: http://droid-hive.com/index.php?/topic/2399-rom-98301-dst/

xt926: http://droid-hive.com/index.php?/topic/2444-rom-9301-dst/

i never created posts for them on xda, although future efforts will likely be posted here. with the imminent release of 4.4, it's hardly worth creating posts for them now. big thanks to aviwdoowks for sharing them with the xda community!
[Droid RAZR M Android Development] Germanese:
Any one has a working link to these roms ?

And also i would not mind to Host them also ...
[Droid RAZR M Android Development] Q9Nap:
batakang ftp is down permanently. i've re-upped my xt907 stuff to drive: https://drive.google.com/folderview?id=0B-53iD-71B3iX0dXU2FTYjRjN3M&usp=sharing

this isn't everything, just the basic stuff. i'll probably put more stuff up once 4.4.2 is released, if that ever happens :/
[Droid RAZR M Android Development] Germanese:
Cool thanks.

Just curious what i just downloaded though ahhaha.

Install all zip though recovery ? OR is Boot the only thing i will need for a bone Stock OS with no VZ junk ?
[Droid RAZR M Android Development] Q9Nap:
everything is flashable through recovery.

first flash the boot and system zip, then the vzw removal to remove vzw bloat and unlock tethering.

you can flash radio, but isn't necessary if you already have the latest.
[Droid RAZR M Android Development] snoop1979:
So if i flash "xt907-98.30.1-boot-system-s.zip" it wont lock my unlocked bootloader is that correct?

After that i can flash "xt907-98.30.1-vzw-removal-s.zip" to debloat the rom right?
[Droid RAZR M Android Development] FirePsych:
Is this stock or revolted?

Can you flash this after a good wipe to get the 4.4.2 or are there files missing?

I'd have to unroot?
[Barnes & Noble Nook Tablet] chimpknowskungfu:
I installed the sdcard version of CM11 from iamafanof website , including the sd card version of Gapps but I don't see the playstore. It looks like Gapps are flashed okay in TWRP...I get no errors, but I get nothing when I boot into Android.

Help appreciated.
[Barnes & Noble Nook Tablet] digixmax:
The Playstore should be there if Gapps package was installed.

Check to make sure that you used the sdcard (and not the emmc) version: gapps-kk-20131208-no_set_metadata_sdc.zip or pa_gapps-modular-mini-4.4.2-20131230-signed_sdc.zip.

Also, iamafanof's guide says you should install and boot CM11, then go back to recovery to install Gapps.

Which version of TWRP recovery did you use? Note that CM11 requires TWRP 2.6.3.0 or later.
[Barnes & Noble Nook Tablet] chimpknowskungfu:
2.6.3.1. I installed the mini version ...and made sure it was the sdc. It boots fine into Android. I even get a dialog box saying x of 9 apps updating after I flash the pa_gapps sdc.zip file. But when it boots up, I don't see the playstore . I can surf then net on wifi and everything else looks okay.

i would like to try cwmbut i cant find the latest sd bootable version.
[Barnes & Noble Nook Tablet] digixmax:
Do the apps show up in Settings->Apps menu?

If so, did you look for these apps on the App Drawer (hit the circle with 6-dots on the navigational bar at the bottom of the screen)?
[Barnes & Noble Nook Tablet] chimpknowskungfu:
Nope..settings app doesn't show Google Play Services either.

I would like to try CWM instead of TWRP. WOuld you know if there's a way to boot the latest CWM from the SDcard like TWRP? All I did for the latest TWRP was rename the sdcard version from their site to recovery.img and coped it over to the main directory of the sdcard.
[Barnes & Noble Nook Tablet] digixmax:
I don't know of an SD-based version for CWM v6.0.4.3 or later (which is required for CM11).

Try using the recovery.img that is included in cm_acclaim_11.0_14JAN2014_HD_SDC.zip (open the zip file and extract recovery using 7-zip), or get the SD version of TWRP 2.6.3.1 from http://techerrata.com/browse/twrp2/acclaim (rename it to recovery.img before copying it to your SDcard).
[Barnes & Noble Nook Tablet] chimpknowskungfu:
I got it fixed by burning the sdcard image and then expanding the partitions accordingly.

Thanks for your help anyway.
[Optimus One, P500, V Q&A, Help & Troubleshooting] chalo99:
Hi, I have some questions with kernels, overclock and governor. I'm using cm10.1 or cm11 or any JB or KitKat and I have some questions:

1- Wich are the best governor for daily use?

2- Wich are the safe levels to overclock the phone?

3- I saw that a lot of people uses OC in Min 122 and Max 806, Is this possible with few risks?

4- Wich are the risks of OC?

5- Should I use a specific kernel? Or the one with the customs ROMs are enough?

5- More questions after I get more information.

Thanks.

PD: I made this thread because the others OC threads are very old, before JB and when ICS was just released I think.
[Optimus One, P500, V Q&A, Help & Troubleshooting] blademarquez1512:
OC 806 can damage your phone for ever manage carefully this
[Optimus One, P500, V Q&A, Help & Troubleshooting] chalo99:
And what are the safest levels? And best governors? Im actually using smartass min 480 max 729
[Optimus One, P500, V Q&A, Help & Troubleshooting] MechanicaIMan:
Overclocking will not "damage your phone for ever." Some of the P500s are stable at higher clock speeds than others, which is typical of mobile CPUs (even the two cores of my Sensation's CPU are stable at different maximum clock speeds). IIRC, my Optimus T was only stable up to 729 MHz. If you try to overclock higher than your phone is capable of, then it will freeze or reboot. There really isn't a "safest" level; any clock speed that your phone is stable at is going to be perfectly safe. Run a stability test or benchmark app from the Play store to check stability. IIRC, another easy way to test stability on the P500 is to open a camera app. The camera tends to crash the phone when the CPU is clocked too high. If you manage to crash the phone by doing any of that, then I recommend dropping down to a lower clock speed. Otherwise, the phone is fine and you can test a higher clock speed. FWIW, I'm pretty sure that most P500s are stable up to 729 MHz, but many of them are not stable higher than that.

I personally like to use Interactive governor. I think I used Interactive with min 480 and max 729 on my Optimus T. Governors Explained
[Optimus One, P500, V Q&A, Help & Troubleshooting] engr_exxi:
1. I use smartass as governor (well on the jenkins build). It has a balanced battery and performance I think.

2. Regarding safe level, no overclock is safe, unless it is specified that the processor can handle overclocking over a certain period of time. That's why it is designed for a certain clock speed, because at the guaranteed clock speed you can get the most out of your processor without even breaking it.

3. Well overclocking on android depends on the ability of the kernel to handle overclocking situations. Some kernel can handle overclocking very well that the noticable errors are up to a minimum level. While setting the frequency to Min 122 and Max 806, it is not really safe to go to a maximum of 806 Mhz. As specified the maximum (safe) frequency of the processor is 600. so even going for 601 above or to 710 even if other claim that 710 is still a stable frequency will not guarantee that it will we stable at 710. Regarding the risk. overclocking in the first place is risky.

unless yo go y.o.l.o over your hardware.

4. Risks are. 4a. going beyond the maximum temperature your hardware can handle. can lead to fire (yeah it is true).4b. boot failure 4.c crashing of applications. 4.d etc etc.

5. Before, we use to have different kernel developers and different rom developers. as the the passed by and newer devices are being developed, some migrated to newer devices and abandoned the development for our beloved phone. Now I think only 1 developer is still developing (original development not just cuztomizing and stuffs it with design) androidmeda (check "jenkins armv6") and the kernel included in the rom is sufficient enough to handle overclocking (used it and set the freq to 320 - 710 at smartass). I also use sweetnsour's kernel before but i think he too abandoned the development)

5. k
[Optimus One, P500, V Q&A, Help & Troubleshooting] MechanicaIMan:
That isn't true. Processor manufacturing is inexact, so some processors end up with higher clock speed capability than others. As the maker of a device, you have to set the clock speed low enough that ALL of the processors in ALL of the devices function properly. Setting the clock speed conservatively means that most or all of the devices are actually capable of functioning at a higher clock speed, which in most cases -- and certainly in the case of the P500 -- is completely safe. And it is extremely naive of you to believe that every processor or computer you buy is running at the "best and safest" speed as tested by the manufacturer. CPUs are often significantly underclocked simply to allow manufacturers to differentiate pricing. The same thing is done with finished products, including smartphones. For example, my HTC Sensation has a Qualcomm MSM8260 clocked (originally) at 1200 MHz. The HTC Sensation XE has the exact same processor clocked at 1500 MHz.

Again, it is nonsense to say that overclocking this phone "is not really safe." You won't find one example anywhere of a person who has damaged this phone by overclocking it. These things don't get hot enough at any clock speed to damage the hardware.

4.a. Heat is probably the only legitimate concern with overclocking a smartphone, and that's exactly why there is no risk with the P500 -- it doesn't get anywhere near hot enough, at any clock speed, to cause any damage.

4.b. This shouldn't be a problem. If your phone is not setting clock speed on boot, then a crash/reboot will send your phone back to the original clock speed. Even if you make a mistake and change a clock speed that is being set on boot (which I actually did by accident just yesterday), you can boot directly into recovery and restore a backup.

4.c. Who cares? As I said before, if your system is unstable as a result of overclocking, then you should lower the clock speed. That isn't a problem.

4.d. *sigh*

But to each his own. If you don't want to go "yolo" with your antiquated $50 smartphone, then by all means, keep it at 600 MHz. Nevertheless, there is absolutely no way that you would damage it by overclocking, regardless of what you may believe.
[Optimus One, P500, V Q&A, Help & Troubleshooting] rharshit:
Well, its overc

lock

ing and not overc

loak

ing.

Small error, but make changes in the OP
[Optimus One, P500, V Q&A, Help & Troubleshooting] chalo99:
I wrote it bad in the title, but in the middle of the post it was OK. Thanks anyway, ****ing spanish that you read it like you write it, or viceversa.
[Optimus One, P500, V Q&A, Help & Troubleshooting] ghostswagking:
The phone won't work above 729MHz. And the only risk i can thinknof is depleting battery life faster. :D
[Optimus One, P500, V Q&A, Help & Troubleshooting] zenista:
Im actually using interactive min 480 max 806.

That permit no lag and normal reactivity.

Obviously there is a battery drain than normal.

I've also use a seeder application.
[XPERIA X10 Q&A, Help & Troubleshooting] addeysalameh:
i want to install feralab v34 on my x10,but every time when i flash it it gives me that the installation is successful ,and when i reboot the phone is stuck on SE logo

my android version now is 2.3.3

baseband 2.1.71

locked bootloader

xrecovery(0.3)

help me please :)
[XPERIA X10 Q&A, Help & Troubleshooting] bart69100:
Do you have flash kernel with ftf kernel file via Flashtool ?
[XPERIA X10 Q&A, Help & Troubleshooting] addeysalameh:
which kernel?

do you mean fera kernel v18??
[XPERIA X10 Q&A, Help & Troubleshooting] bart69100:
yes ! use last Rom and Kernel from Fera ! ( https://content.wuala.com/contents/feravolt/FeraLab/Firmware/FeraLab.zip/?dl=1 )

Readme/Howto file and kernel ftf file is include in ZIP file.
[XPERIA X10 Q&A, Help & Troubleshooting] addeysalameh:
i got a locked bootloader, and they said the kernel included in the rom so i don't need to flash it alone
[Android Q&A, Help & Troubleshooting] donavichcurtis:
First off let me apologize if my thread is in the wrong place (i'm new) anyway i have an xperia m (c1905) i bought an external sdcard to install apps on and what not but then i hit the 'you cant do that now' wall i i rooted my phone and installed Aparted and the like, i went through the process of setting a partition on the sdcard and found it didn't work so i gave it another go and again it didn't work so on the third try i made a huge mistake, i stupidly partitioned my internal memory and didn't realise until i had shut my phone down to then turn it on and see if it had worked this time, now of course my phone is as dead as a doornail, no flashmode no fastboot mode no charge no computer connection.... so my question is... is there any possible chance it could be related to something else and possibly fixable?

High hopes i know but i would like to at least try and bring it back to life :)
[Xperia Z Android Development] GROGG88:
​

I MADE THIS FOR MYSELF, BUT FIGURED I WOULD JUST SHARE IT​

System Requirements:

Device: C6602, C6603, C6606, C6616?

Current Firmware: Any stock 4.2.2 or 4.3 rom.

Root: Yes, you need root.

Recovery: Yes, you need recovery.

Flashtool: Yes, you need flashtool.

*do not ask how to prepare your device for this*

*this is not a Q&A thread*

Features:

This is a very stripped down and basic ROM designed to give more of a basic Google Experience while still running like Xperia. Especially good for those of us with locked bootloaders...

Nexus 5 KitKat Launcher, Calendar, Camera, Email, Clock, Keyboard, and Gallery

Nexus bootanimation

Fully Deodexed

Root (no fix required)

Init.d support

XZDualRecovery 2.7.76-Beta

Sony and other bloatware stripped

Xperia Z Camera

Z1 Camera Add-ons (Info-Eye, Timeshift, BG Defocus)

AOSP Camera with working Photo Sphere

AOSP Browser

Xposed Installer

Gravity Box

AOSP Nav Bar Icons

AOSP Style Status Bar Icons

Status and Nav Bar Transparency

Dark Themed Settings and Small App Launcher

KitKat Themed Status Bar Icons and Highlights

Custom Default Theme App

Active "Ok Google..." Voice Search

Stripped firmware is ES base

Directions:

Download ROM and place on SD card:

DOWNLOAD

Download stripped firmware ftf file and place on PC (if coming from Android 4.2):

DOWNLOAD

Boot into recovery (Don't know how to do this? Stop now and go read).

Create a backup (I shouldn't have to specify this, but sadly I feel it's needed).

Wipe data, cache, and dalvik cache.

Flash ROM zip from recovery.

Power off device from recovery (if coming from Android 4.2, otherwise go to last step).

Use Flashtool to flash the stripped firmware ftf file (if coming from Android 4.2)

(Don't know how to do this? Stop now and go read).

Reboot Device and Enjoy!

Tips:

Gravity Box seems to cause issues with reboots through advanced power menus or from recovery. This is not a ROM issue, but related to Gravity Box.

IF YOU MUST HAVE SONY MEDIA APPS THEN PICK THEM UP HERE AND INSTALL AS NORMAL APPS​

**I am, and will not be responsible for any mishaps you may run in to while using these files.

They have been tested and confirmed to be working.

If you can't follow directions then shame on you.

I will not provide support for laziness, or carelessness!**​

​

**This ROM is based on unbranded 10.4.B.0.569 from ES with added features and many items removed.

XZDual recovery 2.7.76-Beta from [MENTION=4904057][NUT][/MENTION]. Reboot wrapper from [MENTION=2784807]DooMLoRD[/MENTION].

Thanks to [MENTION=5442775]FateNozomi[/MENTION] for transparency resources.**​
[Xperia Z Android Development] GROGG88:
Changelog:

02/04/14 (pm):

NexperiaTheme.apk re-based off system default (fixed erroneous behavior and auto-applies).

Settings.apk menu re-ordered (GravityBox removed and Xposed moved to "Device" title).

GravityBox moved to data for easy removal (I don't use it).

Modified stock lockscreen added (hints/arrows removed, default wallpaper changed).

Screenshots:

02/04/14 (am):

Dark theme applied to themes settings.

Dark theme applied to call settings.

Dark theme applied to qs settings.

Dark theme applied to small app launcher.

Screenshots:

02/03/14:

Battery icon resized.

Transparent Navbar added.

Transparent Statusbar added.

Dark theme applied to settings.

Nexperia theme updated.

Gallery photo edit working.

(To Do...)

Apply dark theme to themes settings, qs settings, call settings, and small app launcher.

Screenshots:

02/01/14:

NexperiaTheme.apk quick setting color modified.

Extra keyboard IME removed.

01/28/14:

Google camera added (with working photo sphere).

Walkman added back in (because I like it).

Apps updated.

Multiple Xposed modules added (ones I find useful).

Stock battery, signal, and WiFi icons modified for KitKat appearance.

Nexperia theme app added.

Offline language updated for "Ok Google" support upon install.

Default wallpaper modified.

V1:

Initial release.

Screenshots:

​
[Xperia Z Android Development] R0MaN0:
Screens thanks

Enviado desde mi super XZ usando Tapatalk Pro
[Xperia Z Android Development] Waelhh90:
I will try this rom

I am using your deodexed version of 4.3 but there is only one bug in language and keyboard settings "fc"

Thanks man
[Xperia Z Android Development] GROGG88:
That's gone in this and the others.
[Xperia Z Android Development] Waelhh90:
Sorry but you release another versions of the deodexed rom??
[Xperia Z Android Development] GROGG88:
I have not updated changelog yet, but links are updated.
[Xperia Z Android Development] Jermino:
Downloading thanks for share.