[HOW-TO] Get The Flashing Trackball - myTouch 3G, Magic Android Development

Hi all, all credits go to xordis for the instructions, cyanogen and Amon_RA for their discussion/findings/contributions in this thread: http://forum.xda-developers.com/showthread.php?t=547896
I just created a separate thread as I realised that the file posted by xordis could be used on various other ROMs (probably except HTC-based ones) to get a flashing trackball on an incoming call. Here are the exact instructions by xordis:
xordis said:
Here is the fix for the trackball flashing.
Grab this file
http://members.iinet.net.au/~xordis/files/lights.msm7k.so
adb remount
adb push lights.msm7k.so /system/lib/hw/
adb shell reboot
Worked for me. would like to know if it works for others.
Cyanogen will hopefully include this in the next release if it works.
Click to expand...
Click to collapse
Also, according to Amon_RA there should be 2 versions of lights.msm7k.so as of now, one for 32A (MD5: FBFC8129630F7C517C7999521B015C20), and one for 32B (MD5: E94DDAD629894B0CB01138A58B2CC031). The one posted by xordis has a MD5 value of E94DDAD629894B0CB01138A58B2CC031, but I have tested it on Amon_RA's ROM and it works.
On the other hand, I have also tried pushing lights.msm7k.so from a 32A ROM (MD5: FBFC8129630F7C517C7999521B015C20), and it does not work. My guess is that it is specially compiled for the HTC framework.
Hope it helps some of you. Once again, all credits go to the respective people! Thanks for all the hard work!

Thanks to all who worked on this, this works great

Does anyone know how we could change the color of the trackball? Just out of curiosity.

Breakthecycle2 said:
Does anyone know how we could change the color of the trackball? Just out of curiosity.
Click to expand...
Click to collapse
I was wondering that earlier. I don't think anyone has tackled it.
I know some devices have the ability to show all colors, but by default they just don't.. so it depends if that trackball led can do it, then its just a matter of someone cracking it open and seeing if they can or not.. but i have no idea.

What does this do?
My Trackball already flashes, when receaving a SMS or phonecall?
does this change the pattern of flashing?

zzup said:
What does this do?
My Trackball already flashes, when receaving a SMS or phonecall?
does this change the pattern of flashing?
Click to expand...
Click to collapse
It's for the people who flashed their MT3G with custom rom that does not support trackball blinking. Mine worked after pushing this thanks

briggs81 said:
I was wondering that earlier. I don't think anyone has tackled it.
I know some devices have the ability to show all colors, but by default they just don't.. so it depends if that trackball led can do it, then its just a matter of someone cracking it open and seeing if they can or not.. but i have no idea.
Click to expand...
Click to collapse
Thanks man. Nucks fan, huh?

Got it for 3.9.11.

Breakthecycle2 said:
Thanks man. Nucks fan, huh?
Click to expand...
Click to collapse
;-) ......

were do i put the file at sorry for the dum ? dose it go on the sd

It's explained in the first post of this thread.

tato22 said:
were do i put the file at sorry for the dum ? dose it go on the sd
Click to expand...
Click to collapse
You got to set up the android SDK first (search in xda for it), then make use of adb. Follow the instructions on the first page to continue .

hi all... how do I fastboot this? Is it replacing adb for fastboot? I'd setup and have working the fastboot method instead the adb... Than ks for your help...

Just connect your phone in normal mode and run the adb commands..

Does this enable persistent flashing while there are new notifications, like the flashing ring on the Touch Diamond for example?
I don't find a single flash useful in any way unless I sit and watch for the moment a new message arrives!

MikLSP: It flashes when there's a new email. However, it does not flash when there's a missed call or new sms for me . No idea why..

it worked ...... but there a slight problem..... if a call is misssed. previously ( before rooting ) the track ball used to blink again and again....but after falshing and uploading that trackball falshing update ...... its just blinking for one time....and then its not blinking.....! any ideas......?

