Okay, so here's the deal.
I have an AT&T HTC One that was running 4.4 Kit Kat (Click: this ROM) and is S-OFF via RumRunner. I am running the latest TWRP recovery.
Yesterday I got prompted for an OTA and accepted it (in the past, with GPE ROMs, it would just reboot to recovery and do nothing). This is the only way I know of to get rid of the annoying "System update available" notification. I figured it wouldn't do anything and I would simply reboot and be good for a few more days until it prompted again. Low and behold, it actually updated my phone to 4.4.2.
Now, I'm having some issues.
I was a user of DashClock Widget...but now I use Better DashClock. However, this app is now prompting me to download a key. When I try to download the key from the Play Store, I get the message:
Error: Couldn't install on USB storage or SD Card.
SwiftKey Keyboard has the same issue.
Other apps (such as ES File Explorer, ESPN, Fandango, etc. update just fine).
-------------
I have read a bunch of posts that suggest cleaning up temp files (which don't exist on my phone) and to download SELinux Mode Changer and change the mode to Passive...but to no avail.
Can someone help me? Is this the developers issue or did my phone do something wonky?
Thanks!
Exactly the same problem here. I've narrowed it down to paid apps that won't install. Followed the same possible solutions in the 1st post, nothing works. HTC One GE 4.4.2.
IlyaKol said:
Okay, so here's the deal.
I have an AT&T HTC One that was running 4.4 Kit Kat (Click: this ROM) and is S-OFF via RumRunner.
Yesterday I got prompted for an OTA and accepted it (in the past, with GPE ROMs, it would just reboot to recovery and do nothing). This is the only way I know of to get rid of the annoying "System update available" notification. I figured it wouldn't do anything and I would simply reboot and be good for a few more days until it prompted again. Low and behold, it actually updated my phone to 4.4.2.
Now, I'm having some issues.
I was a user of DashClock Widget...but now I use Better DashClock. However, this app is now prompting me to download a key. When I try to download the key from the Play Store, I get the message:
Error: Couldn't install on USB storage or SD Card.
SwiftKey Keyboard has the same issue.
Other apps (such as ES File Explorer, ESPN, Fandango, etc. update just fine).
-------------
I have read a bunch of posts that suggest cleaning up temp files (which don't exist on my phone) and to download SELinux Mode Changer and change the mode to Passive...but to no avail.
Can someone help me? Is this the developers issue or did my phone do something wonky?
Thanks!
Click to expand...
Click to collapse
I had a similar problem. I downloaded the 4.4.2 OTA update and tried flashing it with TWRP three different times. All three times I got that same error message with some apps. It was extremely frustrating. I ended up flashing the stock 4.4 recovery and then flashing the update. It worked perfectly and the problem went away. I then reflashed TWRP.
arfon said:
Exactly the same problem here. I've narrowed it down to paid apps that won't install. Followed the same possible solutions in the 1st post, nothing works. HTC One GE 4.4.2.
Click to expand...
Click to collapse
I had a similar experience. Paid apps would not install from Play Store. Amazon app store or F-Droid apps would install.
But my journey was that I had a 4.4 GPE device suffering through an issue where I can't get my bootloader to unlock. So when 4.4.2 came out I wasn't getting the OTA so I tried flashing just the firmware package from the OTA download. That's when I was getting this error (after a factory reset).
But then next day I got the real OTA and after that the problem went away. So for me it was a firmware issue in that it wasn't the right firmware for my OS.
Weird that you are running 4.4.2 but having this issue. Any chance you didn't come to have 4.4.2 the "natural" way?
msw141 said:
I had a similar experience. Paid apps would not install from Play Store. Amazon app store or F-Droid apps would install.
But my journey was that I had a 4.4 GPE device suffering through an issue where I can't get my bootloader to unlock. So when 4.4.2 came out I wasn't getting the OTA so I tried flashing just the firmware package from the OTA download. That's when I was getting this error (after a factory reset).
But then next day I got the real OTA and after that the problem went away. So for me it was a firmware issue in that it wasn't the right firmware for my OS.
Weird that you are running 4.4.2 but having this issue. Any chance you didn't come to have 4.4.2 the "natural" way?
Click to expand...
Click to collapse
Update was OTA last night, so I guess its as natural as it comes.
arfon said:
Update was OTA last night, so I guess its as natural as it comes.
Click to expand...
Click to collapse
Yeah...my process was as natural as possible.
I was on 4.3 at first...so when I was going to 4.4 KitKat I first flashed back to some basic stock Sense ROM to run RumRunner and attain S-OFF. Then I COMPLETELY NUKED my phone and went to 4.4 KitKat. Had no problems, got the OTA, and now this.
It's aggravating, that's for sure.
I really don't want to completely wipe my phone again and have to re-setup all of my home screens, etc.
I received the OTA which installed despite me having TWRP, not stock recovery (as per http://forum.xda-developers.com/showpost.php?p=48586329). Now I have the same issue installing paid apps (the ones I had already installed before the OTA disappeared off the device).
Short of starting from scratch, I'm at a bit of a loss for a solution...
Nick
Sounds like this is wide-spread...or at least amongst the people who are running newer GPE ROMs on their Ones.
im having the exact same issues here
artmunkie said:
I had a similar problem. I downloaded the 4.4.2 OTA update and tried flashing it with TWRP three different times. All three times I got that same error message with some apps. It was extremely frustrating. I ended up flashing the stock 4.4 recovery and then flashing the update. It worked perfectly and the problem went away. I then reflashed TWRP.
Click to expand...
Click to collapse
Can you point me to where you got the stock recovery from please?
Fixed
It looks like this is all to do with custom recovery and OTA updates. I have TWRP installed. This morning I flashed stock recovery. I then put the OTA update file on the phone storage. Then booted into the stock recovery (which is the first time I've seen it, it would be nice if it was the last as it's tricky to get into), then flashed the 4.2.2. update from there. Once I booted the phone again all my paid apps reappeared. No data lost in the process. I'm not sure if going back to TWRP not will cause the problem again, so for now I'll stick with stock recovery....
arfon said:
It looks like this is all to do with custom recovery and OTA updates. I have TWRP installed. This morning I flashed stock recovery. I then put the OTA update file on the phone storage. Then booted into the stock recovery (which is the first time I've seen it, it would be nice if it was the last as it's tricky to get into), then flashed the 4.2.2. update from there. Once I booted the phone again all my paid apps reappeared. No data lost in the process. I'm not sure if going back to TWRP not will cause the problem again, so for now I'll stick with stock recovery....
Click to expand...
Click to collapse
Can you please detail the procedure ?
If possible including where you got the files (OTA and stock recovery ) and how to put OTA on the sdcard to "provoque" que update.
Thanks in advance!
franciscols said:
Can you please detail the procedure ?
If possible including where you got the files (OTA and stock recovery ) and how to put OTA on the sdcard to "provoque" que update.
Thanks in advance!
Click to expand...
Click to collapse
This.
Also, you left 4.4.2 on the device and just 're-applied' the OTA update? Or did you go back to a NANDROID backup of you on 4.4 or 4.3?
arfon said:
Can you point me to where you got the stock recovery from please?
Click to expand...
Click to collapse
Here you go! I can't remember the thread where I found it, so the file is attached. Just to be clear, this is the stock Android 4.4 recovery for the HTC One GPE.
artmunkie said:
Here you go! I can't remember the thread where I found it, so the file is attached. Just to be clear, this is the stock Android 4.4 recovery for the HTC One GPE.
Click to expand...
Click to collapse
So I flash this recovery and then flash the OTA update (this one?) and I should be good?
IlyaKol said:
So I flash this recovery and then flash the OTA update (this one?) and I should be good?
Click to expand...
Click to collapse
Yeah, that's about it. I used adb to flash the stock recovery to replace TWRP, then used the stock recovery to flash the same update you linked to. After it was done updating I reflashed TWRP. And don't forget to make a nandroid.
Thank you! Will report back when I'm done!
What is the fastboot command to flash the OTA zip file?
I'm back on the stock recovery...phone is still booting/working so I just need to do the OTA part now.
IlyaKol said:
What is the fastboot command to flash the OTA zip file?
I'm back on the stock recovery...phone is still booting/working so I just need to do the OTA part now.
Click to expand...
Click to collapse
Sorry, hectic day at work. I should have said that I applied the update with the stock recovery. Not fastboot.
I basically used the guide linked below to flash the update.
Read Step 2
http://www.androidpolice.com/2012/1...e-nexus-7-now-manual-download-link-available/
artmunkie said:
Sorry, hectic day at work. I should have said that I applied the update with the stock recovery. Not fastboot.
I basically used the guide linked below to flash the update.
Read Step 2
http://www.androidpolice.com/2012/1...e-nexus-7-now-manual-download-link-available/
Click to expand...
Click to collapse
What if you don't have an "apply from adb" option?
I have:
- reboot system now
- apply from sd card
- apply from phone storage
- apply from cache
- wipe data/factory reset
- wipe cache partition
Can't I just open a ADB shell while on the fastboot USB option?
Hi everyone, it's been a while since I started thinking to root my Moto G 2 but I still want to run on stock kernel & ROM. We are still waiting for the update to Android 5.1 and I was wondering if I could get the OTA safely with a rooted device. If not, I would wait for the official update and after this I'm going to root it; otherwise I would root it now. Thanks in advance.
I think you should wait for the OTA update and root after the update.
You won't receive any OTA updates from Motorola if you have flashed custom recovery and rooted your device
Copy that, thank you guys.
Nahuwii said:
You won't receive any OTA updates from Motorola if you have flashed custom recovery and rooted your device
Click to expand...
Click to collapse
If I understood it right, @luke! wants to run stock rom after rooting. So there is absolutely no problem to boot into TWRP 2.8.5.0, make a nandroid backup and flash latest superSU from there. OTA just cares about custom recovery and changes in system. So when an OTA arrives just restore your nandroid backup or revert the changes you made like unfreezing systemapps, uninstalling things like adaway and there will be no problem to install OTA.
Even if you flash twrp instead of booting into it,you can easily flash back the custom recovery. As long you stay stock this is all an easy thing. And also after flashing a custom rom there are ways to get back to the original firmware. @luke!:If you need any help pm me.
Wolfcity said:
If I understood it right, @luke! wants to run stock rom after rooting. So there is absolutely no problem to boot into TWRP 2.8.5.0, make a nandroid backup and flash latest superSU from there. OTA just cares about custom recovery and changes in system. So when an OTA arrives just restore your nandroid backup or revert the changes you made like unfreezing systemapps, uninstalling things like adaway and there will be no problem to install OTA.
Even if you flash twrp instead of booting into it,you can easily flash back the custom recovery. As long you stay stock this is all an easy thing. And also after flashing a custom rom there are ways to get back to the original firmware. @luke!:If you need any help pm me.
Click to expand...
Click to collapse
Great! Thank you, very appreciated If I have some problems, I will pm you. Thanks in advance
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
After an attempt to upgrade to Lollipop, the phone froze after software installation when it rebooted.
I was able to restore the phone from a cwm backup file to 4.4.3 and at the moment everything is working great except I cannot update to Lollipop now.
I get this error message:
Package expects build fingerprint of htc/brightstarus_wwe/m:4.4.3/KTU84L/356475.2:usr/release-keys; or
htc/brightstarus_wwe/m7:5.0.2/LRX22G/468180.7:usr/release-keys
this device has htc/brightstarus_wwe/m7:5.0.2/LRX22G/468180.21:usr/release-keys
Here is the phone history of the update attempts:
Device is HTC One M7 WWE Developer Edition 2Gb / 64GB
Device is unlocked and rooted
Device had Android 4.4.3
I flashed the stock recovery to the phone then attempted to install the Lollipop update.
Half way through the installation the operation crashed and phone was in-operatable.
I was able to restore the phone to 4.4.3 from clockworkmod recovery backup.
At this point the phone was working, but slowly.
Everything in the About / Software indicated that the software was 4.4.3 / 6.07.1540.2
However the OS from Hboot screen indicated 7.17.1540.2
Left the phone as is for a long time as it was usable, then had a problem with my SMS application, ultimately I did a factory reset and everything fixed, phone working good.
So now I reflashed the stock recovery again (7.17.1540.7) and tried to install the lollipop update again. It worked this time. 7.17.1540.2 working.
I then got the notice that there was another update (7.17.1520.21) so I tried to install this update.
After the install the phone re-booted and it froze at the HTC / Android screen; I left it for one hour and it did not come to life.
After a reboot the phone would come to this screen then go blank and nothing.
I attempted to re install from clockworkmod recovery restore but it would not work this time.
Had several Lollipop backup files - none worked - thought it was dead.
After some time I did get one to restore but none of the lollipop versions restored worked; I had an older file with 4.4.3 which worked. Phone is now back to 4.4.3
OK now with stock recovery flashed again (7.17.1540.7) I tried the update again to lollipop, but a short ways into the install the operation aborts creating error message as above.
So everything in the About / Software indicates it is 4.4.3 /6.07.1540.2
However the Hboot screen is showing OS 7.17.1540.21 now. Obviously from the last upgrade attempt.
It was a similar situation the first time I was successful installing the lollipop upgrade; the phone indicated that it had version 4.4.3 /6.07.1540.2 but the Hboot OS indicated it had OS 7.17.1540.2 (from the crashed update attempt I guess)
So could someone advise on best coarse of action to try and update this software now to Lollipop?
Could I re-flash something like the kitkat version of boot image? Would this correct the OS version reported by HBoot?
Other options I have found would be to install the RUU factory file:
RUU_M7_UL_L50_SENSE60_MR_BrightstarUS_WWE_7.17.1540.51.exe
But I'm concerned that if this fails due to operating system modifactions the phone may brick, as warned at the site.
Also I have found a TRWP backup file from lollipop upgrade which I could install TRWP recovery and attempt a restore from this file?
Any suggestions?
Just use the RUU, you CANNOT OTA to Lollipop+ if you have rooted the phone without RUUing back to total stock..
Reggi747 said:
So everything in the About / Software indicates it is 4.4.3 /6.07.1540.2
However the Hboot screen is showing OS 7.17.1540.21 now. Obviously from the last upgrade attempt.
Click to expand...
Click to collapse
You must understand here that these 2 numbers are indicating 2 different things. The number you'll find in About/Software is the software version (your rom version). The number you'll find when booted in hboot is the firmware version. In order to install ota updates, everything must be 100% stock and the firmware installed must match the software version (because the firmware is also updated during an ota).
RUU_M7_UL_L50_SENSE60_MR_BrightstarUS_WWE_7.17.1540.51.exe
But I'm concerned that if this fails due to operating system modifactions the phone may brick, as warned at the site.
Click to expand...
Click to collapse
Flashing this file is the best solution, doesn't matters if your system is modified, it will revert everything back to stock and you'll be on the latest version.