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!
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
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
Hey guys, I've rooted, installed CWM Recovery, Unlocked Bootloader, and installed CyanogenMod on another phone before.
The thing is, I've had this phone for about 6 months and wanted to do the same. However, after browsing through the forums, man are there a lot of scary sh*t going down. I would like the request the procedure to install CyanogenMod safely, without losing any Keys/IMEI/XReality/DRMkeys/Etcetera.
I dont know if the method given by FXP is supposed to be this straight forward, but I too like others, do not want to risk losing important stuff if it can be avoided (Keys/IMEI/XReality/DRMkeys/Etcetera).
HOWTO
Install instructions:
first time
- power off the phone:
- hold vol+ and plug usb to boot into fastboot (blu led)
- fastboot flash boot boot.img (from cm10 zip)
- fastboot reboot
- enter recovery, on boot led will be violet for 3'', during this period press vol+
- flash rom zip
- flash gapps zip
- wipe
- reboot
for update just flash rom zip from recovery
Google Apps are not included in this ROM. You'll need to find those yourself if you want them.
Click to expand...
Click to collapse
Frankly speaking, the forums is pretty much jumbled up, and the existing [Guide] Threads are either incomplete (Lacking important steps), or Unclear (Non-Specific steps).
Perhaps someone could do me a favour by using the template that I have below to help me, and possibly others, to install CM 10.2 on our beast of a phone.
Template:
1. Backup TA and DRMkeys and stuff: http://forum-xda-developers-com/backup
2. Root: http://forum-xda-developers-com/root
3. Recovery : http://forum-xda-developers-com/recovery
4: Unlock Bootloader: http://forum-xda-developers-com/ulbl
5: Install FXP's CM 10.2 :http://forum.xda-developers.com/showthread.php?t=2461286
Something like that would suffice I think, as long as no important steps are missing that would cause me to lose stuff unique to my phone, that cannot be recovered if I didn't back it up.
P.S. My version is 14.1.B.2.257
P.P.S. Thank you in advance.
1. Root
2. Backup TA (VERY IMPORTANT)
3. Install Recovery and unlock the bootloader, or the other way around. Both ways work.
4. Install ROM by following the "guide" that you quoted above.
Sent from my C6833 using Tapatalk
I'm on 14.1.B.2.257, I believe reverting to the previous version causes data to be lost unless you back it up right. *Sighs* How troublesome.
Xenogenics said:
I'm on 14.1.B.2.257, I believe reverting to the previous version causes data to be lost unless you back it up right. *Sighs* How troublesome.
Click to expand...
Click to collapse
you will have to back up the data anyways. I think unlocking the bootloader does a factory reset, as well one is needed going from stock to CM if i unforget correctly
I am also wondering about this. I'm currently running firmware .257.
I understand that I need to back up the TA partition first (though I'm not exactly sure on what I will loose if I don't). I also understand that to do this I need to root the stock rom. I understand that in order to root, I'll need to first downgrade to an earlier firmware using flashtool. However, after that I'm not so sure what I need to do. As far as I can see, the only method of gaining root currently is to use vRoot, which is currently under investigation for IMEI mining.
How else can I root the device? I was thinking of maybe using the recovery for locked bootloaders here: http://forum.xda-developers.com/showthread.php?t=2426739
Following by flashing SuperSU from recovery as per usual.
Will this work, keeping the TA partition intact so that I can back it up before flashing CM? Assuming so, would I even need to downgrade from the .257 firmware at all?
Thanks,
i have CWM now so can flash custom roms like i did on other phones right?
what does unlocking the bootloader give me? unless i'm wrong and i have to unlock to flash?
all i've done so far is do a backup is all. (did a TA backup a while back though)
stiggy2012 said:
I am also wondering about this. I'm currently running firmware .257.
I understand that I need to back up the TA partition first (though I'm not exactly sure on what I will loose if I don't). I also understand that to do this I need to root the stock rom. I understand that in order to root, I'll need to first downgrade to an earlier firmware using flashtool. However, after that I'm not so sure what I need to do. As far as I can see, the only method of gaining root currently is to use vRoot, which is currently under investigation for IMEI mining.
How else can I root the device? I was thinking of maybe using the recovery for locked bootloaders here: http://forum.xda-developers.com/showthread.php?t=2426739
Following by flashing SuperSU from recovery as per usual.
Will this work, keeping the TA partition intact so that I can back it up before flashing CM? Assuming so, would I even need to downgrade from the .257 firmware at all?
Thanks,
Click to expand...
Click to collapse
OK, so looking into this further, you already need to have root to be able to flash the "CWM for locked bootloader" rocovery. So as far as I can see, the only way to get root in order to back up the TA partition is to give your IMEI to the Chinese via vRoot?
Thank god the stock rom is so good.
tommo123 said:
i have CWM now so can flash custom roms like i did on other phones right?
what does unlocking the bootloader give me? unless i'm wrong and i have to unlock to flash?
all i've done so far is do a backup is all. (did a TA backup a while back though)
Click to expand...
Click to collapse
You have to unlock the bootloader to flash custom ROMs. You can flash stock ROMs without unlocking it, but you have to unlock it if you want CM, PAC, PA etc.
Sent from my C6833 using Tapatalk
really, so what would happen if i tried to flash an aosp rom now? would the system partition essentially be read only?
sorry for the Qs but haven't had a locked bootloader since the htc desire (although the s-off for that one was to remap the partitions to allow more room for data) and the reasons for unlocking don't seem to be the same.
tommo123 said:
really, so what would happen if i tried to flash an aosp rom now? would the system partition essentially be read only?
sorry for the Qs but haven't had a locked bootloader since the htc desire (although the s-off for that one was to remap the partitions to allow more room for data) and the reasons for unlocking don't seem to be the same.
Click to expand...
Click to collapse
Nothing will happen if you try it now. You can easily unlock the bootloader by going to Sony's Dev site, request your key and use Flashtool to unlock it. It takes a couple of minutes once you have Flashtool and the drivers installed. It's also perfectly safe to unlock it and you will lose your warranty. BUT you can easily relock it again if something happens to your ZU and the warrenty will be back.
Remember to backup your TA before you unlock your bootloader. It contains a lot if device info and your unique DRM keys. Unlocking the bootloader will wipe the system partition, but you will still have root, photos, music etc. (But do a backup of those just in case).
Sent from my C6833 using Tapatalk
i think that's where i got confused with drivers - unlocking.
i have already done a backup of my TA part so that side of it is ok. i'll leave unlocking until there's a rom i want to try. possibly a complete 4.4 or something.
cheers LM
tommo123 said:
i think that's where i got confused with drivers - unlocking.
i have already done a backup of my TA part so that side of it is ok. i'll leave unlocking until there's a rom i want to try. possibly a complete 4.4 or something.
cheers LM
Click to expand...
Click to collapse
If you've already backed up your TA, it means that you have the drivers installed, so job done All you have to do is to install Flashtool and get your key from Sony (which you will get on your email straight away). Either way, just ask here if/when you want to unlock it so we can guide you through it (it's very easy though).
ran flashtool but gave me driver errors - missing. unable to install the drivers included (i guess due to windows 8 driver signing)
Got my XZU last Saturday and decided today to keep it. Being long out of the Sony-world (last was an XS, now coming from a Find 5), I've got some questions. I'm also going to search for the infos, but I feel a single thread for "my stuff" makes it easier for me, so please be kind.
So, for the current state, here's the device's information.
- Sony Xperia Z Ultra (C6833), black
- running on Vodafone DE
- Android version 4.2.2
- Baseband version 8974-AAAAANAZQ-10220006-09
- Kernel 3.4.0-perf-gde8296d-02194-ga2561a5
- Build 14.1.B.1.510
- The device shows me an update to 14.2.A.1.136
Questions:
1) Do Sony's official updates only update Android + Sony Apps or are there also firmware updates included?
2) I want to root and install a custom ROM, should I start from the current build or should I upgrade to $something first?
3) I've read that KitKat is restricting SDcard usage for non-system apps. Do custom 4.4 ROMs work around this(,yet) or should I update to 4.3 max?
4) I probably won't use the camera much, if at all, still, most custom ROMs can't get the camera quality on a level the stock ROM has, so how bad is it on this device?
5) is the PowerCover CP12 available somewhere in the EU? It's "out of stock" in all big shops I looked at in .de,.at,.ch and the Twitter-Team wasn't really helpful. Ordering from outside the EU would be possible, but pretty much guaranteed to get stuck at the customs where the next office is ~50km away and doesn't have work-friendly times at all.
6) About screen protectors: a) can I apply them over the shatter shield and if so b) will input by pens or something still work on a decent level?
7) is there a prefered solution of recoveries on this device or does it not matter at all, if I'd choose CWM or TWRP(or is there something else entirely)?
8) are there known problems in general with custom ROMs regarding external hardware? I'd like to use my "SmartWireless Headset Pro", my "SmartWatch (1)" and TV-Out
That's it for now, thanks for any help
1) The 136 update is a firmware update (to Android 4.3), but they also push out updates for their Sony apps.
2) You have to update to at least 290 (Android 4.3) if you don't want to lose your IMEI when you flash a custom ROM. Also note that you'll lose your IMEI if you downgrade from 136/290 to anything older. There are no real reasons to downgrade though, but just keep that in mind. It's easily fixable, so it's not the end of the world if you do it.
3) Yes, there's a workaround to get SD card working on KitKat (you just have to replace one file)
4) The camera is still bad on custom ROMs. It might get better with official Sony KitKat.
5) I have no idea.
6) a) Yes. b) Yes.
7) We've got double recovery, meaning you'll get both CWR and TWRP when you flash recovery, so use the one you prefer. (Vol Up for CWR and Vol Down for TWRP)
8) I think the only known issue on 136 is that Bluetooth might be a little wonky, but i'm not sure, so be sure to read around here since there's a thread about it.
Thank you for that.
In regard to 1), I meant firmware updates of hardware, f.e. the Find5 received some updates regarding the touchscreen.
As for 2), so there's currently no reason not to install the latest official Sony update, meaning it's also rootable without too much hassle? What would be the consequences of a lost IMEI?
S.D.Richards said:
Thank you for that.
In regard to 1), I meant firmware updates of hardware, f.e. the Find5 received some updates regarding the touchscreen.
As for 2), so there's currently no reason not to install the latest official Sony update, meaning it's also rootable without too much hassle? What would be the consequences of a lost IMEI?
Click to expand...
Click to collapse
Bugfixes are included in firmware updates, so they don't release an update to fix one minor thing. The Find5 receives updates every two weeks, if i'm not mistaken?
There's really no reason to update to 136 (the newest) if you're going to flash a custom ROM. Rooting is fairly easy if your bootloader is unlocked, and it only takes a couple of minutes, but it's a little more complicated if your bootloader is locked. Luckily, you're on 510, meaning it's even easier to root, and once you've rooted 510, make a backup of your TA partition. It holds all of your unique DRM files that makes X-Reality work etc. You'll lose the TA partition when you unlock the bootloader, so that's why you have to make a backup of it before you unlock it. Once you've done that, update to 290, unlock the bootloader, root it and do whatever you'd like to do.
Thanks again.
Now rooting worked(+OTA keeper from the Playstore), so did creating the TA backup.
Having a glance over the custom ROMs available as of now, I think I'd like to stay on rooted stock until Omni (official) comes around.
So what would be the (better) procedure to get latest Sony ROM running? Use Sony's updater and hope OTA keeper works or unlock, install recovery and flash a pre-rooted FTF?
S.D.Richards said:
Thanks again.
Now rooting worked(+OTA keeper from the Playstore), so did creating the TA backup.
Having a glance over the custom ROMs available as of now, I think I'd like to stay on rooted stock until Omni (official) comes around.
So what would be the (better) procedure to get latest Sony ROM running? Use Sony's updater and hope OTA keeper works or unlock, install recovery and flash a pre-rooted FTF?
Click to expand...
Click to collapse
OTA Root Keeper doesn't work on 4.3, so you'll lose root no matter what you do. Are you still on 510, or have you updated to something else?
You have your TA partition backed up now (recommend you to upload it to your Drive or Dropbox), so you can unlock the bootloader without permanently losing the TA partition. It'll delete it when you unlock the bootloader, but you can easily restore it again in case you have to send it in for repairs. Rooting 290 and everything else becomes so much easier and faster the second your BL is unlocked, so head over to the General section and look for Jackie's root guide and see if that's something you might want to do...
...or you can simply stay with the firmware you're on now, granted it's not the most stable firmware version, but it'll save you a lot of time. Official KitKat is also scheduled for release this month, so you can:
A ) Stay on current firmware and wait for official Sony KitKat
B ) Go all out and flash a custom ROM
I'm currently running the GPe ROM, and I can highly recommend it. It's solid as a rock with no bugs.
Any questions?
Sent from my C6806_GPe using Tapatalk
LordManhattan said:
OTA Root Keeper doesn't work on 4.3, so you'll lose root no matter what you do. Are you still on 510, or have you updated to something else?
Click to expand...
Click to collapse
Still on 510, bedtime was up and I don't wanted to do something stupid with a sleepy head.
You have your TA partition backed up now (recommend you to upload it to your Drive or Dropbox), so you can unlock the bootloader without permanently losing the TA partition.
Click to expand...
Click to collapse
Yes, did that and mirrored it over a few systems. BTW, if I'd ever go back to stock, would the TA-p get changed so I'd need to back it up again or does it stay the way it is over the phone's lifetime?
It'll delete it when you unlock the bootloader, but you can easily restore it again in case you have to send it in for repairs. Rooting 290 and everything else becomes so much easier and faster the second your BL is unlocked, so head over to the General section and look for Jackie's root guide and see if that's something you might want to do...
Click to expand...
Click to collapse
No problem, I had my Xperia S unlocked, so I now the procedure. Only question related to that: I read that for the Z1(?) there's a minimal version one should update to before unlocking the BL, if you don't camera stops working or something - so, is this also a problem on the ZU or has this already been fixed?
I'm currently running the GPe ROM, and I can highly recommend it. It's solid as a rock with no bugs.
Click to expand...
Click to collapse
I'll have a look at it, thanks.
S.D.Richards said:
.
Yes, did that and mirrored it over a few systems. BTW, if I'd ever go back to stock, would the TA-p get changed so I'd need to back it up again or does it stay the way it is over the phone's lifetime?
Click to expand...
Click to collapse
The TA partition is unique to your device, so you do it only once, so be sure to not lose it.
No problem, I had my Xperia S unlocked, so I now the procedure. Only question related to that: I read that for the Z1(?) there's a minimal version one should update to before unlocking the BL, if you don't camera stops working or something - so, is this also a problem on the ZU or has this already been fixed?
Click to expand...
Click to collapse
The ZU has never had any of the camera issues when we unlock the bootloader, so there's nothing to add here
Sent from my C6806_GPe using Tapatalk
So to be clear, when you're talking about the GPe ROM, you're meaning this one: http://forum.xda-developers.com/showthread.php?t=2608708 ?
So if I'd like to try this, I'd need to:
1. unlock bootloader
2. install recovery
3. take NAND backup
4. Flash .290 fw
5. flash this ROM
Correct?
S.D.Richards said:
So to be clear, when you're talking about the GPe ROM, you're meaning this one: http://forum.xda-developers.com/showthread.php?t=2608708 ?
So if I'd like to try this, I'd need to:
1. unlock bootloader
2. install recovery
3. take NAND backup
4. Flash .290 fw
5. flash this ROM
Correct?
Click to expand...
Click to collapse
The bootloader unlocking doesn't need to be the first step since you can flash Recovery on a locked bootloader. You can do everything except the ROM flashing on a locked bootloader. But yeah, that looks fine to me. Be sure to download the tweaked GPe version that includes Recovery and SD fix.
If you can't bother making a NAND:
- Unlock the bootloader
- Update to 290
- Flash boot.img (includes recovery)
- Boot into recovery and flash (VOL UP when LED lights up)
- Done.
Thanks again, could/would you link me to a .290 ftf for germany/europe/generic? The ones I found are either for other regions or the links seem to be down.
Here's 290 EU for the C6833.
https://mega.co.nz/#!VR4HyJia!PGxJXHOi8V-eJpWDnsJKShRPlhoYHR5DpFRkko6m0Nk
Sent from my C6806_GPe using Tapatalk
LordManhattan said:
Here's 290 EU for the C6833.
https://mega.co.nz/#!VR4HyJia!PGxJXHOi8V-eJpWDnsJKShRPlhoYHR5DpFRkko6m0Nk
Sent from my C6806_GPe using Tapatalk
Click to expand...
Click to collapse
Thanks, already found that link, but it gives me a "the file you are trying to download is no longer available"-error.
Already searched on Google, but couldn't find one, yet, or only for the other models.
Here's the Chilean 290 for C6833. It doesn't matter which one you use, and you're planning to flash the GPe, so just flash this one and get it done
Sent from my C6806_GPe using Tapatalk
Thank you very much for all your help, GPe is up and running smoothly now.
Apart from anything looking pretty huge, guessing different DPI settings compared to Sony's values, it's fine so far. One question though: under display settings it says X-Reality is on. Is that just cosmetics, since at no point I restored the TA-backup. If it's "fake", is it possible to restore TA and have it working or would that "trash" the system and restore should only be done in case of a stock re-install?
S.D.Richards said:
Thank you very much for all your help, GPe is up and running smoothly now.
Apart from anything looking pretty huge, guessing different DPI settings compared to Sony's values, it's fine so far. One question though: under display settings it says X-Reality is on. Is that just cosmetics, since at no point I restored the TA-backup. If it's "fake", is it possible to restore TA and have it working or would that "trash" the system and restore should only be done in case of a stock re-install?
Click to expand...
Click to collapse
just cosmetic and does nothing. If you restored the TA the GPe rom would fail to boot.
blueether said:
just cosmetic and does nothing. If you restored the TA the GPe rom would fail to boot.
Click to expand...
Click to collapse
Thanks for that quick answer, satisfied for now, so I can finally go to sleep
One last thing. Just change ro.sf.lcd_density=400 to 320 in build.prop to get the same sized UI like the Sony ROM. Unless you like 400.
Sent from my C6806_GPe using Tapatalk
LordManhattan said:
One last thing. Just change ro.sf.lcd_density=400 to 320 in build.prop to get the same sized UI like the Sony ROM. Unless you like 400.
Sent from my C6806_GPe using Tapatalk
Click to expand...
Click to collapse
Perfect, just what I've been looking for, thanks.
Now to hope that the ZU also gets double tap to wake, than I'd be pretty happy.
S.D.Richards said:
Perfect, just what I've been looking for, thanks.
Now to hope that the ZU also gets double tap to wake, than I'd be pretty happy.
Click to expand...
Click to collapse
Yeah, the leaked footage from the Z2 KitKat build shows the option to use double tap to wake, so it looks like we'll get it. It's a kernel feature, so it'll work on mostly anything out there.
hi
i own a Z2 (d6503)
-bootloader unlocked (everything else is custom) i had rooted it previously but i think i lost the root access while updating the firmware to 4.4.4 using EMma
my problems
1. Google services are not working over wifi, but there is no problem with mobile data.
i have tried clear cache method already, factory reset, date/time thing. Sometimes few retries make playstore work.
2. Phone isn't turning on in recovery mode. neither manually (with buttons) nor with quickboot or PC
everywhere i found the same method: turn off, power on and wait for led to light up then press either of the volume buttons repeatedly. But the led doesnt light up
3. I have lost my DRM keys while unlocking the bootloader. (no TA backup). my bad.
what did i looose other than xreality engine? can it be recovered? how?
4. How can i root the new version of firmware android 4.4.4 (23.0.1.A0.167)
Please help
i am familiar with rooting and know a little more than an average user. But at the end of the day i am a noob too.
1. no idea, sounds weird that it works over data but not WiFi.
2. If your running stock rom then you don't have recovery installed hence you can't access it.
3. AFAIK The play station remote won't work, there is no way to recover DRM keys they are device specific so your out of luck.
4. Downgrade to .314 and flash a pre-rooted zip, there is currently no known exploit for 4.4.4 so no direct root method.
Although you have discouraged me completely, thanks anyway.
Can you explain the pre root zip thing? Shouldnt I just wait for the new rooting method to come up?
Sent from my D6503 using XDA Free mobile app
Absarock1 said:
hi
i own a Z2 (d6503)
-bootloader unlocked (everything else is custom) i had rooted it previously but i think i lost the root access while updating the firmware to 4.4.4 using EMma
my problems
1. Google services are not working over wifi, but there is no problem with mobile data.
i have tried clear cache method already, factory reset, date/time thing. Sometimes few retries make playstore work.
2. Phone isn't turning on in recovery mode. neither manually (with buttons) nor with quickboot or PC
everywhere i found the same method: turn off, power on and wait for led to light up then press either of the volume buttons repeatedly. But the led doesnt light up
3. I have lost my DRM keys while unlocking the bootloader. (no TA backup). my bad.
what did i looose other than xreality engine? can it be recovered? how?
4. How can i root the new version of firmware android 4.4.4 (23.0.1.A0.167)
Please help
i am familiar with rooting and know a little more than an average user. But at the end of the day i am a noob too.
Click to expand...
Click to collapse
Once rooted, you can recover most features flashing this : DRM FUNTION RESTORATION FOR UB
Absarock1 said:
Although you have discouraged me completely, thanks anyway.
Can you explain the pre root zip thing? Shouldnt I just wait for the new rooting method to come up?
Sent from my D6503 using XDA Free mobile app
Click to expand...
Click to collapse
AFAIK devs aren't putting a huge amount of effort into finding a new root exploit, why bother when achieving root through downgrade and flashing pre-rooted is fairly trivial.
The pre-rooted zips are just that stock .167 roms that have been pre-rooted, they can be flashed over earlier fw without data loss.
So where can i get one?
ghostofcain said:
AFAIK devs aren't putting a huge amount of effort into finding a new root exploit, why bother when achieving root through downgrade and flashing pre-rooted is fairly trivial.
The pre-rooted zips are just that stock .167 roms that have been pre-rooted, they can be flashed over earlier fw without data loss.
Click to expand...
Click to collapse
[/CODE][/CODE]
oh damn! In my first post i made a mistake i meant to say (everything is stock) but wrote custom instead.
terribly sorry
Where can i get one of these roms u just mentioned?
Even if i get it, how do i flash it? I dont have a custom recovery installed and if there is a stock recovery i cant enter it.
can u elaborate the procedure i mentioned below?
[ how to flash this kernel ] (via fastboot)
download the kernel image
save the boot.img to the folder containing fastboot binary
flash the boot.img using fastboot:
Code:
fastboot flash boot boot.img
reboot from fastboot
Code:
fastboot reboot
the device should now start booting
enjoy!
THAnks
thanks man. 3/4 of my problems are solved now. 1 is going to be solved soon hopefully.