yashsingh1/xdaforums huggingface dataset:
[Desire Android Development] newcastlepunto:
try reading the post

"The purpose of this recovery is to avoid using adb by accessing all features directly from the menu."
[Desire Android Development] rolfd:
That doesn't clearly answer his question.

The simple answer is NO. You still need to connect to the computer.
[Desire Android Development] oderayi:
Device not found

I got device not found. Please help. My HTC Desire is not booting to recovery or normal home scree, keeps looping at start up from the Green HTC logo.
[Desire Android Development] Rastaman-FB:
if it can boot to bootloader, use an RUU

you shouldnt use fake flash for new devices, it doesnt work
[Desire Android Development] blackrat62:
This is doing my head in - can anyone post a simple how to guide please. I have jailbroken iphones, cracked GPS devices with ease but this is defeating me at every step.

I managed to root my Desire but it won't download a custom ROM (get errors as reported in early posts). So put back to stock (unrooted) and hoped to use Alpharev to root fully but that needs rooted ROM, tried to put rooted ROM on using Fake-Flash but post above correctly states can't use with new devices (nothing happens when I run as administrator) - aaaaaaaaah.

The upshot is I have a brand new desire which is not branded or locked to any network out of the box - I think I need to put a rooted ROM on (but cannot find how), then root using Alpharev, the put custom ROM on - or should I have a cup of tea and start again?

Be grateful of your help.
[Desire Android Development] simonthor:
Use Unrevoked to root. It will fully root your device, replacing the recovery permanent. I think you need that to make AlphaRev work. :) (It's also waaay easier)
[Desire Android Development] blackrat62:
Thanks but whole problem is that unrevoked doesn't fully root my Desire as it is the PVT4 type - I cannot do custom ROMs as they simply refuse to load, this seems well documented.

As a result I cannot use Alpharev as that must have a rooted ROM installed. I cannot find a step by step guide, plenty of reports of success but no-one saying exactly how they did it.

Thanks for taking time to reply.
[Desire Android Development] Qli-max:
Great work! Works fine here :)
[Desire Android Development] RustyJoe:
Actually, I did read it but I am a bit of a noob with Android.. Didn't get it..

Thanks for the clarification.

Will we ever have a stand alone recovery w/o the need for pushfiles to enter recovery?
[Desire Android Development] sruon:
Ever? Possibly, that's one of the big feature people are trying to get...

When? No idea =/
[Desire Android Development] PsYDoX:
Mirror: http://desire-stuff.6x.to/
[Desire Android Development] ahmgsk:
link not working
[Desire Android Development] drvdijk:
It is here :)
[Desire Android Development] 77flem:
same here link is working.
[Desire Android Development] shawe_ewahs:
ahmgsk is not possible do a update.zip for install recovery files like a ROM? I understand that we can't flash a recovery.img, but is a lot different that doing a permanent install of this files. I can't understand because we can install update-rom.zip but not a update-recovery.zip.

I try to do a update-recovery.zip for r4 version, I can do it again for your version and try if it is possible to do so.
[Desire Android Development] PsYDoX:
whoot -.-

try again or try

http://r28916.ovh.net/~desire/
[Desire Android Development] shawe_ewahs:
Works for me
[Desire Android Development] 77flem:
Why ROM folders are empty ? ;-)
[Desire Android Development] StuMcBill:
Any chance of an MD5 hash for the zip file, just so I can make sure that nothing got corrupted etc.

Mine shows A5CFFDB7CC4230D3C16E23E6D2100A19
[Desire Android Development] PsYDoX:
LOL.... 2.1 Roms are Uploading and 2.2 Froyo dont exist xD
[Desire Android Development] snear:
nandroid back up isnt working still... is this right?

getting error when trying to back up on both options nandroid & nandroid + ext

