Database Develop

cyanogenmod 4.1.99 support line for installation issues

ok due to the massive number of people clogging the offical thread im starting this thread just to help some of our newer members get working. anyone with a proper working install can help as well. let the issues begin.

i have no data connection at all i have installed 1.6 from htc and then 4.1.99. I even went back and wiped and reinstalled both rebooted and still no connection (3g or 2g).
any ideas

when you signed into google did it work or say cant connect?

Ok here's a question. I was running 4.1.11 which was running fine. I downloaded the recovery image & flashed it thru the recovery console (home + power) and then tried to flash 4.1.99 & now when i try going into the recovery console, I get the Exclamation point with the phone on its side. If i let it power thru it loads up, but like its stock.
I even tried terminal emulation & can't even get the SU command to work.
Any suggestions besides, re-rooting?

This is what I did
Okay, let me start off by saying I have had none of the lag a lot of the people are reporting. So I figured I would post how I installed step by step just incase it helps someone.
Step 1: Download the HTC rom and Cyanogen rom.
Step 2: Reboot into recovery.
Step 3: Flash the HTC update from recovery and let it finish ( it will do the radio as well) the phone will reboot back into recovery by itself.
Step 4: Wipe.
Step 5: Flash the Cyanogen update.
Step 6: Enjoy.
Don't think it would make any diff but just incase, I came from JACxHEROSkiv2.2 and cm 1.4 recovery.
Hope this helps in any way.

yes the same thing happened to me. its very simple too. just fastboot cyanogens recovery.img
http://forum.xda-developers.com/showthread.php?p=3915123
heres fastboot stuff
http://forum.xda-developers.com/showthread.php?t=502010
then flash newest cyanogens like normal and wipe afterwards.

Whenever I follow the steps, the rom is unusuable. This is both before and after a wipe. Everything slows down and crashes. It won't even boot fully, because the launcher has issues. I don't know what to do. Any suggestions? Im about to wipe my EXT3 partition

Every time I try updating to 4.1.99 It stays on the g1 screen.

persiansown said:
Whenever I follow the steps, the rom is unusuable. This is both before and after a wipe. Everything slows down and crashes. It won't even boot fully, because the launcher has issues. I don't know what to do. Any suggestions? Im about to wipe my EXT3 partition
Click to expand...
Click to collapse
try wiping your ext3 however please note alot is going on first boot. i didnt have any issues with slow but i wiped my ext3 and data(wipe in recovery) slow downs are caused mostly by missing or incompatible issues. thats why wiping is recommended. try wiping ext3 and start from scratch. its worth it.

10-05 05:16:25.477: INFO//system/xbin/busybox(49): +++ Apps-to-SD successfully enabled
10-05 05:16:25.517: INFO//system/xbin/busybox(49): /system/etc/init.d/05userinit: 14: Syntax error: "fi" unexpected (expecting "then")
10-05 05:16:25.517: INFO//system/xbin/busybox(49): run-parts: /system/etc/init.d/05userinit exited with code 2

jeremycool said:
Every time I try updating to 4.1.99 It stays on the g1 screen.
Click to expand...
Click to collapse
did you flash the adp image first?

mormo said:
10-05 05:16:25.477: INFO//system/xbin/busybox(49): +++ Apps-to-SD successfully enabled
10-05 05:16:25.517: INFO//system/xbin/busybox(49): /system/etc/init.d/05userinit: 14: Syntax error: "fi" unexpected (expecting "then")
10-05 05:16:25.517: INFO//system/xbin/busybox(49): run-parts: /system/etc/init.d/05userinit exited with code 2
Click to expand...
Click to collapse
check your md5s on both and start from scratch.

Here's what I did:
1. Wipe.
2. Delete all your EXT partition stuff.
3. Reboot into recovery.
4. Flashed the HTC update from recovery. I did NOT reboot after this finished.
5. Flashed the Cyanogen update.
6. Rebooted and waited for the post flashing process to finish.
I had one single FC at the beginning but now it's all good.
If you are not clearing out your dalvik cache and all your other EXT stuff AND wiping, then it's only not working because you didn't do those things.

