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
Hi all
For the last 5 days I have been struggling with my tf103c (which I am very much regretting having purchased in the first place!)
Basically I tried installing Xposed on it so I could try and tweak some of the very lacklustre performance.
However this was incompatible with my email client so I set about removing it.
Long story short I can do is get to a bootloader screen, however without the ability to reflash from SD card or wipe data or anything useful.
I can also get into the recovery screen (or the "Recovery starting..." screen) and can execute fastboot commands sent from my pc via usb from there.
Unfortunately all my attempts to reflash or update, at best lead me to the FAILED (remote: flash_cmds error! )
Which is where I'm now stuck.
I've tried various fimwares and techniques but without any further luck.
I was on the official 5.0 lollipop WW version from the Asus support page but trying to load this from fatboot leads to the same error.
Any suggestions please?
No one have any advice?
Come on - can somebody please help?
I have just bought a brand new Moto to root it.
So everything went fine with the rooting, I managed to get SuperSU on it.
However, I watched a YouTube video where someone said to flash twrp-3.2.0-sanders.img.
I used twrp-3.1.1-sanders.img before which worked fine. However so the person on YouTube gave three files to flash.
Which were:
"System.img"
"Boot.img"
"twrp-3.2.0-sanders.img"
So once I flashed all three using ADB, my phone doesn't boot anymore.
It automatically loads into Recovery mode giving this error:
"Error: failed to load kernel!"
"Fastboot Reason: Fall Through from normal boot mode"
I have tried flashing 'twrp-3.1.1-sanders.img" again but that didn't work. I currently don't know what to do now.
If you can get my phone working again, I'll give you a $20 gift card of your choice. Otherwise I'll just send it off to Motorola to let them fix it.
Solotime said:
I have just bought a brand new Moto to root it.
So everything went fine with the rooting, I managed to get SuperSU on it.
However, I watched a YouTube video where someone said to flash twrp-3.2.0-sanders.img.
I used twrp-3.1.1-sanders.img before which worked fine. However so the person on YouTube gave three files to flash.
Which were:
"System.img"
"Boot.img"
"twrp-3.2.0-sanders.img"
So once I flashed all three using ADB, my phone doesn't boot anymore.
It automatically loads into Recovery mode giving this error:
"Error: failed to load kernel!"
"Fastboot Reason: Fall Through from normal boot mode"
I have tried flashing 'twrp-3.1.1-sanders.img" again but that didn't work. I currently don't know what to do now.
If you can get my phone working again, I'll give you a $20 gift card of your choice. Otherwise I'll just send it off to Motorola to let them fix it.
Click to expand...
Click to collapse
drive.google.com/uc?id=0B1om01aNLee9c0g5M1liM2ltaXM&export=download
download and flash with file ...
your phone will be ok..
Hi all, attempted to root my phone today following this guide.
I got right up to step 9 but upon trying to reboot and launch from TWRP I began to have trouble. I've been able to access TWRP once, but after confirming install of SuperSU (step 11 here, my phone booted to the LG splash and I got the boot loop saying 'Your phone is unsecure, bootloader is unlocked' or words to that effect. Orange ! triangle.
I can launch to fastboot, or download mode. Turning on to a factory reset sends me back to a boot loop after confirming I would like to reset (leading me to believe I've not got a stock ROM in there at all).
Now when I try to flash any version of TWRP from command prompt in my ADB folder, I'm told my phone is corrupt and it won't allow me to flash.
Alternatively, trying to flash a stock ROM doesn't work either. LGUP does not recognise my model, it only shows COM Ports: [COM4, H85020s]. I've also tried using UPPERCUT but I get the following error: "Error reading from file: C:\Users\...\Roaming\Temp\F9FB5BD\TempFolder\UPPERCUT.exe. Verify the file exists and that you can access it." I've attempted running UPPERCUT from various locations, extracted.
I'm on Windows 10 and I've been trying desperately for the last 12 hours crawling through this site/ other articles for some kind of solution to give my phone SOME kind of functionality. Ultimate goal was LineageOS but now I'd be more than happy getting back to stock. I'd really appreciate any help, hope I've given enough information.
I've been getting help on this over at Hovatek, but it's extremely slow going; I first posted there on December 11 and it's still not resolved. This phone is a former Lifeline phone, and I've been trying to get it rooted so that I can use the Tello SIM I obtained. The problem the phone was having is that it refused to do any updates, so Tello's troubleshooting as to why it wasn't detecting the SIM was completely halted.
I did finally get to the point of rooting it. The major problem I have now is that it will only boot to fastboot mode. I can get it into recovery mode, but I get the dead android with "no connection" under it, and I've tried everything the internet has suggested to get past that, and it won't. Additionally, any fastboot command (apart from "fastboot devices") I try in ADB returns "FAILED (remote: 'unknown command'). I don't know how to get it into EDL mode from fastboot. I've tried every button combo possible, and the only one that does anything different is power + volume up, which changes it to a bright white screen. At this point I just want to do a hard reset so I can take another go at the rooting process, but the phone doesn't seem to want to allow me to. I would appreciate any help with this; I don't have a working phone at the moment because of these issues.
https://forum.xda-developers.com/t/trouble-rooting-umx-u683cl.4518007
Yes, that's my original post from back in November. That post is no longer my problem, though I will set your response there aside for when I hopefully get the phone to do anything besides fastboot.
it's clearly same topic, you must not open new thread. add your second post to previous one so mods can delete this thread.
It's clearly not. It's the same phone, but a different problem. The old post was seeking help with rooting it (and got no action, you may note), this one is about getting it out of fastboot mode so I can reset the damn thing and try again.
you bricked that device as a result of trouble with rooting. all info belongs to the previous thread, so others can read the history that caused this situation. I am not arguing any further here. answer in other thread and close this one.
somnomania said:
I've been getting help on this over at Hovatek, but it's extremely slow going; I first posted there on December 11 and it's still not resolved. This phone is a former Lifeline phone, and I've been trying to get it rooted so that I can use the Tello SIM I obtained. The problem the phone was having is that it refused to do any updates, so Tello's troubleshooting as to why it wasn't detecting the SIM was completely halted.
I did finally get to the point of rooting it. The major problem I have now is that it will only boot to fastboot mode. I can get it into recovery mode, but I get the dead android with "no connection" under it, and I've tried everything the internet has suggested to get past that, and it won't. Additionally, any fastboot command (apart from "fastboot devices") I try in ADB returns "FAILED (remote: 'unknown command'). I don't know how to get it into EDL mode from fastboot. I've tried every button combo possible, and the only one that does anything different is power + volume up, which changes it to a bright white screen. At this point I just want to do a hard reset so I can take another go at the rooting process, but the phone doesn't seem to want to allow me to. I would appreciate any help with this; I don't have a working phone at the moment because of these issues.
Click to expand...
Click to collapse
Here is the full firmware for the U683CL. Be sure to wipe the userdata and cache because I dumped the firmware from the same phone from a guy for $5 and it still has the guy's data and it contains pretty weird things...
BE SURE TO USE EDL CLIENT!
EDL CLIENT IS ONLY SUPPORTED ON LINUX SO MAKE A VIRTUAL MACHINE!
EDL CLIENT DOES NOT REQUIRE ANY RAWPROGRAM0.XML OR PATCH0.XML FILE!!
Link (I will make sure this link is never taken down and if it is, I'm reuploading the link no matter what): https://www.mediafire.com/file/js8ynkg8uum9ql0/u683cl_february_patch.zip/file