Develop Bugs

[TUT] Smphony.W25/Karbonn.A7/Mobistar.S01/Ktouch.W650 Rooting Process and Custom ROMs

Symphony W25 device Finally Rooted !
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
All credits go to jason_cheng
Procedure given below:
1. First of all, you need Drivers For your symphony W25 (Smphony.W25/Karbonn.A7/Mobistar.S01/Ktouch.W650 All are the same phone)
Driver for winXP
Get them here (uploaded by prasad12ka4) Or Here uploaded by rainwalker
Click to expand...
Click to collapse
Drivers for Win 7 / Win 8
Get them here
Click to expand...
Click to collapse
64-Bit Win 7 Drivers
Get them here
Click to expand...
Click to collapse
Install them while connecting your phone on "USB debugging mode", and going to "device manager > other devices" on your pc. After installation disconnect the phone.
(I believe some of you are having problems installing the drivers. I recommend you install the drivers on a freshly installed winXP pc. I faced a lot of trouble doing it on my Win8 pc)
2. Download Android software development kit (SDK) from Here and install in pc. Default installation Directory should be C:\Program Files\Android\android-sdk
3. Android SDK may need Java development kit (JDK) installed in pc. If you need jdk, go here or go to their Website to download
3. Download Fastboot From Android Central and keep it inside
C:\Program Files\Android\android-sdk\platform-tools folder
4. Download Clockwork Mod Recovery for w25 from Link #1 or Link #2, unzip and copy to the same folder. replace duplicate (if prompted).
5 hook your phone up with pc in USB debugging mode and go to C:\Program Files\Android\android-sdk\platform-tools folder, Press Shift+right click inside that folder and select "open cmd window here". It opens a cmd window for that folder.
In the cmd window, type
Code:
adb devices
If the driver installations are correct, you'll see your device connected as w650 (as symphony is re-branded from k-touch w650)
6. Disconnect phone from pc and reboot it into the bootloader, by turning it off and holding [vol-up]+[power]
Till screen turns green and says fastboot:recovery ?, Like below
7. Plug your phone into your computer. On cmd window, type:
Code:
fastboot devices
Reply should be "???????????? fastboot" Meanng fastboot detected the device.
8. In the cmd line, type
Code:
fastboot boot recovery-english.img
And that's it. You'll have booted into the custom recovery (cwmr), and from there you can do a full backup, or restore a backup, or wipe the phone. Use vol up/down to navigate through screen and Power to select an item.
9. Use CWMr to backup your ROM. (It will be saved in: "SD card/clockwork mod/backup" on phone.) and reboot. Copy the backup into pc for further use.
Step 8 was to make sure cwmr works on the phone. It's a temporary port of cwmr on your device.
if problem occurs (less likely to occur), let us know in a comment and don't proceed further.
Otherwise, Proceed below for permanent port..
10. Repeat step 6 and 7. Go to C:\Program Files\Android\android-sdk\platform-tools folder and click on recovery.bat file. Click on it and in the next window, Press any key
Permanent port will be completed
reboot phone if not rebooted automatically.
11. To check cwmr, Repeat step 6 but keep pressing the two buttons even if the screen turns green (fastboot). Continue until.....
screen is red (recovery). after that you'll see Clockwork mod recovery page.
You'll need it to restore your original rom if you mess up anything.
12 In CWMr,
a)]Go to Advanced
b) Choose "Wipe dalvik-cache"
c) Now go to "Mounts & Storage"
d) Choose "Format /cache"
e) Shutdown your phone
13. Download and unzip bootrepack from this post (by jason_cheng). Copy the "boot.img" file from "rootrepack" folder and paste to C:\Program Files\Android\android-sdk\platform-tools folder
14. Repeat steps 6 & 7 (green screen)
15. In cmd window type
Code:
fastboot flash boot boot.img
and
Code:
fastboot reboot
see image below if you have any confusion.
16. After the phone is restarted, type in cmd window:
Code:
adb shell id
which should result "uid=0(root) gid=0(root)"
Rooting is now Unofficially completed
17. To verify, Type each line in cmd window, and press enter
Code:
adb shell
Code:
echo "1" > /system/pwned
Code:
cat /system/pwned
If the Reply to the last line is "1", Congrats ! you have root access to your phone!!
Now remove that test file you created just now. Type:
Code:
rm /system/pwned
What now?
18. Install "Superuser" from Play store
It does not come with su binary. For that, Go to this post and download only the attachment. Unzip it and put the files in C:\Program Files\Android\android-sdk\platform-tools folder.
19. Now open cmd window, type each line and enter.
Code:
adb remount
Code:
adb push su /system/xbin/su
Code:
adb shell
Code:
chmod 4755 /system/xbin/su
now open superuser and check for su binary. I don't recommend su update.
20. Install "Busybox free" from Play store (optional)
Rooting Officially Complete.​
If you face problems at any step, please let us know in comments. We'll try to help.you out.
Also feel free to try out the IceCream Sandwitch based roms & the upcoming Jelybean rom for Symphony W25 on the second post of this thread.
If any of you come across a new rom for w25. Please do share.
If you come across dead links on my thread, plz let me know by posting comments, or PM me.
If you find this post useful, then plz hit the thanks button and share it with people who have this phone and waiting for root
End of tutorial.​
.usefull links:
Karbonn Mobile A5 & A7 (Android 2.3.6)
Link2sd tuorial in bangla: সহজেই বাড়িয়ে নিন অ্যান্ড্রয়েডের ইন্টারনাল মেমোরি
How To Solve Internal Memory Problem(Great Post)

Custom Roms for Symphony W25 / Mobistar s01 / KTouch W650 / Karbonn A7
Custom Roms for Symphony W25 / Mobistar s01 / KTouch W650 / Karbonn A7
Here you'll find Custom ROM For Karbon A7 device. Which might also be campatible for Symphony w25. Read the respective posts/ comments carefully before downloading and installing.
(first of all back up your existing ROM with cwmr before any change you do to it.)
1) ICS ROM v1 for Symphony W25, Created By rainwalker
Click to expand...
Click to collapse
2) ICS ROM v2 for Symphony W25, Created By rainwalker
Click to expand...
Click to collapse
3) MIUI Gingerbread 2.3.7 ROM (update.zip file), moded By rainwalker
Click to expand...
Click to collapse
4) Rooted Stock ROM of Symphony W25 (update.zip file), uploaded By rainwalker
Click to expand...
Click to collapse
5) Stock Google android gingerbread for a7 by meosuper
Click to expand...
Click to collapse
6) ICS Huawei For Karbonn A7 / S01 by meosuper, Uploaded by ItsmezakiR
Click to expand...
Click to collapse
7) Official ICS ROM for Karbonn A7/Symphony W25 Uploaded by The Droid Master
Click to expand...
Click to collapse
8) Walton Primo ROM modified for A7 Uploaded by vinodkbishnoi
Click to expand...
Click to collapse
9) XION ROM FOR A5/A7 Uploaded by deadlyindian
Click to expand...
Click to collapse
10) ICS refresh V3 Uploaded by meosuper
Click to expand...
Click to collapse
11) CyanogenMod 10 (Karbonn A7) Beta Posted by prasad12ka4
Click to expand...
Click to collapse
12) Backstreet MOD™ v4.1.1 created by The Droid Master
Click to expand...
Click to collapse
13) Lithium 7 for Karbonn a7, symphony w25 and Mobiistar s01 Created by rainwalker
Click to expand...
Click to collapse
14) XINIX 8 for Symphony w25 Created by rainwalker (Recommended)
Click to expand...
Click to collapse
15) CyanogenMod 10 rom for W25 [Beta]
Click to expand...
Click to collapse
16) JELLYBEAN rom for W25 [Beta]
Click to expand...
Click to collapse

