Develop Bugs

[Q] Invisible apps?

Hey guys,
I have a MetroPCS-HTC-Wildfire-S-CDMA-A510c-PG763, it is rooted with S-OFF and unlocked.
I wanted to start messing around with Cyanogenmod and Clockworkmod and just wanted to start messing with stuff in general, but I've come across a few problems. With the help of you guys (and girls!) here, and on YouTube, I have worked most of those things out.
However, the time has come again for me to ask for help.
Not knowing any better, I wound up putting Clockwordmod Recovery 5.0.2.6 on my phone, and I have tried a few ROMS...99% didn't work.
What did work was the "marvelUSc_metroPCS_1-1_030712.zip" rom which I believe is fairly stock.
What did NOT work was:
MIUIv4-marvelc-2.8.10-deodex.zip
cm-10-20121220-NIGHTLY-wingray.zip
cm-9.1.0-CRYPTOMILK-ALPHA9-marvelc.zip
cm-9.0.0-RC2-CRYPTOMILK-ALPHA7-marvelc.zip
cm-9.0.0-RC2-CRYPTOMILK-ALPHA6-marvelc.zip
cm-9.0.0-RC1-CRYPTOMILK-ALPHA5-marvelc.zip
All of these came up with (mostly) the same error, which was :
"Installing update...
assert failed: getprop ("ro.product.device") == "marvelc" I I getprop ("ro.build.product") == "marvelc"
E: Error in /sdcard/cm-9.0.0-RC2-CRYPTOMILK-ALPHA7-marvelc.zip
(Status 7)
Installation aborted." ... or some such nonsense.
Basically the same error message, with all of the above ROMs. I believe I read somewhere that I might need to update my CWM anyway? Is THAT what is causing this?
How would I go about updating my Clockworkmod 5.0.2.6?
What is the latest release for CDMA Wildfire S A510c?
Link?
Is there another way to fix this?
I read somewhere something about Odin? Like its another ROM manager or something that would fix this?
See, it's not just the fact that I can't get these ROMs to work for me. As if THAT weren't enough, the one ROM that I mentioned earlier DOES work, sorta.
I would download a file manager from Google Play, I believe I downloaded Quickoffice as well as OI File Manager, as well as Astro File Manager.
Ok, I downloaded them, and, according to the same screen where you download them, after you download and install it, that screen then says installed"...know what I'm talking about? But when you go look in the apps, it isn't there. No idea if there in my phone or not, or if I even really DID download them.......or even where they would be......I have no way to manage files on my phone...unless...
Using Firefox or Internet Explorer on my PC, I can basically use THOSE as file managers, just type into the address bar something like C:\phone\xxx.txt and it comes up....can I do this with the browser in my phone? I wouldn't know what path to type. I tried \sdcard\ and it didn't work.
If anyone out there can help me with ANY of this, I would be greatly obliged.
Thanks in advance,
alphataxicab
ps. I do read the forums and try researching first, but many times, someone has the exact problem *I* do, but with a different phone, so...I'm afraid I might make my problems worse, lol.
By the way, other than what I described here, the phone itself seems to work, phone-call-wise.

