Database Users

[Q] Still need help with Dexter Mod

I have tried everything in my toolkit to get the Dexter Mod installed on my A7...the new firmware update worked fine, but when i follow the steps for the Dexter mod..in recovery mode, i get a message that says:
Install from sdcard
Finding update package
Opening update package
E:Can't open /sdcard/update.zip
(no such file or directory)
Installation aborted
Formatting MISC...
I even downloaded the Dexter Mod from my computer at work yesterday and brought it home to try to no avail...
Why isn't this working?
Is there another place I can download the Dexter Mod 11 from to get a different file..
How can I be sure I am in the root directory of the sdcard?
I realize i am brand new at this, and i am willing to do the work, but really I am disappointed the the mod will not install..
also, I noticed that when I ran the firmware update, a few programs that I had downloaded were erased...how do i back program up on the A7 so they are not lost

Another question
Is in necessary to install the previos Dexter mods before the 11?

No, you don't need to download the previous ROMs first.
Your download may be corrupted. That happens a lot with large files.
This one is over 90MB.
Getright is a free download manager that helps with this issue.
Get it here:
http://www.getright.com/
Try that and let us know if it works for you.

I installed update.zip from the root directory of sd card (nothing on sd card except Update.zip), from within settings> about> update firmware.
It will go through the steps and boot loop.
U then hold off for 15 secs, then turn on for 3secs, let go and hold till it says > loading boot kernel ( recovery mode), then wipe cache and settings.
Done!!
Whew.

when renaming the file leave out the zip part. i was having the same problem . if you noticed the elocity update doesnot name the update w/ zip at the end

thank you

Can I do OTA if I rooter my Nexus?

I just got OTA notification, should I install it? I'm rooted and have custom recovery.

If you're running stock 4.2.2 (you didn't flash a custom ROM or applied other system changes), then yes go ahead and install the OTA.
Check this thread for more info.

4.2.2 OTA Failed
Hey
I have a rooted Nexus 4 also. Running mako kernel. I got the 4.3 OTA update. Proceeded to install the update. But the update failed, then directed me to the stock recovery screen with the red warning sign. I rebooted the phone, went to Settings -> System Update, the 4.3 OTA is no longer there, and the phone is still running 4.2.2. What should I do to get 4.3?
I'm a noob.
Thank you for your help.

By "mako kernel" do you mean the stock kernel?
Why did the update fail - did you see the error message?
Since you're rooted, you have the option of re-flashing the OTA update:
1. The update zip should be in system/cache. First copy the zip file into your sdcard (ie the root folder).
2. If you don't have a custom recovery already, I suggest you use one to flash the OTA update. Install GooManager from the Play Store and install recovery. The default recovery is TWRP. Google Youtube for the process if you're not clear.
3. Once you're ready, reboot into TWRP recovery and select the OTA update file which you copied over in step 1. This should update you to 4.3.
4. If flashing this is successful, select the option to wipe dalvik cache, then select reboot device.
5. The phone will boot up and you should now see that you're on 4.3. You can now delete the OTA zip from your root folder.
6. If you want to re-root your phone, here's where TWRP comes in handy again. Download SuperSU from here, and paste it in the same root folder you placed the OTA zip before.
7. Now boot into recovery again, then choose to flash the SuperSU zip file.
8. Reboot phone and check that you have root access.
Good luck.

Settings -> About Phone -> Kernel Version
3.4.0-faux123-mako-custom
[email protected] #141
Sun Jun 23 00:57:50 CDT 2013
Can you please expand on Step 1?
Im not so sure as to what you mean and how to complete that step
Sorry for the trouble
Thanks

I believe that's the faux kernel (not sure if that's the correct name; I don't keep up on kernels). You will need to flash the stock one from Google if you want to apply the 4.3 update.
Search this forum for more info on doing that; I think the thread I linked to earlier should have instructions.
Expanding on step 1:
- When your phone automatically downloads the OTA zip file, it will store it in system/cache. Open a file explorer app (like Solid Explorer), press back a few times, and you should see the "System root" folder. Look for the "cache" folder, and the OTA zip file should be inside.
- Copy this OTA zip file into your "Internal memory" folder. Actually you don't really need to do this step, however it's the easiest folder to select when you go into recovery mode.

