I tried to root android 8.1, then it came up with a error message on startup saying:
This device has loaded a different operating system
ID: (serial number)
This device will shut down in 30 seconds
and it also has an unlock icon.
But I managed to boot to TWRP and I tried flashing the ota itself but it still wouldn't work so I flashed the Nougat OTA and it now boots to recovery instead of the error message. Now I tried to sideload the OTA but it will come up with the error " failed to read command: No error"
By the way I did try OST LA but it was stuck on checking device status.
Use OST LA version 6.0.4. That works. If I understood correctly, you flashed official ROM and OTA through TWRP. You can't do it. ROMs are installed only through OST and OTAs only through official recovery (which TWRP isn't)
Benderisas said:
Use OST LA version 6.0.4. That works. If I understood correctly, you flashed official ROM and OTA through TWRP. You can't do it. ROMs are installed only through OST and OTAs only through official recovery (which TWRP isn't)
Click to expand...
Click to collapse
Thanks a lot, now my phone is working after flashing nougat with OST LA 6.0.4 instead of 6.1.2. Now my phone will probably explode with notifications .
nintendobuster420 said:
I tried to root android 8.1, then it came up with a error message on startup saying:
This device has loaded a different operating system
ID: (serial number)
This device will shut down in 30 seconds
and it also has an unlock icon.
But I managed to boot to TWRP and I tried flashing the ota itself but it still wouldn't work so I flashed the Nougat OTA and it now boots to recovery instead of the error message. Now I tried to sideload the OTA but it will come up with the error " failed to read command: No error"
By the way I did try OST LA but it was stuck on checking device status.
Click to expand...
Click to collapse
hi
can i ask how did u flash while theres no download mode working
hammohammo said:
hi
can i ask how did u flash while theres no download mode working
Click to expand...
Click to collapse
download mode did work i just held the power button and volume down and it booted up into download mode
Related
Hi there! I have this question which I'd love to have answered because I've been on this issue for around 2 days straight.
Long story short:
Tried to flash custom recovery using fastboot, didn't work because bootloader locked
Kept on trying the unlocker apps, none of them even installed fully (THIS WAS WHEN I WAS STILL ON LOLLIPOP)
Somehow, at some point, I just randomly rebooted and BOOM THERE WAS TWRP (Sorry, I don't remember how exactly I managed that. As far as I remember, I was only using fastboot and nothing else)
Flashed CM 14.1 unofficial, device gave an error message regarding boot.img (something like "could not load boot.img"
Used stock ROM to flash OTA Android 6.1
Now the Asus unlocker app downloads but on reboot it says "error: unlock fail !!!"
Obviously, fastboot is unable to flash a recovery right now. I tried ignoring the error message and rebooting to recovery to stop the device from loading the stock recovery again but the device still loads the stock recovery.
I'm really tired
P.S: NO, there is no Enable OEM option in my Developer Options menu and YES, I have all the drivers necessary.
Did you get anywhere with this? I have a similar problem except that I couldn't flash Android 6.1 because the vendor had flashed WW 5.0.2 on a CN phone without also updating the CN recovery to WW. So the update failed its consistency check.
I've got TWRP on there now, but can't unlock the bootloader in 5.0.2 - I think this is why TWRP can't flash anything. It can't see the update files, won't switch to external SD, etc. .
I also found and tried flashing a WW recovery but that didn't work either. I'm wondering now if I got the 615 software by mistake.
Hello!
I am a new to this forums so bare with me please
i have bricked my phone badly.., i tried to install the ota update for P10 Plus (VKY-L29C432B123) with FlashFire and in the middle of the update the phone went black and my problems began getting worse.
i rebooted the phone and got into Error mode Func No: 11 (recovery image) and Error No: 2 (boot faild in recoveryboot mode!).
so i followed a guide and reinstalled twrp to attemp to restore the system somehow, so i kept following the guide and i went into twrp --> wipe --> format data and here my real problems began..
i did many attemps to install any firmware both stock and roms but i got into system mount problem and i can't do anything to transfer files to system i have tried adb but it can't find my device, tried adb sideloaded doesn't work eaither.
so i am stuck in no where..
the phone and frp are unlocked.
but i have missed to enable USB debugg mod
so now i wonder if there is any solution for me in this case?
greatly thankfull if anyone can help me with this big mess.
Try this https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108/page47
gm007 said:
Try this https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108/page47
Click to expand...
Click to collapse
Thanks i had already checked that thread.
i solved the problem by restoring the stock recovery and used eRecovery and funkyhuawei to download firmware and it just went perfectly.
forati89 said:
Thanks i had already checked that thread.
i solved the problem by restoring the stock recovery and used eRecovery and funkyhuawei to download firmware and it just went perfectly.
Click to expand...
Click to collapse
You can use that HWOTA method to recovery FullOTA rom no need to use FunkyHuawei.
forati89 said:
Hello!
I am a new to this forums so bare with me please
i have bricked my phone badly.., i tried to install the ota update for P10 Plus (VKY-L29C432B123) with FlashFire and in the middle of the update the phone went black and my problems began getting worse.
i rebooted the phone and got into Error mode Func No: 11 (recovery image) and Error No: 2 (boot faild in recoveryboot mode!).
so i followed a guide and reinstalled twrp to attemp to restore the system somehow, so i kept following the guide and i went into twrp --> wipe --> format data and here my real problems began..
i did many attemps to install any firmware both stock and roms but i got into system mount problem and i can't do anything to transfer files to system i have tried adb but it can't find my device, tried adb sideloaded doesn't work eaither.
so i am stuck in no where..
the phone and frp are unlocked.
but i have missed to enable USB debugg mod
so now i wonder if there is any solution for me in this case?
greatly thankfull if anyone can help me with this big mess.
Click to expand...
Click to collapse
could you tell me how did you get rid of this error message? im not able to boot into the bootloader, or not completely because the device is not recognized in fastboot.. everytime i turn it off, it turns automatically on and end in, it looks like the bootloader, but with that two error messages, so im not able to do anything..
m_adnan said:
could you tell me how did you get rid of this error message? im not able to boot into the bootloader, or not completely because the device is not recognized in fastboot.. everytime i turn it off, it turns automatically on and end in, it looks like the bootloader, but with that two error messages, so im not able to do anything..
Click to expand...
Click to collapse
To boot into bootloader mode you have to plug the usb and hold volume down while booting.
gm007 said:
To boot into bootloader mode you have to plug the usb and hold volume down while booting.
Click to expand...
Click to collapse
i try that so many times.. but it doesn't work.. as soon as the phone has power, im not able to turn it off.. it start automatically again, and i can press what ever i want, vol down power (with/without usb), vol up power, it always ends in the same:
ERROR MODE
Attention!
Please update system again
Error!
Func NO: 11 (recovery image)
Error NO: 2 (load failed!)
m_adnan said:
i try that so many times.. but it doesn't work.. as soon as the phone has power, im not able to turn it off.. it start automatically again, and i can press what ever i want, vol down power (with/without usb), vol up power, it always ends in the same:
ERROR MODE
Attention!
Please update system again
Error!
Func NO: 11 (recovery image)
Error NO: 2 (load failed!)
Click to expand...
Click to collapse
That's a big problem if you can't access fastboot or erecovery.
Seems you messed up the 2 recoveries.
gm007 said:
That's a big problem if you can't access fastboot or erecovery.
Seems you messed up the 2 recoveries.
Click to expand...
Click to collapse
yes it looks like.. i mean, it wouldn't be a problem to flash recovery again, but i can't get the device to boot into the bootoader so i can work with fastboot..
m_adnan said:
yes it looks like.. i mean, it wouldn't be a problem to flash recovery again, but i can't get the device to boot into the bootoader so i can work with fastboot..
Click to expand...
Click to collapse
Maybe you still have twrp installed?
Volume up + power without connecting usb.
gm007 said:
Maybe you still have twrp installed?
Volume up + power without connecting usb.
Click to expand...
Click to collapse
already tried, but without success.. it always end in that error mode..
forati89 said:
Thanks i had already checked that thread.
i solved the problem by restoring the stock recovery and used eRecovery and funkyhuawei to download firmware and it just went perfectly.
Click to expand...
Click to collapse
how you managed to restore stock recovery? with frp only reading is allowed in fastboot i thought?
same probs here with my p10 vtr-l09 but cant get to one of the recoverys .. how can i tell the frp lock that everything is fine with my fastboot commands?
Sent from my HUAWEI HUAWEI GRA-L09 using XDA Labs
hi, did you manage to solve this problem?
My device was using Oxygen OS Pie official version OTA 43 and the I got the notification for OTA 46 update.
Having an unlocked bootloader and TWRP codeworkx recovery 3.2.3-0, I removed the compatiblity.zip from the OTA, like the other times I did, and tried to flash it, which resulted into a failure. But after rebooting to bootloader and flashing the original oneplus recovery image, I tried to flash the zip again. Which also failed. I have no root, or modifications done to the system. However upon reboot I got the unlocked bootloader warning but nothing else showed up. I couldn't access the recovery nor the bootloader. Fastboot or ADB was unable to detect any device. So I was stuck with a Hard Brick.
After that I downloaded cheeseburger_23_O.13_170803 MsmDownloadTool 4.0 from the unbrick thread and followed the instructions. It completed successfully and I have stock Oneplus 5 on Oxygen OS 4.5.8 and Android 7.1.1 however system update was available to Oxygen OS 5.1.4 and I tried to install it, which failed. I unlocked the bootloader, installed twrp official 3.2.3 and tried again, which also failed with E3005: exit code 7
I tried flashing codeworkx recovery but it results into a black screen at the recovery and a continuous blue light at the LED — like when it was when Hard bricked. I don't understand what to do anymore. Also Bootloader has changed:
Product Name: QC_reference_Phone
Variant : MSM UFS
Bootloader Version: (it is blank)
Baseband Version: (also blank)
Serial Number: (present, same as what it used to be)
Secure Boot: yes
Device State : Unlocked
Did I miss something while Unbricking?
EDIT:
I don't know if something was wrong with my bootloader or unbricking, but I fixed the issue by using an updated version of unbrick tool from: Here
Some information is till missing from the bootloader screen ie. baseband version and bootloader version, but I could update to latest OTA at least.
Kj1594 said:
My device was using Oxygen OS Pie official version OTA 43 and the I got the notification for OTA 46 update.
Having an unlocked bootloader and TWRP codeworkx recovery 3.2.3-0, I removed the compatiblity.zip from the OTA, like the other times I did, and tried to flash it, which resulted into a failure. But after rebooting to bootloader and flashing the original oneplus recovery image, I tried to flash the zip again. Which also failed. I have no root, or modifications done to the system. However upon reboot I got the unlocked bootloader warning but nothing else showed up. I couldn't access the recovery nor the bootloader. Fastboot or ADB was unable to detect any device. So I was stuck with a Hard Brick.
After that I downloaded cheeseburger_23_O.13_170803 MsmDownloadTool 4.0 from the unbrick thread and followed the instructions. It completed successfully and I have stock Oneplus 5 on Oxygen OS 4.5.8 and Android 7.1.1 however system update was available to Oxygen OS 5.1.4 and I tried to install it, which failed. I unlocked the bootloader, installed twrp official 3.2.3 and tried again, which also failed with E3005: exit code 7
I tried flashing codeworkx recovery but it results into a black screen at the recovery and a continuous blue light at the LED — like when it was when Hard bricked. I don't understand what to do anymore. Also Bootloader has changed:
Product Name: QC_reference_Phone
Variant : MSM UFS
Bootloader Version: (it is blank)
Baseband Version: (also blank)
Serial Number: (present, same as what it used to be)
Secure Boot: yes
Device State : Unlocked
Did I miss something while Unbricking?
EDIT:
I don't know if something was wrong with my bootloader or unbricking, but I fixed the issue by using an updated version of unbrick tool from: Here
Some information is till missing from the bootloader screen ie. baseband version and bootloader version, but I could update to latest OTA at least.
Click to expand...
Click to collapse
try a different recovery like "Oreo" and if doesn't help then use unbrick tool
Himanshu.Shukla said:
try a different recovery like "Oreo" and if doesn't help then use unbrick tool
Click to expand...
Click to collapse
I did try to install codeworkx twrp recovery, for the Oreo build but it was giving me a hard brick, ie. A black screen and a blue LED when trying to boot to recovery. But as I said, using Unbrick tool v4.0.8 I was able to restore to Oxygen Os 5.1.7 and then everything worked fine.
I am just unsure why it didn't work with Oxygen Os 4.5.8
I mean, with a locked bootloader and a freshly installed OS, you should be able to get OTA updates, right? But the system update was failing. So maybe there was something wrong with the partitions? I don't know. The bootloader in the older Unbrick tool was different than stock. Maybe that was a fault, well, I'll never know. But all I'm saying is, newer Unbrick Tool worked wonders for me.
I had NOKIA 5 with latest pie update installed
I wanted to flash nokoa 6 ta-1021 rom in it
(I have also successfully installed ta-1000 CN rom in it)
But this this after flashing any older ota update (Dec.2017) I tried to flash with NOST
Although I have unlocked bootloader
But NOST or OST didn't flash and gave an error
Now NOST give me a message that my device is D1C and I am going to flash PLE so confirm it and all data will be erased
Now I confirmed it and it gave me a error of low battery voltage
Now I just boot the phone in recovery mode and power it off so that the phone can get charged
But now it's showing QHSB_BULK in PC
But I just launched NOST and hold the power button
Now my phone is in download mode(thanks to NOST)
BUT the problem is that PC is showing adb interface when the 0hone is in download mode and only adb commands are working
So I typed adb reboot recovery
So I booted in recovery successfully
Now from here I again went in bootloader mode
Now I tried to flash Nokia 5 (ND1) Firmware ,But NOST OR OST both gave an error
I tried ta-1000CN Firmware it also gave an error
Then I tried to flash PLE firmware which I was trying to flash before the phone went in qhsb bulk mode
Now same thing happened when I tried to flash ta-1000 CN firmware
1st-the phone went in qhsb bulk mode because I power off the phone after getting an error
2nd-then using NOST I booted my phone in download mode
Then NOST could only flash ta-1000 model ROMs
So what is it.WHY DOES NOST CAN ONLY FLASH THOSE ROMS WHICH BRICKED MY PHONE A MINUTE EARLY??
AND NOT THE STOCK ONE??
and one thing now I can changed it to Nokia 5 by just flashing any Nokia 5 ota update through applying upadte from sdcard which I downloaded from xda
And now my phone doesn't show POWER BY ANDROID logo while booting
It only shows NOKIA logo
And it doesn't show battery charging icon when the phone is switched off
Other things are working fine(TWRP,magisk)
Except fingerprint data which get lost after flashing any module .
Please read it I know it's very lengthy but suggest me what should I do
Thanks
I had NOKIA 5 with latest pie update installed
I wanted to flash nokoa 6 ta-1021 rom in it
(I have also successfully installed ta-1000 CN rom in it)
But this this after flashing any older ota update (Dec.2017) I tried to flash with NOST
Although I have unlocked bootloader
But NOST or OST didn't flash and gave an error
Now NOST give me a message that my device is D1C and I am going to flash PLE so confirm it and all data will be erased
Now I confirmed it and it gave me a error of low battery voltage
Now I just boot the phone in recovery mode and power it off so that the phone can get charged
But now it's showing QHSB_BULK in PC
But I just launched NOST and hold the power button
Now my phone is in download mode(thanks to NOST)
BUT the problem is that PC is showing adb interface when the 0hone is in download mode and only adb commands are working
So I typed adb reboot recovery
So I booted in recovery successfully
Now from here I again went in bootloader mode
Now I tried to flash Nokia 5 (ND1) Firmware ,But NOST OR OST both gave an error
I tried ta-1000CN Firmware it also gave an error
Then I tried to flash PLE firmware which I was trying to flash before the phone went in qhsb bulk mode
Now same thing happened when I tried to flash ta-1000 CN firmware
1st-the phone went in qhsb bulk mode because I power off the phone after getting an error
2nd-then using NOST I booted my phone in download mode
Then NOST could only flash ta-1000 model ROMs
So what is it.WHY DOES NOST CAN ONLY FLASH THOSE ROMS WHICH BRICKED MY PHONE A MINUTE EARLY??
AND NOT THE STOCK ONE??
and one thing now I can changed it to Nokia 5 by just flashing any Nokia 5 ota update through applying upadte from sdcard which I downloaded from xda
And now my phone doesn't show POWER BY ANDROID logo while booting
It only shows NOKIA logo
And it doesn't show battery charging icon when the phone is switched off
Other things are working fine(TWRP,magisk)
Except fingerprint data which get lost after flashing any module .
Please read it I know it's very lengthy but suggest me what should I do
Thanks
Can you share guide of install nokia 6 ta1021 rom on nokia 5 running android pie
Jitender Baloda said:
Can you share guide of install nokia 6 ta1021 rom on nokia 5 running android pie
Click to expand...
Click to collapse
Mandatory ---Unlocked Bootloader
1st -download any monthly ota update of Nokia 6
Flash it ,it will be aborted
2nd -download Nokia 6 pie ota update from Nokia 6 forum
Flash it
(Both ota updates should be placed on external sdcard)
If this doesnt work then
Flash your phone with Nokia 6 fastboot firmware provided by hikari calyx
It will be done
If it gives an error then boot your phone to recovery
Shutdown from recovery
Now imp.thing is that your phone may be hard bricked at this time
So pc will show it as qhsb_usb bulk
Don't panic
Just open Nost or ost
And press power button
Your phone would boot into download mode
Now you can flash it with ta-1021
Give me your telegram profile name i need to talk on this