Database Develop

[STOCK][C6602&C6603][4.2.2] Update to 10.3.A.0.423 [Rooted & XZDualRecovery][LB/UB]

[STOCK][C6602&C6603][4.2.2] Update to 10.3.A.0.423 [Rooted & XZDualRecovery][LB/UB]
Requirements:
Flashtool by @Androxyde
XZDualRecovery 2.5 BETA
Current FW version: 10.1.A.1.350, 10.1.A.1.434, 10.1.1.A.1.253 or 10.1.1.A.1.307 all can be updated!
Special features:
Superuser integrated in system, FULL root, no reboots when remounting /system RW!
XZDualRecovery 2.5 BETA (CWM 6.0.3.2 & TWRP 2.5.0.0) pre-installed;
Tailored FTF to minimize the chance of accidental system wiping!
No need to clear caches!
@shem2409 created a nice youtube video guide to assist you in your work, be sure to check this post for it! Thanks m8!
In the following guide I suggest you use an external SDCard but that's just good practice, you can use your internal storage or even an USB OTG storage device in TWRP if you like to install, that's no problem!... If you are modding and the likes, best is to have an external sdcard, just for safeties sake.
C6602: How to update to 10.3.A.0.423:
NOTE: STICK TO THIS ORDER AND STEPS!!
For C6602: Download C6602.flashable.423.zip (Bittorrent: 686MB) and C6602_10.3.A.0.423-stripped.ftf (15MB), save it somewhere you remember;
Put 'C6602.flashable.423.zip' on (the external) SDcard1;
Put 'C6602_10.3.A.0.423-stripped.ftf' inside the Flashtool/firmwares folder;
Create a backup of your phone in CWM or TWRP and don't forget to backup the contents of 'SDCard0';
Flash 'C6602.flashable.423.zip' in TWRP, do not reboot but go back to the main menu, then go to reboot->power off;
Flash everything in 'C6602_10.3.A.0.423-stripped.ftf';
Reboot to system without clearing (dalvik-/)cache.
C6603: How to update to 10.3.A.0.423:
NOTE: STICK TO THIS ORDER AND STEPS!!
For C6603: Download C6603.flashable.423.zip (Bittorrent: 719MB) and C6603_10.3.A.0.423-stripped.ftf (15MB), save it somewhere you remember;
Put 'C6603.flashable.423.zip' on (the external) SDcard1;
Put 'C6603_10.3.A.0.423-stripped.ftf' inside the Flashtool/firmwares folder;
Create a backup of your phone in CWM or TWRP and don't forget to backup the contents of 'SDCard0';
Flash 'C6603.flashable.423.zip' in TWRP, do not reboot but go back to the main menu, then go to reboot->power off;
Flash everything in 'C6603_10.3.A.0.423-stripped.ftf';
Reboot to system without clearing (dalvik-/)cache.
The first boot will be considerably slower and after a long wait at the boot animation you will see Android optimizing the apps on your phone.
After updating your NFC firmware and some update information has been displayed, all is done!
I have done this myself, using my own method and I have not found any problem yet, again! :fingers-crossed:
Enjoy! :victory:
Known XZDualRecovery Issues:
TWRP Usage warning: It seems TWRP 2.5.0.0 has issues with the internal storage, which seem related to the changes made to support encrypted storage volumes... This means the internal storage sometimes shows up almost empty (just folders) and no files. Try to use CWM when that happens.
Busybox Updater/Installer: If you have XZDualRecovery installed, un-install any Busybox updating app/tool as most if not all of them will install a version of busybox which does not support the lzma compression applets XZDualRecovery depends on. The version installed together with XZDualRecovery is very stable and I have yet to hear anyone complain about it's stability.
How to report errors:
Please, before shouting out "It doesn't work!!1!" or "I lost root!" or even "My phone reboots when remounting /system RW!!" try the following:
Restore a /system ONLY using any means you are familiar with so you can try again.
Root it using [Z][ROOT] DooMLoRD Easy Rooting Toolkit.
Install XZDualRecovery and then try to update again using TWRP. This time you can skip the FTF as it has already done it's job.
If it still fails something from there on: LOGS!!.
NOTE: The important ones can be found in /cache/recovery and in /tmp/XZDualRecovery, pack them up and send them to me.
Thank you
Flashable ROM Mutator:
Download AROMA ROM Mutator 0.14
This (former patch package) uses AROMA to create a user friendly menu to choose between updates to be installed.
If you want to switch from SuperSU (default in this ROM) to SuperUser (Be careful, SuperUser is incompatible with 4.2.2!) you can use this to make the change.
If you have the reboot problem when trying to remount /system writable, you can reinstall the superuser app of your preference, it's installation includes the latest patch.
If you are missing /system/bin/chargemon.stock and you want to be able to charge your phone while it's turned off.
Flash using one of the recoveries!
Version 0.13 and upwards is using AROMA 2.70B1 or better, the below warning can be ignored for now. Let me know how it performs!
AROMA Warning: AROMA currently works best in TWRP but even there it has some issues on the Z/ZL. It sometimes does not start up correctly or it has a 'sticky button' issue. It makes it a little less easy to use but this will be fixed in time. It is a combination problem caused by the new hardware and incompatibility with it and the fact the recoveries both have been updated considerably to work on the latest phones, causing issues with some functionality of AROMA.
If it hangs when trying to start, reboot your phone and try again.
If it has the sticky buttons, press the button again to activate.
You can avoid the sticky buttons by pressing them for about half a second (that means not too short and not too long). It will work, it's just showing a bug associated with the latest recoveries.
The Samsung S4, HTC One and One X and the Nexus 4 & 7 show the same issues. For them AROMA sometimes crashes, this is an issue i have not yet observed on the Z/ZL.
Thanks go to @Androxyde for the FTF creation, cheers m8!