pintspin said:
it worked after pushing the attached file to phone ...... but there a slight problem..... if a call is misssed. previously ( before rooting ) the track ball used to blink again and again....but after pushing that trackball update ...... its just blinking for one time....and then its not blinking.....! any ideas......?
Click to expand...
Click to collapse
can any one give me an idea.... about this problem.....!

I have tried moving this file to the stated directory then rebooted, but all it does is get rid of all my LEDs. HTC magic 32b CM6 Froyo

I tried this on my 32A with FroyoRedux 1.5 and it caused reboots, plus it blinked non stop...

Related

(Update 32B) cm-recovery-1.4-32A.img

Hi I am new to this forum. but i have made a mew recoveryfile based on cynaogen's latest version. Whats new read http://forum.xda-developers.com/showthread.php?t=523558
I have uploaded to RapidShare but it is only 10 downloads so if anyone can find another place it is god.
Here is the file http://rapidshare.com/files/261114426/cm-recovery-1.4-32A.img.html
Hope it works well for everyone
I have made a new downlod link. Get it here http://www.2shared.com/file/6888950/23092494/cm-recovery-14-32A.html
Okay I have made a version for the 32B phones. I can't test it as I do not have that phone , but here is the file http://www.2shared.com/file/6891840/7bb819d8/cm-recovery-14-32B.html
Test it at your one risk, an dthe consol menu don't work as we don't have a keyboard.
Good testing.
works great... super tool..
I've grabbed it and put it up on a non-limited Rapidshare account, for those who prefer it:
http://rapidshare.com/files/261143874/cm-recovery-1.4-32A.img
the new CM recovery 1.4 is great on the g1. nice to see it ported over. but how about a port for the 32B? thanks
will work for magic 31A,right...?
thx
penguin724 said:
will work for magic 31A,right...?
thx
Click to expand...
Click to collapse
Read the first post in this thread carefully again.
MagicDK said:
Okay I have made a version for the 32B phones. I can't test it as I do not have that phone , but here is the file http://www.2shared.com/file/6891840/7bb819d8/cm-recovery-14-32B.html
Click to expand...
Click to collapse
Tried this on my 32b magic and I couldn't get it to boot at all.
Cheers
Can you test this one http://www.2shared.com/file/6896179/bb4ff189/cm-recovery-14a-32B.html I hope that it will fix the problem.
MagicDK said:
Can you test this one http://www.2shared.com/file/6896179/bb4ff189/cm-recovery-14a-32B.html I hope that it will fix the problem.
Click to expand...
Click to collapse
Nope no luck with that one. Tried different ways of loading it but just wont boot.
njakobs said:
Nope no luck with that one. Tried different ways of loading it but just wont boot.
Click to expand...
Click to collapse
Okay a last one http://www.2shared.com/file/6897314/289c99b9/cm-recovery-14b-32B.html
MagicDK said:
Okay a last one http://www.2shared.com/file/6897314/289c99b9/cm-recovery-14b-32B.html
Click to expand...
Click to collapse
Not sure why you made a 32B version, the dream version will boot fine on the a 32B magic...
Amon_RA said:
Not sure why you made a 32B version, the dream version will boot fine on the a 32B magic...
Click to expand...
Click to collapse
Okay that I did not realise and one in the thread requestet it, but now I know, thanks.
And thank you for a great guide. It was your guide I have been looking at as I made my first images.
This may not be news to the experts
I confirmed that dream's recovery image file work just fine for the 32B (ION)
help me please!!
hi to everybody, i've a problem with my htc magic 32B: i tried to flash the new recovery img by cynogen with these comands
adb push recovery-new.img /sdcard/recovery-new.img
adb shell flash_image recovery /sdcard/recovery-new.img
adb remount
and now, when i try starting my magic in fastboot mode (red button and home) it stops to the red screen "vodafone"...
can anyone help me??!!
PS: sorry about my english....
the fastboot mode is by holding the back and the power buttom....
that's the problem!!! thanck you!!! you saved my magic!!!
Does anyone know if this will work on an obviously non rooted MyTouch?
Breakthecycle2 said:
Does anyone know if this will work on an obviously non rooted MyTouch?
Click to expand...
Click to collapse
Does anyone know?
Breakthecycle2 said:
Does anyone know?
Click to expand...
Click to collapse
No, it will not work. You'll probably not be able to fastboot an image...
cm-recovery-1.4.img : BUG/Feature
Sapphire 32B
Update any zip file: Only works for files in the root of the sdcard folder!!
Either this is was meant to be this way, in that case would be nice to have a version which could read from a folder. Crowds the root folder with too many rom files.
Or it is a bug which needs to be fixed.
Rest works great!!!!