I managed to get the 4.3 OTA again
It downloaded and I'm now in the process of installing.
The phone reboots, (bootloader is unlocked), I see Droid, with the stomach open, blue bar right underneath it.(The screen that shows up with all updates)
Now the progress stopped. The blue bar stopped moving. This is the message on screen
Install Untrusted Package?
THIS CAN NOT BE UNDONE.
-No
-No
-No
-No
-No
- Yes - install untrusted zip
-No
-No
*******Go Back *********
When I choose "Yes- install untrusted zip", the installation fails, with the red warning sign and the droid laying on the ground.
Now I'm at the ClockworkMod Recovery v6.0.3.1 screen, given the following options.
- reboot system now
- install zip from sdcard
-install zip from sideload
- wipe data/ factory reset
-wipe cache partition
-backup and restore
-mounts and storage
-advanced
The error message below the droid reads:
ClockworkMod Recovery v6.0.3.1
E: Invalid command argument
Finding update package...
Opening update package...
Verifying update package...
E: failed to verify whole-file signature
E: signature verification failed
Installing update...
Warning: No file_contextsVerifying current system...
assert failed: apply_patch_check("/system/bin/thermald", "94e92fc68071c4f5b131d6b6a634a8e3ecca", "1f2323bbfa00ccb97c4f345e83f908ba61b830df")
E: Error in /cache/ebc8bad23772b5fd6e2907e48b4c74ba0ed58f21.signed-occam-JWR66V-fromJDQ39.ebc8bad2.zip
(Status 7)
Installation aborted.
Any help would be great.
Thanks again. I appreciate it

That message is very similar to mine when I tried to apply the update using my cwm I have my baseband flashed to .33 so I can enable LTE idk if that's the problem causing it
Sent from my Nexus 4 using xda app-developers app

@cliew:
Signature verification check failures tend to happen on CWM, which is another reason why I recommend using TWRP instead.
You can try following step 2 of my initial post and see if that works.
If the update still fails when you use TWRP, that means you've altered some system files that conflict with the OTA. You'll get another error message when that happens, and it should point to whichever file is in conflict.
---------- Post added at 09:35 PM ---------- Previous post was at 09:33 PM ----------
@droidman89:
Yes, I believe if you've flashed different radios, that would most certainly stop the OTA taking. If you haven't already done so, you'll need to re-flash the stock ones in order to update.

I have the OTA file. Assuming that I'm on stock everything but rooted with a custom recovery, will the install still work, or should I reflash stock recovery as well?

@viewfindr
If only your recovery is custom - and no other system files have been modified - then yes, you should be able to take the OTA successfully.

Rooter? Lol just root or rooted. Sure it's a typo.
Sent from my Nexus 4 using xda app-developers app

mlj11 said:
I believe that's the faux kernel (not sure if that's the correct name; I don't keep up on kernels). You will need to flash the stock one from Google if you want to apply the 4.3 update.
Search this forum for more info on doing that; I think the thread I linked to earlier should have instructions.
Expanding on step 1:
- When your phone automatically downloads the OTA zip file, it will store it in system/cache. Open a file explorer app (like Solid Explorer), press back a few times, and you should see the "System root" folder. Look for the "cache" folder, and the OTA zip file should be inside.
- Copy this OTA zip file into your "Internal memory" folder. Actually you don't really need to do this step, however it's the easiest folder to select when you go into recovery mode.
Click to expand...
Click to collapse
Can't seem to locate this file anywhere in those folders. Any suggestions?

inc188 said:
Can't seem to locate this file anywhere in those folders. Any suggestions?
Click to expand...
Click to collapse
It should be in System root / cache. The other stuff in that folder (at least for me) are three folders named backup, lost+found and recovery.
If you can't find it there, it's probably because it's been some time since your OTA arrived. Which means it's now been cleared from cache.
If that's the case don't worry, because it'll come back again. Alternatively you can flash the update manually using the 4.3 image elsewhere in these forums.
------------------
Hit thanks if I helped

[Q] 4.4.3 Manual update - origibal lib files?