yes both ways work. however if you have issues try letting the radio install. ONLY if you have issues.

here's a question:
Why are some how to's telling you to flash the 2 files and simply fix permissions while others are saying you need to wipe? it seem like some are running fine without the wipe.
Also, did this myself without wiping and getting google fc at reboot. I've been reading these threads for like 2 hours now and i was under the impression the market, etc. would still work but it's backing out of the white screen and not loading it up. Is that my only option is to do a wipe now? And if i wipe, do i need to reflash anything?
Big thanks to cyan and everyone else for so much help! thank guys!

the reason some people have to let the radio flash is due to either a bad flash. corrupted install or some other reason. every new version come with a new radio and it will sometimes delete your recovery. this is because certain older setup are different and not very consistant. however things happen and some stuff gets messed up. every dream is the same and this software is the same. but you are the different part.

damngood98 said:
here's a question:
Why are some how to's telling you to flash the 2 files and simply fix permissions while others are saying you need to wipe? it seem like some are running fine without the wipe.
Also, did this myself without wiping and getting google fc at reboot. Is that my only option is to do a wipe now? And if i wipe, do i need to reflash anything?
Big thanks to cyan and everyone else for so much help! thank guys!
Click to expand...
Click to collapse
wipe is to fix an issue with google apps. as well as if you had something before causing issues.

damngood98 said:
Also, did this myself without wiping and getting google fc at reboot. Is that my only option is to do a wipe now? And if i wipe, do i need to reflash anything?
Click to expand...
Click to collapse
Not sure if it is your only option, but it might help. And no you will not need to flash anything afterwards.

jokersax11 said:
wipe is to fix an issue with google apps. as well as if you had something before causing issues.
Click to expand...
Click to collapse
damn! gonna go bed and maybe pout for a bit tomorrow before i do another wipe. I hate wiping!
thanks for help joker!

