yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] MrCabana:
UPDATE:

I finally succeeded in mounting /system as read-write :D

It turned out that my /system partition was damaged, that is why my phone was reverting it to read-only no matter what I tried. In the end, there was no scripts or anything pulling it back.

How I found that? By reading this post, there's a comment from [MENTION=2341536]bftb0[/MENTION] suggesting it, so I went to dig that out. I simply typed "e2fsck -fv /dev/block/mmcblk0p3" and it tried to correct some errors and failed. That was the reason why I wasn't succeeding in mounting rw.

THE SOLUTION:

Since there was no way of fixing the damaged partition, but still I could access its files, I ran "adb pull /system mysystemfolder\" to grab all the files from there. The reason was that I had to run an update to format system partition and then have all the files back. I didn't want to risk losing all that I have installed.

Anyway, I also found this stock ROM specific for my phone in some italian website. That helped me extract the 4 files adb failed to pull (two were symlinks and other two I don't know why). I basicly copied his updater-script to the sample.zip I found on this post (thanks to [MENTION=4451099]pankaj88[/MENTION]) and removed all the changes reffering to /data (I didn't wanna touch anything there). Then I copied all my backed up /system files into the sample.zip and renamed it to update.zip.

I went into CWM and ran this update.zip and after completion, phone boots up and ... bang !!!!

"mount -o rw,remount /system" .... WORKS !!!!

THE CREDITS:

Thank you [MENTION=3868181]x1123[/MENTION] and [MENTION=3924647]bigrammy[/MENTION] for sticking with me and thanks [MENTION=2341536]bftb0[/MENTION] and [MENTION=4451099]pankaj88[/MENTION] for posting their thoughts.

I couldn't have made it without your help.

THE PS:

For anyone interested in my modified "updater-script", here is the link to it.

THE VERY IMPORTANT WARNING:

The script above should be used only as a SAMPLE for you to build your own script.

DON'T USE MINE ON YOUR DEVICE. It's 200% UNTESTED and worked for MY PHONE in this SPECIFIC situation.
[Android Software/Hacking General [Developers Only]] bigrammy:
Nice work MrCabana well done and welcome to the world that's android :good: :laugh:

I hope you will continue to hang out here once in awhile as we really could do with someone experienced with scripts :eek:

Were the damaged files installed by the factory or was it something you or the rooting software did :confused:

Maybe it would be possible when you get some time for you to make a backup with MTKDroid tools and share your rooted ROM so others can flash it if they are having problems rooting the phone :fingers-crossed:
[Android Software/Hacking General [Developers Only]] MrCabana:
I have no idea. I've tried soooo many scripts I can't really tell what caused the damage. One thing is for sure: I have NO backup of my original/stock ROM (I was lame enough not to do it BEFORE trying anything).

One thing I can remember is that quite a few times the phone froze when I was running some script and I had to remove the battery in order to get it back. Maybe that's what caused the ext4 corruption.

Anyway, I tried quite a few times to use the e2fsck program, as mentioned in my previous post, but it wouldn't fix the partition. I believe there could be ways to accomplish that (ie. from CWM or even some trick to unmount /system somehow). But I've decided to go the clean way and didn't even search for other methods to try.

My rooted ROM is exactly like the one from the Italian site. I tried to be safe and not to use his files for the /system partition, but I compared file by file it's identical. All the changes I made was about the location and that can be done easily from the settings menu.

It's unbelievable how something so simple turned out to be sooooo complicated. Looking back at all that I've tried, I strongly believe that ALL methods really worked. It was just that corruption thing preventing files to stick to /system folder. It was frustrating to search google over and over again only to find out NOBODY seemed to be having the same kind of problem. It was obvious it was something related to my specific device.

And yes, I will keep coming here for news. I've learned quite a lot about android devices and I will surely keep digging. I recently bought an Android TV device that came with Jelly Bean 4.2.3 and as soon as I have sometime I will try to root that baby as well. But that will be another chapter ....

So again, thank you all.
[Android Software/Hacking General [Developers Only]] bigrammy:
[Windows]Android Ultimate Toolbox Pro

Hi all,

I am just spreading the word on this Awesome Windows based Utility Here it's by a true Master dev [MENTION=3424769]despotovski01[/MENTION] :cool:

