174 replies to this topic

[Tilu]

NICIO, on 01 December 2010 - 05:52 PM, said:

USE  UniversalAndRoot 1.6.2-beta and then use Rom Managuer Conecte With Wi-fi Not 3g cuz the file will get corrupte and go to Flash Alternate Recovery it will dowloaded and flashed good

I can't install UniversalAndRoot 1.6.2-beta it gives me this error (i use astro file manager): Unable to open universal....apk as apk file.

[NICIO]

lol... unistall astro and isntall linda file manguer from market and download universalandroot.apk again.... from here

http://bit.ly/dbsWmj


thas from the oficial release websise
http://blog.23corner...iversalandroot/

Edited by Skrki, 07 December 2010 - 12:03 PM.

[Tilu]

I used the flash_image recovery /sdcard/recovery*****.img method and now i have AmonRA-170G recovery on my phone.
Thanks for info anyway!
For Cyanogenmod 6.0 DS how many and what type of partitions I must have on my sdcard for instalation?
soory for offtopic!

hboot 1.33.0007
radio 2.22.19.26i
cpld 10

Edited by Tilu, 05 December 2010 - 04:26 PM.

[Tilu]

finaly I made it!

[herokid]

Hey guys i used the unlock guide to root my phone and flash radio and spl and the generic g1 rom. That all works. I also have ROM Manager on my phone. I have been trying to get cyanogen to work but for some reason when i flash that ROM it will be stuck on the tmoble g1. My recovery is a guy on 1 skate board people say they have 3. How do i  fix that? Secondly i cannot get into reocvery mode anymore its just stuck on the tmoble g1 screen... but i can still go onto my phone.

[herokid]

sorry for double posting but ow to:

    * Reboot to bootloader holding Back+Power or Vol.down+Power or whatever combination applies to your device.
    * Attach your device to a USB port and open up a Terminal/Command prompt of choice
    * Navigate to the folder where your recovery image is, then flash it like so:
that step i dont get two things. Do we open a terminal on the phone or on computer? and that part fastboot flash recovery recovery_of_choice.img makes no sense. my recovery image on my tools in SDK folder is called recovery so wud i type in the command fastboot flash recovery recovery.img?

[Skrki]

I think you should generally spend some more time reading the Wiki and get acquainted with basic "hacking" terms and tools. You can start here:
http://wiki.cyanogen...?title=Fastboot
http://wiki.cyanogen...ng_the_Recovery
and expand your knowledge later, by googling the key terms.

herokid, on 03 January 2011 - 04:24 AM, said:

that step i dont get two things. Do we open a terminal on the phone or on computer?

When you're in Fastboot mode, connected to a PC/MAC (through USB, as stated), you can not open your phone apps, because your system is not booted. Hence, the "Terminal/Command prompt" refers to a computer program, not the Terminal of your Android.

herokid, on 03 January 2011 - 04:24 AM, said:

and that part fastboot flash recovery recovery_of_choice.img makes no sense. my recovery image on my tools in SDK folder is called recovery so wud i type in the command fastboot flash recovery recovery.img?

You answered your own question. "recovery_of_choice.img" refers to an .img file, the recovery image you have downloaded to your machine. File name is not important here, and since users often rename their files, I used a sample file name. You should use whatever names your files have.

Here is the formal syntax of the fastboot command:

fastboot [<option>] <command>

If the <command> is "flash", you have to specify what to flash (which partition), so: system, boot, hboot, userdata, recovery.. In addition, you can specify the file that is going to be used for flashing, so the syntax of fastboot flash is:

fastboot [<option>] flash <partition> [<img_file_name>]

All fastboot commands are issued from your computer. Your phone should just be connected to it, so that it says FASTBOOT USB on the screen, and that's where you should see the 3 Androids on skateboards. You are mixing up recovery and SPL/bootloader/fastboot mode (note the 3 terms that mean the same thing).

This is the recovery mode:
Clockwork: http://geekfor.me/wp.../clockwork8.png
Amon_RA: http://pocketnow.com...Ra-Recovery.png
Amon_RA: http://www.mobilegee...a_170_nexus.jpg

This is the SPL (bootloader) mode:
http://www.gadget-sp...magic-hboot.jpg (MT3G)
http://farm5.static...._a40e478173.jpg (G1)

