Ok guys I managed to identify a file in /root/cache that was downloaded when downloading the firmware straight from the tablet. The file is named "dlpkgfile" and its about 230Mbs, hopefully this can help some ppl. I don't recommend you use this file if you aren't a dev, since I don't know if it can do something bad to your tablet. I have no knowledge of this type of thing, just trying to give a helping hand....
Anyways I uploaded it to my dropbox, so please only devs download it for now I don't want to get a lot of traffic in my dropbox and be shutdown or something lol
My dropbox public link was taken down due to excessive traffic, there are a couple of mirrors around the thread.
I hope someone can verify this soon. I would love to be able to update since my Tablet failed the update :/
Isn't there a way to DL into my own dropbox from yours? That should (at least in my mind) not count as downloads right?
Either way I'm waiting for someone much braver than I to grab this and explain how to flash it. By that time I'm sure it'll be rehosted somewhere else
Just wait till it gets posted on Asus's site, that's what I'll be doing...
Sent from my Transformer Pad TF300T using xda app-developers app
Pretty sure you can just rename it to *.zip and flash it through the recovery.
All the files from the folder patch need to lose their .p suffix and go in /system before you flash it.
need the doctors around
sparky28000 said:
Pretty sure you can just rename it to *.zip and flash it through the recovery.
All the files from the folder patch need to lose their .p suffix and go in /system before you flash it.
Click to expand...
Click to collapse
did that and it did open in 7zip
kindrudekid said:
did that and it did open in 7zip
Click to expand...
Click to collapse
You flashed it?
Sent from my ADR6425LVW using Tapatalk 2
aostl said:
You flashed it?
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
It looks like it's the update file
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Just wondering if this method: http://forum.xda-developers.com/showthread.php?t=1668173 would still work to root.
Looks like an update.zip package with a blob inside. Should be recovery flashable...
Still recommend flashing over the latest ICS US base.
it does not flash you get status error 7
Probably just a buildprop error. What ROM did you try flashing from?
tysj said:
Probably just a buildprop error. What ROM did you try flashing from?
Click to expand...
Click to collapse
stock
This should help ppl force the update coming from US firmware I think: http://forum.xda-developers.com/showthread.php?t=1803090
You need almost an intact /system to flash this.
assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "asus/US_epad/EeePad:4.0.3/IML74K/US_epad-9.4.3.30-20120604:user/release-keys" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "asus/US_epad/EeePad:4.1.1/JRO03C/US_epad-10.4.2.9-20120809:user/release-keys");
assert(getprop("ro.product.device") == "EeePad" ||
getprop("ro.build.product") == "EeePad");
Click to expand...
Click to collapse
This is a diff patch update.zip.
Whatever you do DO NOT flash the blob from the dlpkgfile on a WW tf300. This will leave you with an us bootloader and for some reason I can't seem boot into the recovery after flashing. And I cannot flash any blob because it says the blob has an invalid signature.
Pretty much stuck here right now... I think I'll have to wait until jb is on the asus website.
How did you flash the blob alone?
Which firmware did you come from?
xaueious said:
How did you flash the blob alone?
Which firmware did you come from?
Click to expand...
Click to collapse
Flashed the blob via fastboot (fastboot -i 0x0B05 flash boot blob) I didn't think it would flash a whole new bootloader. And I came from WW 9.4.3.30. I can't reflash the old bootloader because fastboot doesn't want to actually flash it even though it says everything went okay.
sparky28000 said:
Flashed the blob via fastboot I didn't think it would flash a whole new bootloader. And I came from WW 9.4.3.30.
Click to expand...
Click to collapse
Well I think I'll be fine. I converted my WW to US 9.4.3.30 and am now flashing the dlpkgfile using the method I linked to.
I am not bootloader unlocked.
Quick glance at update-script seems to indicate that it shouldn't remove root from a rooted device running 9.4.3.30, but I'm not sure what's in the blob.
xaueious said:
Well I think I'll be fine. I converted my WW to US 9.4.3.30 and am now flashing the dlpkgfile using the method I linked to.
I am not bootloader unlocked.
Click to expand...
Click to collapse
I hope so.
---------- Post added at 08:45 PM ---------- Previous post was at 08:43 PM ----------
xaueious said:
Well I think I'll be fine. I converted my WW to US 9.4.3.30 and am now flashing the dlpkgfile using the method I linked to.
I am not bootloader unlocked.
Quick glance at update-script seems to indicate that it shouldn't remove root from a rooted device running 9.4.3.30, but I'm not sure what's in the blob.
Click to expand...
Click to collapse
The blob contains a boot.img, recovery.img and bootloader.img.
I already have an US bootloader. I think converting from WW to US did that.
The update.zip does not change /system/bin/su
Related
After doing some reading I found a command to extract the radio file from our phones and crypticsorr0w ended up being our guinea pig and it got him his CKB2 Radio back.
It is now tested and I've inserted it into a cwm file that I took from paulobrien so credit goes to him for that. But it's been tested and it works but you're responsible for what you flash, if something happens don't blame me.
MD5 Sum for this file is: 4e926fdf96a2350c85604b1a00009d
CraneGuy said:
First thing I want to say is this is untested, I did this tonight after my son went to bed and haven't had time to test it. After doing some reading I found a command to extract the radio file from our phones.
update : I put the radio.img file into a zip file and I've been told by zephiK that you need to verify it using md5 hash before using to make sure it doesn't brick your device. If you know how to do that then please go right ahead, in the meantime I'm gonna try to get that done.
In the File properties I get
MD5 Sum : 4e926fdf96a2350c85604b1a00009dc5
So if you don't know how to do that I wouldn't recommend it until someone that does either explains to me how to do it or does it.
Click to expand...
Click to collapse
Nice, what was the command?
Just ran md5 on it, matches what you got.
[email protected]*****:~/Documents/Nexus S/test$ md5sum radio.img
4e926fdf96a2350c85604b1a00009dc5 radio.img
I ran the dd if=/dev/mtd/mtd5 of=/sdcard/radio.img count=12583040
in adb shell and it copied it to the root of my sdcard. Now that that matches it should be safe to flash using fastboot with
fastboot flash radio radio.img command.
you check the md5 hash of your download against the original to test that the download isn't corrupt. on linux, you can do this with:
md5sum filename.zip
on windows, i believe there are many freeware md5 sum checkers you can download to check
yeah I just downloaded a md5 sum checker and checked the md5 hash againts the original and they do match. Plus Kryptic checked it with the #'s I gave him so I'm thinking they're good. If someone that knows more on the subject wants to make sure then you're help is more then welcomed.
About md5 hashes, download hashtab (windows) it makes verifying md5,crc32 etc easy!
Sent from my Nexus S using XDA Premium App
Thanks zephiK, that works a lot better then the other program I was using. Again it just confirmed what I found earlier, they're a match so should be good.
zephiK said:
About md5 hashes, download hashtab (windows) it makes verifying md5,crc32 etc easy!
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Sorry new to the Nexus S....
Got a ATT band Nexus S, loaded NScollab and MIUI and neither will keep me connected to the cellular network/3g
I'm assuming its the radio? How do i flash the stock radio you have posted?
beiker44 said:
Sorry new to the Nexus S....
Got a ATT band Nexus S, loaded NScollab and MIUI and neither will keep me connected to the cellular network/3g
I'm assuming its the radio? How do i flash the stock radio you have posted?
Click to expand...
Click to collapse
Did you flash the radio with some other radio? if not, it's the same one your phone came with.
no I just flashed a different rom and I get no service. so need the stock radio I assume
I tried flashing it using fastboot and I get
FAILED (remote: Write Fail)
then I took the file and put it in zip file that contained update script and installed through CWM.
Baseband back to I9020AUCKB2 =>
Thank you again
beiker44 said:
no I just flashed a different rom and I get no service. so need the stock radio I assume
Click to expand...
Click to collapse
The radio will be intact then, no need to flash it.
crypticsorr0w said:
I tried flashing it using fastboot and I get
FAILED (remote: Write Fail)
then I took the file and put it in zip file that contained update script and installed through CWM.
Baseband back to I9020AUCKB2 =>
Thank you again
Click to expand...
Click to collapse
thanks for being the guinea pig!
crypticsorr0w said:
I tried flashing it using fastboot and I get
FAILED (remote: Write Fail)
then I took the file and put it in zip file that contained update script and installed through CWM.
Baseband back to I9020AUCKB2 =>
Thank you again
Click to expand...
Click to collapse
Glad to hear it worked! Now I can edit to say it's tested. So you say it didn't work typing in "fastboot flash radio radio.img" in your android sdk tool folder using adb with your phone in bootloader mode? Just making sure cause it should've worked. oh well just need to make it into a cmw file then and it should be good.
beiker44 said:
no I just flashed a different rom and I get no service. so need the stock radio I assume
Click to expand...
Click to collapse
You get no Service or no 3G?
Glad to hear it worked! Now I can edit to say it's tested. So you say it didn't work typing in "fastboot flash radio radio.img" in your android sdk tool folder using adb with your phone in bootloader mode? Just making sure cause it should've worked. oh well just need to make it into a cmw file then and it should be good.
Click to expand...
Click to collapse
Below are screenshots when trying it in both methods
PS: I used the script from paulobrien XXKB3 zip file http://forum.xda-developers.com/newreply.php?do=postreply&t=1044261
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
crypticsorr0w said:
Below are screenshots when trying it in both methods
PS: I used the script from paulobrien XXKB3 zip file http://forum.xda-developers.com/newreply.php?do=postreply&t=1044261
Click to expand...
Click to collapse
Thanks crypticsorrow, after I read about your problem with fastboot I had to try it and I got the same error so I did the exact same thing you did and by the time I had it posted you said you got it from paulobrien . I tried this cwm file on mine and it said it worked, so it flashed it over my KB2 baseband but still should be good.
Glad we can now flash without worrying too much about losing our baseband.
I tried this cwm file on mine and it said it worked, so it flashed it over my KB2 baseband but still should be good.
Click to expand...
Click to collapse
I am abit confused by what you mean here. I used your radio.img file, i just placed it inside XXKB3-GRI54-radio-nexuss-unsigned.zip from paulobrien post instead of his radio.img. If that is what you did you should not lose your KB2 baseband.
crypticsorr0w said:
I am abit confused by what you mean here. I used your radio.img file, i just placed it inside XXKB3-GRI54-radio-nexuss-unsigned.zip from paulobrien post instead of his radio.img. If that is what you did you should not lose your KB2 baseband.
Click to expand...
Click to collapse
I did the exact same thing you did except I renamed the file to show the correct baseband, I just wanted to see if I'd get any errors from doing it that way and I didn't so shouldn't be a problem.
Ah sorry for misunderstanding that..
Mind if I ask how did you find out which directory has the radio in /dev?
I would like to learn more about dumping to images
on asus page is available new V10.4.2.19 firmware, but without any description, anybody tried this ? is it more laggy than stock V10.4.2.18 ??
Downloading it, some one know if it is WW?
chevy03 said:
on asus page is available new V10.4.2.19 firmware, but without any description, anybody tried this ? is it more laggy than stock V10.4.2.18 ??
Click to expand...
Click to collapse
I will wait until there's more info listed. It doesn't even say what region it's for.
I was wondering if anyone can help me with my query. I recently installed .18. It's rooted and has TWRP recovery. I would like to know the best method for updating to the new firmware. Please let me know if this approach is sound:
Use OTA RootKeeper to disable root access.
Got to recovery and do a factory reset and wipe dalvik cache
Flash the latest update
Restore root with OTA RootKeeper
With this approach, will I still maintain TWRP recovery or will I need to flash it again?
Any help will be much appreciated. Thanks.
Looks like CN version
chevy03 said:
on asus page is available new V10.4.2.19 firmware, but without any description, anybody tried this ? is it more laggy than stock V10.4.2.18 ??
Click to expand...
Click to collapse
Tried downloading it, it starts as "CN_epaduser_10_4_2_19UpdateLauncer.zip".
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Looking at the other files, it seems the update is for Chinese (CN) SKU. So, it is wise not to flash this on other SKUs.
s2_d2 said:
I will wait until there's more info listed. It doesn't even say what region it's for.
I was wondering if anyone can help me with my query. I recently installed .18. It's rooted and has TWRP recovery. I would like to know the best method for updating to the new firmware. Please let me know if this approach is sound:
Use OTA RootKeeper to disable root access.
Got to recovery and do a factory reset and wipe dalvik cache
Flash the latest update
Restore root with OTA RootKeeper
With this approach, will I still maintain TWRP recovery or will I need to flash it again?
Any help will be much appreciated. Thanks.
Click to expand...
Click to collapse
If you have recovery, that means you're unlocked, so you can flash anything. What I do to update is.....
Download the update and put it in /sdcard. Make sure you unzip once to get to the zip within
Reboot to recovery
backup your current ROM with it.
Flash the new update zip with it
After the flash, you lose root and recovery, soooooo
Once done, go flash recovery back on
Flash root back in - there's a superuser zip in the rooting guide in the general section
you're all set. It seems like a pain but always works for me...
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
funnel71 said:
If you have recovery, that means you're unlocked, so you can flash anything. What I do to update is.....
Download the update and put it in /sdcard. Make sure you unzip once to get to the zip within
Reboot to recovery
backup your current ROM with it.
Flash the new update zip with it
After the flash, you lose root and recovery, soooooo
Once done, go flash recovery back on
Flash root back in - there's a superuser zip in the rooting guide in the general section
you're all set. It seems like a pain but always works for me...
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
Many thanks for the feedback and steps.
Yeah, I followed the guide to update and flash from here (excellent guide). Was wondering if flashing the new firmware would completely wipe everything, including the idea of trying to preserve the root functionality using OTE RootKeeper. If it all has to be done again then so be it Plan on using Titanium Backup to back up my apps too. Still learning, though it's a lot of fun and very time consuming.
Cheers.
If you are unlocked with recovery, then you don't need to be concerned with preserving root from ota updates, because this method is not done ota. You lose root after flashing the update because your entire /system partition is overwritten, but you can easily flash root back in after you put your recovery back. Flashing an update like this does not wipe your /data partition, so you keep data apps and their info.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
funnel71 said:
If you are unlocked with recovery, then you don't need to be concerned with preserving root from ota updates, because this method is not done ota. You lose root after flashing the update because your entire /system partition is overwritten, but you can easily flash root back in after you put your recovery back. Flashing an update like this does not wipe your /data partition, so you keep data apps and their info.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
That's good to know, thanks.
ASUS Transformer Pad TF300T Firmware: V10.4.2.19 Only for CN SKU (Android 4.1)
no 4.2, was hoping for it lol
Yep it's out.
For those of you in need to manually update read below.
Download: cm-bacon-d22b777afa-to-0428073396-signed.zip (KTU84P, XNPH30O)
Install: To install the update, flash a custom recovery (TWRP recommended), boot into it, then sideload using adb sideload - if you've ever updated a Nexus device before, then you'll feel right at home, as the steps are exactly the same. TWRP will ask if you want to re-root at the end.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Wtf is this thread....anyways has anyone tried a clean flash yet?
just flashed it. thanks man!
Why can you flash the zip, why do you have to sideload it ?
Mine keeps failing some sort of verification check, on both cm recovery and twrp.
I flashed it through TWRP, NO ISSUES
doalittledanse said:
Mine keeps failing some sort of verification check, on both cm recovery and twrp.
Click to expand...
Click to collapse
Are you sure you're installing with "adb sideload" as instructed? You can't install from the "install" button in TWRP.
clipcarl said:
Are you sure you're installing with "adb sideload" as instructed? You can't install from the "install" button in TWRP.
Click to expand...
Click to collapse
yep. on both the stock cm recovery and twrp i get this error:
Code:
assert failed: apply_patch_check("/system/framework/apache-xml.jar","44e4.........","eab54.........")
If you've flashed any mods or made any changes to the system. It will fail.
Exclusive Member of the OnePlus One Club
If you guys flashed my Smooth Scrolling Mod, flash the revert and then try the OTA
http://forum.xda-developers.com/one...scrolling-mod-mahdi-rom-t2840934/post54762296
Basically when you're on stock ROM and if you did any changes to your /system/ then it will not update because its been modified.
does this include removal of apps ? Mine failed to sideload as well.+
Edit 1: I did do some modding of the build.prop as well this morning.
I had a feeling that the system partition was a problem, so i wiped it and then reflashed the previous build from cyngn.com and the update still fails.
doalittledanse said:
I had a feeling that the system partition was a problem, so i wiped it and then reflashed the previous build from cyngn.com and the update still fails.
Click to expand...
Click to collapse
Same problem here, fails at:
assert failed: apply_patch_check("/system/framework/apache-xml.jar","44e4.........","eab54.........")
Everything is stock, except Recovery. Tried with original recovery and it still fails...
Got mine to update even though the system partition was updated with a modified updater-script.
I will upload the entire zip with the updated script. For those that know what they are doing the updater-script is attached.
Edit 1: Note you do loose root. You have to install supersu again if you did have it previously (if you modified system then you did)
I have a louder sound mod. So basically I have to reflash to pure stock to use this? That sucks.
Sent from my One using xda premium
Anyone tried custom kernels with ota?
Sent from my A0001 using XDA Free mobile app
C-4Nati said:
I have a louder sound mod. So basically I have to reflash to pure stock to use this? That sucks.
Sent from my One using xda premium
Click to expand...
Click to collapse
look at my post.
I guess the update.zip factory image from the official site isn't truly stock. so i went with the nuclear option and just reflashed everything via fastboot. update worked perfectly now haha.
Please go to the thread here to continue the conversation....http://forum.xda-developers.com/oneplus-one/general/cm-11s-30o-ota-slowly-rolling-t2844689
OTA Blur_Version.210.12.40.falcon_umts.Retail.en.GB
** update **
Can confirm this is 5.0.2, provided a screenshot below
Name: Blur_Version.210.12.40.falcon_umts.Retail.en.GB
Size: 365MB
MD-5 = 4F765CABD140ECCA1075BCEA0906BDC1
SHA1 = 05FCB5AB5A0B35CB3C9F62C4760F79FC33408802
Links
Drive = https://drive.google.com/file/d/0Bxgf37IA03s-MTE2S1loYlRaSzA/view?usp=sharing
Mega = https://mega.co.nz/#!tQY1DSBB!QqTw6TnBYg4BkpK-hQ272_g3zt9L_zxsI-WCJfCYZPs
Amazon Cloud Drive (provided by Rendoqoz) = https://www.amazon.co.uk/clouddrive/share/0m0fmO62hNQXeq7tmObqB8lWdAHgl1q3yldg227AGqk
Screenshot of old firmware i'm currently on to left and new 5.0.2 after update on the right
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've uploaded it to Amazon Cloud Drive:
https://www.amazon.co.uk/clouddrive/share/0m0fmO62hNQXeq7tmObqB8lWdAHgl1q3yldg227AGqk
Rendoqoz said:
I've uploaded it to Amazon Cloud Drive:
https://www.amazon.co.uk/clouddrive/share/0m0fmO62hNQXeq7tmObqB8lWdAHgl1q3yldg227AGqk
Click to expand...
Click to collapse
Thanks i downloaded it and confirmed the checksums are the same, updated my post :good:
I captured Blur_Version.210.12.40.falcon_umts.O2SL.en.GB.zip but I cannot upgrade. Do I have to install Stock Firmware-Recovery? Thanks.
I'll mirror it on basketbuild
Fabio, do you have a 4.4.4 gb O2SL stock link? Thanks.
iBART said:
I captured Blur_Version.210.12.40.falcon_umts.O2SL.en.GB.zip but I cannot upgrade. Do I have to install Stock Firmware-Recovery? Thanks.
Click to expand...
Click to collapse
Sorry i dont know, i always just unroot and make sure i'm on stock recovery before updating.
iBART said:
Fabio, do you have a 4.4.4 gb O2SL stock link? Thanks.
Click to expand...
Click to collapse
Nope :/
But i can mirror that version too
Android 5.1 released:
http://officialandroid.blogspot.ro/2015/03/android-51-unwrapping-new-lollipop.html
Eurofighter_ty said:
Android 5.1 released:
http://officialandroid.blogspot.ro/2015/03/android-51-unwrapping-new-lollipop.html
Click to expand...
Click to collapse
Why are you posting that in this thread ?
Just for information nothing more
How do you make games
Mirror for OTA UK
If you like it, hit thanks button
I am running 5.0.1, how do I install this version from the .zip please?
Can't get this to work, i'm trying to install over stock 4.4 KitKat but it's not being very cooperative. When i attempt flashing in TWRP it says 'Error updating execute binary in script' and in stock recovery it just comes up with 'Installation aborted'. Any ideas what i'm doing wrong?
Same here, no success
V3-571G said:
Can't get this to work, i'm trying to install over stock 4.4 KitKat but it's not being very cooperative. When i attempt flashing in TWRP it says 'Error updating execute binary in script' and in stock recovery it just comes up with 'Installation aborted'. Any ideas what i'm doing wrong?
Click to expand...
Click to collapse
I have open bootloader, CWM, and freshly installed untouched 4.4.4.
When installing this zip from CWM i get:
Verifying current system...
"/system/app/3c_main.apk" has unexpected contents.
E: Error in /data/media/0/Blur_version.210.12.40.falcon_umts.Retail.en.GB.zip
(Status 7)
Installation aborted.
Any tips?
Maciejs said:
I have open bootloader, CWM, and freshly installed untouched 4.4.4.
When installing this zip from CWM i get:
Verifying current system...
"/system/app/3c_main.apk" has unexpected contents.
E: Error in /data/media/0/Blur_version.210.12.40.falcon_umts.Retail.en.GB.zip
(Status 7)
Installation aborted.
Any tips?
Click to expand...
Click to collapse
Custom recovery DOES NOT WORK. You need STOCK recovery
AgentChaos said:
Custom recovery DOES NOT WORK. You need STOCK recovery
Click to expand...
Click to collapse
I've tried stock recovery already but it results in an error saying 'Installation aborted', not sure why this is?
iBART said:
I captured Blur_Version.210.12.40.falcon_umts.O2SL.en.GB.zip but I cannot upgrade. Do I have to install Stock Firmware-Recovery? Thanks.
Click to expand...
Click to collapse
Hi Ibart ,maybe you have sim locked firmware ,in fact his firmare is without SL.
V3-571G said:
I've tried stock recovery already but it results in an error saying 'Installation aborted', not sure why this is?
Click to expand...
Click to collapse
have you rooted the device? if the device was rooted, the update will fill, simply unrooting in supersu will not work because supersu adds files to the system folder. the update will only install successfully on a untouched system.
Disclamer: You are doing this at your own risk.
Guide for OTA Updates
Many users asked how to apply OTA with TWRP or Root, so i decided to make full guide for it
before anything when you receive update notification download it but dont install it because you will get error and if you didnt get error you will bootloop
after you download the OTA, use any file manager with root access to copy ota file from /cache
file name will be "dlpkg" copy it to your internal storage and rename it update.zip or simply download it from links that posted in xda after the ota is available
you have to remove any edits youve done to system to update without problems so heres my steps:
1.Full Unroot:
Open SuperSu and go to settings, scroll down you will find Full unroot choose it and wait for it to finish
Screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2.Uninstall Xposed
Go to xposed official thread here and download "xposed-uninstaller-20150831-x86"
then flash it from recovery to Uninstall Xposed
now you have to edit update.zip updater script because with TWRP you will get error
extract it and open updater-script from "META-INF/com/google/android/"
then remove getprop lines it will be from 2nd line to the 5th like this
Code:
getprop("ro.build.fingerprint") == "asus/WW_Z00A/Z00A:5.0/LRX21V/2.20.40.90_20150903_4959_user:user/release-keys" ||
getprop("ro.build.fingerprint") == "asus/WW_Z00A/Z00A:5.0/LRX21V/2.20.40.97_20150917_1572_user:user/release-keys" ||
abort("Package expects build fingerprint of asus/WW_Z00A/Z00A:5.0/LRX21V/2.20.40.90_20150903_4959_user:user/release-keys or asus/WW_Z00A/Z00A:5.0/LRX21V/2.20.40.97_20150917_1572_user:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");
getprop("ro.product.device") == "Z00A" || abort("This package is for \"Z00A\" devices; this is a \"" + getprop("ro.product.device") + "\".");
Remove it and your updater script beginning will be like this
Code:
mount("ext4", "EMMC", "/dev/block/by-name/system", "/system", "max_batch_time=0,commit=1,data=ordered,barrier=1,errors=panic,nodelalloc");
ui_print("Verifying current system...");
now compress update files again to zip and flash it from recovery
One last thing make sure youre using right ota fil or your device will bootloop and you have to flash Full ROM
Guide for Full ROM
With Full ROM you have to only edit updater script and flash the ROM
extract it and open updater-script from "META-INF/com/google/android/"
then remove verify lines it will be from 1st line until "package_extract_file("ifwi.zip", "/tmp/ifwi.zip");" line which is usually 7th line
it will be similar to these
Code:
(!less_than_int(1441255040, getprop("ro.build.date.utc"))) || abort("Can't install this package (四 9月 3 12:37:20 CST 2015) over newer build (" + getprop("ro.build.date") + ").");
ui_print("Device image SKU:");
ui_print(getprop("ro.build.asus.sku"));
ui_print("OTA image SKU: WW");
assert(getprop("ro.build.asus.sku") == "WW");
getprop("ro.product.device") == "Z00A" || abort("This package is for \"Z00A\" devices; this is a \"" + getprop("ro.product.device") + "\".");
your updater script beginning will be like this
Code:
package_extract_file("ifwi.zip", "/tmp/ifwi.zip");
ui_print("Verifing BOM token ...");
flash_bom_token("/tmp/ifwi.zip") || abort("BOM flashing failed");
ui_print("Updating IFWI ...");
flash_ifwi("/tmp/ifwi.zip");
show_progress(0.750000, 0);
now compress ROM files again to zip and flash it from recovery
with PC use Notepad++ to edit updater script
and from mobile use DroidEdit or Turbo Editor
if Stock ROM it looks like it stopped at "Updating IFWI...." check this post
if you guys have any questions feel free to ask
OTA
Full ROM
awesome work, I like to try new roms but always end up going back to stock. this will make it a whole lot easier.
Sent from my ASUS_Z008 using Tapatalk
luisoman2000 said:
awesome work, I like to try new roms but always end up going back to stock. this will make it a whole lot easier.
Sent from my ASUS_Z008 using Tapatalk
Click to expand...
Click to collapse
Edit:tested and working, ifwi flash will take a loooooong time, so wait it out. First boot will also take a while, screen will eventually dim and the phone will vibrate once before booting.
Sent from my ASUS_Z008D using Tapatalk
Hi, i rooted my device with this method:
http://forum.xda-developers.com/showthread.php?p=61523207
And I have newbie question.
How to enter to recovery? Do I need to install TWRP? Or just should press volume at startup screen?
thanks
thank you so much this helped alot in flashing a stock firmware after i bootloader unlocked and just posting my gratitude keep up the good work now i can use custom roms yay
---------- Post added at 06:03 PM ---------- Previous post was at 05:57 PM ----------
luisoman2000 said:
Edit:tested and working, ifwi flash will take a loooooong time, so wait it out. First boot will also take a while, screen will eventually dim and the phone will vibrate once before booting.
phahahaa you wasnt joking longest wait ive had my entire life ohhhh wait its still updating it....... arggghhhhhh as long as it works i dont care
Click to expand...
Click to collapse
Yes
This is what I want.
Great tutorial.
You guys are genius.
I love you.
10 Time thanks
---------- Post added at 05:28 PM ---------- Previous post was at 05:21 PM ----------
squo_85 said:
Hi, i rooted my device with this method:
http://forum.xda-developers.com/showthread.php?p=61523207
And I have newbie question.
How to enter to recovery? Do I need to install TWRP? Or just should press volume at startup screen?
Click to expand...
Click to collapse
Yes
You can flash TWRP.
I mean I need to install TWRP first and than go to there or I already have it using shown rooting method?
squo_85 said:
Hi, i rooted my device with this method:
http://forum.xda-developers.com/showthread.php?p=61523207
And I have newbie question.
How to enter to recovery? Do I need to install TWRP? Or just should press volume at startup screen?
Click to expand...
Click to collapse
Remove root and install ota with stock recovery
squo_85 said:
I mean I need to install TWRP first and than go to there or I already have it using shown rooting method?
Click to expand...
Click to collapse
Not sure about that method but in the asus resource thread root method 3 you can OTA update as long as you have stock recovery and system apps installed and no exposed
I was able to OTA update via method 3 but I didn't have TWRP installed at the time and my stock apps was present. I was rooted and boot loader unlocked
Instructions worked good for me. But a few keys. Keep root until your ready to flash. You need root to edit those files(update) and to save it. I used es file explorer to edit, move and save it
Think this method would be good for people needing to do everything on device, but if you are going to use a pc anyway I suspect it would be quicker and easier to just flash stock recovery, update and then flash twrp again.
The Full ROM method work if I want rollback CM to Stock ROM?
Alex86CT said:
The Full ROM method work if I want rollback CM to Stock ROM?
Click to expand...
Click to collapse
yes it should works fine
followed instruction to flash the update, but it always failed and wouldnt flash. had to flash the full latest rom for my 550 ML to update.
Can anybody make a YouTube tutorial for this?
luisoman2000 said:
followed instruction to flash the update, but it always failed and wouldnt flash. had to flash the full latest rom for my 550 ML to update.
Click to expand...
Click to collapse
error message ?
rblaker said:
Can anybody make a YouTube tutorial for this?
Click to expand...
Click to collapse
OTA
Full ROM
Lol i was just about to make a thread to explain this but you went ahead me
Explained well, @AL_IRAQI
BTW, this can be added and may be usefull for someone...
If somebody removed some apps in system when they will try to apply the OTA it will be bumped an error, so you will also need to delete the apply_patch_check string which controls the signature of every app and odex to see if they got changed...
nilac said:
Lol i was just about to make a thread to explain this but you went ahead me
Explained well, @AL_IRAQI
BTW, this can be added and may be usefull for someone...
If somebody removed some apps in system when they will try to apply the OTA it will be bumped an error, so you will also need to delete the apply_patch_check string which controls the signature of every app and odex to see if they got changed...
Click to expand...
Click to collapse
Thanks buddy
I didn't add because i found many users in other threads know about this trick [emoji16]
But I'll add it in case someone didn't know about it
luisoman2000 said:
followed instruction to flash the update, but it always failed and wouldnt flash. had to flash the full latest rom for my 550 ML to update.
Click to expand...
Click to collapse
Turn Verification off in advanced settings of twrp