yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] Muhilica:
I'm trying the methods described by you and Chico_PinoyCracker as we speak. If I find anything usefull I'll share the info. Thank you.

PS: But, as far as I remember, i never got the "Android Composite ADB Interface" in the device manager recognized. SCI General U2S(AT) (COM4) and SCI Vendor U2S(DIAG) (COM3) were recognized and I managed to get drivers but ADB Interface is not there. Can it be because the phone is stuck in bootlop?
[General Questions and Answers] Chico_PinoyCracker:
Hmmm...

I never got the SCI General U2S(AT) (COM4) and SCI Vendor U2S(DIAG) (COM3) to appear in mine. Just the one 'Android Device' under task manager labelled as 'Android Composite ADB Interface'.

Where did you get the drivers from btw? I just used the default certificates from the Android SDK bundle provided by Google.
[General Questions and Answers] okayasu:
Root

Hello! I'm a newbie.

I saw the portuguese method and i noticed that it fails because of that the operating system is marked as "development" so adb cant get root.

I think that the only way to change that is obtaining the img file and change that parameter.

Any ideas?

Im from Argentina (i have to improve my english hehe)
[General Questions and Answers] Chico_PinoyCracker:
Wasup pinoys

Did you download the root.exe tool posted by sergimas? Visit that site first. Don't use DoomTool. It's in Portuguese so translate the page... This is what sergimas posted:

"I followed this tutorial (Google: "Root Android 4.0 (Novo método) Atualizado x3") to root it, which points to the drivers ( ge.tt/8hWh71S/v/0 ). Though this zip file has 64bit drivers, in my case they didn't work properly, I saw the same screen you post."

I got your email sorry I wasn't able to reply over the weekend.

If my memory serves me correctly, here are the steps I did.

1. Since your done with the ADB drivers, let's proceed with rooting.