Flash with 'shav3d-991.nbh' without "ROMUpdateUtility"

I'm already HARDSPL'd and have already flashed with one ROM. Want to try out or 2 more.... I got the 'shav3d-991.nbh' from a link from from these forums. It didn't come with the usual 4 or 5 other files....
klokwyze said:
I'm already HARDSPL'd and have already flashed with one ROM. Want to try out or 2 more.... I got the 'shav3d-991.nbh' from a link from from these forums. It didn't come with the usual 4 or 5 other files....
Click to expand...
Click to collapse
Just place this nbh file in the same folder as the ROM you have now and delete the other ROM after that. Then run the utility.
I placed it in the folder I HARDSPL'd with, but it gave me a connection error. I'll try it out if my current choice, JustHomeAlpha, doesn't work out. It seems like exactly what I was looking for though. You guys are awesome. =P
klokwyze said:
I placed it in the folder I HARDSPL'd with, but it gave me a connection error. I'll try it out if my current choice, JustHomeAlpha, doesn't work out. It seems like exactly what I was looking for though. You guys are awesome. =P
Click to expand...
Click to collapse
Make sure that when you are flashing through ROM Update Utility that you are higher than 75% battery.
Also, you can flash at the TRI-Colored Screen - Holding camera button in while pressing the soft reset button in with your stylus. Keep holding in the camera button until you get to a screen that is multi-colored - Then you can run the ROMUpdateUtility too.

[FIXED] Downgrading HBOOT to 0.80 from 0.92

Ok so this issue has now been fixed, download the following file and place it on your SD card, start your phone up with, volume down + power and follow the instructions.
PB99IMG.zip
Thanks to everybody who tweeted this in.
o.o adamg - not really! Why did you do that?
That could not mean the end of opendesire and your sense roms could it?
Adam you should have known better, but still look at root method now on my gf's desire will post when I get root
ohh crap i was holding out hoping you'd have an update. hope someone figures it out for your sake if any
I will still be releasing, I have people on the team who test the roms and report the bug errors for me to fix
I will still be releasing, I have people on the team who test the roms and report the bug errors for me to fix
Click to expand...
Click to collapse
If need more help testing email me I'm global mod on villainrom.co.uk
Email [email protected]
Lots of experience
Cheers
Mike
any chance of getting a full root while were at it? it would be awesome to use metamorph
i'm sorry to hear that adam,
but i seriously lol ...... so sorry.
i love your roms.
i got the same problem
http://htcpedia.com/forum/showthread.php?t=2934
Prema999 said:
http://htcpedia.com/forum/showthread.php?t=2934
Click to expand...
Click to collapse
Not possible because you need root to place the flash-executable and the img into a read only directory.
Tried it too but you definitly need a method to execute some lines of code. adb push to /data is not possible because:
- adb is not working
- you can't get root to remount /data rw instead of ro.
Before i flash anything... How did you get there?? Flashed new 2.2 ROM? Or RADIO? or????
after we upgraded the official version throw htc live update
And this?
Isn't it possible to hex edit the version string to trick it into believing it is a newer version?
Prema999 said:
http://htcpedia.com/forum/showthread.php?t=2934
Click to expand...
Click to collapse
twicejr said:
Isn't it possible to hex edit the version string to trick it into believing it is a newer version?
Click to expand...
Click to collapse
that's not so easy, i think it is nearly impossible, you can't hex edit something on a read only phone (if we could edit sth we could flash the 0.80 hboot back), and hex-editing the whole RUU is - as i think - because of encryption and checksum checks etc impossible, too. we have to inject the flash software and the image - and this is impossible without rw / root.
wiggy2k said:
that's not so easy, i think it is nearly impossible, you can't hex edit something on a read only phone (if we could edit sth we could flash the 0.80 hboot back), and hex-editing the whole RUU is - as i think - because of encryption and checksum checks etc impossible, too. we have to inject the flash software and the image - and this is impossible without rw / root.
Click to expand...
Click to collapse
damn you htc
madman_cro said:
damn you htc
Click to expand...
Click to collapse
I think there WILL be a root-hack. it is just a cat and mouse game, htc is now in front, but the dev scene will be back soon with successful rooting i think. so dont fear and be patient
the only hardware which was not exploit-hacked for now is the playstation 3. (I hate not having otherOS anymore ...)
yes should they come with a new release because all the new htc devices will come with 0.92 at least
Adam, get on Freenode IRC and query me.
There's a few things I'd like to test with you
(IRC nick = IEF)
same problem impossible to downagrad hboot or install "RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4.06.00.02_2_release_126984_signed"