nice! so does that mean we dont need to factory wipe before upgrading? I thought if we go across versions (4.1.2 > 4.2.2) you gotta wipe all your stuff first.

After flashing the stripped ftf, the phone doesn't go into recovery. It shows green light, Sony logo and nothing else. Then it just reboot again. Already tried downloaing the file and flashing again. still the same problem.

Ya, I need manual install dual boot to access back to CWM/TWRP then just can install but the preinstall superuser root is not working at all.
Root working back by installing DooMLoRD Easy Rooting Toolkit (v15) - http://forum.xda-developers.com/showthread.php?t=2327472

Is there any reason why the dalvik cache are not wiped in this release process?
Is it simply a speed/optimisation thing, or will it cause issues if it happens?

Comming from PAC... Do i need to install other Stock rom before update or just use the instructions above? thanks.

Ok, so this is what ive done to get this to boot, on existing rom with recovery installed I flashed the .432.zip, obviously it bootlooped, but then flashed the ftf file which got the rom to boot. Then rooted and installed recovery as Andrewtst has linked to above.
Cheers.

Can't download the zip and ftf file, doesnt work, anyone can confirm that? can you reuploading or verify if is everything ok, thx for the work you done.

zanndoth said:
After flashing the stripped ftf, the phone doesn't go into recovery. It shows green light, Sony logo and nothing else. Then it just reboot again. Already tried downloaing the file and flashing again. still the same problem.
Click to expand...
Click to collapse
I got into the same problem, and cannot get out. Anyone has any advice?

please fix dead links

dopeee said:
nice! so does that mean we dont need to factory wipe before upgrading? I thought if we go across versions (4.1.2 > 4.2.2) you gotta wipe all your stuff first.
Click to expand...
Click to collapse
I found out with the leak by doomlord that it would be possible to update, no need to wipe, the official update works even better
lysp said:
Is there any reason why the dalvik cache are not wiped in this release process?
Is it simply a speed/optimisation thing, or will it cause issues if it happens?
Click to expand...
Click to collapse
It's meant as an update process and not wiping anything will make the ROM treat your phone as one that just got updated
Faelz said:
Comming from PAC... Do i need to install other Stock rom before update or just use the instructions above? thanks.
Click to expand...
Click to collapse
Yes, you need a stock ROM before you can flash this, I would not recommend updating your phone from PAC...
bungknees said:
Ok, so this is what ive done to get this to boot, on existing rom with recovery installed I flashed the .432.zip, obviously it bootlooped, but then flashed the ftf file which got the rom to boot. Then rooted and installed recovery as Andrewtst has linked to above.
Cheers.
Click to expand...
Click to collapse
&
zanndoth said:
After flashing the stripped ftf, the phone doesn't go into recovery. It shows green light, Sony logo and nothing else. Then it just reboot again. Already tried downloaing the file and flashing again. still the same problem.
Click to expand...
Click to collapse
&
chuazy said:
I got into the same problem, and cannot get out. Anyone has any advice?
Click to expand...
Click to collapse
I have modified the guide a bit as i should have done before i posted it...
Restore the kernel to anything other then the 4.2.2 one and then try to flash the update package, after flashing the update, re-flash the kernel.
I made one error in my guide: If someone is not using the correct version of XZDualRecovery (2.5 BETA) then you lose recovery when on the 4.2.2 kernel. The correct steps order to prevent this from happening are now in the OP.

please fix dead links

calvinleeabc said:
please fix dead links
Click to expand...
Click to collapse
+1

After flashing this Rom, my data is still at Data/media but not on the default path, what should i do in this case? should i move the data from data/media to new location manually?

calvinleeabc said:
please fix dead links
Click to expand...
Click to collapse
buciupetru said:
Can't download the zip and ftf file, doesnt work, anyone can confirm that? can you reuploading or verify if is everything ok, thx for the work you done.
Click to expand...
Click to collapse
Sorry guys, the server is under a heavy load at the moment... the webserver lost a few workers that ate up much of the cpu time. I've killed them all and restarted the webserver.
IF the problem was caused by that, it's solved now

lethalfriend said:
After flashing this Rom, my data is still at Data/media but not on the default path, what should i do in this case? should i move the data from data/media to new location manually?
Click to expand...
Click to collapse
No need: /data/media IS the 'new' location.

[NUT] said:
Sorry guys, the server is under a heavy load at the moment... the webserver lost a few workers that ate up much of the cpu time. I've killed them all and restarted the webserver.
IF the problem was caused by that, it's solved now
Click to expand...
Click to collapse
thanks:good:efficient

