Related
hello
i have rooted the device using the "1 CLICK ROOT TOOL" and now i have the dead android bot with error when i enter recovery.
i have tried the "fastboot erase cache" command at fastboot mode but it did not help
is their a way to fix it?
Try pressing Volume + key and Power. Don't hold just press. It might take a few goes to get it right. I had the same problem. That means that the update you have downloaded (saved on your system) fails to install.
hello and thanks
i can enter recovery by pressing the keys. this is not the issue
its just that i want to completely solve the problem
koby058 said:
hello and thanks
i can enter recovery by pressing the keys. this is not the issue
its just that i want to completely solve the problem
Click to expand...
Click to collapse
Awh sorry, I thought you can't get into recovery.
Try sideloading the stock Firmware. Go to official ASUS website and download it from there. It's about 1 GB. On this website you can find instructions on how to do it. http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596 Section 3.2)
After that you can download OTA updates and install them using method described here http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835, "Steps to Apply OTA manually".
OTA can be downloaded from there (look at the later posts for newer OTA) http://forum.xda-developers.com/zenfone2/general/ota-links-stock-rom-t3093999
I had a very similar problem few days ago. That solved it. Had a similar problem a few days ago coz I messed up my build.prop
hello
i have already did a "adb siedeload" for the stock rom downloaded from the asus web site but the issue remain.
also i downloaded the latest ota, and "adb sideloaded" them as well. it worked flawlessly .
but the small thing with the recovery is annoying.
i thinking about looking inside tmp directory and delete something called "last update"
what do you say?
koby058 said:
hello
i have already did a "adb siedeload" for the stock rom downloaded from the asus web site but the issue remain.
also i downloaded the latest ota, and "adb sideloaded" them as well. it worked flawlessly .
but the small thing with the recovery is annoying.
i thinking about looking inside tmp directory and delete something called "last update"
what do you say?
Click to expand...
Click to collapse
You're not understanding because the information he gave you is slightly wrong. When you try to enter stock recovery it will ALWAYS say installing update and pop up an error Android bot. It's not about having some update data somewhere that fails to install properly. It will ALWAYS do that. That's normal.
rlaw said:
You're not understanding because the information he gave you is slightly wrong. When you try to enter stock recovery it will ALWAYS say installing update and pop up an error Android bot. It's not about having some update data somewhere that fails to install properly. It will ALWAYS do that. That's normal.
Click to expand...
Click to collapse
Owh, this is embarrassing. I was playing with it a lot and I was kind of sure that if you have a working installed update, which is the same as a zip of an OTA update you have on an SD card it will skip installing the update and go to recovery without an error, but I was very very wrong. I'm very sorry for missleading you, and I've learned something new. Thank you.
NiKiToS-04 said:
Owh, this is embarrassing. I was playing with it a lot and I was kind of sure that if you have a working installed update, which is the same as a zip of an OTA update you have on an SD card it will skip installing the update and go to recovery without an error, but I was very very wrong. I'm very sorry for missleading you, and I've learned something new. Thank you.
Click to expand...
Click to collapse
No worries, I've made the same mistake before. We've all been there, still learning new things about this phone after months of using it!
ok let me tell why i begin asking about it.
when i just got the phone i update all of the ota updates and after that i rooted it with "1 CLICK ROOT TOOL" .
two days ago i receive tha 2.20.40.58 ota . i downloaded and install but the instalation failed .
so i unroot it with "1 CLICK ROOT TOOL" and then i checked for update . but there was no update.
so i assumed the problem is because of the recovery issue.
the qustion is why i cannot install ota automatically ?
koby058 said:
ok let me tell why i begin asking about it.
when i just got the phone i update all of the ota updates and after that i rooted it with "1 CLICK ROOT TOOL" .
two days ago i receive tha 2.20.40.58 ota . i downloaded and install but the instalation failed .
so i unroot it with "1 CLICK ROOT TOOL" and then i checked for update . but there was no update.
so i assumed the problem is because of the recovery issue.
the qustion is why i cannot install ota automatically ?
Click to expand...
Click to collapse
The 2.20.40.58 OTA was bugged and pulled from release. Just flash the full stock 2.20.40.59 firmware available from ASUS site and stop modifying your phone if you want to remain trouble-free with OTA updates. Or if you choose to continue to root and tinker with your phone accept that some things might get broken.
My phone is running the BOG5 5.0.1 software and it is a retail edition.
I recieved a notification on my device prompting me that a new update is available (finally! 5.1.1!) I tap "download now", the download eventually finishes and it proceeds to install.
My phone boots into recovery, "installing update" and very shortly after I see the droid triage error and below it says "error!" and then my phone reboots. When I unlock my phone it says, "Sorry, there was a problem updating your SAMSUNG SM-N910V. No changes were made."
I looked under software update in settings and it says "software not updated to N910VVRU2BOK3" and the error code is 410.
I also notice that when I go into recovery it says "dm-verity verification failed...."
I looked in Kies to see if the update was available there, and of course it wasn't. And I can't find the ROM anywhere as of yet to flash with ODIN.
I would appreciate all of the help I can get.
Thank you.
traceestarr said:
My phone is running the BOG5 5.0.1 software and it is a retail edition.
I recieved a notification on my device prompting me that a new update is available (finally! 5.1.1!) I tap "download now", the download eventually finishes and it proceeds to install.
My phone boots into recovery, "installing update" and very shortly after I see the droid triage error and below it says "error!" and then my phone reboots. When I unlock my phone it says, "Sorry, there was a problem updating your SAMSUNG SM-N910V. No changes were made."
I looked under software update in settings and it says "software not updated to N910VVRU2BOK3" and the error code is 410.
I also notice that when I go into recovery it says "dm-verity verification failed...."
I looked in Kies to see if the update was available there, and of course it wasn't. And I can't find the ROM anywhere as of yet to flash with ODIN.
I would appreciate all of the help I can get.
Thank you.
Click to expand...
Click to collapse
I'm having the exact same issue and symptoms, have you made any progress with this? If I find a solution I'll share here too. I've tried Kies and VZW Software Upgrade Assistant, neither finds the update, but I can get it on my retail VZ Note 4, just won't successfully install.
Keiller said:
I'm having the exact same issue and symptoms, have you made any progress with this? If I find a solution I'll share here too. I've tried Kies and VZW Software Upgrade Assistant, neither finds the update, but I can get it on my retail VZ Note 4, just won't successfully install.
Click to expand...
Click to collapse
Thank you for your feedback. I wonder if it has to do with a corrupt software build on our devices. I ordered my phone in November of last year and it came with BOG5 on it. I'm going to see about flashing stock BOG5 completely fresh on the phone and see if that corrects the issue.
traceestarr said:
Thank you for your feedback. I wonder if it has to do with a corrupt software build on our devices. I ordered my phone in November of last year and it came with BOG5 on it. I'm going to see about flashing stock BOG5 completely fresh on the phone and see if that corrects the issue.
Click to expand...
Click to collapse
I have similar issue ,i don't have a update yet showing on my device so i await for it to show up. Please let us know if flashing it makes the difference.
traceestarr said:
Thank you for your feedback. I wonder if it has to do with a corrupt software build on our devices. I ordered my phone in November of last year and it came with BOG5 on it. I'm going to see about flashing stock BOG5 completely fresh on the phone and see if that corrects the issue.
Click to expand...
Click to collapse
Sounds like something worth trying, I'll watch for an update on how it goes for you. Thanks!
I have found a solution (albeit requires a full wipe, which is worth having 5.1.1 for me)
Firstly, I attempted flashing the "stock restore" file in odin and resulted in an error, I then tried the full firmware instead (mind you for BOG5, if you're having problems on your current version I'd suggest using your current build) with success, proceed with a data wipe in recovery and noticed that the "dm-verity verification failed...." message is now gone and now that bottom area of the screen has information about applying Multi-CSC.
Restart the phone, set up as normal and go straight for the software update. My phone downloaded and installed the update perfectly! For safety just boot into recovery and do a full wipe again, and there you have it!
The stock firmwares for RETAIL SM-N910V are here: http://forum.xda-developers.com/not...mware-firmware-kernel-modem-recovery-t2942937
traceestarr said:
I have found a solution (albeit requires a full wipe, which is worth having 5.1.1 for me)
Firstly, I attempted flashing the "stock restore" file in odin and resulted in an error, I then tried the full firmware instead (mind you for BOG5, if you're having problems on your current version I'd suggest using your current build) with success, proceed with a data wipe in recovery and noticed that the "dm-verity verification failed...." message is now gone and now that bottom area of the screen has information about applying Multi-CSC.
Restart the phone, set up as normal and go straight for the software update. My phone downloaded and installed the update perfectly! For safety just boot into recovery and do a full wipe again, and there you have it!
The stock firmwares for RETAIL SM-N910V are here: http://forum.xda-developers.com/not...mware-firmware-kernel-modem-recovery-t2942937
Click to expand...
Click to collapse
Thank you for reporting back with what worked for you. I've tried following the same steps you took, but after flashing the full BOG5 firmware and doing a data wipe and then doing basic setup on my phone, the OTA is still failing, Error Code: 404. I'll try again, but so far no success. Still stuck on the buggy 5.0.1, the version where you can't flash back to 4.4.4....
Keiller said:
Thank you for reporting back with what worked for you. I've tried following the same steps you took, but after flashing the full BOG5 firmware and doing a data wipe and then doing basic setup on my phone, the OTA is still failing, Error Code: 404. I'll try again, but so far no success. Still stuck on the buggy 5.0.1, the version where you can't flash back to 4.4.4....
Click to expand...
Click to collapse
I am sorry to hear that this didn't work for you. But it appears we're both getting different error codes. Does your recovery display issues with dm-verity failing? I think this was part of my problem in the first place.
traceestarr said:
I am sorry to hear that this didn't work for you. But it appears we're both getting different error codes. Does your recovery display issues with dm-verity failing? I think this was part of my problem in the first place.
Click to expand...
Click to collapse
You're right, I thought I had seen that message earlier in the week while trying to get the OTA for 5.1.1 to work, but I didn't write it down. Your description of symptoms matched mine so well I figured it had to be the same issue or something so similar that running through the same process would work for me too.
I may take the phone into Verizon to show them the update fail and see if they are willing to do anything for me....
Glad you got yours up and running, but I am just a little bit jealous
Keiller said:
You're right, I thought I had seen that message earlier in the week while trying to get the OTA for 5.1.1 to work, but I didn't write it down. Your description of symptoms matched mine so well I figured it had to be the same issue or something so similar that running through the same process would work for me too.
I may take the phone into Verizon to show them the update fail and see if they are willing to do anything for me....
Glad you got yours up and running, but I am just a little bit jealous
Click to expand...
Click to collapse
I've found that most times the OTA update fails prior to rebooting to install the update and I get the 404 error I reported earlier. However, when it does make it to the point of doing the OTA update after reboot, after that fails, I get the same 410 error you reported, see attached, and I also the dm-verity fail message in recovery. Then after using Odin to install BOG5, the verity fail disappears, replaced by a Multi-CSC message, I do a complete data wipe/factory reset, set up my basic google account and try the OTA, which fails every time. But once the dm-verity fail is gone, I can try doing an update from external storage, which I've tried with the BOK3 5.1.1 zip file posted here: http://forum.xda-developers.com/not...id-5-1-1-according-to-website-t3290683/page20 However, this still fails to load.
At this point I'm pretty convinced that I some other issue with my phone. I found elsewhere that someone was able to take their phone into Best Buy and have them flash the 5.1.1 update for them via Kies. That is probably my next step.
But I wanted to share what I've tried in case anyone else is experiencing the same dead end or in the off chance that someone has found a solution.
Sure would love to see the full 5.1.1 BOK3 tar.md5 sometime before Marshmallow hits, pretty sure using Odin to install the update that way would work....
traceestarr said:
I am sorry to hear that this didn't work for you. But it appears we're both getting different error codes. Does your recovery display issues with dm-verity failing? I think this was part of my problem in the first place.
Click to expand...
Click to collapse
The full OTA for 5.1.1 was posted and I was able to update using Odin, following the instructions on this post: http://forum.xda-developers.com/not...nt/firmware-safe-upgrade-to-lollipop-t3313224
Just wanted to update this post with the solution which finally worked for me.
Hello together,
I get some problems with installing the new firmware update (M2-A01wV100R001C100B006). The update does not work with the update tool on the air (OTA). Every time I tried it, my tablet showed "Software install failed - Failed to check the update files. Please download the package again".
First try to fix was to unpack the UPDATE.APP from the 226MB zip-file (/sdcard/HwOUC/...B006.zip) into "dload"-directory (not /dload_ota) and start a local update with the Huawei update tool. --> First time it looked good and showed "update successfully installed", but in the truth it was failed and does not work this way.
Working update process:
- Download the full firmware from Huawei (not the update package) Official Huawei Rom Thread
- Unpack and copy the "dload"-folder with the 2.9GiB UPDATE.APP file in it to your sdcard or internal storage
- Open update tool on the tablet and install from local
(The software shows you will loose all your data, but on my tablet nothing was lost and I only had to root it again.)
Greetz,
CM
Hello,
You write that you have root device?
If you root the device and using the TWRP recovery?
Thx for reply.
Martin
and what is the question?
How install full firmware from Huawei, if I have TWRP recovery?
I don't know but normally flash it via Huawei Update Tool and after it, flash TWRP again if needed!
Huawei update tool is software for Windows? Any link please?
LTE ROM update?
Hi All, my M2 LTE has never received a single OTA update, plus can't seem to find anywhere an official ROM for LTE in Huawei site.
I see there is a Wifi ROM available, but no LTE!?
Can someone shed some light please?
Hello everyone, I decided to root my phone today. First I enabled OEM unlock and then installed TWRP, no problems with that. Then I tried to install CF autoroot through recovery and everything seemed fine. When I tried to boot up my phone it said something like integrity check failed and I had to do a factory reset to be able to even start the phone. I did not do that but tried to install official samsung oreo firmware through odin but it won't install, just fails. Then i got other error message saying "an error occured while updating the device software. Use the Emergency recovery function in the Smart Switch PC software". The only thing I can do now is enter download mode and nothing else but odin does not let me flash anything. I'm desperate here so any suggestion would be great. Model is SM A-320FL btw. Sorry for my english and lengthy post
Jura_11 said:
Hello everyone, I decided to root my phone today. First I enabled OEM unlock and then installed TWRP, no problems with that. Then I tried to install CF autoroot through recovery and everything seemed fine. When I tried to boot up my phone it said something like integrity check failed and I had to do a factory reset to be able to even start the phone. I did not do that but tried to install official samsung oreo firmware through odin but it won't install, just fails. Then i got other error message saying "an error occured while updating the device software. Use the Emergency recovery function in the Smart Switch PC software". The only thing I can do now is enter download mode and nothing else but odin does not let me flash anything. I'm desperate here so any suggestion would be great. Model is SM A-320FL btw. Sorry for my english and lengthy post
Click to expand...
Click to collapse
What kind of error do you get in Odin?
Is it the one that says something like "SW Rev. check fail"?
If so than for me it worked to flash the bootloader and modem of Oreo and the after that i reinstalled the OS without any problems.
First it was just a red fail for BL, CSC and those other things and later it just won't even start. When I try to install TWRP it goes to half and stays there. Thanks for the suggestion though.
Jura_11 said:
First it was just a red fail for BL, CSC and those other things and later it just won't even start. When I try to install TWRP it goes to half and stays there. Thanks for the suggestion though.
Click to expand...
Click to collapse
Was your device from a carrier, if so, try to flash the firmware that your device came with. If you can't solve this, PM me, so that we can try to resolve this on Telegram, Discord etc. :highfive:
MartinYTCZ said:
Was your device from a carrier, if so, try to flash the firmware that your device came with. If you can't solve this, PM me, so that we can try to resolve this on Telegram, Discord etc. :highfive:
Click to expand...
Click to collapse
Thank you for the reply, I don't think it was from carrier, when I tried to flash firmware I downloaded latest firmware from my current carrier so I think that shouldn't be a problem. I'll contact you tomorrow because i'm just too tired now. And update, I can flash TWRP now if that is of any help.
It is solved now, thanks everyone for your help
Jura_11 said:
It is solved now, thanks everyone for your help
Click to expand...
Click to collapse
Hi. Glad to see you got this sorted, but it may be useful for other users to see what you did to resolve this.
Yes, how did you solved that.
Looking at two A320F I found one difference:
One has AP SWREV B:2 K:0 S:0
the other one (that makes trouble): AP SWREV B:3 K:1 S:1
What exactly does it mean.
Flashing with Odin gave me erros (on device, Odin just say "failed") depending on flashing BL (SW Rev Check failed )Bootlader Device: 3, binary: 2 , while flashing AP gives Kernel Rev check fail.
So, how to go on? I was able to flash TWRP, but not Stock (neither an old 6.0 nor 8.0).
Ok, solved it. Flashing stock will probably only work to same or newer versions, not for downgrade (at least not without any special tricks that I don't know).
After downloading the latest stock FW , odin passed.
Now I still have the problem, that I can't transfer data partion from one A3 to another one.
https://forum.xda-developers.com/showpost.php?p=78062070&postcount=71
My first error was that I downloaded wrong firmware for my phone and because of that odin gave me errors. Second error was that I tried to wipe data through advanced wipe, but I needed to format it by pressing format data button. After doing that I was able to flash official stock ROM, install TWRP and root my phone. User MartinYTCZ helped me greatly with this, big thanks to him again. :victory:
starbright_ said:
Ok, solved it. Flashing stock will probably only work to same or newer versions, not for downgrade (at least not without any special tricks that I don't know).
After downloading the latest stock FW , odin passed.
Now I still have the problem, that I can't transfer data partion from one A3 to another one.
https://forum.xda-developers.com/showpost.php?p=78062070&postcount=71
Click to expand...
Click to collapse
Can't you backup your internal storage on PC or SD card, contacts, messages, phone calls, settings on samsung account and apps and data with titanium backup? When I flashed stock ROM I lost all data from my phone so be careful with that.
So, following this guide i tried to root my samsung galaxy a5 2017. Everything was okay, i flashed the custom recovery and tried to install magisk through twrp as said there but... the dreaded 'only official release binaries are allowed to be flashed' red message in black background popped up in my screen. Now i can only boot into download mode, and install official binaries.
So I'm trying to do now, i downloaded the last carrierless spanish sotck room for my mobille. Well, it turns out that it gives an error 'kernel rev check failed. Mobile:9 Binaries:8' aaand i don't know what to do now?
Also, I didn't know Samsung had come to a new way of blocking custom binaries in 8.0.0, so, is there any way to circumvent this? I found this page but I don't really know if that's what I'm looking for
carlosmedia said:
So, following this guide i tried to root my samsung galaxy a5 2017. Everything was okay, i flashed the custom recovery and tried to install magisk through twrp as said there but... the dreaded 'only official release binaries are allowed to be flashed' red message in black background popped up in my screen. Now i can only boot into download mode, and install official binaries.
So I'm trying to do now, i downloaded the last carrierless spanish sotck room for my mobille. Well, it turns out that it gives an error 'kernel rev check failed. Mobile:9 Binaries:8' aaand i don't know what to do now?
Also, I didn't know Samsung had come to a new way of blocking custom binaries in 8.0.0, so, is there any way to circumvent this? I found this page but I don't really know if that's what I'm looking for
Click to expand...
Click to collapse
Apparently I was NOT using the last firmware available, even though i checked it like 4 times, that was the problem. It is fixed.