yashsingh1/xdaforums huggingface dataset:
[Motorola Droid and Milestone Themes and Apps] vmani:
I have modded my milestone with G.O.T 1.10 and its great thanks to the GOT theme

problems i am facing with G.O.T

Physical Keyboard Not working

Volume Roker(volume + -) button not working

Camera button not functioning.

What I did before Modding my milestone :

*rooted my milestone

*installed Droidx Keyboard by replacing the stock app using ROOT EXPLORER

*tried reinstalling the stock android keyboard by copying the LatinIME.apk( I forgot to backup stock apk i downloaded it from internet ..)failed attempt !! dint work"application installation failed!!!"

*After reboot and factory wipe my milestone ended in BLACK SCREEN with an error message "process com.android.inputmethod.latin has stopped working .."force closed the application

*At the end as a solution for this i flashed my milestone with vulnerable sbf file and modded my milestone with G.O.T V1.10 and now i am stuck with the problems in the starting of this thread

I cant blame G.O.T because mistake is on my side

can any 1 please help me in overcoming the above mentioned problems !!

kindly help me :D
[Galaxy S I9000 Q&A, Help & Troubleshooting] articoceanic:
could somone help me out with these questions.

1) i have a 3g samsung galaxy 2.1 rooted, do i need to unroot it before i update to froyo? if i update it to froyo without unrooting it will it mess the phone up?

2) also if i update it, will all my apps stay or will they disappear and need to be reinstalled again?

3) lastly does the official samsung galaxy froyo update fix the lag issues?

thanks to anyone who can answer these questions, can't seem to find the answers on the thread.
[Galaxy S I9000 Q&A, Help & Troubleshooting] bigdyl69:
1) I think you can update without removing the root but just to be safe I'd remove it.

2) If you update the official way (through Kies) you should keep all your apps

3) The lag is almost gone, it's certainly a lot more responsive than the Eclair releases but many people still use a lagfix anyway (I use OCLF v2.2+)
[Galaxy S I9000 Q&A, Help & Troubleshooting] articoceanic:
thanks guess i'll be doing an update soon
[EVO 4G Q&A, Help & Troubleshooting] NinjaPenguin:
Got the 3500MAH battery via ebay yesterday. Plugged it in, ran it all day. Got down to 3 percent when I got home. Plugged it in.. all i get is the amber light blinking, then turning to amber and green blinking. Ok, so i unplugged the charger and let the battery sit out for an hour or so. Maybe it was overheating. Plugged it all back in, same thing and it will not turn on. Tried a different charger, nothing.

I remember seeing something on here a while back, but i can't find it now (yes, even with a google search) about people using 3000-3500MAH batteries and having the same issue but after doing.. something.. everything started working. Couldn't remember what. Any ideas to help me get this thing to charge?
[Desire Android Development] Amon_RA:
Reserved for future use
[Desire Android Development] geminga:
first :P.....

good job, i'll give it a try
[Desire Android Development] mon@diac:
Woow...Great...Thank you very much...the best recovery...

P.S: Great works and so nice CM ver....
[Desire Android Development] shnizlon:
Thanks . Great work ;)
[Desire Android Development] tkm89:
Thank you!
[Desire Android Development] l3zawi:
we like the newest things ... :)

thanx Amon_RA ...
[Desire Android Development] skynapster:
Thank you!
[Desire Android Development] Twau:
Been waiting for this!

Thanks!
[Desire Android Development] l3zawi:
can I flash it via fastboot ???
[Desire Android Development] Latty:
Wohoo, thanks Amon_RA!

(Yup, flashable through fastboot if you have s-off)
[Desire Android Development] Twau:
Works perfect

fastboot flash recovery C:\PATH_TO_RECOVERY
[Desire Android Development] lumich:
Thanks . Great work :)
[Desire Android Development] l3zawi:
alright ... tnx guys ;)
[Desire Android Development] sfjuocekr:
Don't forget about the Desire HD :)

I like your recovery, but am personally using psfMod recovery.
[Desire Android Development] bemymonkey:
Awesome, I never thought we'd see the day... thought you were busy with N1 :)

Thanks a lot for this!
[Desire Android Development] Moe5508:
+100...awesome work. also thought we were stuck on 1.7.0.5 which was working just perfectly by the way...just the flash unsigned files was the big missing function for me. :D

You may want to add to OP that its also possible to flash this using a certain small but greatly effective tool called Android Flasher!
[Desire Android Development] nespresso33:
thanks a lot AmonRa

With recovery 1.7.0.1 , there was a function to disable the verification of signature ;)
[Desire Android Development] Jagdish84:
Flashed, working perfectly!