thanks for all the work you have been doing:)
[Desire Android Development] Bart1981:
I made a Nand backup with no problems at all with this recovery. Never tried it on the other recovery though.
[Desire Android Development] kingchris:
it is not possible atm, because the partition of recovery is write-protected.

so you cant flash anything there

the systempartition is also writeprotectet (if the system is running) but can be accessed from recovery.
[Desire Android Development] amjad_2020:
Thank you how to do it in ubuntu 10.04 ??
[Desire Android Development] shawe_ewahs:
atm means "at the moment"?

Good explanation, I think that only way isn't possible is flashing a recovery.img
[Desire Android Development] drvdijk:
Nice work! However, I have a question. Did you design the recovery process to run as a daemon process? If not, how would it respond to a SIGHUP, possibly maybe sent when the usb cable gets yanked and the tty closes down?

In short, shouldn't there be a nohup call somewhere in your recovery scripts?
[Desire Android Development] snear:
are you on the stock rom??
[Desire Android Development] kingchris:
...right ;-)
[Desire Android Development] Jpcurrie:
Looks good, this will save a lot of time backing up and repartitioning the SD card.

Shame I'm not brave enough anymore to flash :(
[Desire Android Development] snear:
when trying back up I get "error run nandroid-mobile.sh via adb"

anyone else ??
[Desire Android Development] MattCB72:
Hi!

I use Ubuntu 10.04 (32 Bit) and can't get the Recovery to work. Pushing the files seems ok, but then i get a error message:

BTW: i needed to chmod +x the recovery-linux.sh, because the terminal said :
[Desire Android Development] Heppieboeddah:
Did you choose nandroid+ext?

Had the same wenn i made the android+ext. Checking after the error my sdcard the backup was made but just:

boot.img

data.img

and

system.img

So ik think its just gives the error if you do a nandroid+ext

The question i do have: "does the backup do an extended as well"?
[Desire Android Development] shawe_ewahs:
EDITED

Seems to be problem with permissions on Linux do this, modify your recovery-linux to something like this (applicable to Linux or Mac):

#!/bin/sh
echo Desire Recovery Mode
echo
echo Applying correct file permissions
echo
chmod +x adb-linux
chmod -R -w * files/
chmod -R +x * files/
echo
echo Killing adb server...
echo
sudo ./adb-linux kill-server
echo
echo Runing adb like root...
echo
sudo ./adb-linux root
echo
echo Pushing required files to device...
echo
sudo ./adb-linux push files /
echo
echo Installing busybox to device...
echo
sudo ./adb-linux shell busybox --install /sbin
echo
echo Launching recovery on device...
echo
sudo ./adb-linux shell /sbin/recovery &

Zip file is losing file permissions.
[Desire Android Development] kingchris:
run it without sudo

"sh recovery-linux.sh"
[Desire Android Development] snear:
I got the error on just nandroid aswell :(
[Desire Android Development] Nekromantik:
I just tried nandroid and it just froze halfway through the backup

retried and I get the nandroid error when selecting backup + sd
[Desire Android Development] MattCB72:
Nope:

@shawe_ewahs: Same error with the modified recovery-linux.sh
[Desire Android Development] shawe_ewahs:
I edited my last post, try again: http://xdaforums.com/showpost.php?p=6613896&postcount=46
[Desire Android Development] ahmgsk:
@MattCB72

bro which all files u get error -> right click them

allow execution of file -> last tick

and then try
[Desire Android Development] MattCB72:
Thx, it works. :-)
[Desire Android Development] Heppieboeddah:
can you confirm a nandroid+ext backup from the recovery doesn't work?
[Desire Android Development] MattCB72:
No, nandroid+ext backup doesn't work. :-(
[Desire Android Development] shawe_ewahs:
What order do you have the partitions on SD? This can be the problem with this.
[Desire Android Development] stingerpl:
Does not work for me also.
[Desire Android Development] MattCB72:
Card: 8 GB Class 4 from Kingston

1 GB Ext2

