Related
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!
These are flashable zip file and FTF pairs for the latest KitKat firmware 14.3.A.0.681 for C6833/C6806/C6802 based on [NUT]'s modifications. I couldn't wait for his firmware so decided to make it .
The upgrade instructions are exactly the same as in this thread: http://forum.xda-developers.com/showthread.php?t=2631768 . You only need to use the flashable zip and FTF files in this thread instead. In a nutshell:
Install recovery (either via a root exploit or unlocking the bootloader). Note: unlocking the bootloader will typically result in data loss, you are advised to use the root exploit on the older firmware instead of touching the bootloader.
Enter recovery and flash Sony Xperia Z Ultra Europe LTE_14.3.A.0.681_flashable.zip
Power off the device and enter flash mode
Flash Sony Xperia Z Ultra Europe LTE_14.3.A.0.681_Stripped.ftf using FlashTool (0.9.15.0 or later, older versions won't work)
These instructions are relatively safe and you can always downgrade using the other flashable zip/FTF if you so wish.
Lots of credits go to NUT & co. for making the original flashable zip!.
Notes:
- Some people run into a bug that makes camera non-functional. If you have this bug you can try flashing zip/stripped FTF from another region (e.g., US) instead.
- If you have issues remounting /system in TWRP you can try @[NUT]'s patch for the recovery here: http://forum.xda-developers.com/showpost.php?p=51378028&postcount=88 . It can be flashed after you flash the flashable zip with adb sideload recoverypatch.zip inside the package on Linux or running install.bat on Windows.
Download links:
Flashable zip for C6833:
-- Mega -- Sony Xperia Z Ultra Europe LTE_14.3.A.0.681_flashable.zip
-- GDrive -- Sony Xperia Z Ultra Europe LTE_14.3.A.0.681_flashable.zip
Flashable zip for C6806:
-- Mega -- C6806_14.3.A.0.681 US_Unbranded_flashable.zip
-- GDrive -- C6806_14.3.A.0.681 US_Unbranded_flashable.zip
Flashable zip for C6802:
-- Mega -- C6802_14.3.A.0.681_Generic HK_flashable.zip
-- GDrive -- C6802_14.3.A.0.681_Generic HK_flashable.zip
FTF for C6833:
-- Mega -- Sony Xperia Z Ultra Europe LTE_14.3.A.0.681_Stripped.ftf
-- GDrive -- Sony Xperia Z Ultra Europe LTE_14.3.A.0.681_Stripped.ftf
FTF for C6833: C6833_4.4.2_HK_Stripped.ftf
FTF for C6833: C6833_14.3.A.0.681 _Euro-LTE_Stripped.ftf
FTF for C6833: C6833_1275-9413_R3C 14.3.A.0.681_Singapore Generic_Stripped.ftf
FTF for C6806:
-- Mega -- C6806_14.3.A.0.681 US_Unbranded_Stripped.ftf
-- GDrive -- C6806_14.3.A.0.681 US_Unbranded_Stripped.ftf
FTF for C6802:
-- Mega -- C6802_14.3.A.0.681_Generic HK_Stripped.ftf
-- GDrive -- C6802_14.3.A.0.681_Generic HK_Stripped.ftf
fnf said:
This is a flashable zip file and FTF pair for the latest KitKat firmware 14.3.A.0.681 for C6833 based on [NUT]'s modifications. I couldn't wait for his firmware so decided to make it .
The upgrade instructions are exactly the same as in this thread: http://forum.xda-developers.com/showthread.php?t=2631768 . You only need to use the flashable zip and FTF files in this thread instead. In a nutshell:
Install recovery (either via a root exploit or unlocking the bootloader). Note: unlocking the bootloader will typically result in data loss, you are advised to use the root exploit on the older firmware instead of touching the bootloader.
Enter recovery and flash Sony Xperia Z Ultra Europe LTE_14.3.A.0.681_flashable.zip
Power off the device and enter flash mode
Flash Sony Xperia Z Ultra Europe LTE_14.3.A.0.681_Stripped.ftf using FlashTool
These instructions are relatively safe and you can always downgrade using the other flashable zip/FTF if you so wish.
Lots of credits go to NUT & co. for making the original flashable zip!.
Download links:
https://mega.co.nz/#!3xB2TZBI!nMI4MnmGLvU-4e0RmOlpI8XMTnrAEDaPaJoSDo7-MxI
https://mega.co.nz/#!fsJzlI5I!X5rcqH019UCwIxiZvSmFzb4E_1s4J7WIYYxYkAk5o3o
Click to expand...
Click to collapse
Thanks for the work; have you installed via this method yourself?
I ask as there are a couple of other requirements for this to work in Nuts Z1 thread on the same subject here -> http://forum.xda-developers.com/showthread.php?t=2687443
Whereas you link to the 4.3 update without the init.d requirements?
Thanks
Yes, I'm running KitKat with the firmware that I posted.
I didn't need to enable init.d support and can confirm that dr.initd.active is set to false in my XZDR config. SuperSU works as well as the rest of the firmware.
Not to devalue the work that people have done (on the contrary it is much appreciated!), but there are a lot of conflicting information on how to root the device. I feel the rooting guides are much longer than necessary. Here is why (and how) we can root and keep the bootloader locked:
We root a firmware (e.g., 14.1.G.1.534) and install recovery
With recovery we can install the system tarball of any other firmware versions (e.g., KitKat). The flashable zip also installs SuperSU (among other) in the process.
We will then flash everything from the new KitKat firmware but system image. Stripping at least the system image out of the FTF ensures that it will not be reflashed by mistake.
Regarding init.d support, it is no longer needed on 4.3 onwards as daemonsu will be started by install-recovery.sh .
scoobydu said:
Thanks for the work; have you installed via this method yourself?
I ask as there are a couple of other requirements for this to work in Nuts Z1 thread on the same subject here -> http://forum.xda-developers.com/showthread.php?t=2687443
Whereas you link to the 4.3 update without the init.d requirements?
Thanks
Click to expand...
Click to collapse
Stripped FTF is not working
fnf said:
This is a flashable zip file and FTF pair for the latest KitKat firmware 14.3.A.0.681 for C6833 based on [NUT]'s modifications. I couldn't wait for his firmware so decided to make it .
The upgrade instructions are exactly the same as in this thread: http://forum.xda-developers.com/showthread.php?t=2631768 . You only need to use the flashable zip and FTF files in this thread instead. In a nutshell:
Install recovery (either via a root exploit or unlocking the bootloader). Note: unlocking the bootloader will typically result in data loss, you are advised to use the root exploit on the older firmware instead of touching the bootloader.
Enter recovery and flash Sony Xperia Z Ultra Europe LTE_14.3.A.0.681_flashable.zip
Power off the device and enter flash mode
Flash Sony Xperia Z Ultra Europe LTE_14.3.A.0.681_Stripped.ftf using FlashTool
These instructions are relatively safe and you can always downgrade using the other flashable zip/FTF if you so wish.
Lots of credits go to NUT & co. for making the original flashable zip!.
Download links:
https://mega.co.nz/#!3xB2TZBI!nMI4MnmGLvU-4e0RmOlpI8XMTnrAEDaPaJoSDo7-MxI
https://mega.co.nz/#!fsJzlI5I!X5rcqH019UCwIxiZvSmFzb4E_1s4J7WIYYxYkAk5o3o
Click to expand...
Click to collapse
Your stripped ftf is not working. Please check and upload. Thanks!!!!!
android_myan said:
Your stripped ftf is not working. Please check and upload. Thanks!!!!!
Click to expand...
Click to collapse
Weird, I'll check when I come back in an hour or so. If you want to make it work in the mean time, you just need to flash the Germany KK FTF instead of this FTF in the General forums and exclude system, userdata from the flash and especially uncheck all items in Wipe section. If you're unfamiliar with Flashtool it's better to wait.
Will this work with c6802 as well as c6806?
Unlocked bootloader.
Sent from my C6806_GPe using XDA Premium 4 mobile app
atrix2 said:
Will this work with c6802 as well as c6806?
Unlocked bootloader.
Sent from my C6806_GPe using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I can produce the zip and FTF for these devices but I won't be able to test it. That said, if you have an unlocked bootloader wouldn't it be easier to just flash the dual recovery kernel and then supersu to gain root?. Being able to flash custom kernel is an advantage that us with locked bootloader can't enjoy .
fnf said:
Yes, I'm running KitKat with the firmware that I posted.
I didn't need to enable init.d support and can confirm that dr.initd.active is set to false in my XZDR config. SuperSU works as well as the rest of the firmware.
Not to devalue the work that people have done (on the contrary it is much appreciated!), but there are a lot of conflicting information on how to root the device. I feel the rooting guides are much longer than necessary. Here is why (and how) we can root and keep the bootloader locked:
We root a firmware (e.g., 14.1.G.1.534) and install recovery
With recovery we can install the system tarball of any other firmware versions (e.g., KitKat). The flashable zip also installs SuperSU (among other) in the process.
We will then flash everything from the new KitKat firmware but system image. Stripping at least the system image out of the FTF ensures that it will not be reflashed by mistake.
Regarding init.d support, it is no longer needed on 4.3 onwards as daemonsu will be started by install-recovery.sh .
Click to expand...
Click to collapse
OK thanks for the explanation.
Did you make any progress on tracking the error with the stripped down ftf at all?
Installed, but camera won't work. Only preview. Other camera apps works ok, only Sony camera won't make shoots. I try to flash full ftf to see if works.
android_myan said:
Your stripped ftf is not working. Please check and upload. Thanks!!!!!
Click to expand...
Click to collapse
scoobydu said:
thanks for the explanation.
Did you make any progress on tracking the error with the stripped down ftf at all?
Click to expand...
Click to collapse
I have redownloaded the FTF and compared the checksum, it doesn't appear corrupted to me so I think the problem is you're using FlashTool 0.9.13. Newer Sony firmwares work with 0.9.15.0.
dadme said:
Installed, but camera won't work. Only preview. Other camera apps works ok, only Sony camera won't make shoots. I try to flash full ftf to see if works.
Click to expand...
Click to collapse
If you flash the full FTF you will lose root unless you exclude 'system'. I'd suggest clearing the Camera app's data. Camera works fine for me. I just upgraded from 4.3 so mine has not been factory reset.
Edit: Are you storing the photos to the SD card by any chance?. I have applied the fix for SD card permissions so not sure if it is an issue or not.
fnf said:
I have redownloaded the FTF and compared the checksum, it doesn't appear corrupted to me so I think the problem is you're using FlashTool 0.9.13. Newer Sony firmwares work with 0.9.15.0.
Click to expand...
Click to collapse
Thank! I will try with new flashtool version.
my device is C6802, I was on rooted .681 with unlocked BL. I want rooted but with locked BL so I did these:
with TWRP I wipe dalvik and cache and then flashed 6833 flashable zip
power of and then flash stripped ftf via flashtool 0.9.15.0
reboot - restore TA - reboot
done.
now I got root with locked BL
thanks!
fnf said:
If you flash the full FTF you will lose root unless you exclude 'system'. I'd suggest clearing the Camera app's data. Camera works fine for me. I just upgraded from 4.3 so mine has not been factory reset.
Edit: Are you storing the photos to the SD card by any chance?. I have applied the fix for SD card permissions so not sure if it is an issue or not.
Click to expand...
Click to collapse
Tryed everything, only front camera works, with back camera i can't make shoots with sony camera, and autofocus is not working in other camera apps. I upgraded from 4.3. with or without factory reset problem is here.
dadme said:
Tryed everything, only front camera works, with back camera i can't make shoots with sony camera, and autofocus is not working in other camera apps. I upgraded from 4.3. with or without factory reset problem is here.
Click to expand...
Click to collapse
Can anyone else please confirm?. There are nothing specifics to my device in the FTF or the zip so I suspect flashing the full FTF won't fix it.
The binaries were generated from the Germany KK firmware if that helps.
@abuihsan: thanks for letting me know, the only difference between Z Ultra variants that I've seen is radio so the worst we'll get is losing LTE.
If anyone wants me to create the files for other variants then let me know.
thanks will try today
fnf said:
Can anyone else please confirm?. There are nothing specifics to my device in the FTF or the zip so I suspect flashing the full FTF won't fix it.
The binaries were generated from the Germany KK firmware if that helps.
@abuihsan: thanks for letting me know, the only difference between Z Ultra variants that I've seen is radio so the worst we'll get is losing LTE.
If anyone wants me to create the files for other variants then let me know.
Click to expand...
Click to collapse
Sony camera works fine for me.. Also autofocusing on 3rd party camera apps works.. I tested it with vsco and vignette camera.
The only problem I found is sd card writable problem (fixed with an apps from play store). The remaining problem is volume button. If I open an app, example a game then adjusting volume button makes those apps FC.
In setting, adjusting volume also makes setting FC. It happened on both Germany and HK .681.
Hope it can be fixed soon.
thanks bro ..
i got KitKat on my C6802 :victory:
abuihsan said:
Sony camera works fine for me.. Also autofocusing on 3rd party camera apps works.. I tested it with vsco and vignette camera.
The only problem I found is sd card writable problem (fixed with an apps from play store). The remaining problem is volume button. If I open an app, example a game then adjusting volume button makes those apps FC.
In setting, adjusting volume also makes setting FC. It happened on both Germany and HK .681.
Hope it can be fixed soon.
Click to expand...
Click to collapse
Adjusting volume in all apps work fine for me, guess it's just one of those weird Android bugs. If you can get the logcat (pressing volume up/down then FC) then I might have a look.
I've got ClearAudio+, Dynamic normalizer enabled if that helps.
fnf said:
Adjusting volume in all apps work fine for me, guess it's just one of those weird Android bugs. If you can get the logcat (pressing volume up/down then FC) then I might have a look.
I've got ClearAudio+, Dynamic normalizer enabled if that helps.
Click to expand...
Click to collapse
hi.. ClearAudio+, Dynamic normalizer enabled and problem still persist..
hi.. here is the CATLOG .. I use FM radio, 2 games, also attempting adjusting volume in setting.. hope they are recorder fine.. thanks!
I am no developer by any means, just a regular user that was determined to find a stable S5 ROM for my S4, after making the mistake of buying this locked down piece of crap! Anyway, after trying all the S5 ROMs developed for the Verizon variant and I was constantly running into problems with them. Systemui crashing, random reboots, etc. I came across a post on how to get AOSP running on safestrap and it gave me a idea.. Take a AT&T ROM, and replace the (at&t) apns-config.xml file inside the ROM with the (Verizon) apns-config.xml from a Verizon based ROM. So that's what I did, and it seemed to work, on any SafeStrap compatible ROM. But then I came across a Patch that seems to work just as well. And I came across Goldfinger ROM and Ive been running it for a week, with no problems!
UPDATE AS OF 10-06-14 THE ORIGINAL ROM HAS BEEN UPDATED. IR BLASTER BUG FIXED!
Bugs?
Some users report GPS issues, but ive never experienced it, but other users in the original thread have reported it. Test and let me know!
So in this thread, I will explain 2 different ways how to get the great Goldfinger ROM on your Verizon S4.
I TAKE NO CREDIT FOR ANY DEVELOPMENT POSTED. Im just typing the How-To guide!
First things first I want to Thank/Give Credit to everybody deserving it!
[email protected] for developing this fantastic ROM!
[email protected] for the patch
- Chainfire for root
- @Surge1223 for modules and Modems
- Hashcode for Safestrap, making all this possible!
Downloads Needed:
- Goldfinger ROM thread with Download links:
- http://forum.xda-developers.com/galaxy-s4-att/development/movin-please-posts-t2864506
- Patch thread with download links:
- http://forum.xda-developers.com/showthread.php?t=2674280
- Chainfire SuperSu Zip
- http://download.chainfire.eu/452/SuperSU/
- Surge1223 Modem and Modules:
- http://forum.xda-developers.com/showthread.php?t=2487298
- https://www.androidfilehost.com/?fid=23486521113837640
-Signal bar fix:
- https://www.androidfilehost.com/?fid=23501681358559322
After everything is downloaded and moved to your SD-Card:
First install process - Easier, but may not always work properly:
1. Flash GoldFinger ROM and choose your preferences in Aroma
2. Flash Patch
a. inside aroma choose Full install, add Verizon features and build.prop, and no kernel)
3. Flash Signal bar fix
3. SuperSu zip to get root back
4. Wi-Fi modules
5. Bootloader specific modem (optional, but highly recommended)
** If this install works and you get data, and sms, then great youre done! **
** After this install you will have the s4 phone and sms apps. If you would like to update to the S5 apps, there are a few ways to do that.
- Use this thread and follow install instructions as posted:
- http://forum.xda-developers.com/showthread.php?t=2676928
If the first method did not work for you, follow these instructions:
1. Download Goldfinger ROM to your PC
2. Download Verizon ROM (stock, echoe, hyperdrive, etc.)
3. Extract the Verizon ROM to wherever you like
4. Navigate to system > etc and find the file named "apns-config.xml"
5. Save the Verizon ROM apns-config.xml to your desktop
6. Now use 7zip, or a similar program and open the Goldfinger ROM
7. Navigate to system > etc and find the same apns-config.xml
8. Once you've located it, delete it.
9. Now, copy the "apns-config.xml" that you moved to your desktop, from your Verizon ROM, and place it in the same place that you deleted the old one from
10. After that, close out of 7zip and copy Goldfinger to your SD-Card
11. Now follow the normal install process posted above.
I hope everyone enjoys! If you like this ROM, please head over to the ROM thread and thank iB4STiD and let him know his work is appreciated!
Original Thread: http://forum.xda-developers.com/galaxy-s4-att/development/movin-please-posts-t2864506
Thanks for posting this. I always wondered if VZW users could download and use other carriers' ROMs.
jrgthird said:
Thanks for posting this. I always wondered if VZW users could download and use other carriers' ROMs.
Click to expand...
Click to collapse
Welcome! Let me know how everything goes for you!
i'm trying to jump ship from this phone but thanks for the write up, it'll help a lot of ppl still trying to use this phone
luke24 said:
I am no developer by any means, just a regular user that was determined to find a stable S5 ROM for my S4, after making the mistake of buying this locked down piece of crap! Anyway, after trying all the S5 ROMs developed for the Verizon variant and I was constantly running into problems with them. Systemui crashing, random reboots, etc. I came across a post on how to get AOSP running on safestrap and it gave me a idea.. Take a AT&T ROM, and replace the (at&t) apns-config.xml file inside the ROM with the (Verizon) apns-config.xml from a Verizon based ROM. So that's what I did, and it seemed to work, on any SafeStrap compatible ROM. But then I came across a Patch that seems to work just as well. And I came across Goldfinger ROM and Ive been running it for a week, with no problems!
Bugs?
Only one, IR blaster does not work. ROM bug!
So in this thread, I will explain 2 different ways how to get the great Goldfinger ROM on your Verizon S4.
I TAKE NO CREDIT FOR ANY DEVELOPMENT POSTED. Im just typing the How-To guide!
First things first I want to Thank/Give Credit to everybody deserving it!
[email protected] for developing this fantastic ROM!
[email protected] for the patch
- Chainfire for root
- @Surge1223 for modules and Modems
- Hashcode for Safestrap, making all this possible!
Downloads Needed:
- Goldfinger ROM thread with Download links:
- http://forum.xda-developers.com/galaxy-s4-att/development/movin-please-posts-t2864506
- Patch thread with download links:
- http://forum.xda-developers.com/showthread.php?t=2674280
- Chainfire SuperSu Zip
- http://download.chainfire.eu/452/SuperSU/
- Surge1223 Modem and Modules:
- http://forum.xda-developers.com/showthread.php?t=2487298
- https://www.androidfilehost.com/?fid=23486521113837640
After everything is downloaded and moved to your SD-Card:
First install process - Easier, but may not always work properly:
1. Flash GoldFinger ROM and choose your preferences in Aroma
2. Flash Patch
a. inside aroma choose Full install, add Verizon features and build.prop, and no kernel)
3. SuperSu zip to get root back
4. Wi-Fi modules
5. Bootloader specific modem (optional, but highly recommended)
** If this install works and you get data, and sms, then great youre done! **
** After this install you will have the s4 phone and sms apps. If you would like to update to the S5 apps, there are a few ways to do that.
- Use this thread and follow install instructions as posted:
- http://forum.xda-developers.com/showthread.php?t=2676928
If the first method did not work for you, follow these instructions:
1. Download Goldfinger ROM to your PC
2. Download Verizon ROM (stock, echoe, hyperdrive, etc.)
3. Extract the Verizon ROM to wherever you like
4. Navigate to system > etc and find the file named "apns-config.xml"
5. Save the Verizon ROM apns-config.xml to your desktop
6. Now use 7zip, or a similar program and open the Goldfinger ROM
7. Navigate to system > etc and find the same apns-config.xml
8. Once you've located it, delete it.
9. Now, copy the "apns-config.xml" that you moved to your desktop, from your Verizon ROM, and place it in the same place that you deleted the old one from
10. After that, close out of 7zip and copy Goldfinger to your SD-Card
11. Now follow the normal install process posted above.
I hope everyone enjoys! If you like this ROM, please head over to the ROM thread and thank iB4STiD and let him know his work is appreciated!
Original Thread: http://forum.xda-developers.com/galaxy-s4-att/development/movin-please-posts-t2864506
Click to expand...
Click to collapse
What patch should be used?
The international patch. I have the link in the downloads section
luke24 said:
The international patch. I have the link in the downloads section
Click to expand...
Click to collapse
Yes, but which of them?
mitzael said:
Yes, but which of them?
Click to expand...
Click to collapse
Oh my bad haha.. Always use the latest one, V25.
I tried this. I used the 2nd method, changing out the apns config.xml file. After flashing, it seemed like it was going work, but never took me to the setup page. It just kept churning, then a haptic response like it was ready to go, then churning again, over and over. I really think I did this right, but maybe not. I really want this to work!
jrgthird said:
I tried this. I used the 2nd method, changing out the apns config.xml file. After flashing, it seemed like it was going work, but never took me to the setup page. It just kept churning, then a haptic response like it was ready to go, then churning again, over and over. I really think I did this right, but maybe not. I really want this to work!
Click to expand...
Click to collapse
Did you flash the patch as well?
Yep, 25
jrgthird said:
Yep, 25
Click to expand...
Click to collapse
Huh that's weird cause I installed it the dame way you did, using the 2nd method and everything runs great!
You cause always try again it could have been a bad flash, or use method #1. No one has had any problems with that method yet.
But to me it just sounds like a bad flash.
What selections in Aroma do you suggest? IE what phone version? What Kernel etc? I can't seem to get it to work.
jskala said:
What selections in Aroma do you suggest? IE what phone version? What Kernel etc? I can't seem to get it to work.
Click to expand...
Click to collapse
At&t safestrap version
No kernel if you're on safestrap
luke24 said:
At&t safestrap version
No kernel if you're on safestrap
Click to expand...
Click to collapse
Sorry I am on MDK Bootloader still.
jskala said:
Sorry I am on MDK Bootloader still.
Click to expand...
Click to collapse
Oh I'm not sure then.. I'm sorry I'm on SS.
On safestrap, it has been on the boot screen for a while and won't move.
mfun89 said:
On safestrap, it has been on the boot screen for a while and won't move.
Click to expand...
Click to collapse
This happened to me when trying to flash blackbox... no idea what I did wrong. They said it can happen when you don't wipe correctly.
Very interested in trying this out since it has the s5 power saving mode... I only get like one hour of on screen time with any rom as it is haha
vicariouscheese said:
This happened to me when trying to flash blackbox... no idea what I did wrong. They said it can happen when you don't wipe correctly.
Very interested in trying this out since it has the s5 power saving mode... I only get like one hour of on screen time with any rom as it is haha
Click to expand...
Click to collapse
Try out the echoe 29.1 port it has all of the s5 features you're looking for
mfun89 said:
On safestrap, it has been on the boot screen for a while and won't move.
Click to expand...
Click to collapse
Did you flash the signal bar fix? You will get a bootloop if you don't. And make sure you clean install it
What is this?
This is my Custom Rom built from Unova Ironman Firmware V1.1(2.2) 20141016
-This use a 3.4.67 Kernel
-For all those who have problems in installing via SP Flash Tool this is the easiest solution for updating the device to version 4.4.2. Besides being the basis for a custom rom is easily editable and customizable by anyone who wants
-Includes "Unova +" App for bluetooth notifications ( must install on your phone Unova Remind from Playstore and pairing the two devices)
Changes:
• Fix local setting
• Fix Auto reboot in startup
• Fix SystemUI crash
• Remove chinese App
• Include micro Gapps
• Volume control with Home button
• Home button replacing with Swipe App
• Fully rooted
• Flashable Zip Rom
Whats working:
• Phone
• Companion
• Data: 2G/3G
• Wi-Fi
• Bluetooth
• GPS/AGPS
• All other
Not Working/Bugs:
• SENSORS
Requires
• Latest TWRP installed on device
• Highly recommended flash the Rom starting from your Stock Rom (preserve the original partitions, NVRAM, etc) but not strictly necessary as it can also be installed on any version of firmware
Installation Instructions - DOWNLOAD ROM VERSION 1.1
1. download: Google-Drive - Mirror: Dev-Host
2. Copy "X201-KK-V1.1.zip" to Internal Storage
3. Restart device in recovery mode
4. Full Wipe
5. Install "X201-KK-V1.1.zip"
6. Wait for the installation
7. Restart after the first boot
Disclamer
This ROM is tested by me on Iconbit Callisto 100 but it can work on all units (4GB / 512MB 2100MHZ)
Obviously I do not assume any responsibility
Credits
-TeamWin Projects for TWRP
-User "acidbr" for sharing the Ironman Firmware http://forum.xda-developers.com/showpost.php?p=58693313&postcount=225
Can you post the Unova+ app here?
Never mind. Found it on Play Store.
Can you please post it somewhere where not EZDownloaderPro infects the download?
It takes ages to clean, I consider that a virus...
For the documentation:
Is the upgrade working when going directly from 4.2?
I have always had to Upgrade in SPFT.
Good if it is working using SPFT to only flash TWRP.
Have you noticed any changes in the ROM compared to the package kuronosan put together?
(You have done some changes to.)
I tried the Ironman ROM but did not see anything really.
gerhardo said:
Can you please post it somewhere where not EZDownloaderPro infects the download?
It takes ages to clean, I consider that a virus...
For the documentation:
Is the upgrade working when going directly from 4.2?
I have always had to Upgrade in SPFT.
Good if it is working using SPFT to only flash TWRP.
Have you noticed any changes in the ROM compared to the package kuronosan put together?
(You have done some changes to.)
I tried the Ironman ROM but did not see anything really.
Click to expand...
Click to collapse
I'll see if can upload somewhere else when I have time.
If any user wants to go before I can do that easily. thank him
You no longer need to use SPFT, you just flash my Rom. (Contains everything you need for a Firmware Upgrade) Council from stock 4.2 to get everything sorted but not strictly necessary. Can flash any version of departure.
I do not know which changes from the previous Unova Firmware because I come from the firmware Zgpax s8 modified by me.
Greetings
Hello
First of all, thanks you for your hard work.
I'd like to update my Truesmart 4.2 (512MB 2100MHZ) to 4.4 using your firmware. I'm quite ashamed to say it, but can you give me a step by step instructions please?
Not like I didn't try to search, but I find it quite hard. I don't know how to install TWRP. My unit is not rooted.
Can you confirm the step that I'm going to take ?
1) downloading openrecovery-twrp-2.7.1.0-omatesmartwatch2.img
2) Flashing my omate with this image thanks to MTK Flash Tool
3) Following your instructions
=> Concerning the 'Install Zip', do you mean 'ZipInstaller 5.0.3' ?
Between, I don't have window at all, I'm only using linux on my computer. I got a virtual console with windows, but the com and ADP port are not working there, if you have a solution to install TWRP not to using MTK Flash Tool (or windows), I'd be glad.
Thanks you for your advices !
shideneyu said:
Hello
First of all, thanks you for your hard work.
I'd like to update my Truesmart 4.2 (512MB 2100MHZ) to 4.4 using your firmware. I'm quite ashamed to say it, but can you give me a step by step instructions please?
Not like I didn't try to search, but I find it quite hard. I don't know how to install TWRP. My unit is not rooted.
Can you confirm the step that I'm going to take ?
1) downloading openrecovery-twrp-2.7.1.0-omatesmartwatch2.img
2) Flashing my omate with this image thanks to MTK Flash Tool
3) Following your instructions
=> Concerning the 'Install Zip', do you mean 'ZipInstaller 5.0.3' ?
Between, I don't have window at all, I'm only using linux on my computer. I got a virtual console with windows, but the com and ADP port are not working there, if you have a solution to install TWRP not to using MTK Flash Tool (or windows), I'd be glad.
Thanks you for your advices !
Click to expand...
Click to collapse
I proceeded to further clarify the installation instructions.
As for the installation of the Recovery google is your friend. Will surely find a way to install the recovery using Linux terminal
gerhardo said:
Can you please post it somewhere where not EZDownloaderPro infects the download?
It takes ages to clean, I consider that a virus...
For the documentation:
Is the upgrade working when going directly from 4.2?
I have always had to Upgrade in SPFT.
Good if it is working using SPFT to only flash TWRP.
Have you noticed any changes in the ROM compared to the package kuronosan put together?
(You have done some changes to.)
I tried the Ironman ROM but did not see anything really.
Click to expand...
Click to collapse
Upload rom on Google Drive :good:
rik81 said:
What is this?
This is my Custom Rom built from Unova Ironman Firmware V1.1(2.2) 20141016
-This use a 3.4.67 Kernel
-For all those who have problems in installing via SP Flash Tool this is the easiest solution for updating the device to version 4.4.2. Besides being the basis for a custom rom is easily editable and customizable by anyone who wants
-Includes "Unova +" App for bluetooth notifications ( must install on your phone Unova Remind from Playstore and pairing the two devices)
Changes:
• Fix local setting
• Fix Auto reboot in startup
• Fix SystemUI crash
• Remove chinese App
• Include micro Gapps
• Volume control with Home button
• Home button replacing with Swipe App
• Fully rooted
• Flashable Zip Rom
Whats working:
• Phone
• Companion
• Data: 2G/3G
• Wi-Fi
• Bluetooth
• GPS/AGPS
• All other
Not Working/Bugs:
• SENSORS
Requires
• Latest TWRP installed on device
• Highly recommended flash the Rom starting from your Stock Rom (preserve the original partitions, NVRAM, etc) but not strictly necessary as it can also be installed on any version of firmware
Installation Instructions - DOWNLOAD ROM VERSION 1.1
1. download: Google-Drive - Mirror: Dev-Host
2. Copy "X201-KK-V1.1.zip" to Internal Storage
3. Restart device in recovery mode
4. Full Wipe
5. Install "X201-KK-V1.1.zip"
6. Wait for the installation
7. Restart after the first boot
Disclamer
This ROM is tested by me on Iconbit Callisto 100 but it can work on all units (4GB / 512MB 2100MHZ)
Obviously I do not assume any responsibility
Credits
-TeamWin Projects for TWRP
-User "acidbr" for sharing the Ironman Firmware http://forum.xda-developers.com/showpost.php?p=58693313&postcount=225
Click to expand...
Click to collapse
Does this method stop 2G EDGE and make the signal appear?
Does not work for me on my north american model. I only get the boot logo forever.
stanelie said:
Does not work for me on my north american model. I only get the boot logo forever.
Click to expand...
Click to collapse
Sorry, only 512/4GB 2100Mhz EU version
rik81 said:
Sorry, only 512/4GB 2100Mhz EU version
Click to expand...
Click to collapse
Why does the Rom not work the 1GB EU version?
rik81 said:
Sorry, only 512/4GB 2100Mhz EU version
Click to expand...
Click to collapse
Works fine with my 1/8 May EU edition.
(still kind of testing, not noting much difference to the x202 ROM. I do not like HomeSwipe, that is a personal preference...)
gerhardo said:
Works fine with my 1/8 May EU edition.
(still kind of testing, not noting much difference to the x202 ROM. I do not like HomeSwipe, that is a personal preference...)
Click to expand...
Click to collapse
Well thank you for your feedback. I can only guarantee the version 512 / 4GB because in my possession, and I have personally tested. I do not know if the system partition and the kernel are the same. Now we know it.
Regarding the Home button could make a fix
rik81 said:
Well thank you for your feedback. I can only guarantee the version 512 / 4GB because in my possession, and I have personally tested. I do not know if the system partition and the kernel are the same. Now we know it.
Regarding the Home button could make a fix
Click to expand...
Click to collapse
Great ROM.
The Home button action can be overridden with Xposed Addtions module. It's good enough for me.
I wrote a small Xposed module to permanently enable the status bar in Nova Launcher (and most other launchers):
http://forum.xda-developers.com/xposed/modules/truesmart-status-bar-custom-launchers-t3063624
The module is only tested with your ROM. It might not work if GravityBox is enabled as well, I'm investigating that issue.
If you don't want to install Xposed I can provide recovery flashable zip's for enabling the status bar in either all apps or a specific launcher.
Help! my x201 is blocked on the logo UNOVA
Hello
I was on last firmware inconbit Callisto 100 and I tried to install "X201-KK-V1.1.zip" but I probably failed installing last TWRP. My watch is fixed on logo UNOVA and is not recognized on usb neither with SPFlash tool or MtkDroïd tools. The TWRP recovery dont see my Sdcard where I have my backup (Titanium). What can I do to awake my watch UMEOX x201 512/4 2100EU ?
Thanks a lot for helping me!
Hello,
What do i have to do with my omate truesmart after have change the file system\usr\keylayout\mtk-kpd.kl to the changes take effect?
I want key 102 to home button, like it is by default on the watch in the origin and every other roms.
I have already save and overwrite the file after changes, and then reboot omate, but still not working.
Thank you
My felicitations for your great job on this rom, and i have a question
First of all, i want to give you all my felicitations for your work and your rom unova kk for omate truesmart, it is very stable, fast, and battery saver compared to a lot of other roms.
I have European Model 2100 mhz of omate truesmart with 1 gb ram and 8 bg rom.
The only problem that i have with your rom is that i don't want that the home button put volume up, and i want it to go home like default.
How can i do to change it?
I already go to system\usr\keylayout\mtk-kpd.kl and changed the button 102 to HOME instead of VOLUME_UP and write WAKE_DROPPED instead of WAKE.
Also i reput the button 115 to VOLUME_UP instead of HOME and then i save and overwrite the file with es text editor in es explorer in root mode with supersu, and then i reboot the watch, but this still not working.
How do you have make to change the home button to volume_up?
Tell me please, so i can do it in the inverse way, and i'm sure this will work.
Thank very much for your work, you are a great dev
alvespassospaulo85 said:
My felicitations for your great job on this rom, and i have a question
First of all, i want to give you all my felicitations for your work and your rom unova kk for omate truesmart, it is very stable, fast, and battery saver compared to a lot of other roms.
I have European Model 2100 mhz of omate truesmart with 1 gb ram and 8 bg rom.
The only problem that i have with your rom is that i don't want that the home button put volume up, and i want it to go home like default.
How can i do to change it?
I already go to system\usr\keylayout\mtk-kpd.kl and changed the button 102 to HOME instead of VOLUME_UP and write WAKE_DROPPED instead of WAKE.
Also i reput the button 115 to VOLUME_UP instead of HOME and then i save and overwrite the file with es text editor in es explorer in root mode with supersu, and then i reboot the watch, but this still not working.
How do you have make to change the home button to volume_up?
Tell me please, so i can do it in the inverse way, and i'm sure this will work.
Thank very much for your work, you are a great dev
Click to expand...
Click to collapse
Ok i uploaded fix in attached files in the first post .
You may notice the difference by opening the file
Really very good rom, I installed it on TS 1gb/8gb 2100Mhz (I changed the baseband from original 1900Mhz). But with this rom I have some problem, in recovery TWRP I can't use my external SD card (twrp presents empty external_sd). With other variants of roms I didn't have this problem. If someone knows how to fix it?
Baseband
Any way you could post directions for baseband change? I have 2100 and live in US where 1900 mhz is needed for 3g data?
Thanks
This Rom Is ONLY for the G730A and the G730V variant of the s3 mini, i am not responsable if this bricks your phone. (this is untested on the G730V model but it should work)
How to Flash:
1. Root phone with KingoRoot and install SuperSu(must be superSU)
2. Install SafeStrap (click here for download)
3. Flash the Rom with gapps
Bugs:
WiFi doesn't work
Root
Power off/restart button doesn't work
You tell me
Features:
Deodexed
Zip aligned
Debloated
Faster than the regular rom
Download for G730A
Download for G730v
Credits:
KachowPow (for the boot animation)
Update: WiFi is working and the build will be uploaded soon!!!!!
turnert said:
Update: WiFi is working and the build will be uploaded soon!!!!!
Click to expand...
Click to collapse
Upload please deodexed rom for G730a with working wifi.
Thank you
Dr_Wolodya said:
Upload please deodexed rom for G730a with working wifi.
Thank you
Click to expand...
Click to collapse
I will upload it later today.
Dr_Wolodya said:
Upload please deodexed rom for G730a with working wifi.
Thank you
Click to expand...
Click to collapse
If you don't want to wait you should be able to unzip the current version and add this it the update script(META-INF/com/google/Android)
symlink("/system/lib/modules/prima/prima_wlan.ko", "/system/lib/modules/wlan.ko");
Then just compress the files back into a zip file and it should fix wifi.
Corrupt Zip File
Whenever I try to flash your ROM in Safestrap for my G-730A it always tells me I have a corrupt zip file and it is unable to flash it. I have tried to download it multiple times (the first time failed for the Mediafire link) and copy it back onto my SD card but to no avail. I have followed all the necessary steps to get this Samsung Galaxy S3 Mini somewhat custom ROM ready. I installed the busybox scripts, enabled safestrap, set the SELinux mode to permissive, installed Xposed and the libraries, now I just need to know how to flash a modded version of the Kitkat 4.4.2 stock ROM onto this device properly. Do you have another version that's more stable, or possibly even a link to an entirely different de-bloat ROM? Thanks!
ROMmon1941 said:
Whenever I try to flash your ROM in Safestrap for my G-730A it always tells me I have a corrupt zip file and it is unable to flash it. I have tried to download it multiple times (the first time failed for the Mediafire link) and copy it back onto my SD card but to no avail. I have followed all the necessary steps to get this Samsung Galaxy S3 Mini somewhat custom ROM ready. I installed the busybox scripts, enabled safestrap, set the SELinux mode to permissive, installed Xposed and the libraries, now I just need to know how to flash a modded version of the Kitkat 4.4.2 stock ROM onto this device properly. Do you have another version that's more stable, or possibly even a link to an entirely different de-bloat ROM? Thanks!
Click to expand...
Click to collapse
My suggestion would just be to manually debloat the rom by just uninstalling all the useless system apps. The stock rom I made is very buggy and because you can't root on this rom you have to flash back to stock with Odin if something goes wrong. I can try and reupload to Google drive if that helps, but I am unable to test it because I bricked all 3 of my s3 mini's. I also ported another rom called tencent os but that has more bugs than this one so it's not worth using.
Noted
turnert said:
My suggestion would just be to manually debloat the rom by just uninstalling all the useless system apps. The stock rom I made is very buggy and because you can't root on this rom you have to flash back to stock with Odin if something goes wrong. I can try and reupload to Google drive if that helps, but I am unable to test it because I bricked all 3 of my s3 mini's. I also ported another rom called tencent os but that has more bugs than this one so it's not worth using.
Click to expand...
Click to collapse
I will take you suggestion and just do the following on the stock ROM manually. I will heed your advice that the ROM you created just isn't ready for primetime, and I would honestly rather trade stability for convenience any day. You don't have to go to the trouble of re-uploading a new one to Google Drive if you don't want to. Speaking of Tencent OS, while I was doing research for this device on XDA that did come up in the search results. I thought nothing of it and I didn't even look at the author of it, but I'm pretty sure it was you Turnert. At this point I think I will just stick to the stock 4.4.2 image and stop looking for what isn't there.
UPDATE: I was able to get the number of system apps down to about 150. So far so good, initially there was some black screens and random apps opening after the preliminary uninstall. All seems to be fine after a soft reset though. I'm liking the performance and the added storage benefit without all that bloatware running in the background taking up room.
ROMmon1941 said:
I will take you suggestion and just do the following on the stock ROM manually. I will heed your advice that the ROM you created just isn't ready for primetime, and I would honestly rather trade stability for convenience any day. You don't have to go to the trouble of re-uploading a new one to Google Drive if you don't want to. Speaking of Tencent OS, while I was doing research for this device on XDA that did come up in the search results. I thought nothing of it and I didn't even look at the author of it, but I'm pretty sure it was you Turnert. At this point I think I will just stick to the stock 4.4.2 image and stop looking for what isn't there.
UPDATE: I was able to get the number of system apps down to about 150. So far so good, initially there was some black screens and random apps opening after the preliminary uninstall. All seems to be fine after a soft reset though. I'm liking the performance and the added storage benefit without all that bloatware running in the background taking up room.
Click to expand...
Click to collapse
Honestly I might buy an s3 mini and see if I can improve this rom a bit considering it's been quite a while since I've done any work on this device. I would love to work on this device again and see if I could maybe get aosp or something running on it even if it's not very likely that aosp will ever run on it.
Hi guys! is this 4.4.2 because basically 4.4.4 was never released for this phone? thx.
kbuss said:
Hi guys! is this 4.4.2 because basically 4.4.4 was never released for this phone? thx.
Click to expand...
Click to collapse
Ya its 4.4.2 it may show 4.4.4 but it's not.