Database Develop

[Q] stuck at bootloader!!

Current device status:
M7-UL
Relocked
S-OFF
CID-11111111
Stock recovery!!
before action or Problem:
Did full wipe through custom recovery TWRP. which cost me to loose everything SDcard including my OS. Now i can't reboot nor i have custom rom.zip----how stupid
Tries:
1. Tried to ADB push custom rom but was not successful cause SDcard mount. tried to unmount but unusful.
2. so i decided to get the orignal firmware 1.29 (before i was 2.17)---please don't ask why
I used mike guide. it work----Thanks mike for the guide
Now i'm back to the old firmware (1.29) with no OS to boot and stock recovery.
I hope the expert here can give me a hand on this and get my HTC one back to life!!
Thanks in advance for you supports

omvingG upon
aburobeen said:
Current device status:
M7-UL
Relocked
S-OFF
CID-11111111
Stock recovery!!
before action or Problem:
Did full wipe through custom recovery TWRP. which cost me to loose everything SDcard including my OS. Now i can't reboot nor i have custom rom.zip----how stupid
Tries:
1. Tried to ADB push custom rom but was not successful cause SDcard mount. tried to unmount but unusful.
2. so i decided to get the orignal firmware 1.29 (before i was 2.17)---please don't ask why
I used mike guide. it work----Thanks mike for the guide
Now i'm back to the old firmware (1.29) with no OS to boot and stock recovery.
I hope the expert here can give me a hand on this and get my HTC one back to life!!
Thanks in advance for you supports
Click to expand...
Click to collapse
Use twrp to sideload the rom. I think you go to Advance tab in TWRP and choose sideload rom and adb I think the command is "adb sideload <name of rom>".
I can't remember fully. I hope someonce can assist you and correct me if I'm wrong.

Rex2369 said:
Use twrp to sideload the rom. I think you go to Advance tab in TWRP and choose sideload rom and adb I think the command is "adb sideload <name of rom>".
I can't remember fully. I hope someonce can assist you and correct me if I'm wrong.
Click to expand...
Click to collapse
Thanks for the replay.
The problem is i'm on stock recovery. I got it back after updating the firmware.
Now i'm relocked and stuck with the stock recovery.
I thinks first i need to unlock and then flash the custom recovery.
But how to do it while i'm in bootloader and with no OS in place!!

When you are in bootloader, click on Fastboot. After you are in Fastboot USB mode (it will show that on the screen), unlock the bootloader using this tutorial:
http://www.redmondpie.com/how-to-unlock-htc-one-bootloader-tutorial/
After you are done with that, you'll need to download TWRP 2.5.0 and place it inside your fastboot folder on your computer, and then open a command prompt window from there (shift + right click and open command prompt window here) and then execute this command:
fastboot flash recovery recovery.img
Of course you replace recovery.img with whatever the name of your recovery is, in that case TWRP 2.5.0's zip file.

TarekElsakka said:
When you are in bootloader, click on Fastboot. After you are in Fastboot USB mode (it will show that on the screen), unlock the bootloader using this tutorial:
http://www.redmondpie.com/how-to-unlock-htc-one-bootloader-tutorial/
After you are done with that, you'll need to download TWRP 2.5.0 and place it inside your fastboot folder on your computer, and then open a command prompt window from there (shift + right click and open command prompt window here) and then execute this command:
fastboot flash recovery recovery.img
Of course you replace recovery.img with whatever the name of your recovery is, in that case TWRP 2.5.0's zip file.
Click to expand...
Click to collapse
Thanks a lot.
it helped
Now how i can get my OS back to business.
Do i need to flash the stock rom or any rom? and how can i flash it!!

So, i think is better flashing a ruu, like the stock european ruu and, via Revone tool, flash a recovery
You're s-offed, you don't need unlock your bootloader

Guich said:
So, i think is better flashing a ruu, like the stock european ruu and, via Revone tool, flash a recovery
You're s-offed, you don't need unlock your bootloader
Click to expand...
Click to collapse
Thanks for the tip.
i'm only a littlle android guy. i hardly manage to get my S-OFF.
would you be so kind to show me on how to do that:angel:

