Asus Firmware Update Issue - Asus Eee Pad Transformer Prime

I have a TP201, unlocked bootloader, rooted. No ROMs, just Android 4.0.3.
My machine doesn't recognize any system firmware update. I followed the instructions in various locations on downloading the official Asus update, moved to internal memory, temp unrooted (with Voodoo) and restarted. Upon restart, it prompts me to start update sequence. I do so, it reboots to CWM boot. I tried restarting, no dice. I went to install zipped update from Asus, restarted and it still went back to CWM Recovery.
I researched and installed ADB for bricked 1a option...and now my machine boots to 4.0.3 fine again.
I would like to install the Asus firmware update but don't know how - it seems CWM is interfering somehow.
Thank you.

jjjenkin said:
I have a TP201, unlocked bootloader, rooted. No ROMs, just Android 4.0.3.
My machine doesn't recognize any system firmware update. I followed the instructions in various locations on downloading the official Asus update, moved to internal memory, temp unrooted (with Voodoo) and restarted. Upon restart, it prompts me to start update sequence. I do so, it reboots to CWM boot. I tried restarting, no dice. I went to install zipped update from Asus, restarted and it still went back to CWM Recovery.
I researched and installed ADB for bricked 1a option...and now my machine boots to 4.0.3 fine again.
I would like to install the Asus firmware update but don't know how - it seems CWM is interfering somehow.
Thank you.
Click to expand...
Click to collapse
Read about things before unlocking. Learn where to ask questions.
Sincerely,
The Internet
P.S.
You cannot update your tablet with official Asus updates after unlocking. Search the forums for developer assisted solutions.
Sent from my ADR6425LVW using xda premium

jjjenkin said:
I have a TP201, unlocked bootloader, rooted. No ROMs, just Android 4.0.3.
My machine doesn't recognize any system firmware update. I followed the instructions in various locations on downloading the official Asus update, moved to internal memory, temp unrooted (with Voodoo) and restarted. Upon restart, it prompts me to start update sequence. I do so, it reboots to CWM boot. I tried restarting, no dice. I went to install zipped update from Asus, restarted and it still went back to CWM Recovery.
I researched and installed ADB for bricked 1a option...and now my machine boots to 4.0.3 fine again.
I would like to install the Asus firmware update but don't know how - it seems CWM is interfering somehow.
Thank you.
Click to expand...
Click to collapse
Once you unlock there is no way back to a stock Asus Rom. What you can do however is to use a custom Rom based on the Asus source. I'm using Androwook 1.51 which seems very very close to the stock Rom feature wise but rooted and more customizable - and faster and smoother. In fact it makes me wonder why Asus itself can't seem to make a Rom like this when the devs on this site can make an Ausus ROM better than Ausus itself can do?
Bascially unless you use a custom ROM now that you are unlocked you are permanently stuck on 4.03.
Go here: http://forum.xda-developers.com/showthread.php?t=1674827
Follow the instructions in the second post for "Upgrade instructions for ICS". Read everything very carefully. Read it many times if you have to to make sure you understand it. Ask questions first, then flash, not the other way around. You currently have a working device so take your time and don't take unnecessary chances.

In fact it makes me wonder why Asus itself can't seem to make a Rom like this when the devs on this site can make an Ausus ROM better than Ausus itself can do?
That is why i unlocked my last week.
don;t know why u can't stop the updated from asus if you don't want them.

Newfe said:
...
don;t know why u can't stop the updated from asus if you don't want them.
Click to expand...
Click to collapse
Actually the issue is that the OP wants the update from Asus but did not understand that once he unlocked he was never going to get it.

Related

Root Problem. [RESOLVED]