There are some really really useful tools such as the file explore which makes it a breeze to pull edit and push back files to your phone in seconds there are also APK tools and Update.zip tool etc etc just have look you will not be dissapointed its very very professional indeed.

Note: Any of the tools that says FLASH are not normally for our phone's MTK65xx but are for phones with fastboot such as (HTC)

Regards bigrammy. :cool:

[MENTION=4478781]yuweng[/MENTION] :good:
[Android Software/Hacking General [Developers Only]] bigrammy:
Need help for OUR Mediatek SoC

Hi,

I am trying to get better support for the Mediatek SoC on xda so could you all please help me to help you and show your support Here :o

I am asking that the Mediatek SoC be granted its own section under "Device" instead of us being posted all over the forum. :mad:

Maybe they will listen if we get enough response :fingers-crossed:

Please spread the word Thanks
[Android Software/Hacking General [Developers Only]] smoners:
ERROR

Hello,

my MTK6575 appears this error when I do the procedure indicated.

Could help me
[Android Software/Hacking General [Developers Only]] ron.gt:
Hello master [MENTION=4478781]yuweng[/MENTION] and [MENTION=3924647]bigrammy[/MENTION] ... i am having a device named iball andi 3.5... it's chip is mt6575.. it comes with GB... i am trying rooting it by flashing CWMR... problem is i cant read my stock rom back .. i tried almost all versions of SPFT... now versions above 3.1xxx gives a common error S_BROM_CMD_STARTCMD_FAIL (2005). I checked my VCOM drivers... it detects my device ok... (even i dont have problem with my other MT6577 device iBall Andi 4.5h while using SPFT)...

But i just can't get pass this way... now version below 3 (v2.1134 or v2.1140) can't read.. it stucked on 'searching' status after hitting download button...

I have read master [MENTION=5119815]rua1[/MENTION] 's guide on this.... he mentioned about finding test points (TP) if S_BROM_CMD_STARTCMD_FAIL (2005) error shows... because i dont have OTG cable.... now finding TP is also very hard in this device...(i thought it would not be that hard).... just can't understand what to do... stucked with this phone for 2 weeks.... i attached my phone's pics here please check and if u can help me finding TPs....

A small help would be great masters... i don't see any blog or forum discussing about rooting or development of this phone....
[Android Software/Hacking General [Developers Only]] bigrammy:
Hi [MENTION=5257901]ron.gt[/MENTION]

Please download and use only these 2 versions SP Flashtool :good:

This version is only for flashing or push the .img file's too your phone and NOT for doing a readback from your device (getting .img files from your phone) Here

This version is only for getting the .img files from your phone (Readback) Here do not mix them up :laugh:

Just follow [MENTION=4478781]yuweng[/MENTION] tut under is signature for the correct way to do the readback.

I suppose you have tried MTKDroidtools already Here :confused:
[Android Software/Hacking General [Developers Only]] ron.gt:
hi [MENTION=3924647]bigrammy[/MENTION] ... i get the same error with that readback operation with SPFT v3.1224.0.sn85 ... u provided... screenshot is provided ... my mtd partitions screenshot is also attached....

mtkdroid tool shows the block mapping are also given in screenshots... i also tried to flash some cwm recovery.img of some phone called Qmobile Noir 2... which has similar mtd structure using SPFT v2.1134.0... but it shows something like "changed partition size" ...

i dont know what to do... please help me sir...:(
[Android Software/Hacking General [Developers Only]] bigrammy:
Hi [MENTION=5257901]ron.gt[/MENTION]

Please allow me some time I am going to make a TUT on this subject because I have been asked this same questions so many times :eek:

I will dig out my old phone and go through the whole procedure step by step with screenshots I should have done this long ago but I am very lazy :laugh:

Please allow a little time for me to make the tut .

If you can not wait follow this Here you may have to try different key combos at step 9 but I think you are already there as your phone is connected and seen by spft :good:

PS: Step 2 is cat /proc/mtd which you have already done anyway. :)
[Android Software/Hacking General [Developers Only]] ron.gt:
yes i followed that tutorial too... nothing happend... now eagerly waiting for your tut... thank you master [MENTION=3924647]bigrammy[/MENTION] ...:D
[Android Software/Hacking General [Developers Only]] bigrammy:
You probably have "MTD" partitions not "EMMC"

MTD = Gingerbread v2.3.x

