Hello,
First and foremost I would like to give the important information away:
Phone: HTC One (M7)
Carrier: Rogers (I think same as AT&T?)
State: Unlocked, S-On, TWRP v2.7.1.0 installed, Hboot 1.57 and without an OS
The story:
Advance Wiped Everything:
So I didn't transfer the ROM before I used the "wipe" option in TWRP and deleted everything (using advanced wipe). Now I'm left with a phone that is "soft-bricked".
ADB Sideload
I rooted and installed TWRP my phone using QbKing77's guide
I tried googling a soultion and found a guide that told me to enter TWRP->Advanced->ADB Sideload and realized my phone cannot enter ABD sideload mode...so I'm like there must be another way, so I look up ADB push and again the same problem...it wont work. ADB shows: "error:device not found" in cmd.
Drivers
Now I think the problem is in the driver and I have reinstalled all the correct drivers (including Android SDK Google USB drivers). Then it strikes me that if the problem is with the drivers why was I able to use fastboot and not ADB?
RUU
After 4 hours of trying I gave up and was like lets try a RUU, same freaking problem. I get error code 155 which after researching seems to be pointing at my phone's bootloader not being "Re-locked" when the freaking screen says ***tampered*** re-locked****. So now I have unlocked it again and relocked the bootloader again, still no luck. I tried downloading different RUUs for both Rogers and AT&T and both give that exact same error even after "fastboot oem lock" command. After giving up on that I go back to try to entter ADB sideload mode via TWRP, I downloaded TWRP 2.5-2.7 and none of them would allow me to enter ADB sideload mode.. As of now its been 1 hour and TWRP still states: "Starting ADB sideload feature...".
Conclusion
If there is any way to get my phone to it's stock settings (IDC about the tampered, and relocked messages) I am all ears, I'm sorry if the information given isn't organized enough, but I'm very exhausted at this point. I will be more than happy to answer any more questions anybody might have.
Thanks!
haqsaber said:
Hello,
First and foremost I would like to give the important information away:
Phone: HTC One (M7)
Carrier: Rogers (I think same as AT&T?)
State: Unlocked, S-On, TWRP v2.7.1.0 installed, Hboot 1.57 and without an OS
The story:
Advance Wiped Everything:
So I didn't transfer the ROM before I used the "wipe" option in TWRP and deleted everything (using advanced wipe). Now I'm left with a phone that is "soft-bricked".
ADB Sideload
I rooted and installed TWRP my phone using QbKing77's guide
I tried googling a soultion and found a guide that told me to enter TWRP->Advanced->ADB Sideload and realized my phone cannot enter ABD sideload mode...so I'm like there must be another way, so I look up ADB push and again the same problem...it wont work. ADB shows: "error:device not found" in cmd.
Drivers
Now I think the problem is in the driver and I have reinstalled all the correct drivers (including Android SDK Google USB drivers). Then it strikes me that if the problem is with the drivers why was I able to use fastboot and not ADB?
RUU
After 4 hours of trying I gave up and was like lets try a RUU, same freaking problem. I get error code 155 which after researching seems to be pointing at my phone's bootloader not being "Re-locked" when the freaking screen says ***tampered*** re-locked****. So now I have unlocked it again and relocked the bootloader again, still no luck. I tried downloading different RUUs for both Rogers and AT&T and both give that exact same error even after "fastboot oem lock" command. After giving up on that I go back to try to entter ADB sideload mode via TWRP, I downloaded TWRP 2.5-2.7 and none of them would allow me to enter ADB sideload mode.. As of now its been 1 hour and TWRP still states: "Starting ADB sideload feature...".
Conclusion
If there is any way to get my phone to it's stock settings (IDC about the tampered, and relocked messages) I am all ears, I'm sorry if the information given isn't organized enough, but I'm very exhausted at this point. I will be more than happy to answer any more questions anybody might have.
Thanks!
Click to expand...
Click to collapse
first, do not use twrp 2.7.1.0 but 2.6.3.3 and use HTC divers not Google drivers. you will then be able to sideload or push a rom to your phone. Also make sure to use at least adb 1.0.29, sideload will not work on previous version.
alray said:
first, do not use twrp 2.7.1.0 but 2.6.3.3 and use HTC divers not Google drivers. you will then be able to sideload or push a rom to your phone. Also make sure to use at least adb 1.0.29, sideload will not work on previous version.
Click to expand...
Click to collapse
Thanks for your response.
I have flashed TWRP 2.6.3.3, and when I boot into recovery it asks me for a password? I was still unable to boot up ADB sideload (This time I get an error message instead of it failing to start all together). But I was able to access the adb shell and was able to push a custom rom into the device into /data/ and then tried installing it, which failed.
I flashed the ROM using this command: fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
then after the transfer was done typed: fastboot erase cache
as of now when I type adb devices into the command prompt my phone is being detected which is an improvement from last night! Thanks!
haqsaber said:
Thanks for your response.
I have flashed TWRP 2.6.3.3, and when I boot into recovery it asks me for a password? I was still unable to boot up ADB sideload (This time I get an error message instead of it failing to start all together). But I was able to access the adb shell and was able to push a custom rom into the device into /data/ and then tried installing it, which failed.
Click to expand...
Click to collapse
you don't have to use an adb shell to push a rom, only use adb normally from your computer with the phone booted in recovery. And the destination of the rom when you push it is not /data, its /sdcard
adb push name_of_rom.zip /sdcard/
when complete, select "install" in recovery and choose your rom.
alray said:
you don't have to use an adb shell to push a rom, only use adb normally from your computer with the phone booted in recovery. And the destination of the rom when you push it is not /data, its /sdcard
adb push name_of_rom.zip /sdcard/
when complete, select "install" in recovery and choose your rom.
Click to expand...
Click to collapse
The rom.zip is now in my /sdcard/ folder and when I try to install it I get the following error:
Code:
Updating partition details....
E:Unable to mount '/cache'
E:Unable to mount '/cache'
E:Unable to mount '/cache'
Error Flashing zip '/sdcard/rom.zip'
Updating partition details...
E:Unable to mount '/cache'
and my ADB version is 1.0.31
Edit: So I went in the mount option and noticed that "cache" was selected so I deselected it and tried to flash again and it just said
Code:
Error Flashing zip '/sdcard/rom.zip'
Updating partition details...
So now I'm thinking there must be something wrong with the ROM, so i'm downloading and will retry.
Code:
KitKat (Android 4.4.3 + HTC Sense 6.0)
Download Android Revolution HD 81.0
Nope, that didn't work either. Could it be that I need to put in that password first? If so what is the TWRP password?
haqsaber said:
The rom.zip is now in my /sdcard/ folder and when I try to install it I get the following error:
Code:
Updating partition details....
E:Unable to mount '/cache'
E:Unable to mount '/cache'
E:Unable to mount '/cache'
Error Flashing zip '/sdcard/rom.zip'
Updating partition details...
E:Unable to mount '/cache'
and my ADB version is 1.0.31
Edit: So I went in the mount option and noticed that "cache" was selected so I deselected it and tried to flash again and it just said
Code:
Error Flashing zip '/sdcard/rom.zip'
Updating partition details...
So now I'm thinking there must be something wrong with the ROM, so i'm downloading and will retry.
Code:
KitKat (Android 4.4.3 + HTC Sense 6.0)
Download Android Revolution HD 81.0
Nope, that didn't work either. Could it be that I need to put in that password first? If so what is the TWRP password?
Click to expand...
Click to collapse
looks like you have enabled data encryption in the OS...
in twrp wipe everything and format data
then push the rom again and install it.
alray said:
looks like you have enabled data encryption in the OS...
in twrp wipe everything and format data
then push the rom again and install it.
Click to expand...
Click to collapse
And that worked! Thank you so much!!
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
I want to flash a custom Rom but my SD Slot is Brocken.
Can i flash with Flash tool?
If you are using TWRP? Send the ROM to the device.
Activate ADB sideload via TWRP and "adb sideload xxx-yyy-zzzz.zip/img" from CLI/CMD
Or, extract the image from zip/xz and "fastboot flash system xxx-yyy-zzz.img" from CLI/CMD
How to Flash GSIs through Fastboot
I'M NOT AT ALL RECOMMENDING Y'ALL TO TRY THIS OUT ! CUSTOM ROMS WILL COME SOON WHICH IS FAR BETTER THAN GSIs PLEASE FOLLOW THIS GUIDE AT YOUR OWN RISK !, THIS GUIDE MIGHT BE THE SAME FOR MOST DEVICES BUT IM SPECIFICALLY MAKING THIS FOR G40...
forum.xda-developers.com
KJOz68 said:
If you are using TWRP? Send the ROM to the device.
Activate ADB sideload via TWRP and "adb sideload xxx-yyy-zzzz.zip/img" from CLI/CMD
Or, extract the image from zip/xz and "fastboot flash system xxx-yyy-zzz.img" from CLI/CMD
How to Flash GSIs through Fastboot
I'M NOT AT ALL RECOMMENDING Y'ALL TO TRY THIS OUT ! CUSTOM ROMS WILL COME SOON WHICH IS FAR BETTER THAN GSIs PLEASE FOLLOW THIS GUIDE AT YOUR OWN RISK !, THIS GUIDE MIGHT BE THE SAME FOR MOST DEVICES BUT IM SPECIFICALLY MAKING THIS FOR G40...
forum.xda-developers.com
Click to expand...
Click to collapse
Thx, do know any Instructions. I tried that yesterday, but I don't really know how it works.
when i extract lineage 14.1 i have a boot.img and system.new.dat
is system dat the same like img?
Code:
C:\platform-tools>adb sideload lineage.zip
adb server version (39) doesn't match this client (41); killing...
* daemon started successfully
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found
C:\platform-tools>
It works, thx for help.
Excellent. Glad you've figured it out!!
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!