Related
Hi everyone,
I calculate a download website n it can be successfully entered:
http://global-download.acer.com/Ste...0&BC=Acer&SC=&LC=en&OS=a09&FS=O02&Category=OS
Note: If u see nothing there, plz reflash a few times.
(updated by 9th Nov)
Some patches added, u guys can check it out. ( I flashed the patch n found nothing changed! seemd just update some built-in softwares )
(updated by 25th Sep)
There'r some new ROMs with clear label added.
Interesting!
The ROMs on that site are:
Acer_AV041_A510_1.072.00_EMEA_CUS1
Acer_AV041_A510_1.073.00_WW_GEN1
Acer_AV041_A510_1.074.00_EMEA_GB
Acer_AV041_A510_1.076.00_EMEA_DE
Acer_AV041_A510_1.076.00_PA_CUS1
Acer_AV041_A510_1.079.00_PA_CA
Acer_AV041_A510_1.084.00_AAP_AU
Acer_AV041_A510_1.090.00_TWN_GEN1
There's a couple new regions there I didn't know existed
NoThrills said:
Interesting!
The ROMs on that site are:
Acer_AV041_A510_1.072.00_EMEA_CUS1
Acer_AV041_A510_1.073.00_WW_GEN1
Acer_AV041_A510_1.074.00_EMEA_GB
Acer_AV041_A510_1.076.00_EMEA_DE
Acer_AV041_A510_1.076.00_PA_CUS1
Acer_AV041_A510_1.079.00_PA_CA
Acer_AV041_A510_1.084.00_AAP_AU
Acer_AV041_A510_1.090.00_TWN_GEN1
There's a couple new regions there I didn't know existed
Click to expand...
Click to collapse
So you downloaded all n checked them one by one? Thx for the instructions.
Can I flash these over CWM ?
picard47 said:
Can I flash these over CWM ?
Click to expand...
Click to collapse
I haven't tested these ROMs yet, my tab is still on the way from service.
You can have a try unless u know what u do.
jokerzlh said:
So you downloaded all n checked them one by one? Thx for the instructions.
Click to expand...
Click to collapse
Yeah, I wanted to know if there was a new build somewhere... Unfortunately not
picard47 said:
Can I flash these over CWM ?
Click to expand...
Click to collapse
Yes, but they will remove your custom recovery and might even lock your bootloader (there are bootloader.blob files, but I don't know what they do).
only 6 are showing now?? im grabbing them all, hoping my region is still one of them!
Hmm that's odd I have a au over and I cannot ota to the newer version listed??
Acer_AV041_A510_1.084.00_AAP_AU
Mine atm is Acer_AV041_A510_1.036.00_AAP_AU
---------- Post added at 04:58 PM ---------- Previous post was at 04:11 PM ----------
malos1984 said:
Hmm that's odd I have a au over and I cannot ota to the newer version listed??
Acer_AV041_A510_1.084.00_AAP_AU
Mine atm is Acer_AV041_A510_1.036.00_AAP_AU
Click to expand...
Click to collapse
If I download to tab and go to built in recovery and load this firmware could it lock or stuff future otas?
You need to scroll down to see the 2 other ones..
Sent from my MB525 using xda app-developers app
malos1984 said:
Hmm that's odd I have a au over and I cannot ota to the newer version listed??
Acer_AV041_A510_1.084.00_AAP_AU
Mine atm is Acer_AV041_A510_1.036.00_AAP_AU
---------- Post added at 04:58 PM ---------- Previous post was at 04:11 PM ----------
If I download to tab and go to built in recovery and load this firmware could it lock or stuff future otas?
Click to expand...
Click to collapse
Yes. This is also important for other users reading this thread: These ROMs are probably beta's, so if you flash this on your tablet you won't get new OTA's. I'm not 100% certain about this, but just in case: Make a backup!!!
OK so its not like Samsung where I can install the firmware and go back.
Btw when I do power and volume I get android guy with red error why is this. I have not rooted nor tried to install kernel/rom before
I was under the hope an official firmware wouldn't void warranty but it looks like it won't do updates without cwm which I'm not comfortable installing at this time
Marmotte51 said:
You need to scroll down to see the 2 other ones..
Sent from my MB525 using xda app-developers app
Click to expand...
Click to collapse
lol, oops, didnt see the scroll bar hidden over there....
Rusty_Gunn said:
lol, oops, didnt see the scroll bar hidden over there....
Click to expand...
Click to collapse
Sent from my A510 using xda app-developers app
malos1984 said:
OK so its not like Samsung where I can install the firmware and go back.
Btw when I do power and volume I get android guy with red error why is this. I have not rooted nor tried to install kernel/rom before
I was under the hope an official firmware wouldn't void warranty but it looks like it won't do updates without cwm which I'm not comfortable installing at this time
Click to expand...
Click to collapse
That's because the Acer recovery does not have a menu or other interface. If you boot into stock recovery, you'll get the 'error android'. If you boot to recovery with a file called 'update.zip' on your SD-card, the stock recovery will flash this update.zip without error.
However, you can only flash official update.zip files with this, no custom ROMs.
NoThrills said:
That's because the Acer recovery does not have a menu or other interface. If you boot into stock recovery, you'll get the 'error android'. If you boot to recovery with a file called 'update.zip' on your SD-card, the stock recovery will flash this update.zip without error.
However, you can only flash official update.zip files with this, no custom ROMs.
Click to expand...
Click to collapse
Oh OK thanks.
Yeah I tried installing that one from SD card it failed at 50%
regarding the update script,
to get these roms to work, the region check needs to be bypassed (after installing a custom rom), can i just comment out the line in question?
assert(getprop("ro.product.name") == "a510_pa_ca");
and to keep cwm recovery, can i just comment out the recovery package extraction?
package_extract_dir("recovery", "/system");
do i need to comment out the bootloader.blob file? some of what i read seems to indicate if i dont comment it out, the bootloader will be locked after flashing.
then rezip, make sure cwm is set to take an unsigned zip, and flash?
for those trying to select the right rom and dont want to download all 8, the correspond regions are as follows (the RV28RCXX begin an excerpt from the file name on the acer site):
Acer_AV041_A510_1.072.00_EMEA_CUS1 --> RV28RC02
Acer_AV041_A510_1.073.00_WW_GEN1 --> RV28RC01
Acer_AV041_A510_1.074.00_EMEA_GB --> RV28RC03
Acer_AV041_A510_1.076.00_EMEA_DE --> RV28RC04
Acer_AV041_A510_1.076.00_PA_CUS1 --> RV28RC04
Acer_AV041_A510_1.079.00_PA_CA --> RV28RC06
Acer_AV041_A510_1.084.00_AAP_AU --> RV28RC08
Acer_AV041_A510_1.090.00_TWN_GEN1 --> RV28RC10
they all have region checks, so if you have installed a custom rom, the acer roms will fail to flash without some additional tweaking. And two regions (RC04) do have the exact same file name, no idea why acer did that.
And for A511 ?
OK so I retried flashing after saving data and it worked this time last time I tried it kept failing at 50%.
No noticeable difference and the stock browser still crashes on me.
Oh well just have to wait for jelly bean update maybe for some noticeable fixes.
Acer_AV041_A510_1.084.00_AAP_AU --> RV28RC08
For any Aussies reading here I have tested a full deplete and had no major issues except the ones I was already getting I.e stock browser crash and occasionally can't wake up the device.
Though this hasn't happened yet I'm assuming it still is there.
FordSierra88 said:
And for A511 ?
Click to expand...
Click to collapse
The website for A511 is almost same,.
But no ROMs available now. I will keep updating.
I've got myself (and my tablet) into a complete mess.
When I got my tablet it was already unlocked and running ICS (I think).
I decided it was time to upgrade to cyanogenmod Kit Kat.
I started with this tutorial: http://wiki.cyanogenmod.org/w/Install_CM_for_tf700t
I flashed the custom recovery : "recovery-jb-644"
I chose "cm-10.2.0-tf700t" as I was nervous about the nightly. Something went wrong.
The tablet started but crashed after a few minutes and rebooted. I added "gapps-jb-20130813-signed" - it was worse - now the keyboard also crashed.
After that, I tried numerous things to recover it.
Now, I cant access it through the fastboot - it gives the serial number but won't push anything or flash anything.
I put the following on an sd card and tried to install from there but I get:
status 7 assert failed: write_raw_image (" /tmp/blob" , "staging )
or any number of similar messages. I tried the solution here: http://forum.xda-developers.com/showthread.php?t=1235724 which worked once but not again.
My current situation:
The picture attached shows the current installation - it will boot - I have no Google Apps - and it crashes within a minute and then reboots.
I'm not a complete newbie, but I cant find a simple explanation of what to do next.
I just want the tablet to work again, I don't care anymore if its Kit Kat, ICS, Jelly Bean or Honeycomb.... I even considered Linux...
Please help.
Apparently you missed the big fat red warning on the tutorial you linked. You need to install a 10.6.1.14.x bootloader.
(And you need to make sure your recovery is compatible with that bootloader, otherwise you risk a hard brick when you wipe data).
fivaics logical
_that said:
Apparently you missed the big fat red warning on the tutorial you linked. You need to install a 10.6.1.14.x bootloader.
(And you need to make sure your recovery is compatible with that bootloader, otherwise you risk a hard brick when you wipe data).
Click to expand...
Click to collapse
OK, so I've downloaded it, but I still can't install it because of the
status 7 assert failed: write_raw_image (" /tmp/blob" , "staging )
How do I get around this?
I attach a copy of the log showing what happens when I try.
ymget said:
OK, so I've downloaded it, but I still can't install it because of the
status 7 assert failed: write_raw_image (" /tmp/blob" , "staging )
How do I get around this?
I attach a copy of the log showing what happens when I try.
Click to expand...
Click to collapse
According to the page you linked, you are supposed to download a blob file and flash it via fastboot:
http://wiki.cyanogenmod.org/w/Install_CM_for_tf700t#Update_Bootloader_To_Compatible_Version
You didn't say yet in which way fastboot didn't work for you.
Hi,
Thank you for replying.
I can't do "fastboot -i 0x0B05 flash staging XX_bootloaderblob"
When I am in the CMD window, I can do fastboot devices and it see's my serial number, but as soon as I want to actually do something, it tells me the device is not available.
The same goes for any adb commands I want to do.
The only way I found of doing it is through the sideload, but now even this doesnt work.
Hi Again,
Your comment gave me an idea - I did the bootloader fastboot through the sideloader - and it worked!!!
I then added the "gapps-jb-20130813-signed" and now it is crashing on the setup wizard.... and the keyboard crashes.
Any ideas?
ymget said:
Hi Again,
Your comment gave me an idea - I did the bootloader fastboot through the sideloader - and it worked!!!
I then added the "gapps-jb-20130813-signed" and now it is crashing on the setup wizard.... and the keyboard crashes.
Any ideas?
Click to expand...
Click to collapse
Did you reboot after flashing the bootloader and before flashing gapps?
berndblb said:
Did you reboot after flashing the bootloader and before flashing gapps?
Click to expand...
Click to collapse
Yes, I had to check to make sure that the new bootloader worked and the tablet was no longer crashing before I installed the gapps.
ymget said:
Yes, I had to check to make sure that the new bootloader worked and the tablet was no longer crashing before I installed the gapps.
Click to expand...
Click to collapse
I really have no idea... I just checked - you did flash the gapps package for CM 10.2 and I assume you also checked the box "verify zip signature" in your recovery before you flashed gapps?
If not, it maybe as simple as a bad download....
berndblb said:
I really have no idea... I just checked - you did flash the gapps package for CM 10.2 and I assume you also checked the box "verify zip signature" in your recovery before you flashed gapps?
If not, it maybe as simple as a bad download....
Click to expand...
Click to collapse
You were right!! I downloaded the gapps again and now I have a perfectly working tablet.
Thank you to everyone who answered me and helped - you guys are amazing!!
ymget said:
You were right!! I downloaded the gapps again and now I have a perfectly working tablet.
Thank you to everyone who answered me and helped - you guys are amazing!!
Click to expand...
Click to collapse
:GOOD: Glad you got it working! BTW, there's a "Thanks" button for a reason
berndblb said:
:GOOD: Glad you got it working! BTW, there's a "Thanks" button for a reason
Click to expand...
Click to collapse
I know there is supposed to be one - I've read about it - but I can't find it anywhere!!!!
Found it!!!
Anybody figure out how to fix this? I can find people having this problem flashing 4.4 but I can't flash anything. I've tried to flash mf1 firmware, a 4.3 carbon nightly, and a 4.3 pac nightly. All with the same results. Here is exactly what I did -
I flashed PhilZ recovery earlier on a earlier version of TWRP.
kept getting a "failed" in PhilZ
Flashed latest TWRP via Odin
Tried flashing the above mentioned zips all with the error message.
Restored my hyper drive rls16 backup (4.1.2)
Installed latest TWRP via goomanager app
Edit : my phone is flashed to PagePlus so I kinda have to be careful I'm afraid of using Odin to go back to stock/rooted but my luck that's what it'll take. When I get home I'm going to try it with a older version of TWRP that's the only other thing I can think to try.
Any suggestions or info is appreciated.
delete
anyone ? please ?
Supposedly the update binary here is generic, you could try replacing the one in the rom zip with it
http://forum.xda-developers.com/showthread.php?t=2492496
Sent from my SCH-I535 using XDA Premium 4 mobile app
I've tried CWM PhilZ and TWRP all latest versions, and still can't get rid of this.
I Cannot install any rom, whatsoever. I did manage to install a MF1 radio zip, but that's it. I can't install 4.3 or even 4.2 ..
I've replaced the update-binary inside the zips, and edited the update-script and removed the stuff used for recognizing the device, still no dice ..
I ended up flashing a full mf1 img via Odin and then used casual to root/unlock/recovery install - and I STILL get the error. Not sure where to go from here. Seems like nobody else is having this problem unless they're not on the latest recovery and trying to flash KitKat.
Thought I'd share the rest of my story ..
edit: I was able to restore a old backup of 1.7 carbon ...lol. better than nothing or a TW rom, that's for sure.
When you replaced the update binary did you get the same error or a different one? Also, have you tried flashing from internal and external SD?
Sent from my SCH-I535 using XDA Premium 4 mobile app
dpeeps74 said:
When you replaced the update binary did you get the same error or a different one? Also, have you tried flashing from internal and external SD?
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sorry I didn't get a notification for this.
I did get the same error. I did get a error 6 once or twice but it was because I edited the update-script file and used word or word pad I downloaded note++ and it stopped and went back to error 7 :banghead:
Sent from my SCH-I535 using Tapatalk
cjmcsw87 said:
Sorry I didn't get a notification for this.
I did get the same error. I did get a error 6 once or twice but it was because I edited the update-script file and used word or word pad I downloaded note++ and it stopped and went back to error 7 :banghead:
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
OK, I have one for you to try, use the original rom zip (don't edit the update-script), when you flash in recovery and it failed, select boot and boot back into recovery, then reflash again. Try it with the latest TWRP 2.6.3.2.
SOLVED ! only took a week ...
I had been using an update-binary file that was posted in a thread.
I took the file from PhilZ recovery ( which I had been able to flash, just nothing else ) and used that one. Imagine that, it worked.
**DUH** :silly:
cjmcsw87 said:
SOLVED ! only took a week ...
I had been using an update-binary file that was posted in a thread.
I took the file from PhilZ recovery ( which I had been able to flash, just nothing else ) and used that one. Imagine that, it worked.
**DUH** :silly:
Click to expand...
Click to collapse
Nice, glad you have a happy ending!!
buhohitr said:
Nice, glad you have a happy ending!!
Click to expand...
Click to collapse
Me too buddy, let me tell ya ..
I appreciate the advice along the way. Thank you.
now I just have to decide if I want carbon or pac as my daily driver for awhile.. Carbon is what i've almost always used after I figured out how bloated and laggy TW is.. Best of all my PagePlus flash is perfectly fine, didn't have to add APN's or mess with anything else to get data to work.
I hope this thread helps somebody else.
I am having the same issue with HTC One.
Could you please let me know how you solved this. Maybe it can help with my device as well. had no luck in our threds..
Thank you
umka83 said:
I am having the same issue with HTC One.
Could you please let me know how you solved this. Maybe it can help with my device as well. had no luck in our threds..
Thank you
Click to expand...
Click to collapse
If you're getting a status 7 error you have to replace the update binary with the latest nightly from cm11 in anything you want to flash. The update binary is universal and will work on anything you want to flash. If it is throwing another error then this won't work.
This will probably only work with cwm or philz.
BadUsername said:
If you're getting a status 7 error you have to replace the update binary with the latest nightly from cm11 in anything you want to flash. The update binary is universal and will work on anything you want to flash. If it is throwing another error then this won't work.
This will probably only work with cwm or philz.
Click to expand...
Click to collapse
Hello, thanks for reply,
1) I am not getting a STATUS 7 error, only this one:
Code:
E: eror eexecuting updater binary in zip /sdcard/zipfilename.zip Error flashing zip /sdcard/zipfilename Updating partition details Failed
Could you please let me know how can I replace the update binary with the latest nightly from cm11? Do you need to open zip from latest Nities and put it into my ZIP?
2) I have tried both cwm or philz and I am getting this error
Code:
this package is for m7wlj devices this is dlx
My device is m7wlj for sure. But somehow recovery thinks it is DLX
THANK YOU
umka83 said:
Hello, thanks for reply,
1) I am not getting a STATUS 7 error, only this one:
Code:
E: eror eexecuting updater binary in zip /sdcard/zipfilename.zip Error flashing zip /sdcard/zipfilename Updating partition details Failed
Could you please let me know how can I replace the update binary with the latest nightly from cm11? Do you need to open zip from latest Nities and put it into my ZIP?
2) I have tried both cwm or philz and I am getting this error
Code:
this package is for m7wlj devices this is dlx
My device is m7wlj for sure. But somehow recovery thinks it is DLX
THANK YOU
Click to expand...
Click to collapse
It's a recovery version problem, so either update your recovery or use an older one until you find something that works.
Problem Solved
umka83 said:
Hello, thanks for reply,
1) I am not getting a STATUS 7 error, only this one:
Code:
E: eror eexecuting updater binary in zip /sdcard/zipfilename.zip Error flashing zip /sdcard/zipfilename Updating partition details Failed
Could you please let me know how can I replace the update binary with the latest nightly from cm11? Do you need to open zip from latest Nities and put it into my ZIP?
2) I have tried both cwm or philz and I am getting this error
Code:
this package is for m7wlj devices this is dlx
My device is m7wlj for sure. But somehow recovery thinks it is DLX
THANK YOU
Click to expand...
Click to collapse
After conducting my own research with this same problem I discovered a much simpler method of correcting the issue. When flashing KK roms with older versions of custom recoveries, the recoveries did not have sufficient instructions to to handle some of the file system changes in KK. I tried replacing the updater binaries from multiple ROMs to no avail. After about 24 hours of trial and error I managed to successfully flash Cyanogenmod cm-11-20140709-NIGHTLY-d801 and GAPPs aokp_gapps-kk-20140517 to my LG G2 D801. All that had to be done is to update TWRP from 2.6.3.2 to version 2.7.1. This version of TWRP had the necessary instructions to support a KK version custom ROM.
Good Job
Sent from my SM-G900F using XDA Free mobile app
Fixed
buhohitr said:
Nice, glad you have a happy ending!!
Click to expand...
Click to collapse
I had same issue, installed newest TWRP. Fixed! Used Odin to install.
I had the same issue as the OP. I was trying to flash a rom from the external SD card. I moved it to the Internal SD and it worked.
J
I'm prompted to install the XNPH38R Incremental with the message "System update is ready"
I tap on Install update, the phone then does it's thing, reboots and shows the splash screen logo a few seconds, then the recovery comes up and the text scrolls at lightning speed (a second or so) then the phone powers up in full and is ready for use.
When I go to my homescreen the prompt is there again for me to upgrade with the "System update is ready" message.
As such the update doesn't apply successfully. No error messages at all.
Phone is stock ROM (version 11.0-XNPH33R), only thing I did extra was to unlock the bootloader using OnePlus One Toolbox v2 (64 GB). This was done in order for me to root it. Oh, I also installed PhilZ Recovery using this same toolbox.
Any ideas why this happens?
...or suggestions as to how I can do the update?
PS, I saw that there's another tread (http://forum.xda-developers.com/oneplus-one/help/apply-ota-stock-root-franco-23r-twrp-t2900311) with a OTA update failure but that one is different as there's errors involved so I felt that the suggestions were not applicable in my case.
try manually going thru the recovery and run update file from /cache directory. and see what errors is trowing
look for cm-bacon-3628510d76-to-ac1ccf7921-signed.zip
NiTRoN69 said:
try manually going thru the recovery and run update file from /cache directory. and see what errors is trowing
look for cm-bacon-3628510d76-to-ac1ccf7921-signed.zip
Click to expand...
Click to collapse
I found the update file and tried to install in manually. The attached image shows the error message which has no meaning to me. I then cleared the cache and also the dalvik cache, booted up, checked for update, downloaded the update and install.
Same problem happened so back to square one
JJD809 said:
I found the update file and tried to install in manually. The attached image shows the error message which has no meaning to me. I then cleared the cache and also the dalvik cache, booted up, checked for update, downloaded the update and install.
Same problem happened so back to square one
Click to expand...
Click to collapse
That error message is saying that you have a modified lockscreen.
Transmitted via Bacon
timmaaa said:
That error message is saying that you have a modified lockscreen.
Transmitted via Bacon
Click to expand...
Click to collapse
Ah! that makes sense. I got the lockscreen after reading an article about it on the XDA news pages (http://www.xda-developers.com/android/dynamic-oneplus-one-lock-screen/) which took me to this thread http://forum.xda-developers.com/oneplus-one/development/dynamic-oneplus-one-lockscreen-t2890808
From here forward, how do you suggest I proceed. Is there a way to "uninstall" this lock screen or is it a matter of me doing a factory reset and starting afresh?
Unless there's a return to stock zip in the thread where you got your modified lockscreen, you'll need to start fresh.
Transmitted via Bacon
Trying to apply on a stock Oneplus One, just with root and TWRP.
Code:
asset failed: apply_patch_check("/system/app/Music2.apk","....","....")
E: Error executing updated binary in zip '/cache/cm-bacon...signed.zip
Any ideas?
timmaaa said:
Unless there's a return to stock zip in the thread where you got your modified lockscreen, you'll need to start fresh.
Transmitted via Bacon
Click to expand...
Click to collapse
hi, I have the almost the same problem, I did a factory reset but it gives me error again, what should I do
fackamato said:
Trying to apply on a stock Oneplus One, just with root and TWRP.
Code:
asset failed: apply_patch_check("/system/app/Music2.apk","....","....")
E: Error executing updated binary in zip '/cache/cm-bacon...signed.zip
Any ideas?
Click to expand...
Click to collapse
System modification on Music2.apk. Read the above advice by timmaaa.
---------- Post added at 05:11 PM ---------- Previous post was at 05:08 PM ----------
shcxatter2 said:
hi, I have the almost the same problem, I did a factory reset but it gives me error again, what should I do
Click to expand...
Click to collapse
Boot on TWRP recovery and flash XNPH38R OTA zip. See here: 4. Latest OTA incremental update zip
Primokorn said:
System modification on Music2.apk. Read the above advice by timmaaa.
---------- Post added at 05:11 PM ---------- Previous post was at 05:08 PM ----------
Boot on TWRP recovery and flash XNPH38R OTA zip. See here: 4. Latest OTA incremental update zip
Click to expand...
Click to collapse
that's exactly what my problem is I cannot install the update , twrp just gives me error
Use the modified XNPH38R update. You can find it in the xnph38r thread in general.
You did system modifications. By using the modified script, it won't check for those files.
This is why I say when you want to do system changes, just use a custom ROM because OTAs are going to be a headache for you if u dont intend on using what the OTA provided to you.
zephiK said:
Use the modified XNPH38R update. You can find it in the xnph38r thread in general.
You did system modifications. By using the modified script, it won't check for those files.
This is why I say when you want to do system changes, just use a custom ROM because OTAs are going to be a headache for you if u dont intend on using what the OTA provided to you.
Click to expand...
Click to collapse
I'm trying to figure out what "system modifications" I've done. It's probably freezing apps in titanium backup, as google's music always FC's on all devices, so had to be ignored.
fackamato said:
I'm trying to figure out what "system modifications" I've done. It's probably freezing apps in titanium backup, as google's music always FC's on all devices, so had to be ignored.
Click to expand...
Click to collapse
Freezing apps in TB does nothing for those system modifications. Just flash the modified script XNPH38R update and you'll be able to update. I've said this 2 times now.
zephiK said:
Freezing apps in TB does nothing for those system modifications. Just flash the modified script XNPH38R update and you'll be able to update. I've said this 2 times now.
Click to expand...
Click to collapse
Thanks. I think it only has the full one not the incremental one?
WARNING: THIS HAS BRICKED PHONES! It is suspected that having an encrypted phone causes these bricks, but that has not been confirmed. If your data partition is encrypted, it is extra important that you perform a factory reset before taking this OTA. Doing this will remove the encryption.
WARNING: INSTALLING THIS ON A LOCKED BOOTLOADER WILL ELIMINATE ALL CHANCE OF YOU EVER UNLOCKING YOUR BOOTLOADER.
If your bootloader is unlocked, it will not be re-locked after this update.
Do NOT flash this using TWRP. If you want to do that, use this version: http://forum.xda-developers.com/droid-turbo/development/rom-mcg24-251-5-100-stock-t3512949
So if you're a bad enough dude to flash this anyway, follow these instructions:
1. Backup all data on your phone. It will be lost.
2. If your bootloader is locked, make sure you are on SU4TL-49. If you aren't, take all available OTAs until you are.
3. If your bootloader is unlocked and you have TWRP installed, flash SU4TL-49 using this package: https://mega.nz/#!3xRhiaSR!KxH2Ya_BYK4zBjrxmej7dqaaDJVT1coTFJVJ5Fvb2WM
4. If you have TWRP installed on your phone, download the stock SU4TL-49 recovery here: https://mega.nz/#!L1AkQD4T!qoZIlLa-wuUBLMEi_gE574meiHd6Pehb34a-x3Gb-V8 and install it using the install image option in the install menu in TWRP. Reboot to recovery.
3. Perform a factory reset using the stock recovery menu. This will wipe all data and ensure that everything is formatted exactly as it should be.
4. Boot the phone normally and place the marshmallow update on the root of the directory that pops up when you plug in your phone.
5. Boot to recovery and at the stock recovery menu, select "apply update from sdcard."
6. Select the update and cross your fingers.
Get the update here: https://mega.nz/#!v0pRwThS!Pz9xuOSPjiOMtjlORkFrZ_ok0GTKqCfGzi5KmbDpHQ8
TheSt33v said:
WARNING: THIS HAS BRICKED PHONES! Do not use this unless you know what you're doing.
I will do my best to provide more detailed instructions later today. Good luck.
https://mega.nz/#!v0pRwThS!Pz9xuOSPjiOMtjlORkFrZ_ok0GTKqCfGzi5KmbDpHQ8
Click to expand...
Click to collapse
Are you sure that that file is the right one? It has the same version number as su4tl-49.
zys52712 said:
Are you sure that that file is the right one? It has the same version number as su4tl-49.
Click to expand...
Click to collapse
I'm positive. I seem to remember they did the same thing with SU4TL-49. The OTA was named after SU4TL-44 for some reason.
This is the stock recovery version, correct?
koftheworld said:
This is the stock recovery version, correct?
Click to expand...
Click to collapse
Correct. You install this using the sideload option in the stock recovery.
TheSt33v said:
Correct. You install this using the sideload option in the stock recovery.
Click to expand...
Click to collapse
Thanks for the info and the download! You finally brought the wall down. I'm waiting for the twrp version myself
.
Thank you, now we can see what can be done with the new modem, kernel, etc...
Looking forward to a plethora of improvements to our phones
koftheworld said:
Thanks for the info and the download! You finally brought the wall down. I'm waiting for the twrp version myself
.
Click to expand...
Click to collapse
I'm testing the TWRP version now. It should be up shortly.
EDIT: I flashed it and it seems to work fine. Uploading now. Should be up in a few hours. I'll check on it after I go run some errands real quick.
Despite having software status report official, not modified, I too got a status 7 error. Downloading again.
---------- Post added at 09:52 PM ---------- Previous post was at 09:51 PM ----------
zys52712 said:
Are you sure that that file is the right one? It has the same version number as su4tl-49.
Click to expand...
Click to collapse
This used to always be Motorola's naming scheme. New updates were named after the firmware version they replaced.
Sweet. I am going to wait till it is more stable. I do have a bad esn Turbo but I will need to unlock to bootloader to test.
Mirror for people having "quota exceeded" error at Mega
https://yadi.sk/d/AhmhE-yX32E84p
Rename to Blur_Version.24.81.5.quark_verizon.verizon.en.US.zip before use, throw in internal storage, and check for updates.
PS: I have 64Gb Employee Edition, and still had not receive update by air. What a shame, VZ! )
kitcostantino said:
Despite having software status report official, not modified, I too got a status 7 error. Downloading again.
---------- Post added at 09:52 PM ---------- Previous post was at 09:51 PM ----------
This used to always be Motorola's naming scheme. New updates were named after the firmware version they replaced.
Click to expand...
Click to collapse
Error 7? Are you trying to flash this in TWRP? Because you can't do that with this package. You need the stock recovery. I'm uploading a TWRP-friendly version now, but the internet is being slow today.
TheSt33v said:
Error 7? Are you trying to flash this in TWRP? Because you can't do that with this package. You need the stock recovery. I'm uploading a TWRP-friendly version now, but the internet is being slow today.
Click to expand...
Click to collapse
Negative. Stock recovery on a system that reports "Official". I'm at a loss.
kitcostantino said:
Negative. Stock recovery on a system that reports "Official". I'm at a loss.
Click to expand...
Click to collapse
Strange. Try reflashing SU4TL-49. If my TWRP package doesn't do it for you, use the full firmware package and do it manually with fastboot.
Installed successfully on two devices.
...
kitcostantino, did you refresh system, kernel, modem and recovery by SU4TL-49? Are you sure you didn't mess with Turbo Maxx ROMs in the past? Foreign bootloader can cause even brick, not just error. See bootloader status at fastboot mode should be " locked, status 0"
s5610 said:
Installed successfully on two devices.
...
kitcostantino, did you refresh system, kernel, modem and recovery by SU4TL-49? Are you sure you didn't mess with Turbo Maxx ROMs in the past? Foreign bootloader can cause even brick, not just error. See bootloader status at fastboot mode should be " locked, status 0"
Click to expand...
Click to collapse
lol. lawd, No. Ive been rocking status 3 for over a year.
As a tip, if anyone else with an unlocked bootloader runs into this,
what i had to do was restore my su-44 unmodified backup, OTA to SU-49, and then, after confirming my
q/e status was 0/1 i was able to update via the file in my Mega download folder. all is well now. they even added the newer version of command center. sweet. thank you all!!
It works in LOCKED BOOTLOADER??? .-.
square1230 said:
It works in LOCKED BOOTLOADER??? .-.
Click to expand...
Click to collapse
Um, I couldn't tell you.i be been unlocked since the day Sunshine could unlocked our bootloader's. What I can tell you is you should absolutely unlock that via Sunshine before you even dream of applying this update. There will never be another opportunity.
Just my
.02. This is likely the last update for this phone, and your only chance of seeing N is via custom Roms.
TWRP version up now: http://forum.xda-developers.com/droid-turbo/development/rom-mcg24-251-5-100-stock-t3512949
square1230 said:
It works in LOCKED BOOTLOADER??? .-.
Click to expand...
Click to collapse
Yes it should. See instructions in OP.