Hi dear XDA community. I would like to kindly ask you all for your help regarding a strange issue with an Oppo smartphone.
1 week ago i bought for my son (11YO) a used Oppo Reno 5G smartphone from an online market place here in UK. He is more proactive than me with smartphones and he told me that the phone can't be updated and he can't download from Google play any benchmark apps like Antutu or 3D mark. All other games or Device info apps can be installed without any issue. The phone shows in File manager 0 B unusued space but i can copy files, take photos and install games without any issue.
The phone was supposed to be an Oppo Reno 5G and looks identical with Reno 10X. On the side of the body is written with tiny letters "Model: CPH1919 Made in China" The imei checked online on few sites returns Oppo CPH1921.
Specs as shown in all device info apps: Snapdragon 845, Andreno 640, 8GB ram, 256GB, 12Mp or 48Mp camera.
Model shown in phone PAFM00. In software update menu is written "This is already the latest version ColorOS 6 PAFM00EE_11_A.01".
I've studied this issue in the past 2 days on my spare time. Installed Oppo adb drivers and interchanged with android adb drivers. Here's the outcome.
With the phone off, when i press Volume down and power buttons, it flashes an image for quarter second with a winking head icon with headphones and some text in Chinese which I've translated: "Has entered Fastboot Press and hold the power button for 6 ~ 10 seconds or reinstall the battery and exit". As long as i kept these buttons pressed it flashes on and on every 3 seconds. If i release them, phone restarts and Oppo logo appears going back to normal.
Using ADB tools (different version, Studio), only "adb devices" returns the model number and "device" after. All other adb commands (adb reboot, usb, reboot-bootloader and adb reboot recovery, etc, i tried most of them) returned "error:closed", for "fastboot devices" nothing is shown, "fastboot flashing unlock" i get "waiting for device".
I've tried to install stock Rom. Using Volume up and power buttons with QPST i get sometimes Qualcomm and sometimes "Q/QCP-XXX (Sahara Download)", because the phone somehow restarts right after i release these buttons and lose connection.
Any advice to update this device and to make it to properly show the correct model will be awesome.
Thank you for any reply.
{
"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"
}
update
Update: in the Developer options i have "OEM unlock Bootloader unlocked" but it's greyed out.
I've downloaded from firmware27 both stock roms CPH1921 and CPH1919, but the included msmdownloadtool requires a username and a password to continue, so anyone can help me with, please? Any advice how to extract XML from OFP? I've stepped in a field that's going deeper and deeper.
Related
Hello everybody,
want to ask your advice in re: following issue
I am going to use nextbook NX868QW8G tablet as an embedded advertisement solution ie it should start when external power gets plugged in. I can find a normal tech desc of this model in the internet even on the official site.
It have almost the same look&hardware as NX785QC8G availabe at wallmart but have slightly another cpu mtk8382 and embedded 3g modem which was the decisive factor since we need tablets to be updated remotely.
Here are system settings:
{
"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 have done the following:
1) rooted device via cydia impactor - root check apps from gplay are saying its rooted now + it has auto instaled chainfire SU to the tablet. For some reasons cydia impactor thinks its HTC ONE X. I have installed a PdaNetA4150 and it also considers it as HTC phone. I have tried to install drivers for nextbook8 I have found in internet but window doesnt recognize them as appropriate. At the moment device is recognized as unknown MT65XX Android phone
2) run adb reboot-bootloader
3) run fastboot oem unlock
4) run fastboot oem off-mode-charge 0
I have tried doing it manually and through cydia impactor but in both cases the command thread for #3 and #4 seems to be in an infinite sleep - just displays "..." in command line shell and cydia impactor simply gets frozen for a couple of minutes then throws timeout exception.
I think its waiting my input after #3 however the screen remains black and it does nothing when I press on vol up/down/power buttons. Fastboot prints "OK [X sec]" when I call fastboot reboot from another shell window.
In regards to the adb drivers and etc - device is visible through both 'adb devices' and 'fastboot devices' commands. For some reasons
Please advice in which direction to seach and digg.
Any help will be highly appreciated,
Max
Recently I have found in my drawer an old Yarvik Noble 97ic+ (Tab09-410) tablet, I got around 2014. Unfortunately it had a broken DC charging connector and the microUSB wasn't enough to kickstart it back to life. So I decided to disassemble the tablet and after some time I managed to charge it and actually turn it on. It booted up and everything. I left it to charge a bit more, but after coming back I found that the tablet no longer boots and all I can get is the "YARVIK" logo stuck on the screen. I have found another customer with exactly the same problem - He charged the tablet for a bit too long and bricked it.
What I can do with the tablet is get it to show with the "adb devices" and I can get it to STOCK recovery, which unfortunately only allows to flash images verified by the manufacturer. I tried all the options in recovery - wiping the cache, data/factory reset and recovery system from backup.
The Yarvik brand, which was a small company in the Netherlands went bankrupt a while ago and there isn't any support or stock firmware images on the web. I only found some dead links on the site arctablet.com, where I also found some users that successfuly flashed a newer android - a rom for Odys Iron CM12.1 lp 5.1.1 (stock is 4.2.2)
When I reboot it into bootloader the screen is completely dark and "lsusb" command shows only the usb port without any device name.
When I tried the "adb reboot-bootloader" command in the console, the device is no longer recognized (with fastboot devices). I assumed it might be because of missing windows drivers, so after trying a whole bunch of them I connected the device to linux with same results. When I reboot it into bootloader the screen is completely dark and "lsusb" command shows only the usb port without any device name. Therefore I cannot install any custom recovery like CWM or TWRP which would allow to flash another than the original Yarvik image.
Is there anyone that could provide the original Yarvik "Tab09-410.img"? Any help is widely appreciated. Thank you for your precious time.
{
"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"
}
Bump. Anyone?
search for odys-iron-jb4.4.2-V1.04
willem
I am in Android 11 C.06 ver. I installed deeptest app for this version. And when I open the app button says Request to exit deep testing like I already applied. When I click the button it shows No network connection. I tried both WiFi and data, no luck so far. And when I click on the Query approval status it says Application not submitted. (See the screenshot for clarification).
So I downgraded to Android 10 A53 version. Then the deeptest app worked fine and my request accepted. But when I click on the Start in depth test the phone reboots to system instead of fastboot. Tried hardware key combination and adb commands. It's just shows the fastboot logo and reboots to system. (The same thing happened with android 11 too)
So again I upgraded to 11 and still the same issue exists in deeptest app like shown in the screenshot. I searched a lot in Google. Never found anything.
Someone please help me. I just want to unlock ky bootloader.
And when I decoded the deeptest apk, I saw a lot of deprecated functions in the app like network connectivity check, etc. But If that was the issue, then why it's working on other RMX3 SZ phones?
Also tried different deeptest apps. No luck.
{
"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"
}
You should wait for 10 minutes after approval deep test it's works only on a06 version .. don't try on a53 there is risk to brick device for more help watch this channel https://youtube.com/channel/UC3ZscJ8C4y1LN1bmNIMz_pw I am on pixel plus 3.7 July 10 nice full os without bugs
akhilakhi84 said:
I am in Android 11 C.06 ver. I installed deeptest app for this version. And when I open the app button says Request to exit deep testing like I already applied. When I click the button it shows No network connection. I tried both WiFi and data, no luck so far. And when I click on the Query approval status it says Application not submitted. (See the screenshot for clarification).
So I downgraded to Android 10 A53 version. Then the deeptest app worked fine and my request accepted. But when I click on the Start in depth test the phone reboots to system instead of fastboot. Tried hardware key combination and adb commands. It's just shows the fastboot logo and reboots to system. (The same thing happened with android 11 too)
So again I upgraded to 11 and still the same issue exists in deeptest app like shown in the screenshot. I searched a lot in Google. Never found anything.
Someone please help me. I just want to unlock ky bootloader.
And when I decoded the deeptest apk, I saw a lot of deprecated functions in the app like network connectivity check, etc. But If that was the issue, then why it's working on other RMX3 SZ phones?
Also tried different deeptest apps. No luck.
View attachment 5355071
Click to expand...
Click to collapse
He was able to unlock his bootloader, I'm in the same situation as you, only attacking version A.53 I can't find OTA updates to upload to Android 11, maybe if you could guide me to upload to C.06 I would appreciate it
I have downloaded the OTA Realme 2.0 update and installed it. The phone won't start after that. No bootloop but on the screen keeps flashing after booting successfully in the system. I tried wiping data in recovery but no help. I am willing to roll back but it won't let me take a backup which is why I landed here. I cannot access the file manager to paste the rollback update files or to take a backup.
I have the exact same issue. This problem generally applies to all Realme devices upgraded to Realme UI 2.0. The root cause is the disabling of com.coloros.weather.service package, usually done during debloating through adb. Further analysis I have done is explained on my thread.
Quick fixes you have now:
If you have adb enabled and ticked "Always allow from this computer" on the prompt below when your phone is still working, you can connect your phone in the blinking state and issue the following command: adb shell cmd pm enable com.coloros.weather.service. Then, reboot your phone. It will work normally on Realme UI 2.0.
{
"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"
}
Click to expand...
Click to collapse
[DATA LOSS] Download this ozip and put it on an SD card. A used SD card works fine as long as it isn't encrypted and has enough free space. Make sure the file name matches your device model. Enter realme UI Recovery (on Realme 7, you press VolumeDown + Power, which might differ for each device) and choose 'Install from Storage'. Enter your device password, select 'SD Card', and pick the ozip you have downloaded. The phone will wipe itself, and you end up with a working phone on Realme UI 1.0.
[DATA LOSS] If your phone is still on warranty period, go to any Realme Service Centre, and use the following statement; the service centre will either replace your phone free of charge or if they don't have any replacements in stock, put you on a waitlist and calls you back once the replacement device is available.
I am updating my device to Realme UI 2.0 when suddenly the device turns off and reboot itself. Now, this device won't allow me to unlock it.
Click to expand...
Click to collapse
Hey I'm new to this forum and Android Tablets in general. I have received a Vodafone Smart Tab 4G, which doesn't boot up. It's an old Tablet and it hasn't been used in a couple years. I want to see if I can make it boot up and test whether it's still usable for minor tasks. I thought I'd try to install an update using an SD card, but it's surprisingly impossible to find anything from an official source. The service menu does say "KTU84P release-keys" which seems to suggest that it has Android 4.4.4 installed.
What I've tried so far:
1: Go into the service menu and do a factory reset.
2. Try to find an update file to install through SD card method (to no avail)
3. Put some alleged stock roms onto an SD card and try to use the update function (fails on the verification step)
4. Installed ADB & Unsigned Mediatek Vcom Drivers on Windows 10. ADB has no connection to the Tablet.
5. Downloaded and tried SmartTab4G_Recovery_KK_benjaminwan to no avail. It gets stuck at "waiting for device".
6. Downloaded SP Flash tool, but failed to find a ROM for the Smart Tab 4G with a scatter file.
7. Out of desperation I tried to flash it with a Smart Tab 3G Rom which had a scatter file, but when I press download nothing happens.
My current understanding is that the standard service menu isn't meant to be used to flash the firmware. If I had an official update file I might have had some success, but I couldn't find one. All the other attempts involving a connection to my Windows 10 PC failed, which seems to indicate that I might be using bad drivers. I'm honestly at my wits' end and I don't understand why this is any more complicated than going to the manufacturers website, finding my device, downloading the most recent system software and flashing it through the service menu. Hope someone can help me out with this one.
Update: Tried a different computer. Partial success. Device manager actually recognized an Android device this time. I installed the usb driver and the recovery batch actually didn't get stuck on "waiting for device" this time. That's great news, although I didn't get much further. Here's what I got:
{
"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"
}
Thread can be closed. I got it after all with the help of the available information. Turns out the recovery.bat was a dead end. Not sure why it didn't work for me with the batch. I tried the approach explained here with cmd and it worked fine.
fastboot -i 0x1bbb oem unlock
fastboot -i 0x1bbb boot cwm.img
Once I was in the cwm everything went smoothly since verification was disabled and I could install a custom rom. This probably took me way longer than it should've, but at least it's working now.