Runing flash command without the parameters --disable-verity --disable-verification throws no error message, but cause a boot loop (state orange, untrustet, restart after 5 sec)
thanks for your answer, i would need help first in the problem why “fastboot flash --disable-verity --disable-verification boot boot.img” causes “terminating with uncaught exception of type std::out_of_range: basic_string”
The boot loop is the second issue, but (i think) caused by flashing boot.img without the parameters “-disable-verity --disable-verification”
on XDA found this:
Disable AVB by flashing stock vbmeta.img with the following command: “fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img”.
Where can i find this vbmeta.img here? Suppose with that command above and running astboot flash boot boot.img
i will not get a boot loop? And btw. running the easy installer wont work, if decvice is in fastboot mode? Unfortunaltey recovery or normal mode runs in boot loop, therefore no usb detection possible.
Solved the error “terminating with uncaught exception of type std::out_of_range: basic_string” by using the correct (latest) version of platform tools adb and fastboot.
Hope this helps other users running into this error too…
Which fastboot version did you use?
I use fastboot 31.0.2 from Android SDK (Linux) but the error “terminating with uncaught exception of type std::out_of_range: basic_string” raises with this version.
Will trying to downgrade to 31.0.1 or 30.0.5 again.
Had also tried to downgrade this morning, with SDK manager by removing SDK 31, reinstalling SDK 30 / platform tools. But it always installs platform tools with version 31, nevertheless only SDK 30 is installed.
Edit: With Platform Tools 30.0.5 (separately installed) it works.
I have the same problem as the op with a GS290. I used an up-to-date version of adb/fastboot (31.0.0-x instead of 30.0.5) and due to the error went with fastboot flash boot boot.img without the --disable-verity --disable verification options, got an OK exit status and rebooted. Now I’m in a bootloop and can’t get fastboot mode to recognise my device. Tried adb devicesadb reconnect and adb usb. No devices found. I’m on linux. What are my options now?
With volume up I can boot into e recovery v0.14, because system.img and recovery.img flashing (to v0.17) was error-free. From the recovery screen with ‘enabled adb’ (from advanced options) the fastboot flash --disable-verity --disable-verification boot boot.img command didn’t work. I don’t want to brick the phone so I’ve stopped here.
Will the new eOS 0.19 stabile release be applicable with updated versions of the Android tools? I have downloaded the linked Android-tools v30.0.5 in the post above.
error
terminate called after throwing an instance of ‘std::out_of_range’
what(): basic_string::compare: __pos (which is 33554368) > this->size() (which is 0)
Annullato (core dump creato)
Will the new eOS 0.19 stabile release be applicable with updated versions of the Android tools?
I don’t think there is any evidence that platform-tools v30.0.5 is sensitive to /e /version. As it happens it was used when GS290 was first introduced. I see no clear explanation for the reason, but it would seem that more recent versions of platform-tools have introduced some issue that is a bug in some environments with this device.
An explanation for why we must apply
--disable-verity --disable-verification
early
In order to boot a custom boot-partition or custom recovery, you have to disable verified boot, otherwise you can’t boot to the OS.
got into boot-loop after trying to ignore verified boot (beginner’s mistake), had to use the SP Flash Tool to unbrick that device. (volume down & power = force shutdown) then follow this guide Installing /e/OS after removing UbuntuTouch on the GS290 maybe this will help someone else with the same problem
btw if you’re using opensuse, you can also use Yast to add the user to the group
Hi @Xenthos on the basis that this platform-tools version issue applies to #gs290 it would be great if someone affected might try to raise a bug against Platform tools.
If platform-tools worked once, it should be reported where it has stopped working in recent versions.
The reporting system seems to work though Google groups, so it would require someone with some Google login to make any progress! This might be a starting point accessible to all.