Maybe is needed to extract the "boot.img" to remove the restrictions on it, and make it rootable... Have you tried with generic "rooters"?

ICS Baseband Versions For Karbonn A7
ICS Baseband Versions For Karbonn A7 (= Symphony W25)
ItsmezakiR said:
1. 591369_8379_WCDMA_V000001
2. 591357_8376_WCDMA_V0005
3. 591352_8376_WCDMA_V0007
4. 591347_8376_WCDMA_V3070
Click to expand...
Click to collapse
ICS Search Key to Power Key (for Symphony W25)
vinodkbishnoi said:
Hi,
Karbonn A7 ICS. Now you can use search key of your A7 as power key.
Follow the procedure...
1. Download 7x27a_kp.kl.zip file and extract it.
2. Open terminal/Command prompt.
3. Connect your phone to PC via USB.
4. Run following commands.
c:/> adb devices
c:/> adb pull /system/usr/keylayout/7x27a_kp.kl
now copy this file on a safe place. So that if anything goes wrong you could be able to restore it.
now open folder where you have extracted the zip file. The extracted file will be of same name as "7x27a_kp.kl"
c:/> adb push <path to file 7x27a_kp.kl> /system/usr/keylayout/​
Now reboot your phone. You will be able to use your search key as power key.
Click to expand...
Click to collapse
Change partition size on A7/W25
Part1:
Anil_Sharma said:
To begin with, you need a hex editor, HxD - Freeware Hex Editor is a great editor and it is very small(less than an MB). Then you need a baseband to edit, you need to locate the file named ' appsboot.mbn '.
That file contains the partition tables, remember this tutorial is about editing the partition tables not extending your physical memory.
So, lets get cracking. Open HxD from programs and open the appsboot.mbn file, now press F3 and search for ' cache ' and press F3 until you see something like this
.
As you can see the highlighted section of the picture
,
there are a few repetitions of ' F0 F0 F0 F0 xx ' multiple times, you are concerned with only the first two /system and /cache partitions respectively.
Remember, you don't need to specify the partition size for /data as it is done automatically when you flash the baseband.
Now back to the hex editing part, once you've decided how much space(in MBs only) you wanna allocate to /system and /cache use this link to Convert hex/dec and select the two digits after the F0 F0 F0 F0 like in this pic
and type the hex number for example in the screenshot B4 in hex equals 180 in decimal, which means /system is allocated 180 MB of space and do the same with Cache, I would recommend allocating 10 MB to it as you hardly ever use it. Then flash the baseband like you normally do through Fastboot.
If you have any doubts ask me and I will do my best to clear things to you. Click Thanks if I helped you, doesn't cost anything
Click to expand...
Click to collapse
Part2:
vinodkbishnoi said:
Hi,
I am attaching a file named "appsboot.mbn". This is used to determine partition size on android system.
There are two ways you could use it.
1. Replace appsboot.mbn file in any baseband update BP folder.
2. If you are handy with fastboot commands there is very simple method. Just boot your phone in fastboot mode (green screen mode) and use
following command....
C:\>fastboot flash APPSBL <path to appsboot.mbn>​
And you are done.
You will find following changes.
1. Your partition size will be as shown in screenshot.
2. When you run command adb devices you will no more find S01 there, it will be A7
Download file here...
Download
Thanks
Click to expand...
Click to collapse

no one for help??

ahmed.zunaid said:
no one for help??
Click to expand...
Click to collapse
Your phone is the same with mobiistar s01 and karbonn a7, maybe the developer of symphony keep the original cpu clock(1ghz) and s01, a7 was underclocked to 800 to save battery. Now if you want to root.you must install fastboot driver and install cwm recovery for a7 first.then backup your current rom... when done, install rooted rom for s01 and you will have root, but your cpu will be underclocked to 800ghz.
And can you send me the link to download your backup rom??? I need the 1ghz kernel to mod my rom... thanks.
(If install drivers on w7 pc fail, try to use another pc with wXP-32bit).

These phones aren't - or shouldn't be - that difficult to root. I have just rooted an Xplorer W10 from W7 x64 (and reproduced on Linux), and it went without a hitch. Just a number of gotchas to watch out for (from here on I actually refer to W10 and all other models since they are of the same series):
1. Uninstall any kind of driver you have installed. Symphony does not provide drivers for their Android phones, as far as the website is concerned. You get what you pay for, and this is a relatively remote brand, so don't expect much. In fact, don't expect anything at all.
2. Download and run SuperOneClick. Click on the other tab and choose to check for drivers. You should be prompted to install a driver. Do it.
3. Unplug and replug the USB. Go into the ADB folder and shift-right-click, open a command prompt here. Type 'adb devices' and press ENTER. There should be at least one device listed (in the form of an alphanumeric serial).
4. If there is no device listed by ADB, use Linux to root. There is no need to install any driver on Linux, and SuperOneClick is multi-platform. You will need the mono package on Linux instead of .NET.
5. The phone is actually partially rooted. Whether by intention or by mistake, I am not sure. SuperOneClick will warn of this, so just choose to continue with the rooting process.
6. You should now be rooted.
Background:
There is no exotic bootloader locking going on with these phones, as far as I can tell. The manufacturers/vendors are really just trying to capture a certain segment of the market, so I doubt they'd go through extensive efforts to lock you in. Just find any exploit (right now psneuter and zergRush), put them on the phone along with the su and busybox binaries, execute the exploit, and you'll be good to go with the Superuser app.

ok ...
jason_cheng said:
These phones aren't - or shouldn't be - that difficult to root. I have just rooted an Xplorer W10 from W7 x64 (and reproduced on Linux), and it went without a hitch. Just a number of gotchas to watch out for (from here on I actually refer to W10 and all other models since they are of the same series):
1. Uninstall any kind of driver you have installed. Symphony does not provide drivers for their Android phones, as far as the website is concerned. You get what you pay for, and this is a relatively remote brand, so don't expect much. In fact, don't expect anything at all.
2. Download and run SuperOneClick. Click on the other tab and choose to check for drivers. You should be prompted to install a driver. Do it.
3. Unplug and replug the USB. Go into the ADB folder and shift-right-click, open a command prompt here. Type 'adb devices' and press ENTER. There should be at least one device listed (in the form of an alphanumeric serial).
4. If there is no device listed by ADB, use Linux to root. There is no need to install any driver on Linux, and SuperOneClick is multi-platform. You will need the mono package on Linux instead of .NET.
5. The phone is actually partially rooted. Whether by intention or by mistake, I am not sure. SuperOneClick will warn of this, so just choose to continue with the rooting process.
6. You should now be rooted.
Background:
There is no exotic bootloader locking going on with these phones, as far as I can tell. The manufacturers/vendors are really just trying to capture a certain segment of the market, so I doubt they'd go through extensive efforts to lock you in. Just find any exploit (right now psneuter and zergRush), put them on the phone along with the su and busybox binaries, execute the exploit, and you'll be good to go with the Superuser app.
Click to expand...
Click to collapse
I've used SuperOneClick before. In both 7 and XP machines. It gets stuck at "step 7".
Ok i'll try to do it again following your steps. I'll upload the screenshots
thanks for helping btw ...