steve6770 said:
Hey guys,
I have a MetroPCS-HTC-Wildfire-S-CDMA-A510c-PG763, it is rooted with S-OFF and unlocked.
I wanted to start messing around with Cyanogenmod and Clockworkmod and just wanted to start messing with stuff in general, but I've come across a few problems. With the help of you guys (and girls!) here, and on YouTube, I have worked most of those things out.
However, the time has come again for me to ask for help.
Not knowing any better, I wound up putting Clockwordmod Recovery 5.0.2.6 on my phone, and I have tried a few ROMS...99% didn't work.
What did work was the "marvelUSc_metroPCS_1-1_030712.zip" rom which I believe is fairly stock.
What did NOT work was:
MIUIv4-marvelc-2.8.10-deodex.zip
cm-10-20121220-NIGHTLY-wingray.zip
cm-9.1.0-CRYPTOMILK-ALPHA9-marvelc.zip
cm-9.0.0-RC2-CRYPTOMILK-ALPHA7-marvelc.zip
cm-9.0.0-RC2-CRYPTOMILK-ALPHA6-marvelc.zip
cm-9.0.0-RC1-CRYPTOMILK-ALPHA5-marvelc.zip
All of these came up with (mostly) the same error, which was :
"Installing update...
assert failed: getprop ("ro.product.device") == "marvelc" I I getprop ("ro.build.product") == "marvelc"
E: Error in /sdcard/cm-9.0.0-RC2-CRYPTOMILK-ALPHA7-marvelc.zip
(Status 7)
Installation aborted." ... or some such nonsense.
Basically the same error message, with all of the above ROMs. I believe I read somewhere that I might need to update my CWM anyway? Is THAT what is causing this?
How would I go about updating my Clockworkmod 5.0.2.6?
What is the latest release for CDMA Wildfire S A510c?
Link?
Is there another way to fix this?
I read somewhere something about Odin? Like its another ROM manager or something that would fix this?
See, it's not just the fact that I can't get these ROMs to work for me. As if THAT weren't enough, the one ROM that I mentioned earlier DOES work, sorta.
I would download a file manager from Google Play, I believe I downloaded Quickoffice as well as OI File Manager, as well as Astro File Manager.
Ok, I downloaded them, and, according to the same screen where you download them, after you download and install it, that screen then says installed"...know what I'm talking about? But when you go look in the apps, it isn't there. No idea if there in my phone or not, or if I even really DID download them.......or even where they would be......I have no way to manage files on my phone...unless...
Using Firefox or Internet Explorer on my PC, I can basically use THOSE as file managers, just type into the address bar something like C:\phone\xxx.txt and it comes up....can I do this with the browser in my phone? I wouldn't know what path to type. I tried \sdcard\ and it didn't work.
If anyone out there can help me with ANY of this, I would be greatly obliged.
Thanks in advance,
alphataxicab
ps. I do read the forums and try researching first, but many times, someone has the exact problem *I* do, but with a different phone, so...I'm afraid I might make my problems worse, lol.
By the way, other than what I described here, the phone itself seems to work, phone-call-wise.
Click to expand...
Click to collapse
OK I shall do my best to help first off I am unsure if standard gsm roms will work on a cdma device as they require different kernels for the radios. So you had best be sure that the roms you are trying to flash are definitely for the marvelc.
Edit: secondly are you sure that you have a marvelc recovery installed and not the standard marvel? As I think that would not flash a marvelc rom if it believes the device is a gsm phone.
Thirdly if you are having an issue with apps not appearing then look into your settings/apps and see if they are there. If they are not then they are not installed. But you can get a apk file of es plorer (I think that's its name) and use adb to push the app into the phone with adb push *apkname.apk > /data/app I believe. But best read up on that as I am unsure of that command.
Its good to see that people are doing there research before asking stuff, but unfortunately cdma devices tend to be left behind from a development perspective as they require different kernels and works to make them run, and finding a rom that can do both in one zip file is rare....
Edit: herehttp://cm9-wildfire-s.googlecode.com/files/PG76IMG-cwm-6.0.0.3-UNOFFICIAL-marvelc.zip is a download link to the most up to date cwm for the marvelc I could find with Google . Rename it to pj76img.zip and place it on the sdcard like you did to s-off. Then allow it to flash. Reboot when asked And battery pull when you get to the boot animation. Take the sdcard out, then boot to hboot, then select recovery, then re-insert the sdcard

Nabi 2 Keyboard problem

I followed a utube instruction to route Nabi 2 however I ran into a problem with keyboard, the error message that came up is: "Unfortunately, Android keyboard has stopped". I could not enter any text. At this point I was in child mode and could not get access to Mommy mode to allow me to change settings. I decided to do a factory reset thinking it would clear keyboard error...it didn't. When you do a factory reset it brings you to set-up screen that needs text entry which I cant do. I've been advised to return it to stock but when I try run the return to stock zip file (filed is called fuhu_nabi2_back_to_stock_from_scratch) via SD card it comes up with this message:
-- Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted
Any help with this would be appreciated.
Thanks
Virgil

vpporter said:
I followed a utube instruction to route Nabi 2 however I ran into a problem with keyboard, the error message that came up is: "Unfortunately, Android keyboard has stopped". I could not enter any text. At this point I was in child mode and could not get access to Mommy mode to allow me to change settings. I decided to do a factory reset thinking it would clear keyboard error...it didn't. When you do a factory reset it brings you to set-up screen that needs text entry which I cant do. I've been advised to return it to stock but when I try run the return to stock zip file (filed is called fuhu_nabi2_back_to_stock_from_scratch) via SD card it comes up with this message:
-- Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted
Any help with this would be appreciated.
Thanks
Virgil
Click to expand...
Click to collapse
Not sure which technique you used to root. Did you also install the Google play store? If so, it sounds like you installed the wrong gapps.
I would boot to twrp and install the 1011 gapps.
Sent from my One X using xda app-developers app

NABI 2 Keyboard Problem
GuyIncognito721 said:
Not sure which technique you used to root. Did you also install the Google play store? If so, it sounds like you installed the wrong gapps.
I would boot to twrp and install the 1011 gapps.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Hi There,
Unfortunately I can only get to the Nabi Set-up screen. I can't get to the TWRP screen. I can't enable developers options (USB Debugging) as I cant get into the device (This I think is the biggest problem as I cant see the NABI through PDA net and can run any recovery apps from SD as developer option is not enabled). I seem to be stuck in a loop and not sure where to go from here!
Any help or thoughts much appreciated.
Thanks
Virgil

vpporter said:
Hi There,
Unfortunately I can only get to the Nabi Set-up screen. I can't get to the TWRP screen. I can't enable developers options (USB Debugging) as I cant get into the device (This I think is the biggest problem as I cant see the NABI through PDA net and can run any recovery apps from SD as developer option is not enabled). I seem to be stuck in a loop and not sure where to go from here!
Any help or thoughts much appreciated.
Thanks
Virgil
Click to expand...
Click to collapse
Turn off the device. Power on the device by holding the power and volume up. At the option menu press volume down to get to recovery kernel and press volume up. This will get you to twrp.
Sent from my One X using xda app-developers app

GuyIncognito721 said:
Turn off the device. Power on the device by holding the power and volume up. At the option menu press volume down to get to recovery kernel and press volume up. This will get you to twrp.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Hi,
Thanks for that. I now have access to TWRP and though I would be OK. However when I try to install GAPPs or a Keyboard zip file it continuallys comes up with this error:
E: Unable to mount '/data' (tw_mount)
E: failed to mount /data (Invalid argument)
E: failed to mount /data (Invalid argument)
Any thoughts on this one? It seems to be related to SD card but I have tried a couple to no avail. Can the tablet reject SD cards?
THanks again for your help.
Virgil

vpporter said:
Hi,
Thanks for that. I now have access to TWRP and though I would be OK. However when I try to install GAPPs or a Keyboard zip file it continuallys comes up with this error:
E: Unable to mount '/data' (tw_mount)
E: failed to mount /data (Invalid argument)
E: failed to mount /data (Invalid argument)
Any thoughts on this one? It seems to be related to SD card but I have tried a couple to no avail. Can the tablet reject SD cards?
THanks again for your help.
Virgil
Click to expand...
Click to collapse
have you tried going into the MOUNT sub-menu and trying to mount the data partition?
Sent from my One X using xda app-developers app

GuyIncognito721 said:
have you tried going into the MOUNT sub-menu and trying to mount the data partition?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Hi There,
That seemed to work and I now have GAPPS installed and the keyboard working. Unfortunately the only problem remaining is that Wi-Fi is not working. It previously seen my Wi-Fi connection point and now it will not turn on i.e. I try to switch on Wi-Fi but it keeps going back to the Off position? Very strange. I'm on Android 4.0.4 and have tried the change in Mammy and Daddy mode! I appreciate your help with this and don't want to take up your time so I may post this issue under a new heading.
Thanks again for all your help and giving me the solution.
V

vpporter said:
Hi There,
That seemed to work and I now have GAPPS installed and the keyboard working. Unfortunately the only problem remaining is that Wi-Fi is not working. It previously seen my Wi-Fi connection point and now it will not turn on i.e. I try to switch on Wi-Fi but it keeps going back to the Off position? Very strange. I'm on Android 4.0.4 and have tried the change in Mammy and Daddy mode! I appreciate your help with this and don't want to take up your time so I may post this issue under a new heading.
Thanks again for all your help and giving me the solution.
V
Click to expand...
Click to collapse
Hope you updated the tablet software to 1.9.37 before you did everything or you will be starting over from scratch
Sent from my cm_tenderloin using xda app-developers app

When I first rooted mine, probably some time in late Feb the consensus seemed to be to install the latest OTA software upgrade before rooting in order to avoid WiFi problems. I did this and I have not had WiFi problems. Just recently there has been yet another software and interestingly the bullet point summary of what has changed claims fixes for WiFi issues.
To install the upgrade from the rooted state you need to:
* Use the TWRP recovery to restore the backup you took when rooting to return the main OS to stock.
* Use adb fastboot flash to restore the original recovery.
* Boot normally, connect to WiFi, parent mode, settings/about/update and download/install the update.
[The OTA update works by downloading a file which is then installed by the stock recovery in a reboot cycle.]
* Use adb fastboot flash to flash TWRP recovery.
* Use TWRP recovery to backup the latest stock, install root.zip and gapps.zip.
There is more than one version of TWRP and I found the older one worked for me and the newer one had touch screen problems but you may find otherwise. The various versions are discussed here: http://forum.xda-developers.com/showthread.php?t=2074501

HELP
GuyIncognito721 said:
Hope you updated the tablet software to 1.9.37 before you did everything or you will be starting over from scratch
Sent from my cm_tenderloin using xda app-developers app
Click to expand...
Click to collapse
I see you helped this other person and hope you can me too. I like they did, followed the youtube video on how to root and install google play. It worked great when I did this last year on my kids nabi. I tried to do it again this year with a friends and kinda fell into a hole. My keyboard stopped work as well. I went back and tried to fix it by putting the gapps 1011. Well I didnt delete the old one (didnt know how) and now I cant get into TWRP. I have tried getting the recovery kernal and now when I push vol + it starts to load then gives me the dead android guy. Any suggestions on how to fix this. I sure hope so. Thanks

vpporter said:
I followed a utube instruction to route Nabi 2 however I ran into a problem with keyboard, the error message that came up is: "Unfortunately, Android keyboard has stopped". I could not enter any text. At this point I was in child mode and could not get access to Mommy mode to allow me to change settings. I decided to do a factory reset thinking it would clear keyboard error...it didn't. When you do a factory reset it brings you to set-up screen that needs text entry which I cant do. I've been advised to return it to stock but when I try run the return to stock zip file (filed is called fuhu_nabi2_back_to_stock_from_scratch) via SD card it comes up with this message:
-- Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted
Any help with this would be appreciated.
Thanks
Virgil
Click to expand...
Click to collapse
Uncheck signature enforcement or whatever it's called in TWRP?

Rooted Nabi JR with wrong Root
I have been working on my step-sons nabi for a week now. I rooted three Tabeos fine but then i thought i could do the Nabi JR and it would go perfect...i was wrong. I accidently rooted it with the same package for the Tabeo and now when i boot it up the keyboard forces close and i cant do anything. I can not get to daddy mode, can not usb debug. there is no TPK or whatever installed to boot with. Im at a loss, all i can do is load from usb in the stock bootload menu but i cant seem to get it to work. I need help please...i voided the warranty and now he has no nabi! this is also the Nick JR version of the Nabi, i cant be sure what else is in it considering im stuck at the enter daddy password and no keyboad...

d.marie.1490 said:
I have been working on my step-sons nabi for a week now. I rooted three Tabeos fine but then i thought i could do the Nabi JR and it would go perfect...i was wrong. I accidently rooted it with the same package for the Tabeo and now when i boot it up the keyboard forces close and i cant do anything. I can not get to daddy mode, can not usb debug. there is no TPK or whatever installed to boot with. Im at a loss, all i can do is load from usb in the stock bootload menu but i cant seem to get it to work. I need help please...i voided the warranty and now he has no nabi! this is also the Nick JR version of the Nabi, i cant be sure what else is in it considering im stuck at the enter daddy password and no keyboad...
Click to expand...
Click to collapse
Which Nabi JR? There are 2 versions. 4GB with tegra 2, or 16GB with tegra 3. Makes a difference in how we can help you. Probably need to put TWRP on device and restore a stock ROM. Then use TWRP to root it.

are the ROMs out there? I didn't see anything on the wiki page
http://forum.xda-developers.com/wiki/Fuhu_nabi_Jr
I have to admit though, I don't follow the Jr very much, so for all I know the ROMs are all over the place.

need to fix nabi JR
how can i get twrp without entering debug mode..i cant even get into the nabi to get debug on...i can only access bootloader
aicjofs said:
Which Nabi JR? There are 2 versions. 4GB with tegra 2, or 16GB with tegra 3. Makes a difference in how we can help you. Probably need to put TWRP on device and restore a stock ROM. Then use TWRP to root it.
Click to expand...
Click to collapse

2girlzdad said:
are the ROMs out there? I didn't see anything on the wiki page
http://forum.xda-developers.com/wiki/Fuhu_nabi_Jr
I have to admit though, I don't follow the Jr very much, so for all I know the ROMs are all over the place.
Click to expand...
Click to collapse
I think the 16GB tegra 3 is posted. Maybe the TWRP thread? Can't remember. Mr. Karz usually helps people that need the Nabi JR 4GB tegra 2. I think I have both ROM's but they aren't my creation and I don't have the devices to test so I don't post them.
d.marie.1490 said:
how can i get twrp without entering debug mode..i cant even get into the nabi to get debug on...i can only access bootloader
Click to expand...
Click to collapse
You would use fastboot to flash TWRP from the bootloader. That's why I asked which Nabi you have. 2 different TWRP versions, and the tegra3 version has a locked bootloader, so you have to wipe the device to unlock the bootloader to install TWRP.

break it down for me
can you break that down on how i do that. i deleted everything out of it its in stock but keyboard does not work to access anything, i know its still rooted but i dont know how to fix it.
aicjofs said:
I think the 16GB tegra 3 is posted. Maybe the TWRP thread? Can't remember. Mr. Karz usually helps people that need the Nabi JR 4GB tegra 2. I think I have both ROM's but they aren't my creation and I don't have the devices to test so I don't post them.
You would use fastboot to flash TWRP from the bootloader. That's why I asked which Nabi you have. 2 different TWRP versions, and the tegra3 version has a locked bootloader, so you have to wipe the device to unlock the bootloader to install TWRP.
Click to expand...
Click to collapse

Hey guys, this is my last attempt to fix my sons nabi. It has the same issues as the original poster. I basically cant get anything to work on it.
GuyIncognito721 said:
Turn off the device. Power on the device by holding the power and volume up. At the option menu press volume down to get to recovery kernel and press volume up. This will get you to twrp.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
When I follow these steps it goes to the android with the red exclamation point. I can't access the Nabi with my laptop. only a sd card. Is there anything I can do to save this thing? Thanks to anyone with advice and sorry for the thread necro but it was relevant.

nitetimemc said:
Hey guys, this is my last attempt to fix my sons nabi. It has the same issues as the original poster. I basically cant get anything to work on it.
When I follow these steps it goes to the android with the red exclamation point. I can't access the Nabi with my laptop. only a sd card. Is there anything I can do to save this thing? Thanks to anyone with advice and sorry for the thread necro but it was relevant.
Click to expand...
Click to collapse
What version of the Nabi software were you on? Was the tablet stock or had you rooted it, gapps, etc? Can you boot Android but just the keyboard doesn't work? Or are there more issues besides the keyboard. Are your just trying to fix the one problem or are you trying to wipe the device and start fresh?
Likely you will need to get TWRP on the tablet, or at least be able to boot to TWRP. Answer those questions and I can have a better idea of what we can do.

aicjofs said:
What version of the Nabi software were you on? Was the tablet stock or had you rooted it, gapps, etc? Can you boot Android but just the keyboard doesn't work? Or are there more issues besides the keyboard. Are your just trying to fix the one problem or are you trying to wipe the device and start fresh?
Likely you will need to get TWRP on the tablet, or at least be able to boot to TWRP. Answer those questions and I can have a better idea of what we can do.
Click to expand...
Click to collapse
The Nabi wouldn't take the latest update and it was apparently rooted to gain access to the google play store. It now appears the OS and everything else has been erased. I told my wife I would take a look at it and I immediately regret that decision, this is beyond my scope.
The only thing i have been able to access is the android screen which gives me access to the sd card. My laptop does not recognize it. I found this thread after a lot of searching and reading, some of the nabi threads are insanely long, and when I googled 'signature verification failed' to see if I could find someone stuck at the same point I am,
"I've been advised to return it to stock but when I try run the return to stock zip file (filed is called fuhu_nabi2_back_to_stock_from_scratch) via SD card it comes up with this message:
-- Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted
Any help with this would be appreciated.
Thanks"
Everything I have tried to run from the sd has returned this message. There's no keyboard, there's only the android screen. Anything else I try to do just freezes it. I was hoping to get it back to stock and let it update itself. So I guess the first thing I need to do I figure out how to get twrp on it.

[Q] OTA 1.40.841.8 Fail - Stock Phone

Hi all,
I know new users can be annoying, I'll try not to be. I've searched but haven't found anything relevant to a non-rooted, stock phone so here goes. I bought an M9 when they came out, has been great so far, don't care about the camera as it's fine and I don't buy phones for cameras, I buy cameras for that strangely. Either way I have tried to update to the OTA 1.40.841.8 software but it keeps failing. It downloads the half gig package fine, then reboots, then comes up with the installing bar and every time it gets to roughly 25% it fails and goes to the System Recovery screen saying something about "Package expects build fingerprint of ******* or *******; this device has ****different one*** then it says; Error in @/cache/recovery/block.map (Status 7) - Installation aborted.
Is anyone able to assist? This phone is 100% stock, no modding. Also the HTC website says you can update via sync manager so I tried that as a second choice and it doesn't prompt me about a software update.
Any assistance is appreciated.

OneForAllM9 said:
Hi all,
I know new users can be annoying, I'll try not to be. I've searched but haven't found anything relevant to a non-rooted, stock phone so here goes. I bought an M9 when they came out, has been great so far, don't care about the camera as it's fine and I don't buy phones for cameras, I buy cameras for that strangely. Either way I have tried to update to the OTA 1.40.841.8 software but it keeps failing. It downloads the half gig package fine, then reboots, then comes up with the installing bar and every time it gets to roughly 25% it fails and goes to the System Recovery screen saying something about "Package expects build fingerprint of ******* or *******; this device has ****different one*** then it says; Error in @/cache/recovery/block.map (Status 7) - Installation aborted.
Is anyone able to assist? This phone is 100% stock, no modding. Also the HTC website says you can update via sync manager so I tried that as a second choice and it doesn't prompt me about a software update.
Any assistance is appreciated.
Click to expand...
Click to collapse
Welcome! ?
If it really is all stock it should take the ota perfect...
My advice is to take it to a htc service center and let them update your phone.
Usually only having non stock system or something like that would cause ota to fail.
Since this is not the case....take it to htc.
Sent from my HTC One M9 using XDA Free mobile app

dannylow79 said:
Welcome!
If it really is all stock it should take the ota perfect...
My advice is to take it to a htc service center and let them update your phone.
Usually only having non stock system or something like that would cause ota to fail.
Since this is not the case....take it to htc.
Sent from my HTC One M9 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah i've updated it before with no issue, and i updated my old M7 heaps of times, never had one issue, pretty annoying.

how to fix The dead android bot with error when enter recovery?

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.

5.1.1 OTA update not working

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.