Up until today, I've been rooted. Used the SuperOneClick program. It was a piece of cake.
Today, I decide to check for new software updates..Two new ones.
I updated them and now I'm running 2.2.2 and ed05. Well I'm assuming that's the problem.
Because I've been going through the process today of backing up my ROM and stuff, to flash MIUI for the first time. Well, nothing seemed to work.
I tried to backup my current ROM, but nothing happened. (Should've rebooted and come back on, like normal after 'backup current ROM' was selected and a name was entered for it; Didn't happen. )
So I figured that the new software updates unrooted my phone.
So I go back into SOC and root my phone again, but during the process, it tells me that I'm already rooted. Finishes the process and I reboot my phone, etc.
Well the Superuser app is in my list now, but none of the root-required apps are working. They all tell me that I'm not rooted. I even used Root Check to see the status. It tells me as well, that I'm not rooted.
I go back to the SOC program and UNroot. Well that was successful. I reboot, etc.
No Superuser app. So far so good. So I go BACK again and root, everything went well, except when it said an 'su' command was sent to my phone, I never got one, but I still got the Superuser app. And still, the apps tell me I'm not rooted.
Any kind of help is great. I really appreciate all the time, spent reading this.
Sorry if I went on and on, but it's bugging me now and I really need some answers to what the problem might be. Thanks, guys. ;(
superoneclick does not work on ed05
you need to odin cwm recovery
then reboot into recovery using three finger method
install root.zip file
then reboot
directions for rooting with odin is here:
http://www.galaxyforums.net/forum/fascinate-rs-guides/1967-how-root-froyo-gingerbread-your-fascinate.html
SOC does work with ED05.. I've used it several times, different phones.
Really? I thought quite a few folks were having trouble with soc after the ota ed05 update? If thats the case, then thanks for the clarification... although odin is still another option for the op since soc is not working.
droidstyle said:
superoneclick does not work on ed05
you need to odin cwm recovery
then reboot into recovery using three finger method
install root.zip file
then reboot
directions for rooting with odin is here:
http://www.galaxyforums.net/forum/fascinate-rs-guides/1967-how-root-froyo-gingerbread-your-fascinate.html
Click to expand...
Click to collapse
I read most of the first page on that thread, mostly just read the latest replies about that method. I'll read the full directional tutorial once I'm clarified of questions.
I think I read a couple of users saying this does root your phone, but it will wipe all data as well? I'm not quite sure. I want my phone rooted, no matter if I install MIUI or not. I don't want a factory reset though.
Thanks droidstyle, I'm back to being rooted!
Now onward to flashing MIUI! Wish me luck.
:^)

[Q] Is WW JB Update still available from OTA?