EMMC = Ice Cream Sandwich or above
[Android Software/Hacking General [Developers Only]] bigrammy:
I just had a little flash of inspiration & perspiration (its hot today) while writing the TUT :laugh: Can you please tell me what kernel version your phone shows settings/about phone/kernel version :confused:

Regards bigrammy.
[Android Software/Hacking General [Developers Only]] ron.gt:
The system info..

Hardware : MT6575 (MT6515 is Fake!)

Model : iBall Andi3.5

Build number : iBall.ALPS.GB2.MP.V2.4

Build date UTC : 20130312-072121

Android v : 2.3.6

Baseband v: iBall.MAUI.11AMD.W11.50.SP.V16, 2012/06/13 17:58

Kernel v : 2.6.35.7 (linux-server-build2@xuyongfeng-desktop) (gcc version 4.4.3 (GCC) ) #1 Tue Mar 12 15:19:45 CST 2013
[Android Software/Hacking General [Developers Only]] bigrammy:
Ok thanks for that but it was not what i though :(

I have figured out what is going wrong though :D

Ok here we go :eek:

I have attached some images below for you to see.

You are missing the MTK brom driver (bootrom) for your phone :( THIS IS NOT THE PRELOADER VCOM DRIVER

This is what it looks like in device manager.

Here are the driver details.

Ok so how do we install this driver :confused:

On my phone I have a HOME button a real button not a softkey so you will have to experiment if you do not have the same button as me:(

Yours could be Volume up or Volume down a camera button any physical key.

So with my phone this was the procedure.

Close all running PC applications and turn up your volume to max.

Now the PHONE.

1: Battery in (It may need to be out on yours)

2: Phone Totally OFF (Pull battery and replace to be sure)

3: USB in the PC ready but NOT connected to the phone.

4: Press and keep hold of the Home Button ( Remember it may be a different button on your device)

5: Insert the USB cable into the Phone while still holding the Home button.

6: You will hear the "bad umm" sound of the PC detecting the phone

7: You will then hopefully see the message device driver installation. (click the box to see it's progress)

8: Keep holding the Home Button until the driver installs (see first picture)

Thats it you can now let go and unplug the phone then follow the TUT of [MENTION=4478781]yuweng[/MENTION].

When you reach the part where you hit readback just use the same key combo and same usb port as you did when installing the driver. :fingers-crossed:
[Android Software/Hacking General [Developers Only]] ron.gt:
Hi [MENTION=3924647]bigrammy[/MENTION] ... I have tried your method...

I have only 3 physical buttons...vol+, vol-, power on button... tried all combinations...

while pressing vol+ and power menu ... once i got this (in attached screenshot)... and that thing doesn't disappear like preloader VCOM ... so i could take screenshot... but unfortunately this combination also activate factory test ... with options like full test, item test, test report, clear flash, reboot.... so when that Mediatek VCOM USB activated in PC... i got that factory test menu on phone screen... all other combinations of keys doesn't show up anything like that.... i stayed on that screen for a while... and turned off my phone usually as u said... and started SPFT and all the procedure for readback....

but now whenever i press that combination of keys together once again... just preloader VCOM is shown for few seconds and disappear...

Can't even see that Mediatek VCOM USB again... so same readback error....

so what to do master??
[Android Software/Hacking General [Developers Only]] bigrammy:
That seems like the correct one to me :confused:

When you got the factory (test menu:confused: not seen that before) did the mediatek vcom usb stay connected? Normally that combo just boots you into the recovery maybe your phone has to be in recovery for the readback to work :confused:

I am just guessing here which will not help you :(

So you need to try reproduce the same thing once you have locked on and have a steady driver showing in the device manager run the readback from SP Flashtool. v3

Please try the same key volume + or combo of keys with the battery removed maybe it picked it up before the recovery began to load. :fingers-crossed:

PS: Also some phones need you to push volume + & volume - together at the same time again try all with battery IN and OUT until you find the combo that works with your phone. It's definitely there it's just a matter finding it :)
[Android Software/Hacking General [Developers Only]] ron.gt:
Hi [MENTION=3924647]bigrammy[/MENTION] ... i tried that same combination many times... also various and every possible other combinations for past 3 hrs....

Just nothing is happening... can't get back that Mediatek META MODE (Mediatek USB VCOM)...:confused:

tried so hard.. that my fingers paining...:crying:....

so strange that META MODE appeared for only once, stayed for sometime and now gone... in USBDview... i can see that driver is installed "usbser.sys"... but feeling like lost... :mad:

anyways...

My key combinations are::

vol down + power menu ==Stock Recovery mode

vol up + power menu == Factory mode

EDIT: ok now MediaTek VCOM USB is fine.... but just cant start readback process... see the Screen Shot....

What is hapenning exactly is....

1. i insert the battery to the phone while turned off

2. i start read back procedure in SPFT... it shows searching

3. i press and hold vol+ and power button and plug the microUSB cable to phone and connected to PC

4. the factory mode appears on phone screen

5. then device manager page reloads and MEDIATEK USB VCOM appears in PORT and stays permanently there in device manager

6. i keep holding the key combination to start SPFT readback

7. SPFT still shows searching and nothing happens and stuck on 0%

UPDATE:

Hi [MENTION=3924647]bigrammy[/MENTION] ... i came to know from master [MENTION=5119815]rua1[/MENTION] 's post from russian page... mediatek usb vcom is also something like preloader.... in device manager it initially detects as "CDC data" then installs the needed driver which is some version like v2.xx ....

Now i understood it is not the MTK USB port ... as u shown in ur post.... So i am not actually in META MODE....

I tried ur tut once again carefully....

Now i found one more thing ... vol- and power key combination take me to stock recovery (3e)... while in recovery if i press and hold vol- and vol+ key combination... some unknown device appears in device manager with yellow exclamation.... (see the 2nd screen shot).... check the unknown driver version with urs post.... same .... :D...

i dont know what is this...

Now i tried uninstalling all mediatek drivers and re-installing.... still yellow exclamation remains....

What am i doing wrong??....:P
[Android Software/Hacking General [Developers Only]] bigrammy:
Hi sorry for the late reply I have been to my daughters graduation :D

I think we are nearly there now use These Here to install the MTK drivers fully ignor that it says 6577 thats just my refferance it will work and the one you need is also included. It is called the 3 step method.

After extracting the files just open the folder named First Step and run the .exe as Administrator repeat the steps for the other two folders in there correct order :good:

Then reboot the PC and retry your combo :fingers-crossed:
[Android Software/Hacking General [Developers Only]] x1123:
Sorry it is really OOT, are the above PHONES IDENTICAL (?) .. I owned OneScribe za985 and made little observations for finding identical device to check possibility of ROM EXCHANGE
[Android Software/Hacking General [Developers Only]] ron.gt:
dude.. this thread is not for off topic... u asked an irrelevent question in this thread... i can only tell u join this FB group... http://www.facebook.com/groups/357361847702937/ ...

u will hv ur answer...

---------- Post added at 01:43 PM ---------- Previous post was at 01:35 PM ----------

Hi [MENTION=3924647]bigrammy[/MENTION] ... thnks for ur helping hand... but unfortunately i am nowhere.... even after the 3 steps driver installation ... i couldn't activate the META-MODE.... that 'unknown device' i mentioned about .. is detected and it is just 'Andi 3.5 USB Device' under disk drive in device manager... So i am just unable to activate that 'Mtk USB port' .... all key combinations are performed.... what are the modes i could activate ...are..

1. preloader VCOM mode

2. Mediatek USB VCOM Mode

3. Android Gadget VCOM Mode

4. USB Diskdrive Mode

but none of these helping me with SPFT readback....

is it possible that i dont have that META-MODE in my device?? or if it there.. any other way to activate it??? or can u help me with some similar cwm recovery which i can flash through SPFT ?? (i tried 5/6 custom recoveries to flash but everytime i get changed partition size error eboot 16008 SPFT message)

suggest something sir....:confused::confused::confused:
[Android Software/Hacking General [Developers Only]] bigrammy:
Hi [MENTION=5257901]ron.gt[/MENTION] I am running out of ideas now :(

It is really difficult to try resolve these kind of problems without actually having the device in hand :eek:

After some googling around I noticed one method for the andi 4.5 seemed to use the Volume+ and Volume- together I also notice that iball have there own driver http://www.iball.co.in/Downloads just enter your phone specifics. The Andi 3.5i has a tethering driver and a usb2ser_2kXP.inf driver maybe this different to the stock MTK one's :confused:

Maybe give this a go and see if you can get the meta-mode back. Also use google for rooting procedures of there other devices because they may use the same procedure for yours too :fingers-crossed:
[Android Software/Hacking General [Developers Only]] yuweng:
Yeoh man, you gotta read this whole thread then only you'll know, credits to Rastishka... :cool: Your device may be in this category... :o
[Android Software/Hacking General [Developers Only]] ron.gt:
Ok... master [MENTION=4478781]yuweng[/MENTION] ... i am back at the same place....:p

my first post was to finding test point of this device i am having.... here .... now i have already seen the post of @rashtishka ... so i tried for this.... my phone is different than him... so there is no points or dots at the back... or may be due to my ignorance i could not find it... can u check my post once master.... so that if u can see the TPs using ur huge h/w experience....:fingers-crossed:

any help is greatly appreciated master.... (openning the back of the phone making my volume rocker little less responsive... i may get that button bricked sometime.....:silly:)

[MENTION=3924647]bigrammy[/MENTION]... i also have andi 4.5h device of iball... it never gave me trouble... not with drivers, not with spft, not with meta-mode... nothing... so i purchased andi 3.5 with the similar thought.. "if andi 4.5h is a good guy.... then andi 3.5 should also be... but never thought it will be a bad guy"...:laugh::laugh:

i know for sure .. this mt6575 phone is rebranded of some chinese phone... but my bad... i can't find that clone too... so i am in the middle of a sea....:D
[Android Software/Hacking General [Developers Only]] yuweng:
If its not at the back then its in the front... :cool:

Found a quite detail guide by androidmedia on how to look & identify testpoint on MTK devices... :good:
[Android Software/Hacking General [Developers Only]] bigrammy:
Hi [MENTION=4478781]yuweng[/MENTION] and [MENTION=5257901]ron.gt[/MENTION].

I was wondering if anyone has ever used a USB jig Like this here before:confused:

I have used one on the samsung i9000 which puts the phone into flash mode:good:

Maybe iBall have adopted this method because I did notice that in ron.gt photos there is a "VBUS" which I think can identify what kind of USB device has connected I belive the jig just places a ground on one of the USB pins and this puts the phone into Download mode.

Just a thought :confused:
[Android Software/Hacking General [Developers Only]] yuweng:
Hehe, i completely forgot about this testpoint at the USB cable since you mention it... :o

So far that i'm aware, only two MTK device has worked with this technique, a step by step by Nikhilmendu
[Android Software/Hacking General [Developers Only]] mogamycool:
Hi yuweng,

I got a mt6575 mobile ,and tried the method you mentioned, but sp tool said that the file is too big , can I use twrp recovery of alcatel 997d with mt6575 mobile?
[Android Software/Hacking General [Developers Only]] yuweng:
For your case, your recovery partition is only 5Mb thats why ported CWM/ TWRP is oversized... :cowboy:

There is a 7Mb mod for this type of case but its not for n00b you might brick it... :o

if you still wanna try it then post your scatter.txt at this thread... :cowboy:
[Android Software/Hacking General [Developers Only]] mogamycool:
I posted my scatter.txt at the thread you mentioned ,still waiting .
[Android Software/Hacking General [Developers Only]] indtram:
No Recovery !!!

Wrong Section...Apologies
[Android Software/Hacking General [Developers Only]] nudou350:
Can i follow this just to have CWM on my RAZR d1? I mean, follow the tutorial and stop when i get cwm on it, and keep using my stock ROM that is already rooted?? All i want is the CWM!
[Android Software/Hacking General [Developers Only]] t-bon3:
Edit: Please remove, apologies from MTK n00b!
[Android Software/Hacking General [Developers Only]] hubacikj:
HELP

i have a problem with my phone..

Hardware : MT6577

Model : e1901_v77_jbla668_fwvga

Build number :e1901_v77_jbla668_fwvga_20130116

Build date UTC : 20121220-072424

Android v : 4.1.1

Baseband v: MAUI.11AMD.W12.22.SP.V15P2, 2012/12/20 14:10

Kernel v : 3.4.0 (root@abc-desktop))#1SMP PREEMPT Wed Jan 16 18:43:47

I tried all the methods of root what I just found, but no success, you do not know how to do it?
[Android Software/Hacking General [Developers Only]] ron.gt:
You have to flash cwm recovery using spft ...try rua1 method... then auto root using super user flasher...