Database Info

Stock OTA Update and Checking the Status of your Phone

I'm using the default ROM for my One X and I'd like to update it (I haven't since I got it 6 month ago); do I need to re-lock the bootloader and unroot it before I can use the OTA update? Also it's been a while since I even fiddled with my phones software so I forgot anything else I may have done, is there a way I can check to see what else has been done and if it's safe to update it?
Currently I have:
Android Version: 4.0.3
HTC Sense Version: 4.0
Software Number: 1.73.631.1
HTC SDK API Level: 4.11
HTC Extension Version: HTCExtension_403_1_HA_4

What firmware are u on currently for starters
Sent from my HTC One XL using xda app-developers app

I added the info to the original post

bman3k said:
do I need to re-lock the bootloader and unroot it before I can use the OTA update?
Click to expand...
Click to collapse
Your phone should be factory default before performing OTA updates or results may be unexpected.
Most OTA updates are patch file based and require the files to be exactly what is expected.
There have been known issues with root being detected and the OTA failing.
Rooted phones progressing with an update but root lost after the update.
System files being modified and the OTA failing.
Recovery must be factory; not TWRP or CWM.
CID and MID must suit OTA.
The only modification I would consider safe through all OTA's so far has been SuperCID.

If you have any interest in rooting and flashing custom ROMs, I would suggest rooting and unlocking the bootloader now, while you are on 1.73, and not updating via OTA. The latest 2.20 update will also update your hboot, which plugs the holes by which kernels and radios can be flashed from recovery.

Since you're with att you can expect the jelly bean update any time from now till the end of the world which isn't fun waiting for .. I'd suggest if you were rooted download goo manager flash twrp....than flash a solid ics Rom if your prefer ice sense or you can go venture into the jb realms

omario8484 said:
Since you're with att you can expect the jelly bean update any time from now till the end of the world which isn't fun waiting for .. I'd suggest if you were rooted download goo manager flash twrp....than flash a solid ics Rom if your prefer ice sense or you can go venture into the jb realms
Click to expand...
Click to collapse
Agree. If you are already BL unlocked and rooted, why go through the hassle of relocking the BL and returning to stock, just to wait for the OTA?
Just flash a JB ROM, as there are already stock and custom JB ROMs posted in Development.
Plus, until the OTA actually hits, we don't know if it will even be rootable. They have plugged the existing root exploits with every successive AT&T OTA for this phone so far. No reason to think any different for the JB update.
Just flash a JB ROM and stay rooted.

Ya I really like viper xl v3 . Just apply fix listed on op and you should be good to go
Sent from my HTC One XL using xda premium

Stock OTA is not WORTH IT IMO, been there
Reselling the phone is probably the only reason i'd revert to stock.

Ok, so I tried to flash Android Revolution HD 18.0 instead of going back to stock. I used TWRP, but it said "unable to read zip file" and the flash failed, now my phone won't start up it just shows the HTC screen with "this build is for development purposes..." and continuously turns on and off.

bman3k said:
Ok, so I tried to flash Android Revolution HD 18.0 instead of going back to stock. I used TWRP, but it said "unable to read zip file" and the flash failed, now my phone won't start up it just shows the HTC screen with "this build is for development purposes..." and continuously turns on and off.
Click to expand...
Click to collapse
Ok you're really lucky you didn't just brick your phone.... You want to stay in the att one x forums.... Notice theres a title diff. You're lucky it didn't succesfully flash or your phone would be dead... That's an international one x rom

bman3k said:
Ok, so I tried to flash Android Revolution HD 18.0 instead of going back to stock. I used TWRP, but it said "unable to read zip file" and the flash failed, now my phone won't start up it just shows the HTC screen with "this build is for development purposes..." and continuously turns on and off.
Click to expand...
Click to collapse
Stick to the ROM's in our forum, I never heard of anything like that ROM for our phone sorry. Lucky you didn't brick it

O damn I feel very stupid now...
Can someone recommend me a JB ROM?
Also how would I even install one now? The AR HD one was the only ROM I had on my SD card
Edit: I figured out the Mount function in TWRP, so I know how to add new ROMs now

bman3k said:
O damn I feel very stupid now...
Can someone recommend me a JB ROM? Also how would I even install one now? The AR HD one was the only ROM I had on my SD card
Click to expand...
Click to collapse
Try them all, they are all good, the time it takes to ask for other peoples opinions you could have test driven them all yourself.

Are you looking for jb sense?

omario8484 said:
Are you looking for jb sense?
Click to expand...
Click to collapse
I'm just going to try a couple like wrecker suggested now that I've figured out how to flash ROM's properly
Thanks for your guys' helps
Is there a way to back up my apps/texts and stuff when flashing ROM's? I totally forgot about that and lost all of it, I didn't have anything particularly important, but it'd be a hassle to redownload everything everytime. I had Titanium Backup, but that's not a recovery for if you reflash right?

bman3k said:
I'm just going to try a couple like wrecker suggested now that I've figured out how to flash ROM's properly
Thanks for your guys' helps
Is there a way to back up my apps/texts and stuff when flashing ROM's? I totally forgot about that and lost all of it, I didn't have anything particularly important, but it'd be a hassle to redownload everything everytime. I had Titanium Backup, but that's not a recovery for if you reflash right?
Click to expand...
Click to collapse
Funny that you bring titanium up...titanium helps you back up apps it also backs up your app data...and for sms just download something from the market here's one download the app super backup and you can backup your sms

So I installed Cyanogen 10.0.0 but it didn't come with Google Play so I installed Gapps as well; now I keep getting the "Android Keyboard ASOP has stopped working" and I can't do anything. I've tried multiple versions of Gapps but they all give the error. I've also tried installing a keyboard apk on it's own but I am still unable to type anything.
Edit: Also when I downloaded Google Play as an apk separately it would crash immediately, but when I installed it from Gapps it was ok.

bman3k said:
So I installed Cyanogen 10.0.0 but it didn't come with Google Play so I installed Gapps as well; now I keep getting the "Android Keyboard ASOP has stopped working" and I can't do anything. I've tried multiple versions of Gapps but they all give the error. I've also tried installing a keyboard apk on it's own but I am still unable to type anything.
Edit: Also when I downloaded Google Play as an apk separately it would crash immediately, but when I installed it from Gapps it was ok.
Click to expand...
Click to collapse
You did a full wipe before hand right?

I did the factory, system, cache and dalvik cache wipes
Edit: I got it to work, not really sure what I did different =/

[Q] Why is my Model number wrong and is it a bad thing?

I'm sorry to sound like a noob, but I've searched and searched, and haven't been able to find an explanation. When I go to my phone info section (About phone), my phone is listed as a Galaxy Nexus, despite the fact that my phone is a Galaxy S3 (d2vzw). I'm not sure when this changed and I don't remember exactly what it used to say, but I know this was not it. I can't figure out if it was the ROM or the kernel that changed it (though I have my doubts it was the kernel).
I am using the AOKP rom and the KT747 kernel.
The only reason I noticed this is because I've been using the goomanager app to let me know when there have been updates to my ROM and to my surprise one day, I was notified that there was an update (even though I wasn't expecting one). I downloaded it (without even paying attention to the file name) and tried flashing it a few times, but it kept failing no matter what I did. I started to wonder if the recovery was the issue, so I took that opportunity to move from clockworkmod to TWRP. That did not change the outcome. I then decided to check the file itself by googling its file name and I was shocked to learn that it was for the Galaxy Nexus... not for the GS3! I finally went into About phone and noticed my phone was listed as a Galaxy Nexus.
As it stands now, I'm not sure if the reason it's listed wrong is because of me trying to flash the wrong ROM, or if it was like that beforehand. What I do know is that because it's listed wrong, goomanager keeps telling me there's an update to my ROM (and keeps pointing me to that original file I tried flashing).
I only recently flashed a different kernel than what came with the phone and I believe this was after the name was already wrong, so I doubt that's to blame. To be safe, I tried installing a different kernel (I think it was called "Lean" kernel), but that ended up preventing my phone from ever booting (seriously, I waited about an hour and even tried rebooting, but it never actually booted), so I ended up reflashing the KT747 kernel and it's working again.
Any idea as to why this is happening? Is there a way to fix this? Other than the fact that goomanager keeps looking for the wrong updates, is it bad for my phone?
Thanks in advance!

