Database Develop

[STOCK][ROOTED][7.0.A.3.195][Thats it][29/11/12]

Introducing
STOCK ROOTED 7.0.A.3.195
[LT30p][Unlocked and Locked Bootloaders]​
No claims, no nonsense, this is just a rom for people who want a stock rom as is from SONY except with root and want a trusted source.
I hesitate to call it development. [MOD's, if you think it should be moved, feel free] Its just something I did and thought I should share​Feedback is actively encouraged​
Features
Based on [STOCK FIRMWARE][LT30p][UK Generic][7.0.A.3.195]
Rooted
No superuser app is included, as superuser apps are not stock. You can download your choice of superuser.apk or SuperSU.apk from the market.
Full changelog in post 2, will be empty because thats it! It also means I have not added a super user app, because stock rom does not come with one and you have a choice of super user apps to download from the market. ​
Installation for Unlocked Bootloader
Make a backup- Always backup just in case you ****up
Flash my kernel from here or advanced stock kernel found here Credit lzyllp (This is to get Recovery and root. Also, the kernel has a lot of tweaks. Choose either T or TX depending on your phone.)
Enter recovery
Factory reset
Flash rom.
Installation for Locked Bootloader
Use flashtool to flash any generic 7.0.A.1.303 ftf.
Root using Bin4ry's method.
Install CMW for locked bootloaders
Enter recovery, factory reset and flash the ROM. Then flash the flashable version of CMW recovery for locked bootloaders before you reboot.
FIX FOR BOOTLOOP WITH EXTENDED BATTERY MODE. Flash this in flashtool to update your kernel to stock 7.0.A.3.195 Stock kernel
[All the tools and links can be found from the all in one thread here]
Optional Installation Step
If you are coming from a ROM with the same base you can advance restore you data partition in CMW to get all your apps back.​
Known Bugs and Fixes (If applicable)
Code:
[B][U]Bug[/U][/B]
Bootloop for those who are on a locked bootloader and enable extended battery mode.
[B][U]Version[/U][/B]
All
[B][U]Cause[/U][/B]
Using a 7.0.A.3.195 ROM with a 7.0.A.1.303 kernel.
[B][U]Fix[/U][/B]
Flash [URL="http://www.mediafire.com/?2b75t7dpk72z12h"]this[/URL] file in flashtool to update the kernel to 7.0.A.3.195
How to Report Bugs
Answer these questions.
1. Which version of the ROM did you download? Please provide the download link.
2. Are you on a locked or unlocked bootloader?
3. Which kernel are you on?
4. Have you flashed anything else, or is the bug coming from a CLEAN install of this ROM?
5. What are the symtpons of the bug?
6. How can I reproduce the bug?
7. Can you provide a logcat?
8. Any other comments that might help me or others to help you.​
Credits
Sony ​
Download
Here​
Disclaimer
As usual, I am not responsible for turning your beloved phone into a bookend, please read and educate yourself fully before attempting any mod on your phone. And if you drop it down the toilet it has nothing to do with me​

Changelog
Root

Screen shots
Look at your stock Xperia T screen.

wifi dont working...flash the LT30_7.0.A.3.195_kernel.ftf than device dont open appears sony logo than not open device...

It works. Redownload

Hi. I flash your rom and enter in home screens, but when i try flash kernel .195 with flashtool, semc flash device drivers don't install and flash not start. I install any drivers from folder drivers on flashtool, but same error. What drivers files are needed to flash this kernel?

Monipeev said:
Hi. I flash your rom and enter in home screens, but when i try flash kernel .195 with flashtool, semc flash device drivers don't install and flash not start. I install any drivers from folder drivers on flashtool, but same error. What drivers files are needed to flash this kernel?
Click to expand...
Click to collapse
Have you unlocked the bootloader?
If not you will not ba bale to flash the custom kernel

gregbradley said:
Have you unlocked the bootloader?
If not you will not ba bale to flash the custom kernel
Click to expand...
Click to collapse
I know, but in step to flash rom with locked bootloader, you say flash .195 kernel.
I remember in arc thread, when need to root em, we need downgrade kernel, root and after that, flash .587.
I am on locked bootloader. If this rom is with .195 kenel, i don't need flash another. I know this.

Monipeev said:
I know, but in step to flash rom with locked bootloader, you say flash .195 kernel.
I remember in arc thread, when need to root em, we need downgrade kernel, root and after that, flash .587.
I am on locked bootloader. If this rom is with .195 kenel, i don't need flash another. I know this.
Click to expand...
Click to collapse
ok, i see. You are flashing a stock kernel. Then it should be an .ftf file .
Can you flash anything in flash tool? If so you should be bale to flash a stock kernel ftf.
Make sure you are doing it in flashmode

gregbradley said:
ok, i see. You are flashing a stock kernel. Then it should be an .ftf file .
Can you flash anything in flash tool? If so you should be bale to flash a stock kernel ftf.
Make sure you are doing it in flashmode
Click to expand...
Click to collapse
Yes, i flash old .303 ftf with flashtool before 4-5 days.
I connect device in flashmode, green led light, but when window7 notify me to install flash driver and i confirm, windows don't install any flash driver.
PS. Need em i from this kernel or this kernel/.195/ install when i flash on your rom?

Monipeev said:
Yes, i flash old .303 ftf with flashtool before 4-5 days.
I connect device in flashmode, green led light, but when window7 notify me to install flash driver and i confirm, windows don't install any flash driver.
Click to expand...
Click to collapse
goto the drivers folder in flashtool and run drivers.exe

gregbradley said:
goto the drivers folder in flashtool and run drivers.exe
Click to expand...
Click to collapse
Exactly, i install it many times, but when i enter to flashmode, to waiting flash, windows try again install flashmode drivers, but my phone after 10-15s. disconnect and install windows flash drivers stoped.
This disconnected device from flashtools without installed the drivers.

Monipeev said:
Exactly, i install it many times, but when i enter to flashmode, to waiting flash, windows try again install flashmode drivers, but my phone after 10-15s. disconnect and install windows flash drivers stoped.
This disconnected device from flashtools without installed the drivers.
Click to expand...
Click to collapse
post the log from flashtool please.

gregbradley said:
post the log from flashtool please.
Click to expand...
Click to collapse
In time when flashtools say that my device connect in flashmode, windows tried install flash drivers.
But after that device disconnect from flashtool without windows install the drivers.
When i tried again, same result.
My usb debugging is on, but flashtool post, that is Off.
After that, device disconnected again.
I restart my computer, but same ......
02/027/2012 21:27:00 - INFO - <- This level is successfully initialized
02/027/2012 21:27:00 - INFO - Flashtool Version 0.9.9.0 built on 2012-11-13 22:53:30
02/027/2012 21:27:00 - INFO - You can drag and drop ftf files here to start flashing them
02/027/2012 21:27:05 - INFO - Device disconnected
02/027/2012 21:27:11 - INFO - Device connected in flash mode
02/027/2012 21:27:55 - INFO - Device disconnected
02/028/2012 21:28:07 - INFO - Device connected with USB debugging off
02/028/2012 21:28:07 - INFO - For 2011 devices line, be sure you are not in MTP mode

Monipeev said:
In time when flashtools say that my device connect in flashmode, windows tried install flash drivers.
But after that device disconnect from flashtool without windows install the drivers.
When i tried again, same result.
Click to expand...
Click to collapse
uninstall flashtool and reboot and reinstall.
Makesure you are in mtp mode not msc.
also, drop the ftf into the open window first, then wait for the prompt screen to prompt you to connect in flashmode.

gregbradley said:
uninstall flashtool and reboot and reinstall.
Makesure you are in mtp mode not msc.
also, drop the ftf into the open window first, then wait for the prompt screen to prompt you to connect in flashmode.
Click to expand...
Click to collapse
Yes, i am sure that i am in mtp not in msc mod and it is by default after install the rom.
But ok, tomorrow i will reinstall flashtool and all drivers, and tried again.
For now i will stay with old kernel and will see that pc companion recognize my device to device that have new update.
But nevermind, tomorrow i tried fresh install of all and post here result.

Monipeev said:
Yes, i am sure that i am in mtp not in msc mod and it is by default after install the rom.
But ok, i will reinstall flashtool and all drivers, and tried again.
Click to expand...
Click to collapse
yes, and actually try to flash something before you enter flashmode...drop the ftf file into flashtool then enter flashtool when it prompts you

gregbradley said:
yes, and actually try to flash something before you enter flashmode...drop the ftf file into flashtool then enter flashtool when it prompts you
Click to expand...
Click to collapse
Ok, i will.....
I hope so, will be alright.

Hello Sir, I have a question regarding root.
Is it possible to make root this way:
(locked bootloader)
1) Latest firmware .195 (no root).
2) Flash down to .303 kernel+loader.sin with flashtool (from a ftf)
3) Make root with Bin4ary
4) Flash the .195 kernel+loader.sin with flashtools (from a ftf)
5) Ready?
I am new here on this forum, before I was Arc-boy.

