I have a Q706F using Global ROM. Have Unlocked the Bootloader, magisk install and change to TWRP.
Caught a OTA but cannot install. Found the OTA.ZIP and try flashing in TWRP but there was a error (device on SUPER....)
How to you guy flash these OTA.zip?
Put TWRP in sideload mode, and sideload the OTA via ADB: adb sideload ota.zip
V0latyle said:
Put TWRP in sideload mode, and sideload the OTA via ADB: adb sideload ota.zip
Click to expand...
Click to collapse
Tried this but it have the same error of device on Super
Related
downloaded ota.zip and did adb sideload
The update aborts with the massage:
"/system/vendor/etc/audio_effects.conf" has unexpected contents
Do have unmodified 4.4.4
I had root on 9.0.2 did an full OTA 1,5gb even did install magisk on the second slot before rebooting the update. I tried using the one plus one click root tool but that's not working either. Does anyone has an idea what I'm doing wrong ?
Thanks for any help
Fastboot boot Blu_spark.twrp.img
Flash magisk 18.zip
Now you should be rooted
whizeguy said:
Fastboot boot Blu_spark.twrp.img
Flash magisk 18.zip
Now you should be rooted
Click to expand...
Click to collapse
I am still on 9.0.2. So can I download the complete stock rom.zip with blu_spark.twrp.img and boot into it via shell comand on phone and then flash the update , reboot the recovery and then the magisk?
Just Flash the full update in twrp following flashing twrp again before you reboot.
Also I would recommend to not reboot to system then, instead reboot to recovery again and flash full update + twrp again, this time also magisk and then reboot the system.
This way you have updated and rooted both slots and have twrp in place
went to OTA Pie.
Bootloader is unlocked, but phone is S-On.
I'd like to TWRP then Magisk.
From Download mode (to install TWRP) I get "command not found" when I enter fastboot flash recovery twrp.img.
What am I doing wrong?
metropical said:
went to OTA Pie.
Bootloader is unlocked, but phone is S-On.
I'd like to TWRP then Magisk.
From Download mode (to install TWRP) I get "command not found" when I enter fastboot flash recovery twrp.img.
What am I doing wrong?
Click to expand...
Click to collapse
Put twrp.img into directory with adb and fastboot files for Win OS.
Command line must be run from directory where you have adb, fastboot and twrp.img.
same for Mac OS. Done this many times over the years. But not working with Pie on U11.
In Bootloader or Download I get: command not found for either fastboot devices or fastboot flash recovery /Users/fritz/Downloads/•\ android/twrp-3.4.img.
But adb works fine.
Showing modified and S-On, both of which I don't think I had with Oreo.
I had the wrong fastboot version. TWRP and Magisk are in.
For anyone looking for the right adb & fastboot tools for Mac OS, the link on this page, even though old, is good.
Android Basics: How to Install ADB & Fastboot on Mac, Linux & Windows
ADB and Fastboot are probably the most essential tools for any Android aficionado. They can do everything from backing up your device to unlocking your bootloader with a few simple steps. This paves the way for many new tweaks and customizations that weren't possible before. The required...
android.gadgethacks.com
I accidentally flash and overwrite settings.jar and settings.odex in system framework that causes the bootloop.
Re-flash Stock ROM.
jwoegerbauer said:
Re-flash Stock ROM.
Click to expand...
Click to collapse
How to reflash stock rom? I tried to boot in to recovery mode but it did not show up the recovery menu.
iluvtorock26 said:
How to reflash stock rom? I tried to boot in to recovery mode but it did not show up the recovery menu.
Click to expand...
Click to collapse
Re-flashing Stock ROM typicaly is done by tools provided by OEM/Carrier or by ADB Sideload method.
Code:
adb devices
adb reboot sideload
adb sideload <STOCK-ROM.ZIP>
jwoegerbauer said:
Re-flashing Stock ROM typicaly is done by tools provided by OEM/Carrier or by ADB Sideload method.
Code:
adb devices
adb reboot sideload
adb sideload <STOCK-ROM.ZIP>
Click to expand...
Click to collapse
same as recovery mode, sideload also not accessible.
iluvtorock26 said:
same as recovery mode, sideload also not accessible.
Click to expand...
Click to collapse
How did you verify this?
BTW: With Android 4.3.1 ADB Sideload was introduced.
jwoegerbauer said:
How did you verify this?
BTW: With Android 4.3.1 ADB Sideload was introduced.
Click to expand...
Click to collapse
the device just keeps on rebooting, there's no menu or any ui that will display except for logo in boot screen..
and when I tried to sideload the app it says adbre-KitKat sideload connection failed: closed
What happens when you enter these
Code:
adb devices
adb get-state
adb reboot fastboot
adb get-state
fastboot flashall <STOCK-ROM.ZIP>
commands - preferredly stored in a Windows batch-file?
jwoegerbauer said:
What happens when you enter these
Code:
adb devices
adb get-state
adb reboot fastboot
adb get-state
fastboot flashall <STOCK-ROM.ZIP>
commands - preferredly stored in a Windows batch-file?
Click to expand...
Click to collapse
List of devices attached
0123456789ABCDEF device
device
error: no devices/emulators found
< waiting for any device >
I was using a gsi image then I decided to go back to stock rom
I used after sales tools made for transsiom devices(infinix, Tecno,Itel)
After it flashed boot and recovery and on getting to super image it showed an error message 'sending failed' this file doesn't match with the one in the device
Now when I try to power on it tells me
Dm verity corrupted
I can't access fastboot nor recovery
If I press power button to continue it remains stuck on boot logo
Please this is urgent
The device is not mine
Re-flash Stock ROM using ADB Sideload method.
jwoegerbauer said:
Re-flash Stock ROM using ADB Sideload method.
Click to expand...
Click to collapse
Please how
Code:
adb devices
adb reboot sideload
adb sideload <FULL-PATH-NAME-OF-STOCK-ROM-ZIP-FILE>
adb reboot
jwoegerbauer said:
Code:
adb devices
adb reboot sideload
adb sideload <FULL-PATH-NAME-OF-STOCK-ROM-ZIP-FILE>
adb reboot
Click to expand...
Click to collapse
Thanks
Will try it
I solved it by flashing empty vbmeta using
fastboot --disable-verity --disable verification flash vbmeta emptyvbmeta.img
Click to expand...
Click to collapse