You can modify the build.prop to make your phone think its anything. So the ROM has a nexus written in the build.prop. are you using an unofficial build or the official one for our phone?
Also it really doesn't matter that it is listed as a nexus. Just disable goo manager updates. And then you will ha e to manually check for d2vzw updates. There is nothing to worry about. As far as lean kernel not booting. Be sure to use the right kernel (aosp or stock) and if your using the 4.2 version of AOKP you need the new 4.2 kernel, which I am personally unfamiliar with lean if it has a 4.2 kernel
Sent from my SCH-I535 using Tapatalk 2

faehsemc said:
You can modify the build.prop to make your phone think its anything. So the ROM has a nexus written in the build.prop. are you using an unofficial build or the official one for our phone?
Click to expand...
Click to collapse
I'm using the official Milestone build released on 2012-10-29. I know it wasn't changed in the builds prior to that because goomanager was always able to point me to the next, correct update. If they did change the build.prop for that release, what would have been the point?
faehsemc said:
Also it really doesn't matter that it is listed as a nexus. Just disable goo manager updates. And then you will ha e to manually check for d2vzw updates.
Click to expand...
Click to collapse
Well, you're right except that it kind of does matter if goomanager is no longer able to find the right updates. I know I can disable the checks, but I don't want to have to remember to check manually.
faehsemc said:
As far as lean kernel not booting. Be sure to use the right kernel (aosp or stock) and if your using the 4.2 version of AOKP you need the new 4.2 kernel, which I am personally unfamiliar with lean if it has a 4.2 kernel
Click to expand...
Click to collapse
I thought I had checked to make sure it was an aosp version and not touchwiz, but now I don't remember. The Milestone build of AOKP I'm on is 4.1.2.

