This is my first tutorial for installing Cyanogen Mod 7.2.0 on Live With Walkman WT19i. All credit goes to the developers who made all the following and related tools. I simply put together info from various sources. Admins/moderators are welcome to make any changes.
WARNING: Proceed at your own risk! I am not responsible for bricked phones! You might want to do some more research if you're unsure or don't fully understand anything from below
Requirements: ADB drivers:
http://www.mediafire.com/?6u1zl54w3jnvvax
Fastboot drivers:
win_usb.inf file from http://unlockbootloader.sonymobile.com/instructions
Android SDK(unlocking bootloader):
http://developer.android.com/sdk/
Flashtool(flashing kernel):
http://forum.xda-developers.com/showthread.php?t=1351309
Zergrush(for rooting):
http://forum.xda-developers.com/attachment.php?attachmentid=784296&stc=1&d=1321435888
Clockworkmod Recovery(flashing ROM):
http://www.mediafire.com/?73xv18tht0e8zt4
WT19i_4.0.2.A.0.58 firmware:
NOTE:Enable "USB DEBUGGING" from Menu -> Settings -> Applications -> Development
>Enable "UNKNOWN SOURCES" from Menu -> Settings -> Applications
1) If you're already on official ICS, downgrade to Gingerbread, root Gingerbread and then install other custom ROMs as follows:
2) Flash any Android 2.3.4 firmware (I've tried this method only with the WT19i_4.0.2.A.0.58 firmware though) using Flashtool
->Select Flashmode, Wipe data, Wipe cache
3) Use Zergrush v3 by DoomLord. Works well with 0.58 version
If Superuser app has been installed, rooting is successful.
4) Install ClockWorkMod Recovery 5.0.2.7-nAa-r2(Ported by [email protected])
5) Make a backup in recovery mode. (see below for howto)
6) Install Android SDK Manager
If Google USB Driver is not visible, install Android SDK Tools Rev 20 first, reopen SDK Manager.
Replace android_winusb.inf-file in extras\google\usb_driver folder with the new one on http://unlockbootloader.sonymobile.com/instructions
7) Unlock bootloader officially from: http://unlockbootloader.sonymobile.com/instructions
Instructions on that page are pretty clear.
NOTE: Unlocking the bootloader the official way will void your phone's warranty and DRM keys will be lost. You may want to use the testpoint method as mentioned here:
http://forum.xda-developers.com/showthread.php?t=1285285
8) Download Cyanogenmod 7.2 for WT19i (=coconut version) and place it on your SD card.
9) Ensure that the fastboot drivers are installed.
10) Replace stock kernel : Extract boot.img from the Cyanogenmmod 7.2 ZIP file that you downloaded. Now, in Flashtool, select Flash button > Fastboot mode > Select kernel to Flash > Point it to the boot.img file you extracted. Check log in background window for success.
11) Restart the phone into Recovery. Select Wipe data/factory reset followed by Wipe cache partition followed by Advanced>Wipe Dalvik cache.
Then, install zip from sdcard. Select the coconut 7.2.0. ZIP file you placed here earlier.
Wait for about 5-10 minutes. If you're worried, open Command Prompt, navigate to the fastboot folder and run adb logcat to see what's happening!.
And that's it, you're done!
(If the logging process looks like it's repeating itself for more than 10 minutes, remove battery restart phone, and see if Cyanogenmod now boots up(again, will take ~5 minutes). If it does not still boot(rare case), repeat step 10. Make sure you download the CM ZIP package from your computer)
If you get an 'assert' error (Status 7 error) then, edit the file updater-script in your cm7.2.0 ZIP file\META-INF\com\google\android\. Remove only the first line (ending with a . Now repeat step 10 again.
Extra: To use Google services, you need to flash the gapps.zip similar to the way you did CM 7.2. However, do NOT wipe cache do NOT wipe data or anything! To install, simply boot into recovery, install zip from sd card and choose the gapps ZIP file. Later, Restart phone
How to enter recovery mode on the WT19i:
Turn off phone. Turn it on again. As soon as you see Sony Ericsson logo, keep tapping Volume Down button repeatedly. (Once you are familiar, you'll realize that even 1-2 presses can do the trick)
You do not need to root and install Recovery in the first place, I mean skip steps 3, 4 and 5.
Backup can also be made in the same recovery, which is included with kernel, right before wiping and installing the ROM.
I would just install any Android 2.3.4 firmware, then unlock bootloader, install custom kernel, backup, then wipe, then install.
And if you unlock bootloader officially, then do not forget your phone's warranty will be void and DRM keys lost.
If you succeed with official bootloader unlock, then fastboot drivers are already installed, no need to worry about that
And before ppl go crazy - First boot does take a while, as all the caches need to be recreated.
This tutorial can also work for other custom ROMs aswell, because the process is the same, the only different thing is the kernel and the .zip file.
You do not need to root and install Recovery in the first place, I mean skip steps 3, 4 and 5.
Click to expand...
Click to collapse
Right I meant that to install CWM!
I would just install any Android 2.3.4 firmware, then unlock bootloader, install custom kernel, backup, then wipe, then install.
Click to expand...
Click to collapse
Right except that I had problems with using Zergrush v2 and v4. That's why I thought I'd mention.
If you succeed with official bootloader unlock, then fastboot drivers are already installed, no need to worry about that
Click to expand...
Click to collapse
Yes, but that would entail downloading the android_winusb.inf-file from the mentioned official site, wouldn't it?
And before ppl go crazy - First boot does take a while, as all the caches need to be recreated.
Click to expand...
Click to collapse
Oh, but how common is it for a WT19i to take more than 10 minutes at boot? I did this on two other friends' WT19is; both of them took around 3 minutes. (Obviously i did something wrong the first time on my phone)
Anyhow,thanks for the constructive comments!Editing it accordingly!
blackstallion1234 said:
Right I meant that to install CWM!
Click to expand...
Click to collapse
You do not need CWM in the first place. You can make the full Nandroid backup AFTER flashing custom kernel and BEFORE wiping and installing the ROM.
blackstallion1234 said:
Right except that I had problems with using Zergrush v2 and v4. That's why I thought I'd mention.
Click to expand...
Click to collapse
You don't need root to be honest.
blackstallion1234 said:
Yes, but that would entail downloading the android_winusb.inf-file from the mentioned official site, wouldn't it?
Click to expand...
Click to collapse
What's your point? If you unlock the bootloader official way and it succeeds, you do not have to deal with the drivers anymore, as they have been installed properly and they're working
blackstallion1234 said:
Oh, but how common is it for a WT19i to take more than 10 minutes at boot? I did this on two other friends' WT19is; both of them took around 3 minutes. (Obviously i did something wrong the first time on my phone)
Click to expand...
Click to collapse
I didn't mention about minutes. Some ppl are not aware of that, so it was just a small note for them.
You do not need CWM in the first place. You can make the full Nandroid backup AFTER flashing custom kernel and BEFORE wiping and installing the ROM.
Click to expand...
Click to collapse
Right! The custom kernel would provide a recovery (which isn't present on a stock kernel for our phone), right?
You don't need root to be honest.
Click to expand...
Click to collapse
I shall edit the title to something like 'Root and install CM...' where I express the opinion that rooting does have advantages too!
blackstallion1234 said:
Right! The custom kernel would provide a recovery (which isn't present on a stock kernel for our phone), right?
Click to expand...
Click to collapse
Custom kernels already include recovery and stuff needed for root.
blackstallion1234 said:
I shall edit the title to something like 'Root and install CM...' where I express the opinion that rooting does have advantages too!
Click to expand...
Click to collapse
Rooting is already included in custom ROMs, if not then custom kernel does the job and roots it automatically. You don't need to root it by yourself
didn anyone tried latest nightly
There is a stable rom for LWW listed on the cyanogen mod downloads page. Is it really stable? I'm asking this because when you select 'all' and 'stable' on left panel on that site, there is no stable rom listed for lww! This is very confusing.
hsrbnr said:
There is a stable rom for LWW listed on the cyanogen mod downloads page. Is it really stable? I'm asking this because when you select 'all' and 'stable' on left panel on that site, there is no stable rom listed for lww! This is very confusing.
Click to expand...
Click to collapse
Yes the version of CyanogenMod 7.2.0 listed on their site is stable and indeed the one used in this thread for reference. Click coconut in the left hand pane(that's the codename for LWW) and then selecting stable. (Alternately just go to http://get.cm/?device=coconut&type=stable)
I just installed Cyanogenmod today and it's fantastic!
Do i need to unlock my bootloader?
Hi,
I've rooted my phone (Sony Ericssion Live With Walkman-WT19i) and right now running stock ICS ROM from sony (build: 4.1.B.0.431). Even Clockworld Mod is installed. I want to install custom rom from cyanogenmod(or any other custom rom).
My question is : Do i really need to unlock my bootloader,coz as I know rooting may void the warranty but unlocking the bootloader will surely void it.
Please tell me the detailed process of installing custom rom step by step (right after the successful rooting and installing CWM process). I woould be thankful if u include both the process(with and without unlocking bootloader,if any).
Thank You Very Much In Advance.
Could You please mail me the steps even to my persoanl mail id [email protected]
sauravsagar said:
Hi,
I've rooted my phone (Sony Ericssion Live With Walkman-WT19i) and right now running stock ICS ROM from sony (build: 4.1.B.0.431). Even Clockworld Mod is installed. I want to install custom rom from cyanogenmod(or any other custom rom).
My question is : Do i really need to unlock my bootloader,coz as I know rooting may void the warranty but unlocking the bootloader will surely void it.
Please tell me the detailed process of installing custom rom step by step (right after the successful rooting and installing CWM process). I woould be thankful if u include both the process(with and without unlocking bootloader,if any).
Thank You Very Much In Advance.
Could You please mail me the steps even to my persoanl mail id [email protected]
Click to expand...
Click to collapse
You can't install CM with locked bootloader it requires different kernel.
Yes you need to, for CM!
sauravsagar said:
I want to install custom rom from cyanogenmod(or any other custom rom).
My question is : Do i really need to unlock my bootloader,coz as I know rooting may void the warranty but unlocking the bootloader will surely void it.
Click to expand...
Click to collapse
Yes, most custom ROMs need the bootloader to be unlocked(including CyanogenMod). There are two methods to unlock your bootloader - the test point method and the official method. If you're concerned with your warranty(which may already have been voided), use the Test point method described in the FAQ by Someguyfromhell.
And what ^ said.
Please tell me the detailed process of installing custom rom step by step (right after the successful rooting and installing CWM process). I woould be thankful if u include both the process(with and without unlocking bootloader,if any).
Thank You Very Much In Advance.
Click to expand...
Click to collapse
If only people read FAQs on forums...
thanx a million
thanks a million for the tutorial
this thing rocks
i do love this rom
and most nice thing it dose support ad-hoc
wathbiknight said:
thanks a million for the tutorial
this thing rocks
i do love this rom
and most nice thing it dose support ad-hoc
Click to expand...
Click to collapse
Glad it worked for you! Not to be a thanks-whore, but it's just a click away if I really helped ya!
Cheers!
Might be a foolish question but I flashed some custom firmware on my Samsung Star (not Android) back in the days and only had the English language available instead of the Dutch I wanted.
If I root and install the ROM will everything also be available in English only or will I still be able to use Dutch. Will I lose something?
Another question: If I upgrade to ICS official by Sony trough Sony Bridge on my Mac and ICS is installed on my phone, will I lose data and the root and ROM?
Thanks in advance
zeromusx said:
If I root and install the ROM will everything also be available in English only or will I still be able to use Dutch. Will I lose something?
Click to expand...
Click to collapse
That depends on whether the new ROM you're flashing contains a Dutch language pack. Rooting per se will not modify your data or your language. Also note that flashing can erase your internal memory data.(I have no experience with the Star, however I had a Nokia 3500c. Using the official Nokia app, I upgraded my firmware without any data loss. If you will be using the official Samsung app, you should be safe). That said, make it a point to backup your SMSes, contacts, calendars, notes etc.
Another question: If I upgrade to ICS official by Sony trough Sony Bridge on my Mac and ICS is installed on my phone, will I lose data and the root and ROM?
Click to expand...
Click to collapse
Will I lose root? Yes, you will most likely lose existing root permissions if you already are rooted.
Will I lose data? Unlikely, using Sony Bridge.
Will I lose ROM? Of course, that's the reason you're upgrading to ICS in the first place, isn't it?
Have a look at the following resources and any other places you'll stumble across.
http://forum.xda-developers.com/showthread.php?t=1253127,
http://www.techcredo.com/android/android-rom-and-rooting-dictionary-all-the-funny-words-explained
Good luck!
Installed Cyanogen Mod 9 in my Live with walkman. So far So good!
rolo143 said:
I just installed Cyanogenmod today and it's fantastic!
Click to expand...
Click to collapse
Sir can you show us some screenshots?
thanks again
blackstallion1234 said:
Glad it worked for you! Not to be a thanks-whore, but it's just a click away if I really helped ya!
Cheers!
Click to expand...
Click to collapse
my bad
i thought i did click it earlier , but did today
i'll come back for ROM review later
Related
Before I begin, Mods, PLEASE pin this. I (when I was a noob) had absolute difficulty installing ROMs. This is very noob-friendly, fixes Status 7 errors, and is easy to follow.
Alright friends and future flashers. I used to have difficulty installing ROMs. Now that I know how (after going through numerous tutorials), I'd like to make it easy for ALL of you. Enjoy your Custom ROM!
Before beginning, you need Android's SDK,Flashtool and The latest Official firmware.
If ever your phone needs to install drivers, let it install, don't unplug the phone or whatever.
And, battery at least 30%. Mine does it at even 20% without issues, but just to be safe.
Step 1: Revert to Stock
You don't need to downgrade. After flashing the latest stock kernel, I have flashed every single GB and ICS ROM in existence without issues, so you don't need to flash a specific one. But, latest one tends to be more stable. Here's what you do:
Get the latest Global ftf for your phone. Then, flash it using Flashtool. I won't go into specifics, but PM me if needed
By Now, you should have a stock EVERYTHING. Boot up the phone, run through the whole set up process. Once you are done, you need to get your IMEI number. Do this by following the steps here.
In the end, you should have the bootloader unlocked. If you come up with something like bootloader already unlocked, then you are good to go. Now onto......
Step 2: Preparing your Flash.
Download the ROM of your choice. I'd recommend FXP's Unofficial CyanogenMod9 as it has the best stability and no ICS Multitouch issues. If it is GB, any ROM will do. Most of them are stable.
Now, in the case of CyanogenMod, they often come with their own custom Kernel. It is in the zip file, known as boot.img, and you simply extract it to your platform-tools folder in the android-sdk folder you downloaded to unlock the bootloader. This is also true for some MIUI ROMs I've come across. Read their forum posts for more info on which kernel to use.
Copy the ZIP file to your sdcard. It does not have to be the root of SDcard, anywhere will do.
By the end, your Custom ROM's ZIP file will be in your SDCard, and the kernel file (a.k.a. boot.img or whatever_the _kernel_name_is.img) will be here:
32bit Windows: C:/Program Files/Android/android-sdk/platform-tools
64bit Windows: C:/Program Files(x86)/Android/android-sdk/platform-tools
Now we can
Step 3: Flash your Custom ROM
In the folder above (depending on OS version) press Shift+RightClick. Options will show up. Select "Open Command Prompt Here". A Command Prompt will open (duh).
Turn off your phone. Wait 10 seconds. While plugging in your phone, press the Menu button (the Right button). The LED Indicator should turn blue. This shows your in fastboot mode. If it starts to boot, rip out the battery and try again. DON'T STOP PRESSING UNTIL IT TURNS BLUE.
Now, type EXACTLY AS FOLLOWS, ONE AT A TIME. Just type in the lines with the "-" before it, but don't put in the "-" when typing it. The line underneath in brackets is an explanation, so you understand what is happening.
-fastboot devices
(This is actually a quick test I do to see if my phone is connected in flash mode or not. If nothing happens, it is not in flash mode or the drivers are installing)
-fastboot flash boot boot.img
(This is telling fastboot to FLASH the BOOT partition of your phone with the file specified. If you are using a different kernel, simply replace boot.img with the name of the kernel, ending with .img and wait for it to finish. Won't take long)
-fastboot reboot
(This causes the phone to reboot)
Now, while it is starting up, keep repeatedly pressing the Volume Down button until you are in ClockWorkMod Recovery (Assuming you are using it. CWM is the most popular and most kernels use it) Then, If you choose to, make a backup. I personally don't, as it is not too big an issue and I never revert to an old ROM anyway.
After that, choose Factory Reset. This will remove ALL data in your phone except your Stock ROM. Then, Clear Cache. You might've noticed it already did that when you Factory Reset, but this is for safety. Finally, in advanced, Wipe Dalvik-Cache and Wipe Battery Stats. I do this all the time for safety.
Now, the fun bit. GO to Install ZIP from SDCard. Select Choose ZIP, find your ROMs ZIP file, and install. It might take awhile, but not too long. Just be patient. When it finishes, flash anything else the ROMs forum post says to flash (Gapps, Patch, etc) and select Reboot Phone.
Step 4: Done!
Your phone will start up. First time is always slow, but this WILL WORK. Congratulations. You now have a Custom ROM
If you get a Status 7 error while flashing a ROM, reboot recovery and wipe everything again. If that doesn't work, flash official firmware and try again.
Credits to:
-Google: Providing Android SDK and Gapps
-Androxyde: Flashtool
-Madfysh: List of Official ICS ROMs
FXP: Creating CyanagonMod9
-And YOU!
P.S.: If you're confused, or feel this could use something extra PM me.
And uh, if it needs to be moved, please do so. Thanks!
I do know there is THIS but I felt some of his steps were unnecessary. Example, rooting. Any custom ROM will be rooted, so there will be no need to worry about that. And he also provided overclocking tips and an unofficial bootloader unlock which are hazardous and potentially permadamaging to the phone.
PLEASE Don't spoil the mood man!!
This is a development section where even Noob Devs know how to flash a Custom Rom!! PLeaseee Pleaseeee ... Move it
Alright man. How would I move it? Cause, I only RECENTLY started being active on the forums.
Jass5991 said:
I do know there is THIS but I felt some of his steps were unnecessary. Example, rooting. Any custom ROM will be rooted, so there will be no need to worry about that. And he also provided overclocking tips and an unofficial bootloader unlock which are hazardous and potentially permadamaging to the phone.
Click to expand...
Click to collapse
Don't say that thread is unnecessary; they put everything in one thread cause it's easy to find. the first step we should do is rooting if we are noops. Then we will be curious about unlock or custom rom later.
Sent from Xperia Neo using AOKP B40
Still dev thread so if you don't know how you should not be trying
It goes like this no dl link no thread
but still is a good post
some unnecessary parts
some dodgy parts
But good for noob never-ending Questions
Maybe Q&A
Reck1993 said:
Don't say that thread is unnecessary; they put everything in one thread cause it's easy to find. the first step we should do is rooting if we are noops. Then we will be curious about unlock or custom rom later.
Sent from Xperia Neo using AOKP B40
Click to expand...
Click to collapse
Okay. I will add an easy rooting instructions to it.
kormatoes said:
Still dev thread so if you don't know how you should not be trying
It goes like this no dl link no thread
but still is a good post
some unnecessary parts
some dodgy parts
But good for noob never-ending Questions
Maybe Q&A
Click to expand...
Click to collapse
Thanks kormatoes. Could you gimme some of the unnecessary/dodgy parts?
Jass5991 said:
I do know there is THIS but I felt some of his steps were unnecessary. Example, rooting. Any custom ROM will be rooted, so there will be no need to worry about that. And he also provided overclocking tips and an unofficial bootloader unlock which are hazardous and potentially permadamaging to the phone.
Click to expand...
Click to collapse
1) actually that(which you linked) tutorial is good, it just need some updating. but your tutorial is different than that.
2) root is certainly not unnecessary! not all people will go for custom roms, specially as most of them are for unlocked BL.
3) unofficial unlock is not hazardous, it is tricky, but it paid of if we look on the advantage against official unlock
Nice from you that you wrote all this, it's based only for custom roms's, thread which is already sticked is for basic things, which any noob should know.
But still, this looks kinda cluttered, and from noob(which you intend this to) point of view, to long/complicate to read
Madfysh said:
1) actually that(which you linked) tutorial is good, it just need some updating. but your tutorial is different than that.
2) root is certainly not unnecessary! not all people will go for custom roms, specially as most of them are for unlocked BL.
3) unofficial unlock is not hazardous, it is tricky, but it paid of if we look on the advantage against official unlock
Nice from you that you wrote all this, it's based only for custom roms's, thread which is already sticked is for basic things, which any noob should know.
But still, this looks kinda cluttered, and from noob(which you intend this to) point of view, to long/complicate to read
Click to expand...
Click to collapse
Thank you all big guns
but there should be a start-up kit for newbie
There can be a Starter Section with due permission
lalit387 said:
Thank you all big guns
but there should be a start-up kit for newbie
There can be a Starter Section with due permission
Click to expand...
Click to collapse
As it is, I am attempting to code a batch file to automatically run the entire flashing process, including kernel and ROM. Having a small issue where it does not wipe dalvik and cache. It also doesn't flash the custom ROM
Tutorial. Bootloader unlocked. Install ClockWorkMod, Kernel and ROM
Before Flashing a Custom Kernel. You have to have your bootloader unlocked.
To Unlock Bootloader follow this link http://forum.xda-developers.com/showthread.php?t=1730874
"This tutorial is for people who just bought a cell phone and want to customize, but afraid to make any modification other than Workshops.
All I'll be teaching procedures have been tested by me (Xperia Live With Walkman Wt19a) remembering that this tutorial can also be applied to other devices on the same line, but the person is aware of everything you're doing.."
Ok So we go to our interest.
It is recommend to have the Pc and Compani SUS for any drivers.
I will describe in steps. "Before you do anything BATTERY MUST BE 100% LOAD"
1º. You need to have CWM "ClockworkMod" To do a FULL BACKUP which TER is EXTREMELY IMPORTANT. If you can not install the CWM, progress is TOTALLY PUT IN YOUR OWN RISK. (OK JA ADVISED THIS).
2º.Download CWM-Install here is the link: http://www.4shared.com/rar/qZQbLbdc/CWM-Install.html?
3º. After completing the download extract to a folder.
4º.1. Run install-cwm '. Cmd
install-cmw1.cmd - Xperia Arc / Neo
install-cmw2.cmd - Xperia Mini / MiniPro / Active / Live With Walkman
2.Enable USB Debugging on device
3.Connect your device using usb data cable
4.Follow on screen instruction
5º. Once that's done you should have already installed the CWM ClockworkMod then we will open it when you boot the phone. (When the phone shine brighter or some flashing LED FINGER TIGHT TO KEEP THE VOLUME DOWN BUTTON AND HOLD briefly) This should open the recovery console CWM.
6º. Now with the volume knob go to Backup / Restore. Hold down the middle button to enter the option. (Choose Backup) just wait a bit and BACKUP YOUR READY NOW IS READY.
7º. Restart the phone.
8º. Now a lot of attention. We will install the kernel. First of all you need to have the drivers installed ADB; So here's the link: http://www.4shared.com/zip/2KEB9taN/Android_ADB_Interface.html
9º. Now plug the phone into fastboot MODE. is vol + and connect usb cable. Blue LED must be connected. Once that's done your computer will start looking for drivers and will not find ... Then Extract the ADB drivers into a Folder and indicate to the drivers downloaded. This should work. If you are having trouble installing the drivers ADB. I recommend you download a program called Driver Identifier. To locate the driver.
10º. Now with the drivers already instaldos We Correctly Download the program called Flash Tools.
11º. Open the program Flash Tools. After clicking on the radius and choose MODE Fastboot. Not FlashBoot NOT CONFUSE. Leave the phone connected in mass storage mode. Now in clice Reboot into fastboot mode (via Fastboot) Note If you want to connect in Manual mode Fastboot can be connected normally.
12º. Now comes the most decisive moment of all :victory: ... You sure which kernel will apply. For if you apply some kernel Wrong at Risk of Damaging the Machine there only using an Advanced Backup has been done to resurrect.
13º. In my case my Mobile Live With WT19 is a Walkman So I will choose the Kernel Kamarush to show in this tutorial. Link to Kernel http://forum.xda-developers.com/showthread.php?t=1709032
TIP. BEFORE YOU HAVE A ROM A CHOICE IN MEMORY CARD. IN MY CASE TO U.S. USING THE LINK REAL ICS V5 http://forum.xda-developers.com/showthread.php?t=1707876:laugh:
14º. In the Flash Tools Click Select Kernel to Flash. Go up the file you Kernel for Low LWW Live With Walkman. Once you have the absolute certainty that the Kernel is right ok just take two clicks and it already in the kernel will install automatic a process is really fast.
15º. Now when the phone started so get in CWM.
16º. Now you need to do a reset FULL. First MAKE TO DO a FACTORY RESET AFTER A WIPE CACHE PARTITION. GO TO ADVANCED TO CHOOSE AND WIPE Dalvik CACHE.
17º. Then come back and go to install zip from sdcard. Choose choose zip from sdcard.
18º. Now go to the folder that has the ROM. done so just follow the installation procedures is an aroma "Do not clear it does not change anything already WT19 is defined as the first. Do not change anything in the options wipe.
19º. Done it now when you return to the CWM modules you need to install the WIFI to work. Link http://www.4shared.com/zip/c3qIfOdP/new_wifi_modules.html?
Installing is the same as the ROM.
20 °. Once that's done just restart your phone and you're ready. Easy Bad is not the only the beginning you have to install the drivers and ADB CWM for even those who do not have.
THIS IS OPTIONAL.
Fix Accelerometer "ICS" http://www.4shared.com/zip/w82KRrKc/Fix_Accelerometer_LWW.html?
To leave after boot a little faster. http://www.4shared.com/zip/zEQNj-ek/SlaidyBoost-B1_SGS_By_Slaid480.html?
Thema Bacana.
http://www.4shared.com/zip/L0cpG0-V/Themes.html?
Done.
After all that, you leave a thank you.
My Device. [email protected] ICS v5
Kernel: Kamarush.
: D
Thanks to all staff of the XDA tutorial that contributes to my being.
.
Go to Post 2
Some add-ons.
To make more custom than it already is....
Notification Bar Transparent icons and more personalized
Apply the first modification; NEW Nice_Notification_Toggles_For_ICS.zip. http://www.mediafire.com/?awjo5isfkb9nmpi
Then disconnect and reconnect the device again in order CWM.
After applying the Second Amendment, with Transparent statusbar toggles.zip http://www.mediafire.com/?h8b64idzy556xd3
Always remember to have backup. causo act done to a problem.
If you're in trouble then refer to our friend who has provided such work
http://forum.xda-developers.com/showthread.php?t=1690037
am I completely blind or there really isn't any disclaimer that you have to unlock your bootloader to flash custom kernels?
can you play deatrigger n real ics
Thanks For the reply.
najodleglejszy said:
am I completely blind or there really isn't any disclaimer that you have to unlock your bootloader to flash custom kernels?
Click to expand...
Click to collapse
I did not add unlocking the bootloader I have not found necessary. Because there are already Topics unlock your bootloader. If you think I need a Tutorial Add active before Unlock this Topic. I do
No Problem for Games
trantiena10 said:
can you play deatrigger n real ics
Click to expand...
Click to collapse
i'm play deadtrigger.
Perfect runs very smooth and no lag. Add active you need a little overclocking can leave with 1600 Max and 1000 Min. From to play hard and not spend so much battery. Optimal Real ICS ROM V5.1. With some Fix
Thanks for this tutorial!
God, i remember when i didn't flash kernel and when i had to do all this **** to be root and have CWM...
sounds good tht TUT
eltonpestana said:
I did not add unlocking the bootloader I have not found necessary. Because there are already Topics unlock your bootloader. If you think I need a Tutorial Add active before Unlock this Topic. I do
Click to expand...
Click to collapse
no need to put the full tutorial, you could just write that before flashing a custom kernel you have to have your bootloader unlocked, and paste the link to this topic: http://forum.xda-developers.com/showthread.php?t=1730874
najodleglejszy said:
no need to put the full tutorial, you could just write that before flashing a custom kernel you have to have your bootloader unlocked, and paste the link to this topic: http://forum.xda-developers.com/showthread.php?t=1730874
Click to expand...
Click to collapse
Thanks for the tip
excuse me,i just bought this phone.i want to do everything i did to my previous xperia:X8.Xperia X8 had a manufacture date problem
does this phone have it too?what is the danger zone?does it exist?
at x8 11w28 or older is hard brick.can this phone be 100% secure unlocked?or is there any risk?please.
shadik555 said:
excuse me,i just bought this phone.i want to do everything i did to my previous xperia:X8.Xperia X8 had a manufacture date problem
does this phone have it too?what is the danger zone?does it exist?
at x8 11w28 or older is hard brick.can this phone be 100% secure unlocked?or is there any risk?please.
Click to expand...
Click to collapse
I have not tested the method of test point, but it seems safe. If the person does not want to risk connecting something wrong. You can try to follow in the footsteps of Sony http://unlockbootloader.sonymobile.com/ according to your model. In my point of view I prefer methadone plus Sony's command in Ms Dos. Regarding the problem of manufacturing data can rest assured that no problems have at least the Sony because methadone is a specific code. Now as to the test point can not guarantee. In my view these quiet line Xperia handsets are very strong. These devices are actually very good.
eltonpestana said:
I have not tested the method of test point, but it seems safe. If the person does not want to risk connecting something wrong. You can try to follow in the footsteps of Sony http://unlockbootloader.sonymobile.com/ according to your model. In my point of view I prefer methadone plus Sony's command in Ms Dos. Regarding the problem of manufacturing data can rest assured that no problems have at least the Sony because methadone is a specific code. Now as to the test point can not guarantee. In my view these quiet line Xperia handsets are very strong. These devices are actually very good.
Click to expand...
Click to collapse
but that way they will know i unlocked my bl and my warranty will be torn.because they know my phones IMEI.they report that to the centers and they know my phone doesnt have warranty even tho i relocked,stock kernel,stock rom,no root
EDIT
and i saw on other thread that i must downgrade to gb to root the phone.is it true?
shadik555 said:
but that way they will know i unlocked my bl and my warranty will be torn.because they know my phones IMEI.they report that to the centers and they know my phone doesnt have warranty even tho i relocked,stock kernel,stock rom,no root
EDIT
and i saw on other thread that i must downgrade to gb to root the phone.is it true?
Click to expand...
Click to collapse
Yes, you can't root your device on ICS directly, you have to downgrade if you don't want to unlock your bootloader. Everything is here: http://forum.xda-developers.com/showthread.php?t=1695514
[Q]
shadik555 said:
excuse me,i just bought this phone.i want to do everything i did to my previous xperia:X8.Xperia X8 had a manufacture date problem
does this phone have it too?what is the danger zone?does it exist?
at x8 11w28 or older is hard brick.can this phone be 100% secure unlocked?or is there any risk?please.
Click to expand...
Click to collapse
managed to do what you wished?
real ICS on locked bootloader?
hi all,
my device- sony ericsson wt19i LWW
OS- ICS 4.0.4
build no.- 0.431
root- yes
bootloader- locked.
Is it necessary to unlock bootloader to install CWM?????:silly:
I just want to know If I can install real ICS rom on my fone?
if yes,should I must install some kernel before???
Please help me with this !!!!!
very nice tut tnx! :good:
cool
tany with walkman said:
hi all,
my device- sony ericsson wt19i LWW
OS- ICS 4.0.4
build no.- 0.431
root- yes
bootloader- locked.
Is it necessary to unlock bootloader to install CWM?????:silly:
I just want to know If I can install real ICS rom on my fone?
if yes,should I must install some kernel before???
Please help me with this !!!!!
Click to expand...
Click to collapse
No need to unlock the bootloader to install CWM. However you will not get to modify your kernel. Cause to modify kernel you must have unlocked Bootloader. Installs CWM puts your phone in Debug mode and apply the. Bat according to your device model http://www.4shared.com/rar/qZQbLbdc/CWM-Install.html?
The next step you will have CWM.
Now you want to unlock your bootloader? you must use the means of unlocking the Sony the best way http://unlockbootloader.sonymobile.com/
After unlocking your bootloader. Then everything gets easier. Despois to unlock your bootloader. When you apply the Kernel it will come with CWM already built there then just do a full wipe and then apply the ROM to taste.
update the links above plsss... i want to install custom rom like Real Ics..but i'm not sure what kind of kerner it would fit in my LWW WT19i..can you post the link of the kerner ang Real ICS here so that i can install custom rom..thnx!
Great Tutorial, mate :good:
---------- Post added at 02:46 PM ---------- Previous post was at 02:08 PM ----------
tsunamixtreme said:
update the links above plsss... i want to install custom rom like Real Ics..but i'm not sure what kind of kerner it would fit in my LWW WT19i..can you post the link of the kerner ang Real ICS here so that i can install custom rom..thnx!
Click to expand...
Click to collapse
Maybe this would help you, mate
All Roms and Kernels Sorted & Updated: http://forum.xda-developers.com/showthread.php?t=1887855
--->Real ICS
*Real ICS r5.2: http://forum.xda-developers.com/showthread.php?t=1707876
*Real ICS Lite r4: http://forum.xda-developers.com/showthread.php?t=1739569
--->Kernels
*MESA: http://forum.xda-developers.com/showthread.php?t=1715679
*KRsH: http://forum.xda-developers.com/showthread.php?t=1709032
*KernelPanic: http://forum.xda-developers.com/showthread.php?t=1861905
*Rage: http://forum.xda-developers.com/showthread.php?t=1398910 (Both GB & ICS)
I have no idea what I'm doing so I thought following a step by step guide would help me...but apparently not.
I followed this guide because I wanted this ROM:
http://forum.xda-developers.com/showthread.php?t=1206625
BUT I used xRecovery from here (also I used this guide to get root access):
http://forum.xda-developers.com/showthread.php?t=1682966
I already had the baseband so I didn't do the optional step, but I did download the file after searching the topic for a live link (I wanted all the files I might need before starting so I could focus on the job).
My phone is now in an infinite loop of turning on, saying Sony Ericsson, then shutting down after a minute or so and retrying. I'm not sure what info to provide so I will just list off things I wrote down beforehand:
FIRMWARE: 2.1-UPDATE1
KERNEL: 2.6.29
BUILD: 2.1.1.A.0.6
SI: 1248-0835
I just wanted to let anyone who wants to help know I restored the backup through xRecovery...so it's like I never did anything....but I still really need to get rid of the OS I have and replace it with something clean, preferably what I tried the first time (first link).
next time post questions in X10 mini pro section, This is X10 section.
I dont know much about it but did you unlock your bootloader?
Thread Moved
Please take more care when opening a thread
THeLogiC said:
next time post questions in X10 mini pro section, This is X10 section.
I dont know much about it but did you unlock your bootloader?
Click to expand...
Click to collapse
I'm really sorry, I got lost by accident. I'm not used to this sort of forum .
I did not unlock a bootloader, I will go look at it now, thanks so much!
Alunny said:
I'm really sorry, I got lost by accident. I'm not used to this sort of forum .
I did not unlock a bootloader, I will go look at it now, thanks so much!
Click to expand...
Click to collapse
You don't need to unlock the bootloader becasue you're trying to install a modified stock-rom from SE, which will run on SonyEricsson's stock kernel with no problem.
I hope you did all the wipes in xRecovery?
wipe data/factory reset
wipe cache
Go into advanced menu
wipe dalvik-cache
wipe battery stats
Usually a bootloop on a rom that is proven to work is due to left-over junk in the cache or dalvik-cache. You can do these after you've installed the ROM.
Oh okay. I hadn't unlocked the bootloader and I was having trouble keeping my phone off and connected to my puter so thought I had better leave it for a day when I have time to focus on it. That was the part of rooting I was afraid of.
I did the first two cache but not the other two. Will try again in a few minutes and do those!
Same thing. Think I'm going to have to try the bootloader thing.
Alunny said:
Same thing. Think I'm going to have to try the bootloader thing.
Click to expand...
Click to collapse
If you want that particular ROM there is no need to unlock the bootloader.
It is more dangerous than just rooting your phone and only needed if you need a custom kernel, which you don't for this ROM.
If you have flashtool (you can get it from here if you don't have it)
Make sure USB-debugging is on on your phone
Start flashtool
Connect your phone to your computer
Root it using the ROOT button in flashtool (the button with the lock on it)
Install xRecovery using the button with the cross on it.
Use the menu to boot into xRecovery
Choose Install zip from sd-card (no need to rename the zip this way)
Choose zip from sd-card (it wil show you the content on your sd-card)
Choose your ROM's zip
Choose yes
After the install is done reboot your phone.
If it won't boot the zip-file you downloaded may be corrupted.
You can get back to your original firmware by using Sony Update Service or PC Companion, so your phone will work again.
Just got my sony version - can say this phone is beast mode. There is a pending update to .257 and someone told me that if I update to this, i will be locked out of any ROMs, including any google edition ROM. Can anyone verify this or comment? I have NOT updated to .257 yet.
Thanks in advance.
It's not that dramatic. If you update now, you'll have to downgrade again to 532 if you want to root. You'll need root and Recovery if you want to flash the GPE ROM when it gets released, so you're only saving yourself one step by not updating to 257 now
LordManhattan said:
It's not that dramatic. If you update now, you'll have to downgrade again to 532 if you want to root. You'll need root and Recovery if you want to flash the GPE ROM when it gets released, so you're only saving yourself one step by not updating to 257 now
Click to expand...
Click to collapse
Lord, good to see you again - remember you from the GT-N7000 forum! So since of course I want root, I shouldn't update to .257. Am I understanding this correctly?
LxMxFxD said:
Lord, good to see you again - remember you from the GT-N7000 forum! So since of course I want root, I shouldn't update to .257. Am I understanding this correctly?
Click to expand...
Click to collapse
Correct. There are currently no way to root 257, so we have to root 532 and update through OTA to keep root on 257.
- Use this tool to root
- Install OTA Root Keeper from the Play Store
- Since you've already received the OTA, you don't need to change the CDA in build.prop (to force the OTA), so...
- Update to 257
- The root app (i'm not sure what app it installs) may be gone, so just install SuperSU from the Play Store if it's not in your app drawer.
And you're done...
... unless you also want to unlock the bootloader:
But let's not get ahead of ourselves. You really want to take a backup of your TA partition. It holds all your unique DRM keys, and X-Reality won't work without it. Once you lose it, you can't get it back, so back it up and upload it to your Dropbox or something. So how do you backup your TA partition?
- Download this tiny tool on your computer and run it.
Are you done? Great! Let's move on to the bootloader:
- Go to Sony's dev site
- Request the unlock key and check your mail.
- Install Flashtool on your computer (follow the guide)
- Click the "lightning" icon
- Follow the steps and enter your unlock key
This may wipe your phone, so backup your stuff
And you're done...
... unless you want to install Recovery and TWRP!
Installing Recovery and TWRP is easy. Just run this tool on your computer.
Now you're all set to flash custom ROMs and all that stuff
Lord,
Thanks again. And for anyone googling this thread, you'll need the android SDK to get these scripts running. The android SDK can be downloaded here:
http://developer.android.com/sdk/index.html
Once downloaded and extracted, add it to your environment path.
Actually... You only need ADB and Fastboot. You can install this Windows installer which will do all the work for you. I'm sorry if you installed the entire SDK I should have included it in the guide.
http://forum.xda-developers.com/showthread.php?t=2317790
Sent from my C6833 using Tapatalk
Firmware link (532)
http://forum.xda-developers.com/showthread.php?t=2463701
If the Hong Kong firmware is flashed would the interface be in english?
If not, does anyone have a link to 532 ftf english/international. Thanks.
CptAwesomeTT said:
Firmware link (532)
http://forum.xda-developers.com/showthread.php?t=2463701
If the Hong Kong firmware is flashed would the interface be in english?
If not, does anyone have a link to 532 ftf english/international. Thanks.
Click to expand...
Click to collapse
You can select your language from set up wizard after installing rom. i too downloaded HK fw.
techpal said:
You can select your language from set up wizard after installing rom. i too downloaded HK fw.
Click to expand...
Click to collapse
Thank you very much.
I'm new to Sony flashing. Recently bought a XZU (6833) after learning about GPe release. I havent gotten it as yet but i've spent the last few days reading up on preparing for flashing AOSP roms. I'm still not 100% solid on the steps as information is all over the XZU section, not really organised too well. A lot of the information is out of date and there are many gaps that left me scratching my head...
As far as I can gather, these are the steps a new XZU non GPe edition owner should undergo if they would like to flash GPe roms(or any other)...please correct me if I am wrong.
1) Use flashtool 0.9 to flash older 532 firmware ftf file. (does not require root and can be done on a bone stock device non GPe device regardless of installed firmware version). Link here http://forum.xda-developers.com/showthread.php?t=2463701. Now I know Hong Kong version is ok. 532 is older than 257. 257 cannot be rooted directly hence the need to downgrade first.
2) Root using the Japanese rootkitZ Link: http://forum.xda-developers.com/showthread.php?t=2559009 (I assume this installs Superuser as there is a Superuser APK in the folder)
3) Install root keeper to retain root privilege. https://play.google.com/store/apps/details?id=org.projectvoodoo.otarootkeeper. (temporary, must be kept installed at all times or only after OTA? If not doing OTA to 257, is this even necessary?)
4) Backup TA partition with TA backup tool 9.9 to retain original keys for xreality etc.(must be rooted to do this), If partition isnt backed up, these features would be lost forever. This works only with Sony roms anyway so if you plan on only running GPe roms, this isnt necessary?
5) Unlock bootloader using Sony method. Link:http://unlockbootloader.sonymobile.com/
6) Performing OTA update not manditory if flashing to an AOSP rom anyway? I saw mention of changing some build.prop entries for this to before OTA update shows when you check for updates? Is that necessary? If so, what are the changes?
7) Flash cwm/twrp using xzu recovery 4. Link: http://forum.xda-developers.com/showthread.php?t=2426739. The instructions specify to run superuser.bat or supersu.bat. There is only a run.bat file in the folder and this is what you must run After launching there are several options. (If using the root method from step 2, I assume you have to use the SuperUser (option2) when running the tool).
8) Flash any rom (If going back to a Sony rom, must flash to 532 first to get root. Then update through OTA.
Please can someone edit and/or add details where necessary.
---------- Post added at 03:54 PM ---------- Previous post was at 03:40 PM ----------
LxMxFxD said:
Lord,
Thanks again. And for anyone googling this thread, you'll need the android SDK to get these scripts running. The android SDK can be downloaded here:
http://developer.android.com/sdk/index.html
Once downloaded and extracted, add it to your environment path.
Click to expand...
Click to collapse
To what scripts are you referring? Can you help me by fleshing out my above post?
3) Install root keeper to retain root privilege. https://play.google.com/store/apps/details?id=org.projectvoodoo.otarootkeeper. (temporary, must be kept installed at all times or only after OTA? If not doing OTA to 257, is this even necessary?)
Click to expand...
Click to collapse
If you're not planning on keeping the stock ROM, and you want to jump straight to a custom ROM, then no, it's not necessary to install OTA Root Keeper.
4) Backup TA partition with TA backup tool 9.9 to retain original keys for xreality etc.(must be rooted to do this), If partition isnt backed up, these features would be lost forever. This works only with Sony roms anyway so if you plan on only running GPe roms, this isnt necessary?
Click to expand...
Click to collapse
You don't need to back it up, but it's recommended even if you're going to use custom ROMs. What if you're having some issues with your ZU, and you have to send it in for repairs? Sony will notice if the DRM keys aren't there and they'll then know that you've unlocked the bootloader.
6) Performing OTA update not manditory if flashing to an AOSP rom anyway? I saw mention of changing some build.prop entries for this to before OTA update shows when you check for updates? Is that necessary? If so, what are the changes?
Click to expand...
Click to collapse
No, this part isn't necessary if you don't want to.
7) Flash cwm/twrp using xzu recovery 4. Link: http://forum.xda-developers.com/showthread.php?t=2426739. The instructions specify to run superuser.bat or supersu.bat. There is only a run.bat file in the folder and this is what you must run After launching there are several options. (If using the root method from step 2, I assume you have to use the SuperUser (option2) when running the tool).
Click to expand...
Click to collapse
Yes, run the bat-file and choose SuperSU in the terminal.
8) Flash any rom (If going back to a Sony rom, must flash to 532 first to get root. Then update through OTA.
Click to expand...
Click to collapse
Before you start flashing custom ROMs, make a NAND backup of the stock ROM. This way, if you want to go back, all you have to do is to flash a boot.img and restore it, and you'll end up exactly where you left off (with root).
I thank you for your patience I understand what you've said so far.Please bear with me a while longer.
Pertaining to point 7, that xzu recovery uses supersu apk so one would have to choose the supersu option and not superuser right?
Next, looking at the omni rom thread (http://forum.xda-developers.com/showthread.php?t=2548107), I am seeing one single download available in the OP (which is the rom itself), however on the last page (http://forum.xda-developers.com/showpost.php?p=48441587&postcount=273), I am seeing people referencing editing changing biuld.prop and flashing boot.img images.
1) How does one know when it is necessary to do any of the above.
2) I am comfortable with editing build.prop but where is the boot.img come from. How do I know when this needs to be flashed?
3) How do you flash the boot.img files? Through cwm or the flashtool?
4) Some gapps come with recovery? Why is that necessary?
A million thanks.
I gotta say, now having the phone for about 12 hours, this phone is simply impressive. I had a nexus 5 briefly which had the same cpu and ram, but it was not as smooth and speedy as the xperia z ultra. I miss the black contrast of the screen of samsung's super amoled but that is about the only thing I miss. Extremely satisfied with my purchase. First sony device.
And thanks to lord and the rest of this community for making getting root so easy!
LxMxFxD said:
I gotta say, now having the phone for about 12 hours, this phone is simply impressive. I had a nexus 5 briefly which had the same cpu and ram, but it was not as smooth and speedy as the xperia z ultra. I miss the black contrast of the screen of samsung's super amoled but that is about the only thing I miss. Extremely satisfied with my purchase. First sony device.
And thanks to lord and the rest of this community for making getting root so easy!
Click to expand...
Click to collapse
I see you're being taken care of welcome dude, good choice of phone, it's a screamer!
Sent from my C6833 using XDA Premium 4 mobile app
CptAwesomeTT said:
I thank you for your patience I understand what you've said so far.Please bear with me a while longer.
Click to expand...
Click to collapse
No problem. I quite enjoy this (yes, i'm weird)
Pertaining to point 7, that xzu recovery uses supersu apk so one would have to choose the supersu option and not superuser right?
Click to expand...
Click to collapse
That depends on which superuser app you're ending up with after rooting. I haven't used that root tool, so i don't know if it installs SuperSu or something else. If it installs SuperSU, then just choose SuperSU when you're going to install Recovery. Superuser isn't really being used that much these days.
Next, looking at the omni rom thread (http://forum.xda-developers.com/showthread.php?t=2548107), I am seeing one single download available in the OP (which is the rom itself), however on the last page (http://forum.xda-developers.com/showpost.php?p=48441587&postcount=273), I am seeing people referencing editing changing biuld.prop and flashing boot.img images.
Click to expand...
Click to collapse
Yeah, there's currently a newer build being built right now, but that shouldn't stop you from flashing it. The thing with the current build is that data isn't working, so that's why you're seeing the talk about build.prop. By modifying the build.prop you'll get the data working again, so after flashing Omni, you should kick it into Airplane Mode ASAP (thorugh the notification center), use a file explorer to move the new build.prop to /system and overwrite the old one (remember to set the correct permissions to 644 or RW-R-R). After that you reboot and data will work again
- Open QuickIMG on your computer and execute fastboot on your Ultra (Power it off and hold Vol Up and plug your USB in at the same time. A Blue LED will turn on over you screen)
- Flash boot.img and after you're done, boot into Recovery (Power + Vol Up [or power it on as usual and when the Green LED turns on press and hold VOL UP until the light turns purple])
- Wipe everything
- Flash Omni and gapps
- Reboot
2) I am comfortable with editing build.prop but where is the boot.img come from. How do I know when this needs to be flashed?
Click to expand...
Click to collapse
The only times you'll have to flash boot.img is when you're coming from stock ROM and you want to jump over to AOSP (Omni, CM etc.) and when you want to go back to stock. You'll have to do it now when you're going to flash Omni. You don't have to do it when you're updating the ROM, or if you're going to flash CM, PAC or any other AOSP builds.
3) How do you flash the boot.img files? Through cwm or the flashtool?
Click to expand...
Click to collapse
You can use QuickIMG, which is probably the easiest way. After you've flashed boot.img, flash Omni and gapps as usual. Have both of them on your device before you flash the boot.img
4) Some gapps come with recovery? Why is that necessary?
Click to expand...
Click to collapse
That's not right. Kernels come with recovery. Gapps are only Google Apps (Play Store, Maps etc.)
I'm thinking of flashing Omni today myself, so you'll probably read a lot (of cursing) from me around these parts later today :laugh: If you have some other questions, feel free to ask.
LordManhattan said:
No problem. I quite enjoy this (yes, i'm weird)
That depends on which superuser app you're ending up with after rooting. I haven't used that root tool, so i don't know if it installs SuperSu or something else. If it installs SuperSU, then just choose SuperSU when you're going to install Recovery. Superuser isn't really being used that much these days.
Yeah, there's currently a newer build being built right now, but that shouldn't stop you from flashing it. The thing with the current build is that data isn't working, so that's why you're seeing the talk about build.prop. By modifying the build.prop you'll get the data working again, so after flashing Omni, you should kick it into Airplane Mode ASAP (thorugh the notification center), use a file explorer to move the new build.prop to /system and overwrite the old one (remember to set the correct permissions to 644 or RW-R-R). After that you reboot and data will work again
- Open QuickIMG on your computer and execute fastboot on your Ultra (Power it off and hold Vol Up and plug your USB in at the same time. A Blue LED will turn on over you screen)
- Flash boot.img and after you're done, boot into Recovery (Power + Vol Up [or power it on as usual and when the Green LED turns on press and hold VOL UP until the light turns purple])
- Wipe everything
- Flash Omni and gapps
- Reboot
The only times you'll have to flash boot.img is when you're coming from stock ROM and you want to jump over to AOSP (Omni, CM etc.) and when you want to go back to stock. You'll have to do it now when you're going to flash Omni. You don't have to do it when you're updating the ROM, or if you're going to flash CM, PAC or any other AOSP builds.
You can use QuickIMG, which is probably the easiest way. After you've flashed boot.img, flash Omni and gapps as usual. Have both of them on your device before you flash the boot.img
That's not right. Kernels come with recovery. Gapps are only Google Apps (Play Store, Maps etc.)
I'm thinking of flashing Omni today myself, so you'll probably read a lot (of cursing) from me around these parts later today :laugh: If you have some other questions, feel free to ask.
Click to expand...
Click to collapse
Oh man you are so damn helpful!
Ok again I got 95% of what you said. Just to clarify:
Coming from a stock rom, going to an AOSP rom requires you to flash boot.ini prior to flashing the aosp rom. Is it correct to assume that that the boot.img in this case should be extracted from the destination (aosp) rom?
Lastly, other than the rootkitZ Japanese method of rooting an older firmware (532), what is your recommended method of acquiring root?
CptAwesomeTT said:
Oh man you are so damn helpful!
Ok again I got 95% of what you said. Just to clarify:
Coming from a stock rom, going to an AOSP rom requires you to flash boot.ini prior to flashing the aosp rom. Is it correct to assume that that the boot.img in this case should be extracted from the destination (aosp) rom?
Lastly, other than the rootkitZ Japanese method of rooting an older firmware (532), what is your recommended method of acquiring root?
Click to expand...
Click to collapse
Yeah, just do this (i did it myself 30 minutes ago)
- Download the boot.img from here (this one is from the PAC ROM and works great)
- Download QuickIMG from here (and just follow the short guide)
Once you've flashed the boot.img:
- Unplug your Ultra and power it off (in case it powers on, press and hold POWER + VOL UP until you notice some rapid vibrations)
- Now Power it on again and press and hold VOL UP when the LED lights up (green i believe, and it should go purple)
- Once you're in Recovery, flash Omni and gapps (don't forget to wipe data and dalvik (under advance) before rebooting
This one is something i learned myself half an hour ago; pull your SIM out until you've had the chance to replace the build.prop, or else it'll just reboot by itself.
And yes, the japanese rooting tool is the recommended tool. The other ones aren't safe (IMEI collectors)
LordManhattan said:
Yeah, just do this (i did it myself 30 minutes ago)
- Download the boot.img from here (this one is from the PAC ROM and works great)
- Download QuickIMG from here (and just follow the short guide)
Once you've flashed the boot.img:
- Unplug your Ultra and power it off (in case it powers on, press and hold POWER + VOL UP until you notice some rapid vibrations)
- Now Power it on again and press and hold VOL UP when the LED lights up (green i believe, and it should go purple)
- Once you're in Recovery, flash Omni and gapps (don't forget to wipe data and dalvik (under advance) before rebooting
This one is something i learned myself half an hour ago; pull your SIM out until you've had the chance to replace the build.prop, or else it'll just reboot by itself.
And yes, the japanese rooting tool is the recommended tool. The other ones aren't safe (IMEI collectors)
Click to expand...
Click to collapse
You've been so helpful. I think that's all my questions until I actually get the device in hand and start working on it. Thanks a mill.
atm the jap root method is the one I'd use. kingo might be safe and vroot might not be...
Use the one in the zip or download the v4 or v5 boot.img
v4 http://forum.xda-developers.com/showthread.php?t=2426739
v5 http://forum.xda-developers.com/showthread.php?t=2426736
if going to omni i would flash the revolution kernel http://forum.xda-developers.com/showthread.php?t=2548092
No problem!
CptAwesomeTT said:
Firmware link (532)
http://forum.xda-developers.com/showthread.php?t=2463701
If the Hong Kong firmware is flashed would the interface be in english?
If not, does anyone have a link to 532 ftf english/international. Thanks.
Click to expand...
Click to collapse
Link to .532 is gone. Is there another?
Thanks!
There are so many topics on how to root, flash and install the X10, but they're all pretty old and most of them are based on Sony PC Companion, that, as far as I know, isn't available for Linux.
I am guessing that people who are upgrading their X10s to the newest FeraLab versions can do the entire procedure in the blink of an eye. So can you please help me make a quick checklist of the required steps? I'll dig on my own for all the details required by each step.
I just need a "structure" to follow. Let's say a "broader view".
A few days ago I've received an X10i with Android 2.3.3. running on it.
It hasn't been rooted.
How can I check if the bootloader is locked or not?
Note: I've no data to backup on the phone. It's all in its factory default settings with no content on it.
I've downloaded and I'm currently running the latest version of Flashtool on Arch Linux (64bit). It works.
I've also download FeraLab Kernel v28-beta4.
Then I've FeraLab Firmware v40. I couldn't get the latest version (v40.2) since the uploaded.net link doesn't work, at least not for me.
Now, this is what I came up to after reading the most recent threads that I've found here.
Please correct me if I am wrong.
1) Should I click on the "Flash device" icon (top left) and then "flash" the .ftf file of the FeraKernel?
2) Should I "push .ko files to /system/lib/modules/" and restart?
3) Now should I install the v40 ROM using the same procedure of step 1)?
4) In order to do that I think I've to follow FeraVolt steps, right?
-> Boot-up to CWM6 Recovery & just straightly install ROM following AROMA installation wizard.
-> After installation, boot your phone, pass setup wizard and wait 2 minutes. Reboot again.
-> On second boot wait not less than 2 minutes again & reboot.
-> Done. Do a reboot after you've configured your phone. Hit 'Thanks' button and rate this thread if you like my work or consider donating me to let me to have a good dinner.
Am I about to follow the right steps? Or am I doing something wrong?
What about rooting the phone and unlocking the bootloader?
Thanks for helping a n00b!
First, download both the rom and kernel. Put the rom on your sd-card and the kernel (.ftf) inside the firmware folder in flashtool.
Root the phone, then flash the kernel, and from the recovery instal the new rom (don't forget to make a backup first).
Hope this clears it up a bit.
Sent from my KIS PLUS using Tapatalk 2