Depends on what you are looking for. Are you trying to revert your device to stock status so you can receive OTA updates? Because that would mean flashing a RUU and relocking the bootloader, as mentioned above. However if you aren't interested in OTA updates (which we don't know when will be available) then go for the easier route, a custom ROM which you flash via TWRP recovery. After you go into TWRP, go to Advanced and choose ADB sideload and then slide to start, then use your computer to adb sideload rom.zip (of course rom.zip will be replaced by whichever ROM you want to sideload).
This is to set up ADB:
http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/
The proper drivers for your PC to recognize the device in ADB mode are obtained by installing HTC Sync Manager.

TarekElsakka said:
Depends on what you are looking for. Are you trying to revert your device to stock status so you can receive OTA updates? Because that would mean flashing a RUU and relocking the bootloader, as mentioned above. However if you aren't interested in OTA updates (which we don't know when will be available) then go for the easier route, a custom ROM which you flash via TWRP recovery. After you go into TWRP, go to Advanced and choose ADB sideload and then slide to start, then use your computer to adb sideload rom.zip (of course rom.zip will be replaced by whichever ROM you want to sideload).
This is to set up ADB:
http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/
The proper drivers for your PC to recognize the device in ADB mode are obtained by installing HTC Sync Manager.
Click to expand...
Click to collapse
He can use the adb push command too...

Ah okay. I am new to all of this so I don't have sufficient information, I was just sharing how I got to fix my device when I was in the same situation.

I used adb push zip file as below instruction:
C:\Android>adb devices
List of devices attached
FA35VW927790 recovery
C:\Android>adb push Android_Revolution_HD-One_9.4.zip /data/media/
3100 KB/s (1017950778 bytes in 320.621s)
C:\Android>adb reboot recovery
C:\Android>
I try to look for the zip file but did not find it?? any ideas

Still stuck at this point.
I tried to adb push it many times but still no success
:crying:
Please guys tell me if im doing something wrong or you have a better way of doing it.

aburobeen said:
Still stuck at this point.
I tried to adb push it many times but still no success
:crying:
Please guys tell me if im doing something wrong or you have a better way of doing it.
Click to expand...
Click to collapse
The zip will be there somewhere, I command '/sdcard' instead of '/data/media'.
If you still can't find it just use
adb sideload Android_Revolution_HD-One_9.4.zip
Choose install zip from sideload in recovery and once it's finished transferring it will begin to install automatically so you won't have to look for the zip file
Sent from my HTC One using xda premium

aburobeen said:
I used adb push zip file as below instruction:
C:\Android>adb devices
List of devices attached
FA35VW927790 recovery
C:\Android>adb push Android_Revolution_HD-One_9.4.zip /data/media/
3100 KB/s (1017950778 bytes in 320.621s)
C:\Android>adb reboot recovery
C:\Android>
I try to look for the zip file but did not find it?? any ideas
Click to expand...
Click to collapse
because you wiped your internal storage there is no file structure there, that's why you cant find the zip file.
You'll have to sideload your rom from twrp then boot up your phone which will create the needed directories.
1) update your android sdk. Sideload only works on certain versions of the sdk.
2) Place the rom you would like to flash in the same folder as fastboot and adb.( for you it looks like C:\Android\sdk\platform-tools
3) next from twrp under the advanced tab turn on adb sideload
4) issue the command adb sideload name of rom.zip
good luck

aburobeen said:
Still stuck at this point.
I tried to adb push it many times but still no success
:crying:
Please guys tell me if im doing something wrong or you have a better way of doing it.
Click to expand...
Click to collapse
If you use /sdcard then it will work fine, I had the same issue

Victory at last :laugh:
My experience:
TWRP recovery
1.Tried to adb push /sdcard succeeded on this but failed to flash!!
2. Tried to adb sideload failed.
3. Flashed another recovery CWM.
4. adb sideload file.zip...........success
I don't why TWRP recovery was not responding correctly.
Any way got my phone back to life. and hopefully my experience could help people who made the same foolish mistake!!
Thanks to everybody who contributed to this post.
Cheers all

Maybe you had an earlier version of TWRP which had incompatibility issues with ADB. Anyway I'm glad you got through it. I sure hate being stuck like that as well.
Sent from my HTC One using Tapatalk 4 Beta

aburobeen said:
Victory at last :laugh:
My experience:
TWRP recovery
1.Tried to adb push /sdcard succeeded on this but failed to flash!!
2. Tried to adb sideload failed.
3. Flashed another recovery CWM.
4. adb sideload file.zip...........success
I don't why TWRP recovery was not responding correctly.
Any way got my phone back to life. and hopefully my experience could help people who made the same foolish mistake!!
Thanks to everybody who contributed to this post.
Cheers all
Click to expand...
Click to collapse
What version of CWM did you flash to get sideload working??