I wanna say getting google wallet working you have to edit the device in the build.prop? Or is that on TW roms?

x714x said:
I wanna say getting google wallet working you have to edit the device in the build.prop? Or is that on TW roms?
Click to expand...
Click to collapse
Oh wow, I think you just answered my question. Thank you. I do have Google Wallet on my phone, but I installed it using an app called Wallet Installer, so I didn't actually change it myself.

JerseyMike4 said:
Oh wow, I think you just answered my question. Thank you. I do have Google Wallet on my phone, but I installed it using an app called Wallet Installer, so I didn't actually change it myself.
Click to expand...
Click to collapse
Ya then thats why it changed

Right after my last post, I opened the Wallet Installer app and saw that there's a button to restore build.prop, so I pressed it and my phone rebooted. Afterwards, it was back to normal. What's odd is that Google Wallet appears to still work properly (I think; all I've ever done is add a credit card). I guess it only needs to change it for it to install.

Help Deodexing stock rom-Verizon i535PP

im in need of help deodexing. i used the universal deodexer and didnt get proper start up. it became stuck on verizon logo. i reflashed the firmware so its like new again. question is how to properly deodex the stock rom so i can theme status icons? maybe some zip file that i can use in safestrap to make things easier. oh im using verizon prepaid galaxy s3 which is i535PP. any help is appreciated

bjf189 said:
im in need of help deodexing. i used the universal deodexer and didnt get proper start up. it became stuck on verizon logo. i reflashed the firmware so its like new again. question is how to properly deodex the stock rom so i can theme status icons? maybe some zip file that i can use in safestrap to make things easier. oh im using verizon prepaid galaxy s3 which is i535PP. any help is appreciated
Click to expand...
Click to collapse
If root can even be obtained this might be an option, otherwise your probably out of luck
Sent from my Nexus 5

Root has been obtained @ShapesBlue
Nobody has created a ROM for i535PP users yet(the i535 roms run but no wifi/data). And you're correct about having to use safestrap to flash it.If you're comfortable with a bash terminal you can try using one of the various tools found around here to modify the stock rom. If you're not then I'll see what I can do this weekend and try to get something for us i535pp users (after a day or so of testing)

ShapesBlue said:
If root can even be obtained this might be an option, otherwise your probably out of luck
Sent from my Nexus 5
Click to expand...
Click to collapse
Ok, there wasn't really a need to mention me in this thread. Everytime someone does that I get an email. And just because root has been obtained doesn't mean you can flash roms via safestrap
Sent from my Nexus 5

ShapesBlue said:
Ok, there wasn't really a need to mention me in this thread. Everytime someone does that I get an email. And just because root has been obtained doesn't mean you can flash roms via safestrap
Sent from my Nexus 5
Click to expand...
Click to collapse
Flashing via safestrap appears to work fine on my i535pp. The only issue I ran into was wifi not working with roms meant for the i535. And sorry for you having to receive an email for that.

OpenSourcererSweg said:
Flashing via safestrap appears to work fine on my i535pp. The only issue I ran into was wifi not working with roms meant for the i535. And sorry for you having to receive an email for that.
Click to expand...
Click to collapse
Its cool. Good to see safestrap works on the prepaid version also
Sent from my Nexus 5

I'm not sure what a bash terminal is unless it's the same thing as the terminal emulator. I tried using that rom that's called paulpizz or something like that. I used some other rom to. The paulpizz one always failed to install even after downloading it a third time. The other one i can't remember the name but it installed but wouldn't start at all. It would just go black and bootloop and goes into stock recovery for some reason. I came across the nf5 module when i found that paulpizz rom on the goo server they hosted it on. So i got the module and i figured if i were to flash the module over the i535 rom that it would fix the wifi an data problem but never got an answer because it always failed to start up properly and would just bootloop into stock recovery. Ugh Verizon is making things so difficult with modding lol. As of now I'm just using xposed to get at least some theming in and tweaks. I couldn't get any deodex program to work. Whenever i used the deodex files and pushed them to the system of apps and framework, it would restart and just stick on the Verizon logo. So i had to flash the firmware to fix the problem.

When i was on 4.3 with this phone safestrap worked and i got the wifi and data sim error. Now that i got it replaced I'm running the kernel of July 22 2014. Everyone was saying I'm out of luck but i came across kingroot and got the most recent version and it worked. I have root. Installed safestrap for 4.4 and it runs fine but can't get any custom roms to boot. I only managed to find one 4.4 touchwiz rom unfortunately

OpenSourcererSweg said:
Root has been obtained @ShapesBlue
Nobody has created a ROM for i535PP users yet(the i535 roms run but no wifi/data). And you're correct about having to use safestrap to flash it.If you're comfortable with a bash terminal you can try using one of the various tools found around here to modify the stock rom. If you're not then I'll see what I can do this weekend and try to get something for us i535pp users (after a day or so of testing)
Click to expand...
Click to collapse
OpenSourcererSweg said:
Flashing via safestrap appears to work fine on my i535pp. The only issue I ran into was wifi not working with roms meant for the i535. And sorry for you having to receive an email for that.
Click to expand...
Click to collapse
Can you tell me what rom you have successfully flashed with safestrap? I would like to test something

bjf189 said:
Can you tell me what rom you have successfully flashed with safestrap? I would like to test something
Click to expand...
Click to collapse
http://forum.xda-developers.com/gal...iterom-v1-0-i535vrudne1-t2805797/post53919312
If you're going to try flashing an i535 rom and then the i535pp modules let me know how that goes, can't test as I won't be able to do anything till the weekend. If that's the case then there's no need for roms for the pre paid version. Cyanogenmod was also bootable but very buggy.

OpenSourcererSweg said:
http://forum.xda-developers.com/gal...iterom-v1-0-i535vrudne1-t2805797/post53919312
If you're going to try flashing an i535 rom and then the i535pp modules let me know how that goes, can't test as I won't be able to do anything till the weekend. If that's the case then there's no need for roms for the pre paid version. Cyanogenmod was also bootable but very buggy.
Click to expand...
Click to collapse
I'll let you know how it goes and thank you. How is it that you were able to boot CM? From my understanding being that the bootloader is locked and has Knox for extra security to make the unlocking like impossible. But a genius came up with safestrap so we are able to use some custom roms but the down side is that it has to be the same Android OS and has to be a touchwiz based rom. So how are you getting lucky with all this? I love CM and I'd pick CM over any custom rom any day but i gave up an lost hope of ever getting CM because of the locked bootloader

bjf189 said:
I'll let you know how it goes and thank you. How is it that you were able to boot CM? From my understanding being that the bootloader is locked and has Knox for extra security to make the unlocking like impossible. But a genius came up with safestrap so we are able to use some custom roms but the down side is that it has to be the same Android OS and has to be a touchwiz based rom. So how are you getting lucky with all this? I love CM and I'd pick CM over any custom rom any day but i gave up an lost hope of ever getting CM because of the locked bootloader
Click to expand...
Click to collapse
Safestrap 3.75 had support for AOSP roms (wifi/data didn't work for them either) and 4.0 dropped support for that (there is currently no point). Read the thread for more info http://forum.xda-developers.com/showthread.php?t=2797314

Ok i wasn't using safestrap 4.0. I had 3.75 B05 which i thought was the latest version they had. I'm updated to 4.0 now and about to test the modules on the superlite rom

Update: i have tried the super lite rom using safestrap. The boot animation won't work during start up. When it gets to the welcome screen it freezes. It still does it even without applying the nf5 module. It freezes and will keep popping up that system isn't responding. System just keeps freezing and prompting me to wait or force close. So not sure why my s3 has a problem running it but yours don't

bjf189 said:
Update: i have tried the super lite rom using safestrap. The boot animation won't work during start up. When it gets to the welcome screen it freezes. It still does it even without applying the nf5 module. It freezes and will keep popping up that system isn't responding. System just keeps freezing and prompting me to wait or force close. So not sure why my s3 has a problem running it but yours don't
Click to expand...
Click to collapse
Did you wipe cache/data after installing? Other than that I can't think of anything that would cause that

OpenSourcererSweg said:
Did you wipe cache/data after installing? Other than that I can't think of anything that would cause that
Click to expand...
Click to collapse
Well no. The instructions just said to do a full wipe off everything then install and reboot so extra what i did. What version you running of the rom?

bjf189 said:
Well no. The instructions just said to do a full wipe off everything then install and reboot so extra what i did. What version you running of the rom?
Click to expand...
Click to collapse
I'm running the stock prepaid rom, not superlightrom, sorry if there's any confusion there.
When I tried out superlightrom (quite some time ago) it appeared to work fine (excluding wifi/data and nagging about no SIM card being inserted, nothing like what you're describing) and I went back to stock.

Oh ok. Well it seems that the prepaid version or the s3 in general is dead. That's unfortunate

AOSP 6.0.0 Marshmallow Build

So with the Sony binaries and Marshmallow sources released, I figured it was worth trying a build.
I don't have my Z3C on me so no idea how well it'll work but here you go. Roasted Marshmallow, hot off the build server
EDIT: Title is probably wrong, as pointed out by a mod. I based it on the Git ref being "6.0_r1", which I thought meant "6.0.1". This is really 6.0. Specifically, a build based on the exact instructions posted by Sony.
MOD EDIT by @gregbradley
I edited the title for you .

Flashed on a 5803 on T-Mobile USA and it isn't seeing the SIM card. Also, when it unlocks, it gets hung up for a few seconds.

thatguy222 said:
Flashed on a 5803 on T-Mobile USA and it isn't seeing the SIM card. Also, when it unlocks, it gets hung up for a few seconds.
Click to expand...
Click to collapse
dmesg suggests that this may be due to lack of modem.mdt. I'll look into it.
EDIT: From what I can see this looks like a proprietary Sony file that they haven't released. It may also be built with the kernel but that I can't say. Either way I opened a bug on Github that they can hopefully address.

Okay great
---------- Post added at 02:29 AM ---------- Previous post was at 02:15 AM ----------
Gairtial said:
dmesg suggests that this may be due to lack of modem.mdt. I'll look into it.
EDIT: From what I can see this looks like a proprietary Sony file that they haven't released. It may also be built with the kernel but that I can't say. Either way I opened a bug on Github that they can hopefully address.
Click to expand...
Click to collapse
Bummer. Thanks for nothing, Sony!

thatguy222 said:
Okay great
---------- Post added at 02:29 AM ---------- Previous post was at 02:15 AM ----------
Bummer. Thanks for nothing, Sony!
Click to expand...
Click to collapse
Don't jump the gun. There are a lot of files in a standard Android build and I don't know if it comes from them or if it's a product of the build process. It could just be a misconfiguration on my part. The bug is for info, not because it's their fault.

http://forum.xda-developers.com/xperia-z-ultra/orig-development/rom-marshmallow-6-0-z-ultra-t3224321
They seem to have fixed the modem by using the files from the current firmwares.

Just refreshing the page for a build with working modem as i don't have the environment neither the skill to build from scratch

aniket_ said:
http://forum.xda-developers.com/xperia-z-ultra/orig-development/rom-marshmallow-6-0-z-ultra-t3224321
They seem to have fixed the modem by using the files from the current firmwares.
Click to expand...
Click to collapse
I tried that last night using one of the files from the various vendor repos but no luck. The kernel module threw errors about the data being invalid. I'll try extracting from official firmware when I get home. Also that thread doesn't yet have anyone confirming that it works :/
fratzika said:
Just refreshing the page for a build with working modem as i don't have the environment neither the skill to build from scratch
Click to expand...
Click to collapse
I don't have my Z3C with me so I'm unlikely to be able to do anything helpful for ~9h, when I get home. You'll have to be a little patient

Okay, got a build up to date with Git and with a modem copied from one of the latest firmwares (ripped it from the SLIM stock ROM). Wouldn't get your hopes up but it might work
EDIT: No luck. It doesn't seem there's an available modem that's likely to work. Unless someone can suggest another device with close enough hardware and a working Marshmallow modem (seems doubtful), we're lost until someone can extract one from a legitimate Sony firmware or Sony releases it to us (seems unlikely).

Thanks for doing this Gairtail, let's hope you get it up and running soon (if Sony or someone else uploads the modem file..)

Jerpelea says modem is now working on shinano, using the new kernel blobs.
(Just forwarding information I've been told that you might find useful.)

http://www.xperiablog.net/2015/10/2...lable/?utm_source=dlvr.it&utm_medium=facebook refer here to get that modem from the ftf that sony relased for both z3 and z3c !

someone755 said:
Jerpelea says modem is now working on shinano, using the new kernel blobs.
(Just forwarding information I've been told that you might find useful.)
Click to expand...
Click to collapse
Theliakos said:
http://www.xperiablog.net/2015/10/2...lable/?utm_source=dlvr.it&utm_medium=facebook refer here to get that modem from the ftf that sony relased for both z3 and z3c !
Click to expand...
Click to collapse
Thanks. I tried to do a compile today but there were some issues in the repo that broke it (qcom media stuff). I'll try in another day or two and hopefully things will have settled down.

Since you're talking about the modem parts, and i seem to have a problem with my WiFi, is anybody in here able to provide the /persist and /modem folder from the stock MM rom? Mine seems to have been lost after flashing an alternative rom

Gairtial said:
Thanks. I tried to do a compile today but there were some issues in the repo that broke it (qcom media stuff). I'll try in another day or two and hopefully things will have settled down.
Click to expand...
Click to collapse
I built on Novenber 5th, worked just fine. Just synced and started another build, but the November security update isn't here yet, bummer. (I reckon another 24 hours should do it.)
If you'd like, I can upload the build for you.
Apo14 said:
Since you're talking about the modem parts, and i seem to have a problem with my WiFi, is anybody in here able to provide the /persist and /modem folder from the stock MM rom? Mine seems to have been lost after flashing an alternative rom
Click to expand...
Click to collapse
I don't know for sure, but wouldn't flashing a stock FTF solve this?
Overall, I'm starting to like AOSP. Camera now works on every boot (unlike Nougat, because of the memory allocation gone bad), though AF and AE are a bit off, and it's stable enough to use as a daily driver.
Also, not sure if you guys also get this, but I've been getting the dwc3-msm wakelock a lot. Happens because of kernel bug that keeps phone awake, thinking it's connected to a power source even after it's been disconnected. Drained my battery for 17 hours before I even noticed. I don't know if the official method with prebuilt kernels also has this, but I build the upstream sonyxperiadev/kernel repo myself. If you use a kernel source too, instead of using the prebuilt kernels, you could try picking this. Looks to be working for me, but it hasn't been merged yet, so take that as you will.
EDIT: Noticed this isn't upstream Marshmallow, but r1. Bummer.
You should really switch to 6.0.1, the 1.3.3 kernel is much better than 1.2.2 (and without the memalloc reboots caused by media/video). Though if you prefer not to switch, you could still add my uploads to the OP alongside yours if you want? That way we have 6.0 and 6.0.1 under one roof?

@someone755 so should i be able to extract those files without the need to flash?

Apo14 said:
@someone755 so should i be able to extract those files without the need to flash?
Click to expand...
Click to collapse
No reason to avoid flashing, really. Make a backup of system and boot, don't wipe userdata, and have a recovery image handy. Flash FTF, flash recovery, restore system and boot.
The only things that get updated are your modem and bootloader etc, your system and data stay untouched.
Though depending on when you last flashed an FTF, it may be a good idea to wipe your data in recovery before you flash (and back it up, of course). Some firmware can only be updated after Android has booted, like NFC for example.

So best would be to completely start from scratch and wipe everything i guess? Do you have any links to guides for FTF etc? Im not that into these things :/

Apo14 said:
So best would be to completely start from scratch and wipe everything i guess? Do you have any links to guides for FTF etc? Im not that into these things :/
Click to expand...
Click to collapse
I'm not saying it's best, but it could help you avoid potential issues. I don't know what all you've been doing with your device, so I can't make the call for you. Just telling you how it is.
This is a nice thread: http://forum.xda-developers.com/z3-compact/general/list-stock-firmwares-d5803-d5833-t2906706 You'll also need FlashTool if you go down this route, you can Google it to download.
EDIT: @Gairtial I have today's 6.0.1 source in a nice zip. https://www.androidfilehost.com/?w=files&flid=127723
There's also a folder with the kernels for 6.0.1/7.0/7.1 that I'll try to keep up to date, if there's any interest for that. (The kernel zip will flash to any of the three Android versions, so long as the ROM is AOSP-based. Other than that, it's version-independent.)
Another note would be that I didn't make any changes to the ROM build. GApps will have issues starting unless you do some adb wizardry, and you'll get your recovery overwritten with the useless AOSP one if you flash the ROM zip in recovery. (You could also just try flashing system and boot through fastboot, though I haven't tried.)

someone755 said:
Overall, I'm starting to like AOSP. Camera now works on every boot (unlike Nougat, because of the memory allocation gone bad), though AF and AE are a bit off, and it's stable enough to use as a daily driver.
Click to expand...
Click to collapse
I'm tired of using stock Sony roms, and I'm starting to hate them. Still waiting for those latest camera blobs though for AOSP. I've tried your uploaded build, but it's causing a bootloop somehow. Didn't flash the separate kernel, but I don't see the need for that since there is one included in rom zip. Not sure what is the problem...

Cyanogen mod ROM repository

Hi guys, been off the scene for quite a while, so please forgive me if I'm not really up to date with the latest.
I own a OPO anad currently I have Cyanogen 12.0 installed. Lately my phone started to play up, not sure if I got some kind of malware but I thought it was a good occasion to update my ROM. Historically, I've always used CM but they seem to have disappeared completely (they used to have a nice website with all the phone models and the corresponding compatible ROMs, but I suppose that since when they went out of business things might have changed quite a bit). Can they be found somewhere? If not, I'd appreciate any advice on what ROM would be good to have - considering though that even my Teamwin Recovery needs updating as somehow it thinks I'm on an older version of android.
Cheers

duratto said:
Hi guys, been off the scene for quite a while, so please forgive me if I'm not really up to date with the latest.
I own a OPO anad currently I have Cyanogen 12.0 installed. Lately my phone started to play up, not sure if I got some kind of malware but I thought it was a good occasion to update my ROM. Historically, I've always used CM but they seem to have disappeared completely (they used to have a nice website with all the phone models and the corresponding compatible ROMs, but I suppose that since when they went out of business things might have changed quite a bit). Can they be found somewhere? If not, I'd appreciate any advice on what ROM would be good to have - considering though that even my Teamwin Recovery needs updating as somehow it thinks I'm on an older version of android.
Cheers
Click to expand...
Click to collapse
Firstly,this should be in QnA..
Secondly,
For latest recovery,
https://forum.xda-developers.com/oneplus-one/development/recovery-twrp-3-0-3-k1-t3563692
Recommended rom- https://forum.xda-developers.com/on...m-kernel-unofficial-lineageos-14-1-3-t3626403

thanks, do I need to install the recovery first and then the ROM? Also, are there any instructions for the recovery here or should I have a look on the net?
thanks

duratto said:
thanks, do I need to install the recovery first and then the ROM? Also, are there any instructions for the recovery here or should I have a look on the net?
thanks
Click to expand...
Click to collapse
Yes,to flash recovery the process is same as you did for the previous Twrp that is now on your device.