About
This thread contains all the Android NAND development that is going on in different websites like Github.com
The developers are not responsible for any damages happened to your phone in any way so be aware of what you are doing
Note that the development is still in "Beta" state and it has few issues which are still under development, the Android NAND ROMs are almost ready for day to day use
you can always switch back to any windows mobile ROM by flashing the official or a custom windows mobile ROM just like when you had windows mobile using any Sony Ericsson Xperia X1 ROM Update utility or the SD Card (KOVSIMG.nbh) method, as the SPL or windows mobile's bootloader will not be effected
there will be few random screen flashes when the device start even when you shift back to windows mobile but this does not effect the performance of the device in anyway
Your SD Card Android ROMs are not going to be effected but you wont be able to run them unless you re-install Windows Mobile again
below is the list of whats working and not working so far
Working
Phone
SMS
Speaker
LEDs
Bluetooth (beta)
Headphone
Media Playback
Touch Pad
Data connection (GPRS/3G)
Main Camera (Beta)
Hardware acceleration (3D/OpenGL ES) (beta)
USB (beta)
Screen (beta)
Keyboard/Keypad
WiFi (Beta)
Battery Meter (beta)
Battery Charging
Battery Life (beta)
Camera Flash LED
GPS (beta)
Not working
Light Sensor (Under development)
FM Radio
Hardware Acceleration bugs
Flash Player support, YouTube HQ Mode support
Front Camera
Main Camera bugs (under development)
focus function
WiFi bugs (under development)
WEP connection support
GPS bugs (under development)
Bluetooth bugs (under development)
once turned on, causes rapid battery drain and cant be turned off unless user restart the device
USB bugs
Battery Life (beta)
still not same as Windows mobile
Screen auto rotation bug
rotates to landscape every time user turns the screen off and on
Battery Meter (beta)
inaccurate after certain percentage of battery
Downloads
below is the list of Files which are required
HSPL 0.78 (optional)
Download it from here if you haven't install a Custom ROM before or you are on initial HSPL 0.72
A ROM update utility (optional)
Kovsky Advance ROM update utility is recommended as Its easier to work with, but the official RUU and SD Card method will do the same
Latest Android bootloader
Download the latest bootloader available here
Android Driver and Fastboot
Xperoid installer is recommended as it contains the necessary files of Android SDK only and can do the job automatically,
Latest Android Recovery
Download the latest recovery available here
Latest Android Kernel
Download the latest Kernel available here
An Android ROM
choose and download your favorite Android ROM from here or here
Video
Here is the video of how to install any NAND ROM, lots of steps have changed but the main procedure is the same
PART 1
PART 2
1.HSPL
If you have already installed a custom Windows Mobile ROM and have the 0.78 version skip this part, to know about your SPL version turn off your phone, hold Volume down button and while holding hold the power button till you see the Tri colour screen which is the SPL; If you have Olinex name on any line, you have HSPL,
SPL is like your devices BIOS, and Hard SPL will unlock your devices bootloader to allow you to install any custom made Read only memory (ROM)
to do a HSPL refer to THIS thread
(if you had a problem in performing a HSPL, read the replies at the end of the above thread as there were some users not being able to HSPL the normal way and had to do few other steps)
2.Android BootLoader
Put the .zip ROM you have downloaded in the root of your SD Card before you do anything further; which means put the .Zip file in E:\ROM.zip if your SD Card drive letter is E
HTC Linux LK bootloader allows the device to run the kernel directly after it got turned on
Install it just like the way you install any other Windows Mobile ROM, which is using a RUU or the SD Card method
It is always recommended to do a Task29 before you flash an Android Bootloader if you know how to.
(Kovsky Advance RUU)
3.Kernel
Kernels are like drivers in PC, it connects and manage the hardware of the device
they have to be installed using Fastboot. Fastboot is a command line tool used to directly flash the filesystem in Android devices from a host via USB.
>For Windows users
Extract Xperoid Installer
Rename the Kernel you have downloaded to boot.img, then place it in the Xperoid fastboot folder
Rename the recovery you have downloaded to recovery.img, then place it in the Xperoid fastboot folder
connect your phone and install the drivers from Android USB driver folder
then simply run Xperoid Fastboot installer.bat from the Xperoid fastboot folder
>For Linux based OS users
follow the instruction on This page
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5.Recovery
ClockWorkMod Recovery is like the BIOS in PCs, which is the software that can install and manage the device's software
To go into recovery turn on your device and as soon as the phone starts (Sony Ericsson logo stage) hold the Camera Focus button which is holding the Camera button half pressed till recovery starts, (it might take few seconds to load)
once you are in recovery use the touch pad to go up and down, power button to go back and middle button to select trough the menu,
Go to mounts and storage> Format Data
Go to mounts and storage> Format Cache
Go to mounts and storage> Format dalvik cache
go back to main menu
Go to install zip from SDcard
select the file and install it
after installation select restart system now
Remove the SD Card and the battery, put the battery in, turn on the phone and wait till it completely start up
Re enter recovery with SD Card inserted and install the GAPPS
Load the system without SD Card and sync it with your accounts and open all the apps once and then restart again and once you are in android again insert your SD Card
If you are updating your ROM from an earlier version of NAND Android ROM
Download the full wipe script and put it in the root of SD Card
Go to backup and restore
select Backup
go back to main menu
Go to install zip from SDcard
select the full wipe script.zip and install it
go to main menu
Go to install zip from SDcard
select your new ROM and install it
go back to main menu
go to backup and restore
go to Advanced restore
select Restore data
go back to main menu
select restart system now
Recommendations:
Booting with SD Card inserted:
As you might have notice in the guide, the Kernels have a major bug of not being able to boot the ROM with a normally formatted SD Card inside the device. so we have to format the SD card in a special way to bypass this problem
To do so follow this guide
You have to perform these recommended actions for better performance
Back to Windows Mobile:
In order to switch back to any windows mobile ROM, enter the Windows mobile bootloader (SPL) by turning the device on while holding Power and Volume down buttons together, and once you entered SPL simply flash the ROM as you did earlier
It is always recommended again to do a Task29 before and a Hard reset after you installed a Windows Mobile ROM
report back your issues and problems for faster and better ROMs in future.
Special thanks goes to:
SP3DEV
Sun Dream
XDAndroid team
Neopeek
Ady
zargloub
Jerrytan
BrickPSP
Elibl
Im not asking for donation but press the thanks button , Please Vote for this thread too
Hi, very good guide... but
What features are working/not working on the NAND build?
lordblacksuca said:
Hi, very good guide... but
What features are working/not working on the NAND build?
Click to expand...
Click to collapse
updated
kerfooly said:
updated
Click to expand...
Click to collapse
could you add a link to gapps, too?
The guide is very good But I have allready done it
Edit: Just want to let you know, CWM is upside down.
Greetings, guys!
It is necessary to simplify setting!
Task 29
Hey guys,
Just tried to flash the NAND version, but after doing the task 29 I cant reconnect to the PC to flash the other stuff like LK Bootloader etc. All i get is the Sony Ericsson logo at the start of the boot.
How can to get around this?
Thanks in advanced
you must go in bootloader (hold Volume down+power button until you get in the tri-color screen) in order to connect to pc via usb
stefanpowell said:
Hey guys,
Just tried to flash the NAND version, but after doing the task 29 I cant reconnect to the PC to flash the other stuff like LK Bootloader etc. All i get is the Sony Ericsson logo at the start of the boot.
How can to get around this?
Thanks in advanced
Click to expand...
Click to collapse
Go in Bootloader to flash LK Boot
Hi Guys !
When wallpaper are changed the Android will restart. And sometimes reset when I try to unlock phone.
EDIT:
And when I try to unlock the phone screen will be whole black until the keyboard is opened.
Yes, these problems are kernel related...
Like bad wifi width, no mobile data (can't understand why it isn't included, because it says it is easy to add).
Finally, This sounds great ... finally a NAND build ... following with great excitement ... I'll flash it as soon as I get a chance ... college is keeping me busy ... but I'll try to find time to read and figure it out ...
THANKS SO MUCH
Great
Thanks for the update, very nice build, I hope we can have a fully working android in NAND soon.
Thank you all.
Waiting For Final NAND Android?
Are you developing this Nand Rom?
tamakura said:
Waiting For Final NAND Android?
Are you developing this Nand Rom?
Click to expand...
Click to collapse
if you want final nand soon just flash this and report errors and issues, it will help alot
neoofoox said:
could you add a link to gapps, too?
The guide is very good But I have allready done it
Edit: Just want to let you know, CWM is upside down.
Click to expand...
Click to collapse
updated again please do report more
tamakura said:
Waiting For Final NAND Android?
Are you developing this Nand Rom?
Click to expand...
Click to collapse
No this is mostly done by SP3DEV (alex)
does this ROM support Flash and AVI?
Hammerhead89 said:
does this ROM support Flash and AVI?
Click to expand...
Click to collapse
non of the ROMs support Flash player, but AVI, if you install an app and your file be small maybe
Could someone send me the driver for x1 while it is connected in fastboot mode, because it can't find a driver (win xp) have tried the contained driver in the sdk pack, and some others.
I am new here. I flash LK Bootloader successfully. But I don't how to do next step. I downloaded and installed Android SDK, I installed Google usb, I start the phone and it's start into boot loader screen with "reverting to fastboot..." so I don't know ho to do fast boot via PC
=============================
I did it but recovery is up - down :-( any solutions?
Related
[Tutorial][Newbie Only] How to Install & Run Android on SE X1
[email protected] Post here if you have Trouble Installing Android on [email protected]=
So, All Troubles are Gathered in One Thread
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
!!!WARING!!!
This tutorial is ONLY intended for NEWBIE Like ME, Who don't Know How to Run Android on X1 at first place
I'm not Pro on Andoid Stuff + This is my First Guide on XDA.
And I'm Not Use English as my daily Language
So If there is Any Mistakes Please Tell me
Any Suggesstions & Critics are wellcomed
Mods Please delete my Thread if it's posted Already
THANKS
Please Note that Android for X1 is Still in Delvelopment state..
So there Might be some non working camera, Bluetooth, GPS, Apps, etc...
But Hei..... we Run Android On Our Winmo Device
So.. Use it at Your Own Risk
OK Let's Begin
Currently, We Run Android From SD Card by Run Haret.exe
Just wait and see untill Developers Create a Pefect Android Build for Us
Then Maybe we will able to Flash it to our Phone to replace Winmo
Basicly There is two type of Android Build For X1
at least for Now. Next?? Who Know
1. Fat32 Build
This is old method to Run android on our device
+ No need to create partition on SD Card.
+ No need to install andoid, just copy files to SD Card then Run Haret.exe
- It's slower Android build
Main Files on Fat32 Build may Looks like this
Some of Fat32 Build:
- [F1 Froyo 2.2.2 V3][FAT32]
- Xperia-Xdandroid-X1 2.2.1 25.11,Fatsal-xperoid 2.0.1 25.11,Hero Sense UI 2.1 25.11
Fat32 Build Installation:
1. Download Android & Unzip
2. Copy All Files to Root of SD Card
3. Run Haret.exe
Simple right
2. EXT2 Build (introduced by Neopeek)
it's usually faster than Fat32 Build
- Need to Create EXT2 Partition
- Need to install Android before run Haret.exe
+ Android run Stable, Faster & Smoother!!!!. <<== This is what we Need
Main Files on EXT2 Build may Looks like this
Some of EXT2 Build:
- CM Modded V.2 [26.1 FPS] - HoneyComb Froyo V.2 - PureFroyo - SupeFroyo Modded by Needo
- (◣_◢)CyanogenMod 6.1(◣_◢)v1.5
- F1 Froyo 2.2.2 V3 by Faryaab
EXT2 Build Installation:
1. Create EXT2 Partition on SD Card (Explained Later)
2. Download Android & Unzip
3. Copy All Files to Root of SD Card
4. Install Android by Run install.exe from npkinstall Folder
You will see alot of text running there..
Just wait until it's Done
Then your phone will reboot to Winmo5. Run Haret.exe from Root of SD Card to Run Android
3. ClockWorkMod [CWM] Build (introduced by Neopeek)
Refer Here for CWM Update
Currently, This is Best method to Run android on our device
- Need to Create 4 Partition on SDCard [Fat32 & 3 ext2 Partition]
+ Easy to install & Change to another Android
+ Android run Stable, Faster & Smoother!!!! than any Fat32 or EXT2 Method
+ Easy doing a wipe, cleaning cache, (re)formatting sd-card
+ Easy adding/update files on ROM even after installing android & More
+ Superuser & adsblocker working perectly
+ Enable to mount system as writable
Profits for Developers
+ No need to play around with rootfs any more.
+ Android system structure is now 99% native android compatible. Meaning that rom devs simply work with the /system folder.
+ ROM installation / update is done via ZIP files as on native android devices. No tgz, tar.gz or ext2 files any more!
Main Files on ClockWorkMod [CWM] Build may Looks like this
Some of CWM Build:
- [X1][CWM] TouchWiz CM6.1[21.04.2011]
- [ROM] x1 - HoneyComb V2 - ClockworkMod - 20/04
- [ROM] Xperia1 FRX06 V.2-CWM (07.05.2011)
ClockWorkMod [CWM] Build Installation:
Preparation:
1. Create Fat32 & 3 EXT2 Partition on SD Card (Explained Later)
2. Download Neopeek's CWM
3. Copy npkboot folder on Root SD
4. Get kernel, ts-calibration & startup.txt for X1 then copy to npkboot folder
5. Download Android CWM compartible & copy Zip ROM on Root SD
Launch CWM & Android Installation
1. Run HARET, wait until it ask to press "Volume Down"
2. Press "Volume Down" shortly to Launch CWM
3. Go to "install zip from sd card" to install Android
- Use D-Pad or volume Button to navigate
- Press D-pad Button Down to Confirm4. Choose your android rom (zip file) that you want to install then click "yes"
5. When installation finish, go to CWM main menu & Choose Reboot
To Run Android just run Haret.exe from npkboot folder and wait as usual
Neopeek's CWM Screenshot
Detail info Please see here
Creating Partition on SD Card
1. Create EXT2 Partition on SD Card
*It's Recomended to Backup All Your Files on SD Card
Tool : Minitool Partition manager (Freeware Home Edition)
Preparation:
1. Install Minitool Partition manager
2. Connect Phone to PC then Choose USB Connection or You can Plug your SD Card to PC Using Card Reader
Create Partition:
1. Open Minitool Partition Wizard
2. Delete Existing Partition from SDCard
3. Create Fat32 Partition, Set As Primary!!!
4. Create EXT2 Partition, Set As Primary!!!
5. Create Linuxswap Partition, Set As Logical!!!
Video Guide to Create EXT2 Partition
INFO:
- You have to define the sizes of the partitions so that the FAT32 is the Largest, EXT2 is Smaller, and linuxswap is 64
- Fat32 Act As SD Card on Android
- EXT2 Act As Phone Memory. EXT2 Partition only mountable on Linux
- Linux Swap is like an extra RAM on the memorycard so you can run more apps at the same time. more info see here
- Under windows, Only the Fat32 Partition will show as mountable, but in minitool partition manager, it will show all 3 partitions..
2. Create CWM Partition on SD Card
[/B]
Preparation:
1. Install Minitool Partition manager
2. Connect Phone to PC then Choose USB Connection or You can Plug your SD Card to PC Using Card Reader
Create Partition:
1. Open Minitool Partition Wizard
2. Delete Existing Partition from SDCard
3. Create Fat32 Partition, Set As Primary!!!
4. Create EXT2 Partition (System) about 150MB-200MB depend on ROM, Set As Primary!!!
5. Create EXT2 Partition (Data) about 150MB-250MB Set As Primary!!!
6. Create EXT2 Partition (Cache) about 50MB Set As Primary!!!
Video Guide to Create EXT2 Partition
Thanks to BlackRa1n
Will Update With more info that I Found
Android Buttons Layout
* X Panel Button = Home Button
* OK Button = Back Button
* Left Softkey = Menu Button
* Right Softkey = Standby & Lock Button
* Call Button = Dialer Button
* Call End Button = Standby & Lock Button
* Volume Buttons = Volume Buttons
* Power Button = Standby & Lock Button
* Camera = Home Button
What to do when First Time Run Android?
*Note: Android may run Slower on first Run
1. Do some important Settings
- Set your APN if it not Automatic detected
Go to Settings > Wireless & Networks > Mobile Network.
Enable "data enable"
Set your APN at "Access Point Names" then Add "New Apn"
if you don't how to do it use APN apps such as
Apn Droid or Asisten APN(indonesian User Only)- Syncronize to Google Account
Go to Settings > accounts & Sync. then add Account- Sparepart App (install if it's not included in your Build)
Open Sparepart App, go to end button behaviour.
Set to "Nothing" or "Go to home" (prefered)- Display setting
Go to setting > Display.
Disable auto-rotate screen
Animation set to "no Animation" (Speed up Android)
Reduce Brightness (save battery Life)- Application Setting
Enable Unknown source to allow installation of non-market apps
Go to Settings > Application- Disable GPS if you are not using it (recomended to save battery life)
Go to Settings > Location & security. Disable Use GPS satelites- Other settings please refer to Your Android developer in his Thread
2. Open All Application such as 3D gallery, Music, etc. Let Apps load data's
3. Reboot.. Then Android will Run Faster.
Kernel
If you have problem with Wifi, Battery, etc on Android Build, First try to change kernel..
What are kernels?
You can compare the kernels to the drivers from your computer. They can ensure that your WIFI work or that the camera from phone doesn’t work.
jwte said:
A kernel isn't just drivers, it's the OS but without any apps or anything else that you need. And modulesxxxxxxx.tar.gz are usually drivers that you can hook up to the kernel and it better to have buggy drivers in a module so you can restart for example the keyboard driver without need to restart the OS (kernel) and Android.
Click to expand...
Click to collapse
What files are the kernels?
The kernels are named by “modulesxxxxxx.tar.gz” and “zImage”
Credit goes to: Great_Day
How to Change Kernel?
1. Delete Your Current “modulesxxxxxx.tar.gz” and “zImage” from Root of SD Card
2. Replace with the New One then Run Haret.exe
More About Kernel
- Kovsky Kernel Development
- Kovsky Kernel Development [2.6.35]
- [Version: v4b] SEX1 Android Kernel
- Kovsky Kernel Development [2.6.27]
*Recommended to Use YGGE's (Duckly) Kernel... Find it here
5. Create Linuxswap Partition, Set As Primary!!!
Click to expand...
Click to collapse
I think this should be set as logical.
Overall, great guide!
AssasinQ said:
I think this should be set as logical.
Overall, great guide!
Click to expand...
Click to collapse
Sorry for that, Thanks for Help
First Post Update
great guide and thx now my little sister is happy with her phone
squallvai said:
- Linux Swap, I Don't Know what is this for (Maybe someone Can Explaind it??)
What are kernels?
You can compare the kernels to the drivers from your computer. They can ensure that your WIFI work or that the camera from phone doesn’t work.
Click to expand...
Click to collapse
Swap is like an extra RAM on the memorycard so you can run more apps at the same time.
http://www.linux.com/news/software/applications/8208-all-about-linux-swap-space
A kernel isn't just drivers, it's the OS but without any apps or anything else that you need. And modulesxxxxxxx.tar.gz are usually drivers that you can hook up to the kernel and it better to have buggy drivers in a module so you can restart for example the keyboard driver without need to restart the OS (kernel) and Android.
Please correct me if I am wrong
Thread Update [07 April 2011]
Change LOG:
Revision:
- Linux Swap Partition as Logical. Thanks to AssasinQ
- Linux Swap info. thanks to jwte
- Kernel info. thanks to jwte
Added:
- Android Buttons Layout
- What to do when First Time Run Android?
thanks so much! i appreaciate your work! now i can start testing Android on X1! yay !!
Nice tutor, but I can't sent you "Cendol" here.
is there anyone running any android build on the Dynamics ROMs? since when i flash this ROM i couldn't enter any haret.exe when i press it the loading window opens and right before the 2 vibrations everything stops (it doesnt even vibrate once) anyone knows the solution, can HaRET have problem with Dynamic ROMs only
i have 8GB SDHC and tested with both old EXT2 and CWM formatings
my Radio version is the normal one
i put everything in the root of SD card
kerfooly said:
is there anyone running any android build on the Dynamics ROMs? since when i flash this ROM i couldn't enter any haret.exe when i press it the loading window opens and right before the 2 vibrations everything stops (it doesnt even vibrate once) anyone knows the solution, can HaRET have problem with Dynamic ROMs only
i have 8GB SDHC and tested with both old EXT2 and CWM formatings
my Radio version is the normal one
i put everything in the root of SD card
Click to expand...
Click to collapse
here the answer:
Needo said:
dynamics rom is Overclocked by default and haret can't boot your phone in linux while phone is O/C in WinMo ..
So ..
1- You can run android using Applications\Android & OC will be disabled automatically ..
(you can use it if the haret.exe is present in root SD)
2- Or you can use the .cap ultrashot provided to disable overclocking permanently ...
3- Or just click this ..
( \Application Data\OC_disable.lnk ) & it will be disabled temporally (till the next restart) ..
4- Or you can simply use WinmoSpeed to control CPU speed (set it to defualt) ...
Click to expand...
Click to collapse
Needo said:
if this problem is still present .. make sure that android O/C isn't more than 614 mhz .. some processors can't boot in linux with higher values !
Open startup.txt & if you found O/C command like that
( acpuclock.oc_freq_khz=652000 )
just change the value to 614000 ...
& Hope this can help you enjoying android on your phone
Click to expand...
Click to collapse
hi, the video shows a LinuxSwap primary partition, in the guide you have written logical
Thread Update [15 May 2011]
Change LOG:
added:
- ClockWorkMod [CWM] Tutorial
- CWM Partition Video (thanks to Blacka1n)
Nice, that u added the CWM.
So i just got one Question, whats about bigger SD Card?
How would u suggest to split the SD if i got f.e. 8 gb or even 16 or more?
if i had the space is there any reason why i could give the Cache much more storage?
As far as i cann see, the Rom always just use as much as it need never more?
So but whats about the Data?
Isnt it where me ROMS going to be stored? So it would be smart to make this bigger when i want to use a lot of Roms?
And the FAT is just for thinks i want on Wimo ( if i want to xD) and such kind of datas like music and so on?
So i would be realy happy if u could explaint thoose thinks,
but by the way this guide is very nice, AND easy to use, so
Vote for Sticky
hello,
I folowed this guide to boot android on my x1 but i got stucked.When I enter on haret it says loading linux 2 vibrates and it freezes.I tryed everithing.I set up my cpu speed to 528 Mhz and edited the startup file too.I have dinamic ROM.Is there any chanche that this ROM isn't compatibile with this time of android installer?
the.taz911 said:
hello,
I folowed this guide to boot android on my x1 but i got stucked.When I enter on haret it says loading linux 2 vibrates and it freezes.I tryed everithing.I set up my cpu speed to 528 Mhz and edited the startup file too.I have dinamic ROM.Is there any chanche that this ROM isn't compatibile with this time of android installer?
Click to expand...
Click to collapse
Please see Here or Here
hi squallvai,
thanks for the reply.I saw that post & that topic and I did what they sayd ,but nothing.i'll change my ROM and i'll try to change my CPU speed from registry.
LE: I edited cpu speed from registry(it's 528 now) and it still doesn't work.I'll change my ROM and get back here.If You have any ideas why it doesn't work feel free to post here.I know it doesn't work becouse of the cpu speed...but i changed it and it stil ldoesn't work.what am I doing wrong?
LE: I changed the ROM and it isn't working same problem.any ideas please?
thnks man. Y try to install the Froyo 3V
thanks for this information.
it was only because of this thread that i had courage to install and try android on my x 1.
mini tool cannot partition my sd card
i tried to do partition of my sd card exactly as shown in the video, but after completing the process the mini tool shows only fat32 partition with the whole memory of the card
http://www.partitionwizard.com/download.html
Greetings,
Me and krook1 have been working on a CM9 port for the Lenovo Ideapad K1. This is an Alpha release as there is still a lot of work to be done. I have included instructions to either flash as an update.zip with CWM recovery, or if your still on stock you can use the nvflash package.
I have very limited time to invest to this project so if anyone would like to help please join us at freenode IRC room #ideapad-k1. The source code download link is posted below.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Working
-Touchscreen
-Wifi
-Bluetooth
-Accelerometer
-Rotation Lock
-Internal and External Storage
-Audio (thx Koshu and digetx)
-HW Acceleration (thx digetx for green overlay fix)
-CWM Backup/Restore - Fixed by using updated CWM below
Not Working
-GPS? appears to work but doesn't connect?
-HD Video Streaming
-Microphone
-Camera
Haven't tested HDMI out
Changelog
Alpha 1.6
- Fixed storage issue
Alpha 1.5
- Bluetooth fix (Audio doesn't work?)
- Full market compatibility
- Hardware buttons
- Rotation Lock Switch (Functions, but doesn't notify the SW layer)
- External SD mounted at /sdcard/external_sd and linked to /mnt/sdcard2
- goo.im app OTA update compatibility
- Synced with CM9
- New CM9 Bootanimation
- nvflash package includes updated CWM with working backup/restore
Alpha 1.0
- Initial Release
Downloads
As usual flash at your own risk
Gapps
http://goo-inside.me/gapps
CWM Package
update-cm-9.0.0-ALPHA1.6-k1-KANG-signed.zip
md5sum: 239091872daae568d7e9f1680ce49176
1. Place the update.zip on your external sdcard
2. Reboot into recovery.
3. Wipe data/Factory reset
4. Install .zip from sdcard
5. Choose the update.zip and say Yes
6. Flash gapps (optional)
Nvflash Package
K1_CM9_Alpha_1-5_nvflash.zip
md5sum: 7c34ec9242ab6ad4659b3bf310627ff4
Nvflash Windows Drivers
md5sum: 9aa3a4814ca63366329d85a22ed01f64
To boot into APX mode:
1. Power off
2. Hold down the Vol - and the Vol +
3. While holding the Volume keys down, Power on
4. The display should go black, and both LED's on either side of the home button should light up. This is APX mode.
How to flash:
1. Extract the K1_CM9_nvflash.zip contents to a directory
2a. If using Windows, double click the "flash-windows.bat" file
2b. If using Linux, cd into the extracted directory and run either "sudo ./flash-linux.sh" or "./flash-linux.sh" from a root prompt
Source Code
http://github.com/khanning/android_device_ideapad_k1
-or-
git clone git://github.com/khanning/android_device_ideapad_k1.git
Special Thanks
The entire Cyanogenmod team and everyone that has contributed to CM
digetx
Koshu
Jon2555
All the developers that have made the source code for their device tree public. Thank you for helping to move the Android development community forward.
Thank you khanning88 and krook1 for releasing the first ICS rom for the K1!! Of course you had to upload this right before I leave for work, but thats okay! Now I have something to try out over break next week. Woohoo!!
thanks for another great rom ...even being alpha fast and smooth
Been running ice for around an hour now and no issues in performance
Glitches I've noticed
External SD shows being mounted but shows empty in total commander and es file explorer
and will not allow access
But other then the posted issues its running great
Sent from my K1 using xda premium
Just installed this, running great.
Installed Apex Launcher (smooth and fast)
link >>> Apex
Tried Chrome browser, kept crashing
Physical home button doesn't do nothing (no big deal, low priority)
Can't seem to get it connected to pc via usb port.
Storage > USB computer connection > MTP is checked.
After going through the Rom and I've noticed I can get to the external sd card if I go through. /mnt/sdcard2
But not through the regular way
I'm also going to make an update.zip for full screen nexus prime boot anim
Sent from my HTC Sensation 4G with Beats Audio using xda premium
This is excellent news.. ! Great to see progress on K1 custom ROMs!
Even though i have flashed custom roms on other android devices, i am a nOOB when it comes to K1 -- ie, should the tablet be rooted first before one can flash this ROM ? (using Root methods mentioned on other threads here?) or just do what is mentioned here ? -- Sorry.., but inputs here will help a lot of us.
djsat03 said:
Just installed this, running great.
Installed Apex Launcher (smooth and fast)
link >>> Apex
Tried Chrome browser, kept crashing
Physical home button doesn't do nothing (no big deal, low priority)
Can't seem to get it connected to pc via usb port.
Storage > USB computer connection > MTP is checked.
Click to expand...
Click to collapse
DISREGARD THE POST BELOW. BROWSER STILL CRASHES. BUT THIS ONE INSTALLS IF ANYOE WANTS TO PLAY AROUND WITH IT.
Chrome browser works. The problem is the same that all other unofficial ICS builds on other devices have. It has to do with the Device Id Check in the apk from the market. Download chrome from the link below and you are smooth sailing.
http://forum.xda-developers.com/showthread.php?t=1515900
Sent from my K1 using XDA
arjunprabhu said:
This is excellent news.. ! Great to see progress on K1 custom ROMs!
Even though i have flashed custom roms on other android devices, i am a nOOB when it comes to K1 -- ie, should the tablet be rooted first before one can flash this ROM ? (using Root methods mentioned on other threads here?) or just do what is mentioned here ? -- Sorry.., but inputs here will help a lot of us.
Click to expand...
Click to collapse
Like any Android device, flashing custom rom need custom recovery installed (ie CWM revovery).
And root is needed to install custom recovery !
Even the default browser for ICS crashed a lot. So far no problems with dolphin browser HD from market. Its fast and smooth browsing on there.
quyTam said:
Like any Android device, flashing custom rom need custom recovery installed (ie CWM revovery).
And root is needed to install custom recovery !
Click to expand...
Click to collapse
djsat03 said:
Even the default browser for ICS crashed a lot. So far no problems with dolphin browser HD from market. Its fast and smooth browsing on there.
Click to expand...
Click to collapse
I am not a NOOB, as I flash roms to my Droid Incredible all the time, but I have found the detail of instructions on flashing/root in the Idea K1 to be a bit confusing.
So any chance someone could add to the detail above, " if not rooted do install process #2 and follow these step by step"
Reads as if we can use the nvflash method, but no mention of rooting before, if that is the case great. I am looking forward to getting a new rom installed on my K1 as the stock is very buggy!
sorry, didn't see the nvFlash method. Not sur it need root or not (but think it's also needed)
quyTam:
Sorry for not getting back to you sooner. The CWM update.zip is used if you have already used my Honeycomb rom with CWM included. If you are on stock, or unsure, just use the nvflash method. There are no requirements to using the nvflash method because it reformats all the partitions. (root is not required, and it doesn't matter what build you are coming from)
ok, thanks for your reply.
didn't know the nvflahs method; it works on all Android device ?
ps: I don't have K1 but Thinkpad. Is it because Thinkpad doesn't have his bootloader unlocked, so it's not possible to use nvflash ?
khanning88 said:
quyTam:
Sorry for not getting back to you sooner. The CWM update.zip is used if you have already used my Honeycomb rom with CWM included. If you are on stock, or unsure, just use the nvflash method. There are no requirements to using the nvflash method because it reformats all the partitions. (root is not required, and it doesn't matter what build you are coming from)
Click to expand...
Click to collapse
Great to hear, is there any special needs for nvflash or is everything included in the nvflash method. I seem to remember in one of the rooting methods reading about installing drivers or related software necessary to use nvflash.
dc52317 said:
Great to hear, is there any special needs for nvflash or is everything included in the nvflash method. I seem to remember in one of the rooting methods reading about installing drivers or related software necessary to use nvflash.
Click to expand...
Click to collapse
i downloaded the nvflash zip file,.. and it talks about apx drivers.. and asks the user to have the tablet in apx mode --- where can one find that ?
arjunprabhu said:
i downloaded the nvflash zip file,.. and it talks about apx drivers.. and asks the user to have the tablet in apx mode --- where can one find that ?
Click to expand...
Click to collapse
That is exactly what I am trying to find out. I am planning on installing this when I get home in a few hours, but I am hoping that someone can add that detail to the post. I was looking a bit earlier, and found references to making sure you have these apx drivers installed for rooting etc, but no instructions.
Updated the nvflash section with the APX drivers and instructions.
Updated CWM recovery to 5.5.0.4 and fixed Backup/Restore. This will be incorporated into the next nvflash package. For now download the updated CWM recovery .zip in the 'Mods' section of the first post, and flash from recovery.
thank you..! Will try this out soon...
if i have to go back to stock rom from this ROM -- whats the process/steps?
Also, before I do this, is there a way for me to do a nandriod backup of the existing rom from within CWM ?
arjunprabhu said:
thank you..! Will try this out soon...
if i have to go back to stock rom from this ROM -- whats the process/steps?
Also, before I do this, is there a way for me to do a nandriod backup of the existing rom from within CWM ?
Click to expand...
Click to collapse
if you are not rooted and don't cwm on it already. Then just do the nvflash package instructions posted in the op.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ouya Bootmenu development/release thread
This is based on the awesome work by Hal9k.
Because of the fact that the Ouya doesn't have recovery accessibility via hardware buttons we need to play safe and utilise chainbooting.
This bootmenu resides in the kernel partition and is loaded on every normal bootup.
In-depth info in Hal9k's thread here: http://forum.xda-developers.com/showthread.php?t=2499673.
It presents various choices on every boot:
Normal boot - (default) loads bootimage from system partition (/system/boot.img)
Alternate boot - loads bootimage from sdcard (/sdcard/altboot.img)
Recovery - reboots into recovery (recovery partition)
Failsafe - loads built-in failsafe mode
Bootloader - Reboots into stock bootloader (for fastboot access - USE WITH CARE)
Notes about the failsafe
the failsafe mode (which has the bootmenu built-in) will pop up in the following cases:
the bootmenu could not find a valid bootimage (read: /system/boot.img for "normal boot"; /sdcard/altboot.img for "alternate boot")
the user selects "failsafe" from the menu
the failsafe mode resides in the bootmenu image itself and should ONLY be used (as its name suggests) as failsafe.
for regular flashing you need to use a newer cwm version which resides in the recovery partition and is accessible via the "recovery" entry in the bootmenu (see below).
And remember: After flashing this you DON'T NEED TO EVER touch your boot/LNX partition again
Reminder: Failsafe mode is ONLY to be used in case you can't boot into your recovery partition. For regular rom flashing the respective CWM recovery (see below) is required.
Installation
You need to have a newer CWM recovery installed in order to flash the bootmenu.
READ AND UNDERSTAND what you are doing!
This bootmenu is flashed over your current bootimage - newer cyanogenmod builds will place their bootimage to /system/boot.img automatically. if you are not using a custom rom you will need to relocate your bootimage (read: kernel) to /system/boot.img manually.
You need to have a newer CWM recovery installed in order to flash the bootmenu (otherwise you'll get a build.product mismatch while installing).
1a) If you already have an older custom recovery installed:
Boot into recovery and flash https://download.milaq.net/public/android/ouya/misc/recovery-clockwork-6.0.4.8-ouya.zip. This will update your recovery to a newer version allowing you to flash the bootmenu regularly.
1b) If you don't have a custom recovery installed:
You can either use the one-click installer from http://forum.xda-developers.com/showthread.php?t=2295645 and continue with step 1a).
Or you can flash a newer recovery via fastboot (if you know what you are doing): https://download.milaq.net/public/android/ouya/misc/recovery-clockwork-6.0.4.8-ouya.img
2.) Flash the bootmenu via (the new) recovery by installing the latest updatezip (download below). Make sure that the installation procedure was successful.
If you get a "MD5 mismatch" your download is probably broken. Just redownload and try again. The installscript checks the md5's mutliple times while installing and reflashes your old bootimage in case something goes wrong.
So if you are not doing something REALLY stupid this is safe to go.
Download
Download latest version (v2.0.4)
Changelog
Code:
2.0.4
* reduce menu timeout for faster regular boot
* ui improvements in failsafe mode
2.0.3
* bootmenu: increase maximum number of input devices to 5 - e.g. the gpio
keys (the ouya power button - 1 node), a mutlimedia keyboard (2 nodes), a mouse (1 nodes)
and a controller (1 node).
2.0.2
* add in additional alternate boot image folder handling to fix compatibility with kitkat
* update failsafe recovery to differ more from regular recovery
* minor ui and ux tweaks in both bootmenu and failsafe
2.0.1
* initial reworked version
And as always: we take no responsibility whatsoever for raging, screaming, crying, frustration, failing, confusion, dead kittens, etc.
Source
https://github.com/milaq/ouya_bootmenu
Thanks/Credits
Click to expand...
Click to collapse
Hal9k - for the inital ouya bootmenu and many great ideas
Dan Pasanen (invisiblek) - for great work on the recovery and initial porting efforts
Let me know if i omitted you and i will add you here asap
IRC channel
Click to expand...
Click to collapse
Visit us in #cyanogenmod (general) or #cyanogenmod-dev (only dev related talk) on freenode
alright so i installed it, and normal boot boots back into recovery
YoshiFan501 said:
alright so i installed it, and normal boot boots back into recovery
Click to expand...
Click to collapse
This bootmenu is flashed over your current bootimage (you will need to relocate your kernel (to /system/boot.img) if you not using a custom rom)
Click to expand...
Click to collapse
most probably because /system/boot.img is not found. you need to install cyanogenmod afterwards or relocate your bootimage if still on stock.
Is it possible to easily revert the Ouya to a fully stock state after this? Any unninstall method?
Fyi everyone, if you scroll down through the options in cmw a couple times you'll activate rainbow mode! I'm not sure if this is an ouya specific cmw mod or not cuz all my other devices have twrp but anywho ENJOY!
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
Is it possible to use this bootloader with the EternityProject Kernel 3.4.37 for OUYA and the OUYA-Enhanced Rom. I can flash the ROM from within Recovery, but how do I install their kernel for it to boot in ouya bootmenu? I just don't want to brick, thanks for your help!
Just wanted to be the first to tell you that it's working fine and I'm glad to finally give the ouya what it deserves: a custom ROM! Thanks dude!
Can someone post a step by step to move from ep bootlegger to this one?
So can this be dualbooted? If stock ouya boot image is put on /sdcard and named altboot.bin? Right now if I select Alternate Boot, it boots cwm 6.0.3.2. Same as Failsafe.
new version
new version is available in the first post
firmtech said:
So can this be dualbooted? If stock ouya boot image is put on /sdcard and named altboot.bin? Right now if I select Alternate Boot, it boots cwm 6.0.3.2. Same as Failsafe.
Click to expand...
Click to collapse
update the bootmenu to v2.0.2 and rename your alternate bootimage on /sdcard to "altboot.img" and you should be ready to go
milaq thanks for excellent work....
Can you add reboot recovery options in Ouya Failsafe menu to get the full recovery menu?
The power button(for choices) works only if ouya connected-hdmi to hdmi
If Ouya connected hdmi to dvi(Pc monitor) the power button does not respond!
So to go into recovery mode, you can use alt + printScn (SysRq) + i (if keyboard connected)
But now the Ouya goes into a Failsafe menu.
version bump again
krest said:
the power button does not respond!
Click to expand...
Click to collapse
i suspect that you have too many input devices connected during boot.
in version <=2.0.2 the maximum number of input devices that are recognised in the bootmenu was 3.
in case you have a keyboard (usually takes up 2 input nodes) and a mouse connected, the ouya power button (also an input device) was at the end of the list thus not taken into account.
i raised the number of recognised input devices to 5 in version 2.0.3 (see first post for download). that should allow most setups to work fine.
in case you still can't use the power button to select just briefly disconnect your usb devices at boot and reconnect them after making your choice in the bootmenu.
milaq said:
i suspect that you have too many input devices connected during boot.
in version <=2.0.2 the maximum number of input devices that are recognised in the bootmenu was 3.
in case you have a keyboard (usually takes up 2 input nodes) and a mouse connected, the ouya power button (also an input device) was at the end of the list thus not taken into account.
i raised the number of recognised input devices to 5 in version 2.0.3 (see first post for download). that should allow most setups to work fine.
in case you still can't use the power button to select just briefly disconnect your usb devices at boot and reconnect them after making your choice in the bootmenu.
Click to expand...
Click to collapse
Yes, you're right....
Now it's working perfectly
In any case, it would be great if you added the reboot recovery options in Ouya Failsafe menu.
Thanks
Dual Boot
Now that I have CWM with the newest boot menu and CM11 running super smooth how do I go about flashing the stock Ouya ROM to the SD card without wiping the whole thing again? Must restore balance in the household. The natives are demanding to have Amazing Frog back!
bootmenu v2.0.4
new version up.
see first post for details.
KJRob said:
Now that I have CWM with the newest boot menu and CM11 running super smooth how do I go about flashing the stock Ouya ROM to the SD card without wiping the whole thing again?
Click to expand...
Click to collapse
dual booting the stock rom is not as easy as it may seem.
with the boot menu you _have_ the ability to dual boot another boot image (read: kernel/ramdisk) but you still need to have a partition where all stock roms system files reside. the internal "sdcard" is out of the game here as it is just a fused filesystem. but i could imagine external usb storage or such. one needs to partition it and make the respective changes to the stock ramdisk for it to work.
nevertheless, i will not spend time working on stock rom dualboot compatibility. but anyone willing to invest time into it is very welcomed to do so.
milaq said:
new version up.
see first post for details.
dual booting the stock rom is not as easy as it may seem.
with the boot menu you _have_ the ability to dual boot another boot image (read: kernel/ramdisk) but you still need to have a partition where all stock roms system files reside. the internal "sdcard" is out of the game here as it is just a fused filesystem. but i could imagine external usb storage or such. one needs to partition it and make the respective changes to the stock ramdisk for it to work.
nevertheless, i will not spend time working on stock rom dualboot compatibility. but anyone willing to invest time into it is very welcomed to do so.
Click to expand...
Click to collapse
I appreciate the reply. I would love to have the know how to do the work but that is out of my knowledge base. Maybe one day I will. I can wait for the official Ouya store to hit android. The kids will have to wait as well. I love my KK device just the way it is.
milaq said:
dual booting the stock rom is not as easy as it may seem.
with the boot menu you _have_ the ability to dual boot another boot image (read: kernel/ramdisk) but you still need to have a partition where all stock roms system files reside. the internal "sdcard" is out of the game here as it is just a fused filesystem. but i could imagine external usb storage or such. one needs to partition it and make the respective changes to the stock ramdisk for it to work.
nevertheless, i will not spend time working on stock rom dualboot compatibility. but anyone willing to invest time into it is very welcomed to do so.
Click to expand...
Click to collapse
It's doable but once its done both sides of the roms would have significant storage reduction... on another note the method would be completely ( and easily ) reversible to the actual installed rom.
The other route is like you said with usb storage which would probably be the better of the 2 options.
Although with all this said we know that the ouya storefront is coming in the form of an app and I guess the other option would be to "portablize" the current framework ( I did it with 519... could try with the latest one... but I never tried it on anything higher than 4.3 )
How do you revert back to factory settings? Every time I flash stock, it boots to this. Thanks and sorry in advance
This guide is for fellow at&t customers who will be stuck with JB 4.1.2 forever because there won't be an official 4.3 release (and any new Sony phones until at least the next year).
WARNING: You may lose some of your contacts if you don't follow this guide!
DISCLAIMER: I'm not responsible for bricked devices and data loss from power surges, hardware damage, or changes to the linked software. Always check the native manuals for all the tools listed here!
What You Will Lose:
All at&t branding
at&t address book (see below how to save contacts)
at&t emergency numbers dialer
Stable LTE connection (you'll see the H+ icon often in places with weak signal)
NFC icon
What You Will Gain:
Clean ROM with all stock Sony apps
All the new JB 4.3 features
Sony's new camera app with plugins
Significant improvement in battery life if your phone barely survives a day
What You Will Keep:
All of your contacts and data
James Bond themes
Root access
Recovery
Required Downloads:
1. Flashtool (got questions about it? - ask them here) - requires installation
2. @[NUT]'s dual XZDualRecovery. I'm linking to v2.7.94 BETA installer. If you wish to check for a more recent version, go to his download page and do a page search (CTRL+F) for XT-lockeddualrecovery[version-goes-here].installer.zip. (got questions about it? - ask them here) - unzip to a location you'll remember (say, C:\xperia-upgrade\recovery\)
3. @amarullz's AROMA File Manager - current version can be found at the bottom of the 2nd post - don't do anything to the zip
4. @DaRk-L0rD's Ultimate PureXT ROM and all patches and/or add-ons from the 2nd post you'd like (got questions about it? - ask them here) - don't do anything to the zip, save it to a location you'll remember (say, C:\xperia-upgrade\ROM\)
4.1 There might be additional files needed for the ROM, such as SuperSU update. They will be mentioned in the post. Download them to the same location as the ROM (e.g., C:\xperia-upgrade\ROM\).
5. at&t baseband FTF (attached) - unzip it to the default Flashtool firmware directory (C:\flashtool\firmwares\)
The Guide (assuming your phone is running at&t's 4.1.2 (9.1.F.1.120):
1. Backup any contacts saved in at&t address book or make sure there are none.
1.1 Open the stock Contacts app.
1.2 Tap the filter icon on the left.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
1.3 Make sure that the two checkboxes are blank.
1.4 Go through every single connected account EXCEPT for AT&T Address Book and uncheck them (there might be a few), then tap OK.
1.5 Tap the menu button, then Back up contacts.
1.6 Select SD card.
1.7 You don't need to remember the location of the vcf file - the system will recognize it on its own.
2. If USB debugging isn't enabled yet, you need to do it.
2.1 Go to (System) Settings -> Developer options and flip the switch in the top-right corner of the screen.
2.2 Look a bit down (toward the middle of the screen) and check USB debugging.
3. Connect your phone to the computer and let the computer recognize it.
4. Copy AROMA Filemanager to the SD card
4.1 Go to the location on your computer where you saved aromafm.zip and copy the file (select, then CTRL+C).
4.2 Navigate to your SD card (not internal storage) and create a folder called clockworkmod.
4.3 Open the new folder and create another folder inside it called aromafm.
4.4 Open that folder and paste the zip (CTRL+V).
5. Copy the ROM and all of the files required for it to the SD card.
5.1 Go to the location on your computer where you saved the ROM zip with all other required files and copy the files (select, then CTRL+C).
5.2 Navigate to your SD card (not internal storage) and create a folder called 00-install (such a name keeps it on the top of the content list in Linux).
5.4 Open that folder and paste the zips (CTRL+V).6. Install the dual recovery.
6.1 Go to the location on your computer where you extracted dual recovery (e.g., C:\xperia-upgrade\recovery\).
6.2 Double-click install.bat.
6.3 Press 3 on your keyboard for the option 3. Installation on unrooted ROM.
6.4 Follow the instructions on your computer's screen.
6.5 When you will try to reboot the phone back into Android, the recovery will prompt you to root the OS. Do that.
7. Backup old system and install the new ROM (YOU MUST DO THIS!!!) - if you skip this and have issues, later, I'm not responsible
7.1 Initiate the reboot sequence by holding POWER + VOLUME UP for a few seconds.
7.2 Once you see SONY logo, start pressing VOLUME UP to enter clockworkmod recovery.
7.3 Connect the phone to a power outlet.
7.4 Tap Backup and Restore
7.5 Tap Backup to /storage/sdcard1 and confirm. The process can take up to 10-15 minutes depending on the amount of data in your internal storage.
7.6 When backup is complete, tap the Back button (2nd from the right) to go to the main menu.
7.7 Tap Wipe Cache Partition (4th from the top) and confirm the operation.
7.8 Tap Back button (2nd from the right) to go to the main menu.
7.9 Tap Advanced (3rd from the bottom), then Wipe Dalvik Cache (1st from the top) and confirm the operation.
7.10 Tap Back button to go to the main menu.
7.11 Tap Install Zip (2nd from the top), then Choose zip from /storage/sdcard1, then select the folder 00-install, then the ROM file, and confirm the operation. If you receive Status 7 error message, leave the phone as is, scroll down to the troubleshooting section to restore the backup and fix it.
7.12 Repeat step 7.11 for all the files that need to be installed.
7.13 When you are done, select Reboot System Now in the main menu. It may take good 20 minutes for the system to perform all operations needed for the first start.
8. If the phone doesn't pick up LTE signal, you need to re-flash the at&t baseband.
8.1 Turn off the phone.
8.2 Start Flashtool from your Start menu.
8.3 Click the flash icon, select Flashmode (default), and click OK.
8.4 In the list of firmware select the one you've downloaded (if this is your first time flashing, it'll be the only one for LT30) and make sure that No final verification is checked. Then click Flash.
8.5 When prompted, hold the VOLUME DOWN button, and connect the phone to the computer. The operation will take about 10-15 seconds. DISREGARD THE INSTRUCTIONS IN THE ANIMATION. Xperia T/TL doesn't have a hardware Back button.
8.6 Boot the phone.
8.7 Sometimes the phone will still lose LTE signal and show H+. You can reconnect to LTE by putting the phone into Airplane mode for a couple of seconds and then turning the Airplane mode off. If that doesn't help, open dialer, type *#*#4636#*#* to get into Testing service menu. There, you need to tap Phone information and scroll all the way to the bottom where you'll see a selector with the label Set preferred network type. Pick the flavor of LTE and downgrade that you'd like and watch the connection be re-established. Unfortunately, through experimentation, I've discovered that every ROM keeps its regional baseband regardless of flashing method (even overwriting with NAM bands will only enable LTE reception but the baseband property stays the same).
9. Battery fix if your battery dies within 9-10 hours of use.
Apparently, in some areas at&t doesn't support a network feature called fast dormancy (it allows for somewhat faster reconnection to the data network after idling). Some apps aren't written properly and keep on pinging Sony's FD service to connect, which results in thousands of wakeup alarms and the phone never entering deep sleep. You can notice this if Android OS is your top battery hog in standard battery usage stats (com.sonyericsson.android.wakeup is the service name). Before applying this fix, check your battery drain using BetterBatteryStats or Wakelock Detector. If you see what I've described, this will help you increase your battery life by at least a couple of hours (for me, it almost doubled).
There's one downside though: the last 10-15% of battery charging take much longer (my battery now charges over 3+ hours).
Huge thanks to @mirhl for writing the original guide.
1. Install some root-capable file browser (I prefer ES File Explorer for being free).
2. Grant it root access (in ESFE, tap the top-left corner to open the navigation sidebar, scroll down to Tools, tap it to expand, scroll down to Root Explorer, and tap the switch).
3. Mount /system as R/W (in ESFE, get to Root Explorer as above, but instead of the switch tap the tile itself, then tap Mount R/W, and move the radio button next to /system into R/W column).
4. Navigate and open /etc/fast-dormancy/fd_custm_conf.txt (ESFE has a built-in text editor but editing needs to be enabled through the top-right menu.
5. In the file, you'll see two lines ending with MCC and MNC and a zero next to each. Change the zeros to 310 (MCC) and 410 (MNC), save the file, and reboot the phone. That should take care of it.
IF SOMETHING WENT WRONG
1. There shouldn't be any issues until you complete 7.6 (phone backup).
2. You better have followed this guide and created a complete backup of the working setup.
Bricked phones (something went wrong and you turned off your phone and now it doesn't boot)
1. Download a 4.1.2 FTF file from this master list to C:\flashtool\firmwares\.
2. Remove the SD card from the phone just in case.
3. Follow the instructions in the master list on how to flash the firmware.
4. Insert the SD card back into the phone.
5. Repeat steps 2, 3, and 6 of the guide above to install recovery.
6. Boot into clockworkmod (7.3 above), navigate to Backup and Restore, then Restore from /storage/sdcard1 and select the appropriate backup. This will get you up to step 7.6 and you can try the guide again.
Status 7 error message when flashing a ROM
After some experimentation, I noticed that some rooting methods are the culprit. You need to unroot your phone (don't worry recovery installer will work either way and will reroot it safely). Just download this Xperia rooting script, connect your phone with Debugging access enabled, run the script, and select the appropriate option (unroot). When it's done and the phone reboots, reinstall recovery (it will prompt you at one point to root the device), and continue to 7.7.
Huge thanks to all the devs who have built the tools!
Changelog
Code:
v2 - Apr 1, 2014 - Added extensive troubleshooting & battery fix; formatting changes
v1 - Mar 26, 2014 - Original publish
I've linked your guide to my list: http://forum.xda-developers.com/showthread.php?p=50323041#post50323041
I think it will make many AT&T users happy
Nice one
I didn't do that at all due using Ubuntu, I download flash tool, I used the bell firmware didn't exclude baseband (they use the same bands plus h+42 for T-Mobile in case this phone has it). Rooted it and added a recovery, flashed a 4.3 ROM by our doomlord and flashed superuser update thus 4.3 no bloat and got LTE working on T-Mobile
Sent from Sauwny the TL
Durteedee said:
I didn't do that at all due using Ubuntu, I download flash tool, I used the bell firmware didn't exclude baseband (they use the same bands plus h+42 for T-Mobile in case this phone has it). Rooted it and added a recovery, flashed a 4.3 ROM by our doomlord and flashed superuser update thus 4.3 no bloat and got LTE working on T-Mobile
Sent from Sauwny the TL
Click to expand...
Click to collapse
Which rooting script did you use? I couldn't find a working one so I had to wait for a good flashable release. How's the battery life on Bell firmware?
bsined said:
Which rooting script did you use? I couldn't find a working one so I had to wait for a good flashable release. How's the battery life on Bell firmware?
Click to expand...
Click to collapse
I used the one that came with the flash tool 4.1.2 only, battery life wouldn't know it was only on the bell firmware for about 30 mins at most before flashing doomlords 4.3 ROM
Sent from Sauwny the TL
Durteedee said:
I used the one that came with the flash tool 4.1.2 only, battery life wouldn't know it was only on the bell firmware for about 30 mins at most before flashing doomlords 4.3 ROM
Sent from Sauwny the TL
Click to expand...
Click to collapse
That's strange. I've tried every single root method in Flashtool and none of them worked on 4.3.
Link to doomlord's ROM (I found only his 9.2.A.0.278 release)?
bsined said:
That's strange. I've tried every single root method in Flashtool and none of them worked on 4.3.
Link to doomlord's ROM (I found only his 9.2.A.0.278 release)?
Click to expand...
Click to collapse
Because I rooted bell 4.1.2, 4.3 can't be rooted yet without an unlocked bootloader
Sent from Sauwny the TL
Thanks for this. Its been a long time since I've upgraded, came from XperimenT 3.5, and I wasn't sure where to start reading first. I'm curious though. Do you know if the cpu control is working for us locked bootloaders?
Also, do you know how to get rid of this "close all x" button at the bottom of the recent apps list? It covers the bottom ago in the list. Plus I like the one in the top corner thats enabled by gravity box. I'm not sure how it even turned on. I don't remember it being there at first. Even disabling all the xposed modules doesn't remove it.
- Xperia TL, Ultimate PureXT v2 ~ via XDA App
redincali said:
Thanks for this. Its been a long time since I've upgraded, came from XperimenT 3.5, and I wasn't sure where to start reading first. I'm curious though. Do you know if the cpu control is working for us locked bootloaders?
Also, do you know how to get rid of this "close all x" button at the bottom of the recent apps list? It covers the bottom ago in the list. Plus I like the one in the top corner thats enabled by gravity box. I'm not sure how it even turned on. I don't remember it being there at first. Even disabling all the xposed modules doesn't remove it.
- Xperia TL, Ultimate PureXT v2 ~ via XDA App
Click to expand...
Click to collapse
- Judging by the CPU states reported in BBS, governor changes are working. Though I'm also using CPU Tuner for automatic downthrottling.
- "Close all X" is a part of the ported Z2 UI. There's a request to remove it in the ROM thread.
How did you root? is it the dual recovery that does that? or another method. Just asking as I understand that rooting the AT&T TL is extremely hard.
Happy-J said:
How did you root? is it the dual recovery that does that? or another method. Just asking as I understand that rooting the AT&T TL is extremely hard.
Click to expand...
Click to collapse
Dual recovery will prompt you to root the phone on reboot during installation and the new ROM retains root access. However, rooting 4.1.2 on its own was very easy, too - the scripts provided on the forums work flawlessly.
Thanks for the quick reply and answer. One last question for you, can I use flashtool to root 4.1.2?
Happy-J said:
Thanks for the quick reply and answer. One last question for you, can I use flashtool to root 4.1.2?
Click to expand...
Click to collapse
Yes its what I used for my att TL
Sent from Sauwny the TL
Thank you for your help, I think I'll be installing this very soon!
Happy-J said:
Thanks for the quick reply and answer. One last question for you, can I use flashtool to root 4.1.2?
Click to expand...
Click to collapse
FYI: the install might fail if the phone is rooted by a method other than the one included with recovery. If that's the case, see the bottom of the guide for troubleshooting - just don't forget to backup your existing setup before trying to flash.
bsined said:
FYI: the install might fail if the phone is rooted by a method other than the one included with recovery. If that's the case, see the bottom of the guide for troubleshooting - just don't forget to backup your existing setup before trying to flash.
Click to expand...
Click to collapse
Ok, I will keep that in mind when I start the installation, and just use the recovery's root. Thanks for the tip.
I can't seem to get into recovery. I have tried pressing volume up at said time, and long pressing, but no dice. Can anyone offer assistance?
Happy-J said:
I can't seem to get into recovery. I have tried pressing volume up at said time, and long pressing, but no dice. Can anyone offer assistance?
Click to expand...
Click to collapse
Did the phone boot into recovery during installation? If not, you need to reinstall it. If yes, there's now a new app called NDR Utilities - use it to boot into PhillZ Recovery. Otherwise, please ask the recovery script author.
No, the phone did not boot recovery any of the times I reinstalled it, which was about 5. I am going to try flashing back to stock and try it again. Thanks for the helping hand again, very much appreciated.
---------- Post added at 01:07 PM ---------- Previous post was at 12:59 PM ----------
OK, a clean flash of the stock firmware did the trick. Thanks again for the help.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
About this Q&A thread for CyanogenMod 14.1
Use this area to ask anything you want related to CM-14.1,
but try not to spam everyone, always search for an answer before.
CyanogenMod 14.1 for Sony Xperia Blue
Xperia T (Mint) : http://forum.xda-developers.com/xperia-t-v/orig-development/rom-t3461744
Xperia TX (Hayabusa) : http://forum.xda-developers.com/xperia-t-v/orig-development/rom-t3461745
Xperia V (Tsubasa) : http://forum.xda-developers.com/xperia-t-v/v-development/rom-t3461746
General Questions & Answers
Is root access included into CM ?
Yes. Go into Settings, About Phone. Tap "Build number" 7 times.
Go back, open Developer options. Change "Root access" option.
Do not use SuperSU unless you are sure, creates booting issues.
Read more about it : Here.
Is the ROM suited for daily usage ? Google Apps compatible too ?
Yes completely. Nightlies and OpenGApps recommended.
Can I flash CyanogenMod NIGHTLY and UNOFFICIAL without wipes ?
Yes you should be able to.
Phone and telephony apps crash after updates ?
Due to the databases upgrades to support CM-13.0 -> CM-14.1 migrations,
the telephony databases may require to be deleted and rebuilt during the CM-14.1 bringup.
Backup your relevant phone data (SMS, Calls, ...), delete the following paths and reboot
Code:
/data/data/com.android.providers.telephony
/data/user_de/0/com.android.providers.telephony
/data/misc/profiles/cur/0/com.android.providers.telephony
/data/misc/profiles/ref/com.android.providers.telephony
Is the device encryption supported ?
State unknown. If you're coming from an older ROM
please read the details here : a07afb9660a86f702066003b8e81ab63789d1660
When USB connected to a computer, I can't access the storage ?
The phone is in charge-only mode by default on Nougat,
due to a stronger security logic regarding unauthorised data access.
Swipe down the notifications and change the USB mode.
I can't access the ROM's recovery with Volume-
You can either flash the boot.img from the newer Releases with "fastboot flash boot boot.img" or FlashTool,
or follow the instructions of the TWRP Recovery installation to update from TWRP.
Due to an unknown issue in data, the partition still looks like a 2GB
Your device needs to be migrated to Unified UserData.
Please read the section about "Unification of the user partitions into UserData".
If already done, although very unlikely, it may be possible that your data had an error
that could not be fixed automatically by the time you did the UserData Unification.
Export the resize_userdata.zip from the unify_userdata zip (install / unify_userdata),
and flash it from your recovery. If it works, problem solved.
Against advices, I upgraded without GApps and now it crashes. Any way without factory reset ?
Yes there is, but nothing assures you'll manage to do it fully & preserve all your data...
Once booted, keep saying Ok to all "Unfortunately, ... has stopped",
pull-down the notifications panel, press the Settings icon,
go in Apps, menu, Show System, scroll to Setup Wizard (green Android logo),
Permissions, and activate Contacts + Telephone.
Later, some Play Store apps may need reinstalling.
If not ok, try this : CM Wiki
If still not, then I advise a clean factory-reset reinstallation...
The AOSP Keyboard does not support swipe gestures ?
Unfortunately the sources for swipe gestures are not available
and Google still requires their prebuilt library to be there for AOSP Keyboard.
Download the following libjni_latinimegoogle.so API 23 from OpenGApps
and push it to /system/lib/libjni_latinimegoogle.so.
Xperia TX bricked
Philz recovery is completely outdated and not meant to be used on recent ROMs.
Use "fastboot" to flash the last version of TWRP into the boot partition, in order to get TWRP easily.
http://forum.xda-developers.com/xper...overy-t3319588
From there, flash TWRP to the FOTA as explained in the thread (2 ways possible).
Click to expand...
Click to collapse
Hi, it is me again. I have tried to read some threads in xda and googles. So now I already have a fastboot in my pc, downloaded from http://forum.xda-developers.com/showthread.php?p=48915118#post48915118.
But then it seems like the fastboot does not recognized my device as when i tried to reboot into bootloader it shows " error: device '<null>' not found" . Is it mean that the fastboot does not recognize my device or something else has went wrong? Help please....
**my device is turned on when i connected it to laptop using usb cable. But in black screen after sony logo appears and the led is red.**
xperia txxx said:
Hi, it is me again. I have tried to read some threads in xda and googles. So now I already have a fastboot in my pc, downloaded from http://forum.xda-developers.com/showthread.php?p=48915118#post48915118.
But then it seems like the fastboot does not recognized my device as when i tried to reboot into bootloader it shows " error: device '<null>' not found" . Is it mean that the fastboot does not recognize my device or something else has went wrong? Help please....
Click to expand...
Click to collapse
Good start.
Look around for how to properly fix the fastboot bootloader drivers on Windows,
inside the Drivers manager (devmgmt.msc), to allow the fastboot device to be seen.
Adrian DC said:
Good start.
Look around for how to properly fix the fastboot bootloader drivers on Windows,
inside the Drivers manager (devmgmt.msc), to allow the fastboot device to be seen.
Click to expand...
Click to collapse
Basically now my issue is that whenever i connected my device to laptop using USB cable, it will start up with red LED light, sony logo and go black screen and hang there. Flashtool shows "device disconnected" and "device not found" for fastboot. My device can't get into fastboot as well. I connected it while holding the volume up button, it is on with blue LED light, but after half minutes it reboot and the LED turns red, and the cycle keeps going on. After a few times, the cycle stop and the device is off, with green LED light. I really have no ideas on how to do that. Help please..
iSouL_O#" said:
hey, how can i root it ?
sometimes if i try to flash gapps it stucks on bootscreen untill i flash the rom again
Click to expand...
Click to collapse
Hey,
SuperSU is not recommended, just use the included root.
Adrian DC said:
Is root access included into CM ?
Yes. Go into Settings, About Phone. Tap "Build number" 7 times.
Go back, open Developer options. Change "Root access" option.
Do not use SuperSU unless you are sure, creates booting issues.
Read more about it : Here.
Click to expand...
Click to collapse
Theme
CyanogenMod 14 works great for me, but I can't see any theme engine, where I can find it?
Tom.Fucik said:
CyanogenMod 14 works great for me, but I can't see any theme engine, where I can find it?
Click to expand...
Click to collapse
yeah where is theme engine is this support a subtratum theme engine?
for now everything ok, but u need to fix some bugs in status bar like battery icon and it's better to change on it to make the battery icon changeble like old android versions, the twrp needs some edits cuz it tooks from me 4 hour to install the rom without bootloop.
there is another problem in twrp i tried to downgrade my phone to neo's CM but there is a storage issuse + when u install the rom from internal memory u can't install anything after it untill u restart again and copy the files again ..
u can change the trebuchet launcher to Xperia home launcher i think it's better and easy to use, and there is the night mode i using it always is missing
radio works great, camera works great, messaging works great. just fix those bugs if u need any screenshots or logs just tell me
good luck and thanks for this rom
hey i think you have another bug or something like that, when you put music files in internal memory i can't find music in music app or sony music app i'll try again maybe i can solve it
After Overcoming some issues I have successfully installed this ROM.
Issues that i have to overcome is this.
I came directly from CM11, So i have to go through Data unification process,
which was not 100% successful.
After unification It shows only 1.96GB of user data,
After some hair pulling out moments I found a way
Go to the Wipe --> select Data Partition --> Resize File system --> voila,
Now you have 12.8GB of user Partition
Issues I have in this ROM as follows.
Can't change the battery Icon.
Long Press Back Button Kill Foreground app was missing. (I'm so addicted to this feature)
cLock Widget Weather function not working. (It's a cLock app fault. Not working in CM11 Also),
I suggest using Chronus (Very Similar app)
Album Art missing bug. (only some of the mp3 files, I should analyze those mp3s)
Always Using more than 60% of memory. :crying::crying:
Can't Play Temple Run Moded version
Dn.Thanujaya91 said:
After Overcoming some issues I have successfully installed this ROM.
Issues that i have to overcome is this.
I came directly from CM11, So i have to go through Data unification process,
which was not 100% successful.
After unification It shows only 1.96GB of user data,
After some hair pulling out moments I found a way
Go to the Wipe --> select Data Partition --> Resize File system --> voila,
Now you have 12.8GB of user Partition
Issues I have in this ROM as follows.
Can't change the battery Icon.
Long Press Back Button Kill Foreground app was missing. (I'm so addicted to this feature)
cLock Widget Weather function not working. (It's a cLock app fault. Not working in CM11 Also),
I suggest using Chronus (Very Similar app)
Album Art missing bug. (only some of the mp3 files, I should analyze those mp3s)
Always Using more than 60% of memory. :crying::crying:
Can't Play Temple Run Moded version
Click to expand...
Click to collapse
hey did you try to record a video by camera app or instagram app ? and did you try to use music app ?
i am working from 2AM to resize the data partion to give more space to legacy storage ..
Tahax09 said:
hey did you try to record a video by camera app or instagram app ? and did you try to use music app ?
i am working from 2AM to resize the data partion to give more space to legacy storage ..
Click to expand...
Click to collapse
Video Recording Not working. OP Said it. So No hard feelings.
Default Music app working fine, apart from that album art n artist details missing bug.
Do you try My method?
Dn.Thanujaya91 said:
Video Recording Not working. OP Said it. So No hard feelings.
Default Music app working fine, apart from that album art n artist details missing bug.
Do you try My method?
Click to expand...
Click to collapse
Ya i tried everything, like i told you i'll try to edit on data storage to resize it becouse it takes 5GB only.
so i don't know from where this bug untill Adrian DC reply to me to know what i do .
+ i don't know why i can't listen to music from music app it shows nothing for me maybe becouse of storage but i can play them from Solid Explorer ..
Tahax09 said:
Ya i tried everything, like i told you i'll try to edit on data storage to resize it becouse it takes 5GB only.
so i don't know from where this bug untill Adrian DC reply to me to know what i do .
+ i don't know why i can't listen to music from music app it shows nothing for me maybe becouse of storage but i can play them from Solid Explorer ..
Click to expand...
Click to collapse
Don't know what's the wrong..
I think its caused by Data Unification Process
Try this steps if you didn't try till now.
Get in to TWRP Recovery.(Version 3.0.2.0)
Wipe Everything (system, cache, data, internal storage, legacy sdcard)
Put the Rom zip file in micro sd card & flash the rom from it
Hopefully this will create Data Unification properly.
Check the Data partition size from TWRP.
if it is not showing entire 12.8GB, executes the resize file system.
Now you should have the Entire User Data Partition.
These steps Works for me, If not don't blame me. :silly::silly:
Dn.Thanujaya91 said:
Don't know what's the wrong..
I think its caused by Data Unification Process
Try this steps if you didn't try till now.
Get in to TWRP Recovery.(Version 3.0.2.0)
Wipe Everything (system, cache, data, internal storage, legacy sdcard)
Put the Rom zip file in micro sd card & flash the rom from it
Hopefully this will create Data Unification properly.
Check the Data partition size from TWRP.
if it is not showing entire 12.8GB, executes the resize file system.
Now you should have the Entire User Data Partition.
These steps Works for me, If not don't blame me. :silly::silly:
Click to expand...
Click to collapse
i am tired of this everytime i try to wipe data, legacy sdcard i face this
this is my problem if i can solve it, i can work on my phone ..
after 11 hours of work i realized that the problem is from resize_userdata or i guess from it
i tried to resize the storage from ADB, then i flashed stock rom then CM 12 by Neo now i can use the legacy storage + recording videos, after that i tried to install CM14 but it says error ..
is there anyway to flash the rom without the resize_userdata ?
Tahax09 said:
i am tired of this everytime i try to wipe data, legacy sdcard i face this
this is my problem if i can solve it, i can work on my phone ..
Click to expand...
Click to collapse
Tahax09 said:
after 11 hours of work i realized that the problem is from resize_userdata or i guess from it
i tried to resize the storage from ADB, then i flashed stock rom then CM 12 by Neo now i can use the legacy storage + recording videos, after that i tried to install CM14 but it says error ..
is there anyway to flash the rom without the resize_userdata ?
Click to expand...
Click to collapse
I think there was no space assigned to Legacy SDcard portion after the data unification process
So you have to resize the Data Partition to allocate all the usable space.
Let's wait for Adrian DC Reply.
I think, that the system take too much battery, even if the display is off. Behind the night, it take about 30% for me, what about the others?
Maybe this is off-topic, but is there any option to donate the developer?
Tom.Fucik said:
I think, that the system take too much battery, even if the display is off. Behind the night, it take about 30% for me, what about the others?
Maybe this is off-topic, but is there any option to donate the developer?
Click to expand...
Click to collapse
I´m on the latest Build (20161024), and for me it is all fine, and i didn't noticed any weird behave before latest Build.
And yes, you can find Adrian DC's Donation page at his Profile.
I flashed last buid (20161024) and find, that I had NFC turned ON, so I turn it OFF and now it looks better with the battery life and I have to say, with the last build, starting apps is much quicker, thanks
btw: For the next build I suggest to get the NFC shortcut to the quick panel in status bar.