My situation:
.28 Rooted (not unlocked) with a few tweaks such as keyboard and browser2ram.
Tried to JB update via OTA and manual method and got red andy.
Said screw it, took the factory .28 image from asus and loaded it onto my tablet before and after doing a factory reset/data wipe.
So I'm now completely stock and when I check for updates it says not found.
Tried clearing DM and CM CLient as well as cold booting linux [Pow + Vol Dn] and still says "no update found"
So is the WW JB Update still avail or did asus pull it?
Thanks
I'm having the same problem. Can anyone confirm that they have successfully downloaded the JB update OTA in the last few hours?
Happened to me as well, i think after you got red andy once you dont get the ota anymore. I went ahead and used manual upgrade method.
clouds5 said:
Happened to me as well, i think after you got red andy once you dont get the ota anymore. I went ahead and used manual upgrade method.
Click to expand...
Click to collapse
Same problem here. Rooted, locked, stock.
Had the notification bar give me the JB update once, that install failed.
I then checked the f/w update manually, found it, redownloaded it, that install failed.
Now I can no longer get the update via the f/w update checker. (tried many times last night and this morning)
Clouds... is the JB update available to be installed manually? Can you point me in the right direction?
mothman0 said:
Same problem here. Rooted, locked, stock.
Had the notification bar give me the JB update once, that install failed.
I then checked the f/w update manually, found it, redownloaded it, that install failed.
Now I can no longer get the update via the f/w update checker. (tried many times last night and this morning)
Clouds... is the JB update available to be installed manually? Can you point me in the right direction?
Click to expand...
Click to collapse
I think the files you want are linked here, but they take an age to download:
forum.xda-developers.com/showthread.php?t=1909820
I had a completely stock ICS .28 and got a dead droid (DMClient error). I manually downloaded the .28 from asus put it on a micro sd and it found this on reboot and installed OK. Now I am watching the green bar slooooowwwwwlly download the WW rom. The file has no extension, so I can't tell yet whether it is a blob file or the required zip.
ClevaTreva said:
I think the files you want are linked here, but they take an age to download:
forum.xda-developers.com/showthread.php?t=1909820
I had a completely stock ICS .28 and got a dead droid (DMClient error). I manually downloaded the .28 from asus put it on a micro sd and it found this on reboot and installed OK. Now I am watching the green bar slooooowwwwwlly download the WW rom. The file has no extension, so I can't tell yet whether it is a blob file or the required zip.
Click to expand...
Click to collapse
Well, I just finished downloading that file, and whatever it is, and I renamed it as a zip (which it is) and my TFP ignored it. Maybe it needs a specific name to work.
The many of us for which the OTA failed will have to wait for Asus to list the files on their download site.
ClevaTreva said:
Well, I just finished downloading that file, and whatever it is, and I renamed it as a zip (which it is) and my TFP ignored it. Maybe it needs a specific name to work.
The many of us for which the OTA failed will have to wait for Asus to list the files on their download site.
Click to expand...
Click to collapse
Alrighty, thanks.
This is the first time I've had any issues with updates, so was/am hesitant to dive in with the suggested workarounds posted in various places... don't know enough about the whole 'adb shell' stuff, etc, and don't want to make things worse.
I'm assuming that manually updating is relatively simple once Asus provides the files.
mothman0 said:
Alrighty, thanks.
This is the first time I've had any issues with updates, so was/am hesitant to dive in with the suggested workarounds posted in various places... don't know enough about the whole 'adb shell' stuff, etc, and don't want to make things worse.
I'm assuming that manually updating is relatively simple once Asus provides the files.
Click to expand...
Click to collapse
Hi
I had the same problem with the move from Honeycomb to ICS. The OTA would not do it and I got the red/dead droid. I have tried EVERY method to get Jelly Bean. The first attempt was OTA, and this loaded the file and tried to update but failed. Before I did it I back up root and unrooted. I have made no changes to the core system files. I have tried each method posted and none work. It goes straight to a dead driod. I re-installed .28 from the Asus site and still it would not work.
I shall have to wait until Asus decide that those like me 'deserve' JB and post the manual update files on the download page:
http://www.asus.com/Eee/Eee_Pad/Eee_Pad_Transformer_Prime_TF201/#download
Indeed.
Once the update is available there, is a pretty straight forward process? Or does it still require terminal commands, etc?
glad to see i'm not the only one.
Guess i'll have to wait for Asus to post the JB files.
after hearing about some of the bricks I'm patient enough to wait a few more days.

Pantech Flex Jelly Bean Released!