FAT32 Remaining
[Desire Android Development] nico1375:
Just to be sure, "should" it be less risky than the previous recovery concerning the bricking?
[Desire Android Development] eViL D::
Very nice, keep up the great work!
[Desire Android Development] abats:
Crossing my fingers to not hear of any bricking going on with this one!
[Desire Android Development] Letitflow:
Thanks alot man!
[Desire Android Development] nico1375:
Is it a too stupid question?
[Desire Android Development] wgery:
Can I use this recovery if I am not using the apps2sd so my sd card isn't formatted as ext, just simply fat32??
[Desire Android Development] stingerpl:
We are not 100% what is the cause of bricking so I'm pretty sure nobody will answer your question.
[Desire Android Development] kurt666:
Nice thank you very much for this new recovery method.

Keep up the good work.
[Desire Android Development] nico1375:
I know there is nothing certain, hence the "should"...

Actually i'm mostly wondering if this recovery was developed in order to try to avoid flaws in the previous one that "might" have led to bricking...

Also I don't recall having seen some bricks when used under mac os (but since there are bricks on linux, maybe osx is not safer...)
[Desire Android Development] StuMcBill:
I *think* the answer is on the previous page, not 100% sure as I am not familiar with Linux.
[Desire Android Development] GeoTrail:
@StuMcBill, thanks for the reply.

That sorted it. I'm using Mint right now, first time so I didn't know there was a permission issue on here. Got recovery running now :)
[Desire Android Development] StuMcBill:
@GeoTrail Glad I was of some help! :D
[Desire Android Development] GeoTrail:
Nandroid backup +ext doesn't work. It says I need to run nandroid.sh via adb.
[Desire Android Development] Kollegah:
Great Recovery, good work!

Is it possible to develope a Recovery that is independent to a PC? Like the Nexus One Recovery.
[Desire Android Development] shawe_ewahs:
For the moment it can't be flashed, recovery is write-protected.
[Desire Android Development] Gooner4_1998:
Re: [Recovery] AM Desire Recovery v1 [27th May] via PC only

This is possibly a stupid qu but I have rooted my desire using Paul at Modacos method.

What is the benefit of me now applying this?

Also, is there an idiots guide for applying?

Sorry for the noob qus!

-------------------------------------

Sent from my HTC Desire
[Desire Android Development] scotch whisky:
As it is not known what causes the bricking it really is impossible to answer your question. The new method of recovery will wipe the "ext" partition which was broken in the original. This means that you don't have to repartition the SD card every time you flash a ROM.

I personally don't think that this new method will prevent bricking but only time will tell.

You really will not get a better answer at this time.
[Desire Android Development] sgk2007:
Problems installing apps & games from SD card

Hello,

Pls kindly help me with my problems:

- After installing this Recovery exactly as instructed, I get error message when installing *.apk files from SD card: "There is a problem parsing the package".

