well i cant check since i dont know how to get out of fastboot
before i could see those orange letters saying its not safe oem unlocked , but now i get nothing else than fastboot. have no idea how to fix this , searching since yesterday for a solution
You may have to consider your options now, but it’s worth checking if you can boot back to OOS by changing slots in fastboot mode.
fastboot getvar current-slot
Let’s say it is slot_a
fastboot --set-active=b
fastboot reboot bootloader
Then start the device
followed your instructions,
i now see those orange letters again. thats a good sign no? but it wont get to os. it stays on the ‘orange state your device has been unlocked and cant be trusted. your device will boot in 5 seconds’ but it aint
or it goes back to fastboot
Is this your main device? Or can you just leave it for a while?
eOS-T, android 13 will probably be released this week with a bit of luck and you could then try flashing that. Take note that the steps will be slightly different and the eTeam don’t have a very good record of providing the latest correct install methods for this phone.
well , my main phone got broken thats why i got myself a new device so i need it now actually.
what if i just erase the things i did , those 2 images (dtbo and vendor_boot) , delete recovery from both sides and just start over? will the erase data command do the job? the problem here is that it wont get in recovery somehow. i got into recovery once but the original from oneplus , it seems that its another button combination than vol down and power. that possible?
also , does the phone need to be plugged in to get into e/os recovery?
or cant i just use twrp recovery?
I finally found a way to get the device ROM to Android 12 C.66
- Download an OOS FASTBOOT image
- Extract the downloaded compressed file.
- Then start with
.\ flash_all.bator.\ flash_all.sh - …
this?: OOS 12 - C.65 Full Rom - .\490bb705386df0e2f1b1ed4c3fa6483c045a7343.zip
i dont want to do anything wrong anymore
what is step 4?
I can’t do anything with that. Give me a working link!
Just saying…might not be good to flash that fastboot rom if your phone is actually on OOS13. Yhe author of that other thread had downgraded via msm before flashing that script. From memory I recall that most fastboot roms were not compatible with wishing to downgrade your OS.
I may be wrong though.
There should be a stock OOS recovery. I recall it being partly in Chinese (but this was android 12). From powered off try vol up + power. Release power at first sign of booting.
Or maybe try extracting the dtbo and vendor_boot from the eOS image you have and use those. Others have had success to boot recovery like that. Myself included.
Following @chrisrg reasoning - and if you want to install /e/OS-S dev first - follow this guide, e.g.:
After downloading the OOS firmware offered in the above-mentioned thread, the payload.bin file must first be extracted. This then makes the individual files boot.img, dtbo.img, etc… available for flashing.
Then continue with the above instructions.
it was stupid to not check which version of android is on there. i will send the seller a message to ask . i hope they can give me an answer. i guess its 13.
they came shipped with 11 i see.
i just going to take my chances.
so i make a new folder in android tools , then in terminal navigate to that folder?
ah i see how this is going , flash each file invidualy.
This is may help jog your memory as to what you have on your phone. The OOS11 and 12 pictures are of my phone (before I got rid of it) and the OOS 13 picture is from oneplus website.
the red first digit of the clock is what i remember most and sure about. but not more than that. i looked at it in a glimpse because im so disgused i have to accept google’s policies to use the phone. i guess ill go from the idea that the seller did his job to make the phone plug and play without doing updates first , so 13 it should be …
but about the OOS rom , will i do it correctly by extracting the zip into a separate folder inside android tools folder and navigate to it through adb terminal?
just to be sure , ill send a message to the seller. i dont want to brick it
is it in a way possible to recover what i did and boot into OS? since the original firmware should still be there because i only flashed the recovery and dtbo & vendor boot img. i have sended a message to the seller , but its frustrating to wait for a reply when you have no spare phone
If you have done no more than flash dtbo, vendor_boot and boot partitions it may just be possible to reinstate those partitions by trial and error; but it would be a lot of work downloading OOS roms and extracting those images with payload dumper go or suchlike. You would be guessing which roms to choose though.
Personally I think you should maybe try extracting those images from the eOS rom you downloaded and try to boot recovery as you did previously. That should work, and if it does not you could maybe take it as a clear indicator that the phone is not on android OOS12. Then make another plan to try installing an android13 rom such as lineage4microg. Make sure you return to the slot you were on when you first started as you have absolutely no idea where you are otherwise.
can i use twrp to flash eos instead of eos recovery? maybe this give more chance to succes. after flashing dtbo and vendor image?
and if it fails because its on android 13 , another user here sended a guide to downgrade it , thats not possible then? because u speak about an alternative if its on android 13 , while it should be possible to downgrade?
Last time I knew anything about twrp it didn’t work with 12 or 13.
The other stuff I don’t know sorry.
You could try to boot twrp without flashing: fastboot boot <whichever twrp it is.img>
If it does not boot twrp on your phone that could tell you at least you do not have android 11, lol
i was able to flash the recovery , i pushed button volume down and power but then its stuck on screen orange state your device has been unlocked and cant be trusted ,
it also cant be turned off when connected to computer so there is no way of turning it on vol down and power button to manually trigger recovery. it always restarts after turning off while connected