No use ....
Nope. It didn't work. Hangs at step 7 (Pic Attached). tried on XP and 7.
Drivers install this time. and cmd>adb shell shows attached device, just like you said. but nothing happens after step7: waiting for device
I guess this process in not for me
can you provide link or tell me the process on how to add cwm recovery and backup the stock rom from the phone?
So that I can upload for you guys to check it out.
Note: my phone goes to recovery mode using the same method described in Karbonn Mobile A5 & A7 (Android 2.3.6
I checked.

ahmed.zunaid said:
Nope. It didn't work. Hangs at step 7 (Pic Attached). tried on XP and 7.
Drivers install this time. and cmd>adb shell shows attached device, just like you said. but nothing happens after step7: waiting for device
I guess this process in not for me
can you provide link or tell me the process on how to add cwm recovery and backup the stock rom from the phone?
So that I can upload for you guys to check it out.
Note: my phone goes to recovery mode using the same method described in Karbonn Mobile A5 & A7 (Android 2.3.6
I checked.
Click to expand...
Click to collapse
Unfortunately, CWMR needs to be built for your hardware in order for it to work. I think CWMR for the Karbonn should work without modification if it has the same hardware, so see if you can find info on getting CWMR onto the Karbonn. If the bootloader is really locked then you'll have to find some way to unlock first.
Backup the recovery partition [1] before doing anything, although I cannot verify whether it's the same partition across all phones. If anything goes wrong you will lose the ability to boot into recovery mode, but your phone will work. With a backup of the partition you can just bit-copy and rewrite the partition exactly as it was.
Because you already have the drivers installed using SuperOneClick, you may like to see now if Unlock Root works [2]. Else, go ahead and root the phone using the manual method. First, run the exploit [3]. Tell us how this goes, then we'll continue (basically upload the su binary and optionally the Superuser app). Otherwise we need to see what other exploit works.
[1] http://forum.xda-developers.com/showthread.php?t=1160213
[2] http://lifehacker.com/5873745/unlock-root-roots-nearly-250-android-devices-in-one-click
[3] http://forum.xda-developers.com/showthread.php?t=1296916

Could you please also report back with some files after running the following commands (you will find them prefixed with w25_ from the folder you're running ADB):
Code:
adb shell cat /proc/cpuinfo > w25_cpuinfo.txt
adb shell getprop > w25_propinfo.txt
Thanks. I suspect the W25 does not have the Karbonn A7 hardware. If the Karbonn is a rebranded Mobilstar S01 then it has a Qualcomm ARMv7 processor. The Symphony phones (hypothesis based on the only one phone I have, that is a W10) are rebranded Tinno [1] phones, with MediaTek processors.
My W10 is ARMv6, so it depends on whether the W25 has an SoC based on the latest MTK proc (which is ARMv7) [2]. That is highly unlikely because it (the proc) would be too powerful for the model number. As you may or may not know, binaries are not portable across ARM cores.
The phones do indeed have the same chassis and general specs, but any attempt to port and/or copy files/ROMs must be taken with great care and precautionary steps. There is, of course, no rule that each model must depend on the same manufacturer, but it's better to be safe than sorry.
[1] tinno.com (i'm not allowed to post links, funny, did so in the previous post)
[2] mediatek.com

jason_cheng said:
Could you please also report back with some files after running the following commands (you will find them prefixed with w25_ from the folder you're running ADB):
Code:
adb shell cat /proc/cpuinfo > w25_cpuinfo.txt
adb shell getprop > w25_propinfo.txt
Thanks.
...... ...... ......
Click to expand...
Click to collapse
#1 cpuinfo Attached
#2 Prop info Attached
It says ARMv7 processor. So what should I do now?
[off topic. rooted my friends Xperia arc today. Was very easy, like : DL kernel>click some stuffs>plug out>turn off>press n hold button>plug in>done
they should've made it simple for this one. just sayin .. :/ ]

ahmed.zunaid said:
#1 cpuinfo Attached
#2 Prop info Attached
It says ARMv7 processor. So what should I do now?
[off topic. rooted my friends Xperia arc today. Was very easy, like : DL kernel>click some stuffs>plug out>turn off>press n hold button>plug in>done
they should've made it simple for this one. just sayin .. :/ ]
Click to expand...
Click to collapse
Well, popular devices have more people tinkering with them and hence more results I suppose for budget devices we are on our own. After all, I believe these phones are pretty value for money and the effort to tinker is worth it.
Anyway, my suspicions are wrong. Symphony (or whoever they rely on) hand-pick reference models and do not depend on any particular vendor. The W25 is ARMv7 from Qualcomm, rebranded from K-Touch W650 [1] with modest hardware upgrades, almost similar to the Mobiistar and Karbonn:
Mobiistar Touch S01: Qualcomm MSM7225A
Symphony Xplorer W25: MSM7627A or MSM7625a (but because of 1GHz clock more likely the former) [2]
Either way the differences are minor I presume. Clock speeds are different and on-chip options vary slightly depending on what the manufacturer opts for. So with a bit of work someone could port existing recoveries and ROMs from similar devices. See [2] for a list of such devices in the respective row for MSM7627A.
You can worry about this when you come to recovery. The first hurdle to get through is root, so have you proceeded to run an exploit?
Also, if you haven't done anything, I would suggest doing a factory reset and then backing up the entire ROM simply with the cat command [3]. The homemade unsigned backup may come in handy later as there is no official ROM update.
[1] 123.chinatronic.com/products.php/K-Touch-W650 [replace 123 with www]
[2] en.wikipedia.org/wiki/Snapdragon_(system_on_chip)
[3] android-dls.com/wiki/index.php?title=HOWTO%3a_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images

jason_cheng said:
..... Symphony (or whoever they rely on) hand-pick reference models and do not depend on any particular vendor. The W25 is ARMv7 from Qualcomm, rebranded from K-Touch W650 [1] with modest hardware upgrades, almost similar to the Mobiistar and Karbonn:
Mobiistar Touch S01: Qualcomm MSM7225A
Symphony Xplorer W25: MSM7627A or MSM7625a (but because of 1GHz clock more likely the former) [2]
Either way the differences are minor I presume. Clock speeds are different and on-chip options vary slightly depending on what the manufacturer opts for. So with a bit of work someone could port existing recoveries and ROMs from similar devices. See [2] for a list of such devices in the respective row for MSM7627A. ....
Click to expand...
Click to collapse
it says HTC Desire VC T328d, Huawei Ascend C8812 ...
jason_cheng said:
............
You can worry about this when you come to recovery. The first hurdle to get through is root, so have you proceeded to run an exploit?
Also, if you haven't done anything, I would suggest doing a factory reset and then backing up the entire ROM simply with the cat command [3]. The homemade unsigned backup may come in handy later as there is no official ROM update.
[1] 123.chinatronic.com/products.php/K-Touch-W650 [replace 123 with www]
[2] en.wikipedia.org/wiki/Snapdragon_(system_on_chip)
[3] android-dls.com/wiki/index.php?title=HOWTO%3a_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images
Click to expand...
Click to collapse
Not sure how to use these commands. It says that the phone needs to be rooted to use these.
I'm trying to install clockworkmod.
meanwhile, If you have time, plz provide a simplified tutorial.
The zergrush in http://forum.xda-developers.com/showthread.php?t=1296916 doesn't download btw

Sorry, yes, that needs root. You must do everything you can to get root on the phone, because whatever you do you must have a backup. For CWMR, you must back up your recovery partition, else if your CWMR image does not happen to be compatible with your device you risk losing recovery mode.
For MTK devices like the W10, there is a method for non-rooted phones to carry out the backup [1], but I'm not sure about Qualcomm. So in the end, root is unavoidable.
1. Just get zergrush binary from the SuperOneClick archive (it is in another folder along with psneuter).
2. Copy the zergrush binary to the ADB folder.
3. Open a cmd window in the ADB folder just as you would normally type adb commands, then:
Code:
adb push zergrush /data/local/tmp/
adb shell chmod 755 /data/local/tmp/zergrush
adb shell /data/local/tmp/zergrush
Report back with the output.
[1] bm-smartphone-reviews.blogspot.com/2012/04/creating-rom-dump-of-your-mt65x3-device.html

jason_cheng said:
1. Just get zergrush binary from the SuperOneClick archive (it is in another folder along with psneuter).
2. Copy the zergrush binary to the ADB folder.
3. Open a cmd window in the ADB folder just as you would normally type adb commands, then:
Code:
adb push zergrush /data/local/tmp/
adb shell chmod 755 /data/local/tmp/zergrush
adb shell /data/local/tmp/zergrush
Report back with the output.
Click to expand...
Click to collapse
Hellions with blue flames !
See The attached pic

I have the same phone It's original model is ktouch w650
i evem tried to use update.zip method but it says sd storage not found
how do i know if my bootloder is unlocked or locked
tried unlock root with driver installed it says failed to aquire root access\
in adb shell it shows $ sign and if i try to get root acess it says acess denied

Oh boy, it looks like the vulnerability has been patched in your version of Android. Either that, or there is some hardware peculiarity (buffer size being reported wrongly - that's also when this zergrush error comes up) which I do not yet know how to deal with. There is another exploit called 'tacoroot' but I do not prefer going that route as it's not as foolproof/universal as zergrush.
Update zips need to be signed. When your recovery tries to verify the signature it fails, as it is not the signature of the manufacturer that made the update.zip.
Have you guys tried ALL the rooting methods posted in the A5/A7 thread? In the meantime I'll take a look at how Qualcomm ROMs can be dumped.
edit: I'm pretty sure your device has a fastboot mode. If so, you can "hot" boot any cwmr image without flashing it using "fastboot boot theimage.img" as far as I can recall. Having fastboot is a blessing (which the MTK devices do not have) so follow the first few pages of the A7 thread.

thanks
thanks for your hard work....
can you tell me how to acess fastboot?
and also when i press and hold vlo up and power button its displayes" Ap fastboot:recovery " and screen becomes green and then if i keep pressing it goes red into recovery mood
but if i let go at green screen it stays that way
and when i pressed vol down+ power key it said im black screen and yello text " ENTRY QPST DOWNLOAD "

shaon121 said:
thanks for your hard work....
can you tell me how to acess fastboot?
and also when i press and hold vlo up and power button its displayes" Ap fastboot:recovery " and screen becomes green and then if i keep pressing it goes red into recovery mood
but if i let go at green screen it stays that way
and when i pressed vol down+ power key it said im black screen and yello text " ENTRY QPST DOWNLOAD "
Click to expand...
Click to collapse
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

Please develop some custom rom for micromax a52 android mobile

hi this phone was rooted on 25th sept(after many months of launch).i request the devs here someone to please develop an custom rom for the mobile or just mod the current one.

How to root?
By this time, many users may get rooted but there is no tutorial for that in androidforums so posting here.
Plus, I have modded original boot.img of A52 myself and added init.d support plus support for initializing ext2,3,4 modules on boot.
DOWNLOADS:
1) Unsecured boot.img (zip contains unsecured boot.img + A52 scatter file)
http://www.mediafire.com/?h9ubm9dhq9n7jjd
2) SP.FlashTool
http://forum.xda-developers.com/attachment.php?attachmentid=1353992&d=1348592592
3) Drivers
http://forum.xda-developers.com/attachment.php?attachmentid=1353943&d=1348591411
4) UnlockRoot
http://www.unlockroot.com/
Note: Usemastermind1024 as password to download above files.
Advantages of my boot.img:
I have added init.d support plus ext2.ko,ext3.ko & ext4.ko modules initialization on boot.Just place this ko files in /system/lib/modules/ after rooting the device, u will be able to use Link2SD with ext2,3 or 4 filesystems on your 2nd sdcard partition.
Press thanks if helped
Reference for flashing: MT65x3 flashing tutorial
Read the above tutorial first so u get idea how to flash an img file using SP FlashTool.
STEPS TO FLASH BOOT.IMG:
1) First install the drivers you downloaded & then run SPFlashTool, preferably as administrator (not mandatory)
2) Select USB mode under Options
3) Click Scatter-loading & select scatter file you downloaded from above links.
4) It will automatically load boot.img if it's in the same folder with scatter file otherwise click BOOTIMG & select the downloaded unsecured boot.img
5) Turn off the device fully, remove the battery for 5 seconds to be sure n re-insert the battery but do not power on device.
6) Attach the usb cable with PC but not with device
7) Now click on "Download" button on SPFlashTool, it will show searching for device in lower panel.
8) At this time, attach the cable with device in power off state
9) Now as soon as u attach the cable to device in power off state it will show a progress bar in lower panel n then a dialogue which states successfully flashed n another dialogue showing green colored ring n stating Download OK.
12) Close the dialogues, close the program n reboot the device by pressing power key.
STEPS TO ROOT DEVICE:
1. Power on device.
2. Enable USB Debugging.
- Settings > Application tab > Applications > Development > USB Debugging
3. Install UnlockRoot in pc
4. Attach device using usb cable in debugging mode(u just enabled it in step-2) to pc.
5. Now Run UnlockRoot program and click Root button
6. Confirm online device Micromax A52 in the list which pop-up.
7. Let in finish the procedure and Restart device when is asks.
8. See new Superuser app in app drawer
9. Viola...!!! Your A52 is now rooted.
UnlockRoot does not install Busybox on device so after u rooted the device install busybox to work with many root apps.Search Play Store for Busybox Installer by Jrummy OR BusyBox free by Stericson...
DISCLAIMER:
I am not responsible for bricked devices, dead SD cards, . Please do some research if you have any concerns before flashing! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device
Press thanks if helped

