First things first, I am using the SL101 but as I could not find a place for that, I figured this is the best place for this post.Also I hate posting and creating new threads but there is absolutely no other thread like this, I have been searching for 3 days.
So I rooted my SL101 using vipermod with ease, then downloaded ROM manager but I think here is where I hit an issue, When cwm was installed it asked for me to confirm my device and the only device available to click was "Asus Transformer". As every other transformer tf101 firmware has worked on my tablet, I thought it would be fine. Then I was in the process of flashing Revolver 4.2.1 and my battery went flat so that was not ideal and this is when the issues began.
I booted into cwm recovery (vol- + power and then vol+ on the splash screen) and tried to "install zip from sdcard", I got the "Cant mount sdcard" dialog. I then rebooted and tried to flash the rom from ROM manager, when it rebooted, cwm went through a 20 second loop waiting for sdcard, and it did not find the sdcard so the operation was aborted. I tried a factory reset through cwm and when it rebooted, I would get the splash screen and the ASUS logo with the spinning dots loading, but it would not go past that (bootloop?). From here I could not access the OS at all.
Again into cwm and used the peri OneClick R&R Easyrecoveryv0.4. It went through all the unbricking dialog with three reboots, but one of the commands said it could not find "sdcard/recoveryblob". The system still did not work. I then put it into APX mode (vol+ and power) and installed the APX driver, used the download.bat method but the minute it opens commandprompt, it immediately disconnects the APX driver, the tablet remains in APX mode. This method did not work.
Somewhere along the lines I also managed to format the system and data so not when I turn it on it just goes into the splashscreen with the EEEpad logo and nvidia Tegra.
Also tried adb push to push revolver rom onto the system /sdcard/ directory, that works fine but then again it cant mount sdcard so I cant actually do anything with it. adb devices lists the device as 0123456789ABCDEF recovery. Finally I did try boot twrp.img using fastboot with the "fastboot boot twrp.img" command but it hangs on "waiting for device". fastboot devices also does not list any devices.
So I basically have a tablet whose cwm cant mount sdcard, adb works, fastboot doesnt see the device and I can only go onto cwm on the tablet or splashscreen. Can somebody help me out? I have spent a long time trying to fix this.
Fixed
Hi again, sorry for the double post but after posting that I realised the answer was pretty much staring me in the face and now this has been fixed. so this thread can be closed by the bigdogs.
For future reference to anybody who has this or a similar problem, especially if you format the system and fastboot is not working, the issue is cwm v6.0.1.3 (cant mount sdcard issue), I used the PERI oneclickrecovery v0.4. The unbrick selection did not work for my slider as I had already pretty much wiped any data from the system that could have been salvaged by the unbrick, but if you press "r" in the main menu it flashes a new recovery tool over cwm, and this new tool can access external sdcard so just upload the rom zip file onto there and flash. :fingers-crossed: Revolver 4.2.1 is now flashed and working. :victory:
Related
Hey guys, just wondering if any of you know a fix for this on my WIFI only xoom
Using the guide from here about Wifi Unlocking and rooting Ive unlocked the bootloader on my Xoom. Ive flashed Clockwork and am up to the part where I have to boot into clockwork recovery to install the root tool, however there is no option to enter 'Android Recovery' when I push the Down key on the dual core boot screen, during the first 3 seconds of the first boot after flashing. Theres NVFlash, fastboot and another but no recovery.
I am able to get into recovery via the ADB REBOOT RECOVERY command however I dont get into Clockwork and am stuck on a screen with a green android logo in the center. Pushing any manner of buttons does nothing and the tab automatically resets after 2 or 3 mins in that mode. Has anyone else seen this and know of a fix?? Ive since learned that if you allow the tab to boot into honeycomb it installs the stock recovery and you have to start over by reflashing clockwork, as stated tho no Android Recovery option appears. Any ideas?
recovery is not installed properly.
put your recovery file in fastboot folder
rename it to recovery.img
in fastboot run: fastboot flash recovery recovery.img
this recovery file is not zip file but .img file(rename it for ease of typing)
I've done it exactly like that, 3 times now. all the messages seem to indicate its flashed correctly. Heres what it says on the tab:
Flashing allowed for partition recovery
OneWire: Charger not connected
Battery Level 82%
Flashing Stormgr partition recovery Status:- done!
And i get the OKAY's in the terminal box as well. Still no Android recovery menu. I read in a dev post reguarding this same procedure a few other ppl had the same issue. I was hoping sum1 had a fix
Nexus S 4g
I did the one click root month or 2 ago and gained unlock and SU permissions. My phone updated to 2.3.7, last week. I decided to load CWM today and discovered I no longer had permissions. I've tried several things and am stuck.
Nothing in ROM manager will work properly. I get message: "error occured while attempting to run priviledged commands" for fix permissions, or load other CWMR (that worked in the past I had to put an earlier one in to be able to access recovery in bootloader). If I try to backup, apply .zip, etc it just never reboots.
If I go to bootloader and go into recovery, each time it shows unlock, then the triangle with an exclamation point (so I can't backup, restore previous backup, anything)
I managed to grab SU 3.0 and force it to install over my existing 2.3.6, it did, sees my su (which is in system/bin which I've read is a problem ) as being outdated and wants to update it, fails each time.
So someone smarter than me please advise. My phone is functioning nicely without FCs or other issues, a normal boot or reboot goes fine, but I fear for the day I really need my backup. Not to mention frustrating that I seem to be locked out from making any changes now.
Thanks, Travis
sobamaflyer said:
Nexus S 4g
I did the one click root month or 2 ago and gained unlock and SU permissions. My phone updated to 2.3.7, last week. I decided to load CWM today and discovered I no longer had permissions. I've tried several things and am stuck.
Nothing in ROM manager will work properly. I get message: "error occured while attempting to run priviledged commands" for fix permissions, or load other CWMR (that worked in the past I had to put an earlier one in to be able to access recovery in bootloader). If I try to backup, apply .zip, etc it just never reboots.
If I go to bootloader and go into recovery, each time it shows unlock, then the triangle with an exclamation point (so I can't backup, restore previous backup, anything)
I managed to grab SU 3.0 and force it to install over my existing 2.3.6, it did, sees my su (which is in system/bin which I've read is a problem ) as being outdated and wants to update it, fails each time.
So someone smarter than me please advise. My phone is functioning nicely without FCs or other issues, a normal boot or reboot goes fine, but I fear for the day I really need my backup. Not to mention frustrating that I seem to be locked out from making any changes now.
Thanks, Travis
Click to expand...
Click to collapse
You're "locked out" because you don't actually have root access. The OTA update chmods /system recursively (and as a result /system/bin and /system/xbin).
The triangle with the exclamation mark is the stock recovery (applied with the OTA update).
I'm not entirely sure what you've tried as it's a very easy process.
-Download CWM for your device - flash it using fastboot.
-Boot into recovery and flash the su binary via recovery. This will place the binary appropriately as well as chmod it.
-Done
-Profit?
krohnjw said:
You're "locked out" because you don't actually have root access. The OTA update chmods /system recursively (and as a result /system/bin and /system/xbin).
The triangle with the exclamation mark is the stock recovery (applied with the OTA update).
I'm not entirely sure what you've tried as it's a very easy process.
-Download CWM for your device - flash it using fastboot.
-Boot into recovery and flash the su binary via recovery. This will place the binary appropriately as well as chmod it.
-Done
-Profit?
Click to expand...
Click to collapse
Oddly I was getting the triangle intermittently from the get go, but I had been able to get around it by applying an earlier clockworkmod version in Rom Manager. I'm not able to do that now.
My whole problem is I'm unable to do anything at all in Fastboot. If I go to "recovery" to try and apply anything I get the triangle.
Am I missing something?
It does say "Lock State - Unlocked" in fastboot if that means anything.
sobamaflyer said:
Oddly I was getting the triangle intermittently from the get go, but I had been able to get around it by applying an earlier clockworkmod version in Rom Manager. I'm not able to do that now.
My whole problem is I'm unable to do anything at all in Fastboot. If I go to "recovery" to try and apply anything I get the triangle.
Am I missing something?
It does say "Lock State - Unlocked" in fastboot if that means anything.
Click to expand...
Click to collapse
Yeah, you have the stock recovery. You can't apply a new recovery through rom manager because the su binary doesn't have the appropriate permissions since the update.
Boot into the boot loader (Vol up and pwr). Don't go into recovery. Use fastboot from the boot loader to load CWM. Boot into CWM after flashed and flash the SU binary (mount /system first). After this boot up and delete/rename /etc/install-recovery.sh so that it won't overwrite CWM on each reboot. Install CWM again from Rom Manager or via fastboot (as it was overwritten on boot). Done.
Since you are being nice enough to try and help an id10t (apparently) and others may have the same issue and search this I'll ask the dumb questions. (I did a bit of googling a min. ago and found others with the same things I see but didn't get any further...).
When you say "go into Fastboot" you mean opening SDK Manager on my PC while I'm in the Boot Loader Screen?
At the bottom of the screen I see:
USB Control Init
USB Control Init End
[plug in usb get:]
STANDARD_SET_CONFIGURATION
Nothing shows up in SDK, I have the black CMD screen up but can't type anything at all in it?
......I did try loading pda_net (not sure what to do with that? but it was mentioned elsewhere) and I get a grey message at the bottom of the screen that says "FASTBOOT STATUS - FAILinvalid Command"
sobamaflyer said:
Since you are being nice enough to try and help an id10t (apparently) and others may have the same issue and search this I'll ask the dumb questions. (I did a bit of googling a min. ago and found others with the same things I see but didn't get any further...).
When you say "go into Fastboot" you mean opening SDK Manager on my PC while I'm in the Boot Loader Screen?
At the bottom of the screen I see:
USB Control Init
USB Control Init End
[plug in usb get:]
STANDARD_SET_CONFIGURATION
Nothing shows up in SDK, I have the black CMD screen up but can't type anything at all in it?
......I did try loading pda_net (not sure what to do with that? but it was mentioned elsewhere) and I get a grey message at the bottom of the screen that says "FASTBOOT STATUS - FAILinvalid Command"
Click to expand...
Click to collapse
Fastboot is merely a command line tool used for various operations on the device. Mainly though you'll use it to flash an image to a specific partition.
You'll need to boot the device into the boot loader (hold Vol up and power on).
Plug the device in via USB.
Open a command windows in the tools or platform-tools folder of the SDK (depending on your version of the SDK, where the fastboot.exe can be found) and issue the fasboot devices commmand. This should display the serial of any connected devices. If this comes back blank there is an issue with the installed driver. Reinstall the USB driver for the device using the supplied driver from an updated SDK.
Assuming fastboot devices shows one device you now can flash a recovery to the device. Download the appropriate recovery for your device (i9020(a), i9203 or NS 4G) http://mirror.sea.tdrevolution.net/cm/recoveries/. Place this file in the same directory for simplicity.
At this point you can flash your recovery.
fastboot flash recovery file.name.you.downloaded.img
If it is not in the same directory you can alternatively pass the full path to the image.
You now have a custom recovery installed. Select Recovery from the bootloader menu to now boot into this recovery.
Assuming you've already downloaded the su binary and it is on your SD card, mount /system from within CWM and then chose to install zip and select this from the SD card. You now have root access.
Now that a panic attack is settling...
I think I'm getting somewhere but not yet where I want to be. I go to Bootloader, I connect my USB and don't get anything different than above from my sdk tools menu (unusable cmd screen, fail showing on my phone). What does [eventually] work is going back to my "nexus S one click root" folder and clicking run.bat (as fastboot.exe and adb.exe in that folder also do the nothing).
This run.bat reads some sort of fail and boots my phone telling me that debugging is not checked (which it is) and takes me directly to there, then the cmd screen tells me to press enter when I've turned on the [already checked] usb debugging toggle.....what the hell I press enter. Now it goes into the old beautiful CWMR (3.0.xxxx) screen where I'm able to apply .zips, backup etc.
(luckily I think ahead and do a backup right this min.)
Then I go from that screen and decide to apply my new CM7.zip that started all this, I apply that and get a bootloop on the CM7 boot screen.......crap......I go clear my davlik and cache and install CM7 again. Same thing.....crap......
I try restoring my original backup from 9/5/11 I made right after first unlocking my phone.......CM7 bootloop screen.....dammmmiiiiit
I try restoring backup from 9/12 I made after getting everything just like I wanted it.......CM7 bootloop screen.......uh oh, panic beginning.
I restore the backup from a few lines ago, my phone comes back (thank god)
So:
-I have to have the right USB driver in my laptop because something from sdk ultimately talked to my phone?!
-Clockworkmod recovery 5.xxxx has never worked quite right for me, apparently 3.xxxx is still my magic answer?!
-Now that I've gotten this far should I try the same process to get back to my CWMR 3.xxxx screen and put some different files in my root to use than what I've done to this point?
....again, I apologize if I'm being myopic or asking dumb questions. I often say I only know just enough to be dangerous.
[SOLVED] - maybe/sort of
Between reading (and re-reading) the help above and continued research on my own I [think] I solved my problem.
I found the following 2 links:
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
http://theunlockr.com/2010/12/17/how-to-root-the-samsung-nexus-s/
And basically started over from scratch, I deleted what I'd put in my pc and re-loaded using those instructions (in the right place, the right way). Doing this I was able to pull up a cmd window and this time it properly accessed my phone. I got it to fastboot recovery - load CWM 5.0... and from there got into my recovery menus on my phone this time.
One curious thing....I tried the part VI in "how to root the samsung" ...""stop the phone uninstalling the custom recovery image"...... I've tried several things there but still get an error that it is read only.
....I went on to install CM7, and it consequently updated right after to the latest CM7, At this moment I have full permissions, superuser access, was able to make a backup of yesterday, the CM7 this morning and then CM7.1.0.1 that loaded.
Will I ultimately have the same issue as before? But be able to overcome it in the same manner when I want to?
Thanks for the help
This is why one click methods are bad. When a problem arises you have no clue what to do because a software did it for you the first time. Glad you got it figured out.
Sent from my Nexus S 4G using xda premium
So I have got this Nexus S (I9020) from Rogers and it is pretty much bricked...
Turns on and freezes at the black "Google" Logo with the lock image at the bottom of the screen...
Hold Vol + / Pwr takes me to FastBoot Mode where lock state - Unlocked and at bottom says
USB Control init
USB Control init End
Standard_Set_Configuration
I try to go into thirs option down (recovery) and I just see triangle with "!" and a green android in middle of the black screen... press up/pwr there and I get Android System Recovery <3e> with only these options:
reboot system now
apply update from /sdcard
wipe data/factory reset
wipe cache partition
------------------------
I can't put a rom or anything on the sdcard to flash with because I HAVE NOT BEEN ABLE TO get the internal sdcard to mount as a USB drive on my PC.
I have tried 3+ days of search for drivers, tried Google SDK + USB Drivers Package / Samsung Driver Package for Nexus S / Fastboot,ADB "device not found" , nothing!!!!!!
Nothing seems to make this device show up in "My Computer" so I can put required files on the sdcard (internal memory) and flash...
I see the device being detected but the drive is greyed out in Explorer
Please help... there is nothing I can do with this phone but to resist smashing it against a wall
PS: The whole issue started when I tried to root using SuperUser.zip or something like that... in any case, phone doesn't boot and doesn't get accessed via Mac/PC ... cant access sdcard, cant load rom, cant flash...
Its Brick?!? Garbage?
You will need to install ClockWorkMod recovery on the phone. In your situation this can only be done by "pushing" (flashing) the .img file to the phone using fastboot.
Once CWM is installed (will replace your current recovery, the triangle with a square) you can access it through the boot loader like you accessed the older recovery.
In CWM, you can mount your sdcard and upload a custom firmware to it and sequentially install it as well. Once the new rom is installed, your phone will work.
In order to do all the fastboot stuff, I really suggest you read the guides in the General Section of this subforum. If you're having issues connecting your phone to your PC, please read up in this section, this issue has been raised a million times and solved just as many times (hint: it's mostly a drivers issue and the PDANet drivers prove to be very successful for Windows).
Good luck,
Greetz
I installed PDANet drivers and went to connect in fastboot and the phone states "Fastboot Status - FAILInvalid Command" at the bottom in grey...
Fastboot devices.
So I recently tried to install a new ROM and I bricked the TF101. So I will try to elaborate the best I can of the situation. The first thing I did was root the tablet which I was able to with the Peri 0.4 -->http://forum.xda-developers.com/showthread.php?t=1681155
I then installed ROM Manager and I was able to install CWM Recovery v6.0.1.3
At this point, I was like I just install zip from sdcard and just load my ROM. I then try to do so, but I kept getting the error:
E: unknown volume path [/sdcard/]
E: Can't mount /sdcard/
I remember reading somewhere here on XDA to refresh the storage so I went to the main menu of CVM recovery --> mounts and storage
format system/catche/data
After that, the TF101 couldn't boot up anymore. I tried the nvFlash fix here: http://forum.xda-developers.com/showthread.php?t=1123429
I do the Volume up + Power and the thing loads into my computer. I followed everything up until I run the download windows batch file, every time I click it nothing happens. The cmd just comes on for a split second then goes away.
So I am now stuck with a $200 tablet that is a paperweight. If anyone has any solution. It would be great!
Dorianking said:
So I recently tried to install a new ROM and I bricked the TF101. So I will try to elaborate the best I can of the situation. The first thing I did was root the tablet which I was able to with the Peri 0.4 -->http://forum.xda-developers.com/showthread.php?t=1681155
I then installed ROM Manager and I was able to install CWM Recovery v6.0.1.3
At this point, I was like I just install zip from sdcard and just load my ROM. I then try to do so, but I kept getting the error:
E: unknown volume path [/sdcard/]
E: Can't mount /sdcard/
I remember reading somewhere here on XDA to refresh the storage so I went to the main menu of CVM recovery --> mounts and storage
format system/catche/data
After that, the TF101 couldn't boot up anymore. I tried the nvFlash fix here: http://forum.xda-developers.com/showthread.php?t=1123429
I do the Volume up + Power and the thing loads into my computer. I followed everything up until I run the download windows batch file, every time I click it nothing happens. The cmd just comes on for a split second then goes away.
So I am now stuck with a $200 tablet that is a paperweight. If anyone has any solution. It would be great!
Click to expand...
Click to collapse
1. You used ROM manager - that is why your tf seems trashed. There is a warning thread stickied at the top of the general section to this effect.
2. Try a cold boot - power plus volume down (like you were booting to recovery) but don't push volume up and let it take you to the cold boot/wipe option.....select boot from Linux.
3. Hopefully that at least gets you into your ROM or recovery.
4. http://forum.xda-developers.com/showpost.php?p=29632231&postcount=3
Read this to try and remedy the problem if you can get into the working system
If not and you've blanked the slate then one of the other guys who have used peri or one of the nvflash tools will hopefully guide you through.
Also what version of tf do you have? Are you B70+ or B60 or lower?
If your B70+ then the nvflash guide you used most likely failed as its not designed for your version.
---------- Post added at 08:28 AM ---------- Previous post was at 08:11 AM ----------
http://forum.xda-developers.com/showpost.php?p=29632231&postcount=3
Try white kidneys tool and see if it gets you back to life.
If I had a dollar for every person I have helped unbrick because they used ROM Manager, I could have a Nexus 7, Nexus 10, Note 10.1 and an Infinity.
Anywho, my recommendation is to use EasyFlasher in APX Mode (VOL UP & POWER)
I wrote a guide on how to install a custom recovery and then root and/or ROM here:
http://www.transformerforums.com/fo...t/31927-frederuco-s-guide-root-rom-tf101.html
You can skip over the backing up your current ROM most likely, just install a custom recover (if you choose CWM, do NOT use ROM Manager to update it).
I personally like TWRP much better myself.
Hope this helps!
I use the EasyFlasher and it worked brillantly.
Thanks!
Hi guys,
My A510 just turned itself off with no apparent reason. Now I'm experiencing the following, looping :
- It tries to boot,
- freezes on the boot logo (previously "NoThrills", now "Acer"),
- vibrates and reboots.
I can boot in recovery (CWM). When I do, CWM apparently can't access the logs. Here's what I tried :
- wiping everything (data, cache, dalvik)
- restoring Nandroid backup (it was previously a NoThrills JB, now it's back to a stock JB) but I get an error when it tries to restore /data ("Error while restoring /data!").
My computer doesn't detect the tablet when it's plugged in... so I think I can't push or adb anything.
I guess it might be a hardware problem, but does anyone have any idea ? Maybe I could try to diagnose the problem?
Thanks a lot!
You can try to put a full update.zip on your sdcard, and flash it with your recovery
(a custom ROM or a full Acer Stock ROM)
You can also try to format every partitions via fastboot and then, reflash a proper ROM
Hey Shreps,
Thanks for your answer.
- I tried flashing NoThrills' CM10 from the external SD card, it didn't throw any error (although it skipped formatting the boot partition as well as extracting the files to the data partition, I don't know if it's a valuable information or not). Now instead of having the Acer logo during boot, the screen is doing weird stuff and it still won't boot. I can still boot into recovery though.
- I'm not sure how to use fastboot on this device. I get the option to boot into fastboot on my Moto G, but not on my A510. Do I need to flash a more recent CWM to enable it?
Thanks!
Boot in Fastboot via physical button http://forum.xda-developers.com/showthread.php?t=1747802
Thanks!
Volume down + Power on + Rotation switch got me to a black screen with the Acer logo and the following on top :
"Bootloader Version JB-d0ca683 (Unlock Mode)" -> that's normal
"Bootloader VJB-d0ca683(UnlockMode): Starting Fastboot USB download protocol" -> It's stuck there and I'm not sure it completes the operation.
My PC doesn't detect the A510, and "fastboot devices" returns nothing in the terminal.
Any idea?
Thank you!
Ghoorg said:
Thanks!
Volume down + Power on + Rotation switch got me to a black screen with the Acer logo and the following on top :
"Bootloader Version JB-d0ca683 (Unlock Mode)" -> that's normal
"Bootloader VJB-d0ca683(UnlockMode): Starting Fastboot USB download protocol" -> It's stuck there and I'm not sure it completes the operation.
Click to expand...
Click to collapse
That's normal/ok
Ghoorg said:
My PC doesn't detect the A510, and "fastboot devices" returns nothing in the terminal.
Any idea?
Thank you!
Click to expand...
Click to collapse
Should work, try to proper install the Acer drivers & check your USB Cable/port
"fastboot devices" should return a device with its ID
Still no luck after reinstalling the acer drivers... I think some components may be fried at this point?
There's something I'm wondering, it seems I can't mount anything from my pc but I can see files and folders from CWM. Is there any way I could copy everything on the external SD card that's in my A510?
Thanks!
Reply
Ghoorg said:
There's something I'm wondering, it seems I can't mount anything from my pc but I can see files and folders from CWM. Is there any way I could copy everything on the external SD card that's in my A510?
Thanks!
Click to expand...
Click to collapse
With the Tablet in CWM Recovery you can do a Backup on an SD Card
search for cwm recovery backup on the net
lists you the possibilities.
I had the same Problem, fastboot did not list my device because the mode was for receiving data only. But you can try this:
Tablet off.
Enter the Fastboot Commands in the Command-Line
Then turn your tablet in fastboot-mode.
Good luck.