datagubben said:
Hello Sir, I have a question regarding root.
Is it possible to make root this way:
(locked bootloader)
1) Latest firmware .195 (no root).
2) Flash down to .303 kernel+loader.sin with flashtool (from a ftf)
3) Make root with Bin4ary
4) Flash the .195 kernel+loader.sin with flashtools (from a ftf)
5) Ready?
I am new here on this forum, before I was Arc-boy.
Click to expand...
Click to collapse
I dont think so, I think you need to flash the whole 303 firmware. There are plenty of guides in the general section and none of them involve just flashing the kernel.

[Q] Stuck in bootloop (Free Xperia), cannot connect with ADB nor mount via recovery

So I followed the steps very carefully how to install Free Xperia on my Z1. When I booted up my phone in fastboot mode, LED turned blue and I got a new device on my computer under the name "Sony Fastboot Interface" (I believe I got it from Flashtool). I couldn't see my phone in "adb devices", the list was empty. However, I could still do a "fastboot flash boot.img" using the Free Xperia's boot.img. I rebooted using "fastboot reboot" and I was suddenly stuck in an endless loop of the "Free Xperia" boot screen.
So I tried adding another boot.img (Doomlord's "Advanced Stock Kernel with CWM Recovery.zip"). At least I got back the SONY boot screen, but I am still stuck in a loop. I went to the CWM Recovery menu and tried to mount the sdcard to my computer but with no success. I looked under Device Manager on my computer to check if the phone was detected, and frankly it is. However, it shows "Xperia Z1" with a yellow triangle stating "The drivers for this device are not installed. (Code 28)". No matter if I try to uninstall/update drivers or download the official Xperia Z1 drivers and point it to that, I get the message "Windows could not find driver software for your device." So I cannot connect my phone storage to my computer, can't access the phone via ADB, nor can I use fastboot boot a working boot.img.
I searched around on Google and found a solution using EMMA (Sony's own Flash Tool for Xperia devices). But I needed to register an account, and after doing so I never get a confirmation email to activate my account. So I'm stuck where I am. What to do now?
I'm not even sure if my phone is unlocked yet or not. I did the "fastboot.exe -i 0x0fce oem unlock 0xKEY" (with my own key I got in the mail from Sony's generator) and it said "OKAY [ 21.790s]" etc. I presumed that it got unlocked by then. Right?
Thanks in advance!

Well, if you followed all the steps on the sony site to get unlock bootloader then it should be unlocked. Cm roms don't work with stock kernels so flashing the advanced stock kernel will not help anything. When you're connected in fastboot mode, you use "fastboot devices" to see the list of device not "adb devices". Since you can get into fastboot mode then get into flash mode and flash a stock ftf with flashtool. Before doing that, try flashing pimped kernel and see if that works
What version of fxp did you flash btw?

Ahki767 said:
Well, if you followed all the steps on the sony site to get unlock bootloader then it should be unlocked. Cm roms don't work with stock kernels so flashing the advanced stock kernel will not help anything. When you're connected in fastboot mode, you use "fastboot devices" to see the list of device not "adb devices". Since you can get into fastboot mode then get into flash mode and flash a stock ftf with flashtool. Before doing that, try flashing pimped kernel and see if that works
What version of fxp did you flash btw?
Click to expand...
Click to collapse
Thanks for the answer. I was able to revert to stock FTF by following your advice.
I used the fxp honami. Latest CM11 (FXP320-cm-11-20140518-UNOFFICIAL-honami.zip). This was correct right? My phone is a C6903.
I don't understand how to proceed now though. You said I should try flashing a pimped kernel. I looked around and I'm so confused by how many pimped kernels there are, and I'm not exactly sure what a pimped kernel actually is. I need to find the right one specific to my firmware version? It's 14.3.A.0.757 for your info.
Thanks for your help!

bladefinor said:
Thanks for the answer. I was able to revert to stock FTF by following your advice.
I used the fxp honami. Latest CM11 (FXP320-cm-11-20140518-UNOFFICIAL-honami.zip). This was correct right? My phone is a C6903.
I don't understand how to proceed now though. You said I should try flashing a pimped kernel. I looked around and I'm so confused by how many pimped kernels there are, and I'm not exactly sure what a pimped kernel actually is. I need to find the right one specific to my firmware version? It's 14.3.A.0.757 for your info.
Thanks for your help!
Click to expand...
Click to collapse
Sounds like the latest one so that should be right.
Okay do you have root on .757?? If not, flash doomkernel or the advanced stock kernel to get working root and recovery on stock. And since you weren't sure if your bootloader is unlocked, make sure you double check on that before attempting to reflash fxp cm. I'm sure you know the steps to flash but I'll write it down anyways. Put the rom.zip onto your sdcard, get into your choice of recovery, wipe data factory reset, format /system, flash zip from sdcard. If it still doesn't work for you, try official cm builds instead
There's only one pimped kernel. It's a cm based kernel so don't run it on stock roms or you'll end up in bootloops again

Ahki767 said:
Sounds like the latest one so that should be right.
Okay do you have root on .757?? If not, flash doomkernel or the advanced stock kernel to get working root and recovery on stock. And since you weren't sure if your bootloader is unlocked, make sure you double check on that before attempting to reflash fxp cm. I'm sure you know the steps to flash but I'll write it down anyways. Put the rom.zip onto your sdcard, get into your choice of recovery, wipe data factory reset, format /system, flash zip from sdcard. If it still doesn't work for you, try official cm builds instead
There's only one pimped kernel. It's a cm based kernel so don't run it on stock roms or you'll end up in bootloops again
Click to expand...
Click to collapse
I do not have root on my .757. It's completely "stock" so to speak, besides the unlocked bootloader (if it is unlocked, I'm not quite sure). How do I check to see if it's unlocked or not? How exactly do you root? I thought I had found a "ROM" of choice (http://forum.xda-developers.com/showthread.php?t=2711982). But then I saw the prerequisites, that it already needed to be rooted to proceed. I've been looking for straight forward guides, but they all just complicate things with alternatives ways etc.
Which ROM would you recommend?
EDIT: I was able to check the phone's bootloader mode via Sony Mobile Flasher. It's unlocked. However, now I'm trying to enter Recover mode again but now since the phone boots correctly again, I never get any pink LED light or anything. No light, it just boots with the Sony/Xperia splash screen logos.

