Yesterday my phone offered me to update ColorOS to PEUM00_11_a_12 (about 400 MB)
I did not noticed any change. Still based on Android 11.
Removed chinese software has not been reinstalled afterwards.
Changelog (translated via Google)
system
[Optimization] System stability
[Fix] In the system clone scene, the problem that the live wallpaper disappears after one-click cleaning
[Fix] In some scenarios, there is a low probability that the sound cannot be heard during a call
[Fix] The screen move button disappears when launching some game apps in compatibility mode
[Updated] Android security patch to February 2022 to improve system security
Screen
[Optimization] Bright screen response speed after large screen is expanded
[Optimization] The animation of golden peacock wallpaper shows fluency
Input
[Fix] When the input method is set to the handwriting keyboard, the handwriting keyboard cannot be called up with low probability
[Fix] The problem that the input method cannot be called when the search box on the right side of CCTV is used
camera
[Fix] In some scenarios, the camera crashes with a low probability after being turned on
[Fix] In some scenes, there is a low probability of noise in video recording
To view more content and participate in discussions, please log in:
OPPO社区
www.oppo.cn
Precautions
1. To reduce the risk of version upgrade, it is recommended to back up personal data before upgrading.
2. During the software upgrade process, the temperature of the mobile phone may increase slightly for a short time, and it will quickly return to normal after the upgrade is completed, which is a normal phenomenon.
3. If you encounter any problems during use, please contact the official customer service for feedback or consultation.
The "Rotation" app no longer works for me since this update. Does anyone else have this problem?
Can you elaborate on ""Rotation"?
No more wifi calling option
It seems that after the update, wifi calling is gone. I installed android studio and tried to enable it through the below adb commands, but couldn't get the device to be recognized in recovery mode. Its showing unauthorized in recovery mode.
1) Enable developer options in the phone and enable debugging mode, change to MTP connection
2) adb devices -＞its showing the device named attached
3) adb reboot fastboot -＞ phone is rebooted and shows the language option
4) fastboot reboot recovery -＞ rebooting into recovery, finished
5) adb devices -> showing unauthorized
Does anyone know how to enter the recovery mode in this phone?
trojan1111 said:
It seems that after the update, wifi calling is gone. I installed android studio and tried to enable it through the below adb commands, but couldn't get the device to be recognized in recovery mode. Its showing unauthorized in recovery mode.
1) Enable developer options in the phone and enable debugging mode, change to MTP connection
2) adb devices -＞its showing the device named attached
3) adb reboot fastboot -＞ phone is rebooted and shows the language option
4) fastboot reboot recovery -＞ rebooting into recovery, finished
5) adb devices -> showing unauthorized
Does anyone know how to enter the recovery mode in this phone?
Click to expand...
Click to collapse
Once phone is completely powered off hold the volume down button and power button until phone has started in recovery mode
{
"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"
}
Thanks, Tim-2.0. However, if I use that way to enter recovery mode, I cannot get my device shown up in adb commands.
Using the adb commands to reboot the device and triggered the recovery mode, adb devices show "unauthorized", so I cannot proceed to do the adb shell command.
Tim-2.0 said:
Once phone is completely powered off hold the volume down button and power button until phone has started in recovery mode
View attachment 5556199
Click to expand...
Click to collapse
Yes and to be known because the delete option in the menu isn't working
trojan1111 said:
Thanks, Tim-2.0. However, if I use that way to enter recovery mode, I cannot get my device shown up in adb commands.
View attachment 5556235
Using the adb commands to reboot the device and triggered the recovery mode, adb devices show "unauthorized", so I cannot proceed to do the adb shell command.
View attachment 5556239
Click to expand...
Click to collapse
Uh I see, fair enough..
It seems you were able to boot into fastboot? I cannot even do that. It very briefly does before restarting itself and powering on normally. This flashes up on the screen for about a second but that's it:
Tim-2.0 said:
Uh I see, fair enough..
It seems you were able to boot into fastboot? I cannot even do that. It very briefly does before restarting itself and powering on normally. This flashes up on the screen for about a second but that's it:
View attachment 5557135
View attachment 5557137
Click to expand...
Click to collapse
Yes, I was able to boot into fastboot through the adb command. I have never seen that screen before. Weird, I thought all Oppo Find N phones are the same because there is only one version - CN one.
trojan1111 said:
Yes, I was able to boot into fastboot through the adb command. I have never seen that screen before. Weird, I thought all Oppo Find N phones are the same because there is only one version - CN one.
Click to expand...
Click to collapse
Yeah I figured it out, I was using the wrong adb command
Also, I have solved your device not showing up in fastboot problem! It did the same to me.. Folllow this guide and update the fastboot driver
Actually scrap that, I have just remembered that it was an adb / recovery issue. Have you resolved this yet trojan1111?
Tim-2.0 said:
Actually scrap that, I have just remembered that it was an adb / recovery issue. Have you resolved this yet trojan1111?
Click to expand...
Click to collapse
No, i still haven't been able to solve the problem.
If its happen after update OTA, then you need flash the phone with full file.
PS : You may try factory reset
AzimBahar said:
If its happen after update OTA, then you need flash the phone with full file.
PS : You may try factory reset
Click to expand...
Click to collapse
I tried factory reset already and it didn’t work. I guess there is nothing that can be done because there is nowhere to download the firmware for this phone. Hopefully, the next update will fix this issue.
I’ve seen Firmware is available on ROMdevelopers. BUT it’s required official login to flash.
(Login can get from service Center guy or guy who do remotely)
On another thread, someone was able to download a firmware for the phone.
Find N root
Given the pain of trying to make this phone somewhat functional and something that resembles the level of customisation that I am used to I am thinking I might attempt to root my device. I am pretty sure by doing so I can get Android Auto...
forum.xda-developers.com
Maybe you can take a look on it and download the firmware.
Is there any way to bring wifi calling and volte back ????
I lost them since I updated my device.
Any advice??
z06forever said:
Any advice??
Click to expand...
Click to collapse
No way, also in Japan many of provider lost VoLTE call.
you may try to downgrade to the firmware below, but I haven't heard who tried, so not sure.
Oppo Find N 5G PEUM00 Stock Firmware ROM (Flash File)
Download the official Oppo Find N 5G PEUM00 Stock Firmware ROM (Flash File) for your Oppo Mobile. We also provide all other Oppo Stock Firmware for free.
firmwarefile.com
Related
Hi everyone
My phone screen is completely smashed but it appears that the phone can still turn on. I've connected it to the laptop and it seems to connect (installing driver, etc) but it doesnt come up on windows explorer. Presumably because the phone is encrypt + PIN locked. I tried tapping randomly on the phone screen but my guess is that it is not registering but even if it is it would be impossible to get the right decryption code in.
1. Is there a way to display the screen output either on TV / Monitor / Computer ?
2. Even better can I get the display replicated on the laptop with a USB connection and navigate through that
I suspect the answer to all of this is no and I just have accept the photos are gone. Any ideas are welcome.
Thanks for reading
yeancheant said:
Hi everyone
My phone screen is completely smashed but it appears that the phone can still turn on. I've connected it to the laptop and it seems to connect (installing driver, etc) but it doesnt come up on windows explorer. Presumably because the phone is encrypt + PIN locked. I tried tapping randomly on the phone screen but my guess is that it is not registering but even if it is it would be impossible to get the right decryption code in.
1. Is there a way to display the screen output either on TV / Monitor / Computer ?
2. Even better can I get the display replicated on the laptop with a USB connection and navigate through that
I suspect the answer to all of this is no and I just have accept the photos are gone. Any ideas are welcome.
Thanks for reading
Click to expand...
Click to collapse
Mini hdmi. If your screen is unresponsive though there isn't much point.
Sent from Jelly Fuelled SGS2
Screen is smashed pretty bad though - don't think it is going to work. Will the mini hdmi work without the phone turn on pass the decryption password stage. Thanks for your help
yeancheant said:
Screen is smashed pretty bad though - don't think it is going to work. Will the mini hdmi work without the phone turn on pass the decryption password stage. Thanks for your help
Click to expand...
Click to collapse
Really unsure. I use cm10 so tv out is unsupported but the mini hdmi cables can be picked up on ebay pretty cheap.
Sent from Jelly Fuelled SGS2
theres not much you can do if you got a pin or screen security.did you enable usb debugging?
Do full wipe try to look into pictures of recovery.
Send form Galaxy S2. Using XDA Premium
If you had USB debugging enabled, then you can easily use ADB to copy out your files
Paulius7 : what do you mean by full wipe - I can't see anything on the screen at the moment
Jokesy: The phone is probably stuck at the password to decrypt in which case I suspect adb wouldn't work. I haven't used that before but might give it a go
Thanks for all the suggestions
yeancheant said:
Paulius7 : what do you mean by full wipe - I can't see anything on the screen at the moment
Jokesy: The phone is probably stuck at the password to decrypt in which case I suspect adb wouldn't work. I haven't used that before but might give it a go
Thanks for all the suggestions
Click to expand...
Click to collapse
Did you have USB debugging enabled?
We can still access adb via CWM recovery
I said. You can look into pictures if you can reach CWM(recovery mode)
Full wipe-Is Clean everything but not pictures
{
"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"
}
Paulius7 : The screen is smashed - so I can't really get into CWM - unless I do it blindly and then guess the number of clicks to eventually do full wipe. But I don't understand how full wipe can help "Do full wipe try to look into pictures of recovery. "
Jokesy: I installed resurrection remix - don't know if USB debug is enabled by default. Either way I'm going to download the android sdk and give it ago and see .
yeancheant said:
Paulius7 : The screen is smashed - so I can't really get into CWM - unless I do it blindly and then guess the number of clicks to eventually do full wipe. But I don't understand how full wipe can help "Do full wipe try to look into pictures of recovery. "
Jokesy: I installed resurrection remix - don't know if USB debug is enabled by default. Either way I'm going to download the android sdk and give it ago and see .
Click to expand...
Click to collapse
ICS or Jelly bean?
also its ICS
Somehow my previous entry didn't stick.
So .. the good news is usb debug is on. Downloaded android sdk and java. I'm new at this and this is what happened
adb devices - found the phone
adb shell - got in with root
ls /sdcard/ - empty! presumably due to the encryption or PIN
tried it on the new replacement S3
ls /sdcard/ - all the files came out
any ideas ? I appreciate your help Jokesy and we have seen progress although I accept that the chance of reaching our end point still remains low
yeancheant said:
Somehow my previous entry didn't stick.
So .. the good news is usb debug is on. Downloaded android sdk and java. I'm new at this and this is what happened
adb devices - found the phone
adb shell - got in with root
ls /sdcard/ - empty! presumably due to the encryption or PIN
tried it on the new replacement S3
ls /sdcard/ - all the files came out
any ideas ? I appreciate your help Jokesy and we have seen progress although I accept that the chance of reaching our end point still remains low
Click to expand...
Click to collapse
no that's because /sdcard is not mounted.
follow this tutorial
Boot to recovery, then follow these steps:
1. Connect your device to your pc
2. Open command prompt from Adb folder. (hold shift key, then right click on a blank space, select open command window here)
3. #check if your device is connected via adb by typing in the command window:
adb devices
4. adb shell
5. mount sdcard
6. ## check the directories of the sdcard just to be sure by typing:
ls /sdcard
7. exit
8. adb pull /sdcard \mysdcard
wait for the process to finish
Check you C: drive for a folder named "mysdcard". all the files and folders in your internal storage will be there.
If you face any errors, let me know
Good luck
doesn't seem to work
tried mount sdcard and mount /sdcard and mount /sdcard/
it says mount:can't read 'etc/fstab': No such file or directory
yeancheant said:
doesn't seem to work
tried mount sdcard and mount /sdcard and mount /sdcard/
it says mount:can't read 'etc/fstab': No such file or directory
Click to expand...
Click to collapse
what kernel were you running before your screen broke?
default resurrection remix during the installation - i think its siyah
yeancheant said:
default resurrection remix during the installation - i think its siyah
Click to expand...
Click to collapse
were you using adb from recovery?
probably not earlier. i've tried again - blindly getting into recovery - and i think i did as windows then say installing adb driver - but now when you do "ls" there is no sdcard. tried mount sdcard and the same error message
This is the stock Rom of N & M for Yoga Book LTE & WIFI for the needers
if any dev want to help me developing a dual boot for Yoga Book, just PM me or join Telegram Group for Yoga Book devs and users:
MOD EDIT: LINK REMOVED
Prees the Thanks button if that helps you
How to install it:
Be careful, these steps will erase all your data on tablet and will downgrade rom (stock marshmallow)
First of all: read and understand all of the instructions.
1. Download the stock ROM
https://cloud.kolyandex.su/index.php/s/4WDt6ghOzHAyP4s (Nougat WiFi version)
https://easy-firmware.com/home/browse/category/id/19521/ (Marshmallo LTE version)
https://androidfilehost.com/?fid=817550096634799507 (Marshmallo WiFi version)
2. Extract it to some folder
3. Download Intel Platform Tool Lite from here: https://01.org/android-ia/downloads/intel-platform-flash-tool-lite
4. Install Intel Platform Tool Lite
4. Boot into fastboot mode
5. Run Intel Platform Tool Lite
6. Make sure your tablet is recognized by the tool (otherwise you need to enable USB-debug in Developer settings)
7. Select "flash_update_from_eng.json" from folder in (2)
8. Push "start to flash"
9. Wait... (You should check tablet's screen in order to lock/unlock bootloader (it should be locked after flash in order to install OTA updates))
10. Reboot tablet
11. Your keyboard might not work: that is normal (just use on-screen keyboard for now)
12. After initial setup: open Contacts app, create new one (if there are no contacts yet), tap search and enter ####6020#
13. Choose your region
14. Reboot
15. Setup again (now halo should work)
16. Go into settings -> about -> updates and update till the last version (may take several hours)
17. Say thanks for alexjustes for his Amazing Steps
Thank you so much for posting this!
Have you tried flashing this through @danjac's TWRP build? I know trying to restore any nandroid backup made after the OTA upgrade to Nougat results in a boot loop.
beltani said:
Thank you so much for posting this!
Have you tried flashing this through @danjac's TWRP build? I know trying to restore any nandroid backup made after the OTA upgrade to Nougat results in a boot loop.
Click to expand...
Click to collapse
Unfort. no, because i dont have a YB Android Version, i have win ver.
THE MAXIMUM POWER said:
Unfort. no, because i dont have a YB Android Version, i have win ver.
Click to expand...
Click to collapse
I'm 99% sure this isn't flashable in custom recovery, at least without some modification and repackaging. It's a package designed for Intel Phone Flash Tools.
Still a huge asset, though, so thanks again!
beltani said:
I'm 99% sure this isn't flashable in custom recovery, at least without some modification and repackaging. It's a package designed for Intel Phone Flash Tools.
Still a huge asset, though, so thanks again!
Click to expand...
Click to collapse
Same, it can only flashed through fastboot mode
I got myself into quite the pickle today. I've been considering selling my Yogabook to switch to a Chromebook 2-in-1. I wanted to get the device back to as full vanilla as possible. I "thought" the first step was to lock the bootloader again and then do a full factory reset, apparently not... After booting back up from locking the bootloader I kept getting an Intel "bootloader error code 01" and Android would not start. It would take me to fastboot mode on it's own but I was unable to use the power button to make a selection and the device would just power off after 5 minutes. Thankfully from there or fore powering off I could hold Volume up on startup and get to fastboot manually or recovery. It being in a locked state now though I couldn't do much of anything else, no flashing anything other than loader, no format, no erase, and TWRP was not able to be booted.
Anyway I finally read a post about DNX mode and how to get to it, but nothing on how to really use it or any decent information imho. After finally finding some users on another part of the forum discussing a DNX flashing tool made for their devices HTC I went searching for a tool for the Lenovo. Lenovo has nothing for this (shame on you Lenovo!) but Intel does have it and it can be used with the recovery image posted above in this thread (and I assume all the others running around). And here is the URL for the tool
https://01.org/android-ia/downloads/intel-platform-flash-tool-lite
You just have to load a valid JSON file containing the proper config information for the ROM you are flashing iwithin the Intel tool. For this particular version of the ROM I did have to modify the "flash_recover_dnx.json" file to remove this section
Code:
{
"duration" : 5000,
"restrict" : null,
"tool" : "sleep"
},
Otherwise the flash tool would not load it due to the a bad tool from this JSON config named "tool". No other changes to the settings of the Intel flashing tool were needed.
Just click "Start to Flash" and once it was done all was well. Took a little over five minutes, it unlocked, flashed, and locked the device again itself.
{
"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"
}
No more Intel error stating the device isn't secure every reboot. I did lose all my data that was on it doing this but I wasn't worried about that going into it.
After initial setup in Android I did have to do the trick noted here to get the Halo keyboard working again which then required initial setup once more.
Hope this helps others.
@MarkAllen, thank you for your valuable information. This will help people unbrick their devices.
MarkAllen said:
I got myself into quite the pickle today. I've been considering selling my Yogabook to switch to a Chromebook 2-in-1. I wanted to get the device back to as full vanilla as possible. I "thought" the first step was to lock the bootloader again and then do a full factory reset, apparently not... After booting back up from locking the bootloader I kept getting an Intel "bootloader error code 01" and Android would not start. It would take me to fastboot mode on it's own but I was unable to use the power button to make a selection and the device would just power off after 5 minutes. Thankfully from there or fore powering off I could hold Volume up on startup and get to fastboot manually or recovery. It being in a locked state now though I couldn't do much of anything else, no flashing anything other than loader, no format, no erase, and TWRP was not able to be booted.
Anyway I finally read a post about DNX mode and how to get to it, but nothing on how to really use it or any decent information imho. After finally finding some users on another part of the forum discussing a DNX flashing tool made for their devices HTC I went searching for a tool for the Lenovo. Lenovo has nothing for this (shame on you Lenovo!) but Intel does have it and it can be used with the recovery image posted above in this thread (and I assume all the others running around). And here is the URL for the tool
https://01.org/android-ia/downloads/intel-platform-flash-tool-lite
You just have to load a valid JSON file containing the proper config information for the ROM you are flashing iwithin the Intel tool. For this particular version of the ROM I did have to modify the "flash_recover_dnx.json" file to remove this section
Code:
{
"duration" : 5000,
"restrict" : null,
"tool" : "sleep"
},
Otherwise the flash tool would not load it due to the a bad tool from this JSON config named "tool". No other changes to the settings of the Intel flashing tool were needed.
Just click "Start to Flash" and once it was done all was well. Took a little over five minutes, it unlocked, flashed, and locked the device again itself.
No more Intel error stating the device isn't secure every reboot. I did lose all my data that was on it doing this but I wasn't worried about that going into it.
After initial setup in Android I did have to do the trick noted here to get the Halo keyboard working again which then required initial setup once more.
Hope this helps others.
Click to expand...
Click to collapse
Thank You for the INFOS
The tool does not recognized my device
Please help to flash my yoga book.
Got these with the stock .json file as described above:
06/18/18 12:00:01.188 ERROR : No description value in command sleep
06/18/18 12:00:01.188 ERROR : Cannot create command with tool "sleep"
06/18/18 12:00:01.188 ERROR : Tool sleep not found or invalid tool configuration
Opened that file in notepad and deleted the sleep section - started flashing.
The usb drivers are definitely required, I lost the connection because they weren't loaded. I installed them and refreshed device manager and she started receiving the flash.
Used Win7 to flash also, the intel page says its not supported.
Flash success and locked bootloader after entering the country code - thanks very much all!
jeitana said:
Please help to flash my yoga book.
Click to expand...
Click to collapse
Try installing Android SDK drivers in you PC
Guys, if anyone faced a Probleme during his way to flash the ROM, PLZ tell me the problems with More Details
_Deeb0_ said:
Got these with the stock .json file as described above:
06/18/18 12:00:01.188 ERROR : No description value in command sleep
06/18/18 12:00:01.188 ERROR : Cannot create command with tool "sleep"
06/18/18 12:00:01.188 ERROR : Tool sleep not found or invalid tool configuration
Opened that file in notepad and deleted the sleep section - started flashing.
The usb drivers are definitely required, I lost the connection because they weren't loaded. I installed them and refreshed device manager and she started receiving the flash.
Used Win7 to flash also, the intel page says its not supported.
Flash success and locked bootloader after entering the country code - thanks very much all!
Click to expand...
Click to collapse
Is this compatible with the Yoga Book A12?
I have been away for a while. Why should I want to install this rom?
Ok I wanted to reset this tablet because the SystemUI ap was using %25 of the cpu constantly, I do not know when and hopw this piece of **** got to that level of crappy update, must be some google crap
- Can I unlock the OEM bootloader?
- Can I still use the twrp->Magisk method to root this?
thanks
Shawnki91 said:
Is this compatible with the Yoga Book A12?
Click to expand...
Click to collapse
Sorry but no
hajkan said:
I have been away for a while. Why should I want to install this rom?
Click to expand...
Click to collapse
No Need to reinstall this Rom if you have already your System, both are 100 % same
hajkan said:
Ok I wanted to reset this tablet because the SystemUI ap was using %25 of the cpu constantly, I do not know when and hopw this piece of **** got to that level of crappy update, must be some google crap
- Can I unlock the OEM bootloader?
- Can I still use the twrp->Magisk method to root this?
thanks
Click to expand...
Click to collapse
Reinstall the Rom will fix this, but doing factory reset will fix this too
In case anyone wants the wifi only M firmware here it is https://androidfilehost.com/?fid=817550096634799507
Hi there,
I recently bought a LG K40s and wanted to unlock the bootloader in order to root this phone. But I could't find any instructions on how to do this nor a fastboot mode for that phone.
Does anyone know how I can get root access on this phone?
Thanks in advance,
Oebbler1
Fastboot: switch off the smartphone by holding the Power button for a couple of seconds. Then connect the Type C USB cable with your PC or laptop. Now push Volume Down and connect this cable with your device. When
hi. I try to root this device but when I use ADB this don´t go to bootloader, the device reboot in normal mode. I look TWRP web and this device isn´t in the list
Any method to root this device?
Regards
Help
we need to create a post to get help to root and install twrp on LG K40s
@jessepinheiro50
To root Android as 1st thing of all things these requirements must be achieved
{
"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"
}
Next step is to install the USB-driver matching your device
Then check you can access phone from PC via USB
Code:
adb devices
and that boot-loader can get unlocked
Code:
adb shell "getprop ro.oem_unlock_supported"
and if returned value=1 verify that you can deal with phone's boot-loader
Code:
adb reboot bootloader
fastboot devices
Next step is to boot into phone's boot-loader, and unlock it WHAT WILL ERASE ALL DATA ON YOUR PHONE
Code:
fastboot OEM unlock
fastboot reboot
At last step you flash the software that will add root to Android
Code:
adb devices
adb sideload <ROOTING-SOFTWARE-ZIP>
adb reboot
Any news?
Any news on how to root this device?
solve ?
renanflores85 said:
Any news on how to root this device?
Click to expand...
Click to collapse
there is an apk that search for what program can root the current android, and the only it show was stumproot, idk if is safe, i never saw it before, but searching for it, it show that is a root program for lg
jwoegerbauer said:
@jessepinheiro50
To root Android as 1st thing of all things these requirements must be achieved
Next step is to install the
Then check you can access phone from PC via USB
Code:
adb devices
and that boot-loader can get unlocked
Code:
adb shell "getprop ro.oem_unlock_supported"
and if returned value=1 verify that you can deal with phone's boot-loader
Code:
adb reboot bootloader
fastboot devices
Next step is to boot into phone's boot-loader, and unlock it WHAT WILL ERASE ALL DATA ON YOUR PHONE
Code:
fastboot OEM unlock
fastboot reboot
At last step you flash the software that will add root to Android
Code:
adb devices
adb sideload <ROOTING-SOFTWARE-ZIP>
adb reboot
Click to expand...
Click to collapse
this don't worked, it just reboot the phone, and it show 1 when it check if is possible to use boot-loader
letsbrick said:
this don't worked, it just reboot the phone, and it show 1 when it check if is possible to use boot-loader
Click to expand...
Click to collapse
Try
Code:
fastboot flashing unlock
instead of
Code:
fastboot OEM unlock
jwoegerbauer said:
Try
Code:
fastboot flashing unlock
instead of
Code:
fastboot OEM unlock
Click to expand...
Click to collapse
That's not work for me. adb don't identify the device and only wait.
wallrony said:
That's not work for me. adb don't identify the device and only wait.
Click to expand...
Click to collapse
yeah is waiting for any device
So... The problem is that "adb reboot bootloader" doesn't init smartphone in bootloader, but in normal boot process. it's feasible to think about how to "unlock" the "boot of bootloader", since LG may have blocked in this device.
we should create guides in XDA how to install drivers on PC
as this is common hardship for many.
most preferably some autoinstaller of all drivers, for all devices (taken from manufacturers)
indestructible master said:
we should create guides in XDA how to install drivers on PC
as this is common hardship for many.
most preferably some autoinstaller of all drivers, for all devices (taken from manufacturers)
Click to expand...
Click to collapse
No, that's not the problem. Fastboot commands run only when the device's in bootloader device.
So, i solved to persist and search many ways to see something. And that, i got in recovery menu (with Restart System, Wipe, Start ADB sideload - but without connection with PC, as a not connected device, the connection isn't stablished because adbd is a not found command from device shell, in the log returns that, and system wait more or less of 5 minutes to back to recovery menu). In that, i could see the recovery logs, and the last is the normal procedure of a factory reset, i think. In that i encountered some properties that are defined by default:
Code:
ro.boot.flash.locked=1
ro.treble.enabled=true
ro.bootloader=unknown
ro.product.name=mmh551m_f
And by peace of mind, i run
Code:
adb shell "getprop ro.bootloader"
on PC terminal with adb and that returns me the "unknown" that i see in the log. Running
Code:
adb shell "getprop"
returns all prop of the system, so that can be examined to make something. So... I tried to change property using setprop, like ro.boot.flash.locked to 0, or ro.bootloader to any value, but no success.
And to finalize, in contact with LG support whatsapp, the ChatBot returns me a message saying that the bootloader function isn't available by secure reasons.
I think that the value was simply hided from the original value to not access the bootloader, but it's in device ... But with no permission to change the value and not know what value set in the prop.
There are a guide to unlock the boot-loader, but not yet to root.
Root LG K41S + SafetynetAPI pass
Disclaimer These kind of modifications are not for the faint of heart!!! Flash/modify at your own risk!!! I will not be responsible for bricked phones, Dead batteries, world war 3, yada yada yada..... you Know the Rest. :sneaky: Introduction...
forum.xda-developers.com
I followed this process and it doesn't go past the [ fastboot OEM unlock ] step.
I just get < waiting for any device >
However, when I try to use Google Pay and other such apps, I am faced with a security issue.
The question is: Is the bootloader unlocked or not ?
If so, how to relock it ?
Have a device of this wich has a problem with the screen apparently, after changing the screen it wont boot, no battery animation when charger is connected, only a red light and a smooth periodical vibration. If i hold power on and any vol buttons it seems to try boot showing lg logo but fail quicly and keeps off.
Something happened when i repaired it was that side buttons flex got broken so had to order a new one, it passed a lot of time to receive it but i believe that day with broken flex when testing the new screen i think i've seen the battery animation... Im not sure.
But seem its a common issue in this model. So is there something i can do to fix the mainboard?
Hi guys, I'm here to learn something about Android Security System.
I have this Sapphire TV BOX
model: DWI259S / UIW4020ETI / UIW4020ETI2 (Sapphire)
SoC: Broadcom BCM7271
The goal of this post is to understand how I can gain root access on this device
I know how to turn it in recovery mode .
if you are interested you can read this Reddit post from ams_sharif
"You can boot to recovery by switching the unit off ( the black button in the back), then while holding the power button (the one on the side, next to the pair button) turn the set top box on until the recovery shows up."
This is what I see.
{
"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 tried to flash an update.zip in order to see if I can execute command through any script, but the verification of the signature fails.
I tried to click on "Apply update from USB" (that is adb sideload) , but connecting the tv box on the pc nothing happen, no device found neither with "adb devices"
I tried also to click on "Reboot to bootloader" but "fastboot devices" command return nod devices connected.
My idea was to read the recovery image from fastboot extract it and try to compile my own TWRP
Do you have any suggestions to guide me in the right way?
@element14
When you enter
Code:
adb devices
and don't see an entry listed under the “List of devices” section, then your device isn't connected to PC.
Same is case when you enter
Code:
fastboot devices
Recovery option "Apply update from USB" isn't equal to "adb sideload". This option assumes the Update.Zip you want to flash is located on USB-device connected with your TV box.
With regards to rooting your TV box you can try to flash Chainfire's SuperSu Pro.
BTW: TWRP isn't a recovery image you compile in order to flash, it's merely a touch-enabled replacement for device's Stock Recovery menu as shown by you
Example screenshot:
jwoegerbauer said:
@element14
When you enter
Code:
adb devices
and don't see an entry listed under the “List of devices” section, then your device isn't connected to PC.
Same is case when you enter
Code:
fastboot devices
Recovery option "Apply update from USB" isn't equal to "adb sideload". This option assumes the Update.Zip you want to flash is located on USB-device connected with your TV box.
Click to expand...
Click to collapse
I tried to flash a custom script that use the
Code:
u_print()
function , but the signature verification fails i get an
Code:
errorr:21
jwoegerbauer said:
With regards to rooting your TV box you can try to flash Chainfire's SuperSu Pro[/url].
Click to expand...
Click to collapse
Are you sure that I can flash an unsigned zip like superSu , with a stock recovery and locked bootloader ?
jwoegerbauer said:
BTW: TWRP isn't a recovery image you compile in order to flash, it's merely a touch-enabled replacement for device's Stock Recovery menu as shown by you
Click to expand...
Click to collapse
The TWRP is an open source project , all the source code is avaiable. But to have it works , you need the original kernel .
I tought , If I can unlock the bootloader I can read the image of the recvoery.img and from it extarct the kernel
Thanks for your answer.
@ element14
did you manage to make the device usebale?
Hello, i am also interested to reset\flash this device but I couldn't find any useful guide, did you manage to root it or flash it, I want to use it as android STB.
As long as you can establish an USB-connection ( read: ADB connection ) then you can root any device's Android OS, otherwise NOT.
Any updates on this topic? It would be great to know if someone was able to root it.
If this is the etisalat version of this box I have gotten APKs to work on it.
xilogofficial said:
If this is the etisalat version of this box I have gotten APKs to work on it.
Click to expand...
Click to collapse
What apk exactly?what you can do with this apk? And how you installed?
element14 said:
What apk exactly?what you can do with this apk? And how you installed?
Click to expand...
Click to collapse
I think it lets you install any APK on the device. Check https://emiratestel.github.io/website
There is only one port. Is there any other way? And how can i play videos from usb
xilogofficial said:
I think it lets you install any APK on the device. My method:
Going to apps list:
- insert usb
- click browse
- go up to internal storage, press ok, click Apps
part 1
- go to apps list, keep usb inserted
- scroll to Files, click it, click open
- if it opens skip to part 2
- else it will crash and show the first time boot
- go to apps list again while keeping usb inserted
- open files again
part 2
- connect a mouse to other USB port, navigate into the USB and into where you placed your APKs
- double click the apk to install it
- on first time install, it will show an error about unknown sources
- click settings on the prompt
- enable all sources shown
- continue installing the app
Click to expand...
Click to collapse
There is only one usb port. Is there any other way? And how can i play videos from usb
there's another on the bottom, or use a USB hub.
you can't play videos from USB without installing third party apps.
xilogofficial said:
If this is the etisalat version of this box I have gotten APKs to work on it.
Click to expand...
Click to collapse
Good Day! Appreciate your support . Dear Exactly Etisalat TV box model: DWI259S, but it is locked on Etisalat home page with their logo as I don't have Etisalat subscription any more, in that situation how possible to browse an APK file as you said in below steps? 2nd thing there is no standard Firmware available by Manufacturer (Technicolor), Please make a video or at least solve with help of photos and help us close this topic. Till date solution is not yet provided, Please help, Thanks and appreciate your support
.
element14 said:
Hi guys, I'm here to learn something about Android Security System.
I have this Sapphire TV BOX
model: DWI259S / UIW4020ETI / UIW4020ETI2 (Sapphire)
SoC: Broadcom BCM7271
The goal of this post is to understand how I can gain root access on this device
I know how to turn it in recovery mode .
if you are interested you can read this Reddit post from ams_sharif
"You can boot to recovery by switching the unit off ( the black button in the back), then while holding the power button (the one on the side, next to the pair button) turn the set top box on until the recovery shows up."
This is what I see.
I tried to flash an update.zip in order to see if I can execute command through any script, but the verification of the signature fails.
I tried to click on "Apply update from USB" (that is adb sideload) , but connecting the tv box on the pc nothing happen, no device found neither with "adb devices"
I tried also to click on "Reboot to bootloader" but "fastboot devices" command return nod devices connected.
My idea was to read the recovery image from fastboot extract it and try to compile my own TWRP
Do you have any suggestions to guide me in the right way?
Click to expand...
Click to collapse
Any Luck dear, Please advise as I want the same solution and receive same error 21.
engr.sys said:
Any Luck dear, Please advise as I want the same solution and receive same error 21.
Click to expand...
Click to collapse
Kindly Join our Discord Server Link :https://discord.gg/sbFnauNTWy
I can help u there
Hi
Can you please share the APK please ?
any update on this? did anyone managed to finally root this device or least sideload and apk?
b1acktiger said:
Hi
Can you please share the APK please ?
Click to expand...
Click to collapse
PM Me
Can you please share the APK please ?
Hey All
Its been a while since I got to play with anything these days but I recently found one of these POS 10in touchscreen units in the dumpster and it fires up into a menu running android. So I was hoping I could reflash this and use it like a tablet given it's also got a small thermal printer in it, so maybe try and save it from e-waste
I searched online for more details and came across this HERE which is identical to what I have so hoping I can root it and flash it with a clean android?
I would love to repurposed this to use as a touch screen tablet or similar, since it's got a GSM module and can take an SDCard too as I opened it up and took some pictures and I managed to get it in a recovery mode as well - from the PIX its using a rockchip RK3368
{
"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 am not sure if the mini usb port is a OTG port to try and use ADB but I have not been able to do much with it and hoping someone can guide me through to possibly a reflash or ways to unlook root and add in another bootloader/rom
I've downloaded the files from citaq website but so far not been successful to do much with it, has anyone played with these and turned them into something more practical for the home?
Here's hoping for some tips - Apology if this is in the wrong section, move as needed :good:
Cheers
Kosti
@Kostiz
Device actually is running Android 5.1.1. It seems it has only 1GB RAM what is far too little to run a full fledged Android.
As long as you don't replace device's Stock Recovery by TWRP or similar recoveries, after a successful rooting don't install Magisk and/or Xposed Framework, you're on the safe side to play with, IMHO.
As 1st step check whether device is accessable by means of both ADB and Fastboot.
jwoegerbauer said:
@Kostiz
Device actually is running Android 5.1.1. It seems it has only 1GB RAM what is far too little to run a full fledged Android.
As long as you don't replace device's Stock Recovery by TWRP or similar recoveries, after a successful rooting don't install Magisk and/or Xposed Framework, you're on the safe side to play with, IMHO.
As 1st step check whether device is accessable by means of both ADB and Fastboot.
Click to expand...
Click to collapse
Hey, Thanks for chiming in!
So in order to get ADB and or Fastboot its suggested to enable USB debugging in the device system settings, but I am not sure on how to do this, would it be safe to assume this is already USB debug is already enabled?
Could I back up the original stock recovery
I'm a little green on the whole process hence looking thought I'd ask here, I don't think I even have an OTG cable handy
I will see if I can load ADB on a windows box and try and talk to this unit
Cheers
Kosti
@Kostiz
An OTG-cable isn't needed, because the recovery menu
doesn't give you the opportunity to load something from an USB-device
OK, some success!
I went back and connected a mini USB straight to the PC and ADB driver installed detected the android device.
Ran ADB in windows powershell
So whats the best method to backup the entire ROM, and recovery files in the event I stuff this up?
Do I use just ADB for this or someother tools?
I did try one tool here from the vendors website but stuck as not sure what the Chinese characters mean..
Is the fact that this is only 1G i couldn't run Android at all and needs to be stripped down?
Cheers
Kosti
@Kostiz
Android Oreo Go Edition is a lightweight distribution of Android that runs better than normal Android on devices with <= 1 GB of RAM
How to backup device's Stock ROM is eplained here.
Thanks again mate!
Seem I have to do a lot of reading and thankfully everything is here, just got to spend time to read and have a go!
BTW how do I go about using volume rockers and power button to move around the menu in recovery when there is none but only the two buttons as shown the reset and recovery buttons on the main board?
BTW, the current ROM installed boots into a special menu, all other settings are hidden, would there be a way to enable seeing all the items and when getting the the settings (gear icon) that pops up in the corner, only takes me to the standard wifi menu to choose a wifi, so it seems everything else is hidden, if by enabling these I could potentially not need to do anything other than stop the default application from starting up - if that makes any sense
Could I just get back into a adb shell and try
adb shell
su
pm enable applicationname
I have to read up on rooting first I assume before I do much more, this is getting exciting, LOL :good:
Kostiz said:
BTW how do I go about using volume rockers and power button to move around the menu in recovery when there is none but only the two buttons as shown the reset and recovery buttons on the main board?
Click to expand...
Click to collapse
You use Android's HOME button to navigate within the Recovery menu, use POWER button to select option.
Hi, fellas! Please help me with one of these Citaq H10 POS. All we have is bootloop with some custom ROM showing vendor's logo.
Forcing it into recovery gives me some dead android screen with "No command" text.
Please guide me through this challenge, cause I have no other option but to ressurect it somehow.
Good news is that I have another one that is working fine, so we could try cloning it or something. Please help!
Yet I can't attach pics, cause of few posts, but if needed I can PM some.
citaq h10-2
I am also stuck with this machine citaq h10-2 , i did use a wireless kb to move up/down and not the 2 buttons on the motherboard , i can talk with it with ADB but all you can do is put it in sideload to upload new firmware and put it in fastboot but in fastboot you only get a black screen , what I have don is > opened up developer mode but you have no OEM UNLOCK tick box in side so running any bootloader unlock dose not work and i have run them all, if you google this machine for flashing new firmware you only get XDA this forum, unless any body knows another place to get the info from please let us know as i do think this would make a nice tablet with printer, the firmware is 5.1.1 and would love to put 6.0 or above on it but. i did download some firmware and used sideload to install it but it come up with error , i did try and make a backup but cannot do it ?, I think the firmware was from a galaxy s5 , I am not into all this firmware flashing so I am learning as I go along and if I brick it up well it was for free any way as the takeaway was shutting down and he gave it to me so no loss, if any body knows how we can get 6.0 or above on this machine please let us know.
A big thank you to all that can help put android 6.0 or above on this tablet.
Did you guys take a look at the solution here ? It worked for me ! All with a 2k ohm resistor...
Hola, alguien tiene la Rom de este dispositivo?