HTC One - Couldn't Install on USB Storage or SD Card - One (M7) Q&A, Help & Troubleshooting

Hi there!
I received my HTC One two days ago and I am unable to install any PAID apps on the phone. I am able to install free apps without an issue though.
I have searched all over the internet and found two possible solutions, which don't work. These solutions were:
Unmount the SD card. Install app, remount the SD card. This won't work as the HTC One does not have an SD card
In the secure/asec folder, find and delete "smdl2tmp1.asec". Although I found the folder, it was empty and therefore I was unable to delete the file.
I have also completely wiped my phone twice already. I checked the Kernel and Firmware version and it's all up to date. Below are screenshots of the device info.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Finally, I also realized, only after I paid for the device, it's a Dev device. I don't know if this makes any difference though.
The bootloader is unlocked and the device has been rooted. I have full access over the file system.

Make a nandroid and flash another rom to see if that fixes it.

You're using an old custom ROM! Flash any new ROM of your choice from the dev section and it should fix the problem. The issue is within the kernel.
StephanBotha said:
Hi there!
I received my HTC One two days ago and I am unable to install any PAID apps on the phone. I am able to install free apps without an issue though.
I have searched all over the internet and found two possible solutions, which don't work. These solutions were:
Unmount the SD card. Install app, remount the SD card. This won't work as the HTC One does not have an SD card
In the secure/asec folder, find and delete "smdl2tmp1.asec". Although I found the folder, it was empty and therefore I was unable to delete the file.
I have also completely wiped my phone twice already. I checked the Kernel and Firmware version and it's all up to date. Below are screenshots of the device info.
Finally, I also realized, only after I paid for the device, it's a Dev device. I don't know if this makes any difference though.
The bootloader is unlocked and the device has been rooted. I have full access over the file system.
Click to expand...
Click to collapse

Hi,
I'm having a similar problem to the OP. I have a GPE HTC One which is rooted and S-Off. I just updated the software from 4.4 to 4.4.2, at which point the inability to update or install paid apps appeared. As in the original post, I can't find the smdl2tmp1.asec. In fact, my entire mnt/secure folder is empty, as is mnt/asec. I also don't have a .android_secure folder, as has been mentioned in other posts. If I restore to a previous backup running 4.4, everything works fine. The issue is only with installs or updates from the Play Store, because I am able to install the apps from my Titanium backups just fine, but when I do, I get the same error message when I try to update them.
Thanks

roman1984 said:
Hi,
I'm having a similar problem to the OP. I have a GPE HTC One which is rooted and S-Off. I just updated the software from 4.4 to 4.4.2, at which point the inability to update or install paid apps appeared. As in the original post, I can't find the smdl2tmp1.asec. In fact, my entire mnt/secure folder is empty, as is mnt/asec. I also don't have a .android_secure folder, as has been mentioned in other posts. If I restore to a previous backup running 4.4, everything works fine. The issue is only with installs or updates from the Play Store, because I am able to install the apps from my Titanium backups just fine, but when I do, I get the same error message when I try to update them.
Thanks
Click to expand...
Click to collapse
Hi,
I have this exact same issue. Nothing in secure folder etc. From 4.4 to 4.4.2 via OTA.

roman1984 said:
Hi,
I'm having a similar problem to the OP. I have a GPE HTC One which is rooted and S-Off. I just updated the software from 4.4 to 4.4.2, at which point the inability to update or install paid apps appeared. As in the original post, I can't find the smdl2tmp1.asec. In fact, my entire mnt/secure folder is empty, as is mnt/asec. I also don't have a .android_secure folder, as has been mentioned in other posts. If I restore to a previous backup running 4.4, everything works fine. The issue is only with installs or updates from the Play Store, because I am able to install the apps from my Titanium backups just fine, but when I do, I get the same error message when I try to update them.
Thanks
Click to expand...
Click to collapse
The only fix for this is to install Android Revolution ROM. At least, that's the only way I could fix mine :crying:

You should always use stock recovery for OTA updates. This problem is probably due to applying the OTA with a custom recovery.

BenPope said:
You should always use stock recovery for OTA updates. This problem is probably due to applying the OTA with a custom recovery.
Click to expand...
Click to collapse
That's unfortunate, since I like twrp. To reinstall stock recovery, do I just flash the image like I did with twrp?

Yes. You can put TWRP back on after the OTA is on.

BenPope said:
Yes. You can put TWRP back on after the OTA is on.
Click to expand...
Click to collapse
Thanks, that did the trick. Going back and forth between recoveries like that is a little annoying, but fortunately it's relatively quick, so it's not horrible.