ty very much!
[Desire Android Development] angelom:
Toggle Signature Verify is in "Other"
[Desire Android Development] Amon_RA:
I don't have a clue why S-OFF would have any impact whatsoever on a recovery... this recovery works fine with S-OFF.
[Desire Android Development] iinga:
No issues with the nand just people wanted the whole /data on the sd backing up and not just apps.
[Desire Android Development] jmelhus:
Thanks! Do you have a MD5 checksum for that file?

BR

jmelhus
[Desire Android Development] jmelhus:
Figured out I should post the problem I ran into, and how to solve it.

Problem:

1. Used unrEVOked 3.14, flashed RA-desire-v2.0.0 [GSM]

2. Did a Nandroid backup with ROM Manager after successfully booting back into ROM.

3. After the Nandroid backup finished and phone automatically rebooted, Windows XP popped up "qualcomm cdma technologies msm" as a device for my Desire (3 of them in device manager). This would be called a "USB-brick" if I'm not mistaken.

Solution:

1. Follow this great post! ;) http://xdaforums.com/showthread.php?t=691639

BR

jmelhus
[Desire Android Development] Azurael:
So both AmonRa and Clockwork are causign USB bricks after Nandroid in their latest versions...? I think the current version of Nandroid must be broken!
[Desire Android Development] mad-murdock:
i don't think, it was the amon-ra nandroid backup, since it only READS nand and writes to sdcard.

i guess it was unrevoked writing to the wrong nand area. do you use custom partition tables? what rom you use?
[Desire Android Development] Jagdish84:
Im using the custom Alparev supposably stock table, and ya, it causes a USB Brick, happened to me a couple of times now, i think its related to the 1.5 version of the tables coz it did not happen while using an earlier HBOOT version - i used the early and very first version of it, noticing the problem only when upgrading to 1.5...
[Desire Android Development] jmelhus:
I'm using Leedroid 2.2f, SD card is partitioned with ROM Manager (512MB ext3/256MB swap), and Nandroid backup was performed with latest ROM Manager.

Update: After a new nandroid backup with ROM Manager (nothing else done), the USB and SD card is gone again. (How-To FIX). I did not have this problem with the standard Android recovery image.

Update: So at the same time I did the amon-ra recovery flash, I did not pay attention to the Clockworkmod recovery update within ROM Manager. So when I backed up with ROM Manager (nandroid), that one bricked my USB. A amon-ra nandroid backup works just perfectly ;)
[Desire Android Development] mad-murdock:
hey, wait... if you do a nandroid with ROM MANAGER, it fake flashes clockworkmod and does not use amon-ra at all. since rom manager uses latest clockworkmod, and latest clockworkmod got a bug, this all would make sense....

did you ever try to make a backup without useless rom manager? press and hold power off, select reboot, select recovery, see if you got amon-ra there...
[Desire Android Development] jmelhus:
Yep, thats correct. Amon-ra recovery nandroid backup is good! No problem. So it seems that the latest Clockworkmod recovery breaks the USB. Thanks for the reply!
[Desire Android Development] Jagdish84:
I just did a nand backup, flashed a certain kernel and reverted back via nand, eveything went well, I'm using AmonRas 2.0.1 and Alpharevs stock like table.

Sent from my HTC Desire
[Desire Android Development] Amon_RA:
You got me worried there for a minute! ;-)

To everyone making nandroid backups with Clockworkmod/ROM manager : Don't try to restore them with my recovery. The Clockworkmod recovery isn't using the same nandroid script as my recovery.
[Desire Android Development] mercianary:
Would it be worth putting something in to break complatibility so it isn't possible to restore a clockwork recovery with your one? From my experience people just blindly use rom manager and complain when things go wrong.
[Desire Android Development] Azurael:
Glad it's not broken :) I have the old AlphaRev S-Off with the stock table and all seems fine here.
[Desire Android Development] mad-murdock:
isnt it obvious? and also explained 1000 times?

its unrevoked! unrevoked gives you a new recovery AND root's your rom! so it replaces su and the superuser app with its own stuff. you can switch which recovery to use, but you cannot tell unrevoked not to root your rom.

either backup superuser, reflash your rom, flash amon via s-off or another one of the endless creative ways saving and restoring the su and superuser binaries.

is this week the international blame-all-****-on-amon-ra week? we got countless reported "bugs" in amon-ra, which are not closly connected to amon ra.
[Desire Android Development] nickk67:
Hey guys, I tried installing the latest 2.0.1 through a terminal but it came back with errors(a whole bunch of erase failures). The last line says "error writing recovery: No space left on device" but I do have 50MB of internal and 1.6GB of external available. Could anyone point out any ideas here please?

