Topic can be closed: apparently the DB integration works just fine. There was an other bug in the same function. Not sure why the errors above are showing.
-- EDIT--
Hi,
First of all, sorry I am posting in a general forum about development. My low post count doesn't allow me to post in a Dev forum.
I'm am trying to use the sqlite-net-pcl library form Frank Kreuger. Dev in Visual Studio 2015 with Xamarin. Debugging on a Moto G 3th gen XT1541.
When I am debugging on the device, I get the following Output:
02-28 23:40:11.006 D/Mono (11235): DllImport attempting to load: 'e_sqlite3'.
02-28 23:40:11.007 D/Mono (11235): DllImport error loading library '/storage/emulated/0/Android/data/AppName.TimeTracker/files/.override/libe_sqlite3': 'dlopen failed: library "/data/app/AppName.TimeTracker-1/lib/arm//storage/emulated/0/Android/data/AppName.TimeTracker/files/.override/libe_sqlite3" not found'.
02-28 23:40:11.007 D/Mono (11235): DllImport error loading library '/storage/emulated/0/Android/data/AppName.TimeTracker/files/.override/libe_sqlite3.so': 'dlopen failed: library "/data/app/AppName.TimeTracker-1/lib/arm//storage/emulated/0/Android/data/AppName.TimeTracker/files/.override/libe_sqlite3.so" not found'.
02-28 23:40:11.008 D/Mono (11235): DllImport error loading library '/system/lib/libe_sqlite3': 'dlopen failed: library "/data/app/AppName.TimeTracker-1/lib/arm//system/lib/libe_sqlite3" not found'.
02-28 23:40:11.008 D/Mono (11235): DllImport error loading library '/system/lib/libe_sqlite3.so': 'dlopen failed: library "/data/app/AppName.TimeTracker-1/lib/arm//system/lib/libe_sqlite3.so" not found'.
02-28 23:40:11.008 D/Mono (11235): DllImport error loading library 'libe_sqlite3': 'dlopen failed: library "/data/app/AppName.TimeTracker-1/lib/arm/libe_sqlite3" not found'.
02-28 23:40:11.009 D/Mono (11235): DllImport loaded library 'libe_sqlite3.so'.
02-28 23:40:11.009 D/Mono (11235): DllImport searching in: 'e_sqlite3' ('libe_sqlite3.so').
02-28 23:40:11.009 D/Mono (11235): Searching for 'sqlite3_libversion_number'.
02-28 23:40:11.021 D/Mono (11235): DllImport searching in: 'e_sqlite3' ('libe_sqlite3.so').
02-28 23:40:11.021 D/Mono (11235): Searching for 'sqlite3_open_v2'.
02-28 23:40:11.037 D/Mono (11235): DllImport searching in: 'e_sqlite3' ('libe_sqlite3.so').
02-28 23:40:11.037 D/Mono (11235): Searching for 'sqlite3_busy_timeout'.
When I unpack the APK in the Debug folder, I can see that the file is included:
{
"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"
}
But when I look on the device, the file is not deployed in the folder shown in the error:
What Am I doing wrong here?
Thanks a lot!
Rob
How did you solve this problem?
Related
When i proceed to unlock my boot loader an error showing that " Your device does not qualify for bootloader unlocking" ...
Any solution for this ?? Plz help me out....
Refer ss
{
"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 XT1033 using XDA Free mobile app
My device doesnot qualify for unlocking bootloader...my cid code is 0*0007...so what to do now?
Vinod check this info
How can do i validate whether my device is unlockable? You can use our online tool, or you can check manually by issuing a fastboot command and looking at the CID value returned.
$ fastboot getvar all
The table below will indicate whether your device is eligible for the bootloader unlock program:
Your device is unlockable if the CID value returned is:
Your device is NOT eligible for bootloader unlock if the CID value returned is one of
0x0000
0x0003
0x0007
0x0009
0x000B
0x000C
0x000D
0x000E
0x0014
0x00DE
0x0001
0x0002
0x0004
0x0005
0x0006
0x0008
0x000A
0x000F
0x0010
0x0011
0x0032
Sent from my XT1033 using XDA Free mobile app
0x0007 can be unlocked
vinodh44u said:
My device doesnot qualify for unlocking bootloader...my cid code is 0*0007...so what to do now?View attachment 2895550
Vinod check this info
How can do i validate whether my device is unlockable? You can use our online tool, or you can check manually by issuing a fastboot command and looking at the CID value returned.
$ fastboot getvar all
The table below will indicate whether your device is eligible for the bootloader unlock program:
Your device is unlockable if the CID value returned is:
Your device is NOT eligible for bootloader unlock if the CID value returned is one of
0x0000
0x0003
0x0007
0x0009
0x000B
0x000C
0x000D
0x000E
0x0014
0x00DE
0x0001
0x0002
0x0004
0x0005
0x0006
0x0008
0x000A
0x000F
0x0010
0x0011
0x0032
Sent from my XT1033 using XDA Free mobile app
Click to expand...
Click to collapse
Dude did you read it right? My device is also 0x0007. And it says Unlockable. Recheck the website. If it cannot be unlocked you wont even get the key. 0x0007 can be unlocked. Relax. and the error, i had the same trouble. They are saying its because of some bug in 4.4 Android.
hi guys, so I stomped my dads xoom while cleaning and I remembered I was not able to unbrick it, and out of nostalgia wanted to try again. I have read a lot of similar posts and guides still I have not been hable to unbrick this one.
Specs: Motorola Xoom Wifi Only Mz604 sd card missing (Ill buy one tomorrow)
Bootloader Version (According to RSD Lite) :0vx001045
Background: The tablet got bricked while the process of changing "stuff" (its been some years dont quite remember) I remember we got the gpu overclocked and was running a CFW stingray I believe.
Present Situation:
The tablet turns on and goes to "starting RSD Mode 3" at the dual core logo. and just stays there. Funny enough the computer does the dong but its unable to recognize the tablet in device manager. My computer does have Motorola device manager and Motorola Mobile Drivers v6.4.0_64bit.
IF I reset the tablet with "Power & Vol+" resets, but goes back to rsd mode 3
IF I reset the tablet with "Power & Vol+" and do "Vol-" after wards , it stays at Dual Core Logo, but no RSD mode or fastboot or abd. Just plain logo.
IF I reset the tablet with "Power & Vol+" and do "Vol-" While trying "fastboot flash boot boot.img" It gives me waiting for device prompt
At this point I downloaded RSD lite 5.6.4 but it didnt detect my tablet. So I kept digging until I found a thread about a factory Micro usb cable created by bridgeing pin 1 & 4 and BINGO. RSD lite detected my tablet.
Now I have downladed 3 Sbf hoping one will work:
"HUBWF_W5.H.6.4-20_SIGNED_UCAHUBU01SPLAWIFI_P010_A007_M006_HWwifi_hubble_AP1FF.sbf"
"HUBWF_W5.H.6.4-20_SIGNED_UCAHUBU01SPLAWIFI_P010_A007_M006_HWwifi_hubble_Service1FF.sbf"
"HUBWF_W5.H.6.6-27_SIGNED_UCAHUBU01SPLAWIFI_P011_A009_M007_HWwifi_hubble_Service1FF.sbf"
Here is the catch, rsd unzips , re-enumerates and makes the tablet Reboot executes around 3% , then generates an error:
{
"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"
}
This is as far as I've gotten the sbr files have been hard to get (most links broken). I feel Im at brink of getting it done. I believe the error has to do with the tablet not rebooting in rsd mode, it reboots to the plan back screen with dual core logo .
Any ideas? thanks in advance
any advice? anyone??
here is the log of the rsd lite flashing.
02/21/16 22:51:24 00002244 Phone.cpp 514 0 ERROR Generic failure when sending command.
02/21/16 22:51:24 00002244 Phone.cpp 1655 0 ERROR GetPhoneID failed: ERROR.
02/21/16 22:51:24 00002244 Phone.cpp 514 0 ERROR Generic failure when sending command.
02/21/16 22:51:24 00002244 Phone.cpp 1655 0 ERROR GetPhoneID failed: ERROR.
02/21/16 22:51:24 00002244 Phone.cpp 514 0 ERROR Generic failure when sending command.
02/21/16 22:51:24 00002244 Phone.cpp 1750 0 ERROR GetTechnology failed: ERROR.
02/21/16 22:51:24 00002244 Phone.cpp 514 0 ERROR Generic failure when sending command.
02/21/16 22:51:24 00002244 Phone.cpp 1819 0 ERROR GetSoftwareVersion failed: SendTC failed: ERROR.
02/21/16 22:51:24 00002244 Phone.cpp 514 0 ERROR Generic failure when sending command.
02/21/16 22:51:24 00002244 Phone.cpp 1977 0 ERROR GetSoftwareFlexVersion failed: ReadSeemElement failed: ERROR.
02/21/16 22:51:24 00002244 Phone.cpp 514 0 ERROR Generic failure when sending command.
02/21/16 22:51:24 00002244 Phone.cpp 1866 0 ERROR GetDRMVersion failed: SendTC failed: ERROR.
02/21/16 22:51:40 The FlashLog key is turned off.
02/21/16 22:51:40 Multi upgrade started for 1 phones
02/21/16 22:51:40 [Device ID: 0] Flashing phone.
02/21/16 22:51:49 ERROR: Interface AP-OS: Error flashing subscriber unit. Device API Error: 0xE0020085 Address: 0x1F870 Command: ADDR - on device ID 0.
02/21/16 22:51:49 ERROR: Flash failure: Interface AP-OS: Error flashing subscriber unit. Device API Error: 0xE0020085 Address: 0x1F870 Command: ADDR (Error Code: e0020085),
Detailed Error Details: Direction of the Error=2000, Command Value=200000, Code Group Number=3 - on device ID 0.
02/21/16 22:51:49 [Device ID: 0] Interface AP-OS: Error flashing subscriber unit. Device API Error: 0xE0020085 Address: 0x1F870 Command: ADDR
02/21/16 22:51:49 ERROR: Failed flashing process. - on device ID 0.
02/21/16 22:51:50 Multi upgrade finished.
This MZ604 is from what region?
The 3 sbf files you download are for brazil and south america
Hi,
Because I could not find a reliable rooting mechanism I soldered a serial FTDI UB232, and I gain shell access.
The serial works ok as long I am in u-boot prompt.
Texas Instruments X-Loader 1.41 (Apr 12 2012 - 12:06:17)
OMAP4460: 1.2 GHz capable SOM
**** DDR SDRAM PATTERN TEST ****
DDR SDRAM DATA BUS TEST..... [PASSED]
DDR SDRAM ADDRESS BUS TEST..... [PASSED]
Starting OS Bootloader from EMMC ...
U-Boot 1.1.4 (Nov 9 2012 - 20:33:58)
Load address: 0x80e80000
DRAM: 1024 MB
Flash: 0 kB
Using default environment
printenv
bootargs=console=ttyO2,115200n8 [email protected] [email protected] init=/init vram=48M omapfb.vram=0:32M androidboot.console=ttyO2
bootcmd=booti mmc1
bootdelay=1
baudrate=115200
ipaddr=128.247.77.90
serverip=128.247.77.158
netmask=255.255.254.0
bootfile="uImage"
ethact=KS8851SNL
Environment size: 285/131068 bytes
As soon android boots when everything is settled down, the tty input is totally ignored, though the shell
prints all the os messages. There is no prompt. ?!?
[ 33.844390] wlan0: moving STA 00:90:a9:a5:51:a1 to state 3
[ 58.387908] omap_cpu_thermal_manager:sensor 66200 avg sensor 59795 pcb 0, delta 18897 hot spot 85097
[ 58.397766] omap_monitor_zone:hot spot temp 85097
[ 58.887908] omap_cpu_thermal_manager:sensor 63800 avg sensor 59795 pcb 0, delta 17742 hot spot 81542
[ 58.897827] omap_safe_zone:hot spot temp 81542
no prompt
Any idea how to outcome and enable the shell tty input.
Here are the pictures of the serial soldering and the serial to usb adapter.
(The pictures are mine, from the stack-over-flow post)
{
"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"
}
The ftdi
I found and android for OMAP blaze (GB and a kernel from https://e2e.ti.com/support/omap/f/849/t/310839),
After having all cowboys engineering from Texas headaches I finally end up with:
boot.img cache.img fastboot mkbootimg MLO_es2.1_gp MLO_es2.2_emu ramdisk.img ramdisk-recovery.img recovery.img system.img u-boot.bin userdata.img zImage files.
I tried first a non destructive flash, trying to flash the system, (then boot, kernel, recovery / all of them encountering same error)
Linux console:
sudo fastboot flash system system.img
[sudo] password for mpang:
< waiting for device >
sending 'system' (110304 KB)...
OKAY [ 42.127s]
writing 'system'...
FAILED (remote failure)
finished. total time: 42.137s
marquis tablet serial output, as shown in previous post
OMAP44XX TAB # fastboot
I2C read: I/O error
I2C read: I/O error
Device Serial Number: 5C28000200000001
Fastboot entered...
Starting download of 112951340 bytes
................................................................................... many dots
downloading of 112951340 bytes finished
writing to partition 'system'
Wrong Image... Failed to program
How did we get here fastboot.c 993 ?
Anyone ?, Thank you
Hello.
When I try to turn on NFC, it appears for "ON" and then "OFF".
https://sendvid.com/iykxmguc
I back to stock ROM Android 5.0.2 2.33.401.5. S-OFF, unlock bootloader.
This is my logcat when I try to power ON.
(filtering NFC)
{
"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"
}
logcat without filtering "NFC"
Code:
E/MP-Decision( 1971): Update arg 2
E/QCOM PowerHAL( 964): long long_duration_touch_boost fd -1
E/QCOM PowerHAL( 964): long long_duration_touch_boost fd -1
E/QCOM PowerHAL( 964): long long_duration_touch_boost fd -1
E/QCOM PowerHAL( 964): long long_duration_touch_boost fd -1
E/QCOM PowerHAL( 964): long long_duration_touch_boost fd -1
V/NfcEnabler( 5934): Turn on NFC.
D/NFC ( 5934): callMethod: enable() called with system uid.
D/HtcNfcEnablePromptActivity( 1438): isNeedToBlockCaller: caller uid=1000, follow google flow.
I/NfcService( 1438): getDefaultSE 0
D/NfcService( 1438): Enabling Nfc.
W/Settings( 1438): Setting airplane_mode_on has moved from android.provider.Settings.System to android.provider.Settings.Global, returning read-only value.
I/NfcService( 1438): Enabling NFC
D/PMS ( 964): acquireWL(103ea112): PARTIAL_WAKE_LOCK NfcService:mRoutingWakeLock 0x1 1438 1027 null
D/Nfc-Utils( 1438): NFC default protocol route: 2
I/Nfc-Utils( 1438): Disable eSE: false, false
V/NfcEnabler( 5934): handleNfcStateChanged 2
E/MP-Decision( 1971): Update arg 1
W/NFCJNI ( 1438): Firmware update FAILED
D/ContactMessageStore( 1425): MSG_CHECK_DELETION >>
D/ContactMessageStore( 1425): mDeleteTask = null, bDeleting = false
D/AccFlag ( 1425): sku_id=69
D/ContactMessageStore( 1425): MSG_CHECK_DELETION <<
D/ContactMessageStore( 1425): start background delete task...
D/ContactMessageStore( 1425): size: 0 , 0
D/ContactMessageStore( 1425): Background delete complete
W/NFCJNI ( 1438): Firmware update FAILED
W/NFCJNI ( 1438): Firmware update FAILED
E/NFCJNI ( 1438): Unable to update firmware, giving up
W/NfcService( 1438): Error enabling NFC
D/PMS ( 964): releaseWL(103ea112): PARTIAL_WAKE_LOCK NfcService:mRoutingWakeLock 0x1 null
V/NfcEnabler( 5934): handleNfcStateChanged 1
{
"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"
}
ArrowOS
Code:
/*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, We will laugh at you.
* It is your fault because you chose to do all the modifications on your device.
* Remember projects like these and the work done on them is a hobby to the
* contributors and the team members, no one is working for you nor is getting paid for it
* have some respect for the work done by them since it is done purely on interest or a hobby
*/
ABOUT
ArrowOS is an Android Open Source Project based Android mobile operating system started with the aim of keeping things simple, clean and neat.
Website: https://arrowos.net
Telegram: Channel | TG Portal/Links
Github: https://github.com/ArrowOS
Code Review: review.arrowos.net
E-mail: arrowos.contact
PayPal: Donate to us
Blog: blog.arrowos.net
Checkout more documentation at (maintainership/contributing): Check this out
WHAT WORKS?
Almost everything
WHAT DOESN'T WORK?
You tell me
NOTE!
ONLY FOR REALME UI 1.0 FIRMWARE
Be sure to include a log : check how to
DOWNLOADS
Click here to Download
Tip: Select OEM -> Device,choose Arrow version, choose build type: "GAPPS" or "VANILLA" to download.
Read our blog article/post about:
* HOW-TO report a bug
* GAPPS and VANILLA variants
* Checking build integrity
GPL compliance:
ROM Source- https://github.com/ArrowOS
Kernel Source- https://github.com/ArrowOS-Devices/android_kernel_realme_RMX2020
I was able to flash it, but the phone is unable to mount external_primary for some reason, even if I clean flash it by wiping /data.
Code:
03-27 19:36:08.662 3428 3631 E MediaProvider: Volume external_primary not found, calling identity: UserHandle{0}, attached volumes: {MediaVolume name: [internal] id: [null] user: [null] path: [null], MediaVolume name: [1a8f-aa4d] id: [public:179,129] user: [UserHandle{0}] path: [/storage/1A8F-AA4D]}
03-27 19:36:08.662 1114 1186 E system_server: No package ID 7f found for ID 0x7f0802f3.
03-27 19:36:08.662 1114 1186 E system_server: No package ID 7f found for ID 0x7f14063b.
03-27 19:36:08.662 3428 3631 E DatabaseUtils: Writing exception to parcel
03-27 19:36:08.662 3428 3631 E DatabaseUtils: java.lang.IllegalArgumentException: Volume external_primary not found
03-27 19:36:08.662 3428 3631 E DatabaseUtils: at com.android.providers.media.MediaProvider.query(MediaProvider.java:2693)
03-27 19:36:08.662 3428 3631 E DatabaseUtils: at com.android.providers.media.MediaProvider.query(MediaProvider.java:2684)
03-27 19:36:08.662 3428 3631 E DatabaseUtils: at android.content.ContentProvider$Transport.query(ContentProvider.java:272)
03-27 19:36:08.662 3428 3631 E DatabaseUtils: at android.content.ContentResolver.query(ContentResolver.java:1219)
03-27 19:36:08.662 3428 3631 E DatabaseUtils: at com.android.providers.media.MediaDocumentsProvider.isEmpty(MediaDocumentsProvider.java:1106)
03-27 19:36:08.662 3428 3631 E DatabaseUtils: at com.android.providers.media.MediaDocumentsProvider.includeImagesRoot(MediaDocumentsProvider.java:1120)
03-27 19:36:08.662 3428 3631 E DatabaseUtils: at com.android.providers.media.MediaDocumentsProvider.queryRoots(MediaDocumentsProvider.java:594)
03-27 19:36:08.662 3428 3631 E DatabaseUtils: at android.provider.DocumentsProvider.query(DocumentsProvider.java:915)
03-27 19:36:08.662 3428 3631 E DatabaseUtils: at android.content.ContentProvider$Transport.query(ContentProvider.java:272)
03-27 19:36:08.662 3428 3631 E DatabaseUtils: at android.content.ContentProviderNative.onTransact(ContentProviderNative.java:107)
03-27 19:36:08.662 3428 3631 E DatabaseUtils: at android.os.Binder.execTransactInternal(Binder.java:1179)
03-27 19:36:08.662 3428 3631 E DatabaseUtils: at android.os.Binder.execTransact(Binder.java:1143)
And yes I am upgrading from 12.0. As I mentioned earlier I did try a clean flash but that didn't seem to fix things.
NVM, turns out I messed up with wiping data when I attempted to perform a clean flash.
is it require Realme UI 1.0 only
or
i can install in Realme UI 2.0
because my phone running Realme UI 2.0
please reply
adivgrri said:
is it require Realme UI 1.0 only
or
i can install in Realme UI 2.0
because my phone running Realme UI 2.0
please reply
Click to expand...
Click to collapse
Downgrade to RUI1 using SP Flash Tool then flash the ROM.
Hi @sarthakroy2002, first of all, I would like to express my respect for your work - you've created a selection of quality custom roms for our device. As far as I know, you started from zero with few knowledge about rom development, so it's impressing what you have released so far. Unfortunately, I own the european version of the realme C3, which is not officially supported by the "deeptesting tool" for unlocking the bootloader, but I've found other tools which claim to solve this problem! Soon, I will try them out and hope I can unlock the bootloader in order to try one of your vanilla roms...
didux70 said:
Hi @sarthakroy2002, first of all, I would like to express my respect for your work - you've created a selection of quality custom roms for our device. As far as I know, you started from zero with few knowledge about rom development, so it's impressing what you have released so far. Unfortunately, I own the european version of the realme C3, which is not officially supported by the "deeptesting tool" for unlocking the bootloader, but I've found other tools which claim to solve this problem! Soon, I will try them out and hope I can unlock the bootloader in order to try one of your vanilla roms...
Click to expand...
Click to collapse
I have the same version of the device. You gotta change the region of the phone, there's a pretty comprehensive guide here, which is the one I used back then. https://forum.xda-developers.com/t/...de-to-coloros-11-and-enable-dual-sim.4191787/
IF you run into any issues, give me a heads up and I might be able to help you out.
And yes, his work is awesome, agreed on that, this is a completely different rom without the freaking realme painfully slow OS.
I can't go to recovery useing volume down + Power button
Show me : oppo_verify_pass_ok
Now what can i do?
dipanjan.roy22 said:
I can't go to recovery useing volume down + Power button
Show me : oppo_verify_pass_ok
Now what can i do?
Click to expand...
Click to collapse
There's no recovery key combo for this phone once it's unlocked. You're seeing the bootloader screen, from there you can fastboot reboot recovery. Or from the system, you can adb reboot recovery.
With bbs being fixed for Android 12 I've been tracking the wakelock in the couple of Android 12.1 roms @sarthakroy2002 has made available for the community and came across these results. This was with arrow but I believe the same wakelocks are present with pixel os since I noticed a similar battery drain between the two. Anybody with similar results, or suggestions to fix it? All my sync is kept off alrrady. Thanks