Related
Here you can download OTA, fresh firmware or system image to update your device.
OTA_M8_MINI_UL_K44_SENSE60_HTC_Europe_2.19.401.2-2.18.401.3_release_448048.zip [41.2 MB]
firmware.zip only [19.6 MB]
2.19.401.2_boot_system_2015-09-21--20-48-04_KOT49H.zip [TWRP] [1.15 GB]
Downloads: mega
Let's see what's underneath
Main difference, I believe, is a security fix (libStageFright). I assume, that's it:
/system/framework/android.policy.jar
/system/framework/conscrypt.jar
/system/framework/framework3.jar
/system/lib/modules/moc_crypto.ko.sig.3.4.10
Zip also contains lots of *.p files (odexes, apk, jars mainly). Viewable through windows explorer. Don't know, what's that. Looks like a hash or a signature.
OTA includes firmware.zip containing {boot, hboot, recovery}, which can be opened through WinRAR (7Zip 15β failed). If you want just firmware, take it. Should be fastboot flashable.
*Additional notes*
Next lines describe my experience before I returned the device state to nearly stock.
Hello there. )
Want to share my experience. I have 2.18.401.3 and got promt to upgrade to 2.19.401.2.
Basically, as I get it, you need original recovery and that's it. (Pushed original kernel just in case. Also device is unlocked (tampered))
But under updating process the script mechanism checks some files to be original. Many system odexes, framework stuff and some libs.
My update failed on checking Books.odex (meanwhile, this app was deleted and redownloaded as user-app)
So, I might try to edit updater-script later or just copy files from update to folders they belong. The ota got a simple and obvious updater script for people who used to deal with them before. I'm considering delete parsing part or just push on screen what gives fail, but let updating happen. Need to be tested with system backup.
city2026 said:
OTA_M8_MINI_UL_K44_SENSE60_HTC_Europe_2.19.401.2-2.18.401.3_release_448048.zip [41.2 MB]
Download: mega
Let's see what's underneath
Main difference, I believe, is a security fix (libStageFright). I assume, that's it:
/system/framework/android.policy.jar
/system/framework/conscrypt.jar
/system/framework/framework3.jar
/system/lib/modules/moc_crypto.ko.sig.3.4.10
Zip also contains lots of *.p files (odexes, apk, jars mainly). Viewable through windows explorer.
OTA includes firmware.zip containing {boot, hboot, recovery}, which can be opened through WinRAR (7Zip 15β failed).
*Additional notes*
Hello there. )
Want to share my experience. I have 2.18.401.3 and got promt to upgrade to 2.19.401.2.
Basically, as I get it, you need original recovery and that's it. (Pushed original kernel just in case. Also device is unlocked (tampered))
But under updating process the script mechanism checks some files to be original. Many system odexes, framework stuff and some libs.
My update failed on checking Books.odex (meanwhile, this app was deleted and redownloaded as user-app)
So, I might try to edit updater-script later or just copy files from update to folders they belong. The ota got a simple and obvious updater script for people who used to deal with them before. I'm considering delete parsing part or just push on screen what gives fail, but let updating happen. Need to be tested with system backup.
Click to expand...
Click to collapse
My update stopped for "basicdreams.odex". If you are able to get the update flashed do let the community know
TWRP system backup added
csoulr666 said:
My update stopped for "basicdreams.odex". If you are able to get the update flashed do let the community know
Click to expand...
Click to collapse
I tried to update from recent backup (the one before I changed kernel and deleted system apps), but facebook.odex didn't let me.
Finally, the very first backup did it. I took only system and boot, switched twrp recovery to htc, skipped all setup and installed OTA over fresh system.
Here you go. Now you have TWRP image of this update.
BTW, kernel version is different. CL build number is the same.
Hi,
can't I just flash it somehow with TWRP?
The standard update way does not work for me, because of changed *.odex files.
Already tried to flash original recovery etc.
Thanks
ash0r said:
Hi,
can't I just flash it somehow with TWRP?
The standard update way does not work for me, because of changed *.odex files.
Already tried to flash original recovery etc.
Thanks
Click to expand...
Click to collapse
Unfortunately you cannot flash this with TWRP.
Is there a possibility to install this update (or any OTA updates) without having a "not-touched" system?
I could of course flash the TWRP recovery (what I've already done - it worked) but in that case I lose all my modifications. Is it possible to restore the TWRP recovery from that post and afterwards restore my own recovery without overwriting the system files which are needed to be up to date?
Thanks
ash0r said:
Is there a possibility to install this update (or any OTA updates) without having a "not-touched" system?
I could of course flash the TWRP recovery (what I've already done - it worked) but in that case I lose all my modifications. Is it possible to restore the TWRP recovery from that post and afterwards restore my own recovery without overwriting the system files which are needed to be up to date?
Thanks
Click to expand...
Click to collapse
You can try to restore the TWRP backup in the post. And yes, you will lose every mod since it is a backup of the stock, unrooted firmware.
The main problem of flashing the OTA zip would be that you will have to relock the bootloader before installing . So if you unlock it again, the internal storage will be wiped. The best way is to backup everything(Including the internal storage) and then proceed.
Actually, you can save your data while upgrading from non-worthy stock.
So, you may do this
Full backup, you never know what can go wrong.
Save or make a note of what you changed by yourself in system (from busybox to xposed & various modes.). You may use TB for sys-apps and simple file copying for modes. *
Restore updated system image from 1st post, so you have updated system.
See if it worked out and restore/reinstall your other system stuff.
* Remember, you still may access files of your twrp backup images through some archiver. Like I do using 7-Zip.
It's very important to save backup somewhere, cause it might be that my image can be not absolutely clean or can be not absolute right for your phone (like sell location difference). So it'll be easy to return back to working machine.
For this purposes I also setted up my TB for daily auto-backup of texts and settings and weekly backup of apps.
---
Don't sure about relock for upgrading. It seems to be launching, but it needs pure system and original boot & recovery. Some fastboot-magic helps here. That's how I did it after restoring to the very first backup.
So I have build number 2.18.161.3 rooted software on Vodafone, and received an OTA update build number 2.18.161.5-2.18.161.3. Obviously when I come to update it it goes to my custom recovery and can't go any further.
A couple of queries though I wanted to delete all the bloatware from my stock rom, after rooting I found I needed to S-Off as the bloatware keeps coming back on reboot so here are my queries.
Can I delete the APK files from the new OTA update and will this remove them if I install the OTA as a zip through custom recovery. Or can I use this update to wipe the bloatware from it all advice would be helpful
The Watergod said:
So I have build number 2.18.161.3 rooted software on Vodafone, and received an OTA update build number 2.18.161.5-2.18.161.3. Obviously when I come to update it it goes to my custom recovery and can't go any further.
A couple of queries though I wanted to delete all the bloatware from my stock rom, after rooting I found I needed to S-Off as the bloatware keeps coming back on reboot so here are my queries.
Can I delete the APK files from the new OTA update and will this remove them if I install the OTA as a zip through custom recovery. Or can I use this update to wipe the bloatware from it all advice would be helpful
Click to expand...
Click to collapse
For bloatware removal just push a custom boot.img. Liberty kernel or dt2w presented here works fine, you may try them at least with making a backup of original kernel at first. (Custom made kernel might give you permission to write to /system without being s-off.)
I used liberty one, recently flashed the one with double tap to wake, works perfectly fine. Even sd is fine.
I'm not into kernels, perhaps as long as they suit your device they are fine.
OTA have its script, if it has such strings or if you write it into the script, you may delete some apps. Maybe, didn't try nothing with ota scripting. It easier to find working universal bloatware removal script as flashable zip package.
Otherwise, ota just adds some stuff or replaces current stuff.
My htc one mini 2 is all stock. Software number is 1.16.61.2 and my fon cant to update software. Please help. Sory for my english.
keninzeg said:
My htc one mini 2 is all stock. Software number is 1.16.61.2 and my fon cant to update software. Please help. Sory for my english.
Click to expand...
Click to collapse
Did you buy your phone from a carrier? Carrier phones get different software updates
csoulr666 said:
Did you buy your phone from a carrier? Carrier phones get different software updates
Click to expand...
Click to collapse
I bought it used, it has installed EE application from the UK. So is there a way to update. Thanks a lot...
I tried to install OTA_M8_MINI_UL_K44_SENSE60_HTC_Europe_2.16.401.1-1.16.401.2_release from stock recovery and failed.
keninzeg said:
I bought it used, it has installed EE application from the UK. So is there a way to update. Thanks a lot...
I tried to install OTA_M8_MINI_UL_K44_SENSE60_HTC_Europe_2.16.401.1-1.16.401.2_release from stock recovery and failed.
Click to expand...
Click to collapse
If it has EE applications then it is an EE branded phone. Your updates will arrive differently and will have a different software number. So using the Europe zip will not help.
city2026 said:
For bloatware removal just push a custom boot.img. Liberty kernel or dt2w presented here works fine, you may try them at least with making a backup of original kernel at first. (Custom made kernel might give you permission to write to /system without being s-off.)
I used liberty one, recently flashed the one with double tap to wake, works perfectly fine. Even sd is fine.
I'm not into kernels, perhaps as long as they suit your device they are fine.
OTA have its script, if it has such strings or if you write it into the script, you may delete some apps. Maybe, didn't try nothing with ota scripting. It easier to find working universal bloatware removal script as flashable zip package.
Otherwise, ota just adds some stuff or replaces current stuff.
Click to expand...
Click to collapse
Excellent thanks for the reply so in short,
Grab the downloads from above (4 in total?)
Push and override existing TWRP recovery back to stock recovery (Dumbass Details would be helpful as I have not done this in ages)
copy the ADB the new rom to the phone (Again please forgive me as I have not done this in a few years need a memory jog)
Again thanks in advance
The Watergod said:
Excellent thanks for the reply so in short,
Grab the downloads from above (4 in total?)
Push and override existing TWRP recovery back to stock recovery (Dumbass Details would be helpful as I have not done this in ages)
copy the ADB the new rom to the phone (Again please forgive me as I have not done this in a few years need a memory jog)
Again thanks in advance
Click to expand...
Click to collapse
If you'll ask more specificly, I'll provide even shorter reply. )
As I get it, you ask for some short check-list / instruction
You need one of three files I uploaded, based on what do you want. )
You can flash big 1 gb system image v2.19.401.2 through twrp.
You can grab small upgrade package and update your 2.18.401.3 by yourself to have 2.19.401.2. Original firmware and fresh rom state might be needed.
You have other needs, you need just freshest kernel or etc., you grab firmware package and try hook it with bootloader or unzip and get the thing you need.
Pick the option and I'll write simple instruction.
I forget to read your previous post. ) So, you have 2.18.161.3 Vodafone. With root privileges (half-root, I assume)
So, yes, you need to restore original recovery of yours. Then it could handle the ota. If you can get it somewhere, you can update. You can get it in vodafone firmware (big package with everything) or if someone made recovery backup earlier.
My upload contains files for non-locked (operator's) devices.
As long as your phone has operator's rom, I can't give you proper advice. I assume, other recoveries/kernels/etc. might not be ok with your device due to hardware lock or difference.
But you can try always, if you sure you can handle it and revert or if you read on your situation enough. I can't advice you here on 100%.
But. If device is just a device, and roms are just roms (and some operator's special version is just a rom), you can flash other system and kernel and see what happens.
You may do a complete backup and save it somewhere and do one of the following:
Flash firmware.zip* contents, then go to TWRP and format all partitions except sdcard, then flash system image from above.
Just flash some custom 5.1.1 release. I use NostromoPop. It much smoother and it's lollipop.
*Firmware.zip contains boot, hboot, recovery. All that was for 2.19.401.2 but presumably can work separate. So you can get what you want and flash through adb. Like boot and hboot for proper device work on 2.19.401.2, or just recovery to try your vodafone ota w/o dramatic changes.
For futher safeness, you can backup hboot and boot or what you want.
I can recommend you to try custom sense-kernel for system write privileges.
city2026 said:
If you'll ask more specificly, I'll provide even shorter reply. )
As I get it, you ask for some short check-list / instruction
You need one of three files I uploaded, based on what do you want. )
You can flash big 1 gb system image v2.19.401.2 through twrp.
You can grab small upgrade package and update your 2.18.401.3 by yourself to have 2.19.401.2. Original firmware and fresh rom state might be needed.
You have other needs, you need just freshest kernel or etc., you grab firmware package and try hook it with bootloader or unzip and get the thing you need.
Pick the option and I'll write simple instruction.
I forget to read your previous post. ) So, you have 2.18.161.3 Vodafone. With root privileges (half-root, I assume)
So, yes, you need to restore original recovery of yours. Then it could handle the ota. If you can get it somewhere, you can update. You can get it in vodafone firmware (big package with everything) or if someone made recovery backup earlier.
My upload contains files for non-locked (operator's) devices.
As long as your phone has operator's rom, I can't give you proper advice. I assume, other recoveries/kernels/etc. might not be ok with your device due to hardware lock or difference.
But you can try always, if you sure you can handle it and revert or if you read on your situation enough. I can't advice you here on 100%.
But. If device is just a device, and roms are just roms (and some operator's special version is just a rom), you can flash other system and kernel and see what happens.
You may do a complete backup and save it somewhere and do one of the following:
Flash firmware.zip* contents, then go to TWRP and format all partitions except sdcard, then flash system image from above.
Just flash some custom 5.1.1 release. I use NostromoPop. It much smoother and it's lollipop.
*Firmware.zip contains boot, hboot, recovery. All that was for 2.19.401.2 but presumably can work separate. So you can get what you want and flash through adb. Like boot and hboot for proper device work on 2.19.401.2, or just recovery to try your vodafone ota w/o dramatic changes.
For futher safeness, you can backup hboot and boot or what you want.
I can recommend you to try custom sense-kernel for system write privileges.
Click to expand...
Click to collapse
Sorry to be a pain and your help is invaluable but just trying not to screw this up, My phone has been unlocked to all networks, and I would like either a stock rom bloatware free or a custom sense rom.
The phone is still S-On but I have unlocked the bootloader (Obviously). I Kept the stock rom hoping to use titanium backup to remove the bloat however I quickly found out the phone needed to be S-Off to remove it completely because as soon as the phone rebooted the bloatware re-installed it's self.
This is how I have the OTA update sat on my phone, I only Rooted for SU privs and put on TWRP everything else was stock. I did as a question in another post "Could I remove the APK from the OTA Zip on my phone then install it using TWRP and would that remove the bloat" but no response to that one.
Any help would be greatly recieved
The Watergod said:
Sorry to be a pain and your help is invaluable but just trying not to screw this up, My phone has been unlocked to all networks, and I would like either a stock rom bloatware free or a custom sense rom.
The phone is still S-On but I have unlocked the bootloader (Obviously). I Kept the stock rom hoping to use titanium backup to remove the bloat however I quickly found out the phone needed to be S-Off to remove it completely because as soon as the phone rebooted the bloatware re-installed it's self.
This is how I have the OTA update sat on my phone, I only Rooted for SU privs and put on TWRP everything else was stock. I did as a question in another post "Could I remove the APK from the OTA Zip on my phone then install it using TWRP and would that remove the bloat" but no response to that one.
Any help would be greatly recieved
Click to expand...
Click to collapse
Simply flash custom kernel: like liberty sense or stock sense w/ dt2w.
It will unlock the opportunity to write on every partition. I mean system, cache, etc.
The Watergod said:
Sorry to be a pain and your help is invaluable but just trying not to screw this up, My phone has been unlocked to all networks, and I would like either a stock rom bloatware free or a custom sense rom.
The phone is still S-On but I have unlocked the bootloader (Obviously). I Kept the stock rom hoping to use titanium backup to remove the bloat however I quickly found out the phone needed to be S-Off to remove it completely because as soon as the phone rebooted the bloatware re-installed it's self.
This is how I have the OTA update sat on my phone, I only Rooted for SU privs and put on TWRP everything else was stock. I did as a question in another post "Could I remove the APK from the OTA Zip on my phone then install it using TWRP and would that remove the bloat" but no response to that one.
Any help would be greatly recieved
Click to expand...
Click to collapse
Hi
I will assume you have the virus I have been seeing lately that wouldn't allow you to reset the phone, where in reset option the automatic restore option remains checked and you can't uncheck it.
The only solution is through TWRP, you need to enter TWRP, erase Cache, Data, System then flash the Lollipop ROM again or stock from here: http://forum.xda-developers.com/one...one-mini-2-t3250020/post63859743#post63859743
So there is no Rom available that's pretty much stock without bloatware that I can install with twrp? If not is there some idiots guide to putting my stock recovery back on thank you all again
Hi guys, I am only a very junior user who randomly flash his phone but most of the time I want my phone to be stable for work. I have had the situation since the recent OTA available, suffered a lot, would like to seek any help or advice.
I have a L09C635B361, Japan version. I updated to Android 7 via OTA, then unlocked / rooted under the instructions in this forum, forgot which exact thread though. Never thought of flashing any customized rom so I haven't realized the update problem until the recent OTA update (from B361 to B382) released. I got the push, downloaded B382 OTA package, restart to TWRP, then the flash was failed in TWRP screen. Restart again, the system notified there was a recent update failure. Then I installed Firmware Finder, downloaded the 3 update zip files, restart back to TWRP, still failed installing. Please refer to the failure screenshot for detailed reson. I have no idea what it said and how I should do differently.
No other way to go, I backed up my system, then wiped my phone, reset to factory mode, but brand new system was very strange: only voice input, no keyboard, missing several key functions such as camera. So I have to restore to my previous system, everything worked well except I can't open "clock".
Right now I am looking at system notification of B382 all the time, but I can't figure out how to get it updated, I don't mind if there's a way enables me go back to stock rom, but it's really hard to find the stock firmware for C635......
Thanks, appreciate your help in advance.
Hey man, try follow this guide to debrand your phone (get onto C432). It will probably unroot you and get you back to stock firmware as well.
https://forum.xda-developers.com/p9/how-to/guide-debranding-to-c432-updating-to-t3551523
Might want to check around first though, I dont want you bricking your phone on my account.
Good luck
xMrTROLLIPOPx said:
Hey man, try follow this guide to debrand your phone (get onto C432). It will probably unroot you and get you back to stock firmware as well.
https://forum.xda-developers.com/p9/how-to/guide-debranding-to-c432-updating-to-t3551523
Might want to check around first though, I dont want you bricking your phone on my account.
Good luck
Click to expand...
Click to collapse
Thanks bro. I will try the entire process when I have a backup phone.
One more thing is when I first tried to wipe phone, failed for several times. Plus the TWRP flashing error, I have suspect that there's something wrong with my partition information or format error. Can anyone help me to eliminate the possibility by the screenshot please?
On the other hand, I found 3 zip files on Firmware for same version update. Which one should I flash? If I need to flash all of the 3, is there a sequence?
The screenshot for the 3 zip files.
oushouseki said:
The screenshot for the 3 zip files.
Click to expand...
Click to collapse
You flash those in the order they appear. Except the last one, don't flash that (I think). From what I know it's always been update.zip and then update_hw.zip.
I see you're going to flash hw_jp which is the Japanese cust, so ignore the advice above about debranding to c432 as that's essentially the same thing as what you are about to do with those files. (C432 is the European version, which is called update_hw_eu.zip)
Also the voice input only bug is well known. You need to rollback to marshmallow (I forget which firmware but there's a thread on it here somewhere) and then OTA back to nougat and it should fix it.
lostunsunghero said:
You flash those in the order they appear. Except the last one, don't flash that (I think). From what I know it's always been update.zip and then update_hw.zip.
I see you're going to flash hw_jp which is the Japanese cust, so ignore the advice above about debranding to c432 as that's essentially the same thing as what you are about to do with those files. (C432 is the European version, which is called update_hw_eu.zip)
Also the voice input only bug is well known. You need to rollback to marshmallow (I forget which firmware but there's a thread on it here somewhere) and then OTA back to nougat and it should fix it.
Click to expand...
Click to collapse
Well, it ended up with paying 20USD to some "pro"s on taobao.com to unbrick my P9...sigh...am I too old to do this :crying:
Hi, I've got problem with my huawei p9
I really wanted an update to a newer build, so i used firmware finder using app proxy to download it before it will show in system updater. Installation went fine but after all i noticed two things: gps is not working - it shows place where i was two weeks ago as my current location and apps from google play to repair this aren't working - and the second problem is my build number. Instead of EVA-L09C150B385 which this update supposed to bring, it is NRD90M test-keys
And my question is that: Is it possible to reverse the update? And if not is it possible to somehow easily flash stock rom to this phone. The device has stock recovery, locked bootloader and was never rooted (and if possible I would rather prefer to keep it in that state)
I've heard about some method using the sdcard but at the moment i don't have big enough at home, so is there any other way?
Previously I was using LG smartphone and it could easily be fixed using LG flash tool
Is there some kind of similar app for huawei?
I know that google isn't biting and that there were similar threads before, but neither one of them really answers my questions and most of them are more about devices with custom recovery or/and root
I would suggest following the debranding method with downgrading to old Android and then install newer version on top.
https://forum.xda-developers.com/p9/how-to/guide-debranding-to-c432-updating-to-t3551523
You will need the bootloader unlock code.
Of course because of unlocking the bootloader, your device will be wiped so make sure you will have a backup of your data
As @edmun says above, I'd rebrand your phone and then update from there. You must get an SD dude, I can't do without mine.
Once rebranded, use the following tool (all instructions are there) to get to the latest version. I got stuck on NDR test keys at the weekend and used this tool to roll-back and update.
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
You can always relock your bootloader and remove root once you've finished.
As far as I remember, if you will follow the "debranding" manual, at the end you will have bootloader locked.
The debranding method does not root the phone, so no need to "un-root" afterwards.
In my opinion, that is the easiest and cleanest way to restore the phone to a clean genuine software
What Newkeebrown suggested is to rebrand the phone to P9 China which will allow you to install Android 8.0 (Oreo).
Unfortunately, at this moment, I can't confirm whether it is a good idea as I am quite too busy to test this method (it would involve of course backup and restore which takes around half a day for me)
Kinda suggesting rebranding to L09C432 because there's more support on here for that version. But yes, definitely gives you the option to jump up to Oreo if you wish. I'm lucky, no backing up for me as all I need is my contacts, synced to Google. I always start fresh after flashing
Hello,
Is there a way to roll back to Oreo from 47.2.a.4.45 (Pie) saving all personal data and apps untouched?
SonyVLT25ISonyVLT25I said:
Hello,
Is there a way to roll back to Oreo from 47.2.a.4.45 (Pie) saving all personal data and apps untouched?
Click to expand...
Click to collapse
Just downgrade it yourself, you won't damage the phone or change your warranty status.
Look on Xperiafirm and find a 47.1.A.16.20 build that is for your region, although any EU region would be fine, US versions have fingerprint and VoLTE disabled for some reason.
Download Newflasher and put it in the same folder as the firmware you downloaded from Xperiafirm
Delete Userdataxxx.sin and files ending in .ta . This will ensure that you don't lose any personal data. Also delete persist*.sin to avoid losing android attest key.
Then start newflasher.exe and follow instrctions.
You might need a copy of the Sony driver
I would make a backup with Xperia transfer before you do anything, if the phone is glitchty after your rebuild, then factory reset it and then restore from the backup.
Didgesteve said:
Just downgrade it yourself, you won't damage the phone or change your warranty status.
Look on Xperiafirm and find a 47.1.A.16.20 build that is for your region, although any EU region would be fine, US versions have fingerprint and VoLTE disabled for some reason.
Download Newflasher and put it in the same folder as the firmware you downloaded from Xperiafirm
Delete Userdataxxx.sin and files ending in .ta . This will ensure that you don't lose any personal data. Also delete persist*.sin to avoid losing android attest key.
Then start newflasher.exe and follow instrctions.
You might need a copy of the Sony driver
I would make a backup with Xperia transfer before you do anything, if the phone is glitchty after your rebuild, then factory reset it and then restore from the backup.
Click to expand...
Click to collapse
Sorry if I'm being too annoying and big thanks for helping me out.
Just to confirm once more. To insure that a personal data, installed apps and apps' data/cache remains intact after rolling back to Oreo from Pie I need to delete these files prior to flashing old firmware:
All files with ".ta" extention
Userdata.sin
Appslog.sin
Diag.sin
Qnovo.sin
Ssd.sin
Persist.sin (especially this one to keep SOMC FIDO Key & SOMC Attest key )
Is it correct, or I missed something?
Didgesteve said:
I would make a backup with Xperia transfer before you do anything, if the phone is glitchty after your rebuild, then factory reset it and then restore from the backup.
Click to expand...
Click to collapse
Too bad I'm unable to start any in-phone app (except settings) right now, as the desktop is stuck on "Phone is starting...", probably because of Substratum themes (like you've answered in other post).
Also when I am connecting the phone to PC and starting Companion, it says that my phone is locked and I need to unlock it with password or fingerprint, but the thing is it is unlocked... I have tried to disable the password through settings, but upon password confirmation I cannot get to the next screen, there is no transition...
SonyVLT25ISonyVLT25I said:
Sorry if I'm being too annoying and big thanks for helping me out.
Just to confirm once more. To insure that a personal data, installed apps and apps' data/cache remains intact after rolling back to Oreo from Pie I need to delete these files prior to flashing old firmware:
All files with ".ta" extention
Userdata.sin
Appslog.sin
Diag.sin
Qnovo.sin
Ssd.sin
Persist.sin (especially this one to keep SOMC FIDO Key & SOMC Attest key )
Is it correct, or I missed something?
Click to expand...
Click to collapse
I'll be honest when I used Newflasher I didn't bother with any of the .ta files, just Userdataxxx.sin and Persist.sin, I don't knon what the .ta files do and it didn't make any difference to me, I got prefect flash, no loss of data. I copied the .ta files instructions from someone else, I can't find the original thread now, but I don't think you delete all of them, espesially not the one in the boot folder.
Is there a way to backup all data with other software other than Companion?
Didgesteve said:
I'll be honest when I used Newflasher I didn't bother with any of the .ta files, just Userdataxxx.sin and Persist.sin, I don't knon what the .ta files do and it didn't make any difference to me, I got prefect flash, no loss of data. I copied the .ta files instructions from someone else, I can't find the original thread now, but I don't think you delete all of them, espesially not the one in the boot folder.
Click to expand...
Click to collapse
So no need to delete "Appslog.sin", "Diag.sin", "Qnovo.sin", "Ssd.sin"? Just delete "Userdata.sin" and "Persist.sin" and all ".ta" files from Root directory?
SonyVLT25ISonyVLT25I said:
So no need to delete "Appslog.sin", "Diag.sin", "Qnovo.sin", "Ssd.sin"? Just delete "Userdata.sin" and "Persist.sin" and all ".ta" files from Root directory?
Click to expand...
Click to collapse
Yes, that will get you downgraded without losing your data
Didgesteve said:
Yes, that will get you downgraded without losing your data
Click to expand...
Click to collapse
Flash complete. Now my phone reloading after Maintenance sign (the one with a screwdriver), nothing else happens :crying::crying::crying:
SonyVLT25ISonyVLT25I said:
Flash complete. Now my phone reloading after Maintenance sign (the one with a screwdriver), nothing else happens :crying::crying::crying:
Click to expand...
Click to collapse
Try reflash, but take out nothing but the two .sin files, ignore the .ta files. That worked for me.
Took out from firmware root directory files: "persist_X-FLASH-ALL-C93B.sin" and "userdata_X-FLASH-CUST-C93B.sin" and flashed once more. Same thing.
Firmware folder with Newflash looks like on the screenshot in the attach
So I have flashed back to Pie 9 again, my phone started up, I'm again stuck at "Phone is starting..." screen and Companion says that my phone is locked.
SonyVLT25ISonyVLT25I said:
Took out from firmware root directory files: "persist_X-FLASH-ALL-C93B.sin" and "userdata_X-FLASH-CUST-C93B.sin" and flashed once more. Same thing.
Firmware folder with Newflash looks like on the screenshot in the attach
Click to expand...
Click to collapse
Did you do a backup with Xpria Transfer?
Try and download the firmware again perhaps the original download was corrupted. Also, try to flash without taking out Userdata, perhaps there is something that is not backwards compatable. Although I'm sure there would have been reports on the forum if that was the case
Then restore with X Transfer.
If all else fails use Xperia companion to repair your phone.
Didgesteve said:
Did you do a backup with Xpria Transfer?
Try and download the firmware again perhaps the original download was corrupted. Also, try to flash without taking out Userdata, perhaps there is something that is not backwards compatable. Although I'm sure there would have been reports on the forum if that was the case
Then restore with X Transfer.
If all else fails use Xperia companion to repair your phone.
Click to expand...
Click to collapse
Unable to use Xperia Transfer, as the phone is stuck on "Phon is starting...", unable to get to apps. Even after pushing alternative Launcher through ADB.
Unable to fix through Xperia companion, as it says that my device is locked and I need to use a fingerprint, while it is unlocked. :crying::crying::crying:
SonyVLT25ISonyVLT25I said:
Unable to use Xperia Transfer, as the phone is stuck on "Phon is starting...", unable to get to apps. Even after pushing alternative Launcher through ADB.
Unable to fix through Xperia companion, as it says that my device is locked and I need to use a fingerprint, while it is unlocked. :crying::crying::crying:
Click to expand...
Click to collapse
You have to make the Xperia transfer backup at the begining before you start, it's too late now.
I'd say the only thing you can try is to flash again and wipe the phone. Don't delete Userdata and let the phone factory reset.
I think it would be plausible to assume that going back to previous version would need a factory reset as there could be a vulnerability in an older fw that could let people gain control and access the data without a proper password (or something).
Also j4nn mentions the necessity of flashing userdata when downgrading to a firmware where gaining temp root is possible on the TA backup thread.
If I root this device to use titanium backup and root for apps like gsm battery - if i were to upgrade using samsung services, would this undo my root or lock my phone from future updates in some way?
Is it advised against updating if one were to root in the future?
Lastly why can't I call record?
zetsui said:
If I root this device to use titanium backup and root for apps like gsm battery - if i were to upgrade using samsung services, would this undo my root or lock my phone from future updates in some way?
Is it advised against updating if one were to root in the future?
Lastly why can't I call record?
Click to expand...
Click to collapse
I will try to answer....
First, IF you Root, one is Not able to do the OTA updates! ( Meaning, you will not be able to update the phone from within the devise)
Second one- The Hard Q to address - Only due to the fact that Everyone is Different. Everyone uses their phone differently. Plus, add in the fact that Samsung has stated, that the S20 FE will receive regular security updates and a few OS updates as well!! (When Purchased in January I has Android 10. A couple of weeks later, it was February, Samsung updated to Android 11. (Knowing later this year, if not next, we will be on Android 12, says something, about the devise!))
Now all that said, knowing XDA People, in time, we should be able to have Our beloved Root, as well as, Updates that come from Google and Samsung.....
I had to check my phone (recent update, things have changed a bit...) in my case, I no longer have call recording (stock) on the phone! It has disappeared!!!
if you don't mind downloading and manually flashing the latest update via Odin, keeping root would mean taking the boot.img (I think) from the tar file and patching it via magisk and then putting it back into the tar file and flashing the whole thing.
3mel said:
if you don't mind downloading and manually flashing the latest update via Odin, keeping root would mean taking the boot.img (I think) from the tar file and patching it via magisk and then putting it back into the tar file and flashing the whole thing.
Click to expand...
Click to collapse
so the stock updated rom is available here? on this sub foruM? i'm fine with that for now. as long as i can keep my seetings and not hav et o resetup everything
zetsui said:
so the stock updated rom is available here? on this sub foruM? i'm fine with that for now. as long as i can keep my seetings and not hav et o resetup everything
Click to expand...
Click to collapse
not available from here yet, you'd have to download the firmware from one of the Samsung firmware sites / apps. don't quote me on these names, Samfirm, Sammobile and Frija. and again don't quote me, do your own searches here to confirm but if you use the HOME_CSC file instead of the regional one your data won't be wiped.
you'd lose root if you didn't also patch the boot.img file and copy that back to tar archive.
3mel said:
not available from here yet, you'd have to download the firmware from one of the Samsung firmware sites / apps. don't quote me on these names, Samfirm, Sammobile and Frija. and again don't quote me, do your own searches here to confirm but if you use the HOME_CSC file instead of the regional one your data won't be wiped.
you'd lose root if you didn't also patch the boot.img file and copy that back to tar archive.
Click to expand...
Click to collapse
you're confusing me now. so what's the order if I do want to update and keep root?
Root->magisk patch after its released for current upgrade (any eta on time after samsung releases)->upgrade?
my last Samsung was fully custom rom and I only ever flashed radio and bootloader, I got those from links in forums. I think firmware is pretty quick in being made available on these sites / apps but I've not used them myself.
so imagine your phone is already rooted (that first initial root is more involved as there's a data partition wipe), new firmware comes out.
* download that firmware
* open the archive tar of that firmware and copy boot.img file to your phone (I've only read this once so confirm I have the correct file name).
* from your phone install magisk v22
* open magisk and options for direct install will lead you to patching the boot.img
* when that's done, move the patched file back to your computer and replace the original version with the patched one. it might be handy to keep a copy of the unpatched file safe in case you need it one day.
* from your computer flash the contents of that tar archive, you'll need to read a proper guide for this, the correct files need to be assigned to the correct partitions in Odin (the flash app for Samsung) and the names aren't all obvious. also you need drivers for Odin too, and a good version that works for this phone.
* one of those files that needs to assigned is called the CSC file, that deals with the region your phone is going to be (put simply). if you use your phones correct CSC file for the region of firmware you downloaded the data partition will be wiped.
to avoid that you can use the HOME_CSC file and data will not be wiped. on your initial first root you will have to wipe though to make sure your storage is not encrypted.
* you really want to follow guides for everything you're doing for the first time, don't rely on previous experience. Samsung phones are different to Pixels etc. some guides are written as if you'll know half this stuff already, if you don't it doesn't hurt to ask someone.
lol, I haven't actually rooted my own phone yet. I'm waiting to borrow a laptop plus seeing how things develop with TWRP / mods / new procedures.