Edit: How rude of me! I forgot to say: Thanks in advanced guys! :)
[Desire Android Development] cap11:
Maybe you don't understand - or it's me ;-)

Are you telling me that after i flashed AmonRa 2 and afterwards flashed new roms, the unrevoked su is still there?? Cause that's the logic you're implying ...

And like you said:"Reflash your rom" - that's what i did.

and if you read more carefully - i mentioned the fresh installs before ... your blood pressure will surely stay lower ;-)
[Desire Android Development] Amon_RA:
su problems are related to the su binary/apk which is pushed by unrevoked.

They have nothing to do with this recovery.

update/reflash your su/apk if you have issues with it.

Once you got rid of the su issue make a new nandroid.

And if you are using apps/cache or whatever on /sd-ext -> make sure to clean it before restoring a nandroid (or use v2.0.1).
[Desire Android Development] cap11:
thx for the info.

maybe my english is not as understandable as i thought ;-)

only to make clear, what i meant:

1. i did a fresh clean rominstall after wiping, after that all my apps apps -> everything works fine also after reboots

2. next step is a nandroid backup

3. after restoring this NEW nandroid backup the su issues appear

4. old nandroid backups (before v2) are restorabel w/o the issues

maybe i had some kind of special "luck" while backupping ;-)

will also try the sdcard fullwipe

anyway i will wait for your 2.01 :-)
[Desire Android Development] mad-murdock:
sorry mate, i try to help everyone on this thread (and many more), but the last pages here it seams, everyone blames amon-ra-recovery for all strange errors which are not related to the recovery at all.

my favorite is blaming amon ra for usb-bricking, but in fact using clockworkmod.

all these issue get a bit wierd in this amount. right now, amon-ra 2.0.1 doesnt seam to have ANY issues at all.
[Desire Android Development] nickk67:
Any help with this?
[Desire Android Development] cap11:
No problem :-)

And i appreciate AmonRa's work and your trying to help. Thanks to bothof you.

