Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.mobile.android > #58077 > unrolled thread

USB problem

Back to article view | Back to comp.mobile.android

Contents

  USB problem LℲⱵC <joe@somewhere.example> - 2018-12-03 13:12 +0000
    Re: USB problem Frank Slootweg <this@ddress.is.invalid> - 2018-12-03 13:42 +0000
      Re: USB problem LℲⱵC <joe@somewhere.example> - 2018-12-04 08:30 +0000
    Re: USB problem Andy Burns <usenet@andyburns.uk> - 2018-12-03 14:10 +0000
      Re: USB problem LℲⱵC <joe@somewhere.example> - 2018-12-04 08:32 +0000
    Re: USB problem Theo <theom+news@chiark.greenend.org.uk> - 2018-12-03 16:40 +0000
      Re: USB problem LℲⱵC <joe@somewhere.example> - 2018-12-04 08:43 +0000
        Re: USB problem Tim <onelydad58@gmail.com> - 2018-12-05 00:01 +0000
          Re: USB problem LℲⱵC <joe@somewhere.example> - 2018-12-05 08:56 +0000

#58077 — USB problem

	
I'm new to rooting and unlocking bootloaders and stuff, and as an 
exercise I would like to root a cheap Chinese "Susan" smartphone with 
Android Lollipop. 

When I connect the phone to the pc with a usb cable, all I get is a cd-
rom drive (!) in Explorer containing just one file called ADB.rar and 
nothing else. 

When I select Storage > USB computer connection, both options MTP and PTP 
are ALWAYS greyed out. Turning USB debugging on or off doesn't seem to 
make any difference.

I have tried the program Kingroot and others, but to no avail.

Any help in accessing the files on the phone?

Thanks.

[toc] | [next] | [standalone]

#58079

L??C <joe@somewhere.example> wrote:
>         
> I'm new to rooting and unlocking bootloaders and stuff, and as an 
> exercise I would like to root a cheap Chinese "Susan" smartphone with 
> Android Lollipop. 
> 
> When I connect the phone to the pc with a usb cable, all I get is a cd-
> rom drive (!) in Explorer containing just one file called ADB.rar and 
> nothing else. 
> 
> When I select Storage > USB computer connection, both options MTP and PTP 
> are ALWAYS greyed out. Turning USB debugging on or off doesn't seem to 
> make any difference.
> 
> I have tried the program Kingroot and others, but to no avail.
> 
> Any help in accessing the files on the phone?

  (Not so?) Wild guess: Perhaps/probably the ADB.rar archive contains
the Windows (assuming your 'pc' is a Windows one) (ADB) software
(driver?) for your phone.

  .rar (Roshal ARchive) is an archive format, you probably need