[NUT] said:
No need: /data/media IS the 'new' location.
Click to expand...
Click to collapse
But strangely, my phone isn't detecting the media from the above path, its just showing the pictures form newly created DCIM folder which is on a different location

lethalfriend said:
But strangely, my phone isn't detecting the media from the above path, its just showing the pictures form newly created DCIM folder which is on a different location
Click to expand...
Click to collapse
Ooh... i now see what you mean... you are correct. I'll patch up the flashable package to do it automatically.
For you, use a file explorer to move the contents (skipping the 0 folder) of /data/media to /data/media/0/. Sorry man, i missed that completely on my phone

server stilll unreachable.

Needed: stock "install-recovery.sh"

can someone please upload the stock "install-recovery.sh"?
It's located in /system/etc.
I forgot to backup it, while rooting the device.
I need it for the OTA updates.
thanks

@vel_tins
Do not flash the ota if you are rooted, you might get bootloop. Full unroot your device before attempting to update. Anyhow, the ota will most likely fail since you already modified your system partition. Your best option is to unroot your device and capture the ota link, modify the ota updater-script and remove the lines that are showing "unexpected contents" errors. The original "install-recovery.sh" is still there, supersu renamed it to something like "/system/etc/install-recovery_original.sh". Keep in mind, you might loose your custom recovery if you renamed it back to "install-recovery.sh".

Well, OTA was a pain in the a**.
Because I had no stock "install-recovery.sh", I've edited the updater-script and removed all the matching entries.
Executed a full un-root.
Tried to flash the modified update.zip via TWRP, but failed because TWRP couldn't mount partitions with this name scheme:
Code:
"/dev/block/platform/[B]7824900.sdhci/by-name/system[/B]", "/system",
(will investigate later, any ideas?)
Because too lazy to modify the updater-script again,
I've booted into fastboot and loaded my "modded" stock recovery, which accepts also self-signed .zips.
Flashing worked well, but on reboot, I got a nice bootloop because of the formerly installed Xposed framework.
Had to restore from a Nandroid Backup and after reboot, I removed Xposed completely.
Eventually, I was able to flash the OTA and got back a working device...
Gosh...

^^
??

vel_tins said:
Well, OTA was a pain in the a**.
Because I had no stock "install-recovery.sh", I've edited the updater-script and removed all the matching entries.
Executed a full un-root.
Tried to flash the modified update.zip via TWRP, but failed because TWRP couldn't mount partitions with this name scheme:
Code:
"/dev/block/platform/[B]7824900.sdhci/by-name/system[/B]", "/system",
(will investigate later, any ideas?)
Because too lazy to modify the updater-script again,
I've booted into fastboot and loaded my "modded" stock recovery, which accepts also self-signed .zips.
Flashing worked well, but on reboot, I got a nice bootloop because of the formerly installed Xposed framework.
Had to restore from a Nandroid Backup and after reboot, I removed Xposed completely.
Eventually, I was able to flash the OTA and got back a working device...
Gosh...
Click to expand...
Click to collapse
If you still have the original OTA zip, can you please post it for future reference?
As for TWRP mounting /dev/block/platform/7824900.sdhci/by-name/system, what error message did you get? Try running "ls -l /dev/block/platform/7824900.sdhci/by-name/" in both normal Android and TWRP, then compare the results.

pawitp said:
If you still have the original OTA zip, can you please post it for future reference?
Click to expand...
Click to collapse
No problem
pawitp said:
As for TWRP mounting /dev/block/platform/7824900.sdhci/by-name/system, what error message did you get? Try running "ls -l /dev/block/platform/7824900.sdhci/by-name/" in both normal Android and TWRP, then compare the results.
Click to expand...
Click to collapse
Stock and Cyanogen recovery are working with this partition naming scheme.
But in TWRP, I get the following error message:
Code:
ls: /dev/block/platform/7824900.sdhci/by-name: No such file or directory
For TWRP I have to use the following syntax in recovery.fstab:
Code:
/cache ext4 /dev/block/mmcblk0p29
/system ext4 /dev/block/mmcblk0p25
/data ext4 /dev/block/mmcblk0p31 length=-16384
.........etc.

vel_tins said:
No problem
Stock and Cyanogen recovery are working with this partition naming scheme.
But in TWRP, I get the following error message:
Code:
ls: /dev/block/platform/7824900.sdhci/by-name: No such file or directory
For TWRP I have to use the following syntax in recovery.fstab:
Code:
/cache ext4 /dev/block/mmcblk0p29
/system ext4 /dev/block/mmcblk0p25
/data ext4 /dev/block/mmcblk0p31 length=-16384
.........etc.
Click to expand...
Click to collapse
On TWRP, try running "find /dev/block/platform" and see if anything is created there.
The directory should have been populated by init. See https://android.googlesource.com/pl...0ab94b7d5a888f0b6920b156e5c6a075fa0741a^!/#F0.
That code should also be in TWRP, but something might have prevented it from working properly on this device. You might find some clues in dmesg or TWRP's logs.