Tried the search, but couldn`t find the location of 2.0.1 - could you provide a download link or isn't it released yet?

Thanks in advance
[Desire Android Development] sjgore:
It's in post #152.
[Desire Android Development] bemymonkey:
Sounds a lot like you might not be S-OFF?
[Desire Android Development] cap11:
Thank you very much!
[Desire Android Development] nickk67:
Yeah, I didn't S-off. So do I actually need to be S-Off to install it? I wasn't aware I needed to be S-Off to push via terminal.
[Desire Android Development] bemymonkey:
The only way to install this WITHOUT S-OFF is via Unrevoked, AFAIK.
[Desire Android Development] nickk67:
Alright, thanks guys! Will experiment S-OFF on my desire :)
[Desire Android Development] rraaka:
Thanks Amon, iinga, mad murdock for your help and patience.

I managed to flash the 2.0.0 ver of this recovery after the second attempt with unrevoked. the first time had problems with driver - the phone stuck on boot logo. and i had to pull battery out.

For those who are newbies select the custom recovery in menu before plugging the phone in or it wont let you select later.

I flashed the newest blackdroid rom with amon ra recovery. Everything fine so far.

Im s -on. Do i need to keep rom manager at all ? Can i nandroid back up and restore with amon ra recovery now 2.0 now ?

I cannot handle usb brick coz its too difficult for me.

I didnt flash 2.0.1 coz it hasnt been released officially yet.

Thanks again and appreciate your help.
[Desire Android Development] Amon_RA:
Rom manager is for clockwork recoveries, not for this recovery so you can remove it.

Yes, boot into recovery, select backup/restore and make a backup/restore.

2.0.1 is only usefull if you use sd-ext which I assume you are not using.
[Desire Android Development] jmelhus:
Hi Amon_ra,

Could you have a look here? What do you think?

http://xdaforums.com/showpost.php?p=9533643&postcount=93
[Desire Android Development] beanbean50:
the flash worked well first time without any problems (many thanks) superuser updated, but when I power off and reboot into recovery I'm still getting clockworkmod recovery screen, I wonder what I'm doing wrong?

(it's probably blatantly obvious to you guys but not to this thicko...lol)
[Desire Android Development] Heppieboeddah:
There is a discussion in the clockwork 2.5.1.2-topic going on about using Amon_Ra's 2.0 in combination with rommanager/clockwork. Maby Amon_Ra is able to comment on this?

Hoi uDK.

Seems its the combination using Amon-Ra 2.0 as recovery [permanent flashed] and using clockwork for backups and restore. Maybe you are able to reproduce it? Flash the Amon_Ra recovery 2.0 and then make a backup with rommanager/clockwork. After the backup is done. You might see that the phone is USB/SD bricked. Couldt you please confirm that?

Amon_Ra says in the topic about his recovery the following:

To everyone making nandroid backups with Clockworkmod/ROM manager : Don't try to restore them with my recovery. The Clockworkmod recovery isn't using the same nandroid script as my recovery.
[Desire Android Development] Jagdish84:
I used AmonRa 2.0.0 and 2.0.1(permanent flash) without using clockwork or Rom manager and still got the USB bricks, i reverted back to Amon_Ra 1.7.0.1-R5 and everything works just fine...
[Desire Android Development] mad-murdock:
i use amon-ra 2.0.1 (and 2.0.0 before), doing backups each day (for nightlies) and also restores every now and then. never had issues.

can you explain, why people use clockworkmod fake flash at all, if they got amonra? for downloading and auto-flashing rom releases, or what?
[Desire Android Development] Jagdish84:
It might have something to do with the default 1.5 HBOOT by Alpharev...thats table i use...
[Desire Android Development] mad-murdock:
i use alpharev's n1table
[Desire Android Development] beady_uk:
This is probabilly a REALLY dumb question but i just want to know the answer!

When performing a nandroid restore do i need to WIPE ALL then restore, or does the nandroid restore do a wipe as part of its process?

Thanks folks
[Desire Android Development] annewbie:
no need to wipe. Just restore nandroid.
[Desire Android Development] beady_uk:
Thanks for that.
[Desire Android Development] Kanzar:
I'm having issues flashing this. I haven't S-OFF'd (not sure how to, tbh), and Unrevoked isn't working.

I'm running Win7x64, the unrevoked drivers have been installed, HTC Sync is uninstalled.

It gets to "Waiting for root... (safe to restart if this doesn't work)", and while the phone does change connection type to the PC a few times, it just hangs there on the Telstra boot screen without any activity or connection beeps.

It doesn't continue on to Leedroid, or anything. I remove the battery and start the phone up, it boots up Leedroid, and unrevoked says it couldn't get root.

I also can't install it via rom manager because the option is greyed out? I know people say to get it to flash CWR, but when I click 'Flash ClockworkMod Recovery' (current and latest are same version), it just says to confirm device then that it has successfully downloaded it. No further activity. :/
[Desire Android Development] rraaka:
Till now Ive used unrevoked twice and it never works with windows XP 32 bit. But with Vista the drivers get installed on their own and it worked for rooting and recently for flashing Amon ra recovery 2.0.

I wish there could be a suitable application built around Amon Ra recovery just like rom manager for cwm.

Whether its the s- off or the double use of both amon ra and cmw i hope the conflicts are sorted out soon.

Ive been using Amon Ra recovery for rom flashing, wiping, and sd partitioning and its heaven-sent. Love it.
[Desire Android Development] Junp3i:
I'm having mostly the same issue.

My phone is rooted and running the Lambros Rom. I know the Unrevoked3 setup on my pc works as I just used it on my partners desire (hers has never been rooted in the past) and she now has the CWM recovery flashed perfectly

Whenever I run Unrevoked3 (standard CWM or with Amon-RA custom) It gets to the waiting for root section and hangs, Battery pulled, loads up fine. Failed to get root.

Any idea folks?
[Desire Android Development] hallydamaster:
If you cannot get it to work with Unrevoked, the only other options is to S-OFF and flash it with fastboot!

S-OFF is easy, and noone has encountered a brick so far! Follow the guide from AndroidGX by this link:

http://xdaforums.com/showthread.php?t=805811

After S-OFF you can easily flash the recovery image with the Android Flasher:

http://xdaforums.com/showthread.php?t=794638
[Desire Android Development] iinga:
Or connect phone in bootloader and type the following in cmd/terminal after placing the recovery in the android sdk tools folder:

fastboot flash recovery [nameofrecvoery.img]

so in this case (unles you rename it)

fastboot flash recovery recovery-RA-desire-v2.0.0.img
[Desire Android Development] MichelN:
Install official ruu, use unrevoked and select custom recovery. Worked fine for me.
[Desire Android Development] boomam:
Ive just tryed that myself as a fix to the same problem as others, but i just get it hanging on 'waiting for device', got around that by rebooting to fastboot, but now it fails with signature verification.
[Desire Android Development] StuMcBill:
You need to have S-Off to flash via fastboot.
[Desire Android Development] Rastaman-FB:
s-off needed
[Desire Android Development] boomam:
So how do i flash it otherwise?

As unrevoked wont do it, just keeps hanging on the HTC logo after the 'waiting for root'...?
[Desire Android Development] mercianary:
Those are your only 2 options...unrevoked or s-off
[Desire Android Development] Droidzone:
Yours could be a driver issue..Two seperate set of drivers (Hboot, Win, ADB interface) are needed for unrevoked to work..Check the 1st post of unrevoked for the exact procedure to install the drivers..If all else fails, remove HTC drivers and software fully, Choose device manager and uninstall all drivers (uninstall+delete) which seem to be even remotely connected to an Android interface, disconnect from your internet for the entire procedure to prevent windows from connecting to internet and getting another driver, reboot, connect ur phone to pc without internet..Phone should be found by windows but driver should not be recognized..If it is recognized, uninstall and del those drivers too..

Finally, reboot once more, and follow unrevoked's driver installation procedure from scratch..Ought to work unless there's something wrong with ur hardware..

S-OFF 'usually' doesnt cause bricks..I had one..but that was because of a hardware issue which caused my phone to reboot before alpharev had completed..
[Desire Android Development] boomam:
Hmm,

Perhaps not the place, but any idea why unrevoked/the phone is hanging on the 'waiting for root' ?
[Desire Android Development] Droidzone:
Just answered
[Desire Android Development] nickaaai:
Hmm, I'm jusing terminal to flash this recovery.

But it says: "flash_image: not found" ??????
[Desire Android Development] Possible:
Hello everyone,

I just followed the tutorial to turn off the S-off thing.

However, everyone is saying that they flashed the custom recovery with fast-boot. How can i managed this? I read all of the pages but its not explained how to do it ?
[Desire Android Development] Nitin985:
How do I transfer my clockwork backups to this
[Desire Android Development] gutsbn:
Command line stuff using the SDK/ADB

Easier to use this instead: http://xdaforums.com/showthread.php?p=8367093
[Desire Android Development] Heppieboeddah:
Download Flash_Image from here

http://www.4shared.com/file/WcspbUYC/flash_image.html

And copy/paste it to /system/xbin

Its a part of busybox. Youre busybox might not have flash_image
[Desire Android Development] raymondy:
How can I upate my current RA-DESIRE-1.7.0.1 R5 to 2.0.0

I'm still s-on,I used unrevoked to choose this new img file (md5 corrent),

after a few minutes, it said its done and went into recovery menu automatically,

but its still 1.7.0.1 R5. I tried both the original img and also the modded img file,

neither would work:(

any ideas, guys? thank you very much!
[Desire Android Development] mad-murdock:
Oh noes, not again, I still have a serious trauma from the last thread this happend.

The same question 3 or more times on one page close below the answer its a bad sign...

who let the trolls out?

Swyped with HTC Desire. Excuse typos.
[Desire Android Development] reddev0:
Shot in the dark, but bootloader needs to reboot when switching recovery images (at least when using fast boot)

Sent by my Droid
[Desire Android Development] Rastaman-FB:
you using that new ARA htc stock RUU?

if so it cannot be rooted
[Desire Android Development] skedone:
guys is it safe to use unrevoke on the miui rom as i would really like to install this on my desire as i miss the partioning options so much i keep having to put it in my hero and do it at mo lol

forgot to say i have only used the unrevoked method so far and the flashed the miui rom but now would like to try the HD rom
[Desire Android Development] boomam:
No, im using Oxygen v1.0.

I just cannot get it to work at all, ive uninstalled the drivers, put the latest ones from unrevoked in for the HBOOT & Fastboot, and the correct ADB drivers, it just will NOT do!

And this happens on both my home PC and my work laptop, both of which ive rooted using the same method 2-3 phones each!

Any ideas?
[Desire Android Development] Spitniv:
Hi,

I downloaded the unrevoked, loaded the img file, went to recovery, and nothing changed :(

where/how am i suppose to see the new recovery?

Thanks ahead,
[Desire Android Development] Tyderion:
thanks for your feature-packed recovery :)

I had a problem with my sd card (recoveries couldn't mount it). Tried repartioning many times from windows and with parted but nothing changed.

Now, after flashing your recovery with fastboot and then partitioning the SDcard, it works again!!

big thanks, now I'm again able to flash files from recovery :D
[Desire Android Development] Spitniv:
How did you flashed it?

with the unrevoked?

please if you could help me (1 response above you)

cant see the new recovery :/
[Desire Android Development] -V-O-Y-A-G-E-R-:
Agree :)

Any plans on releasing a version that would support DHD?