Related
I searched the forum but couldn't find an answer. I have tried several times to update my TF to 3.2.1 but the update keeps failing.
I get a system update notification. The tablet shuts down. The little green android with the gears on his stomach appears with a progress bar under it. The progress bar gets about 1/3 of the way then an exclamation mark appears in a yellow triangle. The a few minutes later the tablet restarts and it says that the update failed.
I am currently on build number HTJ85B.WW_epad-8.6.5.9-20110816. My TF is unrooted.
Is this happening to anyone else? Anyone have any suggestions besides doing a factory reset then trying the update again? Thanks in advance for any help.
Was it rooted before?
Rooting itself doesn't break updates it's what you do whilst rooted that can, so unrooting isn't necessary. I'm having this issue again as I removed some Asus apps with Titanium Backup which I now can't get back (I did them when there was a bug in TB which didn't backup apps properly). The OTA update script checks the integrity of a bunch of apps and files, which if it fails will abort the update in the way you are seeing. Very annoying.
---
Sent from my Asus Transformer using Tapatalk
Yeah it was rooted. I just realized that immediately after I rooted it, I had made a CWM backup. I'm going to try to restore the backup and see if the update goes through. (fingers crossed)
Sounds like you're running a custom ROM
baseballfanz said:
Sounds like you're running a custom ROM
Click to expand...
Click to collapse
Nope, stock 3.2. The only thing that I flashed was a custom kernel.
The update still didn't work with my backup. Luckily the WW 3.2.1 update was posted in the development section, so I just re-rooted and flashed the update. Worked like a charm.
yeah, I think that your kernel will cause the update to fail since it updates some of the kernel modules.
tmcquake said:
Nope, stock 3.2. The only thing that I flashed was a custom kernel.
The update still didn't work with my backup. Luckily the WW 3.2.1 update was posted in the development section, so I just re-rooted and flashed the update. Worked like a charm.
Click to expand...
Click to collapse
Where did you find the ww 3.2.1? Because have the same problem and haven't found the rom. Wrong serach terms, for sure.
Got the problem, too!
Now I use Revolver!
I flashed revolver, too. Works like a charm.
ppzoid said:
Where did you find the ww 3.2.1? Because have the same problem and haven't found the rom. Wrong serach terms, for sure.
Click to expand...
Click to collapse
I got it from here: http://forum.xda-developers.com/showthread.php?t=1281161
It's only a 3.2 to 3.2.1 update though, it's not a full ROM, so you have to already have 3.2 on your TF. Hope this helps!
i have the same problem too.
my TF101 was totally non rooted .
is there a download for this 3.2.1 update? so i can prehaps update my TF mannually ....
I didn't find one, because of that i flashed revolver.
ppzoid said:
I didn't find one, because of that i flashed revolver.
Click to expand...
Click to collapse
i wish too....the thing is ....my TF cant even load into recovery....
it is a B40...TW 8.6.5.9
is this normal ??
coz I saw people can do it with B40 with 3.2.1....
http://forum.xda-developers.com/showthread.php?t=1280796
I too have a problem with the update on my rotted tf.I got an unofficial update apk here but I still get an error message when trying to flash in CWM.I heard that this could be due to a modified system file,but I don`t remember having done such a thing thought...
Good luck.
This is the Stock 8.6.5.19 US or WW update repackaged for Clockwork mod.
This update DOES NOT:
* Root your device if it's not already rooted
* Install clockworkmod
* Install at all if you aren't rooted
* Install at all if you don't already have clockworkmod.
This update has:
* Clockworkmod support (It does not include CWM, but doesn't reflash the recovery partition either)
* Rooted (includes SuperUser.apk & su 3.0.0)
* Busybox (1.19.2)
This will not work unless you have:
1. clockworkmod
2. STOCK firmware (root is fine)
3. the US or WW firmware
4. firmware 8.6.5.18
If this update will not apply, take note of which assert stopped the process. You probably applied some sort of mod to your transformer.
CWM package for ASUS FOTA Update 8.6.5.19 US
http://bellybuttonporn.com/android/transformer/kwt-cwm-8.6.5.19.zip
Tested on my own tf101.
CWM package for ASUS FOTA Update 8.6.5.19 WW
http://bellybuttonporn.com/android/transformer/kwt-cwm-8.6.5.19-WW.zip
I have not tested this. Let me know if it works, brave soul!
Note that these updates require you to be on 8.6.5.18. If you didn't update to .18 because of the bugs, do that before trying this update.
Applied US version and it was just too darned easy. Usually I have to modify something but this worked first time.
Much thanks, -- Hashi
I'm running revolver, but want to go back to stock rooted and install this. How can I do this? Thanks,
worked
Somehow i lost root after installing this. Cmw is still installed and so is superuser but titanium backup wont work because it says it cannot get root.
Edit: i reinstalled cmw from here http://forum.xda-developers.com/showpost.php?p=18789237&postcount=907 and now it works.
Worked great on my TF with WW.
Many thanks.
slopokdave said:
I'm running revolver, but want to go back to stock rooted and install this. How can I do this? Thanks,
Click to expand...
Click to collapse
This will not work unless you have:
1. clockworkmod
----------Install ClockwordMod Recovery. If already installed skip to step 2
2. STOCK firmware (root is fine)
----------Install stock firmware with or without root. If already installed skip to step 3
3. the US or WW firmware
----------It must be the US or WW firmware. If not install correct firmware listed in step 4
4. firmware 8.6.5.18
---------This is the firmware version it must be. If not then install the correct firmware version.
I beg your forgiveness if this doesn't answer your question. I was just trying to be helpful.
This broke my WiFi. It goes to "Error" after trying to start. Flipping airplane mode on or off doesn't help.
EDIT: Fixed. I hadn't re-installed my OC kernel, so stuff was breaking.
Any ideas?
-bZj
Worked without any problem on a rooted stock ROM WW model.
Worked for me on WW too, many thanks.
I can confirm that the WW update worked fine for me without any problems, thanks
everything works great except my bluetooth radio won't turn on and when I am docked I get no sound. I haven't tried a full wipe which would be the next step. I had to run a great deal of updates to get to this version so maybe that has something to do with it as well.
stuzor said:
everything works great except my bluetooth radio won't turn on and when I am docked I get no sound. I haven't tried a full wipe which would be the next step. I had to run a great deal of updates to get to this version so maybe that has something to do with it as well.
Click to expand...
Click to collapse
I second the wipe. I was initially running Prime and decided to go back to stock due to the numerous FC's I started to get starting apps after a few upgrades. My TF runs nice and smooth after flashing this, no problems with wifi or bluetooth and sound works as it should in my dock. I haven't really noticed any problems at all. And haven't really noticed much of a difference in speed or battery life between this and Prime.
don't suppose 8.6.6.19 WW is out as a flashable CWM zip ?
A few months ago, I loaded 2.3.6 firmware on phone. It is stock gingerbread with root from oden file all_in_one_odin_ep4d. Last week I received an OTA update. The update fails to load and leaves me at the screen with the white triangle with yellow exclamation point. I pulled the battery and rebooted. Today, the update came back. Still no go. I think the update is incompatible with the software on the phone.
Can someone tell me:
1. What is in the update? Is it going to remove root and allow Verizon to see that I 3rd party tether? Are they suddenly going to slap a tether package on my bill? Is it even worth installing?
2. If it’s not worth installing, can I tell my phone that I don’t want it by making it think that the update is already installed?
3. If the update is worth installing, should I wait for an oden install that contains the update or do I do something to the phone to allow it to receive the OTA update? If I do opt for the OTA what must I do to allow it to load?
Being somewhat novice when it comes to loading software on phones, is there a good FAQ out there that lists all the different loads, with what they contain and explanations of those components. Right now, voodoo, Peanut butter and jelly… buzzwords.
beavermjr said:
A few months ago, I loaded 2.3.6 firmware on phone. It is stock gingerbread with root from oden file all_in_one_odin_ep4d. Last week I received an OTA update. The update fails to load and leaves me at the screen with the white triangle with yellow exclamation point. I pulled the battery and rebooted. Today, the update came back. Still no go. I think the update is incompatible with the software on the phone.
Can someone tell me:
1. What is in the update? Is it going to remove root and allow Verizon to see that I 3rd party tether? Are they suddenly going to slap a tether package on my bill? Is it even worth installing?
2. If it’s not worth installing, can I tell my phone that I don’t want it by making it think that the update is already installed?
3. If the update is worth installing, should I wait for an oden install that contains the update or do I do something to the phone to allow it to receive the OTA update? If I do opt for the OTA what must I do to allow it to load?
Being somewhat novice when it comes to loading software on phones, is there a good FAQ out there that lists all the different loads, with what they contain and explanations of those components. Right now, voodoo, Peanut butter and jelly… buzzwords.
Click to expand...
Click to collapse
All in one package that you installed came with custom kernel. You need to flash a FP1 debloated/bloated/rooted rom and the FP1 kernel. Since you have the custom rom+kernel you can not use OTA update. Some people (like me) prefer to do it clean by go back to stock EP4d rom, then do the full update to FP1, then flash what ever custom rom out there, like Eclipse or debloated etc...More on how to do it here:
http://forum.xda-developers.com/showthread.php?t=1560117
Sooner or later you should be on the latest version any way specially for support from XDA.
Thanks for setting me straight. Let’s see if I understand your info.
1. I have a custom ROM and need to use the stock one to be able to get the update to install.
2. Once I install the stock ROM and get the update, I could reinstall the same custom ROM I have now.
3. Returning my phone to stock will remove root access so I can get the update
How do I get back to stock everything, update the phone and then add only root access. I don’t know enough about stock ROMs to know why I’d want or need one.
beavermjr said:
Thanks for setting me straight. Let’s see if I understand your info.
1. I have a custom ROM and need to use the stock one to be able to get the update to install.
2. Once I install the stock ROM and get the update, I could reinstall the same custom ROM I have now.
3. Returning my phone to stock will remove root access so I can get the update
How do I get back to stock everything, update the phone and then add only root access. I don’t know enough about stock ROMs to know why I’d want or need one.
Click to expand...
Click to collapse
1. Yes, you need EP4D stock rom to get OTA update.
2. Yes, once you on stock FP1, you can use flash eclipse 2.0 (which build from FP1 rom). Once done you will have FP1 eclipse with FP1 stock kernel.
3. If you have pure stock EP4D and rooted, you can take the OTA, but yours is not.
You have 2 Options to upgrade:
1. Flash back to pure stock EP4D, OTA upgrade to FP1 then flash pre-rooted FP1 eclipse 2.0 rom. Then flash cwm.
2. Flash FP1 pre-rooted eclipse 2.0 rom, flash cwm, flash FP1 kernel, flash FP1 radio.
Hope this help, don't hesitate to ask if you have more questions.
Ok. That makes sense, sort of…
I’m going to give #1 a try since I found the stock EP4D load on the page you recommended. I will then be able to get the OTA update and have a stock phone with FP1.
I will then follow #5 on that page to root my pure stock FP1 and make CWM stick after reboot. Do you know if there is a free program that will let me change the file permissions of “install-recovery.sh” like root explorer?
beavermjr said:
Ok. That makes sense, sort of…
I’m going to give #1 a try since I found the stock EP4D load on the page you recommended. I will then be able to get the OTA update and have a stock phone with FP1.
I will then follow #5 on that page to root my pure stock FP1 and make CWM stick after reboot. Do you know if there is a free program that will let me change the file permissions of “install-recovery.sh” like root explorer?
Click to expand...
Click to collapse
root browser lite or ES file explorer. Both you can get from the Market (google play).
Thanks for the help. I got the phone updated successfully. I ended up having to load eclipse ROM on the phone after the OTA update as the other method with superuser update and superuser fixer failed to deliver root access.
couple of questions:
1. I can no longer set multi-screen wallpaper. How do I restore this functionality?
2. I can't answer my phone using the puzzle pieces. what am I missing?
Mike
PS thanks again for all the help. Sometimes I just need a push in the right direction.
Now that i've had a chance to play with the phone... The market keeps crashing. Anyone know what to do?
Sent from my SCH-I510 using XDA
FIX: settings/applications/market/clear data Reboot
I have been anxiously waiting for asus to post the jb firmware (us tf300t). I found it today, but now realize if i flash it manually i lose my root, backed up with voodoo and superSU or not. I then was reading about this dlpkgfile thing. Am i understanding this correctly?
It is the file that gets downloaded from asus when you check for an OTA, or when an OTA is pushed to your device
It then reboots, and uses the file to update the device.
It does not make u lose root?
So theoretically, I should be able to put it in /cache/directory and then`reboot my tab and it should start updating right? I know i need to make sure i get US version, backup root, etc. But will this work how I am thinking it will?
Oh and, I am not sure why my ota failed in the first place, i think i might have uninstalled a system app by accident without thinking. I am just plain rooted stock, NOT unlocked. I had also run the firmware for ics from asus website yesterday to get all the stock stuff back on my tab, then rerooted, and am waiting for JB update now
I've noticed there was an update on kies this week (P3113UEBLH1), I'm not sure what it was thought.
I've tried upgrading in kies, it was stuck at 0% downloading then connection timed out.
The OTA update didn't find any updates available.
Then next morning, kies said no update available too.
So, Anyone got the update to work, and if so what changes did you notice?
The update is available for flashing with odin on samsung-updates.com , this is the 2nd 4.0.4 update. (I'm still running the old 4.0.4 (P3113UEBLG5))
I don't have it, but I can look into it...
Bibicp said:
I've noticed there was an update on kies this week (P3113UEBLH1), I'm not sure what it was thought.
I've tried upgrading in kies, it was stuck at 0% downloading then connection timed out.
The OTA update didn't find any updates available.
Then next morning, kies said no update available too.
So, Anyone got the update to work, and if so what changes did you notice?
The update is available for flashing with odin on samsung-updates.com , this is the 2nd 4.0.4 update. (I'm still running the old 4.0.4 (P3113UEBLG5))
Click to expand...
Click to collapse
My device is rooted, and the only backup I made with CWM was after I rooted, if I go to update (if my device can find it) will I:
1) Brick out and be screwed?
2) Have to flash my backup (which is rooted, so would that mean I can't update again?)
3) Be ok and keep my rooting?
4) Be ok, and lose my rooting, and have to re-root?
I realize I am kind of answering your question with a question, but I would be happy to see if I can track it down and see what changes there are, if it's safe to install.
FlynnErik said:
My device is rooted, and the only backup I made with CWM was after I rooted, if I go to update (if my device can find it) will I:
1) Brick out and be screwed?
2) Have to flash my backup (which is rooted, so would that mean I can't update again?)
3) Be ok and keep my rooting?
4) Be ok, and lose my rooting, and have to re-root?
I realize I am kind of answering your question with a question, but I would be happy to see if I can track it down and see what changes there are, if it's safe to install.
Click to expand...
Click to collapse
Try backing up your system using clockworkmod recovery first, then go to download mode, flash your firmware version (download from samfirmware or samsung-updates) and flash it with odin.
This way you're unrooted, running stock rom and stock recovery and then you can install the update.
I didn't try to install an update while rooted, but it's not recommended so don't try.
I did a back up after I rooted with CWM
Bibicp said:
Try backing up your system using clockworkmod recovery first, then go to download mode, flash your firmware version (download from samfirmware or samsung-updates) and flash it with odin.
This way you're unrooted, running stock rom and stock recovery and then you can install the update.
I didn't try to install an update while rooted, but it's not recommended so don't try.
Click to expand...
Click to collapse
So is my backup going to be rooted? Or will it be the stock? I am currently rooted stock 4.0.4.
Btw, I have found no information about the update anywhere on the net. Maybe they accidently did a push to us, and pulled it back?
Should I wipe cache, dalvik and FDR before I flash the firmware from those sites or use the backup I made already? (which I am unsure if I should even use since idk if it will be rooted or not lol)
I wasn't going to update till it was time to get JB, but this update that vanished is intriguing enough I might lol
As i know yes when you restore backup with cwm the result will be rooted also as the cwm takes image of the system when doing backup and as you when doing backup was rooted so when restore this backup you will be still rooted if you flash via odin no need to wipe cash and dalvik cash i never read anyone doing this
Even if you do this wipe no harm at all
Sent from my GT-I9100 using xda app-developers app
As mohamed selim said, but wipe your data and do a factory reset in clockworkmod (after backup)
and why will samsung pull back the update?
There's several reasons why this may happen
Bibicp said:
As mohamed selim said, but wipe your data and do a factory reset in clockworkmod (after backup)
and why will samsung pull back the update?
Click to expand...
Click to collapse
They pushed it out to the wrong devices
They pushed it out to early
They found a last minute bug and had to pull back
They are testing it, and not everyone should have gotten the option to get it.
Ok so to get things straight. If/when we go to JB I will need to download a firmware stock from one of the sites listed above, download it.
Do a backup (just to be safe of what I have now)
FDR/Wipe everything
Install the firmware using Odin
If everything looks good, re-flash CWM
Do another backup so I have a clean stock to revert back to down the road if needed.
That sum it up correctly? This way I can bookmark this thread so I don't forget lol.
**EDIT** When I use Odin to restore stock will I lose CWM? If so, what happens if something goes wrong in the Odin restore and I have a boot loop, or etc, what would be my next move since I won't have CWM to restore previous, would I be able to install it like I would if things were going ok?
Sorry for sounding like a n00b, I am still learning all about this, but I think I am getting closer to learning enough to not be a n00b lol. I only have 10 tabs open with this forum instead of 20!
FlynnErik said:
They pushed it out to the wrong devices
They pushed it out to early
They found a last minute bug and had to pull back
They are testing it, and not everyone should have gotten the option to get it.
Ok so to get things straight. If/when we go to JB I will need to download a firmware stock from one of the sites listed above, download it.
Do a backup (just to be safe of what I have now)
FDR/Wipe everything
Install the firmware using Odin
If everything looks good, re-flash CWM
Do another backup so I have a clean stock to revert back to down the road if needed.
That sum it up correctly? This way I can bookmark this thread so I don't forget lol.
**EDIT** When I use Odin to restore stock will I lose CWM? If so, what happens if something goes wrong in the Odin restore and I have a boot loop, or etc, what would be my next move since I won't have CWM to restore previous, would I be able to install it like I would if things were going ok?
Sorry for sounding like a n00b, I am still learning all about this, but I think I am getting closer to learning enough to not be a n00b lol. I only have 10 tabs open with this forum instead of 20!
Click to expand...
Click to collapse
It's not for the wrong device since it's saying P3113, and it's not jelly bean. as I've seen on samsung firmware.com it's 4.0.4.
Well, on my homescreen I put a shortcut for the software update, it still has a circle saying 'N" on it (which probably stands for new), but going in kies I don't find it, It only says it downloaded it but the firmware is up to date.
So probably either they really pulled it back, or it's a bug and they're fixing it. (I really can't wait for jelly bean)
Second, yes it will erase the CWM recovery and go back to stock recovery.
The common mistake people make to get a bootlop is not wiping data/doing a factory reset before flashing a new ROM, so you should go to recovery and do a factory reset, then go to download mode and flash the firmware with odin. If you ever get stuck in a bootloop, try pressing volume down + power key to get to download mode and re flash the ROM. if it's still stuck, try re-downloading the ROM files you downloaded, it could be corrupted.
Awesome!
Bibicp said:
It's not for the wrong device since it's saying P3113, and it's not jelly bean. as I've seen on samsung firmware.com it's 4.0.4.
Well, on my homescreen I put a shortcut for the software update, it still has a circle saying 'N" on it (which probably stands for new), but going in kies I don't find it, It only says it downloaded it but the firmware is up to date.
So probably either they really pulled it back, or it's a bug and they're fixing it. (I really can't wait for jelly bean)
Second, yes it will erase the CWM recovery and go back to stock recovery.
The common mistake people make to get a bootlop is not wiping data/doing a factory reset before flashing a new ROM, so you should go to recovery and do a factory reset, then go to download mode and flash the firmware with odin. If you ever get stuck in a bootloop, try pressing volume down + power key to get to download mode and re flash the ROM. if it's still stuck, try re-downloading the ROM files you downloaded, it could be corrupted.
Click to expand...
Click to collapse
So the one on the site even though its XAR is us? Can I ask why we have that tag? Not something like US or etc? I mean I don't care, just kinda curious since that would make it more simple to know which region gets what, at least for me it would lol.
Thank you so much for the help and the knowledge, I figured I would end up with stock recovery, which is why I wanted to make sure about what if something goes wrong.
As a side thought, where does the backup that CWM makes located? Can I copy and paste that on to my PC so I always have a back up handy? (I would sync it into the cloud). Can I flash that with odin down the road? Or is that only a CWM usable file?
Any more info on the firmware release?....Trying to download it now!
Firmware Version: P3113UEBLH1
OS: Ice Cream Sandwich
OS Version: v4.0.4
Release Date: 08-10-2012
Build Date: 08-10-2012
Changelist: 999349
Gizmo said:
Any more info on the firmware release?....Trying to download it now!
Firmware Version: P3113UEBLH1
OS: Ice Cream Sandwich
OS Version: v4.0.4
Release Date: 08-10-2012
Build Date: 08-10-2012
Changelist: 999349
Click to expand...
Click to collapse
That's all I know about it, where are you downloading it? samsung updates.com? or kies/OTA update?
Bibicp said:
That's all I know about it, where are you downloading it? samsung updates.com? or kies/OTA update?
Click to expand...
Click to collapse
I found it on some foreign site....samsung-updates.com won't let you download the P3113UEBLH1 firmware, Just the Kernel, I don't use Kies! Uploading it right now!
Gizmo said:
I found it on some foreign site....samsung-updates.com won't let you download the P3113UEBLH1 firmware, Just the Kernel, I don't use Kies! Uploading it right now!
Click to expand...
Click to collapse
Alright, tell me if you notice anything different.
Nice
good!
Im downloading it now. Ill post it when its rooted and deodexed
Bibicp said:
I've noticed there was an update on kies this week (P3113UEBLH1), I'm not sure what it was thought.
I've tried upgrading in kies, it was stuck at 0% downloading then connection timed out.
The OTA update didn't find any updates available.
Then next morning, kies said no update available too.
So, Anyone got the update to work, and if so what changes did you notice?
The update is available for flashing with odin on samsung-updates.com , this is the 2nd 4.0.4 update. (I'm still running the old 4.0.4 (P3113UEBLG5))
Click to expand...
Click to collapse
I tried updating it once with KIES and it got to a point and froze on the screen. I had to force the tablet to shut down and rebooted and the tablet was OK. Being a glutton for punishment I tried again with KIES and the LH1 update successfully updated my GT2 7 and the About screen confirms it. Directly after installing and rebooting I started getting error messages about Chrome crashing. I uninstalled Chrome browser and reinstalled it and all is well. No other problems. Do NOT really notice ANY difference at all.
The only problem I have is that NOW I have decided that I would like to root my GT2 7 and I am NOT sure the methods I see out there will work with the P3113UEBLH1 update.
Does anyone know if my GT2 7 - P3113UEBLH1 can be rooted safely??
grobin
I dont think IT is better than CM9
RomsWell said:
Im downloading it now. Ill post it when its rooted and deodexed
Click to expand...
Click to collapse
Can you please tell me what's different than the older UEBLG5 version? and btw can you upload the stock rom itself without root so I can test it? because I couldn't download :s
EDIT: I downloaded it via samsung-updates.com and flashed it with odin.
It's pretty much the same as UEBLG5 I didn't notice anything different, but I downgraded to UEBLG5 as samsung appears to have pushed back this update (UEBLH1), because when I connect the device to kies, it doesn't recognize it.
Bibicp said:
Can you please tell me what's different than the older UEBLG5 version? and btw can you upload the stock rom itself without root so I can test it? because I couldn't download :s
EDIT: I downloaded it via samsung-updates.com and flashed it with odin.
It's pretty much the same as UEBLG5 I didn't notice anything different, but I downgraded to UEBLG5 as samsung appears to have pushed back this update (UEBLH1), because when I connect the device to kies, it doesn't recognize it.
Click to expand...
Click to collapse
I think it broke wifi. Not sure what the change log says about it. If the Cam is fixed i think im just going to add it to the G5 update. And not bother posting this untill its confrimed OTA
RomsWell said:
I think it broke wifi. Not sure what the change log says about it. If the Cam is fixed i think im just going to add it to the G5 update. And not bother posting this untill its confrimed OTA
Click to expand...
Click to collapse
Sorry for the question, but what do you mean comfirmed OTA? Once kies told me about the UEBLG5 update, I couldn't install it with kies as it was lagging.
Next day I found it on the OTA update.
This one showed on kies for a day, then next day neither kies or the OTA udpates showed there was an update so it probably got pulled back?