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
Related
Hello there,
my issue is that when i go in bootloader mode, i have a blackscreen, then my phone switch off. The system ui (custom rom Crdroid) and the recovery (orange fox) are working well.
I recognize also that when i reboot, i don't have anymore the MI logo where you have the status of your bootloader when it's unlocked.
More of it, when i plug it on windows , i cannot access to its usb storage (i tried also in mounting it through twrp, but same issue), nothing appears. For example, with an "adb devices" cmd command, no device can be found.
When i check the Windows devices manager, i can see an "unknown usb device" (i tried to force to reinstall drivers on it like the latest google usb driver, but windows refuse it, saying that it has the best and latest one for it).
{
"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"
}
Debugging mode is well enabled
Drivers have been reinstalled (the latest miflashtool install all what is needed)
Nothing appears on my smartphone when i plug it to windows (before i had a notification ot choose in charge mode, usb mode, etc...)
Plug to different usb port has been done without succeess
The phone doesn't appear in miflashtool obv
Restoring a previous backup didn't change the issue (i'm using the custom rom crdroid).
I guess all the things are linked but how i can fix it if i don't have access anymore to my bootloader mode to be able to flash some *.img via fastboot or if i cannot transfer files to my phone to operate in recovery, and more WHAT to do?
I hope you guys, will be able to help. The issue can be really annoying, and stuck me in "no rom update and no transfers of anything possible" situation.
Thank you beforehand
@bonbonboy
Try flashing the firmware through recovery from here https://androidfilehost.com/?fid=11410963190603850663 then reboot device and send it to bootloader via command adb reboot bootloader
It works like a charm!
Mi logo back, adb commands run, usb transfers work and no more error in the device manager.
You saved my day :good::good::good: Thanks a lot !
Hey all!
I have a Light Phone 2 which uses Android 8.1. It's a neat little device that I'd love to tinker with. There is a detailed guide explaining the build process ontop of Android 8.1. The TL;DR is the Light Phone uses LightOS which is another word for an app that site on Android 8.1 that has lower-level access, similar to how the settings app works.
There is a medium post outlining the build process entitled Building LightOS with React Native. I cannot link to it as I do not qualify for the 10 post minimum. So you'll have to google it.
I can get to the Android recovery screen. Although from there I can't do anything. As adb is locked to only sideload and mounting the system produces no results on my Linux machine.
I realize very few people have this device and can comment from experience but does anyone have any idea how to go about rooting this phone? Or getting it to a state to begin tinkering?
Thanks!
@kennethashley
Before starting to try to root phone's Android test whether you can enable these 2 options in Android's Settings -> Developer options:
{
"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"
}
If YES then you have to find a Custom Recovery matching your device what is prerequisite to flash any Rooting software.
jwoegerbauer said:
@kennethashley
Before starting to try to root phone's Android test whether you can enable these 2 options in Android's Settings -> Developer options:
If YES then you have to find a Custom Recovery matching your device what is prerequisite to flash any Rooting software.
Click to expand...
Click to collapse
Unfortunately, that is the thing, the phone does not have these settings available. I was hoping there would be a way to do this directly from the recovery menu
@kennethashley You can access the recovery menu by power and volume up at the same time. When you reach the screen that says "no command" press power first, then volume up, then quickly release volume up first then power. There, you should be able to put the phone into recovery mode.
you can then put the phone into fastboot mode and use adb tooling to enable oem unlocking so you can root the device.
This dude did it on reddit: reddit.com/r/LightPhone/comments/jqtfu4/heres_how_to_get_a_shell_on_the_lightphone2_and/
I need to get a backup
A samsung tab s3
A question
1. buy a new display for 200.-
2. buy a new phone for 200.- and take the backup for the new phone
3. you can't get a backup without login in your phone, cause the display is broken
You will never get an answer in the samsung forum..
because only absolute professionals have the answer to that
The stupid samsung programmers in china never made a programm not even had an idea that this could happen...
You could unlock your phone at "find my mobile" but regrettably the smart samsung programmers had set every phone with broken dispaly in offline status. In that state it is impossible to reactivate your phone to unlock it
You can restart your pc
You can install kies
You can put 1000 times the usb cabel out and in
You can restart your phone
no chance...nothing your phone keeps offline even when it shows the folder at the windows explorer
The two way verification is for samsung much more important than a backup for the user and that against the background that in 1 billion accounts only 1...
"1" will be hacked
@xda24xx have you tried external keyboard on USB?
Is ADB set in dev options?
Which OS btw?
bmwdroid said:
@xda24xx have you tried external keyboard on USB?
Is ADB set in dev options?
Which OS btw?
Click to expand...
Click to collapse
{
"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"
}
@xda24xx phone's OS
bmwdroid said:
@xda24xx phone's OS
Click to expand...
Click to collapse
You can't connect a mouse or keyboard on this broken android display because you can't see anything. The display is complete dead
At https://findmymobile.samsung.com/#home you can unlock it but
the phone is offline till you login, but you can't login cause display is dead
I could unlock the phone at find my mobile when the battery was fully charged
Now more Problems
1. Smartswitch doesnt work when the phone is in energie save mode
2. Phone is unlocked but the file transfer is not switched on so it shows an empty folder.
3. Kies can't connect the phone no one knows why
4. The ADB drivers old or new can't find a device
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.
Tablet name: Toshiba Excite AT10-A-104
Release date: 12/17/2013
Android version: 4.2.1
CPU: tostab12BL (armv7l 32-bit)
GPU: nVidia Tegra 3
I would like to access FASTBOOT mode, but I can't. As I said in the title, I never did root or factory reset or flashed anything, so tablet had always this "protection".
This is what I tried:
1) power_button + volume_down => tablet just restarts
2) USB debugging turned on > command prompt > adb reboot bootloader => tablet just restarts
But I can enter 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"
}
If you have any idea or if you can send me tutorial how can I enter FASTBOOT, please help. I did a lot of research but can't find solution.
consider the fact fastboot mode is simply removed by OEM.
curious what's behind the last entry in recovery menu?
aIecxs said:
consider the fact fastboot mode is simply removed by OEM.
curious what's behind the last entry in recovery menu?
Click to expand...
Click to collapse
Thank you, I thought as well that this is a dead end. Last option throws error (SD card is not mounted), don't know what it does.
guesswork, that's same option as "apply update from external storage" but it also allows unsigned update.zip (like custom ROM)?
what you could try is root with SuperSU. download SR3-SuperSU-v2.79-SR3-20170114223742.zip rename it update.zip and copy to MicroSD Card.
now insert SD Card into tablet and try the last option "apply customization from external storage"
in case that succeeds you have rooted your tablet without the need of fastboot (if that's what you're interested in). However, please note there is no way to undo rooting.
I wanted to try things out, but since I don't have fastboot mode access then I will just try to sell tablet, thanks for help.
fastboot is very limited mode, mainly used for flashing. this can be achieved with other tools like tegra-flash, nvflash.
furthermore on such ancient device there is good chance bootloader is shipped unlocked