An update to Android 12 has been released. Everything seems to be fine. Random reboots appeared.
I tried a full reset of nothing, then downloaded the OTA via adb sideload in the hope that it helps, but to no avail.
And it's sad that the bootloader is locked
device verizon.
Screenshot shows adb sideload error
Who knows what can be done, please tell me.
-------------------------------
After 3 long days of agonizing and torturing Google support, no help from them
Found the adb rescue install file.zip command, in their source code
Because I had coral-ota-sp1a.210812.015 firmware, I needed verizon firmware, for me coral-ota-sp1a.210812.016.a1-37be0022 didn't work, it didn't start
But with this coral-ota-sp1a.211105.002.a1-0939d2dd everything is fine
The main thing is to have the usb cable intact. And the pc connector usb 2.0
1. Go into bootloader
2. Select Rescue mode
3. type in the following words at the command line
adb rescue install file_name.zip
All should go through without errors
May help someone
Sorry for my English.
Related
I started to root my phone this morning. I did the HTVDev unlock, flashed twrp, then tried to flash viperboy's disable RW system protect. This caused my phone to just hang at the HTC screen. I let my phone die and was able to get into my bootloader and fastboot. I tried to push the rom via adb but I kept getting the error of no device connected. Then i tried to flash the stock boot.img though fastboot. This brought me back to the HTC screen but now when I plug it in to my computer it shows up for everything and it installs drivers but the HTC MTP Device fails. Now I cant send commands to reboot through fastboot or adb. Im currently waiting for it to die again to get back to twrp or the bootloader. Any advice on how to proceed?
Thanks,
Paris6906
Paris6906 said:
I started to root my phone this morning. I did the HTVDev unlock, flashed twrp, then tried to flash viperboy's disable RW system protect. This caused my phone to just hang at the HTC screen. I let my phone die and was able to get into my bootloader and fastboot. I tried to push the rom via adb but I kept getting the error of no device connected. Then i tried to flash the stock boot.img though fastboot. This brought me back to the HTC screen but now when I plug it in to my computer it shows up for everything and it installs drivers but the HTC MTP Device fails. Now I cant send commands to reboot through fastboot or adb. Im currently waiting for it to die again to get back to twrp or the bootloader. Any advice on how to proceed?
Thanks,
Paris6906
Click to expand...
Click to collapse
Likely no need to let it die -- a hard reset (hold the power and vol down for a very long time) should bring you back to the bootloader (hopefully). It'll seem like a good long while -- keep pressing.
From there, select 'fastboot' and press the power button, then plug in to your computer (USB). That'll show USB on the fastboot line.
Then, on your computer, open a command window (presuming you're using Windows) in the SDK platform-tools directory and type:
fastboot devices
If that gives back your device ID, you're at least at a reasonable fastboot. I'd flash a good recovery (I use PhilZ, and while it might be foreign to you (CWM style), it lets you load a ROM via OTG cable over USB if you have such a cable -- if not, hopefully sideload works for you in TWRP if you stick with that) -- just to be sure you have a good recovery.
Then, reboot into recovery.
Your kernel (boot.img) apparently is garbage, so hopefully you can either put a ROM on USB and flash from that (OTG) or adb sideload it. All the ROMs normally have a good kernel so would flash your boot.img properly during install. Were me me, I'd flash O.M.J's stock rooted ROM just so you at least get back to some place of sanity).
If that all fails, you might have to RUU and start over.
Let us know and we'll help out.
If that gives back your device ID, you're at least at a reasonable fastboot. I'd flash a good recovery (I use PhilZ, and while it might be foreign to you (CWM style), it lets you load a ROM via OTG cable over USB if you have such a cable -- if not, hopefully sideload works for you in TWRP if you stick with that) -- just to be sure you have a good recovery.
ok. can you use adb push in fastboot? also i noticed that my captive buttons blink when i tried to turn off my phone. don't know if that means anything.
OMG it worked! Thank you so much. I uber appreciate it. Today I learned a ton about how android works and how to use adb and fastboot. While the processed about gave me a heart attack i did learn a lot. I can not believe how great of a resource xda is. The knowledge of everyone on here is incredible. I cant thank you enough.
Thanks all,
Paris6906
Hey guys, I am new to this gear live dev and I want to help out. I just got my gear a few days ago and I'm still playing with it I figured that my device is at 5.0.1 and has Dev-Key in the build number. I went ahead and did some research (more than 35 hours) and came to a conclusion. I figured I can help a lot of people by posting my method here. I am currently on 5.0.2 and I am trying to figure out why I still did not get the 5.1.1 update. Looks like Samsung is slow and I will ask around if anyone got the OTA or I'll sideload the OTA scripts. Making the long story short.
Entering the bootloader (hard way)
Press and hold down the power button until your device reboots. Don't let go yet. As soon as you see the Samsung logo you have to swipe from the top left corner to bottom right corner really fast 2 times. Now let go of the power button and you should be in bootloader. If not keep trying again. I would recommend this as the last resort.
Entering bootloader (easy way):
Enable USB debugging by going to settings -> about device -> tapping build number 7 times. A new option should now show up under settings called developer options. At this point make sure that you have proper adb fastboot drivers. If not you can use the minimal ADB FASTBOOT 15 second Installer I will provide a link to the thread. Make sure that the watch is paired with your phone and keep the phone near you. Connect the watch to your machine via USB and let it recognize the device. Open a terminal or cmd window and enter adb devices. You will most likely be returned with some number and unauthorized. At this step if you get an error such like ADB is not an executable program then you have not installed ADB correctly. Switching over to your phone you will now see a debugging request from your watch. Go ahead and it always allow. Now you have granted debug permissions on you watch. Run the command again and this time, the device should return authorized. Run " adb reboot bootloader ". You will be taken to the bootloader.
Unlocking Bootloader and Flashing and relocking the bootloader:
The first step is to unlock the bootloader (don't know if this voids the warranty but I think it will). After you unlock the bootloader (fastboot oem unlock) WARNING: THIS WILL WIPE YOUR DEVICE and then boot back to the OS set it up and redo the steps under Entering bootloader. Once you have entered the bootloader you will need the stock os which is KMV78Y_stock. It is 4.4w and we will upgrade it soon. Open a cmd and run fastboot devices and you should see your device in the list. If not something is wrong , check if you have the right fastboot drivers and your watch is connected properly. Try a different usb port and don't use a usb HUB. ON WINDOWS extract the zip and navigate to the folder till you see the image files. Here shift+right click and you should see an option for open command windows here. For rest of the other people without windows cd to where the image files exist. Run the command “fastboot flash system system.img ” and “ fastboot flash boot boot.img ” . Once you have done that you will have to relock the bootloader. Relocking the bootloader is an important step to receiving further updates so I recommend relocking it. IF YOU DON'T RELOCK THE BOOTLOADER THEN YOU ARE STUCK ON 4.4W WHICH SUCKS SOOOO MUCH!!!!. Relock the bootloader by running “ fastboot oem lock “. Just keep in mind that you can re-unlock your bootloader after you have upgraded but unlocking bootloader will wipe your device again. *SIGH* I ALSO HATE READING LONG INSTRUCTIONS BUT YOU ARE ALMOST AT THE END!!!. After you relock your bootloader go ahead and swipe down on the screen until you highlight the recovery option and swipe right to select. Once you have booted into recovery you will see a warning sign. Don't Panic. Just tap on the screen and you will be brought to the recovery screen once again select reset and select yes.After the reset go ahead and reboot the device. You will be brought into the android wear stock os. Go ahead and set up your device again and go to the setting ->about device -> software updates. You will see that the update is available. There you go install the updates until you get to android 5.0.2. GREAT YOU HAVE UPGRADED YOUR WATCH. There a few ways to get to 5.1.1 but I have not tried them out. I will post the instructions as soon as I have tried it. If your watch says that there is an update the go ahead and install it. Samsung does not push the update to all users at once as it may kill their servers but roll the update out in batches. If you want to sit tight and wait till it comes through or I will be posting a how to soon.
UPDATING TO 5.1.1 AND TO 6.0
Hey, figured out how we can upgrade without waiting. It is actually really simple and easy. You will need to have a locked bootloader to do this or apply any stock update. It does not work with an unlocked bootloader. Your computer will not recognize your watch when sideloading if you have an unlocked bootloader. So let's get started. Download the ota update zip from the links below leave it in the downloads or move it wherever you want it. Open a terminal window or cmd window to the location of the zip either by shift+rightclick (only windows) or by cd’ing you way. At the location of the zip prepare your watch for sideloading. Reboot to recovery by commanding “ adb reboot recovery” or “ adb reboot bootloader” then going to recovery, or going to fastboot the hard way then to recovery. The choice is yours. Once you are in recovery select adb sideload. Now go back to your computer and hit " adb devices ". You should see your device and sideload. If not then something is wrong. Since you are already in the folder where the zip exists simply enter “adb sideload LIVE.zip” and it should send the file to devise. Don't panic if you interrupt the transfer. It will not apply the changes until the entire file has been transferred. Just redo the steps above to resend it. After the update is complete you can restart your device. Upon restart, you will see that your device has upgraded to 5.1.1. Congratulations. Now to go to 6.0 just go to software update and search for another update. I am starting to love this watch at what it can do in 6.0 so I suggest you upgrade.
Thank you, all and I hope this helped a lot of people out there.
Links:
Stock OS:
Android 5.1.1 OTA:
ADB AND FASTBOOT:
I will post inks as soon as I upload them.
-Soma
Hello, first off all I will thank all the help you can provide,
My problem, My urbane was running AW 2.0 but it made it laggy I unlock the bootloader and flash it with the 4 cores boot.img from this thread (I did not root or install twrp) then I realize OTA wont get into my urbane so I flash the stock boot.img from the same thread above, then uptade via OTA, all fife until here.
Then I try to reload the 4cores boot.img and my problems started. after this the watch wont start anymore and stay boot animation. but was responsive to adb reboot bootloader commands so I then flash stock boot.img but also didnt boot (even waiting over 20 mins) then as I had img files (BOOT, RECOVERY and SYSTEM to restore it to original AW v1.5 i tried flashing that boot.img from this thread the MM-boot.img flashed didnt help either. then I pressed the button for 20 secs and watch reload and even when it sounds how to is detected as USB on my computer and it is shown as "Android Bootloader Interface" on the device manager it never ever is shown under adb devices command. whatever I do it does not shown under devices attached so I can flash back factory boot, recovery and system images.
So if I start the watch stays forever on the boot animation, and if I swipe my finger at start to boot into bootloader is detected by windows as "Android Bootloader Interface" but "adb devices" command wont show the watch.
Help Please!!!!
Ale.
If manually start my device in bootloader it is detected by windows device manager, but when I type "adb devices" have nothing but if I set manually to bootloader then to recovery mode and then I select apply update from ADB, then watch is again detected by device manager, in this case and ONLY this case adb devices shows my watch but only as sideload ("my serial number" sideload) what can I do there? I cant use fastboot commands.
The things is that I think I wipe data and factory reset the watch and now I dont have adb debugging enable and cant so fastboot commands what can I do, please? is tehre a way to enable adb debugging without being able to boot the watch? can I sideload (as is the only way adb see my watch) the full "NXH19X_full_factory.zip" I tried "adb sideload NXH19X_full_factory.zip" but strat to write into the watch but gives error 21 and close after few seconds.
Please Help.
Ale.
**UPDATE**
Even when adb devices wont show my watch I was still able to flash factory images and is all working now.
This issue is over, close thread please and thanks.
I'm expecting the same simptoms and issues over here. All happens after to flash the 4 core img. Sudelly stucks. Please let me know if you have any news about
Hi Community,
I was rooted and got some nasty popup virus, then I factory reseted through settings. Everything was fine, then I entered in my software "superuser" and he said he would reinstall something, then booom bootloop!
I tried factory resetting through fastboot didnt work;
I tried flashing stockrom, latest rom, downgrade rom and the error is the same:
Verifying update package...
E: footer is wrong
Update package verification took 0.2 s (result 1).
E: Signature verification failed
E: error: 21
Installation aborted
ADB doesnt recognize my device!!! guess because after rebooting I never re authorized usb debugging mode or oem..
What Can I do now? any help appreciated
Hey, just try this Guide: https://forum.xda-developers.com/moto-x4/development/flash-official-frmware-moto-x4-t3730750
Everything is described there.
If your Device is on Android One, don't take the Rom from the thread but from this link: https://androidfilehost.com/?fid=673956719939834159
If you have further issues feel free to ask again
AdB dont recognize my device fastboot sees im plugged in but adb wont see the device
irongas said:
AdB dont recognize my device fastboot sees im plugged in but adb wont see the device
Click to expand...
Click to collapse
I believe you don't need adb to recognize your device if your flashing OEM firmware from the bootloader (and you have the bootloader unlocked). As long as you can boot into the bootloader you should be able to flash the stock firmware. I got my Moto x4 into a bootloop and was able to revert it back to the stock firmware even though my phone didn't have usb debugging enabled and my PC wasn't authorized for my phone. Follow these commands
screwyou00 said:
I believe you don't need adb to recognize your device if your flashing OEM firmware from the bootloader (and you have the bootloader unlocked). As long as you can boot into the bootloader you should be able to flash the stock firmware. I got my Moto x4 into a bootloop and was able to revert it back to the stock firmware even though my phone didn't have usb debugging enabled and my PC wasn't authorized for my phone. Follow these commands
Click to expand...
Click to collapse
thanks for the response, but i cant load any commands, because I cant connect my pc to the phone. Ive got an option called "apply update from sd card" and "Apply update from ADB" when i try the first it gives error 21, when i try the second it comes to a blank screen asking me to "Now send the package you want to apply to the device with "adb sideload <filename>" and I cant, because there is no connection..
irongas said:
thanks for the response, but i cant load any commands, because I cant connect my pc to the phone. Ive got an option called "apply update from sd card" and "Apply update from ADB" when i try the first it gives error 21, when i try the second it comes to a blank screen asking me to "Now send the package you want to apply to the device with "adb sideload <filename>" and I cant, because there is no connection..
Click to expand...
Click to collapse
Did you install Motorola fastboot drivers?
The menu what you talk about is Recovery. Look if there's an option to boot to bootloader. If not go down to reboot the device and keep VOL-Down pressed so it reboots to bootloader. There you can just use fastboot commands.
sleeptab said:
Did you install Motorola fastboot drivers?
I did, I used to workaround with adb and sending commands, but the command prompt would recognize my device, now, even in bootloader when I plug it in bootloader says: usb plugged in, but the pc wont see my device... im almost crying here lol
Click to expand...
Click to collapse
RESOLVED!
hEY i JUST looked in device manager and there was a driver issue, then I reinstalled the driver from the pc adb phone, and it came back to liiiife!!! I just followed the second sequence and boom its working
Thank you a looot guys!!! sorry being such a noob! =)
Have a nice one!!
Hello all, I'm trying to install a new ROM but one of the first steps consists in getting access to adb and fastboot mode.
Unfortunately, I can easily access to adb mode, and adb commands respond well, but when I then go in fastbood mode 'adb reboot fastboot", My phone goes to fastboot with the icon on the screen, but won't answer to any fastboot commands.
I've tried to install adb drivers, uninstall/reinstall the drivers (but it's always the windows drivers that installs first). I even tried to install google usb drivers using SDK manager, but didn't succeed this step.
I've tried to change the usb cable, but with another one, it was worse: even the adb commands would not work. So I guess the one I'm using is ok.
I'd be very happy if someone could help me fixing this frustrating bug!
Model:M1903F11A
kernel:4.14.117-perf-g0f2347b
MIUI Global 12.0.6
Android version : 10 QKQ1.190825.002
Cyjam said:
.. new ROM but one of the first steps consists in getting access to adb and fastboot mode.
...
Click to expand...
Click to collapse
The first step is to unlock the bootloader.
Cyjam said:
... when I then go in fastbood mode 'adb reboot fastboot", My phone goes to fastboot with the icon on the screen, but won't answer to any fastboot commands.
....
Click to expand...
Click to collapse
For fastboot try:
adb devices
........... (here you must see a number)
adb reboot bootloader
fastboot devices
........... (here you must see that number again)
Hi, thanks for trying to help me:
you're right , first is the unlock, but it's done. it's even in "grey" on the screen and written: bootloader is already unlocked. I've tested my phone with "root checker" and test is ok.
you're right about the command, this is the one I've used to go to fastmode and actually this command works: as I said, when in adb mode, it's all good: my phone is connected to pc and accepts the adb commands. But once I switch to fastboot, this is when it's going wrong: my phone's not answering to any commands.
To be more precise: when prompting: adb devices: i get a number. When prompting, in fastbood mode, fastboot devices: i get nothing.
Alleluia!!
Finally found out how to fix it!
After going in fasboot mode with the command: adb reboot bootloader, i opened the windows device manager: There I found a android XXx interface, or something like this: anyway, something barely identified by windows. Right clik, update drivers, manually update, pointing to the folder I store the google usb drivers and : Bingo! It works like a treat.
I now can step further in the process... Hope I won't need to come back with another question in the next minutes!