roman1984 said:
Thanks, that did the trick. Going back and forth between recoveries like that is a little annoying, but fortunately it's relatively quick, so it's not horrible.
Click to expand...
Click to collapse
Did you have to go back to TWRP and reinstall the GPe ROM? Or did you just have to flash TWRP and it started working again?

DyingBlade said:
Did you have to go back to TWRP and reinstall the GPe ROM? Or did you just have to flash TWRP and it started working again?
Click to expand...
Click to collapse
Once I was able to update using the stock recovery, all I had to do was flash TWRP and everything worked fine (no need to reinstall the GPE ROM since that was already running).

Related

Best strategy to keep One updated and rooted?

What would be in your idea (your suggestions) for keeping HTC One M7 updated with the latest OTAs? while keeping it rooted?
I do not change ROMs or else. I just require root to be able to run some apps (e.g. droidwall). I like to keep my phone updated regularly with the OTA updates. What would be the best strategy to do so?
for example:
a) getting a stock recovery for the phone.
unlocking bootloader, custom recovery, rooting, (s-on).
then whenever an OTA is announced, backing up phone with adb,
flashing with stock recovery,
updating OTA
restore app and data backup
b) unlocking bootloader, custom recovery, rooting, (s-on).
then whenever an OTA is announced, waiting for some time, so that OTA will be available for download as zip file from forums.
when the OTA zip file is available for download, back up phone with adb,
Install update from OTA file (how?)
restore app and data backup
c) ??
Please let us know what you think. what are your solutions. if a or b are feasible? how? any better strategy?
geek654 said:
What would be in your idea (your suggestions) for keeping HTC One M7 updated with the latest OTAs? while keeping it rooted?
I do not change ROMs or else. I just require root to be able to run some apps (e.g. droidwall). I like to keep my phone updated regularly with the OTA updates. What would be the best strategy to do so?
for example:
a) getting a stock recovery for the phone.
unlocking bootloader, custom recovery, rooting, (s-on).
then whenever an OTA is announced, backing up phone with adb,
flashing with stock recovery,
updating OTA
restore app and data backup
b) unlocking bootloader, custom recovery, rooting, (s-on).
then whenever an OTA is announced, waiting for some time, so that OTA will be available for download as zip file from forums.
when the OTA zip file is available for download, back up phone with adb,
Install update from OTA file (how?)
restore app and data backup
c) ??
Please let us know what you think. what are your solutions. if a or b are feasible? how? any better strategy?
Click to expand...
Click to collapse
Best strategy is to ignore carrier updates completely
your at XDA we have releases sometimes months before the carrier gets around to it. Just pick a custom rom you like and follow it. MaximusHD / ARHD / Insertcoin / ViperOne are always far ahead of any OTA package and already rooted / with numerous tweaks
migrating to custom ROM
clsA said:
Best strategy is to ignore carrier updates completely
your at XDA we have releases sometimes months before the carrier gets around to it. Just pick a custom rom you like and follow it. MaximusHD / ARHD / Insertcoin / ViperOne are always far ahead of any OTA package and already rooted / with numerous tweaks
Click to expand...
Click to collapse
My previous android was not very popular so there was very few ROMs for it. and all of them had silly problems with camera, screen etc. I guess you can say I had bad experience with custom ROMs.
So these custom ROMs you mentioned, would have all of the original apps and functions as well (not bloatapp of course, but apps like HTC Sense, and blink feed option, zoe camera, and animated photos. etc) ?
CanI backup my apps and data from current stock rom, and after flashing a custom ROM I restore them there? or it won't work?
What I should use to back up? adb backup command from usb debugging mode, or titanium backup app?
what are the most popular custom ROMS most affine to stock ROM and most stable (I know it is subjective, just asking to know your opinions).
thanks
geek654 said:
My previous android was not very popular so there was very few ROMs for it. and all of them had silly problems with camera, screen etc. I guess you can say I had bad experience with custom ROMs.
So these custom ROMs you mentioned, would have all of the original apps and functions as well (not bloatapp of course, but apps like HTC Sense, and blink feed option, zoe camera, and animated photos. etc) ?
CanI backup my apps and data from current stock rom, and after flashing a custom ROM I restore them there? or it won't work?
What I should use to back up? adb backup command from usb debugging mode, or titanium backup app?
what are the most popular custom ROMS most affine to stock ROM and most stable (I know it is subjective, just asking to know your opinions).
thanks
Click to expand...
Click to collapse
my backup strategy when using custom roms is
copy sdcard to PC (everything)
I use HTC Backup ..it saves my contacts / messages / app settings and folder / desktop layout.
The roms I listed above are the only ones I use, their all mostly stock, Sense based roms
clsA said:
my backup strategy when using custom roms is
copy sdcard to PC (everything)
I use HTC Backup ..it saves my contacts / messages / app settings and folder / desktop layout.
The roms I listed above are the only ones I use, their all mostly stock, Sense based roms
Click to expand...
Click to collapse
Do you mean the app "HTC backup for HTC One" ?
trying to install it from market it says "installed", but there is no "open" option?!! just uninstall
how can I open this app and make a backup by it?
geek654 said:
Do you mean the app "HTC backup for HTC One" ?
trying to install it from market it says "installed", but there is no "open" option?!! just uninstall
how can I open this app and make a backup by it?
Click to expand...
Click to collapse
Settings-> Back up & rest-> Click on the google(see the picture)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my HTC One using Tapatalk