Well, eventually I've got it.
In TWRP, the naming is a little bit different from stock or Cyanogen recovery.
I had to change:
Code:
/dev/block/platform/[COLOR="Red"]7824900.sdhci[/COLOR]/by-name/cache <--- STOCK
to
/dev/block/platform/[COLOR="Blue"]soc.0[/COLOR]/by-name/cache <--- TWRP
However, the "/dev/block/mmcblk0p" naming worked also in TWRP, so this was only a minor issue.

vel_tins said:
Well, eventually I've got it.
In TWRP, the naming is a little bit different from stock or Cyanogen recovery.
I had to change:
Code:
/dev/block/platform/[COLOR="Red"]7824900.sdhci[/COLOR]/by-name/cache <--- STOCK
to
/dev/block/platform/[COLOR="Blue"]soc.0[/COLOR]/by-name/cache <--- TWRP
However, the "/dev/block/mmcblk0p" naming worked also in TWRP, so this was only a minor issue.
Click to expand...
Click to collapse
IMO, you should fix TWRP so that it has the same naming convention. Otherwise OTA packages using the "stock" naming convention can't be flashed on TWRP.
Personally, I prefer the "by-name" mapping rather than the "/dev/block/mmcblk0p" because it is harder to make mistakes if you use a name. With numbers, if a wrong number is typed, then you might end up flashing the wrong partition and bricking the device.
EDIT: It might have something to do with the "system/core" repository you've used to build your recovery. Which Android tree did you use to build Cyanogen Recovery and which one did you use to build TWRP?

vel_tins said:
Well, OTA was a pain in the a**.
Because I had no stock "install-recovery.sh", I've edited the updater-script and removed all the matching entries.
Executed a full un-root.
Tried to flash the modified update.zip via TWRP, but failed because TWRP couldn't mount partitions with this name scheme:
Code:
"/dev/block/platform/[B]7824900.sdhci/by-name/system[/B]", "/system",
(will investigate later, any ideas?)
Because too lazy to modify the updater-script again,
I've booted into fastboot and loaded my "modded" stock recovery, which accepts also self-signed .zips.
Flashing worked well, but on reboot, I got a nice bootloop because of the formerly installed Xposed framework.
Had to restore from a Nandroid Backup and after reboot, I removed Xposed completely.
Eventually, I was able to flash the OTA and got back a working device...
Gosh...
Click to expand...
Click to collapse
Hi sir ,
Please share to us , how you do this , because I have status 7. Install-recovery.sh problem
I have stock recovery , and I'm only make a root for my device by kingroot .
Please share update.zip file and tel me how to make ota update

pawitp said:
IMO, you should fix TWRP so that it has the same naming convention. Otherwise OTA packages using the "stock" naming convention can't be flashed on TWRP.
Click to expand...
Click to collapse
Exactly this is the point...
pawitp said:
EDIT: It might have something to do with the "system/core" repository you've used to build your recovery. Which Android tree did you use to build Cyanogen Recovery and which one did you use to build TWRP?
Click to expand...
Click to collapse
I have to correct myself, Cyanogen has exactly the same problem.
I've used the latest CM 12.1 and Omnirom source trees to build TWRP, but with the same result.
TWRP/Cyanogen only detects "soc.0" instead of "7824900.sdhci" and that will break compatibility with OTA packages (Until you patch "updater-script").

So how you made this ota update after all ?

theeteempire said:
So how you made this ota update after all ?
Click to expand...
Click to collapse
OTA doesn't work with rooted devices.
Do a full un-root and try again.

vel_tins said:
OTA doesn't work with rooted devices.
Do a full un-root and try again.
Click to expand...
Click to collapse
I did it , full unroot , I couldn't update even that with full-unroot , I used kingroot for root ,
Also error status 7 , install-recovery. Sh shown on the update after full-unroot my device !!!
can you help me please !!!!!

theeteempire said:
....I used kingroot for root ,
Also error status 7 , install-recovery. Sh shown on the update after full-unroot my device...
Click to expand...
Click to collapse
I would strongly suggest, to open an new thread, because I guess a lot more people will or had run into these issues.
I don't know what Kingsoft (never used it) has modified/replaced, so in your case I would search for a stock "install-recovery.sh" and replace the modified.
Everything else would be too complicated. (You have read my post on the first page).

vel_tins said:
I would strongly suggest, to open an new thread, because I guess a lot more people will or had run into these issues.
I don't know what Kingsoft (never used it) has modified/replaced, so in your case I would search for a stock "install-recovery.sh" and replace the modified.
Everything else would be too complicated. (You have read my post on the first page).
Click to expand...
Click to collapse
So I need the stock install-recovery. Sh ,.
Are you have it ?

vel_tins said:
Exactly this is the point...
I have to correct myself, Cyanogen has exactly the same problem.
I've used the latest CM 12.1 and Omnirom source trees to build TWRP, but with the same result.
TWRP/Cyanogen only detects "soc.0" instead of "7824900.sdhci" and that will break compatibility with OTA packages (Until you patch "updater-script").
Click to expand...
Click to collapse
This is just a guess. Try adding "TARGET_PLATFORM_DEVICE_BASE := /devices/soc.0/" to BoardConfig.mk.
If you know C, you might want to try mucking around in system/core/init/devices.c and see why it's behaving that way.