[Q] motochopper not working on 4.2.2

I OTA updated to 4.2.2 I believe and am now on M919UVUAMDL which I think is the primary root of my issues if I have read correctly. I used ODIN and tried to put both the TWRP and CWM recovery files for root on their and it didn't work, I then tried using the setUIDrestrictRemovedKernel thingamajig to fix this issue but that doesn't seem to work either, then I tried motochopper 1.1 to root the device and it failed at the root. I have factory restored and tried again individually on these processes and to no avail.
[*] Press enter to root your phone...
Press any key to continue . . .
[*]
[*] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[*] Device found.
[*] Pushing exploit...
3347 KB/s (1283460 bytes in 0.374s)
[*] Pushing root tools...
2552 KB/s (366952 bytes in 0.140s)
2487 KB/s (1867568 bytes in 0.733s)
2823 KB/s (1578585 bytes in 0.546s)
pkg: /data/local/tmp/Superuser.apk
Success
[*] Rooting phone...
[+] This may take a few minutes.
[-] Failure.[*] <<<<<<<<<<<<<<---------------------------------------------------------------------------- no clue why
Cleaning up...
[*] Exploit complete. Press enter to reboot and exit.
Press any key to continue . . .
any help? I am noobish but can comprehend all the basic rooting methods so please elaborate on your advice if you give any. also I used odin "PDA" function to load these recovery methods if that is incorrect lol then im totally lost.