Therefore, I cannot install anything from SD card anymore :( (installed apps work well)

Notes:

I've updated Pays-ROM Desire Sense v1.5 (RockSolid) successfully & working great.

Then immediately after I update this "AM Desire Recovery", errors happen.

Thanks in advance.
[Desire Android Development] oawalker:
i Have a question i previously had a htc hero i rooted it and i am familiar with the process etc. but after i root my htc desire what is the process to update to this new recovery???

Thanks
[Desire Android Development] AlexFLCL:
Same uestion Here. In used intall all kind of things in my Touch 3g but now i'm something like lost. Is there any tutorial to instal that recovery?.
[Desire Android Development] Marco.t...:
Root zhe Desire with the AM Desire Recovery

Hey guys is it possible to root the Desire with this Recovery? Or is this only to flash Custom Roms when the Desire is already Rooted????

If its possible to Root it with this Recovery is there a guide available how it works?

Thx in advance
[Desire Android Development] ieftm:
@ahmgsk:

It's not smart to start your recovery binary with only '&'.

Safer would be to: adb shell sh -c "nohup /sbin/recovery &".

That ensures that recovery isn't killed when the adb shell is terminated (by USB disconnect, or w/e). As you can see from Paul's recovery method, r5 was changed to this default.

With this method, you can even disconnect USB after push and starting recovery is done.

Please update?
[Desire Android Development] lgrangeia:
If anyone ever gets USB bricked using this recovery please report ASAP.
[Desire Android Development] lgrangeia:
OP, can you modify your recovery so it pushes files only to /data/ or below and runs off those files?

I have a theory that modifying / (rootfs) might be causing the USB bricks, check my post here:

http://xdaforums.com/showpost.php?p=6625572&postcount=74

Might be tricky to do this, but maybe chrooting might help. Also, when wiping the data partition care must be taken not to wipe the recovery command itself.

Please let me know if you're working on this.
[Desire Android Development] rolfd:
It might be worth posting this to paul over at modaco too. He was the first one to bring the root process for the desire. He might have a view on it?
[Desire Android Development] nilezon:
Very interesting indeed.

You might be on to something.

Can we execute from /data/local/bin ?

I just spoke to PaulOBrien. He's looking into this, and some other ideas ... stay tuned
[Desire Android Development] JDouce:
talk to this guy :D

http://twitter.com/ahmgsk_mod its his recovery and hes awsome if any1 can do it he can
[Desire Android Development] rolfd:
I've sent him a note on twitter and asked him to take a look!
[Desire Android Development] ahmgsk:
I will check it out

But never to remove usb untill u poweroff or reboot from recovery

He had a look on it i think,

still i will post it
[Desire Android Development] JDouce:
so can you just change the recovery-linux.sh to

chmod +x ./adb-linux
./adb-linux push files /
./adb-linux shell busybox --install /sbin
./adb-linux shell sh -c "nohup /sbin/recovery &"
[Desire Android Development] adam235:
When i run recovery-windows.bat i get this msg "error: device not found". my htc desire is at the screen with the red triangle and in the usb devices i can see a "Qualcomm CDMA Technologies MSM" device.

what should i do ?
[Desire Android Development] rolfd:
Have you rooted this handset previously?
[Desire Android Development] adam235:
yep it was rooted by pauls r4 rls.
[Desire Android Development] rolfd:
If you are at the red triangle and you can't go any further then it's a safe place to take the battery out and reboot.

I fear you have bricked it though, because that qualcomm device is as far as I know, only seen in bricked handsets.

Try to reboot it and check if your usb is working normally, and your FM radio, and SD card.

Good luck!
[Desire Android Development] adam235:
hm damn. no usb or sd card access :/ that sucks.

but step1 (fastboot) is still working. is there any way to fix it there ?
[Desire Android Development] Rudolfje:
There's no fix for the USB Brick (yet)

You might be able to fix SD Card access by some command.

Something like: fastboot oem enableqxdm 0.

You used this recovery and got USB Bricked?
[Desire Android Development] rolfd:
Unfortunately not yet. If you take a look around the dev section here, and on modaco you will find a fair bit of info. You can get your SD card working again for now.

I'd go to modaco and add your name to the vote there for the number of bricked devices. It's over 60 now.

Just to double check, ou have no USB access when the handset is switched on? Does it take a few minutes after you plug the USB lead in before the charging light comes on, and can you get your FM radio working? I just want to be sure your bricked first!
[Desire Android Development] MadMic:
Just a quick question, but why root again? Not flaming you down just trying to understand and learn from all that's going on before deciding to root or not.

Also yours is the first reported 'brick' with the new amon-ra method, wondering if its the method at fault or not...

I feel your pain, but hop over to modaco and there's some really hopeful developments going on and inch by inch the solution is being found - hopefully a break will come soon, either that or you can un-root and return it under warranty :)

Good luck dude...
[Desire Android Development] adam235:
I wanted to flash the froyo rls on my desire through the recovery menu.

i got no usb access and i cant choose to use it as a drive in the usb connection type menu. the usb device i can see is :

Bus 001 Device 017: ID 05c6:9002 Qualcomm, Inc.

and i got no access to the sd card.

but if i can access the device with fastboot isnt there a way to fix it there ?
[Desire Android Development] ahmgsk:
i m going to check it with qualcomm chip settings if that causes it -> or we can do anything for it but after 5th june
[Desire Android Development] adam235:
Another problem i got is that i cant do any calls anymore. the device says that i got no network connection.

if i try to connect by searching for the provider i get the msg that my sim card doesnt support the provider.
[Desire Android Development] Picarden:
I must be stupid, but how should i use these files to root??? :confused:
[Desire Android Development] ahmgsk:
to root

???

this is not for rooting
[Desire Android Development] Gooner4_1998:
Re: [Recovery] AM Desire Recovery v1 [27th May] via PC only

Is there an idiots guide to using this file anywhere?

Thanks

-------------------------------------

Sent from my HTC Desire
[Desire Android Development] adam235:
ive tried to boot the device with the command "fastboot-linux oem boot"

then i get some information about the boot process:

... INFOsetup_tag addr=0xA0000100 cmdline add=0x8E07D98C
INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 0
INFOTAG:hwid 0x0
INFOTAG:skuid 0x21F04
INFOTAG:hero panel = 0x0
INFOTAG:engineerid = 0x0
INFOMCP dual-die
INFOMCP dual-die
INFOTAG:mono-die = 0x0
INFODevice CID is not super CID
INFOCID is T-MOB101
INFOsetting->cid::T-MOB101
INFOserial number: HT0..........
INFOcommandline from head: no_console_suspend=1
INFOcommand line length =419
INFOactive commandline: board_bravo.disable_uart3=1 board_bravo.
INFOusb_h2w_sw=1 board_bravo.disable_sdcard=1 diag.enabled=1 boa
INFOrd_bravo.debug_uart=0 smisize=0 userdata_sel=0 androidboot.e
INFOmmc=false androidboot.baseband=4.05.00.11 androidboot.cid=T
INFO-MOB101 androidboot.carrier=TMD androidboot.mid=PB9920000 an
INFOdroidboot.keycaps=qwertz androidboot.mode=recovery androidbo
INFOot.serialno=HT0....... androidboot.bootloader=0.75.0000 no
INFO_console_suspend=1
INFOaARM_Partion[0].name=misc
INFOaARM_Partion[1].name=recovery
INFOaARM_Partion[2].name=boot
INFOaARM_Partion[3].name=system
INFOaARM_Partion[4].name=cache
INFOaARM_Partion[5].name=userdata
INFOpartition number=6
INFOValid partition num=6
INFOmpu_nand_acpu_rw 23A 1000
INFOjump_to_kernel: machine_id(2457), tags_addr(0x20000100), ker
INFOnel_addr(0x20008000)
INFO-------------------hboot boot time:866136 msec
FAILED (status read failed (Protocol error))

is it normal that board_bravo.disable_sdcard is set to enabled ?
[Desire Android Development] oawalker:
+1

Same here i would like to know as well
[Desire Android Development] gaeng4665:
does this recovery also work with MAC OS since it is written only for pc, but further down it's written: apply with the following commands pc...linux...osx...???

many thx
[Desire Android Development] shawe_ewahs:
You can download and see that it works for windows-linux-mac
[Desire Android Development] ahmgsk:
check 1st post now
[Desire Android Development] oawalker:
Thanks

i think i know what i need to do now.

going to attempt to root my phone and update the recovery an hopefully get froyo on my phone :D.
[Desire Android Development] dancedreamfly:
Okay, I mustered enough courage to run this recovery. During my last flash (circle battery mod) I experienced console instability, which is why I was kind of hesitant to run this new recovery. But then I saw another thread which detailed how to enable the other hardware buttons (e.g. home, menu) to wake the phone when it is locked. Then I felt the sudden itch to flash!

I tried this recovery and I must say it's very stable. No glitches or the need to re-execute the recovery script. I'm using OS X 10.6.3 BTW.

Here's a guide for those new to this:

1. Download the file on page 1, then extract the .zip. There should be a folder named AMDesireRecovery

2. Turn off your Desire then turn it back on with the volume down button held.

3. Use the volume keys to scroll down to 'Recovery', then press the power button to select.

4. You should see a screen with a red triangle on it. At this point, connect the Desire to your Mac.

5. Open Terminal and change the directory to wherever the folder is located. In my case, it was the downloads folder so it looked like this:

cd /Users/YourNameHere/Downloads/AMDesireRecovery/

Then press return

6. Run the appropriate recovery script:

./recovery-mac.sh

Then press return

7. You'll see a new recovery menu (with a Nexus One image)
[Desire Android Development] ibila:
Hello,

Question, is this recovery still free of usb-brick casualties?

I rooted my desire and flashed it with pays rom and im ****ting my pants at the thought of flashing another rom :)

So there are 3 options for me:

-Unroot when froyo goes ota (might take a while).

-Wait untill we get a saver recovery to flash roms (Paul Obrien...lets hope soon).

- Use this new recovery and pray it won't brick my phone.
[Desire Android Development] Rudolfje:
The methods for both recovery are equal, so this one being bricksafe doesn't make a lot of sense.

Flashing is tempting, I know, but if you're happy with your current rom, you'd better stick with it for now.
[Desire Android Development] rolfd:
If I were you I'd wait! This recovery isn't that much different to Paul's and it's generally agreed now that the recovery is what is most likely to be causing the problems.

It really is pure luck, or bad luck that some people get bricked handsets and others don't. I flashed 3 times and got it, some have flashed literally hundreds of times, and others bricked on their first flash. It's kind of russian roulette with the phone :p
[Desire Android Development] ibila:
Your absolute right. I will wait for a better solution. Im used to flashing roms non stop on my g1 so this feels like being in rehab. ;)
[Desire Android Development] emontes:
Adam,

Go to fastboot mode and type:

fastboot oem enableqxdm 0

And reboot your device, you will get at least your cellular and sd card back but unfortunately, there is currently no fix for the usb brick.

Cheers
[Desire Android Development] GeoTrail:
Excellent as always :)

:BIGTHUMBSUP:
[Desire Android Development] GhostSoldier:
All I get when I try this is command not found.

Using Mac , Terminal and navigated to r5-folder.
[Desire Android Development] cedeel:
Bash doesn't work like cmd.exe

Your current dir isn't in the $PATH, so prepend ./ to the command. Also, you probably have a fastboot-mac executable.
[Desire Android Development] shawe_ewahs:
Its normal, you don't have "fastboot" binary file, you have "fastboot-mac", try with:

./fastboot-mac oem enableqxdm 0
[Desire Android Development] shawe_ewahs:
Anyone can explain me why appears this message:

After command:

I think that seems "nohup" is not working.
[Desire Android Development] Rudolfje:
Nohup doesn't output to stdout, but to nohup.out.

So I guess that makes sense.
[Desire Android Development] shawe_ewahs:
Thanks for your reply.
[Desire Android Development] abc27:
Am I right in assuming I can use this recovery to flash FroYo roms? Now that the bricking issue has been solved i'm gonna try new roms far more frequently :D
[Desire Android Development] smarti13:
pb flashing SOME ROMs

E:Error finishing BOOT:

E:Failure at line 373:

write_raw_image PACKAGE:boot.img BOOT:

Installation aborted.

pb with

- Pays-ROM Desire Sense v1.9 Dalvik

- DeFroST 0.4 Desire Froyo

could you help ?

thanks
[Desire Android Development] ahmgsk:
download recovery again n try