2. Get the adb files from H_Bler (See first page of this thread, at the bottom you will find the links. I can't post links yet)

3. Assuming your device is already connected, install the Root Android 4.0 Novo metodo in your C:/

4. Copy and paste the adb files (including the adb.exe) to a similar folder created inside the Root.Exe Novo Metodo folders

5. Run ADB.exe -- this will resolve the 'adb server out of date issue'

6. Reconnect your android phone

7. Run Root.exe

8. Your phone should reboot by itself now and have superuser access.

I only did this in two tries. I know rooting chinese phones here in the PI are rare and I would have to thank H_Bler and sergimas for all their efforts in making this rooting possible and seamless.

Send me a private email regarding your results.

Cheers
[General Questions and Answers] okayasu:
I forgot to say that method didnt work for me.
[General Questions and Answers] Chico_PinoyCracker:
What are your phone specs?

Hi Okayasu,

Can you tell us your complete phone specs?
[General Questions and Answers] okayasu:
specs

Yes,

Model: S560

Android Version: 4.0.3 (fake, i think its 2.3.5)

Base band version: DM_BASE_12A_W12.32|sc8810_modem|08-09-2012 16:47:10

Kernel version: 2.6.35.7

rgk-bu2-05@rgk-bu2-05-desktop #3

Software version: T162_JYY_G2_P2_1_W1220P12_V0.8.2_20121019

Hardware version: 1.1.0

Another specs:

processor: sc6820

Memory: close to 200 mb

Rom: close to 200 mb

screen: 3.5"
[General Questions and Answers] Chico_PinoyCracker:
Hmmm...

I don't think it's a a gingerbread, I think it's a legit ICS (4.0.3), unless you cant run some apps...

Hmm... Our method worked for the Model S930 (s3 replica). I'm not sure about the S560...

What happens when you run the root.exe? What errors does it tell you? What exactly do you mean when you said, "it didn't work...?"
[General Questions and Answers] okayasu:
when you say root.exe, do you mean root.bat from C:\root\platform-tools ?

My drivers are ok, and this happens after i copy and subscribe the adb files:

this is my result:

script root

se a lista de devices estiver vazia, o script nao vai funcionar...

List of devices attached

19761202 device

Comecar processo de Root

Cancelar [n]

Selecione a opcao e o processo comecara (selecione "s" ou "n" e de enter):s

adbd cannot run as root in production builds

remount failed: Operation not permitted

failed to copy 'su' to '/system/bin/su' : Read-only file system

failed to copy 'Superuser.apk' to '/systen/app/Superuser.apk': Read-only file system

Unable to chmod /system/bin/su: No such file or firectory

Unable to chmod /system/app/Superuser.apk: no such file or directory
[General Questions and Answers] Chico_PinoyCracker:
Hmmm...

Did you edit your adb_usb.ini located in ".android" folder?

Edit it using a text editor, here's the syntax:

# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.

# USE 'android update adb' TO GENERATE.

# 1 USB VENDOR ID PER LINE.

USB\VID_1782&PID_5D01&REV_0229&MI_01

USB\VID_1782&PID_5D01&MI_01

0x1782

0x5D01

yours should depend on your own hardware ID -- can be seen if you right click your device and go to properties. It should look something like this:

# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.

# USE 'android update adb' TO GENERATE.

# 1 USB VENDOR ID PER LINE.

USB\VID_xxxx&PID_xxxx&REV_0229&MI_01

USB\VID_xxxx&PID_xxxx&MI_01

0xyyyy

0xyyyy

-Those characters depend on your device ID.

If you've already done those, I want to ask, have you copied the adb.exe files from H_Bler?

If nothing seems to work you can email the Portuguese guy in bdfabricio.blogspot.com.br/2013/01/root-em-android-40-atualizado-novo.html

He is open for questions, as he himself made this rooting tool.
[General Questions and Answers] mia89:
I get the same error, any solution for this?

---------- Post added at 04:35 PM ---------- Previous post was at 04:30 PM ----------

same isue... I think this happens because my device cannot be mounted as a usb w/o sd card.... also, i am not able to view system files at all...

Is there a fix for this?
[General Questions and Answers] okayasu:
I already tried that, nothing seems to work! thanks for your help, i will ask the Portuguese guy.
[General Questions and Answers] hana84:
If you could share your solution finally, would be perfect :fingers-crossed:
[General Questions and Answers] okayasu:
Of course!
[General Questions and Answers] Chico_PinoyCracker:
Same here...

Up to this day, even when this phone is rooted, I never got around to having my device detected by my computer.

H_Bler said to try and use a different USB cable because the stock ones are crap. I tried using an original samsung USB and still my computer couldn't detect the phone's files.

So what I do now is just use a microSD card reader to transfer files...

I don't touch system apps/files anyway so I don't see the point in reading the contents of the phone itself...
[General Questions and Answers] mia89:
@Chico_PinoyCracker : Were you able to root your phone even though it said "read only memory"? Can u pls send me a pm with step by step instructions, please? Also, tell me what is shown in ur device manager when u connect ur pone to pc? I know we should enable USB Debugging but should I also enable USB Storage?
[General Questions and Answers] lskwl:
S560

I got also the S560, from Thailand.

Its NOT an S3 replica and more low end. Its a simple DUAL SIM phone, with fake SAMSUNG label on the backplate.

I have the same specs as user okayasu, exept newer SW Version, just date differs... (mine from Nov 2012).

I am very sure that the shown Android 4.0.3 is its faked and not ICS!!!!

It is really 2.3.5, so this might not be the right thread to talk about this phone.

The problem I have is, I dont get my drivers/adb to work...

Everything looks ok in the device manager.

When I run "ADB devices" it shows up normally.

But when I start anything else like ADB SHELL it just hangs...

ADB LOGCAT just gives me "- waiting for device -"

If somebody has some hint, it would be nice to share...
[General Questions and Answers] okayasu:
try this drivers ge.tt/8hWh71S/v/0 and let me know what happened :good:
[General Questions and Answers] jvrey5:
It seems that this is the only active thread regarding the sprd S930.

PWR + upVolume = Spreadtrum diagnostics

PWR + dwnVolume = Android Recovery (doesn't do much because there's no option to backup. if you're rooted and you mess up your system files - you're pretty much screwed)

= press upVol once you see the yellow exclamation mark to get the menu

To those who were able to root their phones, has anyone been able to create backup ROMs or update ZIPs?

I was able to root mine using H-Bler's method.

DRIVERS: I was successful in installing them for both Windows 8 and XP. I used the Google drivers for ADB composite and USB-Spreadtrum Android.rar for the other 2. In Windows 8, install the inf file before manually choosing the Android composite when running update drivers. In XP, USB-Spreadtrum Android.rar worked fine but I had to edit the inf for the ADB composite. Try to add this:

; Spreadtrum

%SingleAdbInterface% = USB_Install, USB\Vid_1782&Pid_5d01&Rev_0229&MI_01

%CompositeAdbInterface% = USB_Install, USB\Vid_1782&Pid_5d01&MI_01

%SingleBootLoaderInterface% = USB_Install, USB\Vid_1782&Pid_5d01&MI_01

%CompositeAdbInterface% = USB\Vid_1782&Pid_5d01&MI_01

(...make sure that 'Vid_1782&Pid_5d01&Rev_0229&MI_01' and 'Vid_1782&Pid_5d01&MI_01' is the same in the device manager)

ROOT: I also used DooM but with a twist since I kept on getting 'permission denied' errors. I ran ADB (on it's own) first, devices (to make sure that my device is detected),root, then remount; before running DooM.

SUGGESTED APPS/HACKS:

Link2SD - I have a 16GB micro SD but can't maximize it since the apps take up space on the internal memory. This app helped a lot. If you can't mount the 2nd partition, FORMAT both partitons at the SAME time and use FAT32 for both.

MY ISSUE: Phone is stuck on the Android Boot Logo (doesn't even get to the boot animation). When phone is turned off and USB is attached, it does the same thing but keeps on vibrating.

I was able to extract my boot.img but I can't seem to put it back. Phone will only be recognized by my PC if it is in recovery (unforunately, can't flash it that way). I've tried to create my own update.zip but it keeps on saying 'E:signature verification failed'. I've tried signing it using Android Commander and several other ways but nada - still get the same thing.

Any suggestions would be very much appreciated!!!

Cheers!

*BTW, I would have added links and DL links but I'm currently having browser issues. Will upload them in the future.

**I was able to find an 'orig' S3 boot and shutdown anim - I'll add them next as well.

*** I'm also a Filipino =P
[General Questions and Answers] superjavibros:
S560

I'm still trying to root the S560 spreadtrum.

When I execute the root.exe or root2.exe from the portuguese guy I obtain the same as okayasu

script root

Se a lista de devices estiver vazia, o script nao vai funcionar...

List of devices attached

19761202 device

Comecar processo de Root

Cancelar [n]

Selecione a opcao e o processo comecara (selecione "s" ou "n" e de enter):s

adbd cannot run as root in production builds

remount failed: Operation not permitted

failed to copy 'su' to '/system/bin/su': Read-only file system

failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file sy

stem

Unable to chmod /system/bin/su: No such file or directory

Unable to chmod /system/app/Superuser.apk: No such file or directory

I'm shure that the problem is with the read-only file system.

For those guys with the driver problem I have to say that I had to change the adb.exe file that comes with the root.exe to make it work.

I'm shure the drivers work because when I run "adb shell" I can run commands in the shell $ that appears.

But the problem is the same as in DoomLord and superoneclickroot the read-only file system.

Iskwl says in this thread that it really isnt a ICS 4.03 android that its only one 2.35. I'm not shure of that but I buy this as many other persons in focalprice. There this Xmas it costed only 39 euros.

I think it really is a 4.03 because apk that easily root those 2.3- android op sys. don't work with this phone.

But as I say try to change the adb.exe file that will make the driver work with the portuguese method, but the method will not work.

I will try to ask the port guy in his blog.

Thanks to every body

Stay on line:laugh:
[General Questions and Answers] Ladsrag:
Same read-only problem!

Hi,

I am glad to see i am not the only one struggling to get my Chinese phone rooted. Of course i am not so happy to see that i seems you need to be "lucky" to overcome this read-only problem. I have now tried more than 10 different methods and all (yes all) of them give up on the read-only system. Some of the more "professional" system give me some feedback on my phone but they all give up.

I agree with you that we need to concentrate on how to resolve the read-only problem. When this is solved I think that many of the methods mentioned in this thread will function.

When I used the Portuguese method "root.exe" I got exactly the same info as you, ending up with booting the phone. But when I used the "root2.exe" (beta) i got almost the same info but, with some minor difference. (but still no root luck :(:( )

I get this info:

script root

Se a lista de devices estiver vazia, o script nao vai funcionar...

List of devices attached

19761202 device

Comecar processo de Root

Cancelar [n]

Selecione a opcao e o processo comecara (selecione "s" ou "n" e de enter):s

611 KB/s (37272 bytes in 0.059s)

978 KB/s (380532 bytes in 0.379s)

526 KB/s (1468798 bytes in 2.722s)

mount: Operation not permitted

The system cannot find the path specified.

Unable to chmod /system/bin/su: No such file or directory

The system cannot find the path specified.

Unable to chmod /system/app/Superuser.apk: No such file or directory

mount: Operation not permitted

I have two of these quite nice "useless" phones, as I can't create a Google account. Thereby i am stuck with the pre-installed cracked Chinese marked which of course is in Chinese. (not easy to read for a Danish guy) :p:p

I have tried many workarounds, but all of them lead to the "rooted" phone - and circle closed.

When (not if) anybody find a solution to this read-only problem i would be very happy to hear how you did it, and if I come across a solution I will of course post it immediately.

Great thread, by the way :):)

Best regards Peter
[General Questions and Answers] lskwl:
S560

Just look at the UI and settings. You can search at youtube. Its definitely a 2.xx System.

The Interface of ICS - 4.xx looks different and requires faster hardware, more memory and so on.

I am sure this low end phone is a 2.3.5

---------- Post added at 05:48 AM ---------- Previous post was at 05:40 AM ----------

Actually this are the drivers which I did try with already.

I see 2 possible threads of my problem:

1: The used ADB.exe (i tried with the one from doomlord root kit / and the latest version from Google SDK)

2: I am running a Windows 7 x86 using a virtualbox machine and forward the phones USB port

For the 2nd I don't have a possibility to test this under a real hardware right now. but another android phone did work nice under virtualbox before.
[General Questions and Answers] Panoxet:
S3 Clon

Hi all, I'm from Spain and I need your help, I have bought a S3 Clon but I don't know how I have to root it, please check the attachments for more details about my phone.

If do you need more details please check

Thanks/Gracias
[General Questions and Answers] earl22online:
I have also the same S3 replica (clone), which has the specs as yours,

Model number: S930

Android version: 4.0.3

Baseband version: DM_BASE_12A_W12.28_P1|sc8810_modem|07-13-2012 16:42:35

Kernel version: 2.6.35.7 rgk-bu2-04@rgk-bu2-04-desktop #3

Software version: T300_JYYS930_C3BOM_MLB_V6.6.5_20121105

Hardware version: 1.1.0

CPU: Spreadtrum

I managed to installed the first spreadtrum driver which is the "Android Composite ADB Interface (driver instaled with Android SDK)" in my XP laptop successfully, but the two remaining spreadtrum drivers, i can't seem to manage to install all the drivers i've searched from google...

- Spreadtrum Phone >> SCI General U2S(AT)

- Spreadtrum Phone >> SCI Vendor U2S(DIAG)
[General Questions and Answers] earl22online:
>>>

where can i find the ".android folder sir"? i can't manage to install the two remaining spreadtrum drivers of my S3 clone on my XP laptop, but the ADB driver is already installed...please help me....

---------- Post added at 04:31 PM ---------- Previous post was at 04:02 PM ----------

>>>

TS, can you tell me the step by step procedure you do with DooMLoRD ROOT v4 to root the phone? and where can i find the ".android folder" you are telling, if i'm using windows xp?

There is a folder named ".android" at my C:\ drive, but i did'nt find any adb_usb.inf file inside...can i create one and place the hardware ids then i try to install again the drivers?
[General Questions and Answers] Chico_PinoyCracker:
.android is in your phone

Hi Earl,

.android is located IN your phone. If you're using ES File Manager, 'unhide' hidden files.

As for Mia,

The steps are in the previous pages of the thread. ;)

Everything was pretty much dumb luck. Had so many retries.

-----------

BY THE WAY GUYS--> PLEASE BE CAREFUL IF YOU'RE USING LINK2SD FOR THIS PHONE.

THERE ARE MANY KNOWN ISSUES WHEN IT COMES TO RECOGNIZING THE 2ND PARTITION DURING BOOT.

I'm using a 16gb microsd and my 2nd partition is about 2gb.

Android System (default app) still recognizes the phone to have low memory upon boot.

This can cause BOOT-LOOP errors if you chunk too many applications in your 2nd partition.

Also, if you move apps from phone to the SD card, make sure they are MOVEABLE. Otherwise, your apk's, dex's, and lib's will all be fragmented and it will be hard to move them because of the low memory issue inside the phone (to begin with).

If you have APP2SD and LINK2SD at the same time, this will only create a huge amount of confusion to you AND YOUR phone, wether or not you can move your apps.

LAST PIECE OF ADVICE, DO NOT DELETE BLOATWARES AS MUCH AS YOU WOULD LIKE TO (SYSTEM APPS).

I know they're annoying but H_Bler BRICKED his phone in doing so.

Recommended apps:

SD Maid Pro

Titanium Back Up Pro

----

Good luck with by-passing the 'read-only memory' issue. I know you can do it, I've mentioned all the steps I did that worked for my s930. There's certainly a way to get around it.

Please send me an email at veritas38@gmail.com, I'm at work most of the time so I don't get to read and follow the thread.

---------- Post added at 06:07 PM ---------- Previous post was at 05:59 PM ----------

What happened kapatid? Why did your phone brick?

I agree with you that you can't maximize the partition. I just keep a handful of apps in the 2nd partition, and my current phone internal memory is about 70mb (geeesh f**king Chinese phones). The rest are games in the main partition.
[General Questions and Answers] jvrey5:
To be honest, I really don't know. When I bought the phone, they put a code in which changed the bootanim from the blue android bot in 'snow' to the 'S' then Samsung logo. It still looked crappy but I was able to find a more decent S3 startup and shutdown anims. Since I can't get an original S3 boot anim because they're QMG files, I thought of creating one myself. I spent about an hour browsing the web for animated GIFs so that at least I won't have to start from scratch. Then it hit me. Why don't I create one based on the static boot logo. It would be easier because the pic is already in the phone and it will definitely be easier to manipulate since it's only a simple image composed of 3 colors - green; for the bot, black; for android on a white background. The problem is I can't find it anywhere on the phone! That's the reason why I have a boot.img. I thought that it would be in there. I tried looking online, but the proportions are way too different. I did find a good GIF that had 7 frames and was small enough to replace the battery charging icons when it's shut down (FYI, they're in the 'res' folder. not certain if it's in the root or in the system folder). I was having second thoughts of changing it because I knew it involved flashing. I did end up flashing it or at least tried to flash it but I got an error message saying that the command was not recognized. When I rebooted the phone, it was still OK. Unfortunately, I did not stop there. I manually tried to replace the files using both the ES File Manager and ADB. Everytime I rebooted, nothing really changed or it just went back to the original icons. That's when I gave up and that's when it became semi-BRICKED (technically, it's only SEMI because I could still go into recovery mode).