something like 7-Zip (<https://www.7-zip.org>) on your Windows system to
unpack it.

  So try to copy the ADB.rar archive to your Windows system and unpack
it with 7-Zip and take it from there.

[toc] | [prev] | [next] | [standalone]

#58089

On Mon, 03 Dec 2018 13:42:44 +0000, Frank Slootweg wrote:

>   (Not so?) Wild guess: Perhaps/probably the ADB.rar archive contains
> the Windows (assuming your 'pc' is a Windows one) (ADB) software
> (driver?) for your phone.
> 
>   .rar (Roshal ARchive) is an archive format, you probably need
> something like 7-Zip (<https://www.7-zip.org>) on your Windows system to
> unpack it.
> 
>   So try to copy the ADB.rar archive to your Windows system and unpack
> it with 7-Zip and take it from there.

I did that. I unpacked the adb drivers and installed them, both on Linux 
and Windows. Also installed heimdall, kingroot and some other software to 
try to access the phone, but nothing seems to work, it still shows up as 
a cd-rom drive.

[toc] | [prev] | [next] | [standalone]

#58081

LℲⱵC wrote:

> Turning USB debugging on or off doesn't seem to
> make any difference.

With USB debugging enabled, and the correct drivers loaded on the PC, 
and the phone has asked if you want to authorised that PC to use 
debugging (last step might not apply to older androids) the phone should 
show up e.g. when running

"adb.exe devices"

[toc] | [prev] | [next] | [standalone]

#58090

On Mon, 03 Dec 2018 14:10:57 +0000, Andy Burns wrote:

> LℲⱵC wrote:
> 
>> Turning USB debugging on or off doesn't seem to make any difference.
> 
> With USB debugging enabled, and the correct drivers loaded on the PC,
> and the phone has asked if you want to authorised that PC to use
> debugging (last step might not apply to older androids) the phone should
> show up e.g. when running
> 
> "adb.exe devices"

(on Linux) I tried "adb devices" and this is what I got:

List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *

And that's it... Also tried "heimdall detect":

ERROR: Failed to detect compatible download-mode device.

[toc] | [prev] | [next] | [standalone]

#58084

LℲⱵC <joe@somewhere.example> wrote:
>         
> I'm new to rooting and unlocking bootloaders and stuff, and as an 
> exercise I would like to root a cheap Chinese "Susan" smartphone with 
> Android Lollipop. 

You need to know which SoC it uses, and then work from there.
USB rooting/flashing methods typically use SoC or vendor-specific tools

(Samsung = heimdall/odin, generic Android = fastboot, Tegra = nvflash, etc)

[toc] | [prev] | [next] | [standalone]

#58091

On Mon, 03 Dec 2018 16:40:36 +0000, Theo wrote:

> LℲⱵC <joe@somewhere.example> wrote:
>>         
>> I'm new to rooting and unlocking bootloaders and stuff, and as an
>> exercise I would like to root a cheap Chinese "Susan" smartphone with
>> Android Lollipop.
> 
> You need to know which SoC it uses, and then work from there.
> USB rooting/flashing methods typically use SoC or vendor-specific tools
> 
> (Samsung = heimdall/odin, generic Android = fastboot, Tegra = nvflash,
> etc)

Thanks, but I don't think there is any vendor-specific tools available 
for a cheap and completely brandless Chinese phone. 

My goal is to be able to flash a custom rom on a few old smartphones I 
have lying around, but well, I'm not there yet.

[toc] | [prev] | [next] | [standalone]

#58103

=?UTF-8?b?TOKEsuKxtUM=?= <joe@somewhere.example> wrote in news:pu5enh$fjq$3
@news.albasani.net:

> On Mon, 03 Dec 2018 16:40:36 +0000, Theo wrote:
> 
>> LℲⱵC <joe@somewhere.example> wrote:
>>>         
>>> I'm new to rooting and unlocking bootloaders and stuff, and as an
>>> exercise I would like to root a cheap Chinese "Susan" smartphone with
>>> Android Lollipop.
>> 
>> You need to know which SoC it uses, and then work from there.
>> USB rooting/flashing methods typically use SoC or vendor-specific tools
>> 
>> (Samsung = heimdall/odin, generic Android = fastboot, Tegra = nvflash,
>> etc)
> 
> Thanks, but I don't think there is any vendor-specific tools available 
> for a cheap and completely brandless Chinese phone. 
> 
> My goal is to be able to flash a custom rom on a few old smartphones I 
> have lying around, but well, I'm not there yet.
> 
> 
Where did you get the ROM you want to flash? More importantly, will it work 
on the phones you want to load it onto. A custom ROM is very device 
dependent and explicit. A ROM is tuned for a specific set of hardware 
devices [CPU, memory, display, audio, RF, etc]. As an example I would love 
to load an Android 8 rom to my Asus S 8 Zenpad. Unfortunately, I can find 
one for an Asus 8 Zenpad, but not for an S 8. And if I don't have the right 
ROM I will brick my device if I try to install it.

[toc] | [prev] | [next] | [standalone]

#58105

On Wed, 05 Dec 2018 00:01:40 +0000, Tim wrote:


>> Thanks, but I don't think there is any vendor-specific tools available
>> for a cheap and completely brandless Chinese phone.
>> 
>> My goal is to be able to flash a custom rom on a few old smartphones I
>> have lying around, but well, I'm not there yet.
>> 
>> 
> Where did you get the ROM you want to flash? 

I don't have it yet. My goal is to install LineageOS on a new smartphone 
in the near future (probably a Xiaomi), but first I want to learn more 
about all this flashing and rooting stuff and so for the moment I play 
around with an old Sony Xperia E1 and this brandless Chinese phone. I 
already managed to unlock the bootloader on the Sony, but there doesn't 
seem to be any custom ROM available for it.


> More importantly, will it
> work on the phones you want to load it onto. A custom ROM is very device
> dependent and explicit. A ROM is tuned for a specific set of hardware
> devices [CPU, memory, display, audio, RF, etc]. 

I know, that's why I'll make sure that the phone that I buy has a 
LineageOS ROM available by checking the list of supported devices on 
their website.


> love to load an Android 8 rom to my Asus S 8 Zenpad. Unfortunately, I
> can find one for an Asus 8 Zenpad, but not for an S 8. And if I don't
> have the right ROM I will brick my device if I try to install it.

Well, I wouldn't mind bricking this Chinese "Susan" phone as an exercise, 
but it won't even let me do that. PC's are lot easier to mess up. :-)

[toc] | [prev] | [standalone]

Back to top | Article view | comp.mobile.android

csiph-web