Hello,
first of all I'm sorry If I post in wrong thread (not sure that should I post inside Oppo Reno5 or Oppo Reno Z). But to the point.
I just get brand new Oppo Reno 5Z 5G (CPH2211). From the beggining I have problem with update installaion (OTA doesn't work at all*). First of all I was suprised that smartphone doesn't get most current update (available was update with Android 11) but it's not important right now. Anyway I had problems with update installation but finally I made online update inside recovery mode. I thought that maybe with next updates (I knew that few more is waiting) will be no more problems but like with first update OTA doesn't work*. So I went to the recovery mode and try to update phone same way but suddenly when I choose online update inside recovery it doesn't find and wifi network. I have no more idea what more I can do. The only clue I have is that looks like recovery doesn't have some kind of permissions because when I choose inside recovery mode option "install from storage" it won't display any folders/files.
* By OTA doesn't work I mean that it normally download update, verify it but when it comes to installation process starts but just after few seconds it stops and phone boot with notification failes. Same behaviour using "OPPO System upgrade tool". Ofc I tried factory reset, clearing data in downlanding/update managers etc and same.
Related
Hi everyone,
I seem to have nothing but trouble when it comes to installing OTA updates for my Gear Live, and am wondering if anyone can help me.
It all started when the Android 5.1.1 update notification arrived on my Gear Live some time ago. I eagerly installed it, and expected it to install without any problems. Unfortunately, the update reached around 30%, before displaying the Android mascot with a red exclamation mark. I managed to restart the watch, and re-downloaded and installed the update. The same thing happened, except, it was stuck in a boot loop :crying:
I contacted Samsung Australia who took the watch in for repairs (it took them 4 weeks). I was pretty happy to see the watch working again, and running the 5.1.1 update.
Just yesterday, I received a notification that an update is ready to be installed. I swiped and hit install. The watch rebooted, and began the installation. Again, reaching 30% before failing and displaying the Android mascot with the red exclamation mark. I am yet again stuck in a boot loop. I managed to tap the Android mascot, which brought up the Android System Recovery. It said
"Installation aborted.
OTA failed! Please power off the device to keep it in this state and file a bug report!"
I have cleared the cache, and have wiped the data through recovery. This seems to allow the watch to boot up, however, the process repeats itself when I try to update it again.
Does anyone know why the update would be failing, especially after it has already been repaired by Samsung, and how I can fix it myself (I don't really want to be without a watch again for 4 weeks)?
Thanks,
Tim
Did you try the live restore tool? (read the whole thread)
Brendo said:
Did you try the live restore tool? (read the whole thread)
Click to expand...
Click to collapse
I attempted to use it, however, it was unable to detect my device.
Update: I attempted the update again, which failed. However, instead of wiping the data, I navigated to 'Install via ADP' (or the likes), which brought up an error message:
Verifying current system...
"/system/priv-app/ClockworkHomeGoogle/ClockworkHomeGoogle.apk" has unexpected contents.
E:Error in @/cache/recovery/block.map
(Status 7)
Installation aborted.
OTA failed! Please power off the device to keep it in this state and file a bug report!
Click to expand...
Click to collapse
tims1710 said:
I attempted to use it, however, it was unable to detect my device.
Update: I attempted the update again, which failed. However, instead of wiping the data, I navigated to 'Install via ADP' (or the likes), which brought up an error message:
Click to expand...
Click to collapse
Try a different usb cable? (ie official, not a cheap one)
My watch always took a few goes to get detected by adb
tims1710 said:
I attempted to use it, however, it was unable to detect my device.
Update: I attempted the update again, which failed. However, instead of wiping the data, I navigated to 'Install via ADP' (or the likes), which brought up an error message:
Click to expand...
Click to collapse
I had that exact error yesterday when I was trying to install new OTA update. I flashed back to KMV78Y(from live restore tool v2) Don't use v3 it has corrupted file and breaks bluetooth.
Try to manually flash using fastboot. I wouldn't recommend trying to flash recovery partition from live restore tool since you can end up with a broken OTA and broken adb sideload. Also, don't try to flash TWRP into recovery partition. Loading it into ram memory is fine though.
Anyways, to manually flash using fastboot, you need to open console and go to directory of Gear live restore tool. Make sure your watch is in bootloader mode, not recovery. Type fastboot flash boot 78Yboot.img and then fastboot flash system 78Ysystem.img Do factory reset just in-case and upgrade your way up to latest firmware.
Recently I tried out the Nougat preview on my EVA-L09C636. It was ok but seeing as there was a problem with fonts and I'd lost root access, I began thinking about going back to MM.
To prepare for downgrade I tried using srktool to bring TWRP back (and I think this is my big mistake as srktool uses a TWRP made for MM, not N, is that right?). After I tried to restore TWRP I noticed "not recognised" errors when I connected my phone to PC again.
System recovery using hajuuk's Firmware Updater and HiSuite looked like it would complete but near the end of the process (the restoring system part) HiSuite aborted itself saying my device wasn't supported. This has left my P9 is in an unusable state where the only thing I can access is fastboot. Also I can't turn off my phone - holding down power simply makes it reboot then get stuck at the "Your device ... can't be trusted / Your device is booting now" screen.
Reading around a bit I attempted to unbrick it without any luck:
1. downloaded EVA-L09C636B152 update.zip from http://forum.xda-developers.com/p9/development/rom-stock-rom-eva-l19c636b168-t3419586 and installed Snoop05's 15 seconds ADB Installer.
2. extracted images from update.zip using Huawei Update Extractor and did
Code:
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash cust cust.img
then tried rebooting holding volume up + power several times (but never got past untrusted device boot screen).
3. extracted contents of update.zip to folder 'dload' on a blank sd card, trying to force update several times by rebooting and holding down power + volume up + volume down (still never get past the screen saying my device is booting).
At this point I'd be happy to get anything happening on my phone - Marshmallow, Nougat or even some other ROM so I can use my device again.
Any ideas? I'm on EVA-L09 C636.
i2ectcf said:
Recently I tried out the Nougat preview on my EVA-L09C636. It was ok but seeing as there was a problem with fonts and I'd lost root access, I began thinking about going back to MM.
To prepare for downgrade I tried using srktool to bring TWRP back (and I think this is my big mistake as srktool uses a TWRP made for MM, not N, is that right?). After I tried to restore TWRP I noticed "not recognised" errors when I connected my phone to PC again.
System recovery using hajuuk's Firmware Updater and HiSuite looked like it would complete but near the end of the process (the restoring system part) HiSuite aborted itself saying my device wasn't supported. This has left my P9 is in an unusable state where the only thing I can access is fastboot. Also I can't turn off my phone - holding down power simply makes it reboot then get stuck at the "Your device ... can't be trusted / Your device is booting now" screen.
Reading around a bit I attempted to unbrick it without any luck:
1. downloaded EVA-L09C636B152 update.zip from http://forum.xda-developers.com/p9/development/rom-stock-rom-eva-l19c636b168-t3419586 and installed Snoop05's 15 seconds ADB Installer.
2. extracted images from update.zip using Huawei Update Extractor and did then tried rebooting holding volume up + power several times (but never got past untrusted device boot screen).
3. extracted contents of update.zip to folder 'dload' on a blank sd card, trying to force update several times by rebooting and holding down power + volume up + volume down (still never get past the screen saying my device is booting).
At this point I'd be happy to get anything happening on my phone - Marshmallow, Nougat or even some other ROM so I can use my device again.
Any ideas? I'm on EVA-L09 C636.
Click to expand...
Click to collapse
did you wiped data, cache, dalvik?
snapdesign said:
did you wiped data, cache, dalvik?
Click to expand...
Click to collapse
Hi! I'm not sure how to wipe data, cache or dalvik, because when I upgraded to Nougat this apparently removed TWRP.
Also I'm wondering if trying to use srktool to reinstall TWRP for 6.0 might have corrupted my 7.0 phone?
Is there any way to wipe data, cache, and/or dalvik now? Or are there other things I could try to unbrick?
Although my phone was in a pretty bizarre state - it would get hot and sit on the booting now screen until battery died - I was able to use DC Phoenix to make it boot up again. At that point it had no themes and only KitKat-esque icons. A reset and upgrade later icons and themes work and I'm back on stock Marshmallow. Here's an outline:
1. Google "Huawei Bricked phone repair guide with DC Phoenix", go to the first result and look at the instructions (I can't post URLs yet).
I used Method 1. But note! The newer versions of DC Phoenix are missing a feature that the instructions make clear you have to use. To get the original version used in their guide, you have to download the latest version of DC Phoenix, open it on your PC, then click "Enter Support Area" which logs you in to a download section. Find "DC Unlocker Softwares", "DC_Phoenix", then download DC_Phoenix_v14.rar and run that instead. Whether it's Method 1 or 2 make sure you complete it - i.e. the fastboot flash step AND a step they call "flashing in upgrade mode."
(Also note that for DC Phoenix you want to feed it the oldest version of firmware available for your phone, in my case b152. This is because themes and icons won't be fixed until it receives the next version of firmware as an update.)
2. Once I did the fastboot and upgrade flash, I did a system reset from the Settings app trying to get themes and current icons again. (This didn't work but doesn't do any harm or might have helped somehow further down the line).
3. I used hajuuk's Firmware Updater and HiSuite to upgrade to the next version of firmware available (in my case b168).
3. All fine and your phone is back to stock - icons look nice again and local themes are back. To get the original icons layout, go to Recents, hold down on the Trash Icon, show system apps, and Clear Data for Huawei Home.
i2ectcf said:
Although my phone was in a pretty bizarre state - it would get hot and sit on the booting now screen until battery died - I was able to use DC Phoenix to make it boot up again. At that point it had no themes and only KitKat-esque icons. A reset and upgrade later icons and themes work and I'm back on stock Marshmallow.
Click to expand...
Click to collapse
Thanks for sharing! You saved me!
I have a European Huawei P9 EVA-L09 model which I adore. It was running Marshmallow and EMUI 4.1. I found a Nougat beta ROM and I tried to install it but have left it in an unusable state.
I don't think the phone is rooted but I do think the bootloader is unlocked.
I can boot into 3 modes.
Mode 1 - Just reboot
Huawei eRecovery where I get the options to download latest version and recovery, Reboot and Shutdown. If I select the Download latest version and recovery it setups my Wifi and then fails with the message Getting package info failed.
Mode 2 - Power + Vol Up
It boots into a screen that gives me the option to Reboot your System Now, Wipe data / factory Reset , Wipe Cache partition. Selecting Wipe Data/Factory reset returns back to this screen with an error - Red Exclamation mark. Selecting Wipe Cache partition seems to perform a wipe and returns to the original screen with the 3 options again.
Mode 3 - Connect to PC with Hisense and power + vol down
This goes into an android recovery screen which is white with a green android displayed
I have the USB drivers installed on my PC but I cannot see the phone in Windows explorer when I plug it in via USB. I do hear the recognition tone that Windows has recognised that a USB device has been attached. The Huawei PC software doesn't recognise it unless I go into the white android screen and select recover. This always fails saying it cannot find a package.
I have installed stock P9 Marshmallow firmware on my SD card in a dload folder (which is how I bricked it in the first place. When I hold Vol up and Vol Down and power it starts installing but then fails about 40% - 50% through. I have tried multiple versions of the L09 firmware but none of them install successfully.
I am not very technical and not an android expert so cannot say I have done everything perfectly correctly. #
Is my phone bricked or is it possible get my phone back working?
You can get your phone back, search the forums for dc phoenix, which has helped people including myself.
The other option is to go the huawei website, and look under downloads for p9. Find the two firmwares for beta rollback and follow the instructions, although i am not 100% confident that will work for you
use dc phoneix ... i was the in tha same condition
So I have installed and tried install a few different ROMs to the phone. DC Phoenix recognizes the phone as it comes up with the IMEI and version in the left hand window. It seems to install the ROM sucessfully.
I get a message at the end saying it finished successfully but when I boot back up it just goes straight into the same eRecovery screen I have tried B166 and B322 and no luck. Is there anything different I should be doing?
...and now I have a new issue
Thanks for everyone's help. After downloading and trying about 10 different ROMs I was able to get a Nougat ROM to install. Now I have a different problem
1. When I reboot I get a verification failed message. I get an option to go to eRecovery (which works the same as above and doesn't find a package)
So what I really want now is just to get back to stock Marshmallow and not have a verification message and not have some Nougat version that doesn't look like the official Huawei ROM.
So what next folks?
I encountered the exact same problem a few days ago. I didn't try DC Phoenix, instead sent it to Huawei for repair, claiming the phone was in a boot-loop I couldn't recover from.
They have fixed it now and the P9 is on its way back to me. What's strange is that they have swapped the whole motherboard for a new one! Didn't expect that.
Hello friends,
I rooted my P20 Pro (CLT-L29) after this guide:
https://forum.xda-developers.com/hu...ide-getting-started-unlock-twrp-root-t3806180
And everything works pretty well.
I'm on 8.1.0.156(C432) right now. Now, a new system update/patch (CLT-L29 8.1.0.156(C432patch03)) appeared in the updater. It's a small update/patch that weights 9,5 MB and, according to the notes, has a camera/flash fix.
So far so good. I went through this guide on how to OTA-udpate a rooted P20 Pro:
https://forum.xda-developers.com/showpost.php?p=76844754&postcount=254
and flashed the recovery_ramdisk_nocheckP20.img.
Then I went back to the updater and pressed "Download and Install". After the download, the phone reboots and you see the update process, which ends with "update successful", and the phone boots up again.
Now, if I go back to Systemupdates, the same update reappears as a new, uninstalled update again. If I press "Download and Update" again, the same update process happens, but after the phone boots back up, the update in not installed and shows up as a new update.
I tried it 4 times now, without any success. What may cause that ever going update loop? Is something wrong with the recovery_ramdisk_nocheckP20.img? Is there something like a stock recovery I can download and use? Any other suggestions? I've my back to the wall with that thing :crying:.
Every help/suggestion/hint is welcome.
Best regards,
m00h
Hi
I have a very strange case with my P20 PRO 128GB Single Sim. About a week or two ago, I got a message that my phone found a new system update. I was very happy because I was still stuck on 9.1.0.311 because my phone never got the update to 10.
What was my surprise when it turned out that the update has exactly the same number that I have now uploaded to my phone.
I found that I did not have time to install the update yet, so I kept delaying it.
I was also supposed to do a data backup, unfortunately I didn't have time.
Last night my phone was updated. Unfortunately, it did not start normally after this update.
Constantly stops on the screen:
Your device has loaded a different operating system.
To learn more, visit:
http://zh.ui.vmall.com/emotiondownload.php?mod=restore
....
Your device is booting now ...
Then it goes to eRecovery.
I tried to do Update and recover system in this eRecovery, unfortunately after connecting to Wifi and trying to find information, I get the information Get package info failed
The Emergency backup option does nothing. The phone restarts and goes to the first screen Your device has loaded ...
I wanted to repair my phone via Fastboot & Rescue mode and HiSuite, unfortunately I get the information that "System restore is not supported on this device"
If I hold Volume Up + Power on the turned off phone, I enter the menu where I have the option Update mode and Clear data. In Clear data, I chose Wipe cache partition and then Safe mode, but it didn't help.
I wonder if by Update mode and, for example, through Memory card / OTG update mode or USB update mode, I would be able to restore the system and recover the data.
What do you think about it? Is there any chance to recover data (mainly photos and videos) or accept the loss and try to do Factory reset?