Related
Hi,
I installed a while ago 4.3 GE (rooted) for OTA updates. Everything seemed fine. Today i got the 4.4 OTA update so OTA does work. I rebooted the phone so it could install. The installation stopped after a while and gives the error: no command. After 30 seconds it reboots and gives this error again. Over and over again
I did not make a backup of my data on the phone. The default recovery mode is not available, this also gives the no command error. Fastboot does work.
I'm S-OFF and LOCKED.
What to do?
Someone got this working with Nexus 7 2012. But i need the OTA 4.4 file and ADB sideload needs to work...
Are you able to unlock bootloader using fastboot oem unlock ?
SaHiLzZ said:
Are you able to unlock bootloader using fastboot oem unlock ?
Click to expand...
Click to collapse
Yes, i used the unlockcode. Created a new one via htcdev. Bootloader is now unlocked. Try to reflash 4.3 recovery, flash is ok but still can't start recovery. I wanted to try to start normal recovery and use adb sideload to transfer files from sd to pc. Also tried to flash twrp and CWM but found no solution to transfer my files?
Try fastboot boot customrecovery.img
Also once you are in recovery, your device will show up under adb devices. Then you can adb push yourromname.zip /data/media/
SaHiLzZ said:
Try fastboot boot customrecovery.img
Also once you are in recovery, your device will show up under adb devices. Then you can adb push yourromname.zip /data/media/
Click to expand...
Click to collapse
Which customrecovery? Can i also transfer my data (pictures?) from sd to pc?
Use CWM if you wish.. http://forum.xda-developers.com/showthread.php?t=2173863
You have to use adb pull /data/media/DCIM/ if your pics are stored in DCIM folder.
This is DEPENDENT on your phone connecting and responding to ADB..
SaHiLzZ said:
Use CWM if you wish.. http://forum.xda-developers.com/showthread.php?t=2173863
You have to use adb pull /data/media/DCIM/ if your pics are stored in DCIM folder.
This is DEPENDENT on your phone connecting and responding to ADB..
Click to expand...
Click to collapse
OK thank you, i will try this tomorrow. I also found how to enable USB debugging through CWM . I think i will need that too.
I wouldn't do that. I have no idea what will it do to your phone. If you are not sure of ADB commands you can get in a bind. Unless you are doing a crash course on ADB&Fastboot tonight?
SaHiLzZ said:
I wouldn't do that. I have no idea what will it do to your phone. If you are not sure of ADB commands you can get in a bind. Unless you are doing a crash course on ADB&Fastboot tonight?
Click to expand...
Click to collapse
Ok, i only will try to do that when ADB not works. I think ADB only works when USB debugging is enabled in Android. But i can't start Android.
What do i have to start in CWM to use ADB?
mderksen said:
Ok, i only will try to do that when ADB not works. I think ADB only works when USB debugging is enabled in Android. But i can't start Android.
What do i have to start in CWM to use ADB?
Click to expand...
Click to collapse
Same trouble here? Have you figured it out yet?
bluestar23 said:
Same trouble here? Have you figured it out yet?
Click to expand...
Click to collapse
ADB was working, but i could not get my files off the phone. Tried to transfer files with ADB but it could not find the directories. So i gave up and i just flashed the 4.4 (non-root) RUU. The phone is working now but i lost my files
mderksen said:
ADB was working, but i could not get my files off the phone. Tried to transfer files with ADB but it could not find the directories. So i gave up and i just flashed the 4.4 (non-root) RUU. The phone is working now but i lost my files
Click to expand...
Click to collapse
You are lucky. I relocked it... So as of now, I cannot even flash TWRP for any rom...
mderksen said:
Hi,
I installed a while ago 4.3 GE (rooted) for OTA updates. Everything seemed fine. Today i got the 4.4 OTA update so OTA does work. I rebooted the phone so it could install. The installation stopped after a while and gives the error: no command. After 30 seconds it reboots and gives this error again. Over and over again
I did not make a backup of my data on the phone. The default recovery mode is not available, this also gives the no command error. Fastboot does work.
I'm S-OFF and LOCKED.
What to do?
Someone got this working with Nexus 7 2012. But i need the OTA 4.4 file and ADB sideload needs to work...
Click to expand...
Click to collapse
Paste your getvar all
I derped hard by working on my phone late at night. I accidentally wiped internal storage in TWRP and couldn't get ADB sideload to work. I've tried pushing files in NRT, flashing stock + unroot... nothing seems to work.
I then tried flashing the stock image using the instructions on Google's image download page. The command prompt said for security reasons I should re-lock the bootloader, and I did in my sleepy ways. DOH!
Now I can get into the bootloader and TWRP, but sideload isn't working. When I type fastboot devices in the bootloader, my device shows up. Same with TWRP, until I go into Advanced > ADB sideload, then my device suddenly isn't listed. I am using TWRP 2.8.5.0. Is this a bug? I updated ADB binary to the latest version.
Am I totally screwed or is there something I can try before begging google to fix this?
You tried using Nexus Toolkit and select soft-brick to restore phone? Ive ran it a few times and always works for me, will pull latest SW and get it all set up again. After flash just unlock BL and root.
Unless I'm not understanding you correctly:
Since you've locked your bootloader i do believe the acronym SOL applies...
Didgeridoohan said:
Unless I'm not understanding you correctly:
Since you've locked your bootloader i do believe the acronym SOL applies...
Click to expand...
Click to collapse
I believe he is too but I swear I saw a thread somewhere here Motorola had a method for getting out of this. I would search XDA harder
Sent from my Google N6 on VZ
SurlyGnex said:
I derped hard by working on my phone late at night. I accidentally wiped internal storage in TWRP and couldn't get ADB sideload to work. I've tried pushing files in NRT, flashing stock + unroot... nothing seems to work.
I then tried flashing the stock image using the instructions on Google's image download page. The command prompt said for security reasons I should re-lock the bootloader, and I did in my sleepy ways. DOH!
Now I can get into the bootloader and TWRP, but sideload isn't working. When I type fastboot devices in the bootloader, my device shows up. Same with TWRP, until I go into Advanced > ADB sideload, then my device suddenly isn't listed. I am using TWRP 2.8.5.0. Is this a bug? I updated ADB binary to the latest version.
Am I totally screwed or is there something I can try before begging google to fix this?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3059518
Try this.
Sent from my Nexus 6
Casper34 said:
http://forum.xda-developers.com/showthread.php?t=3059518
Try this.
Sent from my Nexus 6
Click to expand...
Click to collapse
To be more specific, this isn't actually a fox for this issue but the guy in the last post as of now, reckons he managed to somehow get KT working. Though I'm skeptical
I was trying to sideload the new update and something wen wrong and it stopped updating. I tried to boot it up but now its just in a bootloop. I am completly stock and don't have TWRP. Is their a way to force unlock bootloader?
win465 said:
I was trying to sideload the new update and something wen wrong and it stopped updating. I tried to boot it up but now its just in a bootloop. I am completly stock and don't have TWRP. Is their a way to force unlock bootloader?
Click to expand...
Click to collapse
without enabling oem unlock in the developer options, nope. but you can use the stock recovery to check if a factory reset would help.
Factory reset doesn't help. When trying to sideload I keep getting error "system partition has unexpected contents" (Status 7).
win465 said:
Factory reset doesn't help. When trying to sideload I keep getting error "system partition has unexpected contents" (Status 7).
Click to expand...
Click to collapse
Had you unencrypted?
Yes, but i flashed backed to stock kernal.
win465 said:
Yes, but i flashed backed to stock kernal.
Click to expand...
Click to collapse
How?
Using the nexus tool kit. After that I locked the bootloader to sideload the update.
win465 said:
Using the nexus tool kit. After that I locked the bootloader to sideload the update.
Click to expand...
Click to collapse
Were you rooted before all of this too?
Nope
Evolution_Tech said:
Were you rooted before all of this too?
Click to expand...
Click to collapse
Nope
win465 said:
Nope
Click to expand...
Click to collapse
Then the toolkit most likely didn't replace the proper kernel, which is why the OTA failed. You'll have to RMA.
Evolution_Tech said:
Then the toolkit most likely didn't replace the proper kernel, which is why the OTA failed. You'll have to RMA.
Click to expand...
Click to collapse
Thank you for your help
Which toolkit did you use? Try to flash everything in BOOTLOADER with the newest 5.1.1 using ADB and Fastboot commands as opposed to the Toolkits. I'm hoping your successful in your endeavours, I'm working on mine too. Even if you are missing any part of your stock image or basic partitions, you should be able to flash it back to normal via your bootloader. I had a similar issue with my Nexus 5, last week, actually.
EDIT: So, when you sideload or fastboot the system partition, it's stopping you? I may have sleep induced stupidity here and not fully taking in the issue but, I was able to flash 5.1.0 on my Nexus 5 after re-locking it via fastboot commands.
RedHazy said:
Which toolkit did you use? Try to flash everything in BOOTLOADER with the newest 5.1.1 using ADB and Fastboot commands as opposed to the Toolkits. I'm hoping your successful in your endeavours, I'm working on mine too. Even if you are missing any part of your stock image or basic partitions, you should be able to flash it back to normal via your bootloader. I had a similar issue with my Nexus 5, last week, actually.
Click to expand...
Click to collapse
Not when his bootloader is locked. Unfortunately, the OP has locked his bootloader and can't boot to android to enable OEM unlock.
Possible idea
Evolution_Tech said:
Not when his bootloader is locked. Unfortunately, the OP has locked his bootloader and can't boot to android to enable OEM unlock.
Click to expand...
Click to collapse
There's some more concrete info in the first couple pages, especially regarding our N6's:
http://forum.xda-developers.com/nexus-9/help/to-toggle-allow-oem-unlock-via-fastboot-t3091119
Hope this helps.
I'll keep my eyes open for anything that seems pertinent.
Best of luck
RedHazy said:
Which toolkit did you use? Try to flash everything in BOOTLOADER with the newest 5.1.1 using ADB and Fastboot commands as opposed to the Toolkits. I'm hoping your successful in your endeavours, I'm working on mine too. Even if you are missing any part of your stock image or basic partitions, you should be able to flash it back to normal via your bootloader. I had a similar issue with my Nexus 5, last week, actually.
EDIT: So, when you sideload or fastboot the system partition, it's stopping you? I may have sleep induced stupidity here and not fully taking in the issue but, I was able to flash 5.1.0 on my Nexus 5 after re-locking it via fastboot commands.
Click to expand...
Click to collapse
I get this error message "system partition has unexpected contents" (Status 7).
win465 said:
I was trying to sideload the new update and something wen wrong and it stopped updating. I tried to boot it up but now its just in a bootloop. I am completly stock and don't have TWRP. Is their a way to force unlock bootloader?
Click to expand...
Click to collapse
Can you fastboot boot twrp recovery? And if that is possible, will twrp flash zips with a locked bootloader?
Edit: I'm almost certain fastboot boot recovery won't work with a locked bootloader. I almost thought I had a good idea.
I am in the same situation. Bootloader locked and no custom recovery nor adb enabled. surprisingly enough, yesterday my phone could boot up but it's stuck now in the configuration process. I cannot access to the settings so I can check usb debugging or oem unlock. I can only access the dialer. my question is: is there anyway to do that with just a dialer code?
Just to clarify: you never need to relock your bootloader! Unless you have some kind of security restrictions from the company you work with or something, just don't!
OTA can be installed even with the bootloader unlocked (normal or sideload). The only prerequisite is that the system is stock (not rooted, stock kernel, stock recovery, and so on).
Didgeridoohan said:
Just to clarify: you never need to relock your bootloader! Unless you have some kind of security restrictions from the company you work with or something, just don't!
OTA can be installed even with the bootloader unlocked (normal or sideload). The only prerequisite is that the system is stock (not rooted, stock kernel, stock recovery, and so on).
Click to expand...
Click to collapse
Sorry for the noob question but where can I find these OTAs and how to install one of them? Does it require usb debugging to be enabled?
I need assistance as the title says. First up my bootloader is not unlockable, (believe me I've tried) and here is my situation. I cannot flash the next OTA, because of failed error in recovery upon trying to install. There is no full firmware to reflash the device, only an OTA that I obtained (and yes it is completely for my phone model) (XT1925DL). I would sideload the OTA or apply it from sdcard in the recovery, however the device is not detected on Windows via adb or on linux, after hitting the sideload zip option, and Sdcard cannot mount. I get (sdcard failed to mount, E: installation aborted in recovery). If someone knows an option to maybe allow me to use the OTA file to repatch the system, without having to resort to the recovery mode, or adb sideload option, it would be appreciated if you could help.
hydroman202 said:
I need assistance as the title says. First up my bootloader is not unlockable, (believe me I've tried) and here is my situation. I cannot flash the next OTA, because of failed error in recovery upon trying to install. There is no full firmware to reflash the device, only an OTA that I obtained (and yes it is completely for my phone model) (XT1925DL). I would sideload the OTA or apply it from sdcard in the recovery, however the device is not detected on Windows via adb or on linux, after hitting the sideload zip option, and Sdcard cannot mount. I get (sdcard failed to mount, E: installation aborted in recovery). If someone knows an option to maybe allow me to use the OTA file to repatch the system, without having to resort to the recovery mode, or adb sideload option, it would be appreciated if you could help.
Click to expand...
Click to collapse
Is it a TracFone? You're probably going to have to flash in Fastboot.
Download the most recent firmware here:
https://mirrors.lolinet.com/firmware/moto/ali/official/TRAC/
And use this guide to flash:
https://forum.xda-developers.com/moto-g6/how-to/guide-faster-updated-guide-to-root-t3914228
Ragarianok said:
Is it a TracFone? You're probably going to have to flash in Fastboot.
Download the most recent firmware here:
https://mirrors.lolinet.com/firmware/moto/ali/official/TRAC/
And use this guide to flash:
https://forum.xda-developers.com/moto-g6/how-to/guide-faster-updated-guide-to-root-t3914228
Click to expand...
Click to collapse
I appreciate the response. Unfortunately that site is not up to date with the TracFone firmware. The latest official one I have. And I can't flash it unfortunately because I'm on a newer firmware and it throws security downgrade errors when I try. If I could figure out how to get recovery mode to show up on my pc I would be ok.... Then I would be able to apply the OTA I need for the next one to complete successfully.
hydroman202 said:
I appreciate the response. Unfortunately that site is not up to date with the TracFone firmware. The latest official one I have. And I can't flash it unfortunately because I'm on a newer firmware and it throws security downgrade errors when I try. If I could figure out how to get recovery mode to show up on my pc I would be ok.... Then I would be able to apply the OTA I need for the next one to complete successfully.
Click to expand...
Click to collapse
Have you tried to run those Fastboot commands without:
Code:
[I]fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img[/I]
Should work if you exclude those two; that's what I did to downgrade from Pie back to Oreo.
You could also try Lenovo Moto Smart Assistant.
I just realized that I totally misread your original post and, man, I feel like a total dummy.
Is the OTA currently on the root of your phone's internal storage?
If it's an actual update.zip file and it's in the root of your internal storage, you could try going into Settings/Apps & notifications/Apps info (tap the down arrow and select Show system)/Moto Update Services and make sure that Storage permission is toggled on. After that, try to perform an update.
I had a similar error when trying to sideload with ABD and update from SD in recovery, but it turned out that I was trying to update using full firmware.
Can you link the update file you have?
Ragarianok said:
I just realized that I totally misread your original post and, man, I feel like a total dummy.
Is the OTA currently on the root of your phone's internal storage?
If it's an actual update.zip file and it's in the root of your internal storage, you could try going into Settings/Apps & notifications/Apps info (tap the down arrow and select Show system)/Moto Update Services and make sure that Storage permission is toggled on. After that, try to perform an update.
I had a similar error when trying to sideload with ABD and update from SD in recovery, but it turned out that I was trying to update using full firmware.
Can you link the update file you have?
Click to expand...
Click to collapse
Unfortunately I cannot not link it but the file size of the ota is roughly 1.47 GB. And the ota was a upgrade to pie. I'm still on that one. Needing to reflash it so I can correct a partition issue. That's preventing the next ota from succeeding. The reason the next one doesn't succeed is because it checks the modem partition and it unfortunately fails to verify it because I accidentally flashed the wrong one. The ota should patch the modem in the device now I'm thinking because the modem that is currently on the device is the one before the ota arrived. All other partitions are the ones meant for the current firmware.
hydroman202 said:
Unfortunately I cannot not link it but the file size of the ota is roughly 1.47 GB. And the ota was a upgrade to pie. I'm still on that one. Needing to reflash it so I can correct a partition issue. That's preventing the next ota from succeeding. The reason the next one doesn't succeed is because it checks the modem partition and it unfortunately fails to verify it because I accidentally flashed the wrong one. The ota should patch the modem in the device now I'm thinking because the modem that is currently on the device is the one before the ota arrived. All other partitions are the ones meant for the current firmware.
Click to expand...
Click to collapse
Hm.
You could try to use the Lenovo Moto Smart Assistant. It has a Rescue option that returns the phone to stock firmware. It also has an Upgrade option; I've tried it but there aren't any updates for my phone. You could Rescuing and then Upgrading. Or you could Rescue and then try the OTA again.
The only downside is that everything on your phone's internal storage will be erased.
my main reason for getting a pixel phone is so I could always be on the latest version of Android for security reasons. I know that OTA updates will not work as seamlessly when I'm rooted.
My question is, how can I update my phone while being rooted, and not losing any of my user data and media?
EDIT: Answer
How to sideload OTA and keep your user data/media!
download OTA image from
https://developers.google.com/android/ota
adb reboot recovery
The device is now in recovery mode and an Android logo with red exclamation mark should appear on screen.
To access the recovery menu, hold the Power button and press Volume Up once. The recovery text menu will appear.
To enter sideload mode, select the option Apply update from ADB.
adb devices
adb sideload ota_file.zip
where ota_file.zip is the name of the file you have downloaded and verified.
Assuming all goes well, it’ll soon run through “Installing update…” and 2 steps. If you grabbed the correct file for your phone, it should complete and finish properly by saying “Install from ADB completed with status 0.” This message will ONLY appear on your phone. On ADB, it will say "(~94%) adb: failed to read command: No error" This is normal!
reboot back into system to finalize update.
Re-Root
adb reboot fastboot
fastboot flash boot magisk_patched.img
xT29c said:
my main reason for getting a pixel phone is so I could always be on the latest version of Android for security reasons. I know that OTA updates will not work as seamlessly when I'm rooted.
My question is, how can I update my phone while being rooted, and not losing any of my user data and media?
Click to expand...
Click to collapse
Don't take my advice.
But, from the steps I was told to perform was :
From within magisk manager, restore images. Not complete uninstall. Afterwards, Don't reboot. Then, head over to the update section of settings and update. Then , pretty sure , install magisk again. Then, reboot.
When you say reinstall magisk again? Are you talking about the APK file or flashing the patched boot.image file?
when I go to the update section, it's not finding the November OTA that was just pushed out today. Am I able to side load the update with ADB and still retain all user data?
Did it myself. Here's my guide. Enjoy.
How to sideload OTA and keep your user data/media!
download OTA image from
https://developers.google.com/android/ota
adb reboot recovery
The device is now in recovery mode and an Android logo with red exclamation mark should appear on screen.
To access the recovery menu, hold the Power button and press Volume Up once. The recovery text menu will appear.
To enter sideload mode, select the option Apply update from ADB.
adb devices
adb sideload ota_file.zip
where ota_file.zip is the name of the file you have downloaded and verified.
Assuming all goes well, it’ll soon run through “Installing update…” and 2 steps. If you grabbed the correct file for your phone, it should complete and finish properly by saying “Install from ADB completed with status 0.” This message will ONLY appear on your phone. On ADB, it will say "(~94%) adb: failed to read command: No error" This is normal!
reboot back into system to finalize update.
Re-Root
adb reboot fastboot
fastboot flash boot magisk_patched.img
xT29c said:
Did it myself. Here's my guide. Enjoy.
How to sideload OTA and keep your user data/media!
download OTA image from
https://developers.google.com/android/ota
adb reboot recovery
The device is now in recovery mode and an Android logo with red exclamation mark should appear on screen.
To access the recovery menu, hold the Power button and press Volume Up once. The recovery text menu will appear.
To enter sideload mode, select the option Apply update from ADB.
adb devices
adb sideload ota_file.zip
where ota_file.zip is the name of the file you have downloaded and verified.
Assuming all goes well, it’ll soon run through “Installing update…” and 2 steps. If you grabbed the correct file for your phone, it should complete and finish properly by saying “Install from ADB completed with status 0.” This message will ONLY appear on your phone. On ADB, it will say "(~94%) adb: failed to read command: No error" This is normal!
reboot back into system to finalize update.
Re-Root
adb reboot fastboot
fastboot flash boot magisk_patched.img
Click to expand...
Click to collapse
Hi, thanks for the guide! When re-rooting, which image should I choose to patch in magisk? The old one, or the OTA image (is that a full image)?
Michael1200 said:
Hi, thanks for the guide! When re-rooting, which image should I choose to patch in magisk? The old one, or the OTA image (is that a full image)?
Click to expand...
Click to collapse
I used the old one. I believe the OTA does not change the boot.img file, since it isn't included in the download. If it did change it, I'm sure I would have semi-bricked my phone. lol.
xT29c said:
I used the old one. I believe the OTA does not change the boot.img file, since it isn't included in the download. If it did change it, I'm sure I would have semi-bricked my phone. lol.
Click to expand...
Click to collapse
Thanks, so basically re-rooting is the exact same procedure as rooting it the first time, right?
Michael1200 said:
Thanks, so basically re-rooting is the exact same procedure as rooting it the first time, right?
Click to expand...
Click to collapse
That's exactly right.
Never use OTA. I prefer use the full image for update without data loss. Little more commandes to type but it's better for me
nico22320 said:
Never use OTA. I prefer use the full image for update without data loss. Little more commandes to type but it's better for me
Click to expand...
Click to collapse
Please explain to yourself
xT29c said:
Please explain to yourself
Click to expand...
Click to collapse
look here https://www.youtube.com/watch?v=fYib1WNr2I8&t=32s
i always use this channel for my update. it's simple.
nico22320 said:
look here
&t=32s
i always use this channel for my update. it's simple.
Click to expand...
Click to collapse
No. I would like to know why you go through the trouble of flashing the entire factory image versus just the OTA file instead?
I do not know. since i got nexus 5, i've always learned how to update like this. moreover all the posts that I looked on the internet say that there is more risk to flash the OTA file than the factory image so..
That's it ?