If you do not know if its unlocked then it is not unlocked.
Flash a stock FTF and spend a week or so reading up
You are lucky you have not bricked your phone...just flashing stuff with no idea what you are doing...

gregbradley said:
If you do not know if its unlocked then it is not unlocked.
Flash a stock FTF and spend a week or so reading up
You are lucky you have not bricked your phone...just flashing stuff with no idea what you are doing...
Click to expand...
Click to collapse
It's alright. I had it checked and it was unlocked. I just got the phone rooted now. It was fairly easy now when I had proper instructions...
Thanks for the help Ahki767!!
I still have one question remaining though... I cannot get Recovery mode to mount storage. Windows recognizes the device, but shows a yellow triangle:
i.imgur.com/so2idLB.jpg (apparently I cannot send links as a new member)
I tried selecting the official Xperia Z1 drivers downloaded from Sony's website. Got the message: "Windows could not find driver software for your device...". I also get the same message when searching the Internet. This prevents me from accessing the sdcard via Recovery mode.
Plus, I tried going into ADB sideload, and when doing the command: "adb devices", I get an empty list of devices. It doesn't say anything about not finding any devices, it's just empty underneath "List of devices attached".

[Q] Telstra Branded Z1 problems :/

Firstly I rooted the phone by downgrading it unlocking bootloader etc. then upgraded to a newer firmware. I then went back to root it again, and tried to then install iHackers v 4.1
It seemed to have installed, but no matter what kernel i use for it, something has been wrong, either the IMEI get cleared from the phone, or it wont boot at all and wont even let me enter any of the recoveries apart from twrp. my flashtool throws this error every time i try to flash certain ftfs
Code:
05/021/2014 03:21:37 - INFO - Preparing files for flashing
05/021/2014 03:21:38 - ERROR - 1
05/021/2014 03:21:38 - INFO - Cannot open bundle. Flash operation canceled
I just want to be able to run the newest clean android rom (aosp style), or closest thing to (with sony apps) which iHackers seemed to be able to provide, or cyanogenmod.
Could someone please tell me how to go about doing what is required, from beginning (as the phone was bought) to end (rooted cyanogen or something of the sort), because im just getting more and more annoyed haha, this phone is nothing like my old htc wildfire and htc velocity :/

