Database Develop

Requesting Cyanogen Upgrade Help

Hello all, I have a friend with a G1 that is currently running Cyanogen 4.0.4. He is interested in updating to the latest stable release, but has had trouble booting after he does. Since I have no experience with the G1 or Android in general, I was hoping someone might be able to walk us through the process.
I know his phone is rooted, but I'm not sure what he used to do so. I also think he could probably use a radio update.
Thanks for your time!

xiton said:
Hello all, I have a friend with a G1 that is currently running Cyanogen 4.0.4. He is interested in updating to the latest stable release, but has had trouble booting after he does. Since I have no experience with the G1 or Android in general, I was hoping someone might be able to walk us through the process.
I know his phone is rooted, but I'm not sure what he used to do so. I also think he could probably use a radio update.
Thanks for your time!
Click to expand...
Click to collapse
This link provides all the steps needed to upgrade from 4.0.4 to the current release
http://wiki.cyanogenmod.com/index.p...version_less_than_4.1.99_or_other_rooted_ROMs

Download the Android 1.6 Recovery Image (it has "-ota-" in the filename):
http://www.4shared.com/file/164243978/15081498/signed-dream_devphone_userdebu.html
Download the latest CyanogenMod ROM for your device:
http://n0rp.chemlab.org/android/upda...7.1-signed.zip
1) Hold power and turn the phone off
2) Start up in recovery mode by holding home and pressing power.
3) You are now in recovery mode.
4) Press Alt-W to wipe all data
5) Press Alt-A to apply any zip from sd
6) Choose signed-dream_devphone_userdebug-ota-14721.zip (You won't see the entire filename)
7) When it is done it will ask you to reboot to complete the installation. Press Home+Back
8) You will be returned to the recovery screen in a few minutes, be patient.
9) Press Alt-A to apply any zip from sd
10) Choose update-cm-4.2.7.1-signed.zip
11) After the update is complete, hold Home and press Back to restart. (May take up to 15 minutes to boot)
12) Complete the setup process

i have looked everywhere (i think) for signed-dream_devphone_userdebug-ota-14721.zip Where did it go... i'm also on 4.0.4 and want all the googly goodness if you have- or- can find a link?? thanks so much. i've learned alot from u guys, sorry for not posting

Found a mirror using the Google (real complicated stuff, not recommended for beginners)
http://pomac.netswarm.net/mirror.html/mirror/android/adp1/android-1.6
It has both
signed-dream_devphone_userdebug-img-14721.zip
&
signed-dream_devphone_userdebug-ota-14721.zip

yozpalang said:
Download the Android 1.6 Recovery Image (it has "-ota-" in the filename):
http://www.4shared.com/file/164243978/15081498/signed-dream_devphone_userdebu.html
Download the latest CyanogenMod ROM for your device:
http://n0rp.chemlab.org/android/upda...7.1-signed.zip
1) Hold power and turn the phone off
2) Start up in recovery mode by holding home and pressing power.
3) You are now in recovery mode.
4) Press Alt-W to wipe all data
5) Press Alt-A to apply any zip from sd
6) Choose signed-dream_devphone_userdebug-ota-14721.zip (You won't see the entire filename)
7) When it is done it will ask you to reboot to complete the installation. Press Home+Back
8) You will be returned to the recovery screen in a few minutes, be patient.
9) Press Alt-A to apply any zip from sd
10) Choose update-cm-4.2.7.1-signed.zip
11) After the update is complete, hold Home and press Back to restart. (May take up to 15 minutes to boot)
12) Complete the setup process
Click to expand...
Click to collapse
iirc, his loader only lets you upgrade if you rename the files to update.zip. whats the one you are using that lets you preserve filenames?

xiton said:
iirc, his loader only lets you upgrade if you rename the files to update.zip. whats the one you are using that lets you preserve filenames?
Click to expand...
Click to collapse
If you can only apply "update.zip" you probably want to upgrade the recovery image
What recovery are you on?
Are you sure the phone is rooted and you're not at the stock recovery?
Either way give Cyanogen's Wiki a read, there's a lot more info there
http://wiki.cyanogenmod.com/index.php/Upgrading_From_Older_CyanogenMod_or_other_rooted_ROMs

