So my brother asked for some help to update his device....
Keep IN Mind his
Software Version is
3.41.651.41
HTC Sense 7.0
Security Patch Nov 1st 2016
as we both checked it had been a long time since he has updated since 7.0.1 and we received a notification about Nougat.
As we 1st downloaded the OTA zip.. we had 52% battery and tried to install it followed by the on screen instructions but to no avail.... a Red Triangle and Exclamation in the Middle Appeared right after the
25% mark... but to note the 24% mark just blinks once. before it hits 25% a few seconds later, before that error is displayed.
After wards we restart it or it restarts itself back to the Original Firmware we were just on a few minutes ago , all untouched.
Tried a 2nd time, cleared the Cache and that didn't work either same response..
as for the the 3rd time i cleared the Cache, and then Restarted to go into the Recovery Mode but I can't event access that at all just another Red Triangle is displayed , unable to perform any actions with the Vol Buttons or Power Buttons...
any suggestions??
htc one m9 s-on bootlodaer locked untouched , not rooted, tried ota update but it failed, can't access recovery menu .
IAmTechFreq said:
So my brother asked for some help to update his device....
Keep IN Mind his
Software Version is
3.41.651.41
HTC Sense 7.0
Security Patch Nov 1st 2016
as we both checked it had been a long time since he has updated since 7.0.1 and we received a notification about Nougat.
As we 1st downloaded the OTA zip.. we had 52% battery and tried to install it followed by the on screen instructions but to no avail.... a Red Triangle and Exclamation in the Middle Appeared right after the
25% mark... but to note the 24% mark just blinks once. before it hits 25% a few seconds later, before that error is displayed.
After wards we restart it or it restarts itself back to the Original Firmware we were just on a few minutes ago , all untouched.
Tried a 2nd time, cleared the Cache and that didn't work either same response..
as for the the 3rd time i cleared the Cache, and then Restarted to go into the Recovery Mode but I can't event access that at all just another Red Triangle is displayed , unable to perform any actions with the Vol Buttons or Power Buttons...
any suggestions??
htc one m9 s-on bootlodaer locked untouched , not rooted, tried ota update but it failed, can't access recovery menu .
Click to expand...
Click to collapse
Make sure you have ADB installed and USB debugging turned on. Now get the RUU
Which you can get from here: https://forum.xda-developers.com/sp...nt/ruu-sprint-htc-one-m9-1-32-651-17-t3073355 and put it in either the SD card or the internal storage then connect the phone to your PC and open the command prompt where adb is installed and type "adb reboot bootloader" and it should reboot it and give you the prompt to install
Help with Nougat update
I'm having the exact same problem. Have tried wiping the cache partition and factory resets among other things but nothing works. It gets stuck at 25% and goes back to 6.0. I don't have easy access to a computer and am hoping to get it OTA. It's a Sprint HTC One M9. Any assistance would be greatly appreciated!
6th_Hokage said:
Make sure you have ADB installed and USB debugging turned on. Now get the RUU
Which you can get from here: https://forum.xda-developers.com/sp...nt/ruu-sprint-htc-one-m9-1-32-651-17-t3073355 and put it in either the SD card or the internal storage then connect the phone to your PC and open the command prompt where adb is installed and type "adb reboot bootloader" and it should reboot it and give you the prompt to install
Click to expand...
Click to collapse
I tried the executable one listed under 'Latest RUU' and in the process it threw an error and along the lines that it was incorrect and rolled back the installation. It's the same version as the original posters, so I'm not sure why it went wrong.
I'm planning to download 4.27 under '0PJAIMG RUUs', but not sure if I'll have the same issue. Will there be?
More specific details
Just about given up on this one but am trying again. Not fully versed in all the language but hope this makes sense.
Have tried cache partition wipes, factory resets, and OTA on bootloader with no success.
Recently moved and can't easily get my hands on a PC. Htc Sync Manager works with Mac but can't install the RUU.
When using bootloader two different error messages showed up. Will try and type the relevant info and see if anyone can make sense of it and possibly help me solve this VERY frustrating situation.
Installing update...
N70QCT.01.000.004
Source: htc/himawhl_sprint_wee/htc_himawhl:6.0/MRA58K/695981.41:user/release-keys
Target:
htc/himahl_sprint_wwe/htc_himawhl:7.0/NRD90M/870580.4 user/release keys
Verifying current system...
system partition has unexpected contents
E:Error in /sideload/package.zip
(Status 7)
Installation aborted.
also
Data wipe complete.
-- Install /sdcard/OTA_HIMA_WHL_N70_SENSE80_SPCS_MR_Sprint_WWE_4.27.651.4-3.41.651.41_release_500479.zip...
E:failed to unmount/preload
E:failed to set up expected mounts for install; aborting
Installation aborted.
Not sure if any of this will make sense to anyone but any assistance would be greatly appreciated! Can give more info if I've missed something.
No surprise that Sprint and Htc have been of little help.
Thanks!
Anevo1ver said:
Just about given up on this one but am trying again. Not fully versed in all the language but hope this makes sense.
Have tried cache partition wipes, factory resets, and OTA on bootloader with no success.
Recently moved and can't easily get my hands on a PC. Htc Sync Manager works with Mac but can't install the RUU.
When using bootloader two different error messages showed up. Will try and type the relevant info and see if anyone can make sense of it and possibly help me solve this VERY frustrating situation.
Installing update...
N70QCT.01.000.004
Source: htc/himawhl_sprint_wee/htc_himawhl:6.0/MRA58K/695981.41:user/release-keys
Target:
htc/himahl_sprint_wwe/htc_himawhl:7.0/NRD90M/870580.4 user/release keys
Verifying current system...
system partition has unexpected contents
E:Error in /sideload/package.zip
(Status 7)
Installation aborted.
also
Data wipe complete.
-- Install /sdcard/OTA_HIMA_WHL_N70_SENSE80_SPCS_MR_Sprint_WWE_4.27.651.4-3.41.651.41_release_500479.zip...
E:failed to unmount/preload
E:failed to set up expected mounts for install; aborting
Installation aborted.
Not sure if any of this will make sense to anyone but any assistance would be greatly appreciated! Can give more info if I've missed something.
No surprise that Sprint and Htc have been of little help.
Thanks!
Click to expand...
Click to collapse
I'm getting similar issues. I tried downloading the executable from the link above and the htc site, both are giving signature errors. I tried updating via adb and i got the same error you have. Not sure if I want to proceed any further with this, if this is causing so much issue installing.
Related
I am a new Android convert and purchased the Photon 4G last week. I successfully rooted, though I have not unlocked the bootloader. I flashed the Photon Laser 1.1 ROM, and then the Alien 1.1 Rom and theme. After noticing that I had no 3G/4G, I decided to revert to stock and avoid the Alien 1.1 for now. I went into Clockworkmod and wiped the dalvik cache, which I think was my major mistake, then in android recovery mode I wiped the cache 3 times, and did a factory restore. From this point forward I can not boot the phone successfully. Once it comes up to the tap the android to begin screen, I receive multiple error messages requesting the calander, phone, and other apps be force closed. I am unable to get into the phone at all. Additionally, if I tap the android icon, I can see the icon flex indicating my tap, but nothing happens. I've spent the last 6 hours attempting to use RSD Lite to reflash the stock image, but I receive an error each time stating "Failed flashing process. Unable to retrieve initialization values from INI file. (0x7029); phone connected." I need some direction from anyone that can help. Thank you in advance.
WEC2011 said:
I am a new Android convert and purchased the Photon 4G last week. I successfully rooted, though I have not unlocked the bootloader. I flashed the Photon Laser 1.1 ROM, and then the Alien 1.1 Rom and theme. After noticing that I had no 3G/4G, I decided to revert to stock and avoid the Alien 1.1 for now. I went into Clockworkmod and wiped the dalvik cache, which I think was my major mistake, then in android recovery mode I wiped the cache 3 times, and did a factory restore. From this point forward I can not boot the phone successfully. Once it comes up to the tap the android to begin screen, I receive multiple error messages requesting the calander, phone, and other apps be force closed. I am unable to get into the phone at all. Additionally, if I tap the android icon, I can see the icon flex indicating my tap, but nothing happens. I've spent the last 6 hours attempting to use RSD Lite to reflash the stock image, but I receive an error each time stating "Failed flashing process. Unable to retrieve initialization values from INI file. (0x7029); phone connected." I need some direction from anyone that can help. Thank you in advance.
Click to expand...
Click to collapse
Hey, I just wanted to confirm that you used RSDlite to flash the Final SBF release...45.2.5? And that didn't work? I've had issues with RSDlite attempting flash and then fail on me too. In that case, my phone would turn on into the Moto-boot logo, and then get stuck. I took the battery out and put it back in and it seemed to get me back into the phone after booting. Maybe you can try to reflash the final 45.2.5 update again?? Try using the cmd terminal to reboot or push files onto the phone? Sorry I don't know too much..I'm still really new to android.
I have followed the exact steps from this page: (http://forum.xda-developers.com/showthread.php?p=16328237), but every time RSD Lite fails with the error message I listed in the original post. I have pulled the battery several times, but am unable to get past the "tap the Android" screen. Tapping it leads to no change at all. I have no access to CWM anymore, and can only access recovery from Android recovery now, which I have used to reboot a few times at this point. When I reboot, I am greeted with errors that include "The process com.android.phone has stopped unexpectedly. Please try again." and "The application Suggestions Poll Scheduler Service (process com.motorola..suggestions.scheduler) has stopped unexpectedly. Please try again." and "The application Calander Storage (process com.android.calendar has stopped unexpectedly. Please try again."
WEC2011 said:
I have followed the exact steps from this page: (http://forum.xda-developers.com/showthread.php?p=16328237), but every time RSD Lite fails with the error message I listed in the original post. I have pulled the battery several times, but am unable to get past the "tap the Android" screen. Tapping it leads to no change at all. I have no access to CWM anymore, and can only access recovery from Android recovery now, which I have used to reboot a few times at this point. When I reboot, I am greeted with errors that include "The process com.android.phone has stopped unexpectedly. Please try again." and "The application Suggestions Poll Scheduler Service (process com.motorola..suggestions.scheduler) has stopped unexpectedly. Please try again." and "The application Calander Storage (process com.android.calendar has stopped unexpectedly. Please try again."
Click to expand...
Click to collapse
I know it's somewhere in this forum, but if you brick your phone and render it useless, you can try and reflash the original SBF...not the update. Give it a shot. Just let the force closes go, but see if you can connect to your computer. Best of luck!
Thanks, but I think that's what I was doing. Maybe it was the update. Can anyone point me to the original sbf? Thanks again for the replies.
http://www.multiupload.com/FNZKNV0T3G
thats the link, u need to unzip and then mount it on RSDlite
Thank you so much. I will download now and run it. Let you know if it finally works. Thank you for the link and help.
So nothing under the sun worked at all. I ended up having to take the phone back to the retailer and received a new one. I am happy now because after two days I have a functioning phone. I still believe that my error was clearing the dalvik cache before the factory reset, but I wouldn't have done that had the Alien ROM, which I mostly liked, hadn't killed my non-wifi data reception, as in I had none. Thank you the those of you who took time out to read and post a reply to help me. I am very grateful.
Help
Hey guys:
Yesterday I made mega mistake, I've flashed CM7 but... I didn't notice that I had to unlock the bootloader, obviously didn't work , but now, the phone is stuck on "unable to boot 2 entering RSD mode" with the Moto logo, so I tough, I will flash it again with the official Sprint update and fix the whole thing, but RSD gets to 100% restarts the phone and then phone shows just garbage! just like a blurry image, can't describe correctly but doesn't go any further. I've removed the battery start the phone again and then I get the same message "unable to boot 2 entering RSD mode". I'm on a loop right now, any advise will very appreciated, thanks'
Try flashing the 154_5 sbf...when in rsd mode...ive always had luck,with it as a starting point.
Sent from my MB855 using xda premium
KTT16 said:
Try flashing the 154_5 sbf...when in rsd mode...ive always had luck,with it as a starting point.
I will certainly give it a shot. I don't remember right now which file is the one that i got, I'm at work, but took me about 2 days in a row to download the file on my 128 kbps connection... third world connection.. I know.
Something that I would like to know is, when I turn the phone on takes directly to the error, if I press power + volume up then takes me to fast boot and stays there and if I do power + volume down gives a messages for about 1 second goes away and the phone goes like dead... I have to remove the battery to get it going again. Is there anything else that I need to know?.
thanks'
Click to expand...
Click to collapse
you need to get into rsd mode by powering up + volume up but use rsd verion 5.5 when connecting to the computer. Then after run the sbf and wait till it asks to manually power up the phone..pull battery and ur golden.
Make sure youre fully charged and have allege drivers installed properly.
Sent from my MB855 using xda premium
KTT16 said:
you need to get into rsd mode by powering up + volume up but use rsd verion 5.5 when connecting to the computer. Then after run the sbf and wait till it asks to manually power up the phone..pull battery and ur golden.
Make sure youre fully charged and have allege drivers installed properly.
You're the man!!!, I've dowloaded the file you told me and RSD 5.5 and I'm back in bussiness. I just unlocked the bootloader... ready to try CM7, yay!.
Thank you for your support, best regards.
Click to expand...
Click to collapse
I've been trying to fix this phone for 3-4 weeks now with no luck, so I figured this would be the right place to come.
I was way too tired and I was trying to use ROM Manager to try and flash a ROM that WAS NOT meant for my phone. Long story short I got stuck in a boot loop. I get past the Pantech logo then I hang at the AT&T logo. All I have access to is the bootloader menu and stock recovery - I can get to fastboot through the bootloader menu and I can get to ADB Sideload through recovery.
I've tried everything I can think to do with no luck. Then last night I got the update.zip for last year's OTA JB update. Through sideload I tried: adb sideload c:\adb\flex-jb-update.zip
It pushes the update to the phone and unpacks it fine. But after 24% or so I get an error on the phone and the installation gets aborted. It says something about the AT&T Family Map apk.
If I could get any pointers that would be great, 'cause I'm really not looking to send it back to AT&T. Last year I bricked my phone and I knew it wouldn't be covered by insurance so I smashed my phone to pieces and told AT&T that it got ran over by a car. Worked once, probably won't work again.
Any help would be great.
Thanks In Advance,
TJ
Just tried re-signing the update.zip and doing it again. I got the same error.
After "Verifying current system..." I get "assert failed: apply_patch_check("/system/app/ATTFamilyMap.apk" , "3014be541877900d308d9ca725ef507c96c33af8" , "1ea33a46e2d5330e30dca81aa4f9ecb52461677c")
Installation aborted.
Urgggg.
Here is where I was at, ready to throw away the phone I ruined. I was rooted and S-ON and unlocked via HTC unlock bootloader web page. I was happily trying new things here when my phone went to all white background with green HTC letters. Wouldnt do anything. While trying to fix that I erased my backup and the software on the phone. I let the phone sit all day hoping the white backgound would go away but no. It wouldnt even power off. But I able to get into bootloader by doing this: Hold down power and volume up for 10 seconds, as soon as the screen goes blank slide finger down to volume down and hold. This got me into boot loader. I tried all the things outlined here to recover (using abd commands, fastboot *.img files nandroid backups, sideloading etc. My CID shows CWS_001 and next to the OS field is blank. Pulled the SIM and SD card to erase cache, no help. Wipe delvick, data, etc all failed with the E: unable to mount message. 2 Days gone by with not even a glimmer of recovering phone
So I went to HTC support download news (sorry cant post a link until 10 posts) and downloaded the RUU that contains the 4.4.3 update. This is an exe file that updates your phone. It failed on the first go. So I relocked the phone using wonders_never_cease M8 all in one kit, then double clicked on the RUU app again. It took off and ran. It is menu driven so I answered all the acknowledgements and got to the update screen. On that screen "current version field was blank and update to field reflected the new RUU version. The instructions tell you to put your phone into recovery mode and select fastboot. My Windows PC already had the HTC drivers loaded. I was shocked when the app began loading modules without failing. I didnt have to do anything except put attach usb cable to phone from PC and put the phone in fastboot. 10 mins later, the phone rebooted and my hated ATT logo and tune showed. Am up and running on 4.4.3 and new firmware.
Everything works fine on the phone (no modules missing). So it appears the "upgrade" will wipe partition and reload all the software on the phone without doing much of anything else. Thought I post this up for any other semi-noob that got into trouble and just wants a working phone. I am not sure a phone that is S-OFF would work but it doesnt hurt to try. I do understand HTC stopped the OTA update due to battery draining issues but the download is still available for fastboot. Am just happy to have a working phone. Now will make a backup in TWRP immediately. Over and out....Michael
sethandian said:
Here is where I was at, ready to throw away the phone I ruined. I was rooted and S-ON and unlocked via HTC unlock bootloader web page. I was happily trying new things here when my phone went to all white background with green HTC letters. Wouldnt do anything. While trying to fix that I erased my backup and the software on the phone. I let the phone sit all day hoping the white backgound would go away but no. It wouldnt even power off. But I able to get into bootloader by doing this: Hold down power and volume up for 10 seconds, as soon as the screen goes blank slide finger down to volume down and hold. This got me into boot loader. I tried all the things outlined here to recover (using abd commands, fastboot *.img files nandroid backups, sideloading etc. My CID shows CWS_001 and next to the OS field is blank. Pulled the SIM and SD card to erase cache, no help. Wipe delvick, data, etc all failed with the E: unable to mount message. 2 Days gone by with not even a glimmer of recovering phone
So I went to HTC support download news (sorry cant post a link until 10 posts) and downloaded the RUU that contains the 4.4.3 update. This is an exe file that updates your phone. It failed on the first go. So I relocked the phone using wonders_never_cease M8 all in one kit, then double clicked on the RUU app again. It took off and ran. It is menu driven so I answered all the acknowledgements and got to the update screen. On that screen "current version field was blank and update to field reflected the new RUU version. The instructions tell you to put your phone into recovery mode and select fastboot. My Windows PC already had the HTC drivers loaded. I was shocked when the app began loading modules without failing. I didnt have to do anything except put attach usb cable to phone from PC and put the phone in fastboot. 10 mins later, the phone rebooted and my hated ATT logo and tune showed. Am up and running on 4.4.3 and new firmware.
Everything works fine on the phone (no modules missing). So it appears the "upgrade" will wipe partition and reload all the software on the phone without doing much of anything else. Thought I post this up for any other semi-noob that got into trouble and just wants a working phone. I am not sure a phone that is S-OFF would work but it doesnt hurt to try. I do understand HTC stopped the OTA update due to battery draining issues but the download is still available for fastboot. Am just happy to have a working phone. Now will make a backup in TWRP immediately. Over and out....Michael
Click to expand...
Click to collapse
congratulations that you restore your device. the link for the RUU its already posted in the General Forum http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
also a bootable no pc version of it http://forum.xda-developers.com/att...-2-23-502-3-bootable-ruu-pc-required-t2860486
as well as the OTA http://forum.xda-developers.com/att-htc-one-m8/general/htc-m8-4-4-3-official-ota-t2860139
t5620 said:
congratulations that you restore your device. the link for the RUU its already posted in the General Forum http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
also a bootable no pc version of it http://forum.xda-developers.com/att...-2-23-502-3-bootable-ruu-pc-required-t2860486
as well as the OTA http://forum.xda-developers.com/att-htc-one-m8/general/htc-m8-4-4-3-official-ota-t2860139
Click to expand...
Click to collapse
Thanks for posting up the links.
sethandian said:
Here is where I was at, ready to throw away the phone I ruined.
Click to expand...
Click to collapse
As long as the screen comes on for this phone, its virtually always recoverable. There was never any reason to think you had to throw away the phone. Next time you are stuck, just ask for help here; as we are happy to help. You did the right thing in trying to find existing solutions. But it sounds like you did your due diligence searching and reading; and would have been justified starting a new thread and asking for help.
sethandian said:
Everything works fine on the phone (no modules missing). So it appears the "upgrade" will wipe partition and reload all the software on the phone without doing much of anything else.
Click to expand...
Click to collapse
That is precisely what the RUU does. Its a complete image, and handy for recovery purposes.
sethandian said:
I do understand HTC stopped the OTA update due to battery draining issues but the download is still available for fastboot. l
Click to expand...
Click to collapse
While the OTA has had some reports of causing battery issues, the RUU has not had any reports of such issue, and seems to be free of it.
sethandian said:
I am not sure a phone that is S-OFF would work but it doesnt hurt to try.
Click to expand...
Click to collapse
S-off does not affect whether or not the RUU will work, I don't know why folks keep saying or asking this. RUU will work whether S-on or S-off. The only difference, is that with S-on, you need to either have a LOCKED bootloader, or RELOCKED (relock it manually if you unlocked it).
Also, in general, S-off does not limit anything. It means "all security off" and enables more access, not the opposite. If anything, S-off enables more things than S-on.
Thanks for the all the info. The experience was a valuable teaching moment. Now back to playing around with the M8.
Hello all. So my rooted HTC Rezound ran into a software problem. After powering it onn, it would get into the system, activate bluetooth (on its own), shut down and restart the cycle again. The only way to stop once it started was by removing the battery. For this reason I was forced to find a technician to replace my OS. However, the software with which he replaced the old one has problems of its own. compatibility issues with applications for instance. Somehow I found myself with this new OS running into its own problems too. the System UI is not responding which basically means I can do nothing on the phone. once I get the device powered up. the only functional element or command left of this ware is the dropdown status bar which is showing not even a single drop-down menu. This compelled me to try and install the CM10. OS package, the PH98IMG.zip in the ClockworldMod Recovery v6.0.3.2 but every time I try it aborts with the message, "Installation aborted"
please help me out what am I doing wrong and how do I make it right?
Telltower said:
Hello all. So my rooted HTC Rezound ran into a software problem. After powering it onn, it would get into the system, activate bluetooth (on its own), shut down and restart the cycle again. The only way to stop once it started was by removing the battery. For this reason I was forced to find a technician to replace my OS. However, the software with which he replaced the old one has problems of its own. compatibility issues with applications for instance. Somehow I found myself with this new OS running into its own problems too. the System UI is not responding which basically means I can do nothing on the phone. once I get the device powered up. the only functional element or command left of this ware is the dropdown status bar which is showing not even a single drop-down menu. This compelled me to try and install the CM10. OS package, the PH98IMG.zip in the ClockworldMod Recovery v6.0.3.2 but every time I try it aborts with the message, "Installation aborted"
please help me out what am I doing wrong and how do I make it right?
Click to expand...
Click to collapse
The recovery fails or the rom install fails? If it is the recovery, then you'll need to install it manually via the PC using fastboot. One of the more important things to note, is if your device is S-On or S-Off. It will tell you on the bootloader screen. If you are S-On (most likely), then you will have to install the rom in recovery, as well as take the boot.img out of the rom zip and install that via fastboot while in the bootloader as well. If this sounds like gibberish to you, then that just means you have a lot of research to do before you get this fixed...
First time poster, but thought I'd share how I managed to fix my problem, in hope that it helps someone else out.
I recently received the OTA Marshmallow update for my Stock Nexus 9 (unrooted and locked bootloader), but unfortunately it didn't work, and threw me into "bootloop" where it continually tried to apply the update but failed. First off I followed instructions to clear the Cache, which only made the problem worse, as all the tablet would do then was boot into the “swirling colour dots” and do nothing else until eventually the battery died.
After reading several forum posts I discovered that the usual solution is to flash via fastboot, however on a Nexus 9 you need to unlock the bootloader by activating "Enable OEM Unlock" from within Android. As I'm running a 100% Stock Nexus 9 I had never done this, so couldn't flash it.
Eventually though, after having an absolute nightmare trying to get it to work again, I found a working solution! Just use "Apply update from ADB" under Recovery, along with the correct update image!
A lot of what's in the steps below is likely to be known to most of the community, but I’ve tried to keep the steps extra simple so anyone can pick this up.
Steps:
1. Reboot into HBOOT (Hold down Volume Down + Power Button).
2. Press Volume Down to highlight Recovery, then press the Power Button to enter it.
3. Wait until the Google logo goes away, and you should see a picture of an Android laying on it’s back. Hold down the Power Button + Volume Up (very important to hold Power FIRST).
4. On the Recovery page it lists a few details about your version at the top. Note down the 6 character identifier for your device (which is in the format of 3 text characters, 2 numeric, and another text char). For me I was running 5.1.1 before the update, so my identifier was LMY48T.
5. Find the OTA update that upgrades from your current version to the next version. For me I was going from 5.1.1 to 6.0.0 on a Nexus 9, so I searched for LMY48T on Google and found that this was the OTA update needed: https://android.googleapis.com/pack...83199e.signed-volantis-MRA58K-from-LMY48T.zip
6. If you don’t have it already, download and install “Minimal ADB and Fastboot”: http://forum.xda-developers.com/showthread.php?t=2317790 – when it’s installed let it run straight away, and leave the command prompt open you’ll need it in a min.
7. If you don’t have it already, download and unzip the Google USB Driver: https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
8. Copy the OTA update file you downloaded to the folder that Minimal ADB was installed in (usually C:\Program Files (x86)\Minimal ADB and Fastboot\).
9. Back on your device use Volume down to get to “Wipe Cache Partition”, and press the Power Button to activate it. If you want to be really sure this will work you should do a “Wipe data/factory reset” too, but be aware you will definitely lose your data.
10. Use Volume up to go to “Apply update from ADB”, and press the Power Button to enter it.
11. Plug your tablet into your PC (if it’s not already). You’ll need to go to your Device settings on your PC and you should see a new device named the same as your device or possibly just “Android”. Go to the Properties of the device and force the Driver to be the ADB Google driver from the Google USB Drivers that you downloaded earlier. (There’s plenty of other longer tutorials on how to do this if you’re having issues)
12. On your PC, in the Minimal ADB Command Prompt (that you should still have open from earlier) enter “adb sideload {NAMEOFOTAFILE}” e.g. for me this was “adb sideload ab835e17c874202049463ccd916f86fede83199e.signed-volantis-MRA58K-from-LMY48T.zip”.
13. Let it run. It took less than half hour for it to install for me, and I’m now the proud owner of a working Stock Nexus 9 with Marshmallow!
So why does this work but applying the stock images via fastboot doesn’t? As far as I can see it must be due to the “signing” of the files. The regular stock Google fastboot flash images don’t include signature information (as far as I’m aware) so they’re rejected as unsafe by the locked bootloader, whereas when you run the OTA update files through ADB sideloading signatures are on the OTA update files, and your device determines that these are safe to install.
Yeah, as long as your system partition is intact, "adb sideload" is a good option. I'm not so lucky...
nothint to do with mine, it doesn't show any OS versione unfortunately.
works well
Hi,
I had exactly the same upgrade failure, despite of a clean stock Nexus 9.
I followed the procedure and it works great for me.
Thank you for this post !
FYI - You don't need to go searching for OTA files on Google. They're all conveniently posted here:
http://forum.xda-developers.com/showthread.php?t=2906492
Ok, so I found where mine said lmy48i. I downloaded the upgrade file a8f87fa059f17f2fd4cd773921e888366b1dfa0e.signed-volantis-LMY48M-from-LMY48I.a8f87fa0.zip. When adb starts sending it, it gets to about 48% and the tablet starts verifying already. It winds up erroring out with the following information:
************
system partition has unexpected contents
E:Error in /sideload/package.zip
(Status 7)
Installation aborted.
************
Any thoughts?
Josh
gijosh28 said:
Ok, so I found where mine said lmy48i. I downloaded the upgrade file a8f87fa059f17f2fd4cd773921e888366b1dfa0e.signed-volantis-LMY48M-from-LMY48I.a8f87fa0.zip. When adb starts sending it, it gets to about 48% and the tablet starts verifying already. It winds up erroring out with the following information:
************
system partition has unexpected contents
E:Error in /sideload/package.zip
(Status 7)
Installation aborted.
************
Any thoughts?
Josh
Click to expand...
Click to collapse
The same situation, maybe have any other solutions?
I wound up calling HTC and getting an return authorization. I have to pay shipping to them. They cover shipping back to me. But the whole thing is going to wind up taking about 2 weeks. Couple days to get there, 7-10 days to fix, couple back. I haven't sent it out yet. I bought mine at BestBuy, so I was going to see if I could swap it out there first.
Josh
it doesnt show any OS version either, what can i do?
Guide works perfectly. Massive thanks.
The trick is finding the latest OTA zip. Here for the moment.
http://apk-bro.blogspot.com/2015/12/download-android-601-marshmallow-ota.html
I got it to work but I'm never buying another HTC product again. I called warranty service in the first guy refused to help me out unless I had the tablet in front of me. The second guy did help me but I'm still waiting for the RMA ticket, it still has not showed up. So when I got these instructions I managed to resurrect for my Nexus 9 which is good. Now I have a working tablet to which I'm talking to the right now, but other than that HTC still sucks ass and I'm never going to buy anything from them again. Done.
I am on MRA58N currently facing the same issue. I downloaded the MMB29K update. But on running the sideload, I am getting the message
"E: Footer is wrong
E: Signature Verification Failed
Installation Aborted"
Pls tell how to proceed
harishvr9 said:
I am on MRA58N currently facing the same issue. I downloaded the MMB29K update. But on running the sideload, I am getting the message
"E: Footer is wrong
E: Signature Verification Failed
Installation Aborted"
Pls tell how to proceed
Click to expand...
Click to collapse
By some miracle or so, my device has come out of the bootloop and is working fine now. But it is giving me this error (link below), before the boot up begins.
https://lh3.googleusercontent.com/iGv9RPFbDSLec-4-cvsQNOh46pt5RhEvPy7EKKZXmbtjJ16P7d5EXOJHCIsR=w300
harishvr9 said:
By some miracle or so, my device has come out of the bootloop and is working fine now. But it is giving me this error (link below), before the boot up begins.
https://lh3.googleusercontent.com/iGv9RPFbDSLec-4-cvsQNOh46pt5RhEvPy7EKKZXmbtjJ16P7d5EXOJHCIsR=w300
Click to expand...
Click to collapse
Looks like the OTA corrupted something.
Note: OTA updates only work on completely stock devices.
Backup your devices important data.
If you where completely stock without unlocked bootloader, you will need to flash stock images to get rid of that message (OEM Unlock Command will wipe your device)
corkiejp said:
Looks like the OTA corrupted something.
Note: OTA updates only work on completely stock devices.
Backup your devices important data.
If you where completely stock without unlocked bootloader, you will need to flash stock images to get rid of that message (OEM Unlock Command will wipe your device)
Click to expand...
Click to collapse
I did a stock image flash using the Nexus Root Toolkit. But the message is still appearing whenever I restart the device. Otherwise the device is working perfectly.
When I get to step 4, I don't see device identifier text. I got text in pink saying
Code:
" *** Device state - LOCKED *** "
What do I do now
Just got it back from 'repair' via HTC, if anything it's got worse, with random freezes, lock screen freeze and bootloop.
Marshmallow OTA hose your Nexus device? Just flash the N dev preview.
Marshmallow OTA hose your Nexus device? Just flash the N dev preview.
Posting the above for anyone with a Bricked device from a previous Marshmallow OTA and where not able to resolve it by sideloading a Marshmallow OTA.
Many Thanks!!!!
Posting the above for anyone with a Bricked device from a previous Marshmallow OTA and where not able to resolve it by sideloading a Marshmallow OTA.[/QUOTE]
Posting the above for anyone with a Bricked device from a previous Marshmallow OTA and where not able to resolve it by sideloading a Marshmallow OTA.[/QUOTE]
I wanted to thank you for posting this solution!! I was able to flash N onto my nexus 9 and it is working once again. I was going to post this onto a main thread so that more people can see this but i did not want to seem as if i was taking credit for finding this. You should post this there so that you can help others. Once again, I would like to thank you. I am now trying to get into the usb debugging menu to unlock the bootloader so this does not happen again but i cannot find it in this version of android.
MANY THANKS!!!
dweissinger said:
I wanted to thank you for posting this solution!! I was able to flash N onto my nexus 9 and it is working once again. I was going to post this onto a main thread so that more people can see this but i did not want to seem as if i was taking credit for finding this. You should post this there so that you can help others. Once again, I would like to thank you. I am now trying to get into the usb debugging menu to unlock the bootloader so this does not happen again but i cannot find it in this version of android.
MANY THANKS!!!
Click to expand...
Click to collapse
1. Share the link where you like, the Original Finder of this is mentioned in the link
Posted here
2. Have you enabled developer options? Or does Android N not have that feature.
Found the developer options!!
Thanks and yes I found it. I had to reboot my tablet to see the Android version. It must be a bug but I will be happy to deal with a small bug like that. Much better than a bricked tablet. The first thing I did was to enable unlocking of the bootloader in case this happens again. Fool me once but not twice..lol