Sorry, yes. OTG adapter, using MTP protocol. Suffice to say that file transfers to/from the USB stick worked fine.Don't you mean OTG? Thanks for testing and @westernmg.
Sorry, yes. OTG adapter, using MTP protocol. Suffice to say that file transfers to/from the USB stick worked fine.Don't you mean OTG? Thanks for testing and @westernmg.
Do you see the factory firmware flashing options? System, boot, recovery, cache, hidden, radio?Sorry, yes. OTG adapter, using MTP protocol. Suffice to say that file transfers to/from the USB stick worked fine.
Yes, they're all there in the backup section.Do you see the factory firmware flashing options? System, boot, recovery, cache, hidden, radio?
Sorry I mean under the image flashing section, Install>>install image.Yes, they're all there in the backup section.
Boot, Recovery, System, Cache, Hidden, Radio.Sorry I mean under the image flashing section, Install>>install image.
cool will test after I'am back from work.
working like a charm, flashed kernel with in all is good, did a backup, mount works too. I can see all image backup and restore options.
Could you post me a screen shot of the factory image flashing page?working like a charm, flashed kernel with in all is good, did a backup, mount works too. I can see all image backup and restore options.
Can't make a screen shot in TWRP and I can't find factory image flashing page unless you are tallking about the button in Install --> Install ImageCould you post me a screen shot of the factory image flashing page?
I had to make some modifications to the layout to ensure everything would fit.
However I'm not sure know how these would look on a portrait device.
Factory image flashing is Install>>Install image then select a file with an .img extension. You will then see the flashing options.Can't make a screen shot in TWRP and I can't find factory image flashing page unless you are tallking about the button in Install --> Install Image
Getting this error when trying to make a screenshot:
![]()
BTW I installed drivers from here:
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
I can give it a go. I need to play with something else for a bit. I'm not really good with ADB. But I've messed with it a few times.Is there anyone out there that has enough knowledge to use ADB?
Still trying to sort this ADB issue.
I could just do with someone to test a build with some mods to the configuration to get ADB working.
I did a build for another member @mk89pwnz who has been very helpful with logs and such.
It seems ADB is running, but his device isn't detected by his PC.
I could do with someone who knows how to install ADB drivers on their PC while in recovery.
Thanks.
Thanks here's the modified version.I can give it a go. I need to play with something else for a bit. I'm not really good with ADB. But I've messed with it a few times.
Heres me messing with TWRP recovery log
Long story short:Thanks here's the modified version.
MTP needs to be disabled under the MOUNT button for ADB to work. Ensure the device is detected in Device manager (might need to reconnect USB cable), look for something like 'Android ADB interface'. If not and there is a device with an exclamation mark then the ADB driver for that device needs manually installing whilst in recovery. (Right click, install driver)
Once your device is detected(if at all) then do adb devices at the command prompt where ADB is installed. It should bring back a device and serial number or may say OFFLINE
twrp_adb_fix
.
So adb is in fact working in the original version? I. E. Adb devices comes back with a device serial no.?Long story short:
ADB works in Windows as MTP for both images. Both have ADB Interface.
In recovery:
ADB with the original recovery will work as MTP in recovery. AND it shows as "SAMSUNG_Android" in "other devices" but cannot find drivers for it.
I've uninstalled and reinstalled drivers while in recovery and not in recovery.
ADB is totally dead in this second version. Doesn't do anything
Hope this helps you
Yup.So adb is in fact working in the original version? I. E. Adb devices comes back with a device serial no.?
To install the drivers for ADB in recovery you need to disable MTP then in device manager select 'Samsung Android', right click, install driver, let me pick from a list, select Samsung then choose the ADB driver.
Ignore any warnings about compatibility.
That's what I expected. Damn. Is there any chance you could start adb sideload and then send me the log? Also could you use the following in TWRP terminal and upload the output?Yup.
So using your original TWRP 3.0.0, I got the driver installed but it comes up as "offline".
Rebooted Tab and computer and tried all 3 driver options I had. All of which came back as offline with the serial number.