Hello, I rooted my tablet for 1 year ago and had been using Revolution HD ever since. This evening I decided to upgrade to something more new and came across goomanager so I downloaded the Cyanmode cm-9.1.0tf101 via the app. I flashed with TWRP (easyflasher) v.2.3.1.1. The issues I am having now are:
1. The loading screen (the guy with spinning circle behind him) keeps appear randomly and constantly and resets everything each time (wifi etc)
2. I cannot access the folders (the file manager is gone). I cannot access to the folders even when the tablet is connected to PC, the folders show emptiness.
3. The TWRP I am using don't allow me to flash anything from external usb. Therefor I dont know how to install another rom or how to fix these problems
EDIT: I have tried to flash the stock version 9.2.1.27 with easyflasher but it failed. The problem is that I cannot enter apx mode. I installed Universal Naked Driver 0.7 but everytime I try to enter apx mode, it resets and says "drivers could not be installed".
EDIT2: I was able to install CWM recovery v.3 with Brk.root.toolkit.v7.1 but can't access sdcard to flash roms, it says "cant mount sdcard, unable to open ums lunfile
Where do I go from here to get anything working?
PLS help
Regards,
Anh
woodendick said:
Hello, I rooted my tablet for 1 year ago and had been using Revolution HD ever since. This evening I decided to upgrade to something more new and came across goomanager so I downloaded the Cyanmode cm-9.1.0tf101 via the app. I flashed with TWRP (easyflasher) v.2.3.1.1. The issues I am having now are:
1. The loading screen (the guy with spinning circle behind him) keeps appear randomly and constantly and resets everything each time (wifi etc)
2. I cannot access the folders (the file manager is gone). I cannot access to the folders even when the tablet is connected to PC, the folders show emptiness.
3. The TWRP I am using don't allow me to flash anything from external usb. Therefor I dont know how to install another rom or how to fix these problems
EDIT: I have tried to flash the stock version 9.2.1.27 with easyflasher but it failed. The problem is that I cannot enter apx mode. I installed Universal Naked Driver 0.7 but everytime I try to enter apx mode, it resets and says "drivers could not be installed".
EDIT2: I was able to install CWM recovery v.3 with Brk.root.toolkit.v7.1 but can't access sdcard to flash roms, it says "cant mount sdcard, unable to open ums lunfile
Where do I go from here to get anything working?
PLS help
Regards,
Anh
Click to expand...
Click to collapse
Remove all Asus drivers installed on your laptop and restart. Now try installing universal naked driver, if your your laptop still says "drivers could not be installed" then unzip the driver and place it in a folder and then go to device manager and look for "unknown devices"... select it and update driver manually by selecting the unzipped folder.
Sent from my Transformer using xda app-developers app
I had the same problem with drivers. The naked universal didn't work, nor any other driver I found on xda.
I uninstalled them and when reinstalling let Windows choose driver from whole c:. After a few minutes a driver was installed.
Related
Okay here is the thing, I am a bit of an advanced user, and have been flashing ROM's for quite a while, so i am not a noob and I have already tried everything in the book to fix my problem.
Info:
1- Drivers installed on Windows 7 and have been working for the past 4 months.
2- USB Debugging ticked
3- Windows recognizes the Galaxy Tab 7" GSM (P1000 International)
Problem:
1-Running "adb shell" in adb results in: error: device not found
2-CWM Restore stops at android_secure.img not found and aborts.
How did it happen (Detailed):
1- Was on Overcome 2.0.1 "Hermes" and found out that there was an update on kies from someone.
2- Decided to restock
3- Flashed P1000JPJM5 (I already did that quite a few times and no problems ever occurred from that)
4- When i restocked i wanted to root, so i went into settings>Application>developement> and ticked USB Debugging
5- Plugged in USB and I opened up Super One Click Root v1.7 and hit Root, however, Nothing happened and it was "Waiting for device" forever.
6- tried Super One Click root v1.9 with the same result
7- Opened adb and typed "adb shell" and got error: device not found.
8- I downloaded Better Terminal app from the market and tried "adb shell" and i got "Adb not found" as a result
9- I wanted to root my device to use the Bootloader Batch and change my protected boot loaders
10- tried everything, Restore factory from 3e Recovery, Doing the same from Setting>Privecy, Flashing the same ROM Over and Over again with no luck
11- learned later that flashing ChainFire's Gingerbread P1000XXJMQ is safe on protected boot Loaders so i did that
12- the problem persisted and i just cant use adb
13- I had a CWM Backup done so i thought doing a restore might solve the problem, but that resulted in a failure in restore. it stops at android_secure.img not found and aborts restore.
If anyone kow's a solution or at least knows what might have gone wrong Please shed some light on how to go about this issue.
Thanks
While the device is plugged in, go to device manager and delete/uninstall the device. Should ask you if you want to delete the driver files also, check the box and go.
After that it will probably ask you to restart, restart the computer and reinstall the device with the google drivers.
pwolfamv said:
While the device is plugged in, go to device manager and delete/uninstall the device. Should ask you if you want to delete the driver files also, check the box and go.
After that it will probably ask you to restart, restart the computer and reinstall the device with the google drivers.
Click to expand...
Click to collapse
well its like i said earlier it is NOT a driver issue.
I mean even Emulater apps from within the Tab are not recognizing ADB
DistortedWisdom said:
well its like i said earlier it is NOT a driver issue.
I mean even Emulater apps from within the Tab are not recognizing ADB
Click to expand...
Click to collapse
Did you at least try what I suggested?
I can't get my galaxy tab to be seen by adb either. At least not since upgrading to Gingerbread.
I'm using the
"sprint_p100_Samung_GALAXY_Tab_USB_Drivers.msi" file from the Samsung web site.
Hi guys,
I just have received a i9023 from a friend to repair. I put fastboot on and the device is unlocked, then I copied over Matr1x kernel via USB to the SD card and flashed CMW to recovery.
From here things went bad.
When trying to update the kernel to Matr1x, it showed that the file wasn't on the SD card anymore, so I tried to mount the SD card to copy it back, but it my computer wouldn't see it. Since then I tried many things to get the USB working - updating drivers etc... after awhile I decided to format SD card, which didn't help, so I formatted all the partitions on the phone.
Now, every time the phone comes on, it boots straight to fastboot, but also the PC will still not recognise the phone via USB.
I've tried getting into Download mode and using ODIN to flash a new kernel & ROM, but this wont work without USB working.
Can anyone help?
PS. I have read many other guides and posts, but nothing has helped.
Many thanks.
*Bump*
Are you running Ubuntu or similar? You need to be root to use fastboot and edit the right config files
wait, did you go to the mount menu in cwm? You can mount as usb storage in that menu... Are you saying it doesn't show up on your computer? Are you running windows?
I've a friend in the same situation.
We managed to make the phone recognizable using pda.net driver for nexus S, but weren't abel to find a single tar file to use on Odin.
Seems that all stocks rom were deleted from any storage.
bedalus said:
Are you running Ubuntu or similar? You need to be root to use fastboot and edit the right config files
wait, did you go to the mount menu in cwm? You can mount as usb storage in that menu... Are you saying it doesn't show up on your computer? Are you running windows?
Click to expand...
Click to collapse
Yes, I tried to mount as USB Storage in the Recovery Menu - didn't work, but now, I've only got fastboot - Booting up the phone normally jumps straight to fastboot, trying to boot into recovery doesn't work (just the fallen over Android pic with the red "!" on his chest).
I'm using Windows 7 and computer will not recognise the phone at all (it was working before this & the MicroUSB port is not damaged).
My GT-i9100 works perfectly via USB.
Piemo said:
I've a friend in the same situation.
We managed to make the phone recognizable using pda.net driver for nexus S, but weren't abel to find a single tar file to use on Odin.
Seems that all stocks rom were deleted from any storage.
Click to expand...
Click to collapse
If I can get it to connect to my PC so I can throw a stock ROM on there via ODIN I should be right (Pretty sure SAMFIRMWARE has some).
I've found often that the sdcard only gets mounted when you "choose zip from sdcard" in recovery. I panicked once with a galaxy s when I had forgot to put any rom on the sdcard and couldn't mount it subsequently. Ended up using heimdall with success. Also make sure you have latest version of fastboot, from platform tools 4.0.3.
Yeah, try Odin
If you can download sdk with the google drivers and install the drivers through device manager, you should be able to get your usb to connect again to fastboot. There is a bootloader driver inside the kit!
twadda218 said:
If you can download sdk with the google drivers and install the drivers through device manager, you should be able to get your usb to connect again to fastboot. There is a bootloader driver inside the kit!
Click to expand...
Click to collapse
Yeah, it is definitely not connecting via fastboot. Windows 7 just comes up with UNKNOWN DEVICE., as does my WinPX machine. It's very strange.
Can you try Ubuntu? Any luck with Odin?
KLoNe1 said:
Yeah, it is definitely not connecting via fastboot. Windows 7 just comes up with UNKNOWN DEVICE., as does my WinPX machine. It's very strange.
Click to expand...
Click to collapse
Does it say unknown device in device manager?
Sent from my ice cream powered Nexus S
I don't have a machine with Ubuntu on it unfortunately.
Yes, Unknown Device in Device Manager - it won't accept it when I point the new driver to the modified Google USB .inf file
KLoNe1 said:
I don't have a machine with Ubuntu on it unfortunately.
Yes, Unknown Device in Device Manager - it won't accept it when I point the new driver to the modified Google USB .inf file
Click to expand...
Click to collapse
Did you click the "Have disk" option, point it at the file then click one of the options? That's what I had to do
Sent from my ice cream powered Nexus S
DarkhShadow said:
Did you click the "Have disk" option, point it at the file then click one of the options? That's what I had to do
Sent from my ice cream powered Nexus S
Click to expand...
Click to collapse
Yes, I did - it said that this inf (driver) doesn't contain information about the device in question.
I think I came across a USB driver problem once that was rectified by deleting the relevant keys from the registry. Could be worth looking into.
EDIT: Found it!
Open regedit and navigate to
HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Enum > USBSTOR
and look for any devices that could be your nexus s.
I think they might be these:
Disk&Ven_Android&Prod_UMS_Composite&Rev_0001
Disk&Ven_Google&Prod_File-CD_Gadget&Rev_0000
You should be able to delete them (if not, change the permissions).
Then reboot and hopefully next time you plug in your phone, the drivers will reload.
Many thanks for all your help everyone; unfortunately I still have yet to figure out how to get this working. Please keep throwing out your ideas
bedalus said:
I think I came across a USB driver problem once that was rectified by deleting the relevant keys from the registry. Could be worth looking into.
EDIT: Found it!
Open regedit and navigate to
HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Enum > USBSTOR
and look for any devices that could be your nexus s.
I think they might be these:
Disk&Ven_Android&Prod_UMS_Composite&Rev_0001
Disk&Ven_Google&Prod_File-CD_Gadget&Rev_0000
You should be able to delete them (if not, change the permissions).
Then reboot and hopefully next time you plug in your phone, the drivers will reload.
Click to expand...
Click to collapse
I gave this a go as it sounded like a great idea, but unfortunately it still isn't working.
I ended up deleting the drivers it was installing which wouldn't work & now it will only show up as 2x Unknown device under 'Portable Devices' heading.
I think you should try installing ubuntu, and the android sdk so you have access to fastboot again.
I just switched ROMs and upon connecting my tablet to my computer Windows simply fails to find the appropriate drivers. If I go into device manager, my device is listed with a yellow exclamation mark under 'Other Devices'. It's called 'Transformer TF101'.
So anyway I tried downloading the drivers off Asus' website and pointing the update driver dialogue to them but it tells me there are no drivers there when there clearly are. I have uninstalled and reinstalled Asus Sync 3 times and it apparently installs the drivers each time and yet when I connect my tablet I get the annoying same telling me no drivers could be found.
WTF do I do???
Download the universal naked drivers, (Search button is your friend to find those :], be sure to search from the index)
uninstall ALL drivers or driver-related to TF from your computer, reboot, then connect your computer and in device manager right click the unknown device and hit update driver, then point it to the folder with the universal naked drivers. Should fix you right up
Nope, I point it to the folder but it still tells me no driver found.
Would it have something to do with Superwipe? I saw it was formatting in EXT4 which I'm not sure if my PC can recognize.
EDIT: I reformatted without using Superwipe then flashed Revolver but not Guever's Kernel and it worked. Then I flashed Guever's Kernel and now it's not working again...
EDIT2: Found the solution for anyone else. Go to Storage, then tap the icon in the top right corner and select USB connection. Tick MTP.
Thank you sooooo much! Just decided to upgrade to ICS (Revolver 4 RC3) today and this was driving me crazy!
DevourDarkness said:
Nope, I point it to the folder but it still tells me no driver found.
Would it have something to do with Superwipe? I saw it was formatting in EXT4 which I'm not sure if my PC can recognize.
EDIT: I reformatted without using Superwipe then flashed Revolver but not Guever's Kernel and it worked. Then I flashed Guever's Kernel and now it's not working again...
EDIT2: Found the solution for anyone else. Go to Storage, then tap the icon in the top right corner and select USB connection. Tick MTP.
Click to expand...
Click to collapse
Hi
So I've just download a rom and superscript on my eee pad and went into cwm and run the superscript. Unfortunately, that wiped everything from my tablet so, I tried to install the rom but the files deleted and I put the rom on an external sd but cwm won't read that. The only thing I can do is access recovery and that's it :/
Can anyone help please!? Thankyou!
I've just got this problem fixed with help from user gee one. Check my recent posts.
rohaan06 said:
Hi
So I've just download a rom and superscript on my eee pad and went into cwm and run the superscript. Unfortunately, that wiped everything from my tablet so, I tried to install the rom but the files deleted and I put the rom on an external sd but cwm won't read that. The only thing I can do is access recovery and that's it :/
Can anyone help please!? Thankyou!
Click to expand...
Click to collapse
You have to change recovery so Look at easy flasher thread, it helps you to push better recovery/return to stock etc..
Download easy flasher and universal naked drivers and install them, before you install anything read the instructions patiently and then go about working on your tablet.
Remember remove all existing Asus drivers before you install universal naked driver, Also use patience while installing drivers, if windows doesn't install then " unzip the driver files into a folder and go to device manager and select Asus tablet/unknown device and update driver/install driver" .
Once you have installed driver its just the matter of plugging your tablet in APX mode(press volume up and power buttons together for few secs) and clicking on your laptop... remember in APX mode tablet won't show anything than few letters on top in very small font... once you are in APX mode use the easy flasher to go back to stock then you can root and install "twrp" recovery as its the best.
Sent from my Transformer using xda app-developers app
Hello everyone and thanks in advance for anyone replying to my dumb question.
Today I was preparing to use the Aroma Toolkit to restore my phone to a basic stock. I placed it in a folder called ".rom" on the internal sdcard so it would appear at the top. (can you believe it?) I have CWM Red and it doesn't see ".rom" as it is now hidden. (I guess) Unfortunately, I already wiped AND formatted "system" so I can't boot the phone up to change the folder to something more sensible. I cannot restore from Odin OR Heimdall because my phone won't show up on ANY PC and it only shows "Unknown USB Device." I've been up and down with that one too. Also, I tried to put the toolkit on the external sdcard both as is and as update.zip but it says there are no files. I think my only way(s) out of this would be to Odin or Heimdall, if I can get either working again, or if there is a way to get the CWM Red to see that hidden ".rom" folder.
ANY help at all would be greatly appreciated.
Thanks for reading this.
folders and files that begin with a dot are hidden in linux systems like android. you are seeing an unknown device because you dont have samsung drivers installed. you should be able to go into mounts and storage and select usb mass storage or something like that and it will mount as a mass storage device where you can rename the file in windows where that doesnt show as a hidden file.
if you wiped system, if you turn off your device, you might not be able to get back into recovery and youll have to use odin or heimdall. you can download the samsung drivers from http://d-h.st/xEG and when you are in recovery mode, go to device manager and select from the list of device and choose samsung composite device or something like that i dont remember.
next time you want a folder to show at the top of the list, i think you can start it with an underscore. i could be wrong about that though. you can try it out and see.
I don't recall if red CWM has the mount as usb storage option. If not...
Next step is getting the drivers on your PC. Easiest option from there is Odin or Heimdall - unless you want to download the android SDK and use adb shell to rename the directory.
Underscore should work for sorting...
fwiw I use exclamation points.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Thanks for the reply! Although I did have the Samsung drivers installed with Kies mini, I removed Kies and installed the drivers in the link you gave me but no luck. USB used to work fine in Win as well as Lin but it stopped suddenly. I am able to get into both recovery and download mode fine but I can't go anywhere from there. I tried to "mount sd_ext" under mounts and storage in recovery, hoping to access the aroma toolkit file from there, but I get a can't mount error that says /dev/block/mmcblklb1p2 (file exists). "mount USB" doesn't help either. I really did it this time....
Thanks again for the input
well, if youre not going to download mode to run odin, and you cant do usb mass storage in red cwm, and you want to do it from recovery, you need to choose samsung adb device in device manager. then you need adb and can do adb shell and run "mv /sdcard/.rom /sdcard/_rom"
mrpectate said:
Thanks for the reply! Although I did have the Samsung drivers installed with Kies mini, I removed Kies and installed the drivers in the link you gave me but no luck. USB used to work fine in Win as well as Lin but it stopped suddenly. I am able to get into both recovery and download mode fine but I can't go anywhere from there. I tried to "mount sd_ext" under mounts and storage in recovery, hoping to access the aroma toolkit file from there, but I get a can't mount error that says /dev/block/mmcblklb1p2 (file exists). "mount USB" doesn't help either. I really did it this time....
Thanks again for the input
Click to expand...
Click to collapse
sd_ext in red recovery does not refer to the external sd card (even though you would think it does from the name)
For compatible drivers, remove all Samsung phone related drivers from your system and install the first driver package located here (not the mini-kies one):
http://www.samsung.com/us/support/owners/product/SGH-I997ZKAATT
Some things that may help:
http://forum.xda-developers.com/showthread.php?t=1982306&page=2
Also, turn off auto driver install in Windows 7 - could be your PC is deciding what is best for you before you can install working drivers:
Go to Control Panel > System > Advanced System Settings > Hardware > Device Installation Settings > "No / Never"
Then install the driver, then connect your phone. Once the driver and devices are fully installed you can change the above setting back to what it was or to "No / Install" (that's where I usually leave it)
Good luck
Well I sincerely appreciate all the help from you guys, and Zen Arcade, thanks for the toolkit that brought me back from disaster quite a few times. I tried all of your suggestions, but it seems like I might have a hardware failure which occured before all this. I was able to connect to USB fine and out of nowhere it just wouldn't anymore. That was OK. I still rom-hopped along with straight to phone rom aquisition, but then I made a mistake. One I have learned from. I'm not able to get the phone to show up AT ALL. I even tried a clean install of WinXP then the drivers from Zen's post, and Nicky's Win7 laptop. I also tried several versions of Linux. Only Mint's Gparted could see it as /sdb/ with a corrupted partition. I even gave Haiku's Drive Probe a shot. Jack of Clubs, I tried the SDK shell but it just scans and sees nothing. I just think that the USB thing is roadblocking any hope of saving this heap. Recovery is there, download mode is there, but the connection required to utilize either of those is gone.
Again, I truly appreciate the help.
Well I've been trying to get CWM to see the Infuse Toolkit (and various roms) on external_sd but it keeps saying:
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(Invalid argument)
E:Can't mount /sdcard
I've tried 4 different microSD's formatted as FAT, FAT32, and I used SDFormatter (I saw someone recommend that somewhere). I really see this as the very last ember of hope for this phone before I let it go.
Any ideas?
BTW, my CWM is v2.5.1.3 - Voodoo lagfix
Thanks again and in advance.
Infuse GB recovery menu will not see external SD card.
If you can get adb working - connection to your PC - you have some options. From adb there are commands that will allow copying files from PC to phone ... also from external to internal sd card depending on which kernel you are running. You could also rename your hidden folder too.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Thanks again for your continued help Zen. I just can't get it recognized (in a constructive way) by anything. I tried Santoku linux today and nothing. I've just been beating my head with this thing. Well here it is: CWM is accessible, as is download mode, and it charges fine, but no PC connection. When it was given to me, the glass was cracked, but it always worked fine for me. It's in a Ballistic case. If your interested in it, I'll be happy to send it to you, even if it's just for parts. I loved this phone, and had a lot of fun with it. (thanks to this community and all of its' contributors) I think it's time to move on.
I'm gonna start looking at a phone with a good selection of custom roms cuz I just love flashin' 'em
Let me know if your interested in this phone Zen.