Weird thing is, when I checked for the partitions while I was creating the boot.img, I remember seeing a FLASHBOOT partition. I can't seem to access it though. I've tried all the regular button combinations (which of course, our phone only has 4). I'm thinking that there might be a release sequence that you need to follow - just like on an iPhone. Anyway, that's the only other method that I haven't tried so far because the update.zip is not getting me anywhere. Maybe it needs to be signed by spreadtum or some ****n' Chinese guy. Who knows?!
[General Questions and Answers] bamanow:
How i rooted Spreadtrum S930 (Samsung Galaxy S3 replica)

First of all, sorry for my English.

After 3 sleepless nights I was able to root this phone :o

Solution was... well synthetic.

In essence it was H_Bler's solution from the 1st page.

BUT

1) adb didn't recognize device in both win7 x86 & win7 x64. So I had to install VirtualBox + Windows XP on my win7 x64.

2) on this virtual machine & on my x64 laptop I installed drivers from SCI-android-usb-driver-jungo-v4-p2.rar (don't remember now where i got them). But i think generic ones which H_Bler suggests will work just as fine.

3) Enable USB Debugging of the phone. Run virtual machine. Connect the phone.

4) Go to Devices->USB devices->Spreadtrum phone (put check). This step connects phone to virtual machine.

5) Now command adb devices DOES list my device in virtual machine.

