Database Info

[ROOT] unrevoked3 v3.31 (with support for new HBOOT, now with amend scripting!)

Hi!
On behalf of the unrevoked team, we're proud to announce the new release of unrevoked -- version 3.3. This version adds support for HBOOT 2.02 and 2.10, and also adds support for the new OTA, 3.70.651.1.
You can get it at our site, http://www.unrevoked.com/recovery/ .
New in this release is ClockworkMod 3.0.0.2. We and Koush have been working hard on getting ClockworkMod all set and safe on EVO 4G; ClockworkMod is now using the latest EVO 4G kernel, for one, and now has nandroid options to back up your WiMAX keys. It also encodes your phone's serial number in the WiMAX backup, which greatly reduces the risk of restoring the wrong WiMAX image to the wrong phone. Please try it out!
We'll be watching this thread off and on. There are a few known glitches; carefully read the frequently asked questions in the "More Info" section, linked from the page above.
Thanks for everyone's support and assistance -- and have a happy new year!
joshua
unrevoked
UPDATE:
I just pushed out 3.31, which fixes a bunch of small issues that people were having, and backs down to Clockwork 2.6.0.1. This adds support for Amend scripting back in, but keeps all the good changes from 3.0.0.2 -- WiMAX backup, and the new kernel with support for new hboot partitions. I tested this pretty thoroughly -- I fully erased my WiMAX partition with erase_image wimax (don't try this at home!), and then restored it from a backup I took with Clockwork 2.6.0.1. My keys were intact, and my 4G still works. More detail about the changes can be found in the changelog. Thanks!

You guys are the best!!!!!!!!

so im guessing you fixed the recovery. because in my testing with the new version of cw...on older hardware with the new hboot it wouldnt back up squat...and there have been reports of people noting being able to flash things with the new version on new hardware or not being able to boot.
thanks for the hardwork

Sweet! will be trying this on my new EVO tonight... will update how it goes.
Thanks guys for the hard work!

This is great news.
I'm going to hold off on doing anything for now until the flashing issues are completely figured out and there is a solid 3.2 build out.
Thanks for all of your hard work guys.

Is the new version setup to install the old 2.5 version of Clockwork if you use it against an older partition structure? Word is that Clockwork 3.0.0.2 is not backwards compatible with the old partition structure.

bkrodgers said:
Is the new version setup to install the old 2.5 version of Clockwork if you use it against an older partition structure? Word is that Clockwork 3.0.0.2 is not backwards compatible with the old partition structure.
Click to expand...
Click to collapse
didnt work in my testing...but i am just one person. all though i got the same results across 3 evo's two old 0003 and one newer 0003 (with the new camera)

Soooooo stoked for this!!!

VERY NICE!!!!

Quick question, I don't have 4g in my area yet so I haven't gotten 4g connected yet. So should I flash the new wimax radio and start my new restorations from there or just leave it as is and keep my old backups along with whichever new ones I create?
Sent from my PC36100 using XDA App

did this and it worked use it guys make sure you follow everything. Unrevoked team cwr gave me some problems while rebooting it gave me lines on my screen it looks scary but it works so i just switch to amon recovery anyways thanks

First post so please be kind!!!
Downloaded 3.3 but the reflash.app won't open on my Mac. I get the "The application Reflash quit unexpectedly". I had done it before on 3.2 and no issues using the same cpu. Please help.

revel1973 said:
First post so please be kind!!!
Downloaded 3.3 but the reflash.app won't open on my Mac. I get the "The application Reflash quit unexpectedly". I had done it before on 3.2 and no issues using the same cpu. Please help.
Click to expand...
Click to collapse
sno leopard only. sorry...

running on Ubuntu, ran it in terminal as "sudo ./reflash" as to give it root permssions and it pushed the recovery in no time but has been stuck on "installing unrevoked3 service" for about 10 minutes now....afraid to unplug/close it. any help/clues?

no workie on mac
does not work on mac.. help please
Process: Reflash [1592]
Path: /Volumes/unrevoked Recovery Reflash Tool/Reflash.app/Contents/MacOS/Reflash
Identifier: com.unrevoked.reflash
Version: ??? (???)
Code Type: X86 (Native)
Parent Process: launchd [1478]
Interval Since Last Report: 67764 sec
Crashes Since Last Report: 14
Per-App Interval Since Last Report: 0 sec
Per-App Crashes Since Last Report: 13
Date/Time: 2010-12-31 18:17:57.903 -0800
OS Version: Mac OS X 10.5.8 (9L31a)
Report Version: 6
Anonymous UUID: A75357B4-8467-4198-A16A-F271443B65A6
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Crashed Thread: 0
Dyld Error Message:
unknown required load command 0x80000022

just did my wife phone on a mac with snow leopard and it worked just fine. the trick was that i had debugging already enabled when i loaded unrevoked so i disabled it then enabled it while still on unrevoked and it worked.

jorge.l.diaz said:
does not work on mac.. help please
Process: Reflash [1592]
Path: /Volumes/unrevoked Recovery Reflash Tool/Reflash.app/Contents/MacOS/Reflash
Identifier: com.unrevoked.reflash
Version: ??? (???)
Code Type: X86 (Native)
Parent Process: launchd [1478]
Interval Since Last Report: 67764 sec
Crashes Since Last Report: 14
Per-App Interval Since Last Report: 0 sec
Per-App Crashes Since Last Report: 13
Date/Time: 2010-12-31 18:17:57.903 -0800
OS Version: Mac OS X 10.5.8 (9L31a)
Report Version: 6
Anonymous UUID: A75357B4-8467-4198-A16A-F271443B65A6
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Crashed Thread: 0
Dyld Error Message:
unknown required load command 0x80000022
Click to expand...
Click to collapse
same error i got on leopard. you need snow leopard.

How would I go about upgrading my hboot so that I can use the new cmw, and root with this method.
Sent From My HTC Evo 4G On The Now Network From Sprint Using Tapatalk Pro!

I Can Backup My Original Evo Rom But I Can't Flash Any. I Get The Lines Too. Should I Just Flash An Older Clockworkmod Or Just Go To Amon's ?
&& I'm On A Old Recovery ( 2.5.0.1 ) . It Looks Like 3.0.0.2 Doesn't Work . Or Am I Wrong ?
I'm A Rookie . -_-
Btw , I'm Trying To Flash Salvage-Mod .9.3 Gingerbread .

I cannot flash a new rom either, it cannot access my SD card.......?

[Completed] PTTYCMD1 deleted after reboot. [Cherry Mobile Omega XL]

Phone model: Cherry mobile Omega XL
Hardware Mediate: MT6582
current ROM: MIUI
Android Version: 4.2.2 JDQ39
baseband Version: Unknown
IMEI: NULL
Dual Sim
Radio State: Off
I installed terminal emulator in my phone and run the following lines:
such
echo 'AT+EGMR=1,7,"123456789012345"'>/dev/pttycmd1
echo 'AT+EGMR=1,10,"123456789067890"'>/dev/pttycmd1
The line above works in terms of creating the file pttycmd1 in dev folder.
So to make sure that my IMEIs' will be set, I connect my phone in my PC and run the MTK droid tools in Windows 7 then set my IMEIs there and I received no error such as " pttycmd1 is not found!" since pttycmd1 is already existing.
Then I reboot my phone. But, the problem still occurs. My IMEIs still null, my radio is turned off and my baseband version is unknown.
I've checked the dev folder and again the pttycmd1 has been removed. Before I reboot my phone, I even changed the permission to read and execute only. But it was gone.
I've done the steps above 3 times but still no luck.
I was not able to backup my stock ROM.
I've previously posted the details of what happened to my phone. see thread below:
forum.xda-developers.com/showthread.php?t=2793105
I've attached the screenshots of the terminal emulator and the dev folder where you'll see the pttycmd1 before it was removed.
See screenshots below:

One of my colleague already answered you in one of your several posts.
I close this thread
Thanks in advance

[Droid Maxx 4.4.4 SU6-7] Trying to root and can't run RUN_Root.bat

Hello all, I've been trying to root my Droid Maxx 4.4.4 SU6-7 and was working fine until after bricking it, I was unable to run the RUN_Root.bat. I'm running Windows 7 64 bit. This is the error I would get in the command prompt after trying to run RUN_Root.bat .
C:\Python27>python qdloadRoot.py MPRG8960.bin -ptf _root/partitions.txt
QDLoad utility version 1.2 (c) VBlack 2014
Found TTY port: com9
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 programming 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 . . .
I can still use the USB I think. I see Qualcomm HS-USB Loader 9008 (COM9) in the device manager whenever I would plug in the USB and it was manually updated after I selected x64 folder from the windows_drivers_QHSUSB_DLOAD folder(windows would say it was up to date when selecting x64 folder). I tried different ports but the Port otion never shows up for them in the device manager. I'm also not using USB 3.0.
I believe I followed every other instruction as far as I know from this thread http://forum.xda-developers.com/droid-ultra/general/droid-mini-maxx-ultra-root-pogress-100-t3071609 I'd really appreciate if someone could help me out.

Phoop said:
Hello all, I've been trying to root my Droid Maxx 4.4.4 SU6-7 and was working fine until after bricking it, I was unable to run the RUN_Root.bat. I'm running Windows 7 64 bit. This is the error I would get in the command prompt after trying to run RUN_Root.bat .
C:\Python27>python qdloadRoot.py MPRG8960.bin -ptf _root/partitions.txt
QDLoad utility version 1.2 (c) VBlack 2014
Found TTY port: com9
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 programming 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 . . .
I can still use the USB I think. I see Qualcomm HS-USB Loader 9008 (COM9) in the device manager whenever I would plug in the USB and it was manually updated after I selected x64 folder from the windows_drivers_QHSUSB_DLOAD folder(windows would say it was up to date when selecting x64 folder). I tried different ports but the Port otion never shows up for them in the device manager. I'm also not using USB 3.0.
I believe I followed every other instruction as far as I know from this thread http://forum.xda-developers.com/droid-ultra/general/droid-mini-maxx-ultra-root-pogress-100-t3071609 I'd really appreciate if someone could help me out.
Click to expand...
Click to collapse
Besides manually update the driver.
First, you have to disable the mandatory use of signed drivers in Windows.
Why? The driver you are trying to install (or update) is not signed and windows by default only allows the use of signed drivers.
Search a tutorial on "how to install an unsigned driver Windows 7"
I send you some, but I am the translator of google lol ..
I had a similar problem for the driver and the solution I gave you, solved my problem.
The best of luck, a big hug!

I managed to fix my problem yeasterday following br0adband advice in this thread http://forum.xda-developers.com/showpost.php?p=62651329&postcount=1159 sorry I forgot to close my thread(if I can figure out how). Thanks for that helpfull tip though, I'll keep that in mind for later driver issues.

[Q] Trying to root SM-G920F using Linux

Hi! I'm exasperated so I turn to the experts: you! I hope this is right (or should I have continued this megathread?)
TLDR: Want to root international S6 running branded 5.1.1; but using Linux and having trouble getting things to work. Have tried lots already; details below.
1. bootloader status = I think it's unlocked but not sure how to determine this.
2. Rom name with complete baseband/date/version = "Austrian 3/Hutchinson" branded, PDA Version G920FXXU3COI9, CSC Version G920FDRE3COJ1, PHONE Version G920FXXU3QOJ1.
3. Kernel name = uh, stock Samsung 5.1.1?
4. Mods = none
5. Custom Rom = none
6. Guides =
7. Root status = unrooted.
8. Your exact problem = Want to root, having trouble doing so.
9. Any method you tried that failed = see details below.
10.Any other detail you think would be necessary = my phone's ODIN screen lists this information:
PRODUCT NAME: SM-G920F
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
REACTIVATION LOCK: OFF
Secure Download: Enabled
KNOX WARRANTY VOID: 0 (0x0000)
RP SWREV: B:3 K:2 S:2
I've tried rooting my S6 using Linux, using a virtual WInXP hosted on Linux, and using an old real WinXP computer. None of the methods worked, but let me describe what I've tried on each -- I'd be happy if I can get either one of the methods across the finish line!
1) Virtual WinXP computer on Linux host
created a brand-new virtual WinXP installation to make sure nothing would interfere.
Installed Samsung drivers.
Installed Odin 3.06 - this is the newest version I could find that didn't show the error "The procedure entry point DecodePointer could not be located in the dynamic link library KERNEL32.dll."
In the settings for the virtual machine, set up rules to ensure all Samsung USB devices (USB vendor ID 04e8, any product ID) would be routed directly to the virtual machine.
Rebooted for good measure.
Connected phone in rear USB port, directly on motherboard (no hubs).
Neither Windows nor Odin sees the phone - neither in its normal operating mode nor in its "Odin" download mode.
Give up.
2) Physical Ubuntu computer, using JOdin
Installed Heimdall (latest version = 1.4.0-0).
Downloaded JOdin (latest version = v1035).
Installed Oracle Java 8 (8u67).
Rebooted for good measure.
Connected phone in rear USB port, directly on motherboard (no hubs).
JOdin says: "We could not obtain the pit file. We tried, but it didn't work." It seems that this is not really JOdin's fault but rather Heimdall (which JOdin relies on) because running just Heimdall from the CLI gives the same problem, as seen from this log (verbose version).
I dare not download a "random" PIT file from the Internet; this would satisfy JOdin but the risk of choosing the wrong one is too high. Other sites also mention ways to use the adb shell but ironically these require root - so I can't use them.
3) Physical WinXP computer
I did all of the above Linux trickery because I don't own a computer with Windows. By sheer chance, a friend came by with an old WinXP machine that I could commandeer for this purpose.
Installed Samsung drivers.
Installed Odin 3.06 - this is the newest version I could find that didn't show the error "The procedure entry point DecodePointer could not be located in the dynamic link library KERNEL32.dll."
Rebooted for good measure.
Connected phone in rear USB port, directly on motherboard (no hubs).
Odin sees my phone in download mode (first success!) and I can do the steps to start the root.
Odin works it way through the file and goes to "NAND write start" and then "Complete(Write) operation failed". I've tried this using the CF-Auto-Root and also separately using the unibase kernel for 5.1.1, with identical results.
I feel that I'm so close and yet success is not yet in reach. What more can I do? Thank you for your help and kind assistance!

torbengb said:
Hi! I'm exasperated so I turn to the experts: you! I hope this is right (or should I have continued this megathread?)
TLDR: Want to root international S6 running branded 5.1.1; but using Linux and having trouble getting things to work. Have tried lots already; details below.
1. bootloader status = I think it's unlocked but not sure how to determine this.
2. Rom name with complete baseband/date/version = "Austrian 3/Hutchinson" branded, PDA Version G920FXXU3COI9, CSC Version G920FDRE3COJ1, PHONE Version G920FXXU3QOJ1.
3. Kernel name = uh, stock Samsung 5.1.1?
4. Mods = none
5. Custom Rom = none
6. Guides =
7. Root status = unrooted.
8. Your exact problem = Want to root, having trouble doing so.
9. Any method you tried that failed = see details below.
10.Any other detail you think would be necessary = my phone's ODIN screen lists this information:
PRODUCT NAME: SM-G920F
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
REACTIVATION LOCK: OFF
Secure Download: Enabled
KNOX WARRANTY VOID: 0 (0x0000)
RP SWREV: B:3 K:2 S:2
I've tried rooting my S6 using Linux, using a virtual WInXP hosted on Linux, and using an old real WinXP computer. None of the methods worked, but let me describe what I've tried on each -- I'd be happy if I can get either one of the methods across the finish line!
1) Virtual WinXP computer on Linux host
created a brand-new virtual WinXP installation to make sure nothing would interfere.
Installed Samsung drivers.
Installed Odin 3.06 - this is the newest version I could find that didn't show the error "The procedure entry point DecodePointer could not be located in the dynamic link library KERNEL32.dll."
In the settings for the virtual machine, set up rules to ensure all Samsung USB devices (USB vendor ID 04e8, any product ID) would be routed directly to the virtual machine.
Rebooted for good measure.
Connected phone in rear USB port, directly on motherboard (no hubs).
Neither Windows nor Odin sees the phone - neither in its normal operating mode nor in its "Odin" download mode.
Give up.
2) Physical Ubuntu computer, using JOdin
Installed Heimdall (latest version = 1.4.0-0).
Downloaded JOdin (latest version = v1035).
Installed Oracle Java 8 (8u67).
Rebooted for good measure.
Connected phone in rear USB port, directly on motherboard (no hubs).
JOdin says: "We could not obtain the pit file. We tried, but it didn't work." It seems that this is not really JOdin's fault but rather Heimdall (which JOdin relies on) because running just Heimdall from the CLI gives the same problem, as seen from this log (verbose version).
I dare not download a "random" PIT file from the Internet; this would satisfy JOdin but the risk of choosing the wrong one is too high. Other sites also mention ways to use the adb shell but ironically these require root - so I can't use them.
3) Physical WinXP computer
I did all of the above Linux trickery because I don't own a computer with Windows. By sheer chance, a friend came by with an old WinXP machine that I could commandeer for this purpose.
Installed Samsung drivers.
Installed Odin 3.06 - this is the newest version I could find that didn't show the error "The procedure entry point DecodePointer could not be located in the dynamic link library KERNEL32.dll."
Rebooted for good measure.
Connected phone in rear USB port, directly on motherboard (no hubs).
Odin sees my phone in download mode (first success!) and I can do the steps to start the root.
Odin works it way through the file and goes to "NAND write start" and then "Complete(Write) operation failed". I've tried this using the CF-Auto-Root and also separately using the unibase kernel for 5.1.1, with identical results.
I feel that I'm so close and yet success is not yet in reach. What more can I do? Thank you for your help and kind assistance!
Click to expand...
Click to collapse
I think may need to find a way to run the newest odin thats the only thing i can see thats rong in your attempts idk im not a big linux guy. U might need to get ahold of a win8 pc

WinXP SP2 = solved!
I solved the problem on Windows and finally got that big friendly PASS! :laugh:
As it turns out, there were two things blocking my success:
Odin version not compatible
Windows XP needed Service Pack 2
Initially I tried using the newest version of Odin, of course. But version 3.10.7 does not work, says "is not a valid Win32 application" so I went back to earlier versions until I found one that could run. The second-newest Odin version 3.10.6 does not work, says "The procedure entry point DecodePointer could not be located in the dynamic link library KERNEL32.dll." Finally, version 3.06 could run, but as I now know, that version is so old that it does not support the Samsung S6! Of course it doesn't say so, and that's why I was stumbling in the dark for a good while.
So I need a newer version, but what can I do to make the newest one work? I finally discover that v3.10.7 (despite being only a minor release) has this in its unofficial release notes: "Removed support for Windows XP or earlier"! Okay that was hard to find!
So I need the previous version, v3.10.6. However, that one complains about kernel32.dll. Where can I find a newer version of that DLL? It dawns on me that my brand-new WinXP installation doesn't have any of the service packs yet, so I install WinXP SP2 and, lo and behold, version 3.10.6 can finally run!
But all of this was on my virtual machine, and it still couldn't detect when I plugged in the phone on the host computer. So I took a look at the WinXP machine that luckily was passing through my home just now. It's in German, and only runs WinXP SP1. I managed to find and install SP2 in German, and finally I had Odin v3.10.6 running on that machine - and it actually detected my phone!!
From here on, it was trivial to complete the rooting process. Once the software gets to run as intended, it's a beautifully simple thing. My phone is now rooted, and I can finally have Llama put it into airplane mode when I go to sleep. SUCCESS!
(But I still don't know why it doesn't work on Linux.)

Asus Flash Tool 2.0 by Adithyan25

Today I Present You with My new Software the Asus Flash Tool 2.0.
By Uisng this Software You Can Flash Your Asus Phone Without any difficulty.
Step 1
Open the ASUS Flashtool, AFT will automatically detect mobile devices (if not automatically detect, please re-plug the USB cable)
Step 2
Automatically detect the serial number (for example: DCATCY141082), State representatives connection status bar turns blue. Not connected display. Detected inconsistent with the actual SN possible, but does not affect the refresh firmware.
Step 3
Manually select the correct model, there is no drop-down menu, and on behalf of Asus Flashtool is not supported; model forget if elected, you will be prompted
Step 4
*Select whether empty user data, Yes on behalf empty, No representative of any default No, please choose according to the actual situation.
*Click on the box icon, select the path to the firmware raw file. DownLoad Raw File From here
*Click again, you need to update the machine, serial number, and blue State status bar.
*The start point Start icon to start the firmware update.
Step 5
*Flash process, the phone will appear black, is a normal, over a period of time will automatically display
*Success, Asus Flashtool will show below, the system will automatically reboot into the phone (entire process takes about 6.5 minutes)
XDA:DevDB Information
ASUS FLASH TOOL 2.0, Tool/Utility for all devices (see above for details)
Contributors
adithyan25
Version Information
Status: Beta
Created 2016-03-04
Last Updated 2016-03-04

Program runtime error
My phone model is ze601kl, connected to the computer to open the Asus Flash Tool 2.0, the error message when run the program.
can't build adb commander!

fake?
ifreenet said:
My phone model is ze601kl, connected to the computer to open the Asus Flash Tool 2.0, the error message when run the program.
can't build adb commander!
Click to expand...
Click to collapse
probabbly is a fake

ifreenet said:
My phone model is ze601kl, connected to the computer to open the Asus Flash Tool 2.0, the error message when run the program.
can't build adb commander!
Click to expand...
Click to collapse
did u installed adb and is your debugging mode on?? and also use given raw file

jokruger said:
probabbly is a fake
Click to expand...
Click to collapse
never judge with out trying... i tried it on Zenfone4 5 6 and wrked like charm

serial number failure
i've done all the instructions but my serial number detected is 123456789ABCDEF (its same to the handphone). Whe i hit the START i got notice that : Check the detected serial number failure (the system cannot find the path specified)
need help please
thank you

Excuse me if I am mistaken, but the tool provided in this thread seems bogus. The linked setup.rar contains Asus Flash Tool 1.0, not 2.0, and it does not autodetect the phone type, and the pulldown menu has only about 6 choices, and does not modern phones like ze551ml. The other Asusu Flash Tool 1.0.0.45 as linked in the below thread seems much more modern! COrrect me if I am wrong.

The download link is for version 1.00 not 2.0 as already posted so I'm closing this up to save anymore confusion
Regards
Sawdoctor