Database Users

[GUIDE] How to Overclock your Motorola Charm

Hey Guys,
The Admins decided to basically add the Charm forums into the Flipout forums, so far only the main forum heading has been changed, hopefully the admins will do the rest of the changes soon.
In the meanwhile, i thought it would be useful to post useful threads on the charm porting, basically since flipout and charm are the same phone with a different design, these should be applicable with respective changes to flipout also.
[GUIDE] How to Overclock your Motorola Charm
Author : dabiano
Thread : http://forum.xda-developers.com/showthread.php?t=1274027
Content :
dabiano said:
Hello and Good Day to All!,
note: I can no longer maintain this as I have already sold my Charm Unit ..., attached below is the source code used on this development
This is a guide on how to overclock your Motorola Charm. [tested on T-Mobile Motorola Charm MB502]
Disclaimer: I am not responsible of bricking/frying your phone!, use this at your own risk
It is confirmed that some users of the Charm Overclock have bricked theirs using this app
Prerequisites:
● Phone should be rooted
● You have a copy of a "proper/valid" sbf file of your Motorola Charm unit in case anything goes wrong.
Ask people in the link provided for directions on how to obtain your proper sbf file: http://modmymobile.com/forums/633-motorola-charm-general/557900-charm-firmwares-superthread.html
Method #1
Install my Charm Overclock App and use it like that of the Milestone Overclock App
[note: apk found just below this very post]
Method #2 (by ryukoz)
1. open /system/build.prop in text editor
2. find ro.product.model=MB502, change MB502 to MB511
3. use milestone overclock
Method #3
Things needed (some maybe optional):
● Your Motorola Charm phone
● PC
● USB Data Cable for your Phone/PC
● MicroSD Card Reader
Prerequisites:
● All pertaining drivers should be installed in your PC (i.e. Moto USB Drivers..., etc.)
The Steps:
1. From your PC, Download 'Milestone Overclock' apk from: http://code.google.com/p/milestone-overclock/downloads/list (I've used version 148)
2. Extract this Milestone Overclock apk to a clean folder and locate the file 'overclock_flipout_21.ko' in: ..res\raw\ directory
3. Copy the module overclock_flipout_21.ko into the root of your SDCard
4. Install the Milestone Overclock App to your phone (either thru Market or with the one you downloaded)
5. Install also SetCPU
6. From a terminal emulator on your phone or thru adb, run these commands (should be root user)
7. # su
8. # cd /sdcard
9. # grep omap2_clk_init_cpufreq_table /proc/kallsyms
● you should see an output like: c004e498 T omap2_clk_init_cpufreq_table
● take note of the red colored eight digit hex number
10. and then we load the Overclocking Module with the code below (replace the RED number with your actual address you found on your device):
11. # insmod overclock_flipout_21.ko omap2_clk_init_cpufreq_table_addr=0xc004e498
12. run dmesg and see if you have something similar below:
● [ 9361.096099] overclock: found mpu_opps_addr at 0xc050c888
13. Open the Milestone Overclock app (the module should be loaded by default as we already loaded it manually)
14. Slide the slider to the far right and press the 'menu' button and choose 'settings'
15. In the 'Custom rate (KHz)', put in the value you like, say: '1000000' (this is 1GHz)
16. In the 'Custom vsel', put in the value you like say: '60'
17. Leave the other settings and press 'Ok'
18. Lastly, Press the 'Apply' button ^_^
Don't forget to set 'SetCPU' as well
I would like to thank "Milestone Overclock" and "SetCPU" ^_^
also..., to the XDA Personnels: Please Open a Motorola Charm Sub Forum ^_^
Click to expand...
Click to collapse
Credits to the respective author and aforementioned credits.

Frequency and Vsel Table
Frequency and Vsel Table
dabiano said:
Currently tested and somewhat stable:
● device=mb502, frequency=1GHz, vsel=60 (stable), user=dabiano
● device=mb502, frequency=1GHz, vsel=58 (stable), user=therkr
● device=mb502, frequency=1.1GHz, vsel=63 (stable? [still testing]), user=elliot.newnham
● device=mb502, frequency=720MHz, vsel=46 (stable? [still testing]), user=ryukoz
Default Frequency Table!? (via cat /proc/overclock/mpu_opps)
● 720MHz @ 62vsel
● 550MHz @ 56vsel
● 500MHz @ 50vsel
● 250MHz @ 39vsel
● 125MHz @ 32vsel
My Customized Frequency Table!
● 1GHz @ 60vsel
● 800MHz @ 50vsel
● 600MHz @ 40vsel
● 400MHz @ 30vsel
● 200MHz @ 20vsel
other values are welcome! ^_^, we need other combinations
Click to expand...
Click to collapse