[4.4.4][XT1039][OFFICIAL][TWRP/CWM] Stock Moto G 4G 21.1.46.en.EU

Stock with unlocked bootloader warning removed
Motorola 4G 4.4.4 Kitkat for EUROPE/AUSTRALIA aka XT1039
This is for unlocked bootloader only
Update brings:​
Android 4.4.4 Kitkat
SD Card Fixes
Instructions:
FLASH CWM
WIPE DATA/FACTORY RESET
FLASH ROM
FLASH Super SU (if you want to root)
WIPE DALVIK.
ENJOY!
Only tested with CWM
Dowload:​
Mega
Google Drive
If you want another filehost just ask and if the zip does not work tell me we will look into it :highfive:​
OMG!!!
About root procedure... Did anyone know about it?
Flash this Super SU
Ps: Is my update working ?
I didn't try it yet. I prefer TWRP, so I was going to test if it's working with it. But I just got the XT1039 last week, so I set it up to my liking, then I unlocked bootloader to root it, so second setup, and then I messed up deleting some files (don't really know what happened), so I had to set it up for the 3rd time just yesterday. I'm not in the mood of wiping it again just yet!
But i will
EDIT: Just installed it, with TWRP and wiping only cache. Works like a charm!
I did the update with the file above without any wipe (except cache)
Envoyé de mon XT1039 en utilisant Tapatalk
It works perfectly, thank you!
I was having some trouble updating to 4.4.4 using OTA as I changed a lot in the stock rom. After spending hours reverting changes, I still couldn't get it to work (without flashing stock and starting all over again, which I didn't want to do really).
Was thinking of starting all over again, flashing stock image, OTA to 4.4.4 and changing everything after that, when I came across your thread.
You saved me from spending hours having to start from scratch! Top job!
I only flashed your file from my OTG drive in TWRP , over my heavily changed system, and it works like a dream.
See this screenshot I took right after flashing and reboot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So, yes man, you did it! Thanks again! [emoji106]
Verstuurd vanaf mijn XT1039 met Tapatalk
Nice work Darius.
Also had probs with 4.4.4 OTA due to custom recovery/rooting.
This was easiest way to 4.4.4 happiness....
I want to try this one, but I want to know how can I verify that bootloader is locked or not, and how can I unlock it.
Any threat talking about this?
PD: Could be unlocked from adb typing "fastboot oem unlock"?
Will this work for the XT1039 from Great Britain? Build numbers are the same but instead of EU there is a GB. I bought mine from Amazon and it is the unlocked version.
Awesome!
Hi,
Just installed on my 4.4.3, wiping only the cache partition as you said. As far as I can see everythying works perfectly.
Thank you man !
guijarrelson said:
I want to try this one, but I want to know how can I verify that bootloader is locked or not, and how can I unlock it.
Any threat talking about this?
PD: Could be unlocked from adb typing "fastboot oem unlock"?
Click to expand...
Click to collapse
The bootloader is proprietary so you need to ask Motorola for an unlock code. "Fastboot oem unlock" won't work. There are a lot of threads about this in Q&A and General.
I just finished updating my GB version to this EU version and it worked great! No issues to report. Installed CWM recovery, then EU 4.4.4., wiped cache then installed superuser. Fantastic work with no lost data. My 32GB sdcard works too!!!! AMAZING
I tried using a Sandisk 32 Gb sd card (bought in 2011, and still working perfectly in my old HTC Desire) that didn't work in this phone before the update, but it still doesn't. Have seen other reports about the same issue, so I guess not every sd card problem is solved with the 4.4.4 update.
The card mounts normally, I can see the files on it in any explorer, but it's not possible to read from or write onto the card.
Phone can't format the card, and a check with a Windows pc doesn't show anything wrong with the card.
Strange huh? Any ideas?
I've flashed this and all is working but I can not enable ART can someone else let me know if they can or can't please?
mhisani said:
I've flashed this and all is working but I can not enable ART can someone else let me know if they can or can't please?
Click to expand...
Click to collapse
Do you have xposed framework installed? Art doesnt work with it so...
Second, do you have enough internal memory free?
jkoetsier said:
Do you have xposed framework installed? Art doesnt work with it so...
Second, do you have enough internal memory free?
Click to expand...
Click to collapse
I factory reset the device and still I could not. I flashed the rom via recovery and that seemed to solve it.. perhaps xposed changed something that was not cleared on wipining
mhisani said:
I factory reset the device and still I could not. I flashed the rom via recovery and that seemed to solve it.. perhaps xposed changed something that was not cleared on wipining
Click to expand...
Click to collapse
Factory Reset does not touch your system partition. Only wipes your data.
Xposed would have modified your system partition to prevent ART. Flashing a new rom would restore your system partition to how it was.
Next time, either disable xposed before uninstalling. Or if that doesn't work, either fastboot flash the system.img chunks found in the stock firmware OR flash the same firmware in a custom recovery (if zip available). This will refresh your system partition and restore any changes without affecting your data.
Edit: ignore
Wait so will this work on the XT1045?
I have flashed this ROM and my SD card (Sandisk 16 GB) is still not recognized by the phone. Any advices ?