pawitp said:
This is just a guess. Try adding "TARGET_PLATFORM_DEVICE_BASE := /devices/soc.0/" to BoardConfig.mk.
.....
Click to expand...
Click to collapse
Seems to work, thanks!
PS: A google search for "TARGET_PLATFORM_DEVICE_BASE" threw only six results, so it doesn't seem to be a very popular flag.

vel_tins said:
Seems to work, thanks!
PS: A google search for "TARGET_PLATFORM_DEVICE_BASE" threw only six results, so it doesn't seem to be a very popular flag.
Click to expand...
Click to collapse
From my experience, you can't rely too much on Google for ROM development. I've found the flag by reading the source file I've previously mentioned.
Sent from my Nexus 4 using XDA Free mobile app

Something about TWRP recovery

Hi guys, I have got a very urgent problem right now, and hope someone can help me out...I am currently using a HTC One M7, and I used the TWRP recovery and the official bootloader or something rooted my phone, the reason why I need root it is that i need a app move into the system apps which may be easier in using it. And after I moved the app into the system apps using Root Explorer and then reboot my phone, the app just disappeared. After tried many times...I think it is because of the twrp just wipe it... do u guys have a method to solve this problem?...really...pls help me out!!

luvu4evermore said:
Hi guys, I have got a very urgent problem right now, and hope someone can help me out...I am currently using a HTC One M7, and I used the TWRP recovery and the official bootloader or something rooted my phone, the reason why I need root it is that i need a app move into the system apps which may be easier in using it. And after I moved the app into the system apps using Root Explorer and then reboot my phone, the app just disappeared. After tried many times...I think it is because of the twrp just wipe it... do u guys have a method to solve this problem?...really...pls help me out!!
Click to expand...
Click to collapse
This is not a twrp issue, /system partition is write-protected by the stock kernel, every changes made in the /system partition will be reverted after a reboot. If you want to be able to write to /system when booted in the rom, you'll need a custom kernel with write-protection disabled (pretty much all custom kernels here have this). The other option is to make the changes you want in your /system partition before the stock kernel boots, so using the embedded file manager of twrp recovery for example.
If you want to use a custom kernel, you must choose one that works with your rom type and version. For example, ElementalX kernel will only works for Sense or GPE rom (stock or custom). The version of ElementalX required depends on your android version so newer doesn't mean better, you need the right one. Flashing a custom recovery is done using twrp recovery. When installing the custom kernel, you can choose the features you want to be installed so if you don't want a specific feature that the kernel offers, its not a problem. The write-protection is removed by default.
If using the twrp file manger, boot in twrp select "advanced" ---> "file manager"
Then to move a file, select it (tap on it) then it will open another menu. Select "move" then select the location you want to move it to. There is also a chmod menu to edit the files permissions.

alray said:
This is not a twrp issue, /system partition is write-protected by the stock kernel, every changes made in the /system partition will be reverted after a reboot. If you want to be able to write to /system when booted in the rom, you'll need a custom kernel with write-protection disabled (pretty much all custom kernels here have this). The other option is to make the changes you want in your /system partition before the stock kernel boots, so using the embedded file manager of twrp recovery for example.
Click to expand...
Click to collapse
Oh, thanks for answering me~ uh, can u be more specific about how to do that? about the kernel thing? I never did this before and actually this is just my second time to root a phone and try to move an app into system app (as last time i did so there is no such a problem...) Also, about the twrp recovery file manager, tried that one yesterday, and it did not show the " app" folder under the system one, which means i just cannot move it using the twrp file manager...

luvu4evermore said:
Oh, thanks for answering me~ uh, can u be more specific about how to do that? about the kernel thing? I never did this before and actually this is just my second time to root a phone and try to move an app into system app (as last time i did so there is no such a problem...) Also, about the twrp recovery file manager, tried that one yesterday, and it did not show the " app" folder under the system one, which means i just cannot move it using the twrp file manager...
Click to expand...
Click to collapse
see my post above (edited while you were replying)
You can also use aroma file manager within twrp recovery
here a nice xda-video about both twrp file manger and aroma file manager

alray said:
see my post above (edited while you were replying)
You can also use aroma file manager within twrp recovery
here a nice xda-video about both twrp file manger and aroma file manager
Click to expand...
Click to collapse
OMFG!!! Finally I made it! I watched the video and find out that I did not mount the permission to the TWRP file manager! Thank you so much!!!

luvu4evermore said:
OMFG!!! Finally I made it! I watched the video and find out that I did not mount the permission to the TWRP file manager! Thank you so much!!!
Click to expand...
Click to collapse
Yep sorry, should have mentioned that, you always have to mount the partition you want to access when using a recovery. Some are mounted by default, but /system isn't.

alray said:
Yep sorry, should have mentioned that, you always have to mount the partition you want to access to when using a recovery.
Click to expand...
Click to collapse
Nah, still thanks a lot,

luvu4evermore said:
Nah, still thanks a lot,
Click to expand...
Click to collapse
you're welcome :good:

Canadian S5 (900W8) 5.1.1 Oficial Update

