Related
Hi I'm trying to sideload the 5.0 lollipop update to my 2013 N7 using adb. I've downloaded the correct file. I have the correct drivers installed, and adb recognizes my N7 just fine. I am able to use the commands to get into the recovery. When I type in "adb sideload <filename.zip>" I keep getting the following message "the syntax of the command is incorrect" Any help would be great. My N7 is unrooted, stock recovery.
Thanks.
evltwn72 said:
Hi I'm trying to sideload the 5.0 lollipop update to my 2013 N7 using adb. I've downloaded the correct file. I have the correct drivers installed, and adb recognizes my N7 just fine. I am able to use the commands to get into the recovery. When I type in "adb sideload <filename.zip>" I keep getting the following message "the syntax of the command is incorrect" Any help would be great. My N7 is unrooted, stock recovery.
Thanks.
Click to expand...
Click to collapse
I didn't get that particular error last night when I tried, but I wa going from 5.0 to 5.0.1 and the sideload first told me the ADB version was too old (I was on 1.0.31 and needed 1.0.32 or something), then it told me that the file check failed (rooted, and non-stock recovery will do that).
I ended up using the factory image instead, which worked great.
Download the factory image, unzip it in your ADB folder and edit the flash-all.bat file. Remove the -w flag near the end of the file. This flag tells the script to wipe your user data, so removing it keeps your data. I did this for both 5.0 and 5.0.1 and all my data/apps/etc were fine.
Once you edit it, save it and double click it with the phone in the bootloader. Took about 2 minutes to flash mine, then about 10-15 minutes to optimize apps. I then ran Chainfire Auto Root and I was back in business. Whole process took about 20 minutes (optimizing apps being nearly all of that).
fury683 said:
I didn't get that particular error last night when I tried, but I wa going from 5.0 to 5.0.1 and the sideload first told me the ADB version was too old (I was on 1.0.31 and needed 1.0.32 or something), then it told me that the file check failed (rooted, and non-stock recovery will do that).
I ended up using the factory image instead, which worked great.
Download the factory image, unzip it in your ADB folder and edit the flash-all.bat file. Remove the -w flag near the end of the file. This flag tells the script to wipe your user data, so removing it keeps your data. I did this for both 5.0 and 5.0.1 and all my data/apps/etc were fine.
Once you edit it, save it and double click it with the phone in the bootloader. Took about 2 minutes to flash mine, then about 10-15 minutes to optimize apps. I then ran Chainfire Auto Root and I was back in business. Whole process took about 20 minutes (optimizing apps being nearly all of that).
Click to expand...
Click to collapse
Well I'm still having no luck. I already had the factory image, I tried what you recommended, and still no luck. Thanks for your help. :highfive: I guess I'll wait until Google decides to push it out. I did call them prior to my 1st post on here, and of course, they were not much help.
evltwn72 said:
Well I'm still having no luck. I already had the factory image, I tried what you recommended, and still no luck. Thanks for your help. :highfive: I guess I'll wait until Google decides to push it out. I did call them prior to my 1st post on here, and of course, they were not much help.
Click to expand...
Click to collapse
I followed this guide which worked great : http://www.androidpolice.com/2014/1...-0-factory-images-heres-how-to-get-around-it/
If you still get the error, maybe deinstall adb, drivers etc and try again
Sent from my Nexus 5 using XDA Free mobile app
chrismast said:
I followed this guide which worked great : http://www.androidpolice.com/2014/1...-0-factory-images-heres-how-to-get-around-it/
If you still get the error, maybe deinstall adb, drivers etc and try again
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
That was my next suggestion. If sideload and factory images aren't working, seems like it's a PC issue. Worth a shot.
My drivers are working just fine. I made sure they were update. I'm just gonna wait until I get the OTA update. Thanks for your help guys.
Sent from my HTC One M8 using XDA app
Well Google just pushed 5.0.1 to my N7. Happy days.
Sent from my Nexus 7 using XDA app
Hello,
First of all, Thanks for this great community. It has been helping me with my S4 for a long time.
Almost a year ago, I bought a fire phone for my younger brother. Today I tried to install the Custom Rom CM11 (which I successfully did), but, among the files in the proper thread, are 2 more files, the Google apps and also, a "flash wipe out". I did this in the end, expecting that just cleaned everything without touching the OS. Huge and novice mistake from miself. After almost 5 hours of looking for a solution, I realized that I don't have an OS and can only enter to "Fire phone recovery mode". I have downloaded almost 5 or 6 stock firmwares that are available to donwload here in XDA. Tried to download the OTA for an unlocked phone from amazon and tried to upload it to the phone via ABD tools. In the end, I always get the same errors: Not-signed and can't install it in the phone.
I'm going to be honest: I'm desperate.
In conlcusion:
1) No OS in a fire phone.
2) No custom TWRP.
3) I just have recovery mode
4) Been trying to install through ADB tools without any success the stock OTA update (the last one, since I had the 4.6.6 version)
Anything that can help will be well received.
Thanks in advance
Hello,
Have you tried ADB sideload when you go into your phone's recovery? And if you did, what did it say when you tried installing it? Try using this to sideload your phone.
Thanks for your answer @mechasnyper but I have tried that out as well
Hey, thanks for the answer. I really appreciate the time for doing it.
Yes, I have tried the ADB Sideload. The phone it's identified through the CMD (I get to see the serial) and then try the ADB Sideload. It doesn't work with bin files. It says unable to load. I tried also with the zip files that are posted here in the forums, being able to load then at 100% but the cell phone says "invalid signature", and for this couldn't install it over the fire phone.
lordofra said:
Hey, thanks for the answer. I really appreciate the time for doing it.
Yes, I have tried the ADB Sideload. The phone it's identified through the CMD (I get to see the serial) and then try the ADB Sideload. It doesn't work with bin files. It says unable to load. I tried also with the zip files that are posted here in the forums, being able to load then at 100% but the cell phone says "invalid signature", and for this couldn't install it over the fire phone.
Click to expand...
Click to collapse
Try sideloading using this file. https://www.androidfilehost.com/?fid=24052804347783512 I found this somewhere else and this is the file I used when I screwed up my ROM installation.
When I get home I'll try using that file that you have posted.
I'll update the results.
lordofra said:
When I get home I'll try using that file that you have posted.
I'll update the results.
Click to expand...
Click to collapse
Success?
Sorry for the delay. Been talking with centurylink because since yesterday I have no Internet service (Answering from the phone). No, no success at all.
lordofra said:
It says unable to load.
Click to expand...
Click to collapse
Your need free RAM on computer bigger than .bin size.
Hey, thanks for the answer.
I'm doing it on my laptop that has 8 Gb of ram. Just in case, I'm going to try it on my brother's laptop that has 16 gb of ram to test this out. But I doubt this will make a difference, since I've tried already many .bin files (all of them are unable to load an their size its 1.2 GB max. Many zip files as well where I have obtained 100% load but the firephone aborts the installation due to signature verification failure.
This is really strange. I have screwed up installing Cyanogenmod onto my phone, yet I was able to revert back to the stock ROM with just the stock recovery. I will have to look more into this. I will post again soon for updates. Have you wiped the data and cache?
EDIT: I am not sure if this will work, but try using this bin file. http://androidhost.org/o120v
@lordofra
Try (with quotes)
adb sideload "full_path_and_name_of_the_bin.bin"
I'm not the kind of person to ask for help if the answer to my problem might be out there already. I've followed relevant threads. I've searched XDA and googled. I've tried some things. I'm stuck.
I have an unlocked bootloader and FRP. When I go into Settings, OEM unlocking is greyed out. (Yes, I can use the phone.)
I do not have TWRP (anymore). I flashed stock recoveries.
I'm on build B101 and System Update is prompting my to update to B130. I can download it and, when prompted, reboot into recovery to update automatically.
I get to 100% and get the following error:
Software install failed!
Failed to check the update files.
Please download the package again.
Reboot system now
(See screenshot attached)
Now that it's available in Firmware Finder, I attempted to load B150 as well. Same thing.
I tried relocking bootloader, but it immediately prompts me to factory reset. After doing that, I get to reboot into recovery by default, other recovery by pressing the buttons, or fastboot via my PC.
Now, since we STILL don't have full firmware (supposed to have gotten it Friday, right?) I'm reluctant to use the images from here, especially if I'm not sure that would actually fix my issue.
What is going on with my software update? How do I fix this?
Did they actually release the BND-L24 firmware and no one noted it here?
Help, please!
Thanks.
johncro13 said:
I'm not the kind of person to ask for help if the answer to my problem might be out there already. I've followed relevant threads. I've searched XDA and googled. I've tried some things. I'm stuck.
I have an unlocked bootloader and FRP. When I go into Settings, OEM unlocking is greyed out. (Yes, I can use the phone.)
I do not have TWRP (anymore). I flashed stock recoveries.
I'm on build B101 and System Update is prompting my to update to B130. I can download it and, when prompted, reboot into recovery to update automatically.
I get to 100% and get the following error:
Software install failed!
Failed to check the update files.
Please download the package again.
Reboot system now
(See screenshot attached)
Now that it's available in Firmware Finder, I attempted to load B150 as well. Same thing.
I tried relocking bootloader, but it immediately prompts me to factory reset. After doing that, I get to reboot into recovery by default, other recovery by pressing the buttons, or fastboot via my PC.
Now, since we STILL don't have full firmware (supposed to have gotten it Friday, right?) I'm reluctant to use the images from here, especially if I'm not sure that would actually fix my issue.
What is going on with my software update? How do I fix this?
Did they actually release the BND-L24 firmware and no one noted it here?
Help, please!
Thanks.
Click to expand...
Click to collapse
I'm not certain why that happens, But I have a guess.
On each update that I have looked at, the recovery gets and update too. So different signatures and such.
Maybe the "stock" recovery you have re-flashed, is not correct version for your installed and update rom.
I cannot confirm this as I am missing the update app.
If you could help me with my missing files , I could help you with your update problem.
You could help me by pulling a list of packages installed so I can see what apps I have missing, and hopefully get them back (stock only, preferably done after a fresh factory reset.)
Directions for this on this thread.
See attached.
johncro13 said:
See attached.
Click to expand...
Click to collapse
thank you that helps.
I see I am missing an entire folder.
/data/hw_init
Could you see if it is accessible .
Code:
mkdir %userprofile%\Desktop\hw_init
adb pull /data/hw_init %userprofile%\Desktop\hw_init
I think it is not permitted though.
Uploaded. See referenced thread. I hope it helps!
johncro13 said:
Uploaded. See referenced thread. I hope it helps!
Click to expand...
Click to collapse
I will see what I can do with that. And hopefully can get past any file verification. And if I figure that out it should help you too.
Or , with my luck, the moment I figure it out , the stock firmware will come out.
I pushed the hw_init folder to /data while in twrp, then put stock recovery back(the version I expect should be correct) and I got same update failed error, as the OP.
That tells me maybe is probably some other reason , besides the version of stock recovery is causing this trouble.
Not sure if there is confirmation of successful update while bootloader is unlocked or not. Too late for me to try tonight, but next I will re-lock bootloader and try again.
My last (really current) phone needed to be re-locked in order to take updates.
**UPDATE**
re-locking bootloader did not help any at all. I still have error failed to check file, please download again.
On the manual update to oreo thread, they are using a "stock-ish" recovery named "no-check"
I am thinking I might flash that recovery to try and force this update to install.
BND-RECOVERY-NoCheck.img? Is that region-specific? Will it work with the BND-L24?
johncro13 said:
BND-RECOVERY-NoCheck.img? Is that region-specific? Will it work with the BND-L24?
Click to expand...
Click to collapse
tried it earlier today. Same error. will not finish update
johncro13 said:
BND-RECOVERY-NoCheck.img? Is that region-specific? Will it work with the BND-L24?
Click to expand...
Click to collapse
I have ordered a second 7x. I plan to pull the hw_init folder , and the remainder of /data that might be missing from this device , because of a result of formating it in twrp. I plan to restore that as an image, in hopes of getting updater to complete properly. And if that works, you will be able to use my backup and update your phone too.
If not , well , doesn't hurt to try.
I'm comparing the images pulled from my device and the images available for the Indian "return to stock thread. And I see the problem with the USA L24 version.
The cust.img for usa has no app folder.
It did not make sense to me before why there was apps only installed in /data. Because /data should be able to be fully wiped and your system will recreate the file structure. But The apps should have been on one of the images.
My second phone arrived today. I pulled the hw_init folder from it.
did a diff comparison on the updater app from the new phone and and the one that I had to apply patches to , to bring it up from b101 to b140. The result was 100% same.
and three more apps where in the hw_init folder as well. (bloat apps really)
now the bad news.
My original phone (the one that I had formatted /data on). Now has the same /data/hw_init folder as the brand new device. But always shows no update available.--It showed update once, the first time checked, install failed , now shows nothing available.
And the new phone does show an update available (B150) , but fails to install. Then after the failed install, now it shows no update available.
That's insane.
So... in summary, neither will update? Neither the original nor the unaltered brand-new device?
If anyone else has had this issue but has since resolved it, would you mind letting us know how? @mrmazak is working on it and I've also been told by the FUT team that I should expect some kind of communication from "Oscar Felix."
(If you've searched the forums for other Honor or Huawei devices, you probably already know that there is some speculation about whether or not Oscar Felix is a real person.)
I have the same problem but I'm stuck on update b140 and I can't even get the face unlock feature update. I was rooted with twrp recovery but now I have reinstalled the stock recovery and removed root
Sonny1732 said:
I have the same problem but I'm stuck on update b140 and I can't even get the face unlock feature update. I was rooted with twrp recovery but now I have reinstalled the stock recovery and removed root
Click to expand...
Click to collapse
Did you get the Oreo update today?
No I didn't, did you find out what can we do about this?
Is it a way I can update my phone manually
I'm watching this thread , myself. That might be the key.
Hopefully something comes up soon or is there a rom I can get if I reroot my phone?
I have an ATT version of Z2 Force edition, it came with Nougat 7.x something. Tried to do the Oreo update by following this guide to update via Lenovo Moto Smart Assist:
https://forum.xda-developers.com/z2-force/help/how-to-manually-update-att-motorola-z2-t3879143
During the Lenovo update, it went to 51%, it seems to be stuck, I thought it was waiting for something, so I looked at the phone screen. Being new to this phone, I saw the fastboot screen that had the up/down arrow and "Start". Unfortunately, i pushed the power button to "Start" thinking it was waiting for me to start something. Phone went into a bunch of reboots and said it can't boot. So then I followed this guide:
https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783
To hopefully return it to stock. The flash all utility went though its thing with Oreo zip file I downloaded, (I think I should have downloaded Nougat?) but it still wouldn't boot.
What correct step should I do next to restore it to stock before I screw it up further by following guides that I shouldn't be or following them wrong?
It also says the firmware is modified, would that return to stock (for warranty) if I flash it back to stock?
I was able to restore to stock via RSD_Lite_Motorola_XML_To_Batch_Script.zip, apparently the flashall utility might not flash all the files I needed. Or perhaps it was because I flashed Oreo on top of Nougat.
rcboosted said:
I was able to restore to stock via RSD_Lite_Motorola_XML_To_Batch_Script.zip, apparently the flashall utility might not flash all the files I needed. Or perhaps it was because I flashed Oreo on top of Nougat.
Click to expand...
Click to collapse
I am in a very similar boat, and have done most of what you have. Could you tell me what you did exactly to get RSD_Lite_Motorola_XML_To_Batch_Script.zip to work? I'm a little lost.
Rayravage said:
I am in a very similar boat, and have done most of what you have. Could you tell me what you did exactly to get RSD_Lite_Motorola_XML_To_Batch_Script.zip to work? I'm a little lost.
Click to expand...
Click to collapse
The zip you're talking about is an xml to batch script convertor, so you can flash in command prompt sans rsdlite. (No really uses rsd around here, and it has been known to cause more problems than fix.) In the 'How to Return to Stock' thread, there is a utilities.zip that has a flashall.bat to flash the firmware you have, but it was made for Sprint and TMO. ATT and such I believe have a couple of other things that are flashed and the flashall.bat doesn't cover it. So you use the convertor to convert the xml in your att firmware to a flashall.bat and you use that to flash your firmware.
Thanks, I got it sorted I believe. Problem was that the Moto Assistant sucks for updating, and that the flash process would fail until I plugged the phone in after starting the process.
Rayravage said:
I am in a very similar boat, and have done most of what you have. Could you tell me what you did exactly to get RSD_Lite_Motorola_XML_To_Batch_Script.zip to work? I'm a little lost.
Click to expand...
Click to collapse
I don't know if you got it or not, in case you didn't I'll just write up some quick steps for anyone else having similar issues.
1. unzip RSD_Lite_Motorola_XML_To_Batch_Script.zip to a folder
2. unzip the image from one of the depots
3. move all of the files (go into the folders until there are no more folder) to folder created in step 1, making sure they're at the same level as the .bat files in step 1.
4. run one of the bat files 1, 2 or 3. I used 2.
5. use the resulting bat file in step 4 to flash phone after you get it into fastboot mode.
6. use volume button on phone to get to "Bootloader log" to make sure all activity have ceased before rebooting. (can't remember if it auto reboots or not.)
post seems to be showing up late after posting.
When I did my update with the Moto assistant, mine seemed to hang at 51% for a bit, so I opened the bootloader logs while it was still plugged in to make sure it was actually doing something and the logs kept updating meaning it was copying files and whatnot. So be patient with the process when it's at 51% and it should work, but I also know others have had issues with it working so ya know...
Thanks in advance if anyone can help me with this.
I tried to root my phone via Magisk using a tutorial on YouTube. I noticed after Magisk had patched the boot.img it reduced in size from around 65MB to 30MB, which seemed odd. Flashed it, and phone became stuck in a boot loop. I tried to use fastboot to put the original boot.img back, and ended up being told the system was corrupted.
Thought I would just flash the factory firmware back on to the phone - however, that is failing partway through, when it tries to flash vendor.img, with an error "write to device failed in SendBuffer()"
I've tried multiple different versions of ADB and Fastboot, from HighOnAndroid and Google, tried flashing from a different laptop, but it fails at the same point regardless. The only thing I haven't been able to try is a different cable, but it would seem odd if that was the cause?
My device was originally on Bonito 10.0.0 (QQ1A.191205.011, Dec 2019) - I've tried to flash that back, and also tried 10.0.0 (QQ1A.200105.002, Jan 2020), neither of them working.
I'm using ADB and Fastboot from the Platform Tools at https://developer.android.com/studio/releases/platform-tools - a lot of posts I've read talk about "installing ADB and Fastboot", but they're just executables that run fine without any installation, unless I'm missing something.
Does anyone have any ideas of what I could try please?
Same old story - different cable, different port, worked.
I also suspect that the platform tools were not compatible with QQ1A.200105.002, Jan 2020, since the one I successfully managed to flash in the end was the December version.
Since I changed both cable and version at the same time, I can't say which one it was.
Hope this helps someone else.
smimon said:
Same old story - different cable, different port, worked.
I also suspect that the platform tools were not compatible with QQ1A.200105.002, Jan 2020, since the one I successfully managed to flash in the end was the December version.
Since I changed both cable and version at the same time, I can't say which one it was.
Hope this helps someone else.
Click to expand...
Click to collapse
I wonder if this is why Magisk Installer doesn't like my boot image, consequently failing to patch it.
clayndwoods said:
I wonder if this is why Magisk Installer doesn't like my boot image, consequently failing to patch it.
Click to expand...
Click to collapse
Known issue with Cannery Channel. Try latest Stable. Also checkout Magisk thread.
Android
I figured it out. I was trying to patch the wrong file, apparently.
I'm a bit concerned, though, as the patched file is 29.6Mb and the orignal boot.img is around 60Mb.
I don't want to hose this phone, has I just got it as a replacement from Google. I tried sideloading the Android 10 update using TWRP (my original phone had TWRP and Magisk installed) and bricked the phone. Well, not exactly bricked. It was stuck in recovery, the only thing that would work was the bar code display.
You never know what you like so much about the pixel until you have to use a Samsung while waiting for your replacement Pixel to arrive. I can't survive without call screening LOL!
clayndwoods said:
Android
I figured it out. I was trying to patch the wrong file, apparently.
I'm a bit concerned, though, as the patched file is 29.6Mb and the orignal boot.img is around 60Mb.
Click to expand...
Click to collapse
The patched file is normally smaller than the stock boot.img. That's OK and expected.