OK, new to this so please be patient.
I am a UK 3G Xoom owner so obviously have some limitations.
Was looking to manually update to 3.1 using the "5/6 easy steps" method.
I then found the thread relating to using the Aussie 3.1 and the UK Xoom.
This seemed ideal for me as the SD support was in place (aside from the problems the update may be causing) and it would less manipulation.
So..(if you are still reading)..
Took the plunge and flashed stock Telstra images... done. No 3g but all else pretty much OK.
Unlocked and rooted....fine. Latest clockword mod and flashed recovery.
I have already pulled the databases i need for later.
Getting confident now...
followed the instructions as per http://forum.xda-developers.com/showpost.php?p=15503902&postcount=261 and created backup folder.
transferred the three image files and the nandroid.md5
rebooted into recovery and selected the boot image.... fine.
selected system.img and error!
I recover using newest back and reboot is fine but root gone.
So where have I gone wrong?
I had the md5 mismatch error the second time I tried and resolved that to get boot.img in and that was fine. Again error on system.img.
I am very new to android but am learning quickly.
Can anyone see where i went wrong?
xoomtastic said:
OK, new to this so please be patient.
I am a UK 3G Xoom owner so obviously have some limitations.
Was looking to manually update to 3.1 using the "5/6 easy steps" method.
I then found the thread relating to using the Aussie 3.1 and the UK Xoom.
This seemed ideal for me as the SD support was in place (aside from the problems the update may be causing) and it would less manipulation.
So..(if you are still reading)..
Took the plunge and flashed stock Telstra images... done. No 3g but all else pretty much OK.
Unlocked and rooted....fine. Latest clockword mod and flashed recovery.
I have already pulled the databases i need for later.
Getting confident now...
followed the instructions as per http://forum.xda-developers.com/showpost.php?p=15503902&postcount=261 and created backup folder.
transferred the three image files and the nandroid.md5
rebooted into recovery and selected the boot image.... fine.
selected system.img and error!
I recover using newest back and reboot is fine but root gone.
So where have I gone wrong?
I had the md5 mismatch error the second time I tried and resolved that to get boot.img in and that was fine. Again error on system.img.
I am very new to android but am learning quickly.
Can anyone see where i went wrong?
Click to expand...
Click to collapse
I had the MD5 issue, so instead of editing it on the PC which never worked, i copied over the md5 file onto the xoom then edited it in root explorer. Once I edited it in root explorer no more mismatch errors.
Once you have the AU image installed you have to use the rooted image with fastboot and that should give you root back.
After that I went to tiamat 1.1 3G and everything worked fine. One thing dont push the frankenrom build you will lose SDcard if you do.
Lordao
Thanks for replying to both threads! I appreciate it honestly.
So it is correct in saying you got Telstra 3.1 on with data showing but no connectivity. Then got Tiamat 1.1 on (this method is one http://forum.xda-developers.com/showthread.php?t=1146153) and all was OK?
I tried using both edited nandroid.md5 and downloaded untouched (both via PC) but may try again and download via xoom only.
Onward and upward....
xoomtastic said:
Thanks for replying to both threads! I appreciate it honestly.
So it is correct in saying you got Telstra 3.1 on with data showing but no connectivity. Then got Tiamat 1.1 on (this method is one http://forum.xda-developers.com/showthread.php?t=1146153) and all was OK?
I tried using both edited nandroid.md5 and downloaded untouched (both via PC) but may try again and download via xoom only.
Onward and upward....
Click to expand...
Click to collapse
I got full connectivity on telstra str8 of the bat, i pushed back my telephony files on the telstra 3.1 but did not need to on the tiamat kernal 3G was working on 1st boot.
If you do not get provider from 3g on telstra go to networks and manually choose your provider it should kick in then.
Lordao
yeeeehaaaa
success!
Uk 3g XOOM with rooted 3.1
Working sd card and some usb thumb drive access, still testing.
So far no noticeable battery issue, honestly!
Ok, I am still learning android and got confused about what exact processes were needed.
I am happy, if anyone wants, to set out my exact route to get to this stage. If you have got to the stage of using adb or flashboot then the process is really easy. If not, then I can include some basics in getting started.
To recap, my Uk 3g XOOM has working 3g, sd support, enhanced usb support, resizable widgets, the "files" apk for looking at sd (es file explorer is better) and so far battery seems fine.
Xoomtastic!
xoomtastic - how did you get access to your SD card on 3.0.1? I'm trying ot update to 3.1 or 3.2 as well, from the euro 3G, which doesn't have SD card support (hence my wanting to update!). Yet the 5-step thread you linked to says to copy files to the SD... only how?
So my sister just bought a Transformer tonight, It has never been rooted or anything.
It will not detect any updates on the "search for update" OTA thing.
I also downloaded the ICS firmware directly from Asus's website, extracted it on a microSD card, and the trasnformer still doesnt show theres any update.
In the manual update guide it says put the extracted ASUS folder on the SD card, however there is no ASUS folder in the update downloaded from their site.
No idea whats going on.
Any help is appreciated.
Did you unzipped the file you download from Asus website? You can't leave it whole, there's another zip inside that zip.
Yep I followed all the instructions
Bawb3 said:
In the manual update guide it says put the extracted ASUS folder on the SD card, however there is no ASUS folder in the update downloaded from their site.
Click to expand...
Click to collapse
Reading that gives me the feeling that you probably didn't do it right. There is no reason it won't work.
Can you post the EXACT steps you took?
I'm having the same issue
There is no ASUS directory in the zip.
Inside the second zip there is a file called blob and a directory called Meta-Inf with a bunch if files in.
Okay, I go to asus's tf101 site, download sectiion > firmware.
Download the US SKU 4.0.3 firmware update which is ~300mb
Extract that zip which yields a file with another ZIP inside of it. There is no ASUS folder.
Like the above poster said, the second zip file looks like a recovery update script that you would flash in CWM with a meta-inf with the signatures, and a blob file.
EDIT[SOLVED]:
Okay I figured it out. I downloaded the 3.2.1 update from asus, which does have the ASUS folder. This one worked and launched the update wizard.
It seems that the update wizard looks for the directory /ASUS/Update/US_epad-user-x.x.x.xx.zip file on the root of the microSd card.
So I put the ICS update which is US_epad-user-9.2.1.11.zip into the ASUS/Update/ Directory in the microSD card that I initially extracted from the 3.2 update. Sure it enough it launched the update wizard and allowed me to select that file for the update.
ASUS Didnt properly upload the ICS update it seems.
I still dont know why the OTA didnt acknowledge an update.
OK, this is just getting dumb now.
OK, this is just getting really really stupid now. ASUS I AM SERIOUSLY STARTING TO HATE YOU.
OK I have done the following across MULTIPLE reboots and really getting ticked off now. This would NOT be an issue if the recovery mode didn't give me a damned green droid with yellow triangle with ! in the middle of it.
I have:
Way 1
-------
1 - Extracted WW_epad-user-9.2.1.11.zip from the original WW_epaduser9_2_1_11UpdateLauncher.zip from ASUS site.
2 - Copied extracted WW_epad-user-9.2.1.11.zip to EP101_SDUPDATE.zip
3 - Put both zips on root of microSD. Failed. Tried with copy on /sdcard/ as well, both with and without leaving the original 2 on the microSD.
Way 2
-------
Extracted the WW zip both to the / of the tablet and to the root of the microSD, trying both with and without leaving the originals on the microSD.
Way 3
-------
Same exact as Way 1 and Way 2 but with removing the .zip extension from both files, and with swapping removal of the extension between the 2 files on both the tablet and the microSD.
Way 4
-------
Tried all permutations of Way 1, 2, and 3 with both 8.6.5.21 and 8.6.6.21.
NONE of these ways worked.
I grabbed NVFLASH with 8.6.5.13 and that flashed just fine, except that the recovery mode is still giving me the triangular ! droid image.
I absolutely positively can not root or otherwise do anything to this tablet.
The tablet is a ASUS 32GB Transformer HD Tablet (Serial #: B50KAS#####) with a 2GB microSD formatted with FAT32. (I've tried formatting NTFS and FAT32) This is not a Prime! This is the original Transformer!
I even found an article for how to create your own and tried that as well!.
(Wow really guys? You can't post outside links?? Really? What the heck is that retardation supposed to prevent? I mean really!)
All I get for that mess is the USB connection is dropped even before NVFLASH can do anything. I have Windows 7 Ultimate, Mac OS X Lion, and several distributions of Linux (ArchLinux, Ubuntu, CentOS, Debian, and OpenSUSE). I've tried on them all!! This has been a great many hours trying to figure this out, searching like crazy through these forums. (Incidently, the 10 posts requirement in order to post in the 'experienced' area is just nuts.)
I even tried both the renaming WW portion of the zip name to US as described in other areas in this forum and it still failed! I'm a programmer by trade, and I have never run up against something as stubborn as this! The recovery mode is what is breaking all of this. I absolutely can not get a stable, working recovery mode on this tablet! Heck, I'd be happy with the stock 8.6.5.21 on here or ICS (the 9.2.1.11) without ever again attempting to root the pup! Can anyone assist in getting the recovery mode back to normal? Is there a way to use NVFLASH to write the original recovery mode back such that I stop getting that dang Droid With Yellow ! Triangle image?
Do you have CWM Recovery installed? If so, it will not do the OTA updates, but you can just go into CWM Recovery and then choose the 9.2.1.11 firmware and when it is done flashing, you will have an unrooted stock ICS (with stock recovery).
CWM
Unable to root. RazorClaw tells me I'm missing the required file (though it doesn't tell me what file that its) and says Too bad!
deryldoucette said:
Unable to root. RazorClaw tells me I'm missing the required file (though it doesn't tell me what file that its) and says Too bad!
Click to expand...
Click to collapse
Razorclaw only works on 8.6.5.19.
Not certain on which version you try to run razorclaw.
use Vipermod on 8.6.5.21 or higher.
was 8.6.5.13 which is what i was able to nvflash back to the tablet. Do you know if there is a more recent nvflash packaged 8.6? Looking to see if I can at least put 8.6.5.21 on here. Currently still running the 8.6.5.13
Mine also wont OTA, i have put the downloads in ASUS/Update and nothing... does not detect updates.
Just bought my tf101 yesterday, same problem. Called support and they told me the update was not pushed to my device yet and a manual update would probably fail.how long ago was ics released?
found it, february 24th... It should be pushed to my device by now, right?
Sent from my SPH-D700 using XDA
G'day guys,
I finally managed to get it to work for me!
TLDR Version - I have the US build version - this may or may not be relevant to these instructions:
* Use "App Backup" to backup all your apps and/or data (optional)
* Factory reset
* Choose "English (US)" from the initial setup wizard and default options for the rest (skip wifi setup)
* Plug the transformer in to your PC via USB
* Create the following folder structure exactly (including case!)
<Internal Storage>\ASUS\Update
* Copy US_epad-user-9.2.1.11.zip that you extracted from US_epaduser9_2_1_11UpdateLauncher.zip to "<Internal Storage>\ASUS\Update"
* Reboot Transformer
* Choose the triangle from the notification area
* TF should update successfully!
Long version:
I followed the instructions in this thread but still wasn't having any luck.
I don't have an external SD card so I was copying the zip from the downloaded file to internal storage\Asus\Update. The triangle was appearing in the bottom right but when I went to do the update it would reboot to the android man with an "!" on his chest. I then tried a factory reset and then recopied the update and tried again. Same "!" dude. I tried another reset but did two things different and it then worked! Instead of choosing "English (UK)" on the initial setup wizard (I'm from Aus) I chose "English (US)" (just a wild guess given its US update required for my TF. The other thing that I did differently was located the update at "ASUS\Update". Note the capitalisation of "ASUS" where previously I was using Asus. I had this idea when I noticed the first time I had both "Asus" and "ASUS" folders there simulataneously. So one or both of those things made it work for me!
If these tips worked for you please post your success (or otherwise even).
Best of luck!
Make sure you are using CWM version 6.0.1.0
I am not responsible for whatever happens to your device because everyone else puts this in their threads too! get over it
Be sure to click that Thanks button if this helped you. this also appears in everyone else's thread's! deal with it
1. download the update file for your region from paugustin's thread here:
http://forum.xda-developers.com/showthread.php?t=1720157
2. unzip it inside any folder.
3. open the file called updater-script which is located at:
/META-INF/com/google/android
4. delete the line and the blank space left afterwards then save changes to the file. the line for the US version looks like this:
assert(getprop("ro.product.name") == "a700_pa_cus1");
5. highlight everything that came out of the download from step 1, zip it, and rename it to update.zip
6. place in the root of an SD card, not internal storage!
Note: a few users have recommended placing the update.zip on internal storage. i tried it again from a SD card and it worked just fine. if you're having issues with this try internal.
7. reboot to recovery mode. if you need this guide you've had to do it in the past, nuff said! :silly:
8. select Apply update.zip
9. after you select Reboot System, you will be given two options:
Yes will keep CWM recovery but you wont be able to use recovery mode at all until you unlock the bootloader again!
No will allow the update to restore stock recovery, and you will need to re-flash CWM.
10. if you chose Yes from step 9, unlock your bootloader and do the root process again. DONE!
if you chose No, unlock your bootloader, flash CWM again, and do the root process again. DONE!
there are already guides on how to do that.
BONUS FOR USA TAB OWNERS!
This is ONLY FOR UPDATING FROM the Acer_A700_AV043.RV00RC00_AV043.RV07RC06_PA_CUS1.zip file from the link in Step 1 at the top of the page.
If you are on any other version, and / or from any other country, DO NOT TRY THIS!
This is the latest update with the power option added in settings & touch sensitivity improvements, with the getprop line already deleted from the script!
A. Download this directly to your tab.
B. Reboot to recovery mode.
C. Install.
D. After selecting Reboot System you will be given two options. Refer to Step 9 above.
E. After making your choice, you will be given the option to prevent the update from deleting root :victory:
F. Unlock your bootloader again.
G. If you chose No. from Step 9, re-flash CWM 6.0.1.0
H. If you chose No. from Step E, root again if you wish.
DONE!!
I've try this, but when I do point 8 (select Apply update.zip), the update is aborded.
I'm on SDs_Acer_AV043_A700_RV07RC06_EMEA_FR.zip with the root by patched boot.
I want install Acer_A700_AV043.RV07RC06_AV043.RV23RC04_EMEA_FR.zip.
I don't know why update fail.
imtheyoyo said:
I've try this, but when I do point 8 (select Apply update.zip), the update is aborded.
I'm on SDs_Acer_AV043_A700_RV07RC06_EMEA_FR.zip with the root by patched boot.
I want install Acer_A700_AV043.RV07RC06_AV043.RV23RC04_EMEA_FR.zip.
I don't know why update fail.
Click to expand...
Click to collapse
i think i know why.
i revised step 5, check it out
That's what I had done, zip and rename in update.zip.
imtheyoyo said:
That's what I had done, zip and rename in update.zip.
Click to expand...
Click to collapse
hmm... did you put it on an sd card?
and what error is it giving you?
Sterist said:
hmm... did you put it on an sd card?
and what error is it giving you?
Click to expand...
Click to collapse
Yes, and the message was "Update aborted"
Just a question. I have unlocked my A700 via method 2, so without CWM install.
If I follow this guide, placing the update.zip on the card, and restart with Volume-down+Power, will it execute the update.zip as well?
The update.zip in fact is the altered Acer_A700_AV043.RV07RC04_AV043.RV23RC05_WW_GEN1.zip according to the instructions.
If using Root Explorer, where would I have to place the update.zip file?
---------- Post added at 10:57 PM ---------- Previous post was at 10:52 PM ----------
CheopsChefren said:
Just a question. I have unlocked my A700 via method 2, so without CWM install.
If I follow this guide, placing the update.zip on the card, and restart with Volume-down+Power, will it execute the update.zip as well?
The update.zip in fact is the altered Acer_A700_AV043.RV07RC04_AV043.RV23RC05_WW_GEN1.zip according to the instructions.
If using Root Explorer, where would I have to place the update.zip file?
Click to expand...
Click to collapse
Thanks for any advice.
CheopsChefren said:
Just a question. I have unlocked my A700 via method 2, so without CWM install.
If I follow this guide, placing the update.zip on the card, and restart with Volume-down+Power, will it execute the update.zip as well?
The update.zip in fact is the altered Acer_A700_AV043.RV07RC04_AV043.RV23RC05_WW_GEN1.zip according to the instructions.
If using Root Explorer, where would I have to place the update.zip file?
Click to expand...
Click to collapse
I'm not sure if a modified update script would run on the stock recovery. you can try it, the worst that would happen is it will decline to run the update. i would recommend you always have CWM recovery regardless of any flashing/updating plans you may or may not have.
and the location for the update.zip does not change regardless of what you use to get the file there lol it doesn't matter if you use a Toyota or Lamborghini to get to work. silly question lol..
Thanks for your answer. The problem is, an unmodified update script wont run either on my unlocked A700.
And, I am scared about using CWM, as I hear stories it will possibly brick your A700, and that is something I am not too keen about.
But, with Root Explorer compared to ES File Explorer you have more possibilities. But I agree, it was abit a silly question.
So now, how to update my unlocked A700 with the OTA delivered by Acer? That's the question.....
CheopsChefren said:
Thanks for your answer. The problem is, an unmodified update script wont run either on my unlocked A700.
And, I am scared about using CWM, as I hear stories it will possibly brick your A700, and that is something I am not too keen about.
But, with Root Explorer compared to ES File Explorer you have more possibilities. But I agree, it was abit a silly question.
So now, how to update my unlocked A700 with the OTA delivered by Acer? That's the question.....
Click to expand...
Click to collapse
by my understanding, the CWM versions to avoid are 5.4.0.0 (something like that) and the touch version(s)
unlocking your bootloader and not installing CWM is like alcohol-free-beer... pointless.
When trying the above mentioned procedure, i first got an error 6, which i solved by editing the updater-script the second time with notepad++, so i could keep the unix-like line-ends.
Then when i tried to run the update.zip from within cwm, i got error status 7.
(On both the downloaded update file from the thread mentioned above, and from the original from Acer received OTA update file)
As far as i know, after googling error status 7 has to do with the update zip not for the system trying to update. But i am sure, as i also tried with the Acer received OTA (after deleting the first line in the updater-script), i used the correct update file.
What could cause this?
Hi. Link for U.S. tab owners (www.sendspace.com) is dead. Can you post again?
eman01 said:
Hi. Link for U.S. tab owners (www.sendspace.com) is dead. Can you post again?
Click to expand...
Click to collapse
LOL stupid mistake on my part
the link wasn't really dead, i just screwed up in how i posting it lol thanks for mentioningit
Got it. Thanks.
OK. I finally tried above method to update rooted U.S. A700.
Started with:
Image Acer_AV043_A700_RV07RC06_PA_CUS1
Build Acer_AV043_A700_1.029.00_PA_CUS1
CWM Recovery 6.0.1.1
I tried both methods above- initially using the update.zip specifically provided for U.S. A700 owners in the 2nd part of 1st post of this thread
IN "BONUS FOR USA TAB OWNERS!".
Tried it on 1st external SD, then internal SD.
Both ways I get RED TRIANGLE with exclamation point and message:
"Can't open /sdcard/update.zip
(bad)"
OR
"Can't open /emmc/update.zip
(bad)"
I am, of course, sure I copied the update.zip directly from Downloads to the root of the external and internal cards;
I also made sure to use "Choose zip from SD card" in CWM to find the Update.zip file right where I put it.
Not ready to quit, I tried again using the original Update zip file and modifying updater.script myself, exactly as described in the 1st part of the 1st post. I also tried this update.zip with modified updater.script on both the external and internal SD, without success.
This time I did get further, receiving:
Finding update package...
Opening update package...
Installing update...
Mount Data success
Verifying current system...
assert failed: apply_patch_check_("EMMC:\dev\block\platform\sdhci-tegra.3/by-name/LNX:4065536:95
Then a bunch of letters/numbers
E:Error in sdcard/update.zip
(Status 7)
Installation aborted.
P.S. I verified I have the assert line deleted in the updater.script before I tried this.
I should mention that I have stock ROM, have and have NOT deleted any system apps
(I have inactivated a few like VirusScan within Android).
Luckily I was able to reboot without any problems after all these attempts, but now I am stuck.
Any ideas?
hmmm that's an error i haven't seen before. try deleting the update and downloading it again, or disabling assert check
I'm not a developer, that's the best i can suggest. you'd have to ask someone with a bit more knowledge
it might have something to do with the root method you used originally
Well, I tried yIur modified update.zip multiple times (downloaded it 3 different times, and tried both internal and external SD). As mentioned, I also tried modifying the updater.script myself (used JOTA text editor; maybe that was an issue with respect to how it saves a file, etc.).
How does one disable assert check, as you describe? A link, perhaps?
Interestingly, today I was able to flash the original1.029 update (1st A700 OTA update) after modifying it's updater.script in exactly the same fashion you describe. It put me back to stock 1.029, which I then updated to stock 1.057 (2nd A700 OTA update). I then re-unlocked bootloader, re-rooted and re-installed CWM recovery 6.0.1.1 easily and successfully as described in the threads in A700 development in this forum. Still holding out on CM ROM, as it seems fairly buggy. Thanks for trying. My way definitely took longer; don't know why your direct method would not work on my tab. Thanks.
disable asset check should be one of about 4 or 5 options to choose from, right next to ''choose from internal'' / external
it actually might not be available on this device it's been a while since I've used CWM
i do these modifications right from my tab with ES file explorer.
glad you were able to get it working
[solved] US A700 rooted OTA update
hi all,
after few days of messing about I finally managed to update a rooted US A700. I will try to guide you through what I did.
After initially booting up the A700 I upgraded it OTA to AV043_A700_RV07RC06_PA_CUS1 and after that rooted it using method #2 in the rooting thread (method #1 didn't work for some reason)
Got OTA notification saying that AV043.RV23RC03_PA_CUS1 was available (performance update, 35.72MB in size) but that wouldn't install giving error Status 7.
Installed CWM 6.1.1, still tthe same results, it wouldn't even install any of the other ROM's that are posted in this forum.
I probably should mention that I saved the original OTA update for installation later.
here is the solution (at least in my case)
Downloaded ROM Acer_A700_AV043.RV00RC00_AV043.RV07RC06_PA_CUS1.zi p from http://forum.xda-developers.com/showthread.php?t=1720157
Extracted boot.img and flashed via fastboot flash boot boot.img
Rebooted into CWM recovery and flashed the earlier saved OTA update no problem (was saved on internal memory but external memory card should work as well)
Then all that needed to be done was to root the A700 again (I used method #2 again)
Hope that helps someone.
eman01 said:
OK. I finally tried above method to update rooted U.S. A700.
assert failed: apply_patch_check_("EMMC:\dev\block\platform\sdhci-tegra.3/by-name/LNX:4065536:95
Then a bunch of letters/numbers
E:Error in sdcard/update.zip
(Status 7)
Installation aborted.
Any ideas?
Click to expand...
Click to collapse
You are not using the original bootloader so checking failed.
Simply delete this line to fix it (it happened to me last week when I created my homemade OTA update). Don't forget to unlock your bootloader after that !
Hello peoples.
I just found this out from T-Mobile Website.
Android version 4.4.2
Build number C2GUMG1
Your phone can update to build number C2CUMC3:
Starting November 4, 2015, you may be prompted to update automatically (OTA).
That was only a few days ago. Someone has to have a phone that's not updated yet.
https://support.t-mobile.com/docs/DOC-13470
We need that update desperately
We can use it to fix Boot looped phones due to corrupting the ROM.
We can use it to potentially build a modified stock rom that will flash.
I know from the recovery.log in the Cache folder that the update zip will be downloaded to ".download" folder. Do notice the " ." it means its a hidden folder. You can view in linux pressing. ctrl - H.
Root Browser or es-file explorer might be able to see the hidden folder.
download the update but pull the battery so it dont install.
Copy that sucker.
Im pretty sure it deletes the update after it installs.
Also maybe safer I have seen people use ADB and start logcat to get the actual download url.
Please someone do this. If i can get my phone back up im working on building a rom.
Here is a thread on how to get the ota update for nexus. I think we can do the same.
http://forum.xda-developers.com/nexus-4/general/how-to-download-url-nexus-ota-update-t2414424
hey whts up
Hey man I've got an "Alcatel one touch fierce 2 7040t.. I've also got the option to download the c2cumc3 update but I have to unroot it first before it will let me download it though...if u can tell me what exactly u need and a lil help and I don't mind tryn to get what u need..I can do minor things with phones like flashing and other lil things so u might have to answer a cpl questions for me though lol so just hmu if u still need it..
BigCountry907 said:
Hello peoples.
I just found this out from T-Mobile Website.
Android version 4.4.2
Build number C2GUMG1
Your phone can update to build number C2CUMC3:
Starting November 4, 2015, you may be prompted to update automatically (OTA).
That was only a few days ago. Someone has to have a phone that's not updated yet.
https://support.t-mobile.com/docs/DOC-13470
We need that update desperately
We can use it to fix Boot looped phones due to corrupting the ROM.
We can use it to potentially build a modified stock rom that will flash.
I know from the recovery.log in the Cache folder that the update zip will be downloaded to ".download" folder. Do notice the " ." it means its a hidden folder. You can view in linux pressing. ctrl - H.
Root Browser or es-file explorer might be able to see the hidden folder.
download the update but pull the battery so it dont install.
Copy that sucker.
Im pretty sure it deletes the update after it installs.
Also maybe safer I have seen people use ADB and start logcat to get the actual download url.
Please someone do this. If i can get my phone back up im working on building a rom.
Here is a thread on how to get the ota update for nexus. I think we can do the same.
http://forum.xda-developers.com/nexus-4/general/how-to-download-url-nexus-ota-update-t2414424
Click to expand...
Click to collapse
Did you ever get the OTA?