Database Users

The Unofficial Thread of Official OTA Updates

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Since we got update threads scattered everywhere, I figured I'd organized things into one thread, as well as give away some new updates.
Retail EU:
81.5.31006-81.5.40002.Retail.en.EU 4.0.4-4.0.4
81.5.32002-81.5.40002.Retail.en.EU 4.0.4-4.0.4
81.5.4002-91.2.26001.Retail.en.EU 4.0.4-4.1.2
Retail GB:
81.5.31002-81.5.39001.Retail.en.GB 4.0.4-4.0.4
81.5.39001-91.2.29001.Retail.en.GB 4.0.4-4.1.2
Orange GB:
81.5.31002-91.2.26001.Orange.en.GB 4.0.4-4.1.2
O2 DE:
81.5.32002-81.5.39002.O2.en.DE 4.0.4-4.0.4
81.5.39002-91.2.26001.O2.en.DE 4.0.4-4.1.2
Vodafone FR:
81.5.31002-81.5.39001.Vodafone.en.FR 4.0.4-4.0.4
81.5.39001-91.2.26001.Vodafone.en.FR 4.0.4-4.1.2
Brasil BR:
871.110.12008-871.110.12012.Brasil.en.BR 4.0.4-4.0.4
871.110.12012-871.111.20003.Brasil.en.BR 4.0.4-4.0.4
871.111.20003-982.50.20.Brasil.en.BR 4.0.4-4.1.2
AmericaMovil MX:
871.110.13009-982.50.25004.AmericaMovil.en.MX 4.0.4-4.1.2
If you have an OTA update.zip please PM it to me or contact me on google talk ([email protected]) and I will quick add it to this thread, with safe hosting, credits to The Firmware Team's Pzyduck for providing safe-haven for these types of files.
Instructions for pulling an OTA update.zip:
Do NOT install the update! Do these first!
Be rooted. We got plenty of methods. Motofail2go for ICS, and my RAZRiRoot.zip for turl1's Clockworkmod.
Download the Root Explorer app, or the ES File Manager app. (Instructions are for Root Explorer.)
Open Root Explorer and go to the ~/cache/ directory, which resides on the root directory of the phone '~/'
Hit the 'Mount R/W' in the corner, if successful will then say 'Mount R/O'
Copy the update file .zip from the ~/cache/ to your sdcard, external to be safe. External is in ~/mnt/external1/ and Internal is ~/sdcard/.
Copy over the update file .zip from the sdcard(s) you chose to your computer and upload it.
You will want to use Voodoo's OTA Rootkeeper before updating if you have a locked bootloader, you can find my thread on a RAZR i compatible version here.
Send me or post a link here to the update and exactly what System Version you were on, and where the update takes you to.
The community will thank you for your help!
Enjoy. Remember to do your part to the community and contribute all updates!

Hmm, but I can't put the EU update.zip on it when I'm on GB without losing data, right?

Vistaus said:
Hmm, but I can't put the EU update.zip on it when I'm on GB without losing data, right?
Click to expand...
Click to collapse
You cannot install any of these on different carriers without use of fastboots and unlocked bootloader.
These updates will ONLY work from PointA-PointB.

Here's another Update Zip for 40002EU. For this one you have to come from 32002 EU. The one in the OP is from 31006.
http://forum.xda-developers.com/showthread.php?p=34886686
Sent from my XT890

HSD-Pilot said:
Here's another Update Zip for 40002EU. For this one you have to come from 32002 EU. The one in the OP is from 31006.
http://forum.xda-developers.com/showthread.php?p=34886686
Sent from my XT890
Click to expand...
Click to collapse
Thanks! Uploaded to server, renamed, and added to the OP.

mattlgroff said:
You cannot install any of these on different carriers without use of fastboots and unlocked bootloader.
These updates will ONLY work from PointA-PointB.
Click to expand...
Click to collapse
mattlgroff, im in 81.5.31006.Retail.en.EU - 4.0.4. and in software update i get notification of an ota. i down loaded that file when ask if i want to install it i select yes. but when in recovery it always fails. why, isnt that the official? because after that i tried flashing it in recovery but it fails too.
before alll this i was already on 81.5.40002.Retail.en.EU - 4.0.4. coming from 81.5.31006.Retail.en.EU. but i wanted to downgrade back to 81.5.31006.Retail.en.EU. and my phone died. thanks to hsd pilot my phone came back to life he sended me a file http://forum.xda-developers.com/attachment.php?attachmentid=1528201&d=1354399653. but now im stuck in what i told you at the begining. why?? what can i do to go back to 81.5.40002.Retail.en.EU. i know this is not the thread sorry but i was watching your new otas. and i cant install the one for my version.

Are you rooted? If yes and you used the Root with insecured Kernel, then you probably have the wrong Boot.img on your Phone. Grap the Boot_signed out of the 31006 Fastboot File and flash it through fastboot
fastboot flash boot boot_signed
Sent from my XT890

HSD-Pilot said:
Are you rooted? If yes and you used the Root with insecured Kernel, then you probably have the wrong Boot.img on your Phone. Grap the Boot_signed out of the 31006 Fastboot File and flash it through fastboot
fastboot flash boot boot_signed
Sent from my XT890
Click to expand...
Click to collapse
As HDS-Pilot says.
The error message from side-loading will tell us exactly the problem.

