I have no issues with TWRP, but the current popular ROMs come with their own Recovery: Pixel Experience 20230419-1745, crDroid 9.4, LineageOS 19.1.
For all three, I get the same problem with ADB sideload (latest macOS platform tools) their Recovery. After performing Factory reset/Format data, I chose Apply update, then Apply from ADB. Then I executed the command on macOS: adb sideload <rom filename>, and almost immediately, the adb command is stuck/hanged at 0%. On the Recovery console, they get stuck / were waiting:
Lineage OS and crDroid:
Code:
Supported API: 3
Finding update package...
Verifying update package...
(nothing happens!)
Pixel Experience:
Code:
Supported API: 3
Finding update package...
Installing update...
(nothing happens!)
I looked at the lastlog (attached) but not sure what's wrong.
I tried flashing to the latest Recovery ROM gemini_global_images_V10.2.2.0.OAAMIXM_20190115.0000.00_8.0_global but that didn't help. I also ensured the downloads are correct by verifying their hashes.
Any ideas what's going on? How do I fix this? Thank you!
Update: I tried platform-tools version 33.0.3-8952118, and it works! The latest version 34.0.1-9680074 gave me the errors! I have no idea why!
Related
Hi everyone,
I received HTCs latest update via OTA yesterday. However, I can't install it.
I am on the rooted stock firmware with CWM as Recovery.
Once the Phone reboots, to install the update it simply goes to CWM and states that it can't find the file.
When I select it manually the following happens:
Code:
-- Installing: /sdcard/Download/OTA_M7_UL_JB_50_HTC_Europe_1.29.401.12-1.28.401.7_release_315849_signedp7v18dqsvls0ht0.zip
Finding update package...
Opening update package...
Installing update...
Preparing reset_system.ko...
Preparing busybox...
Preparing bug_fix1 tool...
Running bug_fix1 tool...
assert failed: check_cid(getprop("ro.cid"), "00000000", "11111111", "22222222", "33333333", "44444444", "55555555", "66666666", "77777777", "88888888", "999999999", "HTC__001", "HTC__E11", "HTC__102", "HTC__203", "HTC__405", "HTC__Y13", "HTC__304", "HTC__032", "HTC__A07", "HTC__J15", "HTC__016") == "t"
E: Error in /sdcard/Download/OTA_M7_UL_JB_50_HTC_Europe_1.29.401.12-1.28.401.7_release_315849_signedp7v18dqsvls0ht0.zip
(Status 7)
Installation aborted.
I deleted and downloaded (again via OTA) the zip to no avail.
Does anyone know what goes wrong here?
I believe you need stock recovery in order to flash OTA updates from HTC.
Do I have any chance to install the update without having to wipe my phone then aka. is there a zip anywhere that can be flashed with a custom recovery ?
Trying to root Huawei Honor 8 (FRD-L09, build no. FRD-L09C432B360, Android version 7.0), following this guide: https://www.xda-developers.com/honor-8-root-twrp-and-xposed/
I'm a bit of a noob, but can follow instructions. Some things didn't work, so I tried changing things up. Such as getting a newer version of TWRP, because the one in the guide didn't want to boot.
TWRP (twrp-3.1.0-2-frd.img) installed with adb.
Using SuperSU-v2.79-201612051815.zip. When starting the flash, it starts fine, but suddenly stops at "mounting image", then the phone reboots into the normal desktop.
I also tried to ADB sideload:
Code:
C:\platform-tools>adb sideload SuperSU-v2.79-201612051815.zip
loading: 'SuperSU-v2.79-201612051815.zip'...
connecting...
serving: 'SuperSU-v2.79-201612051815.zip' (~69%) * failed to read command: No error
Tried redownloading the zip, same result.
LOGS:
TWRP:
Code:
C:\platform-tools>adb pull /cache/recovery/last_log
adb: error: remote object '/cache/recovery/last_log' does not exist
SULOG.TXT.
download here: https://www.dropbox.com/s/5ov273kk3e3svf1/sulog.txt?dl=0
Hello folks,
I have exactly the same issue !!
I've just spend 2 nights on xda and a few other forums and I ran out of clues and things to try.
I really hope someone will know what is it about
Thank you very much.
Hello everyone. My problem is bootloop. I searched this forum before I post my own problem. Im trying to solve bootloop problem for 2 days. So I learned couple things. I had no idea what was fastboot and adp before.
Let me tell you what caused bootloop. I was using 6.0.1 firmware and my phone started working slowly. So I thought maybe new update fix that. I updated my phone and it was still slow. Then I looked that up on the internet. Some people said wipe your cache that might fix slow working zenfone. I put my phone on recovery mode and wiped cache and it caused bootloop. I started to search for my new problem. Found one with cmd command flashall. It turned my phone firmware to 1.17.40.1234 from 21.40.1220.2179. And then I downloaded raw ze550kl rom for my current firmware which is 1.17.40.1234. Extracted recovery.img boot.img and system.img
and used following commands :
fastboot devices
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system.img
fastboot commands worked with no problem and then I switched to recovery mode again and used this command:
adb sideload ZE550KL_WW_1.17.40.1234-20180205T165447Z-001.zip.If I tried to use raw rom as i mentioned before ,cmd says *cannot read. So I used this firmware from asus website.
last command causes this error on pc
C:\Program Files (x86)\Minimal ADB and Fastboot>adb sideload ZE550KL_WW_1.17.40.1234-20180205T165447Z-001.zip
loading: 'ZE550KL_WW_1.17.40.1234-20180205T165447Z-001.zip'adb server version (32) doesn't match this client (36); killing...
* daemon started successfully *
Total xfer: 0.00x
and on my phone this error shows up
Finding update package...
Opening update package...
Verifying update package...
E:footer is wrong
E:signature verification failed
Installation aborted.
Bootloop problem still exists so I tried to use different method which was flashtools. I got "Run flash image script failured" error. I tried to fix it but no luck.
Lastly I tried to apply update from sdcard but my phone cant read on sdcard for some reason and that sdcard is being used my little brother(it works).
What can I do to revive my phone ? Please help me.
Ankeroth said:
Hello everyone. My problem is bootloop. I searched this forum before I post my own problem. Im trying to solve bootloop problem for 2 days. So I learned couple things. I had no idea what was fastboot and adp before.
Let me tell you what caused bootloop. I was using 6.0.1 firmware and my phone started working slowly. So I thought maybe new update fix that. I updated my phone and it was still slow. Then I looked that up on the internet. Some people said wipe your cache that might fix slow working zenfone. I put my phone on recovery mode and wiped cache and it caused bootloop. I started to search for my new problem. Found one with cmd command flashall. It turned my phone firmware to 1.17.40.1234 from 21.40.1220.2179. And then I downloaded raw ze550kl rom for my current firmware which is 1.17.40.1234. Extracted recovery.img boot.img and system.img
and used following commands :
fastboot devices
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system.img
fastboot commands worked with no problem and then I switched to recovery mode again and used this command:
adb sideload ZE550KL_WW_1.17.40.1234-20180205T165447Z-001.zip.If I tried to use raw rom as i mentioned before ,cmd says *cannot read. So I used this firmware from asus website.
last command causes this error on pc
C:\Program Files (x86)\Minimal ADB and Fastboot>adb sideload ZE550KL_WW_1.17.40.1234-20180205T165447Z-001.zip
loading: 'ZE550KL_WW_1.17.40.1234-20180205T165447Z-001.zip'adb server version (32) doesn't match this client (36); killing...
* daemon started successfully *
Total xfer: 0.00x
and on my phone this error shows up
Finding update package...
Opening update package...
Verifying update package...
E:footer is wrong
E:signature verification failed
Installation aborted.
Bootloop problem still exists so I tried to use different method which was flashtools. I got "Run flash image script failured" error. I tried to fix it but no luck.
Lastly I tried to apply update from sdcard but my phone cant read on sdcard for some reason and that sdcard is being used my little brother(it works).
What can I do to revive my phone ? Please help me.
Click to expand...
Click to collapse
First download latest official build and don't do any edit or repack of zip .. Copy that ROM in the SD card make sure SD card works or format SD card into fat32 file system and copy ROM in it .. Go to phone recovery .. Hit update from SD card choose the zip wait till it flash if u still fail comment here .. I will give u alternatives
Hi
I am trying to install magisk 16.7 on my doogee s60 Lite android 7.0 phone. Sticking to v16 in hope google pay works.
I have unlocked bootloader in dev options, restarted into phone's native recovery mode, selected apply update from sd card, selected magisk zip file but after verification install aborted.
So I chose update from adb, which got me into bootloader, prompt now send the package
connected phone to windows 7 machine with drivers installed
adb devices
-> started successfully
typed adb sideload magisk-v16.7.zip/
and here is the response:
->sideload connection failed: no devices found
How to fix that?
You either fastboot flash the boot image that you first patch through the Magisk Manager, or you flash the Magisk zip in a custom recovery. Using the stock recovery or adb sideload won't work.
Hey, since I updated my Tablet it is rebooting everytime. I tried to factory reset it, cache clearing and even flashed it with another ROM. But that didn't help.
So my next step is to downgrade it because it worked probably on the older version. I tried flashing Lineage 15.1 and 14.1 but I get an error everytime.
Code:
adb: sideload connection failed: closed
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: closed
Thanks in advance!