yashsingh1/xdaforums huggingface dataset:
[Upgrading, Modifying and Unlocking] jason_cheng:
Sorry, the W10 is my first ever experience with Android (I was looking for a cheap way to find out how the stuff works), and as it does not even have a bootloader mode I have no idea about fastboot. I have only been with this phone/Android for about a month, so there's still a lot more to learn.

But as far as I can tell "AP Fastboot" already implies that you are in fastboot mode. You need the fastboot drivers installed on your PC, and then when you are at the green screen the phone will accept fastboot commands. [1]

If you guys manage to do this, what I would suggest is hot-loading a Karbonn A7, Mobiistar S01 or any other potential compatible CWMR image, then immediately making a full ROM backup. You can then upload recovery.img and I'll see if I can port it, and after that boot.img so we can at least get you root adb shell if by then rooting is still a problem.

And btw, if it was not clear in my previous post, rooting using current "standard" methods is not going to work as the latest gingerbread vulnerability (which zergrush exploits and many of the tools use zergrush) has been patched since December 2011. Unfortunately, it looks like the build of 2.3.6 that the W25 has is from a period after that, so zergrush on the W25 is a no-go. If you want to try, just follow the adb steps above which was posted for ahmed.zunaid.

[1] http://www.androidcentral.com/how-i-back-my-stock-unrooted-galaxy-nexus
[Upgrading, Modifying and Unlocking] ahmed.zunaid:
Can't find CWMr for karbonn a7, mobistar s01 or k-touch w650. Any other similar model out there which can use CWM for this phone ?

http://www.clockworkmod.com/rommanager/
[Upgrading, Modifying and Unlocking] jason_cheng:
It is here: http://xdaforums.com/showpost.php?p=29300082&postcount=12

Download CWM-English.rar, you need recovery-english.img. Do NOT run recovery.bat! But you can use the adb and fastboot executables from the folder if it's convenient.
[Upgrading, Modifying and Unlocking] ahmed.zunaid:
Ok thanks. I'll use ADB. I'll get back to you afterwards....

Edit:

CWM Backup done ! Saved in: "SD card > clockwork mod > backup" (thanks for the help) :highfive:

What next?

Should I Upload it? Maybe it'll help you understand what's wrong with it ...
[Upgrading, Modifying and Unlocking] jason_cheng:
Great, now you can experiment all you want!

Since the load works, it is surely compatible with your phone. So go ahead and flash that CWMR image:

fastboot flash recovery /path/to/the/recovery.img

If anything goes wrong, you can just reflash your stock recovery so keep one copy zipped up and stored somewhere safe. You're lucky CWM works without a hitch, porting to the W10 is proving to be difficult as none of the hardware buttons function as the select action, I can only scroll :/

Anyway, yes, upload the boot.img.
[Upgrading, Modifying and Unlocking] ahmed.zunaid:
Wait, which CWMR image ar you referring to? is it on the A7 thread?

HERE is the link to boot.img (in a zipped folder)
[Upgrading, Modifying and Unlocking] ahmed.zunaid:
hey when i go to recovery mode (press hold power + vol up tll screen turns red) it opens the stock recovery module. not the clockwork recovery. I have to push cwm each time to my phone to go to clockwork recovery. It is normal? shouldn't cwm be a permanent thing?
[Upgrading, Modifying and Unlocking] jason_cheng:
Yes, the one you downloaded and temporarily booted from.

Correct. That's what 'fasboot boot' does. Now you can 'fastboot flash' it to make it permanent. If you had flashed it and it turned out not to be compatible, you would've bricked recovery. fastboot boot allows you to safely test images.
[Upgrading, Modifying and Unlocking] ahmed.zunaid:
Oh I get it now. Plz dont mind if you find my questions stupid. :p I'm new to android OS and have practically no knowledge of it. Thanks for helping me out btw.

Anyways, I'll try it and report back to you

[EDIT]

Ok it's done. CWM appears when i press power+volumeUP after the red screen. what should i do next?
[Upgrading, Modifying and Unlocking] jason_cheng:
We are all guilty of being stupid, since nobody is born Chuck Norris, so don't mention it :)