If you have unlocked the bootloader then
1) download the update.zip of the rom you want to flash
2) extract boot.img and flash it
3) Enter recovery and flash the update.zip
4) follow any other rom specific install instructions you will find on the OP
EDIT
error 1 on flashtool means you need to upgrade flashtool

gregbradley said:
If you have unlocked the bootloader then
1) download the update.zip of the rom you want to flash
2) extract boot.img and flash it
3) Enter recovery and flash the update.zip
4) follow any other rom specific install instructions you will find on the OP
EDIT
error 1 on flashtool means you need to upgrade flashtool
Click to expand...
Click to collapse
I've tried those things, but ill do it all again.
I've tried the newest version of flashtool, older versions, and im finally trying 0.9.15.0 because that is what another post said had to be used for the bootbundle. Ehm who knows. I guess i'll just keep trying till its all working good. Telstra finally updated to .757 yesterday, and im downloading it right now to test if thats going to be any better than what it has been so far.

Tradie said:
I've tried those things, but ill do it all again.
I've tried the newest version of flashtool, older versions, and im finally trying 0.9.15.0 because that is what another post said had to be used for the bootbundle. Ehm who knows. I guess i'll just keep trying till its all working good. Telstra finally updated to .757 yesterday, and im downloading it right now to test if thats going to be any better than what it has been so far.
Click to expand...
Click to collapse
use the latest version 0.9.16.0
Why are you flashing a FTF? I never said to do that, flash the boot.img extracted from the update.zip using fastboot