Tell me what your HBOOT version numbers are, when you are in the bootloader mode, and we will be able to tell you why you can't install Cyanogenmod on your phone. Just a guess for now, but I think you don't have the DangerSPL.. The G1 image above, shows the DangerSPL (HBOOT ver. 1.33.2005). That's a prerequisite for installing the CM. Look for more info here: http://wiki.cyanogen...title=HTC_Dream

Bye!

[GaryB]

My experience with not being able to boot into recovery on my Rogers Dream:
I used the ROM manager and like everybody else I found out that I could no longer boot into recovery, for some reason running fastboot flash recovery would not work even though fastboot would report a successful write of my recovery image. At that point I was OK with this because the Dream is pretty well maxed out running CM 5.07 anyways. I then made the mistake of deleting the dialer app and there by made my phone useless. So now having painted myself into a corner I decided to reformat my SD card, so when I reran fastboot flash recovery I got the same message as before about the recovery being successfuly written but now I could boot into recovery and it actually did work.

Edited by GaryB, 12 February 2011 - 11:46 PM.

[ty1988]

Hi, I also used clock work and can no longer boot into recovery mode.i want to try solution 3

"The Bash assault"- a smarter solution, but i dont know how to do this.

more specifically how do i put a script on my sd card?

What recovery image do i put on the root of my sd card?

and how do i run the script?

can someone please help me.



phone:i have the magic.

[Leicester]

Works perfect. Thanks, I almost gave up.

[chielus87]

Hello i think i really messud up my phone yesterday i just wanned to flash new spl and then after flah,

- NO HBOOT-
- No recovery


Shiiittt adb cant connect with the phone  It is a sapphier 32b (old hboot was 1.33.0013d)

at first there was a red led and then it turned blue and now it just green again

can you help me, ???? sorry for my eng. i'm dutch

[Tron1978]

Amazingly simple and worked perfectly to restore my recovery image on my dream. Thank you a million times for the simple fix

[munchkinshunny]

Hello!

I was trying to update to ginger yoshi from google ion, but I think I messed up and I just decided to just unroot and restore to original stock rom. Now I am stuck with this error message everytime I boot in rainbow screen.

DREA110 PVT 32B         RUUNBH
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.23.02

serial0

I was trying to flash different DREAIMG.nbh (RC7,RC29,orange), but I keep getting 00028002 not allow.

I read the previous posts here related to my problem and still not working. I have goldcard.

I can't get to recovery screen, and my device is not detected when connected to usb.

Any help is much appreciated. I'm on my wit's end. :(

[Dan0maN]

hi all.

i'm having a hard time getting the recovery-RA-sapphire-v1.7.0G.img recovery image to work correctly.
here's what i have:
t-mobile mytouch 3g (no headphone jack)
SAPPHIRE PVT 32B ENG S-OFF H
HBOOT-1.33.2005 (SAPP30000)
CPLD-10
RADIO-3.22.20.17
Apr 20 2009, 15:30:43

if i attempt to either 'fastboot boot' or 'fastboot flash' it to the device, when attempting to boot into recovery, i simply get the green splash screen until my phone dies (left it on that screen for hours until battery died).  i can reflash an older aman_ra recovery image (recovery-RAv1.2.0H.img) successfully, and boot from it, but it is missing the pieces i'm needing to update my radio, and install the CM mod.  i'm currently booting from an old aman_ra ROM (Rom-RAv1.1.0H-signed-update.zip).  it is working fine, and i have root access.

i just can't seem to get the updated recovery image to work on my MT3G.  ANY help is appreciated.


nevermind.  noob mistake that was caused by too many different versions of aman_ra's instructions.  found out that i was missing a critical step of upgrading the radio back to a 32B image, then re-flashing the 32B recovery image.  for anyone else having the same issue, here was the best set of his instructions that i found:
http://forum.xda-dev...ad.php?t=547133

Edited by Dan0maN, 21 July 2011 - 11:40 PM.

[pantatab]

People, please take time and try out: http://modmymobile.c...-21-2010-a.html
That is a motorola milestone page, but i'm sure you'll find something suitable for your devices.
I was experiencing the no-recovery-problem for quite a long time, tried everything until i just made it work with open recovery.
Good luck!