Related
Hi folks,
I might have a stupid noob question, but not able to find the answer.
I got a Motorola Xoom (EU), and I did root it the other day.
All working fine.
Now I get update notifications for 3.1, but I'm not able to install the stock update.
After the reboot, the Android logo is showing an error, and then it reboots to normal OS.
Now the question is, all instructions I found so far require an external SD Card to get a custom rom with 3.1/3.2 installed.
Is a SD card required, or can I get the same done via USB debug?
Thanks for looking at this thread.
Regards,
derchris
derchrisuk said:
Hi folks,
I might have a stupid noob question, but not able to find the answer.
I got a Motorola Xoom (EU), and I did root it the other day.
All working fine.
Now I get update notifications for 3.1, but I'm not able to install the stock update.
After the reboot, the Android logo is showing an error, and then it reboots to normal OS.
Now the question is, all instructions I found so far require an external SD Card to get a custom rom with 3.1/3.2 installed.
Is a SD card required, or can I get the same done via USB debug?
Thanks for looking at this thread.
Regards,
derchris
Click to expand...
Click to collapse
You need a custom version of ClockworkMod Recovery made for the Xoom. You can flash the solarnz R4c v3.2.0.0 that does require a micro sdcard (even a 2GB is fine) which will appear at mnt/external1, or you can go with Rogue recovery that will let you flash from internal storage (mnt/sdcard) or other options. It's up to you but you must be able to flash the recovery image file through adb/fastboot, since you can't flash a zip file through fastboot.
Thanks for the reply,
I used this thread to install recovery-Tiamat-R4c-100611-1150-cwm.img, as they had a recovery image file for adb/fastboot.
Looking through the options, I see a "mount USB storage" option, but I ended up in only having a 3 MB drive, and as soon as I exited the menu the drive was gone too.
Do you happen to know a download for an adb/fastboot image of the Rogue Recovery?
I don't have a single SD Card, thats why I would like to use USB or internal memory.
derchrisuk said:
Thanks for the reply,
I used this thread to install recovery-Tiamat-R4c-100611-1150-cwm.img, as they had a recovery image file for adb/fastboot.
Looking through the options, I see a "mount USB storage" option, but I ended up in only having a 3 MB drive, and as soon as I exited the menu the drive was gone too.
Do you happen to know a download for an adb/fastboot image of the Rogue Recovery?
I don't have a single SD Card, thats why I would like to use USB or internal memory.
Click to expand...
Click to collapse
You would have to go to that thread and see if there is an option for initial install via img file. I haven't used Rogue, so I don't know.
I figured it out myself
There was an img file inside the zip, which I was able to flash to the Xoom.
Next I used Tiamat Xoom Rom 2.2.2 "Moray" from the internal memory, and have now 3.2.1 on my Xoom.
Thanks for the help
My pleasure.
I've been having problems with ICS and USB mass storage support, or lack of. Is there anything I can place on my micro SD. then copy it to the internal SD and boot from there?
Just grabbing at straws here!
Thansk
TF101 B50 by the way.
honkinn said:
I've been having problems with ICS and USB mass storage support, or lack of. Is there anything I can place on my micro SD. then copy it to the internal SD and boot from there?
Just grabbing at straws here!
Thansk
TF101 B50 by the way.
Click to expand...
Click to collapse
If you're still able to boot into the OS and is able to R/W files than yes, put the files on the micro sd, and using a file manager transfer it to internal sd.
Thanks for the help, but as a neebie, I need a suggestion on WHAT file to place on the internal SD that will I can boot from.
I still get the robot with the red triangle when I try to boot into recovery. I'm assuming that is because there wasn't a bootable file on the internal SD.
Does that make sense?
honkinn said:
Thanks for the help, but as a neebie, I need a suggestion on WHAT file to place on the internal SD that will I can boot from.
I still get the robot with the red triangle when I try to boot into recovery. I'm assuming that is because there wasn't a bootable file on the internal SD.
Does that make sense?
Click to expand...
Click to collapse
Oh I see you're on stock recovery, is the ROM stock also?
Only thing is download the latest firmware from Asus, extract the zip from within, renamed it EP101_SDUPDATE.zip and put it on the micro sd card. Boot into stock recovery and see if it will flash, maybe that will help get USB working again.
Thanks for the suggestion. I did what you told me and still nothing. When I try to boot into recovery, I still get the dead robot with the red triangle, then it boots stock.
IS there a particular folder on the SD or the Micro Sd I need to put the EP101_SDUPDATE.zip file into?
Is there a specific folder on the Intenal SD that the system boots from, that I could replace the update zip with a before ICS version?
Are these dumb questions?
Thanks in advance for taking the time to help me.
Forgot to mentioned, did you extract the zip from within the file you download?
I did extract the zip and placed it on the micro AND the internal SD in the Android folder.
IS there something else I should be doing?
This is driving me nuts.
Try it in the root of the sd card should automatically detect it there
Going on 2 weeks now
Is anyone else stuck in the situation I am? I cannot re-gain Mass Storage, SD support. When I try to boot into recovery, I get the Robot with the red triangle. The only way I can see my internal SD is through the stock file manager that is on the tablet. I don't know if I can move an appropriate file into a certain folder to get this thing to boot up to where I can reflash a ROM.
What is with this POS? I no longer have CWM and root after the OTA update. I e-mailes ASUS and they gave me the " pull the micro card, then do a wipe and re boot" Which did nothing but waste time. as you can probably tell, I am getting tired of dead ends on this Tf101 B50. does anyone have any idea what could have went wrong with the OTA update? Why did I loose the SD? and What can I do to fix/revert back to an earlier state.
self admitted noobie here...Feel free to kick the **** out of me!
Thanks for your help.
With a B50, see if you can get NVFlash working.
Download the NVFLash package
http://forum.xda-developers.com/showpost.php?p=23222380&postcount=414
Get an NVFLash compatible ROM here
http://forum.xda-developers.com/showthread.php?t=1524302&highlight=nvflash+rom
honkinn said:
Is anyone else stuck in the situation I am? I cannot re-gain Mass Storage, SD support. When I try to boot into recovery, I get the Robot with the red triangle. The only way I can see my internal SD is through the stock file manager that is on the tablet. I don't know if I can move an appropriate file into a certain folder to get this thing to boot up to where I can reflash a ROM.
What is with this POS? I no longer have CWM and root after the OTA update. I e-mailes ASUS and they gave me the " pull the micro card, then do a wipe and re boot" Which did nothing but waste time. as you can probably tell, I am getting tired of dead ends on this Tf101 B50. does anyone have any idea what could have went wrong with the OTA update? Why did I loose the SD? and What can I do to fix/revert back to an earlier state.
self admitted noobie here...Feel free to kick the **** out of me!
Thanks for your help.
Click to expand...
Click to collapse
Sounds like your OTA update was fudged so you need to reflash the ROM. I thought people with root and CWM can't do OTA updates?
Does adb or apx mode work? If apx mode works, then you can NVFlash so it shouldn't be a problem.
If ADB works, you can gain root with vipermod so you can install CWM.
I used to have root access. But, My last flash stuck in boot. Had to Nv flash it back to stock. Then the OTA hit, I had no more root or NVflash. So that is where I am. I hope there is something I can do to fix this.
Thanks for the help
OK lets try this method.
The firmware you download, don't rename it.
On the root of your sd card made a folder name ASUS
inside that make a folder name Update
extract the zip file from inside the download firmware and put it in the Update folder.
Just cold boot the TF and see if you get a notification of update avaiable on the status bar.
Outside of that not sure anything can be done except RMA
So ive been at this for 2 days. I finally got the micro sd card with both files to install rom but in clockworkmod recovery i cant mount sd card nor format or anything. I can mount and unmount in the normal settings of the device and see it in root explorer but thats it. Its formatted to fat32. also on rom manager where it says to install from sdcard it only takes u to the internal sdcard which makes no sense because i was told u cant install a rom from the internal sdcard.
PS. This is my first Android Device!!!!
yeah
I am in the exact same situation. I am rooted on 4.0.3 and I wanted to install 4.0.4 or one of the custom ROM's. This is not my first android device but I am at a loss. I can not enter fastboot, can't load anything from the SD card in CWM recovery (get the message E:Can't mount /sdcard/), can not connect via ADB on my PC.
I feel that I have enough skill to do all of this because I have done it in the past. My ADB works fine with my Galaxy Nexus (just updated that and installed new kernel) so I don't know what is causing the problem. I have tried different SD cards(3) as well and nothing.
The biggest problem is I can not get into fastboot and SBF if I wanted to. I have been having issues with drivers even though I have installed motohelper like 6 million times.
I have tried factory resets and wipes and everything. I tried to do the factory update that is being pushed to me and I get an error. Any help would be greatly appreciated.
Sorry if this is stealing your thread but I think we are having the same problems.
check out my thread at xoomforums:
I PM'd it to u cus it dont let me put it here
Read all 3 pages. I think it will help u. posted same question there and a guy suggested to install the rogue cwm 1.5 recory via adb fastboot or whatever. he says that will read your sdcards. if i were u id try and fastboot on a different pc cus it looks like thats what we both have to do unfortunately. it looks like a pain!!! u have a xoom?
anyone figured out how to sort this?? really frustrating it just sayin E:can't mount sd card.. any help will be appreciated!!
platt said:
anyone figured out how to sort this?? really frustrating it just sayin E:can't mount sd card.. any help will be appreciated!!
Click to expand...
Click to collapse
If you are using CWM recovery from Rom Manager (not recommended for Xoom) it does only read your internal flash memory (called sdcard) but not your external microsd card (called external1???). So you need to flash a different custom recovery using adb/fastboot to flash a recovery.image file or, if you can flash through cwm (from internal sdcard) a recovery.zip file (either EOS or Rogue, depending on the ROM you will flash afterwards), Actually, any custom recovery is supposed to work for any rom, but in reality Eos works best for Eos and Rogue works best for the CM9 Kang.
Please, just remember, never flash a .zip file through fastboot, only an .image file!
+1 i agree with the above, fixed this last night. I download a couple recovery images, which were blank for some reason, so i downloaded the zips and extracted the recovery image folder. Then opened the command window from the folder with the recovery image and flashed it with fastboot. Now it works perfect.
Sent from my MB855 using xda premium
Fastboot
I had to use fastboot to flash an entire stock config when I got stuck in this loop.
TheAv8tor said:
I had to use fastboot to flash an entire stock config when I got stuck in this loop.
Click to expand...
Click to collapse
Atleast you got it out, mines been acting up since i flashed cm9. I think i might have to do that
Sent from my MB855 using xda premium
okantomi said:
If you are using CWM recovery from Rom Manager (not recommended for Xoom) it does only read your internal flash memory (called sdcard) but not your external microsd card (called external1???). So you need to flash a different custom recovery using adb/fastboot to flash a recovery.image file or, if you can flash through cwm (from internal sdcard) a recovery.zip file (either EOS or Rogue, depending on the ROM you will flash afterwards), Actually, any custom recovery is supposed to work for any rom, but in reality Eos works best for Eos and Rogue works best for the CM9 Kang.
Please, just remember, never flash a .zip file through fastboot, only an .image file!
Click to expand...
Click to collapse
Thanks for saving the last half of my hair which I hadn't pulled out yet.
Got the backup on SD ONLY after flashing the EOS recovery 1.5.0 (i tried the latest to begin with, did not work, made it worse flashing recovery from ROM Mgr)
http://www.xoomforums.com/forum/mot...ing-flashing-unrooting-under-one-roof-59.html has this particular recovery listed.
I still cannot boot in recovery using power+volUP...i have to get at least adb running. Any suggestion would be golden.
error mounting /internal_sdcard!
error mounting /internal_sdcard! pls help me it got stuck in boot loop tried to wipe cache and user data bt cwm says error mounting /internal_sdcard!
Ipse_Tase said:
Thanks for saving the last half of my hair which I hadn't pulled out yet.
Got the backup on SD ONLY after flashing the EOS recovery 1.5.0 (i tried the latest to begin with, did not work, made it worse flashing recovery from ROM Mgr)
http://www.xoomforums.com/forum/mot...ing-flashing-unrooting-under-one-roof-59.html has this particular recovery listed.
I still cannot boot in recovery using power+volUP...i have to get at least adb running. Any suggestion would be golden.
Click to expand...
Click to collapse
Delete any zip files or IMG files from sdcard and reboot it this helped me ............ Hit thanks if helped
Sent from my HTC Desire C using XDA Premium 4 mobile app
This is my first attempt at unlocking and rooting. So far I did manage to get unlocked. Now I am stuck at: Can't mount/sdcard . . . . .
I have been following the thread: [HOW] Rookie Rooting, Flashing And UnRooting Under One Roof
It seems to be layed out quite well and well, I'd never have gotten this far if it weren't for following those directions. I'm not discouraged because I know this is just a stumbling block. I can't wait to kill the bloatware and see if I can O/C this beast just a little.
Good luck to the folks who posted above me. I will post my results here.
Mike P.
I think the solution is much more simple...
The recovery uses normally e: an external sd card , you just trying by d: internal sd card , so take another sd card and dun let it be internal sd card...
And the recovery back on working with you
I need some help, stupid me put the files i need to flash custom rom on my sd card and when i went to install the zip it was not there, its not my sd card at all. Is there anyway to get those files back on the internal storage instead of my sd card or is there a way to access the actual sd card in cwm? If not is there a way to do a factory reset back to the factory rom?
Lsjreadingpa said:
I need some help, stupid me put the files i need to flash custom rom on my sd card and when i went to install the zip it was not there, its not my sd card at all. Is there anyway to get those files back on the internal storage instead of my sd card or is there a way to access the actual sd card in cwm? If not is there a way to do a factory reset back to the factory rom?
Click to expand...
Click to collapse
Any help would be appreciated. I hate to know that at this point i have a $400 paperweight.
Don't panic, all hope is not yet lost and I don't think you've bricked your device. Can you describe in more detail the exact steps you took? When you say 'sdcard' do you mean your external SD card or the tablets' internal memory (its called /sdcard on the tablet, so its a bit confusing).
There is absolutely ways to recover your tablet assuming you took the proper precautions beforehand. Before I give an answer (assuming my knowledge is even correct) can you give more details of your setup? Which recovery do you have? Which ROM do you have installed? Is your bootloader unlocked? Are you rooted? All of these answers will give more information and will guide you to a better answer.
opethfan89 said:
Don't panic, all hope is not yet lost and I don't think you've bricked your device. Can you describe in more detail the exact steps you took? When you say 'sdcard' do you mean your external SD card or the tablets' internal memory (its called /sdcard on the tablet, so its a bit confusing).
There is absolutely ways to recover your tablet assuming you took the proper precautions beforehand. Before I give an answer (assuming my knowledge is even correct) can you give more details of your setup? Which recovery do you have? Which ROM do you have installed? Is your bootloader unlocked? Are you rooted? All of these answers will give more information and will guide you to a better answer.
Click to expand...
Click to collapse
This is what happened, today i unlocked, rooted and then installed CWM. I followed steps to format my device from this forum post http://forum.xda-developers.com/showthread.php?t=1750861. Like i said instead of putting the rom on my internal storage i put it on my external sd card. That is where we are at now.
Lsjreadingpa said:
This is what happened, today i unlocked, rooted and then installed CWM. I followed steps to format my device from this forum post http://forum.xda-developers.com/showthread.php?t=1750861. Like i said instead of putting the rom on my internal storage i put it on my external sd card. That is where we are at now.
Click to expand...
Click to collapse
OK so you're not bricked, you're not messed up at all. CWM doesn't support flashing from external SD cards, so all you need to do is move the files to the /(root) directory of your tablet. Are you still able to boot up the tablet normally? If so, connect it to your computer with the USB cable (assuming you've got the correct drivers installed, and ADB/fastboot both work) and just copy the files to the first directory you see when you double click "internal storage". This will be the root directory of your tablet. From there, you should be able to just boot into CWM and it will show your ROM there.
I'll be actively monitoring this thread so if you have any questions feel free to continue to post. I know how frustrating it is to post a question and not get an answer until days later.
*EDIT* ok so I just noticed one thing: you're trying to install the Hydro rom, correct? So you need to go back to STOCK using this guide. Then, re-install CWM, re-root your tablet, and then try to install the Hydro rom.
opethfan89 said:
OK so you're not bricked, you're not messed up at all. CWM doesn't support flashing from external SD cards, so all you need to do is move the files to the /(root) directory of your tablet. Are you still able to boot up the tablet normally? If so, connect it to your computer with the USB cable (assuming you've got the correct drivers installed, and ADB/fastboot both work) and just copy the files to the first directory you see when you double click "internal storage". This will be the root directory of your tablet. From there, you should be able to just boot into CWM and it will show your ROM there.
I'll be actively monitoring this thread so if you have any questions feel free to continue to post. I know how frustrating it is to post a question and not get an answer until days later.
*EDIT* ok so I just noticed one thing: you're trying to install the Hydro rom, correct? So you need to go back to STOCK using this guide. Then, re-install CWM, re-root your tablet, and then try to install the Hydro rom.
Click to expand...
Click to collapse
I can not boot past the asus logo. I seen how people were able to push a rom through fastboot and adb but i can not seem to get my device to be seen by my computer.
Lsjreadingpa said:
I can not boot past the asus logo. I seen how people were able to push a rom through fastboot and adb but i can not seem to get my device to be seen by my computer.
Click to expand...
Click to collapse
Then the next logical step will be to diagnose whether you have the drivers installed correctly. Do you have the Android SDK pack installed? It comes with some google drivers, and there is an aftermarket driver file that helps the computer recognize a larger variety of devices. Follow the steps in this thread to get those drivers working. If those don't work, try install the official Asus Pad suite drivers.
opethfan89 said:
Then the next logical step will be to diagnose whether you have the drivers installed correctly. Do you have the Android SDK pack installed? It comes with some google drivers, and there is an aftermarket driver file that helps the computer recognize a larger variety of devices. Follow the steps in this thread to get those drivers working. If those don't work, try install the official Asus Pad suite drivers.
Click to expand...
Click to collapse
Yes i have both installed actually.
Lsjreadingpa said:
Yes i have both installed actually.
Click to expand...
Click to collapse
Hmm, I'm running out of suggestions since I'm still learning all this stuff too. I guess since you can't get past the Asus screen it won't detect in the computer. So the next step I can suggest is to get fastboot mode working. Do this by powering your tablet off. To get into fastboot mode, press and hold the POWER & VOLUME DOWN buttons simultaneously. It'll show some words about booting into recovery, don't do that. Just wait for a few logos, then select the middle one (USB icon) with the VOLUME UP key. Connect your tablet to your computer and you should be recognized to allow you to push files over (I don't know what the syntax is for fastboot but I'm sure it won't be difficult to figure out)
opethfan89 said:
Hmm, I'm running out of suggestions since I'm still learning all this stuff too. I guess since you can't get past the Asus screen it won't detect in the computer. So the next step I can suggest is to get fastboot mode working. Do this by powering your tablet off. To get into fastboot mode, press and hold the POWER & VOLUME DOWN buttons simultaneously. It'll show some words about booting into recovery, don't do that. Just wait for a few logos, then select the middle one (USB icon) with the VOLUME UP key. Connect your tablet to your computer and you should be recognized to allow you to push files over (I don't know what the syntax is for fastboot but I'm sure it won't be difficult to figure out)
Click to expand...
Click to collapse
That's where im at right now, i got nothing here.
Lsjreadingpa said:
That's where im at right now, i got nothing here.
Click to expand...
Click to collapse
I'm going to try hooking my tablet up to another computer and see if i can get anywhere with it like that. I'm really starting to think this thing is fubared.
UPDATE Nothing worked on the laptop. Anyone else know of a way to get me out of this mess or am i screwed?
adb push any rom to the internal memory. if you can't do it in windows try a ubuntu live cd, you won't get errors in adb while using linux.
Sent from my ASUS Transformer Pad TF300T
atomicblue said:
adb push any rom to the internal memory. if you can't do it in windows try a ubuntu live cd, you won't get errors in adb while using linux.
Sent from my ASUS Transformer Pad TF300T
Click to expand...
Click to collapse
I don't have linux i have windows, how do i do that?
UPDATE:
Well i gave up trying to get this to work and luckily i was able to return my tablet to the store. I want to thank opethfan89 for doing what you could to help me. Lesson learned, i have to make sure i use the internal sd card! What got me confused is i rooted and installed a custom rom on my nook and with that you had to put everything on the external sd card. Now i know what not to do again lol.
Good thing you were able to return it. Although im pretty sure you could have used adb to push the files directly to your internal memory no problem.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
thatisandwas said:
Good thing you were able to return it. Although im pretty sure you could have used adb to push the files directly to your internal memory no problem.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
My device was not coming up under adb devices nor fastboot devices so im not sure what else could be done.
Lsjreadingpa said:
My device was not coming up under adb devices nor fastboot devices so im not sure what else could be done.
Click to expand...
Click to collapse
Like the poster above said, you could have used a Linux live CD, downloaded ADB for Linux, and used ADB under Linux.
EndlessDissent said:
Like the poster above said, you could have used a Linux live CD, downloaded ADB for Linux, and used ADB under Linux.
Click to expand...
Click to collapse
I will keep this in mind if something should happen again. This time i put a roms folder on my internal sdcard with the stock rom at the ready just incase.
Lsjreadingpa said:
I will keep this in mind if something should happen again. This time i put a roms folder on my internal sdcard with the stock rom at the ready just incase.
Click to expand...
Click to collapse
That's a good plan. When I flash a new ROM, I always make sure I have at least one known-working ROM and at least one nandroid backup just in case.
Also, just as an organization suggestion, name the ROM folder something like "1-ROMs" or "All ROMS" or something else at the beginning of the alphabet so it appears at the top of the list when you're choosing a zip to flash. I personally use "1-ROMs", "2-Kernels" and "3-Extras", so they're the first three folders listed (Extras is for Gapps, mods, other flashables). It saves a lot of scrolling time.
EndlessDissent said:
That's a good plan. When I flash a new ROM, I always make sure I have at least one known-working ROM and at least one nandroid backup just in case.
Also, just as an organization suggestion, name the ROM folder something like "1-ROMs" or "All ROMS" or something else at the beginning of the alphabet so it appears at the top of the list when you're choosing a zip to flash. I personally use "1-ROMs", "2-Kernels" and "3-Extras", so they're the first three folders listed (Extras is for Gapps, mods, other flashables). It saves a lot of scrolling time.
Click to expand...
Click to collapse
Im glad you got an exchange. I would be so upset if my tab was a 400 dollar brick
another brick
Lsjreadingpa said:
I don't have linux i have windows, how do i do that?
UPDATE:
Well i gave up trying to get this to work and luckily i was able to return my tablet to the store. I want to thank opethfan89 for doing what you could to help me. Lesson learned, i have to make sure i use the internal sd card! What got me confused is i rooted and installed a custom rom on my nook and with that you had to put everything on the external sd card. Now i know what not to do again lol.
Click to expand...
Click to collapse
You were able to return it?? Amazing attitude ASUS has over there. You weren't charged for repair at all?
I did a similar thing on workmate's tablet as he asked me to flash him custom os. I installed TWRP recovery successfully and copied firmware I wanted to install on internal SD. Then I wiped DATA. I thought it would wipe only user data, but it wiped also the root of my SD card with firmware. Before that I wiped system as well. So now I'm stuck at ASUS logo after power up.
I will try methods that were described in the thread by opethfan89 and atomicblue with adb push and Linux after I come back from vacation (14th this month). Hopefully I will be able to save the tablet. Otherwise it'll have to be sold for spare parts as ASUS quoted over 300 € (about $400) for repairs claiming the warranty is void (which I know) as I unlocked bootloader. They said they won't even try flashing it but they'll just replace motherboard as they never repair unlocked devices. I can't imagine car service refusing to change oil claiming they are concerned that owner might have abused it and they'd rather change whole engine instead.
Ok, So I've got a problem, I caused myself of course. I've been running one of the Jelly Bean beta roms that are out there and I wanted to go back to ICS. I've got CWM installed (the touch based one, 5.8 something) I threw Android Revolution 3.5 and the super wipe utility on the external SD card. I tried installing from that in CWM, however I couldn't mount the SD card. I moved the files from the external to the internal, and ran the wipe from there. Then I tried to install the ROM. Now I have nothing on my internal SD card, and I can't seem to mount the internal SD card in windows to put the files on the SD card to try the install again. The tablet will boot into CWM, but won't boot into anything else. If I don't boot into CWM it just stays at the Eee Pad boot screen. I've tried using a couple one click newbie applications I've found in these forums to no avail. I'm currently trying to install it via ADB (adb install C:\ROMfile.zip) and it seems to just be sitting there. I can see my device in ADB if I type ADB devices. I know all is not lost, I'm just not sure where to go from here. Thank you for your help!!!
Edit, I gave up on that and am now trying to push the file to the internal storage, but it isn't working.
EasyFlasher : (http://forum.xda-developers.com/showthread.php?t=1688012)
JoinTheRealms said:
EasyFlasher : (http://forum.xda-developers.com/showthread.php?t=1688012)
Click to expand...
Click to collapse
Yours is one of the ones I've tried. Doesn't seem to flash a recovery, and I can't get it to install the stock firmware.
Perhaps it would help to list what programs I've tried:
Brk Root Toolkit
OneClickRecovery 0.4
Easy Flasher 0.8.3b
WU55 said:
Ok, So I've got a problem, I caused myself of course. I've been running one of the Jelly Bean beta roms that are out there and I wanted to go back to ICS. I've got CWM installed (the touch based one, 5.8 something) I threw Android Revolution 3.5 and the super wipe utility on the external SD card. I tried installing from that in CWM, however I couldn't mount the SD card. I moved the files from the external to the internal, and ran the wipe from there. Then I tried to install the ROM. Now I have nothing on my internal SD card, and I can't seem to mount the internal SD card in windows to put the files on the SD card to try the install again. The tablet will boot into CWM, but won't boot into anything else. If I don't boot into CWM it just stays at the Eee Pad boot screen. I've tried using a couple one click newbie applications I've found in these forums to no avail. I'm currently trying to install it via ADB (adb install C:\ROMfile.zip) and it seems to just be sitting there. I can see my device in ADB if I type ADB devices. I know all is not lost, I'm just not sure where to go from here. Thank you for your help!!!
Edit, I gave up on that and am now trying to push the file to the internal storage, but it isn't working.
Click to expand...
Click to collapse
I can't link to the thread, noob that I am, but here was my solution to a similar problem:
OK. I managed to master the ADB command prompt well enough to "ADB Push c:\update.zip /sdcard/" Hey-zuss, there is a lot out there to read. After that, a few 2 tries with CWM got me to actually flashing '/sdcard/update.zip'
Steps I took:
Install the android SDK
Get the latest version of the ASUS ROM
Unzip the outer container.
Rename the zip carried inside to to "update.zip", and place it on 'C:\'
Start a command prompt in the directory with 'ADB.EXE' in it. (part of platform-tools for the android SDK)
In the command prompt, enter the statement, "ADB Push c:\update.zip /sdcard/update.zip'
Use ClockWorkMod to flash a new ROM, and chose the 'update.zip' from the root directory.
Chew nails.
(mine failed, so as a true windows user, I tried it again)
Chew nails.
Success.
The android SDK is easy to fin/install
The ASUS ROM is available from asus (find downloads/firmware for your system)
Now to time backup the ROM I have with CWM so I never have to do this again!
PMcHargue said:
I can't link to the thread, noob that I am, but here was my solution to a similar problem:
OK. I managed to master the ADB command prompt well enough to "ADB Push c:\update.zip /sdcard/" Hey-zuss, there is a lot out there to read. After that, a few 2 tries with CWM got me to actually flashing '/sdcard/update.zip'
Steps I took:
Install the android SDK
Get the latest version of the ASUS ROM
Unzip the outer container.
Rename the zip carried inside to to "update.zip", and place it on 'C:\'
Start a command prompt in the directory with 'ADB.EXE' in it. (part of platform-tools for the android SDK)
In the command prompt, enter the statement, "ADB Push c:\update.zip /sdcard/update.zip'
Use ClockWorkMod to flash a new ROM, and chose the 'update.zip' from the root directory.
Chew nails.
(mine failed, so as a true windows user, I tried it again)
Chew nails.
Success.
The android SDK is easy to fin/install
The ASUS ROM is available from asus (find downloads/firmware for your system)
Now to time backup the ROM I have with CWM so I never have to do this again!
Click to expand...
Click to collapse
I've tried a couple times to use ADB push to put a ROM on my SD card, and every time ADB has said it successfully transferred the file. Yet when I boot into CWM I can't seem to find it, nothing at all is on my SD card, no folders, nothing, after the super wipe script for Revolution. I'll try again, and continue to do so. I've also found Wheelie which supposedly gets me NVflash on my SBKv2 TF101 that I might try and use to flash my tablet back to stock.
edit: well, for some reason this time the push worked! I'm up and running again!!! Thanks all so much!