Lets just go straight to the point :
Make sure that you've :
- Downloaded and extracted 'DooMLoRD's Easy Rooting Toolkit [v4.0](zergRush Exploit)' (ref : http://forum.xda-developers.com/showthread.php?t=1321582)
- Installed Android SDK to enable you to run ADB shell
- Enabled 'Unknown Sources' in your phone
- Enabled 'USB Debugging' in your phone
Step 1 :
- Open command line as Administrator and go to 'android-sdk/platform-tools' folder
- Run this command :
adb devices (after this command you should see your device id)
adb shell
echo 1 > /data/local/lge_adb.conf
- Leave the cmd windows open
Step 2 :
- Go to DooMLorD folder
- run 'runme.bat'
- press 'Enter' once and then once more
VOILA!!
p/s : You can close the 'cmd' windows now
Superoneclick method is better which dosent need android sdk installed
its just another way. no biggie
I rooted my O1 with Superoneclick and I recommend it , fast and safe
Sorry, where can i found superoneclick?
i have O1 with last ginger update, it's compatible?
kyrulamri said:
Lets just go straight to the point :
Make sure that you've :
- Downloaded and extracted 'DooMLoRD's Easy Rooting Toolkit [v4.0](zergRush Exploit)' (ref : http://forum.xda-developers.com/showthread.php?t=1321582)
- Installed Android SDK to enable you to run ADB shell
- Enabled 'Unknown Sources' in your phone
- Enabled 'USB Debugging' in your phone
Step 1 :
- Open command line as Administrator and go to 'android-sdk/platform-tools' folder
- Run this command :
adb devices (after this command you should see your device id)
adb shell
echo 1 > /data/local/lge_adb.conf
- Leave the cmd windows open
Step 2 :
- Go to DooMLorD folder
- run 'runme.bat'
- press 'Enter' once and then once more
VOILA!!
p/s : You can close the 'cmd' windows now
Click to expand...
Click to collapse
Superoneclick has zergRush exploit in it and more.
Anyone wanting to root their phone or flash baseband go into my guide, link is in my signature
Related
hy
how root the lg optimus pro ?
need a guide thanks
1 º Download this suite of applications that I use (I added the zip original drivers from LG, which, with no specific model for this, worked like a charm):
www.megaupload.com/?d=U3L199Z3
2 Reset the phone manufactures (who have data to backup, use the File maneger Astro, for example), to obtain a clean file system Settings \ Privacy \ Reset factory data;
3 Extract the zip to a folder on your desktop and install the USB drivers, which are in the zip, the folder "USB driver";
4 Connect the phone to pc cable and expect drivers to be installed;
5 º Go to the pc start \ programs \ accessories \ command line;
6 After you open the command line type:
cd \
cd Users
cd (user name in question)
cd Desktop
cd (name of which are powered uncompressed zip files)
cd ADB
and the result is something like: C: \ Users \ (user name) \ Desktop \ Root Maximo LG Pro \ ADB
then enter the following commands:
adb devices (pressenter)
adb shell (press enter, and then the letter of the command line will pass to $)
echo 1> / data / local / lge_adb.conf (press enter)
7 After these commands inserted, turn off and then turn on the phone (very important this step), always with the phone connected by USB;
8 After restarting the phone, go to the folder where the files are downloaded and run the SuperOneClick.exe;
9 Select the method GingerBreak and click "ROOT"
10 When the process finishes (VERY IMPORTANT) make sure you turn off and turn it on again and update the application through the superuser Market.
That's it. Phone with root access.
Credits go to: Bruno Pinto @ AndroidPT
Hi,
I've tried as you say, and i jammed on the driver installation. Why? On the pack you've posted, there's only a shortcut to the driver file: LGUnitedMobileDriver_S4981MAN32AP22_ML_WHQL_Ver_3.2 - Atalho
and when clicking it its giving me a link to something that doesn't exist:
C:\Users\"username"\Desktop\LGUnitedMobileDriver_S4981MAN32AP22_ML_WHQL_Ver_3.2.exe
Even so, i'd already had installed the LG software suite and so i've got the driver so i moved to the next steps.
when going to perform the adb shell command (error: device not found), i tried with mass storage mode on and off and msg is always the same.
can you please help me?
thanks for any answer
That guide is so complicated for n00b like me who has never before used Android. The stock rom is awfull anyway, any hope for costum roms on this one?
Hi!!
After running the adb command line and restart the mobile, i've started the super one click, it started rooting and in the end in step 7 he says "Remounting /system with read-write access .... FAILED", what went wrong?
I have the latest drivers for this smart and the latest super one click v.2.1.1
My LG has the 2.3.4 version of android and it's from TMN
Regards
is it possible to unlock it? (for free preferably)
hugoafsilva said:
Hi,
I've tried as you say, and i jammed on the driver installation. Why? On the pack you've posted, there's only a shortcut to the driver file: LGUnitedMobileDriver_S4981MAN32AP22_ML_WHQL_Ver_3.2 - Atalho
and when clicking it its giving me a link to something that doesn't exist:
C:\Users\"username"\Desktop\LGUnitedMobileDriver_S4981MAN32AP22_ML_WHQL_Ver_3.2.exe
Even so, i'd already had installed the LG software suite and so i've got the driver so i moved to the next steps.
when going to perform the adb shell command (error: device not found), i tried with mass storage mode on and off and msg is always the same.
can you please help me?
thanks for any answer
Click to expand...
Click to collapse
the drivers are here: http://www.mediafire.com/?85wvjkp5ytb816y
This is NOT complicated method and it works great. I have also tried this on Optimus Net and works fine
Help..! Help..!
I have an LG-C660 Android Gingerbread 2.3.4
1 - Does anyone has an Android version fot this device..?
2 - After Root the device, it boots but dont´s shows the Desktop. It´s stucks on Carrier Screen
3 - Please Help me..!
I tried as instructions but the adb driver can't be successfully installed. I've tried installing drivers many times but it doesn't work.
Done! I removed the SD card and it worked finally!
i have a lg C660 from TMN with v2.3.4 i've tried and tried and cant make it work. anyone got it to work?
Edit :: with superoneclick v2.1.1 i get this
SuperOneClick v2.1.1.0
Checking drivers...
Killing ADB Server...
* server not running *
OK 0,10s
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK 4,14s
Waiting for device...
OK 0,08s
2.3.4
Getting manufacturer...
LGE
OK 0,02s
Getting model...
LG-C660
OK 0,03s
Getting version...
V10c-Aug-25-2011.2ED2FC6537
OK 0,03s
Checking if rooted...
False
OK 0,06s
Installing BusyBox (temporary)... - Step #1
2039 KB/s (1062992 bytes in 0.509s)
OK 0,59s
Installing BusyBox (temporary)... - Step #2
OK 0,03s
Rooting device... - Step #1
OK 0,02s
Rooting device... - Step #2
OK 0,03s
Rooting device... - Step #3
782 KB/s (16830 bytes in 0.021s)
OK 0,10s
Rooting device... - Step #4
OK 0,04s
Rooting device... - Step #5
OK 0,02s
Rooting device... - Step #6
[**] Gingerbreak/Honeybomb -- android 2.[2,3], 3.0 softbreak
[**] (C) 2010-2011 The Android Exploid Crew. All rights reserved.
[**] Kudos to jenzi, the #brownpants-party, the Open Source folks,
[**] Zynamics for ARM skills and Onkel Budi
[**] donate to [email protected] if you like
[**] Exploit may take a while!
[+] Plain Gingerbread mode!
[+] Found PT_DYNAMIC of size 232 (29 entries)
[+] Found GOT: 0x00014354
[+] Using device /devices/platform/msm_sdcc.1/mmc_host
[*] vold: 0000 GOT start: 0x00014354 GOT end: 0x00014394
OK 80,24s
Rooting device... - Step #7
OK 8,08s
Remounting /system with read-write access...
mount: Operation not permitted
FAILED ::
When you get the #6 step you have to disable and enable debug usb on the device..in this way it should work
Sent from my LG-C660 using Tapatalk
Sir i have tried the above procedure. But after "loading gingerbreak" nothing happens. i have waited for half hour.Please tell me what went wrong?
some body know how to get in recovery mode ´cuz i can root my c660 i have gingerbread 2.3.4
i have rooted my gf's phone and made a custom ROM for her i made it for her only !
Step 5 and Step 7 problem
EDIT:
Finally Done. I used SuperOneClick v2.2 and removed the SD card (only in settings) and on step five just disable and enable usb debugging. I feel like alchymist.
And now i am looking how i can custom default rom.
simmer14 said:
i have rooted my gf's phone and made a custom ROM for her i made it for her only !
Click to expand...
Click to collapse
sir kindly make one for us too.. we are sick of Stock ROM...
unabl to root every =time it gets strucked on step 7... somebody help me
Installed at last after 3 days hardwork :/ :/
my phone was not rooted and i wanted the new gb official build so i installed it and now i want t go back to froyo how do you do this on a mac
Even though its a Mac cant you run things in a Dos like mode with c:\ prompt?
Even though its a Mac cant you run things in a Dos like mode with c:\ prompt?
Google came up with this
I looked FOREVER for these instructions. While I didn't write them, they definitely worked for me:
- Download the Android SDK for Macintosh at: Android SDK | Android Developers
- Extract it
- Download Fastboot for OSX (If not included with SDK)
- Extract fastboot and place it in your /tools folder.
- Open up a terminal window
- type: pico .bash_profile (this will create a .bash_profile)
- type the following in the new screen: export PATH=$
{PATH}:<sdkfolder>/tools
- Hit CNTRL + X
- Hit Y (for yes to save)
- It will return you to the terminal screen… type: exit
- Restart terminal.
- Then you can use your adb commands like you would on a PC. To test this, plug your device in (make sure its in debugging mode), then type "adb devices" in the new terminal window. It should show up with a number. This means you are good to go.
blueis300 said:
Even though its a Mac cant you run things in a Dos like mode with c:\ prompt?
Click to expand...
Click to collapse
A better statement is he can run things like you would on linux, because osx has a bash terminal built in. Type "terminal" into finder. Sadly, most osx people have no clue that exists, which is sad because it's not a hackjob like cmd.exe.
ok i got all the way to the last step and the terminal window keeps saying: -bash: adb: command not found and -bash: sdkfolder: No such file or directory
blueis300 said:
Even though its a Mac cant you run things in a Dos like mode with c:\ prompt?
Google came up with this
I looked FOREVER for these instructions. While I didn't write them, they definitely worked for me:
- Download the Android SDK for Macintosh at: Android SDK | Android Developers
- Extract it
- Download Fastboot for OSX (If not included with SDK)
- Extract fastboot and place it in your /tools folder.
- Open up a terminal window
- type: pico .bash_profile (this will create a .bash_profile)
- type the following in the new screen: export PATH=$
{PATH}:<sdkfolder>/tools
- Hit CNTRL + X
- Hit Y (for yes to save)
- It will return you to the terminal screen… type: exit
- Restart terminal.
- Then you can use your adb commands like you would on a PC. To test this, plug your device in (make sure its in debugging mode), then type "adb devices" in the new terminal window. It should show up with a number. This means you are good to go.
Click to expand...
Click to collapse
ok i got all the way to the last step and the terminal window keeps saying: -bash: adb: command not found and -bash: sdkfolder: No such file or directory
Has anybody got a Sony Tablet S being recognised by adb?
It seems to be blocked :-(
And yes, I have done all the usual enable USB debugging etc...
I can not use it for development :-(
---------- Post added at 12:56 PM ---------- Previous post was at 12:06 PM ----------
Managed to sort it myself
you need to cd to your .android folder (on a mac, this is ~/.android) and then type
echo 0x054c > adb_usb.ini
Where 0x054c is the vendor id for Sony (I got that by looking at the attached evices in the 'About this mac' preferences)
Now adb sees the device - woohoo
would this apply if i just wanted to use it to transfer music and such? I am not incredibly savy with coding but i tried to enable debugging and all that. I am justnot sure whats the problem.
No, the Android File Transfer program still works without this
Good to know it can be used to dev on. Anyone have any information on how to send data out using the IR blaster, I dont think there is support for it in the native android libraries from what I can see?
The following procedure has confirmed that ubuntu 11.04.
The following procedure has confirmed that ubuntu 11.04.
1. Enable debug mode for sony tablet S
2. Add line /etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="054c", MODE="0666", GROUP="plugdev"
3. Change file mode
sudo chmod a+r /etc/udev/rules.d/51-android.rules
4. Add line idVendor to ~/.android/adb_usb.ini
0x054C
5. adb kill-server ; sudo adb start-server
6. finish!
Kaz Taguchi said:
The following procedure has confirmed that ubuntu 11.04.
1. Enable debug mode for sony tablet S
2. Add line /etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="054c", MODE="0666", GROUP="plugdev"
3. Change file mode
sudo chmod a+r /etc/udev/rules.d/51-android.rules
4. Add line idVendor to ~/.android/adb_usb.ini
0x054C
5. adb kill-server ; sudo adb start-server
6. finish!
Click to expand...
Click to collapse
I don't seem to have that file
I had done all the other steps in order to mount the tablet and copy files over (which works great).
Does anyone have issues with Sony's Music player failing to update the database? Music appears in the native Music app correctly but nothing in the Sony one
Found a way on Windows!
With the help of the vendor ID from above and the following article on generic Tegra Tablets, was able to get it to show up on Windows!
(Copied from addictivetips)
1.You must have Android SDK installed before you can proceed. If you don’t have it already, proceed to our guide on what is ADB and how to install it. Make sure you download the Google USB Driver Package as well.
2.Open the google-usb_driver folder that you will find inside your Android SDK folder.
3.Open the android_winusb.inf file in notepad or any text editor to edit it.
4.Add these lines under [Google.NTx86] or [Google.NTamd64] depending on whether you are using 32 bit or 64 bit Windows. If unsure, it is safe to add these under both these sections. ;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
Don’t edit or replace any other text that is already there; just add these new lines and save the file.
5.Open a command prompt window and enter this command: echo 0x054C >> "%USERPROFILE%\.android\adb_usb.ini"
Note: this is where you have to use 0x054C instead of what is at the link, otherwise it wont work
Now your Android SDK drivers are configured to support any Nvidia Tegra based tablet. To be able to use ADB and other SDK tools with your device, you can proceed as follows:
1.On your tablet, go to Menu > Settings > Applications > Development and enable ‘USB Debugging’.
2.Connect your tablet to your PC via USB. You will get a notification that some drivers were not installed, which is OK for now.
3.Right-click ‘Computer’ and click ‘Manage’. Identify your device from the list, right-click it and click ‘Update Driver Software..’.
4.Choose to browse your computer for driver software and then select to pick from a list device drivers on your computer.
5.Choose to view all devices and click ‘Have Disk…’.
6.Browse to the google-usb_driver folder inside your Android SDK folder and select the android_winusb.inf file.
7.If you get any warnings prompts telling you that the driver might not be compatible, just choose to continue installing.
8.Once the drivers have been installed, you should be able to use ADB with your device.
9.To confirm that your device is recognized, launch a Command Prompt window and enter these commands: adb kill-server
adb start-server
adb devices
Also, using BRKs Transformer's instructions found a way to boot Tablet S into recovery: has reboot, update from ZIP and factory reset options
a) Hold down power and volume UP button
b) when SONY logo appears, release power button but keep pressing volume UP button
c) should load into recovery
This also gives us the MTP device driver, which I have been unable in finding/installing
No luck so far with Automated rooting tools, working hard to crack this awesome tablet!
Bojanglez said:
I don't seem to have that file
I had done all the other steps in order to mount the tablet and copy files over (which works great).
Does anyone have issues with Sony's Music player failing to update the database? Music appears in the native Music app correctly but nothing in the Sony one
Click to expand...
Click to collapse
Thanks Kaz Taguchi !!
Couldn't connect to my Sony..
It made me crazy..!
I was just forgotten the:
4. Add line idVendor to ~/.android/adb_usb.ini
0x054C
So i created the file:
touch ~/.android/adb_usb.ini
and echoed the line into the file.
Works lime a charm now.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
CaptainJack87 said:
With the help of the vendor ID from above and the following article on generic Tegra Tablets, was able to get it to show up on Windows!
(Copied from addictivetips)
1.You must have Android SDK installed before you can proceed. If you don’t have it already, proceed to our guide on what is ADB and how to install it. Make sure you download the Google USB Driver Package as well.
2.Open the google-usb_driver folder that you will find inside your Android SDK folder.
3.Open the android_winusb.inf file in notepad or any text editor to edit it.
4.Add these lines under [Google.NTx86] or [Google.NTamd64] depending on whether you are using 32 bit or 64 bit Windows. If unsure, it is safe to add these under both these sections. ;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
Don’t edit or replace any other text that is already there; just add these new lines and save the file.
5.Open a command prompt window and enter this command: echo 0x054C >> "%USERPROFILE%\.android\adb_usb.ini"
Note: this is where you have to use 0x054C instead of what is at the link, otherwise it wont work
Now your Android SDK drivers are configured to support any Nvidia Tegra based tablet. To be able to use ADB and other SDK tools with your device, you can proceed as follows:
1.On your tablet, go to Menu > Settings > Applications > Development and enable ‘USB Debugging’.
2.Connect your tablet to your PC via USB. You will get a notification that some drivers were not installed, which is OK for now.
3.Right-click ‘Computer’ and click ‘Manage’. Identify your device from the list, right-click it and click ‘Update Driver Software..’.
4.Choose to browse your computer for driver software and then select to pick from a list device drivers on your computer.
5.Choose to view all devices and click ‘Have Disk…’.
6.Browse to the google-usb_driver folder inside your Android SDK folder and select the android_winusb.inf file.
7.If you get any warnings prompts telling you that the driver might not be compatible, just choose to continue installing.
8.Once the drivers have been installed, you should be able to use ADB with your device.
9.To confirm that your device is recognized, launch a Command Prompt window and enter these commands: adb kill-server
adb start-server
adb devices
Also, using BRKs Transformer's instructions found a way to boot Tablet S into recovery: has reboot, update from ZIP and factory reset options
a) Hold down power and volume UP button
b) when SONY logo appears, release power button but keep pressing volume UP button
c) should load into recovery
This also gives us the MTP device driver, which I have been unable in finding/installing
No luck so far with Automated rooting tools, working hard to crack this awesome tablet!
Click to expand...
Click to collapse
Done loading packages.
Preparing to install archives
Downloading Google USB Driver package, revision 4
File not found: C:\Program Files (x86)\Android\android-sdk\temp\usb_driver_r04-windows.zip (Access is denied)
Done. Nothing was installed.
I tried downloading and installing
(Can't post links)Download: Android USB Drivers - Original (Firmware 1.0)
But when I try to install the drivers for the tablet through device manager it says:
The folder you specified doesn't contain compatible software... ...Windows for x64-based systems.
Apparently this driver is only for x86. But after googling "download Google USB Driver Package" that's all I can find.
Got it...
At least I was able to "enable it" through the USB port,
thanks to this exercise in frustration.
Alas no root screen cap still didn't work.
It flashes wildly and does nothing.
Anyone happen to know the proper command line in system variables for win 7 for adb should be?
I haven't used adb in forever, and I think alot of peoples issues with adb is in the fact they cannot use it outside of the android/android-sdk/platform-tools directory. As in you can just type adb shell, adb start-server, adb kill-server from the root dir. I had it set up before, but with a new comp now, and I forgot what it was before.
whats going wrong
i cant seem to get the device driver on my adb at all. no matter what i do i cant get the usb driver sorted. this is where i get stuck"
Please add 0x54c into .android/adb_usb.ini file under HOME directory by using following command from command prompt.
echo 0x54c >> %HOMEPATH%\.android\adb_usb.ini
home directory???? every time i try this from home directory i get nothing.
this is my problem.... i dont have this file or entry. what is the entry?????? o notpad doc??,
adb_usb.ini file was missing the 0x54c entry! <<< what is this. a screen shot goes a loooong way.
Adb was simple with my x10 and sgs2 but man this is giving me the ****s.
can someone please post a few simple screenshots of what directory is supposed to be where please?
---------- Post added at 08:39 AM ---------- Previous post was at 08:21 AM ----------
what does this mean?
Thanks Kaz Taguchi !!
Couldn't connect to my Sony..
It made me crazy..!
I was just forgotten the:
4. Add line idVendor to ~/.android/adb_usb.ini
0x054C
So i created the file:
touch ~/.android/adb_usb.ini
and echoed the line into the file
?????????
I've created an automated ADB driver installer for the Sony tablets.
No more messy, time-consuming SDK install.
http://forum.xda-developers.com/showthread.php?t=1488822
Official Sony instructions
Looks like Sony has posted official instructions for setting up ADB with the Tablet S:
esupport.sony.com/US/perl/support-info.pl?info_id=878
After following their instructions I still had to go to Device Manager, choose to Update the driver for my tablet, and point it to the SDK/usb_driver folder. After that it works great.
debug
Hey guys i have installed the android sdk and the sony s drivers from the official site as dreadengineer posted. but after run the adb devices command i was unable to saw my device.
After that i tried the automated installations that BluechipJ posted, but the result was the same i cannot see the devices neither on eclipse or adb devices command.
i want to debug my application on this device but i could not access it. Can someone help me.
I have a windows 7 x64 OS. i'm able to debug on htc phone and also on the super slower emulator
Hello
This will be my first tutorial on rooting a galaxy player 5.0 using Ubuntu 12. please let me know if there are some changes you believe needs to be made. i will also update this document with photos and add a second part for flashing a custom ROM. i have it as an attachment as well as copied into this post.
Root and Flash Galaxy Player 5.0 (linux)
Hello after some searching I deiced to learn how to root and flash my Galaxy Player 5.0 loaded with GingerBread (2.6.35-Kernal, 2.3.5-firmware).
**First we need to prep your player**
1) go to settings
2) now to applications
3) now open development
4) finally check the USB debugging box
**Install needed Apps**
5) download and install terminal emulator
**Install android SDK**
6) open terminal and use the command (adb) we are looking for “Android debug bridge”
1) if you get android bridge move to step 3 if you do not get android bridge move to step 2
7) adb= Android SDK
1) open terminal and use type sudo apt-get install eclipse-jdt allow the install to complete
2) now lets install the android sdk using this link android-sdk
3) use the software defaults allow it to complete the install process
4) open the eclips application
1) go to help → install new software click add end enter this URL //dl-ssl.google.com/android/eclipse/
2) check the available boxes and choose next followed by finish (restart eclips)
3) now click window → preferences choose browse locate your android SDK folder
4) Apply → OK
5) now choose window → SDK manager
1) select all the packages you will be working with (I choose 4.0.3 and above)
**Lets Root your Player**
8) plug your micro USB into player and Linux box
9) download the following files rootme files //papousek.org/downloads/galaxy_player/rootme.tar.gz
10) extract the file to your home dir
11) open terminal and use the following command
1) cd root/
2) chmod +x rootme.sh
3) ./rootme.sh
12) this will take a few mintutes let the program run **you will know the process is done when your player reboots**
**Lets check if your player is Rooted**
13) open the terminal emultaor you installed on your player
14) in the command line enter the following command
1) su
2) enter
15) you should get a “Allow super user box” choose allow
16) in the terminal emulator type
1) you should see a $ symbol
2) type su
3) you should now see a # symbol this means you are root.
I rooted mine using Oneclick Root. Version 2.2.2.It took less than 5 minutes. My player has the 2.3.5 stock firmware.
[Help!] Update System with Terminal Emulator with Error "no space left on device"
I follow the following instruction to update my Meizu Pro5 with success for several times, but i got an error message "no space left on device" this time. Is there any way to solve this?
1. Enable root
Enable root by tapping on Settings-> Accounts-> My Flyme-> Personal settings (first option) -> System privileges and set it to open - accept disclaimer and confirm.
2. Download and successfully install Busybox (from Google Play or see .apk below)
3. Download and install a Terminal Emulator (from Google Play or see apk below)
4. Download the correct and desired international (i) ROM/firmware (update.zip) for your device
5. Download and use the update.zip (firmware) converter that creates the required system-i.img
Click here to download converter first
Copy system.new.dat and system.transfer.list (from the update.zip) to the folder “in” (see converter folder)
Then start the converting process by starting System-conVERTER.cmd and pressing option 1 [enter]
If successfully converted you can find the system-i.img in the ‘‘out’’ folder.
6. Copy the converted system-img from ‘‘out’’ to the internal memory of your Meizu device
7. Go to Settings-> Display-> Sleep and set it to at least 10 minutes
8. Start the Terminal Emulator and run (type) the super user command
su
A permission popup will come; give permission by tapping allow (always allow).
9. Now run (type) the command for installing the system-img.
dd if=/sdcard/system.img of=/dev/block/platform/XXXXXXX/by-name/system
Replace XXXXXXX with the correct partition system for your device
MX4 Pro = 15540000.dwmmc0
M2 note = mtk-msdc.0
MX4 = mtk-msdc.0 (OR mmcblk0p6)
MX5 = mtk-msdc.0 (OR mmcblk0p18)
Pro 5 = 15570000.ufs
Example for MX5 : dd if=/sdcard/system.img of=/dev/block/platform/mtk-msdc.0/by-name/system
Note: Pro5 might require: dd if=/storage/emulated/0/system.img instead of /sdcard/
10. The installation should start after the ‘‘dd if’’ command, but please note…
…it may seem that the copying/process did NOT start because you didn’t notice it, but it DID start.
do NOT type a new command or whatsoever, just…
…be patient and give your device 5-10 minutes to process.
11. When the process is done you’ll see a # at the very end
Your device should be unresponsive by now - this is normal
12. Now just shutdown your phone (hold power button) and reboot it
13. Once successfully booted your device should be running an I-rom
Once in Flyme again it is wise - but not necessary - to completely reset your phone. Go to settings->about phone->memory->factory data reset-> check both boxes and click start cleaning (this could take 5-10minutes). Always backup your stuff if necessary.