Next is getting you root shell for ADB (probably not the same as root privileges for the whole system, but I don't know yet) by changing the ro.secure flag. This is done by editing the respective file and repacking the boot image (because the file is copied to the system from boot and is not editable afterwards). [1][2] You will then flash this to the boot partition.

I just want to warn you ahead not to panic if anything goes wrong. If things do go wrong your phone will not go beyond the bootloader stage, but you can reflash the stock boot image from within fastboot and you'll be good to go. This is, of course, as far as I understand (since the recovery is supposed to be a separate partition, and it will always work even if the system boot is nuked).

After getting root ADB shell you will try to see what you're capable of doing with such a shell, notably, removing apps from /system.

[1] http://cjix.info/blog/misc/how-rooting-works-a-technical-explanation-of-the-android-rooting-process/

[2] http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
[Upgrading, Modifying and Unlocking] jason_cheng:
Here is the updated boot image attached. Download and verify the checksums [1]. I figured you'd have 7-Zip installed based on the file you uploaded (it is smaller than what standard ZIP tools can manage), but if not, get it [2].

md5sums:
526a31a531034e30035554fa38b917e5 boot-adbroot_w25.7z
6500835b297b4ab86b410f077e8da836 boot-adbroot_w25.img

Move the image to the SD card, rename it if necessary (to simply boot.img) and then, instead of recovery, flash it to the boot partition. Before that, you should also try to temporarily load it like with the recovery image, but I'm not sure if that'll work. Otherwise, cross your fingers:

fastboot flash boot /sdcard/theimage.img
fastboot reboot

Report back with the output of the following command after you reboot and Android is running as per normal:

adb shell id

[1] http://helpdeskgeek.com/how-to/check-md5sum-in-windows-7/

[2] http://www.7-zip.org/
[Upgrading, Modifying and Unlocking] ahmed.zunaid:
yes I use 7zip

I'll try this and get back to you.

stand by . . . . .
[Upgrading, Modifying and Unlocking] jason_cheng:
OK the attachment is there now. Good luck!
[Upgrading, Modifying and Unlocking] ahmed.zunaid:
this error occurs when I use this command fastboot flash boot /sdcard/boot-adbroot_w25.img

"error: cannot load /sdcard/boot......img" See the 1st attached image. line [1]

When I try to do it like the recovery, it says like the one in line [2] but stays at the green screen

Even if I use fastboot reboot it stays at the green screen and says "waiting for device. . .". Nothing happens afterwards. (see line [3] )

I don't think it went the way as planned. but I ran adb shell id anyway. see the 2nd attached image

N.B. I tried renaming it to boot.img and doing the process again. same thing happens.
[Upgrading, Modifying and Unlocking] jason_cheng:
Nope, it did not. Remember, you have to do the same thing as you did for the recovery, except swap any instance of the word 'recovery' with 'boot'.

OK, now start the phone normally, connect adb and show me output of:

ls /; ls /mnt

A couple of things first, though. 'fastboot devices' lists question marks. Was it like this when you went through the steps for recovery?

Anyway looks to me like a path problem (cannot find /sdcard, maybe your phone just has it in /mnt/sd). Could you tell me exactly what you typed for the recovery hot-loading and flashing processes?
[Upgrading, Modifying and Unlocking] ahmed.zunaid:
but it says 'ls' is not recognized as an internal or external command. See attached image.

yes. ??????????? fastboot (the cwm recovery still works btw).

1 I Downloaded cwmr from [1]

2. unzipped and moved everything to adb folder

3. Went [2]. Also connected phone with usb debugging.

4. Opened cmd window and typed adb devices . It showed w650 as a connected device.

Then adb reboot bootloader. The phone turned off itself and restarted. Not into bootloader, just normal mode.

5. Then I went to fastboot stage (green screen) manually. and connected phone to pc. Typed fastboot devices.

It showed ??????????? fastboot

6. typed fastboot boot recovery-english.img and booted into cwmr

7. followed the exact steps from the post in [1] (step2 of that post) for permanent cwmr

[1] http://xdaforums.com/showpost.php?p=29300082&postcount=12

[2] http://www.androidcentral.com/how-i-back-my-stock-unrooted-galaxy-nexus
[Upgrading, Modifying and Unlocking] jason_cheng:
Ahh, sorry about that. I misunderstood how fastboot works. It reads from your PC (also), not (just) from your phone.

So now rename the file, put it in the same folder where you previously ran 'fastboot boot recovery-english.img' from, and do:

fastboot boot boot.img

If it doesn't load, that means it won't work that way. Nevermind, we flash it then:

fastboot flash boot boot.img

Then reboot:

fastboot reboot
[Upgrading, Modifying and Unlocking] ahmed.zunaid:
It doesn't work. stays at waiting for device. see attached. Should i do the adb commands while phone is on the green screen or when cwm screen appears?.

maybe there is a way by using the cwmr to restore backup image.

if i replace the boot.img and select advanced option to restore only the boot.img, will it work?
[Upgrading, Modifying and Unlocking] ahmed.zunaid:
ok this time I didn't use the temporary method.

i used fastboot flash boot boot.img and it was loaded into the phone. [attached]

but phone could not start. keeps restarting at "symphony" logo.

I restored boot image from backup on cwmr. and the phone is running now
[Upgrading, Modifying and Unlocking] jason_cheng:
fastboot commands and adb commands are different. fastboot commands will only run during the green screen. adb commands may also run during the green screen, but I'm not sure about that.

OK we're done confirming whether it works. It doesn't, unfortunately. And you also confirmed that if anything goes wrong you can restore and all is well :)