So I finally ended up with rooted .757 and tried to install ihackers by fastboot flashing the boot.img then booting to recovery (Philz) and installing the aroma version. it failed miserably by going into a boot loop at the boot logo.
I'm currently working my way back to rooted .757 because i forgot to make a backup -_- stupid I know but I was tired and keen to try iHackers.
What could I be doing wrong?

Darkfleet said:
What could I be doing wrong?
Click to expand...
Click to collapse
We don't know, probably wrong sequence or you skipped a step or even rebooted when you shouldn't. Just repeat all the steps and follow the instructions, if you do that there will be no problem at all.

Problems with flashing / rooting

Hello,
english powered by google
I desperately my Xperia SP on Android is trying to switch 4.4. Unfortunately, most Totourials are useless, alone because very often missing files or they are just out of date.
After so many problems I managed to flash my Xperia. Unfortunately nothing had the desired effect due to the files.
Currently I have the following problem which I do not get resolved:
I have loaded with the Flash tool the Cyanogenmod bootfile via fastboot, earlier I had installed CWM course with USB debugging and deactivated Bootlock. ect.
Unfortunately, he did not start the CWM but the CyanogenMod and I did not have the possibility to install the ZIP file on the SD card. Instead, I've obviously just all deleted.
Currently I have no system, but only the CyanogenMod. A flash on Standart is suddenly no longer possible FAILED (remote: Download size too large). Even when I extracted the System.sin I had problems to start them in fastboot mode.
I had previously done with older files, unfortunately the installation was on the ZIP file in recovery mode error. Why I have updated the files and all programs.
Restoring the standard firmware previously ran flawlessly ...
So I really do not go on and am really desperate.
I very much hope that my one helps the more clueless than me.
Best regards,
Ben

