Related
am I just mistiming the enter button or something, or do I have a bad download again.
It was asked last month in the root the aria thread with no resolve so if I could figure it out this might help some others out including myself, and I thought getting adb working was the hard part...
here is the code exactly
Code:
-- Install from sdcard..
Finding update package...
Opening update package...
Verifying update package...
hit enter as per instructed (tried before after and all around this moment)
Code:
Installing update...
E:Error in /sdcard/update.zip (status 0)
Installation aborted.
just run the two commands again.
adb push ota.zip /sdcard/update.zip
then type: adb push update.zip /sdcard/update.zip
but select update.zip on the phone and press power first and when it says "verifying" hit enter on the keyboard.
If it still doesnt work try reformatting the sd card
I'm such a freaking newb I forgot to put the first update.zip /sdcard/update.zip
trying in a few moments
and wham bam thank you mam I have root.
so if you get error 0 make sure you read carefully and don't try to perform root almost asleep.
I was redoing the ota.zip not the update.zip silly me
Mine says the same thing, but I made sure I copied it to the sdcard first along with a ROM and ota.zip, and root.zip.
I also noticed that on my command prompt that it says error: device not found.
Right before it says device not found in my command prompt, the batch file it typing adb push ota.zip //sdcard/update.zip.
right after i type rootme2 the batch file also types in my command prompt clr, but an error comes out 'clr' is not recognized as an internal or external command operable program or batch file. "Please Wait..." This is the time where I am trying to time the apply sdcard:update.zip in my recovery console on my phone with hitting enter for the second time after typing rootme2.
Any suggestions? Am I missing something? Am I mistiming it still? Is it that difficult to time it correctly?
I do have an HTC Android phone USB device under disk drives and a E:\ under portable devices without an exclaimation mark in my device manager. However if I try to double click drive e: in my computer it says to enter a disk.
ANY advice is GREATLY appreciated!!
BTW I have made sure adb is running in task manager and I have tried unplugging and replugging in my usb cord.
I was having problems getting my slide running. It was suggested in the slide forums to install the free version of pda net onto the pc. It will find the right drivers for your device. I know the aria and slide are very simmilar. Alsp, it sounds silly, but I couldn't get root usinf my primary pc running win 7 64 bit. I dug an old xp 32 bit laptop out of my closet and got everything perfect on the first try.
Hope it helps some.
Sent from my rooted Mytouch Slide using XDA app.
Thank you for your reply. I already took the initiative to try it with an XP 32-bit system. Both systems seem to not be able to contact the device while it is in recovery state. No problems with the device while it is on and connected to either machine.
This is an Eris I am trying to root by the way. Everything seems to go like it is supposed to until the last part. The rootme2 command.
Thanks again, any other advice is appreciated!
Sorry that none of that has worked. I saw eris and read aria......
Either way, I wrote it up, maybe it will help someone.
I have been folowing the aria since my father in law had me root his. I used the exact computer and same process to do both. I only got root on the aria, never installed a rom or anything, he just wanted swipe like my wife and I have. I followed one thread or another, and it reccomended running an app called usbdeview. I deleted all htc drivers that were using usb. I then followed advice on another thread to install pda.net with links. Then follow eugene373's htc root method. When it finally worked it was easy. I did it another 10 times before I finally figured out how to get clockwork to take.
Only other thing to make sure you have is the newest java installed. Not the normal one but the one for developers. If ya are stuck, try reading a little in the htc esspresso (mytouch slide) forums. The two phones are pretty much the same on the inside. Different wifi and a few other things. See if ya stumble onto your exact problem. I am not saying to flash slide roms or anything.
Best of luck to you
Sent from my rooted Mytouch Slide using XDA app.
How about...
Move your adb installation to something like c:\android. Put all of the files you are working with into c:\android\tools
The change directory to your android tools folder and try it again.
Sent from my rooted Mytouch Slide using XDA app.
This is what I am getting from windows console both the same result with windows 7 64-bit and windows xp 32-bit...
C:\android\tools>rootme2
C:\android\tools>clr
'clr' is not recognized as an internal or external command,
operable program or batch file.
"Please Wait..."
C:\android\tools>adb push ota.zip /sdcard/update.zip
error: device not found
"OK! Congratulations, your phone is almost ready to be rooted"
"Here is the tricky part..."
""
"To access the controls in recovery, press Volume Up+Power"
"From here, use the Volume buttons to go up and down and the Power button to sel
ect"
""
"IMPORTANT:"
"You will select apply update.zip, but within 1/2 sec of doing this you must pre
ss enter to continue this script"
"If it is not done in the timely manner, you can try again by rerunning this scr
ipt"
C:\android\tools>pause
Press any key to continue . . .
C:\android\tools>adb push update.zip /sdcard
error: device not found
"From here, you should see ClockWork Recovery by Koush, and can install any ROM
you would like!"
"If you liked the work in this, send a donation to Wes Garner or Eugene_373 (lin
ks in the ReadMe)"
On the phone I get...
Android system Recovery <2e>
Use volume key to highlight: click power key to select. (I navigate to Apply sdcard:update.zip and hit power button. (when I see the red triangle in the background on the phone turn to green circle, I immediately press enter on my console on my windows machine and get the following)
E:Can't open /cache/recover/command
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
E:Error in /sdcard/update.zip
(Status 0)
Installation aborted.
I have done this a half a million times already with the same results. I tried at different times of the process with the same results. I do see HTC Android Phone USB device in my device manager with no errors. I do not see an Android adapter with My HTC in the device manager at all while in recovery mode like I do when the phone is all the way on and booted into the system.
I have tried everything listed in this thread and have been following wesgarner's post in forum.xda-developers.com/showthread.php?t=713347 which is based on Eugene_373's instructions. I found this thread with someone that appeared to have the same problem as I, and I tried what he tried and no luck.
Any further advice is GREATLY appreciated!! Thank You in advance!!
Has no one had this problem?
Factory wipe will just take me back to the version that I got this phone with, correct (2.1, replacement phone)?
Thank You!!
the push is
adb push update.zip /sdcard/update.zip
for case 0
I was trying to push this again and getting error 0
adb push ota.zip /sdcard/update.zip
I am haveing the same problem where after fastboot/boot loader screen comes up I go to recovery it brings me to the screen with the phone , triangle and exclamation.I next push power and up volume button and it brings me to the android system recovery. <2e>. In yellow at the bottom it says E:Can't open /cache/recovery/command, before i even touch anything else. I then go to apply sdcard:update.zip and given the error:
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:failed to open /sdcard/update.zip (no such file or directory)
E: signature verification failed
Installation aborted
I have formated the sd card to FAT32 many times and now wondering if someone has the ability to send me their files that worked to boot up their phone with similar problems. Or even the clockwork backup files from the clockwork mod nan backup.
geske001 said:
Thank you for your reply. I already took the initiative to try it with an XP 32-bit system. Both systems seem to not be able to contact the device while it is in recovery state. No problems with the device while it is on and connected to either machine.
This is an Eris I am trying to root by the way. Everything seems to go like it is supposed to until the last part. The rootme2 command.
Thanks again, any other advice is appreciated!
Click to expand...
Click to collapse
if you're having issues with drivers and ADB connectivity, install HTC Sync and it should install the proper drivers for your device. i have done that on a 64x windows 7 machine and a 32x XP machine.
http://www.htc.com/us/support/droid-eris-verizon/downloads/
cemysh33 said:
I am haveing the same problem where after fastboot/boot loader screen comes up I go to recovery it brings me to the screen with the phone , triangle and exclamation.I next push power and up volume button and it brings me to the android system recovery. <2e>. In yellow at the bottom it says E:Can't open /cache/recovery/command, before i even touch anything else. I then go to apply sdcard:update.zip and given the error:
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:failed to open /sdcard/update.zip (no such file or directory)
E: signature verification failed
Installation aborted
I have formated the sd card to FAT32 many times and now wondering if someone has the ability to send me their files that worked to boot up their phone with similar problems. Or even the clockwork backup files from the clockwork mod nan backup.
Click to expand...
Click to collapse
the initial error is expected if you're attempting to access clockwork recovery the old way, (attempting to plug the usb cable in at the right time, pushing the commands, etc) which is now not needed. to root your phone, simply use the unrevoked teams method. http://forum.xda-developers.com/showpost.php?p=6952379&postcount=1
cemysh33 said:
I am haveing the same problem where after fastboot/boot loader screen comes up I go to recovery it brings me to the screen with the phone , triangle and exclamation.I next push power and up volume button and it brings me to the android system recovery. <2e>. In yellow at the bottom it says E:Can't open /cache/recovery/command, before i even touch anything else. I then go to apply sdcard:update.zip and given the error:
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:failed to open /sdcard/update.zip (no such file or directory)
E: signature verification failed
Installation aborted
I have formated the sd card to FAT32 many times and now wondering if someone has the ability to send me their files that worked to boot up their phone with similar problems. Or even the clockwork backup files from the clockwork mod nan backup.
Click to expand...
Click to collapse
ur zip file is not signed properly...try to sign it or install through toggle signature verification in CWM recovery
My nexus 7 (2013) just did the stuck on X during start up thing. I have a bunch of photos from my vacation on it that I would like not to lose.
I've been reading up on adb and so far have installed the SDK and toolkit. My PC recognizes that my nexus is attached when I put it into adb sideload mode.
But I'm too new to know where to go from there. There is a lot out there about using the sideloader to do various things but haven't found anything that would help me so far.
Can I somehow use an adb backup command if install a zip file with the proper commands?
Is there a way to reinstall the OS via adb sideload to get the nexus running again without wiping the internal storage?
There have been some methods mentioned that involve have USB debugging enabled or the bootloader unlocked.
But I don't have USB debugging enabled and my bootloader is locked. I couldn't find a way to enable USB debugging without the nexus being able to start up. It looks like unlocking the bootloader requires a factory reset.
You can try to use adb to get your pictures. It's located in %sdk_folder%/platform-tools.
Simply use this command to get your files
Code:
adb pull /sdcard/Pictures /destination_folder
You can also push files to your sdcard while using the push command. I would try this to push a backup to the sdcard.
Are you able to get in recovery mode (CWM etc.)?
lective renzak
Most adb commands gives me "error:closed"
adb devices gives <serial number> sideload
I can upload a zip file via sideload. I just uploaded a zip file with an empty text document. It gave me an error that the update package failed which was expected.
I know nothing about update packages.
Is there one I could install that would get the nexus working without wiping out my pictures?
I was able to install an OTA update over the adb sideloader. So at least something is working.
I was hoping that installing the update would fix things but the nexus still gets stuck on X when starting up.
I'm wondering if I can insert something into the update installer script to do a backup or pull....
There is an install-recovery.sh script that I could potentially edit and then back up.
I there a command I could put into it that would do something equivalent to an adb pull or backup?
If anyone could give me a place to start, I'd really appreciate it.
I am in the same situation as you I have found nothing and only your posts on other forums!
If you have the stock configuration with usb debugging off and the bootloader locked, you're stuck. At least I couldn't figure out anything after many hours and weeks of asking. Had to bite the bullet and do a wipe. I rooted it when I did the wipe so I could try various recovery tools.
I tried dr fone and hexamob recovery and some other ones but no luck.
The nexus toolkit helped me out a bunch to try out adb commands and install a rooted system.
Sorry I don't have better news.
For backup services, I think shutterfly gives you unlimited photo only backups. For others you can do a combination of google drive, dropbox, amazon, etc. Amazon has some special thing for music I believe.
do u have the link for OTA zip file
AM struck at the same point with my Samsung note 3 . i need the link for ota update so that i can update my OS using ADB sideload . i tried downloading a zip file from sammobile but its gives me an error
E: footer is wrong
E: signature verification failed
i don't know what else i can do .
i tried DR fone i shows my pictures but never completes the backup process and shuts down.
plz help guys
What's your problem with the note 3? Solution likely different than my nexus issue. The Samsung phones do have a power button issue. Either doesn't work or gets stuck in the pressed position so when you try to start it continues to restart. If that's the case try fiddling around with power button. I find it helpful to pull the phone apart so I can get at the actual button.
i checked the power button is fine because it say up in recovery mode but keeps restarting in safe mode or normal mode. i need to either backup my data on the device using the recovery mode or update my device so that i can fix the corrupted OS. but when i try to do a OTA update using adb sideload and a zip file that i downloaded from sammobile it gives me this error :
E: footer is wrong
E: signature verification failed
. or just help me to backup my pictures using the recovery so that i can just do a factory reset any help would be appreciated. Thanks
Haha, got the same problems. But I do have USB Debugging on - does not help anything. Crazy, if you consider that files are there but you have to delete them in order to correct the stubbornness of the OEMs....
Here is the OTA file thanks to the user: OTA update file from here http://forum.xda-developers.com/showpost.php?p=47452029&postcount=325
I have more instructions at the bottom but you take the OTA file and change the file type from .cfg to .zip and you use that (no other modifications to the file)
Boot to recovery mode now and select Apply update from ADB.
Back on your computer... command: adb sideload whatever you named the OTA file you downloaded.zip
What I did was change the file type of the file for example it's blah.cfg I changed the .cfg to .zip and then I put the phone in recovery mode. When you get to recovery mode it gives you different options and you choose the one that says ADB sideload. You then run the command that was put in the first post (I also put the .zip file in the same folder as the folder that the adb is located in) and then I ran the sideload and it worked. I had to google how to run adb and where to get it. You can get adb from developer.google.com download the SDK (which will be in a zip). Extract the SDK and then run the sdkmanager.exe, after that choose the android SDK tools and platform tools. ADB will be in platform tools. Then you open up a command line window and you navigate to the folder that was created when you unzipped the SDK. Once you get there, you then navigate to the platform-tools folder (which is created when you run sdkmanager and install the androidsdk platform-tools). Once you get to platform tools use the command dir to see if adb.exe is there (which it should) then run adb devices (have your phone connected) and it should show a device connected. After that put your phone in recovery and then do the adb sideload and it will be waiting for you to run the command on the command line. Then on the computer you run the adb sideload blah.zip (it's posted on the first post also) and then.....wait everything should work.
I created this so we won't hijack the MJ6 to MJ9 thread and that way that can stay on topic for those users.
Good work, but you should fix your link to be http://forum.xda-developers.com/showpost.php?p=47452029&postcount=325
It's the truncated "..." version and doesn't work currently.
Ota link
raidel00 said:
Here is the OTA file thanks to the user: OTA update file from here http://forum.xda-developers.com/show...&postcount=325
I have more instructions at the bottom but you take the OTA file and change the file type from .cfg to .zip and you use that (no other modifications to the file)
Boot to recovery mode now and select Apply update from ADB.
Back on your computer... command: adb sideload whatever you named the OTA file you downloaded.zip
What I did was change the file type of the file for example it's blah.cfg I changed the .cfg to .zip and then I put the phone in recovery mode. When you get to recovery mode it gives you different options and you choose the one that says ADB sideload. You then run the command that was put in the first post (I also put the .zip file in the same folder as the folder that the adb is located in) and then I ran the sideload and it worked. I had to google how to run adb and where to get it. You can get adb from developer.google.com download the SDK (which will be in a zip). Extract the SDK and then run the sdkmanager.exe, after that choose the android SDK tools and platform tools. ADB will be in platform tools. Then you open up a command line window and you navigate to the folder that was created when you unzipped the SDK. Once you get there, you then navigate to the platform-tools folder (which is created when you run sdkmanager and install the androidsdk platform-tools). Once you get to platform tools use the command dir to see if adb.exe is there (which it should) then run adb devices (have your phone connected) and it should show a device connected. After that put your phone in recovery and then do the adb sideload and it will be waiting for you to run the command on the command line. Then on the computer you run the adb sideload blah.zip (it's posted on the first post also) and then.....wait everything should work.
I created this so we won't hijack the MJ6 to MJ9 thread and that way that can stay on topic for those users.
Click to expand...
Click to collapse
Your link is short. http://forum.xda-developers.com/showpost.php?p=47452029&postcount=325
Bimboy said:
Good work, but you should fix your link to be http://forum.xda-developers.com/showpost.php?p=47452029&postcount=325
It's the truncated "..." version and doesn't work currently.
Click to expand...
Click to collapse
silrosriv said:
Your link is short. http://forum.xda-developers.com/showpost.php?p=47452029&postcount=325
Click to expand...
Click to collapse
Ok...fixed it. Thanks for pointing it out!:good:
Help!
Ok, I redownloaded the cfg file, didn't touch anything except changing the file extension from .cfg to .zip. Rebooted to recovery, adb sideload, I get E:Error in /tmp/update.zip
(Status 7)
Installation aborted
does this wipe the device? or does it keep all your apps / data?
Update
I just chatted with someone at Samsung. The OTA has been pulled for issues by AT&T.
silrosriv said:
I just chatted with someone at Samsung. The OTA has been pulled for issues by AT&T.
Click to expand...
Click to collapse
probably due to some users having some issues with mms
silrosriv said:
Ok, I redownloaded the cfg file, didn't touch anything except changing the file extension from .cfg to .zip. Rebooted to recovery, adb sideload, I get E:Error in /tmp/update.zip
(Status 7)
Installation aborted
Click to expand...
Click to collapse
Interesting....It worked so smooth for me I don't know what else to say.
jherring002 said:
does this wipe the device? or does it keep all your apps / data?
Click to expand...
Click to collapse
If you do it by sideloading it from the computer it will not wipe the device. If you do it by running it from the SD card....it will wipe the device.
silrosriv said:
Ok, I redownloaded the cfg file, didn't touch anything except changing the file extension from .cfg to .zip. Rebooted to recovery, adb sideload, I get E:Error in /tmp/update.zip
(Status 7)
Installation aborted
Click to expand...
Click to collapse
I get the same error. At this point, I may odin to stock and try again. Or, just forget it and root again and stay on MF3.
dwanhala said:
I get the same error. At this point, I may odin to stock and try again. Or, just forget it and root again and stay on MF3.
Click to expand...
Click to collapse
You might want to hold off for a while. It has been reported that the S4 4.3 OTA has been pulled due to "problems". AT&T is supposed to offer the OTA again at a later unspecified date. I would wait until the "problems" are ironed out and try for the OTA when it is re-released...if you still want it.
scott14719 said:
You might want to hold off for a while. It has been reported that the S4 4.3 OTA has been pulled due to "problems". AT&T is supposed to offer the OTA again at a later unspecified date. I would wait until the "problems" are ironed out and try for the OTA when it is re-released...if you still want it.
Click to expand...
Click to collapse
Yup. I chatted with someone at Samsung. The OTA has been pulled for issues by AT&T.
I think I'll jist wait for it to come back.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
It's working pretty good on my phone. I quit using the lookout security app though. It's not really needed. I know they pulled galaxy s3 update.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
silrosriv said:
Ok, I redownloaded the cfg file, didn't touch anything except changing the file extension from .cfg to .zip. Rebooted to recovery, adb sideload, I get E:Error in /tmp/update.zip
(Status 7)
Installation aborted
Click to expand...
Click to collapse
Had the same problem when I tried to sideload the update. I was on MF3 and was rooted. What worked for me was to delete all busybox files and unroot using SuperSU and odin back to stock, just in case. After that, I was able to sideload and the phone booted up with no problems.
It works pretty good on my phone also. Was on mj6 and it was having random FC's also random vibrating but now on mj9 I don't have those problems anymore.
Sent from my SAMSUNG-SGH-I337 using xda premium
Thanks
Sent from my SAMSUNG-SGH-I337 using Tapatalk
I was getting the same error. What I did was re-load mf3 (via odin) and then sideload this update.
scott14719 said:
You might want to hold off for a while. It has been reported that the S4 4.3 OTA has been pulled due to "problems". AT&T is supposed to offer the OTA again at a later unspecified date. I would wait until the "problems" are ironed out and try for the OTA when it is re-released...if you still want it.
Click to expand...
Click to collapse
Yeah, at this point I just rooted again (which of course set my device status back to official from the custom that it had changed to when I unrooted) and I'll wait to see if AT&T is going fix the problems before proceeding.
finally
I can't believe it
- Restore my S4 AT&T to 4.2.2 stock with Odin all the 4 files in MF3 using (download mode)
- Sideloaded to 4.3 ...MJ9 File with the Framework using (recovery mode)
Now my phone is even rooted with SuperSU (starting the root with vroot and converting it to SuperSU)
with the following sort video tutorial that found on youtube this morning
youtube.com/watch?v=isHYNqWCfSc
Did anyone get the following error when flashing with adb?
error: failed to load 'image-blueline-qp1a.190711.019.zip': Not enough space
Got the same error with .020, also. Even keeping the -w in flash-all.bat gets the error.
Ok. NVM. Didn't have the latest platform-tools installed on my new computer.
I tried to sideload June OTA just as normal.
Code:
adb sideload F:\Pixel6a\bluejay-ota-tq3a.230605.010-a67dbf36.zip
serving: 'F:\Pixel6a\bluejay-ota-tq3a.230605.010-a67dbf36.zip' (~0%) adb: failed to read command: No error
that's the output of my terminal after trying to sideload it,.. on the phone nothing happens at all
it says verifying, but nothing about receiving anything and after leaving it for almost 10 minutes still nothing.
So I disconnect it and it says verification failed and it warns me
"Previous installation has failed, Your device may fail to boot if you reboot or power off now."
But it didn't even write anything did it? since it just failed at sending and verifying the ota in the first place.
Can I reboot my phone?
Edit: guess it's true that sideloading the OTA is really as safe as it gets, rebooting to System was no issue.
I just don't get what's wrong... using the same platform tools that I used for March, April and May update, 33.0.3-8952118
I re-downloaded the OTA from google to confirm it wasnt corrupt, same issue.
All my modules were disabled (not that that would stop adb from sending the file).
G5-User7080 said:
I tried to sideload June OTA just as normal.
Code:
adb sideload F:\Pixel6a\bluejay-ota-tq3a.230605.010-a67dbf36.zip
serving: 'F:\Pixel6a\bluejay-ota-tq3a.230605.010-a67dbf36.zip' (~0%) adb: failed to read command: No error
that's the output of my terminal after trying to sideload it,.. on the phone nothing happens at all
it says verifying, but nothing about receiving anything and after leaving it for almost 10 minutes still nothing.
So I disconnect it and it says verification failed and it warns me
"Previous installation has failed, Your device may fail to boot if you reboot or power off now."
But it didn't even write anything did it? since it just failed at sending and verifying the ota in the first place.
Can I reboot my phone?
Edit: guess it's true that sideloading the OTA is really as safe as it gets, rebooting to System was no issue.
I just don't get what's wrong... using the same platform tools that I used for March, April and May update, 33.0.3-8952118
I re-downloaded the OTA from google to confirm it wasnt corrupt, same issue.
All my modules were disabled (not that that would stop adb from sending the file).
Click to expand...
Click to collapse
Yeah, when sideloading an OTA (or updating via Settings) it puts the new version of the OS on the inactive slot. If something goes wrong with the update you'll still have your current slot to fallback on (like in your case).
Maybe try different cables/ports.
You can update through recovery if necessary; download the OTA to your device, reboot to recovery, and select Apply update from SD card.
V0latyle said:
You can update through recovery if necessary; download the OTA to your device, reboot to recovery, and select Apply update from SD card.
Click to expand...
Click to collapse
oh I remember seeing that option, does that mean I need to put the ota.zip in /sdcard/ ?
in essence that would circumvent adb sending issues / cable issues, I suppose?
G5-User7080 said:
oh I remember seeing that option, does that mean I need to put the ota.zip in /sdcard/ ?
in essence that would circumvent adb sending issues / cable issues, I suppose?
Click to expand...
Click to collapse
Yes. You don't need to use a PC at all. You can either download the OTA directly through your phone's browser, or if you want, you can use a USB cable to transfer the OTA file to your phone's storage. It doesn't matter where you put it; if you download it on your phone, it'll be in /sdcard/Downloads, if you use a USB cable you'll see the contents of /sdcard pop up as a USB drive in your computer.
V0latyle said:
Yes. You don't need to use a PC at all. You can either download the OTA directly through your phone's browser, or if you want, you can use a USB cable to transfer the OTA file to your phone's storage. It doesn't matter where you put it; if you download it on your phone, it'll be in /sdcard/Downloads, if you use a USB cable you'll see the contents of /sdcard pop up as a USB drive in your computer.
Click to expand...
Click to collapse
oki, I tried Pixelflasher first and interestingly it just worked.. same cable, same port, same adb, same everything
mhhhh.... using windows terminal wouldnt be the issue would it?
anyway, happy it works, but also frustrated I couldnt figure out why it refused to work typing the adb commands manually totally out of the blue
G5-User7080 said:
oki, I tried Pixelflasher first and interestingly it just worked.. same cable, same port, same adb, same everything
mhhhh.... using windows terminal wouldnt be the issue would it?
anyway, happy it works, but also frustrated I couldnt figure out why it refused to work typing the adb commands manually totally out of the blue
Click to expand...
Click to collapse
Were you using PowerShell or Command Prompt?
What were you doing on the phone?
There's two ways to get into sideload mode:
Manual way:
Manually enter recovery
Select Apply update from ADB
ADB way:
While in Android or recovery, issue the following command to your phone via ADB: adb reboot sideload
Either way, the device should read "Now send the package you want to apply to the device with "adb sideload <filename>"...
V0latyle said:
Were you using PowerShell or Command Prompt?
What were you doing on the phone?
There's two ways to get into sideload mode:
Manual way:
Manually enter recovery
Select Apply update from ADB
ADB way:
While in Android or recovery, issue the following command to your phone via ADB: adb reboot sideload
Either way, the device should read "Now send the package you want to apply to the device with "adb sideload <filename>"...
Click to expand...
Click to collapse
just windows 11 terminal, that should be powershell by default, dont think I've used anything else before tho
on the phone?
like nothing, I did it the way I asked you a few months back, the same I've done for the past 3 OTAs, disable modules, adb reboot sideload, followed by adb sideload <drag ota here>.
then the percentage didnt go up in terminal it said what I posted in OP
the phone only showed "verifying stuff", after like 8 mins I disconnected the phone and it showed like 100 lines of "failed to verify xxx" and then went back to fastbootd
i dont think the phone ever actually received the actual ota file.
it did read "now send the package..." then I did adb sideload ota-xyzyadayada.zip and thats what happened.
G5-User7080 said:
just windows 11 terminal, that should be powershell by default, dont think I've used anything else before tho
on the phone?
like nothing, I did it the way I asked you a few months back, the same I've done for the past 3 OTAs, disable modules, adb reboot sideload, followed by adb sideload <drag ota here>.
then the percentage didnt go up in terminal it said what I posted in OP
the phone only showed "verifying stuff", after like 8 mins I disconnected the phone and it showed like 100 lines of "failed to verify xxx" and then went back to fastbootd
i dont think the phone ever actually received the actual ota file.
it did read "now send the package..." then I did adb sideload ota-xyzyadayada.zip and thats what happened.
Click to expand...
Click to collapse
Odd, and Pixel Flasher worked - did you sideload or did you flash the factory image?
V0latyle said:
Odd, and Pixel Flasher worked - did you sideload or did you flash the factory image?
Click to expand...
Click to collapse
used PF's new "Full OTA" option, so sideload