Related
Hi, I tried to install a rom such as an update (I took the update.img into the root of my archos and It started to update) but when it rebooted It did not start ... So I bricked my Archos 7 HT ;(
Do you know how can I unbrick my archos 7 ht, please ???
(Sorry for my poor english, but I am italian...)
Sent from my iPhone using Tapatalk
Anyone can help me ???
;((
Sent from my iPhone using Tapatalk
Hi,
look here:
http://forum.archosfans.com/viewforum.php?f=59
Then also watch "unbrick APAD" these are the same platforms RK2808.
http://www.slatedroid.com/index.php?topic=5092.0
http://www.youtube.com/watch?v=rqSydpZumno
Good luck
anyone knows where can i download rmandroiddm.exe ?
I restored it using this tuto
If you have a device which is not recognizable by the PC:
You need a 32-bit Windows (I used WinXP VMware player image from my Win7 64-bit)
In my case connecting the device to the PC did not resulted in access to the memory, only the drive letters appeared, but could not be mounted.
At the same time, the RKandroid tool did not recognize the device at all.
So, we need to reflash the archos 7ht. For this we need to enter update mode - and here is the trick:
1. Shutdown the tablet (in my case - pin reset shutdowns it)
2. LOCK the sliding button (for me this was the tricky part to find out)
3. Connect the USB cable and the powercable.
4. The winXP should detect a new USB device. Make him happy - give him the rk28usb-new drivers to install.
5. Now the RKAndroidTool.exe should be able to detect the RKandroid USB device.
Ok, if you've got this far, now we need to re-flash it. For safety, let's do this with the default Archos 7HT update image (which can be downloaded from the Archos website)
I think that the RKAndroidTool.exe needs extracted files from update.img. For this, extract them using AFPTool.exe:
AFPTool.exe -unpack update.img .
(or use the extractupdate.bat)
Now, we can finish the reflashing:
6. Start RKAndroidTool.exe.
7. If the extracted files from update.img are placed in rockdev folder and in image subfolder, the RKAndroidTool.exe should find them automatically.
8. Execute. Make sure the device is plugged to AC, because the process takes some time. IF THE PROCESS STOPS UNEXPECTEDLY YOU GET A HIGH-TECH BRICK (or so everyone says, I didn't test it).
9. You should see the device responding and starting the update process. It will take some time, dont ruch it.
~20 seconds – copy firmware to device,
~30 seconds – device firmware installation,
~3-8 minutes - First boot
10. The Archos Tablet should ask you to recalibrate the screen, and load the OS.
That's it. Good luck!
==========================================
Sent from my iPhone using Tapatalk
1. Turn on xformer with power button - stuck at Asus Eee Pad screen
2. Try to boot into recovery with vol - + power;
- volume up to enter recovery, ded android with an exclamation
- volume down to choose between 'wipe' and 'cold boot' both result in getting stuck at Asus screen
3. Plug in xformer, hold power and vol +; nothing. windows notice found an unknow device but fail to intall the driver
4 i tried many times to manaual install the apx drivers that posted in the bbs, in device manager it always showed as""unknow device"" instead of ""apx device"" , driver installation fail by auto search the apxusb folder liked everybody said
i was able to force install the apx driver by manaul selected the usb.inf fil. however in device manager it said device is not running correctly error.
i try to rebooy laptop ans the error remain
my tf101 is now softbrick with touch cwm. i could not operate with removeable sdcard but internal sdcar.
the worse thing is i dony have any roms storage in internal sdcard
please anyone can give me a hand？
justinmise said:
1. Turn on xformer with power button - stuck at Asus Eee Pad screen
2. Try to boot into recovery with vol - + power;
- volume up to enter recovery, ded android with an exclamation
- volume down to choose between 'wipe' and 'cold boot' both result in getting stuck at Asus screen
3. Plug in xformer, hold power and vol +; nothing. windows notice found an unknow device but fail to intall the driver
4 i tried many times to manaual install the apx drivers that posted in the bbs, in device manager it always showed as""unknow device"" instead of ""apx device"" , driver installation fail by auto search the apxusb folder liked everybody said
i was able to force install the apx driver by manaul selected the usb.inf fil. however in device manager it said device is not running correctly error.
i try to rebooy laptop ans the error remain
my tf101 is now softbrick with touch cwm. i could not operate with removeable sdcard but internal sdcar.
the worse thing is i dony have any roms storage in internal sdcard
please anyone can give me a hand？
Click to expand...
Click to collapse
Further more
When i pressed V+& Power tf101 screen turn off and window found a unregonized device.
But, window only show" unknown device" instead of "APX" Device which yellow A! remark.
Did any one know how to slove this issue, i tried every drivers file i can file in this bbs but none of them work.
thx
justin
Did you install the APX driver?
You can find it with the nvflash package
baseballfanz said:
Did you install the APX driver?
You can find it with the nvflash package
Click to expand...
Click to collapse
hi
thx for ur reply
i tried to install the APX driver but fail
window pop up and said it found a new device and can not recongized.
device manager recongized it as a "UKNOW Device" With out Yellow ! remark.
as i read in other posts it should read as " APX" with yellow remark.
i also try to froce install the driver but fail again.
It means both WINXP and WIN 7 64bit not able to recongized my TF correctly,
device manage keep show " unknow device" but not able to indentity it as a APX device.
what steps am i missing ?
Exact same problem
I am at the same place as this person.
I Booted into CWM Recovery 5.5.0.4 and I can't get back out. I tried wiping. I had an update.zip on my internal SD card. I've tried everything I've seen on the forums. and NOTHING. On windows I get an Unknown Device in both APX and ADB and ADB won't recognize the device. ADB works fine on all of my other android devices. I feel like i've got a 200 door stop. PLEASE HELP!
My device is a B50 TF-101 SBK1
I'll give anyone that can help me solve this $40 through paypal.
Thanks!
Download universal naked driver from easy flash thread.. unzip the drivers into a folder.. Go to device manager in your laptop and look for that unknown device and there double click on unknown device and select update/install driver.. point the installation to the unzipped folders and click update driver and this should install apx drivers and you should be good to go as that's what I did. Its very easy so take your time and do it...
Sent from my Transformer TF101 using xda app-developers app
udupa82 said:
Download universal naked driver from easy flash thread.. unzip the drivers into a folder.. Go to device manager in your laptop and look for that unknown device and there double click on unknown device and select update/install driver.. point the installation to the unzipped folders and click update driver and this should install apx drivers and you should be good to go as that's what I did. Its very easy so take your time and do it...
Sent from my Transformer TF101 using xda app-developers app
Click to expand...
Click to collapse
Same problem ! dosn't work even with naked driver any solution yet ?
mickz said:
Same problem ! dosn't work even with naked driver any solution yet ?
Click to expand...
Click to collapse
Try plugging your tf101 into another usb port and installing the naked drivers.
I am at the same place as this person.
I Booted into CWM Recovery 5.5.0.4 and I can't get back out. I tried wiping. I had an update.zip on my internal SD card. I've tried everything I've seen on the forums. and NOTHING. On windows I get an Unknown Device in both APX and ADB and ADB won't recognize the device. ADB works fine on all of my other android devices. I feel like i've got a 200 door stop. PLEASE HELP!
My device is a B50 TF-101 SBK1
Click to expand...
Click to collapse
Remove the apx drivers you already have and try installing them again by following these steps:
1- Boot up your transformer into apx mode.
2- Goto device manager and right click on the unrecognized device and goto update drivers.
3- Manually point them to the Folder you extracted have the universal naked drivers and install them. Scan for hardware changes
4- Hopefully your transformer will be recognized in the apx mode.
5- Download the EasyFlasher tool from http://forum.xda-developers.com/showthread.php?t=1688012
6- open EasyFlasher and Choose your device SBK1 or SBK2
7- Flash a new recovery on the transformer with the tool and reboot it.
8- You will have the access to your external sd card where u have ur ROM stored.
These step did the trick on my transformer. Hopefully your problem will be solved.
Hit thanks if i have helped in any way!!
konark500 said:
Remove the apx drivers you already have and try installing them again by following these steps:
1- Boot up your transformer into apx mode.
2- Goto device manager and right click on the unrecognized device and goto update drivers.
3- Manually point them to the Folder you extracted have the universal naked drivers and install them. Scan for hardware changes
4- Hopefully your transformer will be recognized in the apx mode.
5- Download the EasyFlasher tool from http://forum.xda-developers.com/showthread.php?t=1688012
6- open EasyFlasher and Choose your device SBK1 or SBK2
7- Flash a new recovery on the transformer with the tool and reboot it.
8- You will have the access to your external sd card where u have ur ROM stored.
These step did the trick on my transformer. Hopefully your problem will be solved.
Hit thanks if i have helped in any way!!
Click to expand...
Click to collapse
I can't thank konark500 enough. I had previously installed ClockworkMod Touch Recovery using the img file using the instructions on the Cyanogenmod Wiki. It worked, but every time I rebooted it would reboot back into flash and I would have to vol- at reboot to get it to boot to Android. Using EasyFlasher I was able to install TWRP and I am so glad I did. Everything is running better and I boot straight to Android when I need to. TWRP also has a way to wipe system. I was having strange issues with bluetooth and wifi others were not having until I wiped system and started over.
Thanks again konark500
Hi,
Sorry to resurrect a dead thread, but I am facing a similar issue. I installed a bad CWM recovery and since then I am not able to use my TF101. I tried to install the Naked drivers, but it does not work. I tried changing ports, but still the same issue. Please help. I am using Windows 8.1.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My guess - your TF101 cable is bad. I had a bad one but it still works with the wall wart to charge. One of the Data + or - cables is disconnected. Try a new cable is my best suggestion.
I searched the forums but couldn't find any answers. This is the first time I'm trying to root an android phone. Things are not going well..
I found a page in Indonesian with instruction on how to root my sister's Lenovo S890. My dad bought her one in China, we live in Europe.
We need to get all the Chinese stuff off and install a "regular" Android version with a normal marketplace (read: whatsapp and google and nothing blocked).
The page with instructions is at http://www.duniaku.net/2013/03/30/u...rtisi-internal-storage-lenovo-ideaphone-s890/ I used Google Translate.
What are the steps? First you need to set up some files such as drivers are required to carry out the process of flashing, SP Flash Tool version 3.1222 or higher, because Lenny chipset MTK6577 S890, S890 and file TWRP to also file a Super User and Busybox will be pushed into the system through TWRP. All the files you can download from the following link:
1 Download Driver Lenovo : Extract file. rar it and then click Install_Driver.exe to install drivers into the system. Rather long process, just wait.
2 Download SP Flash Tool : The author gave the newer version, which v3.1224.01. .
3 Download Team Win Recovery Project : TWRP file is specific to the Lenovo S890, so do not try for another Android, although it also MediaTek chipset.
4 Download Super User and Busybox : Will we push into the system through TWRP custom recovery. Download and copy directly to SD Storage / Memory Cards-mu. Place it outside the / root folder or USB Storage Storage SD / USB storage from your Lenovo S890.
5 Download Data Repartition : This file is optional, just download and place it in the root folder Storage SD / USB Storage. Can later be used to repartition the internal memory is too small Lenovo S890. Author will explain at the bottom.
Click to expand...
Click to collapse
I first installed the Lenovo S890 drivers. Clicked "Install anyway" for everything and rebooted. No problems.
But when I connect the phone it's still complaining that it can't find drivers (and I can't find any official drivers on the Lenovo website either)?
I also installed the MT6577 USB VCOM drivers that I found here http://forum.xda-developers.com/showthread.php?t=2206421 (before I did this the SP Flash Tool did nothing).
I enabled USB Debugging mode on the phone, and took out the SIM, the SD card and the battery when I connect it to USB to the PC. I am running Win7x64.
Every time I try to run (step 2) SP Flash tool, it starts downloading fine, but then Win7 'spits out' the phone (I can hear the 'usb device disconnected' sound) and SP Flash Tool obviously stops working then and gives some error.
I think this is because the MediaTek MT6577 USB VCOM drivers somehow refuse to install correctly? It looks like rooting might go well once this driver thing is fixed?
When I force installation of the drivers I get a Code 10 error and a yellow triangle next to the Preloader and the MediaTEL Vcom something USB driver in Windows Device Manager. ( I searched the forums and didn't find a solution for this).
I forced installation by opening Device Manager, click Add, click Add Legacy Hardware - manual - choose the usb2ser_Win764.info file out of the MT6577 USB VCOM drivers folder
This is what's in the .inf file : Is there anything I can change here to force it to work?
[Version]
Signature="$Windows NT$"
Class=Ports
ClassGuid={4D36E978-E325-11CE-BFC1-08002BE10318}
Provider=%MTK%
DriverVer=05/30/2011,1.1123.0
[Manufacturer]
%MTK%=MTK,NTamd64
[MTK.NTamd64]
%MTK6218%=Reader,USB\Vid_0e8d&Pid_0003,USB\Vid_0e8d&Pid_1003
%MTK_COM%=Reader,USB\Vid_0e8d&Pid_0023&MI_00
%MTK_CAT%=Reader,USB\Vid_0e8d&Pid_0023&MI_02
%MTK_PRELOADER%=Reader, USB\Vid_0e8d&Pid_2000
%MTK_SP_DA%=Reader, USB\Vid_0e8d&Pid_2001
[DestinationDirs]
DefaultDestDir=12
[Reader.NTamd64]
Include=mdmcpq.inf
AddReg=Reader.NTamd64.AddReg
CopyFiles=FakeModemCopyFileSection
[Reader.NTamd64.AddReg]
HKR,,DevLoader,,*ntkern
HKR,,NTMPDriver,,usbser.sys
HKR,,EnumPropPages32,,"MsPorts.dll,SerialPortPropPageProvider"
[Reader.NTamd64.Services]
AddService = usbser, 0x00000002, Service_Inst
[SourceDisksNames]
[SourceDisksFiles]
[Service_Inst]
DisplayName = %Serial.SvcDesc%
ServiceType = 1 ; SERVICE_KERNEL_DRIVER
StartType = 3 ; SERVICE_DEMAND_START
ErrorControl = 1 ; SERVICE_ERROR_NORMAL
ServiceBinary = %12%\usbser.sys
LoadOrderGroup = Base
[Strings]
MTK = "MediaTek Inc."
MTK6218 = "MTK USB Port"
MTK_COM = "MTK USB Modem Port"
MTK_CAT = "MTK USB Debug Port"
MTK_PRELOADER = "MediaTek PreLoader USB VCOM Port"
MTK_SP_DA = "MediaTek DA USB VCOM Port"
Serial.SvcDesc = "USB Serial emulation modem driver"
Click to expand...
Click to collapse
How do I stop Windows from ejecting the phone (force it to keep it connected as the MediaTek thingie that seems to work with SP Flash Tool?).
Or is there a better way to get an English Android version on this phone?
When I now try to boot the phone it says
tool dl image fail
uboot is blocking by dl info
Did I (soft)brick it??
Thanks in advance for all the help!!
Giving up
Since this seems to be a less popular phone with very little support available - I'm giving up.
Spent 3 full days on this thing with no results, and I just read the GPS also won't work outside of China either.
Now all I need to do is figure out how to get it out of META mode or Factory mode, and get it to boot back into it's normal Chinese Android system.
katejones said:
Since this seems to be a less popular phone with very little support available - I'm giving up.
Spent 3 full days on this thing with no results, and I just read the GPS also won't work outside of China either.
Now all I need to do is figure out how to get it out of META mode or Factory mode, and get it to boot back into it's normal Chinese Android system.
Click to expand...
Click to collapse
Hi, I'm having a much similar problem, since I couldn't flash recovery with SP flash tool, the process was terminated unexpectedly showing error message s_ft_need_download_all_fail (4050), after a couple of days looking for a solution I decided to format the phone with SP Flash Tool, and it worked, right after I tried to flas recovery again...and it worked. I thought I had found the way but when I tried to boot the phone in recovery mode nothing happened, no matter what keys combination I use, how long I press them, the phone just won't react, it doesn't show anything on the screen.
I don't know if this was the logic step to follow, but if you want to try and discover what to do next, up to you, 4 hands are better than 2,maybe yuo find the solution.
Good luck.
There is no button combination to boot recovery, try droidgram-reboot on play store.
Sent from my Lenovo S880
Hope you guys manage to root it soon as I am one of those who waiting for it as I need to root my S890 also.
Sent from my Lenovo S890 using xda app-developers app
katejones said:
I searched the forums but couldn't find any answers. This is the first time I'm trying to root an android phone. Things are not going well..
I found a page in Indonesian with instruction on how to root my sister's Lenovo S890. My dad bought her one in China, we live in Europe.
We need to get all the Chinese stuff off and install a "regular" Android version with a normal marketplace (read: whatsapp and google and nothing blocked).
The page with instructions is at http://www.duniaku.net/2013/03/30/u...rtisi-internal-storage-lenovo-ideaphone-s890/ I used Google Translate.
I first installed the Lenovo S890 drivers. Clicked "Install anyway" for everything and rebooted. No problems.
But when I connect the phone it's still complaining that it can't find drivers (and I can't find any official drivers on the Lenovo website either)?
I also installed the MT6577 USB VCOM drivers that I found here http://forum.xda-developers.com/showthread.php?t=2206421 (before I did this the SP Flash Tool did nothing).
I enabled USB Debugging mode on the phone, and took out the SIM, the SD card and the battery when I connect it to USB to the PC. I am running Win7x64.
Every time I try to run (step 2) SP Flash tool, it starts downloading fine, but then Win7 'spits out' the phone (I can hear the 'usb device disconnected' sound) and SP Flash Tool obviously stops working then and gives some error.
I think this is because the MediaTek MT6577 USB VCOM drivers somehow refuse to install correctly? It looks like rooting might go well once this driver thing is fixed?
When I force installation of the drivers I get a Code 10 error and a yellow triangle next to the Preloader and the MediaTEL Vcom something USB driver in Windows Device Manager. ( I searched the forums and didn't find a solution for this).
I forced installation by opening Device Manager, click Add, click Add Legacy Hardware - manual - choose the usb2ser_Win764.info file out of the MT6577 USB VCOM drivers folder
This is what's in the .inf file : Is there anything I can change here to force it to work?
How do I stop Windows from ejecting the phone (force it to keep it connected as the MediaTek thingie that seems to work with SP Flash Tool?).
Or is there a better way to get an English Android version on this phone?
When I now try to boot the phone it says
tool dl image fail
uboot is blocking by dl info
Did I (soft)brick it??
Thanks in advance for all the help!!
Click to expand...
Click to collapse
please use S890_Customized_SP_Flashtool_20121119(v3.1238.5)
flash again ok
i am solve same your problem
https://www.dropbox.com/s/pwvg553v5z1vtju/S890_Customized_SP_Flashtool_20130109(v3.1238.5).rar
kyaw8719 said:
please use S890_Customized_SP_Flashtool_20121119(v3.1238.5)
flash again ok
i am solve same your problem
https://www.dropbox.com/s/pwvg553v5z1vtju/S890_Customized_SP_Flashtool_20130109(v3.1238.5).rar
Click to expand...
Click to collapse
Thanks for sharing. Is it 100% working or still in testing phase?
Sent from my Lenovo S890 using xda app-developers app
nakTT said:
Thanks for sharing. Is it 100% working or still in testing phase?
Sent from my Lenovo S890 using xda app-developers app
Click to expand...
Click to collapse
i fix 2pcs
kyaw8719 said:
i fix 2pcs
Click to expand...
Click to collapse
Meaning?
Sent from my ST26i
doesn't solve the problem
nakTT said:
Meaning?
Sent from my ST26i
Click to expand...
Click to collapse
It doesn't work same problem downloaded the latest SP Flash from the post doesn't work either.. Is there any of you solved the problem? If so then please go detailed about it.
I apologize if this has been answered elsewhere but after hours of trying to figure this out on my own (with search), I'm posting for help. I'm going to provide as much info as I can. Thanks in advance
I had CleanRom 2.3 installed and totally flubbed upgrading to something else. I current have TWRP v2.5.0 installed but no OS.
In the upper left corner on the bootloader screen it says the following
Key driver not found.. Booting 05
Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.14.4-20130329" A03
Starting Fastboot USB download protocol
I see 3 icons "RCK, Android, Wipe Data"
In the mount menu the only things checked are "cache, data, micro SDcard" (not system). I can manually check system.
I am trying to flash the stock rom found here: http://forum.xda-developers.com/showthread.php?t=2223918 (I don't care if I need to go to a different rom, I just want my tablet to work)
When installing it says successful, however the readout above says "Checking for MD5 file... // Skipping MD5 check: no MD5 file found."
When I reboot it prompts me to install SuperSU, device does not appear to be rooted. If I swipe to install the screen immediately goes black and begins reboot. It gets to Asus boot screen with the blue bars, loads the bars and then reboots again. It will hang on Asus screen if I don't go into bootloader.
I have tried going into TWRP and using the advanced wipe to format everything prior to installing and it did not help.
I have tried installing the SDK on my computer to run fastboot, but when plugging in to my PC, it does not recognize the android device.
I'm sorry but I seem to have bit off a bit more than I can chew with this stuff and may need quite a bit of help here. Thanks for anybody willing to help me
skaplan86 said:
I apologize if this has been answered elsewhere but after hours of trying to figure this out on my own (with search), I'm posting for help. I'm going to provide as much info as I can. Thanks in advance
I had CleanRom 2.3 installed and totally flubbed upgrading to something else. I current have TWRP v2.5.0 installed but no OS.
In the upper left corner on the bootloader screen it says the following
Key driver not found.. Booting 05
Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.14.4-20130329" A03
Starting Fastboot USB download protocol
I see 3 icons "RCK, Android, Wipe Data"
In the mount menu the only things checked are "cache, data, micro SDcard" (not system). I can manually check system.
I am trying to flash the stock rom found here: http://forum.xda-developers.com/showthread.php?t=2223918 (I don't care if I need to go to a different rom, I just want my tablet to work)
When installing it says successful, however the readout above says "Checking for MD5 file... // Skipping MD5 check: no MD5 file found."
When I reboot it prompts me to install SuperSU, device does not appear to be rooted. If I swipe to install the screen immediately goes black and begins reboot. It gets to Asus boot screen with the blue bars, loads the bars and then reboots again. It will hang on Asus screen if I don't go into bootloader.
I have tried going into TWRP and using the advanced wipe to format everything prior to installing and it did not help.
I have tried installing the SDK on my computer to run fastboot, but when plugging in to my PC, it does not recognize the android device.
I'm sorry but I seem to have bit off a bit more than I can chew with this stuff and may need quite a bit of help here. Thanks for anybody willing to help me
Click to expand...
Click to collapse
It is a bug in the twrp.. Go to mount and check the box for /system. Shutdown your device completely without install anything when asks for a few seconds and boot back into your twrp. Go back to mount and check to see if your system is mounted. If it is mounted, then you can install the ROM that you like, good luck...:fingers-crossed:
LetMeKnow said:
It is a bug in the twrp.. Go to mount and check the box for /system. Shutdown your device completely without install anything when asks for a few seconds and boot back into your twrp. Go back to mount and check to see if your system is mounted. If it is mounted, then you can install the ROM that you like, good luck...:fingers-crossed:
Click to expand...
Click to collapse
Thanks for the tip! It didn't work I loaded into TWRP. went into Mount and checked the system partition. Then went to Reboot and selected Power Off. No OS Installed, swiped to power off. When prompted to install SuperSU I selected Do Not Install.Left off for about 5 minutes
After booting into TWRP again, system is not showing as mounted.
skaplan86 said:
Thanks for the tip! It didn't work I loaded into TWRP. went into Mount and checked the system partition. Then went to Reboot and selected Power Off. No OS Installed, swiped to power off. When prompted to install SuperSU I selected Do Not Install.Left off for about 5 minutes
After booting into TWRP again, system is not showing as mounted.
Click to expand...
Click to collapse
It happens to me a few time in the past and that was how I fixed the problem. You may want to try that a few time... You could also try to mount the /system and install the new ROM at the same time to see if it works.. Another the solution is to update your twrp to a newer version v2.6.3.1. I don't see that bug any more with that version and let us know if any of those tips is working out for you, good luck...:fingers-crossed:
What is the best way to install the newest version of TWRP? I'm looking here http://teamw.in/project/twrp2/105
I cant do the app install, and fastboot isn't working (pc doesn't recognize device) and I'm not sure how to get it from an external SD card to the internal SD in order to do the ADB/Terminal Method.
Thanks
skaplan86 said:
What is the best way to install the newest version of TWRP? I'm looking here http://teamw.in/project/twrp2/105
I cant do the app install, and fastboot isn't working (pc doesn't recognize device) and I'm not sure how to get it from an external SD card to the internal SD in order to do the ADB/Terminal Method.
Thanks
Click to expand...
Click to collapse
Here is the link for the twrp. Select the version that you like:
http://techerrata.com/browse/twrp2/tf700t
Whatever custom ROM that you choose, you may want to get the bootloader that is going to work for that ROM.
Also, if you have a nandroid backup, you can always restore it to see if it works..
Edit: Oops I did not read carefully. Here is the guide that you could follow, sorry...
http://www.transformerforums.com/fo...ginners-guide-flashing-custom-rom-tf700t.html
LetMeKnow said:
Here is the link for the twrp. Select the version that you like:
http://techerrata.com/browse/twrp2/tf700t
Whatever custom ROM that you choose, you may want to get the bootloader that is going to work for that ROM.
Also, if you have a nandroid backup, you can always restore it to see if it works..
Edit: Oops I did not read carefully. Here is the guide that you could follow, sorry...
http://www.transformerforums.com/fo...ginners-guide-flashing-custom-rom-tf700t.html
Click to expand...
Click to collapse
I really appreciate your help with this, I'm still having trouble even getting that utility working. The linked guide takes me to http://forum.xda-developers.com/showthread.php?t=2588979 which is not installing properly. when it tries to install ADB & fastboot it says " 'setx' is not recognized as an internal or external command, operable program or batch file.
I'm also having driver issues that my pc is not recognizing the device. It sees the unknown device in device manager but when I try to manually add the driver as in that guide it doesn't work the way the guide says it should.
It looks like I'm going to need to spend some time troubleshooting why I can't get fastboot and ADB installed properly. I'll probably try a different PC.
Thanks!
skaplan86 said:
I really appreciate your help with this, I'm still having trouble even getting that utility working. The linked guide takes me to http://forum.xda-developers.com/showthread.php?t=2588979 which is not installing properly. when it tries to install ADB & fastboot it says " 'setx' is not recognized as an internal or external command, operable program or batch file.
I'm also having driver issues that my pc is not recognizing the device. It sees the unknown device in device manager but when I try to manually add the driver as in that guide it doesn't work the way the guide says it should.
It looks like I'm going to need to spend some time troubleshooting why I can't get fastboot and ADB installed properly. I'll probably try a different PC.
Thanks!
Click to expand...
Click to collapse
Since you have SDK tool available, you can try to install the USB driver from this guide and instead using USB driver, you can use the naked driver from this download:
http://developer.android.com/sdk/win-usb.html
http://forum.xda-developers.com/showthread.php?t=2513339
You may want to manually install your driver from your device manager on your pc.
When you are browse to the naked driver, you need to select "android_winusb.inf" file for your fastboot and adb. Reboot your pc when you are done with the installation, good luck...:fingers-crossed:
Edit: Are you using win 8? The naked driver is working fine with win 7 but may not work with win 8....
Update: If you know linux, you can follow this post because linux does not require a driver to run fastboot...
http://forum.xda-developers.com/showthread.php?t=2679916&page=2
LetMeKnow said:
Since you have SDK tool available, you can try to install the USB driver from this guide and instead using USB driver, you can use the naked driver from this download:
http://developer.android.com/sdk/win-usb.html
http://forum.xda-developers.com/showthread.php?t=2513339
You may want to manually install your driver from your device manager on your pc.
When you are browse to the naked driver, you need to select "android_winusb.inf" file for your fastboot and adb. Reboot your pc when you are done with the installation, good luck...:fingers-crossed:
Edit: Are you using win 8? The naked driver is working fine with win 7 but may not work with win 8....
Update: If you know linux, you can follow this post because linux does not require a driver to run fastboot...
http://forum.xda-developers.com/showthread.php?t=2679916&page=2
Click to expand...
Click to collapse
Thanks so much for all your help. There is a lot here for me to try now. I think I am done for the night but will check back when I have had a chance to go through all this stuff. I'll be sure to update you
Many thanks
skaplan86 said:
Thanks so much for all your help. There is a lot here for me to try now. I think I am done for the night but will check back when I have had a chance to go through all this stuff. I'll be sure to update you
Many thanks
Click to expand...
Click to collapse
Don't know, but this thread (post 23) may be helpful to you to get the drivers installed.
http://forum.xda-developers.com/showthread.php?t=2670645&page=3
CROMi 2.3 - wasn't that still ICS based? You may have messed up your file system on /data if you had stock JB and need to reformat it before installing a new rom.
In your current TWRP select Wipe > Advanced > Format Data (you will loose all data on the internal SD)
Go to the CROM--X thread: http://forum.xda-developers.com/showthread.php?t=2425383
Download the bootloader/TWRP 2.6.1 package for your SKU and the CROMi-X zip
Flash the bootloader/TWRP zip in your current recovery
Reboot! Even if your boot hangs or loops, the BL/TWRP will get flashed before Android boots (you should see a blue progress bar)
Reboot into TWRP which now should be 2.6.1
Install CROMi-X
Good luck
Please notice: this has been done on i9500 device. you can try it on your i9505 it 100% not dangerous, but I dont know if its working
Well im using i9500 custom rum running android 4.2.2 and I had a problem: whenever i connect my phone to PC it says: "unknown device MTP device driver error 10 device can not start."
METHOD 1:
**make sure your device is disconnected from the PC.
** make sure that usb debugging is enabled (go to 'developer mode')
1) Open Xposed Installer and go to Framework and UNINSTALL it.
2) reboot your phone. (NOT soft reboot- full one).
3) On your PC, go to "driver manager" and under "universal drivers" section, delete "unknown device". (right click-> delete)
4) restart your PC.
5) connect your PC to the computer, it should work now.
6) you can now reinstall Xposed module. reboot your phone (again- not soft reboot) and reconnect it to your PC just to make sure its still working)
METHOD 2:
STEP 1
**MOST CRITICAL: Update ALL your PC drivers using driver software I personally use 'advanced optimizer pro'. UPDATE YOUR BIOS AS WELL! [/COLOR]
- Update drivers using a software.
-Update your bios.
-Download windows updates (start->type 'windows update' in search bar, click on 'windows update'-> 'check for updates'. dont forget to check optional update as well').
dont forget to restart!
now after you are sure both bios and drivers are up to date, try the following
STEP 2/2
- I downloaded and installed samsung drivers
-Try to connect your phone with ANOTHER cable.
-Try to connect your phone to ANOTHER port (this can indicates where the problem is: maybe the cable/port is corrupt)
-I tried deleting ALL samsung drivers and reinstall
-tried connecting my old s1 i9000. try to connect another phone to see where is the problem- phone or maybe computer.
-try to connect phone while its in 'download mode' and recovery mode.
-try running windows error kit.
-download Android ToolKit.
- if non of the above are working, you can always try FULL WIPE+ REFLASH ROM . (or try flashing another rom).
*if its still not working ever after performing all the steps above under method 2, try restart your PC and try Method 1 AGAIN WITH A DIFFERENT PORT AND CABLE. there might be a chance that you have a 'combined' problem (several issues that preventing from your MTP driver to work properly.
After downloading drivers you can be sure 100% ALL YOUR PC DRIVERS ARE PERFECT, try Method 1 again.
METHOD 3
***Coming soon on next update
worked for me with:
custom android 4.2.2 OzcanRom all version including v5.0 according to sep 20 2014.
stock kernel. no system files have been ever modified
working with android 4.1 and above.
Windows 7 SP1 64bit Updated Sep10 2014.
Hi!
on method 1. under device manager, I can't seem to find the UNIVERSAL DRIVER. are you refering to Universal serial bus controller?
thanks!
Edit: sorry I thought you are referring to device manager. anyway where can i find the driver manager? i'm using windows 7
thanks!
wolper13 said:
Hi!
on method 1. under device manager, I can't seem to find the UNIVERSAL DRIVER. are you refering to Universal serial bus controller?
thanks!
Edit: sorry I thought you are referring to device manager. anyway where can i find the driver manager? i'm using windows 7
thanks!
Click to expand...
Click to collapse
yup im talking about the device manger. i will update the thread soon.
you may find one of the following with an error:
1) universal bus controller.
2) MTP driver failed
try to update both of them or uninstall them
tomorrow i will upload METHOD 3
plus method 4 is on its way..
Method 1 No5 -typo
You will connect your phone to the PC, not the computer to the PC...
Also, updating a BIOS is not straight toward and can cause a bricked pc. Be careful advising people to do that