jackslim said:
If you can only apply "update.zip" you probably want to upgrade the recovery image
What recovery are you on?
Are you sure the phone is rooted and you're not at the stock recovery?
Either way give Cyanogen's Wiki a read, there's a lot more info there
http://wiki.cyanogenmod.com/index.php/Upgrading_From_Older_CyanogenMod_or_other_rooted_ROMs
Click to expand...
Click to collapse
Thanks for all the info. I'm going to forward the info to him, since I'm not sure what he's running atm.

xiton said:
iirc, his loader only lets you upgrade if you rename the files to update.zip. whats the one you are using that lets you preserve filenames?
Click to expand...
Click to collapse
get the CM recovery here the update to this one here then you can apply any zip

yozpalang said:
please don't comment if you don't know what you are talking about
Click to expand...
Click to collapse
That's the OP asking for clarification because he's still lost

jackslim said:
That's the OP asking for clarification because he's still lost
Click to expand...
Click to collapse
sorry ,my bad

Needing some assistance as well.
The steps outlined on Cyanogen's wiki are dead simple. I followed them to the letter (save for installing the Hard SPL).
The problem is when my phone gets to the above listed step 11, it reboots and sits at the T-Mobile G1 logo. This is my second attempt to make the rooting/new mod changes and I let it sit at the logo for over an hour with zero change on the boot screen.
I have already installed the dreaimg.nbh, and I have DL's (3 times fro 2 different sources) the "signed-dream_devphone_userdebug-ota-14721.zip" and the "update-cm-4.2.7.1-signed.zip" and can use the 'apply any zip' option from the recovery menu.
The process itself seems to go fine (i.e. installing/formatting, blah blah blah) but the final reboot does nothing.
So, I am at a loss why apparently installed OS simply will not boot. Odd thing, is that I left my blue tooth headset on by accident and upon the last reboot, I hear it connect! It's almost as if it does boot up but will not change the screen.
I setup a second machine(Karmic Ubuntu) strictly for ADB but haven't the best clue on how to get it to work. While in the recovery menu I can issue "adb shell reboot" and the phone reboots but I cannot get the status. Even when trying "adb usb". Either I get 'device not found' or "connection closed" with either of those commands.(Not recalling which at the moment).
After this 'stuck on G1 logo', I can reboot and 'restore latest backup'(as noted in Cyanogen's steps) and the OS loads (although it is buggy as hell when trying to use any browsing, signal cuts in and out, drops carrier and gets it back.....severely annoying)
So....could use some real guidance.
As it stands:
OS: kila-user 1.0 TC4-RC29 115247 ota-rel-keys, release-keys
Recovery menu shows "Build: CyanogenMod v1.4 + JF" at the bottom.
Where to go from here?

[Q] N1 in trouble! Please help

Hi guys...
First off, i'm somewhat of a noob. Got my N1 already rooted a few months back but i've tried many different ROM's since. I'm using Clockworkmod Recovery.
I was running Cyanogen 6.1 yesterday and wanted to create a backup of stock froyo for gingerbread's release.
So, i did a backup of Cyan 6.1 and followed the following steps off Android Central's forum.
Step One
Download this file. It's the flashable, stand alone version of FRG33.
You can't go straight back to FRG83 using this method. Just trust us.
Place the PASSIMG.zip file on the root of your SD card.
Power off your Nexus One, then hold volume down while pressing the power button.
Your phone will spend a minute or so looking for an update file (the PASSIMG.zip file).
When it has the info it needs, it will ask if you would like to install it. Press the volume up key to choose to install the file.
Your Nexus One will take another few minutes installing the update, then it will reboot.
Let it reboot the whole way, then go on to step two.
Step two is for the update to FRG83 which i did.
The phone boots and runs fine...
But ever since I did all that, my N1 looks like its unrooted. I can't use ROM manager, Titanium backup to restore since they all tell me they don't have su rights. I installed Superuser from the market. It opens but does nothing with my app's rights.
adb can't find my device when I try to list it (adb devices). Neither can Fastboot (fastboot devices), in fastboot mode.
I see the padlock at boot
I can't go into recovery. I get the robot with an exclamation mark. If i hit the power and vol-up I get the android system recovery menu (in blue) with only 4 options; reboot, apply sdcard:update.zip, wipe data/factory reset and wipe cache partition.
I've tried rooting it with Universal Androot but it failed.
I've no idea where to go from there...
Please help!

You have to root again. Use the rageagainstthecage exploit.
Sent from my Nexus One using XDA App

Ok... N1 is rooted using VISIONary.
However, I can't boot into recovery mode (clockworkmod). I still get the exclamation mark.
If I try to use adb, i always get an error: device not found.
If I try to unlock with fastboot oem unlock, i get a waiting for device message but it never finds anything....
Almost there... i think!

Ok... using Clockworkmod, flashed recovery and all is good!
Thanks for your help!

HELP!! my fone wont go on recovery and everything else is acting WIERD!!!

Just to make the long story short!..I am not too familiar with the android interface and I bought my nexus one (second hand ROOTED) I wanted to try on the rodrigoes MIUI
What I did exactly:
first thing I did a nandroid backup of my fone, then I went to the recovery mode and did a factory reset on the fone.. once that was done, I then did a restore the back up. Here is the problem now....
once the back up was running...it was stuck on this one file for the longest time (about 40-50 mins) I dont know why but I took off the battery and rebooted again...I now have a slow working fone... with most of my apps not working!!! IT WONT GO TO RECOVERY MODE!!!! even my rom manage wont let me do anything...it gives me a error message or hangs up on that screen...should I format my sd??...
Can someone please tell me the step to get my fone back to working condition. I dont mind wiping my fone entirely and starting all over again..and can you also recommend what MIUI should i install (fast and stable) right now i have no preferences.. I JUST WANT MY FONE WORKING BACK !!!
Any help would be greatly appreciated!!!
Thanks

Quick and easy option.
Download: http://shipped-roms.com/shipped/Pas...le_WWE_2.16.1700.1_FRG33_MFG_Shipment_ROM.zip
Extract the zip file from it, and rename it passimg.zip. Copy that file to the root of your SD card.
Power the phone off, hold Vol- and turn it on, it will prompt you to install the file, choose yes.
Your phone will be back to stock and away you go.

Rusty! said:
Quick and easy option.
Download: http://shipped-roms.com/shipped/Pas...le_WWE_2.16.1700.1_FRG33_MFG_Shipment_ROM.zip
Extract the zip file from it, and rename it passimg.zip. Copy that file to the root of your SD card.
Power the phone off, hold Vol- and turn it on, it will prompt you to install the file, choose yes.
Your phone will be back to stock and away you go.
Click to expand...
Click to collapse
Thanks buddy!!! you got my fone up and running!!! thnaks a ton!
Ok so I now am running FRG33 and i formatted my sd card too...I wanted to root my phone now... do u recommend using a build number before I root iit, because i cant find the fastboot for FRG33..

FRG33 is an odd build, you should get an OTA update to FRG83D at some point, I'd wait till then as your root access will be lost when you get it.
Or you can manually do it, takes two steps. Download this: http://shipped-roms.com/shipped/Pas...RG83 OTA update, possibly from FRF91 too).zip
Rename it to update.zip and copy it to the root of the SD card, boot into recovery (Vol- with power on and pick recovery), open the menu (Power & Vol+ at the warning triangle) and pick install update.
Then download this: http://android.clients.google.com/p...signed-passion-FRG83D-from-FRG83.ecb21b75.zip and repeat the above process. You're now upto date and root away.

Rusty! said:
Power the phone off, hold Vol- and turn it on, it will prompt you to install the file, choose yes.
Your phone will be back to stock and away you go.
Click to expand...
Click to collapse
When the HBOOT starts it loads the passimg.zip automatically and a blue loading bar appears at the top right. After the blue bar became full it disappear and nothing happens.
My phone still hung on the "X" logo and i'm unable to get into recovery and install any update.zip
What can I do?

The file is a zip within a zip, did you extract it first, or just rename the file you downloaded?

Rusty! said:
The file is a zip within a zip, did you extract it first, or just rename the file you downloaded?
Click to expand...
Click to collapse
lol thank you didn't notice it

[Q] Safestrap 3.05 Problem - Stuck in Safe

A couple days ago I decided to load the new Safestrap Hashcode linked to. Everything went very well, and I have been running Maverick 4.5 in slot 2 as my daily driver. I was able to get back into Safestrap using the menu button. I also loaded Gummybear ICS into Slot 3, but went back to Maverick.
Yesterday I was going to go back into Safestrap and switch to the Gummybear/slot 3 rom to check it out.
I can't get back into Safestrap at all. I am stuck in the Maverick 4.5 rom.
One thing I did notice and do not understand: When I use Titanium Backup or the Reboot Widget to "Reboot into Recovery", I get a Yellow Triangle with an Exclamation Mark and the Android guy.

mhelm23 said:
One thing I did notice and do not understand: When I use Titanium Backup or the Reboot Widget to "Reboot into Recovery", I get a Yellow Triangle with an Exclamation Mark and the Android guy.
Click to expand...
Click to collapse
That's the stock Droid 3 recovery. Using a reboot recovery will lead to that, and will not allow Safestrap's bootloader to intercept the boot and activate Safestrap recovery.
I haven't tried running Safestrap 3.05 myself, since it's still not official, but I do know that you cannot reboot recovery as you describe to to get into Safestrap for any version of Safestrap.

mhelm23 said:
A couple days ago I decided to load the new Safestrap Hashcode linked to. Everything went very well, and I have been running Maverick 4.5 in slot 2 as my daily driver. I was able to get back into Safestrap using the menu button. I also loaded Gummybear ICS into Slot 3, but went back to Maverick.
Yesterday I was going to go back into Safestrap and switch to the Gummybear/slot 3 rom to check it out.
I can't get back into Safestrap at all. I am stuck in the Maverick 4.5 rom.
One thing I did notice and do not understand: When I use Titanium Backup or the Reboot Widget to "Reboot into Recovery", I get a Yellow Triangle with an Exclamation Mark and the Android guy.
Click to expand...
Click to collapse
thats the stock recovery
now. do you still get the boot menu splash page where it asks you to input the menu key or continue?
if so hit the menu many times or hit on the screen the hit menu for recovery image section, as it shoulod also work.
maybe my next question is silly or already tried, but have you tried to try it with the charger disconnected?
some times when my droid 3 is connected, the touch screen gets un responsive o registers more than input
hope this helps

I now have the same problem. I see the splash screen and it vibrates and reacts when I press the menu button, however it does not boot into safestrap v3.05.
From the JB topic it seems more people have this problem!

DoubleYouPee said:
I now have the same problem. I see the splash screen and it vibrates and reacts when I press the menu button, however it does not boot into safestrap v3.05.
From the JB topic it seems more people have this problem!
Click to expand...
Click to collapse
For those with trouble entering recovery with SS 3.05
The EASIEST and most DEPENDABLE way I've found to boot into the new SS 3.05 is;
Shutdown the phone
Slide open keyboard
Hold M and press the power button to boot the phone (still holding M, release when it boots the next step)
Immediately a menu pops up
Press Volume DOWN to highlight "BP Tools" (tap several times, be quick, if you wait too long, it'll automatically select what is highlighted)
Press Volume UP to select it.
Phone will reboot showing the M logo, then proceed into SS Recovery.

Skreelink said:
For those with trouble entering recovery with SS 3.05
The EASIEST and most DEPENDABLE way I've found to boot into the new SS 3.05 is;
Shutdown the phone
Slide open keyboard
Hold M and press the power button to boot the phone (still holding M, release when it boots the next step)
Immediately a menu pops up
Press Volume DOWN to highlight "BP Tools" (tap several times, be quick, if you wait too long, it'll automatically select what is highlighted)
Press Volume UP to select it.
Phone will reboot showing the M logo, then proceed into SS Recovery.
Click to expand...
Click to collapse
This did not work for me. It just hangs on the Motorola splash screen after choosing BP Tools. Just tried a few moments ago.
Also I haven't had my phone plugged in or charging.
Sent from my DROID3 using xda premium

mhelm23 said:
This did not work for me. It just hangs on the Motorola splash screen after choosing BP Tools. Just tried a few moments ago.
Also I haven't had my phone plugged in or charging.
Sent from my DROID3 using xda premium
Click to expand...
Click to collapse
Strange, I have tried it several times... worked each time... maybe try reinstalling safestrap 3.05? Back up what you can of course, stock should not be touched.

Skreelink said:
Strange, I have tried it several times... worked each time... maybe try reinstalling safestrap 3.05? Back up what you can of course, stock should not be touched.
Click to expand...
Click to collapse
Yea - I tried that too. I am really at a loss.
Sent from my DROID3 using xda premium

I am sittin in the same spot. Can't boot into recovery...
Sent from my DROID3 using xda app-developers app

Skreelink said:
For those with trouble entering recovery with SS 3.05
The EASIEST and most DEPENDABLE way I've found to boot into the new SS 3.05 is;
Shutdown the phone
Slide open keyboard
Hold M and press the power button to boot the phone (still holding M, release when it boots the next step)
Immediately a menu pops up
Press Volume DOWN to highlight "BP Tools" (tap several times, be quick, if you wait too long, it'll automatically select what is highlighted)
Press Volume UP to select it.
Phone will reboot showing the M logo, then proceed into SS Recovery.
Click to expand...
Click to collapse
Had this problem today after creating a rom slot and flashing a new rom, this worked for me however I had to try it a few times. Once I got into recovery I wiped the rom and rom slot and ss3 is working properly now. Not sure if this was a rom issue or ss3.
Sent from my DROID3 using XDA

i had the same problem. and a bootloop top...
i have complete install my droid everything is lost...
another question. my "new" droid has the build 860 and withe safetrap i installed 2 other system.
can i update the stock to 906 without loosing safetrap and the 2 new systems?

dabayer said:
i had the same problem. and a bootloop top...
i have complete install my droid everything is lost...
another question. my "new" droid has the build 860 and withe safetrap i installed 2 other system.
can i update the stock to 906 without loosing safetrap and the 2 new systems?
Click to expand...
Click to collapse
When you run the OTA update to 906, it will remove the Safestrap bootstrap and will unroot as well. However, you can reroot with Motofail, then run the Safestrap app again to install recovery, and you slots *should* still be there. Perhaps making a backup of each slot before running the OTA would be smart.

doogald said:
When you run the OTA update to 906, it will remove the Safestrap bootstrap and will unroot as well. However, you can reroot with Motofail, then run the Safestrap app again to install recovery, and you slots *should* still be there. Perhaps making a backup of each slot before running the OTA would be smart.
Click to expand...
Click to collapse
i dont like the word "should"
ok i try to save the files in safetrap and try an OTA. yesterday the ota didn't run but i think i have to wait longer thar it starts the installation than the 10 minutes...

The slots are all stored on the internal storage (the mount point /sdcard) on the phone, so as long as you don't format internal storage, they should stay there.
I should note that I have never tried installing the OTA with safestrap 3.05 installed - I did it with 1.08. Actually, you may want to activate the stock slot, go into the safestrap app and uninstall recovery, and then try running the OTA. It's possible that the OTA will balk with a custom recovery installed - I don't remember, and, like I said, I never tried with Safestrap 3.05 installed.
You can also download the OTA, copy it to an external SD card, and manually run the update from stock recovery. See this thread: http://forum.xda-developers.com/showthread.php?t=1643521
[edit] Sorry - that link is for an update from 890 to 906. I forgot that you were not on 890. Sorry about that...

I had almost the same problem with my phone, the diference is that mine got stuck on non safe system (Stock ROM). Initializing the phone with th Android Recovery (Turning on with the key "m" pressed down) and choosing BP Tools doesn't worked.
- Phone: Milestone 3 XT860 (Brazilian Droid 3)
- Carrier: Vivo
- Current ROM: Stock 2.3.5 - 5.2.440

Massive problem with the tablet

I have spent about 10 hours sitting here, with over 200 tab open trying to find a solution to my problems but I could not find one. My last option is to post here and hope someone can help me out.
I recently bought the tf701t which came with Android 4.2.2. Everything worked fine. A few days ago, I got pushed an update to android 4.3 but it was .1.7 not .1.18 (the newest apparently). With that update, my problems came. When I light up the device by pressing the power button, the lock screen was unresponsive. I pressed my pin numbers in but there was no response and it was as if the touchscreen was broken. However, the home and back button were all working fine. I had to randomly keep pressing until it finally started becoming responsive. When I got in, the quick management window (the one you get by swiping down), kept popping up the moment i press the screen. Because of this, I couldnt do anything. I couldn't even turn off the tablet as the power off option was unable to be pressed by me (When i did press, the window came up again).
After a while, i managed to get around this by again randomly pressing stuff. I got really frustrated and decided maybe if I install a custom rom, this problem might be fixed.
I read around a bit and found that the CROMix rom required firmware 1.18, which I did not have. Because of this, i decided to try install 1.18. First i used the asus unlock tool. Next I tried booting into recovery but here I met my problem. I have guides telling me to first boot using power button + volume down key. This worked. It then told me to choose the RCK option and press the volume up key. This however, did not work. When I selected the RCK option, the android figure appeared lying down with a red triangle and exclamation mark over it.
Unsure of what to do in this situation, i read one of the guides on this forum which said simply place the 1.18 zip file (yes i unziped the zip file from the file i downloaded), in the root folder then reboot and it would automatically update. This didnt happen.
I then tried using the adb thing but it said no devices were connected even when my tf701t was connected to the PC. I guessed that I needed to be in the recovery mode that I could not get into, before it would work.
I then read around and they said I had to first get Rom manager + the CMR recovery thing but Rom Manager said it needed root access. In order to get root access, I needed to get into the recovery mode yet again.
So now I am stuck. Whenever I try the RCK option, the error pops up and I can't get any further.
WIll someone please help me? I have no idea what to do anymore except throw the tablet out.

zhuang281 said:
I have spent about 10 hours sitting here, with over 200 tab open trying to find a solution to my problems but I could not find one. My last option is to post here and hope someone can help me out.
I recently bought the tf701t which came with Android 4.2.2. Everything worked fine. A few days ago, I got pushed an update to android 4.3 but it was .1.7 not .1.18 (the newest apparently). With that update, my problems came. When I light up the device by pressing the power button, the lock screen was unresponsive. I pressed my pin numbers in but there was no response and it was as if the touchscreen was broken. However, the home and back button were all working fine. I had to randomly keep pressing until it finally started becoming responsive. When I got in, the quick management window (the one you get by swiping down), kept popping up the moment i press the screen. Because of this, I couldnt do anything. I couldn't even turn off the tablet as the power off option was unable to be pressed by me (When i did press, the window came up again).
After a while, i managed to get around this by again randomly pressing stuff. I got really frustrated and decided maybe if I install a custom rom, this problem might be fixed.
I read around a bit and found that the CROMix rom required firmware 1.18, which I did not have. Because of this, i decided to try install 1.18. First i used the asus unlock tool. Next I tried booting into recovery but here I met my problem. I have guides telling me to first boot using power button + volume down key. This worked. It then told me to choose the RCK option and press the volume up key. This however, did not work. When I selected the RCK option, the android figure appeared lying down with a red triangle and exclamation mark over it.
Unsure of what to do in this situation, i read one of the guides on this forum which said simply place the 1.18 zip file (yes i unziped the zip file from the file i downloaded), in the root folder then reboot and it would automatically update. This didnt happen.
I then tried using the adb thing but it said no devices were connected even when my tf701t was connected to the PC. I guessed that I needed to be in the recovery mode that I could not get into, before it would work.
I then read around and they said I had to first get Rom manager + the CMR recovery thing but Rom Manager said it needed root access. In order to get root access, I needed to get into the recovery mode yet again.
So now I am stuck. Whenever I try the RCK option, the error pops up and I can't get any further.
WIll someone please help me? I have no idea what to do anymore except throw the tablet out.
Click to expand...
Click to collapse
Did you try to put the update on the external sd card? Not sure if that would make a difference but i remember i used to put it there...
You could also flash a custom recovery and flash the update that way. You can find more info in this thread:
http://forum.xda-developers.com/showthread.php?t=2636093

You should safely be able to update your factory firmware first by putting it at /sdcard location.. Then just reboot. It automatic. I Thought there was also an update available in settings after that. Don't unlock til you are at 4.3.
To unlock with Asus unlock tool make sure Google 2 Step verification is disabled.
Then I used fastboot to flash CWM recovery from a computer. I think you flash with fastboot from the newly unlocked bootloader. Power + Vol DOWN.
After you have flash recovery then you can enter it. No scary man lying down.

YayYouFixedIt said:
You should safely be able to update your factory firmware first by putting it at /sdcard location.. Then just reboot. It automatic. I Thought there was also an update available in settings after that. Don't unlock til you are at 4.3.
Click to expand...
Click to collapse
I forgot to mention one thing at the start. I don't actually have on hand a external microSD card. Which I think might be why placing the zip file in the root of the internal storage did not work.
Should it work? Is there any way to get around it? I've been trying to use sideload with cwm (finally got cwm working), but it comes up with "failed to write data protocol fault no status"
EDIT: Through cwm, I chose "choose zip from /sdcard" then select the "0" file directory then i found my zip at the location. I selected it and confirmed install. However, it then comes up with "Error in data/media/0/(name of update here).zip status 6"
Thanks for the help so far but anyone have an idea about this?

Not sure. After googling I see this
http://forum.xda-developers.com/showthread.php?t=1535546
---------- Post added at 09:54 AM ---------- Previous post was at 09:45 AM ----------
You can put the zips anywhere when your recovery is installed.

Okay so I finally managed to get the custom rom installed and working. However, this did not fix my problem with the touchscreen. I think it is because it only changed the firmware but not the android version (still 4.3).
Is there any place I could find android 4.2.2 rom? This was the one the tablet was on before the update that screwed everything up. If I could downgrade to that version, it may work again.
Thanks
I gave up and just put on the android 4.3 ota from droidbasement. Now the tablet randomly restarts and is stick in reboot loop. It wont even allow me to boot into cwm recovery to delete the cache. But i accept that I now have a $600 piece of **** on my hands. Going to bed. Night.

Ya i dont like the whole void your warranty for "using it" idea. If it responds to fastboot you might be ok.

You should be able to download a 4.2.2 rom from Asus' website (.47 was the last build for 4.2.2). You can use fastboot to install it.

Alta1r said:
You should be able to download a 4.2.2 rom from Asus' website (.47 was the last build for 4.2.2). You can use fastboot to install it.
Click to expand...
Click to collapse
I tried that before but it stated "update aborted" immediately after i pressed confirm, in CWM.
But all that is in the past now. I am pretty sure that the tablet is hard bricked since it no longer even opens bootloader. I accidentally pressed the wipe data option and I read that irreversibly damages the tablet. When I hold pwr+vl down, nothing happens anymore, it keeps on its reboot loop.