Database Info

OTA update for F1f

A new official ColorOS udpate from OPPO is available in my region and at least all Europe I guess.
This is version F1fEX_11_170327. A copy of the OTA update package is here if anyone needs it: F1EX_11_OTA_896-897_patch_201703271119_3cf702307f.zip on MEGA (56.0 MB).
A few screenshots if you want to see the changelog: http://imgur.com/a/5UiiQ
Before:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After, full about phone capture: http://imgur.com/CIbWrWX
This is still Android 5.1.1 with a 3.10.28 kernel. No Marshmallow
I'm a bit amazed by the continuous support from OPPO, and especially the security patches integrated in those updates. I was not expecting this from this brand. This is part of what's preventing me from completely switching to LineageOS. This is my only smartphone and I need it to just work.

Now I wish I can unroot my phone, lol

You can, I did it.
The simplest method:
- copy ColorOS & Project Spectrum zips provided by OPPO
- boot in fastboot mode
- Install stock recovery with fastboot
- Reboot to recovery
- Install Project Spectrum
- Reboot to recovery
- Install ColorOS
You should be stock, relocked.

kdd998 said:
You can, I did it.
The simplest method:
- copy ColorOS & Project Spectrum zips provided by OPPO
- boot in fastboot mode
- Install stock recovery with fastboot
- Reboot to recovery
- Install Project Spectrum
- Reboot to recovery
- Install ColorOS
You should be stock, relocked.
Click to expand...
Click to collapse
Thank you!
But where can I get stock recovery?

You can extract recovery.img from the ColorOS zip.

If someone were to flash this via twrp. When they have followed this thread
https://forum.xda-developers.com/op...pdates-rooted-unlocked-devices-t3395034/page8
They would loose twrp and lose he unlocked bootloader correct?

This zip is only for OPPO*recovery, not for TWRP. It needs to be modified. If modified, I don't think recovery or unlocked state would change as recovery is not included in the original zip.