6) Next problem file system is Read Only! Fortunately Mario's TinyLab (http: //blog.fh-kaernten.at/wehr/?p=1182) had an answer to this problem. It is reply from January 6th, 2013 on 03:05 (Was last comment when i read that article).

7) Now DooMLoRD_v4_ROOT-zergRush-busybox-su.zip did it's work. (After every restart of phone repeat step 4)

Hope this helps.
[General Questions and Answers] Chico_PinoyCracker:
I wanted to do that too

I know what you mean man, I wanted to change those fake icons too so I can resell this crap for a fair price. So far I'm content with my settings, as I use this for gaming and internet only. I still use my old phone for call and texts.

Try to get it unbricked by a firmware developer in Greenhills or Pasay. I know a guy in Pasay-- solid hacker. He taught me how to hack a SIM for unlimited internet... He has his own forum and he even co-authored some of the steps in IOS jailbreaking and Android rooting.

---------- Post added at 10:01 AM ---------- Previous post was at 09:43 AM ----------

There you have it guys, I hope this answers some of the questions you have or I hope this method works for yalls.
[General Questions and Answers] earl22online:
>>>

Ok thanks for the infos…so, the ".android folder" you are telling is in my sdcard of my phone right, is that correct sir? i have also 16GB of micro sdcard, what is the best procedure of partitioning you used on your 16GB sdcard sir? can you give me the link sir for the partition procedures? about the BOOT-LOOP error you are telling, what is the best way to overcome this or precautions (ways) so that it will not happen in our phones? are there limits in the number of apps that we will only install on the 2nd partition (2GB)? what is the format you used in your 2nd partition sir?