Hello.
Yesterday I bought Toshiba Folio 100 tablet. After first run, I ran update (from 02.2011). When I downloaded it, I turn on this update. After the moment, tablet has been restarted. Instead Android screen, I saw Toshiba logo and message "booting recovery kernel image". I think it's okey, i left this tablet for night. In the morning, I didn't see no change, so I restarted tablet.
On this forum I found the way to fix this problem (instruction for install Foliomod), but in my computer, it doesn't work. After install Android SDK, I modifed android_winusb.inf, I turn on folio 100 in fastboot mode. System doesn't find drivers, and I can choosed only folder with driver, not exactly file, so I select usb_driver folder. Driver has been installed, but no one info doesn't shown. After run fastboot.exe, window appears and quickly disappears.
What can i do? Without update tablet's working so slowly.
I please for your help.
Related
So I have a Samsung Focus running Mango 7712. I had no issues updating to that, no 'walshed' phone or whatever it's called. I have been trying and looking for solutions for 3 days now on how to update to Mango 7720 but I'm stuck now and nothing seems to work, so I'm hoping someone can shed some light on this.
I have:
1. All the proper drivers installed I'm pretty sure
2. Zune 4.08.2134
3. The 7720.rar and everything extracted directly and properly to the C: drive. I even uninstalled the update tool I had and installed the one that was located in the 7720.rar folder.
So here's my issue:
When I go to run the .bat file as an administrator, everything starts fine, transfers the updates, perfect...except when it gets to "restarting phone". That's when the problem occurs. I feel like it hangs on the 'Goodbye' screen too long, and THEN the command prompt just quits...a few seconds later the phone finally restarts and is stuck on the screen that says to plug it into the computer. So I have to pull battery and restart...obviously with 7712 still on there
I have tried to clear up more space on the phone ( I have 8.0GB free), I have tried unplugging and plugging the USB back in, just trying to restart the .bat file while it's stuck on that screen (to no avail), and I have tried 'pausing' the process in the command prompt until the phone gets back up to the connect to PC screen- but then when I resume the command...it just auto closes.
PLEASE someone help...I'm tired and can't find any solutions
Thanks to any replies in advance.....
I had the same issue. Instead of right-click, Run As Admin, try running the .bat by double-clicking. It still took quite a while for my Focus to reboot, but it finally restarted before the tool timed out.
Also, make absolutely sure all folders are in the C:\ drive. When I first extracted 7720.rar to the C:\ drive, it actually put everything into C:\MANGO. So I had to move it all to C:\ before anything would work.
Hope that helps.
GAlonzo said:
I had the same issue. Instead of right-click, Run As Admin, try running the .bat by double-clicking. It still took quite a while for my Focus to reboot, but it finally restarted before the tool timed out.
Also, make absolutely sure all folders are in the C:\ drive. When I first extracted 7720.rar to the C:\ drive, it actually put everything into C:\MANGO. So I had to move it all to C:\ before anything would work.
Hope that helps.
Click to expand...
Click to collapse
sigh....thanks for the idea but it didnt help still nothing
maybe this can help
ISVTo7720.bat Hangs on restarting phase/Error 801812c1 after run
This was the most common Error listed and had many solutions which seemed to work sporadically.
1. Do what @DavePerman said, and use the pause command so freeze the cmd command until phone reaches flashing phase.
2. Execute ISVTo7720.bat in a standalone CMD instead of through Windows Explorer. Do this by Run(open as Admin)>cmd>cd Mango>cd RCToRTM>ISVTo7720.bat
3. Remove all music from the device to free up 6+ gigs of memory.
4. Have at least 12 gigs of hard drive space on your computer. Some clam they needed 20
5. press the off button on the phone to force the phone into its flashing screen. (some say they pressed the button, some say they held it down until the screen turned off)
5. The most extreme, and last resort for this problem is to reset your phone through its settings menu. You will lose all information on the phone. (remember your contacts and apps are all in the cloud, so they can be recovered. Music/pictures/videos can be re-synced if backed up before hand.)
nothing seems to work
zune is not running while ur doing this is it ?
make sure zune is not running also try uninstall and reinstall the phone drivers...
bigtime1 said:
zune is not running while ur doing this is it ?
Click to expand...
Click to collapse
No I even killed off all processes with zune in them
also try uninstall and reinstall the phone drivers...
yea I did that, but I'm pretty certain its not the drivers since the phone rebooted, it just hangs...
did u install the windows phone developers tools 7.1
bigtime1 said:
did u install the windows phone developers tools 7.1
Click to expand...
Click to collapse
Yup I have them installed
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.
Hi all,
I ran into a problem with KFU 0.99 and got around it, but I have a question for the next time I root a device.
Basically, unzipped, ran install_drivers, checked Soupkits "ADB checklist" and started up. My device hung at fastboot and needed Soupkit to force it back into normal mode. The problem was the android_winusb.inf file did not have the device IDs that my machine assigned to my Kindle. Once I corrected the file in KFU, deleted the drivers and re-installed, all was well.
My question is -- do I *have* to reinstall the drivers when this happens, or can I simply update the INF file in the \windows\system32\drvstore\androidxxx directory and reboot.
Thanks in advance.
Pat
texnnyc said:
Hi all,
I ran into a problem with KFU 0.99 and got around it, but I have a question for the next time I root a device.
Basically, unzipped, ran install_drivers, checked Soupkits "ADB checklist" and started up. My device hung at fastboot and needed Soupkit to force it back into normal mode. The problem was the android_winusb.inf file did not have the device IDs that my machine assigned to my Kindle. Once I corrected the file in KFU, deleted the drivers and re-installed, all was well.
My question is -- do I *have* to reinstall the drivers when this happens, or can I simply update the INF file in the \windows\system32\drvstore\androidxxx directory and reboot.
Thanks in advance.
Pat
Click to expand...
Click to collapse
OK - from experience ... You *need* to uninstall and reinstall the drivers after you update the INF file.
Good Evening,
I have a Motorola G.
I was running a rooted version for a while, although I am admittedly not an expert. however, i did follow the steps and it was working fine, for about a year.
Well today i was low on internal memory space available, and tried transferring some more data onto it. I didn't realize the size of the data. I got a message from the computer saying there was no more space, and unplugged and went to work.
Phone was not really responsive, but I figured I would delete a couple things once I got to work until I could clear it out.
I took phone out, and it's on a black screen. I tried to restart it, it's freezing at the blue M .
Nothing seems to work, I think the memory is just so full the phone can't even boot, so I decided to do a hard reset. Unfortunately, I'm having some difficulty. I've downloaded and installed the updated Composite ADB Driver from Google, and it DOES show in the Device Manager when I plug in the phone.
I've also downloaded the SDK manager and updated it. I plug the phone in and administratively launch a command prompt. I direct the Command Prompt to the folder containing a recovery.img file, and from that point I am lost. The computer doesn't seem to identify the phone , i'm getting either or error: Device not found.
I'm not sure what I've done wrong, I am sure i'm using the newest ADB Drivers......
I tried the "adb devices" within the command prompt, and in that case it comes up blank....
Can someone please help me?
Thank you....
I got this Surface recently and like dozens of others the touchscreen stopped working.
I tried everything.
-Let the battery drain.
-Resetted it via its internal recovery (delete everything)
-Deinstalled Firmware Touch (2.1.15.0 - 12.08.2013) and Firmware Configuration (0.0.33.0 - 12.08.2013)
-HID Touchscreen (6.3.9600.16384 - 21.06.2006)
-Restarted
-Windows Installed just "Firmware" then and claimed its the newest one...:silly:
-I read there was Firmware 2.1.17.0 (but only for Surface 2 WiFi... (?)
-And I read about KB3172729 which led to this problem according to this link :
https://forums.windowscentral.com/microsoft-surface-2/313399-2.htm
But its a 2016 KB and my Surface got its last updates in 2014.
-I read about custom Recovery Images...but only downloaded an original recovery from MS (Surface2_BMR_20.2.19.0.zip)
which I installed (deleted TPM via F12) and only had issues whiel entering a password for the user...cursor dissapeared and it was laggy as hell.
It installed but no touchscreen.
Time to ask on xda I thought...also Id love to get back to Windows 8.0 RT if possible. (?)
Thanks in advance.
Desperately I did now try :
Stopped service "Windows Update"
Deleted all files in: C:\Windows\SoftwareDistribution\download (it did indeed have 4 temp folders with updates from today)...
-cmd (as admin)
-DISM.exe /Online /Cleanup-image /Restorehealth
100% restore operation completed succesfully
-sfc /scannow
Verification up to 100%, no problems found. -_-
Then started Windows Update. "searching for updates"...it took 10 minutes and showed all updates, including a Firmware (09.11.2015) and the "evil" KB3172729.
I just selected the Firmware thing, which turns out indeed to be the 2.1.17.0 (07.10.2015). Surface restarted and I
got the yellow exclamation Mark in the device manager at the Firmware...like many others before me...just great -_-
Additonally The Microsoft Management Console stopped working...wow...
Still, no touchscreen.
https://www.errorsolutions.tech/error/windows-update-error-code-80244010/
Trying to re-update the firmware keeps showing a "Searching online for drivers"...I cant cancel it.
Installed 1,5GB updates now, without the "evil" KB3172729.
No touchscreen.
I start to regret getting my hands on this device. Seriously Microsoft, wtf ?
Mario,
did you find any solution yet? I tried everything also and still not working.
iResmas
me too ... I got a surface 2, I tried different ways to find a solution for the problem of ''touch firmware = Yellow exclamation mark on it in Device manager'' and still not working.
I downloaded all given updates, but nothing happened, still not working.
PLZ .... guide me to find the right SOL.