http://forum.xda-developers.com/showthread.php?t=2268880

That's the thread to use. My wife updated this s4 last night while I was sleeping.
I had to downgrade before I could flash
Sent from my SGH-M919 using xda app-developers app

JimmyTheShovel said:
http://forum.xda-developers.com/showthread.php?t=2268880
Click to expand...
Click to collapse
thank you thank you, about time someone pointed me in the right direction I was roaming the google machine aimlessly to try and find the proper root procedure. thanks again, thanks thanks thanks

So I just got rom manager and want to test my titanium backup restore.zip but it says I have to have cwm recovery first, do I already have it through the root method you gave or do I need to do that as well. Also if I flash a new mod on my phone do I need to ensure the titanium backup is on the sd card or will it remain on the device? :flamethrower:
Sent from my SGH-M919 using xda app-developers app

[Full guide][XM single] How to have full root and use gl2sd,link2sd[]

hi guys ...this is for those need full root and the locked bootloaders of M who are wondering y the phone reboots when mounting on gl2sd...and tried a lot to fix it...
so here the fix...
definitely not by me....
u have to be rooted for this....
[B]Follow the instructions...[/B]
FOR ROOT[Half root]:
use http://forum.xda-developers.com/showthread.php?t=2529561 to root ur device
now download and install Busybox[https://play.google.com/store/apps/details?id=stericson.busybox&hl=en]
now open busybox and wait till it loads...after that make sure the path is /system/xbin then give smart install
till now your phone rooted and busybox installed but u will be having reboot if u try to edit system app..or mounting RW in system or link2sd,gl2sd reboot on mount..[some says this as Half root]...follow next for reboot fix[full root]
FOR REBOOT FIX [Full root]:
u should use the busybox for this fix to work...so dont miss the above procedure..
Download the http://www.2shared.com/file/e9sDTGJk/rootfixer.html? Tool By Anto Kus
Unzip it somewhere you remember
connect ur phone to pc
then run supersu.bat when prompted grant root access on phone
your xm will reboot,Once phone reboots wait for pc to detect phone again then finish supersu.bat then unplug device
Done!
Upto this strictly for M user...
the guide below can be used in any android device
Guide to use SD card for storing apps and Games
FOR storing apps:use LINK2SD:
Get the app from here:https://play.google.com/store/apps/details?id=com.buak.Link2SD
first guys XM/Mdual dont support ext4....please format ur sd 2nd partition to fat32...then u can link the apps....or else u will endup in bootloop...
use mini partition tools for windows...its easy to use...and easy to create a partition....
and connect your phone with MSC mode to PC for partitioning with the mini partition...which will in settings/xperia/usb connectivity/usb connection mode..
see here http://www.xperiablog.net/2011/12/12/link2sd-guide-never-worry-about-internal-memory-limits-again/
and follow the procedure in that site after 3rd step that is backup sd step in that site....[dont try to use that method of rooting...its not for m,just use guide for Creation of partition] ...
and how to link all given on above site...so now we can link apps which is going to be stored on SD 2nd partiton
FOR storing Game data and how to play game:use GL2SD:
get the app from here:https://play.google.com/store/apps/details?id=com.slf.ListglApp
Guide:
first whatever game u need to play...use some website to download them ...bcoz u wont have space required in internal sdcard if u want to download from playstore...
so i assume u have downloaded the game apk + data from some website....and u have extracrted the zip or rar to somewhere in pc...
1.copy the apk to sdcard1...[Note:sdcard1 is ur external sdcard]
2.see the data folder...
mostly data folder has game name inside them mostly android/obb/game name/ or android/data/game name/ [game name will start as com.xxxxxx.yyy] structure will be followed and
some gameloft or reputed company will have their company name/games/game name/ [game name will start as com.xxxxxx.yyy] structure for games
3.now if it has .obb format file inside the above given structures...then copy game name folder and place them in sdcard1/obb/ [eg:sdcard1/obb/com.rockstar.gta3/xxyyyy.obb]
or if it has many folders and files inside the above structure....then copy the game name folder and place them in sdcard1/data/ [eg:sdcard1/data/com.rockstar.gta3/]
4.now install game.apk from sdcard1 and open gl2sd
5.click mount [the joined chain symbol at top] and click play the game...if u didnt see game on list ...just open setting go down and click recover list
6.if u download some medium size game like 250mb directly from playstore..then open gl2sd and click top right button and choose move data and wait till it moves data] after that ur game data is stored on sdcard1 ....now play with same step 5
7.if game didnt open or cant play or some error...restart ur phone...and repeat the 5th step...
8.if game work..cool but remember to unmount[unlinked chain on top] after u finished playing games..or u cant paste anything in sdcard1
[Note:To run game you must mount after every reboot and unmount if u r going to copy some files to sdcard1]
if u cant understand what i said about gl2sd
see this video..maybe it will help u.. http://www.youtube.com/watch?v=adLQgWyYIXQ
now u can mount any app or game to sdcard1...
credits to
dunc4n88
Anto Kus
Xzn
Hendrico Andre and Muhammad Arif
esrom02
and to link2sd,gl2sd app developers

problem with XM C2005
ansebovi said:
hi guys ...this is for those need full root and the locked bootloaders of M who are wondering y the phone reboots when mounting on gl2sd...and a lot to fix it...
so here the fix...
definitely not by me....
u have to be rooted for this....
[B]Follow the instructions...[/B]
FOR ROOT[Half root]:
use http://forum.xda-developers.com/showthread.php?t=2529561 to root ur device
now download and install Busybox[https://play.google.com/store/apps/details?id=stericson.busybox&hl=en]
now open busybox and wait till it loads...after that make sure the path is /system/xbin then give smart install
till now your phone rooted and busybox installed but u will be having reboot if u to edit system app..or mounting RW in system or link2sd,gl2sd reboot on mount..[some says this as Half root]...follow next for reboot fix[full root]
FOR REBOOT FIX [Full root]:
u should use the busybox for this fix to work...so dont miss the above procedure..
Download the http://www.2shared.com/file/e9sDTGJk/rootfixer.html? Tool By Anto Kus
Unzip it somewhere you remember
connect ur phone to pc
then run supersu.bat when prompted grant root access on phone
your xm will reboot,Once phone reboots wait for pc to detect phone again then finish supersu.bat then unplug device
!
Upto this strictly for M user...
the guide below can be used in any android device
Guide to use SD card for storing apps and Games
FOR storing apps:use LINK2SD:
Get the app from here:https://play.google.com/store/apps/details?id=com.buak.Link2SD
first guys XM/Mdual dont support ext4....please format ur sd 2nd partition to fat32...then u can link the apps....or else u will endup in bootloop...
use mini partition tools for windows...its easy to use...and easy to create a partition....
and connect your phone with MSC mode to PC for partitioning with the mini partition...which will in settings/xperia/usb connectivity/usb connection mode..
see here http://www.xperiablog.net/2011/12/12/link2sd-guide-never-worry-about-internal-memory-limits-again/
and follow the procedure in that site after 3rd step that is backup sd step in that site....[dont to use that method of rooting...its not for m,just use guide for Creation of partition] ...
and how to link all given on above site...so now we can link apps which is going to be stored on SD 2nd partiton
FOR storing Game data and how to play game:use GL2SD:
get the app from here:https://play.google.com/store/apps/details?id=com.slf.ListglApp
Guide:
first whatever game u need to play...use some website to download them ...bcoz u wont have space required in internal sdcard if u want to download from playstore...
so i assume u have downloaded the game apk + data from some website....and u have extracrted the zip or rar to somewhere in pc...
1.copy the apk to sdcard1...[Note:sdcard1 is ur external sdcard]
2.see the data folder...
mostly data folder has game name inside them mostly android/obb/game name/ or android/data/game name/ [game name will start as com.xxxxxx.yyy] structure will be followed and
some gameloft or reputed company will have their company name/games/game name/ [game name will start as com.xxxxxx.yyy] structure for games
3.now if it has .obb format file inside the above given structures...then copy game name folder and place them in sdcard1/obb/ [eg:sdcard1/obb/com.rockstar.gta3/xxyyyy.obb]
or if it has many folders and files inside the above structure....then copy the game name folder and place them in sdcard1/data/ [eg:sdcard1/data/com.rockstar.gta3/]
4.now install game.apk from sdcard1 and open gl2sd
5.click mount [the joined chain symbol at top] and click play the game...if u didnt see game on list ...just open setting go down and click recover list
6.if u download some medium size game like 250mb directly from playstore..then open gl2sd and click top right button and choose move data and wait till it moves data] after that ur game data is stored on sdcard1 ....now play with same step 5
7.if game didnt open or cant play or some error...restart ur phone...and repeat the 5th step...
8.if game work..cool but remember to unmount[unlinked chain on top] after u finished playing games..or u cant paste anything in sdcard1
[Note:To run game you must mount after every reboot and unmount if u r going to copy some files to sdcard1]
if u cant understand what i said about gl2sd
see this video..maybe it will help u.. http://www.youtube.com/watch?v=adLQgWyYIXQ
now u can mount any app or game to sdcard1...
credits to
dunc4n88
Anto Kus
Xzn
Hendrico Andre and Muhammad Arif
esrom02
and to link2sd,gl2sd app developers
Click to expand...
Click to collapse
in gl2sd
When I click mount the device reboot and after reboot not mounted
I think the device Can not read memory card
please help me
thanks for your efforts

