Database Users

CyanogenMod-7.1 Released !!

It’s been far too long since our last official release, but I’m happy to present CyanogenMod-7.1! I apologize for the long delay, and I hope to speed up our release process in the future. We originally planned to release this last weekend at the Big Android BBQ but some issues with our automated build system held it back.
You’ll find many new features (read the CHANGELOG) and support for building on 68 devices! Upgrading from any previous CM-7 release or nightly build should be smooth and no wipe should be required.
New devices since 7.0 included in today’s release are:
HTC Desire S
HTC Incredible S
HTC Incredible 2
LG Optimus 2X and T-Mobile G2x
Motorola Backflip (Motus)
Motorola Cliq / Cliq XT
Motorola Defy
Motorola Droid 2
Motorola Droid X
Samsung Captivate
Samsung Fascinate
Samsung Mesmerize
Samsung Showcase
Samsung Vibrant
Samsung Galaxy S
Samsung Galaxy S2 (multiple carriers)
Sony Ericsson Xperia X8
Sony Ericsson Xperia Mini
Sony Ericsson Xperia Mini Pro
Sony Ericsson Xperia Neo
Sony Ericsson Xperia Play
Sony Ericsson Xperia Ray
Sony Ericsson Xperia Arc
ZTE V9
There are many devices still in beta status (Pyramid, Doubleshot, Shooter, HP Touchpad, Optimus 3D, several more) that we will be promoting to release or release-candidates in the next few weeks when the code is merged to our main branch.
The preferred method of installation is via ROM Manager, but you can directly download the latest release from our mirror network. Head over to our forums to discuss the release or get help. Installation instructions and other information can be found on our wiki.
As we continue to grow and improve CM, we are starting to see support from the industry grow- something that was unheard of previously. Recently, Sony Ericsson assisted our developers by providing over 20 devices, technical assistance, and compatible hardware drivers. CM-7.1 now has support for all recent SEMC devices thanks to this effort. Various other vendors have reached out to us, but we understand that it is still somewhat of a difficult situation. We will soon be providing a porting guide and some information on how vendors can get involved with the project and how/why it will benefit them.
Thanks again for the support, and for making CyanogenMod the #1 community Android distribution. We’ll be following up with a few minor releases and soon it will be time to start work on CM9!
Click to expand...
Click to collapse
courtesy : CyanogenMod.com
For Full Guide On CM7:
http://forum.cyanogenmod.com/topic/32755-cyanogenmod-7-for-the-xperia-arc-v7101-11-oct-2011/

Guys is this the guide to actually make this happen?
http://wiki.cyanogenmod.com/wiki/Sony_Ericsson_Xperia_Arc:_Full_Update_Guide

Bushmaster78FS said:
Guys is this the guide to actually make this happen?
http://wiki.cyanogenmod.com/wiki/Sony_Ericsson_Xperia_Arc:_Full_Update_Guide
Click to expand...
Click to collapse
Yup....this is the official guide to install cyanogenmod for arc...i will install it today and see what happen....is this a 2.3.4 or 2.3.3 version....can it do a overclocking...?

I think it said 2.3.7 ...
http://www.androidcentral.com/cyanogenmod-71-released-brings-android-237-pure-form
I didn't unlock my bootloader since my purchase a few months ago, so I am behind times. I am kind of concerned about the whole warranty issue... If you guys give me good performance and feature feedback, I might just get on the CM7 bandwagon...

Why in the phone list
Code:
http://wiki.cyanogenmod.com/wiki/Latest_Version#Sony_Ericsson_Xperia_Arc
there is no Xperia Arc? And they say Arc fully supported?
Which to download there then?

a guide with no rom. Yes thats so helpful.

Link to ROM
http://forum.cyanogenmod.com/topic/32755-cyanogenmod-7-for-the-xperia-arc-v7101-11-oct-2011/
Edit:
I just installed this ROM, camera is working.

There... i updated my theme to "XDA 2010" just to be able to thank you!
Anyway... will only go CM7 when I get bored of the stock but doomkerneled UI.

Tempting, very tempting.
The two things i'd really miss from the stock ROM are SE's home launcher (i know, i'm weird) and the panorama camera app. Anyone know how likely these are to work on top of CM?

SE Home Launcher is working on CM7, you can find modified versions on xda, I don't know about camera but I doubt it's working.

I installed this rom and did flash a clean 368 before. I am unable to add an APN for att and cannot use mobile data. It looks like I am not the only one. I have a LT15a, generic global was flashed though so it looks like a LT15i.
Sent from my LT15i using XDA App

joecool1029 said:
I installed this rom and did flash a clean 368 before. I am unable to add an APN for att and cannot use mobile data. It looks like I am not the only one. I have a LT15a, generic global was flashed though so it looks like a LT15i.
Sent from my LT15i using XDA App
Click to expand...
Click to collapse
For any issues, u should check out ORIGINAL cm7 thread by fxp in development section.

I would except it won't let me post there
Sent from my LT15i using XDA App

i really want to unlock bootloader for my ARC and install CM7 but i'm afraid about 3 things one is Bravia Engine which i will miss the crispy look on my pictures and videos and secondly i'm afraid that i won't find alternative for Track ID and thirdly facebook integration =__= which my calendar and address book will be missing...

joecool1029 said:
I would except it won't let me post there
Sent from my LT15i using XDA App
Click to expand...
Click to collapse
All the issues are listed and solved in the 139 pages of thread, u just need to find your issue.
PS: u just need one more post and u are good to go to post in dev section

mr.alawi said:
i really want to unlock bootloader for my ARC and install CM7 but i'm afraid about 3 things one is Bravia Engine which i will miss the crispy look on my pictures and videos and secondly i'm afraid that i won't find alternative for Track ID and thirdly facebook integration =__= which my calendar and address book will be missing...
Click to expand...
Click to collapse
have the same troubles.

mr.alawi said:
i really want to unlock bootloader for my ARC and install CM7 but i'm afraid about 3 things one is Bravia Engine which i will miss the crispy look on my pictures and videos and secondly i'm afraid that i won't find alternative for Track ID and thirdly facebook integration =__= which my calendar and address book will be missing...
Click to expand...
Click to collapse
u can always revert back to stock.

Try to flash older version or a 2.3.4 stock ROM with DoomKernel until the problem of APN is solved.

I've managed to flash CM7.1 with out having any issue... (seems there's battery drain... but not confirm yet)
The way I did from unlocking bootloader till flash CM7.1:
- Flash using flash tool to LT15i 4.0.A.2.368 Generic Global
- Unlock Bootloader
- Extract the boot.img from the CyanogenMod update.zip and copy it to the same folder as fastboot (the /tools folder within the Android SDK folder).
- Disconnect the Sony Ericsson Xperia Arc from the computer and power it off.
- Download CM7.1
- Unzip it and copy all the zip file frm the 7z you've downloaded into your microSD
- Press & hold the Menu button while connecting the Sony Ericsson Xperia Arc to the computer.
- On the computer, open terminal and run the following command:
fastboot -i 0xfce flash boot boot.img
fastboot -i 0xfce reboot
- Once the device boots into the ClockworkMod Recovery, use the side Volume Rocker to move around, & the Power button to select.
- Select the option to Wipe data/factory reset.
- Then select the option to Wipe cache partition.
- Select Install zip from sdcard.
- Select Choose zip from sdcard.
- Install the CM7.
- Install Google Apps.
- reboot.
NOTE: IF YOUR CONTACT IS IN SYNCML/SONY ERICSSON SYNC, PLEASE COPY YOUR CONTACT TO GOOGLE BY PERFORMING BELOW STEP:
- Go to Contact
- Setting > Backup Contact > choose memory
- Setting > Import Contact > choose gmail account
- Once you have successfully installed CM7.1, it will autosync the contact from gmail contact to your phone one you have setup the google account.

thank for your info

[Fastboot][script][Windows][Linux]Fastboot Flasher-V3.2 2012/04/13

Includes full fastboot based wipe menus as well as installing OTA packages and PKIMG.zip or RUU.zip PGIMG.zip packages from HTC
Can also Install .img files to most partitions if bootloader is unlocked/s-off
Can get ADB Shell Temp Root VIA ZergRush (most Android 2.2 and 2.3 devices)
Can attempt to push root on temp rooted devices with s-off (device list can be found in post 3)
Can get S-Off On some devices with G-Free (must be temp rooted or rooted)
Can HTCDev Unlock Devices that support it.
Can OEM Unlock and Lock devices (Nexus Devices and devices that have already been HTCDev Unlocked)
Windows Version / General Instructions
slayerXcore said:
Extract it somewhere like your desktop, though anywhere will work.
when i say extract it i mean use extract all so you get my file structure do not move these files or it will break
Run / double click FastbootFlasher.bat
The script displays the readme at startup. close it and continue.
Select what function you want to do and press [ENTER]
Please be careful as to what file you drag and drop when it prompts you
One final note do not give it a file for another device or a non .img file it will flash it anyway no matter what file you drag and drop once you press enter it flashes what ever was dragged onto the script. Also do not drag a radio img when it asks for recovery or in revers, bad things will happen Wile they are fixable by repeating the process I dont want anyone to mess up their deice making such a simple mistake.
Click to expand...
Click to collapse
Download the small ~2.90MB Fastboot Flasher-V3.2-2012.04.13.02.43.17.zip
Download link: http://j.mp/IkudiO Dev-Host
MD5: 2f03dbea1e6f678e3e56cb7f1b3e5b3f
ScreenShots of 3.0
{
"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"
}
Youtube video (slightly outdated) will be making a new video once im finished tweaking more
I hope this tool helps those who aren't familiar with fastboot or helps those who want a faster way of doing things.
Consider this a small holiday gift
share it with anyone who has a rooted android device
yes i know other people have made .exe files with fancy interfaces but they are restricted to some devices and aren't as simplistic or fast.
i made this as a simple batch file so that anyone who wants to open it in a text editor can see exactly what it does and doesn't do as people don't trust executable files that can go downloading stuff or messing up your computer.
Click to expand...
Click to collapse

If anyone would like to port it to linux or mac let me know
also if your wondering why i left out bootloaders its because of the different manufacturers methods of partitioning hboot/bootloader ect......
hope this is useful in some way
Code:
Changelog:
2012/04/13
Version 3.2 Released
Removed Go Launcher on de-sense
Added Launcher Pro on de-sense
Added Recovery Download section featuring Clockwork Mod and Team Win Recovies
Added Nexus Factory Images Download Section
Updated binaries to newest versions
2012/01/16
Version 3.1 Released
Cleaned up a few things
Added De-Sense and Re-sense Options
2012/01/08
First Public Linux Port
2012/01/06
Version 3.0 Released
Added Zergrush exploit (Thanks Revolutionary Team)
Added Gfree to gain S-Off on some devices
Added Push Busybox and SU and Superuser.apk script to perm root after zergrush works hopefully thanks to ChainsDD for the binary and apk (latest version)
Added HTCDev Unlock
Added OEM Unlock and Lock
Slight UI re work
Added ADB Logcat
Added ADB Shell
Added Driver Downloads
Added Update Check (must be done manually opens the XDA post)
Other stuff i don't remember
2012/01/03
Version 2.5 released
Re-Themed
Optimized
added update check option (opens XDA thread)
improved menus in case of invalid key press
more i cant remember
2012/01/02:
Version 2.4 Released
now works on systems that refuse to use setlocal so no one should be having issues
Version 2.3 Released
Wipe Data Improvements
2012/01/01:
Version 2.2 Released
Now includes full fastboot based wipe menus as well as installing OTA packages and PKIMG.zip or RUU.zip packages from HTC
2011/12/31:
Fastboot Flasher-V2-20111231-191438.zip initial release
Flashes Recovery and Radio
post mirrored on rootzwiki
Old Downloads
Code:
[URL="http://j.mp/zQ62f6"]V3.1[/url]
[URL="http://j.mp/wYG8md"]V3.0[/url]
[URL="http://www.sugarsync.com/pf/D315775_7173530_001884"]V2.5[/URL]
[URL="http://www.sugarsync.com/pf/D315775_7173530_000528"]V2.4[/URL]

Device List
Root Method Confirmed to be working on the following devices:
(Not confirmed by myself copied from DooMLoRD's Easy Rooting Toolkit thread since both scripts use the same method to acquire root)
Sony Xperia X10 (GB firmware)
Sony Xperia Arc
Sony Xperia Arc S
Sony Xperia Play [R800i/R800x]
Sony Xperia Ray
Sony Xperia Neo
Sony Xperia Neo V
Sony Xperia Mini
Sony Xperia Mini S51SE
Sony Xperia Mini Pro
Sony Xperia Pro
Sony Xperia Active
Sony Xperia Live Walkman
NTT Docomo Xperia ARCO SO-02C
Samsung Galaxy S2 [GT-i9100/i9100P/i9100T]
Samsung Galaxy S II for T-Mobile (SGH-T989)
Samsung Galaxy S II for AT&T (SGH-I777), Skyrocket (SGH-i727)
Samsung Galaxy S II LTE Rogers Canada (SGH-I727R), Android version 2.3.5, Baseband version I727RUXKJ7
Samsung Galaxy S II Epic 4g Touch
Samsung Galaxy S2 HD LTE (SHV-E120S)(korea)
Samsung Galaxy S2 LTE (SHV-E110S)
Samsung Galaxy S2 LTE Japanese version (carrier DoCoMo) [SC-03D] (2.3.6) {OMKK3}
Samsung Galaxy i9100G
Samsung Galaxy S [i9000B] & [i9000 2.3.3 (PDA I9000BOJV8, Phone I9000XXJVO, CSC I9000GDTMJV7) and german T-Mobile branding], XWJVW (2.3.6)
Samsung Galaxy S 4G (aka SGH-T959V)
Samsung Galaxy S Plus (GT-I9001) OS 2.3.3 and 2.3.6 (I9001ZSKP6) & 2.3.4 firmware (i9001XXKP4)
Samsung Galaxy Mini GT-S5570 (GB only)
Samsung Galaxy Mini Pro i5510
Samsung Galaxy W [i8150]
Samsung Galaxy Y
Samsung Galaxy Y pro [B5510] (2.3.5)
Samsung Galaxy Tab [P1000] (2.3.3 firmware), [P1000N]
Samsung Galaxy Note [N7000]
Samsung Galaxy Player YP-G70 2.3.5 (GINGERBREAD.XXKPF)
Samsung Galaxy Ace (2.3.3, 2.3.4 firmware)
Samsung S5670 FIT DDKQ5 2.3.5
Samsung Nexus S [i9023] (2.3.6)
Samsung Nexus S 4G 2.3.7
Samsung Nexus S [i9020] (2.3.6) & Nexus S i9020A (2.3.6) & Nexus S i9020T (2.3.6)
Samsung Exhibit (SGH-T759)
Samsung Exhibit 4G (SGH-T759) (2.3.3) Build UVKE8
Samsung Epic 4G
Samsung Captivate i897 UCKH3
Motorola ATRIX
Motorola Milestone 3 [ME863 HK]
Motorola Milestone 2 with Gingerbread
Motorola XT860, Bell XT860
Motorola Defy+
Motorola Droid X sys ver 4.5.605 w/ gingerbread
Motorola Droid X2 (2.3.4) Sys ver 1.3.380.MB870.Verizon.en.US Build 4.5.1A-DTN-150-30
Motorola XT883 (China Telecom)
Motorola XT862 (Verizon Droid3)
Motorola DROID RAZR
Nexus One (2.3.6 stock)
LG Revolution
LG Nitro HD
Vizio VTAB1008 Tablet
Huawei Ideos U8150 (2.2)
Huawei Ideos X5 [U8800] (2.3.5)
HTC Sensation (S-OFF only)
HTC Chacha
Acer Liquid Mini (2.3.5)
Acer Liquid Metal (2.3.6)

nice
nicely done, well made .bat file - gona go have a play with this now - thanx

terminal 7 said:
nicely done, well made .bat file - gona go have a play with this now - thanx
Click to expand...
Click to collapse
this is a Work in progress let me know if run into any issues.
I can tell you that on some devices doing a full wipe you still need to do a factory reset in recovery before flashing because the fastboot method leaves the partitions empty

terminal 7 said:
nicely done, well made .bat file - gona go have a play with this now - thanx
Click to expand...
Click to collapse
i fixed your issue with setlocal now should be working for all gtalk me if you have any more issues or concerns

done
hi.
the SETLOCAL issue was good fun
CD method works just fine,
i have been playing with this on my old htc desire and it works great
nice work
.
.
.

terminal 7 said:
hi.
the SETLOCAL issue was good fun
CD method works just fine,
i have been playing with this on my old htc desire and it works great
nice work
.
.
.
Click to expand...
Click to collapse
glad you liked it if you find any issues with any devices let me know and i will work to fix them asap.

Will it work on Motorola Phones
Will it work on the new Motorola Phones?

yes
frankyvee said:
Will it work on the new Motorola Phones?
Click to expand...
Click to collapse
if the bootloader is unlocked and the device is fastboot capable which most if not all moto phones are yes.

Thanks
Awesome write up by Cameron from the portal team
New Tool – Fastboot flasher 2.5 simplifies the fastboot process
thanks for the kind words Cameron

image file
I would like to know witch img file to use and where can I download the file from?
slayerXcore said:
Version 2.5 Released
Re-themed and optimized
Includes full fastboot based wipe menus as well as installing OTA packages and PKIMG.zip or RUU.zip packages from HTC
Can also Install .img files to most partitions if bootloader is unlocked/s-off
Cant install custom ROM update zips due to the way they work
Download the small ~208Kb file Fastboot Flasher-V2.5-20120103-062110.zip
Download link: https://www.sugarsync.com/pf/D315775_7173530_001884
Youtube video (slightly outdated) will be making a new video once im finished tweaking more
Extract it somewhere like your desktop, though anywhere will work.
when i say extract it i mean use extract all so you get my file structure do not move these files or it will break*
Run / double click FastbootFlasher.bat
You will be be greeted by my ReadMe!.txt file please read it as it gives you a disclaimer saying im not liable for anything you do to your device
Close the ReadME!.txt
I hope this tool helps those who aren't familiar with fastboot or helps those who want a faster way of doing things.
One final note do not give it a file for another device or a non .img file it will flash it anyway no matter what file you drag and drop once you press enter it flashes what ever was dragged onto the script. Also do not drag a radio img when it asks for recovery or in revers, bad things will happen Wile they are fixable by using option 3 at the end and repeating the process I dont want anyone to mess up their deice making such a simple mistake.
Preview of 2.5
Consider this a small holiday gift
share it with anyone who has a rooted android device
yes i know other people have made .exe files with fancy interfaces but they are restricted to some devices and aren't as simplistic or fast.
i made this as a simple batch file so that anyone who wants to open it in a text editor can see exactly what it does and doesn't do as people don't trust executable files that can go downloading stuff or messing up your computer.
To *nix users i may try and make a version of this that will work for *nix also but if you run nix i trust you don't really need this
Click to expand...
Click to collapse

Does this work with ns4g
Sent from my Nexus S 4G using XDA Premium App

neo_x22000 said:
Does this work with ns4g
Click to expand...
Click to collapse
Yes it works with all nexus devices if you have unlocked your bootloader and rooted .
Mainly this is to be used to flash radio.img and recoveries for nexus devices. it can also function as a wipe menu for you.
_________________
abeauchamp said:
I would like to know witch img file to use and where can I download the file from?
Click to expand...
Click to collapse
as per the where to download files in question get .img files ect. from the correct device forum on XDA or elsewhere I am never going to include any files for specific devices as this Utility is designed to function for Many devices and I only own a few. The download Link for my Utility is in the OP

Where can I download this?

PTown599 said:
Where can I download this?
Click to expand...
Click to collapse
Download link: http://dev-host.org/CJ1

downloadsite down.....
I tried to download it, but an errormessage is coming up constantly. "Time out"

slayerXcore said:
Awesome write up by Cameron from the portal team
New Tool – Fastboot flasher 2.5 simplifies the fastboot process
thanks for the kind words Cameron
Click to expand...
Click to collapse
Using Chrome not getting a DLoad, is there a mirror?

Tekn010933 said:
Using Chrome not getting a DLoad, is there a mirror?
Click to expand...
Click to collapse
the download Link is in the OP its an HTTPS download so you can't right click it.
just left click to download

Try getting rid of the s.

[OFFICIAL THREAD] Lenovo K3 NOTE [CWM/ROOT]

Modding Lenovo K3 Note
I anticipate that I will, nor the forum will take responsibility 'of malfunctions and \ or damage!
Part One - CMW Install and Root command line
In this thread, I'll describe a simple, fast, and definitely safer than SPFTools.
SPFTools VCOM working on ports that are not always recognized, sometimes give problems also installing special drivers, they are almost always a problem for Windows because of the signatures on the driver.
Closed this little digression for information, we start with the drivers:
Driver Lenovo K3 Note + PDAnet+:
https://mega.co.nz/#!O4lmBaZa!jCUk1z0BB6wsBgP1P3e5BdoJQtBY_xi6TXuwcBOCv5k
Click to expand...
Click to collapse
Install all drivers Lenovo inside. Once you finished enable the USB debugging and wait for Windows to complete its configuration.
When completed restart the PC and install the utility on the device:
PdaNet:
https://play.google.com/store/apps/details?id=com.pdanet&hl=it
Click to expand...
Click to collapse
Be sure to restart to have all the drivers installed correctly and stay in Debug USB.
Without this included in your terminal this .zip file to obtain permits Root later:
SuperSU:
https://mega.co.nz/#!b8tSiYZJ!yr3okwkxmoR8NqSN10PCEtxsLl25aZ3VUSALqTKszsM
Click to expand...
Click to collapse
Now download this Minimal ADB (with Recovery K3 notes included) from here:
Minimal ADB & Fastboot + K3 Note Recovery (CWM):
https://mega.co.nz/#!rs0lHZrI!hE3Ux99skP-q3RYsgb9KNwX2Dnji192uU0KJB3iQNdo
Click to expand...
Click to collapse
Now comes the fun part!
Unzip the zip file and open the file py_cmd.exe and quietly run these commands:
Code:
adb devices
To ensure that the PC recognizes the device, and if it should be unauthorized make sure that USB debugging is enabled.
Code:
adb reboot bootloader
This command will reboot the phone on a black screen, going in fastboot .
Code:
fastboot devices
This command will confirm the above.
Code:
fastboot flash recovery recovery.img
This command will install the much sought CWM, but it is not over yet!
Code:
fastboot reboot
This command will restart the device.
Perfect! now to get root permissions, there will be that off the device, wait a few seconds and turn it on using this key combination:
VOLUME UP - VOLUME DOWN - POWER
Click to expand...
Click to collapse
Wait until the CWM is not playing, choose obviously the English language.
Subsequently searching
Code:
install zip
... and subsequently ...
Code:
choose zip from /sdcard
... looking for that zip file SuperUser inserted at the beginning.
Et voila! The device is unlocked and ready to receive new rom and functionality!
Part Two - Install new ROM from SPFTools CWM does not work when
Many with the above guide you tried to change the finding in eom stuck.
With this procedure you can go back, but before we move forward I want to give you a few details regarding the update of the rom:
*- The rom mounted on chinese devices with Play Service support and multilanguage already moddate the seller.
*- Given the above, download a rom 'official' (see NeedRom) carrying the phone in its native state.
*- If you need to download the latest versions from the site VibeUI not download the latest available, sometimes the downgrade is not possible (personal experience).
Let's start!
First, before you go ahead to make sure you have followed the guidance post 100% in the first part of the thread.
Follow the link:
SPFTools V5:
https://mega.co.nz/#!G0sVBK5A!M9DovhVgx_aCdXpySq0zmkKvrPbAFePtJgZRXyjtG7w
Click to expand...
Click to collapse
Now unpack everything and put it in a folder convenient for you.
I post the link of a rom in case I tried to see if this will work, even to you. To me it is working well.
In the third part if this rom works almost everyone will get all roms that I find around and decide what to do and what to do.
Rom 1949Deal:
https://www.dropbox.com/s/zep53n1j214ri45/lenovo k3 note rom.rar?dl=0
Password: 1949dealjoy
Click to expand...
Click to collapse
Once downloaded, extract directory in a readily available and open flash_tool.exe .
Before we go on, first remove the battery and attach only the USB cable, then set the SPFTools this:
{
"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"
}
Set in this way the program.
In step [1] look for the previously extracted folder and locate the file.
Give the program a few seconds to load the rom, and after leaving it in Download Only Click Download .
Obviously nothing will happen, to make sure that going forward, you can simply insert the battery and wait for the completion of the transaction.
Reinstall the back cover and turn on the device. Give it about 8/10 minutes for the first startup.
Et voila! We are again ready to modding this Lenovo K3 notes!
Part Three - Collection ROM
In update
You will not find in this type of tour guides, as is the link is driving are my own work, so excluding the Play app store are my property. If you have any problem with the link, do not hesitate to ask.
If you have been useful, it is needless to say that it is a thanks is appreciated!
PS: SORRY FOR MY BAD ENGLISH!​

Works like a charm. Thanks

will get my lenovo in a week and will use this guide, Thanks!
just one question, when installing the driver's is phono connected to pc? and is it connected with battery inside it?
kangel said:
Modding Lenovo K3 Note
I anticipate that I will, nor the forum will take responsibility 'of malfunctions and \ or damage!
In this thread, I'll describe a simple, fast, and definitely safer than SPFTools.
SPFTools VCOM working on ports that are not always recognized, sometimes give problems also installing special drivers, they are almost always a problem for Windows because of the signatures on the driver.
Closed this little digression for information, we start with the drivers:
Install all drivers Lenovo inside. Once you finished enable the USB debugging and wait for Windows to complete its configuration.
When completed restart the PC and install the utility on the device:
Be sure to restart to have all the drivers installed correctly and stay in Debug USB.
Without this included in your terminal this .zip file to obtain permits Root later:
Now download this Minimal ADB (with Recovery K3 notes included) from here:
Now comes the fun part!
Unzip the zip file and open the file py_cmd.exe and quietly run these commands:
Code:
adb devices
To ensure that the PC recognizes the device, and if it should be unauthorized make sure that USB debugging is enabled.
Code:
adb reboot bootloader
This command will reboot the phone on a black screen, going in fastboot .
Code:
fastboot devices
This command will confirm the above.
Code:
fastboot flash recovery recovery.img
This command will install the much sought CWM, but it is not over yet!
Code:
fastboot reboot
This command will restart the device.
Perfect! now to get root permissions, there will be that off the device, wait a few seconds and turn it on using this key combination:
Wait until the CWM is not playing, choose obviously the English language.
Subsequently searching
Code:
install zip
... and subsequently ...
Code:
choose zip from /sdcard
... looking for that zip file SuperUser inserted at the beginning.
Et voila! The device is unlocked and ready to receive new rom and functionality!
You will not find in this type of tour guides, as is the link is driving are my own work, so excluding the Play app store are my property. If you have any problem with the link, do not hesitate to ask.
If you have been useful, it is needless to say that it is a thanks is appreciated!
PS: SORRY FOR MY BAD ENGLISH!​
Click to expand...
Click to collapse

itzikd1 said:
will get my lenovo in a week and will use this guide, Thanks!
just one question, when installing the driver's is phono connected to pc? and is it connected with battery inside it?
Click to expand...
Click to collapse
Yes, the battery must be installed

thanks, rooted easly, took 5 mintues!

@kangel,thank you very much for this initiative. great contributions. You can visit the thread in Spanish to complement. Thanks again and I'll be here

Better add a custom ROM for Lenovo K3 note in the thread has official Roms of lenovo k3 note are useless bcuz FDD 4G and VPN are not supported in k3 notes official ROM. It would be better if some one finds and updates the thread with k3 notes custom roms available :good:

asif3366 said:
Better add a custom ROM for Lenovo K3 note in the thread has official Roms of lenovo k3 note are useless bcuz FDD 4G and VPN are not supported in k3 notes official ROM. It would be better if some one finds and updates the thread with k3 notes custom roms available :good:
Click to expand...
Click to collapse
Do you have it and know that FDD LTE is not supported? Sounds unlikely as China Unicom has FDD LTE in addition to TDD LTE (and the phone supports China Unicom).

Is there any ROM supporting dual SIMs?
Thanks.

sam10000 said:
Is there any ROM supporting dual SIMs?
Thanks.
Click to expand...
Click to collapse
Every ROM of k3 note official or custom ROM supports dual sim
---------- Post added at 09:45 AM ---------- Previous post was at 09:32 AM ----------
_mfm_ said:
Do you have it and know that FDD LTE is not supported? Sounds unlikely as China Unicom has FDD LTE in addition to TDD LTE (and the phone supports China Unicom).
Click to expand...
Click to collapse
Yes I have lenovo k3 note since few weeks but still I am not able to make FDD 4g work in my K3 note but yes I have fixed the VPN problem with a custom ROM but still 4g is not working in my K3 note.

Hi
Anyone knows where to get the STOCK rom (VIBEUI_V2.5_1512_5.495.1_ST_K50-T5) ?
And also from above CWM , can we flash below DEV rom ? Took from here (http://www.vibeui.com/vibeui/rom?key=k3 note#version-slip1)
VIBEUI_V2.5_1520_7.128.1_DEV_K50-T5
Or need to use FlashTool ?

asif3366 said:
Every ROM of k3 note official or custom ROM supports dual sim
---------- Post added at 09:45 AM ---------- Previous post was at 09:32 AM ----------
Yes I have lenovo k3 note since few weeks but still I am not able to make FDD 4g work in my K3 note but yes I have fixed the VPN problem with a custom ROM but still 4g is not working in my K3 note.
Click to expand...
Click to collapse
What mobile operator do you use?
BTW, Can you check if RDS is supported in the FM Radio app?

Pls add in 1st page for easy reference...

FeyoMx said:
@kangel,thank you very much for this initiative. great contributions. You can visit the thread in Spanish to complement. Thanks again and I'll be here
Click to expand...
Click to collapse
Hi FeyoMx,
Can you please provide us a link to download the fixed CWM recovery ?
the actual recovery (CWM or TWRP) can not do a correct restore, the phone will only reboot to recovery after a restore
Thank you.

dreambo said:
Hi FeyoMx,
Can you please provide us a link to download the fixed CWM recovery ?
the actual recovery (CWM or TWRP) can not do a correct restore, the phone will only reboot to recovery after a restore
Thank you.
Click to expand...
Click to collapse
Hi, here it is. This restores good backups

FeyoMx said:
Hi, here it is. This restores good backups
Click to expand...
Click to collapse
Thank you
I have already see that link, but I do not understand Spanish and in the google translated version, I can not have the download link :
We must follow the link of the china forum, or we have to be registered to see the link in the thread ?

dreambo said:
Thank you
I have already see that link, but I do not understand Spanish and in the google translated version, I can not have the download link :
We must follow the link of the china forum, or we have to be registered to see the link in the thread ?
Click to expand...
Click to collapse
Sorry https://drive.google.com/file/d/0BwmBEcCNY-yhSUVEY1BITnF5Zjg/view?usp=sharing
the instructions for use if you understand?

FeyoMx said:
Sorry https://drive.google.com/file/d/0BwmBEcCNY-yhSUVEY1BITnF5Zjg/view?usp=sharing
the instructions for use if you understand?
Click to expand...
Click to collapse
Thank you very match
No worry for instructions, the most important file is recovery.img and we can flash it using different manners.
I will test it this night at home.
thank you again.

[REQ] SafeCenter
Dear Colleagues,
I have Lenovo Vibe Z2. It has got recently the Lollipop upgrade that works quite well. But Lenovo did not include the SafeCecter app into the upgrade and the old one, extracted from the 4.4 ROM, isn't compatible with the new ROM, it even cannot be installed.
So, my request: would someone be so kind and extract the SafeCecter app from the K3 Note firmware for me? Since the K3 also has Lollipop I hope that your SafeCecter would serve well on my Z2 too.
Thanks a lot in advance!

ctibor said:
Dear Colleagues,
I have Lenovo Vibe Z2. It has got recently the Lollipop upgrade that works quite well. But Lenovo did not include the SafeCecter app into the upgrade and the old one, extracted from the 4.4 ROM, isn't compatible with the new ROM, it even cannot be installed.
So, my request: would someone be so kind and extract the SafeCecter app from the K3 Note firmware for me? Since the K3 also has Lollipop I hope that your SafeCecter would serve well on my Z2 too.
Thanks a lot in advance!
Click to expand...
Click to collapse
I hope you work. place on /System/priv-app and set permissions. greetings.

[D6603][BETA][OFFICIAL]Sony Official Android 6.0 Marshmallow - Beta testing

With a considerable delay, Sony is inviting users from Spain, Italy and Netherlands, to beta-test new official Android M firmware.
Source: http://www.xda-developers.com/xda-external-link/xperia-beta-program-android-apps-on-google-play/
Direct link to Beta: https://play.google.com/store/apps/details?id=com.sonymobile.xperiabeta.signup
{
"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"
}
I think we are all looking forward to see it in action, and from the beginning, one of the most important question:
Will this firmware be using Verfied Boot (aka. dm-verity) to protect the system?
because if yes, it will render the system unrootable on Locked Bootloader...
So guys and girls from ES, IT and NL ... go on, write your thoughts....
UPDATE 12. March 2016
INSTALLING
You can decide if you want to "install" original unmodified firmware by flashing zip file in recovery or restoring backup of Android M. In any way you need to be on pre-rooted latest Lollipop (v .264) before flashing. Reflash stock if you are on custom ROM. The reason is that this firmware needs bootloader and baseband from v.264 to work.
So to use backup of original Android M Beta:
This was kindly provided by @juanpirulo http://forum.xda-developers.com/showpost.php?p=65777398&postcount=158 and steps to install from @jjwrongjj http://forum.xda-developers.com/z3/general/d6603-sony-official-android-6-0-t3312448/post65781545.
To flash zip:
There is flashable firmware available thanks to @masuods70 at http://forum.xda-developers.com/showpost.php?p=65871019&postcount=440
For D6633 dual
Users of DualSIM D6633 can flash patch: http://forum.xda-developers.com/showpost.php?p=65877968&postcount=459
ROOTING
This ROM is can be currently rooted with /system R/W access on both LB/UB - need to root in recovery after flashing the system
To root both firmwares you need to stay in the recovery after flash/restore and flash SuperSU, byeselinux and RICdefeat.
There is no prerooted zip available at the moment.
THERE is NO RECOVERY for locked bootloaders.
There is dedicated ROOTING thread by bro @wolbreak
The first good news is that dm-verity is DISABLED on this Beta Marshmallow and it means that the firmware can be rooted. As @Black_Eyes found, rooting can be done with KingRoot v.4.82. However, the root is only partial, because it doesn't disable RIC service which is preventing writes to /system (thanks to @lee480 @shoey63 @EricCartmanez )
I am sure this is excellent news as surely guys are now working on RIC part of the deal.
This news also means, that it can probably be pre-rooted as soon as FTF will be available.

Annoying it's restricted. Sony really are going slow with Marshmallow!

Xperia Beta Program Apk Link => https://www.adrive.com/public/zgwRJY.html
I think add first post for link
I'm from TURKEY but ı ınstall this apk and sıgn beta program

bugra333 said:
Xperia Beta Program Apk Link => https://www.adrive.com/public/zgwRJY.html
I think add first post for link
I'm from TURKEY but ı ınstall this apk and sıgn beta program
Click to expand...
Click to collapse
In OP there is already official link for app through Google Store.
Did you already received e-mail that you have been accepted as beta tester? Or just registered and waiting for what is going to happen?

I install the apk and receive a confirmation to my email. Live in Norway signed from Swedish IP with VPN.
XperiaBetaProgram
Thank you for signing up to Sony Mobile’s Xperia Beta Program. You will receive an email notification once the activity is about to start.
Kind Regards,
Xperia Beta Program
edit: The official link say that non of my devices are compatible and unable to install. The direct link with apk it works for me and sign up.

veskostoev said:
I install the apk and receive a confirmation to my email. Live in Norway signed from Swedish IP with VPN.
XperiaBetaProgram
Thank you for signing up to Sony Mobile’s Xperia Beta Program. You will receive an email notification once the activity is about to start.
Kind Regards,
Xperia Beta Program
Click to expand...
Click to collapse
Ok, thanks for info, let's see how it goes. Last time with Concept also everybody got sign-up confirmation, but not everybody got actual confirmation for beta testing..

ondrejvaroscak said:
Ok, thanks for info, let's see how it goes. Last time with Concept also everybody got sign-up confirmation, but not everybody got actual confirmation for beta testing..
Click to expand...
Click to collapse
I got also the first time but i never install it
Great news everyone! You have been selected to participate in phase 2 of the Sony Mobile concept initiative. What this means is that you will be part of a select group receiving a roll-out of our concept software running Marshmallow, with the opportunity to directly influence future releases of this software.
Getting started
You have already been invited to our Google+ community. A majority of the communication will be handled from here.
Please take your time to read through the “How to get started” section in the community.
Here you will find instructions on how to flash the concept software.
https://plus.google.com/communities/*****************
IMPORTANT NOTE:
Your user data will be lost when installing the concept software unless you follow the instructions on how to migrate and backup your data in this post: https://plus.google.com/********************×
The post will be available as soon as you accept your invitation to the g+ community.
We are looking forward to your comments and feedback, let’s rock!
See you in the G+ community!

veskostoev said:
I got also the first time but i never install it
Great news everyone! You have been selected to participate in phase 2 of the Sony Mobile concept initiative. What this means is that you will be part of a select group receiving a roll-out of our concept software running Marshmallow, with the opportunity to directly influence future releases of this software.
Getting started
You have already been invited to our Google+ community. A majority of the communication will be handled from here.
Please take your time to read through the “How to get started” section in the community.
Here you will find instructions on how to flash the concept software.
https://plus.google.com/communities/*****************
IMPORTANT NOTE:
Your user data will be lost when installing the concept software unless you follow the instructions on how to migrate and backup your data in this post: https://plus.google.com/********************×
The post will be available as soon as you accept your invitation to the g+ community.
We are looking forward to your comments and feedback, let’s rock!
See you in the G+ community!
Click to expand...
Click to collapse
I think that e-mail is from Concept, not from this Beta... alright?

FTF anyone ?

DennisDD78 said:
FTF anyone ?
Click to expand...
Click to collapse
I think it is too early, they just begun with registrations...

Registry started 03.february.

dkionline said:
Registry started 03.february.
Click to expand...
Click to collapse
Yes, they take some time. I am sure, if anybody would have this firmware already installed, we would know it here in XDA Forums...

ondrejvaroscak said:
Yes, they take some time. I am sure, if anybody would have this firmware already installed, we would know it here in XDA Forums...
Click to expand...
Click to collapse
I wonder what Sony will do with the Small App whole thing seeing the Concept doesn't have one. Please anybody who have joined this Beta, to post a picture about how the Small Apps getting implemented there.

hansip87 said:
I wonder what Sony will do with the Small App whole thing seeing the Concept doesn't have one. Please anybody who have joined this Beta, to post a picture about how the Small Apps getting implemented there.
Click to expand...
Click to collapse
If I recall correctly the lollipop concept didn't have small apps either. The concept is just that a concept. I don't see Sony removing any of their signature features like small apps or stamina mode. I just hope that marshmallow brings us the automatic Headphone compensation from the z5 since that can't be ported. I have tried

ondrejvaroscak said:
I think that e-mail is from Concept, not from this Beta... alright?
Click to expand...
Click to collapse
Yes first post is from Beta second is from Concept November 2015.

Sony will not remove small app function
But i'm wonder what sony will change how it looks in MM.
Hope the Beta program will come next week, so we can see what sony will do on their old UI.

ReadReadz said:
Sony will not remove small app function
But i'm wonder what sony will change how it looks in MM.
Hope the Beta program will come next week, so we can see what sony will do on their old UI.
Click to expand...
Click to collapse
I think it will not have any changes there. What concerns me is that Google restrict Overlay apps by default so one should turn it on all the way on the Setting page. If Sony can automatically enable the setting, it's great

I registered for Beta too without VPN and got the Confirmation Email already, now lets see if they choose me again. On Concept i was invited to test already. I hope dm-verity will not be included but i think that it will probably be included because of Security reasons like in all new Xperias above Z3.

I'm on the current 6.0.1 concept. The Beta program seems to be incompatible with this ROM. I assume we'll have to wait for the FTF file or at least downgrade to official 5.1.1?
Sent from my D6603 using Tapatalk

humzaahmed155 said:
I'm on the current 6.0.1 concept. The Beta program seems to be incompatible with this ROM. I assume we'll have to wait for the FTF file or at least downgrade to official 5.1.1?
Sent from my D6603 using Tapatalk
Click to expand...
Click to collapse
I would do it clean way, fresh clean stock .264 and go..

Sony's developer policy! RANT

MOD EDIT by @gregbradley. I did not see the need for the expletive in the title, so i took it out for you.
So here's a little rant.
Read it if you'd like to, don't read if you don't like to.
Let's start with a little introduction. I've bought my Z3 about a year ago. I wanted to go with the z3+, but the Snapdragon 810 seemed to cause some issues. I still wanted the Sony batterylife after coming from a Galaxy S4 (which doesn't have the best battery life). I found online that Sony shares AOSP source code, so building a custom rom shouldn't be too hard.
Recently I have thought about unlocking my bootloader, but reading further into it, I found there to be NO upsides to unlocking your bootloader.
- There's a possibility of losing your DRM Keys when unlocking bootloader.
- You can not lock your bootloader again, so you're forever excluded from any OTA's.. Sony supports AOSP source code, you know.. to be developer friendly. But locking your bootloader again is not possible. This makes unlocking it very unappealing.. and very developer unfriendly.
- You cannot flash a recovery through fastboot, because Sony doesn't use conventional recoveries. Very developer friendly!
- Fine, Sony decides to release Android MM concept. Great, I was excited for this! But, the actual MM final firmware is nothing like the concept firmware and still a lot like the actual Sony themed firmware. (In my opinion this is disappointing, but that might be just me). When asked about why there are differences between the concept and the final firmware, the concept team replies that it has nothing to do with the final firmware. Then what's the point of a concept firmware??
Maybe I'm just nitpicking, but this seems very hypocritical from Sony..
C'mon Sony, your mobile department isn't doing too well, and this sure as hell doesn't make it better.
Now I know there are maybe only several thousand people actually wanting to run AOSP on their Sony, but I sure as hell am not buying another Sony phone until this policy changes.
Thanks.
Joost

Im still trying to figure out which part you unhappy about lol ?????
I have the Z3 rooted with Android 6.0.1 Slim1.6 Rom LB
And its the best ever with longest battery life ive experienced no issues fast and smooth
I dont want any other phone right now what more could you want?

MasterCMTS said:
Im still trying to figure out which part you unhappy about lol ?????
I have the Z3 rooted with Android 6.0.1 Slim1.6 Rom LB
And its the best ever with longest battery life ive experienced no issues fast and smooth
I dont want any other phone right now what more could you want?
Click to expand...
Click to collapse
My issue?
On one hand Sony releases AOSP code, while on the other hand they make it a real damn pain in the ass to even run an AOSP rom. There have been several developers out there to try and build an AOSP rom. None of them managed to make a fully working one, because Sony made it so damn hard. I find this hypocritical and unjust.
What I want is for Sony to make it actually possible to run an AOSP rom, and stop pretenting like it's possible.

Me Gusta said:
So here's a little rant.
Read it if you'd like to, don't read if you don't like to.
Let's start with a little introduction. I've bought my Z3 about a year ago. I wanted to go with the z3+, but the Snapdragon 810 seemed to cause some issues. I still wanted the Sony batterylife after coming from a Galaxy S4 (which doesn't have the best battery life). I found online that Sony shares AOSP source code, so building a custom rom shouldn't be too hard.
Recently I have thought about unlocking my bootloader, but reading further into it, I found there to be NO upsides to unlocking your bootloader.
- There's a possibility of losing your DRM Keys when unlocking bootloader.
- You can not lock your bootloader again, so you're forever excluded from any OTA's.. Sony supports AOSP source code, you know.. to be developer friendly. But locking your bootloader again is not possible. This makes unlocking it very unappealing.. and very developer unfriendly.
- You cannot flash a recovery through fastboot, because Sony doesn't use conventional recoveries. Very developer friendly!
- Fine, Sony decides to release Android MM concept. Great, I was excited for this! But, the actual MM final firmware is nothing like the concept firmware and still a lot like the actual Sony themed firmware. (In my opinion this is disappointing, but that might be just me). When asked about why there are differences between the concept and the final firmware, the concept team replies that it has nothing to do with the final firmware. Then what's the point of a concept firmware??
Maybe I'm just nitpicking, but this seems very hypocritical from Sony..
C'mon Sony, your mobile department isn't doing too well, and this sure as hell doesn't make it better.
Now I know there are maybe only several thousand people actually wanting to run AOSP on their Sony, but I sure as hell am not buying another Sony phone until this policy changes.
Thanks.
Joost
Click to expand...
Click to collapse
You can use TA Backup to restore your DRM keys as long as you back them up before unlocking the bootloader ('m just about to do it)
You can install a custom recovery via fastboot (I used TWRP to replace cyanogen recovery).
Not really sure your points to be honest.

savo83 said:
You can use TA Backup to restore your DRM keys as long as you back them up before unlocking the bootloader ('m just about to do it)
You can install a custom recovery via fastboot (I used TWRP to replace cyanogen recovery).
Not really sure your points to be honest.
Click to expand...
Click to collapse
Sure, you can restore DRM.. but is it really convenient? My point is that Sony basically promotes AOSP roms by releasing source code, but on the other hand they make it impossible to enjoy a fully working AOSP rom because of DRM, camera's never working, etc..
Oh, and if you could explain to me how you flashed TWRP, and which file exactly, that'd be great . I've literally already spent 6 hours today trying to figure **** out after unlocking my bootloader..
Thanks in advance!

I totally agree with you. Building an AOSP ROM for Z3 seems to be difficult (Tried cm too but extracting proprietary blobs did not work). The way how recovery works here is pretty stupid, seeing that we dont have a recovery on N for example, so I need to be on it without root (i dont blame developers here, but again, Sony's implementation). Also I haven't been able to work around the radio or camera thing in AOSP, even though I have only been able to build the ROM like once some weeks ago
---------- Post added at 06:00 AM ---------- Previous post was at 05:55 AM ----------
Me Gusta said:
Sure, you can restore DRM.. but is it really convenient? My point is that Sony basically promotes AOSP roms by releasing source code, but on the other hand they make it impossible to enjoy a fully working AOSP rom because of DRM, camera's never working, etc..
Oh, and if you could explain to me how you flashed TWRP, and which file exactly, that'd be great . I've literally already spent 6 hours today trying to figure **** out after unlocking my bootloader..
Thanks in advance!
Click to expand...
Click to collapse
Also the recovery thing. Just download the .img from Nailyk's thread and put it in ADB folder. Then go to fastboot and type fastboot flash FOTAKernel . Then boot to recovery by pressing power and volume down button, releasing power when phone vibrates and volume when sony logo appears.

Me Gusta said:
- There's a possibility of losing your DRM Keys when unlocking bootloader.
Click to expand...
Click to collapse
That is true and disappointing. However, there is a way to backup the keys and restore whenever the need arises.
Me Gusta said:
- You can not lock your bootloader again, so you're forever excluded from any OTA's.. Sony supports AOSP source code, you know.. to be developer friendly. But locking your bootloader again is not possible. This makes unlocking it very unappealing.. and very developer unfriendly.
Click to expand...
Click to collapse
fastboot oem lock or restoring the DRM keys should relock the bootloader.
Me Gusta said:
- You cannot flash a recovery through fastboot, because Sony doesn't use conventional recoveries. Very developer friendly!
Click to expand...
Click to collapse
Sure it works, you just need to run 23.4.A.1.264 firmware or newer. I use fastboot flash recovery something.img all the time.
Me Gusta said:
- Fine, Sony decides to release Android MM concept. Great, I was excited for this! But, the actual MM final firmware is nothing like the concept firmware and still a lot like the actual Sony themed firmware. (In my opinion this is disappointing, but that might be just me). When asked about why there are differences between the concept and the final firmware, the concept team replies that it has nothing to do with the final firmware. Then what's the point of a concept firmware??
Click to expand...
Click to collapse
I think the Concept software is for those who don't need Sony enhancements (X-Reality, ClearAudio+, etc.) and want something that is close to stock.

So:
-You can backup and restore DRM functions even with an unlocked BL.
-You can relock BL again (haven't tried it myself but I think it's possible, if you check out DRM restoration guides I think they also show how to relock the BL)
-The new Sony BL allows fastbooting recoveries, the older ones support FOTA recoveries (I've used both with no problems)
-The MM concept project is still live, you can install it and continue using it, it gets updated regularly and is very close to AOSP.
-True Sony is kind of shady with their sources but you can build AOSP, there are AOSP builds for the Z3 here: http://fxpblog.co/ they get released whenever Sony releases new sources but you can also make builds yourself. The only true issue with sources comes out on certain AOSP functions and that we don't have (yet) fully working CM13 builds. As for the concept firmware it's exactly what you said, Sony is giving it out to people who are interested in having a close AOSP experience with support from the vendor while giving feedback to further improve it. Sony is making moves and is becoming more developer friendly by the month, other than new and constantly updated sources, proof of this is the Xperia Z3 is the only non-Nexus device that gets to run the Android N preview officially given from the vendor.
The Z3 is a great device, I personally haven't regreted the purchase, the only thing that bugs me is that neither I nor anyone else has managed to build a fully functional CM13 build (kudos to infected btw).
---------- Post added at 09:02 AM ---------- Previous post was at 08:58 AM ----------
Evokkimus said:
I totally agree with you. Building an AOSP ROM for Z3 seems to be difficult (Tried cm too but extracting proprietary blobs did not work). The way how recovery works here is pretty stupid, seeing that we dont have a recovery on N for example, so I need to be on it without root (i dont blame developers here, but again, Sony's implementation). Also I haven't been able to work around the radio or camera thing in AOSP, even though I have only been able to build the ROM like once some weeks ago
---------- Post added at 06:00 AM ---------- Previous post was at 05:55 AM ----------
Also the recovery thing. Just download the .img from Nailyk's thread and put it in ADB folder. Then go to fastboot and type fastboot flash FOTAKernel . Then boot to recovery by pressing power and volume down button, releasing power when phone vibrates and volume when sony logo appears.
Click to expand...
Click to collapse
As I said fxp has some builds, I haven't tested them but I think they work (http://fxpblog.co/)

I was eager to try out FXP's aosp ROM, due to 3.10 kernel and such, but I got an error about updater-script in META-INF, didn't read further. I have my suspicions that it was a bad download, but their current site is so slow to download from (about 2 hours to download, and only a +20kb/s faster if you register), and i'm not going to pay for that site. If it helps any, i just wiped data, system and caches and tried flashing the ROM.
---------- Post added at 12:14 PM ---------- Previous post was at 11:56 AM ----------
CedArctic said:
So:
-You can backup and restore DRM functions even with an unlocked BL.
-You can relock BL again (haven't tried it myself but I think it's possible, if you check out DRM restoration guides I think they also show how to relock the BL)
-The new Sony BL allows fastbooting recoveries, the older ones support FOTA recoveries (I've used both with no problems)
-The MM concept project is still live, you can install it and continue using it, it gets updated regularly and is very close to AOSP.
-True Sony is kind of shady with their sources but you can build AOSP, there are AOSP builds for the Z3 here: http://fxpblog.co/ they get released whenever Sony releases new sources but you can also make builds yourself. The only true issue with sources comes out on certain AOSP functions and that we don't have (yet) fully working CM13 builds. As for the concept firmware it's exactly what you said, Sony is giving it out to people who are interested in having a close AOSP experience with support from the vendor while giving feedback to further improve it. Sony is making moves and is becoming more developer friendly by the month, other than new and constantly updated sources, proof of this is the Xperia Z3 is the only non-Nexus device that gets to run the Android N preview officially given from the vendor.
The Z3 is a great device, I personally haven't regreted the purchase, the only thing that bugs me is that neither I nor anyone else has managed to build a fully functional CM13 build (kudos to infected btw).
---------- Post added at 09:02 AM ---------- Previous post was at 08:58 AM ----------
As I said fxp has some builds, I haven't tested them but I think they work (http://fxpblog.co/)
Click to expand...
Click to collapse
I also tried building CM but stuck on proprietary blobs part. Couldn't pull them from the device for some reason, even though i was on CM rom at the time. (I did it because breakfast ended up in some vendor errors and Z3 didnt show up on the list either)

Evokkimus said:
I also tried building CM but stuck on proprietary blobs part. Couldn't pull them from the device for some reason, even though i was on CM rom at the time. (I did it because breakfast ended up in some vendor errors and Z3 didnt show up on the list either)
Click to expand...
Click to collapse
Weird, I build CM12.1/CM13.0/twrp 3 with theMuppet repo without a glitch. Can you paste your compilation error in a pastebin or something like this? Maybe I can help you a little (I'm a compilation newbie)

nailyk said:
Weird, I build CM12.1/CM13.0/twrp 3 with theMuppet repo without a glitch. Can you paste your compilation error in a pastebin or something like this? Maybe I can help you a little (I'm a compilation newbie)
Click to expand...
Click to collapse
Basically the error I get is with extract-files.sh. When I run "./extract-files.sh" while phone is plugged in, I get permission denied. The other option for me is to run it with sudo, but then I get "line XX adb: command not found" (many lines of this error). Someone suggested chmod or opening a terminal window inside the folder where extract-files.sh is located. There shouldn't be any errors with my AndroidSDK path, even though some suggest the error is with this.
Also the reason I'm trying to pull these blobs, is because the CM tutorial told me so
{
"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"
}
https://wiki.cyanogenmod.org/w/Build_for_z3
------------------------------------------------------------
Also the reason I'm building CM is because I still don't know how to get radio working, even though a person has told how to get it working, I don't know how to exactly do it. But firstly I would like this CM thing to work. Thanks for your help.

Evokkimus said:
Also the reason I'm building CM is because I still don't know how to get radio working, even though a person has told how to get it working, I don't know how to exactly do it. But firstly I would like this CM thing to work. Thanks for your help.
Click to expand...
Click to collapse
No worries.
So it may be a little more complicated.... If you just need a functional self build CM, try to include themuppet repo. If your device variant is not currently officially supported it can be more complicated.
I suggest you to open (or find) a dedicated thread and quote me, or join #[email protected]
Otherwise I'm following this thread because I found some point really interesting. I'm currently in trouble with Sony, that's why I subscribe.
Sorry for off-topic answers.

sorry did not see the date

arminbih said:
sorry did not see the date
Click to expand...
Click to collapse
Customer service troubles. They didn't respect law about unlocked bootloader into my country and refused to fix my device.

I know this thread is basically dead but I figured I'd poke it with a stick a few times and give my two cents.
First of all, the reason I chose Sony. I peviously owned Galaxy S4 and at some point (Android 4.2.2?) they implemented a security software called KNOX. It lets you create encrypted partitions for business stuff. Soon after, users started reporting that any unofficial changes result in a "0x01" flag showing in the download mode. Turns out, the device has a physical e-fuse which is burned and can not be reverted (except with a motherboard change). It was mainly for the customer services to be able to tell if the phone had been tampered with. But here's the catch - it was also triggered when installing official Samsung firmware using ODIN (basically FlashTool or Emma for Samsung). And downgrading firmware to pre-KNOX resulted in a special lock - the inability to upgrade again.
XDA members, such as Chainfire and others, have not managed to crack the software after several years, despite the bounty of thousands of dollars. I didn't think much of it, and rooted. Months after that my phone stopped recognizing the SIM card. And since I had "0x01" I had no warranty. So it went to customer service many times, I paid for the SIM reader change, and still nothing. Even custom ROMs didn't help.
So, I had a phone with no SIM support, and no faith in Samsung. I found out that Sony "encourages Android development" - bootloader unlocking and so on. Soon after I bought a Z3, and being a power user, I wanted to root. And then I found out about the DRM. The more I researched, the more livid I got. Finally I managed to dig up a method of rooting without bootloader unlock. After every small update Sony issued, I had to go through hours of researching and developing a new cusom update for my device. After some time I just decided to go with a (back then unreliable) DRM function restoring flashable zip.When I heard there will be no Nougat for Z3, I was quite mad. I looked into some AOSP's. NONE of them were working correctly. So I settled with a Z3 on unlocked BL with some DRMs working. The device has hiccups but is usable. I am disappointed in Sony and I am disappointed in Samsung. Never buying their phones again.
But now that @nailyk is developing LineageOS for Shinano devices, we have new hope! :victory:

The Android Robot said:
I know this thread is basically dead but I figured I'd poke it with a stick a few times and give my two cents.
First of all, the reason I chose Sony. I peviously owned Galaxy S4 and at some point (Android 4.2.2?) they implemented a security software called KNOX. It lets you create encrypted partitions for business stuff. Soon after, users started reporting that any unofficial changes result in a "0x01" flag showing in the download mode. Turns out, the device has a physical e-fuse which is burned and can not be reverted (except with a motherboard change). It was mainly for the customer services to be able to tell if the phone had been tampered with. But here's the catch - it was also triggered when installing official Samsung firmware using ODIN (basically FlashTool or Emma for Samsung). And downgrading firmware to pre-KNOX resulted in a special lock - the inability to upgrade again.
XDA members, such as Chainfire and others, have not managed to crack the software after several years, despite the bounty of thousands of dollars. I didn't think much of it, and rooted. Months after that my phone stopped recognizing the SIM card. And since I had "0x01" I had no warranty. So it went to customer service many times, I paid for the SIM reader change, and still nothing. Even custom ROMs didn't help.
So, I had a phone with no SIM support, and no faith in Samsung. I found out that Sony "encourages Android development" - bootloader unlocking and so on. Soon after I bought a Z3, and being a power user, I wanted to root. And then I found out about the DRM. The more I researched, the more livid I got. Finally I managed to dig up a method of rooting without bootloader unlock. After every small update Sony issued, I had to go through hours of researching and developing a new cusom update for my device. After some time I just decided to go with a (back then unreliable) DRM function restoring flashable zip.When I heard there will be no Nougat for Z3, I was quite mad. I looked into some AOSP's. NONE of them were working correctly. So I settled with a Z3 on unlocked BL with some DRMs working. The device has hiccups but is usable. I am disappointed in Sony and I am disappointed in Samsung. Never buying their phones again.
But now that @nailyk is developing LineageOS for Shinano devices, we have new hope! :victory:
Click to expand...
Click to collapse
Lots of OEM are doing this stuffs to protect their intellectuals rights with DRMs. AFAIK oneplus allow bootloaders unlock.
Just for fun, the TA partition of sony contain so much things... It is crazy! BTW I think we have fuse too
idk where you live but in Europe there is a law which basically said: hardware and software are separated and OEM need to fix hardware, except if they can prove this is user fault.
1999/44/CE in date of 1999-05-31.