kdd998 said:
This zip is only for OPPO*recovery, not for TWRP. It needs to be modified. If modified, I don't think recovery or unlocked state would change as recovery is not included in the original zip.
Click to expand...
Click to collapse
The update zip does contain and flash the locked bootloader(emmc_appsboot.mbn) and also the update zips never contain a recovery.img but do have a script(install_recovery.sh) and patches that patch the latest recovery onto latest boot.img and flash it to recovery. So, yes, flashing it will lock everything down. Modifying it to remove bootloader and recovery is easy enough( I'm happy to do it) but it will also check the current build version on the phone before flashing and refuse to flash unless the rom has been updated to the "896" level, which I have never seen an update zip to go from 894 to 896 (891-894 is the newest update I have seen posted till now). There is a new download of full rom available for the 896 version which could also be modified to install from twrp without bootloader and recovery but it does require a full wipe. If enough people want it, I guess it would be good to have a more up to date full clean install of colouros.
Do you think it's worth the effort?

MiniBlu said:
The update zip does contain and flash the locked bootloader(emmc_appsboot.mbn) and also the update zips never contain a recovery.img but do have a script(install_recovery.sh) and patches that patch the latest recovery onto latest boot.img and flash it to recovery. So, yes, flashing it will lock everything down. Modifying it to remove bootloader and recovery is easy enough( I'm happy to do it) but it will also check the current build version on the phone before flashing and refuse to flash unless the rom has been updated to the "896" level, which I have never seen an update zip to go from 894 to 896 (891-894 is the newest update I have seen posted till now). There is a new download of full rom available for the 896 version which could also be modified to install from twrp without bootloader and recovery but it does require a full wipe. If enough people want it, I guess it would be good to have a more up to date full clean install of colouros.
Do you think it's worth the effort?
Click to expand...
Click to collapse
It would be nice if we ever go back to color os. But don't rush it. Take your time. Its not a big rush. But I would rather the time be spent in lineage first. Up to you

MiniBlu said:
I have never seen an update zip to go from 894 to 896 (891-894 is the newest update I have seen posted till now).
Click to expand...
Click to collapse
I have a 010 to 896 patch here if needed: https://mega.nz/#!hxxDxAwb!nLa3aDvz3GubMcTaxqaLowRujDt6UKcn0DohuhkclXY
Thanks for all the info. From my point of view, I don't think it's worth the effort. I'd rather work on LineageOS (maybe I'll have time on monday to try new things)

Deleted

kdd998 said:
You can, I did it.
The simplest method:
- copy ColorOS & Project Spectrum zips provided by OPPO
- boot in fastboot mode
- Install stock recovery with fastboot
- Reboot to recovery
- Install Project Spectrum
- Reboot to recovery
- Install ColorOS
You should be stock, relocked.
Click to expand...
Click to collapse
what if i still have my stock recovery? can i just flash spectrum os then flash color os to unroot my device? coz i rooted my device also using kingroot. i cant update ota.

wakaranay said:
what if i still have my stock recovery? can i just flash spectrum os then flash color os to unroot my device? coz i rooted my device also using kingroot. i cant update ota.
Click to expand...
Click to collapse
https://www.google.com.au/amp/m.wikihow.com/Unroot-Android?amp=1
That would be the hardest way in my opinion. Try these first.
I would use the supersu app first and if that doesn't work then use the manual delete

Jamie_oppo said:
https://www.google.com.au/amp/m.wikihow.com/Unroot-Android?amp=1
That would be the hardest way in my opinion. Try these first.
I would use the supersu app first and if that doesn't work then use the manual delete
Click to expand...
Click to collapse
both not working. i cant still update tru ota

wakaranay said:
both not working. i cant still update tru ota
Click to expand...
Click to collapse
Have you unlocked your bootloader?

Jamie_oppo said:
Have you unlocked your bootloader?
Click to expand...
Click to collapse
locked bootloader

wakaranay said:
locked bootloader
Click to expand...
Click to collapse
I guess flashing spectrum then color os should work. Not 100% but if you get to spectrum then it will work

Jamie_oppo said:
I guess flashing spectrum then color os should work. Not 100% but if you get to spectrum then it will work
Click to expand...
Click to collapse
thanks. i guess firmware flashing will also work. but i dont know what firmware or when i can get that firmware

wakaranay said:
thanks. i guess firmware flashing will also work. but i dont know what firmware or when i can get that firmware
Click to expand...
Click to collapse
Read post 3 of this thread. Miniblu made a firemware zip. Oops sorry didn't include a link
https://forum.xda-developers.com/oppo-f1/development/rom-unofficial-cyanogenmod-13-t3542718/page23

How to re install the original recovery :crying:

5.1.8 update started

Op started rolling 5.1.8 update
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my ONEPLUS A6003 using Tapatalk

5.1.8 is intended for India

dgunn said:
5.1.8 is intended for India
Click to expand...
Click to collapse
no it says it "also contains the 5.1.7 changes for India" since there were issues with 5.1.7 update for India, it also includes the above changes for all other phones as well, so does not seem to be region specific

True.its for all regions.
Sent from my ONEPLUS A6003 using Tapatalk

So, these guys have an actual department dedicated to fixing community reported issues?
That's incredible.

Is it possible to download it without having to install it right away? Phone is rooted and don't want to lose root in case it starts installing.
Sent from my [device_name] using XDA-Developers Legacy app

Done

To those of you that updated and are rooted, can you confirm you're not sporadically losing root like 5.1.7 was doing?

slonn said:
Is it possible to download it without having to install it right away? Phone is rooted and don't want to lose root in case it starts installing.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
If it installs it won't be active until a reboot anyway, so as long as u don't reboot it won't change, even after install

I never lost root with 5.1.7 or any other 5.1.x rom (no twrp).

akxak said:
I never lost root with 5.1.7 or any other 5.1.x rom (no twrp).
Click to expand...
Click to collapse
users were reporting losing root / twrp with OTA's
im on 5.1.7, if i update to 5.1.8 via system update wont it remove my twrp and root and kernel?
afaik it does...

I applied the OTA (full due to root) with the system installer and reinstalled Magisk via Magisk Manager BEFORE rebooting.
I never used TWRP on the OP 6 and rooted with Magisk, I don't need it. When I got my OP6, there was no TWRP available.
Magisk patched the boot image.
After a smooth reboot, the system was updated and Magisk kept installed.
And yes, TWRP is lost when updating that way but can be reinstalled via Fastboot if it is needed.

so what the proper procedure on installing updates without getting wiped?
so far the most logical way of doing it is downloading the OTA
installing it via twrp
then install twrp.zip in twrp after update
then magisk, then kernel and boot.

If you need TWRP, yes. If not, install via system, reapply Magisk to inactive slot before rebooting and reboot.
I am not sure whether TWRP uses the A/B structure. The system updater does so if for any reason the update dies not start, the old working system remains available and will be booted.
The anxiety whether the system will come up after an update is gone for me... I crashed my OP5 applying the Oreo update and had to setup it up from scratch... while abroad on Christmas.

akxak said:
I never lost root with 5.1.7 or any other 5.1.x rom (no twrp).
Click to expand...
Click to collapse
Of course you lose root and TWRP as it loads a stock Boot.img which includes the OOS stock kernel and stick recovery. You will lose TWRP and Magisk, you have to reflash them.

@Eric214, you did read the original question #8 I was answering?
I answered on a sporadically loss of root, which meant for me after having root, it's suddenly gone without having installed something.
Don't jump on an answer without reading the question.

akxak said:
@Eric214, you did read the original question #8 I was answering?
I answered on a sporadically loss of root, which meant for me after having root, it's suddenly gone without having installed something.
Don't jump on an answer without reading the question.
Click to expand...
Click to collapse
Well I must have read the question wrong as it sounded like some were losing TWRP and root sporadically after the update. I didn't not read it I just took it another way... sorry for confusion
---------- Post added at 09:22 PM ---------- Previous post was at 09:19 PM ----------
Also, just as easy to just wait for Funk Wizard to post the official FULL zip on his thread and just Flash in TWRP. Last time I jumped the gun early I was on the beta 5.1.6 build but saw no issues whatsoever. I'll sit back this time.

Eric214 said:
Of course you lose root and TWRP as it loads a stock Boot.img which includes the OOS stock kernel and stick recovery. You will lose TWRP and Magisk, you have to reflash them.
Click to expand...
Click to collapse
If you only run Magisk and stock recovery, install the update, but before reboot , re-install Magisk to the other A/B side , then reboot. Then reboot, you'll have Magisk freshly installed.
This doesn't work for TWRP!
Sent from my Brain using my Keyboard

akxak said:
If you need TWRP, yes. If not, install via system, reapply Magisk to inactive slot before rebooting and reboot.
I am not sure whether TWRP uses the A/B structure. The system updater does so if for any reason the update dies not start, the old working system remains available and will be booted.
The anxiety whether the system will come up after an update is gone for me... I crashed my OP5 applying the Oreo update and had to setup it up from scratch... while abroad on Christmas.
Click to expand...
Click to collapse
you do appreciate the A/B structure when a flash goes wrong.
ill wait for the official zip to be flashed via TWRP before going ahead with it

virtyx said:
you do appreciate the A/B structure when a flash goes wrong.
ill wait for the official zip to be flashed via TWRP before going ahead with it
Click to expand...
Click to collapse
Of course I do... the Oreo update in December led to an unplanned factory reset of my OP 5 while abroad in Europe for Christmas. With A/B, this would not have happened because the present working OS (with Magisk/root) remains untouched and the update is installed in the other partition. If for any reason the updated OS is not coming up, the systems falls back and boots the previous (working) OS from where a new update or whatever measure can be initiated.
I wonder if (and if not why) TWRP does support that, installing the full update in the unsused slot (including TWRP itself and Magisk) and then boot that slot.
With these two partitions in use, you keep your phone working and avoid a soft brick. For the manufacturer it avoids trouble for the normal user in case an OTA fails...

(Guide) Relock Bootloader/Back To Stock.

This guide is for those who are on unlocked bootloader/custom roms and want to go back to realme UI 1.0 and relock
Needless to say, me, and the makers of realme flash-tool and TWRP/other recoveries wouldn't be responsible for any damage caused to your device. Having said that, this method has been tested and should be fine for realme UI 1.0.
First things first, if you are on custom rom or on rooted stock rom you need to revert to unmodified stock rom.
*Warning :-Make absolutely sure that you are not relocking by flashing an older version, always flash the current or newer i:e If you unlocked while being on version A.19 make sure to flash A.19 and/or newer versions and not A.17. While I'm not sure if this will result in a brick or not and have no intentions of trying, this may result in a hardbrick.*
Links to firmware (RMX2061/EUxxxxxxx.ozip). Search for realme 6pro from the list.
IN.- https://www.realme.com/in/support/software-update
EU.- https://www.realme.com/eu/support/software-update
*Do not lock bootloader while on custom rom.*
*Do not lock bootloader if you're rooted.*
*Do not lock bootloader with any custom partitions even vbmeta with disabled verity and verification.*
IF YOU DO SO YOU'LL END UP WITH A BRICK WHICH CAN ONLY BE FIXED AT A SERVICE CENTER. YOUR PHONE WILL DISPLAY AN ERROR MESSAGE SAYING PARTITONS ARE CORRUPT/DAMAGED.
Backup your stuff before proceeding.
There are three ways to revert to stock:
1. Using RFT (Realme Flashtool) by @sayaoks :-
Instructions provided on the thread.
https://forum.xda-developers.com/re.../tool-rtf-realme-flash-tool-to-flash-t4144969
2. Using TWRP (use the latest from the recovery section).
*Wipe>Format Data> type yes> format
*Reboot>reboot to recovery
*Install > Select .ozip> Swipe to flash
*Reboot
Do not select disable-vbmeta or avb_patcher or anything of that sort.
Recommended-
https://forum.xda-developers.com/realme-6-pro/development/recovery-twrp-recovery-t4171759
3. Using stock recovery.
From system:- To flash using stock recovery, download and put the .ozip in the root of storage and from realme file manager tap on it. It will start Flashing in the stock recovery.
From recovery:- Download and put the .ozip in the root of storage, then reboot to recovery.
Your Language> Install from storage> enter password(only if you have one)> Phone/SDcard and then select the .ozip.
Any custom recovery.img/boot.img should now be replaced with stock.
After flashing is successful and the device has booted to stock rom reboot to the bootloader.
If you want to be extra careful, and used RFT or TWRP/Custom Recovery to flash stock rom, you can flash the fw again using stock recovery after the phone has booted up(steps mentioned above).
Connect the phone to PC and enter command
Code:
fastboot flashing lock
Now on the phone select lock bootloader with the help of volume up and power buttons.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Wait for it to complete... and you will boot into the OS with a locked bootloader.
Thanks to @Satham spot & @sayaoks

I'm on RMX2063_11_A35 I can't find an update more recent than RMX2061EU_11.A.26 Can I use this method and update via OTA and then lock the bootloader?

Andres88z said:
I'm on RMX2063_11_A35 I can't find an update more recent than RMX2061EU_11.A.26 Can I use this method and update via OTA and then lock the bootloader?
Click to expand...
Click to collapse
A35 is the latest version for IN firmware. Latest for EU is A28, which is up on realme EU website.
If you want A35 firmware just visit the Indian downloads page.
And yes you can update to a newer version than whatever you unlocked on and then lock on the newer version. Make sure everything is just stock meaning no twrp,patched boot and/or custom recovery.

Don't have a brick to use the rmx2061 model? instead of device 2063, what method do you recommend.

Andres88z said:
Don't have a brick to use the rmx2061 model? instead of device 2063, what method do you recommend.
Click to expand...
Click to collapse
Well I know someone having Indonesian/Indian model and locking on the EU firmware. It didn't brick but not sure what will happen in the future when an OTA drops.
Lock on the same firmware as the device, like eu device with eu fw and so on (just to be safe).
You can use any methods to get to stock, just to be extra sure, when the phone boots up after flashing stock and before locking, put the fw in the root storage of the phone and re-flash again with the stock recovery. And then proceed to lock.

thanks to carry out the process and start correctly, I got an update of only 300 mb ls which gave me an error, but soon the same RMX2063a1135 came out but 3.5 gb which if it was installed and now I am as I started, without root or magisk, The question is, since the most recent was installed via ota, can I close the bootloader?

Andres88z said:
thanks to carry out the process and start correctly, I got an update of only 300 mb ls which gave me an error, but soon the same RMX2063a1135 came out but 3.5 gb which if it was installed and now I am as I started, without root or magisk, The question is, since the most recent was installed via ota, can I close the bootloader?
Click to expand...
Click to collapse
Yes

can i use orange fox recovery ? which one should i wipe if i use orange fox recovery?

Can this guide help me rollback my realme 6 pro from android 11 beta to android 10? If it does, which steps do I need to add or change. Thanks

noside_143 said:
Can this guide help me rollback my realme 6 pro from android 11 beta to android 10? If it does, which steps do I need to add or change. Thanks
Click to expand...
Click to collapse
Yes but you must use the latest Android 10 image, seem realme blocks to downgrade to older version than this

I have installed custom rom and I need to return to stock rom
all stock versions I found are ui 1.0 only
I unlocked the bootloader while using latest ui 2.0
what should I do to return to stock rom please ?

kiro_koko said:
I have installed custom rom and I need to return to stock rom
all stock versions I found are ui 1.0 only
I unlocked the bootloader while using latest ui 2.0
what should I do to return to stock rom please ?
Click to expand...
Click to collapse
You can use RUI 2.0 to lock. Just be sure that all partitions are stock. Use the .ozips made by @ctapchuk

General Global 11.2.7.7. Root Guide

Frist off Im not responsible for anything that happens to your phone!!!
MUST HAVE UNLOCK BOOTLOADER!!
Steps to root
If you are on 11.2.6.6. and rooted
to take update you must flash stock boot.img can be found in link
reboot to bootloader
fastboot flash boot boot11.2.6.6 .img
once done
fastboot reboot
take update
once update is completed
reboot to bootloader
now down load the PATCHEDBOOT.IMG
and flash
fastboot flash boot patched-11.2.7.7.img
once done
fastboot reboot
BOOM NOW YOUR AR ROOTED!!!
STOCK 11.2.6.6 FIXED AND TESTED THANKS TO
mattie_49​
LINKS / HELP
BOOT.IMGS
HELP
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I should have read this beforehand but I did it the same way as always. Magisk, restore images, OTA updates, magisk install to inactive slot and I get this and I can't get it to go away and it didn't update either. Root is gone as well but it didn't update.
Edit: it fixed itself after the 3rd attempted update. Lost root but that's an easy. I don't know why it did it. Leaving for anyone else that might have this issue

Josh McGrath said:
View attachment 5335417
I should have read this beforehand but I did it the same way as always. Magisk, restore images, OTA updates, magisk install to inactive slot and I get this and I can't get it to go away and it didn't update either. Root is gone as well but it didn't update.
Edit: it fixed itself after the 3rd attempted update. Lost root but that's an easy. I don't know why it did it. Leaving for anyone else that might have this issue
Click to expand...
Click to collapse
please try new uploaded stock boot imgs there fixed now sorry

so, what I (a newbie to rooting without TWRP) should understand is that if I am on stock I just have to unlock bootloader and flash the patched .img?

FizzyAps said:
please try new uploaded stock boot imgs there fixed now sorry
Click to expand...
Click to collapse
Just updated through updated stock image. Thanks for all your efforts

In my case I have found that it is not necessary to flash the stock boot image in order to update. I simply installed the update, rebooted to bootloader, booted the patched boot.img (not flashed), and installed Magisk to my boot partition from there. That way you don't permanently mismatch your ROM from your boot partition in case you are not using global ROM (which is the case for me). I don't know if the boot partition actually differs between the ROMs but this feels cleaner

Won't let me download the OTA after going back to stock bootloader. I have my CN OP9 cross flashed to global. I keep getting Couldn't Update Installation Problem. Guess i'll wait for Oxygen Update.

notiflux said:
In my case I have found that it is not necessary to flash the stock boot image in order to update. I simply installed the update, rebooted to bootloader, booted the patched boot.img (not flashed), and installed Magisk to my boot partition from there. That way you don't permanently mismatch your ROM from your boot partition in case you are not using global ROM (which is the case for me). I don't know if the boot partition actually differs between the ROMs but this feels cleaner
Click to expand...
Click to collapse
You can't install they update if rooted it errors out

hmmm. im coming from rooted global 255 and I uninstalled magisk, flashed stock 255 and rebooted. tried to update to the partial 277 but it always fail. What am i missing here? maybe the stock 255 that i have is bad?

infamousvincci said:
hmmm. im coming from rooted global 255 and I uninstalled magisk, flashed stock 255 and rebooted. tried to update to the partial 277 but it always fail. What am i missing here? maybe the stock 255 that i have is bad?
Click to expand...
Click to collapse
please click the help link we have untouched stock 11.2.5.5 there

FizzyAps said:
You can't install they update if rooted it errors out
Click to expand...
Click to collapse
if it detects that your device is rooted, it will switch to downloading the full update instead of the incremental one. Maybe it is different on global ROM, but that's what worked for me

Thanks, updated from 11.2.4.4 with the stock boot img i found in the other thread with this guide.

Phone stopped booting after flashed 2 custom rom.

Hi guys
I have an oppo r7sf has 1.5ghz Qualcomm 4gb ram.
I flashed project spectrum first, then installed linage os android 9 and mokee os android 9 also.
Both of them wifi didn't work.
I already asked for that here My old post
Then i flashed lower version of android then NONE of them boot up.
I guaranteed that i installed with the same strategy.
Format data, dalvik, cache and system partion at the advanced wipe section.
Next get the rom and installed both rom, root and gapps.
It just hang in logo for 10s and shut down.
Your browser is not able to display this video.
Now even linage os 9 that i flashed before also not booting.
I even not to install either root or gapps or both but the same result
The only custom os i can boot is project spectrum (flashed again XD)
I am thinking of the recovery of this phone.
I flashed almost all version of twrp but only a *third party* one ran.
Link to the post itself The post
Intrestingly, he has almost the same problem as my phone: error 7, all version has dtb error- happened to all *genuine *twrp
Link to recovery that they uploaded: Third party twrp that worked
I also heard that most oppo phones, new or old are not easy to installed custom rom, and if it did, most essential things will not work with full of bugs.
I think i give up on this phone now. It will be put into my S21 ultra 5G box. I will bury it right after my dead dog's location within a week.
I have prepared, you must be fast!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

wikiepeidia said:
Hi guys
I have an oppo r7sf has 1.5ghz Qualcomm 4gb ram.
I flashed project spectrum first, then installed linage os android 9 and mokee os android 9 also.
Both of them wifi didn't work.
I already asked for that here My old post
Then i flashed lower version of android then NONE of them boot up.
I guaranteed that i installed with the same strategy.
Format data, dalvik, cache and system partion at the advanced wipe section.
Next get the rom and installed both rom, root and gapps.
It just hang in logo for 10s and shut down.
Now even linage os 9 that i flashed also not booting.
The only thing i can boot is project spectrum (flashed again XD)
I am thinking of the recovery of this phone.
I flashed almost all version of twrp but only a *third party* one ran.
Link to the post itself The post
Intrestingly, he has almost the same problem as my phone: error 7, all version has dtb error- happened to all *genuine *twrp
Link to recovery that they uploaded: Third party twrp that worked
Click to expand...
Click to collapse
Oh now i see why the rom didnt work, the rom and twrp i provided you was only for r7 plus
ill try finding twrp and a rom for your phone, ill let you know if i find anything

DieFault said:
Oh now i see why the rom didnt work, the rom and twrp i provided you was only for r7 plus
ill try finding twrp and a rom for your phone, ill let you know if i find anything
Click to expand...
Click to collapse
Download TWRP for r7sf
Download TWRP Open Recovery for r7sf
dl.twrp.me
Download TWRP for r7sf
Download TWRP Open Recovery for r7sf
eu.dl.twrp.me
also, where did you get lineageOS previously? i cannot find a download link for it anywhere!

Ok thank you but hurry up before i bury it!!

DieFault said:
Download TWRP for r7sf
Download TWRP Open Recovery for r7sf
dl.twrp.me
Download TWRP for r7sf
Download TWRP Open Recovery for r7sf
eu.dl.twrp.me
also, where did you get lineageOS previously? i cannot find a download link for it anywhere!
Click to expand...
Click to collapse
Oh here in this page: I even follow instruction here!

wikiepeidia said:
Oh here in this page: I even follow instruction here!
Click to expand...
Click to collapse
there is no old lineage os over there... ill let you know if i find another rom.
for now to revive your phone you can flash the new twrp i gave you and install stock r7sf rom onto it