Im trying to sideload magio rom rc6 on my htc one s. I start adb, i go to my computer and open cmd and then i ran the command "adb sideload magiorom_RC6.zip" i kept on getting "error:closed". I tried it multiple times but i still got the same error. Now im getting a message that says "error: more than one device and emulator". What should i do. Please Help!
_______________________________________________________________________________________________________
SOLVED:
What i did is before doing adb sideload rom.zip i did adb usb. That fixed the error
Related
Hey guy's only wanted to do a factory reset but I idiot just wiped everything...
So nothing was anymore on it. I downloaded this file:
OTA_M4_UL_K44_SENSE60_MR_HTC_Europe_4.09.401.3-3.10.401
As I have 4.09.401, CID-HTC__102...
So I was very lost and extracted firmware.zip out of it and flashed it over "fastboot oem rebootRUU" - "fastboot flash zip firmware.zip"
It is also now "Relocked" with S-OFF....
I'm stuck, I need my phone the next few days very often...
I dont know what to do anymore if I try to do the same with the OTA zip file it says FAILED (remote: 24 parsing android-info fail)
(When I tried before with TWRP ADB Sideload before I flashed the firmware.zip, it told me "file_getprop failed to stat /system/build.prop"
What can I do now to get my phone working again
Which version of hboot?
Which version of TWRP?
Are you able to connect to your phone via fastboot?
Are you able to connect to your phone via adb (from within TWRP)?
jollywhitefoot said:
Which version of hboot?
Which version of TWRP?
Are you able to connect to your phone via fastboot?
Are you able to connect to your phone via adb (from within TWRP)?
Click to expand...
Click to collapse
- HBOOT 2.22.000
- openrecovery-twrp-2.7.1.0-m4.img (It's the only version where I even can see my devices with "adb devices")
- Yes I am
- Not really I can go with ADB Sideload but using "adb sideload" does not work...
It tells me:
sending: 'rom.zip' 100%
On my phone it's saved under /data/media/sideload.zip but it tells me:
file_getprop: failed to stat "/system/build.prop": No such file or directory
E: Error executing updater binary in zip '/data/media/sideload.zip'
Click to expand...
Click to collapse
I had a similar issue. Adb only seemed to work on older version of twrp, except in reality, it wasn't working at all. First thing you need to do is get adb working fully to where you can push a Rom to your phone. The problem is likely your Windows drivers and not your phone, so quit trying to flash firmware to fix your phone. For me, I installed a clean copy of Windows xp on an old computer and then set fastboot and Adb up on it. I've also gotten adb and fastboot working using ubuntu live CD. I'll try and find instructions for that method (it's super easy and will run on your CD drive, so you don't need to format hd out install anything).
Once adb works, you can just push any sense6 Rom and then install in twrp and you'll be good to go.
Edit: read posts 17 & 22 here for information on getting ubuntu live CD to work.
http://forum.xda-developers.com/htc-one-mini/help/help-urgent-os-recovery-t2859034/page2
jollywhitefoot said:
I had a similar issue. Adb only seemed to work on older version of twrp, except in reality, it wasn't working at all. First thing you need to do is get adb working fully to where you can push a Rom to your phone. The problem is likely your Windows drivers and not your phone, so quit trying to flash firmware to fix your phone. For me, I installed a clean copy of Windows xp on an old computer and then set fastboot and Adb up on it. I've also gotten adb and fastboot working using ubuntu live CD. I'll try and find instructions for that method (it's super easy and will run on your CD drive, so you don't need to format hd out install anything).
Once adb works, you can just push any sense6 Rom and then install in twrp and you'll be good to go.
Edit: read posts 17 & 22 here for information on getting ubuntu live CD to work.
http://forum.xda-developers.com/htc-one-mini/help/help-urgent-os-recovery-t2859034/page2
Click to expand...
Click to collapse
The problem is that I cant install the ROM.
I've push'ed it do the ROM but as you can see my post above TWRP only gives me error :/
LuvMyHTC21 said:
Hey guy's only wanted to do a factory reset but I idiot just wiped everything...
So nothing was anymore on it. I downloaded this file:
OTA_M4_UL_K44_SENSE60_MR_HTC_Europe_4.09.401.3-3.10.401
As I have 4.09.401, CID-HTC__102...
So I was very lost and extracted firmware.zip out of it and flashed it over "fastboot oem rebootRUU" - "fastboot flash zip firmware.zip"
It is also now "Relocked" with S-OFF....
Click to expand...
Click to collapse
just try to flash not OTA, but ROM
version 2 from here will be Ok
Sweet Jesus, finally after 9 hours (no joke) I got it working, thank you so much !
Hi, need your help if possible. Trying to unbrick my phone via this tutorial:
https://www.youtube.com/watch?v=boyU1MnI7HU
When i need to flash ROM with "adb sideload" i get error "device not found"
fastboot devices give my phone code, i can flash recovery image without problems. only ADB SIDELOAD GIVE ME ERROR
Help me out please.
or tell me some other was to fix brick
PS: can be this coz of USB debugging is not enabled? cannot enable coz cannot start phone
If debuging usb is not enable adb wont detect your device :/
BuzzFuzz said:
Hi, need your help if possible. Trying to unbrick my phone via this tutorial:
https://www.youtube.com/watch?v=boyU1MnI7HU
When i need to flash ROM with "adb sideload" i get error "device not found"
fastboot devices give my phone code, i can flash recovery image without problems. only ADB SIDELOAD GIVE ME ERROR
Help me out please.
or tell me some other was to fix brick
PS: can be this coz of USB debugging is not enabled? cannot enable coz cannot start phone
Click to expand...
Click to collapse
What does typing "adb devices" give you?
BuzzFuzz said:
Hi, need your help if possible. Trying to unbrick my phone via this tutorial:
https://www.youtube.com/watch?v=boyU1MnI7HU
When i need to flash ROM with "adb sideload" i get error "device not found"
fastboot devices give my phone code, i can flash recovery image without problems. only ADB SIDELOAD GIVE ME ERROR
Help me out please.
or tell me some other was to fix brick
PS: can be this coz of USB debugging is not enabled? cannot enable coz cannot start phone
Click to expand...
Click to collapse
For using ADB sideload your phone must be booted to custom recovery e.g TWRP or CWM and SIDELOAD mode must be started manually.
Running Windows 7, was able to get adb drivers running and unlock the bootloader. The problem is trying to flash the TWRP image file. The img file is located in the folder where the adb exe file is located, but when I type in the command to flash the recovery (with the filename), I get a "<waiting for device>" message that simply hangs and doesn't go away. Computer has USB 2.0 and 3.0 ports and I've tried both and same result. Any ideas appreciated.
Billyjack555 said:
Running Windows 7, was able to get adb drivers running and unlock the bootloader. The problem is trying to flash the TWRP image file. The img file is located in the folder where the adb exe file is located, but when I type in the command to flash the recovery (with the filename), I get a "<waiting for device>" message that simply hangs and doesn't go away. Computer has USB 2.0 and 3.0 ports and I've tried both and same result. Any ideas appreciated.
Click to expand...
Click to collapse
You don't use adb in bootloader. Gotta use fastboot. Do you have fastboot.exe? If so, what do you get when you run fastboot devices?
Moto G XT1032
Hello,
I hope that you understand my English. I am kind of a layman concerning Android, but still wanted to install Cyanogenmod 13. I followed these instructions (can't post them apparently since I am new). Official instructions on the CM website. (Bootloader was already unlocked because I already installed Cyanogenmod 12, went back to Stock ROM and now tried to install CM13). Like alwas there were some minor errors during the first steps, but I handled them alright, I think.
The real problem started when I tried to install the zip-file of CM13 ("Installing CyanogenMod from recovery", step 8). I followed the instructions (wipe etc.), but the installation stopped at "Patching system image unconditionally" and it said something like "missing md5-file" although the file I downloaded on the TWRP website was right next to the recovery .img.
After trying and trying I started to go through the options in TWRP recovery (which was a fault, I know) and wiped some things that probably should not have been wiped. Next error message was: "unable to mount /system". New problem.
Then I thought, I might try the recovery that was right next to the downloadlink of the CM13 firmware. Installed it succesfully and tried again some things, now I have a bootloop and can't shut off the phone. When I shut it off, 1 second later the Google-screen with the open lock appears again". The only help was to manually shut it off with recovery.
I can't even start Android anymore, which means I can't activate USB-debugging, the installation files of CM13 are missing and the main problem: my PC only recognizes the phone in fast boot mode - I can't move files to the phone, it just says in the task bar: "Fastboot falcon S".
As soon as I enter recovery mode, the USB-sign on Windows vanishes.
Tried to move the files to the devices by "adb push cm-13.0-20160703-NIGHTLY-falcon.zip /scard", but it says "* daemon not running. starting it now on port 5037 *
* daemon startet successfully *
adb: error: connect failed: no devices/emulators found"
The device is not recognized by "fastboot devices" in cmd.
I hope that you understood everything. Already tried to get help in German forums, but nobody answered there.
And yeah, I definitely stopped trying to solve it by myself because I might just destroy it more.
Thanks for your help!
seems like we are on the same trolley.
I wanted to have a 100% clean system so I wiped everything.
I reinstall SDK, google drivers, motorola drivers, but no success. In fastboot mode it's written: USB connected, on the computer eject "Fastboot falcon S". I create file adb_usb.ini with id in it, restarted system, killed adb and so on. Tried different USB port, different cables.
Aendroit, if you find a way share.
I'm on W10 if that matters.
Ok. So I managed to go through the problem.
First, I was able to reinstall TWRP with fastboot (fastboot root twrp.....), so fastboot worked for me. Then it seems that on the main screen, where you choose options with volume buttons, fastboot works, but not adb.
I went into recovery and "adb shell" worked, so did "adb devices".
I used push command and so on.
I'm glad you got the solution now. Unfortunately I can't follow the instructions. Could you please take me through it step by step ("fastboot root twrp", I never used a command like this before). Thanks!
Because when I go in recovery and type in "adb shell" or "adb shell" on my computer, it says "no devices/emulators found".
Update: Got it. I can enter TWRP now, but in the installation log it said "Mismatched partition size (recovery)" at the end. If someone knows what that means ...
I meant: fastboot flash recovery twrp-3.0.0.0_2-falcon.img
Mismatched size is just an information, nothing to worry about. Now, when you are in TWRP try to check the device "adb devices", should work.
Thank you, my computer recognizes the device again! I was able to copy the files to my phone. Unfortunately I still can't install a custom rom. I tried Mokee instead of CM13 now and i always get the same messages:
"Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Target: 146758281
Detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system" and so on.
I don't know what that is supposed to mean ...
Well, I'm not very good oriented in all this stuff, so I don't know why you got those problems, far from being a dev.
I copied ressurection ROM + open gapps nano (thou I always used banks, but this time wanted to save more free space) and installed it via TWRP without any issues.
Thank you for the answer. Mokee works now! I'm not happy that I can't use CM13, but I got Mokee working after a while and I'm glad about it.
I have a LG stylo 4 and i was trying to root it, well i saw here that some had problems doing so, but i gave it a shot, i was able to enable OEM unlock, and usb debugging, i found boot.img file and i was about to root.
But when i plugged in the phone to my pc and opened adb and entered the command "adb reboot fastboot" the phone just restarted normally. i tried "adb reboot recovery" i the screen saying "no command".
Now the only thing i got to work with adb was to use sideload, when i did this, i got adb to be able to talk to the device.
im wondering if i can use sideload to root the phone?