[Q] ATT Update to 5.0.1 fails, confirming a solution

It has been over a year since I last flashed a S4A phone, so refreshing my notes and hoping someone can confirm the bits below are correct.
In case another, shorter way to accomplish same exists, kindly suggest it.
Background first.
Phone is SG4 Active, running Android 4.4.2. Baseband I537UCUCNH3, model is Samsung SGH I537, Build KOT49H.I537UCUCNH3
Phone is unlocked and was flashed with Odin one year ago to 4.3 and then ATT updated automatically to current version.
Status today.
When ATT offers download and install the 900 plus MB 5.0.1 update, it fails at 27 percent, reboots phone, repeatedly.
Phone has about 8 GB free space on internal memory and about 10 GB on SD card. As far as I can determine, no special mods have been done to phone and I have uninstalled all user installed apps so it has only ATT, Samsung and Google apps.
Proposed solution.
Found the original I537UCUBML2 bundle *2gb* (Android 4.3) with BL,AP,CSC,CP and I think that since Bootloader already installed, it should be possible to run Odin again and just flash AP,CSC and CP.
Once flashed the system will be back to 4.3 and the OTA updates should work, first to 4.4 and later to 5.0.1.
Can not recall right now just how to do the Odin flash but will use search to figure it out but is my thinking correct or am I missing something important ? For example, don't remember if I have to reboot phone first or if Odin handles it all once the USB cable is connected.
Thank you.
xdafly said:
It has been over a year since I last flashed a S4A phone, so refreshing my notes and hoping someone can confirm the bits below are correct.
In case another, shorter way to accomplish same exists, kindly suggest it.
Background first.
Phone is SG4 Active, running Android 4.4.2. Baseband I537UCUCNH3, model is Samsung SGH I537, Build KOT49H.I537UCUCNH3
Phone is unlocked and was flashed with Odin one year ago to 4.3 and then ATT updated automatically to current version.
Status today.
When ATT offers download and install the 900 plus MB 5.0.1 update, it fails at 27 percent, reboots phone, repeatedly.
Phone has about 8 GB free space on internal memory and about 10 GB on SD card. As far as I can determine, no special mods have been done to phone and I have uninstalled all user installed apps so it has only ATT, Samsung and Google apps.
Proposed solution.
Found the original I537UCUBML2 bundle *2gb* (Android 4.3) with BL,AP,CSC,CP and I think that since Bootloader already installed, it should be possible to run Odin again and just flash AP,CSC and CP.
Once flashed the system will be back to 4.3 and the OTA updates should work, first to 4.4 and later to 5.0.1.
Can not recall right now just how to do the Odin flash but will use search to figure it out but is my thinking correct or am I missing something important ? For example, don't remember if I have to reboot phone first or if Odin handles it all once the USB cable is connected.
Thank you.
Click to expand...
Click to collapse
ML2 won't help you. If you give me about 5-10 minutes I'll link you to the file you need (I'm slow because I'm on mobile and it's a tiny screen for my fat fingers lol)
---------- Post added at 02:43 PM ---------- Previous post was at 02:37 PM ----------
OK here is the file you need. Download and save it to your EXTERNAL SD card (internal storage won't work) and flash the file in stock recovery. You can boot to recovery by shutting the phone off, then holding down power and vol+simultaneously
If you want to be rooted, don't do this, I can point you to a different method
Ok, downloading. Now, in case this "manual method" also fails at 27 percent and just reboots with Install failed, what then ? That was the original reason I proposed to use Odin re-flash the SG4A back to some semblance of original state. Thank you.
xdafly said:
Ok, downloading. Now, in case this "manual method" also fails at 27 percent and just reboots with Install failed, what then ? That was the original reason I proposed to use Odin re-flash the SG4A back to some semblance of original state. Thank you.
Click to expand...
Click to collapse
Use Odin to restore NE3 kit kat instead of ML2. I can link to that too if you need
NE3 kit kat
You have to extract all 4 tar files and flash all 4 with Odin simultaneously
xdafly said:
Ok, downloading. Now, in case this "manual method" also fails at 27 percent and just reboots with Install failed, what then ? That was the original reason I proposed to use Odin re-flash the SG4A back to some semblance of original state. Thank you.
Click to expand...
Click to collapse
The reason your install is failing is because you've modified the stock firmware. When you try to install an AT&T update, manually or automatically there is a script in that update that checks all the files on your phone to ensure that they are the original, unmodified files. If any single one of them is not original or modified, then the update will fail as you have experienced. So if you root your phone you are modifying system files. Even if you unroot, the system files were still modified at one point and the update will fail. I suspect you've done something like this.
The only way you can update to stock OC6 (5.0.1) is to flash your phone back to stock firmware and in your case it should be NE3. As has been explained you will need to flash the NE3 Odin package, but beware this will completely wipe your phone so backup anything you don't want to lose. There is a method for updating your phone without flashing back to stock described in this thread. Also, if you're ever looking for information on rooting and updating your phone it would be a good idea to familiarize yourself with the links in the i537 Firmware Guide.
Use Odin to restore NE3 kit kat instead of ML2.
Click to expand...
Click to collapse
Got it. Downloading (as suspected, the update.zip failed) and will hook up cable and run Odin 3.09 with all 4 files
All important data is backed up to Google so unless I lose some ATT settings, such as the IMEI code or similar, all should be well
Does the phone have to be in recovery mode before starting Odin ? Can't remember now and all Youtube videos show only AP being applied, not all 4 files simultaneously.
Edit, read http://www.samsungodindownload.com/odin-tutorial/
Thank you
BL file to bootloader (BL), CP file to phone (CP), CSC file to CSC, like below:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

M7 OTA : OTA_M7_WL_L50_SENSE60_SPCS_MR_Sprint_WWE_6.23.651. 10-6.23.651.7_R_release

Just got the notification for OTA update for m7 .
File name: OTA_M7_WL_L50_SENSE60_SPCS_MR_Sprint_WWE_6.23.651.10-6.23.651.7_R_release_452237.zip
Size: 189.61 mb
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sprint Website
Download link
I rooted my phone yesterday and dont want to go back to stock for the update. Can someone please help me with a flashable zip which I can use.
cheers
tangojoker said:
Just got the notification for OTA update for m7 .
I rooted my phone yesterday and dont want to go back to stock for the update. Can someone please help me with a flashable zip which I can use.
cheers
Click to expand...
Click to collapse
From my understanding, you should be able to take the OTA, but you need to make sure everything is as stock as possible first. Follow these steps:
0. BACKUP with a nandroid backup
1. Uninstall any apps that changed the /system partition (like xposed).
2. Unroot from the SuperSU app.
3. Flash the stock recovery (easiest way is to flash the latest full firmware).
4. If you are s-on, you may have to relock the bootloader first (I'm s-off, so I'm not sure).
5. Take the OTA.
6. If you are s-on, unlock the bootloader if you locked in step 4.
7. Flash TWRP.
8. Allow TWRP to root the phone (it will ask you if you want to root when you exit the recovery).
You can get the full firmware from this thread. If you wait though, someone might release a flashable stock rooted ROM, but the phone is old, so that may not happen.
Won't this wipe everything?
jy04 said:
Won't this wipe everything?
Click to expand...
Click to collapse
I don't believe so. The OTA typically leaves the /data partition alone. Of course, as always, everything you do to your phone is at your own risk.
coal686 said:
From my understanding, you should be able to take the OTA, but you need to make sure everything is as stock as possible first. Follow these steps:
0. BACKUP with a nandroid backup
1. Uninstall any apps that changed the /system partition (like xposed).
2. Unroot from the SuperSU app.
3. Flash the stock recovery (easiest way is to flash the latest full firmware).
4. If you are s-on, you may have to relock the bootloader first (I'm s-off, so I'm not sure).
5. Take the OTA.
6. If you are s-on, unlock the bootloader if you locked in step 4.
7. Flash TWRP.
8. Allow TWRP to root the phone (it will ask you if you want to root when you exit the recovery).
You can get the full firmware from this thread. If you wait though, someone might release a flashable stock rooted ROM, but the phone is old, so that may not happen.
Click to expand...
Click to collapse
If anyone does take the OTA and wants to send me a TWRP backup, I'd be more then willing to post a stock rooted flashable Rom.
Just throwing it out there, in case there's anyone interested, willing, and able.
Sent from my HTC6535LVW using Tapatalk
This is the second Stagefright patch/update.
There is an issue with the idea of flashing the latest full firmware, as it is not posted on the forum, the latest RUU post is the firmware before the first Stagefright update, I didn't realize this so I flashed stock recovery as that's how I took the first Stagefright patch, the problem with this is in the OTA update installation it identifies your build before installing so you will receive an error: "Package expects build fingerprint of blah blah/499067.10:user" but it will show as "499067.7:user" and abort installation as that is the fingerprint of the most recent firmware available on the forum, and not the most recent as of the first stagefright update. Someone needs to upload or find updated full firmware or maybe just stock recovery before the installation is possible.
So 6.23.651. 10 is not patched for "stagefright"?
Joshlul said:
This is the second Stagefright patch/update.
There is an issue with the idea of flashing the latest full firmware, as it is not posted on the forum, the latest RUU post is the firmware before the first Stagefright update, I didn't realize this so I flashed stock recovery as that's how I took the first Stagefright patch, the problem with this is in the OTA update installation it identifies your build before installing so you will receive an error: "Package expects build fingerprint of blah blah/499067.10:user" but it will show as "499067.7:user" and abort installation as that is the fingerprint of the most recent firmware available on the forum, and not the most recent as of the first stagefright update. Someone needs to upload or find updated full firmware or maybe just stock recovery before the installation is possible.
Click to expand...
Click to collapse
Just updating the firmware to the previous version won't be enough to allow the update to work.
Most OTA updates, unless they are a full Rom update or RUU, contain patch files.
Those patch files will check the MD5 of every single system file before patching each one.
So even if your firmware is current or your build.prop is edited, to pretend like you have the last version, it will still fail when checking the system files it intends on patching.
There is no way to trick an OTA to work.
You have to have the proper system files, for them to patch at all or properly.
So don't waste your time on that...you need the previous stock Rom for the latest OTA to ever apply properly, or at all.
Good luck!!
Sent from my HTC6535LVW using Tapatalk
links broken can anyone post the OTA update zip like ,i'm rooted with twrp recovery with s-on
santod040 said:
If anyone does take the OTA and wants to send me a TWRP backup, I'd be more then willing to post a stock rooted flashable Rom.
Just throwing it out there, in case there's anyone interested, willing, and able.
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
I created a TWRP backup using the following procedure:
1. Relocked my bootloader
2. Took the RUU (RUU_M7_WL_L50_SENSE60_SPCS_MR_Sprint_WWE_6.23.651.10.exe)
3. Unlocked my bootloader
4. Booted into fastboot
5. I tried to run: fastboot boot twrp-2.8.7.0-m7wls.img but that didn't work
6. fastboot flash recovery twrp-2.8.7.0-m7wls.img
7. I booted to recovery.
8. I selected read only
9. Created a backup leaving out the cache.
I'm not sure where to send it or where to post it (1.73GB)
chrishonson said:
I created a TWRP backup using the following procedure:
1. Relocked my bootloader
2. Took the RUU (RUU_M7_WL_L50_SENSE60_SPCS_MR_Sprint_WWE_6.23.651.10.exe)
3. Unlocked my bootloader
4. Booted into fastboot
5. I tried to run: fastboot boot twrp-2.8.7.0-m7wls.img but that didn't work
6. fastboot flash recovery twrp-2.8.7.0-m7wls.img
7. I booted to recovery.
8. I selected read only
9. Created a backup leaving out the cache.
I'm not sure where to send it or where to post it (1.73GB)
Click to expand...
Click to collapse
Could upload to Dropbox, Google Drive, Mega, whatever host you prefer.
Then send me a link via PM, or post it here and mention me.
If using Dropbox, a public link could cause too much traffic on your account, if posted publicly.
Feel free to shoot me a PM if you need further guidance on it.
Thanks for your effort, it should benefit a few folks.
Sent from my HTC6535LVW using Tapatalk
I can't post links yet so pm me if anyone wants the link.
The funny thing about this rom is that TWRP didn't root it like i expected it would. It installed SuperSU but "There is no SU binary installed, and SuperSU cannnot install it..."
Maybe I'm missing something.
santod040 said:
Could upload to Dropbox, Google Drive, Mega, whatever host you prefer.
Then send me a link via PM, or post it here and mention me.
If using Dropbox, a public link could cause too much traffic on your account, if posted publicly.
Feel free to shoot me a PM if you need further guidance on it.
Thanks for your effort, it should benefit a few folks.
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
having a similar issue. relocked and RUU'd using last release. For some reason my OTA fails. I found some other guidance that said to extract the stock recovery from the OTA and flash it then run the OTA again, but for some reason I can't extract recovery from firmware. If anyone can post it, I'd like give that method a try. Thanks!
yeah so twrp-2.8.7 wasn't able to flash super su binary in a way that would stick. twrp-2.8.6 worked fine. I think may have seen this issue elsewhere.

Stock Nexus 6 (Verizon) will not update!

Hi guys,
As I wrote in the title, my Verizon Nexus 6 will not update. When I get a notification for the software update, I see that it downloads and is ready to restart the phone so it will install the update...
but when I do, it will display the android icon with the word "error" above it. No error number or details about why it did not work.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Things I tried already are:
formatting the phone (both through the settings menu as well as the stock bootloader)
deleting data and cache in Google Services Framework (via settings/apps/all apps)
I have more than enough space in my storage; more than 2/3rds of my storage is free space, so I really am having trouble wrapping my head around why this software update is failing to install. And since all the threads and help things I find are for rooted phones, I am having trouble finding something that would offer an answer. I was hoping to keep this phone stock as long as possible, which is an oddity for me because I usually want to root my phone immediately. I guess I just really like this phone as stock. And other than this update that fails to load, the phone has no other issues, other than a few emojis that fail to show, but I feel like that's from the software not being able to update for the 6 months that I've been trying to update it.
Any help with this would be greatly appreciated! Thank you!!
Is your device unlocked? Have you tried to sideload the update?
If your device is unlocked you can use NRT to update without loosing any data.
PickelledEggs said:
Hi guys,
As I wrote in the title, my Verizon Nexus 6 will not update. When I get a notification for the software update, I see that it downloads and is ready to restart the phone so it will install the update...
but when I do, it will display the android icon with the word "error" above it. No error number or details about why it did not work.
Things I tried already are:
formatting the phone (both through the settings menu as well as the stock bootloader)
deleting data and cache in Google Services Framework (via settings/apps/all apps)
I have more than enough space in my storage; more than 2/3rds of my storage is free space, so I really am having trouble wrapping my head around why this software update is failing to install. And since all the threads and help things I find are for rooted phones, I am having trouble finding something that would offer an answer. I was hoping to keep this phone stock as long as possible, which is an oddity for me because I usually want to root my phone immediately. I guess I just really like this phone as stock. And other than this update that fails to load, the phone has no other issues, other than a few emojis that fail to show, but I feel like that's from the software not being able to update for the 6 months that I've been trying to update it.
Any help with this would be greatly appreciated! Thank you!!
Click to expand...
Click to collapse
You might try clearing the cache partition in recovery and reboot. Maybe the next OTA will be install without issues.
lol!
if you made any kind of changes, chances are that any ota will not work. but that's alright, all you have to do is flash the factory image. it would've been updated already if you did that instead of writing out your post. you can grab it here https://developers.google.com/android/nexus/images
simms22 said:
lol!
if you made any kind of changes, chances are that any ota will not work. but that's alright, all you have to do is flash the factory image. it would've been updated already if you did that instead of writing out your post. you can grab it here https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
I don't think you read my post at all... I didn't make any changes. My phone is fully stock. No root at all. No unlock. No modifications whatsoever The ota Software update just will not work.
gee2012 said:
You might try clearing the cache partition in recovery and reboot. Maybe the next OTA will be install without issues.
Click to expand...
Click to collapse
I tried going in to recovery mode, but when I do, it gives me the same android error icon, but instead of "error" it says "no command"
Timza said:
Is your device unlocked? Have you tried to sideload the update?
If your device is unlocked you can use NRT to update without loosing any data.
Click to expand...
Click to collapse
Nope. Not unlocked. No modification whatsoever
PickelledEggs said:
Nope. Not unlocked. No modification whatsoever
Click to expand...
Click to collapse
If you nothing else works, I would try to sideload the update by downloading the image from Google's Factory Images for Nexus Devices page.
PickelledEggs said:
Nope. Not unlocked. No modification whatsoever
Click to expand...
Click to collapse
Best is to enable OEM UNLOCKING and usb debugging in developer options, reboot into fastboot and unlock the bootloader and after the reboot flash the latest MMB29S firmware as @simms22 allready stated. Flash the img`s seperately in fastboot, all i would flash personaly is the system and boot img.
Timza said:
If you nothing else works, I would try to sideload the update by downloading the image from Google's Factory Images for Nexus Devices page.
Click to expand...
Click to collapse
gee2012 said:
Best is to enable OEM UNLOCKING and usb debugging in developer options, reboot into recovery and unlock the bootloader and after the reboot flash the latest MMB29S firmware as @simms22 allready stated. Flash the img`s seperately in fastboot, all i would flash personaly is the system and boot img.
Click to expand...
Click to collapse
Oh ok, I must have misinterpereted what SImmz was saying, then. I got in to recovery mode and wiped cache finally, so I will see if that works, otherwise I'll try your guys' other suggestions
PickelledEggs said:
Oh ok, I must have misinterpereted what SImmz was saying, then. I got in to recovery mode and wiped cache finally, so I will see if that works, otherwise I'll try your guys' other suggestions
Click to expand...
Click to collapse
I had this issue with my Nexus 7 (stock) - wiped the cache partition in recovery, and waited for OTA to appear again - and it worked.
BTW, you don't need root to make certain changes(I don't know what changes, but I know many don't get ota because of). or google just made it to sensitive.
Timza said:
If you nothing else works, I would try to sideload the update by downloading the image from Google's Factory Images for Nexus Devices page.
Click to expand...
Click to collapse
You can only sideload OTA`s in stock recovery afaik, not complete images.
gee2012 said:
You can only sideload OTA`s in stock recovery afaik, not complete images.
Click to expand...
Click to collapse
Ah, my mistake. I (wrongly) assumed OTAs were included on that download page.
is using nexus root tool kit let you flash with su 2.5.2 or it using the lastest 2.66? or that makes no difference when flashing stock image?
MikePancake6 said:
is using nexus root tool kit let you flash with su 2.5.2 or it using the lastest 2.66? or that makes no difference when flashing stock image?
Click to expand...
Click to collapse
The latest version of NRT (v2.1.4) uses SuperSU 2.6.6.
Timza said:
The latest version of NRT (v2.1.4) uses SuperSU 2.6.6.
Click to expand...
Click to collapse
is there any way to use 2.5.2, or flashing a custom rom will system root or will it be systemless root anyhow?
MikePancake6 said:
is there any way to use 2.5.2, or flashing a custom rom will system root or will it be systemless root anyhow?
Click to expand...
Click to collapse
After you flash with TWRP (a step with NRT). When you opt to reboot system, you will get a message asking if you would like to install SuperSU. If you swipe to install you will have a "system root". If you opt to not install, you will have a systemless root.
Personally, I have a "system root", and it seems to be working fine, whereas before, I was having an issue with the systemless root.
Timza said:
After you flash with TWRP (a step with NRT). When you opt to reboot system, you will get a message asking if you would like to install SuperSU. If you swipe to install you will have a "system root". If you opt to not install, you will have a systemless root.
Personally, I have a "system root", and it seems to be working fine, whereas before, I was having an issue with the systemless root.
Click to expand...
Click to collapse
ok, thank you for all the help. i already unlocked the bootloader using the tool kit.
tonight i will root it and try a custom rom. maybe chrome or pure nexus project, those seem to be stock with extra options and rro customize.
Thanks guys. I just got around to sideloading the update last night and it's working like a dream.
I'll probably root it soon now. I've been feeling the itch recently... Lol
This (so far) is probably my favorite stock phone though. I might keep it stock for a bit longer
Sent from my Nexus 6 using Tapatalk

Categories

Resources