Related
You need to be in stock emui 8 with unlocked bootloader.
If you are in elemental rom come back to stock emui 8 then flash this rom.
If you are in another gsi you can proceed directly (flash below recovery then do factory reset then flash gsi los rom via fastboot then again reboot to stock recovery do factory reset)
If you are in stock emui 8 do not wipe anything just flash it via fastboot and do factory reset.
first flash this recovery
https://mega.nz/#!cbJFAIQD!qvp1KnZ0qxlg6nHDFmpM5qyZ9QUVIDe5PoZE0BQf8fs
Fastboot command: fastboot flash recovery_ramdisk name of recovery.img
Then download
https://openkirin.net/download/
Fastboot command: fastboot flash system name of image.img
Los or RR rom and flash via fastboot (no need to wipe anything) then reboot to recovery do factory reset. You will have oreo 8.1 with gapps ,full signal bars,face unlock and stock camera.
If you are experiencing no sound its not gsi problem you didn't flashed stock completely so first flash this twrp recovery (only if you are in oreo not for emui5)
https://mega.nz/#!a81EDZAR!2-9yPFh3reghkGcfSl3nRIJhHGkP8fqDsgUG66ewjkk
Then flash stock emui 8 via huru
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
If huru only flased update.zip and gave you error no update_full_hw.zip and no update_data_full_public.zip not found in sd card then you need to rename them and flash again without wiping anything.
If stock emui 8 taking more than 5 minutes to boot then flash stock recovery mentioned above and do factory reset then it will boot with in 5 minutes.
If you don't have network or imei then you need to root. Then use any root explorer then go to cust/cn/all/localprop and change the line ro_config full network support=ture to false then reboot your network and imei will come back. You can do this in stock or in gsi.
RR ROM has great battery life with tons of customizations.
For emui8 flashing instructions,root and sound mod follow these instructions
https://forum.xda-developers.com/ho...si-honor-6x-8-1-0-t3809004/page5#post76981105
For telegram support of openkirin join this group
https://t.me/joinchat/HUf8EBJUJZQD281E59MdDw
Hell yess, thanks to open kirin team and you for mentioning it, the rom is excellent in use all bugs (the ones i faced in other gsi) fixed in this one and the availability of stock camera is just a cherry on top ?
Im newbie not familiar with this term
what is "gsi"?
need help
How to install emui 8 on bln-l21c432
jlan007 said:
Im newbie not familiar with this term
what is "gsi"?
need help
Click to expand...
Click to collapse
Generic system image. Read about project treble.
jlan007 said:
Im newbie not familiar with this term
what is "gsi"?
need help
Click to expand...
Click to collapse
Gsi means generic system image. In oreo custom roms will be available in system image formate we don't need twrp to flash custom roms just flash it via fastboot and factory reset.
Gsi roms will give you latest android os updates same as pixel devices getting so we don't need to wait for hauwei to release updates. If android p releases these gsi roms will give u update same as google devices getting. Oreo is game changer for every device.
If u want to flash gsi rom follow the emui8 upgrade method
https://forum.xda-developers.com/honor-6x/how-to/guide-update-to-emui-8-t3807806
Then follow instructions on openkirin support section.
--ahmed said:
How to install emui 8 on bln-l21c432
Click to expand...
Click to collapse
https://forum.xda-developers.com/honor-6x/how-to/guide-update-to-emui-8-t3807806
Follow that guide you will be on oreo in 10mins or less
If we rebrand to Chinese then update to Oreo and flash gsi..can we rebrand to our original variant or is there need to?
Which gsi redirection rom , carbon rom or los 15 ???
johnscrub said:
If we rebrand to Chinese then update to Oreo and flash gsi..can we rebrand to our original variant or is there need to?
Click to expand...
Click to collapse
Yes we can rebrand to original variant using hwota8
Khan ubaid said:
Which gsi redirection rom , carbon rom or los 15 ???
Click to expand...
Click to collapse
Go for Los 15 which is more stable and updated one.
Resurrection remix has huawei stock camera inbuilt....
Why flash stock recovery ? For those who are on Twrp ?
Great post. Hope you share some more experiences.
Trying to use the Google Play store it's telling me that my device isn't certified and I can't do anything..
NVM: For anyone else wondering I installed Magisk then the Magiskhide module and changed fingerprint.
Khan ubaid said:
Resurrection remix has huawei stock camera inbuilt....
Click to expand...
Click to collapse
Los is also had hauwei stock camera but rr in initial buid and los got 4 updates.
Nollie8969 said:
Why flash stock recovery ? For those who are on Twrp ?
Great post. Hope you share some more experiences.
Click to expand...
Click to collapse
Because you can't perform factory reset from twrp it can't do it correctly finally you will ended up in bootloop. You can flashctwrp right after doing factory reset but openkirin doesn't support twrp.
whateven12 said:
Trying to use the Google Play store it's telling me that my device isn't certified and I can't do anything..
NVM: For anyone else wondering I installed Magisk then the Magiskhide module and changed fingerprint.
Click to expand...
Click to collapse
So before flashing magdisk did playstore worked for you? Or did you flashed magdisk when flashing os? For me playstore works perfectly.
Ramesh006 said:
So before flashing magdisk did playstore worked for you? Or did you flashed magdisk when flashing os? For me playstore works perfectly.
Click to expand...
Click to collapse
Play store or any Google app wouldn't work for me before I install Magisk and the Module to change the fingerprint to a certified device.
No solution, but in the meantime you can use Aptoide as store: http://en.aptoide.com
whateven12 said:
Play store or any Google app wouldn't work for me before I install Magisk and the Module to change the fingerprint to a certified device.
Click to expand...
Click to collapse
Did you flashed los or rr? Try reflash.
Hello I want to install a Android 10 ROM but I just can't do it. I've followed instructions and tried to install crdroid, Paranoid and Pixel Experience. Everything result as a never ending boot animation or "no command" screen.
The logcat spam me with
Code:
[email protected]::IVendorF ingerprintExtensions/default
ServiceManagement: getService: Trying again for [email protected]::IVendorF ingerprintExtensions/default...
I've followed those instructions
From last OOS, reboot to fastboot, boot TWRP, flash last OOS and TWRP, reboot, do the same, reboot, format Data, reboot, flash the ROM and TWRP, reboot.
I've may added some extra reboot to be sure but it should work fine.
What did I do wrong, is this because I come from a BA version and not AA ? or 10.0.4 instead of 10.0.3 ?
I need ppl to tell me if they were able to flash a ROM coming from 10.0.4 BA please.
Thx for your support
Please someone, don't tell me I'm the only one having a European firmware...
I can confirm this too when i use EU vendor (GM1913).
I just use MSM to convert the device to International (after backing up EVERYTHING).
Using MSM->Unlocking bootloader again->Installing AOSP
Svid said:
I can confirm this too when i use EU vendor (GM1913).
I just use MSM to convert the device to International (after backing up EVERYTHING).
Using MSM->Unlocking bootloader again->Installing AOSP
Click to expand...
Click to collapse
Thx it worked
I put the link for MSM tool here to complete your answer
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
Why did you not just falsh the international version in twrp instead of the eu version and then flash a custom rom of your choice. No need for the msm tool.
hallo dare said:
Why did you not just falsh the international version in twrp instead of the eu version and then flash a custom rom of your choice. No need for the msm tool.
Click to expand...
Click to collapse
because you can't flash GM21AA stable on a GM21BA based rom (error 7)
Svid said:
because you can't flash GM21AA stable on a GM21BA based rom (error 7)
Click to expand...
Click to collapse
I did previously. No issues. Not sure if it's possible on latest version, but it did work
Could anybody share how can I move from MiUI EU ROM for K30 11.0.15.0 to Poco X2 official build 11.0.7.0?
I installed EU ROM as I found flashing ROM with TWRP was easier than using Mi Flash tool, in case we want to switch between ROM's. But, after I installed 11.0.15.0 I figured lot of the custom ROM's do not boot after flashing them and phone boots into fastboot mode (except couple of ROM's). So, I have been looking at how switch back EU MiUI ROM from 11.0.15.0 to Poco X2 11.0.7.0. The issue am facing while flashing using Mi Flash tool is that it gives error of ARB (Anti rollback error: 2, also I checked the same by issuing fastboot getvar anti, it says 2), and I am not sure how to get past this.
Could someone please help me with this?
I think your device is triggered with anti-rollback. So you cannot install any rom with build less than 11.0.15.0 that is poco x2 11.0.7.0 cant be flashed. So, you have to wait until new poco build greater than 11.0.15.0 and then flash it. Until then, flash your existing rom or some custom rom. Do it carefully and dont ever flash older roms from now, if something goes wrong, your device will hardbrick and you will have to go to service center where they have authorized EDL access to your device to flash things. Best of Luck.
You can use full recovery rom zip 11.0.7 and flash it via twrp. In 11.0.7 zip make sure you change the devicename in script from phoenixin to phoenix as twrp is pheonix.
After flashing you will be on stock 11.0.7 and stock recovery.
If you want to try custom roms , you can just flash the stock vedor zip of 11.0.07 and then flash any aosp custom rom.(you can find this zip in telegram channel/github)
eagle06 said:
You can use full recovery rom zip 11.0.7 and flash it via twrp. In 11.0.7 zip make sure you change the devicename in script from phoenixin to phoenix as twrp is pheonix.
After flashing you will be on stock 11.0.7 and stock recovery.
If you want to try custom roms , you can just flash the stock vedor zip of 11.0.07 and then flash any aosp custom rom.(you can find this zip in telegram channel/github)
Click to expand...
Click to collapse
Bro, but what about anti-rollback hardbrick?.. new miui wont allow downgrade right? he has very newer build than 11.0.7.
eagle06 said:
You can use full recovery rom zip 11.0.7 and flash it via twrp. In 11.0.7 zip make sure you change the devicename in script from phoenixin to phoenix as twrp is pheonix.
After flashing you will be on stock 11.0.7 and stock recovery.
If you want to try custom roms , you can just flash the stock vedor zip of 11.0.07 and then flash any aosp custom rom.(you can find this zip in telegram channel/github)
Click to expand...
Click to collapse
vivek12341 said:
Bro, but what about anti-rollback hardbrick?.. new miui wont allow downgrade right? he has very newer build than 11.0.7.
Click to expand...
Click to collapse
@eagle06 am worried about 11.0.15.0 > 11.0.7.0 which will trigger ARB as @vivek12341 has pointed out and it will hard brick the device, from what I have read around, hence this post if anybody knows a way out. There seemed to be workarounds initially when Xiaomi introduced ARB, I have not seen anybody mentioning such things in recent times especially for MiUI 11.
The reason why I moved to 11.0.15.0 is was, as it has no bloatware etc, and I did NOT know about ARB, now that I have 11.0.15.0 most of the custom ROMs are based on Poco X2 11.0.7.0 and I am facing issues flashing ROMs based on 11.0.7.0, as the format data from TWRP does not wipe properly + I see 98% of the time device goes to fastboot mode even if I flash Poco stock recovery and clear the data, seems like 11.0.15.0 is also an issue
May be I will have to wait till Poco releases updates > 11.0.15.0 or for MiUI 12. Actually I still dont know, not many know much on this subject.
crDroid works without any issues (which is what my current daily driver, its a very stable ROM), flashing on 11.0.15.0 after clearing data, also any ROM whose dev releases fastboot ROM's those also I can flash and boot without issues, rest all ROM's dont and end up back in fastboot mode
coolcorner said:
Could anybody share how can I move from MiUI EU ROM for K30 11.0.15.0 to Poco X2 official build 11.0.7.0?
I installed EU ROM as I found flashing ROM with TWRP was easier than using Mi Flash tool, in case we want to switch between ROM's. But, after I installed 11.0.15.0 I figured lot of the custom ROM's do not boot after flashing them and phone boots into fastboot mode (except couple of ROM's). So, I have been looking at how switch back EU MiUI ROM from 11.0.15.0 to Poco X2 11.0.7.0. The issue am facing while flashing using Mi Flash tool is that it gives error of ARB (Anti rollback error: 2, also I checked the same by issuing fastboot getvar anti, it says 2), and I am not sure how to get past this.
Could someone please help me with this?
Click to expand...
Click to collapse
You should flash back to China rom (V11.0.15.0.QGHCNXM) using miflash and install TWRP-3.4.1B-0322 using fastboot. After that you can flash all custom roms as normal. I have tried almost all the custom roms and they all work without any problem.
Lol.. Bro i am on miui 12 beta and went back to 11.0.0.7 via twrp flash...
Just download this http://bigota.d.miui.com/V11.0.7.0....NGlobal_V11.0.7.0.QGHINXM_9c232b802a_10.0.zip
Open that in pc, modify the script and rename device name to phoenix from phoenixin.
On twrp format data.. Then reboot to twrp again, tranfer that zip file and just flash. You will be back on stock global 11.0.0.7
Also crdroid as you mentioned has custom vendor which is different from china eu or global one.
If you want to use fastboot zip then you need to use https://www.xiaomitool.com/V2/ to overcome antirollback error.
eagle06 said:
Lol.. Bro i am on miui 12 beta and went back to 11.0.0.7 via twrp flash...
Just download this http://bigota.d.miui.com/V11.0.7.0....NGlobal_V11.0.7.0.QGHINXM_9c232b802a_10.0.zip
Open that in pc, modify the script and rename device name to phoenix from phonenixin.
On twrp format data.. Then reboot to twrp again, tranfer that zip file and just flash. You will be back on stock global 11.0.0.7
Also crdroid as you mentioned has custom vendor which is different from china eu or global one. e
If you want to use fastboot zip then you need to use https://www.xiaomitool.com/V2/ to overcome antirollback error.
Click to expand...
Click to collapse
1. Which script are you talking about? I could not find any script. check attached snapshot.
2. And to do this step from TWRP to flash 11.0.7.0, do I need to be on MIUI EU ROM or I can flash from any custom ROM too?
3. You were on MIUI 12 beta (official global) and changed devicename from phoenixin to phoenix and flashed using TWRP after formatting data, without hitting ARB issue? Wow!
4. You mentioned https://forum.xda-developers.com/showpost.php?p=82502389&postcount=3 Telegram/Github where we can get official vendor zip which we can flash from TWRP, any links to that?
5. Is there a Redmi K30 global ROM which I can use instead of Poco X2, they should be same right?
eagle06 said:
You can use full recovery rom zip 11.0.7 and flash it via twrp. In 11.0.7 zip make sure you change the devicename in script from phoenixin to phoenix as twrp is pheonix.
After flashing you will be on stock 11.0.7 and stock recovery.
If you want to try custom roms , you can just flash the stock vedor zip of 11.0.07 and then flash any aosp custom rom.(you can find this zip in telegram channel/github)
Click to expand...
Click to collapse
Please share telegram or github link for vendor.zip which I can flash using TWRP. As crDroid has custom vendor may be that is why it works for me on EU ROM and I see other custom ROMs do not have vendor installed while flashing using TWRP.
jngiag said:
You should flash back to China rom (V11.0.15.0.QGHCNXM) using miflash and install TWRP-3.4.1B-0322 using fastboot. After that you can flash all custom roms as normal. I have tried almost all the custom roms and they all work without any problem.
Click to expand...
Click to collapse
As a final resort will go to China ROM V11.0.15.0.QGHCNXM (this will be chinese right?) or this itself is global K30 ROM? Any links to global official MIUI K30 ROM, all I get is K30 chinese ROM
Sorry, I am asking too many questions, I do not want to brick phone in these times and go stand in queue at Mi service center during these times, when the servicing engineer will touch my phone all over
coolcorner said:
1. Which script are you talking about? I could not find any script. check attached snapshot.
Its in META-INF/com/google/android/ file name updater-script. Change getprop("ro.product.device") == "phoenixin" || this to getprop("ro.product.device") == "phoenix" || . Why we are doing this? because we are using k30 twrp.. there is no special twrp for poco x2. phoenix = k30, phoenixin=poco x2
2. And to do this step from TWRP to flash 11.0.7.0, do I need to be on MIUI EU ROM or I can flash from any custom ROM too? Any rom
3. You were on MIUI 12 beta (official global) and changed devicename from phoenixin to phoenix and flashed using TWRP after formatting data, without hitting ARB issue? Wow! Yes with twrp. When you flashed twrp recovery , your device is now treated as K30 in twrp space
4. You mentioned https://forum.xda-developers.com/showpost.php?p=82502389&postcount=3 Telegram/Github where we can get official vendor zip which we can flash from TWRP, any links to that?check Pm , cant post telegram links here
5. Is there a Redmi K30 global ROM which I can use instead of Poco X2, they should be same right?Theres no K30 global.., poco x2 rom is global, k30 roms is china and there is eu custom rom based on chinese roms
Please share telegram or github link for vendor.zip which I can flash using TWRP. As crDroid has custom vendor may be that is why it works for me on EU ROM and I see other custom ROMs do not have vendor installed while flashing using TWRP.
Whenever you want to use custom rom without vendor , you need to flash either 11.0.0.7 zip or 11.0.0.7 vendor zip before flashing that custom rom
As a final resort will go to China ROM V11.0.15.0.QGHCNXM (this will be chinese right?) or this itself is global K30 ROM? Any links to global official MIUI K30 ROM, all I get is K30 chinese ROM
Sorry, I am asking too many questions, I do not want to brick phone in these times and go stand in queue at Mi service center during these times, when the servicing engineer will touch my phone all over
Click to expand...
Click to collapse
Check my replies in blue
coolcorner said:
As a final resort will go to China ROM V11.0.15.0.QGHCNXM (this will be chinese right?) or this itself is global K30 ROM? Any links to global official MIUI K30 ROM, all I get is K30 chinese ROM
Sorry, I am asking too many questions, I do not want to brick phone in these times and go stand in queue at Mi service center during these times, when the servicing engineer will touch my phone all over
Click to expand...
Click to collapse
It is a chinese rom. You can select english as your default language. It really doesn't matter as you are going to wipe it anyway if your purpose is to use it for flashing custom roms.
[Deleted]
coolcorner said:
Just now I tried flashing V11.0.15.0.QGHCNXM using Mi Flash tool, and I hit Anti Roll back error again. Not sure what I am missing here I am on same version 11.0.15.0 EU ROM which has same Anti 2, not sure why the error this time?
Click to expand...
Click to collapse
Bro If you want to use fastboot zip then you need to use https://www.xiaomitool.com/V2/ to overcome antirollback error. Connect device and enable usb debugging and proceed.
Mi flash tool doesnt work for poco.....you always get that rollback error.
For fastboot zips use above tool.
For recovery zips use twrp.
Both methods flash the same thing and twrp will be replaced with stock recovery.
---------- Post added at 08:36 AM ---------- Previous post was at 08:20 AM ----------
Vendor only zip.
[ fw_vendor_phoenixin_miui_PHOENIXININGlobal_V11_0_7_0_QGHINXM_9c232b802a.zip
Size : 1.12 GiB
Download : fw_vendor_phoenixin_miui_PHOENIXININGlobal_V11_0_7_0_QGHINXM_9c232b802a.zip
https://drive.google.com/uc?id=1-mIvf3EhtZwLl_rg1cFgZIp5Zz4QlQZu&export=download
Flash via twrp. If you get error 7/wrong device check updater script and change name
eagle06 said:
Bro If you want to use fastboot zip then you need to use https://www.xiaomitool.com/V2/ to overcome antirollback error. Connect device and enable usb debugging and proceed.
Mi flash tool doesnt work for poco.....you always get that rollback error.
For fastboot zips use above tool.
For recovery zips use twrp.
Both methods flash the same thing and twrp will be replaced with stock recovery.
Click to expand...
Click to collapse
Thanks, really appreciate your quick revert. I am trying out with xiaomitool now. I know TWRP method is simple, just edit/change the devicename. But, I am **** scared after seeing ARB error so many times. So using xiaomitool as you mentioned use it to overcome ARB error. I will update how it goes.
I thought Xiaomi is dev/custom dev friendly, seeing all these errors, no wonder why people resent MiUI so much, of course the hardware + price is good. From my search even Google on their devices is not this harsh about ARB blocking after unlocking bootloader.
eagle06 said:
Bro If you want to use fastboot zip then you need to use https://www.xiaomitool.com/V2/ to overcome antirollback error. Connect device and enable usb debugging and proceed.
Mi flash tool doesnt work for poco.....you always get that rollback error.
For fastboot zips use above tool.
For recovery zips use twrp.
Both methods flash the same thing and twrp will be replaced with stock recovery.
---------- Post added at 08:36 AM ---------- Previous post was at 08:20 AM ----------
Vendor only zip.
[ fw_vendor_phoenixin_miui_PHOENIXININGlobal_V11_0_7_0_QGHINXM_9c232b802a.zip
Size : 1.12 GiB
Download : fw_vendor_phoenixin_miui_PHOENIXININGlobal_V11_0_7_0_QGHINXM_9c232b802a.zip
https://drive.google.com/uc?id=1-mIvf3EhtZwLl_rg1cFgZIp5Zz4QlQZu&export=download
Flash via twrp. If you get error 7/wrong device check updater script and change name
Click to expand...
Click to collapse
Thanks for the vendor image link.
Oh! yeah I am back in Poco 11.0.7.0 image, xiaomitool worked without issues. Thanks to you!!
@eagle06 do you know in this entire image (attached file) list (from tgz file) which is fastboot file? The reason I ask is, in Poco X2 in fastboot mode I see a single deadpixel, whereas when I was in EU MIUI I never saw that dead pixel. I plan to replace that file with EU MIUI fastboot image file, so when am in fastboot, it is clean without any dead pixels.
That small white pixel in fastboot is normal. All users have it including me.
Pic
eagle06 said:
Pic
Click to expand...
Click to collapse
Yep right that is the one. When I was on EU Miui, that one did not have, hence asked which is the image file for fastboot, thought I would flash that or replace next time I flash Poco stock when I am installing new custom ROM.
Yes, its a trivial thing can be ignored, does not really bother or harm.
BTW, so now that I am back in Poco X2 stock (On top of that I have installed BlissROM), next time I have to flash I can use either TWRP or Xiaomitool/V2.
1. For TWRP, I need to rename devicename to phoenix from phoenixin in updater-script and flash it using TWRP after clearing data
OR
2. I can use Xiaomitool/V2 with ADB debugging on (same step as last time)
Just check fastboot getvar anti for my phone, it also says 2. There is no problem for me flashing china rom with miflash. I have successfully flashed it 4 times before.
Good to have another way of flashing - will try the xiaomitool next time. :good:
jngiag said:
Just check fastboot getvar anti for my phone, it also says 2. There is no problem for me flashing china rom with miflash. I have successfully flashed it 4 times before.
Good to have another way of flashing - will try the xiaomitool next time. :good:
Click to expand...
Click to collapse
Woah! Miflash tool kept throwing errors at me and you are saying it worked for you? Phew!!
If I had flashed using TWRP, I might have been holding a 200gm brick in my hands LOL. Got lucky by using Xiaomitool/v2 then Thanks to you. I will stick to Xiaomitool for flashing stock ROMs hence forth.
I AM NOT RESPONSIBLE IF YOU MESS UP YOUR PHONE!!!
YOU HAVE BEEN WARNED!!!
Watch dogs is a ROM I created and it started with the OnePlus 9 Pro back in December. I have decided to bring it to the OnePlus 9, it's based on LineageOS & crDroid source & dependencies and I thank them for its use. SafetyNet and CTS passes whether your rooted or not. Modules not required. Most features are the same as crDroid but I have made some adjustments to bluetooth quality and some fonts that are not available there, plus Gapps are included.
Before you begin, if you don't have the latest platform tools installed on your windows machine. Download it here:
DO NOT FLASH GAPPS!!!! THEY ARE INCLUDED IN BUILD!!!!!
Flashing Instructions
First time installation (clean flash):
This update requires OOS 13.1 - 13.1.0.500(EX01) firmware
Backup your data
Download the ROM, and firmware flasher listed further down on this post and place all in your platform tools folder,
Extract all the contents in platform tools, Firmware flasher in folder.
You must flash firmware in bootloader.
Boot to recovery and factory reset then adb sideload
adb sideload WatchDogs-13.0-20230625-lemonade.zip
Reboot to system
reboot to recovery if you want root
adb sideload magisk.apk or adb sideload magisk.zip
Reboot to system
Update installation:
Updates can be sideloaded with custom recovery. Updates do not appear in system updater.
Sources:
ROM
Kernel
Downloads:
ROM
FIRMWARE FLASHER
Bugs?
Let me know.
Initial builds
WatchDogs-WITHGAPPS-13.0-20230312-lemonade.zip
WatchDogs-NOGAPPS-13.0-20230312-lemonade.zip
If you require Google apps, flash the first one only!
If you do not want Google apps, flash the second one only!
You can't cross dirty flash a update which should be common sense. Example, you can't dirty flash the with gapps build then next update, dirty flash the no gapps one.
I tried CRdroid recovery and the one I was on and both said name mismatch. Got any suggestions for me to try? Thank you for the new development too!
Telegram group please
lorilucille9 said:
I tried CRdroid recovery and the one I was on and both said name mismatch. Got any suggestions for me to try? Thank you for the new development too!
Click to expand...
Click to collapse
That's weird. Did you try sideloading the firmware flasher first before the ROM? If you still have difficulties, I will post the dtbo, boot and vendor_boot files for you to flash to make it compatible. I don't have this phone. I have the OnePlus9 Pro so I can't test it. I'm sure it works or there would be other users saying the same thing.
I flashed the firmware successfully and tried it again but still got the same error. It wouldn't hurt to post the kit files and recovery for others too. If you do then I'll try again before I have to head into work in a couple hours.
UPDATE:
I used the CrDroid boot-20230106 file and then sideloaded fw_Oneplus9_IN_OOS13_F20 on both slots and was able to flash the rom on both slots successfully. Will let you know what I find in time and thanks again for another version rom to pplay with
lorilucille9 said:
I flashed the firmware successfully and tried it again but still got the same error. It wouldn't hurt to post the kit files and recovery for others too. If you do then I'll try again before I have to head into work in a couple hours.
UPDATE:
I used the CrDroid boot-20230106 file and then sideloaded fw_Oneplus9_IN_OOS13_F20 on both slots and was able to flash the rom on both slots successfully. Will let you know what I find in time and thanks again for another version rom to pplay with
Click to expand...
Click to collapse
Good deal, and no problem. Since I use crDroid sources, I figured that should work. I will still post the files necessary to flash recovery when I get a chance. Let me know if there are any bugs or issues with the ROM itself so I can work on it. Thank you!
I installed it on my first try without any problems. but I couldn't understand how it differs from crdroid.
incesu571 said:
I installed it on my first try without any problems. but I couldn't understand how it differs from crdroid.
Click to expand...
Click to collapse
Bootanimation, fonts, bluetooth, sound audio and other tweaks.
TheSayaMan said:
Bootanimation, fonts, bluetooth, sound audio and other tweaks.
Click to expand...
Click to collapse
thx bro
TheSayaMan said:
Bootanimation, fonts, bluetooth, sound audio and other tweaks.
Click to expand...
Click to collapse
Not to mention Gapps included if you choose it so OTAs with no issues... otherwise you'd have to sideload Gapps again after at least for me that's what was happening.
lorilucille9 said:
Not to mention Gapps included if you choose it so OTAs with no issues... otherwise you'd have to sideload Gapps again after at least for me that's what was happening.
Click to expand...
Click to collapse
correct, sorry, forgot to mention that as well. Thank you!! crDroid doesn't offer a with gapps build. You can use the no gapps build to flash your own gapps but I won't support force close issues with the ROM. Example, pixel setup wizard can't be used because it interfers with the default launcher. And yes, on updates, just sideload the with gapps build and your done, unless you want root, then you will have to reboot and sideload magisk because root will be gone on a update.
incesu571 said:
Telegram group please
Click to expand...
Click to collapse
There is one in my 9 pro thread. I will update when I can.
I have op 9 t-mobile version le 2117, can you please guide me which firmware should i use IN, EU or NA?
Sady94 said:
I have op 9 t-mobile version le 2117, can you please guide me which firmware should i use IN, EU or NA?
Click to expand...
Click to collapse
Convert your T-Mobile to EU as listed on another thread, then you can use the EU firmware. I will be posting a update soon with the boot, vendor_boot and dtbo. If you don't want to do that, I will post them later to flash recovery on your phone. Keep in mind that different variants act different, so you may have bugs on T-Mobile, it wasn't tested.
screenshots?
pubmastervnt said:
screenshots?
Click to expand...
Click to collapse
Not by me, maybe someone else who is running it
MARCH UPDATES: 03/24:
WatchDogs-WITHGAPPS-13.0-20230324-lemonade.zip
WatchDogs-NOGAPPS-13.0-20230324-lemonade.zip
Sady94 said:
I have op 9 t-mobile version le 2117, can you please guide me which firmware should i use IN, EU or NA?
Click to expand...
Click to collapse
You can use my custom recovery, files added in OP. You still need latest stock A13.
fastboot flash --slot all boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vendor_boot vendor_boot.img
You cant install this (or any rom but base 11) on tmobile 2117 without BL unlock key. Pretty sure its not possible.
You can only convert to base global 11\OOS11 on 2117 for root, then in ui updater doesnt work OTA or manually. You can get to 13 stock only, because you need to be stock to ota, where you need a key to unlock bootloader again (conversion would bring you back to 11).
*The rooting situation with this phone sucks. I think Jaguar is the only one that will work because it is base 11.
Every time i try to flash bliss rom or crdroid for example it wont boot to the next step aka fastbootd step i think its stuck after the first flashing part i have tried multiple firmweres and multiple Platform Tools as different computers. PLEASE HELP ME!
Is it just these two ROMS?
What version of firmware are you currently on? Are you on the correct one for the custom ROM?
What version of platform-tools are you using? Version 33.0.3. is current working one.
Are you using Android Flash Tool, Pixel Flasher, or command line?
Do you see what I'm getting at?
Thank you so much for your reply.
Those that i have tested is Crdroid Bliss Stagos Sparkos and ricedroid.
All is tested to be installd with command line beacuse pixel flasher i couldnt get to work and android flash tool i only use for flasing stock to try again.
33.0.1 beacuse that is what everybody is saying to use.
The firmwere i have tried to install on is february beacuse the changelogs for the roms says februari updates but i have tried with the on before and the one after also with no succes.
95an said:
Thank you so much for your reply.
Those that i have tested is Crdroid Bliss Stagos Sparkos and ricedroid.
All is tested to be installd with command line beacuse pixel flasher i couldnt get to work and android flash tool i only use for flasing stock to try again.
33.0.1 beacuse that is what everybody is saying to use.
The firmwere i have tried to install on is february beacuse the changelogs for the roms says februari updates but i have tried with the on before and the one after also with no succes.
Click to expand...
Click to collapse
You might try 33.0.3 -- although I wonder if the version differences is negligible; but it is the latest version that did not have bugs before r34.
I don't know to flash custom ROMs or anything -- so I don't know if what I'm suggesting is even possible -- but if you know what you need to flash, you should be able to boot into fastbootd mode and individually flash what you want, right? Unless it's something like the flash-all script in Full Factories and all of that is automated....but then again, even in that, it's theoretically possible to enter fastbootd mode and manually flash all the .img's that flash-all does in that mode....