I will give you another boot.img (we have to get the 'offsets' right when making the image with mkbootimg), but in the meantime try once again by following these steps first: http://xdaforums.com/showthread.php?t=1660596

Wipe cache and wipe dalvik-cache. Do NOT wipe data! (will erase your personal data; cache is safe to clear) Then go to fastboot screen and redo the flash command and reboot. Failing that, simply go into CWM and restore boot.
[Upgrading, Modifying and Unlocking] jason_cheng:
Here you go. There are two files this time. I want you to try both. First, try the boot.img in the rootrepack folder. Then try the one in the stockrepack folder if the first one fails. Clear all sorts of cache each time before flashing. No need to try to temporarily load it; just flash directly and reboot (if stuck in boot loop, go to CWM and reflash stock boot, then repeat).
[Upgrading, Modifying and Unlocking] ahmed.zunaid:
Ok it worked. Tried both of them using that method. Now phone is using the boot.img from your rootrepack folder.

took a bit longer to startup though. maybe because of wiping the cache.

What to do next ? [.___.]
[Upgrading, Modifying and Unlocking] jason_cheng:
Yes, correct. The cache is rebuilt (it shouldn't take as long from subsequent boots).

adb shell id

While the phone is running. Let's see what that returns.
[Upgrading, Modifying and Unlocking] ahmed.zunaid:
uid=0(root) gid=0(root)
[Upgrading, Modifying and Unlocking] jason_cheng:
:D

Now, let's see what we can do:

adb remount
adb shell touch /system/pwned && echo success || echo fail

Just copy-paste the output, no need screenshot.

Btw if you're familiar with IRC I'm available on the Freenode network in #android-root :)
[Upgrading, Modifying and Unlocking] ahmed.zunaid:
Not sure how to use IRC. not familiar with it.

Anyways,

C:\Users\ZunA\AppData\Local\Android\android-sdk\platform-tools>adb remount

remount succeeded

C:\Users\ZunA\AppData\Local\Android\android-sdk\platform-tools>adb shell touch /

system/pwned && echo success || echo fail

touch: not found

success
[Upgrading, Modifying and Unlocking] jason_cheng:
Crap. All these funny vendors not supplying useful shell commands. OK nvm try:

adb remount
adb shell echo "1" > /system/pwned
adb shell cat /system/pwned

If the last output of that is "1" then congratulations, you have root! If not, we'll have to see what's preventing write access. Otherwise, go ahead and download the attachment. Unpack, and copy the 3 files to the folder from where you're running ADB.

Then you need to check whether su already exists:

adb remount
adb shell which su

It should return a path (means it exists) or say "no su" (it does not). Even if it does, there may be something wrong with it, so back it up and replace it as well as push all necessary binaries:

adb pull /path/to/su su.bak # you would've got the path from above
adb shell rm /path/to/su
adb push su /system/bin/ # this is the su from the attachment
adb push busybox /system/xbin/
adb shell
# you should now be dropped to a shell on the phone
chmod 4555 /system/bin/su
chown root:root /system/bin/su
chmod 755 /system/xbin/busybox
exit
# now you are back on cmd prompt
adb install Superuser.apk

Now, that looks pretty daunting, I know. But just follow line by line and you'll be good to go ;)
[Upgrading, Modifying and Unlocking] ahmed.zunaid:
C:\Users\ZunA\AppData\Local\Android\android-sdk\platform-tools>adb shell echo "1

" > /system/pwned

The system cannot find the path specified.

C:\Users\ZunA\AppData\Local\Android\android-sdk\platform-tools>adb shell cat /sy

stem/pwned

/system/pwned: No such file or directory

C:\Users\ZunA\AppData\Local\Android\android-sdk\platform-tools>adb remount

remount succeeded

C:\Users\ZunA\AppData\Local\Android\android-sdk\platform-tools>adb shell which s

u

which: not found

haven't tried the other codes. don't know path to su
[Upgrading, Modifying and Unlocking] ahmed.zunaid:
ok this time I used only adb shell at the first line.

C:\Users\ZunA\AppData\Local\Android\android-sdk\platform-tools>adb shell

# echo "1" > /system/pwned

echo "1" > /system/pwned

# cat /system/pwned

cat /system/pwned

1

# which su

which su

which: not found

#
[Upgrading, Modifying and Unlocking] jason_cheng:
Sorry about that. The redirection (the ">") was treated inside the windows prompt (so the prompt was searching for the path on the PC), not in the shell. You did the right thing by just opening a shell, good job ;)