mattlgroff said:
As HDS-Pilot says.
The error message from side-loading will tell us exactly the problem.[/QUOTE
thank you guys!!! that was the problem and another one was that i erase alot of apk.s that i dont use so at time of flashing i saw it said something about an apk. missing so i fastbooted again and flash boot.img and here i am with the 40002.rt.eu. and now waiting for jellybean
Click to expand...
Click to collapse

If I want to update, it can be done on a homemade fastboot or I need to use a stock firmware, my bootloader is unlocked, can I flash a totally stock firmware without problem and then use the OTA update? Thanks.

joel_sinbad said:
If I want to update, it can be done on a homemade fastboot or I need to use a stock firmware, my bootloader is unlocked, can I flash a totally stock firmware without problem and then use the OTA update? Thanks.
Click to expand...
Click to collapse
Yes you can.

I have version 871.110.12008.XT890.Brasil.en.BR installed from sbf.droid-developers
My Razr i bootloader is unlooked and rooted. When i try to install the update with the android button (in about system) i recive error message after reboot. How can i install this update manually with fastboot console?
Thanks!

First, use an Root Explorer and copy your downloaded Update Zip out of the Cache Folder and leak it
Edit : Ok, it's in the OP already. Sorry, it's 1am in Germany :sly:
Your RazR i is rooted, how did you root it? If you used the Unlocked Root (insecure Kernel), than grap the boot signed out of the sbf you flashed and use fastboot to install it
fastboot flash boot boot_signed.
After that it should work. If not, you maybe deleted some System Apps. If that's the case, flash the system_signed.
Sent from my XT890

Hi all, if I have link2sd linked applications. if I do what he says here respectively, applications may be lost or will stay intact?
I have this doubt, I would not lose my apps linked by link2sd when updating

josmel91 said:
Hi all, if I have link2sd linked applications. if I do what he says here respectively, applications may be lost or will stay intact?
I have this doubt, I would not lose my apps linked by link2sd when updating
Click to expand...
Click to collapse
I have no clue. I'd ask in the Q&A section if you want an answer quickly

Hello matt,
Could you pull the latest homescreen & circle widget combo from the latest ota of XT890. I noticed that the occasional lag on on the launcher has been fixed with new version. I want to install it on my droid razr to get a fresh taste.

Semseddin said:
Hello matt,
Could you pull the latest homescreen & circle widget combo from the latest ota of XT890. I noticed that the occasional lag on on the launcher has been fixed with new version. I want to install it on my droid razr to get a fresh taste.
Click to expand...
Click to collapse
After getting a DMCA Takedown Request from posting those before from the MB886 I'm afraid I can't help you there.

The 81.5.31002-81.5.39001.Retail.en.GB OTA update did something to my RAZR i's GSM radio, and now it can't recognize any SIM that I put in it ('No service'). :\ It used to work perfectly on 81.5.31002 prior to the update. Can anyone help me out?
I have tried reflashing the original 81.5.31002 stock firmware, the 81.5.39001 firmware as well as the latest EU firmwares using RSD Lite, didn't help at all. The GSM radio still seems to be out. I have also tried setting the network type to GSM in the *#*#4636#*#*-triggered menu and rebooting the phone, but even that doesn't help.

jenova941 said:
The 81.5.31002-81.5.39001.Retail.en.GB OTA update did something to my RAZR i's GSM radio, and now it can't recognize any SIM that I put in it ('No service'). :\ It used to work perfectly on 81.5.31002 prior to the update. Can anyone help me out?
I have tried reflashing the original 81.5.31002 stock firmware, the 81.5.39001 firmware as well as the latest EU firmwares using RSD Lite, didn't help at all. The GSM radio still seems to be out. I have also tried setting the network type to GSM in the *#*#4636#*#*-triggered menu and rebooting the phone, but even that doesn't help.
Click to expand...
Click to collapse
Use my home-made fastboot to go back to 81.5.31002.
Install the OTA again up to 81.5.39001.
See if that works

mattlgroff said:
Use my home-made fastboot to go back to 81.5.31002.
Install the OTA again up to 81.5.39001.
See if that works
Click to expand...
Click to collapse
Thanks, downloading. Do I just flash it using CWM, RSD Lite or something else?

[Guide] How to use Flashtool

Hi everybody welcome to my tutorial about Flashing with Flashtool. This thread is for those who want to reflash their device back to Sony Stock. See below for last details about this thread and the last build by Sony.
Note: I DO NOT OWN THIS DEVICE ANYMORE. PICTURES ARE REMOVED FROM MY DROPBOX AND THUS NOT VISEBLE. FOR NOW JUST RELY ON THE EXPLANATION PLEASE. ANY QUESTION CAN BE ASKED HERE. I DO NOT RESPOND TO TECHMAIL!
Created: 23-02-2014
Updated: 05-07-2014
Latest Android build released by Sony: 12.1.A.1.205
Let's begin shall we.. We shall!
First you need to download the correct ftf file for your device/operator or needs. This can be done here: http://forum.xda-developers.com/showthread.php?t=2311964 In there you can share and download firmware files in .ftf format..
You alsol need a program called Flashtool. You can download this here: http://forum.xda-developers.com/showthread.php?t=920746
For Windows 8 and 8.1 users I also recommend you to read this thread: http://forum.xda-developers.com/showthread.php?t=2095087 Microsoft has enhanced the security in Windows 8/8.1 and Windows won't install proper signed drivers.
When you are done with that you need to move your downloaded firmware file to the proper location for flashtool to be found:
C:\Flashtool\Firmwares
After that you are good to go, just remember the following:
Bootloader locked? If not you wont have BE2/OTA/PCC etc (for unlocking and relocking: http://forum.xda-developers.com/showthread.php?t=2354721 )
I've made backups of my important files that are stored on my phone?
Battery at atleast 50%?
I have patience?
I got something to do meanwhile?
The last two things are very important
Let's get started:
1: Open Flashtool:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Flashtool(.exe) for 32Bits systems and Flashtool64(.exe) for 64Bits systems
2: Press the Lightningbolt picture and select Flashmode
This will give another screen.
3: Select the downloaded ftf. (In this case 2.254)
Make sure that all the wipes are checked and the others are unchecked. This is to prevent any bootloops or other problems after downgrading.
4: Press Flash and the next two lines will be added to the flashtool log
The files are being prepared and checked. Have a bit of patience please.
5: Turn off your phone and turn it back on into Flashmode
After this the process will start.
After flashing you can disconnect your phone and boot it up.
Via Flashtool you can also reset your system after. For example:
You are running the latest ExistenZe ROM from our beloved Niaboc79 and you want to go back to stock for a reason WITHOUT losing data! Just flash the last Stock ROM and untick the following boxes:
Untick DATA and APPSLOG!! But keep CACHE to wipe the /cache (is the same as a wipe cache via CWM).
FAQ​
- My Phone wont stay into flashmode
> Turn it off, wait a few minutes and turn it back into flashmode
- Flashtool wont recognise my phone
> Make sure you have the proper drivers installed. See C://Flashtool/Drivers
- Flashing failed
> Problem depends on the error code given by Flashtool. Post the problem here and perhaps we can help
- Got a bootloop
> Reflash again
- Even after reflash I got into a bootloop
> Turn off your phone via the small button behind the batterycover and wait a few minutes. Then try again. If that doesnt work you need to flash again.
- Booting takes ages
> This is normal. The entire cache needs to be rebuild. Patience my dear..
- After flashing and booting my phone is laggy.
> Reboot device and wait a bit. The phone needs to fully reset and boot itself. Have some patience dear.
- Do I need to unlock my bootloader to use flashtool
> NO!
- Can I unlock my bootloader with flashtool?
> NO!
- Can I relock my bootloader with flashtool?
> Yes

> Reserved by me

downgrade to root?
first, thanks! Very nice guide. I'm new to the experia world, my previous phone was a Desire S.
I have a question:
I have a problem with all stock roms with the mediaserver process. It is always running while I listen to music (which is a lot of time) and drains a lot of battery (up to 65%). Though I use poweramp player which is totally independent of the process (own library and decoder). On my Desire S on CM11 I don't have the issue this is why I want to move to a custom rom. I'm on 4.3 now (was hoping this would fix the issue) and want to root and full backup with keys for warranty purposes and then move to a custom rom.
Is it right that I have to downgrade first, since there is no root for 4.3 yet? If yes, what ROM? I have a C5303 and don't know what version I had previously. I bought it in Switzerland without SIMlock or any branding. Is there a way I can find out what my previous version was or can I basically just use any generic C5303 version?
Would you recommend 12.0.A.1.284 in order to be able to use DoomLords rootkit: http://forum.xda-developers.com/showthread.php?p=42701183#post42701183 ?
It's just that I don't know if I ever was on this version, also regarding warranty...
I know, many questions, but I just reached a point where I don't seem to get further without asking. Hope someone can clarify some of them.
Thanks in advance!
EDIT: And also I was wondering: In the picture says flashmode is reached by pressing the back button while connection, but there are softkeys. Is it not done with volume down?

mrjraider said:
Small changes.. @ moderators Is it possible this can become a sticky?
Click to expand...
Click to collapse
+1 for a sticky!
Nice done!

TheMorpheus said:
+1 for a sticky!
Nice done!
Click to expand...
Click to collapse
after flashing done
i have to turn on phone & make usb debugging & unknown source option check
but whenever i am going to boot it again reboot after colour bootscreen
i had tried number of times flashing again & again
i am attaching my flashtool log file also
Azhar

According to the log you attached everything went fine. So I dont understand the problem.
Perhaps an idea to redownload it? Sometimes it wont work properly because the ftf file is somewhat damaged..

I have to relock the bootloader before restore?
Edit
No, it's not needed!

reflashig stock rom
Thanks for this nice guide. Im having a lot of issues with the 4.3 rom.
I flashed via SUS, editing build.prop to let the phone detect the new version, because my phone is carrier locked, and they didnt released the update yet.
I have a lot of lag, and I must force reset lots of times, so I want to make a clean install, because last time I only updated.
So my question is, if I do a factory reset, my build.prop is going to change to the original file (Orange's rom) or ill keep with my modified file? (Stock center Europe)
What do you recommend to me? If I reflash a stock European ftf via flashtool, I'll have the stock's build.prop, and I'll receive those Ota updates without problem?
Thanks for your work!

No if you have a TA backup you need to reflash your ROM and Restore TA partition

mrjraider said:
No if you have a TA backup you need to reflash your ROM and Restore TA partition
Click to expand...
Click to collapse
I don't have the backup, because my phone has the bootloader locked, and the only thing I have done is root and editing build.prop to be able to upgrade to European 4.3. Everything is working for me, track id and BE. (btw I have a backup of my build.prop in the computer)
I only want to do a fresh install of 4.3, not my carriers rom, because is on 4.1.2
So can I reflash any Stock 4.3 rom? The rom has it's own build.prop?
Thanks for your help Mrjraider

diolo said:
I don't have the backup, because my phone has the bootloader locked, and the only thing I have done is root and editing build.prop to be able to upgrade to European 4.3. Everything is working for me, track id and BE. (btw I have a backup of my build.prop in the computer)
I only want to do a fresh install of 4.3, not my carriers rom, because is on 4.1.2
So can I reflash any Stock 4.3 rom? The rom has it's own build.prop?
Thanks for your help Mrjraider
Click to expand...
Click to collapse
Yes you can. Simply download the ftf file and follow the steps in the OP

Hi mrjraider,
Many thanks for the guide!
A quick question. I am now in 4.3, bootloader locked. If I downgrade to 4.1.2 (.254 for example) my bootloader is still locked, correct?
Thanks!

Yes

I want to go back to stock from AOSP ROM and I don't know what's the right .ftf file for 12.1.A.0.266 but I think I know the right file for 12.0.A.2.254 (German branded C5303) (I'm from Germany ). If I would flash the 12.0.A.2.254 .ftf file would the Update Center show me the 4.3 OTA update and everything would work like on stock before? And would I lose root even with Voodoo OTA RootKeeper and the option enabled to try keeping Superuser access in SuperSU?

You need to look in the thread I linked to. There you can find many FTF files.

mrjraider said:
You need to look in the thread I linked to. There you can find many FTF files.
Click to expand...
Click to collapse
I know I already looked there but I'm not sure which one is right, because I didn't see a generic one for all C5303 and I don't want do have a foreign branding
Edit: found it, sorry
Gesendet von meinem Sony Xperia SP C5303

hey bro, am looking for Sony C5303_12.0.A.2​.254 tft generic global or CE version also UK version ,am unable to find them . I have being searching xda and a found a link that is broken,so please if any one can help.Thanks in advance.:fingers-crossed:

desmond462 said:
hey bro, am looking for Sony C5303_12.0.A.2​.254 tft generic global or CE version also UK version ,am unable to find them . I have being searching xda and a found a link that is broken,so please if any one can help.Thanks in advance.:fingers-crossed:
Click to expand...
Click to collapse
Do not ask for ftf files in here. There is a proper thread for this
Normaly I would help but the chances of getting an older update is decreasing every day since the update of Sony has rolled out a few weeks ago

Well done ! Rollback firmware 4.3 to 4.1
Hi guys ! thanks for guide. I got successfull revert my phone from update 266 to 254.

hi sir, i'm on .254 rooted and just want to go back to stock because i want to update it to 4.3, is it the safest way? if so, what will happen to my apps like greenify, Titanium backup, and those apps that was already transferred to sd card? should i have to uninstall these aps? does it have remaining unwiped data to be cleaned if flashing the stock rom?
thank you..

[Galaxy K Zoom] [Root] [Kernel] Stock kernel with permanent autoroot

KatAutoRoot
This method uses a modified stock boot.img for the Galaxy K Zoom C115
that will root automatically the current /system in place without flashing a new system image.​
Download: http://downloads.timduru.org/android/kzoom/root/Tim_KZoom_KatAutoRootV3.zip
What you get:
- Stock kernel 3.4.39-1837070
- Root + SuperSu apk
- sysrw/sysro
- addblocker (/etc/hosts)
- init.d support
- microSD card write fix for non system applications (modified platform.xml)
The good thing with this new method is that it will also auto-reroot the system if su disappears.
So for example you can flash a new official stock system.img and then on the 1st boot it will root it again automatically, no need to do anything else.
(as long as you don't flash another boot.img of course)
What you need:
- Computer with Odin working (Tested with V3.09)*
- File from above.
How to root:
- Unzip the file on the computer with odin ( you get a .tar.md5 file)
- Shutdown mobile
- Start mobile in odin mode*
(push *together: volume down + home + power, * when confirmation screen appears, push *vol up to confirm)
- Launch Odin
- Connect phone by USB *(Odin will display *"Added", if it works and com port should be listed)
- In Odin options you only need Autoreboot checked
- Click on AP choose the *.tar.md5 unzipped previously
- Wait that odin checks the file (can take a few seconds and odin can freeze during that time, just wait)
- Click on Start
Odin will flash the image and reboot
If you are having wifi password issues, to make sure it works let it boot fully once after flashing, then reboot
(you might have to reenter your wifi password the 1st time you flash)
Happy rooting !
As usual, use at your own risk
Credits:
- Dan Pollock for the original ad-blocker file http://someonewhocares.org/hosts/
- ChainFire for SuperSU

timduru said:
Download: http://downloads.timduru.org/android/kzoom/root/Tim_KZoom_PermaRootV2.zip
It contains a modified stock boot.img for the Galaxy K Zoom
that will root automatically the current /system in place without flashing a new system image.
Happy rooting !
As usual, use at your own risk
Click to expand...
Click to collapse
Fantastic! Thanks for this, much appreciated

Hi Timduru!
What are the advantages of this method compared to the first one? I rooted with the first method and all is working very good but i'd like to know the differencies!
Sent from my rooted, deodexed, zipaligned, busyboxed, Knox free Galaxy S5 Zoom with stock kernel and Xposed-modded stock ROM.

livio80 said:
Hi Timduru!
What are the advantages of this method compared to the first one? I rooted with the first method and all is working very good but i'd like to know the differencies!
Click to expand...
Click to collapse
This one will not flash a system.img , but root your current /system in place.
it will also auto-reroot if you update the system and lose su
That also makes it a smaller download, only a few MBs compared to almost a GB before
If you already used the 1st method you don't need to flash this one.
But will be easier to use this one after the next update in that case.

timduru said:
This one will not flash a system.img , but root your current /system in place.
it will also auto-reroot if you update the system and lose su
That also makes it a smaller download, only a few MBs compared to almost a GB before
If you already used the 1st method you don't need to flash this one.
But will be easier to use this one after the next update in that case.
Click to expand...
Click to collapse
I tried the original method of rooting and it worked without any noticeable issue. Then I read your post about possible kernel conflicts, so I re-rooted with your latest method (didn't want to try the French version in case of potential problems in the future) However, after this re-rooting, I could not update the SU binaries using the normal method, after each attempt it disabled my SIM card which was a worry, but after 2-3 attempts I tried the CWM/TWRP method to update the binaries and that worked oddly enough. Since then everything appears to be working 100% OK.
The main thing is I have my ad blocking, Titanium Backup and most importantly SD card access for my apps!
Thanks again

apprentice said:
However, after this re-rooting, I could not update the SU binaries using the normal method, after each attempt it disabled my SIM card which was a worry, but after 2-3 attempts I tried the CWM/TWRP method to update the binaries and that worked oddly enough. Since then everything appears to be working 100% OK.
The main thing is I have my ad blocking, Titanium Backup and most importantly SD card access for my apps!
Thanks again
Click to expand...
Click to collapse
Yeah, if you had an already rooted system by a different method before,
the thing to do before flashing this one is to cleanup the previous /system/xbin/su or reflash a stock system.img
otherwise it will not reinstall.
Updating through recovery like you did is fine too.

New version V3
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download: http://downloads.timduru.org/android/kzoom/root/Tim_KZoom_KatAutoRootV3.zip
ChangeLog:
- Add busybox to /sbin/
- Fix SecureStorage errors (wifi passwords might not get stored properly)
To make sure it works, after flashing let it boot fully once, then reboot (you might have to reenter your wifi password the 1st time you flash)

Thanks a LOT!
That was what I am waiting for so long since I selled my rooted S4 Zoom to get the K Zoom!
:laugh::good:

Thank you for this, had my Zoom for a few days and was frustrated not to be able to restore some backed up apps
Just a question, since the device now shows status as "custom", how would you go about un-rooting so you can restore using Samsung Kies if needed?

LususNaturae said:
Thank you for this, had my Zoom for a few days and was frustrated not to be able to restore some backed up apps
Just a question, since the device now shows status as "custom", how would you go about un-rooting so you can restore using Samsung Kies if needed?
Click to expand...
Click to collapse
Same as above but you'd use the official firmware zip,
open the file and just leave the boot.img and system.img
and flash that.

Sooooo glad to hear this. thx man.
the problem is there're various versions of k zoom.
currently 2 model in china. c1116 for china unicom wcdma only. c1158 for china mobile td-scdma. not to mention c115 for many other markets.
is this method suit for all model, or some of them. if so, which model you guys successfully tested?
will test on my c1116 next week. but if anyone can provide their details, will be a great help.
again, great work, it's been a life saver since my ****ty carrier simply deleted any google service and had to stick to whatever bone he throws.

Still WiFi issues...
timduru said:
Download: http://downloads.timduru.org/android/kzoom/root/Tim_KZoom_KatAutoRootV3.zip
ChangeLog:
- Add busybox to /sbin/
- Fix SecureStorage errors (wifi passwords might not get stored properly)
To make sure it works, after flashing let it boot fully once, then reboot (you might have to reenter your wifi password the 1st time you flash)
Click to expand...
Click to collapse
I tried it the first time with the autorootV3, not any older versions before, but it forgets all WiFi passwords...
it says "authetification error" -> I type it in again -> Wifi off and later on = still the same error...
Should I flash your Kernel for the K Zoom to fix this or is there an other way to fix it?
Thanks in advance!:good:
Gerome

btecsm said:
I tried it the first time with the autorootV3, not any older versions before, but it forgets all WiFi passwords...
it says "authetification error" -> I type it in again -> Wifi off and later on = still the same error...
Should I flash your Kernel for the K Zoom to fix this or is there an other way to fix it?
Thanks in advance!:good:
Gerome
Click to expand...
Click to collapse
did you reboot once ?
anarchycn said:
Sooooo glad to hear this. thx man.
the problem is there're various versions of k zoom.
currently 2 model in china. c1116 for china unicom wcdma only. c1158 for china mobile td-scdma. not to mention c115 for many other markets.
is this method suit for all model, or some of them. if so, which model you guys successfully tested?
will test on my c1116 next week. but if anyone can provide their details, will be a great help.
again, great work, it's been a life saver since my ****ty carrier simply deleted any google service and had to stick to whatever bone he throws.
Click to expand...
Click to collapse
it's based on C115 kernel, so yeah better not flash on another model I'd say.

Reboot does not help...
timduru said:
did you reboot once ?
I had rebootet serveral times now, but the problem resists...
(sorry for my bad english, I am german...)
Click to expand...
Click to collapse

btecsm said:
I had rebootet serveral times now, but the problem resists...
(sorry for my bad english, I am german...)
Click to expand...
Click to collapse
Try to long push on the network and click on forget.
reboot
then try again.
Try also to go to applications => ALL => Security Storage
click on force stop + clear data

Clear data?
Sent from my SM-N9005 using XDA Premium 4 mobile app

btecsm said:
Clear data?
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
yeah , but looks like it it's greyed in your capture, so it doesn't have data.

ChangeLog:
- Add busybox to /sbin/
- Fix SecureStorage errors (wifi passwords might not get stored properly)
To make sure it works, after flashing let it boot fully once, then reboot (you might have to re-enter your WiFi password the 1st time you flash)
Click to expand...
Click to collapse
Thank god, I was getting very stressed that my WiFi was not auto connecting and I tried various things to correct it. Came here to find a solution and voilà! Now all working on re-booting. Thanks for the update!!

I tried everything as described, refreshed the whole stock rom and flashed your kernel...
This doesn't helped...
Nothing more to loose, before I make an full wipe, I decided to freeze and than deinstalled the Security store.
Immediately after that, I turn Wifi off and later on...
Wifi works like a charm now!
Do I have to reinstall the secure store?
For what is it, when it stores my passwords for my Wifi connections?!?
Confused ?
Sent from my SM-N9005 using XDA Premium 4 mobile app

Somehow the problem resists for other networks...
To my 2nd home network it connects as usual and for my other network it does not reconnect...
It seems like it doesn't save any new passwords...
But for one it Works?
Can someone please tell me what to do?
Sent from my SM-N9005 using XDA Premium 4 mobile app
---------- Post added at 06:02 PM ---------- Previous post was at 05:44 PM ----------
Sorry for the much posts here...
But now I have an new solution :
I now have frozen wssyncmlnps and it stores new Networks with passwords!
I also deinstalled DS Battery Saver 3.0
Hope that this useful program is not responsible for my problems...
Sent from my SM-N9005 using XDA Premium 4 mobile app

[Discussion] Dumb attempt to upgrade to Marshmallow with TWRM in osprey

Hi everyone, posting this as a information about something you should NOT try: upgrade your OTA rom with custom recovery installed, in my case TWRP.
I did this with ignorance of not think that (or search about) the custom rom could interfere at the normal process of OTA upgrade from Lollipop to MarshMallow. Actually I remembered that I was unlocked and rooted the phone but I did not remember I was using custom recovery. AFAIK at this device is impossible to root without unlocking and custom recovery.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you are on TWRP don't do this!
For those don't know about TWRP and OTA updates, read this:
https://twrp.me/faq/officialota.html
In short terms: don't try OTA updates (official updates) if you installed custom rom such as TWRP. "Installing official updates from your manufacturer or carrier is not supported by TWRP." "[This] may result in unexpected behavior" "Most of the time the best way to get a new update onto your device is to simply wait a couple of days for ROM makers for your device to come up with ROMs that are based on the new update that you can safely and easily install."
But I did it. And now I'm reporting it for those who are curious. So, what's happened?
Fortunately the device is not bricked as I thought when it reboot to TWRP for flashing the OTA update instead of the stock recovery process! I thought that I messed everything when I see the frozen TWRP for something about 10 minutes or less. After the long 10 minutes of frozen TWRP image I got the recovery working and checked the log:
Of course, errors on the log.
Rebooted and got a frozen background image, after a while a permanent black. When the screen turn off the notification system shows the battery as dead (and it as not). But I could turn it off and gain access to the recovery holding power and volume down buttons.
After two failed reboots to the system with the same result I tried to make a screenshot using the hard buttons and it works (screenshoted the black screen) and suddenly the lock screen shows up. I got into, everything working slow meaning that there was a lot things working in the background. Got some error messages from google service and MMS/SMS communication and minutes later it automatically reboots and booted the TWRP again.
This turned to a loop. I stopped this by going to the system setup - about the device - check for updates. And got a message "the update has failed". Good. After a while the message offering the update shows again... No, thanks...
I rebooted to TWRP and fixed the permissions, maybe this solve some problems.
Right now the phone is working but the rebooting process has unexpected behaviors, some tries result in a normal fast process and other tries result in a long black image and the system/launcher just don't arm up for some minutes, but after a while it works. I'm not confident. Already backed up apps with Titanium backup.
I'm planning to restore everything from the stock using this guide:
http://forum.xda-developers.com/mot...e-restore-moto-e-2015-stock-firmware-t3054303
And them, maybe, update the OTA to marshmallow. Before doing that, I will search and get to know if it is possible to re-root the phone with marshmallow in osprey (that means re-unlock and install TWRP again). Rooted device it's a need for me.
This is what happened to my device when tried to OTA update with TWRP. I had luck not bricking this.

+1 on the dumb attempt. Early morning, excited for the release, upgrade please! Yeah, no good. Is restoring our only option? Seems the upgrade has not even started so what about deleting the downloaded image file or trying to kill the process attempt?

did you really had to make a new thread with that huge wall of text? haha come on man, common knowledge that to take the OTA you need stock recovery ?
Sent from my Nexus 6 using Tapatalk

Seems the upgrade has not even started so what about deleting the downloaded image file or trying to kill the process attempt?
Click to expand...
Click to collapse
Yeah, DON'T proceed with the update! Deleting the downloaded files just break the process... My advise is to make a backup before deleting this.

sgloki77 said:
did you really had to make a new thread with that huge wall of text? haha come on man, common knowledge that to take the OTA you need stock recovery
Click to expand...
Click to collapse
Ok, sorry about the huge wall of text.

No need to adb stock image. A simple factory reset worked for me. Next time will have more caffiene before attempting anything major with my phone.

golgiapp said:
No need to adb stock image. A simple factory reset worked for me. Next time will have more caffiene before attempting anything major with my phone.
Click to expand...
Click to collapse
:good:
Good to know that a factory reset could fix the problems caused by the OTA update with TWRP. But after this it should remain with custom recovery and not possible to OTA update. for stock MM

i downloaded the 24.11.25.en.US ota update not installed yet becuase i want to find it first and save it on my pc.
any idea what folder is saved ??

gonzodesigns said:
i downloaded the 24.11.25.en.US ota update not installed yet becuase i want to find it first and save it on my pc.
any idea what folder is saved ??
Click to expand...
Click to collapse
Not sure, but take a look at /cache

gonzodesigns said:
i downloaded the 24.11.25.en.US ota update not installed yet becuase i want to find it first and save it on my pc.
any idea what folder is saved ??
Click to expand...
Click to collapse
/data/data/com.motorola.ccc.ota/app_download

hp420 said:
/data/data/com.motorola.ccc.ota/app_download
Click to expand...
Click to collapse
found it!!
thanks extracted ok !!
its a zip flashable,can it be converted to install like the oem recovery images using the adb method?

gonzodesigns said:
i downloaded the 24.11.25.en.US ota update not installed yet becuase i want to find it first and save it on my pc.
any idea what folder is saved ??
Click to expand...
Click to collapse
Thank you for the warning
---------- Post added at 12:58 AM ---------- Previous post was at 12:54 AM ----------
Thank you for the warning

I experience this today, I flashed a stock rom again so I can have the OTA update, but what I can't do is root my device, I flash the custom recovery and then I flash the beta version of SuperSU, and when I reboot my device it bricks in the Motorola Logo, anybody knows how to fix this, or should I wait a little bit longer to root my phone? as the OP I need root too

Use the latest 2.62 superSU zip. And never root with the TWRP option before reboot.
Sent from my MotoG3 using Tapatalk

nelsonw said:
Use the latest 2.62 superSU zip. And never root with the TWRP option before reboot.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Never done that, I tried flashing the superSU 2.52 from a bunch of tutorials I found on Google, but all it does is bricking my phone on the Motorola Logo, then I have to do all the downgrade and update process again

VicSanRED said:
Never done that, I tried flashing the superSU 2.52 from a bunch of tutorials I found on Google, but all it does is bricking my phone on the Motorola Logo, then I have to do all the downgrade and update process again
Click to expand...
Click to collapse
this is a known issue with the mm update. Use 2.61 or newer, only. These are the new systemless root zips.

hp420 said:
this is a known issue with the mm update. Use 2.61 or newer, only. These are the new systemless root zips.
Click to expand...
Click to collapse
I tried with the latest version 2.66 and still the same issue. Don't know what to do now.

So its posible to root MM ?? Safe ,stable?
Supersu v 2.62??

Yeah, 2.62 is the only one working. This worked for me BETA-SuperSU-v2.62-20151210170034
Sent from my MotoG3 using Tapatalk

nelsonw said:
Yeah, 2.62 is the only one working. This worked for me BETA-SuperSU-v2.62-20151210170034
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Can you post a little tutorial?, I wanna be sure I'm doing everything OK.

[Tutorial] [One click ROOT] Honor 6 Android 5.1/6.0

Easy way to root HH6​No Computer needed, just one simple apk and about 10 minutes of your precious Time
1st step: Own Huawei Honor 6
2nd step: Download and install This app
(Remember to allow unknown sources in settings)
3rd step: Launch it, it will say "not supported" but gives you a chanse to give it a go anyway. So do that. It will start rooting. App may close several times but it will not crash. Just open it again from " recent apps" and it will roll again.
Wait for 100% and rooting is done.
Posting pics soon.
You are welcome

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I don't need to unlock the bootloader first?
Can the rooting be reversed? Is this safe?

Lotroni said:
I don't need to unlock the bootloader first?
Can the rooting be reversed? Is this safe?
Click to expand...
Click to collapse
No unlocking needed, perfectly safe and unroot can be done with same app. (Screenshot of that included in this post)
Spoiler
Sent from my H60-L04 using XDA-Developers mobile app

So I wanted to root my Honor 6, mainly because for Adaway.
This one click root actually worked for rooting(first time got hung up maybe because I lost wifi connection for a while?) but worked when I run it again. The uninstalling got hung up too but it worked after second try I think.
This root wasn't enough for adaway for S-On and S-OFF I think, so I had the bootloader unlocked, got clockwork recovery and tried to root with HONOR Multitool. With multitool rooting with SuperSU it says I need to update SU binary, and I couldn't figure out how to do that. Then I tried rooting again with this one click and it now the Adaway works too so yay and thanks.

Lotroni said:
So I wanted to root my Honor 6, mainly because for Adaway.
This one click root actually worked for rooting(first time got hung up maybe because I lost wifi connection for a while?) but worked when I run it again. The uninstalling got hung up too but it worked after second try I think.
This root wasn't enough for adaway for S-On and S-OFF I think, so I had the bootloader unlocked, got clockwork recovery and tried to root with HONOR Multitool. With multitool rooting with SuperSU it says I need to update SU binary, and I couldn't figure out how to do that. Then I tried rooting again with this one click and it now the Adaway works too so yay and thanks.
Click to expand...
Click to collapse
Thanks for feedback and and good to hear it worked [emoji4]
Sent from my H60-L04 using XDA-Developers mobile app

IMO kingroot is terrible.
a lot of adds and pop up, and it's so unclean.
I've tried to remove it, can't.
I've tried to replace it with SuperSU, can't.
I ended up flashing a new rom to get rid of this.

SM26 said:
IMO kingroot is terrible.
a lot of adds and pop up, and it's so unclean.
I've tried to remove it, can't.
I've tried to replace it with SuperSU, can't.
I ended up flashing a new rom to get rid of this.
Click to expand...
Click to collapse
Yes, i kinda agree with you. It cant be replaced with other root app ( i also tried many times) but this is most likely fastest and easiest way to obtain root acces with honor 6. I havent seen any adds or pop-ups while using kingroot doe. I just deleted purify and disabled all i didnt like in kingroot settings.

Its ok and it can easily be removed and replaced with supersu. Either through terminal or by apps like supersu me.
If you cant replace it, you didnt search enough.
/edit
Ok, Honor strikes again [emoji23]

leechseed said:
Its ok and it can easily be removed and replaced with supersu. Either through terminal or by apps like supersu me.
If you cant replace it, you didnt search enough.
Click to expand...
Click to collapse
I have replaced it with other phones, but with honor, it just doesnt work, it just removes root but supersu stucks abd doesnt grant sudo access. Kingroot itself isnt that bad but supersu is awesome.
Not quite a developer yet, trying tho

Managed to Root my H60-L04 Android M
Hi,
finally managed to root my H60-L04 Android M (B810) via:
http://www.pantomath.xyz/honor-6-root-guide-marshmallow-emui-4-0-twrp/
Really easy, and without any issues

apatrahil said:
Hi,
finally managed to root my H60-L04 Android M (B810) via:
http://www.pantomath.xyz/honor-6-root-guide-marshmallow-emui-4-0-twrp/
Really easy, and without any issues
Click to expand...
Click to collapse
this look just like SRK tool....
Sent from my H60-L12 using Tapatalk

Ranteis said:
Easy way to root HH6​No Computer needed, just one simple apk and about 10 minutes of your precious Time
1st step: Own Huawei Honor 6
2nd step: Download and install This app
(Remember to allow unknown sources in settings)
3rd step: Launch it, it will say "not supported" but gives you a chanse to give it a go anyway. So do that. It will start rooting. App may close several times but it will not crash. Just open it again from " recent apps" and it will roll again.
Wait for 100% and rooting is done.
Posting pics soon.
You are welcome
Click to expand...
Click to collapse
kingroot not installed...any ideas??? already install before but its keep crash and unroot itself...i try uninstall and try to do again but kingroot cant be installed...

mrconfius said:
kingroot not installed...any ideas??? already install before but its keep crash and unroot itself...i try uninstall and try to do again but kingroot cant be installed...
Click to expand...
Click to collapse
You have honor 6 L04?
Android version?
Unistalled kingroot before trying again?

Ranteis said:
You have honor 6 L04?
Android version?
Unistalled kingroot before trying again?
Click to expand...
Click to collapse
yeah h06-L04..
emui 4.0 android 6.0
yeah...already uninstalled it and trying again..but not working..app not installed

Same issue
I have h60-l04
Android 6.0
Emui 4.0
I tried rooting but it does not allow me to do so i says theres no root stg for this phone and reguest gor this module
Is there a away to bybass that??
I hope some could help me to root this phone:crying:

Zeyzed said:
I have h60-l04
Android 6.0
Emui 4.0
I tried rooting but it does not allow me to do so i says theres no root stg for this phone and reguest gor this module
Is there a away to bybass that??
I hope some could help me to root this phone:crying:
Click to expand...
Click to collapse
same w/ u but now i using EMUI 4.0.1 kingroot not supported w/ this version:crying:

As in instructions, it says device not supported BUT it gives you option to try anyway. And it works