mohamad khubayb said:
in gl2sd
When I click mount the device reboot and after reboot not mounted
I think the device Can not read memory card
please help me
thanks for your efforts
Click to expand...
Click to collapse
u must read xda rules properly...dont quote or reply OP post...edit ur post and delete the quotes
and u r using this thread to root?
if u r then...search for XM dual rooting guide...this is for XM single..

Will this work on C2004? firmware =15.2.A.2.5

danger ssteepr
Hi and thanks for the guide!
I've successfully (at least without errors) completed all steps you mention for a full root, but my xperia m still reboots when i try to delete system apps. Can you help me there?

krissel said:
Hi and thanks for the guide!
I've successfully (at least without errors) completed all steps you mention for a full root, but my xperia m still reboots when i try to delete system apps. Can you help me there?
Click to expand...
Click to collapse
r u sure u did install the given busybox?
bcoz my frnd using XM single gave this method...
and i seen some one told this way is to get full root.

ansebovi said:
r u sure u did install the given busybox?
bcoz my frnd using XM single gave this method...
and i seen some one told this way is to get full root.
Click to expand...
Click to collapse
Nevermind! i went through the whole process again, not it seems to work
thanks!

Hi, i have c1905 full root and was following the procedures for making a second partition. When i get the option for picking FAT32 in the link2sd app the phone reboots itself and stuck on a loop. Does anyone have any ideas to help please.

Persevere80 said:
Hi, i have c1905 full root and was following the procedures for making a second partition. When i get the option for picking FAT32 in the link2sd app the phone reboots itself and stuck on a loop. Does anyone have any ideas to help please.
Click to expand...
Click to collapse
Have you already have root access to your link2sd?
For 2nd partitions in sdcard format to ext3 and in link2sd select ext3 too.
Sorry for my English
Sent from my C1905 using XDA Premium 4 mobile app

I was told fat32 in this thread. But took the phone back, think its a joke. Got a moto g for roughly the same price with now problems atoll
Sent from my XT1032 using Tapatalk

Hi, I followed the instructions perfectly for my SingleSim Xperia M C1905 (firmware 15.1.C.2.8) but I can only get the half root. After doing the second part of the steps to fully root, when i try to RW using Root Explorer the phone reboots. So I am thinking the problem is somewhere in the last step when I do the Anto Kus Tool. Below is the result of using the Anto Kus Tool. The part below in bold looks like an error of some kind (rm failed for -f etc) and my phone is NOT being fully rooted (remains at only half root). Can someone please tell me what the below is saying? Some sort of error message right? Anyone have any ideas on what the problem could be? I have tried using the Anto Kus Tool like five times and always the same result as below.... and the phone remains at half-root. I don't know what to try next
==============================================
= =
= Anto Kus a.k.a Splakuk =
= FIX THE XPERIA M ROOT =
= =
==============================================
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Waiting for Device, connect USB cable now...
=============================================
Device found!
.
=============================================
Sending the fixer.
=============================================
362 KB/s (557 bytes in 0.001s)
951 KB/s (1461 bytes in 0.001s)
53 KB/s (82 bytes in 0.001s)
5056 KB/s (657704 bytes in 0.127s)
1377 KB/s (2116 bytes in 0.001s)
.
=============================================
Installing the rootfix.
=============================================
-rw-rw-rw- shell shell 657704 2013-06-24 12:59 busybox
at your device GRANT supersu access!
Press any key to continue after granting root access.
Press any key to continue . . .
killswitch the ric, remount /system rw and temporarily disabling the ric service
...
Found busybox, checking if it supports nohup...
rm failed for -f, No such file or directory
It does not, copying a replacement busybox to system.
rm failed for -rf, No such file or directory
Xperia M (C1904/5) found, installing install-recovery.sh instead...
=============================================
= YOUR DEVICE WILL NOW REBOOT! =
=============================================
Waiting for your device to reconnect.
Remounting system to see if it worked OK
Wait a few seconds to see if it worked, then
Press any key to continue . . .

And I just tried it again after playing around with BusyBox Free and this time I get a different Anto Kus wording result (in bold below) but again I still have only the half-root (when I click RW in Root Explorer my phone still reboots) :crying: Still not working!
What does it mean "installing install-recovery.sh instead" at the end of the Anto Kus Tool message? Does this mean the tool is installing something other that is should be instead? Is this why it's not working?
==============================================
= =
= Anto Kus a.k.a Splakuk =
= FIX THE XPERIA M ROOT =
= =
==============================================
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Waiting for Device, connect USB cable now...
=============================================
Device found!
.
=============================================
Sending the fixer.
=============================================
mkdir failed for /data/local/tmp/rootfix, File exists
155 KB/s (557 bytes in 0.003s)
407 KB/s (1461 bytes in 0.003s)
26 KB/s (82 bytes in 0.003s)
3276 KB/s (657704 bytes in 0.196s)
590 KB/s (2116 bytes in 0.003s)
.
=============================================
Installing the rootfix.
=============================================
-rw-rw-rw- shell shell 657704 2013-06-24 12:59 busybox
at your device GRANT supersu access!
Press any key to continue after granting root access.
Press any key to continue . . .
killswitch the ric, remount /system rw and temporarily disabling the ric service
...
Found busybox, checking if it supports nohup...
Success!
Xperia M (C1904/5) found, installing install-recovery.sh instead...
=============================================
= YOUR DEVICE WILL NOW REBOOT! =
=============================================
Waiting for your device to reconnect.
Remounting system to see if it worked OK
Wait a few seconds to see if it worked, then
Press any key to continue . . .
.
=============================================
Finish.. Enjoy
=============================================
.
Press any key to continue . . .