OK bro, you are officially root :D Please now remove that test file you created for the sake of cleanliness:

adb shell rm /system/pwned

And it seems yet again the phone does not have another *NIX command. Not an issue, after all we're only concerned whether su already exists and we want to replace it.

Actually the files are there for your convenience and immediate testing. You can just get both BusyBox and Superuser from the market [1][2]. I don't know if the Superuser app comes with a su binary, but if it doesn't, simply:

adb remount
adb push su /system/xbin/su
# changed perms slightly so it may be updated by other apps
adb shell chmod 4755 /system/xbin/su

Try the apps, first Superuser, then BusyBox (not mandatory but some root apps may require it). So, tap the install button :)

[1] https://play.google.com/store/apps/details?id=com.noshufou.android.su&hl=en

[2] https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
[Upgrading, Modifying and Unlocking] ahmed.zunaid:
Whut ? That's It? Dude you sure? :laugh: The phone doesn't feel different though. Though it would shoot lasers and stuff :p

Man, thanks a lot for helping me out. I'll DL superuser and busybox then report back if any error occurs

[EDIT] No errors were found for superuser and busybox

Plz tell me the process how to allow superuser access to move files to sdcard.

Alsio suggest me some work I can do with the newly rooted phone

Again, thaks a lot, Bro .. :D
[Upgrading, Modifying and Unlocking] jason_cheng:
Well to be really sure you must get su up and running. I think having BusyBox will test whether you really "have root", or you can get an app like Root Checker (just search, pick the first result).

But otherwise that should really be about it, because the objective was a root shell (the environment that lets you run commands). You see, you were able to create a file in the system partition. That means read-write access to /system, which in turn means being able to modify anything in that partition. The Superuser app is merely a wrapper around the su binary, which forwards any request made to it.

But that also means the Java layer is dependent upon the su binary. Even if you have root via ADB, if su for some reason fails to run properly (it can happen, as it did for the stock binary on my W10), it's as good as no root and you're left to do everything manually (no nice root apps).

You have to keep in mind that one can't really "move" apps to the sd card by just moving the APK. This is because the data the app stores is still on the internal memory, in /data. Thankfully this is where apps like data2sd come in. However, I myself am rather new to Android though not to GNU/Linux (an OS using the Linux kernel for the desktop) and I have yet to do anything more than remove the bloat. I am slowly filling up the internal storage once more.

Building a ROM based on a popular custom distribution (CyanogenMod) should be a reasonable target, but it's not looking trivial at the moment because of the lack of dual-sim ROMs. All you can do is basically repack (which are the ROMs you see currently for the other Indian and Chinese phones) with themes and stuff. Do nudge this thread or PM me if you happen to chance upon a custom ROM for such dual-sim phones, or we may create a new thread which could serve as a placeholder for all things Symphony.

Don't mention it. We jump in to tinker with these phones, we potentially help a small minority out there who cannot afford or have no access to better phones. So far we can vouch for the Symphony Xplorer W10 and W25 :)
[Upgrading, Modifying and Unlocking] ahmed.zunaid:
Used Root checker. Says my phone has root access. :)

there are ics and miui roms availabe for karbon a5, which are said to be working with a7 as well. Do you think these will work on our phones?

Won't try if its a no go.

Off topic: If you happen to create a group or fan page on facebook about rooting symphony phones, pm me the link

I had one problem. I installed beats audio driver without backing up. after that each time I slide to unlock, Phone makes loud noise (like radio without antenna) I restored boot and system with cwmr, and phone is ok (so far)
[Upgrading, Modifying and Unlocking] Equama:
wow!!!so u just rooted symphony w25.good job. :good:

now try to make a tuotorial for others.it will help them.many peoples are waiting for this.

thanks to ahmed.zunaid & jason_cheng.

which beats driver?from play store or from xda?
[Upgrading, Modifying and Unlocking] ahmed.zunaid:
from play store. I don't recommend that driver to symphony. If anyone happens to to know how to install it on symphony phones, please share.