Koodo Mobile: http://downloadmirror.co/android/tq/G900W8VLU1COI4_G900W8OYA1COI4_KDO.zip
SaskTel: http://downloadmirror.co/android/tr/G900W8VLU1COI4_G900W8OYA1COI4_BWA.zip
Virgin Mobile: http://downloadmirror.co/android/ts/G900W8VLU1COI4_G900W8OYA1COI4_VMC.zip
Bell Mobil: http://downloadmirror.co/android/tt/G900W8VLU1COI4_G900W8OYA1COI4_BMC.zip
Rogers: http://downloadmirror.co/android/tu/G900W8VLU1COI4_G900W8OYA1COI4_RWC.zip
Telus: http://downloadmirror.co/android/tv/G900W8VLU1COI4_G900W8OYA1COI4_TLS.zip
Fido Mobile: http://downloadmirror.co/android/tw/G900W8VLU1COI4_G900W8OYA1COI4_FMC.zip
Source: http://www.theandroidsoul.com/downl...1-update-g900w8vlu1coi4-with-root-info-85381/

Nice, which I've would I download for Wind Mobile?

If Flash fire shows protected on some partitions does that mean I have to use Odin on PC?

Spacemonkie4207 said:
Nice, which I've would I download for Wind Mobile?
Click to expand...
Click to collapse
The Wind Mobile firmware is always released under its parent company's name, Globalive, which is not listed here. It's CSC is GLO if you can find it elsewhere. But it really doesn't matter at all. The last few releases that were labelled Globalive were literally just the Bell version renamed. You can use any of the firmware versions above if you want. I used the Telus one a couple of times, just because I have a grudge against Bell and Rogers. But it makes absolutely no difference.

hexavoodoomal said:
The Wind Mobile firmware is always released under its parent company's name, Globalive, which is not listed here. It's CSC is GLO if you can find it elsewhere. But it really doesn't matter at all. The last few releases that were labelled Globalive were literally just the Bell version renamed. You can use any of the firmware versions above if you want. I used the Telus one a couple of times, just because I have a grudge against Bell and Rogers. But it makes absolutely no difference.
Click to expand...
Click to collapse
Where can I find the proper apn settings?

Zehlek said:
If Flash fire shows protected on some partitions does that mean I have to use Odin on PC?
Click to expand...
Click to collapse
use odin in pc

Spacemonkie4207 said:
Where can I find the proper apn settings?
Click to expand...
Click to collapse
Google it.

Whats new ?
Whhats new on 5.1.1 theme store coming out with this ? What can i find
Plz some one upload captures

brayhanrd said:
Whhats new on 5.1.1 theme store coming out with this ? What can i find
Plz some one upload captures
Click to expand...
Click to collapse
I have 900M so i cant install, maybe anyone can post anything, but 99% sure didnt have themes
Enviado de meu SM-G900F usando Tapatalk

brayhanrd said:
Whhats new on 5.1.1 theme store coming out with this ? What can i find
Plz some one upload captures
Click to expand...
Click to collapse
I think it is more under the hood updates
Sent from my SM-G900W8 using Tapatalk

Anyone figure out how to root this version. I tried to install TWRP and flashed Super SU, cleared cache and dalvik but it just boot loops on first boot after flashing firmware. Tried to install after it booted and set up user name and accounts by the same process but I had the same results.
Any suggestions?
Thanks.

daroco said:
Anyone figure out how to root this version. I tried to install TWRP and flashed Super SU, cleared cache and dalvik but it just boot loops on first boot after flashing firmware. Tried to install after it booted and set up user name and accounts by the same process but I had the same results.
Any suggestions?
Thanks.
Click to expand...
Click to collapse
Only with custom kernel
Enviado de meu SM-G900F usando Tapatalk

Thanks bro! I thought about it but I didn't think it mattered. I'll give it a go.
No dice as of yet, custom kernels are not booting either, good thing I had the sense to do a bacup first
☺

daroco said:
Thanks bro! I thought about it but I didn't think it mattered. I'll give it a go.
No dice as of yet, custom kernels are not booting either, good thing I had the sense to do a bacup first
Click to expand...
Click to collapse
The way I usually root is to flash CF-Auto-Root-kltecan-kltevl-smg900w8.tar using odin. Can you try that?
I haven't updated yet until I'm sure root is there as I gave the phone to my wife.

thanks

Still bootloops when I flashed CF-Autoroot. it also installed the original recovery from another BL version. I reflashed TWRP and cleared cache and dalvik (not that I expected it to do much) but still the same. restored a nandroid and I had all kinds of apps FC. End result was to factory reset the phone to be in a stable condition. If this was a car I could get this damn thing running right! I should have learned more about programming while I was in school...... 2 kids and a mortgage I have no time for it now.