[HOW TO] Flash Froyo without loosing downgradability and keeping cam flash

Thought I'd better post this before everyone flashes these sbfs and looses downgradability (is that a word?)
So as you may have worked out this process is if you have never flashed a non downgradable .sbf i.e you have never flashed 2.51 eclair or the 2.2 GB/US 2.2 froyo. If you flashed these then this won't work for you and youve lost downgrability.
Follow the process below, This works with the TMobile US and The GB 3.4.2 Firmwares.
It may seem long winded, but it is the only way to get it running with everything working ok and still downgradable/able to flash other .sbf, most notably the cam flash working 100% - fully sync'd and no greeny blue tinge to it.
Need the Chinese 2.2 release – Download Here
Need the system.img nandroid and boot/devtree.sbf – Download here
Also now added the GB system image+md5 - the one that racca added in the original thread. Download hear
• Flash the Chinese .sbf by RSD lite
• Once booted root via superoneclick http://bit.ly/gUzV19 then reboot (make site debugging on)
• Install Clockworkmod recovery app http://bit.ly/dOdhKc , open app, install recovery and then boot into recovery (make sure debugging is off whenever you boot into recovery
• Wipe data/cache in recovery
• Flash the Tmob 3.42 system image(pre rooted) via advanced restore (folder need to be put in goapkrev/backup folder)
• Once restored pull battery, put battery back in while holding up to get into bootloader
• Flash the boot/devtree.sbf once its rebooted after this you are done.
If you want to use the GB release then just restore the system.img from the GB release.
Enjoy and don't get locked in peoples.
Thanks to adlx whom I enjoyed working with to figure this out - team effort! +as always Sorensiim for the hosting!
I don't think you actually need to flash anything other than boot/devtree.
I tried TMO with uk2.51 and it was just fine.
And if someone followed your post exactly as it is now. Chances are they'd
get their phone bricked (since many are already on 2.51).
Easy to fix for sure, but since it is most likely meant for less experienced
users, we really don't want that, right?
BTW
Thanks for writing it up.
Quick question for you Higgsy...
On one of the original T-Mobile Froyo threads, you posted update files to bypass the Motoblur Setup ("Skip_Blur_adlx-signed" worked fantastically...much thanks!).
Are those modifications included in these posted files already?
EDIT: Went ahead and tried it both with and without the update. Answer is that you cannot skip Moto Setup with this install; however, the Skip_Blue_adlx-signed update will allow you to if the update is applied before leaving recovery.
EDIT: Credit goes to adlx, as it was his file (mis-remembered...should have known better from the file name though). Using Higgsy's instructions and links and adlx's update, I now have a working working US 3.42 with the Motoblur setup bypassed. Thanks to all those who made that possible.
sorry to bother, but as I am now having the green light problem after flashing the "flash fix" several weeks ago, can I get the normal flash back using this method?
and thank you for your work....
conradlyn said:
sorry to bother, but as I am now having the green light problem after flashing the "flash fix" several weeks ago, can I get the normal flash back using this method?
and thank you for your work....
Click to expand...
Click to collapse
No you can't. Nandroid backup and/or SBF won't do anything on that front.
As I am on the UK sbf, this will not be of much use to me. Thankfully, I have no issues with that sbf, so I do not need this.
That said, thank you from those who do.
racca said:
No you can't. Nandroid backup and/or SBF won't do anything on that front.
Click to expand...
Click to collapse
what do you mean by "on that front"?
means that fix package consists some fundamental codes that had thoroughly change the hardware control? and nandroid backup as well as SBF could not overwrite that part?
Forgot to put in the post this is if you have not flashed a non downgradable .sbf before, although I would have thought people would be able to work that out by the nature of the thread.
This will work and will fix you cam flash if you are coming from 2.21+2.35 Eclair ROMs or 2.2 Chinese ROM where you haven't flashed a non downgradable .sbf
Higgsy said:
If you want to use the GB release then just restore the system.img from the GB release.
Click to expand...
Click to collapse
Can you provide a link to that image?
Raccroc said:
Quick question for you Higgsy...
On one of the original T-Mobile Froyo threads, you posted update files to bypass the Motoblur Setup ("Skip_Blur_adlx-signed" worked fantastically...much thanks!).
Are those modifications included in these posted files already?
EDIT: Went ahead and tried it both with and without the update. Answer is that you cannot skip Moto Setup with this install; however, the Skip_Blue_adlx-signed update will allow you to if the update is applied before leaving recovery.
Click to expand...
Click to collapse
I never posted that! and I never used that fix! On the US 3.4.2 you can't skip setup, on the GB 3.4.2 you can skip set up.
conradlyn said:
sorry to bother, but as I am now having the green light problem after flashing the "flash fix" several weeks ago, can I get the normal flash back using this method?
and thank you for your work....
Click to expand...
Click to collapse
If you never installed a non downgradable sbf as per the updated op then yes.
racca said:
No you can't. Nandroid backup and/or SBF won't do anything on that front.
Click to expand...
Click to collapse
appriciate you helping people mate, but let me answer the questions that people have on a procedure that I have written #justsayin
Raccroc said:
On one of the original T-Mobile Froyo threads, you posted update files to bypass the Motoblur Setup ("Skip_Blur_adlx-signed" worked fantastically...much thanks!).
Are those modifications included in these posted files already?
EDIT: Went ahead and tried it both with and without the update. Answer is that you cannot skip Moto Setup with this install; however, the Skip_Blue_adlx-signed update will allow you to if the update is applied before leaving recovery.
Click to expand...
Click to collapse
I think I did post this Skip_Blur_adlx-signed, as I'm adlx lol (although I'm registred here as adlxdum). And yes, it has to be flashed RIEGHT AFTER restoring the nandroid, as I stated. (I can't find the post...)
EDIT: was http://forum.xda-developers.com/showpost.php?p=10930470&postcount=149
Thanks mate, my DEFY is perfect now.
Muznyu said:
Thanks mate, my DEFY is perfect now.
Click to expand...
Click to collapse
Whoop!!!!!!!!!!!!!!!!!!!!!!
Higgsy said:
If you never installed a non downgradable sbf as per the updated op then yes.
Click to expand...
Click to collapse
too bad that you didn't mention this when the post was originally created. when i see this answer, my defy has already been stuffed with 2.2 GB.
conradlyn said:
too bad that you didn't mention this when post was originally created. when i see this answer, my defy has already been stuffed with 2.2 GB.
Click to expand...
Click to collapse
My advice to anyone when something new comes out (not that its any consolation I'm sorry) is to sit back and watch how things pan out, rather than jumping in.
Higgsy said:
My advice to anyone when something new comes out (not that its any consolation I'm sorry) is to sit back and watch how things pan out, rather than jumping in.
Click to expand...
Click to collapse
i also tried to hold on to this rule even before i bought my defy, but just can't reject the temptation of new ROMs...
you couldn't imagine how much i hate myself now, damn!
i could only pray for a real fix on the flash light by great guys like you, Higgsy
Higgsy said:
appriciate you helping people mate, but let me answer the questions that people have on a procedure that I have written #justsayin
Click to expand...
Click to collapse
I might have misread the question
What I meant was that this is not likely to fix the green light problem,
which is not what's asked obviously.
racca said:
I might have misread the question
What I meant was that this is not likely to fix the green light problem,
which is not what's asked obviously.
Click to expand...
Click to collapse
It does fix the green light problem, I wouldn't have posted it if I hadn't spent hors testing to find a fix for the problem lol
Higgsy said:
It does fix the green light problem, I wouldn't have posted it if I hadn't spent hors testing to find a fix for the problem lol
Click to expand...
Click to collapse
man, it is astonishing to see that it does fix, it seems that the green light indeed could be fix. but how?
is it only can be done by your operation procedure, or some independent files could be ported and flashed to fix?
Thanks a lot Higgsy. I'll try your turorial. Could I translate your topic to put it on a French forum ? (i'll put a link to the original thread)

[RECOVERY] DEFY ClockworkMod Recovery - 2.5.1.8

Hi all,
Rumor has it I picked up a DEFY last week. Most people in the community know me for my work on the cliq/backflip/cliqxt. It's been quite some time since I posted any mods/work here on XDA so here we go. First I'd like to say thanks to Koush & Tenfar for the work they've done. They laid the ground work. I simply needed/wanted to improve on it more. I wanted to include the latest 2.5.1.x version since it has some bug fixes/new features also. So here you go. This recovery includes the latest 2.5.1.8 ClockworkMod Recovery, fixed fix_permssions script, and updated adb that allows root access when using adb shell. All your backups, downloads will reside in the clockworkmod directory on your sdcard just like a standard clockworkmod recovery. If you haven't noticed the fix_permissions script don't run properly via the recovery on the DroidX/Droid2/Defy. I simply fixed the script so it does work properly. Thanks again to both Koush & Tenfar. I'm looking into resolving the problem when you have USB debugging enabled you can't boot into recovery mode properly. This release still has that issue, just FYI. If you choose to use this version over Tenfar's, you'll need to un-install his version, install this one, & choose the option to install recovery once. After that, it's works the same way. Take care.
UPDATE: I've uploaded a new version to my 4shared as well as included it here. This new version simply adds a power off option to the menu & was a quick attempt to try to resolve the USB debugging option. I'll give it another try when I have time, until then, I hope you like having the option to power off your Defy from the recovery menu. I've also provided a link to the original version. Take care.
Steve, kb7sqi
Edit: Due to requests, I'm re-adding the link for this updated version. While I do have plans to come back to #android soon, until then, this will be unsupported by me till then. I'm glad it's been useful to others. Take care.
Latest Version:
Older version:
http://goo.gl/NtsTV
Steve
Great work! Will try it out asap.
installed seems to be working fine btw whats key test?
S1dew1nder said:
installed seems to be working fine btw whats key test?
Click to expand...
Click to collapse
It's does exactly what it sounds like. It simply returns the "key" value when you touch keys/buttons on your phone. It's handy if you're wanting to update a recovery to use certain keys if your phone has them. Perfect example, on the cliqxt the phone has a touch pad. So in the version I created for it, instead of needing to use the volume up/down, you could also use the touchpad for up/down/select as well. Take care.
Steve
kb7sqi said:
It's does exactly what it sounds like. It simply returns the "key" value when you touch keys/buttons on your phone. It's handy if you're wanting to update a recovery to use certain keys if your phone has them. Perfect example, on the cliqxt the phone has a touch pad. So in the version I created for it, instead of needing to use the volume up/down, you could also use the touchpad for up/down/select as well. Take care.
Steve
Click to expand...
Click to collapse
thanks for the answer dude, just did a back up with it all went well only diff was it made a new folder btw it will restore older back ups right?
kb7sqi said:
It's does exactly what it sounds like. It simply returns the "key" value when you touch keys/buttons on your phone. It's handy if you're wanting to update a recovery to use certain keys if your phone has them. Perfect example, on the cliqxt the phone has a touch pad. So in the version I created for it, instead of needing to use the volume up/down, you could also use the touchpad for up/down/select as well. Take care.
Steve
Click to expand...
Click to collapse
How can I can quit key test?
Power+VolUp results in a black screen.
pull the bat?
S1dew1nder said:
pull the bat?
Click to expand...
Click to collapse
that's what i did. but would've been nice to have long press (power button) to quit instead of battery-pull.
Ah, well, wouldn't need to use it twice anyway.
I'm gonna try restoring an older img, report back in a few.
S1dew1nder said:
thanks for the answer dude, just did a back up with it all went well only diff was it made a new folder btw it will restore older back ups right?
Click to expand...
Click to collapse
Yeah, you should be able to restore other nandroid backups.
racca said:
How can I can quit key test?
Power+VolUp results in a black screen.
Click to expand...
Click to collapse
You guys do know you don't have to pull the battery out right? You can hold down volume down button & hit the power button to turn the phone off while in the recovery. When you power the phone on, it'll boot up like normal. Take care.
Steve
Restore doesn't work. "can't find directory"
I will switch back to the old version
Andy
morphin said:
Restore doesn't work. "can't find directory"
I will switch back to the old version
Andy
Click to expand...
Click to collapse
try renaming the goapkrev folder on your sdcard to clockworkmod it should be able to find the directory then
S1dew1nder said:
try renaming the goapkrev folder on your sdcard to clockworkmod it should be able to find the directory then
Click to expand...
Click to collapse
You took the words right out of my mouth. I was just getting ready to type that. lol Thanks!
Steve
kb7sqi said:
You guys do know you don't have to pull the battery out right? You can hold down volume down button & hit the power button to turn the phone off while in the recovery. When you power the phone on, it'll boot up like normal. Take care.
Steve
Click to expand...
Click to collapse
ahhhhhh, i tried power+volup
thanks for the refreshment, and again for the great work!
now if only we can be rid of the annoying "debugging" bug.
racca said:
ahhhhhh, i tried power+volup
thanks for the refreshment, and again for the great work!
now if only we can be rid of the annoying "debugging" bug.
Click to expand...
Click to collapse
Thanks. I'm working on it. I got a little tired of rebooting my defy over 100 times yesterday when I was working on this. lol After I get my version done for the Motorola Charm, I'll get back to working on that.
Steve
kb7sqi said:
You took the words right out of my mouth. I was just getting ready to type that. lol Thanks!
Steve
Click to expand...
Click to collapse
lol np bud, btw is there any way to rename backup folders with out having a md5 miss match error?
S1dew1nder said:
lol np bud, btw is there any way to rename backup folders with out having a md5 miss match error?
Click to expand...
Click to collapse
i have no such problem ever. renaming always works and no such info is stored in the md5 file
do you think it could of happened because i edited the file name via my computer while my phone was in usb mass storage mode?
kb7sqi said:
Thanks. I'm working on it. I got a little tired of rebooting my defy over 100 times yesterday when I was working on this. lol After I get my version done for the Motorola Charm, I'll get back to working on that.
Steve
Click to expand...
Click to collapse
no pressure then, it's fine as it is.
i just need to remember, like really hard, to turn it off.
i wish i didn't make the same mistake not turning it off over and over again
S1dew1nder said:
do you think it could of happened because i edited the file name via my computer while my phone was in usb mass storage mode?
Click to expand...
Click to collapse
It's a good chance that could've caused it. I've had some wierd stuff happen doing things like that when in usb mass storage mode.

Categories

Resources