And now the third try today. I am not giving up haha! Thinking perhaps the problem is with the BusyBox Free version I went ahead and uninstalled BusyBox Free and installed the BusyBox Pro version. I did this because the instructions on the first page say to install BusyBox and "give Smart Install" and since Smart Install is not available with the free version I got the Pro version.
So when I clicked the BusyBox Pro icon in the apps tray for the first time it took a long time to load which I think is normal. Then I enabled Smart Install and clicked install. Now it is saying that BusyBox 1.22.1-Stericson is installed to /system/xbin as i think it should be. So I am doing everything right so far right?
So now I run the Anto Kus Root Fixer again (Windows7 64 bit) and again it doesn't work (RW doesn't work, phone reboots). Below is the wording from the latest Anto Kus Root Fixer attempt. What is wrong?
When I run a Root Checker app I got from the Play Store it says this (but like I said my phone reboots when I try to RW)
SU su found [/system/xbin]Version 1.93:Supersu
Root Access : access granted
UID=0 (root) GID=0 (root)
Unix Utils busybox /system/xbin/busybox Version IS
Path /system/xbin
/vendor/bin
/system/sbin
/sbin
/system/bin
==============================================
= =
= Anto Kus a.k.a Splakuk =
= FIX THE XPERIA M ROOT =
= =
==============================================
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Waiting for Device, connect USB cable now...
=============================================
Device found!
.
=============================================
Sending the fixer.
=============================================
mkdir failed for /data/local/tmp/rootfix, File exists
155 KB/s (557 bytes in 0.003s)
475 KB/s (1461 bytes in 0.003s)
26 KB/s (82 bytes in 0.003s)
3219 KB/s (657704 bytes in 0.199s)
1033 KB/s (2116 bytes in 0.002s)
.
=============================================
Installing the rootfix.
=============================================
-rw-rw-rw- shell shell 657704 2013-06-24 12:59 busybox
at your device GRANT supersu access!
Press any key to continue after granting root access.
Press any key to continue . . .
killswitch the ric, remount /system rw and temporarily disabling the ric service
...
Found busybox, checking if it supports nohup...
Success!
Xperia M (C1904/5) found, installing install-recovery.sh instead...
=============================================
= YOUR DEVICE WILL NOW REBOOT! =
=============================================
Waiting for your device to reconnect.
Remounting system to see if it worked OK
Wait a few seconds to see if it worked, then
Press any key to continue . . .
.
=============================================
Finish.. Enjoy
=============================================
.
Press any key to continue . . .

So now it's the next day. I am determined to get full root. But again FAIL.
I started out the day by removing SD Card and doing a FACTORY RESET of my Xperia M. Then first thing I did was do the rooting instructions. But again full root FAIL. I am only able to get the half-root just like before. I am telling you that the Anto Kus Tool does not work or a VERY IMPORTANT KEY PART of the instructions is missing!
Well hopefully when the new KitKAt update for XperiaM comes out next month then a new rooting method will need be devised in order to root these damn Xperia M's. Because right now the current full-root method just does not work. And I have tried and tried and tried again again again

Well, here we are again trying to full-root my Xperia M.
This time I took my girlfriends Xperia M and followed the steps, hers has same firmware as mine. And it all worked perfect. No problems at all to get the full root. One thing I noticed different is that when I used the the Anto Kus Tool on my girlfriend's phone it only rebooted once during the whole procedure while with mine it rebooted twice (the second time right at the point where the Anto Kus tool says "Wait a few seconds to see if it worked ok then..." then my phone reboots a second time while with hers it didn't. I am assuming that that check is to see if the RW works. And of course mine always reboots as I have been explaining for the past week as I am not achieving the full root.
So there is something wrong with my phone. I need to totally erase it and start all over to reinstall the Sony Android OS etc. But I don't know how to do that so I will open a new thread and ask how...
So the moral of this story is that yes, the instructions work fine however not with every phone. With mine it doesn't, then I followed the same procedure that I had used on mine with her Xperia M and it did work fine, first time.

andyxoxo said:
Well, here we are again trying to full-root my Xperia M.
This time I took my girlfriends Xperia M and followed the steps, hers has same firmware as mine. And it all worked perfect. No problems at all to get the full root. One thing I noticed different is that when I used the the Anto Kus Tool on my girlfriend's phone it only rebooted once during the whole procedure while with mine it rebooted twice (the second time right at the point where the Anto Kus tool says "Wait a few seconds to see if it worked ok then..." then my phone reboots a second time while with hers it didn't. I am assuming that that check is to see if the RW works. And of course mine always reboots as I have been explaining for the past week as I am not achieving the full root.
So there is something wrong with my phone. I need to totally erase it and start all over to reinstall the Sony Android OS etc. But I don't know how to do that so I will open a new thread and ask how...
So the moral of this story is that yes, the instructions work fine however not with every phone. With mine it doesn't, then I followed the same procedure that I had used on mine with her Xperia M and it did work fine, first time.
Click to expand...
Click to collapse
Well, it worked fine first time for me. Anyway, if you want to reflash stock firmware then use Sony's PCC. Go to Update and then repair (assuming you have a locked bootloader, if you don't then download an FTF and flash it)
This message was brought to you from my Sony Xperia M C1905 using Tapatalk.

Antrikos48 said:
Well, it worked fine first time for me. Anyway, if you want to reflash stock firmware then use Sony's PCC. Go to Update and then repair (assuming you have a locked bootloader, if you don't then download an FTF and flash it)
This message was brought to you from my Sony Xperia M C1905 using Tapatalk.
Click to expand...
Click to collapse
Yes thank you, after so many tries I finally got full root. I had to do the repair with Sony PC Companion exactly how you said. Now full-root. I could tell it was working right away during the Anto Kus rootfixer because it rebooted only once during the procedure. And then RW was good to go/ Oh happy days

could not update system apps after using link2sd
Thanks for this post ...
m a noob at all this but hv been visiting xda forums since I purchased my xperia M 2 months back.
I have successfully rooted my phone, installed link2sd after lots of trials and now m facing an error while updating any system app.
It says : insufficient storage available
Is thr any solution to that, so that I can update my apps like Google Maps etc.

22sumit said:
Thanks for this post @OP
m a noob at all this but hv been visiting xda forums since I purchased my xperia M 2 months back.
I have successfully rooted my phone, installed link2sd after lots of trials and now m facing an error while updating any system app.
It says : insufficient storage available
Is thr any solution to that, so that I can update my apps like Google Maps etc.
Click to expand...
Click to collapse
Ah yes, I got that too. But I was tinkering with Link2SD setting so I can't be sure.
I fixed it by going into Link2SD Plus (running Plus if it makes difference) and selected settings -> Install Location -> Automatic
I did have the option 'External' set, cause I thought that made more scene, but maybe some apps need the option of Internal or External.
Have a look and see if this applies to your problem.

thanks
Dr Goodvibes said:
Ah yes, I got that too. But I was tinkering with Link2SD setting so I can't be sure.
I fixed it by going into Link2SD Plus (running Plus if it makes difference) and selected settings -> Install Location -> Automatic
I did have the option 'External' set, cause I thought that made more scene, but maybe some apps need the option of Internal or External.
Have a look and see if this applies to your problem.
Click to expand...
Click to collapse
Thanks a lot Dr goodvibes.
That was really helpful... Changed the Install Location to Automatic from External.
BOOM , problem solved :good:

[Q] Saferoot to disable Knox problem

Hey! So I'm trying to root my device. I already ran an old rooting method using Odin, but when I tried to use it afterwards Knox was tripped. This led to finding Saferoot.
I've tried it a few times, only for it to get stuck at trying to disable Knox.
Code:
--- Samsung Galaxy S4 Android 4.3 Root ---
--- Based on the CVE-2013-6282 exploit by cubeundcube ---
[*] Testing adb usability
Plug in your phone and Press any key to continue . . .
[*] Waiting for your phone to appear
[*] Your phone is detected and ready for rooting.
[*] Sending files to your device...
[*] Starting rooting program.
ro.build.product=t03g
ro.build.id=JSS15J
search kallsyms...
1
(kallsyms_addresses=c082efb0)
(kallsyms_num_syms=0000ef10)
kernel dump...
1 2 3 4 5 6 7 8 9
prepare_kernel_cred=c00c04c4
commit_creds=c00bfcb0
ptmx_fops=c0bda36c
ptmx_open=c02bb450
tty_init_dev=c02b3ff0
tty_release=c02b3a4c
tty_fasync=c02b117c
ptm_driver=00000000
Succeeded in getroot!
Remount success!
Copying files..
Done.. reboot to enable root!
[COLOR="Red"](I don't actually need to reboot here, it just goes on to the next step)[/COLOR]
[*] Checking if rooting succeeded
[*] Removing temporary files...
[*] Trying to disable Knox...
Usually the program just hangs here indefinitely, but one time it rebooted my phone and tried to run SuperSU, only for it to be blocked by Knox. My phone seems to be rooted according to Simple Root Checker - it says Application Superuser found, Terminal Rooted, Busybox installed, and Busybox v1.21.1 - so I guess that the old method of rooting did work, but Knox remains.
Any ideas?
[edit] The additional text which shows after a reboot. Obviously I was unable to actually start SuperSU to update it.
Code:
[*] Checking if rooting succeeded
[*] Removing temporary files...
[*] Trying to disable Knox...
[*] Rebooting... Please wait.
[*] Waiting for device to re-appear...
Wait until your phone reboots,then unlock it and Press any key to continue . . .
On your phone, open SuperSU and let it update if it asks.
When SuperSU is done updating, Press any key to continue . . .
On your phone, watch for the SuperSU permission popup and give
permission for ADB Shell to gain root permissions.
I have to quit it manually thereafter.
Just to note, Knox is tripped every time saferoot tries to disable it.

Tuppence_ said:
Hey! So I'm trying to root my device. I already ran an old rooting method using Odin, but when I tried to use it afterwards Knox was tripped. This led to finding Saferoot.
I've tried it a few times, only for it to get stuck at trying to disable Knox.
Code:
--- Samsung Galaxy S4 Android 4.3 Root ---
--- Based on the CVE-2013-6282 exploit by cubeundcube ---
[*] Testing adb usability
Plug in your phone and Press any key to continue . . .
[*] Waiting for your phone to appear
[*] Your phone is detected and ready for rooting.
[*] Sending files to your device...
[*] Starting rooting program.
ro.build.product=t03g
ro.build.id=JSS15J
search kallsyms...
1
(kallsyms_addresses=c082efb0)
(kallsyms_num_syms=0000ef10)
kernel dump...
1 2 3 4 5 6 7 8 9
prepare_kernel_cred=c00c04c4
commit_creds=c00bfcb0
ptmx_fops=c0bda36c
ptmx_open=c02bb450
tty_init_dev=c02b3ff0
tty_release=c02b3a4c
tty_fasync=c02b117c
ptm_driver=00000000
Succeeded in getroot!
Remount success!
Copying files..
Done.. reboot to enable root!
[COLOR="Red"](I don't actually need to reboot here, it just goes on to the next step)[/COLOR]
[*] Checking if rooting succeeded
[*] Removing temporary files...
[*] Trying to disable Knox...
Usually the program just hangs here indefinitely, but one time it rebooted my phone and tried to run SuperSU, only for it to be blocked by Knox. My phone seems to be rooted according to Simple Root Checker - it says Application Superuser found, Terminal Rooted, Busybox installed, and Busybox v1.21.1 - so I guess that the old method of rooting did work, but Knox remains.
Any ideas?
[edit] The additional text which shows after a reboot. Obviously I was unable to actually start SuperSU to update it.
Code:
[*] Checking if rooting succeeded
[*] Removing temporary files...
[*] Trying to disable Knox...
[*] Rebooting... Please wait.
[*] Waiting for device to re-appear...
Wait until your phone reboots,then unlock it and Press any key to continue . . .
On your phone, open SuperSU and let it update if it asks.
When SuperSU is done updating, Press any key to continue . . .
On your phone, watch for the SuperSU permission popup and give
permission for ADB Shell to gain root permissions.
I have to quit it manually thereafter.
Just to note, Knox is tripped every time saferoot tries to disable it.
Click to expand...
Click to collapse
First try to update SuperSu manually it'd probably works.
Have you installed Knox full application which is around 150 Mbs? Then uninstall tha app and repeat the procedure.

If SuperSU is not working. Go to Application manager and try to uninstall. If u can not then re-flash 4.3 from Computer Odin to get rid of Corrpt SpuerSU.
Downgrade from 4.3 to 4.1.2. I have done this with 100% Success
BACKUP everything. (Important)
Turn ON USB Debugging mode and Unknown sources.
First ROOT your phone.
Open Playstore and Update SuperSU. Open SuperSU and it will give a message to disable KNOX. Click YES/Ok.
Then install Titanium backup root from Playstore. Open it, go to backup/restore tab.
Find,
1.com.sec.enterprise.knox.attestation
2.com.sec.knox.eventsmanager
3.KLMS Agent
4.KNOX
5.Knox Notification Manager
6.KNOX Store
Go to each one of it and Uninstall them.
Next restart your phone.
*VERY IMPORTANT* Now Backup your efs folder by using EFS Professional on you computer (Link: http://d-h.st/Gfo ). Because your imei number will be changed after downgrading. You can easily restore it later.
Now install Mobile Odin Pro from Playstore on your phone. Here is the link.
https://play.google.com/store/apps/details?id=eu.chainfire.mobileodin.pro
*IMPORTANT* DO NOT flash firmware for downgrading with Computer Odin as it will NOT work and it will FAIL. *ONLY Mobile Odin Pro from Playstore will work.
Copy your 4.1.2 firmware to your phone. Next Open Mobile Odin Pro on your phone and let it download some necessary files from internet.
When done, click on Open file and select the firmware. After loading the firmware scroll down and UNCHECK EverRoot(because it cause problems). Then click on FLASH Firmware.
*IMPORTANT* If your phone get stuck on samsung logo. Go into recovery mode by pressing Home+Power+Volume UP keys together for 15 seconds. Click Factory wipe/data and then Wipe Cache. Then Reboot.
Now check your imei by *#06#. If imei is changed then restore it from EFS Professional.

Baller231 said:
Downgrade from 4.3 to 4.1.2. I have done this with 100% Success
Click to expand...
Click to collapse
That would be awesome, but I am not sure if it will work for everybody. What phone/carrier did you use?
I am afraid to try it out, because I heard some attempt will results in a hard brick that can only be fixed using Jtag.
Thanks!