Just got to know that Pantech has released the much awaited Jelly Bean 4.1 for the Flex through OTA AT&T software update.
Like many others, I'm using the flex outside US, therefore, cannot update my flex.
Would request someone to upload the OTA JB zip file.
Can't wait to see Jelly Bean on the Flex.
PS: Check out the Pantech website for this great news
This is good news. I wish I wasn't rooted with CWMR so I could get this. Tried flashing stock recovery.img and boot.img files but get NOT SUPPORT.
Anyone know a way to get this phone back to complete stock so we can get the Jell Bean goodness?
I managed to unroot and restore stock recovery.
Got prompted for the update, it downloaded and installed fine!
This little Flex seems quite a bit better with Jelly Bean. Wish it had been 4.2 but 4.1 is fine.
Tersanyus said:
I managed to unroot and restore stock recovery.
Got prompted for the update, it downloaded and installed fine!
This little Flex seems quite a bit better with Jelly Bean. Wish it had been 4.2 but 4.1 is fine.
Click to expand...
Click to collapse
Can you upload the update file?
How did you unroot?
Sent from my PantechP8010 using xda app-developers app
Not rooted anymore so probably can't get the update file. It was like 264MB or something.
Not planning to root this phone again.
Interesting that the Pantech diag menu shows still rooted and tampered, it's definitely not rooted.
It should be 100% stock.
If you know of a way to get the file off the phone I can look for it.
---------- Post added at 01:09 PM ---------- Previous post was at 12:52 PM ----------
I knew from experience I had to go to stock recovery and unroot to update.
I flashed a stock rooted nandroid backup I had made after rooting initially.
To unroot I think I went into the SuperUser app and choose option to unroot.
Stock recovery file is posted in a thread here somewhere, had recovery.img and boot.img.
Tried flashing those in fastboot but only got NOT SUPPORT mesage.
I took a flashable zip file that had CWM recovery.img file in it and replaced it with the stock recovery.img and flashed it in CWM.
Once stock recovery was on the phone when I tried to use it I only got a little android symbol lying on its back with a red exclamation point.
Phone booted fine and worked ok
Couldn't get it to see the AT&T update until this morning.
Things I have noticed in this new Jelly Bean build for our little Flex:
Of the stock AT&T apps only 3 I could disable (ugh), why no Disable button
good news
Tersanyus said:
Not rooted anymore so probably can't get the update file. It was like 264MB or something.
Not planning to root this phone again.
Interesting that the Pantech diag menu shows still rooted and tampered, it's definitely not rooted.
It should be 100% stock.
If you know of a way to get the file off the phone I can look for it.
Click to expand...
Click to collapse
Basically you will find the update in the /cache folder.
I'm not sure if you you can access this folder without being rooted. You can give it a try using the ES File Explorer.
Let me know if you get the update.
ES File Manager did see the cache folder and all the other system folders. It was empty. I'm sorry, I factory reset the phone last night from stock recovery since it was not updating built in apps properly. Never seen stock recovery on this phone before. It has an option for root. I selected it. Downloaded a few root checker apps, not rooted.
I'm sorry if I hadn't reset it last night I might have found the file. I'm sure it will turn up somewhere. This little Flex doesn't have much in the way of development but someone here at XDA will get it sooner or later.
Tersanyus said:
ES File Manager did see the cache folder and all the other system folders. It was empty. I'm sorry, I factory reset the phone last night from stock recovery since it was not updating built in apps properly. Never seen stock recovery on this phone before. It has an option for root. I selected it. Downloaded a few root checker apps, not rooted.
I'm sorry if I hadn't reset it last night I might have found the file. I'm sure it will turn up somewhere. This little Flex doesn't have much in the way of development but someone here at XDA will get it sooner or later.
Click to expand...
Click to collapse
Oh that's bad!
Actually, there's another way. If you can share your system nandroid backup, maybe that can help.
Try Rooting
Tersanyus said:
ES File Manager did see the cache folder and all the other system folders. It was empty. I'm sorry, I factory reset the phone last night from stock recovery since it was not updating built in apps properly. Never seen stock recovery on this phone before. It has an option for root. I selected it. Downloaded a few root checker apps, not rooted.
I'm sorry if I hadn't reset it last night I might have found the file. I'm sure it will turn up somewhere. This little Flex doesn't have much in the way of development but someone here at XDA will get it sooner or later.
Click to expand...
Click to collapse
Why dont you try to root with this method http://forum.xda-developers.com/showthread.php?t=1886460 ,its the same you used to root 4.0.4 I guess, should work, pull out the update and then unroot the phone as you dont want it rooted.
It happened to me, even rooted I wanst able to see /data content with ES File Blablabla, then tried with root explorer and worked fine.
I'm not going to root this Flex. It's not a primary phone for me (never was). It is used as a spare now and can be used by novice users in my family and friends. Don't want them to have a rooted phone. I'd been wanting to get this phone back to complete stock for a while but hasn't really put much effort into it.
When I saw that Pantech released JB for Flex a few days ago that was my motivation to get it back to stock. Frankly I was surprised I was able to get it back to stock and not brick the phone!
I'm uploading the stock rooted rom I have. Luckily I saved that on my computer. It's uploading to Dropbox now so it will take a while.
Thanks for your help
Tersanyus said:
I'm not going to root this Flex. It's not a primary phone for me (never was). It is used as a spare now and can be used by novice users in my family and friends. Don't want them to have a rooted phone. I'd been wanting to get this phone back to complete stock for a while but hasn't really put much effort into it.
When I saw that Pantech released JB for Flex a few days ago that was my motivation to get it back to stock. Frankly I was surprised I was able to get it back to stock and not brick the phone!
I'm uploading the stock rooted rom I have. Luckily I saved that on my computer. It's uploading to Dropbox now so it will take a while.
Click to expand...
Click to collapse
Well, thanks for the file, I'm outside US and even on stock, update notification doesn't prompt.
I got mine back to Stock, but when I hit check for upgrade it says..."Previous session is running. Please Try Later"
I have wiped it several times. any ideas?
Wait...
kneemeister said:
I got mine back to Stock, but when I hit check for upgrade it says..."Previous session is running. Please Try Later"
I have wiped it several times. any ideas?
Click to expand...
Click to collapse
I can see ATT's software updater sucks, we just can wait for our friend's upload.
Here it is: Link removed, Dropbox suspended it.
That should be a stock but rooted rom. Nothing else done to it at all. At least. I had that on the phone for a while as a backup when I was playing with roms for the flex.
Probably only going to leave this link up for a day. I'd make your own nandroid backup first. You'll probably get an md5 error in CWMR but there are instructions for fixing that around. I think it was ADB commands that had to fix it. I know the instructions for clearing the md5 error are in one of the flex rom threads, not that there were many of those. The standard disclaimer applies, if this nandroid backup bricks your phone, I can't help you.
I got the same previous session message too. Then it said no update after wiping. I think the best thing is just wipe and don't check for updates. Leave phone on, wifi on and wait for the phone to check on it's own. I got the prompt in a few hours.
Hope this helps you.
So, need to flash stock recovery after restoring nandroid correct?
Sent from my PantechP8010 using xda app-developers app
Likely if you do not flash stock recovery in CWMR the update will fail. I tried to take the update before flashing stock recovery, it failed each time. I had already unrooted though. Pretty much what I have learned from flashing various phones over the years is that if you are not stock completely any OTA updates from the carrier will fail or soft brick your device.
I think the Flex was one where I had just that issue. There was some AT&T update a few months back, I said to apply it and I got stuck in recovery. Every time I rebooted the phone it just booted to recovery. Found out if I went into the diag screen on the Flex and choose reboot from there I could boot normally. Eventually I figured out I had the wrong boot.img on the phone. Once that was fixed the phone booted fine. But the update never worked.
You can try to take the update with CWMR but I doubt it will work and could brick or soft brick. I've learned to never take an OTA update from the carrier if you are not completely stock.
Still waiting
Tersanyus said:
Likely if you do not flash stock recovery in CWMR the update will fail. I tried to take the update before flashing stock recovery, it failed each time. I had already unrooted though. Pretty much what I have learned from flashing various phones over the years is that if you are not stock completely any OTA updates from the carrier will fail or soft brick your device.
I think the Flex was one where I had just that issue. There was some AT&T update a few months back, I said to apply it and I got stuck in recovery. Every time I rebooted the phone it just booted to recovery. Found out if I went into the diag screen on the Flex and choose reboot from there I could boot normally. Eventually I figured out I had the wrong boot.img on the phone. Once that was fixed the phone booted fine. But the update never worked.
You can try to take the update with CWMR but I doubt it will work and could brick or soft brick. I've learned to never take an OTA update from the carrier if you are not completely stock.
Click to expand...
Click to collapse
Im on stock and I cant update, no root, stock recovery, Ive been waiting for the update and nothing.
I dont know if is because Im outside US
I got mine back to stock and unrooted, but the upgrade still fails at about 25% and reboots. If I clear cache and wipe, it will download again, then fail again. Even after flashing back to stock, recovery still says rooted and so does the software upload screen. But I have confirmed that I am no longer rooted. I am about to give up.

[Q] i9205 problem after ota + root

I connect my Galaxy Mega (i9205) to kies and it showed that my phone have new update. Bear in mind that my phone is rooted previously (CWM). Kies updated my phone to I9205XXUCNA3. I update my phone with no problem (it took longer time only) but unfortunately KNOX ruined everything. It keeps on saying that SuperUser is trying to access the system. Furthermore, my Wifi is not working at all. I tried to click on the toggle button but no to avail.
So after searching, I found out how to disable KNOX - By flashing using vcoreroot-v2. Done flashing with this file, and now I can't see my interna; SDCard. I'm doomed and now I don't know what to do to turn back to how it was before.
Anybody that can help me, really appreciate it.
nuar_y said:
I connect my Galaxy Mega (i9205) to kies and it showed that my phone have new update. Bear in mind that my phone is rooted previously (CWM). Kies updated my phone to I9205XXUCNA3. I update my phone with no problem (it took longer time only) but unfortunately KNOX ruined everything. It keeps on saying that SuperUser is trying to access the system. Furthermore, my Wifi is not working at all. I tried to click on the toggle button but no to avail.
So after searching, I found out how to disable KNOX - By flashing using vcoreroot-v2. Done flashing with this file, and now I can't see my interna; SDCard. I'm doomed and now I don't know what to do to turn back to how it was before.
Anybody that can help me, really appreciate it.
Click to expand...
Click to collapse
I see that so far you have found a way to disable knox AND cripple your Mega...
IMHO the best way to fix this situation is:
1. Download once more your newest firmware I9205XXUCNA3 (e.g. from Sammobile) and flash it by Odin to resolve starting position. Or try to restore your firmware through Kies.
2. Then BEFORE YOU DO SOMETHING read forums to find information how safely root firmware with KNOX. You have to be known so probably your warranty is already void and if not so it will be on the first attempt to root your unit. You are warned... There are some threads about rooting KNOX-ed firmware and even how to come back (partially) to previous build.
BEWARE! Do not attempt to flash older firmware lest you brick your Mega. New bootloader prevent from downgrading and if you try you will have endless bootloop. Upgradindg to newest firmware is one way trip.
OK I've followed your advise:
1. Re-download I9205XXUCNA3 from Sammobile and flash using odin.
2. Re-apply vcoreroot-v2
and after reboot.... WALLA!! My phone is back to normal again! And same goes to my internal SDCard, back as normal.
I have a problem with messaging where it keeps on crashing at first. But then I boot into recovery, clear cache and apply factory reset.
Now, all back to normal.
Anyhow, thank you so much for the tips. Now I can ease out a bit
nuar_y said:
OK I've followed your advise:
1. Re-download I9205XXUCNA3 from Sammobile and flash using odin.
2. Re-apply vcoreroot-v2
and after reboot.... WALLA!! My phone is back to normal again! And same goes to my internal SDCard, back as normal.
I have a problem with messaging where it keeps on crashing at first. But then I boot into recovery, clear cache and apply factory reset.
Now, all back to normal.
Anyhow, thank you so much for the tips. Now I can ease out a bit
Click to expand...
Click to collapse
I am glad you are successful. Sometimes you have to repeat two times, but no more: one for download errors, two for your errors. But if then you are not successful... then you have to look for another solution...
Can I know what rom u are using before updating to stock rom using kies?
Sent from my GT-I9205 using XDA Free mobile app

HTC M8 stuck on boot screen

hi everyone , i rooted my device couple months ago and it was all going well then i received an OTA update i followed the step to get the OTA update install a stock recovery, unrooted my phone and installed OTA update but now my just won't boot up. it is stuck on the white screen . I've tried everything i read a lot of threads on xda but nothing seems to be working . I tried installing twrp and stock recovery again but no luck . Someone please help.........
@darknight#1993,
Thanks for posting in XDA Assist. I will move your question to the HTC One M8 Q&A and Troubleshooting forum. The users there will be able to help resolve your issues.
Good luck,
-- Gandalf
The same thing happened to me over the weekend. After trying everything I gave up and used the official ruu from the HTC site. It sucks having to reinstall all the apps and set the phone up the way I like it but at least it's working again.
darknight#1993 said:
hi everyone , i rooted my device couple months ago and it was all going well then i received an OTA update i followed the step to get the OTA update install a stock recovery, unrooted my phone and installed OTA update but now my just won't boot up. it is stuck on the white screen . I've tried everything i read a lot of threads on xda but nothing seems to be working . I tried installing twrp and stock recovery again but no luck . Someone please help.........
Click to expand...
Click to collapse
How did you unroot? If you just used the SuperSU unroot function (or similar) I don't think its enough. You need the fully stock unrooted ROM.
Also its not clear for your lack of detail if you are using the right stock recovery. What is your main version (firmware) number and what stock recovery did you use?
It will probably be easiest to RUU at this point, as the previous response mentioned. If s-on, you will need to relock the bootloader to RUU; and the phone will be wiped when you do so.

Categories

Resources