General Q and A
Charm Overclock App Q and A
Q. Why does the "Autoload on boot" won't work?
A. Now it works by modifying /system/bin/mot_boot_mode (I don't know other alternatives to make it set during boot/startup)
Q. Your Application sucks.
Q. Can we include this "fill-in-the-blanks" feature?
A. I'm welcome to such improvements [if I have the time][/QUOTE]

Please inform me if there are any corrections to be made

bricked my phone
Hi i was using motorola charm rooted from 6 months with links2sd,
since my phone became slow I followed the instructions of OC,
but never backd up my stock
i OC'd to 1000Hz 60 vsels (dono wat vsel means)
now my phone is not booting past M logo
i tried hard reset methods which did not work ,
IS THERE A POSSIBILITY OF RECOVERY ??
HELP ME PLS I M A NOOB

flash with sbf
hold power and x or power and up on your dpad to boot into bootloader mode,
then flash with sbf, you will lose everything on your device but your device will boot up afterwards
sunilkumar1 said:
Hi i was using motorola charm rooted from 6 months with links2sd,
since my phone became slow I followed the instructions of OC,
but never backd up my stock
i OC'd to 1000Hz 60 vsels (dono wat vsel means)
now my phone is not booting past M logo
i tried hard reset methods which did not work ,
IS THERE A POSSIBILITY OF RECOVERY ??
HELP ME PLS I M A NOOB
Click to expand...
Click to collapse

Please Open Motorola Charm Sub Forum

RSD LITE is not detecting phone
plageran said:
hold power and x or power and up on your dpad to boot into bootloader mode,
then flash with sbf, you will lose everything on your device but your device will boot up afterwards
Click to expand...
Click to collapse
bob,
firstly thanx for ur reply
I followed your steps, but RSD lite is not able to detect
previously i used rsd lite 5... version
now tried with version 4.6 still did not work
suggest me any other software to unbrick my phone:victory:

did you install your motorola drivers?
when you plug your device in, does your machine detect your device and are you sure you see the bootloader screen?
exactly what did you try and how far did you get?
Edit:
I found a link with everything you should need, and your device is only soft-bricked.
As long as your phone switches on you should be able to flash it, its when it doesn't respond that you will have a problem.
Link:
http://forum.xda-developers.com/showpost.php?p=14227486&postcount=1
sunilkumar1 said:
bob,
firstly thanx for ur reply
I followed your steps, but RSD lite is not able to detect
previously i used rsd lite 5... version
now tried with version 4.6 still did not work
suggest me any other software to unbrick my phone:victory:
Click to expand...
Click to collapse

Finally unbricked phone
plageran said:
did you install your motorola drivers?
when you plug your device in, does your machine detect your device and are you sure you see the bootloader screen?
exactly what did you try and how far did you get?
Edit:
I found a link with everything you should need, and your device is only soft-bricked.
As long as your phone switches on you should be able to flash it, its when it doesn't respond that you will have a problem.
Link:
http://forum.xda-developers.com/showpost.php?p=14227486&postcount=1
Click to expand...
Click to collapse
At last I could figure out difference b/w recovery window and boot loader
I was assuming recovery window as bootloader
at last figured out difference and unbricked my phone
thanx alot for ur support,
regards,
Sunil Kumar

sunilkumar1 said:
At last I could figure out difference b/w recovery window and boot loader
I was assuming recovery window as bootloader
at last figured out difference and unbricked my phone
thanx alot for ur support,
regards,
Sunil Kumar
Click to expand...
Click to collapse
Hi Sunil,
What exactly did you do to flash a the sbf file.
I would be of great help as i have bricked mine.

Fixing 0 IMEI

Hello. I've been getting a lot of emails on how to do that and i thought i should make a thread here.
Now you got to have the original box in which there is the imei written. I don't take any credit for this guide as i didn't write it but i found it somewhere here but it doesn't exist anymore. I'm not responsible for any damage may happen to your phone. I did it several times after flashing official 2.3.5.
It has worked fine with my IDEOS X5 U8800.
1. Tools
a. Drivers for U800 32bit win 7 (tested and work )
http://www.2shared.com/file/fnP5fc8G/u8800Drivers.html
b. Drivers for Android 32 and 64 bit win 7 (not tested )
http://www.2shared.com/file/ZNZ4Q0lk...012_09_12.html
c. Software for restore
http://www.2shared.com/file/xBxUOnPz/DFS.html
2. Enable debugging by USB in the settings.
In call type * # * # 2846579 # * # * http://postimage.org/image/tnj4s2dyj/
3. Go to ProjectMenu -> Background settings -> Usb port settings put the Manufacture mode and corfim.
4. Go again to ProjectMenu -> Background settings -> Qualcomm backround open settings put the background open. Password 0 and corfim.
5. Go again to ProjectMenu -> Background settings -> Log setting -> Log switch put log on and corfim.
6. Now conect your phone to pc and install the drivers.
You must see this at your device manager http://postimage.org/image/5lrm61agd/
7. Instal DFS and run.
8. Click Ports, select the port with the signature DBAdapter Reserved Interface (double click) to close.
http://postimage.org/image/3l3bmfyzr/
9. In the DM select Qualcomm.
http://postimage.org/image/6bmt1908z/
10) Press the SPC, the bottom will Device Unlocked.
11) Select Programming and in the IMEI write yours and press Write.
http://postimage.org/image/dmbp29q35/
13) Check Imei, may appear after a reboot, if not try a few more times to try to set the port speed to 115200 (box to the left of DM)
Check IMEI *#06#
As soon as the IMEI restored change:
* # * # 2846579 # * # * -> ProjectMenu -> Background settings -> Usb port settings to put on the Manufacture mode google mode (or normal if you do not get up google)
* # * # 2846579 # * # * -> ProjectMenu - > Background settings -> Qualcomm backround open settings put close
Good luck..

Thanks a lot... now I got my imei back. But now I have one another problem, I installed ics rom and now my wifi Mac id is 00:00:00:00:00:00. Are they related?
Sent from my U8800 using XDA Premium 4 mobile app

I don't think so. But I've already replied somewhere on how to fix mac address. Search
Sent from my U8800 using xda app-developers app