damngood98 said:
here's a question:
Why are some how to's telling you to flash the 2 files and simply fix permissions while others are saying you need to wipe? it seem like some are running fine without the wipe.
Also, did this myself without wiping and getting google fc at reboot. I've been reading these threads for like 2 hours now and i was under the impression the market, etc. would still work but it's backing out of the white screen and not loading it up. Is that my only option is to do a wipe now? And if i wipe, do i need to reflash anything?
Big thanks to cyan and everyone else for so much help! thank guys!
Click to expand...
Click to collapse
Look at it this way...
You moved into a new place and the last tenant was evicted. He left all his crap lying around (mostly trash and dirty laundry.)
Do you sweep the rooms and take out the trash and call it a day? Or do you clean the whole house first? Technically, taking the trash should be enough (laundry included) but you never know what else is hiding in the house (maybe he had a pet tarrantula and it's walking around unbeknown to you. Eventually, you'll run into it and force close yourself in shock.

[Q] After CWM backup system reboots back into CWM

I booted into Clockworkmod Recovery (3.0.0.5) and did a successful backup but when I REBOOT after it is complete it keeps going back into the recovery screen again.
This is driving me nuts. This was a brand new (received today) NC rooted with Auto-Nooter 3.0. I set it up the way I wanted it then did a full backup. Now I can't get out of the backup screen after a reboot.
How can I fix this so I can get back into the O/S?

This happened to me too. I'm still new and dont know why there are specific versions of CWR for specific ROMs... Or why the same version of CWR cannot restore its own backup.
But reinstalling http://forum.xda-developers.com/showthread.php?t=947071 via a sdcard image worked. If your nandroid/cwr backup does not work I hope you have a titanium backup.

MisterEdF said:
I booted into Clockworkmod Recovery (3.0.0.5) and did a successful backup but when I REBOOT after it is complete it keeps going back into the recovery screen again.
This is driving me nuts. This was a brand new (received today) NC rooted with Auto-Nooter 3.0. I set it up the way I wanted it then did a full backup. Now I can't get out of the backup screen after a reboot.
How can I fix this so I can get back into the O/S?
Click to expand...
Click to collapse
Place the file I attached in root of your SDCard and run it from CWR and it will remove CWR and restore you to Autonooter 3.0.0
Apparently CWR has issues with 1.1.0 ROM. This worked for me, when I had the very same issue. I wish I could find the original post I got this from so I could give them the credit.

http://forum.xda-developers.com/showthread.php?t=914690
Ok, this is where I originally got the cwr-removal.zip file, author was samuelhalff
migrax

Same thing happened to mine i ended usinthe removal tool and clearing the cach and then reinstalling the stock zip. I probably spent a good 3 hours figuring it out.
Sent from my LogicPD Zoom2 using XDA App

Rooted Stock boot loop

Hi all,
I have run into one issue on my nook. I have had it for a while and followed all the directions for root and it was running perfect. One day it rebooted and would nver start back up. It gets stuck in the Nook Color Devs Boot Loop where it says Nook, then color in a rainbow scheme. I attempted to reload the factory image, ran the first manual nooter and logged into gmail, etc. Then I ran the second nooter and now I am stuck in a boot loop again. Is there anyway to solve this?
A factory reset appears to help but as soon as I root, the same thing happens. I have attempted to search but couldn't find anything else.
I also found out that if I clear dalvik and cache then it won't go immediately to the boot loop. It attempts to load but i am not sure what to do.
Thanks all.

You may want to specify which version of Stock you're reloading. I don't know for sure, but there may be some different procedures if you're on 1.3... But I don't know, just a tip for people to give you more specific help.

Thank you. This has happened to me on both the1.2 and 1.3 stock rom. It actually just shut off one day and then started doing this.

I'm not very familiar with the stock rom. I got rid of it within like 10 minutes of getting my nook, turning it into a tablet was my whole reason for buying one.
I didn't think there was more than one root script that you had to run though. At least not for 1.2, I dunno about 1.3 though.
Perhaps something there's messing it up?
Personally, I would suggest following one of the threads about restoring to stock... step by step and see if that helps.
http://forum.xda-developers.com/showthread.php?p=13198961#post13198961
Basically... just make a bootable cwm card. Make a backup of what you have atm. Copy the zip you download from that thread to your card. Boot your cwm card and goto mounts and storage, and format: /system, /data, /cache, and I would do /boot just in case. Normally, you shouldn't format boot... but just in case something there is causing you a problem it might be best. I know the stock rom restores the boot files anyway. Then just go to (sorry if the wording here isn't right, I don't have my nook in front of me) install zip from card, then select zip, and choose the 1.2 zip you put on the card. It should take like 5-10 mins to flash... remove the bootable sdcard, and choose reboot now. This should get you back to 100% stock 1.2, then you can retry rooting it... I think 1.2 needs the manual nooter script. You shouldn't have to run anything more than once to root it though, unless you upgrade after that to 1.3.

I had the same problem after getting the 1.3 update and re-rooting. The problem was adobe flash 10.3. I ran flashplayer_fix.zip from GMPOWER's post on this page (sorry don't know how to link the post) and it fixed the problem.
http://forum.xda-developers.com/showthread.php?t=1208896#

I had the same problem after getting the 1.3 update and re-rooting. The problem was adobe flash 10.3. I ran flashplayer_fix.zip from GMPOWER's post on this page (sorry don't know how to link the post) and it fixed the problem.
http://forum.xda-developers.com/showthread.php?t=1208896#

[Q] SafeStrap not flashing roms correctly

So I've followed all the tutorials I could find. I've rooted, installed busybox (to make sure it really existed), installed safestrap (the official one from the blog) and can get into recovery just fine. I made sure I have the right phone version and I've never done any kind of bootstrap stuff on this phone before this.
However, when I switch to safe mode to try out some roms, it simply will not work. I've tried all three versions of Eclipse and one CM9 version, but once supposedly done flashing and told to reboot, it gets a blackscreen for a few seconds and restarts back to the dual-core pre-recovery screen. I've wiped, wiped, super wiped everything just like the various instructions tell me to, but nothing ever changes the blackscreen.
Switching it back to non-safe and rebooting works just fine, but I cannot get any custom safe-mode roms to boot up. Is there something else I should be doing that I missed?