I'll make a tutorial at the first page. credit to jason_cheng
[Upgrading, Modifying and Unlocking] Equama:
i tried that one from play store.i didnt make any change.try to flash any beats mod.search in this forum.i saw a thread about beats audio mod which contains a flashable zip for all android.
[Upgrading, Modifying and Unlocking] ahmed.zunaid:
Thanks, I'll try it later maybe. Plz suggest me on how to make partition on sd card and move apps there to free up phone space.
[Upgrading, Modifying and Unlocking] Equama:
for sd partition use minitool partition wizard home edition. better use fat32 format.

and download link2sd from play store.

you can read this thread.

http://xdaforums.com/showthread.php?t=919326 (link edited)
[Upgrading, Modifying and Unlocking] jason_cheng:
Very likely, yes (w25 only). You have CWM, so there's nothing to lose. Flash them!

Unfortunately I do not use Facebook, or any social networking site for that matter :p

But we can start a thread here (serving as a central info for all Symphony Androids), or I can put up a simple webpage with a simple URL if that helps more people (since some may not be familiar with forums). I'll see to that when I get some time next weekend.

I am not particularly familiar with this as of yet, but it looks interesting.

Anyway, don't go pushing all credit to me. Without your patience we could not have found what worked and what did not. I believe 6 pages to "just root" was worth it :)

I'll also see if I can put the steps into a batch script for Windows and a shell script for GNU/Linux. Enjoy your newfound powers!

P.S.: You may want to edit the thread title and prefix it with [SOLVED]
[Upgrading, Modifying and Unlocking] Equama:
Jason_cheng, do you know how to root mt6575 devices? there's another phone name symphony xplorer w5.see the attached pics for details info.it's similar to the micromax superfone a52.
[Upgrading, Modifying and Unlocking] jason_cheng:
Oh, the W5 :) It's only slightly less expensive than the W10, but hardware-wise it looks much better to me. Do you own it? Is it good?

Well, since it's an MTK65xx, I really want to believe that it's very rootable. But you never know. So the only way to find out is to execute ZergRush on it, or see what others have posted about the A52. Unfortunately even similar phones do not come with the same build of Android, so vulnerability may be patched on one and not the other. To verify, see what X-Ray says. [1]

We could get more info from build.prop, like whether it's an engineering or user build (the W10 is eng, unsecured while W25 is user, i.e. fully secured no root by default).

[1] http://www.xray.io/
[Upgrading, Modifying and Unlocking] ahmed.zunaid:
I'll change the first post of this thread with a tutorial on how to root the w25. I need some time for that. Please be patient everyone....
[Upgrading, Modifying and Unlocking] ahmed.zunaid:
Done. Tutorial on the 1st Post of this Thread. Check it out. [SOLVED] Rooting Smphony W25
[Upgrading, Modifying and Unlocking] Equama:
i don't have w5.my elder brother own it.it's really a good device within this price range.

i will try with zergrush soon.i used zergrush on ubuntu long back to root my live with walkman.

oh w10 is unsecured! that's why many people already rooted it with unlock root.and someone told me update.zip from karbon a7 thread worked with w25.

and i have boot.img and recovery.img from w50 from a user. though i am not sure recovery.img is from w50, coz he had already rooted by following micromax a75 rooting method. he is also using custom rom made for a75.

i read the a52 thread. but i got no solution to backup my own rom.but there's rooted and non-rooted a52 boot.img in that thread.

---------- Post added at 08:13 PM ---------- Previous post was at 08:11 PM ----------

ok.take your time.eagerly waiting for tutorial. :)
[Upgrading, Modifying and Unlocking] Equama:
so, may i share it?
[Upgrading, Modifying and Unlocking] ahmed.zunaid:
The update.zip from karbon a7 thread is actually mobistar s01 stock rom with superuser integration. su binaries are pushed into that rom. It should work on w25. But the thread starter told me that chances of bricking my phone is higher.
[Upgrading, Modifying and Unlocking] Equama:
yes i thought. but someone told that's why i asked did you try that or not.
[Upgrading, Modifying and Unlocking] ahmed.zunaid:
no. But I'll try ICS. Might try MIUI as well. I'll do it and see if it works on the phone or not. Tutorial posted btw.
[Upgrading, Modifying and Unlocking] Equama:
thanks for the tutorial.
[Upgrading, Modifying and Unlocking] Ins3ne33:
About W50

Hi Guys ....... i have Rooted the W50 and installed a new rom .... and its running without aa prob a wanna post a TUT bt i don't how to post in xda ! i'm new around here ! :good: