Related
Do we know what commands does the bootloader accept through mtty?
If we find all of them and what each one does, couldn't we be able to revive a bricked device using mtty? <=The main idea belongs to htctouchp
Here is a list of possible commands(we will have to see which are real commands):
Code:
[SIZE="3"][B][U]Command[/U][/B] [B][U]"Usage"[/U][/B] [B][U]Parameters[/U][/B][/SIZE]
1.ESetDsbDBGMSGT
2.ClearDBGMSG
3.ReadExtROM
4.WLANReset
5.SDSelect
6.emapiCountryID
7.emapiINIT
8.emapiWlanMac
9.emapiPwrDwn
10.emapiRead
11.emapiTest
12.emapi
13.getdevinfo
14.ruustart
15.ruurun
16.progress
17.wdata
18.password
19.set
20.SetDebugMethod
21.checksum
22.ResetDevice
23.BTRouting
24.task "Unknown command"
25.lnbs
26.ls
wow!!! another great thread brother .i really hope that some expert can guide us here.
u have not mentioned the 'task' command here. i was also sure that this command didnt exist for elf/elfins. but today i used snoopypro while flashing a ROM and what i saw was 'task 28' when the ruu was just about to finish. after seeing that, i'm confused a bit
PS: this might be useful a bit:
http://wiki.xda-developers.com/index.php?pagename=Hermes_BootLoader
Very nice....
task command does not work for me...
you may want to add "lnbs"
htctouchp said:
wow!!! another great thread brother .i really hope that some expert can guide us here.
u have not mentioned the 'task' command here. i was also sure that this command didnt exist for elf/elfins. but today i used snoopypro while flashing a ROM and what i saw was 'task 28' when the ruu was just about to finish. after seeing that, i'm confused a bit
PS: this might be useful a bit:
http://wiki.xda-developers.com/index.php?pagename=Hermes_BootLoader
Click to expand...
Click to collapse
what is that snoopypro? u can actually see what is being flashed on the device?
hey great going guys. these threads are gonna be rocking helpful for everyone. spl thnx to htctouchp for initiating this idea
is this (http://forum.xda-developers.com/showthread.php?t=379318) something similar?
ababrekar said:
what is that snoopypro? u can actually see what is being flashed on the device?
hey great going guys. these threads are gonna be rocking helpful for everyone. spl thnx to htctouchp for initiating this idea
is this (http://forum.xda-developers.com/showthread.php?t=379318) something similar?
Click to expand...
Click to collapse
snoopy pro is just a usb port sniffer, it will record everything that passes a port. u cant actually see the flashing data, but u can make a log file out of it and after the flashing is over, u can analyze that log file. that post which u've given as reference, does the same thing. it records the session (usblog data) using snoopypro which later on u can open in hex editor. just try it out while flashing a ROM, and analyze the log later on. may be u can also find something useful
Hey guys!
Has anyone used the ls command?
Is it used like:
Code:
>ls
or
Code:
>ls c:\dump.nb
or
>ls \"Storage Card"\dump.nb
I tried the first one and waited,waited,waited...but (1)I got bored and (2)nothing was really downloaded to my pc so aborted You can see what mtty shows right below:
Code:
Cmd>ls
clean up the image temp buffer at 0x8C100000 Length 0x03A00000
BOOTLOAD_PAGE_TABLE_BASE_C_VIRTUAL= 0x8C080000
Clear image temp buffer done .
MTTYDownloadImage
start download
*Edit1:I'm asking for this command because I think it's a way to dump your rom(IPL,SPL,OS,etc.)
*Edit2:I found this nice tool, but it seems it doesn't work for my phone!Could anyone give it a try too and confirm?
Reading through an SPL.nbh file with a hex editor yielded the following known commands (as listed in the first post here):
SetDsbDBGMSGT
ClearDBGMSG
ReadExtROM
WLANReset
SDSelect
emapiCountryID
emapiInit
emapiWlanMac
emapiPwrDwn
emapiRead
emapiTest
emapi
getdevinfo
ruustart
ruurun
progress
wdata
password
set
SetDebugMethod
checksum
ResetDevice
BTRouting
lnbs
ls
Attached is a text file with a copy/paste of the results from issueing these commands in MTTY.
From what I can figure out you can load an NB or NBH file using lnbs or ls, BUT only ony a Super-CID or CID-unlocked device otherwise you get an error
Code:
Not allow operation!
Error : DownloadImage return error (code = 0xFFFFFFFF)
So, bootloader commands issued through MTTY can be ery usefull for retrieving your Device ID and Model ID, and once CID unlocked you could load an image through MTTY instead of using RUUloader etc, but it looks tricky to figure out how to get things working for a CID-locked/bricked device.
Logic would indicate that somewhere in the NBH file would be a checksum relating to the Vendor-ID and/or Device-ID, having an NBH file where the ID and checksum don'y match would result in the 270 error - corrupt image (one could assume).
So, the big question in my mind at the moment is "How can one figure out where the checksum is in the NBH file". If we can figure out the address of where it resides, we could maybe use the checksum command to pull that info back? Then theoretically, to fix a bricked device all we would need to do would be hex-edit the NBH file to replace the vendor-ID and checksum with the correct one for the particular bricked device?
Thoughts/comments from any of our resident experts in USPL etc would be greatly appreciated!
Craig
good effort Craig
but how to revive an Elf(in) stuck in bootloader is still a mystery for most of us. lets hope for the best that someone out of us can unfold this mystery someday
Interesting!!!
Does anybody knows more comands Im searching for a hardreset via MTTY or a Cleaning DOC leaving behind the task 28 cuase in cmd> dont works... only in usb> i used it just once in a G3 HTCwizard then i cant do it anymore.
Maybe "format" command before the CMD>
kokotas said:
Do we know what commands does the bootloader accept through mtty?
If we find all of them and what each one does, couldn't we be able to revive a bricked device using mtty? <=The main idea belongs to htctouchp
Here is a list of possible commands(we will have to see which are real commands):
Code:
[SIZE="3"][B][U]Command[/U][/B] [B][U]"Usage"[/U][/B] [B][U]Parameters[/U][/B][/SIZE]
1.ESetDsbDBGMSGT
2.ClearDBGMSG
3.ReadExtROM
4.WLANReset
5.SDSelect
6.emapiCountryID
7.emapiINIT
8.emapiWlanMac
9.emapiPwrDwn
10.emapiRead
11.emapiTest
12.emapi
13.getdevinfo
14.ruustart
15.ruurun
16.progress
17.wdata
18.password
19.set
20.SetDebugMethod
21.checksum
22.ResetDevice
23.BTRouting
24.task "Unknown command"
25.lnbs
26.ls
Click to expand...
Click to collapse
Hi do you know a command for unlock the CID, because i tried to flash my phone P3300 an his broken, I can enter only in bootloader, every time when I try to intall a rom shows me error 300, so I think I didn't unlock the CID first time! Thank you and sorry for my english
Hi
You mention your device is P3300, this forum is about the Elf/in P3450 and P3452. No surprise it doesn't work ...
Use this link http://forum.xda-developers.com/forumdisplay.php?f=316
Hey there!
I was wondering if anyone that allready has this phone has managed to dump the rom on the phone? Iam asking on behalf of the people at the Diamond forum.. We would like to have our hands on the Android OS..
~D
I think the folks at the diamond forum are playing a joke on you, I don't think anyone at this site has a G1 or a Dream yet. a bunch of us will though, come OCT 22nd.
damnitpud said:
I think the folks at the diamond forum are playing a joke on you, I don't think anyone at this site has a G1 or a Dream yet. a bunch of us will though, come OCT 22nd.
Click to expand...
Click to collapse
I know that.. I just made the thread so that WHEN the device will come out the thread is already made..
Give Me The Dump
while you're at it, could anyone maybe break into a store or possibly google headquarters (whatever is more convenient), get their hands on a g1, dump the rom, and i dunno, make it work perfectly with the kaiser?
say by monday morning?
thanks a bunch.
Man, these Dream forums sound constipated. Take a dump and get over it, people!
ASAP
I will asap since I will need to neuter all the google phone home and that *G.D.M.F'n.* mandatory google login out of it before I use it.
How do you dump the ROM?
I'm sure having the phone in our hands would be the first step.
I think there are people with the G1 who might do a dump if they knew how.
G1 is still in limited quantity. Must wait some time for rom dump tools.
Found A Dump File!!!!!!!!!
http://forum.xda-developers.com/forumdisplay.php?f=448
http://groups.google.com/group/android-developers/browse_thread/thread/277a73b32a02f26a?hl=en
ryanbradley said:
http://forum.xda-developers.com/forumdisplay.php?f=448
http://groups.google.com/group/android-developers/browse_thread/thread/277a73b32a02f26a?hl=en
Click to expand...
Click to collapse
I dont think this is wat we are looking for...
Its already a year old, and its not a dump from the G1 but 1 from the emulator...
Guys, I am a T-Mobile employee and I went to the event in New York. Its not surprising for somebody to have the phone right now, but luckily somebody who reads the forums haves one!!
I used to follow the Kaisers ROM development until I sold it. Now I have the G1
I will gladly dump the rom and help this community if somebody told me how to do so.
Reply to this message and please send me a email to [email protected] with instructions on how to do it and I will do it tonight EST after work.
Thanks!
raymondf13 said:
Guys, I am a T-Mobile employee and I went to the event in New York. Its not surprising for somebody to have the phone right now, but luckily somebody who reads the forums haves one!!
I used to follow the Kaisers ROM development until I sold it. Now I have the G1
I will gladly dump the rom and help this community if somebody told me how to do so.
Reply to this message and please send me a email to [email protected] with instructions on how to do it and I will do it tonight EST after work.
Thanks!
Click to expand...
Click to collapse
I think if you ues the ADB tool in the android SDK it should be
Code:
adb shell mount
adb shell dd if=/dev/???? of=/sdcard/fs.bin
Whatever mount lists is what you would put in for ???? in the dd if
I also have one (preproduction model/debug model), I'm not sure how exactly to use the adb tool. Anyone care to enlighten me?
Valicore said:
I also have one (preproduction model/debug model), I'm not sure how exactly to use the adb tool. Anyone care to enlighten me?
Click to expand...
Click to collapse
you use it from the cmd prompt and it's in the tool folder in the SDK....
I get the impression that a less 'technical' response would be your best shot here if you're serious that you want a copy of the Android o/s dump
As in (if this were me....a complete 'non-tech' type) a response involving *zero assumed tech knowledge*......eg 'Whats' an SKD???'...or.....'cmd prompt??, where?/how?'
So....
1. Plug phone into PC and start activesynch[or whatever]
2. File explorer and search for file *.*....
Just for example.....
Just trying to make a suggestion that's all - speaking from the point of being a complete tech fkwit myself....and also being ridiculously eager to have Android delivered to all the tech genii here so I can hopefully get it on my Diamond (and soon to have HD as well!)
The SDK is the developer's kit that you can download from Google. It contains a number of tools for use in developing applications for the platform, among them an emulator (for testing apps as if you're on a real android phone) and the ADB tool for accessing the hardware over a USB connection.
The ADB tool is run on the command line (no graphical interface). That's usually a bash prompt found in any console/konsole/terminal in Linux or by running cmd.exe in Windows. It allows the user to execute standard linux shell commands on the phone's filesystem.
Code:
C:/>adb shell ls
For example, the above command runs adb, tells it to issue the "ls" shell command, which gives a directory file listing (similar to the "dir" command in DOS.
Anything beyond that is above my head as of yet, since I don't have any Android hardware to use the tools on.
I can see we're never going to get a ROM dump, not at this rate...
I have no clue how to do it either, nor do I have a G1, but I'm reading your instructions anyways and it still doesn't make sense.
Why can't anyone just post exact step by step instructions? Preferably not using abbriviations or acronyms for 90% of the words.
Also he asked that the instructions be emailed to him.
MODS - can you please move this thread to the sapphire development forum and stick it? thanks
_______________________________________________________________
WE HAVE A ROOT NOW
haykuro said:
GOT ROOT?
http://droiddeveloper.com/hrbuilds/boot-new.img.zip
1. download this, extract boot-new.img to your computer.
2. place your device into bootloader mode (BACK+POWER, or VOLUME DOWN+POWER)
3. fastboot boot boot-new.img
4. wait for device to boot
5. adb push boot-new.img /sdcard/boot-new.img
6. adb shell flash_image boot /sdcard/boot-new.img
that's it!
your device now has root via adb shell.
i'm making the rooted recovery.img now for magic
Click to expand...
Click to collapse
It shouldn't be too hard.
Viper only needs to update his QMAT for creaatin goldcards for the Magic.
Then you have to flash the RC29 nbh with it.
If only adb successes connecting to the magic with rc29 of g1, you can start telnetd.
Then you should be able to. Flash a custom recovery image to flash a modified cupcake.
maxisma said:
It shouldn't be too hard.
Viper only needs to update his QMAT for creaatin goldcards for the Magic.
Then you have to flash the RC29 nbh with it.
If only adb successes connecting to the magic with rc29 of g1, you can start telnetd.
Then you should be able to. Flash a custom recovery image to flash a modified cupcake.
Click to expand...
Click to collapse
Well, you see what I meant? all the expert are here!
Let's wait for Viper comment and/or ideas.
But one problem:
I don't know if the RC29 is compatible with the Magic. Maybe someone has to create a custom .nbh with customized drivers for the magic.
And please. Don't call me an expert
It's only an idea I know linux commands etc. But i know only some basics of programming (e.g. to make a DOS caluclator in C++ )
maxisma said:
But one problem:
I don't know if the RC29 is compatible with the Magic. Maybe someone has to create a custom .nbh with customized drivers for the magic.
And please. Don't call me an expert
It's only an idea I know linux commands etc. But i know only some basics of programming (e.g. to make a DOS caluclator in C++ )
Click to expand...
Click to collapse
I am far from being an expert but even if RC29 works and the DREAM test recovery works (which I doubt), it has no support for virtual keyboard, so right after he gets root he will need a hacked rooted ROM for the Magic. Isn't it safe to assume that until someone cook a special ROM for the Magic he is stuck with a rooted but unusable device?
A much bigger problem: how in the hell can you telnet in the Magic with no keyboard? Or even get past the setup wizard? In other words, even with RC29 there'll be no way to get root or even use the phone. This is gonna be a hell of a lot more difficult than it was for the G1(and it was pretty damn difficult for that)
Well, I guess HTC created this function for their reasons (tests etc.) and now it's only a matter of time until someone will find the way to do it too.
that's the reasone I posted the request, I seen things in XDA that i could never believe before, let's hope it'll happen again ...
Will this post help? http://www.codeandroid.org/forum/?wpforumaction=viewtopic&t=9.2
The guy pk detailed a 27 step, step-by-step guide to unlock those HTC Dream outside UK and US. Hope it helps.
chuazy said:
Will this post help? http://www.codeandroid.org/forum/?wpforumaction=viewtopic&t=9.2
The guy pk detailed a 27 step, step-by-step guide to unlock those HTC Dream outside UK and US. Hope it helps.
Click to expand...
Click to collapse
"2) Launch Terminal Emulator
3) Enter the following:
cd /sys/class/mmc_host/mmc1:*"
Terminal Emulator doesn't seem to work without hardware keyboard(doesn't bring up vk for me on G1 using cupcake, I'd imagine it wouldn't work on magic either). Speaking of which, you guys with Magic's wouldn't be able to use any of the recovery mode options either since those all require a hw keyboard. So even if you got a JF build you wouldn't be able to flash it.
[email protected] said:
"2) Launch Terminal Emulator
3) Enter the following:
cd /sys/class/mmc_host/mmc1:*"
Terminal Emulator doesn't seem to work without hardware keyboard(doesn't bring up vk for me on G1 using cupcake, I'd imagine it wouldn't work on magic either). Speaking of which, you guys with Magic's wouldn't be able to use any of the recovery mode options either since those all require a hw keyboard. So even if you got a JF build you wouldn't be able to flash it.
Click to expand...
Click to collapse
But you do understand this function must be exist right? even if you can't find it now, HTC created it because they do use the recovery mode options for test and stuff...
avimak said:
But you do understand this function must be exist right? even if you can't find it now, HTC created it because they do use the recovery mode options for test and stuff...
Click to expand...
Click to collapse
Unless they do so using some external hardware which is fully possible...(think external keyboard, possibly through extUSB)
EDIT: btw: not trying to be an ass or say that you guys are screwed, just pointing out problems that will need to be solved in order for this to work.
[email protected] said:
Unless they do so using some external hardware which is fully possible...(think external keyboard, possibly through extUSB)
EDIT: btw: not trying to be an ass or say that you guys are screwed, just pointing out problems that will need to be solved in order for this to work.
Click to expand...
Click to collapse
Well, if external USB keyboard is the only thing it takes to root my device - I'll buy one, and root the rest of the Magic Israeli users for free
You don't need a virtual keyboard.
If USB-Connection an ADB wworks, you can get in the hidden root shell by using adb shell with the sdk-tools.
maxisma said:
You don't need a virtual keyboard.
If USB-Connection an ADB wworks, you can get in the hidden root shell by using adb shell with the sdk-tools.
Click to expand...
Click to collapse
I got it:
$ (I can write stuff)...
what next?
@avimak:
You mean, you've connected your magic with installed rc29?
maxisma said:
@avimak:
You mean, you've connected your magic with installed rc29?
Click to expand...
Click to collapse
No, I have the Magic (vodafone version) connected to my PC (win xp) and I can run ADB shell.
avimak said:
No, I have the Magic (vodafone version) connected to my PC (win xp) and I can run ADB shell.
Click to expand...
Click to collapse
ok.
But i meant someone has to test if a magic downgraded to rc29 (via goldcard) works.
Not the orig. Firmware.
maxisma said:
You don't need a virtual keyboard.
If USB-Connection an ADB wworks, you can get in the hidden root shell by using adb shell with the sdk-tools.
Click to expand...
Click to collapse
That's true for the terminal once the operating system has started, but they'll be hosed if they ever reach a boot looping problem or need to flash any ROM.
EDIT: Well not if they boot loop on the android screen, but if it loops on the SPL, then they're hosed.
[email protected] said:
That's true for the terminal once the operating system has started, but they'll be hosed if they ever reach a boot looping problem or need to flash any ROM.
EDIT: Well not if they boot loop on the android screen, but if it loops on the SPL, then they're hosed.
Click to expand...
Click to collapse
Can you please write it again in simple words?
It's a bit "pro only" talking. I got my Android yesterday...
maxisma said:
ok.
But i meant someone has to test if a magic downgraded to rc29 (via goldcard) works.
Not the orig. Firmware.
Click to expand...
Click to collapse
There is an option to go back to the orig. version after the downgrade? can I "dump" my OS somewhere and Install it again from SPL if it failed the rc29?
I'm coming from WM - I'm speaking they lang...
Well I know I'm not the only one who got a bad WiMax MAC address after trying to update my WiMax radio image. I should learn to not try and fix things if they aren't broken
If you've gotten the dreaded "00:16:08:00:24:05" MAC address like I did, this guide will help you fix it. You'll need fastboot set up, a NAND unlocked phone with Toast's part 2 method, your correct MAC address for WiMax, and the files below.
FILES:
New radio
New WiMax
You MUST download & flash these again even if you already have. I don't care if you think you already have the right ones, download these. If you don't, don't ask me for help if you use the wrong ones.
STEP 1: Fix MAC
First, get your right MAC address. It can be found under the battery by the WiMax tag, or on your box under the WiMax barcode. It should be 12 digits long, with no colons in it. If it were supposed to be "00:16:08:00:24:05" it would look like 001608002405 on the box. Write that address down with a colon between every two characters to get it in the right format.
Next, boot your phone into fastboot mode. If you don't know how to do this, hold down volume and press power to boot into the bootloader. After it brings up the menu where "FASTBOOT" is highlighted, press power. It should say "FASTBOOT USB" in red where it previously said "HBOOT" in green.
On your PC, open a shell. First off, lets see if you have a bad MAC, run
Code:
fastboot oem wimaxrmac
It should return something like
Code:
INFOcmd_wimaxrmac
INFODev MAC = *Your MAC address will be here*
OKAY
If it doesn't match the code you wrote down, then you have a bad MAC. If it does match the code you wrote, then skip to step 2.
To fix it, you need to run:
Code:
fastboot oem wimaxwmac *Address you wrote down here*
Like if you wanted it to be "00:16:08:00:24:05" then you would run:
Code:
fastboot oem wimaxwmac 00:16:08:00:24:05
It should return something like:
Code:
INFOcmd_wimaxwmac
IFNOWrite OK! MAC = *Address you entered here*
OKAY
Then just run
Code:
fastboot reboot
To reboot back into Android with your correct MAC address.
STEP 2: Flash the images again
Now push those files to your SD card & reboot into recovery.
Once you're in recovery, flash the "evo.2.05.00.06.10.zip" file. Reboot from the menu like it tells you. Once you're in Android, update your Profile & update your PRL.
Now reboot into recovery again, this time flash the "evo.wimax.25641_r01.zip" file. Reboot again from the menu, and guess what. Once again, update your Profile & PRL. Reboot one more time for good measure, and you should have working 4G. I haven't been able to confirm 4G myself, but others have reported it working with my method. My logcat no longer shows any 4G errors and neither does the kernel log, plus all the data now matches how it was before my update, so that leads me to believe it's working.
I wrecked my MAC with the update and fixed it like this, but I haven't had a chance to try out 4G yet since I won't be going into the city where I'll have coverage until Saturday.
Please post here if it works for you or if it isn't clear then just post & I'll try and clear it up.
Regards,
Jesse C.
EDIT: As a few posters had trouble, it came to my attention that you MUST have run Toast's root part 2 image to have access to fastboot oem commands.
EDIT 2: Now full 4G fix.
Thank you so much!
Sent from my PC36100 using XDA App
On it.....!!!!
It's possible this may only update the MAC and not the key, Joshua (unrevoked) told me and a few others that was their main issue.
Let's see what results show.
Hot damn!!!! It works!!!
Neotelos_com said:
It's possible this may only update the MAC and not the key, Joshua (unrevoked) told me and a few others that was their main issue.
Let's see what results show.
Click to expand...
Click to collapse
If it really is the key, we can modify that here too. If we can pull a copy off a working device, we can write it with fastboot too I'm pretty sure
Geniusdog254 said:
If it really is the key, we can modify that here too. If we can pull a copy off a working device, we can write it with fastboot too I'm pretty sure
Click to expand...
Click to collapse
My understanding is the key is specific to each MAC, either way someone reported it works.
We just need people to post their before and after MAC address to confirm.
It does seem there are two variations of the bad MAC from different roms (at least from reports I've heard).
Well i changes the mac....i dont know if 4G is working on it.....
ON XP opening a shell using CMD? I'm not sure how to communicate with my EVO. Been without 4G for a while, trying to get it back up and running.
( waiting for device )
*nevermind*
Sleep..needed badly
Travyevo said:
ON XP opening a shell using CMD? I'm not sure how to communicate with my EVO. Been without 4G for a while, trying to get it back up and running.
Click to expand...
Click to collapse
You need adb from the Android SDK.
You also need to set your phone for USB debugging.
If you look around there's hundreds of tips on doing all this.
asrebel said:
*nevermind*
Sleep..needed badly
Click to expand...
Click to collapse
are you in fastboot?
Neotelos_com said:
My understanding is the key is specific to each MAC, either way someone reported it works.
We just need people to post their before and after MAC address to confirm.
It does seem there are two variations of the bad MAC from different roms (at least from reports I've heard).
Click to expand...
Click to collapse
I saw the same thing. I ended up with the one i posted in the OP but it seems they all start with the 00:16:08 characters.
I don't think its safe to post the after MAC address, sicne it's unique to every device. It won't hurt anything, but I'd rather keep mine private
Neotelos_com said:
You need adb from the Android SDK.
You also need to set your phone for USB debugging.
If you look around there's hundreds of tips on doing all this.
Click to expand...
Click to collapse
ADB appeared to install when i connected it. I'll take a look.
Thanks
my fastboot doesn't seem to recognize the 'oem' command. Is that a function of fastboot?
Anyone 4G back working using this method?
rocolema said:
my fastboot doesn't seem to recognize the 'oem' command. Is that a function of fastboot?
Click to expand...
Click to collapse
Yes. It should work for everyone. Do you have the newest fastboot?
david279 said:
Anyone 4G back working using this method?
Click to expand...
Click to collapse
I thought you said you had it working? Do you not have 4G or did it not fix the 4G errors
It fixed my MAC address. I have no 4G to test to see if thats working.
This is an interesting method.
I have restored my MAC via a different route, but I believe if I were to flash an offical wimax right now, I would lose my MAC again. What I have done requires modification to the wimax.img file.
Does this persist through reboots? If it does, this would likely be the best answer to the problem of the bad mac addresses.
david279 said:
It fixed my MAC address. I have no 4G to test to see if thats working.
Click to expand...
Click to collapse
Ah okay. I'm in the same boat
What will this do?This will install CWM recovery on your bootloader unlocked HTC One XL (AT&T, Rogers, Asia, etc.)
DownloadDownload Tool
Who do I thank?
Don't thank me. Thank Paul O'Brien of MoDaCo for creating a usable recovery image.
Ty ;-)
Sent from my HTC One XL using Tapatalk 2
Is this for windows only?
Justjusten said:
Is this for windows only?
Click to expand...
Click to collapse
Yes right now. If someone wants to create a Mac/Linux version, that'd be awesome.
You can manually install by doing the following:
Code:
adb reboot bootloader
fastboot flash recovery recovery-clockwork-touch-5.8.3.1-evita-modaco.img
fastboot reboot
Justjusten said:
Is this for windows only?
Click to expand...
Click to collapse
yes
Thank you! Also thank you for the -5 Points, lol guess i got what i deserved
Installed works wonders! Thanks!
too bad recovery doesnt work yet for flashing roms....
hmm install now or wait until its 100% what are the benefits for installing now? wow file is 7.2mb took over 8 minutes to download on my comcast 50MBPS internet!! servers must be getting bogged! lol
Works perfectly... thank you!
We definitely need someone that can do these conversions for mac on board. Hard out here for a mac user. LOL
dscottjr81 said:
We definitely need someone that can do these conversions for mac on board. Hard out here for a mac user. LOL
Click to expand...
Click to collapse
Question, if you run virtualized windows in your mac, can you run adb commands and scripts just like it were a PC?
dscottjr81 said:
We definitely need someone that can do these conversions for mac on board. Hard out here for a mac user. LOL
Click to expand...
Click to collapse
Or the mac users can make a dual boot and use windows lol ....*runs and hides*
Sent from my HTC One XL using xda premium
dscottjr81 said:
We definitely need someone that can do these conversions for mac on board. Hard out here for a mac user. LOL
Click to expand...
Click to collapse
It's no harder than for the linux crowd. If you're familiar with Terminal, then adb commands should be second-nature.
That being said, if you look at the contents of the install.bat, you can see which commands are being run. Use those same commands from Terminal on your Mac, assuming you've already setup the Android SDK tools (adb and fastboot).
Here's where you get the Mac SDK: http://developer.android.com/sdk/index.html
You needn't worry about setting up the Eclipse plugin or anything like that. Once you unpack the zip, you should find an "android" binary, which when run, will launch the SDK Manager. From there you select the Android SDK Tools. That will install adb. Select Android SDK Platform Tools and that should install fastboot.
dscottjr81 said:
We definitely need someone that can do these conversions for mac on board. Hard out here for a mac user. LOL
Click to expand...
Click to collapse
Hey stop giving us a bad name, crack that .bat open and show the world your ADB terminal skills.
About to do the same myself.
hey i keep getting remote: signature verify fail. anyone else have this issue, is there a solution for it?
Thanks as usual ! Worked great
thatg said:
hey i keep getting remote: signature verify fail. anyone else have this issue, is there a solution for it?
Click to expand...
Click to collapse
Your device is not bootloader unlocked. Please read the instructions.
kennethpenn said:
Your device is not bootloader unlocked. Please read the instructions.
Click to expand...
Click to collapse
lol whoops sorry, up and running, need me some CM9!!!
Does this give you the ability to nandroid now?