Alex740il said:
What version of CWM did you flash to get sideload working??
Click to expand...
Click to collapse
I used the latest CWM Version 6.0.3.2.

[Q] Stuck in Boot Cycle With Other Problems

Hi All,
First off please forgive how much of a low level noob I am am at this. I didn't create a backup unfortunately. Now we can get to the good stuff. I have unlocked, s-off, and rooted my phone. Loaded a great GPE rom on there and it was working perfectly fine. While looking for a SU for the Rom so that I could delete some wifi bs I found a the HD rom on this site that I would rather use. Soooo I rooted the rom and used cwm to load up the HD 6.1 rom. After the install, when rebooting, it asked me if I wanted to fix the SU permissions and i clicked yes. Now it is stuck in a boot cycle. When I enter fastboot I can enter commands (no adb detection) I can even flash a different recovery on there and the corresponding logo will flash for a second at the end of each boot cycle. Trying to launch reboot or factory reset will put me into another boot cycle. I have tried using fastboot to load directly into recovery but that freezes the phone 2/3 times. Any help would be greatly appreciated so that I can just go back to the GPE rom i was using and stop screwing around with my phone.

XaBuddy said:
Hi All,
First off please forgive how much of a low level noob I am am at this. I didn't create a backup unfortunately. Now we can get to the good stuff. I have unlocked, s-off, and rooted my phone. Loaded a great GPE rom on there and it was working perfectly fine. While looking for a SU for the Rom so that I could delete some wifi bs I found a the HD rom on this site that I would rather use. Soooo I rooted the rom and used cwm to load up the HD 6.1 rom. After the install, when rebooting, it asked me if I wanted to fix the SU permissions and i clicked yes. Now it is stuck in a boot cycle. When I enter fastboot I can enter commands (no adb detection) I can even flash a different recovery on there and the corresponding logo will flash for a second at the end of each boot cycle. Trying to launch reboot or factory reset will put me into another boot cycle. I have tried using fastboot to load directly into recovery but that freezes the phone 2/3 times. Any help would be greatly appreciated so that I can just go back to the GPE rom i was using and stop screwing around with my phone.
Click to expand...
Click to collapse
fastboot erase cache
then flash the recovery again (twrp 2.6.3.3 suggested)
then from recovery wipe and adb push or sideload the rom

I was able to get twrp to work by flashing it again, probably the 7th time, and erased the cache. Now I don't think i want to load the same rom that started this but to go back to the GPE version that I had. Is there a way to get this on the internal sd card through fastboot?

XaBuddy said:
I was able to get twrp to work by flashing it again, probably the 7th time, and erased the cache. Now I don't think i want to load the same rom that started this but to go back to the GPE version that I had. Is there a way to get this on the internal sd card through fastboot?
Click to expand...
Click to collapse
Your options are:
1) adb push
2) sideload from TWRP
3) OTG cable from TWRP
Lots of threads for each of these available in Google

mb_guy said:
Your options are:
1) adb push
2) sideload from TWRP
3) OTG cable from TWRP
Lots of threads for each of these available in Google
Click to expand...
Click to collapse
I was ablt to get adb to recognize the phone however it lists it as a host. I go into the twrp and do the sideload but it opens up the debug message. adb sideload os.zip is the command I'm using as I renamed the file to os.zip so i don't have to type so much. I tried the adb push but it says error:Closed.

mb_guy said:
Your options are:
1) adb push
2) sideload from TWRP
3) OTG cable from TWRP
Lots of threads for each of these available in Google
Click to expand...
Click to collapse
so adb push finally did something but not quite what I wanted this is the message I got
failed to copy '/Users/robertlitz/Downloads/Archive/os.zip' to '/data/media/0/': Is a directory

XaBuddy said:
so adb push finally did something but not quite what I wanted this is the message I got
failed to copy '/Users/robertlitz/Downloads/Archive/os.zip' to '/data/media/0/': Is a directory
Click to expand...
Click to collapse
Try this instead
adb push os.zip /sdcard/os.zip

mb_guy said:
Try this instead
adb push os.zip /sdcard/os.zip
Click to expand...
Click to collapse
It worked!! Thank you so much. I had tried adb push os.zip /sdcard/ a while ago but it didn't take. by typing the zip name after sdcard i assume that "gives" the file an exact location to be placed?

[SOLVED] E: Can't mount /cache/

I'm sorry to do this, but I don't know where to start. Here's what I did to get to where I'm at:
- previously running SlimBean flashed using TWRP
- Downloaded ROM Manager and it recommended installing CWM Recovery
- Followed prompts
- It installed CWM 6.0.4.8
- Booted back into ROM and used ROM Manager to attempt to flash SlimKat 4.4.2 build 6
- CWM wiped dalvik but then got hung up
- Now it keeps saying Can't mount /cache/recovery/command
I'm completely stuck. Can't figure out what to do next. Please help!!!

Have you tryed reflashing the recovery to rule out a faulty install of cwm?
I should say, have you tried reflashing cwm *through Fastboot* to rule out a faulty cwm install?

Use TWRP recovery, preferred is 2.6.3.3 although there are newer versions, enter recovery, wipe - format data, basically for some reason, fastboot erase cache wipes the cache into an un-readable format.
note: this will also erase your internal storage too, so if theres anything important you want on there, make sure you back it up first using the adb pull command.

dougeedug said:
Have you tryed reflashing the recovery to rule out a faulty install of cwm?
I should say, have you tried reflashing cwm *through Fastboot* to rule out a faulty cwm install?
Click to expand...
Click to collapse
I can't get it to recognize my devices in order to use ADB. When connected, I type ADB Devices and I don't see anything listed. Is there a way to check I'm doing this ok?
EDIT: Ok, I got it to recongize my device. I'm going to try flashing TWRP thru ADB....will report back shortly...
Seanie280672 said:
Use TWRP recovery, preferred is 2.6.3.3 although there are newer versions, enter recovery, wipe - format data, basically for some reason, fastboot erase cache wipes the cache into an un-readable format.
note: this will also erase your internal storage too, so if theres anything important you want on there, make sure you back it up first using the adb pull command.
Click to expand...
Click to collapse
I can't quite risk doing this yet. Only as a last, last resort...

cartisdm said:
I can't get it to recognize my devices in order to use ADB. When connected, I type ADB Devices and I don't see anything listed. Is there a way to check I'm doing this ok?
EDIT: Ok, I got it to recongize my device. I'm going to try flashing TWRP thru ADB....will report back shortly...
I can't quite risk doing this yet. Only as a last, last resort...
Click to expand...
Click to collapse
whilst your phone is in recovery and plugged into your computer, open device manager, is there a yellow ! where its says android devices or myHTC ?
IGNORE THIS, You got it working whilst I was typing this.

cartisdm said:
I can't get it to recognize my devices in order to use ADB. When connected, I type ADB Devices and I don't see anything listed.
Click to expand...
Click to collapse
Use the command "fastboot devices" from the bootloader with "fastbootUSB" highlighted. You can't use adb commands in the bootloader because adb is to interact with android, which is not running while in bootloader. Let me know if you get output with the "fastboot devices" command.
EDIT: I should specify, if you are trying to flash recovery from anywhere but the bootloader using fastboot commands (it sounds like you may be trying to flash recovery with adb commands), you are just doing it wrong. so lets get that sorted first.

cartisdm said:
I can't get it to recognize my devices in order to use ADB. When connected, I type ADB Devices and I don't see anything listed. Is there a way to check I'm doing this ok?
EDIT: Ok, I got it to recongize my device. I'm going to try flashing TWRP thru ADB....will report back shortly...
Click to expand...
Click to collapse
you flash a custom recovery with fastboot commands not adb commands.

Got it!!! Thank you everyone for taking the time. I have a flight in a few hours and I was panicking!!!!
I grabbed universal drivers from here: download.clockworkmod.[com]/test/UniversalAdbDriverSetup6.msi (remove the brackets around .com)
Then my computer picked up the device and I was able to install TWRP. Clockworkmod recovery still doesn't work, no matter which version I tried. I'll stick with TWRP for now.
Thanks again!
EDIT: Well eff me, it wiped my internal storage. It must have done it after I flashed because that's where I grabbed the zip in the first place. That sucks...

cartisdm said:
Got it!!! Thank you everyone for taking the time. I have a flight in a few hours and I was panicking!!!!
I grabbed universal drivers from here: download.clockworkmod.[com]/test/UniversalAdbDriverSetup6.msi (remove the brackets around .com)
Then my computer picked up the device and I was able to install TWRP. Clockworkmod recovery still doesn't work, no matter which version I tried. I'll stick with TWRP for now.
Thanks again!
EDIT: Well eff me, it wiped my internal storage. It must have done it after I flashed because that's where I grabbed the zip in the first place. That sucks...
Click to expand...
Click to collapse
did you format data inside twrp recovery, like I said above, that will erase your internal storage too, you will need to push a rom over to your internal storage now using adb and then flash it.

Seanie280672 said:
did you format data inside twrp recovery, like I said above, that will erase your internal storage too, you will need to push a rom over to your internal storage now using adb and then flash it.
Click to expand...
Click to collapse
I didn't do so intentionally, but it's possible I did it without paying attention. I'm back to my system now so I'll just live with the loss. I flashed an existing ROM that I had in my Downloads folder once I was able to get into TWRP. It's just weird that folder is empty now.

[help] Locked bootloader, and stuck in bootloop with TWRP installed.

So I just bought a new phone and was getting ready to reset my Nexus 6 back to stock and relock the bootloader. Using Wugs toolkit I for some inexplicable reason relocked the bootloader before going stock. I got myself stuck in a boot loop but was eventually able to get into TWRP. Since I cannot unlock the bootloader without checking the box in the SW I want to flash a rom there but sdcard cannot mount in twrp and I am stuck. What should I attempt next or should I rma with Moto?

Bigsam411 said:
So I just bought a new phone and was getting ready to reset my Nexus 6 back to stock and relock the bootloader. Using Wugs toolkit I for some inexplicable reason relocked the bootloader before going stock. I got myself stuck in a boot loop but was eventually able to get into TWRP. Since I cannot unlock the bootloader without checking the box in the SW I want to flash a rom there but sdcard cannot mount in twrp and I am stuck. What should I attempt next or should I rma with Moto?
Click to expand...
Click to collapse
You must use fastboot commands.
fastboot format cache
fastboot format userdata
Then you can transfer a ROM from your PC and flash.

The_Merovingian said:
You must use fastboot commands.
fastboot format cache
fastboot format userdata
Then you can transfer a ROM from your PC and flash.
Click to expand...
Click to collapse
How can I transfer a rom to the phone? adb sideload in twrp does not seem to work and It will not mount storage.

Bigsam411 said:
How can I transfer a rom to the phone? adb sideload in twrp does not seem to work and It will not mount storage.
Click to expand...
Click to collapse
After issuing the fastboot commands I provided, MTP transfer should work.
Simply boot to TWRP after formatting from bootloader. Connect to PC, and you should see your device detected. Drag and drop the ROM in your internal storage.

Bigsam411 said:
How can I transfer a rom to the phone? adb sideload in twrp does not seem to work and It will not mount storage.
Click to expand...
Click to collapse
Should show as standard device storage like MTP. Not under adb. Should show as a drive.

The_Merovingian said:
After issuing the fastboot commands I provided, MTP transfer should work.
Simply boot to TWRP after formatting from bootloader. Connect to PC, and you should see your device detected. Drag and drop the ROM in your internal storage.
Click to expand...
Click to collapse
My phone shows up in windows Explorer but I cannot move anything over to it. I am in TWRP and cannot see the storage partition.

prdog1 said:
Should show as standard device storage like MTP. Not under adb. Should show as a drive.
Click to expand...
Click to collapse
It does show up but I am unable to transfer anything to it.

Bigsam411 said:
It does show up but I am unable to transfer anything to it.
Click to expand...
Click to collapse
Did you use the fastboot commands?

Bigsam411 said:
It does show up but I am unable to transfer anything to it.
Click to expand...
Click to collapse
Have seen this before. Try unplugging and plug back in. There is some way to access it. Never had to do it.

The_Merovingian said:
Did you use the fastboot commands?
Click to expand...
Click to collapse
I had previously tried those before opening this thread, then I tried them again just now. I attached the output from command prompt.

Ok I am now able to get to a point to where I can flash a rom and not get any errors (at least no visible ones) but I still get stuck at the boot screen with the colored dots animation. Is there a specific rom I should try to install?

Bigsam411 said:
Ok I am now able to get to a point to where I can flash a rom and not get any errors (at least no visible ones) but I still get stuck at the boot screen with the colored dots animation. Is there a specific rom I should try to install?
Click to expand...
Click to collapse
If want pure stock deodexed this is based on latest factory image. Wipe everything and flash per the OP.
http://forum.xda-developers.com/nexus-6/development/n6-shamu-lmy48i-deodexed-rooted-v1-0-08-t3176117

prdog1 said:
If want pure stock deodexed this is based on latest factory image. Wipe everything and flash per the OP.
http://forum.xda-developers.com/nexus-6/development/n6-shamu-lmy48i-deodexed-rooted-v1-0-08-t3176117
Click to expand...
Click to collapse
Thanks, I ended up finding a file that could be flashed via an adb command in twrp which let me issue the fastboot oem unlock command and I then flashed stock through twrp. I think I got it working now.

Error flashing ROM via adb sideload/fastboot

I decided to try and flash a custom rom as a .zip into my phone without using TWRP to play around. I first went into bootloader mode, then typed:
fastboot devices
fastboot flash zip Cyanogenmod.zip
Failed, error.
I also tried to use TWRP's adb sideload, swiped to run adb sideload, then typed
adb devices
adb sideload Cyanogenmod.zip
Failed,error.
Both times, there was no OS on the phone, I wiped everything prior.
Wasn't able to get either method to work. Am I doing something wrong ? Just like playing around and trying options to flash a ROM outside of TWRP.
I know how to flash .img files individually in fastboot, just not the .zip of custom ROMs.

mikeprius said:
I decided to try and flash a custom rom as a .zip into my phone without using TWRP to play around. I first went into bootloader mode, then typed:
fastboot devices
fastboot flash zip Cyanogenmod.zip
Failed, error.
I also tried to use TWRP's adb sideload, swiped to run adb sideload, then typed
adb devices
adb sideload Cyanogenmod.zip
Failed,error.
Both times, there was no OS on the phone, I wiped everything prior.
Wasn't able to get either method to work. Am I doing something wrong ? Just like playing around and trying options to flash a ROM outside of TWRP.
I know how to flash .img files individually in fastboot, just not the .zip of custom ROMs.
Click to expand...
Click to collapse
wrong? yes, very much so. first off, you can not flash roms like cm via fastboot. you use twrp to flash those roms. fastboot is only for flashing the factory image or .img files. secondly, you dont have to use adb to transfer files to your phone. twrp recovery has a native feature letting you move files to your phone without adb.

simms22 said:
wrong? yes, very much so. first off, you can not flash roms like cm via fastboot. you use twrp to flash those roms. fastboot is only for flashing the factory image or .img files. secondly, you dont have to use adb to transfer files to your phone. twrp recovery has a native feature letting you move files to your phone without adb.
Click to expand...
Click to collapse
Oh, so you can't flash a ROM .zip via adb ? I know how to do adb push into TWRP then flash the zip if that's what you were referring to ?
Fastboot cannot flash ROM .zips like TWRP ?

mikeprius said:
Oh, so you can't flash a ROM .zip via adb ? I know how to do adb push into TWRP then flash the zip if that's what you were referring to ?
Fastboot cannot flash ROM .zips like TWRP ?
Click to expand...
Click to collapse
Nope, only .img files can be flashed in fastboot.

mikeprius said:
Fastboot cannot flash ROM .zips like TWRP ?
Click to expand...
Click to collapse
nope. or we would just be using fastboot, and not twrp. but we need twrp to do it.

simms22 said:
nope. or we would just be using fastboot, and not twrp. but we need twrp to do it.
Click to expand...
Click to collapse
What does adb sideload do ? How is that different than adb pull for moving a .zip into the storage ??

Searching for adb sideload turned up this thread that pretty much has the two questions I currently have:
simms22 said:
twrp recovery has a native feature letting you move files to your phone without adb.
Click to expand...
Click to collapse
I did some searching for how to do this but the only thing I was able to come up with was changing storage to USB OTG and installing the files from there. Is that the method you were referring to?
mikeprius said:
What does adb sideload do ? How is that different than adb pull for moving a .zip into the storage ??
Click to expand...
Click to collapse
I too am now wondering about what adb sideload does. I thought it was for flashing .zip files, including ROM's. Is that incorrect? Does adb sideload work when there isn't an OS on the phone because USB Debugging can't be enabled?