Phone stuck on android loop

[Guest biron_w]

I installed the custom rom to my phone quite a few weeks ago and have had no problems.

Then I turned my phone on this morning and it won't start properly.All that happens is it shows "t-mobile" then "android" shows up for a bit,it blinks and just shows "android" again.That's all it does.

If I hold vol- and red it goes to the blue screen and shows

usb fastboot:v0.5

Machine ID:

Build date: sep 10 2009,

Serial number: unknown

What can I do to get it working again?

I've seen some threads and tried to follow some instructions but i'm a proper noob and couldn't get anything to work!

[Guest Swift_gti]

Weirdly enough, my girlfriend phoned earlier to say she turned off her pulse while at work this morning.

Then when she tried to turn it back on it just looped between the android/tmobile screens..

She also has the latest custom rom installed which has been working fine since before xmas..

Not been able to look at it yet as I'm still at work.

[Guest Dumela]

I to am having the same problem from this morning...

Pure speculation but seems low/dead battery may cause it. Several other posts with same issue have mentioned that their phone ran out of battery as did mine.

Would love to ehar from anyone who has any idea how to stop it happening.

I'm getting a swap out from t-mobile since the phone is only a week old. Was told by their customer services bod that if it happened again I'd have to send it off for repair. grrrr

[Guest AndAddict]

My pulse has been doing this quite often, usually on low battery till and one time when I was using Dolphin browser it just rebooted, not to sure why it happens yet. Usually I restore a backup and it works fine.

You need to use fastboot, there's no other way about it yet unless you've got the recovery rom installed and can use adb.

What step are you having trouble with?

[Guest Jan M]

it shows "t-mobile" then "android" shows up for a bit,it blinks and just shows "android" again

I got basically the same thing when I tried to upgrade to 1.7 this morning...I tried wiping and reinstalling the ROM a few times...until I finally switched SD cards and it started to work...turns out the new ROM didn't like my old ROM's (1.0u8230 w/ 1.1mck) SD partitioning for some reason...so I went back and repartitioned the original SD and everything worked fine (except that data didn't want to pass through 3G for some reason...another wipe+ROM install fixed that)

biron, for you I would recommend installing the december update:

download, extract, copy "dload" folder to the root of your SD card

enter Update Mode: Volume Up + End Call (Red) button held down then tap Power button

note: this will wipe your data

Edited January 12, 2010 by Jan M

[Guest biron_w]

My pulse has been doing this quite often, usually on low battery till and one time when I was using Dolphin browser it just rebooted, not to sure why it happens yet. Usually I restore a backup and it works fine.

You need to use fastboot, there's no other way about it yet unless you've got the recovery rom installed and can use adb.

What step are you having trouble with?

All of it.Haha!

I've downloaded fastboot and read the instructions on the xda-developers website but don't know where to find the android sdk from(or even know what it is!).

I basically need a step by step guide to sorting it out.

Somebody has said to put the december update on my memory card but I don't have a memory card reader/writer for my pc.

[Guest Jan M]

Somebody has said to put the december update on my memory card but I don't have a memory card reader/writer for my pc.

you can get into recovery from fastboot...

download the patched recovery image, extract the contents, open folder with cmd.exe, connect phone-usb-computer, and run:

fastboot-windows.exe boot recovery-RA-pulse-v1.5.2.img

that should put you into recovery mode, from where you can toggle USB-SD mode to copy over the dload folder.

[Guest blue-e]

Hi guys,

I have been using the 8230 MCR 1.1 edition and when battery dies and you plug phone into charger it just loops like yours do.

I have however found an easy way around that. You need to turn phone on and then quickly insert charger before 1st android screen. Have had this happen a few times and its worked every time.

Updating to 1.7 now so will find out how that works shortly.

Hope this helps some of you

Dave

[Guest feelmychi]

you can get into recovery from fastboot...

download the patched recovery image, extract the contents, open folder with cmd.exe, connect phone-usb-computer, and run:

fastboot-windows.exe boot recovery-RA-pulse-v1.5.2.img

that should put you into recovery mode, from where you can toggle USB-SD mode to copy over the dload folder.

does adb need to be working for this to work (when I try that command it just tells me that it can't find the device...)? If so, could you please possibly tell us exactly how to get it working for the pulse - pretty please? :)

[Guest biron_w]

you can get into recovery from fastboot...

download the patched recovery image, extract the contents, open folder with cmd.exe, connect phone-usb-computer, and run:

fastboot-windows.exe boot recovery-RA-pulse-v1.5.2.img

that should put you into recovery mode, from where you can toggle USB-SD mode to copy over the dload folder.

I don't know how to get fastboot working in the first place.

It says with fast boot you copy fastboot to the system32 folder and then copy AdbWinApi.dll to the system 32 folder as well then run fastboot.When I run it I just get a message saying AdbWinApi.dll is missing from my computer.

Edited January 13, 2010 by biron_w

[Guest Jan M]

does adb need to be working for this to work (when I try that command it just tells me that it can't find the device...)?

in windows you need to install the drivers that came included on the miniCD...I unpacked the setup.exe with 7-zip and pointed windows' driver locator (that appeared after I started fastboot) to this location: setup.exe\$_OUTDIR\driver\Vista

after that I was able to bring up recovery with this:

D:\1.5.2-pulse-amonrarecovery>fastboot-windows.exe boot recovery-RA-pulse-v1.5.2.img

 downloading 'boot.img'... OKAY

 booting... OKAY

biron: AdbWinApi.dll is included in the recovery zip so if you run fastboot-windows.exe from there it should automatically find it...if not you can try replacing it with the one thats in the tools folder on the miniCD

and of course to put your phone into fastboot mode: turn if off, then tap the powerbutton while holding the 'Volume Down' and 'End (Red)' keys

[Guest biron_w]

How do you open a folder with cmd.exe?

I've copied the AdbwinApi thing but if I run fastboot-windows.exe boot recovery-RA-pulse-v1.5.2.img it still says it's not on my pc.

I'll just have to hope putting the update on my memory card works!

[Guest AndAddict]

How do you open a folder with cmd.exe?

I've copied the AdbwinApi thing but if I run fastboot-windows.exe boot recovery-RA-pulse-v1.5.2.img it still says it's not on my pc.

I'll just have to hope putting the update on my memory card works!

You need a quick lesson in cmd :)

First, to change drive, you type the drive letter followed by a colon, so if you wanted to go to your CD drive and its letter was F, you would type

F:

You can then show whats in that folder by typing

dir

And that will list all the files and folders in that directory, to go to another directory you use cd, so if the folder was called SDK, you would type

cd SDK

So if fastboot was in a folder called fastboot, in a folder called android on your C drive you would type:

C:

cd android

cd fastboot

fastboot-windows.exe boot recovery-RA-pulse-v1.5.2.img

[/codebox]

[Guest biron_w]

I have finally fixed this.Went through the process of sticking the december update on my memory card.