Xiaomi Mi 10T stock global stable. Updated to Android 11 and can no longer side load anything – not just Google apps, ANYTHING. Not even via ADB installation commands.
Then I learned that Google introduced something called "app integrity" with Android 11 that hinders side loading. It's a function of Google Play Services, which stores its rules in an inaccessible directory (so I can't delete them). I tried uninstalling Google Play Services altogether and cutting all access to the Internet, but that didn't work either.
There must be a workaround that doesn't involve me having to root my phone (too much hassle and risk for my liking), or reverting to Android 10 (is that even possible?).
Any help would be appreciated.
adb sideload is TWRP specific feature so if you updated your Android Version you need to update TWRP too so it support adb sideload once again ... or you just using adb sideload command directly ??
ineedroot69 said:
adb sideload is TWRP specific feature so if you updated your Android Version you need to update TWRP too so it support adb sideload once again ... or you just using adb sideload command directly ??
Click to expand...
Click to collapse
adb sideload is NOT TWRP specific.
ADB Sideload is a mode the bootloader loads device into if requested to do so.
jwoegerbauer said:
adb sideload is NOT TWRP specific.
Click to expand...
Click to collapse
read my post
ineedroot69 said:
adb sideload is TWRP specific feature so if you updated your Android Version you need to update TWRP too so it support adb sideload once again ... or you just using adb sideload command directly ??
Click to expand...
Click to collapse
Directly, I guess. Am I using it wrong? Tbh, I'm not a dev and don't know what TWRP is.
Before Android 11, I was always able to install APKs directly via the phone. Only after updating did I try it via ADB to see if it solves my problem and it didn't – despite ADB being properly installed and my use of the appropriate commands.
Don't confuse "Sideload an APK" and "ADB Sideload" as others here do.
ADB Sideload isn't the correct method to install ( sideload ) APKs.
Read here
How to Use ADB Sideload in Android [Stock and TWRP Recovery]
In this guide, we will show you how to install ZIP files using the adb sideload command in both the stock and custom TWRP Recovery.
www.droidwin.com
To sideload an APK you run adb install [Options] APK what of course requires USB-debugging got enabled on phone before.
i dunno about Android 11 but have you tried installing it casually then just enable "allow Install unknown apps" ??
jwoegerbauer said:
To sideload an APK you run adb install [Options] APK what of course requires USB-debugging got enabled on phone before.
Click to expand...
Click to collapse
Yes, this is what I tried but it didn't work unfortunately. I keep getting "Failure [INSTALL_FAILED_USER_RESTRICTED: Install canceled by user]".
ineedroot69 said:
i dunno about Android 11 but have you tried installing it casually then just enable "allow Install unknown apps" ??
Click to expand...
Click to collapse
C'mon bro, I'm not that much of a noob. It's allowed for all the apps from which I install APKs.
I can no longer install casually after updating to Android 11.
Dagabix said:
Yes, this is what I tried but it didn't work unfortunately. I keep getting "Failure [INSTALL_FAILED_USER_RESTRICTED: Install canceled by user]
Click to expand...
Click to collapse
On some devices "Install Via USB" must also get enabled.
jwoegerbauer said:
On some devices "Install Via USB" must also get enabled.
Click to expand...
Click to collapse
I always keep it enabled.
jwoegerbauer said:
On some devices "Install Via USB" must also get enabled.
Click to expand...
Click to collapse
^ ohh yeahi forgot that there's this setting on Developer Options it's called Verify app over USB you provably need to disable that since your apk is from unknown source
ineedroot69 said:
^ ohh yeahi forgot that there's this setting on Developer Options it's called Verify app over USB you provably need to disable that since your apk is from unknown source
Click to expand...
Click to collapse
It's always been disabled, except for the one time I enabled it to see if it would make a difference – it didn't.
Problem solved. Turns out uninstalling 'MIUI security components' (com.miui.guardprovider) when debloating is what caused me to lose the ability to side load!
Related
Hi i'm having a problem trying to get my evo shift Perm Rooted. There's like 4 different guides that i've found on how To root an Evo or even more specifically the Shift. I've followed all these guides and still no luck.
I already have my phone Temp Rooted through VISIONary, my problem happens when I have to go to the CMB (Command Prompt)
8. Next, Open the command prompt (Start > Run > type "cmd") and paste the following...
Code:
cd C:\AndroidSDK\platform-tools
Hit enter, and type the following...
Code:
adb
If adb runs you're golden. Type this...
Code:
adb shell
Hit enter, you will see this...
Code:
$
Now type...
Code:
su
I make it to where I need to type in adb shell and what it says is adb server is out of date. killing... *daemon started successfully*
Then it shows the $ sign.
What i'm supposed to do now is type su
Then when I do it says su: permission denied
This is where i'm lost at. I followed everybody's instructions perfectly but cant move on till I get pass this... Can anyone help me please?
Thank you
What Android version are you on?
2.2 ?
2.3.3 ?
2.3.4 ?
Check the permissions under properties of adb.exe (right-click adb.exe and select properties) in your sdk/platform-tools folder. Make sure it is allowed to run as a program.
prboy1969 said:
What Android version are you on?
2.2 ?
2.3.3 ?
2.3.4 ?
Click to expand...
Click to collapse
2.2
Is that good or bad? Should I upgrade?
sparksco said:
Check the permissions under properties of adb.exe (right-click adb.exe and select properties) in your sdk/platform-tools folder. Make sure it is allowed to run as a program.
Click to expand...
Click to collapse
I have a Windows XP So when I go to properties the best I can do is Run it as an older version in compatibility mode? I'll still try it out to see if any older version works
*edit, tried and didnt work
tmb04 said:
2.2
Is that good or bad? Should I upgrade?
Click to expand...
Click to collapse
NO DO NOT UPGRADE!!! If your on 2.2 it's very easy. Just download and use THIS TOOL. It will do it all for you. Just connect the device via USB Cable, and choose charge only. Extract the Zip file that you downloaded onto your desktop, and run the program. Then click the ROOT Button. Make sure your Anti-Virus and Firewall are disabled before you start. Then just follow the Prompts. When it's all done go to the Play Store ( Android Market ) download Rom Manager Free. Open up Rom Manager follow the prompts to Flash CWM Recovery. That's it your Rooted with a Custom Recovery.
prboy1969 said:
NO DO NOT UPGRADE!!! If your on 2.2 it's very easy. Just download and use THIS TOOL. It will do it all for you. Just connect the device via USB Cable, and choose charge only. Extract the Zip file that you downloaded onto your desktop, and run the program. Then click the ROOT Button. Make sure your Anti-Virus and Firewall are disabled before you start. Then just follow the Prompts. When it's all done go to the Play Store ( Android Market ) download Rom Manager Free. Open up Rom Manager follow the prompts to Flash CWM Recovery. That's it your Rooted with a Custom Recovery.
Click to expand...
Click to collapse
I downloaded what you said, I run the program and disable the firewall, I clicked on Root and it says "Error running ADB try again"
I know that means I probably did something wrong in an earlier step but still unaware where I messed up at.
tmb04 said:
I downloaded what you said, I run the program and disable the firewall, I clicked on Root and it says "Error running ADB try again"
I know that means I probably did something wrong in an earlier step but still unaware where I messed up at.
Click to expand...
Click to collapse
You need adb working... In order for adb to work you need to have android debugging checked under Settings > Applications > Development on your phone. It's not enabled by default on Sense roms so you'll need to make sure it's enabled and turned on.
Ok I made it past the part I was stuck at. Rooted my phone, downloaded ROM manager, clicked on Flash ClockworkMod Recovery, and before it finishes it says " An error occurred while attempting to run privileged commands! "
I'm sorry for asking for so much help but I'm not trying to mess anything up
tmb04 said:
Ok I made it past the part I was stuck at. Rooted my phone, downloaded ROM manager, clicked on Flash ClockworkMod Recovery, and before it finishes it says " An error occurred while attempting to run privileged commands! "
I'm sorry for asking for so much help but I'm not trying to mess anything up
Click to expand...
Click to collapse
All good about asking questions. When the message pops up asking for SuperUser Permission, you have to click yes. Otherwise it will not run.
I ended up factory restoring my phone and followed a youtube video for the same exact guide that you told me to use. I followed it step by step and now my phone works perfect. I appreciate all the help.
Instead of me creating a new post, can you recommend a good guide for me to flash my shift to boost mobile?
tmb04 said:
I ended up factory restoring my phone and followed a youtube video for the same exact guide that you told me to use. I followed it step by step and now my phone works perfect. I appreciate all the help.
Instead of me creating a new post, can you recommend a good guide for me to flash my shift to boost mobile?
Click to expand...
Click to collapse
You should be able to find to find the info you need HERE.
Hello, Today i have installed Cyanogenmod 11. But after rebooting i connected my mobile to PC and in command prompt
i gave a command " adb devices" and the list is empty. :crying: This happened after flashing CM11. HELP !!!!!
I can access internal memory as a media device.
Did you enable the ADB?
cyrus_ae said:
Did you enable the ADB?
Click to expand...
Click to collapse
As above.
You'll need ADB active on the phone.
And a new / updated version of the ADB drivers / tools on your desktop.
Also, you will get a dialog prompt on the phone to confirm a security encrypted key (to allow ADB between your desktop and your phone)
This is something Google introduced on 4.1 (I think) which, if is not set, will end in a "devices not found" when trying to use ADB
dubidu said:
As above.
You'll need ADB active on the phone.
And a new / updated version of the ADB drivers / tools on your desktop.
Also, you will get a dialog prompt on the phone to confirm a security encrypted key (to allow ADB between your desktop and your phone)
This is something Google introduced on 4.1 (I think) which, if is not set, will end in a "devices not found" when trying to use ADB
Click to expand...
Click to collapse
Thanks for replay
Actually it worked till I flash CM11 using CWM Recovery. Problem came after flashing .
srujan21 said:
Thanks for replay
Actually it worked till I flash CM11 using CWM Recovery. Problem came after flashing .
Click to expand...
Click to collapse
Revoke all USB authorisation.
Try reconnecting.
And authorize when prompted!
If it doesnt work!
Also Please post Does your device show up in device manager? IF yes by what name? Is there an ADB Interface?
deej_roamer said:
Revoke all USB authorisation.
Try reconnecting.
And authorize when prompted!
If it doesnt work!
Also Please post Does your device show up in device manager? IF yes by what name? Is there an ADB Interface?
Click to expand...
Click to collapse
Its working, Thanks
ADB Device not found
deej_roamer said:
Revoke all USB authorisation.
Try reconnecting.
And authorize when prompted!
If it doesnt work!
Also Please post Does your device show up in device manager? IF yes by what name? Is there an ADB Interface?
Click to expand...
Click to collapse
i had same problem, plz help me
vardhanram said:
i had same problem, plz help me
Click to expand...
Click to collapse
The thing you are quoting is solution my friend. It also has a question if solution doesn't work. Please answer that
I screwed up trying to restore and now it says the phone is not rooted and has no OS installed on it. I still have access to the custom recovery if that helps. I have tried using ADB and Fastboot but it does not seem to be working. I need to know asap because it is for my dad and he travels a lot. He needs a phone. Please any help is appreciated.
1.Flash twrp
2. Go to adb sideload
3. In the terminal type adb sideload filename.zip
The ROM will flash and that's it.
If you need it back to stock just google "nexus 5 factory image" then download the latest one and follow the instructions given by google.
Also are you running linux (which distro) or windows just so I know what to tell you if that doesn't work
First of al: It's best to not use Windows 8 since there have been some driver incompatibilities and I'm not sure if they have been completely fixed yet.
Install 'Universal Naked Driver' and 'Minimal ADB and fastboot'. Both can be found here on xda.
Download the latest factory image for hammerhead from Google website. Extract the downloaded file twice and copy over everything to your 'Minimal ADB and fastboot' install dir.
Double click the flash-all.bat while your phone is in bootloader mode.
This will COMPLETELY reset your phone (all personalbdata will be wiped). Only the bootloader will stay unlocked.
awsumatt said:
1.Flash twrp
2. Go to adb sideload
3. In the terminal type adb sideload filename.zip
The ROM will flash and that's it.
If you need it back to stock just google "nexus 5 factory image" then download the latest one and follow the instructions given by google.
Also are you running linux (which distro) or windows just so I know what to tell you if that doesn't work
Click to expand...
Click to collapse
When trying step 3, it says cannot read sideload.
The command is not "sideload filename.zip" but
"adb sideload filename.zip"
Did you enter it correctly?
What does the terminal say as an error? And are you running Linux, Mac, or windows?
experience7 said:
The command is not "sideload filename.zip" but
"adb sideload filename.zip"
Did you enter it correctly?
Click to expand...
Click to collapse
Yes that is exactly how i entered it but with the file name of course. Although I did try your method but i don't see any file called flash-all.bat.
So just gonna ask again, what message did you get in the terminal?
Did you extract it twice? There should be a tgz file at some point... this one can be extracted as well (using 7-zip for example)
experience7 said:
The command is not "sideload filename.zip" but
"adb sideload filename.zip"
Did you enter it correctly?
Click to expand...
Click to collapse
okay nevermind my last comment. Now it says fastboot is not recognizable internal or external command. Press any key to exit
After you copied all the files into the Minimal ADB and fastboot folder the flash-all.bat should be in the same directory as fastboot.exe. Is this the case?
Try adb kill-server then (I'm a little rusty with windows) su adb start-server
experience7 said:
Did you extract it twice? There should be a tgz file at some point... this one can be extracted as well (using 7-zip for example)
Click to expand...
Click to collapse
Okay after I run the flash-all.bat, it just hangs at waiting for device
Install the 'Universal Naked Driver', reboot your computer and try again.
Again: The phone has to be in bootloader mode (you have to see the green android)
experience7 said:
Install the 'Universal Naked Driver', reboot your computer and try again.
Again: The phone has to be in bootloader mode (you have to see the green android)
Click to expand...
Click to collapse
I've decided to take the loss on this one. I just do not have time for this. I'll just go get it replaced. Thank you so much for the help. I'll definitely use XDA for more of my android problems in the future. Thank you again and to everyone who replied to this thread.
sbecerra407 said:
I've decided to take the loss on this one. I just do not have time for this. I'll just go get it replaced. Thank you so much for the help. I'll definitely use XDA for more of my android problems in the future. Thank you again and to everyone who replied to this thread.
Click to expand...
Click to collapse
Install this(fastboot + adb): http://forum.xda-developers.com/showthread.php?t=2588979
Download the file for Nexus 5: https://developers.google.com/android/nexus/images
Extract the file
Connect phone to pc in bootloader mode
Double click in flash all script
Wait for it to finish
sbecerra407 said:
When trying step 3, it says cannot read sideload.
Click to expand...
Click to collapse
ofc... you need to ENABLE sideload on twrp itself..
Thread cleaned.
Let's keep it on topic guys,
Howdy! I got a gionee a1 lite device recently and I cannot manually reboot the phone to bootloader through recovery mode or fastboot via adb pc tools. Someone here enlightened me that the device's fastboot is disabled which is a bummer.
I'm aware now that some manufacturers disable their devices' bootloaders for reasons unknown. Has anyone been able to root a device with a disabled fastboot? Please help me out.
Trunks614 said:
Howdy! I got a gionee a1 lite device recently and I cannot manually reboot the phone to bootloader through recovery mode or fastboot via adb pc tools. Someone here enlightened me that the device's fastboot is disabled which is a bummer.
I'm aware now that some manufacturers disable their devices' bootloaders for reasons unknown. Has anyone been able to root a device with a disabled fastboot? Please help me out.
Click to expand...
Click to collapse
Methods that involve flashing the device won't do you any good. You'll have to try methods that involve using an app to root the device for you, which have not been useful to root android since android Lollipop/Marshmallow was released.
Droidriven said:
Methods that involve flashing the device won't do you any good. You'll have to try methods that involve using an app to root the device for you, which have not been useful to root android since android Lollipop/Marshmallow was released.
Click to expand...
Click to collapse
Is there possibly any app or other method that doesn't involve unlocking bootloader to root android nougat? Kingroot and kingoroot have been ineffective so far.
It's a misconception to think that device's bootloader must get unlocked before device's Android can get rooted.
Rooting Android simply means a suitable SU binary - by whatever method - gets installed. IMO the easiest method to do this is by means of ADB.
jwoegerbauer said:
It's a misconception to think that device's bootloader must get unlocked before device's Android can get rooted.
Rooting Android simply means a suitable SU binary - by whatever method - gets installed. IMO the easiest method to do this is by means of ADB.
Click to expand...
Click to collapse
I have a ported twrp ready to flash but I'm hesitant because I heard flashing a recovery while bootloader is locked could bork the device. Flashing twrp seems to be the only step now to root the phone, should I give it a try or avoid the risk?
My POV: TWRP isn't needed at all to root a device's Android.
jwoegerbauer said:
My POV: TWRP isn't needed at all to root a device's Android.
Click to expand...
Click to collapse
I needed the twrp to flash magisk. Is there some other method to root an android 7 device that doesn't involve twrp or unlocking bootloader?
I already told you a method: no more to say by me ...
jwoegerbauer said:
I told a method: no more to say by me ...
Click to expand...
Click to collapse
Please put me through or post the link to the method.
1. Download latest version of SuperSU.zip onto PC
2. Install ADB on PC ( systemwide accessible !!! ) if not already done yet
3. On phone enable USB debugging, if not already done yet, and reboot phone
4. Connect phone with PC via USB cable that came with phone
5. Run a Windows command script ( .BAT-file ) that contains these lines
Code:
@echo off
adb devices
adb reboot recovery
timeout /t 10 /nobreak >nul
echo In Recovery menu shown on device select "Update from ADB" and apply
echo Press any key when done ...
pause >nul
adb sideload <PATH-TO-SUPERSU.ZIP-FILE-ON-PC-HERE>
adb reboot
jwoegerbauer said:
My POV: TWRP isn't needed at all to root a device's Android.
Click to expand...
Click to collapse
My POV: it isn't exactly as simple as connect to adb and issue a few commands, that is just a fact. I'm speaking from experience, just isn't that simple in all cases. If you can get the device to accept temp root via adb, then, yes, it "can" be that simple, the problem is, temp root via adb isn't an option on ALL android devices.
jwoegerbauer said:
1. Download latest version of SuperSU.zip onto PC
2. Install ADB on PC ( systemwide accessible !!! ) if not already done yet
3. On phone enable USB debugging, if not already done yet, and reboot phone
4. Connect phone with PC via USB cable that came with phone
5. Run a Windows command script ( .BAT-file ) that contains these lines
Code:
@echo off
adb devices
adb reboot recovery
timeout /t 10 /nobreak >nul
echo In Recovery menu shown on device select "Update from ADB" and apply
echo Press any key when done ...
pause >nul
adb sideload <PATH-TO-SUPERSU.ZIP-FILE-ON-PC-HERE>
adb reboot
Click to expand...
Click to collapse
Thank you. I tried this, unfortunately I got a "device not found" error even though "adb devices" did.
Droidriven said:
My POV: it isn't exactly as simple as connect to adb and issue a few commands, that is just a fact. I'm speaking from experience, just isn't that simple in all cases. If you can get the device to accept temp root via adb, then, yes, it "can" be that simple, the problem is, temp root via adb isn't an option on ALL android devices.
Click to expand...
Click to collapse
I'm really confused ...
With no line in this thread it was mentioned / suggested / recommended to install a temporary root.
I kindly ask you to stop hopping into a thread and post off-topic content. TIA
@Trunks614
When ADB triggers "no devices found" then it's mostly caused by wrong ADB-driver used.
jwoegerbauer said:
@Trunks614
When ADB triggers "no devices found" then it's mostly caused by wrong ADB-driver used.
Click to expand...
Click to collapse
Will "apply update from SD card" work the same way?
jwoegerbauer said:
1. Download latest version of SuperSU.zip onto PC
2. Install ADB on PC ( systemwide accessible !!! ) if not already done yet
3. On phone enable USB debugging, if not already done yet, and reboot phone
4. Connect phone with PC via USB cable that came with phone
5. Run a Windows command script ( .BAT-file ) that contains these lines
Code:
@echo off
adb devices
adb reboot recovery
timeout /t 10 /nobreak >nul
echo In Recovery menu shown on device select "Update from ADB" and apply
echo Press any key when done ...
pause >nul
adb sideload <PATH-TO-SUPERSU.ZIP-FILE-ON-PC-HERE>
adb reboot
Click to expand...
Click to collapse
SuperSU is a deprecated project, that is why and how Magisk came to prominence. Anyone still using SuperSU is taking a real chance of compromising the security of their device at the system level. If SuperSU is used to gain root, it is highly recommended to convert to Magisk root after gaining root via SuperSU.
i have the same problem, zte A5 2019 fastboot disabled, by the way you can try mtk easy-su
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