I occasionally have issues with Safestrap when you choose to reboot, so I just power off and then power on - that always works. Initial boots do take some time, though more than a few minutes without animation is probably too much.
And, just to clarify, this is the Safestrap that I use: http://blog.hash-of-codes.com/downloads/safestrap/

But it's not that it takes time, it reboots the phone itself. It's not locking up like I've seen others say and requiring a battery pull. It just refuses to go on, instead more like a boot loop? But nothing appears to be going wrong and I can easily switch back to the base no-problem.
And yeah, that's the same one I'm using. Droid 3 v1.08 exactly from that site.
It's making me sad that I can't get this going
Edit: I went ahead and tried just powering it off, leaving it for a moment, and turning it back on. Still did the reboot thing

are you installing the rom and then wiping data?
if so try wiping data first then install rom then reboot..

ovelayer said:
are you installing the rom and then wiping data?
if so try wiping data first then install rom then reboot..
Click to expand...
Click to collapse
Yeah, tried both ways. Wipe data/factory and cache numerous times, install, nothing. Install then wipe, nothing. Wipe, install, wipe, nothing.
Is there an easy way to know for sure if it is even installing anything at all, like navigating to it using a root explorer?

Are you sure that the zip files you are loading are complete downloads? Generally you would receive error messages when installing if so, but you can try unzipping on your computer to see if they have errors. I always download ROM zips on my computer and transfer over (usually using the Dropbox app, but only because I don't want to bother with attaching, choosing USB storage mode, copying the files, unmounting the drives, choosing charge only.) But, if you are downloading the zips with your phone, try doing so instead with your computer, check the files sizes, and then transfer them over to the phone.
(Also, most/all/many of the CM9 zips require flashing a Google apps zip after flashing the ROM. That shouldn't prevent the phone from starting if you skip this step, but it will prevent you from having the market. Just FYI.)
I'd also try Maverick ROM to see if it has the same problem.
I've been running the stock 906 based ROM from Q9Nap here (the one marked Safestrap system), debloated by Pete Souza's script: http://forum.xda-developers.com/showthread.php?t=1554916

doogald said:
Are you sure that the zip files you are loading are complete downloads? Generally you would receive error messages when installing if so, but you can try unzipping on your computer to see if they have errors. I always download ROM zips on my computer and transfer over (usually using the Dropbox app, but only because I don't want to bother with attaching, choosing USB storage mode, copying the files, unmounting the drives, choosing charge only.) But, if you are downloading the zips with your phone, try doing so instead with your computer, check the files sizes, and then transfer them over to the phone.
(Also, most/all/many of the CM9 zips require flashing a Google apps zip after flashing the ROM. That shouldn't prevent the phone from starting if you skip this step, but it will prevent you from having the market. Just FYI.)
I'd also try Maverick ROM to see if it has the same problem.
I've been running the stock 906 based ROM from Q9Nap here (the one marked Safestrap system), debloated by Pete Souza's script: "no linkies for me"
Click to expand...
Click to collapse
I did as you suggested and tried unzipping the files on my computer (which was where I original downloaded them). They all unzipped fine without any errors, unfortunately. The chances of 4 full files being that way were slim, but I sorta hoped...
I'll try Maverick and the Safestrap stock after I get done downloading them.
Thanks everyone for trying to help.
Edit: Alright, I tried Maverick and it showed a prettier flash log, symlinked, all that, still reset itself after passing the recovery splash. Same with the 906 stock based. This time I also tried installing from internal and external SD just to test that.
I'll ask again, is there a specific folder I can get to just for my peace of mind where I can see where it is supposed to have installed these? Or is it in a area where a normal root explorer can't get to?

shinseitom said:
I did as you suggested and tried unzipping the files on my computer (which was where I original downloaded them). They all unzipped fine without any errors, unfortunately. The chances of 4 full files being that way were slim, but I sorta hoped...
I'll try Maverick and the Safestrap stock after I get done downloading them.
Thanks everyone for trying to help.
Edit: Alright, I tried Maverick and it showed a prettier flash log, symlinked, all that, still reset itself after passing the recovery splash. Same with the 906 stock based. This time I also tried installing from internal and external SD just to test that.
I'll ask again, is there a specific folder I can get to just for my peace of mind where I can see where it is supposed to have installed these? Or is it in a area where a normal root explorer can't get to?
Click to expand...
Click to collapse
wait a sec..
you unzipped them?
the zip files are not ment to be unzipped..
download the zip to your phone
go into safestrap and choose install zip then choose the zip
oh wait...duh you were just checking to see if they worked lol
use root explorer and navigate to system folder open the build.prop and see if there is a mention of the rom your trying to install..ie..version=mavrick or eclipse

I'm not finding any references to other roms anywhere in it. I did a search by eye, then a search for "version", "cm", and "mav" and didn't come up with anything relevant. Is that bad?

There are two other things that you can try, though I am not sure that they will help:
1. From non-safe, stock, run Safestrap and uninstall recovery. Restart to see that it does not intercept before the boot screen, then go back in and reinstall recovery from safestrap. Restart the phone to see if it is working. Then restart to Safestrap and try toggling safe mode and see if your flashes work.
2. One other thing to try (not sure if this will help, but...) is to (prior to flashing a ROM) go into the Mounts menu and format /system. Maybe the old system isn't being cleared out by the ROMs you are trying to flash? Then go install the zip, do a wipe data/factory reset and see if that works.

Just wondering if there is a benefit to Safestrap or Bootstrap and why?
I went with Safestrap... Is it just a style thing or is one better?

Not trying to be a jerk, but I have been scanning this post.
Any chance you have overlooked the step of "Toggle Safe System" from the recovery menu?
At the top of the menu it should say "Safe System is: Enabled"

Droidlyen said:
Just wondering if there is a benefit to Safestrap or Bootstrap and why?
I went with Safestrap... Is it just a style thing or is one better?
Click to expand...
Click to collapse
Safestrap is supposed to allow you to install a rom onto a safe "partition" of sorts, though that's not really what's going on. Anyway, it doesn't touch your stock rom so if something fails (like my flashing attempts) you're not in trouble.
SteveHebe said:
Not trying to be a jerk, but I have been scanning this post.
Any chance you have overlooked the step of "Toggle Safe System" from the recovery menu?
At the top of the menu it should say "Safe System is: Enabled"
Click to expand...
Click to collapse
Nah, I switch it every time. I'm not quite messing up that bad
Anyway, I might have to resort to bootstrap to see if that works. If not, well, I guess I'll be stuck on stock. Nothing so far mentioned in the thread has worked for me. Kinda sucks, since I have an Infuse that loves being flashed with anything I want to put on it without problems, unlike a friend's Infuse. Maybe its phone karma.

[Q] [URGENT] Need Help For my DEAD TF701

I recently changed back my build.prop to the original one that i backed up before. Then my device cannot boot anymore. It is stuck in the ASUS splash screen when i boot the device.
Then I flash the latest CWM recovery. But even the latest version it cannot do anything like factory reset or flash zip.
After that, i tried to use the "wipe data" in the bootloader, it doesn't work either (still stuck in the splash screen).
And then i tried cold boot linux and it also doesn't work. Up to this point, I cannot find anyway to fix it.
However, I found that adb is somewhat working in CWM recovery. I tried "adb push build.prop /system/build.prop" (the build.prop is extracted from the US_epaduser_10_26_1_7_UpdateLauncher.zip package from ASUS official site), it doesn't work either.
I put the US_epaduser_10_26_1_7_UpdateLauncher.zip package from asus support site in sd card and tried to flash it by CWM recovery, it doesn't work either.
AFTER ALL THESE PROCEDURE, i think the system is corrupted because of some possible dirty wipe
IS THERE ANY WAY TO WIPE EVERYTHING AND RESET THE whOLE SYSTEM?
i feel like my device is completely dead... so i need help and solution asap
my device is unlocked, rooted, and updated to 10.26.1.7 android 4.3.
it is a US version.
btw i asked ASUS support and they said they would charge CAN$330 for fixing it (replacing the main board), which is.........

bruce2662 said:
I recently changed back my build.prop to the original one that i backed up before. Then my device cannot boot anymore. It is stuck in the ASUS splash screen when i boot the device.
Then I flash the latest CWM recovery. But even the latest version it cannot do anything like factory reset or flash zip.
After that, i tried to use the "wipe data" in the bootloader, it doesn't work either (still stuck in the splash screen).
And then i tried cold boot linux and it also doesn't work. Up to this point, I cannot find anyway to fix it.
However, I found that adb is somewhat working in CWM recovery. I tried "adb push build.prop /system/build.prop" (the build.prop is extracted from the US_epaduser_10_26_1_7_UpdateLauncher.zip package from ASUS official site), it doesn't work either.
I put the US_epaduser_10_26_1_7_UpdateLauncher.zip package from asus support site in sd card and tried to flash it by CWM recovery, it doesn't work either.
AFTER ALL THESE PROCEDURE, i think the system is corrupted because of some possible dirty wipe
IS THERE ANY WAY TO WIPE EVERYTHING AND RESET THE whOLE SYSTEM?
i feel like my device is completely dead... so i need help and solution asap
my device is unlocked, rooted, and updated to 10.26.1.7 android 4.3.
it is a US version.
btw i asked ASUS support and they said they would charge CAN$330 for fixing it (replacing the main board), which is.........
Click to expand...
Click to collapse
Since it seems that cwm works did you make nandroid backup before you started fiddling with the Rom? ( basic rule nr.1)
When not go to the boot loader screen and do a factory reset there (third icon from left).
But maybe you can do that also from within cwm but I do not know if it is in there.
The official update zip you must unzip that first and then put the new zip on the sdcard, can't do that from cwm.
Let it reboot and it must start flashing.

Snah001 said:
Since it seems that cwm works did you make nandroid backup before you started fiddling with the Rom? ( basic rule nr.1)
When not go to the boot loader screen and do a factory reset there (third icon from left).
But maybe you can do that also from within cwm but I do not know if it is in there.
The official update zip you must unzip that first and then put the new zip on the sdcard, can't do that from cwm.
Let it reboot and it must start flashing.
Click to expand...
Click to collapse
So is there any ways to fix it without sending it to asus repair ccenter?
I want to make sure that
1. The wipe data function in the bootloader works
2. Does wiping data in bootloader fix the build.prop problem
Or do anyone of you have any idea of solving tthis problem?
sorry for my bad english

bruce2662 said:
So is there any ways to fix it without sending it to asus repair ccenter?
I want to make sure that
1. The wipe data function in the bootloader works
2. Does wiping data in bootloader fix the build.prop problem
Or do anyone of you have any idea of solving tthis problem?
sorry for my bad english
Click to expand...
Click to collapse
Wipe data is like factory reset.
Unzip the firmware package and put the zip on your microSD. Then reboot and let it flash.
This way you get all a clean fresh install

Snah001 said:
Wipe data is like factory reset.
Click to expand...
Click to collapse
Sorry to disagree..
I would NOT wipe from the bootloader with a custom recovery installed! People have hard bricked their tablets that way!
Unzip the firmware package and put the zip on your microSD. Then reboot and let it flash.
This way you get all a clean fresh install
Click to expand...
Click to collapse
That works only with the stock recovery, not with a custom recovery. But you should be able to flash the once unzipped firmware in CWM. That would flash you back to stock, including the stock recovery.
Next time you install CWM your first action should be to make a nandroid.
If it doesn't work please explain why and what. Just "doesn't work" is not helpful - do you get error messages?
Explain - in detail - your steps.
Since you said you flashed CWM you do have fastboot access?

Forgot that you aren't on stock recovery.
When you still get into the recovery did you unzip the factory firmware zip before you tried to flash it?
First give that a try.
Volume-up + power pressed normally would get you into apx mode but since we have no Nvflash files available you can't do anything with that.
So unpack and put the factory firmware zip on you sdcard and flash from custom (think you have cwm installed) recovery (choose install and choose the file you put on your microSdcard).

Del msg

Hi I got an issue today with my TF701T can anyone help.
I got a prompt for installing an update, downloaded it, installed and on reboot the TF701T is stuck on the ASUS Splash screen.
How do you reset this device? I'm new to this TF701T

ToneyEricsson said:
Hi I got an issue today with my TF701T can anyone help.
I got a prompt for installing an update, downloaded it, installed and on reboot the TF701T is stuck on the ASUS Splash screen.
How do you reset this device? I'm new to this TF701T
Click to expand...
Click to collapse
There are a number of users with the same issue. Asus seems to have pushed an incompatible update to WW users (Man! They are really scre*** the release of this device! Unbelievable...)
Head over to the General section, there are a couple of threads dealing with this issue. The fix seems to be to wipe data and manually re-install the 10.26.1.7. (and ignore the update notifications you'll get again!)
But read the threads before you do so...

berndblb said:
There are a number of users with the same issue. Asus seems to have pushed an incompatible update to WW users (Man! They are really scre*** the release of this device! Unbelievable...)
Head over to the General section, there are a couple of threads dealing with this issue. The fix seems to be to wipe data and manually re-install the 10.26.1.7. (and ignore the update notifications you'll get again!)
But read the threads before you do so...
Click to expand...
Click to collapse
Sure buddy I will be reading xda before installing any updates from now on!!! Thats really bad ASUS pushed this update out that gets owners of the TF701T stuck on the Splash Screen after updating.

ToneyEricsson said:
Sure buddy I will be reading xda before installing any updates from now on!!! Thats really bad ASUS pushed this update out that gets owners of the TF701T stuck on the Splash Screen after updating.
Click to expand...
Click to collapse
Haha funny :cyclops:, same problem for the UK devices too (i see you´re from London?)? OMG!
I´m a german user and a bunch of peopole here also had this kind of issue after they did the last update from 4.3 to any newer release, since 27th dezember 2013 there´s no valid reply from ASUS and (for my understanding) the invalid software update is still on the servers and get sent to the EU users (...).
@ XDA: do you know, where i could find out the local storage where on my device the *.zip (or what ever) is saved, so that i could manually delete it? To make sure i´ll receive a newer one in future? Or did this (incorrect 250,8MB file) will be replaced by the newer one?
Regards
Silver

Try the root of your internal sdcard or in the download folder.
Sent from my Asus Infinity TF700 with Dock

where can i delete this file
Hi guys,
i've got the same issue, sent the device to the service and replaced a part of it, but because they've went over the 15 days period where they should have send it back ( fixed or not) I got a new one.
i updated to 4.3 and this time again i got prompted to install the crap update, but i didn't. Now i want to delete this file but i can't find it. if my kid or someone else will accidentally say OK to the update i'm back to older version ( at the best) .
so will be highly appreciated if anybody will provide a solution to remove this file.
thx
Snah001 said:
Try the root of your internal sdcard or in the download folder.
Sent from my Asus Infinity TF700 with Dock
Click to expand...
Click to collapse

xistentz said:
Hi guys,
i've got the same issue, sent the device to the service and replaced a part of it, but because they've went over the 15 days period where they should have send it back ( fixed or not) I got a new one.
i updated to 4.3 and this time again i got prompted to install the crap update, but i didn't. Now i want to delete this file but i can't find it. if my kid or someone else will accidentally say OK to the update i'm back to older version ( at the best) .
so will be highly appreciated if anybody will provide a solution to remove this file.
thx
Click to expand...
Click to collapse
It'll be on the cache partition, which you can only access from the stock recovery - you'll need to boot to nthe boot loader, choose rck and mess around with power and volume up / down until the menu appears. Then choose wipe cache. But it will come back when you next check for an update......