Today(23-Oct) I recieved a notification for restarting my mobile(Nokia 1 TA-1066) to update, after completion of my update , touchscreen of mobile isn't working,
I did a factory reset & still the problem isn't resolved,
Will it be possible to restore the earlier android version(I mean 8.1 version without today's patch) by SD card update option in bootloader mode(achieved after pressing volume up+power key).
I don't have bootloader unlocked & developer options enabled.
I tried to restore Android by placing image from https://forum.xda-developers.com/nokia-1/development/rom-ta-1060-stock-oreo-8-1-t3809578 in SD card & installing update via bootloader mode,I got signature mismatch error.
SholiSJ said:
Today(23-Oct) I recieved a notification for restarting my mobile(Nokia 1 TA-1066) to update, after completion of my update , touchscreen of mobile isn't working,
I did a factory reset & still the problem isn't resolved,
Will it be possible to restore the earlier android version(I mean 8.1 version without today's patch) by SD card update option in bootloader mode(achieved after pressing volume up+power key).
I don't have bootloader unlocked & developer options enabled.
I tried to restore Android by placing image from https://forum.xda-developers.com/nokia-1/development/rom-ta-1060-stock-oreo-8-1-t3809578 in SD card & installing update via bootloader mode,I got signature mismatch error.
Click to expand...
Click to collapse
If you're talking about installing an earlier version such as Android nougat the Nokia 1 comes with Android 8.1 out of the box and you can't downgrade
Related
Hello experts,
I've bought a Huawei u8860 today but when I try to switch on, it goes automatically ( without push any other buttons ) in recovery mode.
I've tried to wipe and format cache, but once rebooted it goes always in recovery mode. The phone is brand new, unboxed today from a box with security stickers.
I've tried to update software from sdcard with its original firmware but it fails with this error:
-- Install /sdcard/dload ...
update package's ext name error.
E: ota_pre_update error.
Installation aborted
I don't think it is a software problem, but an hardware error. Do you agree?
I need an advice from you: try to flash again o give back the smartphone to the store?
Thank you
Stefano
tintin74 said:
Hello experts,
I've bought a Huawei u8860 today but when I try to switch on, it goes automatically ( without push any other buttons ) in recovery mode.
I've tried to wipe and format cache, but once rebooted it goes always in recovery mode. The phone is brand new, unboxed today from a box with security stickers.
I've tried to update software from sdcard with its original firmware but it fails with this error:
-- Install /sdcard/dload ...
update package's ext name error.
E: ota_pre_update error.
Installation aborted
I don't think it is a software problem, but an hardware error. Do you agree?
I need an advice from you: try to flash again o give back the smartphone to the store?
Thank you
Stefano
Click to expand...
Click to collapse
I think if you download the official firmware from huawei, then put the dload folder on an SD card, then flash it (hold the + - volume buttons and power button in until there comes a screen of installing firmware) then it should be ok.
if not, you can always look at this post
http://forum.xda-developers.com/showthread.php?t=1552038
hope it helps!
I remember i had the same issue once.. i installed STOCK ICS .4.0.3 via dload method.. and than everything worked fine..
i guess it might be issue of faulty recovery.img file
Hey XDA Dev,
I own a Z3TC (SPG612) for a while now. Maybe rooted with the kingroot (don't remember the exact name), didn't unlocked the bootloader, installed TWRP, flashed (well, the current and broken one) to 23.4.A.3.6 (5.1.1 ?) and all was fine for months.
And today, because I saw a stupid supersu notification, I say OK, let's update supersu binary (done that several times without issue).
Well, it ended in a bootloop where I could still use TWRP.
Because I found a thread which say "flash kernel fixed the issue", and because I also read that "recovery is totally separated from main Android and also for Kernel" and also probably because I forgot the weird Xperia recovery install (on the system ? Something like that ...) .. I decided to flash a kernel from a previous backup (after flash, I will remember to always backup .. so 1 before and 1 after ..) with version 23.1.A.0.690.
Definitely, it was the worst idea of the day. Now, I still have bootloop, but I lost the recovery access (no more vibration during bootloop).
For now, I take a break ... The device don't wont to stop with power button and I had to use power-vol+ to "force reset" which bring the tab down. I can still start it and continue the infinite bootloop if required.
I tested USB connection to my Linux (without anything set for not) and I'm not able to get the green light : vol- + connect = red light, green light then off (about 1s).
If I try with vol+, I'm able to get the blue light (not of the death I hope).
So of course, any help would be appreciated.
I am reading this for now : https://forum.xda-developers.com/showthread.php?t=1849170
I also read an article (in french) 2 days ago saying supersu had lots of problems and for Xperia, still not fixed. Well, I go through this (and I get caught).
Am I alone ?
What's your advise ?
Thanks
Good news, device is accessible via fastboot
Bad news, the device has normally a locked bootloader ...
Good news, I already backed-up the TA keys (several times with differents updates but I suppose they didn't change).
EDIT: Is that possible to flash only the kernel using fastboot ?
Because I could make it works back to the previous bootloop state, which is still better with TWRP.
EDIT2 : I analysed all my possibilities before going ahead. First, the FlashTool seemed to work in fastboot but not flash mode (because the green led was not staying green, only for 1s and both off). So, I thought only fastbootmode was working.
I tried to flash the fotakernel of the device but failed, probably because the BL was not yet unlock.
So, in order to avoid unlocking the BL, I tried with PC companion. I used the repair function, this also updated to Android 6 (was in 5, rooted, with recovery installed too).
It says to boot in flashmode (well, greenlight). I did and the led was off, as expected. I thought it was not working but at the and, I got a successful repair
started back the device ... it works
So, problem fixed, upgraded to MM, I've just lost the root and the recovery TWRP.
Here are some steps about what's happened :
---
In 2016-03, installed version SGP612_23.4.A.3.6_R3C_Japan Generic_1290-3027_PRFCreator-1.2_SuperSU-2.65_DualRecovery-2.8.26.zip on my z3tc.
On 2017-06-02, an update of supersu break the boot and goes to bootloop.
Trying to fix it by flashing an old kernel from the previous backup (I found easy to try with a backup of TWRP, flash only the kernel .. of a previous backup of a previous firmware version). Since then, lost access to TWRP and device wont power off : have to hard-reset and it sleep then.
Remaining access :
- flashmode (=ADB : green led) : not working, the device wake up after a short time and reboot in a loop, disconnecting the flashmode (saw it through FlashTool) => unstable and unusable
- fastboot (blue led) : working and stable, but could need to unlock the bootloader to permit flash.
Fortunately, there is several backup of the TA and I should be able to re-lock the firmware and restore TA files.
Tried to fix using PC companion (so, avoid to unlock the bootloader ... even if I have TWRP TA backup : better to avoid it ...).
It finishes with OK : now running on 23.5.A1.291-R3D
And this fixed the Z3TC
---
Please note that using the PC Companion for the fix in flashmode (vol down and connect) didn't trigger any restart of the device during the repair process.
At the end, I am surprised that it had worked that way.
But it's OK, the devices seems to works, have to reconfigure it now.
Hello Everyone,
I own a Motorola quark XT1225 64GB indian version. I had earlier rooted it and installed Lineage OS 14.1 (Unofficial) in it. The installation was without any issues and worked for few months then one day i pressed the power button to turn on the phone and it went into a boot loop and nothing would work. i gave it to a repair shop and he installed android 6.0.1 in it and gave me back. But my phone wont connect to WIFI and later i found out that there was no IMEI or any network related information left in it. only the OS booted and nothing else was working. Even the Developer options were not available as for some reason tapping the build number was not giving any result. he refused to fix it. I tried a factory reset from the settings menu with no result. even the recovery was not available any more in the phone. I tried installing new android stock images both for android 5 and 6 first from RSD lite and fast boot mode which kept failing and then i tried it using the command promt. After installation was complete the phone rebooted and android appeared with erasing written under it but then it went into boot loop and would keep restarting every time android appeared. I tried installing TWRP recovery from the command promt the initial image of the recovery appears but then next second it says unable to mount data and keeps rebooting again and again. Kindly suggest ways to fix my OS as well as have my IMEI restored.
Really need help.
Thanks a lot.
Good Morning,
Friday night I downloaded the new EMUI 9.1., the official version, and I installed it during the night.
I used my phone all the Saturday but it was extremly slow. I swiched off my phone several times but it never helped me.
At some point in the afternoon, the phone is reseted alone and I have not been able to use it anymore.
The phone only resets itself: it turns on, reaches the blue screen that says "Honor" and resets again. It can not be turned off.
I tried to do a HW reset (power off + volume up) but nothing happens: it reaches the blue screen and it resets again, and again and again...
The only interaction I can have is with the "Fastboot & Rescue mode" screen. Here I get the error: AP_S_Abnormal 64.
Phone Locked FRP lock.
And nothing more.
Would someone be so kind to help me or give me some recommendation/advice of what I can do?
Thank you
From where did you get EMUI 9.1?
I think he meant 9.0 and not 9.1
Soforid said:
Good Morning,
Friday night I downloaded the new EMUI 9.1., the official version, and I installed it during the night.
I used my phone all the Saturday but it was extremly slow. I swiched off my phone several times but it never helped me.
At some point in the afternoon, the phone is reseted alone and I have not been able to use it anymore.
The phone only resets itself: it turns on, reaches the blue screen that says "Honor" and resets again. It can not be turned off.
I tried to do a HW reset (power off + volume up) but nothing happens: it reaches the blue screen and it resets again, and again and again...
The only interaction I can have is with the "Fastboot & Rescue mode" screen. Here I get the error: AP_S_Abnormal 64.
Phone Locked FRP lock.
And nothing more.
Would someone be so kind to help me or give me some recommendation/advice of what I can do?
Thank you
Click to expand...
Click to collapse
So because :
- your device reboot itself to bootloader mode because 'AP_S_Abnormal 64'
- Phone is Locked FRP lock
- you don't manage to enter recovery mode to do a full wipe / factory restore
You could :
- download and use a dload package with an sd/card or an USB-OTG flashdrive in dload mode.
- or use Honor service center help
- or try again and again to boot right to recovery mode to format.
- or try erecovery restore via wifi in erecovery mode
- or try Hisuite Restore option
I think they all will restore your device to factory stock, meaning the actual user datas would be lost...
---------- Post added at 14:51 ---------- Previous post was at 14:45 ----------
Pro tips to enter recovery mode :
-USB must be unplugged (not plugged to computer)
-Hold VolumeUp key BEFORE device vibrate first at boot and keep holdind UNTIL you are in recovery mode
-Try again to reach 'recovery mode'
the pie update has been pulled because of the recovery error , have a google about it
The Mero said:
the pie update has been pulled because of the recovery error , have a google about it
Click to expand...
Click to collapse
Google heard nothing about that here...
oslo83 said:
Google heard nothing about that here...
Click to expand...
Click to collapse
https://uk.community.huawei.com/honor-phones-34/honor-9-stuck-on-erecovery-loop-after-emui-9-official-update-4340
https://uk.community.huawei.com/software-40/load-honor-screen-after-reboot-stf-l09-9-0-1-162-c432e2r1p5-4131
https://translate.google.co.uk/translate?hl=en&sl=it&u=https://www.optimagazine.com/2019/04/26/scelta-estrema-per-honor-9-aggiornamento-con-emui-9-e-stato-ritirato-per-i-suoi-problemi/1444771&prev=search
Google is your friend
I updated to 9 through hisuite because no OTA update was found . tried it and rolled back to 8 cause they removed image stabiliser fron video recording . I read somewhere else that the update was pulled cause so many were having issues , but i always do a hard reset after updating and had none of the issues described , guess i was lucky.
The Mero said:
https://uk.community.huawei.com/hon...covery-loop-after-emui-9-official-update-4340
Google is your friend
I updated to 9 through hisuite because no OTA update was found . tried it and rolled back to 8 cause they removed image stabiliser fron video recording . I read somewhere else that the update was pulled cause so many were having issues , but i always do a hard reset after updating and had non of the issues desribed .
Click to expand...
Click to collapse
If you say so.
So we should think B162 erecovery is not pushed anymore ?
oslo83 said:
If you say so.
So we should think B162 erecovery is not pushed anymore ?
Click to expand...
Click to collapse
Yeah it looks like it was a bit of a mess so just have to keep checking if they release an update for the update lol
Hello all,
I simply did the EMUI 9.0 update through my phone and when it booted back up I was stuck on eRecovery. No option from there works and it keeps booting up on erecovery (download latest version brings "getting package info failed and the factory reset does nothing, it completes than reboots to erecovery).
I tried everything (firmware-finder + I can't use the dload method because this phone has no sd card access). The bootloader is locked as I'm a casual user who just did official updates through the phone menu.
Any help please? I'm kind of desperate right now!