Didn't work for me
Cybergiannis said:
Hello. I've been getting a lot of emails on how to do that and i thought i should make a thread here.
Now you got to have the original box in which there is the imei written. I don't take any credit for this guide as i didn't write it but i found it somewhere here but it doesn't exist anymore. I'm not responsible for any damage may happen to your phone. I did it several times after flashing official 2.3.5.
It has worked fine with my IDEOS X5 U8800.
1. Tools
a. Drivers for U800 32bit win 7 (tested and work )
http://www.2shared.com/file/fnP5fc8G/u8800Drivers.html
b. Drivers for Android 32 and 64 bit win 7 (not tested )
http://www.2shared.com/file/ZNZ4Q0lk...012_09_12.html
c. Software for restore
http://www.2shared.com/file/xBxUOnPz/DFS.html
2. Enable debugging by USB in the settings.
In call type * # * # 2846579 # * # * http://postimage.org/image/tnj4s2dyj/
3. Go to ProjectMenu -> Background settings -> Usb port settings put the Manufacture mode and corfim.
4. Go again to ProjectMenu -> Background settings -> Qualcomm backround open settings put the background open. Password 0 and corfim.
5. Go again to ProjectMenu -> Background settings -> Log setting -> Log switch put log on and corfim.
6. Now conect your phone to pc and install the drivers.
You must see this at your device manager http://postimage.org/image/5lrm61agd/
7. Instal DFS and run.
8. Click Ports, select the port with the signature DBAdapter Reserved Interface (double click) to close.
http://postimage.org/image/3l3bmfyzr/
9. In the DM select Qualcomm.
http://postimage.org/image/6bmt1908z/
10) Press the SPC, the bottom will Device Unlocked.
11) Select Programming and in the IMEI write yours and press Write.
http://postimage.org/image/dmbp29q35/
13) Check Imei, may appear after a reboot, if not try a few more times to try to set the port speed to 115200 (box to the left of DM)
Check IMEI *#06#
As soon as the IMEI restored change:
* # * # 2846579 # * # * -> ProjectMenu -> Background settings -> Usb port settings to put on the Manufacture mode google mode (or normal if you do not get up google)
* # * # 2846579 # * # * -> ProjectMenu - > Background settings -> Qualcomm backround open settings put close
Good luck..
Click to expand...
Click to collapse
This procedure did not work for me. I found it a couple of weeks ago in another thread (http://forum.xda-developers.com/showthread.php?t=1591997) and gave it a try (numerous times) without success. I was able to complete all steps up until actually writing the new IMEI. I attempted to write it a couple of dozen times without any success. It appears to work but the lMEI never actually changes.
I also found another procedure using a program called NVedit but it would give me an error stating the NV location was set to read only (I forget the actually wording). It seems that my phone has the location that contains my IMEI locked in some way that nothing can change it. So I gave up on that phone and am using a different one that I bought on eBay, brand new at a dirt cheap price ($27.00).

pastorbob62 said:
This procedure did not work for me. I found it a couple of weeks ago in another thread (http://forum.xda-developers.com/showthread.php?t=1591997) and gave it a try (numerous times) without success. I was able to complete all steps up until actually writing the new IMEI. I attempted to write it a couple of dozen times without any success. It appears to work but the lMEI never actually changes.
I also found another procedure using a program called NVedit but it would give me an error stating the NV location was set to read only (I forget the actually wording). It seems that my phone has the location that contains my IMEI locked in some way that nothing can change it. So I gave up on that phone and am using a different one that I bought on eBay, brand new at a dirt cheap price ($27.00).
Click to expand...
Click to collapse
are you rooted? i remember having these issues when i flashed 2.3 after 4.2 rom. u first need ti flash 2.2 then 2.3 and that should work

Cybergiannis said:
are you rooted? i remember having these issues when i flashed 2.3 after 4.2 rom. u first need ti flash 2.2 then 2.3 and that should work
Click to expand...
Click to collapse
Yes, I am rooted.
I started out on 2.2 way back in the beginning. Then I flashed 2.3.5. That's when I lost my IMEI and replaced the phone.
But I wanted to keep experimenting at getting it working 100% even though I had a new working, rooted, and customized phone. Using 5IromToolBox I restored a backup from the new phone to the broken phone just to see if it would work. Then I flashed Stallion-51-ICS custom ROM. It is a GB based ROM with look and feel of ICS.
When I run the procedure in this thread, everything looks as though it has worked, but the IMEI never changes. So what did 5Irom do differently that it was able to restore the backup from a different phone but I cannot use DFS or NVEditor to write to the locations? The back I made from the new phone and restored to the old one is Consumer Cellular so I suspect they have locked something out that 5Irom is able to get around but other tools don't.
On another note, just for the heck of it I tried to upgrade to ICS from GB and it fails on the first update step. Go figure.
If I could find a full-flash procedure for the pro and 51 versions of this phone I suspect I could resolve all issues. Who knows?
UPDATE: I went through the whole process again and noted a point I forgot to mention. In DFS at the bottom of the screen EQF is yellow, not green. I don't recall exactly what that means but in reading through the DFS doc, it states that writing a new IMEI is not possible as long as EQF is yellow. When I enter my IMEI and click on the WRITE command the response is "MODECHANGE OfflineD OK"

pastorbob62 said:
Yes, I am rooted.
I started out on 2.2 way back in the beginning. Then I flashed 2.3.5. That's when I lost my IMEI and replaced the phone.
But I wanted to keep experimenting at getting it working 100% even though I had a new working, rooted, and customized phone. Using 5IromToolBox I restored a backup from the new phone to the broken phone just to see if it would work. Then I flashed Stallion-51-ICS custom ROM. It is a GB based ROM with look and feel of ICS.
When I run the procedure in this thread, everything looks as though it has worked, but the IMEI never changes. So what did 5Irom do differently that it was able to restore the backup from a different phone but I cannot use DFS or NVEditor to write to the locations? The back I made from the new phone and restored to the old one is Consumer Cellular so I suspect they have locked something out that 5Irom is able to get around but other tools don't.
On another note, just for the heck of it I tried to upgrade to ICS from GB and it fails on the first update step. Go figure.
If I could find a full-flash procedure for the pro and 51 versions of this phone I suspect I could resolve all issues. Who knows?
UPDATE: I went through the whole process again and noted a point I forgot to mention. In DFS at the bottom of the screen EQF is yellow, not green. I don't recall exactly what that means but in reading through the DFS doc, it states that writing a new IMEI is not possible as long as EQF is yellow. When I enter my IMEI and click on the WRITE command the response is "MODECHANGE OfflineD OK"
Click to expand...
Click to collapse
it should be green! what i would do is to flash 2.2 then 2.3.5 and follow again the steps very carefully! maybe u ever flashed a partition and it's not the default one? i can't really help you :/ try this and if it doesn't work make a thread in the q&a section

Cybergiannis said:
it should be green! what i would do is to flash 2.2 then 2.3.5 and follow again the steps very carefully! maybe u ever flashed a partition and it's not the default one? i can't really help you :/ try this and if it doesn't work make a thread in the q&a section
Click to expand...
Click to collapse
Yeah, I knew that it should be green. The bottom line is I do not have the 2.2 image to flash. I would have done that a long time ago if I had it. All I have is the DiskImage backup that I made off of my new phone. When I flashed it onto the old phone it starts, displays the Consumer Cellular logo for about ten seconds then shuts off immediately. As far as starting a thread in Q & A, I did that weeks ago and got nowhere fast.
Any link I have found for the original 2.2 for -51 and pro is usually a broken link. or it takes me to download that stupid iLivid program that doesn't do squat to get the files I need. I did find a DiskImage file that somebody made and posted but it is almost 4 gig in size. You are supposed to use Pink Screen to load it but Pink Screen only gives me access to the image directory and it's only 256 meg.
Thank you for your time and suggestions.

I believe in the wiki section there are links to default 2.2 and 2.3.5. The ones I found a long time ago were from Blefish, although I'm not sure. Good luck!
Sent from my U8800 using xda app-developers app

Dead link.
Hi.
I try to download the "Drivers for Android 32 and 64 bit win 7 (not tested )", but its a dead link. I run win7 pro, and somehow the 32 bit driver doesn't work.
Would like to try the 64 bit driver. Could u reupload it, please?

I just did a repost cause i veen asked a lot of times I don't have the files and I don't thinks drivers are needed. You could just install huawei's suite for PC
Sent from my U8800 using xda app-developers app

WORKS!!!!
Cybergiannis said:
I just did a repost cause i veen asked a lot of times I don't have the files and I don't thinks drivers are needed. You could just install huawei's suite for PC
Sent from my U8800 using xda app-developers app
Click to expand...
Click to collapse
YEY!!!!!!! It worked!!!!
Update the first post with this info so others dont have to struggle like I did.
Thanks a bunch!!! :victory:

ευχαριστω πολυ----thanks man

Hi All,
Many thanks for this post.
Iv recently installed the Blefish CM11 rom for U8800 and its works fine. Only issue I have is IMEI=0. I can make and receive calls and even use the mobile internet.
My question is - Is there a way to edit the IMEI no on KK4.4.2 ROM through entering in the engineering mode?
or else, will have to start from the beginning (stock rom process as mentioned in the OP).
thanks for your help.

mohammad.nomaan said:
Hi All,
Many thanks for this post.
Iv recently installed the Blefish CM11 rom for U8800 and its works fine. Only issue I have is IMEI=0. I can make and receive calls and even use the mobile internet.
My question is - Is there a way to edit the IMEI no on KK4.4.2 ROM through entering in the engineering mode?
or else, will have to start from the beginning (stock rom process as mentioned in the OP).
thanks for your help.
Click to expand...
Click to collapse
i have no idea. my guess is that u should try

Cybergiannis said:
i have no idea. my guess is that u should try
Click to expand...
Click to collapse
Hi,
I haven't found out the way to fix it yet.
Only way I got to fix is to redo the stock rom, root, save the imei and the reflash the custom rom.
The reason for the imei issue was changing the partitions
thnx anyways

this guide that you have post it has been made by me and at least you should have say that is ported from me. Even the links that you have are in my acount. YOU ONLY COPY MY POST . you could ask me to repost it or just mention me. Check this link http://forum.xda-developers.com/showthread.php?t=1876501

[UPDATED] [Tool-Windows] [ADB for noobs] [the simplest GUI ADB/Fasboot]

*THE TOOL IS UPDATED HERE, HOPEFULLY WILL FIX WHATEVER PROBLEM YOU HAD, WHATEVER! *​
Hello and welcome ! , I wanna play a game :silly:
This tool made specially for noobs & lazy guys , as some of us hate working with any command prompt -and ADB/fastboot are command prompts- so they avoid using it , even if they needed to!
now forget that , this tool is the simplest Graphical user interface ADB,
which will grab popular ADB & Fastboot commands in simple combobox to use
Features..!
My tool is featured in XDA-Portal . Tab Here
Main Features
this tool is written in java, which mean the simplicity , the smallest size and the fastest functions!
this tool depends on your PC , it does nothing on it's own , that makes it very small (about 45 kb!) but powerful
Currently this tool is my only active project , so i'm working on updating it ASAP :good:
Features for human being (to use)
my tool does the most popular/important pure ADB & fastboot operations ,
these operations are :
Check if Device connected properly (adb devices).
Android Logcat.
Install a specific APK file(Android Application).
Uninstall apk <package> .
pull a file from your Android Device to your PC.
push a file from your PC to your Android Device.
Look at tasks running in your Android device.
Check your Android Device Memory usage.
Check your Android Device storage usage.
Kill all background processes.
Normal Reboot.
Reboot to recovery mode
Reboot to Download mode (for Samsung Devices).
Reboot to bootloader mode.
Reboot to Fastboot mode.
Unlock Patterns/passowords with two methods
Flash Update.zip.
Flash recovery.img.
Flash boot.img.
Wipe (System,data & cache) before restoring nandroid backup.
Flash system.img.
Flash data.img.
Flash cache.img.
My tool UI is very simple and easy to use , it's just about 300 x 450 JFrame
​
Requirements..!
You need JRE (the JAVA Runtime Environment ) to run the Tool , you can get it from here .
ADB / Fastboot in your PC (are you kidding?! :cyclops: ).
USB Debugging enabled in your Android Device.
a Human brain which can read the 'How To' in this Thread.
How to & Downloads..!
Download the "ADB For noobs STABLE V3.0.jar" FROM HERE (or in Downloads Tab up) ,
open the downloaded file and set your ADB directory and click Set Data button (you must do that at least once), to make the tool know where's your ADB to use it.
Select the desired operation , and add required directories , then tab Activate , and that's it ! , isn't it Simple ?! :good:
use Reset button to reset text fields
Screenshots...!
the Final release (3.0) :
{
"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"
}
Old Version (2.5) :
Older Version (2.0) :
Even older Version (1.7) :
Or see the Screenshots Tab up.
How to help ?....
at first thanks for clicking "Click To Show Content" Button , that means you really want to help me :fingers-crossed:
Testing is the best method to help me.
you faced problem while using my tool ? let me know in the comments.
You have Suggestions ? .. PM Me with your suggestions .
you miss some adb/fastboot functions ? , feel free to request :good: .
DON'T FORGET TO CLICK MY
BUTTON .
Changelog...!
Code:
* 29 - 01 - 2015
the final release (3.0)
-fix : a few problems in the UI .. and a simple touch to the code.
-added : unlock patterns/passwords with 2 methods.
Note : no need to say that this update is just to leave that project sleep in peace , it just fixes some mistakes that I couldn't fix them because I didn't had enough time.
* 15 - 06 - 2014
release (v2.5)
-this version will give you the UI that you deserve ,look and feel is better and more simple than before.
-many pure ADB operations optimized.
-setting my data is more reliable (i'v optimized the code to get rid of these (Apk_dir.txt , P_dir.txt ....etc).
-reset button added (to reset text fields).
-the problem of (confirm dialog) that repeat the operations fixed.
-check updates button added (will open this thread's link).
-now all operation that returns output like (logCat , adb Devices.....etc) will store their logs in .text files.
-tool size reduced from 60 kb to 38 kb , lol .
* 10 - 06 - 2014
the third release (v2.0) :
-this version has several UI optimizations to make things 80% easier than before.
-many code problems solved , problems with some operations solved.
-storing all data in one folder ("Data") to make the look unique.
* 05 - 06 - 2014
the second release (v1.7) :
-code optimization , fixed 2 tools problems.
-now the adb / fastboot command prompt will close immediately after finishing an operation, except in memory/storage usage and logcat.
-new adb & fastboot options are added :
-Kill all background processes.
-Reboot to recovery mode.
-Reboot to Download mode (for Samsung Devices).
-Reboot to bootloader mode.
-Reboot to Fastboot mode.
-Flash Update.zip.
-Flash recovery.img.
-Flash boot.img.
-Wipe (System,data & cache) before restoring nandroid backup.
-Flash system.img.
-Flash data.img.
-Flash cache.img.
-the tool will create folder called patch to store all my .bat scripts in it.
* 03 - 06 - 2014
the initial release (v1.0) .
Credits...!
My Friend @kermage .... thanks for helping and Suggestions :good: :fingers-crossed:
My Friend Yusuf Badr ... thanks for Testing :good: :fingers-crossed:
XDA:DevDB Information
ADB for noobs (GUI ADB/Fastboot), Tool/Utility for all devices (see above for details)
Contributors
Mohamed Hashem
Version Information
Status: Stable
Current Stable Version: 3.0
Stable Release Date: 2015-01-29
Current Beta Version: 1.7
Beta Release Date: 2014-06-03
Created 2014-06-03
Last Updated 2015-01-28

Reserved
supposed to be reserved for unknown thing , who cares!

apple pie
DON'T FORGET TO CLICK MY
BUTTON .

Amazing work
Nicely done :good: :good: keep it up

Up!

Good job! :good:
But maybe on the next update, try to make it really for noobs & lazy guys; a 1 tool, installation/settings in the first run.

kermage said:
Good job! :good:
But maybe on the next update, try to make it really for noobs & lazy guys; a 1 tool, installation/settings in the first run.
Click to expand...
Click to collapse
i understand that you mean Setup window at first run .. but this will make the app for windows only , also you just need to run the 1st tool just once , then you can just delete it , but i'll try my best to make it easier , btw , before a day from making this thread , it was so dummy and you should add your adb dir every time to run it , as this pic : http://i.imgur.com/xbwtquz.jpg
btw , what about it's operations , you find any thing bad ? thx very much for your help and report
EDIT: Oh , i think i got an idea .. next update will solve this , also will have more operations , may be fastboot commands too

Mohamed Hashem said:
i understand that you mean Setup window at first run .. but this will make the app for windows only , also you just need to run the 1st tool just once , then you can just delete it , but i'll try my best to make it easier , btw , before a day from making this thread , it was so dummy and you should add your adb dir every time to run it , as this pic : http://i.imgur.com/xbwtquz.jpg
btw , what about it's operations , you find any thing bad ? thx very much for your help and report
EDIT: Oh , i think i got an idea .. next update will solve this , also will have more operations , may be fastboot commands too
Click to expand...
Click to collapse
No need for setup window, use java ini/properties file instead.

new update is out , check the changelog and Screenshot :good:

Now that the Gear has moved from Android to Tizen we need a modded version to work with SDB instead of ADB.

Mohamed Hashem said:
new update is out , check the changelog and Screenshot :good:
Click to expand...
Click to collapse
Are you missing a DLL file from your Java Program? I'm getting Java errors stating it can't find the main class of the file. I'm running Windows 7 32-Bit and Java 6 Standard Edition installed.

how can i use it to flash twrp or cwm img file to my phone??

Would be perfect if it had a feature to batch install apks.

jman1234 said:
Would be perfect if it had a feature to batch install apks.
Click to expand...
Click to collapse
sorry didn't understand that .. i mean it had "install apk" option , but what do you mean with batch install apk ?
mashnino said:
how can i use it to flash twrp or cwm img file to my phone??
Click to expand...
Click to collapse
just add the file you want to flash in the 1st text box called "select file to install / flash / push and then select the option from combo box
rootdefyxt320 said:
Are you missing a DLL file from your Java Program? I'm getting Java errors stating it can't find the main class of the file. I'm running Windows 7 32-Bit and Java 6 Standard Edition installed.
Click to expand...
Click to collapse
no it's just fine with me and others :\ , upgrade to higher Jre or redownload
Guys , new update is coming today or tomorrow , will make things much easier :good:

Mohamed Hashem said:
...
Click to expand...
Click to collapse
great job :good::good::good:
long time no see

naheel azawy said:
great job :good::good::good:
long time no see
Click to expand...
Click to collapse
wallahi enta m4 3arf ana far7an 2d eh eny shoftk

NakedFaerie said:
Now that the Gear has moved from Android to Tizen we need a modded version to work with SDB instead of ADB.
Click to expand...
Click to collapse
the problem is that i don't have any Tizen based device , so , even if i made it support SDB i wouldn't be able to test it lol

Very useful thanks bro. And one thing I pressed thanks button on first post just kidding .
Sent from my LG-P500 using XDA Premium 4 mobile app

Good work there @Mohamed Hashem.. surely will help newbies (Y)

Mohamed Hashem said:
sorry didn't understand that .. i mean it had "install apk" option , but what do you mean with batch install apk ?
Click to expand...
Click to collapse
by batch install, he means to select multiple APKs and install them together without having to select one after another and wait for it to install.

Root+Xposed+Busybox for Bootloader Locked Moto X ATT/VZW

Only fresh flashed bootloader locked XT1058 AT&T - ROM LPAS23.12-21.7-1, and XT1060 VZW - ROM LPAS23.12-39.7-1 are supported!
See archive content for instructions. Time to install ~20 min. If you experience problems after Android boot, like not working buttons or quick settings, wipe cache + data partitions. Don't update SuperSU (disable auto updates), it won't work. Later I'll post complete debloated ROMs with fresh SuperSU version, and simplify instructions. Be informed also, that this method doesn't give you read-write rights like unlocked bootloader. You may read and write having root-rights, but only till a restart or shutdown occurs, and every change will be undo by the Qualcomm protection (like HTC' s=on).
At the moment patch includes:
SuperSU 2.65 Free
Xposed Framework v86 (installer, modules)
Busybox 1.25.0.YDS, path /system/xbin/busybox
Download
P.S. Install only on indicated above ROM versions, and it's obvious that you must have enough theory knowledge and practical experience to make use of 9008 patch, so I'm not responsible for any consequences, etc. Greets go to: CrashXXL (method inventor), Sabissimo (our former OP), and serg_gangubas (ROM guru).
==============================================================================================
31.07.2017 - Full ROM Patch for Bootloader Locked Moto X ATT/VZW/etc
Based on the same principle, and not depend on system partition content, so it suits any bootloader locked Moto X Gen1 ATT/VZW (possibly any model, besides 1049 RepW / 1055 US Cell), but takes about 4 hours to be done - prepare for that, 100% battery level only!
This full ROM patch includes:
SuperSU 2.82 Free
Xposed Framework v87 (installer, modules)
Busybox 1.26.2, path /system/xbin/busybox
ViperFX 2.5.0.5 - sorry needs polishing, removed now (
Gallery and Camera not depend on Moto services
Gboard instead AOSP Keyboard. If it eats too much RAM, see Simple Keyboard
GAPPSes updated. Use command like adb shell pm uninstall --user 0 com.blahblah.blah to block any unwanted app or service
ES File Explorer Free Edition (a clone, you can disable and install yours )
"Jedy" gesture
AdBlock support (effect lasts till the 1st reboot yet, I'll think about make it constant). Please, choose /data/hosts instead of /system/etc/hosts
ROM debloated, but not deodexed.
Download
Instruction
Be careful, phone will be WIPED then flashed in 9008 "brick" mode (CrashXXL idea). Before you start install Moto drivers, latest RSD Lite, and fully charge the battery.
1) Download and unpack zip on С: (or any), open Python27, launch RUN_path.bat (needs to be launched only single time), install driver QHSUSB_driver.exe, and launch file _Moto.X.BootLocked.*.exe (where * - is desired ROM).
2) Go into fastboot mode, execute RUN_blbroke.bat. Screen gets black, Device Manager in Windows finds "QHSUSB_DLOAD", and installs it as "Qualcomm HS-USB QDLoader 9008 (COM*)". If it doesn't install, google for Windows driver digital signature disable.
3) Now launch RUN_root.bat, and see that patching process took start.
4) A small patch *SPEAKERS.BOOST.exe (if exists) boosts both speakers' volume.
P.S. Please, don't flash anything extra into the phone. In case of trouble, all you need is inside this folder. Just make it work.
To make "Battery OK" in fastboot use fastboot_cyclecharge.bat
Completely drained out battery causing "USB input device" needs disassembly of the phone to charge externally.
In case Titanium Backup shows error "Batch backup interrupted: insufficient free storage space", delete default backup folder, and make a new:
Titanium Backup > Menu > Preferences > Backup folder location > Storage Provider > DocumentProvider storage > Show Internal Storage > Internal Storage > Select Internal Storage > Create the folder > Use the current folder. Done!
Notes for myself: Viper, force wipe, readme.txt, volume patch, Adblock, advanced debloat

Debloated, rooted, lightweight ROM - soon! )
PUBLISHED. Sorry, took long time.

As soon as I can actually get 5.1 flashed I'll try this.
Though I'm afraid I'll have to try to go to stock and use sunshine first, still have a locked BL.
But this is great, I didn't expect root so soon.

DownTheCross said:
As soon as I can actually get 5.1 flashed I'll try this.
Though I'm afraid I'll have to try to go to stock and use sunshine first, still have a locked BL.
But this is great, I didn't expect root so soon.
Click to expand...
Click to collapse
This method is working on locked BL.

DownTheCross said:
As soon as I can actually get 5.1 flashed I'll try this.
Though I'm afraid I'll have to try to go to stock and use sunshine first, still have a locked BL.
But this is great, I didn't expect root so soon.
Click to expand...
Click to collapse
Wait wait... If you can have now possibility to unlock bootloader - go for it immediately! You will have normal FULL root-rights (SuperSU 2.49). Don't install 5.1, if you plan to unlock, because Sunshine app (25$) works only on 4.4.2 Android.
This topic is to help those AT&T users that are boot locked forever (who missed out possibility to unlock on 4.4.2 by proceed to 5.1) to give them READ-ONLY root. Yes, it's limited, but anything at least.

s5610 said:
If you can have now possibility to unlock bootloader...
Click to expand...
Click to collapse
I guess anyone on 4.4.4 today. There is no possibility to use Sunshine anymore.
Anyway spasibo za method

Ahh, if I don't have to be BL unlocked that's great lol.
I haven't read too much into the 5.1 updates or sunshine for that matter.
I've been on krypton 1.4.1 since it was released, and I haven't been able to successfully upgrade to any 5.1 roms yet.

Works great!
Works great for me on Windows 10 RTM 64-bit! Thanks a ton, I was waiting for a post like this.
I only had 3 minor hiccups:
1. RSD Lite gave me an error about "getvar", so I had to go into flashfile.xml in the ROM zip and remove the line that said getvar
2. I had to reboot to disable driver signature enforcement twice for some reason because Windows Update
3. The run-root.bat got stuck on "Executing..." because I installed the wrong driver (the correct file is qcusb.inf when installed from device manager -> browse my computer for driver software -> let me pick from a list -> all devices -> have disk)
Otherwise, everything runs just as well as KitKat, including Xposed.

Hehe got to love step 9

System Write
How can we help in getting the system write to zero using the same method,because I have xt1058 model bootloader unlocked and I provide any file needed to disable the pesky system write...

How can we help in getting the system write to zero using the same method,because I have xt1058 model bootloader unlocked and I provide any file needed to disable the pesky system write...
Click to expand...
Click to collapse
First, never quote op. It takes way to much space and is redundant.
Second, to get write off we would need to some how either start a custom kernel some magical way or disable it via a kernel mod like htc guys did. Another way, which was done before was to burn the efuse but kernel has been patched since then.

Need some help, I did all steps until step 9. I installed the QHSUSB_DLOAD driver manually, and I can see 'Qualcomm HS-USB QDLoader 9008 (COM4)' showed in my Device Manager, but when I run 'RUN_Root.bat', I got this
c:\Python27>python qdloadRoot.py MPRG8960.bin -ptf root/partitions.txt
QDLoad utility version 1.2 (c) VBlack 2014
Found TTY port: com4
Sending MAGIC ...
QCOM fast download protocol targ:
Version: 7
Compatible version 2
Maximum block size 1024 (0x00000400)
Base address of Flash 0x00000000
Flash: eMMC
Window size: 30
Number of sectors: 128
First sector size: 2097152 (0x00200000)
Feature bits: 09
Sending SBL Reset...
Done
c:\Python27>pause
Press any key to continue . . .
Then I tried to run 'RUN_Root.bat' again, then I got
c:\Python27>python qdloadRoot.py MPRG8960.bin -ptf root/partitions.txt
QDLoad utility version 1.2 (c) VBlack 2014
Found TTY port: com4
Requesting Params...
Params:
Version: 8
Min version: 1
Max write size: 1536 (0x00000600)
Model: 144
Device size: Invalid or unrecognized Flash device, or Flash device progr
amming not supported by this implementation
Device type: Intel 28F400BX-TL or Intel 28F400BV-TL
Requesting SoftwareVersion...
Version: PBL_DloadVER2.0
Requesting SerialNumber...
Serial number: 00,00,48,03
Requesting HW Id...
HW Id: 00,00,48,03,e1,10,7e,00
Requesting PublicKey...
PublicKey: 39,c4,ee,3e,b5,be,eb,87,8e,2f,e3,b8,53,4d,14,6f,91,ca,fd,bb,94,2a,0d
,aa,d0,1e,b0,87,62,d4,b9,b8
Uploading file 'MPRG8960.bin' to addr 0x2a000000...
Executing...
Could not find Qualcomm device in Emergency download mode
Done, with errors!!!
c:\Python27>pause
Press any key to continue . . .
any suggestions? Thanks

jahrule said:
First, never quote op. It takes way to much space and is redundant.
Second, to get write off we would need to some how either start a custom kernel some magical way or disable it via a kernel mod like htc guys did. Another way, which was done before was to burn the efuse but kernel has been patched since then.
Click to expand...
Click to collapse
Ill put the files here

Fantastic!!! I was looking this. All the last week I was sleeping about 3 hours per day trying to root my phone.
----
I scream "Victory" before the process finish.
Damn! My phone reboot and stay in the android doll fallen screen.

DejanPet said:
Ill put the files here
Click to expand...
Click to collapse
What to do with these files?

Those files are needed by Jahrule

Sabissimo
Hello.
I did everything as instructed, but eventually got the screen "no command".
The only thing I did not flash rom - a month ago updated by an OTA to 5.1, thought it was not necessary.
Factory reset does not help.
Advise something.
In the end, everything worked, thank you))

It works
It works great! Thank you very much! ATT xt1058.

eze_cba17 said:
Damn! My phone reboot and stay in the android doll fallen screen.
Click to expand...
Click to collapse
Follow the OP instruction EXACTLY, no exceptions!
If you got your current 5.1 through AT&T OTA, it's not enough for root patching procedure. A full RSD 5.1 official SBF flash over is required.

Could someone please do a video on this. I'm having a little trouble.

[TOOLKIT][ZS570KL/PRO][1.0] Zenfone 3 Deluxe One Click Tool

Here we are with a new tool. Ready for modding our ZS570KL/PRO
This is a batch modder with all files for modding our device into it.
How to use:
Extract the zip in a folder, then make sure you have all required drivers for fastboot/adb. Then enable USB Debugging into your phone and open the tool.
Functions:
Check connection status
Bootloader Unlocker
Flash TWRP
Root Flasher
ADB Shell
Erase /system, /data and /cache
DPI Changer
Resrart Menu
Download:
Zenfone3 Deluxe Toolkit 1.0
Changelog
Post #2
Based Tool
Zenfone3 Toolkit
Credits:
@Chainfire for SuperSu
Forum OneTeam

V1.0
Turkish English Language choose Added.
Added Dictation on opening.
Added Fastboot Connection Setup.
Added OEM Locker Acme.
TWRP Setup Added.
Root Throw Added.
Drivers Added.
/ System, / data, / oncache Clear Added.
Changes Added.
Added Referral to Forum.
Theme Color Changed.
Sizes Adjusted Repeatedly.
Two pictures added.
Modifications Added Files And Code.
All Codes Created For Both ZS570KL/PRO

Reserved

Picking either language brings up some error then exits out. I'm pretty sure I have everything downloaded for drivers and also have the debugging on.

Yep I had the same problem upon language selection it just crashed

Question
EypCnn said:
Reserved
Click to expand...
Click to collapse
I have a TIM-branded SKU on my ZS570KL, will these tools work for me?
Can you help me unbrand the phone? I have found two forums, but unfortunately both lack the info I need to feel certain enough to try this.

It's possible to relock the bootloader?

Ryder. said:
It's possible to relock the bootloader?
Click to expand...
Click to collapse
Hi Ryder, why do you need relock the bootloader?, for send to repair in warranty maybe, but I think relock is not an option for send to repair in warranty.
Sent from my ASUS_Z016D using Tapatalk

sat182 said:
Hi Ryder, why do you need relock the bootloader?, for send to repair in warranty maybe, but I think relock is not an option for send to repair in warranty.
Sent from my ASUS_Z016D using Tapatalk
Click to expand...
Click to collapse
No, it's just for sell the device if i want

When I choose 1 or 2 I have a message error wiyh "goto"

Serves for the ZE552KL (Z012DC)?