So i assume you now have installed official sony firmware? If yes , and you have unlocked bootloader then all you have to do is install twrp recovery(TWRP recovery for Xperia SP), then download Custom rom(i.e Cyanogenmod-Cyanogenmod builds for Xperia SP), if you like also google apps(OpenGapps) and install trough recovery. It might seem difficult, i know i did not explain it very good but its late... If you have any question or you want me to write a tutorial how to install cyanogenmod step by step just tell me.
Edit: even if you cant access the system it will be easy to install cyanogenmod

Problem Solved:
Flashtool was the Problem. I used the newest Version. After a Downgrade to 9.8.16 it worked.
Thank You very much

Stuck in bootloop after trying to flash TWRP

SOLVED - See second post
-----------------------------------------
Hi there, I'm big trouble.
I have a F8131 with unlocked bootloader. The system was on the latest Oreo.
I tried to flash the latest TWRP using flashtool. After it finished, I get a bootloop, which goes through the unlocked warning to the Sony screen again and again.
What should I do now? Thanks to you all for helping in any way possible!
EDIT: I reflashed TWRP from command line using flashboot and now I can get to TWRP, but now it tells me there is no OS installed (WTF?), so if reboot I go back to the bootloop. Should I try to flash a rom from TWRP, is there something I am missing?

Luckily I was able to solve the issue. I will leave this here in case someone is stuck in the same situation.
1) Use Flashtool in flashmode to flash the FTF firmware you get from XperiFirm into the phone. If you get an error related to drivers, use the Flashtool drivers tool (located in a subfolder in the Flashtool installation folder) to install a set of working drivers (also applies to flashboot drivers).
2) After flashing, disconnect the phone and reconnect it in flashboot mode. Flash TWRP through fastboot commands in a cmd terminal. Flash a boot.img if you have one.
3) This should work, and you should be able to continue to boot your phone or get into TWRP to flash custom packages (Safety, DRM fixes, Magisk, etc) or ROMs.

leandrox said:
Luckily I was able to solve the issue. I will leave this here in case someone is stuck in the same situation.
1) Use Flashtool in flashmode to flash the FTF firmware you get from XperiFirm into the phone. If you get an error related to drivers, use the Flashtool drivers tool (located in a subfolder in the Flashtool installation folder) to install a set of working drivers (also applies to flashboot drivers).
2) After flashing, disconnect the phone and reconnect it in flashboot mode. Flash TWRP through fastboot commands in a cmd terminal. Flash a boot.img if you have one.
3) This should work, and you should be able to continue to boot your phone or get into TWRP to flash custom packages (Safety, DRM fixes, Magisk, etc) or ROMs.
Click to expand...
Click to collapse
um, i need assistance with this
can you help me with it?

velva said:
um, i need assistance with this
can you help me with it?
Click to expand...
Click to collapse
Sure. Where are you at right now?

leandrox said:
Sure. Where are you at right now?
Click to expand...
Click to collapse
About drm fix, is it the same file all phone could use? Or is it special, like TA images? I walk around xda, and somehow i am still not understand.

hasbyduryea said:
About drm fix, is it the same file all phone could use? Or is it special, like TA images? I walk around xda, and somehow i am still not understand.
Click to expand...
Click to collapse
I used the one available at posts with tutorials for installing Kernel + TWRP + Roms for my device. I am not sure whether the drmfix is the same for all Sony Xperia devices.
Nevertheless, I don't think it worked for me, as my keys don't look like they have been recovered when I check them. I haven't noticed any problems so far, though, so maybe it's not a big deal.