hello
I am unable to enable 'adb sideload' mode on my twrp. it loops and ends up failing
We need more information. Which version of TWRP are you using?
Hello
I installed the following twrp version: recovery_h870_20180813-1.img
Related
Hi,
I have installed TWRP 2.7.1.1.
If I am in TWRP recovery mode my adb (on Linux) doesn't see the device.
Only if I switch to USB sideload, adb sees the device but doesn't allow to open a shell.
Furthermore, with CWM recovery, it just works.
But I do need TWRP since CWM doesn't have f2fs support, yet.
Many thanks for a hint,
Helmut
[Emergency Guide] How to Blank or regenerate Watch (WA 5.01) after clearing \system
Prerequisit :
Be sure to have latest adb (1.0.32) and fastboot version. Download it from here
Link to know how to enter into fastboot
Under Fastboot
Download boot from here
Code:
- fastboot flash boot bootll.img
Download TWRP recovery from here
Code:
- fastboot flash recovery twrp.img
Go to Recovery and format all twice with TWRP recovery
Flashing back stock recovery :
Download stock recovery from here
Code:
- fastboot flash recovery recoverll.img
Back to stock recovery, format twice
Regenereting system step :
Download rooted AW 5.01 system directory from here
Code:
- fastboot flash system system.img
Go back to stock recovery, Choose apply update from ADB (adb sideload)
Download AW 5.01 update from here
Code:
- adb sideload 149e0c34d0ab10d3e356d6301915dcc04552d9db.signed-lenok-LWX48P-from-KNX01R.149e0c34.zip
Reboot system now. Choose langage, etc.
Nota : At this time, if you don't need root and Chainfire SU (witch is useless at this time) you can go just for flashing TWRP by :
Code:
- adb reboot bootloader
- fastboot flash recovery twrp.img
And that's it.
Or following steps : Rooting back Watch and custom TWRP Recovery support
Download stock rooted AW 5.01 system directory from here
Code:
- adb reboot bootloader
- fastboot flash system system.img
Reboot Watch, autorize adb debug on the watch
Download Chainfire SU 2.40 from here or BETA-SuperSU-v2.42.zip
Note : You can remove Superuser.apk from the zip file into \common recovery which it is not compatible with AW 5.01
Pushing SU to the watch
Code:
- adb push supersu.zip /sdcard/su.zip
Back to Fastmod and flashing TWRP advanced recovery
Code:
- adb reboot bootloader
- fastboot flash recovery twrp.img
Restart watch and go to TWRP recovery, install/flash su.zip from sdcard, reboot
Et Voilà !
Nice write up, I'm not sure doing the adb sideload does anything though. The system image is already patched, it was a backup from my device just rooted. Currently I have busybox working on the device and and working on init.d support so any changes we want to make will survive after reboot.
Sent from my A0001 using XDA Free mobile app
It'ill be nice :good:
HELP
I've done everything to try to get back to AW 5.01 but when I get to the adb sidelload part it says "error: device not found".
It's seem that windows 8 is not detecting my watch. Anyone have any insight on this would be great thanks!
Jay
edit...
Never Mind Got it to Work!
How did you get it to work?
I managed it, too. Turns out I had to reinstall drivers while in sideload mode. You can do it in device manager, select from computer, from list and find ADB composite device.
Hey guys, I accidentaly installed supersu apk on my watch and now I can see it in the menu all the time. How can I remove it from /system/app/SuperSu? Do I have to root first in order to gain rw rights on /system, remove whole SuperSu folder than do a factory reset for example and it won't show up anymore?
hornedfiend said:
Hey guys, I accidentaly installed supersu apk on my watch and now I can see it in the menu all the time. How can I remove it from /system/app/SuperSu? Do I have to root first in order to gain rw rights on /system, remove whole SuperSu folder than do a factory reset for example and it won't show up anymore?
Click to expand...
Click to collapse
simply flash this in twrp > https://hostr.co/3yMSrXUUMD8B and it will remove for you and you will get root also
[Update]: Now it says no OS installed in TWRP. I think I have wiped the os by mistake. Just need to know how to install cm13 image using fastboot or ADB. Please help!
I wasn't aware if SuperSU works with CM13 and I installed the app, on request to update the binaries, I selected TWRP/CWM method because the normal mode didn't work. After the reboot the phone won't load into os, its stuck on the CM boot screen. I don't have a CM image on my sd therefore unable to flash again either. Is there a way to push files (cm img) to my phone? I have adb/adb over network enabled as well from developer options. I just need a way to put files into my sd card and flash using TWRP. Please help! this is urgent! :crying:
[SOLVED][HOW TO]
This is in a situation where you've messed up your system and don't have the image file stored in your sd card for quick flashing. Make sure you're using the latest USB drivers and ADB binaries 1.0.32+
- Get into TWRP
- Swipe to ADB Sideload and enable it
- On your desktop, open command and type "Adb sideload filename.zip" [Filename here is the filename of your flashable zip/rom]
- Once you the installation finishes, reboot twrp normally into system
dibyajyoti said:
I just need a way to put files into my sd card and flash using TWRP. Please help! this is urgent! :crying:
Click to expand...
Click to collapse
Have you tried enabling MTP in TWRP and using a computer to transfer the image over?
Contact me if you have any questions.
R55770 said:
Have you tried enabling MTP in TWRP and using a computer to transfer the image over?
Contact me if you have any questions.
Click to expand...
Click to collapse
MTP shows as enabled - But the device doesn't show up in my pc. I'm connected through USB in TWRP recovery. I have android debugging also enabled, when trying adb push command, it shows adb devices attached as empty.
[Update]: I am trying to push the file using ADB Sideload in TWRP, the error I get is my adb needs to be updated to 1.0.32. How do i get updated adb 1.0.32?
[Update 2]: So I managed to update by ADB on desktop, and push the zip file using adb sideload in twrp. The zip is being installed as I write this. Lets hope this works!
[Update 3]: Got the rom to install via ADB sideload, though all my apps and settings are gone Anyway, I got the phone back for immediate use. Phew!
dibyajyoti said:
MTP shows as enabled - But the device doesn't show up in my pc. I'm connected through USB in TWRP recovery. I have android debugging also enabled, when trying adb push command, it shows adb devices attached as empty.
[Update]: I am trying to push the file using ADB Sideload in TWRP, the error I get is my adb needs to be updated to 1.0.32. How do i get updated adb 1.0.32?
[Update 2]: So I managed to update by ADB on desktop, and push the zip file using adb sideload in twrp. The zip is being installed as I write this. Lets hope this works!
[Update 3]: Got the rom to install via ADB sideload, though all my apps and settings are gone Anyway, I got the phone back for immediate use. Phew!
Click to expand...
Click to collapse
Great. Thanks for letting us know.
Hello. I ported latest twrp from nexus 2012 to ouya. You can't install it because ouya don't have enough space on recovery partition. You need to boot it from fast boot
fastboot boot recovery.img
download: http://www.mediafire.com/file/7gyb6xjdwr8k3n0/recovery.img
Everything is working
I recommend to disable screen timeout after first boot
Not a single custom recarevi is flashed (writes abortet), being in the stock recovery with the command in the command line adb sideload. Tried using commands in the command line, and put programs like Flashify (for root users) and Rashr - Flash Tool ,does not help, error.
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.