winxp sp3 sony tablet s when put in recovery mode for flashing the mtp driver
shows yellow (!).when i try to install driver manually it trys to start but comes
back with code 10.with tablet in normal mode winxp sees mtp & adb drivers.
the problem is only with recovery mode.tryed all i can think of and read all
solutions but driver still fails to start.so i can,t flash fw!. i really need help with
this one. please someone help i`ll give you a big thanks. i know i am not the
only one with this problem.i hope this is clear enough.
Same problem here:
Everything's fine in normal boot, but in recovery mode, I can't install the MPT driver. Win7pro. It tries to install, but ends up with a Code28 (something in the INF file is invalid, can't tell the english error message, because I have German Win7).
This seems to cause my problem flashing to R5a by AiO or the auto flasher by condi.
I get the exact error message on the tablet, as shown in post #72 in this thread:
[FW R5A WIFI/3G] NEW! custom preROOTed newest stock nbx03 R5A with R1A's recovery
Trying since four nights...
At least I managed to flash and root to 4.0.3 R2a from the "unrootable" 3.2 R10 by flashing via recovery mode to Sony original ICS R2a (downloadable from sony) and then using the AIO 5.3 to root. Don't know why this way is not published here... Tried updating to 3.2.1 etc, nothing worked... the found the links to sony's fw and thought "WTF! Let's try ICS R2a, worst case is an also unrootable Tablet but with ICS". Worked, and was rootable then.
Just ignore the problem. I believe seeing the alerted MTP USB Device in Windows Device Manager when your tablet is in Recovery Mode is being cause by your tablet's borked Android System Recovery Revision 36 (i.e., Rev.36). This problem did not occur with earlier revisions of Android System Recovery. Normally, no MTP USB Device (or Sony Tablet S) should be displayed or even installed for Recovery Mode because a tablet in Recovery Mode cannot provide MTP functionality. Recovery Mode only requires Android Composite ADB Device be installed. Normal Mode, however, requires both Android Composite ADB Device (but only when the tablet's USB Debugging is turned on) and MTP USB Device, which Windows Device Manager renames and displays as Sony Tablet S.
You are basically right... it was ADB drivers, not MTP.
I tried all possible drivers from the list, also some "phone" devices. And YES!! Windows accepted one of them...
After that, I had no problem flashing my tablet to ICS R5a!!
please, could somebody who has writing permission in the dev forums, tell Condi, that the AiO 5.3 tools tells you to check this driver ONLY AFTER you are NOT stuck in "status7" error!!!!!
You do NOT get the message in the terminal box, IF you are stuck.
That would have saved me one or two nights trial and error...
But, after all, I have a nice working ICS R5a on my tablet S
I will post a how-to for other 3.2 kernel10
that explains a lot. so i need to find another adb driver that works in recovery mode and
not worry about mtp driver?.
phc1234 said:
that explains a lot. so i need to find another adb driver that works in recovery mode and
not worry about mtp driver?.
Click to expand...
Click to collapse
Right.
In device manager, it's "android phone" (?), when you select driver manually, then I think it was the same as on the first install, so the third ADB device in the drivers list.
Windows fools you, it installs an MTP driver, and thus keeps you from using your brain
Install ADB drivers, check whether your tablet will be correctly recognized in both modes... then at least the all in one tool with custom zip will work (hopefully).
Why the flasher did not work? Don't know. looking again at my error messages, I would guess, that the busybox was not working correctly. I don't know if you have to install busybox before, manually. I thought everything was integrated into the flasher...
android phone dosent show in device manager
ThreeEyes said:
Right.
In device manager, it's "android phone" (?), when you select driver manually, then I think it was the same as on the first install, so the third ADB device in the drivers list.
Windows fools you, it installs an MTP driver, and thus keeps you from using your brain
Install ADB drivers, check whether your tablet will be correctly recognized in both modes... then at least the all in one tool with custom zip will work (hopefully).
Why the flasher did not work? Don't know. looking again at my error messages, I would guess, that the busybox was not working correctly. I don't know if you have to install busybox before, manually. I thought everything was integrated into the flasher...
Click to expand...
Click to collapse
[edit]
thats the problem android phone dosent show up in device manager. tryed on 3 wixp computers and nothing no way
ti install adb drivers.
phc1234 said:
[edit]
thats the problem android phone dosent show up in device manager. tryed on 3 wixp computers and nothing no way
ti install adb drivers.
Click to expand...
Click to collapse
But by manually updating the driver and choosing manually, you can assign ANY driver to any device - it may not work or even do some damage to the system, but basically, it's your choice!
Take the device with the "!" and give it the right driver...
"CAT" above is right with rel5 and 5a that they changed the recovery rev to 36 and this rendered the
tablet s from loading any mtp driver or seeing the android phone entry in device manager so no way
to install adb driver.this has killed conis AIO tool flashing firmware and roms until someone breaks
the lockdown sony put in.
My question is. How to flash back original recovery.img
I tried to root this device and install custom recovery. seems to worked but now recovery to factory settings wont work - just reboots.
fastboot seems to work and adb connection is ok.
Phone also has SD card slot.
I have original stock .img files but factory procedure wont work - cannot install MT65xx drivers. device in device manager under windows seems to connect/disconnect every second. (procedure is to connect phone to usb with no battery inserted - appears as MT65xx device then)
Any ideas?
Maybe anyone has a good rooting procedure for this phone.
I have rooted it- have access to system files but cant change permissions or modify files. - so rooting is not done properly.
Might be that the phone is too fresh...
Now before you tell me to reinstall my drivers, I have countless times. I'm 90% sure its an issue with the phone itself. When I connect the phone without debug mode it connects. If I have the phone in debug mode and I connect, the phone does get recognized, but not as a storage device but as a driver installer with a driver installer exe, when ran, it almost instantly disconnects the phone. The phone says connected as an installer, and no matter if I try to install this driver or the actual official driver it will not connect.
I had however connected in S/W upgrade mode and flashed, but it didn't fix the problem. I also tried flashing ICS u-boot and xloader then flashing but I can't for the life of me fix this. The phone is a locked bootloader w/ jb 20h. This problem arose when I flashed JB xloader and u-boot then I flashed the ICS one. I feel as if I permanently ruined a part on the phone, because there are countless other problems that go along with this like crashing etc.
Fixed thanks to Kuma
http://forum.xda-developers.com/showthread.php?t=2612356
Hey, I am new here so sorry if I'm posting in wrong board.
I rooted my P70 a while ago and everything was fine. Now I decided that I want to flash 5.1.1 on it. I proceeded to flash TWRP.
I tried it with SP flash on pc, I checked that my scatter file and recovery.img was correct. I opened the scatter file in SP, connected my phone and clicked download, but nothing happened. Only the phone started charging, I have enabled USB Debugging and developer mode. The bootloader was still the stock one. Why?
Next thing I tried is to put the recovery.img on SD card and downloading Uncletools, I flashed it and it asked me if I want to reboot in bootloader, so I did, but it was still the stock bootloader.
What am I doing wrong? Thanks a lot for any response.
Anyone got any idea?
Click download and conecting usb cable to hh
Hey,
I have the same issue. The phone is rooted but the SP flash tool will not do anything. I've read that it's because the USB drivers are incorrect. However I am unable to install the drivers as the phone does not show up under other devices but rather under portable devices. I tried to install the android sdk and use those drivers or ones I found on the web but none of them will take. I found the ADB device signed driver under USB devices in the device manager.
I am honestly at a loss here. Would be grateful if anyone has ideas I could try!
Thanks
Hello, guys.
Recently, I've tried to root a Cubot Power 4G following a guide I found online. I probably should have been more catious about it, cause now the phone is stuck on a bootloop. I tried to install a custom recovery to try and fix this, but as there was no official twrp for Cubot, I once again downloaded something that was probably shady. Thus, now the phone is stuck on bootloop, won't access recovery mode, is now turned off because battery gave out, but if I try to connect it to the pc, it will start to bootloop again. I cannot access adb, or at the least I don't know a way to, since it keeps bootlooping and I have no way to access a recovery mode(since there's no one, or at the least, if there is, it's faulty). What can I do here?
@Giordyman
Re-flash phone's Stock ROM by means od MTK Flash Tool. You have to install the Mediatek VCOM drivers before on your Windows computer, if not done yet.
jwoegerbauer said:
@Giordyman
Re-flash phone's Stock ROM by means od MTK Flash Tool. You have to install the Mediatek VCOM drivers before on your Windows computer, if not done yet.
Click to expand...
Click to collapse
I did! Or so I think... The moment I connect it to the pc, it starts bootlooping and so the pc cannot actually connect there
Bootloop is a situation where you cannot get into the "normal" Android system. Take note that as soon Android logo is shown on phone's display Android kernel got successfully initialized, ADB & Fastboot are ready.