[HOWTO] Root your 5.1.1 G900W8VLU1COI4 firmware
daroco said:
Anyone figure out how to root this version. I tried to install TWRP and flashed Super SU, cleared cache and dalvik but it just boot loops on first boot after flashing firmware. Tried to install after it booted and set up user name and accounts by the same process but I had the same results. [...]
Click to expand...
Click to collapse
mauriicio21 said:
Only with custom kernel
Click to expand...
Click to collapse
Not exactly
You need stock kernel but with sepolicy patched in ramdisk, according to @Chainfire's method.
I think I could help all G900W8's users
Rooting procedure (requires TWRP or CWM):
1. Download patched kernel and the latest SuperSU (2.52+):
>> KERNEL_G900W8VLU1COI4_Stock_patched.zip <<
>> SuperSU BETA by @Chainfire <<
2. Copy both zip files to phone or extSdCard
3. Go to TWRP / CWM and flash both files one by one. Order does not matter
4. Reboot the phone.
5. Enjoy your rooted 5.1.1 firmware
-------------------------------------------------------------------------------------------
It is time to say that I also need your help as there is no 5.1.1 firmware for other S5's variants yet. I need updated SELinux contexts and and permissions list from your 5.1.1 firmware (in all Snapdragon S5 variants contexts/permissions are the same). I require it as I would like to be well prepared with my custom ROMs for G900F/FD. I believe that Android 5.1.1 for G900F/FD is just a matter of a few days...
Please do as follow while running G900W8VLU1COI4 firmware:
- Install Terminal Emulator from Play Store (https://play.google.com/store/apps/details?id=jackpal.androidterm)
- Type commands as follow:
Code:
[COLOR="Red"]su[/COLOR]
cd /system
ls -aRZ > /storage/emulated/0/test1.txt
ls -aRn > /storage/emulated/0/test2.txt
- you will find above txt files in the internal sdcard's root directory - please zip these files and post here as attachment
NOTE1: Rooted phone is not a MUST. If you have not rooted 5.1.1 firmware - just bypass "su" command and ignore "Permission denied" messages. In fact it will also do the work as it should.
NOTE2: Don't worry. Your /system partition will remain untouched by these actions. No private data will be read as all private contents are stored on /data

_alexndr said:
Not exactly
You need stock kernel but with sepolicy patched in ramdisk, according to @Chainfire's method.
I think I could help all G900W8's users
Rooting procedure (requires TWRP or CWM):
1. Download patched kernel and the latest SuperSU (2.52+):
>> KERNEL_G900W8VLU1COI4_Stock_patched.zip <<
>> SuperSU BETA by @Chainfire <<
2. Copy both zip files to phone or extSdCard
3. Go to TWRP / CWM and flash both files one by one. Order does not matter
4. Reboot the phone.
5. Enjoy your rooted 5.1.1 firmware
------------------------------------------------------
It is time to say that I also need your help as there is no 5.1.1 firmware for other S5's variants yet. I need updated SELinux contexts and and permissions/symlinks list from your 5.1.1 firmware. I require it to be well prepared with my custom firmware for G900F. I believe that Android 5.1.1 for G900F is just a matter of a few days.
Please do as follow while running G900W8VLU1COI4 firmware:
- Install Terminal Emulator from Play Store (https://play.google.com/store/apps/details?id=jackpal.androidterm)
- Type commands as follow:
Code:
[COLOR="Red"]su[/COLOR]
cd /system
ls -aRZ > /storage/emulated/0/test1.txt
ls -aRn > /storage/emulated/0/test2.txt
- you will find above txt files in the internal sdcard's root directory - please zip these files and post here as attachment
NOTE1: Rotted phone is not a MUST. If you have not rooted 5.1.1 firmware - just bypass "su" command and ignore "Permission denied" messages. In fact it will also do the work as it should.
NOTE2: Don't worry. Your /system partition will remain untouched by these actions. No private data will be read as all private contents are stored on /data
Click to expand...
Click to collapse
Do you Know how can i get spanish on this Vertion plz. ? @_alexndr

_alexndr said:
Not exactly
You need stock kernel but with sepolicy patched in ramdisk, according to @Chainfire's method.
I think I could help all G900W8's users
Rooting procedure (requires TWRP or CWM):
1. Download patched kernel and the latest SuperSU (2.52+):
>> KERNEL_G900W8VLU1COI4_Stock_patched.zip <<
>> SuperSU BETA by @Chainfire <<
2. Copy both zip files to phone or extSdCard
3. Go to TWRP / CWM and flash both files one by one. Order does not matter
4. Reboot the phone.
5. Enjoy your rooted 5.1.1 firmware
------------------------------------------------------
It is time to say that I also need your help as there is no 5.1.1 firmware for other S5's variants yet. I need updated SELinux contexts and and permissions list from your 5.1.1 firmware (in all Snapdragon S5 variants contexts/permissions are the same). I require it as I would like to be well prepared with my custom ROMs for G900F/FD. I believe that Android 5.1.1 for G900F/FD is just a matter of a few days...
Please do as follow while running G900W8VLU1COI4 firmware:
- Install Terminal Emulator from Play Store (https://play.google.com/store/apps/details?id=jackpal.androidterm)
- Type commands as follow:
Code:
[COLOR="Red"]su[/COLOR]
cd /system
ls -aRZ > /storage/emulated/0/test1.txt
ls -aRn > /storage/emulated/0/test2.txt
- you will find above txt files in the internal sdcard's root directory - please zip these files and post here as attachment
NOTE1: Rotted phone is not a MUST. If you have not rooted 5.1.1 firmware - just bypass "su" command and ignore "Permission denied" messages. In fact it will also do the work as it should.
NOTE2: Don't worry. Your /system partition will remain untouched by these actions. No private data will be read as all private contents are stored on /data
Click to expand...
Click to collapse
Hope this helps, thanks for your help.
Here you go!

Just confirmed the camera can shoot in RAW format

cant write to system

i have did adb remount and also mount -o rw,remount,rw /system on terminal in my phone....did mounted the system partion in twrp ( but it jus goes off again after i turn on my phone ) someone please help me

same here. anyone please help us

quiks11ver said:
i have did adb remount and also mount -o rw,remount,rw /system on terminal in my phone....did mounted the system partion in twrp ( but it jus goes off again after i turn on my phone ) someone please help me
Click to expand...
Click to collapse
delete unneeded system apps from /system/app/ then reboot and try again

simms22 said:
delete unneeded system apps from /system/app/ then reboot and try again
Click to expand...
Click to collapse
Hi when i try to delete, it shows a read only message, and i went root explorer to turn RW it automatically turn it off

quiks11ver said:
Hi when i try to delete, it shows a read only message, and i went root explorer to turn RW it automatically turn it off
Click to expand...
Click to collapse
ok, i understand whats happening now.. youre going to have to reroot. just boot into twrp and flash supersu 2.6x again.

simms22 said:
ok, i understand whats happening now.. youre going to have to reroot. just boot into twrp and flash supersu 2.6x again.
Click to expand...
Click to collapse
Hi, jus a simple question..will my phone be wiped?

quiks11ver said:
Hi, jus a simple question..will my phone be wiped?
Click to expand...
Click to collapse
if you just flash the latest SuperSU, then no. I flashed SuperSU 2.65 today, that works if you don't see a newer version.

simms22 said:
if you just flash the latest SuperSU, then no. I flashed SuperSU 2.65 today, that works if you don't see a newer version.
Click to expand...
Click to collapse
Ty simms22, i just realise my phone has no supersu, but quite odd, kernel auditor works haha...using elite kernel, i may flash later and try

okay, so i flashed the supersu 2.46 into my phone and it still doesnt show the supersu in apps drawer, but in setting/apps there is supersu and i still cannot manage to change write to system, in root explorer of es file manager after changing to RW, it automatic reset to Read only again

quiks11ver said:
okay, so i flashed the supersu 2.46 into my phone and it still doesnt show the supersu in apps drawer, but in setting/apps there is supersu and i still cannot manage to change write to system, in root explorer of es file manager after changing to RW, it automatic reset to Read only again
Click to expand...
Click to collapse
2.46 is very old now, you want 2.65 or above. google SuperSU 2.65, and you'll get it.

Okay bro, i already flash a supersu 2.66 but in my apps drawer i find no supersu apps and i still cant write to system

quiks11ver said:
Okay bro, i already flash a supersu 2.66 but in my apps drawer i find no supersu apps and i still cant write to system
Click to expand...
Click to collapse
wtf? lol! you can try to start over and reroot. thats what i would recommend, and its probably the right thing to do as well.

How to reroot? I oledi reflash but still cant

simms22, is it that i have a kernel or rom that resists me from writing to system, i can do it last time but i keep reflashing kernel making my system crash, then i restore from last backup afterward i cant write to system anymore

quiks11ver said:
simms22, is it that i have a kernel or rom that resists me from writing to system, i can do it last time but i keep reflashing kernel making my system crash, then i restore from last backup afterward i cant write to system anymore
Click to expand...
Click to collapse
what kernel are you trying? try elementalx.
---------- Post added at 01:40 AM ---------- Previous post was at 01:38 AM ----------
oh, BTW, reroot = flash factory image via fastboot, flash twrp via fastbpot as well. then flash SuperSU 2.65 and boot up.

i'm using elite kernel, what is factory image?? i'm kind of a newbie just unlocking and rooting watching youtube videos. please help me!!
where can i find factory image??

okay, i will try elementalX kernel, but 1 question...do i have to do anything before i flash another kernel? cause i used to flash many kernel after and after each1, then my phone keep restarting...so i restored the 1 i backed up

quiks11ver said:
okay, i will try elementalX kernel, but 1 question...do i have to do anything before i flash another kernel? cause i used to flash many kernel after and after each1, then my phone keep restarting...so i restored the 1 i backed up
Click to expand...
Click to collapse
factory images https://developers.google.com/android/nexus/images?csw=1#yakju
you have a nexus 6, so you need a factory image for shamu

hey i have an problem too everytime i try to push files in my system folder (like bootanimations) the es explorer sais i havent enough space every other explorer too, or when i try to change my density from 560 to 493 it sais the same, not enough space; i dont understand that... the phone is unlocked its rooted, i wiped everything a few times but nothing helps... :crying:

x-530 said:
hey i have an problem too everytime i try to push files in my system folder (like bootanimations) the es explorer sais i havent enough space every other explorer too, or when i try to change my density from 560 to 493 it sais the same, not enough space; i dont understand that... the phone is unlocked its rooted, i wiped everything a few times but nothing helps... :crying:
Click to expand...
Click to collapse
delete whatever system apps you don't need from /system/app/ then reboot. it will clear up enough space. google did that on purpose, made it read that its full, this will clear up the space.