I've tried updating my Nexus 4 rooted device via "Nexus Update Checker" app, and when it finished downloading and i pressed "install" the device rebooted and entered CWM, asking me if i want to install. I've pressed "yes", and it gave an error saying there is some "Unexpected Content" in the package. I've searched for it, and found this:
File /system/lib/hw/audio.a2dp.default.so in your device not official. It modify by some app require root permission. Or you install some mod.
In normal method (OTA) or manual install update (sideload). You will found error same this error. Because all method use recovery mode for install update package.
You can fix problem by
1. Flash official ROM.
Or find official file from other device and replace in your device.
2. Update again
Click to expand...
Click to collapse
(sorry, the forum won't let me post the link to the source for some reason)
So, i was wondering - where could i find a download for those original lib files for my device?
My device's android version is currently 4.4.2, updated via OTA before it was rooted.
Thanks for any further help.

Help force Full Update instead of OTA

I just received the information that there is a new OTA update WAS-LX1AC432B184, but it failed to install I think because it want to patch the system, vendor and custom partition instead of adding file. With Firmware Finder I found the full version, is there a way I can force my phone to use the full version and not the OTA to do the update?
Will it delete all of may files?
Thanks

I believe it will wipe your phone so you will lose all data.
To force the update put the 'update.app' file in a folder named 'dload' (if no dload folder just make one) to the root of your sd card.
With the phone dialer type *#*#2846579#*#* and select software upgrade or, turn your phone off and press and hold volume up and down buttons and power on the phone, this will force update.
You could also contact Huawei support (via Hi Care App) who might be able to help you install the failed update.

i received notification for WAS-LX1AC432B185 (i have the 4 GB version)
update failed, because i had TWRP flashed and after reboot it tried to flash the update in TWRP.
so, i flashed stock recovery in fastboot and then the update was succesfull.

[email protected]@[email protected] said:
i received notification for WAS-LX1AC432B185 (i have the 4 GB version)
update failed, because i had TWRP flashed and after reboot it tried to flash the update in TWRP.
so, i flashed stock recovery in fastboot and then the update was succesfull.
Click to expand...
Click to collapse
I tried the same, but it doesn't work. I added the update of some System application inside the System Directory and I think that this is the Problem.
Reading the script for the update/rebrand for Mate9 and P10 I found this command:
$ADB shell "echo --update_package=$TARGET_UPDATE > /cache/recovery/command"
if I download only update.zip from Full-MT through Firmware Finder and copy it for example in /dload (adb push update.zip /dload) and then launch
adb shell " echo /dload/update.zip > /cache/recovery/command"
adb reboot recovery
Will it update my phone without doing a factory reset like if it was an OTA update?
In the update.zip there are the full Version of System, Vendor and Custom Partition instead of only the patch files.
Thanks

I tried but it doesn't work.
I found a tricky solution.
I accepted and download the 3 update files then I don't do immediately the installation, but I substitute in the directory where they where stored (/data/update/HwOUC/serie of number) the update.zip with the full-OTA that I downloaded through FF. I had to change owner, group and SE contest with that of the original file.
After that I tell the system update to perform the update.
The phone rebooted and the update started at end I received an error message, the system rebooted showing the old version B182 but patch updated to 1st September.
Immediately I receive a notification of a system update, but this time the FULL-OTA was proposed I did again the update and this time everything works fine. NOw my Telephone is B184
After that I had to reinstall TWRP and reroot it.
Hope it helps

Kindly provide OTA file WW-14.2016.1804.305

The actual file on the website is corrupted. If someone has working zip file, please upload it. I can not get system update till 309, hence I need to manually download and put it in the root directory. Please note that my device is not rooted. Hence need OTA update file.

​Just directly download the latest zip file (.309 or .311) from Asus website and put it in your root directly. It will update peoperly

yasht011 said:
Just directly download the latest zip file (.309 or .311) from Asus website and put it in your root directly. It will update peoperly
Click to expand...
Click to collapse
Tried with .309. after 20%, phone rebooted and said update failed. .311 is not available in the website.

Jaarit Laal said:
Tried with .309. after 20%, phone rebooted and said update failed. .311 is not available in the website.
Click to expand...
Click to collapse
That's odd. I updated from .252 to .309 directly cuz as you said the file on the website is corrupted.
Anyways, try to wipe the cache partition (Hold power and volume down in power off state and release power when phone vibrates while holding power down. Your phone will boot into fastboot mode. From there select wipe cache partition). After wiping cache try .309 update again by putting the zip file in the root directory and then updating via the notifications.

Will I lose data?

Jaarit Laal said:
Will I lose data?
Click to expand...
Click to collapse
Download below file for v311 update .. Keep it in internal storage ..
WW-15.2016.1805.311
The system will detect it as update file and provide you with option to update firmware.
Your data will be retained.

.A.V.i.n.a.S.h. said:
Download below file for v311 update .. Keep it in internal storage ..
WW-15.2016.1805.311
The system will detect it as update file and provide you with option to update firmware.
Your data will be retained.
Click to expand...
Click to collapse
How did you get this link? In their official website, it is still not updated. https://www.asus.com/in/Phone/ZenFone-Max-Pro-ZB601KL/HelpDesk_BIOS/ .

Jaarit Laal said:
How did you get this link? In their official website, it is still not updated. https://www.asus.com/in/Phone/ZenFone-Max-Pro-ZB601KL/HelpDesk_BIOS/ .
Click to expand...
Click to collapse
It is avaliable but not updated on official site - https://www.asus.com/id/Phone/ZenFone-Max-Pro-ZB602KL/HelpDesk_BIOS/
It is there for ZB602KL and both version use same firmware.
You can clearly see ZB601KL in download link which I provided.

.A.V.i.n.a.S.h. said:
It is avaliable but not updated on official site - https://www.asus.com/id/Phone/ZenFone-Max-Pro-ZB602KL/HelpDesk_BIOS/
It is there for ZB602KL and both version use same firmware.
You can clearly see ZB601KL in download link which I provided.
Click to expand...
Click to collapse
I just downloaded and tried to update it via manual ota. Also cleared cache via recovery. But still after 20% it is getting rebooted and update is failed.

Jaarit Laal said:
I just downloaded and tried to update it via manual ota. Also cleared cache via recovery. But still after 20% it is getting rebooted and update is failed.
Click to expand...
Click to collapse
Thanks. I found out the reason. Google play protect was turned off and luckypatcher was installed. I uninstalled luckypatcher and turned on Google play protect. Then applied the update 311, and it worked. Thanks. Both of you had been of immense help.